DLopen flags

atm, dlopen flags are translated via ctypes_resolve_dl_flag, using the enum dl_flags_caml.
This function is only partial, and throws assertion failure if the received flag is not defined on the current platform.
I wonder if this is intentional -- AFAICS on MacOSX RTLD_DEEPBIND is implicit, and it is not defined on FreeBSD.  A user of ctypes currently needs to write the boilerplate to check whether the current platform defines RTLD_DEEPBIND, and if it does, pass it to dlopen, if not, do not pass it there.
Wouldn't it be more convenient if ctypes would ignore dlopen flags passed to it, but not defined on the current platform?

This function is only partial, and throws assertion failure if the received flag is not defined on the current platform.

We should certainly do better than this.
Is ignoring flags that aren't supported always reasonable behaviour?  If RTLD_DEEPBIND is implicit, then ignoring it seems fine, but ignoring flags might have surprising effects in other cases.  For example, RTLD_NODELETE is not the default, not supported everywhere, and changes the behaviour of the program, so ignoring it could produce silently wrong results.
Would it be useful for Dl to expose some way of checking whether a flag is available on the current platform?

On 29/03/2017 09:41, yallop wrote:

Is ignoring flags that aren't supported always reasonable behaviour?  If RTLD_DEEPBIND is implicit, then ignoring it seems fine, but ignoring flags might have surprising effects in other cases.  For example, RTLD_NODELETE is not the default, not supported everywhere, and changes the behaviour of the program, so ignoring it could produce silently wrong results.
Would it be useful for Dl to expose some way of checking whether a flag is available on the current platform?

I suspect the answer is true - and this would solve my concrete problem.
Thanks for the information on RTLD_NODELETE (I didn't know).

A patch implementing this (i.e. doing better than assert(0) in the flag translation, and exposing a way of checking for flag availability) would be very welcome.

On 30/03/2017 10:59, yallop wrote:

A patch implementing this (i.e. doing better than assert(0) in the flag translation, and exposing a way of checking for flag availability) would be very welcome.

indeed.  a patch would be very welcome.  let's hope someone will find
some time for this.


Uri validation issue on Replicate

When attempting to use this model on Replicate I get an error in relation to the format of the URI which does not have the extension ".mp4" at the end of the path
This is typical in S3 and presigned URLs with their signature
Ideally this restriction should be adjusted parsing the URL to detect the file extension across the entire path string rather than just the end

Apologies, the length of the video url was to long and the request was failing at OS level


Map search replaces new search word with old one

This is a really strange effect, you should have seen it yourself when doing a unit-test.

Open test.loklak.net
search for "stone"
click on the map - > this shows results for stone (so far ok)
enter in the search box "water"
the map shows again in the search box the word "stone" and shows results for "stone" (but far less, but thats another problem)

@fuksi @Orbiter Has this been solved?

I didn't realize this issue until now.
I also noticed the issue and did a patch long time ago to fix this. The obstacle is when trying to delete the old map.
The solution is ( I don't think it the best, but it works ok for user experience), the application will detect if you already did a map search, and try to do a new map search, the url will be changed for the new search and the page is reload.

I just tested this and the behaviour did not change at all. Please point me to the commit where you 'fixed' this.

The same behaviour can be seen on the 'videos' view, but not on the 'photos' view where it works correctly.

The old solution in in here, on line 36-38 : https://github.com/loklak/loklak_webclient/blob/master/app/js/directives/globalSearchForm.js
However the solution seems obsolete with many cases. I found a way to deal with removing old map. Will create a PR today, possibly along with the solution for behavior in videos filter.


maybe fixing 7b79b00

it seems like I did something wrong in 7b79b00, but idk. This needs testing before it can be merged.

lgtm!


Patch to allow arbitrary arguments

This patch addresses issue #62. This patch allows arbitrary arguments being passed to cp. This requires the user to be responsible for setting up appropriate parameters.
F5 Command
{file} = {dir}/{name}{ext}
python -i {file}

The code above examplifies what I stated in issue #62.

the format cp is designed to take is
repl [options... [args...]] {file}
where the last arg, {file}, must always be a file.
I should have just used argparse and used - as the option termination symbol. it'd be quicker to write up, easier to maintain, and allow people do what they expect.
for example
repl [options...] [args...]
would work much better.

The patch now allows the code below to be executed as well; without any issues.
F5 Command
{file} = {dir}/{name}{ext}
python -i {file} hello there world

I'll pull and test it hours later (I am working now) then publish the patch.

v0.9.4 is published, fixed #36 by the way.


Lack of scalability

I tested CaffeOnSpark on 3 node Spark cluster, with one GPU per node. Here are the results for MNIST (wall time):
GPU mode:
3 executors: 183 seconds
1 executor, 75 seconds
CPU mode:
3 executors: 101 seconds
1 executor: 353 seconds
Conclusions:

Distributed CPU mode outperforms distributed GPU mode by a wide margin
Single executor in GPU mode outperforms distributed GPU configuration
Slowest configuration is single node CPU mode

Seems that solutions doesn't scale in GPU mode. Can someone explain why and suggest what to look for to improve this?
Thanks.

MNIST is too small.
Do the same comparison on a larger neural network and a larger database, for example, inception-v3 (or VGG16) on imagenet dataset.


dragdealer.min.js is Broken or Outdated

The version of dragdealer.min.js that's currently in lib doesn't appear to be up to date with the version of dragdealer.js in src. I discovered this when trying to set dragStopCallback(x,y) and dragStartCallback(x,y), which seem to be completely missing from the minified version.
Furthermore, these two options are documented inside the dragdealer.js and index.html files, but the main web site at http://skidding.github.io/dragdealer/ hasn't been updated to reflect this - it probably ought to be.
Thank you.

You're right, lib/dragdealer.min.js was outdated. Removed it altogether and pointed to the cdnjs link instead.
As for the missing documentation for the drag callbacks, feel free to open a separate issue/pull request for that.

Great - thanks for updating the minified version. I see that the web site is up to date now as well. Cheers.


How to run the unit tests and get the angular reference?

Do you know how to get the angular modules references from jasmine tests?

sorry haven't really worked with this for a while :(

I had to modify the karma.conf.js according to this document http://mike-ward.net/2015/09/07/tips-on-setting-up-karma-testing-with-webpack/ and it worked:
module.exports = function (config) {
  const webpackConfig = makeWebpackConfig({
    devtool: 'source-map',
    separateStylesheet: true,
    debug: true,
    cover: process.env.COVERAGE,
  });
  webpackConfig.entry = undefined; // add this line
  ...
    preprocessors: {
      'src/index.js': ['webpack', 'sourcemap'], // add this line
      'src/**/*.test.js': ['webpack', 'sourcemap'],
    },
  ...

Include just the /.test.js$/ files in the ./src/index.test.js file:
// load all js sources
const testsContext = require.context('./', true, /\.test.js$/);
testsContext.keys().forEach(testsContext);


Showcase the implementation of Table Widget

Table widget needs to be added to the widget catalog. There should be two tabs within the page, one tab named "Description' to describe the widget and another tab named 'Implementation' to show the implementation of the widget. Please make sure that the implementation has all the different features of the widget like different alignments, widths and border. Please attach the screenshot of your work in the PR.

I would like to work on this widget.

I would like to work on this widget.

Sure, I'll assign this issue to you. Good Luck!


Add community guidelines to the documentation or README

Towards my review in openjournals/joss-reviews#2597 I have identified that there is not a clear and accessible description for, quoting the review checklist, " third parties wishing to 1) Contribute to the software 2) Report issues or problems with the software 3) Seek support".
Please provide this information in a readily-available location, in practice the documentation and/or README file. A few paragraphs could suffice to cover those three components. Thanks.

Hi,
Thank you for raising that issue.
This issue was also raised by @eviatarbach in his review and is adressed by the commits:
https://github.com/Climdyn/qgs/commit/f87022c6c1f5d5909129fdbba029566f07b1d2bb
https://github.com/Climdyn/qgs/commit/c6a7deefa29f730542a18a206026f269b4c16c2b
in the joss branch. These will be merged into the master when the review process is completed.

Thanks @jodemaey, that addresses the issue well so I will close this. I have now ticked the relevant review checklist item.


Temporary Synapse limit reduction for AzureForStudents

Temporary limit decrease for AzureForStudents

#sign-off

#sign-off

#sign-off

@matt1883 - I'll merge this, but as a Microsoft FTE you should be working in the private repo. Here's some info:

Microsoft authors and contributors need to make content contributions through the private repository so the content can be staged and validated by the current validation rules.
After you make your changes in the private repo, review the articles on staging, and fix any validation issues, you can add the sign-off comment to let PR reviewers know that the updates are ready to be merged.
Read about authors working in the public repo for more information.
If you need help getting set up to work in the private repo, see Get started contributing to the Microsoft Learn platform.


Fix Jittering

setInterval is known to be flaky at high frequency. Switched to a method
described here : https://stackoverflow.com/a/16580064/103916
Feel free to try it localy to see the difference.
Should fix : #26

What about requestAnimationFrame()?


selectedIndexChanged and multi template does not work in my project

Hi @triniwiz
I have here an example of implementation where the latest version doesn't work properly and I don't know what is wrong.
Can you take a look, please ?

First it's selectedIndexChange and not selectedIndexChanged https://github.com/triniwiz/nativescript-pager/blob/master/demo-ng/app/test/test.component.html#L6 also you can try the demo see if that can help if not i'll run some tests later

I found it.
$event.value instead of $event.oldIndex
It was my mistake.


Notification of background job is not getting dismissed even after job completion

Hi,
I noticed 2 issues with the latest version 2.2.0 where notificationText and notificationTitle are added:

My app also shows another persistent notification from a different plugin. However, after upgrade to latest, this plugin's notification replaces the other one which is wrong.
Even after background job is completed, the notification is not removed and even I am not able to swipe it to dismiss.
Thanks for the superb plugin. Let me know if anything else needed.

Thanks

Interesting, I haven't used it with another persistent notification lib. What I could see as a possible issue is both libs using the same notification channel 1. It is defined here:
https://github.com/vikeri/react-native-background-job/blob/b1b64afa6406c499173fe065d8c538bbd77ec0a7/android/src/main/java/com/pilloxa/backgroundjob/ReactNativeEventStarter.java#L74
Could you check what your other lib is using? And try updating that line directly in node_modules and rebuilding to see if issue still occurs.

Hi,
Thanks for the feedback but I won't be able to check that as I am outside.
FYI, the other library is:
https://github.com/mauron85/react-native-background-geolocation
if that helps.
Thanks

Hey,
I have the same problem as the 2nd one:

Even after background job is completed, the notification is not removed and even I am not able to swipe it to dismiss.

This happens very rarely though and only one user reported this to us. However, we would prefer that it doesn't happen at all.
Is there a way to disable the notifications altogether or it's necessary for the Bg-Job to work?

Same

Hey,
I have the same problem as the 2nd one:

Even after background job is completed, the notification is not removed and even I am not able to swipe it to dismiss.

This happens very rarely though and only one user reported this to us. However, we would prefer that it doesn't happen at all.
Is there a way to disable the notifications altogether or it's necessary for the Bg-Job to work?

Unfortunately foreground notifications are needed for Android to allow the jobs to run at all. I have never experienced this myself so I'd need a repro case when it happens to be able to debug.


Python: highlight docstrings differently from strings literals

Sorry if this is the wrong project to request this feature.  GitHub is currently using MagicPython to highlight Python code. And MagicPython assigns distinct scopes to docstrings (there is a .docstring. extra scope):
string.quoted.docstring.multi.python
string.quoted.docstring.raw.multi.python
string.quoted.docstring.raw.single.python
string.quoted.docstring.single.python

It would be really cool if GitHub could color docstrings differently from regular string literals. Here's how it might look like:

Shouldn't MagicPython assign the scope comment.block.docstring. to docstrings?
In any case, it's not something that can be changed in Linguist. You'll have better chances of being heard at MagicPython or by contacting<EMAIL_ADDRESS>;)

Alright, I'll try contacting support. Sorry for the disturbance!


Add benchmark script

Fixes #17
As discussed a while ago with @PicoCentauri , this adds a benchmark script, designed to emulate a "typical" training workload. The idea is that we agree to run this before major merges, to make sure we don't cause performance regressions.
The script runs Ewald and PME, with and without Metatensor, for CsCl crystals of various sizes. The results are saved as .yaml, with some diagnonstic information. An example output can be seen in #80. The script already worked quite nicely to pointint that something was wrong in that case...
We could consider making some additional repository for the .yaml and make a nice plot of performance, hopefully, increasing over time.

📚 Documentation preview 📚: https://torch-pme--81.org.readthedocs.build/en/81/

What is the status here @sirmarcel ?


Transfer right join to left join

Which issue does this PR close?

No
Rationale for this change

This ticket transfers Right Join to Left Join. This will facilitate logic optimization, including predicate push-down, join order exchange, and some future optimization, with one less processing case, and our code logic will also be simplified.
BTW, postgres also did the thing.
What changes are included in this PR?

Are there any user-facing changes?

No

I am not sure we would want to do this?
As a user that might want more control over the execution and join order (to save time, memory in a specific query) currently can help DataFusion a bit by using the smaller side in a join as the left side, or even disable the optimization rule to have full control.
This usage becomes harder when we choose to not respect the SQL syntax and instead encode a right join as a left join even if the user carefully picked the smaller left side in his query?

This usage becomes harder when we choose to not respect the SQL syntax and instead encode a right join as a left join even if the user carefully picked the smaller left side in his query?

If I read the source code rightly, we'll optimize the smaller side in a join as the left side during the physical plan phrase (even if the user doesn't do it in SQL)?
So I think we should reserve Right Join in Join Type, and then it'll be used during the physical plan phrase. In addition, our dataframe API  users also need the Right Join in Join Type.
I think this ticket will only facilitate logic optimization,  with one less processing case, and our code logic will also be simplified.

This usage becomes harder when we choose to not respect the SQL syntax and instead encode a right join as a left join even if the user carefully picked the smaller left side in his query?

If I read the source code rightly, we'll optimize the smaller side in a join as the left side during the physical plan phrase (even if the user doesn't do it in SQL)?
So I think we should reserve Right Join in Join Type, and then it'll be used during the physical plan phrase. In addition, our dataframe API  users also need the Right Join in Join Type.
I think this ticket will only facilitate logic optimization,  with one less processing case, and our code logic will also be simplified.

