crud module generator - page not found error

I created a crud using yo:
yo meanjs:crud-module product

it generated all the files, when I want to create a new product (http://localhost:3000/products/create), after filling the name and clicking on create, it will go to the page not found page http://localhost:3000/not-found, I think something is wrong with the routing generation.
p.s: I used this version meanjs-mean-0.5.0-7-gd37b603.zip

Note that I got 404 (Not Found) error for this page when I submit the form http://localhost:3000/products/api/products, it should be this page?

Hi There,
I am having the same issue! I created a module jobs using yo meanjs and when i try to make a new job, it goes to: http://localhost:3000/not-found
I am using version 0.5.0

my too..
I got the same situation, 404 ...

@Aleyasen As a workaround, until the problem is fixed, simply try to "copy and paste" the article module, and call this new folder "product". Use your favorite text editor, or any other tool that your might prefer, and recursively replace (in this new product folder) all "article" text with "product", and all "Article" text with "Product". It should work, hope it helps.

Forget the Yo generator, something like this is all you need:
#!/bin/bash

# Generate new CRUD module for MEAN.js based on an *unmodified* articles module.

echo -n "Enter the singular lowercase name for your module (i.e. product): "
read NEWMODULE

PLURAL="$NEWMODULE"s
CAPITALISED="${NEWMODULE^}"

echo "Copying articles folder..."
cp -r articles/ $PLURAL

echo "Replacing filenames..."
find $PLURAL -name "*" -type f -exec rename "s/article/$NEWMODULE/" {} ";"

echo "Replacing article with $NEWMODULE..."
find $PLURAL -name "*" -type f -print0 | xargs -0 sed -i'' -e "s/article/$NEWMODULE/g"

echo "Replacing Article with $CAPITALISED..."
find $PLURAL -name "*" -type f -print0 | xargs -0 sed -i'' -e "s/Article/$CAPITALISED/g"

Save it in the same folder as an original MEAN articles folder as newmodule.sh
chmod +x newmodule.sh
./newmodule.sh

@hyperreality I was also want to explicitly control the plural name as well.. so adding an input for PLURAL. e.g. OrderStatuses

@mleanos the plural is only used for the folder name, so you can easily rename that if you like

A simple fix did it for me!
Look for the generated client service file, for example if your module is named products the file can be found at /modules/products/client/services/products.client.service.js. Find the following line:
return $resource('api/properties/:propertyId', { and add a slash before the api. So it needs to be
return $resource('/api/properties/:propertyId', {
The post request was set to a wrong url (/products/api/products/ in my case). So adding the slash fixed the url and the request is correct again.
Hope this works for you too!

Many thanks

if a pull request with this fix hasn't been submitted I would like to do so

@nickwilliamsnewby Are you offering to submit a PR to the generator project? If so, that would be greatly appreciated. Getting the generator up-to-date would be very helpful to user's of MEAN.js.

@mleanos I wasn't aware i could pull request it by myself, sorry for that. I created a pull request for correction right now. Still thanks, it's a great generator.

I still got the problem. The fix suggested by @torbenkorb did not work for me. Instead I did the following:

Created new CRUD module using yo
Open the myModule.client.routes.js file and updated the templateUrl for each route.

Note that the route should be "modules/myModule/views/list-myModule.client.view.html" (as the Article routes) instead they are created with additional folder in the path like "modules/myModule/client/views/list-myModule.client.view.html'" I just deleted the additional folder and the module was OK.


[text analytics] Use AzureKeyCredential from core instead of TextAnalyticsKeyCredential

rebased off https://github.com/Azure/azure-sdk-for-python/pull/10509
fixes #10507

Can one of the admins verify this patch?


Kernel keeps on dying when trying arnheim_3.ipynb

When trying to run arnheim_3.ipynb on local machine, the kernel keeps on dying when executing output = ct.loop(). There no errors before this piece of code. Could you please tell me how to resolve it?

For others who are facing this issue, set the gui flag to false and it should work


How to use this library for chroot?

I try to used
env LD_PRELOAD=“/path/to/libandroid-shmem.so” chroot /rootfs /bin/su -l
But he told me, could not find the file or directory.
If I only use chroot /rootfs /bin/su -l ,will enter the system.
I am sure the library file directory is correct and given permission.
@pelya

it needs Android Dynamic Linker in order to be loaded (usually in /system/lib/linker or something)


Don't throw in the server on certain unsub messages

To use an object as a map with arbitrary keys, you should either use
Object.create(null) or the Map class.  Otherwise you can run into trouble
where keys like toString and constructor are in your app too.
Noticed while reviewing @Urigo 's PR

Thanks @glasser!


✨ mailtrap support send with template method

@JohnCampionJr
I have completed the implementation of email template support for Mailtrap. Please review it, and if it's acceptable, I hope it can be merged it


dbm devcontainer

What does this PR do?
This PR adds devcontainer for DBM integrations (postgres, mysql & sqlserver) with necessary drivers installed to run unit/e2e tests on Mac with arm64 architecture.
platform: linux/amd64 is added to sqlserver docker-compose due to lack of arm64 arch support for mssql images.
Motivation
Develop & test DBM integrations on mac
Additional Notes

Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Changelog entries must be created for modifications to shipped code
[ ] Add the qa/skip-qa label if the PR doesn't need to be tested during QA.

Hey 👋 I would recommend that you add the following line to the end of the .github/CODEOWNERS file:
/.devcontainer/dbm                                                        @DataDog/database-monitoring-agent


Hide pub get output when updating flutter tool

Fixes https://github.com/flutter/flutter.github.io/issues/100

@sethladd

@krisgiesing

LGTM


Pass through micrometer and metric_type tags

Allow the following tags to be forwarded along with the metrics to the trends backend :

micrometer_metrics
metric_type

This allows the backend to know the source of the metric if it is originating from the newer runtimes using the micrometer library or the older runtimes.

looks good to me


Handling lot of markers in localstorage

Hi,
I'm handling a lot of Markeers, 30K +.
So I would like to store in localstorage my marker list just calling that method:
markers.addLayers(markerList);
I tried to do JSON.stringify(markerList) but I have an error like this:
Uncaught TypeError: Converting circular structure to JSON
Here is the code that I wanted to make work:
sessionStorage.setItem('contacts', JSON.stringify(markerList));
markers.addLayers(JSON.parse(sessionStorage.getItem('contacts')));
Is there any ways to store locally this collection of Leaflet Markers ?
Thanks you

Use markerList.toGeoJSON() instead of JSON.stringify(markerList). To add it you could use geojson layer


Use Git for lawrencium dep

Continuation of #46. The needed changes upstream haven't been published on crates.io yet, so we need to source the dep from GitHub until further developments arise. I was about to make this change in the previous PR but it was merged 😅
Warning, untested! Should work, but not a hundred percent confident on whether I specified the commit hash correctly. If it builds, should mean its fine.

Sorry about that! I was over-eager to merge. I just ran your changes and it all looks good. So I'll merge this one as well.
Thanks!
Also free free to open issues (or pull requests) if you run into any problems or would like to add features. I've been mostly using a Mac lately so that's where my focus has gone, but most Windows issues should be relatively straightforward to fix.

Sorry about that! I was over-eager to merge. I just ran your changes and it all looks good. So I'll merge this one as well.
Thanks!
Also free free to open issues (or pull requests) if you run into any problems or would like to add features. I've been mostly using a Mac lately so that's where my focus has gone, but most Windows issues should be relatively straightforward to fix.


[R] mx.io.arrayiter shuffing is disabled

mx.io.arrayiter shuffling option is no longer working, the option only result in the first and last samples to be swapped. Likely appeared at the same time that mx.runif stopped working as well.
> mx.set.seed(44)
> x = mx.io.arrayiter(data = 1:10, label = 1:10, shuffle = T, batch.size = 10)
> x$reset()
> x$iter.next()
[1] TRUE
> x$value()
$data
 [1]  2  3  4  5  6  7  8  9 10  1

$label
 [1]  2  3  4  5  6  7  8  9 10  1

>
> mx.set.seed(21)
> y = mx.io.arrayiter(data = 1:10, label = 1:10, shuffle = T, batch.size = 10)
> y$reset()
> y$iter.next()
[1] TRUE
> y$value()
$data
 [1]  2  3  4  5  6  7  9  8 10  1

$label
 [1]  2  3  4  5  6  7  9  8 10  1

@thirdwing Can you please take a look?

This issue is not reproducible on Mac with my RStudio installation. But I am able to reproduce it on one of my EC2 instances.
The only difference in the two installations is the mxnet version -
In Mac I am running
other attached packages:
[1] mxnet_0.10.1

whereas on the ubuntu installation I am running the latest version -
other attached packages:
[1] mxnet_1.2.0

The root cause of the problem is the behavior of mxnet's uniform distribution generator which is internally used for shuffling the arrayiter object.
On the old code, I get the following
> mx.runif(shape=10, min=0, max=1, ctx=mx.cpu())
 [1] 0.04804938 0.65167809 0.77450776 0.67896259 0.21799077 0.29066718 0.08128081 0.97726691 0.04218456 0.40008616

On the latest mxnet v1.2 I get the following -
> mx.runif(shape=10, min=0, max=1, ctx=mx.cpu())
 [1] 1.168184e-35 0.000000e+00 0.000000e+00 2.522337e-44 0.000000e+00
 [6] 0.000000e+00 1.401298e-45 0.000000e+00 6.726233e-44 0.000000e+00

Similar errors exist for the mx.rnorm too in the latest code.

@sandeep-krishnamurthy please close this issue. It has been fixed.


Create DOC.yml

This PR deploys our documentation to GitHub pages, rather than RTD. See #273 for details. I'll not remove RTD because it's still in use for PR builds.

Also not sure if this workflow works, so there's also that.


Add new function to generate graphs from csv files.

Function requirements:

create a utility that read the csv and check the size if suitable.
call the chatbot function with the right prompt to generate html page with graphs.
return the html to the user.
create utility to save the retuned the returned html for render.
create unit test case for the function.

the csv to html file graph is implemented without the utility part.
const csv_str_data = '<your csv as string>'
const topic = "<the csv topic>";

const htmlCode = await Gen.generate_dashboard(csv_str_data, topic, openaiKey, num_graphs=2);

Connection utilities will be implemented at later stage.


AEM 6.4 defaults to disabled crxde causing integration testing to fail

AEM 6.3 and prior used to default to enabled crxde, hence the integration test against vanilla AEM installation expects crxde status to be disabled.
This test is failing in 6.4, the test has to be modified so that it disables crxde prior to checking the state, ensuring the condition to be met prior to checking.

Fixed in 2.0.0 .


Suggestion: log methods should not throw

I think that any of the log methods (.debug(), .info() etc.) should not cause a program to crash and therefore should not throw.
I notice that you throw for usage errors, which is helpful for the programmer who is implementing log messages, but what about the case where a programmer adds a log for a code path which is both a) not covered in automated tests, and b) in a code path which is rarely hit? Or what about when the arguments provided are different in some production context?
What if canopi had a "strict" mode which the user can set, but which defaults to being "on" when NODE_ENV !== 'production'?

Although Canopi throws some exceptions in the log methods, it then catches them and logs them. Constructing the Canopi object can throw an unhandled exception, however.
I do like your suggestion of a strict mode, however I don't know the Node community well enough to be sure that having some quite serious behaviour changes hinging on the value of NODE_ENV is acceptable.

NODE_ENV !== 'production' is probably the only situation where it's deemed acceptable to change the behaviour (projects like express set a precedent by doing this).
However, given that canopi catches all of the log method usage errors anyway, I don't think this is necessary.


Option value mandatory required to add product to cart

Hi My Dears Sir/Mrs
I need your help to make "option value mandatory required to add product to cart " in my code , The reason for this , i didn't need any of customers skip option value of product without he is unknown , how can i insert this function or if statemeant in my code or where ?!! i hope to help me  this 2 files for my code i worked on it
product.zip
many thanks for you

"Hi @midotaha
This platform is not meant for assistance on personal code. Please see https://flutter.dev/community for resources and asking questions like this,
you may also get some help if you post it on Stack Overflow and if you need help with your code, please see https://www.reddit.com/r/flutterhelp/
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it.
Thank you"


Updated kubectl hlf plugin commands help

I updated most of the hlf plugin help tooltips, they should now indicate a bit better what do they mean

Hey @Wojciechowski-Marcin
Thanks for the PR :)
Try to sign the commit, if not we will not be able to merge the PR:
git rebase --signoff HEAD~1
git push --force


Add a link to GitHub pages to README.md

Add a link to GitHub pages to README.md

See https://github.com/RedHatInsights/insights-operator-cli/pull/206

#206 is already merged and the GH Pages already linked from README.md


Migration error: reportdata: SQLSTATE[HY000]: General error: 1 duplicate column name: uptime

Hi,
I've upgraded to MunkiReport 2.15.2, and I'm now seeing this error:

I'm using sqlite 3.7.17 and my config.php is set to allow migrations.
Looking at similar closed issues, it seems that ways of resolving this may be:

Removing sqlite.db and allowing client check ins to rebuild it

Running a command like:

sqlite3 /path/to/db.sqlite

sqlite> UPDATE migration SET version = 3 WHERE table_name = 'uptime';

Is my understanding correct? If so, is either resolution preferable? If not, do you know what might be going on here?

Something went wrong with the migration. The reportdata table was migrated to version 3 but that did not get recorded in the migrate table. Running UPDATE migration SET version = 3 WHERE table_name = 'reportdata'; should fix that.

Yep, that solved it. Thanks for your quick response.


New VLDB'24 paper(s) about machine unlearning

Communication Efficient and Provable Federated Unlearning
https://dl.acm.org/doi/10.14778/3641204.3641220

updated in repos and our survey paper.


Catch errors thrown while sending notifications.

Summary

Catch all exceptions thrown from NotificationHandlers.

This fixes a regression in #288 refactor when a NotificationHandler throws an error.

Pull Request Test Coverage Report for Build 1023

10 of 10 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 89.068%

Totals

Change from base Build 1020:
0.01%

Covered Lines:
3088

Relevant Lines:
3467

💛  - Coveralls

Pull Request Test Coverage Report for Build 1023

10 of 10 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 89.068%

Totals

Change from base Build 1020:
0.01%

Covered Lines:
3088

Relevant Lines:
3467

💛  - Coveralls

Confirmed that unit tests and compatibility suite tests are passing.


add releases with m1 macos support

Integrate the new gh action runner to build the package within m1 macos support
https://github.blog/changelog/2024-01-30-github-actions-introducing-the-new-m1-macos-runner-available-to-open-source/
Related to https://github.com/kornia/kornia/pull/2775 -- without this, we won't have support for kornia.io under m1 (mps) devices

@edgarriba it's solved here https://github.com/kornia/kornia-rs/blob/06f929b593dc97f6d9ab2e8bd103b11d12a0d1fa/.github/workflows/python_release.yml#L62, right?

I believe it’s that, let’s mark as solved. Reopen if any m1 reports the contrary


Feature: Automatically delete events older than X days

As a system admin, I want to be able to set a max age for events to be retained and any event in the system older than that age will be automatically flushed from the db so that my db doesn't grow in size forever or until I manually flush events in all accounts.

Going to have to push this to next feature release instead of patch release

Going to have to push this to next feature release instead of patch release


How to build 2.0?

Description
Building master branch seems impossible.
Steps to Reproduce
git clone https://github.com/Polymer/polymer.git
cd polymer
npm install
bower install
npm run build

Expected Results
No errors
Actual Results
><EMAIL_ADDRESS>build /media/Data/polymer
> gulp

[13:58:14] Using gulpfile /media/Data/polymer/gulpfile.js
[13:58:14] Starting 'build-bundled'...
[13:58:14] Starting 'build-steps'...
[13:58:14] 'build-steps' errored after 129 μs
[13:58:14] Error: Task print-size is not configured as a task on gulp.  If this is a submodule, you may need to use require('run-sequence').use(gulp).
    at /media/Data/polymer/node_modules/run-sequence/index.js:20:10
    at Array.forEach (native)
    at verifyTaskSets (/media/Data/polymer/node_modules/run-sequence/index.js:13:11)
    at runSequence (/media/Data/polymer/node_modules/run-sequence/index.js:92:2)
    at Gulp.<anonymous> (/media/Data/polymer/gulpfile.js:262:3)
    at module.exports (/media/Data/polymer/node_modules/orchestrator/lib/runTask.js:34:7)
    at Gulp.Orchestrator._runTask (/media/Data/polymer/node_modules/orchestrator/index.js:273:3)
    at Gulp.Orchestrator._runStep (/media/Data/polymer/node_modules/orchestrator/index.js:214:10)
    at Gulp.Orchestrator.start (/media/Data/polymer/node_modules/orchestrator/index.js:134:8)
    at runNextSet (/media/Data/polymer/node_modules/run-sequence/index.js:86:16)
[13:58:14] 'build-bundled' errored after 2.13 ms
[13:58:14] Error in plugin 'run-sequence(build-steps)'
Message:
    Task print-size is not configured as a task on gulp.  If this is a submodule, you may need to use require('run-sequence').use(gulp).
Stack:
Error: Task print-size is not configured as a task on gulp.  If this is a submodule, you may need to use require('run-sequence').use(gulp).
    at /media/Data/polymer/node_modules/run-sequence/index.js:20:10
    at Array.forEach (native)
    at verifyTaskSets (/media/Data/polymer/node_modules/run-sequence/index.js:13:11)
    at runSequence (/media/Data/polymer/node_modules/run-sequence/index.js:92:2)
    at Gulp.<anonymous> (/media/Data/polymer/gulpfile.js:262:3)
    at module.exports (/media/Data/polymer/node_modules/orchestrator/lib/runTask.js:34:7)
    at Gulp.Orchestrator._runTask (/media/Data/polymer/node_modules/orchestrator/index.js:273:3)
    at Gulp.Orchestrator._runStep (/media/Data/polymer/node_modules/orchestrator/index.js:214:10)
    at Gulp.Orchestrator.start (/media/Data/polymer/node_modules/orchestrator/index.js:134:8)
    at runNextSet (/media/Data/polymer/node_modules/run-sequence/index.js:86:16)

npm ERR! Linux 4.10.0-20-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "run" "build"
npm ERR! node v7.9.0
npm ERR! npm  v4.2.0
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>build: `gulp`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script 'gulp'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the @polymer/polymer package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     gulp
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs @polymer/polymer
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls @polymer/polymer
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/nazar-pc/.npm/_logs/2017-04-25T10_58_14_261Z-debug.log

Versions
nodejs --version
v7.9.0
npm --version
4.2.0
bower --version
1.8.0
gulp --version
[14:15:43] CLI version 3.9.1
[14:15:43] Local version 3.9.1

Thanks for the issue.  Agreed we need to get the gulpfile cleaned up.  The gulp tasks there were mainly for spot-checking the size of a minified polymer as well as testing closure compiler build/linting, but got into a state of disrepair since we don't actually use them on a regular basis.

Probably more than you were asking for, but here's background on our release/distribution plans:
The plan for the initial Polymer 2.0 release is actually to distribute the core library as raw ES6 source (unbundled/untranspiled/unminified, hence the gulpfile isn't really in the release workflow), and allow users to perform those tasks at the deployment step as their conditions dictate, e.g. using Polymer CLI.
There are a few different reasons for this approach:

We want the constituent bits of Polymer 2.0 (which is built out of composable mixins) to be consumable alacarte without the payload cost of the entire bundled library (e.g., using only lib/mixins/property-accessors.html or template-stamp.html alacarte gives you a lot of power for just a few kb)
Native custom elements require native ES6 classes, so there are performance benefits to keeping the source as untranspiled ES6 and serve ES5-transpiled source only to browsers that need it (requires a more complex server setup, but we want to allow for that, although we also have the native shim to allow ES5 source be served from a dumb server and still run on native CE with a modest performance hit)
It's more consistent with how elements are delivered

We're also very interested in plugging into the "module ecosystem" as well, so we may very well end up shipping Polymer in a more traditional format (and adapt the gulpfile for build output suitable to that), but haven't quite landed on the final direction for that yet.  In the meantime though, as you pointed out, we need to fix the gulpfile to not explode.

Thanks a lot for those details, makes sense!
Just as a side note, will all of following: Chromium, Firefox, Edge and Safari, support all necessary ES2015 features in 2 latest releases as of today (I'd like to eliminate transpiling process entirely)?

@nazar-pc Correct, no transpilation needed for latest release of all 4 major browsers.  If you choose to use the CLI polymer serve UA sniffs and will transpile on the fly for testing in IE (and older versions of the other browsers) to make it even easier.
polymer build has support for doing a universal ES5 build as well as separate ES5 and ES6 builds for deployment.
One note that Edge 14 does have some bugs in their ES6 impl (a particularly bad one where constructing an ES6 class too many times blows up) and so we recommend transpiling Edge and do so by default in the CLI tools (although I believe Edge 15 has resolved this).

Closing, as gulpfile was cleaned up in https://github.com/Polymer/polymer/pull/4565.
The following gulp tasks are implemented (and default task removed):

clean - removes dist dir
estimate-size - estimates the size of minified polymer.html bundle
lint - runs eslint
lint-closure - runs closure compiler and outputs logfile with closure warnings (closure typing of the entire library is WIP)
closure - runs closure compiler "advanced compilation" mode and outputs build of polymer.html (not particularly useful for end-users due to dead-code elimination, but useful for testing compilability)


create landing page

Create a landing page on how to use and buy the API

Use tailwind for the landing page


Add xc7k160t-marble with bscan_spi_xc7k160t_marble.bit

Tested on BerkeleyLab Marble board

Because the existing xc7k160t uses package fbg484-1, not the Marble board's ffg676-2.

https://github.com/quartiq/bscan_spi_bitstreams/blob/f29f48a1f3fbbd304a4aa23eacfd6ca215b72ae8/xilinx_bscan_spi.py#L359-L360

Can this be closed?

Yes please. Thanks for your help.
On Tue, Mar 7, 2023 at 01:11 Robert Jördens @.***>
wrote:

Can this be closed?
—
Reply to this email directly, view it on GitHub
https://github.com/quartiq/bscan_spi_bitstreams/pull/13#issuecomment-1457812590,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJRTWWGAFMRVFXJIJD765TW233URANCNFSM6AAAAAAUQZYCA4
.
You are receiving this because you authored the thread.Message ID:
@.***>


Create 21-Merge-Two-Sorted-Lists.cs

File(s) Modified: 21-Merge-Two-Sorted-Lists.cs
Language(s) Used: c#
Submission URL: https://leetcode.com/submissions/detail/754300351/

Thanks, @notauserx!


Update URL on https://www.cncf.io/sandbox-projects/

Not sure if this is an issue that should live here per se, but I didn't want to lose it.

fixed with https://github.com/cncf/cncf.io/issues/349


Alert Popup and Noise

Hi,
karma is an amazing project and really fills the gaps on the standard UI.
I have a feature request, I was hoping it might be possible to enhance the experience by adding popups and audible notifications for when new alerts arrive? Maybe making use of the js notifcations api?
Thank you.

Yeah, it seems that audio notification based on severity (label values of a given label) would be a desirable feature.
Audio notification could be different based on the label values. This is to use in the contact of control rooms where audio cues are a requirement.

Native browser notifications would be far more useful than audio alerts to me.


[FEATURE] Implement infrastructure to generate permutation

Implement the infrastructure to generate permutation following a specific algorithm.
Proposed API
from symmetria import generate
...
for permutation in generate(algorithm="lexicographic", degree=4):
    print(permutation)

The first step is:

[x] #88

It follows a list of algorithm of permutations we want to implement:

[ ] #90
[ ] Steinhaus–Johnson–Trotter algorithm;
[ ] Heap's algorithm;
[ ] Ehrlich's star-transposition algorithm;
[ ] Zaks' prefix reversal algorithm;
[ ] Sawada-Williams' algorithm;
[ ] Corbett's algorithm;
[ ] Single-track ordering;
[ ] Single-track Gray code;
[ ] Nested swaps generating algorithm;

Reference: https://en.wikipedia.org/wiki/Permutation#Numbering_permutations

Think about the possible API
'''python
import symmetria
permutations = symmetria.generate(...)
'''
We could use the same for random
import symmetria

random = symmetria.random(...)


Question about advancing the paxos instance

When advancing the paxos instance:
https://github.com/cocagne/multi-paxos-example/blob/924ae6c8690225d83718a26c6932c7c3c3ba493a/replicated_value.py#L190
Seems like like you're setting the value for the next instance instead of the current one.
I understand that the instance number needs to be advanced, but I'd have expected to happen only after saving the current consented value for the current instance. But looking into the self.advance_instance implementation that doesn't seem to be what's happening.
ps: Thanks for putting this repo together, it's been a great help!

It's easy to get confused with these things. Your description of what's
happening isn't wrong but I think your perspective is a little off. Think
of it this way, at any given point in time there is only one consensual
value and we use Paxos to change that value. Each time consensus on a new
value is reached, we save it to disk to ensure we don't loose it and
advance to the next instance of paxos for choosing the next consensual
value. So we don't save a value for the "next" instance, only the
most-recently-completed one. The "next" instance could remain outstanding
for days and the process for choosing a new value doesn't begin until some
outside entity (like the cli) sends a value to consider.
Does that help?
Tom
On Sat, Nov 11, 2017 at 12:11 PM, Juan Ignacio Vimberg <
<EMAIL_ADDRESS>wrote:

When advancing the paxos instance:
https://github.com/cocagne/multi-paxos-example/blob/
924ae6c8690225d83718a26c6932c7c3c3ba493a/replicated_value.py#L190
Seems like like you're setting the value for the next instance instead of
the current one.
I understand that the instance number needs to be advanced, but I'd have
expected to happen only after saving the current consented value for the
current instance. But looking into the self.advance_instance
implementation that doesn't seem to be what's happening.
ps: Thanks for putting this repo together, it's been a great help!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/cocagne/multi-paxos-example/issues/5, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ABrLfAhwpFd8UzCR39vED2JrZOyVN7xyks5s1eNqgaJpZM4QalMK
.

Ohh! I see... that makes sense!
I guess what confused me is the check that's done when receiving messages
https://github.com/cocagne/multi-paxos-example/blob/924ae6c8690225d83718a26c6932c7c3c3ba493a/replicated_value.py#L130-L133
I took that to mean: "only process messages for the instance number we're currently trying to agree upon". And I guess it serves that purpose only that when they reach a resolution it's going to be stored in instance_number + 1. Right?

Mostly. It means "ignore all messages that aren't messages for the current
Paxos instance". Both past and future messages must be taken into
consideration. It could well be that the network delayed delivery of a
message by a few seconds during which time we could have transitioned to
the new Paxos instance. So the instance number for that packet would be
less than the current value. It's also possible that we lost connection to
the peers for a while and they agreed upon the resolution of the paxos
instance a while ago and are now on the next one.... or 100+ instances
further down the chain. In that case, we'll need to catch up to the current
instance before we can participate again in the resolution process. That
catch-up process though is outside the scope of that class. All that class
needs to do is ensure it constrains all of its message handling to that
single Paxos instance.
On Sun, Nov 12, 2017 at 8:01 PM, Juan Ignacio Vimberg <
<EMAIL_ADDRESS>wrote:

Ohh! I see... that makes sense!
I guess what confused me is the check that's done when receiving messages
https://github.com/cocagne/multi-paxos-example/blob/
924ae6c8690225d83718a26c6932c7c3c3ba493a/replicated_value.py#L130-L133
I took that to mean: "only process messages for the instance number
we're currently trying to agree upon". And I guess it serves that
purpose only that when they reach a resolution it's going to be stored in
instance_number + 1. Right?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/cocagne/multi-paxos-example/issues/5#issuecomment-343790069,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABrLfDj7rZdCYnZAVlinlRLvswulFhBuks5s16L_gaJpZM4QalMK
.

Super clear. Thanks for the help!


Problem in admin content type

Hello, I followed the settings correctly, and everything went right.
I created the plugins.js added the settings, and sent the settings via environment variables.
External API working perfectly.
But when I went to access the Content Type, I'm getting this error message:

And it doesn't load the Content Types, and the contents I have are gone:

I'm using strapi 4.1.12
And my settings:

If I disable the settings everything goes back to normal.
And I'm uploading the strapi with:
yarn strapi develop --watch-admin
I would love to use this extension, but with this problem I can't use it, did I miss some configuration?
Thanks for the help.

Thanks for the report, I will have to look into this. It's possible that version changed something that broke the plugin.

I noticed that this only happens when the api prefix is /
I believe that the Admin should consume the api by this prefix, and as the structure of the api has changed, it breaks the contents.
I could be wrong, but using any prefix works normally.
I will follow this problem, thanks a lot for the help.

This should be fixed in v2.0.2


Python: Upgrade to Pydantic 2+

Motivation and Context

Upgraded pydantic to 2.0+, much cleaner, less complexity in different types of base models.
Description

Contribution Checklist

[ ] The code builds clean without any errors or warnings
[ ] The PR follows the SK Contribution Guidelines and the pre-submission formatting script raises no violations
[ ] All unit tests pass, and I have added new tests where possible
[ ] I didn't break anyone :smile:

Looks good to me!


Fix argtypes in Workshop_SuspendDownloads

bool -> c_bool
It causes 'TypeError: item 1 in argtypes has no from_param method'

Looks good!  Thanks for the fix.  Reminds me those Workshop functions need renamed.


Unexpected end of JSON input

It seems like 1 out of every 10 books is returning an "Unexpected end of JSON input" error.

This is the output in the console:
search.js:38 SyntaxError: Unexpected end of JSON input
(anonymous) @ search.js:38
Promise.catch (async)
addBook @ search.js:38
onclick @ search.html:1

And this is from Booktracker's logs:

12/16/2023 2:09:56 PM
Connection id "0HMVUDMTV7BIK", Request id "0HMVUDMTV7BIK:00000001": An unhandled exception was thrown by the application.
12/16/2023 2:09:56 PM
System.InvalidOperationException: Value must be set.
12/16/2023 2:09:56 PM
at Microsoft.Data.Sqlite.SqliteParameter.Bind(sqlite3_stmt stmt)
12/16/2023 2:09:56 PM
at Microsoft.Data.Sqlite.SqliteParameterCollection.Bind(sqlite3_stmt stmt)
12/16/2023 2:09:56 PM
at Microsoft.Data.Sqlite.SqliteCommand.GetStatements(Stopwatch timer)+MoveNext()
12/16/2023 2:09:56 PM
at Microsoft.Data.Sqlite.SqliteDataReader.NextResult()
12/16/2023 2:09:56 PM
at Microsoft.Data.Sqlite.SqliteCommand.ExecuteReader(CommandBehavior behavior)
12/16/2023 2:09:56 PM
at Microsoft.Data.Sqlite.SqliteCommand.ExecuteNonQuery()
12/16/2023 2:09:56 PM
at bookTrackerApi.DB.addNewEntry(VolumeInfo content) in /app/DB.cs:line 111
12/16/2023 2:09:56 PM
at bookTrackerApi.Api.<>c.<b__1_6>d.MoveNext() in /app/Api.cs:line 128
12/16/2023 2:09:56 PM
--- End of stack trace from previous location ---
12/16/2023 2:09:56 PM
at Microsoft.AspNetCore.Http.RequestDelegateFactory.ExecuteTaskResult[T](Task1 task, HttpContext httpContext) 12/16/2023 2:09:56 PM          at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint, Task requestTask, ILogger logger) 12/16/2023 2:09:56 PM          at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext) 12/16/2023 2:09:56 PM          at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext, ISwaggerProvider swaggerProvider) 12/16/2023 2:09:56 PM          at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.ProcessRequests[TContext](IHttpApplication1 application)

I've been able to consistently replicate the error with this book:
Harry Potter Magical Places & Characters Coloring Book
https://www.google.com/books/edition/_/caqDjgEACAAJ?hl=en

Thanks for calling this out. I'll try to get it fixed in the next release.


Argument 1 passed to MongoDB\Driver\BulkWrite::__construct() must be of the type array

Hey guys,
I'm using mongo-phplibrary with mongodb driver, and trying to insertOne document to tests.
But I'm receiving that error:
PHP Catchable fatal error:  Argument 1 passed to MongoDB\Driver\BulkWrite::__construct() must be of the type array, boolean given, in C:\...\vendor\mongodb\mongodb\src\Collection.php on line 1024
I change that code:
public function insertOne($document)
{
        $options = array_merge($this->getWriteOptions());

        $bulk = new BulkWrite($options["ordered"]);

To this, and worked:
public function insertOne($document)
{
        $options = array_merge($this->getWriteOptions());

        $bulk = new BulkWrite($options);

So, is that a bug?
Edit: I'm using version 1.0.0 of mongodb driver

This was a very late change in the mongodb driver.
It is a bug in mongo-php-library yes, and your fix is correct :)

@gabrielalan: I believe you're using a very old version of this library. The latest 1.0.0-beta1 release should be compatible with the 1.0.0 driver API. In that version, Collection.php is also less than 600 lines.

@jmikola the problem persist in 1.0.0-beta1 for what I'm seeing... I think I'm going to create a PR for this.

Closing this out as I've not heard back from the OP. Feel free to re-open if the issue persists.


Bazel Debug build for C/C++ failing

In PR #15173, the Bazel Debug build for C/C++ check fails. The PR just adds a missing include statement, so I'm not sure why it's failing.

The actual link to the test result: https://source.cloud.google.com/results/invocations/b4b5060c-b1d2-4fa7-b55f-7518b6dffa22/targets/%2F%2Ftest%2Fcpp%2Fend2end:end2end_test@poller%3Dpoll-cv/tests.
I've never seen this failure before.

It happened again to grpclb_end2end_test with opt build: https://source.cloud.google.com/results/invocations/2709f51a-2eac-4563-94a7-a7cfebebd11c/targets/%2F%2Ftest%2Fcpp%2Fend2end:grpclb_end2end_test@poller%3Dpoll-cv/tests

Assigning to David for triaging.

Is there a good repro for this one?

Not that I know of. :(

Is this still relevant? I don't see it on dashboards

Probably not relevant. We can reopen if we see this again


Unable to add cluster members while creating a downstream RKE1 clusters

Rancher Server Setup

Rancher version:  v2.6-head 9bcffaa
Installation option (Docker install/Helm Chart): Docker install

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): k3s

Proxy/Cert Details: Self signed

Information about the Cluster

Kubernetes version: v1.23.6
Cluster Type (Local/Downstream): Downstream Infrastructure provider

User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom)

If custom, define the set of permissions: Admin

Describe the bug
When we add cluster members to a downstream clusters under Member Roles ,API post request <rancherurl>v3/clusterroletemplatebinding is not sent while we create the cluster and therefore the added users cannot be listed under cluster members.
To Reproduce

On rancher server create a local user from USers and Auth >> users or enable any Auth provider
Create an RKE1 node driver cluster from cluster management and under Member Roles add the user created above with any role. I tried with both cluster member and cluster owner roles

Result
Once the cluster is created verify the users are no longer listed under cluster members
Expected Result
Expected the users to be listed under cluster members.
Screenshot

Additional context

Same is seen on v2.6.5 as well
This does not seem to happen for an RKE2 node driver clusters. Happens only for RKE1 node driver clusters.
Post request <rancherurl>v3/clusterroletemplatebinding is expected to be made when we create cluster while a user is added in the member roles.
Works on v2.5.13 for RKE1 clusters.
Works on v2.6.3, v2.6.4

I ran a quick test with this on 2.6.7-rc1. I can confirm the original issue. I was able to bypass this by using terraform which did not appear to the have the same issue. That combined with @anupama2501 's comment that no request was made to /v3/clusterroletemplatebinding during creation leads me to believe that this is a UI issue. FWIW, in 2.6.3 a request is made to /v3/clusterroletemplatebinding on cluster creation.
I think that the UI team should take a look into why the UI is no longer making this request. @samjustus can you transfer this over to them?

@gaktive we believe this is a UI issue- see Mike's comment above for more context


Add clickable url links to the description

Hi!
Can you make url in description clickable?

Up?

Sorry for that,
Currently, we don't have any plan to support the clickable on URL Description, but it's good point for sure. We will take into account soon 👍


Fix clang linker driver issue in the bootstrap script

llbuild's utils/adjust-times executable can't be linked on Ubuntu Jammy with a plain clang invocation, which doesn't link C++ standard library. Replacing that clang invocation with clang++ fixes the issue.

@swift-ci test


selenium error

Here is the error what I get when I am trying to run InstaRaider:
@ubuntu:~/temp/InstaRaider$ ./instaRaider.py kryptonitelock ./kryptonitelock
Traceback (most recent call last):
  File "./instaRaider.py", line 257, in <module>
    main()
  File "./instaRaider.py", line 248, in main
    log_level=args.log_level)
  File "./instaRaider.py", line 55, in __init__
    self.setup_webdriver()
  File "./instaRaider.py", line 76, in setup_webdriver
    self.webdriver = webdriver.Firefox(self.profile)
  File "/usr/local/lib/python2.7/dist-packages/selenium/webdriver/firefox/webdriver.py", line 70, in __init__
    self.binary = FirefoxBinary()
  File "/usr/local/lib/python2.7/dist-packages/selenium/webdriver/firefox/firefox_binary.py", line 47, in __init__
    self._start_cmd = self._get_firefox_start_cmd()
  File "/usr/local/lib/python2.7/dist-packages/selenium/webdriver/firefox/firefox_binary.py", line 159, in _get_firefox_start_cmd
    " Please specify the firefox binary location or install firefox")
