python311Packages.jupyter-server: 2.10.1 -> 2.12.1

Description of changes
Changelog: https://github.com/jupyter-server/jupyter_server/blob/v2.12.1/CHANGELOG.md
fix: GHSA-h56g-gq9v-vc8r
775de9fe27c258188b38e747061890ec88c15e05 is cherry-picked from the python-updates branch to avoid conflicts.

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[x] sandbox = true

[x] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review pr 274148 at b0fdc32d run on aarch64-darwin 1

16 packages marked as broken and skipped:

python310Packages.batchspawner
python310Packages.dockerspawner
python310Packages.jupyter-contrib-nbextensions
python310Packages.jupyterhub
python310Packages.jupyterhub-ldapauthenticator
python310Packages.jupyterhub-systemdspawner
python310Packages.jupyterhub-tmpauthenticator
python310Packages.oauthenticator
python311Packages.batchspawner
python311Packages.dockerspawner
python311Packages.jupyter-contrib-nbextensions
python311Packages.jupyterhub
python311Packages.jupyterhub-ldapauthenticator
python311Packages.jupyterhub-systemdspawner
python311Packages.jupyterhub-tmpauthenticator
python311Packages.oauthenticator

16 packages failed to build:

python310Packages.einops
python310Packages.k-diffusion
python310Packages.layoutparser
python310Packages.mkdocs-jupyter
python310Packages.pdfplumber
python310Packages.rotary-embedding-torch
python310Packages.tsfresh
python310Packages.xarray-einstats
python311Packages.einops
python311Packages.k-diffusion
python311Packages.layoutparser
python311Packages.mkdocs-jupyter
python311Packages.pdfplumber
python311Packages.rotary-embedding-torch
python311Packages.tsfresh
python311Packages.xarray-einstats

71 packages built successfully:

ihaskell
jupyter
jupyter-all
nbqa
python310Packages.ansible-kernel
python310Packages.bqplot
python310Packages.bqscales
python310Packages.experiment-utilities
python310Packages.ipytablewidgets
python310Packages.jupyter
python310Packages.jupyter-collaboration
python310Packages.jupyter-contrib-core
python310Packages.jupyter-lsp
python310Packages.jupyter-nbextensions-configurator
python310Packages.jupyter-server
python310Packages.jupyter-server-fileid
python310Packages.jupyter-server-mathjax
python310Packages.jupyterlab
python310Packages.jupyterlab-git
python310Packages.jupyterlab-lsp
python310Packages.jupyterlab-server
python310Packages.jupytext
python310Packages.nbclassic
python310Packages.nbdev
python310Packages.nbdime
python310Packages.nikola
python310Packages.nix-kernel
python310Packages.notebook
python310Packages.notebook-shim
python310Packages.notedown
python310Packages.phik
python310Packages.pydeck
python310Packages.pymoo
python310Packages.qgrid
python310Packages.streamlit
python310Packages.vector
python310Packages.vega
python311Packages.ansible-kernel
python311Packages.bqplot
python311Packages.bqscales
python311Packages.experiment-utilities
python311Packages.ipytablewidgets
python311Packages.jupyter
python311Packages.jupyter-collaboration
python311Packages.jupyter-contrib-core
python311Packages.jupyter-lsp
python311Packages.jupyter-nbextensions-configurator
python311Packages.jupyter-server
python311Packages.jupyter-server-fileid
python311Packages.jupyter-server-mathjax
python311Packages.jupyterlab
python311Packages.jupyterlab-git
python311Packages.jupyterlab-lsp
python311Packages.jupyterlab-server
python311Packages.jupytext
python311Packages.nbclassic
python311Packages.nbdev
python311Packages.nbdime
python311Packages.nikola
python311Packages.nix-kernel
python311Packages.notebook
python311Packages.notebook-shim
python311Packages.notedown
python311Packages.phik
python311Packages.pydeck
python311Packages.pymoo
python311Packages.qgrid
streamlit (python311Packages.streamlit)
python311Packages.vector
python311Packages.vega
quarto


add automatic language detection

no js library ready for this, consider to switch from prism.js to highlight.js

i think there is a way to do this

workaround for now...only needed for cli


hatch: clean, format and fix build

Description of changes
cc @onny
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review pr 335539 run on aarch64-darwin 1

2 packages failed to build:

hatch
hatch.dist

Result of nixpkgs-review pr 335539 run on x86_64-darwin 1

2 packages failed to build:

hatch
hatch.dist

Result of nixpkgs-review pr 335539 run on aarch64-linux 1

2 packages built:

hatch
hatch.dist

Result of nixpkgs-review pr 335539 run on x86_64-linux 1

2 packages built:

hatch
hatch.dist

Some might complain and require that you split your commit into multiple commits, but for me this is totally OK as it is now.
Sure, I tried to do such at the beginning, but then it all got mixed up. I didn't want to go over it again...

I will now try to fix the darwin build, so let's hold on a bit.

Sure, I tried to do such at the beginning, but then it all got mixed up. I didn't want to go over it again...

git commit -p and lazygit must become your best friends :D

git commit -p and lazygit must become your best friends :D

I do use those, but when formatting is applied, it gets very tricky...

I have skipped the necessary tests to make it build fine on darwin.


Miscellaneous housekeeping

👋 Hello! This is a ~(currently draft)~ PR to layer in some slight process improvements and to address some deferred maintenance in advance of potentially migrating terraform-provider-vinyldns to utilize the new plugin framework.

👋 Hi @remerle - are you comfortable approving the workflow run on this PR? There are some additional changes I'd like to layer in -- either in this PR or a follow-on PR -- and CI verification would be very helpful :)
Thanks!


Uncaught ReferenceError: module is not defined

This error occurs here, and I don't know why as it works as expected. There should be more defensive code.
https://github.com/janat08/blockrazor/tree/createButton

Turns out I was me using cdn and importing downloaded file.


WIP: Feature/span classification

This feature branch introduces classification of arbitrary Spans, defined in the span groups in spacy Doc.
They can be generated by e.g. a SpanRuler or any other component that generates Spans.
Either using include_span to include ALL spans for classification, or provide a list by using înclude_span_groups property in configuration.

Hi, looking great already. Could you add a working code snippet and potentially also set the span classification to Doc.ents level?

Great idea! Sure, I can add that as well.

I added a working example, Wdyt? Would add similar for entites and unit test cases, then this PR is ready for merge.

Hi @RobinRojowiec , sorry the end of year has been rather busy. I will take a look during the coming weekend.


Index: Implement search in facets

@clement-leprovost: LGTY?

@clement-leprovost: LGTY?

👍 LGTM.
What a wonderful method name. 😇


Duplicate messages

Steps to reproduce:

Login
Create a group channel with any user
Switching between apps back and forth to triggered onResume() few times
Send a message
The recycler view will display the message twice

Video:
https://www.youtube.com/watch?v=d0v1Ut02050

Yeah, onMessageReceived is being triggered on my own messages, which shouldn't happen.

@terrykwon When you guys are planning to ship new release. Any timeline would be great.

@sf-jay-yun

@aftabsikander Sorry for the belated response. We are digging the issue and expect the new release by next week.

Thank you for the big patience. You can find that the latest version has resolved the issue.


Updating yarn.lock to not use a local repository

I noticed there was already a PR to do this https://github.com/rancher/ui-plugin-examples/pull/15


Difference between navigation_lincoln.pb.txt and lincoln.pb.txt

Hi,
I see two similar looking config file in /module/control/conf. They look like a loop up table.
What are the purposes/differences of navigation_lincoln.pb.txt  and lincoln.pb.txt ?

@wckorealsh They are serving for different purposes : navigation_lincoln is more for highway and Lincoln is for L4 level urban road.

@wckorealsh : First one assumes relative position and second one assumes absolute position

Thank you. Sounds like two different sets of a look-up table.
But, can you please explain what did you mean by relative and absolute position? The position of what? relative to what?
Thank you!

@wckorealsh Navigation mode is for 2.5 which we only assume we have relative position information of vehicle information (with respect to lane markers) in control while in the other one we still use the absolute position (from GPS/IMU) in control

Closing this issue as it appears to be resolved.


JwtSignatureES384.java:104: Add language support for...

The puzzle 1-e107e8f1 from #1 has to be resolved:
https://github.com/shiruka/shiruka/blob/e9651b3f945ec12474aae4254d65683af8156caa/src/main/java/net/shiruka/shiruka/jwt/JwtSignatureES384.java#L104-L104
The puzzle was created by @portlek on 05-Apr-21.
Estimate: 5 minutes,  role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

The puzzle 1-e107e8f1 has disappeared from the source code, that's why I closed this issue.


preprocessor MACRO support

If your program needs something from a specific version, there is no way to tell the user that their version is inadequate within the program.
There is also no way to allow it to still compile with an older version.
Here's what C uses:
Conditional compilation
The directives #if, #ifdef, #ifndef, #else, #elif and #endifcan be used for conditional compilation.
#if VERSION >= 2
  // code block for this version
#else
  // code block for older versions
#endif

An example is net.conn.NetConn() not existing until version 1.18 of Go.

Would a build tag not be sufficient?

Duplicate of #35107

@neetle nope, it looks like they are just going to let them sit and die while people walk on in confusion about it.


Noetic: orientation quaternion of /initialpose is all zero

Orientation field of /initialpose and /move_base_simple/goal are all zero for any given poses.
I'll dig into the code probably next week.
For example,
$ rostopic echo /initialpose
header:
  seq: 0
  stamp:
    secs:<PHONE_NUMBER>
    nsecs: 321122626
  frame_id: "map"
pose:
  pose:
    position:
      x: 0.8154544830322266
      y: 0.20693016052246094
      z: 0.0
    orientation:
      x: 0.0
      y: 0.0
      z: 0.0
      w: 0.0
  covariance: [0.25, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.25, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.06853892326654787]
---
$ rostopic echo /move_base_simple/goal
header:
  seq: 0
  stamp:
    secs:<PHONE_NUMBER>
    nsecs: 422684186
  frame_id: "map"
pose:
  position:
    x: 0.7333250045776367
    y: 0.9347925186157227
    z: 0.0
  orientation:
    x: 0.0
    y: 0.0
    z: 0.0
    w: 0.0
---

Your environment

OS Version: Ubuntu 20.04 (docker)
ROS Distro: Noetic
RViz, Qt, OGRE, OpenGl version as printed by rviz:rviz version 1.14.0
compiled against Qt version 5.12.8
compiled against OGRE version 1.9.0 (Ghadamon)
Forcing OpenGl version 0.
Stereo is NOT SUPPORTED
OpenGl version: 4.6 (GLSL 4.6).

This should be fixed via #1510. But, it's not yet released.

Oh, sorry for duplication.
Happy to hear it has been already fixed.


pixel coordinates beyond width are wrapping around?

playing with the linepen example I noticed some wraparound pixels (?) when going beyond the window's width.

some ideas:

mouse coordinates?
incorrect width calculation (off by 1)?
incorrect pixel coordinates calculation?
sdl stretching?

pfft... this turned out to be an off by one error/bounds checking issue...

fb has width and height attributes
the addressable x values go from 0 to width - 1
the addressable y values go from 0 to height - 1

Since the fb memory is a 1D bytearray I have to convert x, y coordinates to an index in that 1D bytearray. This is done by moving y number of rows through the bytearray and then moving x columns on the last row, which is described by the formula index = (y * width) + x.
There's some bounds checking in the put_pixel method that results in a NOOP if we go beyond the framebuffer bounds, but it had a incorrect bound check that allowed setting a pixel when addressing 1 position beyond the max addressable index in both x and y. This isn't an issue in y because using that formula above we go off the bounds of the 1D bytearray that backs the framebuffer, but with x it results in an off by one error setting the 0th column of the next row (also leaving the 0th row unset).
I confirmed this with a simple sketch that drew a line from width, 0 to  width, height and it drew a line along the 0th column of the framebuffer. Technically, that line as requested would be out of bounds and shouldn't be drawn. Fixing the bounds checking code resolved this.
Commit incoming.


⚠ RPC server - xDai has degraded performance

In 43e9ebe, RPC server - xDai ($XDAI_RPC_URL) experienced degraded performance:

HTTP code: 200
Response time: 453 ms

Resolved: RPC server - xDai performance has improved in c279e91 after 12 minutes.


Update etcd version

We're currently importing github.com/coreos/etcd v3.2.1. The latest release is 3.3.3, so we're at least one dot release behind. Let's use this issue to track discussion and PR(s) required to do this.

@nishanttotla did you try create PR of this and to see if tests still works with that version?

@olljanat I am no longer maintaining SwarmKit, and didn't get a chance to test this out. Please check with current maintainers. Thanks!

OK. Was just curious as this one have P1 label.
Anyway looks that TestNodeAllocator have been failing so it is probably good idea to wait that #2615 will be merged as it replaces it before try etcd upgrade again.


Update README.md

updated ur readme to accurately reflect ur website
lol

Great Idea!  I may suggest referring to our code of conduct and then adding additional changes to reflect these values.

did u merge it yet


ionic_copy override doesn't override it 'adds'

When defining a copy override config:
"ionic_copy": "./config/copy.config.js",

the process executes both the default npm app-scripts located
<EMAIL_ADDRESS>as well as the newly assigned
./config/copy.config.js
A bug or feature?
How can this be turned off?
Thanks
O.
EDIT:
Got it. It requires the same names to be used and will replace their individual definition, it doesn't replace the entire config file & logic per se.

@olivermuc,
This is by design. If you want to remove a key, say copyPolyfills, you can provide a blank object for it. IE
...
copyPolyfills: {},
...

Hopefully this helps you.
Thanks,
Dan

blank object doesn't work,
module.exports = {   copyFonts: {} }
fonts folder copied as usual

@wjljack  just tried it with the current version and it works. Providing an empty copyFonts keyvalue pair does not copy the default fonts inside www dir.


Issue #26 German translation

I've completed the German translation.

Looks good! I don't speak German so I'll have to take your word for it that the translations are correct.
Thanks a lot for this.
If you have the app you should expect to see an update in the next day or so with the translation in it.
FYI: One of the notes for contributors was to include the issue number formatted with a hash (#26) in the commit comment. This would have automatically referenced the translation ticket which makes following up easier. Doesn't really bother me but I've seen pull requests declined for trivial things like this so watch out when contributing to other projects.
Thanks again!

@ScreamingHawk I tried to include "#26", but command line git ignores everything after the shell comment symbol "#" when processing commit messages.

You can put the commit comment in quotes to get around this. git commit -m "#26 German translation".  :)


Update README.md with more information

Goals

What is prestissimo
Contributing
License

refs https://github.com/alexjpaz/prestissimo/pull/17


Too many restarts in K8s cluster deployment

We've been experiencing an unusually high number of restarts in our K8s cluster. For example in the last 3 days K8s restarted QL 103 and 99 times in each of the two pods, respectively.

I think it happens when QL becomes unresponsive, and so it's killed by k8s:
  Warning  Unhealthy  54m (x1061 over 4d21h)    kubelet, ip-172-20-60-68.eu-central-1.compute.internal  Liveness probe failed: Get http://<IP_ADDRESS>:8668/v2/health: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
  Normal   Pulling    54m (x101 over 4d21h)     kubelet, ip-172-20-60-68.eu-central-1.compute.internal  pulling image "smartsdk/quantumleap:rc"
  Normal   Killing    54m (x100 over 4d21h)     kubelet, ip-172-20-60-68.eu-central-1.compute.internal  Killing container with id docker://quantumleap:Container failed liveness probe.. Container will be killed and recreated.
  Normal   Pulled     53m (x101 over 4d21h)     kubelet, ip-172-20-60-68.eu-central-1.compute.internal  Successfully pulled image "smartsdk/quantumleap:rc"
  Normal   Created    53m (x101 over 4d21h)     kubelet, ip-172-20-60-68.eu-central-1.compute.internal  Created container
  Normal   Started    53m (x101 over 4d21h)     kubelet, ip-172-20-60-68.eu-central-1.compute.internal  Started container
  Warning  Unhealthy  53m (x3 over 4d21h)       kubelet, ip-172-20-60-68.eu-central-1.compute.internal  Liveness probe failed: Get http://<IP_ADDRESS>:8668/v2/health: dial tcp <IP_ADDRESS>:8668: connect: connection refused
  Warning  Unhealthy  8m50s (x1127 over 4d21h)  kubelet, ip-172-20-60-68.eu-central-1.compute.internal  Readiness probe failed: Get http://<IP_ADDRESS>:8668/v2/health: net/http: request canceled (Client.Timeout exceeded while awaiting headers)

i believe this was solved with allowing for yellow state of crate cluster.

@c0c0n3 We are facing this issue in our Kubernetes deployment of quantumleap with wq configuration. We have used below liveness probe setting in both deployment files for quantumleap and quantumleap-wq:
        livenessProbe:
          failureThreshold: 3
          initialDelaySeconds: 180
          periodSeconds: 60
          successThreshold: 1
          httpGet:
            path: /health
            port: 8668
            scheme: HTTP
          timeoutSeconds: 60

Please find below observation:

Quantumleap pod does not restart
Quantumleap-wq pod restarts many times
Liveness probe failed for quantumleap-wq pod
Health API returns status:pass

Liveness probe failed for quantumleap-wq:

We have checked our environment for crate health, and it is GREEN.
If we remove livenessProbe from quantumleap-wq deployment file, then it does not restart.
Please confirm our understanding: livenessProbe is not required in quantumleap-wq deployment file.

@c0c0n3 we have following observation on why livenessProbe is not working with quantumleap-wq deployment file:
As two deployments of quantumleap is running in our environment, one is for master and other is for worker.
In master deployment file we can have livenessProbe which will call quantumleap's health API and restart pod if any error occurs.
Whereas worker quantumleap can only handle notify API as mentioned in https://github.com/orchestracities/ngsi-timeseries-api/blob/master/docs/manuals/admin/wq.md.
As per our understanding, health API of quantumleap cannot be executed on worker quantumleap and it returned connection error and restarts.
We can remove livenessProbe from worker quantumleap because it is already handled in master quantumleap which will check crate status.
Please correct my understanding if there is anything I am missing.

hi @pooja1pathak :-)

health API of quantumleap cannot be executed on worker quantumleap and it returned connection error and restarts.

Correct. Each Worker process is a standalone RQ instance, there's no QL Web API there:

https://github.com/orchestracities/ngsi-timeseries-api/blob/master/src/wq/core/cli.py
https://github.com/orchestracities/ngsi-timeseries-api/blob/master/src/wq/core/rts.py

We can remove livenessProbe from worker quantumleap

Yes. I suggest you start Workers using Supervisor with our config:

https://github.com/orchestracities/ngsi-timeseries-api/blob/master/src/wq/supervisord.conf

That will give you the reliability you're after I guess.
More about it here:

https://github.com/orchestracities/ngsi-timeseries-api/wiki/Work-a-Q

Hope this helps!


WIP

working on fixing the release atomicity and ensuring it targets the right commit
atomicity:
the create command just takes the artifacts to upload. weirdly the edit command doesn't but that's ok because we only use edit for draft-release-workflows where spewing some random artifacts onto a draft that can be deleted is ~fine (the undraft happens last)
targetting commit (relevant for workflow-dispatch flow):

If a matching git tag does not yet exist, one will automatically get created
from the latest state of the default branch. Use --target to override this.
To fetch the new tag locally after the release, do git fetch --tags origin.

we also already pass --target for the submodule flow, so we just need to change that to being unconditional, and write some logic to get the current repo commit instead of the submodule

For setting the commit in a same-repo context, we can probably use GITHUB_SHA. It's the specific commit that created the actions run, resolved at the time the action began. The ref is also provided, but since that can get theoretically targeted midflight, GITHUB_SHA is more specifically what we want.


Set StageError cause in ChiselStage

Change ChiselStage to set the cause of a StageError due to a ChiselException to be the ChiselException. This should fix issues where libraries that want to inspect the stack trace can do so. Previously, this would do stack trace trimming and drop a no-cause StageError.

Related issue: https://github.com/freechipsproject/chisel3/issues/1114#issuecomment-601971550

Type of change: bug report

Impact: no functional change

Development Phase: implementation

Looks good to me as well. One thing I was wondering, instead of printlning the trimmed stack trace ourselves, what would happen if we override some of the methods in Throwable? https://docs.oracle.com/javase/7/docs/api/java/lang/Throwable.html
Perhaps then we can use normal printStackTrace() for both and it will make it easier for custom Stages to compose with this

Unfortunately, this by itself, isn't sufficient. Driver.execute catches StageError exceptions and returns an error:
    val annosx = try {
      phases.foldLeft(annos)( (a, p) => p.transform(a) )
    } catch {
      /* ChiselStage and FirrtlStage can throw StageError. Since Driver is not a StageMain, it cannot catch these. While
       * Driver is deprecated and removed in 3.2.1+, the Driver catches all errors.
       */
      case e: StageError => annos
    }

    view[ChiselExecutionResult](annosx)

which eventually gets converted into another zero information exception in chisel3.iotesters.setupTreadleBackend:
    chisel3.Driver.execute(optionsManager, dutGen) match {
      case ChiselExecutionSuccess(Some(circuit), _, Some(firrtlExecutionResult)) =>
        ...
      case _ =>
        throw new Exception("Problem with compilation")
    }

@ucbjrl I think we should reconsider how we compose things and update those places to not catch Errors. As described in the Java documentation: "An Error is a subclass of Throwable that indicates serious problems that a reasonable application should not try to catch."

Perhaps it's time to revisit #361?

Good catch, @ucbjrl.
I expect the Driver shouldn't be catching anything. In 3.1.5 it didn't... This fails some DriverSpec tests, though (checking what's going on).
Hot take: the sooner we can remove Driver, the sooner we can move to a unified exception model...

Actually, @ucbjrl: I think what's happening is the correct behavior of stack trace trimming:

Elaboration fails and ChiselStage will print a verbose trimmed stack trace on stdout
A StageError gets thrown
The Driver converts this to a ChiselExecutionFailure
iotesters converts this to an information-less exception

Even though (4) happens, the information is still provided to the user. This is, as far as I can tell, how #931 was intended to work.
The contract of StageError is that the thrower is providing all information to the user to debug the problem (here, a trimmed stack trace on stdout). Hence, StageError may legally provide zero information on what is going on because the thrower has already provided that information. This is likely an anti-pattern.
@jackkoenig has suggested that stack trace trimming should instead directly manipulate the stack trace. This may be a better approach. Perhaps we should implement something like this instead?

Right, the problem is the failure isn't available programmatically (without some contortions). Chisel is a library and may not always be the top application. One could argue that we shouldn't be printing errors without some negotiation with/advice from  the enclosing application.

Printing generally isn't great, imagine if there's bug in MIDAS Chisel code that isn't supposed to be exposed to the user, they can catch and report a better user error, but Chisel is still going to print the stack trace as if the Chisel code itself is user code.
I think there's general agreement about finding a more composable solution, the real question is if we should do this for 3.3 or perhaps do this for 3.4.

Hot take :two:: We're late enough on 3.3, let's just fix it. (I volunteer...)


Forensic Study 1 submission

Web archiving forensics presentation by David Calano retracing the siege of HK PolyU

Please add a README.md to this directory (and your prior submission as well).


[BUG] Subtitle doesn't show after 2 or 3 minute [hentaistream.moe]

Describe the bug
Subtitle doesn't show after the 2nd or 3rd minute of the video?
To Reproduce
Steps to reproduce the behavior:

get-sauce -s 0 -c 0 https://hentaistream.moe/970/akane-wa-tsumare-somerareru-1/
video and subtitle are merged successfully but
when I try to play with mpv ( vlc, mx or mpc-hc)
subtitle never appears again after 2 or 3 minute
tried to extract subtitle with program and saw subtitle is only downloaded until the 2 or 3 minute

Expected behavior
The Whole Subtitle file will be downloaded for the video
Desktop (please complete the following information):

OS: Android 11 Termux, Xiaomi Redmi Note 8 Pro

Additional context
I think this is a ffmpeg problem because in hentaistream.moe's .vtt subtitle
I saw that they put spaces between some lines and ffmpeg skips the whole lines when such space appears.
Example:
00:02:30.000-xx:xx:xx.000
text text

00:02:57.000-xx:xx:xx.000
text text

text text

00:03:40.000-xx:xx:xx.000
text text

00:03:45.000-xx:xx:xx.000
text text

So in 00:02:57.000 there is a space between the lines and because of this.
ffmpeg does skip 00:02:57.000 line and whatever line comes after so the subtitle file will be only downloaded until 00:02:30.000 minute.
Edit:
merging the video and .vtt subtitle with mkvmerge without converting the subtitle with ffmpeg solves THİS problem! The problem does not occur with mkvmerge.
Could you also add mkvmerge as dependencies? and change the command for merging(for hentaistream.moe ONLY ofcourse) to use mkvmerge instead of ffmpeg?

there is sanitizing logic for exactly this issue maybe it's different from the cases I had before I'll take a look at it 👍

Looks like it's breaking at here:
02:33.210 --> 02:40.630
The Madder
is Plucked
and Dyed

Akane wa Tsumare Somerareru

02:33.210 --> 02:40.630
The Madder
is Plucked
and Dyed

Akane wa Tsumare Somerareru

02:33.210 --> 02:40.630
The Madder
is Plucked
and Dyed

Akane wa Tsumare Somerareru

The sanitizing logic currently only removes additional blank lines. I'll make sure to fix it later today. Thanks for reporting the issue!

The sanitizing logic currently only removes additional blank lines. I'll make sure to fix it later today. Thanks for reporting the issue!

No problem.👍
And Thank you for your answer.

Please try again and if you still have issues don't hesitate another issue! Thanks again for your input :+1:

Please try again and if you still have issues don't hesitate another issue! Thanks again for your input 👍

İt is working fine now thanks again 🙂


Draft impl of passing a ModContainer to the builtin entrypoints

Draft for 2 reasons:

There's not been any discussion on #26 yet. (Although I like the proposal, hence this impl draft)
I haven't tested this on real mods with both kinds of entrypoints.

Since quilt uses a different namespace we can just add new interfaces under org.quiltmc.loader.api. (I didn't put these under org.quilt.api since I'm not sure what the eventual package structure will be for loader plugins and QSL - and it's probably better to move these out from loader rather than pollute a package that might be used in the future).
Discussion about the original request (I.E. adding a ModContainer parameter to entrypoints) should go in #26, but issues with this implementation of it should go here.
This closes #26.

I think the main issue with this is that it currently points to fabric's ModContainer rather than quilt's - although this requires us to clean up quilt's systems (since currently we still use a lot of fabric's interfaces and don't have equivalents for quilt, and I'm not quite sure how that will end).
However that hasn't been started yet, so this can probably be


Cantor refactor (Part 3)

Read and write data using Java's buffer classes rather than 1 element at a time

Thank you for the comment - much clearer! This looks good to me now.

👍


Give struct fields mutable semantic token modifier

Could rust-analyzer emit the mutable semantic token modifier for struct fields when their type is a mutable reference, or when self is mutable or is &mut Self?

Since we do the same for locals if their type is a mut ref this sounds good to be consistent. For when the struct instantiation itself(be it a local or whatever) is mutable.
For fields when the owning binding is mutable does sound like an interesting thought as well, though there we probably want to be careful in that if we have a foo.bar.baz, where foo is a mutable thing and bar is a &T we don't want baz to be highlit as mutable.
Makes me also wonder if we should have a second mutable modifier that is used for actual mutable accesses. 🤔

Makes me also wonder if we should have a second mutable modifier that is used for actual mutable accesses unlike the current one that is for this is mutable, but might be used immutably 🤔

Ooh that is a good idea; would that be use for &mut methods and assignments?

Ye receiver of mutable method calls and the place for when writing to places(assignments) was my first thought here.


Route /v1/hooks/events does not exist in gateway client

I am following this guide to setup safe locally Running our services locally
At step 5, create webhook and point it to http://nginx:8000/cgw/v1/hooks/events, but the problem is that route does not exist in client gateway, cannot find from http://localhost:8000/cgw/api# document also
Environment Details
.env component version
CFG_VERSION=latest
CGW_VERSION=latest
TXS_VERSION=latest
UI_VERSION=latest
EVENTS_VERSION=latest

@iamacook is this step still necessary? https://github.com/safe-global/safe-infrastructure/blob/main/docs/running_locally.md#step-5-add-your-webhooks
As far as I know the CGW is reading the events directly from Rabbitmq. Right?

@moisses89 Yes, but we still have a few hooks that can be invoked through the controller. Additionally, we recently introduced a feature that allows all hooks to be triggered via the controller based on your feature flags.

@vietdht The endpoint is excluded from the docs, but you should be able to access it using the POST method.


running mocha without actual test

Hi,
mocha --reporter spec
this usually runs also the test code, sometimes I just want to see the specs, possible to run it with test code? thanks,
Angelo

I'm afraid I don't understand the question.
Seeing how it's a two-year old and inactive issue by now, I'm going to close it. Feel free to comment and I'll re-open if it's still relevant.


[BUG] udev high CPU usage and trouble shutting down on archlinux-zen-6.5.8

Describe the bug
A clear and concise description of what the bug is.
After installing EnvyControl I rebooted into hybrid mode, but my system sat at the shutdown screen with the following text:
229.011736] systemd-shutdown[1): Waiting for process: 361 ((udev-worker)), 350 ((udeu-worker)), 318 ((udeu-worker)), 328 ((udev-worker)), 302 (systemd-udevd) 246.869244) INFO: task (udeu-uorker):318 blocked for more than 122 seconds. 6.5.8 zen1-1-zen 81 OE Ta inted: P ( 216.869514) [ 246.869780 ] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. L 246.870140] INFO: task (udev-worker):328 blocked for more than 122 seconds. [ 246.670412] 6.5.8-zen1-1-zen #1 OE Tainted: P [ 216.870686) "echo 0 > /proc/sys/kernel/hung_task_tineout_secs" disables this message. 246.870996) INFO: task (udeu-worker):361 blocked for than 122 seconds vore 6.5.8- zen1-1-zen #1 Tainted: P OE [ 246.871310] [ 216.871588] "echo 0 > /proc/sys/kernel/hung_task_tincout_secs" disables this message
To Reproduce
Steps to reproduce the behavior:

Run sudo envycontrol -s integrated
Reboot
After booting up system is fine, until after some time udev kicks in with a high CPU usage.

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
System Information:

Model: [Lenovo Legion 5i 15IHM05H]
Distro:  [Arch Linux]
Kernel: [6.5.8-zen]
DE/WM and Display Manager (if applicable): [Gnome 45 with GDM]
EnvyControl version: [3.3.0]
Nvidia driver version: [35.113.01]
lspci output:

00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) (rev 02)
00:02.0 VGA compatible controller: Intel Corporation CometLake-H GT2 [UHD Graphics] (rev 05)
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 02)
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model
00:12.0 Signal processing controller: Intel Corporation Comet Lake PCH Thermal Controller
00:14.0 USB controller: Intel Corporation Comet Lake USB 3.1 xHCI Host Controller
00:14.2 RAM memory: Intel Corporation Comet Lake PCH Shared SRAM
00:14.3 Network controller: Intel Corporation Comet Lake PCH CNVi WiFi
00:15.0 Serial bus controller: Intel Corporation Comet Lake PCH Serial IO I2C Controller #0
00:15.1 Serial bus controller: Intel Corporation Comet Lake PCH Serial IO I2C Controller #1
00:16.0 Communication controller: Intel Corporation Comet Lake HECI Controller
00:17.0 SATA controller: Intel Corporation Device 06d3
00:1d.0 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #9 (rev f0)
00:1d.6 PCI bridge: Intel Corporation Device 06b6 (rev f0)
00:1f.0 ISA bridge: Intel Corporation Comet Lake LPC Controller
00:1f.3 Audio device: Intel Corporation Comet Lake PCH cAVS
00:1f.4 SMBus: Intel Corporation Comet Lake PCH SMBus Controller
00:1f.5 Serial bus controller: Intel Corporation Comet Lake PCH SPI Controller
01:00.0 VGA compatible controller: NVIDIA Corporation TU106M [GeForce RTX 2060 Mobile] (rev a1)
01:00.2 USB controller: NVIDIA Corporation TU106 USB 3.1 Host Controller (rev a1)
01:00.3 Serial bus controller: NVIDIA Corporation TU106 USB Type-C UCSI Controller (rev a1)
06:00.0 Non-Volatile memory controller: Silicon Motion, Inc. SM2263EN/SM2263XT (DRAM-less) NVMe SSD Controllers (rev 03)
07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)

Additional context
Add any other context about the problem here. If possible try to reproduce the problem with --verbose flag and attach its output.
systemctl status systemd-udev
systemd-udevd[26734]: /etc/udev/rules.d/99-switch.rules:1 Unknown group 'plugdev', ignoring.

sudo envycontrol -s integrated --verbose
Switching to integrated mode
Successfully disabled nvidia-persistenced.service
INFO: Created file /etc/modprobe.d/blacklist-nvidia.conf
# Automatically generated by EnvyControl

blacklist nouveau
blacklist nvidia
blacklist nvidia_drm
blacklist nvidia_uvm
blacklist nvidia_modeset
alias nouveau off
alias nvidia off
alias nvidia_drm off
alias nvidia_uvm off
alias nvidia_modeset off

INFO: Created file /lib/udev/rules.d/50-remove-nvidia.rules
# Automatically generated by EnvyControl

# Remove NVIDIA USB xHCI Host Controller devices, if present
ACTION=="add", SUBSYSTEM=="pci", ATTR{vendor}=="0x10de", ATTR{class}=="0x0c0330", ATTR{power/control}="auto", ATTR{remove}="1"

# Remove NVIDIA USB Type-C UCSI devices, if present
ACTION=="add", SUBSYSTEM=="pci", ATTR{vendor}=="0x10de", ATTR{class}=="0x0c8000", ATTR{power/control}="auto", ATTR{remove}="1"

# Remove NVIDIA Audio devices, if present
ACTION=="add", SUBSYSTEM=="pci", ATTR{vendor}=="0x10de", ATTR{class}=="0x040300", ATTR{power/control}="auto", ATTR{remove}="1"

# Remove NVIDIA VGA/3D controller devices
ACTION=="add", SUBSYSTEM=="pci", ATTR{vendor}=="0x10de", ATTR{class}=="0x03[0-9]*", ATTR{power/control}="auto", ATTR{remove}="1"

Operation completed successfully
Please reboot your computer for changes to take effect!

Same problem here.


Puppeteer takes more and more memory over time

Hello, Im using puppeteer to keep my game room 24/7. I have such a script:
const puppeteer = require('puppeteer');
const fs = require('fs');

function sleep(ms){
    return new Promise(resolve=>{
        setTimeout(resolve,ms)
    })
}

(async () => {

    await puppeteer.launch({
        slowMo: 10,
        headless: true,
        args:[
            '--remote-debugging-port=9222',
            '--lang=en-US,en',
            '--no-sandbox',
            '--disable-setuid-sandbox',
        ], ignoreHTTPSErrors: true, dumpio: false }).then(async browser => {

            const page = await browser.newPage();

            try {
                page.on("pageerror", function(err) {
                    theTempValue = err.toString();
                    console.log("Page error: " + theTempValue);
                });

                page.on("error", function (err) {
                    theTempValue = err.toString();
                    console.log("Error: " + theTempValue);
                });

                await page.goto('https://haxball.com/headless', {timeout:90000});
                await page.waitFor(10000);
                await page.evaluate(fs.readFileSync('room.js', 'utf8'));

                while(true)
                {

                    await sleep(1000000000);

                }

            }catch(erro){

                await page.screenshot({path: 'error.png'});

            }

         });

})();

I noticed, that over time, this puppeteer script takes more and more memory:

It slowly takes more and more memory. For example yesterday this script took about 18.3 percent of whole memory. Now this number is 20.8 and it gradually increases, until the point when I need to restart the room.
Im using pm2 to launch my script. I noticed that there are a lot of ongoing chromium processes. Not sure if this is a normal behavior.

Any ideia of how to improve memory comsuption?! it still happening for me - more and more memory is necessary to keep exactly the same page open, only taking functions and firing over EMIT events on my NodeJS.

Yup keeping puppeteer running for long is hogging memory in an pretty unpredictable nature. At tips?
My use case needs me to keep a page open and not disconnect or close the session! All suggestion I find tells us to reuse pages and stuff, but for me, I just need one website to be logged in 24*7, i.e, suffer very less down time. Is puppeteer suitable for that kind of work, if not could you please suggest me other options to puppeteer for the same, and if yes, what kind of optimizations do you guys recommend for such kind of workload?


Add LogFile as a cio IO option

Signed-off-by: Michael Crosby<EMAIL_ADDRESS>

Codecov Report

Merging #2315 into master will decrease coverage by 0.09%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master    #2315     +/-   ##
=========================================
- Coverage   45.51%   45.41%   -0.1%
=========================================
  Files          83       83
  Lines        9190     9210     +20
=========================================
  Hits         4183     4183
- Misses       4331     4351     +20
  Partials      676      676

Flag
Coverage Δ

#linux
49.9% <0%> (-0.14%)
:arrow_down:

#windows
41.24% <ø> (ø)
:arrow_up:

Impacted Files
Coverage Δ

cio/io.go
35.44% <0%> (-12.02%)
: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 c73794f...caf467b. Read the comment docs.

LGTM


How to avoid data loss on shutdown

:wave: Hi, everyone. I work on code search at GitHub and we ❤ metrics.
We have a panic hook that does metrics::increment_counter!("panic");. But we've found that this increment often doesn't make it to the server.
I think our recorder (we're using metrics-expoter-statsd) buffers output and the process is exiting without flushing the buffers. Dropping the recorder before exiting the process would be sufficient, for us. Is there a way to do that? Is there something else I should be doing? I couldn't figure it out from the readme or API docs.
If this already exists, I think there's already a great place to document it (under "Getting started -> In executables") and I'd be happy to write that up.

Hello there!
Reading through your description, I see where you're coming from.
At a high level, there is no way, currently, to drop the recorder as it's installed in such a way that callers can take a 'static reference to it, which means that installing a recorder requires either a &'static dyn Recorder or an owned R: Recorder which we box and then leak, in order to fulfill the 'static requirement.
Most of the ways around this that I can think of would depend on the exporter being able to give back a handle, of some sort, to the caller that is creating/installing the exporter such that the handle would act as the drop guard that could be used to force a flush, etc, when the process is exiting.

Another thought is potentially doing something with Arc<T>/Weak<T> where the weak reference can be wrapped and installed as the recorder and then then Arc<T> could be held as a drop guard so that the true R (being R: Recorder) could be legitimately dropped and have the Drop impl added directly, and not need to write a custom drop guard, with all of the requisite synchronization.
This would still necessitate holding that drop guard directly, rather than the installed recorder being able to handle this, but it would at least be something we could provide a generalized wrapper for.

@jorendorff A bit late, but... I have a PR up for a drop guard primitive, as described in my last comment on this issue, that I'm curious if you would be interested in. At least ,if nothing else, I'm curious to see if this would have helped solve your problem (if you already found a solution and don't care to switch away from it).

Hey @tobz, not OP, but I was facing this same issue with an influx/grafana cloud exporter and fixed it using this approach. Any plans to cut a new release?

Yeah, I'm a little behind on releasing the currently outstanding changes. Hoping to be able to do so this week.

@aig787 Released in<EMAIL_ADDRESS>

Closing this issue as this use case should be generically solved via #362.


Colors messed up with simple config

Using the new 2.0, with this simple config many colors end up changed from their default. When I run without a config the colors are much different. Since I'm not changing any colors it feels like a bug.
require("nightfox").setup {
  options = {
    styles = {
      comments = "italic",
    },
  },
}

vim.cmd "colorscheme nightfox"

Here is what I see on screen with the above config:

Here is what I see on screen when I use the config shown in the picture below:

Same with the minimal init.lua. Here is the init.lua:
-- `minimal_init.lua` used for reproducible configuration
-- Open with `nvim --clean -u minimal_init.lua`

local is_windows = vim.fn.has("win32") == 1
local function join(...)
  local sep = is_windows and "\\" or "/"
  return table.concat({ ... }, sep)
end

local root_tmp = is_windows and os.getenv("TEMP") or "/tmp"
local site_path = join(root_tmp, "nvim", "site")
local pack_path = join(site_path, "pack")
local install_path = join(pack_path, "packer", "start", "packer.nvim")
local compile_path = join(install_path, "plugin", "packer_compiled.lua")
vim.opt.packpath = site_path

local function load_plugins()
  local packer = require("packer")
  local use = packer.use
  packer.reset()
  packer.init({ compile_path = compile_path, package_root = pack_path })

  use("wbthomason/packer.nvim")
  use("EdenEast/nightfox.nvim")
  -- ADD PLUGINS THAT ARE _NECESSARY_ FOR REPRODUCING THE ISSUE

  packer.install()
end

_G.load_config = function()
  -- ADD INIT.LUA SETTINGS THAT ARE _NECESSARY_ FOR REPRODUCING THE ISSUE
  require("nightfox").setup({
	  options = {
	    styles = {
	      comments = "italic",
	    },
	  },
  })

  vim.cmd('colorscheme nightfox')
end

if vim.fn.isdirectory(install_path) == 0 then
  vim.fn.system({ "git", "clone", "--depth=1", "https://github.com/wbthomason/packer.nvim", install_path })
end
load_plugins()
vim.cmd([[autocmd User PackerComplete ++once echo "Ready!" | lua load_config()]])

The images show both the colors I see on screen and the editing on the init.lua being used.
I'm using nvim 0.6.1 on M1 Mac.
The only thing that appear a bit odd in that I can't explain it is that without the setup options I don't see the "Ready!" message. With my setup options I do see the "Ready!" message.
Without the nightfox setup options:

With the nightfox setup options:

Hmmm that is very weird. What terminal are you using? were you able to view italics before? Does the same thing happen if you checkout the [v1.0.0](https://github.com/EdenEast/nightfox.nvim/tree/v1.0.0] tag? Also just to make sure you dont have compiled files.
This can be checked with :NightfoxStatus and cleaned with :NightfoxClean (guessing that that is not the issue because the minimal_init also has the issue)

I use wezterm but just tried on iTerm2 without any difference.
I was using the 1.0.0 tagged version for about a month. Config here: https://github.com/gwww/dotfiles/blob/main/.config/nvim/lua/plugins/nightfox.lua It was working as expected.
I already had run :NightfoxStatus and it had X's for all the compiled entries.
I have switched back and forth between the 1.0.0 and new version a number of times while testing.
Is there any debugging I can try? I tried putting a couple of print statements in config.lua but they did not print. I think its getting called, not sure why the prints did not show up.

I just ran nvim with -V20. Once with empty setup and once with the "broken" setup. I diff'ed the two logs. The only difference is the empty setup has about 300 highlight commands in it. The broken setup has none. Not sure what that means or why.

I am also using wezterm. For my neovim I use nightly

nvim -v
NVIM v0.7.0-dev
Build type: Release
LuaJIT 2.1.0-beta3
Compiled by nixbld

Features: +acl +iconv +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "
/nix/store/k0ycdg3znwf9z7ls867vg6wh3bqgqv74-neovim-unwrapped-master/share/nvim
"

Run :checkhealth for more info

If you are using nvim 0.7 have you updated your nightly recently. Now that I think about it I am trying out the new nvim_set_hl api that was added to the nightly. If you are on nightly but dont have that function then you would not get anything. If that is the case I should add to the current check to see if the nightly version also has the function. The current highlighting function is here.

I'm not running nightly. I've been trying to stay on stable once 0.6.0 dropped. So, does that explain it then -- nvim_set_hl is not in 0.6?

Yes that is currently on nightly set for next release. If you compile does that work? if so then the check might not be correct.

Ah ok so I used 0.6.1 and it looks like I get the same issue. Looks like checking if nvim version is 0.7 does not pass. I will remove the nvim version until I do a better validation with different nvim versions

Running compile worked!
Maybe conditionally use nvim_set_hl if not on 0.7?

Just ran vim.fn.has("nvim-0.7") and it returns either 0 or 1 instead of true or false. Thank you helping me debug this!

Merged change should be resolved now. Please let me know if your issue is resolved or I should re-open your issue

I tested it and it works! Amazing how one wee little test took out the whole plug-in. Thanks for the plug-in and for the fix!!


[Bug] fix steps check

https://github.com/nikolaydubina/llama2.go/blob/5d672807cb9dc6a91bfe45e8c4e5d7c666bc4f08/main.go#L60-L62
steps should be less than config.SeqLen
	// right now we cannot run for more than config.SeqLen steps
	if steps <= 0 || steps >= config.SeqLen {
		steps = config.SeqLen-1
	}

it will cause KeyCache out of range in function Transformer.
				for t := 0; t <= pos; t++ {
					// get the key vector for this head and at this timestamp
					k := s.KeyCache[(loff + t*dim + h*headSize):(loff + (t+1)*dim + h*headSize)]

test case:
 -steps=1023 is ok, otherwise  -steps=1024 will panic the program.

interesting. @datastream recommend submitting this issue/fix to llama2.c too

fixed. thanks @datastream 👍🏻

investigation notes
key_cache len: p->n_layers * p->seq_len * p->dim

if steps is too large
steps == seq_len

at the end of main loop
pos == steps - 1
(pos == seq_len - 1)

at the end of loop in transformer
t == pos (thus, t == seq_len - 1)
float* k = s->key_cache + loff + t * dim + h * head_size;

l == num_layers-1
loff == l * p->seq_len * dim

h == num_heads - 1

then loop up to head size + head_size.

---

thus k  = (num_layers-1) * seq_len * dim + (seq_len-1) * dim + (num_heads-1) * head_size + (head_size - 1)
k = num_layers * seq_len * dim - seq_len * dim + seq_len * dim - dim + num_heads * head_size - head_size + head_size - 1
k = num_layers * seq_len * dim - dim + num_heads * head_size - 1
k = num_layers * seq_len * dim - dim + num_heads * dim / num_heads - 1
k = num_layers * seq_len * dim - 1

max_k index = num_layers * seq_len * dim - 1

dim = 768
num_heads = 12
head_size = dim  / num_heads

---

thus official run.c code is correct and does not breach array size.


osfv_cli/models/minnowmax.yml: wip

Not tested.
Can be tested via:
osfv_cli rte --rte_ip <IP_ADDRESS> --model minnowmax flash probe

This worked for me, thanks
DUT model retrieved from cmdline, skipping Snipe-IT query
Probing flash...
Executing command: flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=16000
flashrom v1.3.0 on Linux 5.4.69 (armv7l)
flashrom is free software, get the source code at https://flashrom.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).

Found Winbond flash chip "W25Q64BV/W25Q64CV/W25Q64FV" (8192 kB, SPI) on linux_spi.

Found Winbond flash chip "W25Q64JV-.Q" (8192 kB, SPI) on linux_spi.

Multiple flash chip definitions match the detected chip(s): "W25Q64BV/W25Q64CV/W25Q64FV", "W25Q64JV-.Q"
Please specify which chip definition to use with the -c <chipname> option.


Model predict returns result of different quality then validation declares.

Environment info
Operating System: Fedora 24
CPU: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz
C++/Python/R version: Python 3.6.6
Conda env:

python=3.6
numpy=1.15
scikit-learn=0.19.1
pandas=0.23.3
matplotlib=2.2.2
jupyter
jupyterlab
pip:

sklearn-pandas==1.6.0
featuretools==0.2.1
lightgbm==2.2.0
tqdm

Problem description
I create train and valid datasets and run training with this two datasets. All the values are int, float or nan. Some of the columns are categorical [encoded by LabelEncoder].
When I run training I got some valid's rmse and best iteration number. Then I call a predict method on the valid dataframe and I got ... different rmse value.
Am I using categorical features in a not correct way? When I treat all the features as a non-categorical features (I mean delete all three 'categorical_feature=cat_cols' from the code) then problem do NOT exists. I try different boosting methods but problem also exists.
I the below example difference is around 0.006 but I also have an examples in which the gap is much bigger around 0.05.
Reproducible examples
    params = {"objective" : "regression", "metric" : "l2_root","verbose" : -1}

    train_data = lgb.Dataset(data=X_train,
                             label=y_train,
                             categorical_feature=cat_cols,
                             free_raw_data=False)

    valid_data = lgb.Dataset(data=X_valid,
                             label=y_valid,
                             categorical_feature=cat_cols,
                             free_raw_data=False)

    model = lgb.train(train_set = train_data,
                      params = params,
                      num_boost_round = NUM_ROUNDS,
                      early_stopping_rounds = STOP_ROUNDS,
                      categorical_feature=cat_cols,
                      valid_sets=[train_data, valid_data],
                      verbose_eval = VERBOSE_EVAL)

    print('best iter:', model.best_iteration)

    y_valid_pred = model.predict(X_valid)
    print(mean_squared_error(y_valid, y_valid_pred) ** 0.5)

Output
Early stopping, best iteration is:
[97]	training's rmse: 1.43167	valid_1's rmse: 1.6823
best iter: 97
1.6882881181967648

@rybickibartek can you try "reg_sqrt=false" ?

To be honest when I restart my computer problem does not occur. But I will try req_sort = false in the case of the same problem, and give you a feedback about the effect.

Feel free to reopen if needed.


CPLP-1390-dragndrop-design-changes

@oyo  quick info on that, I am ok if this drag and drop is slightly different to your component. Since we cant use the portal component and the registration component was really not nice, Deep did a new implementation of the component for the registration app


token-icons library update

hey, I've realized that LightDotSo is using token-icons, here.
The repository's name has been updated to web3icons, because I'm going to expand the library to include more than tokens, (networks and wallets and more in the future) I was going to open a PR for it but I also realized the referenced path is for not-optimized svgs, wanted to flag that.
The way it works, @web3icons/core package creates a dist folder with optimized svgs. However, I understand that you might not need to directly depend on the package and there is no API or hosted service for the optimized svgs.
LMK If I can help in any way.

@0xa3k5 Thank you for this! Will update the URL accordingly, but since we're not loading the svgs (lazy calling them on the client), we won't have the capability to load your optimized svgs bundled. Regardless, I really appreciate the https://github.com/0xa3k5/web3icons and thank you for your contributions to the community!

thank you! Yeah that makes sense, if I can spare some time I'm thinking about building an api for this so I can host the optimized svgs, or maybe some other way. I'll open an issue/PR if necessary in the future.
Awesome job on the light.so btw, amazing work!

That would be awesome!! Will be on hold for the API 🫡 Appreciate the awesome work 🙏

hey @shunkakinoki I've just updated the monorepo to host/serve the optimized svgs from the core/svgs path. You can just update the URL
from: https://raw.githubusercontent.com/0xa3k5/token-icons/main/packages/core/src/raw-svgs/tokens/branded/${token.symbol.toUpperCase()}.svg
to: https://raw.githubusercontent.com/0xa3k5/web3icons/main/packages/core/src/svgs/tokens/branded/${token.symbol.toUpperCase()}.svg
you should be able to use the optimized svgs without changing much for now 😅

@0xa3k5 That's awesome!! Thank you so much for getting back to me - means a lot
Would you want to submit a PR for recognition or should I go ahead and implement it?
Appreciate the awesome work.


solar charge

Hello, I'm attempting to charge an 18650 battery using a 6V, 15W solar panel. However, it seems to only reach approximately 3.5V in charge.The board is connected to the internet continuously, with no Bluetooth, consuming an estimated 150-200mAh.
SUNYIMA 6V 15W

How much power / current is the panel actually producing? Perhaps it's only just covering the 150-200mA needed to run the board.
Cheap solar panel ratings are often quite optimistic.


Clarify expected use for inlayHint/refresh

I'm implementing InlayHints and noticed an issue with them not refreshing in VS Code when I need them to.
file1
final foo = getThing();

file2
String getThing() {}

If I enable inlay hints, file1 gets a String hint on foo to show that the inferred type is Foo.
However, if I modify file2 and change String to int, VS Code does not know to refresh the labels in file1 (I have both files open side-by-side).
It seems like the answer to this is to call inlayHint/refresh, however:

It doesn't take a filename, so will refresh them for every single file
Doing this essentially on every file modification sounds like it could result in a lot of additional requests
The spec makes it sound like we shouldn't be calling this often:   * Note that this event is global and will force the client to refresh all
   * inlay hints currently shown. It should be used with absolute care and
   * is useful for situation where a server for example detects a project wide
   * change that requires such a calculation.

How is this intended to work? What are the responsibilities of the client, and what are the responsibilities of the server to ensure these labels are kept up-to-date when they reference functions from other files?

@jrieken @alexdima sounds familiar :-) We had the same discussion with semantic tokens and captured the solution we landed on here: https://github.com/microsoft/vscode/issues/130486#issuecomment-938590332
But looks like we never implemented it in VS Code hence no adoption in LSP.
For inlay hints I propose to follow the same proposed pattern.

@dbaeumer do I understand correctly that this proposal means the server will need to send the refresh call? Does VS Code automatically refresh them for the current file after changes?
So from the servers perspective, whenever a file is modified, it should compute if any other files could be affected by the change (for example, whether any public API changed) and then send this ("global") event to invalidate all inlay hints the client has?

pylance is having the same issue. almost any change in a file can cause semantic change in other files that depend on the file that has changed.
currently, since refresh doesn't take any params, we need to send this global refresh for both semantic token and inlay hint if any file that depends on the file is currently opened.
that cause all open files to get new semantic token and inlay hint requests even if most of them don't need to be refreshed. things get worse if some of them are notebooks since all of cells will be asked to be refreshed as well.
but for semantic token case, most of work could be avoided using the previousResultId, when files that no need to be refreshed gets the request, we can simply return previousResultId with no changes.
but for inlayHint case, there is no such capability, so there is no other way but fulfill the request. we could cache the previous results and re-send them, but unlike semantic token case, it could be a lot of same data we kept re-sending for every char user types for all open files.
I think either refresh should take list of files we want to refresh or inlayhint should have similar concept as previousResultId

@dbaeumer any update on this?

@heejaechang I see the problem for inlay hints however this can't be fixed on the LSP client side only. As outlined here https://github.com/microsoft/vscode/issues/130486#issuecomment-938590332 this needs also be addressed in the editor (e.g. VS Code) because you will have the same problem without LSP. I could simply add something to LSP but its capability would be off for VS Code which in the end will not help you. So we need to push for https://github.com/microsoft/vscode/issues/130486 to make progress on this.


feature：need a permanent offline resource to speed up offline e2e

add a special vm to provide minio binary resource of each os resource  and iso resource, provide registry for amd and arm images

/kind feature

do this temporarily

done


Nodes not hosting API VIP IP fail dial tcp <IP_ADDRESS>:6443: connect: invalid argument

After some time of cluster being up it starts to fail with errors like:
Apr 12 09:48:31 master-1 hyperkube[23740]: E0412 09:48:31.776526   23740 kubelet.go:2273] node "master-1" not found
Apr 12 09:48:31 master-1 hyperkube[23740]: E0412 09:48:31.843612   23740 reflector.go:125] k8s.io/kubernetes/pkg/kubelet/kubelet.go:453: Failed to list *v1.Node: Get https://api.ostest.test.metalkube.org:6443/ap
i/v1/nodes?fieldSelector=metadata.name%3Dmaster-1&limit=500&resourceVersion=0: dial tcp <IP_ADDRESS>:6443: connect: invalid argument
Apr 12 09:48:31 master-1 hyperkube[23740]: E0412 09:48:31.844422   23740 reflector.go:125] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Get https://api.ostest.test.metalkube.org:
6443/api/v1/pods?fieldSelector=spec.nodeName%3Dmaster-1&limit=500&resourceVersion=0: dial tcp <IP_ADDRESS>:6443: connect: invalid argument
Apr 12 09:48:31 master-1 hyperkube[23740]: E0412 09:48:31.876801   23740 kubelet.go:2273] node "master-1" not found
Apr 12 09:48:31 master-1 hyperkube[23740]: E0412 09:48:31.977082   23740 kubelet.go:2273] node "master-1" not found
Apr 12 09:48:32 master-1 hyperkube[23740]: E0412 09:48:32.054813   23740 reflector.go:125] k8s.io/kubernetes/pkg/kubelet/kubelet.go:444: Failed to list *v1.Service: Get https://api.ostest.test.metalkube.org:6443
/api/v1/services?limit=500&resourceVersion=0: dial tcp <IP_ADDRESS>:6443: connect: invalid argument

Attempt to ping this ip from any other master nodes(except the one that hosts the ip) fails:
[root@master-1 ~]# ip a | grep <IP_ADDRESS>
[root@master-1 ~]# ping <IP_ADDRESS>
connect: Invalid argument
[root@master-1 ~]# curl -4kvL <IP_ADDRESS>:6443
* Rebuilt URL to: <IP_ADDRESS>:6443/
*   Trying <IP_ADDRESS>...
* TCP_NODELAY set
* Immediate connect fail for <IP_ADDRESS>: Invalid argument
* Closing connection 0
curl: (7) Couldn't connect to server
[root@master-1 ~]# curl -4kvL api.ostest.test.metalkube.org:6443
* Rebuilt URL to: api.ostest.test.metalkube.org:6443/
*   Trying <IP_ADDRESS>...
* TCP_NODELAY set
* Immediate connect fail for <IP_ADDRESS>: Invalid argument
* Closing connection 0
curl: (7) Couldn't connect to server
[root@master-1 ~]#

[root@master-2 ~]# ip a | grep <IP_ADDRESS>
[root@master-2 ~]# ping <IP_ADDRESS>
connect: Invalid argument
[root@master-2 ~]# curl -4kvL <IP_ADDRESS>:6443
* Rebuilt URL to: <IP_ADDRESS>:6443/
*   Trying <IP_ADDRESS>...
* TCP_NODELAY set
* Immediate connect fail for <IP_ADDRESS>: Invalid argument
* Closing connection 0
curl: (7) Couldn't connect to server
[root@master-2 ~]# curl -4kvL api.ostest.test.metalkube.org:6443
* Rebuilt URL to: api.ostest.test.metalkube.org:6443/
*   Trying <IP_ADDRESS>...
* TCP_NODELAY set
* Immediate connect fail for <IP_ADDRESS>: Invalid argument
* Closing connection 0
curl: (7) Couldn't connect to server
[root@master-2 ~]#

and from master-0 that handles the API VIP IP
[root@master-0 ~]# ip a |grep <IP_ADDRESS>
    inet <IP_ADDRESS>/32 scope global ens4
[root@master-0 ~]# curl -4klv api.ostest.test.metalkube.org:6443
* Rebuilt URL to: api.ostest.test.metalkube.org:6443/
*   Trying <IP_ADDRESS>...
* TCP_NODELAY set
* Connected to api.ostest.test.metalkube.org (<IP_ADDRESS>) port 6443 (#0)
> GET / HTTP/1.1
> Host: api.ostest.test.metalkube.org:6443
> User-Agent: curl/7.61.1
> Accept: */*
>
Warning: Binary output can mess up your terminal. Use "--output -" to tell
Warning: curl to output it to your terminal anyway, or consider "--output
Warning: <FILE>" to save to a file.
* Failed writing body (0 != 7)
* Closing connection 0
[root@master-0 ~]# curl -4klv <IP_ADDRESS>:6443
* Rebuilt URL to: <IP_ADDRESS>:6443/
*   Trying <IP_ADDRESS>...
* TCP_NODELAY set
* Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 6443 (#0)
> GET / HTTP/1.1
> Host: <IP_ADDRESS>:6443
> User-Agent: curl/7.61.1
> Accept: */*
>
Warning: Binary output can mess up your terminal. Use "--output -" to tell
Warning: curl to output it to your terminal anyway, or consider "--output
Warning: <FILE>" to save to a file.
* Failed writing body (0 != 7)
* Closing connection 0
[root@master-0 ~]#

/cc @mcornea @achuzhoy @celebdor

Thanks for the report, can you provide the keepalived logs from all masters please?

@hardys logs from keepalieved containers

Worth mentioning that both masters and workers nodes end up in NotReady status:
oc get nodes
NAME       STATUS     ROLES    AGE     VERSION
master-0   NotReady   master   3d2h    v1.13.4+1ad602308
master-1   NotReady   master   3d2h    v1.13.4+1ad602308
master-2   NotReady   master   3d2h    v1.13.4+1ad602308
worker-0   NotReady   worker   2d22h   v1.13.4+1ad602308

Hit this issue in my deployment, only master-2 went to NotReady. Exact same issue described in this issue.

@yprokule , seems like there's L2 connectivity issue for <IP_ADDRESS> (as ping doesn't work) ,

Could you please run the same test for <IP_ADDRESS> (DNS) and <IP_ADDRESS> (INGRESS)?
Could you please attach the output of arp table (arp -a)  from all nodes?

@yboaron
master-0
[root@master-0 ~]# ping -c1 <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=64 time=0.029 ms

--- <IP_ADDRESS> ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.029/0.029/0.029/0.000 ms
[root@master-0 ~]# ping -c1 <IP_ADDRESS>
connect: Invalid argument

master-1
[root@master-1 ~]# ping -c1 <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=64 time=0.174 ms

--- <IP_ADDRESS> ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.174/0.174/0.174/0.000 ms
[root@master-1 ~]# ping -c1 <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=64 time=0.213 ms

--- <IP_ADDRESS> ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.213/0.213/0.213/0.000 ms

master-2
root@master-2 ~]# ping -c1 <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=64 time=0.163 ms

--- <IP_ADDRESS> ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.163/0.163/0.163/0.000 ms
[root@master-2 ~]# ping -c1 <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=64 time=0.030 ms

--- <IP_ADDRESS> ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.030/0.030/0.030/0.000 ms

on other nodes
Apr 15 16:15:41 master-2 hyperkube[121307]: E0415 16:15:41.413449  121307 kubelet.go:2273] node "master-2" not found
Apr 15 16:15:41 master-2 hyperkube[121307]: E0415 16:15:41.497345  121307 reflector.go:125] k8s.io/kubernetes/pkg/kubelet/kubelet.go:444: Failed to list *v1.Service: services is forbidden: User "system:anonymous" cannot list resource "services" in API group "" at the cluster scope
Apr 15 16:15:41 master-2 hyperkube[121307]: E0415 16:15:41.498449  121307 reflector.go:125] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: pods is forbidden: User "system:anonymous" cannot list resource "pods" in API group "" at the cluster scope

@yprokule , I think that I found something.
Master-0 doesn't hold the API VIP (<IP_ADDRESS>) but I can still see the following HOST entry in the routing table:
<IP_ADDRESS> dev ens4 proto kernel scope link src <IP_ADDRESS> metric 101
So, when Master-0 try to send any packet to  <IP_ADDRESS>, network stack fail with 'connect: Invalid argument' .
I deleted the <IP_ADDRESS> route from Master-0 , and now I'm able to ping <IP_ADDRESS>.
[core@master-0 ~]$ sudo ip route del <IP_ADDRESS>/32
[core@master-0 ~]$ ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=64 time=0.170 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=64 time=0.098 ms
64 bytes from <IP_ADDRESS>: icmp_seq=3 ttl=64 time=0.252 ms
64 bytes from <IP_ADDRESS>: icmp_seq=4 ttl=64 time=0.210 ms
^C
--- <IP_ADDRESS> ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 92ms
rtt min/avg/max/mdev = 0.098/0.182/0.252/0.058 ms
[core@master-0 ~]$

yep deleting the incorrect route fixed the notready state of the node, which was simply not able to reach the api to report status

I See @karmab has a WIP patch for this here: https://github.com/openshift-metalkube/dev-scripts/pull/369

seems like a RHCOS/RHEL bug, I filed bz for that https://bugzilla.redhat.com/show_bug.cgi?id=1700415

a different workaround here: https://github.com/openshift-metalkube/dev-scripts/pull/377

We've got an open bug tracking the kernel issue.  In the meantime, we've updated our config such that the undeleted route won't cause a problem anymore.  See #377


wm_raw_data2formula -> wm_partial_answer

[x] gallery: "unclassified" should be for parts of recordings
[x] api/set-accept.php
[x] api/index.php
[x] admin/index.php

Next actions:

[x] grep -rni "wm_raw_data2formula" * to make sure no dependent code is left.
[x] run tools/move_answers.py
[ ] delete table wm_raw_data2formula

wm_strokes_to_symbol seems to be the same as wm_partial_answer


Not recognizing simple errors in c++

I introduce the simplest possible syntax errors into my c++ code, but the errors are not detected. An example of one of these errors is shown below; however, any simple error - a missing semicolon for example - will go undetected.
#include <unistd.h>
include <sys/epoll.h>
#include <sstream>

I am using VIM version 7.4 with patches 1-160, GCC version 4.8.5, and Syntastic version 3.8.0-108. The output produced when I check SyntasticInfo is shown below.
Syntastic version: 3.8.0-108 (Vim 704, Linux)
Info for filetype: cpp
Global mode: active
Filetype cpp is active
The current file will be checked automatically
Available checker: gcc
Currently enabled checker: gcc

Here is my .vimrc:
let g:syntastic_always_populate_loc_list = 1
let g:syntastic_auto_loc_list = 1
let g:syntastic_check_on_open = 1
let g:syntastic_check_on_wq = 0

let g:syntastic_cpp_checkers=['gcc']
let g:syntastic_cpp_check_header = 1
let g:syntastic_cpp_auto_refresh_includes = 1
let g:syntastic_cpp_config_file = '.syntastic_cpp_config'
let g:syntastic_debug = 3

In the top level of my project folder I have a file called ".syntastic_cpp_config". Its contents is shown below. I added this folder and the line let g:syntastic_cpp_config_file = '.syntastic_cpp_config' in my .vimrc config file because before syntastic would only show me one error in each source file at the very first include of one of the header files.
-gidalia/include/gidalia
-gidalia/include/gidalia/channels
-gidalia/include/gidalia/rw

It's long but here is the :mes output when I set syntastic_debug to 3. I notice that maybe there is an issue with what I did to treat include files, because now I see multiple variations of 'g++: error: unrecognized command line option ‘-gidalia/include/gidalia’' in the :mes output.
"/windump/public/nivela/gidalia/src/channels/sock.cpp" 1148L, 31145C
syntastic: 48.845451: g:syntastic_version = '3.8.0-108 (Vim 704, Linux)'
syntastic: 48.845742: &shell = '/bin/bash', &shellcmdflag = '-c', &shellpipe = '2>&1| tee', &shellquote = '', &shellredir = '>%s 2>&1', &shelltemp = 1, &shellxquote = '', &autochdir = 0, &shellxescape = ''
syntastic: 48.846766: UpdateErrors (auto): default checkers
syntastic: 48.847342: CacheErrors: default checkers
syntastic: 48.848023: g:syntastic_aggregate_errors = 0
syntastic: 48.848452: getcwd() = '/usr'
syntastic: 48.902780: CacheErrors: Invoking checker: cpp/gcc
syntastic: 48.910263: SyntasticMake: called with options: {'postprocess': [], 'errorformat': '%-G%f:%s:,%f:%l:%c: %trror: %m,%f:%l:%c: %tarning: %m,%f:%l:%c: %m,%f:%l: %trror: %m,%f:%l: %tarning: %m,%f:%l: %m', 'makeprg': '''g++'' -x c++ -fsyntax-only  -I. -I.. -Iinclude -Iincludes -I../include -I../includes -tachyo
n/include/gidalia -gidalia/include/gidalia/channels -gidalia/include/gidalia/rw  /windump/public/nivela/gidalia/src/channels/sock.cpp'}
syntastic: 49.032583: system: command run in 0.121697s
syntastic: 49.032891: checker output: ['g++: error: unrecognized command line option ‘-gidalia/include/gidalia’', 'g++: error: unrecognized command line option ‘-gidalia/include/gidalia/channels’', 'g++: error: unrecognized command line option ‘-gidalia/include/gidalia/rw’', '']
syntastic: 49.033997: raw loclist: [{'lnum': 0, 'bufnr': 0, 'col': 0, 'valid': 0, 'vcol': 0, 'nr': -1, 'type': '', 'pattern': '', 'text': 'g++: error: unrecognized command line option ‘-gidalia/include/gidalia’'}, {'lnum': 0, 'bufnr': 0, 'col': 0, 'valid': 0, 'vcol': 0, 'nr': -1, 'type': '', 'pattern': '', 'text': '
g++: error: unrecognized command line option ‘-gidalia/include/gidalia/channels’'}, {'lnum': 0, 'bufnr': 0, 'col': 0, 'valid': 0, 'vcol': 0, 'nr': -1, 'type': '', 'pattern': '', 'text': 'g++: error: unrecognized command line option ‘-gidalia/include/gidalia/rw’'}, {'lnum': 0, 'bufnr': 0, 'col': 0, 'valid': 0, 'vcol'
: 0, 'nr': -1, 'type': '', 'pattern': '', 'text': ''}]
syntastic: 49.034526: getLocList: checker cpp/gcc returned 1
syntastic: 49.034785: cpp/gcc raw: [{'lnum': 0, 'bufnr': 0, 'col': 0, 'valid': 0, 'vcol': 0, 'nr': -1, 'type': '', 'pattern': '', 'text': 'g++: error: unrecognized command line option ‘-gidalia/include/gidalia’'}, {'lnum': 0, 'bufnr': 0, 'col': 0, 'valid': 0, 'vcol': 0, 'nr': -1, 'type': '', 'pattern': '', 'text': '
g++: error: unrecognized command line option ‘-gidalia/include/gidalia/channels’'}, {'lnum': 0, 'bufnr': 0, 'col': 0, 'valid': 0, 'vcol': 0, 'nr': -1, 'type': '', 'pattern': '', 'text': 'g++: error: unrecognized command line option ‘-gidalia/include/gidalia/rw’'}, {'lnum': 0, 'bufnr': 0, 'col': 0, 'valid': 0, 'vcol'
: 0, 'nr': -1, 'type': '', 'pattern': '', 'text': ''}]
syntastic: 49.035303: quiet_messages filter: {}
syntastic: 49.035535: getLocList: checker cpp/gcc run in 0.132519s
syntastic: 49.036031: aggregated: {'_sorted': 0, '_name': '', '_owner': 1, '_columns': 1, '_rawLoclist': []}
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Jun 10 2014 06:55:55)
Syntastic version: 3.8.0-108 (Vim 704, Linux)
Info for filetype: cpp
Global mode: active
Filetype cpp is active
The current file will be checked automatically
Available checker: gcc
Currently enabled checker: gcc
syntastic: 230.635333: &shell = '/bin/bash', &shellcmdflag = '-c', &shellpipe = '2>&1| tee', &shellquote = '', &shellredir = '>%s 2>&1', &shelltemp = 1, &shellxquote = '', &autochdir = 0, &shellxescape = ''
E492: Not an editor command: SyntasticVersion
Syntastic version: 3.8.0-108 (Vim 704, Linux)
Info for filetype: cpp
Global mode: active
Filetype cpp is active
The current file will be checked automatically
Available checker: gcc
Currently enabled checker: gcc
syntastic: 248.295631: &shell = '/bin/bash', &shellcmdflag = '-c', &shellpipe = '2>&1| tee', &shellquote = '', &shellredir = '>%s 2>&1', &shelltemp = 1, &shellxquote = '', &autochdir = 0, &shellxescape = ''
"/windump/public/nivela/gidalia/src/channels/sock.cpp" 1148L, 31144C written
syntastic: 338.578938: g:syntastic_version = '3.8.0-108 (Vim 704, Linux)'
syntastic: 338.579236: &shell = '/bin/bash', &shellcmdflag = '-c', &shellpipe = '2>&1| tee', &shellquote = '', &shellredir = '>%s 2>&1', &shelltemp = 1, &shellxquote = '', &autochdir = 0, &shellxescape = ''
syntastic: 338.579943: UpdateErrors (auto): default checkers
syntastic: 338.580964: CacheErrors: default checkers
syntastic: 338.582401: g:syntastic_aggregate_errors = 0
syntastic: 338.582786: getcwd() = '/usr'
syntastic: 338.583736: CacheErrors: Invoking checker: cpp/gcc
syntastic: 338.588421: SyntasticMake: called with options: {'postprocess': [], 'errorformat': '%-G%f:%s:,%f:%l:%c: %trror: %m,%f:%l:%c: %tarning: %m,%f:%l:%c: %m,%f:%l: %trror: %m,%f:%l: %tarning: %m,%f:%l: %m', 'makeprg': '''g++'' -x c++ -fsyntax-only  -I. -I.. -Iinclude -Iincludes -I../include -I../includes -tachy
on/include/gidalia -gidalia/include/gidalia/channels -gidalia/include/gidalia/rw  /windump/public/nivela/gidalia/src/channels/sock.cpp'}
syntastic: 338.620038: system: command run in 0.031002s
syntastic: 338.620330: checker output: ['g++: error: unrecognized command line option ‘-gidalia/include/gidalia’', 'g++: error: unrecognized command line option ‘-gidalia/include/gidalia/channels’', 'g++: error: unrecognized command line option ‘-gidalia/include/gidalia/rw’', '']
syntastic: 338.621348: raw loclist: [{'lnum': 0, 'bufnr': 0, 'col': 0, 'valid': 0, 'vcol': 0, 'nr': -1, 'type': '', 'pattern': '', 'text': 'g++: error: unrecognized command line option ‘-gidalia/include/gidalia’'}, {'lnum': 0, 'bufnr': 0, 'col': 0, 'valid': 0, 'vcol': 0, 'nr': -1, 'type': '', 'pattern': '', 'text':
'g++: error: unrecognized command line option ‘-gidalia/include/gidalia/channels’'}, {'lnum': 0, 'bufnr': 0, 'col': 0, 'valid': 0, 'vcol': 0, 'nr': -1, 'type': '', 'pattern': '', 'text': 'g++: error: unrecognized command line option ‘-gidalia/include/gidalia/rw’'}, {'lnum': 0, 'bufnr': 0, 'col': 0, 'valid': 0, 'vcol
': 0, 'nr': -1, 'type': '', 'pattern': '', 'text': ''}]
syntastic: 338.621903: getLocList: checker cpp/gcc returned 1
syntastic: 338.622148: cpp/gcc raw: [{'lnum': 0, 'bufnr': 0, 'col': 0, 'valid': 0, 'vcol': 0, 'nr': -1, 'type': '', 'pattern': '', 'text': 'g++: error: unrecognized command line option ‘-gidalia/include/gidalia’'}, {'lnum': 0, 'bufnr': 0, 'col': 0, 'valid': 0, 'vcol': 0, 'nr': -1, 'type': '', 'pattern': '', 'text':
'g++: error: unrecognized command line option ‘-gidalia/include/gidalia/channels’'}, {'lnum': 0, 'bufnr': 0, 'col': 0, 'valid': 0, 'vcol': 0, 'nr': -1, 'type': '', 'pattern': '', 'text': 'g++: error: unrecognized command line option ‘-gidalia/include/gidalia/rw’'}, {'lnum': 0, 'bufnr': 0, 'col': 0, 'valid': 0, 'vcol
': 0, 'nr': -1, 'type': '', 'pattern': '', 'text': ''}]
syntastic: 338.622700: quiet_messages filter: {}
syntastic: 338.622926: getLocList: checker cpp/gcc run in 0.038971s
syntastic: 338.623413: aggregated: {'_sorted': 0, '_name': '', '_owner': 1, '_columns': 1, '_rawLoclist': []}

Thanks for your time and for building a really cool tool!

I notice that maybe there is an issue with what I did to treat include files, because now I see multiple variations of 'g++: error: unrecognized command line option ‘-gidalia/include/gidalia’' in the :mes output.

I'm not sure what exactly you're asking here.  Syntastic doesn't know about C++ syntax.  What syntastic does is run g++ against your files, and parses the output.  If g++ complains about the options you pass it, there is nothing syntastic can do about it.

Thanks for the quick response. The error (or lack of error detection rather) was being caused by something to do with the ".syntastic_cpp_config" file and the line let g:syntastic_cpp_config_file = '.syntastic_cpp_config' in my .vimrc config file. I removed those and it is now working, but it was not working without them earlier. I changed many things between now and then, so I am not sure what is allowing it to work now.

The error was caused by you adding -gidalia/include/gidalia to the file .syntastic_cpp_config.  Said file is supposed to contain valid g++ options, and according to your compiler -gidalia/include/gidalia isn't valid.  That's all there is to it.

Thank you very much. After replying the first time I realized I had not solved the issue, but now it is working. For anyone else with this issue, I needed to add 'I' after each hyphen in the .syntastic_cpp_config  file because otherwise they are invalid arguments to g++.


feat: add errgroup

Overview
closes #7

Codecov Report

Merging #32 (625318e) into main (8258fae) will increase coverage by 0.98%.
The diff coverage is 90.69%.

@@            Coverage Diff             @@
##             main      #32      +/-   ##
==========================================
+ Coverage   76.37%   77.35%   +0.98%
==========================================
  Files           7        7
  Lines         237      265      +28
==========================================
+ Hits          181      205      +24
- Misses         29       31       +2
- Partials       27       29       +2

Impacted Files
Coverage Δ

utils.go
85.71% <90.00%> (+1.09%)
:arrow_up:

clean.go
67.70% <100.00%> (-0.66%)
:arrow_down:

restore.go
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 8258fae...625318e. Read the comment docs.


Add documentation for analyzer "AdditionalFiles"

See all the user comments in https://github.com/dotnet/project-system/issues/879. The current terminology seems confusing, with no documentation at all. We should add documentation for current concept of AdditionalFiles BuildAction, which is based upon the /additionalFile:<File> compiler switch that passes non-source additional files to analyzers. You can read more detailed documentation about additional files in C#/VB compilers at https://github.com/dotnet/roslyn/blob/master/docs/analyzers/Using Additional Files.md

Tagging @gewarren

@mavasani How does this look? https://review.docs.microsoft.com/en-us/visualstudio/ide/build-actions?view=vs-2017&branch=pr-en-us-3326

LGTM. Thanks for adding the documentation!

Also tagging @davkean and @pilchie

Definitely a nit-pick but to me:

This build action is mainly used in analyzer projects

implies that you only use this if you are building an analyzer, when in fact the primary use case is in consuming an analyzer.  Perhaps something like:

This build action is mainly used to provide inputs to analyzers used in the project

@Pilchie Yes, that makes much more sense, thanks for clarifying that.


Ambiclimate

Description:
https://www.ambiclimate.com/en/
Smart AC controller
Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#8693
Example entry for configuration.yaml (if applicable):
climate:
  - platform: ambiclimate
    client_id: ''
    client_secret: ''

Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.

If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[x] New dependencies have been added to the REQUIREMENTS variable ([example][ex-requir]).
[x] New dependencies are only imported inside functions that use them ([example][ex-import]).
[x] New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[x] New files were added to .coveragerc.

@andrewsayre Thanks for your review.
Should client_id and client_secret be be added in the gui or the config yaml?
Ref: https://github.com/home-assistant/architecture/issues/139

@andrewsayre Thanks for your review.
Should client_id and client_secret be be added in the gui or in the config yaml?
Ref: home-assistant/architecture#139

Hah, and yes @balloob weighed in on Discord to confirm that's the direction!  Sorry about that!
I do still suggest implementing a config entry/flow for the refresh token logic as you can then create a new config flow if the token can't be refresh, instead of ignore the failure as it does now.  Not required though to move this PR forward.

Still missing tests and to update the documentation

@andrewsayre any comments?

@andrewsayre any comments?

Are you looking for WIP feedback or think this is ready for the final review?  I see build isn't passing and the conversations aren't updated/resolved, so if you could clarify what you'd like assistant with that will help me focus! :)

The code is ready for review.
Still need to make tests and update the requirements file.

The code is ready for review.
Still need to make tests and update the requirements file.

I'm seeing previous review comments not addressed -- like using a webhook over a custom HTTP view.  Can you please review the previous feedback conversations and make sure they are addressed?  Comment and mark them resolved if you've updated the code.

I do not think it is possible to use the webhook component here, since the oauth authorization requires a fix callback URL that is associated with the client id and client secret.
(It also needs to support get requests)

This conversation might be relevant to this PR too:
https://github.com/home-assistant/home-assistant/pull/19548#discussion_r260511482

Martin: Thanks for another great review.
Still need to add tests and update the documentation.
Probably also optimize the config flow a bit.


R-Car-Starter-Kit-gen3.md: Switch from xz to bz2

Update the documentation following the switch of
the archives produced by bitbake from xz to bz2.
Bug-AGL: SPEC-786
Signed-off-by: Leon Anavi<EMAIL_ADDRESS>

@dl9pf these are the files produced in my case by bitbake:
leon@leon-desktop-G1:/media/storage/agl-rcar3/build$ ls tmp/deploy/images/m3ulcb/agl-demo-platform-m3ulcb*
tmp/deploy/images/m3ulcb/agl-demo-platform-m3ulcb-20170728100952.rootfs.cpio.gz
tmp/deploy/images/m3ulcb/agl-demo-platform-m3ulcb-20170728100952.rootfs.ext4
tmp/deploy/images/m3ulcb/agl-demo-platform-m3ulcb-20170728100952.rootfs.manifest
tmp/deploy/images/m3ulcb/agl-demo-platform-m3ulcb-20170728100952.rootfs.tar.bz2
tmp/deploy/images/m3ulcb/agl-demo-platform-m3ulcb.cpio.gz
tmp/deploy/images/m3ulcb/agl-demo-platform-m3ulcb.ext4
tmp/deploy/images/m3ulcb/agl-demo-platform-m3ulcb.manifest
tmp/deploy/images/m3ulcb/agl-demo-platform-m3ulcb.tar.bz2

As far as I remember I built the image from scratch yesterday. I haven't changed any of the configurations for the archive. Why is it tar.bz2?
Best regards,
Leon

Did you keep your conf/local.conf over a few syncs ?
repo might have stale branches.
check repo manifest / repo manifest -r
and sync with "repo sync --force-sync -d"

As far as I remember I kept only the downloads dir and wiped out anything else before doing the build from scratch.
I noticed that file meta-renesas-rcar-gen3.git/meta-rcar-gen3/conf /machine /m3ulcb.conf  from branch morty contains:
IMAGE_FSTYPES += " tar.bz2 ext4 cpio.gz"

Is this the expected configuration?
Best regards,
Leon

Hi,
I have rebuilt again AGL for rcar3 and the output image is in tar.xz format therefore I am closing the issue:
tmp/deploy/images/m3ulcb/agl-demo-platform-m3ulcb-20170817084549.rootfs.ext4
tmp/deploy/images/m3ulcb/agl-demo-platform-m3ulcb-20170817084549.rootfs.manifest
tmp/deploy/images/m3ulcb/agl-demo-platform-m3ulcb-20170817084549.rootfs.tar.xz
tmp/deploy/images/m3ulcb/agl-demo-platform-m3ulcb.ext4
tmp/deploy/images/m3ulcb/agl-demo-platform-m3ulcb.manifest
tmp/deploy/images/m3ulcb/agl-demo-platform-m3ulcb.tar.xz

Leon: AGL_DEFAULT_IMAGE_FSTYPES overrides it for all BSP's .
AGL_EXTRA_IMAGE_FSTYPES is meant to replace IMAGE_FSTYPES += "foo".


Customer sort incorrectly unlike other resources(Product, Order, etc)

http://stackoverflow.com/questions/33994862/shopify-api-customer-sort-incorrectly-unlike-other-resourcesproduct-order-etc

@ShayneP @joshubrown

Bump

Closing issue, this bug has been resolved. Sorting using order on Customers is now working correctly.


when service is many，create group of topology can‘t display all service and can’t scroll

Please answer these questions before submitting your issue.

Why do you submit this issue?
[ ] Question or discussion
[ ] Bug
[ ] Requirement
[ ] Feature or performance improvement

Question

What do you want to know?

Bug

Which version of SkyWalking, OS and JRE?
skywalking 7.0，os linux，jre jdk8

Which company or project?

What happen?
If possible, provide a way for reproducing the error. e.g. demo application, component version.

Requirement or improvement

Please describe about your requirements or improvement suggestions.

Fixed in 8.0 UI already.


Failed to build via bld -i mkfw -m ls1046ardb -b sd, to

$ flex-builder -i mkfw -m ls1043ardb
MACHINE: ls1043ardb
COMPONENT: atf
BOOTTYPE: sd
MACHINE: ls1043ardb
make: Entering directory '/home/quinn/layerscape'
make[1]: Entering directory '/home/quinn/layerscape/packages/firmware'
 Building ATF LSDK-21.08 for ls1043ardb
make[2]: Entering directory '/home/quinn/layerscape/components/firmware/atf'
  REALCLEAN
make[2]: Leaving directory '/home/quinn/layerscape/components/firmware/atf'
COMPONENT: optee_os
MACHINE: ls1043ardb
make[2]: Entering directory '/home/quinn/layerscape'
make[3]: Entering directory '/home/quinn/layerscape/packages/apps'

 Building optee_os ...
make[4]: Entering directory '/home/quinn/layerscape/components/apps/security/optee_os'
core/arch/arm/plat-ls/link.mk:7: warning: overriding recipe for target 'out/arm-plat-ls/core/tee-raw.bin'
core/arch/arm/kernel/link.mk:230: warning: ignoring old recipe for target 'out/arm-plat-ls/core/tee-raw.bin'
  CHK     out/arm-plat-ls/conf.mk
  CHK     out/arm-plat-ls/include/generated/conf.h
  GEN     out/arm-plat-ls/core/ldelf_hex.c

***
Can't find elftools module. Probably it is not installed on your system.
You can install this module with

$ apt install python3-pyelftools

if you are using Ubuntu. Or try to search for "pyelftools" or "elftools" in
your package manager if you are using some other distribution.
***

Traceback (most recent call last):
  File "scripts/gen_ldelf_hex.py", line 13, in <module>
    from elftools.elf.elffile import ELFFile
ModuleNotFoundError: No module named 'elftools'
make[4]: *** [mk/subdir.mk:181: out/arm-plat-ls/core/ldelf_hex.c] Error 1
make[4]: Leaving directory '/home/quinn/layerscape/components/apps/security/optee_os'
make[3]: *** [/home/quinn/layerscape/packages/apps/security/optee.mk:14: optee_os] Error 2
make[3]: Leaving directory '/home/quinn/layerscape/packages/apps'
make[2]: *** [Makefile:25: optee_os] Error 2
make[2]: Leaving directory '/home/quinn/layerscape'
make -s -j16 fip pbl PLAT=ls1043ardb BOOT_MODE=sd RCW=/home/quinn/layerscape/build/firmware/rcw/ls1043ardb/RR_FQPP_1455/rcw_1600_sdboot.bin BL33=/home/quinn/layerscape/build/firmware/u-boot/ls1043ardb/uboot_ls1043ardb_tfa.bin BL32=/home/quinn/layerscape/components/apps/security/optee_os/out/arm-plat-ls/core/tee_ls1043ardb.bin SPD=opteed
make[2]: Entering directory '/home/quinn/layerscape/components/firmware/atf'
Including services/spd/opteed/opteed.mk
board PAth = plat/nxp/soc-ls1043a/ls1043ardb
setting chssis
Makefile:1121: *** 'BL32=/home/quinn/layerscape/components/apps/security/optee_os/out/arm-plat-ls/core/tee_ls1043ardb.bin' was specified, but '/home/quinn/layerscape/components/apps/security/optee_os/out/arm-plat-ls/core/tee_ls1043ardb.bin' does not exist.  Stop.
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory '/home/quinn/layerscape/components/firmware/atf'
cp: cannot stat 'build/ls1043ardb/release/bl2_sd*.pbl': No such file or directory
make[1]: *** [atf.mk:11: atf] Error 1
make[1]: Leaving directory '/home/quinn/layerscape/packages/firmware'
make: *** [Makefile:19: atf] Error 2
make: Leaving directory '/home/quinn/layerscape'


Cannot assign to read only property 'mark' of sass

I'm using gulpjs/gulp#4.0. I've updated it this morning (after quite a while) and I started to get the following error while running my watch-styles task:
Error
[16:40:20] TypeError: Cannot assign to read only property 'mark' of sass
  at new Gaze (.../node_modules/gulp/node_modules/vinyl-fs/node_modules/glob-watcher/node_modules/gaze/lib/gaze.js:41:13)
  at gaze (.../node_modules/gulp/node_modules/vinyl-fs/node_modules/glob-watcher/node_modules/gaze/lib/gaze.js:86:10)
  at Object.module.exports [as watch] (.../node_modules/gulp/node_modules/vinyl-fs/node_modules/glob-watcher/index.js:24:17)
  at Gulp.watch (.../node_modules/gulp/index.js:26:14)
  at .../gulpfile.js:243:8
  at taskWrapper (.../node_modules/gulp/node_modules/undertaker/lib/set.js:17:15)
  at bound (domain.js:254:14)
  at runBound (domain.js:267:12)
  at asyncRunner (.../node_modules/gulp/node_modules/undertaker/node_modules/bach/node_modules/async-done/index.js:38:18)
  at process._tickDomainCallback (node.js:381:11)

gulpfile.js
gulp.task('watch:styles', function () {
  gulp.watch(paths.sass, 'sass');
  ...
});

gulp.task('sass', function () {
  return gulp.src(paths.sass)
  .pipe(plumber())
  .pipe(using({ prefix: 'After changed:' }))
  .pipe(sourcemaps.init())
  .pipe(sass())
  .pipe(changed(paths.dirs.build))
  .pipe(sourcemaps.write('.', { sourceRoot: '/' }))
  .pipe(gulp.dest(paths.dirs.build))
  .pipe(grep('**/*.css', { read: false, dot: true }))
  .pipe(browserSync.reload({stream:true}));
});

Need some help with this one.

We no longer support strings to the watch task. Please use gulp.parallel around your task name. There's a few issues, commits and the docs have been updated for this change. Sorry I can't link because I am answering from my phone.

Thank you. That worked!
gulp.task('watch:styles', function () {
  gulp.watch(paths.sass, gulp.parallel('sass'));
  ...
});

@ilianaza  :+1: Just got hit myself with this after an npm update. Thank you for showing the solution!

gulp.parallel isn't recognized when I try to use it.  Is this supported still?

@dschinkel if I gather correctly, gulp.parallel is only available from gulp 4.0.

thanks @sunilw

@dschinkel I think my statement before might have been incorrect:
I don't actually know if 'gulp watch' is unusable on the latest stable version. From the version number (4.0) I should actually assume that this is a stable version.
However, afaict, 4.0 is not the version that 'npm install' will install by default. Nor is it the version that is contained in the master branch of gulp's github repo.
I'm currently trying to figure out how to install 4.0. If I manage to do it, and you haven't figured it out before me, then I'll let you know if I was able to get gulp.parallel() to work.

This works to install gulp 4: npm install "gulpjs/gulp-cli#4.0"
I'm not sure if this is ideam, because 'gulp --version' returns "Local version 4.0.0-alpha.1".
So now we are working with an alpha version of gulp.

@sunilw no, you are using "edge" which is the latest and greatest.  There is a risk things will break, so we labelled it as version "4.0.0-alpha.1".  Please stop beating this old thread.


Test target from a Swift package cannot be added to a scheme

If I add a locally embedded Swift Package that comes with a unit test target, I'd like to be able to add the test target to the app scheme to be able to run all unit tests in one swoop. Like this:
packages:
  BarPackage:
    path: ../BarPackage
targets:
  FooApp:
    scheme:
      testTargets:
        - FooApp-Tests
        - BarPackageTests

Currently this results in an error:
Spec validation error: Target "FooApp" scheme has invalid test "BarPackageTests"

Maybe this could be an alternative to generating the scheme: https://github.com/yonaskolb/XcodeGen/issues/684