semantically incorrect/incomplete documentation code

Missing closing div on http://ionicframework.com/docs/components/#striped-style-tabs
Should I submit a PR for that?

Greetings @EddyF!
We are now requiring all issues to be submitted through our custom issue form so that we have all of the information necessary to fix them as quickly as possible.
Click Here To Update Your Issue
This issue will be closed if not resubmitted through the form. Please fill out the rest of the form so that we may assist you.
Thank you for allowing me to assist you.

Looks good to me

        Test

        Favorites

        Settings

        Test

        Favorites

        Settings

Mmm strange, looks fine now!
perhaps I overlooked (even tho I checked 100times before posting)
whichever case I'm closing this, cheers.


describe doing value table wrong?

Doesn't this report from pygrambank describe look wrong for number of values in ELDP-glottobank/grambank/original_sheets/FCE_apal1257.tsv
Values:
0	121
1	 67
?	  1
	189

For comparison, here's what I get in R
> library(tidyverse)
>
> SHEET <- read_tsv("../../../glottobank/ELDP-glottobank/grambank/original_sheets/FCE_apal1257.tsv")
>
> SHEET$Value %>% table()
.
  ?   0   1
  1 126  74

I take it it has to do with the binarised features somehow?

First of all: that table only shows the number valid datapoints.  If a data point has an error in it or describes an unknown feature it won't show up in the table.  That's where the discrepancy comes from.
Second:  Whether or not a feature is ‘known‘ seems to depend on gb20.txt.  The binarised features aren't in there, yet.  Should be fixable by copying the gb20.txt from the regular repo over to the ELDP one.
Also, I wanted to check a sheet in regular grambank and picked HC_swed1254 at random.  It said the following features are not valid:
GB029   GB063   GB101   GB154   GB181   GB208   GB220   GB232   GB245   GB269   GB287
GB032   GB064   GB102   GB157   GB182   GB209   GB221   GB234   GB246   GB271   GB288
GB033   GB066   GB106   GB162   GB183   GB210   GB222   GB235   GB247   GB272   GB289
GB034   GB067   GB112   GB163   GB191   GB211   GB223   GB236   GB248   GB274   GB290
GB040   GB076   GB125   GB168   GB194   GB212   GB224   GB237   GB249   GB277   GB292
GB045   GB077   GB128   GB169   GB195   GB213   GB225   GB238   GB251   GB278   GB293
GB050   GB078   GB141   GB173   GB199   GB214   GB226   GB239   GB255   GB279   GB294
GB055   GB085   GB142   GB174   GB200   GB215   GB227   GB240   GB258   GB280   GB295
GB056   GB087   GB143   GB175   GB202   GB216   GB228   GB241   GB259   GB281
GB060   GB088   GB144   GB176   GB205   GB217   GB229   GB242   GB261   GB282
GB061   GB097   GB145   GB178   GB206   GB218   GB230   GB243   GB267   GB283
GB062   GB100   GB153   GB179   GB207   GB219   GB231   GB244   GB268   GB284

Just to double-check:  Anything surprising in this list?

First of all: that table only shows the number valid datapoints. If a data point has an error in it or describes an unknown feature it won't show up in the table. That's where the discrepancy comes from.

Thanks!

Second: Whether or not a feature is ‘known‘ seems to depend on gb20.txt. The binarised features aren't in there, yet. Should be fixable by copying the gb20.txt from the regular repo over to the ELDP one.

the binarised features gb20.txt though.. https://github.com/glottobank/Grambank/blob/4c280aec01e30fa8bf53ad622b3b8e51699b1649/gb20.txt#L4620

Also, I wanted to check a sheet in regular grambank and picked HC_swed1254 at random. It said the following features are not valid:
GB029   GB063   GB101   GB154   GB181   GB208   GB220   GB232   GB245   GB269   GB287
GB032   GB064   GB102   GB157   GB182   GB209   GB221   GB234   GB246   GB271   GB288
GB033   GB066   GB106   GB162   GB183   GB210   GB222   GB235   GB247   GB272   GB289
GB034   GB067   GB112   GB163   GB191   GB211   GB223   GB236   GB248   GB274   GB290
GB040   GB076   GB125   GB168   GB194   GB212   GB224   GB237   GB249   GB277   GB292
GB045   GB077   GB128   GB169   GB195   GB213   GB225   GB238   GB251   GB278   GB293
GB050   GB078   GB141   GB173   GB199   GB214   GB226   GB239   GB255   GB279   GB294
GB055   GB085   GB142   GB174   GB200   GB215   GB227   GB240   GB258   GB280   GB295
GB056   GB087   GB143   GB175   GB202   GB216   GB228   GB241   GB259   GB281
GB060   GB088   GB144   GB176   GB205   GB217   GB229   GB242   GB261   GB282
GB061   GB097   GB145   GB178   GB206   GB218   GB230   GB243   GB267   GB283
GB062   GB100   GB153   GB179   GB207   GB219   GB231   GB244   GB268   GB284

Just to double-check: Anything surprising in this list?

Yeah,  a lot. I'll check :)!


Add: buddy_strings

Codecov Report

Merging #111 into master will decrease coverage by 0.71%.
The diff coverage is 81.81%.

@@            Coverage Diff             @@
##           master     #111      +/-   ##
==========================================
- Coverage     100%   99.28%   -0.72%
==========================================
  Files          49       50       +1
  Lines         541      563      +22
==========================================
+ Hits          541      559      +18
- Misses          0        2       +2
- Partials        0        2       +2

Impacted Files
Coverage Δ

problems/buddy-strings/buddy_strings.go
81.81% <81.81%> (ø)

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 6f5d6c6...564dee5. Read the comment docs.


Correct, TL does not support sub-only videos at the moment. See #531


Allow JSONSchema Custom Definitions to be tied to schemas for config contexts

Environment

Python version: 3.6
Nautobot version: 1.1.3

Proposed Functionality
Potentially create a new model to store definitions that can be referenced within schemas.
An example of what we have are the following:
property:
---
zip_code:
  oneOf:
    - type: "integer"
      min: 10000
      max: 99999
    - type: "string"
      pattern: "^[0-9]{5}(-[0-9]{4})?$"
    - type: "string"
      pattern: "^(?!.*[DFIOQU])[A-VXY][0-9][A-Z]\\s?[0-9][A-Z][0-9]$"

object:
---
lan_network:
  type: "object"
  properties:
    address:
      $ref: "../properties/ip.yml#ipv4_subnet"
    enable:
      type: "boolean"
  required:
    - "address"
    - "enable"

The object one also shows a ref to something existing so we'd want to re-use these within different aspects.

Use Case
We use custom JSON Schema definitions for both properties and objects and would like to move schema validation into the config contexts.

Database Changes
Potentially a new model for storing definitions of objects/properties

External Dependencies
N/A

We could solve this with a new model to store these instances and then have a many-to-many relationship to these instances and the schema objects. The problem then becomes how to handle the refs. I suppose when we load the schema, we would then load all the related instances and combine everything into a single JSON document (dict) at which point the refs become local to the document.

It doesn't seem like there is a lot of adoption here to justify this at the present moment. Closing for now.


fix(docs): fix GitHub repo link

The current GH link is a button, this replaces it with a nav-item.

👍 @yinonov it seems a little odd that the hamburger icon-button has pill shape but the git-hub link is rounded. I guess there's no need for pill shape in menu-item. Maybe menu item is not the right fit here at the end :) Works OK for now, though

so no action to take? should change menu shape?

👍 @yinonov it seems a little odd that the hamburger icon-button has pill shape but the git-hub link is rounded. I guess there's no need for pill shape in menu-item. Maybe menu item is not the right fit here at the end :) Works OK for now, though

so no action to take? should change menu shape?

I have no strong opinion on this. I can update the PR and remove the pill shape from the menu for consistency's sake.
(Note that the dark/light mode toggle doesn't have any shape btw.)

👍 @yinonov it seems a little odd that the hamburger icon-button has pill shape but the git-hub link is rounded. I guess there's no need for pill shape in menu-item. Maybe menu item is not the right fit here at the end :) Works OK for now, though

so no action to take? should change menu shape?

I have no strong opinion on this. I can update the PR and remove the pill shape from the menu for consistency's sake. (Note that the dark/light mode toggle doesn't have any shape btw.)

can open another PR to resolve the shapes.
regarding the dark mode toggle, it's a google web component and not our own, a tech debt we need to replace soon...

@YonatanKra notice beachball never required a change file for this PR.
Since there are changes to docs site (even though it has no effect on library) we should still publish the site.


feat(localization): update pseudo translation

Updated translation using Jenkins. Please review and merge @dfeinzimer
CC: @michi6571 @masa6674

Looks good based on the comment -  swift/issues/4768#issuecomment-4458934


Unable to use fork library with latest react-native-maps version - Getting lib/index.js not found

Summary
Our project is using a fork of react-native-maps. Previously, our fork was using react-native-maps 0.30. I updated our fork by synchronizing it with the latest version of react-native-map master branch. So now, it is using react-native-maps v1.3.2.
Following this update, our app does not start. Im running into the following error:
error: Error: While trying to resolve module react-native-mapsfrom file/path/projectname/folderA/folderB/file.js, the package /path/projectname/node_modules/react-native-maps/package.jsonwas successfully found. However, this package itself specifies a main module field that could not be resolved (/path/projectname/node_modules/react-native-maps/lib/index.js. Indeed, none of these files exist
When I check our node modules, I indeed do not see a lib folder

I tried changing our project to use the main lib instead of the fork (react-native-maps/react-native-maps), and then I reinstalled the packages (yarn install). Then rechecked the node_modules, and Indeed I see a lib folder, and the app starts successfully.

I tried forking this lib under my personal account (https://github.com/yousrasd/react-native-maps). When I use the master branch (which is up to date with this lib), same thing happens when I add this fork in the project: I run into 'this package itself specifies a main module field that could not be resolved' error.
I created a branch test that points to an old version of this lib (v0.30.1). When I use this branch in our project, the app STARTS! So now I confirm that there is something in one of the latest versions (versions 1.0.0 and up) that is causing me this error. Not sure if our project is missing a config or something. The project seems to be following the guidelines mentioned in https://github.com/react-native-maps/react-native-maps/blob/master/docs/installation.md.   Now react-native-maps is using typescript, could it be related? Its like the lib folder is only generated when I use directly your lib which is available on npm.
Update: seems like when I try using your librairy directly by specifying a specific target, I get the SAME behavior as with my forked lib.

No lib folder is present. So now, im thinking that there must be a job that is run that generates that lib folder before publishing the package to npm. That's why it works when I use your lib directly from npm, but doesnt, when I specify a github url. I see that you have a build phase in your package.json that seems to run before you deploy the package to npm (based on the following workflow https://github.com/react-native-maps/react-native-maps/actions/runs/3128916513/workflow#L30). Based on this finding, I guess that this step is generating the lib folder.
Reproducible sample code
In package.json, put a forked lib (make sure that the fork is up to date with latest version of react-native-maps).
  "react-native-maps": "https://github.com/yousrasd/react-native-maps",

then import the Marker from react-native-maps
import {Marker} from 'react-native-maps';

Steps to reproduce

Have a forked lib that is up to date with the master branch
Include it in your project
Run the app

Expected result
App should start
Actual result
App does not start.  An error is returned:

error: Error: While trying to resolve module react-native-mapsfrom file/path/projectname/folderA/folderB/file.js, the package /path/projectname/node_modules/react-native-maps/package.jsonwas successfully found. However, this package itself specifies amain module field that could not be resolved (/path/projectname/node_modules/react-native-maps/lib/index.js. Indeed, none of these files exist

React Native Maps Version
1.3.2
What platforms are you seeing the problem on?
iOS (Google Maps)
React Native Version
0.68.4
What version of Expo are you using?
Not using Expo
Device(s)
iPhone 14 Pro
Additional information
No response

I have a proposal for this. We can add a preinstall hook that runs the "tsc" command. This way the lib folder will be generated when forks are installed in projects.

The library as you see it in this repo isn't the same as hosted by Yarn/NPM. Before a developer submits a new release they usually run a couple of scripts to remove all files needed for development, and what you see on yarn is usually the dist/build/lib folder ready for use. See here
Having said that, in your own app add the following line to your scripts
 "postinstall": "cd ./node_modules/react-native-maps && yarn install && yarn build"
This will build the source code and produce the lib folder.

@yousrasd I tried forking this lib y'day and also was not able to get it to work via the yarn build command either. The only way I got it to work was by copying the contents of the original node_modules/react-native-maps folder and commit those to my fork (and disable the husky script). Which is not the recommended way of getting a fork to work....
But then as soon as I apply my fix  I receive the following error.

@WillyRamirez hmm interesting, I actually got it working with a postinstall script in the fork lib (as you can see in this branch https://github.com/yousrasd/react-native-maps/tree/adding-postinstall-hook). And it worked well in the project.
But the initial reason why I opened this issue is to see if this can be fixed in this lib directly. So that fork libs dont have to add postinstall scripts.

@yousrasd Ok that's smart. I put the postinstall script in my main app's scripts as seen in my first comment. I think yours is a better approach.


Minor Wording Issue in Fairness Audit Documentation

Problem Summary
https://github.com/epic-open-source/seismometer/blob/8ae4df17b4a934227dc05fd2b3d923984032ed97/docs/user_guide/index.rst?plain=1#L229-L230
The text above is confusing and is likely meant to say "the context might explain" instead of "the context might that explains"
Impact
Minor
Possible Solution
Update wording of documentation

Already fixed as part of #109


White block at bottom of page with "night" skin

It renders this way when being locally served as well.
Environment

Basically Basic version: 1.4.1
Ruby gem or remote theme version:
Jekyll version:
Git repository URL: https://github.com/RobertsLab/sams-notebook
GitHub Pages hosted (if yes provide URL to site): https://robertslab.github.io/sams-notebook/
Operating system: Ubuntu 16.04
Browser: Firefox

Expected behavior
Expect solid background color for entire layout.

Did you modify the theme files at all when forking?
Because when I clone your repo, remove the duplicated _layouts, _includes, assets and _sass folders, install the theme as a remote theme by adding `remote_theme: "mmistakes/jekyll-theme-basically-basic" to _config.yml, everything looks correct.
The white box disappears. Which tells me there's something different in your fork from the default theme.

Firstly, thanks so much for checking this out!

Did you modify the theme files at all when forking?

Unfortunately, I'm brand new to Jekyll, so I'm not hip to the lingo. I've modified some stuff, but I'm not sure which files constitute "theme files". So, the answer is: probably.

remove the duplicated _layouts, _includes, assets and _sass folders

Which duplicates? When I look in my repo, I only see those folders in the root directory. Are you referring to removing the "duplicates" found in /example/*?
Or, are you saying you performed the following steps:

Delete existing folders mentioned above.

Add remote_theme: "mmistakes/jekyll-theme-basically-basic" to _config.yml.

Build site (or, push to GitHub).

By theme files I mean everything in the _layouts, _includes, _sass and assets folders. Looks like you directly copied all of them from theme's repo. This is fine, but it's better to remove all of those folders/files and install as a remote_theme.
Doing it this way you can upgrade without needing to copy over files from the theme. By "duplicates" i was referring to those folders. I would suggest you remove them all as it looks like you modified something in one of the layouts that broke the layout.

You can remove example/ and docs/ as well since those are used for testing and the demo site.
Add remote_theme: "mmistakes/jekyll-theme-basically-basic" to _config.yml.
Replace the contents of Gemfile with:source "https://rubygems.org"
gem "github-pages", group: :jekyll_plugins

Run bundle install

Doing this you can build the site locally using the exact same gems GitHub Pages does. This is good to test that everything is working as expected before pushing up to GitHub for them to host your site.

Thanks! This definitely resolves the issue!
However, now that I don't have those folders any more, two quick questions:

If I'd like to change to font that's used throughout the site, what do I do?

How does the site render without those folders?

Have a look over Jekyll's docs on how themes work. When you install as a Ruby gem or remote theme those folders won't be in your repo anymore. They are pulled down and managed elsewhere to make updating easier.
The only reason you'd want to keep copies of these theme file in your repo is if you are overriding them.
If you want to change the font you can do so here, and then you'll need to change the CSS. Add any Sass variable changes or other declarations to this file. It will override what is bundled in the theme.


OCR language support for tamil language

It would be nice if the OCR supports tamil language too.

@javadevelopernextgen that can be done via paid support


Unable to read file 'vscode-userdata:/User/argv.json'

Error: Unable to read file 'vscode-userdata:/User/argv.json' (Error: Unable to resolve nonexistent file 'vscode-userdata:/User/argv.json')
    at o.w (workbench.web.main.js:612:16435)
    at o.v (workbench.web.main.js:612:16097)
    at async o.u (workbench.web.main.js:612:15379)
    at async C.h (workbench.web.main.js:1209:3485)
    at async C.getDefaultLogLevels (workbench.web.main.js:1209:2455)
    at async f.k (workbench.web.main.js:1700:32903)
    at async f.run (workbench.web.main.js:1700:32800)
    at async Object.accept (workbench.web.main.js:741:8127)

When and where are you seeing this? Can you please provide more information and also steps to reproduce?


Underline spacing too low after today's VSCode update.

Using v3.16.0
VSCode v1.88.0
I uninstalled and reinstalled, making sure there were no entries in my user settings JSON. Did not work.
Love this extension and can't live without it anymore.

I ... don't know how this relates. Does the underline fixes itself if you uninstall Error Lens extension?


Add Bootstrap

Hi.
You have great cheatsheets. But there is no Bootstrap!
I think it is better to add Bootstrap.  I can help you in that case.
Tnx.
Amir.

Hi again,
I did it! Added Bootstrap. in this Pull-Request #229.
Hope you like it.
May the force be with you!
Amir.


basic-client/task-giver recursively wait for finalized solution

Right now task-giver only waits up to a certain block number for a finalized solution. There is the very real case that due to the verification game being played, the amount of time needed to wait for a final solution is longer.
The solution would be to have a recursive function that recurs at the designated block number.

wasm-client is the priority now


LSIF Indexing Campaign

redux

as it turns out, this was the only repo which had this issue. going to fix manually in the morning

@gbrik @efritz can this be closed?

This doesn't currently work because lsif-tsc has an issue with multi-projects. We can close it, but leaving it opens serves as a good reminder to get this to work once we have the bandwidth.

@efritz am i misremembering that lsif-tsc now works for multi-projects?

@Strum355 Could you try running the master version of the indexer and see if it works? If so we can update the args here.

lsif-tsc -p . discovered no files. lsif-tsc **/*.ts did work


Code Improvisation + Fixed error

Found an python error in code: (-215) !empty() in function detectMultiScale
peace 👍

@jaivanti  There are some issues in this repo
So start contributing here https://github.com/Ishaan28malik/Get-Dev-Resources


BB Test Failing: Unauthorized Access Failure

Investigate and correct the implementation issue behind the failing blackbox test:
Unauthorized Access Failure

@tingyuz for visibility.

Moved to https://github.com/edgexfoundry/blackbox-testing/issues/305


[Docs] javascript-utilities changed.zf.mediaquery

$(window).on('changed.zf.mediaquery', function(event, newSize, oldSize){});

the newSize and oldSize vars seems to be reversed

i did a mistake


Add ALG_SET_DRBG_ENTROPY and ALG_SET_KEY_BY_KEY_SERIAL constants

ALG_SET_KEY_BY_KEY_SERIAL was added in Linux 6.2:
https://elixir.bootlin.com/linux/v6.2.16/source/include/uapi/linux/if_alg.h#L54
Also adding ALG_SET_DRBG_ENTROPY for completeness.

Regarding the test failures, I think the jammy package for linux-headers is still tied to kernel version 5.15, so this constant is missing.

:umbrella: The latest upstream changes (presumably #3404) made this pull request unmergeable. Please resolve the merge conflicts.

We recently updated Ubuntu images to 23.10, please rebase onto main.
Note that our musl header is old and you would have to tweak https://github.com/rust-lang/libc/blob/main/libc-test/build.rs.

@rzimmerman are you able to rebase to finish this?

@rzimmerman this should just need a rebase if you are able to get it over the line

Actually this should be all set, https://github.com/rust-lang/libc/pull/3404 added these constants. Closing since I don't think there is anything remaining here.


Use autodiff to compute derivative of loss

Currently, using gcp with a custom loss requires providing both the function and gradient:
https://github.com/dahong67/GCPDecompositions.jl/blob/116db757bf621df7248d34347a797a3fb9d3b971/src/gcp-opt.jl#L17-L18
Besides being less user-friendly, there is a potential for incorrect results if the user provides only the function but forgets to provide the gradient (in which case the code would use the default, i.e., least squares).
The goal of this PR is to replace the current default gradient with one that is computed from the function func via (forward-mode) automatic differentiation.

Decided to have Alex work on this in a fork instead.


Install error

Hi，
I install oktoberfest as follows,
pip install .
I got error as follows
#fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
error: subprocess-exited-with-error
× git clone --quiet<EMAIL_ADDRESS>#/tmp/pip-install-kv788z9s/spectrum-io_f0b43d357e3b48689e1385f2e9d33d2d did not run successfully.
│ exit code: 128
?─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.
#error: subprocess-exited-with-error
#× git clone --quiet<EMAIL_ADDRESS>#/tmp/pip-install-kv788z9s/spectrum-io_f0b43d357e3b48689e1385f2e9d33d2d did not run successfully.
#│ exit code: 128
#?─> See above for output.
#note: This error originates from a subprocess, and is likely not a problem with pip.
Shall I got some key in advance?
Best wishes
Yulan Deng

Hi，
I run pip install . , it appears that
<EMAIL_ADDRESS>password:
shall I got passsword?
best wishes,
Yulan Deng


Support for Angular 7

[x] Bug
[ ] Build issue
[ ] Feature request

Version info

Angular: 7.0.0
Angular CLI: 7.0.1
countup.js-angular2: ^6.0.1

Description

ng serve on Angular 7 fails due to:
ERROR in node_modules/@angular/core/src/render3/ng_dev_mode.d.ts(9,11): error TS2451: Cannot redeclare block-scoped variable 'ngDevMode'.
node_modules/countup.js-angular2/node_modules/@angular/core/src/render3/ng_dev_mode.d.ts(9,11): error TS2451: Cannot redeclare block-scoped variable 'ngDevMode'.

Ok. Just pushed 6.0.2 of this lib and tested it in a new Angular 7 project and it works 🎉

Hi,
Thanks, now works again. Could you extend the peer dependencies to avoid the warning?
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^6.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^6.0.0 but none is installed. You must install peer dependencies yourself.

What you could do is change it in node_modules/countup.js-angular2/projects/count-up/package.json to be v7:
"peerDependencies": {
    "@angular/common": "^7.0.0-rc.0 || ^7.0.0",
    "@angular/core": "^7.0.0-rc.0 || ^7.0.0"
  },

If I made the change here it would break for a lot of angular 6 users.

As far as know it is posible to suport both, ngx-ui-switch did this on https://github.com/webcat12345/ngx-ui-switch/commit/e37de190a6e360c6005177a57bca7a3ce0d5560e, can't tell if it would be that easy.
Maybe this afternoon I can try to PR this.


Fix nested multi-dimensional parfor type inference issue

The tuple index variable of multi-dimensional parfors was being assigned a dummy integer constant which is fixed. Resolves #2587.

Codecov Report

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

@@            Coverage Diff             @@
##           master    #2599      +/-   ##
==========================================
+ Coverage    86.5%   86.51%   +<.01%
==========================================
  Files         317      317
  Lines       63261    63267       +6
  Branches     7020     7020
==========================================
+ Hits        54727    54735       +8
  Misses       7426     7426
+ Partials     1108     1106       -2

Thanks for the fix, this seems good, merging.


Destroy of AWS OpenShfit cluster fails

When destroying an AWS OpenShift cluster, the following error is thrown:
TASK [destroy-aws : Destroy Openshift with AWS ROSA] ***************************
Sunday 17 September 2023  05:48:58 +0000 (0:00:00.035)       0:01:33.528 ******
fatal: [localhost]: FAILED! => {"msg": "The conditional check 'current_openshift_cluster.infrastructure.type  == 'rosa'' failed. The error was: error while evaluating conditional (current_openshift_cluster.infrastructure.type  == 'rosa'): 'current_openshift_cluster' is undefined\n\nThe error appears to be in '/cloud-pak-deployer/automation-roles/30-provision-infra/destroy-aws/tasks/main.yml': line 35, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: Destroy Openshift with AWS ROSA\n  ^ here\n"}

Then, once fixed, another error is issued:
TASK [destroy-aws : Destroy Openshift with AWS IPI] ****************************
Sunday 17 September 2023  05:55:46 +0000 (0:00:00.031)       0:01:34.615 ******
fatal: [localhost]: FAILED! => {"reason": "Could not find or access '/cloud-pak-deployer/playbooks/destroy-aws-ipi.yml' on the Ansible Controller."}

I've just started using the Cloud Pak Deployer with Self Managed AWS and hit this same issue today while trying to destroy a failed  cluster build.


[MOBILE] Add Wavlake wallet

I think we'll need to modify the accounting /send route to accept an optional zap request url param from the mobile app.
When included, the accounting API should process the payment (will always be an internal wavlake payment - no support for keysends from the mobile app) and then publish the zap receipt. The mobile app will then listen for the zap receipt. cc @blastshielddown

For zaps in the mobile app today, we are generating an invoice, then paying it somehow, and the accounting API publishes the zap receipt upon payment. Should we generate an invoice for wavlake wallet zaps? or call on the /send auth'd accounting API to do a wavlake wallet zap, and skip generating an invoice?


fix: move optimization

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


Provide an alternate qemu-guest-agent strategy to check VM's CAPI Sentinel file

Context
Following last Syncup Meeting (Tuesday April 18), we are now targeting multiple new features :

short term : bypassing Sentinel file check with a "none" policy
mid term : working on a alternate qemu-guest-agent usage to check file
long term : making the whole SSH logic optional (for keygen & cloud-init management...) with something like a Sentinel File check mode selector in spec

This Issue tracks mid term item 2.
Feature Description
Refering to https://github.com/kubernetes-sigs/cluster-api-provider-kubevirt/issues/230 , we need to check bootstrap status using something else than SSH, and only rely on the Kubevirt apiserver for everything (scheduling , probing, Sentinel checking, ...)
https://github.com/kubernetes-sigs/cluster-api-provider-kubevirt/issues/233 needs to be implmented first before start working on this issue.
Related Issues

https://github.com/kubernetes-sigs/cluster-api-provider-kubevirt/issues/230
https://github.com/kubernetes-sigs/cluster-api-provider-kubevirt/issues/233

quick update on this issue
I've been working for a couple days on it, and I'm now quite confident to says that current implementation is creating major problems on the road.
I'll try to explain as clearly as I can what is blocking us & what should be changed to implement qemu-guest-agent based checks in the VM's virt-launcher pod.
What is going on (during bootstrap check) ?

Machine reconciliation is triggered in kubevirt_machinecontroller.go
Reconcilier fetches & carries a global context with multiple compiled informations (vm, vmi, kubevirtcluster, kubevirtmachines, ssh keys ... )
Reconcilier builds the infra cluster kubernetes client

Depending the kubevirt topology (local or external), machine controller reuses existing capk controller client (based on controller-runtime) or builds a new one from a kubeconfig (based on controller-runtime too)

Bootstrap check is done in machine.go implementation that receive global context & manipulates this controller-runtime client to configure & trigger a SSH check
Bootstrap result is returned to reconciler

What is the problem ?
If we want to check bootstrap status using an exec command, we need the kubernetes client supporting such a feature.
But it seems that controller-runtime client is not able to run exec command on pods at all.
So the only (good) way to be able to trigger a pod exec from the code would be to rebuild a new kube client based on k8s.io/client-go (which supports spawning pod exec commands)
Although it's pretty easy to say, such a change requires extracting controller-runtime client's configuration in order to stay compatible with local / external setups. This configuration must therefore be extracted after building (or reusing) the infrastructure client (during step 3).
Also, extracting kube client configuration is not as simple as it looks. If we're reusing local controller client, it's not only "parsing a kubeconfig file".
Why it has a big impact ?
So far, I've identified & tested several things to implement to support such a change :

we need to make the infra cluster configuration available to the in the controller global context
this configuration cannot be extracted from an existing controller-runtime client. So it has to be created during the client build stage.
the machine bootstrap checker should be aware of this configuration, and build a ephemeral kube client using k8s.io/client-go lib
then it should use it when qemu-guest-agent check is asked

k8s.io/client-go lib allows building a new REST client from a rest.Config{} struct. We can easily return it during client generation because we already working with it (https://github.com/kubernetes-sigs/cluster-api-provider-kubevirt/blob/main/pkg/infracluster/infracluster.go#L75-L78).
Building a REST client also requires codecs & gvk scheme that we may carry along the way too (https://pkg.go.dev/sigs.k8s.io/controller-runtime/pkg/client/apiutil?utm_source=godoc#RESTClientForGVK)
technical focus
In order to make this working we'd need several changes :

GenerateInfraClusterClient func, in addition from returning the right controller-runtime client, should also returns k8s.io/client-go/rest rest.Config configuration.
this configuration should be carried along the rest of the reconiliation context
All controllers should ignore this new configuration except bootstrap_controller that will pass it to externalMachine object (r.MachineFactory.NewMachine)
the externalMachine implementation will avoid using an existing controller-runtime client but rather take a rest.Config{} as input and build a generic go client that is both able to check CRD specs & status but also run exec command depending the bootstrap check mode

Since the rest.Config{} is sufficent to create a new client but is also transparent for both local and remote configurations, it seems to be a good pivot to make bootstrap check a bit more independant from main controller kube client.
Proposed action items

Extract rest.config{} during controller client generation. Update all dependencies & tests
Make rest.config{} available in context
Adapt machine controller & external machine implementation to support rest.config{} for every kube request instead of existing controller-runtime client

this is probably better than maintaining 2 clients for the same infra cluster in the same package

I've already started a concept (https://github.com/BarthV/cluster-api-provider-kubevirt/tree/guestagentcheck), but the change is huge and I realized that it cannot fit in a single PR.
Let's discuss about this plan (or any other possible ones) on next meeting

/remove-lifecycle stale


Aeon.co Extractor

IMPORTANT: PRs without the template will be CLOSED
Description of your pull request and other information

This feature branch permits extractions from https://aeon.co without requiring that the referrer argument be given. It works by matching the first instance of the vimeo video id, then passing a vimeo player url to the VimeoIE extractor, as a referral. Two tests have been added to verify a pattern in the placement of the hosterId.
It has been tested with pytest and linted with flake8.
Fixes #1653
Template

Before submitting a pull request make sure you have:

[X] At least skimmed through contributing guidelines including yt-dlp coding conventions
[X] Searched the bugtracker for similar pull requests
[X] Checked the code with flake8 and ran relevant tests

In order to be accepted and merged into yt-dlp each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[X] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Fix or improvement to an extractor (Make sure to add/update tests)
[X] New extractor (Piracy websites will not be accepted)
[ ] Core bug fix/improvement
[ ] New feature (It is strongly recommended to open an issue first)

The download tests fail


Nat a issue : a request, add a edge panel for samsung

please add a edge panel for Samsung galaxy devices like this app - https://play.google.com/store/apps/details?id=com.edgepro.controlcenter  thanks

The app you mentioned seems to make it's own edge panel. But it's also possible to make a plugin for the official edge panel by using samsung's edge sdk. I could use the SDK but it will only be available on Samsung devices which support this feature.


Configure Azure Pipelines

This pipeline configuration builds the application and produces a build for the release configuration

 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.:x: VenkateshPheonix sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


Implement react-top-loader for Page Loading Indication Description:

To improve user experience during page loads, I propose integrating the react-top-loader component into VigyBag. This will provide a visual indication of page loading progress, enhancing the overall user interface.
Objective:

Implement react-top-loader: Integrate the react-top-loader package to display a loading bar at the top of the page.
Ensure Seamless Integration: Ensure that the loader appears during page transitions and completes when the page is fully loaded.

Kindly assign me this issue under GSSOC'24 .

Issue changed due to current needs and fulfilment of the previous raised issue.


help request: fluentbit namespace

Describe the issue
If I create a fluentbit resource on the same namespace it is created, but If i create a fluentbit resource on an anotther namespace nothing happened.
Since FluentBit is a namespaced resource I assume there is a way that configure the operator to watch on all namespace, but I not found that.
How did you install fluent operator?
I've installed the operator with helm.
Additional context
No response

I have the exact same issue.
Installed the fluentd operator via Helm Chart, but fluentbit crd resources only gets picked up when created in the same namespace as the operator.
For fluentd I seems to work for different namespaces, though.

+1


Add .idea ignore

Reasons for making this change:
Add ignore to folder .idea/
Links to documentation supporting these rule changes:
TODO
If this is a new template:

Link to application or project’s homepage: TODO

It appears as though the android template already ignores some of the files within the .idea folder. The ones that are not ignored are useful to include in a project as they deal with project configuration, such as scripts, linters, vcs, & etc. Essentially, there's a reason why the entire folder isn't ignored, and only the "personal" files are.


Remove mkinitrd script.

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

[x] The toolchain has been rebuilt successfully (or no changes were made to it)
[x] The toolchain/worker package manifests are up-to-date
[x] Any updated packages successfully build (or no packages were changed)
[x] Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
[x] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
[x] All package sources are available
[x] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
[x] LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
[x] All source files have up-to-date hashes in the *.signatures.json files
[x] sudo make go-tidy-all and sudo make go-test-coverage pass
[x] Documentation has been updated to match any changes to the build system
[ ] Ready to merge

Summary
This changes removes the mkinitrd script and replaces all calls with direct calls to dracut.
In addition, the /boot/initrd.img- file has been renamed to /boot/initramfs-.img to match the default name used by dracut. This avoids needing to add a patch to dracut to change the default name of the initrd file.
Also, previously the mkinitrd script passed the --hostonly flag to dracut to ensure the hostonly option was enabled. This has been replaced with setting the hostonly only in the /etc/dracut.conf file instead. One nice advantage this provides is that it allows a user to override this default by adding a config file under the /etc/dracut.conf.d directory.
Change Log

Remove mkinitrd script.
Rename /boot/initrd.img-<kver> to /boot/initramfs-<kver>.img.
Set hostonly to yes in /etc/dracut.conf.
Call dracut directly in iniramfs package post-install scripts.

Does this affect the toolchain?
YES, but only a kernel-headers version bump.
Test Methodology

Built image locally and booted it in a VM.

A message from dracut upstream regarding the intention of standardizing the naming of the generated initramfs.
https://github.com/dracut-ng/dracut-ng/pull/160
https://github.com/uapi-group/specifications/issues/100
You should perhaps consider keeping the initrd-$KVER naming schema.


Initialization of the bias in the last layer of the MLP

Hi Anpei,
thanks for the awesome work. I want to ask about a small implementation detail:
what is the reason/benefit for initializing the bias to zero here:
https://github.com/apchenstu/TensoRF/blob/3948381077dc68767c2ae27ab6cb7118825efea6/models/tensorBase.py#L72

Hi, the initialization would not matter a lot, you can also remove it to simplify.

Thanks for the answer!


Clarify when the state manager does not automatically save state

We recently discovered that our actor methods don't automatically save the state at the end of the method if an exception is being thrown back to the caller, resulting in the updates being lost. It would be helpful if the documentation clarified that state will need to be manually saved using SaveStateAsync() in that case.
Thanks

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

ID: 62631e1c-e929-cd0e-02a4-ed5bbd8cccd4
Version Independent ID: bb841930-95ba-c7d5-ae59-35ab97bdc532
Content: Manage Azure Service Fabric state - Azure Service Fabric
Content Source: articles/service-fabric/service-fabric-reliable-actors-access-save-remove-state.md
Service: service-fabric
GitHub Login: @vturecek
Microsoft Alias: vturecek

@ashleyswanson360
Thanks for the feedback! I have assigned the issue to content author to check and update the document as appropriate.

@vturecek
Can you please check and add your comments on this doc update request as applicable.

Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. Though the scope of our feedback channel here on GitHub covers specific documentation fixes, we can help redirect you to the right support channel to get an answer to your question: [reference to alternative product/service or community endpoint]. Because this issue does not relate to documentation, we are closing this issue. #please-close


When doing a v1 deploy, throw an error if .nowignore is present

Since .nowignore is ignored in a v1 deploy, it would be helpful to let the developer know at deploy time if they try to use it by mistake.
I don't see a reason not to throw an error, though if there is some reason, a warning could suffice!
c.f. https://spectrum.chat/zeit/general/troubleshooting-source-file-selection-in-v1~8dc07b08-99ac-4a02-bfc6-6d40d5e44792?m=MTU0OTQ5MDQ4MDAzNg==

Thank you for creating this issue!
Please note that – in order for us to be able to handle each feature request with care – we have to consume all of them through a unified pipeline that makes it easier for us to prioritize, track and progress on the features our user base is interested in.
In turn, the Issues tab on this repository is best only be used for reporting bugs, which we can immediately act on.
For well-explained feature requests (like the one you just posted), please contact us at<EMAIL_ADDRESS>so that we can consider adding it to our roadmap.


[stdlib] Simplified generic error code module.

The codes start at 2000 such that lower codes are available for ad-hoc error reasons. The codes have been adopted from Google's canonical error codes, which in turn are derived from Unix error codes (see here). Each code has an associated HTTP error code which can be used in REST apis.
Moving forward, applications can continue to use per-module error reasons and the associated errors map tooling, or rely on symbolized stack traces to identify the reason of an error.

Just bringing up this minor point: by starting from 2000 we would effectively disturb the custom based error codes scheme (being linear, or bitmask based), as these predefined codes could lie "in the middle" of the 64bit word.
I would propose starting the numbering from the most significant bit, that way isolating the predefined error codes to the upper part of the word, leaving the rest of the word free for either linear or bitmask based custom error codes. Creation of the error code could be implemented as a function in the errors module.
(Btw, I also see merit in the errmap approach, mainly because of extendibility, but in that case I would get rid of the error codes altogether, placing all the error information in the metadata / source code.)

Just bringing up this minor point: by starting from 2000 we would effectively disturb the custom error codes scheme (being linear, or bitmask based), as these predefined codes could lie "in the middle" of the 64bit word.

Adjusted this now. The highest bytes aren't practical because we need to use literals in Rust constant declaration, but I use now 0xCCRRRR with C category and R reason.

I would propose starting the numbering from the most significant bit, that way isolating the predefined error codes to the upper part of the word, leaving the rest of the word free for either linear or bitmask based custom error codes. Creation of the error code could be implemented as a function in the errors module.
(Btw, I also see merit in the errmap approach, mainly because of extendibility, but in that case I would get rid of the error codes altogether, placing all the error information in the metadata / source code.)

I'm not going to justify to you the need for canonical errors, which is accepted industry wide for web protocols. We had this discussion already long ago. You should accept this and not try to convince me canonical errors aren't needed.
I'm not sure what to say, but basically you broke the way how we at Aptos do  errors (which we plan to continue to do), and how the prover does errors. I'm trying to fix this in some way but the feedback I'm getting here indicates we need to branch the standard library.

I'm trying to fix this in some way but the feedback I'm getting here indicates we need to branch the standard library.

Sorry, @wrwg, I am not trying in any way to say that this change can't go in. Especially since its more or less a hard-coded version of the behavior that used to be there. I just wanted to highlight that I think that there is a lot we can do in the short term here, so this precise change might not be needed. I was only hoping to minimize churn if we were going to turn around and do something different next week :)
I was very intrigued by the idea you had presented about having a string or a category with a string. And was trying to get some feedback myself on an non-breaking implementation strategy for that idea you had presented earlier, with this example:
abort errors::invalid_argument(), "An invalid ASCII character was encountered when creating an ASCII string"

I think this is a good compromise, because in fact currently there are little cycles available to revamp errors in a larger style.

I agree. Very much in favor of moving forward with this, thanks!

Need approval to land this, @davidiw you could jump in as Todd/Sam seem to agree on this as the best we can do for now.


Toggle to view HTML

Are there plans to allow a button to toggle to HTML like Froala does? We are using ngx-wig now, and the user asked me to enable the "<>" button to see what is going wrong with the markup.  For now, I could flip them into a text area.

Not sure whether APIs have changed, isSourceModeAllowed does not exist;
Here is one way of achieving what you want.
https://stackblitz.com/edit/ngx-wig-sample-plugins-supbgz?file=src%2Fapp.ts

overLoading "edithtml" for BUTTONS injection token
some css wizardry


oauth2: cannot fetch token: 400 Bad Request

Can't get local drive initialized, drive init returns:
oauth2: cannot fetch token: 400 Bad Request
Response: {
"error" : "invalid_grant",
"error_description" : "Code was already redeemed."
}
I have:
run drive deinit
deleted .gd
checked app permission in Google account, none there
made sure all other Google accounts are closed
retried numerous times - same error
Other apps have no issues with tokens

Rebooted
Was using Firefox, but changed to Chromium to retrieve token
Drive initialized

Sorry for the late reply, I was tied up in meetings. Glad to know you resolved this issue. Also welcome to drive!


add sphinxcontrib-video to conda-forge

After this is on conda-forge  we can nicly embed mp4 videos on rtfd
https://sphinxcontrib-video.readthedocs.io/en/latest/quickstart.html

https://github.com/conda-forge/staged-recipes/pull/26407

for RTFD it only needs to become added to our environment.yml


Initial commit

Description

Tests and Documentation

This doesn't seem like a proper pull request as it's mostly just notebook output. If there are contributions you would like to make please open an issue first to discuss and plan the contribution. We value all genuine contributions and feedback you may have. In that spirit, I'm going to close this PR.


fix(persist-state): Allow in non-browser

Allow persistState in non-browser environments.
PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/datorama/akita/blob/master/CONTRIBUTING.md#commit
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

persistState currently cannot be called outside of a browser environment.
Issue Number: N/A
What is the new behavior?
Added the enableInNonBrowser option which defaults to false to optionally allow persistState to run outside of a browser environment.
Does this PR introduce a breaking change?
[ ] Yes
[x] No

Other information

What's the use-case?

What's the use-case?

I'm using Akita in an NativeScript Android application, so it's not running in a browser environment. However, I do want to use persistState the same way as I would in a browse,. so I implemented PersistStateStorage to get and set the items from Android's Application Settings.

The issue is SSR.

Adding a return when not in a browser environment completely prevents the use of persistState in environments like NativeScript, even though there isn't anything browser-specific in persistState.
I'd say not calling persistState during SSR isn't the responsibility of the persistState-function.

Agree. But this is a breaking change, so I need to think about it.

I like the idea of extending Akita over to the server side, it would further enhance the NestJS/Angular experience by allowing server side stores to use Akita APIs. As it is a breaking change, perhaps a config flag could be offered instead that defaults to the current functionality for non-browser environments, but can be manually configured to allow it.

Yes, I thought about adding a config option. Let's go with it for now.

I would love to see this landed as I'm trying to use Akita in a NativeScript app too, and it currently gives me an error:
System.err: ReferenceError: window is not defined
System.err:
System.err: StackTrace:
System.err: 	push.../node_modules/@datorama/akita/fesm5/datorama-akita.js.Store.destroy(file:///node_modules/@datorama/akita/fesm5/datorama-akita.js:1179:0)
System.err: 	at push.../node_modules/@datorama/akita/fesm5/datorama-akita.js.EntityStore.destroy(file:///node_modules/@datorama/akita/fesm5/datorama-akita.js:2539:0)
System.err: 	at push.../node_modules/@datorama/akita/fesm5/datorama-akita.js.Store.ngOnDestroy(file:///node_modules/@datorama/akita/fesm5/datorama-akita.js:1145:0)
System.err: 	at callNgModuleLifecycle(file:///node_modules/@angular/core/fesm5/core.js:20320:0)
System.err: 	at push.../node_modules/@angular/core/fesm5/core.js.NgModuleRef_.destroy(file:///node_modules/@angular/core/fesm5/core.js:20921:0)
System.err: 	at push.../node_modules/nativescript-angular/platform-common.js.NativeScriptPlatformRef._livesync(file:///node_modules/nativescript-angular/platform-common.js:220:0)
System.err: 	at (file:///node_modules/nativescript-angular/platform-common.js:102:74)
System.err: 	at push.../node_modules/nativescript-angular/zone-js/dist/zone-nativescript.js.ZoneDelegate.invokeTask(file:///node_modules/nativescript-angular/zone-js/dist/zone-nativescript.js:421:0)
System.err: 	at push.../node_modules/nativescript-angular/zone-js/dist/zone-nativescript.js.Zone.runTask(file:///node_modules/nativescript-angular/zone-js/dist/zone-nativescript.js:188:0)
System.err: 	at push.../node_modules/nativescript-angular/zone-js/dist/zone-nativescript.js.ZoneTask.invokeTask(file:///node_modules/nativescript-angular/zone-js/dist/zone-nativescript.js:496:0)
System.err: 	at ZoneTask.invoke(file:///node_modules/nativescript-angular/zone-js/dist/zone-nativescript.js:485:0)
System.err: 	at timer(file:///node_modules/nativescript-angular/zone-js/dist/zone-nativescript.js:1561:0)
System.err: 	at invoke(file:///node_modules/tns-core-modules/timer/timer.js:20:30)
System.err: 	at push.../node_modules/nativescript-angular/zone-js/dist/zone-nativescript.js.ZoneDelegate.invoke(file:///node_modules/nativescript-angular/zone-js/dist/zone-nativescript.js:388:0)
System.err: 	at push.../node_modules/nativescript-angular/zone-js/dist/zone-nativescript.js.Zone.runGuarded(file:///node_modules/nativescript-angular/zone-js/dist/zone-nativescript.js:151:0)
System.err: 	at (file:///node_modules/nativescript-angular/zone-js/dist/zone-nativescript.js:129:0)
System.err: 	at run(file:///node_modules/tns-core-modules/timer/timer.js:24:0)
System.err: 	at com.tns.Runtime.callJSMethodNative(Native Method)
System.err: 	at com.tns.Runtime.dispatchCallJSMethodNative(Runtime.java:1209)
System.err: 	at com.tns.Runtime.callJSMethodImpl(Runtime.java:1096)
System.err: 	at com.tns.Runtime.callJSMethod(Runtime.java:1083)
System.err: 	at com.tns.Runtime.callJSMethod(Runtime.java:1063)
System.err: 	at com.tns.Runtime.callJSMethod(Runtime.java:1055)
System.err: 	at com.tns.gen.java.lang.Runnable.run(Runnable.java:17)
System.err: 	at android.os.Handler.handleCallback(Handler.java:873)
System.err: 	at android.os.Handler.dispatchMessage(Handler.java:99)
System.err: 	at android.os.Looper.loop(Looper.java:201)
System.err: 	at android.app.ActivityThread.main(ActivityThread.java:6810)
System.err: 	at java.lang.reflect.Method.invoke(Native Method)
System.err: 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:547)
System.err: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:873)

@beeman you have a different issue. I just fixed it. You can try the latest version. (v4.10.6)

@sjroesink will you update the PR to support this new option?

@NetanelBasal The PR is updated.

Thanks @NetanelBasal, that was fast 🙏


What's the roadmap of the nanorpc

Hi Mr. sroycode,
What's the roadmap of the nanorpc?
This poject has not update for about 3 years.
nanomsg has published  1.0 version.
What's your opion for  nanomsg + protobuf  vs  zeromq + protobuf  as RPC framework.
Thanks a lot.

I will take a fresh look at this in Dec. The zqrpc code too has gone through quite a bit of cleanup which I have not been able to post to github.


Add support clusterlinks command

Issue: #2755
Make sure that:

[x] You have read the contribution guidelines.
[x] You have created a feature request first to discuss your contribution intent. Please reference the feature request ticket number in the pull request.
[x] You applied code formatting rules using the mvn formatter:format target. Don’t submit any formatting related changes.
[x] You submit test cases (unit or integration tests) that back your changes.

Awesome, thanks for the contribution!


Added a footer to the page

I want this tutorial example kept simple as it is for complete beginners; I don't want features or complicated stuff like animation added.


Version 2.2 compatibility

I used this package before with Laravel 4 and it worked like a charm. Now I was using the version 2.2 with a Laravel 5.1 app and it seems like the different ways of registering shortcodes don't really work with this version of the library.
I was looking at the code and noticed it now uses a package named thunderer/shortcode which validates that the function that will parse the shortcode is a callable, which will throw an error when trying to use for example the syntax 'ClassPath@method' or just 'ClassPath' (assuming the class has a register method defined). So the current version only supports a closure or anything that can be called as a function. I can confirm this because I updated my composer.json file to use the version 2.1 instead and now it works.

Same issue here. since the last composer update with "~2.1" it throws the error, now i've temporarly fixed by version 2.1


(maint) Add ip and vmhostname keys to SPARC nodes

[skip-ci]

Merge after release freeze.

/cc @johnduarte

:+1:

Will need a rebase after https://github.com/puppetlabs/facter/pull/1161 is merged.


Tidy up resolver import suggestions

Motivation

Some of the suggestions were redundant. In particular, if there was already an
autocorrect, we don't need another ErrorLine saying the same thing.
There was a lot of visual noise. Especially when the constant names and file
names are huge, that distracts from the core message.

This should hopefully cut down on some of the chunder.
I was following this build as inspiration for what it looks like right now:
http://go/builds/bui_LTKnw0Jy0zpU6h
Test plan

exp files

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:
→ https://go/builds/bui_LTNMbDByG9ZoTt
→ https://go/builds/bui_LTNMX6oTvAgAxH


Set proper default values to avoid warnings when overriding

We need to set proper default values for nodeSelector, tolerations and affinity. If we don't set proper default values({} or []) and you override e.g. nodeSelector you will get warnings from Helm.
e.g.
coalesce.go:165: warning: skipped value for nodeSelector: Not a table.

The end result is still correct, but it is very annoying to get warnings in the build when we create our Helm chart with overrides for these values

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: salaboy
If they are not already assigned, you can assign the PR to them by writing /assign @salaboy in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Hi @PashCracken. Thanks for your PR.
I'm waiting for a zeebe-io member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

I tried that in the first change to the previous pull request. And then you asked me to add it back. Will not the helm chart fail if you don't create the values in the base helm chart and don't provide an value when you use it. I really don't see the problem with adding {} and [] that is the standard in all new helm charts you create based on the helm template. It just reflects the default values documented in the readme file


Announcement TODOs

Before announcing this package there are a few things that need to be set up:

[x] Add logo
[x] some level of testing

customizations on components should be tested (i.e. if I call with* on a component, I expect it to look different or behave different)

[x] Add favicon
[x] Good documentation and on-boarding for contributors

[x] unimplemented components must link to a contibuting doc
[x] CI/CD Pipepline

[x] elm-format check
[x] elm-analyze check
[x] elm-review check

https://package.elm-lang.org/packages/jfmengels/elm-review/latest/

[x] elm-test check
[x] elm-verify-examples check (https://github.com/stoeffel/elm-verify-examples)

[x] pull request template
[x] issue template (feature request vs. bug report)

[x] Publish Package (link)
[x] Once published, update ellie links on examples
[x] Do not expose elm-css api

[x] src/Ant/Palette.elm
[x] src/Ant/Typography.elm

[x] Add donation button
[x] MVP set of components

[x] Button
[x] Typography
[x] Icon
[ ] Input
[ ] Form
[x] Tooltip
[x] Layout
[ ] Grid
[ ] Message
[x] Menu

[x] Thorough documentation on the MVP set of components
[x] Basic theme customization functionality
[x] Fully fleshed out showcase site
[x] Final read through package design docs:

https://github.com/dillonkearns/idiomatic-elm-package-guide
https://package.elm-lang.org/help/design-guidelines

We have liftoff 🚀


Use pivot on 2 columns only in a data set with for example 4 columns

I want to use .pivot() to pivot only 2 columns that I have in a data table.  Below is the input format and the expected output format.  So far, I was not able to create the expected output.  Can you help ?
INPUT - Columns
["Name", "Product", "Measure Type", "Measure Value"]
INPUT - Data
["Andrew", "Tables", "Discount", 20],
["Andrew", "Tables", "Profit", 10],
["Andrew", "Tables", "Sales", 2120],
["Marc", "Tables", "Discount", 40],
["Marc", "Tables", "Profit", 6],
["Marc", "Tables", "Sales", 3200],
["Marc", "Desks", "Discount", 20],
["Marc", "Desks", "Profit", 8],
["Marc", "Desks", "Sales", 2200]
Expected Output - Columns
["Name", "Product", "Discount", "Profit", "Sales"]
Expected Output Data
["Andrew", "Tables", 20, 10, 2120],
["Marc", "Tables", 40, 6, 3200],
["Marc", "Desks", 20, 8, 2200]

Thx Nicolas for your quick response. I give it another try this evening; will do a test in jsfiddle so that I can share if I still have a problem.

Nicolas,
I can now pivot the data, but I expect as output again an array of arrays; just like my input. And thus not a rendered table or heatmap, etc.  How can prevent pivot() from rendering towards these forwards and just give me a outputData back ?
This is my code:
var inputData = [
["Name", "Product", "Measure Type", "Measure Value"],
["Andrew", "Tables", "Discount", 20],
["Andrew", "Tables", "Profit", 10],
["Andrew", "Tables", "Sales", 2120],
["Marc", "Tables", "Discount", 40],
["Marc", "Tables", "Profit", 6],
["Marc", "Tables", "Sales", 3200],
["Marc", "Desks", "Discount", 20],
["Marc", "Desks", "Profit", 8],
["Marc", "Desks", "Sales", 2200]
];
var utils = $.pivotUtilities;
var heatmap =  utils.renderers["Heatmap"];
var sum =  utils.aggregators["Sum"];
$("#output").pivot(
inputData, {
rows: ["Name", "Product"],
cols: ["Measure Type"],
vals: ["Measure Value"],
aggregator: sum(["Measure Value"]),
renderer: heatmap
});

Ah, this library is designed as a rendering library, not an array-to-array transformation system.


Vane enchantments will not load, other plugins will

There is no error returned in the logs, and it also seems that the permissions plugin is missed as well. They aren't even mentioned in the console.

I'm sorry, if they are not even mentioned in the logs that 100% points to an installation error or issue with your system. Before any logic of the plugins even comes into play, they will be mentioned in the logs by the plugin loader.
Can be a lot of things. Maybe a file permissions issue, or the files were not completely downloaded, or a previous error in your logs.

Feel free to comment here if you gain additional insights.


[sequencer] Bids should expire

There's no need to have a bunch of bids hanging around, we can put them into Redis with a 10 min expiry or so.

I'm not following the logic here. Are you saying we should delete bids after 10 mins bc they probably are invalid bids, or just to clean out the DB as we go?
Counterexample:

Router A bids for a 2-router multipath transfer
Nothing happens for 10 mins
Router B comes online and bids for a 2-router multipath transfer

This would probs lead to some unexpected behavior. When it comes to deleting old bids, we should probs just track when a transfer has gone over 30 mins and/or has been reconciled... no sense in executing fast liquidity at that point.

I agree with you here. We should actually just remove bids that have been reconciled. I will change the scope of this task.

@rhlsthrm @jakekidd Is this a hard blocker to amarok public testnet/router integration?

It seems like we need to rescope this task to account for multipath CC @jakekidd @alexwhte. Will close and rescope around this later. It's not a blocker.


No Github activity

Greetings,
most likely I'm missing something obvious, but I enabled Greenkeeper on one of my repos and although I get activity reports from Travis (commits), I can't see anything happening on Github (no PR, commit, ...)
https://travis-ci.org/pascalduez/postcss-map/builds
https://github.com/pascalduez/postcss-map/pulls

afaik greenkeeper will only do a pr if a dep updates and a) the build fails b) the version is bigger than allowed in package.json
so if you have 1.0.x and the dep updates to 1.0.2 and it doesn't break your tests, greenkeeper will not do a pr

Hey @pascalduez,
@AdriVanHoudt explained it already. As long as versions that are covered by your existing version range don't fail your tests there is no need to bother you with a PR, as everything still works as expected. Should any of these builds fail you'll see GitHub activity (i.e. a PR).
If there is a new version of your dependency outside of the current version you'll get the PR either way.
Thanks for asking, and thanks for the explanation @AdriVanHoudt,
Best,
Stephan

Np, glad I got it right

Thanks guys for the explanations, indeed, makes much sense.

It used to do that?

As in it did, it doesn't anymore?

It probably did before they added support for version ranges October 7th https://github.com/greenkeeperio/greenkeeper/issues/27#issuecomment-146212266.


Minimal tooling for doing Drip-surveys with Qualtrics

Depends on #59

@nedbat: Review?

@nedbat: Can I get a re-review?

:+1:, because I don't feel like typing another comment saying, "you need a docstring here."

Clearly we need pylint turned on to complain about my lack of docstrings so you don't have to. I'll add them.


pull request for e2e test at 12/02/2016 23:26:04

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


No microphone on Precursor

Because Precursor doesn't have any microphone, would you ship also something like https://www.aliexpress.com/item/32855198716.html together with Precursor to not force everybody wear a headset?

The choice of microphone to use will be up to user! If they prefer to use something like that, then they are welcome to use it.

Of course off-the-shelf PCB-mountable microphones are not trustworthy - but is there any other choice if the device has nothing built in? Speakers apparently are safe enough (judging based on the Crowd Supply Precursor page).
So why not to build an own mic? (there are many other takes on DIY microphones among hifi & radio communities)
It wouldn't increase the device's cost much and would make the use of the device much more likely as currently the device fails in the last mile as it forces one to buy some untrustworthy mic.
I hope there is still time to change this before Beta Custom SoC-based system for early adopters. (taken from Development Plan)  gets to production.


trino-cli: init at 387

Description of changes
Add trino-cli. The Trino CLI provides a terminal-based, interactive shell for running queries
Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

@legendofmiracles thanks for the review!

@legendofmiracles I believe I addressed all of your comments. Please take a look when you get a chance. Thanks!

@legendofmiracles comments addressed, thanks!

@legendofmiracles done.


Adds spo tenant settings list command

Adds spo tenant settings list command. Solves #548

Coverage remained the same at 100.0% when pulling 410f0197a67724a38a6a97f23b852117b3e910b6 on VelinGeorgiev:tenant-settings-list into 7f50b9a67d9c197e4dbf9cff68b7be2a03f7fa4d on pnp:dev.

Nice! I'll have a look shortly!

Works like a charm! Nice job with the enums!

Merged manually! Thanks @VelinGeorgiev!


backend.view_jobs()

Many times we want to be able to view the jobs we have ran and save on the cloud.
In the spec, we defined a  backend.jobs() method which returns job objects. The problem is if this returns a job object then service that requires the job to be deleted after it has been called it removes it from the cloud. Since the use case is just to have a way of checking on all my jobs
for ran_job in backend.jobs(limit=5):
    print(str(ran_job.job_id()) + " " + str(ran_job.status()))

5bba0ceb1a814c003cbfdda2 JobStatus.CANCELLED
5bba0c3d5d72db004c6e1867 JobStatus.DONE
5bba0c3dc6992500552f155c JobStatus.DONE
5bb9b0f19458ec0044ab4954 JobStatus.DONE
5bb9abd60b99f20045d26437 JobStatus.DONE

I suggest that we change this to
backend.view_jobs()

Are there any other things that should be displayed. I think something like a message to add that is human readable if an error occuers.

This works as long as they don’t delete and I can get enough meta data to eventually go into an activity monitor.


jruby: Try to use JDK version of Xalan

What problem is this PR intended to solve?
See https://github.com/sparklemotion/nokogiri/security/advisories/GHSA-qwq9-89rg-ww72 for documentation on a vulnerability in Xalan, and a note that upstream Xalan is no longer maintained.
See https://github.com/sparklemotion/nokogiri/issues/1829 for a conversation about alternatives to Xalan
This PR attempts to use the JDK's vendored version of Xalan, with only limited success ...
The Good
On a positive note, the majority of the changes are simply updating the package paths.
The Bad
However, I've discovered that OpenJDK pulled in Xalan 2.6.0 (see https://github.com/openjdk/jdk/commit/74f4779) which predates the version of Xalan used to implement Nokogiri and so now I'm a little worried about whether JDKs will all have the same API? Over time this detail has emerged in issues like https://github.com/sparklemotion/nokogiri/issues/1114 and commits like c5ad35a and 6cf2b6e.
I worked around this assuming OpenJDK's API, but I'm worried about portability.
The Ugly
Finally, it looks like the Xalan imported into OpenJDK is incomplete and does not contain the class equivalent for Xalan's ./src/org/apache/xalan/transformer/TransformerImpl.java. In this PR I've used
import com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl;

which is incorrect and results in this compiler error:
ext/java/nokogiri/XsltStylesheet.java:188: error: cannot find symbol
    SerializationHandler serializationHandler = transformer.createSerializationHandler(streamResult);
                                                           ^
  symbol:   method createSerializationHandler(StreamResult)
  location: variable transformer of type TransformerImpl

com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl is the analog for Xalan's ./src/org/apache/xalan/xsltc/trax/TransformerImpl.java which seems to be a very different class despite similar names. I'm not familiar enough with this library to completely understand how these classes are related, and I need help resolving this issue.
Tagging @headius for assistance!
Have you included adequate test coverage?
Existing test coverage should prevent any regressions.
Does this change affect the behavior of either the C or the Java implementations?
Ideally there will be no behavioral changes, the test suite should help us stay accountable.

took a quick look and here's smt that might unblock this (the ugly part): https://github.com/sparklemotion/nokogiri/pull/2644

for the record, after merging with #2644 I am seeing: 4 failures, 3 errors (using OpenJDK 11)
... the errors are related to the part changed as part of #2644 (which is likely still be fixable)
Error:
Nokogiri::XSLT::Stylesheet#test_transform:
Java::ComSunOrgApacheXmlInternalSerializerUtils::WrappedRuntimeException: The Properties object passed to the SerializerFactory does not have a 'method' property.
    java.xml/com.sun.org.apache.xml.internal.serializer.SerializerFactory.getSerializer(SerializerFactory.java:172)
    nokogiri.XsltStylesheet.serialize(XsltStylesheet.java:188)
    nokogiri.XsltStylesheet$INVOKER$i$1$0$serialize_DBG.call(XsltStylesheet$INVOKER$i$1$0$serialize_DBG.gen)

however, on Java 17 the whole thing bumps into accessibility issues due having to open the internals we're trying to use from the JDK:
Java::JavaLang::IllegalAccessError: superclass access check failed: class nokogiri.internals.XalanDTMManagerPatch (in unnamed module @0x41d20f06) cannot access class com.sun.org.apache.xml.internal.dtm.ref.DTMManagerDefault (in module java.xml) because module java.xml does not export com.sun.org.apache.xml.internal.dtm.ref to unnamed module @0x41d20f06
    java.base/java.lang.ClassLoader.defineClass1(Native Method)
    java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1012)
    java.base/java.security.SecureClassLoader.defineClass(SecureClassLoader.java:150)
    java.base/java.net.URLClassLoader.defineClass(URLClassLoader.java:524)
    java.base/java.net.URLClassLoader$1.run(URLClassLoader.java:427)
    java.base/java.net.URLClassLoader$1.run(URLClassLoader.java:421)
    java.base/java.security.AccessController.doPrivileged(AccessController.java:712)
    java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:420)
    java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:587)
    java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:520)
    nokogiri.XmlXpathContext.<clinit>(XmlXpathContext.java:51)
    nokogiri.XmlXpathContext$INVOKER$s$1$0$rbNew_DBG.call(XmlXpathContext$INVOKER$s$1$0$rbNew_DBG.gen)

all in all the change to the internal xalan would need more work but at the same time I am not sure it's worth the effort, given the reliance on internals, which the JDK does not want us doing (also makes the change a breaking change to existing users - they would need to adjust JRUBY_OPTS flags to get it working).

I just pushed the merged version (rebased onto #2644 which I just merged) but I hear and understand what you're saying about using the internals. We can take this knowledge back to #1829 and continue the conversation about alternatives to Xalan.

Just a reminder: don't delete this branch, it might be useful to refer back to in the future.


Onslaught on kill not recognizing

It seems that there are multiple options to choose from on trade website and this uses the wrong one.
Rarity: Rare
Foe Bane
Vaal Greatsword
--------
Two Handed Sword
Physical Damage: 55-113
Elemental Damage: 58-109 (augmented), 18-35 (augmented)
Critical Strike Chance: 5.00%
Attacks per Second: 1.30
Weapon Range: 13
--------
Requirements:
Level: 68
Str: 122
Dex: 104 (unmet)
--------
Sockets: R-R
--------
Item Level: 86
--------
40% increased Global Accuracy Rating (implicit)
--------
+10 to Dexterity
Adds 58 to 109 Fire Damage
Adds 18 to 35 Cold Damage
+48% to Cold Resistance
25% chance to gain Onslaught for 4 seconds on Kill
Attacks with this Weapon Penetrate 5% Cold Resistance
99% increased Elemental Damage with Attack Skills
--------
Redeemer Item
--------

I understand the developer in saying this should be fixed on GGG's side, but would it be possible to have a SUM group if there's more than one match for a single mod? Ignoring Implicit, crafted, etc.


[Batch] Remove dependency and update live test case

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

[x] I adhere to the Command Guidelines.

Please fix the CI failures.

Codecov Report

Merging #6473 into dev will not change coverage.
The diff coverage is n/a.

@@         Coverage Diff         @@
##           dev   #6473   +/-   ##
===================================
  Coverage    0%      0%
===================================
  Files       11      11
  Lines      133     133
  Branches     9       9
===================================
  Misses     133     133

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 dbe2440...31a53f7. Read the comment docs.

@troydai  @yugangw-msft  Could you sign off my PR?

Thank you.


Pressing down arrow wile typing "Search For" phrase empties current letters

When I'm trying a search phrase and mistakenly hit down arrow, the search phrase is deleted.
The search phrase dropdown is empty on my system.

This is by design, though it should not do this when the list is empty.

It's actually Windows behaviour, and it would need a major effort to program around this. Just don't hit ...

But Fire could ignore the  key in case that list is empty! That's what I am gonna do.

Fixed.


weave --local launch gives error about weaveutil

$ sudo weave --local launch
cp: cannot stat '/usr/bin/weaveutil': No such file or directory

This was on the 1.9 branch
Doesn't seem to stop it working.

I suspect it was/is trying to copy weaveutil to act as CNI plugin.


[Bug] 修改分区参数时没有校验存储介质

Search before asking

[X] I had searched in the issues and found no similar issues.

Version
f227472db2d8ec207efac2fc144b08a969acb98f
What's Wrong?
没有配置SSD存储介质，建表的时候设置存储介质为SSD会报错
mysql> create table test_storage (k1 BIGINT,k2 DATE,v1 varchar(20)) UNIQUE KEY(k1,k2) partition by RANGE(k2) ( partition
    -> p1 values less than ('2022-03-01')) DISTRIBUTED BY HASH(k1) BUCKETS 4 PROPERTIES("replication_allocation" = "tag.location.default: 1","storage_medium" = "SSD", "storage_cooldown_time" = "2022-06-04 00:00:00")
    -> ;
ERROR 1105 (HY000): errCode = 2, detailMessage = Failed to find enough host with storage medium and tag(SSD/{"location" : "default"}) in all backends. need: 1

mysql>  create table test_storage (k1 BIGINT,k2 DATE,v1 varchar(20)) UNIQUE KEY(k1,k2) partition by RANGE(k2) ( partition
    -> p1 values less than ('2022-03-01')) DISTRIBUTED BY HASH(k1) BUCKETS 4 PROPERTIES("replication_allocation" = "tag.location.default: 1","storage_medium" = "HDD");
Query OK, 0 rows affected (0.02 sec)

mysql> alter table test_storage MODIFY PARTITION (p1) SET("storage_medium" = "SSD", "storage_cooldown_time" = "2022-06-04 00:00:00");
Query OK, 0 rows affected (0.00 sec)

但是修改分区的时候没有报错，成功改为SSD，通过这种方式，绕过了建表时的校验
What You Expected?
修改或添加分区时是不是也应该进行和建表时同样的校验
How to Reproduce?
No response
Anything Else?
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

Actually this is not a bug.
Because when creating table, Doris will do the real "create tablet" task on BE, so that it MUST find enough backends with
specified storage medium.
But when doing alter table, it just modify the metadata in FE, so it will not check the storage medium on BE.
You can treat this storage medium property as a "hint".


Initial zone and contract offerer failures

Motivation

Solution

Codecov Report
Patch and project coverage have no change.

Comparison is base (c73a10f) 100.00% compared to head (42071e7) 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@             Coverage Diff             @@
##               1.5     #1149     +/-   ##
===========================================
  Coverage   100.00%   100.00%
===========================================
  Files           46        25     -21
  Lines         2652      1184   -1468
  Branches       396       134    -262
===========================================
- Hits          2652      1184   -1468

Flag
Coverage Δ

foundry
?

production
100.00% <ø> (ø)

reference
?

Flags with carried forward coverage won't be shown. Click here to find out more.
see 40 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

This one's mostly already in but has fallen kind of far out of sync with what's already merged in given all the changes related to scoping by order hash and such, it's really just the change to provide a full ReceivedItem instead of an amount that's not currently included; let's open a new PR with that change when the time comes


btcpayserver: 1.3.7 -> 1.4.2

Things done:

Tested with the nix-bitcoin VM test.

Notes for reviewers: You can verify GPG signatures with refetch=1 pkgs/applications/blockchains/btcpayserver/update.sh.
cc @prusnak @erikarvstedt

@GrahamcOfBorg build btcpayserver nbxplorer

@GrahamcOfBorg build btcpayserver nbxplorer

The VM test fails for the initial version and for the latest fixup: The btcpayserver service exits (with statuc 0) right after starting.
Manual repro inside a nix-bitcoin system:
runuser -u btcpayserver -- /nix/store/dngc8vx42wq1qi7y002ifxz026cvx7n7-btcpayserver-1.4.2/bin/btcpayserver --conf='/var/lib/btcpayserver/settings.config' --datadir='/var/lib/btcpayserver'
## Output
info: Configuration:  Data Directory: /var/lib/btcpayserver
info: Configuration:  Configuration File: /var/lib/btcpayserver/settings.config
info: Configuration:  Network: Mainnet
info: BTCPayServer.Plugins.PluginManager: Loading plugins from /var/lib/btcpayserver/.btcpayserver/Plugins
info: BTCPayServer.Plugins.PluginManager: Adding and executing plugin BTCPayServer - <IP_ADDRESS>
info: BTCPayServer.Plugins.PluginManager: Adding and executing plugin BTCPayServer.Plugins.Shopify - <IP_ADDRESS>
# Exit with status 0 here

Removing line chains=btc,lbtc from the btcpayserver config file fixes the service.
So lbct (liquid) support is broken in v1.4.2. I'd wait with the upgrade until this is fixed.

Removing line chains=btc,lbtc from the btcpayserver config file fixes the service. So lbct (liquid) support is broken in v1.4.2. I'd wait with the upgrade until this is fixed.

Yeah, I've been troubleshooting that too. Have you found the issue upstream?

I've filed a bug report.

BTCPayServer doesn't build altcoins support by default, so you need to build with -C Altcoins-Release, not -C Release. I will make a commit to make the error more user friendly though.

Will make new version today or tomorrow sweeping a few bugs, included the fact you didn't see error message.

@NicolasDorier, thanks for looking into this. The actual bug was in @nixbitcoin's VM test script which didn't properly set Altcoins-Release, but this in turn uncovered the log printing bug in btcpayserver.

@NicolasDorier, altcoin support is disabled by default in nixpkgs. In nix-bitcoin, it's only enabled when liquid (lbtc) support is required.

Fixup.
This makes the VM test succeed.
@nixbitcoin, please always run the test before pushing.

Yes, I will be careful about that in the future. I have updated the original VM test link and it now runs smoothly.

I bumped to 1.4.4 which at least fix the issue of not seeing proper error message if configuration isn't good.


Added $message to VerifyCsrfToken.php

Adding $message for making it customisable.

Maybe using translator would be better here, since it would allow translation.
To react @GrahamCampbell comment on #32928:

Also, I would consider it a bad practice to translate exception messages. Instead, translate them in the presentation layer.

I agree with this point of view unless the exception is directly used to display the error message on the frontend.


Add Youngs-Experiment-Calculator

Fixes Issue🛠
Closes #1690
Description👨💻
Implemented a calculator for Young's modulus and fringe spacing formulas. This calculator allows users to compute:

Position of Bright Fringe (ym): Calculates the position of the bright fringe based on provided parameters.
Position of Dark Fringe (ym): Computes the position of the dark fringe in the experiment.
Fringe Spacing: Determines the spacing between fringes using the relevant formula.

The tool provides a user-friendly interface for inputting values and displaying results..
Type of Change📄

[x] New feature (non-breaking change which adds functionality)

Checklist✅

[x] I am an Open Source contributor
[x] I have performed a self-review of my code
[x] My code follows the style guidelines of this project

Screenshots/GIF📷

@Rakesh9100  please check this pr

@Rakesh9100 please check this pr

@Rakesh9100 This PR is reviewed and can be merged.

@Rakesh9100 please check this pr


Error on cloning sales order details on invoiced orders

I created a workflow that clones an order and its related lines. It works great, except for invoiced orders. When I try to clone an invoiced order with products, I get error "The detail cannot be updated because the parent is not editable.". If I clone an invoiced order with no products or an active/submitted order, I get no error and the clone completes successfully.

I tried ignoring all fields (both on header and lines) that have to do with status or state in order to prevent the new order from being "locked" but no luck.
OS: Windows
Browser: Edge
CRM Version: Online
WorkflowTools version: <IP_ADDRESS>

We found that the core issue was that the CloneChildren step was first duplicating the record, then updating with a new parent record. This threw the error as it was attempting to add new lines to a closed record.
The new update sets the new parent record (and clears the previous parent if applicable) in the clone itself, not afterwards.

Hi - is there any update as to when the fix for this issue with cloning records with closed parent will be released?  It will be super handy to be able to clone a completed order's associated order lines (and not just the completed order).

@kavila02 may I ask how did you compose the Target Record URL?


Refreshing useObservable upon deps change

I have enhanced our legend v2 with refreshing computing upon deps change.
First I followed your implementation in v3, but had some infinite loop problems so I adapted it.
Maybe v3 works differenly inside, but I cannot integrate v3-alpha in it's current into our full app.
These are the differences:

The update happens in useEffect. Generally it is working good like this with React, instead of doing set in render
The update itself is with simple value instead of storing array in observable
It does not relly on legend object diffing
It does deps comparison same as it is used in React code

Our code:
export const areDepsEqual = (a: DependencyList, b: DependencyList) => {
    if (a.length !== b.length) {
        console.warn('useRecoilMemoSelector deps length changed between renders')
        return false
    }
    for (let i = 0; i < a.length; i++) {
        if (!Object.is(a[i], b[i])) {
            return false
        }
    }
    return true
}

export function useComputed(compute: any, deps: any, set?: any) {
    const depsTrigger$ = useObservable(0)

    const depsRef = useRef(deps)
    let ret = legendUseComputed(() => {
        depsTrigger$.get()
        return compute()
    }, set)
    useEffect(() => {
        if (!areDepsEqual(deps, depsRef.current)) {
            depsRef.current = deps
            depsTrigger$.set((c) => c + 1)
        }
    }, [deps, depsTrigger$])

    return ret
}

Current v3 code:
export function useObservable<T>(
    initialValue?: T | (() => T) | (() => Promise<T>),
    deps?: DependencyList,
): Observable<T> {
    // Create a ref to contain the observable and initialValue function
    const ref = useRef<{ obs$: Observable<T>; value: T }>({} as any);
    ref.current.value = initialValue as T;

    // Create a deps observable to be watched by the created observable
    const depsObs$ = deps ? useObservable(deps) : undefined;
    if (!ref.current?.obs$) {
        // Create the observable from the default value. If the selector function is a lookup table
        // then it needs to be a function taking a string to pass it through.
        const value = depsObs$
            ? isFunction(initialValue) && initialValue.length === 1
                ? (p: string) => {
                      depsObs$.get();
                      return (ref.current.value as (p: string) => any)(p);
                  }
                : () => {
                      depsObs$.get();
                      return computeSelector(ref.current.value);
                  }
            : initialValue;

        ref.current.obs$ = observable<T>(value as T);
    }
    // Update depsObs with the deps array
    if (depsObs$) {
        depsObs$.set(deps! as any[]);
    }

    return ref.current.obs$;
}

That looks like it should work fine. It should work basically the same, except that it may cause multiple renders because of the useEffect:

It re-renders with a dependency change
After render it runs the effect and triggers the observable re-compute
Observable re-compute triggers its own re-render

That should not cause huge problems though, and should be a fine workaround for now.
Why is it that you can't upgrade to v3? Is it just because it's alpha or is there a problem with it?

Why is it that you can't upgrade to v3

Currently these are the blockers:

#314 feature
Update the above refresh mechanism
#305 bug

I still get the infinite error even from my refresh rewrite.
So this mechanism should be optional.
This happens when doing
		let index = plugin$.data.peek().findIndex((instance) => byondId === instance.byondId)
		index > -1 && plugin$.data.splice(index, 1)

But I suspect it causes more problems.


Change detected and watching works but nothing is changing.

I am having an issue with my Watch Sass is on and saving shows "Change Detected" but nothing is actually happening.
I thought my json was configured properly as it came from a coworker who doesn't have issues. But it's still not generating the updated file.
The code below is what is in my json file.
{
    "liveSassCompile.settings.formats": [
      {
        "format": "compressed",
        "extensionName": ".css",
        "savePath": null
      }
    ],
    "liveSassCompile.settings.generateMap": false,
    "liveSassCompile.settings.includeItems": [
      "**/wordpress/wp-content/themes/familylife-theme/assets/css/front-styles.scss",
      "**/wordpress/wp-content/themes/familylife-theme/assets/css/**",
    ],
    "liveSassCompile.settings.excludeList": [
      "**/node_modules/**",
      ".vscode/**",
      "**/wordpress/wp-content/themes/familylife-theme/assets/css/additional-styles/**",
      "**/wordpress/wp-content/themes/familylife-theme/assets/css/front-styles-rtl.scss"
    ],
    "liveSassCompile.settings.generateMap": false,
    "git.confirmSync": false,
    "explorer.confirmDelete": false,
    "launch": {
      "configurations": [],
      "compounds": []
    },
    "workbench.colorCustomizations": {},
    "window.zoomLevel": 2,
  }

I'd need to see the log output please.

Unrelated: you have the generateMap in there twice

if you set the showOutputWindowOn setting to trace it can help find out if there's an issue
My initial thoughts are the file you're saving is excluded or there's an error being thrown

Glenn, thanks for replying. I am a n0ob when it comes to json and navigating this based on what a contractor sent me. I am not 100% sure if how he is set up that it should be the same for me. Not sure if it makes a difference but I am on a Mac and he was working on a PC. I don't want to assume the code should work as-is from the other dev.
He also told me that it took him a bit to get to where the json file was working in the way that he needed. I.e. making edits to files within the wordpress theme and the changes generating the updated font-styles.scss/.css file after saving out the new .scss file within the folder structure.
My understanding of the json updates are basic, I currently have the following code in place:
{   "showOutputWindowOn":"trace",   "liveSassCompile.settings.formats": [     {       "format": "compressed",       "extensionName": ".css",       "savePath": null     }   ],   "liveSassCompile.settings.generateMap": false,   "liveSassCompile.settings.includeItems": [     "/**/wordpress/wp-content/themes/familylife-theme/assets/css/front-styles.scss",     "/**/wordpress/wp-content/themes/familylife-theme/assets/css/**"   ],   "liveSassCompile.settings.excludeList": [     "/**/node_modules/**",     "/.vscode/**",     "/**/wordpress/wp-content/themes/familylife-theme/assets/css/additional-styles/**",     "/**/wordpress/wp-content/themes/familylife-theme/assets/css/front-styles-rtl.scss"   ],   "git.confirmSync": false,   "explorer.confirmDelete": false,   "launch": {     "configurations": [],     "compounds": []   },   "workbench.colorCustomizations": {},   "window.zoomLevel": 2, }
I am getting an error Must start with a path separator (/ or \) and end with a .sass or .scss on the line:     "//wordpress/wp-content/themes/familylife-theme/assets/css/"
When I save my .scss with Watch SASS activated I see the Watching... and Success green change on Save. But I am not seeing my newly generated front-styles change or affected, which I presume to be what should happen.
And maybe I am completely off, but otherwise, I am unsure of how to proceed and if I am asking the right questions and have the correct set up for what needs done.
I appreciate any and all direction as this is all new to me and the method of updating is forcing me to ponder life through an existential crisis.

Sorry for the delay. Glad to help where I can.

I currently have the following code in place:
{
  "showOutputWindowOn":"trace",

Sorry, I should have been more specific. This line should read "liveSassCompile.settings.showOutputWindowOn":"trace",. This will produce more output that should help identify the issue.

I am getting an error Must start with a path separator (/ or \) and end with a .sass or .scss on the line: /**/wordpress/wp-content/themes/familylife-theme/assets/css/**

As the warning says, you need to end with .scss. To remove the warning you need to put /*.scss on the end.

When I save my .scss with Watch SASS activated I see the Watching... and Success green change on Save. But I am not seeing my newly generated front-styles change or affected, which I presume to be what should happen.

The success message means the compiler has done its job. Try deleting the existing CSS file you're expecting it to update and resave the SCSS file. If the CSS file is created, the compiler is working and the issue must be with the SCSS changes not producing your desired output. If the fire isn't created where you expect the output from the new setting will give more details on where it's trying to save to.
Another thing that may be causing an issue is if they're actually shadow files on your Mac

If you can't get to the bottom of it. Paste the extended output in a new comment here (pop it in triple ``` to format it correctly for me, thanks 😁)

Closing as info required