Support remote server URI like a remote file system (Jupyter Lab behavior)

There's been a number of bugs/requests for this:
https://github.com/microsoft/vscode-python/issues/9065
https://github.com/microsoft/vscode-python/issues/9043
https://github.com/microsoft/vscode-python/issues/7956
https://github.com/microsoft/vscode-python/issues/9620
I believe we could implement a remote file system for a remote server URI and then we'd behave the way customers want (and incidentally do the same thing Jupyter Lab does here)

Noting two of the major pain points / expectations from talking to our users:
1. While executing nb with a remote kernel, refer to local files
This is especially a pain point for developers in DS/ML teams that test code locally before connecting to a remote kernel for a scalable / cloud dev environment that provides powerful (or more specific) compute & persistent storage. In these cases, users want and need fast access to notebooks and other related work artifacts on the local file system so that they can "continue" their work. The confusion in the VS Code UI is that it only shows files in the local system (not the one in remote kernels), even though the users cannot access them when they're connected to a remote kernel. Here are verbatims as examples of user frustrations:

If you want to for example call a function from another python file (foo.py) from that notebook (local-notebook.ipynb), the remote kernel can't access local files. The remote kernel can access other files saved on the remote notebook server. The problem is that local (Python) files are not synced with the remote Jupyter server instance, for the remote Python interpreter (kernel) to access them (vscode-jupyter#1601)

wirte csv in remote server save the file in remote server, not in local file. If there is a download tool would be very useful
This is also a pain point when debugging a local notebook using remote kernel as well:

Debugging notebooks when using a ssh remote server doesn't work properly. When trying to Run by line, a lot of times it doesn't stop at any line. Also 'Step into' almost never work for me.

2. While executing nb with a remote kernel, navigate remote files through the UI
The current way of exploring remote files in VS Code is not very UI-friendly when connected to a remote kernel. Users would have to use cell magics through the os library, which isn't the best experience (and also confusing because the output (obviously) doesn't match what's shown on the VS Code file explorer). Being able to access remote files is not only common in professional DS/ML teams, but also in academics where educators set up and manage multiple Jupyter servers for class. This is actually something that other products do by default. DataSpell is a desktop-based product and an example of this:

Though, other web-based products do this as well (mostly by default, since you already have to be connected to a remote kernel when loading the nb UI)
Related to this, is the ability to see and manage the Python environment on the remote kernel without having to SSH into the server, and some verbatims to go with this ask:

Having some capability see the python environment on the other side would avoid having to create that environment locally just to resolve dependencies for my code..

As a new capability for the notebook experience in VS Code, I would like to see integration with remote file browsing

Proposals for exploration:

We should explore enabling users to refer to local files from the nb without having to upload them to the remote server. This way, users would not need to make any potential code changes to refer to the right file structure. (Open q: when user types pd.read_csv('./data.csv'), how would users indicate that they're referring to local file vs. remote one?)
We could also explore a smooth "continue on" like transition (e.g. automatic sync) UX where we'd walk the user through uploading their local files to the remote server (automating most / obvious parts of this flow). The file explorer would then "refresh" to show the latest local files that have just been uploaded to remote

Imagine a scenario where a Jupyter Lab (or hub) user just sends a URI to a VS code user. It opens the entire workspace from that URI.

Precisely. It would be very helpful if we can have something like this.

Is there any update on this? At a bare minimum, is there a way to open remote files through an ipython terminal?

any news about the progress about this feature?

Notes:

Discoverability of VS Code Server & Tunnels

In a number of issues I've suggested the above and users have been happy with this.

VS Code Serer/Tunnel is not an option

Users do not have access to install additional software

Users would like to just view/manage remote files

Solution(s)

KISS - View/Manage remote files via file explorer (using the FileSystemProvider API)

Focus on just the remote file system view, without syncing,
Ability to view local files on the remote server will not be part of this (i.e. syncing files is out of scope for now)

Challenges

Discoverability

How will users know that they can view files on the remote server?

Will a simple command (in command palette) suffice?

How about interatinmg Manage Kernels view, turn this into Manage Jupyter Servers

Here users can manage local kernels/ remote kernels
They can also see the remote files as part of the tree view
They can see icons that will allow them to mount the files system provider as well
Given that some users already know about the this UI, it is easily discoverable, similar to Docker panel

Any update on this feature? Really need it!!

+1

This could be a real game changer.

Still waiting for this, none of the recommendation do this. We want to open a remote file just like we do in browser just with IDE benefits.


json response type

Sails version: 1.0.2^
Node version: 10.10
NPM version: 6.4.1
DB adapter name: N/A
DB adapter version: N/A
Operating system: OSX 10.13.6
Hi,
I wrote a simple action which returns the JSON as response, but I got this message.
The `json` response type will be deprecated in an upcoming release.  Please use `` (standard) instead (i.e. remove `responseType` from the `success` exit.)
<- GET /api/v1/pet/list                  (1ms 200)

Is there anyway to fix this or is there any better way to do this ? Thanks !

Hi @zhoub,
I would consider posing your question to the Gitter community. If your not already a member, Gitter has Sails.js most active members and someone in there may be able to help you along with your Sails app!
https://gitter.im/balderdashy/sails

In sails 1.0 the default responseType is json, so in this case you actually don't have to specify a response at all and the error should go away.


NowLive/NewVideo Feature

Proposal:
Proposal written by Milchreis#8855
What is the title of your proposal?: NowLive/NewVideo Feature
Is it a suggestion for the website or for the bot?: Bot
Explain your proposal more accurately (It's best to give as much information as possible, so that we can implement the proposal better): If a streamer goes online/uploads a video, the bot sends a message with the title of the streamer/yter, of the video and the video url in a channel
Why we should add this feature?: Because not many bots have this feature
ReportID: 36

➤ LenoxBot commented:
Approve:
I agree with Dadi
JUV#4292

➤ LenoxBot commented:
Approve:
why not? It's a good feature for a new command
Dadi#7808

➤ LenoxBot commented:
Approve:
Nice feature, but admins should be able to change the message (formatting, sentences, etc.)
KeinEmxl#3887


Unterminated quote when string contains some chars

folowing lines cause angular to show error

Error: $parse:lexerr
Lexer Error: Unterminated quote at columns ... ['abc] in expression [foo'abc].
but of course these two don't

(escaping doesn't help)
EDIT: this works well

Which version of Angular are you using ? (I can't reproduce it on 1.4.)
A live reproduction would also help.
BTW, make sure to disable any extensions that might fiddle with Angular expressions (e.g. Batarang).

hi gkalpak
it's v1.3.15
live preview not possible :(
digging in the issue i noticed strange thing
when i add ng-click as above using jQuery with .attr() then error occurs
but when i add it by .data() then it doesn't occur

(what)

that was my reaction ;)
btw: switching off batarang "fixes" the problem

The code for readString() has only changed superficially between 1.3.15 and master (https://www.diffchecker.com/lnygm32z), so any impact there likely causes the same issue in master.

btw: switching off batarang "fixes" the problem

Then it's worth filing on batarang

will be done asap
thanx guys for your help ;)


fix -Wdocumentation warnings introduced in Xcode 8.3.2

when using CocoaPods by treating the core+sync headers as system headers.
Fixes #4853.

CocoaPods CI jobs all passed, the 3 CI failures are unrelated and being investigated.

I've also confirmed that both the iOS & macOS versions of RealmTasks no longer display these warnings when pulling the Realm & RealmSwift pods from this branch by specifying this in the Podfile:
pod 'Realm', git: 'https://github.com/realm/realm-cocoa.git', branch: 'jp-fix-cocoapods-docs-warnings', submodules: true
pod 'RealmSwift', git: 'https://github.com/realm/realm-cocoa.git', branch: 'jp-fix-cocoapods-docs-warnings', submodules: true


Multiport

I merged the two units tests for pbitcell so there is only one unit test now that runs two checks (on 2-writes 2-reads and 2-writes 0-reads). I created a unit test titled 05_pbitcell_array_test.py that tests the bitcell_array using pbitcell. Pbitcell inherently uses more nets than the 6T bitcell, so I altered bitcell_array.py to account for those additional nets. Right now it's passing DRC and LVS for the bitcell_array, but the alterations I made to pbitcell to get the cells to align correctly are messy right now. So I need to go through the code and clean it up for clarification. Also bitcell_array only works with a pbitcell with 1 write port and 1 read port. I need change that as well to make it modular. I just wanted to see that it would pass DRC and LVS for the moment, which it does.

Merge into dev please. :)

You changes must not break test 05_bitcell_array_test.py. Please ensure that the other unit tests still work.

Sorry, I could have sworn I merged into dev. I'll do another pull request
when I'm near my computer. I made sure that my changes to bitcell_array did
not affect the original functionally. 05_bitcell_array.py still passes.
On Mar 6, 2018 5:33 PM, "Matt Guthaus"<EMAIL_ADDRESS>wrote:
You changes must not break test 05_bitcell_array_test.py. Please ensure
that the other unit tests still work.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/VLSIDA/OpenRAM/pull/37#issuecomment-370991026, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AVyV3psOOB4SYMddnnWsPx3qIyVz917Iks5tbzjQgaJpZM4SftQY
.


#8 Update README

Resolves #8

@fedorpashin thank you for your Pull Request. I'll assign someone to review it soon.


Where is BUILD_STATUS

In your jenkins-changeLog-dingtalk-notifications/buildNotification.py), I didn't see where BUILD_STATUS is declared.
So, how you compile buildNotification.py successfully?
My compilation failed because of that.

I got it from Jenkins#get_build_info(xxx)#result.


CLOUD-893 handle empty ambari docker container environment variables

@akanto please review!

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/1480/


Help for (1h)CANNOT

Hi Augustine,
This sign had been marked to be hidden, but since it is the only occurrence of this sign,
it came back unhidden.  Could you please remove this from the Sign Bank?  We want to
retain it for the DAI sentence-level searches...  THANKS!

PS. Isn't this a case that should have been detected by the algorithm you developed, to identify signs where different things were happening on the 2 hands, including cases where that happens in the primary (/only) occurrence ??

PS. Isn't this a case that should have been detected by the algorithm you developed, to identify signs where different things were happening on the 2 hands, including cases where that happens in the primary (/only) occurrence ??

(1h)CANNOT is still showing up; it is not hidden, although it was marked to be hidden.  This issue still needs to be addressed.

This has been resolved on dev1.cs


Question about how to create pathless route with react-router-config

This is actually a question:
How do I achieve routing like this using react-router-config?

const routes = (<Route component = { SomeComponent }>
    <IndexRoute component={Index}/>
    <Route name='Sample' path='sample' component={Sample} />
</Route>)

<Router>
    <Route name='Home' path='portal' component={App}>{routes}</Route>
    <Route name='Login' path='login' component={Login}>
 </Router>

This is a bug tracker, not a support system. For usage questions, please use Stack Overflow or Reactiflux where there are a lot more people ready to help you out. Thanks!


[bug] Ctrl+F to enter command line window breaks inc-rename when input_buffer_type = "dressing"

I like to use dressing with insert_only = false, but that doesn't work with inc-rename.nvim (see https://github.com/smjonas/inc-rename.nvim/issues/36). As a workaround, I tried using Ctrl+F to use the command line window in order to edit my command before executing it.
I found that that works with input_buffer_type = nil, but not with input_buffer_type = "dressing".
Behavior with input_buffer_type = nil
https://github.com/smjonas/inc-rename.nvim/assets/16181067/7cda752a-a6ab-49d9-8034-a99a5066123b
Behavior with input_buffer_type = "dressing"

When I exit the command line window, the Dressing input remains open

This happens regardless of whether I ran the IncRename <word> command or I exited the command line window without executing the command

Also, inc-rename.nvim throws an error (pasted below) when exiting the command line window without running a command

https://github.com/smjonas/inc-rename.nvim/assets/16181067/5150d9c6-2b1d-437e-87c5-e02fdcfcf668
CmdlineLeave Autocommands for "*":
Vim(append):Error executing lua callback: .../share/nvim/lazy/inc-rename.nvim/lua/inc_rename/init.lua:139
Vim:E11: Invalid in command-line window; <CR> executes, CTRL-C quits^@stack traceback:^@^I[C]:
in function 'nvim_set_current_win'^@^I.../share/nvim/lazy/inc-rename.nvim/lua/inc_rename/init.lua:139:
in function <.../share/nvim/lazy/inc-rename.nvim/lua/inc_rename/init.lua:132>

Fixed in https://github.com/stevearc/dressing.nvim/issues/99, thanks @stevearc!


some common css like no-padding?

I'm submitting a ...
[ ] bug report
[X ] feature request
[ ] question about the decisions made in the repository

Do you want to request a feature or report a bug?

What is the current behavior?

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via
https://plnkr.co or similar (you can use this template as a starting point: http://plnkr.co/edit/tpl:AvJOMERrnz94ekVua0u5).

What is the expected behavior?

What is the motivation / use case for changing the behavior?

Please tell us about your environment:

Angular version: 2.0.0-rc.X
Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

.noPadding {
padding: 0;
}
In the theme or in the app.component.scss and you can use it in your html by simply adding the class. Dont think this has to be in the standard project.


Customize the yum repository

Adding the option to change baseurl and whether to enable
the repository or not (In case there is already a repository with opendaylight)

@dfarrell07 Can you please check my the job failed?

Can you please check my the job failed?

Yeah, was just looking at that. Not sure off-hand, digging.
Any chance you can add Beaker/rspec tests and docs for this?

@dfarrell07 Thanks. Just did it but still fails - https://travis-ci.org/dfarrell07/puppet-opendaylight/builds/211112534

@itzikb #138 seems like it may provide most/all of the behavior you need. Would just disabling repo management be basically what you're looking for? If no, should be minor changes to expose rpm_enable_repo and add rpm_baseurl on top of the refactor.

@dfarrell07 I agree. #138 seems to better solve the issue of disabling the repository.
We also need to to the change as you suggested.

@dfarrell07 , I have trouble with the new opendaylight::repos tests:
https://travis-ci.org/dfarrell07/puppet-opendaylight/builds/213030036
If I understand correctly it's using the class directly. Can you help?
Thanks


Added a config option to disable the default http_check headers

Simple option to disable the default http_check headers.

Looks great, thanks a lot @eredjar for contributing.
I just added a few nitpicks. Please let me know what you think.

Could you let us know a little more about the motivation behind this feature?

We have some API calls that are really picky about the headers that we send. After some digging we found that "application/x-www-form-urlencoded" header causes a 401 with some endpoints/API.

Hi @yannmh,
I don't know if this the correct place to ask this. But is there a reason why the ssl check within the http_check returns a status(OK,NOK,...) instead of a metric with the remaining days ?
Kind regards
eredjar

Thanks for the last modifications @eredjar. Let's merge 🙌

But is there a reason why the ssl check within the http_check returns a status(OK,NOK,...) instead of a metric with the remaining days ?

I can't think of a specific reason for that. I believe it's simply an innocent choice made by the feature's contributor, to have the thresholds directly set in the agent configurations rather than in a  Datadog monitor.

EDIT: Datadog "warning" alerts on metric monitors were not available at the time of this feature.  Using service checks allowed then to differentiate warnings from alerts.

thanks for the additionele information and the merge. I will contact the support desk if there's a possibility to add/convert this into a metric.


hero5black  remains in pairing mode

@konradIT:
I am on Ubuntu 18.04 on ondroidC2 with GoProHero5black:
1.) I can pair (bluettoothctl) and connect (gatttool) correctly without any problems!
2.) I can connect to my GpH5b wifi correctly without any problems (wpa2psk, 2,4 MHz)
But the cameradoesn't seem to accept this connectivity and NEVER leaves the paring mode! So it finally ends up in breaking up the pairing attempt and killing the wifi AP.
No matter what I try, no successfull paring on the camera side....

