label Of Form not shown?

I set the label of Form,
but It seems not work at all?

Yes, from 0.9 to give more flexibility i removed the standard Separator that was inside Form.
Just add a Separator inside your form and pass the text to the label prop.
Thank you for using my library

Actually, You've done a great work!! I should thank you to save my time.
and another problem is if I use the KeyboardAwareScrollView,
the Simulator will shows me an error:

Am I doing anything wrong?
and code is just:
import React, { Component } from 'react';

import {
    View,
    Text,
    ScrollView
} from 'react-native';

import {
    Form,
    Separator,
    InputField,
    KeyboardAwareScrollView
} from "react-native-form-generator";

class ShirtOrder extends Component {

    state={
        formData: {}
    }

    render(){
        return (
            <KeyboardAwareScrollView
                ref="scroll"
            >

            </KeyboardAwareScrollView>
        );
    }
}
export default ShirtOrder;

yes.. that because KeyboardAwareScrollView is not exported anymore
you can try to access it directly.
try something like
import {
    KeyboardAwareScrollView
} from "react-native-form-generator/src/KeyboardAwareScrollView";

or copy it from the repo.

also not working but import it from react-native-keyboard-aware-scroll-view.

yes you can also use that, but i highly encourage you to create your own solution using the official ScrollView

If I clicked the InputField, error happened

maybe just like you said, I need to do it myself.

can you post a code sample, that error means nothing, it's just the event that is triggered by the focusaction

import React, { Component } from 'react';

import {
    View,
    Text,
    ScrollView
} from 'react-native';

import {
    Form,
    Separator,
    InputField,
} from "react-native-form-generator";

import { KeyboardAwareScrollView } from 'react-native-keyboard-aware-scroll-view'

class ShirtOrder extends Component {

    state={
        formData: {}
    }

    handleFormFocus(event, reactNode){
       this.refs.scroll.scrollToFocusedInput(event, reactNode)
    }

    handleFormChange(formData){

    }

    render(){
        return (
            <KeyboardAwareScrollView
                ref="scroll"
            >
                <Form
                    ref="shirtOrder"
                    onFocus={ this.handleFormFocus.bind(this)}
                    onChange={this.handleFormChange.bind(this)}
                >
                    <InputField
                        ref="ordernumnow"
                        label="orderNum" />

                </Form>
            </KeyboardAwareScrollView>
        );
    }
}
export default ShirtOrder;

I found what's with this,
I've forgot to remove the code in handleFormFocus

;) if you want post a screenshot of your final form in action, i would love
to see it.
Have a nice day.
On Thu, Jul 7, 2016 at 5:56 PM abellee<EMAIL_ADDRESS>wrote:

I found what's with this,
I've forgot to remove the code in handleFormFocus
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/MichaelCereda/react-native-form-generator/issues/22#issuecomment-231123742,
or mute the thread
https://github.com/notifications/unsubscribe/AAGjfgKm8LRREQB6oZJu3w1R6hUAC1TJks5qTSG_gaJpZM4JHJF7
.

--
Michael Cereda
http://michaelcereda.com


Upgrade python3 to 3.12.3

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

[x] The toolchain has been rebuilt successfully (or no changes were made to it)
[x] The toolchain/worker package manifests are up-to-date
[x] Any updated packages successfully build (or no packages were changed)
[x] Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
[x] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
[x] All package sources are available
[x] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
[x] LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
[x] All source files have up-to-date hashes in the *.signatures.json files
[x] sudo make go-tidy-all and sudo make go-test-coverage pass
[x] Documentation has been updated to match any changes to the build system
[x] If you are adding/removing a .spec file that has multiple-versions supported, please add @microsoft/cbl-mariner-multi-package-reviewers team as reviewer (Eg. golang has 2 versions 1.18, 1.21+)
[ ] Ready to merge

Summary

What does the PR accomplish, why was it needed?
Upgrade python3 to 3.12.3
Change Log

CVE-2024-0397
CVE-2023-6597

Does this affect the toolchain?

NO
Associated issues

NA

Links to CVEs

https://nvd.nist.gov/vuln/detail/CVE-2023-6597
https://nvd.nist.gov/vuln/detail/CVE-2024-0397

Test Methodology

Pipeline build id: Ran full toolchain builds whose details are given in the comments section.

I have run toolchain builds for both amd64 and arm64 which are successful.

@mfrw, Thanks for the review. I have implemented your comments. Please take a look.


add BERT

https://github.com/BUPT/awesome-chatbot/issues/22

you should change arxiv to paper. Purposal: rename arxiv to paper #41


OTSession keeps 'stale' connections

Perhaps it's due to how we use it, but it seems that connectionDestroyed which removes a connection is only called when someone disconnects.
However if you're the one closing the conversation the connection stays in the list of connections since OTSession is a 'service', so joining a new conversation you have that 'stale' connection that wasn't cleaned up left in the array. I had to manually clear the array of connection on init.

Good catch, yes it does not clean up the connections.


opn(uri) cause error then launch dev server in environment without browser

Vue.js version
2.0.7
Steps to reproduce
$ docker run -it --rm alpine:latest
$ apk add --no-cache nodejs
$ npm install vue-cli
$ vue init webpack test
$ cd test
$ npm install
$ npm run dev

What is Expected?
App starts
What is actually happening?
dev server is not starting beacuse server try to open window  with running app
JS Error
(node:15) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: Exited with code 3

Well, feel free to remove the line if that does not suit your usecase. It's a template, you should adjust it to your needs.
We feel that opening the window is a nice helper for most scenarios, so I don't see a reason to remove this.

While I agree with @LinusBorg that we everyone is able to make the template fit to their needs, I think this is a bit more complicated than that. For instance, those of us with a Chromebook that run their dev environment in a chroot (with Crouton) will experience the same error as Chrome is not detected from within the chroot. While there are options to open Chrome anyway, I totally understand that Vue will not implement such platform-specific workarounds.
I do however think it's important that if there is no browser detected, the error will be ignored.

That behaviour is customizable since Nov 12, 2017 in /config/index.js


Can one Dapr sidecar support multiple services?

After recently getting in touch with Dapr, I found through documentation that one service needs to be paired with one sidecar component to run. This is acceptable in a production environment. Now, assuming that there are multiple services in a test environment, but we don't want to start up so many sidecar components, can we achieve the goal of having one sidecar support multiple services?

Please see the Dapr Shared project, it could meet your needs!
https://github.com/dapr-sandbox/dapr-shared


Chore/swiftpm tests

Issue #, if available:
Description of changes:
Check points:

[ ] Added new tests to cover change, if needed
[ ] All unit tests pass
[ ] All integration tests pass
[ ] Documentation update for the change if required
[ ] PR title conforms to conventional commit style

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #1309 (23d2d80) into main (a7bdc5d) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1309      +/-   ##
==========================================
- Coverage   60.57%   60.56%   -0.01%
==========================================
  Files         660      660
  Lines       19877    19877
==========================================
- Hits        12040    12039       -1
- Misses       7837     7838       +1

Flag
Coverage Δ

API_plugin_unit_test
65.74% <ø> (-0.10%)
:arrow_down:

AWSPluginsCore
76.48% <ø> (ø)

Amplify
48.60% <ø> (+0.02%)
:arrow_up:

Analytics_plugin_unit_test
73.41% <ø> (ø)

Auth_plugin_unit_test
82.31% <ø> (ø)

DataStore_plugin_unit_test
74.42% <ø> (ø)

Predictions_plugin_unit_test
33.51% <ø> (ø)

Storage_plugin_unit_test
57.72% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...ries/DataStore/Subscribe/MutationEvent+Model.swift
0.00% <ø> (ø)

...n/Operation/AWSGraphQLOperation+APIOperation.swift
43.63% <0.00%> (-10.91%)
:arrow_down:

.../DataStore/Model/Internal/Schema/ModelSchema.swift
64.58% <0.00%> (+2.08%)
:arrow_up:

...CategoryPlugin/Operation/AWSGraphQLOperation.swift
64.28% <0.00%> (+2.38%)
:arrow_up:

...lugin/Operation/AWSAPIOperation+APIOperation.swift
83.78% <0.00%> (+5.40%)
:arrow_up:

Continue to review full report at Codecov.

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


Cannot find python-executable file so showing error all the time when ever i open it

Fixed in python-tools 0.6.8 thanks to @go2sh for the fix


Extra comma with \noindent command

Using a note style with a reference that does not begin with an author (whether because there is no author or it is printed later, as with an edited work for MHRA), if I place the citation in a footnote, preceded by a \noindent command, pandoc 1.17.1/pandoc-citeproc 0.10 adds a comma before the citation.
pandoc -F pandoc-citeproc --csl=chicago-fullnote-bibliography.csl << EOT
---
references:
- id: 'test'
  type: book
  title: Book title
...

Test text.[^1]

[^1]: \noindent @test [p. 196].

EOT

Result:

Test text.1

Book Title, n.d.

Test footnote.

, Book Title, n.d., 196.↩

(Before someone points out that this is unnecessary: I needed to do this in a multi-paragraph footnote, following a block quotation.)

