update plone api versions/bootstrap process

use plone 5.1
do not use bootstrap.py but install zc.buildout via pip (see: bootstrap.sh)

Coverage remained the same at 58.145% when pulling 2388d581ae7a1a9e85d25d7402ea16a7d14029ee on thet-updapi into b2658adee49a1713cb359f0438231be8a37c4fae on master.

@thet thanks for the upgrade. Two remarks from my side. I'd keep the bootstrap-buildout.py for people who prefer that approach. I'd also prefer a Makefile over a bash-script, because you do not risk to end up with a bunch of bash-scripts in your root folder.


[Bug] : Noticed Scroll-Top Icon and Code Pilot Icon Overlapped each other when Dark Mode Theme Action Done

What happened?

Whenever the  Dark Mode Theme Action Done, the Code Pilot Icon and Scroll-Top Icon Overlapped Each Other. But, in Light Mode Theme, That's Issue Not Happens.

In Light Mode Theme:

In Dark Mode Theme:

How can we reproduce this bug?

Go To "https://codesetgo.netlify.app/"
Little Scroll and Observe Code Pilot Icon and Scroll-Top Icon in Light Mode Theme and Dark Mode Theme
See Error on these Two Icons are Overlapped Each Other in Dark Mode Theme

Desktop Information (Optional)
Browser: Google Chrome, OS: Microsoft Windows and Version: 115.0.0
Urgency (Optional)
Medium priority
Record

[X] I agree to follow this project's Code of Conduct
[X] I have checked the existing issues
[X] I'm a GSSoC'23 contributor
[X] I want to work on this issue

Hi @agamjotsingh18 . Please review on this Issue

Too easy issue, just bottom property needed to be changed


chore(lb): always show rank

If we want to show rank no matter the position on the board.

lets just archive this, based on the community votes.


Feature/travis

I'm sorry, wrong repository (♥ GitHub UI…).

@adamkudrna Hi, and aren't you interested to send the changes to the upstream? Would be great to join forces :-).

@OndraM in case you are interested in switching to flexbox, why not :-). However, we should start from scratch then as our fork now also contains older changes that are no longer valid and one would not want to see them in the project's history.

@adamkudrna Sorry, no plans for implementing flexbox. For the future we are rather watching over CSS Grid.

I understand, so are we.
I also hear one of your teams is using our fork of Emerald. We were really surprised when we found out because we forked Emerald only for our purposes and did not mean to distribute it to anyone to use it in production :-). We are not going to use that version (before our v2.0) any longer but we are open to clean up the Git history and contribute properly to your repo if it is interesting to you.

Well, they were actually surprised as well, because it was some unknown and unintentional relic of past Synergic development ;-). AFAIK they no longer use it nowadays.

OK, good for them :-).


Increase default size for PlantUML diagrams

See http://plantuml.com/faq

I will stop using issues for my personal feature requests because it makes the project look more broken than it is :sweat_smile:


[Collection] add CollectionInterface::chunk()

Signed-off-by: azjezz<EMAIL_ADDRESS>closes #210

Pull Request Test Coverage Report for Build 961520501

28 of 28 (100.0%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.0003%) to 99.968%

Totals

Change from base Build 935286366:
0.0003%

Covered Lines:
3091

Relevant Lines:
3092

💛  - Coveralls


Add support for lists

Many elements in a GUI will appear in the form of lists, such as tabs in a browser, bookmarks, messages in a chat client, icons in a launcher, etc.
cedar’s view system should have a way to map a Vec from the model into a list of GUI elements.

That would indeed help a lot.


Face profiling code

In your face profiling code, in the main.m, vertex_full, tri_full and vertexm_full are loaded from .mat file, The question is how I can generate these array by myself?

In your face profiling code, in the main.m, vertex_full, tri_full and vertexm_full are loaded from .mat file, The question is how I can generate these array by myself?

Have you figure out yet?

In your face profiling code, in the main.m, vertex_full, tri_full and vertexm_full are loaded from .mat file, The question is how I can generate these array by myself?

Have you figure out yet?

pls check my profiling code here, hope it helps you.


Nats ?

Is there any interest / need for supporting NATS Jetstream ?
I suspect that supporting both might be quite easy since Pranadb is only subscribing to topic changes and not doing any publications to Kafka / nats

Could you elaborate a bit on what you mean by supporting NATS Jetstream? Do you mean ingesting data from there into Prana?
Prana will be doing publishing to Kafka soon (sinks)

Yes I mean that we both Karla and NATS Jetstream can be supported.
There is an abstraction library in golang that already does this . I just need to search for it on GitHub.
I guess the other aspect of this is if the team members want this.  So basically extend source to also work with NATS. Yes, I think that would be nice to have

Hey @purplefox
Check out this: https://github.com/nats-io/nats-kafka/blob/main/docs/config.md
Its a Kafka / NATS bridge that works both ways. Nats --> Kafka and Kafka --> NATS.
It might be one one to achieve the Issue.. Or it might be over complicated. I am only playing with it for a day or two so far, and still undecided. So figured its worth raising here.

sorry i have not had time to work through this.
i want to but got too many things.
if you have any ideas you want to discuss around this feel free to  drag me in.

@purplefox https://github.com/nats-io/k8s/tree/main/helm/charts/nats-kafka
its clearly been used for real. This makes running it quite easy.


does this a display tool or generate visualize image tool?

I've run this on my server, it occurs this problem:
(Deep Visualization Toolbox:32051): Gtk-WARNING **: cannot open display:
So I have a question here does this a simple display visualization images tool or generate visualization images tool for DL? I havn't go into details in the code.

Hi @sunbaigui, the ./run_toolbox.py command is only used to load the GUI to display the visualizations, so it makes most sense to run it locally. The code for generating the visualization images for one's own network are still in the process of being posted (sorry for the slowness).
If you'd like to get started extracting the max images and max deconv images for your own network, you could consider running my existing scripts yourself, but admittedly without proper documentation, and with some parts hard-coded to my own setup. You'll probably have to hack a few pieces to suit your own setup. Here's everything you'll need:
https://gist.github.com/yosinski/285bc9ed2fd35cba2c76 find_max_acts.py
https://gist.github.com/yosinski/daecbd3a6db824295596 crop_max_patches.py
https://gist.github.com/yosinski/9051b60dc68c4cb0bad4 max_tracker.py
https://gist.github.com/yosinski/9958944c5bf08bd93ba2 loaders.py
https://gist.github.com/yosinski/8f7da9ce60c17d9e8d82 jby_misc.py
https://gist.github.com/yosinski/6c8167195b101c386ee5 caffe_misc.py
Step 1: run ./find_max_acts.py to go through a set of images and record which produce the maximal response for each channel/unit.
Step 3: point your settings.py to that new directory.
Note: these scripts will only generate the bottom two types of visualization (9 top / 9 deconv). To generate the 9 optimized images requires a bit more code, which will take me longer to extract. I hope to get to that soon.

:+1:  for a procedure do visualize "your own network"

I like this tool too, waiting for custom network visualization :+1:

is it possible to have a small example showing the generation of the deconv image of an input image with your modified branch of caffe?

@Trekky12

is it possible to have a small example showing the generation of the deconv image of an input image with your modified branch of caffe?

Sure, here's where the deconv is computed:
https://github.com/yosinski/deep-visualization-toolbox/blob/a74181698933498bf11096895dd971f47234da84/caffevis/app.py#L151-L162
And here's where it's plotted:
https://github.com/yosinski/deep-visualization-toolbox/blob/a74181698933498bf11096895dd971f47234da84/caffevis/app.py#L988-L1022

Do you know why the following code isn't working properly: https://gist.github.com/Trekky12/e99fdc52de0ec4fb77ee

I'm not sure; what error do you get?

@yosinski thank you for your answer. The error was a totally gray image instead some patterns in the image. In the meantime I found the problem.
The method caffe.io.load_image(..) doesn't rescale the image so the net needs to be initialized with a raw_scale of 255 instead of 1.0. With cv2.read(..) the raw_scale can be 1.0

@yosinski , what is the  'layer' argument that you mention in crop_max_patches.py?
parser.add_argument('layer',         type = str, help = 'Which layer to output')

@yosinski sir, can you plz guide for generating "regularized_plot" for those images as we generated the max images and the deconv for those images.

@bhack  @yosinski the above three steps to  visualize my own network  also have some problems:
running  python ./crop_max_patches.py ./output.pkl ./deploy.txt ./caffemodel ./img_val ./val.txt ./unit_jpg/vis/max_im conv2
i got en error  File "max_tracker.py", line 337, in output_max_patches     out_arr[:, out_ii_start:out_ii_end, out_jj_start:out_jj_end] = net.blobs['data'].data[0,:,data_ii_start:data_ii_end,data_jj_start:data_jj_end] ValueError: could not broadcast input array from shape (3,10,0) into shape (3,10,9)
do you know why?ths~

@visonpon did you solve this problem...I have exactly the same problem as you.

@visonpon@pawanhsu I also have the same problem. Did you solve it ?

Yeah. that is because the imagenet example in caffe has default resolution size 256. And it feed in the model with 207 cropped image. However in my case my image doesn't do any cropping before i feed in the model to train. those the padding will causing the overflow in matrix.

@pawanhsu Thanks for your reminder, i have solved it! In file of caffe_misc.py,  init(self) of class RegionComputer(object) used "Woefully hardcoded" just for caffenet. So, it is necessary to rewrite it according to the new network. @visonpon

@bhack, @mtamburrano, @Trekky12
I've made the tool substantially more generic: all the hardcoded parts where replaced with new settings parameters, most are deduced automatically by analyzing the network definition file
@visonpon, @pawanhsu, @qigreen
I've also fixed numerous bugs, some of them in the receptive field calculations which seems related to the mentioned error
Latest version is in https://github.com/arikpoz/deep-visualization-toolbox


Compress Gradle runtime jars

Context
There's no good reason I can think of why we should turn off compression for the runtime JARs. This change enables default compression which creates JARs with roughly half the size as before. It will also save some disk spaces for users of multiple Gradle versions in parallel or in an upgrade scenario.
Before change:
gradle-api JAR: 99.1MB
gradle-testkit JAR: 86KB
After change:
gradle-api JAR: 41MB
gradle-testkit JAR: 41KB
Branch build: https://builds.gradle.org/viewType.html?buildTypeId=Gradle_Check_Stage_BranchBuildAccept_Trigger&branch_Gradle_Check=bm%2Fcompress-runtime-jars&tab=buildTypeStatusDiv
Gradle Core Team Checklist

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation including proper use of @since and @Incubating annotations for all public APIs

@bmuschko the speed at which they are generated is more important than the size. If this makes generation noticeably slower we should reevaluate.

