Deprecated help-text-top-to-workflow-icon-* tokens

Description

Updated help-text-top-to-workflow-icon-* token values to point to component-top-to-workflow-icon-* tokens
Marked help-text-top-to-workflow-icon-* tokens for deprecation

Motivation and context

Due to design updates for the Spectrum 2 help text component, these help-text-top-to-workflow-icon-* component-specific tokens are no longer required since they can use the global aliases instead

Related issue

Types of changes

[ ] Patch (bug fixes, typos, mistakes; non-breaking change which fixes an issue)
[x] Minor (add a new token, changing a value; non-breaking change which adds functionality)
[ ] Major (deleting a token, changing token value type; fix or feature that would cause existing functionality to change)

Checklist:

[x] I have signed the Adobe Open Source CLA.
[x] I updated the token in all applicable sets. This applies if updating, adding, or deleting a token that has data across different sets (for example, if the value differs across color themes.)

TESTING spectrum2-non-colors
READING spectrum-tokens: /spectrum-tokens/packages/tokens/src/
READING   tokens studio: /spectrum-tokens-studio-data/src/tokens-studio/spectrum2-non-colors/
TOKENS STUDIO DATA IS NON-COLOR ONLY
SPECTRUM SYNC SUMMARY
DEPRECATED TOKENS: (8) help-text-top-to-workflow-icon-small/desktop, help-text-top-to-workflow-icon-small/mobile, help-text-top-to-workflow-icon-medium/desktop, help-text-top-to-workflow-icon-medium/mobile, help-text-top-to-workflow-icon-large/desktop, help-text-top-to-workflow-icon-large/mobile, help-text-top-to-workflow-icon-extra-large/desktop, help-text-top-to-workflow-icon-extra-large/mobile
CHANGED VALUES: (8) help-text-top-to-workflow-icon-extra-large/desktop, help-text-top-to-workflow-icon-large/desktop, help-text-top-to-workflow-icon-medium/desktop, help-text-top-to-workflow-icon-small/desktop, help-text-top-to-workflow-icon-extra-large/mobile, help-text-top-to-workflow-icon-large/mobile, help-text-top-to-workflow-icon-medium/mobile, help-text-top-to-workflow-icon-small/mobile impacting 4 tokens
CHANGED SCHEMAS: (4) help-text-top-to-workflow-icon-extra-large, help-text-top-to-workflow-icon-large, help-text-top-to-workflow-icon-medium, help-text-top-to-workflow-icon-small

TEST COMPLETE

@GarthDB I wanted to double-check with you on the type of change. Since the tokens have just been marked for deprecation and have not yet been deleted, I believe this is a minor change. Could you help confirm if that's correct? Thank you!

@lynnhao, correct, it's just adding new tokens.

SYNCING spectrum2-non-colors
READING spectrum-tokens: /spectrum-tokens/packages/tokens/src/
READING   tokens studio: /spectrum-tokens-studio-data/src/tokens-studio/spectrum2-non-colors/
TOKENS STUDIO DATA IS NON-COLOR ONLY
SPECTRUM SYNC SUMMARY
DEPRECATED TOKENS: (8) help-text-top-to-workflow-icon-small/desktop, help-text-top-to-workflow-icon-small/mobile, help-text-top-to-workflow-icon-medium/desktop, help-text-top-to-workflow-icon-medium/mobile, help-text-top-to-workflow-icon-large/desktop, help-text-top-to-workflow-icon-large/mobile, help-text-top-to-workflow-icon-extra-large/desktop, help-text-top-to-workflow-icon-extra-large/mobile
CHANGED VALUES: (8) help-text-top-to-workflow-icon-extra-large/desktop, help-text-top-to-workflow-icon-large/desktop, help-text-top-to-workflow-icon-medium/desktop, help-text-top-to-workflow-icon-small/desktop, help-text-top-to-workflow-icon-extra-large/mobile, help-text-top-to-workflow-icon-large/mobile, help-text-top-to-workflow-icon-medium/mobile, help-text-top-to-workflow-icon-small/mobile impacting 4 tokens
CHANGED SCHEMAS: (4) help-text-top-to-workflow-icon-extra-large, help-text-top-to-workflow-icon-large, help-text-top-to-workflow-icon-medium, help-text-top-to-workflow-icon-small

WROTE: /spectrum-tokens/packages/tokens/src/layout-component.json
SYNC COMPLETE
Spectrum Tokens Pull Request


Can the component prevent repeated submission？

Can the component prevent repeated submission？

You could hook into the onFormComplete event and remove the form or block the submission.
You can see here that there is an event for knowing when everything is done. So you could maybe set a boolean for theFormHasBeenSubmitted when this even is fired. Then, at this event check to see if the form has already been submitted or not.
There are probably server-side ways to do this, but that is very subjective.


TypeError: remap is not a function

Note: for support questions, please use one of these channels: Chat: AngularClass.slack or Twitter: @AngularClass

I'm submitting a ...
[x] bug report
[ ] feature request
[ ] question about the decisions made in the repository

Do you want to request a feature or report a bug?

bug

What is the current behavior?

The following error shows up in the terminal after running the unit tests:
ERROR [coverage]: TypeError: remap is not a function
    at onCoverageComplete (/Users/mattbanz/Desktop/angular2-webpack-starter/node_modules/karma-remap-coverage/remap-coverage.js:23:23)
    at .<anonymous> (/Users/mattbanz/Desktop/angular2-webpack-starter/node_modules/karma/lib/events.js:13:22)
    at emitTwo (events.js:106:13)
    at emit (events.js:191:7)
    at InMemoryReport.writeReport (/Users/mattbanz/Desktop/angular2-webpack-starter/node_modules/karma-coverage/lib/in-memory-report.js:14:22)
    at writeReport (/Users/mattbanz/Desktop/angular2-webpack-starter/node_modules/karma-coverage/lib/reporter.js:68:16)
    at /Users/mattbanz/Desktop/angular2-webpack-starter/node_modules/karma-coverage/lib/reporter.js:290:11
    at Array.forEach (native)
    at forEach (/Users/mattbanz/Desktop/angular2-webpack-starter/node_modules/karma/lib/browser_collection.js:93:21)
    at /Users/mattbanz/Desktop/angular2-webpack-starter/node_modules/karma-coverage/lib/reporter.js:247:16
    at Array.forEach (native)
    at onRunComplete (/Users/mattbanz/Desktop/angular2-webpack-starter/node_modules/karma-coverage/lib/reporter.js:246:15)
    at .<anonymous> (/Users/mattbanz/Desktop/angular2-webpack-starter/node_modules/karma/lib/events.js:13:22)
    at emitTwo (events.js:111:20)
    at emit (events.js:191:7)
    at emitRunCompleteIfAllBrowsersDone (/Users/mattbanz/Desktop/angular2-webpack-starter/node_modules/karma/lib/server.js:294:12)

If the current behavior is a bug, please provide the steps to reproduce

clone the repo
npm install
npm test

What is the expected behavior?

No error in the terminal

What is the motivation / use case for changing the behavior?

Errors are bad and ugly

Please tell us about your environment:

Angular 2.2.1
no browser, just run the tests in the terminal

It seems that it's a problem with the library karma-remap-coverage : https://github.com/sshev/karma-remap-coverage/issues/12
You have to force the remap-istanbul library version to 0.8.1 (maybe 0.8.0) in your package.json as a workaround :
$ npm run install --save-dev<EMAIL_ADDRESS>

@vtabary Thanks for your reply! I got it working with 0.8.0. I got a different error with 0.8.1.

@vtabary Just worked for me too with 0.81. Thank you so much!

I did a npm install remap-istanbul
which installed @0.8.4 and all worked without errors for 'npm run test'

Should work with current master now.

Should work with current master now.


[Documentation] Multiple device types per enpoint?

Documentation issues
I'm creating an Matter Accessory Device with multiple sensors like:

Air Temperature
Barometric Pressure
Illumination
Relative Humidity
CO2 Level

In the Simplicity Studio ZAP-editor, I used to be able to add several device types to an endpoint

But, in the latest version the ZAP-editor complains about this not being allowed:

I'm also very confused about the terminology used in this dialog.
What is a "Simple endpoint" and what other  endpoint type are there?
In the dialog there is also a "Profile ID". I have tried to dig into the Matter 1.2 specs to understand what it is, but have found almost zero documentation on the topis.
I think the documentation /  specs needs to be improved in this area.
Platform
efr32
Anything else?
No response

