Minecraft build fails with Execution failed for task ':deobfMcMCP'.

On macOS 10.12.3 followng ./launchClient.sh:
:deobfMcMCP FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':deobfMcMCP'.
> Your Access Transformers be broke!

Can you check if there's any error reported before this message? In my case there was a failure related to outdated Java3D library (default in osx is 1.3 but it requires 1.5 to work properly because of this function here http://download.java.net/media/java3d/javadoc/1.5.0/javax/vecmath/Tuple4f.html#getW()).
Check here how to upgrade it http://stackoverflow.com/questions/12787476/how-to-install-java-3d-on-mac

As @ptigas says, we need to see the rest of the error message. The "Access Transformers be broke!" error is a catch-all response for any problems with the deobfuscation process - there are several different errors that can cause this, including the vecmath problem mentioned above. Can you give us any more information?

Am closing this due to inactivity, but if it's still a problem please re-open and provide us with some more details so we can help fix it.
Cheers!


Ignore top cmps

Task/Issue URL:
Description
Steps to test this PR
Feature 1

[ ]
[ ]

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

Current dependencies on/for this PR:

develop

PR #2128

PR #2129
PR #2155
PR #2178
PR #2181   👈

This comment was auto-generated by Graphite.


[WIP][HIVEMALL-124][BUGFIX] Fixed bugs in BinaryResponseMeasure (nDCG, MRR, AP)

What changes were proposed in this pull request?
Fixed bug in the BinaryResponse measure such as nDCG, MRR, (M)AP.
What type of PR is it?
Bug Fix
What is the Jira issue?
https://issues.apache.org/jira/browse/HIVEMALL-124
How was this patch tested?
unit tests, manual tests
Checklist

[x] Did you apply source code formatter, i.e., mvn formatter:format, for your commit?
[ ] Did you run manual test on Hive/Spark CLI on the modified functions?

Coverage decreased (-0.05%) to 40.928% when pulling bef36ed9dd4bcd11bd46c156d85e8b2006d3811d on myui:HIVEMALL-124 into 06f2f822008de1990948ffdd81022910e987d548 on apache:master.

@takuti could you review this PR?

Coverage decreased (-0.05%) to 40.926% when pulling eb0cb36ba3cef9a850eea0ec25265924df26a659 on myui:HIVEMALL-124 into 06f2f822008de1990948ffdd81022910e987d548 on apache:master.

Ideally, it should be ndcg(array(1,3), array(1)) < ndcg(array(1), array(1)) but correct code return 1.0 for both cases.

Coverage decreased (-0.05%) to 40.926% when pulling cd5cb4ad8ec7954e3e60cf04aa05a209f1d34557 on myui:HIVEMALL-124 into 06f2f822008de1990948ffdd81022910e987d548 on apache:master.

Coverage decreased (-0.04%) to 40.929% when pulling d70c072f97e882ce36f950798182aefa086efb53 on myui:HIVEMALL-124 into 06f2f822008de1990948ffdd81022910e987d548 on apache:master.


[GLUTEN-5620][CORE] Simplify Decimal process logic

What changes were proposed in this pull request?
This PR trys to unify decimal process logic for https://github.com/apache/spark/pull/36698.

Before 36698
After 36698

PromotePrecision
Actually, it is a placeholder, it dose nothing at runtime.
Removed

CheckOverflow
It calls Decimal::toPrecision to change decimal's type to result type.
Merge Decimal::toPrecision into arithmetic eval and code-gen code path, and still use it in RowEncoder

Add, Divide,  Multiply, etc.
dataType is  not actual result type.
dataType is  actual result type.

How

Don't transform CheckOverflow when its child is decimal BinaryArithmetic in ExpressionConverter:

case CheckOverflow(b: BinaryArithmetic, decimalType, _)
    if DecimalArithmeticUtil.isDecimalArithmetic(
      b) && BackendsApiManager.getSettings.noCheckOverflow =>
  DecimalArithmeticUtil.checkAllowDecimalArithmetic()
  val leftChild =
    replaceWithExpressionTransformerInternal(b.left, attributeSeq, expressionsMap)
  val rightChild =
    replaceWithExpressionTransformerInternal(b.right, attributeSeq, expressionsMap)
  DecimalArithmeticExpressionTransformer(
    getAdnCheckSubstraitName(b, expressionsMap),
    leftChild,
    rightChild,
    decimalType,
    b)

Automatically add native  CheckOverflow  when doing decimal BinaryArithmetic at backend, see FunctionParserBinaryArithmetic::parese

The current PR make ExpressionConverter a bit complicated by introducing BackendSettingsApi::noCheckOverflow, which is for the compatibility of the velox backed.
Hope we can remove this configuration and make code more clean, once velox has same logic. For example, we can remove DecimalArithmeticUtil::getResultTypeForOperation, since we can get it  either from CheckOverflow or decimal arithmetic expression itself.
          val resultType = DecimalArithmeticUtil.getResultTypeForOperation(
            DecimalArithmeticUtil.getOperationType(b),
            DecimalArithmeticUtil
              .getResultType(leftChild)
              .getOrElse(left.dataType.asInstanceOf[DecimalType]),
            DecimalArithmeticUtil
              .getResultType(rightChild)
              .getOrElse(right.dataType.asInstanceOf[DecimalType])
          )

