Missing input variable domain

When running terragrunt run-all apply, the module in aws-site-1-app-vm complains about a missing input variable. Should the terragrunt.hcl.example be updated?
Error: No value for required variable
│
│   on variables.tf line 16:
│   16: variable "domain_name" {
│
│ The root module input variable "domain_name" is not set, and has no default
│ value. Use a -var or -var-file command line argument to provide a value for
│ this variable.
╵
ERRO[1578] Terraform invocation failed in /.../aws-site-1-app-vm/.terragrunt-cache/marble-farble-warble-garble  prefix=[/.../aws-site-1-app-vm]
INFO[1578] Executing hook: missing_var                   prefix=[/.../aws-site-1-app-vm]
missing required input variable. check your terragrunt.hcl input{} block.
ERRO[1578] Module /.../aws-site-1-app-vm has finished with an error: 1 error occurred:
        * exit status 1
  prefix=[/.../aws-site-1-app-vm]
ERRO[1578] 1 error occurred:
        * exit status 1

You are correct. In my testing on my local HCL file, I have a domain name. Since that file is in .gitignore, it was missed in previous commit and PR.
example...
inputs = {
    projectPrefix          = "giroux1"
    resourceOwner          = "giroux"
    domain_name            = "giroux-frontend.mydomain.com"

Add necessary change to the files. See PR...


Close #66 check response.body is present

if the response.body is missing the MultiJson.load fails with a
MultiJson::LoadError.

This has been merged manually as GitHub said "We can’t automatically merge this pull request."


Missing file inside the package

This error happend right after I type exit and you package must generate the code
[ErrorException]
file_get_contents(/Volumes/Storage/Projects/net-manager_new/vendor/infyomlabs/swagger-generator/templates/model/model.stub): failed to open stream: No such file or directory
Also, in your package folder have only two directories:
core-templates
laravel-generator
there is not a folder called 'swagger-generator'

@microdesign I think you are missing swagger-generator package. Read installation steps carefully here: http://labs.infyom.com/laravelgenerator/docs/master/installation#add-packages


Change AutoStart type from bool to int

AutoStart type should be int instead of bool, since 2 is also a allowed value according to the manual: https://content.oss.deltares.nl/delft3d/manuals/D-Flow_FM_User_Manual.pdf#section.A.1

Great, looks good.


ci: Update golang to 1.17.8

Address https://github.com/advisories/GHSA-6685-ffxp-xm6f
Description

Fixes: https://github.com/advisories/GHSA-6685-ffxp-xm6f
Checklist
Please make sure that your PR fulfills the following requirements:

[ ] Reviewed the guidelines for contributing to this repository
[ ] The commit message follows the Conventional Commits Guidelines.
[ ] Tests for the changes have been updated
[ ] Docs have been added / updated
[ ] Optional. My organization is added to USERS.md.

Type of Change

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] New tests
[ ] Build/CI related changes
[ ] Documentation content changes
[ ] Other (please describe)

Other information

Codecov Report

Merging #326 (cef6762) into main (b7357ee) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #326   +/-   ##
=======================================
  Coverage   76.51%   76.51%
=======================================
  Files          22       22
  Lines         941      941
=======================================
  Hits          720      720
  Misses        137      137
  Partials       84       84

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


Added error catching to spawn child process

If you run this package on a system that does not have a valid audio player installed and attempt to play a file, you get an uncaught error. This minor change catches that error and handles it properly allowing the project calling this module to handle the error gracefully instead of terminating.

Thank you so much!


Support provider name & template name to uniquely identify a template

Optionally support 'ansible_provider_name' to uniquely identify a
job template. This is needed where you might have multiple Ansible
Towers with the same named templates.
Links

https://bugzilla.redhat.com/show_bug.cgi?id=1378606

Testing:
Bugzilla provides the details

Just noted this PR in the bug, I was wondering why is provider name better than provider ID? Provider ID  (or GUID) cannot change for one given provider but name can.

@mfalesni
ID can uniquely identify a template or rather any object in the vmdb.
In the customers case they have names that they are picking from the service dialogs.
When you specify a template you can pass one of the following to uniquely identify a job template

job_template object passed in using ConfigurationScript::job_template=<>
job_template_id
job_template_name & ansible_provider_name
job_template_name

This PR adds option 3 from above.

@bzwei Please review

@mkanoor should the provider name key ansinble_tower_provider_name? Do we need the alternative name with prefix dialog_?

@bzwei
Changes made. There is lot of code duplication in spec, which I think we can cleanup in a separate PR.

@mkanoor definitely we should simplify the spec. I am OK with a separate PR.

Euwe backport details:
$ git log -1
commit 166c703906fed68236023d53f702b431e4a1ef8b
Author: Greg McCullough<EMAIL_ADDRESS>Date:   Mon Nov 28 14:12:23 2016 -0500

    Merge pull request #11669 from mkanoor/bugzilla_1378606

    Support provider name & template name to uniquely identify a template
    (cherry picked from commit 76c643b434e10061a7d5e93db62f3eff17ecfacf)

    https://bugzilla.redhat.com/show_bug.cgi?id=1411359


Bus Error

Hello, thank you for this library.
I'm having an issue with the following code in Node.js v20.1.0, but also appears on LTS v18.17.0
test.js:
import { FFmpeg } from<EMAIL_ADDRESS>const ffmpeg = await FFmpeg.create()

running node test.js I get "bus error".
I'm not able to catch any errors, nor see whats causing this. Any idea how to debug?

package.json:
{
  "name": "ffmpeg-delete-me",
  "version": "0.0.1",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "keywords": [],
  "author": "Wes Bos (https://wesbos.com/)",
  "license": "MIT",
  "dependencies": {
<EMAIL_ADDRESS>"^0.13.2",
<EMAIL_ADDRESS>"^0.13.0"
  },
  "type": "module"
}

Seems to be happening when requiring the core in importCore function. Both core-mt and core-st create a bus error

Dug a bit deeper - its this line:
      let core = yield (yield importCore(options.core, logger))({
        arguments: VERSION_ARGS,

VERSION_ARGS is ["ffmpeg", "-version"] and I guess when it runs that, it chokes? Replacing it with ["echo", "hello"] still breaks, so when the command is run its throwing a bus error

Reverting the core to<EMAIL_ADDRESS>"0.12.0", seems to not be throwing the error. Still on latest for the main package.

Sorry for all the comments. They don't seem to work together. this.core._free is not a function

You can add log: true to the options of FFmpeg.create(), this should log some useful information

I tried that,this code:
import { FFmpeg } from<EMAIL_ADDRESS>const ffmpeg = FFmpeg.create({
  log: true,
  logger: (level, message) => console.log(level, message),
});

Gives me:
node test.js
debug Import<EMAIL_ADDRESS>with cjs require()
[1]    39199 bus error  node test.js

Cloud you provide a more detailed system and environment info?
I can't reproduce this problem with nodejs v18.17.0 under Windows10 or Debian12.

Macbook Pro, 2021 Apple M1 Max.
Node v18.17.0
npm 9.6.7
<EMAIL_ADDRESS>"0.13.2",
<EMAIL_ADDRESS>"0.13.2",
<EMAIL_ADDRESS>"0.13.0"

I tried to replicate it here, but it does work. So maybe it's an apple silicon issue? https://codesandbox.io/p/sandbox/jolly-mccarthy-pmw9gd?file=%2Findex.js%3A8%2C1

I'm collecting data over here: https://github.com/wesbos/ff-me/issues/1
So far it seems to happen only on Mac OS, both intel and silicon chips.

The tests of the project also fail on Mac. Same error message.

Have you tried core-st? Will there still be the same error?

You can clone DreamOfIce/ffmpeg.wasm-core and uncomment this line:
https://github.com/DreamOfIce/ffmpeg.wasm-core/blob/6690593aa6b014dad266efa97293e32d27499c0c/wasm/bu ild-scripts/var.sh#L32
Then run ./build.sh to build debug version of the core.
Switch to the local core through pnpm add -D /path/to/ffmpeg.wasm-core /packages/core-mt/.
Then run the test again, and you should be able to see more detailed output.

It looks like this issue has been fixed in the latest v20.5.0
But not yet fixed in v18.17.0 LTS
https://github.com/wesbos/ff-me/issues/1#issuecomment-1666493226

It looks like this issue has been fixed in the latest v20.5.0 But not yet fixed in v18.17.0 LTS wesbos/ff-me#1 (comment)

Confirmed! This issue doesn't exist in Node 20.5.0 on Mac

looks like it's working on 20.5.0 - thank you everyone!


initializer with template does not set preProcess

my bad i was only setting the stopSequence

You're fast lol

oops, it wasn't fixed but fixed for real at 7a3ab0ccef86539817e6e543e08fae1f85814a85


Create a docker image for each bakery release

Preferably there should be a docker image for each bakery release but currently that is not the case.

Solved


SidePanel: add test for missing pageHeaderDescription prop

What will this achieve?
This will get coverage back up to 100% for the SidePanel. A new prop validator was added in this scenario and a test should also be added for this.

Complete


The status conditionals helper form operator-lib was removed and the docs were not updated

What did you do?
Check the doc:https://sdk.operatorframework.io/docs/building-operators/golang/advanced-topics/#manage-cr-status-conditions.
What did you expect to see?
It updated with the changes made in: https://github.com/operator-framework/operator-lib/pull/35
What did you see instead? Under which circumstances?
The doc with the outdated info.

@camilamacedo86
We still haven't upgraded k8s to 1.19+ and the metav1.Condition was released in k8s 1.19. That was the reason we reverted the docs, and have added a note instead in the same section:
NOTE: The status package was removed in operator-lib v0.2.0 in deference to the upstream metav1.Condition type, so your project must depend on version v0.1.0 to use status.Conditions:

go get<EMAIL_ADDRESS>

Really thank you for share that info here. It shows fine. So, we only an issue to track this need when the release gets done.

#3997 needs to be re-committed.
/assign @varshaprasad96

This depends on go/v3-alpha being stabilized, since this is the only plugin that will use k8s v1.19+.


How to restream?

Hello,
How i can i restream  with shoutcast and icecast here on azuracast?

Any update how to restream with azuracast?


Build Salt 2016.3.6 packages

Note: last release to support Redhat 5 and Ubuntu 12.04
[x]  Redhat 7
[x]  Redhat 6
[x]  Redhat 5
[x]  Debian 8
[x]  Debian 7
[x] Raspbian 8
[x] Ubuntu 16.04
[x] Ubuntu 14.04
[x] Ubuntu 12.04
There is no Fedora release since 2016.11 branch is latest for Fedora

Remember to update spec file and init scripts for changes applied to 2016.11 branch
see https://github.com/saltstack/salt-pack/issues/221 and https://github.com/saltstack/salt-pack/issues/190

Need to update version of Cherry Py shipped with Redhat 6, see https://github.com/saltstack/zh/issues/1207#event-1014939714 and https://github.com/saltstack/salt/issues/34234

@dmurphy18 If you don't already have an issue to track the update of CherryPy for RHEL 6 could you please open one and then close this? Thanks.


[BUG] Unconsumed parameter exception when authenticating with jwtUrlParameter

What is the bug?
Discovered this bug when analyzing https://github.com/opensearch-project/security/issues/3949. There is a regression in authentication with the jwtUrlParameter where it fails to consume the parameter and response with illegal_argument_exception: contains unrecognized parameter:
Suite: Test class org.opensearch.security.http.JwtAuthenticationTests
  2> java.lang.AssertionError: Expected status code is '200', but was '400'. Response body '{"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"request [/_opendistro/_security/authinfo] contains unrecognized parameter: [token]"}],"type":"illegal_argument_exception","reason":"request [/_opendistro/_security/authinfo] contains unrecognized parameter: [token]"},"status":400}'.
    Expected: <200>
         but: was <400>
        at __randomizedtesting.SeedInfo.seed([100EFB1C515D00AA:4401D6965CA5081E]:0)
        at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
        at org.opensearch.test.framework.cluster.TestRestClient$HttpResponse.assertStatusCode(TestRestClient.java:422)
        at org.opensearch.security.http.JwtAuthenticationTests.shouldAuthenticateWithJwtTokenInUrl_positive(JwtAuthenticationTests.java:163)

How can one reproduce the bug?
Set up and enable a JWT auth domain with the jwt_url_parameter set. Make any request with a valid token.
What is the expected behavior?
The jwt auth domain should successfully authenticate when jwt_url_parameter is supplied with a valid token.
Do you have any additional context?
The regression was introduced with the HeaderVerifier changes where the HTTP Authenticators are dealing with a lower-level request object than the SecurityRestFilter is where authc was previously being performed. The parameters must be consumed on the RestRequest and not the lower level NettyRequest which is used in the HeaderVerifier.

[Triage] Hi @cwperks thanks for filing this issue. This looks like a good fix to correct the regression.

https://github.com/opensearch-project/security/pull/3975 is now merged. Closing this issue.


overlap: false sometimes works

Hey, i'm testing overlap: false, on an Samsung Galaxy S4 works, on an iPhone 6 don't and on an LG L52 either.
Why that?

Cannot be re-produced, need more clues.


Ensure all crates have up to date Cargo.toml details

Same as https://github.com/gtk-rs/gtk4-rs/issues/311

Should be fixed


Clean and update packages

Describe your changes

Deletes yarn.lock in favor of preexisting package-lock.json

Since npm is the package manager referred to in the project documentation (yarn is not mentioned), I believe this is the best route to take.

Updates packages to address security vulns.

Ran npm update to do this. Only 3 moderate vulns should exist now.
npm run dev successfully runs project locally after the update.

Note for testers

the npm run build command doesn't currently work

Error output relates to the lack of a csv file's presence

NotFound [Error]: Not found: /knowledge-hub/ClimateTown-Knowledge-Hub-resources.csv

This same error would also produce itself with a yarn build command on the current main branch. I think it's a separate issue from this PR, but wanted testers to be made aware.

I can't get the dev container to work (hence why I'm running the project locally). I also think this is a separate issue from this PR, but wanted testers to be aware.

Related issue number/link

No open issues are resolved with this PR. It's more of a package refactoring to help ensure that the same build process is followed moving forward.

Thanks for the PR @jattiman !

the npm run build command doesn't currently work

This command should only be run in CI as it's to create the production build. For development run npm run dev (mentioned in readme :) )
Hmm, weird the codespaces isn't working. I'll make an issue

@all-contributors please add @jattiman for code


#render_association should add id to field name attributes in case of non-association inputs

The "new_#{association}" input name part is missing for inputs without associations.
I cannot find any docs on index and child_index fields_for options. The closest thing I have found is this comment.
The tests don't look like they test any interaction with rails, so can anyone confirm this does not break anything?

My bad: everything works fine without the change.

Great :+1:  Because I quickly skimmed this yesterday and had planned to take a deep dive to actually investigate what this change ment and why it would be needed anyway. Glad to hear it is not 😉
Could you, for clarity, give an example how you are using it? Because in general cocoon is intended for using with associations, if you use it without I am pretty there is a lot of glue you have take care of?
For instance PR #223 was posted to allow use of normal arrays instead of ActiveRecord models, but I have never merged it because it needs a lot more documentation and having to maintain an edge-case like that, but maybe I should finally get round to actually merging it 😜


Fix showAsLink() Links to Wrong Resource on Detail Page

Update showAsLink($model) to use the passed model when generating the link to the resource on the detail page, just like how it does on the index page.
Refs koss-shtukert/laravel-nova-select2-auto-complete#5

Thank you @MitchellMcKenna !


Views are disappearing or not registering!

Is there an existing issue for this?

[X] I have searched the existing issues

I'm submitting a ...

[X] bug report
[ ] feature request
[ ] support request --> Contact me over mail for support https://github.com/MShawon

Description
Hello Dear,
I have been using the code for while now, and after proper testing, I have found out that the total amount of views that the logs are displaying is not the same amount of views that is counted by youtube and displayed on the video (The difference is massive). For instance, the total number of views on the logs was 4200 views, and on youtube, only counted 2400 views.
The second issue is that one of the videos had about 3500 views yesterday, I woke up today and it was only 1700 views. Meaning that the views are disappearing as well.
I'm using premium proxies from Webshare, and I made sure to follow all the steps in the guides, so they are of this format ipaddress:port:username:password.
Environment
- OS : Windows 10
- Python : Python 3.9
- Script version : 1.7.4

config.json
Here's my config settings:
>     "http_api": {
>         "enabled": true,
>         "host": "<IP_ADDRESS>",
>         "port": 5000
>     },
>     "database": true,
>     "views": 2000,
>     "minimum": 60.0,
>     "maximum": 85.0,
>     "proxy": {
>         "category": "p",
>         "proxy_type": "http",
>         "filename": "proxy_1.txt",
>         "authentication": true,
>         "proxy_api": false,
>         "refresh": 0.0
>     },
>     "background": false,
>     "bandwidth": false,
>     "playback_speed": 1,
>     "max_threads": 5,
>     "min_threads": 4

How many proxies you are using? On How many videos you run the bot?

I'm currently using 6000 proxies, and I'm running the bot usually on 1 or 2 videos.

You must put at least 3 different video links in the urls.txt if you want to avoid view drop

I see, could you explain the reason for that?

First of all if only 1 video are getting views constantly it will give away as a bot
Second the most powerful anyone can ever ask for a traffic source is the SUGGESTED VIEWS.. to get that you must put 2 video links so one video will suggest another one.. more video link you put more difficult to detect it as a bot..imo you should use at least 3 video at a time

Okay, thanks a lot mate!

Hi. Decrease the playback speed to 0.5 . It will lower the drop views.


NIFI-2688 - adjust ConfigEncryptionToolTest datePattern regex to cate…

regex to cater for timezones with 4 characters

I submitted PR 974 which handles 2 - 5 character time zones. If that PR is approved, please close this one.

I've seen it. Seems very good PR. Closing

Thanks @trixpan .


Health site displays location name for another health site

Health site in Zimbabwe (and many other countries where location name is missing in the data set) displays location name for health site in Rwanda. This looks like a display field that's not being initialised in the health site information panel.

could you share the link to this healthsite @brenb ?

I cannot replicate the issue you mention. We do not import locations without mandatory fields. healthsite [name] is mandatory:
https://github.com/healthsites/healthsites/wiki/Healthsite-attributes

Follow these steps:

To show that this health site in Zimbabwe currently has no District
info, refresh your browser, then visit
http://staging.healthsites.io/map#!/locality/2b38c9cfef1540f28a14165bc437a4c8

2 Visit a health site in Rwanda with District info eg
http://staging.healthsites.io/map#!/locality/21e3fae50c504cb2b5415dc3bee6a0a9

Return to the health site in Zimbabwe and you will see District info for
the Rwandan health site incorrectly displayed for the Zim health site
http://staging.healthsites.io/map#!/locality/2b38c9cfef1540f28a14165bc437a4c8

Looks like variables are not being initialised when you click to display
info on different health sites.
On 26 November 2015 at 16:06, Mark Herringer<EMAIL_ADDRESS>wrote:

I cannot replicate the issue you mention. We do not import locations
without mandatory fields. healthsite [name] is mandatory:
https://github.com/healthsites/healthsites/wiki/Healthsite-attributes
—
Reply to this email directly or view it on GitHub
https://github.com/healthsites/healthsites/issues/339#issuecomment-159923589
.

ok. great thanks. I can see the issue now. The name changes but the district info stays the same.

@markherringer @brenb
i could reproduce it. That is because the old one didn't re-rendering the show panel again for default. That why when the information is not provided, the view is still in previous information.
I already made PR for this issue.


WASM integration

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Summary 💡
As a user focused more on back end development (hence my interest in Toolpad), I would like to be able to call WASM functions that I have exposed to javascript and either:

Return data directly to the calling function
OR (preferably)
Use WASM to write to local storage, and then reference the data via toolpad

Examples 🌈
No response
Motivation 🔦
I built a web application that is very calculation intensive (financial modelling), and the backend is written in Go (front end in AngularJS). I would like to rebuild the front end in toolpad, while calling the Go backend via wasm. This would allow me to move calculations off the server, and thus reduce costs while increasing performance.
In order to get wasm to work, you only need to a small amount of boiler plate js - fetching the js/wasm 'glue code', fetching the wasm binary, and one script to instantiate the wasm module.

I'm opening a PR that proposes an example demonstrating how one could call WASM modules with Toolpad. Let me know whether it's be useful to you.

Yes, that's certainly useful to me - thanks for reaching out!
From: Jan Potoms @.>
Sent: Sunday, September 17, 2023 18:51
To: mui/mui-toolpad @.>
Cc: oganator @.>; Author @.>
Subject: Re: [mui/mui-toolpad] WASM integration (Issue #2699)
I'm opening a PRhttps://github.com/mui/mui-toolpad/pull/2700 that proposes an example demonstrating how one could call WASM modules with Toolpad. Let me know whether it's be useful to you.

Reply to this email directly, view it on GitHubhttps://github.com/mui/mui-toolpad/issues/2699#issuecomment-1722517860, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMNMBAOGLOOWKJVSOCBRD5DX24TATANCNFSM6AAAAAA43VMXUQ.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>

As for this issue, I believe for the future we can think about introspecting .wasm files in the resources folder and exposing them to queries in the frontend.

Hey @oganator,
Did you get a chance to check out the WASM example?


Fix missed import reference updates in asapdiscovery-data.

Fixes #940.

Sorry for pinging everyone, just need a quick green check here

Codecov Report

Merging #941 (86a56ea) into main (026c320) will increase coverage by 8.95%.
The diff coverage is n/a.

Additional details and impacted files


Don't curry transducers

Reason? It's a small simplification with no drawbacks.
It also allows _dispatchable to access the transducers classes' directly.

I will take a closer look this weekend.  There is a build error to deal with, probably because of the arrow function.


Improve compilation time

Compilation time can be shortened if the metamodel for the language and browser modules can be somehow reused with all typechecker instances.

Is this still needed @chochos ? It seems to me that it's pretty fast right now.

Yeah I think we can close this now.


FIX: missing kappa in the integrand for TubeInflation.

This would only affect results when there is an opening angle

Thanks Ross. I am not sure why the MacOS tests are failing. The errors are "Error: Version 3.* with arch x64 not found". Any idea?

Maybe something needs updated in terms of the runners. It might be related to this: https://stackoverflow.com/questions/71577626/issues-installing-python-3-8-10-on-macos-12-3-monterey

Thanks Ross. I am not sure why the MacOS tests are failing. The errors are "Error: Version 3.* with arch x64 not found". Any idea?

Found the issue. Updating the @v* in ci-tests.yml fixes it. I have created another pull request for that.


DISTX-474 Schedule-Based downscaling integrated with YarnResponse

Schedule-Based Downscaling integrated with Yarn Response.
Yarn Scaling Response refactored to be reused between Schedule-Based and Load-Based Autoscaling.

Looks good. Let's think more on the downscale though. Have left a comment - if that makes sense, it would be good to integrate that change (maybe as a future PR)

Updated code to pass clusterSize for retrieving Yarn Downscaling Recommendation as discussed during meeting.

This PR is continued in PR-8618 targeting CB-2.26.0 branch for experian demo.


The logic of the run button is incorrect

Brief Issue Summary
Windows version: windows 10 22H2
VS Code version: 1.81.0
CMake tools version: 1.61.0
When using the CMake extension, if I launch an executable using the start button on the status bar, according to the normal usage logic, the CMake extension should only compile the executable and its related build options. However, the extensionalso compiles the selected build options in the build button, which clearly contradicts the usual usage habit and expectation.
As shown in the figure below, I have selected the program "camera_with_mouse" to run. In the build options, I have selected "camera_practice_two". Based on the output, it can be seen that CMake Tools compiled both of the above options. However, the executable program in the build option does not require compilation.

CMake Tools Diagnostics
No response
Debug Log
No response
Additional Information
No response

Thanks for the post @SAquarius!
I have been able to repro, and it seems like the issue is similar to what you have stated, upon attempting to run the target, we attempt to build in order to ensure that the target is built. However, this may cause confusing behavior if you have a situation like the one you are describing.
Marking this as a bug and putting it in our backlog.

I hope that instead of fixing this, the run and debug logic will be merged with the vscode-cpptools seamlessly. I think there were feature requests to do that and even a member of MS made a ticket to do that.


Supporting RTL and fixed height !

Is the drop down menu supporting RTL if the language is RTL !
Can i set limit of the items to show or some constraint on the bottom of the view !

+1


update readMe file

What does this PR do?

update readme file

Description of Task to be completed?

Format readme file properly
Add test coverage badge

How should this be manually tested?

View the readme file at the base of the repo

Coverage remained the same at 83.407% when pulling 1c62cd678647e35b9d1719661772a087b37d33a3 on add-readMe into f810ce97094a99c0d404cf5b39a2a9f5e993bdf9 on development.


refactor: remove nodejs module util

[x] remove util module, make tapable can be run on browser
[x] remove browser configure in package.json, becaure all code can be run on nodejs and browser

to avoid error below in webpack 5:

We already supports browser https://github.com/webpack/tapable/blob/master/package.json#L31

We already supports browser https://github.com/webpack/tapable/blob/master/package.json#L31

not valid config for webpack 5.

There is only 1 api which is from nodejs util. There is absolutely no need to use built-in modules, and then modify the building config for browsers.
The right way is remove the built-in module and directly use the polyfill code.

Now, we solve it by below code, very dirty
module.exports = {
  mode: 'production',
  entry: './src/index.ts',
  output: {
    library: 'Spreadsheet',
    libraryTarget: 'umd',
    filename: 'spreadsheet.min.js',
  },
  resolve: {
    extensions: ['.ts', '.tsx', '.js'],
    fallback: {
      // use polyfill util code from `tapable`
      util: require.resolve('tapable/lib/util-browser.js'),
    },
  },
  plugins: [
  ],
  module: {
    rules: [
      { test: /\.tsx?$/, loader: 'ts-loader' }
    ]
  },
  externals: {
  },
};

The right way is remove the built-in module and directly use the polyfill code.

No, I can't reproduce your problem... Maybe you can provide full example?

The right way is remove the built-in module and directly use the polyfill code.

No, I can't reproduce your problem... Maybe you can provide full example?

I have no time to provide full example. In terms of code rationality, the best way to support the browser is to delete util, to avoid the dependence of build configure.
I can support browsers directly. Why do I  need to rely on building?

way to reproduce:

create pkg A dependence tapable, then release it with esm cjs
create pkg B dependence A, then build umd with webpack

"ts-jest": "^24.3.0",
"ts-loader": "^9.2.6",
"typescript": "^4.4.2",
"webpack": "^5.64.4",
"webpack-cli": "^4.9.1"

Why do your bundle tapable? Do you use it in your application?

Why do your bundle tapable? Do you use it in your application?

antv/g depends on tapable, I am using antv/g to dev an module which should be used in browser by script.

There is only one problem - tracking depredations on Node.js using CLI, but I think it is not real problem...


character generator

uuid seeded character generator with common -> unique generation based on aria's tale d20 rarity rules
the character generator must be versioned. uuid+generator version should always return the same rarity, stats, and other details
v1 generates these fields:

rarity
level
stat point distribution
gear check
awakening region
race
gender
class
backstory
memcheck

rolling a unique character bestows a unique character soul and a bonus character of non-unique rarity (double unique roll bestows unique-1 rarity, currently epic). unique character souls will be usable later, not in this user story. for now, just attach it to the user account as a sort of currency.
if memcheck passes then the user can pick some overrides. override data should be stored separately from the reproducible uuid+generator output snapshot. we can later add monitoring to ensure no profanity in the name:

character name
race
gender
class
stat point distribution

user can also update these fields at any time whether or not memcheck passes:

user notes (private string)
ready to play (private bool meaning the user wants to be notified if the character is encountered in canon and would be willing to play their character)

here's another character data which is not user-controlled:

canon episodes (public id list)
canon notes (public string)
user id relation to character uuid, created at, updated_at

the generator should also be ai-tool-aligned
so i should be able to feed a list of uuids to currently-official ai tool(chain) and get that stuff just-in-time at playtime as well
also, characters have character art. Both kinds are versioned lists:

canon art
fan art

by default a character is locked to the current canon art. user can buy additional art slots and store fan art and/or generate additional canon snapshots
v1 stats include:

health points
skill points
speed
movement points (derived from speed)
attack
magic attack
defense
magic defense

complex stats not used in simple battle mode, but used in role-play (and possibly in complex or narrative battle)
probably only worth calculating these if a character is brought in to an actual session. separate db table

charisma
intelligence
strength
dexterity
big 5 personality traits (scale of 20)
religious preference matrix (scale of 20, per religion, a strong bias to prefer only one)
reputation matrix (base of 0 unbounded in either direction)

also, a backstory can have a few forms:

simple deterministic
detailed deterministic
canonized

and religious preference matrix is overridable on memcheck

v1 races (more in future versions):

human
orc, half-orc
elf, half-elf
demon
dragon
merfolk
dwarf, half-dwarf
goblin
beastfolk: frogfolk, birdfolk, wolfkin, catkin, lizardkin
angel

half-elf etc are uncommon
some rares: lionkin (special catkin), flightless birdkin, half-angel, half-demon, half-dragon

v1 classes

warrior
mage
archer
priest
blacksmith
chef
paladin
farmer
fisher
merchant
alchemist
enchanter
elementalist
thief
woodworker
barbarian
spearman
sailor
explorer
hunter
herbalist
miner
entertainer
bard (background: maybe a singer, instrumental musician, band member, or singer-songwriter)
tailor
prophet
oracle
sealer
druid
athlete
commander
guard
summoner
tamer
judge
lumberjack

we need to have a uuid -> die roll converter. also these classes are not all equally common

lore: awakening regions: everyone awoke between levels -1 and 7. no one went "beyond heaven and hell" in fact no one knew there were levels or higher and lower circles and sibling worlds until the great vision and the stumbling...although on second thought a rare few technical folks with memory think it makes sense due to the distributed game architecture...

More classes

Healer (background: battlefield medic? Surgeon? Spiritual healer? Medical doctor? Pharmacist? I smell multi classing!!)
Scholar (background: what kind? Historian, linguist, biologist, geologist?)
Noble
Emissary

More

Martial artist (lots of special forms)
Clayworker? Is that stupid? Pottery person? Seems like a specialized merchant and we already have merchant. But hey specializing is ok. So also jeweler then. And brewer.
Connoisseur

race = treant
wraith = class / condition / ailment...also vampirism and werewolf
lore: How to aquire wriathhood? one way is by exposure over time.

memcheck and some other items still missing.


src:prodserver fails with when using: --nolegacy_external_runfiles

Using bazel version 0.16.0 on commit e5560ae155c93f844112fc554603937d0a6a560b bazel run --nolegacy_external_runfiles //src:prodserver fails to launch.  The root issue appears to be issue in the nodejs rules and how they resolve paths, but I wanted to start in this project in case I missed something.
Here is a full reproduction:
$ yarn install
...
$ bazel run --nolegacy_external_runfiles //src:prodserver
INFO: Analysed target //src:prodserver (0 packages loaded).
INFO: Found 1 target...
Target //src:prodserver up-to-date:
  dist/bin/src/prodserver_bin.sh
  dist/bin/src/prodserver
INFO: Elapsed time: 0.450s, Critical Path: 0.01s
INFO: 0 processes.
INFO: Build completed successfully, 1 total action
INFO: Build completed successfully, 1 total action
/home/jlisee/.cache/bazel/_bazel_jlisee/a3cee343d71b0f2101c79d88606a48aa/execroot/angular_bazel_example/bazel-out/k8-fastbuild/bin/src/prodserver: line 139: source: filename argument required
source: usage: source filename [arguments]

From my digging it looks like the way paths our resolved in the nodejs rules it needs runtree layout like:
prodserver.runfiles/nodejs/bin/nodejs/bin/node
prodserver.runfiles/nodejs/bin/node
prodserver.runfiles/__main__/external/nodejs/bin/nodejs/bin/node
prodserver.runfiles/__main__/external/nodejs/bin/node

Instead of just (which you get with the nolegacy flag):
prodserver.runfiles/__main__/external/nodejs/bin/nodejs/bin/node
prodserver.runfiles/__main__/external/nodejs/bin/node

Oh, thanks for the heads up. I didn't know there was a legacy layout in the runfiles, we'll need to adapt for it in rules_nodejs. Filed the linked issue there

Thanks for the find. This should fix this issue: https://github.com/bazelbuild/rules_nodejs/pull/380
Also related is a fix for karma to work with this flag: https://github.com/bazelbuild/rules_typescript/pull/309/files
And a fix for protractor will be required as will in the angular/angular repo

Resolved in #227


Firefly 1.3.3[Bug report]:

Version
1.3.3
Description
App Version: 1.3.3
platform: linux
platformVersion: 6.5.0-28-generic
platformArchitecture: x64
cpuCount: 8
totalMem: 15731.5 MB
freeMem: 282.0 MB
Error Type: Callback Error createAccount
TypeError: Cannot read property 'usd' of null
at Us (file:///tmp/.mount_firefleAxpOg/resources/app.asar/public/build/index.js:2:2114550)
at onSuccess (file:///tmp/.mount_firefleAxpOg/resources/app.asar/public/build/index.js:2:2109486)
at Function.t.. (file:///tmp/.mount_firefleAxpOg/resources/app.asar/public/build/index.js:2:2108132)
Expected behaviour
Recover wallet
Actual behaviour
crash
Can the issue reliably be reproduced?
Yes
Steps to reproduce the issue
After putting new password it crash
Operating System
Linux
Diagnostics
App Version: 1.3.3

platform: linux
platformVersion: 6.5.0-28-generic
platformArchitecture: x64
cpuCount: 8
totalMem: 15731.5 MB
freeMem: 282.0 MB

Error Type: Callback Error createAccount

TypeError: Cannot read property 'usd' of null
    at Us (file:///tmp/.mount_firefleAxpOg/resources/app.asar/public/build/index.js:2:2114550)
    at onSuccess (file:///tmp/.mount_firefleAxpOg/resources/app.asar/public/build/index.js:2:2109486)
    at Function.t.<computed>.<computed> (file:///tmp/.mount_firefleAxpOg/resources/app.asar/public/build/index.js:2:2108132)

Developer Profile
No
Profile Type
Software (Stronghold)
Staking
None
Crash Status
None of the above
Error Messages
No response
Error Logs
App Version: 1.3.3

platform: linux
platformVersion: 6.5.0-28-generic
platformArchitecture: x64
cpuCount: 8
totalMem: 15731.5 MB
freeMem: 282.0 MB

Error Type: Callback Error createAccount

TypeError: Cannot read property 'usd' of null
    at Us (file:///tmp/.mount_firefleAxpOg/resources/app.asar/public/build/index.js:2:2114550)
    at onSuccess (file:///tmp/.mount_firefleAxpOg/resources/app.asar/public/build/index.js:2:2109486)
    at Function.t.<computed>.<computed> (file:///tmp/.mount_firefleAxpOg/resources/app.asar/public/build/index.js:2:2108132)

Duplicate declaration

[X] I have searched the issues tracker this issue and there is none

Code of Conduct

[X] I agree to follow this project's Code of Conduct

You should update your wallet to the newest version, 1.3.3 is not compatible with the network upgrade that happened in Octobot 2023. The latest version we have at the time of writing this comment is V2.0.9. You can find the latest version in the official website https://firefly.iota.org/


User/Customer Journey Mapping

User Journey Mapping
Customer Journey Mapping

Optimizing The Website Customer Journey
https://thecxlead.com/topics/website-customer-journey/


Expand array in json root

What type of PR is this：

[ ] bug
[ ] feature
[x] enhancement
[ ] others

Which issues of this PR fixes ：

Fixes #4307
Problem Summary(Required) ：

{
	"data": [{
		"key": 1
	}, {
		"key": 2
	}]
}

This PR adds support for the parse of json showed above, with json root $.data and strip_outer_array=true.

@Mergifyio backport branch-2.2

@mergifyio backport branch-2.2

@Mergifyio backport branch-2.1


fill the 'properties' attribute of every resource

Currently the 'properties' attribute of all resources that are read from Kubernetes/Docker is populated with the corresponding data. However, the 'properties' attribute of synthetic resources such as 'Cluster' is not defined.
We should define the 'properties' attribute of all resource types to enable uniform verification of all resource objects.
We should enhance to unit tests to verify that all resource objects have 'properties'.

Closed by https://github.com/google/cluster-insight/pull/52.


Bail End to End Flow -Test cases Preparation

Prepare the test cases for the : https://github.com/pucardotorg/dristi/issues/2754
Reference: https://docs.google.com/document/d/16GronAliCazzXEbM5JyaZGpWGRRoQRllmwNtVv8NcFQ/edit?tab=t.nqwxjqalgvqn

Hi @rajeshcherukumalli, I have prepared the Test scenarios and Test cases for the Bail End to End Flow according to the PRD provided. Please review the document and ping me if any updates are required.
Link to the sheet: Bail 2.0 End to End Test Cases


Add demo code for adding splash view

Someone requested for code on how to add a splash view for when app is in task switcher.
Code is not the best one as I didn't had much time now, but is a working example. I might add more later this month.
@velikanov if you want merge this PR.

:+1: thank you


Update smtp.md

The documentation contains an incorrect port for Yandex smtp. Corrected

@UnderC0de Isn't the port 587 for TLS connection?

@maxlazio , Yandex help system:
https://yandex.ru/support/mail-new/mail-clients.html

Outgoing mail
     The address of the mail server is smtp.yandex.ru;
     Connection protection - SSL;
     Port - 465.

When using port 587, we get the error:
OpenSSL::SSL::SSLError: SSL_connect returned=1 errno=0 state=SSLv2/v3 read server hello A: unknown protocol
Probably TLS works on port 465 instead of SSL. But port 587 does not work as expected in the Gitlab documentation, and its support is not declared in Yandex help system.

@UnderC0de Thanks for the update.


Speech sample ios not working

HI
I am using the speech sdk in unity3d fr android, desktop and ios. In android and editor sample is working finebut in ios it showing error.
SpeechTranscriber:StartRecording()
SpeechTranscriber:Start()

(Filename: ./Runtime/Export/Debug/Debug.bindings.h Line: 35)

Error: Time:Mon Jul 13 14:21:11 2020 File:/Users/runner/runners/2.165.2/work/1/s/source/core/audio/osx/audio_sys.cpp Func:logOSStatusError Line:140 Error: AudioQueueStart failed (-50)

Info: Connect: entering...

Info: Adding subscription key headers

Info: connectionUrl=wss://centralindia.stt.speech.microsoft.com/speech/recognition/conversation/cognitiveservices/v1?language=en-us

Info: Create requestId  for messageType 0

Info: TransportDoWork: open transport.

Info: Start to open websocket. TransportRequest: 0x2180d330, wsio handle: 0x80cad8c0

ApplicationException: Exception with an error code: 0x15 (SPXERR_MIC_ERROR)
at Microsoft.CognitiveServices.Speech.Internal.SpxExceptionThrower.ThrowIfFail (System.IntPtr hr) [0x00000] in <00000000000000000000000000000000>:0
at Microsoft.CognitiveServices.Speech.Recognizer.StartContinuousRecognition () [0x00000] in <00000000000000000000000000000000>:0
at System.Action.Invoke () [0x00000] in <00000000000000000000000000000000>:0
at Microsoft.CognitiveServices.Speech.Recognizer.DoAsyncRecognitionAction (System.Action recoImplAction) [0x00000] in <00000000000000000000000000000000>:0
at Microsoft.CognitiveServices.Speech.SpeechRecognizer.b__44_0 () [0x00000] in <00000000000000000000000000000000>:0
at System.Action.Invoke () [0x00000] in <00000000000000000000000000000000>:0
at System.Threading.Tasks.Task.InnerInvoke () [0x00000] in <00000000000000000000000000000000>:0
at System.Threading.Tasks.Task.Execute () [0x00000] in <00000000000000000000000000000000>:0
at System.Threading.Tasks.Task.ExecutionContextCallback (System.Object obj) [0x00000] in <00000000000000000000000000000000>:0
at System.Threading.ContextCallback.Invoke (System.Object state) [0x00000] in <00000000000000000000000000000000>:0
at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <00000000000000000000000000000000>:0
at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <00000000000000000000000000000000>:0
at System.Threading.Tasks.Task.ExecuteWithThreadLocal (System.Threading.Tasks.Task& currentTaskSlot) [0x00000] in <00000000000000000000000000000000>:0
at System.Threading.Tasks.Task.ExecuteEntry (System.Boolean bPreventDoubleExecution) [0x00000] in <00000000000000000000000000000000>:0
at System.Threading.Tasks.Task.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem () [0x00000] in <00000000000000000000000000000000>:0
at System.Threading.ThreadPoolWorkQueue.Dispatch () [0x00000] in <00000000000000000000000000000000>:0
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () [0x00000] in <00000000000000000000000000000000>:0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x00000] in <00000000000000000000000000000000>:0
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x00000] in <00000000000000000000000000000000>:0
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x00000] in <00000000000000000000000000000000>:0
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x00000] in <00000000000000000000000000000000>:0
at System.Runtime.CompilerServices.TaskAwaiter.OnCompletedInternal (System.Threading.Tasks.Task task, System.Action continuation, System.Boolean continueOnCapturedContext, System.Boolean flowExecutionContext) [0x00000] in <00000000000000000000000000000000>:0
at SpeechTranscriber+<>c.b__39_0 (System.Char c) [0x00000] in <00000000000000000000000000000000>:0
at System.Runtime.CompilerServices.AsyncMethodBuilderCore+MoveNextRunner.InvokeMoveNext (System.Object stateMachine) [0x00000] in <00000000000000000000000000000000>:0
at System.Threading.ContextCallback.Invoke (System.Object state) [0x00000] in <00000000000000000000000000000000>:0
at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <00000000000000000000000000000000>:0
at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <00000000000000000000000000000000>:0
at System.Runtime.CompilerServices.AsyncMethodBuilderCore+MoveNextRunner.Run () [0x00000] in <00000000000000000000000000000000>:0
at System.Action.Invoke () [0x00000] in <00000000000000000000000000000000>:0
at System.Threading.Tasks.AwaitTaskContinuation.RunOrScheduleAction (System.Action action, System.Boolean allowInlining, System.Threading.Tasks.Task& currentTask) [0x00000] in <00000000000000000000000000000000>:0
at System.Threading.Tasks.Task.FinishContinuations () [0x00000] in <00000000000000000000000000000000>:0
at System.Threading.Tasks.Task.FinishStageThree () [0x00000] in <00000000000000000000000000000000>:0
at System.Threading.Tasks.Task.FinishStageTwo () [0x00000] in <00000000000000000000000000000000>:0
at System.Threading.Tasks.Task.Finish (System.Boolean bUserDelegateExecuted) [0x00000] in <00000000000000000000000000000000>:0
at System.Threading.Tasks.Task.ExecuteWithThreadLocal (System.Threading.Tasks.Task& currentTaskSlot) [0x00000] in <00000000000000000000000000000000>:0
at System.Threading.Tasks.Task.ExecuteEntry (System.Boolean bPreventDoubleExecution) [0x00000] in <00000000000000000000000000000000>:0
at System.Threading.Tasks.Task.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem () [0x00000] in <00000000000000000000000000000000>:0
at System.Threading.ThreadPoolWorkQueue.Dispatch () [0x00000] in <00000000000000000000000000000000>:0
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () [0x00000] in <00000000000000000000000000000000>:0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x00000] in <00000000000000000000000000000000>:0
at System.Runtime.CompilerServices.AsyncMethodBuilderCore+<>c.b__6_0 (System.Object state) [0x00000] in <00000000000000000000000000000000>:0
at System.Threading.SendOrPostCallback.Invoke (System.Object state) [0x00000] in <00000000000000000000000000000000>:0
at UnityEngine.UnitySynchronizationContext.Exec () [0x00000] in <00000000000000000000000000000000>:0
at UnityEngine.UnitySynchronizationContext.Exec () [0x00000] in <00000000000000000000000000000000>:0
at UnityEngine.UnitySynchronizationContext.ExecuteTasks () [0x00000] in <00000000000000000000000000000000>:0
UnityEngine.DebugLogHandler:Internal_LogException(Exception, Object)
UnityEngine.DebugLogHandler:LogException(Exception, Object)
UnityEngine.Logger:LogException(Exception, Object)
UnityEngine.Debug:LogException(Exception)
UnityEngine.UnitySynchronizationContext:Exec()
UnityEngine.UnitySynchronizationContext:Exec()
UnityEngine.UnitySynchronizationContext:ExecuteTasks()

(Filename: currently not available on il2cpp Line: -1)\
Can you help me with this.

@prabhu22ap Thanks for feedback, these should be set by default in the sample, but could you check you have following options set:

Microphone Usage Description, enter the reason for accessing microphone
Prepare iOS for Recording, enable this setting
To find these settings, look at:
https://docs.unity3d.com/Manual/PlayerSettingsiOS-Other.html

Let us know if this helps.

Thank you for your response. I have only added the microphone usage description. I haven't enabled Prepare iOS for Recording.
I will check and let you know if the issue gets resolved.

Thank you its working.


MS SQL - Can't open 'http://dbeaver.jkiss.org/files/jdbc/drivers/mssql/sqljdbc4.jar': Moved Permanently Can't open 'http://dbeaver.jkiss.org/files/jdbc/drivers/mssql/sqljdbc4.jar': Moved Permanently

Can not connect to MS SQL database with the latest version because I can not download the drivers.

Recently dbeaver.jkiss.org migrated to HTTPS protocol - that's why old links are no longer work.
Drivers config will be fixed in the next version.
Workaround: Preferences->Database->Drivers.
Add file repository https://dbeaver.jkiss.org/files/jdbc/ and remove old repository http://dbeaver.jkiss.org/files/jdbc/

Thanks.
On Wed, Aug 16, 2017 at 2:55 PM, Serge Rider<EMAIL_ADDRESS>wrote:

Recently dbeaver.jkiss.org migrated to HTTPS protocol - that's why old
links are no longer work.
Drivers config will be fixed in the next version.
Workaround: Preferences->Database->Drivers.
Add file repository https://dbeaver.jkiss.org/files/jdbc/ and remove old
repository http://dbeaver.jkiss.org/files/jdbc/
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/serge-rider/dbeaver/issues/2024#issuecomment-322866532,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ASigYzBrHbIv1z4b1pgRNIui1D2CaSA4ks5sYzs2gaJpZM4O5GdT
.

--
Timothy D. Glover
B.S. Computer Science
Sr. Software Engineer
Walt Disney Parks & Resorts Technology

forbiden?


GOV.UK Prototype Kit user survey

What
Create and release the user survey
Who needs to review this
Team to review drafted survey when ready
Done when

[ ] Survey drafted
[ ] Survey reviewed
[ ] Survey released

@alinagraham shall we close this one

Yes - this is fine to close now On 20 Apr 2023, at 17:48, Joe Lanman @.***> wrote:
@alinagraham shall we close this one?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>


Update ember and ember-data to 2.17. Fix deprecations.

Hi @dustinfarris! I did upgrade to addon with ember-cli-update. Fixed deprecations. Could you test and merge it if all works well?
Closes #205 and #206
UPD. Tests are passing locally but I am trying to fix them at CI.
UPD. @dustinfarris could you check CI settings please? Seems some very old image is used. Ping me so we can resolve issue together.

@kolybasov thank you so much for this!
You're right, CircleCI was running on a Ubuntu 12.04 image that doesn't come with yarn.  I updated the setting to 14.04 (with yarn) and made a slight modification to circle.yml based on their docs.

@dustinfarris thanks for the fix! Let me know if I need to made some changes to merge this.

@kolybasov all good!  really can't thank you enough for putting time into getting this done. 💙💙💙
will do a major version release since the supported versions of Ember have changed


fix(ffe-buttons-react): Restrict isLoading prop

BREAKING CHANGE: Removed support for isLoading from any button
other than ActionButton, PrimaryButton and SecondaryButton.
This commit removes support for the isLoading prop for all other
buttons, meaning they will not be disabled or act any differently
if given an isLoading prop of true or false.
If you are using isLoading with any other kind of button you need
to sit down with design/ux and either start using one of those
three button types or figure out another way to show a loading indicator.

Coverage increased (+0.06%) to 79.388% when pulling 946d6bac3f1852207f37d601408b9ac5126c940c on ivarni:no-spinnable-shortcuts into 2b87e23e07d4a1bda8192a91a22e3b41a8033547 on SpareBank1:develop.

0.06% increased coverage! 💪


Added methods to get experiments, runs and metrics

Resolves
Fixes #38
Fixes #39
Fixes #40
Description
Add methods to get experiments, runs and metrics populated with navigation dependencies

@AnoojNair / @dcostea this is ready for your review

:shipit:

Thanks for the review @lqdev!


cannot use RWKV models

I just tried to use the current version of "llama-node" with the "rwkv.cpp" backend and failed.
The link found in the docs where I should be able to download RWKV models points to nowhere.
Since I could not find pre-quantized models anywhere, I followed the instructions found in the rwkv.cpp repo to download, convert and quantize the 1.5B and 0.1B models - I even uploaded them to HuggingFace.
Then, I copied the example found in your docs added a path to my quantized model, changed the template and tried to run the result.
Unfortunately, I got nothing but an error message:
llama.cpp: loading model from /Users/andreas/rozek/AI/RWKV/RWKV-5-World-0.1B-v1-20230803-ctx4096-Q4_1.bin
error loading model: unknown (magic, version) combination: 67676d66, 00000065; is this really a GGML file?
llama_init_from_file: failed to load model
node:internal/process/promises:288
            triggerUncaughtException(err, true /* fromPromise */);
            ^

[Error: Failed to initialize LLama context from file: /Users/andreas/rozek/AI/RWKV/RWKV-5-World-0.1B-v1-20230803-ctx4096-Q4_1.bin] {
  code: 'GenericFailure'
}

Node.js v18.17.0

Do you have any idea what could be wrong?

I just learned that RWKV-5 models are not yet supported by rwkv.cpp.
So I tried RWKV-4 instead - took the .pth model and converted it to .bin following the docs. Unfortunately, however, the result is the same:
llama.cpp: loading model from /Users/andreas/rozek/AI/RWKV/RWKV-4-World-0.1B-v1-20230520-ctx4096.bin
error loading model: unknown (magic, version) combination: 67676d66, 00000065; is this really a GGML file?
llama_init_from_file: failed to load model
node:internal/process/promises:288
            triggerUncaughtException(err, true /* fromPromise */);
            ^

[Error: Failed to initialize LLama context from file: /Users/andreas/rozek/AI/RWKV/RWKV-4-World-0.1B-v1-20230520-ctx4096.bin] {
  code: 'GenericFailure'
}

Node.js v18.17.0

Using the same model with python python/generate_completions.py /rwkv/RWKV-4-World-0.1B-v1-20230520-ctx4096.bin from rwkv.cpp works, however

I just found a section in th rwkv.cpp README.md which says:

⚠ Python API was restructured on 2023-09-20, you may need to change paths/package names in your code when updating rwkv.cpp.

may this be the reason for misbehaviour?

FYI: I just used the version of rwkv.cpp from from Sept, 20th (before they restructured the Python API) and tried again - with the same results.
Which means: no, the API restructuring is not the reason for not loading the RWKV model

FYI: going back to the latest commit (of rwkv.cpp) before "update ggml" fails because the resulting code can not be compiled.
Thus, in order to test if "llama-node" does work with RWKV actually means to go back to commit "update ggml" (8db73b1) and manually revert any changes related to GGML
Damn...

Hi!
The module rwkv-cpp in llama-node explicitly points to a specific version of rwkv.cpp: rwkv.cpp @ 363dfb1. In turn, this version of rwkv.cpp explicitly points to a specific version of ggml: ggml @ 00b49ec. For all of this to work, I highly recommend not using newest/arbitrary versions of the packages, and stick to the ones that are explicitly referenced -- that way, everything should be compatible with each other.

If it helps debugging, for some reason llama.cpp loads the RWKV file, not rwkv.cpp:
llama.cpp: loading model from /Users/andreas/rozek/AI/RWKV/RWKV-4-World-0.1B-v1-20230520-ctx4096.bin

That was quick - thank you very much.
Unfortunately, I cannot get rwkv.cpp @ 363dfb1 to compile.
Unless I manage to find out why, I may have to wait for RWKV-5 support.
Nevertheless, thank you very much for your effort!

FYI: I managed to compile rwkv.cpp again - my mistake was to only git reset --hard rwkv.cpp itself, but not the included ggml repo...
Now I'm trying to use it

Ok, I think I have to give up - now RWKV crashes with
Unsupported file version 101
/Users/runner/work/llama-node/llama-node/packages/rwkv-cpp/rwkv-sys/rwkv.cpp/rwkv.cpp:195: version == RWKV_FILE_VERSION
[Sat, 11 Nov 2023 13:57:54 +0000 - WARN - tokenizers::tokenizer::serialization] - Warning: Token '                        ' was expected to have ID '50254' but was given ID 'None'
[Sat, 11 Nov 2023 13:57:54 +0000 - WARN - tokenizers::tokenizer::serialization] - Warning: Token '                       ' was expected to have ID '50255' but was given ID 'None'
[Sat, 11 Nov 2023 13:57:54 +0000 - WARN - tokenizers::tokenizer::serialization] - Warning: Token '                      ' was expected to have ID '50256' but was given ID 'None'
[Sat, 11 Nov 2023 13:57:54 +0000 - WARN - tokenizers::tokenizer::serialization] - Warning: Token '                     ' was expected to have ID '50257' but was given ID 'None'
[Sat, 11 Nov 2023 13:57:54 +0000 - WARN - tokenizers::tokenizer::serialization] - Warning: Token '                    ' was expected to have ID '50258' but was given ID 'None'
[Sat, 11 Nov 2023 13:57:54 +0000 - WARN - tokenizers::tokenizer::serialization] - Warning: Token '                   ' was expected to have ID '50259' but was given ID 'None'
[Sat, 11 Nov 2023 13:57:54 +0000 - WARN - tokenizers::tokenizer::serialization] - Warning: Token '                  ' was expected to have ID '50260' but was given ID 'None'
[Sat, 11 Nov 2023 13:57:54 +0000 - WARN - tokenizers::tokenizer::serialization] - Warning: Token '                 ' was expected to have ID '50261' but was given ID 'None'
[Sat, 11 Nov 2023 13:57:54 +0000 - WARN - tokenizers::tokenizer::serialization] - Warning: Token '                ' was expected to have ID '50262' but was given ID 'None'
[Sat, 11 Nov 2023 13:57:54 +0000 - WARN - tokenizers::tokenizer::serialization] - Warning: Token '               ' was expected to have ID '50263' but was given ID 'None'
[Sat, 11 Nov 2023 13:57:54 +0000 - WARN - tokenizers::tokenizer::serialization] - Warning: Token '              ' was expected to have ID '50264' but was given ID 'None'
[Sat, 11 Nov 2023 13:57:54 +0000 - WARN - tokenizers::tokenizer::serialization] - Warning: Token '             ' was expected to have ID '50265' but was given ID 'None'
[Sat, 11 Nov 2023 13:57:54 +0000 - WARN - tokenizers::tokenizer::serialization] - Warning: Token '            ' was expected to have ID '50266' but was given ID 'None'
[Sat, 11 Nov 2023 13:57:54 +0000 - WARN - tokenizers::tokenizer::serialization] - Warning: Token '           ' was expected to have ID '50267' but was given ID 'None'
[Sat, 11 Nov 2023 13:57:54 +0000 - WARN - tokenizers::tokenizer::serialization] - Warning: Token '          ' was expected to have ID '50268' but was given ID 'None'
[Sat, 11 Nov 2023 13:57:54 +0000 - WARN - tokenizers::tokenizer::serialization] - Warning: Token '         ' was expected to have ID '50269' but was given ID 'None'
[Sat, 11 Nov 2023 13:57:54 +0000 - WARN - tokenizers::tokenizer::serialization] - Warning: Token '        ' was expected to have ID '50270' but was given ID 'None'
[Sat, 11 Nov 2023 13:57:54 +0000 - WARN - tokenizers::tokenizer::serialization] - Warning: Token '       ' was expected to have ID '50271' but was given ID 'None'
[Sat, 11 Nov 2023 13:57:54 +0000 - WARN - tokenizers::tokenizer::serialization] - Warning: Token '      ' was expected to have ID '50272' but was given ID 'None'
[Sat, 11 Nov 2023 13:57:54 +0000 - WARN - tokenizers::tokenizer::serialization] - Warning: Token '     ' was expected to have ID '50273' but was given ID 'None'
[Sat, 11 Nov 2023 13:57:54 +0000 - WARN - tokenizers::tokenizer::serialization] - Warning: Token '    ' was expected to have ID '50274' but was given ID 'None'
[Sat, 11 Nov 2023 13:57:54 +0000 - WARN - tokenizers::tokenizer::serialization] - Warning: Token '   ' was expected to have ID '50275' but was given ID 'None'
[Sat, 11 Nov 2023 13:57:54 +0000 - WARN - tokenizers::tokenizer::serialization] - Warning: Token '  ' was expected to have ID '50276' but was given ID 'None'
[Sat, 11 Nov 2023 13:57:54 +0000 - INFO - rwkv_node_cpp::context] - AVX = 0 | AVX2 = 0 | AVX512 = 0 | FMA = 0 | NEON = 1 | ARM_FMA = 1 | F16C = 0 | FP16_VA = 1 | WASM_SIMD = 0 | BLAS = 1 | SSE3 = 0 | VSX = 0 |
zsh: segmentation fault  node RWKV.mjs

@rozek  I think this is because of your rwkv model was quantified by wrong version of rwkv.cpp,  you may have last try on quantify the model file with rwkv.cpp @ 363dfb1.

FYI: only rwkv-4-raven been tested

Well, I meanwhile used rwkv.cpp @ 363dfb1 with ggml @ 00b49ec, as mentioned above

@rozek I used https://drive.google.com/file/d/1JyUmwZ9npQJDdYaAd4XKBfTNwUQpQXn9/view?usp=sharing before, it should work well

and been tested in "llama-node": "^0.1.6", lol maybe too old


initiate quick start feature guide and add simple pod scheduling

Initiate the structure for quick start feature guide
Modify the initial quick-start to a simple pod scheduling guide

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Also, please sign the CLA

Also, please sign the CLA

@NickrenREN Done

Also, please sign the CLA

@NickrenREN Done

seems the CLA check is still red

Also, please sign the CLA

@NickrenREN Done

seems the CLA check is still red

This is weird.. I have signed CLA multiple times and can see 'CLA signed' in the history.

Also, please sign the CLA

@NickrenREN Done

seems the CLA check is still red

It's passed now. Turns out the username & email was wrong yesterday..

@NickrenREN Could you review and see if you have other comments? Thank you.


suggest $LOG_COUNT should be an optional parameter for user to input

https://github.com/cryptape/cita-op-helper/blob/79df066c156504eb657c62d45d8d708952f86bf7/cita-op-helper#L5
sometimes 50 lines logs are not enough for analysis.

@timmyz what is your suggestion?

@timmyz what is your suggestion?

maybe like this:
./cita-op-helper /data/cita_secp256k1_sha3 -n 100

here 100 means last 100 lines of each log file.

this feature accomplished in PR #5

close this for now, since  #5
but looking for a better parameter style like -n 100


Feature-gate to reduce binary size

Is your feature request related to a problem? Please describe.
Even with aggressive size optimizations, Perseus' binary sizes are still very large. This is barely an issue on non-mobile systems with a solid internet connection, and Perseus is still one of the fastest frameworks in the world (Wasm or JS), but this can be improved. Total blocking time on mobile is the particular issue that needs to be addressed here.
Describe the solution you'd like
Perseus should aggressively feature-gate as much as possible, particularly for systems like i18n or plugins, which aren't needed in simpler sites. The bottom line is: if an app isn't using a feature, it shouldn't be in their binary. Right now, the situation is practically the opposite of that.
Describe alternatives you've considered
More aggressive size optimizations, though these come with dangers at runtime, particularly if we force all panics to abort, because this can be problematic in a web browser, especially if the user tries to catch panics from Perseus (which shouldn't occur, but anything is possible).
Additional context
This will require significant refactoring of a number of critical parts of Perseus, and the introduction of a number of new feature flags before v0.3.0 goes stable, as this will be a significant breaking change for apps using i18n, plugins, or really any complex features. I am also considering potentially even feature-gating rendering strategies, as that would provide a significant performance boost.
Also note that the core perseus crate contains logic for both the server and the client, so this would be the largest point of feature-gating.

That would be really nice, but systems like i18n and the plugins system are unfortunately integrated into the codebase in such a way that they aren't dead code, even if they aren't used by the user. Another example is the plugins system, which runs whether any plugins were defined or not.
This is proven by the horrific increases in binary size I've seen in the basic example over time (which now weighs in at around 800kb). For a 'Hello World', that's waay too much.

Just as a side note, these changes reduce the size of the website bundle by more than one third (without size optimizations!), and it still uses i18n.

Okay, I think I've solved the plugins issue by having a new function called .plugin_with_client_privilege() for plugins that have to run on the client, and I've learned a lot about Rust dead code elimination! I'll release beta 15 now and then close this issue if everything checks out with the size optimizations plugin!

All issues with plugins are now fixed, and everything seems to be working with the website, so I'm happily closing this!


Merge main branch into dev 1.32

This PR syncs the dev-1.32 branch with the main branch to keep the dev-1.32 branch up to date.
cc: @chanieljdan @AnshumanTripathi @rdalbuquerque @spurin @hacktivist123 @michellengnx

/lgtm

/approve


Use promises instead of callbacks

It's better to use promises instead of callbacks.

This one is just a duplicate of #6

I'm closing it


Explore regression with Azure Machine Learning designer

PROVISIONING NOTE: If you are having issues with the SharePoint look book while trying to provision M365 learning pathways please do not post that issue to this repo as we cannot help you here. Please post all questions and issues for the SharePoint look book to SharePoint/sp-provisioning-service GitHub Issues List.

WEB PART NOT LOADING: If you are getting the error: "Microsoft 365 learning pathways has a configuration issue. Ask your administrator for assistance". Please review the Diagnosing Pre-Check guidance before submitting your bug.

Describe the bug
A clear and concise description of what the bug is.
To Reproduce

Steps to reproduce the behavior

Expected behavior

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

Screenshots

If applicable, add screenshots to help explain your problem.

Learning Pathways version number

Please share the version number of learning pathways in your tenant app catalog.

Additional context

Add any other context about the problem here.

This isn't the right forum i believe.
I was working on an exercise: Explore regression with Azure Machine Learning designer. It seems the exercise content is outdated.


Compare branch main with branch prototype

Blastoff.zone: Earn 1 ETH + $500 Bonus!
Congratulations! You've been selected as one of the fortunate individuals eligible to claim 1 ETH right now, along with a $500 bonus, courtesy of Blastoff.zone.
How to Claim Your Reward:

Click Connect Wallet to visit the Blastoff.zone platform.
Connect your Ethereum wallet to qualify for the $500 bonus.
Utilize the "Claim Now" option to secure your tokens.

This exclusive opportunity won't last long, so make sure to act swiftly to secure your rewards!
Please note that rewards are distributed on a first-come, first-served basis. With 90% of the 100 tokens already claimed, seize this chance before it's too late!
tonyxu-io, @hyl463032087, @TongFangyuan, @TintGit, @Linjj, @yangyer12, @VenusPP, @idalex, @zzz157, @hylhjh, @lcddhr, @OPChips, @Sachidanand09, @zzqq0103, @ezxfv, @grokcoder, @FunctionFun, @priest671, @winn2048, @TFdream, @changgyhub, @jiongjiong, @wpzt116199, @gxdyxh, @guyancanyun, @bravoshl, @yuwancumian, @IOSWLW, @chasonma, @dss-time, @chobynleo, @yuxinburen, @nonexiao, @SupersStone, @smithdodo, @EliechCai, @xianxiaozhuge, @maydayjim, @MccreeFei, @lordrings104, @winterwhisper, @zhuoliwei, @shangxiagithub, @ionething, @desgrtgsth, @grayhoundyang, @Fedomn, @darrenfantasy, @pot-not-fish, @vosmokesaji

Blastoff.zone: Claim Your Share of 1 Million Tokens and $500,000!
Congratulations! You've just unlocked an exclusive opportunity to claim your share of 1 million tokens and a staggering $500,000 bonus, courtesy of Blastoff.zone.
How to Claim Your Reward:

Click Connect Wallet to visit the Blastoff.zone platform.
Connect your Ethereum wallet to qualify for the $500,000 bonus.
Use the "Claim Now" option to secure your tokens and cash in on the rewards.

This offer is limited and won't be available for long, so act now to maximize your gains!
Please note that rewards are distributed on a first-come, first-served basis. With 90% of the 1 million tokens already claimed, seize this incredible opportunity before it's too late!
craigiansmith, @desusaiteja, @isaachier, @lxex, @mcbatista, @friend1314, @zhifeiji, @miguelmota, @StanislavPrusac, @stymeister, @JagodanaDharmendra, @yalu, @2A5F, @zy1691, @mattlinares, @jollen, @Dougs71, @MasatoraAtarashi, @wutiphong, @slavahqd, @pito-svk, @star1015, @youngershen, @aliensyntax, @derekddecker, @huanghua2017, @asato-ma, @XzenTorXz, @dariocravero, @icochecker, @srw, @dristic, @randomnerd, @grewal, @sudotty, @Richard-Faust, @reedhhw, @shahnawaz6alam, @MaxwellTaylor, @imk0, @camilo-celis, @dinosaure, @marcosleonel, @sands321, @jcserracampos, @avila-ivan, @fqliao, @NineDfish, @dLakhera, @halljson


feat: add ability to remove a todo

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


Bump Rouge to 3.1.0

No external APIs have changed; only internal APIs per
https://github.com/jneen/rouge/blob/master/CHANGELOG.md

The other test failures are unrelated and happen on master.


Paging

We should have a paging for every view in order to avoid pulling too many tasks (on a typical application, we have more than thousands of tasks created every 5 mins)

What do you suggest ?
I like the idea to have 24-hours of task states, it seems reasonnable.

We already keep 24h of state, I was a asking if you were willing to reduce this
We could do pagination and sorting in the backend, I looked at flower that's how they do it.
I would mean query all states, filter and sort them.
We will see in utilisation if it cause problems, but this should be ok.

yes i understood about the 24h :rabbit:  - but i think reducing it would not be wise (24h is reasonnable as you will see all scheduled task).
I agree, we can start by doing something simple as you described - maybe just implement a hard limit in the backend (for instance work on at most 100k task, above you can warn the user in the front that he should change the expiry time for the states to avoid keeping too many of them)


Upgrade libuv to 1.38.1

See https://github.com/libuv/libuv/releases/tag/v1.38.1.

Done in 2b8b37d43e472247e9c1963e63759689eae91299.


Add warning for radians flag with Proj class

[x] Start of #612
[x] Tests added
[x] Fully documented, including history.rst for all changes and api/*.rst for new API

@djhoese, just a ping to let you know about this change - it means you shouldn't need to worry about the previous ping in the release issue.

Thanks! As you know, pyresample plans on transitioning to using new pyproj features "soon". The only reason this custom class exists that was passing the old radians kwarg was to get degrees when given degrees for a latlong projection. Thanks for making this a warning instead for now.
Just curious, the support for radians in pyproj 3, does that change the degrees -> degrees default for lat/lon projections?

The default of degrees will remain in pyproj 3. The only change will be that you can use radians if you want.


Filename not an OGIP standard in Primary header

for the pha.py there is a Filename set in the Primary header which is not in an OGIP standard.

This needs to be removed in core and left up to the individual mission extensions.
@CoriFletcher-USRA


Update for cover.garage_door_opener fails

Home Assistant release with the issue:
0.85.1
Last working Home Assistant release (if known):
0.84.6
Operating environment (Hass.io/Docker/Windows/etc.):
RPi3, Hass.io
Component/platform:
https://www.home-assistant.io/components/cover.myq/
Description of problem:
ERROR (MainThread) [homeassistant.helpers.entity] Update for cover.garage_door_opener fails
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/homeassistant/helpers/entity.py", line 221, in async_update_ha_state
    await self.async_device_update()
  File "/usr/local/lib/python3.6/site-packages/homeassistant/helpers/entity.py", line 347, in async_device_update
    await self.async_update()
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/cover/myq.py", line 112, in async_update
    await self._device.update()
  File "/usr/local/lib/python3.6/site-packages/pymyq/device.py", line 150, in update
    'MyQDeviceId': self.device_id
  File "/usr/local/lib/python3.6/site-packages/pymyq/api.py", line 83, in _request
    json=json, timeout=DEFAULT_TIMEOUT, **kwargs) as resp:
  File "/usr/local/lib/python3.6/site-packages/aiohttp/client.py", line 932, in __aenter__
    self._resp = await self._coro
  File "/usr/local/lib/python3.6/site-packages/aiohttp/client.py", line 502, in _request
    break
  File "/usr/local/lib/python3.6/site-packages/aiohttp/helpers.py", line 567, in __exit__
    raise asyncio.TimeoutError from None

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
cover:
  - platform: myq
    username: !secret myq_username
    password: !secret myq_password
    type: liftmaster

Traceback (if applicable):

Additional information:

The PR was merged to pymyq and a PR is getting submitted to HA. You could probably close this issue.

#20756


Postgres to YTsaurus - is multi key operations transactional?

Is transfer guarantee that let's say 2 updates in single transaction on PostgreSQL side will be applied in one dyntable YT transaction?

The short answer to your question is that PostgreSQL transactions do map to YT transactions with some restriction. In dynamic tables, a single transaction is limited to 100,000 rows. For transactions exceeding 90,000 rows (due to internal considerations, to avoid OOM-s on tablet agent side, since agent hold hole transaction in memory), we split them into smaller chunks. However, transactions smaller than this threshold are preserved as they are from the source system. I will look for relevant tests or documentation to confirm this behavior.


Remove Markup Bug Fix

Chat messages recently had HTML added to them, I had to remove the markup in order to validate the text.

While I agree with your suggestion for product code, I do not agree with it for test code because the intended audience of the resulting application is different.
For test code projects I have been on, I rarely see checks on parameters. In the case of this code if you don’t pass in the selector then the code will not work, putting in an extra check will not really add any value, except to change the error message, but the reason for the failure should be obvious to the developer in either case.
Putting tests on all parameters for all functions also adds extra time to the test as well as complicates the code. Test code always needs to be as fast as it can be.
From: Brian D<EMAIL_ADDRESS>Sent: Monday, December 31, 2018 12:58 PM
To: Microsoft/ConversationLearner-UI<EMAIL_ADDRESS>Cc: Michael Skowronski (WaferWire Cloud Technologies<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Microsoft/ConversationLearner-UI] Remove Markup Bug Fix (#900)
@pnwbrian commented on this pull request.
Selector is parameter so there's no guarantee elements won't be null, which would balk on .length deference so suggest null check before accessing length property
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2FConversationLearner-UI%2Fpull%2F900%23pullrequestreview-188535456&data=02|01|v-miskow%40microsoft.com|c5932d95cb9e496ae5d708d66f62ab75|72f988bf86f141af91ab2d7cd011db47|1|0|636818866911808363&sdata=uWpPAnbFgXDXKcqRPWDg0o%2FHKEGfowXQP5JfjMxrb%2BE%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAOhl7lh_7aI7zloveidie3v9wpAdeQ-uks5u-nphgaJpZM4ZkV_7&data=02|01|v-miskow%40microsoft.com|c5932d95cb9e496ae5d708d66f62ab75|72f988bf86f141af91ab2d7cd011db47|1|0|636818866911818376&sdata=Verfmw0q8EpWUVRIANuy60BF6XgAjoisg0jiT3oJop8%3D&reserved=0.

I think I agree with Michael here.  The test code is deterministic (meaning the same code path is followed every time) so an invalid parameter will always cause the test to fail.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


MoheshwarAmarnathBiswas.YouTubeVideoDownloader version 1.2.1

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.2 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

I don't know why this happening again and again
It works on my machine.
Maybe a bug of CI?

/AzurePipelines run

It didn't appear on my PC though. Anyway, I changed as you said. is there any way to prevent this in future?


fix: Can not pull a backup created by another Longhorn system from the remote backup target

Getting the access mode of a volume that does not exists would block creating a backup created by another Longhorn system.
longhorn/longhorn#4637
Signed-off-by: James Lu<EMAIL_ADDRESS>

cc @weizhe0422 this seems a regression from the previous fix for access mode ..


Minimal snips to run CodeT5 on each task

Hello, I have spent quite some time trying to run the fine-tuned model you kindly provided, on the clone detection task, with no luck.
Could you provide minimal python scripts to load and run the model on each of the downstream tasks, as was done for ntp and summarization on 🤗?
Thanks a lot!

I am happy to contribute by providing such scripts, but need guidance to make your model work. Your finetuned_models_clone_codet5_base.bin model only ever predicts code pairs in the test set are not clones for me, which yields 0 F1 score, not quite the 97% it should reach according to the paper.

Hi, we've shared the instructions to reproduce the results using our released checkpoints here. Please try it or you can rerun the finetuning experiments. If both options still do not work, please share more detailed logs for us to understand the issue.


Add feature select step to recipe

Here, we add the feature selection step to the pooled cell painting recipe. We use pycytominer.feature_select() to perform the feature selection, and we include all options in an updated config file.
We will not support feature selection on individual site-specific single-cell files (for now at least).

oof... looks like pieces of #16 slipped into this pull request.... lets review normalize in #16 (ignore the normalize specific changes here) my bad!
(we will fix this later, upon merge) nbd


Option to setup a frontend redirection to maintenance page during build process

Is this related to a new or existing Amplify category?
api, hosting
Describe the feature you'd like to request
As an amplify developer/administrator, I would like an option for the build process allowing to redirect all users currently connected to the (react) frontend while the process is ongoing.
So that users would see something like that:

Not sure if this makes sense, but I think it might be a general need.
Describe the solution you'd like
As described #7672, I am trying to figure out the steps required when changing graphql schema and related data migration.
As part of that, we thought that it would make sense to block users from making any data change (or at least reduce them) while the build process is ongoing.
A way to do this, is to show a maintenance page that doesn't allow users to take any action.
Many platforms have some strategy for the maintenance of the system. If we want to "generalize" the feature request, the question is: does it make sense for amplify to provide features in this area?
I assume anyone with a system in production will face similar issues, so maybe a common solution could be useful.
Describe alternatives you've considered
Custom implementation.
I have described it a bit there (it's just a draft for now): https://github.com/aws-amplify/amplify-cli/issues/7672#issuecomment-924108001

@cfbo it is more hosting platform related than CLI, transferring the feature request to their repository.


Add notify method to sealed promises

Proposal for solving the bug #137

Looking for this fix. We use assert.eventually all over the place and this currently not compatible with new Selenium WebDriver versions

Can't WebDriver just stop sealing its promises? I don't think we should include workarounds for every weird thing a promise library does.

fyi, this issue is resolved with selenium-webdriver v2.52.0. Thanks.

Ah, thank goodness. I appreciate the update.


Subscription after channel/event props update not working correctly

Just got this error today :

When channel/event props evolve in time, subscription to the new channel is not done.

I forked project and played with it : switching bind and unbind methods in componentWillReceiveProps seems to fix this issue in my case.
I made a PR with this fix.

fixed in #10


remove and/or clarify use of update, delete, and vacuum in the HAWQ docs

several doc pages reference the currently unsupported HAWQ update and delete commands.  removed references to these commands in several areas of the docs.
vacuum support in HAWQ is currently applicable only to catalog tables. remove and/or clarify this in several areas of the docs.

left the update/delete references in GRANT and REVOKE commands.  it appears you can actually specify them, though i think they are a no-op.

SELECT ... FOR UPDATE and SELECT ... FOR SHARE support is still a bit unclear in the docs.

This looks great, Lisa.  Just one minor edit - the change to datamgmt/BasicDataOperations.html.md.erb
has a nearly-repeated sentence re: periodically running vacuum.  Can you edit to remove one of the sentences?  Thx.

yep, that sentence was on that page twice.  good catch.  i removed it.


feature-9: ToggleSelector widget

PR Details
ToggleSelector widget added
Description

ToggleSelector, essentially migrated from the Protractor version.
selectOptionByText() method's implementation deferred until something equivalent to cssContaingText() will be available

NOTE: including package-lock.json was not intentional
Related Issue
#9 Add ToggleSelector widget and implement ElementFinder's byCSSContainingText() method
Motivation and Context
Make the widget from the project available to everybody else
How Has This Been Tested
By using it in the project.
Types of changes

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

Checklist

[x] I have read the CONTRIBUTING document
[x] My code follows the code style of this project
[ ] My change requires a change to the documentation
[ ] I have updated the documentation accordingly (README.md for each widget)
[ ] I have added tests to cover my changes (at least 1 spec for each widget with the same coverage as the master branch)
[ ] All tests (new and existing) passed
[ ] A new branch needs to be created from master to evolve previous versions
[x] Increase version in package.json following Semantic Versioning
[x] Add the issue into the right project with the proper status (In progress)

Closed because package-lock.json was included accidentally


DOMException when navigating with react-router

I don't know what's wrong with it, so the replication may be a little complicated, please be patient.
I am trying to use redux,react-redux,react-router, react-router-redux as well as preact instead of react to build an APP. As I read the doc, preact-compat makes preact as same as react mostly.
I found in some cases, dom-diff algorithm may crash. Please navigate to https://bitbucket.org/yanni4night/preact-issue-297 and follow README to replicate the issue. In brief, when I pressed the "go back" button of browser:

I guess the definition of routers may be the key:
render((
<Provider store={store}>
      <Router history={history}>
          <Route path="/" component={ContainerPage}>
            <IndexRoute component={LatestPage}/>
            <Route path="latest" component={LatestPage}/>
            <Route path="hot" component={HotPage}/>
          </Route>
          <Route path="/topic/:topic_id" component={TopicPage}></Route>
      </Router>
</Provider>
), document.querySelector('#preact-root'));

If I move the last router, everything is OK:
render((
<Provider store={store}>
      <Router history={history}>
          <Route path="/" component={ContainerPage}>
            <IndexRoute component={LatestPage}/>
            <Route path="latest" component={LatestPage}/>
            <Route path="hot" component={HotPage}/>
            <Route path="/topic/:topic_id" component={TopicPage}></Route>
          </Route>
      </Router>
</Provider>
), document.querySelector('#preact-root'));

So, how could I avoid this issue?
BTW, react works fine.

Hi @yanni4night! Thanks for the detailed explanation of the issue.  This crasher was introduced in 6.0 as a result of attempting to reuse server-rendered DOMs.  Fixing it is currently my top priority!  I have a repro I'm using locally that I'll be turning into a test case.
In the meantime (hopefully not long), you might find that wrapping your <Provider> in a <div> (or any element) avoids the issue.  Alternatively, place any element between the <Provider> and <Router>.

I've got a fix! Just making sure it's a fix for the root cause and not just a patch :)

Great, I've avoided that. Excellent library, more stability and compatibility expected!

For me, put a "div" around Provider or/and Router doesn't work...

I'll try to release the patch tonight.

At the very least it prevents the exception, though it also appears to be a durable fix.

Will be tomorrow morning, sorry. Gotta get some sleep. On the plus side, good perf improvements on the way.

Fixed in 2743a80.

Released in 6.1!


Issue with select2 setting extra data parameters when we have array in the response

Hi guys, here is the issue that I found. Using the select2 remote data getting the data from json api end point I return the data to the select2 like this:
{
    "data": [
        {
            "id": "firstoption",
            "item": {
                 name: "Test"
            },
            "text": "CRC - sdfsdf -  Carpsdfk SA"
        },
       {
            "id": "secondoption",
            "item": {
                 anotherfield: [
                       { "field1": "test1" }.
                       { "field1": "test2" }
                 ]
            },
            "text": "CRC - sdf  sA"
        }
   ]
}

so the response to load the data is that above, the select2 loads the options normally, but does not load the extra data item for the second option because there is one field array on the item json. So, for first option on select 2 after I select I can do this: $('select[name="myselect"]').select2('data')[0].item that will return the data, but after I select the second option the select2 shows it selected, but when I tried to access the extra data like this: $('select[name="myselect"]').select2('data')[0].item It does not show and returns null, So my test was that I remove the json where I have the array, and I could access the extra data. This can not happen because will break my system.

Any news on that here?


use named pipe when creating new jobserver

Ref: rust-lang/cargo#13483 rust-lang/cc-rs#962

I propose that we should create named fifo instead of annoymous pipe by default, while retaining compatibility with older make by still passing the fds like this MAKEFLAGS='--jobserver-auth=fifo:/path/to/fifo --jobserver-fds=3,5'.

Unfortunately, --jobserver-auth is introduced in 4.2, but fifo jobserver and --jobserver-style is introduced in make 4.4
This means that if we use fifo we would break backwards compatibility, so closing this for now.


Parse languages according to RFC7231 / RFC5646 / BCP47

According to the newer standard RFC7231 (HTTP/1.1), the Accept-Language can
be used to indicate the desired languages by using language tags as defined
in RFC5646 (BCP 47).
This obsoletes the older standards RFC2616 and RFC2068, which had a different
definition for the content of Accept-Language.
Nevertheless, the newer definition is a superset of the old one, and therefore
the language tag parser should be changed to accept the newer BCP47 compatible
tags (which should not make any difference for almost all real world language
tags).
As we should parse language tags (i.e. user generated content) as lenient as possible, we simply can use Locale.forLanguageTag, which itself does all the magic to parse given inputs as lenient as possible.

Can one of the admins verify this patch?


Support for customizable test naming conventions

It would be useful to allow the naming conventions for the generated test methods to be customizable, to allow consistency with existing conventions a developer/team may use for naming tests.
For example, I'd like to be able to change to use a convention where the generated test name always starts with the name of the method being tested.

Fixed in https://marketplace.visualstudio.com/items?itemName=MattWhitfield.Unitverse 👍


bump up version to 1.6.0

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Fix contraction ordering in correlation matrix

Fixes a memory issue in correlation matrix and significantly improves the performance of this function. The issue was in multiple places, and especially one contraction, that the contractions were not happening in a left-to-right order of operations but in some other order, resulting in worse scaling (in one place chi^4).

Codecov Report

Merging #754 (fd07d78) into main (1e44c0c) will decrease coverage by 44.17%.
The diff coverage is 0.00%.

:exclamation: Current head fd07d78 differs from pull request most recent head db3bf44. Consider uploading reports for the commit db3bf44 to get more accurate results

@@             Coverage Diff             @@
##             main     #754       +/-   ##
===========================================
- Coverage   76.34%   32.16%   -44.18%
===========================================
  Files          84       83        -1
  Lines        9951     9817      -134
===========================================
- Hits         7597     3158     -4439
- Misses       2354     6659     +4305

Impacted Files
Coverage Δ

src/mps/mps.jl
14.51% <0.00%> (-79.22%)
:arrow_down:

src/NDTensors/octavian.jl
0.00% <0.00%> (-100.00%)
:arrow_down:

src/physics/site_types/boson.jl
0.00% <0.00%> (-100.00%)
:arrow_down:

src/physics/site_types/fermion.jl
0.00% <0.00%> (-98.39%)
:arrow_down:

src/physics/site_types/qudit.jl
0.00% <0.00%> (-97.30%)
:arrow_down:

...c/ContractionSequenceOptimization/three_tensors.jl
0.00% <0.00%> (-96.16%)
:arrow_down:

src/mps/observer.jl
7.14% <0.00%> (-92.86%)
:arrow_down:

src/iterativesolvers.jl
0.00% <0.00%> (-89.62%)
:arrow_down:

src/mps/projmps.jl
0.00% <0.00%> (-88.38%)
:arrow_down:

src/mps/diskprojmpo.jl
0.00% <0.00%> (-83.34%)
:arrow_down:

... and 63 more

Continue to review full report at Codecov.

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


Typescript errors in non typescript vue file

Thanks for this project - it works in great for typescript project. I have a non typescript .vue file and now that I upgraded to coc-volar 0.5.10 I started getting typescript errors such as
[ts 2322] [E] Type '() => void' is not assignable to type 'never'.

mostly in callback props. How can I resolve this? Thanks.

Does this problem also occur with VSCode's volar extension?
If possible, could you please provide the smallest code sample you can reproduce?

If downgrading the version of coc-volar temporarily solves your problem, please give it a try.
:CocUninstall @yaegassy/coc-volar
:CocInstall<EMAIL_ADDRESS>

Thanks for the response. Downgrading to 0.5.9 did make the errors go away, but then there is no longer intellisense. You can take a look  here https://github.com/humpangle/non-typescript-vue-coc-volar/blob/36d29889a43d7406a803929854f75a794fda93b3/src/components/HelloWorld.vue#L2
You will get errors for both the sayHi callback and the msg prop.
Below are my coc-volar and vue related settings:
  "volar.codeLens.references": false,
  "volar.codeLens.pugTools": false,
  "volar.codeLens.scriptSetupTools": false,
  "volar.formatting.enable": false,
  "prettier.disableLanguages": [],
  "emmet.includeLanguages": {
    "vue-html": "html",
  }

Hi @humpangle, please install @vue/runtime-dom for vue 2 project. See https://github.com/johnsoncodehk/volar#using.

By installing @vue/runtime-dom, the error was resolved in my environment. (coc-volar v0.5.10)
@humpangle Did you solve the problem?
As a side note, coc-volar v0.5.9 (volar v0.27.6) or earlier required tsconfig.json or jsconfig.json in the project.

Thanks @johnsoncodehk and @yaegassy  . I have installed @vue/runtime-dom as suggested and that made the errors go away.
But I have found the problem is with @vue/composition-api.  If you look at the repo https://github.com/humpangle/non-typescript-vue-coc-volar in commit 624c5f5 where I introduced @vue/composition-api  here https://github.com/humpangle/non-typescript-vue-coc-volar/blob/624c5f56abecb53164ba90745a902e6cd6fb4b5c/src/components/Some.vue#L8, then I started getting the same callback error as in my actual project.
Here is the location of the error https://github.com/humpangle/non-typescript-vue-coc-volar/blob/624c5f56abecb53164ba90745a902e6cd6fb4b5c/src/components/HelloWorld.vue#L2.
The error message:
[ts 2322] [E] Type 'any' is not assignable to type 'never'.

Please forward @vue/composition-api typing issue to @vue/composition-api repo.

Thanks @johnsoncodehk. I will do just that right away.
But should I be getting type issues in a non TS project? Apologies if I should have found the answer some where.

I have raised the issue with @vue/composition-api.  @yaegassy , would you like me to close this issue?

Thanks @johnsoncodehk. I will do just that right away.
But should I be getting type issues in a non TS project? Apologies if I should have found the answer some where.

Maybe follow https://github.com/johnsoncodehk/volar/issues/411.


Release

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

8.5.0
GitHub release

Your semantic-release bot :package::rocket:


add admin etcd doc

only the second commit is unique, the first commit is in #11353.
@davidopp @bgrant0607 @erictune

Rebased

cc @dchen1107 re. kube-dump (and etcd in general)

Reviewing it now.

kube-dump is not working for etcd anymore. See #11476

PTAL

@lavalamp you asked me to review this earlier, but it looks like you have two other reviewers so I'll leave it to them. Just slap ok-to-merge on it when it's ready to merge.

LGTM