Clarify Canopy and first halving checks

The consensus rules are explained differently in different specifications. That's probably how we ended up with different checks.
We think these specifications are all equivalent on mainnet and testnet.
Zcash Specification, section 3.9:
[Pre-Canopy] The block subsidy is composed of a miner subsidy and a Founders’ Reward.
[Canopy onward] The block subsidy is composed of a miner subsidy and a series of funding streams.
ZIP 207:
Once the Canopy network upgrade activates:
The existing consensus rule for payment of the Founders' Reward is no longer active. (This would be the case under the preexisting consensus rules for Mainnet, but not for Testnet.)
ZIP 214:
Since ZIP 1014 specifies that the Zcash Development Fund starts at the first halving, the activation height of Canopy on Mainnet therefore SHALL be 1046400.
ZIP 214 also specifies the exact start and end heights  for funding streams: https://zips.z.cash/zip-0214#specification
ZIP 1014:
Starting at the first Zcash halving in 2020, until the second halving in 2024, 20% of the block subsidy of each block SHALL be allocated to a "Dev Fund" that consists of the following three slices
It appears that ZIP 1014 only applies to mainnet, but that's not explicitly stated in the document.
Originally posted by @teor2345 in https://github.com/ZcashFoundation/zebra/pull/1170#discussion_r510005695

It appears that ZIP 1014 only applies to mainnet, but that's not explicitly stated in the document.

This is a bug in ZIP 1014. Thanks for pointing it out.

It appears that ZIP 1014 only applies to mainnet

This is correct. ZIP 1014 deals with how to fund ongoing development, and testnet funds won't achieve that. ZIP 214 is explicit about why it defines the ZIP 1014-outlined funding streams for both mainnet and testnet:

The primary requirement of this ZIP is to make changes to consensus rules necessary and sufficient to implement the intent of ZIP 1014.
The Zcash Development Fund distributes funding in ZEC obtained from block subsidies on Mainnet. This ZIP should also specify corresponding rules, addresses, and activation height for Testnet, in order to allow testing and auditing of the design and implementation within sufficient lead time before activation on Mainnet.

Perhaps we need a separate category or indicator to outline ZIPs that describe social-level consensus but don't actually specify chain consensus rules, so that implementations like zebra don't interpret them as the actual consensus rules. I guess the ZIP 10XX series is intended for that, but it's not spelled out anywhere AFAIK.

ZIP 1014 is a Consensus ZIP in the sense of imposing requirements that should be followed by other ZIPs that define consensus rules. I can change the category to Social Consensus if you think that would be helpful?

This was fixed in ZIP 1014 by https://github.com/zcash/zips/pull/419 .

Thanks for the update! Closing...


Editing a Journal-Entry can move the Sidebar from the right

When you edit some Journal-Entries and safe them while the module is loaded, the sidebar is moving to the left, leaving a gap to the right. Resizing or Reloading (F5) does not fix this, only reopening foundry by reinserting the URL.

I did some crude debugging and found that on opening the editor-sheet, the parent of the HTML-object in includelinks() was the document body itself so that the journal-backlinks element was directly added to the body. I did not want to mess with your code too much neither did i find the real reason. But i think exiting the includeLinks() methon when the editmode is opened or the HTML.parent()is pointing to the body would do the trick.
A really lazy and bad fix i applied was to add:
$("body > .journal-backlinks").remove();
to the end of includelinks() so the tags would be removed. But I guess with your knowledge of the code you will figure it out real quick.
Note: this MIGHT be an issue with the investigator-System, I sadly did not have the time to investigate further, but i hope this helps :)

@Muwak77 would you be willing to test #22 to see if that addresses this issue? It should hopefully resolve the underlying problem (modifying the main body, or any other element that doesn't match what we expect) but could break rendering the backlinks at all for other systems that have been getting by with how generous our matching was.

I'll install it into my TOC and DTE Worlds and see how it goes. Thanks for fixing btw. :)

Should hopefully be fixed in the latest version.


Original issue reported on code.google.com by<EMAIL_ADDRESS>on 25 Oct 2010 at 5:05

What is the real problem of this issue?  Do these entries produce any real mis
conversions?

Actually, the POS (part of speech) of "どーん/Dawn" is expected.  The POS
stems from the Katakana entry "どーん/ドーン". The POS of Katakana to
English transliteration is basically inherited from the corresponding Katakana
entry in order to control the ranking (position) of English transliteration. In
other words,  Mozc's POS does not always correspond to grammatical/syntactic
POS defined in paper dictionaries.  What user really cares about is the quality
of the conversion. Ordinal user are not aware of which POS is assigned to each
entry.  Mozc's POS tag set and POS assignments are designed so that overall
mis conversions are minimized.

Original comment by<EMAIL_ADDRESS>on 27 Oct 2010 at 4:14

Original comment by<EMAIL_ADDRESS>on 1 Apr 2012 at 2:25

Added labels: Type-Conversion
Removed labels: Type-Defect

Original comment by<EMAIL_ADDRESS>on 1 Apr 2012 at 2:29

Added labels: OpSys-All


04/01/2018 19:05 : Create Pull Request for branch master -> prTesting1_2018040119

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef1.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


icons.dart and map.png don't match

https://github.com/flutter/cupertino_icons/blob/master/map.png and icon.dart don't match，it's difficult to find the icon by map.png

Duplicate of #39308


Bridge from Terra to BSC money never arrived

I bridged UST from terra to bsc but funds never arrived:
Edit 1:OK after reading the others issue i have check the etherium chain of my wallet and i have find my ust...
Edit 2: Nice over 30 $ for send back (charging eth wallet ecc ecc)... lets hope going to the right chain now
The service is nice but 2 sends all 2 to the wrong chain.....

Okay I will request to web devs to check this problem.

btw duplicated so close this issue #90


Example of Correct Way to use MaskZero?

I'm getting warning that I'm not using MaskZero correctly. The message is "you are most likely using MaskZero the wrong way. You should probably use AbstractRecurrent:maskZero() so that it wraps the internal AbstractRecurrent.recurrentModule instead of wrapping the AbstractRecurrent module itself." I'm not terribly intuitive idea of what MaskZero does or how it works, so an example could be helpful.
More specifically,
Here is what I want to do:
local enc = nn.Sequential()
enc:add(nn.LookupTable(#indxToChar, opt.hiddenSize)
enc:add(nn.SplitTable(1, 2)) -- works for both online and mini-batch mode
local encLSTM = (nn.LSTM(opt.hiddenSize, opt.hiddenSize))
enc:add(nn.Sequencer(encLSTM))
enc:add(nn.SelectTable(-1))
dec =  nn.Sequential()
dec:add(nn.SplitTable(1, 2)) -- works for both online and mini-batch mode
local decLSTM =nn.LSTM(opt.hiddenSize, opt.hiddenSize)
dec:add(nn.Sequencer(decLSTM))
dec:add(nn.Sequencer(nn.Linear(opt.hiddenSize, opt.vocabSize),1))
dec:add(nn.Sequencer(nn.LogSoftMax()))
The input is of size batchsize x maxSeqLen, but the trick is that maxSeqLen could change size each iteration. So I compute maxSeqLen. If there are sequences that are shorter than maxSeqLen, I put a zero in that position in the input tensor. Where should I be putting nn.MaskZero? Does it even work for this?

You can call maskZero() directly on all objects inheriting from AbstractRecurrence, like on LSTM objects. This will give you a MaskZero object wrapping your module. In your case, you would need to ensure that the zeros get appropriately propagated from the inputs to the LSTM, e.g., by using a LookupTableMaskZero.
Alternatively, you could wrap up everything together in a Recurrence or Recursor object and then call maskZero() there only once.


Runtime versions

Node's isn't versioned but the others are (ex "python2.7"). We'll have to decide on something to handle these weird cases or just allow python2.7, etc in the field, but it would be easier I think to just add a version field.

Closing as we will stick with AWS terminology for now.


Feature request:  custom recognizer extensibility

A very powerful concept is having the capability of custom NLP model integration and some guidance on writing a custom recognizer as an extension.  This could be powerful for the data science community.

In v4 we don't really have a formalized Recognizer interface. Recognizers are just classes so you can create any class you want. I'm not sure what we would document to be honest. Can you create new recognizers? absolutely!  Do you have thoughts for what advice we'd give in docs?

Closing due to no activity

@Stevenic @vishwacsena In searching through current and closed issues, as well as the source code, it doesn't look like much of the recognizer stuff outside of LUIS is coming over to SDK v4, correct?
For example, SDK v3 had builder.RegExpRecognizer(), and you could create a custom recognizer with bot.recognizer().
Are there equivalents to these in SDK v4, or is the assumption that you can just create your own class/method to process the text from context.activity.message since all of that is handled with the processActivity() method (or it could be handled with a middleware component).
Apologies for commenting on a closed issue, but this seemed the most appropriate thread to get clarity rather than creating a new issue.

is the assumption that you can just create your own class/method to process the text from context.activity.message since all of that is handled with the processActivity() method (or it could be handled with a middleware component).

This is the right approach. We're not bringing the Recognizer stuff (see interface) over because there isn't a need for it. You don't "plug" your "recognizer" into the bot, you just call it when it's necessary.
You might make a middleware that caches a recognizer on context.turnState so that it can be called later in dialogs, or you might make a middleware that calls a NLP service and caches the results on context.turnState.
The latter is what we used to do with LUIS, but we decided to take it out because calling LUIS is more complicated than just calling it for every incoming activity. In some cases, getting the results from LUIS was wasteful as it would just get dropped on the floor.


Please improve documentation of WorkspaceEdit.createFile "ignoreIfExists" option

Hi,
https://code.visualstudio.com/api/references/vscode-api#WorkspaceEdit
The createFile takes following option: options?: {ignoreIfExists: boolean, overwrite: boolean} with following documentation: Defines if an existing file should be overwritten or be ignored. When overwrite and ignoreIfExists are both set overwrite wins.
Please make it clear what happens when ignoreIfExists is set to true. For example, if file exists and ignoreIfExists is true, I assume this edit is skipped. But if ignoreIfExists is false, what is the difference? It's not overwritten, it already exists, so I assume the effect is the same - the edit does nothing. But it's not clear looking at documentation and the user is left wondering if he's missing something or not.

Thank you. That was blazingly fast!


Issues with old InterPro2GOs

From Steven:
10.03.23
I just noticed this apparent redundancy where the ‘evidence’ for an InterProGO annotation is shown once on its own and again coupled with a second one
e.g.
https://flybase.org/reports/FBgn0265262#function
https://flybase.org/reports/FBgn0030052#function
Not sure if there’s anything we can do about this?
It’s not exactly wrong, but it gives a false impression of the weight of InterPro2GO evidence (and takes up space!)

From GAF from FB2023_01
multiple gene-GO ID for InterPro2GO
https://docs.google.com/spreadsheets/d/1bmkCJ9HLZc28914_5dJvwcp92OIsqIoCXusKDzrygGE/edit#gid=0

400 instances.

Looks like where there are different UniProtKB IDs : FBgn and those forms have different InterPro mappings due to isoform seq variation then pipeilne adds Interpro lines as diff evidence lines.
Probably need to alter pipeline to select longest string. But must check this further to make sure this is the correct interpretation of the observation.

Gss2; FBgn0052495	GO:0004363	x4
FBgn0052495	Q9VX03 InterPro:IPR005615|InterPro:IPR014042
FBgn0052495	Q1RL06 InterPro:IPR005615|InterPro:IPR014049
FBgn0052495	Q86B44 InterPro:IPR004887|InterPro:IPR005615|InterPro:IPR014042|InterPro:IPR037013
FBgn0052495	Q8IQZ1 InterPro:IPR004887|InterPro:IPR005615|InterPro:IPR014042|InterPro:IPR014049|InterPro:IPR037013
FBgn0052495	X2JCE7 InterPro:IPR005615|InterPro:IPR014042

FBgn0039478	GO:0006508	x3
FBgn0039478	Q8IHC6 InterPro:IPR000718|InterPro:IPR008753
FBgn0039478	Q95SM2 InterPro:IPR000718|InterPro:IPR018497 & InterPro:IPR000718|InterPro:IPR018497
FBgn0039478	Q8IMQ2 InterPro:IPR000718|InterPro:IPR008753|InterPro:IPR018497

Ticket: https://flybase.atlassian.net/browse/DB-876

For FB_2023_05 P2GO load there are a lot of "old" dated InterPro annotations mainly due to addition of do not annotate labels to BP terms slated for obsoletion. This makes a manual clean up via proforma too hard. Checked pseudoenzymes against old InterPro2GO MFs and no overlap.
IEAs.xlsx
need to get this fixed at load in FB2023_06

closing as this is on jira now


Problems parsing custom emoji

![👍](tg://emoji?id=5368324170671202286)

The top of this chart is right and the bottom is wrong. The one below is after escaping

Custom emoji markdown should be sent as is and should not be escaped.

Investigating


mkDummySrc: support freestanding targets

Currently, when building for targets that do not support std, like x86_64-unknown-none, cargo check on the costructed dummy source fails with:
 > error[E0463]: can't find crate for `std`
       >   |
       >   = note: the `x86_64-unknown-none` target may not support the standard library
       >   = note: `std` is required by `sallyport` because it does not declare `#![no_std]`
       >   = help: consider building the standard library from source with `cargo build -Zbuild-std`
       >
       > For more information about this error, try `rustc --explain E0463`.

To prevent this issue from happening, set #![no_std] for freestanding targets.
Signed-off-by: Roman Volosatovs<EMAIL_ADDRESS>Motivation

Checklist

[ ] added tests to verify new behavior
[ ] added an example template or updated an existing one
[ ] updated docs/API.md with changes
[x] updated CHANGELOG.md

Would you be interested in adding a test case to avoid future regressions?

I'd love to, if fact I looked into doing that while working on this, but was not clear how to proceed, so I did not.
I suppose the way to do it would be to add a freestanding target to the CI toolchain to ensure it's picked up with --all-targets?

I'd love to, if fact I looked into doing that while working on this, but was not clear how to proceed, so I did not. I suppose the way to do it would be to add a freestanding target to the CI toolchain to ensure it's picked up with --all-targets?

I forked your branch, rebased it onto the latest master, and added a commit with a cortex-m #![no_std] example: https://github.com/newAM/crane/tree/fix/no_std
The examples get tested in CI as far as I can tell.
Feel free to take that commit, or remix it however you want :smile:

@ipetkov apologies for the delay, but I have just updated the PR, PTAL.
Note that the issue is not in #![no_std] crates, it's in compiling for freestanding targets. Freestanding targets lack a standard library and therefore cannot be compiled for:
1.) when no_std is not set
2.) when the bare-minimum required runtime handlers are are not defined

Hmm.. I failed to reproduce the error in the check, let me do another iteration

This looks great, thanks again @rvolosatovs!
I've pushed some very minor fixes which weren't even worth mentioning here, will merge as soon as CI passes!


Deepstream 3.1.0 not working with Kafka Connector

Hello,
Deepstream is not starting with the official Kafka Connector.
DS v - 3.1.0
deepstream install msg kafka
Plugin Config
# Plugin Configuration
plugins:

  message:
    name: kafka
    options:
      connectionString: localhost:9092

Also tried passing path instead of name.
Error: Cannot find module '/var/lib/deepstream/kafka'
What I have tried so far.

Changing the config name to use the foldername of the connector (deepstream.io-msg-kafka)
Created a sym link of deepstream.io-msg-kafka as kafka in the same folder only to get the below error.

PLUGIN_INITIALIZATION_ERROR | message needs to implement isReady or be an emitter
[eval]:49348
      throw error
      ^

Error: message needs to implement isReady or be an emitter
    at new DependencyInitialiser ([eval]:49346:21)
    at _options.pluginTypes.forEach ([eval]:40894:27)
    at Array.forEach (native)
    at Deepstream._pluginInit ([eval]:40892:31)
    at Deepstream._transition ([eval]:40830:28)
    at DependencyInitialiser.loggerInitialiser.once ([eval]:40867:12)
    at DependencyInitialiser.g (events.js:292:16)
    at emitNone (events.js:86:13)
    at DependencyInitialiser.emit (events.js:185:7)
    at DependencyInitialiser._emitReady ([eval]:49439:10)

I have also tried using the node.js version of deepstream, after following that guide I get this issue.
     throw new Error(`Unknown option "${key}"`)
      ^

Error: Unknown option "messageConnector"
    at Deepstream.set (/home/rahil.shaikh/projects/deepstream-poc/node_modules/deepstream.io/src/deepstream.io.js:89:13)
    at Object.<anonymous> (/home/rahil.shaikh/projects/deepstream-poc/server.js:16:8)
    at Module._compile (module.js:643:30)
    at Object.Module._extensions..js (module.js:654:10)
    at Module.load (module.js:556:32)
    at tryModuleLoad (module.js:499:12)
    at Function.Module._load (module.js:491:3)
    at Function.Module.runMain (module.js:684:10)
    at startup (bootstrap_node.js:187:16)
    at bootstrap_node.js:608:3

If this is a problem with v3.* and there is any other kafka connector which works with this do let me know.

Hey, message connectors are no longer supported since version 3.0. If you would like a Kafka connector I would recommend you write a backend client that maps deepstream events/records to kafka events.


feat: Support OTel 0.25

Note that https://github.com/open-telemetry/opentelemetry-rust/pull/2040 removed custom writer support from opentelemetry-stdout, so I didn't add that to the tests. Not sure what its purpose is since it only uses std::io::sink() anyways?

Hi! Is this okay to be merged and released soon?

Added support for 0.26 as well, now

Ping @eopb 🙂

Thanks for merging! Any chance for a release as well? 😀


fix crash when __NSCFNumber' is force casted to 'NSString'

force casting to desired type causes crash sometimes

Thanks for this. Do you know what attribute was a different type than expected? Was it called from AXSwift itself or your code? I'd like AXSwift to be a reflection of everything the AX API actually does, so maybe something needs updating.
One reason for the assert is that there are so many layers of optionals, and I want to be able to distinguish "this attribute doesn't exist" from "it wasn't the expected type". So maybe the proper way of doing this is to add another API, without an expected type, and let the user cast it themselves.

Yes, it was an AXValue attribute. In the project where I use AXSwift we track all user-typed text within every app. Sometimes getting string value from the focused element crashes because of casting it to string.
I think it's better to use optional conversion in this case because the returned value is still optional. Thanks for this framework!

Any chance to merge this fix?

@intrigua sorry for the delay. Actually, I re-read the comments and the instructions for dealing with this are in this warning:
     /// - warning: This method force-casts the attribute to the desired type, which will abort if
     ///            the cast fails. If you want to check the return type, ask for Any.

So if you are unsure of the type of an attribute, use attribute<Any>(), and then you'll be able to use a case expression to match the type. This also allows you to differentiate the case of an attribute not existing.
I think crashing the program may be a little extreme for an error in this case, but I also don't want to overload the meaning of a nil return value. I've opened issue #7 with more details on the possibilities, but in short, I'm leaning towards throwing a custom error type.

Ok, thanks for the details. I will switch to Any then. But I still think that force unwrapping before returning optional is a redundant risk of crash.


feat: Add pre-commit hook for lint

Is pre-push needed, as pre-commit is there already?

Is pre-push needed, as pre-commit is there already?

Not every push is preceded by commit, for example when you merge your local fork with upstream when branches are inter-merged when a release tag is made from cli, when a new branch is made from cli and pushed and more other events, so for these actions, a pre-push is defined/

@kushthedude will you present this at the Dev meeting on Wednesday as small bit of training for all on what to expect and what to do when a pre-comment issue rears up?

Sure thing Sir 🚀


{Container monitoring} -Changes for container monitoring to support USNat and USSec

Description -
Changes for container monitoring for USNat and USSec.

/assign MyronFanQiu

acs

add to S172

hi @fengzhou-msft could you pls look at this PR, how to cooperate it into cloud endpoint discovery? thanks.

@arrownj - Could you please take a look at this PR and approve?


fix: redis issue

Description
This PR fixes the issue of persistence of Redis configuration.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[ ] Bug fix

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist

[ ] My commit message is conventional
[ ] I have run pre-commit on all files before creating the PR
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I have checked my code and corrected any misspellings

Codecov Report

Merging #627 (6c8fc91) into develop (72a7d7c) will increase coverage by 0.02%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           develop     #627      +/-   ##
===========================================
+ Coverage    86.72%   86.74%   +0.02%
===========================================
  Files           24       24
  Lines         1589     1592       +3
===========================================
+ Hits          1378     1381       +3
  Misses         211      211

Impacted Files
Coverage Δ

splunk_connect_for_snmp/customtaskmanager.py
95.91% <100.00%> (+0.26%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Add option to sort releases by chart name

Fixes #4321
Changes

Helm changes to include --chart-name option to list command (The option can be changed based on feedback)
Tiller changes to accept the flag in the request and sort the releases accordingly.

@aswinkarthik Can you take a look at #4340 and let us know if that is the same implementation? If it is, we'll probably use the first PR that was submitted.


Discussion: Hardened kernel flags

This is the Nixpkgs part to a13xp0p0v/kconfig-hardened-check#27.
Quick summary:
We have a standard kernel (linux_latest and versioned friends) as well as a hardened kernel (linux_latest_hardened and versioned friends). (and some special cases but let's ignore those for the moment).
What I would like this issue to be is a discussion about the flags tested for in @a13xp0p0v's tool.
He has shown willingness to help us out, so we should take advantage of this opportunity and review what we currently have.
Our standard kernel options can be found here:
https://github.com/NixOS/nixpkgs/blob/master/pkgs/os-specific/linux/kernel/common-config.nix
The hardened kernel config is applied on top of the above:
https://github.com/NixOS/nixpkgs/blob/master/pkgs/os-specific/linux/kernel/hardened-config.nix
I am trying to think of potentially interested parties, pardon my ping if this does not concern you (unsubscribe from this issue on the right):
@joachifm @fpletz @Ericson2314 @Mic92

Hello!
The kconfig-hardened-check tool provides some hardening recommendations for your kernel config.
You can learn the relationships between these hardening options and vulnerability classes / exploitation techniques using the Linux Kernel Defence Map. Your questions and feedback is welcome.
I've also examined your nixpkgs script and took some ideas from it:
https://github.com/a13xp0p0v/kconfig-hardened-check/commit/5c67369249f22690efe4c96c54ef6b0bd0496c13
Thanks!

I'm definitely interested in this; has there been any progress?

I think this is still relevant.

As a result of #90065 we should actually be able to fix some of the flags :)

Established a comparison between NixOs 5.18 (latest) kernel and  Alpine Edge, Fedora 34, and Debian Buster based on the kconfig-hardened-check tool
Here are the results:
comparison.txt
I suggest we can start considering the commonly properly-configured security options, (at the end of the file).
Another configuration option that is not properly set and could be considered is the CONFIG_GCC_PLUGIN_STACKLEAK,
Also :
DEFAULT_MMAP_MIN_ADDR set to 65536
As to the NixOs (5.17) hardened, this is the comparison with Archlinux's hardened kernel:
hardenedcomp.txt.
Currently compiling the 5.18 kernel with some of these options.
Getting NixOS's kernel configs : a13xp0p0v/kconfig-hardened-check#64

cc @Ma27 @alyssais @TredwellGit


Health check stays on initialising

Rancher Version:
1.2.1
Docker Version:
1.12.3
OS and where are the hosts located? (cloud, bare metal, etc):
rancheros (vm)
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)
2 master in HA, external database, 2 agents.
masters behind nginx proxy, setup copied from here: http://docs.rancher.com/rancher/v1.2/en/installing-rancher/installing-server/basic-ssl-config/ (Only difference is that nginx runs on a separate server)
Network:

Note: when directing the agents directly to the internal ip addresses of a master they work as expected.
Environment Type: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
Steps to Reproduce:
Setup ranger according to documentation
Results:
scheduler and health check infrastructure stacks are stuck in Initialising.
Sometimes the scheduler and 1 health check manage to finish, but others are stuck for ever.
Expected:
They should not be stuck
// Edit some logs of the healthcheck

12/19/2016 8:19:32 PMtime="2016-12-19T19:19:32Z" level=info msg="Monitoring 2 backends"
12/19/2016 8:19:34 PMtime="2016-12-19T19:19:34Z" level=info msg="977ece20-f208-4337-bfed-beba012c6aeb_e3c0529c-1392-4074-b02d-7a596dba947e_2=DOWN"
12/19/2016 8:19:34 PMtime="2016-12-19T19:19:34Z" level=info msg="977ece20-f208-4337-bfed-beba012c6aeb_49312f91-179f-4b8e-9973-a307085b9e74_1=DOWN"
12/19/2016 8:19:35 PMtime="2016-12-19T19:19:35Z" level=info msg="Scheduling apply config"
12/19/2016 8:19:35 PMtime="2016-12-19T19:19:35Z" level=info msg="healthCheck -- no changes in haproxy config\n"
12/19/2016 8:19:46 PMtime="2016-12-19T19:19:46Z" level=info msg="Starting haproxy listener"
12/19/2016 8:19:46 PMtime="2016-12-19T19:19:46Z" level=info msg="healthCheck -- starting haproxy\n[WARNING] 353/191946 (18) : config : 'option forwardfor' ignored for proxy 'web' as it requires HTTP mode.\n[WARNING] 353/191946 (18) : config : 'option forwardfor' ignored for backend 'cattle-977ece20-f208-4337-bfed-beba012c6aeb_49312f91-179f-4b8e-9973-a307085b9e74_1' as it requires HTTP mode.\n"
12/19/2016 8:19:46 PMtime="2016-12-19T19:19:46Z" level=info msg="Scheduling apply config"
12/19/2016 8:19:46 PMtime="2016-12-19T19:19:46Z" level=info msg="healthCheck -- no changes in haproxy config\n"
12/19/2016 8:19:48 PMtime="2016-12-19T19:19:48Z" level=info msg="977ece20-f208-4337-bfed-beba012c6aeb_e3c0529c-1392-4074-b02d-7a596dba947e_2=DOWN"
12/19/2016 8:19:48 PMtime="2016-12-19T19:19:48Z" level=info msg="Monitoring 2 backends"
12/19/2016 8:19:50 PMtime="2016-12-19T19:19:50Z" level=info msg="977ece20-f208-4337-bfed-beba012c6aeb_49312f91-179f-4b8e-9973-a307085b9e74_1=DOWN"
12/19/2016 8:19:51 PMtime="2016-12-19T19:19:51Z" level=info msg="Scheduling apply config"
12/19/2016 8:19:51 PMtime="2016-12-19T19:19:51Z" level=info msg="healthCheck -- no changes in haproxy config\n"
12/19/2016 8:20:11 PMtime="2016-12-19T19:20:11Z" level=info msg="Scheduling apply config"
12/19/2016 8:20:11 PMtime="2016-12-19T19:20:11Z" level=info msg="healthCheck -- reloading haproxy config with the new config changes\n[WARNING] 353/192011 (31) : config : 'option forwardfor' ignored for proxy 'web' as it requires HTTP mode.\n[WARNING] 353/192011 (31) : config : 'option forwardfor' ignored for backend 'cattle-977ece20-f208-4337-bfed-beba012c6aeb_ea8bc3df-de01-4bcb-a70a-ae0b7c8dea1f_1' as it requires HTTP mode.\n"
12/19/2016 8:20:14 PMtime="2016-12-19T19:20:14Z" level=info msg="977ece20-f208-4337-bfed-beba012c6aeb_ea8bc3df-de01-4bcb-a70a-ae0b7c8dea1f_1=DOWN"

Update:
Deactivating all hosts but 1, then deleting the scheduler and the healthchecks. This will restart the containers on the last "healthy" host, scheduler will start normally, so does the healthcheck on that host.
Then activating a second host, will schedule the healthcheck there as well, but it will never get out of initialising.

just noticed something (not sure if its part of the same issue), all nodes seem to add them selfs with the gateway address instead of there actual IP address.

I've tried the same, re-adding hosts etc.  The wierd thing is, there are no error logs of any kind indicating there is an issue.  Sigh.

@jclark360 I have just been adding stacks, everything seems to be working normally (except all links in the rancher ui link to the wrong ip).

@jclark360 @matthijsvdr can you check the logs of containers and sidekicks of network-manager and ipsec?

@leodotcloud if you want, I can get you into our environment to take a look.

@leodotcloud Here are some logs, if you need more I could give you access to rancher server
Networkmanager
level=info msg="Setting up resolv.conf for ContainerId [f7a662cc8be1173c2f7c8cae6d7b267caba6aeb2c33e957e134a5753cf027524]"
level=info msg="Setting up resolv.conf for ContainerId [242c328625866b29abaae6e9c6385b2d56d508ea67d1ce5c74eed9fc68ab005e]"
level=info msg="CNI up" cid=f7a662cc8be1173c2f7c8cae6d7b267caba6aeb2c33e957e134a5753cf027524 networkMode=ipsec
level=info msg="CNI up" cid=242c328625866b29abaae6e9c6385b2d56d508ea67d1ce5c74eed9fc68ab005e networkMode=ipsec
level=info msg="Setting up resolv.conf for ContainerId [1cf2ae0cc970f856f99f9113139e22677ee7c14428b1ce04d238b0908f1b5150]"
level=info msg="Setting up resolv.conf for ContainerId [43492dca4094c6146663180feaa02b36022ed08990fce626914533e6386b085b]"
tch by that name.
tch by that name.
level=error msg="Failed to evaluate network state for 242c328625866b29abaae6e9c6385b2d56d508ea67d1ce5c74eed9fc68ab005e: Bringing up networking: failed to set bridge IP: failed to add IP addr to "docker0": file exists"
level=error msg="Error processing event &docker.APIEvents{Action:"", Type:"", Actor:docker.APIActor{ID:"", Attributes:map[string]string(nil)}, Status:"start", ID:"242c328625866b29abaae6e9c6385b2d56d508ea67d1ce5c74eed9fc68ab005e", From:"-simulated-", Time:0, TimeNano:0}. Error: Bringing up networking: failed to set bridge IP: failed to add IP addr to "docker0": file exists"
level=info msg="CNI up done" cid=65c4f7e864f8f436b0bbafe8cb35ca3ed6828eb2ed4df703db655a217d4e0a34 networkMode=ipsec result=IP4:{IP:{IP:<IP_ADDRESS> Mask:ffff0000} Gateway:<IP_ADDRESS> Routes:[{Dst:{IP:<IP_ADDRESS> Mask:ffffffff} GW:} {Dst:{IP:<IP_ADDRESS> Mask:00000000} GW:<IP_ADDRESS>}]}, DNS:{Nameservers:[] Domain: Search:[] Options:[]}
level=info msg="CNI up done" cid=f7a662cc8be1173c2f7c8cae6d7b267caba6aeb2c33e957e134a5753cf027524 networkMode=ipsec result=IP4:{IP:{IP:<IP_ADDRESS> Mask:ffff0000} Gateway:<IP_ADDRESS> Routes:[{Dst:{IP:<IP_ADDRESS> Mask:ffffffff} GW:} {Dst:{IP:<IP_ADDRESS> Mask:00000000} GW:<IP_ADDRESS>}]}, DNS:{Nameservers:[] Domain: Search:[] Options:[]}
level=info msg="CNI up done" cid=cd73d45212ec2115fa83f14d4177d5651cfe1124ddb9d264d24689bbde94f917 networkMode=ipsec result=IP4:{IP:{IP:<IP_ADDRESS> Mask:ffff0000} Gateway:<IP_ADDRESS> Routes:[{Dst:{IP:<IP_ADDRESS> Mask:ffffffff} GW:} {Dst:{IP:<IP_ADDRESS> Mask:00000000} GW:<IP_ADDRESS>}]}, DNS:{Nameservers:[] Domain: Search:[] Options:[]}
level=info msg="Evaluating state from retry" cid=242c328625866b29abaae6e9c6385b2d56d508ea67d1ce5c74eed9fc68ab005e
level=info msg="CNI up" cid=242c328625866b29abaae6e9c6385b2d56d508ea67d1ce5c74eed9fc68ab005e networkMode=ipsec
level=info msg="CNI up done" cid=242c328625866b29abaae6e9c6385b2d56d508ea67d1ce5c74eed9fc68ab005e networkMode=ipsec result=IP4:{IP:{IP:<IP_ADDRESS> Mask:ffff0000} Gateway:<IP_ADDRESS> Routes:[{Dst:{IP:<IP_ADDRESS> Mask:ffffffff} GW:} {Dst:{IP:<IP_ADDRESS> Mask:00000000} GW:<IP_ADDRESS>}]}, DNS:{Nameservers:[] Domain: Search:[] Options:[]}
level=info msg="Applying new port rules"
tch by that name.
level=info msg="Applying new port rules"
tch by that name.
level=info msg="Setting up resolv.conf for ContainerId [47460b1551689e751105c54bca3ced261d6dc389deb62811441618407cfaa32c]"
level=info msg="CNI up" cid=47460b1551689e751105c54bca3ced261d6dc389deb62811441618407cfaa32c networkMode=ipsec
level=info msg="CNI up done" cid=47460b1551689e751105c54bca3ced261d6dc389deb62811441618407cfaa32c networkMode=ipsec result=IP4:{IP:{IP:<IP_ADDRESS> Mask:ffff0000} Gateway:<IP_ADDRESS> Routes:[{Dst:{IP:<IP_ADDRESS> Mask:ffffffff} GW:} {Dst:{IP:<IP_ADDRESS> Mask:00000000} GW:<IP_ADDRESS>}]}, DNS:{Nameservers:[] Domain: Search:[] Options:[]}
level=info msg="Setting up resolv.conf for ContainerId [2daec190892ab95e8de14f1aa31de9310dd81ec9d14e85476389e7f65875f103]"
level=info msg="CNI up" cid=2daec190892ab95e8de14f1aa31de9310dd81ec9d14e85476389e7f65875f103 networkMode=ipsec
level=info msg="CNI up done" cid=2daec190892ab95e8de14f1aa31de9310dd81ec9d14e85476389e7f65875f103 networkMode=ipsec result=IP4:{IP:{IP:<IP_ADDRESS> Mask:ffff0000} Gateway:<IP_ADDRESS> Routes:[{Dst:{IP:<IP_ADDRESS> Mask:ffffffff} GW:} {Dst:{IP:<IP_ADDRESS> Mask:00000000} GW:<IP_ADDRESS>}]}, DNS:{Nameservers:[] Domain: Search:[] Options:[]}
level=info msg="Applying new port rules"
level=info msg="CNI down" cid=f7a662cc8be1173c2f7c8cae6d7b267caba6aeb2c33e957e134a5753cf027524 networkMode=ipsec
level=info msg="Applying new port rules"
level=info msg="Setting up resolv.conf for ContainerId [f7a662cc8be1173c2f7c8cae6d7b267caba6aeb2c33e957e134a5753cf027524]"
level=info msg="CNI up" cid=f7a662cc8be1173c2f7c8cae6d7b267caba6aeb2c33e957e134a5753cf027524 networkMode=ipsec
level=info msg="CNI up done" cid=f7a662cc8be1173c2f7c8cae6d7b267caba6aeb2c33e957e134a5753cf027524 networkMode=ipsec result=IP4:{IP:{IP:<IP_ADDRESS> Mask:ffff0000} Gateway:<IP_ADDRESS> Routes:[{Dst:{IP:<IP_ADDRESS> Mask:ffffffff} GW:} {Dst:{IP:<IP_ADDRESS> Mask:00000000} GW:<IP_ADDRESS>}]}, DNS:{Nameservers:[] Domain: Search:[] Options:[]}
level=info msg="Applying new port rules"
level=info msg="Applying new port rules"
level=info msg="CNI down" cid=65c4f7e864f8f436b0bbafe8cb35ca3ed6828eb2ed4df703db655a217d4e0a34 networkMode=ipsec
level=info msg="Applying new port rules"
level=info msg="CNI down" cid=47460b1551689e751105c54bca3ced261d6dc389deb62811441618407cfaa32c networkMode=ipsec
level=info msg="CNI down" cid=cd73d45212ec2115fa83f14d4177d5651cfe1124ddb9d264d24689bbde94f917 networkMode=ipsec
ipsec-ipsec-cni-driver
level=info msg="rancher-cni-ipam: got ip: <IP_ADDRESS>"
level=info msg="rancher-cni-ipam: r: &types.Result{IP4:(*types.IPConfig)(0xc8200666c0), IP6:(*types.IPConfig)(nil), DNS:types.DNS{Nameservers:[]string(nil), Domain:"", Search:[]string(nil), Options:[]string(nil)}}"
level=info msg="rancher-cni-ipam: got ip: <IP_ADDRESS>"
level=info msg="rancher-cni-ipam: r: &types.Result{IP4:(*types.IPConfig)(0xc820106300), IP6:(*types.IPConfig)(nil), DNS:types.DNS{Nameservers:[]string(nil), Domain:"", Search:[]string(nil), Options:[]string(nil)}}"
level=info msg="rancher-cni-ipam: got ip: <IP_ADDRESS>"
level=info msg="rancher-cni-ipam: r: &types.Result{IP4:(*types.IPConfig)(0xc820010b40), IP6:(*types.IPConfig)(nil), DNS:types.DNS{Nameservers:[]string(nil), Domain:"", Search:[]string(nil), Options:[]string(nil)}}"
ipsec-ipsec
This one keeps spamming
level=debug msg="Local: <IP_ADDRESS>"
level=debug msg="Arp request for <IP_ADDRESS>"
level=debug msg="Local: <IP_ADDRESS>"
level=debug msg="Arp request for <IP_ADDRESS>"
level=debug msg="Local: <IP_ADDRESS>"
level=debug msg="Arp request for <IP_ADDRESS>"
level=debug msg="Local: <IP_ADDRESS>"
level=debug msg="Arp request for <IP_ADDRESS>"
level=debug msg="Local: <IP_ADDRESS>"
network-services-metadata
level=info msg="Downloaded in 607.303655ms"
level=info msg="Loading answers"
level=info msg="Loaded answers"
level=info msg="Applied https://EXTERNAL-URL-HERE/v1/configcontent/metadata-answers?version=2855-8c3c62a605f204e6726515e8122e1268"
level=info msg="Downloaded in 239.631797ms"
level=info msg="Loading answers"
level=info msg="Loaded answers"
level=info msg="Applied https://EXTERNAL-URL-HERE/v1/configcontent/metadata-answers?version=2855-8c3c62a605f204e6726515e8122e1268"
level=info msg="Downloaded in 85.629881ms"
level=info msg="Loading answers"
level=info msg="Loaded answers"
level=info msg="Applied https://EXTERNAL-URL-HERE/v1/configcontent/metadata-answers?version=2855-8c3c62a605f204e6726515e8122e1268"
network-services-metadata-dns
level=info msg="Reloading answers"
level=info msg="Reloaded answers"
level=info msg="Reloading answers"
level=info msg="Reloaded answers"
level=info msg="Reloading answers"
level=info msg="Reloaded answers"
level=info msg="Reloading answers"
level=info msg="Reloaded answers"
level=info msg="Reloading answers"
level=info msg="Reloaded answers"
scheduler
level=info msg="Adding resource pool [storageSize] with total 46641115 and used 0 for host 4431a763-0397-4ce4-8888-b4ec31056248"
level=info msg="Initializing event router" workerCount=100
level=info msg="Connection established"
level=info msg="Starting websocket pings"
level=info msg="Hit websocket pong timeout. Last websocket ping received at 2016-12-20 09:44:40.293806732 +0000 UTC. Closing connection."
level=warning msg="websocket closed: websocket: close sent"
level=error msg="Exiting scheduler with error: "
level=info msg="Listening for health checks on <IP_ADDRESS>:80/healthcheck"
level=info msg="Connecting to cattle event stream."
level=info msg="Subscribing to metadata changes."
level=info msg="Adding resource pool [instanceReservation] with total 1000000 and used 10 for host 977ece20-f208-4337-bfed-beba012c6aeb"
level=info msg="Adding resource pool [cpuReservation] with total 2000 and used 0 for host 977ece20-f208-4337-bfed-beba012c6aeb"
level=info msg="Adding resource pool [memoryReservation] with total<PHONE_NUMBER> and used 0 for host 977ece20-f208-4337-bfed-beba012c6aeb"
level=info msg="Adding resource pool [storageSize] with total 46633652 and used 0 for host 977ece20-f208-4337-bfed-beba012c6aeb"
level=info msg="Adding resource pool [instanceReservation] with total 1000000 and used 12 for host ec9e3ca9-1137-4ff6-b483-1c40b8268503"

I tried changing over from an elb to alb, deleted and re-added hosts, same thing scheduler and health check stuck.  Furthermore any load balancer created also is stuck initializing.

@matthijsvdr Can you please check your LB infront of the rancher/server? Please ALB instead of ELB. The hosts being registered with the same source IP address is a problem.
@jclark360 I am assuming your issue is resolved: https://github.com/rancher/rancher/issues/7132#issuecomment-268530775

@leodotcloud I'm not running on aws

@leodotcloud Been trying some things, when connecting directly to the rancher master -> no issues
When connecting via a nginx lb -> errors
When specifying CATTLE_AGENT_IP and connecting via the nginx lb -> no errors
Looks like rancher does not pickup the correct ip adres.

@matthijsvdr Rancher does a best effort in trying to pick up the IP address. If it is picked up incorrectly, then you would need to use CATTLE_AGENT_IP.

I solved my issue by using the CATTLE_AGENT_IP, so I guess this could be closed

Encountered the same issue on hosts in Digital Ocean with Rancher 1.3 and Agent 1.1.3.  Solution was to disable auto-IP detection by setting the CATTLE_AGENT_IP to the internal droplet IP address, not the external one (although, YMMV as setting it to the external host worked in other clusters).

Hi I'm having an issue like this...I have a rancher-server on a local server. What I'm trying to do is add my AWS host with his public IP but they can reach my local server only by VPN connection. (When I execute the command generated by the UI of Rancher to add a host the detected cattle agent IP is his IP of the VPN even when use the public IP of the host for cattle agent IP).
Every host has a OpenVPN client that is running on background providing a tun0 interface, I have a VPN server on AWS that allows connection between clients and redirect all the traffic through the VPN. Also my local server is connected to that VPN.
The AWS hosts get added but when the second host is added the health check stays on initializing and there is no connection between hosts. Any idea of what is happening? What I'm doing is wrong?


Add superagent

Added a library for really easy HTTP test assertions.

Thanks, but I'm gonna pass on this. I've used SuperTest before and it's API is just too magic. .expect() is way too overloaded and it makes it really hard to read the assertions. There are better HTTP assertion libs on npm.

@sindresorhus A part of your reasoning for declining #608:

I've used SuperTest before and it's API is just too magic. .expect() is way too overloaded and it makes it really hard to read the assertions

But supertest is still valuable just for wrapping an http server and sending requests.
E.g. there is the "Endpoint testing" recipe in ava docs which includes supertest but uses ava assertions.
Maybe it might still be added with a note about avoiding the builtin assertions?


Change behaviour of timing_response in plugin multi-stim-multi-response

Old behaviour: timing_response is measured from the start of the trial
New behaviour: timing_response is measured from the end of stimulus presentation
Why?
Ending a trial on a missing response before the end of stimulus presentation is not needed - in this case, one could just change the duration of stimulus presentation to achieve the same effect.
However, trials can consist of a different amount of stimuli - which results in different total trial lengths. Therefore setting a constant post stimulus presentation interval for response collection was not possible, so far.

I think this is a good idea.
If the change is made to this plugin, it should probably also be made to all of the other plugins which have a timing_response option defined.
I'm also wondering if the implementation would be better if the timeout was set when the last stimulus was cleared from the display, instead of at the start of the trial. There is bound to be some error in when the stimuli get cleared, and it should be more accurate to create the timeout function when the display is cleared instead of at the start using the pre-calculated trial length.

I totally agree with both! I will add some commits reflecting this!

For the categorize, single-stim and multi-stim-multi-response plugins, this was straight forward. For the single-audio plugin, it was not. If I am not mistaken, we would have to catch the event "audio playback finished" first and then add the timer accordingly.

With the "new"/current timeline features, this is not needed anymore. One could now easily set the timing_response parameter to a different value for each trial.


Proxies

Hi, how i can get proxies for use bot? New here.

There's a button to choose proxies

There's a button to choose proxies


Error executing with new VS Code update

It seems that the extension cannot run with the latest version of VSCode that came out a few days ago

It seems that the extension cannot run with the latest version of VSCode that came out a few days ago

Hey,
I am running Vscode version 1.64 and everything seems to be working for me.
Do you get any error or warning or anything in the console that can help me understand the issue?

I am running v1.64 as well. Whenever I run it, it says "There was an error while running php-cs-fixer. Check the Developer Tools console for more information."
The Debug Console is empty

Sorry. I just found out the reason. Apparently my custom setting file was deleted when VSCode updated because I placed it in the same folder as VSCode!
Sorry to take up your time and keep up the good work!


feat(widget): add new alert widget

Depends on https://github.com/gisce/ooui/pull/114
Add a new widget based on Ant Alert
<alert colspan="6" alert_type="error" title="Atenció" text="Aquest és un impagador!"/>

Closes https://github.com/gisce/webclient/issues/1024

:tada: This PR is included in version 2.9.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

Vigent a la v2.4.2 :)


Error running plugin hook closeBundle for vite-plugin-pwa:build, expected a function hook.

App build fails with this error.

vite.config.ts
// ...
    build: {
      outDir: 'build',
      emptyOutDir: true,
    },
    plugins: [
      react(),
      svgrPlugin({ svgrOptions: { icon: true } }),
      tsconfigPaths(),
      VitePWA({
        devOptions: { enabled: !isBuild },
        registerType: 'autoUpdate',
        manifest,
        workbox,
        outDir: 'build',
      }),
    ],
// ...

yarn dev works fine, but dev-dist/sw.js only precaches index.html no other js,css files.
yarn build fails with above error. rest of the build works fine, bundles are generated but no sw.js gets generated in the build folder.

@RohitKaushal7 from version 0.13.0 you need Vite 3.1+

Thanks for quick reply. it works now. but now upgrading vite caused other errors related to

Cannot use import outside module in NodeGlobalsPolyfillPlugin
Identifier 'Buffer' has already been declared. etc..
but that's another problem I guess. 😢

@RohitKaushal7 you can try with v0.12.8 without upgrading Vite to 3.1+

I'm using vite 3.2.2 and vite-plugin-pwa 0.13.1 and I receive this exact error.
I just downgrade to 0.12.8 and did not receive any errors.

Uhmm, maybe Vite regression? Can you remove your node_modules folder and install deps again?

@fs it is weird, have you rollup as dep/devDep?
pnpm info vite

<EMAIL_ADDRESS>| MIT | deps: 5 | versions: 372
Native-ESM powered web dev build tool
https://github.com/vitejs/vite/tree/main/#readme

bin: vite

dist
.tarball: https://registry.npmjs.org/vite/-/vite-3.2.2.tgz
.shasum: 280762bfaf47bcea1d12698427331c0009ac7c1f
.integrity: sha512-pLrhatFFOWO9kS19bQ658CnRYzv0WLbsPih6R+iFeEEhDOuYgYCX2rztUViMz/uy/V8cLCJvLFeiOK7RJEzHcw==
.unpackedSize: 3.2 MB

dependencies:
esbuild: ^0.15.9 fsevents: ~2.3.2 postcss: ^8.4.18 resolve: ^1.22.1 rollup: ^2.79.1

and here my package.json:
{
  "name": "xxxxx",
  "version": "1.0.0",
  "type": "module",
  "private": true,
  "scripts": {
    "dev": "astro dev",
    "start": "astro dev",
    "build": "astro build",
    "build-dev": "astro build",
    "preview": "astro preview",
    "https": "npm run build && serve web-resources",
    "https2": "npm run build && esno server.ts",
    "https2-serve": "esno server.ts",
    "lint": "eslint .",
    "lint:fix": "eslint . --fix"
  },
  "dependencies": {
    "@unocss/reset": "^0.46.3",
    "astro": "^1.6.2"
  },
  "devDependencies": {
    "@antfu/eslint-config": "^0.27.0",
    "@iconify-json/el": "^1.1.2",
    "@iconify-json/fa-solid": "^1.1.2",
    "@iconify-json/grommet-icons": "^1.1.2",
    "@iconify-json/ion": "^1.1.4",
    "@iconify-json/mdi": "^1.1.33",
    "@iconify-json/si-glyph": "^1.1.3",
    "@iconify-json/topcoat": "^1.1.2",
    "@types/express": "^4.17.14",
    "@types/node": "^18.11.9",
    "@types/workbox-build": "^5.0.1",
    "eslint": "^8.24.0",
    "esno": "^0.16.3",
    "express": "^4.18.2",
    "https-localhost": "^4.7.1",
    "parse5": "^7.1.1",
    "postcss-nesting": "^10.2.0",
    "typescript": "^4.8.4",
    "unocss": "^0.45.26",
    "vite": "^3.2.2",
    "vite-plugin-compression": "^0.5.1",
    "vite-plugin-pwa": "^0.13.1",
    "vite-plugin-sitemap": "^0.3.0",
    "workbox-window": "^6.5.4"
  }
}

@fs rollup 2.74.1, we need 2.79.1+ for sequential hooks


Migrate to PackageReference and clean up projects

This PR solves issue #48 by

Migrating to PackageReference approach for remaining projects and
Remove unnecessary dependencies.

There may be more clean up that can be performed, but this appears to make the consuming project able to build whild still performing the animations.

@kimbirkelund the nuspec file is also pulling all the packages within each platforms respective ../bin/release folders. This is incorrect and should only be pulling the plugin package itself i.e. FormsControls.Base, FormsControls.Base and FormsControls.Base.
<!-- Cross-platform .net standard reference assemblies -->
<file src="..\SourceCode\Lib\FormsControls.Base\bin\Release\netstandard2.0\*.dll" target="lib\netstandard2.0"/>

<!-- Android reference assemblies -->
<file src="..\SourceCode\Lib\FormsControls.Base\bin\Release\netstandard2.0\*.dll" target="lib\MonoAndroid10"/>
    <file src="..\SourceCode\Lib\FormsControls.Droid\bin\Release\*.dll" target="lib\MonoAndroid10"/>

<!-- iOS reference assemblies -->
<file src="..\SourceCode\Lib\FormsControls.Base\bin\Release\netstandard2.0\*.dll" target="lib\Xamarin.iOS10" />
<file src="..\SourceCode\Lib\FormsControls.Touch\bin\Release\*.dll" target="lib\Xamarin.iOS10" />

generates:

replaced as:
<!-- Cross-platform .net standard reference assemblies -->
<file src="..\SourceCode\Lib\FormsControls.Base\bin\Release\netstandard2.0\FormsControls.Base.dll" target="lib\netstandard2.0"/>

<!-- Android reference assemblies -->
<file src="..\SourceCode\Lib\FormsControls.Droid\bin\Release\FormsControls.Base.dll" target="lib\MonoAndroid10"/>
<file src="..\SourceCode\Lib\FormsControls.Droid\bin\Release\FormsControls.Droid.dll" target="lib\MonoAndroid10"/>

<!-- iOS reference assemblies -->
<file src="..\SourceCode\Lib\FormsControls.Touch\bin\Release\FormsControls.Base.dll" target="lib\Xamarin.iOS10" />
<file src="..\SourceCode\Lib\FormsControls.Touch\bin\Release\FormsControls.Touch.dll" target="lib\Xamarin.iOS10" />

generates:

The below handles the dependencies:
<dependencies>
        <dependency id="Xamarin.Forms" version="<IP_ADDRESS>8975" />
</dependencies>

I've updated the nuspec, but because PackageReferences are used instead of packages.config, the files from the dependencies aren't actually copied to the output directory at build time.
It is however cleaner this way. Personally I'd add the pdbs too, but I guess that is up to @AlexandrNikulin .

@kimbirkelund  Thanks! I will check it today and update nuget package

Great. Let me know if you need more input.

@kimbirkelund  Sure, thanks


useRxData doesn't support findByIds

I'm trying to query for a set of IDs with a query supplied to useRxData. Unfortunately, it doesn't seem to work. The type definitions don't appear to be compatible, as findByIds returns a Map<string, doc_type>. Thinking maybe the type definitions just needed to be updated, I typed the query constructor instance as any, but that didn't help. The query never resolves and isFetching is always true.

It seems that findOne() is the single exception among collection query functions that exposes a promise-based API, so it can't be used with useRxData which naturally expects a query object with a BehaviorSubject $ attached to it.
I will try to work on a patch for this soon.

Fixed in 4.0.2.


Using custom properties with adjusters results in Expected a color

I'm seeing an Expected a color error when trying to use custom properties with adjusters.
Example:
:root {
  --color: blue;
}

.test {
  color: color-mod(var(--color) shade(20%));
}

I'm using postcss-preset-env as well, so it's possible it's misconfigured or need to use transformVars with the color-mod feature.

Closing due to inactivity. I hope my previous response helped you. If not, feel free to respond at your convenience. 😄

Hi, I get a similar error ('Expected a color') when using color-mod:
This works:
/* test.css */
:root {
    --misty: #C8C8C8;
}
.test {
    color: color-mod(var(--misty));
}

But it does not work when omitting the root declaration, and instead using a postcss-custom-properties variable in postcss.config.js:
/* postcss.config.js */
module.exports = {
    plugins: {
        'postcss-import': {},
        'postcss-preset-env': {
            stage: 0
        },
        'postcss-custom-properties': {
            preserve: true,
            variables: {
                misty: '#C8C8C8'
            }
        }
    }
}

/* test.css */
.test {
    color: color-mod(var(--misty));   /* Gives error: 'Expected a color' */
}

:-(

@jonathantneal i'm having the same problem as @erikmoren, since i'm using variables in postcss-custom-properties config to inject custom properties. Is there any way to make it work with this plugin?
Thanks!

I'm also seeing this issue.

Ok, all setup with Webpack. Problem still exists as expected.
The custom property is resolved. I use it in the lines above:
&:focus {
    border: 1px solid var(--electric-blue);
    outline: 1px solid var(--electric-blue);
    background: color-mod(var(--electric-blue) blend(red 50%)) !important;
}

Both border and outline are --electric-blue and the correct color. But, the color-mod still fails with Expected a color. Here is the full error:
Uncaught Error: Module build failed (from ./node_modules/postcss-loader/src/index.js):
SyntaxError

(46:31) Expected a color

  44 |     &:focus {
  45 |         border: 1px solid var(--electric-blue);
> 46 |         background: color-mod(var(--electric-blue) blend(red 50%)) !important;
     |                               ^
  47 |         outline: 1px solid var(--electric-blue);
  48 |     }

    at eval (base.css?./node_modules/css-loader??ref--4-1!./node_modules/postcss-loader/src:1)
    at Object../node_modules/css-loader/index.js?!./node_modules/postcss-loader/src/index.js!./src/css/base.css (index.js:154)
    at __webpack_require__ (index.js:20)
    at eval (base.css:2)
    at Object../src/css/base.css (index.js:691)
    at __webpack_require__ (index.js:20)
    at eval (index.js:10)
    at Module../src/index.js (index.js:736)
    at __webpack_require__ (index.js:20)
    at eval (webpack:///multi_(:1313/webpack)-dev-server/client?:2:18)

I created a new repo and attempted to reproduce. I couldn't! These are the fun hard to track bugs. At least I know the plugin works fine.

Got it to work. No idea how. I cleaned the project, refactored, cleared cache, deleted node_modules and reinstalled. Now works :S

Now it's back in a different file lmfao! I don't understand, the new file with the problem is included immediately after the file with the working color-mod.

@jonathantneal
It happens when postcss-preset-env disables custom-properties plugin based on .browserslistrc file.
My browserslist config:
and_chr >= 49
chrome >= 49
edge >= 16
firefox >= 52
ios_saf >= 10.2
safari >= 10

Since each browser from the list supports custom properties, postcss doesn't handle them, and this error occures.

@Rendalf do you have a solution for this problem?

hello every one, how fix this problem?

@jbibla @huangyanxiong01 Postcss handles custom props and color-mod during compilation. So if you need to change custom props during runtime, you shouldn't use them in color-mod function. Also you can fix it by forcing plugin to handle custom css props, but you won't be able to change them in runtime.
Btw color-mod is deprecated spec, so I don't recommend to use it.


Why not on Official F-Droid Repo?

Hello @IzzySoft and Mr. Dev,
My i ask why isn't this Application available in the official F-droid Repository.
Thank you

Hi,
this is because I use prerelease Android dependencies when a new Android version is out and FDroid doesn't allow this until the dependency used is available in AOSP.
Hope that answers your question.

We could get around that if you'd use different tag names for those releases, and F-Droid thus could stick to the "available" ones. E.g. you could have fdroid-<versionName> tags for those not using prerelease things, or predep-<versionName> for those F-Droid must skip (these names are just examples).


Added automatic ECDH selection to ssl context

With default setup Windows enables only ephemeral versions of the elliptic curve cipher suites.
https://msdn.microsoft.com/en-us/library/windows/desktop/mt767769(v=vs.85).aspx . With current ssl context configuration this causes ssl handshake failure if such suite is used.
Proposed modification enables automatic selection of appropriate curve
https://www.openssl.org/docs/man1.0.2/ssl/SSL_CTX_set_ecdh_auto.html
It should be noted that modification requires openssl 1.0.2 or above.

Do you know whether it is possible to detect if the function SSL_CTX_set_ecdh_auto is defined within the SSL headers, so that the call can be made conditional?    I just wonder whether this api will be available on other platforms, eg, linux , mac etc.

Router, for which I made this modification, is running on Linux, and the functionality is tested against C# client. Feature is available starting from openssl 1.0.2, which seems to be also available for Mac and Windows, see https://wiki.openssl.org/index.php/Binaries

Merged this change, and then add #ifdef check, so code should continue to compile when that function is not available.


Deployment question: keep getting a 'node bad option -r'

Trying to use https://www.netlify.com/ to deploy my react app but when it does the continous deployment and runs npm run compile I keep getting a strange error.  Was wondering if anyone had any insight as to why I might be getting this error and how to go about fixing it:

I think I may have figured it out... needed to supply a .nvmrc file so their build would use the proper node version.. Will post solution once I confirm I can fix it so maybe future people can use same deploy strategy

I'd need to look at the docs, but my instinct tells me that node -r (the preload flag) is only supported in more recent versions of node.
See: http://blog.modulus.io/fun-with-iojs-6-new-features

Oh yeah sorry I got further along with this.  I had to provide a .nvmrc file in order for it to use node v5.1.0.  I also needed to make sure that the global NODE_ENV was set to development so it would npm install dev depdendencies which are required for the npm run compile script.  I passed a flag of NODE_ENV=production to the npm run compile in order to run it in production mode (and get all the production benefits).  Only problem I'm having now is that it runs fine in development with that flag (some warnings pop up though) and it seems the warnings kill the deploy process for Netlify.

Here are the error sthe build gets.

If you have any recommendations on how to make it not bork on the compile errors that would be much appreciated.
Would be cool to get the automatic deployment working when merged into master though!
I'm guessing it could be due to the uglifying/css bundling of external node_modules like bootstrap.  If there is any other info I can provide let me know!

Are you getting that error with npm run deploy or npm run compile?

Original issue has been solved, if you are still having issues with your CI I'd be happy to accept a new issue :)

Sweet thanks man, I'll let you know.  For now I'm just running the deploy script locally and I added the netlify command line deploy to the end of it.  Not too concerned about continous deployment although it would be cool.
Do you think having a 'Deployment Guide' using netlify (since it's free like heroku) would be beneficial for the starter kit??  If so, when I get some time I an submit a PR


DEPRECATION WARNING: Non-URL-safe CSRF tokens are deprecated.

What Ruby, Rails and RSpec versions are you using?
Ruby version: 3.0.2p107 (2021-07-07 revision 0db68f0233) [arm64-darwin20]
Rails version: <IP_ADDRESS>
RSpec version:

RSpec 3.11

rspec-core 3.11.0
rspec-expectations 3.11.0
rspec-mocks 3.11.0
rspec-rails 5.1.0
rspec-support 3.11.0

Observed behaviour
When running bundle exec rspec I get the following deprecation warning:
DEPRECATION WARNING: Non-URL-safe CSRF tokens are deprecated. Use 6.1 defaults or above. (called from <top (required)> at /Users/hashimgari/Codebases/heritage-calendarize/spec/rails_helper.rb:8)

Line 8 of rails_helper.rb is require 'rspec/rails'

Expected behaviour
No deprecation warning?

Can you provide an example app?
None at the moment.

What is there on line 8?

Are you certain that this option is correctly set for the test environment?

Thanks all. It was a configuration issue. I just updated to Rails 7 and forgot to change the config.load_defaults.