It never leaves the pairing mode because you need to execute the following URL: http://<IP_ADDRESS>/gp/gpControl/command/wireless/pair/complete?success=1&deviceName=DESKTOP

great thanks so much

Same problem but I don't understand the solution.
After 8 hours of searching for the solution, I think it's time to ask for help.
I want to connect my Hero 5 Black to my Raspberry Pi Zero W. I cannot have the camera completing the pairing.
I intend to use Bluetooth to wake up the camera and shoot photos, I'm not planning to use the Wi-Fi at all.
How can I execute the command posted above?
This is the order of my commands:
advertise on
trust XX.XX.XX.XX
pair XX.XX.XX.XX
connect XX.XX.XX.XX

Then the prompt on my Pi shows [GoPro 6092] but the camera remains in pairing mode.
Thanks.


fix: enabling deleted grafana datasources to be recreated

@sthaha do you think we want an e2e test here?

@sthaha do you think we want an e2e test here?

I agree, we should test if operator restores datasource if it is modified or deleted. I suspect that given then current code that it might crash if the datasource is deleted.
@prashbnair  have you tested this?

I agree, we should test if operator restores datasource if it is modified or deleted. I suspect that given then current code that it might crash if the datasource is deleted.

Yes this has been tested.

I think should take the opportunity to fix this name collision as well.

Can we do this in  a separate PR?

Can we do this in a separate PR?

Sure thing :-)

@prashbnair , Could you please also ensure that deletion a namespace that contains monitoring-stacks also cleans up their associated grafana-datasources ?

As discussed, it would be nice to have all reconciliation issues sorted in a single or multiple PRs

@sthaha I will address the clean up of grafana data sources when the monitoring stack or namespace is deleted as a separate PR.


XLA "resnet 50" style example crash during graph building

