[KeyCloak OIDC] Username and Password Field

To resolve https://github.com/rancher/rancher/issues/33337 I have added a Username and a Password field to the oidc config.
These will need to be present in the UI for Keycloak OIDC so that an Admin level user can insert their credentials on auth provider setup - those credentials will then be used to get nested group information for users logging in. The fields are not required, but they are required if you want nested groups to work properly.
This also means you might not need to prompt the user that is setting up the auth provider to login, if you can pass along the username and password they entered into the config page but ultimately that is up to you. Acitve Directory, LDAP and Google have similar setups for an "Admin" if you need examples.
type OIDCConfig struct {
	AuthConfig `json:",inline" mapstructure:",squash"`

	ClientID               string `json:"clientId" norman:"required"`
	ClientSecret           string `json:"clientSecret,omitempty" norman:"required,type=password"`
	AdminAccountUsername string `json:"adminAccountUsername,omitempty"`
	AdminAccountPassword string `json:"adminAccountPassword,omitempty" norman:"type=password"`
	Scopes                 string `json:"scope", norman:"required,notnullable"`
	AuthEndpoint           string `json:"authEndpoint,omitempty" norman:"required,notnullable"`
	Issuer                 string `json:"issuer" norman:"required,notnullable"`
	Certificate            string `json:"certificate,omitempty"`
	PrivateKey             string `json:"privateKey" norman:"type=password"`
	RancherURL             string `json:"rancherUrl" norman:"required,notnullable"`
}

The service account user/pass should be an explicitly and very clearly labeled separate field from the "test" user (like it is in AD)..
You don't want to automatically reuse the user's credentials as the service account that's going to be used by Rancher forever (or even offer the option, if you want that you should explicitly type them in twice).  That person could change their password or be quit tomorrow.

As discussed with Brenda, these changes are now no longer required


Should base64 advance alone or should it be part of a larger proposal?

Somewhat related to my worries in https://github.com/bakkot/proposal-arraybuffer-base64/issues/6, I worry that working on a one-binary-encoding-per-proposal basis might have subpar ecosystem impacts. If base64 gets promoted to first-class language support, but base64url or hex require packages, that might not be the best outcome.
I understand from the discussions in #4 that the champions here don't like the API shape of https://github.com/lucacasonato/proposal-binary-encoding, but I think that proposal does a better job of putting multiple binary encodings on equal footing and ensuring they all get implemented together.
(It might also be worth doing some research on other binary encodings; base64, base64url, and hex are the ones I'm aware of from the research in https://github.com/lucacasonato/proposal-binary-encoding, but I guess the relevant RFC defines base32 as well, and I guess there are a lot of them: https://en.wikipedia.org/wiki/Binary-to-text_encoding )

I intend to support both base64 and base64url in this proposal. Hex is the only other format which is particularly common, and I agree it probably makes sense to include it here rather than doing it as a follow-on. I've opened #8 to track that explicitly.
Base32 and UU also exist, but as far as I can tell mostly only historically - I haven't ever encountered either in the wild. Base85/Ascii85 is used in PDFs and git-patch but does not seem to be common otherwise. I don't think it makes sense to include any of those.
Just to look around at our fellows a bit:

go supports base64, base32, hex, and ascii85
python supports hex, base32, base64, and Base85, as well as the legacy binhex and UU formats
java supports base64, and the widely used apache commons provides base16, base32, hex, and www-form-urlencoded
ruby supports base64 as a first-class module and also supports hex and UU format specifiers in Array#pack and String#unpack
rust supports hex as a format specifier
PHP supports base64, hex, UU, and www-form-urlencoded
C# supports base64 and hex

Elsewhere, @bakkot says that apparently Node.js's Buffer.from(x, "base64"), as well as CSP, support mixing base64 and base64 URL in the same string, when decoding. That might be a variant worth supporting in the API as well.


net: dragonfly broken by Listen after close on same addr

I seem to have broken the dragonfly builder after:
syscall: allow nacl's fake network code to Listen twice on the same address
https://go-review.googlesource.com/16650 (rev 8ee90fad1)
... which added a test to the net package, which dragonfly can't pass.
Failure is:
http://build.golang.org/log/732b7056b17948b06073dbe399de931765307152
--- FAIL: TestListenCloseListen (0.00s)
	net_test.go:283: failed on try 1/10: listen tcp <IP_ADDRESS>:52085: bind: address already in use
	net_test.go:283: failed on try 2/10: listen tcp <IP_ADDRESS>:52093: bind: address already in use
	net_test.go:283: failed on try 3/10: listen tcp <IP_ADDRESS>:52101: bind: address already in use
	net_test.go:283: failed on try 4/10: listen tcp <IP_ADDRESS>:52109: bind: address already in use
	net_test.go:283: failed on try 5/10: listen tcp <IP_ADDRESS>:52117: bind: address already in use
FAIL
FAIL	net	4.894s

I see a recent failure: http://build.golang.org/log/c6e3c951e0398d21ff52b932bc261ab70003120b
--- FAIL: TestServerConnState (1.02s)
	serve_test.go:3041: Unexpected events.
		Got log: Conn 1: new active idle active closed
		Conn 2: new active idle active
		Conn 3: new active hijacked
		Conn 4: new active hijacked
		Conn 5: new closed
		Conn 6: new active closed
		Conn 7: new active idle closed

		   Want: Conn 1: new active idle active closed
		Conn 2: new active idle active closed
		Conn 3: new active hijacked
		Conn 4: new active hijacked
		Conn 5: new closed
		Conn 6: new active closed
		Conn 7: new active idle closed

FAIL
FAIL	net/http	20.463s

... which suggests the net package, poller, or runtime are processing networking events in a different order than all the other platforms.
We also don't have a new-style builder for dragonfly, so people without dragonfly can't use gomote or trybots to debug.
I think a Dragonfly person needs to help.

This suggests that there is something wrong with the way we are using SO_REUSEADDR on DragonFly.  Unfortunately we use the same code on all the *BSD systems, so I have no idea why DragonFly would behave differently.

CC @fupjack @4a6f656c

I am working on tracking someone down who can solve it, who I will immediately refer to as NotMe.

Hi, my understanding is that SO_REUSADDR is meant to relax the rules of address collision at bind. The man says :

SO_REUSEADDR indicates that the rules used in validating addresses supplied in a bind(2) call should allow reuse of local addresses.

This is not really clear, but what it appears to mean is that you can have collision in your binding : for instance you can bind to '<IP_ADDRESS>:80' and then bind to '<IP_ADDRESS>:80', something which is disallowed without this flag. But you cannot bind twice to the same exact (addr, port) tuple.

SO_REUSEPORT allows completely duplicate bindings by multiple processes

SO_REUSEPORT on the other hand allows for this behavior. You can bind twice to the syntaxically identical (addr, port) tuple.
I've tested your (bind/listen/close/bind/listen) example (in C) and indeed, it's working with SO_REUSEPORT but returns EADDRINUSE with SO_REUSEADDR.

SO_REUSEADDR permits a server to quickly bind to the same local address, without having to wait for the TCP TIME_WAIT state to expire.  This is a long-standing feature of the socket network API.  If it doesn't work on Dragonfly (I don't know whether it does or not), that has to be considered a bug in Dragonfly.
SO_REUSEPORT is much newer.  It permits multiple servers to bind to the same local address.  That is not what we want here.

This is indeed a bug in dfly.

Fixed here:
http://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/296c350d3c63a181744b80a4b7973dac5fc162a3
I've cleared the most recent breaks in the DragonFly builder and restarted them, and they are completing this test.  (Albeit still failing with a different error that I suspect is related to the gold linker coming in to DragonFly.)

Looks like dragonfly guys have finished working on handling of shared IP control blocks. So the latest DragonFly kernels, at least 4.4 and above, have no issues. Also we can re-enable TestDualStack{TCP,UDP}Listener in Go 1.7. Closing.


Update meta.yaml - separate constraints vs cuda 11.2 and 11.8

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

conda-forge-admin, please rerender

@isuruf ,  I think the previous commits did not add the constraints for cuda 11.8 - I assume that's necessary since the build is made against 11.2, 11.8 and none ?


Confusing failure when cloning inside an existing git project

@wmputman attempted a mepo clone within a directory that already had a .git.    The failure message was at best confusing and may mean that mepo did not correctly detect the topdir at some point:
GIT/GEOS-v10p22p0> mepo clone -b v10.22.0 git@github.com:GEOS-ESM/GEOSgcm.git
env                    | (t) v3.13.0
cmake                  | (t) v3.12.0
ecbuild                | (t) geos/v1.2.0
fatal: cannot change to '/gpfsm/dnb03/projects/p38/GIT/GEOS-v10p22p0/./src/Shared/@NCEP_Shared': No such file or directory