Regarding speed, it could improve using the same technique as in #2774. Maybe we should ship the 2 in the same version, we would have smaller size and faster.

I started another performance test agains the latest nightly. There are quite a few performance improvements on master at the moment which have not been rebased yet. I just want to see how this change performs in directly comparison to current master.
https://builds.gradle.org/viewQueued.html?itemId=7883085

Any performance regression won't show unless we are particularly testing for this scenario, which is first resolve of gradleApi() for a gradle version/home.

Right. @bmuschko can you check if we can add a performance test for this? Or find another way to measure the speed impact of the change?

We already have a performance test in place: GradleImplDepsPerformanceIntegrationTest. However, I noticed that the time measured for the generation of the JAR files is off. Currently, the generation of JAR files is triggered independent of its actual use in the build. I logged the issue https://github.com/gradle/gradle/issues/2815 for it. The tests would need to be adjusted and the issue would potentially need fixing.
I did some preliminary measurements for just the code that's responsible for the generation of the JARs. It is a bit slower. For the Gradle API JAR roughly 2 secs, for the Gradle TestKit JAR roughly 10 ms. 2 seconds doesn't sound too bad to me for a one-time generation.
Before change:
gradle-api JAR: ~5000-5500 ms
gradle-testkit JAR: ~20-30 ms
After change:
gradle-api JAR: ~6700-6900 ms
gradle-testkit JAR: ~29-32 ms

@jjohannes @ldaley Do you think it's worth pursuing this? I am probably going to close this PR if we are not on the same page.

I think I would lean towards not making the change as speed should always be the main concern. I see that the impact might be small, but I also do not see an urgent need to reduce the size of the jar(s).

I think I would lean towards not making the change as speed should always be the main concern.

Fair enough. Can't argue with that.

...urgent need to reduce the size of the jar(s).

Many customers complain about the size of the cache in general and that it is never purged. That's a bigger discussion though. With this change I tried to make things a little bit better at least.

Did we measure how much slower/faster it becomes to use the generated JARs? I mean, we generate it somewhat slow in the beginning, but having to read half as much data from disk could make things faster in subsequent builds.

Did we measure how much slower/faster it becomes to use the generated JARs?

You make a good point. I haven't measured that.


Add name of track for id274

Flying through the Dravanian Forelands, I was puzzled seeing a track named "Heavensward safezone music 2".
I thus went through Spotify and the Community Spreadsheet to make sure that I didn't do anything wrong. Both agree that this track is called "Safety in Numbers". In accordance with Shelter, the other safezone track in Heavensward, I moved the description of the track to the second column.

Closing because change has already been reflected in Caraxi's patch.


No appointment created in google calendar

There are no one errors in the automated response but no entries were made in calendar

Were you able to solve it? I am facing the same issue

Same and this happens with any Dialogflow fulfillment.

I'm getting the same thing, I've found this fix for which suggests that you need to disable "Dialoglow V2 API" but when I try to do this in the console it doesn't let me, the radio button won't uncheck. Not sure if this is to do with the new API or not?

I didn't even got that positive response.
All i get is: Sorry, we're booked on Invalid Date at Invalid Date. Is there anything else I can do for you?

I am almost giving up on dialogflow..

Did you get this warning? I'm not sure but maybe this is a culprit.

Any solutions here?
I was able to create some appointment somewhere because when I try it for the 2nd time, it says that this date is taken. But I don't see the appointment anywhere in the calendar.
I used calendarId: 'primary'.
Any ideas?

Any solution please?

Anyone already found a solution for this?  Seems to be a problem everyone has...
Pretty frustrating issue.

How come this is open so long, and nobody has a solution to it? Is this API broken in general?

How come this is open so long, and nobody has a solution to it? Is this API broken in general?

I'm pulling my hair out on this one.  Been at it for 2 days straight and nothing I try works.

I am having the same issues.  I have commented out any database references.  I'm thinking it maybe related to this code base for some reason, but I've followe
const admin = require('firebase-admin');
const {Card, Suggestion} = require('dialogflow-fulfillment');
admin.initializeApp({
});

same here any help

same here any help

Please help me out if you find any solution

Same issue . Pls help me out

Same issue

same here - help please

same here, not able to add the meeting in calander via Dialogflow

Did you get this warning in Fulfilment? I'm not sure but maybe this is a culprit.

Yes, I'm getting this warning. Are you able o resolve this issue?

I'm not sure. But I was able to resolve the issue.
On Tue, 27 Jul, 2021, 5:39 pm Ramachandra.N, @.***>
wrote:

Did you get this warning in Fulfilment? I'm not sure but maybe this is a
culprit.
[image: err]
https://user-images.githubusercontent.com/13984195/60947363-523a8980-a32b-11e9-912b-5a3cfcccdf5f.JPG
Yes, I'm getting this warning. Are you able o resolve this issue?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dialogflow/fulfillment-bike-shop-nodejs/issues/11#issuecomment-887458166,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIU3QJKAYFLJDAPUOM6IVPLTZ2OYXANCNFSM4GYDBXRQ
.

Thanks. How did you resolve this issue?
On Tue, Jul 27, 2021 at 5:55 PM Rithwik Reddy @.***>
wrote:

I'm not sure. But I was able to resolve the issue.
On Tue, 27 Jul, 2021, 5:39 pm Ramachandra.N, @.***>
wrote:

Did you get this warning in Fulfilment? I'm not sure but maybe this is a
culprit.
[image: err]
<
https://user-images.githubusercontent.com/13984195/60947363-523a8980-a32b-11e9-912b-5a3cfcccdf5f.JPG
Yes, I'm getting this warning. Are you able o resolve this issue?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<
https://github.com/dialogflow/fulfillment-bike-shop-nodejs/issues/11#issuecomment-887458166
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AIU3QJKAYFLJDAPUOM6IVPLTZ2OYXANCNFSM4GYDBXRQ
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dialogflow/fulfillment-bike-shop-nodejs/issues/11#issuecomment-887468192,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFQRL2K5RWDQXUVFJHMJEQ3TZ2QS5ANCNFSM4GYDBXRQ
.

Thanks. How did you resolve this issue? On Tue, Jul 27, 2021 at 5:55 PM Rithwik Reddy @.> wrote:
…
I'm not sure. But I was able to resolve the issue. On Tue, 27 Jul, 2021, 5:39 pm Ramachandra.N, @.> wrote: > Did you get this warning in Fulfilment? I'm not sure but maybe this is a > culprit. > [image: err] > < https://user-images.githubusercontent.com/13984195/60947363-523a8980-a32b-11e9-912b-5a3cfcccdf5f.JPG > > > Yes, I'm getting this warning. Are you able o resolve this issue? > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > < #11 (comment) >, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AIU3QJKAYFLJDAPUOM6IVPLTZ2OYXANCNFSM4GYDBXRQ > > . > — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#11 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFQRL2K5RWDQXUVFJHMJEQ3TZ2QS5ANCNFSM4GYDBXRQ .

https://codeshare.io/78JDqL

@ramachandra742
https://codeshare.io/78JDqL

Thanks, I'll check it out.
On Tue, Jul 27, 2021 at 6:20 PM Rithwik Reddy @.***>
wrote:

@ramachandra742 https://github.com/ramachandra742
https://codeshare.io/78JDqL
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dialogflow/fulfillment-bike-shop-nodejs/issues/11#issuecomment-887484549,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFQRL2PCFESWDX554SAIQZTTZ2TSXANCNFSM4GYDBXRQ
.

No, I was not able to figure it out.
On Tue, Jul 27, 2021 at 8:09 AM Ramachandra.N @.***>
wrote:

Did you get this warning in Fulfilment? I'm not sure but maybe this is a
culprit.
[image: err]
https://user-images.githubusercontent.com/13984195/60947363-523a8980-a32b-11e9-912b-5a3cfcccdf5f.JPG
Yes, I'm getting this warning. Are you able o resolve this issue?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dialogflow/fulfillment-bike-shop-nodejs/issues/11#issuecomment-887458166,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APJTPJMDMUZ7YPFOIR3V57TTZ2OYXANCNFSM4GYDBXRQ
.

Ok, thanks.
On Mon, Aug 2, 2021 at 7:24 PM allawton @.***> wrote:

No, I was not able to figure it out.
On Tue, Jul 27, 2021 at 8:09 AM Ramachandra.N @.***>
wrote:

Did you get this warning in Fulfilment? I'm not sure but maybe this is a
culprit.
[image: err]
<
https://user-images.githubusercontent.com/13984195/60947363-523a8980-a32b-11e9-912b-5a3cfcccdf5f.JPG
Yes, I'm getting this warning. Are you able o resolve this issue?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<
https://github.com/dialogflow/fulfillment-bike-shop-nodejs/issues/11#issuecomment-887458166
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/APJTPJMDMUZ7YPFOIR3V57TTZ2OYXANCNFSM4GYDBXRQ
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dialogflow/fulfillment-bike-shop-nodejs/issues/11#issuecomment-891046757,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFQRL2I32SCNCYB6XG6NJFTT22PQ5ANCNFSM4GYDBXRQ
.

to be honest, I started working on another project and left it.  sorry
On Tue, Jul 27, 2021 at 8:09 AM Ramachandra.N @.***>
wrote:

Did you get this warning in Fulfilment? I'm not sure but maybe this is a
culprit.
[image: err]
https://user-images.githubusercontent.com/13984195/60947363-523a8980-a32b-11e9-912b-5a3cfcccdf5f.JPG
Yes, I'm getting this warning. Are you able o resolve this issue?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dialogflow/fulfillment-bike-shop-nodejs/issues/11#issuecomment-887458166,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APJTPJMDMUZ7YPFOIR3V57TTZ2OYXANCNFSM4GYDBXRQ
.

No problem, thanks!
On Mon, Aug 2, 2021, 22:50 allawton @.***> wrote:

to be honest, I started working on another project and left it. sorry
On Tue, Jul 27, 2021 at 8:09 AM Ramachandra.N @.***>
wrote:

Did you get this warning in Fulfilment? I'm not sure but maybe this is a
culprit.
[image: err]
<
https://user-images.githubusercontent.com/13984195/60947363-523a8980-a32b-11e9-912b-5a3cfcccdf5f.JPG
Yes, I'm getting this warning. Are you able o resolve this issue?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<
https://github.com/dialogflow/fulfillment-bike-shop-nodejs/issues/11#issuecomment-887458166
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/APJTPJMDMUZ7YPFOIR3V57TTZ2OYXANCNFSM4GYDBXRQ
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dialogflow/fulfillment-bike-shop-nodejs/issues/11#issuecomment-891197501,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFQRL2P7Y43OLIQUITFEASLT23HWNANCNFSM4GYDBXRQ
.


Initialization script when PGData is not empty

I know that when the PGData directory is not empty the container skips the initialization and therefore won't run the initialization script in /docker-entrypoint-initdb.d
I would like to use a way to give the container scripts that will run on startup no matter what (for example to create a role postgres if one does not exist already)

Hi @tianon! Thanks for your response.
I managed to run an init script on my db but it fails with role "postgres" does not exist (it was probably deleted).
I don't know what roles the db has and I want to use the init script to verify the postgres role exists (and if not to create one).

You can run
docker exec -u postgres -it postgres psql
psql (16.2 (Debian 16.2-1.pgdg120+2))
Type "help" for help.

postgres=# \du
                             List of roles
 Role name |                         Attributes
-----------+------------------------------------------------------------
 postgres  | Superuser, Create role, Create DB, Replication, Bypass RLS

Hi @LaurentGoderre unfortunately your solution would not work in my case because there is no role postgres so I'm unable to execute any command with -u postgres, that's why I would like to init the db with a postgres role creation

@tomera-cyera I believe postgres in this case refers to the OS user which is postgres not the db role.

@LaurentGoderre Yes, sorry if it wasn't clear

No, I refer to the postgres db role in case I initialize the container with data-dir that does not have the role postgres I want to make sure the postgres role will be created if not exist

OOh you mean at initialization?

@LaurentGoderre, yes. you see I need to initialize the db to have a postgres role even when the datadir already exists (a.k.a the db already initialized)

@yuvall-cyera can you please be more specific about what it is you're looking for feedback on?  IMO the thread above is pretty clear (if you need one-time initialization, the image has that as-is, and if you need more than that, see the references in https://github.com/docker-library/postgres/issues/1229#issuecomment-2064636436)


react-native transform error on default AwesomeProject (unknown corruption from fresh reinstall)

Is this a bug report?
Yes
Have you read the Contributing Guidelines?
yes
Environment
Windows 10 ver 15063.540
react-native-cli: 2.0.1
react-native: 0.47.1
node v6.11.2
not using yarn

Development Operating System:

android-studio ver 2.3.3

Build tools:

Steps to Reproduce

(Write your steps here:)
react-native init AwesomeProject
cd AwesomeProject
[standard project directory is found. have been developing for approx 8 days. previous various error types which managed to debug and resolve. This is different.]
react-native run-android
Expected Behavior
expected standard AwesomeProject to load.
Actual Behavior
Previously had react-native running nicely, don't recall changing anything, then this error which has proved impossible to clear.environment Windows 10 react-native-cli: 2.0.1 react-native: 0.47.1 node v6.11.2fresh install of node.js after uninstalling previous versions and removing all node and npm directories from paths. fresh install of react-native as per https://facebook.github.io/react-native/docs/getting-started.htmlreact-native init AwesomeProject cd AwesomeProject react-native run-androidalso triednpm i -g react-native-git-upgradereact-native-git-upgradereboot, new project, uninstall node, reinstall node, reinstall react-native, new project.still same problem.repeated with react-native-git-upgrade v0.47.0 Wondering if I should try downgrading to an earlier version. Weird thing is it was working a 2 days ago on react-native version downloaded and installed 8-9 days ago.Repeatedly getting same error as below. lost too much time on this. really hurts.The development server returned response error code: 500URL: http://<IP_ADDRESS>:8081/index.android.bundle?platform=android&dev=true&hot=false&minify=falseBody: {"message":"TransformError: D:\blah\AwesomeProject\index.android.js: Unexpected token ) (While processing preset: "D:\blah\AwesomeProject\node_modules\babel-preset-react-native\index.js")","type":"TransformError","lineNumber":0,"description":"","errors":[{"description":"","lineNumber":0}]} processBundleResult BundleDownloader.java:170 access$100 BundleDownloader.java:39 onResponse BundleDownloader.java:139 execute RealCall.java:135 run NamedRunnable.java:32 runWorker ThreadPoolExecutor.java:1133 run ThreadPoolExecutor.java:607 run Thread.java:761
-->
red error screen on android studio android emulator
no additional error info via external debugger.
have tried
npm i -g react-native-git-upgrade
react-native-git-upgrade
and
react-native-git-upgrade v0.47.0
always the same problem.
Reproducible Demo
https://snack.expo.io/SJz9BMSdW
NB: above example with all stylsheet references removed and simplified to most basic hello world.
have checked previous path settings from previous installs were removed priot to reinstalls.
really at a loss here. Don't know what else I can possibly check.
nb: have choco installed, I think previous install did not use choco to install nodejs, uninstall was without using choco.
checked choco uninstall nodejs  : said nodejs not installed prior to reinstalling without choco.
just bought a new laptop and really not enjoying this. also wondering if problems are less on a linux based dev environment.

This was happening to me earlier. The following lines solved the problem for me  (Windows 10). However, for anyone on OSX, this might require extra work for the same problem. This made me have to install yarn since I didn't have it earlier.
yarn remove babel-preset-react-native

yarn add<EMAIL_ADDRESS>
This fixed the problem for me. Although, later on I ran into other React Native problems (such as, run-android not being recognized as a

wow. thanks for the fast answer.
This worked.
Everything is wonderful again.
also: my first issue raised on a large package. achievement unlocked. :)

wow, @bchehraz thank you! I've been staring at a red simulator for about a week now.

Where am I supposed to run the commands? within the project folder or inside node_modules?

@divyakoshy I actually needed those 3 commands but for a different reason. My ESLint started to tell me my import statements were reserved-- and the "react-native run-android" command stopped working altogether. It was strange.
Anyway, I followed what you said and it fixed my problem. 😄

@bchehraz How did you get the ESLint stuff working. Im using webstorm and it is now suffering from amenesia about ES6 after I ran these commands ? Any help will be really appreciated.

@Almjz Give me more details. What's working and what's not working? Are there import statements that are now invalid? Can you still run react-native commands like run-android?

@bchehraz Yes imports statments and anything es 6 is flagged as a warning as reserver word but react native run-ios works okay

@bchehraz thanks for the answer! I'm running on OSX, had to install yarn but it worked. Simulator works perfectly now

@Almjz I'm using the RallyCoding extension on ESLint. I think to address this you can try to remove all of ESLint, it's possible that some other unneeded packages are interfering with your ESLint. To do this, run this command in the project directory:
npm uninstall eslint
After that, I will run the command that installs this specific ESLint in the same directory:
npm install --save-dev eslint-config-rallycoding
This may or may not fix your problem. And in my .eslintrc file I would put (inside specific project directory):
{   "extends": "rallycoding" }
Let me know if that works for you.

@bchehraz thanks so much for the solutions. It work like a charm!

This was hepful for me too. Thank you


Starting logstash_notifier without any arguments crashes

When running logstash_notifier from the command line, it raises an exception:
$ venv-test/bin/logstash_notifier -h
Traceback (most recent call last):
  File "venv-test/bin/logstash_notifier", line 11, in <module>
    sys.exit(main())
TypeError: main() takes exactly 1 argument (0 given)

Appears to be because the source of the generated command line tool calls __init__.py::main directly bypassing the if __name__ == '__main__' handling:
$ cat venv-test/bin/logstash_notifier
#!/venv-test/bin/python

# -*- coding: utf-8 -*-
import re
import sys

from logstash_notifier import main

if __name__ == '__main__':
    sys.argv[0] = re.sub(r'(-script\.pyw|\.exe)?$', '', sys.argv[0])
    sys.exit(main())

Should now be fixing in version 0.1.1 with pr #4


Aubo package can't be catkin_make because of Eigen3

