Wangc/standard error

Pull Request Description
What issue does this change request address? (Use "#" before the issue to link it, i.e., #42.)
close #881, #884
What are the significant changes in functionality due to this change request?
Standard errors on statistics moments are implemented in this change request.

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[ ] 1. Review all computer code.
[ ] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[ ] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[ ] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.
[ ] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True.
[ ] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[ ] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[ ] 8. If an analytic test is changed/added is the the analytic documentation updated/added?

@wangcj05 tests are failing

Job Test OpenSUSE Leap 15 on b3a740d : invalidated by @wangcj05
doc/workshop/codeCoupling/inputs.batemanInterface: -------------------------------------------------- doc/workshop/codeCoupling/inputs.batemanInterface: There were 2 warnings during the simulation run: doc/workshop/codeCoupling/inputs.batemanInterface: (1 time) No pivot parameter provided; defaulting to "time". doc/workshop/codeCoupling/inputs.batemanInterface: (1 time) There were 1 failed runs!  Run with verbosity = debug for more details. doc/workshop/codeCoupling/inputs.batemanInterface: -------------------------------------------------- doc/workshop/codeCoupling/inputs.batemanInterface: /home/civet/.conda/envs/raven_libraries/lib/python2.7/site-packages/statsmodels/compat/pandas.py:56: FutureWarning: The pandas.core.datetools module is deprecated and will be removed in a future version. Please use the pandas.tseries module instead. doc/workshop/codeCoupling/inputs.batemanInterface:   from pandas.core import datetools doc/workshop/codeCoupling/inputs.batemanInterface: *** Error in `python': free(): invalid size: 0x00007f371c00fb70 *** doc/workshop/codeCoupling/inputs.batemanInterface: IOError: There were failed runs; aborting RAVEN. doc/workshop/codeCoupling/inputs.batemanInterface:  doc/workshop/codeCoupling/inputs.batemanInterface: ################################################################################ doc/workshop/codeCoupling/inputs.batemanInterface: Tester failed, reason: CWD /home/civet/civet/build_0/raven/tests/framework/ErrorChecks METHOD opt Expected files not created /home/civet/civet/build_0/raven/doc/workshop/codeCoupling/inputs/exampleTestInterface/outputHistories_dump.csv

@alfoa This PR is ready for your review.

Job Test qsubs on 3f3126d : invalidated by @wangcj05
CIVET: Cancelling job due to step taking longer than the max 21600 seconds

Job Test CentOS 6 on 3f3126d : invalidated by @wangcj05


[BUG] UI fails to deploy when only IPv4 is enabled on nodes

Describe the bug
Longhorn UI does not come up healthy when cluster nodes only support IPv4
To Reproduce
Steps to reproduce the behavior:

Disable IPv6 on nodes
Build RKE cluster
Install Longhorn 1.1.0
See error Address family not supported by protocol in longhorn-ui deployment

Expected behavior
Longhorn UI comes up successfully.
Log
Environment:

Longhorn version: v1.1.0
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version: RKE 1.18

Number of management node in the cluster:
Number of worker node in the cluster

Node config

OS type and version: RHEL 7
CPU per node:
Memory per node:
Disk type(e.g. SSD/NVMe):
Network bandwidth between the nodes:

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal): vSphere

Known workaround exists - providing in edit to this comment

Known workaround exists - providing in edit to this comment

Known workaround provided above, and as mentioned a fix has been put into the UI already. Closing as this was created mainly for future reference.

Known workaround provided above, and as mentioned a fix has been put into the UI already. Closing as this was created mainly for future reference.

The retagged longhornio/longhorn-ui:v1.1.0 should have the fix now.

The retagged longhornio/longhorn-ui:v1.1.0 should have the fix now.


High DPI scaling messes up placement of breakpoint red circles

The breakpoint red circle is drawn between two lines instead of on the relevant line when high DPI scaling is on.
What steps will reproduce the problem?

Use 4K or other high DPI monitor with scaling turned on (may be unnecessary, I don't have an old one to test right now?)
In general preferences, check "Enable high DPI scaling"
Restart Spyder to enable high DPI scaling
Place a breakpoint in a file

What is the expected output? What do you see instead?
The red circle should be nicely centered on the line with the intended breakpoint.  Instead the circle is drawn about half a line high and it is unclear which line it corresponds to.  Further, trying to turn it off often accidentally leads to turning another one on, but offset from the line you intended.
The breakpoint shown below is intended to be on line 8 with the command "pass", but shows up between lines 7 and 8.

Note, that turning off the scaling fixes the alignment, but then you are stuck with really small icons and circles.

Please provide any additional information below
Versions and main components

Spyder Version: 3.1.4.dev0
Python Version: 3.6.1
Qt Version: 5.8.0
PyQt Version: 5.8.1
Operating system: Windows 10

Dependencies
jedi >=0.9.0     :  0.10.0 (OK)
matplotlib >=1.0 :  2.0.0 (OK)
nbconvert >=4.0  :  5.1.1 (OK)
numpy >=1.7      :  1.11.3 (OK)
pandas >=0.13.1  :  0.19.2 (OK)
pep8 >=0.6       :  1.7.0 (OK)
pyflakes >=0.6.0 :  1.5.0 (OK)
pygments >=2.0   :  2.2.0 (OK)
pylint >=0.25    :  1.6.5 (OK)
qtconsole >=4.2.0:  4.2.1 (OK)
rope >=0.9.4     :  0.9.4-1 (OK)
sphinx >=0.6.6   :  1.5.2 (OK)
sympy >=0.7.3    :  1.0 (OK)

As I'm looking at this more, I noticed that it also happens for things like the orange exclamation triangle for code analysis issues.

Thanks for reporting. We'll at this one after we release Spyder 3.2


error in Install

Hello:
When I run commad'conda env create -f RoseTTAFold-linux-cu101.yml' or 'conda env create -f RoseTTAFold-linux.yml', I'm both getting the following error:
Collecting package metadata (repodata.json): done
Solving environment: failed
UnsatisfiableError: The following specifications were found to be incompatible with each other:
Is this my problem with my running environment. How to solve this problem?
Thany you!

Can you provide the conda version and machine info (Ubuntu 20 or Windows etc)?
And can you show the channels info via conda config --show-sources

Machine info is Ubuntu 18.04.2, conda version is 4.7.10. When I run 'conda config --show-sources',it's no message returned.

Machine info is Ubuntu 18.04.2, conda version is 4.7.10. When I run 'conda config --show-sources' ,it's no message returned.

@lll16 There are two possible solutions you can try:
(I have successfully created the conda env using conda env create -f RoseTTAFold-linux.yml in Ubuntu 20.04.2 LTS and conda 4.10.3 with conda channels :
==> /home/zhangjq/.condarc <==
channels:
  - conda-forge
  - https://mirrors.tuna.tsinghua.edu.cn/anaconda/pkgs/main/
  - https://mirrors.tuna.tsinghua.edu.cn/anaconda/pkgs/free/
  - https://mirrors.tuna.tsinghua.edu.cn/anaconda/cloud/bioconda
  - bioconda
  - defaults
always_yes: True

the reason why your command conda config --show-sources shows nothing may be that you haven't configured conda channel info, right?)
S1: config your conda channel
create .condarc file using
conda config

and add some channels (you can copy my channel, but please note that I am in Beijing)
conda config --add channels conda-forge
conda config --add channels xxx

or modify the .condarc file directly
vim /path/to/.condarc

if you do not know where to find .condarc, you can
conda info

S2: update your conda version
conda update conda=4.10.3

One more word, your problem may be conda's issue
https://github.com/conda/conda/issues/9367
hope reproduce conda version and channels can help you

At present, there is no satisfactory solution, the compromise is to use pip to install. (But pip and conda are not completely compatible, sometimes an error will be reported. )

Thanks your suggestion, I'll be trying.

Hello:
When I run commad'conda env create -f RoseTTAFold-linux-cu101.yml' or 'conda env create -f RoseTTAFold-linux.yml', I'm both getting the following error:
Collecting package metadata (repodata.json): done
Solving environment: failed
UnsatisfiableError: The following specifications were found to be incompatible with each other:
Is this my problem with my running environment. How to solve this problem?
Thany you!

Hi all,
In RHEL 7.5, updating conda to 4.10.3 fix the same issue. RosettaFold maintainers, please, add this issue in the installation documentation.


Wagtail 6 compatability?

Just trying this out with Wagtail==6.1.3 and I'm not seeing the UI elements I'd expect:
From the README

Each draft in the history page for any page (/admin/pages//history/) will now have an additional action - Copy external sharing url. Clicking this will generate a random url (and copy it to the clipboard) that can be shared with anyone. The url will display the draft version of the page.

But locally, I don't see that:

I can see that Wagtail 6 isn't formally supported yet -- I'll see if I can add it

Hi @stevejalim support for wagtail 6 wasn't formally added, so it might be the case that some changes are required. If you already have worked on it, a PR would be great, or I could look into it over the weekend.


@conda-forge-admin, please add user @TomAugspurger

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added user @TomAugspurger in conda-forge/azure-core-feedstock#18.


cache github token for up with --repo

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

This change will be in #97, which targets the new release branch, calvinsID:may-11-2022-containerapp-release

Just so you know, actually you could just reuse this same PR and Edit its base branch to a different branch. That way, you won't have to create another identical PR.


Window is not defined after upgrading to v3

Current Behavior
After upgrading to v3 none of my mui datatables pages are working. Here is the error output:
ReferenceError: window is not defined
    at t.value (/node_modules/mui-datatables/dist/index.js:1:95150)
    at processChild (/node_modules/react-dom/cjs/react-dom-server.node.development.js:3134:18)
    at resolve (/node_modules/react-dom/cjs/react-dom-server.node.development.js:2960:5)
    at ReactDOMServerRenderer.render (/node_modules/react-dom/cjs/react-dom-server.node.development.js:3435:22)
    at ReactDOMServerRenderer.read (/node_modules/react-dom/cjs/react-dom-server.node.development.js:3373:29)
    at renderToString (/node_modules/react-dom/cjs/react-dom-server.node.development.js:3988:27)
    at render (/node_modules/next/dist/next-server/server/render.js:3:298)
    at Object.renderPage (/node_modules/next/dist/next-server/server/render.js:46:1020)
    at Function.getInitialProps (webpack-internal:///./node_modules/next/dist/pages/_document.js:133:19)
    at loadGetInitialProps (/node_modules/next/dist/next-server/lib/utils.js:5:101)
    at renderToHTML (/node_modules/next/dist/next-server/server/render.js:46:1330)
    at async /node_modules/next/dist/next-server/server/next-server.js:68:285
    at async /node_modules/next/dist/next-server/server/next-server.js:67:142
    at async DevServer.renderToHTMLWithComponents (/node_modules/next/dist/next-server/server/next-server.js:91:254)
    at async DevServer.renderToHTML (/node_modules/next/dist/next-server/server/next-server.js:92:254)
    at async DevServer.renderToHTML (/node_modules/next/dist/server/next-dev-server.js:22:539)
    at async DevServer.render (/node_modules/next/dist/next-server/server/next-server.js:48:236)
    at async Object.fn (/node_modules/next/dist/next-server/server/next-server.js:35:852)
    at async Router.execute (/node_modules/next/dist/next-server/server/router.js:28:28)
    at async DevServer.run (/node_modules/next/dist/next-server/server/next-server.js:44:494)
    at async DevServer.handleRequest (/node_modules/next/dist/next-server/server/next-server.js:13:133)

Your Environment

Tech
Version

Material-UI
4.10.2

MUI-datatables
3.1.2

React
16.13.1

browser
Firefox/Safari

3.0.1 should work.
I'm assuming you're doing server-side rendering? I created a beta version which I think will resolve the issue. Can you try it out and let me know:
npm install<EMAIL_ADDRESS>If it works I'll publish it as a patch tonight.

3.1.3-beta.0 worked! thank you very much

Sounds good thank you for the report! I'll push version 3.1.3 tonight.

This issue seems to be back, tested in 3.7.8+ on up to latest, related to the same use case of server side rendering.
Any thoughts @patorjk ?
Here's a snippit from the log


Use xcode to solve Mac High Sierra and reduce build times

Changes xcode from 8.0 to 8.3
Enables caching to build faster

closing in favor of #1692


No Errors reported for incompatible object as map

Here's a contrived example of no errors being reported when there is a definite risk of a runtime error:
I have an userStore object that maps userIds to users and an addUser function that should add a user to the dictionary.
If I ignore the existing user store for now and just return an invalid object for the new user I get an error as I expect:
type User = { name: string }
type UserStore = { [string]: User }

function addUser(userStore: UserStore, user: User): UserStore {
  return {
    "someNewId": {}
  };
}
// Error: Cannot return object literal because property `name` is missing in object literal [1] but exists in `User` [2] in property `someNewId`.

However as soon as I splat the existing user store in the object, the error goes away:
function addUser(userStore: UserStore, user: User): UserStore {
  return {
    ...userStore,
    "someNewId": {}
  };
}
// No errors!

If I write my own strongly typed assign function, I can make the error reappear which is good:
function assign<T>(...objs: Array<T>): T {
  return Object.assign({}, ...objs)
}

function addUser(userStore: UserStore, user: User): UserStore {
  return assign(
    userStore,
    {"someNewId": {}},
  );
}
// Cannot return `assign(...)` because property `name` is missing in object literal [1] but exists in `User` [2] in property `someNewId`

But as soon as the key is non-static I lose type safety again:
function addUser(userStore: UserStore, user: User, userId: string): UserStore {
  return assign(
    userStore,
    {[userId]: {}},
  );
}
// No errors!

This problem also goes away when using type Array<User> or Map<string, User> for the user store, but I need dictionary lookup and vanilla JS objects so neither solution sounds right.
So what is the proper way to do this? The only dependable solution I'm able to come up with is write a assignMap method that looks something like this:
function assignMap<T>(state: {[string]: T}, key: string, value: T): {[string]: T} {
  return Object.assign({}, state, {[key]: value})
}

Or is there a way to document a type as a Map for flow but have javascript use a plain object under the hood?

Looks like this problem only exists on version 0.70.0 and 0.71.0. The error correctly appears on versions 0.69.0 and earlier:
https://flow.org/try/#0PQKgBAAgZgNg9gdzCYAoVAXAngBwKZgCqAzngE5gC8YA3mAHYCGAtngFxjEZkCW9A5mAC+mXARLkAyhjhkC1OgG0uvAQF0OEikIDc6VFACu9AMYYecemEYATG1oAUh0mWmz2RF27kAaMM-JNFz8eGw4VPn4ASiCpGTlaVDAwOQxDMisaJOSwADp8gNd4vB9s5IAiUPKOGiFS5N1UEX0gA

Nevermind this seems to be a duplicate of #1971, #2928
Disregard


Code highlighting

With prism.

In anticipation of other transformers, can this be a function that takes context and returns a new context? Would it be helpful to have a pipeline of f(context):context? Like[figureImages, highlightCode, ...]? We can’t call out from the template here, this is just for the page.html. That pipeline could do anything to the context though. Perhaps jsonLd too for example.


⚠ ClamAV has degraded performance

In d33d72b, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 248 ms

Resolved: ClamAV performance has improved in f4a4934.


create k8s secrets for db access

See https://github.com/jungho/openhack-containers/blob/master/src/poi/yaml/deploy-poi.sh

See https://github.com/jungho/openhack-containers/blob/master/src/poi/yaml/deploy-poi.sh


One contributor field, even if blank, should always display

See Design Doc at https://docs.google.com/document/d/1fcr2DYo7OrX-qTdeUOTWKSS1rlq_47sehESmbvgUsrk/edit#heading=h.d3q6bp4xt33j
This states: The first author/contributor added cannot be deleted, but it can be changed. The subsequent authors/contributors will have a trash can in the upper right corner that allows the user to delete them.
Currently the first contributor box has a trash can icon.
If I delete this entry, it looks like this:

If I try to deposit this item, the validation fails as it should because there are no contributors. However, the error doesn't display because the boxes are entirely gone. It looks the same as above. But if I add back in a contributor, you can see it:

@astridu @amyehodge one way to accomplish this is to ensure the remove icon doesn't exist on the first contributor. Would that be an acceptable approach?

That is what @astridu called out in the Design Doc as linked to above, so, yes, that would work for me.

@amyehodge check it: https://github.com/sul-dlss/happy-heron/pull/564#issue-526054290

@mjgiarlo the screenshot looks right to me. Let me know if there is some other way for me to see this, otherwise I'll double-check it once it's available on qa.

@amyehodge it's on QA and stage now.

Checked on qa and this looks good.


[FEA] Add configuration for saving crash "state"

Is your feature request related to a problem? Please describe.
Sometimes the RAPIDS Accelerator crashes when running a particular job in environments where getting logs is a challenge. Spark logs are tremendously verbose and can be useful when debugging in real time, but are not always fully enabled in production environments due to storage demands or performance.
Describe the solution you'd like
It would be nice for when a Spark application crashes when running the plugin, the crash "state" (the exception backtrace, diagnostic information, etc.) should be saved in a configured location to actually be able to get at least an initial sense of what went wrong. This goes towards making the plugin more enterprise-y.  This location can be configured using Spark configuration, and can be either a JSON file containing all of the information needed, or a directory of files that could be useful.

The plugin has spark.rapids.memory.gpu.oomDumpDir for unrecoverable GPU OOM, which is equivalent to calling jmap -dump on the process. I am not sure if that's the crash you are interested in or if there are others?
We log warn all the threads active on the semaphore (the stack traces) when there is a GPU OOM as well. If it's GPU OOM we have some things in place but could probably do more if needed.
On JVM crashes (say when there is a bug in the native side of things and there is a segfault) we normally get an hs_err file with native stack trace and JVM stack trace. This file can be pretty useful to figure out what the executor was doing. There is also XX:OnError to call some command and I see some documentation of folks using it to drop into gdb for example, so perhaps that could be a trigger for more sophisticated actions.
It mostly depends on what the nature of the crash is IMHO.

I think the goal with this is to make a big debug easy button for customers.  We have a lot of ways to dump debug information, but it is not controlled by a single config, and it is especially hard to do if we are in a distributed setup. Perhaps in some cases, like with YARN, we can just have some instructions on how to set specific things to make it simple to send us a crash report when we don't have direct access to a cluster.  But for other environments we might need to think more about how to make this super simple and as consistent as possible between different cluster types.


[BUG] Plugin sometimes breaks holding Ctrl to drag and drop attachment without copying and linking to external file

Description
So far I've been using hold Ctrl + drag-and-drop attachment (picture, etc.) to a note to link to the external attachment instead of creating a local copy of the file, and it was compatible with Custom Attachment Location plugin.
But recently when I did it, it would ignore me holding Ctrl and still create a copy of the attachment, inserting a snippet [[MyFile]] instead of [MyFile](file:///path/to/MyFile).
It doesn't happen 100% of the time but pretty often still, and once it creates a copy of the file you need to delete it, not just Undo the change so it's quite annoying.
Steps to Reproduce

Open Sandbox vault
Install Custom Attachment Location plugin
Drag a file (.md, .png, etc.) into some note, holding Ctrl before release
...

Expected Behavior
It should not copy the file and add en external file:/// URI:

[MyFile](file:///path/to/MyFile)

Actual Behavior
The file has been added to plugin target location (default is ./assets/${filename}) and a snippet [[MyFile]] points to the local copy of the file.
Environment Information

Plugin Version: 4.30.3
Obsidian Version: v1.7.7
Operating System: Ubuntu 22.04 LTS

Attachments

Video

As you can see it doesn't occur 100%: the first time it worked fine, the second time it didn't, although I held Ctrl in both cases
2024-12-17 Obsidian Custom Attachment Location plugin inconsistently honors hold Ctrl drag external link.webm

Sample vault

Not needed, Sandbox vault + plugin installed is fine
Confirmations

[X] I attached a video showing the issue
[X] I attached a sample vault where the issue can be reproduced
[X] I have tested the issue with the latest version
[X] I have checked for existing issues

Fixed in https://github.com/RainCat1998/obsidian-custom-attachment-location/releases/tag/4.31.0

Thanks, it also fixed Ctrl+drag folder not inserting link to directory!


chore: remove explicit parent option

Fixes #1611

Shouldn't we bump this master/packages/opentelemetry-api/src/api/global-utils.ts#L68 to ensure it doesnt cause a problem ?

done

I understand that open telemetry has not v1 yet but changes like that which brake current usage of parent context should be a little bit more discussed and at least explained in docs how I should now create child span if I don't have Context class instance that with appropriate methods on it, only traceId and parentId.

@LukaszKuciel There was quite a discussion there: https://github.com/open-telemetry/opentelemetry-specification/pull/875
Please note the OpenTelemetry Js follows the spec in such topics. There were also a lot discussions about the context concept, what it should be used for,... Just browse/read through the closed issues/PRs in spec repo to get details.
But I agree that we could improve regarding docs.
At least the latest breaking changes are documented in Readme (see https://github.com/open-telemetry/opentelemetry-js#upgrade-guidelines).

@LukaszKuciel There was quite a discussion there: https://github.com/open-telemetry/opentelemetry-specification/pull/875
Please note the OpenTelemetry Js follows the spec in such topics. There were also a lot discussions about the context concept, what it should be used for,... Just browse/read through the closed issues/PRs in spec repo to get details.
But I agree that we could improve regarding docs.
At least the latest breaking changes are documented in Readme (see https://github.com/open-telemetry/opentelemetry-js#upgrade-guidelines).

I spent some time reading throughout issues and PRs, change log, etc.. You're doing great job with whole project I really appreciate it. I'm only afraid based on my experience working with it on a complex event-driven architecture that without documentation it's really really hard and takes a lot of time.
This is a huge problem IMHO when GCP says in Google Trace docs that you should use Open Telemetry as standard instead of their own SDK for this product and then you try but you are groping in the dark.

I am getting TypeError: _api.default.setSpan is not a function any help would be greatly appreciated
import opentelemetry, {context, getSpan } from '@opentelemetry/api';

    const childSpan = tracer.startSpan('doSomeWorkInNewSpan', {
        attributes: { 'code.function' : 'doSomeWorkInNewSpan' }
    });

    opentelemetry.context.with(opentelemetry.setSpan(opentelemetry.context.active(), childSpan), () => {
        console.log('Client traceId ', span.context().traceId);
    });

TypeError: _api.default.setSpan is not a function
    at doSomeWorkInNewSpan (E:\githubRepos\nodejs-opentelemetry-tempo\src\/server.js:44:46)
    at E:\githubRepos\nodejs-opentelemetry-tempo\src\/server.js:33:5
    at Layer.handle [as handle_request] (E:\githubRepos\nodejs-opentelemetry-tempo\node_modules\express\lib\router\layer.js:95:5)
    at next (E:\githubRepos\nodejs-opentelemetry-tempo\node_modules\express\lib\router\route.js:137:13)
    at Route.dispatch (E:\githubRepos\nodejs-opentelemetry-tempo\node_modules\express\lib\router\route.js:112:3)
    at E:\githubRepos\nodejs-opentelemetry-tempo\node_modules\@opentelemetry\plugin-express\build\src\express.js:182:41
    at Layer.handle [as handle_request] (E:\githubRepos\nodejs-opentelemetry-tempo\node_modules\express\lib\router\layer.js:95:5)
    at E:\githubRepos\nodejs-opentelemetry-tempo\node_modules\express\lib\router\index.js:281:22
    at Function.process_params (E:\githubRepos\nodejs-opentelemetry-tempo\node_modules\express\lib\router\index.js:335:12)
    at next (E:\githubRepos\nodejs-opentelemetry-tempo\node_modules\express\lib\router\index.js:275:10)


Run Time issue unicode Charmap

C:\Users\ramak.conda\envs\trade36\lib\site-packages\requests_init_.py:104: RequestsDependencyWarning: urllib3 (1.26.10) or chardet (5.0.0)/charset_normalizer (2.0.12) doesn't match a supported version!
RequestsDependencyWarning)
Traceback (most recent call last):
File "run.py", line 9, in
from jyotisha.rest_api import api_v1
File "C:\Users\ramak.conda\envs\trade36\lib\site-packages\jyotisha-0.1.5-py3.6.egg\jyotisha\rest_api\api_v1.py", line 7, in
from jyotisha.panchaanga.spatio_temporal import City, daily, annual
File "C:\Users\ramak.conda\envs\trade36\lib\site-packages\jyotisha-0.1.5-py3.6.egg\jyotisha\panchaanga\spatio_temporal_init_.py", line 12, in
from jyotisha.panchaanga.temporal.zodiac import Ayanamsha
File "C:\Users\ramak.conda\envs\trade36\lib\site-packages\jyotisha-0.1.5-py3.6.egg\jyotisha\panchaanga\temporal_init_.py", line 6, in
from jyotisha.panchaanga.temporal.festival.rules import RulesCollection, RulesRepo
File "C:\Users\ramak.conda\envs\trade36\lib\site-packages\jyotisha-0.1.5-py3.6.egg\jyotisha\panchaanga\temporal\festival\rules_init_.py", line 15, in
from jyotisha.panchaanga.temporal import names
File "C:\Users\ramak.conda\envs\trade36\lib\site-packages\jyotisha-0.1.5-py3.6.egg\jyotisha\panchaanga\temporal\names_init_.py", line 65, in
NAMES = init_names_auto()
File "C:\Users\ramak.conda\envs\trade36\lib\site-packages\jyotisha-0.1.5-py3.6.egg\jyotisha\panchaanga\temporal\names\init_names_auto.py", line 22, in init_names_auto
names_dict = toml.load(f)
File "C:\Users\ramak.conda\envs\trade36\lib\site-packages\toml\decoder.py", line 156, in load
return loads(f.read(), _dict, decoder)
File "C:\Users\ramak.conda\envs\trade36\lib\encodings\cp1252.py", line 23, in decode
return codecs.charmap_decode(input,self.errors,decoding_table)[0]
UnicodeDecodeError: 'charmap' codec can't decode byte 0x8d in position 44: character maps to ''

undefined

run.py was last run several years ago. Please either fix it, or don't use it (we don't).


ErrorException: file(/var/www/html/app/../resources/lang/de/messages.po): failed to open stream: No such file or directory in /var/www/html/vendor/fisharebest/localization/src/Translation.php:56

Hello ;)
now i have another error. I don't know if i could change something
i used the latest container image.
This exception is displayed in the browser if i tried to open the website
ErrorException: file(/var/www/html/app/../resources/lang/de/messages.po): failed to open stream: No such file or directory in /var/www/html/vendor/fisharebest/localization/src/Translation.php:56
Stack trace:
#0 [internal function]: Fisharebest\Webtrees\Webtrees::Fisharebest\Webtrees\{closure}(2, 'file(/var/www/h...', '/var/www/html/v...', 56, Array)
#1 /var/www/html/vendor/fisharebest/localization/src/Translation.php(56): file('/var/www/html/a...')
#2 /var/www/html/app/I18N.php(306): Fisharebest\Localization\Translation->__construct('/var/www/html/a...')
#3 /var/www/html/app/Http/Middleware/UseLanguage.php(67): Fisharebest\Webtrees\I18N::init('de')
#4 /var/www/html/vendor/oscarotero/middleland/src/Dispatcher.php(136): Fisharebest\Webtrees\Http\Middleware\UseLanguage->process(Object(Nyholm\Psr7\ServerRequest), Object(Middleland\Dispatcher))
#5 /var/www/html/app/Http/Middleware/UseSession.php(71): Middleland\Dispatcher->handle(Object(Nyholm\Psr7\ServerRequest))
#6 /var/www/html/vendor/oscarotero/middleland/src/Dispatcher.php(136): Fisharebest\Webtrees\Http\Middleware\UseSession->process(Object(Nyholm\Psr7\ServerRequest), Object(Middleland\Dispatcher))
#7 /var/www/html/app/Http/Middleware/UpdateDatabaseSchema.php(58): Middleland\Dispatcher->handle(Object(Nyholm\Psr7\ServerRequest))
#8 /var/www/html/vendor/oscarotero/middleland/src/Dispatcher.php(136): Fisharebest\Webtrees\Http\Middleware\UpdateDatabaseSchema->process(Object(Nyholm\Psr7\ServerRequest), Object(Middleland\Dispatcher))
#9 /var/www/html/app/Http/Middleware/UseDebugbar.php(67): Middleland\Dispatcher->handle(Object(Nyholm\Psr7\ServerRequest))
#10 /var/www/html/vendor/oscarotero/middleland/src/Dispatcher.php(136): Fisharebest\Webtrees\Http\Middleware\UseDebugbar->process(Object(Nyholm\Psr7\ServerRequest), Object(Middleland\Dispatcher))
#11 /var/www/html/app/Http/Middleware/UseDatabase.php(117): Middleland\Dispatcher->handle(Object(Nyholm\Psr7\ServerRequest))
#12 /var/www/html/vendor/oscarotero/middleland/src/Dispatcher.php(136): Fisharebest\Webtrees\Http\Middleware\UseDatabase->process(Object(Nyholm\Psr7\ServerRequest), Object(Middleland\Dispatcher))
#13 /var/www/html/app/Http/Middleware/BadBotBlocker.php(212): Middleland\Dispatcher->handle(Object(Nyholm\Psr7\ServerRequest))
#14 /var/www/html/vendor/oscarotero/middleland/src/Dispatcher.php(136): Fisharebest\Webtrees\Http\Middleware\BadBotBlocker->process(Object(Nyholm\Psr7\ServerRequest), Object(Middleland\Dispatcher))
#15 /var/www/html/app/Http/Middleware/RegisterFactories.php(72): Middleland\Dispatcher->handle(Object(Nyholm\Psr7\ServerRequest))
#16 /var/www/html/vendor/oscarotero/middleland/src/Dispatcher.php(136): Fisharebest\Webtrees\Http\Middleware\RegisterFactories->process(Object(Nyholm\Psr7\ServerRequest), Object(Middleland\Dispatcher))
#17 /var/www/html/vendor/middlewares/client-ip/src/ClientIp.php(81): Middleland\Dispatcher->handle(Object(Nyholm\Psr7\ServerRequest))
#18 /var/www/html/app/Http/Middleware/ClientIp.php(47): Middlewares\ClientIp->process(Object(Nyholm\Psr7\ServerRequest), Object(Middleland\Dispatcher))
#19 /var/www/html/vendor/oscarotero/middleland/src/Dispatcher.php(136): Fisharebest\Webtrees\Http\Middleware\ClientIp->process(Object(Nyholm\Psr7\ServerRequest), Object(Middleland\Dispatcher))
#20 /var/www/html/app/Http/Middleware/HandleExceptions.php(90): Middleland\Dispatcher->handle(Object(Nyholm\Psr7\ServerRequest))
#21 /var/www/html/vendor/oscarotero/middleland/src/Dispatcher.php(136): Fisharebest\Webtrees\Http\Middleware\HandleExceptions->process(Object(Nyholm\Psr7\ServerRequest), Object(Middleland\Dispatcher))
#22 /var/www/html/app/Http/Middleware/BaseUrl.php(77): Middleland\Dispatcher->handle(Object(Nyholm\Psr7\ServerRequest))
#23 /var/www/html/vendor/oscarotero/middleland/src/Dispatcher.php(136): Fisharebest\Webtrees\Http\Middleware\BaseUrl->process(Object(Nyholm\Psr7\ServerRequest), Object(Middleland\Dispatcher))
#24 /var/www/html/app/Http/Middleware/ReadConfigIni.php(69): Middleland\Dispatcher->handle(Object(Nyholm\Psr7\ServerRequest))
#25 /var/www/html/vendor/oscarotero/middleland/src/Dispatcher.php(136): Fisharebest\Webtrees\Http\Middleware\ReadConfigIni->process(Object(Nyholm\Psr7\ServerRequest), Object(Middleland\Dispatcher))
#26 /var/www/html/app/Http/Middleware/SecurityHeaders.php(47): Middleland\Dispatcher->handle(Object(Nyholm\Psr7\ServerRequest))
#27 /var/www/html/vendor/oscarotero/middleland/src/Dispatcher.php(136): Fisharebest\Webtrees\Http\Middleware\SecurityHeaders->process(Object(Nyholm\Psr7\ServerRequest), Object(Middleland\Dispatcher))
#28 /var/www/html/app/Http/Middleware/EmitResponse.php(57): Middleland\Dispatcher->handle(Object(Nyholm\Psr7\ServerRequest))
#29 /var/www/html/vendor/oscarotero/middleland/src/Dispatcher.php(136): Fisharebest\Webtrees\Http\Middleware\EmitResponse->process(Object(Nyholm\Psr7\ServerRequest), Object(Middleland\Dispatcher))
#30 /var/www/html/app/Http/Middleware/PhpEnvironment.php(49): Middleland\Dispatcher->handle(Object(Nyholm\Psr7\ServerRequest))
#31 /var/www/html/vendor/oscarotero/middleland/src/Dispatcher.php(136): Fisharebest\Webtrees\Http\Middleware\PhpEnvironment->process(Object(Nyholm\Psr7\ServerRequest), Object(Middleland\Dispatcher))
#32 /var/www/html/vendor/oscarotero/middleland/src/Dispatcher.php(118): Middleland\Dispatcher->handle(Object(Nyholm\Psr7\ServerRequest))
#33 /var/www/html/index.php(57): Middleland\Dispatcher->dispatch(Object(Nyholm\Psr7\ServerRequest))
#34 {main}

Could you please provide the command how you start the container?
Important is which environment variables are set by you.
Do not provide any credentials.
I need this information to analyze the problem further. I am running the container on my own and have not seen this error before.

Yes no problem.
the command is :
docker run -d -p 8088:8079 --name webtrees  -v webtree:/var/www/html/data  -e PORT=8079 -e DB_USER=root -e DB_PASSWORD=***** -e DB_HOST=<IP_ADDRESS> --network=webtree --restart always dtjs48jkt/webtrees
The db host is a latest maria db docker container .
i suppose the bug is dependet on the german language directory?

Ok. I can reproduce this error with Webtrees 2.0.9. Locally I will rollback to 2.0.8 to check if the error was introduced with Webtrees 2.0.9

I found the problem. It should be fixed with Pull Request #28
You should find version v2.0.9-2 in some time on docker hub.
Thank you for your contribution.

Version v2.0.9-2 is available which fixes the problem.


Asynchronous API get Insert Row Id

Hi, how I can get immediately the Row Id after InsertAsync() in the SaveNote() in Main.cs?
I have 2 classes:
Main.cs
	private async void SaveNote() 	{ 		int rowId = await Database.Instance.SaveNoteAsync(note); 	}
Database.cs
public Task<int> SaveNoteAsync(Note note) {     return database.InsertAsync(note); }

You aren't awaiting your InsertAsync method so your operation becomes "FireAndForget". If you want to return a value from a Task, you MUST include await before.
public Task<int> SaveNoteAsync(Note note) {
    return await database.InsertAsync(note);
}


Add a Prowlarr integration

Details
Prowlarr aggregates metrics on the clients it uses and can report hit rates etc. It would be nice to be able to pipe these into prometheus and query with Grafana.

Anything else you would like to add:
For reference https://prowlarr.com

Additional Information:

Duplicate: https://github.com/onedr0p/exportarr/issues/35
Closing

Ah totally missed it, thank you!


add decimal to currency

Issue Reference

Description

How To Test This?

Documentation

[ ] My pull request requires an update on the documentation repository.

@gh-darvishani
Please correct the translation of Decimal

@gh-darvishani Please correct the translation of Decimal

@gh-darvishani any update on this


{{link-to}} "disabledWhen" documentation wrong?

According to the documentation, {{link-to}} should work with a disabledWhen attribute that is evaluated dynamically (as opposed to the "static" disabled attribute). This also used to work in Ember 1.12. However, it doesn't seem to work as advertised: http://ember-twiddle.com/4bcac030ed2c19272271
Changing disabledWhen to disabled seems to work, however, and doesn't seem to be "static" at all (maybe I'm misunderstanding the labels static and dynamic here?).

related? https://github.com/emberjs/ember.js/pull/12344

@jcope2013 is correct, https://github.com/emberjs/ember.js/pull/12344 fixed the issue in the Ember release-1-13 branch. So I'm going to go ahead and close...

sorry, just to follow up: in which release is this fixed? 'cause i'm running ember 1.13.7.

@Fryie add "ember": "#release-1-13" to your bower.json to get it now, it will be included in 1.13.11 but you can get it now by using the release branch

sweet, thanks a lot

just to clarify, though: why does the syntax with "disabled" work, even though it's supposed to be "static" as per the docs? is that also part of the fixed bug?

just to answer my own question, "disabled" only seems to work: it creates the right css class, so the link looks disabled, but it's actually clickable. I'll try updating ember and changing back to "disabledWhen". :)


Issue for request.duration (Server response time degradation)

Rule name: Server response time degradation
When: 2022-04-23T00:00:00.000Z - 2022-04-23T23:59:59.000Z
Detection Id: "2d68bbc1-42e9-d73d-0ae9-2edd1976d60a"
Detection Type: request.duration

Resolved


Autocomplete input field in insert Modal

I would like to have an input text field in my Insert Modal with autocomplete functionality (given a set of values). I don't really want to implement my custom Modal - the perfect solution would be if the file Editor.js had an additional case for type 'autocomplete' or something similar.What I mean by autocomplete is something like this: https://www.w3schools.com/tags/tryit.asp?filename=tryhtml5_datalist
Since I am new to webdevelopment and javascript in general, I wanted to ask advice if it can be done with the current react-bootstrap-table and how. Obviously I don't want to overwrite the original Editor.js file in my node_modules directory and extend it there.
If it is not possible at the moment, could you maybe add such functionality, AllenFang?

Good question and this is need to be enhanced, because developer may only want to custom only one field but now you need to custom the body of insert modal, it's not make sense, so I'll try to support it in near future but not sure whether I can achieve it due to I remember there's some restriction here.
Duplicated issues with https://github.com/AllenFang/react-bootstrap-table/issues/1031#issuecomment-291492624
Let me know if you have any questions, thanks

HI, now we can support the custom only for input field, check this example to learn how to custom it, let me know if you have any questions, thanks 👍
Remember to upgrade to v3.2.0

while i am trying to get table data it is through me this error at the same time this property can be seen in a debugger mode, can someone please help me out why this is happening??
error:

debugger mode:


ModuleNotFoundError when running tests from subfolders

Describe the bug
Running unittest tests from project subfolders is very fragile. It's common to receive the error "ModuleNotFoundError: No module named '[your test module]' when executing.
The following seems to work:

Test modules in the root of the project
Test modules in a subfolder, with the same name as the subfolder

Everything else fails.
Steps to Reproduce

Unzip TestErrors.zip and try to execute tests.

Expected behavior
Test methods are executed.
Additional context and screenshots
    Failed to import test module: tests_foo
    Traceback (most recent call last):
      File "C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python37_64\lib\unittest\loader.py", line 154, in loadTestsFromName
        module = __import__(module_name)
    ModuleNotFoundError: No module named 'tests_foo'

Sample Code
TestErrors.zip
Diagnostics file
Diagnostic Info 2020-03-21T162604.txt

Thank you for the detailed report.
Try adding  init.py in the import and module directories.
Discovery for unittest pattern matches on that https://docs.python.org/3.3/library/unittest.html

Thanks, that fixes everything.
But...until recently I was using VS Code, which does not have this requirement. It also isn't at all obvious thing to do, at least for me; the error mentions the .py file, and in project settings I configured a mask to select which individual .py files to run within the folder.
Do you think you could work around this limitation somehow?

To my experience the problem is still exist.
__init__py
-pp
----innit.py
----person.py
-test_pp
----__init__py
----test_person.py
from pp.person import Person
throws Error:
ModuleNotFoundError: No module named 'pp'

Are you opening the root folder in Vscode?

yes

please attach the logs from the "Python Language Server" output window

´´´
Traceback (most recent call last):
File "/home/pr/gyak/unites/test_pp/test_person.py", line 2, in
from pp.person import Person
ModuleNotFoundError: No module named 'pp'

Oh, sorry, my fault. I was thinking this was VSCode.
you could try adding the pp folder to your search path.

by name, and by subdirectory.name

did you fix/workaround this?

This is old but I was dealing with this issue recently and adding this before importing project modules fixed the issue:
sys.path.append(os.path.dirname(os.path.abspath(__file__)).replace('app/unit_tests',''))
from app import app, db, config # and whatever other module imports

This is for a project that is structured like this:
project_dir/
--app/
--app/__init__py
----unit_tests/


A visible timer is displayed on the screen, counting down the time limit within which players must submit their guesses.

commit: 0ce79ac


Add configuration options for channel settings

Channel name (e.g. change channel XX to say "Fog horn")
Scrambler codes

Currently available for testing at https://mbof.github.io/hx/alpha/.
Doc here: https://github.com/mbof/hxsync/blob/main/yaml.md#channels

URL for testing has changed to: https://mbof.github.io/hx-alpha/

Testing notes:

Prefer the one-line syntax for scrambler code for brevity ({ type: 4, code: 3 })
Maybe ignore unknown channels instead of erroring out. Different channel layouts make cross-device configuration a bit of a pain (e.g. HX890 / HX890E).
The config gets very long, and most users would likely change waypoints / route / DSC directory much more often than channel config. Maybe add a selection dialog to pick which sections of the YAML to load from the radio, instead of loading everything.

More notes. Current configuration is pretty verbose.
Here's a proposal for shorter format
- channels:
    intership: [ 6, 13, 68, 69, 71, 72, 78 ]
    names:
        9: TwoHar-CALLING
        12: Avalon-VTS
        1081: FogHorn-CCG
        88: Scrambl-COMMER
    scrambler:
        88: { type: 4, code: 3 }

Key differences

Quotes not required
Configure only channel group 1 if no other groups are provided
Set up the configuration hierarchy as [ intership, names, scrambler ] -> channel rather than channel -> [ intership, names, scrambler ]

The new format is live for testing at https://mbof.github.io/hx-alpha/


Delta NDS doesn't send InitialResourceVersions, presumably breaking removals on reconnect

InitialResourceVersions is never sent for initial NDS connections. I think this means we will miss any removals that happen during a disconnect

Oh NDS is 1 big resource so this probably doesn't matter


Problem in Nmap2CVE-Search.py

I have this error message :
<urlopen error [Errno 101] Network is unreachable>
Any suggestion?

did you set up a CVE-Search instance or modified the URL to point to a valid instance?

Yes cve-search is setup correctly. I think the adress of CIRCL is not valid any more !!


Remove Export Services for Geneva Release

Related to: https://github.com/edgexfoundry/edgex-go/issues/2218
Signed-off-by: Michael W. Estrin<EMAIL_ADDRESS>

The PR for #295 will be opened after merging this one because there are some conflicts

@michaelestrin please help merge this PR.  Since there is no export-client in nightly build docker-compose file, we need this PR merge first and open another PR for #295
thanks

please help merge this PR. Since there is no export-client in nightly build docker-compose file, we need this PR merge first and open another PR for #295

@cloudxxx8 I don't understand what you're asking me to do.  This is a draft PR that is scheduled to be discussed later today in the Core WG meeting.  I currently don't know if/when this PR (and the others associated with removing the export services from master) will be merged.  You should proceed independently with the work for #295 and we'll just have to deal with the conflicts.

@michaelestrin , ok, we will open the PR for #295 first
@jinlinGuan please open the PR and remove the export client test trigger in your PR


Added documentation for multiple arguments for ToolSettings

New PR (with a clean start) based on the comments from the older one https://github.com/cake-build/cake/pull/1043
This will just add a second example to show how to set multiple arguments on the toolsettings.

Hi @robertmuehsig, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

@robertmuehsig I have merged this here: https://github.com/cake-build/cake/commit/298262727fd591d6959943e2404356ce83d8bf65 to save a rebase.  I have done this since it was simply a change to the documentation.  GitHub doesn't follow what i have done, so I am going to close this PR, but your work will be included.
Thanks again!


Additional metadata in package.json to avoid warnings

Right now, running 'npm install' on the analysis directory gets several warnings because it's missing some fields that installer hopes to see: description, readme, and repository. This pull request adds the missing fields.
(I notice that when I grunted the files, it appears to have deleted a bunch of stuff from analysis/reports/scripts/scripts.js -- is that ok? is it not as dire as it seems?)

Actually, this is fairly dire, as it breaks the reports. Would you mind running Grunt again, checking the analysis/reports/scripts/scripts.js file (that code should not be deleted), and then verifying that the analysis tools still work on your instance?
It's possible that we need to lock down a dependency to an earlier version in the package.json, but let's try this first.
Thanks,
Bret

After wrestling with grunt a bit, I got to not make any changes to the js files -- all that's changed now are a few lines of metadata, the reports work, and I no longer get the missing-metadata warnings on a fresh install.

Hi Ken,
Thanks for modifying this patch. I'm sorry to ask this, but I just pushed some changes to master that include a number of updates to the node modules and dependencies. Would you mind resubmitting this pull request using a new branch that contains those changes? I'm going to close this pull request in the meantime.
Thanks in advance,
Bret


[PROPOSAL] #3 Remove Affiliation of RMC Members from Governance Document

This is a Proposal as per the R-multiverse Governance Document at https://r-multiverse.org/governance.html.
The intention is to edit the Governance Document to remove mention of the affiliations of the RMC members. This is being done so that these can be more easily updated in a timely manner by the members themselves, at other public locations on this site.
Further background is detailed in the issue raised at https://github.com/r-multiverse/help/issues/91.
A PR implementing this is available at: https://github.com/r-multiverse/r-multiverse.github.io/pull/31.
This shall become effective November 12, 2024.

I vote yes

Sounds good to me.

Adopted.


GHA release template

This PR

adds the template for automated tagged releases + PyPI publishing through GitHub Actions
adds clarifying instructions for unittests.yml

gitcount notebook also needs to be updated here

gitcount notebook also needs to be updated here

nice catch.
see also https://github.com/pysal/libpysal/pull/316#issuecomment-655044635

a boilerplate readme with some common formatting, thats templated out for PACKAGENAME or something w/ content designed to be replaced would be useful in here

Would you like to tack that on to this PR or in another?

TO DO

[ ] move Makefile from docsrc/ to docs
[ ] remove docsrc
[ ] remove readthedocs.yml
[ ] add README.md template

TO DO

[ ] move Makefile from docsrc/ to docs
[ ] remove docsrc
[ ] remove readthedocs.yml
[ ] add README.md template

@knaaptime I think this is ready for re-review.

@knaaptime I think this is ready for re-review.

lets merge this. Do we need to add the latest and greatest @jGaboardi ?

Completely forgot about this... Yeah, maybe let go ahead and merge, then we can update later.


Present app to users

Users can download the app and see the prototype

problem connect with clients @robi-y @kob-e


implement firebase-admin db for view counter

implement firebase-admin db for view counter, Please view firebase docs.

Hi Shikhar, I can work on this. Please assign this issue to me.


About 3rd Party Integrations

IMO, 3rd party integrations like flutter_hooks should be optional and be provided via different packages. Otherwise the dependency stack of the core package can be huge and hard to maintain.

totally agree. I will be moving hooks into its own package.
Sent from Outlook Mobilehttps://aka.ms/blhgte

From: necatisozer<EMAIL_ADDRESS>Sent: Saturday, May 2, 2020 8:06:23 PM
To: FilledStacks/stacked<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [FilledStacks/stacked] About 3rd Party Integrations (#19)
IMO, 3rd party integrations like flutter_hookshttps://github.com/rrousselGit/flutter_hooks should be optional and be provided via different packages. Otherwise the dependency stack of the core package can be huge and hard to maintain.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/FilledStacks/stacked/issues/19, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AA3M72R3G5QJGVLZ4HBCXW3RPROJ7ANCNFSM4MXY665Q.

Removed the Flutter Hooks dependency in favor of a separate package

Nice job @FilledStacks. How about keeping all these packages in the same repository like bloc library?

Also not a bad idea. Should be able to do that in about 12 hours after all the other things on my list are done.


NLog.Schema for new csproj file format

Bug
NLog version: 4.4.12
In case of a BUG:

What is the current result?
XSD added to %USERPROFILE%.nuget\packages

What is the expected result?
XSD added to referencing project folder

Are there any work arrounds? yes/no

Is there a version in which it did worked?
https://github.com/NuGet/Home/issues/4803

hi!
Any idea how to fix this?

this is also an issue for nlog.config I guess

A csproj to replace the schema nuspec can help if the xsd is packed into
the contentFiles folder.
I am working on the same issue forthe Syslog target and will let you know
as soon as I validate my solution.

:+1: thanks!

Would be great if I could add this for NLog 4.5 rc2 ;)

You should run dotnet pack --no-build in a folder with a NLog.Schema.csproj file like the following one:
<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <TargetFrameworks>net45;netstandard2.0</TargetFrameworks>

    <Product>NLog.Schema</Product>
    <Copyright>Copyright info</Copyright>

    <Company>Company info</Company>
    <Authors>Authors info</Authors>
    <PackageId>NLog.Schema</PackageId>
    <Title>NLog schema for Intellisense™</Title>
    <Description>Enables Intellisense™ for NLog settings in NLog.config</Description>
    <PackageTags>NLog Log Logging Intellisense xsd</PackageTags>
    <Version>0.1.0-alpha-01-commitHash</Version>
    <PackageLicenseUrl>https://github.com/NLog/NLog/blob/master/LICENSE</PackageLicenseUrl>
    <PackageProjectUrl>https://github.com/NLog/NLog</PackageProjectUrl>
    <PackageIconUrl>http://nlog-project.org/NConfig.png</PackageIconUrl>
    <RepositoryUrl>https://github.com/NLog/NLog</RepositoryUrl>
    <PackageReleaseNotes>https://github.com/NLog/NLog/releases/tag/v0.1.0-alpha-01-commitHash</PackageReleaseNotes>
    <RepositoryType>Git</RepositoryType>
  </PropertyGroup>

  <PropertyGroup>
    <IncludeBuildOutput>false</IncludeBuildOutput>
    <EnableDefaultItems>false</EnableDefaultItems>
  </PropertyGroup>

  <ItemGroup>
    <Content Include="NLog.xsd" Pack="true" PackagePath="$(ContentTargetFolders)" />
  </ItemGroup>
</Project>

FYI the current nuspec https://github.com/NLog/NLog/blob/master/src/NuGet/NLog.Schema/NLog.Schema.nuspec

You should migrate NuSpec tags to the csproj and then remove the NuSpec and only use the csproj with the dotnet CLI