Handling non-confirmed funding transactions

Issue
During the current funding workflow, the responder should forget the channel if the funding transaction is not confirmed within a reasonable timeout. For lnd this timeout is currently set to 288 blocks.
The funder (initiator) of the channel cannot forget about the channel if the funding transaction is broadcast, since he has funded the transaction with coins. Therefore, we should make sure the money is returned to the funder's wallet.
Steps to completion:

[x] Prevent the funder from forgetting about the channel if the fundingManager gets restarted while waiting for the funding transaction to confirm. Currently, on restart it will launch a goroutine that will timeout after 288 blocks, but this should only be done for the channel responder.

[ ] Determine how to reclaim the funds. We can either double spend the input to the funding transaction back into our wallet, or broadcast the commitment transaction and sweep the funds using CPFP.

Extra credits: We might also be able to bump the fee of the funding transaction to get it confirmed, but this would possibly need some more advanced scripting features, due to changing the amounts int the funding tx changes the txid, which the commitment tx relies on.

I'll try to resolve this issue.

I've done the first part here #514

First portion fixed by #514.

Hi if nobody is working on this, I'd like to take it

Since I haven't gotten a reply I'll assume nobody is working on this and work on it myself

I believe @wpaulino has started on this one.
On Wed, Jul 11, 2018 at 4:47pm, Eugene <<EMAIL_ADDRESS><EMAIL_ADDRESS>> wrote:
Since I haven't gotten a reply I'll assume nobody is working on this and work on it myself
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub [https://github.com/lightningnetwork/lnd/issues/386#issuecomment-404196823] , or mute the thread [https://github.com/notifications/unsubscribe-auth/ADl15MEKau2-xao1LRCKVajwy9gAuqfyks5uFhAYgaJpZM4QBLco] .

I'm really sorry I didn't give any news. I no longer work on this problem indeed.

currently working on this

From #3149:
After discussing this a bit we have come to the conclusion we do not want to introduce more persistent state during the funding process. Instead we should let the fundingmanager

unlock the coins after a timeout, making them spendable in other transactions.
In combination with something like #1755  this should allow it to gracefully fail the channel.

To bump the fee on an unconfirmed channel manually, the current bump fee logic can be used.

Another suggestion here is to allow the cancellation of the funding transaction by doublespending it back to the chain wallet. This can be useful in the scenario I just went through where I set low-ish fees, and then the China outage happened, causing the funding tx to confirm after the two week window. I knew it was going to take a while and would have liked to double spend back to self in order to avoid having to pay 3x chain for [fund,force close,sweep].

Note that double-spending is currently not detected be neither funder nor receiver.

I'm having a look at bringing https://github.com/lightningnetwork/lnd/pull/1755 up to date. I'm working on integration tests, in theory it should be working though.
I can create a draft PR if it's of interest

@johng that'd be awesome!


Fix Missing job requirement check on job signs

This will add code to the JobManager to make the interaction with job signs respect the defined job requirements.
Additionally I went ahead and updated the German localization.
I would like to ask @pigneedle to test this PR to see if their issue has been fixed.

Fixes: #273

I get a message that there is no message for failing to meet the requirements, but it seems to at least be checking now.
Error message when I use a job sign that I don't meet the level requirement for:
Message not found (en): jobs.unmet.level

Did you delete/rename your messages file so it is replaced by the updated one?

I didn't. I realized that just after I posted my comment. I'm loading it up now to verify it works. I expect it will since it was just calling a missing string. I'll post after I run it.

I now receive a different error. When I use a sign, instead of the previous error, I now get:
Error occurred while executing command: null
This is on a fresh server running:
Minecraft 1.12.2
Forge <IP_ADDRESS>55
SpongeForge 1.12.2-2655-7.1.0
I don't think this error is related to this issue.

@pigneedle Should be fixed. Please re-do your messages file once again.

Job requirements seem to be working now after some testing.


fix method name: curserTo() --> cursorTo()

Might require a major version update, since this is technically a breaking change? Or just a minor version update, since it's a "this might break your implementation or it might not" change.


String enums are not recognized by intellisense (TypeScript 2.4.0 + Latest vscode)

VSCode Version: 1.13.1
OS Version: Mac OS Sierra 10.12.3

Steps to Reproduce:

Create a file for newly introduced string enum e.g. test.enum.ts with such content:

export enum DefaultImages {
  defaultMerchantHeader = "/assets/default_merchant_header.jpg"
}

Create another file where you import string enum and try to set variable with it e.g. logic.ts
const test = DefaultImages.defaultMerchantHeader;

While compilator doesn't complain and compiles code nicely (using angular-cli setup) vscode is highlighting the usage of string enum as not correct...
Screenshots:
http://imgur.com/0a5mqqO

Reproduces without extensions: Yes

Please try in VSCode 1.14. I see this working properly:

Also please make sure that TS 2.4.1 is active in your workspace: https://code.visualstudio.com/Docs/languages/typescript#_using-newer-typescript-versions

Yes, newer version fixed it :) At the moment when I was posting it there were no updates available yet... :)


More MSP Refinement

This cleans up some of the more inscrutable if-else code in the MSP comment-to-CV attribute mapping. It also corrects more attribute accessions and routes them to the correct location in the entry. I added more attribute handling code to work with more NIST HCD libraries.
While at it, I made the CLI log more informatively and made the plotting code marginally more colorful.

TODO: Joshua will relook to see if still compatible with latest code and then merge it.

This PR was rolled into the semantic validator PR


Unrestrict capybara test

@twalpole I have finally managed to triage this weird behaviour down to a specific commit SHA - https://github.com/teamcapybara/capybara/commit/a76a35fbc8bb5baceb13c50ede1b9ee551f674d7
I'm not saying it's wrong, I'm just maybe asking you for help on this. It feels odd that the boolean check works, but the rspec matcher doesn't. I want to try help here so if I can provide anything else please ask.
@tgaff worked on this functionality, where we allow scoping inside of a block. We also know it's a SitePrism interop issue, not a Capybara issue. I was just wondering if you could help.

This is happening because you're overwriting page and returning an element wrapper rather than a Capybara session. I think the element being used  should just implement the method to_capybara_node and return @root_element

@luke-hill completely agree with @twalpole. Adding to_capybara_node to Section class solve the problem

PR #65 - read description


sibling tab-content should be hidden or removed or transclude

After implementing tabs directive, there is a
 sibling to

You can see that my ui-view has a tab-content class on it as well to fall in line with angular-ui.  Unfortunately, this creates two tab-content classes which produces some unexpected UI with empty spacing / padding from the former.
If the functionality is required, then this could just be hidden.  Otherwise if it doesn't matter, we can remove it.  If possible, it would be cool to replace the .tab-content with transclude.. EG:  ui-view.
<tabs ...>
   <ui-view></ui-view>
</tabs>

+1. This is definitely undesirable behavior in its current state.

There isn't anything in this library that adds a tab-content class anywhere, is this just the behaviour of angular-ui (which this library uses)?  I'll take a further look when i'm back from holidays to reproduce the example, feel free to submit a PR.
I'm against including the ui-view element inside the default template since it forces the location of the target route's outlet (limits customisation).

The easy solution is to put it where tab content is and just tell people
how to override it. You could provide multiple templates, too.
On May 7, 2015 3:43 AM, "Robert Pocklington"<EMAIL_ADDRESS>wrote:

There isn't anything in this library that adds a tab-content class
anywhere, is this just the behaviour of angular-ui (which this library
uses)? I'll take a further look when i'm back from holidays to reproduce
the example, feel free to submit a PR.
I'm against including the ui-view element inside the default template
since it forces the location of the target route's outlet (limits
customisation).
—
Reply to this email directly or view it on GitHub
https://github.com/rpocklin/ui-router-tabs/issues/24#issuecomment-99775534
.

Here is the rendered DOM in Chrome from the online example demo, with the accounts tab selected.

This only has one tab-content div, which is inside the ul.nav class.  You are right in that it is redundant the way this library uses the bootstrap tabs, but in the example there is no change in the screen layout if it is removed (ie. causes no artifacts).
Can you share a plunkr to demonstrate the problem you are having?  Also let me know what version of ui-boostrap you are using.

Happy to look into this further, but if there's no response i'll close this in 7 days.

I think the issue is to get the proper layout when using type='tabs' and not 'pills' is that there is a 'tab-content' class that is needed to wrap the ui-view -

So you end up with two dom elements with a class of 'tab-content' both with a border displaying but one empty (sibling of ul.nav).
Not ideal for nested tabs but to test I added a .tab-container .tab-content{display:none} and that cleaned it up.

Since the .tab-container which is auto-generated will never be used by developers (no transclusion), then you could at least add style="display: none;" to it after it gets rendered...  Otherwise, every developer who wants to use wrap .tab-container styling around their own <ui-view /> will have to add the above css def.

@heliocreative good to know there's a simple workaround for you.  I can see the problem now with type="tabs". If people would use it, i'm happy to put transclude on this directive so they can put the ui-view inside the directive template if they wish.
In terms of the .tab-content artifacts, it seems like the best thing to do would be to remove it from the DOM.  Is this acceptable?  I still only see visual changes if I add my own CSS styles to .tab-content { ..} am I missing something?

Closing due to inactivity.


[Bug]: No tests found using --findRelatedTests always exits with code 0

Version
27.5.1
Steps to reproduce

Clone my repo https://github.com/ted-kayak/jest-findrelatedtests-repro
npm install
npm run test:related

Expected behavior
I expect for the script to exit 1 like the output says it will.
npm test runs jest with no additional arguments and it exits with 1
Actual behavior
The script with --findRelatedTests exits with code 0, despite the output saying it will exit with 1, and prompts for --passWithNoTests to exit 0.
Additional context
--testFailureExitCode=99 seems to have no discernible effect on the script.
Environment
System:
    OS: macOS 12.2.1
    CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
  Binaries:
    Node: 14.18.3 - ~/.nvm/versions/node/v14.18.3/bin/node
    Yarn: 1.22.17 - ~/.nvm/versions/node/v14.18.3/bin/yarn
    npm: 7.24.2 - ~/.nvm/versions/node/v14.18.3/bin/npm

https://github.com/facebook/jest/releases/tag/v28.0.0-alpha.5


Syntax error in run-minidlna.sh

