Cross-server restores are not possible

The bullet points at the top of the article say that one of the options for restoring a database is to "Create a new database on any SQL Database server in the same region recovered to the point of the most recent backups."
This does not appear to be possible, at least not for single instance databases.
If you try to do this in the Azure Portal, the Target Server selector is locked and cannot be changed.
If you try to do this via Azure PowerShell, the Restore-AzureRmSqlDatabase cmdlet gives an error "Cross-server restores are not currently supported."
If cross-server restores are limited to certain types of database instances, or can only be executed in certain ways with certain tooling, please update the docs accordingly.

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

ID: de79f464-39dc-a5ad-0d9d-fab2ed248222
Version Independent ID: 6cf17fc7-3bdd-c419-8d9d-7d3067bb86ae
Content: Restore an Azure SQL database from a backup
Content Source: articles/sql-database/sql-database-recovery-using-backups.md
Service: sql-database
GitHub Login: @anosov1960
Microsoft Alias: sashan

Thank you for the detailed feedback.
We are actively investigating and will get back to you soon.

@tonesandtones
On your target database server, create a new database -> Select source -> Choose Backup.
You will be able to choose a backup from databases across servers and will be able to restore it.
Does that help clarify your question?
Please comment and let us know if you need any further clarification.

@MashaMSFT for awareness and visibility

@KalyanChanumolu-MSFT
Thanks for those instructions, creating a new database from backup (as opposed to restoring the existing database to a different server) has worked.
From reading the docs, it looks like in this case the correct PS cmdlet to use would be New-AzSqlDatabaseCopy instead of Restore-AzureRmSqlDatabase

Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

Hi @KalyanChanumolu-MSFT , can you please clarify if you're doing a point-in-time restore, or if you're doing a geo-restore? Thanks!

Hi @tonesandtones , it's been some time since we've heard from you so we have to assume that your issue has been resolved. As such, we will proceed with closing out this Git Issue. However, if you need further assistance, please reply to this Git Issue. Thanks for contacting Microsoft! #please-close

@MashaMSFT This issue should be reopened, as the documentation is still incorrect/misleading and we wasted a lot of time trying to figure out what was wrong. We are trying to do a point-in-time restore to a new server and the steps to do this are not clear nor documented.
https://docs.microsoft.com/en-us/azure/sql-database/sql-database-recovery-using-backups#point-in-time-restore - There is a screen shot that shows the lock icon next to Target Server, but there is no reference to it in the docs.

Hi @terrimorton , thanks for letting me know! Let me look into further. Thanks!

Hi @terrimorton, thanks for contacting Microsoft! I have reviewed this and I am not sure I understand which part is misleading. What were you trying to do and what wasn't working? Were you asking to get just an explanation of what the lock is into the documentation? Thanks!

We are simulating a disaster recovery and attempting to restore a Point in Time backup to a new server.
As stated, there is no explanation of the lock icon next to Target Server.  It states elsewhere in the docs that recovery to a different server is possible, but there is no explanation on how to do so.

Hi @terrimorton ,
Thank you for the clarification! So it looks like there may be some confusion. Geo-restore is possible to another server,  but point-in-time is not supported. It states so in the geo-restore section of the document:
Point-in-time restore on a geo-secondary is not currently supported.
The lock you're seeing indicates that you cannot change the server that you're restoring to.
I hope that helps and please let me know if you have any questions or concerns.
Thanks!

@MashaMSFT When I go to create a new database and select "Backup" as the data source it says "No available items.". It does this when I try it on both a brand new SQL server resource and on the server resource on which the original database exists. I know I have backups as I can see them in the portal under my-sql-server > Manage Backups > Available Long-Term Retention backups. Does the fact that they are not showing up mean they are not geo-replicated?
Additionally (and probably related), if I select one of those backups it pops open the "Long-term retention restore" blade where the "Target server" option is locked (with the little padlock icon described in other comments). This lock is there when trying restore from my-sql-database > Restore, both when "Point-in-time" and "Long-term backup retention" are selected.
I can not find any way to restore my database to another server within the Azure portal.

Hi @benmiller86, thanks for contacting Microsoft! Actually, restoring long-term retention backups to a different server is not supported via the portal. This can only done using PowerShell. Additionally, point in time restore backups in the same region are only supported on the same server.
I hope that helps and please let us know if we can be of further assistance.
Thanks again!
Masha from the SQL Docs team

@MashaMSFT then these docs that explicitly describe doing it via the portal need to be amended.

Hi @benmiller86 , ah you're referring to the geo-restore section? that's an interesting point, let me look into this. Thanks for bringing it to my attention!
Masha from the SQL Docs team

+1, it would be extremely valuable if these docs have a clear front and center documentation of geo-restore, point in time restore and import support across sku's  (hyperscale, business critical) and regions.  The trial and error approach has consumed an unfortunate amount of time and ultimiately we do find snippets through out the documentation however a single clear location across the 3 would be extremely helpful for the next person.


No operation displayed if min date = max date

In the search operation component, if the min date and max date are the same, no operation is displayed, even if there are operations done on this day.

Thanks for the report.

The selected min and max dates are off by two hours, which shift the selected date by one day. Timezones, anyone?


Feature/xivy 5006 mail

Looks good.
Did you see this: https://jenkins.ivyteam.io/view/scrum-master/job/market-connectors/job/master/

Yes, I was a little too fast yesterday. But the tests are adjusted and should pass now: https://jenkins.ivyteam.io/job/market-connectors/job/feature%252FXIVY-5006-mail/


git version check is incorrect when git is aliased to hub

The original problem was that zplug couldn't find a remote branch which I specified with at functionality. I dig into the problem and noticed that when git remote url is https://github.com git could find a remote branch while when url is<EMAIL_ADDRESS>git shows only master branch.
Then I looked through the source code and found if git version is over 2.3.0 it simply used https://github.com. My git version is 2.7.0, but I alias git to hub command, which version is 2.2.1.
So I guessed git version check is incorrect when git is aliased to hub command (and when hub version is lower than 2.3.0, maybe).

I understand your problem, please update zplug and try it out.

Now it works! Thanks for the quick fix!


Sprint 2 winter 2019

@frjo All tickets for winter sprint 2 have now been approved and are ready for deploying to live.
Changes
This branch includes the following work:

Adds the ability to batch assign reviewers to submissions
Adds the submissions by status page (not readily visible from the admin, see #869/#851 for links if required)
Adds the submission by status detail view (not readily visible from the admin, see #869/#851 for links if required)
Adds the ability to create and view Notes associated with submissions within the detail view
Detail views now display human friendly statuses
Ability to easily navigate statuses/rounds within the detail view through a dropdown
Adds a personalised rounds block to users dashboards

Migrations
There are no data migrations in this deployment.
There are no tables created by this deployment
All other changes impact the Meta properties of the tables only.


UI: Fix route to domain details

Description
This PR fixes router link to domain details

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[X] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity
Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[ ] Minor
[X] Trivial

Screenshots (if appropriate):
How Has This Been Tested?

@blueorangutan ui

@Pearl1594 a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_check_mark:
Live QA URL: http://qa.cloudstack.cloud:8080/client/pr/6086 (SL-JID-1237)

@Pearl1594 don't think it is related but getting error on navigation,

Yes @shwstppr  that's something I've been investigating.. It's not related to this PR.. I noticed this on the QA server too..

Hi @utchoang have any hint on what could be causing the navigation to back issue? It seems like when clicking the back button the wrong UUID is sent. Anyways this would need a separate issue


Merging dev to prod

Merging dev to prod

Will not work in firefox as ancestorOrigins is not supported on FF


chore(examples): update Convex React Query types

Update Convex, update @convex-dev/react-query to deal with new React Query types, and add a clear function to the public backing database.

@thomasballinger safe for merge?

@SeanCassiere yep, sorry about the changes coming in just as you were merging!


[Bug]: Puppeteer on GAE Flex (which uses npm ci) fails to install or find chromium

Bug description
Install 19.0.0 or later puppeteer (18.2.1 works) in a Google App Engine Flex project.
Launch the browser per example code in main.  Expect this error:
Error: Run npm install to download the correct Chromium revision (1056772)
Note everything works fine locally on Ubuntu 22.04.1
Puppeteer version
19.x.x
Node.js version
16.7.1
npm version
8.19.2
What operating system are you seeing the problem on?
Linux
Configuration file
No configuration file used

Relevant log output
Error: Run `npm install` to download the correct Chromium revision (1056772)
 at ChromeLauncher.resolveExecutablePath (/workspace/node_modules/puppeteer-core/lib/cjs/puppeteer/node/ProductLauncher.js:120:27)
 at ChromeLauncher.executablePath (/workspace/node_modules/puppeteer-core/lib/cjs/puppeteer/node/ChromeLauncher.js:166:25)
 at ChromeLauncher.launch (/workspace/node_modules/puppeteer-core/lib/cjs/puppeteer/node/ChromeLauncher.js:70:37)

Deployed this to a linux environment and also encountered this

Duplicate of #9162


Release 1.0

PR checklist

[ ] This comment contains a description of changes (with reason).
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] If you've added a new tool - have you followed the pipeline conventions in the contribution docs
[ ] If necessary, also make a PR on the nf-core/metatdenovo branch on the nf-core/test-datasets repository.
[ ] Make sure your code lints (nf-core lint).
[ ] Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).
[ ] Usage Documentation in docs/usage.md is updated.
[ ] Output Documentation in docs/output.md is updated.
[ ] CHANGELOG.md is updated.
[ ] README.md is updated (including new tool citations and authors/contributors).

PR for metatdenovo v1.0 release

Hi there, you re-requested a review. But it seems like that a bunch of my comments from my first review were not considered yet. Crucially I do not see any additional test profiles running in CI tests.

Hi Daniel, I made the changes we talked. We decided to not include those test that needs a database to be downloaded for the GitHub test. The user can still run them from the local machine.

Hi,
great that many more test profiles are now running automatically!
However, there are still many of my comments not addressed. Here the top two that should be changed (or convince me why not to change it):

conf/modules.config: mode: 'copy' to mode: params.publish_dir_mode
conf/test_rnaspades.config & conf/test.config: (some) links are to https://raw.githubusercontent.com/erikrikarddaniel but should be to https://raw.githubusercontent.com/nf-core