That's true - but a user can also disable that specific optimization in the configuration if he wants to make sure the order is preserved. After all, the reordering is/might be based on heuristics instead of complete knowledge about the biggest / smallest side.

I agree with @Dandandan  that keeping the Left and Right enum and not trying to change from Right to Left implicitly is probably the best thing to do for now as it allows users to explicitly control what the join order is.

I agree with @Dandandan that keeping the Left and Right enum and not trying to change from Right to Left implicitly is probably the best thing to do for now as it allows users to explicitly control what the join order is.

Ok, I'll close the ticket.

Thanks @xudong963  -- I appreciate your flexibility and understanding


Push Notifications Are Not Configured

Hi, I have the 3.6.3PE version of Thingsboard. I have downloaded all the packages to create the application, and everything works fine except for push notifications, just like in the previous versions.
I followed the guide to integrate Firebase with Flutter to enable push notifications. I built an APK to test it. By going to the app's permissions, I can actually enable the notifications (previously I couldn't even see them). I enabled them, logged in, and checked that the dashboard, alarms, etc., work, and everything is functioning correctly. At this point, I did a notification check.
I went to "More," clicked on "Notifications," and I get the message "Notifications are not configured. Please contact your system administrator" (light gray button).
I inserted the JSON into Thingsboard
I executed flutterfire configure
Followed the documentation
How can I resolve this?

Hello @YuriYabe!
After running flutterfire configure, you should see changes in lib/firebase_options.dart. Can you confirm if you are seeing these changes?

Hi @ybeshkarov  , thanks for your response! Yes, I see the changes. Actually, I managed to resolve it during the night. I deleted the firebase_options file and when I did flutterfire configure, it recreated it correctly! I see the notifications now.
However, as soon as I open the app, I get a message "path '/api/notifications/unread/count': not found." I can close it, but it appears every time I reopen the app! In fact, I can't see the unread notifications. Do you have any idea what the problem might be? Tonight I will try to rebuild the app from scratch!
(At least the notifications arrive; if I go under "all" I can see them. The problem is only with the "unread" ones.)

Hi @ybeshkarov , thanks for your response! Yes, I see the changes. Actually, I managed to resolve it during the night. I deleted the firebase_options file and when I did flutterfire configure, it recreated it correctly! I see the notifications now.
However, as soon as I open the app, I get a message "path '/api/notifications/unread/count': not found." I can close it, but it appears every time I reopen the app! In fact, I can't see the unread notifications. Do you have any idea what the problem might be? Tonight I will try to rebuild the app from scratch!
(At least the notifications arrive; if I go under "all" I can see them. The problem is only with the "unread" ones.)

UPDATE: (Now I still have the same error, but when I go to "unread" I can see the notifications.)

Hi @YuriYabe,
It's good to hear that the notifications are working for you now.
The error message path '/api/notifications/unread/count': not found indicates that your ThingsBoard instance doesn't have the specified endpoint https://thingsboard.cloud/swagger-ui/#/notification-controller/getUnreadNotificationsCountUsingGET.
This endpoint was added in version 3.6.4.

Closed due to no further action required. Please reopen if the issue persists.


/delay not documented?

I'm really sorry if I'm blind, but looking at the source doesn't have the word delay in it at all. Yet /delay/2/ works.
Should it be documented? I only found it because I had this tickling feeling in my brain that it used to exist, and then I found it mentioned here in the bug tracker.

https://github.com/postmanlabs/httpbin/blob/master/httpbin/core.py#L1195

Hm, perhaps github search failed me, but does it appear in the documentation /

Hm, perhaps github search failed me, but does it appear in the documentation?

https://httpbin.org/#/Dynamic_data/get_delay__delay_
Category "Dynamic data -> delay"

@mlissner close?

 Sorry for wasting time here. Yes, closing!

 Sorry for wasting time here. Yes, closing!

Don't blame yourself, we all make mistakes 😉


Supporting pipes in providers

10.5.0 has been released and contains a fix for the issue.
Feel free to reopen the issue or to submit a new one if you meet any problems.


Change dns to *.dev

How can I use *.dev instead of *.docker?

This isn't possible today, but we could add a preference and modify dnsmasq.rb to allow defining the TLD.

@codekitchen had a go at implementing this #124


Potential Issue with Newer Instance Types and etcd

I was standing up a production cluster and wanted to use an m5.large instance type for my etcd nodes. However they never stood up. I went back to using a t2 instance type and they stood up and I could carry on setting up everything.
Here are the logs from the failed etcd node:
Apr 09 14:23:12 ip-10-100-9-140.us-east-2.compute.internal systemd[1]: Starting cfn-signal.service...
Apr 09 14:23:12 ip-10-100-9-140.us-east-2.compute.internal systemctl[1852]: inactive
Apr 09 14:23:12 ip-10-100-9-140.us-east-2.compute.internal systemd[1]: cfn-signal.service: Control process exited, code=exited status=3
Apr 09 14:23:12 ip-10-100-9-140.us-east-2.compute.internal systemd[1]: cfn-signal.service: Failed with result 'exit-code'.
Apr 09 14:23:12 ip-10-100-9-140.us-east-2.compute.internal systemd[1]: Failed to start cfn-signal.service.
Apr 09 14:23:22 ip-10-100-9-140.us-east-2.compute.internal systemd[1]: cfn-signal.service: Service hold-off time over, scheduling restart.
Apr 09 14:23:22 ip-10-100-9-140.us-east-2.compute.internal systemd[1]: cfn-signal.service: Scheduled restart job, restart counter is at 108.
Apr 09 14:23:22 ip-10-100-9-140.us-east-2.compute.internal systemd[1]: Starting etcdadm reconfigure runner...
Apr 09 14:23:22 ip-10-100-9-140.us-east-2.compute.internal systemd[1]: Stopped cfn-signal.service.
Apr 09 14:23:22 ip-10-100-9-140.us-east-2.compute.internal systemctl[1855]: inactive
Apr 09 14:23:22 ip-10-100-9-140.us-east-2.compute.internal systemd[1]: etcdadm-reconfigure.service: Control process exited, code=exited status=3
Apr 09 14:23:22 ip-10-100-9-140.us-east-2.compute.internal systemd[1]: etcdadm-reconfigure.service: Failed with result 'exit-code'.
Apr 09 14:23:22 ip-10-100-9-140.us-east-2.compute.internal systemd[1]: Failed to start etcdadm reconfigure runner.
Apr 09 14:23:22 ip-10-100-9-140.us-east-2.compute.internal systemd[1]: Dependency failed for etcd (System Application Container).
Apr 09 14:23:22 ip-10-100-9-140.us-east-2.compute.internal systemd[1]: Dependency failed for etcdadm update status.
Apr 09 14:23:22 ip-10-100-9-140.us-east-2.compute.internal systemd[1]: etcdadm-update-status.service: Job etcdadm-update-status.service/start failed with result 'dependency'.
Apr 09 14:23:22 ip-10-100-9-140.us-east-2.compute.internal systemd[1]: etcd-member.service: Job etcd-member.service/start failed with result 'dependency'.