Hi there
I'm trying to run MiniDLNA using your Docker image. Unfortunately, I'm getting this error message:
/app/bin/run-minidlna.sh: line 97: [: too many arguments
/app/bin/run-minidlna.sh: line 97: [: too many arguments

I use this command to start the container:
$ docker run -d --name=minidlna \
  -e USER_MODE=Y \
  -e MINIDLNA_ROOT_CONTAINER=V \
  -e MINIDLNA_DIR_V_1=/media/videos \
  -e MINIDLNA_ENABLE_INOTIFY=YES \
  -e MINIDLNA_FRIENDLY_NAME=MiniDLNA \
  -v /.../videos:/media/videos \
  -v /.../log:/log \
  -v /.../db:/db \
  --net=host \
  giof71/minidlna

$ docker logs minidlna
Current user id is [0]
t=A
Processing media_dir for ENV_NAME=[]
t=P
Processing media_dir for ENV_NAME=[]
t=V
Processing media_dir for ENV_NAME=[/media/videos]
t=A
Processing media_dir for ENV_NAME=[]
t=P
Processing media_dir for ENV_NAME=[]
t=V
Processing media_dir for ENV_NAME=[]
t=A
Processing media_dir for ENV_NAME=[]
t=P
Processing media_dir for ENV_NAME=[]
t=V
Processing media_dir for ENV_NAME=[]
t=A
Processing media_dir for ENV_NAME=[]
t=P
Processing media_dir for ENV_NAME=[]
t=V
Processing media_dir for ENV_NAME=[]
t=A
Processing media_dir for ENV_NAME=[]
t=P
Processing media_dir for ENV_NAME=[]
t=V
Processing media_dir for ENV_NAME=[]
/app/bin/run-minidlna.sh: line 97: [: too many arguments
/app/bin/run-minidlna.sh: line 97: [: too many arguments
# MINIDLNA CONFIG
media_dir=V,/media/videos
db_dir=/db
log_dir=/log
root_container=V
port=8200
friendly_name=gioDLNA
inotify=yes
album_art_names=Cover.jpg/cover.jpg/AlbumArtSmall.jpg/albumartsmall.jpg
album_art_names=AlbumArt.jpg/albumart.jpg/Album.jpg/album.jpg
album_art_names=Folder.jpg/folder.jpg/Thumb.jpg/thumb.jpg
force_sort_criteria=
CMD_LINE=/usr/sbin/minidlnad -S -f /tmp/minidlna.conf -P /tmp/minidlnad.pid
USER_MODE=[N]

$ cat /.../log/minidlna.log
minidlna.c:521: warn: Unset locale
minidlna.c:1126: warn: Starting MiniDLNA version 1.3.0.
sql.c:88: error: prepare failed: no such table: SETTINGS
SELECT VALUE from SETTINGS where KEY = 'UPDATE_ID'
minidlna.c:393: warn: Creating new database at /db/files.db
minidlna.c:405: fatal: Failed to clean old file cache!  Exiting...

Am I doing something wrong?

Hello, I think you are doing nothing wrong, the is a bug for sure, I will be checking asap

Please try the newest version.

Images are building right now...

Thanks for having a look so quickly!
It looks better - the error message too many arguments is gone :)
However, the fatal log line Failed to clean old file cache!  Exiting... in the minidlna.log is still there. So, that seems to be a separate issue:
minidlna.c:521: warn: Unset locale
minidlna.c:1126: warn: Starting MiniDLNA version 1.3.0.
minidlna.c:393: warn: Creating new database at /db/files.db
minidlna.c:405: fatal: Failed to clean old file cache!  Exiting...

Your paths don't look correct:

Yes, I replaced the real paths from my system with ... before pasting the command here, but the paths seem not to be the problem, as the log and DB file get created where I'd expect them :)

Hello, I don't get the issues with the db... maybe check the permission although they should be set by the run script.
A better way than this user mode is using the --user method which is supported since the end of last year.
Maybe can you port your final docker compose file so I can try and reproduce the issue?

Hmm, when I use --user with docker run, it does not run minidlna in user mode:
$ docker run -d --name=minidlna --user="1000:1000" -e MINIDLNA_ROOT_CONTAINER=V -e MINIDLNA_DIR_V_1=/media/videos -e MINIDLNA_ENABLE_INOTIFY=YES -e MINIDLNA_FRIENDLY_NAME=gioDLNA -v /.../videos:/videos -v /.../log:/log -v /.../db:/db --net=host giof71/minidlna && docker logs minidlna
abc408cbdfddef27c633676672978d65f18a778d1750f0ca5a2a57327554442b
Current user id is [1000]
t=A
Processing media_dir for ENV_NAME=[]
t=P
Processing media_dir for ENV_NAME=[]
t=V
Processing media_dir for ENV_NAME=[/media/videos]
t=A
Processing media_dir for ENV_NAME=[]
t=P
Processing media_dir for ENV_NAME=[]
t=V
Processing media_dir for ENV_NAME=[]
t=A
Processing media_dir for ENV_NAME=[]
t=P
Processing media_dir for ENV_NAME=[]
t=V
Processing media_dir for ENV_NAME=[]
t=A
Processing media_dir for ENV_NAME=[]
t=P
Processing media_dir for ENV_NAME=[]
t=V
Processing media_dir for ENV_NAME=[]
t=A
Processing media_dir for ENV_NAME=[]
t=P
Processing media_dir for ENV_NAME=[]
t=V
Processing media_dir for ENV_NAME=[]
# MINIDLNA CONFIG
media_dir=V,/media/videos
db_dir=/db
log_dir=/log
root_container=V
port=8200
friendly_name=gioDLNA
inotify=yes
album_art_names=Cover.jpg/cover.jpg/AlbumArtSmall.jpg/albumartsmall.jpg
album_art_names=AlbumArt.jpg/albumart.jpg/Album.jpg/album.jpg
album_art_names=Folder.jpg/folder.jpg/Thumb.jpg/thumb.jpg
force_sort_criteria=
CMD_LINE=/usr/sbin/minidlnad -S -f /tmp/minidlna.conf -P /tmp/minidlnad.pid
USER_MODE=[N]

However, regarding the db issue, I have tried to run the Docker image on a different machine, and there it works out of the box. So there might be a problem with my Docker setup...

Ah, I see! I was confused by the last line USER_MODE=[N], but that makes sense now.
Actually, the "other machine" is the machine where I intended to run it in the first place. Also, I was able to run some tests and it looks good. So, I am happy the way it is :)
Thanks a lot!

Thank you for the feedback. Consider starring the repo if that is not an issue for you.
Cheers!


Remove runtime/browser/demo folder, update products recipes and tests to match

I sent you https://github.com/PolymerLabs/arcs/pull/804 to fix the lint errors that landed.

These 2 recipe files (runtime/browser/demo/recipes.manifest and shell/artifacts/Products/Products.recipes) were almost identical, so there is not much point in keeping both.
Updated README (Ideally i think the main README should either link, or duplicate info from ./shell/apps/web/README.md).


Search tool is broken when excluding a folder from the search

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.57.0
OS Version: Ubuntu 18.04 (same issue on Docker Ubuntu 16.04 using Remote Development Containers).

Version: 1.57.0
Commit: b4c1bd0a9b03c749ea011b06c6d2676c8091a70c
Date: 2021-06-09T17:18:42.895Z
Electron: 12.0.9
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 5.4.0-74-generic snap

I believe this is a bug introduced in the newest version release (as I literally didn't change anything in my workspace besides upgrading VSCode).
Disclaimer: I'm not sure what's the source of this bug, but it doesn't seem to affect the new "Remote Repositories" extension, as I  tested it out to create an "anonymous" version for this ticket using this same repository.
Steps to Reproduce:

Create a multi-root workspace (I think this is related as the error cites one of my workspaces "/^Workspace/C++")
Search for anything using the Search tool (CTRL + SHIFT + F)
Add some exclusion criteria - the all should work but excluding other workspaces - e.g. "./Documentation"
Watch a "regular expression" error pop-up in the search bar citing one of the multi-root workspace folders.

Oops, regression from https://github.com/microsoft/vscode/issues/99512, if your workspace name has other regex characters in it (like + here)


Create custom cassandra image for single instance integration tests

On my machine it now takes 5s to startup the cassandra container instead of 80s.
I have not touched multi-instance integration tests because I dont think the same speedups are possible there.
I discovered the magic speedups here: https://github.com/saidbouras/cassandra-docker-unit/blob/master/scripts/setup-config.sh
Disabling gossiping is fine because its only a single instance.
Disabling virtual nodes is more iffy, but I figure its fine because the multi-instance clusters are still running with a proper virtual node setup.
It might still be worth investigating if there is anything we can do to speedup or skip gossiping on multi-instance clusters as every node starts with a complete list of seeds.
But we would want to be very careful that it doesnt alter post-setup functionality from what a production cassandra cluster would be like.
The cassandra.yaml is from here: https://github.com/apache/cassandra/blob/cassandra-4.0/conf/cassandra.yaml
The only changes I made is to set enable_user_defined_functions and enable_scripted_user_defined_functions.

Can we put this in a separate repo and publish to dockerhub instead?

IMO we are better off not doing that.
If we put dockerhub in between our checked in Dockerfile and our integration tests, anytime we need to tweak something, even just to quickly test something, we need to publish to dockerhub.
Using the approach in this PR, any change to the Dockerfile will be immediately reflected in the next test run, without any user intervention.

I'm hesitant to start adding the building of docker images to our integration tests.
Anytime you need to tweak something and test you can just download the docker image repo and build it yourself. Even that is an uncommon scenario, we have barely had to edit the docker images.
And of course the added advantage that you can use it like a normal docker image/other projects can use the published one.

And of course the added advantage that you can use it like a normal docker image/other projects can use the published one.

The only advantage I'm hearing is that other projects will be able to make use of it too.
This is a noble goal, but, in order to better serve that goal I believe we need to test it internally first for a while to make sure we have something thats worth sharing and wont have unintended side effects.
I dont believe that building images during integration tests will introduce debt.
It's very easy to remove the building logic and transferring the images to a new repo will also be very easy when the time comes.

I dont believe that building images during integration tests will introduce debt

It's another part of the CI that can fail. Plus won't it need to be rebuilt every test run? Or does caching handle that for us.

It's another part of the CI that can fail.

If it fails, then thats good because we've caught something thats broken?
If you think docker build could be flakey... well thats possible I guess but I've yet to see any evidence of that being the case.

Plus won't it need to be rebuilt every test run? Or does caching handle that for us.

It takes ~1s to build the first time because its just adding a very tiny layer on top of library/cassandra:4.0.6 and subsequent runs only take ~40ms (as per the comment)

If it fails, then thats good because we've caught something thats broken?
A published Docker image will never be broken once it's published, but yes I suppose docker build won't be likely to fail.

My main concern with this change is that it sort of sets a precedent for the Shotover repo to become a kitchen sink. For something like building/versioning/modifying Docker images, I'd expect that not to be a concern for the Shotover repo, we'd use the existing tools that manage this (Dockerhub).


[Bug] Weird refresh when marking chapters as read/unread/bookmark

Device information

Tachiyomi version: <IP_ADDRESS>
Android phone & version: note9 android 10

Steps to reproduce

select manga from library
swipe chapter to mark as read/unread/bookmark

Expected behavior
No weird animation/refresh thing
Actual behavior
Weird animation when swiping chapters.
Other details
This doesnt happen when you are in browse.
https://discord.com/channels/349436576037732353/569823838305648640/800974816067715082

fixed in latest


How can I force a rebuild for every run ?

If you don't change any files in between 2 runs, Flutter won't rebuild the app. I don't want this behavior, I'd like the app to be rebuilt on every run no matter what. How can I achieve this ?

@TheCarpetMerchant
I think your question is better suited for support channels like StackOverflow, or can reach out in flutter reddit help page or on discord for existing solutions. If you are looking to propose new changes in existing behavior as how it rebuilds the app currently, please use relevant template and fill out requested details so that we can address it as applicable.
I'll close it for now.


Screenshot/Art issue

So, Screenshots follow the current MAME protocol of being grouped in a folder, based on ROM name, so all your Mortal Kombat screenshots are in a folder called "MK" ETC, however, IV-Play only reads from the SNAP folder, and not from any sub-folders in that directory, as MAMEUI used to.
The result is that to get your handy-dandy screenshots of what this game is and if you've played it before, you have to go in to, say, your Street Fighter 2 folder in SNAP, copy out the screenshot you want, rename it to sf2.png or whatever it would be, all to get the screenshot to display properly.
Needless to say, this probably shouldn't be happening.

Out of scope.
Baseline's screesnhot behaviour changed somewhere along the line since IV/Play was introduced.
Simple solution is just alter mame.ini to:
snapname %g
To return to previous behaviour.


Add links to each other in the doc.

Refine mutual links for aggregate, apply, and transform, and links to the each equivalent function between DataFrame and Series.

LGTM

Thanks! I'd merge this now.


Popup misalignment when inside of a container with position relative

Current behavior
The popup's initial render is always misaligned when nested in a container with position: relative:
https://user-images.githubusercontent.com/943036/180498198-72348d99-be5d-4fb7-b7e8-ec73002bced6.mov
Consequently, this affects all components backed by the popover (menus, hover cards, etc).
Steps to reproduce the bug

Open sandbox: https://codesandbox.io/s/blissful-panna-ss5b9s?file=/src/popover.tsx
Click on the button
Notice the popup is misaligned
Click on the button to hide the popover
Click on the button again
Notice the popup is now correctly aligned

Expected behavior
Correct alignment on the first render.
Workaround
Any of the following:

Add an explicit width value to the popover styles.
usePopoverState({ fixed: true })
Remove the intermediate <div> wrapper between the container and the anchor/popover elements.

Possible solutions
No response

Thanks! It looks like it happens since next.31 and may be related to #1535

It looks like we'll have to add top: 0, left: 0 here: https://github.com/ariakit/ariakit/blob/790af4e1acd75864f46f589819f066fc70e5f992/packages/ariakit/src/popover/popover.tsx#L78-L81
Reference: https://github.com/floating-ui/floating-ui/issues/1809#issuecomment-1192904516


Meta: Ceramic Improvement Proposals

cip:
title: Meta: Ceramic Improvement Proposals
author: Michael Sena (@michaelsena)
discussions-to:
status: Draft
category: Meta
type:
created: 2020-05-22
requires:
replaces:
Simple Summary
This proposal describes the process for Ceramic Improvement Proposals (CIPs).
Abstract
Ceramic Improvement Proposals (CIPs) are standards for improving the Ceramic platform, including core protocol specifications, client APIs, doctypes, and document standards. CIPs allow anyone to contribute to the development of the Ceramic Network and standards built on top of it. As a result, CIPs allow the Ceramic Network to thrive as an open source project and protocol.
Motivation
Here are some of the reasons why Ceramic needs a CIP process:

To define an explicit governance process for Ceramic network upgrades
To make it easy for community members to contribute to the development of the protocol
To provide a way to discover implementation standards accepted by the community
To provide a vehicle for community discussion around important topics
To remove any individual or group of individuals as gatekeepers to the Ceramic Network

Specification
Process
1. Propose a new idea

Ideas are incomplete proposals meant to initiate community conversation.

Create a new issue in the CIP repository containing the idea for your your proposal, following the CIP template format. Be sure to add the Status: IDEA label to your issue.
2. Complete your draft

Drafts are complete proposals, but still undergoing rapid iteration and change.

Complete your proposal by filling out all appropriate fields in the CIP template. Update your proposal to Status: DRAFT in the issue header and Github label. Gather community feedback and make improvements as required.
3. Enter last call for community feedback

Last Calls are stable proposals ready for final review by the community.

Once you feel that your proposal is stable and ready for final review by the community, update your proposal to Status: LAST CALL in the issue header and Github label. In order to proceed beyond Last Call, your issue must remain in Last Call for at least 2 weeks and any technical changes that are requested must be addressed by the author.
4. Submit a Pull Request

Pull Requests are CIPs ready for consideration by editors and/or core devs.

When your proposal exits Last Call, you should submit a Pull Request to the CIP repository. To do this, fork the CIP repository by clicking "Fork" in the top right. Add your CIP to your fork of the repository. Update your proposal to Status: PENDING in the issue header and Github label (on both your previous open issue and new PR). Then, submit a Pull Request to the CIP repository.
Upon submission an editor will manually review the first PR for a new CIP, assign it a canonical number (i.e. CIP-1), and merge it into the CIP repo. They will then reach out to discuss next steps to achieve finalization. These steps will depend on whether or not your CIP is of type Core.
When submitting your Pull Request:

If your CIP requires images, the image files should be included in a subdirectory of the assets folder for that CIP as follows: assets/cip-N (where N is to be replaced with the CIP number). When linking to an image in the CIP, use relative links such as ../assets/cip-1/image.png.

5.  If your CIP is a Core CIP
An editor will reach out to provide the dates of the upcoming Ceramic Core Devs calls. Once you select one, your issue will be added to the agenda for that call where it will be discussed for inclusion in a future network upgrade.
If implementers agree to include your CIP in a future network upgrade, CIP editors will update your CIP to Status: ACCEPTED. Once your proposal has been released in a network upgrade, CIP editors will update your CIP to Status: FINAL.
If implementers decide not to include your CIP in a future network upgrade for whatever reason, you are always able to propose it again at a later time. It will remain as Status: PENDING in the CIP repo.
5b. If your CIP is a non-Core CIP
An editor will ask if anyone objects to it being finalized. If the editor decides there is no rough consensus - for instance, because contributors point out significant issues with the CIP - they may close the PR and request that you fix the issues in the draft before trying again. If the editor finds there is rough consensus, they will merge the PR and update it to Status: FINAL.
CIP Terms
Categories

Standards: an CIP that affects the protocol or is an implementation standard.
Meta: an CIP that affects the governance process for CIPs.
Informational: an CIP that is merely for informational purposes but requires no action by the community, and will not be merged as a CIP.

Types

Only applicable to CIPs of type Standards.

Core: an CIP that affects the core protocol.
Networking: an CIP thst affects the networking layer (i.e. libp2p or syncing).
Interface: an CIP that affects the Ceramic API or provider interface.
RFC: an CIP that proposes an implementation standard (i.e. doctypes, document configurations, or document schemas).

Statuses

Idea: an CIP issue that is incomplete.
Draft: an CIP issue that is undergoing rapid iteration and changes.
Last Call: an CIP issue that is stable and ready for final review by the community.
Pending: an CIP that has been merged but not finalized.
Accepted (Core): an CIP of type Core that has been accepted by the core devs to be included in a future network upgrade.
Final (Core): an CIP of type Core that has already been released in a network upgrade.
Final (non-Core): a non-core CIP that has met all criteria and is finished.

Rationale
It is prudent to look at other successful examples of open source software governance. CIPs are inspired by the previous work of Ethereum (EIPs), Bitcoin (BIPs), Python (PIPs), and others. CIP is slightly different in implementation than those examples, but shares many similarities. In some cases, CIP even borrows certain language from those examples.
Implementation

Official Process: This CIP and the README of the CIP repository.
Issue Template: Create a new CIP issue here.

Copyright
Copyright and related rights waived via CC0.

Just finished a draft of a CIP that proposes the CIP process. Pinging @oed @dazuck @pedrouid etc for feedback.

Looks good @michaelsena 👍

agree 👍

Okay, moving this from DRAFT to LAST CALL.


fix(create-vite): remove redundant tsconfig include configuration

Description
The "src/**/*.d.ts" configuration seems redundant.
Because "src/**/*.ts" can actually match to .d.ts files.
The description of include configuration on the Typescript official website is: "e.g. .ts, .tsx, and .d.ts by default", but this does not mean that after you configure include in tsconfig.json, you must put "src/**/*.ts" and "src/**/*.d.ts" are configured.
I have tested that "src/**/*.ts" can match the .d.ts file in the project.
Or is this intentionally set by the vite team so that developers can directly see that the .d.ts file can be resolved by Typescript?

Additional context

What is the purpose of this pull request?

[ ] Bug fix
[ ] New Feature
[ ] Documentation update
[x] Other

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the Pull Request Guidelines and follow the PR Title Convention.
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[x] Ideally, include relevant tests that fail without this PR but pass with it.

Looks good to me, can you make the same change for the svelte template too?
https://github.com/vitejs/vite/blob/1a2e5e6d9a6bb2531bf73be801c9778dbf39d51b/packages/create-vite/template-svelte-ts/tsconfig.json#L18

Looks good to me, can you make the same change for the svelte template too?
https://github.com/vitejs/vite/blob/1a2e5e6d9a6bb2531bf73be801c9778dbf39d51b/packages/create-vite/template-svelte-ts/tsconfig.json#L18

Of course, if you guys think it would help

Thanks!


Added Mini Project - Basic Background Generator

Hi,
Please review this mini project's PR.
This commit can fix #10
Thank You
@Ayushparikh-code

Kindly add the label of LGMSOC'21 to this PR.
@Ayushparikh-code

Kindly add the label of LGMSOC'21 to this PR.
@Ayushparikh-code

done✌


INDO output & tests

Fixes #149. I consulted with Rebecca Gieseking about INDO outputs, and she considers the partial charges to be meaningful enough to report. I reinstated the standard MOPAC output block for all INDO calculations with all total-energy-like quantities suppressed, since those aren't meaningful for INDO calculations.
Status

[x] Ready for merge

Codecov Report

Merging #150 (7a0219a) into main (d37f6c7) will decrease coverage by 0.01%.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##             main     #150      +/-   ##
==========================================
- Coverage   66.68%   66.68%   -0.01%
==========================================
  Files         331      331
  Lines       73721    73720       -1
==========================================
- Hits        49159    49157       -2
- Misses      24562    24563       +1

Impacted Files
Coverage Δ

src/run_mopac.F90
76.31% <ø> (-0.04%)
:arrow_down:

... and 3 files with indirect coverage changes


add JPMS metadata to gradle jars

Expected Behavior
It'd be nice if gradle jars were at least JPMS automatic modules themselves. module-info would be preferred, but that is harder to perhaps even impossible at this time.
Current Behavior (optional)
No response
Context
This is so that plugin authors could choose to module-info for compile time restrictions if they wanted.
Having gradle eventually require all plugins to have a module-info would solve the duplicate library classpath issue (or at least make it obvious). I don't expect that to happen for a very long time.

This issue needs a decision from the team responsible for that area. They have been informed. Response time may vary.

It is very unlikely that Gradle will itself execute with the module path concept. Also our current plans on publishing a Gradle API are about publishing a single JAR for this.
There would be limited value in pretending it can be consumed in a module aware runtime.

Yeah, really right now I would just like to see the automatic module metadata added. That way if we want to use more statically typed module metadata we can at compile time.


Fix #54315

Fix #54315

Smoked the explorer. Merging.

@joaomoreno Following test is contradicting the fix
refresh(element, false) refreshes the element
Refreshing an element without recursive is refreshing its children also. Hence did not merged. Lets discuss about it.


Implement v-clamp with v-html

I'm currently using Vuetify and Vue-Clamp
The body contains html elements such as span, ,

 etc...
I tried

    <v-clamp autoresize :max-lines="10" v-html="body"></v-clamp>

and
<v-clamp autoresize :max-lines="10">

</v-clamp>

But both approach doesn't work

Duplicate of #13

@ChunAllen Have you found a solution for this? Running into the same problem.

Hi, i also have same issue. Any suggestion to solve this issue?


restore the original settings and reboot scheduler when fail to restart scheduler with user-custom settings

Background
this simulator restart when user request to change the scheduler configuration.
Currently, when fail to restart with custom setting, the scheduler is dead until the user adapts the correct settings.
new feature
restore the original settings and reboot scheduler when fail to restart scheduler with user-custom settings

/assign

/kind feature

/good-first-issue

/unassign

Hey, I would like to work on this issue, still relevant?

Hi @R4ZN1V. feel free to open PR :)

@sanposhiho could you give a bit of an insight or how to start with it? If I get a little help, I guess I will be able to work on it.

scheduler is restartd on RestartScheduler
https://github.com/kubernetes-sigs/kube-scheduler-simulator/blob/master/scheduler/scheduler.go#L38

shutdown scheduler.
start scheduler with new configuration.

But, if 2 is failed, it returns error and scheduler will be not working after that.
scheduler configuration is stored on the field currentSchedulerCfg.
https://github.com/kubernetes-sigs/kube-scheduler-simulator/blob/master/scheduler/scheduler.go#L30
So, we can achieve this enhancement by getting the configuration before changing and restarting the scheduler with it when error.

/assign


Improve process for clearing 'started-at' annotations from workspaces

What does this PR do?
Avoid attempting to update stopped workspaces to remove started-at annotations if the annotation is not present on the workspace.
What issues does this PR fix or reference?
Minor fix to avoid sending unnecessary update requests.
Is it tested? How?
Should be no functional change -- annotations should still be removed from stopped workspaces.
PR Checklist

[ ] E2E tests pass (when PR is ready, comment /test v8-devworkspace-operator-e2e, v8-che-happy-path to trigger)

[ ] v8-devworkspace-operator-e2e: DevWorkspace e2e test
[ ] v8-che-happy-path: Happy path for verification integration with Che

In my brief testing, this change cuts 50-150ms from reconcile times for stopped workspaces (which, on most clusters, tends to be most of them). This especially helps during phases like startup, where it can take a while to process hundreds of stopped workspaces.

I've added a second commit that goes a step further to also not make any API requests for updating the status if the controller thinks this would be a no-op. This slightly increases the chances of an out-of-date status (in the case where DWO misses an on-cluster update and the cache is out of sync) but also makes re-reconciling workspaces that have not seen any changes take practically no time.
Below is a graph of DWO metrics with the following configuration:

500 stopped workspaces, unchanging
1 minute resync interval for DWO (i.e. it re-reconciles all resources every minute)

Resyncing all resources is a case where DWO will hit internal rate limits for requests, causing each API call to take a lot longer than normal

The first half of the graph is for the current main branch. The second half is with only the first commit in this PR applied.

The relevant metric to follow is reconcile time, which goes from ~500ms to ~250 during the resync. Additionally completing the full resync takes a lot less time (due to each reconcile taking half the time).
With the second commit, the graph is even less interesting; reconciles of stopped workspaces take >5ms since no API calls are made, and DWO can re-reconcile all 500 stopped workspaces in one second.
This change should be safe for regular workspaces, as we still update status when the computed status is different from the on-cluster status.

/retest

/retest


keep it up-to-date with the upstream repository.

keep it up-to-date with the upstream repository.


uniques, reduce, fold, and flatMap DQL functions

Is your feature request related to a problem? Please describe.
I'm frustrated when I can't de-duplicate entries in list values within DQL. These functions would help with this!
Describe the solution you'd like
The following functions are implemented for DQL (forgive any flubs in TS-like syntax):

uniques, that removes any duplicate entries in the list, keeping the first. This looks like it would be as simple as exposing DataArray::distinct as a DQL function.
reduce<T>(array: DataArray<T>, app: Function<T, T, T>): T, that folds all entries into one using the provided function app.
fold<U, T>(array: DataArray<T>, init: U, app: Function<U,T,U>): U, that works like reduce but can change type due to having an explicit starter value.
flatMap, that exposes DataArray::flatMap.

Describe alternatives you've considered
It is always possible to implement these by dropping to JS, but DQL is often far clearer due to its declarative nature.
Additional context
Would these be appreciated? I'm willing (once I have time in a few weeks) to try and implement these myself.

There is a reduce function (reduce(list, (a, b) => a + b)), though the other functions are not present yet. They are all pretty easy to implement; you are welcome to put up a PR for them in the next few weeks.

Ah! It's missing from the functions docs, then! I'll add it there when I get to this if it hasn't happened already.

A quick note to myself for when I get to this: some kind of sortBy would also be useful to have in DQL.

I agree - sortOn or sortBy would be great.

Great! I'll probably add a sortBy that takes a projection function, but also sortWith where you can pass a comparator lambda.


Register vulnerability

Resolved vulnerability where user could assign himself admin permissions or activation even without email verification.
During registration user can assign himself admin permissions if in the same request user will send form data 'permission: admin'. As register route does not check whether request contains this field this can be considered a serious exploit. In addition, user can also immediately activate his account during registration if is_active parameter is set.
Below is shown an example request that would allow user to register an account without email confirmation as well as with admin permissions.

Fix is simple, do not trust all the data user provided in his request as it can contain more than fields than the rest api handler actually needs. Insert only known parameters into the database.

Thanks for your outstanding contribution @DiRaltvein


Update Russian and Ukrainian translations

This updates the POT file, as well as the translations for the two languages that I maintain.
I used to write "Call for translations" emails, but they never resulted in more translations, so I'm trying something new today: I've created @newsboat/translators team and invited everyone who translated something since 2017 onwards. From now on, I'll update the POT file two weeks before the release, and highlight that team. You all will get emails, and will have two weeks to update your translations and submit PRs. I'm open to suggestions on how to improve that, of course.
Since not everyone accepted the invite to the team yet, I'm mentioning everyone directly too: @adiel-mittmann @alejandrogallo @der-lyse @carno @deob83 @bitigchi @programandala-net @esteban123456789 @tkerdonc @dennisschagt
If you don't accept the invite, I promise not to bug you about translations anymore.

Coverage remained the same at 57.18% when pulling d35ef7956ea39d3a561f43f93b3e86b71e8dd871 on feature/update-ru-uk-translations into 9d97282a13dfceaf4bfbc6d920341e3c0cff104f on master.

Thanks! :)

Um, upon re-reading, I realise I didn't mention that 2.21 release will happen this Sunday, so it'd be nice if the updated translations are posted before then. The well-maintained ones only need 13 messages to be updated, while others need way more work and probably won't make it in time for the release—which is okay, since the next one is just 3 months away ;)


Cloud Service deployment fails with ARM-based storage account

Required Information
Entering this information will route you directly to the right team and expedite traction.
Question, Bug, or Feature?
Type: Bug
Enter Task Name: AzureCloudPowerShellDeploymentV1
Environment

Server - Azure Pipelines or TFS on-premises? Azure Pipelines

If using Azure Pipelines, provide the account name, team project name, build definition name/build number:

Account Name: adunnith at microsoft (Adi Unnithan)
Organization: empowermd
Team Project Name: IntelligentScribe
Build Definition Name: RecorderBotService-CI-TEST
Build Number: 20200426.6
Agent Specification: windows-2019
Issue Description
I was trying to use the cloud deployment task and it fails with an ARM-based storage account. The task looks like this:
 - task: AzureCloudPowerShellDeployment@1
    displayName: 'Bot Service Deploy: $(BotServiceName)'
    inputs:
        azureClassicSubscription: ${{ parameters.classicSubscription }}
        EnableAdvancedStorageOptions: true
        ARMConnectedServiceName: ${{ parameters.armBuildStorageSubscription }}
        ARMStorageAccount: $(BuildStorageAccount)
        ServiceName: $(BotServiceName)
        ServiceLocation: $(RegionName)
        CsPkg: $(Pipeline.Workspace)/cspkg/**/*.cspkg
        CsCfg: $(Pipeline.Workspace)/cscfg/**/*.cscfg
        AppendDateTimeToLabel: true
        AllowUpgrade: true

When running this, the Set-AzureDeployment step errors out because CurrentStorageAccountName was not set for the subscription via Set-AzureSubscription.
##[debug]Exception:
##[debug]System.ArgumentException: CurrentStorageAccountName is not set. Use Set-AzureSubscription subname -CurrentStorageAccountName storageaccount to set it.
##[debug]   at Microsoft.WindowsAzure.Commands.ServiceManagement.HostedServices.SetAzureDeploymentCommand.ExecuteCommand() in d:\workspace\powershell-sign\src\ServiceManagement\Compute\Commands.ServiceManagement\HostedServices\SetAzureDeployment.cs:line 217
##[debug]   at System.Management.Automation.CommandProcessor.ProcessRecord()
##[error]CurrentStorageAccountName is not set. Use Set-AzureSubscription subname -CurrentStorageAccountName storageaccount to set it.
##[debug]Processed: ##vso[task.logissue type=error]CurrentStorageAccountName is not set. Use Set-AzureSubscription subname -CurrentStorageAccountName storageaccount to set it.
##[debug]Processed: ##vso[task.complete result=Failed]

If I set up a new Classic Storage Account and don't use the ARM capabilities with this task like the following, then it succeeds:
 - task: AzureCloudPowerShellDeployment@1
    displayName: 'Recorder Bot Service Deploy: $(BotServiceName)'
    inputs:
        azureClassicSubscription: ${{ parameters.classicSubscription }}
        EnableAdvancedStorageOptions: false
        StorageAccount: classicstoragetest
        ServiceName: $(BotServiceName)
        ServiceLocation: $(RegionName)
        CsPkg: $(Pipeline.Workspace)/cspkg/**/*.cspkg
        CsCfg: $(Pipeline.Workspace)/cscfg/**/*.cscfg
        AppendDateTimeToLabel: true
        AllowUpgrade: true

Task logs
Feel free to email me at adunnith at microsoft for a zip file with the logs.
Troubleshooting
Checkout how to troubleshoot failures and collect debug logs: https://docs.microsoft.com/en-us/vsts/build-release/actions/troubleshooting
Error logs
##[debug]Exception:
##[debug]System.ArgumentException: CurrentStorageAccountName is not set. Use Set-AzureSubscription subname -CurrentStorageAccountName storageaccount to set it.
##[debug]   at Microsoft.WindowsAzure.Commands.ServiceManagement.HostedServices.SetAzureDeploymentCommand.ExecuteCommand() in d:\workspace\powershell-sign\src\ServiceManagement\Compute\Commands.ServiceManagement\HostedServices\SetAzureDeployment.cs:line 217
##[debug]   at System.Management.Automation.CommandProcessor.ProcessRecord()
##[error]CurrentStorageAccountName is not set. Use Set-AzureSubscription subname -CurrentStorageAccountName storageaccount to set it.
##[debug]Processed: ##vso[task.logissue type=error]CurrentStorageAccountName is not set. Use Set-AzureSubscription subname -CurrentStorageAccountName storageaccount to set it.
##[debug]Processed: ##vso[task.complete result=Failed]

+1
My team has also encountered this issue. We migrated many storage accounts to ARM, only to find out that our release pipelines broke.
This fix will have a huge impact on the migration from classic to ARM storage accounts.

The task works on the older Azure RDFE model and uses the Azure RDFE cmdlets because Cloud service also works on RDFE (or classic) model and so requires a classic storage account. And not an ARM storage account.


App Config Provider - Fix Correlation Context

Description
Updated request type to be watch on refresh.
Key Vault Usage wasn't correct on refresh.
All SDK Contribution checklist:

[X] The pull request does not introduce [breaking changes]
[X] CHANGELOG is updated for new features, bug fixes or other significant changes.
[X] I have read the contribution guidelines.

General Guidelines and Best Practices

[X] Title of the pull request is clear and informative.
[X] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[X] Pull request includes test coverage for the included changes.

API change check
API changes are not detected in this pull request.


CURAND Gen Uniform float failed

[09:15:29] /root/mxnet/dmlc-core/include/dmlc/logging.h:235: [09:15:29] /root/mxnet/mshadow/mshadow/./random.h:344: Check failed: (status) == (CURAND_STATUS_SUCCESS) CURAND Gen Uniform float failed. size = 65536
[09:15:29] /root/mxnet/dmlc-core/include/dmlc/logging.h:235: [09:15:29] src/engine/./threaded_engine.h:306: [09:15:29] /root/mxnet/mshadow/mshadow/./random.h:344: Check failed: (status) == (CURAND_STATUS_SUCCESS) CURAND Gen Uniform float failed. size = 65536
An fatal error occurred in asynchronous engine operation. If you do not know what caused this error, you can try set environment variable MXNET_ENGINE_TYPE to NaiveEngine and run with debugger (i.e. gdb). This will force all operations to be synchronous and backtrace will give you the series of calls that lead to this error. Remember to set MXNET_ENGINE_TYPE back to empty after debugging.
terminate called after throwing an instance of 'dmlc::Error'
  what():  [09:15:29] src/engine/./threaded_engine.h:306: [09:15:29] /root/mxnet/mshadow/mshadow/./random.h:344: Check failed: (status) == (CURAND_STATUS_SUCCESS) CURAND Gen Uniform float failed. size = 65536
An fatal error occurred in asynchronous engine operation. If you do not know what caused this error, you can try set environment variable MXNET_ENGINE_TYPE to NaiveEngine and run with debugger (i.e. gdb). This will force all operations to be synchronous and backtrace will give you the series of calls that lead to this error. Remember to set MXNET_ENGINE_TYPE back to empty after debugging.
Aborted (core dumped)

Help!!!

@liuxialong Could you help submit an example code that reproduces this error message?
Also, what's your CUDA version and GPU version? Random generator in CUDA 7.5 does not work on Pascal GPUs.
See also https://github.com/dmlc/mxnet/issues/1240

upgrade to cuda 8.0 or generate random numbers on cpu then copy them to gpu.
This is a know bug before cuda 8.0

Sorry,I've updated the cuda version from 7.5 to 8.0,but still remain this error?

same issue under docker. Without nvidia-docker - its okay

This issue is closed due to lack of activity in the last 90 days. Feel free to reopen if this is still an active issue. Thanks!


Feature Request: Rearrange the order of your accounts

Original issue 118 created by FlintB on 2011-11-09T07:30:09.000Z:
What version of the product are you using? On what operating system?
Version 0.73 on Android version 2.3.7
Please provide any additional information below.
I'm using Google Authenticator to manage many different accounts. I'd like the ability to rearrange the order of my accounts in GA.

  Welcome to mediocre Google.  I am now an Authy user as well and it's 2015...

How's the status of this feature?

As you'll see, the status of this issue is "closed". For more details, see rest of thread.

Holy crap, is this really something that's not possible, and has not been done after all this time?  Such standard operations should not be able to be requested and denied...  Good grief.  This is the one thing stopping me from adopting this app more than I have to.  I don't want to have to remove all my accounts just to re-add them in the order I want every time I add a new one.

@matt-tatnell

your pull request must have gotten lost somewhere. Could you send it again?
Like the comment before yours says, please read the rest of the thread before commenting, especially if you're going to rant.

I knew how bad google was but this is just too funny lol.

I'll just repeat, then:

This issue refers to the Android version.
This issue tracker does not track Android feature requests
Ergo, the bug is closed

Hilariously enough though: an update was just pushed to my phone today finally adding the reorder feature.  Better late than never I guess! :)

