[bug] Delegator workflow verification - should it verify builder ID tag?

The delegator workflow causes two levels of indirection:
TRW -> Delegator workflows
When scoping verification for delegator workflows, I need to do some internal logic changes and checks:

When the delegator workflow signed the certificate, the provenance BuilderID() can be anything - it does not have to match the certificate.
Verify that the delegator workflow was called at a trusted ref (tag), EXCEPT in the example-package and presubmit repository.
The --builder-id MUST be specified, and MUST match the provenance's BuilderID() (the TRW)
Verify that the TRW was called at a trusted ref (tag), EXCEPT in same repository as the TRW

Notice that the check in 4 is generalized - instead of pre-submit in the slsa-github-generator/slsa-framework exception we have the builder's source repository. This allows the TRW owner to create pre-submit workflows against TRW@main in their repositories to test.
WDYT @ianlewis @laurentsimon ?

I'm drafting the verification changes here: https://github.com/slsa-framework/slsa-verifier/compare/main...asraa:slsa-verifier:delegator-verification?expand=1, but I require some fixes (https://github.com/slsa-framework/slsa-github-generator/pull/1619) to actually test this. Then I will add tests.
We have a slight chicken and egg problem about the tag verification tests using delegator@tag and trw@(tag/main) (this has existed for all builders...)

Verify that the TRW was called at a trusted ref (tag), EXCEPT in same repository as the TRW

In pre-submit there is no provenance to verify, so do we need this special case? Do we expect to give users an Go API for their pre-submits?

We have a slight chicken and egg problem about the tag verification tests using delegator@tag and trw@(tag/main) (this has existed for all builders...)

What do you mean?
Changes 1-3  LGTM.

In pre-submit there is no provenance to verify, so do we need this special case? Do we expect to give users an Go API for their pre-submits?

Sorry, i did not mean pre-submit event. I meant a workflow_dispatch in the TRW workflow. Otherwise, how will the TRW test it's workflow before distributing it and tagging it for clients?

What do you mean?

I can only test the e2e repo exception with using a tagged builder in verifier tests before we tag one for release.

Got it, that makes sense. There may be use cases where the TRW repo wants to call their own TRW to cut a release too (using a previously-tagged release), so maybe we need a way for the caller to indicate whether it was an e2e test? Something like SLSA_VERIFIER_XXX?

There may be use cases where the TRW repo wants to call their own TRW to cut a release too

Yes... I was thinking there might a case like that. Yes, maybe something that is blatantly labelled insecure like "SLSA_VERIFIER_INSECURE_ALLOW_MAIN` that will allow main ref, but again ONLY when the source repository is the same location as the builder.

SG. Could also verify whether it's running in a GitHub workflow (by checking env variables from GitHub like GITHUB_ENV and CI) which would indicate a test.

That would restrict them from only being able to test slsa-verifier inside the workflow. It's a little restrictive but maybe that's a good thing! That ensures that someone doesnt download the provenance and use it elsewhere.

yeah. I think being restrictive still gives us the opportunity to remove the restriction in the future (if people really need this flexibility), but t the other way around would break folks.
I added a note in the doc issue https://github.com/slsa-framework/slsa-github-generator/issues/1574

How do you think we should handle this before we officially GA delegator? (All current TRW writers are calling @main). Is it possible to use release another 0.0.3 tag (which tags all builders, meanwhile we only care about delegator)

Other convo:

Make it clear that user needs to specify https://
Request full Builder ID until someone asks about pinning trust on just the org or repo


Ergosoft.ErgoFAKT_V5 version <IP_ADDRESS>94

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.0 schema?

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

Microsoft Reviewers: Open in CodeFlow

Hello,
I am confused about the "Contributor License Agreement" I have to sign.
The product we want to provide by winget (ErgoFAKT V5) is a commercial product and we do not want to licence it to Microsoft.
Can you please clarify?
Thx
Robert Holler

cc @robongit: Please read https://github.com/microsoft/winget-pkgs/discussions/14084#discussioncomment-794372.