Hi Daniel,
I didn't see the other comments until today but I want through all of them now.

Looks good to me now, but why did you do 075d5b7 ???

Since mode: params.publish_dir_mode is at the top, I don't need to have it inside the modules. At least this is what I understood that line works.

Since mode: params.publish_dir_mode is at the top, I don't need to have it inside the modules. At least this is what I understood that line works.

Hm, I actually do not know, never tested it, but I assume mode: params.publish_dir_mode needs to be in each publishDir = [ ... ] construct. And it seems to me that this is indeed how nf-core pipelines do it (see rnaseq, sarek, ampliseq, mag), so I would follow their examples.

then I'll fix it

Danke sehr @d4straub!
Frohe Weihnacten!

Hi @mahesh-panchal I made changes as you suggested in the comments. KOfamscan and eggnogs now use storeDir while EUKulele does is download inside the module and we will keep it as it is.

I have a feeling that workflows/metatdenovo.nf is not the latest version. There's lot's of things marked resolved, but the changes haven't been made in this version.

Yes, I can see how changes that I made are not present anymore in the main workflow.. I will fix that!

Hi @mahesh-panchal I made new changes to your comments.

By the way, you can use the files changed tab to add all suggestions to a single commit.

By the way, you can use the files changed tab to add all suggestions to a single commit.

ah ok, good to know 😅


wsk action update does not support the --kind flag

While this is supported in the Python CLI, it is not for the Go CLI. I think (hope?) this is just an oversight.

You can update the kind if you also update the exec artifact. You cannot update the kind independently. This is a restriction from the API side. This prevents for example updating a swift action with a kind nodejs.

Once I discovered that (at least in the Python CLI) wsk action update will actually create the action if it does not yet exist, then I just stopped using wsk action create entirely. Sadly though, I can't do this with the Go CLI because update doesn't support --kind at all.

Resolved by : https://github.com/openwhisk/openwhisk/commit/b8f333497ff1df2b190ece2dc4f97a2f4eb683e8.


[5.5][Refactoring] Support refactoring calls to async if a variable or function is used as completion handler

Cherry-pick of https://github.com/apple/swift/pull/37314 into release/5.5

Explanation: Async refactoring previously failed if we were using a variable as a completion handler. For example, we couldn’t refactor wrapperAroundSimple to async.

func simple(completion: (String) -> Void) {}
func simple() async -> String {}

func wrapperAroundSimple(completionHandler: (String) -> Void) {
  simple(completion: completionHandler)
}

Now we generate
func wrapperAroundSimple() async {
  return await simple()
}

Similarly, we previously failed if a function was used as completion handler
func printResultOfSimple() {
  simple(completion: print)
}

We now generate
func printResultOfSimple() async {
  let result = await simple()
  print(result)
}

Scope: Async refactoring (add async alternative, convert to async, convert call to async)
Risk: Low (this only affects async refactoring)
Testing: Added new test cases to the refactoring test suite
Issue: rdar://77460524
Reviewer: Ben Barham (@bnbarham)

@swift-ci Please test

@swift-ci Please nominate


Add say_with_time around is_datacenter migration

Follow up to https://github.com/ManageIQ/manageiq/pull/7070
ping @jrafanie

I'm good with this.  Thanks @agrare.  :+1:


enableBuildConfigAsBytecode is provoking FileAlreadyExistsException

Current Behavior
We are using this configuration in the gradle.properties:
android.enableBuildConfigAsBytecode=true

Also, we have ksp.incremental=true.
We have many compilation failures (not always):
java.nio.file.FileAlreadyExistsException: /<project-path-name>build/app/build/generated/ksp/debug/<package-name>/BuildConfigUtils_Factory.java

Not 100% sure of the root cause, but I intuit this has been triggered after upgrading any of these libraries:
com.android.tools.build:gradle 8.3.1 -> 8.3.2
com.gradle.common-custom-user-data-gradle-plugin 1.13 -> 2.0
Expected Behavior
Compile as expected with KSP incremental and enableBuildConfigAsBytecode enabled.
Gradle version
8.6
Your Environment (optional)
Android Studio Iguana | 2023.2.1
Build #AI-232.10227.8.2321.11479570, built on February 21, 2024
Runtime version: 17.0.9+0-17.0.9b1087.7-11185874 aarch64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
macOS 14.4.1
GC: G1 Young Generation, G1 Old Generation
Memory: 8192M
Cores: 10

This is an issue with the Android Gradle Plugin, which is developed by Google and cannot be addressed in the Gradle Build Tool project. We also cannot just move the issue.
Please open such Android-related issues on the Android Issue Tracker at https://source.android.com/docs/setup/contribute/report-bugs#filing-a-bug
If you believe this is not an Android issue, please update with a reproducer that does not involve Android.

You are right, @ov7a!
Sorry for the inconvenience. :pray:
I already reported there.


Why the visualization results are bad

Hi,
Thank you for the exceptional code you provided! However, after running 500,000 iterations on the Building dataset and attempting to visualize the merged ".ply" file, I encountered unsatisfactory results in Meshlab, as illustrated below.

Can you assist me in identifying the reason behind the occurrence of this problem, please? Thanks!

Hi, from the image, I think the problem is you didn't visualize the points with their transparency/alpha values. You can try the alpha_visualizer provided by us to specifically visualize the points with alpha values.

@MiZhenxing Hi, thank you for your detailed reply.
I try the alpha_visualizer to visualize the merged points but have got the similar results:

Any solutions?
Thank you again for your awesome work and detailed reply!

Hi, could you check the ply file to see whether the alpha values are written correctly?

Hi, I think there might be something wrong when you generated the point clouds. Below are the results from my experiments.
The point clouds using alpha_visualizer.

The point clouds using meshlab:

The point clouds using meshlab with Dot Decorator:

I think you may check the detail arguments when generating the point clouds. You can also step into the _run_validation_points function to see whether the values are properly written into the ply file. You can also read the ply files and compute the mean / median of the alpha values to see whether they are in a reasonable range. Most of the alpha values are very small so the mean / median values should be small.


vmagent: build from victoriametrics derivation

Description of changes
fixes #306253
Main goal is to avoid having 2 definitions for building for the same repository (see linked issue).
This PR migrates the building of the client tool vmagent to the victoriametrics  package.
This deduplicates the code base on our side as upstream is maintaining and building everything from the same code base (so its a mono repo with different subpackages).
Beside just to split out vmagent, i tried to build up all logical packages that make sense to me, to that people can override the package easily to optimize the derivation size if needed.
One has now

the timeseries server
vmagent as pushing service
alterting tools
vmauth as HTTP proxy in case one wants to use authentication for the timeseries server
the backup tools to backup the timeseries
vmctl which is used to migrate between timeseries (vm to vm, but also from other servers to vm)
logging server

A pure minimal server then could just enable the withServer and disable everything else.
I personally switched my VM server for testing to just use withServer and withVmAuth (and withVmAgent to be able to push metrics to itself), beside that every other thing is disabled as i am not using it and it seems to run fine.
The said package is ~76MiB large.
The full package victoriametrics is about 162 MiB.
Vmagent by itself is be about 53 MiB (which we are migrating here and is about the same like the old).
I did check the functionality of the reduces package by looking at logs and verifying that my Grafana (with vm-datasource installed) is still able to query the data.
Vmagent is deployed to all my machines, checked the log on those also.
As the vmagent package had different maintainers listed, i migrated everyone to the victoriametrics package.
Please let me know if you disagree with that action @NULLx76 @leona-ya
As the action should be transparent for user of the vmagent package, i dont see a requirement to create a release note here.
I added a release note entry as Victoria metrics no longer provides vmagent by default as suggested in the PR comments.
In addition, i also added myself as a maintainer.

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/3916

I'm not quite sure why vmagent needs to be included in the normal victoriametrics package. Does it needs it for basic functioning (i.e. without the vmagent module probably?)?

It could be excluded, due sending metrics to the server itself was at least how I did configure it and then you don't need two derivations to install (as one could set the package in vmagent module then), but if it's preferred I can change the default

If it was included before by accident, we might as well disabled it.

If it was included before by accident, we might as well disabled it.

I am actually not sure if its by accident. I personally find it absolute useful as one might want to scrape the vmserver  as well.
But as it seems that others are not in favor of this use case (as its was pointed out that it could be an accident) and the freeze is over, i have pushed an update that removes vmagent from the victoriametrics package and added an entry for 24.11 release notes as it might break users setup otherwise.

did force push a migration to pkgs/by-name for vmagent.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/4079

@ofborg vmagent

@ofborg build vmagent

i think the disabling of the agent isn't the best choice personally, but it really doesn't matter and is strictly an opinion based choice

I am fine with both options, we have just to agree on one, initially I kept it enabled (as it's also my personal preference as pointed out in prior comments), I just switched as it was suggested.
@leona-ya , @SuperSandro2000 you both still prefer to exclude vmagent from the full VictoriaMectrics package, am I correct on this?

I don't really have a strong opinion right now. Can you two decide this?

it is very normal for stat gathering and monitoring tools to keep information on themselves 🤷♂

As I think the same (see previous comments) that it's a quite normal use case that a monitoring system also monitors itself I would flit the default in the next days unless @leona-ya reports a strong opinion against it.

Pushed a change that flips the vmagent args default on the package again to true and removed the release-note entry.
Also rebased on top of recent master.

@ofborg build vmagent victoriametrics


Find a way to use hibernate to query and use data from a file store

It would store the data as a file synchronised with git.
This would allow querying the data and use it in the app that gets generated as a static website.
The prerequisite is to have something easy to run in a CI (like github action) and that gives readable diffs for git.

Zulip discussion (https://quarkusio.zulipchat.com/#narrow/stream/187038-dev/topic/Json.20File.20JDBC.20driver) abstract:
Summary for GitHub Issue
Title: Implementing a JDBC Driver for JSON File Storage
Description:
Andy Damevin is exploring the possibility of using a JDBC driver to access and manipulate data stored in human-readable text files (preferably JSON) synchronized through Git. The goal is to allow easy data editing and storage in a format that supports version control and diffing, without requiring an additional runtime process.
Key Points:

Use Case: Similar to roq-data but using Hibernate. Accessing and modifying data from Quarkus with synchronization via Git.
Current Solutions:

H2 Database: Provides a file-based storage but results in binary-like data files.
CSV JDBC Drivers: Exist but are read-only and not suitable for the use case.
SQL Dumps: Suggested as an alternative, but it involves using traditional databases and exporting data.

Explored Options:

Implementing a custom JDBC driver for JSON/YAML files.
Considering existing solutions like Apache Drill, which supports JDBC drivers for various data stores.
Existing systems like Gatsby, which queries data and stores it as JSON for static use.

Discussion Highlights:

Yoann Rodière advised caution, noting that using JDBC for file-based storage is unconventional and might lead to challenges.
Max Andersen highlighted multiple historical and modern solutions for similar needs, emphasizing the variety of ways to manage data storage and synchronization.

Next Steps:

Further exploration of a custom JDBC driver for JSON/YAML.
Investigating Apache Drill and other potential tools for file-based JDBC connectivity.
Opening an issue to gather more insights and track progress on this exploration.

Links:

JSON JDBC Driver Example
CSV JDBC Driver (readonly)

Feel free to provide additional input or alternative solutions for efficiently managing and syncing human-readable file-based data storage through JDBC.

"Find a way to use hibernate to query and use data from a file store" - what is the queries you are after doing?

This is a good example: https://github.com/FroMage/RivieraDEV-Quarkus/tree/main/src/main/java/model

What I would do is:

Import YAML or JSON or whatever into ORM
Queries / mutation / whatever
Export back to YAML / JSON or whatever from ORM

Possibly using H2.


Identifiers validation failed for dataset Etapa final de la captura y catalogación del Herbario del Instituto de Ecología, A.C., Centro Regional del Bajío

Identifier validation failed for the dataset Etapa final de la captura y catalogación del Herbario del Instituto de Ecología, A.C., Centro Regional del Bajío:

Crawler attempt: 324
Publishing organization: Comisión nacional para el conocimiento y uso de la biodiversidad
Publishing country: MEXICO
Installation: IPTCONABIO
Number of occurrences indexed for this dataset at the time of the issue: 162306
Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 162207 total records; 162207 absent records
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3740035/step

New IDs sample:

Old IDs sample:

11ae483a6ab0162cf21ee5d7cabacfba
1f61a6071cbcb285d2cc755fa520a270
330ecf7078d88716fc11e055457c165b
812ab94416cf95fccba638e10772f655
cacc1e247bc1f2d6aa314df67559df4c
e0618073df040c8a579c1c825be38f4e
e3d954986ec9c27339c7efb9b401eac0
f1cfa1d163dd95cd2b9cca6544c02da2
0a6200558e50b109c6009f7f4b614d40
1001c92cf678bf351c4e890375a54e70

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Etapa final de la captura y catalogación del Herbario del Instituto de Ecología, A.C., Centro Regional del Bajío : https://doi.org/10.15468/dk7ca2.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

Identifier validation still  failing for the dataset Etapa final de la captura y catalogación del Herbario del Instituto de Ecología, A.C., Centro Regional del Bajío:

Crawler attempt: 325
Publishing organization: Comisión nacional para el conocimiento y uso de la biodiversidad
Publishing country: MEXICO
Installation: IPTCONABIO
Number of occurrences indexed for this dataset at the time of the issue: 162306
Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 162207 total records; 162207 absent records
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3740993/step

New IDs sample:

Old IDs sample:

11ae483a6ab0162cf21ee5d7cabacfba
1f61a6071cbcb285d2cc755fa520a270
330ecf7078d88716fc11e055457c165b
812ab94416cf95fccba638e10772f655
cacc1e247bc1f2d6aa314df67559df4c
e0618073df040c8a579c1c825be38f4e
e3d954986ec9c27339c7efb9b401eac0
f1cfa1d163dd95cd2b9cca6544c02da2
0a6200558e50b109c6009f7f4b614d40
1001c92cf678bf351c4e890375a54e70

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Etapa final de la captura y catalogación del Herbario del Instituto de Ecología, A.C., Centro Regional del Bajío : https://doi.org/10.15468/dk7ca2.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

Identifier validation still  failing for the dataset Etapa final de la captura y catalogación del Herbario del Instituto de Ecología, A.C., Centro Regional del Bajío:

Crawler attempt: 327
Publishing organization: Comisión nacional para el conocimiento y uso de la biodiversidad
Publishing country: MEXICO
Installation: IPTCONABIO
Number of occurrences indexed for this dataset at the time of the issue: 162306
Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 162207 total records; 162207 absent records
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3741635/step

New IDs sample:

Old IDs sample:

11ae483a6ab0162cf21ee5d7cabacfba
1f61a6071cbcb285d2cc755fa520a270
330ecf7078d88716fc11e055457c165b
812ab94416cf95fccba638e10772f655
cacc1e247bc1f2d6aa314df67559df4c
e0618073df040c8a579c1c825be38f4e
e3d954986ec9c27339c7efb9b401eac0
f1cfa1d163dd95cd2b9cca6544c02da2
0a6200558e50b109c6009f7f4b614d40
1001c92cf678bf351c4e890375a54e70

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Etapa final de la captura y catalogación del Herbario del Instituto de Ecología, A.C., Centro Regional del Bajío : https://doi.org/10.15468/dk7ca2.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.


CI (travis?)

done in:
https://github.com/SAP/chevrotain/commit/ca1347620d4991e610517e5f80b96f5477fd3160
https://github.com/SAP/chevrotain/commit/8cb30b400108197dfd1fded3294188462429a9f7
https://github.com/SAP/chevrotain/commit/c6c8e60d96db5de10d8bec4fe557041beebcff27
https://github.com/SAP/chevrotain/commit/1e25d21b4c66906186d78184ea1ec3608453e1bd


Move local alias file to the same folder the plugin is located in

My documents folder is littered with folders and configuration files created by programs, and my documents folder is synchronised to my OneDrive and, therefore, to my other computers. This isn't a file that I would ever need to interact directly with myself, and it makes more sense for it to be located in the plugin's directory in %LOCALAPPDATA%\Microsoft\PowerToys\PowerToys Run\Plugins\CurrencyConverter.

Storing configuration files in the same directory as the plugin is not ideal. This arrangement poses a risk that existing configurations could be inadvertently lost during a plugin upgrade. Additionally, if the PowerToys application is reinstalled to address a different issue, all files related to this plugin may also be deleted. Therefore, it is essential to keep the configuration files in a separate location from the plugin directory.
While I understand the desire to minimize interaction with these configurations, many users appreciate the ability to customize their settings for various reasons. Unless a universally acceptable alternative location can be proposed, changing the current setup is not feasible. Moreover, implementing a customizable location is currently not possible due to the lack of support for a file picker in PowerToys Run. As a result, designating a URL as a text field is not a viable solution.
The purpose of having configuration files is to allow user-specific customization rather than being limited by a standard imposed by the plugin. Therefore, the configuration files should reside in an easily accessible location.

Isn't that then the purpose of the %AppData% directory? If you want users to know where the file is, that information can be provided in the UI. Dropping a random file into your own folder in my documents folder doesn't necessarily make me more or less inclined to edit the file, especially if I can't even open it by default.

That makes sense to me, I will wait one more week to see if someone else has an opinion about this, otherwise, I will make the migration.

Hi, I believe we can move on with this implementation, I am attaching the build with the changes, please try it out and let me know your thoughts.
CurrencyConverter-1.4.0-ARM64.zip
CurrencyConverter-1.4.0-x64.zip

https://github.com/Advaith3600/PowerToys-Run-Currency-Converter/releases/tag/v1.5.0
The alias file can be located at %LOCALAPPDATA%\Microsoft\PowerToys\PowerToys Run\Settings\Plugins\Community.PowerToys.Run.Plugin.CurrencyConverter


Remove uglifyOnProduction from Node targets

What does this PR do?
This is a followup for #54 ... Node targets don't have uglification.
How should it be tested manually?
Read the lines I removed(?)

Pull Request Test Coverage Report for Build 195

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 193:
0.0%

Covered Lines:
1831

Relevant Lines:
1831

💛  - Coveralls


MameUI Download URL Broken

Bug Report
MameUI
Current Behaviour
Unable to install due to 404 when attempting to fetch archive. Download URL has been changed.
Expected Behaviour
Package should correctly download and install.
Additional context/output
N/A
Possible Solution
Change download URL in manifest. Fix has been tested on my machine, and hash still matches. File has simply been moved.
I can easily issue a PR to fix it, but the PR template specifies that a corresponding issue is required.
System details
Windows version: 11
OS architecture: 64bit
PowerShell version: 7.2.6
Additional software: N/A
Scoop Configuration

{
  "lastupdate": "2022-10-07T04:00:55.4267401-05:00",
  "aria2": "aria2-enabled",
  "SCOOP_REPO": "https://github.com/lukesampson/scoop",
  "SCOOP_BRANCH": "master",
  "aria2-enabled": false,
  "MSIEXTRACT_USE_LESSMSI": true,
  "aria2-warning-enabled": false
}

@isavegas  Thanks for reposting the issues.. Strange thing is that the bots that are responsible for these things (updating, formatting and maintaining specific manifests) do not do anything about that... Will try to look at that too in the future..
Is this the correct link? -> http://www.mameui.info/MAMEUI248.7z  ;
The one that states MAMEUI .248 'Final' (2022.09.27) ?
For now i'll add the mentioned link and file to the manifest

Yes, they appear to have simply renamed the file. The hash still matches. That should correct the issue. 👍

I think i've fixed it in the latest update.. Run scoop update && scoop install mameui  and see if it works for you. I'll close the issues for now, but can reopen it if something is not working properly and if it can be fixed from my end.


Kuiper 0.2.1 - Cannot  get message from edgex

edgex.yaml configuration as following, but cannot receive message.
Running env：Use 0.2.1 version, and compiled to native binary, EdgeX is Fuji, and used docker-compose in Ubuntu OS. Use app-service  pipeline mqtt and zmq to pub message, but Kuiper cannot receive any message.
default:
protocol: tcp
server: localhost
port: 5570   #What's port? EdgeX does not have this port, is ZeroMQ or MQTT port? It seems neither of both?
topic: events
serviceServer: http://localhost:10080  #What is port 10080？If it's /api/v1/valuedescriptor, it should be 48080 of edgex
#Override the global configurations
application_conf: #Conf_key
protocol: tcp
server: localhost
port: 5571
topic: application
Stream created, and no field definitions, but cannot receive any message.
root@ubuntu:~/kuiper/_build/kuiper-0.2.1-linux-amd64# bin/cli create stream demo'() WITH (FORMAT="JSON", TYPE="edgex")'
Connecting to <IP_ADDRESS>:20498...
Stream demo is created.

[1]+  Killed                  bin/cli query
root@ubuntu:~/kuiper/_build/kuiper-0.2.1-linux-amd64# bin/cli describe stream demo
Connecting to <IP_ADDRESS>:20498...

Fields
------------------------------------------------------

FORMAT: JSON
TYPE: edgex

root@ubuntu:~/kuiper/_build/kuiper-0.2.1-linux-amd64# bin/cli query
Connecting to <IP_ADDRESS>:20498...
kuiper > select * from demo;
Query was submit successfully.
kuiper >

Thanks for your feedback. Both of the 2 configurations are in file cmd/core-data/res/configuration.toml. We will change the default port configurations to the value that normally used in EdgeX.
[MessageQueue]
Protocol = 'tcp'
Host = '*'
Port = 5563
Type = 'zero'
Topic = 'events'

[Service]
...
Host = 'localhost'
Port = 48080
...

@jinfahua
The message can be retrieved, but there is a problem: the stream can only find the following format:
[{"rotationrate":2880}][{"temperature":27.56395}]
[{"humidity":95.48503}]
[{"bool":true}][{"rotationrate":4}][{"temperature":6.945715}]
[{"humidity":4.094852}]
[{"rotationrate":5819}][{"temperature":21.14119}]
[{"bool":false}]
[{"humidity":55.49818}]
[{"rotationrate":5442}][{"temperature":11.64447}]
But,the original fields of edgex events, such as devicename, id, orgin, cannot be obtained in the stream. The original format is maintained in the stream establishment. The original format is as follows:
{"id":"9ca84f73-c9dd-45be-b494-f6e4361e5c49","device":"RotationRate-Device","origin":1584355563897550720,"readings":[{"id":"2353187f-70c5-44fe-a434-928367c5cab4","origin":1584355563885392388,"device":"RotationRate-Device","name":"RotationRate","value":"1176"}]}
In addition, when sinking to edgex, the same format as above is also maintained.
So that the edgex pipeline can consume zmq message from kuiper normally, just like zmq (5563) which consumes edgex-core-data
Thank you very much!

@jinfahua
In addition, in an evnet, multiple readings may be encapsulated. There are two readings as follows, respectively RotationRate and Temperature:
{
"id": "9ca84f73-c9dd-45be-b494-f6e4361e5c49",
"device": "RotationRate-Device",
"origin":<PHONE_NUMBER>897550720,
"readings": [{
"id": "2353187f-70c5-44fe-a434-928367c5cab4",
"origin":<PHONE_NUMBER>885392388,
"device": "RotationRate-Device",
"name": "RotationRate",
"value": "1176"
},
{
"id": "2353187f-70c5-44fe-a434-928367c5cab5",
"origin":<PHONE_NUMBER>885392323,
"device": "RotationRate-Device",
"name": "Temperature",
"value": "30"
}
]
}
It is recommended to split it into streams, as shown below, so that it is convenient for business processing (such as conditional query), otherwise the query is troublesome
{
"id": "9ca84f73-c9dd-45be-b494-f6e4361e5c49",
"device": "RotationRate-Device",
"origin":<PHONE_NUMBER>897550720,
"readings": [{
"id": "2353187f-70c5-44fe-a434-928367c5cab4",
"origin":<PHONE_NUMBER>885392388,
"device": "RotationRate-Device",
"name": "RotationRate",
"value": "1176"
}
]
}
{
"id": "9ca84f73-c9dd-45be-b494-f6e4361e5c49",
"device": "RotationRate-Device",
"origin":<PHONE_NUMBER>897550720,
"readings": [
{
"id": "2353187f-70c5-44fe-a434-928367c5cab5",
"origin":<PHONE_NUMBER>885392323,
"device": "RotationRate-Device",
"name": "Temperature",
"value": "30"
}
]
}

@jinfahua
The message can be retrieved, but there is a problem: the stream can only find the following format:
[{"rotationrate":2880}][{"temperature":27.56395}]
[{"humidity":95.48503}]
[{"bool":true}][{"rotationrate":4}][{"temperature":6.945715}]
[{"humidity":4.094852}]
[{"rotationrate":5819}][{"temperature":21.14119}]
[{"bool":false}]
[{"humidity":55.49818}]
[{"rotationrate":5442}][{"temperature":11.64447}]
But,the original fields of edgex events, such as devicename, id, orgin, cannot be obtained in the stream. The edgex event original format is maintained in the stream establishment. The original format is as follows:
{
	"id": "9ca84f73-c9dd-45be-b494-f6e4361e5c49",
	"device": "RotationRate-Device",
	"origin":<PHONE_NUMBER>897550720,
	"readings": [{
		"id": "2353187f-70c5-44fe-a434-928367c5cab4",
		"origin":<PHONE_NUMBER>885392388,
		"device": "RotationRate-Device",
		"name": "RotationRate",
		"value": "1176"
	}]
}

In addition, when sinking to edgex, the same format as above is also maintained. So that the edgex pipeline can consume zmq message from kuiper normally, just like zmq (5563) which consumes edgex-core-data
Thank you very much!

@lesliechung88 Thanks for your feedback... Could you please read How to use meta function to extract additional data from EdgeX message bus?. We provided a function named meta to get these data.

In addition, when sinking to edgex, the same format as above is also maintained.
So that the edgex pipeline can consume zmq message from kuiper normally, just like zmq (5563) which consumes edgex-core-data

You could refer to this doc for how to send data to EdgeX message bus - the data sent to EdgeX message bus will be encoded.

@jinfahua
In addition, in an event, multiple readings may be encapsulated. There are two readings as follows, respectively RotationRate and Temperature:
{
	"id": "9ca84f73-c9dd-45be-b494-f6e4361e5c49",
	"device": "RotationRate-Device",
	"origin":<PHONE_NUMBER>897550720,
	"readings": [{
			"id": "2353187f-70c5-44fe-a434-928367c5cab4",
			"origin":<PHONE_NUMBER>885392388,
			"device": "RotationRate-Device",
			"name": "RotationRate",
			"value": "1176"
		},
		{
			"id": "2353187f-70c5-44fe-a434-928367c5cab5",
			"origin":<PHONE_NUMBER>885392323,
			"device": "RotationRate-Device",
			"name": "Temperature",
			"value": "30"
		}
	]
}

recommend to split it into streams, as shown below, so that it is convenient for business processing (such as conditional query), otherwise the query is troublesome
{
	"id": "9ca84f73-c9dd-45be-b494-f6e4361e5c49",
	"device": "RotationRate-Device",
	"origin":<PHONE_NUMBER>897550720,
	"readings": [{
			"id": "2353187f-70c5-44fe-a434-928367c5cab4",
			"origin":<PHONE_NUMBER>885392388,
			"device": "RotationRate-Device",
			"name": "RotationRate",
			"value": "1176"
		}
	]
}

{
	"id": "9ca84f73-c9dd-45be-b494-f6e4361e5c49",
	"device": "RotationRate-Device",
	"origin":<PHONE_NUMBER>897550720,
	"readings": [
		{
			"id": "2353187f-70c5-44fe-a434-928367c5cab5",
			"origin":<PHONE_NUMBER>885392323,
			"device": "RotationRate-Device",
			"name": "Temperature",
			"value": "30"
		}
	]
}

In the How to use meta function to extract additional data from EdgeX message bus?  describes how the data models are transferred from EdgeX to Kuiper.  We discussed the design with EdgeX App Working group, if you think your design is better than current solution, feel free to open another issue, so that we could have more detailed discussion.  Thanks!

@jinfahua
The message can be retrieved, but there is a problem: the stream can only find the following format:
[{"rotationrate":2880}][{"temperature":27.56395}]
[{"humidity":95.48503}]
[{"bool":true}][{"rotationrate":4}][{"temperature":6.945715}]
[{"humidity":4.094852}]
[{"rotationrate":5819}][{"temperature":21.14119}]
[{"bool":false}]
[{"humidity":55.49818}]
[{"rotationrate":5442}][{"temperature":11.64447}]
But,the original fields of edgex events, such as devicename, id, orgin, cannot be obtained in the stream. The edgex event original format is maintained in the stream establishment. The original format is as follows:
{
	"id": "9ca84f73-c9dd-45be-b494-f6e4361e5c49",
	"device": "RotationRate-Device",
	"origin":<PHONE_NUMBER>897550720,
	"readings": [{
		"id": "2353187f-70c5-44fe-a434-928367c5cab4",
		"origin":<PHONE_NUMBER>885392388,
		"device": "RotationRate-Device",
		"name": "RotationRate",
		"value": "1176"
	}]
}

In addition, when sinking to edgex, the same format as above is also maintained. So that the edgex pipeline can consume zmq message from kuiper normally, just like zmq (5563) which consumes edgex-core-data
Thank you very much!

@lesliechung88 Thanks for your feedback... Could you please read How to use meta function to extract additional data from EdgeX message bus?. We provided a function named meta to get these data.

@jinfahua
I used your way and encountered a new problem, how to assemble the following json format,
### readings is followed by an array object, as shown below
{
	"id": "9ca84f73-c9dd-45be-b494-f6e4361e5c49",
	"device": "RotationRate-Device",
	"origin":<PHONE_NUMBER>897550720,
	"**### readings**": **### [**{
		"id": "2353187f-70c5-44fe-a434-928367c5cab4",
		"origin":<PHONE_NUMBER>885392388,
		"device": "RotationRate-Device",
		"name": "RotationRate",
		"value": "1176"
	}**### ]**
}

@jinfahua
I used your way and encountered a new problem, how to assemble the following json format,
### readings is followed by an array object [ ], as shown below
{
	"id": "9ca84f73-c9dd-45be-b494-f6e4361e5c49",
	"device": "RotationRate-Device",
	"origin":<PHONE_NUMBER>897550720,
	"readings": [ {
		"id": "2353187f-70c5-44fe-a434-928367c5cab4",
		"origin":<PHONE_NUMBER>885392388,
		"device": "RotationRate-Device",
		"name": "RotationRate",
		"value": "1176"
	} ]
}

I need to sink this json format to edgex message bus

Now it's not supported. Could you please tell me what kind of case that you need to send the data back into EdgeX message bus with same format again?
If we decide to support add this feature, how to handle following case? Should we generate 2 readings for it, and what's the metadata value for t2 field?
SELECT temperature, temperature*1.3 as t2 FROM events

@jinfahua
I used your way and encountered a new problem, how to assemble the following json format,
### readings is followed by an array object [ ], as shown below
{
	"id": "9ca84f73-c9dd-45be-b494-f6e4361e5c49",
	"device": "RotationRate-Device",
	"origin":<PHONE_NUMBER>897550720,
	"readings": [ {
		"id": "2353187f-70c5-44fe-a434-928367c5cab4",
		"origin":<PHONE_NUMBER>885392388,
		"device": "RotationRate-Device",
		"name": "RotationRate",
		"value": "1176"
	} ]
}

I need to sink this json format to edgex message bus

Now it's not supported. Could you please tell me what kind of case that you need to send the data back into EdgeX message bus with same format again?
If we decide to support add this feature, how to handle following case? Should we generate 2 readings for it, and what's the metadata value for t2 field?
SELECT temperature, temperature*1.3 as t2 FROM events

@jinfahua
The scene is external data that flows into edgex through kuiper, such as:
Edge gateway-> emq-> kuiper-> edgex

@jinfahua
How is Kuiper currently implemented? Can edgex handle this sink? I think it also needs to be encapsulated into edgex event format zmq, which can be processed by edgex pipeline
{
       "edgex": {
         "protocol": "tcp",
         "host": "*",
         "port": 5571,
         "topic": "application",
         "contentType": "application / json"
       }
   }

In your scenario, where to get the metadata information for Events & Reading ?

@jinfahua
How is Kuiper currently implemented? Can edgex handle this sink? I think it also needs to be encapsulated into edgex event format zmq, which can be processed by edgex pipeline
{
       "edgex": {
         "protocol": "tcp",
         "host": "*",
         "port": 5571,
         "topic": "application",
         "contentType": "application / json"
       }
   }

Refer to this - https://github.com/emqx/kuiper/blob/master/xstream/sinks/edgex_sink.go

In your scenario, where to get the metadata information for Events & Reading ?

@jinfahua
The third-party gateway system only needs to send data to edgex according to the edgex event json protocol. It may not be part of edgex. The purpose of doing this is to take full advantage of the high throughput of EMQ and connect the third-party gateway data to edgex. Then edgex can Use the collected data to do more processing, such as collaboration, edge computing, and finally return the results to a third-party gateway through EMQ, or upload the received data directly to the cloud

@jinfahua
How is Kuiper currently implemented? Can edgex handle this sink? I think it also needs to be encapsulated into edgex event format zmq, which can be processed by edgex pipeline
{
       "edgex": {
         "protocol": "tcp",
         "host": "*",
         "port": 5571,
         "topic": "application",
         "contentType": "application / json"
       }
   }

Refer to this - https://github.com/emqx/kuiper/blob/master/xstream/sinks/edgex_sink.go
@jinfahua
I probably took a look at the code. Sink to edgex is a dynamic message mode. In this way, for each message, edgex needs to write the corresponding model adaptation. Currently, edgex cannot handle such messages, which increases the workload of the code.
Recommended to agree A json format (this format is the current event), which is convenient for processing

@lesliechung88 Thanks for your feedback. We also consulted this issue with EdgeX App group, and now we are planning to design a new solution for EdgeX sink.  A new enhancement is created for tracking the issue - https://github.com/emqx/kuiper/issues/187. Let's have discussion in that issue.


Error: The specified module could not be found.

Hi folks,
I'm not strong in C++, so sorry for stupid question :)
I compiled library, but i could not able to import it into project. I'm trying to build electron app, and during import i see this error:
module.js:583
  return process.dlopen(module, path._makeLong(filename));
                 ^

Error: The specified module could not be found.
\\?\C:\Users\Anton\Documents\Source\coverretriever\node_modules\taglib2\build\Release\taglib2.node
    at Error (native)
    at Object.Module._extensions..node (module.js:583:18)
    at Module.load (module.js:473:32)
    at tryModuleLoad (module.js:432:12)
    at Function.Module._load (module.js:424:3)
    at Module.require (module.js:483:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (C:\Users\Anton\Documents\Source\coverretriever\node_modules\taglib2\index.js:1:80)
    at Module._compile (module.js:556:32)
    at Object.Module._extensions..js (module.js:565:10)

I thought that also i need build taglib (1.11.1) library itself, but it did not help. Let me know if you need more info.

can you paste the output of npm install taglib2? Also, what version of windows are you on?

Hello @0x00A
log.txt
Windows 10 x64

Can you do ls on \Users\Anton\Documents\Source\coverretriever\node_modules\taglib2\build\?

sure.
build.txt
Also i packed build directory, in case if it help
build.zip

Hello Paolo,
Any update?

We've had terrible luck with windows so far, we're looking to hire someone who has some windows skills :)

This should be fixed in windows now.


Are there plans to make a version of Pytorch?

I want to do related work on this paper in the pytorch environment. Do you have any plans to release the pytorch version?

Thank you for your interests in our work. Currently I dont have enough time for a PyTorch re-implementation, but I will think about it later, as we may consider to extend it for a journal submission.


Add "CZ Project" filter to search results page

Describe the feature you'd like and what it will do
A clear and concise description of what you want to happen.
The search results page needs a "CZ Project" filter that provides the ability for users to select one or more CZ projects for filtering results.

Users should be able to select multiple projects.
Search results will be limited to those resources in the catalog that are affiliated with the selected project(s).
The list of projects should include the 9 CZNet thematic cluster projects and the legacy CZO projects.

Why is this feature important?
A short description of the importance of this feature and what it will help you achieve.
This will make it easy for users to isolate cataloged resources associated with one or more CZ projects.
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...].
Nope. Feature request.
Additional context
Add any other context or screenshots about the feature request here.
NA

This filter has been added.


FileNotFound amazonaws

Hello, when launching the application, on an Android 15 phone, with google services, using the Fdroid flavor, we can see in the logs the following error:
2024-05-19 14:38:57.472 27861-27950 DistanceConfigFetcher   xyz.malkki.neostumbler.fdroid.dev    W  error reading beacon data
      java.io.FileNotFoundException: https://s3.amazonaws.com/android-beacon-library/android-distance.json
    at com.android.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:255)
    at com.android.okhttp.internal.huc.DelegatingHttpsURLConnection.getInputStream(DelegatingHttpsURLConnection.java:211)
    at com.android.okhttp.internal.huc.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:30)
    at org.altbeacon.beacon.distance.DistanceConfigFetcher.request(DistanceConfigFetcher.java:94)
    at org.altbeacon.beacon.distance.ModelSpecificDistanceUpdater.doInBackground(ModelSpecificDistanceUpdater.java:28)
    at org.altbeacon.beacon.distance.ModelSpecificDistanceUpdater.doInBackground(ModelSpecificDistanceUpdater.java:16)
    at android.os.AsyncTask$3.call(AsyncTask.java:394)
    at java.util.concurrent.FutureTask.run(FutureTask.java:264)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
    at java.lang.Thread.run(Thread.java:1012)