(Fixes: #5620)
How was this patch tested?
Existed UT

LGTM

@jinchengchenghh can you please help to take a look on this patch?

/Benchmark Velox

===== Performance report for TPCH SF2000 with Velox backend, for reference only ====

query
log/native_5621_time.csv
log/native_master_05_06_2024_72e787c64_time.csv
difference
percentage

q1
37.27
36.58
-0.695
98.14%

q2
23.85
23.74
-0.115
99.52%

q3
38.43
38.97
0.534
101.39%

q4
38.61
38.09
-0.517
98.66%

q5
69.84
68.56
-1.278
98.17%

q6
7.14
6.78
-0.353
95.06%

q7
81.96
83.29
1.335
101.63%

q8
83.23
87.34
4.111
104.94%

q9
121.14
122.36
1.221
101.01%

q10
45.86
46.26
0.408
100.89%

q11
20.29
20.36
0.063
100.31%

q12
29.88
27.48
-2.402
91.96%

q13
54.40
54.80
0.407
100.75%

q14
19.12
20.20
1.081
105.66%

q15
30.78
30.34
-0.444
98.56%

q16
13.69
15.88
2.190
116.00%

q17
102.62
101.90
-0.720
99.30%

q18
145.94
146.06
0.117
100.08%

q19
15.85
14.65
-1.196
92.46%

q20
26.33
26.35
0.013
100.05%

q21
283.57
291.97
8.394
102.96%

q22
17.08
15.01
-2.072
87.87%

total
1306.90
1316.98
10.082
100.77%

For velox backend, it check overflow in native binary arithmetic too, can you try to change the code to not transform checkoverflow?

I think we can also remove getResultTypeForOperation

For velox backend, it check overflow in native binary arithmetic too, can you try to change the code to not transform checkoverflow?

@jinchengchenghh would you please create followup pr to remove  transformCheckOverflow option?  I add this option for the compatibility, I am not familiar with velox backend.

ok @baibaichen


reflect: Value.Call panic on nil T interface assignable to R interface

I'm investing a bug report and I traced it down to the following discrepancy, and I've convinced myself that it is a bug, but would appreciate a 2nd opinion.
Consider the following snippet:
type Iface interface {
	Method()
}
type IfaceAlt interface {
	Method()
}

func Func(Iface) bool {
	return true
}

func main() {
	sa := struct{ X Iface }{}

	v1a := sa.X
	fmt.Println(Func(v1a))

	v2a := reflect.ValueOf(sa).FieldByName("X")
	fmt.Println(reflect.ValueOf(Func).Call([]reflect.Value{v2a})[0])

	sb := struct{ X IfaceAlt }{}

	v1b := sb.X
	fmt.Println(Func(v1b))

	v2b := reflect.ValueOf(sb).FieldByName("X")
	fmt.Println(reflect.ValueOf(Func).Call([]reflect.Value{v2b})[0])
}

We have two interfaces Iface and IfaceAlt, which are defined the exact same way.
We also have a function Func that takes Iface as an input and always reports true.
Since both interfaces are assignable to each other, we expect that you should be able to call Func with values of either type.
The sa and sb variables are structs where the X field is of type Iface or IfaceAlt.
v1a and v2a shows that you can call Func directly in Go and also with reflection.
v1b and v2b shows that you can still call Func directly in Go, but the equivalent call with reflect panics with: interface conversion: interface is nil, not main.Iface
What I expected:
true
true
true
true

What I saw instead:
true
true
true
panic: interface conversion: interface is nil, not main.Iface

\cc @ianlancetaylor @mdempsky

It's an interesting case.  I do think it's a bug.  The reflect package is trying to handle Call as it does any assignment: when assigning a value to a variable of interface type, it converts the value to an empty interface and does the assignment.  That works fine except when the value happens to itself be a nil interface.  When the value is a nil interface, converting to an empty interface produces simply the nil empty interface, and that can not be assigned to any non-empty interface.
I think we need to change assignTo to specially handle the case of assigning one interface type to another, much as there is a test for src.Kind() == Interface in convertOp.

Does this affect both gc and gccgo compilers (if it's easy to find out)?

@shurcooL Yes, it affects both compilers.  I believe the key code here is reflect.Value.assignTo, which is the same for both compilers.


format string by tuple

i think this is would be useful
crystal eval 'p "%d-%d" % {1, 2}'

seems this is fixed in master


FeignClient send post request instead of get

I use spring cloud version 2021.0.3 also tried to use version 2021.0.4
I have FeignClient "DigitalCashTokenFeign" and I'm trying to send a request to my other service
Example:
@FeignClient(
    value = "digital-cash",
    primary = false,
)
interface DigitalCashTokenFeign {
    @GetMapping("/digital-cash/internal/api/v1/digital/token/{deviceId}")
    fun getDigitalCashToken(@PathVariable deviceId: String): ResponseEntity<String>
}

Also i tried use (@PathVariable("deviceId") deviceId: String) but nothing has changed
when calling this method i get service side error:
2023-02-16 21:29:56.360  WARN [digital-cash,faee331c0ae7e791,8389463eec20bd06] 44424 --- [nio-9876-exec-4] .w.s.m.s.DefaultHandlerExceptionResolver : Resolved [org.springframework.web.HttpRequestMethodNotSupportedException: Request method 'POST' not supported]
and accordingly in my service I get the error
[Request processing failed; nested exception is feign.FeignException$MethodNotAllowed: [405] during [GET] to [http://digital-cash/digital-cash/internal/api/v1/digital/token/211671606232197] [DigitalCashTokenFeign#getDigitalCashToken(String)]: [{"timestamp":1676564996373,"status":405,"error":"Method Not Allowed","path":"/digital-cash/internal/api/v1/digital/token/211671606232197"}]] with root cause

Hello @Fortage, we haven't really introduced dedicated support for Kotlin. Are you experiencing the same issue if you rewrite this code to Java? If yes, please provide a minimal, complete, verifiable example that reproduces the issue.

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

I think nothing is wrong with Feign itself. I faced a similar problem, although with a complex Object as the parameter. I successfully solved it, by recognizing:

If one does not specify @SpringQueryMap beside @Parameter, Feign converts the parameter object to a json and puts it to the body of the request.
Since GET requests with body are not really conform to http standards, the default http client used by Feign automatically converts the GET to POST. This, however can be worked around: if one adds Apache Http client 5 as dependency to the project, Feign will use it automatically instead of the java.net.http.HttpClient. And Apache's client does not changes the method, so it will stay GET. (Please note that the parameter object will still travel in the body as a json.)
Simply put this to your pom.xml:

		<dependency>
			<groupId>io.github.openfeign</groupId>
			<artifactId>feign-hc5</artifactId>
		</dependency>

Spring Boot's autoconfigure feature will handle the rest.
I know this is not exactly the situation you are facing, but I hope this information might help you to search for the cause of your problem at the right place.

Thanks for your comment @gviczai! It helps me a lot!
Where do you find this kind of information for my personal culture?

@gviczai
Previously I was also facing same issue. GET request is automatically converting into POST request and downstream application throwing error like POST not supported.
Then adding this dependency
		<dependency> 			<groupId>io.github.openfeign</groupId> 			<artifactId>feign-hc5</artifactId> 		</dependency>
I am not able to get proper request at down stream application. Thanks a lot.

@gviczai In my case this was my problem.
I signed in just to say thank you, you saved me.


Balder/reply in own thread

@vekterli PR Only the second commit has sematics.

Closing as it has been applied to master in smaller bits.


gitnuro: add aarch64-linux support

Description of changes
Add support for aarch64-linux, as already discussed here.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@pbsds we already talked about these changes, could you review this?

@ofborg build gitnuro
@ofborg eval

Please squash the commits

Done @pbsds

This and earlier commits should be eligible for stable, could you backport this @julius-boettger?

This and earlier commits should be eligible for stable, could you backport this @julius-boettger?

I have never done that before, can you link me to a guide on how to do that? I also don't have much time right now, so if someone else could do it instead of me, I would also appreciate it.

Backporting involves cherry picking commits from master branch (obviously PRs need to be merged first) into one of supported release branches. Current release is 24.05, so one should clone release-24.05 branch and make a PR to that branch with the cherry picked changes.
Guide is here.
In this particular case, commit from this PR and https://github.com/NixOS/nixpkgs/pull/278514 are to be cherry-picked.
Automatic backport (can only be done by a maintainer) failed because the earlier change has not been backported yet.


Suggestion: Add more default search paths

Suggestion to add more default search paths now that multiple can be added.
For example: C:\Program Files\Zulu on windows, but there are certainly more, for adopt open jdk etc.

Yes that's right, there are more distribution dependent paths but I won't add them all because this is already a mess on Windows but it gets even worse when using tools like sdkman etc. It's maybe a good practice to keep the installed JDKs in one place if possible and if not simply add the folders to the search path. This only has to be done once for each folder which should be ok.

Sure it can be done, but for user conveience it's a very nice experience when you launch the app and all the different jdks are just there out of the box.
Having all different jdks in one place is not really an option as most people just use the defaults when installing them.
Maybe add a separate text file for each platform (windows, mac, linux) with locations to check and loop through them?


Sudoku_Solver

Submission Title
Sudoku_Solver
Submission Type
Algorithm
Folder Related To
Algorithm => Dynamic_Programming => Sudoku_Solver => File.ext
Contributors

[x]  C++ -
[x]  C -
[x]  Python -
[x] Java -
[x] JavaScript -
[ ] TypeScript -
[ ] Golang -
[ ] Ruby -
[ ] php -
[ ] Swift -
[ ] C# -

@ahampriyanshu I want to contribute to this in C++. Can you Please assign it to me.

I can contribute in C. Kindly assign this to me.

I can do it in Java .Please assign it to me.

Please Assign It to me in Python

I can contribute to this issue in Python, if assigned. Thanks

Hi @adidesh07 :wave:
Please opt a different language/issue :grin:

I would like to work on this in C++. Can you please assign it to me?

I would like to work on TypeScript please assign this to me

thanks everyone :v:


FLASH_OB_GetRDP has 32-bit return type but HAL_FLASHEx_OBErase implicitly converts it to 8-bits

Describe the set-up

Hardware agnostic (encountered while compiling program for STM32F072)
STM32CubeIDE v1.14.0 (build 19471_20231121_1200 (UTC))

Describe the bug
Compiling stm32f0xx_hal_flash_ex.c results in (conversion related) warnings at build-time like this:
...
arm-none-eabi-gcc "../Drivers/STM32F0xx_HAL_Driver/Src/stm32f0xx_hal_rcc_ex.c" -mcpu=cortex-m0 -std=gnu11 -g3 -DDEBUG -DUSE_HAL_DRIVER -DSTM32F072xB -c -I../Core/Inc -I../Drivers/STM32F0xx_HAL_Driver/Inc -I../Drivers/STM32F0xx_HAL_Driver/Inc/Legacy -I../Drivers/CMSIS/Device/ST/STM32F0xx/Include -I../Drivers/CMSIS/Include -Og -ffunction-sections -fdata-sections -Wall -Wconversion -fstack-usage -fcyclomatic-complexity -MMD -MP -MF"Drivers/STM32F0xx_HAL_Driver/Src/stm32f0xx_hal_rcc_ex.d" -MT"Drivers/STM32F0xx_HAL_Driver/Src/stm32f0xx_hal_rcc_ex.o" --specs=nano.specs -mfloat-abi=soft -mthumb -o "Drivers/STM32F0xx_HAL_Driver/Src/stm32f0xx_hal_rcc_ex.o"
../Drivers/STM32F0xx_HAL_Driver/Src/stm32f0xx_hal_flash_ex.c: In function 'HAL_FLASHEx_OBErase':
../Drivers/STM32F0xx_HAL_Driver/Src/stm32f0xx_hal_flash_ex.c:317:12: warning: conversion from 'uint32_t' {aka 'long unsigned int'} to 'uint8_t' {aka 'unsigned char'} may change value [-Wconversion]
  317 |   rdptmp = FLASH_OB_GetRDP();
      |            ^~~~~~~~~~~~~~~
../Drivers/STM32F0xx_HAL_Driver/Src/stm32f0xx_hal_flash_ex.c: In function 'HAL_FLASHEx_OBGetConfig':
../Drivers/STM32F0xx_HAL_Driver/Src/stm32f0xx_hal_flash_ex.c:449:23: warning: conversion from 'uint32_t' {aka 'long unsigned int'} to 'uint8_t' {aka 'unsigned char'} may change value [-Wconversion]
  449 |   pOBInit->RDPLevel = FLASH_OB_GetRDP();
      |                       ^~~~~~~~~~~~~~~
...
13:52:02 Build Finished. 0 errors, 2 warnings. (took 4s.966ms

How To Reproduce

Application agnostic.
Suspect is HAL (stm32f0xx_hal_flash_ex.c)
No need to make any calls to reproduce -- problem is warning at compile time.
Can reproduce by compiling stm32f0xx_hal_flash_ex.c with conversion warnings enabled.

Additional context
My suggested solution is to simply change the return type from uint32_t to uint8_t since result must be one of OB_RDP_LEVEL_0, OB_RDP_LEVEL_1, or OB_RDP_LEVEL_2
diff --git a/Drivers/STM32F0xx_HAL_Driver/Src/stm32f0xx_hal_flash_ex.c b/Drivers/STM32F0xx_HAL_Driver/Src/stm32f0xx_hal_flash_ex.c
index 7ea91b9..34068c7 100644
--- a/Drivers/STM32F0xx_HAL_Driver/Src/stm32f0xx_hal_flash_ex.c
+++ b/Drivers/STM32F0xx_HAL_Driver/Src/stm32f0xx_hal_flash_ex.c
@@ -102,7 +102,7 @@ static HAL_StatusTypeDef FLASH_OB_RDP_LevelConfig(uint8_t ReadProtectLevel);
 static HAL_StatusTypeDef FLASH_OB_UserConfig(uint8_t UserConfig);
 static HAL_StatusTypeDef FLASH_OB_ProgramData(uint32_t Address, uint8_t Data);
 static uint32_t          FLASH_OB_GetWRP(void);
-static uint32_t          FLASH_OB_GetRDP(void);
+static uint8_t           FLASH_OB_GetRDP(void);
 static uint8_t           FLASH_OB_GetUser(void);

 /**
@@ -899,7 +899,7 @@ static uint32_t FLASH_OB_GetWRP(void)
   *            @arg @ref OB_RDP_LEVEL_1 Read protection of the memory
   *            @arg @ref OB_RDP_LEVEL_2 Full chip protection
   */
-static uint32_t FLASH_OB_GetRDP(void)
+static uint8_t FLASH_OB_GetRDP(void)
 {
   uint32_t tmp_reg;

See also stm32f1xx_hal_driver#7

If changing the signature is too much to ask, perhaps an explicit cast to suppress the warning would be OK?
https://github.com/STMicroelectronics/stm32f0xx_hal_driver/blob/5fd31c52559a593dd9038c4abb4b85faeac728c6/Src/stm32f0xx_hal_flash_ex.c#L317
rdptmp = (uint8_t)FLASH_OB_GetRDP();

Hello @jacobq,
Thank you for your report. We confirm the appearance of warnings by activating -Wconversion warnings. This problem has been reported to our development teams for further analysis. We'll get back to you as soon as we have any updates.
With Regards,


Update and rename zh_cn.guess to zh_cn.lang

Fix #4837

@tyler489
This is not necessary. Minecraft will process all language files into a hashmap, which you can verify by reading the forge document

I had a translation for the base module but i pulled request on my fork...

@fluid-uu-matter I think the site maybe have some help https://cfpa.team


--verbose is still rather taciturn

It'd be nice if --verbose added some more information about progress as the algorithm runs. As it stands, --verbose adds exactly two output lines in the entire program. While the multi-stage nature of the Modisco algorithm means that a progress bar is not very meaningful, I'd like to get updates to know how far the program has gotten, especially when I do something weird and it crashes. Particularly when I'm starting out with a project, I'd like to know if my modisco run is going to take thirty minutes or five hours.
Even if there's not a time estimate, just seeing an occasional
INFO: 2024-01-29 13:38:34 tfmodisco.py:174: Positive seqlets refinement, phase 3/5, round 1/2
in the logs would be nice.
I'm very fond of the logging library in Python, since you just have to configure the logger once and then you don't have to pass a verbose parameter to every function call, but that's definitely personal taste.

Thanks for the suggestion. I agree that this would be useful, but I think it's unlikely that I have time to modify tfmodisco in any way in the near future.


Fix typos when handling CMYK colors in src/core/default_appearance.js

Note how we're accidentally using the wrong operator when trying to parse CMYK colors. I'm not aware of any bugs caused by this, since it seems uncommon in practice for annotations to specify text-colors in CMYK format.

/botio test


[test-triage,i2c] Assertion failure in ic2_csr_bit_bash test

Hierarchy of regression failure
Block level
Failure Description
The i2c_csr_bit_bash nightly test has started failing in a new way, triggering an assertion in the RTL itself. The errors look like this:
Test i2c_csr_bit_bash has 2 failures.

    2.i2c_csr_bit_bash.66345618441548207127530761161532642421862022572628371803450295713579265220547
    Line 251, in log /container/opentitan-public/scratch/os_regression/i2c-sim-vcs/2.i2c_csr_bit_bash/latest/run.log

          Offending '($stable(tx_fifo_wvalid_i) && $stable(tx_fifo_wdata_i))'
      UVM_ERROR @<PHONE_NUMBER> ps: (i2c_fifos.sv:315) [ASSERT FAILED] TxWriteStableBeforeHandshake_A
      UVM_INFO @<PHONE_NUMBER> ps: (uvm_report_catcher.svh:705) [UVM/REPORT/CATCHER]
      --- UVM Report catcher Summary ---

    4.i2c_csr_bit_bash.112489021735320966066037566388927808396706657839552643311521380754970972310728
    Line 251, in log /container/opentitan-public/scratch/os_regression/i2c-sim-vcs/4.i2c_csr_bit_bash/latest/run.log

          Offending '($stable(tx_fifo_wvalid_i) && $stable(tx_fifo_wdata_i))'
      UVM_ERROR @ 243684582 ps: (i2c_fifos.sv:315) [ASSERT FAILED] TxWriteStableBeforeHandshake_A
      UVM_INFO @ 243684582 ps: (uvm_report_catcher.svh:705) [UVM/REPORT/CATCHER]
      --- UVM Report catcher Summary ---

The nightly failures started on 25th April (b938dde05c)
Steps to Reproduce

GitHub Revision: b938dde05c

Tests with similar or related failures
No response

This seems to occur because i2c_csr_bitbash can fill the TX FIFO, and then the assertion triggers because of the overflow (wvalid drops without wready acceptance).


New Feature: Agents story - Tighten collaboration with the AutoGen Team

Foster a more clear and collaborative relationship with the AutoGen team to co-author packages like Microsoft.SemanticKernel.Experimental.Agents.AutoGen (or without the experimental tag 🥇 ).  and to use them widely in AutoGen.
Of course ensure immediate support on the agent abstractions and Core packages to support them as a TOP customer.
This collaboration will ensure cohesive development and integration, presenting a unified "ONE Microsoft" approach to the community and users.
That would require probably covering all the points of the "New Feature: Agents story" issues (feature requests) complete, so the .NET (and maybe the python teams) of AutoGen can build upon those abstractions.
This would simplify their work and tighten the collaboration.
Also you would make a lot of people very happy with this.
I would LOVE to see this happen in a joint "office hours" together.

AutoGen.SemanticKernel is already available maybe we can follow the similiar pattern if there is no circular dependency problem.

Yes, and the integration is very well done - lean and as simple as it can get :)
As I understand, please correct me, it is a wrapper to use Semantic Kernel constructs within the AutoGen framework.
My idea, call it wish, which I did not convey or explain properly - sorry for that - would be that the SK SDK is used as the base, core, for the AutoGen. For this a lot of things should be implemented (see the epic, maybe you can add any which is missing here...) but with those, AutoGen would have a solid Core base where to build upon the abstractions/base implementations provided by the kernel, to build the concrete implementations of, for example:

A proper ConversableAgent (inc. summarizer), and its inherited types (AssistantAgent, UserProxy, GroupChatManager)
Any chat workflow. Sequential Chat, Group Chat, two-agent chat, nested chat...

And other constructs.
This way there would be no integration, SK would be the core. Also if AutoGen exports the Agents & workflow implementations as a nuget package, you could import as "AutoGen.Agents" and use them from any .NET app right away...
I can only dream but that is what I meant, hope I explained it properly, otherwise let me know.
Anyhow, I am thankful & humbled by you responding.


PopupViewClass breaks in Ember 1.8 beta

Ember 1.8-beta removes _insertElementLater.
It looks like all of the _insertElementLater block could be replaced with this._popupView.constructor.renderer.appendTo(this._popupView, this._popup._contentNode);
I tried to make a pull request but I couldn't figure out how to update to Ember 1.8-beta to run the tests.

@edance, could you provide an example of how you worked around the issue?

Sorry @pedrokost for the delay. Here is what I do. I render it offscreen to the body. Then after rendering I grab the html. Probably not the cleanest solution but it worked.
createAndOpenPopup: function() {
  var properties, view, viewClass;
  viewClass = this._container.lookupFactory("view:" + this.popupViewClass);
  if (this._popupView) {
    this._popupView.destroy();
  }
  view = viewClass.create({
    controller: this._controller // you will want to include your data as well
  });
  this._popupView = view;
  view.append();
  return Ember.run.scheduleOnce("afterRender", this, function() {
    return this.bindPopup(view.$().html(), this.popupOptions).openPopup();
  });
}

I was able to get it working by overriding _createPopupContent:
 _createPopupContent: function() {
    if(!get(this, 'popupViewClass')) {
      this._popup.setContent(get(this, 'popupContent'));
      return;
    }
    if(this._popupView) { this._destroyPopupContent(); }
    var viewClass = get(this, 'popupViewClass');
    if(Ember.typeOf(viewClass) === 'string') {
      viewClass = get(this, 'container').lookupFactory('view:' + viewClass);
    }
    // This has the wrong context here. The container is the parent (arraycontroller), not the
    this._popupView = viewClass.create({
      container: get(this, 'container'),
      controller: get(this, 'controller'),
      context: get(this, 'controller'),
      content: get(this, 'content')
    });

    this._popupView.append();

    Ember.run.scheduleOnce('afterRender', this, function() {
      this._popup._contentNode.innerHTML = ''; // HACK to prevent adding duplicates on each click
      this._popupView.$().appendTo(this._popup._contentNode);
    // After the view has rendered, call update to ensure
    // popup is visible with autoPan
      this._popup.update();
    });
  },

One issue with this code it that clicking multiple times on the marker, each time appended a new view to the popup, keeping the previous one. Therefore, I clear the previous content with this._popup._contentNode.innerHTML = '';. What is a better way to fix this?

Has anyone come up with a more up to date solution than the ones posed above?

Meanwhile, you can check this: https://github.com/gabesmed/ember-leaflet/blob/ember-cli-es6/app%2Fmixins%2Fpopup.js#L57-L87

Thanks @miguelcobain! Could you elaborate on https://github.com/gabesmed/ember-leaflet/blob/ember-cli-es6/app%2Fmixins%2Fpopup.js#L74-L77

// You can't call this._popupView.replaceIn because it erroneously detects

// the view as an Ember View because the popup's parent map's parent view
// is an Ember View. So we need to trick it by calling the renderer's
// replace function.

Well, @gabesmed is the author of that part.
But it obviously is a sensible part since we're using internals (private API).
Tell us if you have an alternative.

@srt32 yeah I wrote that and it appears to work with modern embers? not sure what your question is

this is part of the es6 migration which we'll hopefully finish real soon

@gabesmed thanks for the response. I misread the code. Makes sense!


adding operator skipUntil - #193

Adding operator skipUntil

Codecov Report
Base: 99.55% // Head: 99.57% // Increases project coverage by +0.01% :tada:

Coverage data is based on head (5c17b60) compared to base (b0deabd).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #197      +/-   ##
==========================================
+ Coverage   99.55%   99.57%   +0.01%
==========================================
  Files          47       49       +2
  Lines        1582     1643      +61
  Branches      329      338       +9
==========================================
+ Hits         1575     1636      +61
  Misses          2        2
  Partials        5        5

Impacted Files
Coverage Δ

src/ops/skip-while.ts
100.00% <ø> (ø)

src/ops/take-while.ts
100.00% <ø> (ø)

src/index.ts
100.00% <100.00%> (ø)

src/ops/skip-until.ts
100.00% <100.00%> (ø)

src/ops/take-until.ts
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


DMSDB.Context.tt is not need !but !!!

You have to set its Property from "Build action : Content" to "Build action : None".
Wax is based on the csproj file, so files which are in "Build action : Content" would be detected, and that's a standard behaviour.

Thank you very much for your patience!
But the output is not "copied to the output directory" , so I think it should not be brought in wix！

Can you send me the project file, so I can check what goes wrong here?

WindowsFormsApplication5.pdf
i can't upload zip files , so  download this file , rename plase!
this project file for #29  #28

\zh-Hans\EntityFramework.resources.dll" not include by  wax , you can test for #29

Build action of the .tt files is "Content" - and all content will be reported by VS as project output, no matter if copy to output directory is checked or not.
You must change the build action to none.


Improve Cropping Behavior #166 by Sethdenner

This is an upgrades the Original feature in #166 with the current development branch

sorl-thumbnail has been a great asset in our Django based web project however the implementation of cropping left a little to be desired (or at least the implementation didn't make a lot of sense to me) so I made some modifications.
I modified the cropping behavior in the following ways:
The crop parameter now takes x,y coordinates of the top left corner as well as width/height of the crop region.
Cropping occurs before scalling.
Feel free to merge this into the main project if you also feel that this is an improvement. If you have any additional notes I will be happy to make further modifications if this isn't exactly what you had in mind.

https://github.com/mariocesar/sorl-thumbnail/pull/166

Any hope? Clipping image from user or admin panel is good idea, with JCrop. Now I switched to easy_thumbnails who have this feature, but without Wand or ImageMagick support as engine this is not a perfect idea.


fido-authenticator: “up needed” not signaled on NK3AM

one curious thing is that I get the prompt to touch the device in the 3A NFC but it doesn't prompt with 3A mini
It seems if status == STATUS.UPNEEDED: # Waiting for touch this call in python-fido2 isn't called on the 3aMini

https://github.com/Nitrokey/pynitrokey/pull/274

I also have the feeling that this https://github.com/Nitrokey/nitrokey-3-firmware/issues/94 is also related to the issue here and the firmware is missing something - although I have no way to test what's going on at the hardware/firmware level

In combination with https://github.com/Nitrokey/nitrokey-3-firmware/issues/93, my guess that there is something wrong with the timers that trigger the ctaphid_keepalive and ui tasks:  the CTAPHID_KEEPALIVE command signals STATUS_UPNEEDED, and ui should call the code that toggles the LED if it is blinking.  @daringer do you have an idea why this could be the case?  I will also try to debug this while working on https://github.com/Nitrokey/nitrokey-3-firmware/issues/79.

looks like this is also fixed by #319
based on the original issue (https://github.com/Nitrokey/pynitrokey/pull/274) I tested using nitropy fido2 verify and both behave identical now:

nk3am:

❯ nitropy fido2 verify
Command line tool to interact with Nitrokey devices 0.4.38
Enter PIN:
Touch your authenticator device now...
/../

nk3an:

❯ nitropy fido2 verify
Command line tool to interact with Nitrokey devices 0.4.38
Enter PIN:
Touch your authenticator device now...
/../

so, should we close this as fixed?

AFAIS this is fixed in current firmware releases, so I’m closing this issue.  Please re-open if the problem occurs again.


Document the benefits / tradeoffs made by this library

The README doesn't exmplain why I would want to use this library instead of serde, miniserde ormicroserde

I do not have much to add over this part of the README, that's pretty much it:
No more syn, proc_macro2 or quote in the build tree!

> cargo tree
nanoserde v0.1.0 (/../nanoserde)
└── nanoserde-derive v0.1.0 (/../nanoserde/derive)

Answering your question - you want to use nanoserde if you want a cargo tree without said dependencies. If you are okay with them - all the other libraries are probably a better choice.

Answering your question - you want to use nanoserde if you want a cargo tree without said dependencies. If you are okay with them - all the other libraries are probably a better choice.

I would also be curious to know how this crate compares to serde and miniserde in terms of speed, compilation time, and binary size.  serde is fast, but tends to generate bloated binaries; miniserde is slower but leaner (since it uses dynamic dispatch and is generally less optimized). Have you done any benchmarking against these crates by any chance?

I'm also curious - is there a reason I should be concerned about having those in the dependency tree?


Bungeecord Linking

Alright, so I put it in bungeecord, and then it works, but when i try to get the rank using LuckPerms API or Vault, it doesn't work.

Vault is only used on spigot servers.
So when you use LuckPerms on BungeeCord only you need to use a bungee plugin that uses the LuckPerms api.


Loudness: enable the Cancel button only while analyzing

To avoid possible confusion as this Cancel button is not for closing the dialog without saving (issue #917).

Merged into next


Create a repo

Please include:

GitHub repo to create: bevel-samples
Project to be added to:  N/A
Teams with which access:  https://github.com/orgs/hyperledger/teams/bevel-contributors
* Team name: bevel-samples-committers same as (https://github.com/orgs/hyperledger/teams/bevel-committers)

Team name: bevel-samples-admin
Role:

Admin - (suvajit-sarkar, sowank)

@suvajit-sarkar here you go!


websocketd for http

Websocketd is an awesome project.
Do you know of a solution with a similar approach for http?

Without completely understanding your request: Isn't inetd something to look into?

Since there is no clarification on question I'll close it but feel free to re-open.


Documentation doesn't specify that Chart.register is required for adding a Legend

Documentation Is:

[X] Missing or needed?
[ ] Confusing
[ ] Not sure?

Please Explain in Detail...
Multiple people are confused by the documentation as seen in:

https://stackoverflow.com/a/67949681/6517320
https://stackoverflow.com/a/70753333/6517320

Users attempt to add a legend to the chart, and are confused about why it doesn't work. The solution is to call Chart.register on Legend, but this is missing from the documentation.
Your Proposal for Changes
Mention the need to call Chart.register on Legend for the legend to be displayed.
Example
No response

Chart.register(Legend) is only required when using tree shaking. If you use chart.js in your browser you don't need to import and register anything, if you import the registerables and register those or import chart from chart.js/auto it also is not necessary.
All this is described here in the docs:
https://www.chartjs.org/docs/master/getting-started/integration.html#bundlers-webpack-rollup-etc

This took way too long to figure out after migration.
Not sure how this can be solved but there was 0 warnings or errors when supplying a plugins object but without registering the plugin. I think an enhancement of this sort would improve Developer Experience.

took me so long to figure out why my legends were not working - we should add a little yellow card in the docs about this.

Yeah, same. The explanation that @LeeLenaleee provides isn't really an explanation or an answer as, surprise, there are people who want to use tree-shaking and so the answer about importing the whole library or using <script> tags (in 2023, really??) isn't really of much value.

Well I linked the docs to the exact page that describes what you could import and how to do it for treeshaking. But reading documentation is too hard for people it seems like.

When it's poorly written or lacking then yes, it is too hard.


error: cannot find symbol flag = PendingIntent.FLAG_MUTABLE

Hi,
I am trying to build my project with "react-native-nfc-manager": "3.11.5", and I am getting this error:
node_modules/react-native-nfc-manager/android/src/main/java/community/revteltech/nfc/NfcManager.java:1080: error: cannot find symbol
flag = PendingIntent.FLAG_MUTABLE;
^
symbol:   variable FLAG_MUTABLE
location: class android.app.PendingIntent
My setup:
"react-native": "0.66.0",
"react-native-nfc-manager": "3.11.5",
buildToolsVersion = "30.0.2"
minSdkVersion = 21
compileSdkVersion = 31
targetSdkVersion = 31
Device: android 8.0
seems like the fix for FLAG_MUTABLE is not backward compatible.

Same Problem.

Upgrade gradle tools sdk to 11 fixes this, close this issue.

gradle tools sdk to 11 f

Gradle tools newest version is 7.2 ?

NfcManager.java compares the buildSDK version with Build.VERSION_CODES.M (which is 23)
  int flag = 0;
  if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.M) {
    flag = PendingIntent.FLAG_MUTABLE;
  }

However FLAG_MUTABLE is not added until API 31:
https://developer.android.com/reference/android/app/PendingIntent#FLAG_MUTABLE
I don't understand.

NfcManager.java compares the buildSDK version with Build.VERSION_CODES.M (which is 23)
  int flag = 0;
  if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.M) {
    flag = PendingIntent.FLAG_MUTABLE;
  }

However FLAG_MUTABLE is not added until API 31: https://developer.android.com/reference/android/app/PendingIntent#FLAG_MUTABLE
I don't understand.

Just find the reason here: https://github.com/revtel/react-native-nfc-manager#android-12
Change the compileSdkTaget to 31 will fix it.

NfcManager.java compares the buildSDK version with Build.VERSION_CODES.M (which is 23)
  int flag = 0;
  if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.M) {
    flag = PendingIntent.FLAG_MUTABLE;
  }

However FLAG_MUTABLE is not added until API 31: https://developer.android.com/reference/android/app/PendingIntent#FLAG_MUTABLE
I don't understand.

Just find the reason here: https://github.com/revtel/react-native-nfc-manager#android-12 Change the compileSdkTaget to 31 will fix it.

This works 🔥


fix(vsphere): synchronisation cluster witness VM "device with this asset tag already exists"

vsphere sets  "No Asset Tag"  for infoValue.  This messes up the synchronization process and troughs errors.
Adjusting infoValue to empty fixes this.

Hello, thanks for this PR. Looks fine to me. Could you just rebase your commits and use semantic relase commit message so the repo worflows will run automatically.
Like this:

merge last two commits with new message:

git rebase -i HEAD~2
# pick first and squash second and change message to fix(vmware): asset tag logic (fixes #387)
git push --force

And also since this repo keeps linear history
git rebase origin main # When origin points to this repo

Thanks for the PR. Looks good to me, will first merge it to develop to refractor commits, so automatic semantic release ci will work.


Dashboard landing: Add a dashboard plus ff section

Description
In an effort to highlight that the Dashboard is even better when combined with the FlowFuse platform, I've added a new section to the landing page.
Related Issue(s)
#2279
Checklist

[x] I have read the contribution guidelines
[x] I have considered the performance impact of these changes
[ ] Suitable unit/system level tests have been added and they pass
[ ] Documentation has been updated

Hi @Hasmin-AC, wdyt?
I know we have "Flexible deployment with FlowFuse" as part of the previous section, but I wanted to add another one dedicated exclusively to the benefits of using FF + Dashboard and being a bit more specific.

here are some resources:

build personalized Dashboards for each of your users: https://www.youtube.com/watch?v=rl6uwV2PhOc | https://flowfuse.com/blog/2024/01/dashboard-2-multi-user/ | https://flowfuse.com/blog/2024/04/how-to-build-an-application-with-node-red-dashboard-2/
Easy integration with FlowFuse Devices:- https://www.youtube.com/watch?v=pCYzJGVkG8s
trustworthy security out of the box: - https://www.youtube.com/watch?v=TY9dhT_tAT0

here are some resources

build personalized Dashboards for each of your users: https://www.youtube.com/watch?v=rl6uwV2PhOc | https://flowfuse.com/blog/2024/01/dashboard-2-multi-user/ | https://flowfuse.com/blog/2024/04/how-to-build-an-application-with-node-red-dashboard-2/
Easy integration with FlowFuse Devices:- https://www.youtube.com/watch?v=TY9dhT_tAT0
trustworthy security out of the box: - https://www.youtube.com/watch?v=pCYzJGVkG8s

Links added!!


Add more search support - BREAKING CHANGE

Is required for this issue: spotify-cli #40
Changed the api.Search() function to take in an additional paramater of 'searchType)
FROM:
Search(q string, limit int)
TO:
Search(q, searchType  string, limit int)
This will cause all the functionality within spotify-cli that uses the api.Search() to fail as it will require an additional parameter of 'tracks' to beadded

I have realised this included the changes from PR#4 accidentally - Do I need to remove this?

As per your comments on the other PR I will separate these two and remove the other two functions by changing the play() one

Play() now incorporates all that is required to play a specific album or playlist.
The other two redundant functions have been removed and the other PR closed without merge. This will require a small about of spotify-CLI refactoring
It is not known what happens if you pass a playlist as context_URI but with a song URI that is not in the playlist. If both are passed and the track is found within the playlist then the playlist will be played from that song onwards.

I think they might need to be split up sadly.

I think they might need to be split up sadly.

We can probably do an if statement like:

if contextURI != "", call Play() only with contextURI in the body.
else if len(uris) > 0, call Play() only with uris in the body.
else, call Play() with neither one the body.

But that logic has to be done within the api.Play() function unless we split it out right? Because where we define the json fields is there

New push -

We need to catch if both are set though?
If both are set then we will be returned an error.

I know I could have 'commited suggestions' But I wanted to ensure that I had just missed the go fmt command locally and it still worked. All good I believe.

Worth noting this was my first open source golang PR.
Glad it worked out on something I will use :)


getIncomingFiles returns File with undefined filesizes after upgrading to 2.1.1

Link to reproduction
No response
Describe the Bug
getIncomingFiles is supposed to return a File[]
After upgrading to Payload v2.1.1 from 2.0.13, getIncomingFiles returns a File[] where file.fileSize is undefined.
Its supposed to be defined, see:
export interface File {
    buffer: Buffer;
    filename: string;
    filesize: number;
    mimeType: string;
    tempFilePath?: string;
}

To Reproduce
Use a default media collection, add a beforeChangeHook like so
import { getIncomingFiles } from '@payloadcms/plugin-cloud-storage/dist/utilities/getIncomingFiles';
import { FileData } from 'payload/dist/uploads/types';
import { Media } from 'payload/generated-types';

const calculateSizeBeforeUpload: CollectionBeforeChangeHook<
  FileData & Media
> = async ({ data, req }) => {
  const files = getIncomingFiles({ req, data });

  // The following line now fails because fileSize is undefined
  const totalFileSize = files.reduce((acc, file) => acc + file.filesize, 0);

  return data;
};

Then upload a file, and you will see filesize is undefined
Payload Version
2.1.1
Adapters and Plugins
"@payloadcms/bundler-webpack": "^1.0.3",     "@payloadcms/db-mongodb": "^1.0.3",     "@payloadcms/plugin-cloud-storage": "^1.1.1",     "@payloadcms/richtext-slate": "^1.0.6",

Working around this by calculating the fileSize length ourselves for now
fileSize = file.buffer.byteLength

Hi @RickVM - I was not able to replicate this, the req returned by getIncomingFiles did have the filesize. Could you share your upload config or provide a basic reproduction?

Closing - feel free to reopen if you are still experiencing this and can provide a reproduction or some detailed steps for us. Thanks!


Queue

Basically I:

Checkout branch alekseysemenov:queue as local branch queue
Apply code review remarks mentioned in https://github.com/griddynamics/nexus-replication-plugin/pull/23
Rebase on griddynamics/master.
Create new pull request, because I cannot commit to @alekseysemenov 's repository.

@alekseysemenov , @kevstigneev please review and merge if possible.

LGTM. @alekseysemenov ?


fix: phantom popover position on first render (#1723)

Please read and mark the following check list before creating a pull request:

[x] I read and followed the CONTRIBUTING.md guide.
[x] I read and followed the New Feature Checklist guide.

Short description of what this resolves:

merged into https://github.com/akveo/react-native-ui-kitten/pull/1727/files#


Remove gluesql prefix in dependencies and features

Codecov Report

Merging #465 (d89e7a9) into main (8b34701) will not change coverage.
The diff coverage is 0.00%.

:exclamation: Current head d89e7a9 differs from pull request most recent head feb23c6. Consider uploading reports for the commit feb23c6 to get more accurate results

@@           Coverage Diff           @@
##             main     #465   +/-   ##
=======================================
  Coverage   91.06%   91.06%
=======================================
  Files         159      159
  Lines        9247     9247
=======================================
  Hits         8421     8421
  Misses        826      826

Impacted Files
Coverage Δ

src/main.rs
50.00% <0.00%> (ø)

tests/glue.rs
73.07% <ø> (ø)

Continue to review full report at Codecov.

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


typo for the themely command

this is my last pr before kurisu rewrite

tfw your pr was for a typo but you made a typo in the description


use k8s module or openshift applier

How do I decide (and convince my colleagues) what to use?  Do I use Ansible k8s module to provision my Openshift objects or do I use the Openshift Applier role?
I started with Openshift applier, but I find it sometimes limiting in flexibility.  I have the impression vanilla Ansible modules (k8s, k8s_facts) gives me more freedom..
Any comments ?

Not sure this is quite an apple-to-apple comparison. I.e.: one is a set of modules and the other is a role that provides structure around how said modules can are used (yes, openshift-applier uses oc or kubectl, but it could as well use the k8s modules). In other words, loosely said, if you have a list of object definitions and content for a cluster, and you wanted to use the k8s modules to create/apply this content, you would have to write a similar role/playbook to what the openshift-applier provides.


ninja build step should use gcc 10 by default even if 9 is your system default

Workaround I used:https://askubuntu.com/questions/26498/how-to-choose-the-default-gcc-and-g-version
Should be fixed in the Makefile though I think?


opening a ory tunnel for local dev doesn't work anymore

Preflight checklist

[X] I could not find a solution in the existing issues, docs, nor discussions.
[X] I agree to follow this project's Code of Conduct.
[X] I have read and am following this repository's Contribution Guidelines.
[X] I have joined the Ory Community Slack.
[X] I am signed up to the Ory Security Patch Newsletter.

Ory Network Project
inspiring-archimedes-tjzunlod7c
Describe the bug
When I run ory tunnel to setup a local dev environment, it gets stuck
Reproducing the bug
run

ory tunnel --dev --project inspiring-archimedes-tjzunlod7c http://localhost:6200/

the browser opens up

log into the ory account

click "allow"

everything freezes up

Relevant log output
on the network tab, I see that a pending call to the following url is attempted

http://<IP_ADDRESS>:33655/callback?code=ory_ac_tgku....&scope=offline_access+full_access+email+profile&state=m7S...

this is what I get on the console:
[41500:41527:1222/072200.833541:ERROR:registration_request.cc(291)] Registration response error message: DEPRECATED_ENDPOINT
[41500:41527:1222/072538.829726:ERROR:registration_request.cc(291)] Registration response error message: DEPRECATED_ENDPOINT

Please notice that everything used to be working until some days ago.

Relevant configuration
No response
Version
ory cli v1.1.0
On which operating system are you observing this issue?
Linux
In which environment are you deploying?
Ory Network
Additional Context
I am reopening #407 because the issue is still there

works now


Merging convolutional layer with Merge layer

Hi,
I wanted to merge two sequential models input into one using Merge layer. But it is showing me error.
I am using image, with size 128x128 (RGB image)  and batch size is 32.
The error coming is : ValueError: The model expects 3 input arrays, but only received one array. Found: array with shape (32, 3, 128, 128)
The model is  ---
model = Sequential()
leftBranch = Sequential()
leftBranch.add(Reshape((3,128,128), input_shape=(3, img_width, img_height)))
leftBranch.add(Convolution2D(14, 3, 1, activation='relu'))
leftBranch.add(ZeroPadding2D((1, 1)))
leftBranch.add(Flatten())
rightBranch = Sequential()
rightBranch.add(Reshape((3,128,128), input_shape=(3, img_width, img_height)))
rightBranch.add(Convolution2D(14, 1, 3, activation='relu'))
rightBranch.add(MaxPooling2D((2, 2), strides=(2, 2)))
rightBranch.add(Flatten())
centralBranch = Sequential()
centralBranch.add(Reshape((3,128,128), input_shape=(3, img_width, img_height)))
centralBranch.add(Convolution2D(14, 5, 5, activation='relu'))
centralBranch.add(MaxPooling2D((2, 2), strides=(2, 2)))
centralBranch.add(Flatten())
merged = Merge([leftBranch, centralBranch, rightBranch], mode='concat')
model = Sequential()
model.add(merged)
model.add(Dense(64))
model.add(Activation('relu'))
model.add(Dropout(0.5))
model.add(Dense(1))
model.add(Activation('sigmoid'))
Error coming is : ValueError: The model expects 3 input arrays, but only received one array. Found: array with shape (32, 3, 128, 128)
So, whats is the proper way to concatenate two sequential model with convolutional layers. I just want to Merge  convolutional layers output like I did it here.
Any suggestions will be appreciated. Plz help.

Can you post your model.fit() line and everything that have to do with preparing your input?
It's seems like currently you are only feeding one of the branches with input.

model.fit_generator(
train_generator,
samples_per_epoch=nb_train_samples,
nb_epoch=nb_epoch,
validation_data=validation_generator,
nb_val_samples=nb_validation_samples,callbacks=callbacks_list)

@dasraf9  thanks for replying . I am using imagedatagenerator  for image augmentation.
Yeah It is saying that it is receiving one array instead of 3. But i am merging three .

I understand that you wish to have the same input to all 3 branches.
If so, try this:
`input_layer = Reshape((3,128,128), input_shape=(3, img_width, img_height))
leftBranch = Sequential()
leftBranch.add(input_layer)
leftBranch.add(Convolution2D(14, 3, 1, activation='relu'))
leftBranch.add(ZeroPadding2D((1, 1)))
leftBranch.add(Flatten())
rightBranch = Sequential()
rightBranch.add(input_layer)
rightBranch.add(Convolution2D(14, 1, 3, activation='relu'))
rightBranch.add(MaxPooling2D((2, 2), strides=(2, 2)))
rightBranch.add(Flatten())
centralBranch = Sequential()
centralBranch.add(input_layer)
centralBranch.add(Convolution2D(14, 5, 5, activation='relu'))
centralBranch.add(MaxPooling2D((2, 2), strides=(2, 2)))
centralBranch.add(Flatten())`

@dasraf9 thanks . its working now


ITLB / I$ power optimizations

I-cache power optimization
Bypass I-TLB and tag_mem when possible. In addition, select the necessary bank of data_mem.
I-TLB:
1) General Case:
When incoming vaddr tag == previously fetched valid vtag and we’re not doing itlb_fence or itlb_fill, we bypass the i-tlb
If we bypass the i-tlb, then the physical tag is always valid (ptag_v_li) and the physical tag (ptag_li) is previously stored ptag. Note itlb_r_v_lo = 0 when bypass is enabled
2) Special Case 1 (itlb_fence or itlb_fill)
While we’re performing a itlb_fence or itlb_fill, we do not bypass
Furthermore, we invalidate the current vtag that’s going to be stored in the prev_fetch_vtag_r
3) Special Case 2 (itlb_miss_lo)
If a fetch results in a miss, we invalidate the vtag in prev_fetch_vtag_r. Note that itlb_miss_lo is determined on the same cycle as we’re storing prev_fetch_tag
I-Cache Tag_mem:
1) General Case:
When incoming vaddr index == previous valid index and we’re not writing to or poisoning tag_mem, we bypass the tag mem
If we’re reading and we bypass the tag mem. Latch_last_read_p=1 will hold onto the previous tag_mem output
2) Special Case 1 (writing to tag mem)
Turn off bypass and we invalidate the previously stored tag_mem address until we read again
3) Special Case 2 (poisoning)
Turn off bypass signal
I-Cache Data_mem:
1) General Case:
If we decided to bypass tag_mem, we can use the hit_index_tl to help select the single data_mem bank that will be used.
2) Special Case 1 (ptag_i changes while tag_mem under bypass)
To solve this issue, vaddr_vtag and addr_vtag_tl were added. If the vtag changes during bypass, all banks must be enabled