Sorry, never worked with GitHub.
Find no way to rename the version folder :-|
Can you please guide me in the right direction?
Thx
Original Message        processed by David.InfoCenter
Subject: Re: [microsoft/winget-pkgs] Ergosoft.ErgoFAKT_V5 version <IP_ADDRESS>94 (#23902) (06-Aug-2021 16:33)
From:    ItzLevvie @.>
To:      @.
@ItzLevvie requested changes on this pull request.
You'll have to update the version folder as well using the web or client version of GitHub.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
@ItzLevvie requested changes on this pull request.
You'll have to update the version folder as well using the web or client version of GitHub.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
ht__tps://github.com/microsoft/winget-pkgs/pull/23902#pullrequestreview-724420783


Add CONTRIBUTING.md and PROJECT_ARCHITECTURE.md

Fix for #3
Add CONTRIBUTING.md and PROJECT_ARCHITECTURE.md

We should also mention that any non-code type of pull requests are welcome, such as, designs, copywriting, translations and documentation edits.
There is an error with "enhanchement" -> enhancement

A topic for discussion:

Shouldn't we also ask that any pull request should also have respective tests.


Add subscribe/unsubscribe functions to websocket.

I think it would be great if the websocket client allowed changing what channels are subscribed without losing the connection.
How does this proposed API look?

To summarize, this patch adds the following functions to WebsocketClient:

subscribeProduct(..products)
subscribeChannel(...channels)
unsubscribeProduct(...products)
unsubscribeChannel(...channels)

This allows the specified subscriptions to be changed dynamically.  The code maintains the set of channels and products such that for each channel, one is always subscribed to the same set of products as all other channels.

Thanks for the review.  I'll try to find the time to add all your suggestions and some tests.

I've changed all the mentioned items, written a test for each new API function, and squashed it into one commit.

Good work @fuzzyTew. I gave it another quick look, and things look much better (especially the additional tests). Thank you. Let's see what @fb55 thinks about these changes.
(I'm good with merging, but still waiting on collaborator/write access to the repository)

@fuzzyTew Would you also please add a short snippet about these new Websocket usage patterns to the relevant section in the README?
https://github.com/coinbase/gdax-node#websocket-client


Create package.json

Fixes #148
This PR will allow publishing the repository to npm registry.
Details about different fields in the package.json file can be found here: https://docs.npmjs.com/files/package.json
After merging this PR

make an account on npmjs.org
publish the package following the official guide: https://docs.npmjs.com/getting-started/publishing-npm-packages

Just waiting on an account at NPM.

This may take up to 4 weeks - as I'm trying to publish under the @edent name there. It is currently in use, so I'm seeing if it can be transferred. https://www.npmjs.com/policies/disputes

OK - here we go!


RelPositionalEncoding implementation has some bug？

Describe the bug
The relposencoding implementation is same with abs pos encoding.
Implemention now

  self.pe[:, 0::2] = torch.sin(position * div_term)
  self.pe[:, 1::2] = torch.cos(position * div_term)

Expected behavior
The relposencoding in conformer descriped in paper should be:

  pe_positive[:, 0::2] = torch.sin(position * div_term)
  pe_positive[:, 1::2] = torch.cos(position * div_term)
  pe_negative[:, 0::2] = torch.sin(-1 * position * div_term)
  pe_negative[:, 1::2] = torch.cos(-1 * position * div_term)
  pe = torch.cat([pe_positive, pe_negative], dim=1)

Yes, it's not exactly the same to the paper, we just use it.

I've experimented and got better wer with the standard relative positional encoding. 1% improvement.

I've experimented and got better wer with the standard relative positional encoding. 1% improvement.

dynamic chunk training or non streamming？

I've experimented and got better wer with the standard relative positional encoding. 1% improvement.

dynamic chunk training or non streamming？
in origin transformer paper pos emb can be like pe = torch.cat([pe_positive, pe_negative], dim=1)

Non streaming with business data in real scenarios, not open source data.

Will hold this PR for anyone else who has encountered and interested in the same question.


Remove parameterless and internal ModelBuilder constructors

Per API review decisions, a parameterless ModelBuilder constructor that creates a ModelBuilder without conventions would be a pit of failure. Therefore, this constructor is removed and now a convention set must always be passed, which may be empty. Also verified it is pretty easy to create a ModelBuilderFactory for a given provider and get a convention builder from that.

:shipit:


Support for AFNetworking 3

Eventually, people will be migrating to AFNetworking 3 for their apps, leading to a conflict with the CDA SDK, especially when using CocoaPods. We should start a 2.0 branch which moves away from AFNetworking 2.x for midterm evolution. Another option would be to move people over to contentful.swift.

Main obstacle going AFNetworking 3.0 is that the NSURLConnection based API is gone, so is support for iOS 6.

@neonichu Any thoughts on this migration or contentful.swift supporting CoreData persistence?  We have other dependancies that have started requiring AFNetworking 3, so we are stuck using older versions and missing out on fixes.

I'd be in favor of moving to AFNetworking ~> 3.0.  NSURLConnection is getting a lot of deprecation too so I believe that to be a weighting factor.  Apple reports less than 5% of devices are using iOS < 8.0 too.  If you do migrate, one feature request would be to expose the AFSecurityPolicy through the client (or configuration) so we can at least pin to the root CA.  We'd be happy to help out if needed.  It would solve some issues for us too.  Also on the note about moving people to contentful.swift, Swift 3.0 will also have code breaking changes.

Yah, this should definitely happen at some point. There's an unfinished branch at https://github.com/contentful/contentful.objc/tree/2.0-dev which is now quite out of date in regards to master.
Regarding contentful.swift, there is https://github.com/contentful/contentful-persistence.swift now, albeit it is still a bit in its early stages.

Brought the branch up to date with current master, but the full test suite isn't running, yet. However, it should be fine for testing it if you urgently need to switch to AFNetworking 3:
pod 'ContentfulDeliveryAPI', :git => 'https://github.com/contentful/contentful.objc', :branch => '2.0-dev'

Awesome!  Thanks @neonichu.  Is there an open issue for setting the security policy for pinning to the root CA as an option?  You're API is put together well in that it could be exposed easily, maybe as part of the CDAConfiguration.  Would you see any concerns in doing that?

@mrrobby don't see any concerns, could you open an issue for it? Thanks 👍

You got it.  See #53

Hello neonichu,
Please let me know asap that the stable branch having support for AFNetworking 3.0 in objective c is exist or not.
If exist than please provide me the pod setup path as i am using this path (pod 'ContentfulDeliveryAPI', :git => 'https://github.com/contentful/contentful.objc', :branch => '2.0-dev') and it giving error while installing.
Its urgent.

@CrazyPro007 could you please share which errors you're seeing?
This branch should be stable, there are just some smaller issues with the test suite which haven't been resolved, yet and those block merging this to master.

@CrazyPro007, what version of CocoaPods are you running?  The lock file is showing an older version so if you are on 1.0, maybe try switching to 0.38.2 and try again.

@neonichu i am using cocoapods version 1.0 and troubling with  following errors.
[!] Error installing ContentfulDeliveryAPI
[!] /usr/bin/git clone https://github.com/contentful/	contentful.objc /var/folders/m6/fp4xfrdx5mx7y0gryyw_ryym0000gn/T/d20160808-22421-17nowla --template= --single-branch --depth 1 --branch 2.0-dev
Cloning into '/var/folders/m6/fp4xfrdx5mx7y0gryyw_ryym0000gn/T/d20160808-22421-17nowla'...
fatal: unable to access 'https://github.com/contentful/	contentful.objc/': The requested URL returned error: 400

@CrazyPro007 that error looks like there is a problem with your connection to GitHub rather than with the branch — are you able to successfully clone other branches of the same repo?

@neonichu
I am successfully able to clone the other branches from github and even your branch #pod 'ContentfulDeliveryAPI'

@CrazyPro007 can you share your Podfile please, I'm unfortunately not able to reproduce this

@neonichu
Pod file unable to upload so i am uploading the pdf file.
Podfile.pdf

Looks like there are some accidental extra characters in the repo URL, please try this Podfile instead:
target 'Contentful' do
  pod 'ContentfulDeliveryAPI', :git => 'https://github.com/contentful/contentful.objc', :branch => '2.0-dev'

target 'ContentfulTests' do
  inherit! :search_paths
  # Pods for testing
end

target 'ContentfulUITests' do
  inherit! :search_paths
  # Pods for testing
end

end

Thanks @neonichu
It working fine now.

Support for AFNetworking 3 has been moved to a new branch: #67


Trying to add new character sprites to non-mod folder doesn't work

Describe your problem here.
how do you add new sprites? is there code im missing i need to edit?
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
yes, but only clientprefs.hx

you have to go in assets\shared\images\characters for the image and for json file go to assets\preload\characters

it work ?

it just spits out this error attempting to load it
its named correctly in the json

@VanessaMae1087 what source file do you change

still having this issue
recompiling doesnt change anything, files are in the right places...

re-exporting the sprite sheet fixed it for some reason but at least it works????


Examples of how to interact with new/pre-existing tables with Hash and Sort keys

It would be nice to have some more examples showing of this behavior :smile:

There's nothing particular to the examples that requires them to have new tables.
The main reason for creating and dropping tables as part of the examples is that they're all executed as test cases as part of the build pipeline.
If there's anything that's still not clear, let me know and I'll try and elaborate.

I'm a bit confused as to how to use a table that has a hash and a sort key and one that has a GSI index. Can you please elaborate on this?
Thank you very much, this is an awesome library

The Table scaladoc has an example showing querying from a GSI.
While the Scanamo scaladoc has an example of getting with a hash and range key. I should probably move the latter over to the Table docs now, as that's the main approach I'm suggesting.

Thanks! That helps a lot :-)

Oops my fat fingers

I took a look at the Table example you provided. To make it more clearer that you are using a GSI, it would be great if you could state in a comment as to how the table is configured (primary key, GSI hash and sort key). What do you think?

Yes, I'll try and add something to the README (unless someone else gets round to a PR first).
I need to take a look at how to structure it better at some point too.

Sounds good. I'm also working on a full end to end example with Play framework to get a simple REST API hooked into DynamoDB via Scanamo. You can find it here
https://github.com/referentiallytransparent/play-framework-validation-example/tree/feature/crud/app/services/data/dynamodb
Still have to clean it up some more

Does https://github.com/guardian/scanamo/blob/00e4d4530acba3709e4a67c9010ea62874aaf3b0/README.md#using-indexes look like it explains things a bit more?

Absolutely, great job :+1:


change url backend on the frontendc

change url backend on the frontend

Solved on  the  PR Develop #116


[BUG]: Unused variable "X_CSI_POWERMAX_ENDPOINT" resulting in driver not to start in PowerMax

Bug Description
https://github.com/dell/csi-powermax/blob/3c84a94e38f7ab7185060e12ecab5149db1f4ead/samples/configmap/powermax-array-config.yaml#L22
This particular endpoint is not required, but without it driver is unable to start
Logs
https://github.com/dell/csi-powermax/blob/3c84a94e38f7ab7185060e12ecab5149db1f4ead/samples/configmap/powermax-array-config.yaml#L22

Two place needs update
ConfigMap
Documentation
Better approach is to change ConfigMap, remove the sample in documenation and give a link to the configmap from the documentation
Screenshots
No response
Additional Environment Information
No response
Steps to Reproduce
Refer to the configMap https://github.com/dell/csi-powermax/blob/3c84a94e38f7ab7185060e12ecab5149db1f4ead/samples/configmap/powermax-array-config.yaml#L22
Deploy without filling the variable, installation fails
Expected Behavior
This dependency should be removed completely
CSM Driver(s)
PowerMax
Installation Type
No response
Container Storage Modules Enabled
No response
Container Orchestrator
NA
Operating System
NA

@shanmydell not quite sure I understand the issue here. I don't see where the documentation says this value is optional -- do you want to add comments saying which values are mandatory? We could delete the file from documentation and link to it ilke you suggested, but I'm not sure what the existing issue is.

@ashleyvjoy @harishp8889 : Can you guys review this once if this variable is supposed to be there or not since it was added by your team? Thanks

@jooseppi-luna This variable is injected via config map, again why this is needed as a variable, we are asking the user to insert the same value again in multiple places

@harishp8889 is OOO.  @shanmydell Are these the expected changes?

The  X_CSI_POWERMAX_ENDPOINT variable in config-map should be marked as 'required'
Remove the sample in documenation and give a link to the above onfigmap from the documentation

@ashleyvjoy ; Required change is not to have that variable itself

Handled as part of https://github.com/dell/csm/issues/1570


How to use the scripts after make install?

I'm interested in using the book.o script, but I can't find any Rofi documentation related to using object files as plugins/scripts for Rofi. How does this work?

Nevermind, just realized they're not actually object files, they're executables.


Design Documentation

existing documentation covers how to use the application, what it helps with, how to customize its execution, etc.
need some documentation on how the system itself is constructed beyond the sections necessary to tweak how it runs.

not sufficiently complicated or looking for external devs


4.01 Cannot remove/disable placeholder when regex mask provided

Hi,
Just recently upgraded from v3 to v4 and I cannot disable the placeholder on inputs when a regex max is bound.
e.g: If I have a regex like this: "^(-|(0|([1-9]\d*)))$" then the input always has a placeholder with "-", even if I set it to an empty string.

@hunfatal ,
Try jitMasking: true option

@RobinHerbots  Wow, that was a quick answer. And it solved the issue, thanks!


Support Facility Sequencing within Facility Groups

Description
Currently, the Facilities app does not support sequencing or custom ordering of facilities within facility groups. This enhancement aims to introduce a feature that enables users to specify the order or sequence in which facilities appear within their respective facility groups.

A group detail page where users can also add custom sequence to a list of facilities.

This will be handled under #293 . Closing this ticket.


initial, metadata endpoint for json-stat2

The metadata endpoint now reads an output-format parameter which lets you choose between px-json and the new json-stat2.
The  json-stat2 is not complete, but cover the most common stuff.
To continue  testdata for codelists, hierachy and metaid should be added, but  this is perhaps better as another PR

Looks good 👍 but can you also include then links to both metadata formats in navigation, something like this<EMAIL_ADDRESS>
Ok, we'll do this as a seperate PR like we talked about :-)


Wishlist - Integration with Facebook messenger

Integration with Facebook messenger

https://docs.aws.amazon.com/lex/latest/dg/fb-bot-association.html

This is now integrated: https://github.com/arun-gupta/chatbot/commit/85d91a8528bc9c6d9e36be54b3ea573b9f883c29


Update dependency dts-bundle-generator to v8.1.2

This PR contains the following updates:

Package
Type
Update
Change

dts-bundle-generator
devDependencies
minor
8.0.1 -> 8.1.2

Release Notes

timocov/dts-bundle-generator (dts-bundle-generator)
v8.1.2: 8.1.2
Compare Source
Fixed

Something went wrong - value cannot be null (see #265 and #267)

v8.1.1: 8.1.1
Compare Source
Fixed

Stack overflow while handling re-exports with circular dependencies (see #264 and 4429eac)

v8.1.0: 8.1.0
Compare Source
Added

Added support for .mts and .cts extensions (see #204)
Fixed handling re-exports in dependencies (see #259)

Configuration
📅 Schedule: Branch creation - "before 4am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Self-Hosted Renovate Bot. Find all logs here.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: package.json
Command failed: make _bootstrap-renovate clean compile

  bundles/thunk_bundle.js  247.5kb

⚡ Done in 28ms

  dist/bundle.js  68.1kb

⚡ Done in 13ms
Error: Something went wrong - value cannot be null
make: *** [Makefile:198: compile] Error 1

Renovate Ignore Notification
Because you closed this PR without merging, Renovate will ignore this update (8.1.2). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.
If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.


Iteration Plan for June 2017

This plan captures our work in June. This is a 4 week iteration. We will ship early July. The main focus of this iteration is to continue pushing on the big rock item #396 "Multi-folder workspaces".
Endgame

June 26th: Code freeze for the endgame
June 30th: Endgame done

The endgame details for this iteration are tracked in TBD
Plan Items
Below is a summary of the top level plan items.
Legend of annotations:

Mark
Description

:runner:
work in progress

:hand:
blocked task

:muscle:
stretch goal for this iteration

:large_blue_circle:
more details required

:red_circle:
missing issue reference

Workbench

[ ] :runner: Multi-folder workspaces #28344 (feature request #396) @bpasero @tyriar @ team
[x] Improve window switching #25145 @bpasero
[ ] :runner: Finish emmet 2.0 support #27697 @ramya-rao-a
[ ] :runner: Finish Tasks v2.0 improvements #28235 @dbaeumer
[ ] :runner: :muscle: Allow users to manage custom sections in the explorer #27823 @sandy081

Editor

[ ] :runner: Improve indentation of lines #28658 @rebornix

Monaco Editor

[ ] :runner: New release of the Monaco Editor Microsoft/monaco-editor#467 milestone @alexandrudima

Accessibility

[ ] :runner: Improve accessibility of the Monaco editor See query. @alexandrudima
[ ] :muscle: Improve accessibility of the diff editor #17263 @alexandrudima
[x] Improve accessibility of the Tree/List widget #27900 @isidorn

Debug

[ ] :hand: Implement extension host debugging for inspector protocol Microsoft/vscode-node-debug2#4 @weinand @bpasero @roblourens
[x] :runner: Autodetect debug protocol for SIGUSR1 initiated debugging #25036 @roblourens @weinand
[x] Translation support for inspector protocol based debug adapters Microsoft/vscode-node-debug2#83 @roblourens
[ ] :runner::muscle: Show loaded scripts in a custom explorer section #28521 @weinand

Install/update

[ ] :large_blue_circle: Provide Windows 64-bit install (and migration from 32-bit) #507 @joaomoreno
[ ] Make update notification less invasive @joaomoreno @isidorn
[ ] :muscle: Improve update experience on Windows #26199 @joaomoreno, @isidorn

Integrated Terminal

[x] Support selecting and copy more than just the visible text in a terminal #9958 @tyriar
[x] Support find in the terminal output #15198 @Tyriar @rebornix

Languages
JavaScript/TypeScript

[x] Bundle TypeScript 2.4 #28056 @mjbvz
[x] Support TS 2.4 refactorings #25739 @mjbvz

Extensions
API

[ ] :runner: Finish Task Provider API #27575, #27577, #27582, #27587 @dbaeumer
[x] :runner: Debug: support a debug session terminated event #28234 @weinand
[x] Custom sections: support conditional visibility based on a context (when clause) #27823 @sandy081
[ ] :runner: DocumentContentProvider support to update document content #10547 @jrieken

Extension management

[ ] :runner: Add sections for installed and recommended sections to the extensions viewlet #28663 @sandy081

Extension Contributions

[ ] Go https://github.com/Microsoft/vscode-go/issues/959 @ramya-rao-a
[ ] Polish PHP language server https://github.com/felixfbecker/php-language-server/issues/404 @roblourens
[ ] Polish Git extension #28657 @rebornix
[ ] Polish Github extension #28631 @chrmarti

Engineering items

[ ] :runner: Investigate using snapshots for workbench.main.js to speed up startup #28492 @jrieken
[ ] :runner: Adopt Electron 1.7.2 #28582 @bpasero
[x] Adopt TS 2.4 #28643 @mjbvz
[ ] Investigate language packs for translations #29008 @dbaumer
[ ] Avoid process leakage of the extension host #15962 @alexandrudima
[x] :runner: Build definition for smoke test #27845 @michelkaporin
[ ] :runner: Smoke test build status indicator #28586 @michelkaporin
[ ] :runner: Revisit smoke test CSS selectors to mimic interactive user behaviour #29254 @michelkaporin
[ ] :runner: Improve issue tracking with automation #26223 @chrmarti
[ ] :muscle: Enable electron crash reporter for all processes #21944 @ramya-rao-a

Documentation

[x] :runner: Add recipe for Angular debugging weinand/vscode-recipes#1 @weinand

Deferred

:muscle: Support custom sections in other viewlets #28662 @sandy081
:muscle: :runner: Provide out-of-the-box color picker #28587 @michelkaporin

Hi, link to this issue is missing in wiki. Thanks!

@obrejla fixed :smiley:

I think this issue should be included in June milestone. :)


fix medical jobs not being fast at surgery + small cleanup

About the PR
wrong field name so it did nothing
added comments and moved damage stuff to shitmed folder
might add more later
Changelog
:cl:

tweak: Medical jobs are now much faster at surgery.

that feeling when knee surgery is tomorrow


Cache runtime images

Clear and concise description of the problem
Currently each time a domain is visited with an OG image generated by the package, it is rendered by the number of times the url is visited, which could have a negative effect on the server side.
Suggested solution
It would be nice to have an option to cache the images generated by the package, with a certain expiration time, etc. In this way it would be possible to better control the resources needed for image generation.
This affects more when using the browser strategy, and not the Satori strategy.
Alternative
None.
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

This is now supported in the latest beta. See the Caching documentation for more details.


Add option to block non-https requests.

This is for part of #460.
Added enforce_https flag to API. If true, middleware is added that
checks whether https is the url scheme or the value of
X_FORWARDED_PROTO header. If it is not, an exception is raised
that can be caught be a user provided error handler.

Oops left out new test file in commit. Just amended commit with it.

Over the past several months there has been a lot of community discussion around where add-ons AKA plugins should live. I think we are coming to a rough consensus that the core framework should be as lean as possible, but that for additional functionality that is quite common/important, we could create standalone "official" packages with repos under the GH falconry org. Each of those would have a project technical lead.
@paul291 With that in mind, what do you think about creating a package names something like "falcon-appsec" that could have this middleware, and perhaps other middleware over time, such as for input validation or whatever?

If someone wants to maintain this as a standalone package, please let me know.

Superseded by https://github.com/falconry/falcon-require-https/pull/5


docs: Commit discipline improvements.

At Greg's suggestion on a PR of mine, this PR brings in the very good copy from zulip-mobile admonishing against GitHub @-mentions in commit messages. The copy is introduced whole-cloth, and then modified a bit in a subsequent commit.
To help readers scan the Commit Discipline document, and to make it easier to reference specific sections, this PR also changes some previous pieces of copy marked as paragraphs and makes them appropriately leveled headings.

Screenshots and screen captures:
Original documentation

Copy without headings (before)
Copy with headings (after)

New section on @-mentions, from zulip-mobile docs

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

This section is kind of long; I think it might be useful to move the "Examples" section higher up if we're adding it:
https://zulip--25768.org.readthedocs.build/en/25768/contributing/commit-discipline.html#examples-of-good-commit-messages

This section is kind of long; I think it might be useful to move the "Examples" section higher up if we're adding it:

I think the one risk of that is that it could make the examples less visible. As is, if you skim to the end, you find examples. Given how short that section is (because its content is all in a couple of links), the examples probably stand out more there than they would if sandwiched between longer sections of prose.

Yeah OK let's leave doing something about the examples for a later PR -- I would like good examples to be more prominent, but probably we can do that separately as its own change. (I also don't know if those are the best examples to highlight, for example).

Thanks so much for the comments, everyone. I believe I've addressed all of them, apart form the example re-organization, etc., which I've made a note of to return to as a separate PR sometime this summer.

I think this is quite a bit longer than it should be given how often it comes up. We are already asking folks to digest a lot of info on this page. I'll take a stab at a shorter version.

How about #25784?

How about #25784?

That's some nice, tight writing, Alya! I wonder if maybe the admonition not to @-mention deserves some boldface or something--since the issue as I understand it is usually someone @-mentioning, rather than wondering how to credit others.

I don't carefully review commit messages, so I'm not sure what's common. I've see the credit question pop up, but haven't personally encountered stray @-mentions. @timabbott how often do those happen?

how often do those happen?

Here's the examples in zulip/zulip in the last two years:
dbe930394f7586c79808d6d60568fd2ef434957d
7a1ed9a4cba72b668a3cf8299fc648291f2320a7
15e871784725a817499e74119e57838487ec5186
fd0ce2802937bc64cc26c218db6effd5fc4dc8c2
db934be0646e3002287c72ba2154a904a4dc42b5
f1c61fbea19c45bb2ba53c3db72c1b5d4302032f
a96c61442027bf34d0eade3362aaf8dc0dfbd4d7
afe0b7df61ae7cb1a98d8d0783da482756a466e8
846200f36ece9dc38b687ff3af4aacc8a770b16d
1e2f15477567ccd665ebd3be299020523e384921
9418ae51fa8d5364f736be7939444f24f5645ec8
A search that finds those is:
git log --grep '(?<!\w)@\w+'
That search also finds some others that weren't intended as GitHub @-mentions but would be parsed as such, like the @all, @everyone, and @stream (but without backticks) in https://github.com/zulip/zulip/commit/738a676 and many other commits. The search is also inexact in that it finds cases where someone correctly escapes such things to avoid creating @-mentions.
IME it's fairly annoying when it happens — GitHub generates spam from it for a while. So it's worth doing some education to prevent.

Ooh, should we add a note to use backticks for @-mentions when not trying to refer to someone? Do these @-mentions affect someone only if they are a member of this project, or would they produce notifications for someone named @stream who hasn't interacted with zulip/zulip?

Closed in favor of https://github.com/zulip/zulip/pull/25784.


Version 2.0.4 is released

and fixes a regression introduced in 2.0.3, sorry :(

Great work!

I must say I'm absolutely impressed with DNSCrypt v2. Thank you very much for your great work!


OpenMemories-Tweak is disable in A6000

I just installed OpenMemories-Tweak, all good. However, when I navigate to Application List, OpenMemories-Tweak is disable, I am not able to select "Region" and all other tabs. My firmware is 3.2. Please help. Thanks.

You have to push the arrow up key once to access the tabs. Does this resolve your problem?

Working! Thank you very much 👍


ci: install CRDs chart for operator when needed

Elemental Operator chart has been split, so newer versions should install all charts.
Verification runs:

CLI-K3s-OBS_Dev
UI-K3s-OBS_Dev
UI-K3s-OBS_Stable

@ldevulder I saw verification runs are green, with your permission I am merging this PR. Thanks much for the quick solution 🙏🏽


[WIP] formula_installer: Don't check devtools if pouring

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[ ] Have you successfully run brew style with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

This should stop Homebrew from nagging users about their outdated Xcode installation during bottle-only installs. I'll be able to test it locally in a few days (my mac is currently packed away).
Some notes:

This fixes the current behavior by moving the development tools check out of perform_preinstall_checks and into FormulaInstaller#install. This should be fine, although it does cause us to run the check N + 1 times for 1 formula and  N dependencies.
Some users may prefer this behavior, but it may not be beneficial in the long term: users should be nagged about the presence of unsupported Xcode installs, as doing so lessens the amount of weird setup triaging we have to do. Warning the user instead of totally failing the install might be a workable middle ground.

We may also be able to skip the check if it's bottle unneeded.

This should be good to go, pinging @ilovezfs and @MikeMcQuaid for final comments (if any).

Thanks @woodruffw! 🏆


disable animation

hi, how can I completely disable sliding animation. I want just a simple click to go sub menus.

When calling .slinky(), you can set the speed to 0
$('.menu').slinky({
  speed: 0
})

nice, but I also edited the code and disabled move(). I think your solution was simpler.
Thanks


Keep up with latest rust nightly by renaming std::io -> std::old_io

Relevant discussion: http://internals.rust-lang.org/t/psa-io-old-io/1403

Thanks!

Just released 0.2.12 with this fix!


Support arrays in JSONPath keys

The PR adds support for json arrays in JSONPath keys and fixes the bug with root array and nested arrays in the root array not being masked.
The performance is expected to decrease as now the masker checks every array element if it needs to be masked. The check entails traversing the trie.
The optimization of keeping a trie node of the parent segment on the jsonpath dequeue is not yet implemented in this PR. I will implement it in the next PR.

A small follow up: I made isInArray check to be the last operand in every "and" if statements in the track method and the benchmarks seem to report way smaller performance degradation.

@donavdey I'm done messing with your PR :)


Updated for zap 1.0.0-rc1

Thanks for your contribution. Can you please make those 2 small changes:

Change commit message to present tense: Update for zap 1.0.0-rc1
Fix README example according to new import path and change logger.Zap to be a pointer.

Thanks!


Authorization header not included

The issue I am facing is Eventhough I have send the Bearer token in the requestOptions , it takes the value the first time but if the page is refreshed the Bearer token is not present in header.
requestOptions: {
          auth: () => {
            return 'Bearer xxxxx';
          },
        },

This is the console log I get back , the first getAuthorisation gets the bearer from the request option but then after refresh nth.

First img as soon as viewer load and the second when refreshed

I face the same issue how did you solve it? :smile:


Applying batch normalization to a non-convolutional layer fails due to restriction of input to rank 4

Starting from this top answer of stackoverflow, I tried to make batch normalization work for a fully connected layer. This is the relevant part of the code:
            if self.convolutional:
              mean, variance = tf.nn.moments(x, [0, 1, 2])
            else:
              mean, variance = tf.nn.moments(x, [0])
            assign_mean = self.mean.assign(mean)
            assign_variance = self.variance.assign(variance)
            with tf.control_dependencies([assign_mean, assign_variance]):
                return tf.nn.batch_norm_with_global_normalization(
                    x, mean, variance, self.beta, self.gamma, self.epsilon,
                    scale_after_normalization=self.scale_after_normalization)

The call to tf.nn.batch_norm_with_global_normalization fails however:
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/ops/gen_nn_ops.py", line 104, in batch_norm_with_global_normalization
    name=name)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/ops/op_def_library.py", line 659, in apply_op
    op_def=op_def)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/framework/ops.py", line 1896, in create_op
    set_shapes_for_outputs(ret)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/framework/ops.py", line 1524, in set_shapes_for_outputs
    shapes = shape_func(op)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/ops/nn_ops.py", line 313, in _BatchNormShape
    input_shape = op.inputs[0].get_shape().with_rank(4)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/framework/tensor_shape.py", line 614, in with_rank
    return self.merge_with(unknown_shape(ndims=rank))
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/framework/tensor_shape.py", line 542, in merge_with
    self.assert_same_rank(other)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/framework/tensor_shape.py", line 585, in assert_same_rank
    "Shapes %s and %s must have the same rank" % (self, other))
ValueError: Shapes (64, 512) and (?, ?, ?, ?) must have the same rank

since, as far as I can tell, the input is constraint to have rank 4 in in nn_ops.py. Is this really a necessary constraint?

As currently written, the op expects inputs of 4 dimensions.  https://github.com/tensorflow/tensorflow/blob/9c3043ff3bf31a6a81810b4ce9e87ef936f1f529/tensorflow/core/kernels/batch_norm_op.h
But it doesn't seem to need to -- it just flattens everything but the last dimension anyway.  We would need to update the kernels and then the shape function, but it seems possible.
@sherrym, @shlens in case they want to comment.

My workaround for now is to just reshape my tensor to [-1, 1, 1, depth] (with depth the number of outgoing connections of my fully connected layer). But it would be nice to have this built in.

Many ops still have historical and/or arbitrary rank restrictions. Wherever knowledge of the rank is not needed, they should be generalized.

Note that batch normalization is a different operation depending on whether the layer is convolutional or not: when using it on a convolutional layer, you can aggregate sufficient statistics across patches. Not so when the layer is fully connected. Reshaping to [-1, 1, 1, depth] is the correct thing to do though, and we should probably just do that.

We'd be happy to accept PRs if anyone wants to generalize batch normalization to arbitrary rank.

This is obsolete. nn.batch_norm_with_global_normalization has been replaced by nn.batch_normalization which accepts arbitrary geometries.


GitHub workflow release

Description
Added GitHub Workflow Action to trigger a Release.
Testing
https://github.com/unskript/Awesome-CloudOps-Automation/releases
Checklist:

[ ] My changes generate no new warnings.
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] Any dependent changes have been merged and published.

Documentation
Make sure that you have documented corresponding changes in this repository.

@jayasimha-raghavan-unskript need a readme internally to trigger release, so put that in confluence


playvideo not working

i´m using vue3-youtube, i load a playlist properly but video not start playing neither using autoplay nor using playvideo
i load playlist in this object
const variables = ref({
controls: 0,
rel: 0,
playlist: ""
})
i include this code
<YouTube  width="100%" height="100%" :mute="true"
:vars="variables" @ready="onReady" ref="youtube" >

and if i click play everything works fine and playlist is played, only problem is start to play without click
any idea why is this happening?

onReady() {
console.log("ready to play");
this.$refs.youtube.playVideo();
//this.$refs.youtube.seekTo(20, true);
//this.$refs.youtube.playVideoAt(1);
//this.$refs.youtube.playVideo();
},
all checked comands works only playvideo is not working and playvideoat goes to indicate video but not starting

more infor, i checked statechange and it goes to -1, 3 and back to -1


Delete Message

I think there should be a delete feature for individual messages so that user can delete the message they don't want. It should be a deletion from database or just from the client side that's the question !!
Suggestions Open !! 😄

I think it should soft deleted the message from the DB along with the key isDeleted so if use want to to recover their messages so it can easily be done.

@saqlain11 great !!


Brooklyn Gateway Packet Capture feature

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

Automation for azure-sdk-for-python

Can one of the admins verify this patch?

Automation for azure-sdk-for-go

@pilor @KrisBash could you please review this PR?

Mirror changes from https://github.com/Azure/azure-rest-api-specs/pull/7179. Can't really cherry pick them since ADO configs were refactored in master branch. Before merging network branch back into master I'll rebase it and remove this commit


Add MinkPantherDriver support

MinkPantherDriver is currently under namespace robertfausk/MinkPantherDriver.
For installation you will need to composer require --dev robertfausk/MinkPantherDriver or look at robertfausk/MinkPantherDriver.

As this is an unofficial driver, I think the factory should be provided by your own Behat extension. The registration of driver factories is an extension point of the MinkExtension. See https://github.com/Behat/Symfony2Extension/blob/31258ea704144c2cd55db1ce58de000c5d59a77b/src/Behat/Symfony2Extension/ServiceContainer/Symfony2Extension.php#L47-L55 for an example.

Ok, I‘ll have a look at writing my own extension.
Another option:
What do think of making MinkPantherDriver an „official“ driver under behat namespace?
Maybe @Lctrs is also willing to help as a maintainer?!? At least he offered joining forces: https://github.com/robertfausk/MinkPantherDriver/issues/1


refactor(samples): use env variable

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[X] Make sure to open an issue as a bug/issue before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[X] Ensure the tests and linter pass
[X] Code coverage does not decrease (if any source code was changed)
[X] Appropriate docs were updated (if necessary)

unblocked by #344


inconsistencies in taxon constraints on cilia terms

I was just annotating Panther family PTHR10779 (DYNEIN LIGHT CHAIN ROADBLOCK) in PAINT and propagated some terms specific to cilia and ciliary movement. For some terms PAINT marked a loss for fungal taxa, but it marked the losses for the three different ciliary terms in different places, or not at all, so I think we need to check if the taxon constraints are done correctly.
Relevant fungal species in the family:

two Ascomycota species
-- Neurospora crassa
-- Phaeospaeria nodorum
two Basidiomycota species
-- Ustilago maydis
-- Puccinia graminis (3 sequences)

GO Terms
outer dynein arm (GO:0036157)

blocked for the two Ascomycota species, but not for the two Basidiomycota species

cilium movement (GO:0003341)

not blocked at all, so this term is propagated to the the two Ascomycota species as well as to the Basidiomycota species. I thought Ascomycota had lost cilia entirely, so this seems like it might be wrong.

cilium movement involved in cell motility (GO:0060294)

blocked for both the Ascomycota and the Basidiomycota species

@ukemi - I'll need help to know how to check the taxon constraints