Digging around i traced it to the var-lib-etcd2.mount that is a requirement of the etcd-member.service. It was returning these errors:
Apr 09 17:34:22 ip-10-100-7-66.us-east-2.compute.internal systemd[1]: Dependency failed for /var/lib/etcd2.
Apr 09 17:34:22 ip-10-100-7-66.us-east-2.compute.internal systemd[1]: var-lib-etcd2.mount: Job var-lib-etcd2.mount/start failed with result 'dependency'.
Apr 09 17:35:54 ip-10-100-7-66.us-east-2.compute.internal systemd[1]: Dependency failed for /var/lib/etcd2.
Apr 09 17:35:54 ip-10-100-7-66.us-east-2.compute.internal systemd[1]: var-lib-etcd2.mount: Job var-lib-etcd2.mount/start failed with result 'dependency'.

Not sure if its something with the way the drives are setup or what, but figured I would pass along.

Seems like the same for me too, with c5.large:
Apr 13 07:58:38 ip-10-0-0-152.ap-northeast-1.compute.internal systemd[1]: dev-xvdf.device: Job dev-xvdf.device/start timed out.
Apr 13 07:58:38 ip-10-0-0-152.ap-northeast-1.compute.internal systemd[1]: Timed out waiting for device dev-xvdf.device.
-- Subject: Unit dev-xvdf.device has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit dev-xvdf.device has failed.
--
-- The result is RESULT.
Apr 13 07:58:38 ip-10-0-0-152.ap-northeast-1.compute.internal systemd[1]: Dependency failed for Formats etcd2 ebs volume.
-- Subject: Unit format-etcd2-volume.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit format-etcd2-volume.service has failed.
--
-- The result is RESULT.
Apr 13 07:58:38 ip-10-0-0-152.ap-northeast-1.compute.internal systemd[1]: Dependency failed for /var/lib/etcd2.
-- Subject: Unit var-lib-etcd2.mount has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit var-lib-etcd2.mount has failed.
--
-- The result is RESULT.
Apr 13 07:58:38 ip-10-0-0-152.ap-northeast-1.compute.internal systemd[1]: var-lib-etcd2.mount: Job var-lib-etcd2.mount/start failed with result 'dependency'.
Apr 13 07:58:38 ip-10-0-0-152.ap-northeast-1.compute.internal systemd[1]: format-etcd2-volume.service: Job format-etcd2-volume.service/start failed with result 'dependency'.
Apr 13 07:58:38 ip-10-0-0-152.ap-northeast-1.compute.internal systemd[1]: dev-xvdf.device: Job dev-xvdf.device/start failed with result 'timeout'.

I slightly remember that someone told me that device names are different in newer instance types with its EBS volumes exposed as NVMe block devices:
$ ls -lah /dev/ | grep 'nvme\|xvdf'
crw-------.  1 root root    249,   0 Apr 13 07:55 nvme0
brw-rw----.  1 root disk    259,   0 Apr 13 07:56 nvme0n1
brw-rw----.  1 root disk    259,   1 Apr 13 07:56 nvme0n1p1
brw-rw----.  1 root disk    259,   2 Apr 13 07:56 nvme0n1p2
brw-rw----.  1 root disk    259,   3 Apr 13 07:56 nvme0n1p3
brw-rw----.  1 root disk    259,   4 Apr 13 07:56 nvme0n1p4
brw-rw----.  1 root disk    259,   5 Apr 13 07:56 nvme0n1p6
brw-rw----.  1 root disk    259,   6 Apr 13 07:56 nvme0n1p7
brw-rw----.  1 root disk    259,   7 Apr 13 07:56 nvme0n1p9
crw-------.  1 root root    249,   1 Apr 13 07:55 nvme1
brw-rw----.  1 root disk    259,   8 Apr 13 07:55 nvme1n1

We just used a different instance type for the time being. Should I close this or leave it open?

@kylegato Thanks for the confirmation 👍
Let's keep this open so that we won't forget adding support for c5/m5 series.

Just found this issue and wanted to chime in - I spun up a cluster with c5.9xlarge as one of my worker node pool and the cluster seems to have come up ok.
Is this issue only appearing if I have an external mount point or something along those line? Or should I have run into this issue with root volume?
It seems this is fixed now?


The Command autoload approach, core and module-based

See https://github.com/wireshell/wireshell/blob/feature/autoload/app/wireshell.php#L110 - core Command loading works fine with this, but I can't (literally) grasp potential Command files within /site/modules dir, also regarding their namespace and how to introduce them to the composer autoloader/psr-4. Any ideas @clsource @justonestep ?

I propose creating a module for PW with hookable methods and an admin page. Then you enable/disable custom commands. That creates a json file that wireshell could use for autoloading. The module checks for possible conflicts.

I found a simple config syntax called neon
https://github.com/nette/neon
http://ne-on.org/

I suggest that wireshell 0.5.1 have the autoloading of core commands. Then the next version we could play with adding custom commands. As I think version 1.0 must have custom commands enabled.
:smile:

Module as bridge between PW and WS sounds good, worth a try!
As autoloading of core files does not contain any advantage for normal users (it's just an internal milestone) I would prefer to release @justonestep 's great updates in #30 as 0.5.1 and keep the whole autoloading issue with 1.0.0 - and maybe it's possible to have proper test coverage. Right now, releasing half the autoloading (the boring part :D) would be hasty.

Just thinking out loud here... That "bridge file", telling wireshell where to find module-provided commands and how to autoload them - can't this be the ProcessWire 3's own composer.json? Or is that idea too narrow minded because it would require PW-module installation exclusively via composer to work?
Also, thoughts on idea: Making wireshell 1.0.0 PW 3-only, embracing its composer-goodness?

Additional (loud) thought: If glueing WS1 to PW3, maybe let's change wireshell in two projects:

wireshell bootstrapper: Globally installed, dealing with the heavy lifting (downloading, installing, grunt work stuff)
wireshell: Installed locally in per-PW3-installation-composer.json. No "multiple classmaps" hassle. If wireshell is installed in this PW installation, and its modules "emitt" Commands, they will be available in $ wireshell.

Why am I proposing this? ;) Even with @clsource idea of an intermediary file (see above) I heavily fail to find a solution to load "local"/"installation" modules.

I think its a good idea in making 2 versions of wireshell
one for PW 2.x  and other por PW 3.x
the current version will work for 2.x but will not have all the 3.x goodies like custom commands via modules and that stuff.
So I propose
keep wireshell as is for 2.x
and work a new wireshell for 3.x using all the new awesome tools that PW brings on :)


Emoji prevents Viber messages

I followed the tutorial https://claudiajs.com/tutorials/viber-chatbot.html and it's working well. However, when the bot receives a string containing an emoji, such as 😀 , the reply never reaches Viber. I have checked that request.text (in bot.js) does contain the correct string, so it seems the reply gets lost inside the bot builder code itself. Also, I did verify that sending 😀 directly to the Viber API does result in a message.

Fixed in version 2.7.2
Thanks!


fix(olm): update CSV status properly

This sets status after creation.

Although this will fix the e2e, it may not be the best fix after all.
/hold

/retest

/test unit

/retest

/test e2e-aws-olm

/test unit

This fix was included in https://github.com/operator-framework/operator-lifecycle-manager/pull/603.


Echo Devices show up as Unavailable

IMPORTANT: Please search the issues, including closed issues, and the FAQ before opening a new issue. The template is mandatory; failure to use it will result in issue closure.
Describe the bug
I've installed this integration, and after everything went fine, and then a extra reboot, all the echo devices show up as Unavailable.
To Reproduce

Go to HACS
Click on Integrations
Add Alexa Media Player
Reboot
goto settings > devices and services
add integration > Alexa Media Player and follow the steps
Select at the end the Echo Devices
Reboot
goto settings > devices and services
Click Alexa Media Player
Click on Devices and select 1 device
It shows Unavailable

Expected behavior
Available devices
Screenshots

System details
Home Assistant 2023.7.2
Supervisor 2023.07.1
Operating System 10.3
Frontend 20230705.1 - latest

alexa_media > latest: 4.6.5
Amazon [2FA is enabled] Is Enabled

Logs
This error originated from a custom integration.
Logger: alexapy.alexalogin
Source: custom_components/alexa_media/init.py:327
Integration: Alexa Media Player (documentation, issues)
First occurred: 2:45:36 PM (2 occurrences)
Last logged: 3:03:29 PM
Domain amazon.com does not match reported account domain https://www.amazon.co.uk; functionality is not likely to work, please fix

Use the UK domain instead. I'm not sure how to make the error message clearer but happy to take suggestions.


Add support for execution of a raw command on the data store

Provide a simple mechanism for executing a raw command (SQL statement) that does not return a value

@rowanmiller is this a feature we would expect to have parody with ExecuteStoreSql from EF6? If so should we consider moving it into the 7.0.0 milestone?

Clearing milestone so that we can address in triage

We missed creating the async version of ExecuteSqlCommand. Reopening to track that.


Upgrade to Rust 1.78

We are currently on Rust 1.74, and now as of Rust 1.78, the u128 type is now FFI safe. Lets go ahead and upgrade.
Doing this upgrade will help us resolve https://github.com/ros2-rust/ros2_rust/issues/320 once and for all. As part of this upgrade, we should also remove the #![allow(improper_ctypes)] and #![allow(improper_ctypes_definitions)] lines from our rcl bindings as we no longer need to ignore these lints.

