Missing Dependencies

I am trying to build the repo that I just cloned and getting the following error:
[ERROR] /E:/github/apis/apis-surfconext-authn/src/main/java/org/surfnet/oaaas/conext/SAMLAuthenticator.java:[39,39] package org.opensaml.ws.message.decoder does not exist
What repository contains the missing dependencies?
Thanks,
Caleb

Interesting error. That specific package should be provided by one of the opensaml dependencies. You should not need any specific configuration whatsoever for fetching those.
Can you have a thorough look through the maven log file (perhaps share it with us using Github Gist?) for hints that these dependencies cannot be fetched?

Thanks for the fast reply!
Here's the log file.  The fun starts at line 1367:
https://gist.github.com/calebgerlach/7744c7f8e01184502c82
And for additional fun, the same command run with -X for more details:
https://gist.github.com/calebgerlach/1d0a29a7a5bc84156fa9


Added support for webdriverManagerUpdate property in config.

Issue: https://github.com/blackbaud/skyux2/issues/2124
Related PR: https://github.com/blackbaud/skyux-config/pull/9

Codecov Report

Merging #488 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master   #488   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          54     54
  Lines        1653   1658    +5
  Branches      245    246    +1
=====================================
+ Hits         1653   1658    +5

Flag
Coverage Δ

#builder
100% <100%> (ø)
:arrow_up:

#runtime
100% <ø> (ø)
:arrow_up:

#srcapp
100% <ø> (ø)
:arrow_up:

Impacted Files
Coverage Δ

cli/e2e.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f9d7447...1faf213. Read the comment docs.


Migrate wasm-themis to TypeScript

So my PR for TS is finally here. This PR only changes syntax and should not change semantics. This is not possible in every case, but in all cases that matter.
The module works in node, older browsers and also works using ES6 and TypeScript. Here is an example for node:
mkdir test && cd test
npm init -y
npm install file://./wasm-themis-0.14.0.tgz
echo "const themis = require('wasm-themis'); \
themis.initialize().then(() => { \
    const cell = themis.SecureCellSeal.withPassphrase('pass'); \
    console.log(cell.encrypt(new Uint8Array([1]))); \
})" > example.js
node example.js

Example for web like a react app:
// @ts-ignore
import themisWasm from "wasm-themis/dist/libthemis.wasm";
import { initialize, SecureCellSeal } from "wasm-themis"; // webpack takes care of making the wasm file available

await initialize(themisWasm);
const cell = SecureCellSeal.withPassphrase(pw);

Here are links to the diffs for easier reviewing:

Syntax changes from plain JS to TS

You can simple review the commit referenced above and then only review the changes to the package.json and build files.
Checklist

[x] Change is covered by automated tests
[x] Benchmark results are attached (if applicable)
[x] The [coding guidelines] are followed
[ ] Public API has proper documentation
[ ] Example projects and code samples are up-to-date (in case of API changes)
[ ] Changelog is updated (in case of notable or breaking changes)

I'm not sure where to change example or where examples exist. The api only changed ìnitialisedto ìnitialize()

I think the RustThemis failure is not introduced in this PR. For some reason Node 10 fails because of a timeout when initializing wasm. Not sure why this happens...

Next steps:

Remove tests which check for types errors
Remove all exceptions which are thrown because of wrong types. Typescript handles this now.
Remove legacy arguments.length ==  handling
Remove coerceBytes

Wow, that's a lot 🔥

Wow, that's a lot 🔥

Yeah I tried to do minimal changes. But a rewrite is a rewrite :D
The other changes can follow in other prs. They are optional and just code quality improvements.

Also, a comment from the operational point of view for @shadinua: WasmThemis publishing should not really change much with all of this. You can still just run make wasmthemis to build a wasm-themis.tgz to be uploaded to npm and that's it. The build process gets slower though, as now it needs to download more stuff from the Internet, transpile TypeScript into JavaScript, etc.

FYI, @maxammann, the fix for Rust build has been merged into master, so you can pull the updated version and merge it into your branch to turn the build green. Just a merge commit with git checkout typescript && git merge master, not rebases or anything like that (the PR branch is going to get squashed anyway).

@ilammy any update on this one? :)

@maxamman, I'm sorry, it seems that high-context culture has some effects on me and I kinda mishandled this.
It looks like we ended up playing this silly game where everybody expects other people to do something, but they never tell that explicitly and the other party does not read the air. And so weeks pass without anyone doing anything while everybody is under impression something is being done and it just takes time. From my point of view, open-source contributors are volunteers and all, they have other stuff to keep them busy. From your point of view, I think, maintainers might look the same.
I'm biased for merging this to make future work easier. However, this will block the 0.17.0 release until the backwards compatibility issues outlined in https://github.com/cossacklabs/themis/pull/792#discussion_r602680678 are resolved (one way or another: either we avoid them, or we assert them). I'm not aware of time constraints for this release, so I guess I'd go for making it when it's done rather than postponing TypeScript rework for some later release.
@vixentael, what's your take on this?
Again, @maxammann, I'm sorry for not setting my expectations straight :pray: I was under impression that you were looking into those issues, it just takes time.

I'm sorry, it seems that high-context culture has some effects on me and I kinda mishandled this.

Absolutely no problem, no mishandling happened in my opinion :)
Actually, I did not see your last comment in our discussion. As far as I can see I have two open things:

Continue to support initialized promise
Drop ES5 support because all wasm supporting browsers also support ES6 and therefore also revert the changes about extending ArrayBuffer

Thank you for your patience @maxammann!
Scenario 1

Continue to support initialized promise

Would be nice if we can!

Drop ES5 support

I'm ok with this., it's old :)
If we can support old initialized promise OR write deprecation notice on that one, then I think we can merge TS support to master and release with next Themis release.
Scenario 2
If we can't support old initialized promise, then I suggest merging these changes to a separate branch master/typescript, and aim at releasing 0.14.0 with breaking changes (add initialize(); drop ES5) :)
I'd love to support backwards compatibility, but I understand that WASM Themis is typically used in desktop and web apps, which move fast. Soo... sorry devs? We will describe breaking changes as detailed as possible.

@maxammann do you think it's possible to support initialized promise or to write some deprecation/breaking change notice in code to let devs know that they should use initialize now?

Alrighty. @maxammann, I've retargeted your PR onto a new branch – wasm-typescript – and merged it there. Please target your future TypeScript PRs for that branch. Once TypeScript support is stabilized and ready for release, the wasm-typescript branch will be merged into master.
This way if Themis really needs a release, we can provide it without potentially introducing a breaking change. Hopefully, we won't need this and TypeScript will be in there in Themis 0.14.

Thanks! Right now I don't have time to continue but soon I will :)
Just ping me when there are urgent changes for wasm-themis.


Moving Time Axis Outside the Graph

I am having troubles either trying to get the time axis outside of the graph, or to make x-axis use times that display on the hour. Ultimately, I need the time axis to not overlap the graph for readability. Do you have any suggestions, or is this already possible and I missed it somehow?

Try adding the following to your css:
/* "title" is the class assigned to the x-axis labels */
.title {
bottom:       -19px !important;
}


update : update README, added Eutophia sample project

sound-helper Overview
sound-helper is a sample application using the euphony Acoustic Data Telecommunication Library.
This application is designed to verify patient's chronic disease information and identity in urgent situations.
If you use this application, you can use this function

Function to send information when a mobile phone is detected shaking
Function to receive information by pressing a button
Function to store information in advance

Co-Authored-By: eunzinn<EMAIL_ADDRESS>Co-Authored-By: JK Park<EMAIL_ADDRESS>Co-Authored-By: kmsaidev<EMAIL_ADDRESS>

Thanks for the great reviews and comments!
We'll try to improve that suggested in comments.


Got same problem that model only return lots of  '\n'

I got the same problem when use the quick start script to run an inference task.
Just the same as this issue: https://github.com/ise-uiuc/magicoder/issues/22
what should i do to solve this problem?

here is my code:
`from transformers import pipeline
import torch
MAGICODER_PROMPT = """You are an exceptionally intelligent coding assistant that consistently delivers accurate and reliable responses to user instructions.
@@ Instruction
{instruction}
@@ Response
"""
instruction = "Implement a high-level API for a TODO list application. The API takes as input an operation request and updates the TODO list in place. If the request is invalid, raise an exception."
model_path='/data/MagiCoder'
prompt = MAGICODER_PROMPT.format(instruction=instruction)
generator = pipeline(
model=model_path,
task="text-generation",
torch_dtype=torch.bfloat16,
device_map="auto",
)
result = generator(prompt, max_length=2048, num_return_sequences=1, temperature=0.0)
print(result[0]["generated_text"])`

Thanks for reporting this. Did you also try to update the package as described in the issue you referred to, and could that help?

Thanks for reporting this. Did you also try to update the package as described in the issue you referred to, and could that help?

do u have recomended version of packages that magicoder need?

Yes they are listed in pyproject.toml.


LLVM tests and improvements

Adds some tests and TypeScript-related improvements to the LLVM target compiler.

Merging since all tests pass and no comments.


feat: implemented support for basic ad-group-permissions

Types of changes

[ ] Bug fix
[x] New feature
[ ] Removed feature
[ ] Code style update (formatting etc.)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Content/Data

Does this PR introduce a breaking change?

[ ] Yes (I have stepped the version number accordingly)
[x] No

Checklist:

[x] My code follows the code style of this project.
[x] I have updated the documentation accordingly (if applicable).
[ ] I have added/updated tests to cover my changes (if applicable).

Jira https://jira.sundsvall.se/browse/MOD-28


Modified TokenGroupIdentifier to detect spam, added SpamTokenService to autohide spam tokens

Closes #6445
Tests
Stand alone

Delete the app
Start the app
Tap "I already have a wallet"
Tap "Track Wallet Address"
Type in "hweeboon.eth" in the Ethereum Address field
Tap "Watch Wallet"
Wait 2 minutes
Tap ellipses in upper right corner
Tap "Add / Hide Tokens"
Scroll down to Hidden Tokens
Expects there to be up to 8 tokens

Switch wallets

Delete the app
Start the app
Tap "I already have a wallet"
Tap "Track Wallet Address"
Type in "hweeboon.eth" in the Ethereum Address field
Tap "Watch Wallet"
Tap Blockie in upper left corner
Tap + in upper right corner
Tap "Create Wallet"
Wait 2 minutes
Tap Blockie in upper left corner
Switch to "hweeboon.eth" wallet
Tap ellipses in upper right corner
Tap "Add / Hide Tokens"
Scroll down to Hidden Tokens
Expects there to be up to 8 tokens

Code
TokenGroupIdentifier
This is moved up from ActiveWalletCoordinator to AppCoordinator so that there is only one copy of it in the app instead of one copy for each wallet.
Functions to detect spam are added.

