[#2] As a user, I can initialize the project with a 'make' command

https://github.com/nimblehq/flutter_templates/issues/2
What happened 👀
Once checking out the project from the main branch, we should make the process to initialize the project intuitively.
Insight 📝

Allow the user to name their project.
Allow the user to name their project package name.
How to use:

On the project level, we run one command to update the package name and the project name at the same time. It is: make init PACKAGE_NAME=${com.example} PROJECT_NAME=${project_name} APP_NAME="{Your App Name}"

If not defining PACKAGE_NAME, APP_NAME or PROJECT_NAME, we will reuse the old name

There are some prerequisite steps that are included in Makefile also. They are: install python3 and install an isolated environment for Python3. If we want to check this step, just run make prepare-dev. If there is an error, please raise it to me so I can fix it 😅
Last but not least, run make help or make to show the help.

Proof Of Work 📹
https://user-images.githubusercontent.com/60863885/137101656-00096bdc-3543-48d6-8472-2befd936ac89.mov

@sleepylee oh I forgot it. Updated 🙏 😆
@doannimble Because you are starting the IC, I think it would be a great chance to test this script. 😋 Could you please help me initialize your project by using this script? 🙏

@luongvo I fixed the missing case that the project name in info.plist is not updated, and added the ability to update the  app name as well 🙏

I'm thinking...should you run test at the end automatically too? 😂

@sleepylee import the test to setup.py will cause the recursion because 2 python files depend on each other 😂
To solve this issue, I created a make run command to init the project then test that project 😁
Here is the result after I run the new command 🤤

@luongvo all good to go?


⚠ Bofrost.nl has degraded performance

In 441559e, Bofrost.nl (https://www.bofrost.nl) experienced degraded performance:

HTTP code: 200
Response time: 894 ms

Resolved: Bofrost.nl performance has improved in c7ff596.


Add Playlists to rules conditions

Hey,
first of all, thank you so much for this fantastic piece of software, it's AMAZING 👏🏻
I stream Plex content through Infuse on AppleTV, and I was looking for a way to prevent certain movies from being removed by Maintainerr's rules within Infuse itself.
With the Plex app this would not be a problem, as I could simply add movies to a specific Collection, and then tell the rule to avoid removing movies that are in that Collection. But my problem is that Infuse only supports Playlists.
Infuse does pull collections from Plex, but you can't add/remove items to them from Infuse itself.
Would it be possible to have a new condition that checks if a movie is (or isn't) in a Playlist, just like the Collection rule we have at the moment?

Thank you!

Hey, thanks for giving Maintainerr a shot!
I added the rules you requested in https://github.com/jorenn92/Maintainerr/pull/615, they'll be available in the next release.

:tada: This issue has been resolved in version 1.6.9 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

@jorenn92
You are an absolute legend, thank you so much!
will test it tomorrow when I have a moment. 🖤

just realized I posted the last message from my work account 😅 closing!


Don't use ssh-keyscan before connecting

Doing a ssh-keyscan first and then connecting is as bad as not verifying the keys at all
You want to be notified in case those host keys change (and that should not happen unexpectedly as for github.com), so you should consider setting them in action variables (can be public) or ask the CBC to publish SSHFP records (similar to what is done for files01)
Current keys:
# webhost.gewis.nl
webhost.gewis.nl ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQDaS7GVAQvQlZlqz1wEN9PdIC/DnfX9jXbjpLko9q6i2bB0ceCv0tJexynToDgRdGKd/ALF8kALr6uNQ98LU+mDGZGWI+BFg6HS6mp/zmZIrkigVyoFQhR6U1c14RyG63w1NFGXbAt6dPwAehqAXrxz5sCn5NJaMOldSmEkNYmG7Mu8WDaVjLUS7QVJA50EYW+wqK6w4khO/3TBZvXl2lyHykSoQ0m4g9oXjzm7MGVOCzrk1463xEG0DGYVZJfVfKKBYDq2Mlb0/ruy6T6heM+Og2zr6cwOgevGcVAbvL+Hh99Zf1frxqs/+cmWc5OTI9QNY4tIb6S8B7QigasTHh7uTso3UI1A5EqdwdGPUE0Ta5GjaqtNhRd8klVFXYw3zQ5sq7yRv4VpxH03STOjBxKdGvXKwubUTxCybZNY2EOA2cMD39bqgmX8o+CBDkUgqVMJ2X/1whPGbw5vERDXqjZO8+G7tHKfBJ3NIq169OwWVbR5Lcu3WHyMgqw+FOV2Cnk=
webhost.gewis.nl ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBHhW3PGsTBvaZwPSjwcnkbO4AgZGhvHlJcnpPkEjxLUgfE2XdWeaEY1mtyZ1wp1mxnCrZzbIyrY8+tLrRoJVR84=
webhost.gewis.nl ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIN6gM0CojAcA/wv0LytELxZY6b4ExaTiNHWYENCrVmdm

https://github.com/JustSamuel/dispuutivv/blob/5de7f5fea6a1093d74b7ded815c8144cd1689706/.github/workflows/node.js.yml#L51C23-L51C23

Thanks for the heads-up. This has been resolved.


"Multiple vaults with the same name" when continuing freshly created workspace.

Please select the area your Bug applys to. (Multiple selections are Possible)

[x ] Onboard. Initial vault setup and import/export pods
[ ] Create. Note creation, lookup, snippets and templates
[ ] Retrieve. Backlinks, references, graph view
[ ] Structure. Refactoring, multi-vault and schemas
[ ] Publish. Sharing your repo with the world
[ ] Misc (Choose this if your not sure)

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Dendron Initialize
Close Workspace
Dendron Initialize (same path)
continue

Expected behavior
I should be able to continue a workspace once created without that error message.
When continuing freshly created workspace, I get the error of "Multiple vaults with the same name".
Screenshots

Desktop (please complete the following information)

OS: iOS, Windows, Linux
Browser chrome, firefox
Version v0.49.0

Dendron Log file
dendron.log

@phiwi - after the first initialize there is no need to run it a second time (a dendron.code-workspace should have already been created). What happens when you double click on the code-workspace file?


Change license to BSD-3-Clause (close #1)

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


[FancyZones] Custom layout settings reset to default every PT update

ℹ Computer information

PowerToys version: Affected many previous versions, currently 0.29.3
PowerToy Utility: FancyZones
Running PowerToys as Admin: Yes.
Windows build number: Win10 Pro 20H2 64bit build 19042.746
Also note I have a dual monitor setup, but I only ever use FancyZones on Monitor 2. Never thought to test whether it affects both monitors or just the 2nd one - I'll let that on the next update

📝 Provide detailed reproduction steps (if any)

FancyZones enabled.
With mouse hovering on Monitor 2, press WIN+tilde to open layout editor
Change from Templates tab to Custom tab, create a new custom layout. I have two zones/columns, a skinny one on the right (about 15-20% of screen width), and the main zone on the left. "Show space around zones" unchecked. I saved this as MyCustom
Carry on living your life and enjoying FancyZones until the next power toys update.
Update

✔ Expected result
All fancyzones settings should remain in place after update
❌ Actual result
Fancyzones settings revert to Enabled, but reset back to default layout (3 columns with large padding zones). When I go into settings, MyCustom is still defined and remembered correctly, but it's just not selected.
📷 Screenshots
I've already updated and fixed my settings again today before submitting this issue, so I don't have anything to screenshot now I'm afraid.

@tmo793
PowerToys is still in technical preview and in some cases it is expected that an update can break backwards compatibility.
Since you are experiencing this problem frequently, I suggest to clean up all the settings and start clean.
Are you still running 0.29.3 or did you update to 0.31.2?

@enricogior I've just auto-updated to 0.31.2 and I've been proven wrong -- all my settings have been retained. I swear I would lose the settings every time there was an update, but now I'm starting to think it happens only rarely and I just think it's every time due to confirmation bias.
Issue closed due to pebkac.

Hi there,
I am having the exact same problem as above on V0.45.0 running windows 10 pro V21H1. Any help would be greatly appreciated as it saves my settings and custom layout but on laptop restart reverts back to the standard 3 column layout.
Regards

Hi @mccshane,
The current issue you're having is likely this one: https://github.com/microsoft/PowerToys/issues/13069
We're working on a fix for it.


Security update: Patch vuln related to okhttp3 dep CVE-2021-0341

This should fix the critical vulnerability ( CVE-2021-0341) found in the "okhttp3" dependency.
Okhttp3 changelog: https://square.github.io/okhttp/changelogs/changelog_4x/
Vuln info: https://nvd.nist.gov/vuln/detail/CVE-2021-0341
Okhttp3 fix pr: https://github.com/square/okhttp/pull/6740

Added patched versions of log4j and gson


Add extensible directive display information

Should add DisplayName and Description to our directive descriptors. This way when the descriptors are consumed in VS it can provide proper IntelliSense for what they're supposed to do.

Moving this to preview 3 since it's additive.

95c5049dd03ee856a7d2e870e794a5d1257244bc


Error out on TO0 after entire RVInfo is tried

Fix an issue where exception was being thrown on any exception,
except ConnectException, causing the Owner to not iterate through all
the RV locations. Instead, the exception will now be thron only if all
the RV locations have been tried once and failed.

Signed-off-by: Chandrakar, Prateek<EMAIL_ADDRESS>

Verified this PR, can be merged


Fails to parse some valid i64 and u64 numbers using the fallback implementation

Add the following test to the codebase:
#[test]
fn test_parse_i64_fuzzed() {
    let input = b"02221222122210221223";
    let result = parse::<i64>(input).unwrap();
    assert_eq!(result,<PHONE_NUMBER>2210221223);
}

Run it with SIMD disabled (with the .cargo/config.toml file deleted) and you'll see that it fails. Meanwhile the standard library parses this number correctly.
This bug was discovered using cargo-fuzz. You can find a guide to it here and the fuzzing setup I used here. I will contribute the fuzzing setup to your repository eventually.

Actually, it fails with SIMD enabled as well. So turning SIMD on/off doesn't make any difference.

I am also getting a similar error when trying to parse<PHONE_NUMBER>000000000000000000000000000001
The standard library implementation also handles this one correctly.

Zeroes at the beginning of the input are not supported by the design, and I am not sure if it's needed, because it will work slower.

I see, thanks for clarification.
Parsing numbers with leading zeroes is something people also need to do, and I think this library could do it faster than str::strip_leading_maches('0'). There are ways to quickly count leading decimal zeroes with SIMD: https://github.com/KholdStare/qnd-integer-parsing-experiments/issues/2

Hm, it might be not that slow. Will think about it, thanks

Test 228836832f162352cf17699f1feebaa557e11573

FWIW the standard library parser supports even longer sequences of leading zeroes, so that<PHONE_NUMBER>00000001 does parse correctly into a u16.
It's up to you whether you choose to support this use case.

I just don't see any use cases. If anybody needs it, write it here, with explanation of the use case, would be interesting to know.

Done in a separate function atoi_simd::parse_full


"You are offline"

Keybase GUI Version: 5.3.0-20200310142606+4f2689009b
Hello,
i've been getting a "You are offline" alert when i try to login in Win10 gui.
i'm not offline.. :)

Hi!
Did this just resolve itself for you, or did you figure out something to do?
I'm having the same issue and I've experienced it before, but not for days on end.
Since this is almost four years later:) this is in Version 6.2.4-20231019203304+5cfcf6b41e


Deploy to rubygems with travis

@carlossg could you add<EMAIL_ADDRESS>on rubygems?
btw, and this is more for the future, did you also want to move https://github.com/carlossg/librarian at some point?

@igalic or you have some voxpupuli-managed account?
And how do you actually do such a travis release? I understand we need to merge a pull request with the version bump, and at the same time push a tag to the voxpupuli/master branch, before the travis build does the deployment. Is that correct?

unfortunately, we do not (yet)
but if you can create one and add the credentials to voxpupuli/plumbing that would be amazeballs
all you need is a trusted GPG key :D

all you need is a trusted GPG key :D

Unfortunately I don't have that (yet) :/ But I will start getting signatures tomorrow!

@njam you are an owner now of both librarianp and librarian-puppet
I don't have permissions here to move https://github.com/carlossg/librarian, @igalic ?

@carlossg will put you into the admin group

I just moved it, but somehow in the process I lost some permission because I can't see the Settings tab anymore

@carlossg should be fixed now

I've added the encrypted API key of my rubygems account now.
@igalic or did you want to use the "plumbing" approach (that I don't fully understand)?
Either way, I think you'll need to merge and tag.

i'm not sure this will work, @njam. but we can see what it does for us for now

one second

Forgot to bump version, did it now.
I'm also not sure if it will work (never did it before). My guess is that you can merge this PR, then push a new tag (v2.2.2), which will trigger another build, and that build will finally deploy to rubygems with the API key I encrypted with travis for "voxpupuli/librarian-puppet".

will we need a tag, too?

I think we should have a tag so that the "release" shows up on git and Github? And the travis build is configured to only trigger the deployment on tags (on: tags: true).

@njam so essentially same as https://voxpupuli.org/docs/#releasing-a-new-version-of-a-module

I think yes. The difference seems that you usually push the version bump directly to master.
Should I remove it from this PR? Or you can merge this and push a tag separately to master (as tags can't be in pull requests).

I can do that. In fact, part of the idea behind the way we setup deployment is that the person who merges creates the tags.
it would be cool if that was somehow automated ;)

@njam can we coordinate this on irc when we're both online so we can react a bit quicker should something go wrong?

FYI, 2.2.2 was never deployed to rubygems.

Yes, for some reason it didn't work :/ (RubyGems authentication error).
Second try: https://github.com/voxpupuli/librarian-puppet/pull/10


Add new header comment location

This pull requests adds a new location for the header_comment configuration: 'after_namespace'. If configured, the header is inserted after the namespace declaration. In none namespace declaration is found, the default 'after_declare_strict' configuration is used to find the correct header position.

Hi @IchHabRecht and thanks for the proposal :)
I like the idea and hope to review soon.

This fixer brings third place for header comment - which makes tests much more complicated.
Lets consider having following template:
<?php
/**
 * {pos1}
 */
declare(strict_types=1);
/**
 * {pos2}
 */
namespace Foo;
/**
 * {pos3}
 */
class Bar
{
}

What if pos1 = pos3 = "Hello World" and pos2 = "Hello Universe" and config is ['header' => 'Hello Milky Way', 'location' => 'after_open']? Do we remove pos3 as it's the same as the one we will update? Maybe pos2 as well? Or only replace the first one?
My first solution was to refactor the current fixer - so it locates all possible places for the comment, updates the configured one and removes others. But what if the comment at pos2 is meaningful and someone want to update only pos1?

To be honest, defining what to do with existing comments is not the scope of this patch. Of course that should be done, but IHMO is not defined yet nor working correctly (currently I get two time the same header if I switch between both existing options).
@kubawerlos in your example pos3 and the new header aren't the same and I would advice not to remove anything.

What if they are the same? Then remove it?
What I meant is having 2 locations we have issues like https://github.com/FriendsOfPHP/PHP-CS-Fixer/issues/2590 and https://github.com/FriendsOfPHP/PHP-CS-Fixer/issues/3467, so adding third location without properly handling two is not the best way.

Would be good to get some tests in here

@IchHabRecht Any chance you have the time to add some tests here?

Thank you @IchHabRecht for your work, but I am going to close this because:

it's massively outdated (2018!) and requires solid rebase
it does not have tests
there wasn't any interest in this feature for years 🤷♂


Updating to 0.3.x from 0.2.x

Hi,
I was looking for a changelog or history documentation. By reading the commits log it seems that the major change is related to session. One have to do app.use(passport.session()); now after initialize.
If I do not want to use sessions, is omitting  app.use(passport.session()); will be enough? Or is {session: false} still relevant when invoking authenticate? I see it in the documentation still, but is it just a remainder of 0.2.x that need to be removed?

somehow linked #397 #375

Ok, will answer to myself, {session: false} is still needed...
@jaredhanson could you consider the session option being false by default if passport.session() was not used, and true by default the other way?

@jaredhanson please also consider maintaining a changelog.

@jaredhanson changelog please.

@jaredhanson +1 for a changelog!
The suggestion from @JSteunou about default session behavior also would make a lot of sense.

+1 for default session behavior

bump! for default session


Perf tests for stateware and dot-prop-immutable

https://github.com/zhDmitry/statewarePerfTests
Take a look on this pref tests. It looks that dot prop uses optima algorithm for updating arrays and object. It also gives you nice api for updating nested values without big perf reduction.
I guess stateware api  could be something like this.
const iState = createState({ }, { dotprop: true,  computed: true }) // i guess the defaults should be true but would be useful to turn off one of it
iState.set(['path', 'to' 'value'], value or func func from prevValue);

set, get, delete, merge, toggle - methods from dotprop with binded value for first argument.
What do you think about this improvement  ?

Looks good! I've seen another interesting lib do deal with nested immutable data: https://github.com/Zenika/immutadot
Its utilities are mostly based on lodash, so there're some extra features... Maybe too much? Dunno... Anyway, dot prop performance looks really good. We could test them both to make those features available.

@wellguimaraes i also have tested performance with ramda it looks awesome too.
Maybe  we should add more cases for testing.

For what it's worth, there's at least a couple dozen immutable update utility libraries out there.  See the Immutable Data#Immutable Update Utilities section of my Redux addons catalog for a list.
Also, quick side question.  I'm not exactly clear on the use case for Stateware.  Is it intended as a replacement for Redux, or a replacement for using plain JS objects inside of Redux?

@markerikson no, it's not a replacement for Redux. The idea is to have cleaner code while using Redux, specially regarding async action creators. Instead of having action creators, actions and action types, you'll have only "actions" and reducers. On reducers, you can listen to these actions "events", which are basically before, error and success.
Additionally, you get:

busy and error status for every action
actions are cancellable
you can add side effects to actions on separated handlers, etc

@markerikson The goal is similar to reselect, but with a different approach. For me, it looks clearer and less verbose.


negative times formatted as seconds from BC

Reported by hankin on 26 Jul 2001 00:02 UTC
! err533_leftover_neg_calendar.jnl
! 7/01
! the year field is suppressed as if negative times are still seconds from BC
define axis/units=days/t/t0=1-jan-1980 tax_neg = {-3,-2,-1}
show axis/l tax_neg
pause
define axis/units=days/t/t0=1-jan-1980 tax_pos = {1,2,3}
show axis/l tax_pos
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/294

Comment by ansley.b.manke on 24 Jul 2010 01:06 UTC
This is working correctly:

yes? define axis/units=days/t/t0=1-jan-1980 tax_neg = {-3,-2,-1}; show axis/l tax_neg
 name       axis              # pts   start                end
 TAX_NEG   TIME                 3 r   29-DEC-1979 00:00    31-DEC-1979 00:00
T0 = 1-JAN-1980
   Axis span (to cell edges) = 3

       L     T                   TBOX      TBOXLO                TSTEP (DAYS)
       1>  29-DEC-1979 00:00:00  1          28-DEC-1979 12:00:00    -3
       2>  30-DEC-1979 00:00:00  1          29-DEC-1979 12:00:00    -2
       3>  31-DEC-1979 00:00:00  1          30-DEC-1979 12:00:00    -1
yes? define axis/units=days/t/t0=1-jan-1980 tax_pos = {1,2,3}; show axis/l tax_pos
 name       axis              # pts   start                end
 TAX_POS   TIME                 3 r   02-JAN-1980 00:00    04-JAN-1980 00:00
T0 = 1-JAN-1980
   Axis span (to cell edges) = 3

       L     T                   TBOX      TBOXLO                TSTEP (DAYS)
       1>  02-JAN-1980 00:00:00  1          01-JAN-1980 12:00:00    1
       2>  03-JAN-1980 00:00:00  1          02-JAN-1980 12:00:00    2
       3>  04-JAN-1980 00:00:00  1          03-JAN-1980 12:00:00    3


Webpage does not mention language support

Although multi language support is provided, the webpage does not mention anything about it.
Lets presume that is a key aspect for most users.

Hey @AndersBillLinden, I think the webpage mentions the **multilingual support of the library **.
Here is a screenshot:

Do you want to show anything more specific than that?

This was an intentional choice as annyang itself does not contain the individual languages support because it does not contain the speech recognition engine. The speech recognition - and supporting different languages - is up to the browsers and differs from browser to browser.
The FAQ does go into more detail than that - https://github.com/TalAter/annyang/blob/master/docs/FAQ.md#what-languages-are-supported


test(GearVR): test project for GearVR support in VRTK

made with Unity 5.5.3
Updated to work with the ControllerReference feature (see PR #1142).
In Assets\VRTK_GearVR_Test here are 3 scenes to be tested with GearVR:

object touching and grabbing (005_Controller_BasicObjectGrabbing_GearVR)
interaction with Unity UI (034_Controls_InteractingWithUnityUI_GearVR)
teleport (044_CameraRig_RestrictedTeleportZones_GearVR)

The examples were tested after changing [CameraRig] and [VRTK] in
order to support GearVR. The script EditorLikeCameraController is
attached to the camera to move/rotate it only in Unity Editor play mode.
In this way the examples can be tested also with mouse and keyboard
(the controls are almost the same as in Unity Scene Editor).
Warning! You must copy special OSIG file additions (oculussig_*)
to Assets/Plugins/Android/Assets/

There were the following issues with your Pull Request

Commit: 3259fa83c05bbc4b88a8be99ebc2f2a31e59217a
Your commit message body contains a line that is longer than 72 characters

Guidelines are available at https://github.com/thestonefox/SteamVR_Unity_Toolkit

This message was auto-generated by https://gitcop.com


kW as Unit (kWh already exists)

Description of the issue

How should the unit kW be expressed? With the help of the entity Watt? The Watt entity is not an individual and therefore cannot be linked to any individual via object properties. Should individuals for important units of measurement perhaps generally be added to the OEO in order to assign them to individuals using object properties?
There is an entity for the unit kWh. But not for kW. This is somewhat inconsistent. Should perhaps only the Si units be used in general and all other units be expressed using the Si unit and linked via the "has value" property with the corresponding prefix?

The same question arises for mega...

Ideas of solution
I would suggest offering only the Si units for all units and using the prefixes to display the other units. It would be helpful to provide examples for this. I would also create individuals for the most common units.
Workflow checklist

[ ] I discussed the issue with someone else than me before working on a solution
[ ] I already read the latest version of the workflow for this repository
[ ] The goal of this ontology is clear to me

I am aware that

[ ] every entry in the ontology should have a definition
[ ] classes should arise from concepts rather than from words

I transfer this issue to the OEO extended (OEOX) repository. Combinations of units with their prefixes like kW is exactly the use case we created the OEOX for.


problem for training

Thanks very much for sharing your work! But when I'm training as the readme introduces, I meet problems below, hope you can help, thank you!(python3.6.1, torch1.2.0)
do:
python train.py
problem:
.......
[2019-09-17 14:34:44,364] [p43415] [train.py:210] [INFO] Use VDC Loss
Traceback (most recent call last):
File "train.py", line 281, in
main()
File "train.py", line 241, in main
transform=transforms.Compose([ToTensorGjz(), normalize])
File "/home/zhanglijun/FaceLandmarks/3DDFA/utils/ddfa.py", line 117, in init
self.lines = Path(filelists).read_text().strip().split('\n')
File "/usr/local/python3.6.1/lib/python3.6/pathlib.py", line 1177, in read_text
with self.open(mode='r', encoding=encoding, errors=errors) as f:
File "/usr/local/python3.6.1/lib/python3.6/pathlib.py", line 1164, in open
opener=self._opener)
IsADirectoryError: [Errno 21] Is a directory: '.'

Make sure the path contains the file. It is obviously the path problem.

Thanks for your reply! I'm sure the path in bash scripts is right and contains the file. Is there any other paths I've missed?
LOG_ALIAS=$1
LOG_DIR="logs"
mkdir -p ${LOG_DIR}
LOG_FILE="${LOG_DIR}/${LOG_ALIAS}_date +'%Y-%m-%d_%H:%M.%S'.log"
#echo $LOG_FILE
./train.py --arch="mobilenet_1"
--start-epoch=1
--loss=wpdc
--snapshot="snapshot/phase1_wpdc"
--param-fp-train='/home/XXX/3DDFA/train.configs/param_all_norm.pkl'
--param-fp-val='/home/XXX/3DDFA/train.configs/param_all_norm_val.pkl'
--warmup=5
--opt-style=resample
--resample-num=132
--batch-size=512
--base-lr=0.02
--epochs=50
--milestones=30,40
--print-freq=50
--devices-id=0,1
--workers=8
--filelists-train="/home/XXX/3DDFA/train.configs/train_aug_120x120.list.train"
--filelists-val="/home/XXX/3DDFA/train.configs/train_aug_120x120.list.val"
--root="/home/XXX/3DDFA/train_aug_120x120"
--log-file="${LOG_FILE}"

I suggest you may debug it first. Jump to here File "/home/zhanglijun/FaceLandmarks/3DDFA/utils/ddfa.py", line 117

Thanks for your help, I've solved the problem.

Ok.

Hi @jiajiajun, I am facing the same issue. my filelists is empty.
How did you solve the issue? Could you help me too?


Typo fixed

Changed yuo to you in line 15.

A lot of these small spelling mistakes can be found automatically by a spell checker.
Also you can auto correct mistakes too.
refs #513
Most spell checkers are different so they don't check all file types etc or all types of code.
It's always good to have at least one spell checker on the CI.


Outline doesn't apply to alpha clip edge

I noticed that in Unity (using 2018.3), the outline selection on objects with alpha clip, it conforms to the texture edge. But with UnityOutlineFX, the outline follows the edge of the mesh. Is there a fix for this? I realize Unity probably updated their outliner since they last shared the code.

I figured out a solution. I forked and refactored things, but you can see how I did it here: https://github.com/brettmjohnson/Outliner/blob/master/Outliner/Outliner.cs


Reshape bug

Fixes #7

Codecov Report

Merging #8 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master      #8      +/-   ##
=========================================
+ Coverage    88.4%   88.4%   +<.01%
=========================================
  Files          43      43
  Lines        6680    6681       +1
=========================================
+ Hits         5905    5906       +1
  Misses        775     775


Redshift compresion utility

Hi, please resubmit a pull with fewer changes and a description of what you have changed. Thanks!


client.write can't create dir

client.write("/test/ni", dir=True) can't create dir
because the "write" method required "value" field, and has "value" field will raise Exception:
Traceback (most recent call last):
File "", line 1, in
TypeError: write() takes at least 3 arguments (3 given)
pls fix it

And give value field, always has Exception:

etcd.write('/nodes/queue', "1",dir=True)
Traceback (most recent call last):
File "", line 1, in
File "/Users/shujian/project/tw_collection/.venv/lib/python2.7/site-packages/etcd/client.py", line 484, in write
'Cannot create a directory with a value')
EtcdException: Cannot create a directory with a value

Coverage remained the same at 88.212% when pulling 388983471fb42d75a5ba903947ba7b2b066b276c on WanzyShu:master into 18c75196ffd04b3104f3ba44356ec1fcbcc4d09a on jplana:master.

You can create a directory by passing a value of None explicitly. It was preferred as we want people to be forced to pass a value in general.


Documentation guidelines

Hi everybody,
It's currently not easy to find any guidelines about how our documentation should look like. There are currently a couple of things that I learned while adding four PRs to the documentation and I would like to summarize those into a DOCUMENTATION_GUIDELINES.md file. I will start by adding a new PR to add that file and afterwards we can still modify it when necessary.

The pr is already merged, so this issue can be closed

@JWO719 thanks for the reminder 👍


Add Sensei Ten support (1038:1832)

I bought this mouse earlier this evening, and had of course not considered that sitting down with something like this was necessary. Thanks for providing such a great piece of software!
I duplicated the configurations used for the recently released Sensei 310 and updated the sensitivity settings to match the Sensei Ten.
Thoughts:

The device actually comes with five CPI presets. Is this what is referred to as "sensitivity presets"? Setting these values to anything within the range have no apparent effect.
The Wheel color can as of now not be configured separately. Calling the --wheel-color command ultimately does nothing. The color of both leds are updated by the --logo-color command.
It seems the led_id property is ignored by the software. Changing it, or even removing it completely does not prevent the software from updating the mouse color. Updating the LED indexes to [0,1] in the rgbuniversal_format object did not matter.

Questions:

I kept uninstalling and reinstalling the rivalcfg python package to make sure that my configuration changes were updated. Is there a quicker way to do this?

Device specifications:
https://steelseries.com/gaming-mice/sensei-ten#specs

Hello,
thank you for your interest in this project. I will first try to answer your question in this comment and then, in an other comment, I will try to guide you to reverse engineer the mouse to have a proper support of it 😁

The device actually comes with five CPI presets. Is this what is referred to as "sensitivity presets"? Setting these values to anything within the range have no apparent effect.

Yes, "sensitivity" preset is the CPI preset.
It seems you are right, I see five CPI presets in the default configuration of the mouse (extracted from the Windows SSE3 database):
{
  // ...
  "raw_cpi": {"level1": 400, "level2": 800, "level3": 1200, "level4": 2400, "level5": 3200},
  // ...
}

I suppose you can switch CPI preset using the button under the wheel, but you have no way to know which preset you are currenlty using. To test this feature, set all five preset to the lowest sensitivity, then move your mouse to "feel" the speed of the pointer. Then you can try to set all five preset to the higher value and move the mouse to see if something changed.

The Wheel color can as of now not be configured separately. Calling the --wheel-color command ultimately does nothing. The color of both leds are updated by the --logo-color command.

That's strange, I find two led configuration in the default config:
{
  // ...
  "logo_lighting": {
    // ...
  },
  // ...
  "wheel_lighting": {
    // ...
  },
  // ...
}

It seems the led_id property is ignored by the software. Changing it, or even removing it completely does not prevent the software from updating the mouse color. Updating the LED indexes to [0,1] in the rgbuniversal_format object did not matter.

The format of the packet sent to the Sensei Ten to configure RGB LEDs is probably different from the one of the Sensei 310 (the color packets on recent SteelSeries mice are similar but not exactly identical).

I kept uninstalling and reinstalling the rivalcfg python package to make sure that my configuration changes were updated. Is there a quicker way to do this?

You are not obligated to reinstall the software after each change, you should be able to run your dev version using the following command (from the root dir of the project):
python -m rivalcfg [args]

Reverse engineering a mouse (if you want to try, no obligation)
The best way to add support of the mouse is to play with the SteelSeries Engine 3 (SSE3) on Windows while capturing the packet between the mouse and the computer. We can then analyze the packets to understand how to configure the mouse. Don't be afraid, it is easier than it seems. 😉
For the "packet capturing" part, I wrote an article. It is in French, but Google translate can help: https://blog.flozz.fr/2016/03/27/steelseries-rival-100-reverse-engineering-dun-peripherique-usb/
Do not hesitate if you have question or if you need help with the capture of the packets.
Then, change one setting a time in the SSE3 to see what is sent to the mouse. You can post here the captured packet along with the setting you changed (and the value you set). You can take this post as an example: https://github.com/flozz/rivalcfg/issues/82#issuecomment-577256710
The best thing to do is to start with a simple value like the CPI:

Change the first CPI preset to the lower value and save the packet.
Change the first CPI ppreset to the higher value and save the packet.
Change the second CPI preset to any value and save the packet.
Change the third CPI preset to any value and save the packet.

this should be sufficient to understand how to configure all CPI preset :)

for reference, I put here the default config of the Sensei Ten extracted from the SSE3 database:
{
  "batch_resolution" : {"enable_mask": 31, "active_level": 1,
    "resolution_1" : 8,
    "resolution_2" : 16,
    "resolution_3" : 24,
    "resolution_4" : 48,
    "resolution_5" : 64},
  "raw_cpi": {"level1": 400, "level2": 800, "level3": 1200, "level4": 2400, "level5": 3200},
  "polling_rate": {"level": 1},
  "exact_accel": {"level": 0},
  "exact_aim": {"level": 0},
  "free_move": {"level": 0},
  "button_mappings": {
    "buttons": [
      {"function": 1, "key_codes": [0, 0, 0, 0]},
      {"function": 2, "key_codes": [0, 0, 0, 0]},
      {"function": 3, "key_codes": [0, 0, 0, 0]},
      {"function": 4, "key_codes": [0, 0, 0, 0]},
      {"function": 5, "key_codes": [0, 0, 0, 0]},
      {"function": 81, "key_codes": [78, 0, 0, 0]},
      {"function": 81, "key_codes": [75, 0, 0, 0]},
      {"function": 48, "key_codes": [0, 0, 0, 0]}
    ],
    "no_live_deploy": 1
  },
  "wheel_mappings": {
    "wheels": [
      {"function": 49, "key_codes": [0, 0, 0, 0]},
      {"function": 50, "key_codes": [0, 0, 0, 0]}
    ],
    "no_live_deploy": 1
  },
  "logo_lighting":{
    "type": 1,
    "has_direction": 0,
    "direction_type": 0,
    "direction_inverted": 0,
    "focal_x": 0,
    "focal_y": 0,
    "speed": 1000,
    "scale": 1,
    "num_colors": 3,
    "colors": [
      { "r":255, "g":0,   "b":0   },
      { "r":0,   "g":255, "b":0   },
      { "r":0,   "g":0,   "b":255 },
      { "r":0,   "g":0,   "b":0   },
      { "r":0,   "g":0,   "b":0   },
      { "r":0,   "g":0,   "b":0   },
      { "r":0,   "g":0,   "b":0   },
      { "r":0,   "g":0,   "b":0   },
      { "r":0,   "g":0,   "b":0   },
      { "r":0,   "g":0,   "b":0   },
      { "r":0,   "g":0,   "b":0   },
      { "r":0,   "g":0,   "b":0   },
      { "r":0,   "g":0,   "b":0   },
      { "r":0,   "g":0,   "b":0   }
    ],
    "positions": [
      { "pos": 0  },
      { "pos": 33 },
      { "pos": 66 },
      { "pos": 0  },
      { "pos": 0  },
      { "pos": 0  },
      { "pos": 0  },
      { "pos": 0  },
      { "pos": 0  },
      { "pos": 0  },
      { "pos": 0  },
      { "pos": 0  },
      { "pos": 0  },
      { "pos": 0  }
    ],
    "initial_color": { "r":255, "g":0, "b":0 },
    "react_color": { "r":0, "g":0, "b":0, "time": 0 },
    "trigger_mask": 7,
    "settings_mask": 0
  },
  "wheel_lighting":{
    "type": 1,
    "has_direction": 0,
    "direction_type": 0,
    "direction_inverted": 0,
    "focal_x": 0,
    "focal_y": 0,
    "speed": 1000,
    "scale": 1,
    "num_colors": 3,
    "colors": [
      { "r":255, "g":0,   "b":0   },
      { "r":0,   "g":255, "b":0   },
      { "r":0,   "g":0,   "b":255 },
      { "r":0,   "g":0,   "b":0   },
      { "r":0,   "g":0,   "b":0   },
      { "r":0,   "g":0,   "b":0   },
      { "r":0,   "g":0,   "b":0   },
      { "r":0,   "g":0,   "b":0   },
      { "r":0,   "g":0,   "b":0   },
      { "r":0,   "g":0,   "b":0   },
      { "r":0,   "g":0,   "b":0   },
      { "r":0,   "g":0,   "b":0   },
      { "r":0,   "g":0,   "b":0   },
      { "r":0,   "g":0,   "b":0   }
    ],
    "positions": [
      { "pos": 0  },
      { "pos": 33 },
      { "pos": 66 },
      { "pos": 0  },
      { "pos": 0  },
      { "pos": 0  },
      { "pos": 0  },
      { "pos": 0  },
      { "pos": 0  },
      { "pos": 0  },
      { "pos": 0  },
      { "pos": 0  },
      { "pos": 0  },
      { "pos": 0  }
    ],
    "initial_color": { "r":255, "g":0, "b":0 },
    "react_color": { "r":0, "g":0, "b":0, "time": 0 },
    "trigger_mask": 7,
    "settings_mask": 0
  },
  "logo_element": {
    "pos": {
      "x": 0,
      "y": 0
    },
    "effect_index": 0
  },
  "wheel_element": {
    "pos": {
      "x": 0,
      "y": 0
    },
    "effect_index": 1
  }
}

Hey @flozz, how did you extract that file? Is this the .edevice file?

@FFY00 no, I was not able to understand how to use .edevice files yet...
There is a SQLite database that is built when installing SSE3, it contains the list of all devices with their default config. :)

Released in rivalcfg v3.12.0.
Thank you :D


Feature/changing colors and front design

Pull Request Test Coverage Report for Build<PHONE_NUMBER>2
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>8:
0.0%

Covered Lines:
4

Relevant Lines:
4

💛  - Coveralls


Powershell statement requires quotes.

Otherwise, powershell complains:
/path/to/service_account_key.json : The term '/path/to/service_account_key.json' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

Thanks for pointing this out. Merging!


feat(core): NeonObject

This introduces the NeonObject interface and adds them to the original few objects that implements them.
A breaking change was introduced to Network and Protocol as they exported the configuration style object instead. Now, the export method will work as normal to export it as a JSON object and a new method toConfiguration is added that will export it as PascalCased JSON which was the old behavior for export.

400 points snowypowers

https://neoscan.io/transaction/44C84C9E7582DC00411BC9D9D075F6993BA7E203FFDDE366E21DFEBD125EA580


add parry hitbox+logic

be careful with hitbox logic, since OnHit is called both when something enters and when something stays in the hitbox (maybe have a parrying state)


Data invalid

Hello Volcan
The date 2016/04/31 for version 2.0.13 does not exist, it's just a small detail.
Greetings.

Thanks :) It was about to 23:55 while publishing so was simple math error


measure plugin is not working over geojson layer

measure plugin is not working over geojson layer. there is any way to implement this plugin over any geojson polygon layer.

Even if it's an old post, this could help someone.
I'm not completly sure why, but the geojson layers don't manage click events exactly like other layers. I tried to hack it in leaflet, but the projet is simply too big for a quick hack.
In my fork I "fixed" it (it's not really a fix). I simply added a new custom event listener. Every time that I was listening an event on a geojson layer I simply added
map.fire('measure:click', e);

to be able to receive the blocked event in leaflet.measure.


Case insensitive keywords?

I've got a use case where the keywords in my language are case insensitive but other things (e.g. the contents of strings) aren't. Is there any way I can make a lexer that recognizes these? I tried keyword: [/foo/i, ...] but it complains that the "/i" flag isn't allowed.

Right. Moo combines all the tokens into a single RegExp, so supporting both case-sensitive and insensitive tokens is difficult. Can you tell me more about the language? That might help :-)
One suggestion would be to do e.g. /[fF][oO][oO]/. You could write a function to generate such RegExps from strings, you needn't do it by hand. :-)

Ah, yeah. It's a pretty simple DSL where each line starts with a case insensitive keyword, e.g.:
enter: (some-terrible-lisp-expression). ;comment
Enter: (another-terrible-lisp-expression).
delete: "string".

etc.
I think generating the individual cases won't be too hard, so that will probably work. Thanks.

Glad I could help! :-)
Be aware that you might run into an edge case if you have identifiers too: https://github.com/tjvr/moo#keywords —moo only handles that if your keywords are specified as strings.

Maybe it would be a good idea to add something like this:
moo.compile({
  evenOdd: { caseInsensitive: true, keyword: ['even', 'odd'] }
})


Custom Playbook Name Proposal

I do believe that the easiest way for you to be able to move forward w/o having to modify the apb-base would be to simply update the Dockerfile of the impacted APBs.
Instead of this example:
FROM ansibleplaybookbundle/apb-base
LABEL "com.redhat.apb.spec"="..."
ADD playbooks /opt/apb/actions
ADD roles /opt/ansible/roles
RUN chmod -R g=u /opt/{ansible,apb}
USER apb

Your APB's dockerfile could look something like:
FROM ansibleplaybookbundle/apb-base
LABEL "com.redhat.apb.spec"="..."

COPY playbooks/apb_number1.yml /opt/apb/actions/provision.yml
COPY playbooks/apb_number1.yml /opt/apb/actions/deprovision.yml

ADD roles /opt/ansible/roles
RUN chmod -R g=u /opt/{ansible,apb}

USER apb

I'm not clear what these projects look like structure wise but I suspect you could put the files in the correct place at build time w/o breaking the pattern.

That would work @djzager, thanks

Can we summarize the results of the F2F discussion here? It sounded like maybe this should get either updated, or closed, and we should work with @dymurray to implement some best practices based on where he sees this going.

A best practices doc would cover this


Evaluation failed ( when inside child process)

So I have trying to use puppeteer for writing tests. Everything worked great, until I started using nyc for coverage reports.
Everytime I run puppeteer as child process of nyc, it throws an exception shared below.
  Error: Evaluation failed: ReferenceError: cov_1oomibe77f is not defined
    at e (<anonymous>:1:27)
    at HTMLFormElement.<anonymous> (<anonymous>:1:93)
    at ElementHandle.evaluate (/Users/myapp/node_modules/puppeteer/lib/ElementHandle.js:56:13)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:169:7)

To isolate the issue, I created this repo https://github.com/thetutlage/puppeteer-tests. Which has an index.js file to start the browser and submit a form.

Now if run the file as node index.js it works great.
But if I run it as ./node_modules/.bin/nyc node index.js the same exception is thrown. 100% of times reproducible.

I am trying to run my node process as a child process but not under nyc to see if the problem persist, but still want to create an issue to have some feedback from you guys too.
Thanks

This looks like it is because nyc messes with the JavaScript in order to provide coverage data, but we run .toString() on some of functions and send the strings into the page.

Yes, I tried running the main node process inside a child process and everything works great. For sure it has something to do with nyc or any other instrumentation tools.
Would you mind keeping this issue open, meanwhile I dig into nyc codebase to understand which part causes this issue?

@thetutlage from a brief analysis, that's what I see.
NYC/istanbul does the following:

sets up a global cov_XXX variable in the node.js context
transforms the code so that every line writes to the cov_XXX variable, reporting coverage

Puppeteer is a node.js library, but it runs certain parts of the code in a browser context (for example, the page.evaluate method does just this).

NYC knows nothing about browser, thus it doesn't setup the cov_XXX variable there.
NYC also doesn't know which code Puppeteer will execute in browser context and which will be run in node.js, so it just transforms everything

As a result, it tries to refer to the cov_XXX variable from-inside the browser, and this naturally yields an exception during code evaluation:
  Error: Evaluation failed: ReferenceError: cov_1oomibe77f is not defined
    at e (<anonymous>:1:27)
    at HTMLFormElement.<anonymous> (<anonymous>:1:93)
    at ElementHandle.evaluate (/Users/myapp/node_modules/puppeteer/lib/ElementHandle.js:56:13)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:169:7)

Would you mind keeping this issue open, meanwhile I dig into nyc codebase to understand which part causes this issue?

I don't think there's anything we can do in puppeteer to fix this issue. Do you still want this issue to be open?

Nope, it's fine to close the issue. Thanks for sharing insights 👍

@thetutlage Did you find any workaround? E.g. maybe use // istanbul:ignore comments around evaluate(), or exclude the test files from instrumentation completely?

It seems that ignoring doesn't work because of https://github.com/istanbuljs/nyc/issues/890

I just wanted to report that ignoring does work. I am able to work around this issue by putting /* istanbul ignore next */ at the beginning of every page.evaluate call:
/* istanbul ignore next */
await page.evaluate(data => { return data*2; }, 2);

Hi, I have same problem, here is my project https://github.com/frantallukas10/youtu-get
I try to create test for my function where I use puppeteer for get every title and id from youtube playlist
here is my test: https://github.com/frantallukas10/youtu-get/blob/master/tests/test.js
and here is my function: https://github.com/frantallukas10/youtu-get/blob/master/src/main.js
thank you for your help or information... =)

maybe I have same problem https://github.com/GoogleChrome/puppeteer/issues/5175#issue-523897962
anybody can help me please?


Jump in finger position caused by capacitive touch or press on button from gestures

Unfortunately, it appears that having thumb approximation enabled on full-tracking enabled games leads to the thumb looking jumpy, as the hand tracking in apps (like SteamVR home) seems prioritize finger positions from capacitive touch first before looking at skeletal input. This appears to happen to the index finger due to the trigger gesture as well.
Perhaps there's a way to have it automatically detect what games don't have analog thumb support and enable from there (maybe by querying a predetermined list), but that doesn't sound like a perfect solution either.
Until there's a definite solution to this, the easiest solution is to default the thumb approximation to false and have people turn it on when they plan to play a game that requires index emulation. This is a setting that would really benefit from real-time updating.
Currently, my testing platform is very laggy because I'm using Virtual Desktop over a non-local network, so it's possible that what I'm noticing is caused by lag and not actually from the approximation.

After testing on a more robust setup, this does not appear to be an issue and was just caused by lag.


How to be keep up with security upgrades?

Describe the bug
Subscribing to all security issues on GitHub is far too work intensive for anyone simply interested in whether they need to upgrade.
Expected result
Some easily consumable, automatically updated list of security updates, including at least the package name, the new version number, and a CVE link.
Actual result
Keeping up with security updates is a non-starter.
Additional context
Arch Linux has at least a web feed, Ubuntu has a mailing list, and I expect every major distro has something similar.

If you follow a stable channel, you are pretty much just getting security updates. I'm not saying that it wouldn't be nice to have some way to list security issues, but presently the best thing is just to always update stable.

Could also filter PR's on github with is:pr label:"1.severity: security". Though I'm not sure everything gets labeled properly.

@peterhoeg

[…] presently the best thing is just to always update stable.

The problem with that approach is having to upgrade "arbitrarily often" to try to stay on top of security updates. That is not a viable strategy for someone using NixOS as a server OS, unless they have already perfected a continuous delivery pipeline and are willing to use lots of extra resources to deploy whenever anything at all upstream changes. And as an end user updating very often makes the probability of breakages much higher than it would otherwise be. I'm not saying the probability would be high — my experience with Arch Linux was that running an update approximately daily was much less error prone than other distros — but it would be higher, and for a reason which it should be possible to remove.
A workaround would be to have an upgrade script which only actually upgrades when there's a security update to any of the installed packages. Then running it very often would not be such a problem.

@worldofpeace That's not a viable approach for anyone except extreme die-hards. First, GitHub doesn't provide a feed of PR updates (at least not on that filter page), and implementing one myself is just out of the question. Second, such a feed would then have to be filtered to only contain merge events, and only those for packages I have already installed. Third, knowing that a PR has been merged is not the same as the PR code being available in the NixOS repositories. So a bunch of work would still be needed to tie the PR to an actual package release to make the entire system usable.

It would be nice if https://github.com/NixOS/nixpkgs/security/advisories could be used for this purpose, similar to what arch linux has going on. I only suggested a way to keep up with security updates, as we currently don't have any other way to do this.

I expose feeds per label for myself at https://feed.nix.tx0.co, which I subscribed to in Thunderbird.
It's a little crude, and has no guarantees for accuracy or uptime, but it's what I use to be notified of interesting issues.
Security feed: https://feed.nix.tx0.co/1.severity%3A_security/atom.xml (rss might work, not tested)

I'm working on a little something that extracts the data from the PR title/body using regex
Not the world's most reliable solution, but should work for creating a feed that yields the needed data

fwiw I put together a similar script a while ago. It tries to figure which channel the system is running on and scans any commits between system state and channel head. Unfortunately the GitHub API only allows going back in time, not forward from a given commit, so the script has to fetch a bunch of commits on a best-effort basis.
see here https://github.com/wamserma/nixos-check-update


open editors in explorer section is not supposed to be important.

Open editors is not so important when tab is available in vs code. open editor and tab are doing just same there. I guess Tab is only better.
This is just a suggestion but I always appreciate the decision what vs code team is making to make vs code a better editor.
Thanks vs team

You can hide the "Open Editors" section via this setting: "explorer.openEditors.visible": 0


[SDPA-3101] Update width to 100% to correctly fit 25% + 75% split.

JIRA issue: https://digital-engagement.atlassian.net/browse/SDPA-3101
Changed

Update width to 100% to correctly fit 25% + 75% split.

NOTE: Some discussion was had on if this will affect other browsers. Checking:
Firefox, Safari, Chrome, Edge, and IE11, I couldn't see any discernible differences.
Screenshots

Fixed issue in edge:

Comparison before / after 100% change on Chromium browser for: demo-landing-page, homepage, standards-and-guidelines.

I will add a test on grid for assurance.


Adds pop-os btrfs-LVM-luks guide for 21.04

Due to changes in the Pop!_OS 21.04 installation workflow, now creating the user account during installation and not on the first boot, it is required to perform an additional step and copy the user home from @/home to @homes/.
Therefore I have updated your 20.04 guide and added an additional passage for this.
This fixes the installation issues as mentioned in #14 for me.

Thanks! I will now install Pop following your proposed guide and maybe add some slight changes to it!


merge from arlac77/template-arlac77-github,arlac77/template-esm-only

package.json

chore(deps): add ^17.1.1 remove ^17.1.0 (devDependencies.semantic-release)

.npmignore

chore: add .github ()
chore: add  remove  ()
chore: remove  ()

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


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

Comment:
No response

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added user @hmaarrfk in conda-forge/ffmpeg-feedstock#183.


Path/URL/URI manipulation utilities?

Feature request:
Manipulating file paths, URIs and URLs (parsing, un-parsing, etc.) seem like the kind of "small but fiddly to do right" operation that shows up in a lot of places and which ABSL is seeking to cover.
I don't know where this would fit in the priorities, but I personally would find use for it, so I'd like to track when/if it gets done.

File may happen, but it is probably very far away. I've never used it myself, but if you can use C++17, filesystem is part of the standard library: https://en.cppreference.com/w/cpp/filesystem
I don't think URLs is anywhere on our roadmap.

It's not a stretch to assume that some projects using abseil follow the Google C++ Style Guide, which writes

In addition to what's described in the rest of the style guide, the following C++ features may not be used:
...

The <filesystem> header, which does not have sufficient support for testing, and suffers from inherent security vulnerabilities.


f-droid: the "start at boot" option is not supported on some devices

The "start at boot" option added in https://github.com/vector-im/riot-android/issues/412 seems ignored on some devices
see: https://matrix.to/#/!GnEEPYXUhoaHbkFBNX:matrix.org/$151792196912TpHjZ:vnti.de

Thx for writing this issue (I'm Blue Ghost), but after a bit more testing and having a look into the logs of riot, it not seems to be a "start at boot" problem: Riot is shown in the notification area and the new message is shown in the logfile of riot. But I miss the notification sometimes.
It seems to be a crazy problem on my phone 🤔. E.g. when the phone is plugged in everything works fine. So from my side you could close this bug.

Thx @lugino-emeritus for the feedback


Updates for UG and DG

This PR will make the following changes for the UG and DG:

Updated the screenshot images for the UG to not include import buttons, and include the resize button for images missing this.
Updated the HTML tags in DG
Updated the markdown syntax in DG
Resized the undo redo activity diagram in the DG
Added use cases in the DG
Added manual test case for saving, archiving, editing and resizing feature in DG
Updated archive feature description in UG, including glossary for JSON explanation

This PR is for review and is ready to merge thereafter.

Codecov Report

Merging #295 (959f7da) into master (c4a2b61) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #295   +/-   ##
=========================================
  Coverage     65.77%   65.77%
  Complexity      590      590
=========================================
  Files            90       90
  Lines          2092     2092
  Branches        244      244
=========================================
  Hits           1376     1376
  Misses          647      647
  Partials         69       69

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Importing unicode_literals into histogram example notebook

PR title says it all - thumbnailing has to be run with Python 2 and this should allow the thumbnail to be generated for this example.

As it turns out this may not actually help and the from __future__ import needs to be in the thumbnailer script. Problem is I can't reproduce the unicode error seen in doc building so I can't test whether that would help either.
@philippjfr  Happy to see this PR closed and I am happy to merge a PR with this import in the thumbnailer script in nbpublisher if it helps fix the issue with the thumbnail for this notebook.

I'll close and see if I can fix the issue myself in the thumbnailer. Thanks for submitting the fix though.


cloudtrail plugin: Support S3-based SNS ingestion

Motivation
A common practice is to use org-wide cloudtrails. These trails write events to s3 nested under account number. As it stands today, there is no easy way to selectively ingest only specific accounts.

Feature
We would like to selectively ingest cloudtrail data from aws accounts in an org-trail s3 bucket by way of configuring s3 bucket notifications with prefixes and pointing them to SNS.  Currently the plugin expect SNS notifications directly from cloudtrail.

Alternatives

Additional context
Looking at the snsMessage struct, it appears that the plugin will only ingest directly from cloudtrail. The proposal is to introduce a flag/param that can be used to direct the plugin to read SNS originating from s3.

cc @ldegio


Make log profile IAM credentials available within the pod via the imds proxy.

Add second IAM proxy for log profile.
We need to provide credentials to the log upload profile in the network namespace of the pod. We add an env variable to the imds proxy to add a second assume role proxy if started by the imds-cni hooks.
These credentials are available at /latest/meta-data/iam/logging/...
Additionally added a credential provider to the uploader package for loading them.  This is just a helpful convenience for customers who might want to load the creds.
For more context review this problem doc

Why don't we always wire up the /logging route on the IMDS, and if the logging role is equal to the normal role, then just point them at the same handler?

This seems a reasonable change, might as well always provide it and have it fall through to the task profile.

An alternate idea might be to use a special header, or user agent to indicate that this is coming from the logging daemon and the IMDS does the right thing and hands back the right creds.

Yes this likely will increase sts load.  I only say likely because as far as I could tell the agents were doing this previously every time a uploader was created in the executor https://github.com/Netflix/titus-executor/blob/master/executor/runner/runner.go#L372
We talked to Mike Grima about this on Tuesday and he suggested that if we're only doing it once per agent we're probably ok.  I admittedly didn't worry too much since our workloads on real kubelet are 0 right now.  I believe we could add logic to do agent level caching of these creds since almost all containers will be using the same profile on the same agent.
@alekar curious for you to weigh in on this.

Why don't we always wire up the /logging route on the IMDS, and if the logging role is equal to the normal role, then just point them at the same handler?

This seems a reasonable change, might as well always provide it and have it fall through to the task profile.

An alternate idea might be to use a special header, or user agent to indicate that this is coming from the logging daemon and the IMDS does the right thing and hands back the right creds.

Yes this likely will increase sts load.  I only say likely because as far as I could tell the agents were doing this previously every time a uploader was created in the executor https://github.com/Netflix/titus-executor/blob/master/executor/runner/runner.go#L372
We talked to Mike Grima about this on Tuesday and he suggested that if we're only doing it once per agent we're probably ok.  I admittedly didn't worry too much since our workloads on real kubelet are 0 right now.  I believe we could add logic to do agent level caching of these creds since almost all containers will be using the same profile on the same agent.
@alekar curious for you to weigh in on this.

I think we can handle the scaling concern if it's gradual, so I'm not worried about scale today. More so fewer code paths of how the server gets setup, and how logging creds are retrieved. I like the idea that the logger client supplies a custom header on fetching creds, or a custom user agent, and the IMDS knows to respond with different creds. That way you could test the log uploader on a vanilla EC2 instance because the vanilla IMDS would just ignore it.

I think we can handle the scaling concern if it's gradual, so I'm not worried about scale today. More so fewer code paths of how the server gets setup, and how logging creds are retrieved. I like the idea that the logger client supplies a custom header on fetching creds, or a custom user agent, and the IMDS knows to respond with different creds. That way you could test the log uploader on a vanilla EC2 instance because the vanilla IMDS would just ignore it.

I think we can start w/o caching. Then move to per instance caching if required as we discussed w/ Mike. Hopefully off-box STS will get prioritized and we won't have to worry about STS rate limiting.

I think we can start w/o caching. Then move to per instance caching if required as we discussed w/ Mike. Hopefully off-box STS will get prioritized and we won't have to worry about STS rate limiting.


Racket ignore files

.bak as temp files in root and compiled as default build folder

Closing in favour of #1616


Prefix UIView extensions properties with "trikot" for viewmodels

Description
All (or at least, the most used and problematic) public properties used for binding the ViewModels on UIView extensions are now prefixed with "trikot".
Motivation and Context
This prevents naming conflicts with host applications.
How Has This Been Tested?
Tested in my application. A simple rename in all UIViews did the trick :).
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)

Breaking change (fix or feature that would cause existing functionality to change)
Don't forget to add a breaking change note in CHANGELOG.md

To follow Semantic Versioning guidelines, we would have to bump the major version for the next release (since we’re > 0.x).
@npresseault Are we ready for that?

It is usually done in a separate commit so that we can revert changes independently but I actually don't mind.

Sure, I'll bump on master before deploying.


Pr183

ms.assetid: 930e758f-bd50-46b4-a3a4-9857110f17b4
author: shirgall
ms.author: kathydav
-ms.date: 08/14/2017
+ms.date: 08/30/2017
Supported FreeBSD virtual machines on Hyper-V
@@ -26,9 +26,9 @@ The following feature distribution map indicates the features in each version. T

(blank) - Feature not available

-|Feature|Windows Server operating system version|11.1|11|10.3|10.2|10 - 10.1|9.1 - 9.3, 8.4|
+|Feature|Windows Server operating system version|11.1|11.0|10.3|10.2|10.0 - 10.1|9.1 - 9.3, 8.4|
|-|-|-|-|-|-|-|-|
-|Availability||Built in|Built in|Built in|Built in|Built in|Ports |
+|Availability||Built in|Built in|Built in|Built in|Built in|Ports |
|Core|2016, 2012 R2, 2012, 2008 R2|✔|✔|✔|✔|✔|✔ |
|Windows Server 2016 Accurate Time|2016|✔||||||
|Networking||||||||
@@ -70,26 +70,28 @@ The following feature distribution map indicates the features in each version. T

Suggest to Label Disk Devices to avoid ROOT MOUNT ERROR during startup.

The virtual DVD drive may not be recognized when BIS drivers are loaded on FreeBSD 8.x and 9.x unless you enable the legacy ATA driver through the following command.

dd if=/dev/da1 of=/dev/da1 count=0

gpart recover da1

echo ‘hw.ata.disk_enable=1’ >> /boot/loader.conf

shutdown -r now

9126 is the maximum supported MTU size.

In a failover scenario, you cannot set a static IPv6 address in the replica server. Use an IPv4 address instead.

-5. KVP is provided by ports on FreeBSD 10. See the FreeBSD 10 ports on FreeBSD.org for more information.
+5. KVP is provided by ports on FreeBSD 10.0. See the FreeBSD 10.0 ports on FreeBSD.org for more information.

KVP may not work on Windows Server 2008 R2.

-7. To make VHDX online resizing work properly in FreeBSD 11, a special manual step is required to work around a GEOM bug which is fixed in 11+, after the host resizes the VHDX disk - open the disk for write, and run “gpart recover” as the following.

set hw.ata.disk_enable=1

boot

+7. To make VHDX online resizing work properly in FreeBSD 11.0, a special manual step is required to work around a GEOM bug which is fixed in 11.0+, after the host resizes the VHDX disk - open the disk for write, and run “gpart recover” as the following.

dd if=/dev/da1 of=/dev/da1 count=0

gpart recover da1

Additional Notes: The feature matrix of 10 stable and 11 stable is same with FreeBSD 11.1 release. In addition, FreeBSD 10.2 and previous versions (10.1, 10, 9.x, 8.x) are end of life. Please refer here for an up-to-date list of supported releases and the latest security advisories.
+Additional Notes: The feature matrix of 10 stable and 11 stable is same with FreeBSD 11.1 release. In addition, FreeBSD 10.2 and previous versions (10.1, 10.0, 9.x, 8.x) are end of life. Please refer here for an up-to-date list of supported releases and the latest security advisories.
+
See Also

Feature Descriptions for Linux and FreeBSD virtual machines on Hyper-V

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

twitter_data.docx


dag-cbor: add ability to validate input without fully deserializing

To implement https://github.com/filecoin-project/FIPs/pull/483 securely in the FVM, we need to validate that entry values are well-formed DAG-CBOR payloads. All we need is to perform syntatical validation without incurring in any serde costs/overheads.

Based on https://github.com/filecoin-project/FIPs/pull/483/files#r1013446172 comment, it sounds being more than syntactical validation, e.g. key ordering. I guess using the Serde code path wouldn't add much overhead, if the deserialized values are dropped (I assume something like that is possible, I haven't tried).
If a custom validation function is added, it should be benchmark against a Serde version, to see if the performance justifies having a separate code with potentially introduces bugs.

@vmx How would a serde path work here? This is a dynamic data structure whose schema we don't know.

@raulk: You can deserialize to an Ipld enum. See https://github.com/ipld/serde_ipld_dagcbor/blob/ea9b594421a47ac431627781a65d641ff54a3f2b/tests/de.rs#L88-L98 for a full example.

Yes I know, but validating the whole input would imply deserialising into ipld::Ipld, which uses owned data, so it's not zero-copy syntactical validation?

Here's a PR: https://github.com/ipld/libipld/pull/159 I'm working on removing the recursion. I have some ideas.

Yes I know, but validating the whole input would imply deserialising into ipld::Ipld, which uses owned data, so it's not zero-copy syntactical validation?

Correct. Though I think zero-copy should be possible with Serde, it's just not implemented in serde_ipld_dagcbor.

@Stebalien hinted that deserializing into IgnoredAny may do the trick here.

Unfortunately, we've found that that doesn't quite work as upstream (cbor4ii) doesn't validate minimality.

as upstream (cbor4ii) doesn't validate minimality.

We already kind of patch upstream in serde_ipld_dag_cbor, could it be integrated there? I'd surely be interested in pushing as much as possible upstream.


Mat-Paginator: Ensures elements with an ARIA role that require child roles contain them.

Reproduction
Use StackBlitz to reproduce your issue: https://stackblitz.com/angular/mkqleegjgor?file=app%2Fpaginator-overview-example.ts
Steps to reproduce:

Go to the Preview window or copy the URL from Preview window and browse with the browser having Accessibility Insight tool as extension.
Run the Accessibility Insight(Keros) tool and check the Result.

Expected Behavior
Accessibility Insight should not report any violations for Paginator Control.
ARIA Role required by Child Element.
Actual Behavior
Ensures elements with an ARIA role that require child roles contain them.

Environment

Angular:~0.901.1
CDK/Material:5.2.5
Browser(s):Edge
Operating System (e.g. Windows, macOS, Ubuntu): Window

See the discussion here: https://github.com/angular/components/pull/20082#issuecomment-686622547. Our select is based on a newer version of the ARIA spec that doesn't require an input to be placed inside a combobox. A lot of these automatic accessibility checks haven't been updated to the latest spec yet.

@crisbeto I am not running older version of Material .I am running Latest version of Material(i.e 10.2.1) and found same Accessibility Insight Issue. Please refer below screen .

Can you please reopen the reported Bug

The thread I mentioned above (https://github.com/angular/components/pull/20082#issuecomment-686622547) refers to the latest version.


External links

Would this work between pages on different domains?
The use case I'm thinking of would be transitioning between three subdomains.

This is not possible due a pushstate Api security limitation. See here for more details: https://github.com/luruke/barba.js/issues/46

OK, thanks. (I somehow didn't find that issues when I searched)


[Event Request] Page 283 Recurring General Journal

The following events are required for this object:
    [IntegrationEvent(false, false)]
    local procedure OnBeforeUpdateBalance(var GenJournalLine: Record "Gen. Journal Line"; xGenJournalLine: Record "Gen. Journal Line"; var Balance: Decimal; var TotalBalance: Decimal; var ShowBalance: Boolean; var ShowTotalBalance: Boolean; var IsHandled: Boolean)
    begin
    end;

    local procedure UpdateBalance()
    var
        IsHandled: Boolean;
    begin
        //EVENT REQUEST
        IsHandled := true;
        OnBeforeUpdateBalance(Rec, xRec, Balance, TotalBalance, ShowBalance, ShowTotalBalance, IsHandled);
        if not IsHandled then
            GenJnlManagement.CalcBalance(
              Rec, xRec, Balance, TotalBalance, ShowBalance, ShowTotalBalance);
        //EVENT REQUEST
        BalanceVisible := ShowBalance;
        TotalBalanceVisible := ShowTotalBalance;
        if ShowTotalBalance then
            NumberOfRecords := Count();
    end;

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


Full names next to usernames are no longer displayed

Hey,
since when are the full names no longer displayed next to the username? Has the function been removed because of the hover card? If so, then the line in the README.md would have to be deleted. Tested under GNU/Linux and Windows.

Full names of comment authors are shown next to their username.

For me everything still works...

You have some other extension/userscript conflicting?

@rzpio they are not displayed by default if the comment or action is performed by you. You won't see your name displayed by your username.
Is that what you are seeing?

Haha, the example was perhaps chosen somewhat unluckily. 🤣 No, I don't see the full name for others either. I have not activated any other extensions or user scripts. Works neither in Firefox nor in Brave.

This feature is using GraphQL API v4. Did you added an API token? If not, maybe you hit your GraphQL API resource limitations.

I didn't add a token. I'm not familiar with the API, but I don't think I've reached the limit in my home network. I probably can't see how many points I've used for the API anywhere, can I?

Try to create one (instructions are in the Settings of GitHub Refined) and see if it solves your problem.

Yeah, it worked. Thank you very much, @jerone! Interesting, some time ago it worked without a token.

Oh and you can check your rate limit here.

@rzpio commented on Mar 9, 2019, 4:51 PM GMT+1:

Yeah, it worked. Thank you very much, @jerone! Interesting, some time ago it worked without a token.

Great. The more you work on GitHub, the more API calls you do. There are multiple API call in GitHub Refined. At some point that might add up. But with the token you should be fine.

Oh and you can check your rate limit here.

Cool, I didn't know that.

Great. The more you work on GitHub, the more API calls you do. There are multiple API call in GitHub Refined. At some point that might add up. But with the token you should be fine.

Ah, that could explain that. Thanks for the help. :smile:


Fixed #30330 -- Fixed setting of primary key to None during fast-delete.

@apollo13 Thanks!

Ticket Link


How the tflite file has been created for a frozen file from the simple audio recognition tutorial?

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04):Ubuntu 16.04
TensorFlow installed from (source or binary): source
TensorFlow version (or github SHA if from source):1.14

Provide the text output from tflite_convert
# Copy and paste here
``
 Array AudioSpectrogram, which is an input to the (Unsupported TensorFlow op: Mfcc) operator producing the output array Mfcc, is lacking min/max data, which is necessary for quantization. If accuracy matters, either target a non-quantized output format, or run quantized training with your model from a floating point checkpoint to change the input graph to contain min/max information. If you don't care about accuracy, you can pass --default_ranges_min= and --default_ranges_max= for easy experimentation.
Fatal Python error: Aborted
Also, please include a link to a GraphDef or the model if possible.
https://github.com/tensorflow/docs/blob/master/site/en/r1/tutorials/sequences/audio_recognition.md

**Any other info / logs**

Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.
tflite_convert \
--output_file=model.tflite \
--graph_def_file=/home/unizen/Downloads/my_frozen_graph.pb \
--inference_type=QUANTIZED_UINT8 \
--input_shapes=16000,1:1,1\
--input_arrays=decoded_sample_data,decoded_sample_data:1 \
--output_arrays=labels_softmax \

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04):Ubuntu 16.04
TensorFlow installed from (source or binary): source
TensorFlow version (or github SHA if from source):1.14

Provide the text output from tflite_convert
# Copy and paste here
``
 Array AudioSpectrogram, which is an input to the (Unsupported TensorFlow op: Mfcc) operator producing the output array Mfcc, is lacking min/max data, which is necessary for quantization. If accuracy matters, either target a non-quantized output format, or run quantized training with your model from a floating point checkpoint to change the input graph to contain min/max information. If you don't care about accuracy, you can pass --default_ranges_min= and --default_ranges_max= for easy experimentation.
Fatal Python error: Aborted
Also, please include a link to a GraphDef or the model if possible.
https://github.com/tensorflow/docs/blob/master/site/en/r1/tutorials/sequences/audio_recognition.md

**Any other info / logs**

Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.
tflite_convert \
--output_file=model.tflite \
--graph_def_file=/home/unizen/Downloads/my_frozen_graph.pb \
--inference_type=QUANTIZED_UINT8 \
--input_shapes=16000,1:1,1\
--input_arrays=decoded_sample_data,decoded_sample_data:1 \
--output_arrays=labels_softmax \


'Error::_message' is std::string now

Automatically release string resource in destructor

From what I see Error accepts string constant in all places;
No need to release string constants in C/C++.

This change doesn't seem to address any known issue - I'd better leave the existing code.


Rigidbodies remain in graph after node removal

I am facing the problem that rigidbody components seem to remain in the graph even when the node is deleted
.
This screenshot is from my application where I am already trying o remove the rigidbodies before removing the node itself.
My code currently looks like this:

If any more details are necessary to fix the bug, lease tell me.
Kind regards

Seems to work now. I havent noticed any outdated rigidbodies at least.


"One shot wait/rewound" sound flags don't seem effective

"One shot wait" is meant to prevent a sound from being played more than once at the same time.
"One shot rewound" is meant to stop other occurrences of a sound when a new one starts.

For example, my TRNG level has a room with many wood beams Lara can jump on.
On almost every one of them, I put a sound source with a chance of 1 so it plays a creaky sound occasionally.
CH01 was still making the sound play way too much (ie. non stop), because of how many sound sources I have for this sound.
I fixed this by using the "One shot wait" mode. This way, only 1 at a random location in the room can ever be heard at a time.
In TEN, these flags don't seem to work as intended: each sound source plays like if you put "Normal" mode.
tomb4 (using "One shot wait"):
https://youtu.be/BTpQ-JIzDzs
TombEngine (both flags do the same thing):
https://youtu.be/HNfuik4joSs

May I ask - in what circumstances you have an object travel whole block at the timespan of 1 frame?

I will sum up what I wrote on Discord so information is not lost.
With the help of @Trxyebeep, we now see that originals can't handle two or more same looped/wait sound IDs playing in close proximity. Original engines will only play closest (loudest) one.
However, a trivial case is when you have two or more same sound sources in close proximity - e.g. two waterfalls, several blowing winds, several enemies shooting uzis, etc etc. In that case, original engine will only play closest one, which will inevitably cause sound bugs in tense gameplay scenarios with a lot of sounds emitted. Do we want to reproduce this faulty behaviour in TEN, or we want more consistent and flexible approach?

My last video was a pure test, just to show the difference TEN has compared to the classics.
My actual use case was the one in the original video: multiple sound sources for the same "sound", but I only want 1 to play at a time because otherwise it quickly gets overwhelming, even with a very low chance.
The thing is i don't think it's a faulty behavior, the name "one shot wait" does imply that the sound will not play again if it's already playing.
And in case of random environmental sounds (ie. non looping ones, for example wood cracks, wind bursts, birds chirping, or even a random whisper in some horror level, or voices), I think it makes sense.
The thing is this 1 square limit, in this case, makes that mode completely redundant: you would just use the normal play mode if you didn't mind the same sound playing more than once at the same time.
For looping sounds, I definitely agree, we should keep the ability to have the same sound playing multiple times.
I'm using several looping wind sound sources in more or less close distance, and even when it is is the same sound it plays in "stereo" (the instances are not synced), which is a huge atmosphere booster. Same with river sounds.


Idea: generate the stylesheet with Linaria

Link: https://github.com/callstack/linaria.
The idea would be to define each class name only once, and reference them in the CSS-in-JS stylesheets via constants.

Does not seem adapted for the use case.


add random number generator to sample deterministic batches