I can explain why this happens.  I don't know if I'd
consider this a bug; you're running up against the kind
of problem that typically arises when you use a note style
inside a note.
Pandoc has a deNote function that removes notes from
inside notes.  (The @test citation originally gets
turned into a note, since it's a note style.)  This function
inserts a comma between "non-spacelike" content and the
contents of the note.  Here it's treating \noindent as
non-spacelike (because it's not a Space or SoftBreak).
+++ Andrew Dunning [Jun 30 16 23:46 ]:

Using a note style with a reference that does not begin with an author
(whether because there is no author or it is printed later, as with an
edited work for MHRA), if I place the citation in a footnote, preceded
by a \noindent command, pandoc 1.17.1/pandoc-citeproc 0.10 adds a comma
before the citation.
pandoc -F pandoc-citeproc --csl=chicago-fullnote-bibliography.csl << EOT
references:

id: 'test'
type: book
title: Book title
...

Test text.[^1]
[^1]: \noindent @test [p. 196].
EOT
Result:
Test text.1

Book Title, n.d.

Test footnote.
, Book Title, n.d., 196.↩

(Before someone points out that this is unnecessary: I needed to do
this in a multi-paragraph footnote, following a block quotation.)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, [1]view it on GitHub, or [2]mute the
thread.
References

https://github.com/jgm/pandoc-citeproc/issues/243
https://github.com/notifications/unsubscribe/AAAL5K24Qo35CEQUubvS-FVJ2u9egF5vks5qRLe3gaJpZM4JC3NP


www subdomain should resolve to simple report

https://www.simplereport.gov/ should resolve to https://simplereport.gov/

duplicate of https://app.zenhub.com/workspaces/simplereport-5ff8be8854ae8b000e378210/issues/cdcgov/prime-simplereport/896


New version: Zoom.Zoom version <IP_ADDRESS>74

Pull request has been created with Komac v1.11.0 :rocket:
Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:


HAL: add PIO configuration API

This PR starts the work on a PIO configuration API, heavily inspired by the API available in the atsamd crate.

This PR depends on #16.

Branch is now deprecated. Closing. Refer to https://github.com/atsams-rs/atsamx7x-rust/discussions/24.


FIO Fee Update

Tracks discussion surrounding FIO BP update of FIO Fees.
The following price data is taken from Coingecko FIO Protocol USD (Historical Data)
https://www.coingecko.com/en/coins/fio-protocol/historical_data/usd#panel
snapped_at | price
2020-07-13 00:00:00 UTC | 0.113946112
2020-07-14 00:00:00 UTC | 0.113946112
2020-07-15 00:00:00 UTC | 0.086577099
2020-07-16 00:00:00 UTC | 0.093932881
2020-07-17 00:00:00 UTC | 0.084144208
2020-07-18 00:00:00 UTC | 0.083985383
2020-07-19 00:00:00 UTC | 0.083476238
2020-07-20 00:00:00 UTC | 0.124258708
2020-07-21 00:00:00 UTC | 0.148377484
2020-07-22 00:00:00 UTC | 0.181089225
2020-07-23 00:00:00 UTC | 0.181444731
11 day average price: 0.118
7 day average price: 0.127
5 day average price: 0.144
Current FIO Fee for register_fio_address: 40 FIO
Current price of register_fio_address in USD using 11 day average: 40 FIO * 0.118 = $4.71
Current price of register_fio_address in USD using 7 day average: 40 FIO * 0.127 = $5.07
Current price of register_fio_address in USD using 5 day average: 40 FIO * 0.144 = $5.75
Target price of FIO Address is $2.00
Suggested FIO Fee for register_fio_address using 11 day average: $2.00 / $4.71 * 40 ~ 17 FIO (multiply current fee by .42)
Suggested FIO Fee for register_fio_address using 7 day average: $2.00 / $5.07 * 40 ~ 16 FIO (multiply current fee by .39)
Suggested FIO Fee for register_fio_address using 5 day average: $2.00 / $5.75 * 40 ~ 14 FIO (multiply current fee by .34)
Proposed: Multiply current fees times 0.35
(Current fees: https://www.alohaeos.com/tools/fiofees)
The new register_fio_address fee would be 14
If FIO trades at ~$0.14 a FIO Address would cost $0.14 * 14 = $1.96
The best way to think of this is to agree on what the assumed exchange rate might settle at in the near future. This proposal suggests $0.14

In my opinion a slightly cheaper address is better than an address that is too expensive.. I agree with your $0.14 / FIO rate right now.

$0.14 sounds fair to me!

Good point that slightly cheaper is better than too expensive. To be more conservative we could assume an exchange rate average of $0.15 which would put the price of an address at ~13 FIO. Then we would multiply all current prices by 0.325.

$0.14 its a reasonable rate

Fee was updated by BPs. Closing.


Weird hash marked as domain in cps-collected-iocs.intel

Hello,
I'm working on Slips IDS and it's consuming the  cps-collected-iocs.intel feed from the master branch
https://raw.githubusercontent.com/CriticalPathSecurity/Zeek-Intelligence-Feeds/master/cps-collected-iocs.intel
it's complaining about this line
22813a7723dbdceb828c0263431465e3698aa0fc	Intel::DOMAIN	CPS-CTI	F	PHISHING
I'm not sure what kind of hash this is, and why is it marked as DOMAIN

Issue resolved from EW on our team.
Thank you for letting us know!


Fix #32035 -- AbstractUser.clean assumes default manager is named objects

See ticket: https://code.djangoproject.com/ticket/32035#ticket

Closing per ticket.


torch.onnx.export transform bevformer to onnx occure error aten::mul not support

when i train model from https://github.com/fundamentalvision/BEVFormer, and transform to onnx，occur error:
/home/xjw/Desktop/cyp/bxie/BevFormer/BEVFormer/tools/onnx_utils.py", line 74, in get_onnx_model
torch.onnx.export(
File "/root/miniconda3/lib/python3.8/site-packages/torch/onnx/init.py", line 350, in export
return utils.export(
File "/root/miniconda3/lib/python3.8/site-packages/torch/onnx/utils.py", line 163, in export
_export(
File "/root/miniconda3/lib/python3.8/site-packages/torch/onnx/utils.py", line 1074, in _export
graph, params_dict, torch_out = _model_to_graph(
File "/root/miniconda3/lib/python3.8/site-packages/torch/onnx/utils.py", line 731, in _model_to_graph
graph = _optimize_graph(
File "/root/miniconda3/lib/python3.8/site-packages/torch/onnx/utils.py", line 249, in _optimize_graph
_C._jit_pass_canonicalize_graph_fuser_ops(graph)
RuntimeError: 0 INTERNAL ASSERT FAILED at "../torch/csrc/jit/ir/alias_analysis.cpp":608, please report a bug to PyTorch. We don't have an op for aten::mul but it isn't a special case.  Argument types: Tensor, bool,
bevformer transform to tensorrt also need onnx, did you encounter this error ? How did you resolve it?
Thanks!

Sorry, I haven't tried the code BevFormer/BEVFormer/tools/onnx_utils.py to transform bevformer to onnx.
There are lots of Ops unsupported by ONNX and TensorRT in the original forward. And I changed all unsupported operators.  BEVFormer_tensorrt supports the official PyTorch models.


Question: Next.js 5.1.0 with redux in SSR - How to get state from store in SSR?

It's okay when I dispatch action in client side, all work as normal react redux app.
But my question would be like do I need to use redux in SSR or just simply fetch api and then base on api response to create dynamic web content in SSR - this do not need redux at all.
I am kinda confuse.
I still can get the dispatch and reducer work as normal in SSR.
But I don’t know how to grab the state out.
If can get state from store (when I can't do it now and struggling how to do it) how to do I pass it from server side to client side?
I am using this https://github.com/zeit/next.js/tree/5.1.0/examples/with-redux as example to implement my app right now.
Please correct me if I have anything misunderstanding.
Thanks for the helping hand!
Environment:
Next.js 5.1.0

SSR is only for rendering the initial state, after the first render we have a normal client side redux app.
You can see in the store there's an action called startClock() which dispatches an action every one second, that only happens after client render.
For state: look at /components/Page.js there's a redux connect function that spreads the state of the Store into props of the react components. Sometimes people namespace any higher order connect components under the folder such as /containers so it's clearer.

I solved this with async wait pattern. I forgot about JavaScript async patten need to wait until the XHR call to finish. Otherwise, no data can be get at the point.

@thanhvk
Action:
import { GET_LATEST_FIVE_ARTICLES } from './types';
import api from '../config/api';

const getLatestFiveArticles = (endpoint, language) => {
    return async (dispatch) => {
        await fetch(endpoint + api.latestFive + `?language=${language}`)
        .then((response) => response.json())
        .then((data) => {
            dispatch({
                type: GET_LATEST_FIVE_ARTICLES,
                articles: data
            });
        })
        .catch((error) => console.log(error));
    }
}

export { getLatestFiveArticles };

Reducer:
import { GET_LATEST_FIVE_ARTICLES } from '../actions/types';

const INITIAL_STATE = {
    articles: []
};

export default (state = INITIAL_STATE, action) => {
    switch (action.type) {
        case GET_LATEST_FIVE_ARTICLES:
            return {
                articles: action.articles
            };
        default:
            return state;
    }
}

Page:
static async getInitialProps({ req, pathname, t, i18n, store }) {
        let endpoint;
        let language;

        if (req) {
            endpoint = process.env.API_ENDPOINT;
            language = req.language;
        }
        else {
            endpoint = '/';
            language = I18n.language;
        }

        await store.dispatch(getLatestFiveArticles(endpoint, language));

        return { pathname, t, i18n };
    }

for your reference

I'll close this as it's solved.


(FunctionClauseError) no function clause matching in System.cmd/3 (Linux server)

Related to https://github.com/gutschilla/elixir-pdf-generator/issues/56
I'm getting this error on linux server:
(elixir) lib/system.ex:621: System.cmd(nil, ["/opt/app/lib/pdf_generator-0.6.0/priv/node_modules/chrome-headless-render-pdf/dist/cli/chrome-headless-render-pdf.js", "--url", "file:///tmp/0wolmM04.html", "--pdf", "/tmp/0wolmM04.pdf", "--paper-width", "8.26772", "--paper-height", "11.695", "--dpi", "300"], [stderr_to_stdout: true])

In my case, I'm switching from wkhtmltopdf which was working but with some issues in the layout to chrome-headless. I'm sure that chromdriver, nodejs, chrome-headless-render-pdf and, puppeteer are being installed as well.

Here is a snippet from my Docker file.

Alright @feliperenan thanks for opening a new issue. Please help me reproduce this error:

Please provide the FROM-clause of your Dockerfile
Please provide your mix.exs (deps and releases part)

Since reproducing this error by guessing you configuration is pretty time-consuming please consider granting me read access to your repo so I can at least run mix test which should yield an error.

Don't get me wrong – to reproduce I would have

create project depending on :pdf_generator
write a call to PdfGenerator.generate on startup
prepare releases
build release
put that into a Docker container
run it in hopes of seeing the error

I am looking for a shortcut to this :-)

@feliperenan We could do this together in a new git repo, WDYT?

https://github.com/gutschilla/test-pdf-generator-alpine-docker

Sure, I'm still doing some investigation here and if I didn't find anything I will come up with some reproduced app. Just opened the issue to make sure I'm doing anything wrong and maybe others also is having it 😄

@feliperenan Added you as contributer. Allow me to create the boilerplate

Hey @gutschilla
I've found the issue, it's on my side and sorry to bother your about that :see

@feliperenan Thanks for your investigation and congrats for solving the issue. You are right, this error should emit some friendly warning like "please check if your chrome-headless-renderer-pdf is installed correctly as I cannot find the executable on PATH" or something.
I am happy to hear you suggestions.
On a side note: if you have questions about the code let me know. The underlying base dates back to 2015/16. It's been a while.

I'll reopen this so a PR can properly point to this.


chore(main): release 0.1.1

:robot: I have created a release beep boop
0.1.1 (2024-12-02)
Bug Fixes

release with PyPI's trusted publisher (b7ed5bd)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v0.1.1
:sunflower:


Add words "Optimist", "Pessimist" and "Pessimistic"

Add words Optimist, Pessimist and Pessimistic
Add all the definitions of Optimist in a file named Optimist.json
Add all the definitions of Pessimist in a file named Pessimist.json
Add all the definitions of Pessimistic in a file named Pessimistic.json
Refer Contribution.md for more details on how to contribute.
Comment here if you're are working on this issue to avoid conflicts.
Add reference to this issue i.e Issue #235 in your pull request description.

Let me check this

Check my PR @Showndarya


Move loader.js into subdirectory.

This is not technically needed, but it makes life a little easier when addons have bad treeForVendor hooks that include all of node_modules.
When that happens, we get an error saying that loader.js is both a file (from our lib folder before this change) and a directory.(from our own folder in node_modules for this package).
This avoids the issue by always using a subfolder for the imported file.

This change broke Ember Twiddle. I was depending on the location of loader.js: https://github.com/ember-cli/ember-twiddle/blob/dcd1eb5fab05147e21535e333e2d066f4b39247d/ember-cli-build.js#L57

You should be resolving the dependency rather than hard coding the path.

@rwjblue how to?


Update Dependecies formidable and superagent

Update the dependencies: formidable and superagent, please.

It is not my dependancy, it is a dependency of my dependency npm why superagent
Deprecated doesn't mean it doesn't work and need an update
To reinvent the wheel, you can create a fork and make a pull request


Gitbook Editor reverts any changes made externally

Bug Report
What is the current behavior?
Make a change to a file using a text editor of your choice. Save it. Now open that file in the Gitbook Editor. Your file has been reverted without any notification or confirmation.
What is the expected behavior?
It should detect the file as changed/unsaved and give you the opportunity to save the changes. At the very least just ask if I want to keep the change or revert to the most recently committed version.

For GitBook Editor

Operating System: Windows 10 Pro x64
(Desktop) Editor version: 6.2.1
Was the bug present in previous versions: Not sure as I never tried before.

It will be fixed by https://github.com/GitbookIO/feedback/issues/101
The editor only works with files in the GIT history.

@SamyPesse I'm not sure #101 is related. As I understand it, #101 is about creating new files from outside of the GitBook Editor.
These files I'm talking about in this issue were already in the git history, having been created from within the GitBook Editor already. In fact, I had added and modified them many times before using the GitBook Editor. But when I edited (not created) the files externally to the Editor, they became reverted when I opened the Editor again.

Yes, technically this is the same issue, #101 only describe one aspect of the problem. But basically this is about supporting edition/creation outside the editor.

We just released the first beta of 6.3.0, you can download it and read the full changelog at gitbook.com/editor/releases/all.
it adds basic synchronization with local files and git repository. Can you test and let me know if it works as expected?

I opened up GitBook Editor to a page, then opened that page in Notepad++ and added a line, then saved it. Almost immediately I saw a popup dialog in GitBook Editor telling me the file had changed externally and asked me to select which file(s) I wanted to sync changes with, and which files' changes I wanted to discard.
I selected the file I edited (actually it was already selected) and pressed sync. Within seconds I saw the icon in the corner show that there was 1 local change that hadn't been synced with the GitBook repository, and I saw the source in the editor update to show the change. But the preview window didn't update for several seconds, and then GitBook Editor locked up, using about 20% CPU (of my 8-cores) for so long that I was halfway finished writing this response (up to this point) before the application finally started responding again.
But I had pressed the X button in the corner to close it while it was still locked up, so it closed immediately when it started responding again.
So I just tried it again, this time undoing the little test edit I made, and I'm seeing similar behavior. It asked me what to sync, I press the sync button, the little cloud icon updates to show 2 unsynced changes now, the source window updated, a few seconds later the preview window updated, and the entire program is unresponsive and using ~20% CPU usage for about maybe 2-3 minutes before finally becoming responsive again and after that the CPU usage gradually goes down to normal levels.


Mismatch between TFLearn documentation and tutorial

Hi all,
The changes to the metric creation in Estimator in tflearn don't match the current documentation on monitors. For example:
https://www.tensorflow.org/versions/r0.11/tutorials/monitors/index.html
suggests:
validation_metrics = {"accuracy": tf.contrib.metrics.streaming_accuracy,
                      "precision": tf.contrib.metrics.streaming_precision,
                      "recall": tf.contrib.metrics.streaming_recall}
validation_monitor = tf.contrib.learn.monitors.ValidationMonitor(
    test_set.data,
    test_set.target,
    every_n_steps=50,
    metrics=validation_metrics)

wheras
https://github.com/tensorflow/tensorflow/blob/r0.11/tensorflow/contrib/learn/python/learn/estimators/rnn.py
contains:
# Single head metrics.
      if isinstance(predictions, dict):
        raise ValueError(
            'Metrics passed provide only name, no prediction, '
            'but predictions are dict. '
            'Metrics: %s, Targets: %s.' % (metrics, targets))

What related GitHub issues or StackOverflow threads have you found by searching the web for your problem?
None
Environment info
Operating System:
Max OSX El Capitan
Installed version of CUDA and cuDNN:
N/A - cpu version

The output from python -c "import tensorflow; print(tensorflow.__version__)".

0.11.0rc0
If possible, provide a minimal reproducible example (We usually don't have time to read hundreds of lines of your code)
https://gist.github.com/alexshires/d9674c58e352ad81be43f5f7da74c7e1
What other attempted solutions have you tried?
Looking up MetricSpec configuration - no examples or help available
Logs or other output that would be helpful
(If logs are large, please upload as attachment or provide link).
https://gist.github.com/alexshires/5310a751e9b767fbd3595570d618c342

Thanks for the detailed report @alexshires !
@martinwicke @ispirmustafa : IIRC, you guys were looking to switch to MetricSpec from a dict (a274c662b3f090193ead4138791896ffb65d680e). Would you be the right persons to fix the tutorial?

@sandersk, @ispirmustafa, looks like the monitors tutorial references an old form of metrics. Should we fix it, or are you making a new one for hooks anyway?

@martinwicke, since we need to update regardless, I think it would be ideal to replace the Monitors tutorial with a new one on Hooks. I will work with @ispirmustafa on that.

That's perfect, thanks!
On Thu, Oct 27, 2016 at 2:35 PM, Sanders Kleinfeld<EMAIL_ADDRESS>
wrote:

@martinwicke https://github.com/martinwicke, since we need to update
regardless, I think it would be ideal to replace the Monitors tutorial with
a new one on Hooks. I will work with @ispirmustafa
https://github.com/ispirmustafa on that.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/5005#issuecomment-256776051,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjO_WRgrPyv4F2-2Otn2M05lWeP-hRmks5q4RkTgaJpZM4KYhc_
.

I made a quick and dirty hack to the example code on my own fork for those who (like me) got stuck because of this: https://github.com/dbfr3qs/tensorflow/commit/e1006cf8307662e1984dba6560e67e246a7ba46c

We're still working on new tutorial content, but this particular issue is out of date.


Specific video fails to download

Please follow the guide below

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2016.06.25. If it's not read this FAQ entry and update. Issues with outdated version will be rejected.

[ X] I've verified and I assure that I'm running youtube-dl 2016.06.25

Before submitting an issue make sure you have:

[ X] At least skimmed through README and most notably FAQ and BUGS sections
[X ] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[ X] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
$ youtube-dl -v https://www.youtube.com/watch?v=IyFw9YgsCFw
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'-v', u'https://www.youtube.com/watch?v=IyFw9YgsCFw']
[debug] Encodings: locale US-ASCII, fs utf-8, out US-ASCII, pref US-ASCII
[debug] youtube-dl version 2016.06.25
[debug] Python version 2.7.11 - Darwin-15.5.0-x86_64-i386-64bit
[debug] exe versions: ffmpeg 3.0.2, ffprobe 3.0.2
[debug] Proxy map: {}
[youtube] IyFw9YgsCFw: Downloading webpage
[youtube] IyFw9YgsCFw: Downloading video info webpage
[youtube] IyFw9YgsCFw: Extracting video information
[youtube] IyFw9YgsCFw: Downloading MPD manifest
[youtube] IyFw9YgsCFw: Downloading MPD manifest
[debug] Invoking downloader on u'https://r9---sn-5hne6n76.googlevideo.com/videoplayback/id/232170f5882c085c/itag/137/source/yt_otf/requiressl/yes/pl/15/mm/31/nh/IgpwcjAyLmFtczE2KgkxMjcuMC4wLjE/mn/sn-5hne6n76/ms/au/initcwndbps/1131250/mv/m/ratebypass/yes/mime/video%2Fmp4/otfp/1/otf/1/lmt/1463190250552525/upn/3gIUDIbpv6k/key/dg_yt0/fexp/9416126,9416891,9419452,9422372,9422596,9428398,9431012,9431418,9433096,9433380,9433946,9435242,9435409,9435526,9435876,9436928,9437066,9437553,9437652,9437740,9438662,9438804,9439652,9439748,9439882,9439884,9439944/mt/1466927622/signature/7ACB9B8186774BFE97E7B9A6CD88514304A8C5AD.4D1F9B20FBAA4BC234F7C12A7A5EE489B8CB4105/sver/3/ip/<IP_ADDRESS>/ipbits/0/expire/1466949541/sparams/ip,ipbits,expire,id,itag,source,requiressl,pl,mm,nh,mn,ms,initcwndbps,mv,ratebypass,mime,otfp,otf,lmt/'
[dashsegments] Total fragments: 20
[download] Destination: Compliatie _ 4x Ambulance met spoed in Breda!-IyFw9YgsCFw.f137.mp4

Description of your issue, suggested solution and other information
Download fails https://www.youtube.com/watch?v=IyFw9YgsCFw
The issue is specific to this video, I haven't seen it on other video's.
As an added info, also the Youtube app (iPad) doesn't play it. Mobile safari also doesn't play it.
It does play on OSX Chrome.

It downloads fine according to your log and it plays fine by vlc, mpv, wmp.

Not, it doesn't : it hangs at the last line.

Disable IPv6 with -4.


dbt-adapter-tests for MySQL

Describe the bug
dbt-adapter-tests assumes support for certain SQL syntax that is not supported by different versions of MySQL.
Steps To Reproduce
Something similar to the following should expose this issue (for the data_test test):
$ pip install pytest-dbt-adapter
$ pytest test/mysql.dbtspec

Expected behavior
This shouldn't fail for SQL syntax reasons.
Example
An example that doesn't work for MySQL 8.0:
select 1 as id where id = 2

The following alternative works for MySQL 8.0 but not for 5.6 or 5.7:
select 1 id where 1 = 1

This alternative works for all versions of MySQL:
select 1 id from dual where 1 = 1

Unfortunately, a simple pull request to dbt-adapter-tests won't resolve this since not all databases have a dual table. A notable example is MS SQL Server.

Here's a branch with the necessary changes:

https://github.com/dbeatty10/dbt-adapter-tests/tree/mysql


HTML chars >< are escaped in query log

What did you do?
Enable query log and run the query oo > 0
What did you expect to see?
In the query log:
"query":"oo > 0"
What did you see instead? Under which circumstances?
In the query log:
"query":"oo \u003e 0"

Prometheus version:
v2.16.0

Additional info:
This is fix by unrelased go-kit:
https://github.com/go-kit/kit/commit/913ff7dc1f45175b3f5b094721716b3efde5b3da
https://github.com/go-kit/kit/pull/914

We could copy https://github.com/go-kit/kit/blob/913ff7dc1f45175b3f5b094721716b3efde5b3da/log/json_logger.go internally but I would prefer to wait for a release of go-kit and fix it later.


WSL X11 to Windows

Hello, thank you for this great tutorial. Many useful ideas are highlighted and it is very informative.
On my computer I connect to WSL Windows Subsystem for Linux. Launching a GUI application, in my case, would not work. The reasons could be SSH which X11 server on Windows 10 (XLaunch) is already taken up by Visual Studio debugging. Is there a workaround that enable debugging GUI programs from Visual Studio in WSL using Windows 10 as X11 display server?

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

ID: 4535255d-395b-6b11-daf3-b03e0c3ad87d
Version Independent ID: 1aad5206-ea1e-630c-800a-bb79bbd942b4
Content: Create C++ cross-platform projects in Visual Studio
Content Source: docs/build/get-started-linux-cmake.md
Product: visual-cpp
Technology: cpp-tools
GitHub Login: @corob-msft
Microsoft Alias: corob

@Coarist
That's an interesting question, but you're probably asking in the wrong place. For product questions like this, I'd recommend the Visual Studio C++ Developer Community site. That's where the developers who can tell if it's a bug with a workaround, an unimplemented feature, or just an oversight in the docs can respond. If the documentation needs to be updated to address the issue, they'll let us know. Closing for now, but if you respond with a link to the issue on Developer Community, and a doc change is needed, that will help us link it up. Thanks, and good luck.


Use Obsidian & Dataview metadataCache instead of parsing fileContent

Use Obs cache for yaml fields.
Then if(app.plugins.plugins.dataview), use dv cache for inline fields app.plugins.plugins.dataview.api.page(<path>).
Group them all together, and generate the graphs from there

I've made some good progress with this! If the user has dataview installed, everything works just as it used to, but faster! I have not done the same if they don't have dataview, though

Issue from #10: Dataview indices aren't loaded by the time the BreadcrumbsView tries to populate

Obsidian version: 0.12.4
Breadcrumbs plugin: 0.2.1
Dataview: 0.3.13
My breadcrumb view is empty now. Tried clean reinstall of the plugin and also disabling and re-enabling the plugin.
Ther are some error logs (also, I noticed that the plugin says "loading plugin" instead of "loading Breadcrumbs plugin". This is what I get when I start Obsidian. I think it might be due to dataview not having populated its index yet. Don't think there's much that can be done until Dataview provides an API to check if indexing is done.

Fixed in 0.4.0


mgmt: mcumgr: transport: src: fix smp_udp_open() corrupting socket var

When smp_udp_open() was executed more than once, create_socket() returned an error code (EALREADY) rather than a newly created socket FD. This error was saved in a global variable that was then directly accessed in a thread by recvfrom(), causing the loop in the thread to start spinning and printing error messages uninterruptedly.

@thedjnK
when CONFIG_MCUMGR_TRANSPORT_UDP_AUTOMATIC_INIT is enabled, smp_udp_open() is called directly from smp_udp_net_event_handler() everytime NET_EVENT_L4_CONNECTED event triggers. If you dig a bit in Zephyr repository, you would understand why this is very probable to happen. Clues are in smp_udp.c itself.
In regards to your door example, your review would sound more professional without it. Thanks

I can't replicate any issue without this patch using things that are in-tree, during init that might called multiple times but would run the disconnected path each time for ethernet drivers, then once the network driver starts would be called once each time layer 4 connectivity appears or vanishes, so even if there are multiple network connections, it will only be called once when one of them gets connectivity (connected) or when all of them lose connectivity (disconnected) and in the disconnected path, the thread is aborted. Not that I'm against this change but given that I'm unable to reproduce the issue, please describe how you are.

@nordicjm, as @nixward has pointed out, when CONFIG_NET_MGMT_EVENT and CONFIG_NET_CONNECTION_MANAGER are enabled, the API net_conn_mgr_resend_status() is implemented and it goes through all the registered callback functions and notifies them of the connection status, even if they had already been notified about it. This API function can be called arbitrarily from anywhere in the code (Zephyr or application) at any time.
When CONFIG_MCUMGR_TRANSPORT_UDP_AUTOMATIC_INIT is enabled, smp_udp_start() is one of the places where net_conn_mgr_resend_status() is called, other places are:

zephyr/subsys/shell/backends/shell_mqtt.c
multiple Zephyr's samples projects
potentially user application code

When at init time a software module requires to know the connection status and registers a callback function via net_mgmt_add_event_callback(), it is likely that net_conn_mgr_resend_status() is called straight after in order to allow the callback function to process the current connection status.
In an ideal world, smp_udp_open() would be called only once and never again.
However, this function itself implements a basic safety-check and executes create_thread() only if create_socket() was successful. In case smp_udp_open() was already called before, create_socket() would correctly fail and the smp_udp_open() would return an error. However, the bug this PR is attempting to fix, is currently causing the thread to turn into a useless and never-ending loop executing LOG_ERR() statements and basically killing communication via MCUMGR over UDP.

@nordicjm looks like your PR https://github.com/zephyrproject-rtos/zephyr/pull/58065 supersedes mine. Yours does fix the bug pointed out here and provides additional improvements.
I believe this PR can be closed if yours gets merged in.

@marco85mars20 this PR could still be useful as a backport PR to fix this issue in older releases.

Feel free to submit this to the v3.3-branch if you want it backported.

As suggested by @nordicjm and @nixward, I have rebased this PR into v3.3-branch to get it backported to older releases.

@nordicjm could you please check why the Zephyr's CI is failing to build?

Closing this PR and opening a new one to merge into v3.3-branch


Apply material design 3 to MaterialSlider

Mark the old one as obsolete.
Create the new version on the new M3 folder.
Apply default styles.
Apply the new look and feel proposed by M3.
Use the MaterialCustomControl in the same way that we used in the MaterialRating.

https://m3.material.io/components/sliders/specs

We are excited to announce that we are working on a new generation of controls based on Material Design V3, which we will be releasing soon.
This ticket has been included/fixed in the upcoming version of this NuGet package, which will include both current and new generations of controls.


Hide last empty row for months that don't need it

A number of months do not need the last row. Would be nice if this row is hidden for those months that can live without. I can imagine some designs would prefer to have a static layout (i.e. not shrinking during every month toggle), so in case you like to honor this request, I'd make it configurable.

This has been implemented in v0.0.11 - showEmptyRow is the config option (link to docs page). Let me know if you have any issues!


push per-thread statistics to parent immediately

In the current implementation, each Goose client thread processes requests and maintains statistics, which are pushed up to the client every 15 seconds.
The intent of this PR is to instead push the raw requests/response details to the parent immediately, offloading the overhead of calculating statistics so clients can run as quickly as possible. This will primarily benefit a Goose Attack if the load test server isn't already using 100% of the CPU.
Performance:
Crossbeam

With a non-starved CPU we're seeing a ~2% performance improvement
With a starved CPU we're seeing a ~2-3% performance improvement

Tokio mpsc

With a non-starved CPU we're seeing a ~2.1% performance improvement
With a starved CPU we're seeing a ~1-2% performance improvement

The raw numbers:

https://docs.google.com/spreadsheets/d/18qW_ZTWeY5apSSIeGhT298DzVA0IIs2kHxq9wAbkgGE/edit#gid=0

I'm leaning toward using Tokio mpsc as Tokio is already a dependency, and it's definitely preferred you don't starve the load test server for the most reliable numbers.

I had hoped for a more clear winner between Crossbeam and Tokyio sync, but since they're both offering similar performance and we already depend on Tokio, I went with that.


Consider deprecating @layer.mouse_drag_callbacks.append syntax

@sofroniewn got me thinking about mouse & key callbacks recently, both of which pose small (but solvable) problems for trimming down our models and Viewer/Layer objects to their "essential data".  Currently, we store callbacks on the classes and instances themselves, in special dicts and lists for the purposes.
The primary advantage I can see is the nifty decorator that we have in our examples:
my_layer = viewer.add_points()

@my_layer.mouse_drag_callbacks.append
def my_callback(): ...

These attributes aren't exactly fundamental data about the layer or viewer though, and their mixin classes (the classes that actually add the mouse_drag_callbacks, etc... attributes to the subclass) make it a bit difficult to use them in pydantic-style classes.  Additionally, it scatters our key/mouse-binding information across a lot of different objects, making it a bit harder to ask "what's bound to the C key?"
One option would be to make those mixins purely behavioral (methods only), where the bind_mouse_callback method would store the actual event/callback binding elsewhere in some more global mapping.  That solves a handful of problems, but it means we'd need to change the example above to something like:
my_layer = viewer.add_points()

@my_layer.bind_mouse_drag_callback  # no "append" here
def my_callback(): ...

thoughts?

One option would be to make those mixins purely behavioral (methods only), where the bind_mouse_callback method would store the actual event/callback binding elsewhere in some more global mapping.

Yes, I prefer using methods here and think it will give us greater control. It will also bring things closer in line with our @bind_key approach.
I wonder when we do this if it isn't also an opportunity to look at some of the proposals in #1048 again too, for example we could do something like @bind_mouse('press') too.
Ideally we could do this in a way with deprecations. If so then I say full steam ahead. I'm also thinking about how to let plugins provide interactive callbacks, but will make a new issue for that.


[AutoPR apimanagement/resource-manager] [Hub Generated] Review request for Microsoft.ApiManagement to add version stable/2019-01-01

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/5568

This PR has been merged into https://github.com/Azure/azure-sdk-for-js/pull/2121


Add new lua package: lpty

I needed this package for Prosody's external authentication functionality to work.
More info on it here:   http://www.tset.de/lpty

Travis passed, thanks.


Added Palindromic Numbers in Every Language Article

Whenever you finish your changes, we'll be good to merge.

I think I've done everything. You may check and let me know if there are other things you'd want me to do.

I'm having a little problem renaming the folder to palindrom-number, I will make another pull request if I'm able to figure it out.

It's fixed I think

Sure. Thanks


Failed to download the image (Intel macOS)

Description
The image linked in .lima/default/lima.yaml gives a 404.
a11ce@cat ~/D/c/O/msl> limactl start
INFO[0000] Using the existing instance "default"
INFO[0000] Attempting to download the image from "~/Downloads/hirsute-server-cloudimg-amd64.img"
INFO[0000] Attempting to download the image from "https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64.img"
FATA[0000] failed to download the image, attempted 4 candidates, errors=[failed to download "~/Downloads/hirsute-server-cloudimg-amd64.img": failed to open source /Users/a11ce/Downloads/hirsute-server-cloudimg-amd64.img: open /Users/a11ce/Downloads/hirsute-server-cloudimg-amd64.img: no such file or directory unsupported arch: "aarch64" failed to download "https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64.img": expected HTTP status 200, got 404 Not Found unsupported arch: "aarch64"]

a11ce@cat ~/downloads> wget "https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64.img"
--2022-09-20 16:39:46--  https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64.img
Resolving cloud-images.ubuntu.com (cloud-images.ubuntu.com)... <IP_ADDRESS>, <IP_ADDRESS>
Connecting to cloud-images.ubuntu.com (cloud-images.ubuntu.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2022-09-20 16:39:49 ERROR 404: Not Found.

Nevermind, brew on 10.14 installs Lima 0.7.1


Image name is not parsed correctly

When I try to start a TestContainer with an Azurite container (mcr.microsoft.com/azure-storage/azurite), it fails with the following message:
Docker.DotNet.DockerApiException : Docker API responded with status code=NotFound, response={"message":"manifest for mcr.microsoft.com/azure-storage:latest not found: manifest unknown: manifest unknown"}
It appears as if the name of the container is not parsed correctly (azure-storage/azurite vs azure-storage:latest).
To Reproduce
Dot not work:

            var testcontainersBuilder = new TestcontainersBuilder<TestcontainersContainer>()
              .WithImage("mcr.microsoft.com/azure-storage/azurite")
              .WithName("azurite")
              .WithPortBinding(10000)
              .WithWaitStrategy(Wait.ForUnixContainer().UntilPortIsAvailable(10000));
            BlobContainer = testcontainersBuilder.Build();
            await BlobContainer.StartAsync();

Note: The problem does not appear if a version is added to the container name. e.g. mcr.microsoft.com/azure-storage/azurite:latest
Does work:

            var testcontainersBuilder = new TestcontainersBuilder<TestcontainersContainer>()
              .WithImage("mcr.microsoft.com/azure-storage/azurite:latest")
              .WithName("azurite")
              .WithPortBinding(10000)
              .WithWaitStrategy(Wait.ForUnixContainer().UntilPortIsAvailable(10000));
            BlobContainer = testcontainersBuilder.Build();
            await BlobContainer.StartAsync();

Expected behavior
The container should start.
dotnet-testcontainers 1.2.0

Should be fixed in #233 and published in 1.3.0-beta.20200409.3.


Ollama create test -f ./Modelfile error ==> Error: command must be one of "from", "license", "template", "system", "adapter", "parameter", or "message"

What is the issue?
Ollama create test -f ./Modelfile error ==> Error: command must be one of "from", "license", "template", "system", "adapter", "parameter", or "message"
same Modelfile works in version 0.1,33, but the above error occurs in version 0.1.38
0.1.33

0.1.38

OS: Ubuntu 22.04.2 LTS
OS
Linux
GPU
Nvidia
CPU
Intel
Ollama version
0.1.38

@farmountain can you post the modelfile?

weird, it works if I paste the prompt into Modelfile 1 by 1...

lets close this for now until I have clearer understand of the error. Thanks

Hi, I have this problem too.

@ajcookservices what version of Ollama?

My situation is that the first line in the generated Modelfile is "failed to get console mode for stdout: The handle is invalid." Deleting this line and then executing the command to create a new model works.

@ZhangChi7 I that sounds like a Windows issue. How did you create the file?


window is not defined - running under NodeJS

Hi! We use your library over at Buttercup, and we're upgrading kdbxweb. It seems we've encountered an issue where the current copy of this library references window:
/*! kdbxweb v1.5.2, (c) 2019 Antelle, opensource.org/licenses/MIT */
(function webpackUniversalModuleDefinition(root, factory) {
	if(typeof exports === 'object' && typeof module === 'object')
		module.exports = factory(require("crypto"), require("xmldom"));
	else if(typeof define === 'function' && define.amd)
		define(["crypto", "xmldom"], factory);
	else if(typeof exports === 'object')
		exports["kdbxweb"] = factory(require("crypto"), require("xmldom"));
	else
		root["kdbxweb"] = factory(root["crypto"], root["xmldom"]);
})(window, function(__WEBPACK_EXTERNAL_MODULE__42__, __WEBPACK_EXTERNAL_MODULE__44__) {
return /******/ (function(modules) { // webpackBootstrap

Which is of course undefined:
ReferenceError: window is not defined
    at eval (webpack:///./node_modules/kdbxweb/dist/kdbxweb.js?:4:4)
    at Object../node_modules/kdbxweb/dist/kdbxweb.js (/Users/pez/git/buttercup-importer/dist/buttercup-importer.js:2311:1)
    at __webpack_require__ (/Users/pez/git/buttercup-importer/dist/buttercup-importer.js:21:30)
    at eval (webpack:///./source/importers/KDBXImporter.js?:2:15)

This only cropped up after updating from 1.2.7 to 1.5.2. I'm using Node v10 at the moment.

Ok, I fixed the issue myself as I'm using Webpack to bundle for node+browser - Using imports-loader I simply do: const KDBXWeb = require("imports-loader?window=>this!kdbxweb");
This of course doesn't fix it on Node, but only if you bundle this library further.

Fixed this, it should work well in 1.5.3.

This.. is probably the fastest response and fix I've ever seen. Amazing @antelle!


Cosmoogy: CAMB with Neff=0 does not complain...

Hi, I report a possible problem that can be avoided by making a more restrictive parameters x-check:
If you run this small snippet
cosmo_ccl = ccl.Cosmology(
    Omega_c=0.3, Omega_b=0.05,
    h=0.7, A_s=1.58e-9, n_s=0.96,
    transfer_function='boltzmann_class', matter_power_spectrum='halofit')

sigma8=cosmo_ccl.sigma8()
print(sigma8)

cosmo_ccl = ccl.Cosmology(
    Omega_c=0.3, Omega_b=0.05,
    h=0.7, A_s=1.58e-9, n_s=0.96,
    transfer_function='boltzmann_camb', matter_power_spectrum='halofit')

sigma8 = cosmo_ccl.sigma8()
print(sigma8)

cosmo_ccl = ccl.Cosmology(
    Omega_c=0.3, Omega_b=0.05,
    h=0.7, A_s=1.58e-9, n_s=0.96, Neff=0,
    transfer_function='boltzmann_camb', matter_power_spectrum='halofit')

sigma8=cosmo_ccl.sigma8()
print(sigma8)

cosmo_ccl = ccl.Cosmology(
    Omega_c=0.3, Omega_b=0.05,
    h=0.7, A_s=1.58e-9, n_s=0.96, Neff=0,
    transfer_function='boltzmann_class', matter_power_spectrum='halofit')

sigma8=cosmo_ccl.sigma8()

you will get
0.8005284561523333            # class sigma8
0.8005634892329894           # camb sigma8
1.083442499820305              # camb sigma8 if user set wrongly Neff=0

ans a crash if you use Neff=0 with Class: with this message
Error in Class: thermodynamics_init(L:344) :error in thermodynamics_helium_from_bbn(ppr,pba,pth);
=>thermodynamics_helium_from_bbn(L:620) :condition (DeltaNeff < deltaN[0]) is true; You have asked for an unrealistic small value of Delta N_eff = -3.046000e+00. The corresponding value of the primordial helium fraction cannot be found in the interpolation table. If you really want this value, you should fix YHe to a given value rather than to BBN

I am pretty sure that CAMB may also complain with the user wrongly setting Neff=0, but I think CCL can help the user with an ERROR raising.

CLASS apparently only fails because the He fraction is out of the internal interpolator's bounds for this extreme value of Neff. It's not like it's doing a check to see whether Neff makes sense. I had a go at CAMB and it looks like it also works with negative values of Neff.
I think this is a clear case of Garbage-In-Garbage-Out. If users really want to put in such extreme values of Neff they should be free to do so. We have too many neutrino consistency warnings anyway.

To me this looks more like a boltzmann solver issue than a CCL issue. I'll leave it open a bit longer for others to chime in (@c-d-leonard ?) and will then close


Edit: Fix userContextFiles missing from context response

Description
Ensures we populate the user context files with the associated content when building our context messages.
We already do this for Chat, we just also need to do the same for Edit too.
Test plan

Start an instruction-based edit with Opt+K
@ mention a file
Execute an edit, check that the file that was mentioned is included as context

Thanks! I can't tell from the PR description, but sorry if I regressed this. 😄


Register package

https://github.com/JuliaRegistries/General/pull/61020

@JuliaRegistrator register

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/61050
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.0 -m "<description of version>" 086dbb282df929935c77baea68dfbdca3e2fbdb4
git push origin v0.1.0

@JuliaRegistrator register

Error while trying to register: "Tag with name v0.1.0 already exists and points to a different commit"

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/61250
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.1 -m "<description of version>" ab230f04e1e47db2cda4427b709cef450bbcf6be
git push origin v0.1.1

https://github.com/JuliaRegistries/General/pull/61020

https://github.com/JuliaRegistrator

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/61266
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.2 -m "<description of version>" f0469a60667aae6daf91a18bdacac6bb089a825f
git push origin v0.1.2

@JuliaRegistrator register

Error while trying to register: "Tag with name v0.1.2 already exists and points to a different commit"

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/62979
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.3 -m "<description of version>" fd321ed19f39ab1d69c16912aef4e305ad774285
git push origin v0.1.3

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/62992
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.4 -m "<description of version>" 8125784b11689bbc83fcbbf1ec3d6d0f9295fc4b
git push origin v0.1.4

@JuliaRegistrator register

Error while trying to register: "Tag with name v0.1.4 already exists and points to a different commit"

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/63129
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.5 -m "<description of version>" bdf89ce01e471330ccf9cbe5c55c1588b7351824
git push origin v0.1.5

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/63562
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.6 -m "<description of version>" 244392dd2e4e64abc65d9bc875585cc40a09f263
git push origin v0.1.6

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/81261
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.7 -m "<description of version>" f9ea76ce48ecdb2355977e961a909eb6303e3170
git push origin v0.1.7

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/103057
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.2.0 -m "<description of version>" bedfbbd09e3524741278ced0bf5e15b716895a7c
git push origin v0.2.0

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/103186
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.2.1 -m "<description of version>" de5f14b1b09b195ffaef13ed44ac88aebf7caf55
git push origin v0.2.1

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/103909
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.2.2 -m "<description of version>" f3de6ad61b90a1e786f10a1dda3a2abd15f74a6b
git push origin v0.2.2

@JuliaRegistrator register
Release notes:
Breaking changes
the log file format changed, old log files cannot be opened with this version
the number of segments is added as meta data to the log files
five variables have been added to the SystemState that can be freely used, their names can be added as meta data to the log file

New Features
the example autopilot.jl was vastly improved
a menu with 6 pre-defined plots was added to the GUI
a statistics dialog was added
saving and loading of log files added
a second menu was added that allows to change the tolerance of the solver

Registration pull request created: JuliaRegistries/General/103951
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.0 -m "<description of version>" 029afa2fa4deb4c28a71f4e75e42ffe1e2ad7e7a
git push origin v0.3.0

Registration pull request updated: JuliaRegistries/General/103951
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.0 -m "<description of version>" 029afa2fa4deb4c28a71f4e75e42ffe1e2ad7e7a
git push origin v0.3.0

Registration pull request updated: JuliaRegistries/General/103951
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.0 -m "<description of version>" 029afa2fa4deb4c28a71f4e75e42ffe1e2ad7e7a
git push origin v0.3.0

Registration pull request updated: JuliaRegistries/General/103951
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.0 -m "<description of version>" 029afa2fa4deb4c28a71f4e75e42ffe1e2ad7e7a
git push origin v0.3.0

@JuliaRegistrator register

Release notes:

Breaking changes

the log file format changed, old log files cannot be opened with this version
the number of segments is added as meta data to the log files
five variables have been added to the SystemState that can be freely used, their names can be added as meta data to the log file

New Features

the example autopilot.jl was vastly improved
a menu with 6 pre-defined plots was added to the GUI
a statistics dialog was added
saving and loading of log files added
a second menu was added that allows to change the tolerance of the solver

Registration pull request updated: JuliaRegistries/General/103951
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.0 -m "<description of version>" ff4af2ed6ec9ae43247f1c74d34cd6cce4cac7f4
git push origin v0.3.0

@JuliaRegistrator register
Release notes:
Fixes

fix script create_sys_image

Registration pull request created: JuliaRegistries/General/103964
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.1 -m "<description of version>" 27acf3fd275e02a1dd76f8e2476f349e3a1cfe53
git push origin v0.3.1

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/103966
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.2 -m "<description of version>" 34c2b962e84bfd3376165c32d0329bce52797849
git push origin v0.3.2

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/103967
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.3 -m "<description of version>" beb0c2a2ffad760d23a8d36fc210c743d7e6f3e5
git push origin v0.3.3

@JuliaRegistrator register

Registration pull request updated: JuliaRegistries/General/103967
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.3 -m "<description of version>" 0277ed2141ed14fe610fd8487d82add294df97fb
git push origin v0.3.3

@JuliaRegistrator register
Release notes:
Fixes

fix autopilot.jl
fix script create_sys_image

Registration pull request created: JuliaRegistries/General/103993
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.4 -m "<description of version>" 5303d4caef7173b3f88d14f4a32e22e4ccd8c356
git push origin v0.3.4

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/104200
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.5 -m "<description of version>" 28967de0f9db1cca06670e92ef2af09cedd29607
git push origin v0.3.5

@JuliaRegistrator register
Release notes:
Fixes

fix print_statistics() function

Registration pull request created: JuliaRegistries/General/104212
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.6 -m "<description of version>" 9caee055e434743af85f7347613ddbed049c7147
git push origin v0.3.6

@JuliaRegistrator register
Release notes:
Changes

replace the plotting library Plots with ControlPlots to speed up compilation and to avoid error messages
the autopilot example GUI provides now the possibility to load three different projects (well, any project file that has the ending .yml and exists in the data folder)
the configuration of the flight path controller and flight path planner happens now using the related .yaml files
more diagrams added, statistics dialog extended
log files are now stored in the output folder by default

https://github.com/JuliaRegistries/General/pull/61020
Release notes:
Fixes

fix the .bat files needed for Windows using Julia 1.10
update the documentation

Registration pull request created: JuliaRegistries/General/106506
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.8 -m "<description of version>" 52c261e74f2d3e3820f28e7f47da028b75f28543
git push origin v0.3.8

@JuliaRegistrator register
Release notes:
Fixes

all batch files now use .so as file ending of the system image instead of .dll

Registration pull request created: JuliaRegistries/General/106528
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.9 -m "<description of version>" 43ac366a65a8c83bf9368dba414673e94c79ab25
git push origin v0.3.9

@JuliaRegistrator register
Release notes:
Added

add control_plots_II diagram
add hydra20_926 project with high wind speed
add copyright waiver from TU Delft
add section kps4_3l to settings files
add function fulldir() to this package
add documentation page autopilot.md

Changed

the script autopilot.jl is logging additional fields
update the hydra20 projects, both work fine now
bump KiteControllers to 0.2.6
bump KiteModels to 0.5.16
bump KiteUtils to 0.6.16
remove support of Julia 1.9
fix the example plot_log.jl
update documentation of logging

Registration pull request created: JuliaRegistries/General/110402
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.10 -m "<description of version>" dd4878b0740aeb1b96467a9767193493d1c4460f
git push origin v0.3.10

@JuliaRegistrator register
Release notes:
Added

add documentation joystick.md

Changed

reduced simulation frequency to 20 Hz as required for Windows
reduced default time-lapse to 6x as required for Windows
use FAST_EXP instead of EXP law for the hydra20 settings to improve performance
smaller font for Windows
fix the example joystick.jl
update README.md

Registration pull request created: JuliaRegistries/General/110660
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.11 -m "<description of version>" 4dacae80d774bf2e0d984e1f2fa9ffd1e6169c0a
git push origin v0.3.11

@JuliaRegistrator register
Release notes:
Changed

bump KiteControllers to 0.6.7
bump GLMakie to 0.10.5

Added

add project hydra10_951

Fixed

fix the wind profile for the hydra20 projects
saving of plots works again
all examples have been tested and fixed where needed

Registration pull request created: JuliaRegistries/General/111142
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.12 -m "<description of version>" 0c075c1ffdc80a6a9a9a5e5f5ce2d8d339ebed35
git push origin v0.3.12

Registration pull request created: JuliaRegistries/General/112010
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.13 -m "<description of version>" f37f52857f6177a63d44765f5ef6d8e6feffaafe
git push origin v0.3.13

Registration pull request created: JuliaRegistries/General/114830
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.4.0 -m "<description of version>" e1fc2fb13eea7c3842d96864d488042b28115fa4
git push origin v0.4.0

@JuliaRegistrator register
Release notes:
Changed

the build script now only installs matplotlib if it is not yet installed on the system
improved the example joystick.jl and its documentation
bump KiteControllers to 0.2.10
bump KiteModels to 0.6.6
A new kite model (KPS4_3L) was added, that uses three winches at the ground to steer the kite.
The new variant (version 3) of the KPS4 kite model allows to define polars that do not depend on the steering input, which makes it easier to define new kites.
bump KitePodModels to 0.3.3
A simplified KitePodModel was added with a linear relationship between depower setting and depower angle, which makes it easier to define new KCUs.

Added

a new, torque controlled winch model
you can now define the diameter and the aerodynamic drag coefficient of the KCU
plot aerodynamics

Fixed

changes of the polars had no effect
changes of max_steering had no effect
fix example compare_kps3_kps4.jl

Braking

the function next_step! now requires either the parameter set_speed, which replaces v_ro, or the parameter set_torque, depending on the question if you use the AsynchGenerator or TorqueControlledWinch in the settings
the function init_sim has the new parameter delta. It should be between 0.0 and 0.03 and defines the pre-tension of the tether. The parameter stiffness_factor should be between 0.1 and 1.0 and not longer smaller than 0.1.
the constructor FPCSettings now requires the named parameter dt
the constructor SystemStateControl now requires the named parameter u_d0 and u_d

Registration pull request created: JuliaRegistries/General/114862
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.4.1 -m "<description of version>" 60626e068fb1ea6490bba429f87be2f76f3d1284
git push origin v0.4.1

Registration pull request updated: JuliaRegistries/General/114862
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.4.1 -m "<description of version>" 60626e068fb1ea6490bba429f87be2f76f3d1284
git push origin v0.4.1


Update docker-compose.yml Resolve #207

Resolve #207
Update migrations command in docker-compose.yml

see #207


TODO notice, but no issue link in source

Is your proposal related to a problem?

No.
Describe the solution you'd like

https://github.com/facebook/create-react-app/blob/bbd5a6015561c6ff8a18d99b4f852c9b10e55198/packages/react-scripts/scripts/test.js#L86
I'd like an issue number next to this TODO. No one will know if it's fixed or not and if this code can be removed.
Describe alternatives you've considered

N/A
Additional context

N/A

Whoops. It was listed higher up.


Enforce consistent code style

I've noticed that there are a few places in the codebase (i.e. FileSource) which use inconsistent code style.
Would you be happy with an enforced code style, perhaps via the Spotless Gradle plugin, which allows folks to easily apply code style changes through ./gradlew spotlessApply, instead of needing any other local setup?
If so, are there any preferences you would have? I.e. are you happy with Google Java code style, or would another style be preferable?

It's been on my list for a while to think about this.
I'm not really a fan of heavy-handed code style enforcement in the build as I find you can end up fighting it when you want a little discretion.
But having said that enforcing a few basics, in particular indentation and brace placement would make merging PRs a hell of a lot easier so perhaps we can start there rather than enforcing a full code style?

That's interesting - are there any cases where you would see i.e. Google Java code style not being suitable?
Having used differing code styles over the years, I've got to the point where I'd rather have something consistent that takes away any choice from the implementer, and just keeps things consistent
But I get your point, and as you're gonna be working with the code the most, your opinion is most important :grinning:
It could be the eclipse-jdt configuration is best as it'll provide you the opportunity to hand-craft the required code style you'd like?

I don't think there's anything unsuitable in the Google code style specifically. It's just that my memory of working on projects where there's build-time enforcement is that it's like having an overly pedantic teammate nagging you about trivia.
But I also get your point, and TBH the priority should be making it as easy as possible for others to contribute, rather than my own foibles.
If you're happy to open a PR with the Google style enforced, then we can take a look. I guess the clincher might be whether it's going to take days/weeks of work to make the codebase compliant.

Thanks Tom! I've rasied #1563 for this - fortunately Spotless allows it to be really straightforward to get set up, and to apply against the codebase.
This will cause a lot of conflicts for folks who've already got branches/PRs open - unfortunately I don't have a good suggestion for how to manage this so well :disappointed:
So the current codebase can be up-to-date easily, but the difficulty will be on folks who've got open contributions.

Thanks for this.
Agree that existing PRs are going to be a bit of a nightmare so I'm going to park this until I've got 2.29.1 released, then probably try and merge the PRs I think are a priority before pulling the pin out of the grenade.

Sounds like a plan - I'll mark the PR as a draft for now then

Sounds like a plan - I'll mark the PR as a draft for now then

This might help: https://github.com/diffplug/spotless/tree/main/plugin-gradle#ratchet

Sorry looks like my reply didn't send - we certainly can do it with ratcheting - I was thinking going for a "big bang" approach would mean some merge conflicts now, but it's reduced soon, whereas ratchet will slowly bring the changes in and folks may have style-related merge conflicts for some time.
It's a balance - sorry for not raising it as I had considered it, and my personal preference is "big bang". What do you think?

I tend to lean towards doing most things iteratively, so I think I'd prefer the ratcheting approach. It would also be an opportunity for me to get used to working with it without 100% committing up front. Ratcheting doesn't preclude going all-in at some point, but it's harder to back out if you've taken the big bang approach.

That makes sense ☺ in which case, the PR should be ready to review when you get a chance!


Replace hashicorp/go-uuid import with gofrs/uuid

Replace import of hashicorp/go-uuid as its license MPL 2.0 is not incompatible with the license of the project Apache 2.0. Instead use gofrs/uuid which is compatible. It uses an MIT license.

I am not sure why MPL would be incompatible with this project, but I like the idea of switching to a compliant UUIDv4 generator. What do you think of https://github.com/gofrs/uuid which is also MIT?

MPL 2.0 is not compatible with Apache 2.0. The project I work on has a license scanner and it flagged the go-uuid dependency as incompatible. I traced it coming from gophercloud as we don't import it ourselves. I am fine with that one. I picked the google one, but if you prefer gofrs that works for me.

Well, thank you then!

Updated the PR to replace it with gofrs/uuid instead.


Drop the dependency on s3fs

I think it would be a good improvement to drop the dependency on s3fs and instead use aws-sdk directly. This would save the extra dependencies and give us access to upstream updates quicker.
I would be happy to provide the code if no one beats me to it.
On a related note, it seems like uploading to s3 from multer is very popular. How would you feel about getting some help on maintaining this module? I would personally be happy to hop on as a maintainer. Since it's such a small module I think the most work would be to cut new releases when dependencies (probably only aws-sdk) updates, and to answer questions from users.
I'm linusu on npm :smile:

I'd love help on this module!  The only real value I added was making sure the integration worked - the rest was trivial yet I didn't see other modules doing the same thing.  I don't have much time myself on open source unfortunately.
I'd be happy to take any pull requests.  I can also add you as a maintainer


problem editing pipelines created using azure-devops extension

Wen creating a pipeline using the az pipelines create command, the pipeline works fine, but if I edit it in the Azure DevOps web interface (yaml editor), i get this error consistently

If I from te web interface delete the pipeline and recreate it (still in the the web ui) pointing to the same repo/yaml file, it works fine it will work again, and now the editor will also show the yaml file without problems.
I had
Version information:
I had the same problem on azure-cli 2.0.79 with devops 0.16.0 - updating did not help. Here is current version information:
azure-cli                          2.6.0
command-modules-nspkg              2.0.3
core                               2.6.0
nspkg                              3.0.4
telemetry                          1.0.4
Extensions:
azure-devops                      0.18.0
Python location 'C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\python.exe'
Extensions directory 'C:\Users\anrem.azure\cliextensions'
Python (Windows) 3.6.6 (v3.6.6:4cf1f54eb7, Jun 27 2018, 02:47:15) [MSC v.1900 32 bit (Intel)]
Command to create te pipeline:
az pipelines create --name $serviceName --description 'Pipeline for $serviceName' --org https://dev.azure.com// --project $ProjectName --repository $serviceName --branch master --repository-type tfsgit --yml-path azure-pipelines.yml

Same issue for me, but with different error:


Question: Call async Javascript function from Python

Maybe I'm stupid, but I don't understand how to call an async JS function from Python. For example:
eel.expose(test);
async function test() {
    console.log("Hello world!");
}

This does not work:
eel.test()

Does this example help?
https://github.com/python-eel/Eel/blob/main/examples/03 - sync_callbacks/web/sync_callbacks.html
https://github.com/python-eel/Eel/blob/main/examples/03 - sync_callbacks/sync_callbacks.py

Out of curiosity, can you give a more specific example of when you want to do something like this? I'm struggling to come up with a specific use case I would want to do this.


image size in info box

Is your feature request related to a problem? Please describe.
no knowledge of image size so not able to check which scale image was scaled up at
Describe the solution you'd like
add image size in info box

I pull the image size from the parameters, this might be different from the actual image size, or might be missing. I can pull the actual image size, if that's what you need.
You will probably need to rebuild the database when I push the changes.

Ok, I will rebuild the db now...
metadata rebuilt

Image size is now in info box


Fix automatic dark mode.

Fixes issue #2334
PR Checklist
Please check all that apply to this PR using "x":

[x] I have checked that this PR is not a duplicate of an existing PR (open, closed or merged)
[x] I have checked that this PR does not introduce a breaking change
[ ] This PR introduces breaking changes and I have provided a detailed explanation below

PR Type
What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting)
[ ] Refactoring (no functional changes)
[ ] Documentation changes
[ ] Other - Please describe:

Fixes
Issue Number: #2334
What is the current behavior?
Automatic dark mode can't turn on unless light mode is chosen first.
What is the new behavior?
be able to set that option regardless of the selected theme. If it is selected, it should not allow the theme to be changed.

Welcome back Dan, nice to see you! We'll get a review on this over the next few days. You know the drill with appreciation - shoot us and email once it's merged.

Thanks @tzarebczan :smile:

Welcome back @dan1d !
This is still a little weird since it doesn't switch to light mode if dark mode is selected then you turn on automatic dark mode in the morning. But it should turn on the following day. I think it's still better than what we currently have so I'm going to merge it. Thanks!


Indicate that md5 is not being used for secure purposes—and that's okay (FIPS fix)

Merge this to fix #10184 wherein calls to hashlib.md5 would raise an exception on security-restricted systems (such as FIPS mode systems used in newer U.S. Government computers). MD5 is disabled by default on such systems but a flag may be passed to indicate that it's being used for non-secure reasons (such as fingerprinting).

Thanks @nutjob4life! Merged in 4dea70250bc2923b826676be6b9187a8107b4a20.

Reverted in f6781a29d0f11aa498a3e7f271301aa734f82912 (CI was failing against Python 3.7)

It seems Python 3.7 doesn't include the signature object for md5 to be used with inspect.signature.
Sorry this fell off my radar before the 5.0 feature freeze, so it looks like this'll be in 5.1. Thanks @nutjob4life!


Sample code for a single entry view?

From what I gather, contentful.some_content_type returns an array containing all entries in said content type.  How would I structure the Jade in my single entry view to only grab one entry (say, one blog post) per generation of single entry view though? Currently my template produces (obviously) output containing all posts.
extends _bloglayout

block content
	each post in contentful.blog_posts
		h1= post.title
		!= markdown(post.body)

I'm kind of unsure how else I'd structure it so Roots can iterate through the array on each view generation.  I get the feeling there's something very fundamental I'm missing regarding how roots-contentful does its generation of single entry views.

content_types:
blog_posts:
id: '1fUnrMgZL8WeSu26AYQyOY'
template: 'views/_single.jade'
path: (e) -> "blog/#{slugify(e.title)}"
This will render each blog post to into a HTML file in /blog/My-post.HTML
In your template you do not need to loop through post, but you need to know that each post gets resolved as 'entry'  exp. entry.title

Using entry for my entry data is exactly what I was looking for, chalk that one up to common sense lol.  Thanks for the reply! Closing


chore(dependabot): always increase version requirement to match new version

Description

update dependabot config so that we don't get package-lock version updates without updating the package.json version

How to test

From now on, we should only get PRs from dependabot which update both package.json and package-lock.json

:tada: This PR is included in version 1.203.5 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


fastqc results don't always line up in summary file

If the sample name doesn't match what fastqc and multiqc thinks it should be, then the fastqc results don't get linked to the right sample in the final summary file.
This is annoying.

In principle, what needs to happen is some sort of file or key with the sample and corresponding fastq files that can be used for matching.

vadr results have similar issues (see kitchen sink test to replicate)
nextflow run ~/sandbox/Cecret \
    -profile singularity,artic_V3 \
    --reads /home/eriny/sandbox/test_files/cecret/reads \
    --single-reads /home/eriny/sandbox/test_files/cecret/single-reads \
    --fastas /home/eriny/sandbox/test_files/cecret/fastas \
    --multifastas /home/eriny/sandbox/test_files/cecret/multifasta \
    --outdir kitchen_sink  \
    -with-tower

FastQC results now line up, but there wasn't time to check vadr for 3.6.20230418

Fixed in https://github.com/UPHL-BioNGS/Cecret/pull/157


[chttp2] Fix a bug whereby trailers-only is not reported

We don't report trailers-only if the trailers are parsed prior to executing recv_initial_metadata.
Needed to get #31204 landed

ah I see! Let's write a quick test for this?

I've got a failing test that turns green with this fix in #31204 and we're gonna remove this flag pretty soon, so hesitant to add another test.


Use print() function in both Python 2 and Python 3

**Note: DefectDojo is now on Python3 and Django 2.2. Please submit your pull requests to the 'python3_dev' branch as the 'dev' branch is only for bug fixes. Any PR's submitted to the 'dev' branch should also be converted to Python3 and submited to the 'python3_dev' branch.
When submitting a pull request, please make sure you have completed the following checklist:

[ ] Your code is flake8 compliant
[ ] If this is a new feature and not a bug fix, you've included the proper documentation in the ReadTheDocs documentation folder. https://github.com/DefectDojo/Documentation/tree/master/docs or provide feature documentation in the PR.
[ ] Model changes must include the necessary migrations in the dojo/dd_migrations folder.
[ ] Add applicable tests to the unit tests.

Hi @cclauss, thank you for your PR! We have already converted Dojo to python 3.7 in the dev branch. The current master release is the second to last Python 2.7 release that will exist for Dojo. We have another legacy branch that will be the last 2.7 release once testing is completed on it. We don't accept PRs to the master brach only to dev per our PR template. Hope that all makes sense!


Asset Tag System

Provide some way for assets to be associated with tags, so that the asset manager can retreive all the assets with a particular set of tags. The idea is that a tag marks that an asset is suitable to use in a particular context, and the module that requires an asset can freely substitute in assets, possibly provided by other modules it doesn't even know about, that fulfill its requirements. Perhaps there could also be some tags listed as preferable but inessential as part of the request, so that if any asset matches the preferred tags too, ones that lack them won't be listed.
As an example, consider a module that builds cities using buildings based on StructureTemplates. It could request from the asset system an asset of type Prefab, with the tags StructureTemplates:template, ThemedBuildings:small_temple and OldWestCities:culture_oldwest, and if any module provides a template for an old-west style church, it can just slot that into place in a modular city with that theme. Exactly the same procedure could then be used for other themed cities, just substituting in a different culture tag to get different versions of each type of building.
Of course, this doesn't make sense for all assets. A texture designed for a specific block, for example, doesn't need any tags because it would only be used, by name, for that one block.
Probably most of the use-cases of this would end up being Prefabs. In that case, it would be possible to sort of do something like this already, by retreiving all the Prefabs and looking through for those with particular Components. If this does end up being a separate system in some way, perhaps it could base the tags on the Components of a Prefab rather than having it be completely separate. The intention is sort of similar to the way Components are sometimes used on entities, just for assets instead of entities.

I wrote somewhat of a primitive approach to this ages ago in Portals/Spawning, looks like it was way back in 2012 - wee!
https://github.com/Terasology/Spawning/blob/develop/src/main/java/org/terasology/spawning/SpawnerSystem.java#L90-L120
That was meant to simply take in tags defined in prefabs so a given portal block would spawn creatures matching specific tags, and creatures defined via prefab would define tags they could be spawned by, rather than just by exact asset match. So you could have a portal that spawned anything defining itself as a "goblin" even from assets contributed by other modules with no dependency relationship at all.
Of course supporting this at the asset system level is a vastly more complex and powerful approach, but this made me think of that old code. Eight years, sheesh. Back then I actually wrote code!
A whole other set of examples for this might be related to crafting and materials, although maybe that's a subtly different system of categorization. One simple example would be metal ingots, and variants of ore introduced independently in different modules, yet smelting to the same usable metal.
@SkySom is also looking to write up some possible ideas related to how tags are handled for modded MC :-)


Add note in README/examples that AR are lifesize such that 1 unit == 1m

At least for iOS Quick Look and WebXR

Closed via #154