Looks good. Assume you tested.

I did not do the test where two wallets have the same spam tokens. Only the two tests mentions in the introduction.

[ ]  Follow up to see if this needs cleaning up https://github.com/AlphaWallet/alpha-wallet-ios/blob/52081f6e986dbd33c5c76d66cc42907585d95ffb/modules/AlphaWalletFoundation/AlphaWalletFoundation/Tokens/Lists/SpamTokens.swift#L5

This is not used and should be removed.

[ ]   Follow up to see if this needs cleaning up https://github.com/AlphaWallet/alpha-wallet-ios/blob/52081f6e986dbd33c5c76d66cc42907585d95ffb/modules/AlphaWalletFoundation/AlphaWalletFoundation/Tokens/Lists/SpamTokens.swift#L5

~This is not used and should be removed.~ This is used in TickerIdsFetcherImpl and looks like we might have duplicate functionality. I can't find which coordinator this is created under...

In TickerIdsFetcherImpl. Think it's only meant to be temporarily, can probably remove it and add the contracts into tokens.json if you haven't and if they are missing.

@hboon updated

@oa-s in case you are still looking at it.


[TS]Getting duplicate error message in editor without adding linter extension for typescript.

From @v-pavanp on March 22, 2016 23:56
OS Version: Windows10
VSCode version: 0.10.12-alpha
Steps:

launch app and open a folder which contain .TS file.
Verify any error message is showing up.

Expected: If there is not extensions installed for TS lint then error should not be highlighted in editor.
Actual:
While verifying bug #4107 with "Express Node.js typescript" project. I observed that there are two error messages showing up in my .ts file and when I closely watched, I found there is no extension installed for TS lint. I also removed extension for ESlint as well and restarted app.
I observer that still it is showing two errors messages in the editor and when I hover over on it, it is displaying :

[ts] cannot find module 'http'
[ts] Cannot find name process.

But when I clicked on error icon from the status bar then could see in the pop-up (in command palette) it is showing up duplicate error message like below.

Questions:

When there is no linter installed for TS or ES then why it is displaying red mark in the code.
Is there any reference left for the TSLint in the system after removing extension which is causing this issue.

I also verified in the extension directory and didn't find any reference of TS or ES lint extension.

Copied from original issue: Microsoft/vscode#4591

From @egamma on March 23, 2016 7:23
The linters generate markers and these markers survive when a linter is uninstalled.
A linter should remove the diagnostics it generated in the extensions deactivate call.
Not critical for March.

Closing. The language client is now disposed its diagnostics collection when it is shutdown. The extension hover has to shutdown the client in deactivate.


Change language on local installation

Hi guys,
I'm currently translating parts of your awesome work into german. To have some visual feedback on my translations I installed FreeCodeCamp on my local machine and it runs perfectly. But when I'm following 8.3 of the Translations Guide ( https://github.com/FreeCodeCamp/FreeCodeCamp/wiki/Translations-Guide ) I hit a dead end.
Point 8.3 says:

Follow the changes shown in this commit but instead of descriptionEs and nameEs use the keys of your language (e.g descriptonFr and nameFr)

The thing is that I can't find the files mentioned in the commit ( https://github.com/FreeCodeCamp/FreeCodeCamp/commit/d36e33f3938ddd079931a5fb2bc5dc6db37667e5 ). Even when I search for the changes, I'm not able to locate the files I have to change in order to switch the language to german.
Am I simply too blind, or did something change? How can I change the language?
Thanks a lot :-)

The files seem to have moved over the time the code has changed:
Currently you can find them at:
https://github.com/FreeCodeCamp/FreeCodeCamp/blob/staging/server/boot/challenge.js
https://github.com/FreeCodeCamp/FreeCodeCamp/blob/staging/server/views/map/show.jade
/cc @vtamara Can you confirm, these are the files that @5k9m needs?

Going by the issue title my impression is that the question may actually be about changing the display language on FCC for viewing/testing on the local copy (though I don't know how to answer that).

I updated, @5k9m please check https://github.com/pasosdeJesus/FreeCodeCamp/commit/ad584ebec449734267e6f7dc5234eeae1b240ec3


Polygon Foundry Deployment Issue

There are problems with deploying ANY contracts through foundry's forge create as well as forge script both don't work under any RPC i.e. alchemy. I even tested with multiple gas multipliers with no luck. Will need to open up an issue with foundry. Current work around will use a hardhat project to deploy. Mainnet  should be working fine as I have tested on Goerli.
[] Opening up foundry issue for polygon ProviderError(JsonRpcError(JsonRpcError { code: -32000, message: "transaction underpriced", data: None }))

No longer an issue.


Accomodate image observations in ULTRA

Is your feature request related to a problem? Please describe.
Image observations are offered in SMARTS but not currently in ULTRA
Describe the solution you'd like
An option to use image features. Will likely require framestacking, but we can downsample and use greyscale to lower the dimension of the inputs. Would also require updating the baselines to accomodate this, there is already some CNN code for TD3 and BDQN.
Describe alternatives you've considered
N/A
Additional context
We can either use images in addition to low-dim states (images replace social vehicles), or images alone. The images observations can be used as a sanity check for social vehicle interaction, but will require more compute.

See https://github.com/huawei-noah/SMARTS/tree/ultra_baseline_image_observations for an initial implementation. DQN, BDQN, and TD3 all can support RGB image observations (turned to stacked grayscale images during preprocessing) using their CNNs.
It is far from ready to be merged (if that is what we intend to do), but it allows for training with images and low dimensional states as input.

Looks pretty good! I'll run some experiments over the weekend and see if this helps the collision problem.


6.10.1 isn't loading on iPad

Unlike the previous Admonition version this fails to load on the current iPad version (1.0.5).

Hmm, it loads fine on my iPhone.
what iOS version are you on?

12.5.5 I haven't changed the iOS version but updated the plug-in. That's the only thing changed. Now I get the loading error.

Have you updated the Obsidian app lately?

Nope. I'm not updating Obsidian on the desktop anymore. The mobile app is far enough behind as it is already. The only change I made was updating Admonition. Had a similar issue with Dataview when that got updated. It was loading though but most of the stuff isn't working anymore on iPad. Might be related, might not be.

Okay, this is likely an app versioning issue then. I use some new features from Obsidian v0.13.14+ (desktop... not sure how that maps to the mobile version). I updated my versioning file to reflect this, but you'll likely have to downgrade your Admonitions install.

Found the last version that still works on iOS: 6.9.5
Maybe that helps diagnosing.

I believe that this issue should be resolved with the latest Obsidian Mobile public release. Can you confirm?

Just tested it. Nope. Need to roll back when I get back to the desktop. For now my files look like a mess again.

Certainly weird. For me it stopped after 6.9.5.
Here's my data file. But after the last update problems (update > didn't work > delete > unzip 6.9.5 > copy back ) I left everything on default as I've always deleted the plug-in folder each time anyway.
data.json.zip

Does this still occur?

I just installed it again.
Install went fine but tapping on Enable yielded the same error yet again. 🤷♂

@frankjonen This may seem like a redundant ask, but I am checking if this is still an issue. There has been quite a few major Obsidian updates since then on iPadOS that have improved the rendering of code blocks, and our ability to diagnose those issues have been improved as a result.

@sigrunixia Thanks for checking. I've moved on from Admonitions to Obsidian's native ones with some own CSS extensions (custom terms).


Audio language: does not accept :en symbol