Need to rebase on latest fe_dev to get the one-hot caches. Let me know if you need clarification on those changes.
Otherwise, LGTM, pending timing path analysis

May you clarify on what you mean by "need to rebase on latest fe_dev to get the one-hot caches"? What action is required on my end? Thanks
Synthesis Time Path Analysis:
Technology Node: gf12
Operating Conditions: SSPG_0P72V_M40C
Freq/Per: 1GHz/1000ps
Library: IN14LPP_SC7P5T_84CPP_BASE_SSC16L_SSPG_0P72V_M40C
Wire Load Model Mode: top
Path affected by tlb bypass changes in Icache:
pc_gen_stage_reg -> fe/mem/itlb/vtag_i -> fe/mem/itlb/tlb_bypass_reg
total arrival time = 956.26ps
total max timing slack=0.19ps
note: tlb_bypass_reg adds about 21.14ps delay
Path affected by tlb bypass changes in dcache:
dtlb/cam/r_tag_reg -> cam_tag_array -> one_hot_mem -> r_entry_bypass_reg(bsg_chip_bsg_dff_reset_en_bypass) -> dtlb/entry_o -> dcache_ptag -> dcache/wbuf
total arrival time = 927.30ps
total max timing slack=1.05ps
note: r_entry_bypass_reg adds about 36.88ps delay
Path affected by icache tag/data bypass logic:
None shown in timing report with max path of 1000
Other notable timing paths unrelated to this change but might be helpful for future reference:

icache: data_mem_pkt_way_r_reg -> read_mux_butterfly -> icache_UCE -> cmd_fifo (932.0ps/slack=0ps)
hit_index_tv_r_reg -> data_set_select_mux -> final_data_mux -> pc_gen/instr_scan -> icache_vaddr_i -> icache/data_mem (767.24ps/slack=0.01ps, large setup time)
fe_cmd_fifo (unhardened fifo) -> pc_gen -> bp_fe_bht (945.62ps/slack=0.1ps)

Great work! Thanks for your patience on the reviews :)


Remove initial-scale=1 from

This saves some bytes and avoids propagating an obsolete workaround. The initial scale already defaults to 1. initial-scale=1 in viewport was propagated widely by https://css-tricks.com/probably-use-initial-scale1/ (though css-tricks itself doesn't use it). It was necessary to work around the orientation change bug in Safari for iOS < 9. iOS 9 was released in 2015 and iOS < 9 usage is extremely low in 2022.
https://webhint.io/docs/user-guide/hints/hint-meta-viewport/ seems authoritative about it no longer being necessary.
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[ ] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[ ] This message body should clearly illustrate what problems it solves.
[ ] Ideally, include a test that fails without this PR but passes with it.

Tests

[ ] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[ ] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. All changesets should be patch until SvelteKit 1.0