I'm glad your entitlement worked out for you.


FailedPreconditionError: Attempting to use uninitialized value

I'm trying to use a resnet-50 Unet with encoder weights from imagenet.
But I'm getting the next error:
FailedPreconditionError: Attempting to use uninitialized value decoder_stage0_bn1_5/moving_mean/biased
[[Node: decoder_stage0_bn1_5/moving_mean/biased/read = IdentityT=DT_FLOAT, _class=["loc:@decoder_stage0_bn1_5/AssignMovingAvg"], _device="/job:localhost/replica:0/task:0/device:CPU:0"]]
I tried both encoder_weights='imagenet' and encoder_weights=None.
IMAGE_SIZE=224
model = Unet(backbone_name=BACKBONE_NAME, encoder_weights='imagenet',
                 freeze_encoder=True,
                 input_shape=(IMAGE_SIZE, IMAGE_SIZE, 3))
model.compile('Adam', 'binary_crossentropy', ['binary_accuracy'])

    ...

history0 = model.fit_generator(train_gen,
                                  callbacks=[learning_rate, save_checkpoints],
                                  epochs=2,
                                  shuffle=True)

It seems like if the the Unet expansive path hadn't been initialized.
How could I solve this?

Hi,
I installed via pip segmentation_models 0.1.2
Using keras 2.2.2 and tf 0.10.1
The same error with freeze_encoder=True and with freeze_encoder=False
Thanks qubvel

Did you mean tf version 1.10.1?

I was not able to reproduce your error with following:
Evironment
Docker image: python:3.6
tensorflow==1.10.1 (cpu)
keras==2.2.2
scikit-image==0.14.1
segmentation-model==0.1.2

Code
import numpy as np
from segmentation_models import Unet

x = np.ones((160, 224, 224, 3))
y = np.ones((160, 224, 224, 1))

model = Unet('resnet50', encoder_weights='imagenet',
                 freeze_encoder=True,
                 input_shape=(224, 224, 3))

model.compile('Adam', 'binary_crossentropy', ['binary_accuracy'])
model.fit(x, y, epochs=10)

Everything works fine, maybe something wrong with your environment?

Hi Pavel,
There was a bug in a piece of my code that I didn't write in the issue summary.
I was using importing a tensorflow package (from tf.keras.callbacks) instead of importing from keras.callbacks
This solved my problem:
learning_rate = keras.callbacks.LearningRateScheduler(cosine_annealing)
Thanks a lot for helping me and for your pretty segmentation models library!


heroku integration

push button config with loggly integration.

https://github.com/oreoshake/octopusci-heroku


Switch to dynamic Riverside CA source

Our current riverside, CA source is missing a lot of new subdivisions like the one above

https://github.com/openaddresses/openaddresses/commit/53c2c92ca2ce1ffc85aa4bb0b2e890760b0b52c1 updated the source for Riverside County. Should this PR be closed?


