Added JavaDoc for clarification

Added some JavaDoc and a note to the spec document.
Especially the need for a named health check response made me run into errors when using HealthCheckResponse#builder() without setting a name.

relates to #178

Thanks! Are the typos already targeted, otherwise I'll follow up with a PR.

@sdaschner I already created a PR - https://github.com/eclipse/microprofile-health/pull/192 because there were some checkstyle errors, so I included the suggestions also.


Markdown appearing when manually failing test case

When rendering with markdown in the web viewer, if I manually fail the test case (i.e. thumbs down), the markdown appears and is rendered:
https://github.com/promptfoo/promptfoo/assets/17098959/a80c214c-511b-449e-aea8-eb45bab074cc
Is this intended? Would be nice if we only rendered the markdown, similar to the success case

https://github.com/promptfoo/promptfoo/assets/17098959/db302cbd-5810-4dd6-8e39-62697aee9afa
This no longer occurs as of version 0.61.0, closing!

@typpo looks like this is issue is re-occurring in 0.62.0
Can we open up this issue again? 🙏


fix(select): fixed option style

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.006%) to 83.842%

Totals

Change from base Build<PHONE_NUMBER>:
-0.006%

Covered Lines:
10029

Relevant Lines:
11011

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.01%) to 83.837%

Totals

Change from base Build<PHONE_NUMBER>:
-0.01%

Covered Lines:
10029

Relevant Lines:
11011

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 83.837%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
10029

Relevant Lines:
11011

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 83.837%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
10029

Relevant Lines:
11011

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 83.837%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
10029

Relevant Lines:
11011

💛  - Coveralls


chore: Bump zcash_primitives, orchard and zcash_proofs

Solution

Bump orchard from 0.7 to 0.8.
Bump zcash_primitives from 0.14 to 0.15

The new version moves the methods previously in zcash_primitives::consensus::Parameters to zcash_protocol::consensus::NetworkConstants, which is now blanket-implemented for Zebra's Network, so I removed our implementation of zcash_primitives::consensus::Parameters because of conflicting method names. The blanket implementation of NetworkConstants returns hard-coded HRPs, so we lost the ability to return custom ones. We don't need custom HRPs now, so I removed them.

Bump zcash_proofs from 0.14 to 0.15.

Tests
Existing tests should suffice.
PR Author's Checklist

[x] The PR name will make sense to users.
[ ] The PR provides a CHANGELOG summary.
[x] The solution is tested.
[x] The documentation is up to date.
[x] The PR has a priority label.

PR Reviewer's Checklist

[ ] The PR Author's checklist is complete.
[ ] The PR resolves the issue.

@mergifyio refresh


ProfilePath: error/crash when manually renaming a profile folder

there is no handling in place when a user manually deletes or renames a arma 3 profile under the ProfilePat.

could not reproduce error myself. also only one user reported this issue so far.


Cleaning up multiple unnecessarily exported methods

Changes
Converted the following exported methods into un-exported local methods since they are being called from the same file/package to avoid direct access. No logic changes are involved in this PR. This just has refactoring of method names.
ApplyResourceSubstitution
DagFromState
EmitErrorEvent
EmitEvent
EventForObjectWithCondition
EventForPipelineRun
EventForTaskRun
GetPVCSpec
GetPersistentVolumeClaim
HasDefaultConfigurationName
IsPodHitConfigError
MarkStatusFailure
MarkStatusRunning
MarkStatusSuccess
NeedsPVC
NewArtifactBucketFromConfig
NewFakeClient
NewPipelineRunTest
NewTektonCloudEventData
ResolvePipelineTaskResources
ShowRef
SubmoduleFetch
ValidateDeclaredWorkspaces
ValidateResults
WithDefaultConfigurationName

Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[ ] Includes tests (if functionality changed/added)
[ ] Includes docs (if user facing)
[ ] Commit messages follow commit message best practices
[ ] Release notes block has been filled in or deleted (only if no user facing changes)

See the contribution guide for more details.
Double check this list of stuff that's easy to miss:

If you are adding a new binary/image to the cmd dir, please update
the release Task to build and release this image.

Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes

/ok-to-test

/kind cleanup
Can you also squash your commits so this PR only contains one commit?
Thanks for making this change!

Sounds like a duplicate of #3289

/test check-pr-has-kind-label


fix: there maybe unexpected files in event file list, not like 1.json…

fix: there maybe unexpected files in event file list, not like 1.json, 2.json, but .DS_Store for macOS system.
so the _reinitialize_from_file_store will throw exception during init EventStream from existing event store.

Would it make sense to explicitly filter out .DS_Store when on Mac since now the exception would not bubble up any other issue?

Would it make sense to explicitly filter out .DS_Store when on Mac since now the exception would not bubble up any other issue?

Not sure if other system may generate some other kinds of sys files, and the method _get_id_from_filename is simple, I think for any kinds of exception, just return a invalid id will be ok.
But thanks for your suggestion, I think print the exception will be better.


Example of how to use without decorators?

I am new to this library, but my project is based without decorators because create-react-app does not support them. And the workarounds for supporting decorators could be detrimental to performance/stability.
How do I use this without decorators?

You can write decorators in another form:
import { __decorate } from 'tslib'
import { version } from 'mobx-sync'

class FooStore {
  foo: string
}

__decorate([version(1)], FooStore.prototype, 'foo', void 0)


Added a new scheduled updates FAQ

Can an update that is covered and managed by the "Scheduled Updates" featuer happen outside of the "Scheduled Updates" window?
Yes, while in general updates are not applied outside of the configured "Scheduled Updates" window, rare critical security updates can be applied outside of the patching schedule as part of our security policy.

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

#sign-off

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


Bug: Copy button on export collections page does not actually copy to clipboard

I thought it was a client issue, but I have noticed on Windows 11, MacOS Big Sur, and Linux Mint that the collections copy button does not work. This isn't a huge deal, but I thought I would just add it to the list! :smile:

I just checked on Firefox 108 and Chrome 108 in both normal and incognito mode on Linux Mint. Checked again on Windows Chrome 108 in Incognito mode and still can't click to copy. No errors in console.
Just to confirm, I am clicking this button and trying to paste elsewhere.

I did just notice that I am quite a bit behind on PocketBase v0.9.2... This may be the problem. Thanks for looking in to it.

What do you mean "can't click to copy"? Can you reproduce it in the live demo - https://pocketbase.io/demo
Is the button not accessible? Maybe is a z-index issue but I can't reproduce it.
The "Copy" button will not work on older browsers that don't have the Navigator.clipboard API or browsers that don't allow access to the clipboard.

I can click the copy button. The notification appears that it copied to clipboard, but it doesn't actually copy to my clipboard.
I tested on the live demo and was not able to reproduce. It must be a version issue or client side.
Thanks again.


Support 7z besides unzip

Now install.sh works if either unzip or 7z is available.  There are people who prefer 7z over unzip even for extracting ZIP files so that they are not willing to install unzip besides 7z.  This change could make such people happy.

I'm fan of this pr, since 7z is the only option for installing it on Synology DSM. See Issue #260

@dahlia could you check why the test is failing for macOS?

@erelinz It was due to inconsistent indentations (2-space soft tabs instead of hard tabs).  I just amended it!

Could this be merged? Apparently it's already reviewed, so it would be nice if it'd land shortly!  :)

@bartlomieju Could you review this patch?


[HOT_TOAST] Specs: Write cypress tests for missing features

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request
[x] Other... Please describe:

Current behavior
Cypress tests are not written for all cases.
Expected behavior
Library should have test cases written for all cases.
What is the motivation / use case for changing the behavior?
To keep the library bug free.

Maybe I can help you with Cypress. Still need help?

Yes


Changes in the flow of the program, new features, and fixing some issues

Splitted start method into start and setup to get information about the torrent without downloading
Constants organized in Configuration.py to facilitate the customization of the program
Timeout constant for all requests
Get peers from string as well
TCP only mode
Preventing TypeError in bcoder.get_dict()
Attempt to configure some torrent files that don't follow the standard by searching the values outside the info dictionary
If the metadata for the package is not found then a generic version is used
Preventing the program to exit when a tracker responds with unexpected contents such as webpages
Minor changes in redundant code

5 and 6 are probably related.

Now that I look at it I should have organized in branches. If it's not a problem to merge like that then ok, else I'll reorganize for a new PR.
Some of the changes are quite unusual. Tell me what you think.

Now that I look at it I should have organized in branches. If it's not a problem to merge like that then ok, else I'll reorganize for a new PR. Some of the changes are quite unusual. Tell me what you think.

You mean to you request the changes to merged to the main branch?
That's ok.

Thank you for making PyBitTorrent much better!


qemu: introduce vhost-user handling

Add ability to add a vhostuser device to the
QEMU commandline.  We expect two different types of devices
to be connected through a vhostuser socket: SCSI and network.
Signed-off-by: Eric Ernst<EMAIL_ADDRESS>

@mcastelino @amshinde -- FYI.

Coverage increased (+0.05%) to 64.549% when pulling 9fa6027f0265929af1b30053f763e7b7be7e0667 on egernst:vhostuser-enabling into b4a2d33d7c30a4ecf0af1de4729c2125c1bfadaa on ciao-project:master.

Coverage increased (+0.06%) to 64.563% when pulling 6e885674f52fab0051a6913b7cc0e9d7e29b863b on egernst:vhostuser-enabling into b4a2d33d7c30a4ecf0af1de4729c2125c1bfadaa on ciao-project:master.

Coverage increased (+0.06%) to 64.558% when pulling d1729adc9796b22ecd5b3aabdc834f502c616a81 on egernst:vhostuser-enabling into b4a2d33d7c30a4ecf0af1de4729c2125c1bfadaa on ciao-project:master.

Coverage increased (+0.05%) to 64.561% when pulling 2a6d1e40805f7967fdb54320514750832eb3ba1b on egernst:vhostuser-enabling into 01454f15bd116aad10e56ce8b1f3075288e3d3a8 on ciao-project:master.

Coverage increased (+0.05%) to 64.561% when pulling 2a6d1e40805f7967fdb54320514750832eb3ba1b on egernst:vhostuser-enabling into 01454f15bd116aad10e56ce8b1f3075288e3d3a8 on ciao-project:master.

Coverage increased (+0.06%) to 64.575% when pulling 2a6d1e40805f7967fdb54320514750832eb3ba1b on egernst:vhostuser-enabling into 01454f15bd116aad10e56ce8b1f3075288e3d3a8 on ciao-project:master.

Coverage increased (+0.05%) to 64.561% when pulling 2a6d1e40805f7967fdb54320514750832eb3ba1b on egernst:vhostuser-enabling into 01454f15bd116aad10e56ce8b1f3075288e3d3a8 on ciao-project:master.

Coverage increased (+0.06%) to 64.571% when pulling 2a6d1e40805f7967fdb54320514750832eb3ba1b on egernst:vhostuser-enabling into 01454f15bd116aad10e56ce8b1f3075288e3d3a8 on ciao-project:master.

Coverage increased (+0.05%) to 64.595% when pulling 8d5522d57526f1de8b2250513670284e6604ff1f on egernst:vhostuser-enabling into c3de387d86ff689f7edde0e5a69cbb2cf4c4af3b on ciao-project:master.

@mcastelino -- sounds good -- will add these tomorrow.

@egernst The qemu package has moved. Please submit your new patch to https://github.com/intel/govmm


Favicon coloring based on PR status

Hi,
I think it would be nice to have coloring in the github icon based on the PR status.
Example:

Use case: Sometimes I leave some PRs that I review unclosed to revisit them later after CIs pass (or fail). It would be nice to quickly check that without going into the tab.
For instance this is being done in CI status pages like travis, appveyor et all...

:+1: I like how Travis does this.

Could this include whether PR is mergeable? So not only CI status, but also whether there's an approval if it was required?

We could add a star next to the icon to denote non-merge-ability maybe... But I'd recommend against coloring based on mergeability...
To me this coloring would tell me if I need to visit the page or wait for the CIs to turn green... Reviews on the other hand don't typically involve a fixed wait time where this could be useful...
But it would be nice to know that too without visiting the page... So a star or a specific separate symbol for that would be good...

I don't see the value in just showing if CIs passed. Those are automated and usually only take a short period of time to run. More to the point, if CIs pass and something else blocks merging (e.g. Conflicts or review denial), showing a green icon because my linter passed is, at best, inaccurate.
If we add a star for merging, what about other automated runners? I have sites with a deployment preview that can pass/fail. Test coverage can drop, the repo owner can request changes, etc. Should each of these get a special symbol?
I say keep it simple: Green is everything passed, red is something failed, yellow is something has a warning or needs specific input (i.e. Merge conflict, someone asked for changes to be made to the PR).
My 2¢.

👍 to what @paulmolluzzo said, but then I thought of a good (but complex) solution (I think).
What if we use what GitHub uses to show some reviewers have approved and others have requested changes - a multi-coloured green/red pie.
So here's my concrete suggestion:
If PR doesn't require an approval and there's only one commit status:
We have 3 icons - green, yellow, red - representing the commit status
If PR doesn't require approval and there are multiple commit statuses:
We may either use the 3 icons - green, yellow, red to indicate the total status or we can use a combination - half in green + half in red, half in yellow + half in green etc. If there are two commit statuses - every half represent one, if there are more than two - we could just one half in green if there's something passed and the other half in red if anything has not passed, otherwise yellow.
If PR requires an approval and there aren't commit statuses:

Green if all who were requested has approved and there aren't any requested changes
Red if there are only change requests
Yellow if there are no reviews yet
Green + Red if there are both approvals and change requests
Green + Yellow if there's an approval, but someone who was requested hasn't reviewed yet
Green + Red if there are both approvals and change requests
Red + Yellow if there's a change request, but someone who was requested hasn't reviewed yet

If PR requires an approval and there are commit statuses:

First half is for reviews, second half is for commit statuses
Green if everything's OK, Red if something has failed, Yellow if something hasn't finished yet

I guess this is a bit too much, but we could probably simplify it if you think the direction is right - combining colours in the icon.

Those are automated and usually only take a short period of time to run.

Completely depends on your CI... I constantly work with CIs (that are used only for testing rather than deployment) that are super congested and take 30 minutes to even start running and another 15 mins to complete at best... Even that could be considered short when you compare with some CIs that take several hours to start/pass...

what about other automated runners? I have sites with a deployment preview that can pass/fail. Test coverage can drop

One can add a status check for each of those...
To clarify I'm saying let's make the favicon colored same as that of the "github status check", but not the review status alone...
This

But not this

I agree, * is a poor suggestion...

Half in green half in red is a neat idea... Thanks @hkdobrev...

@hkdobrev's idea is interesting, but it's pretty complex. I'd need a cheat sheet to remember all these scenarios, and worse they'll change from repo to repo depending on third party processes. To top it all off the icon is... 32px square?
Further, this extension becomes kind of "transparent" over time. (@raghavrv forgot he had it installed! :smile:) Even if you commit this to memory you might forget, and then you have to remember if it's from GH officially or not and hunt down documentation... IDK.

Completely depends on your CI... I constantly work with CIs (that are used only for testing rather than deployment) that are super congested and take 30 minutes to even start running and another 15 mins to complete at best... Even that could be considered short when you compare with some CIs that take several hours to start/pass...

My point was super general and reductive, you're right. But this could be a yellow icon and still meet your specific needs, be expressive enough to show temporary state in other scenarios, and simple enough to grok without documentation/memorization.
Green: All good.
Yellow: Waiting on something.
Red: Fails for a reason.

@raghavrv forgot he had it installed!

:P
How about color it like @paulmolluzzo suggests and add a status mark (green tick / red x / grey x / yellow dot) next to it just before the title?

We should try to keep it simple.

I won't get much benefit from it anyways. This is how my browser looks... 😫

okay this gives the state of the PR :
document.getElementsByClassName('statuses-toggle-opened')[0].parentNode.parentNode.getElementsByClassName('status-heading')[0].innerHTML.trim()...
I can try and make a PR... Any guidance on where to fiddle? I have not touched javascript in a long while...
So keeping it absolutely simple, we want -
Green: All good.
Yellow: Waiting on something.
Red: Fails for a reason
Black: If PR not open

EDIT: Using jquery - all_statuses = $('.statuses-toggle-opened').parents(2).find('.branch-action').find('.status-heading').map(function(i, e) {return e.innerHTML.trim()})

I think you'll want to look for something closer to $('.branch-action-item .completeness-indicator') - this is the actual icon, and if it's a success it has the class .completeness-indicator-success as well. The Changes Requested item is an svg with a class on a path.

I can try and make a PR... Any guidance on where to fiddle? I have not touched javascript in a long while...

You might want to put this in a separate file and then you'll include and use it on on PR pages in content.js, probably in this block:
if (pageDetect.isPR()) {
   linkifyBranchRefs();
   addDeleteForkLink();
}

NB: I'm still not sure how all the cases would pan out. What would you show for something like this PR? https://github.com/sindresorhus/refined-github/pull/346 We will have to account for a lot of different scenarios and have some logic that reduces the possibilities to 3 or 4 options.

Sorry for the late response...
For #346, I guess red as we decided (Fails on something (something=merge conflict))?

You might want to put this in a separate file and then you'll include and use it on on PR pages in content.js, probably in this block:

Thanks... I'll try to make a PR tomorrow!

For #346, I guess red as we decided (Fails on something (something=merge conflict))?

@raghavrv I guess that makes sense. It clearly can't just be merged as is.

Thanks... I'll try to make a PR tomorrow!

Awesome!

GitHub got to it first. Less work for us!

I'd like to re-open this issue if possible. While GitHub has implemented this feature it doesn't cover all cases. The favicon indicators only relate to the CI checks and not if it's been approved by reviewers. So the green tick can show but the PR still not in a state where it can be merged. I'd love it if refined-github could tweak this so that the yellow dot is shown until all the checks are showing green.

I've opened an enhancement suggestion to encapsulate @MarcusNoble's observation 🤙🏻 I agree whole-heartedly.
https://github.com/refined-github/refined-github/issues/6134


Add 'like' extension to Option[String]

Supersedes #2039
Problem

In large databases, string partial match on nullable strings are not uncommon. It would be more ergonomic to write field like "%abc%" than field.exists(_ like "%abc%").
Furthermore, "like" extension sometimes causes syntax error In SQL Server as reported in #2039

Solution

Add LikeOption(s1: Option[String]) extension similar to Like.
Make "like" expression a condition instead of a boolean

Checklist

[x] Unit test all changes
[x] Update README.md if applicable
[x] Add [WIP] to the pull request title if it's work in progress
[x] Squash commits that aren't meaningful changes
[x] Run sbt scalariformFormat test:scalariformFormat to make sure that the source files are formatted

@getquill/maintainers

Rebased onto the current master.

@guersam So https://github.com/zio/zio-quill/pull/2039 looks totally right but I'm not sure about this. Can you do field.getOrNull like "%abc%". We also support that.

I'd like to avoid it because there are too many of them in my usecase, but I can bake it into my custom context anyway.


supporting ui router..  when?

Do you have a schedule to support ui router ? Is it already in the road map?

@ronalds1  sorry for the slow reply. Not at this time no. Happy to accept pull requests though!


How to do this with SQUEEL

      u_t = Arel::Table::new :users
      l_t = Arel::Table::new :logs

      counts = l_t.
        group(l_t[:user_id]).
        project(
          l_t[:user_id].as("user_id"),
          l_t[:user_id].count.as("count_all")
        ).as "foo"

      users = u_t.
        join(counts).
        on(u_t[:id].
        eq(counts[:user_id])).
        project("*").project(counts[:count_all])

      puts users.to_sql

generates the SQL
SELECT *, foo."count_all" FROM "users"
 INNER JOIN (
 	SELECT "logs"."user_id" AS user_id, COUNT("logs"."user_id") AS count_all
 	FROM "logs"
 	GROUP BY "logs"."user_id"
  ) foo
  ON "users"."id" = foo."user_id"

Brad,
Unless the join is an association, you can't. Squeel doesn't let you specify alternate conditions for your join.


部署和asgi相关问题

会有内存溢出的问题，关键嵌套的递归还不多的情况下

asgi

There will be memory overflow problems, when the recursion of key embeddings is not much

@lsm1103 if you still have problems, please follow the new issue template step by step. Without it, and all the information in it is much more difficult to help you. :coffee:
Given that, I will close this one now.


[IQE]: Health Data Report File Stat metric for working set does not capture the preferences file count opened from debug menu in the w

Steps:

Launch Bracekts
Open preferences file from debug menu
Open Health Data Report

Result : Health Data Report File Stat metric for working set does not capture the preferences file count opened from debug menu, only openedFileExt count increases

The main idea of tracking file types is to get the distribution of standard file extensions used by user.
Since the Preferences is brackets centric, this will not affect the aggregate metric we want to track. So this won't affect the tracking requirements.
Closing as never fix.

@abose But don't we want to track, how many users are actualy making changes in the preferences file for which have brought a change and included default preferences file as well. We would definitely want to know the no of users making changes to their prefernces.

The main intent is to get an approximate distribution of standard file types opened by the user. This metric is not intended to track the preferences file usage.
We only track the file extension right[say js].

Got your point but I opened a json file which is not trackable how about that. And I understand that its the exception for preferences file which supposedly is json but we should have tracked it.
However I believe our intent is to capture any file that is being used in the editor be it prefernces or any other file. Up to you to decide :+1: :)


Geocode does not offer bounds

I'm submitting a ...  (check one with "x")
[ ] question
[ ] any problem or bug report
[x] feature request
The plugin version:  (check one with "x")
[ ] 2.0-beta3 (github)
[x] 2.0 (npm)
cordova information:  (run $> cordova plugin list)
com.googlemaps.ios 2.4.0 "Google Maps SDK for iOS"
cordova-plugin-add-swift-support 1.7.0 "AddSwiftSupport"
cordova-plugin-compat 1.1.0 "Compat"
cordova-plugin-console 1.0.7 "Console"
cordova-plugin-datepicker 0.9.3 "DatePicker"
cordova-plugin-device 1.1.6 "Device"
cordova-plugin-facebook4 1.9.1 "Facebook Connect"
cordova-plugin-geolocation 2.4.3 "Geolocation"
cordova-plugin-globalization 1.0.7 "Globalization"
cordova-plugin-google-analytics 1.8.3 "Google Universal Analytics Plugin"
cordova-plugin-googlemaps 2.0.0 "cordova-plugin-googlemaps"
cordova-plugin-nativegeocoder 1.0.2 "NativeGeocoder"
cordova-plugin-recentscontrol 1.1.0 "RecentsControl"
cordova-plugin-splashscreen 4.0.3 "Splashscreen"
cordova-plugin-statusbar 2.2.3 "StatusBar"
cordova-plugin-whitelist 1.3.2 "Whitelist"
ionic-plugin-deploy 0.6.7 "IonicDeploy"
ionic-plugin-keyboard 2.2.1 "Keyboard"

If you use @ionic-native/google-maps, please show me the package.json
"@ionic-native/google-maps": "^4.3.0",

Current behavior:
Geocoding does not have the bounds parameter, which is crucial for nice results around an area.
Expected behavior:
Geocoding to be able to accept bounds with the address, so it will be more accurate

Please ask to Google and Apple.


Relative paths instead of absolute one when building

Describe the bug
I was making a new site using Vite which I love as a framework probs the best but when I ran npm run build and deployed my site to fleek (IPFS) I noticed a crucial error that broke my entire site the Vite frame uses absolute paths ie. /assets/index.js instead of ./assests/index.js, well technically my site octawack.on.fleek.co  works well but the IPFS support in brave auto replaces to the gateways which fails so I was wondering if the Vite team could set some option to fix I get that in most websites don't need this but there are edge cases I am so sorry  if this already exists as an issue or option
Reproduction
https://fleek.ipfs.io/ipfs/QmNWhGuQ47bYLajmPaA2y4w47P84SNGHwLGWLY5TuPUCEN/
Steps to reproduce
No response
System Info
fleek hosting

Used Package Manager
npm
Logs
--
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[ ] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

I guess you can use base: './'.
https://vitejs.dev/config/shared-options.html#base


Error: malformed ws or wss URL

Hello
I get this error below when i run terraform plan.
Planning failed. Terraform encountered an error while generating this plan.
Error: malformed ws or wss URL
│
│   with provider["registry.terraform.io/terra-farm/xenorchestra"],
│   on providers.tf line 11, in provider "xenorchestra":
│   11: provider "xenorchestra" {
This only happens when i use XOA_URL, XOA_USER and XOA_PASSWORD environment variables. When i replace the variables with the actual values eg. url = "wss://192.168.xx.xx" etc, the terraform plan works as expected.
This is my terraform code:
  # Instruct terraform to download the provider on `terraform init`
  terraform {
    required_providers {
      xenorchestra = {
        source = "terra-farm/xenorchestra"
      }
    }
  }

  # Configure the XenServer Provider
  provider "xenorchestra" {
    # Must be ws or wss
    url      = "XOA_URL"               # Or set XOA_URL environment variable
    username = "XOA_USER"              # Or set XOA_USER environment variable
    password = "XOA_PASSWORD"          # Or set XOA_PASSWORD environment variable

    # This is false by default and
    # will disable ssl verification if true.
    # This is useful if your deployment uses
    # a self signed certificate but should be
    # used sparingly!
    insecure = true              # Or set XOA_INSECURE environment variable to any value
  }

Any suggestions on what the issue could be?

@GilbertK99 the url, username and password HCL arguments should be omitted when you want it to fall back to the environment variables. They do not provide a way to tell terraform which environment variables to look at.
See that they are specified for each one: url, username, password.
Assuming the code you mentioned above is what you are testing with, this would be expected behavior (XOA_URL is not a valid websocket server address).

Thank you so much! @ddelnano @ackjewtn I understand how its meant to work now.  My mistake was including the HCL arguments in the code.
VS Code kinda fooled me into thinking the attribute is required due to it showing some code errors as shown on this screenshot below.


[5.4] @lang directive is not working with json lang file

@lang Blade directive is not working. This PR tries to adjust @lang directive with new "getFromJson" method. If json is not set then "get" method will be called as fallback.

Use the trans directive.

Hey @taylorotwell  there is no trans directive in Laravel5.4 I do not see that directive in documentation or in any part of the code. I have only seen this directive at laravel-news post which was written by @themsaid . I also confirm that trans directive not working (because there is not trans directive I think) on my Laravel5.4.11 installation.

Thanks


Remove very white and black colors from the color pool for subreddit accent colors

The subreddit color picking algorithm should only match to material colors from 400 to 700. That will ensure that the colors chosen don't conflict with lighter or darker themes.

Done, have pruned a lot of colors out and made all accents/main colors readable. Also took out gray from the auto-coloring system choices

Sorry to reopen this, but I'm still getting some darker colors. It looks in that commit that a lot of 800/900 color variants are still available.

I don't think it's worth removing those colors, I tested them on black and they were still readable. Maybe some of the dark blue ones could be removed but the colored ones are okay imo

I don't think this is an issue anymore


add public query results on plots for Azure D8lds v5

@harsha-simhadri  Hi, harsha-simhadri, May I ask why there is no DHQ algorithm result in the neurips23/filter/plot_public_queries_AzureD8lds_v5.png you just updated? Thank you very much.

@harsha-simhadri Hi, harsha-simhadri, May I ask why there is no DHQ algorithm result in the neurips23/filter/plot_public_queries_AzureD8lds_v5.png you just updated? Thank you very much.

@SDU-L  Thanks for pointing this out. This PR is still in draft mode. I have not completed all the runs. I am still uploading data. I will change the status from draft PR to PR when all runs complete.

@SDU-L  I added the DHQ plot. Does it look OK to you?

@harsha-simhadri
There is no entry of NGT in the figure. Is there  any reason for this?

@harsha-simhadri There is no entry of NGT in the figure. Is there any reason for this?

Its on oversight. Will look into this. I could not run your entry on all machines. This must be from one of those machines where it failed.

Its on oversight. Will look into this. I could not run your entry on all machines. This must be from one of those machines where it failed.

Did you run this last commit? Since NGT was updated after our submission before the deadline, you should rebuild it and avoid using the cache of NGT source code.

Update: failed on 2 more machines. Onto a third. Will update.

In addition, I would like you to confirm the following messages in the build log. In particular, the commit number of NGT source must be the same as that in your server's log.
Step 6/11 : RUN cd NGT && git log -n 1
 ---> Running in adc04f274b08
commit 39c584f6f5c69d9afc373bbba27552296235320f
Author: Masajiro Iwasaki<EMAIL_ADDRESS>Date:   Mon Oct 30 18:45:37 2023 +0000

Hello @harsha-simhadri,
I've noticed that the PR is now open, and I just have some concerns because I observed that the plot has been updated in this 1afc681d8df since the last time I viewed it a few days ago in the 1cb63a847.
It appears that three algorithms (namely puck, puck-fizz, and vamana) have been added to the figure. However, when comparing the two plots, it shows that all the algorithms present in the previous commit maintain the same performance at the pixel-level, except for pyanns. In this instance, the curve has shifted by 20% (approximately to 1/5 grid box) when comparing the two plots, while the performance of the others remains unchanged. Is there any reason for this? Thanks.

@SDU-L I added the DHQ plot. Does it look OK to you?

@harsha-simhadri  That’s ok.Thank you very much.

@harsha-simhadri on the filter track, there are two entries that seem duplicates: mysteryann and mysteryann-dif. is this intentional?

@harsha-simhadri on the filter track, there are two entries that seem duplicates: mysteryann and mysteryann-dif. is this intentional?

I thought these were two submissions from the same team. As the organizer in charge of the track, please decide whether to accept two submission or only on.

Update: failed on 2 more machines. Onto a third. Will update.

In addition, I would like you to confirm the following messages in the build log. In particular, the commit number of NGT source must be the same as that in your server's log.
Step 6/11 : RUN cd NGT && git log -n 1
 ---> Running in adc04f274b08
commit 39c584f6f5c69d9afc373bbba27552296235320f
Author: Masajiro Iwasaki<EMAIL_ADDRESS>Date:   Mon Oct 30 18:45:37 2023 +0000

Yes, this is the commit I cloned and ran on the extra machines. It failed again. I am trying one more time.

@harsha-simhadri
I use Linux (ubuntu 22.04) with Azure Standard D8lds v5. On the instance, building the NGT index never fails. I think there is definitely something different between my azure server and your azure server. Another try will also fail. Which instance do you use?

@harsha-simhadri on the filter track, there are two entries that seem duplicates: mysteryann and mysteryann-dif. is this intentional?

I thought these were two submissions from the same team. As the organizer in charge of the track, please decide whether to accept two submission or only on.

@harsha-simhadri I meant the OOD track (not the filter track), I believe this is your track.
There are actually two pairs of submissions that look like duplicates: {mysteryann and mysteryann-dif} and {puck and puck-fizz}.
Another issue is that some submissions have more than 10 sets of hyperparameters, where most submissions did adhere to that rule. We don't want this to end up being the deciding factor as to who is the winner of a track.
Also, the csv results file for the ood track seems like the wrong file (it is some binary file and not csv).

@harsha-simhadri on the filter track, there are two entries that seem duplicates: mysteryann and mysteryann-dif. is this intentional?

I thought these were two submissions from the same team. As the organizer in charge of the track, please decide whether to accept two submission or only on.

@harsha-simhadri I meant the OOD track (not the filter track), I believe this is your track.
There are actually two pairs of submissions that look like duplicates: {mysteryann and mysteryann-dif} and {puck and puck-fizz}.

I believe both teams take the public query set for text2image into account for their second solution (-dif and -fizz).

Another issue is that some submissions have more than 10 sets of hyperparameters, where most submissions did adhere to > that rule. We don't want this to end up being the deciding factor as to who is the winner of a track.

I checked for this for the ones that I merged, do you have a list of offending submissions? I will check one more time otherwise.

List of the offending submissions:
'neurips23/ood/mysteryann-dif/config.yaml':
text2image-10M.mysteryann-dif: 'query-args' count = 14
'neurips23/ood/mysteryann/config.yaml':
text2image-10M.mysteryann: 'query-args' count = 16
'neurips23/ood/pyanns/config.yaml':
text2image-10M.pyanns: 'query-args' count = 12
'neurips23/sparse/nle/config.yaml':
sparse-small.NLE-Full: 'query-args' count = 25
'neurips23/sparse/nle/config.yaml':
sparse-1M.NLE-Full: 'query-args' count = 25
'neurips23/sparse/nle/config.yaml':
sparse-full.NLE-Full: 'query-args' count = 25
'neurips23/sparse/shnsw/config.yaml':
sparse-full.shnsw: 'query-args' count = 13
'neurips23/filter/faiss/config.yaml':
yfcc-10M.faiss: 'query-args' count = 18
'neurips23/filter/puck/config.yaml':
yfcc-10M.puck: 'query-args' count = 12
On Thu, Nov 9, 2023 at 9:33 AM Martin Aumüller @.***>
wrote:

@harsha-simhadri https://github.com/harsha-simhadri on the filter
track, there are two entries that seem duplicates: mysteryann and
mysteryann-dif. is this intentional?
I thought these were two submissions from the same team. As the organizer
in charge of the track, please decide whether to accept two submission or
only on.
@harsha-simhadri https://github.com/harsha-simhadri I meant the OOD
track (not the filter track), I believe this is your track.
There are actually two pairs of submissions that look like duplicates:
{mysteryann and mysteryann-dif} and {puck and puck-fizz}.
I believe both teams take the public query set for text2image into account
for their second solution (-dif and -fizz).
Another issue is that some submissions have more than 10 sets of
hyperparameters, where most submissions did adhere to > that rule. We don't
want this to end up being the deciding factor as to who is the winner of a
track.
I checked for this for the ones that I merged, do you have a list of
offending submissions? I will check one more time otherwise.
—
Reply to this email directly, view it on GitHub
https://github.com/harsha-simhadri/big-ann-benchmarks/pull/233#issuecomment-1803297493,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWJRULFYGKV7QX2L7YTJ7VDYDSBOFAVCNFSM6AAAAAA66BGTX6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBTGI4TONBZGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

@harsha-simhadri on the filter track, there are two entries that seem duplicates: mysteryann and mysteryann-dif. is this intentional?

I thought these were two submissions from the same team. As the organizer in charge of the track, please decide whether to accept two submission or only on.

@harsha-simhadri I meant the OOD track (not the filter track), I believe this is your track. There are actually two pairs of submissions that look like duplicates: {mysteryann and mysteryann-dif} and {puck and puck-fizz}. Another issue is that some submissions have more than 10 sets of hyperparameters, where most submissions did adhere to that rule. We don't want this to end up being the deciding factor as to who is the winner of a track.
Also, the csv results file for the ood track seems like the wrong file (it is some binary file and not csv).

puck-fizz could be removed from the results, as it misunderstood the concept of query train datasets. I'm sorry for the mistake.

@harsha-simhadri on the filter track, there are two entries that seem duplicates: mysteryann and mysteryann-dif. is this intentional?

I thought these were two submissions from the same team. As the organizer in charge of the track, please decide whether to accept two submission or only on.

@harsha-simhadri I meant the OOD track (not the filter track), I believe this is your track. There are actually two pairs of submissions that look like duplicates: {mysteryann and mysteryann-dif} and {puck and puck-fizz}. Another issue is that some submissions have more than 10 sets of hyperparameters, where most submissions did adhere to that rule. We don't want this to end up being the deciding factor as to who is the winner of a track.
Also, the csv results file for the ood track seems like the wrong file (it is some binary file and not csv).

puck-fizz could be removed from the results, as it misunderstood the concept of query train datasets. I'm sorry for the mistake.

removed

@harsha-simhadri I use Linux (ubuntu 22.04) with Azure Standard D8lds v5. On the instance, building the NGT index never fails. I think there is definitely something different between my azure server and your azure server. Another try will also fail. Which instance do you use?

I use the same image on the same machine. I had to remove every other entry, prune down a lot of other stuff to run your entry. I added it to the plot. In the future, I would request that an entry not push the DRAM requirement so far to the limit as some natural variation on a machineis to be expected when running all entries. Thanks for your patience.


readthedocs not using latest commit for build

Details

Project URL: https://github.com/power-system-simulation-toolbox/psst
Build URL (if applicable): https://readthedocs.org/projects/psst
Read the Docs username (if applicable):

Expected Result
On hitting the build button, I expect to have the latest commit built
Actual Result
It uses a previous commit or a commit that I removed from the branch. I've tried this multiple times on different days and no luck. It also seems be using a different commit for every build.

@kdheepak can you provide a more specific and detailed example? what's the url of the build? which should be the correct commit and which one is RTD using instead?

Closing due to inactivity


How to send massage to chat

How to send massage to chat, where located my bot?
I have string array and I want to send it to chat, nothing more.
pls tell me/Thx\ noob

package main

import (
	tb "gopkg.in/tucnak/telebot.v2"
)

type recipientString string
func (r recipientString) Recipient() string {
	return r
}

func main() {
	b, _ := tb.NewBot(tb.Settings{Token:  "TOKEN_HERE"})
        b.Send(recipientString("@stek29"), "hello")
}

this should work


Can we disable Travis tests?

It's not clear what the development status of this package is, but in any case I'd like to disable Travis tests for this package.

Yes, we can disable Travis tests (and archive this repo). All the code in here was merged back into legacypipe nearly two years ago.

Yes, we can disable Travis tests (and archive this repo). All the code in here was merged back into legacypipe nearly two years ago.


no matches found: handcuffs:migrate[phase]

bundle exec rake handcuffs:migrate[all]
zsh: no matches found: handcuffs:migrate[all]

I'm running into the above issue. I have gem "handcuffs", "~> 1.1.1" in my gemfile.
I've also tried gem install handcuffs followed by rake handcuffs:migrate[all] which has the same issue.

Hey @amayernc! This is actually zsh interpreting the [] as special characters, if you wrap the command in quotes it should work fine.
bundle exec rake 'handcuffs:migrate[all]'

Thanks! Should I put in a PR with a readme update?

Oh man, I already went and opened one: https://github.com/procore/handcuffs/pull/12


Add support for ARM

@jsignell All checks have passed. You can review it now.

@jsignell @giswqs any chance we could merge this? I had opened https://github.com/conda-forge/conda-forge-pinning-feedstock/pull/4696 but didn't check this repo first to see this pr

Fine by me!


Add recursive support to list in http

This PR adds recursive option to http, to align with the API.
This solves the 4th todo in #46

I would say again that HTTP is just a communication protocol and not a filesystem. By a small chance WebDAV is a filesystem-like protocol built on top of HTTP, but it's almost overtaken by CIFS. That said, the HTTP wrapper should be removed from this library.

close in favor of #51


Incorrect SDK types for MediaQueryList.addListener

The SDK has the signature for MediaQueryList.addListener as void Function(dynamic Function(Event)), as it's expecting the parameter to be a MediaQueryListEvent. This is correct in Chrome and Firefox, but in Safari and Edge, the listener method is called with a MediaQueryList, and MediaQueryListEvent doesn't exist.
Both MediaQueryList and MediaQueryListEvent have a boolean matches property, but they don't share a common interface.

Dart SDK Version (dart --version)
2.7.0-edge+google3-v2

Whether you are using Windows, MacOSX, or Linux (if applicable)
Linux

Whether you are using Chrome, Safari, Firefox, Edge (if applicable)
Safari, Edge

We probably need to type this as:
void Function(dynamic Function(Object))
then.

I'm closing this issue as likely now obsolete. That said, I'd like to share some general comments that are very applicable here.
In the last few years we have developed and improved the JS-interop solution for Dart so that it can be used to interact with browser APIs directly. Any API that is not exposed properly can be worked around with a direct JS-interop access instead. We also are moving away from dart:html, and have evolved package:web as a replacement. It is based on JS-interop, generated from the Web IDLs (rather than Chrome IDLs) so they are likely to have fewer browser incompatibilities, and it will be supported on Wasm (unlike dart:html).


Tests: fix general confusion about supported vs enabled extensions

Various tests check for the physical device supporting an extension to gate some piece of logic, but don't bother to actually enable it.

I am actually fixing this now.  Added validation for enabled extensions and now get 500+ unexpected errors in the LVT.

Just put up PR #1843 that at least partially addresses this issue.  I don't think it helps with Mark's 500+ errors.

The errors manifested if you tried to verify at getprocaddress time, which is a bad idea.  Shifted to doing this at entrypoint-call-time.


Delay on Click Commands

This script is an actual game-changer. Thank you for sharing it. I was just wondering if it is possible to reduce the delay on the click commands as it is quite noticeable. Every other command (double_click, release, and so on) works as intended with no delay, from what I can see. Thanks again for the awesome script.

Since there are multiple possible actions there is no way for me to do this.
If there is any good idea or practical case I will try it.
About noticeable delay you can try input-doubleclick-time=200 or lower value, maybe 150.

No problem. Your idea of lowering the input-doubleclick-time did the trick. I put it to 125, and there is a notable difference. Thank you so much! I'll go ahead and close the comment as this helped decreased the delay.


Edit description of "ℹ" and "⚠"

Hi,
Sorrt that I forgot to edit the desciption last time, so I edit it based on the comment

lgtm 😊

fyi: I slightly changed the wording. Hope that was okay, because I forgot to ask before merging. 😉

No worry 😉


fetch trunk from TFS collection issues.

While fetch trunk from TFS collection i faced this issues.
error:
=>error:TF246021: An error occurred while processing your request.
Technical information (for administrator):
SQL Server Error: 64

fetch truck from TFS collection issues.

git-tfs can't be used to fetch trucks ;)
It's not an error caused by git-tfs and it seems more a problem with a tfs workspace. See this stackoverflow post:
https://stackoverflow.com/questions/14746267/how-to-solve-tfs-error-tf246021-and-sql-server-error-500200-while-checking-in

Thanks mate. it was TFS issues . :+1:


Concurrent Access Exception during serialization based ticket replication

JBoss Cache any any other replicated ticket cache serialize the tickets. In CAS 3, Tickets in the Registry sometimes contain non-transient direct references to other tickets instead of just IDs since an ID requires a lookup which in turn requires a reference to the Registry itself. A Cache replicates by serializing the ticket which incidentally then serializes all tickets the Ticket references and all collections within that ticket. Then the blob of serialized data is transmitted to the other node and deserialized, although only the original Ticket is really used and any referenced tickets are ignored on the receiving node. Unfortunately, a Browser can open several Tabs simultaneously, requesting multiple STs concurrently in separate threads on the same server. As each ST is created, the Registry tries to replicate it to the other nodes, and that serializes the Ticket and its directly linked parents. Unfortunately, the parent TGT is maintaining a collection of ST children, and the creation of a second ST tries to add a new entry in the collection while the TGT and its collection are being serialized by the replication of the first ST to another node. This can throw a ConcurrentAccess exception: modifying the collection of child STs in the TGT while another thead is in the middle of enumerating the collection (the enumeration is built into the Serialization process). Potential solutions involve locking the Registry during Ticket creation, marking the Ticket references as transient so they don't serialize, replace all direct references to Tickets with IDs that are found with a registry lookup. Essentially the problem is built into JBoss Cache, Ehcache, Memcached, or any other replication technology that serializes because these technologies are not really designed to cache objects that have references to other cached objects creating uncontrollable serialization chains. Should at least be considered in the Registry rewrite in CAS 4.
Environment: Any clustered TicketRegistry (other than JPA). Noted in JBoss Cache.
Reported by: Howard Gilbert, id: gilbert
Created: Tue, 29 Mar 2011 07:52:50 -0700
Updated: Tue, 29 Mar 2011 08:04:41 -0700
JIRA: https://issues.jasig.org/browse/CAS-962
Because of the Single SignOut child pointers, it may be necessary to synchronize updates to a Ticket tree with or without serialization. To avoid deadlock, you want to find one clean lock. Based on hierarchy, the unique object is the top level (original login, non-proxy) TGT at the top of the tree. We addressed the problem by configuring JBoss Cache to do synchronous replication and we lock the top level TGT when making changes or adding tickets anywhere under that TGT. If you need to lock, that is the safe place to do it.

Closing due to inactivity. May revisit later.


refactor: Refactor of hocr functions and fixing lost changes

Note - the error for the Samples might actually need fixing in the document.py wrapper. Not sure if the paths all line up correctly for the template when using the compiled library


j3l

[Enter feedback here]

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

ID: 35f8441a-d145-c5ce-36ee-49058d0c09b4
Version Independent ID: 49a7f4be-4d96-8b7b-537d-3a758d0a4beb
Content: Change a drive letter
Content Source: WindowsServerDocs/storage/disk-management/change-a-drive-letter.md
Product: windows-server
Technology: storage
GitHub Login: @JasonGerend
Microsoft Alias: jgerend

#assign:xelu86

Hey @j3lli215,
Thanks again for contacting Microsoft. We value your feedback.
We're unable to determine what the intent of your question is. If there are any errors or areas of improvement with said documentation, please let us know so we may better assist.
We're closing this issue but please feel free to reopen it and advise us what revisions may be needed. Thank you and have a most pleasant day. #please-close


Go build - Cannot find CLI packages

Description
Initially building sources with go build does not find cli packages:
ui\ui.go:6:2: cannot find package "." in:
        C:\Users\awindowsuser\go\src\github.com\cloudfoundry\cli\cf\i18n
ui\ui.go:7:2: cannot find package "." in:
        C:\Users\awindowsuser\go\src\github.com\cloudfoundry\cli\cf\terminal
clients\create_service_instance.go:12:2: cannot find package "." in:
        C:\Users\awindowsuser\go\src\github.com\cloudfoundry\cli\plugin
commands\base_command.go:9:2: cannot find package "." in:
        C:\Users\awindowsuser\go\src\github.com\cloudfoundry\cli\plugin\models

After installing those manually there is a go related conflict, which is suggested to be solved by go mod tidy and go mod vendor. I am no go expert so this may be the wrong way to go. but when doing so this leads to another issue:
# cf-html5-apps-repo-cli-plugin/ui
ui\ui.go:17:37: not enough arguments in call to terminal.NewTeePrinter
        have ()
        want (io.Writer)
ui\ui.go:18:21: not enough arguments in call to terminal.NewUI
        have (*os.File, *terminal.TeePrinter)
        want (io.Reader, io.Writer, terminal.Printer, trace.Printer)
ui\ui.go:24:28: cannot use bucket (type *[]string) as type io.Writer in argument to teePrinter.SetOutputBucket:
        *[]string does not implement io.Writer (missing Write method)
ui\ui.go:59:15: too many arguments in call to ui.Ask
        have (string, []interface {}...)
        want (string)
ui\ui.go:64:19: too many arguments in call to ui.Confirm
        have (string, []interface {}...)
        want (string)
ui\ui.go:79:4: ui.PanicQuietly undefined (type terminal.UI has no field or method PanicQuietly)
ui\ui.go:89:17: cannot use ui.Table(headers) (type *terminal.UITable) as type terminal.Table in return argument

This is caused because a different version is used, then the one provided in the vendor folder.
Environment

Plugin version (e.g. 1.3.0) - Lates commit: b2739467857b59052650b37cad2a205c165f62b0
OS (macOS/Windows) - Windows
SAP CF Landscape (e.g. Canary) - cf version 6.47.2+d526c2cb3.2019-11-05
IaaS provider (e.g. AWS) - AWS
Region (e.g. eu10) - eu10

CLI Output
None, as this issue is about the build.

Hi @wilhelmbecker,
Thanks for reporting an issue.
All dependencies of HTML5 CLI plugin are embedded into the project and located in vendor folder of the project. There are no external dependencies to files that are not inside project folder.
Can you please post here output of go version, so that I will be able to reproduce the issue with the same GO version and OS.

Thank you for your response!
The output is:
go version go1.13.5 windows/amd64

Hi @wilhelmbecker,
I tried to reproduce the issue you are facing. Here are the steps that I've done:

Spin brand new Window 8.1 VM
Install GIT
Install GO 1.13.5 (with msi)
Create folder C:\Users\<my_user>\go\src
Change working directory to just created folder cd C:\Users\<my_user>\go\src
Clone CLI plugin repo git clone https://github.com/SAP/cf-html5-apps-repo-cli-plugin.git
Change working directory to project root cd C:\Users\<my_user>\go\src\cf-html5-apps-repo-cli-plugin
Build project go build

The build finished successfully without any errors. So, I guess the problem may be with the environment you have. What I suggest you to try:

Make sure the folder in C:\Users\awindowsuser\go\src\ is exactly cf-html5-apps-repo-cli-plugin. If you used download option instead of git clone, you'll usually have -master suffix in the name of the folder. This may cause an issue for GO to resolve package name. Once the name is OK, cd to it an try go build once again.
If the first option didn't help. Temporary move or rename your C:\Users\awindowsuser\go\src\to some other name. Create src folder once agin (it should be empty now). Clone the repo of CLI plugin. If you have GOPATH environment variable set, delete it.

 Can this cause the issue?
Secondly here my answer to your two suggestions:

I used git clone  and the folder name is correct (double checked this  of course!)
First I had to remove the GOPATH variable for my local user. When executed as described (renamed src - >src_old, mkdir src, cd src, git clone, cd cfcf-html5-apps-repo-cli-plugin) the build fails with the log:

C:\Users\<my_user>\go\src\cf-html5-apps-repo-cli-plugin>go build
commands\html5_push_command.go:4:2: cannot find package "archive/zip" in any of:
        C:\Users\<my_user>\go\src\cf-html5-apps-repo-cli-plugin\vendor\archive\zip (vendor tree)
        C:\Users\<my_user>\go\src\archive\zip (from $GOROOT)
        ($GOPATH not set. For more details see: 'go help gopath')
vendor\github.com\cloudfoundry\cli\cf\terminal\ui.go:4:2: cannot find package "bufio" in any of:
        C:\Users\<my_user>\go\src\cf-html5-apps-repo-cli-plugin\vendor\bufio (vendor tree)
        C:\Users\<my_user>\go\src\bufio (from $GOROOT)
        ($GOPATH not set. For more details see: 'go help gopath')
clients\upload_app_host.go:4:2: cannot find package "bytes" in any of:
        C:\Users\<my_user>\go\src\cf-html5-apps-repo-cli-plugin\vendor\bytes (vendor tree)
        C:\Users\<my_user>\go\src\bytes (from $GOROOT)
        ($GOPATH not set. For more details see: 'go help gopath')
vendor\github.com\cloudfoundry\cli\cf\resources\i18n_resources.go:19:2: cannot find package "compress/gzip" in any of:
        C:\Users\<my_user>\go\src\cf-html5-apps-repo-cli-plugin\vendor\compress\gzip (vendor tree)
        C:\Users\<my_user>\go\src\compress\gzip (from $GOROOT)
        ($GOPATH not set. For more details see: 'go help gopath')
vendor\github.com\blang\semver\sql.go:4:2: cannot find package "database/sql/driver" in any of:
        C:\Users\<my_user>\go\src\cf-html5-apps-repo-cli-plugin\vendor\database\sql\driver (vendor tree)
        C:\Users\<my_user>\go\src\database\sql\driver (from $GOROOT)
        ($GOPATH not set. For more details see: 'go help gopath')
vendor\github.com\nicksnyder\go-i18n\i18n\translation\template.go:5:2: cannot find package "encoding" in any of:
        C:\Users\<my_user>\go\src\cf-html5-apps-repo-cli-plugin\vendor\encoding (vendor tree)
        C:\Users\<my_user>\go\src\encoding (from $GOROOT)
        ($GOPATH not set. For more details see: 'go help gopath')
vendor\github.com\cloudfoundry\cli\cf\configuration\core_config\access_token.go:4:2: cannot find package "encoding/base64" in any of:
        C:\Users\<my_user>\go\src\cf-html5-apps-repo-cli-plugin\vendor\encoding\base64 (vendor tree)
        C:\Users\<my_user>\go\src\encoding\base64 (from $GOROOT)
        ($GOPATH not set. For more details see: 'go help gopath')
clients\create_service_instance.go:6:2: cannot find package "encoding/json" in any of:
        C:\Users\<my_user>\go\src\cf-html5-apps-repo-cli-plugin\vendor\encoding\json (vendor tree)
        C:\Users\<my_user>\go\src\encoding\json (from $GOROOT)
        ($GOPATH not set. For more details see: 'go help gopath')
clients\create_service_instance.go:7:2: cannot find package "errors" in any of:
        C:\Users\<my_user>\go\src\cf-html5-apps-repo-cli-plugin\vendor\errors (vendor tree)
        C:\Users\<my_user>\go\src\errors (from $GOROOT)
        ($GOPATH not set. For more details see: 'go help gopath')
commands\html5_delete_command.go:7:2: cannot find package "flag" in any of:
        C:\Users\<my_user>\go\src\cf-html5-apps-repo-cli-plugin\vendor\flag (vendor tree)
        C:\Users\<my_user>\go\src\flag (from $GOROOT)
        ($GOPATH not set. For more details see: 'go help gopath')
log\log.go:4:2: cannot find package "fmt" in any of:
        C:\Users\<my_user>\go\src\cf-html5-apps-repo-cli-plugin\vendor\fmt (vendor tree)
        C:\Users\<my_user>\go\src\fmt (from $GOROOT)
        ($GOPATH not set. For more details see: 'go help gopath')
vendor\github.com\cloudfoundry\cli\cf\resources\i18n_resources.go:21:2: cannot find package "io" in any of:
        C:\Users\<my_user>\go\src\cf-html5-apps-repo-cli-plugin\vendor\io (vendor tree)
        C:\Users\<my_user>\go\src\io (from $GOROOT)
        ($GOPATH not set. For more details see: 'go help gopath')
clients\get_file_content.go:6:2: cannot find package "io/ioutil" in any of:
        C:\Users\<my_user>\go\src\cf-html5-apps-repo-cli-plugin\vendor\io\ioutil (vendor tree)
        C:\Users\<my_user>\go\src\io\ioutil (from $GOROOT)
        ($GOPATH not set. For more details see: 'go help gopath')
vendor\github.com\cloudfoundry\cli\cf\trace\trace.go:6:2: cannot find package "log" in any of:
        C:\Users\<my_user>\go\src\cf-html5-apps-repo-cli-plugin\vendor\log (vendor tree)
        C:\Users\<my_user>\go\src\log (from $GOROOT)
        ($GOPATH not set. For more details see: 'go help gopath')
vendor\gopkg.in\yaml.v2\decode.go:7:2: cannot find package "math" in any of:
        C:\Users\<my_user>\go\src\cf-html5-apps-repo-cli-plugin\vendor\math (vendor tree)
        C:\Users\<my_user>\go\src\math (from $GOROOT)
        ($GOPATH not set. For more details see: 'go help gopath')
clients\upload_app_host.go:8:2: cannot find package "mime/multipart" in any of:
        C:\Users\<my_user>\go\src\cf-html5-apps-repo-cli-plugin\vendor\mime\multipart (vendor tree)
        C:\Users\<my_user>\go\src\mime\multipart (from $GOROOT)
        ($GOPATH not set. For more details see: 'go help gopath')
vendor\github.com\cloudfoundry\cli\plugin\cli_connection.go:6:2: cannot find package "net" in any of:
        C:\Users\<my_user>\go\src\cf-html5-apps-repo-cli-plugin\vendor\net (vendor tree)
        C:\Users\<my_user>\go\src\net (from $GOROOT)
        ($GOPATH not set. For more details see: 'go help gopath')
clients\delete_service_content.go:6:2: cannot find package "net/http" in any of:
        C:\Users\<my_user>\go\src\cf-html5-apps-repo-cli-plugin\vendor\net\http (vendor tree)
        C:\Users\<my_user>\go\src\net\http (from $GOROOT)
        ($GOPATH not set. For more details see: 'go help gopath')
vendor\github.com\cloudfoundry\cli\plugin\cli_connection.go:7:2: cannot find package "net/rpc" in any of:
        C:\Users\<my_user>\go\src\cf-html5-apps-repo-cli-plugin\vendor\net\rpc (vendor tree)
        C:\Users\<my_user>\go\src\net\rpc (from $GOROOT)
        ($GOPATH not set. For more details see: 'go help gopath')
clients\upload_app_host.go:10:2: cannot find package "net/textproto" in any of:
        C:\Users\<my_user>\go\src\cf-html5-apps-repo-cli-plugin\vendor\net\textproto (vendor tree)
        C:\Users\<my_user>\go\src\net\textproto (from $GOROOT)
        ($GOPATH not set. For more details see: 'go help gopath')
clients\get_token.go:9:2: cannot find package "net/url" in any of:
        C:\Users\<my_user>\go\src\cf-html5-apps-repo-cli-plugin\vendor\net\url (vendor tree)
        C:\Users\<my_user>\go\src\net\url (from $GOROOT)
        ($GOPATH not set. For more details see: 'go help gopath')
log\log.go:5:2: cannot find package "os" in any of:
        C:\Users\<my_user>\go\src\cf-html5-apps-repo-cli-plugin\vendor\os (vendor tree)
        C:\Users\<my_user>\go\src\os (from $GOROOT)
        ($GOPATH not set. For more details see: 'go help gopath')
vendor\github.com\cloudfoundry\cli\cf\i18n\i18n.go:6:2: cannot find package "path" in any of:
        C:\Users\<my_user>\go\src\cf-html5-apps-repo-cli-plugin\vendor\path (vendor tree)
        C:\Users\<my_user>\go\src\path (from $GOROOT)
        ($GOPATH not set. For more details see: 'go help gopath')
vendor\github.com\cloudfoundry\cli\cf\configuration\config_disk_persistor_win.go:7:2: cannot find package "path/filepath" in any of:
        C:\Users\<my_user>\go\src\cf-html5-apps-repo-cli-plugin\vendor\path\filepath (vendor tree)
        C:\Users\<my_user>\go\src\path\filepath (from $GOROOT)
        ($GOPATH not set. For more details see: 'go help gopath')
vendor\github.com\cloudfoundry\cli\cf\models\application.go:4:2: cannot find package "reflect" in any of:
        C:\Users\<my_user>\go\src\cf-html5-apps-repo-cli-plugin\vendor\reflect (vendor tree)
        C:\Users\<my_user>\go\src\reflect (from $GOROOT)
        ($GOPATH not set. For more details see: 'go help gopath')
vendor\gopkg.in\yaml.v2\encode.go:7:2: cannot find package "regexp" in any of:
        C:\Users\<my_user>\go\src\cf-html5-apps-repo-cli-plugin\vendor\regexp (vendor tree)
        C:\Users\<my_user>\go\src\regexp (from $GOROOT)
        ($GOPATH not set. For more details see: 'go help gopath')
vendor\github.com\cloudfoundry\cli\cf\terminal\color.go:7:2: cannot find package "runtime" in any of:
        C:\Users\<my_user>\go\src\cf-html5-apps-repo-cli-plugin\vendor\runtime (vendor tree)
        C:\Users\<my_user>\go\src\runtime (from $GOROOT)
        ($GOPATH not set. For more details see: 'go help gopath')
vendor\github.com\blang\semver\sort.go:4:2: cannot find package "sort" in any of:
        C:\Users\<my_user>\go\src\cf-html5-apps-repo-cli-plugin\vendor\sort (vendor tree)
        C:\Users\<my_user>\go\src\sort (from $GOROOT)
        ($GOPATH not set. For more details see: 'go help gopath')
vendor\github.com\cloudfoundry\cli\plugin\plugin_shim.go:6:2: cannot find package "strconv" in any of:
        C:\Users\<my_user>\go\src\cf-html5-apps-repo-cli-plugin\vendor\strconv (vendor tree)
        C:\Users\<my_user>\go\src\strconv (from $GOROOT)
        ($GOPATH not set. For more details see: 'go help gopath')
clients\create_service_instance.go:9:2: cannot find package "strings" in any of:
        C:\Users\<my_user>\go\src\cf-html5-apps-repo-cli-plugin\vendor\strings (vendor tree)
        C:\Users\<my_user>\go\src\strings (from $GOROOT)
        ($GOPATH not set. For more details see: 'go help gopath')
vendor\github.com\cloudfoundry\cli\cf\configuration\core_config\config_repository.go:5:2: cannot find package "sync" in any of:
        C:\Users\<my_user>\go\src\cf-html5-apps-repo-cli-plugin\vendor\sync (vendor tree)
        C:\Users\<my_user>\go\src\sync (from $GOROOT)
        ($GOPATH not set. For more details see: 'go help gopath')
vendor\github.com\cloudfoundry\cli\cf\configuration\config_disk_persistor_win.go:8:2: cannot find package "syscall" in any of:
        C:\Users\<my_user>\go\src\cf-html5-apps-repo-cli-plugin\vendor\syscall (vendor tree)
        C:\Users\<my_user>\go\src\syscall (from $GOROOT)
        ($GOPATH not set. For more details see: 'go help gopath')
vendor\github.com\nicksnyder\go-i18n\i18n\translation\template.go:7:2: cannot find package "text/template" in any of:
        C:\Users\<my_user>\go\src\cf-html5-apps-repo-cli-plugin\vendor\text\template (vendor tree)
        C:\Users\<my_user>\go\src\text\template (from $GOROOT)
        ($GOPATH not set. For more details see: 'go help gopath')
vendor\github.com\cloudfoundry\cli\plugin\models\get_app.go:3:8: cannot find package "time" in any of:
        C:\Users\<my_user>\go\src\cf-html5-apps-repo-cli-plugin\vendor\time (vendor tree)
        C:\Users\<my_user>\go\src\time (from $GOROOT)
        ($GOPATH not set. For more details see: 'go help gopath')
vendor\github.com\blang\semver\range.go:6:2: cannot find package "unicode" in any of:
        C:\Users\<my_user>\go\src\cf-html5-apps-repo-cli-plugin\vendor\unicode (vendor tree)
        C:\Users\<my_user>\go\src\unicode (from $GOROOT)
        ($GOPATH not set. For more details see: 'go help gopath')
vendor\gopkg.in\yaml.v2\resolve.go:8:2: cannot find package "unicode/utf8" in any of:
        C:\Users\<my_user>\go\src\cf-html5-apps-repo-cli-plugin\vendor\unicode\utf8 (vendor tree)
        C:\Users\<my_user>\go\src\unicode\utf8 (from $GOROOT)
        ($GOPATH not set. For more details see: 'go help gopath')
vendor\golang.org\x\crypto\ssh\terminal\util_windows.go:22:2: cannot find package "unsafe" in any of:
        C:\Users\<my_user>\go\src\cf-html5-apps-repo-cli-plugin\vendor\unsafe (vendor tree)
        C:\Users\<my_user>\go\src\unsafe (from $GOROOT)
        ($GOPATH not set. For more details see: 'go help gopath')

Looks like in your initial attempt GO was not looking for packages in vendor folder of the project, and in the last one it can't find even standard built-in packages...
In GO 1.13 the package resolution was changed in favor of modules, which may be a reason of your issue. Try to put GOPATH back and set GO111MODULE=off to enable backward compatibility with previous GO versions package resolution mechanism.

Thank you very much!
This is the solution!
Just for other (windows) user with the same issue run set GO111MODULE=off before go build.
( I struggled a bit with the correct Syntax :sweat_smile: )


Update run_as_windows_service.md

When running as a Windows Service, Gogs is not started from the gogs.exe location, and to prevent Gogs storing and looking for files in System32, absolute paths should be used in app.ini

Thank you!


RPi Pico Error WARN: starting new transfer on already active ep 0 out

Describe the bug
Whenever I run a Pi Pico program (using the C/C++ SDK) that includes stdio_init_all();, it gives this error and frequently printf results in corrupted data being printed to the terminal.
To Reproduce
See the file I attached below. If you extract the archive and run snowflake/snowflake.uf2 in Wokwi, it will show the error in the serial terminal. The source is included as well as the build files (assuming the archive is extracted to /tmp/snowflake).
Expected behavior
I expect not to see this warning/error and, since this is a simulation not real hardware, there wouldn't be any data corruption issues (other than as a direct result of my code being buggy).
Environment (please complete the following information):

OS: Ubuntu 22.10
No browser, using VSCode
VSCode is Version 1.75.1 with Electron 19.1.9 and Chromium 102.0.5005.194. The Wokwi extension is version 1.3.0 (the latest at the time of writing). The RPi Pico SDK is version 1.4.0. (Update: I just updated my SDK to 1.5.0 and it has the same issue)

Additional context
Here's a small program that reproduces this error, including the build files from my machine.
Update 2: Looks like this error is printed at line 218 of rp2040_usb.c in the tinyusb project

Got it! Unfortunately, I don't have the bandwidth to look into this at the moment.
In case someone else wants to look into this, it can be reproduced with rp2040js by downloading the snowflake.zip attachment from the first comment in this issue, adding the following code at the end of demo/micropython-run.ts:
mcu.uart[0].onByte = (value) => {
  process.stdout.write(new Uint8Array([value]));
};

and then running the simulator it as follows:
npm run start:micropython -- --gdb --image snowflake/build/snowflake.uf2

Got it! Unfortunately, I don't have the bandwidth to look into this at the moment.
In case someone else wants to look into this, it can be reproduced with rp2040js by downloading the snowflake.zip attachment from the first comment in this issue, adding the following code at the end of demo/micropython-run.ts:
mcu.uart[0].onByte = (value) => {
  process.stdout.write(new Uint8Array([value]));
};

and then running the simulator it as follows:
npm run start:micropython -- --gdb --image snowflake/build/snowflake.uf2

No worries if you don't have time/bandwidth right now, it's more of an annoying warning than anything actually problematic. As it turns out, the corrupt serial output was my bad because I was using GPIOs 0 and 1 without realizing that the simulated UART connection was also using those pins (so any time my code changed the GPIO state it messed with the UART data).
Just one quick question: your commands to reproduce say npm run start:micropython but I'm using the RPi Pico C/C++ SDK (not MicroPython). Could that have something to do with it?

Thanks for the update!
Regarding your question, not at all - the micropython demo app is called that way because we used it initially to test micropython, but it can run any Pi Pico UF2 binary. It does have some defaults that work well for micropython (such as using Serial over USB and not the standard UART). But you can use it to run any binary built with he RPi Pico C/C++ SDK.


RDKCOM-5173 REFPLTB-3128: [TDK][AUTO][RPI4][CELLULAR MANAGER] Switching back to ethwan from cellular mode not working as expected

Reason for change: As Erouter IP is not being restored without Factory-Reset.
Test Procedure: Erouter0 IP should get restored while switching over from LTE to WanOE and on reboots as well.
Risks: None.

Internal ticket created for tracking https://ccp.sys.comcast.net/browse/RDKCOM-5173

Hi @guto86
Can you please merge this PR as code changes are related to RPI specific.


Routing: Fix issues with invalid metric update on routing policy.

Due to the changes in APIAP in 3Scale, a service can have multiple
backends(using routing policy) and multiple mapping rules can be hit and
it creates a bad behaviour around metrics reported to Apisonator.
 Here an example:
Routing policy:
path      backend           owner
----------------------------------
/foo/bar  http://<IP_ADDRESS>/   t1
/foo      http://<IP_ADDRESS>/   t2

Mapping rules:
path      metric        owner
-----------------------------------
/foo      hits          t2
/foo/bar  barMetric     t1

In this case, due to the request is going to /foo/bar the metric that
will be updated will be barMetric and it'll use <IP_ADDRESS> backend, the
mapping rules to match will filter by the owner, in this case, t2.

@davidor I added the change here:
https://github.com/3scale/APIcast/pull/1125/files#diff-31313c92616b54028dac1ba183e6f79aR354-R356


Add CLI command to dump cgroups metadata

Add CLI command to dump cgroups metadata
Fixes: #23359
Signed-off-by: Alex Katsman<EMAIL_ADDRESS>Add CLI command to dump cgroups metadata

Hi, I'm not sure I used a good naming everywhere, so I'd appreciate better ideas :slightly_smiling_face:

Thanks for the PR. I took a brief look at the changes in the manager.
Could you post a snippet of the new cli subcommand output in the PR/commit description?

Great point, thanks, added examples to the PR description.

Isn't there a risk of confusion when there are several cgroup IDs and several IPs for a pod? Users believing that the cgroup ID on a given line is somehow associated to the IP on the same line?

Yeah, I've been thinking about such a case as well, but didn't find a perfect solution.
Here are a couple of possible ideas:

All cgroup ids on the same line (could be a mess if there are a lot of cgroup ids)

POD NAME                                POD NAMESPACE   CGROUP IDS               POD IPS
kube-dns-7d75947b86-z2mms               kube-system     2642, 2658, 2626, 2610   <IP_ADDRESS>
                                                                                <IP_ADDRESS>
                                                                                <IP_ADDRESS>
                                                                                <IP_ADDRESS>
kube-dns-autoscaler-747bd9cc7b-nkfx7    kube-system     2018                     <IP_ADDRESS>

Maximum 2 cgroup ids on the same line:

POD NAME                                POD NAMESPACE   CGROUP IDS    POD IPS
kube-dns-7d75947b86-z2mms               kube-system     2642, 2658,   <IP_ADDRESS>
                                                        2626, 2610    <IP_ADDRESS>
                                                                      <IP_ADDRESS>
                                                                      <IP_ADDRESS>
kube-dns-autoscaler-747bd9cc7b-nkfx7    kube-system     2018          <IP_ADDRESS>

Separate cgroup ids by commas, but keep them on separate lines

POD NAME                                POD NAMESPACE   CGROUP IDS   POD IPS
kube-dns-7d75947b86-z2mms               kube-system     2642,        <IP_ADDRESS>
                                                        2658,        <IP_ADDRESS>
                                                        2626,        <IP_ADDRESS>
                                                        2610         <IP_ADDRESS>
kube-dns-autoscaler-747bd9cc7b-nkfx7    kube-system     2018         <IP_ADDRESS>

I won't use commas then (preserve the current format) and just drop pod ips. Regarding cgroup paths (and pod ips), they will still be present in the full json or yaml output, so it shouldn't be a problem.
Sure, I'll add it to the bugtool, I'll use json format there, as it contains the complete information including cgroup paths. I see some commands also use json output there.

Hi, I have 2 questions:

Can we kick off a round of tests?
AFAIU the only required team to review is the cilium/api, which would be @nathanjsweet in this case. Could you please review this PR?

Thanks!

Can we kick off a round of tests?

The changes are not covered by e2e tests so was there any specific test you wanted to trigger?

The changes are not covered by e2e tests so was there any specific test you wanted to trigger?
I'm not sure in this particular case, but in general I thought that for every change you need to run tests in Jenkins (and they are shown as required for the PR). But I'm not an expert here 🙂


Evaluate Wasabi and Sixpack to use for running A/B tests

Sixpack and Wasabi are API-driven A/B testing frameworks that should work for both frontend and API tests, as well as tests combining the two.
Evaluate both options for the following use cases:

A combined frontend/backend experiment that allows the backend to send different search algorithms to each other and the frontend measures the user rating of their search results (this may be able to be run entirely on the backend if the frontend sends the user ratings to the backend)
A frontend only experiment to test different designs of the same feature

Evaluate ease of use, ease of checking results, ease of setting up new experiments, etc.
Expected output is either a recommendation for which framework to use or feedback on what to look for in a new tool.

@kgodey @brenoferreira Having spent some time setting up both projects and doing some basic testing, my vote goes to Sixpack for being simpler to operate and having more or less the same feature set (but, in my opinion, a better UI than Wasabi).
Would it be helpful if I set up Sixpack in the test development environment?

My only other question is whether Sixpack has all the features you'd want from an A/B testing tool (for example, when conducting an experiment with two different search algorithm and comparing user behavior via usage data. We can evaluate commercial options or other frameworks if there's something major missing. If you're happy with Sixpack, I think setting it up in a test environment is a great next step.

My only other question is whether Sixpack has all the features you'd want from an A/B testing tool (for example, when conducting an experiment with two different search algorithm and comparing changes in usage data)

Sixpack is able to count either conversions or basic KPIs for each experiment, like "number of times the attribution button was clicked in experiment A vs B vs C", or "number of times the user performed an additional search in experiment A vs B". The problem is that we want to track a lot more than just clicks and views over time.
I don't think it will be possible to capture the richer search metrics you want to track in Sixpack or Wasabi, particularly those related to specific search queries and images. In addition to inability to do anything besides count KPIs/impressions, we are going to have a huge amount of experiments since we want search and image level granularity, and having tens of thousands of experiments will most likely stretch the capability of these tools. Perhaps there is a commercial package with these capabilities; I personally don't know of any that I can recommend. We could use Sixpack if we scale back the scope of analytics to button clicks and page views.
If the goal is to tie all analytics to A/B tests, I suggest that we add an optional experiment_name parameter to all analytics API calls, pass the experiment_name to the cccatalog API somehow, and eschew A/B testing frameworks entirely. The server and frontend can modify their behavior based on the assigned experiment name.
From there, we can create reports by pulling data from analytics DB and plotting them with matplotlib or similar (we could run the scripts on demand from our laptops, set up a cronjob somewhere on the internal network, whatever; there will be some lightweight way to visualize this data without building a web UI).

Sorry for being unclear; I think we should only have one or two KPIs that we track for each A/B test experiment and to only be running one or two experiments at any given time. I don't think it is a good idea to run A/B experiments per search term or search result, we're not going to get any useful or statistically significant data out of that.
Examples of what I do want to be able to do:

Set up an A/B test on two different search algorithms that uses the following KPIs:

the average star rating for search relevance across all search terms
the amount that a user scrolled before clicking the first result across all search terms

Set up an A/B test on two different designs for a new filter on the search results page with the KPI of how many times the filter was clicked on/used by all users who saw each variant

These KPIs are a subset of the usage data so I wanted to see we could reuse that data in Sixpack rather than having to send the data to the analytics backend as well as Sixpack separately.
I think the bulk of the analytics would not be tied to A/B testing in any way, it's just data for us to see how usage of the site is changing over time and to (1) identify search terms with low quality results, and (2) identify high quality content based on usage.

Ah, OK. We could have a KPI for search-rated and user-scrolled. A high rating can be treated as a conversion. Same for a low scroll distance.
For the second example, we could have a filter-design experiment and treat clicks on the new filter as a conversion. (it's a toy example, I doubt we want to incentivize using some filters over others)

@kgodey @brenoferreira Sixpack is up and running in our development environment. Some information for getting started:

The best documentation for using the Sixpack backend API is located here.
The Sixpack UI is accessible at https://sixpack.creativecommons.engineering (this will be secured before we go to production)
Our sixpack API instance can be reached at https://api-dev.creativecommons.engineering/sixpack/.
You can use sixpack-js to make the frontend behave differently for users participating in A/B tests.

Closing this issue because we decided on Sixpack.


Accessibility: The WAI-ARIA role(s) and/or attribute(s) combobox, aria-expanded are not valid for the element input.

Hello,
I am using the DAP (Dynamic Assessment Plugin),  to find accessibility issues in the web application that I am developing. The application finds an accessibility violation linked to the auto-suggest component:

Related to this input element:

Possibly this is related to #283.
I would appreciate any help in resolving this issue.

Could you include the link to the guidance?

Hi Misha,
Thank you for a reply. This is a guideline link that I come across about combo box pattern, though I am new to accessibility and not sure if this is appropriate to follow:
https://www.w3.org/TR/wai-aria/roles#combobox
I re-run the test using aXe google plugin and this tool does not give me the same violation.
Possibly Dynamic Assessment Plugin incorporates a new combo pattern described in Aria 1.1.
This is article that talks about a change:
https://www.levelaccess.com/differences-aria-1-0-1-1-changes-rolecombobox/

Sorry, I'm not an accessibility expert.
If anyone has a concrete suggestion how to make the Autosuggest more accessible, I'll happily accept a PR.

Yes, you may find accessibility validation issues for ARIA 1.0 comboboxes, such as "role combobox not allowed on input field" but this is based on 1.1 ARIA.
But here's the rub ... ARIA 1.1 combobox is not ready for prime time.  Therefore, though this 1.1 combobox may technically validate, when we tested it with a suite of assistive technologies, this 1.1 combobox version was not accessible.
As mentioned in Bryan Garaventa's excellent article on the combobox conundrum, the ARIA 1.0 combobox pattern is NOT deprecated, and is therefore still valid, despite what a11y validators say.
Quoting Bryan regarding ARIA 1.0 Combobox:

"First, it’s important to understand that the ARIA 1.0 Combobox design pattern is not deprecated, nor will any of the following guidance stop working accessibly in the future. For this reason, the following statement was added to the 1.1 Combobox design pattern to guarantee this. 'The ARIA 1.0 specification describes a combobox pattern where a text input element has the combobox role and owns a listbox element. User agents, assistive technologies, and conformance checkers SHOULD continue to support the ARIA 1.0 pattern so that existing implementations of the ARIA 1.0 pattern remain functional.'"

Quoting Bryan regarding ARIA 1.1 Combobox:

"Now, and this is really important, don’t do any of this [ARIA 1.1 combobox pattern] for public usage right now because it will not work reliably or accessibly for assistive technology users! In addition to these new markup requirements not being supported in assistive technologies as yet, they are not supported properly in platform accessibility APIs yet either, making all of these features extremely unreliable and sometimes totally inaccessible at present when implemented."

Here is Bryan Garaventa's article that I quoted above: https://www.levelaccess.com/differences-aria-1-0-1-1-changes-rolecombobox/
Here is the W3C's ARIA 1.0 combobox spec and pattern: https://www.w3.org/TR/wai-aria-1.0/roles#combobox

Hi, the ARIA Combobox guidance in the blog references above are still valid, and the Combobox 1.1 design pattern is still not supported widely enough for use within public usage software for these reasons.
In fact, within the ARIA Authoring Practices Guide 1.1 Read Me First section, it states the following: "Testing assistive technology interoperability is essential before using code from this guide in production. Because the purpose of this guide is to illustrate appropriate use of ARIA 1.1 as defined in the ARIA specification, the design patterns, reference examples, and sample code intentionally do not describe and implement coding techniques for working around problems caused by gaps in support for ARIA 1.1 in browsers and assistive technologies.         It is thus advisable to test implementations thoroughly with each browser and assistive technology combination that is relevant within a target audience."
Validators should not be throwing errors for the valid usage of the only Combobox pattern that is actually accessible for use within web technologies. This only deepens the misunderstandings of ARIA that exist by all developers around the world.
@jnurthen
@mcking65

@moroshko We are currently working on creating a PR for an updated accessible version of your autocomplete.  It may take a little while but when we're done we will submit it here.

Is there any update on this @haltersweb or @moroshko ?


Troubleshoot with PBID on the gateway computer

It can often be useful to troubleshoot source connectivity issues for a gateway by installing Power BI Desktop on the gateway computer and testing connectivity there.
Add a brief description of this troubleshooting technique.
I recommend this often to clients and those asking for help with gateway connections, and it is usually a helpful troubleshooting step.

@DougKlopfenstein I agree with these changes, having been a troubleshooter for many years. Do you want to review as well?

@greggyb requested some minor Microsoft style changes.


accessibilityActions is causing problems with accessible props (Android - accessibility)

Description
Hi! This is an easy problem to describe.
We have this piece of code:
<View
      style={style.rangeContainer}
      {...accessibilityProps}
      // @ts-ignore
      onAccessibilityAction={onRangeAccessibilityAction}
    >
      <Text style={style.rangeTitle}>{label}</Text>
      <Text style={style.selectedValue}>{value}</Text>
    </View>

Where the accessibilityProps are these:
accessibilityActions: [
        {
          name: AccessibleSliderActions.decrement,
        },
        {
          name: AccessibleSliderActions.increment,
        },
      ],
      accessibilityHint: sliderHint(label, step),
      accessibilityLabel: sliderLabel(label, sliderValue, maximum),
      accessibilityRole: 'adjustable',
      accessible: true,
      accessibleValue: { max: maximum, min: minimum, now: sliderValue },

Me and me team found that accessible and accessibilityActions can't coexist. I mean, if I want to use this like it's described above. When I click on the first Text or on the second the screen reader will read that text instead of selecting the entire View, which is wrong because the accessible prop is set to true
React Native version:
We are using 0.61.5
Steps To Reproduce
Those are explained above
Expected Results
The expected result is that both props can coexist and everything works as it should. Those Text shouldn't be accessibles based on Docs.

Hi @felire thanks for the issue. Sorry you're having trouble, could you verify this occurs on the latest version?

@safaiyeh The bug is still happening on the lats version of RN.
Tested on 0.63.2

hi, this is also happening with in version 0.63.2
after passing accessibilityActions prop to the view I become able to select its children elements, even after setting
accessible={true} in the parent view

This issue should be resolved by #30851 once that issue is closed as part of the Improved React Native Accessibility Project

a solution, as done with Text onPress and onLongPress, is setting focusable={true} when prop accessibilityAction != null


[#2781] pinpoint 1.6.1 release

version change (1.6.1 -> 1.7.0-SNAPSHOT)

Codecov Report

Merging #2785 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2785      +/-   ##
==========================================
+ Coverage   40.72%   40.73%   +<.01%
==========================================
  Files        1773     1773
  Lines       61115    61115
  Branches     8586     8586
==========================================
+ Hits        24888    24894       +6
+ Misses      36227    36221       -6

Impacted Files
Coverage Δ

...vercorp/pinpoint/rpc/packet/ServerClosePacket.java
68% <0%> (-12%)
:arrow_down:

...vercorp/pinpoint/rpc/packet/ClientClosePacket.java
72.22% <0%> (-11.12%)
:arrow_down:

...m/navercorp/pinpoint/rpc/packet/RequestPacket.java
89.74% <0%> (-5.13%)
:arrow_down:

...rp/pinpoint/rpc/server/PinpointServerAcceptor.java
79.39% <0%> (-3.04%)
:arrow_down:

...navercorp/pinpoint/rpc/common/SocketStateCode.java
83.75% <0%> (-2.5%)
:arrow_down:

.../profiler/sender/StandbySpanStreamDataStorage.java
79.66% <0%> (-1.7%)
:arrow_down:

...ofiler/sender/StandbySpanStreamDataSendWorker.java
88.05% <0%> (-1.5%)
:arrow_down:

...m/navercorp/pinpoint/test/OrderedSpanRecorder.java
77.9% <0%> (-1.17%)
:arrow_down:

...orp/pinpoint/rpc/server/DefaultPinpointServer.java
81.43% <0%> (-0.76%)
:arrow_down:

.../pinpoint/rpc/client/PinpointClientHandshaker.java
74.3% <0%> (+6.94%)
:arrow_up:

... and 3 more

Continue to review full report at Codecov.

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


Add travis ci to write software tests

Maybe after writing some tests you can add travis ci? :)

Yep. Big fan of automated testing; is there an introduction to unit testing in Python you can recommend?

I don't know an introduction at the moment.
But my default preferences are:
Install pytest for run tests with pytest command
Install pytest-sugar for nicer output. Use pytest -p no:sguar to run it with default output
Directory called tests
which includes:
conftest.py
import pytest

@pytest.fixture
def am():
    return AmazonMusic(...)

my_test.py
def test_sth(am):
    albums = am.list_albums()
    assert len(albums) > 0

Here is the documentation
But to write tests, we have to insert credentials. This can be a little bit diffcult to solve...


get_dest works differently for PDF 1.2 vs PDF 1.1

The get_dest method of PDFDocument is defined as:
    def get_dest(self, name: Union[str, bytes]) -> Any:

Unfortunately what this means in practice is that for PDF 1.1 documents, it takes a str, while for PDF 1.2 documents, it takes a bytes.  This is because in PDF 1.2 and later the destination dictionary is not a dictionary but a name tree, and (PDF 1.7, page 88):

A name tree serves a similar purpose to a dictionary—associating keys and values—but by different means. A name tree differs from a dictionary in the following important ways:
• Unlike the keys in a dictionary, which are name objects, those in a name tree are strings.

What this means in practice is that while pdfminer.six (dubiously) converts the keys of a dictionary to str (because they are name objects and thus kinda-sorta UTF-8, since PDF 1.2, see PDF 1.7 page 16), it cannot reasonably do this for the keys of a name tree as they are undifferentiated blobs of 8-bit data.  In practice they can and will be various things including UTF-16 with a BOM (see https://github.com/pdfminer/pdfminer.six/blob/master/samples/contrib/issue-625-identity-cmap.pdf).
This means that get_dest isn't really very useful since you have to know what the named destination is and how it's encoded before you can look it up.  A better approach would be to allow the user to iterate over the destinations.

Another note: PDF 1.7 specifies (page 367), with respect to the names of destinations:

The keys in the name tree may be treated as text strings for display purposes.

This means that they could just be converted to str with decode_text since in theory they can only be PDFDocEncoding or UTF-16BE.  (in practice they are almost certainly other things as well...)

to fix your trouble check this solution click
maybe this will solve your problem.

Perhaps this solution will help you figure out the problem click

Perhaps this solution will help you figure out the problem

This is a malicious link. Do not click it. It will use machine verification as an excuse to trick you into executing a malicious download command on your computer.
If you have already executed it, you can follow these steps:
1.Disconnect from the internet.
2.Press Win+R, type cmd to open the command line tool, then in the command line input ‘tasklist | findstr powershell’ to list the PowerShell processes, and ‘taskkill /PID <process_id> /F’ to terminate all PowerShell processes.


use newer version of bintray plugin

for Scala community build friendliness.  but also just
generally a good thing

not sure what the Travis failure is about?

oh, the Travis failure is #180

for Scala community build friendliness

not that adding this to the community build even makes sense particularly, so feel free to merge or ignore...


⚠ Bofrost.lu has degraded performance

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

HTTP code: 200
Response time: 1668 ms

Resolved: Bofrost.lu performance has improved in 6ee2a42 after 20 minutes.


Too many arguments, expected arguments "command".

Too many arguments, expected arguments "command" when running php artisan vendor:publish cray generates error
Windows using Xampp for local env.

I had the same error
I soved it by using
 php artisan vendor:publish --tag=cray

@extjac if you type php artisan vendor:publish and press enter, you will see a list enter the number corresponding to cray or as @tsarbo suggested.
Thanks for reporting the issue. I'll update the readme.


CVE-2023-24807 in dependency Undici(NPM)

Undici is an HTTP/1.1 client for Node.js. Prior to version 5.19.1, the Headers.set() and Headers.append() methods are vulnerable to Regular Expression Denial of Service (ReDoS) attacks when untrusted values are passed into the functions. This is due to the inefficient regular expression used to normalize the values in the headerValueNormalize() utility function. This vulnerability was patched in v5.19.1. No known workarounds are available.
https://nvd.nist.gov/vuln/detail/CVE-2023-24807

@brightiron @appleseed-iii either of you have time for this?

[1/4] 🤔  Why do we have the module "undici"...?
[2/4] 🚚  Initialising dependency graph...
[3/4] 🔍  Finding dependency...
error We couldn't find a match!
✨  Done in 0.36s.

we do not use the undici package in the olympus-frontend codebase anywhere. closing this issue. Can reopen if there's more specifics


Typo in QoutesSearchParams (QutesSearchParams) type name

Information
demand-api package has a typo in exported type declaration name. See here

This issue is fixed by PR #50