2024-05-19 14:38:57.472 27861-27950 ModelSpeci...Calculator xyz.malkki.neostumbler.fdroid.dev
W  Cannot updated distance models from online database at java.io.FileNotFoundException: https://s3.amazonaws.com/android-beacon-library/android-distance.json

It doesn't seem to affect the rest of the behavior

Thanks for the report. I think this could be fixed by providing a stub implementation of the distance calculator to the beacon library (https://altbeacon.github.io/android-beacon-library/javadoc/org/altbeacon/beacon/Beacon.html#setDistanceCalculator(DistanceCalculator)). The estimated distance is not used in any way


A Few Issues found on Kubernetes

I am following k8s part on https://uber.github.io/fiber/getting-started/ and realized the following issues:

seems like k8s 'Job' only works in 'default' namespace ?
when I try on different namespace, the master pod keep failing and recreate.

poolwork pods terminate with 'Failed' status, while master pod returns 'Success'. Any way to address that ?

It looks like the k8s 'Job' must have explicit 'name' instead of 'generateName', otherwise master pod throws 'Pod not found' error. Is it known issue ?

Thanks

Hi @ericxu10101 , let me reply those questions inline:

seems like k8s 'Job' only works in 'default' namespace ? when I try on different namespace, the master pod keep failing and recreate.

That's true. Currently k8s jobs only work in 'default' namespace. It's a limitation of the current version. I'm planning to add that in the next version. Or if you have time, you can submit a PR for that.

poolwork pods terminate with 'Failed' status, while master pod returns 'Success'. Any way to address that ?

The pods failed most likely due to the daemon thread inside each worker pod which terminates the worker when it lose connection to the master. It' doesn't mean the whole job failed, it only means the worker exited in a special way. And it shouldn't affect the final result (If you notice something otherwise, please create a new issue for it). I'm planning to address this issue in the next version to make sure the exit status of worker pods can be correctly set.

It looks like the k8s 'Job' must have explicit 'name' instead of 'generateName', otherwise master pod throws 'Pod not found' error. Is it known issue ?

Currently 'name' is required for Fiber on K8s to work. Do you have a use case for 'generateName'? If it's general enough, it can be supported later.

@ericxu10101 issues 1 and 2 have been fixed in #29 and #28. Feel free to install the newest version from the current master branch and test it out. Regarding issue 3, do you have a further explanation of the details of the issue?

@calio thanks a lot. That' awesome! 3 is not actually an issue, just wanted to confirm the behavior. So seems like giving an explicit name instead of using 'generateName' is the current limitation.
I think supporting 'generateName' probably can be a future feature. It would be handy when scheduling the Job.

Hi @ericxu10101 , currently all features are tracked with Github issues. You can create a new issue with the tag "enhancement" and can track progress over there.

I'm getting urllib3 unable to establish connection in process.py with pi-estimation example. I am unable to resolve it. Tried giving all the permission but nothing seems to work. And also I'm getting this via running fiber cli.
  File "/usr/local/lib/python3.7/dist-packages/click/core.py", line 555, in invoke
    return callback(*args, **kwargs)
  File "/home/help_myjournal/.local/lib/python3.7/site-packages/fiber/cli.py", line 395, in run
    job = k8s_backend.create_job(job_spec)
  File "/home/help_myjournal/.local/lib/python3.7/site-packages/fiber/kubernetes_backend.py", line 171, in create_job
    raise e
  File "/home/help_myjournal/.local/lib/python3.7/site-packages/fiber/kubernetes_backend.py", line 168, in create_job
    self.default_namespace, body
  File "/home/help_myjournal/.local/lib/python3.7/site-packages/kubernetes/client/api/core_v1_api.py", line 7320, in create_namespaced_pod
    return self.create_namespaced_pod_with_http_info(namespace, body, **kwargs)  # noqa: E501
  File "/home/help_myjournal/.local/lib/python3.7/site-packages/kubernetes/client/api/core_v1_api.py", line 7429, in create_namespaced_pod_with_http_info
    collection_formats=collection_formats)
  File "/home/help_myjournal/.local/lib/python3.7/site-packages/kubernetes/client/api_client.py", line 353, in call_api
    _preload_content, _request_timeout, _host)
  File "/home/help_myjournal/.local/lib/python3.7/site-packages/kubernetes/client/api_client.py", line 184, in __call_api
    _request_timeout=_request_timeout)
  File "/home/help_myjournal/.local/lib/python3.7/site-packages/kubernetes/client/api_client.py", line 397, in request
    body=body)
  File "/home/help_myjournal/.local/lib/python3.7/site-packages/kubernetes/client/rest.py", line 280, in POST
    body=body)
  File "/home/help_myjournal/.local/lib/python3.7/site-packages/kubernetes/client/rest.py", line 233, in request
    raise ApiException(http_resp=r)