Note: The test code below was cobbled together from various un-credited sources.
The example crashes, during the building of the reduce_mean.   It fails with quite a large stack, maybe some sort of stack overflow?  Without the last two 'block's (marked with #*****) the compilation succeeds.
Perhaps it is as simple as it failing on my laptop (OS/X, 16GB RAM).
import tensorflow as tf
import numpy as np

def _get_variable(name, shape, initializer, dtype=tf.float32):

  return tf.get_variable(name,
                         shape=shape,
                         initializer=initializer,
                         dtype=dtype)
def inference(x):

  with tf.variable_scope('scale1', use_resource=True):
    x = conv(x, 7, 2, 64)
    x = tf.nn.relu(x)

  with tf.variable_scope('max_pool', use_resource=True):
    x = max_pool(x, ksize=3, stride=2)

  with tf.variable_scope('scale2-1', use_resource=True):
    x = block(x, 1, 64, 256)

  with tf.variable_scope('scale2-2', use_resource=True):
    x = block(x, 1, 64, 256)

  with tf.variable_scope('scale2-3', use_resource=True):
    x = block(x, 1, 64, 256)

  with tf.variable_scope('scale3-1', use_resource=True):
    x = block(x, 2, 128, 512)

  with tf.variable_scope('scale3-2', use_resource=True):
    x = block(x, 1, 128, 512)

  with tf.variable_scope('scale3-3', use_resource=True):
    x = block(x, 1, 128, 512)

  with tf.variable_scope('scale3-4', use_resource=True):
    x = block(x, 1, 128, 512)

  with tf.variable_scope('scale4-1', use_resource=True):
    x = block(x, 2, 256, 1024)

  with tf.variable_scope('scale4-2', use_resource=True):
    x = block(x, 1, 256, 1024)

  with tf.variable_scope('scale4-3', use_resource=True):
    x = block(x, 1, 256, 1024)

  with tf.variable_scope('scale4-4', use_resource=True):
    x = block(x, 1, 256, 1024)

  with tf.variable_scope('scale4-5', use_resource=True):
    x = block(x, 1, 256, 1024)

  with tf.variable_scope('scale4-6', use_resource=True):
    x = block(x, 1, 256, 1024)

  with tf.variable_scope('scale5-1', use_resource=True):
    x = block(x, 2, 512, 2048)

  with tf.variable_scope('scale5-2', use_resource=True):  #*****
    x = block(x, 1, 512, 2048)

  with tf.variable_scope('scale5-3', use_resource=True): #*****
    x = block(x, 1, 512, 2048)

  x = tf.reduce_mean(x, reduction_indices=[1, 2])

  with tf.variable_scope('fc', use_resource=True):
    x = fc(x, 1000)

  return x

def block(x, first_stride, internal_filters, final_filters):
  shape_in = x.get_shape()

  shortcut = x

  with tf.variable_scope('a', use_resource=True):
    x = conv(x, 1, first_stride, internal_filters)
    x = tf.nn.relu(x)

  with tf.variable_scope('b', use_resource=True):
    x = conv(x, 3, 1, internal_filters)
    x = tf.nn.relu(x)

  with tf.variable_scope('c', use_resource=True):
    x = conv(x, 1, 1, final_filters)

  with tf.variable_scope('shortcut', use_resource=True):
    pad = int(x.get_shape()[-1] - shape_in[-1])
    kernel = np.reshape(np.concatenate((np.identity(shape_in[-1], dtype=np.float32),
                                        np.zeros([pad, shape_in[-1]]))),
                        [1, 1, shape_in[-1], final_filters])

    shortcut = tf.nn.conv2d(shortcut,
                            kernel,
                            [1,first_stride,first_stride,1],
                            padding='SAME')

  return tf.nn.relu(x + shortcut)

def fc(x, num_units_out):
  num_units_in = x.get_shape()[1]
  weights_initializer = tf.truncated_normal_initializer(stddev=0.01)

  weights = _get_variable('weights', shape=[num_units_in, num_units_out],
                          initializer=weights_initializer)
  biases = _get_variable('biases', shape=[num_units_out],
                         initializer=tf.constant_initializer(0.0))

  x = tf.nn.xw_plus_b(x, weights, biases)

  return x

def conv(x, ksize, stride, filters_out):

  filters_in = x.get_shape()[-1]
  shape = [ksize, ksize, filters_in, filters_out]
  initializer = tf.truncated_normal_initializer(stddev=0.1)

  weights = _get_variable('weights', shape=shape, initializer=initializer)
  return tf.nn.conv2d(x,
                      weights,
                      [1, stride, stride, 1],
                      padding='SAME')

def max_pool(x, ksize=3, stride=2):
  return tf.nn.max_pool(x,
                        ksize=[1, ksize, ksize, 1],
                        strides=[1, stride, stride, 1],
                        padding='SAME')

#
# Main code
#

with tf.device("/job:localhost/replica:0/task:0/device:XLA_CPU:0"):
  # Inputs
  x = tf.placeholder(tf.float32, shape=[2, 224, 224, 4])

  # Inference
  logits = inference(x)

sess = tf.InteractiveSession()

sess.run(tf.global_variables_initializer())

training_data = np.zeros([2, 224, 224, 4]);

sess.run(logits, feed_dict={x: training_data})

sess.close()

I know we're actively working on XLA/resnet, @tatatodd might be able to add some color on this.


chore(redis): edit limit coverage

Codecov Report

Merging #8 (dcb0a2d) into master (2bce770) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master        #8   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           49        49
  Lines          383       383
  Branches        38        42    +4
=========================================
  Hits           383       383

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 2bce770...dcb0a2d. Read the comment docs.


Add packagemanifest:aggregated-apiserver-clusterrole

Fixes https://github.com/operator-framework/operator-lifecycle-manager/issues/577

/assign @ecordell @njhale

@sttts Thanks for taking the time to add this. I should note that we also need to update the helm chart deploy/chart/templates/0000_30_13-packageserver.yaml to enable this change for future releases.
/approve
/ok-to-test

Closed in favor of #580.


Add option to pass yaml object instead of path

This pull request is coming along with this pull request: https://github.com/apigee-127/swagger-tools/pull/253

Hey Gilad,
Unfortunately, your PR breaks the build, so I can't accept it presently. Also, all functions must include unit tests to ensure they are operating correctly.
But first, can you also explain why the changes in functionality you are proposing in this and the related PRs are necessary?
Thanks!
Scott

Hi,
Thx for your response.
My yaml is separated to different files (because i have a lot of API, and i can't put them all in one file).
I used this technique http://azimi.me/2015/07/16/split-swagger-into-smaller-files.html to seperate the yaml parts to different files and i'm concatenating them in run time using the code in the end of this post.
because my yaml is loaded in runtime i have to somehow pass it to swagger runner and i can't just pass a path to a file.
i started to create an example for advanced using of swagger-node using swagger-express-mw (which uses this technique and also separate the controller to different location (like i have in my real project) and more stuff.
you can see my example here (it's in progress so no documentation yet but it's pretty easy to under stand. and it won't work with your version of runner, but only if you use my forked version and also my forked version of swagger-tools)
https://github.com/GiladShoham/SwaggerExpressAdvancedExample
about the tests, it will be great if you can help me with this, if not, ill try to fix them in a few days.
Thx a lot.
p.s in this example you can also see the reason beyond the https://github.com/theganyo/swagger-node-runner/pull/8

The latest version of swagger-node-runner has been updated to the latest swagger-node module - which should resolve your refs without you having to concatenate the yaml files yourself.

Hi,
I will check this, but i still think it a great feature because of 2 reasons:

you can never know where is the swagger of the user come from, maybe someone generate it from other spec in run time or someone can retrieve it from his DB or bring it in run time via HTTP from another server, so it's great option to pass it in.
i have also added the option to pass different path of the yaml file, which is also a great feature because right now the yaml have to be in specific path in the project.

Last thing, maybe it worth to ask the people who maintain the swagger node to make sure that the swagger-express-mw is using the last version of the runner.
Have a nice day

FYI, this should work in the new beta: https://github.com/swagger-api/swagger-node/issues/294
set: config.swagger = { your object }


2.0.0-beta.4

Bump version so it's easy to pickup recent changes

2.0.0-beta.4 was already released, but from a feature branch. That branch is now merged, and 2.0.0-beta.5 was pushed to npm with all the recent changes.


Network documentation 2.0 (In progress)

-Files changed.
Comments for ClientHandler.java Finished.
Comments for MetricRecordingHandler.java Finished
Signed off.
engiValk.

Contains
Just contains networking comments and javadocs.
How to test
No testing.

Hooray Jenkins reported success with all tests good!

closing this PR due to lack of response.

To add to Pollends comment, if you at any stage wish to continue working on this just reopen the PR and we can work out the best way to continue these changes.
:)
Documentation is always welcome.


Fixed non-working link

Hi @wytsevisser, thanks for your contribution!
In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes.

You did it @wytsevisser!
Thank you for signing the Contribution License Agreement.

thanks for this.  i merged this to titan11 branch as development is focused there at the moment.


setup Github actions to autorun tests

Use Github actions to provide continuous integration

Initial pull request does not work since it doesn't import any of the libraries. It does work locally. It is also run automatically when items are pushed.

Simple test working to check a certain set of api queries against what they should be. I had to remove some libraries from the requirements.txt file to get the test to run as it couldn't find the file when testing.


Directory permission

Please ensure that the SDK and/or project is installed in a location that has read/write permissions for the
current user.
Please, help me with this issue. It is confusing!

@RustambekSafarov
When opening an issue next time, please try to provide all or some of the information indicated in the template so that we'll have enough details to work with.

Issue Template
If you are looking for support, please check out our documentation
or consider asking a question on Stack Overflow:
- https://flutter.dev/
- https://api.flutter.dev/
- https://stackoverflow.com/questions/tagged/flutter?sort=frequent

If you have found a bug or if our documentation doesn't have an answer
to what you're looking for, then fill our the template below. Please read
our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports

Steps to Reproduce

Please tell us exactly how to reproduce the problem you are running into.

Please attach a small application (ideally just one main.dart file) that
reproduces the problem. You could use https://gist.github.com/ for this.

If the problem is with your application's rendering, then please attach
a screenshot and explain what the problem is.

1. ...
2. ...
3. ...

Please tell us which target platform(s) the problem occurs (Android / iOS / Web / macOS / Linux / Windows)
Which target OS version, for Web, browser, is the test system running?
Does the problem occur on emulator/simulator as well as on physical devices?

Target Platform:
Target OS version/browser:
Devices:

Run your application with `flutter run --verbose` and attach all the
log output below between the lines with the backticks. If there is an
exception, please see if the error message includes enough information
to explain how to solve the issue.

Run `flutter analyze` and attach any output of that command below.
If there are any analysis errors, try resolving them before filing this issue.

Finally, paste the output of running `flutter doctor -v` here.

Please ensure that the SDK and/or project is installed in a location that has read/write permissions for the
current user.

Based on this message log, I see there's an open issue addressing the case you described #70216.
Closing this issue as a duplicate, so please follow up on it for further updates. Thank you!


Truncation takes longer and longer

I had noticed that my specs are getting very slow, and started investigating strategies. Apparently the more you truncate, the longer it takes. This behavior seems very strange:
irb(main):009:0> t = Time.now; 10.times{ DatabaseCleaner.clean_with :truncation }; Time.now - t=> 1.023764
irb(main):010:0> t = Time.now; 10.times{ DatabaseCleaner.clean_with :truncation }; Time.now - t
=> 0.793042
irb(main):011:0> t = Time.now; 10.times{ DatabaseCleaner.clean_with :truncation }; Time.now - t
=> 0.829454
irb(main):012:0> t = Time.now; 10.times{ DatabaseCleaner.clean_with :truncation }; Time.now - t
=> 0.870453
irb(main):013:0> t = Time.now; 10.times{ DatabaseCleaner.clean_with :truncation }; Time.now - t
=> 0.940325
irb(main):014:0> t = Time.now; 10.times{ DatabaseCleaner.clean_with :truncation }; Time.now - t
=> 1.03202
irb(main):015:0> t = Time.now; 10.times{ DatabaseCleaner.clean_with :truncation }; Time.now - t
=> 2.176829
irb(main):016:0> t = Time.now; 10.times{ DatabaseCleaner.clean_with :truncation }; Time.now - t
=> 2.466992
irb(main):017:0> t = Time.now; 10.times{ DatabaseCleaner.clean_with :truncation }; Time.now - t
=> 2.341618
irb(main):018:0> t = Time.now; 10.times{ DatabaseCleaner.clean_with :truncation }; Time.now - t
=> 2.4591
irb(main):019:0> t = Time.now; 10.times{ DatabaseCleaner.clean_with :truncation }; Time.now - t
=> 3.078432
irb(main):020:0> t = Time.now; 10.times{ DatabaseCleaner.clean_with :truncation }; Time.now - t
=> 3.056646
irb(main):021:0> t = Time.now; 10.times{ DatabaseCleaner.clean_with :truncation }; Time.now - t
=> 3.314674
irb(main):022:0> t = Time.now; 10.times{ DatabaseCleaner.clean_with :truncation }; Time.now - t
=> 3.514017
irb(main):023:0> t = Time.now; 10.times{ DatabaseCleaner.clean_with :truncation }; Time.now - t
=> 3.822936
irb(main):024:0> t = Time.now; 10.times{ DatabaseCleaner.clean_with :truncation }; Time.now - t
=> 4.109673

I tried this on another app, and did not see the same behavior. Probably something funny about my app...

What database are you using?

How did you discover this?  Did you see it materialize in your tests?  I ask because this issue could explain some of the problems I'm finding in my tests.

Using PostgreSQL.
I noticed that truncation was much slower than transaction. So, I started benchmarking truncation, transaction and deletion.

Hmmm I'm using MySQL and we're getting odd test failures with parallel_tests on cucumber integration specs.


OpenAI http client

@aacebo please add more details to the task

One question to this task: can we wrap the OpenAI package to provide strong type, instead of writing from scratch?

This work adds an Http Client to the codebase for handling interactions with OpenAI. I explored using their python SDK https://github.com/openai/openai-python but it was nearly impossible to use for a few reasons:

it does not come with typings
it is a single instance global implementation, our SDK uses multiple instances since you could potentially have a bot that calls many differnet LLM's, like Azure OpenAI, OpenAI, and Bard. Using their SDK would require us to not only add typings for it but also it would not support a bot that had to call two different OpenAI sources like Azure and OpenAI.


chore(all): Full support of AGP 8

Description
This PR is a replacement for #11318 as it was agreed in that PR. Opened another PR as don't have access to push anything to that other fork used to create #11318.
Summary of changes and things to note:

Added required  buildFeatures block in all build.gradle files for support of AGP 8.
Dropped step to install Java from CI as it is pre-installed on Github runners: https://github.com/actions/runner-images/blob/main/images/linux/Ubuntu2204-Readme.md UPD: Looks like workflow can't pick Java 17 on its own even though it is installed, so brought back the Java setup step.
Dropped Jetifier everywhere as it is not needed and negatively influences build speed: https://adambennett.dev/2020/08/disabling-jetifier/
Switched to new syntax to declare min, target and compile SDKs (e.g. instead of compileSdkVersion use compileSDK). Note, this would require projects using plugins to have at least AGP 7 as it mentioned here: https://developer.android.com/about/versions/13/setup-sdk
Updated AGP everywhere to 8.1.2 and Gradle wrapper to 8.3. Considering that some plugins still had 3.x versions of AGP after this PR build speed should improve for such packages.
Bumped minSDK to 19 for all plugins, because with current min Flutter version 19 is minimally supported anyway: https://docs.flutter.dev/reference/supported-platforms#deploying-flutter
Dropped last mentions of jcenter() as it is not reliable and replaced with mavenCentral().
Changed declaration of Kotlin dependency to not mention -jdk7 or -jdk8 as it is not needed for quite a long time already and since release 1.8.x is the default required way of declaring Kotlin dependency.
I didn't update Kotlin as it was done in that other PR, because it would bring only issues to most projects. See https://github.com/fluttercommunity/plus_plugins/issues/2251 and https://github.com/juliansteenbakker/mobile_scanner/issues/729 for more information on the issue.
Updated annotation Android dependency in all plugins.
Removed redundant gradle folders in packages where they are not needed.
Did some formatting for build.gradle files so they have the same position of blocks across plugins as it was confusing to update code in different places for every plugin.

Related Issues
Closes #11266
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (melos run analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change.
[x] No, this is not a breaking change.

@vbuberen - thank you for the PRs 🥳 . I will take a look at them next week 😄

@vbuberen - The CI is failing because of the need for compileSdkVersion here: https://github.com/firebase/flutterfire/actions/runs/6533992367/job/17740279394?pr=11699#step:14:62
I've built it locally and it doesn't work with compileSDK but does build with compileSdkVersion 🤔

I've built it locally and it doesn't work with compileSDK but does build with compileSdkVersion 🤔

I will check it out a bit later today.

I made a typo there 🤦🏻
It should be compileSdk not compileSDK


Fix bug validating 'required' paramas in Routerts

Currently, the builtin validateParametersmiddleware that comes with express-router-factory check against all fields/properties of the Mongoose-Schema that have some type of validation. If any of those fields are no passed in a POST request the POST will fail.
It is necessary to refactor this middleware in order to check only for the required fields.

The PR Jesuarva fix router issues #38 fix this issue.


Feat/pagination

This PR...
Changes

Fixes

Checklist

[x] tested locally
[ ] added new dependencies
[ ] updated the Swagger API docs
[ ] updated the Postman collection
[ ] added a test
[x] linter passes
[x] format check passes

Fixes #

Thank you, Munir! Please use a different pull request for the pagination feature.
It will help us to manage the features independently


Migrate away from request

Seeing
warning matrix-js-sdk ><EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142

over and over is getting a bit tiresome.

https://github.com/Sorunome/matrix-js-bot-sdk uses got as backend

Seems as good as any :)

fwiw you can replace the request used. The motivation for an issue should also be the fact that it's deprecated, not that it's annoying to see warnings - install warnings are a very common and expected thing.

Yes, that wasn't meant to be taken seriously as the reason :p


Remove mutexes from ECP hardware acceleration

Protecting the ECP hardware acceleratior with mutexes is inconsistent with the
philosophy of the library. Pre-existing hardware accelerator interfaces
leave concurrency support to the underlying platform.
Fixes #863

Thanks @yanesca ! LGTM

Reviewed, approved, tested and merged.


Readme/Spec: Revive grammatical right associativity

Consider bringing back right associativity so that x |> (f |> g) is valid. x |> f |> g would still also be valid. This may make any future short-circuiting conditional pipeline operator like with x ?> f |> g—as well as monadic binding, Kliesli arrows, or other sorts of higher-order composition—easier to explain. Right associativity was  first introduced in 22547070ba5ee39f72be7bab2a9d9ffe07c2f906  and removed in 90ada7934d5caa885fdd77ad6462b6395c784ff5.

Even though |>’s grammar is right associative, it is, practically, left associative.
x |> f |> g |> h
(x |> f) |> g |> h // Still equiv. to first line.
x |> f |> (|> g |> h) // Still equiv. to first line.
x |> f |> (g |> h) // Still not equiv. to first line.

x |> f ?> g |> h // Hypothetical short-circuiting conditional pipeline.
(x |> f) ?> g |> h // Equiv. to first line.
(x |> f) ?> (|> g |> h) // Equiv. to first line.
(x |> f) ?> (g |> h) // Not equiv. to first line.
((x |> f) ?> g) |> h // Not equiv. to first line.

Spec updated. Explainer left alone: In actual practice, it acts with left associativity. The difference will only occur with other sorts of binding like with a short-circuiting conditional pipe operator, and that can be explained its own way if the time comes.


Add

Config for reward ?

You can configure commands that can give rewards.

Ok

the ids are compatible ?

Yes, "give" supports item ids.


Incompatibility with at.js in recent versions

I am using at.js alongside emojionearea, by enabling it on the contenteditable editor of emojionearea. This worked fine with emojionearea 3.2.6 (note that I have autocomplete disabled for emojionearea. I haven't tried with it enabled). When upgrading to 3.4.1, this does not work anymore, because emojionearea removes the span used by at.js to wrap the range triggering it while its dropdown is opened.

@stof - at.js appears to be discontinued, in favour of tribute...  https://github.com/zurb/tribute
If you are having the same issue with tribute, provide a demo url I can test with, and I'll take a look


Menu option 'Defaults' does not restore terminal properties to factory settings in non-legacy mode

Environment
Microsoft Windows [Version 10.0.18362.418]
Steps to reproduce

Open Command Prompt - i.e. run cmd
Open properties dialog and ensure 'Use Legacy Console' is unchecked, then close dialog
Select menu option 'defaults'

Expected behavior
The terminal properties should be set to their factory defaults.
Actual behavior
Property window opens and properties have not been changed. What are the factory defaults? Who knows?

Hey thanks for the feedback! I definitely understand that UX is especially confusing. However, the "defaults" menu has literally never worked that way. When it comes to console settings, they're layered from a variety of locations, starting with the first here and successively applying subsequent layers:

The hardcoded defaults embedded in the application itself.
"Defaults" storen in the registry under HKCU\Console
Optionally, one of the following:

Properties that are stored in the shortcut
per-title settings that can be stored in HKCU\Console\<title>

Runtime settings passed in through STARTUPINFO.

When you open the "Defaults" propsheet, what you're actually doing is opening the menu to edit the defaults in item 2, the "registry defaults".
If you really want to "reset to factory defaults", you can just delete all the the keys under HKCU\Console.


Problem setting up stream

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?

Yes

Are you sure you're not using someone else's docker image?

Yes

Have you searched for similar issues (both open and closed)?

Yes

Describe the bug

While setting up a stream, an error shows up saying "data.forwarding_host should match exactly one schema in oneOf"
Nginx Proxy Manager Version

Verstion 2.9.8
To Reproduce
Steps to reproduce the behavior:

Create a new stream
Fill in all values
Get error on saving

Expected behavior

Creating a new stream
Screenshots

Operating System

Photon Os 3.0, build 11dd065
Additional context

This issue didn't happen before in a previous install, we upgraded and re-setup nginx proxymanager today because of issues upgrading.
I don't seem to find any logs about this issue on the server either.
Docker version used: 19.03.15, build 99e3ed8

is a fix planned ?

Might want to try the fix in the aforementioned PR.


elm-package publish allows revision where an exposed module is missing

I managed to publish signal-extra 5.2.0 with the new Signal.Fun module, but under that tag the Fun.elm file isn't present. I guess I forgot to put that file in the commit.
This situation sounds like something elm-package should check and disallow, right?

Closing in favor of the other one. Thanks for the report!


Revert "Use cpu-cores instead cores in constraints (#351)"

cpu-cores is deprecated:
$ juju add-machine --constraints cpu-cores=1
Warning: constraint "cpu-cores" is deprecated in favor of "cores".
created machine 0

More importantly, it's breaking conjure-up deployments:
$ conjure-up --channel edge kubernetes-core aws/us-east-1 aws-dev test
[info] Summoning kubernetes-core to aws/us-east-1
[info] Running step: pre-deploy.
[error] Unsupported constraint: cpu-cores
[warning] Shutting down

The failure in charm proof is being addressed:
https://github.com/juju/juju-bundlelib/pull/62
https://github.com/juju/juju-bundlelib/pull/63

@marcoceppi and I are working on building a new release of charm-tools that contains the juju-bundlelib fix.


What is the point of this?

I mean, It is kind of obvious but there is no visual example or screenshot to muse the people.

There are two screen shots in the documentation.
But this is a program that takes a text file and produces a different text file. There's not a whole lot of exciting visuals to go with it.

So how does Kicad relate with this? Kicad is a GUI tool to make schematics and pcb layouts.

You make a schematic in KiCad, export its netlist, then run this plugin to convert the netlist to Verilog code.

Exactly, it would be nice to see something like that. For instance, you show a schematic and the generated verilog.


Additive badge appears to be blurry

Which badge would you like the changes to be applied to?
Additive Badge
What fix would you like to see applied?
Make it not blurry lol
Provide any preferred icons/text (icons must be SVG)
Example if needed

lol. I think it's because I used the additive logo .png, I can fix this tomorrow if I have time. Should be pretty easy


Iterate on press page for Meltano.com

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/696
Originally created by @dmor on 2019-06-11 15:36:00

Similar to https://about.gitlab.com/press/

View 4 previous comments from the original issue on GitLab


[SPARK-27680][CORE][SQL][GRAPHX] Remove usage of Traversable

What changes were proposed in this pull request?
This removes usage of Traversable, which is removed in Scala 2.13. This is mostly an internal change, except for the change in the SparkConf.setAll method. See additional comments below.
How was this patch tested?
Existing tests.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/10599/
Test PASSed.

Test build #105327 has started for PR 24584 at commit fd3f46f.

The internal change is easy to understand.

Test build #105327 has finished for PR 24584 at commit fd3f46f.

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

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/105327/
Test PASSed.

BTW we have a bigger related issue: TraversableOnce -> IterableOnce. This is much more widely used and in some key APIs. I may break that one out separately into a new JIRA.

Merged to master


Moving the player

Input handing in process function

https://github.com/user-attachments/assets/e6f00461-e5a5-4583-b042-88e68f17f989


Why are integers strings?

"rewards" are string type. Why? Shouldn't they be int?

There's a lot of little weird types like that because of the way the Tezos RPC responds. I think it's annoying too, but the RPC to get rewards uses a string, instead of an int. You'll also notice if you dive into the RPC that this practice isn't always universal, so you have to be careful.


"Error 403 Forbidden" displayed on an embedded chart when using a particular aggregation function in the chart metric

Bug description
I am embedding a dashboard in another app. Embedding does not work when the chart metrics are using some of the aggregation functions :

embedding works fine with charts using: SUM, COUNTD, AVG
embedding DOES NOT WORK for charts using: MIN, MAX, COUNT

On the Superset tool itself, there's no visible issue. It's only once the chart is embedded that I am encountering this issue and the following error message:

<!doctype html><meta charset="utf-8"><meta name=viewport content="width=device-width, initial-scale=1"><title>403</title>403 Forbidden
How to reproduce the bug
You need to embed the charts in another app to reproduce the bug. There's no sign of the bug on Superset.

Create a chart (tested on : big number chart, bar chart, line chart)
For the metric, choose an aggregation of type MIN or MAX or COUNT
Save the chart and add it to the dashboard you are embedding.
Normally: you should see the chart on Superset, but chart should be broken in the final destination of the chart.

Screenshots/recordings
No response
Superset version
3.1.3
Python version
I don't know
Node version
I don't know
Browser
Chrome
Additional context
No response
Checklist

[X] I have searched Superset docs and Slack and didn't find a solution to my problem.
[X] I have searched the GitHub issue tracker and didn't find a similar bug report.
[X] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

@dosu
I have taken a look at the permissions associated with each role in the Superset settings: all of them already has the "can csv on Superset" permission.
You are mentioning a "can_csv" permission: is it a permission that should be implemented elsewhere ? thanks

@dosu
I have verified for all of my users and they all have the "can csv on Superset" and the "can explore json on Superset" permissions.
Could there be another reason to my issue ?


feat: Separated UI from core
BREAKING CHANGE:  _______

Description
The main goal of this PR is to separate the Modal UI into a separate package and move it away from the core package.
The idea is to give users/developers more flexibility, now they will have the option to use our Modal or they can implement their own UI.
The modal now will be a custom web component which is developed using Stencil.
This PR adds three additional projects under /packages:

selector-ui (the stencil component from which we create the react and angular wrappers around)
selector-ui-react ( creates <WalletSelectorModal />)
selector-ui-angular (creates <wallet-selector-modal />)

These are the main things on the PR:

Removed old modal.
Created Modal UI using Stencil.
Created 3 additional packages/projects mentioned above.
Updated the react and angular example to use the new modal component(s).

Closes # (issue)

Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings

Type of change. This type of change is the main reason for the PR.

[ ] FIX - a PR of this type patches a bug.
[x] FEATURE - a PR of this type introduces a new feature.
[ ] BUILD - a PR of this type introduces build changes.
[ ] CI - a PR of this type introduces CI changes.
[ ] DOCS - a PR of this type introduces DOCS improvement.
[ ] STYLE - a PR of this type introduces style changes.
[ ] REFACTOR - a PR of this type introduces refactoring.
[ ] PERFORMANCE - a PR of this type introduces performance changes.
[ ] TEST - a PR of this type adds more tests.
[ ] CHORE - a PR introduces other changes than the specified above.

Breaking changes

[x] BREAKING CHANGE - SPECIFY: _______
[ ] NO BREAKING CHANGE - this PR doesn't contain any breaking changes and it's backwards compatible

Closing this PR in favor of a much simpler solution:
https://github.com/near/wallet-selector/pull/287


Vanilla Whitelist Import?

I cant see any information about it, how do I import a vanilla whitelist file to the plugin data storage? I have a whitelist file that is hundreds of players large and cant be expected to manually import almost 1500 users over to a new plugin manually

hi, this function will be tracked in #10
there you can find a light plugin in case you want to use the function earlier
it is an add-on so it is necessary to have the base plugin
this function will be later added to the base plugin
thanks!

Thank you!! Would you also consider adding an option to have the plugin also use the vanilla whitelist file along side the plugins current data storage when adding and removing users from the whitelist. This would help to have a fallback for if theres some sort of plugin issue, or data loss from a sql database or any other worst case scenario. It would also help to ensure compatibility with any plugin that might read data from the default whitelist file, like DiscordSRV for example with its account linking system, which requires accounts to be linked through their bot, but has an option to not require that for whitelisted users. I personally use the DiscordSRV bot to sync my support roles to the mc server

hii, yes I could add it, although I will look for a correct way to implement it
the vanilla whitelist is stored in an array, so a lot of continuous changes and specially when there are a lot of entries maybe can impact on performance
in any case I would end up adding it experimentally, only for those who know how to use it ^^
and thanks for mentioning DiscordSRV, I was modifying the discord plugin to integrate with other plugins that connect to discord
so it can reduce resource usage, and they can manage all that part from another known plugin
I'll keep an eye on that, thx!


EPS Faulting since NEOS v8 update - 2018 GMC Acadia Denali

i really hope someone can help me.  For whatever reason since i updated my eon to neos 8 iv been having issues where i get an EPS faults randomly.  every time this happens i see theres a late/early ASCMLKASteeringCmd msg.  it seems as if when the EPS receives two ASCMLKASteeringCmd msgs in under 0.010ms it faults out.
normally the msgs should be about 0.020ms apart or a steer step of 2 as per stock.
the ASCMLKASteeringCmd msg timing is the only common denominator i can find on every fault.  This happens engaged or not.  i tried with different usb cords and another panda.  everything has been fine for months, the only thing that changed recently was the neos update but im not sure how that could have changed anything.
this is on the comma devel branch too.  i even tried factory resetting my eon just to be sure and i still experience this problem.
i had a thought to try and test this timing theory,  maybe if i tried delaying the ASCMLKASteeringCmd  msg to a step of 3 or about 0.030ms it would have less of a chance of having a delay and causing the following msg to be sent under 0.010ms from the previous lka msg.
by doing this i was not able to reproduce the EPS issue.
heres the drive from that testing.  this is just one of many tests.
https://community.comma.ai/cabana/?route=7cc2a8365b4dd8a9|2018-12-19--13-16-22&max=48&url=https%3A%2F%2Fchffrprivate.blob.core.windows.net%2Fchffrprivate3%2Fv2%2F7cc2a8365b4dd8a9%2F87d09f383607dd19cb4a21a9cb9b6fbc_2018-12-19--13-16-22
So to try and test this theory further i set the steer step to 1 which would be sending the ASCMLKASteeringCmd msg every 0.01ms which should pretty much guarantee a msg in under 0.01ms and therefor should fault out almost right away..
sure enough the EPS does fault out pretty much right away every time it receives 2 ASCMLKASteeringCmd msgs.
https://community.comma.ai/cabana/?route=7cc2a8365b4dd8a9|2018-12-19--17-29-59&max=41&url=https%3A%2F%2Fchffrprivate.blob.core.windows.net%2Fchffrprivate3%2Fv2%2F7cc2a8365b4dd8a9%2F54904d53333f5b094f6211e8f705d254_2018-12-19--17-29-59
im not sure what i can do to try and resolve this or where to even start.
is there a way i can make sure the ASCMLKASteeringCmd msg is never sent any sooner than 0.010ms after the previous msg?
i used a screen recorder and could see the controlsd lag build up a bit at the time i get the fault so im not sure if that has anything to do with it

problem drives
12:55:25 - 12:58:25 - seekTime=894
parked after drive - late/early ASCMLKASteeringCmd msg? - 894.251 - 894.259
https://community.comma.ai/cabana/?route=7cc2a8365b4dd8a9|2018-12-18--12-43-25&max=15&url=https%3A%2F%2Fchffrprivate.blob.core.windows.net%2Fchffrprivate3%2Fv2%2F7cc2a8365b4dd8a9%2F0aaa6f910b9885b07bf3c563084427e9_2018-12-18--12-43-25
20:01:05 - 20:04:05 - seekTime=604
late/early ASCMLKASteeringCmd msg? - 604.490 - 604.529
https://community.comma.ai/cabana/?route=7cc2a8365b4dd8a9|2018-12-17--19-52-05&max=29&url=https%3A%2F%2Fchffrprivate.blob.core.windows.net%2Fchffrprivate3%2Fv2%2F7cc2a8365b4dd8a9%2Ffac15d8847e972be0af85395da5fbdf2_2018-12-17--19-52-05
14:57:09 - 15:00:09 - seekTime=544
late/early ASCMLKASteeringCmd msg? - 544.890 - 544.930
https://community.comma.ai/cabana/?route=7cc2a8365b4dd8a9|2018-12-17--14-49-09&max=28&url=https%3A%2F%2Fchffrprivate.blob.core.windows.net%2Fchffrprivate3%2Fv2%2F7cc2a8365b4dd8a9%2Ffcda4af77cef4657c7a55bfbf7bf5697_2018-12-17--14-49-09
13:49:51 - 13:52:51 - seekTime=128
large amount of dropped ASCMLKASteeringCmd msgs 128.494 - 128.801
https://community.comma.ai/cabana/?route=7cc2a8365b4dd8a9|2018-12-17--13-49-51&max=8&url=https%3A%2F%2Fchffrprivate.blob.core.windows.net%2Fchffrprivate3%2Fv2%2F7cc2a8365b4dd8a9%2Fc5a9d6b472c6e6546c8d8909647959ca_2018-12-17--13-49-51
13:12:13 - 13:15:13 - seekTime=623
ASCMLKASteeringCmd extra msg? 623.912 - 623.918
https://community.comma.ai/cabana/?route=7cc2a8365b4dd8a9|2018-12-17--13-04-13&max=13&url=https%3A%2F%2Fchffrprivate.blob.core.windows.net%2Fchffrprivate3%2Fv2%2F7cc2a8365b4dd8a9%2Fea58a0e2a094b72577bb31a270365803_2018-12-17--13-04-13
18:59:59 - 19:02:59 - seekTime=1873
not engaged.  late ASCMLKASteeringCmd becomes 2 msgs at the exact same time @ 1873.915
https://community.comma.ai/cabana/?route=7cc2a8365b4dd8a9|2018-12-15--18-30-59&max=36&url=https%3A%2F%2Fchffrprivate.blob.core.windows.net%2Fchffrprivate3%2Fv2%2F7cc2a8365b4dd8a9%2F371205592513649334672473064953af_2018-12-15--18-30-59
16:26:13 - 16:29:13 - seekTime=656
late ASCMLKASteeringCmd becomes 2 msgs at the exact same time @ 656.661
https://community.comma.ai/cabana/?route=7cc2a8365b4dd8a9|2018-12-15--16-17-13&max=14&url=https%3A%2F%2Fchffrprivate.blob.core.windows.net%2Fchffrprivate3%2Fv2%2F7cc2a8365b4dd8a9%2F16af576e14e34c5be1a1115a5e58565e_2018-12-15--16-17-13

stock drive / stock lkas - 18:03 - 18:06
https://community.comma.ai/cabana/?route=7cc2a8365b4dd8a9|2018-09-12--17-57-31&max=52&url=https%3A%2F%2Fchffrprivate.blob.core.windows.net%2Fchffrprivate3%2Fv2%2F7cc2a8365b4dd8a9%2Fb144fb331c158412cdc93ec42cb059eb_2018-09-12--17-57-31

Pictures showing the issue

I’m having the same kind of issue with my Prime 2017. Seems that if the car is already started when the EON boot up, fix this problem.

I have the same kind of issue with my Prime 2017. I found that booting the oen before starting the car solve my issue.

yeah i dont really have an issue on starting the car although i do occasionally get an EPS fault upon start but almost never.  the problem is more random than that
i recorded my screen today showing what happens when i get the fault.  as you can see controlsd lags excessively.  any thoughts @rbiasini ?
it starts about 20 secs into the GIF

I was able to downgrade NEOS back to the last version along with 0.5.6 and the EPS faults went away with my white panda.  HOWEVER with my grey panda and the antenna connected I still get EPS faults.  if i remove the antenna from the grey panda it works fine just like the white panda.  no faults at all.
This is actually how my grey panda has acted since i got them in the summer, i just assumed it was an issue with me but now it seems like its more of a resource issue with the EON perhaps?
with NEOS 8 on both my white and grey pandas I get EPS faults, antenna or not.
the faults all happen the same way.  it appears to lag just enough to cause two lkasteeringcmd msgs to be delivered in under 0.01ms
heres proof it works fine with the grey pandas antenna disconnected.
one hour driving
https://community.comma.ai/cabana/?route=7cc2a8365b4dd8a9|2018-12-25--15-00-48&max=55&url=https%3A%2F%2Fchffrprivate.blob.core.windows.net%2Fchffrprivate3%2Fv2%2F7cc2a8365b4dd8a9%2F2b6fabb76e15a559425262c643d13387_2018-12-25--15-00-48
another hour driving back
https://community.comma.ai/cabana/?route=7cc2a8365b4dd8a9|2018-12-25--16-42-04&max=57&url=https%3A%2F%2Fchffrprivate.blob.core.windows.net%2Fchffrprivate3%2Fv2%2F7cc2a8365b4dd8a9%2F25918245ddf8045d963383c69a414d3c_2018-12-25--16-42-04
heres the drive with the antenna connected where it didnt last even 15 mins which is about as long as i can get without a fault
14:50:08 - 14:53:08 - 866 secs
https://community.comma.ai/cabana/?route=7cc2a8365b4dd8a9|2018-12-25--14-38-08&max=17&url=https%3A%2F%2Fchffrprivate.blob.core.windows.net%2Fchffrprivate3%2Fv2%2F7cc2a8365b4dd8a9%2F87397ac015f523fded7dbb34783c0fd1_2018-12-25--14-38-08
im not sure what can be done about this.  any ideas?

just an update.  last week I reverted back to neos 6 and both 0.5.6 and 0.5.7 work fine without any EPS faults.
couple hour drive without issue
https://community.comma.ai/cabana/?route=7cc2a8365b4dd8a9|2018-12-29--16-44-26&max=100&url=https%3A%2F%2Fchffrprivate.blob.core.windows.net%2Fchffrprivate3%2Fv2%2F7cc2a8365b4dd8a9%2F136995c9b0879f75bccd5c53a4ad89b8_2018-12-29--16-44-26
this is still with my grey panda antenna disconnected.  if i plug the antenna in i will get an EPS fault after a few mins.  i even drove for an hour then plugged the antenna in while still driving and within a min or 2 my EPS faulted out.
as mentioned the faults all appear to happen the same way.  two lkasteeringcmd msgs in under 0.01ms as shown above
vtarasov mentioned profiling controlsd so i did.  heres the cprofile output file if it helps.
acadia cprofile.zip
is there something you guys can suggest?

This should be resolved with 0.5.9 release. Going to close this but feel free to reopen if you still have issues.

This issue has not yet been resolved.


Easier setup of a "registration-only" implementation

Some schools that have their own well-functioning websites may not want to switch to Django CMS right away, but they may still want to switch to this registration system right away.  To make this easier, there should be an option in the setupschool script to configure urls for a "registration-only" implementation in which the registration page is the front page of the site.  That way, a school could simply add a link to, say, registration.mydanceschool.com, which holds their Django installation with their registration system.
There are probably a couple of different ways to do this, but I suspect that the easiest will be to use a pretty straightforward implementation of Django CMS apphooks.  I will look into it to see what is the best way to proceed.

This was in fact a simple change to the setupschool script.  It has now been implemented and will be pushed with version 0.3.0.


Cleanup

Codecov Report

Merging #48 (a3f55b9) into main (3060e16) will decrease coverage by 37.64%.
The diff coverage is 39.43%.

@@             Coverage Diff             @@
##             main      #48       +/-   ##
===========================================
- Coverage   89.52%   51.87%   -37.65%
===========================================
  Files          88       89        +1
  Lines        4486     4588      +102
===========================================
- Hits         4016     2380     -1636
- Misses        470     2208     +1738

Impacted Files
Coverage Δ

src/bodies/origin.jl
36.36% <0.00%> (-63.64%)
:arrow_down:

src/contacts/collisions/capsule_capsule.jl
0.00% <ø> (ø)

src/contacts/collisions/sphere_halfspace.jl
75.43% <ø> (-7.02%)
:arrow_down:

src/contacts/collisions/sphere_sphere.jl
0.00% <ø> (-100.00%)
:arrow_down:

src/contacts/collisions/string.jl
0.00% <ø> (-100.00%)
:arrow_down:

src/contacts/constructor.jl
83.87% <ø> (-12.91%)
:arrow_down:

src/contacts/impact.jl
0.00% <0.00%> (-93.11%)
:arrow_down:

src/contacts/linear.jl
0.00% <0.00%> (-100.00%)
:arrow_down:

src/gradients/data.jl
23.55% <0.00%> (-76.45%)
:arrow_down:

src/gradients/finite_difference.jl
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 94 more

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 3060e16...a3f55b9. Read the comment docs.


Add licence

I'd like to ask to add a license to the repository

Done! I added an Apache (permissive) License.


不支持10.0.19041.1620

不支持10.0.19041.1620
termsrv.zip

my windows 10 Pro version also can not use....would you please help to update...tks
Windows 10 Pro termsrv.dll 10.0.19041.1620

Tks!!!!


Add rollout options to job config

Codecov Report

Merging #1165 into master will increase coverage by 0.19%.
The diff coverage is 75%.

 Also updated inspect output.

I'm OK with this approach if we update docs that say job configs with null rollout options will have those options defaulted to some values by the master at rolling-update time not on job creation time.

Last two commits address 1-3 here.

@caipre just curious, do you have another approach in mind?

thanks for addressing my feedback


Create registerview.js

This code defines a React Native component for user registration. It includes text input fields for a username, password, and password confirmation. The component uses Axios to make a POST request to a registration API endpoint. If the registration is successful, it sets the user's username and navigates to the "Home" screen. If there are errors, it highlights the corresponding input fields. Additionally, there is a link to navigate to the login screen. The UI is styled using the React Native StyleSheet.


Kiota should send properties in OAS declaration order, not alphabetic order

What are you generating using Kiota, clients or plugins?
API Client/SDK
In what context or format are you using Kiota?
Nuget tool
Client library/SDK language
Csharp
Describe the bug
My OAS file lists properties (in component schema) in an intentional order: type, id, firstName, lastName, age. While the last three vary per model, the first two are always present. Kiota ignores that and uses alphabetic order instead: age, firstName, id, lastName, type. This makes the payload harder to read, test, and debug.
Expected behavior
Preserve declaration order. In the case of inheritance, fields from base types come first.
How to reproduce

Open API description file
No response
Kiota Version
1.14.0
Latest Kiota version known to work for scenario above? (Not required)
No response
Known Workarounds
None
Configuration
No response
Debug output
No response
Other information
No response

Hi @bkoelman
Thanks for using kiota and for reaching out.
Can you outline further why do you think this makes things harder to debug?
The reasons why properties are in alphabetical order it to:

get deterministic output
ease debug/code reading (easier/faster to scan an ordered list than an unordered one)

Thanks for the additional information.
I'm not sure why anybody would implement an API with dependencies on the order of properties for a JSON payload when the JSON RFC especially calls out object properties are unordered by nature.

An object is an unordered collection of zero or more name/value
pairs, where a name is a string and a value is a string, number,
boolean, null, object, or array.

This sounds like a bad design of the API itself that should be addressed in the API instead of pushing a constraint on clients. Do you have example scenarios that cannot be achieved through any other way than a specific ordering of the properties?

Not at the moment, but years ago I ran into that with XML more than once: Large commercial enterprise systems that we couldn't change because they were provided by external vendors, or because the source code got lost over time (yes, that happens, and more often than you'd think, even today). Or 3rd party external systems written in PHP, that didn't rely on an XML DOM parser, because at the time there wasn't one built-in yet. We had to work around these problems because getting the external systems changed was too expensive.
I agree that an implementation that depends on the order is a bad design, however, sometimes it's out of our control. But my primary concern is readability, as my sample shows.

Thanks for the additional information.
I want to be transparent with the fact that we're unlikely to invest in ordering to accommodate the legacy/badly designed systems.
As for the readability aspect, is it because you want the discriminator property to be first? or am I missing something here?

It's unrelated to discriminators, it's about preserving the declaration order. A model that defines first name, middle name and last name (in that sequence) should not be hussled.

I understand you have a specific opinion of how things should be, however between the JSON spec that explicitly calls out the unordering, and lack of additional evidence/scenarios, it's only an opinion.
I'm going to go ahead and close this issue since it's unlikely we're going to change things here.
Thanks for your understanding.

 SQL columns are unordered in SELECT, yet their order is preserved in EF Core queries. C# methods are unordered, yet their order is preserved in IL (MetadataToken). Not because it's a technical requirement, but because it improves usability and readability. Even IDictionary<,> preserves insertion order.
I can understand this is low priority, but closing this because your personal opinion goes against what's common in most other tools, and ignoring all motivation, is just disrespectful. You're apparently not very experienced with developer expectations, nor managing an open source project. It would make more sense to leave this open for others to upvote. I've proven you wrong on nullability before, which is now the most updated issue. Having some faith in what users care about would avoid a lot of frustration. This recurring attitude of "I know better than the rest of the world" makes me eager to abandon kiota, and I'm pretty sure more people feel that way.

We have countless instances of issues being left open for upvote/future consideration in this repo. (see v2 or v3 or backlog milestones for examples, or even past versions). This includes multiple of your own issues
At some point, the sheer management of issues being left open becomes a challenge in itself, this is why I drive the conversations to demonstrate tangible additional values. You've had multiple opportunities to demonstrate that "if we invest in making sure properties are ordered in the same way they are in the description, we unblock this scenario, which is likely to benefit a broad base of users", and you haven't.

@bkoelman The JSON specification specifications states https://datatracker.ietf.org/doc/html/rfc8259#section-4

JSON parsing libraries have been observed to differ as to whether or
not they make the ordering of object members visible to calling
software.  Implementations whose behavior does not depend on member
ordering will be interoperable in the sense that they will not be
affected by these differences.

As Kiota is intended to support any JSON parsing library, taking dependencies on the behaviour of some libraries would impact interoperability.  As far as developer experience goes, I've yet to see an autocomplete experience that lists members of an object in declared order.  Using alphabetical ordering is quite common when selecting properties.
The OpenAPI.NET library that Kiota is based upon makes no attempt to preserve document content that is outside of the OpenAPI semantics.  e.g. map ordering, whitespace, Therefore it would make it challenging to consistently carry through this information into Kiota and project it into source code.
It was not a design objective of Kiota use non-significant formatting of the source OpenAPI as part of code generation.  I have not seen strong reasoning in this thread to suggest revisiting that goal.
I would however be open to considering using semantics like required/readonly/etc to suggest ordering, but attempting to insult community members doesn't seem like the right approach to make that case.

We have countless instances of issues being left open for upvote/future consideration in this repo. (see v2 or v3 or backlog milestones for examples, or even past versions). This includes multiple of your own issues

I appreciate the effort to act and decide on issues early, instead of leaving them lingering. Exceptions aside, the large amount of open issues reflects the poor quality of kiota. Because most are bug reports, or clumsy limitations that make using kiota a pain (from a consumer perspective). It sounds like you're doing me a favor by not closing my bug reports? When the goal is building a flourishing community, it should be the other way around: be grateful for opening them, acknowledging that other people are giving up their free time to provide an opportunity to build a better product, even when the team currently doesn't have time for that. Having many open bugs reflects the product is popular, which may give you leverage in allocating more resources to the team. That, and not bothering to test with the provided repro steps, and closing issues as completed without actually fixing the problem (taking note isn't enough; taking responsibility means reopening, and converting it to an umbrella issue that lists other issues it depends on), is what I meant with being unexperienced in managing an open source project.

At some point, the sheer management of issues being left open becomes a challenge in itself, this is why I drive the conversations to demonstrate tangible additional values.

I don't see why. GitHub has great capabilities to manage large amounts of issues, by using tags, milestones, projects, advanced issue filters, etc. Runtime has 5k open issues, aspnetcore has 3k open issues; perhaps ask there on how to manage them?

You've had multiple opportunities to demonstrate that "if we invest in making sure properties are ordered in the same way they are in the description, we unblock this scenario, which is likely to benefit a broad base of users", and you haven't.

I've given several motivations, which you haven't responded to. You're supposed to explain why your point of view is the better solution, and what the downsides are in my point of view. Just dismissing them isn't having a discussion.

As Kiota is intended to support any JSON parsing library, taking dependencies on the behaviour of some libraries would impact interoperability. As far as developer experience goes, I've yet to see an autocomplete experience that lists members of an object in declared order. Using alphabetical ordering is quite common when selecting properties.

Neither does the spec recommend to order them alphabetically, which is what kiota does. I'm just asking to not sort them, I have no idea what kind of investment you're referring to. Sorting the list of schemas is fine, but the model properties reflect something functional that users care about. It matters in reading logged requests and responses. Autocomplete is a lookup tool that has its own logic to sort, based on the most-likely match. The declaration order is irrelevant in that case, but that was never my point.

The OpenAPI.NET library that Kiota is based upon makes no attempt to preserve document content that is outside of the OpenAPI semantics. e.g. map ordering, whitespace, Therefore it would make it challenging to consistently carry through this information into Kiota and project it into source code.

I'm not concerned about whitespace, but OpenAPI.NET doesn't take explicit steps to change the ordering, which is nice. I'd be fine if kiota worked similarly.

It was not a design objective of Kiota use non-significant formatting of the source OpenAPI as part of code generation. I have not seen strong reasoning in this thread to suggest revisiting that goal. I do think there is value in having a deterministic order of the properties.

Why would this tradeoff be different for kiota than for OpenAPI.NET?

I would be open to considering using semantics like required/readonly/etc to suggest ordering

I don't see the advantage of that. I'd consider that unintuitive.

but attempting to insult community members doesn't seem like the right approach to make that case.

That's not my goal. In being a fully-remote worker for years I've learned to always assume best intent, asking for clarification instead of making assumptions. But also to reach out if things aren't right. As expressed above, there wasn't much of a discussion. Perhaps some of you are just too overworked, but feedback and concerns are often dismissed without explanation, which is demotivating and disrespectful. These and other concerns came up in #4349, but I'm not seeing a change in attitude. There's an underlying sentiment of disliking feedback and not being interested in what matters to users, despite saying otherwise.

Here's evidence that users care about the order: https://github.com/dotnet/runtime/issues/102932:

While this is consistent with the semantics of JSON where order of properties is not significant, it is often the case that one wants to arrange the order out of human readability concerns. For example, it is common for JSON schema docs to place the $schema and $id properties at the start of the object.

Another reason is performance: in System.Text.Json, a JsonConverter takes a forward-only reader. In JSON:API the "type" property determines how the remaining properties are serialized. When it doesn't appear at the top, the converter needs to run a second pass.


input  label error when col and rows classes are not used

On FireFox v49.0.1, the label gets fixed incorrectly to the right of the input field, instead of flushed with the input field at the left margin.
Adding left: 0 fixes this immediately, with no foreseeable consequences.
Here is the current way it looks.

Here is how it looks with this PR, which is how it should look

PR already submitted:
https://github.com/Dogfalo/materialize/pull/3821

Can you post your code so I can recreate it locally?

I saw this was reported here several times, but I never was able to reproduce it.
Here is Firefox 49.0.2 got from https://www.mozilla.org/en-US/firefox/new/ on ubuntu 15.10

It looks it happens if a form doesn't use grid "row" and "col" classes.
http://codepen.io/kmmbvnr/pen/kkmAAO
It's ok on Chrome 54

But broken on FF 49

See also #3789

@kmmbvnr Yes you are correct, this is occurring when not using .row .col tags. The reason is because I prefer to use a custom grid made with Susy 2, rather than the premade grid in materialize. In that case, I have no need for the .row .col tags since my grid handles it.
But, then we have the label positioning issue.
My code:
Sass
/********************/
/* Login.scss */
/********************/
@import '../../assets/styles/appwide-metastyles.scss';

/// <reference path="../../../node_modules/susy/sass/susy/language/_susy.scss" />
/// <reference path="../../../node_modules/bourbon/app/assets/stylesheets/bourbon" />
/// <reference path="../../assets/styles/shared/variables.scss" />
/// <reference path="../../assets/styles/shared/mixins.scss" />

// The Susy Span Mixin Syntax
// This creates the app layout using Susy's Math functions
// @include span( <$span> of [<$context>] [<$last>] );
// Note: Arguments within square brackets are optional arguments

@include nested(24) {
   login {
      @include clearfix;
      align-items: center;
      height: 80vh;
      display: flex;
      justify-content: center; //height: 100vh; // This forces .app-container to 100% of your viewport

      .welcome-message {
         color: #fff;
         font-weight: bold;
      }

      .login-form {
         width: span(6);
         margin: 20px;
         position: relative;
         //top: 200px;
         @include border-radius(10px);

         md-card {
            background-color: #f9f9f9;
            margin: 20px 0;
            padding: 34px;
            @include border-radius(10px);
         }

         button.login-submit {
            margin: 15px 0 10px;
            font-size: 1.5em;
         }
      }
   }
   // end login {}
}

// end susy nested {} context

HTML

Angular2 Webpack2 DotNET Starter

By IAMtheIAM

         <form role="form" (submit)="login($event, username.value, password.value)">

                  account_circle
                  <input type="text" #username class="" id="username1" value="admin">
                  Username

                  lock_outline
                  <input type="password" #password class="" id="password1">
                  Password

                  <input type="checkbox" id="rememberMe1" value="" class="rememberMe" />

                  <input type="checkbox" id="filled-in-box1" class="filled-in rememberMe" />
                  Remember me

                  Forgot password?

            <button class="btn btn-block btn-large waves-effect waves-light login-submit" type="submit" name="action">
               Loginsend
            </button>
         </form>

Have you been able to recreate this on the latest master branch? I'm pretty sure i've added this in 28b119a8233280e927318f8b02051a6f69ff65cf

I've upgraded the codepen to from 0.97.7 to 0.97.8 and the issue looks fixed under FF

@kmmbvnr You say this issue is fixed?

@tomscholz yep, works fine in latest release http://codepen.io/kmmbvnr/pen/kkmAAO

@kmmbvnr thanks!


Detect and report an ErrImagePull/ImagePullBackOff VM status

What this PR does / why we need it:
This PR extends the VM status field (.status.printableStatus) with new ErrImagePull/ImagePullBackOff statuses, reported when an error occurs when pulling a container image for the VM.
This will typically indicate that one of the container disks of the VM has failed to be pulled, but may also indicate that there was an error pulling the virt-launcher image or one of its init container images.
Special notes for your reviewer:
This was implemented by first propagating the ErrImagePull/ImagePullBackOff container status from the virt-launcher pod, to the VMI conditions (Synchronized=False, Reason: ErrImagePull/ImagePullBackOff), and then from the VMI to the VM's status.
This approach involves additional updates to the VMI object. Alternatively, we could have avoided that by adding a pod informer to the VM controller, and propagate the status directly from the pod to the VM (without updating the VMI). But there's a caveat too:

If we configure the pod informer callbacks to trigger the controller with each pod update, then we add quite a lot of additional processing to the VM controller. This is not necessarily better than additional VMI updates.
If we avoid pod informer callbacks in the VM controller, we won't be able to track the ErrImagePull-->ImagePullBackOff transitions in the pod, so we'll have to just report a single value in the VM status.

Eventually, I chose the pod-->VMI-->VM approach since it's (1) able to report both ErrImagePull, ImagePullBackOff statuses from the pod, and (2) provides visibility to this kind of error via the VMI object too.
Release note:
Report ErrImagePull/ImagePullBackOff VM status when image pull errors occur

/retest

/retest

/retest

/retest

/lgtm

@zcahana  For the testcase: VirtualMachine: A valid VirtualMachine given should report an error status when image pull error occurs it is [test_id:6869]

Thanks @ashleyschuett and @kbidarkar!
I've rebased + updated the functest with the new test_id.
The PR is now ready for re-review.

/retest

/lgtm

/lgtm

Thanks @ashleyschuett! do you think there's anything else needed for an /approval or this is ready to go as-is?

/approve

/retest

/retest


Should we allow bit-select on/with Bool() type?

Type of issue: Feature Request
Is your feature request related to a problem? Please describe.
It is nonintuitive what it is supposed to mean if you have a Bool type and do a bit-select on it (which is apparently allowed even if the thing you are bit-selecting with is a boolean!). IN fact it is strange that we allow a Bool to be the selector too.
Describe the solution you'd like
It would make more sense if it were a compile or runtime error to do a bitselect on a Bool type or a bitSelect where the selector is a Bool type.
Describe alternatives you've considered
Leave things as they are
Additional context
https://scastie.scala-lang.org/HU5nisSDQR6g35rO66Nzhg
What is the use case for implementing this feature?
What is the use case for allowing this?

What is the use case for implementing this feature?

Catching bugs at compile time instead of silently allowing them.

I think that making this a compile time error will be a heavy lift, but I think we can focus on a shorter-term runtime error/warning solution


Broken link for swagger API docs

The link directing one to Fineract's API Swagger docs from the fineract.dev website or this repo's ReadMe is broken. When visited on comes across this page

Yeah. As https://www.fineract.dev says:
Who pays for hosting this? vorburger@ originally paid for it personally. Google Cloud hosting costs for this demo site were graciously offered by Google Open Source from mid October 2021 to 2022. The demo instance is currently stopped; please reach out to<EMAIL_ADDRESS>if you would like to discuss bringing it back alive.


Question on plugin usage for React.createContext

Hello, I am seeking some help to better understand how should I organise my components in order to minimize elslint error for
react-refresh/only-export-components rule.
Case - When creating a React Context it is common practice do like this
// code is simplified
const ThemeContext = React.createContext();

const ThemeProvider  = ({ theme, children }) => {
	return <ThemeContext.Provider value={theme}>{children}</ThemeContext.Provider>;
};

const useTheme = () => {
	return useContext(ThemeContext);
};

export { ThemeProvider, useTheme };  //Fast refresh only works when a file only exports components...

Is this correct, that I need to split this to 3 files for fast-refresh to work propertly? Or is this a false-positive and file can be kept as is, just some modification to plugin are required?
Thanks for your answer.

Yes this is the most annoying change when you want to follow the rule.
If you don't do it here, any change to this file will create an HMR updates of all files and components using useTheme and ThemeProvider. While sometimes having HMR updates at the root component is fine, sometimes it can lead to some state loss when some component do a bit too much on useEffects.
Personally I use less and less contexts and more zustand store when the context is used as a singleton (one instance always available). Theme provider seems like a well suited usecase for this.
Also splitting in 2 is enough, ThemeContext & useTheme in one and ThemeProvider in the other

Thank you a lot for clarifications.


Add a planar digitisation algorithm

that should be ready for multithreading (currently not supported in k4FWCore so that will have to wait)
BEGINRELEASENOTES

Add the DDPlanarDigi processor as a Gaudi algorithm. It should have exactly the same logic as the original DDPlanarDigiProcessor. There has been a bit of clean up, some parameters have been changed and some variable names have been changed to be in the style of the rest of the key4hep repositories. Ported from https://github.com/iLCSoft/MarlinTrkProcessors/blob/master/source/Digitisers/include/DDPlanarDigiProcessor.h

ENDRELEASENOTES
Plots will be commented out since the current version of Gaudi in the stack is too old and there are some compiler errors, but it builds and works fine with master in Gaudi.
Validation has been done with a file with 25 events (Z->qq). On the Marlin side the Overlay has been disabled to make sure the input collections are not modified. Then, I ran the python file in this PR over that file. The parameters
are taken from https://github.com/iLCSoft/CLICPerformance/blob/master/clicConfig/clicReconstruction.xml.
So far everything I have checked looks good, these are the plots that both the processor and this algorithm make that I haven't changed (except the binning for diffu and diffv), the order is first the plot from the processor and then the plot from this algorithm
This is the change in the local coordinate u for the accepted hits; the resolution is set to 0.003 mm which is what we get in the resolution.

Same as above but for v

This is the energy of the hit, should be identical in both cases. Note that there are more entries since this plot is done for every hit, including the ones that are not accepted.

This is the percentage of hits accepted for each event

This is the smearing in u but divided by the resolution; i.e. normalized to have sigma 1

Same as above but with v

Note that the number of accepted hits is the same in both cases but this isn't necessary since the random numbers generated for the smearing are different in each case.

This PR has been updated and it's ready for comments


intltool recipe fetch failed due to certificate issues

Hi,
I am compiling openwebrtc on ubuntu14.04 with instructions from wiki of this project. Got the below message for recipe intltool. Any work around for this or any patches to apply to this recipe?
Fetching tarball https://launchpad.net/intltool/trunk/0.51.0/%2Bdownload/intltool-0.51.0.tar.gz to /home/ret/cerbero/build/sources/local/intltool-0.51.0/intltool-0.51.0.tar.gz
Downloading https://launchpad.net/intltool/trunk/0.51.0/%2Bdownload/intltool-0.51.0.tar.gz
Running command 'wget https://launchpad.net/intltool/trunk/0.51.0/%2Bdownload/intltool-0.51.0.tar.gz -O /home/ret/cerbero/build/sources/local/intltool-0.51.0/intltool-0.51.0.tar.gz '
wget: /opt/openwebrtc-0.3/lib/libcrypto.so.1.0.0: no version information available (required by wget)
wget: /opt/openwebrtc-0.3/lib/libssl.so.1.0.0: no version information available (required by wget)
--2017-12-18 17:07:33--  https://launchpad.net/intltool/trunk/0.51.0/%2Bdownload/intltool-0.51.0.tar.gz
Resolving launchpad.net (launchpad.net)... <IP_ADDRESS>, <IP_ADDRESS>
Connecting to launchpad.net (launchpad.net)|<IP_ADDRESS>|:443... connected.
ERROR: cannot verify launchpad.net's certificate, issued by ‘/C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert SHA2 Extended Validation Server CA’:
Unable to locally verify the issuer's authority.
To connect to launchpad.net insecurely, use --no-check-certificate'. Downloading https://gstreamer.freedesktop.org/src/mirror/intltool-0.51.0.tar.gz Running command 'wget https://gstreamer.freedesktop.org/src/mirror/intltool-0.51.0.tar.gz -O /home/ret/cerbero/build/sources/local/intltool-0.51.0/intltool-0.51.0.tar.gz ' wget: /opt/openwebrtc-0.3/lib/libcrypto.so.1.0.0: no version information available (required by wget) wget: /opt/openwebrtc-0.3/lib/libssl.so.1.0.0: no version information available (required by wget) --2017-12-18 17:07:34--  https://gstreamer.freedesktop.org/src/mirror/intltool-0.51.0.tar.gz Resolving gstreamer.freedesktop.org (gstreamer.freedesktop.org)... <IP_ADDRESS>, 2610:10:20:722:a800:ff:feda:470f Connecting to gstreamer.freedesktop.org (gstreamer.freedesktop.org)|<IP_ADDRESS>|:443... connected. ERROR: cannot verify gstreamer.freedesktop.org's certificate, issued by ‘/C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3’:   Unable to locally verify the issuer's authority. To connect to gstreamer.freedesktop.org insecurely, use --no-check-certificate'.
Recipe 'intltool' failed at the build step 'fetch'
Select an action to proceed:
[0] Enter the shell
[1] Rebuild the recipe from scratch
[2] Rebuild starting from the failed step
[3] Skip recipe
[4] Abort
Thanks,
Hari.

Hi,
Sorry for the really late answer, you probably fixed that already but maybe this can help someone that have your same problem.
I had a similar issue and I fixed it using this command:
git config --global user.email<EMAIL_ADDRESS>just insert your actual email instead of<EMAIL_ADDRESS>Hope this can help someone out there.


[messagingextension][docenhance][1553330]

Added note to show the difference in behavior when you select action.submit Please review.

Docs Build status updates of commit aabb47d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/messaging-extensions/how-to/action-commands/respond-to-task-module-submit.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel