Add Chinese (Traditional) translations

Chinese (Traditional) (zh-TW) language file has been created.

Thanks for the translation!


Train problem

Hi:
Do you know the reason about the trouble "epoch 1, validation error nan, train error nan  time spent 31758.06"

It looks like something is wrong with your training data.
What is your setting? Are you using GPU?

I was using CPU

I have checked my data, the data is ok.

Use below script to check for nan in your training data:
https://github.com/CSTR-Edinburgh/merlin/blob/master/egs/build_your_own_voice/s1/scripts/test_nan.sh

thank you
cal you tell me what's the additional_features?

additional features can be anything apart from linguistic features extracted from text.
For example, word embeddings, or bottleneck features etc.,  when you have such features prepared in "data/wemb/.wemb" and "data/bn/.bn"
This is how you set them in config file:
additional_features : {'wemb':300, 'bn': 32}

I encountered the same problem. I did check my training files but none of them had a "NaN" value.
I turns out that I had pretraining enabled and that my learning rate was too large (0.004). Lowering it (to 0.002) solved the problem.
Hope this can be useful for others who come across this issue

@syltruong May I know where are the pretraining and learning rate variables?

Pretraining configuration setting must be set by the user within python https://github.com/CSTR-Edinburgh/merlin/blob/master/src/configuration/configuration.py#L983-L993
Learning rate can be set in a .conf file https://github.com/CSTR-Edinburgh/merlin/blob/master/src/configuration/configuration.py#L337


How to check if "aes_gcm_dec_128" failed to decrypt ciphertext into plaintext?

We plan to use ISA-L crypto AES_128_GCM in HTTP/3 case. Given that a HTTP/3 endpoint receives a AES_128_GCM AEAD-protected packet whose QUIC short packet header DCID(destionation connection ID) field has been modified by an attacker, how to detect this change or fail the AEAD decryption when using aes_gcm_dec_128()?
For BoringSSL, its AES_128_GCM method EVP_AEAD_CTX_open() returns one on success and zero otherwise. So if it returns 0, then the AEAD decryption failed.
isa-l_crypto-2.24.0/include/aes_gcm.h
/**

@brief GCM-AES Decryption using 128 bit keys

@requires SSE4.1 and AESNI
*/
void aes_gcm_dec_128(
const struct gcm_key_data *key_data,   //!< GCM expanded key data
struct gcm_context_data *context_data, //!< GCM operation context data
uint8_t *out,         //!< Plaintext output. Decrypt in-place is allowed
uint8_t const *in,    //!< Ciphertext input
uint64_t len,         //!< Length of data in Bytes for decryption
uint8_t *iv,          //!< iv pointer to 12 byte IV structure.
//!< Internally, library concates 0x00000001 value to it.
uint8_t const *aad,   //!< Additional Authentication Data (AAD)
uint64_t aad_len,     //!< Length of AAD
uint8_t *auth_tag,    //!< Authenticated Tag output
uint64_t auth_tag_len //!< Authenticated Tag Length in bytes (must be a multiple of 4 bytes).
//!< Valid values are 16 (most likely), 12 or 8
);

OK. One can compare the aes_gcm_dec_128()'s output authentication tag against the original authentication tag carried in the received packet to check if the decryption has succeeded.
if (check_data(aead_decrypted_gcm_tag, ciphertext + plaintext_length, MAX_TAG_LEN, "auth tag"))  {
// decryption has failed
}


Duplicate recipe and variable override order in imports is backwards

When duplicate recipes are in the same module, the later one overrides the earlier one:
set allow-duplicate-recipes

foo:

foo:
  echo winner

When they are in imports, because just uses a stack to process imports, the duplicate in the earlier module will win, because it will be processed last:
# a.just
foo:
  echo winner

# b.just
foo:

# justfile
import 'a.just'
import 'b.just'

This was discovered by @redsun82 in #2523.
This is not great behavior, and pretty clearly a bug. I'm not sure, but I don't think we ever considered this case when designing either imports or allow-duplicate-recipes. (@neunenak do you have any recollection of this? I'm thinking that we just didn't notice it.)
just has a very strong backwards compatibility guarantee, but this is definitely a bug and should probably be fixed.
However, I feel like there are probably a bunch of existing justfiles that rely on this behavior, and they're likely especially complicated, so such a bug fix could be disruptive.
The most non-disruptive way to fix it would be:

Add a setting which opts into the new behavior
Print a warning if a justfile doesn't opt in to the new behavior and doing so would change which recipes are defined
Elevate the warning in 2 to an error
After some suitably long period of time, change the default to the new behavior, and make the setting a no-op

We could also add a setting which opts into the new behavior, and then wait and see if it's worth actually changing the default behavior.

No tests break when we use the stack like a queue:
while !stack.is_empty() {
  let ast = stack.remove(0);
  …
}

So we probably just didn't consider this.

This is not great behavior, and pretty clearly a bug. I'm not sure, but I don't think we ever considered this case when designing either imports or allow-duplicate-recipes. (@neunenak do you have any recollection of this? I'm thinking that we just didn't notice it.)

Back when this feature was called include and was experimental, I remember proposing that the semantics of a justfile with includes should always be identical to that of a justfile that had the literal contents of the included justfile copy-pasted in place of the include line. That principle would imply that this should definitely be considered a just bug, although yeah this is probably something that just slipped in as a result of using a stack for import processing that no one thought to explicitly test for.
I wonder if there are other weird semantics that result from using a stack for import processing in this way.


Jasmine Tests Failure

Nginx, Windows 7, Mozilla Firefox 10
Full useragent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0) Gecko/20100101 Firefox/10.0
SpecRunner.html: 9 specs, 3 failures
should parse / and add endmarker
Expected '\/$' to equal '/$'.

should parse basic route and leave untouched
Expected '\/category$' to equal '/category$'.

should parse basic named identifier in position 0
Expected '\/([^\/.\\]+)$' to equal '/([^/.\\]+)$'.
In google chrome: 9 specs, 0 failures

Thanks - will get on to this now.


Deployment Fails with Code Deserialization Error

Describe the bug
Attempts to publish or upgrade a Move package on Porto Testnet result in deserialization failure (CODE_DESERIALIZATION_ERROR).
To Reproduce

Initialize a Move project: aptos move init
add a module
Publish the package using aptos move publish or deploy via object.

{
  "Error": "Simulation failed with status: CODE_DESERIALIZATION_ERROR\nExecution failed with message: Backtrace: Backtrace [\n    { fn: \"move_binary_format::errors::PartialVMError::finish\" },\n    { fn: \"aptos_vm::aptos_vm::AptosVM::deserialize_module_bundle\" },\n    { fn: \"aptos_vm::aptos_vm::AptosVM::resolve_pending_code_publish\" },\n    { fn: \"aptos_vm::aptos_vm::AptosVM::execute_script_or_entry_function\" },\n    { fn: \"aptos_vm::aptos_vm::AptosSimulationVM::create_vm_and_simulate_signed_transaction\" },\n    { fn: \"aptos_api::transactions::TransactionsApi::simulate\" },\n    { fn: \"aptos_api::transactions::TransactionsApi::simulate_transaction::{{closure}}::{{closure}}\" },\n    { fn: \"<tracing::instrument::Instrumented<T> as core::future::future::Future>::poll\" },\n    { fn: \"tokio::runtime::task::core::Core<T,S>::poll\" },\n    { fn: \"tokio::runtime::task::harness::Harness<T,S>::poll\" },\n    { fn: \"tokio::runtime::blocking::pool::Inner::run\" },\n    { fn: \"std::sys_common::backtrace::__rust_begin_short_backtrace\" },\n    { fn: \"core::ops::function::FnOnce::call_once{{vtable.shim}}\" },\n    { fn: \"std::sys::pal::unix::thread::Thread::new::thread_start\" },\n    { fn: \"start_thread\" },\n    { fn: \"__GI___clone\" },\n]"
}

Expected behavior
The package should deploy successfully, as it does on Aptos devnet/testnet/mainnet.
Desktop (please complete the following information):

OS: macOS Sequoia
Aptos CLI: v4.2.6

Additional context

both publish and upgrade result in the same error

Also the same issue.
I've tried the aptos-framework with rev=main, rev=aptos-framework-v1.20.0, but no luck.
Desktop:
OS: macOS Sequoia
Aptos CLI: v4.2.6

Anyone experiencing this, can you try with Aptos CLI 3.5.1?

Is there any workaround to resolve this without having to downgrade?

Anyone experiencing this, can you try with Aptos CLI 3.5.1?

for Mac brew:
Warning: No available formula with the name<EMAIL_ADDRESS>==> Searching for similarly named formulae and casks...
Error: No formulae or casks found for<EMAIL_ADDRESS>

So I managed to deploy by making the following changes:

Used Movement CLI instead of Aptos CLI, this will enforce the use of Aptos CLI v3.5.0.
Updated Move.toml by replacing:[dependencies.AptosFramework]
git = "https://github.com/aptos-labs/aptos-core.git"
rev = "main"
subdir = "aptos-move/framework/aptos-framework"

with:
[dependencies.AptosFramework]
git = "https://github.com/movementlabsxyz/aptos-core.git"
rev = "movement"
subdir = "aptos-move/framework/aptos-framework"
Refactored the configuration directory from .aptos to .movement.

Refactor the config directory .aptos to .movement.

I was able to deploy after following these steps. Just be aware that any feature beyond v3.5.0 won't be available.


[ts] Type '0' cannot be used to index type 'T'.

Everything seems to work, but i get this error on propToQuery param:
[ts] Type '0' cannot be used to index type 'T'.
But type checking works as i want it to work when i call this method(i can pass only string which is equal to keys of that array element).
 checkResponse<T>(response: { [p: string]: string }[] | T, propToQuery: keyof T[0],  error = ID_ERRORS.BACKEND)
  {
    if (response[0][propToQuery] === "ERROR") throw new Error(error);
    else return response as T;
  }

Expected behavior:
No error?
Actual behavior:
Visual Studio Code says there is an error.

How is the shape of T? Or how you would expect the shape of T? Cause, the shape I can infer as human is:
interface IResponse extends Array<{ [key: string]: string }> {}

If that is, then you should mark your response as such.
interface IResponse extends Array<{ [key: string]: string }> {

}

function checkResponse<T extends IResponse>(
    response: T,
    propToQuery: keyof T[0],
    error = ID_ERRORS.BACKEND
) {
    if (response[0][propToQuery] === "ERROR") throw new Error(error);
    else return response as T;
}

Yeah, T needs to be constrained to a type with a property named 0, or have a numeric or string index signature.

Thanks, now i understand, yep T is always an array of objects, but objects are also always different,
if i don't want to create an interface, essentially in this specific case i can go even with this:
function checkResponse<T extends any[]>(
    response: T,
    propToQuery: keyof T[0],
    error = ID_ERRORS.BACKEND
) {
    if (response[0][propToQuery] === "ERROR") throw new Error(error);
    else return response as T;
}


[Intel MKL]: Fixing AVX Performance Issue

This PR fixes the MKL performance on machines with AVX instruction set by using some functionality from MKL binary version. Also, a new config option was added. If that option is used, only MKL-DNN open source lib will be used, without depending on MKL binary version.

Can you look at the build failures?

@martinwicke sorry, there was a file missing from this PR. Can you re-run the test?

I think you have to export build_defs.bzl in your BUILD file?

@martinwicke I did.

Ah, never mind. The license check failed. It is there to ensure that for each third_party package we depend on which requires we include the license in the distribution, we actually include the license in the distribution. MKL-DNN may have a license that falls in that category? In that case, the fix would be to include the license in the deps for the pip package.
@yifeif can you correct me or fill in details?

Yea we include the licenses for the third party packages we depends on.
Missing the licenses for the following external dependencies: //third_party/mkl_dnn
Mind adding the license to the following targets? https://github.com/tensorflow/tensorflow/blob/master/tensorflow/tools/pip_package/BUILD#L123
https://github.com/tensorflow/tensorflow/blob/master/tensorflow/tools/lib_package/BUILD#L111
and
https://github.com/tensorflow/tensorflow/blob/master/tensorflow/tools/lib_package/BUILD#L153

Thanks for the info @martinwicke and @yifeif . I made the change.

@yifeif it is still failing after adding the license. I am confused why the error message says "Please remove the licenses for the following external dependencies:
@mkl_dnn//". Any idea?

Thanks for the commit @mahmoud-abuzaina. Left a comment inline.

@martinwicke the tests seem to be passing now. Can we merge it?

@yifeif is copybara import stuck? It's been a long time since the label was applied...

@martinwicke it looks like all tests are passing now. Maybe we can merge this.

hi @mahmoud-abuzaina sorry for the delay, I'm working on bring this change in internally. Once it gets submitted, it will get merged. Will ping back if anything comes up. Thanks!

Thank you!


x4plus vs x4plus_netD

Hello,
thank you for this amazing tool.
May I ask you what is the difference between RealESRGAN_x4plus and RealESRGAN_x4plus_netD?

RealESRGAN_x4plus_netD is the discriminator, while RealESRGAN_x4plus is the generator/restorer.
RealESRGAN_x4plus_netD cannot be used for restoration but for someone that wants to fine-tune RealESRGAN_x4plus with their own data

Thank you!


Extra spaces are not removed

In the following example rustfmt is not removing the extra spaces in all the lines
fn main() {
    const TEST: [&str;    1]     =    [
                "asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfsdaasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf"
         ];
}

I don't see any reason why not.

Thanks for the report, but I think this is a duplicate of #4403

Ah, thats true :+1:  I'll close this then.

Thank you!


Release v2.5.0

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

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

@conda-forge-admin, please rerender

I will. Please wait with the merge until then, if possible.


Plot styling

Currently, the plots are made with the default mpl settings. I'd like to discuss the styling of figures to improve their appearance.

@RemDelaporteMathurin, for the D in damaged W case. What do you think of making a temporal diagram such as (sorry for the ugly power point sketch):

We could show only 3 D inventory profiles at t=6h, 48h, 100h. These profiles could be set above the temporal dependence

This sounds like a great idea! are you planning on providing the other profiles (2.5h, 23h, 30h, 70h) as an appendix or something?

I don't know. We can discuss. I was thinking of smth like this:

This is very nice!


Rancher CLI on Windows partially not worked

Rancher Version:
v1.2.2
Docker Version:
1.12.5
OS and where are the hosts located? (cloud, bare metal, etc):
VPS
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)
single node
Environment Type: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
Steps to Reproduce:
rancher exec --debug -it 1s218 bash
Results:
FATA[0001] listen unix C:\Users\Shandy\AppData\Local\Temp\docker-sock234811611: socket: An address incompatible with the requested protocol was used.
Expected:
Exec in container on remote host.
Hi,
Windows 10 Pro, docker for windows (hyper-v), native docker client, latest rancher cli (0.4.1)
Exec command as example, all rancher docker commands have same behavior.
I tried on both windows shell: git bash & powershell.
It seems problem is here:

https://github.com/rancher/cli/blob/master/cmd/docker.go#L113
https://github.com/rancher/rancher-docker-api-proxy/blob/master/server.go#L43

Sorry found dublicate issue https://github.com/rancher/rancher/issues/6949 But I provided more details )

To add some additional info, this is due to windows currently being fundamentally incompatible with unix sockets. Until someone comes up with a translation layer for winsock<->unix, we wont see these features working.
Also, before anyone says "But docker for windows works just fine", note that the windows version of docker is a bit of a hack and is just used to talk to a real docker daemon in a vbox/hyperv virtual machine.

+1

So, with last windows 10 update (creators update) I found way to work "rancher exec" and so on:

update docker to latest (I used 17.03)
install latest WSL (Bash on Ubuntu) and go to bash
download Rancher CLI for linux x64
Set up Racnher CLI config & run rancher exec
profit!!!

On Windows binary is same fail result:

listen unix C:\Users\Shandy\AppData\Local\Temp\docker-sock746830959: socket: An address incompatible with the requested protocol was used.

I think it work on "Bash on Ubuntu" because docker server now can access via TCP: "docker -H tcp://localhost:2375 info" in both console (win + ubuntu).
So instead of "translation layer for winsock<->unix" I propose change logic connect to docker server in Racher CLI for win platform, it can be just fallback after trying connect via socket, try connect via TCP.

I posted a workaround in the ticket linked by @shandyDev https://github.com/rancher/rancher/issues/6949#issuecomment-323134373
TL;DR: Use the rancher/cli Docker container to run commands for you in Windows:
docker run -e RANCHER_URL=<URL> -e RANCHER_ACCESS_KEY=<KEY> -e RANCHER_SECRET_KEY=<SECRET> -it rancher/cli:latest <CMD>

Tested with rancher/server:v1.6.15-rc3 with rancher CLI v0.6.8-rc2.
In the rancher/server:v1.6.15-rc3, Rancher CLI can work on windows.


Fall back to CPU in small FRI.

This change is

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#840  👈
#838
#827
dev

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @alonh5 and the rest of your teammates on  Graphite

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

Project coverage is 92.01%. Comparing base (1a9755a) to head (a60c629).

Additional details and impacted files
@@                                 Coverage Diff                                 @@
##           09-17-fall_back_to_cpu_in_small_constraint_eval     #840      +/-   ##
===================================================================================
+ Coverage                                            92.00%   92.01%   +0.01%
===================================================================================
  Files                                                   90       90
  Lines                                                12202    12212      +10
  Branches                                             12202    12212      +10
===================================================================================
+ Hits                                                 11226    11237      +11
  Misses                                                 869      869
+ Partials                                               107      106       -1

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

Merge activity

Sep 24, 4:47 AM EDT: @alonh5 started a stack merge that includes this pull request via Graphite.


TS2307: Cannot find module when pure ESM packages with Vue SFC files

{
  "name": "test-a",
  "version": "1.0.0",
  "exports": {
    ".": "./index.js",
    "./components/date-picker": "./components/date-picker/index.vue"
  }
}

// GET TS2307 error
import DatePicker from 'test-a/components/date-picker'

Repro case:
https://github.com/yoyo930021/volar-pure-esm-project-bug/blob/main/src/app.vue#L17

Same issue

@yoyo930021, change the path to:
import DatePicker from 'test-a/components/date-picker/index.vue'

Since you are using an SFC, maybe you don't need a directory for that component?

@yoyo930021, change the path to:
import DatePicker from 'test-a/components/date-picker/index.vue'

Since you are using an SFC, maybe you don't need a directory for that component?

This is unsafe code. It is broken when package internal changed.
It also does not meet the ESM.

@yoyo930021, change the path to:
import DatePicker from 'test-a/components/date-picker/index.vue'

Since you are using an SFC, maybe you don't need a directory for that component?

This is unsafe code. It is broken when package internal changed. It also does not meet the ESM.

Then why resolve to the index file in your package.json?
{
  "name": "test-a",
  "version": "1.0.0",
  "exports": {
    ".": "./index.js",
    "./components/date-picker": "./components/date-picker/index.vue"
  }
}

@yoyo930021, change the path to:
import DatePicker from 'test-a/components/date-picker/index.vue'

Since you are using an SFC, maybe you don't need a directory for that component?

This is unsafe code. It is broken when package internal changed. It also does not meet the ESM.

Then why resolve to the index file in your package.json?
{
  "name": "test-a",
  "version": "1.0.0",
  "exports": {
    ".": "./index.js",
    "./components/date-picker": "./components/date-picker/index.vue"
  }
}

It have same problem. They are the temp workrounds.

Also, even it's a Vue2 documentation using exports to publish SFC ready versions of your components is the documented way

The repro case seems to be invalid as this setup does not work even in .ts files.
Steps to reproduce:

Create test-a/components/date-picker/foo.ts with empty export export { };.

Update test-a/package.json

{
  "name": "test-a",
  "version": "1.0.0",
  "exports": {
    ".": "./index.js",
+    "./components/date-picker2": "./components/date-picker/foo",
    "./components/date-picker": "./components/date-picker/index.vue"
  }
}

Add import {} from 'test-a/components/date-picker2' to src/main.ts, test-a/components/date-picker2 failed to resolve to test-a/components/date-picker/foo.ts.

Closed as this is expected behavior.


enable schema check for ticket ETL-8753

Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[ ] My PR addresses the following Gobblin JIRA issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"

https://issues.apache.org/jira/browse/GOBBLIN-726

Description

[ ] Here are some details about my PR, including screenshots (if applicable):
During the process of derived data deployment, we need to verify that data schema matches deployed schema. Each distcp mapper will first read the schema of the file to be copied, and abort if the file schema does not match the expected schema.

Tests

[ ] My PR adds the following unit tests OR does not need testing for this extremely good reason:
My PR adds the checkSchemaTest in EmbeddedGobblinDistcpTest to test the function when schema is right or wrong,.

Commits

[ ] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

@ibuenros @autumnust can you take a look at this?


Remove NSP checks from Travis

These are no longer necessary as Snyk is being used for security checks on PR's.

LGTM


Add unit tests(mostly assertions) for retrieval scripts and tags

Done for the following -

tags
editorials
invalid handle
contest rating data
download submission

Pending -

submission retrieval


Add support for permalinks

The slug/URL for a post currently changes as the title changes which can make it inconvenient for linking to a post; If a post's title is changed at some point the old link is broken.
To solve this, the frontend should have a route such as /permalink/[id] which then fetches the appropriate API endpoint. The backend needs only minor tweaking in terms of adding a cache and endpoint since a getPostByID function is already implemented.
The frontend should have a "share" button which could then display a list of options. For right now it will only need to include copying a permalink, but in the future, it could also include other options like sharing on twitter or Reddit.

https://nextjs.org/docs/api-reference/next.config.js/redirects


Be able to change the property name of request

Instead of using req.universakCookies I'd like to be able to use req.cookies.
So, I could use it like that:
app.use(universalCookieMiddleware('cookies'));

app.get('/', (req, res) => {
req.cookies.get('foo'); // instead of req.universalCookies.get('foo')
});