As an initial point, Zap lets you do a lot of stuff that doesn't strictly conform with the Matter specs  (at least it didn't in earlier versions - I haven't checked lately). So Zap permitting it doesn't make it conforming.
I believe what should be done to conform to Matter is covered in the Matter documents (but I can't find it at the moment).  My recollection is that you can add multiple "types" to an endpoint, but it is only "correct" if the Primary Device is a superset of all of the others. In other words, the Primary must have all the clusters of the secondary types. This would be pretty rare. An example that comes to mind is for Color Dimmer Switch, Dimmer Switch, and On/Off Switch.  If Color Dimmer Switch is the Primary, you can put "Dimmer Switch" or "On/Off Switch" as secondary. This is allowed since Color Dimmer Switch contains all the clusters of Dimmer Switch and On/Off Switch.   Similarly, if you put "Dimmer Switch" as Primary, then "On/Off Switch" is permitted as the secondary since Dimmer contains all its clusters, but Color Dimmer Switch would not since Dimmer is missing the color control cluster.
I also believe a strict interpretation of the spec would say that if a specific device type does not specifically say a cluster is optional, then it should not be added for that type. So, in your case, the Matter Temp. sensor 0x0302 device type does not say that light, pressure, humidity clusters are optional within that type, so they are not optional. Indeed, if you could add whatever you want to a defined device type, then "optional" loses all meaning. I note that  Matter does allow you to define your own device type with an "anything goes" mix of clusters, but the same isn't (or IMO should be) true if you use a defined type.
So if I were you, I'd suggest you use a discrete endpoint for each sensor type as that conforms to a strict reading of the Matter standard and gives a clearer layout of exactly what the node is doing.  At least this is my reading of the standards.


Benchmark API Improvements

This PR updates parts of the benchmark harness to match the API guidelines closer. That includes using a String enum for BenchmarkCategories and renaming BenchmarkCategories to BenchmarkCategory (since it is an enum that represents a single benchmark category after all).

@atrick @shajrawi What do you guys think? While doing the initFunction change I noticed this.

👍 Obvious goodness. You also mentioned moving the runFunction to the end of the initializer.

@swift-ci smoke test

@swift-ci smoke test


support user configured cloud provider for Tencent

What does this PR do?
Support user configured cloud provider for Tencent, see  #4930.
Motivation
After #4554 and #4930 are merged, now support user configured cloud provider.

Hello @oiooj,
Thanks for the follow-up PR. It should be merged by the next release (7.20).


Single Select

Description
Don't be afraid! Most of the diff lines are package-lock.json and boilerplate. This PR adds the nested single select into this package. I have not updated the README, incorporated CodeCov or added a test workflow yet, these will happen once the multiselect is added but to see demo run:
npm i
npm run dev

Feel free to change the data in the App.vue file to test out the different cases.
To test run:
npm run test

This project uses vite.
Guide
My general approach was to use an existing dropdown component and modify it so we can have nested options. The way this works is we first flattenOptions which will convert
[{
  id: "id1",
  label: "label1",
  children: {
    id: "id1_1",
    label: "label1_1"
  }
}]

into
[
  {
    id: "id1",
    label: "label1",
    hasChildren: true,
    open: false,
    show: true,
    path: "/id1"
  },
  {
    id: "id1_1",
    label: "label1_1",
    hasChildren: false,
    show: false,
    path: "/id1/id1_1"
  }
]

The path keeps track of the directory like structure so we can find if something is a child of another by comparing strings. The show will control what options are shown in the menu so when we expand a collapsible item, all the shows of the children will flip to true. The collapse will scan for any path with the same prefix as the item being collapsed and collapse those.

Are you going to add a gha to run the tests and coverage?

Yes I will be adding these once single select and multiselect components are done, i think these things are better once theres a decent base!


Go packages with capitals in the user/repo name cause issues with mise upgrade

Describe the bug
Installing Go packages that canonically have capitals in the user/repo name cause issues with mise upgrade
To Reproduce
[tools]
"go:github.com/Crosse/sshsrv" = "master"

The install goes OK:
$ mise list | grep sshsrv
go:github.com/Crosse/sshsrv           master (missing)  ~/.config/mise/config.toml  master

$ mise install
mise go:github.com/Crosse/sshsrv@master ✓ installed

$ which sshsrv
/Users/josh/.local/share/mise/installs/go-github-com-crosse-sshsrv/master/bin/sshsrv

$ sshsrv
Usage: check the ssh man page.

(possible issue: the install name is lower-cased)
Now, when using mise upgrade:
$ mise cache clear
mise cache cleared

$ mise upgrade
go: invalid github.com import path "github.com/Crosse"
go: invalid github.com import path "github.com"
mise WARN  No versions found for go:github.com/Crosse/sshsrv
mise All tools are up to date

I've also tried to lower-case the user name (e.g. Crosse to crosse):
[tools]
"go:github.com/crosse/sshsrv" = "master"

but Go doesn't love that:
$ mise install
go: github.com/crosse/sshsrv@master: version constraints conflict:
<EMAIL_ADDRESS>parsing go.mod:
        module declares its path as: github.com/Crosse/sshsrv
                but was required as: github.com/crosse/sshsrv
mise ERROR go failed
go: github.com/crosse/sshsrv@master: version constraints conflict:
<EMAIL_ADDRESS>parsing go.mod:
        module declares its path as: github.com/Crosse/sshsrv
                but was required as: github.com/crosse/sshsrv
mise ERROR failed to install go:github.com/crosse/sshsrv@master
mise ERROR go exited with non-zero status: exit code 1
mise ERROR Run with --verbose or MISE_VERBOSE=1 for more information

Expected behavior
mise upgrade shouldn't complain.
mise doctor output
mise doctor
version: 2024.12.10 macos-arm64 (2024-12-14)
activated: yes
shims_on_path: no

build_info:
  Target: aarch64-apple-darwin
  Features: DEFAULT, NATIVE_TLS
  Built: Sat, 14 Dec 2024 18:40:19 +0000
  Rust Version: rustc 1.83.0 (90b35a623 2024-11-26) (Homebrew)
  Profile: release

shell:
  /bin/zsh
  zsh 5.9 (arm64-apple-darwin24.0)

dirs:
  cache: ~/.cache/mise
  config: ~/.config/mise
  data: ~/.local/share/mise
  shims: ~/.local/share/mise/shims
  state: ~/.local/state/mise

config_files:
  ~/.config/mise/config.toml

backends:
  aqua
  asdf
  cargo
  core
  gem
  go
  npm
  pipx
  spm
  ubi
  vfox

plugins:
  jq          https://github.com/mise-plugins/asdf-jq.git#6d86d19
  poetry      https://github.com/mise-plugins/mise-poetry.git#431c335
  shellcheck  https://github.com/luizm/asdf-shellcheck.git#780d78d
  shfmt       https://github.com/luizm/asdf-shfmt.git#a42c5ff
  sops        https://github.com/mise-plugins/mise-sops#cfa3ab5
  tiny        https://github.com/mise-plugins/mise-tiny.git#c532b14
  usage       https://github.com/jdx/mise-usage.git#fe3888a

toolset:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>  cargo:rydesun/fennel-language-server@HEAD
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>  go:github.com/Crosse/sshsrv@master
<EMAIL_ADDRESS>  go:github.com/kitagry/bqls@main
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
path:
  ~/.local/share/mise/installs/bun/1.1.38/bin
  ~/.local/share/mise/installs/node/23.4.0/bin
  ~/.local/share/mise/installs/poetry/1.8.5/bin
  ~/.local/share/mise/installs/python/3.12.8/bin
  ~/.local/share/mise/installs/sops/3.9.2/bin
  ~/.local/share/mise/installs/pipx-tuna/0.5.11/bin
  ~/.local/share/mise/installs/cargo-lockdiff/1.1.7/bin
  ~/.local/share/mise/installs/cargo-pylyzer/0.0.73/bin
  ~/.local/share/mise/installs/cargo-rydesun-fennel-language-server/HEAD/bin
  ~/.local/share/mise/installs/cargo-tinty/0.23.0/bin
  ~/.local/share/mise/installs/npm-fast-cli/4.0.0/bin
  ~/.local/share/mise/installs/npm-gha-check-updates/1.0.8/bin
  ~/.local/share/mise/installs/npm-sql-language-server/1.7.1/bin
  ~/.local/share/mise/installs/npm-tslab/1.0.22/bin
  ~/.local/share/mise/installs/npm-tsx/4.19.2/bin
  ~/.local/share/mise/installs/go-github-com-aykamko-tag/1.4.0/bin
  ~/.local/share/mise/installs/go-github-com-kitagry-bqls/main/bin
  ~/.local/share/mise/installs/go-github-com-crosse-sshsrv/master/bin
  ~/.local/share/cargo/bin
  ~/.local/share/go/bin
  ~/.local/share/pipx/bin
  ~/.local/bin
  ~/.local/state/nix/profile/bin
  ~/.local/state/nix/profile/sbin
  /nix/var/nix/profiles/default/bin
  /opt/homebrew/bin
  /opt/homebrew/sbin
  /usr/local/bin
  /usr/bin
  /usr/sbin
  /bin
  /sbin
  /System/Cryptexes/App/usr/bin
  /Library/Apple/usr/bin

env_vars:
  MISE_SHELL=zsh

settings:
  disable_hints           ["outdated_bump"]     ~/.config/mise/config.toml
  experimental            true                  ~/.config/mise/config.toml
  jobs                    8                     ~/.config/mise/config.toml
  legacy_version_file     false                 ~/.config/mise/config.toml
  not_found_auto_install  false                 ~/.config/mise/config.toml
  pipx.uvx                true                  ~/.config/mise/config.toml
  python_compile          true                  ~/.config/mise/config.toml
  status.show_env         false                 ~/.config/mise/config.toml
  status.show_tools       false                 ~/.config/mise/config.toml
  trusted_config_paths    ["~/repos/checkmate"] ~/.config/mise/config.toml
mise WARN  mise version 2024.12.11 available

1 problem found:

1. new mise version 2024.12.11 available, currently on 2024.12.10

I don't think it's the capital, I think mise up doesn't handle versions that don't change like that

looking at this again, versions that don't change like that just aren't going to work in mise up

yep - I see what's going on - not sure why no Versions is returned by go list, even though there is a v1.0 tag in the repo...
$ go list -m -versions -json github.com/Crosse/sshsrv
{
        "Path": "github.com/Crosse/sshsrv"
}

here's one that works:
$ go list -m -versions -json github.com/kitagry/bqls
{
        "Path": "github.com/kitagry/bqls",
        "Versions": [
                "v0.0.3",
                "v0.1.0",
                "v0.2.0",
                "v0.2.1",
                "v0.2.2"
        ]
}

Oh, it's probably because it's only v1.0 rather than v1.0.0 - I'll let the repo owner know :)

OK - adding an actual semantic version resolved the issue


Allow to configure the attribute that works as "class" attribute in the xml mapping

When mapping xml to standoff, the same xml-tag can be mapped to different standoff classes by using the "class" attribute. This seems a bit limited, since the "class" attribute is a html attribute and not available, for example, in TEI. So it is not possible to map a tei-tag to more than one standoff-class in a tei-conformant way. I would like to do this to have some tags reference a resource in knora via standoffLinkTag, and others not. E.g. some pb-Tags are linked to a kwa:Page resource, others are not.
An easy way to improve on this would be to allow to define the "classifiing attribute" in the mapping. For tei, e.g., the globally available "type" attribute could be used.
Also note that the class attribute in html can have more than one value (which would not work in knora atm.).

ping @tobiasschweizer

When mapping xml to standoff, the same xml-tag can be mapped to different standoff classes by using the "class" attribute. This seems a bit limited, since the "class" attribute is a html attribute and not available, for example, in TEI.

That's true since we rather had HTML in mind than XML.
At the moment, we are exploring the possibility of connecting eXist-db to Knora so that TEI-XML files could be uploaded to an instance of eXist-db (see DSP-task).
Depending on the outcome of this, there is a chance that we are not going to store edited texts in Knora in the future and that the mapping (XML to standoff and vice-versa) would not be necessary anymore.
I think that the current implementation of the mapping is sufficient for simple use cases, i.d. annotations with some formatting etc. but cannot meet the requirements of critical editions such as yours.
There is also a good chance that the client could handle standoff conversions for annotations with a simple mapping mechanism (Knora would not have to do the conversion from and to XML).
Could we maybe present our ideas about how to connect with eXist-db to you to see if this would work for the Walser-edition?


Fishing using ifps one more case...

Hello,
i paste the link receive this day:
<EMAIL_ADDRESS>and a screen capture:

and a screen capture of the mail  involved in this tentative :+1:

Please make something to secure use of your software...

Does this even having anything to do with the core development of IPFS? 😒

If your software allow to make bad things , YES it's an issue for you...

If your software allow to make bad things

So basically everything on the internet. This boils down to you being mad you got phised and your email used to spam...may as well complain about HTML or any other webhost having clone pages too, and you complained on their dev page instead of flagging the page in the application, thinking something would be done about it...

First i'm not complaining on everythings. Just i notice your software is used to make attempts of phishing.
After i'm not trying to make you trouble. Just when you develop something, you need to anticipate bad uses. If not there's a problemif ethic and of efficency. I try to undersand what is ipfs... And it seems to be an alternative infrastructure  to the web. Sale goals, same issues, each system need regulation. And in my mind it's in the core project...

Please see: https://github.com/ipfs/community/blob/master/SECURITY.md#reporting-abuse


[ISSUE-5705] Support for degraded health

Motivation:
Add support for degraded health.
Modifications:

Add HealthStatus enum which can represent the health status of a server
Add healthStatus() method in HealthChecker for fine-grained representation of server's status
Add degradedResponse which shows that the server's status is being degraded.

I think adding new health check service which returns HealthStatus(instead of boolean) might be an alternate option. But because this PR is before any reviews, I've just implemented feature on top of HealthCheckService.
Result:
Users can now receive notification for degraded server status like below
{"healthy":true, "degraded":true}

Closes https://github.com/line/armeria/issues/5705. (If this resolves the issue.)
Users can now identify degraded server status in addtion to healthy and unhealthy.

Removed the [ISSUE-5741] prefix in the commit messages.

Question) what do you think of just combining the two HealthCheckUpdateHandler and adding similar logic as HealthCheckService?