kubernetes.client.exceptions.ApiException: (501)
Reason: Unsupported method ('POST')
HTTP response headers: HTTPHeaderDict({'Server': 'BaseHTTP/0.3 Python/2.7.13', 'Date': 'Sun, 21 Feb 2021 11:26:45 GMT', 'Connection': 'close', 'Content-Type': 'text/html'})
HTTP response body:
<title>Error response</title>

Error response

Error code 501.

Message: Unsupported method ('POST').

Error code explanation: 501 = Server does not support this operation.

Anyone have idea what is happening here? Is it a bug?


unable to resolve module stream

when I run RN project on ios,it throw 'unable to resolve module stream' exception.But,android is fine.
OPTIONS:
ios 10.1
react-native 0.38.0
npm 3.10.3
node 6.3.1

I think modifying this line of code should solve this problem. I will release it tomorrow.

@oyyd sorry,it's my fault.
when I change the cheerio module to cheerio-without-node-native,not change the import.
import Cheerio from 'cheerio-without-node-native'
instead of
import Cheerio from 'cheerio'
Now.it's ok.Thanks!


Integration test fixes

Description of changes:

Remove invalid tests where current item is expected to be removed from recommendations. The endpoints do not support that functionality.
Fixed URL format syntax errors causing tests to fail.

Description of testing performed to validate your changes (required if pull request includes CloudFormation or source code changes):

Ran all integration tests against deployed service endpoints.

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

closing this one and see #397 to be merged with added fixes. @james-jory


As a developer, I want to ensure image dependencies are secure

Checked for duplicates
Yes - I've already checked
🧑🔬 User Persona(s)
Devops
💪 Motivation
...so that I can ensure the dependencies used in container images are secure and up-to-date.
A scanning tool such as Grype can ensure that package dependencies, operating system versions, and language-specific vulnerabilities do not end up in generated images. Combined with a pre-commit hook, this can prevent such security problems from proliferating into distributed images. GitHub Actions can ensure the safety of such images from contributions made without pre-commit hooks.
The SLIM community has an in-progress guide describing just this.
📖 Additional Details
No response
Acceptance Criteria
Given
When I perform
Then I expect
⚙ Engineering Details
No response
🎉 I&T
No response

Awesome @nutjob4life - interested to hear your experience with this tool and guide. SLIM is currently collecting feedback on how to improve the guide before we publish it to our site.

Starting with validate.

validate has many dependencies, some of them have vulnerabiliies.

@tloubrieu-jpl @nutjob4life do validate dependencies have vulnerabilities? between dependabot and sonatype, I am surprised we have not caught these. I monitor these closely.

@jordanpadams, yes, validate depended on pds4-jparser, which depended on pds-opencsv, which depended on commons-text:1.9, which had a critical vulnerability (detected using Grype, the container image-scanning tool).
Dependabot caught it roughly the same time I did!

Status: Completed on validate. Will add more sub-tasks for adding this other repos as they come up.
other higher priority repos in the future:

Registry API
Registry Loader Tools

Closed per https://github.com/NASA-PDS/validate/pull/1010. Will create new tasks for future expansion to other repos


Should we rename routeLegs[] into deliveryLegs[]?

In XML, this is called  (see 419 of 1747, Build V2R31_20211013 Date 2021-10-22).

papiNet 2024-01-31 CWG meeting decision: Yes, we should rename routeLegs[] to deliveryLegs[].


[ENH]: use ordered writing mode for full-text index creation

Description of changes
The full-text index writer now uses the ordered blockfile mutation mode.
1+ threads call .handle_batch() in parallel, which turns documents into a sorted flat Vec<u128> of encoded token instances. Then, write_to_blockfiles() does a k-merge on the lists of token instances and performs the actual blockfile set() / delete() calls.
Sadly, because we are still fundamentally bottle-necked by the blockfile writer, and because ordered blockfile writing is currently single threaded (possible in theory to make this parallelized in the future as long as the incoming mutations are sorted and larger than the block size), increasing parallelism of handle_batch() doesn't improve throughput that much:

(ignore time/thrpt diffs)
Based on my profiling removing locking from the blockfile writer would give a 10-15% perf bump so it's probably worth doing that in the near future.
Changes:

Removes Chroma's tokenizer abstraction. This was serving no purpose other than adding a layer of indirection and needless clones/buffering. We can add back this layer in the future if necessary, but it seemed unnecessary for now given we are always using Tantivy's ngram tokenizer.
Token frequencies are no longer tracked. I can add them back if necessary, but given that we don't use the frequency data it seemed like an unnecessary perf hit (I think the plan was to use the data to optimize trigram querying? which is no longer necessary in the short-term after my speedups on the querying side).

Test plan
How are these changes tested?

[x] Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Documentation Changes
Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs repository?
n/a

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#3065  👈
#3043
#3029
#2984
#2961
#2952 : 1 other dependent PR (#2953 )
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @codetheweb and the rest of your teammates on  Graphite

I am little bit hesitant to remove the frequencies, you need them to make the query side more intelligent and if we ever wanted to do that in the future we'd have to special case or backfill.

I am little bit hesitant to remove the frequencies, you need them to make the query side more intelligent and if we ever wanted to do that in the future we'd have to special case or backfill.

Ok, I'll see if there's a way to retain it with minimal perf impact. I think it may be difficult to do so without giving blockfile writers a closure-based writing function like we've discussed before. Without frequencies, there is minimal read IO on the write path. With frequencies, each token requires 1+ binary searches to find a possibly existing value and then needs to perform a write after combining the old and new values.

I am little bit hesitant to remove the frequencies, you need them to make the query side more intelligent and if we ever wanted to do that in the future we'd have to special case or backfill.

Ok, I'll see if there's a way to retain it with minimal perf impact. I think it may be difficult to do so without giving blockfile writers a closure-based writing function like we've discussed before. Without frequencies, there is minimal read IO on the write path. With frequencies, each token requires 1+ binary searches to find a possibly existing value and then needs to perform a write after combining the old and new values. (With a closure API, you could read the old value and perform the update inside a closure on an ordered writer, eliminating the binary searches.)

I think if there is a perf consideration, then lets leave it. We can always special case in the future if we need it and subsequent compactions can rebuild.


Support runtime with raw result.

Use case is phantomjs renders a page as PDF to stdout, I don't want that output to be passed through the decoding and extract result process.  I have a PR for this if it's wanted.

Please submit the PR.


Update headers in source file

[x] Remove empty line 1
[x] Update Presence to Presence_Fl, Presence_Br, Presence_Wa
[x] Remove empty 3 and 4
[x] Add column ID as first column

all four steps done


Create a working button paginator

Simple Embed paginator that I've been using for a while. Thought it could help others too.

Summary

This PR provides an example Embed paginator using Views (buttons). I believe the examples/views folder could use one.
Checklist

[ ] If code changes were made then they have been tested.

[ ] I have updated the documentation to reflect the changes.

[ ] This PR fixes an issue.
[ ] This PR adds something new (e.g. new method or parameters).
[ ] This PR is a breaking change (e.g. methods or parameters removed/renamed)
[x] This PR is not a code change (e.g. documentation, README, ...)

@ImAnAgent Is this being worked on? because it does not look good in its current state.


VrtNU extractor broken

Checklist

[x] I'm reporting a broken site support
[x] I've verified that I'm running youtube-dl version 2021.01.03
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[x] I've searched the bugtracker for similar issues including closed ones

Verbose log

