KHTTPError 520, System.IndexOutOfRangeException with private preview plugin

So I've got something of a tricky problem. I'm getting an error that can only be reproduced with a combination of azure-kusto-go and a kusto plugin command that's in private preview.  If I run the query through kusto explorer, it works fine. And if I run most non-plugin queries through my azure-kusto-go client, it works fine. Even some queries with the plugin via the azure-kusto-go client work, just not all of them.
The queries don't seem particularly complicated, they're basic heartbeat checks of the following form:
let mt = evaluate redacted_plugin_request('redacted_account_parameter', @'redacted_kqlm_parameter', ago(35m));
mt
| where Region in ("westus2")
| summarize percentHealthy=todouble(count())

When one of these queries breaks, it looks like this:
Op(OpQuery): Kind(KHTTPError): error from Kusto endpoint(520 ):
{
  "error": {
    "code": "Internal service error",
    "message": "Request aborted due to an internal service error.",
    "@type": "System.IndexOutOfRangeException",
    "@message": "Index was outside the bounds of the array.",
    "@context": {
      "timestamp": "2020-10-06T23:09:50.4300781Z",
      "serviceAlias": "redacted",
      "machineName": "KEngine000035",
      "processName": "Kusto.WinSvc.Svc",
      "processId": 4836,
      "threadId": 9492,
      "appDomainName": "Kusto.WinSvc.Svc.exe",
      "activityStack": "(Empty activity stack)"
    },
    "@permanent": false
  }
}

I raised the issue with the team who built the plugin, they asked me to talk to the kusto team. I raised the issue to the kusto team, and I have a suspicion that they're going to ask me to raise it with the team behind the client I'm using, so I figured I'd parallelize.
This kind of error look familiar at all? Any chance I'm, like, somehow using the client incorrectly in a way that can be easily fixed?

I've managed to produce, a single error from the kusto web explorer, but I can't repro it.  ( :
I shifted the timespan on that query down from ago(35m) to ago(1m), and it threw an error evaluating the plugin, Message:An error occurred while sending the request., but every subsequent run, for that timespan or any other (down to ago(1s)), worked fine.  big shrug emoji

Can you please provide a request ID for such a failure? Thx

This is a problem outside the SDK.  Support suggested that he prepend: set query_take_max_records=1000;
That apparently took care of the issue.
If your interested Ziv, there is an ICM issue for this: https://portal.microsofticm.com/imp/v3/incidents/details/208378690/home
I'm going to close this issue as this doesn't look relevant to the Go SDK.  If there is some tweak needed Ziv, let me know.


Feature/vvalenti/gocart2g to gmi connectivity

Adding connectivity between GOCART2G aerosols and GMI. Make fields required by GMI available at Chem level (need fields from aerosols to be exported for GMI until GOCART2G provides new custom exports for GMI)

The following depend on this PR:
#2 in GMI
#254 in GEOSchem_GridComp

Changes no longer needed


Fix yarl version requirements

Closes #485
So weird that yarl installed an alpha release on CI but not on local testing in tox. Can't get it to install 1.4 even if I want it to.
Anyway... added version check to address the upcoming version support issue where yarl 1.4 only support >3.6

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@0d623ae). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #489   +/-   ##
=========================================
  Coverage          ?   89.39%
=========================================
  Files             ?       24
  Lines             ?     1546
  Branches          ?      215
=========================================
  Hits              ?     1382
  Misses            ?      135
  Partials          ?       29

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 0d623ae...dbd6f2c. Read the comment docs.


Cannot read property 'toString' of undefined

TypeError: Cannot read property 'toString' of undefined
    at Object.decode (/Users/luna/checkouts/patchwork/node_modules/ssb-conn-db/lib/atomic-file-codecs.js:9:27)
    at /Users/luna/checkouts/patchwork/node_modules/ssb-conn-db/lib/index.js:89:80
    at /Users/luna/checkouts/patchwork/node_modules/atomic-file-rw/browser.js:22:12
    at intercept (/Users/luna/checkouts/patchwork/node_modules/promisize/index.js:22:15)
    at IDBRequest.request.onsuccess (/Users/luna/checkouts/patchwork/node_modules/idb-kv-store/index.js:333:7)