Looks better. I don't think we need to split them into different classes. 👍


Linting Error: angular is not define. export namspace angular

am using angular in vscode editor, but am having errors saying: "angular is not define, export  namespace angular" please anyone with an idea on this?

Hello, we reviewed this issue and determined that it doesn't fall into the bug report or feature request category. This issue tracker is not suitable for support requests, please repost your issue on StackOverflow using tag angular-cli.
If you are wondering why we don't resolve support issues via the issue tracker, please check out this explanation.


Create API Endpoint for Project CRUDL

Create a json-api conforming endpoint for creating/updating/reading/deleting/listing work items.
Depends on #509

Create a json-api conforming endpoint for creating/updating/reading/deleting/listing work items.

You mean "projects" instead of "work items" right? Or do you want to have an endpoint like /project/:name/workitems that lets you define work items which belong to the project?
Please share your ideas on the the concrete endpoint URL.

Is this issue referring to something like:
Org Name/Project Name/Area Name/Area Name/Work Item Name ?
-Monica
On Wed, Nov 30, 2016 at 7:33 AM, Konrad Kleine<EMAIL_ADDRESS>wrote:

Create a json-api conforming endpoint for creating/updating/reading/deleting/listing
work items.
You mean "projects" instead of "work items" right? Or do you want to have
an endpoint like /project/:name/workitems that lets you define work items
which belong to the project?
Please share your ideas on the the concrete endpoint URL.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/almighty/almighty-core/issues/510#issuecomment-263862891,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARTwq88g_Uh5Cg1QSPqjyTQlg1Jdlw6Lks5rDW02gaJpZM4K8arA
.

Yes, projects instead of work items. Also, as the connection to work items will come later, there will be no "/project/x/workitems" urls yet.


Question on sphereface implementation

Hi, I have a question on sphereface implementation.
In this SphereFace-Revived paper, the 4-th row in Table-1, the characteristic function delta(theta)=ita(theta)-psi(theta)
however in the implementation, it is as follows
d_theta = phi_theta - cos_theta

which I am confused.
In the implementation of SphereFaceR_H with "v2" type of magnitude.  The code follows the equation in Table-1
Any help would be appreciated and thanks for your time.

Hi Lizhen,
Sorry for the confusion. These two deltas denote different terms in our loss function.
The delta in table 1 is to show the difference between the positive and negative logits.
While the delta in our implementation is used for a detach operator.
You could understand them as different terms.


⚠ Doshipui has degraded performance

In 84d4b86, Doshipui (https://дошипуй.рф/) experienced degraded performance:

HTTP code: 200
Response time: 5007 ms

Resolved: Doshipui performance has improved in b9f2b4d after 11 minutes.


How to visualize the tracks?

Hi,
Thanks for the open repository. it is a great project!
I had completed Run the single camera tracking and Run the multi camera clustering, got some revelant files.
so what need to do if i want to visualize the tracks?
Thanks

Hey,
you can check e.g. here: https://github.com/koehlp/wda_tracker/blob/master/utilities/draw_multi_camera_tracks.py
But it might be that you have to adjust it a little bit to get it running.
The concept is simple. Just draw every tracking position into the correct camera image and annotate the trackID.
You can also annotate in multiple images to get a video.
Just play around.
Thanks,
Philipp

Hi, Philipp
Thanks for your reply
I had checked the code in utilities/draw_multi_camera_tracks.py,
i see that it uses the camera full annotation csv files in the MTA_ext_short_coords.zip.
Can I visualize the tracts only use the csv files in the MTA_ext_short.zip
thanks


Disable the linter if loop variable is used after the loop

If you have a loop where you use the loop variable after the loop, for example:
var i int
for i = 0; i < 1; i++ {
  fmt.Println(i) // prints 0
}

// Then use the value of i after the loop
fmt.Println(i) // prints 1

If you replace it with an intrange without too much thought, you get
var i int
for i = range 1 {
  fmt.Println(i) // prints 0
}

// Then use the value of i after the loop
fmt.Println(i) // prints 0

This got caught in one of my tests, and it really does worry me I would miss such non obvious cases.
This is rather worrisome and prone to human error, it is critical to implement a disable rule in your linter, if the linter finds the loop variable is used after the for loop notably.

Hi @qdm12,
Thanks for the report! This is an interesting one. I think it's not recommended to react to the feedback from any linter without too much thought! 🤪
I'm going to update your examples to use values other than 1 because I think using 1 kind of masks an off by one issue.
var i int
for i = 0; i < 3; i++ {
	fmt.Println(i) // prints 0, 1, 2
}

// Then use the value of i after the loop
fmt.Println(i) // prints 3

var i int
for i = range 3 {
	fmt.Println(i) // prints 0, 1, 2
}

// Then use the value of i after the loop
fmt.Println(i) // prints 2

Now we can see that using the range loop in this style does update i as expected, its just off by one because the first example causes a final post increment on the last iteration.
I think the linter is correct that this code can be updated even though the original code is kind of odd. It just can't be updated without a bit thought 🤔
For example, it could be updated to add a final post increment after the loop to replicate the original logic:
var i int
for i = range 3 {
	fmt.Println(i) // prints 0, 1, 2
}

i++

// Then use the value of i after the loop
fmt.Println(i) // prints 3

Or better yet, since you know what the final value of i will be before even going into the loop, just use that:
n := 3
for i := range n {
	fmt.Println(i) // prints 0, 1, 2
}

// Then use the value of n after the loop
fmt.Println(n) // prints 3

Go Playground with all examples
This would be a dangerous thing to autofix but since the tool doesn't autofix these I don't think I see an issue yet.
There is some discussion about user defined exclusions in #31. Unless I'm missing something here, I'll probably close this one in favor of that one.

I think it's not recommended to react to the feedback from any linter without too much thought

Definitely, but that was really an non obvious case to think about. I really thought intrange would behave the same, especially given the linter suggesting the replacement.

I think the linter is correct that this code can be updated even though the original code is kind of odd.

It's not that odd, in that case I was keeping track of the number of tries and there is an if check after the loop checking if we reached the max number of tries i == n.
The approaches you mention to workaround it don't work if you have if+break within the loop, you would need to check i == n - 1 instead of i == n after the loop, I think that's the only fix.

This would be a dangerous thing to autofix but since the tool doesn't autofix these I don't think I see an issue yet.

Ehh I'm pretty sure I wouldn't be the only one wanting to migrate to intrange without realizing this intrange tiny change of behavior. I wouldn't have a unit test covering the code, this could have catastrophic consequences and is also tedious to debug. My point is, even knowing the problem now, I still think it's easy to get bitten by this especially since your linter suggests the replacement.
Again, a fix would be to NOT suggest using intrange for code using the loop variable AFTER the loop (rare-ish cases like mine). Or at the very least suggest it but with a different message pointing out the last value of the loop variable won't be the 'max'.

@qdm12 I'm not going to keep providing example code but I'm still failing to see any reason a range loop would not be able to be used when the key is defined in an outer scope.
I have augmented the message in the case that the key could be accessed outside of the loop as a hint to be aware of side-effects.

I have augmented the message in the case that the key could be accessed outside of the loop as a hint to be aware of side-effects.

That's great, thank you 💯

I'm still failing to see any reason a range loop would not be able to be used when the key is defined in an outer scope.

Really the problem is not using the key in an outer scope, but using it in an outer scope to check if it's the last element due to the last increment not being ran anymore.
Developers using your linter are likely new to the new range mechanism, and, if their code checks the last value of the index, it can cause problems. The most concrete use of this for me is, as previously mentioned, to check if we reached the last "try". This is obviously an easy fix, but it's rather obscure to know the problem first.


[REQUEST] Allow "customers" to use !close

Allow the "customers" DMing the bot to close their own ticket with !close
Would reduce admin overhead closing tickets that slip through the "ignoreAccidental" cracks

I agree with this.

Any update on this? @dragory

Added in v2.17.0 as allowUserClose option. The command will provide no feedback to the user unless closeMessage is also set, but the thread will be closed regardless.

Thanks!
v / r
Robert Klebes
Mobile:<PHONE_NUMBER>
https://keybase.io/sporkwitch
https://www.linkedin.com/in/klebes
On September 20, 2018 4:43:08 PM EDT, Miikka<EMAIL_ADDRESS>wrote:

Added in v2.17.0 as allowUserClose option. The command will provide
no feedback to the user unless closeMessage is also set, but the
thread will be closed regardless.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/Dragory/modmailbot/issues/69#issuecomment-423326450


QUIC: Fix multistream script 19 stochastic test failure

Urgent due to CI breakage on FreeBSD.

*#!$!. I am just outright dumping this line, it is not even needed because the thing it is supposed to be testing is tested perfectly fine by script 17.
-    OP_CHECK                (check_key_update_ge, 4)

OK with urgent. @mattcaswell please reconfirm.

Agree urgent

Merged to master. Thanks.


Update outdated link

Old link gives SSL error.
Editing old link to same without https redirects to http://docs.brew.sh, which I assume is the correct link.

Thanks for your contribution to Homebrew!  You rock!


[AutoRelease] t2-consumption-2022-11-30-93016(can only be merged by SDK owner)

https://github.com/Azure/sdk-release-request/issues/3482
Live test success
https://dev.azure.com/azure-sdk/internal/_build?definitionId=979

issue link:https://github.com/Azure/sdk-release-request/issues/3482


Update reactivations-report.md

Added Azure DevOps Service extension details on similar lines for Azure DevOps Service users and marketplace link
email id -<EMAIL_ADDRESS>

@Frenemee2020 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@KathrynEE - Thanks for accepting the PR. We would also need to change the content on top to include Azure DevOps Service
Azure DevOps Server 2020 | Azure DevOps Server 2019 | TFS 2018 - TFS 2013| Azure DevOps Service
Please let me know if i can submit a change for this as well.

@Frenemee2020  - Hi Deepak - you should be making updates to content in the azure-devops-docs-pr repo. For information on making contributions, please see the information posted here: Contribute content to Azure DevOps.
The SQL Reports are only valid for on-premises Azure DevOps - so the change to the platform/version header at the top should not be changed.  If you want to add a note about the marketplace extension - then it should probably be placed on this page: https://docs.microsoft.com/en-us/azure/devops/report/powerbi/sample-odata-overview?view=azure-devops-2020. I can also add it to this page: https://docs.microsoft.com/en-us/azure/devops/boards/extensions/?view=azure-devops-2020.


s3 maven repository always requires credentials/authentication

Context
I have S3 bucket that's accessible via specific network (whose ip address is whitelisted in bucket policy).  The bucket is accessible via curl/browser. I couldn't find a way to access (read from) the bucket w/o authentication.
Current Behavior
Credentials/Authentication is required when specifying s3 backed maven repository.
    maven {
        name 'maven repository'
        url 's3://bucket-name.s3.amazonaws.com/'
    }

Results in:
S3 resource should either specify AwsIamAutentication or provide some AwsCredentials.

Expected Behavior
A way to access s3 bucket w/o authentication. To this moment I only have two suggestions:

Accessing w/o authentication when no credentials/authentication is specified:

    maven {
        name 'maven repository'
        url 's3://bucket-name.s3.amazonaws.com/'
    }

Accessing with new authentication type, let's call it 'None':

        maven {
            name 'maven repository'
            url 's3://bucket-name.s3.amazonaws.com/'
            authentication(None)
        }

PS: any simple workaround (that requires no extra dependencies) would help me.

The bucket is accessible via curl/browser.

Then you should be using http as the protocol. If you've enabled static web hosting (or something similar) to allow anonymous access to the bucket then it should not be accessed via the AWS API but rather as a regular HTTP repository.

I haven't enabled static content serving, also responses are BucketList xml. It's early morning, and I may be missing something, but switching to http:// instantly solved the issue.
Thanks, Mark!

Closing this issue since this is just a configuration issue. There is effectively no such thing as anonymous access via the s3 protocol. Talking to the S3 API (or any AWS API for that matter) requires credentials of some sort. It wouldn't make sense for us to not require a credentials provider here, although there are likely other credentials providers we don't currently support.

@mark-vieira Do we need credentials for accessing the  bucket which have public read


Add option to bypass authenticating to s3

This allows for anonymous uploads to s3.
An example would be a setup where you are running an s3 bucket that is accessed through an s3 endpoint on a vpn'ed subnet, or in some other highly restricted way.
Tested and "works on my machine", would love to see this added.

No need, @jaustinpage. Github will squash automatically on merge.
This looks good now. Thanks for your contribution!


Document selectTab in README

Would be nice to have this in the README.

Feel free to send PRs to improve the readme.


Support generating user delegation backed SAS tokens

Storage Explorer currently only supports generating SAS tokens backed by the account keys. Storage Explorer should also be able to generate user delegation backed SAS tokens.
Note: issue created from CSS user feature request.

I am eagerly awaiting this feature to be implemented as soon as possible.

We're going to break this up by service type.

[ ] Blob (incl Gen2) -> 1.26
[ ] Table -> 1.27
[ ] Queue -> 1.28

Done for blob/gen2. Move to near future for the rest of the services because they don't have user delegation SAS support at the moment.

Haven't heard anything regarding tables and queues. Going to close this. Can open issues once those services support user delegation SAS.


meltano ui anonymous opt-in analytics refresh

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/3234
Originally created by @pandemicsyn on 2022-02-10 22:14:25

@tayloramurphy and friends are trying to understand UI adoption/usage and it appears we're using google analytics to collect some anonymous opt-in metrics in the UI. However, the data we're receiving appears to be limited to vanilla page view events.
To collect analytics and inject the ga tracker we're using vue-analytics. Considering what @tayloramurphy shared in the GA console and based on the fact that I don't see any use beyond https://gitlab.com/meltano/meltano/-/blob/master/src/webapp/src/utils/setupAnalytics.js we're probably not actually capturing much beyond basic pageviews.
vue-analytics does support custom events but I checked a few spots and ran a few searches (v-ga, $ga, etc) but didn't find any occurrences of those in the web app. I don't think we're firing any additional events today in the UI.
Since vue-analytics is no longer maintained anyway, we should consider switching either to Google Tag Manager (vue-gtag?) or could consider a switch to Snowplow (via BrowserTracker?).
@tayloramurphy do y'all have a bias or preference here on which route we should take (GA vs Snowplow)?

View 3 previous comments from the original issue on GitLab

Closing as no longer relevant on account of the removal of the UI for Meltano 3.0


missing unmask

My models don't use masks and I want to be able to unmask the input value before sending to database.
Is there a feature/option like that?
From testing I became creating a directive to remove the masks on (blur) just on the model with:
this.model.viewToModelUpdate(this.model.model.replace(/\-/, ""));
Example: In the component below from PrimeNG there is an attr unmask:
http://www.primefaces.org/primeng/#/mask

Thanks for the request. Unfortunately, Text Mask does not support this yet. I still haven't figured out a good way to add it that will work for all use cases and for components other than Angular 2.
Check out this issue, it might contain ideas on how to achieve what you want (if your current solution is not sufficient).


Fixed Typo

Nit: This should probably have a better commit message than just Fixed Typo since that's pretty non-descriptive!?

Nit: This should probably have a better commit message than just Fixed Typo since that's pretty non-descriptive!?

Sorry about that: I just focused on the patch itself. @Bomberus ^^

Hi @calixteman,
commit message and title should now be more descriptive.

/botio xfatest

Looking at the ref-tests there appears to be some actual regressions, e.g. in xfa_bug1718670_1-page3 and xfa_bug1717668_4-page12.


Adoption

I emailed my interest in adopting simple-statistics-py yesterday, but opening this issue here just in case.

Awesome!

[ ] @tmcw requests a transfer from tmcw-up-for-adoption to @sheriferson

Thanks! :)