Simple question

Hello)
@adieuadieu, could u, please, explain for me some simple stuff:
How is that possible that chrome can bind to the port 9222 on aws lambda?
Does it binds to a port at all?
I'm asking because i want to use binary with cdp client written in go.
Will it work at all?
Sincerely

Hi @yarikbratashchuk. I'm not sure I understand your question. Chrome binds to port 9222 just like any other program can bind to a port. Lambda doesn't forbid you from creating ports. You should be able to use Go to connect to port 9222 from within a Lambda invocation. However, you won't be able to connect to the port from outside of the Lambda function. Lambda functions do not have a public IP.

@adieuadieu thank u for the answer)
The go client makes get request to  http://<IP_ADDRESS>:9222/json/new, but gets "context deadline exceeded", that is why i asked, it doesn't work for me for now.
How much memory this lambda probably need?

Hi @yarikbratashchuk. I'm not familiar with that error message. Is there any more information in the function's CloudWatch logs? I would recommend running the function with at least 1024 MB of memory. I usually use the maximum 1536 MB. Chrome is not.. lightweight.

@adieuadieu, this is what i get when try to test function via aws lambda dashboard:
 "Get http://localhost:9222/json/new: dial tcp <IP_ADDRESS>:9222: getsockopt: connection refused"
"context deadline exceeded" means that some time has passed but it didn't get a response from "http://<IP_ADDRESS>:9222/json/new".
Does headless_shell depends on some js stuff, to work?
Do i need to set --headless flag?
Thanks a lot

Hm..
Launch the headless_shell with --disable-gpu --single-process --no-zygote --no-sandbox flags. If you want logging, add --enable-logging --log-level=0 --v=99. Try to capture or log the output from headless_shell to CloudWatch (in JS this is done with console.log.) There's usually some kind of error that gets logged by headless_shell if something went wrong.

@adieuadieu, seems like no logs on startup.


[okina] Cleanup of the okina branch before mfem-4.0 merge

Support 'make cuda' in the makefile
Edits in the memory manager
Consolidating okina and its backends.
Replaced __NVCC__ with MFEM_USE_CUDA and __OCCA__ with MFEM_USE_OCCA
Renamed the config class to Device (and general/config.?pp to general/device.?pp), and simplified its use in the examples
Renamed linalg/device.hpp to linalg/dtensor.hpp and replaced DeviceVector3 with DeviceVector.
Removed __restrict as it may not be standard (we can use a compiler option instead)
Added device sample runs in examples
Mentioned C++11 in CONTRIBUTING.md
Updated CHANGELOG

This is ready for review. Thanks for your help @camierjs!


publishing a new version to npm

#249 has a lot of goodies in it, and I'm using gl-matrix via npm

I've got at least one more change I would like to see make it in (#251) but I plan on pushing it to NPM after that's landed.

Done!


Websockets do not work properly.

Due to issues with firewalls or something, when opening a websocket to a wss://_____ address, the thing seems to instead convert it to a https://____ request, which the apache proxy does not forward properly.
Suggested change:
Have a /wss subdomain, so the websocket makes a request to wss://ml-api.uk.ms/wss/...., which even if the request fails and goes to https://ml-api.uk.ms/wss, we can proxy properly.

