octofetch: init at 0.3.1

Motivation for this change
Add https://github.com/azur1s/octofetch
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

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

1 package built:

octofetch

Sorry about that, this is my first package. Thanks for the feedback!


Readme: Updated script tags with CDN links

Generated CDN links with JS Deliver and added in the Readme.md installation section!

hmm. probably we don't want to put the version in the readme file, if avoidable, can you do @latest or not specify a version, and it will take the latest?

hmm. probably we don't want to put the version in the readme file, if avoidable, can you do @latest or not specify a version, and it will take the latest?

We could actually do that by omitting the version from the link! But it may affect all the users, if the latest version is buggy! So shall we add two sections namely latest stable version & latest version.

hmm. maybe add a note that you can add a version string to it to pin the version .. but i don't want to be editing the readme every release.  :-)  thank you!


Version 3.0.11 has broken the icon styling

Hi.
I have recently updated to version 3.0.11 and noticed that the alert text was flush up against the icon instead of there being some space (see attached screenshot).
The previous version (3.0.10) works fine.

Dan

You closed this ticket, did you resolve it? @danr1979

I did. It seems to be working now so might've been something to do with my
environment.
Thanks.
On Wed, 30 Oct 2024, 14:34 CodeWithDennis, @.***> wrote:

You closed this ticket, did you resolve it? @danr1979
https://github.com/danr1979
—
Reply to this email directly, view it on GitHub
https://github.com/CodeWithDennis/filament-simple-alert/issues/29#issuecomment-2447359271,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABFVJFGDKFJIYLMMQOTTWATZ6DU7BAVCNFSM6AAAAABQ4HPONGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBXGM2TSMRXGE
.
You are receiving this because you were mentioned.Message ID:
@.***>


uv_fs_realpath causes SIGABRT on darwin when the realpath is really long

Version: 1.32.0 (node 12.12.0)
Platform: Darwin Kernel Version 19.6.0: Sun Jul  5 00:43:10 PDT 2020; root:xnu-6153.141.1~9/RELEASE_X86_64

Reproduce from nodejs:
$ LONG_PATH='/tmp/long/long/long/long/long/long/long/long/long/long/long/long/long/long/long/long/long/long/long/long/long/long/long/long/long/long/long/long/long/long/long/long/long/long/long/long/long/long/long/long/long/long/long/long/long/long/long/long/path/254B'
$ SHORT_LINK='/tmp/short'
$ mkdir -p "${LONG_PATH}"
$ ln -s "${LONG_PATH}" "${SHORT_LINK}"
$ node -e "fs.realpathSync.native('${SHORT_LINK}/file-not-exist')"
node(60274,0x10eabedc0) malloc: Incorrect checksum for freed object 0x104805aa0: probably modified after being freed.
Corrupt value: 0x7473697865
node(60274,0x10eabedc0) malloc: *** set a breakpoint in malloc_error_break to debug
Abort trap: 6

macOS crash report:
Application Specific Information:
abort() called
node(96859,0x105cd6dc0) malloc: Incorrect checksum for freed object 0x102b153d8: probably modified after being freed.
Corrupt value: 0x707865

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        	0x00007fff6a2b433a __pthread_kill + 10
1   libsystem_pthread.dylib       	0x00007fff6a370e60 pthread_kill + 430
2   libsystem_c.dylib             	0x00007fff6a23b808 abort + 120
3   libsystem_malloc.dylib        	0x00007fff6a33150b malloc_vreport + 548
4   libsystem_malloc.dylib        	0x00007fff6a342d27 malloc_zone_error + 183
5   libsystem_malloc.dylib        	0x00007fff6a329081 tiny_free_list_remove_ptr + 690
6   libsystem_malloc.dylib        	0x00007fff6a328279 tiny_free_no_lock + 1018
7   libsystem_malloc.dylib        	0x00007fff6a327d8b free_tiny + 459
8   node                          	0x0000000100892240 uv__free + 27
9   node                          	0x0000000100896c58 uv__fs_work + 260
10  node                          	0x00000001008991d2 uv_fs_realpath + 191
11  node                          	0x000000010008bd0c node::fs::RealPath(v8::FunctionCallbackInfo<v8::Value> const&) + 759

The apparent cause for this is that when the file doesn't exist, pathconf   will fail with ENOENT and uv_fs_realpath will fallback to _POSIX_PATH_MAX (256 on darwin), and allocates 257 bytes for realpath, but the realpath is longer than that.

Thanks for the bug report. It's caused by a regrettable misuse of _POSIX_PATH_MAX. #2966 should fix it.


fix: fix memory issue in stat query

Category

[ ] New feature
[x] Bug fix
[ ] Improvement
[ ] Refactor
[ ] etc

Description

fix memory issue in stat query

tageet=target looks like typo


pod new version is 1.3.0 ,  The latest version is 1.3.1

pod 'GZIP', '~> 1.3.0'

Sorry about that - the pod is now pushed.


Improve by detecting the statement end position

debugprint now insert in next line, but one expression or statement may be across multiple lines like:
let a = b
   .set_x(1)
   .set_y(1);

in this case debug a will give wrong result

@GopherJ I did consider this in issue #74, which I closed as being too complex to implement given all of the different languages debugprint supports - debugprint is meant to be a lightweight tool.
If someone was willing to invest the time to create an extensible language-by-language mechanism that supports doing something like this, maybe with support for a few of the popular languages (lua? python? typescript?) I'd certainly discuss adding it. But right now I don't think there's return on investment in adding it. Almost always inserting lines only where they are appropriate and/or moving them with syntactically incorrect is not difficult for an experienced developer.


Create aioelasticsearch.exceptions

from elasticsearch.exceptions import *
place correct __ALL__
use in __init__.py and all internal modules import from .exceptions

https://github.com/wikibusiness/aioelasticsearch/pull/14


Use regular pods for reply service

Use regular pods for reply service
Have a trigger for each pod

cc @pierDipi


Rename cupy.util submodule to cupy._util

Rel #3420.
This PR renames cupy.util submodule to cupy._util to indicate it is CuPy's private submodule and not intended to be used by users.

./cupy/cuda/compiler.py:10:1: F401 'cupy' imported but unused

Jenkins, test this please

Jenkins CI test (for commit 50cbf5cf23b6c719f547bd938659c6e6276c5e76, target branch master) failed with status FAILURE.

Jenkins, test this please

Jenkins CI test (for commit f66a58df601468af77711e5447212fec524e31c9, target branch master) succeeded!


Inherit Linux semantics for fd_pwrite with O_APPEND

This commit updates the implementation of fd_pwrite in WASI to match Linux semantics for an under-specified corner of WASI. Specifically if fd_pwrite is used the offset specified is ignored if the file is opened in append mode and the bytes are instead appended.
This commit additionally refactors fd_write and fd_pwrite to have basically the same code with only a minor branch internally when the final write is being performed to help deduplicate more logic.
Closes #8817

Redirecting to @pchickey

CI turned up an interesting phenomena which makes sense in retrospect. With wasi-common the behavior is subject to whatever the platform OS provides which makes Linux the odd-one-out. Papering over OS differences is easy enough in wasmtime-wasi but is not trivial in wasi-common.
@pchickey how do you feel about sticking with these semantics and just ignoring the whole test in wasi-common? Alternatives could include not landing this in Wasmtime and taking it up in an issue with WASI and/or adding more stuff to wasi-common.

I think it is fine to just leave this bug in wasi-common and ignore the test - I don't think there is much value in bringing bug fixes for corner cases like this, if users need the fix the real question is why they havent upgraded to wasmtime-wasi.


change user agent. Won't be blocked ;-)

We could provide some field descriptions and a proper .gitignore I guess. These .DS_Store files are awful.


Wanna add a HEX Color Project in JS

Wanna to make a Hex Color Generator

I wanna work on this issue #757.Please assign me this one


fix: check DiagnosticArray length

Types of PR

[x] Bugfix

Description

Dealing with IndexError issues

How to review this PR
Others

The CI failure is happening when I put in the changes to the PERCEPTION.
The PR below will correct the problem.
https://github.com/tier4/driving_log_replayer/pull/494

I rebased the branch and force pushed.
I'll check CI test pass. Then I'll merge


Highlighting woes

This behavior can be seen in the examples in the README. Is there a workaround for getting syntax highlighting to work for things like @param with DocBlockr?
This seems like one of the most important features, yet I constantly find myself looking grey walls of text like this, even when initializing the block using DocBlockr:

Atom 1.16.0 x64 + DocBlockr 0.10.3
I have a short list of 22 community packages installed. If it would be valuable to dump them here I'm happy to do so. Meanwhile I'm upgrading to Atom 1.17.0 to see if the issue persists.

Looks like upgrading to 1.17.x did the trick! 🌮

WRT @exception not being highlighted, I simply changed to @throws. And for the return value I updated to {Promise<Object>[]} which feels more correct. 🍕 🍕

The highlighting in doc commends is not defined by docblockr, but by the individual language packages.
In your case this would be atom/language-javascript.
Perhaps open an issue for your @exception vs @throws problem there.

No shit? Fooled me. Thanks for the info.


Included pdf parsing and error handling

ChangeLog:

Added pdf to text conversion
Added processing of text before inference
Added error messages/handling for both text/pdf options
Added inference call and returns output to frontend

Requirements:

Frontend must pass files in the request under the key 'file'
Frontend must pass text in the request under the key 'text'
Frontend calls the proper URL (there is one for each)

TODO:

[Optional] Text pre-processing can be further enhanced

Testing:

Used Postman to send text and files under both URLs to the server

Closes #6
Closes #8

LGTM


Fill and submit form in jest test