That rust version is supposed to be the minimum supported version of rust that rclrs would work with. However, our CI does not use this same version so there is a chance that its actually misleading now.
I think with this upgrade to at least Rust 1.78 we'd want to upgrade rclrs to 1.78 in the cargo.toml as well since we would depend on u128 FFI safe functions.

Something that we should probably think about is what ROS 2 / Ubuntu version we target and what Rust compiler is shipped with it.
The rustc shipped in Noble is 1.75, so having anything higher than that as a minimum supported version might put us at risk of not being able to build the packages on a stock Ubuntu distro that only relies on Debian packages and doesn't boostrap rustc from rustup.

@luca-della-vedova That's a good point. Since Noble is an LTS we should expect that the build farm will be targeting it for quite a while now, and any build farm integration that we hope to accomplish before 26.04 will probably be forced to rely on the version of Rust that shipped with Noble.
It seems the only motivation to go as high as 1.78 is this FFI safety for u128, but even with version 1.78, it's not guaranteed to be safe across all targets. Maybe it's worth putting some time into researching whether there's a more sound way to achieve FFI safety. Especially something that can work with version 1.75.

Yeah, I think tying our minimum Rust version to what is shipped with Noble is reasonable if it helps reduce friction to get into the build farm.

boostrap rustc from rustup.

FWIW, rustup is also shipped in 24.04. All hope is not lost for moving beyond 1.75. Perhaps as the project matures and we are integrated into the build farm we can look at how to unblock Rust upgrades. The hope is still to have a single version of rclrs target many different ROS distros.

It turns out the FFI issue is thornier than we originally realized.
The real origin of the problem is that rosidl_dynamic_typesupport introduces float128 support, even though float128 is not a primitive type that's normally supported by rosidl.
This becomes a problem because bindgen does not properly support long double (float128). These uses of long double in the C API are quietly converted into u128 by bindgen, which is immediately a big problem for us, regardless of the u128 alignment issue that triggers the warning that we've been suppressing.
Currently our dyn_msg module is extremely minimal and doesn't include much of anything to actually inspect messages. I considered whether we can just filter out float128 from all the bindings that we generate to sidestep the error, but this indispensable struct contains a member that references float128, so the warnings would persist even if we try to filter.
My recommendation would be this:

We rename this issue to something like "dyn_msg float128 support needs bindgen to fix long double"
We disregard the v1.78 concern because it doesn't address the real problem
We keep the improper_ctypes warning suppression, perhaps adding a comment placing the blame on the lack of long double support in bindgen
We don't worry about this problem until someone starts fleshing out the dyn_msg module to really do type inspection
We probably shouldn't support float128 at all until bindgen fixes long double because we shouldn't take accountability for the ABI issues that could arise

After doing even more research on long double, I've reached the conclusion that bindgen shouldn't support interpreting long doubles from a C API, now or ever, because the binary representation of a long double is ambiguous.
Moreover I believe ROS should not support transmitting long doubles for the same reason, and I've opened an issue ticket upstream recommended that they be removed from dynamic type support: https://github.com/ros2/rosidl_dynamic_typesupport/issues/11
If that goes through, the following step would be to update the ROS IDL design doc to explicitly exclude long double from the subset of IDL that ROS supports (it's already not present in the ordinary builtin primitive types).
If that all goes according to plan, we'll be able to just remove the improper_ctypes suppression in the future and forget that float128 was ever a concern.

@mxgrey thank you so much for doing all this research, it'd be great to constraint rosidl_dynamic_typesupport and so we could remove improper_ctypes. Would you like to wait for https://github.com/ros2/rosidl_dynamic_typesupport/issues/11 to be addressed before we update the version of Rust in our CI or would you rather update it now and then remove improper_ctypes in the future?

I think we should not increase the minimal version to 1.78 no matter what because it will leave us incompatible with the build farm which will be limited to 1.75 for the next two years or so.
In the PR I've increased it to 1.75 to reflect our need to maintain support for 1.75, but I don't mind reverting it to 1.74 and putting in a comment to remind us not to go past 1.75.


Cordova 6 + function name typo

Just readme changes:

Added new Cordova 6 plugin syntax info.
isVisible function is actually isHidden just a typo in the readme I guess ;-).

Thanks


each infinite loop

Do you test each() in https://github.com/muut/riotjs/blob/dev/lib/browser/tag/util.js#L6 of dev branch?
Its give me infinite loop with this test in node.js:
function each(els, fn) {
  for (var i = 0, len = (els || []).length, el; i < len; i++) {
    el = els[i]
    console.log(el) //@debug
    // return false -> remove current item during loop
    if (el != null && fn(el, i) === false) i--
  }
  return els
}

console.log( each(['a','b','c'], function(el){
  return el !== 'b';
}) );

i-- is the guilty, it is not removing the current element. You need els.slice too.
However, it is documented behavior?

I want to invite yes so

sorry, its splice:
    if (el != null && fn(el, i) === false) els.splice(i--, 1), len--

The each loop it's heavily tested on node and on any supported browser (https://github.com/muut/riotjs/blob/master/test/specs/node.js#L30-L39 and https://github.com/muut/riotjs/blob/master/test/specs/compiler-browser.js#L356-L399). Could show us a test case where it does not work please?

copy the code above and run it with node in the command line.
it is testing your implementation of each() with [a,b,c] and deleting 'b', I add console.log only.
You will see multiple 'b', the loop don't stop.

@GianlucaGuarini, I see the actual code and I think
  // return false -> remove current item during loop
  if (el != null && fn(el, i) === false) i--
}

is removing nothing, although if i == 0 the code does not crash.
If i == 0 the bug is hidden because the for exits at i < len (i.e. -1 < len), before entering the infinite loop, but if i > 0 ...
maybe I'm wrong, please correct me.

sorry, the comment "remove current item" confused me.
els[i] is removed by the callback, not each().
Anyway, --len avoid unnecessary loop.


[NEW GAME] Flappy Bird

i want to add new game flappy bird

Hi @RitiChandak ,I am assigning this task to you. Kindly complete your work within a week. Good luck!


Update "working with labeled data"

fixes #91
@dcherian still need to update plotting

still need to update plotting

We could just link to the existing basic plotting notebook too in the "tutorial syllabus". The sidebar organization need not be the best organization for a given tutorial...

We could just link to the existing basic plotting notebook too in the "tutorial syllabus". The sidebar organization need not be the best organization for a given tutorial...

agreed, don't need to assume or require people will go from top-to-bottom!


[openCypher compatibility] Fail to filter on tag in WHERE

nGQL:
MATCH (v) WHERE v:player RETURN v.name, v,age
MATCH (v) WHERE id(v)=="Tim Duncan" AND v:player RETURN v.name, v,age;

In openCypher it works:
MATCH (n)
WHERE n:Swedish
RETURN n.name, n.age

match (v) where id(v)=="Tim Duncan" and "player" in tags(v) return v,tags(v)


https://github.com/ShikiSuen/SourceHanSansUI no longer available?

Yes, No longer available. The Origin Han Sans UI is available on CodePlex at this moment. However, CodePlex is shutting down. I will find a time (probably months later) to migrate it back to GitHub.


Move formatter from Prettier to Biome and Speed up eslint

Moving Formatter to Biome which is much faster, also optimizing what we eslint on commit. Overall this leads to a MUCH faster commit:
https://github.com/Azure/LogicAppsUX/assets/13208452/4db11b52-3990-4570-a2fa-88f6ef4fa331
I think we could also adopt Biomes linter and import sorter but will save that for later since it would be big file writes. The formatter is almost 1:1 compatible with prettier output except for better tertiary handling.

I also realized we were compiling our loc files to the wrong location. So that's fixed too.

Hi, Biome maintainer here, thank you choosing Biome!
Out of curiosity, do you know how much time will you save using Biome? Either locally or in CI?

Hey @ematipico
Won't save any in CI yet since we're only using the formatter, it'll save us a few seconds on each commit though since we run it as a commit hook.
I'm pretty excited though about what I'm seeing from y'all in the linter space though. The only real hold back for me switching us to that is that we rely on a few eslint plugins. Most importantly the one for formatjs. But that would  come with signifigant time savings locally and in CI. I would also imagine other savings such as battery life on our laptops.


Implement accessibility for tizen platform

Transplant linux part of chromium accessibility.

Screen reader reads widget information by atk/atspi2 on tizne platform, and chromium accessibility support atk/atspi2
Screen reader only read highlighted widget information on tizen mobile/wearable, modify the platform node of chromium accessibility to support it.

Implement the accessibility for tizen platform