TIL! Thanks

Hey @ivan I don't think the initial-scale=1 workaround is obsolete yet! I'm working on a project, and everything behaves fine on Firefox, but not so when I looked on my mobile. I can confirm the issue shown in the screencast happens on the following Chrome-based browsers:

Linux Pop!_OS 22.04 LTS:

Chromium Version 117.0.5938.92 (Official Build) snap (64-bit)

Android 13

Brave 1.50.114, Chromium 112.0.5615.49
Vanadium 117.0.5938.60

Screencast from 27-09-23 10:41:10.webm
Can you confirm that this is an issue with Chrome handling the viewport meta tag?

Google writes on their lighthouse page:

Lighthouse doesn't check that width equals device-width. It also doesn't check for an initial-scale key-value pair. However, you still need to include both for your page to render correctly on mobile devices.

and the example they provide as best practice is:
 <meta name="viewport" content="width=device-width, initial-scale=1">

Adding back initial-scale=1 seems a bit easier than changing Chrome :sweat_smile:

... the difference of viewport handling can be seen with window.innerWidth, MDN:

innerWidth returns the width of the window's layout viewport

Discrepancy in Chrome:
Screencast from 27-09-23 11:14:18.webm
No discrepancy in Firefox:
Screencast from 27-09-23 11:15:12.webm