added a simple fix for now:
9   decode: function (input) {
10      if (!input) return {};
11      const str = input.toString();

Oh yes, that's the right solution.


Yosys not removing DFF with constant input and replacing with a constant driver.

Version
Yosys 0.34+43 (git sha1 d21c464ae, gcc 9.4.0-1ubuntu1~20.04.2 -fPIC -Os)
On which OS did this happen?
Linux
Reproduction Steps

I have an rv32i cpu core design in verilog which I am trying to synthesize using Yosys targeting the sky130 library.
For ease of doing gate level simulation, I am currently hard-coding the instructions for the test program.
The synthesis commands used in Yosys is given below:
(Required files are attached at the end of the below section)

read_liberty -lib ./lib/sky130_fd_sc_hd__tt_025C_1v80.lib

read_verilog ./riscv_pipelined_Final.v

hierarchy -check -top riscv_core
synth -top riscv_core
stat

dfflibmap -liberty ./lib/sky130_fd_sc_hd__tt_025C_1v80.lib
opt
stat

abc -liberty ./lib/sky130_fd_sc_hd__tt_025C_1v80.lib -script +strash;scorr;ifraig;retime,{D};strash;dch,-f;map,-M,1,{D}
flatten
setundef -undriven -init -zero
opt_clean -purge
rename -enumerate
stat
write_verilog -noattr ./synth/riscv_pipelined_Final_netlist.v

Expected Behavior

DFF with constant input are reducible to a sequential constant, but it seems like Yosys is not removing some of the DFF with constant inputs in the design and replacing them with constant drivers.

Actual Behavior

While I was doing basic checks of the synthesis output netlist, I found that there are three DFF instances that have a constant input of 1'h0.

In the ABC result, I can see that there are three const0 cells (which I believe must correspond to the above three DFF instances

I even tried adding another opt command  (which should by default run opt_dff) after the abc command, but these 3 DFF instances with constant input are kept as is.

Please find attached the following:

Zip file with all files to repro the issue: yosys_issue_4266.zip

For taking a quick look, attaching some of the files directly here:

Yosys log file: yosys_synthesis_log.log
The generated netlist: riscv_pipelined_Final_netlist.txt
Source RTL: riscv_pipelined_Final.txt
Sky130 Lib file: sky130_fd_sc_hd__tt_025C_1v80.lib.txt

Attaching the verilog model files of the sky130 library cells.

sky130_fd_sc_hd.v.txt
primitives.v.txt

Snapshots of the verilog model DFF cell of concern below (sky130_fd_sc_hd__dfxtp_1) showing that these are simple DFF without any set/ reset inputs :

Hello Claire @clairexen ,
Could you kindly take a look and help figure out why this is happening and how it can be avoided ?

I could be wrong, but I think this is because opt_dff doesn't know that sky130_fd_sc_hd__dfxtp_1 is still a DFF and so doesn't optimise it, and it isn't until after the call to abc that the CPU_is_slti_a1 signal is optimised to 0 (and those 3 cells become driven by 1'h0).
Testing locally I had success with the following script:
read_liberty -lib ./lib/sky130_fd_sc_hd__tt_025C_1v80.lib

read_verilog ./riscv_pipelined_Final.v

hierarchy -check -top riscv_core
synth -top riscv_core
opt
stat

abc -script +strash;scorr;ifraig;retime,{D};strash;dch,-f;map,-M,1,{D}
flatten
setundef -undriven -init -zero
opt_clean -purge
opt
rename -enumerate
stat

dfflibmap -liberty ./lib/sky130_fd_sc_hd__tt_025C_1v80.lib
stat
write_verilog -noattr ./synth/riscv_pipelined_Final_netlist.v

Where abc runs on the yosys internal cells, allowing the call to opt afterwards to optimise out the constant-driven cells and then running dfflibmap at the end before output.

Thanks @KrystalDelusion !
I will try this out and get back to you tomorrow confirming whether or not this fits for me.

Hi @KrystalDelusion ,

Using the explanation that you had provided, I settled on the below sequence of steps:

read_liberty -lib ./lib/sky130_fd_sc_hd__tt_025C_1v80.lib

read_verilog ./riscv_pipelined_Final.v

hierarchy -check -top riscv_core
synth -top riscv_core -flatten
opt
stat

abc
opt
opt_clean -purge
stat

dfflibmap -liberty ./lib/sky130_fd_sc_hd__tt_025C_1v80.lib

abc -liberty ./lib/sky130_fd_sc_hd__tt_025C_1v80.lib -script +strash;scorr;ifraig;retime,{D};strash;dch,-f;map,-M,1,{D}
setundef -undriven -init -zero
opt
opt_clean -purge
rename -enumerate
stat

write_verilog -noattr ./synth/riscv_pipelined_Final_netlist.v

Attaching the log file using above steps for reference: yosys_issue_4266_fix.log

PS:
Sorry, it took me a while to get back.
I had another VirtualMachine running on my laptop that I could not open this VM for any work.

Using the explanation that you had provided, I settled on the below sequence of steps

I'll go ahead and close this issue then.

Is there way for me to tell Yosys to not optimize this section of the code in any manner ?

If you mark something with the "keep" attribute then it will prevent Yosys from optimising it out.  E.g.
// The program in an instruction memory.
(* keep *)
wire [31:0] instrs [0:12-1];
assign instrs[0] = {7'b0000000, 5'd0, 5'd0, 3'b000, 5'd10, 7'b0110011};
assign instrs[1] = {7'b0000000, 5'd0, 5'd0, 3'b000, 5'd15, 7'b0110011};
assign instrs[2] = {7'b0000000, 5'd0, 5'd0, 3'b000, 5'd14, 7'b0110011};
assign instrs[3] = {12'b1010, 5'd0, 3'b000, 5'd12, 7'b0010011};
assign instrs[4] = {7'b0000000, 5'd0, 5'd0, 3'b000, 5'd13, 7'b0110011};
assign instrs[5] = {7'b0000000, 5'd14, 5'd13, 3'b000, 5'd14, 7'b0110011};
assign instrs[6] = {12'b1, 5'd13, 3'b000, 5'd13, 7'b0010011};
assign instrs[7] = {1'b1, 6'b111111, 5'd12, 5'd13, 3'b100, 4'b1100, 1'b1, 7'b1100011};
assign instrs[8] = {7'b0000000, 5'd0, 5'd14, 3'b000, 5'd10, 7'b0110011};
assign instrs[9] = {7'b0000000, 5'd10, 5'd0, 3'b010, 5'b00100, 7'b0100011};
assign instrs[10] = {12'b00100, 5'd0, 3'b010, 5'd15, 7'b0000011};
assign instrs[11] = {1'b1, 10'b1111101010, 1'b1, 8'b11111111, 5'd7, 7'b1101111};

results in the following block in the output verilog:
assign \instrs[0]  = 32'd1331;
assign \instrs[10]  = 32'd4204419;
assign \instrs[11]  = 32'd4250924015;
assign \instrs[1]  = 32'd1971;
assign \instrs[2]  = 32'd1843;
assign \instrs[3]  = 32'd10487315;
assign \instrs[4]  = 32'd1715;
assign \instrs[5]  = 32'd15107891;
assign \instrs[6]  = 32'd1476243;
assign \instrs[7]  = 32'd4274441443;
assign \instrs[8]  = 32'd460083;
assign \instrs[9]  = 32'd10494499;

Thanks @KrystalDelusion !
For the (* keep *)  attribute, is there some other keyword to mark the end of the code section that is to be prevented from getting optimized out ?

Attributes don't apply to code sections, they apply to specific design elements (modules, wires and cells). In this case if it is set on a signal declaration, it ensures that a signal of this name remains in the design and is driven with the correct value. But it can optimize away anything in the input cone of the signal that is not necessary to produce the value, e.g. if you say (* keep *) wire foo = 3+5; it will not keep the adder, it will only keep a wire in the design driven directly by the constant 32'd8. If it finds another wire in the design that happens to have the same value it is also allowed to reconnect it to that wire instead.

Thanks @nakengelhardt !
Understood it clearly.
I was experimenting it out in Yosys after I posted the query and was able to get what I wanted by adding (* keep *) to some of the required signal declarations.


Pattern106 116

@aryashah2k
solution to symbol patterns 107-116 in python

Ive merged the PR but I was checking the issues, you had'nt assigned them to yourself?

No I wrote the code for them in python instead of Java so I created another PR for python as it was available.

No I wrote the code for them in python instead of Java so I created another PR for python as it was available. I'll make sure i get them assigned to me before creating a PR next time

Okay cool, I've counted this with appropriate tags and had assigned the issues for formality and have closed them as well!
Double win for you!!!


Undefined method 'devise' (OmniauthCallbasksController)

Hello, today I have tried to move my application to heroku for the first time, but when I want to open the page I get the following error. I am not using oauth functionality yet.
/app/app/controllers/users/omniauth_callbacks_controller.rb:3:in <class:OmniauthCallbacksController>': undefined method devise' for Users::OmniauthCallbacksController:Class (NoMethodError)
2015-07-30T14:35:17.790120+00:00 app[web.1]: 	from /app/app/controllers/users/omniauth_callbacks_controller.rb:1:in `<top (required)>'
It works just well on my locale environment.
Any idea what I have missed?
Thanks a lot,
Miroslav

Please use the mailing list or StackOverflow for questions/help, where a wider community will be able to help you. We reserve the issues tracker for issues only.


Add the ability to pass :no-phone=true so we only have the country se…

…lection

Everything seems to be behaving.  👏


Direct download of Phi-3/3.5 task on Kaggle

MediaPipe Solution (you are using)
LLM Inference
Programming language
Android Java/Kotlin
Are you willing to contribute it
None
Describe the feature and the current behaviour/state
Would it be possible to provide the phi-3.task or phi-3.5.task for download directly on Kaggle?
Will this change the current API? How?
No response
Who will benefit with this feature?
No response
Please specify the use cases for this feature
To use phi-3/3.5 in an easy way.
Any Other info
I followed the documentation to create the phi-3.5-mini.task, but when I built the app and entered a prompt on my Android phone, I encountered the following error:
2024-10-11 09:25:05.516 24523-24599 tflite     com...diapipe.examples.llminference  E  Encountered unresolved custom op: odml.update_external_kv_cache.
                                                                                See instructions: https://www.tensorflow.org/lite/guide/ops_custom
2024-10-11 09:25:05.516 24523-24599 tflite     com...diapipe.examples.llminference  E  Node number 40 (odml.update_external_kv_cache) failed to prepare.

I sought assistance in the ai-edge-torch repo, but it didn't resolve the issue:  https://github.com/google-ai-edge/ai-edge-torch/issues/293

Hi @chienhuikuo,
Unfortunately, the documentation you are following is not applicable to the Phi-3.5-mini, as we only support and have tested Phi-2. As a result, we may have limited ability to assist with this issue. However, we will mark this feature and share it with our team to see if we can offer any support.
Thank you!!

Hi @kuaashish,
Thank you for your reply.
As you mentioned that only Phi-2 is supported and has been tested, I tried to convert the Phi-2 TFLite model to a .task file following the sample code. However, I encountered an issue because I couldn't obtain the tokenizer.model from Hugging Face. The microsoft/phi-2 repository doesn't provide it.
I understand that we can use the genai.converter library to convert Phi-2 to get the phi2.bin, but I would like to go through the process of creating the .task file myself. Could you please advise me on how to obtain the tokenizer.model?

Hi @chienhuikuo,
Could you please try this official Colab example for converting the model to TFLite? You can also find this example in our documentation here.
Thank you!!


Change 'static' naming

the naming for static conflicts with the keyword static which i keep running into linting problems etc as it does not at all like that.
import { static as Immutable } from 'seamless-immutable'

this does appear to work but for example with flow you can not use static ANYWHERE

I am sure there are other places where this conflict will come into play in order to use the library in the recommended manner.
Perhaps instead something like
import { seamless as Immutable } from 'seamless-immutable'
// or
import { StaticImmutable } from 'seamless-immutable'
// or
import { I } from 'seamless-immutable' // supah short

or similar?
I would imagine you can keep the static export but would be good to have some sort of other option to use other than the static naming to do this.

Err yeah what's more is this basically completely breaks flow and the entire app - seamless-immutable can not go with flow when using the recommended way or every single file is an error automatically :(

Maybe we can export it under the alias functional or fp? From what I've seen that is pretty standard in community packages that have a functional version of their code.
For backwards compatibility it could be exported under static as well.


Port secrets for AWS and collections for Azure

Codecov Report
Base: 54.81% // Head: 54.81% // No change to project coverage :thumbsup:

Coverage data is based on head (af63aaf) compared to base (869fce9).
Patch has no changes to coverable lines.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@                   Coverage Diff                    @@
##           feat/framework-refactor     #379   +/-   ##
========================================================
  Coverage                    54.81%   54.81%
========================================================
  Files                           24       24
  Lines                         1578     1578
========================================================
  Hits                           865      865
  Misses                         649      649
  Partials                        64       64

Flag
Coverage Δ

unittests
54.81% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
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.


Site Down on Aug. 28th

The site went down seemingly randomly on August 28th. Django showed no error on its end and additionally the Docker cache had been reset. This may point to some reset of the machine on which Mexer runs.
We should ask Professor Weirenga if anything like that happened around that time.

This has been fixed and Docker will restart gracefully now.


Block Code PRs on the presence of a Docs PR

The merge bot should not merge PRs in kubernetes/kubernetes unless there is an accompanying Docs PR, or the PR has been marked as docs-not-required.

+1 - we seem to not be able to do it without enforcement.  Brian proposed to let all the OWNERS work finish before we muck with more gates :)  Also we should make sure it is possible to write good docs :)


GUI: make syntax page "no errors" more neat

Looks a bit strange,

This looks like a change which can be fixed by a novice like me. Can I work on it?

yea, sure 👍 guess few html/css fixes are needed, I have not looked at the details

:+1:
Please try to reuse existing css styles when possible.
Have a look at code inspector page. As far as i remember it renders green “no errors” panel on success, which should be very similar.

This is how the current screen looks in my abapgit. Is something changed?

I made a few changes by replicating the result of code inspector check to show a similar message if no syntax errors. I will create pull request if this looks fine.

looks good to me, much better than before

fixed by @Srinu3366, closing


feat(!): converts to typescript

Only named exports
No more CJS, only ESM
Adds auto-publish
Adds dependabot

BREAKING CHANGE: switch to named exports, ESM only

N.b. to get the auto-publish goodness, create a repository secret here called NPM_TOKEN with a npm automation token that can publish to is-loopback-addr.

Codecov Report

Merging #41 (ba7a2dd) into main (b6e4832) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main       #41   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            2         2
  Lines            3        48   +45
  Branches         0         7    +7
=========================================
+ Hits             3        48   +45

Impacted Files
Coverage Δ

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

test/index.spec.ts
100.00% <100.00%> (ø)

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 b6e4832...ba7a2dd. Read the comment docs.


Detailed dependency path for DependencyConflictException

Motivation:
See #73
VertxStacksTest will print something like the following when a DependencyConflictException occurs:
Note: In this case the conflicting artifacts io.vertx:vertx-web-templ-pug:4.4.8 and io.vertx:vertx-lang-kotlin:4.4.8 were chosen for the stack.
Conflict detected for artifact org.jetbrains:annotations:jar - version 15.0 was already selected by [io.vertx:vertx-web-templ-pug:jar:4.4.8] while io.vertx:vertx-lang-kotlin:jar:4.4.8 depends on version 13.0 - see the following chain:
io.vertx:vertx-lang-kotlin:jar:4.4.8
    \-- org.jetbrains.kotlin:kotlin-stdlib-jdk8:jar:1.7.21
        \-- org.jetbrains.kotlin:kotlin-stdlib:jar:1.7.21
            \-- org.jetbrains:annotations:jar:13.0

great work @oliver-brm can you backport to 4.x branch ?


Feature Request: Run e2e tests in arm64 architecture

As we do for amd64, run the e2e tests against arm64.

ping @kravciak: do you think this is now doable given e2e tests are stable on amd64?


Code indentation mistake found

Request type

[ ] Please close this issue, I accidentally submitted it without adding any details
[ ] New documentation
[x] Correction or update

Details

Hi, When I started reproducing your example code on my local machine, I noticed what I think is an overlooked indentation mistake. Specifically, it's the else block in the fetchAndDecode() function.
Hope my code illustrates...
function fetchAndDecode(url, type){
        return fetch(url).then(response => {
          if(!response.ok){
            throw new Error(`HTTP error! status: ${response.status}`);
          }
          else{
            if(type === "blob"){
              return response.blob();
            }
            else if(type === "text"){
              return response.text();
            }
          }
        })
        .catch(err => {....})
    }

Great work, Thanks.
Please close without hesitation if this is just a style difference.

https://developer.mozilla.org/en-US/docs/Learn/JavaScript/Asynchronous/Promises

Withdrawing this issue. Although I still believe that indentation level should convey meaning, my view on what that indentation looks like has been tempered a bit after using the 'Prettier' code standardisation tool.


Add django 3.1 support

Added support for Django 3.1
Dropped support for Python 2.7 and Python 3.4
Dropped support for Django < 2.2

Codecov Report

Merging #543 into master will decrease coverage by 0.57%.
The diff coverage is 60.00%.

@@            Coverage Diff             @@
##           master     #543      +/-   ##
==========================================
- Coverage   67.23%   66.66%   -0.58%
==========================================
  Files          14       14
  Lines         409      390      -19
  Branches       44       41       -3
==========================================
- Hits          275      260      -15
+ Misses        119      117       -2
+ Partials       15       13       -2

Impacted Files
Coverage Δ

djangocms_text_ckeditor/compat.py
60.00% <ø> (-15.00%)
:arrow_down:

djangocms_text_ckeditor/migrations/0001_initial.py
100.00% <ø> (ø)

...ions/0002_remove_related_name_for_cmsplugin_ptr.py
100.00% <ø> (ø)

...rations/0003_set_related_name_for_cmsplugin_ptr.py
100.00% <ø> (ø)

...ext_ckeditor/migrations/0004_auto_20160706_1339.py
28.57% <ø> (-2.47%)
:arrow_down:

...ditor/templatetags/djangocms_text_ckeditor_tags.py
100.00% <ø> (+13.33%)
:arrow_up:

djangocms_text_ckeditor/html.py
45.05% <33.33%> (ø)

djangocms_text_ckeditor/utils.py
89.01% <100.00%> (-0.12%)
:arrow_down:

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 f8dc530...788f064. Read the comment docs.

If you drop support for Python<3.5 and Django<2.2 I would also:

remove # -*- coding: utf-8 -*- on top of each file.
replace django.utils.translation.ugettext_lazy against django.utils.translation.gettext_lazy
simplify super(...) calls, using Python-3 syntax.

If you drop support for Python<3.5 and Django<2.2 I would also:

remove # -*- coding: utf-8 -*- on top of each file.
replace django.utils.translation.ugettext_lazy against django.utils.translation.gettext_lazy
simplify super(...) calls, using Python-3 syntax.

@jakob-o thanks for the feedback:

I'll change ugettext_lazy to gettext_lazy
With super you mean using class instead of the hardcoded name?
Will probably also remove "# -- coding: utf-8 --"

With super you mean using class instead of the hardcoded name?

No, I mean to change, for example
https://github.com/divio/djangocms-text-ckeditor/blob/afb41bd8858269682c7a4cd8da83792109f81b5c/djangocms_text_ckeditor/models.py#L75
to super().save(update_fields=('body',))
The old syntax is only required for grandpa-super.
btw. I'm @jrief :)

@jrief sorry (stupid autocomplete), sure will update it accordingly, thanks for the feedback

@yakky or @jrief this is also ready to be merged. Looking forward to your review and approval.

@victor-yunenko or @Aiky30 maybe I can get a 👍  from you?


Temperature correction in WebConfig - -Feedback for Webinstaller alpha

Hi Riccardo,
thank you so much that we can now update our Trackers also with webinstaller and can config this on WebBrowser.
But one small issue:
i need a correction of the temperature (and also the humidity), but the Webconfig does only allow positive values. I need a negative value, e.g. temperature -5.
Some feedback for the Webinstaller:

it works on the first flashing ! and that great well, thank you!!!! (my HW SX1268)
would it be possible that the tracker can join another WLAN? after 3times pushing the button, not only choose WIFI AP but also choose another WIFI which is already configed
may it be possible to change the message-text via WebConfig for the APRSthursday? that would be great !
and would it be possible to add a correction for the humidity

73 DC4FRT, Thomas

Humidity: it looks also like an offset failure. I have this also on my BME in the iGate. until 10% difference. And yes, i guess that they are o.k. but they have also on humidity an offset failure.
Wifi-connect: to change parameters on Smartphone is o.k. but to do this on my PC with big monitor is more comfortable :-)
Maybe for future: to send also messages over this website, cause i have no KeyBoard and maybe as an alternative to bluetooth connection and an additional app.
73 Thomas

@DC4FRT please explain me again the last part of the PC connection
so, all need Hum and Temp correction...

change parameters would be more comforable if you can do this on PC when the tracker is in your local network. To start this WLAN connection you can do this as today, after 3times pushing the button then you can choose a.) AP or b.) WLAN Access
feature could also be to send APRS messages over this webside. like message to CA2RXU over the tracker: "Hello how are you" :-) like example: https://www.findu.com/cgi-bin/entermsg.cgi but not send the message over internet but over the tracker if it is in the local Wireless lan. I know, we can do this over KeyBoard (but how i said, many cables and i do not have this). or bluetooth, but there you need an additional app.

temperature now with +-5 correction added
will take a while to add the hum, because I wanted to add another updates sooner ;) but will return for this


first commit

@kelockhart
Thank you for your comments. But you know, some of the issues you bring up, I don't know the answer to, for example, how often to update the synonyms file. So I am going to compile these and make it an issue for you/Alberto and anyone else in the know to answer them.

You said you only checked out the unittests. If you have time or inclination to check it out more, I am not going to have time to work on this until second week of August. So feel free to look some more and post feedback. There are two issues that I need a bit more explanation on, and two issues that we need to chat about since I dont know the answer. Thank you for check this out.

@kelockhart
OK, addressed all the comments. Please check it out and if OK merge it.
I will start working on populating the database as soon as @tjacovich give me the address to the database.
Would you create the deployed ymls?


Promise is not resolved on browser reload - Edit Identity

Describe the bug
When browser is reloaded the edit identity is not working due to the schema promise is not resolved.
https://github.com/dfoxg/kratos-admin-ui/blob/0977adc5c331b4240c55d2c0e0ac1d7c3e90f420/kratos-admin-ui/src/service/schema-service.ts#L39-L44
But the edit.tsx expects the schema which is not resolved sometimes and schema is undefined - may be network issue
https://github.com/dfoxg/kratos-admin-ui/blob/0977adc5c331b4240c55d2c0e0ac1d7c3e90f420/kratos-admin-ui/src/sites/identities/edit/edit.tsx#L40-L42
To Reproduce
Steps to reproduce the behavior:

Select Identity and click edit
Reload the page
See error

schema-service.ts:50 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'properties')
    at SchemaService.getSchemaFields (schema-service.ts:50:1)
    at EditIdentitySite.mapEntity (edit.tsx:42:1)

Thanks @anupriya17, I will look at it :)


missing translated habitat text related to Plazi's Treatment XML

more info to be added

see related issues #175


GitHub Enterprise support

Hi, is this action comptabile with GitHub Enterprise? When I try to use it, I receive the following error:
ℹ  info      Creating tree
Error: Bad credentials

✖  fatal     HttpError: Bad credentials
    at /mnt/data/actions-runner/_work/_actions/internal-marketplace/build-and-tag-action/v2/dist/index.js:4476:23
    at processTicksAndRejections (internal/process/task_queues.js:[9](https://code.rbi.tech/raiffeisen/wzhgaho-merlin-gha-helper/runs/307969?check_suite_focus=true#step:5:10)7:5)
    at async Object.createCommit [as default] (/mnt/data/actions-runner/_work/_actions/internal-marketplace/build-and-tag-action/v2/dist/index.js:17383:18)
    at async buildAndTagAction (/mnt/data/actions-runner/_work/_actions/internal-marketplace/build-and-tag-action/v2/dist/index.js:17492:20)

My configuration:
name: publish

on:
  release:
    types: [published, edited]

env:
  NODE_EXTRA_CA_CERTS: /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem

jobs:
  publish:
    runs-on: [ self-hosted, build-testtenant ]
    permissions: write-all
    steps:
      - name: Checkout
        uses: actions/checkout@v2
        with:
          ref: ${{ github.event.release.tag_name }}
      - uses: actions/setup-node@v3
        with:
          node-version: 16
      - name: Install deps and build
        run: npm ci && npm run build
      - uses: internal-marketplace/build-and-tag-action@v2
        env:
          DEBUG: '*'
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

I'm pretty sure I hand over correctly the token. The issue is somewhere here, with the createTree API.
https://github.com/JasonEtco/build-and-tag-action/blob/main/src/lib/create-commit.ts#L11
Should this action work with GHES 3.6?
Thank you.

After adding NODE_DEBUG: http environment variable to my workflow, I can clearly see that the action is talking to api.github.com and not to my GHES instance. I tried to set GITHUB_API_URL as this commit suggests, but did not helped.
Can you please add GHES support?

I've got this working and interacting with my GitHub Enterprise Server, but its not only a fix here.
Working backwards, this code relies on https://github.com/JasonEtco/actions-toolkit where we use the run method here: https://github.com/JasonEtco/build-and-tag-action/blob/8aebd433ae6d9f3d7433205d11740c3f5163db8e/src/index.ts#L4
The constructor then create the github property using the Octokit class here: https://github.com/JasonEtco/actions-toolkit/blob/c6c7208c521db3b7418dbc9cf5eab282a501250e/src/index.ts#L142
This Octokit object was the issue, it doesn't know how to reach my GitHub Enterprise Server
In my copy of the code, I changed this
    this.github = new Octokit({ auth: `token ${this.token}` })

becomes
this.github = new Octokit({
  auth: `token ${this.token}`,
  baseUrl:  `${process.env.GITHUB_URL}api/v3`
})

With this change, the Octokit object now knows how to reach my enterprise server


[FLINK-12754][table-api]alterTableColumnStatistics() in GenericInMemo…

…ryCatalog should ensure the table is non-partitioned

What is the purpose of the change
alterTableColumnStatistics() in GenericInMemoryCatalog should ensure the table is non-partitioned
Verifying this change
This change is already covered by existing tests, such as CatalogTest.testAlterTableStats_partitionedTable().
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)

Failed reason is "GET request of: org/apache/avro/avro/1.8.2/avro-1.8.2.jar from google-maven-central failed -> [Help 1]" build for flink-avro.


Review advanced audio settings

[ ] make ptime configurable
[ ] make stereo configurable
[ ] make Settings-UI cleaner and more intuitive
[x] audio output selection
[x] echo cancellation not working properly?

Fixed in new client


like() returns error 400

Hi,
I just tried this great project and I'm very exited about :) But a little problem appeared, after a successful auth (and some config to display requests details):
In [33]: tinder_api.like("583b4a3be6230d9d08761381")
INFO:requests.packages.urllib3.connectionpool:Starting new HTTPS connection (1): api.gotinder.com
send: 'GET /like/583b4a3be6230d9d08761381 HTTP/1.1\r\nHost: api.gotinder.com\r\napp_version: 6.9.4\r\nAccept-Encoding: gzip, deflate\r\nAccept: application/json\r\nX-Auth-Token: xxxxx-xxxxxx-xxxxxx\r\nplatform: ios\r\nConnection: keep-alive\r\nUser-agent: Tinder/7.5.3 (iPhone; iOS 10.3.2; Scale/2.00)\r\ncontent-type: application/json\r\n\r\n'get_person
reply: 'HTTP/1.1 400 Bad Request\r\n'
header: Content-Type: application/json; charset=utf-8
header: Date: Fri, 15 Feb 2019 01:14:37 GMT
header: X-Request-ID: b8tqs3k7qpju5afs8gg0
header: Content-Length: 42
header: Connection: keep-alive
DEBUG:requests.packages.urllib3.connectionpool:"GET /like/583b4a3be6230d9d08761381 HTTP/1.1" 400 42
Out[33]: {u'error': u'malformed request', u'status': 400}

In the other hand, tinder_api.get_person("583b4a3be6230d9d08761381") works well. get_meta(), get_self() works too.

after using paul-at's commit, i am faced with this is the json response from the like function:
{
"X-Padding": "{meta:{code:200,requestId:59a45921351e3d43b07028b5},response:{venue:{id:412d2800f964a520df0c1fe3,name:Central Park,contact:{phone:2123106600,formattedPhone:(212) 310-6600,twitter:centralparknyc,instagram:centralparknyc,facebook:37965424481,facebookUsername:centralparknyc,facebookName:Central Park},location:{address:59th St to 110th St,crossStreet:5th Ave to Central Park West,lat:40.78408342593807,lng:-73.96485328674316,postalCode:10028,cc:US,city:New York,state:NY,country:United States,formattedAddress:[59th St to 110th St (5th Ave to Central Park West),New York, NY 10028,United States]},canonicalUrl:*https://foursquare.com/v/central-park/412d2800f964a520df0c1fe3*,*categories*:[{*id*:*4bf58dd8d48988d163941735*,*name*:*Park*,*pluralName*:*Parks*,*shortName*:*Park*,*icon*:{*prefix*:*https://ss3.4sqi.net/img/categories_v2/parks_outdoors/park_*,*suffix*:*.png*},*primary*:true}],*verified*:true,*stats*:{*checkinsCount*:364591,*usersCount*:311634,*tipCount*:1583,*visitsCount*:854553},*url*:*http://www.centralparknyc.org*,*likes*:{count:17370,summary:17370 Likes},rating:9.8,ratingColor:00B551,ratingSignals:18854,beenHere:{count:0,unconfirmedCount:0,marked:false,lastCheckinExpiredAt:0},photos:{count:26681,groups:[{type:venue,name:Venue photos,count:26681,items:[{id:513bd223e4b0e8ef8292ee54,createdAt:1362874915,source:{name:Instagram,url:http://instagram.com},prefix:*https://igx.4sqi.net/img/general/*,*suffix*:*/655018_Zp3vA90Sy4IIDApvfAo5KnDItoV0uEDZeST7bWT-qzk",
"likes_remaining": 100,
"match": false
}
every call to the like function produces this same output.

Don’t include your phone number 🤦♂
Sent from my iPhone

On Feb 26, 2019, at 8:49 PM, cdangerdouglas<EMAIL_ADDRESS>wrote:
after using paul-at's commit, i am faced with this is the json response from the like function:
{
"X-Padding": "{meta:{code:200,requestId:59a45921351e3d43b07028b5},response:{venue:{id:412d2800f964a520df0c1fe3,name:Central Park,contact:{phone:2123106600,formattedPhone:(212) 310-6600,twitter:centralparknyc,instagram:centralparknyc,facebook:37965424481,facebookUsername:centralparknyc,facebookName:Central Park},location:{address:59th St to 110th St,crossStreet:5th Ave to Central Park West,lat:40.78408342593807,lng:-73.96485328674316,postalCode:10028,cc:US,city:New York,state:NY,country:United States,formattedAddress:[59th St to 110th St (5th Ave to Central Park West),New York, NY 10028,United States]},canonicalUrl:https://foursquare.com/v/central-park/412d2800f964a520df0c1fe3*,categories:[{id:4bf58dd8d48988d163941735,name:Park,pluralName:Parks,shortName:Park,icon:{prefix:https://ss3.4sqi.net/img/categories_v2/parks_outdoors/park_*,*suffix*:*.png},primary:true}],verified:true,stats:{checkinsCount:364591,usersCount:311634,tipCount:1583,visitsCount:854553},url:http://www.centralparknyc.org,likes:{count:17370,summary:17370 Likes},rating:9.8,ratingColor:00B551,ratingSignals:18854,beenHere:{count:0,unconfirmedCount:0,marked:false,lastCheckinExpiredAt:0},photos:{count:26681,groups:[{type:venue,name:Venue photos,count:26681,items:[{id:513bd223e4b0e8ef8292ee54,createdAt:1362874915,source:{name:Instagram,url:http://instagram.com},prefix:https://igx.4sqi.net/img/general/,suffix:/655018_Zp3vA90Sy4IIDApvfAo5KnDItoV0uEDZeST7bWT-qzk",
"likes_remaining": 100,
"match": false
}
every call to the like function produces this same output.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

My phone number is not in there. That is maybe the phone number for Central Park?
Im not sure what this response is.

@paul-at https://github.com/fbessez/Tinder/pull/64 solves the problem

@brunetton Is tinder_api.get_person() still works?


Mouse not working

Describe the bug
Mouse doesn't work when going full screen when hovering over title bar.
To Reproduce
Steps to reproduce the behavior:
2. Hover the mouse over the title bar
3. Press Ctrl+Alt+Enter to enter full screen
4. Mouse not working
Expected behavior
The mouse should work
Screenshots
no
Application details

FreeRDP version：2.11.8-dev（0c20fac8f1deeeca3df93a6619542e5d9176f0f0）

Command line used：xfreerdp /u:xxx /v:xxx /p:xxx /f

Output of xfreerdp /buildconfig:
This is FreeRDP version 2.11.8-dev (0c20fac8f)
Build configuration: BUILD_TESTING=OFF BUILTIN_CHANNELS=ON HAVE_AF_VSOCK_H= HAVE_AIO_H=1 HAVE_EXECINFO_BACKTRACE=1 HAVE_EXECINFO_BACKTRACE_SYMBOLS=1 HAVE_EXECINFO_BACKTRACE_SYMBOLS_FD=1 HAVE_EXECINFO_H=ON HAVE_EXECINFO_HEADER=1 HAVE_FCNTL_H=1 HAVE_GETLOGIN_R=1 HAVE_GETPWUID_R=1 HAVE_INTTYPES_H=1 HAVE_JOURNALD_H=TRUE HAVE_MATH_C99_LONG_DOUBLE=1 HAVE_PIXMAN_REGION=OFF HAVE_POLL_H=1 HAVE_PTHREAD_MUTEX_TIMEDLOCK=ON HAVE_PTHREAD_MUTEX_TIMEDLOCK_LIB=1 HAVE_PTHREAD_MUTEX_TIMEDLOCK_SYMBOL= HAVE_SYSLOG_H=1 HAVE_SYS_EVENTFD_H=1 HAVE_SYS_FILIO_H= HAVE_SYS_MODEM_H= HAVE_SYS_SELECT_H=1 HAVE_SYS_SOCKIO_H= HAVE_SYS_STRTIO_H= HAVE_SYS_TIMERFD_H=1 HAVE_TM_GMTOFF=1 HAVE_UNISTD_H=1 HAVE_XI_TOUCH_CLASS=1 WITH_AAD=ON WITH_ABSOLUTE_PLUGIN_LOAD_PATHS=ON WITH_ADD_PLUGIN_TO_RPATH=OFF WITH_ALSA=ON WITH_BINARY_VERSIONING=OFF WITH_CAIRO=OFF WITH_CCACHE=ON WITH_CHANNELS=ON WITH_CLANG_FORMAT=ON WITH_CLIENT=ON WITH_CLIENT_AVAILABLE=1 WITH_CLIENT_CHANNELS=ON WITH_CLIENT_CHANNELS_AVAILABLE=1 WITH_CLIENT_COMMON=ON WITH_CLIENT_INTERFACE=OFF WITH_CLIENT_SDL=OFF WITH_CUPS=ON WITH_DEBUG_ALL=OFF WITH_DEBUG_CAPABILITIES=OFF WITH_DEBUG_CERTIFICATE=OFF WITH_DEBUG_CHANNELS=OFF WITH_DEBUG_CLIPRDR=OFF WITH_DEBUG_CODECS=OFF WITH_DEBUG_DVC=OFF WITH_DEBUG_EVENTS=OFF WITH_DEBUG_KBD=OFF WITH_DEBUG_LICENSE=OFF WITH_DEBUG_MUTEX=OFF WITH_DEBUG_NEGO=OFF WITH_DEBUG_NLA=OFF WITH_DEBUG_NTLM=OFF WITH_DEBUG_RAIL=OFF WITH_DEBUG_RDP=OFF WITH_DEBUG_RDPDR=OFF WITH_DEBUG_RDPEI=OFF WITH_DEBUG_RDPGFX=OFF WITH_DEBUG_REDIR=OFF WITH_DEBUG_RFX=OFF WITH_DEBUG_RINGBUFFER=OFF WITH_DEBUG_SCARD=OFF WITH_DEBUG_SCHANNEL=OFF WITH_DEBUG_SDL_EVENTS=OFF WITH_DEBUG_SDL_KBD_EVENTS=OFF WITH_DEBUG_SND=OFF WITH_DEBUG_SVC=OFF WITH_DEBUG_SYMBOLS=OFF WITH_DEBUG_THREADS=OFF WITH_DEBUG_TIMEZONE=OFF WITH_DEBUG_TRANSPORT=OFF WITH_DEBUG_TSG=OFF WITH_DEBUG_TSMF=OFF WITH_DEBUG_TSMF=OFF WITH_DEBUG_TSMF_AVAILABLE=0 WITH_DEBUG_URBDRC=OFF WITH_DEBUG_WND=OFF WITH_DEBUG_X11=OFF WITH_DEBUG_X11_CLIPRDR=OFF WITH_DEBUG_X11_LOCAL_MOVESIZE=OFF WITH_DEBUG_XV=OFF WITH_DSP_EXPERIMENTAL=OFF WITH_DSP_FFMPEG=ON WITH_EVENTFD_READ_WRITE=1 WITH_FAAC=OFF WITH_FAAD2=OFF WITH_FFMPEG=TRUE WITH_FFMPEG=TRUE WITH_FREERDP_DEPRECATED=OFF WITH_FREERDP_DEPRECATED_COMMANDLINE=OFF WITH_FUSE=ON WITH_GFX_H264=ON WITH_GPROF=OFF WITH_GSM=OFF WITH_GSSAPI=OFF WITH_ICU=OFF WITH_INTERNAL_MD4=OFF WITH_INTERNAL_MD5=OFF WITH_INTERNAL_RC4=OFF WITH_IPP=OFF WITH_JPEG=OFF WITH_KRB5=ON WITH_KRB5_NO_NTLM_FALLBACK=OFF WITH_LAME=OFF WITH_LIBRARY_VERSIONING=ON WITH_LIBRARY_VERSIONING=ON WITH_LIBRESSL=OFF WITH_LIBSYSTEMD=ON WITH_LODEPNG=OFF WITH_MACAUDIO=OFF WITH_MACAUDIO=OFF WITH_MACAUDIO_AVAILABLE=0 WITH_MANPAGES=ON WITH_MBEDTLS=OFF WITH_NATIVE_SSPI=OFF WITH_NEON=OFF WITH_OPAQUE_SETTINGS=OFF WITH_OPENCL=OFF WITH_OPENH264=OFF WITH_OPENSC_PKCS11_LINKED=OFF WITH_OPENSLES=OFF WITH_OPENSSL=ON WITH_OPUS=OFF WITH_OSS=ON WITH_PAM=ON WITH_PCSC=ON WITH_PKCS11=ON WITH_PLATFORM_SERVER=ON WITH_POLL=ON WITH_PROFILER=OFF WITH_PROXY=ON WITH_PROXY_APP=ON WITH_PROXY_EMULATE_SMARTCARD=OFF WITH_PROXY_MODULES=ON WITH_PULSE=OFF WITH_RDTK=ON WITH_SAMPLE=ON WITH_SANITIZE_ADDRESS=OFF WITH_SANITIZE_ADDRESS_AVAILABLE=1 WITH_SANITIZE_MEMORY=OFF WITH_SANITIZE_MEMORY_AVAILABLE=1 WITH_SANITIZE_THREAD=OFF WITH_SANITIZE_THREAD_AVAILABLE=1 WITH_SDL=OFF WITH_SDL_IMAGE_DIALOGS=OFF WITH_SDL_LINK_SHARED=ON WITH_SERVER=ON WITH_SERVER_CHANNELS=ON WITH_SERVER_INTERFACE=ON WITH_SHADOW=ON WITH_SMARTCARD_EMULATE=ON WITH_SMARTCARD_INSPECT=OFF WITH_SMARTCARD_PCSC=ON WITH_SOXR=OFF WITH_SSE2=OFF WITH_SWSCALE=ON WITH_SYSTEMD=ON WITH_THIRD_PARTY=OFF WITH_UNICODE_BUILTIN=OFF WITH_URIPARSER=OFF WITH_VAAPI=OFF WITH_VALGRIND_MEMCHECK=OFF WITH_VALGRIND_MEMCHECK_AVAILABLE=1 WITH_VERBOSE_WINPR_ASSERT=ON WITH_VIDEO_FFMPEG=ON WITH_WAYLAND=ON WITH_WEBVIEW=ON WITH_WEBVIEW_QT=OFF WITH_WINPR_DEPRECATED=OFF WITH_WINPR_TOOLS=ON WITH_WIN_CONSOLE=ON WITH_X11=ON WITH_XCURSOR=ON WITH_XDAMAGE=ON WITH_XEXT=ON WITH_XFIXES=ON WITH_XI=ON WITH_XINERAMA=ON WITH_XKBFILE=ON WITH_XRANDR=ON WITH_XRENDER=ON WITH_XSHM=ON WITH_XTEST=ON WITH_XV=ON WITH_ZLIB=ON
Build type:          Release
CFLAGS:               -Wall -Wno-unused-result -Wno-unused-but-set-variable -Wno-deprecated-declarations -fvisibility=hidden -Wimplicit-function-declaration -Wredundant-decls -fno-omit-frame-pointer -DWINPR_DLL
Compiler:            GNU, 8.3.0
Target architecture:

OS version connecting to (server side): win2016(any version)

cmake command-line: cmake ..

Environment (please complete the following information):

OS: linux(UOS, debian based)
Version/Distribution: 4.19.71-arm64-desktop
Architecture: arm

Additional context
Keyboard works fine. The mouse works fine when going full screen, provided it is not hovering over the title bar.

not reproducible and from the description most likely not a FreeRDP bug.
(note: mouse handling is up to X11 we only forward the move and button events.

Resoved by remapping window in function xf_toggle_fullscreen。

I found that freerdp-stable-1.1 enter fullscreen by recreating window, and it works fine.

It may not

not reproducible and from the description most likely not a FreeRDP bug. (note: mouse handling is up to X11 we only forward the move and button events.

Yes, I cannot reproduce it another UOS(amd64). Thanks for your support.

@JSSSSSSSSSS this sounds like a windowmanager bug and some ancient workaround fixes it?
which window manager do you use?


compute_hash_on_elements could accept any iterator on FieldElement

https://github.com/xJonathanLEI/starknet-rs/blob/d980869d44ef86249b4077f4ec809165f470678d/starknet-core/src/crypto.rs#L49
Right now the signature requires the input to be &[FieldElement] but it's implementation would still be valid if the input were to be a more generic T: Iter<FieldElement>. It would allow more flexibility for the lib users

The issue with Iterator<FieldElement> is then you can't use say slices they yield &FieldElement instead of FieldELement.

What we could do is maybe T: AsRef<[FieldElement]>? This way you can send in anything that can be referenced as a slice, but then... if you can reference it as a slice you could have just passed in the slice like you do right now.
The only benefit of this change, as far as I know, is that you can now also pass in owned values, which could be useful in a threading scenario. Not that it's not useful in certain cases, but it's probably not what you're looking for.

Oh the other than, we can indeed provide a hasher type which would actually work better with iterators? Such a hasher would probably be rather generic and won't hash the arrary length at the end though.

https://rust-lang.github.io/api-guidelines/flexibility.html#functions-minimize-assumptions-about-parameters-by-using-generics-c-generic
T: IntoIterator<Item = FieldElement> requires you to have ownership of the value, if you want to pass a slice, you can do so:
compute_hash_on_elements(my_slice.into_iter().cloned())

This ensures you own the value you are passing in.


feat:Kubeblocks pika-master-slave-group

Added the kubeblocks master/slave configuration,but still some bugs need to be solve,it will be continuously updat

Summary by CodeRabbit

New Features

Introduced new Helm charts for Pika Master-Slave Group and Pika Cluster, enhancing deployment options in Kubernetes.
Added dynamic namespace assignments and templated service versions across various component definitions for better configurability.
Implemented a new configuration template for the Pika database to streamline setup and management.

Improvements

Updated existing Helm charts to improve formatting and consistency.
Enhanced resource management with new volume and persistence settings in component definitions.

Bug Fixes

Minor formatting corrections in documentation files for clarity.

Documentation

Added README updates to reflect changes and new features in the Helm charts.

In the future,plan to use job resources instead of mounting sript scripts to implement master/slave binding or cluster pika-group control.
Implementation details are still under discussion.


Add emit support for jsx/jsxs experimental jsx runtime api

This adds two new options for the jsx compiler option - react-jsx, and react-jsxdev. They use the jsx and jsxDEV constructors and the react/jsx-runtime and react/jsx-dev-runtime entrypoints, respectively. The primary differences, as noted in the linked issue, are that children are passed as part of the props object, and the key is passed as a separate argument. (The jsxDEV constructor further takes some debug data.) In addition, this adds a jsxImportSource compiler option (and @jsxImportSource file pragma) to control the root specifier the jsx runtime is imported from (which defaults to react). In it's current state, I believe this is usable, but there are some known flaws:

The checker/program need to load the jsxImportSource module and use it as the source for the JSX namespace automatically. Presently you need to include it in the program yourself (ie, with a types directive or compiler option). This is moreso a TODO for myself, since I don't think there's any question to what we should do (implicitly include the package or @types version in the program). This is more interesting for the jsxImportSource pragma, which, for all intents and purposes, is an import statement. We have a lot of services for real import statements - should they be applied to the pragma, where possible?
Babel additionally supports a jsxRuntime pragma (with values classic or automatic) to swap between the old emit and the new one. This is supportable; however currently I only key our emit off the jsx compiler option, and the presence of the jsxImportSource pragma.
In some cases, the new transform still falls back to createElement (when a key prop follows a spread) - this is a kind of soft deprecation; however it still implicitly imports the jsx runtime and pulls in createElement. This PR does not yet do this, as, awkwardly enough, the module createElement is supposed to come from is different from the jsx-runtime module entrypoint. I could make this work, but I think this is something we should provide some feedback on - so long as there's still a createElement fallback required in the API, why can't it be exported by the same entrypoint exporting jsx or jsxDEV?
Without an import or export, a file is not marked as a module, and will not have an import automatically added. Should this issue an error? Or should, under these jsx modes, the presence of a jsx tag imply module-ness?

Fixes #34547
This is currently experimental in babel, and AFAIK not yet supported in a stable version of react; as such, we should probably continue to experiment with it for awhile before merging it into a stable release.
TL;DR
When jsx: react-jsx (and target: esnext) is set,
export default (props: {className: string}) =>
childtext

compiles to
import { jsx as _jsx } from "react/jsx-runtime";
export default (props) => _jsx("div", Object.assign({ className: props.className }, { children: "childtext" }), "stablekey");

@typescript-bot pack this

The checker/program need to load the jsxImportSource module and use it as the source for the JSX namespace automatically.

This is an interesting piece of information for me - or it might be. Could you clarify for me if this works on per-config basis (or per-file when using @jsxImportSource)? In other words - could one compile a library with a particular JSX namespace for it but later have it consumed by an application with other JSX namespace "defined" for it and one would not affect the other?
Right now JSX "pollutes" the global namespace and AFAIK what I'm talking about is not possible.

Right now JSX "pollutes" the global namespace and AFAIK what I'm talking about is not possible.

We actually already support localized JSX namespaces (and therefore loading multiple into a project (and using them via pragmas)) - react just makes a global one (which we also still support for ecosystem compatibility). We'll look for a JSX member on the root of the factory function. Eg, if the factory is defined as React.createElement, we'll check for React.JSX.

Huh, that's great to hear - I will have to experiment with how it behaves to get a better feeling of how it works in various situations. 👍
Do you happen to know when the support for this was added? If @types/react would be to remove the global namespace in favor of a localized one then how much of a breaking change that would be?
With this PR it would be great to be able to customize the jsxImportSource in tsconfig.json. It seems a real bummer that the config only allows a strict set of values and it enforces the usage of pragma for all the other modules.

Do you happen to know when the support for this was added?

Same time as support for per-file @jsx pragmas.

If @types/react would be to remove the global namespace in favor of a localized one then how much of a breaking change that would be?

Pretty bad, I think. There's a lot of JSX.IntrinsicElements references out there that assume react.

This is awesome - I have been searching for a way to define such local JSX namespace for a while and wasn't aware that this is already implemented!
I've played a little bit with it and it seems to work pretty well - I only have one caveat with it: it doesn't support /** @jsx jsx */ as it's not a member expression. Or at least I couldn't figure out how to make it work. As the whole thing only seems to work with namespaces anyway as you can't really put types onto runtime values - would it be possible to extend the support for it in a way that if a particular simple binding that is used as a pragma is imported from a module then this would check if the module itself exports JSX? I might be wrong - but the change seems quite logical and shouldn't be that hard to implement, given the fact that the whole notion of localized JSX is already implemented. I could even try to implement support for this myself. Would that be something that TS team could endorse?

@typescript-bot pack this

Would it be possible for you to support a new option (existing "jsx" would have slightly conflicting semantics with it), smth like jsxImportSource? I'm a maintainer of Emotion - a popular CSS-in-JS library and we recommend people to use our pragma approach for styling which works great and a tip from this thread by @weswigham has even allowed us to add more proper type-checking for our css prop API, but many users are complaining about having to add pragma manually over the place. It would really make a difference for us if this could be configured globally per tsconfig.json project

I've opened https://github.com/microsoft/TypeScript/issues/40502 and https://github.com/microsoft/TypeScript/issues/40501 as followups to this PR to further refine the experience offered. I'm going to merge this as-is so we start getting feedback on the meat of the implementation (the emit code) during the upcoming nightlies and beta.

Question: Why vscode shows me Value is not accepted. Valid values: "preserve", "react", "react-native" and not recognizing react-jsx reacxt-jsxdev variables and keeps throwing me
Cannot use JSX unless the '--jsx' flag is provided error where I'm using JSX syntax in my code

Question: Why vscode shows me Value is not accepted. Valid values: "preserve", "react", "react-native" and not recognizing react-jsx reacxt-jsxdev variables and keeps throwing me
Cannot use JSX unless the '--jsx' flag is provided error where I'm using JSX syntax in my code

Hello @devarsh,
Using the workspace version of TypeScript may help.

Question: Why vscode shows me Value is not accepted. Valid values: "preserve", "react", "react-native" and not recognizing react-jsx reacxt-jsxdev variables and keeps throwing me

Cannot use JSX unless the '--jsx' flag is provided error where I'm using JSX syntax in my code

Hello @devarsh,
Using the workspace version of TypeScript may help.

Thanks this worked. I figured vscode was using an current stable version and not next 😊

@weswigham  The fallback to createElement should be createElement of @jsxImportSource.
https://www.typescriptlang.org/play?ts=4.1.0-dev.20201015#code/PQKhAIAECsGcA8CSBbADgewE4BcDK6BXTAYwFNxVNSBDY7cEYAKCYB5ZVqA7cAbwDpBldKlgBfcMAB8Ldpx4BrUgE8AvACJq6voP7DRE6bI7cdQzCPHgla9QBNqsbdKA
if using React.createElement, it is a different results from babel, and will broken react-like lib.
https://github.com/facebook/react/issues/20031#issuecomment-709550075

Note https://github.com/microsoft/TypeScript/issues/41146 is critical to fix not only for React-like libs, but for React itself too, since it would otherwise lead to a non-existent reference being emitted.

I have started looking into fixing this - doesn't look overly complicated but I haven't contributed much to the codebase, so we'll see how it goes.

@gaearon I've implemented this locally already - however, I've discovered that I will have to adjust the implementation further. I'll probably wrap this up tomorrow, but I've wanted to report back here, especially because of the obstacle I've encountered. TS compiler currently assumes that all imports that have to inserted comes from a single entry and thus after my changes the createElement gets imported from 'whatever/jsx-runtime.js'. This seems like a good testament that the way this got handled is confusing for people - most assume that everything JSX-related is put into those special new entries, but unfortunately, it's not the case because of the createElement quirk.

I don’t think anyone is arguing that this isn’t confusing for the implementors. :-) In particular because it wasn’t clearly specified in the RFC. That’s our fault. But I think talking about whether this is confusing or not for the implementors or not doesn’t move the discussion forward. I’m not sure I understand the goal of continuously bringing this up. It confused me too, I dug out the reasoning and wrote it up in the linked thread. I hope it’s helpful.

Re: confusion — if this is the criticism of the rollout and communication, I fully agree we could do a better job about this case. It is indeed very subtle (and I only understood it yesterday myself). I’m not sure if you’re just communicating frustration about this or if you want to change this to a different solution. Regardless this should probably be discussed on the React repository instead.

VScode shows me Value is not accepted. Valid values: "preserve", "react", "react-native" warning, even with TS workspace version  on 4.1.1-rc

vscode uses this schemastore definition to provide help for tsconfig files. It needs to be updates for the release.

@weswigham  Can we sync next time if this requires work on @types/react? https://github.com/DefinitelyTyped/DefinitelyTyped/pull/48971 was open for a month now and now we learn that "jsx": "react-jsx" requires additional work in @types/react without any guidance how this should look like.

If you are referring to the types for the JSX namespace (because otherwise you only have to provide standard types for jsx, jsxs and jsxDEV factories) then you can look into the tests introduced in those PRs:

https://github.com/microsoft/TypeScript/pull/41330
https://github.com/microsoft/TypeScript/pull/41476

I've also commented in that DefinitelyTyped PR.

Can we sync next time if this requires work on @types/react?

This is the reason I'm getting this error?

error TS7016: Could not find a declaration file for module 'react/jsx-runtime'. 'node_modules/react/jsx-runtime.js' implicitly has an 'any' type.
If the 'react' package actually exposes this module, consider sending a pull request to amend 'https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/react`

This is the reason I'm getting this error?

It seems to me. Changes like https://github.com/DefinitelyTyped/DefinitelyTyped/pull/49701 fix the issue for me so it seems like the new compiler options need new releases of @types/react first.

can we use this with TypeScript3.9?

No, it's a 4.1 feature.

React Native was a weird (admittedly frustrating) case where Metro insisted on not accepting any file type other than .js. Is there a reason Docusaurus can't use .jsx?

React Native was a weird (admittedly frustrating) case where Metro insisted on not accepting any file type other than .js. Is there a reason Docusaurus can't use .jsx?

Docusaurus can use .jsx but we'd prefer not to.
We use tsc to output clean React theme components that can be "swizzled": the React theme components are then copied to the user's source code for shadowing the original implementation so that users can override the default UI we provide.
Using .jsx is not very common these days and might be confusing for our users (not all of them are React/frontend devs) so it's probably better if the copied files have the .js extension, like the rest of the "modern" React industry does today.
We can probably rename the extension at copy time but it would look cleaner if there was an official way to output js instead of jsx.


Error rendering a page due to InvalideStateError of CanvasContext is not reported

It would be difficult to setup a sample project, as I'm doing this on android and call the api from Java code.
The problem I'm seen is related to rendering while parsing other pages, these need to be pages with content and not some empty pages with a word in it.
So for example if I try to render 20 pages, then I iterate on the indices:
renderPageCallBack = funciton (pdfPage){
	logD("Page #" + pageIndex + " - Parsed");
...
...
	pdfPage.render(renderContext).then(function pdfPageRenderSuccess() {
		logD("Page #" + pageIndex + " - Completed");
	}, function pdfPageRenderError(error) {
		logD("Page #" + pageIndex + " - Error: " + error);
	});
}

doc.getPage(index).then(renderPageCallBack)

All the pages are logged as Parsed, most pages are rendered correctly, but only few (which most of the time are the first ones to be rendered) fail with the following log and no callback to 'pdfPageRenderError':
"Uncaught InvalidStateError: An attempt was made to use an object that is not, or is no longer, usable.", source: content://com.nu.art.software.android.pdf.sdk/pdf.js/web/core/pdf.js (5023)

I'm not really sure why this is happening, but if I'll get the error I could consider rendering that page again, otherwise I'm stuck in limbo...
I've also made another attempt, to parse all the pages before calling any rendering, and everything seemed to be just fine!

Which version of PDF.js are you using? Are you using our master branch or one of the stable/beta releases?

master...

Could you add some timeout inbetween the page requests just to see if that is the issue?

If iterate manually... via clicking a button and calling the api everything is working fine.

Also if I depends on the amount of pages I iterate on... for example, on some pdfs it doesn't matter if I iterate on 30 pages and on some even iterating on 3 causes this.

Hm, the fact that the issue is intermittent makes it hard to find the cause. I'm marking this issue as triage-needed since we would need to look into this some more.

What I can suggest to reproduce it is to parse page 1, call render on it and break the execution before rendering starts call parse on two or more other pages, destroy the canvas of page 1 manually (not really sure how to do that) and let the code run...
I believe this would trigger the bug and not report to the error callback.
Thanks for your help.

Is it still an issue?

No response. Closing as incomplete.


How do I run this with analytics turned on?

I am trying to figure out how to turn analytics on. It seems like only cassandra is turned on by default. What am I missing?

The DESCRIPTION.md has a section on how to start it. It's got a link in that section to the documentation for the command line flags available if you don't want to use the default (which is to just start a Cassandra node). So, put it all together and you should be able to start a Spark node by adding the -k switch like this:
docker run --name my-dse -d luketillman/datastax-enterprise:5.0.4 -k

If you need to expose any of the ports to your host, you'll want to be sure to add the -p xxxx:yyyy or -P flags after the -d. You can find a list of the ports used by DSE in the docs. So, for example, to expose the CQL port (9042) as port 9042 on the host, you'd do:
docker run --name my-dse -d -p 9042:9042 luketillman/datastax-enterprise:5.0.4 -k

See the docker run docs for more info.
HTH.

Thanks Luke!


Update env, package.json and the contributors markdown

📋 Description

🔨 Changes Made

Added and detailed a new .env.example file
Updated the package.json file so the main entry points to app.js
Updated the CONTRIBUTING.md file with a new step (step 4)

✅ Checklist
Before submitting the PR, please make sure you have completed the following:

[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have made corresponding changes to the documentation (if applicable).
[x] My changes generate no new warnings.
[x] I have tested it locally and it works fine.
[x] Any dependent changes have been merged and published in downstream modules.

🏷 Types of Changes
What type of changes does your code introduce? (Check all that apply)

[x] Bug fix (non-breaking change which fixes an issue) 🐛
[x] New feature (non-breaking change which adds functionality) ✨
[ ] UI enhancement (non-breaking change which enhances UI) 🎨
[x] Documentation update 📚

🤝 Related Issues

Fixes #

📸 Screenshots (if applicable)

Thank you for contributing to VigneshDevHub! We look forward to reviewing your PR and getting it merged!

This pull request is in reference to and addressing Issue #20.

Hi @stacknomad ,
Thank you for submitting the pull request and providing a detailed description of the changes! I really appreciate your initiative in adding a .env.example file, updating the package.json entry point, and improving the CONTRIBUTING.md documentation.
I’d like to ask if you could break these changes into separate commits to maintain clarity and ensure each update can be reviewed independently. For example:

One commit for the .env.example file.
Another commit for the package.json update.
A final commit for the changes to CONTRIBUTING.md.

This would make the review process smoother and help with tracking specific changes. Once these commits are made, I'll be happy to review the pull request and merge it into the project.
Thanks again for your contributions! Looking forward to collaborating further.

Hey @Vignesh025,
Sorry but you're making pull requests more difficult than it has to be. I tried to do what you said and make a pull request on the test branch, but apparently that branch is out of date and the only copy I have is from the main branch. So when I attempt to make the request, it also adds the different changes from main compared to the out-dated test. But I don't know if you have something in test which you don't in main.¯_(ツ)_/¯
Can you please update the test branch? Thanks!

My changes are still in sync with the main branch upstream, just not test. Once you sync test and main, then I can make my pull request to test.

Hi @stacknomad ,
Apologies for the confusion. The test branch is now in sync with the main branch, so you should be able to proceed with your pull request. Let me know if you encounter any further issues.
Thanks!


Add ping sweeper

Pings every IPv4 address in the local subnet.  Would need to be added after making a GUI.

208f5ee98147792f3ecb27502e6a07d2d87f9221


lxd/main_forkfile: Change counting model

The use of CompareAndSwap from the atomic package is causing a large
number of EAGAIN during the accept phase of connection handling.
This in turn results in a number of "Connection reset by peer".
Instead change the logic to rely on more traditional locks and counters,
combined with a grace period of 5s, this gives us a pretty solid
auto-exit behavior.
Closes #10448
Signed-off-by: Stéphane Graber<EMAIL_ADDRESS>

This PR similarly passed the test of transferring 200k+ files to an instance.

This PR broke the ZFS tests, sorry I didn't spot it at the time.


[YUNIKORN-949] Location of the state dump file should be configurable

What is this PR for?
Shim changes for enabling the state dump file should be configurable instead of hardcoded.
What type of PR is it?

[ ] - Bug Fix
[x] - Improvement
[ ] - Feature
[ ] - Documentation
[ ] - Hot Fix
[ ] - Refactoring

Todos
What is the Jira issue?

https://issues.apache.org/jira/browse/YUNIKORN-949

How should this be tested?

Manually using non-helm deployment.

Screenshots (if appropriate)
Questions:

No longer needed since we will make state dump output path a partition level config property instead of env var.


Bug：Failed assertion: line 894 pos 16: 'index == parameters.length': is not true

════════ Exception caught by Flutter framework ═════════════════════════════════════════════════════
The following assertion was thrown during a service extension callback for "ext.flutter.inspector.setPubRootDirectories":
'package:flutter/src/widgets/widget_inspector.dart': Failed assertion: line 894 pos 16: 'index == parameters.length': is not true.
Either the assertion indicates an error in the framework itself, or we should provide substantially more information in this error message to help you determine and fix the underlying cause.
In either case, please report this assertion by filing a bug on GitHub:
https://github.com/flutter/flutter/issues/new?template=BUG.md
When the exception was thrown, this was the stack:
#2      WidgetInspectorService._registerServiceExtensionVarArgs. (package:flutter/src/widgets/widget_inspector.dart:894:16)
#3      WidgetInspectorService._registerServiceExtensionVarArgs. (package:flutter/src/widgets/widget_inspector.dart:882:17)
#4      BindingBase.registerServiceExtension. (package:flutter/src/foundation/binding.dart:546:32)

(elided 2 frames from class _AssertionError)
════════════════════════════════════════════════════════════════════════════════════════════════════
════════ (2) Exception caught by Flutter framework ═════════════════════════════════════════════════
'package:flutter/src/widgets/widget_inspector.dart': Failed assertion: line 894 pos 16: 'index == parameters.length': is not true.
════════════════════════════════════════════════════════════════════════════════════════════════════
════════ (3) Exception caught by Flutter framework ═════════════════════════════════════════════════
'package:flutter/src/widgets/widget_inspector.dart': Failed assertion: line 894 pos 16: 'index == parameters.length': is not true.
════════════════════════════════════════════════════════════════════════════════════════════════════

This is a duplicate of https://github.com/flutter/flutter/issues/68705 and was recently fixed by https://github.com/flutter/flutter/pull/68721.
The fix is currently on latest master channel.

What is the fix then pls?

The fix is currently on latest master channel.


Adding LVS environment for Gdsfactory generic tech, Adding straight_heater_metal extractor

Adding LVS environment for Gdsfactory generic tech, Adding straight_heater_metal extractor

@atorkmabrains Ready to review, but we need to discuss some LVS derivations.

@atorkmabrains Ready now

@atorkmabrains Ready to review

@atorkmabrains Please check


Mousewheel event should report freshly obtained mouse coordinates

@waxlamp THere is a fix in #1027, if you'd like to try it out or review it.  There are build artifacts here if those are useful for testing.


[feature request] rename variables

Thank you for maintaining this awesome project!
I would love to have the ability to rename variables with the LSP.
If there is no time to implement it I understand that. Just wanted to let you know.

As stated in the README, I don't really have time to maintain this. If you'd like to, you could become the next maintainer of this project. You could also look into https://github.com/nolanderc/glsl_analyzer or https://github.com/KubaP/glsl-lsp.


Problem building the rust library

Hi,
I'm trying to install the package using rust, cargo and Python3.7 on Ubuntu 18, But I get the following error message from cargo:

Caused by:
  unable to get packages from source

Caused by:
  failed to parse manifest at '/home/jens/.cargo/registry/src/github.com-1ecc6299db9ec823/numpy-0.13.2/Cargo.toml'

Caused by:
  feature 'resolver' is required

  consider adding 'cargo-features = ["resolver"]' to the manifest

I tried to use resolver="2" within the package area of the Cargo.Toml, but that didn't solve the issue. Could you have a look at my problem?
Best regards
Jens

Hi Jens,
can you try this version https://github.com/fmfi-compbio/transducer_decoder/pull/3 and let us know whether it works? Note the change in rust nightly version!

As for the original error - you can also try adding cargo-features = ["resolver"] to the /home/jens/.cargo/registry/src/github.com-1ecc6299db9ec823/numpy-0.13.2/Cargo.toml but this is obviously very brittle setup so I would advise against it

Hi,
Trying to install with
Ubuntu 18.04.5
Python 3.7.12
rustc 1.56.1 (59eed8a2a 2021-11-01)
rustup 1.24.3 (ce5817a94 2021-05-31)
setup tries to run
Running rustc --crate-name decoder --edition=2018 src/lib.rs --error-format=json --json=diagnostic-rendered-ansi --crate-type cdylib --emit=dep-info,link -C opt-level=3 -C panic=abort -C lto -C codegen-units=1 --crate-type cdylib -C metadata=d05393d4d30562a0`
and I get
warning: library kind static-nobundlehas been superseded by specifying-bundleon library kindstatic. Try static:-bundle`
error: library kind static-nobundle are currently unstable and only accepted on the nightly compiler
warning: decoder (lib) generated 1 warning
error: could not compile decoder due to previous error; 1 warning emitted
`
I don't deal a lot with rust so this could be a problem on my side.


column_decoder 异常导致be挂了

I0218 19:10:47.043725 26715 column_decoder.cpp:60] Internal error: not found slice: in global dict will force the use of the global dictionary encoding

starrocks version ?
2.0.0-GA ?

you could set cbo_enable_low_cardinality_optimize=false to avoid crash.
this is a known issue https://github.com/StarRocks/starrocks/issues/3082
Fixed By https://github.com/StarRocks/starrocks/pull/3083

This week, we will publish version 2.0.2 .
You can reopen this issue if you still meet this problem after you upgrade to 2.0.2.


Space Carp should break apart walls if they have no human target

They've got a good chance of finding a target if they do!
They should also break walls in pathing attempts.

oh yeah they do that nowadays

fishe


Does not work when ssr: false

I've tried installing Nuxt DevTools multiple times on this project where server-side rendering is disabled on project-level, it installs correctly and when I run npm run dev it show ✔ Nuxt Devtools is enabled v0.3.2[global] (experimental) but when I open the devtools it shows this 404 error

I installed nuxt devtools the same way on a server-side rendered project and it worked correctly.
Development environment

Manjaro Linux 22.1.0
node v18.12.1
npm v8.19.2
nuxt v3.1.2

How to reproduce

clone the project: git clone https://github.com/itsmohmans/PomoDo.git
install packages: npm i
enable nuxt devtools: npx nuxi@latest devtools enable
run the nuxt server: npm run dev

Can you narrow it down to a minimal reproduction? Thank you

so I've created a new<EMAIL_ADDRESS>project and set ssr: false in the configs, and the devtools worked fine so apparently it's not a problem with ssr: false but it's problem with the specific project above.
I can't pinpoint what the issue is right now, but I'll update the comment once I find out

Update:
It worked after I did the following:

removed @vite-pwa/nuxt module from nuxt.config.ts and npm uninstall @vite-pwa/nuxt
npx nuxi@latest devtools enable then npm run dev and it worked

Hi, is there a way to use nuxt devtools together with the @vite-pwa/nuxt module?

I am having a similar issue when i add the @vite-pwa/nuxt module.
the devtool breaks. is there any workaround for this? @antfu


laravel scount brokes when using meilisearch version 0.25.2

Describe the bug
OS : Ubuntu 20.04 LTS
laravel : v8.69.0
laravel-scout : v9.3.1
meilisearch: v0.25.2
For version 0.24.0 every thing works fine but when I upgrade to version 0.25.2 the system fall apart and stops working..
and for every request to meilisearch service it returns
The Authorization header is missing. It must use the bearer authorization method
please help!

What version of meilisearch-php are you using? The error message makes me think an older version, it needs to be v0.22.0 to work with Meilisearch 0.25.2.

Hello @mohsenMJ
@sanders41 is right, your need to use the right meilisearch-php version to use it, so meilisearch-php v0.22.0.
Closing this issue :) feel free to ask to re-open if needed.


⚠ Bofrost.lu has degraded performance

In 1620814, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 2020 ms

Resolved: Bofrost.lu performance has improved in 682384f after 20 minutes.


add to-do.ofice.com

Please remember the Contributing Guidelines :heart:
:star2: What does this PR do?
Adds the to-do.ofice.com url to the Microsoft to-do integration. Currently it only supports the personal version of todo, not the office 365 one. Added as a seperate option as it is possible someone may want to integrate with personal and not business etc.

:bug: Recommendations for testing
All changes should be tested across Chrome and Firefox.

:memo: Links to relevant issues or information

Fixes #1678


Automate php version discovery

This snippet was being used in the MS SQL section already in the helper_functions.sh. I have updated install_moodle and setup_webserver shells scripts to replace the previously hard-coded paths to php.ini.

Fix missing brace in helper_functions.sh.


Update Links

See https://github.com/Senzing/template-repository/issues/40
governor-postgresql-transaction-id/README.md:    1. [git](https://github.com/Senzing/knowledge-base/blob/main/HOWTO/install-git.md)

Pull requests:

https://github.com/Senzing/governor-postgresql-transaction-id/pull/48


cannot set STKEEPER_PG_LISTEN_ADDRESS to *

What happened: I am deploying the stolon helm chart with istio proxy sidecar injection enabled. As per istio documentation here we need to set the listen address to * so that clients can connect to the database. To do that I set the environment variable STKEEPER_PG_LISTEN_ADDRESS  * The keeper however still continues to listen to the $POD_IP.
    Ports:         8080/TCP, 5432/TCP
    Host Ports:    0/TCP, 0/TCP
    Command:
      /bin/bash
      -ec
      # Generate our keeper uid using the pod index
      IFS='-' read -ra ADDR <<< "$(hostname)"
      export STKEEPER_UID="keeper${ADDR[-1]}"
      export POD_IP=$(hostname -i)
      export STKEEPER_PG_LISTEN_ADDRESS=$POD_IP
      export STOLON_DATA=/stolon-data
      chown stolon:stolon $STOLON_DATA
      exec gosu stolon stolon-keeper --data-dir $STOLON_DATA

    State:          Running
      Started:      Wed, 14 Oct 2020 16:26:12 +0530
    Ready:          True
    Restart Count:  0
    Environment:
      POD_NAME:                         empirix-stolon-keeper-0 (v1:metadata.name)
      STKEEPER_CLUSTER_NAME:            empirix-stolon
      STKEEPER_STORE_BACKEND:           kubernetes
      STKEEPER_KUBE_RESOURCE_KIND:      configmap
      STKEEPER_PG_REPL_USERNAME:        <set to the key 'pg_repl_username' in secret 'db-replica'>  Optional: false
      STKEEPER_PG_REPL_PASSWORDFILE:    /etc/secrets/stolon-db-replica/pg_repl_password
      STKEEPER_PG_SU_USERNAME:          <set to the key 'pg_su_username' in secret 'db-admin'>  Optional: false
      STKEEPER_PG_SU_PASSWORDFILE:      /etc/secrets/stolon-db-admin/pg_su_password
      STKEEPER_METRICS_LISTEN_ADDRESS:  <IP_ADDRESS>:8080
      STKEEPER_DEBUG:                   false
      STKEEPER_PG_LISTEN_ADDRESS:       *
    Mounts:
      /etc/secrets/stolon-db-admin from stolon-secret-db-admin (rw)
      /etc/secrets/stolon-db-replica from stolon-secret-db-replica (rw)
      /stolon-data from data (rw)

What you expected to happen: Setting the STKEEPER_PG_LISTEN_ADDRESS to * should be honoured and not be overwritten by the command
Without this working the database cannot work with istio sidecar injection enabled.
I need to set these two variables, but they are not possible
    - name: STKEEPER_PG_LISTEN_ADDRESS
      value: "*"
    - name: STKEEPER_PG_ADVERTISE_ADDRESS
      value: "$POD_IP"

How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:

Stolon version: helm 1.6.2 stolon 0.16.0
Stolon running environment (if useful to understand the bug):
Others:

thanks for the detailed issue.
sounds like a right thing to do.

any chance of having a fix?

Can't provide any ETA, but feel free to create a PR


Clean up doc links

Easy contribution for someone to who's wanting to get involved.
Occasionally we'll bump into links like the one in this section:
https://threlte.xyz/docs/reference/extras/transitions#usage
where there's a reference to localhost 😅
If someone could do a decent comb over the docs and sort those out that'd be super 🎉

On it!

On it! I am going to create a fork and then check and fix the documentation in apps/docs/src/content/reference/extras/ directory. Let me know if there is another directory that needs a similar fix!

Well that was pretty good! thank you @eerkmen


fix: Fixed some problems of google/uuid and pg.uuid code generation

google/uuid and pg.uuid code generation was not working properly
fixed it and added a example to see where old code will fail

https://github.com/walterwanderley/sqlc-connect/pull/5
https://github.com/walterwanderley/sqlc-grpc/pull/13

Thanks!


Texts show on top of cutscenes

What version are you using?
1.0
What were you trying to do?
Play the game with cutscenes.
What were you expecting to happen?
The texts is hidden in cutscenes.
What actually happened?

What are your system specifications?
No response
Anything else you might want to add?
Probably also applies to other non-cutscene events.


BQLivePlot: uses different coordinate system

It has the origin at bottom-left by default. Might need to be flipped for consistency w/ mpl

LOL a recurring theme it seems... +1 for keeping it consistent between plots and using matplotlib default behavior as a reference, as described in https://libertem.github.io/LiberTEM/concepts.html#coordinate-system.

Fixed in https://github.com/LiberTEM/LiberTEM/pull/1011, closing!


BUG: Opening Evaluation.evaluate tab triggers error in UI

I keep getting this error when I select an Evaluation (Evaluation.evaluate) - Happens most times, not every time.

Happens here:
https://wandb.ai/cbs-nlp/llama-7b-chat_center_embed_tn1_ce-lvl1_n5_tn0_i1/weave/calls?filter={"frozen"%3Atrue%2C"opVersionRefs"%3A["weave%3A%2F%2F%2Fcbs-nlp%2Fllama-7b-chat_center_embed_tn1_ce-lvl1_n5_tn0_i1%2Fop%2FEvaluation.evaluate%3A*"]}&peekPath=%2Fcbs-nlp%2Fllama-7b-chat_center_embed_tn1_ce-lvl1_n5_tn0_i1%2Fcalls%2F75ac49c6-64c3-4a79-8ed7-a649c6b22be9
Stacktrace (Chrome)

Hi @nthomsencph, sorry about error and thank you for sending in a bug report and a project with that repro, I will file an internal ticket and someone will hop on that as soon as possible.
https://wandb.atlassian.net/browse/WB-18743

Thank you again for the detailed error report. This error is occurring because of the '/' character being used in object names, which is causing problems in parts of our code that use that as a delimiter. If possible I would recommend avoiding any special characters like that. Letters, numbers, dashes, and underscores should continue to be safe. We do intend to introduce more strict limitations on names.
We've deployed a fix that should prevent the URL you linked from crashing in that way, but I believe you are likely to encounter other problems with objects named like this until we can do a more comprehensive fix.

Confirming that the initial fix from Jamie does allow the page to render, but these names are not handled properly in all cases. @nthomsencph we will be putting in place backend checks to stop such names in the future, so it is advised to change the names now if possible.

Thanks for the clarification and swift action!


Feature request: more consistent file outputs between tools

Currently, I'm working on processing roman + italic variable fonts for Google Fonts.
I need to use four gftools for this: fix-vf-meta, fix-nonhinting, fix-gasp, and fix-dsig.
I tend to need these gftools in each font I prep for Google Fonts.
A big point of friction for using these is that these four scripts have different (and somewhat hard to predict) file output names.
# build stat tables for proper style linking

gftools fix-vf-meta $interUprightVF
gftools fix-vf-meta $interItalicVF

mv ${interUprightVF/".ttf"/".ttf.fix"} $interUprightVF
mv ${interItalicVF/".ttf"/".ttf.fix"} $interItalicVF

# prevent warnings/issues caused by no hinting tables – this fixes the file in-place

gftools fix-nonhinting $interUprightVF $interUprightVF
gftools fix-nonhinting $interItalicVF $interUprightVF

rm ${interUprightVF/".ttf"/"-backup-fonttools-prep-gasp.ttf"}
rm ${interItalicVF/".ttf"/"-backup-fonttools-prep-gasp.ttf"}

# assert google fonts spec for how fonts should rasterize in different contexts

gftools fix-gasp --autofix $interUprightVF
gftools fix-gasp --autofix $interItalicVF

mv ${interUprightVF/".ttf"/".ttf.fix"} $interUprightVF
mv ${interItalicVF/".ttf"/".ttf.fix"} $interItalicVF

# prevent warnings/issues caused by no digital signature tables

gftools fix-dsig --autofix $interUprightVF
gftools fix-dsig --autofix $interItalicVF

Request
Each gftool could have an argument like --inplace / -i to edit a file and output it with the original name. This would make pipelines much simpler to set up. Alternatively, every script could allow the tool <input-font> <output-font> setup.
Additionally, all edited files could get the same suffix. E.g. every output could be suffixed with .fix, to make names such as inter-regular.ttf.fix. This would also simplify shell pipelines.

YES PLEASE! I came around just to request this. Trying to use gftools in fontship is a real headache because of this. Every subcommand has a different expectation about input/output file names!

All tools should be consistent somehow.
No tools should only operate in-place. That should be optional for tools that only work on a single file perhaps, but inplace edits are problematic to use in other automated tooling because one cannot verify whether the tools has been run or not.
Automatically added suffixes to batch jobs should be configurable. Some people may always want .fix, but some workflows will be much easier to support if each tool had a configurable output file name or name format (or at least a configurable output suffix).


doesn't show the dependency graph

Example:
https://leanprover-community.github.io/mathlib-port-status/file/measure_theory/function/jacobian

edges & nodes in HTML are both empty.
const edges = [];
const nodes = {};

It's fixed. Thank you!


Improve debug-level Logging

In the past few weeks, we've had several issues with misconfigured nodes that have been difficult to debug. We should add additional logging to help with debugging.
Connection-Level Misconfiguration
The connection-level misconfiguration manifests as follows:

A user is configuring a private network using static nodes

The static nodes contain the correct endpoint, but the public keys are wrong

This can be due to file system issues where a node can’t access the correct key and so generates a new key. This means that any enode urls referencing this node will have the wrong public key.

When a connection is attempted to an enode with an inaccurate public key, the crypto handshake will fail.

We can catch this case in the [ECIESHandshaker here|https://github.com/PegaSysEng/pantheon/blob/a4bb4af0dfc8ca9e7b97720aa8ef47e330d7f903/ethereum/p2p/src/main/java/tech/pegasys/pantheon/ethereum/p2p/rlpx/handshake/ecies/ECIESHandshaker.java#L208]. If this error is thrown when a the handshaker is the initiator (initiator = true), we should log a debug error like: LOG.debug(“Outbound handshake to {} failed. Static nodes configured with the wrong public key are a possible cause of this error.”, theirPubKey.getEncodedBytes())
Discovery-Level Misconfiguration
The discovery-level misconfiguration manifests as follows:

The bootnode enode urls are inaccurate: they contain the correct endpoint information but the wrong public key.

As a result, our misconfigured node will send a discovery PING to its bootnode

The bootnode will respond with a PONG, but because the PONG comes from a peer with a non-matching node id, we’ll ignore it.

Suggested fix:

If a [PONG is received|https://github.com/PegaSysEng/pantheon/blob/80f293ae7cdf43b06317957c2d37221df7d0d57f/ethereum/p2p/src/main/java/tech/pegasys/pantheon/ethereum/p2p/discovery/internal/PeerDiscoveryController.java#L315] with no corresponding match, log a debug message (possibly including the list of inflight PING messages or the list of unbonded bootnodes).

Hi, i would like to work on this issue

closing. out of date


There was a problem in the negotiation with the server.

I have an ASP Core API with SignalR. For my web client using javaScript everything work fine but when I use in flutter status always respond disconnect with error message "There was a problem in the negotiation with the server".

i have ASP API  with signalR still getting error message  "There was a problem in the negotiation with the server"

I also have this, what can I do about it?

This plugin is for ASP.Net SignalR. ASP.Net Core SignalR won't work with this plugin.


Fix passing Colormap objects

When passing a Colormap instance via cmap, an error is raised although it is supported according to documentation.
  File "…/site-packages/spatialdata_plot/pl/basic.py", line 370, in render_images
    cmap_params = _prepare_cmap_norm(
  File "…/site-packages/spatialdata_plot/pl/utils.py", line 339, in _prepare_cmap_norm
    cmap = copy(matplotlib.colormaps[rcParams["image.cmap"] if cmap is None else cmap])
  File "…/site-packages/matplotlib/cm.py", line 80, in __getitem__
    return self._cmaps[item].copy()
TypeError: unhashable type: 'ListedColormap'

This change looks up a colormap by name only if a string is passed.

Hey @aeisenbarth, (again :D) many thanks for your suggestion and the code contribution! @Sonja-Stockhaus has moved your changes over to https://github.com/scverse/spatialdata-plot/pull/194 so that we could add tests and slight modifications. So we'll close this one here now.


Gem not working with Rails 5

When upgrading to Rails 5, bundler works for all my other gems - but when I add rails-observers, this is the error I get:
bundle update
Fetching gem metadata from https://rubygems.org/.........
Fetching version metadata from https://rubygems.org/...
Fetching dependency metadata from https://rubygems.org/..
Resolving dependencies........................................................................................................................................................................................................................................................................................................................................................................................................................
Bundler could not find compatible versions for gem "rack":
  In Gemfile:
    rails (= 5.0.0.beta3) ruby depends on
      actioncable (= 5.0.0.beta3) ruby depends on
        actionpack (= 5.0.0.beta3) ruby depends on
          rack (~> 2.x) ruby

    rails (= 5.0.0.beta3) ruby depends on
      actioncable (= 5.0.0.beta3) ruby depends on
        actionpack (= 5.0.0.beta3) ruby depends on
          rack-test (~> 0.6.3) ruby depends on
            rack (>= 1.0) ruby

    sass-rails (>= 0) ruby depends on
      sprockets (< 4.0, >= 2.8) ruby depends on
        rack (< 3, > 1) ruby

    capybara (>= 0) ruby depends on
      rack (>= 1.0.0) ruby

    passenger (>= 0) ruby depends on
      rack (>= 0) ruby

    thin (>= 0) ruby depends on
      rack (~> 1.0) ruby
Bundler could not find compatible versions for gem "activemodel":
  In Gemfile:
    rails (= 5.0.0.beta3) ruby depends on
      activemodel (= 5.0.0.beta3) ruby

    rails (= 5.0.0.beta3) ruby depends on
      activemodel (= 5.0.0.beta3) ruby

    web-console (>= 0) ruby depends on
      activemodel (>= 4.2) ruby

    simple_form (>= 0) ruby depends on
      activemodel (< 5.1, > 4) ruby

    carrierwave (>= 0) ruby depends on
      activemodel (>= 3.2.0) ruby

    rails-observers (>= 0) ruby depends on
      activemodel (~> 4.0) ruby
Bundler could not find compatible versions for gem "railties":
  In Gemfile:
    rails (= 5.0.0.beta3) ruby depends on
      railties (= 5.0.0.beta3) ruby

    lograge (~> 0.3.1) ruby depends on
      railties (>= 3) ruby

    coffee-rails (>= 0) ruby depends on
      railties (< 5.1.x, >= 4.0.0) ruby

    sass-rails (>= 0) ruby depends on
      railties (< 5.0, >= 4.0.0) ruby

    jquery-turbolinks (>= 0) ruby depends on
      railties (>= 3.1.0) ruby

    factory_girl_rails (>= 0) ruby depends on
      railties (>= 3.0.0) ruby

    web-console (>= 0) ruby depends on
      railties (>= 4.2) ruby

    jquery-rails (>= 0) ruby depends on
      railties (>= 4.2.0) ruby

    rails-observers (>= 0) ruby depends on
      railties (~> 4.0.0.beta) ruby

Sorry, I should have checked the closed issues. Looks like this has been dealt with, just not released to rubygems. I'll point my gemfile to this repository.
Thanks to the contributors.

Confirming that I was able to get this to work with Rails 5 by updating my Gemfile to:
gem 'rails-observers', git: 'https://github.com/rails/rails-observers.git'
Which allowed bundle update to succeed:
Using rails-observers 0.1.3.alpha from https://github.com/rails/rails-observers.git (at master)

@rafaelfranca Any update on when this will be released to RubyGems? Thanks!