I'm not sure I see a reason to be able to rename a variable name. I made sure it will not conflict with anything else. Is there a use-case where this would be problematic?


Using eslintrc from the project

https://github.com/feross/standard/issues/351#issuecomment-170360310
It'd be nice for standard-engine to pick up your local .eslintrc. You can set your eslintrc to this, and customize it as you see fit.
{
  "extends": ["standard", "standard-react"]
}

Rationale:

be able to use (or not use) standard-react (ouch)
be able to use semistandard (or similar)
you can disable rules if you really really want to
use standard-engine (which is much better than eslint's own CLI, imho!) with other eslint rules
use tape-standard, mocha-standard and similar with other eslint rules

As a bonus, maybe it can be defined in package.json as an alternative (much like babel lets you define options in .babelrc and package.json/babel)

Could this be built as a separate CLI tool on top of standard-engine? A lack of configuration/options/deviation was one of the original goals of standard, and allowing everything to be overridden by a local .eslintrc may undermine that goal.
It could also get confusing if someone has an old .eslintrc file in their project and things start acting strange (I guess this would be the "breaking" part).
I do like this idea though! We could add it as a configurable option to standard-engine but I don't know how keen @feross and others would be on adding it to standard.

Is this a simple matter of allowing the user to set the useEslintrc eslint option? If that's all it is, I don't see the harm in letting users of standard-engine set it.
That said, it was an explicit decision to not do this for standard itself, as this would make standard behave differently on different machines, if a user keeps their code in ~/code and a config file in ~/.eslintrc, which actually bit me once.
I think the solution that standard will offer for this is to just allow rule overrides directly in package.json for those who just need to change a rule or two for their project. But that's separate from this issue.


Prompt for the generator name

Is it possible to prompt the user for the generator name?
I actually can't figure out to make it work:
_templates/app/new/index.js:
module.exports = {
  prompt: async ({ prompter, args }) => {
    let prompt
    prompt = await prompter.prompt({
      type: 'input',
      name: 'name',
      initial: args.name,
      message: `Your app name`
    })
    return prompt
 })
}

When executing it from the console, I get:
$ hygen app new
? Your app name > john
x   exists: packages/unnamed/.babelrc. Overwrite? (y/N)

Expected name: john
Actual name: unnamed
Any help would be very much appreciated :)

my bad... its was as a matter of fact a very simple matter: the above code snippet works. What didn't was overriding the prompt variable again and again, thus losing track of its previously-set key/value pairs.
TL;DR: nevermind, my bad


Update how-to.md for HNCConfig schema change

Update how-to.md to reflect both kubectl hns config set-type and kubectl hns config set-resource before and after HNC v0.6,
and schema/field changes.
Fixes #1207

/assign @adrianludwin
/assign @GinnyJI
/assign @rjbez17
The initial work in my workstation was lost due to tech issue so this doc change PR is done on github.

Nice work!


Request to make full url from pom

Is your feature request related to a problem? Please describe.
I used DepedencyCheck tool to analyze Jar file. DependencyCheck must be a very useful tool for me.
But the url result from pom is not full link,
Maybe if the url is a link to github, it seems that only the back of the address, not the full link, comes out like this.

Maybe... I think that the full url will be 'https://github.com/googleapis/api-common-java'.
Describe the solution you'd like
I think it would be more useful if you could derive the result with full url.
Namely, the url from pom is

AS-IS

url : googleapis/api-common-java

TO-BE

url : https://github.com/googleapis/api-common-java

The url entry that you reference is from the evidences section which is just showing you which parts of the dependency where used in the fuzzy matching. It properly shows you what part of the URL as discovered in the pom was used as an evidence to try and find a matching 'Product' and 'Vendor'.
None of the items of the evidences section is meant to give you a way to navigate to sources/artifacts/whatnot. They are only meant as informational items so that, in case of false-negatives you can take a look in the evidences if there is something identifying that you can use as a hook to use for a Hint in order to make DependencyCheck properly find the corresponding CPE.

I understand what you mean.
I inquired because I wanted to check the source(web link) of the open source through the full url result and move it right away using the url.
Thank you for your detailed explanation.

We could extract the SCM url and add it to the reports.

@jeremylong
Thank you for your response.
Where can I get the SCM url in the report?  If you have an explanation or document link, please let me know.
If it's not currently extractable, is it possible to fix it?

@jeremylong
Is there any update or progress for SCM url?

Nope - we accept PRs

@jeremylong
Should I wait for your PR? or should I create PR myself?
If it's the latter, could you let me know how do I get access your repo to create PR?

@bjk7119 👋
Everybody is allowed to contribute to DependencyCheck and we would love you to else us. 🤗
You can suggest a change by forking the DependencyCheck repository, working on your change on a branch of your repository, then opening a pull request of your change on DependencyCheck master branch.
If you are not comfortable with GitHub and open-source contributions, you can find some documentation here: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks
If you are facing troubles with DependencyCheck project setup, you may ask for help here after providing details about your issue. 🙂

Thank you for the explanation. @nhumblot
I will fork it and create PR. 🙂

We could extract the SCM url and add it to the reports.

Is there any idea to extract SCM url and add it to the report?
I am asking you because I think it would be better to listen to @jeremylong's thoughts before I contribute.


Add new maintainers to fortify-plugin

The existing maintainer 'akaryakina' is currently taking leave.
Add the following new maintainers:

young-s-park
hiro0824

Description

Submitter checklist for adding or changing permissions

Always

[ ] Add link to plugin/component Git repository in description above

For a newly hosted plugin only

[ ] Add link to resolved HOSTING issue in description above

For a new permissions file only

[ ] Make sure the file is created in permissions/ directory
[ ] artifactId (pom.xml) is used for name (permissions YAML file).
[ ] groupId / artifactId (pom.xml) are correctly represented in path (permissions YAML file)
[ ] Check that the file is named plugin-${artifactId}.yml for plugins

When adding new uploaders (this includes newly created permissions files)

[ ] Make sure to @mention an existing maintainer to confirm the permissions request, if applicable
[ ] Use the Jenkins community (LDAP) account name in the YAML file, not the GitHub account name
[ ] Make sure to @mention the users being added so their GitHub account names are known if they require GitHub merge access (see below).
[ ] All newly added users have logged in to Artifactory at least once

Reviewer checklist (not for requesters!)

[ ] Check this if newly added person also needs to be given merge permission to the GitHub repo (please @ the people/person with their GitHub username in this issue as well). If needed, it can be done using an IRC Bot command
[ ] Check that the $pluginId Developers team has Admin permissions while granting the access.
[ ] In the case of plugin adoption, ensure that the Jenkins Jira default assignee is either removed or changed to the new maintainer.
[ ] If security contacts are changed (this includes add/remove), ping the security officer (currently @daniel-beck) in this pull request. If an email contact is changed, wait for approval from the security officer.

There are IRC Bot commands for it

Please fill in the template and follow the instructions. We need a sign-off from an existing maintainer to do this.

Please fill in the template and follow the instructions. We need a sign-off from an existing maintainer to do this.
Could you please review the description? If there is something incorrect, please correct me. Also the existing maintainer is now taking maternity leave, so I'm not sure if she can afford to check this...

Hi everyone, thank you for looking at the request. I am the current maintainer and I do approve both Hiro and Young to be able to release the plugin since I'm on maternity leave till February next year.

Please fill in the template and follow the instructions. We need a sign-off from an existing maintainer to do this.
@slide The current maintainer has commented on this pull request. Is there anything else that needs to be done to get Hiro and myself added as maintainers?


Does deepstream sdk support RTX2080/2080Ti?

Please let me know if the deepstream sdk supports 2080Ti and Titan 2080Ti GPUs

@Zeus916 In my testing I have found that deepstream sdk works on 2080Ti and Titan Rtx Gpus. Also how are you?


Auto paste chuncks?

Hey, can you make a script that Auto paste the chuncks to chatGPT??

Hello. That would be great... but I need to figure out how to do it if they are on different tabs... I would need to do some research. But I'm already preparing a version of the chatgpt-prompt-splitter as a Chrome extension, where it will be more accessible to copy+paste automatically... let's see... I'll publish if I make it work. Thanks for your interest!

No, sorry, time has been short on my side. At this point I would also do a good search, see if no one else implemented it already.


ng build --prod fails

Please provide us with the following information:

OS?

Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
Linux mint 17.3

Versions.

Please run ng --version. If there's nothing outputted, please run in a Terminal: node --version and paste the result here:

@angular/cli: 1.0.0-beta.31
node: 6.9.5
os: linux x64
@angular/common: 2.4.7
@angular/compiler: 2.4.7
@angular/core: 2.4.7
@angular/forms: 2.4.7
@angular/http: 2.4.7
@angular/platform-browser: 2.4.7
@angular/platform-browser-dynamic: 2.4.7
@angular/router: 3.4.7
@angular/cli: 1.0.0-beta.31
@angular/compiler-cli: 2.4.7
@ngtools/webpack: 1.2.9

Repro steps.

Was this an app that wasn't created using the CLI? What change did you do on your code? etc.
App was created with CLI, I updated it from beta.28 to beta.31

The log given by the failure.

Normally this include a stack trace and some more information.

Hash: 2a99f13b5b62365e1c82
Time: 22299ms
chunk    {0} scripts.eba1fd04cb853331827e.bundle.js (scripts) 1.59 MB {4} [initial] [rendered]
chunk    {1} styles.7fa2a0ee5b161732eff6.bundle.css (styles) 652 bytes {4} [initial] [rendered]
chunk    {2} main.83c4de0f806812b7af3c.bundle.js (main) 1.47 kB {3} [initial] [rendered]
chunk    {3} vendor.3c9407a92164ae98a7fe.bundle.js (vendor) 1.06 MB [initial] [rendered]
chunk    {4} inline.c4d016c6bd1a57a97f49.bundle.js (inline) 0 bytes [entry] [rendered]

ERROR in this._input.charCodeAt is not a function

ERROR in ./src/main.ts
Module not found: Error: Can't resolve './$$_gendir/app/app.module.ngfactory' in '/home/vs/Work/GoFactTables/GoFactFrontend/src'
 @ ./src/main.ts 5:0-74
 @ multi ./src/main.ts

Mention any other details that might be useful.

Thanks! We'll be in touch soon.

Same issue for me (also updated to 1.0.0-beta.31), except the error is different:
ERROR in Can't resolve all parameters for provideLocationStrategy in<EMAIL_ADDRESS>([object Object], ?, [object Object]).

Error doesn't appear when using command with aot turned off (--aot=false). Is there any way to check what goes wrong with aot?

Closing issue. The problem was in application itself, there was a component with template loaded as require(...) . Build went ok when I replaced this template with inline one.


Add subscription test case and Azure boot up case

Signed-off-by: Yuxin Sun<EMAIL_ADDRESS>This pull request includes:

[x] adequate testing for the new functionality or fixed issue
[ ] adequate documentation informing people about the change such as

[ ] create a file in news/unreleased directory if this change should be mentioned in the release news
[ ] submit a PR for the guides repository if this PR changed any behavior described there: https://www.osbuild.org/guides/