Review deployment script

I recently added a deployment script and Travis deployment
I'd love if someone review it and write in this issue if there are things that could be better implemented.
Thanks!
Some info about what this script actually does:
Every time a branch/pull request is being merged to the master branch, Travis execute the deployment script atdeploy/deploy.collections.js.
This script connects to a MySQL database, checks to see what changed in collection/, and updates the database. (removes/changes/adds data, so it'll be exactly like collection/)
The MySQL database from above, is being used by the API to deliver the data. (see code)

Hello, there was a blocking issue (wrong package) on the travis script, I just did PR fix to make it run again.


[Feature Request] Allow indirect dragging for some items, i.e. header and footer items

Hello,
I am migrating from Vue 2 to Vue 3 and wanted to update the version of vue-draggable. Previously, since we needed to loop around the items, we had the control of disabling drag for some items explicitly. Still, these items can be adjusted/dragged indirectly if any other item is moved before or after.
How do we achieve a similar thing with this package? I have looked into the header and footer slots, but these are limited to header and footer for draggable lists only which is not helpful for my use case.
I am giving some code snippets for the old version implementation and the new one I am trying to implement.
Old implementation
<draggable
   v-model="list"
   v-bind="dragOptions"
   @change="itemChanged"
   @start="onDragStart"
   @end="OnDrop"
>
  <transition-group name="flip-list" type="transition">

      {{ listeItem.name }}

  </transition-group>
</draggable>

New implementation
<draggable
  :list="list"
  v-bind="dragOptions"
  itemKey="name"
  @change="itemChanged"
  :component-data="{
    tag: 'div',
    name: 'flip-list',
    type: 'transition',
  }"
  @start="onDragStart"
  @end="onDrop"
>
  <template #item="{ element: milestone, index }">
     {{ listeItem.name }}
  </template>
</draggable>

Got the solution from Sortable Options


restrict vpn traffic

vpn lets all outgoing traffic through, but clients only need to talk to futel-prod and futel-stage.

and futel-dev

any specifics for this change, like ports or ips? stage vs prod?

I think all traffic to the hosts is ok. The main motivation is just to stop somebody from plugging a cable into one of our vpn client boxen and then routing all their traffic through our vpn.
The only thing connected to a vpn client should be a SIP client., and a SIP client only needs to talk to the asterisk server. The asterisk server then talks to providers and other services directly, as well as back to the clients.
The asterisk server is on futel-prod.phu73l.net, or futel-stage, or futel-dev.
Allowing any subdomain of phu73l.net might be easiest and best.
The vpn setup is maybe a bit weird. Only the SIP clients are behind vpn clients. The asterisk server doesn't have a vpn client and doesn't really know there's a vpn, it just talks back using the connection the sip client opens. It would probably be best for everything to have a client - then we might be able to retire phu73l.net altogether, and our deploy might be smoother. But that's a bigger change, I just don't want our clients to let inappropriate traffic through the vpn.

moved to https://github.com/kra/futel-vpnbox/issues/1


Update Readme.md

Should be marked as Hacktoberfest spam, reported and closed.

https://twitter.com/shitoberfest

Shame

Durig Parsing


Added Support for Monks Enhanced Journals Module so that it can find the image

Monks-enhanced journals is a popular tool that places journal images in a different location.
I would like to make a minor adjustment that will enable it to find the image when quests use a reference to the monk's enhanced journal. Presently when the enriched attempts to find the image on a monks enhanced journal page it will be undefined and show as blank.

I have modified the enhancer slightly so that when it finds a journal page it will first attempt to check the monks enhanced journal location and if that returns undefined it will search the normal location.

In the past MEJ custom journal types were supported prior to any changes in MEJ to store image paths in a custom flag. I only test FQL every core release of Foundry, so not sure when that MEJ change occurred. I'll accept this PR, but modify it accordingly when I work on the v12 FQL release.

Thank you!


API reference for editor autocomplete

Fixed in https://github.com/defold/extension-rive/commit/373c071fb08f0741b653d18a7ebb9079b358f2f5


Improve parameter naming convention for hfss.set_impedance_multiplier()

Description of the current limitations
As mentioned in #2358, the parameter given to hfss.set_impedance_multiplier() is the multiplier value not the impedance.
Code sample expected
change "impedance" to "multiplier"
Useful links and references
https://github.com/ansys/pyaedt/issues/2358

Hi @fwlfHS ,
As mentioned in #2358 , are you going to do the implementation?
Thanks

Hi @Samuelopez-ansys, please see PR #3328

That's great! Thank you for your contribution 🥇


Improve log stream processor examples

Purpose

Improve usability.

Codecov Report

Merging #1501 into master will decrease coverage by 0.04%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #1501      +/-   ##
============================================
- Coverage     68.18%   68.14%   -0.05%
  Complexity       42       42
============================================
  Files           643      643
  Lines         26984    26984
  Branches       4260     4260
============================================
- Hits          18399    18388      -11
- Misses         6799     6808       +9
- Partials       1786     1788       +2

Impacted Files
Coverage Δ
Complexity Δ

...ore/query/processor/stream/LogStreamProcessor.java
63.88% <ø> (ø)
0 <0> (ø)
:arrow_down:

.../siddhi/core/util/event/handler/StreamHandler.java
62% <0%> (-12%)
0% <0%> (ø)

.../io/siddhi/core/util/snapshot/SnapshotService.java
70.39% <0%> (-0.83%)
0% <0%> (ø)

...o/siddhi/core/aggregation/IncrementalExecutor.java
80.46% <0%> (-0.79%)
0% <0%> (ø)

Continue to review full report at Codecov.

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


Change Background Image on Title

Coverage remained the same at 78.906% when pulling 5244c9f250a6bccd71b8234cb504d1bf1377f21d on psastras:master into b7b52a303a8a6f4f453d430faaf9e6c6f447f18b on OpenChatAlytics:master.


Power needs documenting in code

i.e. ExtensionCableSystem and PowerReceiverSystem. Like I get overall how our power works but 0 clue how it relates to these components as there's not an xmldoc in sight so I don't know if my prototype needs them or not.

I can document them, I was the last person that worked with those files.
As a heads up: Those don't really belong to pow3r. They are for connecting lv wires to things over a distance and haven't been toucht much by pjb when he did pow3r.

tbh I think we ought to do it outside of code comments/xmldocs. In-line comments should be for comments about the code, not comments about what the code implements. High-level discussion/explanation belongs elsewhere, like the wiki.

We already have the documentation outside of the code, but I shouldn't have to leave my IDE to remember which component is for which piece.


[PDP-2827] update latest changes for recipe and scripts

changes

fix the typo
update the recipe

So the changes are

for certificates
We remove the need for using AWS ACM to manually create certificate before deploy CP. We always create certificate using cert-manager.

for Azure storage
We remove the need to manually create storage account before deploy CP.

for ingress
We add kong support and secondary domain


Begin process of deprecating MAINTAINER

This may take some time, but start by pointing people at
LABEL instead.
MAINTAINER predates general LABEL and has basically no tooling,
only allows a single item to be added, and is has been
unofficially deprecated for some time, with many images not
including it, but we have never specifically said that it
should be replaced by LABEL as a better more generic metadata
solution.
Signed-off-by: Justin Cormack<EMAIL_ADDRESS>
I would imagine that we would not remove support for some considerable time. One option would be to simply treat the MAINTAINER line as a noop in a few releases.
cc @thaJeztah @SvenDowideit  I picked a few places in the docs to remove it, but there are more, could add here.

Can we get some docs started that call-out "well defined" label names - like "maintainer" so that people have a consistent usage pattern?  Maintainer vs MAINTAINER vs maintainer vs author....  can lead to a usability issue.

There exist general schemas eg Dublin Core
http://dublincore.org/documents/dcmi-terms/
Also draft container specific scheme at http://label-schema.org
I don't know of anything else targeted at software specifically, none of
the packaging formats seemed to use standards.
I do agree standardisation would be helpful.
On 6 Aug 2016 18:01, "Doug Davis"<EMAIL_ADDRESS>wrote:

Can we get some docs started that call-out "well defined" label names -
like "maintainer" so that people have a consistent usage pattern?
Maintainer vs MAINTAINER vs maintainer vs author.... can lead to a
usability issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/docker/docker/pull/25466#issuecomment-238030524, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAdcPB0vBqpkdtVnmObAsOWOPub6rIeQks5qdK_vgaJpZM4JeRba
.

This also needs to be added to https://github.com/docker/docker/blob/master/docs/deprecated.md

@thaJeztah added there....

@SvenDowideit done.

One option would be to simply treat the MAINTAINER line as a noop in a few releases.

If we want to do that, we should decide on a release (default deprecation policy is 3 releases now, but we can diverge from that), and mention that release in the deprecated.md

LGTM

but /cc @shykes (I think) :smile:

+1!  I stopped using the MAINTAINER instruction ages ago, essentially for the reasons you've outlined -- the only "tooling" that displays it is docker inspect, it's inherited by sub-images (and thus if it's not used 100% consistently by all authors, the results "bleed" -- I don't want credit for the Dockerfiles based on mine :innocent:), and it used to waste a layer. :smile:

@justincormack Does it mean deprecating https://github.com/docker/docker/blame/master/image/spec/v1.1.md#L184 as well as there will be no way to fill that field.

LGTM :+1:
absolutely closes #18921.

@justincormack needs a rebase 👼
Also, I do agree with @tonistiigi

@justincormack Does it mean deprecating https://github.com/docker/docker/blame/master/image/spec/v1.1.md#L184 as well as there will be no way to fill that field.

Will rebase.
I don't know exactly how/when we deprecate that field, do we do it when we actually eg stop filling it in from MAINTAINER? or now?

I don't know exactly how/when we deprecate that field, do we do it when we actually eg stop filling it in from MAINTAINER? or now?

I would say first one when we actually stop filling it :angel:

@justincormack ?

LGTM 🐸 as is, and we can do the rest in follow-up (and even in later versions)
/cc @thaJeztah

re-LGTM, thanks!


Frame sampling in test phase

Hi, I am confused about the description of frame sampling while testing: 'The values for i are determine using a stride S, resulting in an array of video embeddings v = [v_0 , v_S , v_2S , v_M ].'
Could you please take MSRVTT as an example to show us how to sample frames in testing phase? Thanks a lot

Does v_0 mean you take 8 frames to get v_0 embedding and eventually take 4 times 8 frames to get [v_0 , v_S , v_2S , v_M] ?

Hi, yes exactly. You can set this running by setting the argument:
test.py --sliding_window_stride NUM_FRAMES
Where NUM_FRAMES is the stride in frames. The video embedding is average over all v embeddings


some qustions about oneshot_matching experiment

Hi, i have something that confused me:

What is the difference of oneshot_matching and BBP_MAP?
The retrain process in matching  actually introduces multiple original data information, so does the matching really reflect his ability to aggregation in a single communication?

and in FL, data privacy is very important， how to do this retrain without increasing the number of communications?


Remove duplicate section and fix formatting

In the README.md the GitLab section was listed twice and the formatting for the Google Hangouts Chat and Mailman was incorrect.

@sabre1041 @matallen This PR has been out for a while and just updates the README. Can you review and merge if you are good with the changes?


Race condition (?) on ProcessedImage's TaskEventMixin with ManyToManyField