Recently, I met the problem that Aubo package can't be catkin_make because of Eigen3 lib. Also the same issues occurs with moveit_tutorials can't be catkin built because of Eigen3.
My ROS system is Kinetic,  the Eigen3 version is 3.3~beta 1-2. And the gcc version is 5.4.0.
I follow the aubo_robot/readme.md file to install Aubo package, and I have install moveit-core and induatrial-core, but I met the error occures. And the error log file is in the following.
From the error log file, I think the version of Moveit_tutorials is not compatible with the version of Eigen3. Because the error log file shows the problem is from  Eigen::transform() function. Furthermore, I check the tranform.h file from Eigen3 lib, the Eigen::Transform() function is forbidden to use, because this function may cause error. But the error log file show that the movtit_tutorial have call the Eigen::transform() function, so it make a mistake.
[ 93%] Built target aubo_joint_trajectory_action
In file included from /usr/include/eigen3/Eigen/Core:142:0,
from /usr/include/eigen3/Eigen/Geometry:11,
from /home/menghui/ws_moveit/src/moveit/moveit_core/robot_model/include/moveit/robot_model/joint_model.h:47,
from /home/menghui/ws_moveit/src/moveit/moveit_core/robot_model/include/moveit/robot_model/joint_model_group.h:41,
from /home/menghui/ws_moveit/src/moveit/moveit_core/robot_model/include/moveit/robot_model/robot_model.h:47,
from /home/menghui/ws_moveit/src/moveit/moveit_core/robot_state/include/moveit/robot_state/robot_state.h:41,
from /home/menghui/ws_moveit/src/moveit/moveit_ros/planning_interface/move_group_interface/include/moveit/move_group_interface/move_group_interface.h:43,
from /home/menghui/aubo_ws/src/aubo_robot/aubo_demo/src/MoveGroupInterface_To_Kinetic.cpp:39:
/usr/include/eigen3/Eigen/src/Geometry/Transform.h: In instantiation of ‘Eigen::Transform<Scalar, Dim, Mode, _Options>::Transform(const Eigen::Transform<_Scalar, Dim, OtherMode, OtherOptions>&) [with int OtherMode = 2; int OtherOptions = 0; _Scalar = double; int _Dim = 3; int _Mode = 1; int _Options = 0]’:
/home/menghui/aubo_ws/src/aubo_robot/aubo_demo/src/MoveGroupInterface_To_Kinetic.cpp:92:73:   required from here
/usr/include/eigen3/Eigen/src/Core/util/StaticAssert.h:33:40: error: static assertion failed: YOU_PERFORMED_AN_INVALID_TRANSFORMATION_CONVERSION
#define EIGEN_STATIC_ASSERT(X,MSG) static_assert(X,#MSG);
^
/usr/include/eigen3/Eigen/src/Geometry/Transform.h:334:5: note: in expansion of macro ‘EIGEN_STATIC_ASSERT’
EIGEN_STATIC_ASSERT(EIGEN_IMPLIES(OtherMode==int(Affine)||OtherMode==int(Af
^
[ 95%] Linking CXX executable /home/menghui/aubo_ws/devel/lib/aubo_driver/testAuboAPI
[ 96%] Linking CXX executable /home/menghui/aubo_ws/devel/lib/aubo_driver/aubo_driver
[ 96%] Built target testAuboAPI
[ 96%] Built target aubo_driver
[ 98%] Linking CXX executable /home/menghui/aubo_ws/devel/lib/aubo_planner/aubo_planner_test
aubo_robot/aubo_demo/CMakeFiles/MoveGroupInterface_To_Kinetic.dir/build.make:62: recipe for target 'aubo_robot/aubo_demo/CMakeFiles/MoveGroupInterface_To_Kinetic.dir/src/MoveGroupInterface_To_Kinetic.cpp.o' failed
make[2]: *** [aubo_robot/aubo_demo/CMakeFiles/MoveGroupInterface_To_Kinetic.dir/src/MoveGroupInterface_To_Kinetic.cpp.o] Error 1
CMakeFiles/Makefile2:595: recipe for target 'aubo_robot/aubo_demo/CMakeFiles/MoveGroupInterface_To_Kinetic.dir/all' failed
make[1]: *** [aubo_robot/aubo_demo/CMakeFiles/MoveGroupInterface_To_Kinetic.dir/all] Error 2
make[1]: *** 正在等待未完成的任务....
[ 98%] Built target aubo_planner_test
Makefile:138: recipe for target 'all' failed
make: *** [all] Error 2
Invoking "make -j8 -l8" failed

@mengzhilinxi2018
Recently we checked our master branch, the compiler did not find the above error. because you also have errors when compiling moveit_titorial, I suggest you check your ROS environment.
Need to pay attention to Eigen appears in the indigo version, Eigen3 appears in the kinetic version, and CmkaeList.txt in our program makes a distinction


PSSE Exporter Part 1: Add Tests and Formalize Exporter Implementation

This PR picks up the effort to implement a Sienna to PSS/E exporter, an effort started by @HaleyRoss here (see also my cleanup of that code to work with PSY4 here). Very much a draft for now, but I'll be building out a public interface to perform this export in the next few weeks.

Here's my Git plan:

hrgks/psse_exporter_psy4 is a "dev" branch
For each major part of this effort (currently we have identified three), I'll submit a PR into there
We'll avoid merging hrgks/psse_exporter_psy4 into main until I can be more certain that there will be no more breaking interface changes (probably not until the end of part two)

This lets me submit PRs for code review along the way, rather than having one massive code review at the end, while also letting the interface evolve as I discover more requirements of it.

The current exporter interface is:
# Initialize an exporter from a Sienna system
PSSEExporter(PSY.System, psse_version::Symbol)

# Whenever you have new data to export, update the exporter with either a `PowerFlowData` or
# a modified `System` (which must be fundamentally the same system, just with some values changed):
update_exporter!(exporter::PSSEExporter, data::PowerFlowData)  # preferred
update_exporter!(exporter::PSSEExporter, data::System)  # less preferred

# Actually perform an export
write_export(exporter::PSSEExporter, scenario_name::AbstractString, year::Int, export_location::AbstractString)

and I expect this will probably stay roughly the same throughout Part 1 — though I may change up the arguments a bit — but will probably change substantially in Part 2.

The current status of Part 1 is that the above interface is fully implemented and round-trip tested up to a certain level, but the implementation still relies on old code. I'll now work on a from-scratch reimplementation of the exporter.

@jarry7 verifies that PSS/E can read the export as currently written under certain modes but not others. I'm going to merge this into the dev branch now to continue with Part 2 and readdress this later.


Order of kind coalesce sometimes funky

This feature is a soccer pitch, but is showing up as kind:university in tiles:
https://www.openstreetmap.org/way/338698145

amenity:university
landuse:grass
sport:soccer

We also need to deal with *=yes values. See #335.
For instance:
http://vector.dev.mapzen.com/osm/all/18/41885/101371.topojson?api_key=vector-tiles-HqUVidw
{
type: "Point",
properties: {
kind: "yes",
id:<PHONE_NUMBER>,
name: "Special Education & Communicative Disorders"
},
coordinates: [
252,
94
]
}
]

Matt suggests:
3) Pull all the values "aerialway", ... "waterway" back to Python-land and normalise them to a kind there. This is, I think, what we'll end up doing for #282 anyway to have more control over kind selection.

This is coming up again for the Indy's work, scheduled in March

Do we want to put in the effort for transitioning to an explicit kind calculation for each layer at this point? Or do we want to make a smaller effort here to just transition to a smarter coalesce in python to ensure that we don't get kind=yes properties?
I assume the former since based on previous discussions it sounded like this was the eventual goal.

Tiles meeting: let's pursue the CSV route.

The implementation will be related to #580.

Another example for Indy's Fitness blog post:
In some tile cut runs this building is kind:yes, others it's kind: fitness_centre:

https://www.openstreetmap.org/way/264528016

In some tile cut runs this building is kind:yes, others it's kind: fitness_centre

If this is displaying non-determinism, then it is a different issue. That building / fitness centre doesn't seem to have been edited recently, and we don't coalesce the building value in the kind calculation. There is some extra processing for fitness, but it only sets the kind to fitness, never yes. Likewise, there's some extra processing for buildings, but these explicitly avoid setting kind: yes.
Currently, I'm seeing kind: fitness on both dev and prod - if anyone sees a different value for this feature, please file a new bug with the full GeoJSON/TopoJSON tile attached!

Moving the fitness building discussion to: https://github.com/mapzen/vector-datasource/issues/589.

Both examples are fixed. Verified visually and in tiles.


data下的bag文件太大，请问是什么文件？可以删除吗？

Yes, can be deleted if you don't need it.
files
The data directory mainly includes the following types of files

Bag package recorded by cyber_recorder, In most cases the recording is manually triggered
In the case of automatic driving takeover, the data automatically saved by the system

thank you!

Yes, can be deleted if you don't need it.
files
The data directory mainly includes the following types of files

Bag package recorded by cyber_recorder, In most cases the recording is manually triggered
In the case of automatic driving takeover, the data automatically saved by the system

Hi, may I ask how to turn off the automatic record function in automatic driving mode?

This depends on how you start the autopilot module. Normally, record files will not be recorded actively.
@AOOOOOA This issue will be closed. If you have questions about recording, please create a new one.


style: contracts

:notebook: Overview
Lints contracts

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

116 of 231 (50.22%)  changed or added relevant lines in 25 files are covered.
44 unchanged lines in 10 files lost coverage.
Overall coverage decreased (-2.3%) to 56.379%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

contracts/staking/GrgVault.sol
5
6
83.33%

contracts/staking/libs/LibCobbDouglas.sol
0
3
0.0%

contracts/staking/sys/MixinFinalizer.sol
3
7
42.86%

contracts/protocol/RigoblockV3Pool.sol
18
26
69.23%

contracts/protocol/extensions/adapters/AUniswapV3.sol
0
9
0.0%

contracts/protocol/extensions/adapters/AUniswapV3NPM.sol
0
9
0.0%

contracts/staking/staking_pools/MixinStakingPoolRewards.sol
3
12
25.0%

contracts/staking/libs/LibFixedMath.sol
0
72
0.0%

Files with Coverage Reduction
New Missed Lines
%

contracts/staking/libs/LibCobbDouglas.sol
1
0%

contracts/staking/libs/LibSafeDowncast.sol
1
53.33%

contracts/staking/staking_pools/MixinCumulativeRewards.sol
1
41.18%

contracts/staking/sys/MixinFinalizer.sol
1
39.39%

contracts/staking/GrgVault.sol
2
61.11%

contracts/staking/libs/LibFixedMath.sol
2
0%

contracts/protocol/extensions/adapters/AUniswapV3NPM.sol
4
0%

contracts/protocol/RigoblockV3Pool.sol
5
68.82%

contracts/staking/staking_pools/MixinStakingPoolRewards.sol
8
29.41%

contracts/protocol/extensions/adapters/AUniswapV3.sol
19
0%

Totals

Change from base Build<PHONE_NUMBER>:
-2.3%

Covered Lines:
548

Relevant Lines:
937

💛  - Coveralls


Automatically populate development databases with sample data

We can run the script at https://github.com/DigitalSlideArchive/tcga_ingest , but terminate after the first dozen images or so.

This is now implemented.


windows build

The package.json scripts use npm environment variables with ${} syntax. This does not work in windows shells. Thus it is necessary to change the npm script shell via
npm config set script-shell="C:\\Program Files\\git\\bin\\bash.exe"

But due to https://stackoverflow.com/questions/63996834/maven-doesnt-work-in-git-bash-on-windows the build fails when it wants to use ./mvnw. Overriding ./mvnw with
echo '#!/bin/sh' > mvnw
echo 'mvn "$@"' >> mvnw

works to call the existing mvn executable. It is necessary to git restore ./mvnw at the end of the build to make sure the git repository is clean.

Figured it out and opened an issue in the maven-wrapper repository.


EF Projections: Allow registering multiple DbContexts on the readmodel

At the moment we are limited to having one single DbContext, we can register multiple projections under the AddReadModel extension method.
The proposal is to allow multiple calls to AddReadModel with different DbContext instances for any number of projections.

Closed by #76 and #79


Add IsActive to ApplicationLanguage entity.

This will allow enable / disable languages.

Hi Ismail,
To double confirm on this enhancement, it allows administrator to set the list of 'active' languages and therefore, restricting the list of languages the users are able to select as their preferred language in the languages dropdown list?
Thanks.
/Tommy

It's for that. But "filtering inactive languages to create language selection list" is application's responsibility like:
var activeLanguages = languageManager.GetLanguages().Where(l => !l.IsDisabled).ToList();

Hi Halil,
Thanks for prompt response.  I would also like to confirm if the following behavior is part of the enhancement where "once a user selected a preferred language, the system will always show that specific language regardless of which device used to logged in or cookies or user session".
To understanding, aspnetzero will show the user selected language after logged out and in again but it is NOT permanent as it will revert to system default language if log in using a different device or using "In-private browsing" mode with IE.


💄 API Provider Spacing

This is a...

[ ] Feature request
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ x] Bug report
[ ] Documentation issue or request

Spacing is incorrect ont the main API Provider page

@mcoker I'm not really sure if this can be addressed entirely on your side. In case not, please add comment here..
Thanks

The file uploader spacing should be fixed in https://github.com/syndesisio/syndesis-react/pull/403
This is master

How does that look @gaughan? Or were you referring to something else?

@gaughan ping - is this still an issue?


[c++][wip] Addition of SOMAMetadataMapping

Issue and/or context:

#1577
https://github.com/single-cell-data/SOMA/blob/main/abstract_specification.md#somametadatamapping

Changes:

Cache metadata values in map when opening the array or group so that it can be accessed in either read or write mode