[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-f', 'best', 'https://www.vrt.be/vrtnu/a-z/terzake/', '--verbose', '--print-traffic']
[debug] Encodings: locale UTF-8, fs utf-8, out utf-8, pref UTF-8
[debug] youtube-dl version 2021.01.03
[debug] Python version 3.9.1 (CPython) - Linux-5.9.14-arch1-1-x86_64-with-glibc2.32
[debug] exe versions: ffmpeg 4.3.1, ffprobe 4.3.1, rtmpdump 2.4
[debug] Proxy map: {}
[VrtNU] terzake: Downloading webpage
send: b'GET /vrtnu/a-z/terzake/ HTTP/1.1\r\nHost: www.vrt.be\r\nUser-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3775.5 Safari/537.36\r\nAccept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7\r\nAccept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8\r\nAccept-Encoding: gzip, deflate\r\nAccept-Language: en-us,en;q=0.5\r\nConnection: close\r\n\r\n'
reply: 'HTTP/1.1 200 OK\r\n'
header: Content-Type: text/html;charset=utf-8
header: Content-Length: 7721
header: Connection: close
header: Date: Thu, 07 Jan 2021 10:23:07 GMT
header: X-Content-Type-Options: nosniff
header: Expires: Thu, 07 Jan 2021 10:24:01 GMT
header: Cache-Control: max-age=300
header: X-UA-Compatible: IE=edge
header: Content-Encoding: gzip
header: X-Served-By: i-0632883e90d7e8d22
header: Accept-Ranges: bytes
header: Vary: Accept-Encoding
header: X-Cache: Miss from cloudfront
header: Via: 1.1 7d12bef71f48487e9202b581d949876e.cloudfront.net (CloudFront)
header: X-Amz-Cf-Pop: BRU50-C1
header: X-Amz-Cf-Id: TVWg6_jEmI_EI5KtRYQZEIYXxXz5UK52rlU9mc3BoKH_JVJTlOrIAw==
header: Age: 245
[VrtNU] terzake: Downloading JSON metadata
send: b'GET /vrtnu/a-z/terzake.mssecurevideo.json HTTP/1.1\r\nHost: www.vrt.be\r\nUser-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3775.5 Safari/537.36\r\nAccept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7\r\nAccept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8\r\nAccept-Encoding: gzip, deflate\r\nAccept-Language: en-us,en;q=0.5\r\nConnection: close\r\n\r\n'
reply: 'HTTP/1.1 410 Gone\r\n'
header: Content-Type: text/html; charset=utf-8
header: Content-Length: 238
header: Connection: close
header: Date: Thu, 07 Jan 2021 10:23:07 GMT
header: Server: Varnish
header: X-Varnish: 179536045
header: X-Robots-Tag: noindex, nofollow
header: Cache-Control: max-age=604800
header: Retry-After: 5
header: X-Cache: Error from cloudfront
header: Via: 1.1 32e3b86ae254a231182567c0124af893.cloudfront.net (CloudFront)
header: X-Amz-Cf-Pop: FRA2-C2
header: X-Amz-Cf-Id: 8fI1TmRF_DZywQ5k0BDRZfiAuK-ioTVYDRlO7EkzFRReDmL_e5A0vA==
ERROR: Unable to download JSON metadata: HTTP Error 410: Gone (caused by <HTTPError 410: 'Gone'>); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
  File "/usr/lib/python3.9/site-packages/youtube_dl/extractor/common.py", line 632, in _request_webpage
    return self._downloader.urlopen(url_or_request)
  File "/usr/lib/python3.9/site-packages/youtube_dl/YoutubeDL.py", line 2248, in urlopen
    return self._opener.open(req, timeout=self._socket_timeout)
  File "/usr/lib/python3.9/urllib/request.py", line 523, in open
    response = meth(req, response)
  File "/usr/lib/python3.9/urllib/request.py", line 632, in http_response
    response = self.parent.error(
  File "/usr/lib/python3.9/urllib/request.py", line 561, in error
    return self._call_chain(*args)
  File "/usr/lib/python3.9/urllib/request.py", line 494, in _call_chain
    result = func(*args)
  File "/usr/lib/python3.9/urllib/request.py", line 641, in http_error_default
    raise HTTPError(req.full_url, code, msg, hdrs, fp)

Description

The website vrt.nu has updated its delivery to akami and the relevant ID's seem to be located in a different json (eg: https://remix-cf-vrt.akamaized.net/remix/$ID/remix.ism/.m3u8). The mentioned ID is part of the json response from https://media-services-public.vrt.be. The origin of the request seems to originate from sentry (https://github.com/getsentry/sentry-javascript). I don't have the time to investigate further, hopefully i'll be looking in to this myself at a later date. Pointers on how to find the source of the magic json would be much gladly received.

#11873

#11873


new device mode blog post

New blog post about the new Device Mode. Please review @paulirish and @kaycebasques!

@crhym3 when I go to https://pr-2704-dot-weasel-dot-web-central.appspot.com/web/updates/devtools/?hl=en and then click on the new blog post ("A new device mode for a mobile-first generation") it redirects me to web-central.appspot.com. I haven't dug into it so it may just be the way that the page is coded, but I suspect it's related to the builder

@pbakaus what is the color value for the blue that you are using in the annotated screenshots? No issue, just want to make sure I use the same value.

@kaycebasques looking at src/jekyll/_layouts/updates/index.liquid, it generates cards with linkHref=article.canonical_url and canonical_url is, if I'm not mistaken:
site.config['WFAbsoluteUrl'] + getFilteredUrl()

where WFAbsoluteUrl is a hard-coded value for jekyll config.

@pbakaus please address my comments then LGTM

OK thanks @crhym3

Here's direct link to that article: https://pr-2704-dot-weasel-dot-web-central.appspot.com/web/updates/2016/03/device-mode-v2
It would be nice if WFAbsoluteUrl could be changed dynamically, e.g. from cmd line.

All changes addressed, good to merge. @petele what's up with that red scary looking label?

@pbakaus - used to make sure things that aren't ready aren't merged. In the future, please remove it when it's good to go!

@petele got it thanks, will do!


types in moduleIncludes block

[#6] includes the %{...%}  code block into the generated TS file. This is fine for constants but problematic for code that needs typing because jison's output isn't typescript-friendly. I'm tooling away on this now.

ts-jison seems to be working for this. See it in action in ShapePath.js.  I had to place the parser-internal types in ShapePathParserInternals.ts because the test-compiling the typecheck output wasn't find them even though they were in the same file.
It was a pretty big investment to create the typedict but it paid for itself many times over in catching type errors that would have had to bubble up through human-curated tests.

Nice!
Previously, as a workaround, I typically instructed the TS compiler to not typecheck JS files, and then created a parser.d.ts so I could import parser from "./parser";. But with ts-jison, this hack will no longer be necessary. Thanks!
Can I close this issue now, or is there something else that hasn't been addressed?


Wrong inheritance shown for .NET classes

Original GitHub issue https://github.com/dotnet/docs/issues/7083 from @kwalker360
I see two issues here:
(1) The C# code showing the class definition shows ManualResetEvent inherits from EventWaitHandle, but the Inheritence section shows it inherits from WaitHandle.
{2} The Reset() method is missing from the list of methods. (Fortunately it is discussed in the Remarks section and the link there works.)

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

ID: 43502a0b-0e55-14fb-1771-26630e891c68
Version Independent ID: 111d5b72-5469-93f2-f199-1456300225cd
Content: ManualResetEvent Class (System.Threading)
Content Source: xml/System.Threading/ManualResetEvent.xml
Product: dotnet-api
GitHub Login: @rpetrusha
Microsoft Alias: ronpet

Another issue re. the same problem with a great amount of detail: https://github.com/dotnet/docs/issues/6722

We are investigating this, thanks for the heads-up, @mairaw @kwalker360

#log-suggestion @dend

🚀 ATTENTION: Internal request logged.

@mairaw the issue with the inheritance is already tracked in #223. That said, the Reset method is now documented (see here) - it was part of the new documentation that we generated recently. I will close out this item with this new development 😄

@dend I don't think #223 discusses the same problem highlighted here. 223 is about the collapsing of interfaces when showing the signatures, this one was about not showing the appropriated inherited method for the selected platform because the hierarchy is different from one version to another but the system can't handle that.

@mairaw I will re-open this, good catch.

To add a few details here, the EcmaXml source lists two separate base types:
  <Base>
    <BaseTypeName>System.Threading.EventWaitHandle</BaseTypeName>
    <BaseTypeName FrameworkAlternate="netframework-1.1">System.Threading.WaitHandle</BaseTypeName>
  </Base>

And the first line of the remarks reads:

In the .NET Framework version 2.0, <xref:System.Threading.ManualResetEvent> derives from the new <xref:System.Threading.EventWaitHandle> class. A <xref:System.Threading.ManualResetEvent> is functionally equivalent to an <xref:System.Threading.EventWaitHandle> created with <xref:System.Threading.EventResetMode.ManualReset?displayProperty=nameWithType>.

So the metadata reflects this change in inheritance chain between versions ...

Another issue reporting the same problem: https://github.com/dotnet/docs/issues/8688

Can we change the title of this issue so I can more easily find when users report the same issue?
Maybe something like wrong inheritance shown for .NET classes or something.

Go for it!

Duh. I haven't realized I was the one who created the issue here 😄 Done.

(Thought you were just being polite, checking with others first. :-) )


🚧 WIP: add tests for the password forgot/reset/update endpoints

Work in progress. Not ready for merge.
Description of changes

controller test for forgot and model test for the generate_password_token! method that forgot uses

Issue Resolved

Fixes #

@robbkidd do you know if this is nearly ready?

I mean clearly the tests pass, we should merge and if he wants to do more we can take another PR

🤦♂ I've left this sit for so long I've forgotten what else there was to do.


Out of bounds memory access for 5->7 byte reads

Working on fuzzing and address sanitizer found an overflow
this test:
use prefix_uvarint::PrefixVarIntBuf;

#[test]
fn fuzz_one() {
    let decode_data = [240u8, 175, 59, 43, 0];
    let mut buf = decode_data.as_slice();
    let v = buf.get_prefix_varint::<u32>().unwrap();
    assert_eq!(v,<PHONE_NUMBER>);
}

when run as
RUSTFLAGS=-Zsanitizer=address cargo +nightly test -Zbuild-std --target x86_64-unknown-linux-gnu --test fuzz

will touch out of bounds memory because of this in raw.rs:131
else if tag < 0b11111111 {
        let len = tag.leading_ones() as usize + 1;
        let shift = (8 - len) * 8;
        let mask = !(u64::MAX << (len * 7));
        (
            (u64::from_be(std::ptr::read_unaligned(p as *const u64)) >> shift) & mask,
            len,
        )
    }

I have done this optimization before myself but then erred on the side of not doing for fear of the unknown. Is it safe in rust to read out of bounds if the resulting bytes are masked to only be valid? I think technically this could cause a segfault?

fixed by #9


CSS Overhaul, cards, color, detail page

Completely Changes CSS color scheme to Red and White(Temporary until we finalize color scheme and name), just messing with different ideas there.
Fixed card loading between different screen sizes, mobile vs. desktop.
Added shopping cart to the header and stretched it across the page, also moved Signup and Login buttons to the right side of Header
Made all image files on Cards the same size for uniformity.
Added margins to buttons and cards
Added margins on individual shoe page, going to make singular page card-like tomorrow with image on left side and description, price and add to cart buttons on the right.
Removed cart at bottom of the individual product page, will fix the close button on the cart tomorrow.
Add texture background tomorrow for shoe page
Add jumbotron or some kind of visual element on website load, video or picture with about me section maybe?
Need to revamp signup and login pages.
Logo and finalize name tomorrow as well.

LGTM!


[build] post-release modifications

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 97.81%. Comparing base (ba59ffc) to head (4722d9d).
Report is 2 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main      #20   +/-   ##
=======================================
  Coverage   97.81%   97.81%
=======================================
  Files          63       63
  Lines        1922     1922
=======================================
  Hits         1880     1880
  Misses         42       42

Flag
Coverage Δ

unittests
97.81% <ø> (ø)

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


MyThings view tests

Add tests for the MyThings view. This may include tests for creating new Things.

I've finished issue #46, and am going to continue.

I added a shallow render test, but after the refactor, there isn't a whole lot to test. Closing this issue and opening new ones for different components.


if leaving nested route, child page is unmounted before suspense resolves

stackblitz.com/edit/github-f4gpfk-qhgrfy?file=pages/test.vue

https://github.com/nuxt/nuxt/issues/13814#issuecomment-1544828371

I am having a similar problem. Only the child, not parent, of the new nested page are being set up before page:start so child can't receive props properly from async parent

@daehyun-thevc would you post a reproduction so when we resolve this we can verify your use case is also covered?

https://stackblitz.com/edit/github-szoey5?file=pages/index.vue
when navigating from /basecamp to /mountain which is async nested route, mountain/index.vue implements setup function before mountain.vue implements setup function, so there is undefined prop mountainTitle

https://stackblitz.com/edit/github-szoey5?file=pages/index.vue
when navigating from /basecamp to /mountain which is async nested route, mountain/index.vue implements setup function before mountain.vue implements setup function, so there is undefined prop mountain

I know this is being a bit pushy, but this issue is kinda related to the suspensible issue that Vue 3.3 fixed, but unfortunately hasn't fixed that specifically. I'd totally appreciate it (and I hope more that have this issue upvote it) if it got fixed already, I've been waiting months and this is the only major issue I have with Nuxt right now. 🚀

Heya yep. I agree that this needs a bit of priority. I am half way in my project and we keep building it hoping this will be fixed soon. Just that user experience is not very good with half of the page missing whenever change route.
Is there any workaround during the meantime?


Content missing?

José, unless I'm missing something, this repo doesn't contain anything other than read-me files. Is this not where you intend to share the ipython notebooks?

You are correct. I plan to share the Extras content from the book here. Still working on it. I'm planning to have much of the material up by the end of this summer.
Thanks for your patience!
Jose


[bug] xDismFeature fails silently when parent features are required

Set-TargetResource is invoked and ends successfully even though following error is reported:
dism /online /enable-feature -featurename:IIS-ASPNET45
Deployment Image Servicing and Management tool
Version: 6.3.9600.17031
Image Version: 6.3.9600.17031
Enabling feature(s)
[==========================100.0%==========================]
Error: 50
The operation is complete but IIS-ASPNET45 feature was not enabled.
A required parent feature may not be enabled. You can use the /enable-feature /a
ll option to automatically enable each parent feature from the following list. I
f the parent feature(s) are already enabled, refer to the log file for further d
iagnostics.
IIS-NetFxExtensibility45
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
dism /online /enable-feature /featurename:IIS-ASPNET45 /all
Deployment Image Servicing and Management tool
Version: 6.3.9600.17031
Image Version: 6.3.9600.17031
Enabling feature(s)
[==========================100.0%==========================]
The operation completed successfully.

See https://github.com/PowerShell/xDismFeature/pull/1


Feature/grep n

implemented n option for grep

Codecov Report

Merging #1057 (5db549b) into master (ad91197) will decrease coverage by 0.81%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #1057      +/-   ##
==========================================
- Coverage   97.14%   96.32%   -0.82%
==========================================
  Files          35       35
  Lines        1332     1335       +3
==========================================
- Hits         1294     1286       -8
- Misses         38       49      +11

Impacted Files
Coverage Δ

src/grep.js
100.00% <100.00%> (ø)

src/which.js
80.00% <0.00%> (-15.00%)
:arrow_down:

src/cmd.js
94.11% <0.00%> (-5.89%)
:arrow_down:

src/find.js
95.45% <0.00%> (-4.55%)
:arrow_down:

src/ln.js
96.87% <0.00%> (-3.13%)
:arrow_down:

src/ls.js
97.67% <0.00%> (-2.33%)
:arrow_down:

Continue to review full report at Codecov.

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


Moving kopia logging from util/logging to remove kopia from indirect dependency in velero plugins

when running go mod why -m github.com/kopia/kopia in velero-plugins prior to this change you will see following
❯ go mod why -m github.com/kopia/kopia
github.com/konveyor/openshift-velero-plugin/velero-plugins
github.com/vmware-tanzu/velero/pkg/plugin/framework
github.com/vmware-tanzu/velero/pkg/util/logging
github.com/kopia/kopia/repo/logging

after
❯ go mod why -m github.com/kopia/kopia
(main module does not need module github.com/kopia/kopia)

Signed-off-by: Tiger Kaovilai<EMAIL_ADDRESS>Thank you for contributing to Velero!
Please add a summary of your change
Does your change fix a particular issue?
Fixes #(issue)
Please indicate you've done the following:

[ ] Accepted the DCO. Commits without the DCO will delay acceptance.
[ ] Created a changelog file or added /kind changelog-not-required as a comment on this pull request.
[ ] Updated the corresponding documentation in site/content/docs/main.

This looks like a good change. We should post upstream too, and we can remove this commit when we pull it in from upstream.

Ok

Upstream PR https://github.com/vmware-tanzu/velero/pull/6484

/cc @shawn-hurley @sseago @shubham-pampattiwar carry this cp? I wonder if upstream change will be cp to release-1.11

maybe create a 1.11 PR and see ?

Lets pull this in now and if/when it's pulled into a 1.11.z release, we can drop it in favor of what's in the release. It may well be that 1.11.1 comes out before the change is pulled into 1.11 branch, so upstream may not get it until 1.11.2.

closing due to https://github.com/vmware-tanzu/velero/pull/6484 merging. Will be cherrypicking from upstream.


bug/HTML files with extension .htm  raises Invalid file error File type not support in partition.

Describe the bug
Cannot partition HTML files with file extension .htm. It raises the error
File "/usr/local/lib/python3.10/site-packages/unstructured/partition/auto.py", line 72, in partition
    raise ValueError(f"{msg}. File type not support in partition.")
ValueError: Invalid file example.htm. File type not support in partition.

To Reproduce
Partition a html file with extension .htm the following code
from unstructured.partition.auto import partition
file_path = `example.htm`
partition(filename=file_path)

A workaround is to rename the file from example.htm to example.html. This makes it accept the file as a valid HTML file.
Expected behavior
It should return the partitions for the HTML file.
Desktop (please complete the following information):

OS: Linux and Mac.
Python version: 3.10.11

Hi @obi-a, thanks for reporting this bug! I've fixed it, cheers.


Use file-based locking when persisting cookies.

This is a proposal for file-based locking and merging when persisting cookies.
Tests and docs are missing. I'd add them when the overall implementation is finalized.
Let me know if there are major flaws.

Thanks @dullgiulio for this, it looks like a nice start. I've commented on a few things that might need some thought. Also as you pointed out it could do with documentation and tests.

Superceded by PR #6


Unable to run workflow if non-runtime configurable variables are configured

Describe the bug

Steps to reproduce

Create a workflow and add a variable that does not enable runtime-configurable.

Run the workflow.

Result

Shows variables that can't be overwritten.

Directly executed the workflow without filling in a variable value. Returned an error.

Filled in a value and then execute. Returned an error too.

Check GET workflow api response.

Expected behavior

Do not display the variables that can't be overwritten.
Environment

Walrus version: f94d57de903a925f2bd72d34b5aa1eaf8213f6ad
UI version: dev-c05317a

Additional context
Add any other context about the problem here.

Environment
Walrus version: v0.4.0-rc2
UI version: v0.4.0-rc2
Test Result: Pass


Product Model

For bugs, please include the following:

What is the expected behavior?
What is the actual behavior?
What steps reproduce the behavior?

For features, please specify at least minimal requirements, e.g.:

"As a user, I want a notification badge showing unread count, so I can easily manage my messages"
"As a developer, I want linting to work properly with JSX, so I can see when there is a mistake"
"As an admin, I want a management panel for users, so I can delete spurious accounts"

Build the product model.

Done and merged into master


[Bug]: Appsmith crash when create an API pointing to Github hosted json

Is there an existing issue for this?

[X] I have searched the existing issues

Description
We saw an issue where Appsmith crashed for users when they created an API with URL as  https://raw.githubusercontent.com/dmfilipenko/timezones.json/master/timezones.json and hit run to it.
Steps To Reproduce

Create a new API
URL = https://raw.githubusercontent.com/dmfilipenko/timezones.json/master/timezones.json and hit run to it

Public Sample App
https://release.app.appsmith.com/app/dynamically-change-input-text/page1-62729b10bf58a33d4ce4cedb/edit
Version
1.7.1

[ ]  1755 [Testcase]: [Bug]: Appsmith crash when create an API pointing to Github hosted json

I believe I am seeing this same issue for a custom API I am integrating with. When executing, or now even when just browsing to the query page, I see the error "Oops! Something went wrong". My API is returning JSON data.

The issue still exists https://www.loom.com/share/6041f202ba5848a7a4715da0f0bb8a6c

@yatinappsmith Its working fine for me. Can you try once again. If repeated can you share your app with me so that i can debug.

Image was not built at that point of time. Now it's working in release also. Closing this issue.


Fix build break on system without O_CLOEXEC

On system without O_CLOEXEC, HAVE_O_CLOEXEC is defined as 0 in include/port/port_config.h, not undefined.  Therefore, the right way to test it is "#if HAVE_O_CLOEXEC" rather than "#if defined(...)".

Also see https://github.com/google/leveldb/pull/1028.