Added never_in_taxon constraints to term "cilium movement" to match the constraints present on "cilium assembly" since organisms that don't assembly cilia can never have "cilium movement".
These are new and pre-existing taxon constraints on the term "cilium movement" now.
+relationship: never_in_taxon NCBITaxon:3176
+relationship: never_in_taxon NCBITaxon:3312
+relationship: never_in_taxon NCBITaxon:3378
+relationship: never_in_taxon NCBITaxon:3398 ! Magnoliophyta
+relationship: never_in_taxon NCBITaxon:4890 ! Ascomycota
+relationship: never_in_taxon NCBITaxon:5782
relationship: only_in_taxon NCBITaxon:2759 {id="GOTAX:0010017"} ! Eukaryota

Do we encode this dependency? If we did we could automatically propagate TCs. Would also be useful for phenotype inference.

I agree that it would be nice if "cilium movement" could inherit the taxon constraints from "cilium assembly", but I don't currently see any kind of relationship between "cilium movement" and "cilium assembly".
Biologically, "cilium movement" depends on or requires "cilium assembly", i.e. you can't have any ciliary movement if you don't have a cilium at all. Do we use any relationships in GO to encode that type of relationship?


replaceWithChannel:channel:error method in ZZDataChannel.m fails in Swift 3

ivar _allData is declared as NSData and is being cast to NSMutableData in this method in order to call setData on it. This operation fails at runtime in Swift 3 with the error: [Foundation._SwiftNSData setData:]: unrecognized selector sent to instance.
The solution appears to be to declare _allData as NSMutableData instead, which is what it should have probably been declared to begin with.

I admit the internal ZZDataChannel API isn't ideal. It does double duty initialised with NSData or NSMutableData and so sometimes gets into an inconsistent state as you've noticed.
We should have a ZZDataChannel and a ZZMutableDataChannel instead -- the ZZDataChannel can throw errors for inappropriate write operations. Then ZZArchive could be initialised with NSMutableData as an alternative, which leads to the creation of a ZZMutableDataChannel.
The write operations that should result in errors are temporaryChannel:, replaceWithChannel:error:, removeAsTemporary and newOutput:.
Anyone interested in working on a fix? I'll leave this open for discussion for a week or two.


Minor fix for markdown (was missing close for code block)

This has been fixed in https://github.com/localForage/localForage/commit/57c79652db0794dc11ba435d92b8bd54b832ca8e


Pulsing current draw

I just set up my reload pro from the original kickstarter today. I downloaded the latest firmware and installed the fankit. First time powering on the screen flashed and then went blank but after re-seating the ribbon cable that part worked fine.
The main problem that im seeing is a continuous pulsing of current of the reload pro instead of a steady current draw. My setup is as follows:
-Reload Pro running Reload Pro v1.9.cyacd
-9V battery connected to the red and black leads. 8.17V with no load
-20mA selected as the current setpoint.
-Agilent MSO3000 series oscope connected to the battery leads in parallel with the reload pro.
The reload pro current current and voltage are jumping all over the place instead of converging to a single value.
Below is my oscilloscope capture of the phenomenon. Note the time scale and voltage range.

This is almost certainly an issue with the software loop designed to match actual to measured current. Do you have access to a copy of Windows where you can install PSoC creator? If not, I can provide a custom build of the firmware to test this out.

No not readily available.
What is the blue port for?
On Feb 11, 2015 2:28 AM, "Nick Johnson"<EMAIL_ADDRESS>wrote:

This is almost certainly an issue with the software loop designed to match
actual to measured current. Do you have access to a copy of Windows where
you can install PSoC creator? If not, I can provide a custom build of the
firmware to test this out.
—
Reply to this email directly or view it on GitHub
https://github.com/arachnidlabs/reload-pro/issues/85#issuecomment-73842707
.

The blue port is an accessory port, currently unused.
I'll put together a build that has this feature disabled (or at least toggleable) this evening. Can you confirm that you get less variation (proportionally) at higher currents?

Going pat ~180mA appears to create a dead short, so I only used small
currents at first.
Part of my problem is that my DC power supplies are out of commisiom, but I
can use alkaline and lipo (3s 2600mAh) batteries for now
On Feb 11, 2015 9:12 AM, "Nick Johnson"<EMAIL_ADDRESS>wrote:

The blue port is an accessory port, currently unused.
I'll put together a build that has this feature disabled (or at least
toggleable) this evening. Can you confirm that you get less variation
(proportionally) at higher currents?
—
Reply to this email directly or view it on GitHub
https://github.com/arachnidlabs/reload-pro/issues/85#issuecomment-73886428
.

Any update?
On Wed, Feb 11, 2015 at 9:25 AM, Theodore Tzanetos<EMAIL_ADDRESS>wrote:

Going pat ~180mA appears to create a dead short, so I only used small
currents at first.
Part of my problem is that my DC power supplies are out of commisiom, but
I can use alkaline and lipo (3s 2600mAh) batteries for now
On Feb 11, 2015 9:12 AM, "Nick Johnson"<EMAIL_ADDRESS>wrote:

The blue port is an accessory port, currently unused.
I'll put together a build that has this feature disabled (or at least
toggleable) this evening. Can you confirm that you get less variation
(proportionally) at higher currents?
—
Reply to this email directly or view it on GitHub
https://github.com/arachnidlabs/reload-pro/issues/85#issuecomment-73886428
.

Sorry for the delay; please try flashing the CYACD file here: https://drive.google.com/file/d/0B_iKMAYU3t1LNWh1RFdWRHVoYnM/view?usp=sharing
You may see offset error between the set and actual current with this test firmware, but it should allow us to check that the oscillations are eliminated.

Yes this seemed to fix the oscillations. I see more of an offset  at lower
currents (<500mA). What is the long term fix/solution for this problem, and
why was mine defective. Have others experienced the same?
Also i registered to receive the thermal insulation kit. When will that be
sent out?
Thanks,
-Teddy
On Sat, Feb 14, 2015 at 6:37 AM, Nick Johnson<EMAIL_ADDRESS>wrote:

Sorry for the delay; please try flashing the CYACD file here:
https://drive.google.com/file/d/0B_iKMAYU3t1LNWh1RFdWRHVoYnM/view?usp=sharing
You may see offset error between the set and actual current with this test
firmware, but it should allow us to check that the oscillations are
eliminated.
—
Reply to this email directly or view it on GitHub
https://github.com/arachnidlabs/reload-pro/issues/85#issuecomment-74371788
.

@Arachnid
Is there a permanent fix for this issue?
I just downgraded from firmware version 1.11 to fix this issue (using the firmware linked above) because I was getting the same issue. My multimeter was reading upwards of 4A (no oscope available) before my power supply would shutoff.


Use CONSUL_HTTP_ADDR adress when available in environment for consul discovery

By default consul tools use CONSUL_HTTP_ADDR to guess the schemes/server ip/port.
Use the same naming convention, so exporting http://consul.machine.acme.org:8500
will be used for consul discovery instead of localhost:8500.
This also detect the scheme and apply similar rules as Consul if scheme is not
setup.

To keep things understandable and have only one source of truth, we do not read configuration from the environment. That way you can look at the file and know what's happening.


fix: hide header on activity screen

Description
This PR fixes an issue introduced here https://github.com/artsy/eigen/pull/11178
I accidentally not add headerShown: false to the activity list.

Header
Header

PR Checklist

[X] I have tested my changes on iOS and Android.
[x] I hid my changes behind a [feature flag], or they don't need one.
[x] I have included screenshots or videos, or I have not changed the UI.
[x] I have added tests, or my changes don't require any.
[x] I added an [app state migration], or my changes do not require one.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added a changelog entry below, or my changes do not require one.

#nochangelog

Warnings

:warning:

✅ No changelog changes

  Generated by :no_entry_sign: dangerJS against cb8b52bd23c5cf90e22b1fe6b96b7bb6ba4d1cff


What is the purpose of the XMLDocument interface defined in lib.d.ts?

Dear Ladies and Gentlemen,
it appears that the XMLDocument interface defined in lib.d.ts is only a double of the HTMLDocument interface. That's not surprising when you look at the definition:

interface XMLDocument extends Document {
}

declare var XMLDocument: {
prototype: XMLDocument;
new(): XMLDocument;
}

But I would expect the members which are defined for the "IXMLDOMDocument" as defined here:
https://msdn.microsoft.com/en-us/library/ms756987(v=vs.85).aspx
A second HTMLDocument interface which only differs in it's name doesn't make much sense to me.
Please can you explain what's the purpose of the "XMLDocument" interface?
Kind regards, Lord Saumagen.

The XMLDocument interface is defined in the DOM specs and lib.d.ts is based on these, so the definition should stay.
But you're right, practically, it is not very useful in its current form.
https://dom.spec.whatwg.org/#xmldocument
http://www.w3.org/TR/domcore/#xmldocument

Dear Mr. or Mrs. rielz
thank you very much for your explanation. Now I know where the Interface comes from, but I'm still wondering how such a stupid interface could become part of the specification in the first place. It seems that some brighter persons at the W3C share my opinion.
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22960
Thank you for enlighten me and kind regards, Lord Saumagen


Ability to set persistentStoreOptions for deprecated classes

Ability to set persistentStoreOptions for swift 3 version also.

Closing in favor of #185


Add genome build to dropdowns

See comment below 👇 https://github.com/broadinstitute/gnomad-browser/pull/1152#issuecomment-1672063250
fixes #1010

Hiya, snooping on the PR while I'm looking through issues and PRs.
I will probably bring this up at browser meeting, but the Cypress tests I think are doing more harm than good (my fault for wanting to get those in when I started, without really knowing how to do make them effective). I don't think they're catching anything that the Jest tests aren't already, and right now they just add another step to the CI.
At this point, I'd be in favor of removing the Cypress tests step from the CI, and revisiting some sort of integration test for a happy path with Cypress at a later date. I just figured I'd comment here since that is what's causing this PR to fail currently.

Currently, users are unaware of the Genome Reference Build they are searching on – whether it's the GRCh37 build or GRCh38 build. For example, gnomAD v2.1.1 uses the GRCh37 build, this goes the same for all datasets before v3.
This pull request aims to providing users with visibility into the reference genome build for each dataset they select. This is added in both the Searchbox and the DatasetSelector component as seen below.

@ch-kr hoping for your feedback on the UI changes specifically

This is fantastic -- thank you for working on this! A lot of the emails coming into the inbox are users asking questions about why they can't find a variant in one gnomAD version (or why a variant seems to have "disappeared"), and the answer is often because they're searching with coordinates from the wrong genome build.
I really like this addition:

I have a quick question on this view:

Is "Build" necessary? It might be nice to have the reference build text be consistent between both drop downs (and just be "GRCh37" or "GRCh38")

For some reason it looked aesthetically pleasing to have "Build" there because it made the text width more symmetrical with the sample number. We can remove it though and show you how it looks, no problem.

Personally I like the "Build XXXX" as shown, but that's just one man's
opinion.
On Wed, Aug 9, 2023 at 6:19 PM Matthew Solomonson @.***>
wrote:

For some reason it looked aesthetically pleasing to have "Build" there
because it made the text width more symmetrical with the sample number. We
can remove it though and show you how it looks, no problem.
—
Reply to this email directly, view it on GitHub
https://github.com/broadinstitute/gnomad-browser/pull/1152#issuecomment-1672303778,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZQ2NNMEQV2Z4EBRNMISDBLXUQLGVANCNFSM6AAAAAA3KINYAQ
.
You are receiving this because your review was requested.Message ID:
@.***>

ooh, you're right, it does look a bit strange when the build is right aligned and just GRCh37/8. I like the last option (with parentheses). Maybe it's worth posting in gnomad_browser to see if there is a consensus?

Sure @ch-kr.
@elissa-alarmani can you please write a message in the #gnomad_browser channel on ATGU slack summarizing the proposed change, along with a link to this issue?

The people have spoken: the one with the parentheses.

Thanks for the feedback!

I personally think the build in the Searchbox component is a bit large and redundant