RuntimeError: Could not find firefox in your system PATH. Please specify the firefox binary location or install firefox

selenium is the latest one selenium-2.48.0

If you haven't solved this already, I suggest checking the version of your Firefox to make sure it's compatible with that version of selenium. Here's the CHANGELOG: https://github.com/SeleniumHQ/selenium/blob/master/dotnet/CHANGELOG


Mistakenly marked uint32 -> double conversion as NYI

I thought uint32 -> double was not implemented, I was wrong.
This reverts the change made by #1142 for this operator

This change is

@MikeHolman @commonlisp Could you review this please?

lgtm


[vcpkg] use x64 (64-bit) compiler/linker/utilities and tools when building x64 triplets on windows

Feature Improvement to vcpkg
[vcpkg] use x64 (64-bit) compiler/linker/utilities and tools when building x64 triplets on windows
Is your feature request related to a problem? Please describe.
x86 (32-bit) compiler/linker/utilities and tools often fail building 64-bit windows triplets with exhausted heap memory, memory segmentation faults, other untraceable issues, etc.
I know I have spent literally days tracing down some issue related to a 32-bit binary, tools, utility somehow causing an issue with the build of a 64-bit binary (not just windows either, but on Linux/Unix also).
Examples I could find:

Issue #13627 [ace[core]:x64-windows] LINK fatal error LINK : the 32-bit linker (C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.27.29110\bin\HostX86\x64\link.exe) ran out of heap space
Issue #13388 building faileds on shogun repositions. C:\vcpkg\installed\x64-windows-static\include\eigen3\Eigen\src/Core/MatrixBase.h(276): fatal error C1060: compiler is out of heap space
Issue #1594 failure building boost (c1060) C:\externals\vcpkg-master\buildtrees\boost\src\boost_1_64_0\boost/proto/generate.hpp(456): fatal error C1060: compiler is out of heap space
Issue #12240 [nettle:x64-windows] build failure https://github.com/microsoft/vcpkg/issues/12240#issuecomment-653815465 seems 32-bit yasm is causing issues on 64-bit ports, using 64-bit yasm seems to fix in many cases ([gmp:x64-windows] build failure #12237, [gmp,nettle,hogweed] Add new ports #10613).

Proposed solution
A clear and concise description of what you want to happen.
use x64 (64-bit) compiler/linker/utilities and tools when building x64 triplets on windows (Linux/Unix/OSX) where available.
Although Linux seems to be a challenge as there is the /lib, /lib32, /libx32, /lib64, /libx64, etc depending on the flavor of Linux you are working with, as I am always having to modify the portfile.cmake to handle the /lib64 used in OpenSUSE for 64-bit binaries instead of /lib used on other "user friendly" Linux versions.
Describe alternatives you've considered
In my environment, vcpkg is build with the -win64 option, vcpkg_acquire_program.cmake and vcpkgTools.xml have been modified to acquire and install x64 bit versions where available, the environment variables PreferredToolArchitecture=x64 and _IsNativeEnvironment=true are set (commented out the set PreferredToolArchitecture= in both vcvars.bat and vcvars140.bat and modified visualstudio.cpp to use /HostX64 instead of /Hostx86, as I do not even build x86 ports/projects/binaries at all.
Result is I have not had any of the issues with heap, segmentation or other unexplained problems with the 64 ports.
Additional context
Even though Microsoft is still update x86 versions of windows, the x86 platforms are dying out and we need to engage in the mindset to build x64 platforms and software, having the x86 (32-bit) go the way of the 4, 8 and 16-bit programs of the past.

That must be a bug of vcpkg. We need to fix it soon.

From --debug
[DEBUG] CreateProcessW(cmd /c ""C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Auxiliary\Build\vcvarsall.bat" -vcvars_ver=14.2 amd64   2>&1 <NUL" & echo cdARN4xjKueKScMy9C6H& set)
from the script:
if /I "%1"=="amd64" (
    set __VCVARSALL_TARGET_ARCH=x64
    set __VCVARSALL_HOST_ARCH=x64
    set __local_ARG_FOUND=1
)

so the environment should be setup correctly. Maybe something is failing in vcpkg detection and is calling vcvarsall.bat with x86_x64 or x86_amd64

Closing, no longer an issue for me as we have chosen to no longer use vcpkg.

Reopen this issue since it's not resolved.

Currently, vcpkg uses the x64 (64-bit) compiler by default when building x64 triples on Windows (Linux/Unix/OSX).


Attempts to send the robot destinations to navigate to were unsuccessful. (associated with: ntp time, transform, odom and base_link)

OS: Ubuntu 22.04
ROS Distro: Humble
Built from source or installed: installed
fastrtps enabled

Expected behaviour
Being able to send the robot to goal poses on a map.
Actual behaviour
The robot wont't start moving.
To Reproduce
I was following the tutorial for navigation on the documentation. When launching the following launchfiles i get some infos/warnings. The mapping beforehand had worked. Only the saving of the map with a specified name not.

running: ros2 launch turtlebot4_navigation nav2.launch.py.
output:

...
[controller_server-1] [INFO] [1685961758.902200663] [local_costmap.local_costmap]: Timed out waiting for transform from base_link to odom to become available, tf error: Could not find a connection between 'odom' and 'base_link' because they are not part of the same tree.Tf has two or more unconnected trees.
...

I am seeing the /odom topic and i can echo it.

running: ros2 launch turtlebot4_viz view_robot.launch.py.
output:

...
[rviz2-1] [INFO] [1685961757.008412115] [rviz2]: Message Filter dropping message: frame 'rplidar_link' at time<PHONE_NUMBER>.735 for reason 'discarding message because the queue is full'
[rviz2-1] Warning: Invalid frame ID "left_wheel" passed to canTransform argument source_frame - frame does not exist
[rviz2-1]          at line 93 in ./src/buffer_core.cpp
[rviz2-1] Warning: Invalid frame ID "right_wheel" passed to canTransform argument source_frame - frame does not exist
[rviz2-1]          at line 93 in ./src/buffer_core.cpp
[rviz2-1] Warning: Invalid frame ID "left_wheel" passed to canTransform argument source_frame - frame does not exist
[rviz2-1]          at line 93 in ./src/buffer_core.cpp
[rviz2-1] Warning: Invalid frame ID "right_wheel" passed to canTransform argument source_frame - frame does not exist
[rviz2-1]          at line 93 in ./src/buffer_core.cpp
[rviz2-1] Warning: Invalid frame ID "left_wheel" passed to canTransform argument source_frame - frame does not exist
[rviz2-1]          at line 93 in ./src/buffer_core.cpp
[rviz2-1] Warning: Invalid frame ID "right_wheel" passed to canTransform argument source_frame - frame does not exist
[rviz2-1]          at line 93 in ./src/buffer_core.cpp
[rviz2-1] Warning: Invalid frame ID "left_wheel" passed to canTransform argument source_frame - frame does not exist
[rviz2-1]          at line 93 in ./src/buffer_core.cpp
[rviz2-1] Warning: Invalid frame ID "right_wheel" passed to canTransform argument source_frame - frame does not exist
[rviz2-1]          at line 93 in ./src/buffer_core.cpp
...

Running: ros2 launch turtlebot4_navigation localization.launch.py map:=scs-map.yaml.
output:

...
[amcl-2] [INFO] [1685961708.094046398] [amcl]: initialPoseReceived
[amcl-2] [INFO] [1685961708.094282927] [amcl]: Setting pose<PHONE_NUMBER>.094282): -0.258 -0.314 3.045
[amcl-2] [INFO] [1685961708.111703829] [amcl]: Message Filter dropping message: frame 'rplidar_link' at time<PHONE_NUMBER>.110 for reason 'the timestamp on the message is earlier than all the data in the transform cache'
[amcl-2] [INFO] [1685961708.234964788] [amcl]: Message Filter dropping message: frame 'rplidar_link' at time<PHONE_NUMBER>.232 for reason 'the timestamp on the message is earlier than all the data in the transform cache'
...

Other notes
I am sorry if there were already some of the issues mentioned. However, I did not quite understand how to solve them.

I am seeing the following topics when the robot is docked:
/battery_state
/cmd_audio
/cmd_lightring
/cmd_vel
/color/preview/image
/diagnostics
/diagnostics_agg
/diagnostics_toplevel_state
/dock_status
/function_calls
/hazard_detection
/hmi/buttons
/hmi/display
/hmi/display/message
/hmi/led
/imu
/interface_buttons
/ip
/joint_states
/joy
/joy/set_feedback
/mouse
/parameter_events
/robot_description
/rosout
/scan
/stereo/depth
/tf
/tf_static
/wheel_status

And the following when it is off the dock:
/battery_state
/cmd_audio
/cmd_lightring
/cmd_vel
/color/preview/image
/diagnostics
/diagnostics_agg
/diagnostics_toplevel_state
/dock_status
/function_calls
/hazard_detection
/hmi/buttons
/hmi/display
/hmi/display/message
/hmi/led
/imu
/interface_buttons
/ip
/ir_intensity
/ir_opcode
/joint_states
/joy
/joy/set_feedback
/kidnap_status
/mobility_monitor/transition_event
/mouse
/oakd/rgb/preview/camera_info
/oakd/rgb/preview/image_raw
/oakd/rgb/preview/image_raw/compressed
/oakd/rgb/preview/image_raw/compressedDepth
/oakd/rgb/preview/image_raw/theora
/odom
/parameter_events
/robot_description
/robot_state/transition_event
/rosout
/scan
/slip_status
/static_transform/transition_event
/stereo/depth
/stop_status
/tf
/tf_static
/wheel_status
/wheel_ticks
/wheel_vels