Traceback (most recent call last):
  File "/discover/swdev/gmao_SIteam/mepo/mepo", line 17, in <module>
    main()
  File "/gpfsm/dswdev/gmao_SIteam/mepo/mepo.d/main.py", line 6, in main
    command.run(args)
  File "/gpfsm/dswdev/gmao_SIteam/mepo/mepo.d/command/command.py", line 11, in run
    cmd_module.run(args)
  File "/gpfsm/dswdev/gmao_SIteam/mepo/mepo.d/command/clone/clone.py", line 76, in run
    git.sparsify(comp.sparse)
  File "/gpfsm/dswdev/gmao_SIteam/mepo/mepo.d/repository/git.py", line 71, in sparsify
    shellcmd.run(shlex.split(cmd1))
  File "/gpfsm/dswdev/gmao_SIteam/mepo/mepo.d/utilities/shellcmd.py", line 15, in run
    result.check_returncode()
  File "/usr/local/other/python/GEOSpyD/4.10.3_py3.9/2022-01-14/lib/python3.9/subprocess.py", line 460, in check_returncode
    raise CalledProcessError(self.returncode, self.args, self.stdout,
subprocess.CalledProcessError: Command '['git', '-C', '/gpfsm/dnb03/projects/p38/GIT/GEOS-v10p22p0/./src/Shared/@NCEP_Shared', 'config', 'core.sparseCheckout', 'true']' returned non-zero exit status 128.

Clone was from within:  gpfsm/dnb03/projects/p38/GIT/GEOS-v10p22p0
which looked like this:
  /gpfsm/dnb03/projects/p38/GIT/GEOS-v10p22p0:
  total used in directory 101 available<PHONE_NUMBER>76
  drwxr-sr-x 10 wputman s1062 8192 Apr 12 11:37 GEOSgcm
  drwxr-sr-x  8 wputman s1062 8192 Apr 12 11:37 .
  drwxr-sr-x  8 wputman s1062 8192 Apr 11 22:10 .git
  drwxr-sr-x  2 wputman s1062  512 Apr 11 12:40 .mepo
  -rw-r--r--  1 wputman s1062  103 Apr 11 12:40 .gitignore
  drwxr-sr-x  4 wputman s1062  512 Apr 11 12:40 .github
  -rw-r--r--  1 wputman s1062  674 Apr 11 12:40 .editorconfig
  drwxr-sr-x  2 wputman s1062  512 Apr 11 12:40 .codebuild
  drwxr-sr-x  2 wputman s1062  512 Apr 11 12:40 .circleci
  drwxr-sr-x 38 wputman s1062 8192 Apr  9 20:34 ..

This is actually weirder than you think. I found a more perverse mepo issue looking at this. Give me a bit...


All button styles are the same color

Describe the bug
All button styles are the same color
To Reproduce
Send a button component with any style other than one
Screenshots

Infomation (please complete the following information):
Discord channel: Stable
OS: Win10
Mod: BetterDiscord
Discord language: English
Additional context
See https://discord.com/developers/docs/interactions/message-components#buttons-button-styles

Newest update should fix this.


NameError: name 'osp' is not defined

import keras
from vis.visualization import visualize_activation
Using TensorFlow backend.
ImportError                               Traceback (most recent call last)
~\Anaconda3\envs\cv\lib\site-packages\skimage_init_.py in
161     try:
--> 162         from ._shared import geometry
163         del geometry
ImportError: DLL load failed: The specified module could not be found.
During handling of the above exception, another exception occurred:
NameError                                 Traceback (most recent call last)
 in
1 import keras
2
----> 3 from vis.visualization import visualize_activation
~\Anaconda3\envs\cv\lib\site-packages\vis\visualization_init_.py in
2
3
----> 4 from .activation_maximization import visualize_activation_with_losses
5 from .activation_maximization import visualize_activation
6
~\Anaconda3\envs\cv\lib\site-packages\vis\visualization\activation_maximization.py in
4 from keras import backend as K
5
----> 6 from ..losses import ActivationMaximization
7 from ..optimizer import Optimizer
8 from ..regularizers import TotalVariation, LPNorm
~\Anaconda3\envs\cv\lib\site-packages\vis\losses.py in
2
3 from keras import backend as K
----> 4 from .utils import utils
5
6
~\Anaconda3\envs\cv\lib\site-packages\vis\utils\utils.py in
12 from .. import backend
13
---> 14 from skimage import io, transform
15 from collections import Iterable
16 from keras import backend as K
~\Anaconda3\envs\cv\lib\site-packages\skimage_init_.py in
163         del geometry
164     except ImportError as e:
--> 165         _raise_build_error(e)
166     # All skimage root imports go here
167     from .util.dtype import (img_as_float32,
~\Anaconda3\envs\cv\lib\site-packages\skimage_init_.py in _raise_build_error(e)
136 def _raise_build_error(e):
137     # Raise a comprehensible error
--> 138     local_dir = osp.split(file)[0]
139     msg = _STANDARD_MSG
140     if local_dir == "skimage":
NameError: name 'osp' is not defined

Thank you for your report.

ImportError: DLL load failed: The specified module could not be found.
During handling of the above exception, another exception occurred:

However, it seems a problem of Anaconda or your Windows environment.
I don't use either Anaconda and Windows, so I can't suggest any good idea, sorry.
We hope you can enjoy keras-vis.
Let us know to feel free when you find any problem about keras-vis.


MultiDirChooser does not handle Windows volume labels correctly

[x] OS - Windows 7
[x] Python Version - 3.8
[x] Gooey Version - 1.0.3 (with fix for Issue #550)
[x] Thorough description of problem

[x] Expected Behavior
After choosing a directory (or more) in the MultiDirChooser, I should be able to use the value of the argument as a valid directory name on the system.
[x] Actual Behavior
Attempting to use the argument value as a directory name gives me this message:

OSError: [WinError 123] The filename, directory name, or volume label syntax is incorrect: 'Media (E:)\Users\My Name\Music'

I imagine this ought to be just E: as the volume label, not Media(E:).

[x] A minimal code example -- preferably copy/pastable in the issue itself (less time figuring out how to run your code == more time debugging!)
Run the following on a Windows machine, selecting at least one directory. Observe the error message in the output window.

import os

from gooey import Gooey
from gooey import GooeyParser

@Gooey
def main(args):
    parser = GooeyParser()
    parser.add_argument("dirnames", nargs = "+", widget="MultiDirChooser")
    args = parser.parse_args(args)

    # try to access the given path
    os.listdir(args.dirnames[0])

if __name__ == '__main__':
    import sys
    main(sys.argv[1:])

[x] Screenshot (if visual quirk) - N/A, incorrect volume syntax appears in GUI as well.
[x] Anything else you may think will be helpful
The plain 'ol DirChooser does not have this problem.

I'm investigating and will hopefully have a pull request for you soon.

This appears to be how wx.lib.agw.multidirdialog provides the directories; Gooey is not doing anything wrong here.

And that appears to be a consequence of wx.lib.agw.multidirdialog having volume labels in its chooser.
Since wx.lib.agw.multidirdialog hasn't seen changes since 2012, I assume this is the correct behavior for it. However, it's very bad behavior for Gooey, so probably Gooey should add some additional massaging to the output of the wx dialog.

Pull request now merged! Thanks for the fix!


ISSUE: Error saving configuration when upgrading to 0.1.4

Describe the bug
Received an error about configuration formatting because of the new option for random string image name.
Resolution: Turn it on, save, then turn it off.
This would not be a problem for new setups.

Issue pinned in case someone runs into this issue in the future.


load-grunt-tasks added in the project.

This pull request includes a

[ x] New feature

The following changes were made

make Gruntfile.js  a bit smaller, we saved a bit of lines.
Very Easy now if someone install a dependency in the project from package.json, does not need to load this  in the Gruntfile.js

when usually  happen the merges? thanks

I'm honestly not sure if the extra dependency is worth it. I actually don't mind the fact that we have to be explicit when loading in Grunt tasks.

when usually happen the merges? thanks

It usually takes more than a day, we're a small team with other full-time jobs.

@kevin-brown  np, I just want to contribute with the project, even more with scss part, but I understand your approach.
it is a scss documentation for this project? thank you very much


feat: wip

bb bench in comments

Benchmark results
Metrics with a significant change:

note_trial_decrypting_time_in_ms (32): 95.1 (+271%)
note_trial_decrypting_time_in_ms (64): 109 (+80%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit a0720ff3 and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
64 txs

l1_rollup_calldata_size_in_bytes
676
676
676

l1_rollup_calldata_gas
6,424
6,412
6,424

l1_rollup_execution_gas
585,757
585,745
585,757

l2_block_processing_time_in_ms
1,313
4,871 (+4%)
9,154 (-2%)

note_successful_decrypting_time_in_ms
268 (+4%)
578 (-5%)
1,082 (+5%)

note_trial_decrypting_time_in_ms
70.6 (+11%)
:warning: 95.1 (+271%)
:warning: 109 (+80%)

l2_block_building_time_in_ms
12,185
44,369 (-1%)
88,506 (+1%)

l2_block_rollup_simulation_time_in_ms
7,438
25,747 (-1%)
51,249 (+1%)

l2_block_public_tx_process_time_in_ms
4,726
18,568 (-1%)
37,156

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

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
13,997
26,691 (-3%)

note_history_successful_decrypting_time_in_ms
1,333 (+8%)
2,473

note_history_trial_decrypting_time_in_ms
91.6 (+6%)
146 (-3%)

node_database_size_in_bytes
18,624,592
34,828,368

pxe_database_size_in_bytes
29,859
59,414

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

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
183 (+1%)
44,379
28,214

private-kernel-ordering
170 (+1%)
52,880
14,296

base-parity
3,676 (+4%)
128
311

root-parity
1,273 (-1%)
1,244
311

base-rollup
14,966
165,760
861

root-rollup
49.5
4,359
725

private-kernel-inner
228 (+1%)
73,795
28,214

public-kernel-app-logic
95.5
35,252
28,217

public-kernel-tail
138 (-1%)
40,928
28,217

merge-rollup
8.72 (+6%)
2,568
861

public-kernel-teardown
92.9 (+1%)
35,252
28,217

public-kernel-setup
92.1 (+1%)
35,252
28,217

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

Metric
1 leaves
16 leaves
64 leaves
128 leaves
512 leaves
1024 leaves
2048 leaves
4096 leaves
32 leaves

batch_insert_into_append_only_tree_16_depth_ms
10.1 (+1%)
16.1 (+1%)
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.8
31.6
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.588 (+1%)
0.497
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
46.3 (-1%)
72.8
232
453 (+1%)
876
1,749 (+2%)
N/A

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
96.0
159
543
1,055
2,079
4,127
N/A

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.474 (-1%)
0.448
0.422
0.422 (+1%)
0.416 (+1%)
0.419 (+2%)
N/A

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
54.5
108 (+1%)
337
670 (+1%)
1,315
2,624 (+1%)
N/A

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
105
207
691
1,363
2,707
5,395
N/A

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.481
0.485 (+1%)
0.458
0.460
0.455
0.457 (+1%)
N/A

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
61.7 (+1%)

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
109

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
0.538

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

Metric
0 registered classes
1 registered classes

tx_size_in_bytes
14,968
495,320

Transaction size based on fee payment method

Metric
none fee payment method
native fee payment method
fpc_public fee payment method
fpc_private fee payment method

tx_with_fee_size_in_bytes
773
905
1,161
1,377

Transaction processing duration by data writes.

Metric
0 new note hashes
1 new note hashes
2 new note hashes

tx_pxe_processing_time_ms
1,813 (+1%)
1,208 (+1%)
5,743 (+2%)

Metric
0 public data writes
1 public data writes
2 public data writes
3 public data writes
4 public data writes
5 public data writes
8 public data writes

tx_sequencer_processing_time_ms
10.3 (-14%)
582
445 (+2%)
1,186 (+2%)
592 (+1%)
2,053 (+2%)
568 (+1%)


Package Gaia

We might need to need this in few months for end-to-end testing. One thing to keep in mind is that we will have to build different major versions of Gaia for testing, for example v4.2 and v5.0. So it would be good to make the Nix module modular such that the user can instantiate Gaia with different versions of source code.

That's a good point. That should be fairly straightforward, we can specify a different input per version, and set the rev of the input to the tag of that major version release. I am thinking 3.0.1, 4.2.1, and 5.0.5 would be a reasonable place to start?

Sounds good. Just 4.2.1 and 5.0.5 should be fine. I think the ecosystem has mostly moved to v4 now, and are beginning to move to v5.

despite https://github.com/informalsystems/cosmos.nix/pull/8 I am leaving this open until I add support for v5 and v4


Different values returned from getberegnregnskab

Hi
It looks like my data returned looks a bit different from what you are using in your code, so I have attached my data, if you want to use it.
For example, my line 18 is the aconto amount (for each aconto) and I got a line 7 and 22 also.
{"faktlini":[{"ekstra":"kr.","enhedPris":"392,00","linieType":"3","antalEnheder":"5,290","enhed":"MWh","tekst":"6464705","prisEnhed":"kr./MWh","opl4":"MWh","opl3":"152,753","opl2":"MWh","opl1":"147,463","ialt":"2.073,68"},{"ekstra":"kr.","enhedPris":"392,00","linieType":"3","antalEnheder":"7,464","enhed":"MWh","tekst":"Prognose: 08-04-2023 til 31-12-2023","prisEnhed":"kr./MWh","opl4":"","opl3":"","opl2":"","opl1":"","ialt":"2.925,89"},{"ekstra":"","enhedPris":"","linieType":"22","antalEnheder":"","enhed":"","tekst":"","prisEnhed":"","opl4":"","opl3":"","opl2":"","opl1":"","ialt":""},{"ekstra":"","enhedPris":"","linieType":"22","antalEnheder":"","enhed":"","tekst":"Gennemsnitlig fremløbstemp. i perioden","prisEnhed":"","opl4":"°C","opl3":"61,64","opl2":"","opl1":"","ialt":""},{"ekstra":"","enhedPris":"","linieType":"22","antalEnheder":"","enhed":"","tekst":"Gennemsnitlig returtemp. i perioden","prisEnhed":"","opl4":"°C","opl3":"25,06","opl2":"","opl1":"","ialt":""},{"ekstra":"","enhedPris":"","linieType":"22","antalEnheder":"","enhed":"","tekst":"Forventet returtemperatur","prisEnhed":"","opl4":"°C","opl3":"40,00","opl2":"","opl1":"","ialt":""},{"ekstra":"kr.","enhedPris":"","linieType":"22","antalEnheder":"","enhed":"","tekst":"Ingen tillæg","prisEnhed":"","opl4":"%","opl3":"0,00","opl2":"","opl1":"","ialt":"0,00"},{"ekstra":"","enhedPris":"","linieType":"22","antalEnheder":"","enhed":"","tekst":"","prisEnhed":"","opl4":"","opl3":"","opl2":"","opl1":"","ialt":""},{"ekstra":"","enhedPris":"","linieType":"0","antalEnheder":"","enhed":"","tekst":" ","prisEnhed":"","opl4":"","opl3":"","opl2":"","opl1":"","ialt":""},{"ekstra":"kr.","enhedPris":"10,00","linieType":"1","antalEnheder":"106","enhed":"m²","tekst":"Beboelse iflg. BBR","prisEnhed":"kr./m²","opl4":"","opl3":"","opl2":"dage","opl1":"365","ialt":"1.060,00"},{"ekstra":"kr.","enhedPris":"600,00","linieType":"7","antalEnheder":"","enhed":"","tekst":"Abonnement","prisEnhed":"kr./år","opl4":"","opl3":"","opl2":"dage","opl1":"365","ialt":"600,00"},{"ekstra":"","enhedPris":"","linieType":"0","antalEnheder":"","enhed":"","tekst":" ","prisEnhed":"","opl4":"","opl3":"","opl2":"","opl1":"","ialt":""},{"ekstra":"kr.","enhedPris":"","linieType":"12","antalEnheder":"","enhed":"","tekst":"Total før moms","prisEnhed":"","opl4":"","opl3":"","opl2":"","opl1":"","ialt":"6.659,57"},{"ekstra":"kr.","enhedPris":"","linieType":"10","antalEnheder":"25","enhed":"%","tekst":"Moms","prisEnhed":"","opl4":"","opl3":"","opl2":"","opl1":"","ialt":"1.664,89"},{"ekstra":"kr.","enhedPris":"","linieType":"12","antalEnheder":"","enhed":"","tekst":"Total med moms","prisEnhed":"","opl4":"","opl3":"","opl2":"","opl1":"","ialt":"8.324,46"},{"ekstra":"kr.","enhedPris":"","linieType":"18","antalEnheder":"","enhed":"","tekst":"Opkrævet acontorate (med moms)","prisEnhed":"","opl4":"","opl3":"","opl2":"","opl1":"","ialt":"-1.700,00"},{"ekstra":"kr.","enhedPris":"","linieType":"20","antalEnheder":"","enhed":"","tekst":"Forventet indbetalt: 08-04-2023 til 31-12-2023","prisEnhed":"","opl4":"","opl3":"","opl2":"","opl1":"","ialt":"-6.800,00"},{"ekstra":"kr.","enhedPris":"","linieType":"12","antalEnheder":"","enhed":"","tekst":"Årets forventede resultat","prisEnhed":"","opl4":"","opl3":"","opl2":"","opl1":"","ialt":"-175,54"},{"ekstra":"","enhedPris":"","linieType":"0","antalEnheder":"","enhed":"","tekst":" ","prisEnhed":"","opl4":"","opl3":"","opl2":"","opl1":"","ialt":""}]}

Thanks. Does your PR take care of all relevant differences?

Thanks. Does your PR take care of all relevant differences?

No, but im looking into it 😃

Hi again.
Today, I saw that I've have paid to much last year, so for the first rate (due to 01-03-23) instead of paying 1700,- dkr I had to pay 246,78 dkr.
But somehow that's not reflected in the heat accounting.
This year, it's divided into 5 payments, the first 01-03-23 then 01-05-23 and so forth, but when I look how they summed it up, they added the 01-05-23 rate as unpaid. That way the rest of April, it looks like, that I by the end of the year are 1400,- dkr short of payment when in fact they owe my 230,- dkr.
Maybe there's a way to get around this

This report is really difficult because it seems this is not standardised across all eForsyning companies.  Some use more text, some less, some uses some words, other not for the same thing.
From this report I pick out the price of M3 and MWh, VAT and the total incl. VAT line (8269,09 in your case).  The amount paid (Opkrævet acontorate (med moms), and lastly the Amount remaining (Forventet indbetalt) which is both an attribute and the actual sensor value.
Those were the only amounts I could get to line up consistently :-)  The 'good' thing is that the amount remaining is adjusted every day and gives an indication of where it is headed (hopefully towards 0).


Alphabet Offset Scale Fix

This missing maths was causing a weird bug with the letters offsets with edited scale; for example I tested with scaleX and scaleY = 0.6 and with aligment = RIGHT
Before this fix:

After this fix:

good stuff, can u test with heights also? it'd be like awesome

good stuff, can u test with heights also? it'd be like awesome

tested with text.height -= text.height / 2; and everything seems to work as intended:

it works fine even with normal scaleX and scaleY being at 0.6 and viceversa:

Thanks and this is for the Big engine Brawl mod bug right man

Thanks and this is for the Big engine Brawl mod bug right man

Whats that

Big Engine Brawl is a mod directed by ronbrazy and Jack Orange, published to GameBanana under the team name Astral Lane. The sequel (Big Engine Brawl 2) plans to be released under a new team name known as "Vicarstown Creations" due to Astral Lane moving on from FNF due to creative differences.
The mod is mainly based off of the classic Thomas & Friends show, with Story Mode featuring loose adaptations of three particular Season 1 episodes.

oh alr

Ok

Wait how should i edit this to fix it when i can't enter the mod?


Allow to instantiate DenseKKTSystem on CUDA GPU

This is the final step: we can now solve dense problem on the GPU with MadNLP, without transferring the Hessian and the Jacobian matrices to the host.
This PR adds a few structural changes:

MadNLPGPU now depends on KernelAbstractions.jl. The module now implements a few kernel functions to assemble and analyse the KKT system directly on the GPU.
The signature of MadNLPLapackGPU.Solver has been updated to MadNLPLapackGPU.Solver{MT<:AbstractMatrix}, so we can now instantiate solver.dense on the GPU to avoid expensive transfer between the host and the device.
The signature of MadNLP.Solver has been updated, to take as input a kkt system (by default equal to nothing). This clashes with the previous solution (specifying the KKT system we want in the options). I think we should figure out a better API for this.
We check the correctness of the results on the GPU directly in MadNLPGPU/test/runtests.jl, by checking that we get exactly the same results as on the CPU.
build_qp_tests has been moved to MadNLPTests.

@frapac The issue probably was that I didn't start the action after moonshot's reboot. I wasn't able to find a way to automatically restart after reboot 😂

Merging it to master. Thanks for the great work.


update build for dax_imgserv

Please review changes: 1) remove obsolete dax/webserv build 2) enhance docker build for imgserv.

Sorry, I'm a bit out of my depth here in terms of the Jenkins parts.  We're removing the old one, which I understand, is the new one just being scheduled here with this change?

@cbanek See DM-20192.  The new one was set up to run prior, but now is much enhanced with this change.

Ah okay, yes knowing the ticket is helpful.  I think it is standard practice to tie the ticket name to the branch name or something in the commit message to link everything together.

Now I see what you mean (even for a forked repo) looking at the commits history of this repo.   I will try that route next time, tying in the ticket with the PR.


rafs: introduce iterator to walk inode of a rafs filesystem

Introduce iterator to walk inode of a rafs filesystem.
Signed-off-by: Jiang Liu<EMAIL_ADDRESS>

/retest


master

Coverage increased (+0.2%) to 71.939% when pulling 51b93021c825372029ebbca4e04a9ea6a3dcfe55 on dev into 45fd6e0a4e38915afa6df33b3085834ea59e74d6 on master.


Training time finished without completing a successful trial. Either no trial completed or the metric for all completed trials are NaN or Infinity

at Microsoft.ML.AutoML.AutoMLExperiment.d__24.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.ML.ModelBuilder.AutoMLService.Experiments.MultiClassificationExperiment.d__14.MoveNext() in //src/Microsoft.ML.ModelBuilder.AutoMLService/Experiments/MultiClassificationExperiment.cs:line 140
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.ML.ModelBuilder.AutoMLEngine.d__21.MoveNext() in //src/Microsoft.ML.ModelBuilder.AutoMLService/AutoMLEngineService/AutoMLEngine.cs:line 169
i have this error
im reading https://dotnet.microsoft.com/en-us/learn/ml-dotnet/get-started-tutorial/train
anyone can help me?
i hope i write currectly (im persion)

I am having this same issue.  I even set the training time to 240 seconds.

How large the dataset do you have.

It was very small.  Probably only 60 records.  I had to tell it which column to look at when I was doing the import and it worked nicely that time.
So, issue resolved.
Jim
From: Xiaoyun Zhang @.>
Sent: Friday, October 6, 2023 1:14 PM
To: dotnet/machinelearning-modelbuilder @.>
Cc: Jim Bliss @.>; Manual @.>
Subject: Re: [dotnet/machinelearning-modelbuilder] Training time finished without completing a successful trial. Either no trial completed or the metric for all completed trials are NaN or Infinity (Issue #2777)
How large the dataset do you have.
—
Reply to this email directly, view it on GitHubhttps://github.com/dotnet/machinelearning-modelbuilder/issues/2777#issuecomment-1751211820, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BDCMETDT3LPKFFGXV7IQTILX6BC5HAVCNFSM6AAAAAA5HYORNOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJRGIYTCOBSGA.
You are receiving this because you are subscribed to this thread.Message ID<EMAIL_ADDRESS>

By the way, you can close my ticket at this time.
Jim
From: Xiaoyun Zhang @.>
Sent: Friday, October 6, 2023 1:14 PM
To: dotnet/machinelearning-modelbuilder @.>
Cc: Jim Bliss @.>; Manual @.>
Subject: Re: [dotnet/machinelearning-modelbuilder] Training time finished without completing a successful trial. Either no trial completed or the metric for all completed trials are NaN or Infinity (Issue #2777)
How large the dataset do you have.
—
Reply to this email directly, view it on GitHubhttps://github.com/dotnet/machinelearning-modelbuilder/issues/2777#issuecomment-1751211820, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BDCMETDT3LPKFFGXV7IQTILX6BC5HAVCNFSM6AAAAAA5HYORNOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJRGIYTCOBSGA.
You are receiving this because you are subscribed to this thread.Message ID<EMAIL_ADDRESS>

Make sure the column to predict correctly chosen


Updated cronnix (3.0.2)

Tick #17075

Thank you for the contribution. It was merged directly as b6304a019295fb9ad6d4739a46773e8aa63cd3da to keep commit history cleaner. Your contribution is still credited to you.


🏗 Enhance carousel buttons to be arrows

Description
We can create custom components to use as the carousel 'next' and 'prev' buttons. We should update to something a bit smaller and cleaner. My thought is circular buttons with arrows inside.
We can also consider adding a tooltip, and ensuring they are easily keyboard navigable.
Docs
https://formidable.com/open-source/nuka-carousel/api#defaultcontrolsconfig
Example
https://github.com/FormidableLabs/nuka-carousel/blob/main/website/src/components/controls.tsx

Need to double check, but I think this was done with the recent nuka-carousel update.


Have talk/event level flag to turn off collecting talk ratings

This feature request might go against the grain of joind.in so feel free to discard.
I run a meetup and we typically get between 10% and 20% of attendees rating talks. See here
We advise attendees to give feedback along the line so:

what you liked
how it can be even better

The main purpose we push for giving feedback is to help speakers improve. Arguably the most important feedback for speakers to receive is how to improve for next time.  PHPSW is, and I might be biased, quite a friendly and supportive group and I think there are times when people are not as happy to give low ratings (anything under 4).  As a consequence the how to improve next time advice is lost.
If there was an option to turn off rating the talks, but still capturing the feedback, then I think that might be beneficial to meetups.  Especially for times when we have new speakers or they are not looking to get ratings for conference submissions.

Not "going against the grain" at all; have discussed as much internally, as a detailed comment without a rating is more useful than the converse basically 100% of the time.


Full API reference is blank on readthedocs.io

When going to https://pylookml.readthedocs.io/en/latest/reference.html , I see nothing:

What I've tried so far:

Tried with Firefox and Chrome
Tried going back to stable version

@EricHeidbreder  apologies for the delay. Looking into this today


[FLINK] Fix fetch timeout in session conf doesn't support ISO-8601

:mag: Description
Issue References 🔗
Currently, Flink engine supports overwriting result fetch timeout in session conf, but in that way IOS-8601 time format is not supported. This PR fixes the problem.
This pull request fixes #
Describe Your Solution 🔧
Apply ConfigOption's time value conf parsing in session conf parsing.
Types of changes :bookmark:

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Test Plan 🧪
Behavior Without This Pull Request :coffin:
Behavior With This Pull Request :tada:
Related Unit Tests

Checklists
📝 Author Self Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] This patch was not authored or co-authored using Generative Tooling

📝 Committer Pre-Merge Checklist

[x] Pull request title is okay.
[x] No license issues.
[x] Milestone correctly set?
[x] Test coverage is ok
[x] Assignees are selected.
[x] Minimum number of approvals
[x] No changes are requested

Be nice. Be informative.

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

Comparison is base (f4a739e) 61.41% compared to head (417898a) 61.35%.
Report is 1 commits behind head on master.

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #5799      +/-   ##
============================================
- Coverage     61.41%   61.35%   -0.06%
  Complexity       23       23
============================================
  Files           607      607
  Lines         35948    35948
  Branches       4939     4939
============================================
- Hits          22077    22056      -21
- Misses        11486    11502      +16
- Partials       2385     2390       +5

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

Merged to master and 1.8-branch.


Integrate New Feedback Form UI into the Feedback Page for DLP

Subtask for Feedback Form Revamp

@alantao912, @codingwithsurya will work on the feedback form UI revamp

@alantao912 Just to update this issue -- I have handed this issue to @alantao912
Alan, please feel free to let me know if you have any questions!

@alantao912 more info on feedback form revamp
https://github.com/DSGT-DLP/Deep-Learning-Playground/issues/906

@alantao912 update on this?


An experimental support of msgpack as Marshalling backend

Note this drops jruby support until msgpack-jruby is properly merged into official msgpack with all features.

Coverage decreased (-0.68%) when pulling fb2e2abb619b2a681b8edca54ac5500ea56b1e54 on niamster:master-next into b65b9b4b1626abd2955ff85a7484d91eee4264b4 on celluloid:master.

msgpack-jrubx just got merged into msgpack-ruby ☺

Spec with jruby-head doesn't pass but it's not tested by msgpack so I'm about to merge this if everybody agree.

Nice! :+1:


Write a GO program to check anagram string

Description
Write a GO program to check anagram string
Two strings are said to be anagrams if they make a meaningful word by rearranging or shuffling the letters of the string. In other words, we can say that two strings are anagrams if they contain the same characters but in different order.
Input  : pan, nap
Output : Anagram Strings

Contributed by - @sahdev77

How to contribute

Save the solution in write_a_program_to_check_anagram_string.go file
Add write_a_program_to_check_anagram_string.go file in program/write-a-program-to-check-anagram-string folder

Can you assign this to me


build failed

thanks first.
I enter ../Frameworks/gyroflow/ directory and typing " cargo build ", it failed with err info as:
error: failed to ruin custom build command for object_exception v0.1.2 ..
any advice for this issue, I am rust beginner ,thanks~

You should just be able to use the /Scripts/build_rust.sh build script to build the Rust code.

You can also learn more about building Gyroflow here:
https://docs.gyroflow.xyz/app/technical-details/building-from-source

Thanks for you response ! latenitefilms!


Fixed test issue for SD model with disabled LoRA adapter

Hi!
I've bumped up a threshold for comparing base Stable Diffusion output to Stable Diffusion + LoRA with disabled adapter.
Somehow on my machine, the version from main was failing (giving difference in output about 0.02).
@pacman100 @BenjaminBossan your review is kindly appreciated

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

It also seems strange to me, from my perspective, there is nothing unusual in my setup (just using the provided Dockerfile for peft-gpu).
Currently, I would like to work on some additions to PEFT LoRA SVD decomposition, but the tests are failing on my local machine.
Does this threshold is just a "percentage of image changed"? Maybe something about 0.05 would fit?

From my experience, the results of SD may be very dependent on the scheduler used, seeding, and also the GPU card you are trying to inference on.
Despite the output images may look very similar, they may have some big differences even when using txt2img, so on one machine I may get a dog with some shadow behind it, and on another machine, I may get a dog with less visible shadow, so results may differ from setup.

Here is an example (note the difference in grass and shadow between these two):
The output on 1st machine:

The output on 2nd machine:

Here is what I am getting when this test fails.
output_before:

output_peft_disabled:

Here are the pixels that differ:

From my experience, the results of SD may be very dependent on the scheduler used, seeding, and also the GPU card you are trying to inference on.

Yes, I agree on that, but for the unit tests, all those parameters should be the same right? The only thing that may differ is the seed if we forget to set it correctly.

Does this threshold is just a "percentage of image changed"? Maybe something about 0.05 would fit?

Hmm, that's still quite high. On the other hand, I guess we can argue that 95% of pixels being identical cannot really happen if the adapter is not correctly disabled. Another idea could even be to measure the divergence with adapters_enabled and then assert that with adapters disabled, it should be much lower (instead of coding a fixed threshold).

@BenjaminBossan yes, that is an intresting point, and it should work fine. Updated the code to match the proposed method.
However, I've found out that one of the tests I've written for SD also fails "sometimes" (maybe 1 time out of 5):
https://github.com/huggingface/peft/blob/7d44026dea18221e33affaa4868c908ef2c33f54/tests/test_stablediffusion.py#L118-L121
I've run tests on two machines and saw that if fails sometimes on both of them (so probably this fail is not machine-specific). It also seems strange to me, that this test fails even if I enable deterministic mode in torch, so probably this is related to something else. Maybe you have some suggestion on how this test should be changed to also be valid all the times?
Here is what I get when this test fails:
peft_output:

merged_output:

pixels that differ between them:

I'm not sure if you're finished with your changes or not, but I think this line needs some work:
            self.assertTrue(
                (output_before != output_peft).float().mean() / (output_before != output_peft_disabled).float().mean()
            )

As it, it doesn't perform any meaningful check. I think what we should test is that with peft disabled, the divergence should be much lower than with peft enabled. So something along the lines of:
mean_diff_enabled = (output_before != output_peft).float().mean()
self.assertTrue(diff_enabled > 0.9)
mean_diff_disabled = (output_before != output_peft_disabled).float().mean()
# check that there are far fewer differences with peft disabled
# ideally, differences should be 0, but that cannot be guaranteed...
self.assertTrue(mean_diff_disabled < 0.1 * mean_diff_enabled)

The test function would need to be rearranged a bit to not make it too confusing.

I've found out that one of the tests I've written for SD also fails "sometimes" (maybe 1 time out of 5):

That's strange. Is it the test you linked or are you talking about another test? Does this happen with both GPU and CPU?
It could be that the test is flaky, which would be very unfortunate. There are some ways to live with flaky tests, but ideally we can avoid it.


Strike through link to closed issue

Like Bugzilla, strike through the link to a closed issue or PR. Perhaps some slightly different formatting for merged PRs as well. cf https://github.com/isaacs/github/issues/451, https://github.com/isaacs/github/issues/313

Would be useful indeed, but we would have to use the GitHub API for this, which has limits on how many requests we can do, so it gets complicated fast. We would also need to have an options page for the user to save their token. We could fetch the whole page instead and have no limits, but that's wasteful.

I would have liked that if it could have been done without requests.
Regarding the actual UI, I'd go with an icon of open/closed issue/PR. This way you'll also know what's this number is referring to.

This seems to be the same as #202.

@durka You are absolutely right! Closing in favour of #202.


Fix types

Fix for https://github.com/DidoMarchet/vue-3-supabase/issues/2

Hi @vasia123,
thanks for your contribute.
I publish the new release so you can try.
Let me know and kind regards,
Davide


Icons are not appear on Dark Menu Bar

It is impossible to see icons on Dark Menu Bar.

I have forked your project. I will try to do that change and pull request ASAP ;-)
Great project btw ^^ Thank you.

Oh, didn't think about that!
It would be awesome if you have the chance to get it fixed. I will put on my list as well in case you can't do it.
Thanks for reporting!

+1

I have fixed it at #13. I hope it helps 😉

Thanks @se, PR accepted.


Enhancement: BH behind proxy / tunnel

An option to force BH to use a proxy server (for a HTTP Tunnel) would be very nice. My ISP blocks some ports like 8332 and so I can't access many pools.
There are good free options like HTTP-Tunnel but I would need to force BH to connect through a local proxy server.
Ideas???

You can use btcproxy.net. It basically has bitHopper on its side and it is connected to over port 80.

Hi,
I'm not a python expert but from urllib docs[1] it looks like that urllib should honour the http_proxy environment variable: for my eyes it looks like bitHopper is using urllib but it also seems (from my own test) that this trick is not working on bitHopper.

Do you have any ideas?
Thanks
Bye
Piero
[1]http://docs.python.org/library/urllib.html

Um, it's not currently honoring that variable, I'll add it to the feature list. I'm getting paid for doing this in about  weeks so I'll start working on this a lot more.

For the moment I use Proxifier to force python.exe to use the local proxy tunnel.
Works pretty good. You can set port based rules to save tunnel bandwidth for not blocked ports too.
http://www.proxifier.com/


Added sequence field parsing

hi, I have added parsing of the field "update_seq" to StreamingViewResult. Can you merge this update and deploy new version? Or should I do it myself and work with the local repository

worth bearing in mind that this will break against CouchDB 2.0 / Cloudant / BigCouch where update_seq is non-numeric. To be compatible, treat update_seq as a json object (maybe something similar to https://github.com/helun/Ektorp/pull/240).


fix data length in btc_blufi_recv_handler

In function btc_blufi_recv_handler, using hdr->data_len as the data length receiving from mobile phone.
We send the following data from mobile phone:
111111111122222222223333333333444444444455555555556666666666777777777788888888889999999999000000000011111111112222222222333333333344444444445555555555666666666677777777778888888888999999999900000000001111111111222222222233333333334444444444555555555566666666667777777777888888888899999999990000000000
We will just receive:
11111111112222222222333333333344444444445555
The correct data length is 0x12C, however hdr->data_len is 0x2C as the type of it is uint8_t
So, in function btc_blufi_recv_handler, we can use parameter len to describe the length of received data.
As parameter len describes the whole length of struct blufi_hdr, we have to subtract the the bytes before data in struct blufi_hdr.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.rock.gu seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Updated to fix a broken link

Link to Local Deep Kernel Learning for Efficient Non-linear SVM Prediction obsolete.
Updated to
http://proceedings.mlr.press/v28/jose13.html

@brohrer : Thanks for your contribution to the Azure documentation! The author, @garyericson, has been notified to review your proposed change.

@PRMerger13  Gary is out on holiday. Can I sign off?
#sign-off

@j-martens: I'm sorry - only the author of this article, @garyericson, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

#sign-off

@j-martens: I'm sorry - only the author of this article, @garyericson, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


update comment to reflect change in function name to renderQuickActions

Minor error in commen

Thanks for this comment fix.


Add perf test framework for Hyperledger Composer

Signed-off-by: Nick Lincoln<EMAIL_ADDRESS>This pull request adds a test framework for Hyperledger Composer.
It enables the performance testing of a Fabric blockchain platform through the Composer abstractions.
The code within this PR is currently being used by the Hyperledger Composer team for performance testing.
The PR includes:

Readme on how to use the Composer plugin
Composer sample networks for testing
Example tests targeting the sample networks
Composer Utilities for setting up Fabric (uses the docker exec commands to join peers etc, instead of current API)
Composer main file
Docker files to use for creating various Fabric configurations using the Fabric 1.1.0

Apologies, I neglected to copy that one across when creating a separate branch to pull from, I have updated the PR to include the required documentation

Closing PR as Composer is planning to release with breaking changes in the APIs, thus breaking the deployment mechanisms used within the Caliper flow. Making edits to retain compatibility and will resubmit once Composer has released.


Genericize PipeBuf over Copy + Default + 'static types, add a maybe_space method for backpressure.

Sometimes the unit of data in the pipeline might not be bytes, but instead, e.g., u16s for a UTF-16 text-encoded-binary pipeline. This allows genericizing over the contents of the PipeBuf, but still retains u8 as the default.
This also adds a maybe_space method on PBufWr, which is intended to be used as a backpressure mechanism. If a pipeline stage is responsive to backpressure and gets a None from maybe_space, then it can pause processing, or attempt to process a smaller chunk instead.

Okay, thanks for the PR. A byte-stream is a fundamental thing in computing. For example UNIX read and write only deal with byte-streams, similarly data files, TCP streams, UNIX pipes, serial ports, and so on.  Even std::io::Write only deals with byte-streams. The Rust team could have parameterized it, but they didn't. So that is the world that PipeBuf is trying to fit into.
What is the motivation to make it work with any type? Do you have something you're coding that requires a non-u8 PipeBuf? Can you explain the problem you're trying to solve?

My main motivation is to make it work with u16 streams as well, to enable a Rust port of https://github.com/qntm/base32768; the underlying transformation there is from u8 bytes to u16 UTF-16 codepoints and back, so having a u16 version of PipeBuf would be very convenient (especially in a JS-WASM environment, where you can avoid string-encoding costs by passing around Uint16Arrays).
You can see the result of using these genericized PipeBufs in https://github.com/khoover/base32768-rs/tree/pipebuf.

Thanks. I'll study that example and think through it all.

I've been playing with this this morning. I think it's looking okay. I had a number of concerns, e.g. would it make it slower to build, or too complicated when viewing the docs, or too hard to explain or whatever. But I think it will be okay. It's not any worse than Vec. I have to take care as this isn't a toy project -- we're using it in production. Obviously I'm going to keep the focus on the byte-stream aspect in the docs, but I could add a separate section for using other types.
However the changes you had to make to the tests suggest that this is breaking in some cases. I tried rebuilding some of my other code against it and it works, but it must be able to infer the u8 in those cases. I tried cargo-semver-checks to verify, but it doesn't detect a semver violation, but then it doesn't claim to be complete either. It seems like the problem is due to not being able to put a default type for T in the impl sections. But this isn't supported by Rust.
I think there are two ways to solve it. Either have new, with_capacity and with_fixed_capacity return a PipeBuf<u8>, and add three extra functions for the generic versions. Or else just go to 0.3.0.
The new functions to check whether there is space make sense. In other words, you'd check that there is data to process and also space to write the result before doing an operation when working with fixed-size buffers. I will rearrange these new functions and clarify the docs around that.
Let me know your thoughts. I will probably accept this PR and then make my modifications on top. Or if you want to review my modifications, then I can add to this branch instead.

Accepting then making modifications on top works for me.

However the changes you had to make to the tests suggest that this is breaking in some cases.

It is, but those cases are a bit pathological; they're where you create the pipebuf, but then don't return it, pass it or a derived struct down to another function, or attempt to read/write. In those cases inference doesn't really have anything to work with, so you have to tell the language what the contained type is.

I'm now looking at docs, testing, release etc.

I'm going to change maybe_space to try_space, since that is the convention in std for the "possibly-failing" version of a call.
I'm going to 0.3.0 as it's a breaking change (strictly) and also it's a significant change.

Also, thanks for making the changes minimal and keeping the code lean. There was one panic check that you effectively moved from "cold" code to "inline" code (in PBufWr::space). I was trying to keep the inline code as small as possible for the common case, and keep everything else in a method that wouldn't be inlined. So I've fixed that.
I'll do some more testing now and then release it.

Doesn't expect internally use a cold function for the actual panic? Or do you mean you wanted to keep that branch and call out of the inlined code too?

Yes, the latter. I want to keep only the hot path in the inline code. So I rearranged things slightly. I know it's only a small thing, but it is not much effort to do it right.
The 0.3.0 release is out now. I'm going to update pipebuf_rustls soon to (hopefully) use the new unbuffered interface on Rustls 0.23, so I'll switch to the new pipebuf at the same time.
I don't know if anyone much out there is using pipebuf. There are no publically-released crates dependent upon it at least. But anyway, I probably should update all my pipebuf crates soon so that they are on the same version in case there is anyone out there using them. I guess now (with few users) is the time for breaking changes, if ever.

The original intention of the PipeBuf model is that backpressure will be handled by the glue code, not the component code. But I've realized that there is a case that will definitely need your new calls (especially free_space), and that's decompression. So anything like decompression will need to work this way. I've clarified the documentation.
If you have experience (good/bad) making pipebuf work for some scenario, maybe that can inform the recommendations in the documentation. I'm inviting people to open Discussion items. I need to implement more adaptors. Incidentally I got pipebuf_rustls working against Rustls unbuffered, but I found a limitation (bug?) in that Rustls feature.

I've been thinking about this overnight. I think I may move to the model that you seem to be using, i.e. component-based backpressure, because this is a simplification and takes care of several other cases at the same time. I've added a discussion item, and I will investigate further: https://github.com/uazu/pipebuf/discussions/2


Authorship

Remove explicit dependency on quilljs
Use submodule to include the code
Create a small gulpfile to compile and expose the color picker

Changes Unknown when pulling 3978b8773eaf47d2fdf5bbc311bbff6f1f21695f on authorship into ** on master**.


Specialized parsing error for apparent JSX tag in .ts file

Adds a specialized diagnostic for the case of a /> (slash and greater-than-sigh) after an identifier in a non-JSX-mode file.
JSX tags are not permitted in `.ts` files. Did you mean to change the file extension to `.tsx`?

I'm not at all confident in this PR's approach. It feels weird to work with a "previousNode" and then skip through tokens. Would love to know if there's a cleaner way of doing things, please!
This also doesn't capture every possible syntax variant that could appear to be from JSX syntax in a non-JSX file. I couldn't figure out any clean way to get more cases that came to mind.
Fixes #29375

A good fix might not exist. We really don't know something's syntactically invalid until way later; this code is legal (!):
declare const div: any, foo: any;
type div = {};
const a =
foo
/;

I'm not totally sure how I feel about threading the previous node down into the parser like this, honestly. I'm not sure of a better way, though, besides passing down a boolean that's true if it's a type assertion or something.

Sorry to not have a good update here - this is a tricky issue and I don't have the bandwidth to focus on it now. 😞
If someone else could push this forward, that'd be great.


Add usage instructions to README.

This isn't a good fit for 2 reasons:

livereload is not part of guard-livereload, and guard-livereload starts automatically, so you don't need to run livereload

Different browsers may have different options, so a Wiki page is better for this

Instead, I created a wiki page here
And here's the updated README Usage section
Feel free to update/improve the Wiki page (probably best to add links to existing page, e.g. the LiveReload ones with the same images you posted).


Remove unnecessary focus methods and directly bind to set_close_on_escape

Suggested by @AThousandShips for #86654, figured I would apply it everywhere else.

Thanks!


Better immediate link representation

The current sub-graph marking in the links-branch is not satisfactory as it is hard to visually locate all connected nodes. @jesperlauridsen suggested that the full graph be faded away and only the relevant sub-graph be shown, both nodes and edges.
This can be achieved by a SVG overlay. The "only" thing needed is information on the edges, which requires 2 extra sets of coordinates (the start- and end-points are already in the nodes list) as well as a color.
Packing that extra information into the linked.js-structure without blowing it up might not be possible. Instead a callback for JSON-blocks to the server could be used: The node-index is known from the existing (small) structure, so the blocks could simply be index 0-999, 1000-1999 and so forth.

A version with fading, but without callback has been created in the branch overlay. It seems to work on a desktop browser for 200K nodes, although is is a bit slow to update when clicking on nodes with many (500+) links. Not done yet, but getting there.

The overlay branch has been to master.


[0.5.x] AF-1079 : Empty 'Validation errors' popup in Decision/Business Central

https://issues.jboss.org/browse/AF-1079
These PRs change the service visibilities to protected for testing purposes. Not how I would like to do them, but the other option is to do even more refactoring and since this is an older branch, I don't think it is worth the risk.
https://github.com/AppFormer/uberfire-extensions/pull/324
https://github.com/dashbuilder/dashbuilder/pull/419
https://github.com/kiegroup/kie-wb-common/pull/1489
https://github.com/kiegroup/drools-wb/pull/825
https://github.com/kiegroup/jbpm-wb/pull/992

jenkins please retest this

jenkins, please retest this and make it pass

@mbiarnes Would you happen to remember if this the issues jenkins is picking up are randomly failing or not?

Jenkins test this please

locally tests are passing, so merging.

@mbiarnes thanks!


Issue-114 - Use Camel Case in identifiers

added CamelCase check

I've created another PR to master branch.


How will this differ with hyper::error::Error?

Since this is related to https://github.com/hyperium/hyper-util/pull/3, figured I'll take a look at this.
One thing I'm not too sure of is: how exactly does this Code differ from hyper::error::Kind?

It's not required to make progress on https://github.com/hyperium/hyper-util/pull/3, we can figure out the relationship afterwards. But to the question: the major difference is that Code is a public thing. The internal Kind is meant to be a cheaper way to assign specific error information, vs allocating a string that might not ever be printed. I expect Kind to probably hold more specific information than Code might expose.

I think I do right by responding to this issue instead of making an ew one, but if not sorry for hijacking and I'll make a new one none the less, @seanmonstar .
I think this is the kind of thing I need and wouldn't mind contributing one of these weeks, just would need a bit of guidance.
Currently the error reporting of Hyper is pretty limited as exposed by the current Error struct https://docs.rs/hyper/1.0.0-rc.4/hyper/struct.Error.html (seems unchanged from 0.14).
In general it is fine, but if you want to be able to handle specific kinds of errors you're often now forced to downcast_ref, perhaps even a chain of such checks, which becomes very painful very quickly. E.g. you might be looking for a specific kind of IO Error (which can happen in different ways), or some specific h2 issue (e.g. invalid frame size), etc etc.. Right now checking these kind of things so you can handle failures in a proper manner (so instead of just logging and accept failure, that you can actually correct your mistake on the fly, or retry, or w/e else.
For this I would argue against another opaque type.. I mean the type can be opaque in its implementation (so if you prefer a struct over an Enum, I'm fine with that), but the other approach is fine as well. Most important however is that any kind of error can just be accessed just as easily, while now some seem more exposed then others.
Is this the kind of use case you had in mind for this issue, or am I completely in the wrong issue?

I've updated the top issue comment, indicating a proposal is welcome and some values to consider.

@seanmonstar We've had some success with a revised set of "send" errors on the Fastly Compute platform that are roughly based on the proxy-status RFC, though of course extended with cases that cover non-proxy points of view.
The tentative success here has led my colleagues to use a similar structure in the error-code struct of the vendor-agnostic wasi-http spec.
The major gap here is that our work has so far focused on errors that arise during the initial exchange of request/response headers, rather than errors that can arise during subsequent reads of message contents.
I'm interested to take folks's temperature on this kind of approach. I know that basing things on an enum gets into the above-mentioned issues with pattern matching and compatibility, but my feeling is that stability concerns are mitigated by tying things (if unofficially and inexactly) to open standards. If it seems promising, I'll write up a more detailed proposal.


release opinion deploy on nexus repository

Hi,
I'm experiencing an issue with release-opinion plugin; every build is uploaded to release plugin in nexus repository, i would expect dev versions to be uploaded on snapshot repository and rc and milestones and finals to release repository;
is there a sample configuration i can use or something I'm missing ?
my actual config is:
   group = 'social.picnik.backend'

    plugins {
        id 'org.ajoberstar.grgit' version '1.7.0'
        id 'org.ajoberstar.git-publish' version '0.2.0'

    // if you want to use the opinionated config
        id 'org.ajoberstar.release-opinion' version '1.7.0'

    // if you want to configure it to your preferences
    //    id 'org.ajoberstar.release-base' version '1.7.0'
    }

    apply plugin: 'java'
    apply plugin: 'maven'

    //version = '3.31.3-SNAPSHOT'

    description = " --backend-services-- "

    sourceCompatibility = 1.8
    targetCompatibility = 1.8
    tasks.withType(JavaCompile) {
        options.encoding = 'UTF-8'
    }

    tasks.release.dependsOn 'build', 'uploadArchives'

    uploadArchives {
        repositories {
            mavenDeployer {
                repository(url: "${nexusUrl}/content/repositories/releases") {
                    authentication(userName: nexusUsername, password: nexusPassword)
                }
                snapshotRepository(url: "${nexusUrl}/content/repositories/snapshots") {
                    authentication(userName: nexusUsername, password: nexusPassword)
                }
            }
        }
    }

    wrapper {
        gradleVersion = '3.4'
    }

when i run the command

gradle release

the plugin infer the version correctly as 3.31.3-dev.22.uncommitted+c6e4922
but then i find the jar on nexus in release repository (even if nexus is giving 400 response code)
do you have any suggestion ?

I think snapshot repos are only for literal -SNAPSHOT versions.

Feel free to reopen if this did not answer your question.

thanks it does not solves my problem but it does answer, I could solve the problem using nebula-release plugin
thanks for your time


0.18.0 link to abc

Could you move the "Compatible Implementations" to after the Spec links?
Also, I think it would be better if "Compatible Implementations" were not a link, just "Bitcoin ABC 0.18.0"


Evaluate Measure takes longer than Care Gaps

Calling $care-gaps is faster than calling $evaluate-measure even though $care-gaps uses evaluateMeasure().
$care-gaps immediately followed by $evaluate-measure:
Is:
$care-gaps: 1683ms

$evaluate-measure: 3.74s

Should be:
Since $care-gaps is being called first, the expectation is that any caching is warm for the subsequent $evaluate-measure call.  Given this and the fact $care-gaps literally calls evaluateMeasure (https://github.com/DBCG/cqf-ruler/blob/a80853dcc2fda4b601c016bca70622ccbff5d1df/plugin/cr/src/main/java/org/opencds/cqf/ruler/cr/r4/provider/CareGapsProvider.java#L320) the expectation is that the $care-gaps time should always be $evaluate-measure plus additional $care-gaps processing time, i.e., $care-gaps > $evaluate-measure.
Repro:
https://cloud.alphora.com/sandbox/r4/gic/fhir/Measure/$care-gaps?periodStart=2020-01-01&periodEnd=2020-12-31&status=open-gap&status=closed-gap&subject=Patient/numer-EXM130&measureId=ColorectalCancerScreeningsFHIR
https://cloud.alphora.com/sandbox/r4/gic/fhir/Measure/ColorectalCancerScreeningsFHIR/$evaluate-measure?patient=numer-EXM130&periodStart=2020-01-01&periodEnd=2020-12-31

It's kinda a WAG, but I wonder if this could be related to instance vs type invocation.
Unfortunately, I'm unable to test due to both operations under consideration have instance vs type issues atm, ref https://github.com/DBCG/cqf-ruler/issues/442.

Resolved by #524


line breaks get deleted when calling prism.highlightElement(code)

I set up my HTML using the following snippet:

When I call prism.highlightElement(code); from the following TypeScript snippet:
import * as prism from "prismjs";

const code: HTMLElement = document.getElementsByTagName("code")[0];

prism.highlightElement(code);

... all line breaks in the  element get deleted when calling prism.highlightElement(code).

The result is that all code is getting displayed in a single line then:
before

after

I believe this is not supposed to happen?

I assume that you wrote the highlighted code yourself (because of contenteditable="true").
The problem here is that Prism uses a literal string line break (so \n or \r\n).
But that is not what the browser will insert when you press Enter.
The best solution in that is to use keyboard event to handle Enter yourself.
A working example of this dabblet. The script responsible for this behavior can be found here.

I believe this is not supposed to happen?

If my assumption is correct, this is supposed to happen.
Otherwise, please provide the full example producing the bug.

Nope. The  element lies within a
 element, so \r\n and \n are both interpreted as newlines by the browser. I debugged my session and I can confirm that \n characters are being inserted.
I will upload a sample in short time.

Is there a public CDN available for Prism I can link to in my sample page?

https://cdnjs.com/libraries/prism will work I guess.

Prism will also add the language-js CSS class to the
 element.
Could it be that this changes the white-space property to something which is not pre, pre-line, or pre-wrap?

I will upload a sample in short time.

Thank you.

Nope. Checked.

I created a test page now (the following ZIP file contains the HTML file):
PrismJS Test.zip
You were right: The browser adds
 tags instead of using \n.
So I needed to replace every occurrence of
 with \n:
let code = document.getElementsByTagName("code")[0];

code.innerHTML = code.innerHTML.replace(/[<]br[/]?[>]/gi,"\n");

Prism.highlightElement(code);

It was the reason you suggested. Thanks!

Though, AFAICS, the reason is based on the fact that prism.js uses var code = element.textContent;. If Prism would use element.innerText instead, the
 would be converted to \n by the browser itself, automatically:

Wouldn't it make sense to update the code line in prism.js accordingly?

innerText has a few other properties which make it less useful for Prism.
It would also change the current behavior of Prism, so for some people out there, this might be a breaking change.
Also, you can use hooks to make Prism use innerText.
Prism.hooks.add('before-sanity-check', function (env) {
    env.code = env.element.innerText;
});

From the description you mentioned I can only read the inteded behaviour and a performance issue.
In contrast to the documents' statement, innerText has become a standard meanwhile:

From the description you mentioned I can only read the inteded behaviour and a performance issue.

Performance aside: Is breaking change not enough reason?
Also, I don't think that it's a good idea for the text Prism highlights to change depending on whether the element is being rendered or not.
What do you think @mAAdhaTTah ?

Please pardon me for being ignorant. Would you mind elaborating on the issues you see?
I'm just trying to being constructive.
I tested three different scenarios now:

, as suggested by Prism documentation.

From my perspective I don't see any negative consequences when applying #1766. On the contrary.

 is supposed to retain newline characters, so it doesn't make sense to remove them (in the original code, see merge request).

 is supposed to retain newline characters

It does but only characters.

From my perspective I don't see any negative consequences

My main problem is that textContent and innerText behave slightly differently. Most users of Prism probably wouldn't even notice the change because the  element Prism highlights isn't supposed to contain markup*.
(* except when it does)

Would you mind elaborating on the issues you see?

innerText is intended to return the text the user gets when selecting and copying the visible text of an element.
So it makes sense that this is what you want. You're writing a text editor, so it makes sense that Prism should highlight what the user sees.
My problem is that this not how Prism behaves now. Prism doesn't highlight the text the user sees, but the text which is there (sounds dumb, I know...).
As an example: innerText doesn't return the text of elements which have display: none, because they are not visible. Now, how should Prism behave?
I say display: none shouldn't matter because markup is stripped.
Btw.: Same problem for display: block where extra \ns will be inserted around the block.
Now, the next problem: innerText is only really defined for elements which are visible. As a consequence, its behavior changes depending on whether the element, from which you want the innerText, is visible.
Example: Let's say we highlight a code element. With innerText we might get different results depending on whether the element is visible (right now) or not. (Happy debugging...)
(Well and then again: Most users don't care, so why not do them a favor and use what's faster.)
Summary:
My main issue is that the behavior of Prism changes. So we risk breaking the code of a lot of Prism users.
Also, there is this more general question of how Prism should behave. Should it highlight the visible text or all text?

Again: I can see why you want to use innerText in your specific use case but you don't need to change all of  Prism for that. You can use the features Prism already provides to implement this.

I'm not sure whether these edge cases really matter. However, of course, I refrain from my pull request.
Just to finish the discussion, regardless of the result:

I wouldn't expect nodes deliberately designated to be display: none to still appear. I personally would consider this behaviour unexpected, or even not desired, if I happened to stumble over it.

I would expect nodes deliberately designated to be display: block to be displayed with line-breaks. Otherwise I wouldn't expect the web page designer to have applied that attribute to those nodes in the first place.

A few minutes ago I applied display: none to the  element. The result: innerText was the same as textContent: Both omit child elements when the element is hidden.
I comprehend that old (pre-standard) IE implementations behave differently. For these edge cases element.innerText || element.textContent should have sufficed.

I would have considered the innerText behaviour - including its line-break behaviour - much more what I'd expect from the converted result as the textContent behaviour.

The hook appears to be incorrect. The correct hook name is: before-highlight
Prism.hooks.add('before-highlight', function (env)
{
  env.code = env.element.innerText;
});

The hook appears to be incorrect. The correct hook name is: before-highlight

I specifically wanted before-sanity-check because it is executed before (almost) all other hooks and (more importantely) before the checks of highlightElement.

This works too:
Prism.hooks.add('before-sanity-check', function (env)
{
  env.element.innerHTML = env.element.innerHTML.replace(/
/g, '\n');
  env.code = env.element.textContent;
});

This has been closed for a while, but I am having a problem as well with straight code like this:
import Prism from 'prismjs';
let thecode = "int main()\n{\n  3+4;\n}";
html = Prism.highlight(thecode, Prism.languages.clike);

The resulting html has no line break despite the 3 \n in the source code.
int main()
{
  3+4;
}

What am I doing wrong?

The resulting html has no line break despite the 3 \n in the source code.

Prism's HTML output is intended for pre elements which use white-space: pre by default. Set this property for the element you're using for displaying code, and everything should work fine.

The resulting html has no line break despite the 3 \n in the source code.

Prism's HTML output is intended for pre elements which use white-space: pre by default. Set this property for the element you're using for displaying code, and everything should work fine.

I am not using an element and do not wish to use an element. I have markdown text downloaded from a server and want to use svelte to put the HTML in an element afterwards using svelte's {@html html}. Can't I call the highlight function so that it does treat it as if it got the text from a pre element? I've only looked over the code for hilightElement and it does get the text in what seems should result in the same code I am passing to highlight, but I am not seeing yet how its call of highlight is differently from what I do.
I am sure you can help me with that 👍

The hook appears to be incorrect. The correct hook name is: before-highlight
Prism.hooks.add('before-highlight', function (env)
{
  env.code = env.element.innerText;
});

I had this issue trying to add Prism.js to Anki card template and I fixed it by adding this hook to Prism.js code. Thank you!


Apache-affiliated Twitter screen names: A dataset

http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=6624043

This Paper's Data
This paper is about one specific dataset (SQL database) linking the names of people involved with the Apache project to their Twitter accounts. The data was contributed to a repo called FLOSSmole, which we should consider either linking to or grabbing data from.
FLOSSmole
FLOSSmole is a "Collaborative collection and analysis of free/libre/open source project data". They have BOATLOADS of datasets of all sorts of things. Perhaps there should be a separate issue of sharing with, linking to, or otherwise collaborating with them.
FLOSSmole homepage: http://flossmole.org/
FLOSSmole data: http://flossdata.syr.edu/data/


xDomain for Multichart does not work

I'm trying to force the x-axis to hold up to 24 hours but it current stops at the latest hour which is 10 am in this example. Is there a way to extend it?

You can't force xAxis range in a multiChart although you can do with other types of chart.
I faced the same issue and as a workaround, I had to add a 'fake' point with a null value at the beginning of each serie and do the same at the end with respectively the min value and the max value.


Has the auto-generated firewall rule been renamed from AllowAllWindowsAzureIps to Azure_service_allow_all?

When enabling the Allow Azure Services and resources to access this server to ON in the Firewalls and virtual networks settings. setting, we are noticing the auto-generated firewall rule has been renamed from AllowAllWindowsAzureIps to Azure_service_allow_all.  If this is expected, documentation should be updated.
Old server that was recently updated has both rules:

New server that was provisioned only has the Azure_service_allow_all rule:

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

ID: 770df8c3-4e61-3aee-b346-ed3e244b8b4f
Version Independent ID: c4d19eb8-e945-6227-c15f-7a3b01935aac
Content: IP firewall rules - Azure SQL Database and Azure Synapse Analytics
Content Source: azure-sql/database/firewall-configure.md
Service: sql-database
Sub-service: security
GitHub Login: @VanMSFT
Microsoft Alias: vanto

Hi, @sivetic Thank you for reaching out. We will look into it and update as appropriate.

Hi, @sivetic Thank you for reaching out. We will look into it and update as appropriate.

Oh sorry my fault, I just realized the old firewall rule comes from our side!  I'll close the ticket, it is not relevant or caused by Microsoft.


Athena support

POC athena support for elementary. Limited to Athena 3 and iceberg tables for incremental elementary tables. Testing with dbt-core 1.5.0, dbt-athena-community 1.5.0 and lalalilo/athena_utils 0.3.0.
Working features based on ad-hoc tests:

elementary dbt artifcat tables (dbt_*, elementary_test_results)
dbt and elementary tests (volume_anomalies, column_anomalies, dimension_anomalies)
one page report (edr report)
alert tables and sending slack alerts (edr monitor)

@artem-garmash great job
Few notes:

we can add what we can in https://github.com/dbt-athena/dbt-athena - happy to help you and review your PRs/
lalalilo/athena_utils was moved to https://github.com/dbt-athena/athena-utils consider to use that instead

I left some minor comments, overall looks great 💯


Add Release Asset for SHA256 of DesktopAppInstaller_Dependencies.zip

Description of the new feature / enhancement
With the new file DesktopAppInstaller_Dependencies.zip being included in the release, there should be a way to verify the hash matches what is expected. This is required for SandboxTest.ps1 over at winget-pkgs to function without major modifications
Proposed technical implementation details
Add DesktopAppInstaller_Dependencies.txt to the release as a text file containing the SHA256 of the zip file
Alternatively, add the hashes to the .json file

https://github.com/microsoft/winget-cli/releases/download/v1.9.25180/DesktopAppInstaller_Dependencies.txt

https://github.com/microsoft/winget-cli/releases/download/v1.9.25180/DesktopAppInstaller_Dependencies.txt

Will this continue to be part of the releases moving forward?

Yes, we're going to update the pipelines so the dependencies get included in the artifacts built so we can easily add them to the releases. @ryfu-msft to confirm here.


cmd/go: go mod tidy and go mod download don't agree on same go.sum file.

What version of Go are you using (go version)?

go version go1.16 darwin/amd64

Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
go env Output
$ ~/Downloads/go\ 2/bin/go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/caguilar/Library/Caches/go-build"
GOENV="/Users/caguilar/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/caguilar/go/pkg/mod"
GONOPROXY="slack-github.com"
GONOSUMDB="slack-github.com"
GOOS="darwin"
GOPATH="/Users/caguilar/go"
GOPRIVATE="slack-github.com"
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/Users/caguilar/Downloads/go 2"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/Users/caguilar/Downloads/go 2/pkg/tool/darwin_amd64"
GOVCS=""
GOVERSION="go1.16"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/caguilar/src/goslackgo/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/sd/dhdfq5qx471__68g8fl9v_jh0000gp/T/go-build540412494=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?

go mod tidy
go mod download

What did you expect to see?
I was expecting go.sum to not change.
What did you see instead?
go.sum changed. This causes issues in our CI since we don't expect source files to be arbitrarily changed during CI.

This is a duplicate of #43994.


A double tilde accent

Description
There is neither an accent function nor a symbol for a double tilde (except approx).
tilde(tilde(C)) looks awful:

limits(C)^approx also really isn't a good alternative.
Please either add a separate accent function for it or make tilde(tilde(C)) prettier.
Use Case
Some specific math applications.

Please either add a separate accent function for it or make tilde(tilde(C)) prettier.

There is no double tilde accent in unicode, so the solution should be the latter.
Stacking multiple accents in math just doesn't work very well at all right now in general. I thought there was an issue about it, but I couldn't find one.

This was fixed by #3059 I think. From some quick testing on main, stacked accents are working just fine now.


Skip specific imports

Is it possible to skip certain imports?
For example I have the bootstrap lib locally installed and imported to get auto-completion to work, but in production the actual file is served from CDN. Is there any way to exclude the complete bootstrap lib, but keep my custom code compiling?

I was looking for similar issue, found a solution.
Extend compiler class, override function findImport(). If parameter matches file you want to skip, return null (then you get to keep import statement in output) or replace with dummy file (then import will not be in output).


GSLUX-559: Display external metadata

JIRA issue
https://jira.camptocamp.com/browse/GSLUX-559
Description
PR adds the capability to add WMTS layers to the remote layers layertree and to display their metadata.
The same should already be possible for WMS layers.
To-dos:

[x] some more refactoring
[x] adding some tests

Note: It does not address displaying the WMTS on the map.

Thanks a lot for the detailed review @AlitaBernachot! Don't hesitate to have another look at my latest commit, as it includes quite some changes :-)


Extend Application to allow catching route exceptions - lack of Factory

According to Extend Application to allow catching route exceptions #120 there's a lack of Factory for ZF\Apigility\Application.
Adding \ZF\Apigility\Application::init($appConfig)->run(); to index.php changes nothing, because when bootstrapping application there's a call to return $serviceManager->get('Application')->bootstrap($listeners);, but $serviceManager->get('Application') returns original Zend\Mvc\Application
To be done:

create Factory which returns ZF\Apigility\Application
add it to:

'service_manager' => [
        'factories'  => [
            'Application' => \ZF\Apigility\ApplicationFactory::class,

Or is there other existing or possible solution for that @weierophinney  ?

@weierophinney ping ;)

This repository has been closed and moved to laminas-api-tools/api-tools; a new issue has been opened at https://github.com/laminas-api-tools/api-tools/issues/28.


ArrayField with different delimiter

I'm using ArrayField that contains some text, which can have a comma in it. Import/export is a problem, because it splits a field if it contains a comma. Can we add an option for custom delimiters?

One way to do this now is to subclass the CSV class and overwrite the delimiter, for instance to use ; instead of ,:
from import_export.formats import base_formats

class SCSV(base_formats.CSV):
    """ CSV with Semicolons instead of Commas. """

    def get_title(self):
        return "scsv"

    def create_dataset(self, in_stream, **kwargs):

        kwargs['delimiter'] = ';'

        return super().create_dataset(in_stream, **kwargs)

Oh!  By "ArrayList" do you mean the Django model field type ArrayField?
And are you exporting to JSON again, is that it?

Sorry, yes. I export to JSON and import from JSON on another server.

mgrdcm, can you explain where put the override method or make a example to how use it please?

Hi, I also would like to import a list to a field from a JSON file to a postgres ArrayField.
For example when importing
[
  {
    "keywords": ["keyword1", "keyword2"]
  }
]

I get
Error in line: 1, 'list' object has no attribute 'split'
If I store the keywords as a comma seperated string "keywords": "keyword1,keyword2" they get imported correctly. Is this not possible I already have the list?

Is this an import JSON file specific issue? Or can this be generalized to csv, xls, etc.?


Gym is unable to find provisioning profiles when invoked from a Fastlane lane

If I run
gym --scheme "Scheme Name"
directly from the terminal, my app builds fine.
However, if I run either
gym(scheme: "Scheme Name")
or
gym(scheme: "#{gym_build_scheme}")
from within a lane in my Fastfile, I get an error explaining that no non-expired provisioning files were found.
Here are my two lanes.  When invoking Fastlane, I do so by using fastlane ios beta_mo

This is a particularly frustrating issue, as I don't understand what gym could be doing differently based upon whether I invoke gym directly from the terminal or if gym is invoked from a lane.  Below is the error I get when invoking gym with a scheme from the lane.

However, when I use the terminal command gym --scheme "Scheme Name" (my scheme name is "Motion Organized"), it builds successfully without any provisioning issues.
The gym summary printouts are identical whether I invoke directly from terminal or through the lane.
Directly from Terminal

Invoking gym from a lane

For reference and for SEO, here is the error:
Code Sign error: No provisioning profiles found: No non–expired provisioning profiles were found.
Does anybody have any ideas as to what I might be able to do to work around this issue?
Please let me know if you need any additional information.
Thanks!

Can you try adding calls to cert and sigh before gym?

Thanks for your prompt response, @vpolouchkine.
Per your request, I added (to my lane) calls to cert and sigh before gym, and I received the same error.
I think a telling sign that this may be a bug is that I get different results when invoking gym from different places.  gym fails to find provisioning profiles when run from a lane but succeeds when running directly from terminal using identical parameters.

@vpolouchkine: In my previous message, I was a bit unclear when I said that gym

[gym] succeeds when running directly from terminal.

What I meant is that the build succeeds when running gym from terminal and fails after a few seconds when running from a lane.  When running gym from either, however, it ultimately ends up with this error message.  Please note that I have replaced the app name with <AppName> and my project name with <ProjectName>, due to an NDA to which I am bound.

[01:28:21]: ▸ Touching .app
[01:28:21]: ▸ Signing /Users/Alex/Library/Developer/Xcode/DerivedData/-fwoucivldnnsgoawkbrrzykriffp/Build/Intermediates/ArchiveIntermediates//InstallationBuildProductsLocation/Applications/.app
[01:28:22]: ▸ Touching .app.dSYM
[01:28:22]: ▸ Archive Succeeded
xattr: No such file: /Users/Alex/Library/Developer/Xcode/Archives/2016-05-24/ 2016-05-24 01.27.03.xcarchive
[01:28:22]: The generated archive is invalid, this can have various reasons:
[01:28:22]: Usually it's caused by the Skip Install option in Xcode, set it to NO
[01:28:22]: For more information visit https://developer.apple.com/library/ios/technotes/tn2215/_index.html
[01:28:22]: Also, make sure to have a valid code signing identity and provisioning profile installed
[01:28:22]: Follow this guide to setup code signing https://github.com/fastlane/fastlane/blob/master/fastlane/docs/CodeSigning.md
[01:28:22]: If your intention was only to export an ipa be sure to provide a valid archive at the archive path.
[!] Archive invalid

I have run both cert and sigh and have still gotten this error message every time.  Archiving from Xcode works just fine, so I'm not sure why gym is having so much difficulty finding the right profile to use.
Any other debug steps or tips you may have would be greatly appreciated.  Thanks, again!

Oh, snap.  The archives aren't even showing in Xcode's Organizer anymore.  Please standby on this issue until I confirm that I didn't derp something on my end.

It looks like there hasn’t been any recent activity on this issue, so I’m closing it. If this is still a problem, feel free to re-open and I’d be happy to help :+1: