Tip16 JavaScript code snippets deprecated

Updated content to match new content template

Tested JavaScript tip several times, getting errors/tests fail, code snippet may need to be updated

Errors I got :  1) Screenshot
"before each" hook for "on failure":
Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.

Screenshot "after each" hook for "on failure": TypeError: Cannot read properties of undefined (reading 'takeScreenshot')

Add a timeout before line 38 in non-updated-tips.
beforeEach(async function() {     this.timeout(60000)     driver = await new Builder().forBrowser("chrome").build();   });
This will ensure the driver has enough time and the test will fail and a screenshot will be taken in the current directory.

Thank you @aquaomarine!!!

closing pull request - this file has been transferred to #194 - I created this one under unupdated tips instead of updated. #194 was created correctly under updated tips.


iindex.md

Changes in PR:

Can you tell me why this renaming is necessary? I couldn't find any information in vitepress docs about it


Fix lint errors

make lint is failing in CI. See https://drone.gitea.io/go-gitea/gitea/693/5, for example.

Codecov Report

Merging #2547 into master will increase coverage by 0.02%.
The diff coverage is 40%.

@@            Coverage Diff             @@
##           master    #2547      +/-   ##
==========================================
+ Coverage   26.96%   26.98%   +0.02%
==========================================
  Files          84       84
  Lines       16906    16892      -14
==========================================
  Hits         4559     4559
+ Misses      11672    11660      -12
+ Partials      675      673       -2

Impacted Files
Coverage Δ

models/gpg_key.go
30.18% <0%> (+0.28%)
:arrow_up:

models/login_source.go
0% <0%> (ø)
:arrow_up:

models/issue.go
25.02% <0%> (+0.07%)
:arrow_up:

models/org.go
69.8% <100%> (+0.44%)
:arrow_up:

models/ssh_key.go
10.39% <100%> (+0.05%)
:arrow_up:

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 d155d0e...de60e75. Read the comment docs.

LGTM

make L-G-T-M work

Could you add a backport to v1.2 too, since the CI test is failong too?

LGTM

@ethantkoenig Could you add a backport to v1.2 too, since the CI test is failong too?


run: Support endpoint enrichment

This commit introduces a new endpoint type that can be used by the
events generated by the gadgets. The gadgets need to fill in the IP
address (IPv4 or IPv6), the version (4 or 6) and the port (in host byte
order) for each endpoint. Then the user space part automatically enriches
that with the KubeIPResolver operator.
One virtual column is added per endpoint, and it's enriched and
formatted according to the data available:
$ ./kubectl-gadget run --prog @./gadgets/trace_tcpconnect_x86.bpf.o --definition @./gadgets/trace_tcpconnect.yaml
INFO[0000] Experimental features enabled
NODE                   NAMESPACE             POD                   CONTAINER             PID     TASK        SRC                      DST
ubuntu-hirsute         default               mypod6                mypod6                182408  wget        p/default/mypod6:44632   r/<IP_ADDRESS>:80
ubuntu-hirsute         default               mypod6                mypod6                182408  wget        p/default/mypod6:33464   r/<IP_ADDRESS>:443
ubuntu-hirsute         default               mypod6                mypod6                182444  wget        p/default/mypod6:37184   s/default/nginx:80

Custom columns are available for different fields inside the endpoint (addr, port, etc):
$ ./kubectl-gadget run --prog @./gadgets/trace_tcpconnect_x86.bpf.o --definition @./gadgets/trace_tcpconnect.yaml -o columns=node,pod,src.addr,src.port,dst.addr,dst.port
INFO[0000] Experimental features enabled
NODE                                   POD                                    SRC.ADDR             SRC.PORT            DST.ADDR            DST.PORT
ubuntu-hirsute                         mypod6                                 <IP_ADDRESS>       51828               <IP_ADDRESS>             80
ubuntu-hirsute                         mypod6                                 <IP_ADDRESS>       45184               <IP_ADDRESS>             443

Endpoints are also presented in the json/yaml/jsonpretty output modes:
$ ./kubectl-gadget run --prog @./gadgets/trace_tcpconnect_x86.bpf.o --definition @./gadgets/trace_tcpconnect.yaml -o json | jq
...
    {
      "src": {
        "port": 38548,
        "v": 4,
        "namespace": "default",
        "kind": "pod",
        "name": "mypod6",
        "addr": "<IP_ADDRESS>",
        "proto": "TCP"
      },
      "dst": {
        "kind": "svc",
        "namespace": "default",
        "v": 4,
        "addr": "<IP_ADDRESS>",
        "name": "nginx",
        "port": 80,
        "proto": "TCP"
      },
      "runtime": {
        "runtimeName": "containerd",
        "containerId": "23d304dfed76c670696cb532f5f6efed7cda9e91e7884be35ec227ef5f613d80",
        "containerName": "",
        "containerImageName": "docker.io/library/busybox:latest"
      },
      "node": "ubuntu-hirsute",
      "namespace": "default",
      "pod": "mypod6",
      "container": "mypod6",
      "hostnetwork": false,
      "timestamp": "1970-01-01T00:00:00.000000000Z",
      "mntns":<PHONE_NUMBER>,
      "pid": 11116,
      "task": "wget",
      "uid": 0,
      "gid": 0
    }

TODO

[x] Make extractor generic not to marshal integers as strings in json (https://github.com/inspektor-gadget/inspektor-gadget/pull/1817#pullrequestreview-1530468503)
[ ] Avoid running operators all the time (https://github.com/inspektor-gadget/inspektor-gadget/pull/1825#discussion_r1259537234) (Future PR?)

This is ready for review folks, thanks!

But I find the code to get the L3/L4 endpoint a bit too complicated.

Unfortunately I haven't find a better way to handle it. Suggestions are welcome.

This is ready for reviewing folks. It's still missing to fix the issue about having operators always run (https://github.com/inspektor-gadget/inspektor-gadget/pull/1825#discussion_r1259537234), but that requires some more work and I'd prefer to tackle that in another PR.

I still find the code heavy but I still do not have another solution, so I think we are tied with it.

I share the same concerns. This is still in a very early development phase, so I don't want to expend too much time trying to write perfect code, I'd rather prefer some code that works and then iterate to make it better.

Do we have some tests for containerized gadgets? I would like to avoid the case where we translate plenty of gadgets to this, deprecate the old and just a whole red CI.

We have an integration tests for trace_open (https://github.com/inspektor-gadget/inspektor-gadget/blob/main/integration/inspektor-gadget/run_trace_open_test.go), and we'll be adding more tests as we convert the gadgets.
Thanks for the review!


Query on partitioned table doesn't filter out partitions in a smart way

CrateDB version
5.7.0
CrateDB setup information
No response
Problem description
Query on partitioned table doesn't filter out partitions in a smart way if the source of the partitioned generated column is used
Steps to Reproduce
CREATE TABLE IF NOT EXISTS "doc"."weather_data_partitioned"(
   "timestamp" TIMESTAMP WITHOUT TIME ZONE,
   "location" TEXT,
   "temperature" DOUBLE PRECISION,
   "humidity" DOUBLE PRECISION,
   "wind_speed" DOUBLE PRECISION,
   "ts_month" TIMESTAMP GENERATED ALWAYS AS date_trunc('month', "timestamp")
) CLUSTERED INTO 1 SHARDS
PARTITIONED BY ("ts_month");
COPY weather_data_partitioned
FROM 'https://github.com/crate/cratedb-datasets/raw/main/cloud-tutorials/data_weather.csv.gz'
WITH (format='csv', compression='gzip', empty_string_as_null=true);

The following query doesn't filter out partitions (hits all of them)
EXPLAIN ANALYZE SELECT
       ts_month,
       AVG("temperature") AS "avg_temperature",
       AVG("humidity") AS "avg_humidity",
       AVG("wind_speed") AS "avg_wind_speed"
    FROM "doc"."weather_data_partitioned"
    WHERE "timestamp" >= '2023-01-01' AND "timestamp" < '2023-03-01'
    GROUP BY "ts_month"
    ORDER BY "ts_month" ;

where as:
EXPLAIN ANALYZE SELECT
       ts_month,
       AVG("temperature") AS "avg_temperature",
       AVG("humidity") AS "avg_humidity",
       AVG("wind_speed") AS "avg_wind_speed"
    FROM "doc"."weather_data_partitioned"
    WHERE "ts_month" >= '2023-01-01' AND "ts_month" < '2023-03-01'
    GROUP BY "ts_month"
    ORDER BY "ts_month" ;
``` filters the partitions correctly

### Actual Result

Partitions are not filtered out if `timestamp` column is used in the `WHERE` clause.

### Expected Result

Automatically understand that `timestamp` is the source column for the generated expression that constructs the `partitioned by` `ts_month` column and use it to filter out the partitions

For a simpler table:
cr> create table t_p(a int, b generated always as (a % 10)) partitioned by (b);
CREATE OK, 1 row affected (0.048 sec)
cr> insert into t_p(a) select * from generate_series(1, 20, 1);
INSERT OK, 20 rows affected (3.329 sec)
cr> refresh table t_p;
REFRESH OK, 10 rows affected (0.001 sec)
cr> explain analyze select * from t_p where a = 11;

the mechanism works correctly, and this is done in GeneratedColumnExpander, so the query becomes:
((a = 11) AND (b = (11 % 10))) which is used to filter out partitions.
For the timestamp case though there is an implicit _cast function introduced, for which the signature doesn't support the Feature.COMPARISON_REPLACEMENT, so the GeneratedColumnExpander exits here: https://github.com/crate/crate/blob/master/server/src/main/java/io/crate/analyze/GeneratedColumnExpander.java#L185

Is this a regression? If not, it's not a bug, but a potential performance improvement

Based on https://github.com/crate/crate/issues/14250, I tested on 5.3.2, 5.6.1 and current nightly. It worked with a modified create table statement, as there has been TIMESTAMP WITHOUT TIMEZONE vs. TIMESTAMP in the column definitions for timestamp vs. ts_month (see below). Omitting the datatype on the generated column leads to the expected effect, that partitions are selected. It touches three partitions (maybe because we put the 1st March, but no docs are fetched from this partition).
Modified CREATE TABLE statement (omitted data type on generated column - using TIMESTAMP WITHOUT TIMEZONE in the column definition of ts_month still leads to the scan of all partitions):
CREATE TABLE IF NOT EXISTS "doc"."weather_data_partitioned"(
   "timestamp" TIMESTAMP WITHOUT TIME ZONE,
   "location" TEXT,
   "temperature" DOUBLE PRECISION,
   "humidity" DOUBLE PRECISION,
   "wind_speed" DOUBLE PRECISION,
   "ts_month"  GENERATED ALWAYS AS date_trunc('month', "timestamp")
) CLUSTERED INTO 1 SHARDS
PARTITIONED BY ("ts_month");

EXPLAIN ANALYZE of the query filtered by WHERE "timestamp" >= '2023-01-01' AND "timestamp" < '2023-03-01':

Thx for checking it further @ckurze!
@mfussenegger, yep it's not a bug, as I missed this issue with the datatype which adds the implicit cast, and I thought that the mechanism to filter out the irrelevant partitions was broken in general.

So the issue is the type definition in the table schema ? o_O
Is there a difference between TIMESTAMP and TIMESTAMPTZ ?

Workaround is to just omit the data type for the generated column that is used for partitioning, but the implicit cast should be fixed. I see it moved into the candidates for 5.8. Thank you :)

Thanks for catching!
Has been implemented in https://github.com/crate/crate/pull/15920 and will be available in CrateDB 5.8


Added OS and architecture to user-agent string

Fixes #101. Not sure about the format of the string but at least it
contains arch and os now.
@csaunders

<3


[GHSA-vg46-2rrj-3647] Twisted vulnerable to NameVirtualHost Host header injection

Updates

Affected products

Comments
It looks like the version on PyPI is https://pypi.org/project/Twisted/22.10.0rc1/ without the extra .

Hi there @alex and @adiroiban! A community member has suggested an improvement to your security advisory. If approved, this change will affect the global advisory listed at github.com/advisories. It will not affect the version listed in your project repository.
This change will be reviewed by our highly-trained Security Curation Team. If you have thoughts or feedback, please share them in a comment here! If this PR has already been closed, you can start a new community contribution for this advisory

This seems to match the normalized version form used by PyPI: https://pypi.org/project/Twisted/#history


Test bundle size effects of using serde_lite instead of serde for Resources

Okay, this is pretty promising; it did manage to drop the bundle size of the HackerNews hydration client from 470kb to 445kb.
There are two concerns right now that are stopping me from just doing this:

At the moment the serde-lite author doesn't have Serialize and Deserialize implemented for Result, so I moved all the HTTP requests over to return an Option<T>. Given that I was returning Result<T, ()> for simplicity there is no real difference, but in a real app this is a blocker. I've opened an issue on serde-lite (see https://github.com/operutka/serde-lite/issues/2) but would definitely want that resolved before I'd do this.
There are plenty of convenience crates that rely on serde to do things like JSON deserialization in fetch requests. The manual version with serde-lite is a little more awkward, since you get text, then deserialize to an intermediate format, then deserialize to the actual type https://github.com/gbj/leptos/blob/5c022879f16d488ba7eca017a6aa42ad1474199a/examples/hackernews/hackernews-app/src/api.rs#L18-L27

Given the bundle size effects and the big benefit this would on load times have as apps scale up — I've found serde to be the main culprit in real-app bundle sizes — I think this is worth it but would love some feedback.

Oh and I should clarify: this is mostly to do with SSR + hydration mode, not pure-SPA client-side-rendering mode.
If you are doing SSR and hydrating resources/async requests will actually start on the server, and stream the results down to the client, which is much faster than waiting until the client has fully loaded. So initial load for the HackerNews demo is faster in SSR + hydrate mode than in SPA mode.
SPA/CSR mode:

Ask server for HTML
Browser sees it needs JS/WASM, and downloads them
Once WASM is downloaded, run component, including the create_resource
Begin network request to fetch from API (from browser)
Now we have data and can render it

SSR/hydrate mode:

Ask server for HTML. Server has to render the page. While rendering page, sees the create_resource
Begins fetching from API (on server)
Browser gets HTML. Sees it needs JS/WASM, and downloads them
API request resolves on server and it streams the result down to the client. (If you're inside a <Suspense/> component it actually streams the newly-rendered HTML too and replaces the fallback state)
WASM is downloaded and runs the component.
Sees the resource is already resolved, and deserializes it from JSON.

Depending on the API latency + WASM bundle size, streaming SSR means you often get the data + HTML before the WASM has even begun running, which is a huge speedup.
But this is why resource types need to be Serialize + Deserialize: so we can actually poll them on the server, send down JSON, and resolve them on the browser.

Thinking more I'm pretty sure the answer is to feature flag this so you default to serde but can opt in to serde-lite (or even miniserde) with a flag.

This was good for me to think aloud... I'm pretty happy with the solution in #33 and am going to go with that.


Errors while building with R.swift

Everytime I build(after clean the project) the project, and the error always show up but it still able to run!
The message is :
egrep: $PODS_ROOT/R.swift: Is a directory
Command /bin/sh emitted errors but did not return a nonzero exit code to indicate failure

You might still be able to build because you've a previously generated R.generated.swift file that is not being updated.
What script do you have in Build Phases?
It should be something like this:

Also double check the installation instructions to see if there's something you've missed.

It's the same to yours!

Could you please try to put the R.swift script and the TODO/FIXME script in seperate steps? That would make it more clear where the error is coming from.
Your error message mentions egrep which is in the find commando. Also rswift should always exit with a non-zero exit code if something goes wrong. That indicates to me that the find/egrep command is giving errors and not R.swift. Splitting up the scripts would make this more clear.

I'll close this, feel free to still comment if this isn't the solution!

I've removed the TODO/FIXME script and reinstall R.swift !
It works! everything is great!
Thanks a lot!

TAGS="warning:"
ERRORTAG="danger:"
find "${SRCROOT}/{TARGET_NAME}" ( -name ".h" -or -name ".m" -or -name ".swift" ) -print0 | xargs -0 egrep --with-filename --line-number --only-matching "($TAGS).$|($ERRORTAG).*$" | perl -p -e "s/($TAGS)/ warning: $1/" | perl -p -e "s/($ERRORTAG)/ error: $1/"
-working without errors


abstract out device conversion

Timeline values should be specifiable in any unit and converted at the end by merging with device specifications.

work has started on this. add_linear_conversion is available (though it's in the wrong place) with tests.


Bump testify to 1.3.0

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Codecov Report

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

@@          Coverage Diff           @@
##           master    #204   +/-   ##
======================================
  Coverage    77.2%   77.2%
======================================
  Files          18      18
  Lines         636     636
======================================
  Hits          491     491
  Misses        104     104
  Partials       41      41

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 af0b813...88d0d5d. Read the comment docs.


chore: Migrate to centralized package management

Our production libraries core dependencies (Grpc.Net.Client etc) are currently still explicit, but we could potentially even centralize though, only being explicit when creating patch releases (which is rare).
There's a significant downside, which is that we either need to use package source mapping, or only have a single package source. This is probably a generally good thing for supply chain security, but we'll want to work out how to use locally-generated packages easily.

Humbug - releases have conflicted. Will rebase and sort out...


Fix HealthCheck

file:///home/node/app/node_modules/puppeteer-core/lib/esm/puppeteer/common/Connection.js:58
        _Callback_error.set(this, new ProtocolError());
                                  ^

ProtocolError: Protocol error (Page.printToPDF): paper width is zero or negative
    at new Callback (file:///home/node/app/node_modules/puppeteer-core/lib/esm/puppeteer/common/Connection.js:58:35)
    at CallbackRegistry.create (file:///home/node/app/node_modules/puppeteer-core/lib/esm/puppeteer/common/Connection.js:103:26)
    at Connection._rawSend (file:///home/node/app/node_modules/puppeteer-core/lib/esm/puppeteer/common/Connection.js:212:26)
    at CDPSessionImpl.send (file:///home/node/app/node_modules/puppeteer-core/lib/esm/puppeteer/common/Connection.js:419:78)
    at CDPPage.createPDFStream (file:///home/node/app/node_modules/puppeteer-core/lib/esm/puppeteer/common/Page.js:720:88)
    at CDPPage.pdf (file:///home/node/app/node_modules/puppeteer-core/lib/esm/puppeteer/common/Page.js:746:37)
    at PdfAction (file:///home/node/app/src/Action/PdfAction.js:29:31)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
Exit code: 1.

Current Workaround is deactivating the health check in the docker-compose file.
    healthcheck:
      test: [ "CMD", "none" ]

now works again!


Hang while processing 2K by 16K map

Trying out the map generator with the following code:
                let map = DensityMap::new(extent.width as usize, extent.height as usize, 1, raw_data).unwrap();
                let settings = GenerateDensityMeshSettings {
                    points_separation: 16.0.into(),
                    keep_invisible_triangles: false,
                    ..Default::default()
                };
                // create live density mesh.
                let mut live = LiveDensityMesh::new(map, settings);
                // perform initial processing.
                live.process_wait().unwrap();

The map is 2K by 16K. I waited for more than an hour for a release build, it hasn't finished.
Here is the test file -

(I wasn't able to upload the lossless PNG version, since it's above 10Megs)

hi! i've found many more problems with live density mesh for big maps and right now i'm currently rewriting it to work on snall changes, should be ready on monday :D

Great, thank you! In the meantime, is there a way to generate the mesh statically? I've only been able to find https://docs.rs/density-mesh-image/1.3.0/density_mesh_image/fn.generate_densitymap_from_image.html , which depends on Image crate.

during last week work on new live mesh generation i was fighting with spade's iterative adding/removing of vertices that has a nasty internal infinite loop bug on vertices remove. trying to fix it was a nightmare and i failed to fix it properly without introducing new bugs, which means i have to make a dedicated triangulation from scratch that will work with live vertices removal.
about static mesh generation, i'm gonna post an example after work today, stay tuned! :D

covid situation and deadlines at work made me able to work a couple hours on weekends.
long story short: i was about to say that dynamic points removal in spade's delaunay was impossible to not fall into internal infinite loops which makes this problem impossible to solve atm, then i changed spade back into triangulation crate and found out that my entire region change points selection algorithm after refactoring, was more or less a bunch of crap - so there is a light in the tunnel! working on it rn :D

ok, after fixing this particular problem it showed me that there are more.
sadly, i have to say this: for now, at this moment, it is not possible to make reliable live terrain updates other than rebuilding the whole mesh from the whole density map on each change. i'm going to prepare new update to do that to make sure it always gives reliable output, and try to optimize as much as i can based on that. i could jump into the live mesh generation again in next month :<

I'll be happy to test it once ready. No rush from my side, and thank you for all the hard work!

there is new version, example is listed in README, as well as playground app is in the density-mesh-playground project.
please note, that atm with your map it is reeeeeeeaaaaaally slow, so i'm gonna work on optimizing this with your map you've provided in a month or so :)

Thank you! Note that I don't need that published on crates, necessarily. I'm fine with a github dependency, so that we can iterate faster.

Ok, I tried it, and now I see why you had so many "e" and "a" in that "really" word. It's not only non-realtime, it's more of a supercomputer task now. Is it remotely feasible to get this close to realtime somehow? Maybe trading performance for quality or something?

Basically, this comes down to using proper settings, but I don't know what they mean. So putting proper documentation in place for them would be great!


Update documentation for xpcshell debugging  (remote debugging)

The following page still references the Connect... page: https://developer.mozilla.org/en-US/docs/Mozilla/QA/Writing_xpcshell-based_unit_tests#Debugging_xpcshell-tests
At this stage in a running Firefox instance:

    - Go to the three-bar menu, then select Web Developer -> Connect...
    - A new tab is opened, keep the defaults of localhost and 6000 and select Connect
    - You should then get a link to Main Process, click it and the Developer Tools debugger window will open.
    - It will be paused at the start of the test, so you can add breakpoints, or start running as appropriate.

The Connect page has now been disabled (in FF 69) and removed (in FF70) so this is no longer usable.
Instead the text could say:
- Go to about:debugging
- If there is no "localhost:6000" item in the sidebar:
  -  go to "Setup"
  - add a Network Location with the value "localhost"
- Click on the "Connect" button next to the Sidebar item for "localhost:6000"
- Note: if there are no debugger statements in the test, the test will resume and terminate as soon as the debugger connects. Make sure to add at least one debugger statement before trying to debug.

cc @irenesmith
should block https://github.com/mdn/sprints/issues/851


Revert "Merge pull request #19 from SwiftPackageIndex/hang-workaround"

This reverts commit a335f1266d0066e370b93f0a9db03c671fc207ee, reversing changes made to 4877d48116268ce12051c2acd78f77092581616a.

self-merging


Members participation

Same as #29 .

A section should be included in the README.md in which each team member indicates their participation in that phase with:

Textual description of the tasks performed in the phase.
List of the 5 most significant commits during the phase (linked to these commits in GitHub).
List of the 5 files in which he has participated the most (linked to said files in GitHub).

Closed with #138


Enable vertical scroll synchronization

As briefly explained here, the template's notification structure had wrongly sized fields.
This corrects the alignment so that scroll events can be detected.

@rdipardo Thank You!  I merged on my local copy into develop branch and pushed giving you credit in the message.


feature(ui-ux): add skeleton loader to balance screen

What kind of PR is this?:

/kind feature
What this PR does / why we need it:

To display skeleton loader in balance screen
To not display 0 as balance amount when balance API has yet to return

Which issue(s) does this PR fixes?:

Fixes #970
Additional comments?:
Developer Checklist:

[x] Read your code changes at least once
[x] Tested on iOS/Android device (e.g, No crashes, library supported etc.)
[x] No console errors on web
[x] Tested on Light mode and Dark mode*
[x] Your UI implementation visually matched the rendered design*
[ ] Unit tests*
[x] Added e2e tests*
[ ] Added translations*

Can we align the loaders?

Curious if there's a way to handle these errors from the loader

Can we increase margin top here?

Alignment issue on the DFI card, on the webapp, not sure if this will affect mobile view

I think we always have the priority of testing on mobile first then web, does it work on mobile?
For both the horizontal alignment issue from chloe and pierre should be from web, will address them
For @fullstackninja864 issue, can't seems to find that huge gap as shown in your screenshot on my ios, android and web, may I know what device did you test on?

@kyleleow I am testing on Samsung Galaxy A30S


Save original source metadata

This saves the original source metadata in the source folder of the processed scene, including the manifest.safe and the content of the annotation directory.
Currently a subdirectory based on the productIdentifier is created to save the files:

Another option would be to use the complete name for the directory. E.g., in this case S1B_IW_GRDH_1SDV_20211114T190500_20211114T190525_029588_0387F4_527F. Thoughts @johntruckenbrodt ?

Thanks a lot @maawoo. I think the way you have solved it is good. Upon entering the annotation directory, one immediately sees the NRB metadata files as usual and can directly relate to the product identifier of the subdirectory via the file names. Shortening the path is also a good idea to limit the maximum possible path for windows systems.


Bumping deps, k3d/kubernetes, helm-charts

@enrichman what's the status of this? was it ready to merge, or does it need to be revisited?


Move 'mark as unread' to overflow menu

The envelope icon seems to be confusing to many users. I suggest when showing the message view we put the "mark as unread" action into the overflow menu (by default; may be changed once #5300 is implemented).

I agree that the picture is not really easy to understand (an arrow trying to open/close the envelope may be indeed more clear), but moving it in the overflow menu is to me a bad idea. Overflow menu is indeed hard to reach, and it would lose a lot of time going into this menu everytime I want to mark an email as unread. Another option may be to keep a better picture AND also put the item in the overflow menu.

No way! I use "unread" as a means of tracking messages I still need to do something with. As a result I regularly read a new message, decide I can't do anything about it right then and need to follow up on it later, and mark it as unread. Either leave it alone, or make it's move to overflow an option.


Fixes for nvidia-ko-to-module-symvers

Note that these changes were previously merged into the old ntv2 repo, here: https://github.com/aja-video/ntv2/pull/34

Fix nvidia-ko-to-module-symvers pattern matching. The previously used pattern would hit partial matches, which could lead to errors if more than one symbol shared the same prefix.

Update nvidia-ko-to-module-symvers to support CRC table. CRC entries for symbols exported by kernel modules may be provided either by absolute values in the symbol table, or as offsets into the CRC table stored in a separate __kcrctab data section. This change adds support for the latter type of relative entry as it is needed to support RDMA with newer kernels (>= 5.19).

@ibstewart Please change the PR so that it wants to merge into the "main" branch. Our "release" branch is currently used to follow our latest tagged release. The main branch is for ongoing development. Thanks.

Seems these changes were recently added to the main branch anyways, my bad!


Support for Softlayer multi-path feature

This is needed for Bluemix on SoftLayer (SL) since the best disks on SL are iSCSI and the changes are needed to correctly setup these disks. Most of this code was part of a forked copy of the agent code that the Bluemix team has been maintaining so it's already in production but we want to contribute this back.
This new PR changed to use device path resolver infrastructure. The new multipath_device_path_resolver.go is added.

Is this PR out of date? I see a lot of commits but a tiny diff... may be rebase is needed?
I thought this PR was about adding iscsi attachment logic to the agent so that agent can properly connect to any iscsi device.

@gu-bin Your tracker story is still pointing to this PR. Can you update @cppforlife and myself to the new PR by commenting here as well. Thanks,
max

@cppforlife I've combined all the commits to one. Please let me know if any other problems. Thanks.

@cppforlife @bosh-ci-push-pull
Softlayer can't partition disk for us before use so the parameter "UsePreformattedPersistentDisk" in agent.json must be set to "false" and we need bosh agent to partition and format the disk for us.
When bosh agent do the partition for the disk, it must use the real path of the disk like
/dev/mapper/3600a098038303051555d4637396e4c7a
And after partition, the partition path is something like
/dev/mapper/3600a098038303051555d4637396e4c7a-part1
So the disk path that CPI passes to bosh agent must be something like /dev/mapper/3600a098038303051555d4637396e4c7a with no "-part" appended.
If CPI passes something like "/dev/mapper/3600a098038303051555d4637396e4c7a-part" to bosh agent which is not a real disk path, the bosh agent can't partition the disk. So we still need this PR.

@cppforlife @bosh-ci-push-pull
Any comments for this PR?

I am looking through the softlayer cpi code to understand a bit more how this could be consolidated...

After another review of the code, we found the way to add a new devicePathResolver to support Softlayer multi-path feature doesn't work for MountPersistentDisk in linux_platform.go. If use multipathDevicePathResolver to GetRealDevicePath that adds "-part" to the device path, the Partition will fail, because "/dev/mapper/xxxxxx-part" is not a valid disk path to partition.
The root cause is that partitionPath is hard coded to realPath + "1". But for multi-path, the partitionPath should be realPath + "-part1". The problem exists in MountPersistentDisk, UnmountPersistentDisk and IsPersistentDiskMounted of linux_platform.go. I wonder if we can have something like partitionPathResolver which can resolve partition path accordingly. Especially for multi-path, it will add "-part1" not "1" for partition path.

@cppforlife @bosh-ci-push-pull
What's  your comment for this PR?

@gu-bin Emailed you and Max to get an environment to play around with some of these features.

@cppforlife @bosh-ci-push-pull
I've sent you the environment info via email.

@cppforlife @bosh-ci-push-pull
This PR is finalized. Please review. Thanks.

time.sleep is fine. its location what doesnt make sense to me. lets move it after err check. no amount of time waited will make that err switch its value.
Sent from my iPhone

On Dec 15, 2015, at 7:49 PM, Gu Bin<EMAIL_ADDRESS>wrote:
@cppforlife @bosh-ci-push-pull
This PR is finalized. Please review. Thanks.
—
Reply to this email directly or view it on GitHub.

@cppforlife @bosh-ci-push-pull
I've moved the time.Sleep after err check. Please review.

Can you also please add analogous unit tests for -part1 just like we have for 1 suffix?

@cppforlife @bosh-ci-push-pull
Unit tests have been added. My local run of test-unit is successful. Please review.

@cppforlife @bosh-ci-push-pull
We changed to use retryable to check xxx-part1 partition to show up instead of time.Sleep. Please review. Thanks.

@cppforlife @bosh-ci-push-pull
Any update for this PR?

@cppforlife can we get a status on this one, I believe @gu-bin addressed all pending issues.
Thanks,
Max

oops thx for the bump. will take a look at this one tomorrow.
Sent from my iPhone

On Jan 12, 2016, at 6:37 PM, Gu Bin<EMAIL_ADDRESS>wrote:
@cppforlife @bosh-ci-push-pull
Any update for this PR?
—
Reply to this email directly or view it on GitHub.

Merged to develop.
Thanks for your pull request!


feat(jellyfish-api-core): add blockchain getMempoolAncestors RPC

What this PR does / why we need it:
/kind feature
Which issue(s) does this PR fixes?:
Implemented type for RPC: https://github.com/DeFiCh/jellyfish/issues/48

blockchain.getMempoolAncestors()

Additional comments?:

If you run every test item individually, some of them will fail


Please look at this Bug: the color of the link should be changed.

Please visit  https://jsfiddle.net/gazeldx/9nbkm904/9/ and read the description I added.

The style field of the items in your list is not defined upfront, so Vue can't pick up changes for this field, and does not consider it reactive.

new Vue({
  el: '#homePage',
  data: {
    products: [{capacity: 'link 1', style: ''}, {capacity: 'link 2', style: ''}, {capacity: 'link 3', style: ''}],
    product: null,
  },
  methods: {
    selectProduct: function (product) {
      this.product = product
      this.products.forEach(function (prod) {
        if (prod === product) {
          prod.style = 'color: #1aad19; font-weight: bold;'
        } else {
          prod.style = "background-color: ''"
        }
      })
    },
  },
})


Add schedule trigger to yaml

Please add schedule triggers to yaml (currently not supported).

I think this is an important feature in context of Infrastructure-as-Code and in particular Immutable Infrastructure builds.
Examples:

Building and maintaining OS Images with a pipeline e.g. using Packer:
A Team might be maintaining various Packer Pipelines. (e.g. os-base-image, webserver-nginx, ubuntu-tomcat, etc.)
Each time a new image is being introduced, they would want to utilize a template repository that contains both, packer definitions and azure-pipeline.yaml.

Building and maintaining Docker Images with a pipeline.
Here a DevOps Teams might want to recurringly build these images against the latest OS Upgrades. If this cannot be scheduled recurringly, each time someone has to go in and hit unexpected surprises which can happen proactively when the pipeline runs scheduled.

Thanks,
Darius

Another use case is testing stochastic (non-deterministic) functionality.  I have a scenario where we would like to periodically run tests to build up many sets of outputs, from which we determine whether there are meaningful changes over time.
For example:

I have 20 different statistical optimisation algorithms
Every hour I want re-run the oldest test

Now my pipeline that has an existing scheduled trigger got the message as follows
You can no longer define scheduled triggers in the editor. Instead, you must add schedules to your YAML file. For more information, see https://go.microsoft.com/fwlink/?linkid=2080841

But there is no info on how to add schedules to yaml in the mentioned link.

I'm having the same problem @andyli is having.  It's worth mentioning that there's more documentation for yaml triggers here: https://docs.microsoft.com/en-us/azure/devops/pipelines/build/triggers?view=azure-devops&tabs=yaml#scheduled-triggers .... but it says scheduled triggers aren't supported in the yaml syntax.

@stevedanielson @vijayma can you get the official docs up and the FWlink updated to point to it? Thanks.

The manual now has some mention of the schedule configuration, but it is far from sufficient for transferring scheduled triggers to YAML. Let's say I have two pipelines A and B which use the same YAML file x.yml, but with different variables and variable groups and different schedules, e.g. pipeline A is configured with a variable group DEBUG_BUILD and a variable TEST=quick and runs once a day, and pipeline B is configured with a variable group RELEASE_BUILD and a variable TEST=full and runs once a week. The manual doesn't say anything about variables or variable groups in the YAML schedule configuration, and from the current look of it, this configuration cannot be transferred to YAML at all. I hope it's a documentation oversight, because duplicating YAML files isn't a really a viable option for real-life setups which can have dozens of such parallel configurations.

Having different schedules for different pipelines but using the same YAML is not supported. You can factor out your pipeline logic into a template, and then have a very small YAML wrapper that just includes the schedule triggers and imports the template.

(And we will definitely consider this feedback as we evolve the feature - thank you!)

So, just to make sure I understand -- it was fully supported in UI, then scheduling got removed from UI with the suggestion that it should be done in YAML instead, but there is no way to do it in YAML. Is it correct? Or do you mean that it was an unsupported feature in the UI as well, it just happened to work?
And yes, I fully understand that I could do it as you said, but the reality is (and I suppose not just mine), that I have over 40 pipelines using the same YAML with different options and running on different schedules, so I will need over 40 wrappers, which is hardly maintainable.

Our view of config-as-code is to push as much configuration into the code file as possible, rather than have some in code and some in a database. Is maintaining 40 YAML files more effort than maintaining 40 point-and-click schedules? (That's a genuine question - there may be something here I'm not considering.)

Numerous YAML files pollute the source tree, and frequent updates to them flood git history; but it's a rather small (and maybe arguable) nuisance.
The problem is, config-as-code approach in its current form doesn't replace the UI configuration. If I were now able to have only one UI pipeline which would magically run with different YAML files and different parameters on different schedules, it would be all right, but it's not so, I still have to have the same 40 UI pipelines, but now also 40 YAML files instead of only one, and keep them in sync. Whenever I need to add or remove a configuration, I will need to do it in two places, as a YAML with the schedule and as a UI pipeline. Changes in schedule also usually come together with configuration changes (you modify certain parameters and because of that, change the schedule to make the run more or less frequent), so again, two places instead of one.
Anyway, I appreciate the clarification, I needed to make sure I'm not missing anything, because converting the scheduled setup from UI to YAML is a big job which I didn't want to do just out of ignorance.

As per the docs, scheduled triggers are not yet supported in YAML syntax with Azure DevOps Server.
Is there any plan to support it?

It should be available in a future Azure DevOps Server release. (I don't believe it made the cutoff for 2019.1, though.)

Since this feature has shipped, closing the issue.

Hello all, I am unable to delete current schedule from UI, what is wrong with you dev team?
Besides if I need to create multiple pipelines from single yaml file now they will have same schedule? Really?
Why I can't override schedule from UI as for trigger?

We are working on enabling the UI again for the schedules. You will be able to use YAML for the scheduled, but if you do not want to, you can continue to use the UI. Sorry about the trouble.

Hello Vijayma,
Our build was using the GUI schedule even though it isn't supported anymore.
So my plan was to add the schedule to the yaml and delete the GUI schedule.
However I am not able to delete the schedule even though there is a trash icon present. Clicking on it does not nothing.
To give some feedback I am all for putting config in code and under source control (everything should be)  so I am all for this move.
For feature parity though (GUI<->Yaml) I think releasing the feature it without timezone support is premature. We now have cadence of our master build of 3h,12h,20h and it's summer here. When it is winter this suddenly becomes 2,11,19 and we have to manually adjust and other dependent process will fail because of this change. Yes, we observer daylight saving time in the EU for at least a year more :)

I understand. Thanks for the feedback on timezone support.

Having different schedules for different pipelines but using the same YAML is not supported. You can factor out your pipeline logic into a template, and then have a very small YAML wrapper that just includes the schedule triggers and imports the template.

Being able to refer to a 'Schedule.Reference' (for example) would be extremely useful for then only running certain steps (as per @elenst post).

I don't see why this would be closed out - it is an important feature to have. I mean... Jenkins can do this. Why can't Azure DevOps? We have a need to run the same pipeline with several different parameters on several different schedules. Has a solution to run YAML build pipelines on a schedule w/ the parameters you want been found?
Seems odd that something like Jenkins can do this but ADO can not...

I don't see why this would be closed out - it is an important feature to have. I mean... Jenkins can do this. Why can't Azure DevOps? We have a need to run the same pipeline with several different parameters on several different schedules. Has a solution to run YAML build pipelines on a schedule w/ the parameters you want been found?
Seems odd that something like Jenkins can do this but ADO can not...

FWIW there's this StackOverflow answer which allows you to do custom things if the pipeline was scheduled vs manually run: https://stackoverflow.com/a/71511521/3688293


refactor(merchant_connector_account): change unique constraint to connector label

Type of Change

[x] Refactoring

Description

This Pr changes the unique constraint of merchant_connector_account to connector_label and profile_id
Motivation and Context

In order to allow multiple instances of the same connector to be created.
How did you test it?

Create a stripe account with the same connector twice -> Second time an error must be thrown

{
    "error": {
        "type": "invalid_request",
        "message": "The merchant connector account with the specified profile_id 'pro_BrafXvLpgRJNdRDVhS4P' and connector_label 'stripe_fallback' already exists in our records",
        "code": "HE_01"
    }
}

Checklist

[x] I formatted the code cargo +nightly fmt --all
[x] I addressed lints thrown by cargo clippy
[x] I reviewed the submitted code

@Narayanbhat166 We cannot make this change until we have removed backwards compatibility from routing (i.e. made merchant_connector_id mandatory) and ensured that every connector in every payment intent/attempt is coupled with a merchant connector id.
If we remove the constraint before the aforementioned is done, we'll run into issues (eg: for PSync, if the payment attempt only has stripe but no merchant connector id, and the profile has 3 stripe connector accounts, there's a 2/3 chance that the call will fail since the wrong credentials will be picked)
@Aprabhat19 is working on removing the backwards compatibility and backfilling all payment intents/attempts in the DB.


add py3.7 support

This adds py3.7 support, since colab and kaggle don't support newer python versions.
Note that the rest of the PyData stack has moved on and doesn't support 3.7, so this would mean users are using older versions of those libraries on those platforms.
cc @merveenoyan

Damn, I forgot that I actually use py3.8 features in this project. I'll need to see how easy it is to get it working on the older python.


values in vars files are not resolved into credhub

What version of the credhub server you are using?
1.95
What version of the credhub cli you are using?
2.0.0 ( has little bearing to the issue, I think )
If you were attempting to accomplish a task, what was it you were attempting to do?
I was attempting to deploy a new CF
What did you expect to happen?
I expected any missing certs to get autogenerated
What was the actual behavior?
the missing certs failed to auto generate with the error:
Error: Config Server failed to generate value for '/bosh-bbl-env-qinghai-2017-09-05t21-24z/cf/cc_public_tls' with type 'certificate'. HTTP Code '404', Error: 'The request could not be completed because the credential does not exist or you do not have sufficient authorization.'
at the time this happened we were in transition and using both a vars and credhub. And I do understand that because our CA was defined in the vars file credhub was not able to see it, and thus unable to generate the certs. That said having an error point directly to that fact in some way would have avoided a lot of the efforts put in to debug this.  I was told that the reasoning for such a vague error was due to security  concerns, but I view this type of error as a compilation error, and the error should provide more context as to what happened and what actions could be taken to resolve the issue. ( accept variable resolution from the vars file into credhub... but that would be a behavior change. )
I think making the errors more actionable and at the very least give more context into what went wrong, while balancing security would lessen operational burden imposed on operator.
Thank you,
Please confirm where necessary:

[x] I have included a log output
[x] My log includes an error message
[x] I have included steps for reproduction

[1] https://cloudfoundry.slack.com/archives/C02HPPYQ2/p1533756359000048
[2] https://cloudfoundry.slack.com/archives/C02HPPYQ2/p1533837835000255

I have the same issue with passwords.

@sjolicoeur @amuessig This seems like a BOSH issue to me. CredHub does not have any knowledge of the context in which your cert is being created. It is error-ing because there was not CA that it knew about to sign the cert you are asking it to create. BOSH holds all the cards in that it should be responsible for seeing the CredHub could not create the cert and telling you why. Closing. Feel free to reopen if you disagree.

Hey, @athornton2012, I agree that BOSH could do more to provide context here, but this is fundamentally an issue with the vague error coming from the CredHub API. In this case, BOSH requested that this new certificate be issued with a reference to a CA cert named /bosh-bbl-env-qinghai-2017-09-05t21-24z/cf/service_cf_internal_ca that it though CredHub would have, but didn't. It's possible to generate the same error via the CredHub CLI when generating a certificate entry against a reference to a CA cert that does not exist:
$ credhub generate -n /cert -t certificate --ca /ca-not-there -c cert
The request could not be completed because the credential does not exist or you do not have sufficient authorization.

In general, it would be clearer for the error message to refer to the name of the certificate credential that doesn't exist: The request could not be completed because the credential '/ca-not-there' does not exist or you do not have sufficient authorization. Otherwise, the user is inclined to think that the credential that doesn't exist is the one they are trying to generate, which is especially confusing because of course that credential doesn't exist yet before it has been generated.
In any case, the non-specificity of this error tied up a pair on the Diego team for about a day while they figured out the reason behind it. I expect they would have figured it out much faster if the error message had specified the precise credential that didn't exist. I don't think there's a concern here about leaking information, because the client already knows that CA credential name, and they presumably see this error if it does exist but the client isn't authorized to read it.
Thanks,
Eric

@emalm Hm okay, that seems like a good point. There is no need to obscure the credential name that CredHub was unable to find. Also I can see how this would be really annoying (it happened to me a couple days ago). Thanks for your comment!

Hey folks, this should be fixed in the latest release of CredHub! Here is the story we did to make error messages a little better: https://www.pivotaltracker.com/n/projects/1977341/stories/161087845.


the Loss not converging

Has anyone have happened this case，my loss always in 5 range，while I testing my image
we got too low score and not correct bounding-box
Which the range of this Loss is fine ?

Hi @gugugilin, loss can be affected by a lot of factors. Even modification of a single hyper parameters may lead to losses of different magnitudes. So "fine loss range" is unknowable.
I prefer to monitor the mAP of validation set during training.
Here are some tips when train this project:

Check the generator. Make sure correct data is feed to the training model.
If the loss does not converge at the early steps,reduce the lr.
CenterNet seems to converge slowly.So please by more patient.

Hi @gugugilin, loss can be affected by a lot of factors. Even modification of a single hyper parameters may lead to losses of different magnitudes. So "fine loss range" is unknowable.
I prefer to monitor the mAP of validation set during training.
Here are some tips when train this project:

Check the generator. Make sure correct data is feed to the training model.
If the loss does not converge at the early steps,reduce the lr.
CenterNet seems to converge slowly.So please by more patient.

Thanks for your replay, I have some question ，if you don't mind
I didn't overwrite the loss function and use the other backbone of a pre-trained model from Imagenet, Why they cause the range of loss has a huge difference between MobileNetv2 and ResNet
FYI, I am trying to reduce the learning rate， hope it is helpful for my case

I found that the focal loss which let my training become wirde，because my dataset has too much negative sample，so they always predict to zero, I update the parament of focal loss, it seems fine as far


BLE Server

Does blessed-bluez support a server? I want to wait for a connection from a specific device.

No, not yet...


Bringing GPMDP(u) to the Windows Store and Mac AppStore. [Universal App]

Having the app accessible for download just on a site and some tech news articles online is not enough.Today, when someone wants to download an app, more and more people are looking through the app stores pre-installed with their devices than ever before. I really believe it would be an asset to both development of the app and the general public to bring Google Play Music Desktop Player (unofficial) to both the Windows Store and Mac AppStores, the first of which can be brought to easily - Microsoft has a tool for developers to easily port x86 and x64 System32 apps to the Universal Windows Platform. It's definitely worth looking into.

https://github.com/MarshallOfSound/Google-Play-Music-Desktop-Player-UNOFFICIAL-/issues/2105


Dynamic class initialization does not work

from formatron.schemas.pydantic import ClassSchema
from formatron.formatter import FormatterBuilder
from formatron.integrations.exllamav2 import create_formatter_filter

I create a class for the formatter builder
class InfoExtraction(ClassSchema):
            Investments: float

it works with exllamav2 filters
filters = create_formatter_filter(utils.model, utils.tokenizer, formatter)

But If I want create the class dynamically exllamav2 is not able to create a response.
class InfoExtraction(ClassSchema):
            pass
InfoExtraction.__annotations__['Investments'] = float

@abpani You can dynamically create the class schema through the type() operator if you truly want to to. In my opinion, I think python class schema is expected to be created statically in one running program and then used as-is. If you need dynamic behaviour/serialization, you can use json schema instead.


Add keaising/im-select.nvim

Add keaising/im-select.nvim
Checklist:

[x] The plugin is specifically built for Neovim.
[x] The lines end with a .. This is to conform to awesome-list linting and requirements.
[x] It's not already on the list.
[x] If it's a colorscheme, it supports treesitter syntax.
[x] The title of the pull request is Add `username/repo`  when adding a new plugin.
[x] Neovim is spelled as Neovim (not nvim, NeoVim or neovim), Lua is spelled as Lua (capitalized).

Thanks for the PR!


fix: url for deployment demos

Description
The link provided in the ci script pointed to a non-existent url.
Changed it to point to the current guide, where some samples are located

Thanks 🙂


Small cs fix (Usage of !! cast is not allowed)

!! to (bool)

Codecov Report

Merging #1233 into master will increase coverage by 0.08%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #1233      +/-   ##
==========================================
+ Coverage   72.19%   72.27%   +0.08%
==========================================
  Files          35       35
  Lines        5549     5566      +17
==========================================
+ Hits         4006     4023      +17
  Misses       1543     1543

Impacted Files
Coverage Δ

src/Phinx/Console/Command/Rollback.php
95.18% <100%> (+1.24%)
:arrow_up:

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 b49fd8c...05bc378. Read the comment docs.


Wondering what APIs to use to query PerfView with only code

Hi,
I understand PerfView is a wonderful tool created by the Microsoft team, and I'm grateful for its existence! I'd like to if there are any APIs I can use directly to query the tool as a service or would I need to dive deeply into the source code and find the public APIs on my own for my purposes?

Did you found this page: https://github.com/microsoft/perfview/blob/master/documentation/TraceEvent/TraceEventProgrammersGuide.md#what-you-can-do-with-the-traceevent-library
It describes essentially the library Perfview is using.

Thanks, @eric-b, I missed that page!


Install failed with python version 3.11.3

Hi Diederick,
I was trying to install this project with python version 3.11.3,but it shows an error below.

Could you please help check this issue?
Thanks

3.11 is not supported for now, just 3.10, as stated in setup.py, strange
pip didn't complain about that. The problem is needing a specific scipy
version for now, I have it on my todo list to try and remove that
restriction, but it seems to be a hairy issue. Another blocker is opencv,
the latest version has a bug in a function we need. Its been fixed, but we
need to wait for a new release.
Can you run on 3.10, or if you only intend to use the GUI, use the
precompiled version?
I'll leave this open until i manage to make things work with 3.11.
On Thu, May 18, 2023 at 8:49 AM hubandad @.***> wrote:

Hi Diederick,
I was trying to install this project with python version 3.11.3,but it
shows an error below.
[image: image]
https://user-images.githubusercontent.com/32879674/239161698-b536f60e-c365-4129-bc8c-a44c66fb0b1a.png
Could you please help check this issue?
Thanks
—
Reply to this email directly, view it on GitHub
https://github.com/dcnieho/glassesValidator/issues/1, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AANUOGIZKV6NNVQOEASCXWDXGXA75ANCNFSM6AAAAAAYGB2EAU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Thanks for your response,  It works with 3.10.

Hi, Just to let you know that the scipy dependency issue is now fixed. That just potentially leaves a problem with opencv, i am not sure the release we are currently pinned to (due to a bug in the latest release that affects this project) supports 3.11. I do not have a 3.11 install. Would you be able to test the current master branch? Thanks!

OpenCV version is also updated. I assume this solves any issues using 3.11 that may have been there. Closing this


List VMs or Templates when filter for host is assigned

https://bugzilla.redhat.com/show_bug.cgi?id=1300809
Filter for host is setting in groups in tab Host and Cluster
2 bugs here:
a) UI doesn't reflect that group has assigned host filter.
Fixing bad matching of objects in belongs to filters in belongsto2object_list.
After this belongsto2object_list returns Host object moreover, so
we need to skip it here for origin behavior.
This settings is in group, in Host/Nodes& Clusters tab.
When host was checked it was stored in db but not visible in
tree that it is checked.
b) Handle situation when user is using host filter from group settings
This is handling listing of VMs or Templates for case when we have in belongs_to filter:
/belongsto/ExtManagementSystem|X1/EmsFolder|X2/EmsFolder|X2/EmsFolder|host/Host|HOST1
Then we are determining VMs and Templates by relations from Host object(HOST1).

@miq-bot remove-label wip


Dropdown: wrong window position

Testing on Debian bullseye, the position of the dropdown popup window is wrong. The following
patch makes it better:
diff --git a/src/dropdown.rs b/src/dropdown.rs
index 357a80e..dbd692a 100644
--- a/src/dropdown.rs
+++ b/src/dropdown.rs
@@ -33,7 +33,7 @@ impl<T: Data> Dropdown<T> {

     fn show_dropdown(&mut self, data: &mut T, env: &Env, ctx: &mut EventCtx) {
         let widget = (self.drop)(data, env);
-        let origin = ctx.to_screen(Point::new(0., ctx.size().height));
+        let origin = ctx.to_window(Point::new(0., ctx.size().height));
         self.window = Some(
             ctx.new_sub_window(
                 WindowConfig::default()

Horizontal position is now correct, but the windows has still the wrong vertical position (off by about the size of the window decorations).

If it's an improvement, then make a PR. :slightly_smiling_face:
If you do, could you add a TODO comment.  Just copying and pasting

Horizontal position is now correct, but the windows has still the wrong vertical position (off by about the size of the window decorations).

Would be fine.

If it's an improvement, then make a PR.

done


Add checkstyle bear with proper configuration

Assign me this one please.

[x] Assign this to me.
This is the one for JAVA, right ?


trialized event-aligned analysis

@kabilar - Do you want to take a look before I merge this to the event branch? I expect thorough review to take place when merging event to main

Thanks for merging @CBroz1.  I will review when this work gets merged into main.


Crash on every search

Crashlog.txt
Exception:
System.IO.InvalidDataException: Steam Search|Traceback (most recent call last):
  File "C:\Users\Zottelchen\scoop\apps\Flow-Launcher\current\app-1.9.3\UserData\Plugins\Steam Search-4.1.1\run.py", line 9, in <module>
    from plugin.main import SteamSearch
  File "C:\Users\Zottelchen\scoop\apps\Flow-Launcher\current\app-1.9.3\UserData\Plugins\Steam Search-4.1.1\plugin\main.py", line 6, in <module>
    from flox import Flox, ICON_SETTINGS
  File "C:\Users\Zottelchen\scoop\apps\Flow-Launcher\current\app-1.9.3\UserData\Plugins\Steam Search-4.1.1\lib\flox\__init__.py", line 40, in <module>
    if str(APPDATA.joinpath(launcher_dir)) in str(CURRENT_WORKING_DIR):
  File "C:\Users\Zottelchen\scoop\apps\python\current\lib\pathlib.py", line 851, in joinpath
    return self._make_child(args)
  File "C:\Users\Zottelchen\scoop\apps\python\current\lib\pathlib.py", line 616, in _make_child
    drv, root, parts = self._parse_args(args)
  File "C:\Users\Zottelchen\scoop\apps\python\current\lib\pathlib.py", line 578, in _parse_args
    a = os.fspath(a)
TypeError: expected str, bytes or os.PathLike object, not NoneType

I've set the trigger to * and entered my steam path, but it still crashes.

I believe the code I use to find FLow Launcher on your system (so I can reference settings) is not written with scoop in mind and is failing. I'm working on a fix now.


Remove oelint-adv downgrade workaround

Remove the oelint-adv downgrade once > v3.15.1 is available.

:+1:


Diwali-A community event

The data is about an Indian Festival called Diwali.

@aparna03dubey, hello there. I think this project requires events like open-source/developing or related to web development. We shouldn't list any religious event here. Thanks!

@TenTraicion you're right.
@aparna03dubey
sorry, but it seems your event doesn't fit in with our community. If you wish, you can open another pull request with another event or resource.

I have opened another pull request.
Please check if it's what you are looking for!
On Wed, Oct 5, 2022, 23:42 Clebson @.***> wrote:

@TenTraicion https://github.com/TenTraicion you're right.
@aparna03dubey https://github.com/aparna03dubey
sorry, but it seems your event doesn't fit in with our community. If you
wish, you can open another pull request with another event or resource.
—
Reply to this email directly, view it on GitHub
https://github.com/OctobearHub/octobear.org/pull/18#issuecomment-1268773414,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AYJY3DCE63IGNA5BFIR42Z3WBXAKRANCNFSM6AAAAAAQ5SOJTE
.
You are receiving this because you were mentioned.Message ID:
@.***>


Create atk.txt

The domain atk.kg I submitted previously belongs to faculty and staff
Domain for ATK students is atk.com.kg .
Government website：https://2020.edu.gov.kg/spuz/reports?id_university=102
Domain should be existent.
I have check the dns records and website. It is work.

@atkkg The first verification stage is complete: the official domain for  К.И. Скрябин атындагы Кыргыз улуттук агрардык университетине караштуу Султан Ибраимов атындагы Агротехникалык колледжи is 2020.edu.gov.kg, to the best of my knowledge. This is just an informational note. The pull request is still under review. The review may take some more time. I greatly appreciate your patience. Here is the proof of domain ownership: https://2020.edu.gov.kg/spuz/reports?id_university=102

@atkkg Thank you for your patience while waiting for a review and processing your request. Pull request merged.


feat: Add close tag after inputting /

Introduction.
Hello, I've been using Neovim exclusively for a while now.
One of the features I still miss in my Neovim is the ability, as in WebStorm, to automatically close an HTML tag when an opening tag is already available. (#94)
So, since I had some free time, I thought why not try to implement this feature myself and then share my modifications with you.
Operation.
When you write code like this:

    hoi
<

And when you add a / at the after normally the start of a close tag, with this Pull Request the tag will automatically close with the correct name:

    hoi

Note.
Just a last small detail, since I'm not the most comfortable with treesitter and the source code of this repository, I tried to modify as little as possible to avoid stepping on the work that has already been done.
That's why, apart from the signature of check_close_tag which has slightly changed, all the code I added is independent of the base code.
Also, for the consistency of this feature, I have added additional tests to verify that my modification also works in TSX, Vue, PHP, etc...
Finally, I am open to any changes or suggestions.

Ok thank


question about training data

Hello!!
Here is a question . Your traing dataset save in baidu disk. I can't download it cause i don't have baidu account.
Could you put it on google drive please!!
Thanks for watching!!

https://1drv.ms/f/s!AsP2NtMX-kUTmlCZgJwzejJvPLay?e=yBa1Hf
I upload it to onedrive, can you download it?

Hi, unfortunately the data was crash when i open the zip file

https://1drv.ms/f/s!AsP2NtMX-kUTml4U3DYUD6Hy9FJn?e=8QfJTH
If crashed, please tell me which one


Two features: more robust [session store] variables and expose body read status

1d2b509 allows one to call [$session store data] without fear of getting an error if that key has not yet been set.
ee6852d gives the route handler a way to know whether the entire request body has been read yet. If there is another way to accomplish this, please let me know...I couldn't find one. For use example: https://github.com/raztus/file-tally/blob/master/main.tcl#L38
Let me know if you prefer this as two separate pull requests.

Hi! Sorry about the time it's taken for me to get to this. I've been busy with another project of mine, and I haven't quite noticed this email until just recently! Yikes!
Anyhow, the first commit looks fine, so if you can open a separate pull request for that I will take care of it immediately. If you open a pull request for the second commit I'll explain my thinking on that one therein, and we can work towards a good solution. My primary complaint with the second commit is that a session object might not be the best place to indicate that the request body has been fully read; I'm sure there's a nicer way to accomplish what you need, and I certainly agree that placing the responsibility of knowing if a request body has been fully received into the application code atop tänzer may not be the nicest solution.
Thanks for using and helping contribute to tänzer!

Closed in favor of #8 and #9.


[ERROR] "Schedule for later" on publishing does not work

Issue Summary
I scheduled a post, and it did not publish on the date/time of scheduling.
I have tried publishing 5 minutes advance and it did not work.
Regular publishing works, not scheduling.
Steps to Reproduce
On Posts/Drafts/blog/editor

Publish
Schedule for later
In 5 minutes (In my case, I tried to schedule a week in advance)
Continue, final review
Publish post, on ...
All set! Your post will be published today at ...

Ghost Version
ghost:5.2.3
Node.js Version
v16.15.1
How did you install Ghost?
Docker & amd64
Database type
SQLite3
Browser & OS version
Edge & Version 103.0.1264.44 (Official build) (64-bit)
Relevant log / error output
[2022-07-04 14:43:17] INFO "GET /content/images/2021/11/2745c156-cc72-4615-a2f8-cb962ef92266.png" 200 2ms
(node:1) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 committed listeners added to [Function]. Use emitter.setMaxListeners() to increase limit
(Use `node --trace-warnings ...` to show where the warning was created)
[2022-07-04 14:43:31] INFO "PUT /ghost/api/admin/posts/62af758dcf04f70001e09b3a/" 200 587ms
[2022-07-04 14:43:31] INFO "GET /content/images/2022/06/fuelfilter.png" 200 7ms
[2022-07-04 14:43:31] INFO "GET /content/images/size/w256h256/2022/07/favicon-1.png" 200 4ms
[2022-07-04 14:48:26] ERROR The server has encountered an error.
The server has encountered an error.
Error ID:
    5c263c90-fba8-11ec-a1cb-450ae2361ad4
----------------------------------------
HTTPError: Response code 302 (Moved Temporarily)
    at /var/lib/ghost/versions/5.2.3/core/server/adapters/scheduling/SchedulingDefault.js:319:23
    at EventEmitter.<anonymous> (/var/lib/ghost/versions/5.2.3/node_modules/got/source/as-promise.js:74:19)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

Also posted issues on: https://github.com/docker-library/ghost/issues/316#issue-1293327851
Code of Conduct

[X] I agree to be friendly and polite to people in this repository

The scheduling functionality works by Ghost sending an HTTPS request to itself to trigger the publish. Scheduling is working in general, therefore I assume this is related to your docker setup and the issue there (or posting on the forum) would be the best way to get useful support from other docker users 🙂


search functionality

@hodgestar can you please review my code :)

I seem to have ended up leaving a lot of comments but they're mostly very minor. Looking nice!

Thanks @hodgestar, will have look at them :)

@hodgestar I applied the changes can you please review them :)

@saeedmb8 Looks good. The only thing left to do is to test that the SMS is actually sent. I've left a comment with a link to how that is done in one of the existing tests.

Thanks @hodgestar , I've added the test for sms functionality.

:+1:

@hodgestar I've added the exit option alongside the sms option, can you please review the codes and give me your opinion on the way I've done it :)

I've left a few minor comments. This work should probably have been done in a separate pull request since this pull request was already +1ed and the new commits are a fairly distinct piece of work. Long pull requests become harder and harder to review -- e.g. it's now tricky for me to review all the new work because it's buried inside a larger PR.

P.S. Don't worry about having done it in this PR for now -- just think about it for future PRs.

Thanks @hodgestar , Noted 🙏

:+1:


Raw Data link missing

Currently our production server is using the data that was in place on staging.
Staging had received list uploads from data.gov.uk, standbytaskforce, health-ministry-of -kenya, health-ministry-of -rwanda, nigeria MDG infomation system, kenya open data, testismail600
example:
https://www.healthsites.io/map#!/locality/f2adb2ed36e748879ee3ee293d4e0597
https://staging.healthsites.io/map#!/locality/f2adb2ed36e748879ee3ee293d4e0597

For production i found that incorrect localities (not OSM, and don't have raw link except the locality that created by user) are around 42992 localities

Hi @meomancer @timlinux yes, we need to re-load these locations. I will list the upload files here:
Nigeria:
https://docs.google.com/spreadsheets/d/1ddTv1D39ab1QymQ9ZN8MFpgmXKTRRmDdPvMJ_Ue3HXQ/edit?usp=sharing


Add validations for duplicate JMX bean entries

What does this PR do?
Add logic to check if any duplicate bean + attribute combination exist in a metrics.yaml
Motivation
To prevent the same data to be collected 2 or more times
Additional Notes
Tested it against the confluence_platform's and hive's metric.yaml and was able to find a couple of duplicate beans. Examples:
Link1 versus Link2
Sample output:
Validating JMX metrics files for 13 checks ...
confluent_platform:
    - The following bean and attribute combination is a duplicate:
    - kafka.controller:type=KafkaController,name=OfflinePartitionsCount: ['Value']
hive:
    - The following bean and attribute combination is a duplicate:
    - metrics:name=memory.heap.init: ['Value']
    - metrics:name=memory.heap.usage: ['Value']
    - metrics:name=memory.heap.used: ['Value']
    - metrics:name=memory.heap.max: ['Value']
    - metrics:name=memory.heap.committed: ['Value']
    - metrics:name=memory.non-heap.init: ['Value']
    - metrics:name=memory.non-heap.used: ['Value']
    - metrics:name=memory.non-heap.max: ['Value']
    - metrics:name=memory.non-heap.committed: ['Value']
    - metrics:name=memory.total.init: ['Value']
    - metrics:name=memory.total.usage: ['Value']
    - metrics:name=memory.total.used: ['Value']
    - metrics:name=memory.total.max: ['Value']
    - metrics:name=memory.total.committed: ['Value']
13 total JMX integrations
11 valid metrics files
2 invalid metrics files

Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] PR title must be written as a CHANGELOG entry (see why)
[ ] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
[ ] PR must have changelog/ and integration/ labels attached

Thanks! And ah sorry, that's true we shouldn't check for duplicate beans. What I was trying to say was we want to catch fully duplicate entries ie
bean:'my.bean:type=foo,name=baz'
  attribute:
    - Count
bean:'my.bean:type=foo,name=baz'
  attribute:
    - Count

@sarah-witt I added some suggestion from the links you provided, thanks! I tested it against the commit you referenced and seems to be working there.


tegola: 0.12.0 -> 0.12.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/go-spatial/tegola/releases.
meta.description for tegola is: "Mapbox Vector Tile server"
meta.homepage for tegola is: "https://www.tegola.io/"
meta.changelog for tegola is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 0.12.1 with grep in /nix/store/abi65cvp5g78hnglwiammcy7xm753rb1-tegola-0.12.1

directory tree listing: https://gist.github.com/c2406315e7f3cb980ba76472f6fa813c

du listing: https://gist.github.com/1b51d6526b1de3500e6a92490c4a444e

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
tegola

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/abi65cvp5g78hnglwiammcy7xm753rb1-tegola-0.12.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A tegola https://github.com/r-ryantm/nixpkgs/archive/cb814301193d7d9c00f76c9355965c3187ccd4aa.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/abi65cvp5g78hnglwiammcy7xm753rb1-tegola-0.12.1
ls -la /nix/store/abi65cvp5g78hnglwiammcy7xm753rb1-tegola-0.12.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review 1

1 package built:

tegola

Maintainer pings
cc @ingenieroariel for testing.

lgtm


[stable/mysqldump] option to run additional shell steps

What this PR does / why we need it:
This PR introduces a new parameter for custom steps in the mysqldump script.
These steps will run after all dumps and backups finished successfully.
It's handy if you need to do additional $stuff with your dumps. Without it, and without the possibility to specify a dump file name, automation is a lot harder.
Also, the Notes.txt had probably custom aliases of kc, which obviously should be kubectl as not everybody aliased his kubectl to kc, thus returning an error message after installing the Chart and running suggested commands.
Special notes for your reviewer:
Checklist

[X] DCO signed
[X] Chart Version bumped
[X] Variables are documented in the README.md

/assign @monotek

Oh, of course, here we go :)


Add ECS config file support

Add support to filter ECS Clusters and Services by name in config file.
Test output:
https://gist.github.com/brandonstrohmeyer/e3bc64ebf9d2ac98c055ec48fc7180f2

https://github.com/gruntwork-io/cloud-nuke/pull/261/files#r768149940

LGTM as well! I'll kick off a sanity check regression build now and if that passes, we can merge this in! Thanks for your contribution!

Build failed, but it's for an unrelated resource test, so it effectively passed. However, as mentioned on the ELBv2 version of this (https://github.com/gruntwork-io/cloud-nuke/pull/261), there is a merge conflict, so consider combining the two PRs together.

Build failed, but it's for an unrelated resource test, so it effectively passed. However, as mentioned on the ELBv2 version of this (#261), there is a merge conflict, so consider combining the two PRs together.

I opened #266 as a combined PR. Originally I wasn't sure if it was better to submit each individual config file "feature" as an individual PR, but it seems that creates more problems than it solves so will lean toward larger PRs in the future.
Thanks!


Mobile: Ifdef escape some test code which isn't supported on iOS

We'd like to run common and cc tests on the iOS simulator inside Google.  The ::system and EXPECT_DEATH calls are not supported on iOS, so I have ifdeffed them out.
I've already made this change internally and enabled iOS tests!

/retest

/retest

/retest


Integrating Nvidia's Transfer Learning Toolkit (Feature Request/ Question)

Hello @dusty-nv !
Fantastic repo. Been following it for a few years now since DIGITS was first introduced.
I saw in another issue that you are integrating a Pytorch SSD detector into the repo. Can I ask why there is no push to integrate the TLT package from nvidia into this repo?
They support the following:
Image Classification
ResNet10/18/50
VGG16/19
MobileNet V1/V2
AlexNet
SqueezeNet
GoogLeNet

Faster RCNN supporting backbones:

ResNet10/18/50
VGG16/19
GoogLeNet
MobileNet V1/V2
Object Detection
DetectNet_v2 supporting backbones:

ResNet10/18/50
VGG 16/19
GoogLeNet
MobileNet V1/V2

SSD:

ResNet10/18

I hear they plan to introduce maskRCNN and yolov3 as well.
If one could use that toolkit for training and then use this repository for doing inference with the models, that would make for an amazing combination!
TLT training --> export to tensorRT engine --> Jetson Inference (classifcation/detection/segmentation)
The toolkit already comes with a model optimizer and converter to a tensorRT engine for the jetsons. All we need is a way to load the model and run inference realtime with your python/c++ jetson inference stack.
I hope this can someday be a reality. It would really be great to make sure all software with this repo and other models stay relevent throughtout the years and has support from Nvidia as a whole.
Thank you for all your hard work!

Hi @mbufi, thanks for your feedback - I will have to take a look at integrating TLT workflow.   For now, I have been aiming to get PyTorch re-training of SSD object detection, as it can be run onboard the Jetson (for those who may not have access to training PC/server).   The TLT container runs on x86, however it should not be a problem to run the TensorRT engine from it.

@dusty-nv great to hear. Thank you for that.
I totally understand why you are integrating the ssd model for people without a dedicated x86 computer.
I will leave the issue open to inquire about any updates in the future with regards to your progress with TLT if you decide to integrate it.
Cheers

@dusty-nv I just watched the new video posted on Nvidias youtube about the ketson IOT platform. Any updates on this?


BugFix:  after  won't work

Fixes #2045

supersedes https://github.com/NLog/NLog/pull/2096

Maybe change the logic, so it always parses elements in this order (and not just targets first):
case "EXTENSIONS":
case "INCLUDE":
case "TIME":
case "VARIABLE":
case "APPENDERS":
case "TARGETS":
case "RULES":

Indeed this was too Much quick fix

Easy fix would be to always parse "RULES" last :)

Have to look into this. Where variables and include is defined, does matter.

Easy fix would be to always parse "RULES" last :)

That's indeed a much easier approach -  keep it simple :)
changed!

Fixed in 4.4.10 and the release is queued. Will be online in a few hours!


Inc migration from Framework to ASP.NET Core /1

Internal review URL
contributes to #27405 and https://github.com/dotnet/systemweb-adapters/issues/98

I'll hook up the TOC in a follow-up PR once this is approve. I can also do a style guide edit in the future.

Thanks Rick, will take a look. Also added a few more reviewers.

@adityamandaleeka  only 1 question left

[ ]  The VS tools team has a VS extension that helps with incremental migration and makes this process a lot easier. Would it make sense to talk about that here and link to the vsix?  @adityamandaleeka - do you know if there's a reason we should or shouldn't talk about the vsix in these docs?

Thanks @Rick-Anderson!


migrate to react-router-v4

Do not merge.
This is just for review diff. I'll create a new folder to store RRv4 implementation.

Can we use<EMAIL_ADDRESS>in production environment?


Change month by click on different month days

Is possible to change the month by click on a different month day? Maybe it's already possible and I don't have found how, but the others days seems click disabled.
Many thanks.

There isn't anything to do this, and it would be complex to change it. Right now the views for days from previous and next months are disabled entirely, which disables clicking and changes the text color automatically. I might be able to include this with #88; we will have to see.

Many thanks! Anyway great work, my compliments!

I will be working on this in the next couple days and will make a pull request. Thinking of either adding another attribute (disabledViewsAreSelectable) with the same possible values as showOtherDates).

Wonderful! I think your addition idea could be nice. Well done, thanks!
On 28 October 2015 at 19:30, Adam Charron<EMAIL_ADDRESS>wrote:

I will be working on this in the next couple days and will make a pull
request. Thinking of either adding another attribute
(disabledViewsAreSelectable) with the same possible values as
showOtherDates).
—
Reply to this email directly or view it on GitHub
https://github.com/prolificinteractive/material-calendarview/issues/116#issuecomment-151943131
.

Well I did most of the work in getting this functional. I structured it pretty similarly to showOtherDates, but I'm having an issue where when it's applied programatically, it only applies to the nearest couple of months, and when I scroll back to the months it was working on, the affect has disappeared.


Add data_mode()

This PR resolves #962  . Created  def data_mode in Model_Results class for access via df.

Codecov Report

Merging #998 (01b8146) into main (ee6e3f0) will decrease coverage by 0.03%.
The diff coverage is 93.10%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

@@            Coverage Diff             @@
##             main     #998      +/-   ##
==========================================
- Coverage   85.56%   85.53%   -0.03%
==========================================
  Files          34       34
  Lines        7530     7515      -15
==========================================
- Hits         6443     6428      -15
  Misses       1087     1087

Impacted Files
Coverage Δ

ross/results.py
89.45% <93.10%> (+0.13%)
:arrow_up:

... and 11 files with indirect coverage changes

Continue to review full report in Codecov by Sentry.

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


404 Island component not found since Nuxt 3.6.0

Describe the bug
Hey @harlan-zw, has anything changed since Nuxt 3.6.0? Can't figure out why things are not working after bumping nuxt to latest.
[nuxt-og-image 11:33:49 PM]  WARN  nuxt-og-image does not support the nitro target undefined with the runtime browser. Set runtimeBrowser: false to stop seeing this.
                                                                              11:33:47 PM
✔ Nitro built in 1449 ms                                                nitro 11:33:53 PM
ℹ Vite client warmed up in 2841ms                                             11:33:54 PM
✔ Vite server hmr 18 files in 1064.645ms                                      11:33:56 PM
[Vue warn]: Component <Anonymous> is missing template or render function.     11:33:56 PM
[11:33:57 PM] [nuxt] [request error] [unhandled] [404]  (404 Island component not found: undefined (/__nuxt_island/OgImageBasic:VvoKLzP9ba?

I basically took your "Minimal Playground Example" and bumped both Nuxt to v3.6.1 and nuxt-og-image to beta.58
Reproduction
https://stackblitz.com/edit/nuxt-starter-p6wd8z?file=components%2FCustomBanner.island.vue
System / Nuxt Info
------------------------------
- Operating System: Linux
- Node Version:     v16.20.0
- Nuxt Version:     3.6.1
- Nitro Version:    2.5.1
- Package Manager<EMAIL_ADDRESS>- Builder:          vite
- User Config:      modules
- Runtime Modules<EMAIL_ADDRESS>- Build Modules:    -
------------------------------

Thanks @tmlmt, looks like the Nuxt core is handling the island routes different as of 3.6.0, have pushed up a fix in beta.59

Thanks @harlan-zw!
For the sake of clarity regarding the island component:

Your readme instructions tells to place the component in /components/islands/MyTemplate.vue
Your Minimal Playground Example has one as /components/CustomBanner.island.vue
The Nuxt docs seem to indicate that server components are registered with the suffix .server in e.g /components/MyTemplate.server.vue

Could you clarify what matters and what doesn't?

As of v2.0.0-beta.60, the recommendation will be to place the components in the OgImage folder by default.
Any components in these folders will be configured to be a Nuxt Island. You can extend the folders by using the componentDirs option if you prefer your own convention. Setting up components in this dir will also allow you to reference the component using a shorthand instead of the full path.
For example, a component at ./components/OgImage/Foo.vue can be referenced as defineOgImage({ component: 'foo' }) (instead of the full path)
Otherwise, any island components set up with the previous convention will still work.
Let me know if you have any feedback on that :)

It also worked before with a component placed directly in the components folder and the server suffix (e.g. /components/CustomOg.server.vue) and referencing the component without full path. But I think it makes sense to place the OgImage specific components in a subfolder for readability. So if it works your new way, thanks a lot @harlan-zw for clarifying things with the new convention 😊


[FE + Version Control] Accessibility Insights Fast Pass: Section 508 502.3.1: (DevHome/button '') The Name property must not contain any characters in the private Unicode range.

The following accessibility issue needs investigation.
App: DevHome
Element path: button ''
Issue Details: The Name property must not contain any characters in the private Unicode range. Section 508 502.3.1
How To Fix: Modify the Name property, removing all characters in the range U E000 to U F8FF and replace them with meaningful, standard text content.
This accessibility issue was found using Accessibility Insights for Windows, a tool that helps debug and find accessibility issues earlier. Get more information and download this tool at https://aka.ms/AccessibilityInsights.

@ethanfangg can you clarify (visual tree path or owning type) that tells us which button this is referring to?

@DefaultRyan, @ssparach should know but let me also attach a screenshot of the Accessibility Insights tool analysis:

(I believe this has to do with the "Git" drop down)

@DefaultRyan, @ssparach should know but let me also attach a screenshot of the Accessibility Insights tool analysis:

(I believe this has to do with the "Git" drop down)

Yes, this has to do with hardcoding the name of the extension on the dropdown i.e. Git

I just ran the Accessibility Insights again on Canary 0.1701.612.0, and it's still reporting improperly named Button. It's the "..." next to the Dropdown.


Resolves Issue #217

I have made changes that would handle all regex and this also solves the Issue #217.
Thanks and Regards,
Henil Panchal

#build_preview

#delete_preview

#build_preview

#delete_preview


i18next script bug fix

address issue where frontend tranlation json files were not being converted to pot files

fix is to wait for i18next scanner to finish extracting json text before conversion.

@ivan-c ivan, let me know if you see issue, it worked in my instance after I made the fixes.

@ivan-c ivan, I think  this was an issue but we just didn't catch it. I think the context separator, one of the available options for the i18next converter is the culprit.  Let me know if you see anymore issue.


Added SMTP_METHOD variable to set delivery_method as smtp or async_smtp

Hi!
I created an variable to set smtp method as smtp or async_smtp. I think that is an option to set email as sendmail (issue 72). I don't know if this solution it's correct, but for me works :D
Do I need to change anything else?
Regards

@fbertux also please mention the SMTP_METHOD setting in the readme, with the possible settings

I changed the lines that you mentioned and I added a description on README.

this pull closes #72


Add missing sum of multiples test

Closes https://github.com/exercism/todo/issues/59.

This should complete https://github.com/exercism/todo/issues/20 in its entirety. These issues were not automatically closed when the pull requests were merged, but should be closed:

https://github.com/exercism/todo/issues/53
https://github.com/exercism/todo/issues/54

Thanks for following up--I often forget to go back and check these things! Closed them now.

Thanks!


Add support for kubelet HTTP endpoints

The kubelet readonly server (normally at :10255) listens for HTTP. The kubelet main server (normally at :10250) will also listen for HTTP when no TLS configuration is specified.
When attempting to issue commands through kubeletctl to a kubelet's HTTP endpoint, the following error occurs:
$ kubeletctl --server <IP_ADDRESS> --port 10255 pods
[*] Failed to run HTTP request with error: Get https://<IP_ADDRESS>:10255/pods: http: server gave HTTP response to HTTPS client

$ curl http://<IP_ADDRESS>:10255/pods # works
{"kind":"PodList","apiVersion":"v1", ... }

Consider adding support for HTTP, perhaps through a cmdline flag.
Also, great tool (:

Hi @YuvalAvra, thanks for the feedback! :)
I did some changes and added new flag --http and support on any port, it seems to work on my side, I will appreciate if you can check it again and let me know if it works on your side too.
By the way, the default IP is <IP_ADDRESS> so you don't need to use -s, you can use it like that:
kubeletctl --http --port 10255 pods

Thanks for the quick response, works on my side


HighNodeUtilization: support node steal when high nodes empty

HighNodeUtilization: support node steal when high nodes empty

❌ - login: @jandai-xx . The commit (7e247a4) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please submit a support request ticket.