juliaup does not install/alias julia as expected by the juliaup README

Solution to issue cannot be found in the documentation.

[X] I checked the documentation.

Issue
When installing juliaup, I have juliaup and julialauncher installed. From the video linked in #17, it seems that julia is actually an alias for julialauncher, but this isn't obvious from unless you watch that particular video.
Installed packages
N/A

Environment info
N/A

From the README at https://github.com/JuliaLang/juliaup/blob/main/README.md it seems the way to install is via a shell script rather than using cargo --install
curl -fsSL https://install.julialang.org | sh

Here is a link the shell script in the repository.
https://github.com/JuliaLang/juliaup/blob/main/deploy/shellscript/juliaup-init.sh
Here's a larger question. If this package and the julia-feedstock are both installed, how do we deconflict the situation?

This appears to be resolved, at least in more recent versions of the feedstock. (When I've installed juliaup from conda-forge, I correctly get a julia program (and julialauncher is nowhere to be found).
I'll leave it open until maintainers see this, but feel free to close, I think. 🙂

Are you sure? I just checked and this has not changed.

Also, I think the actual solution to this is to create an alternate install of the julia package that uses juliaup to install julia.


Allow to suppress testng checks

Allow to suppress testng checks

though I have doubts if this ReportUnannotatedMethods does not give more pain than benefit.

It is painful. But it provides benefits too. Imagine that we used to have test method without @Test annotation (false test coverage impression). Now it is not possible.

though I have doubts if this ReportUnannotatedMethods does not give more pain than benefit.

It is painful. But it provides benefits too. Imagine that we used to have test method without @Test annotation (false test coverage impression). Now it is not possible.

Yeah - I know what it does. Yet the same argument works for unit/integration tests. And we do not have mechanism there. And we assume we are good.

Yet the same argument works for unit/integration tests. And we do not have mechanism there.

This works for all tests, unit and product tests.

Yet the same argument works for unit/integration tests. And we do not have mechanism there.

This works for all tests, unit and product tests.

Oh. Good to know. I though it is only enabled for PTs.


Fix headers included in max_age_filter.c

No significant performance differences

Known issues:
Basic Tests Linux: #10180
Basic Tests Mac: #9727
Portability Tests Linux: #9726


Shibb dev

*********************  WORK IN PROGRESS **************************************

@JuliusGruber please delete this PR if is a duplicate of #429

Closing in favor of #429 (which is the latest Shib PR)


Ground state cost function

A quick question about steps/optimize_test.py. I definitely would like to keep these unittests and continue to write them in the future as it helps significantly with development and they could also become acceptance tests, however, I am worried that leaving them inside steps will bloat the directory. Does anyone have suggestions/thoughts on these kinds of files moving forward?

A quick question about steps/optimize_test.py. I definitely would like to keep these unittests and continue to write them in the future as it helps significantly with development and they could also become acceptance tests, however, I am worried that leaving them inside steps will bloat the directory. Does anyone have suggestions/thoughts on these kinds of files moving forward?


How to set connection deadline?

Please read the instruction and answer the following questions before submitting your issue. Thank you.
Please answer all the questions with enough information. All issues not following this template will be closed immediately.
If you are not sure if your question is truely a bug in V2Ray, please discuss it here first.

What version of V2Ray are you using (If you deploy different version on server and client, please explicitly point out)?
commit: 425ac88133e655ec509e976161323731c0011813

What's your scenario of using V2Ray? E.g., Watching YouTube videos in Chrome via Socks/VMess proxy.
Create a net.Conn from the Dial(ctx context.Context, v *Instance, dest net.Destination) (net.Conn, error) function, and use this Conn for TCP/UDP connections.

What did you see? (Please describe in detail, such as timeout, fake TLS certificate etc)
TCP connection is disconnected instantly or disconnected in a very short time.
e.g. Send lots of DNS queries to <IP_ADDRESS>:53 use TCP.

checked the source cord and found that the net.Conn from V2Ray did not implement the *Deadline methods.(https://github.com/v2ray/v2ray-core/blob/4b2ee1185dba234971925fdef2c0fa95d9e239dc/common/net/connection.go#L143)
BTW, the *core.Config generate the instance has add the policy settings.

What's your expectation?
How to set timeout?

Please attach your configuration file (Mask IP addresses before submit this issue).

Server configuration:
    // Please attach your server configuration here.

Client configuration:
    // Please attach your client configuration here.

Please attach error logs, especially the bottom lines if the file is large. Error log file is usually at /var/log/v2ray/error.log on Linux.

Server error log:
    // Please attach your server error log here.

Client error log:
    // Please attach your client error log here.

Please attach access log. Access log is usually at '/var/log/v2ray/access.log' on Linux.

    // Please attach your server access log here.

Other configurations (such as Nginx) and logs.

If V2Ray doesn't run, please attach output from --test.

The command is usually /usr/bin/v2ray/v2ray --test --config /etc/v2ray/config.json, but may vary according to your scenario.

If V2Ray service doesn't run, please attach journal log.

Usual command is journalctl -u v2ray.
Please review your issue before submitting.

Per offline discussion, please use Policy for timeout settings. SetDeadline on returned connection is an no-op.


Disable looseness/enable strictness in JavaScript files with checkJS/ts-check

With<EMAIL_ADDRESS>given the following index.ts file:
export const createModel = ({ name }) => ({
  name: String(name)
});

const m = createModel({name: 'some name'});
m.a = '';

shows an error for that m.a = '', because there is no a property in the returned object. It says that m is of type:
{
    name: string;
}

All right there.
But now I rename it to .js (and with jsconfig allowJs etc.) and gives no errors, because it says that m is of type:
{
    [x: string]: any;
    name: string;
}

That [x: string]: any; makes this less strict, and impossible to track bugs due to variable shapes. It's kind of useless this way and forces us to write the shape in JSDoc, losing type inference.
How can I do JS to be equally strict as TS in this little sample? I see this like an error, I expect that if for TS the return type has no [x: string]: any;, JS shouldn't, too.
keywords: JavaScript strict returntype index any

In that case, I would like to be able to configure that. It could be available for both JS and TS in the same way that noImplicitAny does, for example.
We work with a large repo for a webapp, made with JS and JSDoc, but wanted to take advantage of TS strictness.
We also try to avoid duplication, so because we already have model creators (functional way) like:
/** @typedef {ReturnType<typeof createModel> Model} */

export const createModel = ({name}) => ({name: String(name)});

We don't want to re-define the sape of the model with a JSDoc dedicated typedef, because we wuld have the same info both in JS code and in JSDoc.
But there comes the difference, where JSDoc explicit typedef with properties is stricter tan the infered return type of the model creator.
It would be really nice to have some compiler flag that enables us to work that strict way.

Update to the OP: In 3.1 we made it so that if you have noImplicitAny on, JS objects no longer gain an implied any index signature. So I think this is solved.


SyntaxError: Unexpected token in JSON at position 332

When I run the gg command, I am getting SYNTAX ERRORS: Unexpected token
My index.js from C:\Users\Christopher Wetmore\AppData\Roaming\npm\node_modules\giveaway-grabber/index.js :

My guess is you have invalid JSON in your .ggrc.json file. Open it up and copy it's contents into https://jsonlint.com/, which will help you figure out what's wrong.


Safari extension converter

Has anyone run the conversion tool for Safari?  https://developer.apple.com/documentation/safariservices/safari_web_extensions/converting_a_web_extension_for_safari/

@taogoddd Can you check and help with it?

Closed as no further updates. Please feel free to reopen as you need.


Make Compatible with Python 3.4 and Django 1.7

Attempted to maintain backwards compatibility but didn't test with old versions to confirm.


put image above title text ?

thanks for providing this lib. works well for us.
is it possible in a ButtonBarPagerTabStripViewController , to place an image above the title text ?
like this ?

@ajonno Hi, Add Example Youtube with Label.
Best Regards!


Add Magical status effect

Adds the Magical status to mark active effects as magical. Effects without the Magical status would be considered nonmagical.
We'll need to update all effects in compendium packs and add the Magical statuses where the effect is magical before merging this in. Perhaps even add migration that adds the Magical status to existing effects that originate from a spell or magical item.

Might be easier to just set a flag on the effect during the enchanting/effect grant process, rather than having to edit every effect in every piece of content.
Since every item can have the mgc property, that can be used to check whether this flag should be added.

The status effect has advantages over a flag:

The user can configure what active effects a magical and which are not via UI.
Whether a token is affected by magic can be tested efficiently by testing the actor's statuses, which is useful for detection modes like Detect Magic.

Also every spell effect being automatically magical is probably undesirable. A spell could have nonmagical effects: it could give you exhaustion or sever a limb for example.

The user can configure what active effects a magical and which are not via UI.

Adding it to the UI would be desirable, but non-magical effects are the exception not the norm, so perhaps a simple boolean property for nonmagical could be added. The result would be that only a small handful of effects would need to be amended, rather than who knows how many, across the system and every content module, for Detect Magic to work properly.


fix: JSON view should not attempt to draw links for glob paths

port of https://github.com/adobe/aem-sidekick/issues/215

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

GitHub release
v6.49.4

Your semantic-release bot :package::rocket:


Unexpectedly found nil while unwrapping an Optional value on dismissCoordinator

Found this in version 2.0
To replicate:

Launch Stinsen example app
Switch to TestBed tab
Tap on "Modal Screen"
Tap on "Dismiss me!"
Observe Unexpectedly found nil while unwrapping an Optional value

Ah... use modal coordinator does not cause the error, I guess that was there for an bad example. My bad...


adding bank account guide

Description

Creating a guide for collecting / using bank account information
Creating a guide for updating an existing application that uses Bank Data
Want to be able to add a Loom to this as well and a link to a "simple" loom as well.

Testing required outside of automated testing?

[ ] Not Applicable

Screenshots (if appropriate):

Rollback / Rollforward Procedure

[ ] Roll Forward
[ ] Roll Back

Reviewer Checklist

[ ] Description of Change
[ ] Description of outside testing if applicable.
[ ] Description of Roll Forward / Backward Procedure
[ ] Documentation updated for Change

I know this still uses /decrypt for now. Once we get the new ways of doing this out, we can update this guide and sample to accomplish it the non-deprecate way.

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


Improve docstring examples

Codecov Report

Merging #516 into master will decrease coverage by 0.55%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #516      +/-   ##
==========================================
- Coverage   96.36%   95.81%   -0.55%
==========================================
  Files          37       37
  Lines       13347    13347
==========================================
- Hits        12861    12788      -73
- Misses        486      559      +73


Return Environment on stop.

This removes manual parsing of the response json in clients, when they want to know the state, for example.

@hsmade can you check and fix the test? When it passes I'll merge it...

Took me a bit of debugging. Which is fun because it just works when you run it using delve. But in the end the fix makes sense actually.  It now returns an object, so it needs some json from the API.


Import metrics error

@gerhc @draix @dekked  hi thanks for sharing this source code when i try to install pip install norfair[video]  # Adds several video helper features running on OpenCV
pip install norfair[metrics]  # Supports running MOT metrics evaluation
pip install norfair[metrics,video]  # Everything included
I i get the following error "ImportError: cannot import name 'metrics'"
Please let me knw what is the issue

Hi @abhigoku10
Can you show us what is the exact script you run to get the ImportError?
Does it happen if you pip uninstall norfair and then only run pip install norfair[metrics,video]?

Can you paste the output of a fresh pip install norfair[metrics,video]?

@dekked  i checked in multiple systems both on windows and linux yet i am getting the same error

Hi @abhigoku10, I am really trying to help you here, but if you don't paste what I asked for in my previous comment, there is not much else I can do.

@dekked  apologies for the difference in understanding please find the output of the installation
Requirement already satisfied: norfair[metrics,video] in c:\python36\lib\site-packages (0.1.8)
WARNING: norfair 0.1.8 does not provide the extra 'metrics'
WARNING: norfair 0.1.8 does not provide the extra 'video'
Requirement already satisfied: filterpy<2.0.0,>=1.4.5 in c:\python36\lib\site-packages (from norfair[metrics,video]) (1.4.5)
Requirement already satisfied: rich<7.0.0,>=6.1.1 in c:\python36\lib\site-packages (from norfair[metrics,video]) (6.2.0)
Requirement already satisfied: opencv-python<5.0.0,>=3.2.0 in c:\users\ska10\appdata\roaming\python\python36\site-packages (from norfair[metrics,video]) (<IP_ADDRESS>)
Requirement already satisfied: scipy in c:\users\ska10\appdata\roaming\python\python36\site-packages (from filterpy<2.0.0,>=1.4.5->norfair[metrics,video]) (1.5.4)
Requirement already satisfied: numpy in c:\python36\lib\site-packages (from filterpy<2.0.0,>=1.4.5->norfair[metrics,video]) (1.19.5)
Requirement already satisfied: matplotlib in c:\python36\lib\site-packages (from filterpy<2.0.0,>=1.4.5->norfair[metrics,video]) (3.3.4)
Requirement already satisfied: typing-extensions<4.0.0,>=3.7.4 in c:\python36\lib\site-packages (from rich<7.0.0,>=6.1.1->norfair[metrics,video]) (<IP_ADDRESS>)
Requirement already satisfied: dataclasses<0.8,>=0.7 in c:\python36\lib\site-packages (from rich<7.0.0,>=6.1.1->norfair[metrics,video]) (0.7)
Requirement already satisfied: pygments<3.0.0,>=2.6.0 in c:\users\ska10\appdata\roaming\python\python36\site-packages (from rich<7.0.0,>=6.1.1->norfair[metrics,video]) (2.8.1)
Requirement already satisfied: colorama<0.5.0,>=0.4.0 in c:\users\ska10\appdata\roaming\python\python36\site-packages (from rich<7.0.0,>=6.1.1->norfair[metrics,video]) (0.4.4)
Requirement already satisfied: commonmark<0.10.0,>=0.9.0 in c:\python36\lib\site-packages (from rich<7.0.0,>=6.1.1->norfair[metrics,video]) (0.9.1)
Requirement already satisfied: pyparsing!=2.0.4,!=2.1.2,!=2.1.6,>=2.0.3 in c:\users\ska10\appdata\roaming\python\python36\site-packages (from matplotlib->filterpy<2.0.0,>=1.4.5->norfair[metrics,video]) (2.4.7)
Requirement already satisfied: python-dateutil>=2.1 in c:\users\ska10\appdata\roaming\python\python36\site-packages (from matplotlib->filterpy<2.0.0,>=1.4.5->norfair[metrics,video]) (2.8.1)
Requirement already satisfied: cycler>=0.10 in c:\python36\lib\site-packages (from matplotlib->filterpy<2.0.0,>=1.4.5->norfair[metrics,video]) (0.10.0)
Requirement already satisfied: kiwisolver>=1.0.1 in c:\python36\lib\site-packages (from matplotlib->filterpy<2.0.0,>=1.4.5->norfair[metrics,video]) (1.3.1)
Requirement already satisfied: pillow>=6.2.0 in c:\python36\lib\site-packages (from matplotlib->filterpy<2.0.0,>=1.4.5->norfair[metrics,video]) (8.1.2)
Requirement already satisfied: six in c:\python36\lib\site-packages (from cycler>=0.10->matplotlib->filterpy<2.0.0,>=1.4.5->norfair[metrics,video]) (1.15.0)
what i was able to find out is norfair==0.1.8 version is getting installed and the latest is 0.3.0 version

What happens is the latest version of Norfair doesn't support Python 3.6, only 3.7+.
Therefore, you are installing a previous version which does not have the "metrics" module.
You need to upgrade your Python installation or use a tool like Pyenv.


Is there a pytorch implementation?

as the title.

+1

no PyTorch implementation that I know off. Let me know if you find any repo that has a PyTorch implementation


request to highlight "bare" links

This is a feature request.  If somebody types a "bare" link in their markdown, such as
http://google.com

can we have it highlighted, even though it's not
[](http://google.com)

?  I think this is reasonable because this project is for GitHub Flavored Markdown, and in github a markdown file with a bare link will make the link clickable in the browser, just like a wrapped link.  (for example, http://google.com and wrapped.)
Thanks for the great plugin!
-Matt

A workaround is to enclose it in angle brackets: <https://example.com>


Custom webpack plugin config not being loaded by Storybook

Support request summary
I'm having an issue when trying to add a plugin like https://github.com/shaketbaby/directory-named-webpack-plugin, where it should be added as a config.resolve.plugin.
If I'm not mistaken, while looking at the code I saw that particulary configuration part isn't taken into account for the merged webpack config.
Steps to reproduce

Add custom webpack config file with Directory Named Webpack which requires to be in resolve section.
Storybook fails to load the Directory Plugin.

Please specify which version of Storybook and optionally any affected addons that you're running

@storybook/react 3.4.3
directory-named-webpack-plugin 4.0.0

Screenshots / Screencast / Code Snippets (Optional)
    resolve: {
      plugins: [
        new DirectoryNamedWebpackPlugin(),
      ],
    },

On full control mode the plugin is created but it fails (Inside my webpack config works fine), the log here:
``bash
C:...\node_modules\directory-named-webpack-plugin\index.js:23
var target = resolver.ensureHook("undescribed-raw-file");
^
TypeError: resolver.ensureHook is not a function
at module.exports.doApply (C:...\node_modules\directory-named-webpack-plugin\index.js:23:25)
at Resolver.apply (C:...\node_modules@storybook\core\node_modules\tapable\lib\Tapable.js:375:16)
at C:...\node_modules@storybook\core\node_modules\enhanced-resolve\lib\ResolverFactory.js:249:12
at Array.forEach ()
at Object.exports.createResolver (C:...\node_modules@storybook\core\node_modules\enhanced-resolve\lib\ResolverFactory.js:248:10)
at WebpackOptionsApply.process (C:...\node_modules@storybook\core\node_modules\webpack\lib\WebpackOptionsApply.js:283:47)
at webpack (C:...\node_modules@storybook\core\node_modules\webpack\lib\webpack.js:37:48)
at exports.default (C:...\node_modules@storybook\core\dist\server\middleware.js:29:40)
at buildDev (C:...\node_modules@storybook\core\dist\server\build-dev.js:163:36)
at Object. (C:...\node_modules@storybook\react\dist\server\index.js:23:22)
``

directory-named-webpack-plugin 4 is only compatible with Webpack 4.
Storybook uses webpack 3, and it breaks for that reason.
My solution was to install directory-named-webpack-plugin 2 for Storybook build only with Yarn alias while keeping my Webpack 4 config with DNWP 4, and works well.

Storybook 4.0.0 will be use webpack 4. There's an alpha you can try right now.
The full release should happen next month.

Storybook 4.0.0 will be use webpack 4. There's an alpha you can try right now.
The full release should happen next month.

Is there any update on when Webpack 4 support will be released? Your comment said next month but it's been almost 5 months now and it's still alpha.

@codeaid You're right, the update is we're aiming to release it next week.
Sorry my optimism got the better of me.


[Infrastructure][LocalNet] Investigate & determine if kubernetes / minikube should be used in place of docker-compose

Objective
As we continue to build V1 localnet, we should evaluate our tooling to ensure our deployment and management pipelines are scalable and easily configurable. Currently we use docker-compose, but this should be evaluated against options like Kubernetes/Minikube to identify what works best for our stack.
Origin Document
@olshansky?
Goals

[ ] Recommend a path forward for how we scale and configure localnet

Deliverables

[ ] Provide a 1-2 pager summarizing the tradeoffs between Minikube vs Kubernetes vs Docker Compose with a focus on:

[ ] Ease of use
[ ] Ease of comfortability
[ ] Time to completion/to code changes
[ ] Compatibility with Docker File

Non-goals / Non-deliverables

Implementing any new desired infrastructure tooling

General issue checklist

[ ] Update the appropriate CHANGELOG
[ ] Update the README
[ ] If applicable, update the source code tree explanation
[ ] If applicable, add or update a state, sequence or flowchart diagram using mermaid
[ ] Update any relevant global documentation & references
[ ] Document small issues / TODOs along the way

Creator: @jessicadaugherty
Co-Owners:

Per my comment in https://github.com/pokt-network/pocket/issues/298#issuecomment-1281763062, @okdas would this be mutually exclusive from k8s operators or is there a world where we use both minikube AND k8s operators?
I'm not familiar with the overlap of those two technologies, which is why I ask.


STORM-3118 fix netty buffer usage

My 2 cents, looks like summary of JIRA represents the issue and which we are addressing better than PR/commit title.

+1


Rename SDAM packages

I know I just merged SDAM packages, but in fact SDAM acronym only refers to Server Discovery and monitoring and besides it refers to a key part of the client, it's only a part.
SDAM -> Client should fit better

This is already done


Build the build info variables to its own library.

The libraries capture build information (git revision, compiler, compiler version, compiler flags), which is useful to record in benchmarks and some tests.  It made no sense to capture this information both in the Cloud Bigtable library and the Cloud Storage library.  So I created a common library to keep it.  The same library will be used for other things, like the throw delegate functions.

@houglum Can you take a look at this PR when you have a chance?  Thanks!


winget install julia -s msstore installed the wrong thing - certainly not the Julia we know and love!

I've used the command winget install julia -s msstore a few times successfully, but today on a new PC the command installed completely the wrong thing, namely an app called "Julian Date Selector".

Wow, that is bad! I can reproduce it, this must be a bug on the winget side of things. Thanks for reporting, I'm trying to follow up with the winget team to figure out what is going on.

https://github.com/microsoft/winget-cli/issues/2005

I wonder if the Author of "Julian Date Selector" has just seen a gratifying uptick in his download count!


hledger-utils: init at 1.11.0 (also init so far unpackaged dependencies)

Description of changes

This adds the following three python packages:

drawille at 0.1.0
drawilleplot at 0.1.0
hledger-utils at 1.10.0

Whereas the former have been added as dependencies for the latter.
hledger-utils has also been made available as an application at the top-level under the hledger-utils attribute, as it provides 2 executables that can be used as a hledger "plugin".
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

After the most recent rebase where I also had to change setuptools_scm to setuptools-scm I get a NumPy error in the nixpkgs-review shell, but not after a nix-build and running the same from the result-link. Though the stack trace also shows 2 python versions, therefore I think this is happening because of the leaking pythonpath in the review shell.

Result of nixpkgs-review pr 212407 run on aarch64-darwin 1

6 packages built:

hledger-utils (python310Packages.hledger-utils)
python310Packages.drawille
python310Packages.drawilleplot
python311Packages.drawille
python311Packages.drawilleplot
python311Packages.hledger-utils

Result of nixpkgs-review pr 212407 run on aarch64-linux 1

6 packages built:

hledger-utils (python310Packages.hledger-utils)
python310Packages.drawille
python310Packages.drawilleplot
python311Packages.drawille
python311Packages.drawilleplot
python311Packages.hledger-utils

Result of nixpkgs-review pr 212407 run on x86_64-darwin 1

6 packages failed to build:

hledger-utils (python310Packages.hledger-utils)
python310Packages.drawille
python310Packages.drawilleplot
python311Packages.drawille
python311Packages.drawilleplot
python311Packages.hledger-utils

@ofborg build hledger-utils python310Packages.drawille python310Packages.drawilleplot python311Packages.drawille python311Packages.drawilleplot python311Packages.hledger-utils

Please disable the check phases, when there are no tests.
drawille> running test
drawille> WARNING: Testing via this command is deprecated and will be removed in a future version. Users looking for a generic test entry point independent of test runner are encouraged to use tox.
drawille> running egg_info
drawille> writing drawille.egg-info/PKG-INFO
drawille> writing dependency_links to drawille.egg-info/dependency_links.txt
drawille> writing top-level names to drawille.egg-info/top_level.txt
drawille> reading manifest file 'drawille.egg-info/SOURCES.txt'
drawille> writing manifest file 'drawille.egg-info/SOURCES.txt'
drawille> running build_ext
drawille>
drawille> ----------------------------------------------------------------------
drawille> Ran 0 tests in 0.000s
drawille>
drawille> OK
```

@ofborg build python3.pkgs.hledger-utils
@ofborg build python311.pkgs.hledger-utils


Proper place to initiate a db connection

I am new to hapi and a node beginner. I installed the generator and have a skeleton api running. Where and how would i launch a db connection..?
my api structure looks like this...
server
--api
----models/
-------------/model1.js
------------/model2.js
thanks

Thanks for opening an issue. Take a look at some of the boilerplate apps: http://hapijs.com/resources#Boilerplates


fix: review hydration error

Why:
Closes: #ID
Describe your changes
Checklist before requesting a review

[ ] My code follows the code style of this project.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.
[ ] I've updated docs/changelog/changelog_en.md and docs/changelog/changelog_de.md. If I'm a non-German speaker, I've still updated the file with the English version as a placeholder.

Appreciate the effort, but I dont think thats necessary anymore, issue fixed here:
https://github.com/plentymarkets/plentyshop-pwa/pull/536/files#diff-59db589430edc0bf5ba303841a5acbc46a17a7b55ae981a5b5385b58785049f5


Development First PR for assignment

Thanks for the PR @ishitaguptabits but if you have a project you'd like to add please open an issue first!


Fix forbiddenapis causing travis failing

Description
Fixed the problem that the forbiddenapis plugin cannot recognize multiple versions after shade. Because the MoreExecutors#sameThreadExecutor()  method is not found in the project code, it cannot be solved from the code level. It can only be solved at the Maven level. Even the latest version 3.2 of the forbiddenapis plugin does not support this situation yet, so simply skip this check in the new extension first to quickly fix blocker issues.

This PR has:

[x] been self-reviewed.

[x] using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)

[x] added documentation for new or modified features or behaviors.
[x] added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
[x] added or updated version, license, or notice information in licenses.yaml
[x] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[x] added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
[x] added integration tests.
[x] been tested in a test Druid cluster.

This patch will rollback part of https://github.com/apache/druid/pull/12034, @xvrl any comments on this?

Thanks for making this PR. The change seems reasonable to me as a temporary workaround. We can figure out later how to resolve this issue without using the deprecated option.
[2022-01-15 05:49:23] [build-stdout] [2022-01-15 05:49:23] [autobuild] [ERROR] Failed to execute goal de.thetaphi:forbiddenapis:3.1:check (compile) on project opentelemetry-emitter: Parsing signatures failed: Method not found while parsing signature: com.google.common.util.concurrent.MoreExecutors#sameThreadExecutor() -> [Help 1]
[2022-01-15 05:49:23] [build-stdout] [2022-01-15 05:49:23] [autobuild] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal de.thetaphi:forbiddenapis:3.1:check (compile) on project opentelemetry-emitter: Parsing signatures failed: Method not found while parsing signature: com.google.common.util.concurrent.MoreExecutors#sameThreadExecutor()

LGTM failed with the same error. I'm not sure why it failed though as the patch works well in my machine. I retriggered LGTM.

Another strange thing is that Travis was not triggered for this PR. I checked the "Requests" history in Travis and found that you seem to not have the permission to run Travis jobs as seen in the screenshot. Apparently, the reason that Travis didn't run for this PR before also seems related to you not having permissions because Travis is running after I close and reopen this PR. Can you please check your permission with the ASF infra team first? This seems also a critical issue as Travis has not been running for not only the PRs you create but also the PRs you merged. Please fix your permission first before you merge any PRs.

Forgot to mention, thank you for creating labels that could be useful for classifying and searching for PRs. However, maven doesn't seem accurate for this PR because it's not really about maven, but CI.
Also, I think labels should be general enough because having a large number of labels does not help with either classifying PRs or searching for PRs. It will rather increase the maintenance cost for labels. I don't think I remember all labels we have today. If all those labels are legit and reasonable, then we should document them. However, I don't think all of them are worth to document because many of them are specialized for particular topics. For example, I see labels for "Apache Pulsar", "Apache Spark", "Apache RocketMQ", and "Apache Avatica". Do we really need all these labels? How many PRs have been being created for each topic? To me, they have a very narrow scope of topic.  "Apache Pulsar", "Apache Spark", and "Apache RocketMQ" can be just one label "extension" or "ecosystem". "Apache Avatica" should be "JDBC". This is why we have instructions documented for creating a new label on GitHub. These instructions explicitly say that you should be able to find at least 3 PRs that are relevant to the new label. This implies that the new label should be general enough to be applied to multiple PRs. The instructions also say that you have to update the doc for labels and announce the new label you created, so that other committers can be aware of the new label and what it is for. Please follow these instructions when you create a label.

LGTM is still failing after a couple of retriggers. As seen in the screenshot, it seems like it failed while building the master branch (the commit https://github.com/apache/druid/commit/d2ac14636535a2293171166dee4019e7210d69a8). The master branch build cannot pass until this PR is merged. So I'm going to merge this PR to unblock all other PRs. If LGTM is still unhappy even after this PR is merged, we can fix it in a follow-up PR.

Hi @jihoonson , thanks for your comments, and you are welcome. Yes, the LGTM seems unstable, and I tried to restart it and it seems not work. And after you merged this PR to master branch, the status of CI shows pending but actually the job of CI already completed successfully, which is odd, we can get the details from the log of the job of CI. However, I also passed the test locally, so the PR should be OK. The entire project shares the same Token instead of multi tokens for each one, so there should be no permission issues, right. In the long term, we can use Github Action to trigger instead to ensure the stability of the CI process. Anyway, I'll go check it out recently.

About the label part, I got your point, SGTM. However, I remember that the maven label was not created by me. If you think it is unsuitable, please feel free to delete it. In addition to labels you mentioned, there are Kubernetes and Helm labels. If they are too detailed, please also feel free to delete them.
BTW, this blocker problem caused by third-part maven plugin, so I just report this to the author of the forbiddenapis maven plugin. Hope we can get some answers soon.

After merging this PR, everything seems to be working fine. After about four hours, it finally went from the Pending state to the Success state. In fact, the task has already been successfully completed. 😂

LGTM seems unstable, and I tried to restart it and it seems not work.

It's not LGTM being unstable. LGTM was trying to run the forbidden API check against the master branch without your change in this PR which must fail. That's why it never passed. But now other PRs seem to be passing LGTM after this PR is merged which is expected. I'm not sure why LGTM was building the master branch though. Maybe we should fix the LGTM script or configuration.

However, I also passed the test locally, so the PR should be OK. The entire project shares the same Token instead of multi tokens for each one, so there should be no permission issues, right. In the long term, we can use Github Action to trigger instead to ensure the stability of the CI process. Anyway, I'll go check it out recently.

I'm not sure if you understand me correctly. I'm not talking about flaky tests. I'm talking about Travis not running for the PRs you create or the master branch after you merge a PR into it. This seems important as we don't want to skip relevant CI in Travis in any case after the master branch is updated. I'm not entirely sure what's the issue. I'm just guessing it could be a permission issue because that's what I see in Travis as seen in my previous comment. Please contact the ASF infra team as soon as possible and fix it first whatever the issue is before you merge any PRs.

About the label part, I got your point, SGTM. However, I remember that the maven label was not created by me. If you think it is unsuitable, please feel free to delete it. In addition to labels you mentioned, there are Kubernetes and Helm labels. If they are too detailed, please also feel free to delete them.

So, I don't know what you had in mind when you create those labels. My point is, please share your thought for those labels when you create them. And this is all what our instructions say too. For example, why do we need the "Kubernetes" label? I know it can be added to PRs that are related to k8s. My question is what is the use of this label? How do you use it? Your intention about this should be shared with other developers. This is also why I'm asking you to document those labels you created with your intention together. So, let me clarify my thought again here. I'm not saying "don't create labels". What I mean is, you can create whatever labels you want, but please share with other developers what label you created and how we can use it. If someone disagrees with you, then we can discuss. But we should first know why you created the label before we discuss.

Hi @jihoonson, thanks for your comment. I understand your point and will raise up an issues to describe the purpose of new label before creating it. Beside, I have created a Jira ticket to ASF infra team to take a look at it. BTW, the status of CI of the master branch is failed now, which was successful about 1 hour ago, which is weird. Any thoughts on this?

1 hour ago:

now:

Hi @jihoonson, the ASF infra team has resolved the permissions issue, thanks for your guidance :+1:

Hi,
my personal optinion here: From what I understand by default you use Guava 16.0 in your main dependecies. This one has the method still available (although deprecated after 18).
In opentelemetry-emitter you seem to use another more modern Guava version 30.1.1. So it can't parse the signatures file, because the class is available, but not the method.
I would cleanup by signatures file and put the Guava one in a separate file (or maybe inline it directly in the pom.xml on top-level scope). For https://github.com/apache/druid/blob/6a938725861f0cafbe97e5ff8c3417fe65405cca/extensions-contrib/opentelemetry-emitter/pom.xml, I'd change the forbiddenapis config to not use the extra guava signatures file, but for the default config in root pom use the signatures file.
Uwe (from forbiddenapis)

Or maybe update Guava at all, 16.0 is quite old? :-)

In Apache Lucene's Gradle build we have a separate signatures file for every external dependency. In the Gradle script that setups forbiddenapi we check the dependencies of the subproject and only add files based on their filename pattern (so it translates the dependency coordinates to signatures filename and includes it if found in the signatures folder): https://github.com/apache/lucene/blob/0b517573a469acadd97ce7327b2d708ef1ef79d8/gradle/validation/forbidden-apis.gradle#L30-L39; https://github.com/apache/lucene/blob/0b517573a469acadd97ce7327b2d708ef1ef79d8/gradle/validation/forbidden-apis.gradle#L73
Unfortunately with Maven this is not possible, I suspect. But maybe some automatism like this is possible.

Yeah, his suggestion sounds good to me. @uschindler are you interested in making a PR for this issue? :slightly_smiling_face:

Let me check it out, Maven is unfortunately very unflexible with inheriting plugin configs. In Gradle you can just "modify config" in a subproject, but I am not sure if this works with Maven, too.

Here is a PR fixing the issue, but to me it still feels like a hack (copypaste of a whole section of the plugin config): #12170


Introduce Pull Request Reviewers

Introduces a generated set of code owners to ensure a good contribution experience.
For more details/timelines (internal): go/codeowners

@lokesh-shekar, @domenicbove please take action to review and merge this pull request.
For more details/timelines see: go/codeowners
Note: This pull request and subsequent comments are automatically generated

@domenicbove, @lokesh-shekar please take action to review and merge this pull request.
For more details/timelines see: go/codeowners
Note: This pull request and subsequent comments are automatically generated


Update to .travis.yml

Updated without branches only in the .travis.yml file.

Merging with team-1 branch with default .travis.yml


Typo in your website

Describe the bug
Hey man I've been looking at your beautiful website, and I came across a typo
To Reproduce
Steps to reproduce the behavior:

Go to 'https://www.weibozhang.com/blog/now'
Scroll down to 'Working on Bluon AI'
You can see there is a typo there in the third list item

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots

Hey, thank you so much! I have made some changes to the page! I really appreciate your feedback!


Pathfinder 2 issues

Hello.
There are two issues I am experiencing:

Not compatible with "PF2e TokenMagic Integration" module, which disables walled templates when both are loaded (walls are ignored then).

Unfortunately I am not able to create PF2e compatible templates with Walled Templates. Different area settings fit different template shapes and sizes.

There also is the libwrapper conflict message when Walled Templates is run in combination with Token Magic FX with or without the PF2e integration module. So the
"libWrapper: Potential conflict detected between module Walled Templates and module Token Magic FX.
Module walledtemplates did not chain the wrapper for 'MeasuredTemplate.prototype.refresh'."

PF2e TokenMagic Integration does not use libWrapper, so there is not much I can do on my end to ensure compatibility. I am happy to try to coordinate with that author if I can.
I will close this for now, as I am not sure if your issue #2 is a separate issue or not. If it is separate, please feel free to add a comment with some details or screen shots of what you are seeing with template shapes and sizes. Thanks!


Changes repos to archive.apache.org

The download URL goes through the Apache mirror selection, which makes me wonder whether that build error wasn't a transient error. My concern with archive.apache.org is that you're apparently supposed to use it only as a last resort:

Do note that a daily limit of 5GB per IP is being enforced on archive.apache.org, to prevent abuse.

This could be a problem in itself for Docker's build nodes.

@barend you are right, I am closing the PR.


Small-scale code improvement in ImageFileLoader.kt

In ImageFileLoader.kt, merge into single condition: file != null && file.exists

Hi @nicolas-raoul I think this issue is solved through #5055 ? Is it correct ?

@bosankus You are right, thanks for spotting this! I will close it now.


Support generated columns

This PR adds generated column support.

Update cloud.google.com/go/spanner to parse generated columns.
Update loaders and default templates to not try to write values to generated columns. Generated columns are non-writable and writing values to them causes an error.

LGTM


docs(api): Update pyenv in CONTRIBUTING.md

Overview
pre-3.7.10 fail often. Just updating command to reflect.
Changelog
Review requests
Risk assessment
None

pre-3.7.10 fail often

This is surprising to me. What kind of failures are you seeing?
Should we keep this version in sync with what's on the robot?

pre-3.7.10 fail often

This is surprising to me. What kind of failures are you seeing?
Should we keep this version in sync with what's on the robot?

New hires using big sur have been running into this: https://github.com/pyenv/pyenv/issues/1737
Perhaps I'll just put a note about Big Sur


Bugfix #6

Default timezone is still Europe/Paris but it can be overridden with —build_arg CTRN_TZ


Update Microsoft-Teams.md index due to 404 on Powershell cmdlet reference

Updated page due to 404 on Powershell Cmdlet reference,
I think it should be going to the  Teams PowerShell Overview, which includes information on both teams and sfbo modules

Just realised this is also logged as an issue #1848

Yes, was down the end of last week, then there was an issue opened in PowerShell repo.. then it was fixed for all but Exchange. Now all these TOC references are down again. :(  I opened a case with the team that owns this and they are working on it now.

Should be fixed now.


remove pre-fill validation in deploy

What this PR does / why we need it: Reverting pre-autofill validation in deploy command that was introduced in PR #2771. The validation prevents usage of flags for properties such as --dns-prefix since it requires the properties to exist in the apimodel. The model will be validated after so there is no need to validate beforehand.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #3051 #2933
Special notes for your reviewer:
If applicable:

[ ] documentation
[ ] unit tests
[ ] tested backward compatibility (ie. deploy with previous version, upgrade with this branch)

Release note:

/assign @jackfrancis

/approve
/lgtm


feat: extend configuration arguments in facade functions

Make check_reaction_violations() work with a custom ParticleCollection, so that the user can pass in modified particles.
Add more spins and orbital angular momenta to the default list of quantum numbers to be tried when solving for a reaction.
The latter change comes, of course, with some penalty on the execution time.  It may therefore not be an appropriate default.
If we want to keep the shorter original list, then it might be a good idea to catch particles with higher spins somewhere,
tell the user to modify default_settings.py, and throw an exception.

Thanks for @wgradl for fixing this!
I think I will re-open an older PR that was rejected for the expertsystem earlier on, because that would automatically extend the ranges from the ParticleCollection that is provided, see
https://github.com/ComPWA/expertsystem/pull/486#issuecomment-775040377
I'll also take care of the failing tests

Upgrade workflow fails due to https://github.com/ComPWA/repo-maintenance/issues/14


remove client.address as default attribute on RPC metrics

Enabling this attribute by default could lead to thousands/millions of new series for public services with high number of clients.

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

Project coverage is 50.97%. Comparing base (84148fe) to head (a7ef662).

:exclamation:  There is a different number of reports uploaded between BASE (84148fe) and HEAD (a7ef662). Click for more details.
HEAD has 3 uploads less than BASE

Flag
BASE (84148fe)
HEAD (a7ef662)

oats-test
1
0

k8s-integration-test
1
0

integration-test
1
0

Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1022       +/-   ##
===========================================
- Coverage   81.64%   50.97%   -30.68%
===========================================
  Files         137      137
  Lines       10936    10935        -1
===========================================
- Hits         8929     5574     -3355
- Misses       1498     4980     +3482
+ Partials      509      381      -128

Flag
Coverage Δ

integration-test
?

k8s-integration-test
?

oats-test
?

unittests
50.97% <ø> (-0.04%)
:arrow_down:

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

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


When archiving, archive also all comments (made by others) and likes on your posts

The big downside of Facebook official archive feature is that they provide to you only your content. So when you make a post and others comment on it, you do not get those comments (and likes) saved.
This tool could be better and save in JSON also all comments you got on your posts, before deleting them.

+1, I think it should ultimately support both methods. Do a dump before running using the official tools, then archive everything that gets removed as it runs.
It could even take screen captures as well (but I would not enable it by default to avoid spamming the user's hard drive)

Screen captures would be awesome!

I'm going to put some more work into this soon


iOS Archive -> Lexical or Preprocessor Issue Group  'FlutterPluginRegistrant/GeneratedPluginRegistrant.h' file not found

Steps to Reproduce

The flutter run and flutter build iOS is correct

but when I archive ,the error has occurred

Logs

Logs

</details>

Hi @NkGins, Thanks for filing the issue. Is this issue with a newly created flutter app too?
Please ensure that you are opening ios/Runner.xcworkspace also You seem to be on older version of flutter and Unfortunately we cannot provide support to old versions. I would recommend you to please update flutter to latest stable by running flutter upgrade.


write/flush asynchronous

More question first: is flushing to gcs asynchronous ? i.e. I like this not to be a blocking operation so that the buffer (and new one ?) gets filled in while the previous block is being written to backend.
If it is a blocking op, request is to not make it ;-) or provide an option to enable/disable.
Our use case is a high-volume high-speed module in flask (switching to aiohttp server) where we continuously stream to GCS during a time window.

Writes append to a buffer, which is pushed to remote when it gets bigger than the configured block size. That push is blocking. It would take work to make async and not all fsspec backends would support it. However, if you use Dask, you can already pass work off to its scheduler, to be executed concurrently.
On October 22, 2019 12:30:07 PM EDT, Yannick Einsweiler<EMAIL_ADDRESS>wrote:

More question first: is flushing to gcs asynchronous ? i.e. I like this
not to be a blocking operation so that the buffer (and new one ?) gets
filled in while the previous block is being written to backend.
If it is a blocking op, request is to not make it ;-) or provide an
option to enable/disable.
Our use case is a high-volume high-speed module in flask (switching to
aiohttp server) where we continuously stream to GCS during a time
window.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/dask/gcsfs/issues/188

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


Why the redisson reconnected the connection  and still throw exceptions

   config.setCodec(new StringCodec())
            .useSingleServer()
            .setAddress("redis://" + "******" + ":" + "6379")
            .setConnectionMinimumIdleSize(3)
            .setConnectionPoolSize(3)

using the latest version .
After debugging,I found that when the connection lost,redisson will try to reconnect and it do succeed,but it still throw an Exception.
I have try enlarging the timeout options,But it just idel there .Can somebody tell me how to solve this?
////////////////////////////////////////////
2020-06-20 17:41:58.529 [http-nio-18080-exec-1] ERROR o.a.c.c.C.[.[.[.[dispatcherServlet].log:175 - USER: NULL_USER Servlet.service() for servlet [dispatcherServlet] in context with path [/api] threw exception
org.redisson.client.RedisTimeoutException: Command still hasn't been written into connection! Increase nettyThreads and/or retryInterval settings. Payload size in bytes: 29. Node source: NodeSource [slot=0, addr=null, redisClient=null, redirect=null, entry=null], connection: RedisConnection@491672465 [redisClient=[addr=redis://*:6379], channel=[id: 0x1a073aa2, L:/<IP_ADDRESS>:60488 - R:/1:6379], currentCommand=CommandData [promise=RedissonPromise [promise=ImmediateEventExecutor$ImmediatePromise@326e8324(failure: java.util.concurrent.CancellationException)], command=(PSETEX), params=[user:token:secret:13560124863,<PHONE_NUMBER>, PooledUnsafeDirectByteBuf(ridx: 0, widx: 29, cap: 256)], codec=org.redisson.client.codec.StringCodec]], command: (PSETEX), params: [user:token:secret:13560124863,<PHONE_NUMBER>, PooledUnsafeDirectByteBuf(ridx: 0, widx: 29, cap: 256)] after 3 retry attempts
at org.redisson.command.RedisExecutor$2.run(RedisExecutor.java:200)
at io.netty.util.HashedWheelTimer$HashedWheelTimeout.expire(HashedWheelTimer.java:680)
at io.netty.util.HashedWheelTimer$HashedWheelBucket.expireTimeouts(HashedWheelTimer.java:755)
at io.netty.util.HashedWheelTimer$Worker.run(HashedWheelTimer.java:483)
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.lang.Thread.run(Thread.java:748)

Which Redisson version do you use?

hello, I use Redisson version is 3.13.1。but i can not to acquire lock。constantly refresh in the console
22:34:26.535 [redisson-netty-8-17] DEBUG org.redisson.connection.DNSMonitor - Request sent to resolve ip address for master host: <IP_ADDRESS>
22:34:26.535 [redisson-netty-8-20] DEBUG org.redisson.connection.DNSMonitor - Resolved ip: /<IP_ADDRESS> for master host: <IP_ADDRESS>
22:34:26.613 [redisson-netty-11-17] DEBUG org.redisson.connection.DNSMonitor - Request sent to resolve ip address for master host: <IP_ADDRESS>
22:34:26.613 [redisson-netty-11-20] DEBUG org.redisson.connection.DNSMonitor - Resolved ip: /<IP_ADDRESS> for master host: <IP_ADDRESS>
22:34:26.676 [redisson-netty-14-17] DEBUG org.redisson.connection.DNSMonitor - Request sent to resolve ip address for master host: <IP_ADDRESS>
22:34:26.676 [redisson-netty-14-20] DEBUG org.redisson.connection.DNSMonitor - Resolved ip: /<IP_ADDRESS> for master host: <IP_ADDRESS>
22:34:31.322 [redisson-netty-2-18] DEBUG org.redisson.connection.DNSMonitor - Request sent to resolve ip address for master host: <IP_ADDRESS>
22:34:31.322 [redisson-netty-2-20] DEBUG org.redisson.connection.DNSMonitor - Resolved ip: /<IP_ADDRESS> for master host: <IP_ADDRESS>
22:34:31.455 [redisson-netty-5-18] DEBUG org.redisson.connection.DNSMonitor - Request sent to resolve ip address for master host: <IP_ADDRESS>
22:34:31.455 [redisson-netty-5-20] DEBUG org.redisson.connection.DNSMonitor - Resolved ip: /<IP_ADDRESS> for master host: <IP_ADDRESS>
22:34:31.537 [redisson-netty-8-18] DEBUG org.redisson.connection.DNSMonitor - Request sent to resolve ip address for master host: <IP_ADDRESS>
22:34:31.537 [redisson-netty-8-20] DEBUG org.redisson.connection.DNSMonitor - Resolved ip: /<IP_ADDRESS> for master host: <IP_ADDRESS>
22:34:31.615 [redisson-netty-11-18] DEBUG org.redisson.connection.DNSMonitor - Request sent to resolve ip address for master host: <IP_ADDRESS>
22:34:31.615 [redisson-netty-11-20] DEBUG org.redisson.connection.DNSMonitor - Resolved ip: /<IP_ADDRESS> for master host: <IP_ADDRESS>
22:34:31.677 [redisson-netty-14-18] DEBUG org.redisson.connection.DNSMonitor - Request sent to resolve ip address for master host: <IP_ADDRESS>
22:34:31.677 [redisson-netty-14-20] DEBUG org.redisson.connection.DNSMonitor - Resolved ip: /<IP_ADDRESS> for master host: <IP_ADDRESS>

Which Redisson version do you use?

3.13.1

Try to set pingConnectionInterval setting


Some sort of CSRF protection

(draw the rest of the owl)

Listening to your Svelte Summit (spring 2021) post talk discussion about the "enhance" form support and its integration with SvelteKit. Maybe that same integration is what can provide the CSRF support (considering since a non JS post to a form is where CSRF is most needed)

@Rich-Harris I soon need to draw this owl for an app nearing production, and why duplicate work?
Do you have any thoughts on this or how you'd like to see it implemented? :)

I think, since svelte kit pairs nicely with FaaS, it would likely be best to avoid server side state. The Double Submit Cookie technique seems like a reasonable choice. https://cheatsheetseries.owasp.org/cheatsheets/Cross-Site_Request_Forgery_Prevention_Cheat_Sheet.html#double-submit-cookie
I believe it could be implemented as a POC without modifying svelte kit code. There's a few strategies that could be considered, but I'd consider using the JWT standard to be the simplest.
Proposal using JWT:

Server generates anti-csrf token in the form of a JWT (hs256, maybe?) to generate anti-csrf token with expiration time, using server-side secret.
Token is given to client in either session, or cookie, or a custom hidden input field injected into each form.

Cookie or hidden form input would be best for no-javascript executions

Server uses middleware to validate token, rejecting with 403 if it is missing or invalid.

I hope to follow up soon with a strawman implementation gist

I think, since svelte kit pairs nicely with FaaS, it would likely be best to avoid server side state. The Double Submit Cookie technique seems like a reasonable choice. https://cheatsheetseries.owasp.org/cheatsheets/Cross-Site_Request_Forgery_Prevention_Cheat_Sheet.html#double-submit-cookie

I agree. A cookie with a SameSite: strict and HttpOnly (Secure too obviously) should do the trick

@nbgoodall I'm also needing to draw this owl about now. Did you get anywhere with this?
My first idea was to set the double submit cookie and inject the form field/value though the handle function (now nicely chainable with sequence). The cookie worked, but the input value was of course overwritten by Svelte during hydration. I don't yet have an idea for injecting the token into the form (so it will also appear in the POST request).
I'm trying right now to do this purely as a handler middleware without changing any code in SvelteKit itself.

So I've arrived at (I think) a working solution using only a handler.
It's essentially a signed double submit cookie with the added security of submitting it through a custom header (which means the same-origin policy comes to our defence as well).
The handler generates a JWT token with an expiry in a few minutes, then it adds a Set-Cookie header and injects a meta tag with the token in the document head.
On incoming requests, the handler reads the x-csrf-token custom header, compares it to the cookie, and verifies the signature. If everything is good it sets requests.locals.csrfVerified = true.
What I haven't decided is how to deal with getting new tokens. As it stands, tokens are only changed when the user reloads the page (and triggers SSR). The easy option is of course to just disable the router where necessary. That said, I don't think there's a way to disable the router for all navigation to a page, only from a page.
Alternately, you can just accept that the token is the same for however long the user remains on the page without refreshing.

@Karlinator how are you adding the x-csrf-token header? In the fetch requests themselves?
My biggest motivation for this was making forms secure without JavaScript. It is a double submit cookie, storing an encrypted value in the cookie session and exposing a masked version in forms (similar to how Rails does it to protect against SSL breach attacks). I was already using an encrypted cookie to store arbitrary JSON, so the token lives in there.
On each request:

If there's not a CSRF token in the encrypted cookie session, generate and store a new one.
Mask the token using a one-time pad and add it to Svelte's $session.
Add the token in a hidden input field to all non-GET forms (I've created a custom Form element). This works for me, but asking users to do something like this seems a bit much...
On form submission, unmask the token and compare it to the encrypted one. If they don't match, throw an error.

The session is encrypted using AES as I needed to decrypt the contents, but HMAC would be slightly faster if all you need is to verify the token...

What I haven't decided is how to deal with getting new tokens. As it stands, tokens are only changed when the user reloads the page (and triggers SSR).

I'm not sure this is an issue; it's common for a token to last a whole session, and realistically how long is someone going to be on a page for?

@nbgoodall
I'm adding it in the fetch requests, yes. We ended up not supporting non-JS anyway, so at that point there was no reason not to.
I tried to limit myself as far as I could to only doing stuff in the handle function, as I didn't really want to create custom components. That said, I did have to manually pass the token into the fetch calls so I only partly succeeded. That is the only thing that happens outside the handle hook though, which I am pretty happy with.
But I had to trade off non-JS function entirely so it's definitely not a universal solution. I think creating (or importing, if this were a package) a custom form component is probably reasonable given the alternatives right now? Otherwise we'd have to modify Svelte itself probably (and in the process "lie" about what the DOM will look like). I could definitely see a CSRFForm as a component with a slot (although that double F is killing me).

What I haven't decided is how to deal with getting new tokens. As it stands, tokens are only changed when the user reloads the page (and triggers SSR).

I'm not sure this is an issue; it's common for a token to last a whole session, and realistically how long is someone going to be on a page for?

You're probably right. Depending on who you ask (there are some long threads on this on StackOverflow) I'd probably be fine with just checking for the existence of the header and relying on the same-origin policy. It's generated anew every time it's sent out, after all, so it shouldn't really be a problem. I'm probably being a bit paranoid; I have more than enough layers of defence in depth already not to worry about the token living through some client-side routing.
Thanks for outlining your solution though!

Here's more details on the solution I ended up using. It supports JS and non-JS forms and operated in a serverless environment, so seems to be perfectly aligned with svelte-kit's principles. I'm only using this token for CSRF protection and not to store any session info.
Generate & Hyrdate
To add CSRF to a non-js page, you can hydrate the tokens in the handle hook. You'll need to set your cookie value and inject values into the HTML, like so:
import * as cheerio from "cheerio";

export async function hydrateCsrfProtection(
  response: ServerResponse,
  csrfToken: string
): Promise<ServerResponse> {
  if (response.headers["content-type"] !== "text/html") {
    return response;
  }

  // Add csrf information to meta tags
  const $ = cheerio.load(response.body.toString());
  $("head").append(
    `<meta name="csrf-param" content="${clientConfig.csrfParam}" />`,
    `<meta name="csrf-token" content="${csrfToken}" />`
  );

  /// Add csrf information to forms in case javascript is disabled or not loaded
  $("body")
    .find("form")
    .each(function () {
      $(this).append(
        `<input type="hidden" name="csrf-token" content="${csrfToken}" />`
      );
    });

  return {
    ...response,
    body: $.html(),
  };
}

Enhance Forms
To solve the cookie going away with hydration, you can add a use directive to "enhance" the form. For example:
const csrfTokenMeta = (): HTMLMetaElement =>
  document.querySelector('meta[name="csrf-token"]');
const csrfParamMeta = (): HTMLMetaElement =>
  document.querySelector('meta[name="csrf-param"]');
export const csrfToken = (): string => csrfTokenMeta().content;
export const csrfParam = (): string => csrfParamMeta().content;

// this action (https://svelte.dev/tutorial/actions) allows us to
// progressively enhance a <form> that already works without JS

export function enhance(form: HTMLFormElement): void {
  if (browser) {
    const csrfParamInput = document.createElement("input");
    csrfParamInput.setAttribute("type", "hidden");
    csrfParamInput.setAttribute("name", csrfParam());
    csrfParamInput.setAttribute("value", csrfToken());
    form.append(csrfParamInput);
  }
}

Wrap fetch for client-side only posts
You can support client-side fetch like this:
export const clientFetch: typeof fetch = (
  input: RequestInfo,
  init?: RequestInit
) => {
  const initHeader =
    typeof input === "string" ? init?.headers : init.headers ?? input.headers;
  const headers = new Headers(initHeader);
  headers.set("Content-Type", "application/json");
  headers.set("x-csrftoken, csrfToken());

  if (typeof input === "string") {
    return fetch(input, { ...init, headers });
  }

  return fetch({ ...input, headers }, { ...init, headers });
};

To get the token from the form or the header, you can use another handle hook modification
const extractCsrfToken = (request: ServerRequest) => {
  if (request.body === undefined) {
    return "";
  }

  return typeof request.body !== "string" && "get" in request.body
    ? request.body.get(clientConfig.csrfParam)
    : request.headers[clientConfig.csrfHeader];
};

Ensure the tokens in the header/form and cookie match
You'll need to make sure the header/form value matches the cookie. To get the cookie:
  const cookies = cookie.parse(headers.cookie ?? "");
  const cookieCsrfToken = cookies.csrf_token;

Your matching algorithm will differ depending on how you implement your tokens. A good start would be a HS256 JWT for both tokens. Use the same sub value for both tokens with a different cyptographically-random jti. In addition, set and eat (15 minutes is probably a good start). Validate both JWTs to make sure they haven't been tampered with or expired. Then, make sure the sub value in each token matches.

I'm a little confused as to why someone would add a CSRF token to a fetch request, when SOP/CORS already solve that. An attacker cannot forge a request via fetch without CORS being configured, and then you'd additional need Access-Control-Allow-Credentials for it to work and a CORS misconfiguration that allows any (evil) host. The only reason a CSRF token for fetch is needed in some frameworks is because it already has a CSRF token for classic forms and then fetch requests need to be made compatible to that because the server doesn't know. If you do not use <form> and only fetch, then the Origin header solves CSRF. There is no need to use a token. Turns out all modern browsers also set Origin for <form> POSTs. That means if you only use fetch but an attacker uses <form> on a different origin then Origin header does not match. If it is missing (IE < 11 + some edge cases, Firefox for Android) you can safely discard the request, since you only use fetch, which always includes Origin for non-GET/HEAD. No false-positive in that case.
My suggestion for SvelteKit:

Do not implement any form of CSRF token
Check Origin header on every request that is not GET or HEAD. If Origin is missing, fall back to Referer. If both are missing or do not match, reject the request.
Make sure #1046 is applied before the CSRF logic and only for POST, or else you can bypass the whole thing
Serve cookies with SameSite=strict as additional measurement

To my knowledge there is no way to bypass this and this is the recommended approach moving forward. It is also recommended by OWASP. There is one downside: this can lead to false positives (rejecting valid requests) under very specific circumstances:

If a user is using IE < 11, IE 11 in some cases, Firefox for Android or any other outdated browser that does not set Origin for <form>
This user also has Referer disabled via some privacy settings
This user also does not have JavaScript enabled or uses a browser that doesn't support fetch
Then this user will not be able to submit your forms. I think this is acceptable.

Sources:

https://caniuse.com/mdn-http_headers_origin
https://fetch.spec.whatwg.org/#origin-header
https://cheatsheetseries.owasp.org/cheatsheets/Cross-Site_Request_Forgery_Prevention_Cheat_Sheet.html#identifying-source-origin-via-originreferer-header
https://security.stackexchange.com/questions/158045/is-checking-the-referer-and-origin-headers-enough-to-prevent-csrf-provided-that
https://stackoverflow.com/questions/1413930/is-checking-the-referrer-enough-to-protect-against-a-csrf-attack
https://www.brandur.org/fragments/origin
https://www.sjoerdlangkemper.nl/2019/02/27/prevent-csrf-with-the-origin-http-request-header/
https://portswigger.net/web-security/csrf/samesite-cookies

I want to point out that OWASP (in the source I linked above) only recommends this in addition to the other approaches under the "Defense In Depth Techniques" section. Because of the following downsides (I didn't list all of them above):

This mitigation is working properly when origin or referrer headers are present in the requests. Though these headers are included majority of the time, there are few use cases where they are not included (most of them are for legitimate reasons to safeguard users privacy/to tune to browsers ecosystem). The following lists some use cases:

Internet Explorer 11 does not add the Origin header on a CORS request across sites of a trusted zone. The Referer header will remain the only indication of the UI origin. See the following references in Stack Overflow here and here.
In an instance following a 302 redirect cross-origin, Origin is not included in the redirected request because that may be considered sensitive information that should not be sent to the other origin.
There are some privacy contexts where Origin is set to "null" For example, see the following here.
Origin header is included for all cross origin requests but for same origin requests, in most browsers it is only included in POST/DELETE/PUT Note: Although it is not ideal, many developers use GET requests to do state changing operations.
Referer header is no exception. There are multiple use cases where referrer header is omitted as well (1, 2, 3, 4 and 5). Load balancers, proxies and embedded network devices are also well known to strip the referrer header due to privacy reasons in logging them.

However, some of these points don't really apply (e.g. if you are using GET to make mutating requests that's a bug in your app). It's up to the maintainers to decide if this is something that they want in the core. I personally think the benefits outweigh the downsides by a lot and I will take this approach, it's trivial to implement. I don't think a token based approach can be added to SvelteKit in a way that works for all use cases and adapters. There are too many edge cases since SvelteKit doesn't follow the classic request/response pattern to serve pages and swapping out tokens will become a pain (will end up in false positives as well because of edge cases and timed out tokens and whatnot).
I also want to point out that if your Svelte app uses a non-cookie approach to sessions (e.g. JWT in localStorage) CSRF does not exist. CSRF only exists because of cookies.

It looks like Firefox for Android has likely added support for the Origin header:

https://caniuse.com/mdn-http_headers_origin
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Origin

I notice that Play Framework uses a token and checks under the following conditions:

The request method is not GET, HEAD or OPTIONS.
The request has one or more Cookie or Authorization headers.
The CORS filter is not configured to trust the request’s origin.

And it has a warning about needing different settings when using NTLM or client certificate based authentication.
Rails and Laravel use tokens as well. Next.js apparently leaves it to the user :stuck_out_tongue_closed_eyes:
Some additional thoughts about the configuration:

You might not want to bake the origin into the application at build time because you might deploy the site to different domains (e.g. a staging and production version of your site). I.e. maybe it should live in $env/dynamic/public? (should we rename our existing environment variables to fit the new naming scheme?)
Perhaps it should be on by default for good security? But that would be a breaking change as it would break sites that don't configure the origin. Maybe you'd also want a way to disable it? (E.g. if you're storing tokens in local storage instead of cookies.)

It's possible we could just add this to the templates rather than the framework so that users have full control over the logic being used. E.g. something like this in handle:
if (request.headers.get('origin') !== url.origin) {
  return new Response('nice try, bad guy', { status: 403 });
}

I don't remember where I found this implementation, but I like it very much.
There are 2 values in the form: "token number" and the token itself. Each time, the user gets a new pair. It may have two tabs open and the submission of the forms will be correct.
I don't like the solution: <input type="hidden" name="csrf-token" content="${csrfToken}" /> because the first submission of the form will consume a token, and the next submission will report an error.
I imagine the use in SK as:
<Form csrf>

and:
/** @type {import('./$types').FormAction} */
export function createTodo({ request }) {
  if (!request.csrf.validate()) {
    return {
      errors: {
        csrf: 'Oh no!.. You failed'
      }
    };
  }
// another form validations
request.csrf.consume(); //Consider when to refresh the token: How the next message will behave, how errors occurred in the form / database.
  // ...
}

BTW: With the server, I can easily fake the header origin. :-P

BTW: With the server, I can easily fake the header origin. :-P

With a server, I can easily scrape the csrf-token from the html source and send it along.
The purpose of a csrf token is to protect your users which are visiting your site with a browser.

@bato3 would it work without JS?


Board Review: Introducing Confidential Ledger

Thank you for starting the process for approval of the client library for your Azure service.  Thorough review of your client library ensures that your APIs are consistent with the guidelines and the consumers of your client library have a consistently good experience when using Azure.
The Architecture Board reviews Track 2 libraries only. If your library does not meet this requirement, please reach out to Architecture Board before creating the issue.
Please reference our review process guidelines to understand what is being asked for in the issue template.
Before submitting, ensure you adjust the title of the issue appropriately.
Note that the required material must be included before a meeting can be scheduled.
Contacts and Timeline

Service team responsible for the client library: Azure Confidential Ledger
Main contacts<EMAIL_ADDRESS>Expected GA date for this library: December 2021

About the Service

Link to documentation introducing/describing the service: Azure Confidential Ledger is a confidential computing service running in SGX enclaves that provides customers with an immutable, tamper-proof ledger for saving data. Write transactions, once durably saved to the ledger, may be cryptographically verified with a receipt at any time. The service is built on Microsoft Research's Confidential Consortium Framework.
Link to the service REST APIs:  https://github.com/Azure/azure-rest-api-specs/pull/13613
Is the goal to release a Public Preview, Private Preview, or GA? Public Preview

About the client library

Name of client library: azure-confidential-ledger
Link to library reference documentation: N/A
Is there an existing SDK library? If yes, provide link: No

Step 1: Champion Scenarios
Ultimately the library should be easy to use for common scenarios that developers want. Consider the following questions when thinking about champion scenarios:

What is the app the developer is building that uses your client library?
Who is the end-user of the application (the developer's customer)?
What features of the API need to be explained in the sample so that someone could use this API in real app?
How does the authentication workflow look?

See Champion Scenario section here.
Code is appreciated but optional. Pseudocode is fine.

Champion scenario 1: Writing to the Ledger, retrieving previously written data, and getting a receipt for past writes.
The customer has a service that is producing logs they wish to store in an immutable, tamper-proof manner. When they have a log entry to emit, they call the Confidential Ledger service (POST /app/transactions) with said data. The service returns a value in the header, x-ms-ccf-transaction-id, that indicates when the write will be durably saved to the ledger. The customer may continue writing ledger entries, or poll the Confidential Ledger service until the previous write becomes durable. Durably written data may be retrieved at any time with GET /app/transactions/{transactionId}.

# The TLS certificate for Confidential Ledger is self-signed, so we retrieve the certificate from the Identity Service to use for HTTPS verification in the ConfidentialLedgerClient.
identity_service_client = IdentityServiceClient()
ledger_identity = identity_service_client.get_ledger_identity(ledger_id)

confidential_ledger_client = ConfidentialLedgerClient(url=ledger_url, tls_certificate=ledger_identity.tls_certificate, credential=ConfidentialLedgerCertificateCredential("/path/to/client/cert.pem"))  # Here, we use cert-based mutual TLS authentication.
write_response = confidential_ledger_client.append_to_ledger("Hello World")

confidential_ledger_client.wait_until_durable(write_response.transaction_id)  # Blocking call
assert confidential_ledger_client.get_ledger_entry(write_response.transaction_id).contents == "Hello World"

receipt = confidential_ledger_client.get_receipt(write_response.transaction_id).receipt
# The receipt may be parsed and validated as described here: https://microsoft.github.io/CCF/main/use_apps/verify_tx.html#transaction-receipts

Champion scenario 2: Manage users for the ledger.
An Administrator user, added via ARM at the time of Confidential Ledger creation, may GET/PATCH/DELETE other users. New users may have the following roles: Reader (read-only), Contributor (read-write), Administrator (read-write and modify users).

identity_service_client = IdentityServiceClient()
ledger_identity = identity_service_client.get_ledger_identity(ledger_id)

admin_client = ConfidentialLedgerClient(url=ledger_url, tls_certificate=ledger_identity.tls_certificate, credential=ConfidentialLedgerAadCredential(admin_aad_object_id)  # Clients may also authenticate with the Confidential Ledger using AAD Bearer tokens.

# User IDs may be the following:
#   1. AAD Object Id
#   2. PEM certificate fingerprint
admin_client.patch_user(reader_object_id, ConfidentialLedgerUserRole.READER)
admin_client.patch_user(contributor_cert_fingerprint, ConfidentialLedgerUserRole.CONTRIBUTOR)

# Now, clients that authenticate with the user identity `reader_object_id` can read, and clients that authenticate with a certificate matching `contributor_cert_fingerprint` may read and write.

admin_client.get_user(contributor_cert_fingerprint)  # Get details about this user.
admin_client.delete_user(contributor_cert_fingerprint)  # Revoke permissions for this user.

Champion scenario 3: Validate details about the Confidential Ledger.
Since the Confidential Ledger's TLS certificate is self-signed, a customer might want to validate information about the Ledger before writing data. Details we make available at the moment include enclave quotes, consortium members (identities with permissions to modify the Confidential Ledger, such as adding nodes to the Ledger or upgrading the enclave code), and the constitution (a script run in the Confidential Consortium Framework that assesses member actions).

identity_service_client = IdentityServiceClient()
ledger_identity = identity_service_client.get_ledger_identity(ledger_id)

confidential_ledger_client = ConfidentialLedgerClient(url=ledger_url, tls_certificate=ledger_identity.tls_certificate, credential=ConfidentialLedgerCertificateCredential("/path/to/client/cert.pem"))

enclave_quotes = confidential_ledger_client.get_enclave_quotes()  # type: List[EnclaveQuote]
for quote in enclave_quotes:
    # Code to validate the quote
    pass

constitution = confidential_ledger_client.get_constitution()
print(constitution.script)

consortium = confidential_ledger_client.get_consortium()
for member in consortium.members:
    print(member.certificate)

Step 2: Quickstart Samples (Optional)
Include samples demonstrating how to consume the client library if available:

Create a new resource
Read the resource
Modify the resource
Delete the resource
Error handling
Handling race conditions/concurrency issues

Thank you for your submission!

scheduled for 4/8

Recording[MS INTERNAL ONLY]


Test demonstrating explicit validation issue between different enumerables with mapped generic types

Provides a test that demonstrates the problem with validation between different enumerables with the mapped generic types: Issue #17

Going to close this one and open a new one after merging latest.


Why is there no validation loss?

Hi, thanks very much for providing the code and framework!
Can I check why the code does not monitor loss evolution for a separate validation set? I see from the closed issues that there used to be one, but it seems to have been removed in latest. I'm sure validation loss should still be monitored to ensure model learns proper features right?
Thanks!
Michael

I think the evaluation code may be the ipynb in the feature_eval folder,and the ipynb need to be run in the google colab.


feat!: remove Start/EndTime from LogSink, Metadata from LogEntry, implement multipattern resource names

Regenerates the Logging Client with the v2 Gapic configuration which includes multi-pattern resource names
NOTE if you are only using the hand-written layer, no changes should be necessary. The protobuf messages and generated clients are part of the public surface area so this is a major version bump.
Breaking proto message changes

Removes startTime and endTime fields from LogSink protobuf message
Removes metadata field from LogEntry protobuf message

Resource ames
Rather than providing an abstract base class for a resource name type, we provide a concrete base class which serves as the default resource name.
For example, we previously provided an abstract class LogName with concrete implementations of BillingLogName, FolderLogName, OrganizationLogName, and ProjectLogName from which you would pick one to use. Now LogName behaves like a ProjectLogName by default but can also be used to build all types - LogName.ofProjectLogName, LogName.ofBillingLogName, LogName.ofFolderLogName, LogName.ofOrganizationLogName. If you were using the LogNames.parse(String) static method, you can now use LogName.parse(String).
BREAKING CHANGE:

If you only use com.google.cloud.logging classes (without the v2), you should not need to change any code.
Removes start/endTime from LogSink protobuf messages
Removes metadata from LogEntry protobuf messages
Removes old resource name types in favor of the new multi-pattern resource names

How does the release tooling know to do this? Does it rely on the release
engineer remembering what the version number is supposed to be?
On Thu, Apr 2, 2020 at 2:29 PM Jeff Ching<EMAIL_ADDRESS>wrote:

@chingor13 commented on this pull request.
In README.md
https://github.com/googleapis/java-logging/pull/127#discussion_r402524972
:

@@ -38,11 +38,11 @@ If you are using Maven with [BOM][libraries-bom], add this to your pom.xml file
If you are using Maven without BOM, add this to your dependencies:

-    <dependency>
-      <groupId>com.google.cloud</groupId>
-      <artifactId>google-cloud-logging</artifactId>
-      <version>1.101.0</version>
-    </dependency>
+<dependency>
+  <groupId>com.google.cloud</groupId>
+  <artifactId>google-cloud-logging</artifactId>
+  <version>1.101.1-SNAPSHOT</version>

This will be updated by the release tooling and actually shouldn't be a
SNAPSHOT in the README

—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
<https://github.com/googleapis/java-logging/pull/127#discussion_r402524972>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHVP2BW23LAQZ6RUIJHRJ3RKTKQ3ANCNFSM4LZUVPHA>
.

--
Elliotte Rusty Harold
<EMAIL_ADDRESS>

The feat! indicates a breaking change which prompts a major version bump.

This PR got stale after being open too long. Regenerating and applying the same fixes in #174


What is html rendering?

I am not very good at English, so I apologize in advance.
I understand svg / canvas rendering.
but, I don`t understand html rendering.
I want to try 3D layer.
What kind of code should I write?

the 'html' renderer renders svg elements wrapped in div elements.
That way CSS 3d transformations can be applied to them.
Depending on your animation, it can help to render 3d.

I used a 3D layer &camera on AfterEffects cc 2017.
but, bodymovin(version 4.6.9) gives an error.
"Unable to execute script at line 311. undefined is not an object"
I use camera (position(z) anime) & plane(3d layer Y axis anime).

I've found the issue.
I'll be uploading it by the end of this week.
thanks for reporting it.

I am looking forward to the weekend.
thank you.

fixed


Display not normal in reading mode,

Before you open a bug report
Disable plugins and snippets that could be causing a conflict. Update to the latest versions of the following, and restart Obsidian:

Minimal Theme
Minimal Theme Settings plugin (or Style Settings plugin, but not both)
Contextual Typography plugin

Describe the bug
Display not normal in reading mode, normal in live preview。
To reproduce
Steps to reproduce the behavior:

I think it's the mix of graphics and text
Adding a blank line makes the display different, if there is a place where no blank line is added, the problem still exists

See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots

Debug info (please complete the following information):
SYSTEM INFO:
Obsidian version: v0.13.30
Installer version: v0.12.3
Operating system: Windows 10 Home China 10.0.19043
Login status: logged in
Catalyst license: none
Insider build toggle: off
Live preview: on
Legacy editor: off
Base theme: light
Community theme: Minimal
Snippets enabled: 18
Safe mode: off
Plugins installed: 81
Plugins enabled: 65
1: Buttons
2: Citations
3: Clear Unused Images
4: Convert url to preview (iframe)
5: Dataview
6: Diagrams
7: Workspaces Plus
8: Workbench
9: Word Splitting for Simplified Chinese in Edit Mode
10: Text expand
11: Templater
12: Tag Wrangler
13: Remember cursor position
14: Recent Files
15: QuickAdd
16: Reset Font Size
17: Icon Shortcodes
18: Hotkeys++
19: Better footnote
20: Obsidian Leaflet
21: YouHaveBeenStaring
22: Vault Statistics
23: Admonition
24: Advanced URI
25: Annotator
26: Bartender
27: Block Reference Counter
28: Calendar
29: Completr
30: Customizable Sidebar
31: Easy Typing
32: Editor Syntax Highlight
33: Excalidraw
34: Extract url content
35: Find unlinked files and unresolved links
36: Folder Note
37: Fullscreen mode plugin
38: Global Hotkeys
39: Homepage
40: Hotkey Helper
41: Image Toolkit
42: Journey
43: Juggl
44: Kanban
45: Map of Content
46: Map View
47: Media Extended
48: MetaEdit
49: Metatable
50: Mind Map
51: Obsidian Memos
52: Obsidian42 - BRAT
53: Obsidian42 - Text Transporter
54: Search on Internet
55: Shell commands
56: Table Extended
57: Various Complements
58: Auto Note Mover
59: ZH增强编辑
60: BookNote
61: Dynamic Highlights
62: Style Settings
63: Contextual Typography
64: Minimal Theme Settings
65: Highlightr
RECOMMENDATIONS:
Custom theme: for cosmetic issues, please first try updating your theme to latest. If still not fixed, please try to make the issue happen in the help vault or disable community theme and snippets.
Community plugins: for bugs, please first try updating all your plugins to latest. If still not fixed, please try to make the issue happen in the help vault or disable community plugins.

You currently have 65 plugins enabled. Are you able to reproduce this issue in a new vault? If not can you try again by disabling plugins, or in a new vault so you can identify which plugin is causing the issue?

I see, that's why.close it is ok


Update README.md

Basic Formatting is done to test the merging of the request.

@akashchouhan16 , what do you understand from this line https://github.com/firstcontributions/merge-bot/blob/master/api/merge.js#L46


[Comments] 170201

Comments for https://bit101.github.io/lab/dailies/170201.html  and https://bit101.github.io/lab/dailies/170201a.html

Zoopraxiscope? I thought you were having a vinyl synesthetic moment.

I have recently re-discovered the lost joys of vinyl from my youth. So perhaps it's not an accident that I wound up with this.

See https://www.youtube.com/watch?v=DqVwc6nrHjI&t=259s at 4:25

That is amazing. I need to watch the whole video.


add in morning report / report on demand

Using calendar, weather, or other things, generate a good daily report. perhaps including recommended watching on YouTube based on a list that is analyzed.

I think this would be cool to have the bot post this in maybe the general slack channel in the morning.

Use emails from mailing lists too. That would be kind of cool. The extract wisdom fabric prompt would be interesting


[GURPS] Replaced all instances of the word Fear or fear with the word Fright.…

… In GURPS the proper term is Fright or a Fright Check, not fear. Also modified the Fright check macro to replace the word Will wuth the word Fright so it states it is making the roll vs Fright and not vs Will.
 In GURPS the proper term is Fright or a Fright Check, not fear. Also modified the Fright check macro to replace the word Will wuth the word Fright so it states it is making the roll vs Fright and not vs Will.

Hi @TankFarmer, while the terminology may need changing, it may be easiest for you to only change the user-visible indicators of the word.  The problem with your changes is that you are changing attribute names, and so the values in those attributes will be lost for current users of the sheet.  You could change the attribute names if you handle retrieving the previous attribute values and updating them to their new attributes via a sheet worker if you really wanted the underlying attribute names to change.
For now I'll close this, but feel free to make a new PR with either of the above modifications (either only change visible verbiage, or make a sheet worker to convert the attribute values).
Thanks!

JeffreyQuick question, if I may ask:Does changing the type of an attribute require any special code changes to retain existing data?
There is an attribute which is restricted to 'value' and I want to change it to 'text'.The current attribute only allows for a numerical entry BUT it needs to allow for several entries plus alpha characters as well.I am not changing the name of the attribute, just its type.Tom
On Tuesday, July 17, 2018, 6:51:32 AM PDT, Jeffrey Lamb<EMAIL_ADDRESS>wrote:

Hi @TankFarmer, while the terminology may need changing, it may be easiest for you to only change the user-visible indicators of the word. The problem with your changes is that you are changing attribute names, and so the values in those attributes will be lost for current users of the sheet. You could change the attribute names if you handle retrieving the previous attribute values and updating them to their new attributes via a sheet worker if you really wanted the underlying attribute names to change.
For now I'll close this, but feel free to make a new PR with either of the above modifications (either only change visible verbiage, or make a sheet worker to convert the attribute values).
Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

You can change an <input type="number" name="attr_attributename"> to an <input type="text" name="attr_attributename"> with no issue, yes.  If it has a default value, I would keep it as such.  Note that if you change the input type you might have to do a bit of CSS to make sure the layout remains consistent.

JeffreyThank you for the quick answer.All seems fine here, I can make the CSS layout changes as needed, I figured that part out.This is exactly what I needed to know.As you can tell I am rather new at this BUT no one else is making the changes we need so I took it upon myself to give it a try.Thanks again,Tom
On Tuesday, July 17, 2018, 6:47:38 PM PDT, Jeffrey Lamb<EMAIL_ADDRESS>wrote:
You can change an  to an  with no issue, yes. If it has a default value, I would keep it as such. Note that if you change the input type you might have to do a bit of CSS to make sure the layout remains consistent.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


rdt push --force-build option.

We should have a --force-build option, to allow people to force a docker rebuild instead of a sync.

@shaunmulligan there's a --force option, I guess we should just rename it to --force-build to make it more clear what its function is?


Refactor orders list

very well done!
i added a few comments regarding the comments ;)
strings are immutable and are expensive when we create a bunch of them for no reason. I have not added the comment everywhere
but notice how here a lot of those comments can be just like so:
"comment \n\n\n" instead of "comment" << "\n" << "\'n"<< "\n", so try to fix that :)


Added LiveSharp

https://www.livesharp.net/ seems to be the hot-reload feature we always dreamed of. Please consider adding this to the tooling section.

Very interesting, thank you!


Dots in wrong position

Hello, i' using the latest release on a 4k monitor with resolution set to 2560x1440, the preset is 1440p_SMF_en
I tried to use the 4k present but my monitor doesn't support HDR.

As you can see in the screenshot the dots are at the center of the screen, is something wrong with my configuration?

The dots are woking, just appearing in the wrong position

Don't have any 4k screens myself to troubleshoot this. But my guess is it's related to your resolution or scaling settings.
Are you monitor and Diablo both set to the same resolution?
Or maybe do you use multiple monitors with different resolutions/scaling settings?

I have a 4k monitor set to 2k.
Diablo is set to the same resolution of monitor by default, i dont think it's possible to have another one (the select dropdown is locked for me).
However setting the monitor to full hd with the 1080p preset fix this, it a problem related to my specific configuration (4k monitor downscaled 2k resolution with 1440p_SMF preset).

Strange that downscaling to 1080p works and 1440p not. Do you notice any differences between the two in your windows settings? To what value is the scaling set for 1080p and 1440p?
And another question to troubleshoot this. Do you have one or two monitors connected to your pc?

Problem solved: the windows scaling has to be set 100%.
Previosly i was using 150% on 2k resolution.
Thank you for your help!


What is a "Commitment?"

What does "Commitment" mean?

My understanding is that a commitment is a statement that you are available
and will be in position on a given day / range of days...
On 5 May 2016 at 19:17, Adam Ex Machina<EMAIL_ADDRESS>wrote:

What does "Commitment" mean?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/HTBox/crisischeckin/issues/567