shush

This issue has been solved by whitelist to firewall.
Apache frontend should attempt to proxy any websocket connections with Sec-WebSocket-Key even if it does not contain the Connection: upgrade headers.


Support for logging-setup

I find click wonderful as it simplifies all my cli-related code lines.
What I also do besides argument checking (what click does) is setting up the logging (using Python's logging-facilities) according to certain parameters.
I'd find it great, if click would also do that. Namely...

Understand -q for quiet mode (call logging.basicConfig(level=logging.CRITICAL))
Understand -v for verbose mode (call logging.basicConfig(level=logging.INFO))
Understand -d for debug mode (call logging.basicConfig(level=logging.DEBUG))

Call logging.basicConfig(level=logging.ERROR) without any specific parameter.
That could be done using another decorator like @simplelog.

I think it's unnecessary to have three switches for the same feature. How py.test does it, also it appears in click documentation: with count for e.g. -v, so like $ command -vvv is more verbose than $ command -vv

I'll add that flavor to my pull request.

Please merge this - @click.simplelog(flavor='vvv') is pretty much what I need.

If you're interested in this, there is a basic implementation at https://github.com/click-contrib/click-log. Patches for other option flavors are welcome!


Multiple Popover

I am getting this issue of multiple popover on my site. I am not using the tour css file and also backdrop is not getting removed when clicked on next step or even when tour is ended.
`var tour = new Tour({
steps: [
{
element: "#menu-primary-navigation > li.active.menu-home > a",
title: "Initialize",
content: "Content of my step",
position:"bottom"
        }

        ]
});

tour.addSteps([
{
element: "#menu-primary-navigation > li.active.menu-home > a",
title: "Step 1",
content: "Content of my step"
},
{
element: "#menu-primary-navigation > li.active.menu-home > a",
title: "Step 2",
content: "Content of my step"
}
]);
            tour.init();

            tour.start();

        }`

are u using SPA?
Cause if you implemented this in your controller, every time you activate that controller you create another instance of this tour

No I am just adding it on page directly in script tag. Also I have commented out the window resize code in the library to check if its triggering with that resize event but its still there.

Try using a more specific selector e.g. "#menu-primary-navigation > li.active.menu-home > a:first-child" or  document.querySelectorAll(""#menu-primary-navigation > li.active.menu-home > a"")[0]


Helm chart fails to recognize kubernetes in Installation.spec.calicoNetwork.nodeAddressAutodetectionV4

Expected Behavior
It should be possible to change the autodetection method to Kubernetes / Internal IP as documented on https://projectcalico.docs.tigera.io/networking/ip-autodetection#change-the-autodetection-method using the Helm chart
Current Behavior
Using this values file:
installation:
  calicoNetwork:
    nodeAddressAutodetectionV4:
      kubernetes: NodeInternalIP

the installation using /usr/sbin/helm --version=3.21 upgrade -i --reset-values --create-namespace -f=/tmp/values.yml -n calico-system calico projectcalico/tigera-operator fails:
Error: unable to build kubernetes objects from release manifest: error validating "": error validating data: ValidationError(Installation.spec.calicoNetwork.nodeAddressAutodetectionV4): unknown field "kubernetes" in io.tigera.operator.v1.Installation.spec.calicoNetwork.nodeAddressAutodetectionV4

Possible Solution
The API spec at https://projectcalico.docs.tigera.io/reference/installation/api#operator.tigera.io/v1.NodeAddressAutodetection suggests that the field exists. The schema may have a bug.
Steps to Reproduce (for bugs)

Create values.yml file as above
Run setup command
Observe failure

Context
Attempt to provision a kubernetes cluster using ansible and helm, where calico picks up the wrong IP address
Your Environment

Calico version 3.21
Orchestrator version (e.g. kubernetes, mesos, rkt): kubernetes 1.21, helm 3.8.1
Operating System and version: Ubuntu 21.10

kubernetes: NodeInternalIP is not valid in Calico v3.21 - it was introduced in v3.22.0.  See https://projectcalico.docs.tigera.io/archive/v3.22/release-notes/#other-changes-1


Encoding Multiple Sentences for Roberta?

The .encode method converts all the 3 sentences to a 1-D array with placeholders('<s>') to signify separators. How do I use this as an input to a classification task for 3 sentences?

Since output size is flattened [18], the model with a classification head of 2 classes, is just returning a single prediction instead of 3 predictions. Is there a way to encode multiple sentences in bulk as separate tokens?

Ah, for three separate examples you should call encode three times. You can then use fairseq.data.data_utils.collate_tokens to merge them into a batch. The predict function will operate fine on the batch of inputs and return a 3x2 output.

Thank you for clarifying. Won't it be a performance bottleneck to make repeated calls to encode for large number of responses? How was this handled during your experiments?

Ah, if you want to BPE-encode a large volume of text then you should use the multiprocessing_bpe_encoder: https://github.com/pytorch/fairseq/blob/master/examples/roberta/multiprocessing_bpe_encoder.py
Then you can pass through the standard fairseq-preprocess script using the dict.txt from the RoBERTa archive.

We wrote a more detailed writeup here: https://github.com/pytorch/fairseq/blob/master/examples/roberta/README.finetune_custom_classification.md

Hey! I was wondering how would the predict function for mnli.large model work in case the input is provided in batches. As in, what would the scores indicate?
I have also opened a separate issue about this here: https://github.com/pytorch/fairseq/issues/1167
Would be grateful for some help.


Support debounced web request to remoteUrl

The paper-typeahead-input supports a remoteUrl and combines the fetched results with the suggestion list. This is a great feature!
However, I have been avoiding it because I do not want to hammer the server by sending a new web request every time the user types a new character. Typically, the user  will type several characters, maybe deleting a few and typing more to spell the beginning of a longer word or sentence. Every one of those changes sends a web request. By making the web request function call debounced, lets say 250 ms, the number of unnecessary web requests will be be reduced by a lot.
So what I do right now is to externally debounce a web request when the bind-value-changed event fires from the paper-input, and I rebind the pt localCandidates list with the result. I then call the private function _search (which i should not do...) to display the new suggestions from localCandidates. It would be nice if paper-typeahead-input would support a debounced web request to remoteUrl.
This would not add much extra complexity to the code, it would simply be the same function call, only wrapped with a debouncer. The debounce wait time could be a new property 'debounceMs' (type: Number) that defaults to undefined, which will cause the function to be called as soon as possible so the behaviour will remain the same as now.
    if (typeof(this.remoteUrl) != 'undefined'){
        var self = this;
        this.debounce('remoteSearch', function() {
           var url = self.remoteUrl.replace("%QUERY", term);
           ...
           xmlhttp.send();
         }, this.debounceMs);
    }

It would probably make sense to cancel the debounced function call when the user confirms a suggestion (has found what he/she was searching for), like so:
   this.cancelDebouncer('remoteSearch');

This is an interesting point. So in summary, you are suggesting:
add some customizable delay to the search for remoteUrl
instead of firing the http request after typing every single word.
Is that correct?
Say, if set up the delay wait time to be 1 second,
the user type "a", then a search to remoteUrl is set up by debounce, and will fire up after 1 second,
but user types fast and another "b" comes, so a new search is set up with search term "ab" and scheduled to be fired up 1 second later.
The first search hasn't been fired and it will be canceled automatically ( I guess, I am not very familiar with the debounce function. Polymer doc said: Call debounce to collapse multiple requests for a named task into one invocation, which is made after the wait time has elapsed with no new request. ).
So without the delay feature, 2 calls will be made, and with only 1 call will be made.
Am I right about the concept here?

That's exactly right. Debouncing the web request is a simple way to reduce the burden on the remote web server in this case. There is really not much point in sending the web request as long as the user keeps typing. I find that a wait time of 250ms or maybe a bit lower works pretty well for me.

This debounced feature has been implemented in release 1.3.1.
I am not sure about the cancelDebouncer. When user begin to select, either by mouse or by keyboard, they already stopped typing, no more request should be in the queue at the moment an item from suggestion is confirmed(if the wait time is set up properly).
.

Perfect, I tested it and it works well.  Thank you very much for the quick update.
Would it be possible to add a Boolean property with notify: true that indicats that there is an async web request going on? That way I can display a paper-spinner elsewhere on my page when that value is true.

Well, adding a boolean property will solve the problem but I am not sure if that is intuitive enough.
A boolean property called remoteUrlSearching? to indicate if a request is on the way?
How about firing custom event when request is scheduled and request is finished?
Or both?

Yes an event would work. I could use a handler for that event like so:

...
handleUrlSearchingChanged: function(remoteUrlSearching) {
   this.$.spinner.active = remoteUrlSearching;
}

Yep. I would say both of the two approached would work. Not sure which one is better, what's your thoughts?

The event, that way I can just copy paste the suggested event handler from this issue thread ;-)
No but seriously, I guess its just a matter of taste and consistency in how your element notifies changes for stuff. A benefit of a custom event is that it bubbles upward, parent elements high up in the hierarchy can listen to the same event. With a property, there would have to be a chain of property propagation.

Think it might be a good idea to support both. Done in 1.3.2. Added property remoteUrlSearching and custom event pt-remote-searching-start and pt-remote-searching-end.

OK!
I noticed a mistake, on this line
this.fire('pt-remote-searching-end',pt_element);

fire is not defined. You need a var self = this or bind the function to this.

+1 to torsjonas.
var self = this , and self.fire required for line 449.

Good call. Fixed.

Hi Guys, @torsjonas  @raghav135
I think this issue is resolved and I am going to close this issue.

I agree, this is resolved. I have tested the same.
Cheers.


deps: try gax 2.17.0 for Java 8 compatibility (not for merge)

Not for merging.
Confirming GAX 2.17.0's Java 8 compatibility.

Assigning to @suztomo to understand if this is ok to close out or if something else needs to be done here?


Results Output Format

Results output formatting to terminal and to file.
Simple idea would be results in dict, pretty print to terminal and output to JSON file
Other things

Should count benchmark run (for iterative learning tasks)

Dump the entire output

For this we might as well just use pprint to pretty print the dict.
import pprint
results = benchmark.run()
pprint.pp(results)


luci-mod-status: extend DSL metrics

This restructures the DSL metrics to make them easier to read, and adds several additional metrics, making use of https://github.com/openwrt/openwrt/commit/b91d7d9d78ea12097de4c518c8cd2215ff286f7a.

Nice, I still need to try this!
This looks all good at first glance, but that DSL status box is getting rather huge.
Maybe we can move some stuff elsewhere? Network/Interfaces/DSL might be too hidden though.
Or group stats by topic and make it child boxes, like the wifi networks are on the phy box? So they float/arrange themselves based on the browser window width, that'll make it at least shrink in height.

I'd say make a separate DSL status page and only keep the most relevant indicators (SNR & line status?) in the general overview page.

I assume it would make sense to add the separate status page to luci-mod-dsl instead of this one then. Should I create a separate pull request for that once it is done?

We could also integrate it into the dsl spectrum status and rename it accordingly.
Tested as-is, apart from the big box it works as described :)