Hi @atodorov ,
I've update the script, removed the "dnf install dos2unix" step, because in some branches(e.g. https://gitlab.com/osbuild/ci/osbuild-composer/-/jobs/1350313301 ) it cannot get available repo. Perhaps because this RHEL version has not been released yet and no published repo for that.
+ ssh -oStrictHostKeyChecking=no -i /tmp/tmp.iCaR9Uweoz/id_azure<EMAIL_ADDRESS>sudo dnf -y install dos2unix
Updating Subscription Management repositories.
Failed to set locale, defaulting to C.UTF-8
Error: There are no enabled repositories in "/etc/yum.repos.d", "/etc/yum/repos.d", "/etc/distro.repos.d".

I don't know now to check whether the OS is released and I think the package installation check is not so important. It'll be enough to just verify the system is subscribed. What's your opinion about that? Thanks!

Hi @atodorov ,
I've update the script, removed the "dnf install dos2unix" step, because in some branches(e.g. https://gitlab.com/osbuild/ci/osbuild-composer/-/jobs/1350313301 ) it cannot get available repo. Perhaps because this RHEL version has not been released yet and no published repo for that.
+ ssh -oStrictHostKeyChecking=no -i /tmp/tmp.iCaR9Uweoz/id_azure<EMAIL_ADDRESS>sudo dnf -y install dos2unix
Updating Subscription Management repositories.
Failed to set locale, defaulting to C.UTF-8
Error: There are no enabled repositories in "/etc/yum.repos.d", "/etc/yum/repos.d", "/etc/distro.repos.d".

That's running on a rhel-8-x86_64 runner which is a released distro, 8.3 at this time. Something went wrong during subscription/repo enablement. Not sure what.

Hi @atodorov ,
I've update the script, removed the "dnf install dos2unix" step, because in some branches(e.g. https://gitlab.com/osbuild/ci/osbuild-composer/-/jobs/1350313301 ) it cannot get available repo. Perhaps because this RHEL version has not been released yet and no published repo for that.
+ ssh -oStrictHostKeyChecking=no -i /tmp/tmp.iCaR9Uweoz/id_azure<EMAIL_ADDRESS>sudo dnf -y install dos2unix
Updating Subscription Management repositories.
Failed to set locale, defaulting to C.UTF-8
Error: There are no enabled repositories in "/etc/yum.repos.d", "/etc/yum/repos.d", "/etc/distro.repos.d".

That's running on a rhel-8-x86_64 runner which is a released distro, 8.3 at this time. Something went wrong during subscription/repo enablement. Not sure what.

Hi @atodorov ,
I've update the script, removed the "dnf install dos2unix" step, because in some branches(e.g. https://gitlab.com/osbuild/ci/osbuild-composer/-/jobs/1350313301 ) it cannot get available repo. Perhaps because this RHEL version has not been released yet and no published repo for that.
+ ssh -oStrictHostKeyChecking=no -i /tmp/tmp.iCaR9Uweoz/id_azure<EMAIL_ADDRESS>sudo dnf -y install dos2unix
Updating Subscription Management repositories.
Failed to set locale, defaulting to C.UTF-8
Error: There are no enabled repositories in "/etc/yum.repos.d", "/etc/yum/repos.d", "/etc/distro.repos.d".

That's running on a rhel-8-x86_64 runner which is a released distro, 8.3 at this time. Something went wrong during subscription/repo enablement. Not sure what.

Hi @atodorov , do you think we still need this "package installation check" step? If not, we can just skip this issue. Thanks!

The previous job that you linked failed because of the failing dnf install which reveals some issues with this job. Could be the runner, could be a network hiccup, IDK. The point is that without this failure we would never know about this. IMO the dnf install command should be present.

Hi @atodorov , do you think we still need this "package installation check" step? If not, we can just skip this issue. Thanks!

The previous job that you linked failed because of the failing dnf install which reveals some issues with this job. Could be the runner, could be a network hiccup, IDK. The point is that without this failure we would never know about this. IMO the dnf install command should be present.

Thanks Alex! Add it back. And try to auto-attach if no repo.
Besides, I also find some unexpected failures:

Sometimes the VM is not subscribed in 300s. See https://gitlab.com/osbuild/ci/osbuild-composer/-/jobs/1351080822 and https://gitlab.com/osbuild/ci/osbuild-composer/-/jobs/1351080820.
Sometimes the "subscription-manager unregister" failed. See https://gitlab.com/osbuild/ci/osbuild-composer/-/jobs/1351080825

+ ssh -oStrictHostKeyChecking=no -i ./keypair.pem<EMAIL_ADDRESS>sudo subscription-manager unregister
Unregistering from: subscription.rhsm.[MASKED]:443/subscription
Remote server error. Please check the connection details, or see /var/log/rhsm/rhsm.log for more information.

Sometimes the Azure VM fails to be created. Error details:

{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":[{"code":"OSProvisioningInternalError","message":"OS Provisioning failed for VM 'vm-b0b2d348-e5f6-4e00-b3df-881386dc6bec' due to an internal error: [ProtocolError] [CopyOvfEnv] Error mounting dvd: [OSUtilError] Failed to mount dvd device\nInner error: [mount -o ro -t udf,iso9660 /dev/sr0 /mnt/cdrom/secure] returned 32: mount: /mnt/cdrom/secure: no medium found on /dev/sr0.\n."}]}

It looks like an error from Azure side but I've never met it in my own testing. So I change a VM size to see if it happens again.

Hi @atodorov ,
Again I see there's no repo for RHEL-8.3: (https://gitlab.com/osbuild/ci/osbuild-composer/-/jobs/1353875306)
+ ssh -oStrictHostKeyChecking=no -i ./keypair.pem<EMAIL_ADDRESS>sudo subscription-manager attach --auto
Installed Product Current Status:
Product Name: Red Hat Enterprise Linux for x86_64 Beta
Status:       Not Subscribed
Unable to find available subscriptions for all your installed products.

I guess the problem is that the system is identified as a "Beta". Not sure why it's beta. I've tried that created a RHEL-8.3 VM from Azure Marketplace and register with this RHSM account, it can get repo.

1. Sometimes the VM is not subscribed in 300s. See https://gitlab.com/osbuild/ci/osbuild-composer/-/jobs/1351080822 and https://gitlab.com/osbuild/ci/osbuild-composer/-/jobs/1351080820.

FAIL when this happens. Leave it as-is. If we see this happening often then we have to investigate.

2. Sometimes the "subscription-manager unregister" failed. See https://gitlab.com/osbuild/ci/osbuild-composer/-/jobs/1351080825

+ ssh -oStrictHostKeyChecking=no -i ./keypair.pem<EMAIL_ADDRESS>sudo subscription-manager unregister
Unregistering from: subscription.rhsm.[MASKED]:443/subscription
Remote server error. Please check the connection details, or see /var/log/rhsm/rhsm.log for more information.

1. Sometimes the Azure VM fails to be created. Error details:

{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":[{"code":"OSProvisioningInternalError","message":"OS Provisioning failed for VM 'vm-b0b2d348-e5f6-4e00-b3df-881386dc6bec' due to an internal error: [ProtocolError] [CopyOvfEnv] Error mounting dvd: [OSUtilError] Failed to mount dvd device\nInner error: [mount -o ro -t udf,iso9660 /dev/sr0 /mnt/cdrom/secure] returned 32: mount: /mnt/cdrom/secure: no medium found on /dev/sr0.\n."}]}

It looks like an error from Azure side but I've never met it in my own testing. So I change a VM size to see if it happens again.

Hi @atodorov ,
Again I see there's no repo for RHEL-8.3: (https://gitlab.com/osbuild/ci/osbuild-composer/-/jobs/1353875306)
+ ssh -oStrictHostKeyChecking=no -i ./keypair.pem<EMAIL_ADDRESS>sudo subscription-manager attach --auto
Installed Product Current Status:
Product Name: Red Hat Enterprise Linux for x86_64 Beta
Status:       Not Subscribed
Unable to find available subscriptions for all your installed products.

I guess the problem is that the system is identified as a "Beta". Not sure why it's beta. I've tried that created a RHEL-8.3 VM from Azure Marketplace and register with this RHSM account, it can get repo.

CC @ondrejbudai. Any idea what's happening here ?

New update: For Fedora images, skip boot up testing on Azure because of #1479

New update: For Fedora images, skip boot up testing on Azure because of #1479

Reverted. Do not skip now.

Hi @atodorov ,
Again I see there's no repo for RHEL-8.3: (https://gitlab.com/osbuild/ci/osbuild-composer/-/jobs/1353875306)
+ ssh -oStrictHostKeyChecking=no -i ./keypair.pem<EMAIL_ADDRESS>sudo subscription-manager attach --auto
Installed Product Current Status:
Product Name: Red Hat Enterprise Linux for x86_64 Beta
Status:       Not Subscribed
Unable to find available subscriptions for all your installed products.

I guess the problem is that the system is identified as a "Beta". Not sure why it's beta. I've tried that created a RHEL-8.3 VM from Azure Marketplace and register with this RHSM account, it can get repo.

CC @ondrejbudai. Any idea what's happening here ?

Hi @atodorov ,
I retried this job and checked the release version today. It is indeed RHEL-8.4 Beta. That's why it cannot find available subscriptions from CDN server.
[root@vm-0955321c-3e71-4073-b569-9257d249b01f ~]# cat /etc/os-release
NAME="Red Hat Enterprise Linux"
VERSION="8.4 (Ootpa)"
ID="rhel"
ID_LIKE="fedora"
VERSION_ID="8.4"
PLATFORM_ID="platform:el8"
PRETTY_NAME="Red Hat Enterprise Linux 8.4 Beta (Ootpa)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:redhat:enterprise_linux:8.4:beta"
HOME_URL="https://www.redhat.com/"
DOCUMENTATION_URL="https://access.redhat.com/documentation/red_hat_enterprise_linux/8/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"

REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 8"
REDHAT_BUGZILLA_PRODUCT_VERSION=8.4
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="8.4 Beta"

The job is https://gitlab.com/osbuild/ci/osbuild-composer/-/jobs/1360801578

So for the 8.4 runners (soon to be 8.5) - we can't subscribe to CDN b/c there's nothing to subscribe to really. The majority of the times these will be unreleased systems or at times (during the end of a release cycle) we'll be using older systems than what is available.
I'm not sure how to solve this problem ATM. IMO open a Jira ticket for the subscription+nightly part and we can deal with it later. Let's now focus on having all jobs for this PR report PASS so we can merge it.

So for the 8.4 runners (soon to be 8.5) - we can't subscribe to CDN b/c there's nothing to subscribe to really. The majority of the times these will be unreleased systems or at times (during the end of a release cycle) we'll be using older systems than what is available.
I'm not sure how to solve this problem ATM. IMO open a Jira ticket for the subscription+nightly part and we can deal with it later. Let's now focus on having all jobs for this PR report PASS so we can merge it.

Opened a ticket for that: https://issues.redhat.com/browse/COMPOSER-996
And I just updated the case to skip package installation checking in Beta versions.

Rebase to matest main. Testing on Fedora32 has been removed.

Rebased and changed the resource delete order in Azure cleanup due to https://github.com/osbuild/osbuild-composer/issues/1479#issuecomment-865659613

So the rpmrepo snapshot that we're using for Fedora 33 contains WALinuxAgent-<IP_ADDRESS>. If we want a newer one, we need to update the snapshot in test/data/repositories. You can find how to find the repository baseurl here: https://www.osbuild.org/rpmrepo/

Blocked by #1487 .

So for the 8.4 runners (soon to be 8.5) - we can't subscribe to CDN b/c there's nothing to subscribe to really. The majority of the times these will be unreleased systems or at times (during the end of a release cycle) we'll be using older systems than what is available.
I'm not sure how to solve this problem ATM. IMO open a Jira ticket for the subscription+nightly part and we can deal with it later. Let's now focus on having all jobs for this PR report PASS so we can merge it.

Opened a ticket for that: https://issues.redhat.com/browse/COMPOSER-996
And I just updated the case to skip package installation checking in Beta versions.

Revert the skip because the Beta SKU has been added into the test account. Just need to disable all beta repos because they are unreachable. Code has been updated.

Do we even want to run this test on pre-GA RHEL? Image Builder runs on GA RHEL and produces only GA RHEL images. There's definitely some value in testing pre-GA stuff but if it's too weird with subscriptions, I would suggest just dropping it. AFAIK beta repositories are removed shortly after GA.

Do we even want to run this test on pre-GA RHEL? Image Builder runs on GA RHEL and produces only GA RHEL images. There's definitely some value in testing pre-GA stuff but if it's too weird with subscriptions, I would suggest just dropping it. AFAIK beta repositories are removed shortly after GA.

Hi Ondrej,
Actually I'm not quite understand what is the "rhel-8.json" for? Is it for the latest nightly RHEL-8 compose test? Thanks!

Do you mean test/data/repositories/rhel-8.json? These are repositories are used e. g. for test manifests generation, api tests, koji tests, grep -r /usr/share/tests/osbuild-composer/repositories . might help you.

Do we even want to run this test on pre-GA RHEL? Image Builder runs on GA RHEL and produces only GA RHEL images. There's definitely some value in testing pre-GA stuff but if it's too weird with subscriptions, I would suggest just dropping it. AFAIK beta repositories are removed shortly after GA.

Probably not much, let's discuss this on the QE meeting in few days.
OTOH a Beta system already skips the subscription part, that's:
  # Beta image doesn't have available subscription so skip subscription check. See COMPOSER-996
  if [[ "$ID" =~ "rhel" ]] && [[ ! "$pretty_name" =~ 'Beta' ]]; then

so what's the current issue we're trying to resolve then ?

Do you mean test/data/repositories/rhel-8.json? These are repositories are used e. g. for test manifests generation, api tests, koji tests, grep -r /usr/share/tests/osbuild-composer/repositories . might help you.

Thanks Ondrey! I meant to ask that what are the differences between "rhel-8" and "rhel-8.4" branches? It seems that the repos in rhel-8.4.json point to the latest 8.4 development composes. But I've no idea what is "https://rpmrepo.osbuild.org/v1/psi/el8/el8-x86_64-baseos-8.4.0.n-20201108" in rhel-8.json and why we test it. Thanks!

Updated the PR due to the discussion today:
Do not verify package installation in api.sh. Only verify subscription registration in all the images.
There's only 1 concern:
Currently we use the host OS version(ID) to judge if we need to test the subscription registration case in guest image. Due the the previous discussion we know that the host OS and guest OS are not the same. So it'll be better to add an external variable here. But currently it's not a problem because the product ID(rhel/fedora) of the host and guest OS are the same.

Updated the PR due to the discussion today:
Do not verify package installation in api.sh. Only verify subscription registration in all the images.
There's only 1 concern:
Currently we use the host OS version(ID) to judge if we need to test the subscription registration case in guest image. Due the the previous discussion we know that the host OS and guest OS are not the same. So it'll be better to add an external variable here. But currently it's not a problem because the product ID(rhel/fedora) of the host and guest OS are the same.

This is not going to be a practical problem until the time when building cross distro images becomes a supported functionality.

This appeared on Fedora, no? I'm not sure whether we want to run this test on Fedora. I think it doesn't bring much value.

sudo: subscription-manager: command not found
Add subscription-manager to the dependencies in spec file.

 I'd like to debug the CI results myself first and then when it's all passed I'll @you to help review it, to prevent wasting your time :)

This appeared on Fedora, no? I'm not sure whether we want to run this test on Fedora. I think it doesn't bring much value.

That's a side effect of how the matrix is defined.

Hi @atodorov , all the jobs are passed. Could you please help to merge it when available? Thank you so much!

Azure test jobs reported PASS. Merging.


Changelog Request!

Please implement a changelog with deprecation notices in the future.
Thanks!
edit: Such as OAuth2.new to OAuth2.Client.new, and the access token response being returned instead of the body.

Hi @stavro,
I've added a changelog as requested. I have been adding changelogs to the release notes for each release. I'll start adding changes to the changelog and compiling those into release note from now on. Will probably be a better workflow.
Thanks!


Publish the language spec proposals for features released in C# 7.0

The 7.0 language proposal are:

[ ] pattern matching
[ ] local functions
[ ]  out variable declarations
[ ]  throw expressions
[ ] binary literals
[ ] digit separators

When these are published, the page for the -langVersion switch should be updated to point to these new spec documents.


raspbian :Activating cgroup support - failure on x64 Debian Buster platform

Getting a 'raspian is true' failed error when master and nodes are x64 Intel Debian Buster , not ARM, not RaspberryPIs
$ ssh <IP_ADDRESS> uname -a
Linux alfred 4.19.0-10-amd64 #1 SMP Debian 4.19.132-1 (2020-07-24) x86_64 GNU/Linux
....
TASK [download : Download k3s binary x64] ******************************************************************************
Sunday 06 September 2020  00:21:32 -0600 (0:00:00.412)       0:00:05.811 ******
changed: [<IP_ADDRESS>]
changed: [<IP_ADDRESS>]
changed: [<IP_ADDRESS>]
TASK [download : Download k3s binary arm64] ****************************************************************************
Sunday 06 September 2020  00:22:13 -0600 (0:00:41.544)       0:00:47.356 ******
skipping: [<IP_ADDRESS>]
skipping: [<IP_ADDRESS>]
skipping: [<IP_ADDRESS>]
TASK [download : Download k3s binary armhf] ****************************************************************************
Sunday 06 September 2020  00:22:13 -0600 (0:00:00.137)       0:00:47.493 ******
skipping: [<IP_ADDRESS>]
skipping: [<IP_ADDRESS>]
skipping: [<IP_ADDRESS>]
TASK [raspbian : Test for Raspbian] ************************************************************************************
Sunday 06 September 2020  00:22:13 -0600 (0:00:00.177)       0:00:47.671 ******
ok: [<IP_ADDRESS>]
ok: [<IP_ADDRESS>]
ok: [<IP_ADDRESS>]
TASK [raspbian : Activating cgroup support] ****************************************************************************
Sunday 06 September 2020  00:22:14 -0600 (0:00:00.299)       0:00:47.970 ******
fatal: [<IP_ADDRESS>]: FAILED! => {"msg": "The conditional check 'raspbian is true' failed. The error was: template error while templating string: no test named 'true'. String: {% if raspbian is true %} True {% else %} False {% endif %}\n\nThe error appears to have been in '/home/sean/k3s-ansible/roles/raspbian/tasks/main.yml': line 11, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: Activating cgroup support\n  ^ here\n"}
fatal: [<IP_ADDRESS>]: FAILED! => {"msg": "The conditional check 'raspbian is true' failed.
...

As a workaround, I removed:

role: raspbian

Line 9 from site.yml and reran the playbook successfully.  I'm not that strong in ansible but I believe the if statement in the roles/raspbian/tasks/main.yml is incorrectly detecting a RaspberryPi OS for Debian Buster x64

I just experienced this error and fixed it by changing the test case in the raspbian role main.yml file from
- name: Activating cgroup support
  when:
    - raspbian is true

to
- name: Activating cgroup support
  when: raspbian

Raspberry Pi OS cgroup support should now be working.


Self Host Error

Have you read a contributing guide?

[X] I have read CONTRIBUTING.md
[X] I have searched the existing issues and didn't find any that were similar
[X] I have considered creating a pull request with fixes instead of a bug report and want to proceed

Current Behavior
After installing the config and creating a new account, I get a Self Host Error
Expected Behavior
I will get an OK message and working sync
Steps To Reproduce

make start
install EXTERNAL_LISTEN_HOST
make restart

Environment
- OS: Ubuntu 22
- Version: latest

Anything else?
No response

The error is that forced generation of .env is being started, overwriting the changes.
When I deleted the item with env generation, everything worked for me

This is not an error; we're using auto-generation for the .env file.
The necessary changes you need to make should be applied to the .env.override file.
You can find more information about this here https://github.com/anyproto/any-sync-dockercompose/wiki/Configuration

Okay. Maybe it's worth adding information about this to the main ReadMe?


Problem with wireds bots.

Look screenshot:

Important: (I have add all furniture interactor).

Check the interaction_type at Database.

All interaction type its good for all wired furniture.
Dont work.


--env parameter does not list multidev sites on prompt

If you leave off the --env param, dev, test, and live will be listed, but it leaves off the multidev sites.
Example: This site has several multidev sites:
[2015-11-18 18:03:47] [info] An update to Terminus is available. Please update to 0.9.3.
    version: '0.9.3'
  1. dev
  2. test
  3. live

Choose environment: ```

Nice catch! I'll fix this up right away.

Is this implemented now, or still in some dev code? I still don't find any way to clear caches or do anything with multdevs using terminus.
I tried updating terminus using the composer install command on readme


[10.x] Add isUrl to the Str class and use it from the validator

Just like isUuid. I've also fixed some incorrect param doc where the intention of the methods is to accept any value and both validate if it is a string and is a URL or UUID, etc.

Why not use filter_var('http://example.com', FILTER_VALIDATE_URL, FILTER_FLAG_PATH_REQUIRED) directly?

Because that is not the same behaviour.


feat: @octokit-next/core

closes #72

tests are failing because the user agent string changes depending on the platform it's ran on, and it's now part of a few test snapshots 😭


Tab Index for items

Currently I notice the tabIndex for the multiselect it always set to the first item on opening the control. Also I observed the tab index for all the items is set to -1. Suggest me the way to set the tab index to selected item on opening the control.

@mail2gopinath ,
Sorry for the late reply.
In short.. add 1 into that number.
But you need to take into account these:

If filter box is ON, the directive will focus to the filter box.
If filter box is OFF, the directive will focus on the first item.


Disable testing code which force custom commission

Problem
Regular commission should go through Standard Commission Flow.
However the Custom Commission flow (for testing only) is enabled,
and override the Standard Commission flow
Change overview
Disable the Custom Commission flow for testing only
Testing
How was this tested? (at least one bullet point required)

Build examples/all-cluster-minimal-app and verify commissioning with examples/chip-tool

Approving, but this is going to break various QA/smoketest flows, I expect....

If things are actually using this, maybe adding it back as an argument would be the correct thing to do.
None of our CI uses it though it seems.

Yes, it's used by manual smoketests to test "commission with long pairing code"...

The origial testing code was added in #15506

The origial testing code was added in https://github.com/project-chip/connectedhomeip/pull/15506

That PR moved the code around.  It did not add it.

The origial testing code was added in #15506

That PR moved the code around. It did not add it.

Do you think the current fix makes sense? If yes, can you help to approve?


Release v0.8.3

Release Checklist

[ ] OWNERS must LGTM the release proposal.
At least two for minor or major releases. At least one for a patch release.
[x] Verify that the changelog in this issue and the CHANGELOG folder is up-to-date

[x] Use https://github.com/kubernetes/release/tree/master/cmd/release-notes to gather notes.
Example: release-notes --org kubernetes-sigs --repo kueue --branch release-0.3 --start-sha 4a0ebe7a3c5f2775cdf5fc7d60c23225660f8702 --end-sha a51cf138afe65677f5f5c97f8f8b1bc4887f73d2 --dependencies=false --required-author=""

[x] For major or minor releases (v$MAJ.$MIN.0), create a new release branch.

[x] An OWNER creates a vanilla release branch with
git branch release-$MAJ.$MIN main
[x] An OWNER pushes the new release branch with
git push release-$MAJ.$MIN

[x] Update the release branch:

[x] Update RELEASE_BRANCH and RELEASE_VERSION in Makefile and run make prepare-release-branch
[x] Update the CHANGELOG
[x] Submit a pull request with the changes: https://github.com/kubernetes-sigs/kueue/pull/3442

[ ] An OWNER creates a signed tag running
git tag -s $VERSION
and inserts the changelog into the tag description.
To perform this step, you need a PGP key registered on github.
[ ] An OWNER pushes the tag with
git push upstream $VERSION

Triggers prow to build and publish a staging container image
us-central1-docker.pkg.dev/k8s-staging-images/kueue/kueue:$VERSION

[ ] An OWNER prepares a draft release

[ ] Create the draft release poiting out to the created tag.
[ ] Write the change log into the draft release.
[ ] Run
make artifacts IMAGE_REGISTRY=registry.k8s.io/kueue GIT_TAG=$VERSION
to generate the artifacts in the artifacts folder.
[ ] Upload the files in the artifacts folder to the draft release - either
via UI or gh release upload <tag> artifacts/*.

[ ] Submit a PR against k8s.io,
updating registry.k8s.io/images/k8s-staging-kueue/images.yaml to
promote the container images
to production:
[ ] Wait for the PR to be merged and verify that the image registry.k8s.io/kueue/kueue:$VERSION is available.
[ ] Publish the draft release prepared at the GitHub releases page.
Link:
[ ] Run the openvex action to generate openvex data. The action will add the file to the release artifacts.
[ ] Update the main branch :

[ ] Update RELEASE_VERSION in Makefile and run make prepare-release-branch
[ ] Release notes in the CHANGELOG
[ ] SECURITY-INSIGHTS.yaml values by running make update-security-insights GIT_TAG=$VERSION
[ ] Submit a pull request with the changes:
[ ] Cherry-pick the pull request onto the website branch

[ ] Run the SBOM action to generate the SBOM and add it to the release.
[ ] For major or minor releases, merge the main branch into the website branch to publish the updated documentation.
[ ] Send an announcement email to<EMAIL_ADDRESS>and<EMAIL_ADDRESS>with the subject [ANNOUNCE] kueue $VERSION is released.
[ ] For a major or minor release, prepare the repo for the next version:

[ ] Create an unannotated devel tag in the
main branch, on the first commit that gets merged after the release
branch has been created (presumably the README update commit above), and, push the tag:
DEVEL=v0.$(($MAJ+1)).0-devel; git tag $DEVEL main && git push $DEVEL
This ensures that the devel builds on the main branch will have a meaningful version number.
[ ] Create a milestone for the next minor release and update prow to set it automatically for new PRs:

[ ] Create the presubmits jobs for the next patch release:

Changelog
Changes since `v0.8.2`:

## Changes by Kind

### Bug or Regression

- Workload is requeued with all AdmissionChecks set to Pending if there was an AdmissionCheck in Retry state. (#3323, @PBundyra)
- Account for NumOfHosts when calculating PodSet assignments for RayJob and RayCluster (#3384, @andrewsykim)

As @andrewsykim mentioned in https://github.com/kubernetes-sigs/kueue/pull/3384#issuecomment-2455952955, it seems that I forgot to include the KubeRay NumOfHosts fixes...
So, let us do an additional patch release.
cc : @mimowo

It seems that some of the fixes are not included...

thank you @tenzen-y

Thank you! LGTM

Tag final confirmation:
$ git log v0.8.3 --oneline
982a9f33 (HEAD, tag: v0.8.3, upstream/release-0.8) Prepare v0.8.3 (#3442)
aa89cdb5 (release-0.8) Prepare release v0.8.2 (#3433)
fd60db57 Remove WithName() on BaseWebhook. (#3415)
4adebae9 [KubeRay] Support NumOfHosts when calculating PodSet assignments (#3386) (#3408)
59f6a906 Cleanup debug log in provisioning integration tests (#3407)
9e7a61ba Reset all Ready and Ready AdmissionChecks on Eviction as Pending (#3323) (#3395)
73e2a4ce Force status field ownership by core Kueue to fix the MultiKueue integration (#3396)
916dfde1 Automated cherry pick of #3132: Drop remove operations from webhook patches (#3358)
[...]

Here is the git differences between pushed v0.8.3 and v0.8.2: https://github.com/kubernetes-sigs/kueue/compare/v0.8.2...v0.8.3

lgtm

$ docker pull registry.k8s.io/kueue/kueue:v0.8.3
v0.8.3: Pulling from kueue/kueue
3697361640de: Download complete
Digest: sha256:bce25ee1315d46f94a84697002397f666f4619a623513d669285dd541bc59956
Status: Downloaded newer image for registry.k8s.io/kueue/kueue:v0.8.3
registry.k8s.io/kueue/kueue:v0.8.3

What's next:
    View a summary of image vulnerabilities and recommendations → docker scout quickview registry.k8s.io/kueue/kueue:v0.8.3
$ kubectl get pod -n kueue-system kueue-controller-manager-6bb64cc786-fqv5k -ojsonpath='{.spec.containers[0].image}{"\n"}'
registry.k8s.io/kueue/kueue:v0.8.3
$ kubectl get pod -n kueue-system
NAME                                        READY   STATUS    RESTARTS   AGE
kueue-controller-manager-6bb64cc786-fqv5k   2/2     Running   0          59s

All tasks are completed.
@andrewsykim Again, thank you for reporting this!
/close

thank you @tenzen-y for the quick fix!


src/win/udp.c: Incompatible with Visual C++ 9/C89

Version: 1.38.0 (upgrading from 1.36)
Platform: Windows (AppVeyor VM)

gevent supports Python 2.7, which has a particular compiler it must use (Visual C++ 9). When updating from 1.36 to 1.38, I find that I can no longer compile with that compiler. Error message:
   C:\Users\appveyor\AppData\Local\Programs\Common\Microsoft\Visual C++ for Python\9.0\VC\Bin\amd64\cl.exe /c /nologo /Ox /MD /W3 /GS- /DNDEBUG -DLIBUV_EMBED=1 -D_GNU_SOURCE=1 -DWIN32=1 -D_CRT_SECURE_NO_DEPRECATE=1 -D_CRT_NONSTDC_NO_DEPRECATE=1 -D_CRT_SECURE_NO_WARNINGS=1 -D_WIN32_WINNT=0x0600 -DWIN32_LEAN_AND_MEAN=1 -IC:\projects\gevent\deps\libuv\include -IC:\projects\gevent\deps\libuv\src -IC:\projects\gevent\src\gevent -IC:\Python27-x64\include -IC:\Python27-x64\PC /Tcdeps\libuv\src\win/udp.c /Fobuild\temp.win-amd64-2.7\Release\deps\libuv\src\win/udp.obj    udp.c
    deps\libuv\src\win/udp.c(777) : error C2143: syntax error : missing ';' before 'type'
    deps\libuv\src\win/udp.c(778) : error C2143: syntax error : missing ';' before 'type'
    error: command 'C:\\Users\\appveyor\\AppData\\Local\\Programs\\Common\\Microsoft\\Visual C++ for Python\\9.0\\VC\\Bin\\amd64\\cl.exe' failed with exit status 2

It appears the STATIC_ASSERT macros on those lines are incompatible with the C89 syntax required by this compiler. I'm not sure what the problem was, other STATIC_ASSERT statements (pipe.c, fs.c) compiled successfully; I guess it's that there's code that comes before these uses, and these uses expand to something that looks like a variable definition.
My temporary patch was just to comment them out, though of course that's not ideal:
diff --git a/deps/libuv/src/win/udp.c b/deps/libuv/src/win/udp.c
index 1c4977af..958dee28 100644
--- a/deps/libuv/src/win/udp.c
+++ b/deps/libuv/src/win/udp.c
@@ -774,8 +774,8 @@ int uv__udp_set_source_membership6(uv_udp_t* handle,
     mreq.gsr_interface = 0;
   }

-  STATIC_ASSERT(sizeof(mreq.gsr_group) >= sizeof(*multicast_addr));
-  STATIC_ASSERT(sizeof(mreq.gsr_source) >= sizeof(*source_addr));
+//  STATIC_ASSERT(sizeof(mreq.gsr_group) >= sizeof(*multicast_addr));
+//  STATIC_ASSERT(sizeof(mreq.gsr_source) >= sizeof(*source_addr));

I can fix that, however... we're in the process of phasing out pre-VS2015 support, see #2821 (and that's really just making de jure what was already de facto the case.)
With python 2 EOL there's no reason for us to support VS 2008 any longer. If you still want to support it, you'll be on the hook for maintaining patches as we are unlikely to accept them.

I can fix that

Thank you!

With python 2 EOL there's no reason for us to support VS 2008 any longer.

Of course that's this project's decision to make, but that's very unfortunate for me. gevent needs to continue to support Python 2.7 for some time to come. It's not like a switch was flipped and usage of Python 2.7 just stopped — it still makes up more than a quarter of gevent's 3 million monthly downloads. While direct upstream support may have ended, distributors such as Anaconda and RHEL are continuing to offer support (through 2024 in the latter case).


Flutter VSC cant run on ios 17 | Xcode 15

Is there an existing issue for this?

[x] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce

Create new Flutter Application

Open in Xcode 15 and change Bundle Identifier for Runner and RunnerTests

Run in Xcode 15 -> Build Succeeds -> Install on iPhone Succeeds -> Run on iPhone Succeeds
or

Run Flutter Application in VSC with "flutter run" or press execute

Build Succeeds -> Install on iPhone Succeeds -> Error:
Could not run build/ios/iphoneos/Runner.app on 00008020-00186DCE0A33002E.
Try launching Xcode and selecting "Product > Run" to fix the problem:
open ios/Runner.xcworkspace

Expected results
The Flutter App runs perfectly fine when Compiling in Xcode 15.
The Flutter App does not run via VSC.
Actual results
I ran "flutter run --verbose" and the output before the crash is shown below:
Unable to locate DeviceSupport directory with suffix 'DeveloperDiskImage.dmg'. This probably
means you don't have Xcode installed, you will need to launch the app manually and logging output will not be shown!
Funny thing is that the Device Support File for iOS 17 is not even in the folder.
Code sample
Code sample
[Paste your code here]
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        // This is the theme of your application.
        //
        // TRY THIS: Try running your application with "flutter run". You'll see
        // the application has a blue toolbar. Then, without quitting the app,
        // try changing the seedColor in the colorScheme below to Colors.green
        // and then invoke "hot reload" (save your changes or press the "hot
        // reload" button in a Flutter-supported IDE, or press "r" if you used
        // the command line to start the app).
        //
        // Notice that the counter didn't reset back to zero; the application
        // state is not lost during the reload. To reset the state, use hot
        // restart instead.
        //
        // This works for code too, not just values: Most code changes can be
        // tested with just a hot reload.
        colorScheme: ColorScheme.fromSeed(seedColor: Colors.deepPurple),
        useMaterial3: true,
      ),
      home: const MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({super.key, required this.title});

  // This widget is the home page of your application. It is stateful, meaning
  // that it has a State object (defined below) that contains fields that affect
  // how it looks.

  // This class is the configuration for the state. It holds the values (in this
  // case the title) provided by the parent (in this case the App widget) and
  // used by the build method of the State. Fields in a Widget subclass are
  // always marked "final".

  final String title;

  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  int _counter = 0;

  void _incrementCounter() {
    setState(() {
      // This call to setState tells the Flutter framework that something has
      // changed in this State, which causes it to rerun the build method below
      // so that the display can reflect the updated values. If we changed
      // _counter without calling setState(), then the build method would not be
      // called again, and so nothing would appear to happen.
      _counter++;
    });
  }

  @override
  Widget build(BuildContext context) {
    // This method is rerun every time setState is called, for instance as done
    // by the _incrementCounter method above.
    //
    // The Flutter framework has been optimized to make rerunning build methods
    // fast, so that you can just rebuild anything that needs updating rather
    // than having to individually change instances of widgets.
    return Scaffold(
      appBar: AppBar(
        // TRY THIS: Try changing the color here to a specific color (to
        // Colors.amber, perhaps?) and trigger a hot reload to see the AppBar
        // change color while the other colors stay the same.
        backgroundColor: Theme.of(context).colorScheme.inversePrimary,
        // Here we take the value from the MyHomePage object that was created by
        // the App.build method, and use it to set our appbar title.
        title: Text(widget.title),
      ),
      body: Center(
        // Center is a layout widget. It takes a single child and positions it
        // in the middle of the parent.
        child: Column(
          // Column is also a layout widget. It takes a list of children and
          // arranges them vertically. By default, it sizes itself to fit its
          // children horizontally, and tries to be as tall as its parent.
          //
          // Column has various properties to control how it sizes itself and
          // how it positions its children. Here we use mainAxisAlignment to
          // center the children vertically; the main axis here is the vertical
          // axis because Columns are vertical (the cross axis would be
          // horizontal).
          //
          // TRY THIS: Invoke "debug painting" (choose the "Toggle Debug Paint"
          // action in the IDE, or press "p" in the console), to see the
          // wireframe for each widget.
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            const Text(
              'You have pushed the button this many times:',
            ),
            Text(
              '$_counter',
              style: Theme.of(context).textTheme.headlineMedium,
            ),
          ],
        ),
      ),
      floatingActionButton: FloatingActionButton(
        onPressed: _incrementCounter,
        tooltip: 'Increment',
        child: const Icon(Icons.add),
      ), // This trailing comma makes auto-formatting nicer for build methods.
    );
  }
}

### Screenshots or Video

Screenshots / Video demonstration
Unable to locate DeviceSupport directory with suffix 'DeveloperDiskImage.dmg'. This probably
means you don't have Xcode installed, you will need to launch the app manually and logging output will not be shown!

### Logs

Logs

```console
[Paste your logs here]
2023-06-20 19:08:18.238 ios-deploy[21379:195653] [ !! ] Unable to locate DeviceSupport directory with suffix 'DeveloperDiskImage.dmg'. This probably
means you don't have Xcode installed, you will need to launch the app manually and logging output will not be shown!
[        ] Script started, output file is /dev/null
[        ] Script done, output file is /dev/null
[        ] ios-deploy exited with code 0
[   +1 ms] Could not run build/ios/iphoneos/Runner.app on 00008020-00186DCE0A33002E.
[        ] Try launching Xcode and selecting "Product > Run" to fix the problem:
[        ]   open ios/Runner.xcworkspace
[        ] Installing and launching... (completed in 10,7s)
[        ] Error launching application on iPhone von Manuel.
[        ] "flutter run" took 24 208ms.
[   +1 ms]
           #0      throwToolExit (package:flutter_tools/src/base/common.dart:10:3)
           #1      RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:757:9)
           <asynchronous suspension>
           #2      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1336:27)
           <asynchronous suspension>
           #3      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #4      CommandRunner.runCommand (package:args/command_runner.dart:212:13)
           <asynchronous suspension>
           #5      FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:296:9)
           <asynchronous suspension>
           #6      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #7      FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:244:5)
           <asynchronous suspension>
           #8      run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:91:9)
           <asynchronous suspension>
           #9      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #10     main (package:flutter_tools/executable.dart:91:3)
           <asynchronous suspension>

[ +173 ms] ensureAnalyticsSent: 171ms
[        ] Running 1 shutdown hook
[        ] Shutdown hooks complete
[        ] exiting with code 1
</details>

### Flutter Doctor output

<details><summary>Doctor output</summary>

```console
[Paste your output here]
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.10.5, on macOS 13.4 22F66 darwin-arm64, locale de-AT)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
[✓] Xcode - develop for iOS and macOS (Xcode 15.0)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2021.3)
[✓] VS Code (version 1.79.2)
[✓] Connected device (3 available)
[✓] Network resources

• No issues found!

A working workaround is:
https://github.com/flutter/flutter/issues/128531#issuecomment-1587984546

Thanks for the report.
Currently we are unable to replicate this due to lack of latest config (Xcode 15 and iOS 17), but based on the report, adding applicable labels for team's attention.
Below is the list of issues related to Flutter, Xcode 15 and iOS 17 for reference:
https://github.com/orgs/flutter/projects/87/views/1
/cc @vashworth

Is this a duplicate? https://github.com/flutter/flutter/issues/128531
@vashworth?

Yes, this is the same issue. Closing as a duplicate.


devops server/TFS

"The Azure DevOps team is made of about 800 people that contribute to either the subscription-based cloud service (Azure DevOps Server) or the on-permise product (TFS)."
this no longer seems correct as 'Azure Devops' is the online version and 'Azure DevOps server' is the on-premise solution now.

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

ID: 80853077-4c90-2663-7ed6-5fadbcf4f4ed
Version Independent ID: 4864bcb3-1930-d4f1-c927-1adbbb2899ac
Content: Agile principles in practice - Azure DevOps
Content Source: https://mseng.visualstudio.com/DefaultCollection/TechnicalContent/_git/devops-learn-pr?path=%2fdocs%2fdevops-at-microsoft%2fagile-principles-in-practice.md&version=GBlive&_a=contents
Product: devops
Technology: devops-learn
Git Login: samgu
Microsoft Alias: samgu

@CloudCrusader -- thank you for your feedback.  I have updated the documentation and it should be live by tomorrow.


chore(sdk-trace-base): fix spanLimits attribute length/count to consider env values

Which problem is this PR solving?
OTEL_ATTRIBUTE_VALUE_LENGTH_LIMIT and OTEL_ATTRIBUTE_COUNT_LIMIT env values were being ignored when re-configuring span limits.
Fixes #3049
Short description of the changes
Updated the reconfigureLimits function to check additional items before updating spanLimits.attributeValueLengthLimit and spanLimits.attributeCountLimit property.
BEFORE
Before, reconfigureLimits wasn't considering if the user set the general attribute value length limit (OTEL_ATTRIBUTE_VALUE_LENGTH_LIMIT) via env - it was only checking if user set that value programmatically. Same issue with the attribute count limit OTEL_ATTRIBUTE_COUNT_LIMIT.
NOW
Now it checks if the user did not set the spanLimits.attributeValueLengthLimit programmatically AND if OTEL_SPAN_ATTRIBUTE_VALUE_LENGTH_LIMIT env value is still set to the default value (ex. Infinity) BUT if the user set the generalLimits.attributeValueLengthLimit programmatically OR user set the OTEL_ATTRIBUTE_VALUE_LENGTH_LIMIT via env, then reconfigure the spanLimits.attributeValueLengthLimit value to either use the generalLimits.attributeValueLengthLimit set programmatically or use the OTEL_ATTRIBUTE_VALUE_LENGTH_LIMIT env value.
Note: I had to wrap the old DEFAULT_CONFIG object into a function because those envs value (parsed in DEFAULT_CONFIG) were being parsed before the tests ran so it caused the new tests to fail. I added a comment about that above that function just in case someone had questions about it but I can remove the comment if needed.
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)

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

[x] Unit tests

Checklist:

[x] Followed the style guidelines of this project
[x] Unit tests have been added

I don't think this is a "chore" patch. IMO, it's more like a "feat" or "fix", from various perspectives.


Type error while trying to override existing behavior

TypeError

Cannot read properties of undefined (reading 'value')

  https://nickcoutsos.github.io/keymap-editor/6538.60e18e71838a18bab272.js:1:19686
  https://nickcoutsos.github.io/keymap-editor/6538.60e18e71838a18bab272.js:1:21790
  https://nickcoutsos.github.io/keymap-editor/6538.60e18e71838a18bab272.js:1:21766
  webpack:///node_modules/react-dom/cjs/react-dom.production.min.js:182:188
  webpack:///node_modules/react/cjs/react.production.min.js:25:207
  https://nickcoutsos.github.io/keymap-editor/6538.60e18e71838a18bab272.js:1:21744
  https://nickcoutsos.github.io/keymap-editor/6538.60e18e71838a18bab272.js:1:21673
  https://nickcoutsos.github.io/keymap-editor/6538.60e18e71838a18bab272.js:1:15138
  webpack:///node_modules/react-dom/cjs/react-dom.production.min.js:166:136

Hey, thanks! I think I've got it sorted out, please confirm when you get a chance.
If you're still having problems it would help to provide a little more detail about the behavior you're trying to reconfigure and maybe a sample keymap to look at.

Thanks for the quick fix. Seems like I'm no longer having the issue, for now. I'll keep using the tool and let you know.
And hey, thanks for making this :)


create pre-index db dump for integration testing

Proposed changes
convert integration test db creation to a pre-index db dump SQL
sizes:
(base) ubuntu@:~/dea-notebooks$ ls -la docker/database/ -h
total 424K
drwxrwxr-x 2 ubuntu ubuntu 4.0K Jan 11 23:14 .
drwxrwxr-x 4 ubuntu ubuntu 4.0K Jan 11 23:14 ..
-rw-rw-r-- 1 ubuntu ubuntu   71 Jan 11 23:14 Dockerfile
-rw-r--r-- 1 ubuntu ubuntu 409K Jan 11 23:12 dump.sql

This looks fantastic Pin! A few questions:

So this is currently an empty database with no data indexed yet?
What does this file do?
Tests/Frequently_used_code/file.txt

And a suggestion: can we please move this "docker" folder inside the "Tests" folder? We want to keep the top level of DEA Notebooks as clean as possible as beginner users get confused by stuff like this - it's good to hide it where possible.

docker folder moved and file.txt deleted

Will be superceded by direct Sandbox datacube access, can close for now


[Cleanup] NewBlastEditor cleanup

Lots of very minor changes here. I definitely want to see if I can refactor this file more in a future change. For now, I'm just tidying up.

Rebased to take in ircluzar's changes.


Move the E2EE popout over the button

Perhaps it showing on hover vs click should be an option? Maybe the same with the placement, I rather like it appearing above on click.

Prefer on top as well

Above or on top (overtop/overlaid)?

above


Non-resizable columns

Is there a way to have some columns be resizable and others not?  I've got a table with columns of checkboxes, icons and text - it makes sense for the text columns to be resizable but the checkboxes & icons should remain fixed width.
Awesome module, btw.

Currently no.
The next major version in the works will have this functionality.

Great, I'll look out for it, thanks.


[SPARK-49560][SQL] Add SQL pipe syntax for the TABLESAMPLE operator

What changes were proposed in this pull request?
WIP
This PR adds SQL pipe syntax support for the TABLESAMPLE operator.
For example:
CREATE TABLE t(x INT, y STRING) USING CSV;
INSERT INTO t VALUES (0, 'abc'), (1, 'def');

TABLE t
|> TABLESAMPLE (100 PERCENT) REPEATABLE (0)
|> TABLESAMPLE (5 ROWS) REPEATABLE (0)
|> TABLESAMPLE (BUCKET 1 OUT OF 1) REPEATABLE (0);

0	abc
1	def

Why are the changes needed?
The SQL pipe operator syntax will let users compose queries in a more flexible fashion.
Does this PR introduce any user-facing change?
Yes, see above.
How was this patch tested?
This PR adds a few unit test cases, but mostly relies on golden file test coverage. I did this to make sure the answers are correct as this feature is implemented and also so we can look at the analyzer output plans to ensure they look right as well.
Was this patch authored or co-authored using generative AI tooling?
No

Alright @gengliangwang @cloud-fan here's the TABLESAMPLE operator. It is super simple, we just add | sample to the list of parsing options and call withSample(c, left) on it from the AstBuilder. 🙏

Thanks, merging to master


Remove reference to disabled inputs

Disabled and readonly inputs work with :input_html => { :disabled => true (or) :readonly => true }, just as they do in Formtastic.

@karpah Are you saying that disabled inputs are already working as they do in Formtastic and I just didn't know it?

That's correct, as far as I can see.

Thanks for the contribution!


MSSQL Environment Variables

What are the environment variables used in the MSSQL container? Should these be listed in the README.md?
https://hub.docker.com/_/microsoft-mssql-server
In particular, what are the following:
MSSQL_SA_PASSWORD
MSSQL_PID

To answer my own question, by running the following they are visible. Should we still list them in Readme?
docker exec mssql_example-database-1 /bin/sh -c /usr/bin/env
(where 'mssql_example-database-1' is the container name).


Update Messages_zh_CN.properties

modifying error of positional argument in Chinese search result text
Description
The second positional argument is mistakenly set to the third one in Chinese text

@CirQ thank you!


New converter branch

Added Integration Tests for Avro and Json Format

I saw there is another PR for merging some changes into the current branch, do you want to merge in the PR first?

Please use other connector integration test as your reference


Move azure-cosmos-js/master into central repo

@bsiegel for the rush related change: https://github.com/Azure/azure-sdk-for-js/pull/2208/commits/43eabaac1d52c0a45626bc8ff995992d531390c3

I temporarily renamed test to integration-test so emulator tests are skipped for our Rush CI builds. @bsiegel is working on using a different name in Rush CI builds to execute unit tests.

@christopheranderson and @southpolesteve Is this good to merge? I believe the latest master is included and I don't see any open PRs against master in azure-cosmos-js repo.

I'll look this over ASAP


Cannot pull from YAML array when index is also a YAML  data member

What happened?
Hey there. I'd be very happy if this were just user error, but I'm not sure what else to try. =)
When I run the query below on YAML looking like this:
status: 2
statusList:
 -
 - 📆 Scheduled
 - ⚙ In Progress
 - ✋ On Hold
 - ✅ Complete
 - ❎ Will Not Do

The result is simply a bullet followed by a dash. If I actually populate statusList[0] the result just comes back entirely blank. Meanwhile, if I ask for any specific index by hard coding it, I get exactly what I'm expecting. I can request the whole list, and it'll come through. Emojis render just fine. If I've got the entries wrapped in quotes or just as plain text (or both) the same behavior exists.
I've tried every variation I can think of (including a couple of different YAML array syntaxes) and the result is the same. The silly thing is, this used to work, maybe six months ago. =)
Please let me know if any further details are required, and thank you in advance!
DQL
TABLE statusList[status] as Status
FROM "Things"
WHERE status = 2 OR status = 3
SORT priority DESC

JS
No response
Dataview Version
0.5.33
Obsidian Version
0.14.15
OS
Windows

Good catch... fixed in 0.5.34.


Default get_public_dsn() to https

The API enforces https, the DSN returned should match.
The issue with proto-relative is that it creates CORS errors.
On http, the call results in:

307 Internal Redirect
Location:https://app.getsentry.com/api/....

and the console errors:

XMLHttpRequest cannot load .... Origin 'null' is therefore not allowed access.

The event is is still successfully logged.
The error is, at best, annoying.
The scheme argument can not be purged without breaking backward compatibility. Folks already using:
{% sentry_public_dsn 'https' %}

will see no change. Those using:
{% sentry_public_dsn %}

Will no longer get a console error.

So to comment here on some high level things without actually reviewing code:

The redirect you’re seeing is coming from your browser, not our server. We do allow ingestion for this endpoint alone over both http and https. The protocol needs to match to avoid cross-origin requests, which strip headers that we need.
Regardless of this change, raven-js takes it upon itself to strip the protocol anyways, no matter what we specify here for the above issue. So in theory, no change here will actually have an impact.
Users run Sentry themselves in an environment that might not even have https, so we can enforce this on them.

The redirect you’re seeing is coming from your browser, not our server.

Is this entirely accurate?
When I do:
curl -I https://app.getsentry.com
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload

So yeah, the browser is redirecting, but only because the server is setting HSTS.

We do allow ingestion for this endpoint alone over both http and https

How is http possible with HSTS? I'm assuming outside of a browser context? ... now curious if the template tag is ever consumed for a non-browser environment.

Users run Sentry themselves in an environment that might not even have https, so we can enforce this on them.

👍
Thanks for the reply.

Regardless of this change, raven-js takes it upon itself to strip the protocol anyways

Double check this? I'm currently using<EMAIL_ADDRESS>Updated to production to use {% sentry_public_dsn 'https' %}, I see Raven._dsn is https and all CORS now happen without error.
With the service using HSTS (and the web trending toward https) I think there is still value in this pull. Granted, http users would now have to pass the scheme http (which may be an intolerable break in compatibility).


Whse.-Shipment Release - Reopen

In the latest version v16.1 - Microsoft_Base Application_16.1.12629.13149
Codeunit "Whse.-Shipment Release" - Reopen function is missing the call by reference. after the function call the value remains unchanged.
procedure Reopen(WhseShptHeader: Record "Warehouse Shipment Header")  - missing call by reference

Does it really need to be by reference? The caller can Find() the record afterwards. Changing this now would break API/ABI I think.
Do other Release codeunits take by var in their Reopen()s? Does this codeunit in its other methods?

codeunit 414 "Release Sales Document" - procedure Reopen(var SalesHeader: Record "Sales Header")
after the reopen function call, again it has to be fetched from DB to get the latest. so it is better to have reference.

Hi! Please take a minute to read the guidelines for this repository https://github.com/microsoft/AL and our collection of frequently asked questions https://github.com/Microsoft/AL/wiki/frequently-Asked-Questions .
As this repository is only for issues related to the AL compiler in latest developer preview environment for Dynamics 365 Business Central. We suggest that you open a support case or file a bug in Collaborate, to ensure that all Business Central users benefit from your catch as soon as possible.
To open a support case, you can:

Open a support request to CSS through the PartnerSource portal
Contact your Service Account Manager (SAM) in your local subsidiary to understand what is included in your contract as of support incident and PAH (Partner Advisory Hours). Your SAM might also direct you "step by step" how to open a support request or how to get credentials, if this is the first time for you or your company

If you file the bug in Collaborate, remember to include steps to reproduce the issue, and the Business Central build number and country version you're using.


Removing OutputString Event Handler

Resolves #600. On a related note, we still need to fix the ShouldSupportRemoteSession test (#252). May take that task pending time.
@EricMSFT @AndreSayreMSFT @HuanhuanSunMSFT

Looks good, once AppVeyoyr's happy

Agree with @AndreSayreMSFT :D


Actors following the player

Is your feature request related to a problem? Please describe.
A way to make an actor follow the player would be a nice feature. Right now, we have to use a lot of events that won't even work with the 16px grid.
Describe the solution you'd like
I would like to be able to make an actor follow the player from the actor's properties, something like a check box.
Additional context
Many old RPGs had characters following the player, for example, Final Fantasy or Dragon Quest/Warrior II.

try this for plataformer:
https://i.imgur.com/n6Ex7Q9.png
or use both variables if your game is top down 2d


feat(ui): show when devices needs to be re-interviewed

Fixes #3225

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 4 (0.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.005%) to 21.777%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/ZwaveClient.ts
0
2
0.0%

src/components/nodes-table/nodes-table.js
0
2
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.005%

Covered Lines:
3845

Relevant Lines:
18673

💛  - Coveralls

Hello Robert,
Nice feature but once I re-interview the node, the little blue icon does not go away. Maybe I am doing something wrong?

Home Assistant 2023.8.1
zwave-js-ui: <IP_ADDRESS>eba25
zwave-js: 11.13.0
home id:<PHONE_NUMBER>
home hex: 0xd5ed4cd5

@snowmangh You are right! I forgot to update the status when the interview is done, let me fix that asap :)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 4 (0.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.005%) to 21.777%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/ZwaveClient.ts
0
2
0.0%

src/components/nodes-table/nodes-table.js
0
2
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.005%

Covered Lines:
3845

Relevant Lines:
18673

💛  - Coveralls