Problem 1) The engine is being included as part of the embedder binary.
 You may need to either exclude the code (related to the accessibility feature) from the wearable embedder build (by modifying tizen/BUILD.gn and using #ifndef WEARABLE_PROFILE) or send a request to add the symbols to the store's API allowlist.

@swift-kim , about "Problem 2) Non-public API usage detected", wearable support accessibility(screen reader), and if I exclude the code, screen reader will not read the widget information of flutter app, I think it's better to add the symbols to the store's API allowlist.

Please format the GN file (shell/platform/common/BUILD.gn) correctly so that the CI build can run.

I think it's better to add the symbols to the store's API allowlist.

By the way, do you know why the symbols used by the embedder itself (kFlutterSemanticsCustomActionIdBatchEnd, kFlutterSemanticsNodeIdBatchEnd) are externally exported? We should avoid adding these symbols to the allowlist as much as possible.

about kFlutterSemanticsCustomActionIdBatchEnd and kFlutterSemanticsNodeIdBatchEnd, flutter engine will get all semantics node and custom actions, the symbols are used to notice the end.
bool FlutterTizenEngine::RunEngine(const char* entrypoint) {
  ...
  args.update_semantics_node_callback = OnUpdateSemanticsNode;
  args.update_semantics_custom_action_callback = OnUpdateSemanticsCustomActions;

about kFlutterSemanticsCustomActionIdBatchEnd and kFlutterSemanticsNodeIdBatchEnd

Anyway you need to find a way to prevent these symbols from being exported.

And I have no list of atk_* symbols, is there any way to show such list?

You may take a look at the src/build/linux/debian_sid_amd64-sysroot/debian/libatk1.0-0/DEBIAN/symbols file in your buildroot or https://gnome.pages.gitlab.gnome.org/atk/api-index-full.html. According to https://github.com/flutter-tizen/tizen_tools/runs/5418572124?check_suite_focus=true, you are using the libatk version 2.30.0.

@wanchao-xu Where did you copy the Chromium Linux accessibility code from? I need to be able to reproduce what you've done in order to upgrade the engine and accessibility code in the future. I need very detailed information on each file (e.g. why ax_platform_node_base.cc has been modified) but not just a link to the repo.

I copied the chromium linux accessibility from https://chromium.googlesource.com/chromium/src/+/4579d5538f06c5ef615a15bc67ebb9ac0523a973. Please refer to src/flutter/third_party/accessibility/README.md/.
The original chromium accessibility has many dependencies, I should modify some code to reduce the dependencies after transplanted. Google also modify the chromium accessibility to support mac and windows, not just a link to the repo.

To use the flutter tizen accessibility, the screen reader should apply the patch https://review.tizen.org/gerrit/#/c/platform/core/accessibility/screen-reader/+/270107/.

I think it's better to add the symbols to the store's API allowlist.

@wanchao-xu I discussed with Mr. Kwon today and decided not to enable accessibility support for wearable devices (mainly due to MX division's recent security issue).
You can apply this patch to disable the feature from the wearable embedder: https://github.com/swift-kim/engine/commit/76c43c8e8edd24a3162bafde7e2ad449fe9e5056. (Please cherry-pick the commit but do not manually modify the code to avoid human errors.)
Please make a suggestion if you have a better idea.

@swift-kim , Can I merge this request into branch now?


commit -> rev

The right key to use to pin a Cargo git dependency is rev, not commit; this was causing mio to depend on the latest master of "https://github.com/carllerche/bytes". Unfortunately Cargo doesn't seem to warn about the unused key in this case!

Thanks for pointing this out. I ended up updating the commit at the same time: 77775a151d5fb9cedcb6b298f06198aec2c8e62a


hipchat room_id field to string

https://github.com/prometheus/alertmanager/issues/133
hipchat api accepts room names or room id's in room_id field. this changes that.
not sure if you wanted me to run make config or if that should be done in a seperate commit

Thanks. We are currently rewriting the alertmanager in the dev branch. So we will most likely not release another version of the current one.
It might more sense to look into integrating this in the new branch.
Unless you want to run an alertmanager build from master. If so, we can reconsider.

it's fine for now. looking forward to the proposed changes in alertmanager


[SPARK-13842][PYSPARK] pyspark.sql.types.StructType accessor enhancements

What changes were proposed in this pull request?
Expand the possible ways to interact with the contents of a pyspark.sql.types.StructType instance.

Iterating a StructType will iterate its fields

[field.name for field in my_structtype]

Indexing with a string will return a field by name

my_structtype['my_field_name']

Indexing with an integer will return a field by position

my_structtype[0]

Indexing with a slice will return a new StructType with just the chosen fields:

my_structtype[1:3]

The length is the number of fields (should also provide "truthiness" for free)

len(my_structtype) == 2

How was this patch tested?
Extended the unit test coverage in the accompanying tests.py.

Can one of the admins verify this patch?

Discussed most of these changes ahead of time with @holdenk and @davies in the associated JIRA.  The last commit might be considered extraneous, but I thought it was related enough and a good idea so I went ahead and offered it up.  Easy enough to remove if people would prefer.
Ran just the pyspark.sql.types.StructType tests locally on a Python 3.5 setup.  Tried to be mindful of coding for python 2.7 compatibility (although I already miss type hints...).
Should be ready to review/discuss.
Thanks!

Can you update the description to include the ways that are being expanded?

I updated the pull request description, but I also realize your comment could have meant the user documentation.  I'll spend a moment to see if I can find the appropriate location for that.

It appears the user documentation is nicely scraped from the docstrings, so I went ahead and expanded the docstring slightly (and added a couple doctests).
Let me know if you intended something different.

I updated the pull request description to reflect the fix for using the slice syntax.  It is my belief that this should offer a solid balance of functionality and the principal of least astonishment.  I'm still happy to revise this further (and even trim down the proposed changes).  Just let me know.

cc @davies for review

@skparkes These accessor look good, but have some concern about the performance of serialization, please don't remove the without a good reason.

Alright, I had all the @property work rolled into a single commit.  I've reverted it so only the accessor work should be left.  Let me know if you see anything else you think should be changed.

LGTM

Test build #2831 has started for PR 12251 at commit 387cdfe.

Test build #2831 has finished for PR 12251 at commit 387cdfe.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

I apologize, I did not realize you were still targeting python 2.6 compatibility.  You guys really are gluttons for punishment.  I'll get a commit up today that should provide 2.6 compatibility.

@skparkes We had decided to drop Python 2.6 support, so we should run the tests with Python 2.7, will send a PR to fix that.

After reading the discussion again, it seems that we still need some work to drop Python 2.6. So go ahead to fix this for 2.6 please.

I believe this pull request should now be compatible with python 2.6.  I did stand up a python 2.6 environment to run the pertinent tests locally and they now pass.

The final code looks a little silly without a dictionary comprehension now that I reflect on it.  Let me swap that over to just direct returning from the iteration.

Okay, I made the switch over to the boring linear search method when accessing by field name.  I'm comfortable with the state of this pull request and believe it should pass tests on python 2.6 now.  Thanks.

Test build #2838 has started for PR 12251 at commit fc7898b.

Test build #2838 has finished for PR 12251 at commit fc7898b.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merging this into master, thanks!

Thank you guys for working through this.


PHP version

Hi,
This repo is not compatible at all with php7.4 right ?
Thanks

No, I'm sorry
PHP7.4 will go in EOL on 2022-11-28, so it would be useless to extend Telegraph compatibility to it
https://www.php.net/supported-versions.php


fix: update nonce in refreshPermissions when refresh is 438

Relates: #102
cc @enobufs

Build failed because of The command "bash .github/lint-commit-message.sh" exited with 1. All worthwhile tests pass, however.

@AeroNotix thanks for grabbing this!
CI should be green if

Add yourself to the README
Keep your subject to 50 chars fix: handle stale nonce in refreshPermissions  you can fill out the body more, could be helpful for others in the future.

@enobufs yes this does fix the issue for me.
Here's how I tested:

Two applications, one with and one without the code in the PR.
I brokered a connection between the two peers and waited 12 minutes.

12 minutes because by default (per RFC) the nonce value is valid for 10 minutes, we then have a timer on 120 seconds which calls CreatePermissions. To me I believe this makes the timing of the 438 line up to when the server has invalidated the nonce value.

Once the 12 minutes was up, I ensured to check logs. In the peer without the change, the CreatePermissions 438 error happened regularly in the logs.
Once the 12 minutes was up, in the peer with the changes the logs were free from the CreatePermissions 438 error.

I believe, for my particular use-case this PR fixes the issue but reading through the code more and more and starting to understand the RFC for how the Nonce should/could be used I believe a more general way to update the nonce could be implemented.

Codecov Report

Merging #103 into master will decrease coverage by 0.52%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master     #103      +/-   ##
==========================================
- Coverage   68.46%   67.94%   -0.53%
==========================================
  Files          31       31
  Lines        1817     1831      +14
==========================================
  Hits         1244     1244
- Misses        440      454      +14
  Partials      133      133

Impacted Files
Coverage Δ

internal/client/conn.go
52.9% <0%> (-2.51%)
:arrow_down:

Continue to review full report at Codecov.

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

(I really don't like this commit-message checker...)
git rebase master -i should help you modifying the commit message...
* Separate subject from body with a blank line
* Limit the subject line to 50 characters
* Capitalize the subject line
* Do not end the subject line with a period
* Wrap the body at 72 characters

@enobufs now the linter is happy now

@AeroNotix Great work! Thank you!


Add condition checks to install target

Add checks to ensure that the deployments bundled with the default
rukpak installations are Available before returning from install. This
prevents users accidentally creating rukpak resources before the
controllers are initialized.
This does hardcode the namespace/name of the deployments, but since we don't currently provide a way to configure those it seems like an acceptable compromise.

Should we edit the release notes to reflect these changes as well? Mainly so users can follow the same steps when officially installing.

I'm not sure about editing the existing release notes but maybe we can do so moving forward? cc @timflannagan

Let's just edit the v0.3.0 release notes? Can we double check that the additional wait commands actually work on a cluster before editing that release?

Let's just edit the v0.3.0 release notes? Can we double check that the additional wait commands actually work on a cluster before editing that release?

Sure, I can confirm, and if they work add them in.

SGTM - thanks!

Looks good. I did notice that there is a discrepancy in the name of the core webhook deployment:

in the v0.3 release it's called core-webhook
on master it's called rukpak-core-webhook

I believe this is a result of the recent kustomize work (#235 specifically) and if it's intentional and we intend on shipping it with that new name in v0.4 we will have to remember to modify that check in the instructions to refer to the new deployment name.


Extract templating and compressing

We'd been doing text/json/userdata templating in a specific package(=config).
While doing the same templating in the implementation of the node pools feature, it turned out that it is time to reveal what is the common sense of "templating" in kube-aws and what can be reused.
I've made each of the text, json and userdata templating resides in their own packages, and placed them under the umbrella package filereader because the templating happens while reading files e.g. user-data/cloud-config-* and stack-template.json templates initially generated via kube-aws render but can be modified by users.

Current coverage is 56.41% (diff: 33.33%)

Merging #101 into master will increase coverage by 1.03%

@@             master       #101   diff @@
==========================================
  Files             3          3
  Lines          1042        998    -44
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits            577        563    -14
+ Misses          385        362    -23
+ Partials         80         73     -7

Powered by Codecov. Last update b59b684...b4bcb32


INTERNAL ERROR: cannot create temporary directory!

I am trying to use GreenLuma to bypass the steam family share limit but I am on macOS while using CrossOver (a program that runs most windows programs on a Mac), when I try to run the exe file the error message below comes up and nothing else happens.

INTERNAL ERROR: cannot create temporary directory!

Please let me know if you need any more info.

I have zero idea if the manager or GreenLuma itself will work on macOS via wine, but the latest release has been rebuilt with a newer version of PyInstaller that should fix this issue, redownload.


New Release any time soon?

Hi @jpic it seems DAL has some good new functionality since October 15, 2020, and it seems the documentation has been updated as well. Is there anything blocking a new PyPi release for these changes? Thanks!

There were some blockers indeed but I think they have been fixed in upstream releases, will check and release this weekend.

Superb, thanks!


feat: multiinput with input/multicombobox

Changes

replace multiInput with Input
outsource filter in multiComboBox next to sort Select
various performance improvements on startup
in AllPackages.view.xml only change in first FlexBox, rest in formatting

https://github.com/ui5-community/bestofui5-website/blob/f61d6b524fba672bc8fa5ba512456b8b20ff92d4/src/view/AllPackages.view.xml#L12-L54

Screenshot

current error:

here:
https://github.com/ui5-community/bestofui5-website/pull/247/files#diff-009457ff331a1df27a38d8bbd6d062c2591322cd726314ebe11cbda5f68b9ed8R71-R81
@petermuessig can you might help here?
using the ViewSettingsDialog from the OpenUI5 Web Components
It does not work in a fragment

Hey @wridgeu ,
would be great to have your feedback on this.
Anytime when it works best for you.
Cheers

I feel like the icons are a bit too large which make them feel out of place. For the visuals on the two filter drop downs I made some changes locally regarding the sizing, color, flexbox basesize on phone and some margin changes

Perfect, wanted to achive that but i was tryin to get some results :)
Can you commit that please

Perfect, wanted to achive that but i was tryin to get some results :) Can you commit that please

Done :)

Looking good, thanks for your feedback :)


Move and Size Tails of a multi-tail arrow

As a User, I want to move and resize the tails of a multi-tail arrow so that I can accurately represent the reactants in my synthesis tree.
Acceptance Criteria:

When the user is hovering on the left corner of one of the tails, clicking and dragging to the left or right changes the widths of all tails.
1.1. During and after moving, the whole arrow should be highlighted/selected.
1.2. Dragging to the left is not limited.
1.3. Dragging to the right is limited to [minimum tail length>=radius of the corner curve]

When the user is hovering over the center of a tail (not the left corner), clicking and dragging up and down changes the position of the tail, and (if applicable) changes the length of the spine and the corner curvature.
2.1. During and after moving, the whole arrow should be highlighted.
2.2. Behaviour for the upper tail is covered bellow.
2.2.1. The upper tail can be moved up with no limitation.
<IP_ADDRESS>. The spine is adjusted accordingly.
2.2.2. The upper tail can be moved down until one radius of the corner curve above the head or another tail
(whichever comes first).
(Image for better understanding)

<IP_ADDRESS>. The spine is adjusted accordingly.
<IP_ADDRESS>. Any dragging bellow this point results in no movement.
2.3. The behavior for the lower tail is identical to the behavior for the upper tail, just with reversed directions.
2.4. The middle tail(s) can be moved anywhere along the spine with a radius of the corner curve as the limitation on both sides.
2.4.1. If the user drags the tail closer than one radius of the corner curve to another tail, after releasing the cursor, the tail position is automatically adjusted to the closest position to where the user dragged the tail, that is at least one radius of the corner curve away form other tails.
(Image for better understanding)

Pointer must represent possible actions.

Selection and hover highlighting of the whole Multi-Tailed Arrow is out of scope for this task - it will be implemented here - https://github.com/epam/ketcher/issues/5057

During exploratory preview testing on the nightly environment (5107-move-size-head-tails) some issues are found, need to be fixed:

Can't remove middle tail;
Can move tail to any place on spine if selection tool is used;

Points above are fixed and verified on Nightly environment (5057-hover-selection):

Middle tail can be removed:

Tails can be moved when the selection tool is used:

When moving down the top tail, it stops 0.15 before head:

Issues for cases when there are no free spaces for moving tail related to rounding - fixed, no errors are in console;
Tail can be put to 0.35 before the bottom tail:

Console issue when image is added to Canvas - fixed, no error are in console;


 Already set ip and login in Bridge control just want to add devices and activities :)
