Adds Link checker and fixes internal links

Description

Adds a Link checker plugin to the project website.
Fixes broken internal links in the project website

Issues Resolved
#206
By submitting this pull request, I confirm that my contribution is made under the terms of the BSD-3-Clause License.

So, I did test this out on my other machine, but I'm using a temp machine with an older version of Ruby and it seems to be throwing an error message:
/.gem/ruby/2.4.5/gems/jekyll-4.2.0/lib/jekyll/external.rb:60:in `require': /repos/ashwin-project-website/_plugins/link-checker.rb:95: syntax error, unexpected ']' (SyntaxError)
+[^>]+(?:id|name)="#{href[1..]}"/i).nil?
                              ^
/repos/ashwin-project-website/_plugins/link-checker.rb:96: syntax error, unexpected tCONSTANT, expecting tSTRING_DEND
        @failures << "Process:: ##{href[1..]}, linked in ./
                             ^
/repos/ashwin-project-website/_plugins/link-checker.rb:100: syntax error, unexpected keyword_end, expecting tSTRING_DEND
      end
         ^
/repos/ashwin-project-website/_plugins/link-checker.rb:229: syntax error, unexpected keyword_end, expecting tSTRING_DEND
/repos/ashwin-project-website/_plugins/link-checker.rb:253: syntax error, unexpected end-of-input, expecting tSTRING_DEND
	from /.gem/ruby/2.4.5/gems/jekyll-4.2.0/lib/jekyll/external.rb:60:in `block in require_with_graceful_fail'
	from /.gem/ruby/2.4.5/gems/jekyll-4.2.0/lib/jekyll/external.rb:57:in `each'
	from /.gem/ruby/2.4.5/gems/jekyll-4.2.0/lib/jekyll/external.rb:57:in `require_with_graceful_fail'
	from /.gem/ruby/2.4.5/gems/jekyll-4.2.0/lib/jekyll/plugin_manager.rb:89:in `block in require_plugin_files'
	from /.gem/ruby/2.4.5/gems/jekyll-4.2.0/lib/jekyll/plugin_manager.rb:87:in `each'
	from /.gem/ruby/2.4.5/gems/jekyll-4.2.0/lib/jekyll/plugin_manager.rb:87:in `require_plugin_files'
	from /.gem/ruby/2.4.5/gems/jekyll-4.2.0/lib/jekyll/plugin_manager.rb:21:in `conscientious_require'
	from /.gem/ruby/2.4.5/gems/jekyll-4.2.0/lib/jekyll/site.rb:131:in `setup'
	from /.gem/ruby/2.4.5/gems/jekyll-4.2.0/lib/jekyll/site.rb:36:in `initialize'
	from /.gem/ruby/2.4.5/gems/jekyll-4.2.0/lib/jekyll/commands/build.rb:30:in `new'
	from /.gem/ruby/2.4.5/gems/jekyll-4.2.0/lib/jekyll/commands/build.rb:30:in `process'
	from /.gem/ruby/2.4.5/gems/jekyll-4.2.0/lib/jekyll/command.rb:91:in `block in process_with_graceful_fail'
	from /.gem/ruby/2.4.5/gems/jekyll-4.2.0/lib/jekyll/command.rb:91:in `each'
	from /.gem/ruby/2.4.5/gems/jekyll-4.2.0/lib/jekyll/command.rb:91:in `process_with_graceful_fail'
	from /.gem/ruby/2.4.5/gems/jekyll-4.2.0/lib/jekyll/commands/serve.rb:86:in `block (2 levels) in init_with_program'
	from /.gem/ruby/2.4.5/gems/mercenary-0.4.0/lib/mercenary/command.rb:221:in `block in execute'
	from /.gem/ruby/2.4.5/gems/mercenary-0.4.0/lib/mercenary/command.rb:221:in `each'
	from /.gem/ruby/2.4.5/gems/mercenary-0.4.0/lib/mercenary/command.rb:221:in `execute'
	from /.gem/ruby/2.4.5/gems/mercenary-0.4.0/lib/mercenary/program.rb:44:in `go'
	from /.gem/ruby/2.4.5/gems/mercenary-0.4.0/lib/mercenary.rb:21:in `program'
	from /.gem/ruby/2.4.5/gems/jekyll-4.2.0/exe/jekyll:15:in `<top (required)>'
	from /.gem/ruby/2.4.5/bin/jekyll:23:in `load'
	from /.gem/ruby/2.4.5/bin/jekyll:23:in `<top (required)>'
	from /.rubies/ruby-2.4.5/lib/ruby/site_ruby/2.4.0/bundler/cli/exec.rb:63:in `load'
	from /.rubies/ruby-2.4.5/lib/ruby/site_ruby/2.4.0/bundler/cli/exec.rb:63:in `kernel_load'
	from /.rubies/ruby-2.4.5/lib/ruby/site_ruby/2.4.0/bundler/cli/exec.rb:28:in `run'
	from /.rubies/ruby-2.4.5/lib/ruby/site_ruby/2.4.0/bundler/cli.rb:481:in `exec'
	from /.rubies/ruby-2.4.5/lib/ruby/site_ruby/2.4.0/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
	from /.rubies/ruby-2.4.5/lib/ruby/site_ruby/2.4.0/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
	from /.rubies/ruby-2.4.5/lib/ruby/site_ruby/2.4.0/bundler/vendor/thor/lib/thor.rb:392:in `dispatch'
	from /.rubies/ruby-2.4.5/lib/ruby/site_ruby/2.4.0/bundler/cli.rb:31:in `dispatch'
	from /.rubies/ruby-2.4.5/lib/ruby/site_ruby/2.4.0/bundler/vendor/thor/lib/thor/base.rb:485:in `start'
	from /.rubies/ruby-2.4.5/lib/ruby/site_ruby/2.4.0/bundler/cli.rb:25:in `start'
	from /.rubies/ruby-2.4.5/lib/ruby/gems/2.4.0/gems/bundler-2.2.25/exe/bundle:49:in `block in <top (required)>'
	from /.rubies/ruby-2.4.5/lib/ruby/site_ruby/2.4.0/bundler/friendly_errors.rb:128:in `with_friendly_errors'
	from /.rubies/ruby-2.4.5/lib/ruby/gems/2.4.0/gems/bundler-2.2.25/exe/bundle:37:in `<top (required)>'
	from /.gem/ruby/2.4.5/bin/bundle:23:in `load'
	from /.gem/ruby/2.4.5/bin/bundle:23:in `<main>'

Is there something required as far as version of Ruby for this?

Interesting, the version i have on my system is ruby 2.7.0p0 (2019-12-25 revision 647ee6f091) [x86_64-linux-gnu]. This code is almost identical to the link checker on the documentation website

Ive updated the PR to fix both internal and external links and rebased the commit to be on top of the latest changes in main.

@ashwin-pc OK. Looks like Jekyll requires ruby 2.5, so that's the source of the error I was getting on the other machine.
Can we add something to the README file with your info on JEKYLL_LINK_CHECKER, etc. info? I don't want that information to only exist in this PR.
Otherwise, I've checked everything and I'll merge after you add that bit in the readme.

Good point! I've added the instructions to the readme.

Thanks @ashwin-pc!


Ehancements of Backend Controller

Hello.
Thank you for your project. I actually forked it for a project for the city of Toulouse (FR).
During our usage, we faced two issues about the BackendController.
First of all, the @RestController used on the top of the class force @ResponseBody to all the methods; this sometimes causes the text "forward:/" to be displayed as response content. With the usage of @Controller with @ResponseBody only on JSON-format output methods; the controller correctly forward to frontend. To avoid that, you should probably seperated forward @Controller, and security @RestController in two separated controllers.
Secondly, with have some routes /admin/users for ex. in our projet. Your regexp path for the forward method does not currently accept several level of paths for Vue Router.
I hope this could help; thx you again for your REALLY nice base project for SB/VueJS  :)
Regards

Thank you very much for your feedback @AlexandreClose Really happy to hear that the project was/is of help to you! Thanks also for the PR :octocat:


Add settings in Rails example to ignore false positives from Rails ActiveStorage and ActionText

First step towards fixing issue #52

Hey, thank you for your contribution!


.idea directory shouldn't be part of node package

This is strange, .idea is part of .gitignore and as such should also be ignored by npm. Maybe it's because of the missing slash? https://github.com/kaliber5/ember-bootstrap/blob/master/.gitignore#L20
Though git seems to accept this...

Thanks anyways!

@simonihmig
https://github.com/npm/npm/issues/3763#issuecomment-22255799
npm respects .gitignore only if there is no .npmignore
Welcome :wink:

Oh, did't know that, thanks for teaching me this! ;)


Support get sats/BTC balance for address (REST API)

Similar to get runes balances API, could we have one that returns sats?

Similar to get runes balances API, could we have one that returns sats?

this curl command works for me - how about you?
curl -s 'https://ordinals.com/address/bc1pqaxt572lqqrpvvxajfxltjhq0et37ynczfxty8zz53phnqyuht4sutx04y' | grep -A 1 '
sat balance
' | tail -n 1 | sed 's/<\/\?dd>//g; s/^[ \t]*//; s/[ \t]*$//'

We should put it in the JSON API though. Should be a super easy PR. Does one of you want to try it? @cryptoni9n @kevinfaveri

We should put it in the JSON API though. Should be a super easy PR. Does one of you want to try it? @cryptoni9n @kevinfaveri

thanks raph, I'll take a stab at it shortly.

@raphjaph @kevinfaveri how does this look?

Perfect!

while we are at it, can we also add rune balances too? to have it with the parity of html page. @cryptoni9n @raphjaph

oh it has now, it's just not released it yet.

while we are at it, can we also add rune balances too? to have it with the parity of html page. @cryptoni9n @raphjaph

yes and also inscription ids

while we are at it, can we also add rune balances too? to have it with the parity of html page. @cryptoni9n @raphjaph

yes and also inscription ids

I have added it in this PR by the way 🤝 https://github.com/ordinals/ord/pull/3924

I have added it in this PR by the way 🤝 #3924

merged


Fix the DB username can't contain "@" character

If  user name of DB contains"@" char, the sqlcon can't connect to the DB.
The DSN example is as following:
DSN=mysql://sa@test.mysql.database.azure.com:MyPassword@(<IP_ADDRESS>:3306)/hydra
This PR do a very simple fix.

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

Thank you!


BUG: not all status tags visible in project status selection

When defining a project the status 'OPEN' I've created is not visible for selection

Thanks and closed.


Lambda forces disconnect on code completion

This change makes our Javabuilder lambdas disconnect from the client on code completion.
Testing story
I was only able to test this change via Postman, with my deployed development version of Javabuilder. Here's what running the default code on /s/allthethings/lessons/44/levels/8 (prints hello world) produced without this change:

Here's with the change:

LGTM!
A couple things I checked:

does the SQS get deleted? (i.e. does the delete action get called via API Gateway) - yes
does the client gracefully handle cases where it tries to close the connection, but the server's already closed it? - yes
does the server gracefully handle cases where it tries to close the connection, but the client's already closed it? - I think so - deleteConnection seems to return a result object rather than throwing an exception

Happy to chat through any of these if you'd like!

Would love to talk through how you tested these things when you have a minute!


Issue in creating custom Objective function

How can you create your own objective function, I tried to create a very basic objective function but it gives an error and I there is no way to know the size of the parameters passed to the function at run time.
def loss(y_true,y_pred):
    loss = T.vector('float64')
    for i in range(1):
        flag = True
        for j in range(y_true.ndim):
            if(y_true[i][j] == y_pred[i][j]):
                flag = False
        if(flag):
            loss = loss + 1.0
    loss /= y_true.shape[0]
    print loss.type
    print y_true.shape[0]
    return loss

I get this error saying
model.compile(loss=loss, optimizer=ada)
  File "/usr/local/lib/python2.7/dist-packages/Keras-0.0.1-py2.7.egg/keras/models.py", line 75, in compile
    updates = self.optimizer.get_updates(self.params, self.regularizers, self.constraints, train_loss)
  File "/usr/local/lib/python2.7/dist-packages/Keras-0.0.1-py2.7.egg/keras/optimizers.py", line 113, in get_updates
    grads = self.get_gradients(cost, params, regularizers)
  File "/usr/local/lib/python2.7/dist-packages/Keras-0.0.1-py2.7.egg/keras/optimizers.py", line 23, in get_gradients
    grads = T.grad(cost, params)
  File "/usr/local/lib/python2.7/dist-packages/theano/gradient.py", line 432, in grad
    raise TypeError("cost must be a scalar.")
TypeError: cost must be a scalar.

Now if I change the code at the second line , it shows this error
loss = T.scalar('float64')

Error:
model.compile(loss=loss, optimizer=ada)
  File "/usr/local/lib/python2.7/dist-packages/Keras-0.0.1-py2.7.egg/keras/models.py", line 75, in compile
    updates = self.optimizer.get_updates(self.params, self.regularizers, self.constraints, train_loss)
  File "/usr/local/lib/python2.7/dist-packages/Keras-0.0.1-py2.7.egg/keras/optimizers.py", line 113, in get_updates
    grads = self.get_gradients(cost, params, regularizers)
  File "/usr/local/lib/python2.7/dist-packages/Keras-0.0.1-py2.7.egg/keras/optimizers.py", line 23, in get_gradients
    grads = T.grad(cost, params)
  File "/usr/local/lib/python2.7/dist-packages/theano/gradient.py", line 529, in grad
    handle_disconnected(elem)
  File "/usr/local/lib/python2.7/dist-packages/theano/gradient.py", line 516, in handle_disconnected
    raise DisconnectedInputError(message)
theano.gradient.DisconnectedInputError: grad method was asked to compute the gradient with respect to a variable that is not part of the computational graph of the cost, or is used only by a non-differentiable operator: <TensorType(float64, matrix)>

Is there something I am missing about how to create new objective functions because this is all I was able to understand from the limited documentation and examples about creating custom objective functions

Is there something I am missing

You are missing the basics of writing Theano code. It's a symbolic tensor manipulation language, it doesn't work like Numpy. Here's a start: http://deeplearning.net/software/theano/tutorial/index.html#tutorial

Yes, I am new to writing Theano code. I also saw that all the objective functions in https://github.com/fchollet/keras/blob/master/keras/objectives.py call Theano tensor functions so tried doing this, I copy pasted the categorical crossentropy code from objectives.py and pasted it into my code no changes made
def categorical_crossentropy(y_true, y_pred):
    '''Expects a binary class matrix instead of a vector of scalar classes
    '''
    y_pred = T.clip(y_pred, epsilon, 1.0 - epsilon)
    # scale preds so that the class probas of each sample sum to 1
    y_pred /= y_pred.sum(axis=-1, keepdims=True)
    cce = T.nnet.categorical_crossentropy(y_pred, y_true)
    return cce

I still get the same error:
TypeError: cost must be a scalar.

This should work if you have properly defined T and epsilon and your inputs are in the correct format. See the example below:
import theano.tensor as T
import theano
from keras.utils.np_utils import to_categorical
import numpy as np

if theano.config.floatX == 'float64':
  epsilon = 1.0e-9
else:
  epsilon = 1.0e-7

def categorical_crossentropy(y_true, y_pred):
    '''Expects a binary class matrix instead of a vector of scalar classes
    '''
    y_pred = T.clip(y_pred, epsilon, 1.0 - epsilon)
    # scale preds so that the class probas of each sample sum to 1
    y_pred /= y_pred.sum(axis=-1, keepdims=True)
    cce = T.nnet.categorical_crossentropy(y_pred, y_true)
    return cce

y_true = T.matrix()
y_pred = T.matrix()
loss_fun = theano.function([y_true, y_pred], categorical_crossentropy(y_true,y_pred))

ytrue = np.asarray(to_categorical(np.random.randint(5,size=10)), dtype=theano.config.floatX)
ypred = np.asarray(np.random.rand(10,5), dtype=theano.config.floatX)
ypred = ypred/np.expand_dims(np.sum(ypred,-1),1) # class probabilities should sum up to 1
loss = loss_fun(ytrue, ypred)

The output is a cost for every sample (here: 10), which keras will sum up automatically.
Note that keras will take care of compiling your loss function (theano.function(...)). You simply have to provide a function that can handle symbolic Theano expressions. Make sure that the outputs of the previous layer conform to what the cost function expects.


problem with custom widget class

hi once again,
i add class to custom widget using re.addClass the class added but it cant find those classes although i added.. is it something missing ???

addWidget() {      const ref: MyWidgetComponent = this.dashboard.addItem(MyWidgetComponent);      ref.setSize([this.static_width, this.static_height]);      ref.addClass('notes-box')      ref.widgetId = '123123';      ref.type = 'notes';      ref.title = 'notes';      ref.content = 'notes';      ref.close = this.close;      ref.dashboard = this.dashboard;   }

it works when i add class in main index.html file

I think that if you call it directly after adding the widget on dashboard it will not work because widget is not ready yet you need to listen for AfterViewInit event of your widget component and do it here (or after this event when the widget is ready)

@waleed-sarwar is it ok ?

Closing this one as the problem is not part of this library

yes its ok


[bugfix] Fix deadlock in test_cancel for pbs-based schedulers

Create the stdout, stderr files if the don't exist
to make the torque scheduler treat the job as finished.

Fixes #1298

I think the problem is more fundamental, because this deadlock could happen in normal operation. I guess that a better solution would be to fix that in the PBS/Torque backends, such that if the job is cancelled, we should not do the additional check for its stdout/stderr files to mark it as done.

Then maybe open a new issue to find a fundamental solution, while temporarily have this one so that it does not block the CI?

Then maybe open a new issue to find a fundamental solution, while temporarily have this one so that it does not block the CI?

No, the solution is quite easy. Set an is_cancelling flag that will be set when cancel() is called and the finished() should simply do the additional check only if this flag is not set.


Internal Error 500 while opening issue with attached file(s)

Hi,
I met a misbehaviour of onlyoffice-redmine plugin while opening an issue with attached file(s). As I understand it can't manipulate with file extension in code (production.log):
`I, [2022-08-24T12:50:58.420840 #1]  INFO -- :   Rendered issues/show.html.erb (Duration: 341.5ms | Allocations: 127861)
I, [2022-08-24T12:50:58.426989 #1]  INFO -- :   Rendered plugins/onlyoffice_redmine/app/views/issues/show.html.erb within layouts/base (Duration: 347.9ms | Allocations: 129983)
I, [2022-08-24T12:50:58.427191 #1]  INFO -- :   Rendered layout layouts/base.html.erb (Duration: 348.1ms | Allocations: 130011)
I, [2022-08-24T12:50:58.427711 #1]  INFO -- : Completed 500 Internal Server Error in 418ms (ActiveRecord: 71.2ms | Allocations: 144875)
F, [2022-08-24T12:50:58.429942 #1] FATAL -- :
ActionView::Template::Error (undefined method + for nil:NilClass):
42:     @issue.attachments.each do |attachment|
43:       is_editable_array = is_editable_array + [DocumentHelper.is_editable(attachment)]
44:       attachments_disk_filenames = attachments_disk_filenames + [attachment.disk_filename]
45:       ext = attachment.disk_filename[attachment.disk_filename.index(".")+1..]
46:       is_convert = is_convert + [FormatUtility.format_supported(ext).length != 0]
47:     end
48:   %>
plugins/onlyoffice_redmine/app/views/issues/show.html.erb:45
plugins/onlyoffice_redmine/app/views/issues/show.html.erb:42
app/controllers/issues_controller.rb:118:in block (2 levels) in show
app/controllers/issues_controller.rb:110:in show
lib/redmine/sudo_mode.rb:61:in sudo_mode_`
Could someone point me how to fix problem?

This github version has errors and compatibility issue. I make a modified working version, but I do not know how to use github to request a pull. So I put the fixed version here
https://drive.google.com/drive/folders/18RUVPV9LhsXmqTQ5BQqcxQGhkdJ5EYlG?usp=sharing
Hope it helps
Regards,

Please check if the issue persists with the recently released version 3.0 of the plugin.


broken link

windows defender antivirus group policy ADMX templates link is broken.
I like to add the link of  November 1909 administrative templates.

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

ID: 65f5f37f-9e03-eac1-715b-4a01acfff33e
Version Independent ID: b7e76481-3859-c8d1-c22d-ee238fadd1e9
Content: Use PowerShell cmdlets to configure and run Windows Defender AV - Windows security
Content Source: windows/security/threat-protection/windows-defender-antivirus/use-powershell-cmdlets-windows-defender-antivirus.md
Product: w10
Technology: windows
GitHub Login: @denisebmsft
Microsoft Alias: deniseb

@RAJU2529 - Thank you for submitting feedback.
From our understanding, the issue has been resolved based on this merged commit https://github.com/MicrosoftDocs/windows-itpro-docs/commit/90bb3edaec2d834af492d13b3b38437ba47341e7.
Thank you for your contribution to make the docs better! Much appreciated!


Update main.lua

Fixed typo

The typo that affected nothing got fixed by the demo getting rewritten. Thank you stranger, for such out of nowhere merge request.


The ember-headless-form-changeset example in the docs does not work

I have followed the installation steps for this addon and ember-changeset/ember-changeset-validations. Using the example you provide I found two issues:

because the validate-changeset helper has no arguments @validate={{validate-changeset}} resulted in an error and required @validate={{helper "validate-changeset"}} instead; and

more crucially, I get the Unhandled Promise Rejection: TypeError: this.args.validate is not a function. (In 'this.args.validate?.(this.internalData,Array.from(this.fields.keys()))', 'this.args.validate' is an instance of CurriedValue) on submission of an empty form.

Steps to replicate

Clone the repo: https://github.com/roomman/ember-headless-forms-changeset-test
npm install
ember s
Click on the "Submit" button

This should be enough to replicate and view the error.
I hope this is helpful. 👍🏻

Importing the helper into the backing class and exposing it via a getter works around this for me:
// test-form.ts
import Component from '@glimmer/component';
+ import { validateChangeset } from 'ember-headless-form-changeset';

export default class TestFormComponent extends Component {
  data: MyFormData = {};

+  get validateHelper() {
    return validateChangeset;
  };

  validations = {
    name: validatePresence(true),
    email: validateFormat({ type: 'email' }),
  };

  handleSubmit({ firstName, email }: MyFormData) {
    alert(`Hello ${firstName} with email ${email}!`);
  }
}

// test-form.hbs
<HeadlessForm
  @data={{changeset this.data this.validations}}
  @dataMode="mutable"
  @onSubmit={{this.handleSubmit}}
  @validate={{this.validateHelper}}
  as |form|
>
  <form.Field @name="name" as |field|>

      <field.Label>Name</field.Label>
      <field.Input class="border rounded px-2" />
      <field.Errors />

  </form.Field>

  <form.Field @name="email" as |field|>

      <field.Label>Email</field.Label>
      <field.Input class="border rounded px-2" />
      <field.Errors />

  </form.Field>

  <button type="submit">Submit</button>
</HeadlessForm>

Thanks for reporting, and sorry for the late feedback!
I was able to reproduce this, not only in your reproduction case (thanks for that!), but also in our docs-app. The reason this was not detected before:

in the test-app we use <template> (strict mode templates), with no helper or component resolution at all, instead explicit imports
the docs-app runs with Embroider, which seems to behave differently regarding helper reolution (switching to a classic build revealed the error!)

{{validate-changeset}} is indeed special: helpers are normally functions, that return a value. In the case of {{validate-yup schema}} it is a function that returns a function (which maps validation errors from yup format to headless-form). But in the case of {{validate-changeset}}, we are not expecting any arguments, so we didn't even invoke the helper (which would also have to return a function then), we just passed it as-is. This worked in the above cases, but was probably not a good design choice, for the bug reported here but also consistency.
The bug fix will probably be to make {{validate-changeset}} a higher-order function as the other, so you have to invoke the helper to get the actual function back. This will be a breaking change (glad we haven't released 1.0.0 yet 😅), the usage will change from @validate={{validate-changeset}} to @validate={{(validate-changeset)}}.
Will work on a PR tomorrow!
/cc @ynotdraw @nicolechung


TRY/EXCEPT not working in Teardown

Failing keywords in teardown are not handled with TRY/EXCEPT:
Sample robot file:
*** Settings ***
Test Teardown  TeardownKW

*** Keywords ***
TeardownKW
    TRY
        Fail  1
        Fail  2
        RETURN
    EXCEPT
        Log  err handled
    END

*** Test Cases ***
DraftTest
    Log  This test is used for experiments.

Results in:

Expected: Keywords Fail 2 and RETURN should not be executed due to Fail 1 is failing.
Tested in RF version 5.0 and 5.1a2

Failures don't stop execution in teardown because we want all cleanup activities to be done. That means TRY/EXCEPT structures work differently in teardowns than elsewhere and this was already reported as #4293. As you can see in the comments of that issue, we decided not to change this because teardown behavior changing inside TRY/EXCEPT would have been strange and also complicated to implement. We instead decided to make it possible to explicitly disable the continue-on-failure mode that's automatically on in teardowns. For more details about that see #4303.


Frontend : Add Eslint and prettier for code formate!

Is your feature request related to a problem?
Error detection: ESLint analyzes JavaScript code and identifies potential errors, such as syntax mistakes, variable misuse, undeclared variables, and more. It helps catch these issues early in the development process, reducing bugs and improving code reliability.
Code style enforcement: ESLint enforces coding style guidelines and conventions. It can detect and flag inconsistencies in code formatting, such as indentation, whitespace usage, line length, and the placement of semicolons. This promotes readability and makes the codebase more maintainable.
Best practices enforcement: ESLint provides rules that enforce JavaScript best practices. It helps identify potential issues or anti-patterns that could lead to bugs or performance problems. For example, it can flag the use of deprecated or unsafe APIs, suggest more efficient alternatives, or enforce the use of certain language features for better code quality.
Customizability: ESLint offers a wide range of configuration options and extensibility. It allows developers to tailor linting rules based on their specific project requirements, coding style preferences, or coding guidelines established within their team or organization.
Integration with development workflows: ESLint seamlessly integrates with various development tools and workflows, including text editors, IDEs, build systems, and continuous integration (CI) pipelines. It provides real-time feedback and can be configured to run automatically as part of the development process, ensuring code quality is maintained throughout the project lifecycle.
Describe the solution you'd like
I would like to add configuration.

@J0SAL Hey!! check the feature and assign it to me!!

Hey @Hareesh108, we don't need this for now


Downloads fail from SBS

Checklist

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

Verbose log

PASTE VERBOSE LOG HERE

Description

WRITE DESCRIPTION HERE

Issue resolved. The new url format was slightly different to what it used to be. A few days ago the url had the following format
https://www.sbs.com.au/ondemand/video/1911251011518/believe
The new format is
https://www.sbs.com.au/ondemand/movie/believe/1911251011518 - this url does NOT work with youtube-dl and produces the error mentioned above
However, if I use this old format, youtube-dl downloads successfully.
Also, this one works too.
https://www.sbs.com.au/ondemand/watch/1911251011518 which is which is the url that gets displayed when one presses the play button.
Thanks

I think I have a fix for this.  I'm about to work out how to submit a pull request - I'll post the link when I've done it.
For those who want to try it in the meantime, and who are comfortable changing a line in a Python file, here's what's required:

NOTE: I'm doing this on the latest source version from Github. If you're on an earlier version, the line number below may be different
Find the file youtube_dl/extractor/sbs.py, and open it in a text editor
Go to line 13 (?) where _VALID_URL is defined
Change the definition from:

_VALID_URL = r'https?://(?:www.)?sbs.com.au/(?:ondemand(?:/video/(?:single/)?|.*?\bplay=|/watch/)|news/(?:embeds/)?video/)(?P[0-9]+)'

to:

_VALID_URL = r'https?://(?:www.)?sbs.com.au/(?:ondemand(?:/movie/.?/|/video/(?:single/)?|.?\bplay=|/watch/)|news/(?:embeds/)?video/)(?P[0-9]+)'

Pull request submitted.  See #29644

@captsens - thanks very much. I am using the binary so will have to wait for the next update. Thanks again.


Implement new _transform methods in BatchTransformerMixins

Now that we have added the functionality thanks to #69 we should implement batch processing for transformers that can gain from it. This includes a fair chunk of the API and Google transformers.

Per discussion, closing this for now because it's not clear that batch-processing images within API Extractors is going to provide enough benefit to warrant the time investment. Most APIs charge on a per-file basis, so sending multiple files will, at best, save some (but probably not much) overhead on the request and response.

Reopening because found notable performance differences for the Clarifai API


ORMs using node-sql?

I'm kinda ticked off that it's 2016 and not a single node ORM uses SQL correctly. None of them use prepared statements / parameterized queries.
The good news though is that at least 3 of them (bookshelf, objection.js, firenze) use a single query-building library called knex.
If node-sql (or a wrapper to node-sql) conformed to knex's API, then all 3 of those ORMs would suddenly "do SQL right".

Looks like Waterline should make this fairly simple to do! 😄
If I manage to create a Waterline adapter for node-sql I'll be sure to update this issue. Note there's also a feature-fork of it called Offshore.

sounds good! thanks!
On Thu, Jun 2, 2016 at 10:16 PM, Greg Slepak<EMAIL_ADDRESS>wrote:

Looks like Waterline https://github.com/balderdashy/waterline should
make this fairly simple to do! 😄
If I manage to create a Waterline adapter for node-sql I'll be sure to
update this issue. Note there's also a feature-fork of it called Offshore
https://github.com/Atlantis-Software/offshore.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/brianc/node-sql/issues/320#issuecomment-223481207,
or mute the thread
https://github.com/notifications/unsubscribe/AADDoWxvH-LEtiFFF6JJ476-hhCp445-ks5qH5yfgaJpZM4ItFPZ
.

It turns out that Knex actually does do parameterized queries, so I ended up going with objection.js for the ORM. However, the good news is that objection.js is just a thin wrapper around Knex, and theoretically it would be fairly simple to create a node-sql version of it (if someone wanted to give that a try).
Closing this issue since I (unfortunately) don't have the time available to work on that.


Removes _lastUpdated and _id from search param tables

Description

Store the resource type ID in all search param and compartment assignment table. It will not be an index column, but it is available for filtering on.
Do not store the resource id as in the TokenSearchParam table as the _id search param. It is already on the Resource table. The same for _lastUpdated in the DateTimeSearchParam.

Related issues
Addresses AB#69044

CREATE NONCLUSTERED INDEX IX_StringSearchParam_SearchParamId_TextWhereNoOverflow

Wrong index name?

Refers to: src/Microsoft.Health.Fhir.SqlServer/Features/Schema/Migrations/1.sql:489 in 68d685c. [](commit_id = 68d685cdbbe49f1e9dc643a40dbf063b50297f17, deletion_comment = False)

CREATE NONCLUSTERED INDEX IX_StringSearchParam_SearchParamId_TextWhereNoOverflow

Wrong index name?

Refers to: src/Microsoft.Health.Fhir.SqlServer/Features/Schema/Migrations/1.sql:489 in 68d685c. [](commit_id = 68d685cdbbe49f1e9dc643a40dbf063b50297f17, deletion_comment = False)

CREATE NONCLUSTERED INDEX IX_StringSearchParam_SearchParamId_TextWhereNoOverflow

Wrong index name?
Refers to: src/Microsoft.Health.Fhir.SqlServer/Features/Schema/Migrations/1.sql:489 in 68d685c. [](commit_id = 68d685c, deletion_comment = False)

Fixing in #474


FRAME: Minor fix for failsafe.

As per https://github.com/paritytech/substrate/pull/12951#discussion_r1141335468

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2605117

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2607101


Output correct barcodes to Preparation Sheet

Barcodes in the mapping file (i.e., prep information sheet) are not correct--i.e., do not match those in the preparation sheet generated by wet lab via existing process--and do not seem to appear in EMP barcode list at all.
Raised in amplicon walkthrough 07/30/2018

Confirmed: checking a small sampling of the 16S barcodes in the known-good prep info file provided by the lab shows that they either don't appear in among those in the labman database (which are populated by db_patch_manual.sql) or they appear but are said to be on different plates than they should be.  Hopefully this just means we need to update db_patch_manual.sql with the correct info.


Open VSX Hosting

Hi,
Will this extension be published to https://open-vsx.org
Just for some background info, this is an open source vscode registry used by the eclipse foundation and there new project theia (https://theia-ide.org/) an open source ide based on the open source code from vscode.

I think it is already there. See: https://github.com/GabrielBB/vscode-lombok/issues/41


Java version for Nextflow (r 1.2.1) version 20.01.0

Hello Team
I am trying to replicate my old nfcore-ChipSeq run using Nextflow version 20.01.0.
Unfortunately our server team recently updated the nextflow versions. all dependent packages including JAVA was also updated simultaneously. This has resulted in old nfcore-chipseq script not working anymore.
Can you tell me which JAVA and other packages and their version which Nextflow version 20.01.0 is using?
Any help will be appreciated.
Thanks
-Biju Issac

Hi @bijuissacch224610, you can find the requirements in the documentation, see here.
Let us know if you have any further issues.

I will close the issue now, if you have any further questions please let us know.


[BUG]: DOCA TCP Sensitive Information Detection Example

Version
24.06
Which installation method(s) does this occur on?
Source
Describe the bug.
DOCA Source Stage originates from PreallocatorMixin which only works with MultiMessage and ControlMessage types. Although UDP examples (run_udp_raw.py and run_udp_convert.py) work well, the run_tcp.py example reports the following error.
RuntimeError: Additional columns were requested to be inserted into the Dataframe, but the output type morpheus.RawPacketMessage isn't a supported type

Forum post: https://forums.developer.nvidia.com/t/doca-sensitive-information-detection-example/294898/1
Minimum reproducible example
No response
Relevant log output
Click here to see error details
[Paste the error here, it will be hidden by default]

Full env printout
Click here to see environment details
# python3 ./examples/doca/run_tcp.py --nic_addr ca:00.0 --gpu_addr 17:00.0
...
====Building Pipeline Complete!====
E20240605 08:22:01.757285 14853 builder_definition.cpp:283] Exception during segment initializer. Segment name: linear_segment_0, Segment Rank: 0. Exception message:
RuntimeError: Additional columns were requested to be inserted into the Dataframe, but the output type morpheus.RawPacketMessage isn't a supported type
...
  File "/workspace/morpheus/pipeline/stage_base.py", line 396, in build
    out_ports_nodes = self._post_build(builder=builder, out_ports_nodes=out_ports_nodes)
  File "/workspace/morpheus/pipeline/single_output_source.py", line 72, in _post_build
    ret_val = self._post_build_single(builder, out_ports_nodes[0])
  File "/workspace/morpheus/pipeline/preallocator_mixin.py", line 131, in _post_build_single
    raise RuntimeError(msg)
RuntimeError: Additional columns were requested to be inserted into the Dataframe, but the output type morpheus.RawPacketMessage isn't a supported type

Other/Misc.
No response
Code of Conduct

[X] I agree to follow Morpheus' Code of Conduct
[X] I have searched the open bugs and have found no duplicates for this bug report

@e-ago it looks like you fixed this with PR #1728 is this issue good to close?


fix: highlight enum keyword

Fixes enum highlighting and corrects typo of deafult -> default. Also updates hightlight.js to latest version.
The issue was both the syntax of the keywords in beginKeywords (should be separated by space, not |), and the end regex which had a \( expression outside the [] matcher. Just leaving this here for future reference.
Related to https://github.com/flix/book/pull/104
Fixes #28

Thanks!


minor: convert if into a check

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Add possibility to delete users

Is your feature request related to a problem? Please describe.
n/a
Describe the solution you'd like
I believe it would be beneficial to include a delete option, accompanied by a confirmation prompt, within the three-dot menu in the user interface.

Perhaps it would be a good idea to add a delete button between the save and cancel buttons within the user edit menu.

Looks like you're trying to delete another admin user, first change the role to User and then you can delete the account.

Also why not just stick with the first account?


openPrivateChannel returns null

General Troubleshooting

[x ] I have checked for similar issues.
[x ] I have updated to the latest JDA version
[ x] I have checked the wiki and especially the FAQ section for similar questions.

Question
When I open a privatechannel it returns with null, how can I fix this?
My Code
PrivateChannel user1 = DiscordBot.shardMan.getUserById(448459851685822465L).openPrivateChannel().complete();

Already received in the Discord solution


Missing noSuchMethod-induced hashCode stub?

Consider the following program:
abstract class WeirdHashCode {
  Never get hashCode;
}

class SecretNonPrimitiveHashCode implements WeirdHashCode {
  noSuchMethod(Invocation invocation) {
    print('In noSuchMethod!');
    return 0;
  }
}

This program gives rise to a compile-time error from the analyzer:
Analyzing n013.dart...                 0.6s

  error • n013.dart:16:7 • 'Object.hashCode' ('int Function()') isn't a
          valid concrete implementation of 'WeirdHashCode.hashCode' ('Never
          Function()'). • invalid_implementation_override

1 issue found.

The CFE reports an error, too:
n013.dart:16:7: Error: The implementation of 'hashCode' in the non-abstract class 'SecretNonPrimitiveHashCode' does not conform to its interface.
class SecretNonPrimitiveHashCode implements WeirdHashCode {
      ^^^^^^^^^^^^^^^^^^^^^^^^^^
org-dartlang-sdk:///sdk/lib/_internal/vm/lib/object_patch.dart:24:11: Context: The return type of the method 'Object.hashCode' is 'int', which does not match the return type, 'Never', of the overridden method, 'WeirdHashCode.hashCode'.
Change to a subtype of 'Never'.
  int get hashCode => _getHash(this);
          ^
n013.dart:13:13: Context: This is the overridden method ('hashCode').
  Never get hashCode;
            ^

These error messages are consistent with a situation where SecretNonPrimitiveHashCode is a typical class.
However, SecretNonPrimitiveHashCode actually has a non-trivial noSuchMethod, which changes the rules when one or more members do not have an implementation with the required signature.
I think the expected behavior is that (1) we detect that SecretNonPrimitiveHashCode has a non-trivial noSuchMethod, and (2) it does not have an implementation of hashCode that is a correct override of the signature in the interface of SecretNonPrimitiveHashCode, and hence we should implicitly induce a noSuchMethod forwarder for hashCode with the required signature.
The program may not be very useful, but on the other hand it should not have any compile-time errors.

Given that this is a corner case, I'm going to initially give it a low priority. Please adjust the priority if you disagree.

My bad, the behavior is correct after all! (So, I'm closing the issue!)
The reason why we should not get an implicitly induced noSuchMethod forwarder is that it would override Object.hashCode respectively Object.[]. It's ok for a noSuchMethod forwarder to override another noSuchMethod forwarder, but there will not be any such forwarder in the case where it would override an explicitly declared method implementation.
The point is that it would be confusing and error-prone if an existing (visible) method implementation suddenly starts to throw (or behave in some other unexpected way) because we're actually calling an (invisible) noSuchMethod forwarder, just because we have chosen to say implements SomeClass, and SomeClass makes too big promises about the signature of some member.
So it's all working as intended. Sorry about the noise!


FEATURE: uses new topic footer button API

Conflicts should be good @ZogStriP
@romanrizzi can you review this and merge it if it looks good, just want to make sure it's not colliding with any of your recent work, thanks.


feat(view): process filter in view

Checklist

[x] npm test passes
[x] process filter
[x] commit message follows commit guidelines

Description of change

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

14 of 14 (100.0%)  changed or added relevant lines in 2 files are covered.
5 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.5%) to 66.309%

Files with Coverage Reduction
New Missed Lines
%

src/chart/view.ts
5
89.27%

Totals

Change from base Build<PHONE_NUMBER>:
0.5%

Covered Lines:
1356

Relevant Lines:
1930

💛  - Coveralls


moving out the extra view check in the bread controller

I didn't know that Laravel automatically looked inside of the /resources/views/vendor/{package} folder to override package views.
So, I'm reverting back my old change. My bad. Moving forward, I'm going to have someone else Merge my PR's. 👍

It's all good!


added missing assert package to package.json, fixed timezone issues.

Things fixed in this PR

Added missing assert package.
Fixed tests to reflect the API.
Fixed conversion and validation for different timezones as switching timezone would make the tests fail.
Add test case

Switching to another timezone would make a valid personnummer fail.
Had a problem with ts compilation, the code in the test file was unreachable. Did some investigation and fixed the issue by switching the place of the parameters to reflect assert.strictEqual(actual, expected)
strictEqual node doc

Terrific, thanks a lot! Will update the package.

Now shipped with version v2.1.0 :package: :ship:


Do not append Helm classifier in the tar files

As this seems to be included with systems like ArgoCD, we are not appending the classifier. Users that still want this behaviour, can use the new property quarkus.helm.tar-file-classifier=helm and the generated tar file will be generated as before <app name>-<app-version>-helm.tar.gz. I've also checked that this is how the Helm command line behaves when using helm package <chart name>.
Fix https://github.com/quarkiverse/quarkus-helm/issues/110

cc @csscriptplus


NNBD: Dart does not throw a compile error when declare a non-function typedef variable with unacceptable nullable type parameter

Dart VM version: 2.9.0-18.0.dev (dev) (Mon Jun 22 16:07:30 2020 +0200) on "windows_x64"
The following source code example declares a A<num?> variable for typedef A<X extends num>
class C<X> {}
typedef A<X extends num> = C<X?>;

main() {
  A<num?>? aaa = throw "Here is me";
}

Num? is not assignable to num, so compile error should be thrown here. However, dart does not throw it.
Sample output is:

$> dart --enable-experiment=nonfunction-type-aliases,non-nullable test.dart
Unhandled exception:
Here is me
#0      main (file:///D:/DART/sdk/tests/co19/src/LanguageFeatures/Simple-bounds/static/type-aliases/test.dart:5:18)
#1      _startIsolate. (dart:isolate-patch/isolate_patch.dart:301:19)
#2      _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:168:12)

This looks like a front-end issue as there is a missing compile-time error.
/cc @johnniwinther

Removing from NNBD since this requires nonfunction-type-aliases.

@eernstg is this still an issue?

Yes, the error message is still missing. The following variant avoids the throw (which helps avoid some potential confusion):
class C<X> {}
typedef A<X extends num> = C<X?>;

main() {
  A<num?>? aaa = null;
}

The following one does report the error, so this issue is associated with non-function type aliases:
class C<X> {}
typedef A<X extends num> = C<X?> Function();

main() {
  A<num?>? aaa = null;
}

@eernstg Are you looking into this or should someone from the CFE take over?

I think it would be nice if someone else took over—I'm trying to get the 2.11 stable spec done, and that keeps getting pushed ahead for various reasons. ;)

Sounds good.

This now works.

The fix for this issue was reverted due to a crash in google3, but will be re-landed soon. The re-landing CL is here: https://dart-review.googlesource.com/c/sdk/+/193401.


Add pre-commit config.

fixes #28

FYI: all the python files were updated automatically by the pre-commit hooks.


 So there is a conflict may be we should try specifying the gotoolchain version too

/unhold


Doc clarification

In this step in the readme, "open this folder in VS Code. In the Debug viewlet, run 'Launch Client' from drop-down to launch the extension and attach to the extension.", please be sure to specify that "this folder" means the client folder. I spent hours trying to debug from the root folder.

Sorry, this is for the language server example.

Fixed in https://github.com/Microsoft/vscode-extension-samples/pull/55


Article is no longer accurate

[Enter feedback here]
As of SQL 2017, adding an assembly requires signing and managing signatures, SAFE is no longer allowed apparently.
The complexity of this process is extreme and so a clear guide on how to do so would be expected here.

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

ID: a21d0936-6216-2251-6bdc-b1d7746c7039
Version Independent ID: cd19b31a-b56d-6958-a404-a5a04db7b4bc
Content: Deploying CLR Database Objects - SQL Server
Content Source: docs/relational-databases/clr-integration/deploying-clr-database-objects.md
Product: sql
Technology: clr
GitHub Login: @rothja
Microsoft Alias: jroth

@Pxtl Martin, thanks for the feedback and sorry for any confusion. Let me confirm your suggestion here with the product team and get back to you with my recommendations here. Thanks!

@Pxtl (and @WilliamAntonRohm and @rothja ): SAFE assemblies are still allowed, they just need to be signed. That is the main difference, though it is not a trivial one. The CLR strict security server configuration option added in SQL Server 2017 definitely over-complicates things, especially because there's no easy way to create an asymmetric key based on the public key of the strong-name key used to sign/strongly-name the assembly (please vote on this suggestion to hopefully make that happen: Allow Asymmetric Key to be created from binary hex bytes string just like CREATE CERTIFICATE ).
I have written a series of articles showing how to create publishable T-SQL scripts with no external DLL dependencies:

SQLCLR vs. SQL Server 2017, Part 2: “CLR strict security” – Solution 1
SQLCLR vs. SQL Server 2017, Part 3: “CLR strict security” – Solution 2

And, for unsigned, SAFE assemblies that already exist (typically in DBs upgraded/restored from prior versions), here is how to sign them in-place:

SQLCLR vs. SQL Server 2017, Part 4: “Trusted Assemblies” – The Disappointment (Msg 10314)

The documentation, in several places, states that all assemblies are now considered UNSAFE, and this is clearly incorrect ( SQLCLR vs SQL Server 2017, Part 9: Does PERMISSION_SET Still Matter, or is Everything Now UNSAFE? ). However, the situation is slightly more complicated and requires a little more investigation before I can submit a fix for that wording (am working on it, though).
Related info: Signing an Assembly = Signing with Strong Name Key #2052
Take care,
Solomon...
https://SqlQuantumLift.com/
https://SqlQuantumLeap.com/
https://SQLsharp.com/

@srutzky Solomon, thanks for the in depth analysis and pointer to your articles. Your expertise in this area continues to pay off for improvements to our docs that you suggest. Please do consider submitting a suggestion for us to get this messaging right, and I will approve it with the product team. @Pxtl Martin, can you take a look at the explanation and references that Solomon provides and see if that makes sense. Obviously, we still need to make the docs more clear, so apologies on the confusion.

@Pxtl Martin, since Solomon provided some guidance and plans an update in the near future, I am going to close out this git issue. But please let me know if you have any more questions or concerns. Thank you!


Focus on suggest box when it is clicked when in compact mode

Currently, when the suggest box is clicked when in compact mode, the nav view expands and displays the entire input box but doesn't focus into it and it needs an additional click into input box to trigger focus. It'd be better to focus on the input box when the nav view is expanded.
Suggest box doc with preview: https://metroui.org.ua/navview.html#_navview_pane_suggest-box

I will add this to 4.2.3. Wait for release.


Add "visual inspection" steps / links to the PR process

It's often difficult to "test" the visual style etc of a website, so we should make sure to add a few systematic visual checks to the built docs each time a PR is submitted. We should pick a few pages that demonstrate the breadth of functionality in jupyter-book and make sure that they look "correct" given a new change.

closing as this will be superceded by https://beta.jupyterbook.org/intro.html


SIT-2 Release [dev]

This PR marks the release of version 2.0.0, which corresponds to the completion of SIT-2. This PR is being merged back into dev per the nominal git & GitHub workflow and release workflow.

Seeing how we missed commits from the previous time of doing this, how would you feel about instead of going from v2.0.0 -> dev (currently done here), we go from main -> dev after v2.0.0 -> main? This would make the release a two-step dependent PR process instead of in parallel. Thoughts?

@greglucas I can't say I have a strong opinion here, and I think your proposed method would work just fine, though I think the workflow we are using here is sound. I think the main reason we missed commits this time around was because there were direct commits to main, which is something we should be really trying to avoid.
FWIW, I did a quick search of 'GitHub release workflow' and the vast majority of the diagrams have the release branch being merged into dev and main, which makes me think that this is an industry standard (I think people refer to this as "git Flow"). Not saying this is a good reason to stick with 'the norm' necessarily, but just wanted to point it out.

Sounds good to me! Lets stick with what you've got here then.
I think part of my confusion here may be this piece of text from the Atlassian doc "Once the release is ready to ship, it will get merged it into main and develop, then the release branch will be deleted." I'm generally used to keeping multiple release branches around, so we'd have branches: v1.x, v2.x, ... with our releases that we could backport things to if need be. The main branch here is really saying we are only going to have one supported release at all times I think? So in my mind I can switch "main" with "v2.x" and those would be analagous in our current situation.
Regardless, I say we're good to go here!

@greglucas I agree, I also like to keep release branches around for those reasons you mention. I'm not sure why Atlassian likes to delete theirs 😂


Fix related & linked with enum columns

PR Info

Resolve #374

Hey @MorganNesbitt, can you try this PR?
You can update your toml
sea-orm = { git = "https://github.com/SeaQL/sea-orm.git", branch = "issues/374", ... }

Can briefly explain what's the root cause?

hi @billy1624 that fixed the panic!
One thing I did notice now that I have a join working, is that it adds an order by id no matter what. which seemed odd, and when you add an order to the query it doesn't replace it just puts it right after.
A normal single query doesn't add an order, but the join does.
is this expected?
Below is what's being generated when I do a find_with_related but provide no order_by myself.
This is part of the debug that's being printed when I run the query
...
FROM
      "customer_employee_record"
      LEFT JOIN "historical_customer_employee_record" ON "customer_employee_record"."id" = "historical_customer_employee_record"."customerEmployeeRecordId"
    WHERE
      "customer_employee_record"."companyId" = $1
    ORDER BY
      "customer_employee_record"."id" ASC

hi @billy1624 that fixed the panic!
One thing I did notice now that I have a join working, is that it adds an order by id no matter what. which seemed odd, and when you add an order to the query it doesn't replace it just puts it right after.
A normal single query doesn't add an order, but the join does.
is this expected?
Below is what's being generated when I do a find_with_related but provide no order_by myself. This is part of the debug that's being printed when I run the query
...
FROM
      "customer_employee_record"
      LEFT JOIN "historical_customer_employee_record" ON "customer_employee_record"."id" = "historical_customer_employee_record"."customerEmployeeRecordId"
    WHERE
      "customer_employee_record"."companyId" = $1
    ORDER BY
      "customer_employee_record"."id" ASC

That additional order by is intended. If you look into the implementation of SelectTwoMany, you will notice that it consolidate single dimension query rows into nested result, Vec<(E::Model, Vec<F::Model>)>. Hence, the relative order of E::Model result and its related F::Model result is important.
https://github.com/SeaQL/sea-orm/blob/18ed68371238003cc39a13883f8c3a33256f46d9/src/executor/select.rs#L751-L785
(My explanation might be confusing loll)


reverting to Shapefile source for Broward as ESRI source no longer exists

Shapefile has been updated for 2020

This has since been updated in #6490


portico: Add /api links to /integrations.

Thir PR closes #11803
I did the following in this PR.
a) Add the custom section with all the links on the /integrations page.
b) Added the /api links, in the mobile drop down as well.
c) I broke down the .integration-category class into two parts named .integration-category_css and .integration-category_js
@rishig Please review.
Thanks

@sameerchoubey I noticed that this messes up the per-integration pages:

As a sidenote, when making visual changes, please include screenshots to show your work; it saves time in collaborating with reviewers.
What's the story with your adding the integration-category_js integration-category_css classes?  That seems like an awkward approach; I would imagine it'd be cleaner to keep the name integration-category for the JS purpose and make a new integrations-sidebar-link class used for the CSS purpose.

@timabbott Yeah. Initially, I wanted to break down the existing integration-category into CSS and JS. That's why I used. It may be awkward depending on the situation.
The links are working fine without any extra CSS. This is because I think that styling is probably given to the h4 tag.

Also, as of now, the https://zulipchat.com/integrations/doc/{integration_name} pages are broken. Below is a screenshot. So, I can open an issue for that.

Nice, merged as 2efe1963a5ec58bef310a7928753ad69fadfa429 after making a few small tweaks to labels and things.  @rishig FYI here are the screenshots for how this looks:

Mobile "categories" dropdown:

That other bug you mentioned is https://github.com/zulip/zulip/issues/11701.
Thanks @sameerchoubey!

Should we make these target=_blank?


Failing to build on Nix

Hyprland Version
 System/Version info
@nix { "action": "setPhase", "phase": "unpackPhase" }
Running phase: unpackPhase
unpacking source archive /nix/store/dpdlfy8v8y3pzc07k732i1nxmmsrpj32-source
source root is source
@nix { "action": "setPhase", "phase": "patchPhase" }
Running phase: patchPhase
@nix { "action": "setPhase", "phase": "updateAutotoolsGnuConfigScriptsPhase" }
Running phase: updateAutotoolsGnuConfigScriptsPhase
@nix { "action": "setPhase", "phase": "configurePhase" }
Running phase: configurePhase
fixing cmake files...
cmake flags: -GNinja -DCMAKE_FIND_USE_SYSTEM_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_BUILD_TYPE=RelWithDebInfo -DBUILD_TESTING=OFF -DCMAKE_INSTALL_LOCALEDIR=/nix/store/64ij5wjzrd2lzz3z91az755zwl4rnw6z-hyprland-0.40.0+date=2024-05-08_6a988d9/share/locale -DCMAKE_INSTALL_LIBEXECDIR=/nix/store/64ij5wjzrd2lzz3z91az755zwl4rnw6z-hyprland-0.40.0+date=2024-05-08_6a988d9/libexec -DCMAKE_INSTALL_LIBDIR=/nix/store/64ij5wjzrd2lzz3z91az755zwl4rnw6z-hyprland-0.40.0+date=2024-05-08_6a988d9/lib -DCMAKE_INSTALL_DOCDIR=/nix/store/64ij5wjzrd2lzz3z91az755zwl4rnw6z-hyprland-0.40.0+date=2024-05-08_6a988d9/share/doc/Hyprland -DCMAKE_INSTALL_INFODIR=/nix/store/64ij5wjzrd2lzz3z91az755zwl4rnw6z-hyprland-0.40.0+date=2024-05-08_6a988d9/share/info -DCMAKE_INSTALL_MANDIR=/nix/store/p86jfpnn01hsn2angc2sgnw0zmq88g5q-hyprland-0.40.0+date=2024-05-08_6a988d9-man/share/man -DCMAKE_INSTALL_OLDINCLUDEDIR=/nix/store/0vfvv1vhib0rli2c9ijb3q4hszsi3nyi-hyprland-0.40.0+date=2024-05-08_6a988d9-dev/include -DCMAKE_INSTALL_INCLUDEDIR=/nix/store/0vfvv1vhib0rli2c9ijb3q4hszsi3nyi-hyprland-0.40.0+date=2024-05-08_6a988d9-dev/include -DCMAKE_INSTALL_SBINDIR=/nix/store/64ij5wjzrd2lzz3z91az755zwl4rnw6z-hyprland-0.40.0+date=2024-05-08_6a988d9/sbin -DCMAKE_INSTALL_BINDIR=/nix/store/64ij5wjzrd2lzz3z91az755zwl4rnw6z-hyprland-0.40.0+date=2024-05-08_6a988d9/bin -DCMAKE_INSTALL_NAME_DIR=/nix/store/64ij5wjzrd2lzz3z91az755zwl4rnw6z-hyprland-0.40.0+date=2024-05-08_6a988d9/lib -DCMAKE_POLICY_DEFAULT_CMP0025=NEW -DCMAKE_OSX_SYSROOT= -DCMAKE_FIND_FRAMEWORK=LAST -DCMAKE_STRIP=/nix/store/4i0gb09kcanl3gbmqmm82iivbcjh2lmw-gcc-wrapper-13.2.0/bin/strip -DCMAKE_RANLIB=/nix/store/4i0gb09kcanl3gbmqmm82iivbcjh2lmw-gcc-wrapper-13.2.0/bin/ranlib -DCMAKE_AR=/nix/store/4i0gb09kcanl3gbmqmm82iivbcjh2lmw-gcc-wrapper-13.2.0/bin/ar -DCMAKE_C_COMPILER=gcc -DCMAKE_CXX_COMPILER=g++ -DCMAKE_INSTALL_PREFIX=/nix/store/64ij5wjzrd2lzz3z91az755zwl4rnw6z-hyprland-0.40.0+date=2024-05-08_6a988d9 -DNO_XWAYLAND:BOOL=FALSE -DLEGACY_RENDERER:BOOL=FALSE -DNO_SYSTEMD:BOOL=FALSE
-- The C compiler identification is GNU 13.2.0
-- The CXX compiler identification is GNU 13.2.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /nix/store/4i0gb09kcanl3gbmqmm82iivbcjh2lmw-gcc-wrapper-13.2.0/bin/gcc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /nix/store/4i0gb09kcanl3gbmqmm82iivbcjh2lmw-gcc-wrapper-13.2.0/bin/g++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Gathering git info
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
CMake Error at CMakeLists.txt:32 (add_subdirectory):
  The source directory

    /build/source/subprojects/udis86

  does not contain a CMakeLists.txt file.

-- Setting up wlroots
-- Found PkgConfig: /nix/store/vbk2n3094zyl9ywijks6a3d7s2i6wnfm-pkg-config-wrapper-0.29.2/bin/pkg-config (found version "0.29.2")
-- Found WaylandScanner at /nix/store/jsdqzw2g14h1wk6x93bl551drcd5i9ha-wayland-1.22.0-bin/bin/wayland-scanner
-- Found wayland-protocols at //nix/store/6v7nvm2lm6sy4ws9x4ksgyfjxxnpad9d-wayland-protocols-1.35/share/wayland-protocols
-- Configuring Hyprland in Release with CMake
-- Checking deps...
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
-- Found Threads: TRUE
-- Found OpenGL: /nix/store/n5plv6lv08bxshqq9ina34ckzklc7i81-libGL-1.7.0/lib/libOpenGL.so  found components: GLES3
-- Checking for modules 'xkbcommon;uuid;wayland-server;wayland-client;wayland-cursor;wayland-protocols;cairo;pango;pangocairo;pixman-1;libdrm;libinput;hwdata;libseat;libdisplay-info;libliftoff;libudev;gbm;hyprwayland-scanner>=0.3.5;hyprlang>=0.3.2;hyprcursor>=0.1.7'
--   Found xkbcommon, version 1.5.0
--   Found uuid, version 2.39.3
--   Found wayland-server, version 1.22.0
--   Found wayland-client, version 1.22.0
--   Found wayland-cursor, version 1.22.0
--   Found wayland-protocols, version 1.35
--   Found cairo, version 1.18.0
--   Found pango, version 1.52.2
--   Found pangocairo, version 1.52.2
--   Found pixman-1, version 0.43.4
--   Found libdrm, version 2.4.120
--   Found libinput, version 1.25.0
--   Found hwdata, version 0.381
--   Found libseat, version 0.8.0
--   Found libdisplay-info, version 0.1.1
--   Found libliftoff, version 0.4.1
--   Found libudev, version 255
--   Found gbm, version 24.0.5
--   Found hyprwayland-scanner, version 0.3.5
--   Found hyprlang, version 0.5.1
--   Found hyprcursor, version 0.1.7
-- Looking for execinfo.h
-- Looking for execinfo.h - found
-- Configuration supports execinfo
-- Looking for backtrace in execinfo
-- Looking for backtrace in execinfo - not found
-- Looking for sys/timerfd.h
-- Looking for sys/timerfd.h - found
-- Checking for module 'epoll-shim'
--   No package 'epoll-shim' found
-- XWAYLAND Enabled (NO_XWAYLAND not defined) checking deps...
-- Checking for modules 'xcb;xwayland;xcb-util;xcb-render;xcb-xfixes;xcb-icccm;xcb-composite;xcb-res;xcb-ewmh'
--   Found xcb, version 1.17.0
--   Found xwayland, version 23.2.6
--   Found xcb-util, version 0.4.1
--   Found xcb-render, version 1.17.0
--   Found xcb-xfixes, version 1.17.0
--   Found xcb-icccm, version 0.4.2
--   Found xcb-composite, version 1.17.0
--   Found xcb-res, version 1.17.0
--   Found xcb-ewmh, version 0.4.2
-- Checking for module 'xcb-errors'
--   Found xcb-errors, version 1.0.1
-- SYSTEMD support is requested (NO_SYSTEMD not defined)...
-- Setting precompiled headers
-- Setting link libraries
Could not open input file: No such file or directory
Could not open input file: No such file or directory
Could not open input file: No such file or directory
Could not open input file: No such file or directory
Couldn't load proto
-- Checking for module 'tomlplusplus'
--   Found tomlplusplus, version 3.4.0
-- Configuring incomplete, errors occurred!

Bug or Regression?
Bug
Description
Hyprland is failing to build on nix-unstable (for about a week now)
• Updated input 'hyprland':
    'github:hyprwm/Hyprland/70b5e6df70a7eac180e2c8e9c2bce70ff43b45ad' (2024-05-08)
  → 'github:hyprwm/Hyprland/6a988d9276691957f1d9138f93c2209b580cad13' (2024-05-08)
• Updated input 'hyprland-plugins':
    'github:hyprwm/hyprland-plugins/d716d1221348b5bef9d13161876caa91a3e33705' (2024-05-05)
  → 'github:hyprwm/hyprland-plugins/dcbdc9a08d1df753d6799bab823486f1fff5b8e6' (2024-05-08)
• Updated input 'nixpkgs':
    'github:nixos/nixpkgs/25865a40d14b3f9cf19f19b924e2ab4069b09588' (2024-05-05)
  → 'github:nixos/nixpkgs/b211b392b8486ee79df6cdfb1157ad2133427a29' (2024-05-07)

How to reproduce
Build with above hash
Crash reports, logs, images, videos
No response

Maybe #5891?

Ah, changed the inputs as that issue mentioned and it builds. I thought there was a commit submitted that resolved it without needing to change the inputs.


Support direct connections to ent from the rest api

Description of the PR
Adds configuration to allow endpoints from the REST API to connect directly to Ent. This will allow bypassing the GraphQl API to use database native functionality.
This option can be enabled with guacrest --db-direct-connection. Current endpoint implementations can be overridden to use this optimized implementation by adding methods to EntConnectedServer. If --db-direct-connection is specified but an endpoint does not have a corresponding EntConnectedServer implementation, then the default one will be used.
PR Checklist

[x] All commits have a Developer Certificate of Origin (DCO) -- they are generated using -s flag to git commit.
[ ] All new changes are covered by tests
[x] If GraphQL schema is changed, make generate has been run
[x] If OpenAPI spec is changed, make generate has been run
[x] If collectsub protobuf has been changed, make proto has been run
[ ] All CI checks are passing (tests and formatting)
[x] All dependent PRs have already been merged

Very nice! @mdeicas

Hmm, won't this create opportunities for the two backends to get out of sync? You'll now be able to write data that would not pass graphql ontology validations.

Hmm, won't this create opportunities for the two backends to get out of sync? You'll now be able to write data that would not pass graphql ontology validations.

Good point, that's true. This should only be for read access to the database, though. I think we can enforce this by adding a hook to the ent client to reject all writes, and also generally through code reviews.

If we make it only read queries that works for me

@mrizzi @dejanb for visibility and any thoughts, I think you were interested in this!


include a validation method with verbose info about skipped shipments

commit 6435170 will disappear with the merge of https://github.com/suvie-eng/solidus_shipstation/pull/3

Task linked: CU-2w5ch6p Re-sync orders to SS for those that didn't sync automatically

feedback from the Solidus team is that the intent of the original code is that the rails app would decide whether  and when the shipment change should touch the parent order - thereby retriggering the sync to shipstation.


IGC file format support (import / export)

Is your feature request related to a problem? Please describe.
Following discussion
https://forums.flightsimulator.com/t/sky-dolly-v0-8-flightaware-kml-import-visualise-replay-real-world-flights/405367/12?u=scls19fr
IGC file format is widely used by glider pilots
Describe the solution you'd like
Supporting IGC both as import and export could be an important feature to have (especialy for glider pilots).
See Technical specification for GNSS flight recorders from international gliding commission (FAI)
https://www.fai.org/page/igc-free-software
https://www.fai.org/sites/default/files/igc_fr_specification_2020-11-25_with_al6.pdf

Note to myself: the most important data (position, altitude, possibly timestamp) are in the so-called „B records“.

Some IGC parser implementations using several differents languages exist
https://github.com/topics/igc
C++ implementations can be found using
https://github.com/topics/igc?l=c%2B%2B
be aware that some implementations are released under GPL (so it could be a problem if you want to keep MIT license)... but I'm pretty sure you will find a simple manner of implementing B records parsing.

B records provide time (not date) so for full knowledge of timestamp (ie date and time) you need to also parse HFDTEddmmyy record (H=header)
I have never flown during night (above 00:00) but I think it's important to ensure timestamp are always increasing (if time is not increasing it's because that's a point which should be attached to another day).

I am not promising any timeline here, but...
https://github.com/till213/SkyDolly/tree/feature-igc
(feature branch with initial import plugin just created).
By the way, is there really a need for an export plugin? What would be the use case here? You can already visualise flight paths exported in KML format (with Google Earth and others)?

Having built in IGC import will be very convenient.
Maybe you are right @till213 maybe export to IGC is not necessary as KML export exist and some tools can convert KML files to IGC... But it simplifies creation of such IGC file without the need of an other tools.

Jesus Christ! Already parsing the date of the flight becomes an adventure alone (note to myself):

First, the official documenation, page 26, is pretty simple and clear: H F DTE DATE: DD MM YY, NN - or in other words: "The header H contains the date DTE, typically written by the flight recorder (F), spelled out again as "DATE:" and then the date is in the format DDMMYY, followed by an optional comma (,) and "flight number of the day" (NN)
But another "real world IGC" file already deviates from this, and we simply have: HFDTE250809 - so no DATE: string present!
And the best of all: the example given in the official documentation, page 41, contradicts the formal specification as well: HF DTE DATE: 16 08 19 02 - so a flight on the 16th August 2019, but where is the comma to separate the flight number 02?

Oh, the joy of verbose text formats ;)

A basic IGC import plugin has been implemented and downbranched into the current release v0.8.6 (see "Releases").

Basic header data (H record) import (pilot name, glider type and ID)
Basic task (C record) import (-> imported as waypoints in Sky Dolly, also see "Flight" dialog, key F)
Basic position data import (B records)

Current limitations & known issues

The GNSS (altitude above WGS84 elipsoid) is currently imported ("hardcoded"). I also tried with the provided "pressure altitude", but in most cases the imported flight path is either under or over the terrain data in MSFS

This might be amended with a future "altitude offset" setting in Sky Dolly

Most IGC data records the glider "sitting on the ground" for a while - due to slight GPS "signal noise" the position changes ever so slightly - and with it the (reconstructed) heading - so the glider may "turn wildly" on the ground

This might be amended by taking the first "real movement vector" (which exceeds some distance threshold) into account in the future

Depending on the sample rate of the IGC flight recorder (I have a file with a sample interval of 10 seconds only) it might simply not possible to reconstruct "tight turns" (e.g. when climbing in a "thermal layer" (?)): the aircraft in MSFS will then "wildly turn" (there is then simply no way - way too few data points - to properly reconstruct the attitude of the aircraft)
Only "mandatory" B record (fix) data is imported, but e.g. currently not yet the (optional) "noise level"

This might be used in the future to turn off/on the aircraft engine, based on some "noise threshold level"

I'm wondering which aircraft do you use. I have Schempp-Hirth Discus-2c installed in my community folder but couldn't find it in Aircraft list in Sky Dolly when selecting File / Import / IGC

Sky Dolly does not actually scan your Community folder ;) So in order to have an aircraft selectable in the dropdown list (of the import dialog) you have to record at least one (dummy) flight with it.
Or in other words: the already selectable aircraft are "pre-installed" in each "logbook" (database), as a courtesy of the developer (me ;)). Any additional aircraft is added ("upsert") as soon as it is recorded.
Does that help?

Thanks. I will record a flight with this glider.

By the way:
https://github.com/till213/SkyDolly/blob/feature-iep/CHANGELOG.md
;)
Note that this is still a feature branch"iep" (= "import/export plugins") for the upcoming v0.9 - no date yet set ;)
P.S. If you happen to be some real-world glider pilot - or are otherwise attached to some aviation friends / clubs - please feel free to make some noise for Sky Dolly ;)

A new IGC export plugin has just been merged into the current MAIN branch (for the upcoming 0.9 release - no release date set).
Both the IGC import and export plugin will received some more minor features (keyword: environmental noise level -> engine start/stop) and fine-tuning, but are both functional at this point.
If you want to test those features you can build Sky Dolly MAIN branch, as described in the BUILD.md instructions.
I will hence close this issue for now.


Only 3 guides showing up in the guides list?

For some reason only 3 of the many guides in guides show up on the website (at least on arc)

the guides that show up are controled by the metadata file in /guides/ directory. I think this is intentional

Yes the other guides are a bit out of date. It would be nice to update them. I wanted to have a somewhat coherent style to the guides we had on release too.


fix(atomic): use correct delimiting character for category facet headless controller

https://coveord.atlassian.net/browse/KIT-2036

Unfortunately yes it's breaking, we need to do something "uglier" until the next major. Maybe have a way to escape the commas in the path value

@btaillon @ThibodeauJF : Ready to re-review.
Old format (comma separated) will still work properly, but will not print a warning to the console about deprecation, and the need to move to a JSON string representation.
If you like this approach, after merging this PR I can also do the job of going through other comma separated list properties, and move them to this new format.


starting login helper, checks for email and password, need to work on…

… authentication

Will edit and push the new version soon

Incredible! Great work!


[Contextual Cursor] Resizing of infobox groups

This issue is for the external plugin: Contextual Cursor
When trying to resize infobox groups when the Contextual Cursor plugin is enabled the arrow cursor appears for 1 client tick and then resets back to default, preventing the user from resizing infobox groups:

Fixed in 1.2


request.DashboardClient().List() ignores Selector

I took a stab at migrating the helm plugin to the latest octant + helm releases and kept getting grpc errors listing Secrets...
rpc error: code = ResourceExhausted desc = grpc: received message larger than max (13036146 vs. 4194304)

So I tried tweaking the code to use stricter label selectors to reduce the amount of data returned by request.DashboardClient().List() and found the Selector is completely ignored; so there's no way to filter via selector.
	client := request.DashboardClient()
	dl, err := client.List(ctx, store.Key{
		APIVersion: "apps/v1",
		Kind:       "Deployment",
		Selector: &labels.Set{
			"app": "something",
		},
	})

it doesn't seem to matter what selector is specified; the same data is returned.
Anyone got any ideas of how to use selectors to filter the results; or to avoid grpc message limits from a plugin?
BTW the above is using deployments as every call to list Secrets in my cluster fails so I was using Deployments to test out whether selectors worked from inside a plugin)

Just realized the convertFromKey helper in conversion.go doesn't pass the selector. There should be a fix for this shortly


ndstore stack for AWS/Redis pushed.

And run Redis on the nodes, no elastic cache redis.
Artifact, branch delivered to Alex that will ingest data from an existing project into

@kunallillaney @randalburns any updates? I'm looking to get started on moving clarity to S3 this week, if possible.

Yes. I am currently setting up the AWS instance for this and writing a README. kasthuri11 res5-res1 has beeb uploaded to the s3 bucket as a proof of concept.


Display "error" notification when limits are being reached in API

Basically, if any limit is being hit by the current user, APIs request will start returning 4XX errors, and Builder should display a proper notification.
But for accomplishing that, we need to "receive" the error from CARTO.js (or DI.js). So we need first changes there, tackled in https://github.com/CartoDB/cartodb.js/issues/1714).

after the 'meeting', we decide to show the infobox only in the layer list :)
Thanks guys

Right now the error is:

But what happens if the tiles are working and the limit error is thrown by any other thing? Widget/Interaction/SQL... should this message be more generic?

Merged!

Reopening due to https://github.com/CartoDB/cartodb/issues/12968. But we need to enable them again because if not the user will not have any clue about the errors those appear over the map. Unfortunately, we don't have enough information about the source of the "error", so the options are:

Make a new request (no idea where but from Builder) in order to collect the necessary error info. If the problem comes from limits, we should display the infobox we used to have.
Display an infobox with another message, more standard, not providing anything about upgrade and pointing to our docs (like the overlay does in the CARTO.js side).

If you ask me, I'd go with the second option.
@noguerol @matallo @rjimenezda @rubenmoya

I'll go for the second option too, and change the documentation so it doesn't show only information about pricing but also show that it could be a connection problem or our servers being down

The first one is not realistic, and wouldn't work on an offline / shoddy connection scenario, which also causes a tile error.
I'd go with the second one, we can point the CTA towards the same places as the 'Learn more' on the Overlay, but the message has to be decided by someone. Currently:

Looks like you are over your limits when trying to render some of your tiles. Try to:

As @rubenmoya pointed out this morning, hopefully on other scenarios (wax, mvt, torque) we can emit a more specific error, and display it. But for raster tiles we're pretty much limited to a generic error.

while ideal I agree it's not realistic to get further information just for the raster errors, who shall confirm the new literal @xavijam ?

I'd write something like:
Something happened and some tiles were not displayed. If the problem persists contact us or check our docs.

I'll put that temporarily.
So if we're not sure what exactly caused this, should the CTA still take the user to the pricing page? Should we point to some specific docs page? Should we remove the button altogether?

Hey, just a comment. It doesn't matter how good is the msg if the error still pops up a lot of times. Prior to any decision: is there any way we can now the number of users that are seeing it?
CTA should point to the docs, yes. My suggestion for the msg is Some tiles were not displayed. If the problem persists check our docs or contact us

Hey, +1 to noguerol's suggestion

I am no expert, but we can probably add some event (FS?).
This error will show for any user that has a problem loading as little as one tile (for whatever reason).
(Right now, nobody will see it because we removed it on a previous PR.)
Is pointing to carto.com/docs enough?

I am no expert, but we can probably add some event (FS?).

we can

Is pointing to carto.com/docs enough?

there's an open issue for that https://github.com/CartoDB/learn/issues/425

We cannot measure this in FS because every free user is currently using vector maps. But even without metrics I still feel we cannot afford to have such a visible generic tile error, so I suggest we either
a) Figure out a way to only activate this notifications for vector users (via a feature flag or somehow discriminating sources; dunno if that is even technically possible)
b) Delay the re-deploy of these notifications until every user is using vector maps, which should happen shortly.

The button should be gone. About @noguerol message, sounds good to me, but it is your call mates. And about the stat, yes, we can take those stats, but it will be ambiguous, because the causes are different...

On 19 Oct 2017, at 14:55, Javier Noguerol<EMAIL_ADDRESS>wrote:
Hey, just a comment. It doesn't matter how good is the msg if the error still pops up a lot of times. Prior to any decision: is there any way we can now the number of users that are seeing it?
CTA should point to the docs, yes. My suggestion for the msg is Some tiles were not displayed. If the problem persists check our docs or contact us
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

The stats will ve valid as long as the error message is generic. So @matallo tell me is a) is feasible and if its not, then we go for b)

We're already showing a very subtle error on the map view, which coupled with the striped tiles gives a clear impression of 'something's not right'.
I would keep this very "in-your-face" error for things that we can 100% identify and point the user  towards a solution. As a matter of fact, the other error that is displayed on that area is the one for maximum number of Layers reached, which is something we can tell the user how to fix.

we left this at PR https://github.com/CartoDB/cartodb/pull/12974 with a more generic message and the rest of the requested changes
bear with me, why should we only show this for vector maps? just want to wrap my head around this

This is what we've agreed to do:
Only show notifications/error tiles for vector maps until @CartoDB/design works in a much subtle version of the last one, which will be then implemented at least for raster. In other words, we:

Work on a light tile error version
Disable notifications for raster maps and implement the light tile error
Notifications/Tile error for vector remains the same until we decide the implications of activating limits

What about one of our firsts approaches on this?

Hi @josecruz can we talk later about this?

I think this is the best approach cc @noguerol

Thanks!
Just to be safe, by 'The current behaviour for vector' do we mean:

Warning + Infobox + orange tile?

Vector is not available in builder so ... :(

not yet, but it can be detected, unlike raster (whenever the implementation for it is finished)
@rjimenezda as we can differentiate between the limits error, and the general error I think in that case we should go on with the limit error we left in the en.json
as @piensaenpixel suggested, for any raster error no tile, no infobox, just overlay warning, thrown via img.onError event

I start to be part of the project, talking to @matallo to understand internals and roll-up. Specifically those things that are pretty linked to Engine.
But in terms of the global user experience, and that doesn't understand about our separations between Builder/Engine and so on, I wonder how we will communicate them about the limits. Well, I see we have plans for displaying alerts about errors and limits, but where can be found that information about limits.
@noguerol
Is there any part on the dashboard giving information about that?
Is there any part on documentation explaining those limits? Is that documentation dynamically connected to the limits configuration, so that when one part is updated the other one reflects it?
Is there any part of the rollup taking care about that but on future steps?

Hi! As you know I've been in the response team last week so I'm kind of lost here. Right now we're showing a generic message and the orange tile, if I've read correctly we want to stop showing both of them, and just keep the map overlay (the yellow button in the bottom left corner) is that correct? The PRs are already open, should I prioritize this?
@noguerol @inigomedina

We've been talking in the standup and the backend will send us the error tile, so finally what we're doing is:

No infobox
Map overlay
Tile error sent by backend

It is worth to get back this issue created by @saleiva for the design team, looking for a solution to upsell from these kind of errors: https://github.com/CartoDB/design/issues/800


jwt token decoded on the frontend

Hello, I was looking at the base auth storage and I saw that there is a function getTokenPayload imported from the utils folder that simply decodes the token.
From what i understand, this js-sdk is made to work on the frontend, so isn't this some security concern that the jwt is decoded on the client side?

The token is always validated when sending request to the PocketBase server.
The getTokenPayload is just a helper to extract the base64 decoded payload. It doesn't have or serve any security purpose.


How can I migrate old data to a new computer?

I copied the files from /var/lib/docker/volumes/wandb to the new server, but it doesn't work.
The wandb version is the same for both (wandb/local:0.9.41).
The first error that appears is:
chmod: changing permissions of '/vol/env': Operation not permitted
After changing the file owner of /var/lib/docker/volumes/wandb/_data/env,  this error has been solved. But  a new error appeared:
*** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
*** Running /etc/my_init.d/01_enable-services.sh...
*** Copying services to runit
*** Copying jobber template
*** Enabling production mode
*** Running /etc/my_init.d/02_load-settings.sh...
*** Loading settings...
*** Booting runit daemon...
*** Runit started as PID 59
*** Starting wandb servers...
./run: line 1: kill: (137) - No such process
./run: line 1: kill: (243) - No such process
./run: line 1: kill: (295) - No such process
./run: line 1: kill: (343) - No such process
./run: line 1: kill: (391) - No such process

Is there any solution for this?

Are you able to access the interface?  Something is failing to startup, it's likely permissions in /var/lib/docker/volumes/wandb/_data/minio and /var/lib/docker/volumes/wandb/_data/mysql that are incorrect.

Thanks, I solved this problem by this command :)
chmod 777 -R  /var/lib/docker/volumes/wandb/_data/


Plugin Infrastructure Discussion

I'm close to finishing up #43 now, and I'd appreciate some thoughts on details of how add plugin support to OPS.
Here are the big ideas of the plugin infrastructure, no matter what:

We will use essentially the same plugin infrastructure for plugins providing multiple types of functionality: CLI subcommands are plugins, but so are tools to compile OPS objects from YAML/JSON, and so are (well technically, will be) components of the Wizard.  This makes developing for the CLI extremely easy and means that contributions can be made without ever touching the core code. Different plugins types are distinguished by type: CLI commands are instances of OPSCommandPlugin; plugins implementing support for compiling a new engine from YAML are instances of EngineCompilerPlugin, etc. In the future, analysis tools may be developed based on the same plugin infrastructure.

There are two ways of distributing plugins -- as files, or as namespace packages. Files are better for quick setups for yourself or a small group. To distribute to a wider audience (and have a more convenient mechanism for providing updates), use a namespace package.

My main question is: Should we use one location for all plugins, or a specific location for each plugin type? Command plugins can currently be installed in the namespace paths_cli_plugins or in the user's ~/.openpathsampling/cli_plugins/ directory. The question is whether that same namespace should be used for other plugins, like for the wizard or for the
Advantages for the single namespace:

Easier for developers (package a new engine and support for it in the CLI and in the wizard all in Python package)
With #48, it is possible to have more than one plugin in the same file, making it possible to add multiple pieces of functionality through one file-based plugin file, if all use the same namespace.
Easier to tell users where to put things (especially for file-based; otherwise you say "well, put this file here, that file there...")

Advantages for multiple namespaces:

There may be some performance advantages for multiple namespaces if users have lots of plugins. (Only search the namespace relevant to the current task.)
If there are enough file-based plugins, a user might find their ~/.openpathsampling/cli_plugins/ directory to be too cluttered to find the plugins they want.

Note that the default plugins for each of these are in a different default namespace, so the default plugins already have the advantages of multiple namespaces.
@sroet : Any thoughts?

I think the solution is to error out if there is more than one plugin trying to register for the same name within the same kind of functionality. It looks like this is not done in (yet) in the command plugins, but it's what I'm doing in #43. The error messages in there are already reasonably descriptive, I think:
https://github.com/dwhswenson/openpathsampling-cli/blob/4e748999e6a4d1d9a3af5ba84de016c32fa58636/paths_cli/compiling/root_compiler.py#L72-L86
(leading to messages like CategoryCompilerRegistrationError: The category 'engine' has already been reserved by another plugin)
https://github.com/dwhswenson/openpathsampling-cli/blob/4e748999e6a4d1d9a3af5ba84de016c32fa58636/paths_cli/compiling/core.py#L282-L291
(leading to messages like RuntimeError: 'openmm' is already registered with engine)
Now, the fact that there's some repeated behavior here (plugins register under some name or names and we need to watch for duplicates) suggests that this might be something that should be refactored into a more DRY solution. But that's a very low priority right now.
Note that technically we search the posix-style app dir (.openpathsampling) but also do the formally correct thing of searching OS-specific app dirs. This may lead to more risk of duplication, so at some point it might be worth having a little debug-plugins command to illustrate where each plugin is found.

Also, I agree on using a single namespace. This wasn't possible before #48, so I had the idea of different namespaces for each plugin type in my head. Now that separate namespaces aren't required by technical limitations, I see no reason to add user/contributor confusion by requiring it.
I expect that the vast majority of installed plugins will be the built-in plugins anyway (i.e., the stuff that ships in this package), which means that the main reasons for multiple namespaces are unlikely to be relevant.


Initialization of BootstrapSwitch is not shown in docs

I had to find out myself that I need to initialize 'em like this:
$("[name='my-checkbox']").bootstrapSwitch();

See #247


Cygwin integeration

Is it possible to get this to work with Cygwin? I followed instructions but I still get empty boxes for symbols. I ran the install.sh script to install fonts, but I can't seem to get any of them to work. I'm running Cygwin inside Cmder (which uses Conemu), and I selected the Meslo LG M for Powerline as my font.

I was able to get this completely configured on my Mac (looks pretty awesome!), but not via Cygwin (darn it Windows!)

Thanks for your report!
Uhm. Haven't done very much with cygwin for a long time..
Can you do an echo awesome: "\uE0B0" new powerlline "\uE0B0" old powerline "\u2B80" and post the result here?
And could you please double-check that you selected your powerline font in Conemu? I think it is the "alternative font"-Setting like shown in this screenshot: https://conemu.github.io/en/Settings.html#Main
I hope that helps.

@DanielGGordon - Let us know how @dritter's suggestions, went! If it is working for you, can you close this issue?

Closing due to inactivity.

I'm considering opening this issue up, but really, it's a font/mintty issue I think. I got it working quite a bit better, where almost all the symbols work. But it seems no matter what patched font I use, there are always a few that are missed. Right now I only see 1x icon missing (it shows up as a plain "?"), see below.

@DanielGGordon I think this is not a missing icon. I think it is the VCS_UNTRACKED_ICON. In the default (a.k.a. "powerline") mode this is a plain question mark.. See the documentation.
Sorry for the confusion.

@dritter Do you have the list of character codes so I can verify they all work? And right now I'm testing this on Babun, which is really just Cygwin/Mintty.

@DanielGGordon You could check that by overriding the icon:
POWERLEVEL9K_VCS_UNTRACKED_ICON='test' print_icon 'VCS_UNTRACKED_ICON'
If you see test, it worked. ;)
You can get a full list of all icons by calling get_icon_names (which already gives you full variable names for overriding).

Looks like some are missing. That VCS_BOOKMARK_ICON looks a bit odd too. Node icon is also just a box.

It looks like your POWERLEVEL9K_MODE is falling back to the standard powerline patched font mode(no awesome fonts) and everything looks appropriate for that with the exception of the NODE_ICON(maybe we need to find a more portable icon for Node, or just ditch the icon in powerline only mode all together). A lot of icon's just don't exist in that mode. You can see all the modes and their icons here - https://github.com/bhilburn/powerlevel9k/blob/master/functions/icons.zsh
What font are you using/what is your POWERLEVEL9K_MODE setting?

I think the only missing icon is the NODE_ICON.. This is the typical "no icon found in your font"-rectangle.
The other "icons" are in that mode basically strings (like the NETWORK_ICON is just IP). This is due to the "powerline" mode requires a powerline font which is a regular font with that triangles (powerline symbols). So there are no more fancy icons..
If you want more icons, you need to switch to "awesome-patched" or "awesome-fontconfig" mode and install a awesome-terminal-font.

Sorry what do you mean by my POWERLEVEL9K_MODE setting? I think you mean regular or 'awesome'.
Awesome fonts cant even be loaded at all by Mintty, so I am using the regular mode in Inconsolata for Powerline.
Also, the "+" symbol looks like it is cut off a bit

I think they aren't monospaced or something, so they don't show up as an option for font selection. Other patched fonts work, but not the awesome ones. In theory, I could go through the font, and make everything monospaced - but I'm not even sure how that would turn out.
It seems though that the regular icons are working pretty well.

Ah. Okay. I think it won't be a good idea to force awesome fonts into monospacing, as it has a lot of double-width glyphs..

Yea I think then the only way would be to have Mintty support non-monospaced fonts, and that's probably not going to happen.

It seems like the best font (for any powerline) is the DejaVu Sans Mono for Powerline. It even shows the gear icon and lightning bolt that I haven't been able to get before.
That node icon doesn't show up, but I'm ok with that. But how would I fix that? Do I need to do something to the font itself?


Iterators: Add iterator state types and ops for Open/Next/Close.

@nicolasvasilache: Thanks for the review. The last three commits use some more built-in constructs for verification. I am not sure how to remove the remainder (see inline discussion).

Addressed with latest commit. I'll merge when the tests completed.


Add support to carry an error description back to third party clients on authorize error results

Duplicate/re-open of #2902
What issue does this PR address?
Only specific error types can result in a redirect back to the third party client and we'd like to give our third party clients more context on why authorization couldn't progress with the use of the error_description query param that's currently not hooked up but is sent back empty.
I think it's related to these open issues

#1972
#2031

Does this PR introduce a breaking change?
No, shouldn't do
Please check if the PR fulfills these requirements

[x] The commit follows our guidelines
[x] Unit Tests for the changes have been added (for bug fixes / features)

Other information:
This is required following our discussions on our approach to extending the authorize flow for tenanting @brockallen @thirkcircus

@brockallen @leastprivilege, the original PR for this was assigned to the 2.5 milestone. Can this PR be assigned to that milestone so it's not missed?

Yep, nice addition. Thanks.


import from Student

1.Excel template have two phone，1.Contact phone 2.phone.
delete a phone column from excel or add a contact phone in user model
2.Student need below field
a.特长 b.入学时间 c.入学年级 d.生源(0.本地 1.借读)
3.Excel Template didn't provide school & campus info
a.change template provide campus
b.create Admin domain which contains campus, get campus from token
4. Can't operate grade.
a.Can't find grade repository & service.
b.Excel template provide a grade name, can't get grade id from name.

@xxing1982 @jerrywalker0435 @Morgan-Leon

import book from Excel model:

the first column id is useful? we need update book with the id or ignore id column and all use save operation.
2.picture url contains domain url, our rule's is store path of picture in db don't store domain name into picture field.
3.Can't find  packaging posters video evaluationNum highPraise from book , bookextra model.
4.book adapt age is a range value, model is a int value can't convert AgeRange to bookextra age.
5.type column in excel template is map with category, if it map category we need provide an method convert type String to category, or type is an int value, just store type into category is ok.


Fan speed language is in china

What file/config do I have to modify to translate these? Everything else works but the fan speed control shows four options in china
Xiaomi vacuum mop 1C

https://github.com/al-one/hass-xiaomi-miot/issues/842#issuecomment-1275964389


[NSE-360] fix ut compile and travis test

What changes were proposed in this pull request?
fixed: https://github.com/oap-project/native-sql-engine/issues/360
How was this patch tested?
locally tested

@weiting-chen fixed compilation here, thanks!

@rui-mo
Find a solution to keep the ut and pass the testing.
Please assign scala-maven-plugin to version 4.5.2 instead of 4.4.0.
Check if this can work, then we don't have to remove the ut.


Renamed Payload to PayloadRaw and Fields to PayloadFields

Closes #276

Coverage remained the same at 55.874% when pulling b2f9665f9d332d51ff614fffea07e7cf3dbabdd8 on issue/276 into b1ff842a6e6853d3cd35eb518558310ba098e97f on refactor.


Write migration guide for azure-spring-boot-starter-storage

Parent issue: #24351

close this issue, refer to Spring-Cloud-Azure-Migration-Guide-for-4.0