Automated cherry pick of #9925: Notify Optimization

Cherry pick of #9925 on release/3.5.
#9925: Notify Optimization

Codecov Report

Merging #9928 (9feefb2) into release/3.5 (6a15e02) will increase coverage by 11.92%.
The diff coverage is 1.85%.

@@               Coverage Diff                @@
##           release/3.5    #9928       +/-   ##
================================================
+ Coverage         5.98%   17.90%   +11.92%
================================================
  Files              796       85      -711
  Lines           125693     8923   -116770
================================================
- Hits              7522     1598     -5924
+ Misses          117504     7153   -110351
+ Partials           667      172      -495

Flag
Coverage Δ

aFlag
17.90% <1.85%> (+11.92%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/apigateway/handler/auth.go
0.00% <0.00%> (ø)

.../monitor/alerting/conditions/suggestrulereducer.go
0.00% <0.00%> (ø)

pkg/monitor/alerting/conditions/suggestquery.go
2.00% <2.00%> (ø)

pkg/util/seclib2/seclib.go
80.39% <0.00%> (-5.66%)
:arrow_down:

pkg/util/ansiblev2/session.go
0.00% <0.00%> (ø)

pkg/compute/models/snapshotpolicy.go

pkg/compute/guestdrivers/virtualization.go

pkg/hostman/system_service/host_deployer.go

pkg/cloudcommon/db/update.go

pkg/mcclient/options/k8s/fed_rolebinding.go

... and 591 more

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 53fd469...9feefb2. Read the comment docs.

Codecov Report

Merging #9928 (9feefb2) into release/3.5 (6a15e02) will increase coverage by 11.92%.
The diff coverage is 1.85%.

@@               Coverage Diff                @@
##           release/3.5    #9928       +/-   ##
================================================
+ Coverage         5.98%   17.90%   +11.92%
================================================
  Files              796       85      -711
  Lines           125693     8923   -116770
================================================
- Hits              7522     1598     -5924
+ Misses          117504     7153   -110351
+ Partials           667      172      -495

Flag
Coverage Δ

aFlag
17.90% <1.85%> (+11.92%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/apigateway/handler/auth.go
0.00% <0.00%> (ø)

.../monitor/alerting/conditions/suggestrulereducer.go
0.00% <0.00%> (ø)

pkg/monitor/alerting/conditions/suggestquery.go
2.00% <2.00%> (ø)

pkg/util/seclib2/seclib.go
80.39% <0.00%> (-5.66%)
:arrow_down:

pkg/util/ansiblev2/session.go
0.00% <0.00%> (ø)

pkg/compute/models/snapshotpolicy.go

pkg/compute/guestdrivers/virtualization.go

pkg/hostman/system_service/host_deployer.go

pkg/cloudcommon/db/update.go

pkg/mcclient/options/k8s/fed_rolebinding.go

... and 591 more

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 53fd469...9feefb2. Read the comment docs.


Escape shortcuts not working properly.

https://vimeo.com/manage/videos/914570721/9e51eed7b5?extension_recording=true
Ref: https://github.com/bigbinary/neeto-molecules/issues/1067

@AbhayVAshokan _a


Checking hook.params.headers.authorization

Steps to reproduce
When authenticating with rest I check if the client is sending his jwt, and as such I check
hook.params.headers.authorization
When authenticating with socket.io I tried to do the same.
Expected behavior
checking hook.params.headers.authorization would have the jwt.
Actual behavior
hook.params.headers.authorization is undefined, the jwt is under hook.params.headers.Authorization note the A of authorization.
I modified my code to make it work but i think it should be the same for all cases that have the authentication
System configuration
feathers --version
2.1.1

This is the correct behavior.  Authentication over socket.io and primus doesn't happen with headers.  It works by sending messages to authenticate.  You can see the code here: https://github.com/feathersjs/feathers-authentication/blob/master/src/socket/handler.js#L150.
Let me know if you're interested in making header support work.

https://github.com/feathersjs/feathers-authentication/blob/master/src/socket/handler.js#L150
This repo is unavailable now, is there any other repo that i can refer.


camel-rest-openapi - Generated produces string is missing media types

Bug description
I found a bug in camel-rest-openapi.
The following code exists in RestOpenApiProcessor.java in 4.8.0 and 4.8.1:
// the operation may have specific information what it can produce
if (o.getResponses() != null) {
    for (var a : o.getResponses().values()) {
        Content c = a.getContent();
        if (c != null) {
            produces = c.keySet().stream().sorted().collect(Collectors.joining(","));
        }
    }
}

In main,  the code seems to have been refactored into OpenApiUtils.java:
public String getProduces(Operation operation) {
    // the operation may have specific information what it can produce
    if (operation.getResponses() != null) {
        for (var apiResponse : operation.getResponses().values()) {
            Content content = apiResponse.getContent();
            if (content != null) {
                return content.keySet().stream().sorted().collect(Collectors.joining(","));
            }
        }
    }
    return null;
}

In my case, I have a structure which looks like this:
operation
   ...
   responses
      {0}
         key = "200"
         value
            ...
            content
               {0}
                  key = "application/json"
                  value = ...
      {1}
         key = "400"
         value
            ...
            content
               {0}
                  key = "application/problem+json"
                  value = ...
      {2}
         key = "404"
         value
            ...
            content
               {0}
                  key = "application/problem+json"
                  value = ...
      ...

When running the code with 4.8.0, produces is set to application/problem+json. It should be set to application/json,application/problem+json instead.
The code from main also generates wrong result.

https://issues.apache.org/jira/browse/CAMEL-21430


Resolved bug in kMaxValue in SerializationTest for toml_fuzzer

What does this change do?
Fixes a super simple logic msitake in the harness, where the kMaxValue was set to 1 less than the true max- preventing one branch of the switch from ever being exercised.
Is it related to an exisiting bug report or feature request?
No
Pre-merge checklist

[X] I've read CONTRIBUTING.md
[ ] I've rebased my changes against the current HEAD of origin/master (if necessary)
[ ] I've added new test cases to verify my change
[ ] I've regenerated toml.hpp (how-to)
[ ] I've updated any affected documentation
[X] I've rebuilt and run the tests with at least one of:

[X] Clang 8 or higher
[ ] GCC 8 or higher
[ ] MSVC 19.20 (Visual Studio 2019) or higher

[X] I've added my name to the list of contributors in README.md

Thanks :)


Structural improvement & more

It's a bad practice to include build files in version control, I could submit a PR to clean it up a bit and update the ,gitignore if you're up for it;
Also optimization process is quite slow, would be nice to utilize GPU and with increased batch size of the training to speed it up. I believe this could reduce iteration (design) time to couple of seconds. Now even for toy datasets it takes tens of minutes to optimize. Would be up for contributing to that also;
Another point is measurements arriving at different rates, would love to hear your opinion about supporting real world use cases of the package. Now it kinda works with simply assuming that all sensor data are coming in at the same rate but in reality it's never the case...
Awesome work by the way : )

Thank you for your comments!
PR submissions are welcome.
GPU
Your contribution for GPU support will also be much appreciated.
At the time I trained on 1500 trajectories in a low-dimensional doppler radar problem. The training took just a few minutes (not tens of minutes...), and I could parallelize different variants on my CPU cores, so there was not much room for acceleration. On other scenarios, though, GPU may indeed be more efficient.
Irregular time-steps

The KF works in constant time-steps. One way around is having a basic time-step dt, and expressing longer intervals as integer multiplications K*dt. Then, you can call predict() K times before calling the update() step.
For high irregularities, I would consider the approach of neural ODEs: by predicting the derivative dx/dt instead of the next state x itself, you get much more flexibility with the time-steps. Such neural ODE methods may be further stabilized via a piecewise-linear implementation, as we discuss in this work:
https://research.nvidia.com/labs/par/publication/nesde.html

You are also welcome to pm me if you like to discuss specific use-cases.


Could not find a backend to open ./logs/llff/fern/render_video_fine_last/video.rgb.mp4`` with iomode wI`.

thanks for your great jobs!
but i meet some problem when i run "python run.py --config=configs/llff/fern.py --stop_at=20000 --render_video --i_weights=10000"

Actually, i have install the imageio==2.22.2 and i could not found the mp4 under the folder "render_video_fine_last" .

Hello! Thanks for your interests.
I guess the imageio[ffmpeg] is different from imageio. Have you tried the “pip install imageio[ffmpeg]” instruction?

THX！ the problem solved


Connect shell scripts

For example:

collect container, stop all containers and calculare docker images
info pip packages and update pip packages
network and osx wifi strength

pip scripts are have been connected: https://github.com/mdrocan/shell-scripts/commit/19379bf1afe38980856be7924774add821c19c19

Network and wifi strength for different purposes. Will keep them separated for now.

Done for now. Further improvements with separate tickets.


facebook pixel fired outside concerned views

Hi,
first at all, thanks for your great work !
I have installed the tracker and I have few comments.
When specified in the controller method :
tracker do |t|
t.facebook_pixel :track, { type: 'ViewContent', options: { p: 'my_way' } }
end
the facebook pixel is correctly fired ..
but there is another one pixel fired too , PageView, altough I have modifyed the facebook_pixel template and delete the js track call in the template.
I still have fbq('track',"PageView"); at the end of the script.
how to avoid having pageview fb pixel on pages whereas nothing about it in the controller method ?
Regards,

Hey! Thanks for the comment :)
So the pixel is indeed inserted always.
We have some functionality for google that enables you to check for a proc that helps you decide where to show the script:

https://github.com/railslove/rack-tracker/blob/master/lib/rack/tracker/google_analytics/google_analytics.rb#L56
https://github.com/railslove/rack-tracker/blob/master/lib/rack/tracker/google_analytics/template/google_analytics.erb#L2

We could come up with the same for facebook,
or something similar which would be more usable for all tracking handlers...

Hi !
thanks for your quick reply
I will take a look on the solution, thanks
and thanks again for your great work ! :+1:
Keep on ! :)

@rubyrailsninja did you get this to work?

I finally keep all fired pixels, simple et easy solution :D

ok, that means it works? can we close this issue?

Yes, I close it :)


Hashing Example does not get compiled with ArmCC in Ubuntu

hasnain@ubuntu:~/Repos/OOB_Repo/mbedtls-examples/hashing$ yt clean
hasnain@ubuntu:~/Repos/OOB_Repo/mbedtls-examples/hashing$ yt target frdm-k64-armcc
hasnain@ubuntu:~/Repos/OOB_Repo/mbedtls-examples/hashing$ yt build
info: get versions for frdm-k64-armcc
error: could not install target frdm-k64-armcc at * for frdm-k64-armcc
error: frdm-k64-armcc does not exist in the targets registry. Check that the name is correct, and that it has been published.
hasnain@ubuntu:~/Repos/OOB_Repo/mbedtls-examples/hashing$

see #246


Roll Flutter from fce3cee7763c to 2bc539a896a0 (5 revisions)

https://github.com/flutter/flutter/compare/fce3cee7763c...2bc539a896a0
2022-04-21<EMAIL_ADDRESS>Marks Mac_ios native_ui_tests_ios to be unflaky (flutter/flutter#102225)
2022-04-21<EMAIL_ADDRESS>Marks Mac_ios flutter_view_ios__start_up to be unflaky (flutter/flutter#102224)
2022-04-21<EMAIL_ADDRESS>Marks Mac_android entrypoint_dart_registrant to be unflaky (flutter/flutter#102223)
2022-04-20<EMAIL_ADDRESS>The sample code used within the comments in textContaining is wrong (flutter/flutter#100860)
2022-04-20<EMAIL_ADDRESS>Increased StandardMethodCodec's WriteBuffer start capacity (flutter/flutter#101860)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-plugins
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Plugins: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


Cannot attach more than 1MB

Currently there is a limit 1MB for the attachment size which limits the type of attachments we can make. Would be great, at least for the paying users to be able to attach more: 10MB would be great, 100MB even better.

The attachment file size upload limit is now 3MB. We can increase it further if any customers ask for it.
After we release free accounts, we can have separate limits depending on subscription.

Let's see if people complain and we'll change it if needed.


Add environment variable to overwrite the cuda path

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
We add a new environment variable MARQO_CUDA_PATH to overwrite the cuda path as this path varies on different platforms (e.g., ec2, gcp)

What is the current behavior? (You can also link to an open issue here)
it is hardcoded to /usr/local/cuda

What is the new behavior (if this is a feature change)?
if MARQO_CUDA_PATH is provided, we use the provided value.
If not provided, we use default value /usr/local/cuda

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
no

Have unit tests been run against this PR? (Has there also been any additional testing?)
no

Related Python client changes (link commit/PR here)
no

Related documentation changes (link commit/PR here)
no

Other information:
no

Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines
[x] Tests for the changes have been added (for bug fixes/features)
[x] Docs have been added / updated (for bug fixes / features)

How are we testing this?

I will have an API test to do this.


Fix the elements position and margins on mobile view

I have applied new design here #30. So, closing this as irrelevant


Theme isn't applied

First at all, good job! It's look really well.
I'm trying to apply the theme in a MacOS and I can't. I didn't receive any error message, I just open Slack after apply the theme and it isn't have any change.
Is there any logs folder where I can check for error messages?
Thanks!

Having the same issue this morning. Tried removing and re-adding, but no luck.

oops i removed the styles by mistake....................... fixing 🤦♂


Owncloud from catalog get stuck on activating

Rancher Version: 1.0.1
Docker Version: 1.11.0
OS: Debian 8 Jessie
Steps to Reproduce: catalog>owncloud>activate
Results: Activating... (forever)
Expected:Active
On rancher webUI I succesfully activate Wordpress and Janitor from catalog, but owncloud stuck on activating with no errors. This is my second attempt to use Rancher, the first one it happened that owncloud activated correctly but wordpress get stuck on activating. This from catalog.
I could launch wordpress containers from docker-compose on command line, they are running but on rancher webUI they allways keep on activating

Any questions regarding community catalog entries should be asked in the rancher/community-catalog repository to help get support from the community.
A rancher tip, if a service is stuck in activating, you can click on the service (in your case owncloud) that is stuck and see the containers that are trying to spin up. You can click on one of them and see why it's failing. We provide messages on what is going on during the deployment and if the deployment fails, it will enter an errored state and you can click on that container to see why it is in error state.


Unifi websockets tests for Starlite

Move the tests for the websockets integration for Starlite to the new /tests/websocket

Description
Websockets tests for all integrations are unified under /tests/websockets and parametrized
so that the tests can be written once.  Starlite tests were still in their old location.
In addition, fixed some cases in the integration where "close" messages didn't contain a "reason", and
some other cleanup.
Types of Changes

[ ] Core
[ ] Bugfix
[ ] New feature
[x] Enhancement/optimization
[ ] Documentation

Issues Fixed or Closed by This PR
Checklist

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] I have tested the changes and verified that they work and don't break anything (as well as I can manage).

There is no RELEASE.md, since this is testsing only.

Hi, thanks for contributing to Strawberry 🍓!
We noticed that this PR is missing a RELEASE.md file. We use that to automatically do releases here on GitHub and, most importantly, to PyPI!
So as soon as this PR is merged, a release will be made 🚀.
Here's an example of RELEASE.md:
Release type: patch

Description of the changes, ideally with some examples, if adding a new feature.

Release type can be one of patch, minor or major. We use semver, so make sure to pick the appropriate type. If in doubt feel free to ask :)
Here's the tweet text:
🆕 Release (next) is out! Thanks to @kristjanvalur for the PR 👏

Get it here 👉 https://github.com/strawberry-graphql/strawberry/releases/tag/(next)

Also just learned that Starlite is now called Litestar lol

Yes, it just happened.  Someone must have complained about naming confusion.

FYI, I just submitted a PR to the django/channels to update the websockets support to ASGI spec 2.3:  https://github.com/django/channels/pull/2002


raft leader hangs log replication until next heart beat

raft leader does not forward logs until next heartbeat.

Is there a test to reproduce this issue?
I noticed it too days before and haven't yet got time to fully dig into it...

first found in https://github.com/datafuselabs/databend/issues/3474

the pr has been merged into openraft,but seens that has_more_log and tokio::select has the same effect.

Hmm... not exactly. I was wrong about it last time we discuss it:

line-14 is required to forward every log even when there is no incoming event about new logs.
line-13 is required to shut the replication down at once even when there are still a lot of logs that need to be sent.

    1 pub async fn line_rate_loop(&mut self) -> Result<(), ReplicationError> {
    2     loop {
    3         loop {
    4             let res = self.send_append_entries().await;
    5
    6             if let Err(err) = res {...}
    7
    8             if self.matched.index == self.max_possible_matched_index {
    9                 break;
   10             }
   11         }
   12
   13         self.try_drain_raft_rx().await?;
   14         if self.has_more_log() {
   15             continue;
   16         }
   17
   18         tokio::select! {
   19             _ = self.heartbeat.tick() => { continue }
   20
   21             event_span = self.repl_rx.recv() => {
   22                 match event_span {
   23                     Some((event, _span)) => {
   24                         self.process_raft_event(event)?;
   25                         self.try_drain_raft_rx().await?;
   26                     },
   27                     None => {
   28                         return Err(ReplicationError::Closed);
   29                     },
   30                 }
   31             }
   32         }
   33     }
   34 }


Bug report: Docker health issue

Describe the bug
After docker health state transitions from starting it moves to unhealthy
To Reproduce
Steps to reproduce the behavior:
1: Start the container
2: Wait ~3 mins
Expected behavior
Docker state transitions to healthy
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Solved by #10


Missing pets Not showing

Did You Remove The missing pets Feature? Or is it a bug

Looks like a bug to me

Thank You For Fixing This Issue. :)


Fixed inspect request using Preamble approach

On main

On branch

cc @ioanaif
Continuing our discussion from Friday. I have the following
After talking to Johan, I got to know about the following
i) The execute request and the inspect request are decoupled but then at the same time as use shift + enter to trigger both of them, the inspect request for a client like JupyterLab would be processed through an execution request only
ii) But then what role does inspect_request_impl play ? It comes into picture when other client like a jupyter console is used .Hence we have established that we need an inspection check separately and also one through the execution request.
iii) But should we use the inspect function in the execute_request_impl body ? After discussing with Johan I realized that a better method to do this would be using preambles. This helps us overall (also when we get to magics in the near future) .
So we have the following
A cell with a behavior defined in the preamble manager which depends on a certain pattern. For example:

if a cell begins with %% or %, it is a magic cell or magic line,
if a cell begins with !, it is a shell command,
if a cell begins with ?, it is an introspection.

Is there a way to add tests to this PR?
cc: @JohanMabille

@anutosh491, could you do that?


Import from JSR

This PR:

Updates @std/encoding's version tag.
JSR supports 0.224.0 as tag to be backward compatible but new tag is started from 1.0.0 and the current one is 1.0.1.

Imports packages from JSR in tests.

Imports packages from JSR in examples.

See

https://jsr.io/@std/encoding
https://jsr.io/@std/testing

Thank you @emrahcom . What are the advantages and disadvantaes here?

The standard package will be updated in JSR. https://deno.land/std will not be updated anymore.
See this post for more details.
And tests will be more acqurate if they use the same packages.

I will not merge it, because I want the deps to be available inside the browser.


[SECURITY] Privilege escalation: Unquoted call to "crlfsuite-script.py"

Please see the readme of this project: https://github.com/ItsIgnacioPortal/Improper-Quotes-Monitor
TL;DR: CRLFsuite is vulnerable to privilege escalation because it tries to access a file without quotation marks. More specifically, it tries to run:
C:\Program Files\Python39\python.exe C:\Program Files\Python39\Scripts\crlfsuite-script.py --help

but because it's not quoted properly, it actually runs:
C:\Program.exe Files\Python39\python.exe C:\Program Files\Python39\Scripts\crlfsuite-script.py --help

This vulnerability isn't super serious because crlfsuite doesn't need to be ran as Administrator at any point, and no "default" Windows configuration makes this exploitable.

Hi @ItsIgnacioPortal,
Thanks for reporting this security issue, we are currently in the process of fixing it. Once it's fixed, we will let you know.


IEEE 15.4: cc1200 support

Finally had time to test this driver on 868, 920 and 434 MHz and it looks ok.
As this chip is working on a lower level than usual 15.4 chips, there is no hw filtering for pan id, extended address nor ack handling.
These parts will have to be done by the host, I'll add these features on another PR, as this does not prevent 15.4 from working on this chip. (it's just unable to filter out and handle acks in an optimal way).

Note: only the 2 last patches are part of that PR. All the other are in this PR #4095


Php solution doesn't work

When I do your step-by-step tutorial to set up a subscription with PHP as a server. I only have error messages that appear. I used the method with the CLI, it doesn't work. Same thing by doing it manually. I put a screenshot so that you can see the error messages.
Can you help me because my project needs this solution?
Regards,

Could you tell me your environment information?
PHP version:
Web Server type: Apache / Nginx / other
Thanks!

I created pull request #653 to fix this issue. The sample was written with slim v3 and phpdotenv v3, but the auto updater bot upgraded the project to their latest versions in the repo, which introduced breaking changes.  You can change 2 lines in your composer.json file
composer.json
"slim/slim": ">=3.12 <4.0",
"vlucas/phpdotenv": ">=3.4 <4.0"


Seeking help to get porcupine work on Mac OS 10.13

NOT AN ISSUE
Hello,
First of all, kudos on the great application you have built. This is the first simple yet powerful library I found for keyword detection.
I tested out this application on Mac OS 10.15.* using a pip install and it works just as it should. I replicated the same on my iMac running Mac OS 10.13.* where I keep getting OSError from ctypes module. I figured this isn't an issue with porcupine itself.
I tried using install_name_tool to change the reference of the .dylib but no luck.
I followed some earlier issues and found one of the devs have actually used this on Mac OS 10.13.*
I'm curious how I can install this module on Mac OS High Sierra. Can you please let me know if that can be done with an alternate way of installation or an older version would help.
https://github.com/Picovoice/Porcupine/issues/39
Traceback:
iMac:~ vicky$ porcupine_demo_mic --keywords alexa
Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/3.8/bin/porcupine_demo_mic", line 8, in <module>
    sys.exit(main())
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/pvporcupinedemo/porcupine_demo_mic.py", line 201, in main
    PorcupineDemo(
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/pvporcupinedemo/porcupine_demo_mic.py", line 84, in run
    porcupine = pvporcupine.create(
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/pvporcupine/__init__.py", line 64, in create
    return Porcupine(
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/pvporcupine/porcupine.py", line 60, in __init__
    library = cdll.LoadLibrary(library_path)
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/ctypes/__init__.py", line 451, in LoadLibrary
    return self._dlltype(name)
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/ctypes/__init__.py", line 373, in __init__
    self._handle = _dlopen(self._name, mode)
OSError: dlopen(/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/pvporcupine/lib/mac/x86_64/libpv_porcupine.dylib, 6): Symbol not found: ____chkstk_darwin
  Referenced from: /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/pvporcupine/lib/mac/x86_64/libpv_porcupine.dylib (which was built for Mac OS X 10.15)
  Expected in: /usr/lib/libSystem.B.dylib
 in /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/pvporcupine/lib/mac/x86_64/libpv_porcupine.dylib

Thanks! we will address this in the coming weeks. The .dylib is built to run on 10.15 and later. just curious, why not update to the latest macOS?

Thanks for the response. The iMac is a 2011 model running High Sierra. It's hardware doesn't support an upgrade 😞

hey - unfortunately this doesn't seem to be making it to our immediate roadmap. I keep this in mind for the future if we can make dev time.

@kenarsa Thanks for the intimation. I have upgraded my Mac and got it working fine but still will keep an eye around, I'm curious.


Make easier to find PicoZed part number

Per questioning from @elsevers

Add PicoZed to AMDC BOM on AMDC-Hardware REVxxxx folders
Add link to PicoZed article in the Obtaining Hardware page
Add link to Obtaining Hardware page in the Onboarding page

Per questioning from elsevers

Add PicoZed to AMDC BOM on AMDC-Hardware REVxxxx folders

Addressed by Divya in AMDC-Hardware 3371c5a

Add link to PicoZed article in the Obtaining Hardware page
Add link to Obtaining Hardware page in the Onboarding page

Addessed by me in docs.amdc.dev 608e801


New Rule: requireVarDeclFirst

Enforce variable declaration at the top of declaring scope
Fixes #99

Could you add some comments, like for while for loops, or why you need to break/continue, etc.
Need some else to give "LGTM" since this logic is not obvious like for the other rules.

@zxqfox @mrjoelkemp @mikesherov @hzoo i would like to merge this, so it would go in to 2.0, but need a at least one "LGTM" from you

@markelog sorry could not look into the comments yet. I will try to put them in before you start your monday. Although while working on this I have to say the rule was more complex then most of what I have work on so far.

@oredi which is makes so cool :-)

Great work here @oredi! Excited for this rule. However, as my comments suggest, I worry about the maintenance of the current state of the code. Any improvements to stating the high level algorithm through function usage is a big win.
Feel free to ping me for clarification or when the edits are made. Thanks for the great effort here.

@markelog  and @mrjoelkemp, I will need some time to look into the changes. I have found some bugs today as well. I will update the PR again when I can get the fixes in and hopefully make the implementation clearer

@markelog @mrjoelkemp
I restructured the tests and code, hopefully this version is clearer. Please let me know if further edits are required

hm, it will fail for the case like this -
function tst(node) {
    var array, // array of class names
        ncn = node.className;
}

When it is ready, would like to add to presets -
Crockford - http://javascript.crockford.com/code.html#variable declarations
"The var statement should be the first statement in the function body."
Wikimedia - https://www.mediawiki.org/wiki/Manual:Coding_conventions/JavaScript#Declarations
"Variables must be declared before use and should be the first statement of the function body."
WordPess - https://make.wordpress.org/core/handbook/best-practices/coding-standards/javascript/#declaring-variables-with-var
"Each function should begin with a single comma-delimited var statement that declares any local variables necessary."
/cc @Krinkle, @paulschreiber

Happy to see this rule being implemented. I'll try it out soon.
I'd like to see a test case for (ignoring) the Directive Prologue (i.e., "use strict" directives); see 14.1.1.

Also, I think this rule should be called requireVariableDeclarationFirst, as "declaration" is spelled correctly in 5 other rules, and requireMultipleVarDecl should be renamed to requireMultipleVariableDeclarations with the old name as an obsolete alias.

@markelog Thanks I missed that scenario, I have put in the fix with the update to the tests.
@jacksonrayhamilton Support for this has been added to the latest commit, now the rule allows the placement of 'use strict' as the first statement of the Program, Function Declaration or Function Expression scope. I am keeping this as a separated commit as it is a special condition. If everyone agrees I combine them into a single commit.
I am keeping the name for now but if the others agree with the name change I will do that.

Great job here @oredi! The code reads much better now; hopefully you agree. Thanks so much for making the edits.

I predict that we will receive a ticket that would ask to allow case like this -
// Example
var i;

Thank you @oredi, nicely done

@markelog  Thanks and I believe the following code will not cause any issue as the code handles that condition as well. Btw shall I put in another PR to add the rule to the presets for Crockford, Wikimedia and WordPess. And if yes do I need to create an issue for it or just the PR will do?
// Example
var i;
@mrjoelkemp Thanks. And the truth is I like this way of coding method. It literally allows me to KISS the code. :)

@markelog  sorry looks like you added the presets. Thanks


Releasing TinyLlama T1.5

i wanted to know when will TinyLlama 1.5T checkpoint will be released in README.md it's says
2023-10-31 and (Today (November 4, 2023) is 4 days after October 31, 2023)

https://github.com/jzhang38/TinyLlama/issues/81

I hope that nothing untoward happened again.


jsPDF sometimes only creates .part file on Firefox for Android

I've got FF 37.0.2 running on Android 4.4.4 (Nexus 4, CM11).
I tried to run the basic example on my phone and it seems to work fine most of the time. But from time to time I only get a .pdf.part file with a file name like "5+Xni03k" that is exactly the same size as the pdf file that gets written when everything works. When I rename the file and get rid of the ".part"-part I can open the pdf without a problem.
I think FF sometimes doesn't notice file creation is done and doesn't rename the .part file to test.pdf.
I'm not sure if this is a bug in FF or jsPDF, though.

Not reproducable


ElementalUI

Give it a go
Demos ready:

Buttons
Forms
All of the components are done, all the demos are done as well (they show the same stuff as the elemental website)

fantastic contribution there, @rleibman! I'll just merge this now and hope that things work - can't wait to experiment a bit with it


⚠ Processors has degraded performance

In 44da01b, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 99 ms

Resolved: Processors performance has improved in c2ca3b0.


Loadbalancer listener module

slightly reworked loadbalancer.py
added integration test
added listener module
added listener info module

@gtema somehow in zuul always failing TASK [loadbalancer : Create Router for ELB], can you look at that? In 447 integration test passed

regate

regate

regate


make api_version required

I think the current policy will lead to breakage: #257
The current policy, as far as I can tell, kind of implies that we need perfect backwards compatibility. Or to coordinate multi-year changes across multiple projects, which sounds...really hard
I'd suggest just making api_version a required argument. This just simplifies everything

no objections in today's call so let's do this


Adding orderby to Table 'not grouped by' and fixing metrics ordering

Also did a bit of refactoring along the way.

Coverage decreased (-0.2%) to 81.248% when pulling 002d504d37cdefd0e94fa3521a648a17f0d92deb on mistercrunch:orderby into 141dc12e445f5a1bbaa720b988b135b01d329789 on airbnb:master.

Coverage decreased (-0.2%) to 81.248% when pulling 13c790ee55e284da7b2ce4a5f76845c01763d1f6 on mistercrunch:orderby into 141dc12e445f5a1bbaa720b988b135b01d329789 on airbnb:master.


Fix JS Compilation Conflict with Reanimated Babel Plugin

Summary
This PR addresses a common JavaScript compilation issue caused by the Reanimated Babel plugin. The plugin converts worklet functions to arrow functions, which disrupts function hoisting and leads to runtime errors.
Changes
Manually converted all affected worklet functions to arrow functions to ensure compatibility with the Reanimated Babel plugin.

#80


Is there a changelog?

What are the (breaking) changes between 0.9.9 and 0.10.0 ?

There shouldbn't be any, you could check the changes at commits history for now. A new feature will the that matches are sortable, other than there is just a few bug fixes a refactor splitting source code to multiple files but final dist files is the same.
Unfortunately we don't have s standard way to define a changelog yet but suggestions are welcome

+1
Without release notes we can't safely upgrade to the version. This should be one of the top priorities for this repo.

through trial and error, i'm afraid.

+1

0.13.0 CHANGELOG.md file created
Thanks for this.


Python 3 - Solution error: Function "url_to_attrs_dict" expects a string or a dict with key "url".

#Fix bootstrap.py
Please correct the file!
def get_bootstrap_setting(setting, default=None):
"""
Read a setting
"""
value = BOOTSTRAP3.get(setting, default)
return value if value else BOOTSTRAP3_DEFAULTS.get(setting)

Thanks for reporting this. I cannot reproduce any error that looks like this. Can you provide a failing test?


[Enum Request] Table: Sales Header Archive Field: Shipping Advice

Please add the Enum "Sales Header Shipping Advice" of the Sales Header also for the relating field "Shipping advice" in the archive. Currently it is still an option.
Thanks :).

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


1.3.0 install fails "Special device /dev/sda4 does not exist"

Describe the bug
1.3.0 install fails . I tried install in 4 different servers .

To Reproduce
Steps to reproduce the behavior:
Install using dell idrac virtual console mounting harvester 1.3.0 iso , go through install , it fails toward the end.
Environment

Underlying Infrastructure: Baremetal  Dell PowerEdge R730

Additional context
Add any other context about the problem here.

Hi @kingnarmer, could you also check the dmesg output?
It seems the format did not succeed.

@Vicente-Cheng attached is dmesg output .
dmesg.log


Dockerfile ENV PATH

This line in the Dockerfile:
https://github.com/gibiansky/IHaskell/blob/60fceecc7edb76645d158dce1c801cfc59fb6d70/Dockerfile#L59
Results in this PATH in the container. I think these bash command substitution arguments don't get evaluated in PATH, so this will not have the intended effect on the PATH.
I don't know of any good way to set a Dockerfile ENV with a command from the container context, so I'm not sure what should be done instead. The notebook container still seems to work, though, even with this PATH.
jovyan@dbd2de6954af:~$ echo $PATH | tr ':' '\n'
/opt/conda/bin
$(stack path --local-install-root)/bin
$(stack path --snapshot-install-root)/bin
$(stack path --compiler-bin)
/home/jovyan/.local/bin
/opt/conda/bin
/usr/local/sbin
/usr/local/bin
/usr/sbin
/usr/bin
/sbin
/bin

Thanks for pointing this out! This is definitely different from what I expected, and it's especially strange that it continues to work. As you can probably tell, my understanding of Docker is fairly limited. I'll leave this open until I (or someone else) can fix this.

I tried:

surrounding the value in double quotes
replacing the parentheses with curly braces

but neither of those approaches worked.

Closing as this doesn't appear to be an issue in practice.


[Tooltip] location

When the zoom is set to 1 the Tooltip appears in the proper location.  However if you change the css  zoom: ,8  the tooltip  doesn't appear near the element.   Any Suggestions?

Closing due to inactivity.


Remove mention of heuristic planner from 19.2 docs

Fixes #5823.

This change is

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/9106af6d62b9db3096f39b5bde0723579ec48226/
Edited pages:

v19.2/cost-based-optimizer.md
v19.2/explain.md
v19.2/show-trace.md

@RaduBerinde pinging you since AIUI this is an area you are knowledgeable about.  Please feel free to redirect as needed.

@ericharmeling I'm merging this now since it's small, but pinging you as a content FYI

And thanks Radu!


Update aws-java-sdk-kinesis, ... to 1.11.793

Updates

com.amazonaws:aws-java-sdk-kinesis
com.amazonaws:aws-java-sdk-s3
com.amazonaws:aws-java-sdk-sqs

from 1.11.772 to 1.11.793.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.amazonaws" } ]

labels: library-update, semver-patch

Codecov Report

Merging #347 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #347   +/-   ##
=======================================
  Coverage   46.26%   46.26%
=======================================
  Files          24       24
  Lines         281      281
=======================================
  Hits          130      130
  Misses        151      151

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 a12252d...5dbe6b0. Read the comment docs.


Add support for Swift 2.2 and Xcode 7.3

Thanks for the PR! I think we have this adequately covered by #141, however.


Android target publishing/archiving

We need a doc on publishing Android apps using the CLI. The process is doc'd at https://github.com/dotnet/maui/issues/4377, and it links into some Xamarin content on signing the app package that will need pulling into the new doc.
The Xamarin docs on publishing Android apps can be found at: https://docs.microsoft.com/xamarin/android/deploy-test/publishing/. There's no requirement to pull that content into the new doc. I've just included the link in case there's any useful intro content there you want to reuse. Note: the Xamarin docs mention publishing to an APK. However, Google Play store no longer accepts APKs, and so the package format must be AAB.
At the end of the doc, link to Google's doc on how to upload the AAB to the Play store. You could also link to any other Google docs on package requirements etc.
The doc should go in a new node at the bottom of the TOC that's called something like Deployment/Publishing/Packaging. Maybe Publishing, as it is the dotnet publish command.

Will need to follow up with more docs around:

App sizing
Zipalign
MSBuild reference material
Baking the app into a ROM image
Using a central keystore


Odd idea for arcane workbench

Pretty much everything has NEI/JEI compatibility... but why not give the arcane workbench thaumonomicon  interaction?  As in, as you determine recipes, anytime you open the arcane table, there's a recipe-list on the side?   Maybe a rolo-thauminomicodex where you can add on non-Thaumcraft recipes to allow for quick crafting.
It'd just be an ease of use thing as opposed to opening worktable, forgetting what you need, closing worktable, opening thaumonomicon, finding the item, closing thaumonomicon, opening worktable again.  Doesn't happen too horribly often but when you're crafting stuff with multiple steps, it can be a bother.

Maybe a little scroll off to the side you can click to show a list of all crafting recipes

This issue was moved to Azanor/thaumcraft-suggestions#174


The switch from synchronous I2C writes to queued asynchronous I2C writes

In the past, raspi-io used synchronous methods for I2C writes. For example, writeSync here and writeByteSync here. Today, I2C write are queued and written using asynchronous methods. For example, write here and writeByte here.
On the other hand, Johnny-Five has I2C code that implicitly assumes that I2C writes are synchronous. As an example, to initialize an I2C LCD display, Johnny-Five runs this blocking synchronous code. The calls to sleep in this blocking code are important and essential. In the past, when raspi-io used synchronous methods for I2C writes this code was highly likely to have functioned correctly. Today, raspi-io queues I2C commands and uses asynchronous methods for I2C writes and the code is far less likely to function correctly. Today, sleeps can complete before the asynchronous writes that they are waiting for to complete have actually completed.
I think today’s queued asynchronous I2C writes in raspi-io are the cause of this Johnny-Five issue.

Hrmmm...that’s unfortunate. Switching to this async format was one of the big ways I fixed high CPU usage, so I really don’t want to revert it. I’m traveling right now, but I’ll think on this.
My current thought is to add an i2cSleep method to the IO plugin protocol and use that if available, otherwise use standard sleep. In J5-IO, this would be another queued operation.
As a side note, formats is all implicit async code like this since it has to communicate over the wire. I’d guess the processing power of a computer vs RPi masks the fact that this is happening due to lower latency and better predictability (context switches are way faster, etc)

Switching to this async format was one of the big ways I fixed high CPU usage, so I really don’t want to revert it.

I can understand not wanting to revert it and it's entirely up to you how to proceed. That being said, I don't see how changing to async alone can decrease CPU usage. If anything, it should increase it slightly as it results in more context switching. CPU usage can be quite high with the current version of raspi-io. For example, the last time I checked, running this bme280 program results in about 60% CPU usage on a Pi 3.

My current thought is to add an i2cSleep method to the IO plugin protocol and use that if available

Implementing such a change would require a considerable amount of time.

That being said, I don't see how changing to async alone can decrease CPU usage. If anything, it should increase it slightly as it results in more context switching. CPU usage can be quite high with the current version of raspi-io. For example, the last time I checked, running this bme280 program results in about 60% CPU usage on a Pi 3.

60% is a major improvement over the 80-100% Raspi IO had at idle in version 9 😉
Using synchronous calls for I/O in Node.js is antithetical to how Node.js itself works, because we're intentionally blocking the event loop. TBH if the performance cost of context switches is the bottleneck in someone's app, then they shouldn't be using Node.js at all and should be using C++ instead, and Raspi IO is the wrong library for them. That's not my use case and I don't intend to optimize for it.

Implementing such a change would require a considerable amount of time.

Doesn't seem like it to me. We look for the instances of sleep(n) used for I2C code (perhaps on a case by case basis starting with LCD) and replace it with:
if (io.plugin.i2cSleep) {
  io.plugin.i2cSleep(n);
} else {
  sleep(n);
}

It's really just a search and replace, and I'd rather spend my time doing that than reverting this code.
As another side note: the amount of blocking code in Johnny-Five is itself a problem, and as long as that code is around, Johnny-Five will never be a best-in-class Node.js library. To be super frank: the download numbers for Johnny-Five have been dropping steadily for some time, and if we don't modernize the framework to make it relevant again, then all this discussion is moot anyways IMO.

60% is a major improvement over the 80-100% Raspi IO had at idle in version 9 :wink:

True :smile:

My current thought is to add an i2cSleep method to the IO plugin protocol and use that if available

Implementing such a change would require a considerable amount of time.

Doesn't seem like it to me. We look for the instances of sleep(n) used for I2C code (perhaps on a case by case basis starting with LCD) and replace it with:
if (io.plugin.i2cSleep) {
  io.plugin.i2cSleep(n);
} else {
  sleep(n);
}

It's really just a search and replace, and I'd rather spend my time doing that than reverting this code.

I think there's going to be more to it than changing the calls to sleep. Changing the calls to sleep should be fairly easy as there's not many of them. It's also code like this where it's a little more subtle:
            io.i2cWriteReg(address, this.REGISTER.AXIS_MAP_SIGN_ADDR, axisSign);

            // Set operational mode to "nine degrees of freedom"
            setTimeout(function() {
              io.i2cWriteReg(address, this.REGISTER.OPR_MODE_ADDR, this.REGISTER.OPR_MODES.NDOF);
              resolve();
            }.bind(this), 10);

I think there's going to be more to it than changing the calls to sleep. Changing the calls to sleep should be fairly easy as there's not many of them. It's also code like this where it's a little more subtle:

That's true, those will indeed be harder to spot. I'm OK with that though...magic numbers, such as pre-defined sleep/setTimeout/etc. lengths, will always be inherently buggy. I think it's fine to fix them as they're discovered.

OH OH OH! I know exactly what is going on, and why the LCD now breaks. We don't need to do an i2cSleep thing...it's not the queueing mechanism at all causing the issue. It's the sleep method.
So here's what's happening:

Johnny-Five calls two I2C methods at https://github.com/rwaldron/johnny-five/blob/v1.3.1/lib/lcd.js#L420-L421
This call winds through J5 to J5-IO and enqueues two I2C operations at https://github.com/nebrius/j5-io/blob/master/src/managers/i2c.ts#L208
Best case scenario, there are no other I2C operations queued up, so the item gets dequeued and we call into Raspi.js at https://github.com/nebrius/j5-io/blob/master/src/managers/i2c.ts#L94-L107, which directly calls i2c-bus. This is asynchronous, so the call is dispatched into the event loop for it to do its thing in C++ land. One I2C write is (most likely) issued on the wire here, but I'm not sure, nor does it matter
The stack unwinds back to https://github.com/rwaldron/johnny-five/blob/v1.3.1/lib/lcd.js#L422
Sleep is called at https://github.com/rwaldron/johnny-five/blob/v1.3.1/lib/lcd.js#L422. Sleep doesn't actually sleep. Rather, it's a while loop so it pegs the CPU core at 100% and (this is the important part) blocks the event loop so we never get the I2C write completion callback for the first operation.
The while loop exits
The I2C write callback is called because the event loop is now unblocked, which goes through the J5-IO queueing mechanism and causes the second write to now be issued (which is supposed to happen before sleep is called, not after).

Anyways, tl;dr, Johnny-Five is blocking the event loop and causing the writes to be issued out of order w.r.t. sleep calls.
As such, this is a bug in Johnny-Five, and needs to be fixed there (probably with an async function).


running "go install ./..." installs two internal programs

It is fairly common to cd into a Go project and run go install ./... to install it. At least that is what I tend to do. You could say that I should be running go install ./cmd/... instead, but cmd/ is not a universal convention, and I am also a creature of habit who is lazy to type more unless strictly necessary :)
I also don't think we want to be telling our users that they should only ever run go install ./cmd/cue, because in the future CUE might come in the form of multiple binaries - much like Go today comes with the gofmt binary. We just happen to have one binary right now.
I think it would be nice if ./... only matched one main package, where right now it matches three:
$ go list -f '{{.Name}} {{.ImportPath}}' ./... | grep '^main '
main cuelang.org/go/cmd/cue
main cuelang.org/go/internal/cmd/qgo
main cuelang.org/go/pkg/gen

A particular problem is that these have short and generic names, so I ended up with a gen program in my $PATH, which was pretty confusing.
 I imagine that the current setup was done for the sake of gopls working well, but with https://github.com/golang/go/issues/49657#issuecomment-1205757682 being fixed very soon (hopefully!), I think we can finally make this nicer for everyone.
Not urgent - mainly a reminder to revisit this once the gopls fix is released, presumably in v0.10.0 sometime this fall.
cc @myitcv @rogpeppe

There are other alternatives too, such as placing the Go packages under directores not traversed by ./..., such as internal/cmd/_qgo. However, that feels unnecessary if we can go for the ignore build tag, and also drop the directories entirely.


add target parameter

When you have a multi-stage docker file you sometimes want to build an image of an intermediate step like a builder. This PR adds supports for the docker target parameter

Thanks for the contribution @JonCubed 💯

Published in v1.3.0


Weird string value written to the standard output

Unwanted std out side effect on window resize
The library (or one of its dependencies?) seems to write the string value "\u001b[3J" to the standard output under certain circumstances. As a result, if one has decided to redirect the standard output to some UI component, such as a TextView, they see this weird string value the first time the application starts and whenever the window size changes.
To Reproduce
Steps to reproduce the behavior:

Create a console GUI app with a multiline text view (the component and its multiline attribute should be irrelevant).
Redirect the standard output like so:  Console.SetOut(outputWriter); where outputWriter is a TextWriter that writes to the text view.
Start the application and observe the the weird string value written to the text view.
Resize the window or enter and exit full screen and observe the same value written multiple times.

Expected behavior
This string value should not be written to the standard output.
Screenshots

Desktop (please complete the following information):

OS: Windows 10

Try with this PR #2264 and check this isn't happening.

If you move cursor around and click do you see other escape codes comming through?

That not the case @tznind. The WindowsDriver (@chr1st0scli please confirm if you are running this driver) don't recognize escape sequence, so it's echoed to the console output and this code if for clear the buffer.

Try with this PR #2264 and check this isn't happening.

Hi @BDisp I just tried the proposed PR. Indeed the weird string value has stopped appearing but unfortunately it has been replaced by another one, namely "\u001b[0J"

I already expected that. Was changed from "\u001b[3J" to "\u001b[0J". This code is in the ResizeScreen method of the WindowsDriver.cs. Removing it solves the issue. That PR is still under development, I think. WindowsDriver can not have escape sequences because it isn't configured to use virtual terminal, so it's supposed to output that characters if the console output is redirected, on theses terminals (cmd, vsdebugger, conhost, pwsh). Strangely the escape sequences are executed on the Windows Terminal but, unfortunately still have some incompatibilities with legacy terminal, like not allowing resize the console buffer size but only the window size.

That not the case @tznind. The WindowsDriver (@chr1st0scli please confirm if you are running this driver) don't recognize escape sequence, so it's echoed to the console output and this code if for clear the buffer.
Edit: Your solution is great @tznind.

@BDisp I am not sure how I can determine with certainty the thing you are asking about WindowsDriver. I am not sure what we are talking about. My OS is windows though. If you are referring to the class, no I am not directly using it as it is internal in the library.

Ok no problem. For your information there are 3 official drivers and another for tests (FakeDriver).
If you are running on a Windows OS:

If you running with the Application.UseSystemConsole as false (default) then you are using the WindowsDriver.
If you running with the Application.UseSystemConsole as true then you are using the NetDriver.

If you are running on a Linux or macOS:

If you running with the Application.UseSystemConsole as false (default) then you are using the CursesDriver.
If you running with the Application.UseSystemConsole as true then you are using the NetDriver.

So the NetDriver is a cross platform driver but more slower.

Hi @BDisp

I have noticed that "\u001b[3J" is no longer written when using the WindowsDriver. (Noticed since 1.14.0 I think)
I still need to ignore "\u001b[0 q" or "\u001b[1 q" when using the CursesDriver.

Should I close this bug or is the second information above of some value?

What does the escapes sequences in the second information?

The "\u001b[1 q" is being printed by the CursesDriver (I have tried it with a docker container using alpine).

If you are interested to reproduce, I have a temporary branch here https://github.com/chr1st0scli/RainLispConsole/tree/terminalgui-bump
But you have to comment out lines 26 & 27 in OutputTextViewWriter.cs and try out in Linux.

I already know what is going on here. The cause of the output is CursesDriver escape sequence Console.Out.Write ("\x1b[{0} q", ((int)visibility >> 24) & 0xFF); which handles the cursor visibility. When you exit the application you'll see that mouse escape sequences are echoed to the console. The main cause of the issue is the fact you are redirecting the output to a custom TextWriter. You must prevent using the redirection before the app is loaded and after is unloaded. The Ansi escape sequences must always run on the original console output.
Maybe you can use the toplevel Loaded and UnLoaded events to restore the output redirection.

Thanks!


build_summary - error in merge statement

Describe the bug
build_summary results in error.
Error message “Warning: Error in fix.by: 'by' must specify a uniquely valid column”.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Additional context
After some debug and found that the R function went through successfully after I did a minor change as below:

Undone by issue #5


Display filepath for RuntimeError: Error loading audio file in sox_io backend

🚀 Feature
When user encounters the error RuntimeError: Error loading audio file: failed to open file. using sox_io backend, the filepath should be displayed as part of the error message at the bottom of the stack trace.
Motivation
This is a very common error when setting up a new dataset and it would be much faster to fix if the filepath were output to the user.
Pitch
Wrap the relevant section of load with a try/except to catch RuntimeError and reraise with the filepath included so that the user may more easily fix the issue. I'm happy to PR if this is an acceptable fix.
Alternatives
Ideally the filepath would be added to the error at the original point of failure but it appears to be in c++ so I'm not sure how.
Additional context
relevant code from torchaudio/backend/sox_io_backend.py
if not torch.jit.is_scripting():
        if hasattr(filepath, 'read'):
            return torchaudio._torchaudio.load_audio_fileobj(
                filepath, frame_offset, num_frames, normalize, channels_first, format)
        filepath = os.fspath(filepath)
    return torch.ops.torchaudio.sox_io_load_audio_file(
        filepath, frame_offset, num_frames, normalize, channels_first, format)

HI @rbracco
Thanks for the suggestion. I'll take a look into it.

Filed #1503. If no one picks it up, I will come back before the release.

Awesome, thank you so much. Closing the issue.

@rbracco I will keep this open until the actual change is implemented.


Route does not fail while while dragging marker

While dragging a marker to an unroutable area, the suggested route continues to display the last successful route till the marker is dropped. This behavior makes it very hard to spot the exact point of failure while doing directions QA.

http://map.project-osrm.org/?z=17&center=43.653788%2C-79.380233&loc=53.544389%2C-113.490927&loc=43.653691%2C-79.380566&hl=en&ly=&alt=&df=&srv=
In the previous frontend the route would update will dragging the marker. Lets have this behavior back..

cc @amyleew @shvrm

I'm pretty sure this issue really relates to LRM, so I've created https://github.com/perliedman/leaflet-routing-machine/issues/167 for this.
Since I'm currently mostly doing LRM in my free time, any help with this would of course be very much appreciated.

I've investigated this a bit, and I don't think there's an exact solution to the problem. It would be interesting to know how the old frontend worked.
The issue is really this:

When a waypoint is located in an "unroutable" area, OSRM will still find the nearest routable node, and route from there
Because the nearest node is used for routing, there's no such thing as an "unroutable area", or at least there is no way for LRM to tell - actual, routed waypoints will often be located some distance from where the user placed them, and OSRM will still route
The new frontend uses a waypointMode called snap, that means waypoints will be moved to the actual, routed waypoint locations once routing finishes - this is not done during drag, however, which makes it less clear what is happening
If you do the same routing with waypointMode set to extend, it becomes much more visibly clear which part is actually routed

My guess is that the old frontend used some sort of threshold - if the actual, routed waypoint was further away from the placed waypoint, the route was simply discarded.
I'm still a fan of waypointMode: extend, but I would be interested in other ideas of how this could work .

@perliedman to clarify, the most important task while debugging a failed route is to find the exact point of failure. This allows us to investigate why the route failed at that exact point.
This is how it used to work in the previous frontend.

Yep, I think I get it!
Weirdly enough, I couldn't find any unroutable areas around where I live, even if I placed waypoints far out in the sea - OSRM would always return a route, even though several kilometers from any road or ferry route. Because of this, I misunderstood the issue.
However, when actually trying the example you provided above, I can get OSRM to refuse to route me.
Anyway, a fix for when OSRM actually doesn't return a route is available in https://github.com/perliedman/leaflet-routing-machine/commit/001a83748439ada4176f0faaab4f2a5493edfc16

@perliedman yeah the intended behavior is that it always returns a route. But sometimes we hit edge cases where this is not the case. This helps to debug this.
Thanks! :+1:

Thanks for the fix @perliedman

I think this should be closed, since the site runs LRM 2.6.1, which contains the fix mentioned above.

@perliedman thanks for digging this up! :+1:


Update Erjang link

The link to the Erjang homepage now resolves to a Japanese voice acting website. I've updated the link to point readers to the author's GitHub page, which seems to be the most up-to-date resource.

Thanks


[19.09] protonvpn ng 2.2.0 to 2.2.2

Motivation for this change
Make sure the package works for everybody
Things done
Backport from PR #81735

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/pr-approved-needs-merging-protonvpn-cli-ng/6406/3


resolvePageComponent maybe cause import incorrect component

The docs topic in Vite with Inertia of Extra topics.
In Example implementation section the sample code as follow
function resolvePageComponent(name: string, pages: Record<string, any>) {
  for (const path in pages) {
    if (path.endsWith(`${name.replace('.', '/')}.vue`)) {
      return typeof pages[path] === 'function'
        ? pages[path]()
        : pages[path]
    }
  }

  throw new Error(`Page not found: ${name}`)
}

It's may meet the problem that loads the wrong component. Let's say I have two components Post/Index and Administrator/Post/Index one for the client and one for the dashboard.
Only using endsWith will cause wrong behavior.

Hey, I'm aware of that issue - it came with Vite 3 - I forgot to change the snippet in the docs. I'll update it, thanks for the heads up.


Highlighting full samples

#57283

@GeekTrainer : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Incompatibility

After version 1.3.7 the mod is incompatible with Comments in Pause menu.  More details in the video: https://youtu.be/EX0LUILfstA?si=Cf0hHl2x0e8IDVQo

Also this bug appears when viewing player's levels through globed players menu


Load state dict with assign to avoid OOMs

Description
I personally keep getting OOMs when trying to load llama3 8B. I narrowed down the offending code to load_and_process_state_dict, then realized Neel offered a suggestion in #480 that isn't implemented yet.
So, a simple change: always use assign=True (if the installed PyTorch version is recent enough).
Previously, tests broke because of a mismatch in the dtype of the state_dict mask and the default TL mask. Adding a cast fixes all tests.
Fixes #480. (issue)
Type of change
Bug fix or new feature, depending on perspective. Should allow loading more models without needing a ton of memory.
Screenshots
Please attach before and after screenshots of the change if applicable.

Checklist:

[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I have not rewritten tests relating to key interfaces which would affect backward compatibility

Thank you very much for doing this! I am going to be using this PR to work on something else I have been working on to see if I notice anything odd. This is a pretty sensitive area of the project, so we need to make sure things are working as expected before merging.

Alright, so after first run, it seems pretty good. I did get some weird generations with your branch though, which is generally not unheard of. I do want to run my two scripts side by side to make sure there is no further degradation beyond what we have at the moment.

Well, I am sorry to say, but there are more issues. Both Qwen/Qwen-1_8B and Qwen/Qwen-1_8B-Chat are both broken on this branch. I have verified that they both work with the current release of TransformerLens, and that the failure is indeed exclusive to this PR. The issue is type mismatch.
Here is the full error
[/usr/local/lib/python3.10/dist-packages/transformer_lens/HookedTransformer.py](https://8toay7rrexo-496ff2e9c6d22116-0-colab.googleusercontent.com/outputframe.html?vrz=colab_20240919-060125_RC00_676352627#) in generate(self, input, max_new_tokens, stop_at_eos, eos_token_id, do_sample, top_k, top_p, temperature, freq_penalty, use_past_kv_cache, prepend_bos, padding_side, return_type, verbose)
   2137                         )
   2138                     else:
-> 2139                         logits = self.forward(
   2140                             tokens,
   2141                             return_type="logits",

[/usr/local/lib/python3.10/dist-packages/transformer_lens/HookedTransformer.py](https://8toay7rrexo-496ff2e9c6d22116-0-colab.googleusercontent.com/outputframe.html?vrz=colab_20240919-060125_RC00_676352627#) in forward(self, input, return_type, loss_per_token, prepend_bos, padding_side, start_at_layer, tokens, shortformer_pos_embed, attention_mask, stop_at_layer, past_kv_cache)
    559                     )
    560
--> 561                 residual = block(
    562                     residual,
    563                     # Cache contains a list of HookedTransformerKeyValueCache objects, one for each

[/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py](https://8toay7rrexo-496ff2e9c6d22116-0-colab.googleusercontent.com/outputframe.html?vrz=colab_20240919-060125_RC00_676352627#) in _wrapped_call_impl(self, *args, **kwargs)
   1551             return self._compiled_call_impl(*args, **kwargs)  # type: ignore[misc]
   1552         else:
-> 1553             return self._call_impl(*args, **kwargs)
   1554
   1555     def _call_impl(self, *args, **kwargs):

[/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py](https://8toay7rrexo-496ff2e9c6d22116-0-colab.googleusercontent.com/outputframe.html?vrz=colab_20240919-060125_RC00_676352627#) in _call_impl(self, *args, **kwargs)
   1560                 or _global_backward_pre_hooks or _global_backward_hooks
   1561                 or _global_forward_hooks or _global_forward_pre_hooks):
-> 1562             return forward_call(*args, **kwargs)
   1563
   1564         try:

[/usr/local/lib/python3.10/dist-packages/transformer_lens/components/transformer_block.py](https://8toay7rrexo-496ff2e9c6d22116-0-colab.googleusercontent.com/outputframe.html?vrz=colab_20240919-060125_RC00_676352627#) in forward(self, resid_pre, shortformer_pos_embed, past_kv_cache_entry, attention_mask)
    158             # queries, keys and values, independently.
    159             # Then take the layer norm of these inputs, and pass these to the attention module.
--> 160             self.attn(
    161                 query_input=self.ln1(query_input)
    162                 + (0.0 if shortformer_pos_embed is None else shortformer_pos_embed),

[/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py](https://8toay7rrexo-496ff2e9c6d22116-0-colab.googleusercontent.com/outputframe.html?vrz=colab_20240919-060125_RC00_676352627#) in _wrapped_call_impl(self, *args, **kwargs)
   1551             return self._compiled_call_impl(*args, **kwargs)  # type: ignore[misc]
   1552         else:
-> 1553             return self._call_impl(*args, **kwargs)
   1554
   1555     def _call_impl(self, *args, **kwargs):

[/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py](https://8toay7rrexo-496ff2e9c6d22116-0-colab.googleusercontent.com/outputframe.html?vrz=colab_20240919-060125_RC00_676352627#) in _call_impl(self, *args, **kwargs)
   1560                 or _global_backward_pre_hooks or _global_backward_hooks
   1561                 or _global_forward_hooks or _global_forward_pre_hooks):
-> 1562             return forward_call(*args, **kwargs)
   1563
   1564         try:

[/usr/local/lib/python3.10/dist-packages/transformer_lens/components/abstract_attention.py](https://8toay7rrexo-496ff2e9c6d22116-0-colab.googleusercontent.com/outputframe.html?vrz=colab_20240919-060125_RC00_676352627#) in forward(self, query_input, key_input, value_input, past_kv_cache_entry, additive_attention_mask, attention_mask, position_bias)
    193         """
    194
--> 195         q, k, v = self.calculate_qkv_matrices(query_input, key_input, value_input)
    196
    197         if past_kv_cache_entry is not None:

[/usr/local/lib/python3.10/dist-packages/transformer_lens/components/abstract_attention.py](https://8toay7rrexo-496ff2e9c6d22116-0-colab.googleusercontent.com/outputframe.html?vrz=colab_20240919-060125_RC00_676352627#) in calculate_qkv_matrices(self, query_input, key_input, value_input)
    354             )
    355         else:
--> 356             q = self.hook_q(attn_fn(query_input, self.W_Q, self.b_Q))
    357         if self.cfg.load_in_4bit:
    358             if not isinstance(self.W_K, Params4bit):

[/usr/local/lib/python3.10/dist-packages/transformer_lens/utilities/attention.py](https://8toay7rrexo-496ff2e9c6d22116-0-colab.googleusercontent.com/outputframe.html?vrz=colab_20240919-060125_RC00_676352627#) in simple_attn_linear(input, w, b)
     17     w = einops.rearrange(w, "head_index d_model d_head -> (head_index d_head) d_model")
     18     b_ = einops.rearrange(b, "head_index d_head -> (head_index d_head)")
---> 19     return F.linear(input, w, b_).reshape(input.shape[0], input.shape[1], b.shape[0], b.shape[1])
     20
     21

RuntimeError: mat1 and mat2 must have the same dtype, but got Float and BFloat16

To be completely honest with you, I am not sure if this is worth pursuing. There could be a whole cascade of issues here caused by this loading variable, which we may not even think to test due to the multitudes of possible ways TransformerLens can be configured. I am not sure if I would ever feel comfortable merging this given the whack-a-mole bug hunting that this is already turning into. The CI coverage is simply not high enough for me to feel like we will ever have all of the bugs caused by this resolved.
If you want to keep pursuing this, we can, and I am happy to keep stress testing different revisions to make sure it is working, but I want you to know my feeling today before you spend another 10-20 hours working on this to ultimately have it be decided to not merge 2 months from now due to compatibility uncertainty.
Realistically, this pr got us 98% of the way there. Using this variable is going to use slightly less ram than what TransformerLens uses now, but only slightly less. Three months ago, this would have saved 50% memory consumption, but things have changed since then. This variable will cause the load to run faster, but when weighing a change on the spectrum of compatibility/stability against performance, compatibility is always going to win out on this project.
If we can improve performance even 1% without impacting compatibility, then that's great. The moment we start seeing that something is a miss in the compatibility, then that raises a massive red flag. Now we are in a situation where the CI is passing, but we don't have great coverage to begin with, and it was really easy for me to break this implementation beyond what the CI tells us.
It's a good idea, and a good effort, but I am very uncertain of if the benefits of this outweighs the potential pile of bugs we may introduce.

Thanks, closing this for now. I was pondering if there is some way to only use assign if the dtype matches what's expected by TL, but not sure how to properly do that kind of type introspection.

@cyber-chris If you want to explore this more later on let me know! I may still reopen your branch, and merge it into the main repo as an experiment. I am working on a way to bulk test all supported models, which is a pretty big logistical task. Once that is done, I would be more willing to put something like this into a release.


kernel: fatal: unlock IRQs in early return points in z_fatal_error

We need to unlock IRQs in early return points of
z_fatal_error() functions; not only at the normal
return point.
Signed-off-by: Ioannis Glaropoulos<EMAIL_ADDRESS>Fixes #22828

Heh, what's TEST mode? I genuinely would have thought this was a no-return function.

Well it is useful to return when we execute tests :)


[0.41] Commits to cherry pick into stable

List of fixes to cherry-pick
CC: @oblador

https://github.com/facebook/react-native/commit/8d2a034f9c18988a6a63726767bddecd0d02424d Fix sizing of container with child overflowing parent

If any podspec user would like to run 0.41 i suggest this is included since it breaks 0.41 https://github.com/facebook/react-native/commit/6e9fe3707a8701c0d2910f96bfb053e8bbe67c4a

The iOS release build of a new (react-native init) project is broken without https://github.com/facebook/react-native/commit/e0c3d56d3a5dcc68c1a7585275a051d781ade914.

Noticed that the RC that went out yesterday didn't have these commits. Do we want to release these directly into the final release?

We released stable. RC you referring to was released by @mkonicek and included fixes he needed for internal works.

@grabbou Please cherry-pick the fixes for this issue: #11809 into 0.41. Thanks a lot.


What are some modern alternatives?

Any suggestions?

@jgonggrijp develops https://jgonggrijp.gitlab.io/wontache/

Please feel welcome to respond to tickets or submit new tickets on the issue tracker. You can login with your GitHub if you don't have GitLab.


Info about unsupported sources

Problem
Every time I open sources page, I get the following error. This message does not really mean anything since I don't know what to do really.
Learn More button takes me to medium article that is more targeted to developers.
If I'm not a developer, I have nothing. I would maybe want to know about the details about these unsupported sources so that I can uninstall those apps that are not supported anymore.
What do you think?
Screenshot

Muzei sends notifications after you upgrade to Muzei 3.2.0 for each unsupported source, telling you exactly what source is no longer supported. I assume you already dismissed those notifications?

Hmmm, I haven't seen them unfortunately. 😔

Muzei 3.2.0 Alpha 5 is rolling out now with a fix (the 'Learn More' link in the Snackbar now opens a separate screen with details about all of the Legacy Sources).


Azure SDK for PowerBI Dedicated

Description

This checklist is used to make sure that common guidelines for a pull request are followed.

[V] I have read the contribution guidelines.
[V] The pull request does not introduce breaking changes.

General Guidelines

[V] Title of the pull request is clear and informative.
[V] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[V] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[V] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[V] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.
[V] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

Description:
First generation of SDK for Power BI Dedicated resource. New Azure resource which simplify the way ISVs and developers use Power BI capabilities.
Link to spec PR:
https://github.com/Azure/azure-rest-api-specs/tree/current/specification/powerbidedicated/resource-manager/Microsoft.PowerBIdedicated/2017-10-01/powerbidedicated.json
Thanks!


[ UI ] - Popup component MUI version updated.

Notes for Reviewers
This PR fixes #12423
Migrated the Popup.js function to MUI V5 using supported sistent components.
Light mode:
Previous component:

New component:

Dark mode:
Previous component:

New component:

Signed commits

[X] Yes, I signed my commits.

Hello @SAHU-01 @yash37158 @sudhanshutech I've made the PR as assigned to me have a look at this. Thanks!

@Pratik-050
Thank you for your contributions! Let's discuss this during the Meshery Development call today at 9:00 AM CT | 7:30 PM IST. Adding it as an agenda item to the meeting minutes || meeting link.

This looks good to me @Pratik-050, have you run this locally to test with other components, to ensure it's not breaking the existing functionality/style?
Once, you add the necessary sistent token changes we should be good to merge.

Hello @SAHU-01 everything is working fine, I'm just unable to find the correct background token from sistent.
Once that is fixed then we are good to go. Can you help me finding that?

Hello @SAHU-01 I've made some some changes please have a look. @leecalcote @yash37158 @sudhanshutech does the new colors good to go?

Is there a pop-up component in Sistent?

Is there a pop-up component in Sistent?

No sir I don't think there's a dedicated component for popup in the sistent library.

LGTM otherwise

LGTM otherwise


Remove setup_optimizers_in_pre_dispatch logic (from #10596 comments)

Proposed refactor
Commented in #10596, setup_optimizers_in_pre_dispatch logic is not needed anymore
Motivation

Pitch
To be added
Additional context

If you enjoy Lightning, check out our other projects! ⚡

Metrics: Machine learning metrics for distributed, scalable PyTorch applications.

Lite: enables pure PyTorch users to scale their existing code on any kind of device while retaining full control over their own loops and optimization logic.

Flash: The fastest way to get a Lightning baseline! A collection of tasks for fast prototyping, baselining, fine-tuning, and solving problems with deep learning.

Bolts: Pretrained SOTA Deep Learning models, callbacks, and more for research and production with PyTorch Lightning and PyTorch.

Lightning Transformers: Flexible interface for high-performance research using SOTA Transformers leveraging Pytorch Lightning, Transformers, and Hydra.

cc @awaelchli @justusschock @akihironitta

Yes, in a sense it is not needed anymore, but what is needed instead is that the fully sharded plugin will have to override the setup() and pre_dispatch() methods.


void before an expression is misclassified as a variable

The void before the expression is used to discard the value of the expression from the return value candidate list
I think lint has misjudged here

maybe fixed in v1.6.2.


Fix issues with file_system dependency

I got some issues when starting the tableau server:
warning: using map.field notation (without parentheses) to invoke function FileSystem.Backends.FSInotify.bootstrap() is deprecated, you must add parentheses instead: remote.function()
  (file_system 0.2.10) lib/file_system/backend.ex:23: FileSystem.Backend.backend/1
  (file_system 0.2.10) lib/file_system/worker.ex:18: FileSystem.Worker.init/1
  (stdlib 6.0) gen_server.erl:2057: :gen_server.init_it/2
  (stdlib 6.0) gen_server.erl:2012: :gen_server.init_it/6
  (stdlib 6.0) proc_lib.erl:329: :proc_lib.init_p_do_apply/3

22:25:50.659 [error] unknown option `{:latency, 0}`, ignore

This upgrade of file_system to version 1.0 fixes those issues

@mhanberg This would be a very good fix to have.

Turns out I don't haven't notifications on for this repo 🤦
Thanks for the ping


Extension not found

I'm trying to download the extension through Visual Studio Marketplace but it says that the requested page cannot be found

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

ID: e40394ca-9a55-d9b5-d427-7c2a2c00cfc8
Version Independent ID: 5a5c17e2-a683-88f6-07a9-2002e814d54c
Content: Live Reload - Xamarin
Content Source: docs/xamarin-forms/xaml/live-reload.md
Product: xamarin
GitHub Login: @pierceboggan
Microsoft Alias: piboggan

the extension is not in the marketplace. Is this removed parmanently or temporarily. was lookin for it for UWP

As mentioned in the linked issue, it has been removed from the marketplace. Try the XAML Previewer for an alternative way to see your UI during development.


缺少这么多文件怎么破？OSError: Error no file named pytorch_model.bin, tf_model.h5, model.ckpt.index or flax_model.msgpack found in directory projects/GLEE/clip_vit_base_patch32.

OSError: Error no file named pytorch_model.bin, tf_model.h5, model.ckpt.index or flax_model.msgpack found in directory projects/GLEE/clip_vit_base_patch32. 缺这么多文件怎么说

Thank you for bringing attention to the error message regarding the missing CLIP .bin weights. The requirement for this weights is indeed mentioned in our training documentation at https://github.com/FoundationVision/GLEE/blob/main/assets/TRAIN.md.
Understanding that not everyone will need to train the model, I have now updated our installation instructions to include this prompt. You can find the revised instructions at https://github.com/FoundationVision/GLEE/blob/main/assets/INSTALL.md.
Thanks for your reminder.


Replace symlinks with copy files

This change is

Coverage remained the same at 82.305% when pulling 72a557c8747ec532361ad2d9c54612c76d01505d on alleycat-at-git:alexey/replace_symlinks_copy into a921fbf529fedcd7ca2d59919f34984e0eb91760 on shakacode:master.

See #479


Handle FontScale for macOS retina

Hello, and happy new year!
I'm working on adding your project, and I stumbled on this issue. On Mac Retina screen, I was having a layout like this:

This is when handling highDPI with imgui: macOS "hides" the DPI, and we are using virtual pixels (i.e the screen is seen as being 1280x720 instead of 2560x1440)
=> Fonts are loaded at twice the size, and then resized before being displayed.
FontGlobalScale is used almost only on MacOS. On Windows and Linux, imgui uses the real pixel sizes.
With this patch, I can obtain:

I'm sorry, there might be an issue in my PR.
Let me explain: I'm integrating your library into imgui_bundle. imgui_bundle provides a bunch of ImGui libraries, for c++ as well as for python with quasi identical sources.
However, in order to generate bindings, it cannot accept const char * members. During this process, I had to change const char* Command::Name to std::string Command::Name.
I wanted to do this only for my fork, not in the main repository (and also not in this PR), and I accidentaly put a PR on a branch on which I am also adding changes related to imgui-bundle.
If you want to remove this part of the change you should git revert  3db0ff7fad3c17206c90d7fdb11ef5323a1c9e4c
(However, since you are already using std::function, using std::string is perhaps not too much of a concern to you).
Sorry for this!

Indeed I did notice this, but I thought it made more sense for ImCmd::Command to own its name instead of having a borrow to some random owner's string (although for me the command names tend to be literals so that worked out initially).
It it break the example though, I'm fixing it. Thanks for mentioning the problem anyways!


use PkgTestSuite.jl

Coverage remained the same at 100.0% when pulling f01df7f8df3f16be4f81e8feb1f3b425f8aed759 on PkgTestSuite into 8dae1414f540d4b416824018d9a0b345d092c48c on master.

Coverage remained the same at 100.0% when pulling f01df7f8df3f16be4f81e8feb1f3b425f8aed759 on PkgTestSuite into 8dae1414f540d4b416824018d9a0b345d092c48c on master.


Module version mismatch. Expected 47, got 46.

Hello,
After downloaded the source added dashGB service using command from cf command line. After adding the service, get the credentials and put in app.js. Install the npm modules. now on doing npm start or node app.js it's giving following error,
        throw e
        ^

Error: Module version mismatch. Expected 47, got 46.
    at Error (native)
    at Object.Module._extensions..node (module.js:440:18)
    at Module.load (module.js:357:32)
    at Function.Module._load (module.js:314:12)
    at Module.require (module.js:367:17)
    at require (internal/module.js:16:19)
    at bindings (C:\Prasanta\Official\IBM\IDEA\NBA\dashdb-nodejs-helloworld-mast
er\dashdb-nodejs-helloworld-master\node_modules\bindings\bindings.js:74:15)
    at Object.<anonymous> (C:\Prasanta\Official\IBM\IDEA\NBA\dashdb-nodejs-hello
world-master\dashdb-nodejs-helloworld-master\node_modules\ibm_db\lib\odbc.js:27:
31)
    at Module._compile (module.js:413:34)
    at Object.Module._extensions..js (module.js:422:10)

Please let me know how to resolve the issue while running it in local.

Hi @prasanta303 ,  I hope you are on Windows. This issue is fixed in ibm_db version 1.0.2.  Can you please modify your package.json to include the latest version and try again.
"ibm_db": "1.0.2",
Please let me know how it goes.  Thank you.

Hi @prsahoo, Yes, I am on Windows. I have modified my package.json as per your advice. Even if, I am getting same kind of issue but have different version mismatch as below,
C:\Prasanta\Official\IBM\IDEA\NBA\dashdb-nodejs-helloworld-master\dashdb-nodejs-
helloworld-master\node_modules\bindings\bindings.js:83
        throw e
        ^

Error: Module version mismatch. Expected 47, got 48.
    at Error (native)
    at Object.Module._extensions..node (module.js:440:18)
    at Module.load (module.js:357:32)
    at Function.Module._load (module.js:314:12)
    at Module.require (module.js:367:17)
    at require (internal/module.js:16:19)
    at bindings (C:\Prasanta\Official\IBM\IDEA\NBA\dashdb-nodejs-helloworld-mast
er\dashdb-nodejs-helloworld-master\node_modules\bindings\bindings.js:76:44)
    at Object.<anonymous> (C:\Prasanta\Official\IBM\IDEA\NBA\dashdb-nodejs-hello
world-master\dashdb-nodejs-helloworld-master\node_modules\ibm_db\lib\odbc.js:27:
31)
    at Module._compile (module.js:413:34)
    at Object.Module._extensions..js (module.js:422:10)

Please help me out.

@prasanta303 I managed to get this to work - I changed the Package file - Jade was deprecated and you need Pug
"dependencies": {
"cf-deployment-tracker-client": "0.0.8",
"express": "3.5.x",
"ibm_db": "1.0.2",
"pug": "2.0.0-beta11"
},
Refresh your package file and rerun npm install.
Not sure it's relevant but I also updated the Manifest File to have my own unique host variable below with your own unique one

Error: Module version mismatch. Expected 47, got 46.

This is because you installed your dependencies with one node version, and are requiring them with another node version.
47 is node 5.x and 46 is node 4.x, FYI:   node -p process.versions.modules will tell you the ABI number for your node.


 I have tested this on the newest commit, and the overflow still exists.

ASAN:DEADLYSIGNAL
=================================================================
==18556==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x7feef1c3fb51 bp 0x7ffc3c4431c0 sp 0x7ffc3c442910 T0)
==18556==The signal is caused by a READ memory access.
==18556==Hint: address points to the zero page.
    #0 0x7feef1c3fb50  (/usr/lib/x86_64-linux-gnu/libasan.so.4+0xafb50)
    #1 0x4850b1 in lexer_construct_literal_object /home/XXX/git/jerryscript/jerry-core/parser/js/js-lexer.c:2450
    #2 0x485cb4 in scanner_create_variables /home/XXX/git/jerryscript/jerry-core/parser/js/js-scanner-util.c:2171
    #3 0x4529d4 in parser_push_block_context /home/XXX/git/jerryscript/jerry-core/parser/js/js-parser-statm.c:367
    #4 0x461a95 in parser_parse_for_statement_start /home/XXX/git/jerryscript/jerry-core/parser/js/js-parser-statm.c:1533
    #5 0x461a95 in parser_parse_statements /home/XXX/git/jerryscript/jerry-core/parser/js/js-parser-statm.c:2967
    #6 0x46654b in parser_parse_source /home/XXX/git/jerryscript/jerry-core/parser/js/js-parser.c:2304
    #7 0x466e4b in parser_parse_script /home/XXX/git/jerryscript/jerry-core/parser/js/js-parser.c:2933
    #8 0x4aa2d5 in jerry_parse.constprop.28 /home/XXX/git/jerryscript/jerry-core/api/jerry.c:451
    #9 0x402eb8 in main /home/XXX/git/jerryscript/jerry-main/main-unix.c:112
    #10 0x7feef17e683f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2083f)
    #11 0x4041c8 in _start (/home/XXX/git/jerryscript/build/bin/jerry+0x4041c8)

AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV (/usr/lib/x86_64-linux-gnu/libasan.so.4+0xafb50)
==18556==ABORTING

Still valid on latest master ( 0ffe1665bd0ee457dd4c1083811e1592a5e2908d ).
The test case hits the same assertion as the test case in #4190 issue:
ICE: Assertion 'context_p->next_scanner_info_p->type == SCANNER_TYPE_BLOCK' failed at /home/oszi/jerryscript/jerry-core/parser/js/js-parser-statm.c(parser_push_block_context):344.

Resolved via #4462.

Resolved via #4462.


Allow hubs to maintain their own user image

For most of the hubs hosted on our cluster (in *.pilot.2i2c.cloud, and *.cloudbank.2i2c.cloud), we use this user image. This is a bit generic, and has things many people want. But customizing this on a per-hub basis doesn't work very well!

Version conflicts will happen quickly and cause big problems
Any environment updates require intervention from 2i2c engineers
If we install additional languages, becomes confusing for users of hubs that don't need it.

So we need a solution that's as close to binder as possible, in terms of empowring our hub admins. It should:

Give hub admins complete control over the user environment
... in a way that lets them iterate and test the environment with standard tools (in this case, mybinder.org)
... without having to deeply understand how all the pieces (repo2docker, docker, mybinder, binderhub, jupyterhub, etc) fit together
... with minimal intervention from 2i2c staff.

Potential solution
For the peddie hub, @sawula requested the py5 package. This adds a new kernel, and also requires Java. Instead of adding it to default image, I've instead:

Forked the binderized example repo to https://github.com/2i2c-org/peddie-image (Thanks to https://github.com/2i2c-org/pilot-hubs/issues/479#issuecomment-866519098)
Setup repo2docker-action to push to our quay.io account
Setup a different action to comment with a 'test this in binder' link for each PR
Add docs on how to update your hub to use a new image + tag with the JupyterHub Configurator

There's lots to be improved here, but I think this is a good start on making this process easier.
Related: https://github.com/2i2c-org/pilot-hubs/issues/312

Pre-existing very helpful feedback about the configurator: https://github.com/2i2c-org/pilot-hubs/pull/329#issuecomment-809747595

This is great @yuvipanda!
I really like the idea "test this in binder"... it is super important the users do not need to deal with local setups to test their changes.
Maybe one future improvement would be a way to automatically update the image from the very same image repository, so they do not need to go through the configurator step... although the configurator path is more than enough for now, IMHO.

Could we consider this a duplicate of https://github.com/2i2c-org/pilot-hubs/issues/631 ?

@choldgraf, I opened an issue about the test this in binder feature in the new user image template repository.
I think this was the only thing was missing from https://github.com/2i2c-org/pilot-hubs/issues/631. So, I think we could potentially close this one and leave the other issue open (since it's is more "closer" to where the change should happen).
What do you all think?

perfect - that makes sense to me! let's close this and track it in #631 thanks Georgiana :-)


how to tranform 3d points from one frame to another

hi,
Yao-Shao,
thanks for your awesome work. may i ask a question about the transformation? how can man tranform 3d points from one frame to another(or is it even possible to do that?)
i know there is a 4x4 row major transform matrix. but it is 4x4. when we have points whose shape is (n, 3), how can we do the transform operation?
thanks for your reply in advance.

Hi @hughlee815. Just add "1" for the forth dimension, like (x, y, z) -> (x, y, z, 1) and then apply the transform matrix

hi,
thanks for your soon reply. i tried your solution immediately, it works very well. but i got another question---after applying the transform matrix with the boxes of the second frame, these new boxes i got didn't coincide with those of the first frame.
i am wondering whether i get any wrong? shouldn't those boxes of the two frames coincide?

What do you mean by "coincide"? Did you draw the two boxes on the same image? If so, ofcourse the two boxes won't coincide because they are in the diffrent frame and the image is in the camera frame. If you want to draw bounding boxes on the image, you should use the bbox in the camera frame only, otherwise the bbox will not work well with the ground truth.

Aha, thanks, i guess i understand why i am wrong. Just one thing I am still not so clear --- I transform points from the 9th frame (just an example) to the 1st frame by
trans = np.dot(np.linalg.inv(frame_1_pose), frame_9_pose)    # frame_1_pose means the 4*4 transform matrics in frame 1 points = np.row_stack((frame_9_points, np.ones(points.shape[0]))) points_transformed = np.dot(points, trans)[:,:3]
then i draw points_transformed and also 3d boxes in frame 9(which are not transforemed) via mayavi in one figure. In theory, point objects should not be in these 3d boxes, since these points have been transformed, while the 3d boxes are not. But according to my experiment, these point objects are still in these boxes, like they have never been transformed.
This result is a little hard for me to understand. If it's not too much trouble, could you please tell me why this happen or did I do anything wrong?
Thanks in advance.

thans so much. i finlly find it is my code problem, the method is perfect!!!   thanks once again. respect!