text:
Cannot set control setpoint to 0

Currently using version 0.8.3. Previously I was able to send this request:
POST http://otgw.local/api/v1/otgw/command/CS=0
this would turn off boiler if nothing is using it.
Now it no longer works, I can send :
POST http://otgw.local/api/v1/otgw/command/CS=1
and it updates fine, but 0 is ignored.

There was a bug in pre-0.8.5 that sometimes causes messages to stay in the queue for a long time.
Cloud you try the lars test firmware and validate if that solves your issue.
Thanks
Robert

Just updated to 0.8.5+dc3dc14. It worked once, but then stopped working after that. Also tried sending CS=-1`  but does not work.

It sounds like a bug. So I will try to replicate it. Could you share some debug logs from your problem?

I just tested the latest firmware, and the REST API just works fine.
Not sure what problem you are experiencing, so could you please share some debug logs.
Read this: https://github.com/rvdbreemen/OTGW-firmware/wiki/How-to-debug-the-OTGW-firmware
If you want some realtime interaction you can share the Discord community. And chat about your issue with me and others. Just go here: https://discord.gg/zjW3ju7vGQ

So did you read this part of the OTGW commands?
"CS=temperature
Control Setpoint - Manipulate the control setpoint being sent to the boiler. Set to 0 to pass along the value specified by the thermostat. To stop the boiler heating the house, set the control setpoint to some low value and clear the CH enable bit using the CH command.
Warning: manipulating these values may severely impact the control algorithm of the thermostat, which may cause it to start heating much too early or too aggressively when it is actually in control.
Example: CS=45.8, CS=0
C2=temperature
Control Setpoint for 2nd CH circuit - Manipulate the control setpoint being sent to the boiler for the second CH circuit. Set to 0 to pass along the value specified by the thermostat.
Example: C2=45.8, C2=0
CH=state
Central Heating - When using external control of the control setpoint (via a CS command with a value other than 0), the gateway sends a CH enable bit in MsgID 0 that is controlled using the CH command. Initially, this bit is set to 1. When external control of the control setpoint is disabled (CS=0), the CH enable bit is controlled by the thermos"
So what are the commands you are sending to the OTGW using the REST command interface?

@katilius I noticed this:
"To stop the boiler heating the house, set the control setpoint to some low value and clear the CH enable bit using the CH command."
If I understand correctly, then you need to clear the CH bit and you need to set the CS to a low value....
Meaning to turn off your boiler, you send two commands back to back:
CS=0
CH=0
That should turn off the boiler then.
Could you try that?

Yes, I missed the part about CH. Will try it now. Initially I was experimenting with all commands that my boiler supported and looked what could stop the boiler and using just CS worked up until I upgraded to version 0.8.

@katilius did you upgrade you PIC to a newer version by any chance? As the 8266 firmware basically forward the commands

I did, but I can double check. Is version somwehere available to check ?

Goto the webUI, click Device Info. And check the "OTGW PIC Firmware Version". The current version I run is version 4.3 btw...

I have tried sending CH as well, but now I am in different state, I cannot reenable heating. I send this request:
http://otgw.local/api/v1/otgw/command/CH=1
But it does not turn back on.
Here is the log after sending command:
[07:29:58][  14408| 13640] addOTWGcmdto( 991): CmdQueue: Adding cmd end of queue, slot [0]
[07:29:58][  13064| 12344] addOTWGcmdto( 994): CmdQueue: Insert queue in slot[0]:cmd[CH=1] (4)
[07:29:58][  13064| 12344] addOTWGcmdto(1012): CmdQueue: Next free queue slot: [1]
[07:29:58][  12680| 11696] processOTGW (1163): Boiler           [B40193966] [READ_ACK        ]  [Tboiler                       ]        Tboiler                               = 57.40 °C
[07:29:59][  14248| 13096] handleOTGWqu(1024): CmdQueue: Checking due in queue slot[0]:[23727393]=>[23727776]
[07:29:59][  12904| 11800] processOTGW (1172): Request Boiler   [R80010000] [READ_DATA       ]  [TSet                          ]                hb[  0] lb[  0]
[07:29:59][  12904| 11800] processOTGW (1163): Boiler           [B70010000] [UNKNOWN_DATA_ID ]  [TSet                          ]                hb[  0] lb[  0]
[07:30:00][  14248| 13096] handleOTGWqu(1024): CmdQueue: Checking due in queue slot[0]:[23728393]=>[23727776]
[07:30:00][  12904| 11800] handleOTGWqu(1026): CmdQueue: Queue slot [0] due
[07:30:00][  12904| 11800] sendOTGW    (1108): Sending to Serial [CH=1] (4)
[07:30:00][  11560| 10504] checkOTGWcmd(1064): CmdQueue: Checking if command is in in queue [CH: 1] (5)
[07:30:00][  11560| 10504] checkOTGWcmd(1075): CmdQueue: Checking [CH]==>[0]:[CH=1] from queue
[07:30:00][  11560| 10504] checkOTGWcmd(1078): CmdQueue: Found cmd [CH]==>[0]:[CH=1]
[07:30:00][  11560| 10504] checkOTGWcmd(1081): CmdQueue: Found value [ 1]==>[0]:[CH=1]
[07:30:00][  10888|  9856] checkOTGWcmd(1082): CmdQueue: Remove from queue [0]:[CH=1] from queue
[07:30:00][  10888|  9856] checkOTGWcmd(1084): CmdQueue: Moving [1] => [0]
[07:30:00][  11920| 11400] processOTGW (1172): Request Boiler   [R00740000] [READ_DATA       ]  [BurnerStarts                  ]                hb[  0] lb[  0]
[07:30:00][  12904| 11800] processOTGW (1163): Boiler           [B407477E5] [READ_ACK        ]  [BurnerStarts                  ]        BurnerStarts                          = 30693
[07:30:01][  10664|  9936] processOTGW (1172): Request Boiler   [R00110000] [READ_DATA       ]  [RelModLevel                   ]                hb[  0] lb[  0]

@katilius it in the end depends on your thermostat and boiler, not the firmware of the NodeMCU and the PIC. So you have to experiment with the settings, you have to probably do a combination of CH and CS to turn off and turn on your boiler.
Just come to discord channel to discuss with others, or, if you are more comfortable with a forum you could go here: https://www.domoticaforum.eu/viewforum.php?f=75

Closing this issue, because it's not a problem with the firmware it seems, but more on how to control your boiler.

authors: katilius rvdbreemen

repo: rvdbreemen/OTGW-firmware


text:
Update lfe_doc's guard handling in 1.1.1

Currently (and for 1.1):
%% function_patterns(LambdaForm) -> {Arity,Patterns}.
%% macro_patterns(LambdaForm)    -> Patterns.
%%  Given a {match-,}lambda form, attempt to return its patterns (or
%%  arglist).  N.B. A guard is appended to its pattern and Patterns is
%%  a list of lists.  A macro definition must have two args, the pattern
%%  and the environment.

-spec function_patterns(LambdaForm) -> {Arity,Patterns} when
      LambdaForm :: nonempty_list(),
      Arity      :: non_neg_integer(),
      Patterns   :: nonempty_list(pattern()).
-spec macro_patterns(LambdaForm) -> Patterns when
      LambdaForm :: nonempty_list(),
      Patterns   :: nonempty_list(pattern()).

For 1.1.1:

I think I would prefer to separate them, sort of {Patterns,GuardTests}.

%% Something like:
-spec function_patterns(LambdaForm) -> {Arity,PatternGuards} when
      LambdaForm    :: nonempty_list(),
      Arity         :: non_neg_integer(),
      PatternGuards :: nonempty_list({Patterns,GuardTests}),
      Patterns      :: nonempty_list(pattern()),
      GuardTests    :: nonempty_list(guard()).   %Assuming guard/0 is defined.
-spec macro_patterns(LambdaForm) -> PatternGuards
      LambdaForm    :: nonempty_list(),
      PatternGuards :: nonempty_list({Patterns,GuardTests}),
      Patterns      :: nonempty_list(pattern()),
      GuardTests    :: nonempty_list(guard()).   %Assuming guard/0 is defined.

Related: #220

Yes, to separating the patterns and guards in that fashion. However the API has changed so it mightn't be those functions where you see it.

source: gharchive/issue

authors: rvirding yurrriq

repo: rvirding/lfe

license_type: permissive

license_source: bigquery


text:
make compile fails in pristine clone of repo

On the develop branch, a make compile in a pristine clone results in:
12:33 $ make
escript get_comp_opts.escript
make  erlc-lfec
make[1]: Entering directory '/home/mjl/work/castlerock/src/test/lfe'
erlc -I include -o ebin -DERLANG_VERSION=\"19.3\" -DHAS_MAPS=true -DHAS_FULL_KEYS=true -DNEW_REC_CORE=true -DNEW_RAND=true -W1 src/lfe_shell.erl
erlc -I include -o ebin -DERLANG_VERSION=\"19.3\" -DHAS_MAPS=true -DHAS_FULL_KEYS=true -DNEW_REC_CORE=true -DNEW_RAND=true -W1 src/lfe_codegen.erl
erlc -I include -o ebin -DERLANG_VERSION=\"19.3\" -DHAS_MAPS=true -DHAS_FULL_KEYS=true -DNEW_REC_CORE=true -DNEW_RAND=true -W1 src/lfe_io_pretty.erl
erlc -I include -o ebin -DERLANG_VERSION=\"19.3\" -DHAS_MAPS=true -DHAS_FULL_KEYS=true -DNEW_REC_CORE=true -DNEW_RAND=true -W1 src/lfe_macro.erl
erlc -I include -o ebin -DERLANG_VERSION=\"19.3\" -DHAS_MAPS=true -DHAS_FULL_KEYS=true -DNEW_REC_CORE=true -DNEW_RAND=true -W1 src/lfe_io_write.erl
erlc -I include -o ebin -DERLANG_VERSION=\"19.3\" -DHAS_MAPS=true -DHAS_FULL_KEYS=true -DNEW_REC_CORE=true -DNEW_RAND=true -W1 src/lfe_lint.erl
src/lfe_lint.erl:1477: Warning: function add_errors/3 is unused
erlc -I include -o ebin -DERLANG_VERSION=\"19.3\" -DHAS_MAPS=true -DHAS_FULL_KEYS=true -DNEW_REC_CORE=true -DNEW_RAND=true -W1 src/lfe_doc.erl
erlc -I include -o ebin -DERLANG_VERSION=\"19.3\" -DHAS_MAPS=true -DHAS_FULL_KEYS=true -DNEW_REC_CORE=true -DNEW_RAND=true -W1 src/lfe_io_format.erl
erlc -I include -o ebin -DERLANG_VERSION=\"19.3\" -DHAS_MAPS=true -DHAS_FULL_KEYS=true -DNEW_REC_CORE=true -DNEW_RAND=true -W1 src/lfe_comp.erl
erlc -I include -o ebin -DERLANG_VERSION=\"19.3\" -DHAS_MAPS=true -DHAS_FULL_KEYS=true -DNEW_REC_CORE=true -DNEW_RAND=true -W1 src/lfe_ms.erl
erlc -I include -o ebin -DERLANG_VERSION=\"19.3\" -DHAS_MAPS=true -DHAS_FULL_KEYS=true -DNEW_REC_CORE=true -DNEW_RAND=true -W1 src/lfe_env.erl
erlc -I include -o ebin -DERLANG_VERSION=\"19.3\" -DHAS_MAPS=true -DHAS_FULL_KEYS=true -DNEW_REC_CORE=true -DNEW_RAND=true -W1 src/lfe_macro_record.erl
erlc -I include -o ebin -DERLANG_VERSION=\"19.3\" -DHAS_MAPS=true -DHAS_FULL_KEYS=true -DNEW_REC_CORE=true -DNEW_RAND=true -W1 src/lfe_internal.erl
erlc -I include -o ebin -DERLANG_VERSION=\"19.3\" -DHAS_MAPS=true -DHAS_FULL_KEYS=true -DNEW_REC_CORE=true -DNEW_RAND=true -W1 src/lfe_pmod.erl
erlc -I include -o ebin -DERLANG_VERSION=\"19.3\" -DHAS_MAPS=true -DHAS_FULL_KEYS=true -DNEW_REC_CORE=true -DNEW_RAND=true -W1 src/lfe_macro_include.erl
src/lfe_macro_include.erl:306: Warning: variable 'Line' is unused
erlc -I include -o ebin -DERLANG_VERSION=\"19.3\" -DHAS_MAPS=true -DHAS_FULL_KEYS=true -DNEW_REC_CORE=true -DNEW_RAND=true -W1 src/lfe_edlin_expand.erl
erlc -I include -o ebin -DERLANG_VERSION=\"19.3\" -DHAS_MAPS=true -DHAS_FULL_KEYS=true -DNEW_REC_CORE=true -DNEW_RAND=true -W1 src/lfescript.erl
erlc -I include -o ebin -DERLANG_VERSION=\"19.3\" -DHAS_MAPS=true -DHAS_FULL_KEYS=true -DNEW_REC_CORE=true -DNEW_RAND=true -W1 src/lfe_parse.erl
erlc -I include -o ebin -DERLANG_VERSION=\"19.3\" -DHAS_MAPS=true -DHAS_FULL_KEYS=true -DNEW_REC_CORE=true -DNEW_RAND=true -W1 src/lfe_bits.erl
erlc -I include -o ebin -DERLANG_VERSION=\"19.3\" -DHAS_MAPS=true -DHAS_FULL_KEYS=true -DNEW_REC_CORE=true -DNEW_RAND=true -W1 src/lfe_lib.erl
erlc -I include -o ebin -DERLANG_VERSION=\"19.3\" -DHAS_MAPS=true -DHAS_FULL_KEYS=true -DNEW_REC_CORE=true -DNEW_RAND=true -W1 src/lfe_macro_export.erl
erlc -I include -o ebin -DERLANG_VERSION=\"19.3\" -DHAS_MAPS=true -DHAS_FULL_KEYS=true -DNEW_REC_CORE=true -DNEW_RAND=true -W1 src/lfe_gen.erl
erlc -I include -o ebin -DERLANG_VERSION=\"19.3\" -DHAS_MAPS=true -DHAS_FULL_KEYS=true -DNEW_REC_CORE=true -DNEW_RAND=true -W1 src/lfe_io.erl
erlc -I include -o ebin -DERLANG_VERSION=\"19.3\" -DHAS_MAPS=true -DHAS_FULL_KEYS=true -DNEW_REC_CORE=true -DNEW_RAND=true -W1 src/lfe_qlc.erl
erlc -I include -o ebin -DERLANG_VERSION=\"19.3\" -DHAS_MAPS=true -DHAS_FULL_KEYS=true -DNEW_REC_CORE=true -DNEW_RAND=true -W1 src/lfe_trans.erl
erlc -I include -o ebin -DERLANG_VERSION=\"19.3\" -DHAS_MAPS=true -DHAS_FULL_KEYS=true -DNEW_REC_CORE=true -DNEW_RAND=true -W1 src/lfe_types.erl
erlc -I include -o ebin -DERLANG_VERSION=\"19.3\" -DHAS_MAPS=true -DHAS_FULL_KEYS=true -DNEW_REC_CORE=true -DNEW_RAND=true -W1 src/lfe_init.erl
erlc -I include -o ebin -DERLANG_VERSION=\"19.3\" -DHAS_MAPS=true -DHAS_FULL_KEYS=true -DNEW_REC_CORE=true -DNEW_RAND=true -W1 src/lfe_eval.erl
erlc -I include -o ebin -DERLANG_VERSION=\"19.3\" -DHAS_MAPS=true -DHAS_FULL_KEYS=true -DNEW_REC_CORE=true -DNEW_RAND=true -W1 src/lfe.erl
erlc -o src src/lfe_scan.xrl
erlc -I include -o ebin -DERLANG_VERSION=\"19.3\" -DHAS_MAPS=true -DHAS_FULL_KEYS=true -DNEW_REC_CORE=true -DNEW_RAND=true -W1 src/lfe_scan.erl
install -m755 bin/lfeexec /usr/local/lib/lfe/bin
install: cannot stat 'bin/lfeexec': No such file or directory
Makefile:121: recipe for target 'bin/lfeexec' failed
make[1]: *** [bin/lfeexec] Error 1
rm src/lfe_scan.erl
make[1]: Leaving directory '/home/mjl/work/castlerock/src/test/lfe'
Makefile:95: recipe for target 'compile' failed
make: *** [compile] Error 2

Switching to master, the build succeeds. Switching back to develop, it is now possible to build.
I'm guessing this is because some things in bin (lfeexec?) gets built properly on master, and then becomes available to subsequent builds on develop. As the initial build on develop also seems to try to do an install, I'm guessing the whole build process gets derailed somehow, possibly because of the missing lfeexec.
For reference, I'm doing this on Ubuntu 17.04 64bit, using Erlang Systems Erlang 19.3.

/cc @oubiwann

There shouldn't be any difference between building master and building develop (famous last words)

As I recall, there where quite some difference between the Makefile on master and develop when I tried to build, but I did not have time then to go through it. I can do another test later this afternoon, on the new master (after the 1.3 release), and see if I can figure it out.

This commit seems to be the culprit: https://github.com/rvirding/lfe/commit/a834120d271df6b5644b19e0b6bd4de33b27043b
I have not figured out why it breaks things, just that reverting it makes it possible to build again. If no one else beats me to it, I may have some time tomorrow to create a patch.
I think that the reason why some people don't see this problem is that if you've already built lfeexec as part of an older branch, it's already there, and you won't be bitten.

Odd. It's cool you found the breaking commit though. Fwiw I try to git clean -fdx when debugging issues like this one.

In fact, it seems to be the following rule that causes the problem:
$(BINDIR)/lfe%:
	$(INSTALL_BIN) $@ $(DESTBINDIR)

I'm unsure what the idea of this rule is in a broader context, but it seems the erlc-lfec rule triggers the erlc-compile (when 'lfeexecis *not* already compiled and existing inbin), which depends on a $(addprefix $(BINDIR)/, $(BINS), which I believe expands to, amongst others, bin/lfeexec, which then triggers the above rule that tries to install lfeexec`, rather than compile it. But given that my Makefile-fu is rusty, I might as well be totally wrong... :-)
I believe the problem can be easily triggered by simply deleting bin/lfeexec and trying to do a make compile.

Aha! I think you're right. I think the idea was to replace the curly brace globbing lfe{,c,doc,exec,script} with a pattern-matching rule. Seems like the trouble is that bin/lfeexec already has a rule.

Here's a quick and dirty approach that enables me to:
git clean -fdx
make compile

diff --git a/Makefile b/Makefile
index 59f2c06..a197308 100644
--- a/Makefile
+++ b/Makefile
@@ -117,9 +117,6 @@ comp_opts.mk:

 -include comp_opts.mk

-$(BINDIR)/lfe%:
-	$(INSTALL_BIN) $@ $(DESTBINDIR)
-
 install: compile install-man
 	rm -Rf $(DESTEBINDIR)
 	$(INSTALL_DIR) $(DESTEBINDIR)
@@ -127,7 +124,9 @@ install: compile install-man
 	$(INSTALL_DATA) $(addprefix $(EBINDIR)/, $(EBINS)) $(DESTEBINDIR)
 	$(INSTALL_DATA) $(addprefix $(EBINDIR)/, $(LBINS)) $(DESTEBINDIR)
 	$(INSTALL_DIR) $(DESTBINDIR)
-	$(MAKE) $(BINDIR)/lfe $(BINDIR)/lfec $(BINDIR)/lfedoc $(BINDIR)/lfescript
+	for f in $(BINDIR)/lfe $(BINDIR)/lfec $(BINDIR)/lfedoc $(BINDIR)/lfescript; do \
+		$(INSTALL_BIN) $f $(DESTBINDIR)
+	done
 	ln -sf $(DESTBINDIR)/* $(PREFIX)/bin/

 clean:

To be clear, as @superjudge discovered, the issue seems to be that the pattern rule added in a834120:
$(BINDIR)/lfe%:
	$(INSTALL_BIN) $@ $(DESTBINDIR)

results in the following:
install -m755 bin/lfeexec /usr/local/lib/lfe/bin

(as per make -n compile | grep lfeexec)
Notably, this is (erroneously) the only resulting install call.

@yurrriq that was a fix I was just about to suggest. It also seems a pretty reasonable solution. I will try to get a debian running and test it as well.

I've done it a bit cleaner in #338.

authors: rvirding superjudge yurrriq


text:
source repo has updated commits

hey! I don't know if you're still updating this but the source repo (tab organizer) has a pretty hefty commit related to themes. Might be worth pulling that in and pushing to crates.io.

For now the work on this is paused on my side due to health issues, but I will be happy to take a look if there is demand.
PRs always welcome as well :)

authors: rvolosatovs tcheinen

repo: rvolosatovs/web-extensions-sys

license: MIT

license_source: github-api


text:
checker.forEmber is not a function

checker.forEmber is not a function
TypeError: checker.forEmber is not a function
    at CoreObject.module.exports.included (/node_modules/ember-getowner-polyfill/index.js:13:32)

This function was added in https://github.com/ember-cli/ember-cli-version-checker/pull/21 and released in ember-cli-version-checker@1.2.0 (which is what we depend on in our package.json).
My guess is that an addon is including ember-getowner-polyfill but also including an older version of ember-cli-version-checker.
You can track that down via these two commands:
npm ls ember-getowner-polyfill
npm ls ember-cli-version-checker

Ok thanks!
The error has currently disapeared (following a re-install of the node modules) (thanks to the non-deterministic nature of npm). If and when it re-appears will make sure to run the commands provided above.

Great, thanks for reporting and letting me know that it seems resolved.

Re-install of node modules fixed it for me also: delete ./node_modules then $ npm install

authors: dirkdirk olivierlesnicki rwjblue

repo: rwjblue/ember-getowner-polyfill

license: mit


text:
[Snyk] Fix for 32 vulnerabilities

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

cmd/suggestion/nas/enas/v1beta1/requirements.txt

Vulnerabilities that will be fixed
By pinning:

Severity
Priority Score (*)
Issue
Upgrade
Breaking Change
Exploit Maturity

506/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 3.7
NULL Pointer Dereference SNYK-PYTHON-NUMPY-2321964
numpy:  1.21.3 -> 1.22.2
No
Proof of Concept

399/1000  Why? Has a fix available, CVSS 3.7
Buffer Overflow SNYK-PYTHON-NUMPY-2321966
numpy:  1.21.3 -> 1.22.2
No
No Known Exploit

506/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 3.7
Denial of Service (DoS) SNYK-PYTHON-NUMPY-2321970
numpy:  1.21.3 -> 1.22.2
No
Proof of Concept

509/1000  Why? Has a fix available, CVSS 5.9
Regular Expression Denial of Service (ReDoS) SNYK-PYTHON-SETUPTOOLS-3180412
setuptools:  39.0.1 -> 65.5.1
No
No Known Exploit

344/1000  Why? Has a fix available, CVSS 2.6
Denial of Service (DoS) SNYK-PYTHON-TENSORFLOW-3136192
tensorflow:  2.9.1 -> 2.10.1
No
No Known Exploit

344/1000  Why? Has a fix available, CVSS 2.6
Denial of Service (DoS) SNYK-PYTHON-TENSORFLOW-3136196
tensorflow:  2.9.1 -> 2.10.1
No
No Known Exploit

344/1000  Why? Has a fix available, CVSS 2.6
Denial of Service (DoS) SNYK-PYTHON-TENSORFLOW-3136200
tensorflow:  2.9.1 -> 2.10.1
No
No Known Exploit

569/1000  Why? Has a fix available, CVSS 7.1
Out-of-bounds Write SNYK-PYTHON-TENSORFLOW-3136204
tensorflow:  2.9.1 -> 2.10.1
No
No Known Exploit

344/1000  Why? Has a fix available, CVSS 2.6
Denial of Service (DoS) SNYK-PYTHON-TENSORFLOW-3136208
tensorflow:  2.9.1 -> 2.10.1
No
No Known Exploit

344/1000  Why? Has a fix available, CVSS 2.6
Denial of Service (DoS) SNYK-PYTHON-TENSORFLOW-3136212
tensorflow:  2.9.1 -> 2.10.1
No
No Known Exploit

444/1000  Why? Has a fix available, CVSS 4.6
Buffer Overflow SNYK-PYTHON-TENSORFLOW-3136216
tensorflow:  2.9.1 -> 2.10.1
No
No Known Exploit

344/1000  Why? Has a fix available, CVSS 2.6
NULL Pointer Dereference SNYK-PYTHON-TENSORFLOW-3136220
tensorflow:  2.9.1 -> 2.10.1
No
No Known Exploit

344/1000  Why? Has a fix available, CVSS 2.6
Denial of Service (DoS) SNYK-PYTHON-TENSORFLOW-3136224
tensorflow:  2.9.1 -> 2.10.1
No
No Known Exploit

344/1000  Why? Has a fix available, CVSS 2.6
Denial of Service (DoS) SNYK-PYTHON-TENSORFLOW-3136228
tensorflow:  2.9.1 -> 2.10.1
No
No Known Exploit

344/1000  Why? Has a fix available, CVSS 2.6
Denial of Service (DoS) SNYK-PYTHON-TENSORFLOW-3136232
tensorflow:  2.9.1 -> 2.10.1
No
No Known Exploit

344/1000  Why? Has a fix available, CVSS 2.6
Out-of-bounds Read SNYK-PYTHON-TENSORFLOW-3136236
tensorflow:  2.9.1 -> 2.10.1
No
No Known Exploit

344/1000  Why? Has a fix available, CVSS 2.6
Reachable Assertion SNYK-PYTHON-TENSORFLOW-3136240
tensorflow:  2.9.1 -> 2.10.1
No
No Known Exploit

344/1000  Why? Has a fix available, CVSS 2.6
Denial of Service (DoS) SNYK-PYTHON-TENSORFLOW-3136244
tensorflow:  2.9.1 -> 2.10.1
No
No Known Exploit

454/1000  Why? Has a fix available, CVSS 4.8
Denial of Service (DoS) SNYK-PYTHON-TENSORFLOW-3136248
tensorflow:  2.9.1 -> 2.10.1
No
No Known Exploit

344/1000  Why? Has a fix available, CVSS 2.6
Improper Input Validation SNYK-PYTHON-TENSORFLOW-3136252
tensorflow:  2.9.1 -> 2.10.1
No
No Known Exploit

344/1000  Why? Has a fix available, CVSS 2.6
Incorrect Calculation of Buffer Size SNYK-PYTHON-TENSORFLOW-3136256
tensorflow:  2.9.1 -> 2.10.1
No
No Known Exploit

344/1000  Why? Has a fix available, CVSS 2.6
Buffer Overflow SNYK-PYTHON-TENSORFLOW-3136260
tensorflow:  2.9.1 -> 2.10.1
No
No Known Exploit

554/1000  Why? Has a fix available, CVSS 6.8
Out-of-bounds Read SNYK-PYTHON-TENSORFLOW-3136264
tensorflow:  2.9.1 -> 2.10.1
No
No Known Exploit

454/1000  Why? Has a fix available, CVSS 4.8
Incorrect Calculation of Buffer Size SNYK-PYTHON-TENSORFLOW-3136268
tensorflow:  2.9.1 -> 2.10.1
No
No Known Exploit

344/1000  Why? Has a fix available, CVSS 2.6
Buffer Overflow SNYK-PYTHON-TENSORFLOW-3136272
tensorflow:  2.9.1 -> 2.10.1
No
No Known Exploit

344/1000  Why? Has a fix available, CVSS 2.6
Always-Incorrect Control Flow Implementation SNYK-PYTHON-TENSORFLOW-3136276
tensorflow:  2.9.1 -> 2.10.1
No
No Known Exploit

554/1000  Why? Has a fix available, CVSS 6.8
Out-of-Bounds SNYK-PYTHON-TENSORFLOW-3136280
tensorflow:  2.9.1 -> 2.10.1
No
No Known Exploit

579/1000  Why? Has a fix available, CVSS 7.3
Out-of-bounds Write SNYK-PYTHON-TENSORFLOW-3136509
tensorflow:  2.9.1 -> 2.10.1
No
No Known Exploit

589/1000  Why? Has a fix available, CVSS 7.5
Denial of Service (DoS) SNYK-PYTHON-TENSORFLOW-3136512
tensorflow:  2.9.1 -> 2.10.1
No
No Known Exploit

589/1000  Why? Has a fix available, CVSS 7.5
Heap-based Buffer Overflow SNYK-PYTHON-TENSORFLOW-3136515
tensorflow:  2.9.1 -> 2.10.1
No
No Known Exploit

509/1000  Why? Has a fix available, CVSS 5.9
Denial of Service (DoS) SNYK-PYTHON-TENSORFLOW-3136520
tensorflow:  2.9.1 -> 2.10.1
No
No Known Exploit

589/1000  Why? Has a fix available, CVSS 7.5
Regular Expression Denial of Service (ReDoS) SNYK-PYTHON-WHEEL-3180413
wheel:  0.30.0 -> 0.38.0
No
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.
Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 NULL Pointer Dereference
🦉 Denial of Service (DoS)

Pull Request Test Coverage Report for Build 4410582249

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.1%) to 72.857%

Totals

Change from base Build 4238827672:
-0.1%

Covered Lines:
3111

Relevant Lines:
4270

💛  - Coveralls

source: gharchive/pull-request

authors: coveralls ryan-ally

repo: ryan-ally/katib


text:
Will react localize redux package set the lang attribute in  element ?

Do you want to request a feature or report a bug?
Bug
What is the current behavior?
Will react localize redux package set the lang attribute in  element ?
What is the expected behavior?
As per accessibility issues, we see Html element is not set with a lang attribute.

This would be up to you to set this attribute as react-localize-redux is completely agnostic when it comes to setting up the languages you're supporting. This would be a matter of updating the html lang attribute every time the active language changes. The implementation of that is outside the scope of this library though as it really depends on how your app is setup. e.g. Is the  element part of your react app vs not

authors: lavanya-kuda ryandrewjohnson

repo: ryandrewjohnson/react-localize-redux


text:
Validation messages are link to the first child object when using a list in the Model of the edit context

When using a list with multiple child object in the model of the edit context,
all the validation messages of all the child objects are linked to the first child object.

Working as intended. If requiring a different / more advanced behavior, PR welcome.

I need a more detailed information about this issue. For example, a repro.

Ok, I'll try to give you a description or project to reproduce this issue, I'll keep you informed when I have it. Thank you for taking a look at it.

FluentValidation.Blazor.Repro.zip
I've created a repro project. The example is on the home page of the repro project. Just click the submit button and then you can see that all the validation messages appear at the first address instead of at their own address.
The suggested fix from PR #37 fixes this issue.

Is this solved in 3.0 v?

authors: BEzGumpTion ryanelian sergshu


text:
utop: segfault, matrices not printing

Maybe these are different problems, but they're appearing at the same time; I just pulled the latest master this evening.  I get a segfault or another memory error from reverse in utop sometimes.  I'm not sure what else causes it.  Also, matrices are not printing out their contents in utop, even though I am running #require "owl_zoo".  These problems aren't occurring with a version of Owl from a day or two ago.
# let k = M.sequential 1 51;;
val k : M.mat = <abstr>
# M.reverse k;;
- : M.mat = <abstr>
ocamlrun(88974,0x7fff73eca000) malloc: *** error for object 0x7fcd087c1d78: incorrect checksum for freed object - object was probably modified after being freed.
*** set a breakpoint in malloc_error_break to debug
/Users/marshall/bin/itop: line 2: 88974 Abort trap: 6           utop `find _build/default -name '*.cma' | sed -e 's/[.a-zA-Z]*$//' -e 's/^/-I /'` "$@"

(itop is just utop run from a script with some extra -I flags.)
let k = M.sequential 1 51;;
val k : M.mat = <abstr>
# let xs = M.concat_vertical k k;;
val xs : M.mat = <abstr>
# let xs = M.concat_vertical k (M.reverse k);;
/Users/marshall/bin/itop: line 2: 88962 Segmentation fault: 11  utop `find _build/default -name '*.cma' | sed -e 's/[.a-zA-Z]*$//' -e 's/^/-I /'` "$@"

I would rather have had a chance to do more investigation before reporting this, but it seems serious enough that I felt I should report it right away.
One thing that's different in my config is that I add -L/usr/local/opt/openblas/lib to src/owl/jbuild, following earlier advice for MacOS.  I'm also using 4.05.0+flambda, though I don't add any -O flags or anything else to the Owl jbuild files other than that -L.  I can try vanilla 4.05.0 in the morning if that seems helpful, roll back to earlier versions and see where the problems are introduced, etc.
utop -version
The universal toplevel for OCaml, version 2.0.1, compiled for OCaml version 4.05.0

I get similar error message on my machine using the latest master branch code:
utop # Mat.reverse k;;
- : Mat.mat = <abstr>
*** Error in `/usr/bin/ocamlrun': double free or corruption (out): 0x0000000001ba9f70 ***
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x777e5)[0x7f72ea78d7e5]
/lib/x86_64-linux-gnu/libc.so.6(+0x8037a)[0x7f72ea79637a]
/lib/x86_64-linux-gnu/libc.so.6(cfree+0x4c)[0x7f72ea79a53c]
/usr/bin/ocamlrun(caml_empty_minor_heap+0x116)[0x40ec96]
/usr/bin/ocamlrun(caml_gc_dispatch+0x46)[0x40f106]
/usr/bin/ocamlrun(caml_make_vect+0x10c)[0x416e4c]
/usr/bin/ocamlrun(caml_interprete+0x13cb)[0x4276db]
/usr/bin/ocamlrun(caml_main+0x1e8)[0x4296d8]
/usr/bin/ocamlrun(main+0xc)[0x40ca2c]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7f72ea736830]
/usr/bin/ocamlrun(_start+0x29)[0x40ca69]
======= Memory map: ========
00400000-00437000 r-xp 00000000 103:05 527937                            /usr/bin/ocamlrun
00636000-00637000 r--p 00036000 103:05 527937                            /usr/bin/ocamlrun
00637000-00639000 rw-p 00037000 103:05 527937                            /usr/bin/ocamlrun
...
7f72e9e7b000-7f72e9e7c000 r--p 0000e000 103:05 802480              /usr/lib/ocaml/stublibs/dllunix.so
Aborted (core dumped)

I was trying to change the shape of the matrix or generate  matrix with Mat.zeros but the same error still occur.
utop -version
The universal toplevel for OCaml, version 2.0.1, compiled for OCaml version 4.04.2

Thank for reporting this. This relates to my last night's update on simplifying the types in owl_dense_common. I implemented a new owl_copy function with slightly different semantics. This should have been fixed now, please give it a try.
There are also several other places called owl_copy, I will check them all later today. But in case you noticed anything wrong, please do let me know, many thanks!

Thanks very much; I've experienced no memory problems so far with the new commit.
Matrices are still not printing out, so that seems to be a different problem.  In utop:
# #require "owl_zoo";;
# M.sequential 1 8;;
- : M.mat = <abstr>
#

@mars0i my apologies, I replied here last night: https://github.com/ryanrhymes/owl/issues/99
In short,
#require "owl_top";;

Ah, OK, great.  For some reason I didn't get a notification for that.

authors: jzstark mars0i ryanrhymes

repo: ryanrhymes/owl


text:
For CloudFront, the ACM certificates must always be in us-east-1

ACM is available in more regions, but for CloudFront, they must always be created and discovered in us-east-1.

I'm going to close this PR so that it no longer shows up in my list of outstanding PRs (especially since this custom resource is no longer needed).

repo: ryansb/acm-certs-cloudformation


text:
StackOverflowError when using Spring 4.3

I am trying to upgrade to Spring 4.3.0, but I am unable to initialize the spring context:
[ERROR] 09:25:31  Context initialization failed []
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'healthCheckBeanPostProcessor' defined in class path resource [com/ryantenney/metrics/spring/config/annotation/DelegatingMetricsConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.beans.factory.config.BeanPostProcessor]: Factory method 'healthCheckBeanPostProcessor' threw exception; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'getHealthCheckRegistry' defined in class path resource [com/ryantenney/metrics/spring/config/annotation/DelegatingMetricsConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.codahale.metrics.health.HealthCheckRegistry]: Factory method 'getHealthCheckRegistry' threw exception; nested exception is java.lang.IllegalStateException: Failed to introspect annotations on public com.codahale.metrics.health.HealthCheckRegistry com.ryantenney.metrics.spring.config.annotation.DelegatingMetricsConfiguration.getHealthCheckRegistry()
    at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:599) ~[spring-beans-4.3.0.RELEASE.jar:4.3.0.RELEASE]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:1123) ~[spring-beans-4.3.0.RELEASE.jar:4.3.0.RELEASE]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1018) ~[spring-beans-4.3.0.RELEASE.jar:4.3.0.RELEASE]
[... more stuff ...]
Caused by: java.lang.StackOverflowError
    at java.lang.reflect.Method.hashCode(Method.java:330) ~[?:1.8.0_65]
    at java.util.HashMap.hash(HashMap.java:338) ~[?:1.8.0_65]
    at java.util.HashMap.put(HashMap.java:611) ~[?:1.8.0_65]
    at java.util.HashSet.add(HashSet.java:219) ~[?:1.8.0_65]
    at org.springframework.core.annotation.AnnotatedElementUtils.searchWithFindSemantics(AnnotatedElementUtils.java:1119) ~[spring-core-4.3.0.RELEASE.jar:4.3.0.RELEASE]
    at org.springframework.core.annotation.AnnotatedElementUtils.searchWithFindSemantics(AnnotatedElementUtils.java:1183) ~[spring-core-4.3.0.RELEASE.jar:4.3.0.RELEASE]
    at org.springframework.core.annotation.AnnotatedElementUtils.searchWithFindSemantics(AnnotatedElementUtils.java:1208) ~[spring-core-4.3.0.RELEASE.jar:4.3.0.RELEASE]
    at org.springframework.core.annotation.AnnotatedElementUtils.searchWithFindSemantics(AnnotatedElementUtils.java:1086) ~[spring-core-4.3.0.RELEASE.jar:4.3.0.RELEASE]
    at org.springframework.core.annotation.AnnotatedElementUtils.searchWithFindSemantics(AnnotatedElementUtils.java:1060) ~[spring-core-4.3.0.RELEASE.jar:4.3.0.RELEASE]
    at org.springframework.core.annotation.AnnotatedElementUtils.findMergedAnnotationAttributes(AnnotatedElementUtils.java:656) ~[spring-core-4.3.0.RELEASE.jar:4.3.0.RELEASE]
    at org.springframework.core.annotation.AnnotatedElementUtils.findMergedAnnotation(AnnotatedElementUtils.java:730) ~[spring-core-4.3.0.RELEASE.jar:4.3.0.RELEASE]
    at org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:314) ~[spring-context-4.3.0.RELEASE.jar:4.3.0.RELEASE]
    at com.ryantenney.metrics.spring.config.annotation.DelegatingMetricsConfiguration$$EnhancerBySpringCGLIB$$2cc24d5e.getHealthCheckRegistry(<generated>) ~[metrics-spring-3.1.3.jar:?]
    at com.ryantenney.metrics.spring.config.annotation.MetricsConfigurerComposite.getHealthCheckRegistry(MetricsConfigurerComposite.java:68) ~[metrics-spring-3.1.3.jar:?]
    at com.ryantenney.metrics.spring.config.annotation.DelegatingMetricsConfiguration.getHealthCheckRegistry(DelegatingMetricsConfiguration.java:69) ~[metrics-spring-3.1.3.jar:?]
    at com.ryantenney.metrics.spring.config.annotation.DelegatingMetricsConfiguration$$EnhancerBySpringCGLIB$$2cc24d5e.CGLIB$getHealthCheckRegistry$3(<generated>) ~[metrics-spring-3.1.3.jar:?]
    at com.ryantenney.metrics.spring.config.annotation.DelegatingMetricsConfiguration$$EnhancerBySpringCGLIB$$2cc24d5e$$FastClassBySpringCGLIB$$7853f663.invoke(<generated>) ~[metrics-spring-3.1.3.jar:?]
    at org.springframework.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:228) ~[spring-core-4.3.0.RELEASE.jar:4.3.0.RELEASE]
    at org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:356) ~[spring-context-4.3.0.RELEASE.jar:4.3.0.RELEASE]
    at com.ryantenney.metrics.spring.config.annotation.DelegatingMetricsConfiguration$$EnhancerBySpringCGLIB$$2cc24d5e.getHealthCheckRegistry(<generated>) ~[metrics-spring-3.1.3.jar:?]
    at com.ryantenney.metrics.spring.config.annotation.MetricsConfigurerComposite.getHealthCheckRegistry(MetricsConfigurerComposite.java:68) ~[metrics-spring-3.1.3.jar:?]
    at com.ryantenney.metrics.spring.config.annotation.DelegatingMetricsConfiguration.getHealthCheckRegistry(DelegatingMetricsConfiguration.java:69) ~[metrics-spring-3.1.3.jar:?]
    at com.ryantenney.metrics.spring.config.annotation.DelegatingMetricsConfiguration$$EnhancerBySpringCGLIB$$2cc24d5e.CGLIB$getHealthCheckRegistry$3(<generated>) ~[metrics-spring-3.1.3.jar:?]
    at com.ryantenney.metrics.spring.config.annotation.DelegatingMetricsConfiguration$$EnhancerBySpringCGLIB$$2cc24d5e$$FastClassBySpringCGLIB$$7853f663.invoke(<generated>) ~[metrics-spring-3.1.3.jar:?]
    [... repeat 100 times ...]
    at org.springframework.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:228) ~[spring-core-4.3.0.RELEASE.jar:4.3.0.RELEASE]
    at org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:356) ~[spring-context-4.3.0.RELEASE.jar:4.3.0.RELEASE]
    at com.ryantenney.metrics.spring.config.annotation.DelegatingMetricsConfiguration$$EnhancerBySpringCGLIB$$2cc24d5e.getHealthCheckRegistry(<generated>) ~[metrics-spring-3.1.3.jar:?]
    at com.ryantenney.metrics.spring.config.annotation.MetricsConfigurerComposite.getHealthCheckRegistry(MetricsConfigurerComposite.java:68) ~[metrics-spring-3.1.3.jar:?]
    at com.ryantenney.metrics.spring.config.annotation.DelegatingMetricsConfiguration.getHealthCheckRegistry(DelegatingMetricsConfiguration.java:69) ~[metrics-spring-3.1.3.jar:?]
    at com.ryantenney.metrics.spring.config.annotation.DelegatingMetricsConfiguration$$EnhancerBySpringCGLIB$$2cc24d5e.CGLIB$getHealthCheckRegistry$3(<generated>) ~[metrics-spring-3.1.3.jar:?]
    at com.ryantenney.metrics.spring.config.annotation.DelegatingMetricsConfiguration$$EnhancerBySpringCGLIB$$2cc24d5e$$FastClassBySpringCGLIB$$7853f663.invoke(<generated>) ~[metrics-spring-3.1.3.jar:?]

Seems to happen when a @Configuration class is annotated with @EnableMetrics.

Which stack frame or set of stack frames repeats 100 times?

Not exactly a hundred, but several dozens:
    at org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:356) ~[spring-context-4.3.0.RELEASE.jar:4.3.0.RELEASE]
    at com.ryantenney.metrics.spring.config.annotation.DelegatingMetricsConfiguration$$EnhancerBySpringCGLIB$$2cc24d5e.getHealthCheckRegistry(<generated>) ~[metrics-spring-3.1.3.jar:?]
    at com.ryantenney.metrics.spring.config.annotation.MetricsConfigurerComposite.getHealthCheckRegistry(MetricsConfigurerComposite.java:68) ~[metrics-spring-3.1.3.jar:?]
    at com.ryantenney.metrics.spring.config.annotation.DelegatingMetricsConfiguration.getHealthCheckRegistry(DelegatingMetricsConfiguration.java:69) ~[metrics-spring-3.1.3.jar:?]
    at com.ryantenney.metrics.spring.config.annotation.DelegatingMetricsConfiguration$$EnhancerBySpringCGLIB$$2cc24d5e.CGLIB$getHealthCheckRegistry$3(<generated>) ~[metrics-spring-3.1.3.jar:?]
spring```

@ryantenney Are you able to reproduce it, and/or do you need more info from me?

I'm trying to understand what @EnableMetrics does.  Is it only used to enable scanning of the  @Metric annotation?

    at org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:356) ~[spring-context-4.3.1.RELEASE.jar:4.3.1.RELEASE]

    at com.ryantenney.metrics.spring.config.annotation.DelegatingMetricsConfiguration$$EnhancerBySpringCGLIB$$2c4ac852.getMetricRegistry(<generated>) ~[metrics-spring-3.1.3.jar:na]
    at com.ryantenney.metrics.spring.config.annotation.MetricsConfigurerComposite.getMetricRegistry(MetricsConfigurerComposite.java:52) ~[metrics-spring-3.1.3.jar:na]
    at com.ryantenney.metrics.spring.config.annotation.DelegatingMetricsConfiguration.getMetricRegistry(DelegatingMetricsConfiguration.java:59) ~[metrics-spring-3.1.3.jar:na]
    at com.ryantenney.metrics.spring.config.annotation.DelegatingMetricsConfiguration$$EnhancerBySpringCGLIB$$2c4ac852.CGLIB$getMetricRegistry$2(<generated>) ~[metrics-spring-3.1.3.jar:na]
    at com.ryantenney.metrics.spring.config.annotation.DelegatingMetricsConfiguration$$EnhancerBySpringCGLIB$$2c4ac852$$FastClassBySpringCGLIB$$2acb39f3.invoke(<generated>) ~[metrics-spring-3.1.3.jar:na]
    at org.springframework.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:228) ~[spring-core-4.3.1.RELEASE.jar:4.3.1.RELEASE]

It happens during the call to: "com.ryantenney.metrics.spring.config.annotation.DelegatingMetricsConfiguration#getMetricRegistry" because "delegates" contain an instance of "DelegatingMetricsConfiguration" which causes Stack Overflow.

Yes, this is happening for me as well. I upgrade to boot 1.4.x and the MetricRegistry bean can no longer create. It looks like recursion in the DelegatingMetricsConfiguration#getMetricRegistry.
Metric registry is null, and the delegates recurse.

@roykachouh @henrik242 @rafal-glowinski do any of you have AspectJ Autoproxying enabled?

@ryantenney Nope, not that I'm aware of.

@ryantenney thanks for looking into this...no i don't have aspectj autoproxying enabled...i even tried disabling the auto-configuration just in case...but to no avail, the stack still overflows...
  aop:
    auto: false```

For now I "fixed" this by removing @EnableMetrics and adding this:
@Configuration
public class CustomDelegatingMetricsConfiguration extends DelegatingMetricsConfiguration {

	@Override
	@Autowired(required = false)
	public void setMetricsConfigurers(final List<MetricsConfigurer> configurers) {
	}
}

Yep, temporarily got around it by removing EnableMetrics
On Wed, Aug 3, 2016 at 5:46 PM Dmitry Chornyi notifications@github.com
wrote:

For now I "fixed" this by removing @EnableMetrics and adding this:
@Configuration
public class CustomDelegatingMetricsConfiguration extends DelegatingMetricsConfiguration {
@Override
@Autowired(required = false)
public void setMetricsConfigurers(final List<MetricsConfigurer> configurers) {
}

}
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ryantenney/metrics-spring/issues/184#issuecomment-237384933,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB_QXtAcdNMOW1K82bsmqZ2kUxtsIaLyks5qcQw7gaJpZM4JF1GW
.

I'm having the same issue and it looks like it is because the @EnableMetrics annotation does not work correctly on a @Configuration POJO.
This works:
@Configuration
@EnableMetrics
public class MetricsConfig extends MetricsConfigurerAdapter {
}

This does not and causes the stack overflow
@Configuration
@EnableMetrics
public class MetricsConfig {
}

I ran into the same problem. I've tracked the issue down to DelegatingMetricsConfiguration.setMetricsConfigurers(List<MetricsConfigurer> configurers). The issue is that configurers contains itself (i.e. this), obviously a big no-no for a list of delegates. There must have been a change in Spring 1.4 that allows autowiring objects with themselves.

This issue should be closed, as it doesn't reproduce with spring 4.3.7 (spring boot 1.5.X).

I have spring 4.3.9 and it still reproduces

authors: Trii celandroWeblate chornyi henrik242 laur89 rafal-glowinski roykachouh ryantenney sfussenegger

repo: ryantenney/metrics-spring


text:
Support recursive types

e.g.
type t = A | B(t);

type r1 = W | X(r2)
and r2 = Y | Z(r1);

I'd be happy to (try) to take a look

Thanks @boyswan! It may be as easy as making this line, where the let statements are generated, use Recursive instead of Nonrecursive. Unfortunately I can't find the documentation I used when developing this originally, but these might help:
https://docs.mirage.io/ocaml-migrate-parsetree/Ast_402/index.html
https://github.com/ocaml-ppx/ocaml-migrate-parsetree/blob/master/src/ast_402.ml
One of the tricky things will be that, IIRC, the compiler will emit a warning if the rec flag is included but recursion isn't used, so we won't want to include it for all codecs – just the ones we generate for types that are actually recursive.
As far as environment setup and building goes, the package.json and .travis.yml will point you in the right direction. Let me know if it's not intuitive to get up and running and I can put together a guide.
Finally, you can run ppx/_esy/default/build/install/default/lib/ppx_decco/ppx.exe in.ml > out.ml to see what the output of the PPX is given an Ocaml input. AFAIK the ppx can't be run directly on a Reason file, but you can use refmt to convert between re and ml.
Let me know what questions you have!

So I started looking into this and ran into a snag: the rec_flag for type declarations isn't exposed in Ast_402. This means that we can't detect the nonrec flag which is necessary to do this properly. This may need to wait until #23 is done.


text:
Lecture03 practice

Габдрахманов Ильнар

Coverage decreased (-16.4%) to 31.624% when pulling c26a0ff4c6b183d4658a3a45e922b9fbaca5cdbb on Anonimous102:lecture03 into 16dad782f5d596ae50d0b39665b32df40da60c19 on rybalkinsd:lecture03.

Не вижу тестов

Coverage increased (+23.7%) to 71.795% when pulling 4aac5c072f83bc78d1401bb7730902306add6a68 on Anonimous102:lecture03 into 16dad782f5d596ae50d0b39665b32df40da60c19 on rybalkinsd:lecture03.

authors: Anonimous102 IVSivak coveralls

repo: rybalkinsd/atom


text:
Make HomeWork 1 great again

Сделано Воробьевым Евгением.

OK

authors: DeviantBadge rybalkinsd

repo: rybalkinsd/kotlin-boot-camp


text:
Error during sigdial (Misplaced alignment tab character & )

While running this command
./bin/generate examples/sigdial --proceedings --handbook
Misplaced alignment tab character &.
 &
l.275    Ruihong Huang, Texas A\&
M University, United States\

Did you change the input from the sigdial example?
In this case, remember that input text should be escaped to be later compiled in latex

I did not change it.
Anyway it worked when I use the below commands. Thanks a million.
./bin/generate examples/sigdial --proceedings --overwite.

Perfect


text:
Can the new version of jetjrains gateway be supported?

Since the "vcs" module has been updated, it appears to only be supported until 2024.1.4. I'll probably try to fix it this week.

authors: AhDEV-free ryoii

repo: ryoii/git-extend-untracked


text:
@ExtensionMethod not working properly with templates and lambda expressions in Eclipse

I had a little play around with this feature and stumbled across an issue.
I am currently trying to use the @ExtensionMethod on the new Java 8 Stream.
I tried the following:
import java.util.Arrays;
import java.util.Spliterator;
import java.util.function.Consumer;
import java.util.function.Supplier;
import java.util.stream.Stream;
import java.util.stream.StreamSupport;

import lombok.experimental.ExtensionMethod;

@ExtensionMethod({Extension.class})
public class Test {
  public static void test() {
    // Working
    Arrays.asList("123", "abc", "test").stream()
        .nonEmptyStream((Supplier<RuntimeException>) () -> new RuntimeException())
        .forEach(System.out::println);

    // Working
    ((Stream<String>) Arrays.stream(TestEnum.values()).filter(test -> test.isOk())
        .map(test -> test.toString()))
            .nonEmptyStream((Supplier<RuntimeException>) () -> new RuntimeException())
            .forEach(System.out::println);

    // Error in Eclipse:
    // The method nonEmptyStream(Stream<T>, Supplier<RuntimeException>) in the type Extension is not
    // applicable for the arguments (Stream<String>, Supplier<RuntimeException>)
    Arrays.stream(TestEnum.values()).filter(test -> test.isOk()).map(test -> test.toString())
        .nonEmptyStream((Supplier<RuntimeException>) () -> new RuntimeException())
        .forEach(System.out::println);

    // Error in Eclipse:
    // The method nonEmptyStream(Stream<T>, Supplier<RuntimeException>) in the type Extension is not
    // applicable for the arguments (Stream<String>)
    Arrays.asList("123", "abc", "test").stream().nonEmptyStream(() -> new RuntimeException())
        .forEach(System.out::println);
  }
}

class Extension {
  public static <T> Stream<T> nonEmptyStream(Stream<T> stream, Supplier<RuntimeException> e) {
    Spliterator<T> it = stream.spliterator();
    return StreamSupport.stream(new Spliterator<T>() {
      boolean seen;

      public boolean tryAdvance(Consumer<? super T> action) {
        boolean r = it.tryAdvance(action);
        if (!seen && !r)
          throw e.get();
        seen = true;
        return r;
      }

      public Spliterator<T> trySplit() {
        return null;
      }

      public long estimateSize() {
        return it.estimateSize();
      }

      public int characteristics() {
        return it.characteristics();
      }
    }, false);
  }
}

enum TestEnum {
  BLA, TEST;

  public boolean isOk() {
    return this == BLA;
  }
}

But when I compile this using a compilation tool (like gradle) it works without any problem!
Tested with version 1.16.8

I have a similar problem and it seems to be dependent on the Eclipse version.
This minmal example works in Luna, but stops working in Mars. Also tested in Mars 2 and Neon 3, it refuses to play. Maven compile works though.
Code:
@ExtensionMethod({Extension.class})
public class ExtTest {

    public static void main(String[] args){
        System.out.println(Stream.of("a","b","c").map(x->x+"test").toList()); //The method toList(Stream<T>) in the type Extension is not applicable for the arguments (Stream<String>)
    }

}

public class Extension {
	public static <T> List<T> toList(Stream<T> stream){
		return stream.collect(Collectors.toList());
	}
}

These variants compile without error:
Stream<String> stream = Stream.of("a","b","c").map(x->x+"test");
System.out.println(stream.toList());

System.out.println(Stream.of("a","b","c").map(x->x+"test").distinct().toList());

+1
Can you please fix this? Makes @ExtensionMethol less useful with Eclipse.

Still having this problem with 1.18.4 and Eclipse 2018-12 (4.10.0)

authors: BrainStone fwgreen maherm tintor

repo: rzwitserloot/lombok


text:
Precise parallel relation size

Hi:
Can ask for the reason why in default RelIndexRead implementation for CRelIndex, we are computing an approximate size?
I was thinking use precise relation size may avoid the redundunt computation in the case that some inner join body clause is empty.
Yihao

For more details, what I want do is add following change in line 522 in ascent_macro/src/ascent_codegen to :
let size_check_code_list = rule.body_items.iter().filter_map(|bi| {
         if let MirBodyItem::Clause(clause) = bi {
            let rel = expr_for_rel(&clause.rel, mir);
               Some(quote! {
                  #rel.len() > 0
               })
         } else {None}
      });
      // connect the size check code with logical and
      let size_check_code = size_check_code_list.reduce(|a, b| quote!{#a && #b}).unwrap_or(quote!{true});
      evaluate_rules.push(if rule_parallelism { quote! {
         ascent::internal::comment(#msg);
         if #size_check_code {
            __scope.spawn(|_| {
               #before_rule_var
               #rule_compiled
               #update_rule_time_field
            });
         }
      }} else { quote! {
         #before_rule_var
         ascent::internal::comment(#msg);
         if #size_check_code {
            #rule_compiled
         }
         #update_rule_time_field
      }});
   }

Seems when running large rules like ddisasm, this extra check could save us lots of time avoid spinning in long tail iterations

Hey @StarGazerM, yeah I think that's reasonable. I initially made the len an estimate for perf reasons (you can check its impl for parallel relations). But maybe we can calculate the len when freezing the rel. But I'd need to think about how it would affect BYODS rels. In any case, if making the len precise turns out not to be feasible for BYODS rels, we can add an is_empty() method to RelIndexRead and do the optimization you suggested.

yep, I agree, if the len can be unreliable for many data structure maybe we can consider rename? ==, although now these change will immediate force everywhere to be changed in current BYODS relations....

authors: StarGazerM s-arash

repo: s-arash/ascent


text:
Passing active parameter to getData

This allows restricting the data returned by using a row range lookup value:
visible - Rows currently visible in the table viewport
active - Rows currently in the table (rows that pass current filters etc)
selected - Rows currently selected by the selection module (this includes not currently active rows)
all - All rows in the table regardless of filters

The parameter is named active as this is what it is called in the original source code: https://github.com/olifolkerd/tabulator/blob/75799201323ac2f4a912aeec9a9668494c2c3099/src/js/core.js#L976

thanks @samcarswell (@claresloggett) looks good - can you add a doc string for the autocomplete.
I know most methods are missing docstrings but it's on my to do list to add them all.
No more than a couple of sentence but it should include the valid values for active
And I think the default value should be "all" rather than False.

Hi @s-cork, no problem. I've added a doc string and updated the default active value. Let me know if anything else needs to change.

authors: s-cork samcarswell

repo: s-cork/Tabulator


text:
Border Gradient With Animation

Issue:

Someone else is assigned to this @FvorY please make sure to comment on issues to be assigned to them before working on them.

authors: FvorY shahednasser

repo: sButtons/sbuttons


text:
Toast positioning classes not working with responsive prefixes

Responsive prefixes are not applying to the classes used to position toast.
I was able to recreate the bug in the tailwind playground (link). You can see that the button changes color responsively, but the toast does not change position, even though both are using the md: responsive prefix.
I understand that the basetoast class is not intended to be responsive, but the documentation says that the positioning classes are.

Another note: I looked at the CSS that was generated in the linked tailwind playground, and for the component CSS, this block of code was at the bottom:
   {
    top: auto;
    bottom: 0px;
    --tw-translate-y: 0px;
    transform: translate(var(--tw-translate-x), var(--tw-translate-y)) rotate(var(--tw-rotate)) skewX(var(--tw-skew-x)) skewY(var(--tw-skew-y)) scaleX(var(--tw-scale-x)) scaleY(var(--tw-scale-y));
  }

I think those styles are meant to be the responsive toast-bottom styles, but for some reason the selector is just blank

This is unexpected behavior. I used :where() selectors which caused Tailwind CSS to generate empty selectors for some reason.
I opened an issue for it: https://github.com/tailwindlabs/tailwindcss/issues/9303
If that didn't get fixed I should somehow find another way...

repo: saadeghi/daisyui


text:
bug: Z-index issues with the tooltip component

What version of daisyUI are you using?
4.6.1
Which browsers are you seeing the problem on?
Firefox, Other
Reproduction URL
https://stackblitz.com/edit/vitejs-vite-v8afg3?file=src%2FApp.tsx
Describe your issue
The Tooltip component appears behind the pinned row table component.
https://github.com/saadeghi/daisyui/assets/25080013/f1388899-17d4-4852-b78e-8d166dd330ff

By default it has no z-index.  but you can add a z-index like z-10 or (any value) to the tooltip.
z-index is something you should define based on the content of the page because in some cases you may want things to be placed under tooltip and sometimes you may want them to be over tooltip. It's not a good idea for daisyUI to make decisions about that.
Let me know if you have a question.

authors: nbran saadeghi


text:
VideoToVideo Example Runners And StableDiffusionService GenerateInputVideoFrames Bug Fix

Added Example Runners for VideoToVideo demos, one from scratch and one using the VideoService.
Fixed bug in StableDiffusionService GenerateInputVideoFrames where promptOptions.InputVideo.VideoFrames was being checked to not be null twice.

Awesome thanks for adding these.


text:
Fixed reset and filter counter issue on Revenue filter page

Summary:
Fixed reset and filter counter issue on the Revenue filter page
Preview:
https://www.loom.com/share/7a58f8842d3e4ecdbb71818d2f69c792

@apoorv1316 Please test this PR before mergin it

@Ankita012 Apoorv has raised issues on the UI of filter panel let me know how much work is done in the current PR.
https://www.notion.so/saeloun/Update-the-UI-for-filter-panel-on-revenue-report-094a8bec41a24a079694e37fd4851dc6?pvs=4

@Ankita012 Please update

@Ankita012 Apoorv has raised issues on the UI of filter panel let me know how much work is done in the current PR. https://www.notion.so/saeloun/Update-the-UI-for-filter-panel-on-revenue-report-094a8bec41a24a079694e37fd4851dc6?pvs=4

@Ankita012 Apoorv has raised issues on the UI of filter panel let me know how much work is done in the current PR. https://www.notion.so/saeloun/Update-the-UI-for-filter-panel-on-revenue-report-094a8bec41a24a079694e37fd4851dc6?pvs=4

on Press ESC key panel gets closed fixed.
on selection of clients All clients option removed from the main screen got fixed.
on clearall, all filters were removed. Fixed.
All filter counter things are working- Fixed

repo: saeloun/miru-web


text:
Running BioCypher from GitHub install shows "This is BioCypher vNone." instead of the current version.

E.g. in the tum-bc pipeline

I've fixed this in c4d2c93, wait a bit until merge

authors: deeenes slobentanzer

repo: saezlab/BioCypher


text:
Summary
I would like to add IRISHub Mainnet which is the first mainnet in Cosmos Ecosystem: https://irisnet.org/
Chain ID
6688
Chain detail URL
https://chainlist.org/chain/6688
RPC URL
https://evmrpc.irishub-1.irisnet.org
Blockscout Client URL
No response
Etherscan Client URL
No response
Etherscan Client API URL
No response
Version
1.4.1
Address (Master copy)
0x41675C099F32341bf84BFc5382aF534df5C7461a
Deployment Tx hash (Master copy)
0xde92d2a06a77ddfd447819c7b20182363576c53aab65b8d7dfb9afd1dd6a605b
Block explorer URL (Master copy)
No response
Address (Master copy L2)
0x29fcB43b46531BcA003ddC8FCB67FFE91900C762
Deployment Tx hash (Master copy L2)
0xae25619dc9393b5d10c296467df1c4582ab3d6794fa07ea88cdc24c5bc36c3dc
Block explorer URL (Master copy L2)
No response
Address (Proxy factory)
0x4e1DCf7AD4e460CfD30791CCC4F9c8a4f820ec67
Deployment Tx hash (Proxy factory)
0xdd2e5eb9770223822e8088ce49dd6ff8cbc0289241e8dba8035b26dc4eaf5113
Block explorer URL (Proxy factory)
No response

Please, @mitch1024, add these addresses first in https://github.com/safe-global/safe-deployments.
Thanks!

Please, @mitch1024, add these addresses first in https://github.com/safe-global/safe-deployments.
Thanks!

Done: https://github.com/safe-global/safe-deployments/pull/746

/execute

repo: safe-global/safe-eth-py


text:
Simplification of cell type calling

Cell type and subtype calling is currently a bit cumbersome and should be simplified. Current syntax:
# processing and recomputing quantification
ds_processed = ds.pp[channels].pp.threshold(quantiles).pp.apply(medfilt2d, kernel_size=3).pp.add_quantification().pp.transform_expression_matrix(method='arcsinh')

# predicting major cell types
ds_with_ct_predictions = ds_processed.la.predict_cell_types_argmax(ct_marker_dict, key='_intensity', overwrite_existing_labels=True)

# merging processed image with segmentation etc.
# thresholding specific markers and adding the final labels

There are a couple of things that could be simplified here:

add a channel argument to pp.threshold. This way, we can still threshold selected channels, and simply threshold non-listed channels at 0. This removes the step of having one thresholded and one non-thresholded object.
a hierarchical, all-in-one approach to cell type and subtype classification. This could for example look like this:

# predicting major cell types
ct_marker_dict = {'B': 'PAX5', 'T': 'CD3', 'Myeloid': 'CD11b', 'Dendritic': 'CD11c', 'Granulo': 'CD15', 'Macro': 'CD68', 'Stroma PDPN': 'Podoplanin', 'Stroma CD31': 'CD31', 'Stroma CD34': 'CD34', 'Stroma CD90': 'CD90', 'NK': 'CD56'}
ds = ds.la.predict_cell_types_argmax(ct_marker_dict)

# binarization of markers
# current syntax: ds.pp[marker].pp.threshold(intensity=threshold).pp.add_quantification(func=sp.percentage_positive, key_added='_perc_pos_filtered').la.threshold_labels({marker: perc_pos}, layer_key='_perc_pos_filtered')
ds = ds.pp.binarize(markers, thresholds)

# calling of cell subtypes with a provided hierarchy
subtype_dict = {
    'B': {
        'subtypes': [
            {
                'name': 'B_prol',
                'markers': ['Ki67']
            }
        ]
    },
    'T': {
        'subtypes': [
            {
                'name': 'T_h',
                'markers': ['CD4']
            },
            {
                'name': 'T_tox',
                'markers': ['CD8'],
                'subtypes': [
                    {
                        'name': 'T_tox_naive',
                        'markers': ['CD45RA']
                    },
                    {
                        'name': 'T_tox_mem',
                        'markers': ['CD45RO']
                    }
                ]
            }
        ]
    }
}

ds = ds.la.predict_cell_subtypes(subtype_dict)

Addressed in #99, published with v0.6.0


text:
🛑 Evon Stone Ceramics is down

In e211404, Evon Stone Ceramics (https://evonceramics.com) was down:

HTTP code: 504
Response time: 6913 ms

Resolved: Evon Stone Ceramics is back up in f22e1d6.

repo: sahajananddigital/status


text:
🛑 Evon Stone Ceramics is down

In f4ba9d5, Evon Stone Ceramics (https://evonceramics.com) was down:

HTTP code: 500
Response time: 1349 ms

Resolved: Evon Stone Ceramics is back up in 2459f58 after .


text:
Error when discovery is enabled

Hi.
With discovery enabled I am getting the below error. When I disable discovery the plugin works fine
2019-1-29 20:01:44] [MagicHome-Platform] Discovering Devices                                                                                Error: spawn UNKNOWN                                                                                at _errnoException (util.js:1022:11)                                                                                at ChildProcess.spawn (internal/child_process.js:323:11)                                                                                at exports.spawn (child_process.js:502:9)                                                                                at LightAgent.getDevices (C:\Users\Administrator\AppData\Roaming\npm\node_modules\homebridge-magichome-platform\src\lib\lightAgent.js:143:17)                           at LightAgent.startDiscovery (C:\Users\Administrator\AppData\Roaming\npm\node_modules\homebridge-magichome-platform\src\lib\lightAgent.js:68:12)                        at new MagicHome (C:\Users\Administrator\AppData\Roaming\npm\node_modules\homebridge-magichome-platform\src\magichome.js:37:14)                                         at Server._loadPlatforms (C:\Users\Administrator\AppData\Roaming\npm\node_modules\homebridge\lib\server.js:326:32)                                                      at Server.run (C:\Users\Administrator\AppData\Roaming\npm\node_modules\homebridge\lib\server.js:86:36)                                                                  at module.exports (C:\Users\Administrator\AppData\Roaming\npm\node_modules\homebridge\lib\cli.js:45:10)                                                                 at Object. (C:\Users\Administrator\AppData\Roaming\npm\node_modules\homebridge\bin\homebridge:17:22)  �
Any advice would be appreciated
Thanks

Are you working on windows? I fixed it by changing
this.proc = spawn('python', [cmd, '-s'])

in the lightAgent.js file. I think its because windows doesn't know shebangs like linux does

I'm also on windows and changed the line in lightAgent.js but now am getting this error:
Error: spawn python ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:264:19)
at onErrorNT (internal/child_process.js:456:16)
at processTicksAndRejections (internal/process/task_queues.js:84:9)

Nevermind, got it working. Great plugin

Thank you @FeBe95 .
I was able to edit the lightAgent.js file on my Windows 10 machine and Homebridge now launches without having to set the disableDiscovery to false.

I'm also on windows and changed the line in lightAgent.js but now am getting this error:
Error: spawn python ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:264:19)
at onErrorNT (internal/child_process.js:456:16)
at processTicksAndRejections (internal/process/task_queues.js:84:9)

Sorry, i know this is almost a year later, but what did you do to fix that error?

I'm also on windows and changed the line in lightAgent.js but now am getting this error:
Error: spawn python ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:264:19)
at onErrorNT (internal/child_process.js:456:16)
at processTicksAndRejections (internal/process/task_queues.js:84:9)

sorry for digging this but what did you do to solve that issue?

I'm also on windows and changed the line in lightAgent.js but now am getting this error: Error: spawn python ENOENT at Process.ChildProcess._handle.onexit (internal/child_process.js:264:19) at onErrorNT (internal/child_process.js:456:16) at processTicksAndRejections (internal/process/task_queues.js:84:9)

How did you fix this error, I am getting the same error


text:
🛑 Cerletti Immobilien is down

In 324b542, Cerletti Immobilien (https://www.cerlettimmobilien.ch) was down:

HTTP code: 403
Response time: 122 ms

Resolved: Cerletti Immobilien is back up in eb3e03c.


text:
Remove ingressClassName to use annotation instead

what

Remove ingressClassName in favor of using the annotation

why

The annotation and class name cannot both be used, or the installation will fail on a fresh deployment

/test


text:
defineConfig apiVersion is for some reason not allowed

Not entirely sure why, but apiVersion is not supported:
Argument of type '{ apiVersion: string; title: string; projectId: string; dataset: string; basePath: string; schema: { types: ((Omit<{ type: "object"; groups?: FieldGroupDefinition[] | undefined; ... 12 more ...; fields: ((Omit<...> & ... 1 more ... & FieldDefinitionBase) | ... 1 more ... | (Omit<...> & ... 1 more ... & FieldDefiniti...' is not assignable to parameter of type 'Config<(Omit<{ type: "object"; groups?: FieldGroupDefinition[] | undefined; fieldsets?: FieldsetDefinition[] | undefined; options?: ObjectOptions | undefined; ... 10 more ...; fields: ((Omit<...> & ... 1 more ... & FieldDefinitionBase) | ... 1 more ... | (Omit<...> & ... 1 more ... & FieldDefinitionBase))[]; }, "FIX...'.
  Object literal may only specify known properties, and 'apiVersion' does not exist in type 'Config<(Omit<{ type: "object"; groups?: FieldGroupDefinition[] | undefined; fieldsets?: FieldsetDefinition[] | undefined; options?: ObjectOptions | undefined; ... 10 more ...; fields: ((Omit<...> & ... 1 more ... & FieldDefinitionBase) | ... 1 more ... | (Omit<...> & ... 1 more ... & FieldDefinitionBase))[]; }, "FIX...'.ts(2345)
(property) apiVersion: string

I ended up explicitly casting for now...
const config = defineConfig({
  apiVersion: "2023-06-04",
  title: "myapp",
  projectId: env.NEXT_PUBLIC_SANITY_PROJECT_ID,
  dataset: env.NEXT_PUBLIC_SANITY_DATASET,
  basePath: "/studio",
  schema: { types },
  plugins: [ deskTool(), visionTool({ defaultApiVersion: "2023-06-04" }) ],
} as Parameters<typeof defineConfig>[0]);

I'm not sure how that's solving the problem for you. I'm looking at the types and apiVersion is not part of config:
https://github.com/sanity-io/sanity/blob/v3.12.0/packages/sanity/src/core/config/types.ts
Either way, all I'm doing is passing through defineConfigs parameters through, so whatever parameters it has are because of defineConfig.

Thanks for such a fast response :)
Well its not you. I kinda forgot that Sanity has a tendency to [string, any] all the things... And thus kill off intellisense.

If it’s a field that sanity supports, please make a PR in their repo! @markomitranic

@saiichihashimoto I picked it up from their docs actually as a copypasta. So it most likely is...

authors: markomitranic saiichihashimoto

repo: saiichihashimoto/sanity-typed


text:
fix #1730

Related Issuse

Info about Issue or bug

fix #1730
Describe the changes you've made
A clear and concise description of what you have done to successfully close your assigned issue. Any new files? or anything you feel to let us know!
Checklist:

[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.

Screenshots

@satyampgt4 I have already created this issue and it is merged also Issue Number #1657   PR #1926
@sairish2001

@satyampgt4 I have already created this issue and it is merged also Issue Number #1657 PR #1926
@sairish2001

both are different you version showing result in cartesian  form an this pull request is calculating vector form of projection

@satyampgt4 I have already created this issue and it is merged also Issue Number #1657 PR #1926
@sairish2001

both are different your version showing result in cartesian form and this pull request is calculating vector form of projection
please see the screenshot before concluding anything

Firstly i have not concluded anything and secondly both are calculating vector projection so both can be in one vector projection calculator showing both results


text:
SAK-48998 Footer build info is missing

This fixes SAK-48998. It looks like a previous commit pushed the antrun plugin back to 1.3.
I tested some more and didn't see any issue upgrading everything up to 3.1.0. Everything is building and this fixes the issue.

I tested the ckeditor plugins and config builds as expected.
I was getting an error with pack but I was getting the same error as before. I'm not sure if the error is related to me building in a container or a maven version. I'm guessing it's related to a container build and nothing to do with the plugin and would need adjustment for that. It starts to build but says it can't find the maven repository.
I don't know how/if pack-bin is still used much, maybe for the release? I'll see if I can test that.

repo: sakaiproject/sakai


text:
SAK-50720 Lessons include full archive in CC

This is now ready for review and merging.

@adrianfish  - I agree that tons of this code could be re-written and cleaned up. I kind of shuddered when I used the cover.  But I really don't want to do that in this JIRA.  This JIRA is destined to go back to 23 and 21 and I worry that the more lines I change just for prettiness sake the harder that will be.  I am happy to clean this up in Sakai-25 once the patch makes it successfully back to -23 and -21 and ocne we do the more important work of cleaning up the archive and merge calls.
And if you want to clean things up by rewriting a bunch of code to be equivalent but more elegant code you should not limit this to the (as few as possible) files that I am changing for this as limited as possible in the name of easy back porting change.  So my tendency is to say no to most of this (except for spacing of course).
Over the past two weeks I have looked at a lot of cc / archive / merge code including the code in Site Info / Import from Archive Archive.  It is all complex and obtuse with very weird approaches and implementation patterns.  That is for example why this patch does not try to add this new feature to Site Info / Import from Archive.
I want to get archive and merge working well enough to get the data in and out of Sakai without a complete refactor and kick that large can of worms down the road.

I have copied all the comments to date into the JIRA.  I am about to rebase this and resolve the comments and start a new review thread.

SO I did a quick text back to 23.x and there were three conflicts - easy to resolve.


text:
SAK-33898 - Support SHA265 LTI Launches

This has a test plan - it should go into 12-x and 12.1 once tested and approved but is a new feature not a blocker so should not be in 12.0.

Thans @ottenhoff

Commit message should have been SHA256 :(

authors: csev jonespm


text:
SAK-41858 - Change deleteWhitespace method by regular replace, as del…

…eteWhitespace also deletes newline characters and strip only removes in beginning/end of lines.

Please resolve the conflicts and fix the PR, thanks.

authors: danielmerino mpellicer


text:
Add remote configuration for secure conversations 2.0

Add unified remote configuration for SC 2.0. Related styles are to be added naturally with views that need them.
MOB-3671
What was solved?
Release notes:

[ ] Feature
[x] Ignore
[ ] Release notes (Is it clear from the description here?)
[ ] Migration guide (If changes are needed for integrator already using the SDK - what needs to be communicated? Add underneath please)

Additional info:

[ ] Is the feature sufficiently tested? All tests fixed? Necessary unit, acceptance, snapshots added? Check that at least new public classes & methods are covered with unit tests
[ ] Did you add logging beneficial for troubleshooting of customer issues?
[ ] Did you add new logging? We would like the logging between platforms to be similar. Refer to Logging from iOS SDKs → Things to consider for newly added logs in Confluence for more information.

Screenshots:

You added only new structure, but didn't add it into RemoteConfiguration object and didn't add applying it on top of Theme object. Is it expected?

@EgorovEI  Yes it is expected - this will be added when styles are created. Since styles should be naturally created with view implementation, it does not seem reasonable/obvious to create styles without the views that take advantage of them.

repo: salemove/ios-sdk-widgets


text:
Go/Terraform Integration

@kmcquade thanks for making this tool! I have a use case where Id like to run this through terraform, which currently I basically execute the pull into json and then soup it up, but I was wondering if there was any interest in making this part of a custom provider? This is somewhat a feature request, but due to the fact that its a completely different implementation strategy, feel free to close if you don't find interest in it!

Hey @danquack ! In the meantime, you can find all of the compliance SCPs in the repo here: https://github.com/ScaleSec/terraform_aws_scp/tree/main/compliance_scp
Right now I am manually updating the terraform as this repo is updated but thats not the long-term solution (really not scalable). I actually talked with @kmcquade today about keeping the two repos synced somehow but it may make more sense to add tf to this one.

@jdyke does it make sense to do a web hook trigger from this repo to yours on publish to keep them in sync? Happy to contribute to whatever solution you decide on!

Perhaps we can include Terraform module creation inside this repository, as part of this: https://github.com/salesforce/aws-allowlister/blob/main/Makefile#L60-L61
And the ScaleSec repository can leverage this as a remote Terraform module. Thoughts?

Happy to reference it as a module from terraform_aws_scp -> aws-allowlister, it doesn't make sense to maintain it in two different places. Single source of truth is preferred and this repo is better suited for that.

I was just about to suggest the module approach as well. It will make it easy for anyone to include it in their own code (I know we want to!). The versioning on the module is important so that people don't accidentally have new SCP policy versions.
I would recommend having the module in a separate repo though, as Terraform/Hashi's structure around modules is quite specific and most modules I've ever seen live at the root of their GH repo. Will require syncing through a GH Action on the module repo probably, but easier from a usability perspective. @antonbabenko is an expert in this stuff.

That could make sense. It would have the benefit of clear GitHub issues dedicated to that.

@jdyke @kmcquade If I'm understanding this right, it makes sense to close this issue and open a new one in terraform_aws_scp?

That is desirable from my point of view to keep the repos focused. The terraform repo is strictly for AWS SCPs written in HCL and already has some documentation outlining what they do. In the end it's up to @kmcquade !

I am cool with having this in the Terraform repo under ScaleSec!

authors: danquack jdyke kmcquade yi2020

repo: salesforce/aws-allowlister


text:
git: Strip away the depot path from the beginning of the file path

Let's mimic git-p4.py's behavior for this case

This change will require a re-clone of the entire depot if you are upgrading your p4-fusion version to any version after 1.8.1


text:
fix(list): empty list when no authed orgs are found

What does this PR do?
Fix the list printing empty table when no auth'd orgs are found
What issues does this PR fix or reference?
https://github.com/forcedotcom/cli/issues/1796
As suggested by @cristiand391, I've simply added a check for the length of the array returned by AuthInfo.listAllAuthorizations to avoid relying on the error to be throw thrown.

Merged, thanks @aemounib! :)

Thanks @aemounib! And congrats to Morocco on the World Cup! ⚽ ⚽ ⚽

authors: aemounib cristiand391 cromwellryan

repo: salesforcecli/plugin-auth


text:
🛑 RAÄ Kulturarvsdata Runor is down

In 66244c0, RAÄ Kulturarvsdata Runor (https://kulturarvsdata.se/uu/srdb/fab985d7-61cc-4014-9d85-0a5011d40dc8) was down:

HTTP code: 503
Response time: 558 ms

Resolved: RAÄ Kulturarvsdata Runor is back up in 137e969 after 8 minutes.


text:
Update to cursive 0.17

The version of rust_sodium from crates.io links to an old version of
lazy_static, incompatible with what Cursive 0.17 requires (through
crossbeam).
The git repository has been updated (for almost 2 years now), but that
has not been pushed to crates.io.
This PR updates Cargo.toml to point to the git repo of rust-sodium.
That being said, this particular repository appears abandoned.
The link to SubSpace included in the repo is dead as well.

Hi, I just merged #74, which replaces rust_sodium with crates from the RustCrypto ecosystem. The rust_sodium crate is dead, which caused a lot of maintenance issues in this project as well. I hope this will now become easier, especially since no more C dependencies are included.
Would you like to rebase your PR?

Rebased :)

Great, thanks!
There was a CI mis-configuration that should now be fixed, I'll amend your commit to trigger CI.

Huh, I have no idea what just happened, I just tried to push an update to your branch 😕
I'll cherry-pick it onto a new PR, sorry about that.

I'll cherry-pick it onto a new PR, sorry about that.

Done in #77.

authors: gyscos threema-danilo

repo: saltyrtc/saltyrtc-client-rs


text:
refactor(plasma-web/plasma-b2c): move common code to plasma-hope

:baby_chick: Download canary assets:
colors--canary.324.4164905653.xml
color_metro_ios-swift--canary.324.4164905653.swift
color_metro_kotlin--canary.324.4164905653.kt
color_metro_react-native--canary.324.4164905653.ts
color_sbermarket_ios-swift--canary.324.4164905653.swift
color_sbermarket_kotlin--canary.324.4164905653.kt
color_sbermarket_react-native--canary.324.4164905653.ts
color_sberprime_ios-swift--canary.324.4164905653.swift
color_sberprime_kotlin--canary.324.4164905653.kt
color_sberprime_react-native--canary.324.4164905653.ts
color_selgros_ios-swift--canary.324.4164905653.swift
color_selgros_kotlin--canary.324.4164905653.kt
color_selgros_react-native--canary.324.4164905653.ts
color_smbusiness_ios-swift--canary.324.4164905653.swift
color_smbusiness_kotlin--canary.324.4164905653.kt
color_smbusiness_react-native--canary.324.4164905653.ts
PlasmaTokensColor--canary.324.4164905653.swift
shadow_sbermarket_react-native--canary.324.4164905653.ts
typo_mage_ios-swift--canary.324.4164905653.swift
typo_mage_kotlin--canary.324.4164905653.kt
typo_mage_react-native--canary.324.4164905653.ts
typo_plasma_ios-swift--canary.324.4164905653.swift
typo_plasma_kotlin--canary.324.4164905653.kt
typo_plasma_react-native--canary.324.4164905653.ts
typo_ruler_ios-swift--canary.324.4164905653.swift
typo_ruler_kotlin--canary.324.4164905653.kt
typo_ruler_react-native--canary.324.4164905653.ts
typo_sage_ios-swift--canary.324.4164905653.swift
typo_sage_kotlin--canary.324.4164905653.kt
typo_sage_react-native--canary.324.4164905653.ts
typo_sbermarket_ios-swift--canary.324.4164905653.swift
typo_sbermarket_kotlin--canary.324.4164905653.kt
typo_sbermarket_react-native--canary.324.4164905653.ts
typo_soulmate_ios-swift--canary.324.4164905653.swift
typo_soulmate_kotlin--canary.324.4164905653.kt
typo_soulmate_react-native--canary.324.4164905653.ts

📦 Published PR as canary version: Canary Versions

:sparkles: Test out this PR locally via:
npm install @salutejs/plasma-b2c@1.137.2-canary.324.4164905653.0
npm install @salutejs/plasma-hope@0.0.1-canary.324.4164905653.0
npm install @salutejs/plasma-web@1.163.1-canary.324.4164905653.0
# or
yarn add @salutejs/plasma-b2c@1.137.2-canary.324.4164905653.0
yarn add @salutejs/plasma-hope@0.0.1-canary.324.4164905653.0
yarn add @salutejs/plasma-web@1.163.1-canary.324.4164905653.0

Component performance testing
Result: 🌚 Missing base report
Check out current report in job artifacts!

Component performance testing
Result: 🌚 Missing base report
Check out current report in job artifacts!

Theme Builder app deployed!
http://plasma.sberdevices.ru/pr/plasma-theme-builder-pr-324/

Theme Builder app deployed!
http://plasma.sberdevices.ru/pr/plasma-theme-builder-pr-324/

Component performance testing
Result: 💀 Missing report, something went wrong
Check out current report in job artifacts!

Theme Builder app deployed!
http://plasma.sberdevices.ru/pr/plasma-theme-builder-pr-324/

Component performance testing
Result: 🌚 Missing base report
Check out current report in job artifacts!

Theme Builder app deployed!
http://plasma.sberdevices.ru/pr/plasma-theme-builder-pr-324/

Theme Builder app deployed!
http://plasma.sberdevices.ru/pr/plasma-theme-builder-pr-324/

Component performance testing
Result: 🌚 Missing base report
Check out current report in job artifacts!

Theme Builder app deployed!
http://plasma.sberdevices.ru/pr/plasma-theme-builder-pr-324/

Component performance testing
Result: 💀 Missing report, something went wrong
Check out current report in job artifacts!

Theme Builder app deployed!
http://plasma.sberdevices.ru/pr/plasma-theme-builder-pr-324/

Component performance testing
Result: 💀 Missing report, something went wrong
Check out current report in job artifacts!

Theme Builder app deployed!
http://plasma.sberdevices.ru/pr/plasma-theme-builder-pr-324/

Component performance testing
Result: 💀 Missing report, something went wrong
Check out current report in job artifacts!

Theme Builder app deployed!
http://plasma.sberdevices.ru/pr/plasma-theme-builder-pr-324/

Demo canvas app deployed!
http://plasma.sberdevices.ru/pr/demo-canvas-app-pr-324/

Component performance testing
Result: 💀 Missing report, something went wrong
Check out current report in job artifacts!

Theme Builder app deployed!
http://plasma.sberdevices.ru/pr/plasma-theme-builder-pr-324/

Demo canvas app deployed!
http://plasma.sberdevices.ru/pr/demo-canvas-app-pr-324/

Documentation preview deployed!
website: http://plasma.sberdevices.ru/pr/pr-324/
ui storybook: http://plasma.sberdevices.ru/pr/pr-324/ui-storybook/
web storybook: http://plasma.sberdevices.ru/pr/pr-324/web-storybook/
b2c storybook: http://plasma.sberdevices.ru/pr/pr-324/b2c-storybook/
temple storybook: http://plasma.sberdevices.ru/pr/pr-324/temple-storybook/

Theme Builder app deployed!
http://plasma.sberdevices.ru/pr/plasma-theme-builder-pr-324/

Component performance testing
Result: 🌚 Missing base report
Check out current report in job artifacts!

Theme Builder app deployed!
http://plasma.sberdevices.ru/pr/plasma-theme-builder-pr-324/

Demo canvas app deployed!
http://plasma.sberdevices.ru/pr/demo-canvas-app-pr-324/

Component performance testing
Result: 🟢 Success
Check out comparison report in job artifacts!

Documentation preview deployed!
website: http://plasma.sberdevices.ru/pr/pr-324/
ui storybook: http://plasma.sberdevices.ru/pr/pr-324/ui-storybook/
web storybook: http://plasma.sberdevices.ru/pr/pr-324/web-storybook/
b2c storybook: http://plasma.sberdevices.ru/pr/pr-324/b2c-storybook/
temple storybook: http://plasma.sberdevices.ru/pr/pr-324/temple-storybook/

Theme Builder app deployed!
http://plasma.sberdevices.ru/pr/plasma-theme-builder-pr-324/

Demo canvas app deployed!
http://plasma.sberdevices.ru/pr/demo-canvas-app-pr-324/

Documentation preview deployed!
website: http://plasma.sberdevices.ru/pr/pr-324/
ui storybook: http://plasma.sberdevices.ru/pr/pr-324/ui-storybook/
web storybook: http://plasma.sberdevices.ru/pr/pr-324/web-storybook/
b2c storybook: http://plasma.sberdevices.ru/pr/pr-324/b2c-storybook/
temple storybook: http://plasma.sberdevices.ru/pr/pr-324/temple-storybook/

Component performance testing
Result: 🟢 Success
Check out comparison report in job artifacts!

authors: Salute-Eva Yeti-or

repo: salute-developers/plasma


text:
Updated Dockerfile removed old hacks

The hacks arn't needed any more ubuntu fixed it in its apt-get as also docker applyed some to the base ubuntu image that your using. You get now better results without that i think it will not brake any existing img i am near 100% sure!

@frank-dspeed can you please point me to the configuration where install-recommends and install-suggests is disabled by default?

@frank-dspeed I tested apt-get behaviour with the latest ubuntu:14.04 image and found that install-recommends is enabled by default. Following is a test
default behaviour
docker run -it --rm ubuntu:14.04 bash
apt-get update && apt-get install postgresql
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  krb5-locales libasn1-8-heimdal libedit2 libgssapi-krb5-2 libgssapi3-heimdal
  libhcrypto4-heimdal libheimbase1-heimdal libheimntlm0-heimdal
  libhx509-5-heimdal libk5crypto3 libkeyutils1 libkrb5-26-heimdal libkrb5-3
  libkrb5support0 libldap-2.4-2 libpq5 libroken18-heimdal libsasl2-2
  libsasl2-modules libsasl2-modules-db libwind0-heimdal libxml2 openssl
  postgresql-9.3 postgresql-client-9.3 postgresql-client-common
  postgresql-common sgml-base ssl-cert xml-core
Suggested packages:
  krb5-doc krb5-user libsasl2-modules-otp libsasl2-modules-ldap
  libsasl2-modules-sql libsasl2-modules-gssapi-mit
  libsasl2-modules-gssapi-heimdal ca-certificates oidentd ident-server
  locales-all postgresql-doc-9.3 sgml-base-doc openssl-blacklist debhelper
The following NEW packages will be installed:
  krb5-locales libasn1-8-heimdal libedit2 libgssapi-krb5-2 libgssapi3-heimdal
  libhcrypto4-heimdal libheimbase1-heimdal libheimntlm0-heimdal
  libhx509-5-heimdal libk5crypto3 libkeyutils1 libkrb5-26-heimdal libkrb5-3
  libkrb5support0 libldap-2.4-2 libpq5 libroken18-heimdal libsasl2-2
  libsasl2-modules libsasl2-modules-db libwind0-heimdal libxml2 openssl
  postgresql postgresql-9.3 postgresql-client-9.3 postgresql-client-common
  postgresql-common sgml-base ssl-cert xml-core
0 upgraded, 31 newly installed, 0 to remove and 6 not upgraded.
Need to get 6439 kB of archives.
After this operation, 27.8 MB of additional disk space will be used.
Do you want to continue? [Y/n]

with -no-install-recommends
docker run -it --rm ubuntu:14.04 bash
apt-get update && apt-get install --no-install-recommends postgresql
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  libasn1-8-heimdal libedit2 libgssapi-krb5-2 libgssapi3-heimdal
  libhcrypto4-heimdal libheimbase1-heimdal libheimntlm0-heimdal
  libhx509-5-heimdal libk5crypto3 libkeyutils1 libkrb5-26-heimdal libkrb5-3
  libkrb5support0 libldap-2.4-2 libpq5 libroken18-heimdal libsasl2-2
  libsasl2-modules-db libwind0-heimdal libxml2 openssl postgresql-9.3
  postgresql-client-9.3 postgresql-client-common postgresql-common ssl-cert
Suggested packages:
  krb5-doc krb5-user ca-certificates oidentd ident-server locales-all
  postgresql-doc-9.3 openssl-blacklist
Recommended packages:
  krb5-locales libsasl2-modules xml-core
The following NEW packages will be installed:
  libasn1-8-heimdal libedit2 libgssapi-krb5-2 libgssapi3-heimdal
  libhcrypto4-heimdal libheimbase1-heimdal libheimntlm0-heimdal
  libhx509-5-heimdal libk5crypto3 libkeyutils1 libkrb5-26-heimdal libkrb5-3
  libkrb5support0 libldap-2.4-2 libpq5 libroken18-heimdal libsasl2-2
  libsasl2-modules-db libwind0-heimdal libxml2 openssl postgresql
  postgresql-9.3 postgresql-client-9.3 postgresql-client-common
  postgresql-common ssl-cert
0 upgraded, 27 newly installed, 0 to remove and 6 not upgraded.
Need to get 6325 kB of archives.
After this operation, 24.6 MB of additional disk space will be used.
Do you want to continue? [Y/n]

You can see that in the default behaviour the additional packages krb5-locales libsasl2-modules xml-core are also installed.

authors: frank-dspeed sameersbn

repo: sameersbn/docker-ubuntu


text:
typo

evlauation -> evaluation

Looks good, thanks!

authors: nakosung samjabrahams


text:
🛑 HostNoc is down

In 289d236, HostNoc (https://www.hostnoc.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: HostNoc is back up in 089cbe9 after 5 minutes.

repo: sammaryasir/host


text:
Transparently handle session terminations during long-polling between Proxy and Broker

If the long-polling of tasks or results is disrupted by session terminations (e.g. caused by latency spikes), the proxy client is not informed of that connection loss. An alternative, transparent long-polling mechanism could look like the following:
The long polling wait_time is set as a maximum wait time. If no wait_time is given, a sensible default cap is chosen (e.g. 1 minute). The proxy chooses a lower wait time for repeated long-polls to the broker, up to the chosen maximum time. The timeout for that connection is chosen using a learning mechanism analyzing previous requests (and optionally an echo endpoint in the broker) and converging to an optimal time.
In case of a fast, unimpeded connection, the result is returned – as expected by the application – as fast as it is available in the broker or at least partially after wait_count. In case of a broken session, the connection is transparently reinitialized by the proxy.

Check if this is still required with the SSE interface #105

authors: TKussel lablans

repo: samply/beam


text:
Extension should be .trump

Trump loves his name to be stamped everywhere.

I propose .djt (Donald J Trump).
True conservatives hold to three-character extensions. It’s like in golf. A lot of people  -  I don’t want this to sound trivial -  but a lot of people are switching to these really long putters, very unattractive. It’s weird. You see these great players with these really long putters, because they can’t sink three-footers anymore. And, I hate it. I am a traditionalist. I have so many fabulous friends who happen to use four-character extensions, but I am a traditionalist.

I think the canonical way would be all-caps surname-only. .TRUMP, like constants.
Small caps may not carry enough power.
A more archaic mode could probably be activated with a .Drumph extension (see https://youtu.be/DnpO_RTSNmQ).

The extension doesn't matter,  nothing checks it

.trump, like it

See a76f078

authors: CryoBrown StevenGann eamanu nazieb samshadwell ssaavedra

repo: samshadwell/TrumpScript


text:
mount files specified in command line arguments

Note: Please file issues for subcomponents under the appropriate repo

Component
Repo

kraken-lib
samsung-cnct/kraken-lib

kraken-charts
samsung-cnct/k2-charts

kraken-tools
samsung-cnct/kraken-tools

What keywords did you search in Kraken issues before filing this one? (If you have found any duplicates, you should instead reply there.): kubectl

Is this a BUG REPORT or FEATURE REQUEST? (choose one): feature request

if I run kraken tool kubectl apply -f <some arbitrary file path> I expect this to work.  Currently, the command line path isn't being parsed for files to mount into the running kraken-lib container.
Kraken version (use kraken version): 1.2.1
Environment: darwin
Please be sure not to submit any confidential information (e.g. ssh keys, provider secrets, etc.) as issues are publicly accessible.

Environment variables (e.g. env | grep 'KRAKEN_):
**Configuration files (~/.kraken/config.yaml or the file passed to kraken --config) **:
Others:

What happened:
kubectl failed because kubectl couldn't find the file
What you expected to happen:
kubectl call to succeed because it could find the file
How to reproduce it (as minimally and precisely as possible):
run the above command
Anything else we need to know:

interesting point. So, I'm not sure which approach is best but here are some possible ways to do this, and im not saying these are the only ways:

Create new flag that points to the location of files to mount for deployment
Override the kubectl apply function and then parse out the -f (but must then pass to kubectl)
parse argument (get command and flags and arugment) to then mount the requested volume.

Either way the functionality to mount additional volumes exists not in kraken, so its a matter of determining what is the best approach.

my preference is to parse the command line and mount that directory/file much like we already do for the config file.  it seems to be consistent with how we do things and means we don't have to do much with arg mangling for kubectl

authors: alejandroEsc coffeepac

repo: samsung-cnct/kraken


text:
Build PyPy wheels for Linux and macOS

Upgrade maturin to 0.13.0
Build PyPy wheels for Linux and macOS

Build PyPy wheels for Windows is possible but it will need to install PyPy beforehand since you need to link to a dll or dll import library on Windows. I'll investigate that later to keep this one simpler.
PyPy 3.7 has some tests timeout so I did not add it.

thanks so much.

authors: messense samuelcolvin

repo: samuelcolvin/watchfiles


text:
Make linted paths implicit for RuboCop

This is split from #21.

Thanks!

authors: dorner samuelmeuli

repo: samuelmeuli/lint-action


text:
Undefined steps when running gradle cucumber

Referenced from #27 https://github.com/samueltbrown/gradle-cucumber-plugin/issues/27#issuecomment-294860608 as it is closed.

Hi @viphe I am also having the similar problem when I used gradle cucumber it complained steps are undefined. I am using cucumber-jvm with scala. I am using this plugin version 0.9, cucumber version is 1.2.5 and my gradle version is 3.5. I added the glueDirs as classpath: and also hard coded the path but it still says steps are undefined. Any progress on this issue?

cucumber {
  formats = ['pretty','json:build/cucumber.json']
  glueDirs = ['classpath:step_definition_package_name']
  featureDirs = ['path_to_feature']
  tags = ['@wip']
  monochrome = false
  strict = false
  dryRun = false
  ignoreFailures = false
  jvmOptions {}
}

When I added a task as below in build.gradlew file and ran with new task, the tests run
task cucumber12(type: JavaExec, dependsOn: assemble ) {
  main = "cucumber.api.cli.Main"
  classpath = configurations.cucumberRuntime + sourceSets.main.output + sourceSets.test.output
  args = ['-f', 'json:build/reports/cucumber/cucumber.json', '--glue', 'step_definition_package_name', 'path_to_feature']
}

Why I am not able to use this plugin but able to run via new task added?

Same here. Is not able to find my Java step definitions.
I have step definitions in
src/test/java/com/myapp/test/cucumber/StepDefs.java"

and the feature file in
src/test/resources/com/myapp/test/cucumber/test.feature

When I run the task it finds the feature, but says all the steps are uninplemented.
If I run using the JUnit test runner, it finds the steps without any problems and executes the BDD correctly.
My config
cucumber {
    formats = ['pretty','junit:build/cucumber.xml']
    glueDirs = ['src/test/java']
    featureDirs = ['src/test/resources']
    tags = []
    monochrome = false
    strict = false
    dryRun = false
    ignoreFailures = false

    jvmOptions {
        maxHeapSize = '512m'
    }
}

As soon as I upgraded from gradle 2.8 to 4.3, the step definitions are not being recognized.
tasks.cucumber {
formats = ['pretty', 'json:build/cucumber-tests/cucumber.json', 'html:build/cucumber-tests/cucumber_results.html']
}

I know that this is an old thread, but I also had a problem running the cucumber gradle task...
task cucumber() {
    dependsOn assemble
    doLast {
        javaexec {
            main = "io.cucumber.core.cli.Main"
            classpath = configurations.cucumberRuntime + sourceSets.main.output + sourceSets.test.output
            args = ['--plugin', 'pretty', '--glue', 'hellocucumber', 'src/test/resources']
        }
    }
}

the --glue switch in this gradle task arguments is what I had to change to fix the issue. I changed "hellocucumber" to the correct package name I'm using in my project...I hope it helps someone who finds this thread in the future.

I was having the same issue I had to put the full package path instead of just "hellocucumber" ' so at the end --glue', 'com/jmconsultant/hellocucumber'

authors: bindulaxminarayan jacek99 jdmesalosada poornima-ns

repo: samueltbrown/gradle-cucumber-plugin


text:
Don't include item and itemScope in collection component

Fixes an error when trying to print the full collection into console or trying to use the for ... of construct.
The problem was that we were generating an invalid component item inside the collection component that was throwing an Element not found error when inspected. By removing this invalid element, the collection component can be inspected safely.
Fixes #196

👍

@san650 thanks for contibuting, this is included on v1.4.1