Anyone know how to properly simulate filling form inputs, then submit the form and checking that the onValidSubmit method has been properly called with the expected values, using jest and enzyme ?
Have been digging in the code for half a day,  but couldn't figure this on. Here's a test I'd expect to work:
describe("EmailLoginForm", () => {
  const mockStore = configureStore();

  const initialState = {
    firebase: {
      login: jest.fn((email, password) => Promise.resolve()),
    },
  };
  const initialContext = {
    store: mockStore(),
  };
  // dive in Formsy
  const wrapper = shallow(<EmailLoginForm {...initialState} />, {
    context: initialContext,
  }).dive();

  it("should render properly", () => {
    expect(wrapper).toMatchSnapshot();
  });

  it("can trigger a login action", () => {
    const form = wrapper.find("Formsy");
    form.simulate("change", {email<EMAIL_ADDRESS>password: "password"}, true);
    form.find(".submit-btn").simulate("click");
    expect(initialState.firebase.login).toHaveBeenCalledWith(
<EMAIL_ADDRESS>      "password",
    );
  });

Using a regular formsy form behind:
          <Formsy
            name="login_form"
            onValidSubmit={this.doSubmit}
            onValid={enableButton}
            onInvalid={disableButton}
          >
            <Input
              type="text"
              name="email"
              validations="isEmail"
              required
            />
            <Input
              type="password"
              name="password"
              required
            />
            <FlatButton
              type="submit"
              className="submit-btn login-submit"
              disabled={!canSubmit}
              secondary
            />
          </Formsy>

I understand that enzyme simulate("change") (doc) method will call the element's related onChange method, which Formsy implements. Since formsy  onChange expects 2 variables currentValues and isChanged, I passed them to the simulate method.
If overriding the onChange method in my component, I can see that the function is properly called. That confirms the fact that my simulate call is done properly.
Yet, my doSubmit method never gets called on onValidSubmit (or onSubmit for that matter). When debugging my elements, the inputs values stay undefined, hence they never got updated.
Any help will really be appreciated
Cordially

@christianalfoni looking forward to your reply :)

Hi, this repo has moved to https://github.com/formsy/formsy-react - can you recreate your issue there please.

[ ] oi


Query - more precise description.

A data query is performed with the help of a query object, which is a symbolic...

Fixed via #177


Sensor: use icons that better match a 3D-printer

Small update to use icons that better match a 3D-printer:

Thanks a lot @tehmaze


Status{statusCode=DEVELOPER_ERROR, resolution=null} this error occur when doing google sign in

create a project on firebase then authentication on but this error occur
Status{statusCode=DEVELOPER_ERROR, resolution=null}
i have already done firebase authentication and also check my SHA1 key but result is same

Hi @jatinbsa ! Thank  you for interest in our project.
Actually, many factors could be the cause of this error. Please check the app package (it should be different from com.rozdoum.socialcomponents) and google json file.
I believe, if you follow this instruction,  you will achieve success.


Cannot send requests via secure connection

Hi,
I am trying to use this plugin to send a GRPC request via Jmeter. I have imported the trusted keys into my Jmeter key store and can see them loading in the debug output - however whenever I try and run the request I see the following error.
DEBUG i.n.h.s.ReferenceCountedOpenSslEngine: SSL_read failed with 1: OpenSSL error: 268436496 error:10000410:SSL routines:OPENSSL_internal:SSLV3_ALERT_HANDSHAKE_FAILURE
The same GRPC request works in a standalone application using the same keys used to send single requests. I only seem to have this error while sending requests from this plug in.
Do you have any suggestions on the cause of this issue ? Do I need to import certificates a different way compared to normal Jmeter certificate locations ?

Hi,
Found almost the same issue. Requests from jmeter-grpc-request plugin fails with this in debug logs:
2022-06-08 15:17:07,969 DEBUG v.z.b.c.g.ChannelFactory: Create SslContext with NPN_AND_ALPN 2022-06-08 15:17:07,974 DEBUG o.a.j.t.p.AbstractProperty: Running version, executing function 2022-06-08 15:17:08,151 DEBUG i.n.h.s.u.InsecureTrustManagerFactory: Accepting a server certificate: CN=server.address 2022-06-08 15:17:08,152 DEBUG i.n.h.s.SslHandler: [id: 0x3d46fc58, L:/<IP_ADDRESS>:49389 - R:mrc.server.address/<IP_ADDRESS>:443] HANDSHAKEN: protocol:TLSv1.3 cipher suite:TLS_AES_128_GCM_SHA256 2022-06-08 15:17:08,152 DEBUG i.g.n.NettyClientHandler: [id: 0x3d46fc58, L:/<IP_ADDRESS>:49389 - R:mrc.server.address/<IP_ADDRESS>:443] OUTBOUND SETTINGS: ack=false settings={ENABLE_PUSH=0, MAX_CONCURRENT_STREAMS=0, INITIAL_WINDOW_SIZE=1048576, MAX_HEADER_LIST_SIZE=8192} 2022-06-08 15:17:08,152 DEBUG i.g.n.NettyClientHandler: [id: 0x3d46fc58, L:/<IP_ADDRESS>:49389 - R:mrc.server.address/<IP_ADDRESS>:443] OUTBOUND WINDOW_UPDATE: streamId=0 windowSizeIncrement=983041 2022-06-08 15:17:08,173 DEBUG i.n.h.s.ReferenceCountedOpenSslEngine: SSL_read failed with 1: OpenSSL error: 268436572 error:1000045c:SSL routines:OPENSSL_internal:TLSV1_ALERT_CERTIFICATE_REQUIRED 2022-06-08 15:17:08,175 DEBUG i.g.n.NettyClientHandler: [id: 0x3d46fc58, L:/<IP_ADDRESS>:49389 ! R:mrc.server.address/<IP_ADDRESS>:443] OUTBOUND GO_AWAY: lastStreamId=0 errorCode=2 length=105 bytes=6a617661782e6e65742e73736c2e53534c457863657074696f6e3a206572726f723a31303030303435633a53534c20726f7574696e65733a4f50454e53534c5f... 2022-06-08 15:17:08,176 DEBUG i.n.h.c.h.Http2ConnectionHandler: [id: 0x3d46fc58, L:/<IP_ADDRESS>:49389 ! R:mrc.server.address/<IP_ADDRESS>:443] Sending GOAWAY failed: lastStreamId '0', errorCode '2', debugData ''. Forcing shutdown of the connection. javax.net.ssl.SSLException: SSLEngine closed already
In the result it shows:
Exception: io.grpc.StatusRuntimeException: UNAVAILABLE: ssl exception. []
The same requests with the same certificates works good in GRPC GUI tool.
I added certificates in pkcs12 format to Jmeter keystore in system.properties file. Request to the same server with HTTP work well - server accepts the certificate.

This issue is stale because it has been open for 30 days with no activity.

This issue was closed because it has been inactive for 14 days since being marked as stale.


is summary plot only for classification?

Thank you for this amazing work. Just wondering, I want to identify variable importance using the summary plot. But my model is a tree-based regressor. I am not sure if I understand the paper correctly, I found all examples calculating shap values are all classifications. Could you please help clarify this, can this be used in regression? Thank you so much!

I've used shap and summary plot for the house list price problem before, which is a regression, and the explanations work just fine, and adjust to what I would expect from a logical standpoint. For example, construction area, distance to certain places of interest, and house geographical sector were all top features. I don't have the plot at hand, but a mini app that uses an XGBoost model for house list price prediction (at least in my city), is available in my profile, albeit with some fixes that I need to do for it.
From what I've understood, the shapley values for each feature is the same as a weight or coefficient, like in regression. These weights are then added, including the intercept or bias, then the sigmoid function is applied to the result of the sum. The result of the sigmoid function is the prediction that the original model gave, which is a probability between 0 and 1. For regression models, the process is the same, except that the sigmoid step is skipped, since the output isn't between 0 and 1, but continuous.
@slundberg  Can give you better details though, so you should wait for his output.

Thank you @JuanCorp, I think you are right. Even for classification the log odds needs to be computed in order to find the probability. The syntax I tried is referred to the classification example:
shap_values = shap.KernelExplainer(randomforest.predict, X_train).shap_values(X_test)
shap.summary_plot(shap_values, X_test)
is this the same as yours? at least now I can get the shap values.
@slundberg  Would you mind to clarify the shap_values in regressions? If it is already mentioned in your paper, please let me know, I can check that! thank you.

Sorry for asking again, I sometimes have runtime error when I used different number of samples in my X_test (sometimes is ok, sometimes if I only use 100 sample of the test, this error occurs),
Exception in thread Thread-15
RuntimeError: Set changed size during iteration
Could you help me with this? Thank you!

@jayden526 SHAP values work well with regressions, in fact the Boston housing example in the read-me is a least squares regression. The SHAP values are in the same units as the model output (for tree SHAP in XGBoost this is before the link function (such as a logistic). So if you are predicting dollars, then the units of the SHAP values will be in dollars and will sum to the output of the model.
As for the error, if there is a simple example of how you got it, please post it and I'll fix it.
FYI...If you are using a tree model I would suggest using XGBoost and getting the exact shap values vs using the model agnostic Kernel SHAP on scikit.

@slundberg Thank you so much! I will definitely try with Xgboost to see whether it works for me.

sounds good

@slundberg Hi, thanks for the great package! I am not getting how to use my own dataset with shap? What is the use of *shap.dataset and how can I use my own datasets in the form of (X, y) with SHAP? Thanks :)

Do you have a model and a dataset or just a dataset representing the output of the model? Perhaps clarifying what doesn't make sense about the examples in the README would be helpful.


Consider moving to CommonMark

Sounds like a plan re using our version :+1:
That's fair - I think if it were me, I'd potentially be using this OpenAPI description with different tools (i.e. it may go onto the API Catalogue or other internal/external tooling, such as rendering inside tools like JIRA, or an IDE) and I'd be expecting a consistent formatting across all of those.
It's unlikely that many users will be affected, but the reason CommonMark became a thing is because so many Markdown flavours are inconsistent, so it's possible that people will be affected by quirks that RedCarpet has.
I agree that it'd be odd to write a doc page that doesn't render the same as the API docs, and to that I wonder if maybe we should look at using CommonMark everywhere?

Originally posted by @jamietanna in https://github.com/alphagov/tech-docs-gem/issues/281#issuecomment-966234478
Notes:

[ ] GitHub previews won't necessarily match the site's view of content, so may make it less easy for folks just reviewing through GitHub
[ ] Would require a SemVer major bump, as it would introduce chance of breakage, unless made opt-in

This would be useful for the Learn to Code repo, which has an issue because Redacarpet doesn't support Markdown in HTML in the same way CommonMark does:
https://github.com/alphagov/learn-to-code/issues/56


coalesce(1).saveAsTextfile() takes forever?

hi I am trying to save many partitions of Dataframe into one CSV file and it take forever for large data sets of around 5-6 GB.
sourceFrame.coalesce(1).write().format("com.databricks.spark.csv").option("gzip").save("/path/hadoop")
For small data above code works well but for large data it hangs forever does not move on because of only one partitions has to shuffle data of GBs please help me

This isn't an issue with spark-csv. Running coalesce(1) puts all data onto 1 partition on 1 node, which means that 1 node will be performing all of this work. This is essentially going to produce the same speeds as if your driver was running the entire file in a FileStream object.
What you're looking for is FileUtil.copyMerge from the Hadoop API. This will merge hadoop files into a single file:
https://hadoop.apache.org/docs/stable/api/org/apache/hadoop/fs/FileUtil.html#copyMerge(org.apache.hadoop.fs.FileSystem, org.apache.hadoop.fs.Path, org.apache.hadoop.fs.FileSystem, org.apache.hadoop.fs.Path, boolean, org.apache.hadoop.conf.Configuration, java.lang.String)

Save problem here, I had the following code hanging forever:
data.coalesce(1).write.option("header", "true").csv("s3://path/file.csv")

I solved it with:
// store data to disk
import org.apache.spark.storage.StorageLevel
val persistedData = data.persist(StorageLevel.MEMORY_AND_DISK_SER)
// force evaluation
persistedData.count
// write data
persistedData.coalesce(1).write.option("header", "true").csv("s3://path/file.csv")

Have you tried without coalese(1) normal hadoop write and then when downloading from hadoop just use hdfs dfs -getmerge hdfs-dir-path local-file-path to write hadoop directory parts to one local disk file. This avoids collecting big files to worker memory.

I’m also facing same issue, I’m using PySpark APIs. I tried suggested approach in above comments but no luck.


Revert "Configure cloud provider"

Reverts krnepuane/github-actions-continuous-delivery-azure#2

closed.

closed.


map.removeLayer() seems to clear all event listeners of the map

When I setup my map, I add listeners for the click and mousemove events. Some time later, layers (in this case markers and polylines) get added and removed. Once a layer is removed, the map doesn't send any more events to my click listener, the mousemove listener however still gets the event.
When I register the click listener again, it will resume sending events, so a workaround for me is to re-add all my listener after I removed layers.

Can you setup a minimal test case to reproduce the issue: http://playground-leaflet.rhcloud.com/ ?

I'm using Mapbox 2.2.2, but since the bug is in the leaflet API, I reported this here. My test case uses only the latest leaflet and there it works without any issues.
http://playground-leaflet.rhcloud.com/dig/2/edit?html,output

@narrowtux If I replace the Leaflet 0.7.x library from your playground example and select MapboxJS 2.2.2 from the drop-down menu, the bug is still not reproducible.

Seems like something else is wrong. I'm using http://inkblot.io/angular-mapbox/ to be able to use mapbox in my Angular project, and there's probably a bug there then.

Update to this: I changed my project around a bit so I am not using angular-mapbox in any way, just the normal Mapbox 2.2.2 Javascript library. The bug still persists, weirdly only for the click event.

I'll try to make a working example of the bug later.

Hey, just wanted to give a specific example of this, because I discovered this behavior as well. Like narrowtux, this event only manifested itself with the click event.
If you look at the code below, it nukes the click events added in the onEachFeature property, because I remove a layer after adding the click listener
MapDataService.getGeodocsData(MapService.getDataCategory())
                .then(function(geojson) {
                    var newGeoJsonLayer = L.geoJson(geojson, {
                            onEachFeature: featureFunction
                        }),
                        oldGeoJsonLayer = vm.geoJsonLayer;

                    // this also calculates color breaks, so it must be called before style is set
                    MapDataService.calculateLabels(MapService.getDataCategory());

                    newGeoJsonLayer.setStyle(styleFunction);

                    vm.map.addLayer(newGeoJsonLayer);

                    vm.geoJsonLayer = newGeoJsonLayer;

                    if(vm.map.hasLayer(oldGeoJsonLayer)) {
                        vm.map.removeLayer(oldGeoJsonLayer);
                        oldGeoJsonLayer = null;
                    }
                });
        }

function featureFunction(feature, layer) {
            layer.on({
                click       : function(e) {
                    showPopup(e);
                },
                mouseover   : function (e) {
                    highlightLayer(e.target);
                },
                mouseout    : function (e) {
                    revertStyle(e.target);
                }
            });
        }

However, if I reverse the order like so:
MapDataService.getGeodocsData(MapService.getDataCategory())
                .then(function(geojson) {
                    var newGeoJsonLayer = L.geoJson(geojson, {
                            onEachFeature: featureFunction
                        }),
                        oldGeoJsonLayer = vm.geoJsonLayer;

                    // this also calculates color breaks, so it must be called before style is set
                    MapDataService.calculateLabels(MapService.getDataCategory());

                    newGeoJsonLayer.setStyle(styleFunction);

                    if(vm.map.hasLayer(oldGeoJsonLayer)) {
                        vm.map.removeLayer(oldGeoJsonLayer);
                        oldGeoJsonLayer = null;
                    }

                    vm.map.addLayer(newGeoJsonLayer);

                    vm.geoJsonLayer = newGeoJsonLayer;
                });
        }

The click events register fine. This isn't a real, breaking issue for me, because I can just reverse the order. For others however, this could be a breaking bug.

I am having the same issue here... Sadly I can't just reverse the order.
I am removing data when the data is too far from the screen bounds. When I do all the other click events on my other layers stops working...
I tried to do a simple fiddle, but since I do not know the cause it's really hard to replicate the issue. It's really only the click event. My mouseover / mouseout events are still working fine...
Some help would really be appreciated.


Illegal instruction in jctx_setjmp(x)

When I run udepot-test in bin/, I got Illegal instruction in jctx_setjmp(x); if I set #define jctx_longjmp(x) longjmp(&(x)->ctx_, 1), I got segentation fault instead. My GCC version is 11.3.0.

I haven't looked at this for a while, and the project is not really being maintained.
Unfortunately GCC disallowed using __builtin_longjmp and __builtin_setjmp since after GCC 7.4 or so.
But you should be able to build in a docker container using the supplied Dockerfile. If you statically build then you should be able to use the resulting binary outside the container.
Another thing that could work (but I did not try it), is to use the longjmp and setjmp implementations shared at https://nullprogram.com/blog/2023/02/12/.

Yes, this sounds like a kernel mismatch issue while building dpdk.
io_uring should perform well too, but depending on your setup spdk might be faster.


File already exists error

I found a bug on inviso.cc that I cannot save an export.  I deleted some of the cones and then I could export a file.

@codyjroberts also I found that load/save doesn't work on Safari (OSX) and no save on Firefox (OSX). I looked into the console but I see no error related to it. Chrome works fine but there are some glitch on the sound so we prefer the other browsers.

@micuat the file already exists error should be fixed now at inviso.cc. Can you check on your end? Export sometimes takes a little bit of time (or might require a second try) but it at least shouldn't throw an error now.

@anilcamci yep, works fine! thanks!


docs: Add missing any_of.signatures to RFC 3

Description
RFC 3 for policy signing is missing some fields on the examples.
Related to: https://github.com/kubewarden/policy-server/issues/142

Rebased main.


Add AvgPool2d as a layer

Hmm, why? This is in yolo and isn't used.

I wanted to use it for resnet. Is there a better place to store this?

Why is this a class at all? It has no state

It matches the implementation in PyTorch, but I agree that it doesn't need to be a class

One of the reasons tinygrad is better than PyTorch :)
Stateless classes are dumb.

Understood. Since MaxPool2d also has no state, I suggest to remove it from yolo.

That yolo code is quite bloated tbh


Incorrect implicit underlying type for enums

Brief Description
When a header includes an enum with an implicit value representation such as the following:
enum myEnum {
    myVal = 0xffffffff;
};

The BuiltinType of the generated Enumeration declaration is erroneously int and the correpsonding item is incorrect (it's (ulong)(int)0xffffffff).
After some digging, it appears the code responsible for setting the type is:
https://github.com/mono/CppSharp/blob/166e45e9af4c0d40e17ac80a021197bb44a14751/src/CppParser/Parser.cpp#L2990-L2994
int is returned by getIntegerType and the items are being incorrectly represented as above.
It appears EnumDecl is a type directly provided by clang, so this appears to be a bug in clang?
Explicitly specifying the value representation makes everything work as expected.
This is especially odd considering that the clang compiler correctly increases the underlying type's size (and uses unsigned int unless negative values are present):
https://godbolt.org/z/K8neMYrYT
OS: Windows 10
Target: MSVC

The erroneous behavior is still the standard in the latest preleases for VS as far as I can see. 17.4 only introduced the compiler flag to fix it and the patch notes explicitly mention it being off by default.
The TargetTriple approach didn't prove fruitful (I'm getting errors about STL types (e.g. size_t) being redefined differently). Ultimately it would have likely required parsing MSVC headers in non-MSVC mode and that doesn't seem like a feasible path.
I'm currently looking into getting support for /Zc:enumTypes in LLVM: https://discourse.llvm.org/t/implicit-underlying-enum-type-with-msvc-compatibility-zc-enumtypes-flag/83775.
I assume this might take a bit longer with holidays coming up and such, but I'll report back here once that has been accomplished.
Fortunately my use case (currently working on a wrapper for assimp) does not require this, as no value is large enough to cause information to be lost, thus it's sufficient to simply manually set the enum types correctly as a workaround.


Minimap Button

I've found some shaky instructions on how to do this, and I'd love to not have to include a 100s-lines-long library just for this one feature, but I'm sure it can be done in less! :)

Added with a5faafd


Missing "try {" on line 11 of setFossils.js

exactly what the title says lol

https://github.com/Minesraft2/Blooket-Cheats/


Remove broken anyOf implementation

I'm not sure what is correct, this stuff is complex

I'm not sure what is correct, this stuff is complex


contracts/test/utils/VM.sol: typo in annotation

Summary
stopPrank()'s annotation cites prankStart() at the end:
https://github.com/ourzora/v3/blob/ef8807fec73bd2d77ac13beae55b70fa0b8db4bd/contracts/test/utils/VM.sol#L42-L43
However, prankStart() doesn't exist beyond this citation: startPrank() does! 😉
https://github.com/ourzora/v3/blob/ef8807fec73bd2d77ac13beae55b70fa0b8db4bd/contracts/test/utils/VM.sol#L39-L40

Cut https://github.com/ourzora/v3/pull/134 to resolve this!


Add Awesome Biomarkers List

Hi, I created this list awhile back but forgot to contribute it back to the central list. The list is a collection of info on biomarkers and blood tests. Still a work in progress but key aspects are there now. Thanks for having me on the awesome list family!
https://github.com/markwk/awesome-biomarkers
The objective of the list is to help people to learn more about blood testing, biomarkers and tech and services to help quantify (and improve) your health!
I went through the requirements and added a TOC. I think everything else is covered. Ping me back if I missed something. Thanks!

I like the purpose behind this list a lot. I do think you should look over the requirements again though, it looks like some things are missing and there are a lot of awesome-lint errors. I think most of them should be pretty easy to fix, like some of them are from using "*" instead of "-" for formatting lists.

Thanks for taking a look @CompSciLauren and hat tip on awesome-linter since I had missed that. I correct everything except some odd error on the TOC that doesn't track with anything. Hopefully it's done or at least closer.

So that error is happening because you have nested sections but the TOC doesn't show them as being nested.
The preferred solution according to the awesome list requirements is to only have main sections and not include any subsections.
So you currently have subsections with three hashtags like this:
### Complete Blood Count Biomarkers

You need to remove a hashtag to make them not be subsections:
## Complete Blood Count Biomarkers

If you think it's necessary to have subsections, then those sections need to look nested in the TOC and you need to make sure to only include one level of nested-sections at most (one of your sections doesn't comply with this).

Ok. This list works best with multiple subsections so I'll leave that and wait for the lead maintainer to make the final call. Thanks. Appreciate the heads up.

Thanks for making an Awesome list! 🙌
It looks like you didn't read the guidelines closely enough. I noticed multiple things that are not followed. Try going through the list point for point to ensure you follow it. I spent a lot of time creating the guidelines so I wouldn't have to comment on common mistakes, and rather spend my time improving Awesome.

Awesome Lint returns:
  readme.md:11:1
  ✖  11:1  ToC item "Complete Blood Count Biomarkers" does not match corresponding heading "Blood Testing Companies"  remark-lint:awesome/toc

  1 error

However, I'm not sure what does it mean in this context.
Although guideline encourages us to make ToC as flat as possible, in this case I would use nested list with one indentation level or remove all the sublevels from the ToC. In my opinion, it'd be clearer :smiley:

@markwk Ping

@sindresorhus I'm not sure what I'm missing besides 🦄 unicorn

The PR title is not correct. Please read the guidelines. They are carefully written so I don't have to point out obvious stuff.

The item title is Biomarkers and Blood Tests, while the heading in the list is Awesome Biomarkers, Blood Tests and Health Indicators. The heading in the list should be Awesome Biomarkers and Blood Tests.

I think the Learn more about blood testing, biomarkers and tech and services to help quantify (and improve) your health! could be more comprehensive.

It's weird to suddenly have a subheading called Awesome List on Biomarkers here: https://github.com/markwk/awesome-biomarkers#awesome-list-on-biomarkers

Bump


Skip installing docs when installing Ruby

I noticed that our Ruby installs included generating docs, which takes
~30 seconds:
https://github.com/dependabot/dependabot-core/runs/7646741836?check_suite_focus=true#step:3:5996
But we don't need docs in our docker images--humans can always look them
up online.
So skip installing docs and cut 30s off our CI times.
Thanks to @deivid-rodriguez for the tip on how to pass the arg through
ruby-install to the underlying ruby.
Fix #5475

I verified the new build doesn't include building the docs. Compare:

With docs: https://github.com/dependabot/dependabot-core/runs/7646741836?check_suite_focus=true#step:3:5996
Without docs: https://github.com/dependabot/dependabot-core/runs/7677091557?check_suite_focus=true#step:3:4000


Properties don't work on Chrome

I test on v48 but not before

Seem to work fine to me. Can you provide a specific example of a property not working?

Have you an inline exemple ? Thanks

My tests are here: http://tests.caniuse.com/?feat=background-img-opts

OK, thanks, I don't see what I talk about.
Here an exemple works on FF and not in Chrome :
<select id="companytype" class="selecticon" name="companytype">
<option value="all">--- All Types ---</option>
<option value="1" style="background: transparent url(farm.png) no-repeat 0 0;">Farm</option>
<option value="3" style="background: transparent url(packhouse.png) no-repeat 0 0;">Packhouse</option>

Ah, so those are being applied to <option> elements in a <select> list. I believe there's no defined way for browsers to apply styles on such elements, so that doesn't need to be considered partial support.

The code I pasted works fine on Firefox !


Multicue groundtruth file for edge detection result evaluation

Hello, thanks for your kind sharing and great work.
I currently intend to evaluate my edge detection model's performance on Multicue dataset, but I could not obtain the groundtruth file of it, could you please give me any advice on it?

I upload the ground truth below which includes image format and mat format.
gt.zip

Thanks SOOOO much !

I upload the ground truth below which includes image format and mat format.
gt.zip

Sorry for the disturbance again, I noticed the zipped files you provided only contain groundtruth file of 20 images, I guess it may be a random split in your experiment.
For the reason that, for multicue, it is better to train in 3 random splits, could you please offer me the groundtruth files of all 100 images if it is convenience to you?

link：https://pan.baidu.com/s/1Yx9CYllZtYtu5k-FahzpbA
code：k817
I have stored the gt on the above link, you can download it from it.

link：https://pan.baidu.com/s/1Yx9CYllZtYtu5k-FahzpbA
code：k817
I have stored the gt on the above link, you can download it from it.

Cheers man! That's what I actually need. Thanks for everything.


It's version 1.5.2 but it doesn't show up when I install mov is there a way?

It's version 1.5.2 but it doesn't show up when I install mov is there a way?

need 1.6 version


Add EventSource/EventCounter tracing and metrics for Session

Some events listed below. The goal is to add events that will help users solve problems so if these aren't going to do that job, feel free to suggest/discuss others!

Microsoft-AspNetCore-Session EventSource

SessionsCreated - Counts sessions created
SessionsLoaded - Counts the number of times a session is loaded from the provider (this happens on each request for a session)
SessionsCommitted - Counts the number of times a session is commited to the provider (again, happens on each request)
We can't track abandoned or timed-out sessions any more as they are handled by caching now and we don't provide a way to explicitly abandon a session. We could detect "empty" sessions (with no data) but such a session could always be added to again later.

See https://gist.github.com/anurse/af1859663ac91c6cf69c820cebe92303 for some guidance on adding EventSources and EventCounters to ASP.NET projects.

This issue was moved to aspnet/Home#2396


core-image-pelux: add git to dev images

Signed-off-by: Oleksandr Kravchuk<EMAIL_ADDRESS>

This question should have been answered in the commit message, because people in the future will have it too.

The biggest reason for my skepticism is that we have been discussing that we want to make the images more lightweight and find what is included but not needed. If this is in fact needed for a specific use case, then that's one thing, but if this is just "would be nice to have" then I don't see any urgency and it can wait until a use case presents itself or at least until after the analysis of the image (an removal of unnecessary includes) is done.

Wait, so there was no discussion about it and it wasn't even attempted to be explained in the commit message? How in the world are people supposed to review something like that??

As a developer, don't you develop on your own machine, using the SDK to cross-compile, and then deploy the artifacts to the target and test. (Or bitbake the complete image and deploy)
Has the team defined what a dev-image mean? I would assume that it has the same content as the non-dev image but with libraries with debug symbols, gdb, valgrind and ssh deployed to target.
In the handbook it' stated: "Both PELUX images are available as -dev variants, which include some extra development and debugging tools. For some platforms, those images are also available as -update to generate update artifacts for the SOTA System."
Not so much, so perhaps there is a need to add more info about what a dev image is?
To summarize, I think there is a need to discuss this in the team before this pull request can be merged.

As a developer, don't you develop on your own machine, using the SDK to cross-compile, and then deploy the artifacts to the target and test. (Or bitbake the complete image and deploy)

I personally don't see the need to develop on the Pelux image. I would develop on a separate machine and then recompile. I guess if you just want a specific package added on your Pelux image you could use scp.

Has the team defined what a dev-image mean? I would assume that it has the same content as the non-dev image but with libraries with debug symbols, gdb, valgrind and ssh deployed to target.
In the handbook it' stated: "Both PELUX images are available as -dev variants, which include some extra development and debugging tools. For some platforms, those images are also available as -update to generate update artifacts for the SOTA System."
Not so much, so perhaps there is a need to add more info about what a dev image is?
To summarize, I think there is a need to discuss this in the team before this pull request can be merged.
I agree that this most likely needs to be defined so that the entire team is aware of the purpose and use cases of the different images.


Unpublish buildx-shim

Removing until we implement a buildx driver

This breaks depot/use-action in it's default configuration: https://github.com/depot/use-action/blob/main/action.yml#L27-L30 along with our build job with:
[2023-08-02T19:54:22.151Z] ERROR: Multiple platforms feature is currently not supported for docker driver. Please switch to a different driver (eg. "docker buildx create --use")

Is there a workaround until the proper buildx driver is out?

Hey @dylanratcliffe sorry for the disruption - PR #148 should implement a proper driver, we're hoping to have that released in the next day or so, I'll ping back here when it's live.


[Auto-generated] Update requirements.txt

Update requirements.txt
Automatically created PR from the ci_update_requirements.yml workflow.

Codecov Report

:exclamation: No coverage uploaded for pull request base (ci/dependabot-updates@39895f2). Click here to learn what that means.
Patch has no changes to coverable lines.

Additional details and impacted files
@@                   Coverage Diff                    @@
##             ci/dependabot-updates     #198   +/-   ##
========================================================
  Coverage                         ?   68.43%
========================================================
  Files                            ?       17
  Lines                            ?      491
  Branches                         ?        0
========================================================
  Hits                             ?      336
  Misses                           ?      155
  Partials                         ?        0

Flag
Coverage Δ

pytest
68.43% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


Workflow execution fails when the workflow name is more than 44 characters

Describe the bug

Workflow execution fails when the workflow name is more than 44 characters
Steps to reproduce

Create a workflow and name it with 63 characters.
Execute the workflow.

Result

Failed to execute and returned an error.

Check walrus logs.

2023-11-09T09:12:45.553Z	E	api	error requesting POST /v1/projects/486372827121844226/workflows/486524256461520898/run: 1 error occurred:
	* rpc error: code = InvalidArgument desc = workflow name "test-flow-with-loooooooooooooooooooooooooooooooooooooooong-name-486525113324273666" must not be more than 63 characters long (currently 82)

github.com/seal-io/walrus/pkg/apis/runtime.erroring
	github.com/seal-io/walrus/pkg/apis/runtime/middleware_error.go:45
github.com/gin-gonic/gin.(*Context).Next
	github.com/gin-gonic/gin@v1.9.1/context.go:174
github.com/seal-io/walrus/pkg/apis/runtime.recovering
	github.com/seal-io/walrus/pkg/apis/runtime/middleware_recovery.go:39
github.com/gin-gonic/gin.(*Context).Next
	github.com/gin-gonic/gin@v1.9.1/context.go:174
github.com/seal-io/walrus/pkg/apis/runtime.observing
	github.com/seal-io/walrus/pkg/apis/runtime/middleware_observation.go:89
github.com/gin-gonic/gin.(*Context).Next
	github.com/gin-gonic/gin@v1.9.1/context.go:174
github.com/gin-gonic/gin.(*Engine).handleHTTPRequest
	github.com/gin-gonic/gin@v1.9.1/gin.go:620
github.com/gin-gonic/gin.(*Engine).ServeHTTP
	github.com/gin-gonic/gin@v1.9.1/gin.go:576
github.com/seal-io/walrus/pkg/apis/runtime.(*Router).ServeHTTP
	github.com/seal-io/walrus/pkg/apis/runtime/router.go:191
net/http.serverHandler.ServeHTTP
	net/http/server.go:2947
net/http.initALPNRequest.ServeHTTP
	net/http/server.go:3556
net/http.(*http2serverConn).runHandler
	net/http/h2_bundle.go:5910
2023-11-09T09:12:45.553Z	D	api	500 | HTTP/2.0 |        0 B |      100 B |   12.675843ms |   <IP_ADDRESS> | POST    /v1/projects/486372827121844226/workflows/486524256461520898/run

Expected behavior

Environment

Walrus version: main 065ee92e55e14044fa0777be4c631f7082fadc0e
UI version: dev-81ad833

Additional context
Add any other context about the problem here.

Environment

Walrus version: v0.5.1

Test Result:
Workflow names are limited to 30 characters now.


Correct type validations

Dynamic nature of moving dotnet versions to hiera was broken by requiring enum of static version values. Validating as String allows for simple hiera additions to expand to newer dotnet versions.
Additionally documentation should be updated to reference appropriate new use cases and PR submitted to voxpupuli for release to forge.

Pull Request (PR) description

This Pull Request (PR) fixes the following issues

If you do not wish to maintain and contribute, I can send this PR to the project space. Since you did the work to get dotnet core support in place, I am sending to you first.


Bug : on August the 31st, on view=date, next month button goes to October

Hi there,
I've found the weirdest bug :

set the date to August the 31st (you can do this on Mac going to System Preferences -> Hour and Date -> First tab -> Manually set Date and Time)
go to the demo page https://rawgit.com/g00fy-/angular-datepicker/master/app/index.html
on the view=date component (3rd one from the top, left column) you see 2015 August
click next month
you will see 2015 October (instead of 2015 September)

What's weird is that if I set the date to September the 30th, the next month button will display October 2015. If I set the date to October the 31st, the next button will show ... December.
wat.
I have no idea why this happens. Looking at the source and Ctrl+F'ing "31" or "30" does not show results.
Do you guys reproduce this bug ?
Any ideas ?

Have you been able to look into this issue ? Thanks.

+1 i have the same issue ! Any idea?

This issue has been fixed in the latest version of the library. The demo no longer exhibits this problem.


Adjust method return for annotateVMH

Currently annotateVMH only returns the amount of annotated metabs.
https://github.com/Porthmeus/MeMoMe/blob/099518aa126b4e5d59fd59f14cf1ce32c9d02409/src/annotateVMH.py#L94
Jan also added annotated names and databases to the return. If would be good if the annoatteVMH function does this as well.
See here for an example:
https://github.com/Porthmeus/MeMoMe/blob/669b67cefe7ccfc1236a238d46d47f3f62418dfb/src/annotateBiGG.py#L53

@DafniGi Please see latest Version on the main branch. Return type chanded

See annotateVMH.py


[Feature Request] QR code scanner for IDs of (indoor) locations

Virologists point out that the virus appears to spread in over 40% of the infections caused by aerosols, which can remain in the air for up to several hours in closed rooms. I think it could be helpful to create a possibility for restaturants, hairdressers etc. to be part of the tracing process without using a Bluetooth device, e.g. with the help of QR codes.
Guests would scan the respective QR code when entering and leaving such a store and the app would rate the transmitted IDs as contacts. If it turns out that an employee has tested positive for Corona, the IDs would be uploaded to the backend server as infected and all guests who have been in this room in e.g. the past 2 weeks (or five days before the onset of symptoms) will be informed by the app.
Such a solution would require a server that provides IDs based on a public url for the participating shops / locations.

Thanks a lot for your proposal. In the initial version, the app scope will adhere to the scoping document.
But, of course, we welcome discussion and ideas around potential future functionality and leave this issue open for others to discuss and refine the idea.

We used QR Codes in a lot of projects.
It can be trolled by a simple photo :)
So you need somehow signed NFC stickers to gain a minimum of security.

You need a direct contact to NFC stickers (this creates a new hotspot!)
NFC can also be copied...

I see no possibility implementing this using customer cell phones.

The possibility of misuse with an insecure technology such as QR codes should of course be considered and evaluated. Perhaps this discussion will help developing a robust concept, possibly with the involvement of health authorities or 'Ordnungsämter' who regularly check the QR codes used.

Thank you @medienintegration. I second this. There are already a lot of 2nd thoughts and well-known Show-Stopper. You have one job, do it accordingly and stop mixing functions.Its very easy to understand:
With the mixing of functions the discrimination of non-App users increases.
It's also horrific how complexity is increased.
I also recall this prematurely closed and not understood issue (https://github.com/corona-warn-app/cwa-documentation/issues/23)
But of course I could miss the point, that this could be the strategy right from the beginning. To integrate as much as possible in order to nudge as many as possible.
Let me say this very clearly: This will not work!

@TomTeeJay

With the mixing of functions the discrimination of non-App users increases.
It's also horrific how complexity is increased.

On the one hand I agree that things should be kept simple and focused. On the other hand, this project has skipped design exploration and is taking an arbitrarily set approach. It should not surprise us that alternative approaches keep popping up in various forms. This project lacks a design rationale.

@medienintegration
Sorry, until the BLE approach is not proven to be ineffective/broken we cannot concentrate on different solutions. I have to close this issue. Feel free to re-open as soon as there is an indication the BLE approach does not work in your sketched environment. But I am pretty sure you have described a perfect setting for BLE contact tracing 😉
Malte

@MalteJ Could the idea of @medienintegration be implemented as a protocol extension based on BLE? Imagine a location participating in contact tracing with its own device(s). If an infected person has visited the location recently, this location becomes exposed and if locations are distinguishable from persons one could in this case notify secondary contacts.
I have not thought this through – some form of authentication and location-binding will probably be needed and one will have to analyze the privacy implications – but dismissing the entire idea without much discussion seems premature to me.

@MalteJ I understand that the focus should be on developing the core function. However, the point is not that the BLE approach is ineffective / broken, but that scenarios are conceivable that could save valuable time with the help of QR codes (or stationary devices). In other scenarios, the BLE approach would just not work (simple example: I am in the barber shop with 2 employees and another customer in one room - and I am the only one who has installed the app).
@sventuerpe Actually, stationary BLE devices were my first idea, but after a discussion with a friend, she had the idea with the QR codes, which I find much less problematic. As you mentioned, stationary devices would have to be authenticated. In addition, they should not leave the place, otherwise they would trigger a myriad of "contacts". But maybe someone has an idea for a working solution.

Another situation where the current approach fails, is a chef in a kitchen with access to the meal of a customer but behind a Bluetooth impenetrable barrier (metal kitchen walls, far distance, ...)


[AutoPR recoveryservicessiterecovery/resource-manager] chore: jsonfmt recoveryservicessiterecovery

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/6224

This PR has been merged into https://github.com/Azure/azure-sdk-for-js/pull/3704


added post method, as get was failing. Also did away with yeild, and …

…added random header.

Also added  multiple search terms etc

not for me, I'm getting a great response, merge or no merge, i'm happy :)
It's doing what I want.
On Wed, Jul 12, 2023 at 9:24 PM Nv7 @.***> wrote:

@.**** commented on this pull request.
In googlesearch/user_agents.py
https://github.com/Nv7-GitHub/googlesearch/pull/57#discussion_r1261688432
:

-_useragent_list = [

"""
return random.choice([
'Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:66.0) Gecko/20100101 Firefox/66.0',

We only kept the common user agents since having a bunch was causing some
issues.
—
Reply to this email directly, view it on GitHub
https://github.com/Nv7-GitHub/googlesearch/pull/57#pullrequestreview-1527178006,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIVZ7JABWDSROFYY4AAJXFDXP4BX5ANCNFSM6AAAAAAZYLMLWE
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
[image: created with MySignature.io]
https://mysignature.io/?utm_source=logo
Lewis Morris
M:<PHONE_NUMBER>5
E:  @.***
[image: created with MySignature.io] https://github.com/lewis-morris [image:
created with MySignature.io]
https://stackoverflow.com/users/3348264/lewis-morris

I'm getting 429 errors - Too many requests as well. I think I can add more user agents to resolve the issue, and this PR is exactly (and above) what I need. If this is not merged, I'll raise a PR to add more user agents only.

Worked for me when I was getting the same issue.
On Thu, Sep 21, 2023 at 7:22 PM Nguyen Minh Thai @.***>
wrote:

I'm getting 429 errors - Too many requests as well. I think I can add more
user agents to resolve the issue, and this PR is exactly (and above) what I
need. If this is not merged, I'll raise a PR to add more user agents only.
—
Reply to this email directly, view it on GitHub
https://github.com/Nv7-GitHub/googlesearch/pull/57#issuecomment-1730085118,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIVZ7JFQUL6SNA26GDFOENTX3SAU7ANCNFSM6AAAAAAZYLMLWE
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
[image: created with MySignature.io]
https://mysignature.io/?utm_source=logo
Lewis Morris
M:<PHONE_NUMBER>5
E:  @.***
[image: created with MySignature.io] https://github.com/lewis-morris [image:
created with MySignature.io]
https://stackoverflow.com/users/3348264/lewis-morris

You could have a use_additional_agents flag which might help.
On Fri, Sep 22, 2023 at 4:40 PM Lewis Morris @.***> wrote:

Worked for me when I was getting the same issue.
On Thu, Sep 21, 2023 at 7:22 PM Nguyen Minh Thai @.***>
wrote:

I'm getting 429 errors - Too many requests as well. I think I can add
more user agents to resolve the issue, and this PR is exactly (and above)
what I need. If this is not merged, I'll raise a PR to add more user agents
only.
—
Reply to this email directly, view it on GitHub
https://github.com/Nv7-GitHub/googlesearch/pull/57#issuecomment-1730085118,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIVZ7JFQUL6SNA26GDFOENTX3SAU7ANCNFSM6AAAAAAZYLMLWE
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
[image: created with MySignature.io]
https://mysignature.io/?utm_source=logo
Lewis Morris
M:<PHONE_NUMBER>5
E:  @.***
[image: created with MySignature.io] https://github.com/lewis-morris [image:
created with MySignature.io]
https://stackoverflow.com/users/3348264/lewis-morris

--
[image: created with MySignature.io]
https://mysignature.io/?utm_source=logo
Lewis Morris
M:<PHONE_NUMBER>5
E:  @.***
[image: created with MySignature.io] https://github.com/lewis-morris [image:
created with MySignature.io]
https://stackoverflow.com/users/3348264/lewis-morris


Improved plotting & docs

also added L1 metric for early stopping

Codecov Report

Merging #10 (0982919) into main (2adb125) will decrease coverage by 8.10%.
The diff coverage is 6.66%.

@@            Coverage Diff             @@
##             main      #10      +/-   ##
==========================================
- Coverage   51.68%   43.57%   -8.11%
==========================================
  Files           6        6
  Lines         238      280      +42
==========================================
- Hits          123      122       -1
- Misses        115      158      +43

Flag
Coverage Δ

unittests
43.57% <6.66%> (-8.11%)
:arrow_down:

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

Impacted Files
Coverage Δ

setup.py
0.00% <ø> (ø)

cbm/CBM.py
30.36% <6.66%> (-9.24%)
:arrow_down:

Continue to review full report at Codecov.

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


Mouse Cursor highlight and zoom

Here are a few features that I think was not able to find that worked well on windows.

Mouse cursor highlight
Highlight color can be changed and along with opacity and radius

Click ripple
A ripple that denotes a click, color can be changed

Magnify
The screen is magnified and shown in a little preview window

Scribble and draw
Draw shapes or scribble to highlight stuff

If you'd like to see this feature implemented, add a 👍 reaction to this post.

@prantikv
we don't track more than one request per issue.
Also, for each request we need a full user scenario with the explanation and the motivations for the feature request. There is a template when opening a feature request that lists those requirements.
Thanks.


Using Editor,   checkbox control: unable to set the text

Are you requesting a feature, reporting a bug or ask a question?
Facing this issue, while using editor. I'm setting text values for checkbox & click on 'Ok" but after coming on same dialog , I saw nothing is there for text.  ?
What is the current behavior?
What is the expected behavior?
How would you reproduce the current behavior (if this is a bug)?
Provide the test code and the tested page URL (if applicable)
Tested page URL:
Test code
your_code_here

Specify your

browser:
browser version:
surveyjs platform (angular or react or jquery or knockout or vue):
surveyjs version:

@lalitkhanna Unfortunately, I do not understand how to reproduce the problem :-(
Thank you,
Andrew


chore(sdk): Use a single unit test job in CircleCI

Description

Use a single job called "unit-tests-new" to run both SDK and non-SDK unit tests on Linux (non-"legacy" tests).
I didn't add an option to run unit tests on Mac, assuming that there is not much value in running unit tests on different systems and machines, but I can add it if we think it's still useful.
Testing
Running on CircleCI.

I would like to have the new test just be unit-tests (we ideally soon going to get rid of the legacy ones) and the new ones are actually the default.
I think it would be nice to have them running on mac as well (usually it shouldn't matter, but it is so fast i don't think it hurts)
Looks like the new tests running everything? i see reports and launch in there too...   (that's why it fails)
When you are ready with the tests let me know and we will update the required in github.

I would like to have the new test just be unit-tests (we ideally soon going to get rid of the legacy ones) and the new ones are actually the default.

Noted, I'll rename!

I think it would be nice to have them running on mac as well (usually it shouldn't matter, but it is so fast i don't think it hurts)

It's a bit ugly: on Mac, the python binary is called python3, and its only version is 3.11. I think I'd need to add steps that alias the python and pip binaries, and the python_version_major / python_version_minor parameters would be coupled to the mac executor version. But I can still try to add it.

Looks like the new tests running everything? i see reports and launch in there too...   (that's why it fails)

There are "-sdk-" and "-other-" jobs. The "-other-" jobs are failing, the "-sdk-" ones are succeeding.

I would like to have the new test just be unit-tests (we ideally soon going to get rid of the legacy ones) and the new ones are actually the default.

Noted, I'll rename!

I think it would be nice to have them running on mac as well (usually it shouldn't matter, but it is so fast i don't think it hurts)

It's a bit ugly: on Mac, the python binary is called python3, and its only version is 3.11. I think I'd need to add steps that alias the python and pip binaries, and the python_version_major / python_version_minor parameters would be coupled to the mac executor version. But I can still try to add it.

i think if you use tox it should use an env with the required python version is not the case?

Looks like the new tests running everything? i see reports and launch in there too...   (that's why it fails)

There are "-sdk-" and "-other-" jobs. The "-other-" jobs are failing, the "-sdk-" ones are succeeding.

ignore... i miss read the name of the test...

i think if you use tox it should use an env with the required python version is not the case?

tox doesn't install the Python version unfortunately, it expects it to be available in the system

i think if you use tox it should use an env with the required python version is not the case?

tox doesn't install the Python version unfortunately, it expects it to be available in the system

hmm... what do you think about installing the relevant python version in the mac executor?

total nit, but can we have the names of the test be something like:
unit-tests-3-{7,12}-{other,sdk}-{core,no-core} core/no-core you can modify, just true/false is not very clear what it refers to...

Improved test names
Added macOS unit tests
Removed separate "reports-py*" tox section, merging into the main testing section

Look at all those green jobs :)


Unable to package in Fedora

I wanted to package this project as a Fedora package.

First issue is that your project source bundles all its dependencies, that is unacceptable but can be fixed on our side by replacing dependencies with the system ones. It would be nice if your Cmakefile use standard ways of searching for system dependencies and linking with them.

Another worse problem is that your project depends on mongoose 6.9 and on functions which are no longer present in the latest version 7.10. Would it be possible for you to update your dependencies?

I'd still like to be a better upstream here but frankly I think I'll sooner be rewriting this in Rust than spending time getting C++ dependencies right.

I recently rewrote a good chunk of my hobby code to Rust, it is doable after some time investment...

I'm really quite comfortable writing Rust so that's not much of an issue.

There is a different project but that is not even usable in Kate text editor: https://github.com/KubaP/glsl-lsp

Oh, I had no idea. That's great!


Update eslint dep to v1.0.0

https://github.com/eslint/eslint/releases/tag/v1.0.0

That dep bump was a bit more involved than I was expecting.  Let me know if you'd like the commits arranged differently.

I should also note, I upped the deps and fixed tests.
I don't know what might be missing from: https://github.com/eslint/eslint/blob/master/docs/user-guide/migrating-to-1.0.0.md#all-rules-off-by-default
And are changes needed for https://github.com/eslint/eslint/blob/master/docs/user-guide/migrating-to-1.0.0.md#column-numbers-are-1-based ?

I appreciate the (fast) PR. Though, I had also performed the migration along with some dependency updates. gulp-eslint v1.0.0 has been published.


Type and param1 value of m_libspdm_negotiate_algorithm_request14

For the purpose of unittest18, it seems that the value of param1 should be 5 and the number of Alg structs should be 4.
So I think the type of m_libspdm_negotiate_algorithm_request14 is not libspdm_negotiate_algorithms_request_spdm11_multiple_tables_t but libspdm_negotiate_algorithms_request_spdm11_t.
https://github.com/DMTF/libspdm/blob/798ef4739ad5c1648f6d90a62774da2e7330795c/unit_test/test_spdm_responder/algorithms.c#L2527-L2528
https://github.com/DMTF/libspdm/blob/798ef4739ad5c1648f6d90a62774da2e7330795c/unit_test/test_spdm_responder/algorithms.c#L491-L567

I will check this


rules do not seem to work

For some reason my rules are ignored,
for example, I got a nginx_connections_current metric
> kubectl get --raw '/apis/custom.metrics.k8s.io/v1beta1/namespaces/satellite/pods/web-backend-5dbc7475ff-54tfv/nginx_connections_current' | jq .
{
  "kind": "MetricValueList",
  "apiVersion": "custom.metrics.k8s.io/v1beta1",
  "metadata": {
    "selfLink": "/apis/custom.metrics.k8s.io/v1beta1/namespaces/satellite/pods/web-backend-5dbc7475ff-54tfv/nginx_connections_current"
  },
  "items": [
    {
      "describedObject": {
        "kind": "Pod",
        "name": "web-backend-5dbc7475ff-54tfv",
        "apiVersion": "/__internal"
      },
      "metricName": "nginx_connections_current",
      "timestamp": "2018-08-09T01:30:34Z",
      "value": "2"
    }
  ]
}

Now I create a rule
apiVersion: v1
kind: ConfigMap
metadata:
  name: adapter-config
  namespace: monitoring
data:
  config.yaml: |
    rules:
    - seriesQuery: 'nginx_connections_current{state="active"}'
      name:
        as: "ilya"
      metricsQuery: 'sum(nginx_connections_current{state="active"})'

And I expect a new metric ilya to be available via API.
After applying the config map and recreating the pod
$ kubectl apply -f custom-metrics-config-map.yaml
$ kubectl -n monitoring delete pod custom-metrics-apiserver-7f4996f669-vbvql

I still do not see any changes
$ kubectl get --raw '/apis/custom.metrics.k8s.io/v1beta1/namespaces/satellite/pods/web-backend-5dbc7475ff-54tfv/ilya' | jq .
Error from server (NotFound): the server could not find the metric ilya for pods

Am I missing something? please help

You don't have any resources associated with the metric, so it won't show up.  You need a resources section to indicate which resources the metric is associated with.  See the config docs or the config walkthrough in #95 for more information.

@DirectXMan12  thank you for a prompt response!
after reading config.md everything makes sense, I managed to get my custom metrics for the pod
    - seriesQuery: 'nginx_connections_current{state="active"}'
      resources:
        overrides:
          namespace:
            resource: namespace
          pod:
            resource: pod
          service:
            resource: service
      name:
        as: "ilya"
      metricsQuery: 'sum(<<.Series>>{state="active",<<.LabelMatchers>>}) by (<<.GroupBy>>)'

kubectl get --raw '/apis/custom.metrics.k8s.io/v1beta1/namespaces/satellite/pods/web-backend-5dbc7475ff-54tfv/ilya' | jq .
{
  "kind": "MetricValueList",
  "apiVersion": "custom.metrics.k8s.io/v1beta1",
  "metadata": {
    "selfLink": "/apis/custom.metrics.k8s.io/v1beta1/namespaces/satellite/pods/web-backend-5dbc7475ff-54tfv/ilya"
  },
  "items": [
    {
      "describedObject": {
        "kind": "Pod",
        "name": "web-backend-5dbc7475ff-54tfv",
        "apiVersion": "/__internal"
      },
      "metricName": "ilya",
      "timestamp": "2018-08-09T19:48:56Z",
      "value": "1"
    }
  ]
}


Support prefix in subqueries.

I raised an issue a while back (https://github.com/elixir-ecto/ecto/issues/2036) regarding a lack of a prefix option in subqueries. I closed it at the time because I found a workaround, and assumed there was no good reason to include it.
I ran into another case where this was required, so attempted to add the required functionality.
Please review that this makes sense, I'm not very familiar with the rest of the code. All tests do still pass though.

:heart: :green_heart: :blue_heart: :yellow_heart: :purple_heart:


dnstwist: 20201228 -> 20211204

Motivation for this change
Update to latest upstream release 20211204
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

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

1 package built:

dnstwist


Added Xcode 7.2 support to Travis

Current coverage is 65.87%

Merging #3216 into master will decrease coverage by -0.09% as of a7a184f

@@            master   #3216   diff @@
======================================
  Files            5       5
  Stmts         2415    2415
  Branches         0       0
  Methods          0
======================================
- Hit           1593    1591     -2
  Partial          0       0
- Missed         822     824     +2

Review entire Coverage Diff as of a7a184f

Powered by Codecov. Updated on successful CI builds.


Question about the PHONE dataset

Dear Mr. Ding
Thanks for providing the code and the data of your work.
I have a question about the PHONE dataset, related to the scale of the data. I have tried to test relative pose estimators in the image pairs given, but when I inspected the scale of the data, I found that it was excessively small. I paste here a plot of the translation values for the first sequence:

Should the data be scaled somehow to get the real GT?
Best

Hi,
Thank you for the comments. Since the dataset was build based on a Monocular camera, the ground truth for the translation is only up to a scale factor. So it's possible to evaluate the translation direction error, i.e., acos(Test'*Tgt/(norm(Test)*norm(Tgt))).
Best


Problem  whit  text_hide()

The compiler processes return to me an error of   ##bulding:
15% building modules 46/47 modules 1 active ...aravel\resources\assets\sass\app.scssWARNING: The `text-hide()` mixin has been deprecated as of v4.1.0. It will be removed entirely in v5.
        on line 10 of node_modules/bootstrap/scss/mixins/_text-hide.scss, in mixin `text-hide`
        from line 57 of node_modules/bootstrap/scss/utilities/_text.scss
        from line 14 of node_modules/bootstrap/scss/_utilities.scss
        from line 41 of node_modules/bootstrap/scss/bootstrap.scss
        from line 9 of stdin
                                   15% building modules 48/49 modules 1 active ...aravel\resources\assets\sass\app.scssWARNING: The `text-hide()` mixin has been deprecated as of v4.1.0. It will be removed entirely in v5.
        on line 10 of node_modules/bootstrap/scss/mixins/_text-hide.scss, in mixin `text-hide`
        from line 57 of node_modules/bootstrap/scss/utilities/_text.scss
        from line 14 of node_modules/bootstrap/scss/_utilities.scss
        from line 41 of node_modules/bootstrap/scss/bootstrap.scss
        from line 9 of stdin
                                   95% emitting

Who it is error  ?

I'm having the same problem...

This is just a warning and has since been suppressed: #26242.

this warnig has  removed;


Add git safe directory to workaround github actions ownership issues

Closes #25
As discussed in #25, new versions of git check ownership of .git directories. Until github/github actions change how docker-based actions are called, this will cause failures every time coverage/coveralls checks for metadata about the current commit. This PR is the simplest fix I could think of to accomplish this. The alternative would be to add a subprocess.run call in entrypoint.py to run the same command there. I figure since this repository is just a github action and nothing else that doing it in the Dockerfile would be fine.
When I use this on my own CI I see:
   File "/usr/local/lib/python3.12/site-packages/coveralls/api.py", line 301, in submit_report
    raise CoverallsException(
coveralls.exception.CoverallsException: Could not submit coverage: 422 Client Error: Unprocessable Entity for url: https://coveralls.io/api/v1/jobs

I'm hoping this is just a hiccup or a threshold from coveralls that they are mad about me restarting the same CI job over and over again.

I'm not sure what I did but coveralls seems to be made at me.

@AndreMiras Is the failing test expected to fail?
 Running on Github Actions but GITHUB_TOKEN is not set. Add "env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}" to your step config.
Traceback (most recent call last):
  File "/src/entrypoint.py", line 176, in try_main
    main()
  File "/src/entrypoint.py", line 171, in main
    run_coveralls(repo_token, parallel, flag_name, base_path)
  File "/src/entrypoint.py", line 80, in run_coveralls
    coveralls = Coveralls(service_name=service_name, **kwargs)
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/coveralls/api.py", line 47, in __init__
    self.ensure_token()
  File "/usr/local/lib/python3.12/site-packages/coveralls/api.py", line 54, in ensure_token
    raise CoverallsException(
coveralls.exception.CoverallsException: Running on Github Actions but GITHUB_TOKEN is not set. Add "env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}" to your step config.
ExitCode.FAILURE

I (my fork) doesn't have access to the COVERALLS_REPO_TOKEN secret, right?

Thanks for the PR, it looks good to me. Indeed for the repo secret access

Ok thanks for the context, no strong feelings at all. I was just curious about what made you change from your original implementation idea


[oracle] Fix setup/test errors related to RDS

What does this PR do?

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


[system] Does not pass invalid props to DOM

close #29320
📦 https://codesandbox.io/s/styled-prop-forwarding-to-dom-forked-p68wr?file=/src/Demo.js
@mnajdova What I did is import @emotion/is-prop-valid directly in @mui/system since both emotion & styled-components are using @emotion/is-prop-valid internally.

[x] I have followed (at least) the PR section of the contributing guide.

On hold, this is more complicated that I thought. Example is Chip component.
const ChipRoot = styled('div')(...)

function Chip(props) {
  return (
    <ChipRoot {...props} />
  )
}

ChipRoot is created by styled('div'), so invalid HTML props cannot be used. However, the Chip can receive the component prop which passed as an as prop and other props send to the custom component again. Those props are filtered by isValidProp which breaks the existing behavior.

Before we move forward, I think that we should consider the following (to be thorough):

Is the bundle size increase OK?
Does it lead to a hit in runtime performance?
Does it mean hiding prop leaks? Before we could see them leak when they were applied to the DOM node, going forward, we won't. Maybe our components need a different treatment than what developers are creating (I assume we would. be willing to spend more time to pinpoint the leak origin).
What's the root problem we are trying to solve? Could #25925 be more efficient/effective?

@oliviertassinari

Before we move forward, I think that we should consider the following (to be thorough):

Is the bundle size increase OK?
Does it lead to a hit in runtime performance?
Does it mean hiding prop leaks? Before we could see them leak when they were applied to the DOM node, going forward, we won't. Maybe our components need a different treatment than what developers are creating (I assume we would. be willing to spend more time to pinpoint the leak origin).
What's the root problem we are trying to solve? Once we know this, then I think we can consider: Could Add support for transient props with the styled API? #25925 be more efficient/effective?
Why fix it in system not one layer down, in styled-engine?

I will move @emotion/is-prop-valid to styled-engine instead. Note that it is internally used in emotion & styled-components. I don't think it will increase the bundle size.
No, is-prop-valid is the same function used in emotion & styled-components.
It should be fine, this PR only preserve the same behavior as emotion & styled-components if you do this:import { styled } from '@mui/material/styles';
const Custom = styled('div')(); // prevent leaks, similar experience to emotion & styled-components. This is what developers expect including me!

But if you specify slot, you will have to handle the shouldForwardProp by yourself (we are doing this in MUI components)const Internal = styled('div', { slot: 'Root' })(); // MUI components

preserve the same DX from the original styled. This is a common use case when developers want to create their components and leverage our styling APIs.
At first I thought there is no difference because both emotion and styled-components are using the same @emotion/is-prop-valid

@mnajdova I found that this is not a good way to go because it fails with this test.
it('able to pass props to `as` component that is from styled(string)', () => {
      const styled = createStyled({});
      const ChildRoot = styled('div')({});
      const Child = ({ component }) => <ChildRoot as={component}>content</ChildRoot>;
      const Button = styled('button')({});
      const { container } = render(<Button as={Child} component="span" />); // span should pass to Child

      expect(container.firstChild).to.have.tagName('span');
    });

With the current approach of our custom createStyled, we know only the initial tag when using const X = styled('div')({}) but we don't know about the as prop so we can't switch between using isPropValid (for HTML tag) or (prop) => prop !== 'theme' (for component).


[Bugfix] Send with Scan crashes

Problem
When the user scans a QR code the address is not passed to the send field / address
Expected
After the Scan button is tapped, and a QR is shown, the LTC address should show in the field
Steps to produce

Open app and tap the  Send tab
Tab the Scanbutton
Point the frame at a valid LTC QR code
Scan disappeared and the app crashes

Video Clip

Action Clip

@kcw-grunt Do you still have this issue with v2.0.0(635)?

looking...

It's not crashing but the hard wallet is making it hard to figure out the passphrase.

But, it works using this: https://walletgenerator.net/?currency=Litecoin

@kcw-grunt let's close this issue and you can create another issue for the new issue.


Readme link to setup instructions is broken

It should be:
https://developers.arcgis.com/ios/beta/swift/guide/install.htm
Or:
https://developers.arcgis.com/ios/beta/objective-c/guide/install.htm

FYI: @singhgag

Fixed. Closing


support rendering AuthProvider server-side

Hey, I see things are in flux here with the oidc-client-ts migration, hopefully it's ok that this targets the main branch.
This PR fixes SSR by condtitionally creating a UserManager instance based on the presence of window. The context API is preserved since I replace all userManager actions with a no-op function that throws when called.
This doesn't change existing client-side behavior to my knowledge.

P.S. your package-lock.json appears to contain resolutions to an npm registry that I can't resolve: https://devops.bt.siemens.com/artifactory/api/npm/
Your oidc-client-ts repo has the same problem - could you make sure your home folder's ~/.npmrc is clear of any custom registry settings?

Yes maybe its time to update npm to v7, This mean also updating CI by using nodejs v16, to keep it simply and which should be soon LTS...

nice now even with SSR support :-) thanks for contributing


Add support for message level 'info'.

When styling markers and a line has multiple messages, choose the message
with the level of highest precedence.
Default view:

ShowInfoMessages turned on:

@beck, want to add a few tests for this?

@park9140 - I've added some tests.
Testing here was a bit rough.  This area of code seems to be pretty sparse in terms of testing.
I wish the dependency injection of the editor was done differently, a bit more quarantined.  Since the editor is deeply coupled, (and trying not to avoid invoking the workspace) the test setup and tear downs required some heaving stubbing to get a LinterView instance.
I rewrote the pull.  Breaking display into smaller routines with associated unit tests.
There is definitely more cleanup that can happen in LinterView but the section I touched now has better coverage.

@dmnd, any thoughts on this?  I've been thinking this has been missing for a while. Would be nice to get in.

I haven't reviewed the code, so I could be making assumptions here (sorry), but I'm not really that enthusiastic about a simple integration of info level messages if we don't have a reliable way to dismiss them. Consider what the different levels of lint message mean:

Error: 99% of the time I will fix this and the message will disappear
Warning: ~97% of the I will adhere to the message and it will disappear
Info: often the message should be ignored and so it will be persistently present in my editor

For error and warnings, if I don't agree with the linter, I'm usually happy with disabling that lint message entirely. Very infrequently I will agree with the class of lint message, but decide it doesn't apply to the specific example in my code. I add a comment to disable the message locally in these cases, which is ugly, but infrequent.
But info level warnings are often useful but just as often not. I don't want to disable the entire class of message because that defeats the purpose of in "info" message. But I also don't want to little my code with local disabling comments. The only other option is to put up with info messages persistently being present in my editor.
Perhaps if there is a quick way to disable/enable info messages I'll be happier with them. I do agree they are useful, but by their nature I don't think they should be as persistent as errors and warnings, and right now all the different kinds of views (inline, gutter, highlight) all assume you always want to know about a message.

@dmnd, at this point there are not any linters producing info level errors, so it is unlikely to produce an overwhelming amount of issues by adding it.  That said I do think we will needs some way of configuring what level of messaging we care about.

@dmnd how you interact with errr/warning/info is the exact same as my own behavior.
Let me explain the motivation then for introducing info.  I've built a linter for python docstrings but it is far more annoying than useful because the feedback is styled as warning or errors. Introducing info provides a distinction.
The default styling for info is more subdued, making it easier to ignore my docstring violations when I don't care.  Screenshot attached above.
The hope is that linters will not start throwing out tons of info but use the level with as much discretion as error and warning. Or, as the case with my docstring linter, set the default level to info so the entire linter can be disable when annoying.
This pull also fixes a subtle bug.  Before: if a line has multiple messages, the marker will be styled according to the last message received.  Now: the message with highest priority is marked.
Thanks for the review. This is actually my first time diving into CoffeeScript. Any additional nitpicks / advice on writing idiomatic code is much appreciated.

at this point there are not any linters producing info level errors

Even one linter producing info messages means that you're likely to end up with a persistent message, though.

The default styling for info is more subdued, making it easier to ignore when I don't care

That's a good start, but I think we need something better instead.
How about this:

info messages don't show up in the gutter, or as underlines, until they are toggled on via a command linter.toggle-info.
linter.toggle-info is bound to keyboard shortcut ctrl-cmd l, i.
a count of all info messages for the current file does appear by default in the new status bar summary
clicking the blue dot in the status bar summary activates linter.toggle-info

What do you guys think? Does that sound like a reasonable UX for info messages?
By the way, I haven't used that docstring linter yet, but since you brought it to my attention I'm definitely going to try it - looks useful! :smile:

@dmnd, I like your suggestions. For those of us who like to burn our retinas with more information than is actually necessary,  it would be nice to have a way of forcing the info errors on at all times.

IMO adding an info display toggle command is slightly overengineering a solution to a problem that does not (yet) exist.
I've added a config to "hush" info-level messages.  "hush" meaning hide the gutter marker and highlighting but keeping the message in the status bar.
Due to purely selfish reasons, I've toggled hushInfoMessages to false - reason being that my own linter's default level is info. If other linters start spamming the UI with info messages, then it will be needed to be defaulted to true (I personally hope info will be used with discretion).
@dmnd what is this "new status bar summary" you so speak of?
The changes to config I introduced are a bit simpler than @dmnd's suggestion but it should address the main concern: the ability to hide noise.

what is this "new status bar summary"

See #277. It shows a count of each type of message for the current file. You can see it in the bottom right of the screenshot on that PR.

a problem that does not (yet) exist... I personally hope info will be used with discretion

I think this is why we disagree. I think we have different ideas about how info will be used.
I don't expect any linter package to filter messages generated by the underlying linter. Exercising discretion is not really the job of the linter package. Maybe your linter is different (I haven't tried it yet), but most linter packages simply conveniently display in the editor whatever output a linter executable generates. The package doesn't exercise any editorial behaviour because each underlying linter has its own config system.
As an example, when this info level ships, I expect the existing pylint linter will map its "convention" messages as "info", because they're basically synonyms. Right now I think it maps both "fatal" and "error" to our "error", and "warning" to "warning". Were you thinking that linter-pylint would only report a subset of "info" messages through to the UI?

I don't expect any linter package to filter messages generated by the underlying linter

I see what you're saying.  We're on the same page now, and I agree.

Were you thinking that linter-pylint would only report a subset of "info" messages through to the UI?

Nope, I'd imagine it would pipe out all convention messages as info just as you except.
I've removed the last commit, hushInfoMessages is now defaulted to true.  I'm thinking that this is still not good enough, the message needs to also be suppressed from the status bar too.

I've updated pull.  The config now has showInfoMessages which is defaulted to false.
I still need to update the status bar.  Still sorting out the best approach.  Tried editing processMessage but that had negative side-effects.  So next up is editing the statusbar view, which will have to wait until tomorrow.

Updated the status bar (with new screenshots above).

:bell:

@dmnd, this is looking good to me, any problem with going ahead and pulling it?

Sorry for the wait.
And thanks for understanding my point @beck! I think it's in a good spot to ship at the moment given that the default is off. We can deal with the other stuff I mentioned if it's popular.
@park9140 feel free to pull this yourself if you want. Otherwise I promise (!) I'll dedicate some time this weekend to linter and do a release with this in it.

Merged, thanks @beck!

No prob.  The feedback on this pull was great, thanks all.

@beck, Would just like to say how glad I am you put together these tests.  Our coverage has been lackluster at best and every bit helps.  Thank you.


Add MetalLB support in Metal3

Add support for MetalLB in Metal3 charts.
The default installation of the chart will still be with PowerDNS and External DNS.
The following configurations in the Metal3 chart will disable the PDNS and EDNS and will start using MetalLB:
global:
  enable_external_dns: false
  enable_pdns: false
  enable_metallb: true
  ironicIP: "<STATIC_IRONIC_IP>"
  ingress:
    enabled: false

metal3-ironic:
  service:
    type: LoadBalancer

Currently, the MetalLB should be manually installed in the cluster and also if K3s is used as Kubernetes distribution, then it should be started with --disable=servicelb flag.
Also if Traefik is enabled in the K3s, it will not receive an external-ip, as the IP pool defined in the metal3-deploy/0.1.0/README.md has only one IP and it selects the ironic service.
In order to allocate an external-ip to Traefik, new IPAddressPool should be defined.

I tested this and other than the minor nits mentioned in the README it works great, thanks!

@dprodanov4 @ipetrov117 as discussed please review - if you're happy we can either merge this as-is and deal with the README nits as a follow-up, or one of us can push to this branch to address them

Hey Steve, i did review the changes too and actually started testing in my own branch but we can go ahead and merge that. LGTM as well!

@hardys I addressed your comments, can you please check the latest changes?


 Is it possible to upgrade to the latest version, 1.3.15.dev1023?

Of course.  Thank you - may I ask, as I am curious, as to the naming convention for your versioning - the latest production, I assume is 1.3.14?

Yes, that's correct - that is the production release. Official releases only happen every now and then, though, so we encourage people to use dev-releases when possible to stay up to date. (A dev-release is created after every commit to the main branch)


Update alert-policies.md

Adding missed mention for all EOP, MDO P1 or P2 add on subsciption as a SKU option for 2 alerts.

Learn Build status updates of commit 5e7d821:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-365/compliance/alert-policies.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@robmazz Gentle reminder.


Uploader组件增加可上传同一文件功能

RT

Coverage increased (+3.6%) to 79.826% when pulling ea2aa0dc32a5bc166bddf6b19d1a902d7627c52a on regrex:develop into eacb599920380f577ddbee8f12e06227325138cb on ecomfe:develop.


Typescript go to definition no longer working

Issue Type: Bug
Load a typescript project, command click or right click on a type name, the go to definition option is no longer available.
VS Code version: Code 1.64.1 (d6ee99e4c045a6716e5c653d7da8e9ae6f5a8b03, 2022-02-07T17:26:08.977Z)
OS version: Darwin x64 21.2.0
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz (16 x 2300)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
2, 2, 2

Memory (System)
32.00GB (0.17GB free)

Process Argv
--crash-reporter-id 9b1dda95-bb03-4b84-aa39-6cf6657594ae

Screen Reader
no

VM
0%

Extensions (7)

Extension
Author (truncated)
Version

vscode-eslint
dba
2.2.2

gitlens
eam
11.7.0

prettier-vscode
esb
9.2.0

auto-rename-tag
for
0.1.10

copilot
Git
1.7.4924

intellij-idea-keybindings
k--
1.5.0

vscode-open-in-github
sys
1.16.0

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyl392cf:30425750
pythontb:30283811
pythonvspyt551cf:30345471
pythonptprofiler:30281270
vsdfh931cf:30280410
vshan820:30294714
vstes263:30335439
vscorecescf:30435083
pythondataviewer:30285071
vscod805:30301674
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
vsc1dst:30433059
pythonvs932:30410667
wslgetstartedc:30433508
vscop940:30404999
vsrem710:30416614

Please share a minimal code example that demonstrates the issue

https://user-images.githubusercontent.com/4025574/153108862-b6b298ae-2b1b-4415-a49e-0d1474062f62.mov
Sorry, here's a screen recording, as you can see there is no option to go to definition on the ListingStatus type, option click or command click doesn't navigate either.
I notice that the Typescript version is not displayed in the window I'm using, its set to auto detect.

hi @mjbvz,
I've spent some more time trying to figure out why this is happening for me but haven't had any luck yet. Goto definition is still missing from the context menu.
This is what I've tried:

disabling all extensions
clearing all my custom vscode settings
Using a simple project with npx create-next-app -e with-typescript
Switching from asdf managed node to volta.sh managed node
Downgrading to vscode 1.62

It was working fine a few weeks ago 🤔

Can you please share a project that demonstrates this problem?
Also make sure you have not disabled the built-in typescript extension:

In the extensions view
Search @builtin typescript
Make sure TypeScript and JavaScript Language Features is enabled

Oh thank you so such!! I can't remember disabling it but the builtin typescript extension was disabled.
Its all good now :)


More intuitive way to close suggestion box

Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
Make onOutSideTap close the suggestion box by default. Right now, user has to use focusNode to close the suggestion box manually. If the user doesn't know or is new to the package, it can put them in an uneasy situation to find a way to do that.
Or we can update the document to show the user how to close the panel in a clear and straightforward section, with clear section name.

Describe alternatives you've considered

I completely agree, I had that on my mind before, I think the challenge here is identifying the global TapOutSide, Searchfield has its own TapOutSide which is built by combining taps on TextField + Suggestions I believe to understand whether Searchfield has Focus,  I can't think of it at this time.

By just passing suggestionAction: SuggestionAction.unfocus, will close the suggestion box  We should make this behavior as default

Published in v1.2.0