There's a flaky error happening when POSTing a ProcessedImage where the save event that triggers the task event is called, seemingly before the ManyToManyField is populated.
To my understanding, you have to save the model before populating the ManyToManyField and thus a race condition of sorts happens where the task checks for the needed source image in _processed_image_helper(). This is flaky as the refresh_from_db() call sometimes gets it in time, but sometimes does not:
https://github.com/ResonantGeoData/ResonantGeoData/blob/78065e2d44c27e2715a47028a33c3eae89ebca71/django-rgd-imagery/rgd_imagery/tasks/subsample.py#L27

I wonder if we need to change the signal to be m2m_changed instead of post_save?

AND if the group field is updated

I need this working by tomorrow, so I added fb26d3c to workaround it for now


Danger check (DO NOT MERGE)

testing to see whether danger check catches package-lock.json and secrets-heroku.properties.SAMPLE bad changes

looks like Danger caught the PR mistakes


Don't use numba on string dtypes

Fixes #1000

@mrocklin i can take this if you want

Sure

closing in favor of #1002


⚠ Mobitopup has degraded performance

In 5c44bc6, Mobitopup (https://napcard.voz.tech) experienced degraded performance:

HTTP code: 200
Response time: 4537 ms

Resolved: Mobitopup performance has improved in 75c9fc7 after 7 minutes.


Fix go version may be passed to the go-buildkite-plugin as a number and not a string

This means that when trying to specify the go version with "1.20", the current version of go, 1.2 is passed to the golang-buildkite-plugin instead. Note that even if the user is doing the right thing and quotes the version in their pipeline, but this plugin does not respect that.
Fortunately, specifying the version as 1.20.0 side steps the issue, as there is a tag on the docker image for both 1.20 and 1.20.0. However, we should support both ways to specify the version, as much of the release materials refer to it as 1.20 and not 1.20.0. As a further example, the URL to download the source is https://go.dev/dl/go1.20.src.tar.gz, whereas https://go.dev/dl/go1.20.0.src.tar.gz is a 404.

LGTM! you can merge it @triarius :)

Thanks, @pzeballos, I don't have the button to merge, though.

Ups! Sorry, we'll review that 🫠 thanks!


WIP: Overhaul

Heyo @bgruening.
Let me know if you see something you don't like, I'll add more to this branch which reflect the changes I'm doing to the Galaxy configs.

Thanks @TorHou!

@TorHou GATK should be put into a deprecated section if you ask me :) We are not maintaining it anymore and do not recommend it.

@TorHou should we merge this?
I would like to add a few new tools and I'm not sure where to add without causing you troubles.

go ahead. You can merge and modify at will :wink:

Oki  doki.


unresponsive toelectrical stimuli - typo

unresponsive toelectrical stimuli MP:0013922
Insert space in primary term label after "to"

Primary term label for unresponsive toelectrical stimuli MP:0013922 looks fine in Protege, Ontobee and OLS but does not display properly on the MGI MP Browser (no space between "to" and "electrical". I deleted and re-entered the term label to see if that fixes the issue.

Issue has been fixed. Primary term label for MP:0013922 now displays properly on the MGI MP Browser.


Parsing Fails only on Windows

I have a strange issue where logos fails tests only on Windows builds.
This is how I define the token types. I test it across this custom script.
While MacOS and Linux builds pass the tests, Windows build oddly fails while parsing a token.
Troubleshooting
Windows Paths
At first, I have thought maybe it is related Windows paths when I include_str here since it might require backwards slashes. However, it is not the case, the file is read successfully.
Windows Whitespace Encoding
This is the only thing I am suspicious about. I define there might be a whitespace at this line as [ ]. Maybe the encoding in Windows is not the same. What do you say?

Environment

Rust 1.43.1
logos 0.11.4

I actually shared this on Rust Users Forum, this is the solution.
Apparently, include_str was the problem and, as far as I could understand, it was including the related text file with some Windows specific setting/encoding (?).
https://github.com/maciejhirsz/logos/blob/5c391c615cec44f8a7158f27e0ba37620e6a9c17/logos/src/lib.rs#L43
I believe this line better contain \r unless there is a better reason to keep it that way. See below:
#[regex(r"[ \t\r\n\f]+", logos::skip)]

Thanks, I'll keep this open so I remember to note that in the handbook!

Closing this as the solution has been found and is not really related to Logos, but more to file encoding where Windows uses \r\n instead of the classical \n on other platforms. Feel free to re-open this issue if you think this should be documented in Logos, or else.


Improved CMS capabilities - edit content from a webpage

We're now using AtomicServer + front-end frameworks (sveltekit, astro) in production for a couple of customers, and I think there is one common usecase that requires some improvement: see a resource in your deployed website, and decide you want to change it.
Let's dive into how we can improve this:
Browser extension with editing capabilities
When the browser extension is installed, user can hover over a resource to see an edit button. Clicking that opens a resource form overlay. The extension manages the secret of the Agent. The extension queries the dom for some attribute (e.g atomic-subject) and injects a button on hover.

Requires user to install an extension
Requires us to manage another app / publish extension in multiple stores

Add alt-click action to compiled front-end
When the user holds the alt or option key, show borders of resources (can be the same atomic-subject) on hover. Clicking opens that resource on atomicdata.dev in edit mode in a new tab.

Elegant, simple solution
Takes over the alt keys default behavior, can be odd to users who aren't admins
Can be forgotten by admins

---
/**
 * A wrapper component that enables alt+click editing functionality for Atomic Data resources.
 * When holding Alt, the wrapped content will show an outline and clicking will redirect to the edit page.
 *
 * @component
 * @example
 * ```astro
 * <ResourceClickWrapper subject="https://example.com/resource">
 *   <SomeContent />
 * </ResourceClickWrapper>
 * ```
 */

type Props = {
  subject: string;
};

const { subject } = Astro.props;
const editLink = `https://atomicdata.dev/app/edit?subject=${subject}`;
---

  <slot />

How about this?

The extension doesn't need to manage an agent or have any settings or even a UI (Maybe only for usage instructions). When the user clicks the extension icon a script will be injected in the current tab. The script will look for any nodes with a data-atomic-subject attribute, measure it's dimensions using getBoundingClientRect and overlay an element with an outline on top. Then when clicked the user navigates to the subject in the attribute (to [domain]/edit?subject=[subject]).
Since we don't edit in the extension it self we don't need an agent, or even use @tomic/lib at all.
We could also publish this script on a cdn and have the developer include it on the page instead. Personally I'd go for the extension because I don't like including dev/admin stuff in a production app. It's also means every visitor will send a request to a cdn for a script that doesn't get used by them att all

---
/**
 * A wrapper component that enables alt+click editing functionality for Atomic Data resources.
 * When holding Alt, the wrapped content will show an outline and clicking will redirect to the edit page.
 *
 * @component
 * @example
 * ```astro
 * <ResourceClickWrapper subject="https://example.com/resource">
 *   <SomeContent />
 * </ResourceClickWrapper>
 * ```
 */

type Props = {
  subject: string;
};

const { subject } = Astro.props;
const editLink = `https://atomicdata.dev/app/edit?subject=${subject}`;
---

  <slot />

How about this?

This is to specific for astro. We should make it generic so it works with every possible framework

Hmm yeah. Would be better to make it generic.


Ability to generate separate forcing instances for bgc

I attempted to get around #89 by creating a new BGC forcing file with roms-tools.
I'm used to working with a year-long BGC forcing file with 12 entries in it, so I then attempted to just generate the equivalent:
roms_frc_bgc= rt.SurfaceForcing(
    grid=roms_grd,
    start_time=dt.datetime(2012, 1, 1, 0, 0, 0),
    end_time=dt.datetime(2013, 1, 1, 0, 0, 0),
    bgc_source={"name": "CESM_REGRIDDED", "path": datadir+"CESM-surface_lowres_regridded.nc"},
    correct_radiation=True,
    use_coarse_grid=True,
)

note the absence of physics_source here : I did not want to create a physics forcing file with ~9000 entries in it, just a bgc file with 12. However, this is not supported by roms-tools : TypeError: SurfaceForcing.__init__() missing 1 required keyword-only argument: 'physics_source'
A quick check shows physics_source only is supported, but I would argue the same should be true of bgc_source only.

Related: #82


cmd/go: .s: +build comment must appear before package clause and be followed by a blank line (regression)

Please answer these questions before submitting your issue. Thanks!
What did you do?
Hello up there. I was updating my tracing/xruntime package for Go1.12 and hit test error:
.../src/lab.nexedi.com/kirr/go123/tracing/internal/xruntime$ go test
# lab.nexedi.com/kirr/go123/tracing/internal/xruntime
./runtime_g_amd64.s:3:1: +build comment must appear before package clause and be followed by a blank line
FAIL    lab.nexedi.com/kirr/go123/tracing/internal/xruntime [build failed]

The error here complains about +build directive in assembly file:
---- 8< ---- (runtime_g_amd64.s)
#include "textflag.h"

// +build amd64 amd64p

// func getg() *g
TEXT ·getg(SB),NOSPLIT,$0-8
	MOVQ (TLS), R14
	MOVQ R14, ret+0(FP)
	RET

(https://lab.nexedi.com/kirr/go123/blob/7ee2de42/tracing/internal/xruntime/runtime_g_amd64.s)
It was working with Go1.11 and previous releases.
What did you expect to see?
Build and test succeed; test pass, as with e.g. Go1.11:
.../src/lab.nexedi.com/kirr/go123/tracing/internal/xruntime$ go1.11 test -v
=== RUN   TestStartStopTheWorld
--- PASS: TestStartStopTheWorld (1.00s)
PASS
ok      lab.nexedi.com/kirr/go123/tracing/internal/xruntime     1.003s

What did you see instead?
.../src/lab.nexedi.com/kirr/go123/tracing/internal/xruntime$ go1.12 test -v
# lab.nexedi.com/kirr/go123/tracing/internal/xruntime
./runtime_g_amd64.s:3:1: +build comment must appear before package clause and be followed by a blank line
FAIL    lab.nexedi.com/kirr/go123/tracing/internal/xruntime [build failed]

System details
go version go1.12.3 linux/amd64
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/kirr/.cache/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/kirr/go"
GOPROXY=""
GORACE=""
GOROOT="/home/kirr/src/tools/go/go"
GOTMPDIR=""
GOTOOLDIR="/home/kirr/src/tools/go/go/pkg/tool/linux_amd64"
GCCGO="/usr/bin/gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD=""
GOROOT/bin/go version: go version go1.12.3 linux/amd64
GOROOT/bin/go tool compile -V: compile version go1.12.3
uname -sr: Linux 4.19.0-4-amd64
Distributor ID:	Debian
Description:	Debian GNU/Linux buster/sid
Release:	testing
Codename:	buster
/lib/x86_64-linux-gnu/libc.so.6: GNU C Library (Debian GLIBC 2.28-8) stable release version 2.28.
gdb --version: GNU gdb (Debian 8.2.1-2) 8.2.1

Thanks beforehand for looking into this,
Kirill

CC @jayconrod

The error could be improved (obviously there is no package clause), but it is correct to be complaining. The // +build line in this file has no effect. You should move it up above the #include.
A more appropriate error would be
./runtime_g_amd64.s:3:1: +build comment must appear before first non-comment source line
and the "blank line" should be dropped in this instance. When the blank line is relevant the message should be
./runtime_g_amd64.s:3:1: blank line must separate +build comment from first non-comment source line

@rsc thanks for feedback. I confirm that moving +build ... to the top fixed my package for Go1.12. Good idea to improve the error message.

@ianthehat, how do you want us to triage cmd/vet issues?
(@alandonovan is still listed as the primary owner on dev.golang.org/owners, but I'm guessing there might be someone else on your team stepping up for vet maintenance?)
CC @josharian @mvdan (secondary owners)


PropertySpelling: Not picking up text-align: centre;

I noticed text-align: centre; in a .scss file, but it didn't get picked up. Wondering if it should have done?

The PropertySpelling linter would only pick up mistakes in the property, not the value of the property. So, if it was text-algin: center, the linter would pick it up.
There's a way to disallow certain units from being used in property values, but not sure there is currently a way to blacklist a misspelled (or alternative spelling) of a valid value.

@chris-dura ah, thanks.
Closing in favour of https://github.com/brigade/scss-lint/issues/779


Support cuTensorNet (from cuQuantum) as an einsum backend

This PR

closes #6261
supports using cuTensorNet as an einsum backend for

path optimization (by setting optimize="cutensornet")
tensor contraction

adds cutensornet as a valid CuPy accelerator
fixes the einsum docstring

Commits f92be944cd864d3635f89d7a0e0b219ad8b41a47 and 18d32e632d587279ce1a9d4c121e3358d96fd4ce can be backported

requires cuquantum-python >= 22.03 and cuTENSOR >= 1.5.0 (#6656)

In terms of implementation, for both path finding and actual contraction I simply hijack the einsum call and delegate to cuquantum.contract() (cuQuantum Python's public APIs that use cuTensorNet). The reason includes:

the way that NumPy/CuPy internally computes the input/output subscripts makes it very hard to just intercept at the pairwise contraction loop (as in the cuTENSOR's case)
In cuQuantum Python we made significant efforts to parse/validate the inputs and can generate better error messages if an error occurs, so it'd be a waste to do input verification twice (in CuPy and then in cuQuantum Python) instead of reusing it
cuQuantum Python supports enormously large inputs that are otherwise incomprehensible to NumPy/CuPy due to the way the unicode string or interleaved inputs are parsed. (Those cases usually require calling opt_einsum.contract() + NumPy/CuPy as its backend.)

Note that I did not do any refactoring as proposed in #6261 to support cupy.einsum_path() for reasons discussed later in that issue. I will send a follow-up PR to add it.

Let me do a test drive (should be a no-op before a CI with cuQuantum installed is set up 🙂).
/test mini

I locally tried the cuTensorNet-based einsum, and it did work. Super cool! Should we have some CI condition that tests _einsum_cutn (possibly in another PR), @kmaehashi?

Installing cuQuantum Python also installs libcutensor.so which is independent of one CuPy sees to have cutensor accelerator. I think this fact would make no harm.

/test mini

Should we have some CI condition that tests _einsum_cutn (possibly in another PR)

That'd be great, but I'm not sure if you'd wanna run the full test suite or just target einsum.

Installing cuQuantum Python also installs libcutensor.so which is independent of one CuPy sees to have cutensor accelerator. I think this fact would make no harm.

Yes. That's why it'd be nice to get #6656 in, otherwise depending on the import order we could be loading a different cuTENSOR (I hit this issue during local development). With cuTENSOR 1.5.0+ it should not matter which gets loaded first.

CI cuda102 complains:
#6 48.07 E: Unable to locate package libcudnn7
#6 48.07 E: Unable to locate package libcudnn7-dev

Maybe removed from Nvidia's apt repository?

Fixed by #6708.
/test mini

Oh I was being silly and forgot to merge with the master branch...

/test mini

/test mini

Now that cuTENSOR 1.5 support is marged to master, I've enabled auto-merge. The backport follows soon.

Thanks, @takagi!


Refactor Ouroboros.Network.Diffusion.runM

Description
resolves #3834 : Refactor Ouroboros.Network.Diffusion.runM.
Motivation
runM (called by run) is 640 lines of code, and is currently not very easy to follow and there is a significant amount of code duplication.
There are two primary case alternatives in runM, where currently we have a lot of duplication; abstractly:
  case diffusionMode of
   InitiatorOnlyDiffusionMode -> ...
   InitiatorAndResponderDiffusionMode -> ...

Objectives of refactor
Our objectives here are

reduce linecount, if possible
more importantly, remove code duplication
restructure code so as to have 80 character lines and no "indentation fudging".
make the similarities and differences between the two diffusion modes more apparent.
make the "primary control flow" of the two modes readily apparent (and comparable to one another).

Notes to reviewers

This "big refactor" is a sequence of a couple dozen small refactors, each which should be relatively obvious.
Not every refactor may seem to be compelling; but most all will enable future refactors.  For justification/motivation, one may want to view the final result.
Many of these "refactors" involve large moves where git diff gives poor results; but one might, using the command-line, view some of these with something such asgit show -w --color-moved=dimmed-zebra --color-moved-ws=ignore-space-change <COMMIT>

Checklist

Branch

[x] Updated changelog files.
[x] Commit sequence broadly makes sense
[x] Commits have useful messages
[x] The documentation has been properly updated
[x] New tests are added if needed and existing tests are updated
[x] If serialization changes, user-facing consequences (e.g. replay from genesis) are confirmed to be intentional.

Pull Request

[x] Self-reviewed the diff
[x] Useful pull request description at least containing the following information:

What does this PR change?
Why these changes were needed?
How does this affect downstream repositories and/or end-users?
Which ticket does this PR close (if any)? If it does, is it linked?

[x] Reviewer requested

haskell-stylish complains in CI.  You can run ./script/ci/check-stylish if you have stylish-haskell-<IP_ADDRESS> installed on your system or run nix build .\#stylish-haskell.

There is a conflict with master, it's due to 8fa5913ba7.

@coot fixed merge conflict


[REQUEST] Implement missing none DRC preset with binary edit.

https://forum.doom9.org/showpost.php?p=1973074&postcount=144

For TrueHD there is an ON flag and a ability to write -31. That is none, right?

F.W.I.W: adding the line "<custom_dialnorm>-31</custom_dialnorm>" to the XML configuration file apparently avoids the undesired dialnorm thing.
Still, no way to set the DRC value to "none".

You can use -31 for DD, DDP and TrueHD aswell. The on flag is only for TrueHD 2.0, don't know why. Dolby doesn't plan to add the missing none preset.

Dolby doesn't plan to add the missing none preset.

That is just -31, right? They are not planning to add it cause that should be turned off on the AVR.
TrueHD 2.0?? You mean DVD-A MLP was 1.0? Or you are talking about thd 1.0 from here? https://trac.ffmpeg.org/ticket/667

dialnorm -31 is not the same as a disabled drc.

What is the difference? Again, ffmpeg does not support encoding or decoding THD taking DRC into account.

The on flag is only for TrueHD 2.0

That is false, not stereo works too. 2.0 is a downmix of 5.1, the option is not for it.
See, this is left "DRC default on" toggle on, and right off.


Investigate jsdom==2.1.1 regression

Apparently upgrading jscom from 24.1.0 to 24.1.1 is causing one of our tests to fail on MacOS, because the selection seems to misbehave, like selecting both last two lines as a single line (newline vanishes?):
https://github.com/ansible/vscode-ansible/blob/main/test/units/lightspeed/editableList.test.ts#L115-L122
    editableList.setToUI(["1. Line 1", "2. Line 2"]);
    editableList.focus();

    // Verify the cursor is located at the end of the last list item.
    const sel = dom.window.getSelection();
    assert.ok(sel);
    assert.equal(sel?.anchorNode?.textContent, "2. Line 2");
    assert.equal(sel?.anchorOffset, "2. Line 2".length);

Normally this code would pass but after the upgrade we get (MacOS only):
  AssertionError [ERR_ASSERTION]: '1. Line 12. Line 2' == '2. Line 2'

CI
This needs to be investigated and we need to raised an upstream bug with jsdom if this proves to be their regression and not just a side effect.

https://github.com/ansible/vscode-ansible/commit/f21f543206d949b5e5952c7970dfeb646c9d87bd


Adjust Basilisk to Basilisk (testnet) to chain selector

To avoid any confusion people in production, let's rename there Basilisk to "Basilisk (testnet)"

👋

@zhengow seems doesn't work on https://beta.kodadot.xyz after merging #3164 ?

https://github.com/kodadot/nft-gallery/pull/3164#issuecomment-1158711796

let me see later
发自我的iPhone
------------------ Original ------------------
From: Matej yangwao @.>
Date: Fri,Jun 17,2022 8:02 PM
To: kodadot/nft-gallery @.>
Cc: zhengow @.>, Mention @.>
Subject: Re: [kodadot/nft-gallery] Adjust Basilisk to Basilisk (testnet) tochain selector (Issue #3162)

it's on https://beta.kodadot.xyz in incognito but doesn't update in previous instance tho, whatever, hopefully for new ones doesn't break anything in production

Right, it's related to cache something. It will not break anything in production because the only change is basilisk text


issue while uploading

i was trying to upload songs and i got this error
python gmupload.py /media/extssd/musicdl
13
Loading local songs...
Excluded 0 local songs.
Filtered 0 local songs.
Loaded 18 local songs.

Uploading 18 songs to Google Music

Traceback (most recent call last):ajor Lazer - Free The Universe 2013 Electronic 320kbps CBR MP3 [VX]/01 Major Lazer - You're No Good (feat. Santigold, Vybz Kartel, Danielle Haim & Yasmin).mp3
  File "gmupload.py", line 94, in <module>
    main()
  File "gmupload.py", line 84, in main
    mmw.upload(upload_songs, enable_matching=cli['match'])
  File "<string>", line 2, in upload
  File "/usr/local/lib/python2.7/dist-packages/gmusicapi/utils/utils.py", line 582, in wrapper
    return function(*args, **kw)
  File "/home/supergonkas/gmusicapi/gmwrapper.py", line 463, in upload
    uploaded, matched, not_uploaded = self.api.upload(file, transcode_quality="320k", enable_matching=enable_matching)
  File "<string>", line 2, in upload
  File "/usr/local/lib/python2.7/dist-packages/gmusicapi/utils/utils.py", line 582, in wrapper
    return function(*args, **kw)
  File "<string>", line 2, in upload
  File "/usr/local/lib/python2.7/dist-packages/gmusicapi/utils/utils.py", line 559, in wrapper
    return function(*args, **kw)
  File "/usr/local/lib/python2.7/dist-packages/gmusicapi/clients/musicmanager.py", line 412, in upload
    raise NotLoggedIn("Not authenticated as an upload device;"
gmusicapi.exceptions.NotLoggedIn: Not authenticated as an upload device; run Api.login(...perform_upload_auth=True...) first.

how do i login?

Have you already enabled Google Music on your Google account?

yes @thebigmunch  but i didnt put my details in anywhere .Where should i put them?

If you try to login without using my scripts, does it work?

@thebigmunch im not understaning ,where do i login? in your script,in the browser?

I mean just using gmusicapi directly. If you can't do that much, I won't really be able to help you.

@thebigmunch  can you guide me on how do i do it?

@thebigmunch  Somehow its now working ,it propmted with link i put the code and it worked
Thanks for your help ,and sorry for wasting your time :P


Error when setting up stock environment

I am getting this error when trying to set up the stock environment:
Select technology distribution:
1) stock
2) intel
#? 1
Creating conda environment FraudDetection_stock...
Setting up environment with packages : stock...
setupenv.sh: /glob/intel-python/python2/bin/conda: /glob/intel-python/versions/2018u2/intelpython2/bin/python: bad interpreter: No such file or directory
Environment FraudDetection_stock creation failed

Please verify your conda environment is using Python3