I merged the change for now. Would be great if you could follow up with moving extended status info into a separate view and only keeping most important indicators on the main status screen.


offset in tile corners alignment needs sorting out

The determination of the corner offset between tiles of the same shape is confused with the determination of tile shapes and their symmetries. Would be better to determine the offset, apply it and then return to the other tasks associated with examining tile shapes.

fixed in change from Symmetry class to Transform class


Defining macro environment properties.

Work in progress
Pairs with: https://github.com/FLAMEGPU/FLAMEGPU2/pull/643

This should be complete, might require some editing after a review, but the core information should be present.


feat: add settings menu

Description

add Settings Menu UI
show Settings Menu via .sheet modifier

Related Issues

Closes #689

Progress

How to test it

Start any form of video
Tap on the player to show the control buttons
Tap on the gear icon to show the Settings Menu

Visual reference

I feel like the settings button is a little too big, what do you think about making it smaller?


12567 Fixed Notebook connections not showing in recent connections

Changed tryAddActiveConnection to always add recent connect

This PR fixes #

Reopening PR under a new branch

Pull Request Test Coverage Report for Build 334178537

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.01%) to 39.648%

Files with Coverage Reduction
New Missed Lines
%

src/sql/workbench/services/connection/browser/connectionManagementService.ts
1
76.38%

Totals

Change from base Build 333993046:
0.01%

Covered Lines:
20573

Relevant Lines:
47670

💛  - Coveralls


How to mock session storage when running a test?

I am trying to setup mocha for my reactjs app.
However, running the command mocha --compilers js:babel-register --recursive produces an error saying
mocha --compilers js:babel-register --recursive

/Users/purezen_/workspace/webapp/src/js/data/reducers/auth.js:31
var auth = sessionStorage.getItem('auth');
           ^

ReferenceError: sessionStorage is not defined
    at Object.<anonymous> (auth.js:5:14)
    at Module._compile (module.js:397:26)
    at loader (/Users/purezen_/workspace/kredx-fe/client/node_modules/babel-register/lib/node.js:158:5)

even when I have included code to mock session storage inside the test file according to  http://stackoverflow.com/q/11485420/1509855

Was able to get it working using https://github.com/letsrock-today/mock-local-storage.

This was a lifesaver! Thanks a ton @purezen
I used mock-local-storage to mock my sessionStorage. It was as simple as just installing with npm and running the test. No additional code needs to be written!!

How to do this?
It is not working for me.
Please help

Do I need to change any file?


Background text field gets focused on text field focus

On 1.0.0 if the background page has any text fields it gets focused when we focus the text field of giphy_get

I can't modify focus outside BottomSheet, should relase all focus before call GipyGet()

yes but this wasn't an issue in earlier versions


IE9 scrolls to top every time scrollbar CSS is updated

It's known issue for the IE9
http://stackoverflow.com/questions/11111528/ie9remove-floated-or-absolute-positioned-element-will-cause-sibling-elements
I've added variable to temporarily store scrollTop value before changing CSS, and apply it after.
I think this should work for the scrollbarX too.
var updateScrollbarCss = function () {
$scrollbarX.css({left: scrollbarXLeft + $this.scrollLeft(), bottom: scrollbarXBottom - $this.scrollTop(), width: scrollbarXWidth});
var scrollTopTemp = $this.scrollTop();
$scrollbarY.css({top: scrollbarYTop + $this.scrollTop(), right: scrollbarYRight - $this.scrollLeft(), height: scrollbarYHeight});
$this.scrollTop(scrollTopTemp);
};
Not really good solution, but works (with some flickering in IE of course).

Hi,
When I have a scroller in another one, the parent scroller scrolls the same time with the child (mousewheel)
Could you please help me with this problem? Thank you.


[Help] Steps vertical alignment

What version of daisyUI are you using?
v3.7.3
Describe your issue
I am trying to build a "timeline" by using "steps component". But it gives all "< li >" same highest height, then center.
The "Register" step should appear next to bullet.

What browsers are you seeing the problem on?
Safari
Reproduction URL
https://play.tailwindcss.com/C4B832D0SD

With steps all items have the same size. It's not optimal to use as a timeline where items need different sizes.
It's also not possible to change the behavior of steps because it will break all the current websites that are using it.
A new timeline component will be released soon. I'm working on it and it will be perfect for what you need.

@saadeghi Nice! looking forward

@saadeghi For now I built my own version. But intend to switch to daisyUI component when you release it.
https://mary-ui.com/docs/components/timeline

@robsontenorio Looks good 👍

intend to switch to daisyUI component when you release it

I will let you know when it's ready.
I'm really excited about Mary project 👏
I also added a link on daisyUI's website footer. Let me know if I can help with anything.

With steps all items have the same size. It's not optimal to use as a timeline where items need different sizes. It's also not possible to change the behavior of steps because it will break all the current websites that are using it.
A new timeline component will be released soon. I'm working on it and it will be perfect for what you need.

could you spill the eta?


2 buttons with the same id error, but cannot find any duplicates in XML or UI

Hello,
While trying to publish a particular entity ribbon (Account), I have been unable to use the XRM toolbox version (3.1.391.1.9) of the Ribbon Workbench because it has issues with validation that I can't seem to find a cause for. It indicates that there are two buttons with the same ID:
https://i.imgur.com/rFE4E3H.png
I work around this by using an older solution based version of the workbench for this entity but it only seems to impact our Account entity ribbon.
Any idea what might cause this error or how I would fix it so this stops?

This is usually caused by there being a customisation of a group or tab as well as the actually button.
Download the solution and unzip it - then do a search for the button ID's to see where the duplicates are.

Hmm I verified no duplicate button id's already in the xml. Is it possible
it indicates one id is the duplicate when it is actually some other ID?
On Tue, Sep 8, 2020, 6:03 PM Scott Durow<EMAIL_ADDRESS>wrote:

This is usually caused by there being a customisation of a group or tab as
well as the actually button.
Download the solution and unzip it - then do a search for the button ID's
to see where the duplicates are.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/scottdurow/RibbonWorkbench/issues/51#issuecomment-689181088,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFPL5EFKLELVFZBQDAT7N23SE2Z55ANCNFSM4QVDD6XA
.

The duplicate warning happens when the ribbon xml is being assembled. Could you send me your ribbon xml so I can take a look please?

Hi Scott - thanks for your work, we really depend on you. I was going to open a new issue for this but since this one is so new I thought it might apply. I've been googling for info on the new "Mscrm.OpenRecordItem" feature in PowerApps and how it relates to Ribbon Workbench. The MS documentation around this feature mentions Ribbon Workbench with a big disclaimer, then goes on to describe how to edit RibbonDiffXml directly. As you know, in D365 apps there are both the HomepageGrid along with the SubGrid. In order to override the grid behavior using Mscrm.OpenRecordItem, you have to specify exactly "Mscrm.OpenRecordItem" as the Button ID (for some reason, rather than Command name). However, in RW I believe the CustomAction name is derived from the Button Id. For example, the code below allows both HomepageGrid and SubGrid to use the same command, but this was because I manually changed the ID to 'Mscrm.OpenRecordItem'. This prevents RW from being able to validate the XML, and will not publish any further changes.
<CustomAction Id="pfx.Mscrm.HomepageGrid.opportunity.OpenRecordItem.CustomAction" Location="Mscrm.HomepageGrid.opportunity.MainTab.Management.Controls._children" Sequence="10">     <CommandUIDefinition>         <Button Command="Mscrm.OpenRecordItem" Id="Mscrm.OpenRecordItem" LabelText="$LocLabels:pfx.Mscrm.HomepageGrid.opportunity.OpenRecordItem.LabelText" Sequence="10" TemplateAlias="o1" />     </CommandUIDefinition> </CustomAction> <CustomAction Id="pfx.Mscrm.SubGrid.opportunity.OpenRecordItem.CustomAction" Location="Mscrm.SubGrid.opportunity.MainTab.Management.Controls._children" Sequence="1">     <CommandUIDefinition>         <Button Command="Mscrm.OpenRecordItem" Id="Mscrm.OpenRecordItem" LabelText="$LocLabels:pfx.Mscrm.SubGrid.opportunity.OpenRecordItem.LabelText" Sequence="1" TemplateAlias="o1" />     </CommandUIDefinition> </CustomAction>

Ribbons.zip
@scottdurow Attached two ribbon xml. Seeing the issue on the Contact entity as well.


[AppConfig] October release preparation

Prepare the release process for AppConfig October

API change check
API changes are not detected in this pull request.


PacReq: nerd-fonts-hack

Patched font Hack from nerd-fonts library.
URL: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=nerd-fonts-hack
Building Guide: https://gist.github.com/smac89/35d1c7576889419854e3c7d2684cb759
Error I get when trying: https://gist.github.com/HarleyQuinn-Z6/c521e9f2d585c0bcca1098a34f196779
nerd-fonts-hack.pacscript
name=nerd-fonts-hack
pkgname=nerd-fonts-hack
version="2.1.0"
url="https://github.com/ryanoasis/nerd-fonts/releases/download/v$version/Hack.zip"
description="Patched font Hack from nerd-fonts library"
hash="70852e59fcffbe31d401f615625bcb9ebb6af72732c2f1fe9b9d5370c2565514"
maintainer="ajr<EMAIL_ADDRESS>
prepare () {
    true
}

install() {
    install -d "$STOWDIR/$name"/usr/share/fonts/TTF
    rm "${SRCDIR}/"*"Windows Compatible.ttf"
    install -Dm644 "${SRCDIR}/"*.ttf "$STOWDIR/$name"/usr/share/fonts/TTF
}

Your $name is nerd-fonts-hack-git but your not pulling from a git repo 🤔

Fixed that.

Add
build() {
	true
}

Segmentation fault (core dumped)

Can you send the full log?

Patched font Hack from nerd-fonts library.
URL: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=nerd-fonts-hack
Building Guide: https://gist.github.com/smac89/35d1c7576889419854e3c7d2684cb759
Error I get when trying: https://gist.github.com/HarleyQuinn-Z6/c521e9f2d585c0bcca1098a34f196779
nerd-fonts-hack.pacscript
name=nerd-fonts-hack
pkgname=nerd-fonts-hack
version="2.1.0"
url="https://github.com/ryanoasis/nerd-fonts/releases/download/v$version/Hack.zip"
description="Patched font Hack from nerd-fonts library"
hash="70852e59fcffbe31d401f615625bcb9ebb6af72732c2f1fe9b9d5370c2565514"
maintainer="ajr<EMAIL_ADDRESS>
prepare() {
    true
}

build() {
    true
}

install() {
    install -d "$STOWDIR/$name"/usr/share/fonts/TTF
    rm "${SRCDIR}/"*"Windows Compatible.ttf"
    install -Dm644 "${SRCDIR}/"*.ttf "$STOWDIR/$name"/usr/share/fonts/TTF
}

