[compatible] Make medium bootstrap sections hard fail

This PR converts the section calls in the medium bootstrap test to section_hard. This ensures that the test will end if any step fails, rather than attempting to continue in a failed state.
This should also stop the test earlier when we hit the hard timeouts, which should reduce the runtime of the test when it's failing.
Checklist:

[ ] Dependency versions are unchanged

Notify Velocity team if dependencies must change in CI

[ ] Modified the current draft of release notes with details on what is completed or incomplete within this project
[ ] Document code purpose, how to use it

Mention expected invariants, implicit constraints

[ ] Tests were added for the new behavior

Document test purpose, significance of failures
Test names should reflect their purpose

[ ] All tests pass (CI will check this if you didn't)
[ ] Serialized types are in stable-versioned modules
[ ] Does this close issues? List them

!ci-build-me

!ci-build-me

!ci-build-me

!ci-nightly-me

Nightly run: https://buildkite.com/o-1-labs-2/mina-end-to-end-nightlies/builds/562

!ci-build-me

!ci-build-me

!ci-build-me

This is already done in berkeley, and no further changes to the compatible branch are planned. Closing.


20.7 fb elisa 7669

Rationale
The ELISA assay is being enhanced to support a new high throughput data format which will introduce some new concepts:

multiple plates per run (similar to the NAb high throughput variants)
multiple values per well, through the use of analytes that could result in up to 4 values per well that need to be tracked separately
multiple standard curves per plate, similar to the sample wells there could be multiple analytes for each plate well

Additionally, some new statistics will be added as detailed in this spec. Run, sample, and result domains were expanded to include new data to be captured as well as to hold some of the new calculations. The ELISA data handler was refactored to handle the legacy and new behavior, this ensures that previous assays and new assays that don't use the new format will continue to work as before.
An experimental flag was put in place to hide the new features until a follow on story to update the run details report is complete.
Related Pull Requests
https://github.com/LabKey/platform/pull/1598
Changes

Add assay provider option to collect both sample and results data from a combined file (assay design selection)
Add run level option to specify the curve fit : 4 & 5 param, linear
Refactor the data handler so it can process both legacy data input as well as the new high throughput format
Add a 16 x 24 plate template which matches the NVITAL plate design
Since linear curve fit is now a standard StatsService option, we need to constrain the NAb run option to not offer the new curve fit (NAbProviderSchema)
Additionally for the ELISA provider schema, don't offer the polynomial fit option
Push new features under an experimental flag

FYI, I just locally tried to upload one of the existing ELISA sampledata files, and I get the following exception on save and finish (with and without the experimental feature enabled):
java.lang.IllegalArgumentException: curveParameters must be an instance of LinearParameters
       at org.labkey.core.statistics.LinearCurveFit.solveForX(LinearCurveFit.java:102)
       at org.labkey.elisa.AbstractElisaImportHelper.createWellRow(AbstractElisaImportHelper.java:66)
       at org.labkey.elisa.ManualImportHelper.createWellRow(ManualImportHelper.java:91)
       at org.labkey.elisa.ElisaDataHandler.getValidationDataMap(ElisaDataHandler.java:163)
       at org.labkey.api.assay.AbstractAssayTsvDataHandler.importFile(AbstractAssayTsvDataHandler.java:124)

FYI, I just locally tried to upload one of the existing ELISA sampledata files, and I get the following exception on save and finish (with and without the experimental feature enabled):
java.lang.IllegalArgumentException: curveParameters must be an instance of LinearParameters
       at org.labkey.core.statistics.LinearCurveFit.solveForX(LinearCurveFit.java:102)
       at org.labkey.elisa.AbstractElisaImportHelper.createWellRow(AbstractElisaImportHelper.java:66)
       at org.labkey.elisa.ManualImportHelper.createWellRow(ManualImportHelper.java:91)
       at org.labkey.elisa.ElisaDataHandler.getValidationDataMap(ElisaDataHandler.java:163)
       at org.labkey.api.assay.AbstractAssayTsvDataHandler.importFile(AbstractAssayTsvDataHandler.java:124)

Update: when I re-imported the run and gave it more meaningful concentration values (i.e. 100 down to 0) instead of just setting all concentration values to 1, then the run uploaded successfully. So likely this means just a check is needed somewhere in the code when the concentration values are not descending (or something along those lines).

It probably means the standard concentrations couldn't be fit to a curve, I'll add a check for that.


Crowdsourced images

cd rl_loop
python
import shipname
print('\n'.join(["google-chrome https://www.google.com/search?q=british+ship+%s &" % n for n in shipname.NAMES]))

copy and paste the first set to a new terminal
(This should open a google search tab for each one
function photo { echo "$2" > $1.meta; curl "$3" > $1.jpg; }

mkdir -p photos; cd photos
photo <NAME> <wikipedia image page> <wikipedia image url>

i.e.
photo warspite "https://en.wikipedia.org/wiki/HMS_Warspite_(1666)#/media/File:HMS_Edinburgh-IMG_7758.jpg" "https://upload.wikimedia.org/wikipedia/commons/8/89/HMS_Edinburgh-IMG_7758.jpg"

Many of the name represent multiple ships (WWI, WWII, older ships, ...) feel free to choose any one of them (I like models from museums but choose as you please.
I'm working alphabetically backwards. If someone (cough Andrew cough) wanted to work forwards that would be nice.

ok, what do you want me to do with these that i've got?

If you could zip them and send them to me (here, my email, or a gs link) that would be the easiest

ace to formidable is done,
pallas to zephyr is done.

Missing two in the magnanime to otter range

Remaining
google-chrome https://www.google.com/search?q=british+ship+ace &
google-chrome https://www.google.com/search?q=british+ship+alaric &
google-chrome https://www.google.com/search?q=british+ship+alkmaar &
google-chrome https://www.google.com/search?q=british+ship+anchorite &
google-chrome https://www.google.com/search?q=british+ship+arachne &
google-chrome https://www.google.com/search?q=british+ship+artemis &
google-chrome https://www.google.com/search?q=british+ship+cato &
google-chrome https://www.google.com/search?q=british+ship+clove-tree &
google-chrome https://www.google.com/search?q=british+ship+constant-warwick &
google-chrome https://www.google.com/search?q=british+ship+content &
google-chrome https://www.google.com/search?q=british+ship+crown &
google-chrome https://www.google.com/search?q=british+ship+defiance &
google-chrome https://www.google.com/search?q=british+ship+expedition &
google-chrome https://www.google.com/search?q=british+ship+golden-horse &
google-chrome https://www.google.com/search?q=british+ship+grief &
google-chrome https://www.google.com/search?q=british+ship+hazardous &
google-chrome https://www.google.com/search?q=british+ship+heron &
google-chrome https://www.google.com/search?q=british+ship+hydra &
google-chrome https://www.google.com/search?q=british+ship+icarus &
google-chrome https://www.google.com/search?q=british+ship+illustrious &
google-chrome https://www.google.com/search?q=british+ship+implacable &
google-chrome https://www.google.com/search?q=british+ship+impregnable &
google-chrome https://www.google.com/search?q=british+ship+indefatigable &
google-chrome https://www.google.com/search?q=british+ship+indus &
google-chrome https://www.google.com/search?q=british+ship+inflexible &
google-chrome https://www.google.com/search?q=british+ship+intrepid &
google-chrome https://www.google.com/search?q=british+ship+invincible &
google-chrome https://www.google.com/search?q=british+ship+irresistible &
google-chrome https://www.google.com/search?q=british+ship+isis &
google-chrome https://www.google.com/search?q=british+ship+jupiter &
google-chrome https://www.google.com/search?q=british+ship+juste &
google-chrome https://www.google.com/search?q=british+ship+kent &
google-chrome https://www.google.com/search?q=british+ship+kingfisher &
google-chrome https://www.google.com/search?q=british+ship+kite &
google-chrome https://www.google.com/search?q=british+ship+leander &
google-chrome https://www.google.com/search?q=british+ship+leopard &
google-chrome https://www.google.com/search?q=british+ship+leviathan &
google-chrome https://www.google.com/search?q=british+ship+lightning &
google-chrome https://www.google.com/search?q=british+ship+lincoln &
google-chrome https://www.google.com/search?q=british+ship+lion &
google-chrome https://www.google.com/search?q=british+ship+lively &
google-chrome https://www.google.com/search?q=british+ship+lynx &
google-chrome https://www.google.com/search?q=british+ship+moderate &
google-chrome https://www.google.com/search?q=british+ship+olympus &
google-chrome https://www.google.com/search?q=british+ship+orestes &
google-chrome https://www.google.com/search?q=british+ship+parthian &
google-chrome https://www.google.com/search?q=british+ship+portia &
google-chrome https://www.google.com/search?q=british+ship+prospero &
google-chrome https://www.google.com/search?q=british+ship+redoubtable &
google-chrome https://www.google.com/search?q=british+ship+renown &
google-chrome https://www.google.com/search?q=british+ship+robust &
google-chrome https://www.google.com/search?q=british+ship+san-josef &
google-chrome https://www.google.com/search?q=british+ship+san-nicolas &
google-chrome https://www.google.com/search?q=british+ship+sapphire &
google-chrome https://www.google.com/search?q=british+ship+two-lions &
google-chrome https://www.google.com/search?q=british+ship+unity &
google-chrome https://www.google.com/search?q=british+ship+valiant &


Ambiguity Between Implicit Multiplication and Function Calls

Since func(...) and func (...) are treated equivalently, the expression x (...) is interpreted as a function call (x called with (...)) rather than implicit multiplication. Due to this ambiguity, I have temporarily removed this test case (and improved the description) until the behavior can be clarified or adjusted.
Reference: #2 Manual std::hash::Hash implementation for consistency with PartialEq

I didn't even realize that was possible! Thank you for discovering this.
The best solution I can think of is to make func(...) always be a function call, and make func (...) (with a space) always be implicit multiplication. It'll be easy to implement and makes the behavior consistent and easily documentable, and it allows implicit multiplication to stay, although it forces a particular style on developers who prefer func (...) for their function calls.
There are some other interesting ideas:

Make func(...) or func (...) always be function calls, and limit implicit multiplication to "unambiguous" expressions, like 3(x + 4), or (x + 4)3. This appears to be the current behavior.
Make func(...) or func (...) always be implicit multiplication, and add some other syntax for function calls, like func.call(...). Consistent, but somewha tdifficult to implement, and might be confusing to programmers.
Parse func(...) as an ambigious expression. At runtime, check to see if func is indeed pointing to a function and call it if it is; otherwise, treat it as implicit multiplication. Hard to implement and has the potential to be highly confusing!
Remove implicit multiplication or function calls entirely. Hopefully we won't have to 😅

3 is the best solution, but it'll be a bit of work. But, doable nonetheless else we would fall back to 1.
2 and 4 are a big no-no in my opinion.

To me, it seems like the detriments of solution 3 outweigh the benefits. It would certainly be highly flexible, but it becomes more difficult to look at CalcScript code and know whether a function will be called or not. In addition, by moving the check from compile-time to runtime, we might lose the ability to catch particular errors early on, and performance would suffer slightly. (In the future, I want to make CalcScript compile into bytecode instead of using a tree-walking interpreter, which would be faster and easier to debug, see the dev branch!)
My initial idea aims to also be as flexible as solution 3, but with the benefit of being able to unambiguously determine the behavior of func() or func () at compile-time, and avoiding the other issues that solution 3 brings. Forcing a style on the developer may be a bit annoying, but it may be worth it for flexibility and consistency.
However, I am open to other ideas or suggestions. If you have other reasons to prefer solution 3, I'd be happy to hear them!


Lite Mode?

I absolutely love this mod; it allows for a single (yet complex) piping system, turning Medusa's hair into a single pipeline. However, I feel the mod adds too much. I like using buildcraft/ industrialcraft/ Thermal Expansion, which add their own ores/processing, and I really would prefer an Ender IO download that gave only it's piping features. I understand this would require a rework of the recepies, but I feel a "Lite" version would be much easier to use with other tech mods.

EnderIO offers a lot more than just conduits - and you have to use the Alloy Smelter to make the alloys for the conduits.
If you don't want to use the rest of the mod - that's up to you.

That's exactly what I mean though, Ender IO has a lot to offer that other mods offer as well. A "lite" version with simpler crafting recipes without the need for another power source and machine would blend in so much more when used with other tech mods.

i dont really see the point to that, every mod has their own way of machines, i dont see why you would need to make a lite version of this, its a tremendous amount of work, all recipes would have to be changed.
You can literally just use the parts of the mod you want

the way this can be done is split up the alloys to it's own mod and make it required (core) then conduits, upgrade items for conduits and filters in another  and last the machines and other blocks in the last mod. the alloys can be made into blends by combining the items used now to make a dust of that alloy then smelt them in any furnace. this feature can be turned on and off in the configs to make it require the alloy smelter to make the alloys or the blend crafting recipe.
names suggestion for the mod split
EnderIO-Core (alloy recipes and api) *required by the other two
EnderIO-Conduits (conduits and items needed for them)
EnderIO-Machines (All machines, capacitor banks, capacitor items and xp related blocks)


add[resource card]:master dataviz file direct download

Closes https://github.com/carbon-design-system/carbon-website/issues/1563

[x] Updated Chart anatomy images (desktop and mobile) with new zoom bar and tooltip
[x] Added master data vis design file direct download resource card to data viz > getting started page
[x] Added master data vis design file direct download resource card to resources page
[x] Fixed incorrect donut chart guidance on legend page
[x] Updated some palettes on legend page that didn't correspond with our docs

🎉  🎉  You did it! this is great

@aagonzales what do you think. If we leave it in box I should add (IBM Internal link) like the other one.

Yeah I think adding that label would suffice for now.

@aagonzales what do you think. If we leave it in box I should add (IBM Internal link) like the other one.

does Box do version control? git might be better

What’s stopping us from going live on github right now? Is there a process?
Let’s put this in the hands of everyone rather than just an internal link
On Fri, Aug 14, 2020 at 2:05 PM Anna Gonzales<EMAIL_ADDRESS>wrote:

@aagonzales approved this pull request.
Yes, box has version control. Its not as prominent as a github source
control but it will save versions if you "upload new version" of a file. It
would be more for the sake of maintainer ship than for users to select
which version they want.
[image: image]
https://user-images.githubusercontent.com/11670886/90279435-d57fb600-de2e-11ea-9825-5c60ee04e2e5.png
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/carbon-design-system/carbon-website/pull/1565#pullrequestreview-467770446,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADSLT3DJIIRAIZVWMEDRKRTSAV4HZANCNFSM4P5VVAVA
.


Slow performance when calling getMap().then(function(){}); but not getMap();

I'm tracking down a performance critter. I use $interval to constantly center the map. Seems that getMap().then(function() {}) causes a performance hit while getMap() does not. The code is below.
function centerOnTrip(data, mapName) {
      if(!data) {
        return;
      };
      leafletData.getMap(mapName).then(function doCenter(map) {
        console.timeEnd('get map');
      });
}

This issue was moved to angular-ui/ui-leaflet#167

I'm going to rework&redesign angular-leaflet-directive to be compatible with Leaflet v1.0. It will mantain almost all its functionality, and will be compatible with the current features of the directive, but I must start from a fresh point, so I'm going to close this issue. If you think it must be worked with the new version, please reopen it.


Add support to add Ejabberd license file install via Metro

Add support to add Ejabberd license file install via Metro

Ready for review again

Added HA support ready for review again


[FLINK-20342][docs] Restructuring of Deployment & Operations documentation pages

In order to see the new structure, please take a look at the screenshot.

This PR also moves the configuration of the metrics reporters to Deployment/Metrics Reporters as it is a concern of the deployment.
cc @rmetzger

What about splitting up the Configuration page into subpages as it is quite long already. This way we could also make the Memory Configuration a subpage of Configuration

This change is already quite big. I would do such changes in follow up PRs. Ideally this change only focuses on the structure, individual pages should be updated separately.
(As a side note: I'm not convinced that splitting the Configuration page is a good idea, because then you can not search the page for config keys anymore (with CTRL+F))

Rendering of the change somehow fails locally, any ideas?
Configuration file: /Users/robert/Projects/flink/docs/_config.yml
            Source: /Users/robert/Projects/flink/docs
       Destination: /Users/robert/Projects/flink/docs/content
 Incremental build: disabled. Enable with --incremental
      Generating...
Is a directory @ io_fillbuf - fd:7 /Users/robert/Projects/flink/docs/deployment/memory
/Users/robert/Projects/flink/docs/.rubydeps/ruby/2.5.0/gems/jekyll-4.0.1/lib/jekyll/utils.rb:141:in `readline'
/Users/robert/Projects/flink/docs/.rubydeps/ruby/2.5.0/gems/jekyll-4.0.1/lib/jekyll/utils.rb:141:in `open'
/Users/robert/Projects/flink/docs/.rubydeps/ruby/2.5.0/gems/jekyll-4.0.1/lib/jekyll/utils.rb:141:in `has_yaml_header?'
/Users/robert/Projects/flink/docs/.rubydeps/ruby/2.5.0/gems/jekyll-4.0.1/lib/jekyll/reader.rb:52:in `block in read_directories'
/Users/robert/Projects/flink/docs/.rubydeps/ruby/2.5.0/gems/jekyll-4.0.1/lib/jekyll/reader.rb:48:in `each'
/Users/robert/Projects/flink/docs/.rubydeps/ruby/2.5.0/gems/jekyll-4.0.1/lib/jekyll/reader.rb:48:in `read_directories'
/Users/robert/Projects/flink/docs/.rubydeps/ruby/2.5.0/gems/jekyll-4.0.1/lib/jekyll/reader.rb:89:in `block in retrieve_dirs'
/Users/robert/Projects/flink/docs/.rubydeps/ruby/2.5.0/gems/jekyll-4.0.1/lib/jekyll/reader.rb:86:in `each'
/Users/robert/Projects/flink/docs/.rubydeps/ruby/2.5.0/gems/jekyll-4.0.1/lib/jekyll/reader.rb:86:in `retrieve_dirs'
/Users/robert/Projects/flink/docs/.rubydeps/ruby/2.5.0/gems/jekyll-4.0.1/lib/jekyll/reader.rb:60:in `read_directories'
/Users/robert/Projects/flink/docs/.rubydeps/ruby/2.5.0/gems/jekyll-4.0.1/lib/jekyll/reader.rb:16:in `read'
/Users/robert/Projects/flink/docs/.rubydeps/ruby/2.5.0/gems/jekyll-4.0.1/lib/jekyll/site.rb:174:in `read'
/Users/robert/Projects/flink/docs/.rubydeps/ruby/2.5.0/gems/jekyll-multiple-languages-2.0.3/lib/jekyll-multiple-languages/site.rb:19:in `read'
/Users/robert/Projects/flink/docs/.rubydeps/ruby/2.5.0/gems/jekyll-4.0.1/lib/jekyll/site.rb:74:in `process'
/Users/robert/Projects/flink/docs/.rubydeps/ruby/2.5.0/gems/jekyll-multiple-languages-2.0.3/lib/jekyll-multiple-languages/site.rb:11:in `process'
/Users/robert/Projects/flink/docs/.rubydeps/ruby/2.5.0/gems/jekyll-4.0.1/lib/jekyll/command.rb:28:in `process_site'
/Users/robert/Projects/flink/docs/.rubydeps/ruby/2.5.0/gems/jekyll-4.0.1/lib/jekyll/commands/build.rb:65:in `build'
/Users/robert/Projects/flink/docs/.rubydeps/ruby/2.5.0/gems/jekyll-4.0.1/lib/jekyll/commands/build.rb:36:in `process'
/Users/robert/Projects/flink/docs/.rubydeps/ruby/2.5.0/gems/jekyll-4.0.1/lib/jekyll/command.rb:89:in `block in process_with_graceful_fail'
/Users/robert/Projects/flink/docs/.rubydeps/ruby/2.5.0/gems/jekyll-4.0.1/lib/jekyll/command.rb:89:in `each'
/Users/robert/Projects/flink/docs/.rubydeps/ruby/2.5.0/gems/jekyll-4.0.1/lib/jekyll/command.rb:89:in `process_with_graceful_fail'
/Users/robert/Projects/flink/docs/.rubydeps/ruby/2.5.0/gems/jekyll-4.0.1/lib/jekyll/commands/serve.rb:86:in `block (2 levels) in init_with_program'
/Users/robert/Projects/flink/docs/.rubydeps/ruby/2.5.0/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `block in execute'
/Users/robert/Projects/flink/docs/.rubydeps/ruby/2.5.0/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `each'
/Users/robert/Projects/flink/docs/.rubydeps/ruby/2.5.0/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `execute'
/Users/robert/Projects/flink/docs/.rubydeps/ruby/2.5.0/gems/mercenary-0.3.6/lib/mercenary/program.rb:42:in `go'
/Users/robert/Projects/flink/docs/.rubydeps/ruby/2.5.0/gems/mercenary-0.3.6/lib/mercenary.rb:19:in `program'
/Users/robert/Projects/flink/docs/.rubydeps/ruby/2.5.0/gems/jekyll-4.0.1/exe/jekyll:15:in `<top (required)>'
/Users/robert/Projects/flink/docs/.rubydeps/ruby/2.5.0/bin/jekyll:23:in `load'
/Users/robert/Projects/flink/docs/.rubydeps/ruby/2.5.0/bin/jekyll:23:in `<top (required)>'
/usr/local/share/gems/gems/bundler-1.16.1/lib/bundler/cli/exec.rb:75:in `load'
/usr/local/share/gems/gems/bundler-1.16.1/lib/bundler/cli/exec.rb:75:in `kernel_load'
/usr/local/share/gems/gems/bundler-1.16.1/lib/bundler/cli/exec.rb:28:in `run'
/usr/local/share/gems/gems/bundler-1.16.1/lib/bundler/cli.rb:424:in `exec'
/usr/local/share/gems/gems/bundler-1.16.1/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
/usr/local/share/gems/gems/bundler-1.16.1/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command'
/usr/local/share/gems/gems/bundler-1.16.1/lib/bundler/vendor/thor/lib/thor.rb:387:in `dispatch'
/usr/local/share/gems/gems/bundler-1.16.1/lib/bundler/cli.rb:27:in `dispatch'
/usr/local/share/gems/gems/bundler-1.16.1/lib/bundler/vendor/thor/lib/thor/base.rb:466:in `start'
/usr/local/share/gems/gems/bundler-1.16.1/lib/bundler/cli.rb:18:in `start'
/usr/local/share/gems/gems/bundler-1.16.1/exe/bundle:30:in `block in <top (required)>'
/usr/local/share/gems/gems/bundler-1.16.1/lib/bundler/friendly_errors.rb:122:in `with_friendly_errors'
/usr/local/share/gems/gems/bundler-1.16.1/exe/bundle:22:in `<top (required)>'
/usr/local/bin/bundle:23:in `load'
/usr/local/bin/bundle:23:in `<main>'                    done in 0.396 seconds.

From the stacktrace, it seems to be related to the multiple languages? or the has_yaml_header? maybe some header is wrong somewhere?

Hmm, locally it builds for me. But let me check whether I can find the problem.
Concerning the redirect links, I have also thought about it. We can definitely do it but it will probably only be a best effort. Moreover, if you link to the latest documentation, then you shouldn't expect that all links stay forever the same. Maybe we should stop using https://ci.apache.org/projects/flink/flink-docs-stable/ as the URL for the latest docs and instead use an explicit URL like https://ci.apache.org/projects/flink/flink-docs-release-1.10/ to avoid this problem in the future.

Are you building the docs in docker, or directly in your OS? (I'm using docker)
I would only do the redirect if jekyll supports wildcards, and I would just redirect to the Deployment Overview page.

I am building the documents locally. One difference I've noticed is that I have Ruby 2.7.0 locally. But I guess I should use Docker for reproducibility.

Docker also works for me @rmetzger.

Thanks a lot for testing it with Docker as well. It was indeed a local issue. Sorry for the trouble.

Did you intentionally move the "Configuration" and "Memory Configuration" so low in the "Deployment" section. Maybe we can put it after "Resource Providers"?

Please remember to run the check_links.sh script before merging.
Due to recent events, I don't trust my local setup anymore, but
≻ ./check_links.sh
http://localhost:3000/d/FOe0PbmGk/walkthrough?viewPanel=2&orgId=1&refresh=5s:
Remote file does not exist -- broken link!!!
--
http://localhost:8081/:
Remote file does not exist -- broken link!!!
--
http://localhost:4000/deployment/resource-providers/kubernetes.html:
Remote file does not exist -- broken link!!!
--
http://localhost:4000/zh/deployment/resource-providers/kubernetes.html:
Remote file does not exist -- broken link!!!
---------------------------------------------------------------------------
Found 4 broken links.
Search for page containing broken link using 'grep -R BROKEN_PATH DOCS_DIR'

Didn't we want to address YARN HA as well? It's missing in the subsection list of HA Services.
And from a stylistic point of view: IMHO, we could remove "HA Services" from "Kubernetes HA Services" and "Zookeeper HA Services" as it's obsolete considering that those are subsections of "High Availability (HA)".

This change is already quite big. I would do such changes in follow up PRs. Ideally this change only focuses on the structure, individual pages should be updated separately.
(As a side note: I'm not convinced that splitting the Configuration page is a good idea, because then you can not search the page for config keys anymore (with CTRL+F))

Searching the Configuration page is a good point. I haven't thought about that 👍

Yes, I agree let's remove the "HA Services" part as it is redundant.
The entries under "HA Services" are the supported HA services implementations (ZooKeeper and K8s). Hence, I think we shouldn't mention Yarn here. Instead, the Yarn resource provider page should have a subsection HA where we say what you need to configure in order to support AM restarts on Yarn which is required (next to ZooKeeper HA services) to enable master failover.

@XComp did you expect that High Availability (HA) -> Kubernetes HA Services explains how to setup HA on K8s? The idea is that this page contains explanations about the K8s HA service and how to activate it in the configuration. It won't explain which deployment yaml to change, though. If this is the case, then removing the "HA Services" might even be more misleading.

I actually wanted to put the Configuration page at the bottom because I thought it would make sense to close the deployment section with it (in some sense, at the end you find an overview over all configuration settings we have talked about). Given the current state where it is in the lower quarter, I guess it would make sense to move it a bit up. Will change it.


How to auto-redirect non-ssl to ssl?

Hi,
after rcssl installed certs, how to auto-redirect non-ssl traffic to ssl version?

If you on wordpress use Really Simple SSL plugin and activate

If you on wordpress use Really Simple SSL plugin and activate

Thanks for your reply. I think there should be a solution at server level so that it works for all kinds of app

If you're using hybrid apache/nginx, add these lines to your .htaccess
RewriteCond %{HTTP:X-Forwarded-Proto} !=https
RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R=302,L]


Extending anvil

Is possibile a tutorial to extend Anvil with custom views (like Anko)???

@FunnyDevs it is possible to extend Anvil with custom views, although maybe not like with Anko.

You can always build "components", self-contained ViewGroups (extended from RenderableView).
You can always mounts custom views into existing renderables, like v(MyCustomView.class, () -> {...}).
You can now create your own Anvil.ViewFactory implementations, register them, and then use them to build custom classes on demand (e.g. if you class constructor is now just View(Context), but something more complex, like using styles etc.

Starting with Anvil 0.5.0 (just released it today) you may set custom attributes as well, just do attr("myAttr", someValue) and that will call setMyAttr(someValue) on your view if fthe value has been changed since the last call. In the worst case that will use reflection, but you may also register your own Anvil.AttributeSetter to handle your custom attributes and speed up things.

i would like to do like Anko that maps custom function (like toast(), dialog()), but with custom view:
customview()
Must i do a custom Anvil.ViewFactory???
Is there a changelog of new release???
Thanks


Currency Field summing to $0

IMPORTANT NOTE The Chatter Community Group can be found here. If it is an issue that you need help on configuring the tool or have an unexpected error its really worth seeing if the community can help first before raising a GitHub issue. Most users hangout in the Chatter Community Group. Otherwise if prefer you can post here and still link in the Chatter Community Group.
Wondering if anyone has had a similar issue with DLRS, I did a search and did not find anything similar.
I have a Custom Object Payments with a "Payment Amount" currency field. I am rolling this filed on to a related Object, Batch on a Currency Field called "Entered Amount". The Sum always returns $0, I manually updated the "Entered Amount" filed to $20 but DLRS reverted it back to $0.

@afawcett can you help me identify this ghost?

@BelmarSid, I'm not sure what is going on with this one.
Is the "$0" being set when you update the parent or child records? In theory DLRS runs when you update the child record, if you're manually setting the value and it is immediately set to "$0" then I'd look at other automation that might be involved.
If you can capture a debug log during the execution that might help us understand what is happening.
https://help.salesforce.com/s/articleView?id=sf.code_add_users_debug_log.htm&type=5


Added pptx extension to ignore file so that all PowerPoint presentati…

…ons don't get uploaded on GitHub.

Thanks


Incorrect title for Bitwarden icon in README.md

The title of the Bitwarden icon in README.md is currently "imgur" it should be "Bitwarden"
Fix in #713

Closed in #713


B2 init repo doesn´t work / hangs

Got an Issue when trying to initalize an repo on B2. I got the keys from the web-interface of b2.
If i try to run the commands below, simply nothing happens, for at least 10minutes.
The --verbose argument doesnt give any additional info.
I can init a local repo with restic without a problem.
If i use the b2 cli tool i can successfully authenticate and upload files to my bucket.
So i think this is not an issue based on too less rights of the executable or a firewall (i dont have one).
I tried to run older versions (0.81 x64, 0.83 x64 / 386 ) resulting to the same issue.
Output of restic version
restic 0.9.1 compiled with go1.10.3 on linux/amd64
Ubuntu 16.04
How did you run restic exactly?
export B2_ACCOUNT_ID=xxx
export B2_ACCOUNT_KEY=xxx (Master App Key)
chmod 777 restic_0.9.1_linux_amd64
./restic_0.9.1_linux_amd64 -r b2:bucketName init
What backend/server/service did you use to store the repository?
b2
Expected behavior
init repo
Actual behavior
nothing happens
Steps to reproduce the behavior
run the commands
Do you have any idea what may have caused this?
maybe restic executable got too less rights , gets blocked somewhere?

So, to clarify, you hit "Enter" to run the command and then it just sits there, nothing to stdout, stderr, or any other activity? Any network activity going on?

has been resolved, thx!

What was the solution?

Not related to restic. It was a typo in my credentials.

Thanks for the feedback! We're always interested in what the solution was :)

But the thing is: there was no error reply in restic on that issue. It simply hang without any output.
Duplicati at least returned the b2 errormsg "ERROR 500 internal_error Unexpected exception".
Maybe some error handling in restic would receive that b2-message and print it, as i was really confused that simply nothing was replied.

Hm, that's odd. I agree that an error message should be printed...
I'm unable to reproduce it here... what was the typo? any hints on how to reproduce it?
For the record, changing the last character of my key and running restic gives me:
$ restic init
Fatal: create repository at b2:bucket:/path failed: b2.NewClient: b2_authorize_account: 401: Invalid authorization

@kurin can you have a look? Is there anything we should do from restic's side?

Reopening for now.

It was a typo in my account id.

Yeah, that's a change Backblaze implemented just a few days ago, and other keys than the Master Application Keys are not supported yet (but we're working on that). We need to update the docs also then.

ahh, okey that explains my confusion.

Sorry about that, I've just tested the master branch of the blazer library and it's working with restricted application keys now, so @kurin hopefully tags a release the next couple of days and then we can update restic and fully support the new keys :)


Editor settings are not saving in my account.

If I log out and then log back in all settings are reset.

well then don't log out.

Confirmed. Can you both comment here with your username?


Internal methods names shouldn't be allowed as control names

Also: The editor currently accepts sending a control name starting with __UI_, when it shouldn't, and it wrecks havoc, as expected.

Partially fixed by c4f91eaab5573a345dbcf98785d1063d28ec5d30


proc: support inlining

proc: support inlining

Go 1.10 added inlined calls to debug_info, this commit adds support
for DW_TAG_inlined_call to delve, both for stack traces (where
inlined calls will appear as normal stack frames) and to correct
the behavior of next, step and stepout.

# Changes to stack traces

The calls to Next and Frame of stackIterator continue to work
unchanged and only return real stack frames, after reading each line
appendInlinedCalls is called to unpacked all the inlined calls that
involve the current PC.

The fake stack frames produced by appendInlinedCalls are
distinguished from real stack frames by having the Inlined attribute
set to true. Also their Current and Call locations are treated
differently. The Call location will be changed to represent the
position inside the inlined call, while the Current location will
always reference the real stack frame. This is done because:

* next, step and stepout need to access the debug_info entry of
the real function they are stepping through
* we are already manipulating Call in different ways while Current
is just what we read from the call stack

# Changes to step, next

The strategy remains mostly the same, we disassemble the function
and we set a breakpoint on each instruction corresponding to a
different file:line. The function in question will be the one
corresponding to the first real (i.e. non-inlined) stack frame.

* If the current function contains inlined calls, 'next' will not
set any breakpoints on instructions that belong to inlined calls. We
do not do this for 'step'.

* If we are inside an inlined call that makes other inlined
functions, 'next' will not set any breakpoints that belong to
inlined calls that are children of the current inlined call.

* If the current function is inlined the breakpoint on the return
address won't be set, because inlined frames don't have a return
address.

* The code we use for stepout doesn't work at all if we are inside
an inlined call, instead we call 'next' but instruct it to remove
all PCs belonging to the current inlined call.

Done.

@aarzilli must rebase.

Done


update documentation to use new project and package names

👍 Looks good to me. I'll trust you on the project.name and tagPrefix stuff.


Add Favorites Button Functionality

This PR adds functionality for the favorites button. The button itself is pulled out into another component.

PR Overview

In this PR, we want to add the 'Favourite' button functionality.
The Favourite button has the following requisites:

On page load, the button should indicate whether the current Subject has already been 'favourited'. (Filled heart = already marked as favourite, empty heart = not marked.)
When the button is clicked, the Panoptes API needs to be informed to add the Subject to the user's list of Favourites.

OR, if the Subject is already in the user's list of Favourites, the Panoptes API needs to remove it from the list.
On that note, when the button is clicked, the heart icon needs to be updated to reflect the current favourite/not-favourite status.

A list of the user's favourites can be viewed at https://www.zooniverse.org/favorites/USERNAME?env=ENVIRONMENT, e.g. https://www.zooniverse.org/favorites/darkeshard?env=staging (you need to login to see your own favourites - I don't believe faves are open info.)

Note the heart icon on the right hand side.
Minor Note:
If we're going for a multi-image Subject route when we organise our project, users need to be aware that they're marking a whole document as a favourite, not a single page.
Status
Reviewing

PR Review
I'm currently encountering issues with the Favourites/Favorites feature.

Using OSX+Chrome and accessing http://localhost:3000/classify...
When I click on the Favorite button, the icon indicates that the Subject has been favourited (i.e. the Heart becomes filled)...
However, a quick check indicates that Panoptes did not register the Subject in my list of favourites.

Analysis:

When clicking on the Favorite button, the console shows an error message: TypeError: Cannot read property 'display_name' of null
This is traced to ducks/subject, the line...

display_name: `Favorites ${project.data.display_name}`

...where project.data is undefined. Or not conforming to the expected structure. Or something.
This may be related to an error seen in the Network console: https://panoptes-staging.zooniverse.org/api/projects/1764?http_cache=true returns a 404, so perhaps the project isn't being pulled properly.

PR Review (update)

With the most recent updates, I can confirm that the Favorite button functions as required - the icon correctly reflects the Favourite-ed status of the Subject, and the 'registering' of a Favourite-ed item can be confirmed at the Zooniverse.org fave page.
While this PR is functional - and I'm clicking that 'approve' button - there is a small tweak to the code that I'd like to request for future robustness. It's that project.data.display_name thing again - I'd like to see some existential checking there to prevent future devs working on our code from running into the same issues that we did earlier.

Status
LGTM, approving, but requesting one change (highly recommended, but not blocking) before a merge.

SOLID! Latest change addresses the recommended existence check, so I'm going to ahead and merge this. 👍


sourceMap option

What nextSourceMap value for sourceMap option mean? Isn't it supposed to be string? I would expect that it is one of these values https://webpack.js.org/configuration/devtool/ If not, could you please describe what it is.

Where did you find that option?

it is in readme https://github.com/intervolga/optimize-cssnano-plugin/blob/master/README.md
`
plugins: [
new ExtractTextPlugin("styles.css"),
new OptimizeCssnanoPlugin({
  sourceMap: nextSourceMap,
  cssnanoOptions: {
    preset: ['default', {
      discardComments: {
        removeAll: true,
      },
    }],
  },
}),

]
`

Sorry, that is misspell.
Source map should be boolean.
In my projects true for  development, false for production.


[Breaking change]: IAsyncEnumerable API buffered result stopped working even when not using System.Text.Json

Description
I am using buffered output from AutoMapper ToAsyncEnumerable with API configured to use Newtonsoft Json as JSON serializer.
context.Table.AsQueryable().ProjectTo<TableModel>(mapper.ConfigurationProvider).ToAsyncEnumerable()
After upgrade to dotnet 6.0.100, the response from this API call is as follows:
{"current":null}
Since such behavior is not documented, I would assume this is a breaking change or a bug. I am using AutoMapper 9, running on Linux.
Version
Other (please put exact version in description textbox)
Previous behavior
Resulting JSON array was returned
New behavior
{"current":null} is returned
Type of breaking change

[ ] Binary incompatible: Existing binaries may encounter a breaking change in behavior, such as failure to load/execute or different run-time behavior.
[X] Source incompatible: Source code may encounter a breaking change in behavior when targeting the new runtime/component/SDK, such as compile errors or different run-time behavior.

Reason for change
There should be a method of streaming results without oboe.js.
Recommended action
Bring back previous streaming behavior.
Feature area
ASP.NET Core
Affected APIs
No response

@eiriktsarpalis Do you know what might be causing this?

I'm not sure. A minimal reproduction would help here. @t00 have you filed an issue in dotnet/runtime?


WIP Get ImportProvider working with mutability and provided methods.

This new branch has ImportProvider working with mutability for struct members, allowing for the dynamic importing functionality I initially described. Without the custom_import feature enabled, permissions checking remains same. Imports that use file or http/https are not able to be overridden by ImportProvider, but I don't think that's a huge loss.
Permissions checking in RustyLoader's resolve method occurs after the ImportProvider's (or deno's) resolve method is called. This means that if the user makes a custom specifier resolve to an http or https url while url_import is disabled, the resolution will fail as web imports are not allowed, even though the specifier doesn't contain http or https on the javascript side.
I also added two separate examples, which I think demonstrate why I think ImportProvider's import and resolve should be provided methods; they have separate use cases and should be able to be used conveniently without both methods implemented. The exact implementations provided by the trait may not be final.
EDIT: There's also a couple formatting anomalies. I will clean this up later today.

Sorry for the delay here. That test isn't written yet and a couple parts maybe could be a bit cleaner, but I think these changes are a bit more like what you were looking for. Feel free to suggest more changes.
Also, I don't know why maybe_referrer needs to be in an Rc in order to avoid the extra clone but the others are fine. Will investigate further.

The import method on the ImportProvider trait still has the same return as before, but since file and http/https are placed in the match statement before the custom behavior is reached, the provided implementation of that method only denies schemes that rustyscript doesn't already recognize.  If that method returns an option, it has to be handled inside the returned future, which means we'd need some way to route back to the logic for the other schemes, requiring a decent amount of rewriting. Unless we want to execute the user's load method outside of the boxed local async block?

Nvm figured it out, see commit.

And that's the test done. Feedback is appreciated.

I have not forgotten about this, btw
Just trying to get 0.5.0 working and out, and this can be 0.5.1 immediately after

I have not forgotten about this, btw Just trying to get 0.5.0 working and out, and this can be 0.5.1 immediately after

Of course, don't worry about it. I will take care of any merge work that will be necessary.

@rscarson There's a handful of "unused variable" and "variable is never read" warnings which only appear when the feature gate is disabled. Is it preferable to silence these with underscores or #[allow(dead_code)]?

@rscarson There's a handful of "unused variable" and "variable is never read" warnings which only appear when the feature gate is disabled. Is it preferable to silence these with underscores or #[allow(dead_code)]?

Where are the errors?

Where are the warnings?

warning: unused variable: `kind`
   --> src/module_loader.rs:155:9
    |
155 |         kind: deno_core::ResolutionKind,
    |         ^^^^ help: if this is intentional, prefix it with an underscore: `_kind`
    |
    = note: `#[warn(unused_variables)]` on by default

warning: unused variable: `maybe_referrer`
   --> src/module_loader.rs:210:9
    |
210 |         maybe_referrer: Option<&ModuleSpecifier>,
    |         ^^^^^^^^^^^^^^ help: if this is intentional, prefix it with an underscore: `_maybe_referrer`

warning: unused variable: `is_dyn_import`
   --> src/module_loader.rs:211:9
    |
211 |         is_dyn_import: bool,
    |         ^^^^^^^^^^^^^ help: if this is intentional, prefix it with an underscore: `_is_dyn_import`

warning: unused variable: `requested_module_type`
   --> src/module_loader.rs:212:9
    |
212 |         requested_module_type: deno_core::RequestedModuleType,
    |         ^^^^^^^^^^^^^^^^^^^^^ help: if this is intentional, prefix it with an underscore: `_requested_module_type`

warning: field `import_provider` is never read
  --> src/module_loader.rs:48:5
   |
46 | struct InnerRustyLoader {
   |        ---------------- field in this struct
47 |     cache_provider: Rc<Option<Box<dyn ModuleCacheProvider>>>,
48 |     import_provider: Rc<Option<RefCell<Box<dyn ImportProvider>>>>,
   |     ^^^^^^^^^^^^^^^
   |
   = note: `InnerRustyLoader` has a derived impl for the trait `Clone`, but this is intentionally ignored during dead code analysis
   = note: `#[warn(dead_code)]` on by default

warning: `rustyscript` (lib) generated 5 warnings

Whoops, messed up the merge on the test section. Will get that in a bit.

@rscarson I made sure to more thoroughly feature-gate every instance where ImportProvider is used, even in function parameters. I've just been adding to module_loader.rs thus far, so gating the whole file wouldn't make much sense at the current moment, but if you'd prefer I can split this feature off into its own file.

LGTM! I'll merge this in Monday! Thanks for all your hard work!

I had to make a few changes, but the new trait is now integrated and working
I also modified it in a way that feature-gating is no longer required


Rate limiter unit tests

Describe the Issue
Implement unit tests for the rate limiter CCTXs query

To be merged: https://github.com/zeta-chain/node/pull/2060


DBZ-6388 __source_ts_ms r (read) operation date is set to future for SQL Server

https://issues.redhat.com/browse/DBZ-6388

Hi @harveyyue, could we adjust the commit message as I have done for the PR message, thanks?

Applied to main (=2.3), thanks @harveyyue !


[Navigation Material] Current release 0.30.0 ships navigation-compose alpha

Description
Current accompanist stable release 0.30.0 ships the navigation-compose:2.6.0-alpha07. We have an internal policy that we dont want to alpha versions without an important reason. This includes also transitive dependencies.
Was this commit intended and what was the reason?
https://github.com/google/accompanist/commit/c1ac4cb0a1bf4d2e01e7def6a3479204805f48d0
Steps to reproduce
Expected behavior
Stable releases only ships stable transitive dependencies or has a valid reason to depend on beta/alpha versions.
Additional context

I came here to create this same issue.
Especially because the alpha version seems to have an annoying bug where it always adds parent nav graphs multiple times to the back stack.
So, totally agree let's have stable accompanist use stable 2.5.3 compose navigation 🙂


We need more settings to express when scores should be shown

At the moment, there are settings about when to reveal answers - immediately on completion, when entering in review mode, or never.
There should be a similar setting for showing all scores. There's only one "revealed" flag for the exam, which covers both expected answers and scores. You might want to show scores but not expected answers after the exam is finished.

see numbas/editor#795

Another awkward thing that we noticed today: when you have "reveal answers to all questions" set to never, the results page doesn't show individual question scores, even though they're visible when you review the question. They should be hidden only when "show scores in review mode" is off.
There should be a way to say that scores shouldn't be shown immediately after finishing the exam, but are shown when you re-enter in review mode.


Fix Azure/autorest.typescript#545 where obviously fixable

CC @daviwil
One of our users reported an issue (#6634) that led me to a bug in our code generation (Azure/autorest.typescript#545). The issue is that the baseUri option always defaults to the endpoint of the Azure Resource Manager in whatever environment it is in, and what is clearly intended in the code to be the default endpoint is silently ignored. In practice, that means that the baseUri parameter on those clients was actually required and non-optional.
In addition, the error message returned by the service when no baseUri is provided is not very helpful.
I've manually patched a few packages for now to ignore the ARM default endpoint and use the Azure Public Cloud endpoint unless baseUri is set in the options bag.

This isn't quite right. Don't merge this yet, as 3/4 of these packages are using ms-rest-js which should not be affected (only ms-rest-azure-js). I am trying to figure out if it is really only @azure/graph that is affected here.

It really does seem like @microsoft/graph is the only package affected here.

The check:everything script should have failed as the version is not updated in this PR.
The expectation of auto generated libraries is that a version bump is done in each PR, and the package is auto published when merged.
Can you take a look if we are excluding graph from such checks?

@ramya-rao-a At a glance, it looks like check:everything is trying to diff between origin/master and origin/patch-ts-gen, which wouldn't work because patch-ts-gen is in my fork not this repo.
I added a version number bump to 5.0.1


[Feature Request] Support InternLM

Dear DocsGPT developer,
Greetings! I am vansinhu, a community developer and volunteer at InternLM. Your work has been immensely beneficial to me, and I believe it can be effectively utilized in InternLM as well. I hope to get in touch with you.
Best regards,
vansinhu

Hi, I see that the model has huggingface page, this it should work locally for users too, using from_pretrained
If you want, you can provide some examples in our documentation.
You may want to check out https://github.com/arc53/DocsGPT/blob/main/CONTRIBUTING.md to get you started

A quick not for people who are thinking about using a different LLM with docsgpt.
https://docs.docsgpt.cloud/Guides/How-to-use-different-LLM


Support for bundling assert (Node.js core) and async (NPM) modules

I have this script:
let path = require('path');
let Builder = require('systemjs-builder');

let builder = new Builder(__dirname, {

  paths: {
    assert: require.resolve('assert'),
    async: require.resolve('async')
  }

});

let src = path.resolve(__dirname + '/browser-polyfills/systemjs/all-core-and-npm.js');
let dest = path.resolve(__dirname + '/dist/outfile.js');

builder
.bundle(src, dest )
.then(function() {
  console.log('Build complete');
})
.catch(function(err) {
  console.log('Build error');
  console.log(err);
});

it's pointing to a node.js file in my project that simply has 2 lines like so:
require('assert');
require('async');

what I am looking to do is bundle the core assert module and the async NPM module into a SystemJS build for the front-end.
However when running the script, I get this output:
Build error
{ Error on fetch for assert at file:///Users/alexamil/WebstormProjects/oresoftware/sumanjs/suman/assert
        Loading browser-polyfills/systemjs/all-core-and-npm.js
        Error: ENOENT: no such file or directory, open '/Users/alexamil/WebstormProjects/oresoftware/sumanjs/suman/assert'
    at Error (native)
  originalErr:
   { Error: ENOENT: no such file or directory, open '/Users/alexamil/WebstormProjects/oresoftware/sumanjs/suman/assert'
       at Error (native)
     errno: -2,
     code: 'ENOENT',
     syscall: 'open',
     path: '/Users/alexamil/WebstormProjects/oresoftware/sumanjs/suman/assert' } }

is there any way to accomplish want I want to do? Totally stuck. Thanks.

I realized what was happening => require.resolve('assert') does not yield an absolute path, I filed a ticket with Node.js about this, since that seems bad. Closing, thanks.


[RELAY][PASS] detect depthwise conv2d in mac_count pass

before mobilenet1.0 was counted as over 4G MACs, now it is ~500M MACs.

Any updates? Is the general group conv2d supported? We should probably try to get it merged before it start to bitrot


Release notes are difficult to associate with package versions

Description
Currently release notes are sent out with every release in the form of a blog post. These blog posts are dated, but do not show the version numbers of the packages. The installed npm packages however use semver. To answer the question "have any released changes addressed a problem I'm experiencing, and are there any breaking changes I need to be aware of to update?" neither the github releases or the release notes posts provide all the answers.
By looking for the tag for the version I have installed I can determine what date it was released, then start finding the relevant blog posts. But it would be easier if this information was all in one place. Even including the tinacms package version in the release notes as a lowest common denominator might be helpful. A CHANGELOG.md which just contains a link to the blog posts might also be helpful to others.

This is a problem that I has been annoying me basically since this project started. Unfortunately I don't really know what we can do.
Here's the crux of the issue. As of today, the tinacms/tinacms monorepo contains about 35 packages. In order to make developing and publishing this vast array of packages easier, we use lerna. Lerna let's you choose between independent and fixed vesioning schemes. In independent versioning, every package has it's own version number. In fixed versioning, every package has the same version number.
This project uses independent versioning. The reason it does that is that a lot of the packages are totally decoupled. If we were to use fixed versioning then it would break semver on all of the packages. For example, updates to next-tinacms-github will never effect anybody that uses gastby-tinacms-git, but with fixed versioning a new feature added to the next package would create a minor version bump in the gatsby package. As the project grows, we might start having dozens of packages having new versions published even if they don't need them.
My suspicion is that it might be better if all the core packages (i.e. those scoped to @tinacms were versioned together) and other packages were not then it would be fine. As far as I know lerna does not allow for this. This means the only way we could do this is by moving the non-core packages out of the monorepo into other repositories. This would solve the problem for people using Tina, but it would make developing Tina harder because it would increase the difficulty of developing non-core packages using the local core packages.
In summary

Keep with independent versioning aka ignore the problem
Switch to fixed versioning and forget about semver
Move all non-core packages from the mono repo and put them in other packages.
 I'm pretty much fed up with the current approach and I'm not sure I care about semver. There's a lot of advantages to going with the fixed approach (i.e. versioning documentation, identifying mismatched versions in your package.json) but it might be problematic.
Worst case scenario we have to switch back. Should that happen it won't be that big of a deal. We're pre-1.0 so I'm willing to be a bit annoying. Right now I care more about the project being designed and managed well then I do in maintaining API so to speak.
That said, I would love to hear your opinion @IronSean, as well as the opinion of anyone else who might be interested.

@ncphillips you could pull off a double monorepo in a single git repo with Lerna by doing:
|-- core
|--- lerna.json.   => 1
|- packages
|--- lerna.json    => 2
|- lerna.json        => 3

Where:

Handles publishing core fixed
Handles publishing packages independant
Handles development concerns

Yeah, I knew this would be a real dog of an issue when I mentioned it. There are so many decoupled packages involved there's no simple answer.
I figured just associating the tinacms root package version like you mentioned in option 1 might be nice since everyone will have it, everyone will possibly be updating packages at the same time, and it'll probably update versions more often then not. But faces the limitation that some weeks it might not actually get any releases and suddenly the whole "one helpful hint" approach breaks down. It's definitely the simplest incomplete bandage.
For option 2, I've used collections of packages before that use that approach: every package gets a version bump even if nothing has changed. As a developer it's easy to reference one set of release notes with one version number, and it's easy to know that all your versions are in sync. It's also fairly easy to just bump them all up at the same time. It definitely causes some release bloat though, where multiple package versions are the same code. It ends up being semver for the entire project ecosystem instead of individual packages.
But npm should mostly handle that package version bloat. And although there are 35 packages currently, it seems most developers only install a handful in a given project. As a developer I don't find it unreasonable to go "oh library collection X has had a release, time to update them all to 2.2.3".
I also don't know if semver for individual packages provides value in the context of tinacms. If gatsby-tinacms-git has a breaking change I don't want to update to, and I update tinacms to a version that expects it to be updated I'll get a peer dependency error anyway. And if I'm updating any tinacms packages, I imagine under most circumstances I would update them all. If I decided not to update one for some reason I would probably hold off on updating any. Although decoupled, I wouldn't feel comfortable mixing and matching old and new plugin versions without having intimate knowledge of all their relationships.
That said, if @chrisdmacrae's approach above works, that might be a nice compromise of getting all the core packages on a fixed version scheme, and leaving the secondary packages that are unlikely to frequently update to do their thing. If Gatsby somehow goes completely out of fashion, you could stop updating those related packages and leave them at their final release. I think that approach could also work for a fixed versioning scheme, where gatsby-tinacms-git gets left at 2.5.1 while tinacms continued to >3, but I don't know how annoying configuring lerna to stop updating a package is if you switch to fixed globally.

This is some really great feedback.

t'll probably update versions more often then not. But faces the limitation that some weeks it might not actually get any releases

As a developer it's easy to reference one set of release notes with one version number, and it's easy to know that all your versions are in sync. It's also fairly easy to just bump them all up at the same time.

This is the major benefit in my eyes. Seems like the downside is low, and the benefits to both maintainers and developers is high.

wouldn't feel comfortable mixing and matching old and new plugin versions without having intimate knowledge of all their relationships.

This is a really good point. Doing that is something someone might do in theory, but so far I doubt it would happen in practice.

but I don't know how annoying configuring lerna to stop updating a package is if you switch to fixed globally.

If it really became that stale we could remove the package from the repository

Sorry if I'm missing this context but it's not clear why these version bumps are happening? Does Lerna think there's a change when there isn't? As far as I know Lerna is able to look at the previous changes for a package

Sorry if I'm missing this context but it's not clear why these version bumps are happening? Does Lerna think there's a change when there isn't? As far as I know Lerna is able to look at the previous changes for a package

With fixed every package gets bumped always as they all have the same version number.
With independent, if a package's dependency gets bumped then it gets a patch bump to update the dependency version number. For example, if I change @tinacms/core then basically every package in the repository gets a patch bump. But if I change react-tinacms-github then no other package gets updated.

The real issue though isn't the version numbers, it's how does someone using make sense of the version numbers? How can they use the version numbers to figure out what changes they might have to make?

A sort of out there idea would be a mixed mode: Packages are always on the same version, but the version only increment when there are changes.
i.e.
pA 1.0.0, pB, 1.0.0, pAB 1.0.0
pA 1.0.0, pB, 1.0.0, pAB 1.0.0

A sort of out there idea would be a mixed mode: Packages are always on the same version, but the version only increment when there are changes.
i.e.
pA 1.0.0, pB, 1.0.0, pAB 1.0.0
pA 1.0.0, pB, 1.0.0, pAB 1.0.0

Fun fact: Shift+enter in github posts your comment instead of a line break. And I think it even chose "Close and Comment" over "Comment"
A sort of out there idea would be a mixed mode: Packages always update to the same version, but the version only increment when there are changes.
i.e.
pA 1.0.0, pB, 1.0.0, pAB 1.0.0 //initial state
pA 1.0.1, pB, 1.0.0, pAB 1.0.1 // update pA, pAB also updates because pA is a dep.
pA 1.0.1, pB, 1.0.0, pAB 1.0.2 // update pAB, nothing else was changed
pA 1.0.1, pB, 1.1.0, pAB 1.1.0 // update pB, pAB updates because it's a dependency.
I can't decide if this is a good or awful idea. I'm probably just high on fumes since my mental gas tank is about empty for the day. It definitely isn't supported out of the box with Lerna.

Hello, i thought it might make sense to drop my 2ct here as well - essentially another option to https://github.com/tinacms/tinacms/issues/1331#issuecomment-659056943 :
just do a monorepo with a topic specific changelog.

I just upgraded to apollo-client@3 and have to say working with it is a breeze.

you have single package shipping all the bells and whistles instead of x package
local development and linking the package is super easy as it's a single package (didn't do that yet, but with tina i did and it's a tad annoying as you have to link multiple packages)

What exactly is the big advantage of shipping all these tinacms parts (from which in a lot of cases a big subset is used together at some point) as multiple packages? A medium post on that topic.

Hey @sakulstra thanks for the input! I intend on writing more about this in the future but I'll answer in short here. The main thing is that Tina is a not meant to be a standalone application, but a toolkit for building CMSs. We provide many tools for people using Tina in different use-cases. One reason why this matters is bundle sizes. People using next-tinacms-github shouldn't need to use gatsby-tinacms-git, and vice versa.  We even extracted react-tinacms-editor so you can leave the wysiwyg out entirely, or at least load it more efficiently. This idea extends even to some of the "core" tinacms features. Making it possible to remove the tinacms package from your website would be quite difficult, but because of the more decouple structure developers with serious performance constraints can by-pass it and get more control over their website and CMS. There's certainly downsides to using the decoupled mult-package architecture, but in the case of Tina it is the most appropriate structure for our goals.

While I was/still am following that thinking for some projects I think the point on bundle size not  true when using modern bundlers and side effect free code.
When using parts of gql-client, lodash or material-ui, you only pay the price for e.g. popper.js in bundle size when you import sth using popper.
Anyhow that's just food for thought. I realized that 100% of my private monorepo usage is in fact unnnecessary which got me thinking it might be the case with Tina as well.
Tina is as it is, is incredible cool - I'm happy to continue importing a few modules 😅

Having switched to fixed versioning I think this issue is resolved.
Here's the first Release Notes post after switching
Here's the project wide CHANGELOG


libgstreamer rpi dependency version

Hi, thank you for this really good work.
I'm a bit curious is there any important reason why you include libgstreamer0.10-dev and libgstreamer-plugins-base0.10-dev at the times when there are gst-1.0 packages available?

Thanks, and you're welcome!
The two libgstreamer pacakges needed to be 0.10 for qt 5.9.3. That might have changed with qt 5.9,4, do you know more about it?

Afaik Qt >= 5.8 should rely on gst-1.0 by default. And according to this thread you can specify the version explicitly for QtMultimedia with:
qmake -r GST_VERSION=1.0
make
make install

I am currently stuck with weird gstreamer behaviour on RPi3. gst-play-1.0 perfectly decodes Full HD mp4 videos using playbin, qopenglwidget and cube examples definetely utilize brcm_egls. But if you will try to make them work together you get fucked with terrrible framedrops (while logs show that hardware decoding is utilezed) :)
I'm not asking for help, but any ideas are appreciated :)

Ok, actually there is no need to explicitly set  GST_VERSION=1.0. Qt determines available version of gstreamer and configures itself to use it. Just checked it is working.
I suggest update gstreamer dependency to 1.0. (though it is really broken on Stretch, for compiling and linking purposes it should not be a problem).

Please try the new release I just committed.
Since they do not conflict I am simply installing both glstreamer 0.10 and 1.0 now and let the Qt builder pick the one it prefers (Qt 5.9.4 in my case chooses 1.0).
Cheers and let me know if it works!
Christian

Great, and thanks for the feedback!


Clarify the purpose of contrib/bug390.patch

There's an old patch sitting in the contrib/ folder called bug390.patch.  The current GitHub repository does not have an issue with that high of a number yet, so it's a bit of a mystery as to what this patch is for.
The closest match I could find is this ticket for PowerDNS that referneces an old Bugzilla instance that NLnetlabs used to run on their home website that had an ID of #390, which seems to align with something the patch is doing:

It appears bind version <9.9.0 requires extra NSEC3 records to validate positive wildcard queries. It would be nice to have a compatibility config switch/option and ability for pdns to serve these extra records that older bind versions require to properly validate.
Ref to same issue with NSD: https://www.nlnetlabs.nl/bugs-script/show_bug.cgi?id=390

However, that Bugzilla instance no longer exists, so it's impossible to review it and see if it's applicable to a modern-day build of NSD.  Can someone evaluate whether this patch is still needed and, if it is, document what it's doing and/or maybe drop some history about it if info from the old Bugzilla instance is still available?  Thanks!

The bugzilla page explains that the patch was briefly useful, while bind had an error where it would need a superfluous NSEC3 record. The patch provides this record, until the time when bind could have been patched to upgrade and fix the issue. That was on 2011-10-26. And in 2013-05-16 there is note that BIND 9.9.0 correctly validates without needing this patch. At that time the patch became no longer necessary.

The commit fixes the text in contrib/README to explain the purpose of the patch. That has been fixed for some time now, so I guess the patch could be removed. But I am keeping it for the moment to make the documentation visible with it.


Chrome won't work without --no-sandbox option

Hi !
I'm using Arch as host, with 4.6.2-1 kernel and 1.11.2 is my Docker version.
This doesn't work for me:
 docker run -it \
    --net host \ # may as well YOLO
    --cpuset-cpus 0 \ # control the cpu
    --memory 512mb \ # max memory it can use
    -v /tmp/.X11-unix:/tmp/.X11-unix \ # mount the X11 socket
    -e DISPLAY=unix$DISPLAY \
    -v $HOME/Downloads:/root/Downloads \
    -v $HOME/.config/google-chrome/:/data \ # if you want to save state
    --device /dev/snd \ # so we have sound
    -v /dev/shm:/dev/shm \
    --name chrome \
    jess/chrome

this doesn't open the chrome window for me. but when I add--no-sandbox or --disable-setuid-sandbox, it works.
Also, with 512mb ram, it crashes tabs multiple times, also "HTTPS everywhere" and "uBlock" will crash multiple times. adding --disable-appcontainer won't help either.
is there any way to run Chrome container with sand-boxing in Arch ?
best regards.

Oh it's because you don't have userns enabled in your kernel

See https://github.com/jfrazelle/dockerfiles/issues/65

I can confirm after enabling User Namespace and re-compiling the kernel (4.7RC3), it works flawlessly. Also, VLC on docker seems to be working better and i3 shows the logo at the bottom.

I got the same problem ,so i disable sandbox ,but it still cann't works!

@creatist You need to enable user namespaces in your kernel for this to work.

I can confirm after enabling User Namespace and re-compiling the kernel (4.7RC3), it works flawlessly. Also, VLC on docker seems to be working better and i3 shows the logo at the bottom.

Could you tell me what command you ran to do this? I'm new to docker.

I can confirm after enabling User Namespace and re-compiling the kernel (4.7RC3), it works flawlessly. Also, VLC on docker seems to be working better and i3 shows the logo at the bottom.

Could you tell me what command you ran to do this? I'm new to docker.

did you get any resources for how to disable sandbox and run chrome in docker.

I can confirm after enabling User Namespace and re-compiling the kernel (4.7RC3), it works flawlessly. Also, VLC on docker seems to be working better and i3 shows the logo at the bottom.

Could you tell me what command you ran to do this? I'm new to docker.

did you get any resources for how to disable sandbox and run chrome in docker.

Yes, please help! I'm totally lost reading pages like this:
https://docs.docker.com/engine/security/userns-remap/


feat!: Make linear types @inout by default; add @owned annotation

Resolves #413 and #414.
BREAKING CHANGE: Linear function arguments are now borrowed by default; removed the now redundant @inout annotation

I think you also need to update the autogenerated constructors for structs (see guppylang/definition/structs.py) to take ownership of linear arguments. Surprising that this wasn't caught by the tests :/

I've added a test and the logic for this, but it seems like it was working by accident! Something's a bit fishy there...

@croyzor could you also resolve the conflicts that github is pointing out in tests/integration/test_array.py?


Should GO:0016174 exist?

I am looking at a paper describing a plant NADH(P) oxidase, and Im trying to figure what its activity is
(A fungal gene directly regulators the activity of the gene product)
there are 2 slightly different reactions
GO:0016174    NAD(P)H oxidase activity
Catalysis of the reaction: NAD(P)H + H+ + O2 = NAD(P)+ + hydrogen peroxide.
GO:0016175  superoxide-generating NADPH oxidase activity
Catalysis of the reaction: NAD(P)H + O2 = NAD(P)H + O2-. PMID:10806195
I assumed the reaction catalysed was
GO:0016175  superoxide-generating NADPH oxidase activity
but all arabidopsis are annotated to GO:0016174
form the paper intro
Generation of a burst of reactive oxygen species (ROS) catalyzed by NADPH oxidase (Nox) is an important defense mechanism for both mammals and plants against invading microbes (Doke, 1983; Reeves et al., 2002; Lambeth, 2004; Torres and Dangl, 2005). In phagocytes, activation of the membrane-associated NADPH oxidase (gp91phox/NOX2) to produce ROS in response to microbial or inflammation signals involves cytosolic recruitment of a heterotrimeric phagocyte oxidase complex (phox) together with the small GTP binding protein Rac2 (Diebold and Bokoch, 2001; Lambeth, 2004). The discovery of new functional members of the Nox family has led to the recognition that ROS production is a ubiquitous eukaryotic signaling system to control various dif- ferentiation processes, including cell proliferation, apoptosis, and hormone responses in animals (Suh et al., 1999; Lambeth et al., 2000; Lardy et al., 2005), programmed cell death and root hair growth in plants (Foreman et al., 2003; Carol et al., 2005), and sexual development and spore germination in filamentous fungi (Lara-Ortiz et al., 2003; Malagnac et al., 2004; Aguirre et al., 2005).
then I found this in another paper:
NADPH oxidase enzymes belong to a family of transmembrane
proteins able to transport electrons across a membrane -usually
the plasma membrane- from a cytosolic electron donor to oxygen
-the extracellular acceptor- thus catalyzing the generation of O•−
2
(Lambeth, 2004). However, the lifespan of superoxide molecules,
which are rapidly dismutated to H2O2 either spontaneously or
through the action of apoplastic superoxide dismutases (SOD),
is extremely short (Bowler et al., 1994). NADPH oxidase (NOX)
activity was first described in mammal phagocytic cells and
consists of two plasma membrane proteins, gp91phox and
p22phox (phox for phagocyte oxidase). This protein complex
is regulated by its interaction with other cytosolic proteins
(p47phox, p67phox, p40phox, and Rac2) producing the active
form (Cross and Segal, 2004; Lambeth, 2004). Although these
mammalian protein complexes are the most studied NOXs, these
enzymes have also been characterized in other animals, fungi,
and plants. NADPH oxidase enzymes share a basic structure
consisting of six transmembrane domains, two heme-binding
sites and a long cytoplasmic C-terminal which includes FAD and
NADPH binding sites (Bedard et al., 2007).
so it seems that the reaction catalysed is
GO:0016175  superoxide-generating NADPH oxidase activity
Catalysis of the reaction: NAD(P)H + O2 = NAD(P)H + O2-.
Should GO:0016174 exist?
I can't find an EC number or a ref.

RHEA:11260 : H(+) + NADPH + O2 = H2O2 + NADP(+)
Yes the term is real.
GO:0016174 NAD(P)H oxidase activity
Catalysis of the reaction: NAD(P)H + H+ + O2 = NAD(P)+ + hydrogen peroxide (H2O2)

EC <IP_ADDRESS>
PMID: 10401672
PMID: 10601291
PMID: 11822874
(refs are from the RHEA entry;
I will update GO:0016174

The EC was there already in the term info.

Update done. I assume I can close this.

so even though EC's exist,  this is definitely not the case?
"two views of the identical molecular function, one that defines the reaction in terms of the immediate product of the reaction enabled by the oxidase activity and the other in terms of the first relatively stable product of that reaction."
if not, I'm not sure how to figure out which one I am annotating, and the common parent is
GO:0050664   oxidoreductase activity, acting on NAD(P)H, oxygen as acceptor
which is n't very satisfactory?
So in that case, if these 2 term definitely exist to describe different reactions, would it be possible to have a parent grouping term?

Actually
GO:0050664 oxidoreductase activity, acting on NAD(P)H, oxygen as acceptor
is OK.
or make the term name of
GO:0050664 oxidoreductase activity, acting on NAD(P)H, oxygen as acceptor
NADPH oxidase
currently broad for NADPH oxidase | broad for  GO:0016174   NAD(P)H oxidase activity

Forgot to mention that I also added the EC name as an exact synonym NAD(P)H oxidase (H(2)O(2)-forming)
I could change to make THAT the name of 664, to make it more explicit, since the other term has 'superoxide' forming. I would not want to make a grouping term that I would feel the the need to make do not annotate since one makes superoxide and the other does not.

OK; changed the name to bring it more in line with it's sib. That should make it very clear

on nuts forgot to add 'activity' I'll get this right yet.

OK thanks! I'll figure it out ;)

Also noticed sib term does not have a RHEA; requesting
[help #180802] in the subject line of all future correspondence to RHEA  about this issue.

Hi Harold, any news on this one?
Thanks
Val

Note if I didn't mention this before, consider GO:0016174  as a grouping term because its NAD(P). However, RHEA ids can either be NAD, OR NADP, not both. Only to be used IF one doesn't know; presumably, a paper would have an assay (?).
If the enzyme in question CAN use both, it doesn't do it at the same time; hence the two reactions
RHEA:63180 NADPH + 2 O2 = H+ + NADP+ + 2 superoxide
RHEA:63184 NADH + 2 O2 = H+ + NAD+ + 2 superoxide
But not Public yet (will be on June release; so then can add and close this ticket.

Rheas are now public. Made children of GO:0016175
+id: GO:0106291
+name: superoxide-generating NADH oxidase activity.
+id: GO:0106292
+name: superoxide-generating NADPH oxidase activity

Made children for GO:0016174 with RHEA references.; removed rhea from GO:0016174
+id: GO:0106293
+name: NADH oxidase H202-forming activity
+id: GO:0106294
+name: NADPH oxidase H202-forming activity
Since RHEA has supplied the defs, I will defer to them that these are valid terms and close the ticket.


Windows screen settings affects to Screenshots and Actions coordinates

Development of #217 improves the screen coordinates used to make screenshots and mouse movements. This development verify the current display of the environment to make the improvement.
However, there are still problems with the use of a not recommended display (by the system) and the advanced Windows option to fix applications that are blurred.
https://support.microsoft.com/en-us/help/4091364/windows-10-fix-blurry-apps

The resolution issues depend on the environment where TESTAR is being run, and in most cases they can be fixed with Windows settings.


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1653

Questions ?
Please refer to the Backport tool documentation


Int converted à char

I'm on debian 9
When I use typeString with the sequence "test567", I obtain "test(-è"
It seem's that numbers are replaced by the shift-character on the keyboard
thanks in advance for your time :-)

This issue has been closed because it has been inactive for > 180 days.
You may reopen this issue if it has been closed in error.


fatal: protocol error: bad pack header

Gogs version (or commit ref): <IP_ADDRESS>1
Git version: 1.9.1
Operating system: Ubuntu 14.04.1
Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[ x] SQLite

Can you reproduce the bug at https://try.gogs.io:

[ ] Yes (provide example URL)
[x ] No
[ ] Not relevant

Log gist:

gogs.log:
exit status 3 - error: sha1 mismatch c644886cc66af78a38c8ba60cb9c6686d09098c5
error: c644886cc66af78a38c8ba60cb9c6686d09098c5: object corrupt or missing
error: sha1 mismatch cfaed4e3143675833448bd70b8af7bcb4fc8cae0
error: cfaed4e3143675833448bd70b8af7bcb4fc8cae0: object corrupt or missing

stderr.log:
error: corrupt loose object 'c644886cc66af78a38c8ba60cb9c6686d09098c5'
fatal: loose object c644886cc66af78a38c8ba60cb9c6686d09098c5 (stored in ./objects/c6/44886cc66af78a38c8ba60cb9c6686d09098c5) is corrupt
error: corrupt loose object 'c644886cc66af78a38c8ba60cb9c6686d09098c5'
fatal: loose object c644886cc66af78a38c8ba60cb9c6686d09098c5 (stored in ./objects/c6/44886cc66af78a38c8ba60cb9c6686d09098c5) is corrupt
error: corrupt loose object 'c644886cc66af78a38c8ba60cb9c6686d09098c5'
fatal: loose object c644886cc66af78a38c8ba60cb9c6686d09098c5 (stored in ./objects/c6/44886cc66af78a38c8ba60cb9c6686d09098c5) is corrupt
error: corrupt loose object 'cfaed4e3143675833448bd70b8af7bcb4fc8cae0'
fatal: loose object cfaed4e3143675833448bd70b8af7bcb4fc8cae0 (stored in ./objects/cf/aed4e3143675833448bd70b8af7bcb4fc8cae0) is corrupt
fatal: unable to read d003c51e9e9bd9a481061c0f0e8e3fc7d31b69b0

Description
When i use  git clone , the result is :
$ git clone http://xxxxxx/xxxxx/SpiderMan.git
Cloning into 'SpiderMan'...
remote: Counting objects: 1030, done.
remote: error: corrupt loose object 'c644886cc66af78a38c8ba60cb9c6686d09098c5'
remote: fatal: loose object c644886cc66af78a38c8ba60cb9c6686d09098c5 (stored in ./objects/c6/44886cc66af78a38c8ba60cb9c6686d09098c5) is corrupt
remote: aborting due to possible repository corruption on the remote side.
fatal: protocol error: bad pack header

I found my local repo ·.git/objects/· contains those file:
cf/cfaed4e3143675833448bd70b8af7bcb4fc8cae0   2.61MB
c6/44886cc66af78a38c8ba60cb9c6686d09098c5   17.33MB
5b/e979f406913a030d4f2b8406f0765cdc34958d   17.35MB
my repo have some files:
phantomjs-2.1.1-windows.zip   17.3 MB
phantomjs.exe      17.7 MB
But I don't know why it error? How to solve it?

Can you reproduce the bug at https://try.gogs.io?

@Unknwon I'll try and get back to you when I get the results.

I can't reproduce this bug.
I create a new repository and add some big files and it`s good for git clone or other operations. So i guess It`t not because of the big files or program bug . Maybe because of system file error for object corrupt or missing .
Now my solution is to copy a new repository and keep the error one.
Thanks.

Thanks for the feedback!
I'm closing this until it happens more reproducibly.


Can you support python3?

Or just give some ideas how could I modify the code to support python3.
Thanks!

I figured it out by pip3 install -e ./.

hey thanks for checking out the package! I developed with python3 exclusively

If you have issues installing you can use the docker build or check out the travis yaml: https://github.com/btaba/yarlp/blob/master/.travis.yml#L9


chore: maturin develop in justfile + bump execute version

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

Project coverage is 92.62%. Comparing base (471b74c) to head (538e226).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #730   +/-   ##
=======================================
  Coverage   92.62%   92.62%
=======================================
  Files          71       71
  Lines        7955     7955
=======================================
  Hits         7368     7368
  Misses        587      587

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


Setting boost temp sometimes errors

I have seen a situation whereby setting the boost temp when calling setRoomMode causes an error from the hub that it is expecting an integer.
I think this is caused by the fact that passing a float value (ie 21.5) to the method maintains a float when passing to the hub.
Line
temp=boost_temp*10
needs to be
temp=int(boost_temp*10)
to ensure this cannot happen
Thx Mark

Hey Mark, I think I fixed this bug earlier on, which version of HA are you using?
(still not got around to fixing my server :-( , xmas lag...)

I am running 103.4 with wiser component 1.7.1.  I can send you a PR but think just need to sent to an integer value when we multiply boost temp by 10.  Think you have fixed this in the setTemperature method but not in the setRoomMode method.

Sorry i was probably remembering a previous version where you were removing the decimal point instead of multiplying by 10. It is true that i cannot recreate this issue right now but i think we maybe should do the integer conversion as suggested to ensure we cannot pass a non integer value to the wiser hub.

Mark,. this issue is fixed with your PR right?

Yes


could not find urwid-ueberzogen

When I do:
pip3 install --user lookatme.contrib.image_ueberzug
I get the following error.

ERROR: Could not find a version that satisfies the requirement urwid-ueberzogen<1.0.0,>=0.0.4 (from lookatme.contrib.image_ueberzug) (from versions: none)
ERROR: No matching distribution found for urwid-ueberzogen<1.0.0,>=0.0.4 (from lookatme.contrib.image_ueberzug)

I am using python3.8 in Ubuntu.
Also the link to urwid-ueberzogen appears to be broken:

The ueberzog projects are deprecated and have been effectively removed by the owner. See both of the repos for their explanation:

https://github.com/seebye/ueberzug
https://github.com/seebye/urwid-ueberzogen

If you go to previous commits of the repos and manually install those you can get this working, though you might run into issues using the latest version of lookatme.


Popover anchoring issue on iOS 14

The search settings popover anchor moves when interacting with a setting. This is only visible on iOS 14 but might be related to a bug which existed before but with less visible effects.
Issue type
Incorrect behavior
Environment information

Application version: 3.1.4
iOS version: 14
Device: Any

Reproducibility
Always reproducible
Steps to reproduce

Open search settings on an iPad in landscape orientation.
Tap on some setting.
The popover moves to the top left.

This is related to the underlying view being reloaded (commenting out the cell didSelect method fixes the issue). Maybe this is related to the bar button item anchor being recreated in the process.

Avoiding unnecessary button destruction and creation fixes the issue.
We still have an issue with the popover content disappearing and staying invisible after a rotation, but I could trace it back to the use of Fingertips. I will have a look if something can be done, otherwise this is not a severe issue as this code is not added in production builds.

Fixed on the {{feature/popover-fix}} branch. I also updated other popovers (working well) to anchor them to a bar button item.
I have no clue for Fingertips at the moment, but this is not a serious issue (we must only keep it in mind in internal builds).

Thank you for explaining here the "transparence popover after rotation" issue, because of Fingertips SDK. This SDK is not included in the production build, and I checked again that the issue is not reproducible in the AppStore build.
Thank you to found this bug issue, and the fix.


^ - what does it mean in url alias?

^ - what does it mean in url alias?

That's part of a regular expression. ^ means start of a line in regex.
Here it's used as start of the url path.
https://javascript.info/regexp-anchors


IL2CPP Exception for method System.Void.Ninja.Websockets when installing from Asset Store

Describe the bug
IL2CPP Exception errors when building to for any Platform.
Repro project
Unavailable apologies.
To Reproduce
Steps to reproduce the behavior:

Create a New Project in Unity.
Add a scene.
Import Mirror from Asset Store.
Build Project (without using any scripts or prefabs related to Mirror)

Expected behavior
A build will be successful with no errors
Screenshots
Please see build logs attached
BUILD.txt
Desktop (please complete the following information):

OS:  macOS Catalina
Build target:  All Build targets
Unity version: 2019.3.1f1
Mirror branch: Asset Store as of October 10th

Additional context
No use or invocation of Mirror is needed.  Import is enough to cause this.

My mistake. I didn't upgrade the .Net runtime


upload?

Hi,
How can I get a version of this library that supports video uploads?

The upload feature is part of the commercial package downloadable from http://RedCorners.com

Seriously...? (sigh)


Update composer.json

Support for Laravel 8.
Summary of the change:
composer.json laravel requirements.

Thank you <3 !
I'll publish the new release ASAP, with some fixes

Thanks, i'm waiting :)


Some supplements and small fixes

Supplemented stuff I needed when developing with the library, fixed some minor bugs, please refer to commit messages for details.
Since VSCode automatically formats every time I save, I formatted all the code in one commit, so the diff might look a bit messy.
BTW, I'm new to Rust, so some of the code may not be best practices, please let me know or edit the code directly. Thanks!

It's probably better at least splitting the formatting part into a separate PR.
@uonr What do you think?

@upsuper Most of them are simple formatting of examples, just merge it this time.

Thanks!

It's probably better at least splitting the formatting part into a separate PR.

@upsuper I'll pay attention next time.