Notes for Reviewer:
N/A

Codecov Report
Patch coverage has no change and project coverage change: -11.89% :warning:

Comparison is base (7b37048) 65.47% compared to head (5763843) 53.59%.
 Consider uploading reports for the commit 8ce5c16 to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1584       +/-   ##
===========================================
- Coverage   65.47%   53.59%   -11.89%
===========================================
  Files         108       74       -34
  Lines        9003     6141     -2862
===========================================
- Hits         5895     3291     -2604
+ Misses       3108     2850      -258

Flag
Coverage Δ

python
?

r
53.59% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 35 files with indirect coverage changes

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


still supported?

I get a lot of deprecated warnings these days when using this module. Are you considering updating it?

Hello,
Not update here but you can find a fork here: https://github.com/solution-libre/puppet-gitolite
Regards,


e2e tests in CI

closes: #12
closes #15
Integrations tests are not added for now as the e2e tests cover all routes : #64

bors try

bors try

bors merge


Updating PowerTools to only build on VS2017

(but still install on older versions). This is required so that the build will generate manifest.json and catalog.json within the resulting VSIX which are required for the VSIX to install on VS2017.
Fix for #152

Note: I can revert the #line changes if you think it's important. But given that I'm going to be out for a few days I thought you'd like to see the changes before I leave.

Fix checked in with commit 4fe5c3c.


add more helpful syntax links to dynamic badges

fixes https://github.com/badges/shields/issues/3203

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @tooomm!

:book:

Thanks for contributing to our documentation. We :heart: our documentarians!

  Generated by :no_entry_sign: dangerJS against 77d5b0766d4353cb55a2f20d63992d74369f8151


Renaming merged samples in a more robust way

cc @BrieucF
This should avoid renaming the samples in downstream scripts for every new prod

Thanks!


Risk Level resource

This PR adds a Risk Level resource that can be used to create a risk level. You can use this to set a risk level on a entitlement.

Closing in favor of 27


Thibaultmh/proposed fix to decode id token without kid in alg header

DO NOT SEND ANY SECURITY FIX HERE. Please read "Security Reporting" section
on README.

What kind of change does this PR introduce? (check at least one)

[X] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes
[X] No

[X] You consent that the copyright of your pull request source code belongs to Authlib's author.

First of all thx for maintaining this awesome library.
Any perspective on when this PR will be released?

Thanks for the fix.

Was about to raise a PR for this, thanks! Would it be possible to bump the version? @lepture


Incorrect sorting of predicted formulae

Basic information

My operating system and version: Windows 10
My MZmine version: 3.4.0

What happened
The selected formula from those assigned to a feature based on the m/z, using the "formula prediction" module, is often incorrect. Where multiple fomulae are assigned, the selected main formula is the assignment with the lowest Δm/z as opposed to the lowest absolute Δm/z.
For example, the feature below displays a predicted formula of C23H22N2O2 with a Δm/z ppm of -2.2257:

The dropdown menu on the formula shows an alternative of C15H26N4O4S, which has a lower absolute m/z difference (-0.4064) and a higher "Combined score":

This second formula should be the default, and the same is true whenever there is a suggested formula with a very negative Δm/z or multiple negative Δm/z suggestions. The behaviour is as expected when no negative Δm/z values are present as then the smallest Δm/z is also the smallest absolute Δm/z. This issue then carries through to exported csv's unless the formulae are manually changed prior to export, which is not feasible for a large untargeted analysis.
I have included an example project here which should demonstrate this problem, but I believe the same will apply to any use of the formula prediction module.
Thanks for taking the time to look through this, let me know if there is any more information I can provide to help clarify, and apologies if I have overlooked anything.

Did you apply sorting in formula prediction?
Can you add your batch processing file or screenshots of all parameters?

Yes, sorting was selected in the formula prediction module. I've put a screenshot below, and a link to the batch file here.

I also tried adjusting these parameters to be 10, 0, 0 for max ppm distance (weight), weight isotope pattern score, and weight MS/MS score respectively. This didn't seem to make any difference to the outcome (presumably because isotope score and weight MS/MS score are empty in this example).

Hi there, I am also having exactly the same problem. It seems that where multiple formulae are assigned, the selected main formula is the assignment with the lowest Δm/z i.e largest negative value, as opposed to the lowest absolute Δm/z as previously stated. When exporting the csv, unfortunately the Δm/z is not given for all potential (Top N) formulae, so can't be sorted out in post processing. Currently, we are having to use mzmine 2.53 due to this issue.

Hi,
i think we finally found the issue. Feel free to test the latest development built, which should be available in a few minutes.
https://github.com/mzmine/mzmine3/releases/tag/Development-release


Mismatch between changing the pods CIDR config and the automatic iptables rules

Summary
Following this guide to change the pods CIDR instruct to modify two files /args/kube-proxy and /args/cni-network/cni.yaml. And it works fine.
But I also encountered the same issues as in #266 after rebooting my nodes. Somehow on only one node, the traffic from the cluster couldn't reach anything. iptables was reset to -P FORWARD DROP.
microk8s had added an automatic rule to allow forward traffic on the node. Using iptables -S:
-A FORWARD -s <IP_ADDRESS>/16 -m comment --comment "generated for MicroK8s pods" -j ACCEPT
-A FORWARD -d <IP_ADDRESS>/16 -m comment --comment "generated for MicroK8s pods" -j ACCEPT

Problem is, this is the default CIDR, and not the changed one.
Looking at the code adding this rule here  it takes his cidr information from either /args/kubelet or /args/flannel-network-mgr-config, which is not the same as the files mentioned in the guide above. The flannel config file still have the old <IP_ADDRESS> value.
What Should Happen Instead?
No clash between the CIDR configuration location, so that following the guide to change CIDR also set the correct iptables rules.

Hi @Dunge
Thank you for bring this issue to our attention. Indeed this seems to be a bug on our scripts. I believe we should be getting the CIDR from kube-proxy. Would you be interested in a PR to address this? If not we will provide a fix shortly. Many thanks.


Improving IntelliSense for React Components in JavaScript

From: https://github.com/Microsoft/vscode/issues/24926
Problem
For a simple react component defined in a JavaScript file:
class MyComponent extends Component {
    render() {
       ...
    }
}

I was unable to figure out how to get proper intellisense inside of Component. Specific problems:

No suggestions for members of Component provided inside of MyComponent when typing this.
No way to specify the type of props or state using jsdocs.

https://github.com/Microsoft/vscode/issues/24926 suggested that we use the PropTypes object for IntelliSense. I'm not sure this is feasible, although someone could probably write a TSServer plugin to do this.
However, I also wasn't able to write a jsdoc that provides proper IntelliSense here. Is there any way to do this currently?

I may be missing something obvious, but I would imagine integrating with React's propTypes would be the most obvious path here.  So
static propTypes = {
    x: PropTypes.string,
    y: PropTypes.number,
    submoduleStore: PropTypes.instanceOf(store)
}

would type this.props.x, .y, and .submoduleStore correctly.

I may be missing something obvious, but why would using propTypes not be feasible?  Why would
static propTypes = {
    x: PropTypes.string,
    y: PropTypes.number,
    submoduleStore: PropTypes.instanceOf(store)
}

inside a class not be doable to infer type bindings inside of this.props.

Someone on the TypeScript team may be able to speak to this better, but I don't think we can pick up types from a static property like that. A TypeScript server extension may be able to enrich TypeScript's knowledge of the component however

I guess I'm speaking more on the VS Code side, than TypeScript.  I'm not sure if VS Code does any sort of type inference on its own, or it's just limited to what TypeScript would do.
I can see why TypeScript wouldn't bake in React support to their language; I had just assumed VS Code would be able to, assuming the file is javascriptreact or typescriptreact, be able to sniff out propTypes on a class component definition.
But no complaints - we're really loving VS Code :)

You could use @augments to specify the propTypes as well as the type of the state for a react component.  for instance:
/**
 * @augments {Component<{x: string, y:number}}, State>}
 */
class MyComponent extends Component {
...
}

Now the type of this.props should be {x: string, y: number} and the type of of this.sate should be State.
As for bake-in inferences for react, we have always shied away from baking-in any type inferences for frameworks. we believe a better approach is to add more power to the language to allow users to explicitly declare their intent, hence the @augments support.

@mhegazy thank you SO much.  Will try this now.  I definitely don't think TypeScript should bake in React stuff - that comment should have been made on the VS Code issue, not here.  Apologies, and thanks again!

@mhegazy am I missing something?  Should this work, or am I missing something?
/**
 * @auguments {React.Component<{x: string, y: number}, {}>}
 */
export default class TasksComponent extends Component {
    render() {

        return null;
    }
}

right now I'm not getting any type inferences in this.props. inside render()

Closing since I believe the original question has been answered

I tried this workaround, but it doesn't seem to work with such a syntax:
    export default withStyles(styles)(
class MyComponent extends Component {

}
)

I tried:
/**
 * @augments {Component<{x: string, y:number}}, State>}
 */
export default withStyles(styles)(
class MyComponent extends Component {

}
)

or

export default withStyles(styles)(
/**
 * @augments {Component<{x: string, y:number}}, State>}
 */
class MyComponent extends Component {

}
)

without success.
Sorry for the bad formatting. (don't know what is happening)


Cleanup lab for handling errors

@balteravishay - I made various tweaks that I think are improvements. Let me know if I got something wrong!


[web] Make flutter web profile builds always keep wasm symbols

So far flutter build web --wasm was always stripping wasm symbols except if --no-strip-wasm is passed.
=> Ensure that in profile mode we also keep the symbols

Since this PR changes when we drop the symbols but doesn't update or add any documentation, should we update or add any documentation on when do we drop symbols?

I think this just brings it on par with dart2js & vm. Profile mode means one can profile (and see symbols on the profile).


Error underline wrong when lines are indented using tabs

If you get an error on a line with tab indents then the error underline is off. I done some testing and I am pretty sure that it is because Metis' error system prints the tabs directly to the terminal however assumes that the tab width is only one character. This means that the underline is in the wrong location if the terminal renders tabs as more than one character.
As for a solution, you could replace tabs with four spaces when printing the messages and then add four spaces instead of adding one to the prepending spaces before the underline for tabs.
This image shows an erroneous line with no indentation:

This image shows an erroneous line with a single tab indent:

Here is the output of the error message from the second screenshot (single tab indent) piped to a file and highlighting the whitespace.

Quick and dirty fix by replacing a tab with a space


samples: sysbuild: updated IPC RPMsg service to use CPU cluster SoC info

This commit updates Kconfig.sysbuild to use the CPU cluster info of the
SoC to determine the CPU cluster to use for the remote build.
This means that instead of testing each board, then it's now possible
to test against the CPU cluster of the SoC and thus support any board
which contains a SoC already supported in the IPC RPMsg Kconfig.sysbuild
file.

First commit is to be ignored, under review in #64792

@sylvioalves  I have done first move of the PROCPU / APPCPU for the RPMsg sample use-case in commit https://github.com/zephyrproject-rtos/zephyr/pull/69749/commits/74b33eabc620e65066d61596b895e2d1afd86737.
Please followup for other esp32 / esp32s3 based boards, and fell free to force-push into this PR, or push fixup commits, then I'll rebase afterwards.

@sylvioalves I have done first move of the PROCPU / APPCPU for the RPMsg sample use-case in commit 74b33ea.
Please followup for other esp32 / esp32s3 based boards, and fell free to force-push into this PR, or push fixup commits, then I'll rebase afterwards.

@tejlmand, thanks for bringing this. I would start handling it this week.

(Ack for changes, nack until first commit is removed)

No need to nack, we're still waiting @sylvioalves to push the changes to update remaining nxp boards.
Hence the DNM label.
@sylvioalves feel free to rebase the branch, so that both of us don't force-push the branch.

(Ack for changes, nack until first commit is removed)

No need to nack, we're still waiting @sylvioalves to push the changes to update remaining nxp boards. Hence the DNM label.
@sylvioalves feel free to rebase the branch, so that both of us don't force-push the branch.

Sure, working on that right now. Will push soon.

Sure, working on that right now. Will push soon.

@sylvioalves any updates on this ?


Refactor/select

Resolves #274 by trying to clean up src/Select.js and keep behaviour the same between ClickSelect and DragSelect actions. This is still a work in progress although now a selectAll function exists that handles the selecting and context options for all drag selections and most click selections (all but click selecting a staff and not clicking on an SVG element).

@zoemcl I think this is good for now. 134 lines less and some of it was tidied up. There's room for improvement but if everything looks alright to you I think we can merge it into develop.

@JRegimbal Looks good to me!


Default generated endpoints places variables into the root object: should variables be nested into a property?

Description
When you start a instance, you are submitted variables.  But when you GET an instance you are receiving process instance ~metadata and process variables (or task/local variables).
The variables are mixed into the name level as the metadata.  Should this data be moved into a nested property?  such as "variables", or "data" (data because that is the name used internally).
I suggest this because as processes get complex, the number of variables increases and it is quickly easily to get mixed up on what are variables and what are process/task metadata.  Then scale that out when you start to add new properties in the future, and could easily have variable name conflicts with newly added metadata.
Example: imagine one day you added a pre-calculated duration property for instances that showed the total duration (without the need to calculate it).  This could easily become a conflict with business variables.
Implementation ideas
No response

@cristianonicolai @evacchi @ricardozanini I agree with @StephenOTT rationale. Although currently we only have id as metadata, when we add business key, thing might start getting messy. I think wrapping model under a model field is a must.
I do not see as clear the need to wrap metadata under a different objet, because metadata fields the same one for all processes and there is not risk for name collision, which is the main argument to do that from my point of view

Anything that is a property name created by the modeler could cause collision. so should be isolated.

the main idea behind keeping it at root level is that we avoid having Kogito specific structure in the response, we want to focus on the domain and so making it extremely easy to be consumed/integrated elsewhere. In saying that I agree that at some point things can get messy. Maybe we could have strategies to deal with it so people can decide how to best approach this based on their use case. For instance, we could also have Kogito specific details sent as headers instead.

Having the "data" in the body makes it easy for consumption.  Getting into headers starts to create complexity for regular business data consumption.
What about an optional data wrapper that could be set in config?
@ChristianLowe if you do not have a model/data wrapper, how do you intend to deal with property name collision?  Imagine you decided in v1.20 to start returning a status property, dueDate or an assignee property on user tasks: these could easily be process variables already in use by modellers.

I think it's doable to have this feature configurable. This way, the consumer will understand the caveats and implications to their architecture. By default, we can add this information to the headers as we do for CloudEvents and OpenAPI client calls.

In my opinion, If we want to keep model data at root level, then we need to move the not model info under a different object. I propose to call that field "_meta" to make name colision really unlikely.
This idea is taken from HATEOAS impl named HAL, which use _links for additional info.


I change the join message but still says the old one?

I go into the file and set it to my own but still says the old one?

Its also with everything. Any of the messages i change doesn't change on the real bot..

When you changed the message, did you move the file into the "to-load" folder and restart the bot?

Well now i'm having another problem now it won't connect..i have the right username and password..and have it set to BEAM

Hmmm I have just connected to Beam fine, can you get the log file from ".otbproject/logs/app.log" and put the contents into a gist/pastebin please.

Thank you. I coulden't connect cause i had some bad code in some of the files and such.


Remove initialization of TranShkNow

fixes #326
I think it makes no sense to hard-code the initial transitory income shock. If it is super important from a practical point of view, we should simply make the very first distribution a discrete distribution with one point (1.0 ofc). Otherwise the simulations don't really match the model specification.

The problem goes the other direction, in my view. Lifecycle models in HARK
have no input for what the distribution of income shocks at t=0 should be.
The object ThisType.IncomeDstn[0] is what the solver needs to know for
t=0, which is the distribution of income shocks at the start of t=1.
Permanent income shocks at t=0 can be handled by the distribution specified
with the pLvlBlahInit variables-- there is no difference between initial
pLvl distribution and "shocks" that occur between birth and the first time
they could be "observed", so they're lumped together.
Transitory income shocks are more difficult, because we have no alternate
way to specify it. Moreover, there are some papers (including by us) that
assume no transitory shock in the very first period. Among other things,
this simplifies ex ante welfare analysis because you only consider the
value function at exactly one state.
In the big overhaul of HARK, this is one of the timing quirks that needs to
be worked out. We would like to be able to specify things so that shock
distributions at the beginning of t=0 are put into an instance like any
other period, but our solver framework knows that it's not actually useful
for solving the problem.
On Fri, Jun 21, 2019, 4:42 PM Patrick Kofod Mogensen <
<EMAIL_ADDRESS>wrote:

fixes #326 https://github.com/econ-ark/HARK/issues/326
I think it makes no sense to hard-code the transitory income shock. If it
is super important from a practical point of view, we should simply make
the very first distribution a discrete distribution with one point (1.0
ofc). Otherwise the simulations don't really match the model specification.
You can view, comment on, or merge this pull request online at:
https://github.com/econ-ark/HARK/pull/327
Commit Summary

Remove initialization of TranShkNow

File Changes

M HARK/ConsumptionSaving/ConsIndShockModel.py
https://github.com/econ-ark/HARK/pull/327/files#diff-0 (2)

Patch Links:

https://github.com/econ-ark/HARK/pull/327.patch
https://github.com/econ-ark/HARK/pull/327.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/econ-ark/HARK/pull/327?email_source=notifications&email_token=ADKRAFLE4EL5FSADBDOI3W3P3U4MTA5CNFSM4H2UWW72YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G3BLRXA,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADKRAFIGY6WFVOXXS7ZO6QLP3U4MTANCNFSM4H2UWW7Q
.

The object ThisType.IncomeDstn[0] is what the solver needs to know for t=0, which is the distribution of income shocks at the start of t=1.

I see you point. The model is solved conditional on the initial condition.
Then why don't we introduce a distribution of initial (t_age = 0) income shocks that is only used in these lines - that is it is only used for simulation. It's not necessary for solve() to run. The default can be IncomeDstnNow[0] for permanent income shocks and degenerate 0 or 1 for the transitory shocks. Optionally, they can be given as T_sim length arrays such that newborns are endowed with initial conditions the evolve as t in the simulations.
I think an explicit "initial shock distribution for simulation" would be both useful and easy to implement.

In the talk today, we agree on a solution as sketched above, so I will move forward with that. I'll keep the default as a degenerate "draw" of 1, but allow users to more flexibly control it with a distribution if they want.

@pkofod what is the status of this?


A value of Req type can't be assigned to a variable of "Req & Opt" type, although Opt has all fields optional and T is a record

Bug Report
When some record type is e.g. defined as generic FullRow<T extends { id: string }> = RequiredRow<T> & OptionalRow<T> where RequiredRow is a row with all required fields and OptionalRow is a row with all optional fields, an attempt to assign a value of RequiredRow to a variable of FullRow fails, although it should've been possible since OptionalRow has all fields optional.
When using no generics, it works as expected.
🔎 Search Terms
keyof generic
🕗 Version & Regression Information
Nightly & previous versions too
⏯ Playground Link
Here is a playground link
💻 Code
const $SYM = Symbol();

type Table = {
  id: string;
}

export type RequiredStringRow<TTable extends Table> = {
  [K in string & keyof TTable]: string;
};

export type OptionalSymbolRow<TTable extends Table> = {
  [K in symbol & keyof TTable]?: string;
};

export type FullRow<TTable extends Table> = RequiredStringRow<TTable> & OptionalSymbolRow<TTable>;

export function some1<TTable extends Table>() {
  const r1: RequiredStringRow<TTable> = {} as any;
  const r2: FullRow<TTable> = r1; // <-- ERROR HERE; why?
  console.log(r2);
}

export function some2() {
  type SomeTable = {
    id: string;
    some: string;
    [$SYM]: string;
  }
  const r1: RequiredStringRow<SomeTable> = {} as any;
  const r2: FullRow<SomeTable> = r1; // <-- it works
  console.log(r2);
}

🙁 Actual behavior
In some1(), the error is
Type 'RequiredStringRow<TTable>' is not assignable to type 'FullRow<TTable>'.
  Type 'RequiredStringRow<TTable>' is not assignable to type 'OptionalSymbolRow<TTable>'.
    Type 'symbol & keyof TTable' is not assignable to type 'string & keyof TTable'.
      Type 'symbol & keyof TTable' is not assignable to type 'string'.(2322)
const r2: FullRow<TTable>

The question is, why does it even try to type-match RequiredStringRow to OptionalSymbolRow, although it knows that FullRow is defined as RequiredStringRow & OptionalSymbolRow (and thus, it should've been 100% sure that RequiredStringRow is assignable to FullRow)?
(I actually have a suspicion why this happens: maybe I haven't convinced TS enough that OptionalSymbolRow always has all its fields optional, so TS thinks that it may have something non-optional. Is there a way to convince TS that some generic has ALL its fields optional no matter what?)
🙂 Expected behavior
r2 is correctly assigned

The question is, why does it even try to type-match RequiredStringRow to OptionalSymbolRow, although it knows that FullRow is defined as RequiredStringRow & OptionalSymbolRow (and thus, it should've been 100% sure that RequiredStringRow is assignable to FullRow)?

I think you have this backwards—intersection types are at least as narrow as the narrowest of their constituents, which means that A & B is always assignable both to A and to B, but not the reverse. Conversely, X is assignable to A & B if it is assignable both to A and to B individually.
So the job here is to find some value that can inhabit RequiredStringRow<TTable> but not FullRow<TTable> for some instantiation of TTable. I’ll use your SomeTable definition (playground):
type SomeTable = {
  id: string;
  some: string;
  [$SYM]: string;
}

const r1 = {
  id: "id",
  some: "some",
  [$SYM]: 3, // ❗
};

const _: RequiredStringRow<SomeTable> = r1; // Works
const r2: FullRow<SomeTable> = r1;
//    ^^
// Type '{ id: string; some: string; [$SYM]: number; }' is not assignable to type 'FullRow<SomeTable>'.
//  Type '{ id: string; some: string; [$SYM]: number; }' is not assignable to type 'OptionalSymbolRow<SomeTable>'.
//    Types of property '[$SYM]' are incompatible.
//      Type 'number' is not assignable to type 'string | undefined'.(2322)

This proves that not all RequiredStringRow<T> are assignable to FullRow<T>, because the former may have excess properties whose types conflict with those needed by OptionalSymbolRow<T>. Put another way, while your intuition is correct that FullRow<T> could not possibly require any additional properties that RequiredStringRow<T> doesn’t contain, if any additional symbol-keyed properties are present, their types could easily conflict with what OptionalSymbolRow<T> would require them to be.

    Type 'symbol & keyof TTable' is not assignable to type 'string & keyof TTable'.
      Type 'symbol & keyof TTable' is not assignable to type 'string'.

These last two lines of elaboration are admittedly a bit confusing - saying, essentially, that the reason assignability is denied is due to symbol not being assignable to string when really that's not the cause of the error, it's actually precisely this:
Type 'RequiredStringRow<TTable>' is not assignable to type 'OptionalSymbolRow<TTable>'.

In other words the fact that there might be symbol properties isn't the problem per se, it's that those symbol properties might have values of the wrong type.  Thus the elaboration is misleading.

@andrewbranch

Conversely, X is assignable to A & B if it is assignable both to A and to B individually

But doesn't it apply to only types where all the fields are required? Here is an example:
type A = {
  a: string;
}

type B = {
  b?: string;
}

const a: A = { a: "aaa" };
const b: B = { a: "aaa" }; // Type '{ a: string; }' is not assignable to type 'B'.

const x: A & B = { a: "aaa" }; // OK!

In this example, { a: "aaa" } is assignable to A and not assignable to B, but still, it's assignable to A & B.

I did not say “X is assignable to A & B if and only if it is assignable both to A and to B individually.” 😄 Excess property checks, common property checks, and other things that make assignability different from the type-theoretical subtype relationship do indeed make that untrue. But I’m pretty sure that even for assignability, the statement I made is true, and it was a direct answer to your question of

[when checking if RequiredStringRow is assignable to FullRow] why does it even try to type-match RequiredStringRow to OptionalSymbolRow, although it knows that FullRow is defined as RequiredStringRow & OptionalSymbolRow

—the algorithm for checking if RequiredStringRow is assignable to RequiredStringRow & OptionalSymbolRow would be to check that the former is assignable to all constituents of the intersection. It is assignable to itself, so then it must check if it is assignable to OptionalSymbolRow, and it is not, so that’s where the error elaboration starts.


Automaticly cancel charge when it goes back to 0%

Could result in a charged shot getting cancelled if the user only charges for a short duration. Won't fix.


Timing and Context can now be used as decorators

The various updates to documentation and code outside helper.py is just some suggestions. I can remove all of them if wanted.
(I initially pitched this in #1331.)

Changes made in tinygrad/:
------------------------------------------------------------
files                             insertions       deletions
------------------------------------------------------------
tinygrad/helpers.py                        3               2
------------------------------------------------------------
lines added in the tinygrad folder: 1


[FEATURE] [1.17.1] Fabric version

A fabric loader version would be useful, there are more and more fabric players and the loader is getting better and better, that's why i requested a fabric version.

Please read the readme


[WIP] compose: Fix keyboard UI with new global time widget

This should fix the keyboard issue for the enter and escape commands. This is a work in progress, and the remaining commands for tab, arrow keys and numpad (?) are not implemented. But their default implementation is cancelled because I noticed they caused some other issues. The default implemention for tab when opening the time picker caused it to switch focus to the zulip logo in the top left corner, and using the left_arrow command seems to open the message editor. The issue seems to be depending on which DOM element the user is focusing on, and there might be some inconsistency there.
When opening the timer picker with keyboard navigation, I noticed the year changes to 1910. But using container.trigger("focus") instead of container.find(".flatpickr-monthDropdown-months").trigger("focus") seems to resolve this issue.
I did not see a8c488bc565b9d7626e99c968cce5b44e633985a before pushing my changes, so some changes in there are overridden. However, I believe it is better to toggle a class (like the emoji picker does) to indicate whether the popover is active.

Can you reproduce the issues with flatpickr keyboard UI using flatpickr using just their code? I wonder if there's a bug we should report upstream.

@timabbott I have tried creating a minimal reproducible example of the bug, but I believe the problem is how the keyboard events are being propagated. Ideally, we want to catch the keyboard events and stop them from propagating to the areas like the message view, which caused the "blue box" to move. As done in this PR, overriding the keydown events from $($(instance.innerContainer).parent()) does intercept all key events for the whole flatpickr, but in doing so it will cancel all other keyboard events when calling e.stopPropagation(). Since we still want some default keyboard events for flatpickr, this might not suffice.
flatpickr does supports keyboard navigation by itself, but there is no documentation of it. I was however able to find an article on stack overflow describing how to override inherit keyboard events for the flatpickr instance. In this hook it is possible to simply call e.stopPropagation() and the keyboard events will only be forwarded to the flatpickr instance. The problem with this is that moving the highlighter (or caret) inside the flatpickr past the edge with the arrow keys will cause a new month to be selected, but this particular key event does not get intercepted for some reason (it does for the other key event handler). I will consider reporting this issue to flatpickr if you recommend doing so, but as stated, there is no documentation for even being able to handle keyboard events in flatpickr (from what I can see).
It might still possible to solve this by also overriding onMonthChange, and somehow calling e.stopPropagation() but without e since the method does not access any event. Is there a way to cancel all current keyboard propagation's in Zulip?

The keyboard navigation in the flatpickr example works well - https://flatpickr.js.org/examples/#datetimepicker-with-limited-time-range

Enter to date select and navigate to time
tab to switch between time inputs
arrow keys works well.
tab to navigate from date to time doesn't work.

We just need to catch the next tab after AM/PM selector and put it on OK button. Or Enter to press OK after user is on time input should work too.

The keyboard events should be working now, can you review it @amanag ?
A small bug still exists, as explained in my previous comment. When moving the date selector with arrow keys passed the edge the month changes, but this event will still propagated to the foreground which results in the "blue box" moving.
Another detail, as @amanagr noted, the default tab event is a bit inconsistent. It only cycles between the elements associated with the time inputs. Here I overrode the default implementation to include elements like the OK button. This implementation is based of this. However, I could not figure how to include elements like the year and month dropdownlist.

@kevjn can you split changes in this commit into different commits if the changes are independent of each other? I see a few possibly.

Thanks for the review @amanagr!
I split the changes into two different commits, I am not sure how to fragmentize it further.

The UX seems great; so if need be we can merge this, because it does fix an important bug.  I intend to squash the commits, since they don't seem separated correctly; the first commit using the has_popover attribute.
I'm not sure it's the cleanest fix, though.  I don't understand the problem this is addressing fully, but it seems possible we should be using popovers.any_active() to prevent the hotkey.js logic from firing, or the handle_popover_events system, rather than duplicating code from flatpickr.
Is that a direction you've investigated?

ui_util.convert_enter_to_click may also be useful for preventing the enter from propagating?  Not sure.

@timabbott Thanks for the review, I have considered implemented the time picker as it's own entity (like the emoji picker) but I still believe the click events will need to handled in a similar fashion. The tricky part is that we only want to relay certain keyboard events to the flatpickr instance and I am not sure how to do so without explicitly catching the keydown events associated with flatpickr instance. This kind of overloading is also done in the emoji picker. I am not entirely sure what you mean by preventing the hotkey.js logic from firing, the only dependency I have introduced with hotkey.js is a function for parsing the keyboard event; hotkey.get_keydown_hotkey(e). However, I can confirm that handle_popover_events does get called in the hotkey.js file for all keyboard events, but this is not due to my changes. I could add the time picker popover to popovers.any_active() and make use of the shared functionality like process_escape_key(e) in hotkey.js to close the popover. But I still need some extra logic before closing the popover on an escape event (like toggling the css attribute). I wouldn't say the code for tab and shift_tab is duplicated from flatpickr, since I have added support to cycle between more elements with support for the plugin (this might however be a desired change for the flatpickr community also).
I do not fully understand the critique, so I am sorry if I misinterpreted anything. To conclude, I think it is possible to make more use of shared functionality in hotkey.js, but I am not sure how to do so and if it is even worth the effort.
Regarding you second comment, I had a look at ui_util.convert_enter_to_click and it seems to be what I am effectively doing already (but uses .flatpickr-confirm instead of e.currentTarget.
export function convert_enter_to_click(e: JQuery.KeyDownEvent): void {
    if (e.key === "Enter") {
        e.preventDefault();
        e.stopPropagation();
        $(e.currentTarget).trigger("click");
    }
}

I'll squash my commits and I believe this PR is ready to merge, but as stated there is a small bug when moving the day-picker caret cross the edge.

Merged, thanks for all the work on this @kevjn!  I think given your investigation, it's probably not worth trying harder to reuse existing hotkey.js logic in this case.  As a general rule, it is generally worth substantial effort to avoid complexity on this sort of code path, because at a certain point it just becomes hard to understand/debug -- so if 90% of our popovers use popovers.any_active in hotkey.js to manage the escape key for popovers, it's nice if we can make that 100%, and that's the sort of deduplication I had in mind here. (We'd then need to figure out a way to register a hook to do that CSS adjustment whenever the flatpickr is closed).  It's also find to do that sort of thing in a follow-up if you see a good way to do it.
This was nice work -- feel free to PM me if you need help finding a good next project.
In any case, I think it's worth reporting an issue in flatpickr; they've been a fairly responsive upstream project.  Or maybe 2: That its keyboard UI should be documented and second that the keyboard UI is mostly great but you ran into the day-picker caret problem with it.
(As a sidenote, it's generally worth taking the time to express appreciation in those reports, since it's a nice thing to do for the maintainer).


With TypeScript: Property 'history' does not exist on type 'Router'

In your usage example you're passing a history prop to the <Router> component. Typescript doesn't like that because it doesn't have such prop defined.
I know we can extend the interface to include the prop but I was wondering why do you need to send a prop to the Router component if react-router-dom won't actually use it. Or is it that it's propagated down in the tree and that's what you need?
Anyway, consider adding a d.ts file extending the Router interface to allow a history prop.

Nevermind, I was importing BrowserRouter instead of Router.


drawio-image/figure directives to replace drawio

inherits from the image/figure directives so that draw.io images
behave the same as images/figures
this means that all builders will be able to handle draw.io images
without any custom code

Refer to the README for an overview of the changes compared to the old
drawio directive. See also #28.
Diagrams are now also exported to the .drawio directory beside the
document. Each diagram is exported to a separate subdirectory in this directory named by the hash of the diagram filename and export
options. The base name of the exported image file is the same as that
of the draw.io file. This has these advantages:

we don't interfere with the image/figure directive copying of image
files to the output directory
a diagram needs to be exported only once when two builders use the
same export format
more descriptive image filenames for the HTML builder

Two tests fail when the whole test suit is run at once (like on CircleCI) for some reason. I'll investigate that.

Thanks for the quick review!

If possible, could you make git recognise the move of drawio.py to old_drawio as a move, and the creation of a new drawio.py? Should be able to use git mv or somewhat (might need a rebase, and possibly multiple comments but I don't think so).

I'm afraid not. git mv doesn't do anything special; no "move" or "copy" information is stored in commits, AFAIK. Git identifies file copies after the fact, for example when you do git log -p.

I'd also prefer if the old file is old_drawio not olddrawio.

I'll change that. I also considered creating a drawio package with __init__.py (new code) and deprecated.py (old code). Let me know if you prefer that approach.

I rebased and renamed olddrawio.py.
Thanks for the push access! How about I commit bugfixes myself but still open a PR for feature additions so they are first reviewed?

I think it's probably best to keep everything to PRs, however it probably depends on the nature of the fix - a one line change vs refactoring some method would make a difference to whether it's okay (the first would be fine, the latter, probably not).
That being said, if I take 2 weeks to respond to an bugfix PR you can probably just merge it :)
I'll merge this PR when I'm next at a desktop, and will probably tag a new version on pypi.

Just a friendly reminder to merge this and create a new release. We're anxious to start using it :-)

Sorry, my bad. I'm in the middle of exams right now.
If you'd like to merge & tag a new release go for it.
[Not sure if documented but I tend to use lightweight tags on the latest commit then push both tags & commit at the same time].

*Just to be clear, I'm saying that you should merge and tag this because I won't get to it for a while.

Sorry, my bad. I'm in the middle of exams right now.

No problem. Good luck!
Merged, tagged, pushed: 0.0.10 is available on PyPI! We'll start using this now and I'll be the fixing bug we run into. Cheers!


No linter errors when build project

Hello!
I have installed<EMAIL_ADDRESS>with config   eslint: {     lintDirtyModulesOnly: false,     cache: false,     failOnError: true   }
When I call nuxt dev (with eslint problems in project) - errors appears in console and it blocks application.
However, when I call nuxt build - there are no problems and build makes success.
I need to prevent success build when eslint errors are exists.
How can I do that?

Also, lint errors in nuxt.config.js file are ignored.

Hi @evd3v
See https://github.com/nuxt-community/eslint-module/issues/60#issuecomment-919448303


User error in javascript-node-postgres template

devcontainer.json is using non-root user
and
docker-compose.yml is using root user
using the default configuration cause a error when loading the Codespace

Hi @erikalira,
I wasn't able to repro the bug with javascript-node-postgres template in a Codespace. The container was created successfully.
The comments need to updated which may have been confusing. Looks like they were missed in https://github.com/devcontainers/templates/pull/29

name: Bug Report
description: File a bug report
title: "[Bug]: "
labels: ["bug", "triage"]
assignees:

octocat
body:
type: markdown
attributes:
value: |
Thanks for taking the time to fill out this bug report!
type: input
id: contact
attributes:
label: Contact Details
description: How can we get in touch with you if we need more info?
placeholder: ex<EMAIL_ADDRESS>validations:
required: false
type: textarea
id: what-happened
attributes:
label: What happened?
description: Also tell us, what did you expect to happen?
placeholder: Tell us what you see!
value: "A bug happened!"
validations:
required: true
type: dropdown
id: version
attributes:
label: Version
description: What version of our software are you running?
options:
- 1.0.2 (Default)
- 1.0.3 (Edge)
validations:
required: true
type: dropdown
id: browsers
attributes:
label: What browsers are you seeing the problem on?
multiple: true
options:
- Firefox
- Chrome
- Safari
- Microsoft Edge
type: textarea
id: logs
attributes:
label: Relevant log output
description: Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
render: shell
type: checkboxes
id: terms
attributes:
label: Code of Conduct
description: By submitting this issue, you agree to follow our Code of Conduct
options:
- label: I agree to follow this project's Code of Conduct
required: true

Closing as stale, feel free to reopen the issue if the bug resurfaces!


Create build.yml

builds it

Thanks for adding this, this is great! Just one question on the name of dig, other than that LGTM

Codecov Report

Merging #417 (aa77dd7) into main (af6cb98) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #417   +/-   ##
=======================================
  Coverage   18.50%   18.50%
=======================================
  Files         142      142
  Lines       22035    22035
=======================================
  Hits         4078     4078
  Misses      17273    17273
  Partials      684      684

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 af6cb98...aa77dd7. Read the comment docs.


initial commit

Sets up an invenio-module.
See issue #2.

You could also add the tasks.py and cli.py file to that PR. Thematically it would fit. But we could do that also afterwards.


Windows: libomp.dll

Forgot to redeclare the dependency in #31 (see #29).

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)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] 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.

@conda-forge-admin, please rerender

Removed rerendering for this PR, because things exploded.


[BUG] FATAL  Error: Cannot find module '../../../../packages/osd-std'

What is the bug?
Found this on main branch, runtime error which says FATAL  Error: Cannot find module '../../../../packages/osd-std'
How can one reproduce the bug?
Steps to reproduce the behavior:

Build security-dashboards-plugin
Install security-dashboards-plugin tarball
Start OSD server
Open OSD, you should see error

What is the expected behavior?
No error
What is your host/environment?
Not applicable
Do you have any screenshots?
Not applicable
Do you have any additional context?
The reason is the path of imported osd-std package, it should not be a relative path '../../../../packages/osd-std', but instead from @osd/std

[Triage] Thanks for filing this issue. @cwperks Please add your thoughts on this.

This will be a 2.9 release blocker.

How did this get past CI?

Good question @wbeckler... I see the PR that introduced those imports with the relative paths passed all CI checks. @cwperks  I see you are assigned to it, please look into how this snuck past CI to make sure we catch future ones. Thanks!

Thanks for providing a fix in the description @ruanyl.  Would you be able to reproduce your build scenario from a fresh repository(ies), and then copy the full transcript of your log so we can inspect it?

In my PR, I didn't look into how this snuck past CI, I suspect it has to do with path differences from how our CI workflow is set up compared to how ruanyl performed their build.  The code that was called out is clearly wrong, but there might be more issues even with my PR.
@cwperks I'll look to your guidance on what makes sense around merging #1498.

Reopening to make sure the investigation into the root cause isn't lost

[Triage] Hi @ruanyl, thank you for filing this issue. Looks like this is being addressed by work done by @cwperks.


Considerate .gemrc when determine http_proxy.

Bundler doesn't see http_proxy written in .gemrc. So I have to set environment var corresponding to each host. I think, usually, host specific setting of rubygem is customize and adjust using .gemrc.
This patch consider http_proxy written in .gemrc when determine proxy.

Could you please add a test for this fix?

Also, anything that calls into the  Gem module should probably live in rubygems_integration.rb

I modified code and added test.

Merged via https://github.com/bundler/bundler/issues/3936.

Thank you!!


Searching for bugs, nothing to see here... oefztt

Searching for bugs, nothing to see here... oefztt

 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.


Video issues

[x] Shadowbox swiping gets laggy
[x] There may be an audio bug? Need to re-look at how we mute vids
[x] Opening videos from thumbnail opens web

Found out that not all videos have audio tracks at 00:00, which was causing our issue (we muted it because no audio, but it appeared later)


How to customise number of columns ?

Can we customise number of columns, like we can customise number of row ,
instead of showing 7 days in week, want to show the last 5 days only in a row as below screenshot

and also if I select 15 days (start :15 Jan , End : 30 Jan ) , it is showing complete month as active dates, I want only 15 days . means only those which are from start date and end date
This library is very interesting , very helpful to achieve  what we want. Thanks a lot

Unfortunately, it only has a 7 column month for now. But if someone can programatically describe for me how a column of a different number can be achieved i'l be glad to implement it.

Concerning the 15 days, it sounds like you just want to implement a date boundary?

as in my shared UI ,
Can I start the row with 15 April (instead of 1st April )?
I didn't find solution  for this.

Simply scroll to April 15.
calendarView.scrollToDate(theDateWithApril15)

but using this only we can scroll upto the segment which contains date April 15 ,
It is not making April 15 as starting element of visible segment for Week View

@iOSUser110 what is visible first is based on your scrolling mode -> https://patchthecode.github.io/CalendarScrolling/
Can you try changing your scrolling mode to .none ?

Also, i was thinking, it might be possible to show less columns.

Closing issue.
If this is still a problem for you then respond here, and I will re-open this.
More than 5 days has passed with no user-input


New version: BitFloats v0.0.3

Registering package: BitFloats
Repository: https://github.com/rfourquet/BitFloats.jl
Created by: @rfourquet
Version: v0.0.3
Commit: 745f57b1884b2dcc25009a9cf7e4b5e8d8047285
Reviewed by: @rfourquet
Reference: https://github.com/rfourquet/BitFloats.jl/commit/745f57b1884b2dcc25009a9cf7e4b5e8d8047285#commitcomment-35884413

Please discard, I will add an upper-bound for the dependency to allow auto-merging.

Ok, it's good to go now but I guess I already blocked auto-merging by the previous comment :)
[noblock]

Ok, it's good to go now but I guess I already blocked auto-merging by the previous comment :)

Yea, but you can edit it, (which I just did)
[noblock]


std.string.entab_alias_fix

make entab and entabber accept custom types with an alias this to a string
member of member function
@MartinNowak I created this against master as the 2.069 beta was already created. Input?

@rainers updated this one two

@rainers anything else missing?

LGTM

Auto-merge toggled on

thanks