Your install commands in install() need sudo

Nice. It's working now. You can add it to the packages. I don't use github since they stopped allowing user and password.


[question] any idea on how to test these in github actions?

[edit]: I managed to make it work; See reploy to original post.
Locally, on multiple computers of mine (different OS) everything works fine. However, when I run this on CI/CD via github actions, I get this pesky error which I was also getting when I was executing the against a regular chromium app (non-production build).
Getting a little desperate here. The build is available as expected on the out dir, just like locally.
    Error: electron.launch: Process failed to launch!

      21 |   process.env.CI = 'e2e'
      22 |
    > 23 |   electronApp = await electron.launch({
         |                 ^
      24 |     args: [appInfo.main],
      25 |     executablePath: appInfo.executable,
      26 |   })

Hope you have some pointers for me! :robot:
For curiosity, here's a minimum version of my checks-slow.yml (which contains the e2e tests)
name: Callable - Slow Checks

on:
  workflow_call:

jobs:
  e2e-test:
    timeout-minutes: 20
    name: 🐌 Slow checks
    runs-on: ubuntu-latest

    steps:
      - name: 🦖 Cancel Previous Runs
        uses<EMAIL_ADDRESS>
      - name: 🔻 Checkout repo
        uses: actions/checkout@v3

      # Basically runs `npm run ci`
      - name: 🏃 Run Node and NPM setup
        uses: ./.github/actions/setup-project

      - name: 🌏 Install playwright chromium browser
        run: npx playwright install --with-deps

      # Createsa build for the currently running OS (linux ubuntu in this case)
      - name: 🏗 Build test project
        run: npm run build

      # Basically `npx playwright test`
      - name: 🎭 Run Playwright tests
        run: npm run playwright:ci

      - name: 📄 Upload test results
        uses: actions/upload-artifact@v3
        if: always()
        with:
          name: playwright-report
          path: playwright-report/
          retention-days: 30

      # Add this because I got it to work on multiple OS runners :)
      - name: 🏗 Build test project
        run: |
          if [ "$RUNNER_OS" == "Linux" ]; then
            npm run build:linux
          elif [ "$RUNNER_OS" == "macOS" ]; then
            npm run build:mac
          elif [ "$RUNNER_OS" == "Windows" ]; then
            npm run build:win
          else
            echo "Operating system $RUNNER_OS is not supported"
            exit 1
          fi
        shell: bash

      # This action was the important part, it sets up and cleans up XVFB when running on Linux)
      - name: 🎭 Run Playwright tests (using XVFB*)
        uses<EMAIL_ADDRESS>        with:
          # Moved the test command here
          run: npm run playwright:ci

A lot of the work on this repository has moved over to the electron-playwright-helpers repository. There's a GitHub workflow over there which shows how to configure a Playwright e2e test.
Sounds like you've got things working. But maybe this is helpful too.


(~20%) Update broken links from url_checker

~20% of links found in #1586 (url_checker). THIS WILL NOT CLOSE THE ENTIRE ISSUE.

free-programming-interactive-tutorials-en.md

[x] 404 Not Found http://jhusain.github.io/learnrx/

free-programming-books-ja.md

[x] 500 Can't connect to www.narihiro.info:80 (Connection refused) http://www.narihiro.info/g1gc-impl-book/
[x] 404 Not Found http://rd.clojure-users.org/
[x] ARCHIVED > 500 Can't connect to www.doyouphp.jp:80 (Bad hostname) http://www.doyouphp.jp/book/book_phpdp.shtml
[x] ARCHIVED > 404 Not Found http://www4.ocn.ne.jp/~inukai/scheme_primer_j.html
[x] ARCHIVED > 404 Not Found http://karetta.jp/book-cover/gauche-hacks
[x] 404 Not Found http://gst.plasticheart.info/tutorial-c84

free-programming-books-tr.md

[x] 500 Internal Server Error http://www.kaanaslan.com/resource/course_note/download_file.php?file_id=16

free-programming-books.md

[ ] 404 Not Found http://stackoverflow.com/revisions/392926/175
[x] 404 Not Found http://www.songho.ca/opengl/index.html
[x] 404 Not Found http://see.stanford.edu/see/materials/aimlcs229/handouts.aspx
[x] 404 Not Found http://web.mit.edu/~holden1/www/math/number-theory.pdf
[x] 404 Not Found http://www.iitg.ac.in/kartha/CE601-14/CourseSchedule.htm),2014
[x] 404 Not Found http://cm.bell-labs.com/cm/ms/what/shannonday/paper.html

Some links are crossed out because they worked for me (New Jersey, USA). If they do not work elsewhere, let me know.
Some Japanese links are unchecked. Because I do not know Japanese, I used the Web Archive links for the meantime
The "original list" from StackOverflow can no longer be found, not even on Web Archive

Note to self: squash commits 5adb785, 51ea4bc, d836607 as they all update free courses doc

👍🏻

@borgified This pull request is ready for review. I made it smaller so others could submit changes, as well.

:+1:

:+1:


Does not account for flying in spectator mode

Hello!
I've noticed mod doesn't account for flying in spectator mode, in https://github.com/tired9494/Flight-Rings/blob/f07cad51ecf601fc82d10d4697b980a25e6db08b/src/main/java/flight_rings/flight_rings/rings/AdvancedRing.java#L98 there is an exception for creative mode however none for spectator mode which results in noclip falling into void and dying.
By the way, thank you for creating the mod!

Thank you,
this has been fixed in 1.4.2


unk issue

When I ran tutorial 4 and ran a variation of tutorial 4 since I wanna develop a similar seq2seq model to work on other tasks, I noticed that there wasn't any <unk> in translation. It's amazing but also troublesome since we do wanna see some <unk>'s in inference and then we can apply some techniques like copy mechanism to boost up the translation quality

The source and target vocabularies are built with a min_freq of 2, so there will be <unk> tokens. I am 100% sure I have seen them myself - I'll see if I can find a concrete example.

You are right, man. I set min_freq to be 1 so there is no unk appearing in training or testing


Find OpenAL correctly on iOS

Following on from #1263
This removes the conditional checks which were stopping openAL being found properly on iOS, and updates the relevant includes

Does this find the OpenAL framework in macOS SDK, or iOS SDK, or the headers provided by SFML? In my opinion the best would be to use the framework from iOS SDK but I don’t think current code with find_host_package() does this. And actually there is most likely no search to do, just using flag «-framework OpenAL » should use the correct headers (from iOS SDK).

For me, it finds the openAL framework in the iOS sdk: /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator11.2.sdk/System/Library/Frameworks/OpenAL.framework

Ok.. then I really don’t understand the purpose of find_host_package() which is made (from what I understand) specifically to NOT find dependencies for the target system but for the host...
Can check what I get with your branch on my PC in ~2 days if you want to wait.

Here is what I get with your branch

So for OpenAL it looks good indeed, even if I'm still puzzled by find_host_package() and its expected behavior…

I think the intention is that find_package should only search in the relevant sdk, and find_host_package uses all the standard search paths?
If that's correct, then it should probably be find_package for openAL, instead of find_host_package?

This is also my understanding… but hey, good luck getting it to work with just find_package() :)

I just tried using find_package() for openAL, and it seems to still work as expected. It's the other 3rd party libs which don't like find_package(), because they aren't installed in the sdk, as expected. Are you able to do a quick test using find_package for openAL and confirm it still works for you too?

find_package() indeed works fine for OpenAL, which makes sense indeed… so it could be fixed (at least for this dependency).
As a sidenote, it is however possible to wait for https://github.com/SFML/SFML/pull/1335 to be merged before this PR? #1335 assumes that all find_package() on iOS actually are find_host_package() so they were all factorized in sfml_find_package(). If we introduce an exception for OpenAL, it'll require significant changes in the already long-waiting PR :(

I have no problem with waiting. I haven't changed this PR, so it still uses find_host_package, so it can either be merged in it's current state which (if I understand correctly) won't conflict with #1335, or If #1335 is merged first I will make the relevant changes to this PR

See https://github.com/SFML/SFML/pull/1335/files#diff-6e3aba620b5d5027b0b256ccb9ad1063
A lot has changed actually so even if this PR was merged as-is it would conflict. I've been too greedy in changing everything, sorry 😄

No worries, this is a super simple fix, so let's just pop it on hold, and I'll update once #1335 is merged.


"yakut publish" should print the published message (like "yakut subscribe")

This will also resolve the common misunderstanding when people believe that the command is not going anything because it is producing no output.


Fix nightly build for API docs

The nightly API docs depend on the Operator, which is not built
https://github.com/keycloak-rel/keycloak-rel/actions/runs/9278480146/job/25529571886#step:4:44135

Superseded by https://github.com/keycloak/keycloak/issues/29984


English Document has lack of info with 'Microsoft.ContainerService'

Hello, I found out the following actions are listed in Microsoft.ContainerService when document is in Japanese but it does not include in English.
Could you please fix the document please?
/containerServices/subscriptions/read サブスクリプションに基づいて、指定されたコンテナー サービスを取得します。
/containerServices/resourceGroups/read リソース グループに基づいて、指定されたコンテナー サービスを取得します。
https://docs.microsoft.com/en-us/azure/active-directory/role-based-access-control-resource-provider-operations#microsoftcontainerservice
https://docs.microsoft.com/ja-jp/azure/active-directory/role-based-access-control-resource-provider-operations#microsoftcontainerservice

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

ID: 33219707-3b9f-cc6b-541e-a806dc82622a
Version Independent ID: b4e96391-bcf9-1f30-cb44-ed339469da4f
Content: Azure Resource Manager Provider Operations
Content Source: articles/active-directory/role-based-access-control-resource-provider-operations.md
Service: active-directory
GitHub Login: @rolyon
Microsoft Alias: rolyon

@KeiroKamioka0000
Thanks for your feedback! We will investigate and update as appropriate.

@MohitGargMSFT, can you please assign this issue to @DavidPrio

Hi all,
This doesn't look like a localization issue.
None of the mentioned items can be found neither the localized version nor the source pages:
/containerServices/subscriptions/read
/containerServices/resourceGroups/read
Please check on your side if this repro and confirm if we can close this issue.
Kind regards,
Microsoft DOCS International Team

Hello, @KeiroKamioka0000

Thank you for your feedback.

The issue was solved after the latest update and now the current version of both en-US and localized pages match.
We truly appreciate your contribution to our articles and we encourage you to continue providing your valuable feedback.
Kind regards,
Microsoft DOCS International Team
@MohitGargMSFT  you can close this issue


musikcube: 0.96.7 -> 0.96.9

motivation
musikcube was out of date and refused to build
things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

@ofborg build musikcube

it looks like there was another release since this one. i'm going to update this pull request with it in a moment

alright. i've updated the derivation again and tested the resultant binaries. that should be good for now

Thanks!


Handle CMake warning(s) on Policy

Policy CMP0115 is not set: Source file extensions must be explicit

This warning arises in some (or all) CMake builds. The purpose of this issue is to understand and eliminate these warnings.

See also #284