The original request was specifically to have build in the search bar (https://github.com/broadinstitute/gnomad-browser/issues/1010), so we need to keep this. Regarding redundancy (that the info is already visible on the gene/variant pages), the goals are (1) to inform user what dataset they will be searching as opposed to the build of the dataset they have already searched for because it could be completely different and (2) when users start from the home page they have no info about genome build on screen anywhere.

the UI choices for that component (smaller font, grey font color) do a good job at conveying the information while keeping things legible

This is a good suggestion and what indeed what I would have done for the Search if the component could support it, but decided it wasn't worth the effort. Elissa and I can take another look to see if we want to do this, otherwise maybe it warrants a new ticket.

Perhaps we can look at react-select library for inspiration: https://react-select.com/home
I see they have a "grouped" option. One idea could be to group datasets by GRCh37 or GRCh38. This would allow us to preferentially show GRCh38 datasets first (which would encourage users to use the latest build, which is what we want). And would address your concern that parentheses add clutter.

@rileyhgrant what do you think about using react-select directly in gnomAD browser?

I see they have a "grouped" option. One idea could be to group datasets by GRCh37 or GRCh38. This would allow us to preferentially show GRCh38 datasets first (which would encourage users to use the latest build, which is what we want). And would address your concern that parentheses add clutter.

Ah neat! This seems like it would be a good middle ground.
I see now the sticking point of wanting to know the build before searching the first time. I definitely agree that the information should be there, and see how having it only appear in the dropdown does not necessarily address that goal, I am still in favor of that option, whether it be our own component or using some other functionality (react-select or just html tags).
I like the idea of grouping them in the dropdown, and I believe the HTML select has an optgroup tag that does this as well, so it might not even require adding react-select.

Oooh amazing idea @elissa-alarmani!

@elissa-alarmani can you push this change so we can try locally?

OK yeah I love this and think it resolves @rileyhgrant's concerns. Are we OK to merge (once tests pass?)

LGTM! Since there are quite a few individual commits, this PR would be a good fit for the "Squash and merge" option from the Github UI, Elissa.


Add standard logging module and clean up docstrings

Discuss what type of events we want to keep track of

Quick proposal for discussion:
At ERRORS and WARNINGS levels:

any thrown exceptions or error conditions, at the appropriate severity level

At INFO level:

a single message for each public API call structured to show success or failure (e.g. "Successfully stored hash: XXYYZX" or "Failed to store PID: doi:XXXX/677y87867"  -- these are off the cuff examples and may not sync with the API fully, so don't take them literally

At DEBUG level:

Detailed progress messages for each API call, showing movement through the process (e.g., at start and end of each implementation method, and exposing key data for debugging. For some simpler methods, this may not be needed

Additionally, review doc strings and ensure they are all consistently formatted (periods, capitalization, etc.)

Doc strings have been reviewed for consistency of usage of punctuation in PR-30: Refactor HashStore to enhance modularity and configurability.

Standard logging module has been added in branch 'feature-10-standard-logging'. Logging statements have been written for the initialization process. However, I had to include a questionable parameter to logging.basicConfig(force=True,...) to get logging to write into the desired file as expected.
The rest of the logging statements need to be written, but am currently investigating the usage of force=True to ensure that this is the best way to have resolved my issue.

It appears that allowing the python logging module determine where the log file is written is standard practice. However, I would like to place logs at the store root because I feel that it would be less confusing to look there; since the default location may be shared with other logs potentially (ex. access logs, error logs, etc.). I will confirm in our backend discussion, and continue to add logging statements to  the 'FileHashStore' class in the meantime.

It appears that allowing the python logging module determine where the log file is written is standard practice

Let's chat tomorrow, but I think it is best practice to not override incoming log preferences from the deployment. And logging config is very deployment-specific -- e.g., the differences between deploying in a VM with filesystem access, versus in a K8S container with a logging facility (see https://kubernetes.io/docs/concepts/cluster-administration/logging/).

I have removed the logging configuration as we discussed and have added logging statements to the FileHashStore module. Changes have been merged into develop via pull request Feature-10: Standard Logging.


cgpt: add type guid for root on raid

Add ability for cgpt to recognize root on raid.

Changed to better description (28 bytes long, which is OK). The ResolveType function uses strcpy not strncpy, I did a search to uncover the size of the buffers the description gets copied into and they're both of size GUID_STRLEN (37 bytes). If someone adds a string that's too long in the future, we'll overrun the buffer. Do you think it's worth changing ResolveType to use strncpy with a hardcoded GUID_STRLEN size?

Changed the name and description to be char arrays instead of pointers so the compiler can catch for overruns if someone adds a name or description that is too long

Switched to strncpy (wish gnu99 c had strlcpy). Also did a grep through cgpt and made sure we don't have any other strcpy or strcats. The only other ones are in tests.


WIP: Send previous checksum with updates

(still figuring this out)
Warn Checklist

[ ] This changes the interface and requires a Major/Minor version change.
[ ] I have :tophat:'d these changes by using the commands I changed by hand.
[ ] I have added a dependancy to the project.

@tanema I'm still doing some testing and cleanup, but let me know if you have any initial thoughts here.


Redmine 2.6.1

Hi,
Are you thinking about doing any update to install new redmine version with your Vagrant?
Thanks!

Hi!
For now I just use the .deb package included in Ubuntu. If it is not
updated by apt, I don't use the new version.
To install a newer version of Redmine,  the method is very different to the
described in the bootstrap.sh file (ruby rake appears in the middle).
If you are interested, you can fork the project and I can give you some
hints to make Redmine 2.6.0 work, so you can create a new bootstrap.sh
file. Unfortunately, I don't have time for now to do this.
Kind regards, Claudio.
El feb 2, 2015 6:07 AM, "El Alemaño"<EMAIL_ADDRESS>escribió:

Hi,
Are you thinking about doing any update to install new redmine version
with your Vagrant?
Thanks!
—
Reply to this email directly or view it on GitHub
https://github.com/clalarco/vagrant-redmine/issues/2.


Add support for cppcheck

I'm using a new handling function because the cppcheck "gcc-compatible" output mode does not include column numbers, so it does not work with the already existing gcc handler.

I have added a test (sorry, thought about it, but then forgot)


Upstream changes from Servo

This contains changes which add flake8 linting to the CI, and a fix for #100.
The multiple build thing seems to work fine for us with appveyor.
Let me know if I should exclude something! I'd like servo/homu and homu/homu to be near-identical, with servo being a bit more liberal in accepting fixes which get eventually upstreamed to homu after style decisions and testing is done.
r? @barosl

cc @frewsxcv @larsbergstrom

This is a giant change in a single pull request. Also, nitpicking: Isn't barosl/homu upstream and servo a downstream fork? ;)

@sigmavirus24 It isn't, there are only two changes in this PR (the rest are merge pull requests).
Yes, barosl/homu is upstream, hence "upstreaming". I'm using it as a verb.

Superseded by #133

Superseded by https://github.com/barosl/homu/issues/134


VNext move all spatial types to spatial namespace

There is a mix of spatial types in the root namespace that should be moved to the spatial namespace.

This was already done in https://github.com/Azure/azure-cosmos-dotnet-v3/pull/1072
Any new Spatial types will go to the Spatial namespace in vNext

@ealsur take a look at PR #1097 . It adds new types Geo types that are under the common namespace.

Yup, saw it, but that change is not in vNext. Any new change I port to vNext, if its on the client surface/rest contract, I do the namespace adjustments 😄

I'm closing this issue then.


Set cartesian impedance failed while running Moveit!

Hi all,
I am implementing impedance control for a trajectory planned by Moveit!. I have tried two approaches but both of them failed:

Launch panda_control_moveit_rviz.launch from the package panda_moveit_config ([https://github.com/ros-planning/panda_moveit_config]) and call service /franka_control/set_cartesian_impedacne. However, an error appears as below

set_joint_impedance failed: libfranka: Set Cartesian Impedance command rejected: command not possible in the current mode!

Launch two controllers position_joint_trajectory_controller and cartesian_impedance_example_controller with the node controller_spawner at the same time. As a result, Moveit! can generate a trajectory and it can be executed in rviz. However, it cannot be executed by the real franka robot! During the fake execution period, the topics /execute_trajectory/actiontopics and /position_joint_trajectory_controller/follow_joint_trajectory/actiontopics both show messages.

Thus, does anyone can help me to tackle these two situations? Any other methods to realize planning with Moveit! and follow the trajectory with impedance control are welcomed! Really appreciate your reading!
Best regards,
Fei

Hi @feimeng93,

Launch panda_control_moveit_rviz.launch from the package panda_moveit_config ([https://github.com/ros-planning/panda_moveit_config]) and call service /franka_control/set_cartesian_impedacne. However, an error appears as below

This is expected behaviour. If you look at the documentation of the FCI you will find the following section:

Non-realtime commands are blocking, TCP/IP-based and always executed outside of any realtime control loop.

Meaning by design you cannot call the non-realtime commands like set impedance while having an active controller running. To mitigate use something like this:
rosservice call /controller_manager/switch_controller "stop_controllers: ['<YOUR_CONTROLLER_NAME>']"
rosservice call <YOUR_NON_REALTIME_COMMAND>
rosservice call /controller_manager/switch_controller "start_controllers: ['<YOUR_CONTROLLER_NAME>']"

If you are using the CartesianImpedanceExampleController you can set the impedances also via dynamic reconfigure without stopping the controller.

Launch two controllers position_joint_trajectory_controller and cartesian_impedance_example_controller with the node controller_spawner at the same time.

What would you expect to happen when you run a joint position controller and simultaneously a Cartesian impedance controller? Both controllers claim some command interfaces of the hardware so the controller manager from ROS control shouldn't even allow you to start both. I don't quite understand what you are trying to achieve here, TBH. I suggest you only start one (commanding) controller and use the interface from that. If you need both, first stop the one controller and then start the new one.
For more details on the topic please familiarize yourself again with: http://wiki.ros.org/ros_control
Hope this helps. Feel free to reopen if the issue persists

For completeness, we have implemented a Cartesian impedance controller that can run (MoveIt) trajectories using the nullspace stiffness component while staying compliant.
This way, one does not need to switch to position control & I think this is what the original author wanted to achieve.


add Marc Khouzam as a core maintainer

Signed-off-by: Matthew Fisher<EMAIL_ADDRESS>

Thank you! 🎉


Allow blacklist of repositories and organizations

Currently, I'm tied into many organizations that I would not like to pull code from in a personal backup.
It would be nice to be able to prevent these repos/orgs from being backed up into this system

Put in a pull request with basic support for excluding a repository. Only tested on user repository. Further testing is welcome from the fork prior to accepting the pull request.


RubberBand spelled icorrectly

Hi,
Please fix spelling
fun Ruberband (view: View) :AnimatorSet{
line 26 in class Attnetion.Kt

I fixed the typo. Thank you.


🎭Create Character class

Related to #56
Originally I thought we might be able to get away with just using an interface, but we need some kind of character class that inherits from MovingObject and implements an IAttackable.
In the short term this class needs:

[ ] HP
[ ] Implementation of IAttackable (exact methods TBD). This shouldn't be implemented by Moveable since we could have moving objects that are not attackable.
[ ] Stats

In the long term (separate issues as needed)

[ ] Ongoing effects/Status Effects
[ ] Other things as combat and gameplay design is ironed out

Is this still relevant with the combat changes made in PR #76? I notice we closed #10 in favor of this issue, but these issues seem wholly unrelated.

Is this still relevant with the combat changes made in PR #76? I notice we closed #10 in favor of this issue, but these issues seem wholly unrelated.

I closed #10 since it had no information on the issue and without anything there, they're duplicates.

HP is contained in CombatData - this seems to work well and the player can kill a penguin (in theory).
IAttackable has a few methods on it, feel free to add more there, it's only enough to make a bare bones combat system.
I wonder if we couldn't implement class stats as something that modifies the CombatData when we pull it from the player object. We could combine that with status effects on the player as well and have the combat resolution mechanic handle combining a class with CombatData. Admittedly, that could lead to some hilarious interactions.

Example The beerbarian
Lutefisk - harvesting lutefisk increases your damage. Attacks decrease your lutefisk score.
If lutefisk score goes over some threshold, the seal goes into crazy mode an attacks nearby enemies for a certain number of terms.

Example wizard hat
Three levels:

Chum-mancer
Cod-jurer
War-lox

Example Thief

Clown fish -
Clamdestine agent -
Angler fish - chance to confuse enemies, throws a lamprey

Example Cleric

In-squid-itor
Octopriest
Cephalapadre 🦑


Clear cache correctly upon extension enable/disable/update

Until https://github.com/flarum/core/issues/837#issuecomment-288233553 is fixed in core maybe we should clear the manifest.json ourselves so assets get a new name and bypass the old version from Cloudflare/Proxy ?
Might also help against the CTRL+F5 CTRL+F5 CTRL+F5 CTRL+F5 CTRL+F5 effect

I've created a new label to keep track of stuff we might do to patch core. If we want to do this, we should fix it in Bazaar and tag it asap, but also PR against core.


Fixing typo in the message

Hi @BrucePay, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Bruce Payette). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;


Feature Request: Space Biomes, Endor, and Laying Claim to Planets

It would be nice if you created a biome specifically for space (It's basically a single biome anyhow), it would be handy for packs that include Tough as Nails and would allow the pack makers to customize how TAN treats temperatures in space.
The biome(s) could be divided into three basic sectors based on the distance from the star systems center.
Hot Zone: Basically where you would find Venus and other Hot planets like it, generally closer to the star than the overworld
Goldilocks Zone a.k.a. Overworld Zone: Between the Cold and Hot zones and where the overworld and similar worlds would be by default.
Cold Zone: Basically where Neptune and other Cold Planets would be found by default, generally far away from the center.
In Addition, the moons around Gas Giants, would have their own zones due to the effect of gravity and heat from said giants.
It would make it very interesting to see a Jungle Moon (basically Endor from star wars) around a Gas Giant which is in it's systems Cold Zone. Planetary Moons could be coded as being planets orbiting Gas Giants for world generation and mapping (basically moons around gas giants would have a chance of being generated as planets, essentially being the larger moons and in the case of smaller rocky planets it would be at most a planets twin).
Edit: just thought of it afterwords, could it be possible to "lay claim" to a planet and name it using an item, all it would do is change the displayed name, but it would still be fun, you'd have to limit it to the first time only (or multiple times in the case of OP commands).
Heck it could even be configurable on whether it shows to other players on the server and whether it can be changed once, multiple times, or at all.

It would be nice if you created a biome specifically for space (It's basically a single biome anyhow),

This is already implemented. See under "Space".

The biome(s) could be divided into three basic sectors based on the distance from the star systems center.
Hot Zone: Basically where you would find Venus and other Hot planets like it, generally closer to the star than the overworld
Goldilocks Zone a.k.a. Overworld Zone: Between the Cold and Hot zones and where the overworld and similar worlds would be by default.
Cold Zone: Basically where Neptune and other Cold Planets would be found by default, generally far away from the center.

Before we do this, can we improve how objects are rendered in the map of planets? Currently the distance limit for planets is 2 AU, and anything higher doesn't work on the map for some reason. Also, Wikipedia has a nice equation for calculating the temperature of a planet based on Orbital Distance, Star Luminosity and Albedo.

In Addition, the moons around Gas Giants, would have their own zones due to the effect of gravity and heat from said giants.

It would make more sense for moons to be heated by the sun, the tidal effects from a gas giant might heat up a planet, but they'd also make the planet have bad geological activity. (Earthquakes, etc.)

Edit: just thought of it afterwords, could it be possible to "lay claim" to a planet and name it using an item, all it would do is change the displayed name, but it would still be fun, you'd have to limit it to the first time only (or multiple times in the case of OP commands).

That could be cool. I'm not sure why you put this in the same post about planet and moon biome temperature, though.

Didn't know about the space biome...
still would be nice to have planetary moons though (I want to lay claim to Endor! LOL), oh and the reason the laying claim part was in this post as well was because I had been thinking about things that would be interesting to put in, but was unable to remember what the third idea I had was.
So, what or how do you think you'd make claims in the mod, personally I'd make a flag, a memorial (basically a sign that says something along the lines of "Welcome to ______, Kilroy was here!" or something ("Kilroy was Here!" would be in graffiti)) or some other block that would trigger the interface.

The realistic solar-based temperature is in and has been for a little while, and from what I remember TAN has been out of support for a while now so the only thing left to get from this issue is planet claiming.

Last part of this issue is better served by #1895


Optimize testing config to dev

As of now, when npm test is launched, tests execute in single run. Karma test runner initializes itself, browsers to test, then shuts them down.
It suits for CI, but causes additional latencies in development workflow.
npm test should be optimized to run in autoWatch mode by default, and --single-run option should be added to CI config.

Better leave npm test config as is but add npm run test-dev in addition.

Continuous integration testing and development process also need different reporters.
When CI-ing it would be better to report all processed specs.
But when developing reporting should only indicate that it took place and report failing tests.
So, for CI we'd use "karma-spec-reporter" and for development testing combination of "karma-super-dots-reporter" and "karma-failed-reporter".


Rules starting with the same pattern do not work as alternatives to each other

Consider the rule
start = [a-z]+
/ [0-9]+ '!'

in a grammar.
abc // matches
123! // matches

Now change the alternate rule to create the grammar
start = [a-z]+
/ [a-z]+ '!'

then
abc // matches
abc! // does not match

Please correct me if I'm wrong, but I don't believe this is how it's supposed to work.

For input abc!, the first alternative ([a-z]+) matches a part of the input, meaning the second alternative ([a-z]+ '!') isn’t tried at all. The result is that the matching expression doesn’t consume the whole input, which is why parsing fails at the end.
This is how PEG.js is supposed to work. You need to order alternatives in a choice so that the ones potentially matching longer inputs go first.


⚠ Bofrost.at has degraded performance

In 2115f0d, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 922 ms

Resolved: Bofrost.at performance has improved in ab86070.


Build is not running on raising PR from forked repository

When i am trying to run my build on creating PR from my forked PR, it is not working but if am creating PR through another branch in my parent repository it is working fine.!!

I'm having the same issue of not being able to build from forks

@obenziane2 This is because security issue, If you try it with same Repository and raise PR by created new branch then It will show on github and show checks on Github.
If somebody knows more about please let us know!!


Add README for the new repository

The new repository is created as: https://github.com/ChallengeForge/TheWeeklyChallenge
I would love to have same README as in https://github.com/manwar/theweeklychallenge

Hello. I can take up this issue.
I also wanted to look at the issue with updating Hugo and wanted to know the way forward in regards to which repository will be accepting submissions. Will it be this current repo or will all the issues also move to the new repository?

@tony-nyagah Please ignore the Hugo as it will stay with the current working website.
We are moving away from Hugo and going to Dancer2.


Device IP always return same IP

SUMMARY

I have 2 devices in my home when calling a command to turn on/off light, it always returns the same device IP for both device. Use the latest version 0.1.10.
ECHO DEVICES

Echo Dot 1st generation
Echo Cube

Duplicate to #76


[INFINITY-3214] Nullify default value for HDFS authz mapping

The docs reflecting this change are in #2216

The docs in #2216 still seem to indicate that kerberos principals are being mapped to the user nobody: https://github.com/mesosphere/dcos-commons/pull/2216/files#diff-874c92dd598ecf9b90ea2d5322ef75a2R178

@mpereira right, so I commented on that PR mentioning we'd need to update that documentation

Whoops. I hit merge before giving a 👍


update to web 0.5.0

With flutter 3.19 the package web is updated to 0.5.0, is there any option to update the library?

Please update to youtube_player_iframe: ^5.1.0


Integrate repo with AppVeyor

Is your feature request related to a problem? Please describe.
Now that the repo is configured for AppVeyor, someone with admin rights needs to integrate the repo with the Appveyor service for ArkEcosystem.
Describe the solution you'd like
I would like this repo integrated with AppVeyor and have the AppVeyor CI system run on PRs.
Describe alternatives you've considered
There are other Windows CI systems out there like Azure, but AppVeyor seemed the simplest.
Additional context
The .appveyor.yml has been tested on my personal AppVeyor account before I submitted it so this should work first time.

It looks like the .appveyor.yml is available in develop and master.  The CI just needs to be turned on by Ark Crew.  There is nothing I can do at this point.
Once CI is going, I can debug any issues with the config file or builds.

@faustbrian
Can you check that Appveyor is configured?
It’s showing up in the repo apps for C++ Client & Crypto;
but it’s not triggering, and the configure option is grayed out for me.
Please and thank you.

@ciband
Appveyor may not be needed now.
https://circleci.com/build-environments/windows/
@faustbrian any info on this, or if it's available to us?

Here are some more details on the Windows support:
https://circleci.com/blog/windows-general-availability-announcement/
It looks like you need the "Performance" plan to get access.  Not sure if we have that for our MacOS builds or not.
From the article:
Now you can use Windows, Linux, and macOS jobs all in a single workflow. With this release, CircleCI is your standard CI solution for building cross-platform applications. Windows jobs are already available to all Performance plan customers today. Learn more about our Performance plan here.

Unassigning from me until there is something actionable that I can do.

This issue has been closed. If you wish to re-open it please provide additional information.

Seems to be all green at https://ci.appveyor.com/project/faustbrian/cpp-crypto


Issue with :addModel

Having issues with the :addModel function. I call Scene:addModel() previously, multiple times, and it works perfectly fine, but now I'm getting the error: ss3d/engine.lua:255: attempt to call field 'insert' (a nil value)
The code is called from
print(pathModel) Scene:addModel(pathModel)
It prints "table: xxxxxx", but then gives me the error on the next line

It seems the Scene:addModel() function does not accept paths. Try to load the model into the correct lua table structure first, the Engine supplies functions for the commonly used .obj file format.
An example from where the url "assets/alakazam.obj" gets loaded into the scene:
AlakazamModel = Engine.newModel(Engine.loadObj("assets/alakazam.obj"), DefaultTexture)
Scene:addModel(AlakazamModel)


Make result printer compatible with phpUnit version 7

Fixed parameter type hinting
Fixed void returns
Updated composer settings
Updated phpunit xml config to v7

Looks good to me, please merge :-9

PHPUnit 7 support is here https://github.com/JeroenDeDauw/nyancat-phpunit-resultprinter

Thanks @JeroenDeDauw! I'm using your fork <3

I just made a new release that adds compat with PHPUnit 8. Getting PHPUnit 9 to work looks rather involved and I do not currently have the time to spend on that. Pull requests welcome though!

@JeroenDeDauw May you enable issue creation on your Fork, so we can continue there?

Huh. Did not realize those where disabled. Here you go: https://github.com/JeroenDeDauw/nyancat-phpunit-resultprinter/issues


Quote FROM table names if option is enabled

Fixes a bug where enabling autoQuoteTableNames did not quote the table name in FROM clause. This failed for me when using with postgres.
Code:
var squel = require('squel');

var query = squel.select({ autoQuoteTableNames: true })
.field('id')
.from('user', 'u')
.where('u.id = ?', 1)
.toString();

console.log(query);

Before:
SELECT id FROM user `u` WHERE (u.id = 1)

After:
SELECT id FROM `user` `u` WHERE (u.id = 1)

Merged latest upstream master and rebuilt assets.
PS: @hiddentao I know it's written in the contribution guide, but should I really be generating the assets for the pull request? Seems like it'll generate conflicts for every new pull request merged.

Thanks! Made some changes to the code though so I ended up just fixing this along the way. 5.3.1 has it fixed for you :)

Btw, as for why we bundle the buitl output in the repo, it's for people who don't want to install via NPM and go straight for the repo instead. Because squel is designed for browser usage too.

Makes sense. Thank you 👍


Success.

I have my Controller 67 working as it should.

Thanks for all the work, this is a game changer for U.K. owners as there is a complete lack of U.K. plug for UIS devices.
Rapsberry Pi 4 running HAOS
Notes
Make sure you use advanced terminal from HACS. (remember to fill in info at top of page)
cd to /config/custom_components no sudo needed
install expect no apt, just install expect
Install ac-infinity-hacs you may need to link to this repo
If you have the app installed on your phone disable BT when setting up.
The slider won’t work if you have automations set up, disabling automations will let you control the fan.

Hello flamedodger
Would you be able to post step by step of the above I try to cd  /config/custom_components using advance terminal then I run install expect and  nothing happens no installation etc I think I am missing something.
Thank you


Gemspec: Drop EOL'd property rubyforge_project

The RubyGems property rubyforge_project is removed without a replacement.

Thank you!


Add holoAng(n), holoPos(n) getters

Add functions to simplify getting holo angles and positions

Merged too fast. This was missing nodiscard and I would've preferred the Angle(ang[1],ang[2],ang[3]) be converted to just ang.


Async pipeline compilation

Objective

Pipeline compilation is slow and blocks the frame
Closes https://github.com/bevyengine/bevy/issues/8224

Solution

Compile pipelines in a Task on the AsyncComputeTaskPool
This won't actually improve anything until wgpu 0.19, as wgpu currently has internal locks that will cause blocks anyways

Changelog

Render/compute pipeline compilation is now done asynchronously over multiple frames
Added CachedPipelineState::Creating
Added bevy_utils::futures::check_ready

Migration Guide

Match on the new Creating variant for exhaustive matches of CachedPipelineState

Shame we couldn't get this one out in time for the jam. Darn!

Shame we couldn't get this one out in time for the jam. Darn!

Wouldn't be possible, as we need wgpu 0.19 first for this to actually work.

Sadly causing an error log message (but no crash) when the app first loads, as it renders nothing while waiting for pipelines to compile :grimacing:
We might need some logic to block that specific log message for the first few frames of the app, or something else hacky.
2023-12-01T19:50:50.742368Z ERROR present_frames: wgpu_core::present: No work has been submitted for this frame

I'd like to try and land this for 0.13. We can cut it if it's not ready, it's semi-low priority, but it's a nice improvement if we can land it.

The last thing remaining for this PR is fixing compiling without multi-threaded or on wasm.

For some reaosn, #[cfg(all(not(target_arch = "wasm32"), feature = "multi-threaded"))] seems to be true on desktop??

Doesn't work for me on Linux+AMD 6800xt with radv drivers.

Does it just crash or do you mean that it still compiles synchronously?

Does it just crash or do you mean that it still compiles synchronously?

It seems to compile synchronously looking at tracy, and then stuff just doesn't render randomly.

The new fix works for me.

Result on Mac as of https://github.com/bevyengine/bevy/pull/10812/commits/4aed836e344b68305da5995f383ccc530cc81851
AdapterInfo { name: "Apple M1 Pro", vendor: 0, device: 0, device_type: IntegratedGpu, driver: "", driver_info: "", backend: Metal }
SystemInfo { os: "MacOS 14.2.1 ", kernel: "23.2.0", cpu: "", core_count: "10", memory: "32.0 GiB" }

https://github.com/bevyengine/bevy/assets/2771466/72dda7db-5661-4688-b50e-a044d2bc11b9

Same example on main for comparison.
https://github.com/bevyengine/bevy/assets/2771466/22edfc20-fd85-46d6-8c7f-a6a7444394ea

For completeness, it seems metal async support is blocked on https://github.com/gfx-rs/wgpu/issues/3794. Identified by @Elabajaba

I removed macOS support for now. Once wgpu gets create_pipeline_async() we can revisit this for WebGPU/macOS support.

I did some profiling, and we do still stutter when we hit new pipelines, but it's significantly less bad (~50ms instead of ~200+ms).
The issue is when we first call process_pipeline with a Queued pipeline naga_oil has to do a bunch of stuff (in the ShaderCache::get calls) which can take ~50ms on my system.

I moved the expensive naga oil work into the task. There's still a chance of stutter if extract_shaders() is blocked waiting for a lock a task is holding, but it should be pretty rare hopefully.

Is there any way for an app to request that pipelines be synchronously built: i.e. to turn this behavior off? I worry that just having objects silently not appear for a few frames is not the behavior that every app wants.

I'd like to leave that to a followup. We can put it in the RenderPlugin settings, but it's a bit of a pain.

It'd also be nice if apps could preload pipelines, but that can be done as a follow-up, as I'm not sure what the API for that would look like.

https://github.com/bevyengine/bevy/issues/10871

Works for me locally. I'm content with the level of review and testing for this, and no crimes have been committed in the code base. Merging now: I'd much rather have to revert just before release than find out it's broken for users after launch.