Context
http://googlecloudplatform.github.io/google-cloud-ruby/#/docs/google-cloud-speech/master/google/cloud/speech/audio
I'm trying to use the Speech API Japanese recognition. I'm not sure what the symbol, but I'm guessing it's :jp. I tried the snippet with english (I understand it's set by default),  but it fails with an invalid argument for string field.
Snippet
require "google/cloud/speech"

speech = Google::Cloud::Speech.new

audio = speech.audio "path/to/audio.raw",
                     encoding: :raw, sample_rate: 16000,
                     language: :en

Error
from /usr/local/lib/ruby/gems/2.3.0/gems/google-cloud-speech-0.21.0/lib/google/cloud/speech/project.rb:512:in `initialize': Invalid argument for string field. (TypeError)
from /usr/local/lib/ruby/gems/2.3.0/gems/google-cloud-speech-0.21.0/lib/google/cloud/speech/project.rb:512:in `new'
from /usr/local/lib/ruby/gems/2.3.0/gems/google-cloud-speech-0.21.0/lib/google/cloud/speech/project.rb:512:in `audio_config'
from /usr/local/lib/ruby/gems/2.3.0/gems/google-cloud-speech-0.21.0/lib/google/cloud/speech/project.rb:392:in `recognize_job'
from /usr/local/lib/ruby/gems/2.3.0/gems/google-cloud-speech-0.21.0/lib/google/cloud/speech/audio.rb:239:in `recognize_job'

Ruby Version
ruby 2.3.1p112 (2016-04-26 revision 54768) [x86_64-darwin16]
Gem Versions
  * addressable (2.5.0)
  * bundler (1.13.6)
  * faraday (0.10.0)
  * google-cloud-core (0.21.0)
  * google-cloud-speech (0.21.0)
  * google-cloud-translate (0.22.1)
  * google-gax (0.6.0)
  * google-protobuf (3.0.2)
  * googleapis-common-protos (1.3.4)
  * googleauth (0.5.1)
  * grpc (1.0.1)
  * jwt (1.5.6)
  * little-plugger (1.1.4)
  * logging (2.1.0)
  * memoist (0.15.0)
  * multi_json (1.12.1)
  * multipart-post (2.0.0)
  * os (0.9.6)
  * public_suffix (2.0.4)
  * rly (0.2.3)
  * signet (0.7.3)
  * streamio-ffmpeg (3.0.1)

Thanks for the report. Will get this fixed ASAP.

Thanks! :+1:

This is fixed in google-cloud-speech 0.21.1. PTAL.

@blowmage It now accepts :en, but It doesn't complain if I provide an incorrect language code such as ":ddddd". I think that's too flexible without an error message to provide feedback.
Thanks for your help!

We think its best to now check language codes in the ruby client. Language codes are checked during the API calls, and history has shown that supported language codes will change over time. If the ruby client adds a check for the code then we will eventually be in the position where the ruby client errors on a code that the API supports, or vice-versa.

I understand. It might be helpful how to have a note about this in the client library documentation. I get confused for languages such as Chinese which has four language codes. How should I write the symbol for each? Would this be a correct symbol: :cmn_Hant_TW?

According to Language Support it would be "cmn-Hant-TW".

Ruby doesn't make it easy to create symbols with dashes in them, so if you want to express that as a symbol you can either use "cmn-Hant-TW".to_sym or :"cmn-Hant-TW".

Thanks! That was my question. That's where my confusion came from. Seeing the documentation have :en instead of :"en-US", when we have language codes with en-*. I guess it's assumed when someone writes "en" they mean "en-US".


Add a printer function which is dynamic in output.

A simple function that will print inserted data to stdout in such a way that single line on the output prompt is refreshed at every call. This prevents the output prompt from being filled with clutter from previous iterations.

I really like the idea of a live_monitoring module. This printer function is also a great idea, but currently I think it's a bit too easy to screw up; any additional printing will interfere badly with it.
MWE of screwing it up:
import numpy as np
from qcodes import new_experiment
from qcodes.dataset.data_set import new_data_set, ParamSpec
from qcodes.dataset.live_monitor import printer
from time import sleep

specs=[ParamSpec("x", "numeric", unit='Hz'), ParamSpec("y", "numeric", unit='V')]
new_experiment('test', 'no_sample')
data_set = new_data_set("test", specs=specs)
sub_id = data_set.subscribe(printer(["x", "y"]), state=[])
for x in np.linspace(100, 200, 15):
    y = np.random.randn()
    data_set.add_result({"x": x, "y": y})
    sleep(0.2)
    print("I am here to wreck havoc")

Lol, I get your point. But I think we should not be too concerned with all the ways a user can screw this up. Else we will end up being completely paralyzed. Also, I think this should be seen as a relatively quick and dirty solution to a quite urgent problem. Let's get this quick solution out first and worry about a more durable solution later.
The reason this is an urgent problem is that users have been used to saving to a text file rather than a database. The fortunate side effect of text files is that live monitoring is less difficult: simply open the text file with your favorite editor and keep refreshing! But this is suddenly not possible anymore. The effect of that is that users demand to save to text files in addition to the sql lite database. This is not what we want!


Roll engine 9b905d3f03f2..67675173b332 (7 commits)

https://github.com/flutter/engine/compare/9b905d3f03f2...67675173b332
git log 9b905d3f03f2..67675173b332 --first-parent --oneline
2020-05-08<EMAIL_ADDRESS>Roll src/third_party/skia b55372444d1b..ac09f7cd7a28 (2 commits) (flutter/engine#18229)
2020-05-08<EMAIL_ADDRESS>Roll src/fuchsia/sdk/mac from 4MCVP... to T5tT0... (flutter/engine#18228)
2020-05-08<EMAIL_ADDRESS>Roll src/third_party/skia 8f6c3ed7c7be..b55372444d1b (4 commits) (flutter/engine#18224)
2020-05-08<EMAIL_ADDRESS>Make robolectric tests run against SDK 29 by default (flutter/engine#17996)
2020-05-08<EMAIL_ADDRESS>Roll src/third_party/skia a14084ba1b41..8f6c3ed7c7be (1 commits) (flutter/engine#18223)
2020-05-08<EMAIL_ADDRESS>Roll src/fuchsia/sdk/linux from MhpFP... to c1q_S... (flutter/engine#18222)
2020-05-08<EMAIL_ADDRESS>Add FlMessageCodec, FlBinaryCodec, FlStringCodec (flutter/engine#18186)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

Commit queue failed; closing this roll.


Convert all Toast alerts to Modals

Resolve #1037
This PR custom success, error modals and change most of Toast alerts to modals
Screenshot

This is a simple function that requires just a toggle switch on or off.
Also, the recent mockups doesn't contain any modal to confirm transaction notification success.
There is a ton of white space in this screenshot, it doesn't look like the initial pixels in which modals are designed with for GoDCR Version 2 was used here.


Required proxy fields

Closes #104
Form saves result without proxy data both apiUmbrella and emqtt type

Create validation function
Checking for validation on before-insert autoform hook
Delete useless optional field in schema (on default optional: false)

While this solution is clever and elegant, there may be a solution that is more aligned with simple schema. In that approach, the apiUmbrella or emqtt sub-fields would look at the proxyType field and perform validation based on the proxy type selected. This will get much easier in SimpleSchema v2, so lets keep this work relatively close to how Simple Schema is designed to work.

Basically, what we are trying to do is define validation in the schema.

@brylie Of course it was my first decision to make validation with simple schema. But we have three independent schemas. apiUmbrella and emqtt schemas don't know anything about proxy schema. We can't use this solution because we don't know in which moment we must make a field required.

Even with multiple sub-schemas, the proxyType should be available at the time of validation. I.e. when a document is validated, Simple Schema will be using the combined schema -- despite us breaking it into parts for extensibility.

I am willing to merge this solution, if there is no way we can validate closer to the schema. So, lets leave this branch/PR open.

Try a quick test to validate or refute the idea, e.g.:
// Inside of custom validation function for emqtt URL field
console.log(this.field('proxyType'));

@brylie Nothing useful
{isSet: false, value: undefined, operator: undefined}

Ah, sorry. It should have been:
// Inside of custom validation function for emqtt URL field
console.log(this.field('proxyType')).value;

Did you set a value for the Proxy Type field, via the form?
Sure

OK, I am thinking that our schemas don't need to be so complicated for right now. I.e. we are defining them in separate files for modularity, but they are hard coded inside of index.js anyway (in terms of imports and listed within _.assign(). Lets move all of the schemas back together inside of index.js, that way we can use the custom validation function.


Add bmp280

check Code!

[ ] Unnecessary wire.begin isn't it?

[ ] Line 119, "/ HTTP/1.1\r\n" change to "/ "+"HTTP/1.1\r\n"


Layer alignment

framework for scaling and translating multiple yt layers.
For #16, but will be limited use before a graphical plugin that can access to the existing layer context.

actually, just realized with a slight change to the schema I can have normalization across layers now! have a local change that loads and properly scales, translates selections of different regions at different resolutions, but will need to update tests...


KeyboardAvoidingView misplaces absolutely positioned elements

Description
Having an element with position: absolute in a KeyboardAvoidingView with behavior="padding and keyboardVerticalOffset greater than 0, moves the element permanently (even after closing the keyboard).
React Native version:
System:
    OS: macOS Mojave 10.14.6
    CPU: (8) x64 Intel(R) Core(TM) i7-4850HQ CPU @ 2.30GHz
    Memory: 727.96 MB / 16.00 GB
    Shell: 5.3 - /bin/zsh
  Binaries:
    Node: 12.16.1 - ~/.nvm/versions/node/v12.16.1/bin/node
    Yarn: 1.21.1 - ~/.yarn/bin/yarn
    npm: 6.13.4 - ~/.nvm/versions/node/v12.16.1/bin/npm
    Watchman: 4.7.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.9.1 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 13.1, DriverKit 19.0, macOS 10.15, tvOS 13.0, watchOS 6.0
    Android SDK:
      API Levels: 23, 25, 26, 27, 28
      Build Tools: 23.0.1, 25.0.2, 26.0.1, 27.0.3, 28.0.3
      System Images: a...google_apis | Google APIs Intel x86 Atom Sys...
      Android NDK: 17.0.4754217
  IDEs:
    Android Studio: 3.4 AI-183.6<IP_ADDRESS>22156
    Xcode: 11.1/11A1027 - /usr/bin/xcodebuild
  Languages:
    Java: 1.8.0_102 - /usr/bin/javac
    Python: 2.7.17 - /usr/local/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.11.0 => 16.11.0
    react-native: 0.62.2 => 0.62.2
  npmGlobalPackages:
    *react-native*: Not Found

Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.

Run app
Tap on text input
Close text input

Expected Results
After closing the keyboard the element should be at its original position.
Snack, code example, screenshot, or link to a repository:
link to snack:
https://snack.expo.io/@vmark/keyboardavoiding-absolute-positioning-bug
link to repo:
https://github.com/vujevits/KeyboardAvoidingAbsoluteExample
Screenshots

@vujevits Did you find a solution?

@randytorres I'm afraid I had to get rid of the absolute positioning.

@vujevits remove {flex: 1} from your KeyboardAvoidingView so that it take only as much space as it's children. that should fix it right up.

why have you added keyboardVerticalOffset ?
this works as expected.
 <KeyboardAvoidingView
      behavior="padding"
      style={styles.container}
      contentContainerStyle={styles.container}
      keyboardVerticalOffset={0}
    >
      <SafeAreaView style={styles.container}>
        <View style={styles.container}>
          <TextInput style={styles.paragraph} placeholder="Click here" />
          <View style={styles.button} /></View>
      </SafeAreaView>
    </KeyboardAvoidingView>

if you are using positioning as behavior your KeyboardAvoidingView only as much space as it actually needs, so you should not have {flex: 1}

@a-eid not sure what are you suggesting, the bug report is about using specific settings, in which case the absolutely positioned element is permanently moved to another location, even after closing the keyboard.

Hello guys, I solved this by taking the 'event' and checking if the keyboard was 'visible' or 'hidden', put it in a state and did the logic.
const [keyboard, setKeyboard] = useState(Boolean);

  useEffect(() => {
    Keyboard.addListener('keyboardDidShow', _keyboardDidShow);
    Keyboard.addListener('keyboardDidHide', _keyboardDidHide);

    return () => {
      Keyboard.removeListener('keyboardDidShow', _keyboardDidShow);
      Keyboard.addListener('keyboardDidHide', _keyboardDidHide);
    };
  }, []);

  const _keyboardDidShow = () => {
    setKeyboard(true);
  };

  const _keyboardDidHide = () => {
    setKeyboard(false);
  };

and...
{!keyboard && (
    <View style={{ position: 'absolute', bottom: 0, height: 60 }} >
      <Text style={{ alignSelf: 'center' }} >Criar uma conta</Text>
    </View>
  )}

To be honest, I didn't like the solution 100% because of the size of adding code for something so 'simple', but that's what I did.

Hello guys, I solved this by taking the 'event' and checking if the keyboard was 'visible' or 'hidden', put it in a state and did the logic.
const [keyboard, setKeyboard] = useState(Boolean);

  useEffect(() => {
    Keyboard.addListener('keyboardDidShow', _keyboardDidShow);
    Keyboard.addListener('keyboardDidHide', _keyboardDidHide);

    return () => {
      Keyboard.removeListener('keyboardDidShow', _keyboardDidShow);
      Keyboard.addListener('keyboardDidHide', _keyboardDidHide);
    };
  }, []);

  const _keyboardDidShow = () => {
    setKeyboard(true);
  };

  const _keyboardDidHide = () => {
    setKeyboard(false);
  };

and...
{!keyboard && (
    <View style={{ position: 'absolute', bottom: 0, height: 60 }} >
      <Text style={{ alignSelf: 'center' }} >Criar uma conta</Text>
    </View>
  )}

To be honest, I didn't like the solution 100% because of the size of adding code for something so 'simple', but that's what I did.

 I can't believe it's still there!

This is still an issue for me as well. Has there been any update on this? I need elements to be absolutely positioned on my screen but I also need to use the KeyboardAvoidingView.

any updates?

any updates ?

I'm suffering from this as well. I feel like I spend about 50% of my RN dev time dealing with the keyboard behavior (covering the wrong things, not hiding when you click on certain things, etc).

Hey ! I had the same problem, I was  using keyboardAvoidingView with absolute position and putting it at the bottom of the screen.
This  code was not working :
<KeyboardAvoidingView        style={{             position: 'absolute',         top: WINDOWHEIGHT - 100,  ...
But this code is working :
      <KeyboardAvoidingView        style={{             position: 'absolute',         left: 0, right: 0, bottom: 0, ...

experiencing the same issue

Same problem here
Make sure to add a 👍 reaction to the issue so the RN team can filter and prioritize this

FIXED IT!!! WOOOO!
This will automatically move the whole screen up
```
<KeyboardAvoidingView
keyboardVerticalOffset={headerHeight}
style={{position: 'absolute', width: '100%', bottom: 0, flex: 1}}
behavior={'position'}
enabled>
CONTENT

i found a solution for myself. Since I have many inputs, I use ScrollView + KeyboardAvoidingView, but outside of these components, I have a button that I want to hide when the keyboard is open
none of the options above solved my problem perfectly, but everything turned out to be much simpler, I just added on top of the flex button: 1
<ScrollView>
        <KeyboardAvoidingView
          style={[{marginBottom: Insets.bottom}, styles.ph27]}
          behavior={Platform.OS === 'ios' ? 'padding' : 'height'}>
          // My inputs
        </KeyboardAvoidingView>
</ScrollView>

<View style={[flex: 1, styles]}>
        <ButtonUI
          style={[{marginBottom: Insets.bottom}, styles.mb20]}
          text={t(LangText.buttonsReady)}
          onPress={() => {}}
          rightIcon={<CheckIcon color={ColorsUI.white} />}
        />
</View>

!!!!!!!! READ THIS !!!!!!!!
when you don't have many inputs this solution won't help, but in those cases you may not need to use KeyboardView at all as the keyboard won't overlap your inputs

I found a solution using flex layout for this issue (using tailwind for react native)

 (
                    <>

                </>
              )}
            />
          </View>
          <View className="mt-6">
            <Controller
              control={control}
              name="lastname"
              render={({ field: { value, onChange } }) => (
                <>
                  <SomeTextInput />
                </>
              )}
            />
          </View>
        </View>
        <View className=" mt-6 w-full">
          <Button >
            Confirm
          </Button>
        </View>
      </View>