Thanks

The helper tabs on the top row are available to help you with that.

All good, Turns out I just had to update to the latest version and it all appeared.


change config to attrs, write docstring for sub-config classes, use those in docs

Done in #39
(but not using docstring in docs yet)


GUI editor-panel breaks at width 960px

The editor-top-panel breaks at 960px when a datasource has been added. This can easily be reproducued in Chrome devtool at freeboard demo. See screenshoots below.
This issue makes freeboard unusable on screens smaller than 960 (like the official 7" raspberry pi touchscreen).

I have the same problem

Guys,
These are the changes in CSS file to make it work for width upto 960px.
Update following css code in Freeboard.css or Freeboard.min.css (whichever you are using)
@media screen and (max-width: 960px)
#board-tools {
width: 50%;
}
#datasources {
width: 50%;
/* float: none; */
clear: both;
}

(960 x 226) px screen on chrome


Update README typo

fix some typo:

date_tpch_10 may be data_tpch_10
Could must be Cloud

Thanks for your efforts.


[Feature Request] Loosen the clampings for w[9]

Is your feature request related to a problem? Please describe.
I checked my parameters again and noticed that w[9] is 0.1 for some easy decks.
Describe the solution you'd like
I suggest changing the clamping to w[9] = w[9].clamp(0.025, 0.8)

According to https://supermemo.guru/wiki/Stabilization_decay,  w[9] is usually in the range of [0.2, 0.8]. I have loosened it to [0.1, 0.8].

Supermemo formulas aren't exactly the same as ours.

At least for stabilization decay, FSRS and SM are the same. And for easy cards, I'm afraid it's due to the underestimation of initial stability.

I just checked parameters of another user, he also has the same issue with w[9].
[0.1358, 0.5044, 18.4034, 18.4034, 4.8368, 1.1219, 0.8531, 0.0, 1.3932, 0.1, 0.8975, 2.0978, 0.1428, 0.3228, 1.3624, 0.2382, 2.7056]

My main worry is if w[9] is too small, the long-term interval will be very large, which could scare new users.


Unable to run the ansible command

I have created a single EC2 instance that meets the requirements stated.
I SSHed into the instance and started running the install commands.
This command fails:
ansible-playbook -e "ansible_ssh_user=ubuntu" -k -K -i "<IP_ADDRESS>," ansible/k8s-master.yaml
I am using ubuntu which has no password.
I am running this on the instance itself so why does it need to SSH.
From the documentation, I had assumed all the commands listed were to be directly on the instance, do I have that wrong?
Do I need to create a specific users/pass combination on the target server and then run this command from a separate server?
Please let me know.

Could you please provide output?

ubuntu@ip-10-70-2-60:~/optscale/optscale-deploy$ ansible-playbook -e "ansible_ssh_user=ubuntu" -K -i "<IP_ADDRESS>," ansible/k8s-master.yaml
BECOME password:

PLAY [all] *************************************************************************************************************

TASK [Gathering Facts] *************************************************************************************************
fatal: [<IP_ADDRESS>]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh<EMAIL_ADDRESS>Permission denied (publickey).", "unreachable": true}

PLAY RECAP *************************************************************************************************************
<IP_ADDRESS>                 : ok=0    changed=0    unreachable=1    failed=0    skipped=0    rescued=0    ignored=0

It should be noted that in AWS EC2 ubuntu user does not have a password, so I left that blank.  I am thinking this is the problem.

I went back and created a user named optscale, and created an ssh key for it.
Then I ran the entire install as that user.
The installation completed after that.
So if anyone is trying to run this on an EC2 instance you need to create a user.  My example:
sudo adduser optscale
pw: yourpassword
sudo usermod -aG sudo optscale

Create SSH Key
ssh-keygen -t rsa
cat ~/.ssh/id_rsa.pub
nano ~/.ssh/authorized_keys

Copy the contents of id_rsa.pub
chmod 600 ~/.ssh/authorized_keys

Change to that user
su optscale

Then, the host fingerprint needs to be added to the known hosts file.  Easiest way to do this is to ssh to itself:
ssh -i ~/.ssh/id_rsa optscale@IPADDRESS
The authenticity of host 'IPADDRESS (IPADDRESS)' can't be established.
ECDSA key fingerprint is SHA256:9EOmIzF1GisILso03ZVCgw+ggY42FiSFnzy+EFjPrGs.
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added 'IPADDRESS' (ECDSA) to the list of known hosts.

Then run the commands as the instructions say.

I went through the same exercise as you did, found that the instructions weren't clear and finally got it working. I should have looked at the Open issues before spending half a day on debugging the issue of why the deployment wasn't going through. Perhaps a PR to update the deployment instructions will help other interested users. I will create one.

Thanks @bharath144 !


Build for osx-arm64

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Good luck ok this one. I doubt I'll be of much help here. If you'd be willing to be a maintainer here that'd be great.

Already expected that I should do that :D

@beckermr This is 💚


RN FbSdk setAdvertiserTrackingEnabled()  is not working, Unhandled promise rejection TypeError  is returned  on IOS Simulator

🐛 Bug Report

setAdvertiserTrackingEnabled()  is not working, Unhandled promise rejection TypeError  is returned
To Reproduce

install react-native-fbsdk-next  via  "npm install react-native-fbsdk-next"
change ios realated files according to documentation: info.plist, appDelegate.m
cd ios
pod install
cd ..
run "react-native run-ios"
while running the app on simulator (iphone12), i get the error
Unhandled promise rejection TypeError,

Expected Behavior

Code Example

this is my code
import { useEffect, useState } from "react"
import { getTrackingStatus, requestTrackingPermission } from "react-native-tracking-transparency"
import { setAdvertiserTrackingEnabled } from "react-native-fbsdk-next"
const useGetTrackingStatus = () => {
const [trackingStatus, setTrackingStatus] = useState(false)
const setAdvertiserStatus = (status: boolean) => {

    setAdvertiserTrackingEnabled(status)
    .then((result) => setTrackingStatus(status))
    .catch((err) => setTrackingStatus(false));
}

}
Environment

IOS
running on iPhone12 simulator
react-native version is 0.64.1
react-native-fbsdk-next  version is 6.14.15
if any other details is needed please request

Hi there! Not enough information to reproduce - what version of this module, for example? Big difference between v6 and v7 for example
https://stackoverflow.com/help/how-to-ask

hi @mikehardy
thanks for your reply
i updated the bug description
thanks for helping

the issue was resolved
i am not sure if i am doing something not correct, or it is a real bug
but when i changed the code to
import { useEffect, useState } from "react"
import { getTrackingStatus, requestTrackingPermission } from "react-native-tracking-transparency"
import {Platform, NativeModules} from 'react-native';
const Settings = NativeModules.FBSettings;
const useGetTrackingStatus = () => {
const [trackingStatus, setTrackingStatus] = useState(false)
const setAdvertiserStatus = (status: boolean) => {
// note: TODO: need to add a condition of ios platform here
**Settings.setAdvertiserTrackingEnabled(true)**
.then((result) => setTrackingStatus(true))
.catch((err) => setTrackingStatus(false));

}
that is getting the FBSettings and call its method it worked
but i don't understand why
is there something wrong with my import ? (in the original code i provided?)

@salihboshnak in your bug report you're importing the method directly. I think you should import the Settings first to use the setAdvertiserTrackingEnabled . Like this:
import { Settings } from 'react-native-fbsdk-next'

Settings.setAdvertiserTrackingEnabled(status)

@andrewdazs  thanks for passing by
but i think you are wrong
since the function  setAdvertiserTrackingEnabled(status) implementation
is calling Settings.setAdvertiserTrackingEnabled(status)  under IOS platform only
this is a wrapper function in order to make the API  not related to a platform
and to make easier for developers


Implement skeleton codes for Push APIs (#496)

This is an initial implementation to provide IndexedDB wrapper APIs to client app.
The APIs always return false right now and we can implement them later.

@yeonsuyam Also, you should update your patch's title.
You implemented IndexDB API but your patch's title is about Push API.


[release/1.5] cri: PodSandboxStatus should tolerate missing task

Backport of #7535
Resolved conflicts in cherry pick:

sbserver - deleted file
fmt.Errorf vs errors.Wrap

/test pull-containerd-node-e2e


[notarize] preserve meta-data and symlinks

Checklist

[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I see several green ci/circleci builds in the "All checks have passed" section of my PR (connect CircleCI to GitHub if not)
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.

Motivation and Context

When using notarize the implementation of ditto causes the archived app to be different in comparison to the original one , the current way it's being done doesn't preserve meta data or symlinks.
This lead to the app being damaged after running notarize.
Resolves #20828
Description

Adding an extra parameter to the ditto command --sequesterRsrc fixes this issue .
https://ss64.com/osx/ditto.html

To test it i compared the output app with the original one previously it showed these changes
diff -q -r original.app produced.app

Only in produced.app/Contents/Frameworks/Factory_32A9B87E1196645F_PackageProduct.framework: ._Factory_32A9B87E1196645F_PackageProduct
Only in produced.app/Contents/Frameworks/Factory_32A9B87E1196645F_PackageProduct.framework: ._Resources
Only in produced.app/Contents/Frameworks/Factory_32A9B87E1196645F_PackageProduct.framework/Versions: ._Current
Only in produced.app/Contents/Frameworks/Paddle.framework: ._Paddle

after the fix it showed none.
Testing Steps

diff -q -r produced.app original.app
If needed i could provide a copy of the app bundle with the issue.

Could you explain a bit what this solves? Thanks

Could you explain a bit what this solves? Thanks

Description updated with all the details.


Upgrade Lucene to 5.5.0

On 2.2.x series we can at least upgrade to 5.5.x because Lucene 6.x requires Java8

core done, spatial to do

Cool! Though, wouldn't this advance be reason to have at least a minor version release to 2.3.0?
Scott

@robfrank - Do I understand correctly that Lucene 6.2.0 is now going to be in 2.2.11? Are there any new features that can be taken advantage of directly? This is a pretty cool update from what I understand of Lucene's newer versions.
Scott

no, I'm sorry. We are migrating to 6.2.0 on 3.0.x (develop brach). Even if it could be safe to migrare lucene, such a big version change on a maintenance branch could not be done.

Ahh! :+1: Ok. That makes perfect sense. :smile:
Thanks for the explanation.
Scott


[REST] Rest test changes

The xyz and org are changing and the json body too. the only common for now is the REST status RC..

Code under review

Done as part of the https://github.com/openbmc/openbmc-test-automation/issues/392 changes
closing


Update containerd to 1.5

Current situation
Containerd 1.5 was released.
As the new release has quite a lot of changes, it might not be trivial for Flatcar to update containerd to 1.5.
One of the issues is Go modules, which is now turned on by default.
app-emulation/containerd ebuilds in coreos-overlay need some changes.
Config formats have also changed, not sure yet if the issue also affects Flatcar.
Once the containerd 1.5 was included in Flatcar stable, we should also update containerd version in image-builder.

Fixed build issues with containerd 1.5, and the PR https://github.com/kinvolk/coreos-overlay/pull/1006 was merged.
containerd 1.5.2 will be included in the next major Alpha release.


[feature]Cross-referencing this feature needs to be improved

jadx-1.0.0-b1163-a48ce296
My English is not good, please don't mind the grammar of the words I am talking about next.
Java has two characteristics of extends and implements.
Subclasses can override methods of the parent class, and subclasses can override methods of the parent class interface.
But jadx cross-references can't find them.
For example, a subclass overrides the method of a parent class, which is an interface class. But using jadx cross-references on the methods of the parent class, you can't find the method that the subclass overrides!
Similarly, using the jaxx cross-reference on the method that the subclass overrides, you can't find the method corresponding to the parent class.

Cross-referencing this feature needs to be improved.
I look forward to your realization of this feature.
Thank you for reading this suggestion.

I forgot to say before, does the JAVA field have the same problem? I don't have a good sample to verify if this problem exists.


wiegand app cannot compile

Hi @jamisonderek
No matter what I do, I cannot get the wiegand app to compile.
I was getting a number of errors relating to furi declerations, and after potentially solving those I am now getting errors regarding members and years, months, etc.
I am well out of my depth here and would really appreciate some assistance in getting this working!
I want to test some wiegand readers with my flipper, and have plans to design a wiegand interface PCB for them if i can get your app working.

I found a compiled version elsewhere that works.
Also, can the app turn on 5v by default ?

@CountParadox, could you possibly share the link to the compiled version?

I'll take a look tomorrow. Which firmware are you running?

Fixed https://github.com/jamisonderek/flipper-zero-tutorials/commit/e6debaf3884a339044ca84d703c4702a4c671157


Realsense D435 + SLAM

I am currently using this:
https://github.com/intel-ros/realsense/wiki/SLAM-with-D435i
along with my D435i camera. I have got it working fine and outputting reasonable poses. My question pertains to the co-ordinate systems:
I know that the algorithm localizes relative to the first captured frame, but physically speaking, does that correspond to the center of the RGB camera? Or some other point on the D435 camera?
Thanks!

Look at your TF and the middle (intersection of 3 axes, XYZ) is the correspondence point

[Please Ignore - RealSense system comment]


Improve client workflow for connect and disconnects

Is your feature request related to a problem? Please describe.
Improve the overwall connect/disconnect workflow of a client.
Although we do have methods for switching between all the client states. I was unable to put the client on the ready state after a disconnect of an LiveNotFound exceptions.
Describe the solution you'd like
I was thinking an in a "autoconnect" argument on both the "connect"  and "start" methods.  Goal is to keep the connection/disconnection workflow in charge of an inner deamon of the client. Client it self must retry in a consistent retry interval. Also, interval could be incremented with a function argument.
Well, if that is not an option. What do you think of at least an example on how to achieve that.
Describe alternatives you've considered
So far what I've I'm trying is, i've encapsulated the client, and in my connect method I'm retrying when the attempt have failed.

class Tiktok:

    def __init__(self, user):
        self.user = user
        self.loop = asyncio.new_event_loop()
        self.loop.set_exception_handler(self.exception_handler)
        self.client = TikTokLiveClient(unique_id=user, loop=self.loop)

    async def connect(self):
        while True:
            if self.client.connected:
                print('connected:', self.user)
                await asyncio.sleep(5)
            if self.client.connecting:
                print('connecting:', self.user)
                await asyncio.sleep(1)
            elif not self.client.connected and not self.client.connecting:
                print('connect: ', self.user)
                try:
                    await self.client.start()
                except LiveNotFound:
                    self.client.stop()
                    await asyncio.sleep(60)

Then, I just try to connect with all clients with:
async def start(loop):
    for user, client in clients.items():
        asyncio.run_coroutine_threadsafe(client.connect(), loop)
    while True:
        await asyncio.sleep(10)

if __name__ == '__main__':
    loop = asyncio.new_event_loop()
    loop.run_until_complete(start(loop))

Good day, what could be the reason for this error? I've been struggling with this issue and I want to run it please help :(


Added new tab with effort and catch data

Hi Denisse,
I finished adding a tab for the fishing effort and catch data. Right now it just pulls the data directly in from gem, but when we add the data to thredds we can pull it from there if we want. Take a look and let me know what you think. I'm not super attached to anything there so if you have suggestions/wanna make changes go right ahead!

Hi Gage,
The app uses the native R pipe: |> instead of the magrittr pipe: %>%. This will need to be updated before I can merge it.
I can see some lines of code are commented out and I cannot tell if these are meant to be kept or not. Please remove any lines of code that are not needed.
It would be great if you follow the same formatting as the rest of the code, that is:

Keep lines to a maximum of 80 characters to reduce horizontal scrolling (you can activate the "Show margin" option under Options > Code > Display
Use curly brackets {} in if statements
Avoid hard coding if possible. For example, in line 1132, you use new_choices[1]. Are you able to avoid this at all?

The idea behind this is that the code is easy to read, which we hope in turn will incentivise people to contribute towards the development of the app.
Also, it appears you are using an outdated version of the code that does not include the "download" button in the comparison tab. Could you please use the most up to date version of the app?

In regards to the comments about making the app faster. You can do this by avoiding processing your data every time you load it. For example, you remove any rows in the effort data that have no information under the region column and then you rename the FGroup column.
Instead of doing this every time the app is started, it would be better to simply save the data as you need it to minimise or avoid any processing in the app itself.

Hey Denisse,
Just updating you; I'm working on making those changes and will push the updated branch (using the most recent version of the app) later today!

Hi @lidefi87,
I've just pushed all of the changes I needed to make. Everything runs smoothly and quickly now. Please let me know if there's anything I missed.
Best,
Gage

Thanks, Gage. I may be a bit delayed in checking this PR, but I'll get back to you by the end of the week. Thanks for your help 😊

All merged now. Thanks again for your help

Thanks @lidefi87 !!


Add wait message to test connction screen

With Tor it can take a bit until the account is ready to use.
@secondl1ght what do I need to do for the dark mode here?

I can test this and update for dark mode, what is the user flow to get to this page? I don't think I have seen the test connection screen before.

just adding a connection. it is briefly seen in before the success screen.
but when connecting to Tor this takes a bit longer

I dont have write access so I wasn't able to suggest the changes in the actual code, but I left a review showing what needs to be updated. Thanks!

great, thanks! updated.


Add multi-user key store provider registration support

These changes add a public method to register providers into an instance cache at the command-level, allowing users to maintain their own set of providers in the same application.
The current column encryption key (CEK) cache is global so a new CEK cache and signature verification cache is added at the SqlColumnEncryptionAzureKeyVaultProvider level. Each SqlColumnEncryptionAzureKeyVaultProvider is linked to a single TokenCredential, which serves as the user identity.
public class SqlCommand
{
       // Added API: registers into command-level key store provider cache
       public void RegisterColumnEncryptionKeyStoreProvidersOnCommand(IDictionary<string, SqlColumnEncryptionKeyStoreProvider> customProviders);
}

Can you assess TTL by adding more tests?

I've tried adding the following test but it doesn't run reliably because the expired cache entry is sometimes not removed until access is attempted, and so GetCacheCount() returns 1 both times. Any better idea on how to test it?
public static void CekCacheEntryIsRemovedAfterTtlExpires()
        {
            SqlColumnEncryptionAzureKeyVaultProvider akvProvider = new SqlColumnEncryptionAzureKeyVaultProvider(new SqlClientCustomTokenCredential());
            akvProvider.ColumnEncryptionKeyCacheTtl = TimeSpan.FromSeconds(5);
            byte[] plaintextKey = { 1, 2, 3 };
            byte[] encryptedKey = akvProvider.EncryptColumnEncryptionKey(DataTestUtility.AKVUrl, "RSA_OAEP", plaintextKey);

            akvProvider.DecryptColumnEncryptionKey(DataTestUtility.AKVUrl, "RSA_OAEP", encryptedKey);
            Assert.Equal(1, GetCacheCount("_columnEncryptionKeyCache", akvProvider));

            Thread.Sleep(TimeSpan.FromSeconds(5));
            Assert.Equal(0, GetCacheCount("_columnEncryptionKeyCache", akvProvider));
        }


Create vera_defi.md

Initial grant application
Grant Application Checklist

[x] The application-template.md has been copied, renamed ( "project_name.md") and updated.
[x] A BTC or Ethereum (DAI) address for the payment of the milestones is provided inside the application.
[x] The software of the project will be released under the Apache license version 2.0 as specified in the terms and conditions.
[x] The total funding amount of the project is below USD $30k for initial grant applications and $100k for follow-up grants.
[x] The initial PR contains only one commit (squash if needed before submitting your PR).
[x] The grant will only be announced once we've successfully delivered the first milestone.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Repo was turned private by mistake. I also brought the nodes and app up. Sorry about that.
AssetManager is Ink smart contract, there is description about it on the READ.ME in the repo.
We are working on adding more documentation.
Thank you.

We are working on more technical specification for the milestone, including the UI and contracts. Will update application soon.
UI will be in react as you can see in the tech stack already included in the application.
In the application we included clickable wireframe. The actual design will be part of the grant, as we want to make sure it's top quality work. Design and UX are essential for the long term success of this project.
Thanks for the feedback!

Thanks. Feel free to ping me once you’ve updated the application.

David, please check we have added more details to our application. Application now includes

@denislam also needs to sign the CLA.

David, Thank you for the review.
Yes, NFT lending is part of this, sorry about the confusion. I have updated the table. There are details on the NFT itself in under the milestone details.
Would love to hear any feedback you have, negative before positive.
Thanks

David,
We have discussed and added the license to our code.
As for the UI, it will built with React mostly coded with TypeScript, and we will rely on Polkadot.js to sign transaction, that is already included in our wireframe.

Sorry about that. We have added missing attribution to all relative files.
We are eager to work with you, let me please if there is anything else we can do to make sure our project is accepted in the program.
If you think we need to add more technical details, or elaborate on the business further we are more than happy to do it.
Thanks.

Thanks for adding the additional attribution and details. To be honest, I’m personally at the moment not convinced by your application but I will share it already with the rest of the team. Also are you aware of the Element/Telegram chat group for all things NFT on Kusama and Polkadot. Also something you should be aware is that: A group of devs, PMs and designers, along with artists and NFT creators are working on a NFT strategy for Kusama network (already ongoing: https://kusama.polkassembly.io/post/303).

research and implement attributes and functionalities to link Token to real assets, such as hash or signature of scan of Art, and other proprietary techniques.

This is just adding a metadata to the token, nothing new here.

Add support for perpetual royalties to original creator

This is covered by ERC-2665, so I'm not sure what further research you need to do in this front (and adapting ink!'s erc721 to support this feature should be trivial).

We also don't provide support for the UX design phase as part of grants, as we believe this should form part of the team's investment and market research, and normally should be provided as part of the application. In your case, it's a benefit that you already provided wireframes, thanks for that.

With the above two points in mind, your list of core deliverables is halved. I think the idea you have might have some potential and I would be happy to support your project for a smaller amount. Let me know if this makes sense!

On top of what @mmagician mentioned, given that the aspect of linking real-world assets to NFTs isn't part of this application, it isn't a good selling point in the context of a grant. I would be keen to support a more generalised smart contract lending library, though.

Thanks for adding the additional attribution and details. To be honest, I’m personally at the moment not convinced by your application but I will share it already with the rest of the team. Also are you aware of the Element/Telegram chat group for all things NFT on Kusama and Polkadot. Also something you should be aware is that: A group of devs, PMs and designers, along with artists and NFT creators are working on a NFT strategy for Kusama network (already ongoing: https://kusama.polkassembly.io/post/303).

David, thanks for the great valuable feedback, this is exactly what we are looking for. We already  joined both these group and will start discussion the best fit for our solution in the ecosystem based on their feedback and need. Our primary goal is to bring our industry connections, and technical knowledge to the Polkadot ecosystem to  learn, contribute, and be part of the success of the wider ecosystem. We will keep you posted as our business evolve as we engage further with the community.

research and implement attributes and functionalities to link Token to real assets, such as hash or signature of scan of Art, and other proprietary techniques.

This is just adding a metadata to the token, nothing new here.

Add support for perpetual royalties to original creator

This is covered by ERC-2665, so I'm not sure what further research you need to do in this front (and adapting ink!'s erc721 to support this feature should be trivial).
We also don't provide support for the UX design phase as part of grants, as we believe this should form part of the team's investment and market research, and normally should be provided as part of the application. In your case, it's a benefit that you already provided wireframes, thanks for that.
With the above two points in mind, your list of core deliverables is halved. I think the idea you have might have some potential and I would be happy to support your project for a smaller amount. Let me know if this makes sense!

Marcin, we appreciate the valuable feedback.
For the attributes, our long term intention is to bring more industry standard to the on chain data to incorporate things like ISO 25178 to have better traceability of physical assets and their digital representation.
Yes, indeed ERC-2665 already provide strong foundation, however we are hoping to provide more comprehensive royalty structures. Complete understand if you think this doesn't add value to the ecosystem.
Thanks for the clarification on the UI/UX. Our team is heavily invested in this, and will cover that aspect of the expense.
Having said that, our primary objective is the engagement with the community to make sure what we are building has value for everyone. We highly appreciated your generous support and happy to take a smaller amount you suggest for this project.

On top of what @mmagician mentioned, given that the aspect of linking real-world assets to NFTs isn't part of this application, it isn't a good selling point in the context of a grant. I would be keen to support a more generalised smart contract lending library, though.

Sebastian, thank you for the valuable feedback!  we talk about physical assets to give context for our overall vision as recommended by the grant guideline, sorry if we took this too far in this application. At it's heart this is a lending smart contract. and will be available for use by other under open source license. We are open to put more effort to make our smarts in a well documented library to be used by other as well.
Let me please know if you have further suggestion to help us gain your support for our project.
Thank you.

@arbach We are generally happy to support a research phase, although in general I would see it as a separate grant. In this case, however, I'm not sure what the outcomes/deliverables of such a research phase would contribute, so without seeing a concrete proposal it's hard to judge.
Nevertheless, my personal suggestion would be to decouple NFT specifications from the rest. For this grant I suggest to focus on the AssetManager & the ExchangeManager, given that we've already got plenty of similar NFT grants. @semuelle @Noc2 do you think that would make sense?

the AssetManager & the ExchangeManager

@mmagician Isn't the ExchangeManager rather common? Agreed on the AssetManager, though.

@arbach

For this grant I suggest to focus on the AssetManager

If you're ok with it, you can go ahead and change the scope of the application to reflect that. You should be able to integrate with existing NFT implementations, rather than building another one anew.

If you're ok with it, you can go ahead and change the scope of the application to reflect that. You should be able to integrate with existing NFT implementations, rather than building another one anew.

@mmagician
I have update our application accordingly.

Thanks for your flexibility.
As I pointed out before:

With the above two points in mind, your list of core deliverables is halved.

I believe you still should adjust the price accordingly.

@mmagician   Sorry I missed that. fixed.

@mmagician  @Noc2  @alxs @semuelle , web3 team
We , the Vera team, are grateful for the trust you put in us, and we are thrilled for your approval for our project, and looking forward to complete this work and move forward with you!

Hello web3 team,
Wanted to keep you posted that our work on this was done a while back, we did not have time wrap up the delivery for it yet.
here is the beta app.  http://beta.vera.financial/
and recorded demo https://drive.google.com/file/d/16sUVt-wvYdWAUsfupGVtnzWDOvYAbio6/view
and here is the source code https://github.com/veraprotocol/ambrosia
Working on putting together all documents required for the delivery, and submitting as per instruction.
Sorry we are late on this, we had multiple good partnerships that we had to do tech work for that delay this specific project.
Looking forward to continuing the collaboration.

Thanks for the update, @arbach. Looking forward to your delivery.


fix(cloudflare-workers): do not buffer content

Author should do the followings, if applicable

[ ] Add tests
[x] Run tests
[x] yarn denoify to generate files for Deno

@cometkim
Thanks. Indeed, it should be a stream. Thanks.