Update event-list.component.ts DOM text reinterpreted as HTML

By using innerText, it will avoid the risk of HTML injection, as these properties automatically escape any HTML special characters in the provided text. This helps prevent cross-site scripting (XSS) vulnerabilities by treating the input as plain text rather than interpreted HTML.

Hi @evil-shrike Could You Please Review This PR
Thanks

Hi @evil-shrike Thanks For Reviewing PR's
Instead of using innerText or innerHtml  Can we use textcontent
I think it could be work fine ?
Thanks

Maybe, but may I what issues you're facing (so that innerHTML doesn't work for you)?

Hi @evil-shrike Thanks For Reviewing
It works Fine But I think it would be More Secure and Provide Security Enhancement To the Code
Thanks

Understand but the project isn't in a state where I'm ready to introduce changes 'just-in-case', sorry


[W5.11][F09-3]Tan Wei Ming

This is a large enhancement that is written extremely well, is structured correctly, and follows the OOP style. Perhaps you could add a few test cases to test out your new command.

A good function to add to the code base. Written for humans to read and is structured well, all while following the OOP style. Possibly updating the UserGuide to allow new users to use the new feature would be a nice touch.


Multiple Pages: Links not opening in a new tab

The following Links on the home page are not opening in a new tab:

The Ionic Framework
Angular (Google)
React.js (Facebook)
Node.js,
MongoDB
Adobe Photoshop
Sketch App
Abstract

The following Links on the Opportunities page are not opening in a new tab:

“Ionic Team”
“React App”
“Ionic”

Present On all browsers

PR #153 fixes this

Working As expected. Closing TIcket.


python312Packages.nanobind: fix build on x86_64-darwin

https://hydra.nixos.org/build/279984694
ZHF #352882

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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/)
25.05 Release Notes (or backporting 24.11 and 25.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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 359539

x86_64-linux

x86_64-darwin

:x: 4 packages failed to build:

python311Packages.asteroid-filterbanks
python311Packages.asteroid-filterbanks.dist
python312Packages.asteroid-filterbanks
python312Packages.asteroid-filterbanks.dist

:white_check_mark: 18 packages built:

pianotrans
pianotrans.dist
python311Packages.librosa
python311Packages.librosa.dist
python311Packages.piano-transcription-inference
python311Packages.piano-transcription-inference.dist
python311Packages.soxr
python311Packages.soxr.dist
python311Packages.torchlibrosa
python311Packages.torchlibrosa.dist
python312Packages.librosa
python312Packages.librosa.dist
python312Packages.piano-transcription-inference
python312Packages.piano-transcription-inference.dist
python312Packages.soxr
python312Packages.soxr.dist
python312Packages.torchlibrosa
python312Packages.torchlibrosa.dist

aarch64-darwin

:fast_forward: 2 packages marked as broken and skipped:

tts
tts.dist

:x: 14 packages failed to build:

python311Packages.asteroid-filterbanks
python311Packages.asteroid-filterbanks.dist
python311Packages.pyannote-audio
python311Packages.pyannote-audio.dist
python311Packages.torchcrepe
python311Packages.torchcrepe.dist
python312Packages.asteroid-filterbanks
python312Packages.asteroid-filterbanks.dist
python312Packages.pyannote-audio
python312Packages.pyannote-audio.dist
python312Packages.torchcrepe
python312Packages.torchcrepe.dist
whisper-ctranslate2
whisper-ctranslate2.dist

:white_check_mark: 22 packages built:

pianotrans
pianotrans.dist
python311Packages.librosa
python311Packages.librosa.dist
python311Packages.piano-transcription-inference
python311Packages.piano-transcription-inference.dist
python311Packages.soxr
python311Packages.soxr.dist
python311Packages.torch-audiomentations
python311Packages.torch-audiomentations.dist
python311Packages.torchlibrosa
python311Packages.torchlibrosa.dist
python312Packages.librosa
python312Packages.librosa.dist
python312Packages.piano-transcription-inference
python312Packages.piano-transcription-inference.dist
python312Packages.soxr
python312Packages.soxr.dist
python312Packages.torch-audiomentations
python312Packages.torch-audiomentations.dist
python312Packages.torchlibrosa
python312Packages.torchlibrosa.dist


Add feature toggle configuration & configurable key validation

Add feature toggle configuration for future features.
Either perform validation or disallow multiple URLs for a key, depending on the toggle activation.
This will allow breaking changes to be manually activated, until such a time as we want to do a release which enforces the breaking change to be active.

Codecov Report

Merging #825 into master will decrease coverage by 0.02%.
The diff coverage is 96.49%.

@@             Coverage Diff              @@
##             master     #825      +/-   ##
============================================
- Coverage     99.49%   99.47%   -0.03%
- Complexity     2032     2047      +15
============================================
  Files           305      306       +1
  Lines          5999     6039      +40
  Branches        299      306       +7
============================================
+ Hits           5969     6007      +38
  Misses            5        5
- Partials         25       27       +2

Impacted Files
Coverage Δ
Complexity Δ

...c/main/java/com/quorum/tessera/p2p/P2PRestApp.java
100% <100%> (ø)
3 <2> (ø)
:arrow_down:

...rum/tessera/partyinfo/PartyInfoServiceFactory.java
100% <100%> (ø)
2 <1> (ø)
:arrow_down:

...java/com/quorum/tessera/p2p/PartyInfoResource.java
100% <100%> (ø)
15 <3> (+1)
:arrow_up:

...va/com/quorum/tessera/admin/ConfigServiceImpl.java
100% <100%> (ø)
8 <1> (+1)
:arrow_up:

...java/com/quorum/tessera/config/FeatureToggles.java
100% <100%> (ø)
7 <7> (?)

...rc/main/java/com/quorum/tessera/config/Config.java
100% <100%> (ø)
31 <2> (+2)
:arrow_up:

...quorum/tessera/partyinfo/PartyInfoServiceImpl.java
96.92% <91.3%> (-3.08%)
20 <10> (+4)

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 d94b76f...b93eede. Read the comment docs.

Fixes https://github.com/jpmorganchase/tessera/issues/833


QUESTION ❓: Any reason to not include 'OnEnable' and 'OnDisable' on the list of Unity Lifecycle Callbacks?

Besides that I'm looking forward in contributing to this project!
Do you plan to maintain / continue developing it?

@niscolas OnDisable and OnEnable are callbacks for when a behaviour gets disabled or enabled, and can be called multiple times over the lifetime of a particular object. That's why, though they can be called during the creation and destruction of GameObjects, I wouldn't consider them primarily lifecycle callbacks. If the developer is using them as work-arounds for the "no lifecycle callbacks rule", then that would considered a rule break.
I also don't want to restrict usage of these callbacks, as they can be useful for other things (such as a pooling system or general optimizations).

Besides that I'm looking forward in contributing to this project!
Do you plan to maintain / continue developing it?

Yes! I do have some plans for this package, and hope to polish it as It gets applied to other projects. Feel free to contribute with pull requests!


Two MS Teams user with compliance policy assigned in the same call, captures double audio streams

@ksikorsk @ssulzer @ananmishr @zihzhan and anyone can help on this.
When two users with recording policy assigned join the same meeting/call, it captures the data twice. I am using that data for audio transcription which transcribes the audio data twice.
How can I resolve that?

@bijaykush I also encountered this problem. Have you already resolved this problem? I will be appreciate you for answer.

I believe that this is intentional.  Policy recording is per-user, so it's entirely possible that there will be multiple recording bots in the same call paired to different users, with different policies, and maybe even from different orgs.  This also means that if you have a call that has AB, then ABC, then BC, a recorder on A could record the first two blocks, and a recorder on C could record only the second two.  If you want to handle this in your bot, and keep recording until the end of a call no matter what, just track the conference IDs that you're already recording, and don't start a duplicate.

@chrisbardon It`s good idea to to track the conference id. Thank you!

Hi,
This is by design. Every time a policy assigned user joined in the meeting, a policy recording bot would join in and start recording. Vice versa when the user left the meeting. Like @chrisbardon said. It's a really a good example that he provided.


[Cortx/Seagate hackathon] FreeSheet project

Add FreeSheet hackathon integration project.
Effortlessly move and onboard csv data between Cortx and IPFS into autogenerated starter Jupyter lab notebooks.
Built for the CortX 2022 hackathon on devpost: https://seagate-cortx-hackathon2022.devpost.com/
See Readme in project root folder for full instructions.
Screenshots (if appropriate)
Checklist

[ x] tested locally
[ x] added new dependencies
[ x] updated the docs
[ x] added a test

View rendered doc/integrations/freesheet-jupyter/LICENSE.md
View rendered doc/integrations/freesheet-jupyter/README.md

@mukul-seagate11 please merge this hackathon entry.


This should not happen. For some reason the elements is already added

Hi,
Only see it when running nmslib in k8s pod. The same data set(can be shuffled) runs ok locally.
Could you elaborate about the error?

Hi @sh1ng what's exactly the problem? Could you elaborate?

Sorry, looks like multiple threads were adding duplicated.
May be it's worth to make the message more explicit about it.


Add "client_src" field

This new field is part of the initiative to incentivize applications to run their nodes instead of relying on remote nodes thus "client_src" references where the client source code can be download from.
There should be a discussion about what requirements these references must have to be valid to be added to this registry

Thanks for explaining the motivation, this really helps. Given this, I think the term "client" is misleading as it implies a software connecting to the blockchain. What about "node source"?

Sounds good to me. Let's change it to "node_source"

Is this supposed to me machine-processable in the sense that it allows for automatic node spawning?

If yes, we should have download source, software version and checksum/signature in the registry. This comes with the drawback that an update to the registry is necessary for every single patch release of every implementation of every network.
If no, we can link webpages that describe the software distribution process in a general, admin friendly way. The link should be long living.

I think that two main things should be considered when speaking about this field:
First, it should not be mandatory.
There could be some chains that do not want to distribute their node source code (federated ones, or even private chains as a whole)
Second, also answering @webmaster128, I think we should require the user to use a Github/Gitlab/w.e link to a specific commit that represents the software version to use.

If we allow the user to insert a generic link, we cannot make sure that is a valid link and will always be (might be a redirect, or something else).
If we allow the user to insert a downloadable executable, we cannot make sure that it will always be a trustworthy executable. It might start acting as a virus or something else malicious.

Targeting developers, I think they will know how to build and deploy the node by just having two things:

Reference to the executable source
Reference to the build guide

So, I think we could expand the node_source field renaming it to node_info and having the following attributes
{
 "node_info": {
   "version": "1.0.1",
   "source_code": "https://github.com/commercionetwork/commercionetwork/tree/v1.0.1",
   "build_instructions": "https://github.com/commercionetwork/commercionetwork/blob/master/docs/join-mainnet.md"
 }
}

Also, having an object as a field we will later be able to add additional information without much trouble.

+1 for making this optional.
With this approach I see two disadvantages at the same time:

An update to the registry is required for every version update of the node software
It is not possible to automatically spawn a node with the information provided by the registry

We should accept the fact that with URLs and redirects it is always possible to change the target to somewhere else than at the time of the PR. This can also be very good e.g. when thinking of download mirrors. Having checksums ensures nothing crazy happens.
So for me the question is still open: does this need to be machine processable? Then we should have a direct link and a checksum of the file. Otherwise build instructions are sufficient and we don't need the version in the registry, since the latest version can be available in the build instructions.

I think this should not be machine processable.
Some chains might not have the characteristic of having reproducible builds (such as Cosmos a few weeks ago)  and thus the checksum on the executable itself will not prevent strange things from happening.
A link to the codebase and build instructions could be best way to go that allows to have fewer updates and prevents anything strange from happening.
If a developer wants to automatically spawn a node, then he can create a tool to perform all the checks and different things he might want to do IMO.

Fine for me. In this case a generic link to build instructions would do the job


[google_sign_in] Throwing deprecation warnings and using outdated SDK and dependencies

Right now google_sign_in is throwing several deprecation warnings about embedding v1 like the following.
With #91069 in mind, i think the best action would be to remove all reference to embedding v1.
Besides that this package is targeting old dependencies and SDK and it should be updated.
/Users/x/Documents/flutter/.pub-cache/hosted/pub.dartlang.org/google_sign_in-5.1.1/android/src/main/java/io/flutter/plugins/googlesignin/GoogleSignInPlugin.java:79: warning: [deprecation] Registrar in PluginRegistry has been deprecated
  public void setUpRegistrar(PluginRegistry.Registrar registrar) {
                                           ^
/Users/x/Documents/flutter/.pub-cache/hosted/pub.dartlang.org/google_sign_in-5.1.1/android/src/main/java/io/flutter/plugins/googlesignin/GoogleSignInPlugin.java:270: warning: [deprecation] Registrar in PluginRegistry has been deprecated
    private PluginRegistry.Registrar registrar;
                          ^
/Users/x/Documents/flutter/.pub-cache/hosted/pub.dartlang.org/google_sign_in-5.1.1/android/src/main/java/io/flutter/plugins/googlesignin/GoogleSignInPlugin.java:285: warning: [deprecation] Registrar in PluginRegistry has been deprecated
    public void setUpRegistrar(PluginRegistry.Registrar registrar) {

Right now google_sign_in is throwing several deprecation warnings about embedding v1

@blasten We should have suppressions on these until we fully remove support for v1, right?

Besides that this package is targeting old dependencies and SDK and it should be updated.

This is unrelated, and should be tracked in another issue (IIRC there is one already, but I'm not 100% sure offhand.)

This is unrelated, and should be tracked in another issue (IIRC there is one already, but I'm not 100% sure offhand.)

Yes indeed my bad, there is already a draft PR for this. https://github.com/flutter/plugins/pull/4253


chore: improve web load time

inline boostrap script
preconnect to www.gstatic.com

FYI: TTL for fontmanefist.json is around 240ms on my machine (at work). This is a good measure to see if this PR changes things.

FYI: I didn't see any actual load time improvement. 🤔 🤷


Use Redux and upgrade react and react-router modules

Use redux instead of reflux to manage actions and state, to make the application scale up easily.
First steps:

Use react and react-dom 0.14.0 instead of react 0.13
Use react-router 1.0.0-rc3 instead of ^1.0.0-rc1
add redux, redux-react and redux-thunk
check what is the purpose of     "redux-logger": "^2.0.2" and "redux-router": "^1.0.0-beta3" also used in real-world example
Use "dumb" React components in the "components" folder, and smart component(s) in a new "containers" folder...

Problem when updating react-router: how to pass data to Route components ?
Before the following code was used to start the route, after having made the initial request to get project data:
app.start( function (err, data) {
  var node = document.getElementById('app');
  //Setup content about bestof.js.org so that it can be used in any page (homepage, about...)
  var staticContent = {
    projectName: 'bestof.js.org',
    repo: 'https://github.com/michaelrambeau/bestofjs-webui'
  };
  if (err) {
    React.render(<ErrorMessage text={ err.message } />, node);
    return false;
  }
  Router.run(routes, function (Handler) {
    React.render(
      <Handler data={ data } staticContent={ staticContent }/>,
      node);
  });
});

It is no more possible with the v1.0... TO BE CONTINUED...

Release 0.2.0 introduces Redux in the mix!
New start-up process:

entry.jsx file calls ./getInitialData file that triggers an ajax request to get data about projects and tags from the static JSON file on divshot.

When data is received, the Redux state is initialized using const store = configureStore(initialState)

Then the Redux application is started with the code

  render(
    <Provider store={store}>
      <ReduxRouter />
    </Provider>,
    window.document.getElementById('app')
  );


Total breakdown of syntax highlighting with ES6 factory functions

From @David-Else on September 1, 2017 9:47

VSCode Version: 1.15.1
OS Version: Fedora 26

Steps to Reproduce:

copy the code pasted below into vscode with Javascript as the language
observe the syntax highlighting fail

Please see the attached screen dump

Reproduces without extensions: Yes
    // Factory functions

    const createZombie = ({
        status = 1,
        width = 10,
        height = 10,
        xPosition,
        yPosition,
        color = "green"
    }) => ({
        status,
        width,
        height,
        xPosition,
        yPosition,
        color
    });

    const createHero = ({
        status = 1,
        width = 25,
        height = 50,
        xPosition,
        yPosition,
        color = "red"
    }) => ({
        status,
        width,
        height,
        xPosition,
        yPosition,
        color
    });

Copied from original issue: Microsoft/vscode#33664

This is a similar issue to #481 and some others. We currently do not handle multiline arrow function declarations well

Thanks for your explanation. Hope it gets sorted soon, it look dreadful inside VSCode like that and is causing bad vibrations inside the editor.


MariaDB - Fixing Hyperlink in Readme file.

Signed-off-by: Sandeep Kumar Verma1<EMAIL_ADDRESS>

Hi @Tal-Daniel
Its just a minor PR, its pending from long time.  Please take the necessary action on it.

Hi @ofer-haim  @PratikshaSonawane
This is a minor link change can you request you to please review so that Tal can merge the changes.
Thanks
Sandeep Verma


Shrink sizeof Value struct

Use pointer instead of inlined value for std::string
Use bit fields in DateTime

Great job, take https://github.com/vesoft-inc/nebula-common/pull/488 together.


mkdir followed by createWriteStream causes "Error: You cannot pipe after data has been emitted from the response." sometimes

I am obtaining sftp connection from ssh2.connect(), then running sftp.mkdir() followed by createWriteStream to send file from local machine.
I then commence transferring data by doing following.
readstream.pipe(writestream);

When I do, I sometimes receives following error message.

Error: You cannot pipe after data has been emitted from the response.

I have an async for loop to run multiple paris of sftp.mkdir() and uploading files to the sftp server. I usually run into the issue within 2nd or 3rd file.
If I don't run mkdir(), I can keep uploading files without the error message. I believe there is a bug within sftp.mkdir() that corrupts the next streaming.. or something.. but I am not sure. I also saw a note about "continue" event sometimes generated that I need to wait for, but my sftp() calls alway return true. (And the documentation doesn't describe what "continue" events are, and why I need it, etc..)
Thank you!

A brief google shows 'You cannot pipe after data has been emitted from the response' is an error coming from the module request, not from this module or node core.

I found what the issue was. sftp.createWriteStream() by-default closes sftp session after the pipe closes. I've updated it to this
let writestream = sftp.createWriteStream(path, {autoClose: false});

Yep, that mirrors the node fs API. I'm glad you found a solution though.


Receive contact us details on EMAIL instantly for faster response to user

Is there an existing feature request for this?

[X] I have searched the existing feature requests

Describe the feature you would like to request
i can implement this feature where you will receive this info instantly on mail
What problem does this feature solve?
for instant response to user
enhance user experience
Alternative solutions
No response
Confirmation

[X] I have read the Bitbox Contributing Guidelines
[X] I am a GSSOC-EXT contributor
[X] I am a HACKTOBERFEST contributor
[X] I have starred the Bitbox repository
[X] I would like to help implement this feature

Hyy @Sawan-Kushwah, I'm assigning this issue to you.


Add column-wise transforms & refactor TableVectorizer

closes #874, #886, #894, #877, #848, #904, #905
This is the last part of the changes outlined in #877 (the first two parts have been merged in #895 and #888)
The main addition is OnEachColumn, a transformer that applies a transformation independently to each column in a dataframe, and is used to refactor the TableVectorizer and ensure it does consistent operations across calls to transform.

after removing the remainder transformer I am wondering if we need the numeric_transformer in the TableVectorizer? Numeric columns are already "vectorized". And if we want to apply a transformation to numeric columns such as scaling or imputation, we probably want to do it for all columns (including the output of the low_cardinality, high_cardinality, and datetime transformers), not just for columns that were already numeric in the input. So we would need a pipeline step after the tablevectorizer rather than setting the numeric_transformer. @GaelVaroquaux  and others WDYT?

also WDYT of renaming the transformers to 'encoders': high_cardinality_encoder to distinguish them more clearly from the other transformers that are applied (the preprocessing steps)?

yep I think you're right

I'll make a pass now.

Oops so sorry @glemaitre I should have said so but I think @GaelVaroquaux was planning to review it as well ... @GaelVaroquaux , if you would like LMK if you want to review maybe the easiest way will be to revert the merge commit and open a new PR to un-revert

Thanks a lot for the review @glemaitre !

No, no, it's good to have merged. I can give feedback via issues.
Hurray for merge. Thanks a lot to everyone involved!!

Thanks @GaelVaroquaux. We will address the subsequent issues. Let's roll ;)

No, no, it's good to have merged. I can give feedback via issues.

ok, thanks. there will be a few follow-up PRs in any case, @TheooJ and I are going to open a couple of issues


⚠ Bofrost.lu has degraded performance

In 7665f4e, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1255 ms

Resolved: Bofrost.lu performance has improved in 7f9e2c9.


Have MLDB compile under MacOSX

Blog post about MLDB Hacktoberfest 2016

Compile MLDB under MacOSX. Alter the code if needed, but it must not break existing compatibilities.
If special instructions need to be followed (eg.: setup, package installations), provide an instruction page.

@FinchPowers Is this not supported for mac OS X yet, except by using OVA?

Correct.

See #914


Bugfix & Update to CWOD-Exalted EXvWOD

Submission Checklist
Required

[x] The pull request title clearly contains the name of the sheet I am editing.
[x] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[x] The pull request makes changes to files in only one sub-folder.
[x] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

New Sheet Details

The name of this game is: <   >  (i.e. Dungeons & Dragons 5th Edition, The Dresden Files RPG)

The publisher of this game is: <   > (i.e. Wizards of the Coast, Evil Hat)

The name of this game system/family is: <   > (i.e. Dungeons & Dragons, FATE)

[x] I have followed the Character Sheets Standards when building this sheet.

[ ] This sheet has been made on behalf of, or by, the game's publisher.
[x] This game is not a traditionally published game, but a copy of the game rules can be purchased/downloaded/found at: < https://holdenshearer.wordpress.com/2021/10/26/exalted-vs-world-of-darkness-revised/   >
[x] This sheet is for an unofficial fan game, modification to an existing game, or a homebrew system.

Changes / Description
Modified EXvWOD.css to prevent the sheet from running out of room for Backgrounds and Charms. Updated EXvWOD.html to reflect revised essences recovery values.

Character Sheet Info Roll20 Internal Use only.


How to connect the wheelPicker with Storyboard?

I can't seem to connect the wheelpicker w/ storyboard.
It would've been nice if you provided some documentation on that.

Figured out.
For anyone in the future struggling this is how I got it working for mine.
Download his example code, make it work. You need to connect a UIView outlet into your view controller. In the UIVIew in the storybaord, override the view's class to "WheelPicker". Then it should work


Chessboard Display Problem

The chessboard is not displaying properly

At the bottom the files are there but not the correct height. The Pieces move properly but they are not visible.
My code:  I used this: AbChess-0.3.0.zip but extracted as a folder

Chess-Website

Home
Puzzles
Play
Watch
Login/Sign up

Hello, thanks for using my code. Unfortunately, it is no longer maintained and it should not be used for any production.
Regards.


Various fixes for ZIP64 writer (zero byte entries, 32 bit where supported)

To improve compatibility with older ZIP clients I've modified the directory headers to write the corresponding 32 bit values if values still fit in 32 bits (this will allow them to read as if it's a ZIP32, and able to completely ignore the extra ZIP64 fields in ZIP headers if the decompressed size <= 32 bits)
Another problem fixed in order not to trip up 7-zip/WinRAR, zero byte files need to have compression value 0 (STORED). Now with zero byte files in the archive they will validate correctly.
I've tested these changes on WinRAR, 7-zip and windows explorer .zip (Windows 10 RS5), and using the latest changes don't get any complaints anymore extracting ZIP/ZIP64.

Great!  Thank you!


Update songstats.js - translations, styling

Added translation of the popup title (please correct the French popup title if I am wrong) and added Czech translation.

And even did a bit of styling, maintaining its simplicity.
By the way, love the code, went through it and it gave me ideas and motivation perhaps for my own extension, thanks!


Instrument modules loaded via process.getBuiltinModule?

Node has added process.getBuiltinModule(id) to allow synchronous loading of built-in modules:
https://github.com/nodejs/node/pull/52762
The idea is that library authors will now more easily be able to create cross runtime libraries that can conditionally load Node APIs only when running in Node:
if (globalThis.process?.getBuiltinModule) {
  // Running in Node.js, use the Node.js fs module.
  const fs = globalThis.process.getBuiltinModule('fs');
}

OpenTelemetry instruments modules via require-in-the-middle and import-in-the-middle but built-in modules loaded via this new API will not be instrumented as it doesn't go through require.

Keep it

Looks like this was added to require-in-the-middle a few weeks ago:
https://github.com/elastic/require-in-the-middle/pull/92
So we just need to update to the latest release and this can be closed?

Ok so we're using a caret for the require-in-the-middle version so if users update their dependencies they will get the latest version.
https://github.com/open-telemetry/opentelemetry-js/blob/f047db9da20a7d4394169f812b2d255d934883f1/experimental/packages/opentelemetry-instrumentation/package.json#L78


E: Some index files failed to download. They have been ignored, or old ones used instead. this issue is occurred  while using command apt-get update in bash on ubuntu on windows

This bug-tracker is monitored by developers and other technical types.  We like detail!  So please use this form and tell us, concisely but precisely, what's up.  Please fill out ALL THE FIELDS!
If you have a feature request, please post to the UserVoice.  If you're reporting a BSOD, don't post here!  Instead, e-mail<EMAIL_ADDRESS>and if possible attach the minidump from "C:\Windows\minidump".

Your Windows build number:  (Type ver at a Windows Command Prompt)

What you're doing and what's happening:  (Copy&paste specific commands and their output, or include screen shots)

What's wrong / what should be happening instead:

Strace of the failing command, if applicable:  (If <cmd> is failing, then run strace -o strace.txt -ff <cmd>, and post the strace.txt output here)

See our contributing instructions for assistance.

@rohithsingamsetti - Can you please fill in the details as per the template above.


domain specific fine-tuning

hi team,
I wanted to fine-tuning full parameters of gemma model, I noticed there is an example, https://github.com/Lightning-AI/litgpt/blob/main/litgpt/finetune/full.py , can I use this example for domain specific fine-tuning?
I have prepared the dataset, I converted each page from pdf as each row in csv, and with end of sentence <eos> delimiter.

additionally, I wanted to check whether GaLore has been implemented in Lightning?

@carmocca

I wanted to fine-tuning full parameters of gemma model, I noticed there is an example, https://github.com/Lightning-AI/litgpt/blob/main/litgpt/finetune/full.py , can I use this example for domain specific fine-tuning?

Yes, this model is compatible with finetuning. You could start with one of our config files and then just swap out the dataset. E.g.,
litgpt finetune \
  --config https://raw.githubusercontent.com/Lightning-AI/litgpt/main/config_hub/finetune/gemma-2b/full.yaml \
  --data ...

or
litgpt finetune \
  --config <your updated config file>

additionally, I wanted to check whether GaLore has been implemented in Lightning?

No, I think that's not been super high interest in that, but there's been an open issue for that though if you want to contribute: #1075. We'd definitely appreciate it!
I think that would require some discussion of how the user interface would look like via the config file etc. But  I think it should be a relatively straightforward update if you want to just implement it in a your local litgpt as a local copy for now.

Do I have to maintain any dataset structure or format for domain based fine tuning? Because in instruction based fine tuning I maintain a dataset format like system prompt + instruction + context + question.
Just wanted to check with you whether do I need to maintain a dataset structure? Because I have 480 pdf files and each pdf file consist around 250 pages.
Do I need to use any delimiter? If yes, can you please provide some sample.
Regarding contributions yes I can do it. Once I complete this I can start that.

Sorry, for the late responses, but it's been a busy week. Regarding the domain-specific finetuning, it would be similar to continued pretraining without instructions in your case, correct? Regarding the delimiter, I'd say this is best handled by using the eos token via the respective tokenizer when you are reading and tokenizing the dataset, e.g., tokenizer.encode(text, bos=False, eos=True).
@awaelchli  has a nice working example here in the Continued Pretraining with TinyLlama 1.1B Studio that might come in handy as a template.


Concurrent whisper jobs may fail

Concurrent whisper jobs may overwrite each other's output causing the transcription of one event to end up attached to another event.

PR is merged -> close


Form Validation

🚀 Feature
Form Validation is a project which helps you to check whether your form is correct according to some criteria
Have you read the Contributing Guidelines?
Yes
Motivation
To explore the difficulties and enjoyments of creating projects using JavaScript
Pitch
It can be used to check whether your email id, password, name, age etc are correct or not to get used of it in future work

Please assign me and add it under Hacktoberfeast don't forget to add the label

Related PR: #182

🚀 Feature
Form Validation is a project which helps you to check whether your form is correct according to some criteria
Have you read the Contributing Guidelines?
Yes
Motivation
To explore the difficulties and enjoyments of creating projects using JavaScript
Pitch
It can be used to check whether your email id, password, name, age etc are correct or not to get used of it in future work

Please assign me and add it under Hacktoberfeast don't forget to add the label

Please make a pull request with replying in that issue @UG-SEP

You are 7 commits behind the main. Please fetch it to make it even. @UG-SEP


A task is missing. The pipeline references a task called 'AzureAppConfigurationPush' with version '6'. This indicates that the specific task version can not be found

Receiving the task is missing error with versions 5, 6 and 7 of 'AzureAppConfigurationPush starting around 3pm EST.  Occurring in multiple Azure DevOps projects / orgs and pipelines.  No changes were made to our pipelines around this time.
A task is missing. The pipeline references a task called 'AzureAppConfigurationPush' with version '6'. This indicates that the specific task version can not be found

This just started happening for me as well about an hour ago. I only tried changing from v6 to v7 but saw the same result. Doesn't seem like the task has been updated, nor any changes to our ADO instance. It's blocking all our builds from running right now.

Same issue for us with the AzureAppConfiguration task. Was there a recent deployment or change?

Same here. Our pipeline using this task is blocked because of this.

A task is missing. The pipeline references a task called 'AzureAppConfiguration' with version '6'. This indicates that the specific task version can not be found.

Hello currently looking into this

I have worked around the issue by changing the version to 10 instead of 6. Build is proceeding per usual.
I noticed that the only available version of these tasks in the official repo is v10: https://github.com/microsoft/azure-pipelines-tasks/tree/master/Tasks
And it looks like these tasks were officially adopted into the official repo a few weeks ago:
https://github.com/microsoft/azure-pipelines-tasks/pull/20328
https://github.com/microsoft/azure-pipelines-tasks/pull/20338
But we also have the ADO extension installed from the marketplace (for some reason, this was set up before I got here): https://marketplace.visualstudio.com/items?itemName=AzureAppConfiguration.azure-app-configuration-task&targetId=ca8b8e9e-7645-44ce-bbb0-091e4afb6830&utm_source=vstsproduct&utm_medium=ExtHubManageList
To hazard a guess - having these tasks included in the built-in tasks overrides the extension, such that the extension's version (which I'm assuming includes 6) is no longer usable?

Release notes for v7 and lower are here:
https://github.com/Azure/AppConfiguration/blob/main/releaseNotes/AzureDevOpsPipelineExtension.md
But this page lists a v8, so maybe App Config team broke something trying to switch it from a built-in task to a task on the market?
https://marketplace.visualstudio.com/items?itemName=AzureAppConfiguration.azure-app-configuration-task

We recently released the  AppConfigurationPushTask as a built in task which I suspect could be causing the extension task to be missing as a workaround or to avoid being blocked I would suggest to changing to  version 10. Apologies for the inconvinence caused.
We are currently looking into the issue.
We are also working on updating our release notes to reflect the latest updates.

Yes.  Thanks.  Updating to AzureAppConfiguration@10 as noted by @MaryanneNjeri and @lettucemode worked for me as well.

Is there going to be a fix in the task AzureAppConfiguration itself? I can see two tasks with same name one with version ranging from 3.* to 8.* and another with only @10.* We have multiple pipelines impacted and updating them all might not be possible.

The classic editor give some enlightenment.
The task is there two times:

Once containing version 3-7
And once containing version 10

I was able to use old task by specifying this task name:
AzureAppConfiguration.azure-app-configuration-task-push.custom-build-release-task.AzureAppConfigurationPush@3

After doing some investigation  we also realized that the extension task name somehow got updated to AzureAppConfiguration.azure-app-configuration-task.custom-build-release-task.AzureAppConfiguration after the built in task was deployed which I suspect could be causing the extension task to go missing.
We are currently looking into resolving the issue for the missing task for older versions

@dawidholka

*NOTE: This breaks redeploy functionality. So you will no longer be able to re-run old pipelines :(

The @10 workaround is no longer working.  Getting a few different errors:
##[warning]Failed to download task 'AzureAppConfigurationPush'. Error No task definition found matching ID 04fc3ed1-4513-4f38-b0fe-5a15864bfa9c and version 10.245.0. You must register the task definition before uploading the package.
##[error]wrong number of segments

Same... we were in the middle of updating all of our pipelines to 10. Has the update been pulled? @MaryanneNjeri

Yep, this is what we're seeing as of a few minutes ago: ##[error]A task is missing. The pipeline references a task called '04fc3ed1-4513-4f38-b0fe-5a15864bfa9c'. This usually indicates the task isn't installed, and you may be able to install it from the Marketplace: https://marketplace.visualstudio.com. (Task version 10.245.0, job 'Job', step 'AzureAppConfigurationPush'.)

Version 10 has been pulled.

Yesterday my pipelines were running with version 6 and started giving errors, I changed it to version 10 and it started working, now my pipes are not working with any version, I tested 5, 6, 7 and 8 and it is returning the following
error: ## [error]wrong number of segments.
Anyone else having this problem?

@evertonlsouza
How are you referencing the AzureAppConfiguration task?
For example
- task: AzureAppConfiguration@7

We're using - task: AzureAppConfigurationPush@7

@danieljaime-liberis
Version 10 has been removed, if you revert back to 5 does it work again?

Hi, I made a change that was sent by MaryanneNjeri, and it worked, it seems that the name of the task also changed, making it work like this:

task: AzureAppConfiguration.azure-app-configuration-task.custom-build-release-task.AzureAppConfiguration@6

@evertonlsouza
Please revert back to the short name
task: AzureAppConfiguration@6

@Tiberriver256 what error are you getting after rolling back to  AzureAppConfigurationPush@3 ?

@jimmyca15, It started working the way it was before.
AzureAppConfiguration@6

@Tiberriver256
We have updated the guidance here to reflect this. Version 10 had to be removed to restore the functionality of previous versions.

@evertonlsouza
Thank you for confirming.

Latest Versions
AzureAppConfiguration: 8
AzureAppConfigurationPush: 7
@MattJeanes

@rwonepipeline
What version were you using previously?

we were using AzureAppConfigurationPush: 3

@MaryanneNjeri We are getting this error with AzureAppConfigurationPush@3:

@MaryanneNjeri After updating to AzureAppConfigurationPush: 7, we get Key cannot start with the reserved prefix for feature flags error

@rwonepipeline  a breaking change was introduced in version 5, please see here where Settings with feature flag prefix and content type will fail to import

@Tiberriver256 are you referencing the task as AzureAppConfigurationPush@3 ? From the errors it also seems that version 10 of the push task is still being refernced

@MaryanneNjeri Thanks,  Seems like we have to make too many changes at least from the content part.
is it possible to use older version say zureAppConfigurationPush@3. from marketplace, we can only download the latest version of that particular task

@Tiberriver256
@rwonepipeline
Did you happen to uninstall and re-install the AzureAppConfiguration market place extension?

@Tiberriver256 @rwonepipeline
Did you happen to uninstall and re-install the AzureAppConfiguration market place extension?

unfortunately yes, When I saw V10 to be used :D

@Tiberriver256 @rwonepipeline
Did you happen to uninstall and re-install the AzureAppConfiguration market place extension?

We did unfortunately as a troubleshooting step early on 🥲

We just spent the day moving to 10 to find it removed? This is utterly disruptive and causing unnecessary costs.

In the first place you released breaking change without any notification, then we spent hours changing all pipelines to @10 and now we come back 4 hours later and you remove @10 and we have to revert back to either @6 or @8...

Couldn't the last working version have been promoted into v10 and all of this avoided?

I usually try to stay calm and just deal with stuff in a rational way. This comment won't be.
As if waking up today with about 50 broken pipelines wasn't bad enough, I spent my whole morning upgrading this stuff to v10 to make it working again.

You cost us a couple of thousand $$$ today, Congrats.

On behalf of the App Configuration team, I apologize for the disruption that this issue has caused. I understand that we provided a work around, and then the work around became non-operable resulting in additional disruption and lost time. We do not take this issue lightly. We strive to be a resilient, reliable configuration solution for developers and that includes being resilient and reliable in dev ops scenarios. We cannot make up for the lost hours caused by this particular issue, but we can ensure that every bit of attention possible is being put in place to ensure that this is never repeated. This wasn't the result of a planned breaking change. Details on the root cause will follow.
@cheesi @davenicoll @holyyyns @Werner-Swart-83 @rwonepipeline @Tiberriver256 @MattJeanes @concreteutopia @bbrandt @lettucemode @adrian-patt @ez5504 @dawidholka
&Everyone else impacted

Root Cause
Prior to September 4th, the AzureAppConfiguration (AAC) and AzureAppConfigurationPush (AACP) tasks were available as Azure Dev Ops market place extensions. Their latest versions were v8 and v7 respectively. On September 4th 7:38 PM UTC, The App Configuration team released new versions of these tasks, v10, as built-in tasks in Azure Dev Ops, rather than market place extensions. Upon release, it was discovered that v10 was working, yet all previous versions of the task were no longer operable. A testing deficiency for the migration to built-in tasks caused this issue to go undetected before release. At this point, an incorrect initial determination was made that removing the newly released v10 was not an option to restore the functionality of previous versions. The App Configuration team immediately began working to restore the operability of previous task versions, e.g. AAC v8 and below and AACP v7 and below. As the team worked to restore previous versions of the task, it was recommended to migrate to v10 to enable tasks to run successfully. During this effort it was determined that restoring the functionality of previous task versions would take longer than originally estimated, and additionally it was verified that removing v10 would restore previous versions contrary to previous conclusions. To avoid further impact on those who were unable to execute the work around, the team removed v10 of the AAC and AACP tasks. The removal of v10 completed on September 5th 2:40 PM UTC. This resulted in any pipelines that were updated to use the workaround to become inoperable. In order to avoid further disruption, v10 was not re-released in any capacity.

Root Cause
Prior to September 4th, the AzureAppConfiguration (AAC) and AzureAppConfigurationPush (AACP) tasks were available as Azure Dev Ops market place extensions. Their latest versions were v8 and v7 respectively. On September 4th 7:38 PM UTC, The App Configuration team released new versions of these tasks, v10, as built-in tasks in Azure Dev Ops, rather than market place extensions. Upon release, it was discovered that v10 was working, yet all previous versions of the task were no longer operable. A testing deficiency for the migration to built-in tasks caused this issue to go undetected before release. At this point, an incorrect initial determination was made that removing the newly released v10 was not an option to restore the functionality of previous versions. The App Configuration team immediately began working to restore the operability of previous task versions, e.g. AAC v8 and below and AACP v7 and below. As the team worked to restore previous versions of the task, it was recommended to migrate to v10 to enable tasks to run successfully. During this effort it was determined that restoring the functionality of previous task versions would take longer than originally estimated, and additionally it was verified that removing v10 would restore previous versions contrary to previous conclusions. To avoid further impact on those who were unable to execute the work around, the team removed v10 of the AAC and AACP tasks. The removal of v10 completed on September 5th 2:40 PM UTC. This resulted in any pipelines that were updated to use the workaround to become inoperable. In order to avoid further disruption, v10 was not re-released in any capacity.

Hello Crowdstrike...

I would also like to extend my sincere apologies to everyone affected by the recent disruption. We understand the inconvenience this has caused and deeply regret any impact it may have had on your operations.

Appreciate the team's efforts and transparency on this issue!
Are there any plans to re-release v10+ in the future? Or is that still being worked out?

@lettucemode

Are there any plans to re-release v10+ in the future? Or is that still being worked out?

Currently there are no plans to re-release v10+, though we are looking into having the task in-built

@MaryanneNjeri  @jimmyca15 this issue has returned with the v7 tasks


CI: Dont run test/build... instead only lint on PR's with .md files

.png, .pdf and some other file endings might be considered too.

We have since introduced a mechanism to only run linters, instead of the full testing pipeline, based on the commit message.


Use CITATION file from repository

~4 years ago there was a push to make finding the correct software citation easier by including a CITATION file in the repo: https://www.software.ac.uk/blog/2013-09-02-encouraging-citation-software-introducing-citation-files
E.g., we have on here: https://github.com/weecology/retriever/blob/master/CITATION
These don't appear to currently being used.
There does appear to be quite a lot of variation, e.g., here's one from a @ctb project: https://github.com/dib-lab/khmer/blob/master/CITATION
which maybe makes them difficult to use, but I thought I'd mention it. It might be possible to at least look for a bibtex citation inside the files.

And never mind. You are finding it already. Sorry for the noise. I was thrown off by it being call R CITATION FILE

Yeah that makes sense.  Have modified the "R CITATION" to just "CITATION" and added your blog post as a resource when describing them.  Thanks Ethan!


Convert cannot handle yaml conditions for improperly configured RulesBasedSampler

Versions

Refinery: 2.0.0

Steps to reproduce
Input
rules:
  Sampler: DeterministicSampler
  SampleRate: 1
  test: # E&S kibble rules (hence lowercase)
    Sampler: RulesBasedSampler
    rule:
      - name: test
        condition:
          field: service.name
          operator: =
          value: test

expected output:
rules:
    RulesVersion: 2
    Samplers:
        __default__:
            DeterministicSampler:
                SampleRate: 1
        test:
            RulesBasedSampler:
                Rules:
                    - Name: test
                      Conditions:
                        - Field: service.name
                          Operator: =
                          Value: test

actual output:
panic: readV1RulesIntoV2Sampler unable to unmarshal config: json: cannot unmarshal object into Go struct field RulesBasedSamplerRule.rule.condition of type []*config.RulesBasedSamplerCondition

goroutine 1 [running]:
main.convertRulesToNewConfig(0x102837f20?)
        /Users/tylerhelmuth/projects/honeycomb/refinery/tools/convert/ruleconvert.go:165 +0x25c
main.ConvertHelm(0x1400000e2e8, {0x1028743c8?, 0x14000010060})
        /Users/tylerhelmuth/projects/honeycomb/refinery/tools/convert/main.go:346 +0x55c
main.main()
        /Users/tylerhelmuth/projects/honeycomb/refinery/tools/convert/main.go:216 +0x93c

Process finished with the exit code 2

Additional context
It seems the issue is because the old Refinery could handle converting from
Conditions:
  Field: service.name
  Operator: =
  Value: test

to a list of conditions even tho that is not how a list is defined in refinery.  When converting helm the convert tool expects proper yaml so when it sees the above configuration it cannot unmarshal it as expected.
As a workaround
Conditions:
  - Field: service.name
    Operator: =
    Value: test

is converted correctly.

This is caused by bad input yaml.  The real fix is to not have improver yaml.


How to get export of .gdoc/.gslides in .pdf?

In iOS sdk we have method for this: https://developers.google.com/drive/ios/devguide/files
Some files in Google Drive are not directly downloadable. Google Docs, Sheets, and Slides must be converted into a portable format. These files can be downloaded using the export URL. For example, to export a document as a PDF:
NSString *url = [NSString stringWithFormat:@"https://www.googleapis.com/drive/v3/files/%@/export?alt=media&mimeType=application/pdf",
                          file.identifier]

I have found only this solution: http://stackoverflow.com/questions/32975533/google-drive-import-google-docs
but it's looks like a "hack". Can you add support for this, or point how I can do it in better way?
Thank you.


Change telegram chat to one controlled by us

For context: there have always been 2 Telegram groups, but one seems to be getting out-of-hand, so this changes the recommended Telegram group to one that is more Monero-centric.


How to get Request in function map?

var funcs = template.FuncMap{
	"formatDate": func(date time.Time) string {
		return date.Format("2006/01/02 03:04pm")
	},
	"yield": func() string { return "" },
}

ab.Layout = template.Must(template.New("layout").Funcs(funcs).Parse(string(b)))

Like this one, How i can get request in function map?
I would like to do things like this:
var funcs = template.FuncMap{
	"aHelperNeedRequest": func(r *http.Request) string {
		return ""
	},
}

This isn't actually a supported use case right now in Authboss. We have very little data available to the views and it was somewhat intentional. We're open for pull requests but have no intention of adding this feature at this time.
An example of where the data for a view is being defined:
https://github.com/go-authboss/authboss/blob/586415a7db9d2b1538cd2c05ca2dbbce0ee9cc62/register/register.go#L128
An example of the data being consumed in the template:
https://github.com/go-authboss/authboss/blob/586415a7db9d2b1538cd2c05ca2dbbce0ee9cc62/internal/response/templates/register.html.tpl
Your templates will have access to the same data, but nothing more. Again though, I'm happy to consider code that would make this feature possible in a generic way.

I see. The case i face is like this:

We have function t in layout template anywhere. the t used to translation, e.g. {{ t "header.title" }}
And the t function need context (Request) to known which language's translation need to be display.

I think this case it is normal, right?

I agree. Context and i8n is something we'd be looking at for authboss 2.
Which as more of these kinds of requests come in, we're considering
spending time on more and more. As I said though I'd be happy to accept
code that makes this possible!
On May 13, 2016 12:04 AM, "binqin"<EMAIL_ADDRESS>wrote:

I see. The case i face is like this:

We have function t in layout template anywhere. the t used to
translation, e.g. {{ t "header.title" }}
And the t function need context (Request) to known which language's
translation need to be display.

I think this case it is normal, right?
—
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub
https://github.com/go-authboss/authboss/issues/84#issuecomment-218967176


sidebars: Update unread pills to handle zoom better.

This updates the unread pills in the left and right sidebar to look better at a wide range of zoom values. (It doesn't change their appearance at all.) It also refactors the CSS so that less code is duplicated between the multiple types of unread pill.

Updated!

Just updated this with a few minor improvements:

Made the span height and line-height match so the text stays centered
Made the height an even number of pixels (16px vs 15) so it scales better
Adjusted the top position of #global_filters .count so it's centered in the selection highlight

This works great, merged, thanks @maxnuss!


cleanvm: Run Ocata on Leap_42.3

recently built a 42.3 qcow2 in OBS Cloud:Images

I also have one from home:tbechtold:Images where I build the cleanvm images. Already copied to the machine and it seems to work.


pulumi convert from terraform does not support private terraform module registry.

Hello!

Vote on this issue by adding a 👍 reaction
If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

pulumi convert --from terraform should support modules stored in TF private registry.
Affected area/feature

@MitchellGerdisch I'm glad that I've found this issue. We're evaluating switch from TF to Pulumi in our organisation. Using converter I was getting error below. But as I see now - private modules are not currently supported.
[I] ➜ pulumi convert --from terraform --language yaml

error: <nil>: Error accessing remote module registry; Failed to retrieve available versions for app.terraform.io/xxx/module-hello-cloud/aws: error looking up module versions: 401 Unauthorized
error: conversion failed