Any updates on this issue?

props tried
keyboardVerticalOffset:
Platform.OS === 'ios' ? 90 :75,
behavior: Platform.OS === 'ios' ? 'padding' : 'height',


[REQUEST] Remove edge during installation

Hello, is it also possible to add an option to directly uninstall edge instead of make it removable?
I wont use it if i ever need to download something i can use curl directly on cmd.

There are scripts that uninstall Edge (or at least claim to do so), but they are typically too complicated for my liking. If you want to use such scripts, you should probably put them in the Scripts to run in the system context, before user accounts are created section.
I was very content with the MakeEdgeUninstallable.ps1 script, but that approach does no longer work in 24H2.

@cschneegans what about removing the edge folders at <settings pass="windowsPE">
				<RunSynchronousCommand wcm:action="add">
					<Order>21</Order>
					<Path>cmd.exe /c "rmdir /s /q "C:\Program Files (x86)\Microsoft\Edge" & rmdir /s /q "C:\Program Files (x86)\Microsoft\EdgeUpdate" & timeout /t 25"</Path>
				</RunSynchronousCommand>
```I'm not sure whats wrong with the syntax but the installation is complaining about it

C:\Program Files (x86) does not yet exist when RunSynchronousCommand elements are processed. Windows Setup might even use a drive letter other than C: for the target volume during the windowsPE phase.
If you really want to meddle with files and folders on the target volume during the windowsPE phase, check how the DisableDefender.vbs script is implemented.

I did some tests and i have been able to delete both folders during the windowsPE phase, trying to delete them on the moment the "specialize" scripts are executed i get a permission error.
I see how you are calling the defender scripts, i think its a problem on the syntax of the command, do you see something wrong on it?

The text value (i.e. after unescaping the XML markup) of the <Path> element must not exceed 256 characters in length. Your second command is 261 characters long.

@cschneegans thanks i didn't know this.
Removing edge during the windowsPE phase worked, when the system started i don't have edge anywhere, but theres a catch i cant delete the folders while the files are being installed or it throw an error, i need to wait it finish everything until that point it restarts on 10seconds.
Do you have any idea how to stop it from rebooting while still using the unattended answer?
I have tried this:
https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-setup-automation-overview?view=windows-11#setupconfigini
but it is ignoring the option and auto rebooting.

Do you have any idea how to stop it from auto rebooting while still using the unattended answer?

As far as I know, the new “ConX” setup.exe in 24H2 does not accept command line options at all. You would need to switch to legacy setup mode first. I do not know how that switch can be automated. See my comment on how to do it manually.

@cschneegans thanks ill try it.
				<RunSynchronousCommand wcm:action="add">
					<Order>21</Order>
					<Path>cmd.exe /c "start /MIN cscript.exe //E:removeedge E:\removeedge.vbs"</Path>
				</RunSynchronousCommand>

I have put it into the same root folder of the setup.exe but when the auto installation start it doesn't get called.
I test manually calling it opening shift+10 and it does work, just the auto start not.

When you already rebuild your .iso file, I think it would be far easier to remove the C:\Program Files (x86)\Microsoft\Edge folder in the .wim image.

There are scripts that uninstall Edge (or at least claim to do so), but they are typically too complicated for my liking. If you want to use such scripts, you should probably put them in the Scripts to run in the system context, before user accounts are created section.
I was very content with the MakeEdgeUninstallable.ps1 script, but that approach does no longer work in 24H2.

The MakeEdgeUninstallable.ps1 script still works in 24H2.
You must install all Windows updates and run the script as TrustedInstaller.
I recently tested it on a VM.

To my surprise, Edge on 24H2 can be uninstalled once again via Settings > Apps, no System or TrustedInstaller permissions required, only the modification to IntegratedServicesRegionPolicySet.json during Windows Setup. This is an excerpt from C:\Windows\SystemTemp\msedge_installer.log after I had Edge uninstalled:
[8904:8900:1211/162356.174:156843:VERBOSE1:install_util.cc(284)] Existing version found: 131.0.2903.86
[8904:8900:1211/162356.214:156875:VERBOSE1:edge_install_util.cc(216)] Parent process: C:\Windows\System32\sihost.exe
[8904:8900:1211/162356.214:156875:VERBOSE1:edge_install_util.cc(240)] Caller is not under windir environment variable.
[8904:8900:1211/162356.214:156875:VERBOSE1:edge_install_util.cc(256)] Uninstall allowed: Windows caller
[8904:8900:1211/162356.214:156875:VERBOSE1:shell_util.cc(4117)] Uninstall enabled by regional policy
[8904:8900:1211/162356.214:156875:VERBOSE1:edge_install_util.cc(280)] Uninstall allowed: Product is not sticky

I am not sure what triggered this change. Note that the very same process C:\Windows\System32\sihost.exe was excluded from uninstalling Edge when I commented on https://github.com/cschneegans/unattend-generator/issues/81 a few weeks back.

@cschneegans Is the ISO from the MediaCreationTool (build 26100.2033) right?

Is the ISO from the MediaCreationTool (build 26100.2033) right?

It's Win11_24H2_English_x64.iso, downloaded directly, not through the Media Creation Tool.


Project Starters

Here is the two awesome project starter:
MVP
MVVM
Would you please add this two tool.

Thanks, the Android Architecture Blueprints are in my opinion better starters:
https://github.com/JStumpp/awesome-android/blob/master/readme.md#code-examples


Compile with ESP-IDF

Can you please guide me to compile this project with ESP-IDF without Arduino component? I am using ESP-IDF v4.4.1.

Hello. I would really like to help you but I've never used ESP-IDF. Please, share your experience once you succeed.

If you have any specific question though, I woul like to help if I can.

Hello, Thank you for quick response.
Your code is elegant. But somehow IDF compiler does not understand it and throws a lot of compiler errors like fall through if-statements, format-overflow, return-type. I tried to fix all, and compiled using Arduino as a ESP-IDF component. It compiled ok, but after flashing to device I am getting continuous crashes. I guess its Arduino component issue. Also this Arduino component is bulky. For the time being I will pause this exploration and come back when I get some other esp component library to compile your code.

I have replaced Arduino Strings with std::Strings and delays with esp_task_wdt_reset and vTaskDelay (see the attachment). Haven't tested it thoroughly, though.
I believe that with some extra effort you should be able to port the code to ESP IDF without including Arduino libraries now
Esp32_web_ftp_telnet_server_template.zip
.

I tried compiling this code with ESP-IDF but there are still a lot of dependencies on Arduino core such as timing and filesystem. This is a good start. I will try to replace those with IDF natives. Thanks for your support.


Fix the problem of pausing the beatmap per second on Android

https://github.com/ppy/osu/pull/4021
Opentk does not support android focus

Have you checked how this was fixed for iOS? Should probably be done in the same way.

Have you checked how this was fixed for iOS? Should probably be done in the same way.

For the way ios, android does not seem to work

please provide a reason when closing PRs, thanks!


com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Invalid byte 2 of 2-byte UTF-8 sequence. thrown on windows

From<EMAIL_ADDRESS>on March 26, 2013 07:00:54
Reproduce:
Please unzip the attached file and run ant.
I use powermock-easymock-testng-1.5
My ant is 1.8.3.
My OS is windows server 2003, 64-bit.
jdk 1.6.0_26
I can't reproduce it on my MacOS 10.8.2.
But i can reproduce it on my Redhat linux.
When I replace the testng to v5.7, i can't reproduce it.
Attachment: project.zip
Original issue: http://code.google.com/p/powermock/issues/detail?id=437

From<EMAIL_ADDRESS>on March 26, 2013 12:52:21
Sorry but I don't have time to look into this. First of all I don't have Redhat Linux (I have a Mac) and it'll be too much of a challenge to install Redhat only to look into this issue. I would really appreciate if you try to figure out what's wrong and fix the issue by providing a patch. That will probably be simpler since you are experiencing the problems. The project is open source and its dependent on contributions.


feat(deps): upgrade compiler dependencies

Upgrades project dependencies. See details in workflow run.

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

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

Questions ?
Please refer to the Backport tool documentation


Update JLFzf.jl

Before
julia> using JLFzf
julia> a = JLFzf.inter_fzf(["a", "b", "c"])

julia> @show a
a = "a\0b\0c"
"a\0b\0c"

After
julia> @show a
a = "b"
"b"

thx, this was changed in #6 to "preserve multi-line command", I don't know what's a better "sentinel value" here


fix: compress marketdata

smartENERGY provides data in 15-minute intervals, the amount of data leads to the following warning in HA:
2024-01-10 19:00:00.415 WARNING (Recorder) [homeassistant.components.recorder.db_schema] State attributes for sensor.epex_spot_data_price exceed maximum size of 16384 bytes. This can cause database performance issues; Attributes will not be stored
2024-01-10 19:00:00.415 WARNING (Recorder) [homeassistant.components.recorder.db_schema] State attributes for sensor.epex_spot_data_net_price exceed maximum size of 16384 bytes. This can cause database performance issues; Attributes will not be stored

As the price only changes hourly anyway, the data can be compressed, which is implemented by this PR.

Thanks for your contribution.


Invalid configuration: Unknown function onedark#GetColors

Hello... I cannot for the life of me figure out what the issue is.  Would very much appreciate any advice you can give :)
"Invalid configuration: ...site/pack/packer/start/onedark.nvim/lua/onedark/init.lua:95: Vim(let):E117: Unknown function: onedark#GetColors" file="init.lua",

Please tell us what neovim version are you using.
Have you tried to update onedark.nvim?

I am on the master branch, using packer, and using NVIM v0.7.0

Can you share your config, in particular how you're calling onedark's setup function?
Also please note that we aren't using vimscript, so this error probably comes from onedark.vim and not from onedark.nvim
https://github.com/joshdick/onedark.vim/blob/7db2ed5b825a311d0f6d12694d4738cf60106dc8/autoload/onedark.vim#L27
As you can see onedark#GetColors() is defined there and not in onedark.nvim

I had same issue as @rkabrick - it turned on that I also had onedark.vim theme in ~/.vim/colors.


Manage the false positive given from the 0 number

This is connected to this issue https://github.com/kandashi/Active-Token-Lighting/pull/91/files because i encounter the same issue with the property brightSight, but i think this check is something to add too.
Manage the false positive given from the 0 number value because is detected like a 'false' from standard ecmascript and wrongly set the 'null' value instead the '0' value, so i there is some other property number it will be correctly converted ?

Ok I found myself with a problem, I am developing a module that uses the ATE (https://github.com/p4535992/foundryvtt-lights-hud-ate) module a lot, but for how it is set up now the module is updated the actor's token prototype while I want to update the individual tokens also separately and also I have to manage also combinations of AEs when they are turned on and off.
I have tried to fix the code to make it work in this mode, made some test but i'm not happy with this, when you have time try to have a look at it and let me know.
At the same time I also fixed some minor bug fixes:

replace Object.assign with the mergeObject there it was some problem with the merging of the data.
Manage the false positive given from the 0 number

Ive taken the core idea of this PR and done a slight re-work myself. Prototype Token data will no longer be adjusted, and instead used as the baseline for Active Effects to apply onto.
This branch is avaliable https://github.com/kandashi/Active-Token-Lighting/tree/new-proto-rework


Free plan OAUTH support

Currently workflow support only the paid plans.

https://developers.google.com/gmail/api/quickstart/python#authorize_credentials_for_a_desktop_application


CORS / CORB error for data urls -- testable-projects

Methods tried:
d3.json(DATASET.FILE_PATH, function (error, data) {
    if (error) {
        throw error;
    }

yields

fetch(DATASET.FILE_PATH, {mode: 'no-cors', dataType:'jsonp'}, function (error, data) {
    if (error) {
        throw error;
     }

yields

I feel like I've solved this before with dataType: 'jsonp' when using AJAX... I'll look into that.
edit: AJAX request tried with both 'json' and 'jsonp' dataType , yielding the same result as with fetch .

We need someone to investigate and confirm if this is still the case.

@raisedadead Hello, I did some investigation on this with following result:
const URL = 'https://cdn.freecodecamp.org/testable-projects-fcc/data/tree_map/video-game-sales-data.json';

// CORS / CORB ERROR
d3.json(URL, function(error, data) {
  if (error) throw error;
});

// SUCCESS
fetch(URL, {mode: 'no-cors', dataType:'jsonp'}, function (error, data) {
  if (error) throw error;
});

// CORS / CORB ERROR
var xhttp = new XMLHttpRequest();
xhttp.open("GET", URL, true);
xhttp.send();

Also I did the test on CodePen via latest Chrome if it can help.

I landed a commit to enable execution https://github.com/freeCodeCamp/cdn/commit/ccd31d521d8f73c91163e4ec0a0e5145094d8136
Please comment if issue still exists.


Construct synthetic API for comprehensive testing of discovery sample gen

A synthetic API could replace redundant baseline coverage in toolkit by exercising all known features of the discovery sample gen transformers. This would obviate #201.
To aid such development, the following incomplete list serves to record test elements that might otherwise be overlooked:

formatting of Go Download method links with multipart resource paths (#645)

May not have bandwidth for this item anymore :(


Publish/Unpublish buttons wonky

From feedback:

Publish/unpublish buttons appear to do what they promise to, but land the user on a n HTTP 500 page.

Is this still true? Looks like this feedback came in a while ago.

@JCattera could you look into this one? It might already be fixed, but if not it should be relatively easy to fix.

The Publish/Unpublish works perfectly for me on all pages of the organizer, so I assume it's already been fixed.


Spreadsheet of 'response to' term requests

Response to requests 9-2017 B.xlsx

I didn't look at this, but what is it? If it is a long list of terms, perhaps it could be done programmatically.

I forgot to add: Where's the new TermGenie?

Hi @slaulederkind
Would it be possible for RGD to use annotation extensions for these ? We would keep a number of parent classes that make sense for grouping purposes (the exact ones to be discussed), and specify the exact chemical in the 'has input' field.
Thanks, Pascale

Personally I think that "response to" terms should ONLY be allowed in extensions, and blocked in primary annotation (similar to phase terms currently).
This would prevent their use for describing a change in viability in response to a specific chemical (a viability or growth phenotype).
I was going to recommend this soon, as a follow on from the slim talk (50% of mouse proteins  already have 'response to' annotations, and often we would be better to class these as "unknown physiological role"). Sometime no annotation is better......."response to should only be applied as an extension to certain pathways (mainly signalling).

RGD doesn't use column 16 at the moment, but maybe in the future.

Would it be possible to use Noctua for these annotations for now ? And then upload the annotations generated by Noctua back into RGD ?

Personally I think that "response to" terms should ONLY be allowed in extensions, and blocked in primary annotation (similar to phase terms currently)

good suggestion. We could go even further and ditch the terms from GO and use an exposure event ontology...

I maybe misunderstanding this thread but the UCL team is not convinced about removing the 'response to' terms. These enable grouping of many different processes together and when I have conducted functional analysis I have found it useful to see the response to terms enriched as they often help confirm the area of biology being disregulated, or relevant to the samples. If this is a serious proposal please let me know and I will get examples together to explain this further. But I do not want to do this unless there is a suggestion that all 'response to' terms are going to be removed. Would it be possible to do a text search for 'response to' and transcriptomic/proteomic/functional analysis to get a sense of how often papers find this term useful in their analysis?

My comment was more of an opinion than a proposal. I do think we need to adress the use of "response to terms"
As @ukemi  said during my slim presentation at GOC, everything occurs in respsonse to something. Some response to terms are probably OK in GO, but we should really think what we mean when  we use them.
Response to hormone, or other receptor ligand, probably OK, but would this not always be used in the context of a signalling pathway as an extension?
response to drugs, like " response to vasoconstrictor agent" seems outside of the scope of GO?
At PomBase we annotate response to x using the phenotype ontology, because all that is usually shown is an effect on growth in a mutant.
Where you say "often help confirm the area of biology being disregulated" indicates that these are not normal processes, and are therefore outside of the scope of GO.
We already  almost half of our protein coding genes annotated to "response to some chemical" , and this isn't really often indicative of any particular process ( It is frequently just a pathological/toxic effect of the chemical). Similarly for mouse, over 11,000 gene products annotated to response to something terms.
When the response * is* part of an identifiable biological program/process,  we can make an annotation to the process with "response to" in the extension (with occurs during, or part_of).
This is probably a good topic for discussion on a future annotation call, or at a future GO meeting. It would be good to have published examples of usefulness. I'm sure we have some good published examples of the phenotypes of drug sensitivities and resistance.  They  may be useful, but that doesn't necessarily mean that they should be GO terms.
A  generic cell level phenotype ontology would help to capture these....

At PomBase we annotate response to x using the phenotype ontology ...

For this reason, it's convenient for us to have the "response to" terms in GO -- we use them in logical definitions for FYPO terms. That usage would be unaffected by flagging some or all of the GO response terms as not for direct annotation.
In principle we could rejig the FYPO logical defs to use the exposure event ontology that Chris alluded to. In practice, the ExO listed at OBO Foundry isn't remotely suited to our purposes at present (and I haven't found any others), so we would have to inundate its maintainers with requests as well as do the rest of the work of updating our defs. Our lives will be easier if we don't have to do all that.
So at present I favor keeping the terms, for admittedly selfish reasons. On whether to annotate using them, I'm approximately neutral, with no objection to some restrictions.

A good example of where they should not be used is in changes in gene expression in response to chemical (for example arsenic).
Arsenic causes problems for 100s of enzymes. Does it interfere with iron biosynthesis? (I'm not sure).
But if a chemical is toxic  a good annotation would be either
signalling pathway x occurs_during response to chemical y
or
detoxification of chemical y
If you can't be this specific an effect might just be due to the toxicity.
A good first move would be to ban IEP  for these terms.....

just wanted to also state that response to terms do not just cover the signaling pathways but the whole response of a cell to a specific signal, which might lead to for eg secretion of another signaling molecule

Hi @RLovering
Can you give some examples of useful enrichments ? By definition enrichments should be groups, so perhaps having grouping terms such as 'response to antibiotic' and 'response DNA damage' + the with column for the specific treatment would be sufficient ?
Thanks, Pascale

just wanted to also state that response to terms do not just cover the signaling pathways but the whole response of a cell to a specific signal, which might lead to for eg secretion of another signaling molecule

So in these cases wouldn't you want to couple?
So
exocytosis/signalling etc  occurs_during response_to x
These "response to" terms are used in many unintended ways.
For example (and these are the first 2 I looked at randomly!)
http://amigo.geneontology.org/amigo/reference/PMID:20978158
Title
A novel human dynactin-associated protein, dynAP, promotes activation of Akt, and ergosterol-related compounds induce dynAP-dependent apoptosis of human cancer cells.
used for
response to ergosterol?
This isn't really saying anything about a biological process.
http://amigo.geneontology.org/amigo/term/GO:0036275
http://www.informatics.jax.org/reference/MGI:5636128
used for "response to flouro uracil.
These are not processes, they are phenotypes.
There is a reason to use some terms probably like "response to certain stresses, Oxidative, osmolarity, DNA damage" but  in these cases it should be possible  to say what the process is (signalling, or detoxification or whatever) with the occurs_during/part_of "response to x
as an extension.
Otherwise- how do you know that it is really a  valid organismal response?

I would challenge all of these if I had time......
http://amigo.geneontology.org/amigo/term/GO:0060992

response to methyamine?
http://amigo.geneontology.org/amigo/reference/PMID:7440563
for
Glycine dehydrogenase (decarboxylating), mitochondrial?
methyamine is an inhibitor....

http://amigo.geneontology.org/amigo/term/GO:1905705
cellular response to paclitaxel (from IEP)
from
http://www.sciencedirect.com/science/article/pii/S0014299908003968
Many of these terms are used only once or twice and they are not biological processes they are phenotypes.
Perhaps to start with we should restrict the usage?

Surely we need to be able to specify which process the  "response to thing" is affecting?

@pgaudet and @ukemi and I discussed the 'response to' issue on a recent call.
We think this issue merits a more in-depth discussion akin to what is currently being done for signaling pathways.
We'd like to propose a 'response to' session or workshop at the GOC meeting in NY in May.  The main goals would be to:

Understand better what groups who use the 'response to' terms are hoping to capture with these annotations

Determine what level of granularity is appropriate  for 'response to' terms in the ontology

Devise annotation SOPs for annotating 'responses'

We will discuss more on a future annotation call.

Moved from #15103
We should take a good look what we are really using these terms to annotate.
Many appear to represent conditions. Some are phenotypes. Some are the target of a drug. Some are requested to construct logical definitions of phenotypes and should not be used in annotation (maybe we could do this differently?). It often isn't clear which BP the response is related to (when it usually could be). etc. You can throw any chemical at an organism and most times there will be some "response"...what does it mean?
Some examples:
cellular response to topoisomerase inhibitor? (drug target?)
cellular response to gold(3+)????
cellular response to alkane?
cellular response to boron-containing substance levels?
GO:1901593 response to GW 7647 ?????
GO:0072757 cellular response to camptothecin (camptothecin is A topoisomerase inhibitor see above)
GO:1904842 response to nitroglycerin? hmmm....
GO:0070301 cellular response to hydrogen peroxide?? isn't that just the oxidative stress response? It's a condition used to produce oxidative stress (response to oxidative stress is a useful one, if qualified).
It would be better if these terms were only used as refinements to true process annotations:
"signalling pathway x" occurs_during "response to y"
or "cellular detoxification" in response to y.
It is difficult to assess what is "unknown" with so many uninformative "response to x " annotations...
Comment from @mah11
Re "response to" terms: quite a few of the strange-looking ones are there to allow other ontologies (including FYPO) to use them in logical definitions or other cross-references. Any such terms should be flagged as not for gene product annotation (I thought they were, but it's certainly possible that some were missed).
https://mailman.stanford.edu/pipermail/go-ontology/2016-April/007432.html

For the FYPO owl definition use case, do you actually need a response-to-X GO term, or do you need the X? You could use your SPECO ontology here. Or in many cases, CHEBI. For other species we are developing a multispecies exposure ontology https://github.com/EnvironmentOntology/environmental-exposure-ontology/

@cmungall

For the FYPO owl definition use case ... [questions]

I did a quick review of FYPO terms, and they fall into a few categories:

In most cases, usually cell population growth terms, we do use ChEBI for X. Presumably these are of no concern here.
Some terms refer to GO "cellular response to" terms that haven't been called into question (responses to calcium ions, iron ions, pheromone, ROS, or various stresses that have reasonably well-characterized responses).
Among the remainder, there are responses to chemicals, of which I think at least some could be converted to annotations using conditions+a chemical-agnostic FYPO term, but we would have to review the annotations to make sure. For some chemicals, there are both a lot of terms and a lot of annotations, so changing them would be a big, tedious task unless there's a way to automate it (applies to hydrogen peroxide, hydroxyurea, methyl methanesulfonate).

easy example: abnormal chromosome morphology during cellular response to acetaldehyde
harder example: abnormal mitotic cell cycle regulation during cellular response to hydroxyurea

The rest are the potentially problematic ones - the stimulus isn't presence of a chemical, and I don't know whether there's really a specific and biologically meaningful cellular response.

examples: increased RNA level during cellular response to adenine starvation, decreased protein degradation during cellular response to UV

Could the exposure ontology be used regardless of whether a GO "response to" BP does or should exist? If so, we could switch to it in principle, but I would greatly appreciate guidance for suitable design patterns.
In the attached list I've ferreted out all the "response to" terms we're using, and put them in categories as above.
responses_in_fypo.txt

updated attached list (new term requested using "cellular response to leucine starvation")

... and would the exposure ontology include "exposure to x starvation"?


Casting Runtime errors

When casting a data structure in Changesets that the library does not expect, it will trigger a runtime error such as
** (RuntimeError) could not infer polymorphic embed from data %{}

Ideally, I'd rather have this as an :error as would be produced by Ecto.Type.cast/1. This way, I could get the error back to the Changeset instead of having to defensively try to rescue errors with Changeset casting.
Could this be improved at library level, or am I somehow using this wrong currently?

I think it depends whether the error is caused by a bug in the code, or invalid user input.
User input will go through a set of Changeset validations and any errors will be added to the Changeset and generally displayed in a form, allowing the user to correct his input. However, when there's a bug in your code, in Erlang/Elixir it's normal to let the application crash; you should then notice the bug and fix it.
If we add an error to the Changeset, and the error was caused by some erroneous code, we might miss that bug.
I guess in your case, this was a bug in the code?

I'll check tomorrow again if it was my own code but from what I understand this is a casting error in the changesets.
So cast produces the changeset from the parameters. We cannot run changeset validations before casting the data right? Currently, I'm casting external parameters to the polymorphic embed with cast. And this triggers that runtime error when the external parameters are not what the library expects for determining which polymorphic type to use.

If the library doesn't know which type to use, it is an error in the code. Typically a hidden input "__type__" would be missing.

Right, so that's what I got a problem with. I'm building an API where the user can supply anything they want. With this library's current approach, I'd have to write a pre-validation outside of Ecto Changesets before attempting to cast the external parameters to the polymorphic embed. Or optionally, build a defensive rescue for a failed Changeset cast.
I feel this is not how Ecto custom types should work. The Changesets are built for validating external data, and should generally not trigger a runtime error on receiving unexpected data. It should simply fail to cast it, which would propagate back to the Changeset as a :cast error.
The custom Ecto.Type.cast/1 callback return values reflect this: https://github.com/elixir-ecto/ecto/blob/266e4fc2313c43f10276ac45e59f72c768e7ecb9/lib/ecto/type.ex#L229
If we expect that cast/1 would cause a runtime error upon unexpected data, it would be annotated with a bang ! instead, as in cast!/1.

This library's cast also may return a tuple {:error, changeset} on error https://github.com/mathieuprog/polymorphic_embed/blob/master/lib/polymorphic_embed/custom_type.ex#L43

If we expect that cast/1 would cause a runtime error upon unexpected data, it would be annotated with a bang ! instead, as in cast!/1.

Not true. Take a random example, put_assoc: if you pass it a wrong field as argument, it will trigger an error (KeyError), although it has no bang !. A function without a bang doesn't necessarily mean it won't raise an error.

the user can supply anything they want

What kind of inputs do you provide to the user? How does the type get determined?

I don't believe it's the same thing with put_assoc. Because you do not pass external parameters to it directly. Instead, it takes a Changeset and the name of the field, which is supplied by the programmer, not the user. You would've already constructed the Changeset before calling it. Therefore, if it caused a runtime error that would clearly be an error in the application code.
Whereas if the cast fails, there is that callback return type for indicating the failure, handled by Ecto. I don't see why it should also optionally raise errors in some cases.
In my case, as my users are my API consumers, I have no control over what they supply as parameters in their endpoint calls. I use Changesets to validate the supplied parameters. If they supply faulty parameters, I'd like to give them back the Changeset errors indicating which cast or validation failed, instead of it simply crashing.

Thank you I understand your argument. Let me do some research on the topic and ask the community, I'll get back to you soon.

Thanks for spending time looking into it!

Thank you for raising this question. I'd like to add an option to make it optionally raise, but to default the option to a changeset error as you suggested.
If you have any idea of the error key and error message to add in the changeset, and even option name and value for raising, let me know:)

Awesome, thanks!
I feel the current error message is nicely descriptive. I mean
"could not infer polymorphic embed from data #{inspect(attrs)}"

As for the key, maybe something like :poly_inference or something to indicate it's an error determining which embedded schema to pick would work?

This is an error message for programmers. Changeset errors are for users (as "can't be black", ""should be at least %{count} characters", etc.).

An option :on_type_not_found has been added. By default, a changeset error "is invalid" will be added to the changeset.
Let me know if you think this can be improved.
Note that the API has changed in the meanwhile for defining and casting your dynamic embeds, check the Readme.

Thanks a lot, I appreciate you spending your personal time to produce a solution to this!


I can't reproduce your BulkRead example.

I can't reproduce your BulkRead example.
// USE
var items = itemsNames.Select(a => new Item { Name = a }); // creating list of Items where only Name is set
var bulkConfig = new BulkConfig { UpdateByProperties = new List<string> { nameof(Item.Name) } };
context.BulkRead(items, bulkConfig); // Items list will be loaded from Db with data(other properties)

In fact, items you create is not a list but IEnumerable and this example produces compile compiler Error CS0411:
The type arguments for method 'DbContext.BulkExtensions.BulkRead' cannot be inferred from the usage.
If I convert items from an IEnumerable to a List by adding .ToList() in the first line of your example then compile error goes away but getting runtime error instead "The method or operation is not implemented" with no clues what is about.

Yes it should be list:
var items = itemsNames.Select(a => new Item { Name = a }).ToList();
I've updated ReadMe.
As for the second error, in source code in EFCoreBulkTest there is example that works.
However if you are using Sqlite, BulkRead for Lite is not yet implemented, probably why you have this exception.

Thanks! This is really pity. Looking forward for SQLite implementation!

BulkRead is now implemented for Sqlite, v5.0.8.+

Oh, wow. Never seen that feature request would got implemented so fast. Thanks!


Odd behavior with auto definition

Hi there,
I've recently started using your library and I have come across some odd behaviour. I'm not sure if I'm missing something subtle here or not.
#include "xtensor/xarray.hpp"
#include "xtensor/xmath.hpp"
#include "xtensor/xio.hpp"
#include "xtensor/xview.hpp"

template <typename E>
auto deg_to_rad(E&& input) {
	return input * (M_PI / 180.0);
}

auto lims(double x, double y, std::size_t steps) {
	xt::xtensor<double, 2> limits( {2, steps} );

	auto theta = deg_to_rad(xt::linspace(0, 90, steps));

	std::cout << "theta : " << theta << std::endl;
	auto temp_x = x * xt::cos(theta);
	std::cout << "theta : " << theta << std::endl;
	xt::view(limits, 0) = temp_x;
	//xt::view(limits, 0) = x * xt::cos(theta);

	std::cout << "theta : " << theta << std::endl;
	auto temp_y = y * xt::sin(theta);
	std::cout << "theta : " << theta << std::endl;
	xt::view(limits, 1) = temp_y;
	//xt::view(limits, 1) = y * xt::sin(theta);

	return limits;
}

int main(void) {
	std::cout << lims(1,1,5) << std::endl;
	return 0;
}

The output of the above is:
theta : { 0.      ,  0.383972,  0.785398,  1.169371,  1.570796}
theta : { 0.      ,  0.383972,  0.785398,  1.169371,  1.570796}
theta : { 0.      ,  0.383972,  0.785398,  1.169371,  1.570796}
theta : { 0.,  0.,  0.,  0.,  0.}
terminate called after throwing an instance of 'xt::broadcast_error'
  what():  Incompatible dimension of arrays:
 LHS shape = (5, )
 RHS shape =<PHONE_NUMBER>05216, )
[1]    13749 abort (core dumped)  ./a.out

Am I missing something with regards to theta being reset?
I've noticed that if I change the theta definition from auto theta = ... to xt::xtensor<double, 1> theta = ... the code executes as expected. As a side effect, changing the definition from auto allows direct assignment to the xt::views as commented out in the lims function above.
Thanks a million for any insight!

The reason for this is that in the case of an auto return type, you are returning an un-evaluated expression that depends on variables that are local to the function, and are out of scope at the time when you need them. (Basically, you end up with dangling references)
You can check out this section of the documentation for more information about this:
https://xtensor.readthedocs.io/en/0.19.3/closure-semantics.html#writing-functions-that-return-expressions
Let us know if this is helpful!

Thanks for the quick reply Sylvain!
I see now that the linspace rvalue was the issue and that's what ended up dangling.
I really appreciate the help!


Animation

possibly add carousels or 3-D imaging javascript plugins to various screens

Ben looked into doing a carousel of pages on the home page, but it uses jQuery, so we decided not to implement it


[T3A4][T15-A1]Ying Ying Choi

Ready for review.

@ychoi1997 Some comments added. Please close the PR after reading comments.
.- Good attempt. Keep it the good work.

As per discussed in tutorial earlier on, it is more suitable to have the exception thrown in the storage class's save method instead.


Problem with DND Beyond Importer

Since 5 days we have been getting a lot of error messages when we log into a campaign in the FoundryVTT.
I have now tested the following in several campaigns:
All modules deactivated and module by module activated until the error messages reappear.

As of yesterday we can no longer import any characters.
Error see screenshot, if you need more logs, please write to me.
Briefly about my surroundings:
Foundry VTT runs on a Windows Server 2019 with IIS.
Foundry Version: 0.8.9
DND Beyond Importer Version: 2.5.33
GameSystem: DND5e - Version 1.5.3
greeting
Martin

The compendium messages indicate that the DDB Compendiums are not set correctly - can you make sure that the Settings -> Modules -> DDB Importer -> Compendiums are set correctly.
Regarding character imports, what errors are you getting?

Closed via Discord - compendium settings had become borked.


Solving issue #937

Replacing deprecated MAINTAINER from /dev/Dockerfile with LABEL
Be sure and add yourself to AUTHORS along with your changes.

@edgardmota looks good, thanks! please add yourself to the AUTHORS file.

Codecov Report

Merging #958 into master will increase coverage by 0.08%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #958      +/-   ##
==========================================
+ Coverage   78.49%   78.58%   +0.08%
==========================================
  Files          52       52
  Lines        5572     5572
==========================================
+ Hits         4374     4379       +5
+ Misses       1198     1193       -5

Impacted Files
Coverage Δ

vent/api/plugins.py
81.08% <0%> (+0.18%)
:arrow_up:

vent/api/menu_helpers.py
93.11% <0%> (+0.4%)
:arrow_up:

vent/menus/main.py
79.21% <0%> (+0.78%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 67b01ab...59df75d. Read the comment docs.


CI: upgrade macOS testing environments

Cirrus seems to have dropped support for macOS Catalina (10?). It is claimed to
be officially supported¹ but jobs on it simply stall forever. For Rumur, it is
fine to migrate to newer macOS as we only really support whatever is the latest
macOS.
¹ https://cirrus-ci.org/guide/macOS/

Rebased into #222.


MM-14931 Fix markdown checkboxes not being rendered correctly after post edits

Summary
This is a really weird one. If a checkbox was unedited in the post, the post would not update. I checked to make sure that we were actually re-rendering the Markdown component, which we were, and tracked (with @hmhealey's help) the problem down to the fact that the React key for the checkbox elements was preventing the low-level re-rendering of the checkbox to happen.
My fix is a workaround to change the key based on whether the checkbox is checked or not. Open to other suggestions if others can think of better solutions.
Ticket Link
https://mattermost.atlassian.net/browse/MM-14931

@migbot keys only need to be unique per list not overall so collisions with other lists aren't a worry

The best way to pick a key is to use a string that uniquely identifies a list item among its siblings

https://reactjs.org/docs/lists-and-keys.html#keys

@migbot you're right, just updating the checked attrib to be boolean worked great 👍


Fix Version.next_devrelease() when starting with a prerelease.

Version('1.2.3-pre.0').next_devrelease() raises an exception, and Version('1.2.3-dev.0').next_devrelease() doesn't change the version.  It seems that this code was probably copied from next_prerelease(), but not completely updated from pre to dev?
The version/expected list is based on the behavior of next_prerelease().  I'm not sure if this is the most "correct" logic here?  I removed passing pre to the created version because turning "1.2.3-alpha.0" into "1.2.3-alpha.0-dev.0" didn't seem right, but I'm not sure that turning it into "1.2.3-dev.0" is right either.

[X ] Added tests for changed code.
[ ] Updated documentation for changed code.

Technically 1.2.3-alpha.0.dev.0 is a pre-release to the pre-release 1.2.3-alpha.0. But in this case I suspect the right behaviour is to bump to 1.2.3-alpha.1.dev.0. This means the last set component gets bumped prior to initialising dev release. So 1.2.3 -> 1.2.4-dev0, 1.2.3-post1 -> 1.2.3-post2.dev0 etc.

Technically 1.2.3-alpha.0.dev.0 is a pre-release to the pre-release 1.2.3-alpha.0. But in this case I suspect the right behaviour is to bump to 1.2.3-alpha.1.dev.0. This means the last set component gets bumped prior to initialising dev release. So 1.2.3 -> 1.2.4-dev0, 1.2.3-post1 -> 1.2.3-post2.dev0 etc.

That's an option for sure.  In this case I was just trying to make the logic not obviously broken.
Right now, Version('1.2.3-dev.0').next_devrelease() doesn't do anything and that's obviously wrong, with this patch it will return Version('1.2.3-dev.1') which is correct.
I consider the Version('1.2.3-pre.0').next_devrelease()  behavior to be more of a corner-case.  The alpha+dev type versioning will likely be controversial no matter which approach is chosen and some people will use it and others will just implement their own versioning logic (which I ended up doing anyway because I didn't like how the release tags kept getting expanded).

Merged via https://github.com/python-poetry/poetry-core/commit/4781c82b2a0326fd344fbb28c721b58f8551b81a


Fixes YASS container

This is just a oneliner, which fixes error message reported in Issue #56

By design we do not install spikeinterface in the docker.
spikeinterface is updated too often and maintaining theses images is tedious.
So we install spikeinterface on-the-fly in the docker image with a pip install in the caintainer at run time. It is a small overhead but really more easy to maintain.
Users can do it if they want in there own dock images.
For your error I do not understand why pip install is not working : do you have network on run time ?

See my reply here: https://github.com/SpikeInterface/spikeinterface/issues/1186#issuecomment-1379038828
The problem is the Python version. It needs to be fixed on the SpikeInterface side


Better errors

This PR re-merges the reverted branch, but I am implementing some changes we discussed during the last week, including #55.

@antoinefalisse @suhlrich I have solved all of the conflicts in this PR and tested locally. It allows me to login normally and visualize everything normally.
We should test a full Opencap cycle, I have no phones for this.
However, this PR introduces a LOT of changes (not in functionality, but in how errors are displayed and handled), and I had to manually resolve all of the conflicts, so we have to test it really carefully and make sure everything is doing what it should be doing (In the original PR, before of the conflicts, there were not many of the bug fixes that now are implemented, so we have to make sure that everything is still there).

@suhlrich I will address all of these comments today after the meetings.


Software Packaging MD (Hexo)

Add links and information.

1.8 Epic 8: Software Packaging + Criteria
1.8.1 Story 1 + Criteria:

As a student, I want to access the Software Packaging page to understand how applications and their dependencies are bundled for consistent execution.

Acceptance Criteria:

The index or glossary should have a clearly visible and functional link to the Software Packaging page.
The link must direct the user to the appropriate page.

1.8.2 Story 2 + Criteria:

As a student, I want to confirm that the Software Packaging page accurately describes the software bundling process.
Acceptance Criteria:

The browser tab should display “Software Packaging.”

The page heading should read “Software Packaging.”

The page should include explanations about key concepts like "Dependency Management" and "Portable Applications."


Silence warnings

Hi!
First of all - thanks for this really nice and helpful library!
It's not a bug, rather a feature request.
I'm getting tons of warnings like those:
WARNING	Property: Unknown Property name.
WARNING	Property: Unknown Property name.
WARNING	Property: Unknown Property name.
WARNING	Property: Unknown Property name.
WARNING	Property: Unknown Property name.
WARNING	Property: Unknown Property name.
WARNING	Property: Unknown Property name.
WARNING	Property: Unknown Property name.

Is there a way to silence them? I couldn't find any verbose option.
Thanks!
Daniel

Hi - great idea! I bet there's something we could pass to lxml to have those suppressed unless in verbose mode.
I'll have a look in a few weeks when I have some time, or happy to review a PR if you want to take a go at it.


3.0.8 RE1 305->30d , inventory gender changed.

Version
3.0.8
Seed
R710-3B2X-ZTRHB0ZZCR64HNNMKATYVYZZZZZZZZZZZZZ
Scenario
RE 1 (Chris)
Player Character
chris
What happened?
Connected 30D:2 [FLAMETHROWER] to 305:2 (locked 138)
305 back to 30D , chris's inventory changed to jill's.
g Chris_01_2023-07-02 23^51.33.zip

This can also happen when taking the lift in the garden. It is a very annoying issue/bug in the game.


Add OCP support to helm chart

This setup has been tested with OCP 4.6 and 4.7, and is based on these previous discussions:

okd 4.5: https://github.com/longhorn/longhorn/issues/1831#issuecomment-702690613
okd 4.6: https://github.com/longhorn/longhorn/issues/1831#issuecomment-765884631
oauth-proxy: https://github.com/openshift/oauth-proxy/blob/master/contrib/sidecar.yaml

Main changes and tasks for OCP are:

security setup for namespace longhorn-system
option to use separate disk in /var/mnt/longhorn
exposing longhorn ui via oauth-proxy
adding finalizers for mount propagation
machineconfig file to start iscsid
mahcineconfig file to mount /var/mnt/longhorn

@binguo-casa Thanks for the contribution! Please help resolve the DCO check failure first. ref: https://github.com/longhorn/longhorn/pull/2909/checks?check_run_id=3383674759

@khushboo-rancher let's check this after 1.2.0

Missing instancemanagers/finalizers, will figure out how to update:
+++ b/longhorn/helm/1.2.0/longhorn/templates/clusterrole.yaml
@@ -38,7 +38,7 @@ rules:
   resources: ["volumes", "volumes/status", "engines", "engines/status", "replicas", "replicas/status", "settings",
               "engineimages", "engineimages/status", "nodes", "nodes/status", "instancemanagers", "instancemanagers/status",
   {{- if .Values.openshift.finalizers }}
-              "engineimages/finalizers", "nodes/finalizers",
+              "engineimages/finalizers", "nodes/finalizers", "instancemanagers/finalizers",
   {{- end }}
               "sharemanagers", "sharemanagers/status", "backingimages", "backingimages/status",
               "backingimagemanagers", "backingimagemanagers/status", "backingimagedatasources", "backingimagedatasources/status",

@binguo-casa could you help resolve the conflicts? thanks.

Form my Testing kind: MachineConfig is no longer required.

This seems outdated. Let's do https://github.com/longhorn/longhorn/pull/5004 instead.
@binguo-casa feel free to be involved in the review of 5004. Thanks for the contribution.


swarmctl: Remove -f flag for cluster update.

This is not supported anymore, adds confusion to --help.
Signed-off-by: Andrea Luzzardi<EMAIL_ADDRESS>

[Current coverage][cc-pull] is 52.71%

Merging [#886][cc-pull] into [master][cc-base-branch] will decrease coverage by 0.12%

3 files (not in diff) in manager/orchestrator were modified. more

Misses +6
Partials +1
Hits -7

1 files (not in diff) in manager were modified. more

Misses -1
Partials -1
Hits -2

3 files (not in diff) in ca were modified. more

Misses +2
Hits -9

File .../test/deepcopy.pb.go (not in diff) was modified. more

Misses +2
Partials 0
Hits -2

@@             master       #886   diff @@
==========================================
  Files            70         70
  Lines         11154      11143    -11
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits           5894       5874    -20
- Misses         4434       4443     +9
  Partials        826        826

[][cc-pull]

Powered by Codecov. Last updated by [bdca88d...231d43d][cc-compare]
[cc-base-branch]: https://codecov.io/gh/docker/swarmkit/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/docker/swarmkit/compare/bdca88de522b6f272895194de0ca92f4b08577a4...231d43d586d7ff8b78933e10d7689909eb0ffcbb
[cc-pull]: https://codecov.io/gh/docker/swarmkit/pull/886?src=pr

LGTM


fix: Update Lacework provider requirement to 0.27

Summary
Updates the Lacework provider version requirement, because the lacework_integration_aws_org_agentless_scanning resource used in 0.5.0 of the module was added in version 0.27 of the provider.
How did you test this change?

I'm being a little lazy and editing in the browser, was going to wait and see if it passes your CI. :) Happy to test something else locally if need be.
Issue

Good catch!


CouchDB_Onprem_Bug_Fixes

updates Hashcode for SessionId
updates README to conform to a newer template
adds support for query to get all databases.
refactors a few constants to use ApplicationConstant

Thanks! See comments, with request to add a comment before merging.

Hi Tal, comment added.  Thanks!

Next time, please sign-off all the commits (it usually doesn't work when adding fixes directly from GIthub GUI page)


Enable BWC tests with with OpenSearch 1.1

Signed-off-by: Joshua Li<EMAIL_ADDRESS>Description
closes #733
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[ ] All tests pass, including unit test, integration test and doctest

[ ] New functionality has been documented.

[ ] New functionality has javadoc added
[ ] New functionality has user manual doc added

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #772 (3407fdb) into main (ce15448) will decrease coverage by 32.09%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##               main     #772       +/-   ##
=============================================
- Coverage     94.85%   62.76%   -32.10%
=============================================
  Files           288       10      -278
  Lines          7839      658     -7181
  Branches        571      118      -453
=============================================
- Hits           7436      413     -7023
+ Misses          349      192      -157
+ Partials         54       53        -1

Flag
Coverage Δ

query-workbench
62.76% <ø> (ø)

sql-engine
?

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

Impacted Files
Coverage Δ

...a/org/opensearch/sql/utils/MLCommonsConstants.java

...ensearch/sql/sql/parser/AstAggregationBuilder.java

...nsearch/sql/planner/physical/RareTopNOperator.java

...arch/sql/expression/function/FunctionResolver.java

...ql/planner/physical/collector/BucketCollector.java

...opensearch/sql/expression/ReferenceExpression.java

...rch/planner/logical/rule/MergeAggAndIndexScan.java

...in/java/org/opensearch/sql/data/type/ExprType.java

...opensearch/sql/exception/QueryEngineException.java

...nsearch/sql/expression/aggregation/Aggregator.java

... and 268 more

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


/usr/bin/ld: cannot find -lopencv_dep_cudart

I met a problem when I tried to build the program.
$ make

Linking CXX shared library libbgslibrary_core.so
/usr/bin/ld: cannot find -lopencv_dep_cudart
collect2: error: ld returned 1 exit status
CMakeFiles/bgslibrary_core.dir/build.make:2639: recipe for target 'libbgslibrary_core.so' failed
make[2]: *** [libbgslibrary_core.so] Error 1
CMakeFiles/Makefile2:67: recipe for target 'CMakeFiles/bgslibrary_core.dir/all' failed
make[1]: *** [CMakeFiles/bgslibrary_core.dir/all] Error 2
Makefile:127: recipe for target 'all' failed
make: *** [all] Error 2

I think it doesn't need CUDA, but how to fix it.

Hi @yao177 , thanks for reporting this issue. Yes, it's strange, because bgslib do not use CUDA.

Oh, I found a solution. To add -DCUDA_USE_STATIC_CUDA_RUNTIME=OFF can fix it.

Great, thank you @yao177 for this info.


Downloading to file with name of part of URL

This is a feature request.
In case you have a URL, for example
https://www.abc.company.com/123456/file=bla.exe
I would like my file to be downloaded to folder location "123456/bla.exe"
If this is currently already possible, I would love to learn how :)
BR,
Des

something like this
url: .+?://www\.abc\.company\.com/([0-9]+)/.*
destination path: ${url:1}/


removed resource script field doesn't update scene data (error when opening scene) & Resources

Godot version:

3.3.mono.rc6.official
OS/device including version:

kubuntu 20.10, Windows 10
Issue description:

When a script that exports a resource type is part of a packedscene, its exported field/data is saved with it.
When this field is later removed from the script, the assembly rebuilt (clicking "Rebuild" in the editor), the assigned reference deleted and the scene reopened, the editor complains about missing dependencies (which are the removed fields' data), even though there should be none. The loader seems to ignore the actual script fields, loading that lingering data preemptively for some reason.
This can be worked around by opening every related scene via 'open anyway', manually and resaving it, which is less than ideal though.
Steps to reproduce:
Create a c# script, add an exported field of some resource type to it. create a resource and assign it. Save this as a PackedScene. close the scene. Delete the resource, remove the field from the script. click rebuild. Reopen the scene. Notice the warning.
By inspecting the Packedscene in a text editor, it shows that the removed fields' data is still present, which results in this error.

Here's an example:
`[gd_resource type="Resource" load_steps=4 format=2]
[ext_resource path="res://Shared/Scripts/Resources/EquipmentModelHandle.cs" type="Script" id=1]
[ext_resource path="res://Client/Art/Icons/foresticons/ForestIcons_back/addons/ForestIcons_111_b.PNG" type="Texture" id=2]
[ext_resource path="res://Client/GameData/Equipment/SimplePants.tscn" type="PackedScene" id=3]
[resource]
script = ExtResource( 1 )
prefab = ExtResource( 3 )
readableName = "Test Pants"
icon = ExtResource( 2 )
slot = 0`
Where the field 'prefab' is not part of the script anymore, but the tscn still contains the external resource reference. This results in cyclic errors in my case and everyhing cascading from it.

Still an issue in 3.4. It means the game doesn't start when there were at some points assignments to nodes in scenes that no longer exist (n/either the fields n/or their assigned content). It requires manually going through each and every one and resaving it.

This is a really bad showstopper in some situations. I have scenes that cannot be opened anymore with 'unexpected end of file' errors. Luckily i know the source of the error so i can manually open the scene file in a text editor and remove the offending lines, but others might not.

This is not specific to mono, same thing happens with GDScript.
When you delete a resource that is referenced in a scene it shows a dialog warning you:

If you proceed to remove the resource the scene will keep the reference to the now non-existent resource so opening the scene results in a error loading the scene:

This happens even if I delete the exported property that references the resource from the Main.gd script before opening the scene.

I am seeing same in Godot 4.2 beta 2
I have deleted @export var soil_data: Soil but tscn file still have soil_data = ExtResource("2_0ywxf"). It is not showing the field in the editor thou.


Follow up for 53

Heh, some GitHub bug here ... please ignor (the Author stays correctly set to Daniel, but the author avatar is broken).


Maintainers team in det-lab

@pibion repositories are now under det-lab,
it would be useful to create a Team of Awkward-kaitai maintainers with Maintain permission on those 2 repositories and add me, @jpivarski and @ManasviGoyal to it.

@zonca I think I've got this set up now!

@pibion group is there, next you need to add the 2 repositories under the group

@zonca thank you!  I think I've added the repositories.

ok, finally from https://github.com/orgs/det-lab/teams/maintainers/repositories you should be able to give "Maintain" permissions on those repos.