@tschinfra Are you running simple discovery or discovery server? Also can you check the Create 3 webserver to see if the Create 3 clock is sync'd with the RPi4?

This issue is being closed due to inactivity. If you are still experiencing the issue, feel free to reopen this ticket when you are ready to continue the troubleshooting process.

Hi, did you find a fix for this?


[SPARK-39800][SQL][WIP] DataSourceV2: View Support

What changes were proposed in this pull request?
This PR adds support to load, create, alter, and drop views in DataSource V2 catalogs.

View substitution rule
Create view DDL
View SQL DDLs

Why are the changes needed?
Support views stored in DataSourceV2 catalogs. Details in SPIP.
Does this PR introduce any user-facing change?

Support views from DataSource V2 catalogs in SQL
Support views from DataSource V2 catalogs in DataFrame API

How was this patch tested?
New unit tests

TODO

Regression

DDLParserSuite
PlanResolutionSuite
DataSourceV2SQLSuite

+CC @shardulm94, @wmoustafa

TODOs and comments:

More unit tests
Conform to “v2 command framework”. ResolveCatalogs seem to have too much extra view code, but that cleanup might require migrating more SQL commands to “v2 command framework”. Maybe a good opportunity to split PR.
Further cleanup/simplify/unify code, especially around ResolvedV2View.

Thanks @amogh-jahagirdar for driving this PR!

cc @holdenk (Shepherd) @cloud-fan @imback82 @huaxingao @xkrogen

shall we have the first PR only support creating and reading v2 views? Then we can add alter view commands (which can be done in parallel) later.

shall we have the first PR only support creating and reading v2 views? Then we can add alter view commands (which can be done in parallel) later.

Yes it is exactly what we planed. Amogh will split the PR.

Thanks @jzhuge, happy to help ! Yes I plan on splitting this PR, I will get more time later this week to look into this.

Current status:

Incorporate all @MaxGekk comments (took care of some)
Add unit tests

Follow up:

Support user specified column names
Support viewSQLConfigs
Conform to “v2 command framework” (SPARK-36586). - ResolveCatalogs seem to have too much extra view code, but that cleanup might require migrating more SQL commands to “v2 command framework”.

It won't let me re-open, can you re-create the PR?


Enabling CodeQL scanning

Enabling CodeQL security scanning

CodeQL doesn't do shell scripts.  Closing without merging.


Add an action for an AI Pull Request helper

Type
enhancement

Description

Introduced a new GitHub Actions workflow to automate pull request handling and response to user comments.
The workflow is triggered by pull request events such as opened, reopened, and ready for review, as well as issue comments.
It includes conditions to exclude bots and uses specific permissions to interact with issues and pull requests.
The action step utilizes an external action (Codium-ai/pr-agent@main) and passes necessary secrets for operation.

Changes walkthrough
Relevant filesEnhancement

pr_agent.yamlAdd GitHub Actions Workflow for PR Agent

.github/workflows/pr_agent.yaml
Added a new GitHub Actions workflow triggered by pull request events and issue comments.  Configured the workflow to run on ubuntu-latest with specific permissions for issues, pull-requests, and contents.  Included a step to use Codium-ai/pr-agent@main with environment variables for OPENAI_KEY and GITHUB_TOKEN.

+20/-0

✨ PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

Kinda noisy...

Looks like it doesn't re-run on changes. Which is fine. I'm going to remove the description it gave to (hopefully) check if the configuration changes are right.


Implement datetime selections as strings

Closes https://github.com/ioam/holoviews/issues/886

Great to see this coming along! Just tested your PR, ran into the following:
df = pd.DataFrame(dict(time=pd.date_range('2018-1-1', freq='1D', periods=10),
             x=np.arange(10), y=np.linspace(10,1,10)))

x = hv.Curve(df, vdims='x')
y = hv.Curve(df, vdims='y')

l = x*y

x['2018-1-1':'2018-1-3'] # works
y['2018-1-1':'2018-1-3'] # works
# x['2018-1-1':'2018-1-3'] + y['2018-1-1':'2018-1-3'] # fails
# l['2018-1-1':'2018-1-3'] # fails

@philippjfr I've been chasing a few bugs in your PR. Would you mind if I pushed directly to this branch?

Please do.
On Sat, 27 Apr 2019, 23:29 Achim Randelhoff<EMAIL_ADDRESS>wrote:

@philippjfr https://github.com/philippjfr I've been chasing a few bugs
in your PR. Would you mind if I pushed directly to this branch?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pyviz/holoviews/pull/3197#issuecomment-487321292, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAL2TM7XSI6ULHG4J65KZCLPSTATDANCNFSM4GGIU5PQ
.

Sorry for all the force pushing, I rolled back on a commit to rebase and use some recent datetime util of yours (only to hesitate once more). Could you take a look at 6dedb77? That piece clashes when values have been parsed in the meantime, such as datetimes, and that was the one that prevented layouts from being rendered. I don't think it's necessary either as the various get_extents methods and utils do the same thing, but please correct me.

That piece clashes when values have been parsed in the meantime, such as datetimes, and that was the one that prevented layouts from being rendered. I don't think it's necessary either as the various get_extents methods and utils do the same thing, but please correct me.