Hi @perrin-isir ,
I had issues reproducing two times the same results when using Xpag (even with Jax only on the CPU) in my project. I could track the differences down to the Sampler, which in my case was the DefaultSampler. Adding a numpy rng and using it to sample the batches solved my reproducibility issues (even on GPU I'm getting the same now). As there was already the seed field in Sampler, I think it was the intended behavior to have a deterministic sampler. Therefore, I created this PR.

Totally right, thanks a lot!!


Access to inner request is no synchronised

There are two points from which in-flight request.inner gets accessed: from eventfd handler and from the WaitFuture itself. Eventfd handler will take buffer out of canceled request when the event received, while WaitFuture Drop may be in-progress. Mutex should be used instead of RefCell

Closed by #4


What happens to my Words .docx files and my Excel .xlsx files when my subscription expires?

The page is very unclear, as it does not give any examples. It is all high level legal gibberish.
If I have created a Word document with a subscription version of Microsoft 365 - will it then eventually disappear or become useless if my subscription ends?
What exactly is Customer Data - is that my documents? Where are they residing? Will I loose my work?
This confusion is the biggest reason I do not want a MS 365 subscription. The next biggest reason is that it is very expensive to pay a substantial amount every year, just to have my document files available, as compared to a fixed price single version app.
Perhaps this is a big misunderstanding but you're not doing a great deal to do away with it.

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

ID: e5e656ac-5f86-6f46-55fc-5ea2cef0b51c
Version Independent ID: 74553c8e-e34c-8f5b-c2c2-95100c357d74
Content: What happens to my data and access when my subscription ends?
Content Source: microsoft-365/commerce/subscriptions/what-if-my-subscription-expires.md
Service: o365-administration
GitHub Login: @cmcatee-MSFT
Microsoft Alias: cmcatee

@frankbj57 Thank you for your feedback.
If they are located on your computer, you will still be able to open them, but will not be able to edit them or create new documents.
If you have them saved on OneDrive, and your subscription has not yet expired, you should download them from OneDrive to your computer as I understand that you will no longer be able to access documents on the OneDrive account that is associated with your subscription, after the subscription expires.
Hope this helps!
Thanks
Sri

@msbemba Thank you very much for the contribution and sharing this explanation. @frankbj57 Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Special Character Handling

How does this project handle special characters such as currency symbols, apostrophes, percent symbols, etc (¢, $, %, ')?    Can I just adjust the vocabulary and include these symbols in my dataset?
TARGET_VOCAB_SIZE = 26+10+3 # 0: PADDING, 1: GO, 2: EOS, >2: 0-9, a-z)

Please help me on including the special characters


⚠ Samsung has degraded performance

In 316d491, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2772 ms

Resolved: Samsung performance has improved in 219bd4a.


Can't find ios-release DSYM in google storage on stable branch engine.version 91c9fc8fe011352879e3bb6660966eafc0847233

can't find ios-release DSYM in google storage on stable branch engine.version 91c9fc8fe011352879e3bb6660966eafc0847233

no reason

@ldhlfzysys How did you fix this? Seeing the same issue with fastlane.

Filed a new ticket that shows that this broke between 2.2.1 and 2.2.2: #85604

@ldhlfzysys How did you fix this? Seeing the same issue with fastlane.

i just giving up


ionic3?

Hi,
Since it requires angular4, is there a ionic3 version of this component?
Can i use it in a ionic3 with angular5 project?
Thanks

Yes it is possible.


added method 'paginate' for relationships and method 'chunk' for query builder

Coverage remained the same at 96.754% when pulling e5a1b1ffc7613dcd884c37cf1afcb3ab2de9323c on LookinGit:develop into 045d587b7bf0e35d7994cd858dbef85f4674fe33 on adonisjs:develop.

Coverage decreased (-0.4%) to 96.382% when pulling 307f878a74d5af51483952c811460aa7e441e1b3 on LookinGit:develop into 045d587b7bf0e35d7994cd858dbef85f4674fe33 on adonisjs:develop.

Coverage decreased (-0.4%) to 96.382% when pulling bf853953f825b1d916851b7ce2bbec29bc55b8a7 on LookinGit:develop into 045d587b7bf0e35d7994cd858dbef85f4674fe33 on adonisjs:develop.

Coverage increased (+0.01%) to 96.767% when pulling 34fe9bda09fe892d7e99acf808b55a1fa7be11a7 on LookinGit:develop into 045d587b7bf0e35d7994cd858dbef85f4674fe33 on adonisjs:develop.

Coverage increased (+0.02%) to 96.772% when pulling 834d1169b9d3df78bcc2344c936d4f95273802d4 on LookinGit:develop into 045d587b7bf0e35d7994cd858dbef85f4674fe33 on adonisjs:develop.

Hey @LookinGit! 👋
Thanks for your contribution.
May you add tests to test this feature?

Also the method added is chunk and we have paginate in the title.
Can u please take a minute to explain, what exactly the feature is supposed to do as per you.

Coverage increased (+0.02%) to 96.772% when pulling 30b61e97e1d4297aaa55304e8e372e7e349c598b on LookinGit:develop into 045d587b7bf0e35d7994cd858dbef85f4674fe33 on adonisjs:develop.

Hey, @RomainLanz and @thetutlage
Sorry, at first it was PR with method paginate, but then I added PR with method chunk in the same branch. I renamed PR.
Should I create two new PR instead of this?

Hello @LookinGit
I actually removed chunk method for a reason, since we can use stream instead of buffering the data in memory http://knexjs.org/#Interfaces-stream

Coverage increased (+0.03%) to 96.782% when pulling 71e139b00fcb116d0c926c40eb487ef3ce9d5265 on LookinGit:develop into 045d587b7bf0e35d7994cd858dbef85f4674fe33 on adonisjs:develop.

@thetutlage I changed method chunk using streams

Created new PR only with paginate method, without chunk
https://github.com/adonisjs/adonis-lucid/pull/222


Prepare transfer to w3c organization

Updates all reference to tidoust/reffy across files, updates copyright notice and adds a w3c.json file.
See #449.
To be merged right after the transfer has taken place.

reports/ed/README.md
reports/tr/README.md

I fixed them silently a few days ago (the links were no longer valid) in https://github.com/tidoust/reffy/commit/f1fdd19ed9f0878548ec06fd91fb0f983cd6550f

(possibly the comment in src/browserlib/extract-dfns.js referring to an issue comment)

Done.


Added wishlist name to wishlists items WIP

Resolves #166
Description

New linie with wishlist name to distinguish items, doesn't look like duplicate now.
Short names (DC General) don't break lines, they are in  tags, I think bootstrap div class="row" is an issue here.
I'm not so sure about "Item for:" line, requested by doesn't seem right here.
I think simple "For:" will suit best.
Type of change

New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Works my local.
Screenshots

I'm working on alternative. Make item unique with wishlists, count and priority for each wishlist listed, when user pledges to donate app queries user about wishlist destination. Locations would be sorted by priority.
For example:


Fix typo in README.zh.md

Hi @intchensc - please see the instructions here on how to fix the DCO issue. Once fixed, I will merge

Hi@ryjones , is it ok now?


Adds multiarch Docker image support, as provides some relief to #350

Adds multiarch Docker image support, as provides some relief to #350
All Submissions:

[X] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[X] Have you added an explanation of what problem you are trying to solve with this PR?
[NA] Have you added information on what your changes do and why you chose this as your solution?
[NA?] Have you written new tests for your changes?
[NA] Does your submission pass tests?
[NA] This project follows PEP8 style guide.

Hello @intellitour and thanks for the effort on this.
Work is being done on this aspect under https://github.com/IdentityPython/satosa-docker following the "Docker Official Images" guidelines. Soon, we will remove the Dockerfile from this repo and all related information about Docker and the image will move there.
I will close this PR and I would urge you to open an issue or new PR there. Thank you!
/cc @xenophonf

For those who are in a hurry: https://hub.docker.com/r/intellitour/satosa

Dear @intellitour, thank you so much for your proposal!
SATOSA has recently been accepted into the Docker "Official Images" library:
https://hub.docker.com/_/satosa
https://github.com/IdentityPython/satosa-docker
As a result, we now officially support Debian- and Alpine-based SATOSA container images on amd64, arm32v5, arm32v6, arm32v7, arm64v8, i386, mips64le, ppc64le, and s390x.  Please note that in two cases, mips64le and s390x, only the Debian variant is supported.  These are due to limitations in SATOSA's dependencies (cf. https://github.com/IdentityPython/satosa-docker/issues/1) and out of our control, I'm afraid.
Please let me know if this doesn't meet your needs or if something doesn't work.


Ember Lifeline No Longer Supports jQuery selectors

I just updated ember-light-table to 1.12.2 (from 1.8.6), which bumped ember-lifeline.
Ember-Lifeline stops supporting jquery selectors here https://github.com/rwjblue/ember-lifeline/blob/master/addon/mixins/dom.js, resulting in: Called addEventListener with selector not found in DOM [Object: Object]
PR forthcoming.

Same error here.


A possibility to dispose the root container

When using a parent container for the root ProviderScope, it will not be disposed if we call runApp again with a different parent.
Using the parent here is necessary for calling some async operations before running the app.
I think not auto-disposing the parent is reasonable, but is there another way to dispose the root container without declaring it globally?
I'm looking for something like:
ProviderScope.containerOf(context, rootContainer: true);

Example:
import 'dart:async';

import 'package:flutter/material.dart';
import 'package:flutter_riverpod/flutter_riverpod.dart';

Future<void> restartApp(BuildContext context) async {
  scheduleMicrotask(() {
    main();
    print("app restarted");
  });
}

void main() {
  final container = ProviderContainer();
  runApp(
    ProviderScope(
      key: UniqueKey(),
      parent: container,
      child: const TestApp(),
    ),
  );
}

class TestApp extends ConsumerWidget {
  const TestApp({
    super.key,
  });

  @override
  Widget build(BuildContext context, WidgetRef ref) {
    return const MaterialApp(
      title: 'App',
      home: HomeScreen(),
    );
  }
}

class HomeScreen extends ConsumerWidget {
  const HomeScreen({
    super.key,
  });

  @override
  Widget build(BuildContext context, ref) {
    return Scaffold(
      body: Center(
        child: ElevatedButton(
          onPressed: () {
            Navigator.of(context).push(MaterialPageRoute(builder: (context) => const Page2()));
          },
          child: const Text('Go to Page2'),
        ),
      ),
    );
  }
}

class Page2 extends ConsumerWidget {
  const Page2({super.key});

  @override
  Widget build(BuildContext context, ref) {
    ref.watch(testProvider);
    return Scaffold(
      body: Center(
        child: ElevatedButton(
          onPressed: () {
            restartApp(context);
          },
          child: const Text("Restart"),
        ),
      ),
    );
  }
}

final testProvider = StreamProvider<String>(
  (ref) async* {
    print('init');
    final timer = Timer.periodic(const Duration(seconds: 1), (timer) {
      print(ref.hashCode);
    });
    ref.onDispose(() {
      print('dispose');
      timer.cancel();
    });
    yield "";
  },
);

Using the parent here is necessary for calling some async operations before running the app.

No it isn't. No docs recommend putting init logic in the main. Instead it is recommended to use a ConsumerWidget at the root

I'm looking for something like:
ProviderScope.containerOf(context, rootContainer: true);

I don't see the relationship between this and disposing the root container. And this snippet isn't present in your example
So at the moment I'm not sure what you're requesting. The example you gave works today.

I don't see the relationship between this and disposing the root container.

I'd be able to do the following at my restart method:
final rootContainer = ProviderScope.containerOf(context, rootContainer: true);
rootContainer.dispose();

The example I gave is broken, with each restart the previous parent container won't be disposed.

Keep a reference to it and dispose it then?

That's what i'm doing currently.
I was looking for a better and direct approach same as the rootNavigator of Navigator class. I think this has a low priority.

I don't think I'll add such an API. It's too niche and you can already work around this on your own.


Fix magellan _updateActive() behavior. Fixes #8960

When the links are not in the same order as the targets, or a link exists without a corresponding target, or several links with the same href are in a magellan container, the wrong link may get the .active class.
A visual test has been added for this case.

Thanks, this seems to work out.


cowboy_req:match_qs with nonempty constraint fails ungracefully on redefined parameters

I'm using Cowboy 2.7.0.
Perform a HTTP get on http://host/path?username=x&username=y.
In the handler, calling cowboy_req:match_qs([{username, nonempty}], Req) causes the following crash:
initial call: cowboy_stream_h:request_process/3
pid: <0.522.0>
registered_name: []
exception error: no function clause matching
                 cowboy_constraints:nonempty(forward,[<<"y">>,<<"x">>])
  in function  cowboy_constraints:apply_list/3 (/home/myproject/_build/default/lib/cowboy/src/cowboy_constraints.erl, line 48)

I believe that the same will happen for the int constraint.
Given that cowboy_req:parse_qs can handle a redefined parameter, I found this a little surprising (but understandable).  I suppose you could modify cowboy_constraints:apply_constraint to handle this in a few different ways:

Succeed and return all parameters if they all pass the constraint.
Succeed and return any parameters that pass the constraint, as long as one does.
Always fail if a parameter is redefined (raise a request_error like normal).
Allow the caller to choose one of those behaviours.

But maybe that's more complicated than you want?

So that's not really a bug, the constraints were made to work only with binaries on purpose. They can of course be extended, although I do not think the int constraint should be (or perhaps there's a good reason for it to also accept int but I'm not sure there is.
For nonempty I could definitely see a case for accepting lists and looking whether the list is empty. It sounds like this would cover your case.
But otherwise constraints crashing on invalid input data is the correct behavior.

So that's not really a bug, the constraints were made to work only with binaries on purpose.
For nonempty I could definitely see a case for accepting lists and looking whether the list is empty. It sounds like this would cover your case.

For my case I want to assert that each member of the list isn't empty.  But fair enough.  On reflection I'm not too desperate to put this change into the library, as it's an unusual situation that people might not want to accept by default.  I'll define a custom constraint function.

But otherwise constraints crashing on invalid input data is the correct behavior.

The main issue I had was not the crashing itself, but that it doesn't give a friendly failure reason.  Normally when a nonempty fails you'd get:
{{request_error, {match_qs,#{username => {nonempty,empty,<<>>}}},
  'Query string validation constraints failed for the reasons provided.'},
  blah...

If redefined parameters aren't valid then personally I would prefer it to crash with something like:
{{request_error, {match_qs,#{username => {nonempty,redefinition_forbidden,[<<"y">>,<<"x">>]}}},
  'Query string validation constraints failed for the reasons provided.'},
  blah...

That way it's more obvious why it's failing, and I don't have to read the library code to figure out what's going on.  It's a minor point though.  Thanks for maintaining a cool library :)

Yeah I don't think nonempty should look at members, but maybe there should be a nonempty_values or something.
I can also see the value in not crashing. To be honest this is one of the cases where I wasn't sure what was the best and therefore did not make a decision yet (you'll notice there's no tests for these cases). I think it comes from constraints being added for routing only, initially, where the crash does help. But then they were added to match functions and there it's not exactly the same.
I'll soon be adding some good improvements to constraints via the work I'm doing on Farwest. So let's keep this open and I'll consider it when that happens.