That stuff is the focus of multiple (very old) issues (see https://github.com/pyviz/holoviews/issues/181 and https://github.com/pyviz/holoviews/issues/566). The long and short of it is that I really would like to get rid of it, but the main problem is that to get rid of it consistently everywhere we would have to implement proper routines for slicing paths and polygons. I haven't thought about that for a long time and would say that maybe it's okay to simply drop it from Chart because slicing is implemented in a more appropriate way there.

Ok, then I'd say this is ready for review. I've tested slicing a few more elements and overlays with various annotations and didn't come across anything obvious apart from the DictInterface issues mentioned in #3697.


Implementing Control Curves.

Adds control curves. These are intended to map input control values such as velocity, note number, assignable controllers etc to some other value range that we want to modify such as volume, filter cutoff, FM modulation, etc.


Extremely slow the first time

Once the data is loaded, it is working fine but the first time it is loaded (even though the w3wp process is still there) it takes like 5-10 minutes for the data to load (the page doesn't load except for the title). Idle for a few minutes and it'll take the same 5-10 minutes again until we see something to load. The server we run this on is more than fast enough to handle some exceptions. Is this something that is known/expected or ...?

 I fired up the profiler and noticed that it takes 30+ seconds here for Jurassic Js Engine to complete. When I switch to V8 or MSIE it loads within 5 seconds. Is there any reason why Jurassic is used?

You can switch to the other JS engines. The reason why we were using the Jurassic engine is because it doesn't require special permissions on the server.
In Exceptionless 2.0, we aren't using a JS engine at all so that issue should go away completely.

Thank you for the information, I'll use V8 for now then and wait until 2.0 is ready!


Google issue

When browsing on Google, i.e
https://www.google.com/intl/en-US/gmail/about/
There is an error:
about/:137 [Report Only] This document requires 'TrustedScriptURL' assignment.
And then on the Login page, there is in the console:
m=_b,_tp:117 Uncaught (in promise) TypeError: Illegal invocation
I've tried tweaking most things, userAgent latest... none at all... and all of them seems to not have Google work.
Of course it does work with a normal browser.

Try removing the background-networking flag from the engine. That might also be part of it

I tried removing absolutely EVERY flags, but still.

Yeah, sadly it makes Hero unusable anymore :( Impossible to use any sort of Google accounts, regardless of flags.


CSS in media queries is ignored.

Any CSS inside a media query is ignored.
That way you can not judge CSS for responsive websites.

It should be analysed and the position of the media query should be marked in the graph.

Hi @derheap - thanks for raising this issue, crazy that I never noticed that before. Will look into.

Thanx for the quick fix!


Support Ada

Codecov Report

Merging #18 (dee5946) into master (f17b391) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #18      +/-   ##
==========================================
+ Coverage   92.97%   92.99%   +0.01%
==========================================
  Files          34       34
  Lines        1609     1613       +4
==========================================
+ Hits         1496     1500       +4
  Misses        113      113

Impacted Files
Coverage Δ

src/baca/details/language.rs
98.48% <100.00%> (+0.09%)
:arrow_up:

Continue to review full report at Codecov.

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


Add per-file-ignores

Fixes https://github.com/PlasmaFAIR/fortitude/issues/6
Allows the user to specify --per-file-ignores and --extend-per-file-ignores to switch off rules/categories for specific files:
fortitude check --per-file-ignores=myfile.f90:typing,myotherfile.f90:S001

Using --extend-per-file-ignores on the command line adds to the list in the config file, while --per-file-ignores overwrites it.
As we're just using serde to handle the config file vs CLI problem, the .toml interface is a bit clunky:
[check]
per-file-ignores = [
  "myfile.f90:typing",
  "myotherfile.f90:S001",
]

Ideally we would have a separate interface like:
[check.per-file-ignores]
"myfile.f90" = ["typing"]
"myotherfile.f90" = ["S001"]

I'd suggest raising a new issue for this if this PR is merged.

I had to copy quite a lot of new Ruff machinery over to get this working, and while I've tried it out on some local files, I haven't written any tests yet. I'll leave this as a draft until those are done.

Sounds like we might need to have the split types for CLI and config file sooner rather than later.
My first thought on doing this was to filter the ruleset for each file beforehand (in the loop, but before we check), but this way looks pretty expedient and clean.

Hi folks,
this is a missing feature that's currently blocking us from using Fortitude in CI (ideally we'd like to just exclude all rules for certain files). Feel free to ping me once things start converging and I am happy to take this PR for a spin on our codebase.
Thanks for all the work!

@danielhollas I'm glad to hear that you're finding this useful, and I hope that by our next release we'll have enough configuration options for the most common use-cases. We're aiming to also add per-line rule ignores, the ability to exclude certain file patterns, and the ability to follow rules in the user's .gitignore files.

ideally we'd like to just exclude all rules for certain files

I've just tested this, and the following seems to work:
fortitude check --per-file-ignores=myfile.f90:ALL src/
The file pattern can be finicky however. It will match all files with a certain file name (including with wildcards), but I can't get it to match files within a certain directory, which is something that you can do with ruff:
fortitude check --per-file-ignores=./src/myfile.f90:ALL src/  # Doesn't work for some reason
@ZedThree Would you be in favour of merging this now and raising a new issue for the directory-selection bug, or should I get that fixed first?

I think that needs to be fixed, src/myfile.f90 should work, and myfile.f90 should not match src/myfile.f90 -- **/myfile.f90 should match both myfile.f90 and src/myfile.f90

I think I've gotten the directory selection to work, but it's strange in the tests -- it seems we need to specify /tmp/.tmpDSFGJ725/ (or whatever) in the path to get **/some_dir/*.f90 to work:
fortitude check --per-file-ignores=/tmp/.tmpSFGJ525/**/some_dir/*.f90 /tmp/.tmpSFGJ525

Outside of the tests however, the following seems to work just fine:
fortitude check --per-file-ignores=**/some_dir/*.f90 src

I think that needs to be fixed, src/myfile.f90 should work, and myfile.f90 should not match src/myfile.f90 -- **/myfile.f90 should match both myfile.f90 and src/myfile.f90

Ruff's behaviour is that myfile.f90 should match src/myfile.f90. I could try to get this implemented, but it might take me a little while to work out exactly how the matching works and modify it accordingly.

Ruff's behaviour is that myfile.f90 should match src/myfile.f90. I could try to get this implemented, but it might take me a little while to work out exactly how the matching works and modify it accordingly.

Ahh, this is .gitignore-like behaviour:

If there is a separator at the beginning or middle (or both) of the pattern, then the pattern is relative to the directory level of the particular .gitignore file itself. Otherwise the pattern may also match at any level below the .gitignore level.

If there is a separator at the end of the pattern then the pattern will only match directories, otherwise the pattern can match both files and directories.

For example, a pattern doc/frotz/ matches doc/frotz directory, but not a/doc/frotz directory; however frotz/ matches frotz and a/frotz that is a directory (all paths are relative from the .gitignore file).


Add option for detached HUP on startOsUpdate

This will call the v2 actions endpoint for resinhup which runs a detached version of HUP that increases HUP reliability on slow networks but will offer
no status updates such as in_progress.

Resolves: #
HQ:
See:
Depends-on:
Change-type: major|minor|patch

Contributor checklist

[ ] Includes tests
[ ] Includes typings
[ ] Includes updated documentation
[ ] Includes updated build output

One more thing to add OsUpdateActionResult needs a 'triggered' status option. For v2, the status is either 'idle', 'triggered', or possibly 'error'. It will error for example if there is a bad parameter in the request. In that case the HUP is not started on the device. See balena-proxy src/services/actions-backend/app.ts.

@jaomaloy I've gone through all the code now, and overall it is more compact and looks good. Please update the API comments in src/models/device.ts to describe that startOsUpdate() is deprecated for for runDetached=false. Also add a comment to getOsUpdateStatus() also is deprecated, and will not return a useful status for runDetached=true.

@jaomaloy I've gone through all the code now, and overall it is more compact and looks good. Please update the API comments in src/models/device.ts to describe that startOsUpdate() is deprecated for for runDetached=false. These marks will update the online API docs to show in strikethrough font.
Also add a comment to getOsUpdateStatus() also is deprecated, and will not return a useful status for runDetached=true.

We will do this at the next step, correct? This PR isn't for deprecation yet but to add the option for true so the rest of our code can use runDetached=true.

@jaomaloy we want to deprecate now to give users notice of the change and time to adapt.

Tests look OK, except for what I describe below.
When I test v1, I see these results when starting the update, as expected.
> await balena.models.device.startOsUpdate("43c932f91a2e305a13f6b692faf39230", "2.99.27")
{
  status: 'in_progress',
  lastRun:<PHONE_NUMBER>785,
  parameters: { target_version: '2.99.27' },
  action: 'resinhup'
}
> await balena.models.device.getOsUpdateStatus("43c932f91a2e305a13f6b692faf39230")
{
  status: 'in_progress',
  lastRun:<PHONE_NUMBER>785,
  parameters: { target_version: '2.99.27' },
  action: 'resinhup'
}

However, when running v2, I see these results when starting the update. I actually would expect to see similar results -- basically whatever is in the action server's ACTION_STATUS dictionary.
> await balena.models.device.startOsUpdate("43c932f91a2e305a13f6b692faf39230", "4.0.26+rev1", {runDetached: true})
{
  status: 'triggered',
  lastRun:<PHONE_NUMBER>298,
  parameters: { target_version: '4.0.26+rev1' },
  action: 'resinhup'
}
> await balena.models.device.getOsUpdateStatus("43c932f91a2e305a13f6b692faf39230")
{ status: 'error' }

Looking into the error, I see this in the log for balena-proxy -- generating an error just looking up the device. Of course we don't support getOsUpdateStatus() when running in detached mode. However, it should not generate an error either. Do you get the same results? My concern is that there may be some code or rules in pinejs that are sensitive to the status of the device.
Oct 22 04:28:24 d90c519 2c27e73cdc26[1631]: [40938.112701] actions-backend[7773]: ::ffff:<IP_ADDRESS> GET actions.devices.d90c5192ae585eaed21f1f48258c954c.kb2ma.balena-dev.com /v1/43c932f91a2e305a13f6b692faf39230/resinhup 400 12 10.968ms curl/7.81.0
Oct 22 04:28:24 d90c519 2c27e73cdc26[1631]: [40938.112886] proxy[7757]: ::ffff:<IP_ADDRESS> GET actions.devices.d90c5192ae585eaed21f1f48258c954c.kb2ma.balena-dev.com /v1/43c932f91a2e305a13f6b692faf39230/resinhup 400 12 15.058ms curl/7.81.0
Oct 22 04:28:24 d90c519 2c27e73cdc26[1631]: [40938.113011] actions-backend[7773]: error: Error: Actions Backend error: -  StatusError
Oct 22 04:28:24 d90c519 2c27e73cdc26[1631]: [40938.113076] actions-backend[7773]:     at PinejsClientRequest._request (/usr/src/app/node_modules/pinejs-client-request/request.ts:143:10)
Oct 22 04:28:24 d90c519 2c27e73cdc26[1631]: [40938.113122] actions-backend[7773]:     at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
Oct 22 04:28:24 d90c519 2c27e73cdc26[1631]: [40938.113166] actions-backend[7773]:     at async PinejsClientRequest.callWithRetry (/usr/src/app/node_modules/pinejs-client-core/src/index.ts:1173:11)
Oct 22 04:28:24 d90c519 2c27e73cdc26[1631]: [40938.113205] actions-backend[7773]:     at async PinejsClientRequest.get (/usr/src/app/node_modules/pinejs-client-core/src/index.ts:1308:18)
Oct 22 04:28:24 d90c519 2c27e73cdc26[1631]: [40938.113245] actions-backend[7773]:     at async getDeviceInfo (/usr/src/app/src/common/api-utils.ts:146:17)
Oct 22 04:28:24 d90c519 2c27e73cdc26[1631]: [40938.113283] actions-backend[7773]:     at async <anonymous> (/usr/src/app/src/services/actions-backend/app.ts:689:23)

There is another problem. If I run a HUP in non-detached mode, and then run a second HUP in detached mode, the second HUP actually runs in non-detached mode.
1st HUP:
> await balena.models.device.getOsUpdateStatus("447c7aeda6702cac332d48bc65d78797")
{ status: 'idle', action: 'resinhup', lastRun: null }
> await balena.models.device.startOsUpdate("447c7aeda6702cac332d48bc65d78797", "2.99.27", {runDetached: false})
{
  status: 'in_progress',
  lastRun:<PHONE_NUMBER>485,
  parameters: { target_version: '2.99.27' },
  action: 'resinhup'
}
> await balena.models.device.getOsUpdateStatus("447c7aeda6702cac332d48bc65d78797")
{
  status: 'in_progress',
  lastRun:<PHONE_NUMBER>485,
  parameters: { target_version: '2.99.27' },
  action: 'resinhup'
}
> await balena.models.device.getOsUpdateStatus("447c7aeda6702cac332d48bc65d78797")
{
  status: 'done',
  action: 'resinhup',
  stdout: '[upgrade-2.x.sh][000000000][INFO]Loading info from config.json\n',
  error: 'failed to get digest sha256:cfe5adead644da98672552df619e3758fe4e8773abe02f54b95bf01cd2fd71f4: open /mnt/sysroot/inactive/balena/image/overlay2/imagedb/content/sha256/cfe5adead644da98672552df619e3758fe4e8773abe02f54b95bf01cd2fd71f4: no such file or directory\n' +
    "WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested\n" +
    "WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested\n" +
    "WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested\n" +
    'Running as unit: run-update-supervisor.service\n' +
    'Finished with result: success\n' +
    'Main processes terminated with: code=exited/status=0\n' +
    'Service runtime: 9.969s\n',
  lastRun:<PHONE_NUMBER>902,
  parameters: { target_version: '2.99.27' }
}

2nd HUP. Notice status should be 'triggered'.
> await balena.models.device.startOsUpdate("447c7aeda6702cac332d48bc65d78797", "4.0.26", {runDetached: true})
{
  status: 'in_progress',
  lastRun:<PHONE_NUMBER>882,
  parameters: { target_version: '4.0.26' },
  action: 'resinhup'
}
> await balena.models.device.getOsUpdateStatus("447c7aeda6702cac332d48bc65d78797")
{
  status: 'in_progress',
  lastRun:<PHONE_NUMBER>882,
  parameters: { target_version: '4.0.26' },
  action: 'resinhup'
}

Proxy log shows the second attempt did indeed call the /v1 endpoint:
Oct 22 05:41:20 d90c519 2c27e73cdc26[1631]: [45314.541747] actions-backend[7773]: ::ffff:<IP_ADDRESS> POST actions.devices.d90c5192ae585eaed21f1f48258c954c.kb2ma.balena-dev.com /v1/447c7aeda6702cac332d48bc65d78797/resinhup 200 109 63.712ms node-fetch/1.0 (+https://github.com/bitinn/node-fetch)

Tests look OK, except for what I describe below.
When I test v1, I see these results when starting the update, as expected.
> await balena.models.device.startOsUpdate("43c932f91a2e305a13f6b692faf39230", "2.99.27")
{
  status: 'in_progress',
  lastRun:<PHONE_NUMBER>785,
  parameters: { target_version: '2.99.27' },
  action: 'resinhup'
}
> await balena.models.device.getOsUpdateStatus("43c932f91a2e305a13f6b692faf39230")
{
  status: 'in_progress',
  lastRun:<PHONE_NUMBER>785,
  parameters: { target_version: '2.99.27' },
  action: 'resinhup'
}

However, when running v2, I see these results when starting the update. I actually would expect to see similar results -- basically whatever is in the action server's ACTION_STATUS dictionary.
> await balena.models.device.startOsUpdate("43c932f91a2e305a13f6b692faf39230", "4.0.26+rev1", {runDetached: true})
{
  status: 'triggered',
  lastRun:<PHONE_NUMBER>298,
  parameters: { target_version: '4.0.26+rev1' },
  action: 'resinhup'
}
> await balena.models.device.getOsUpdateStatus("43c932f91a2e305a13f6b692faf39230")
{ status: 'error' }

Looking into the error, I see this in the log for balena-proxy -- generating an error just looking up the device. Of course we don't support getOsUpdateStatus() when running in detached mode. However, it should not generate an error either. Do you get the same results? My concern is that there may be some code or rules in pinejs that are sensitive to the status of the device.
Oct 22 04:28:24 d90c519 2c27e73cdc26[1631]: [40938.112701] actions-backend[7773]: ::ffff:<IP_ADDRESS> GET actions.devices.d90c5192ae585eaed21f1f48258c954c.kb2ma.balena-dev.com /v1/43c932f91a2e305a13f6b692faf39230/resinhup 400 12 10.968ms curl/7.81.0
Oct 22 04:28:24 d90c519 2c27e73cdc26[1631]: [40938.112886] proxy[7757]: ::ffff:<IP_ADDRESS> GET actions.devices.d90c5192ae585eaed21f1f48258c954c.kb2ma.balena-dev.com /v1/43c932f91a2e305a13f6b692faf39230/resinhup 400 12 15.058ms curl/7.81.0
Oct 22 04:28:24 d90c519 2c27e73cdc26[1631]: [40938.113011] actions-backend[7773]: error: Error: Actions Backend error: -  StatusError
Oct 22 04:28:24 d90c519 2c27e73cdc26[1631]: [40938.113076] actions-backend[7773]:     at PinejsClientRequest._request (/usr/src/app/node_modules/pinejs-client-request/request.ts:143:10)
Oct 22 04:28:24 d90c519 2c27e73cdc26[1631]: [40938.113122] actions-backend[7773]:     at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
Oct 22 04:28:24 d90c519 2c27e73cdc26[1631]: [40938.113166] actions-backend[7773]:     at async PinejsClientRequest.callWithRetry (/usr/src/app/node_modules/pinejs-client-core/src/index.ts:1173:11)
Oct 22 04:28:24 d90c519 2c27e73cdc26[1631]: [40938.113205] actions-backend[7773]:     at async PinejsClientRequest.get (/usr/src/app/node_modules/pinejs-client-core/src/index.ts:1308:18)
Oct 22 04:28:24 d90c519 2c27e73cdc26[1631]: [40938.113245] actions-backend[7773]:     at async getDeviceInfo (/usr/src/app/src/common/api-utils.ts:146:17)
Oct 22 04:28:24 d90c519 2c27e73cdc26[1631]: [40938.113283] actions-backend[7773]:     at async <anonymous> (/usr/src/app/src/services/actions-backend/app.ts:689:23)

This is likely to be because if we getOsUpdateStatus with a v2 running, the result is forced to 'error'. I could just make this return new error type instead?
		getOsUpdateStatus: async (uuid: string): Promise<OsUpdateActionResult> => {
			try {
				const osUpdateHelper = await getOsUpdateHelper('v1');
				const result = await osUpdateHelper.getOsUpdateStatus?.(uuid);

				if (result === undefined) {
					return { status: 'error' } as OsUpdateActionResult;
				}

				return result;
			} catch (err) {
				if (err.statusCode !== 400) {
					throw err;
				}

				// as an attempt to reduce the requests for this method
				// check whether the device exists only when the request rejects
				// so that it's rejected with the appropriate BalenaDeviceNotFound error
				await exports.get(uuid, { $select: 'id' });
				// if the device exists, then re-throw the original error
				throw err;
			}
		},

It's good that the SDK code is catching this, but I don't think we need a separate error. My concern is that the error occurs on line 689 in balena-proxy src/services/actions-backend/app.ts, where the resinhup GET is just looking up device info.
For v2, the resinhup GET should still return either 'triggered' or 'idle'. They are not really useful, but I don't understand why an error would be generated in this case. I'm concerned that backend modules like the UI will use the SDK as well, and also will get this odd error.
Is there something in the pinejs rules or SQL that is failing because the device is in an unexpected state? @Page- , any insights here?

LGTM, please rebase and squash commits. @Page- do you want to take another look?

When I do a local build, the DOCUMENTATION.md file is updated for the deprecations. I expect this update should be included with the PR. Also, please confirm that the documentation for getOsUpdateStatus() is accurate. I'm not sure it works to put the @summary and @deprecated on a single line.

When I do a local build, the DOCUMENTATION.md file is updated for the deprecations. I expect this update should be included with the PR. Also, please confirm that the documentation for getOsUpdateStatus() is accurate. I'm not sure it works to put the @summary and @deprecated on a single line.

yep, @deprecated needed a new line.


"TypeError: undefined is not a function" from react-native-camera

Description
I have been trying to use react-native-camera in my react native project but whenever I try to load RNCamera in the code it immediately throws a "TypeError: undefined is not a function". I have checked all my dependencies and they are properly installed so that is not the issue. I also get this error "ViewPropTypes will be removed from React Native, along with all other PropTypes. We recommend that you migrate away from PropTypes and switch to a type system like TypeScript. If you need to continue using ViewPropTypes, migrate to the 'deprecated-react-native-prop-types' package." whenever I first load the app. Any help would be appreciated, thanks in advance.
code:
import React, { useRef, useState } from 'react';
import { View, Text, StyleSheet } from 'react-native';
import { RNCamera } from 'react-native-camera';

export default TextScanner = () => {
  const cameraRef = useRef(null);

 return (
   <View style={{ flex: 1 }}>
     <RNCamera ref={cameraRef} style={{ flex: 1 }} />
     <View style={{ position: 'absolute', bottom: 0 }}>
     </View>
   </View>
 );
};

React Native Version
0.71.8
Output of npx react-native info
System:
OS: Windows 10 10.0.22621
CPU: (16) x64 13th Gen Intel(R) Core(TM) i7-13620H
Memory: 4.21 GB / 15.70 GB
Binaries:
Node: 18.16.0 - C:\Program Files\nodejs\node.EXE
Yarn: Not Found
npm: 9.8.1 - ~\OneDrive\Dokument\VisulaStudio Projects\FoodCheck\node_modules.bin\npm.CMD
Watchman: Not Found
SDKs:
Android SDK: Not Found
Windows SDK: Not Found
IDEs:
Android Studio: AI-223.8836.35.2231.10406996
Visual Studio: Not Found
Languages:
Java: Not Found
npmPackages:
@react-native-community/cli: Not Found
react: 18.2.0 => 18.2.0
react-native: 0.71.8 => 0.71.8
react-native-windows: Not Found
npmGlobalPackages:
react-native: Not Found
info React Native v0.72.3 is now available (your project is running on v0.71.8).
info Changelog: https://github.com/facebook/react-native/releases/tag/v0.72.3
info Diff: https://react-native-community.github.io/upgrade-helper/?from=0.71.8
info For more info, check out "https://reactnative.dev/docs/upgrading".
Steps to reproduce
npm start
Snack, screenshot, or link to a repository
Error: ViewPropTypes will be removed from React Native, along with all other PropTypes. We recommend that you migrate away from PropTypes and switch to a type system like TypeScript. If you need to continue using ViewPropTypes, migrate to the 'deprecated-react-native-prop-types' package.
TypeError: undefined is not a function
TypeError: undefined is not a function

Did not realize the react-native-camera was deprecated

@ajdnakljdkjasdnasdad have you found a solution??


Add PublicKeyProvider interface

Given the requirements of cosign, I split out the PublicKey() method into its own interface such that it can be implemented by both signers and verifiers (since both have a public key).
Also small fixes including:

ed25519 passes by value rather than pointer for public/private keys
adds SupportedAlgorithms() and DefaultAlgorithm() method for KMS SignerVerifiers (ideal for use in CreateKey() method)

Signed-off-by: Bob Callaway<EMAIL_ADDRESS>

@dekkagaijin could you please take a look? thanks!


Allow placement of caret after end of line - like IntelliJ IDEA

Setting "Allow placement of caret after end of line" in IntelliJ IDEA allows one to move caret to any location by mouse-click or arrow keys.

This feature would be very nice to have.

Duplicate of #13960


Extended AzureSearchVectorStoreRetriever and AzureSearch to support Semantic Hybrid Search with Re-Rank

Hi @efriis , Please help to review and merge changes if they are ok.
Issue:
Currently _get_relevant_documents function in AzureSearchVectorStoreRetriever class and similarity_search in AzureSearch class do not have condition to retrieve documents based on semantic hybrid score with re-rank. This PR implements it.
Dependencies:
None

Thank you for sharing the information. I will close the PR.


Current install --HEAD fails to build due to missing tmp directory

Steps to reproduce
brew install neovim --HEAD
# or when already installed
brew reinstall neovim

Expected
Installs neovim
Actual
λ brew reinstall neovim                                                                                [10:36:10] 55%🔋
==> Reinstalling neovim/neovim/neovim
==> Cloning https://github.com/neovim/neovim.git
Cloning into '/Users/ohcibi/Library/Caches/Homebrew/neovim--git'...
remote: Counting objects: 64235, done.
remote: Compressing objects: 100% (60/60), done.
remote: Total 64235 (delta 47), reused 35 (delta 18), pack-reused 64157
Receiving objects: 100% (64235/64235), 55.10 MiB | 2.49 MiB/s, done.
Resolving deltas: 100% (46226/46226), done.
==> Checking out branch master
==> Downloading https://github.com/luvit/luv/archive/146f1ce4c08c3b67f604c9ee1e124b1cf5c15cf3.tar.gz
==> Downloading from https://codeload.github.com/luvit/luv/tar.gz/146f1ce4c08c3b67f604c9ee1e124b1cf5c15cf3
######################################################################## 100.0%
==> Downloading https://raw.githubusercontent.com/neovim/deps/master/opt/LuaJIT-2.0.4.tar.gz
######################################################################## 100.0%
==> Downloading https://github.com/keplerproject/luarocks/archive/5d8a16526573b36d5b22aa74866120c998466697.tar.gz
==> Downloading from https://codeload.github.com/luarocks/luarocks/tar.gz/5d8a16526573b36d5b22aa74866120c998466697
######################################################################## 100.0%
==> Building third-party dependencies.
==> cmake ../third-party -DUSE_BUNDLED_BUSTED=OFF -DUSE_BUNDLED_GPERF=OFF -DUSE_BUNDLED_LIBUV=OFF -DUSE_BUNDLED_MSGPACK=OFF -DUSE_BUNDLED_UNIBILIUM=OFF -DUSE_BUNDLED_LIBTERMKEY=OFF -DUSE_BUNDLED_LIBVTERM=OFF -DUSE_BUNDLED_JEMALLOC=OFF -DU
Last 15 lines from /Users/ohcibi/Library/Logs/Homebrew/neovim/01.cmake:
-DUSE_BUNDLED_UNIBILIUM=OFF
-DUSE_BUNDLED_LIBTERMKEY=OFF
-DUSE_BUNDLED_LIBVTERM=OFF
-DUSE_BUNDLED_JEMALLOC=OFF
-DUSE_EXISTING_SRC_DIR=ON
-DCMAKE_C_FLAGS_RELEASE=-DNDEBUG
-DCMAKE_CXX_FLAGS_RELEASE=-DNDEBUG
-DCMAKE_INSTALL_PREFIX=/usr/local/Cellar/neovim/HEAD-838277e
-DCMAKE_BUILD_TYPE=Release
-DCMAKE_FIND_FRAMEWORK=LAST
-DCMAKE_VERBOSE_MAKEFILE=ON
-Wno-dev

CMake Error: The source directory "/tmp/neovim-20170601-52701-1jgdocb/third-party" does not exist.
Specify --help for usage, or press the help button on the CMake GUI.

If reporting this issue please do so at (not Homebrew/brew or Homebrew/core):
https://github.com/neovim/homebrew-neovim/issues

These open issues may also help:
Can't install via homebrew-neovim if luarocks path is set explicitly https://github.com/neovim/homebrew-neovim/issues/149
TERM=xterm-256color brew reinstall neovim  15.67s user 6.94s system 36% cpu 1:01.55 total

Something is wrong with buildpath.
buildpath should be /tmp/neovim-20170601-52701-1jgdocb/neovim--git, but actually /tmp/neovim-20170601-52701-1jgdocb/.

Bisecting brew, homebrew/brew#d34ba73 breaks the installation.

The problematic commit has been reverted.
Please try again.

Thanks @equal-l2 !


moved ProvenHeadersConsensusManagerBehavior

moved ProvenHeadersConsensusManagerBehavior.cs to Stratis.Bitcoin.Features.Consensus project

@dangershony  here it is


Update ReadME

Hi @yagizhanNY ,
Great work and I want to use the component library for my .NET8 based blazor project, can you update the documentation on how to use it

The readme should be up to date in that regard. Can you please describe your problem with the current readme?

Hi @asheesh1996, actually noting changes with .NET8. Installation process is same. But it would be good to add supported .NET version in README 👍

Is it still ongoing issue for you? @asheesh1996

If it's still ongoing please re-open the issue.


Implement masquerade CIDRs

Implements #9
Note:

I thought about adding an option that allow one to toggle the insertion of the last catch-all rule, but decided against it
I thought about changing the comments in the iptables rules, since the categorization of traffic as local and outbound in them doesn't seem to always hold, but it didn't seem important enough to get into
I am not proficient in Golang

What's the status on this one? Any reason why it can't be merged? It's a nice feature indeed.

/assign @MrHohn
can you tell us what we need to do to get this merged?

@TheWolfNL Sorry this dropped off the radar. Will take a look soon.


fix: test 2

Description
fix: test 2

💚 All backports created successfully

Status
Branch
Result

✅
release/v0.54

Questions ?
Please refer to the Backport tool documentation and see the Github Action logs for details


fix redacting personal info from analytics data on Prometheus-side

While working on documentation I found that there are two problems with redacting personal info from analytics data on Prometheus-side:

the rule drops too much (it should only drop user_name and user_email, it drops everything starting with user)
it somehow gets stripped from the ServiceMonitor in most installations 🤔

Re 2) as you can see the metricRelabelings is only there on anchovy and beaver:
❯ opsctl kubectl -i (opsctl list installations --short | tr ' ' ',') -- --namespace=monitoring get servicemonitor/macropower-analytics-panel-server -o jsonpath='{range .spec.endpoints[*]}{.metricRelabelings}{end}'
Querying 37 installations...

=====> installation: gopher
        Could not boot kubeConfigService: execution failed error

=====> installation: geckon
        Could not boot kubeConfigService: execution failed error: no healthy jumphost found

=====> installation: puma

=====> installation: anubis

=====> installation: buffalo

=====> installation: ghost

=====> installation: bandicoot

=====> installation: anchovy
[{"action":"labeldrop","regex":"(user.*)"}]

=====> installation: viking

=====> installation: eagle

=====> installation: exodus

=====> installation: valkyrie

=====> installation: orion

=====> installation: victory

=====> installation: gaia

=====> installation: visitor

=====> installation: gorgoth

=====> installation: flamingo

=====> installation: beaver
[{"action":"labeldrop","regex":"(user.*)"}]

=====> installation: asgard

=====> installation: otter

=====> installation: talos

=====> installation: kudu

=====> installation: godsmack

=====> installation: seal

=====> installation: gauss

=====> installation: anteater

=====> installation: gorilla

=====> installation: gollum

=====> installation: antelope

=====> installation: alpaca

=====> installation: goku

=====> installation: ginger

=====> installation: gremlin

=====> installation: akita

=====> installation: argali

=====> installation: giraffe

We had a look at this with Theo, got the labels handled, these PRs should sort them out:

https://github.com/giantswarm/config/pull/418
https://github.com/giantswarm/macropower-analytics-panel-server-app/pull/23
https://github.com/giantswarm/prometheus-rules/pull/89

Once they're merged we'll need to do releases of those three repos and we should be good.
We also noticed that when deploying test builds, the ServiceMonitors were suddenly restored and contained all the needed values. We suspect that last version of the macropower-analytics-panel-server-app was deployed back when Kyverno rules for ServiceMonitors were still in place, so they were mutated on deployment, but after the rules were reverted the ServiceMonitors were just left as-is.
I'll double-check them after the new releases are out. If our suspicions are correct, new releases should sort that out too.

PRs merged.
Release PRs:

https://github.com/giantswarm/prometheus-rules/pull/91
https://github.com/giantswarm/config/pull/422
https://github.com/giantswarm/macropower-analytics-panel-server-app/pull/24

Releases:

https://github.com/giantswarm/config/releases/tag/v1.90.0
https://github.com/giantswarm/macropower-analytics-panel-server-app/releases/tag/v0.4.0
https://github.com/giantswarm/prometheus-rules/releases/tag/v0.19.0

Everything deployed and working fine. Incident closed.


#15542: Add dtype to to_torch

Ticket
https://github.com/tenstorrent/tt-metal/issues/15542
Problem description
import pytest
import torch
import ttnn

torch.set_printoptions(threshold=1000000, linewidth=100000000, sci_mode=False)

@pytest.mark.parametrize("ttnn_dtype, torch_dtype", [
    [ttnn.DataType.FLOAT32, torch.float32],
    [ttnn.DataType.BFLOAT16, torch.bfloat16],
    [ttnn.DataType.BFLOAT8_B, torch.bfloat16],
],)
def test_support_1d(device, ttnn_dtype, torch_dtype):
    torch_x = torch.rand(20, dtype=torch_dtype)

    ttnn_x_bf16 = ttnn.from_torch(torch_x, dtype=ttnn.DataType.BFLOAT16, layout=ttnn.TILE_LAYOUT)
    ttnn_x = ttnn.from_torch(torch_x, dtype=ttnn_dtype, layout=ttnn.TILE_LAYOUT)
    torch_y = ttnn.to_torch(ttnn_x)

    print("ttnn_dtype", ttnn_dtype)
    print("torch_dtype", torch_dtype)
    print("torch_x\n", torch_x)
    print("ttnn_x_bf16\n", ttnn_x_bf16)
    print("ttnn_x\n", ttnn_x)
    print("torch_y\n", torch_y, type(torch_y))

In the unit test, the to_torch function is used to convert ttnn tensors to torch tensors.
However, the dtype conversion in to_torch is as follows:
ttnn -> torch
BFLOAT16-> bfloat16
FLOAT32-> float32
BFLOAT8_B -> float32
Since PyTorch does not have a bfloat8_b type, it is not an issue that it converts to float.
However, the problem with from_torch is that it has a dtype parameter, while to_torch requires an additional conversion using to(dtype=torch_dtype), which makes it a bit cumbersome.
What's changed
Add dtype to to_torch
Add test.
Checklist

[ ] Post commit CI passes
[ ] Blackhole Post commit (if applicable)
[ ] Model regression CI testing passes (if applicable)
[ ] Device performance regression CI testing passes (if applicable)
[x] New/Existing tests provide coverage for changes

You mean output_dtype are providing TT-NN type, not torch type.
I think this API will be confusing for users.
I am ok if this output type is torch type

You mean output_dtype are providing TT-NN type, not torch type.
I think this API will be confusing for users.
I am ok if this output type is torch type

Ah, my mistake. The dtype should be torch type.
I will make the correction.


Leave ca-certificates installed

A common use-case for the mongo image is to easily access the MongoDB CLI
where one is not natively installed. However, the mongo image currently
ships without ca-certificates which causes the CLI to fail when connecting
to MongoDB servers that require SSL.
The ca-certificates package is already installed during the build process
of this image, but it is removed during the build. This commit changes the
Dockerfile to leave ca-certificates installed. The size increase is
modest (~ 1 MB) but the increase in usefulness is vast.

Can confirm!  According to our Travis build logs, we're at ~359.7MB before this change, and ~360MB after. :+1:
I'm +1 on the change in general, although I think the installation of ca-certificates needs to move up to the section where we install jq and numactl and be removed entirely from the section that's dealing with gosu (especially so we don't lose the side effect of that RUN installing ca-certificates and leaving it there).

@tianon, thanks for the suggestion, good point. I incorporated it in my PR.


Start of Feature Bars in Release Not Corresponding to Story Start Dates

First off, GREAT WORK!!
Can you please explain the logic that determines where the start of the feature bars are placed? I assumed it was to be the start of a user story being transitioned from proposed to the active state, but that does not seem to line up with our situation.
TIA!
MR
PS. Do you have a place for submitting feedback and suggestions for new capabilites?

@maxxis, can you give me an example? Please ensure that the team subscribes to the iterations the stories are in.
Please feel free to create issues for feature requests.

Here is an example of what I'm asking for:

Thanks @maxxis ... is the team still subscribes to those sprints that finished long ago? If not then we do not consider those sprints.

@navneetg-msft, can you please explain what you mean by subscribed? Also, what do you mean by long ago, is that supposed to mean greater than 5 sprints?

@maxxxis I can setup a quick skype call and we can go over this, it will be easier to communicate.
Please send me an email at<EMAIL_ADDRESS>and I can setup a call.

As we have not heard back on this for about 3 weeks, we are closing the issue. Please reopen when you have time to work on it.


Mapped out a few resource-related stuff

I need them for my mod! Please take it!
Signed-off-by: liach<EMAIL_ADDRESS>

thanks!


Can't see this in HACS

This comes highly recommended by a few people on the Agile Chat in facebook.  I would love to install it but for some reason can't see it in HACS.  If i try and add it as a custom repository,  it wont let me.
Am I doing something wrong?

Have you got AppDaemon installed within Home Assistant already (Supervisor -> Add on store)?
If so you should be able to find Octoblock from the Automations page of HACS...

So I checked and I didnt have 'Automation' as an option.  Did a bit of research and there is a setting in the HACS integration for enabling AppDaemon discovery.  Ticked that and its working fine.  Thanks!


pg is not available during auth

It would be nice to be able to use pg on the request object inside an auth strategy. By attaching at preAuth instead of preHandler it becomes possible to use request.pg.client inside the auth strategy.

Thanks for opening an issue. You can pass an option to control which mount point pg will be available in. See: https://github.com/jedireza/hapi-node-postgres#usage

Awesome, thank you.


Add environment variable to suppress packaging warnings

Summary
This PR adds a new env variable QISKIT_SUPPRESS_PACKAGING_WARNINGS and a
matching user config file option suppress_packaging_warnings which can be used to optionally
suppress the regular warnings about aer and/or ibmq-provider missing at import time. This strikes
a balance between telling users who potentially have a packaging issue that would otherwise go
by unnoticed and giving users who are intentionally (or unable to) install the components the ability to disable the warnings.
Details and comments
Some platforms (in my case IBM i) cannot reliably build newer versions qiskit-aer due to new dependencies, etc. In my case, I want to pursue qiskit use with only terra (and show others), but the constant RuntimeWarning is an annoyance easily (incorrectly) perceived as an error.
In short, I'd like a way to suppress that warning, and I think an environment variable is a cheap and easy way to do so.
Co-authored-by: Matthew Treinish<EMAIL_ADDRESS>

Yes, that example code using the warning filter does address my use case. I'm happy with that since it is documented (I didn't want to blindly apply a warnings filter and didn't read the doc).
I do like both of your suggestions. QISKIT_SUPPRESS_PACKAGING_WARNINGS seems a good choice, and adding to the user_config certainly makes sense. Of course, I'm not sure how many people are out there building terra and aer from source. If I'm the only one who cares, we can table the idea. Or, I can clean it up and make the necessary changes.

Yeah, I think it's worthwhile even if it's not for the majority of users I think that there is a big enough set of users where this matters.
I actually hit this personally because on one of my systems I'm fighting a packaging issue with ibmq and the import doesn't ever work which always emits a warning. So having a way to filter it easily outside of the calling script would be handy.
I think that this will make the developer experience a bit more friendly. The warnings were mostly added as a stopgap against frequent bug filings because of the fragility of python packaging, especially around namespace packages. But, that was a conscious tradeoff of annoying people with more specialized use cases. So having a builtin workaround for that is a good idea.

@ThePrez is there any update on this?

Sorry. I haven't had time to circle back around and finish this up in other places. I probably won't be able to dig back into this for another couple weeks. We can let simmer, or we can merge the trivial changes in this PR and keep a work item open for the qiskit user config file and also ibmq if needed.

@ThePrez I went ahead an updated this, it's been sitting idle for several months and we'd really like to get this feature in the next release.

That's a fair point, the env variable should take precedence over the user config file. We don't have it with env vars anywhere but it does exist for the parameters (like visualization backend)

@kdk ok I updated the logic in https://github.com/Qiskit/qiskit-terra/pull/3362/commits/4f5f8eaa7c5e05e6de9d19a7ad620e32521d79ac the env var set to N will override the user config file setting