prepend basePath when autogenerating from route result

I believe that invoking helper should end in consistent results with generated urls containing - if set - the basePath prefix.
Should we also avoid getter (getRouteResult, getBasePath) calls and use $this->result and $this->basePath directly?
(code contained mixed getter and property call for result)
I don't see any reason why those getter should be eventually overridden in a child class to send something different from the internal properties themselves.
kind regards

One difference from: https://github.com/zendframework/zend-expressive-helpers/pull/11
i believe we should use basePath only when invoking the helper and not when calling the private method generateUriFromResult. If we strip the basePath from the uri for a website running in a subdir, we then set the base path in the generator, but for the router and route result that basePath does not exist.

@pine3ree this makes sense. Thanks! Can you add some tests for the affected cases? The test coverage still happens to be 100% after your changes, but there are no test cases to cover specifically that the basePath is prepended when the provided $route is null.

@michaelmoussa
Hello, i added a simple test case. Pls let me now if this would suffice. kind regards.
maks

@pine3ree this is fixed in 2.0.2.
I made a minor adjustment in addition to your commit to remove the need for the else / if. The way it looks now is similar to in the previous version, but with the $basePath still being prepended always.
Thanks for your contribution!


s3 action failure after migrating to 1.3.0

Just migrated to 1.3.0, shenzhen needs to be an explicit dependency in the gem file?
----------------
22:50:52 [22:50:52]: --- Step: s3 ---
22:50:52 [22:50:52]: ----------------
22:50:52 [22:50:52]: ipa distribute:s3 -f "XXX.ipa" -a "XXX" -s "XXX" -b "jenkins-ios" -P "jobs/iOS-job/7/"
22:50:52 [22:50:52]: [SHELL COMMAND]: ipa distribute:s3 -f "XXX.ipa" -a "XXX" -s "XXX" -b "jenkins-ios" -P "jobs/iOS-job/7/"
22:50:54 [22:50:53]: [SHELL]: /Users/xbot/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/bundler-1.9.2/lib/bundler/rubygems_integration.rb:263:in `block in replace_gem': shenzhen is not part of the bundle. Add it to Gemfile. (Gem::LoadError)
22:50:54 [22:50:53]: [SHELL]: from /Users/xbot/.rbenv/versions/2.2.1/bin/ipa:22:in `<main>'
22:50:54 [22:50:53]: Exit status of command 'ipa distribute:s3 -f "XXX.ipa" -a "XXX" -s "XXX" -b "jenkins-ios" -P "jobs/iOS-job/7/"' was 256 instead of 0.
22:50:54 /Users/xbot/.rbenv/versions/2.2.1/lib/ruby/gems/2.2.0/gems/bundler-1.9.2/lib/bundler/rubygems_integration.rb:263:in `block in replace_gem': shenzhen is not part of the bundle. Add it to Gemfile. (Gem::LoadError)
22:50:54 	from /Users/xbot/.rbenv/versions/2.2.1/bin/ipa:22:in `<main>'

Thanks, I'll push a fix in a minute.

Thanks @KrauseFx for the quick fix, testing right now.

One second, just uploading the new version :+1:

It's live :rocket:

Thanks, works like a charm

Great to hear :+1:


Set up CD to AKS/ACR

Pull Request
Description

Related Issue(s)

Screenshots (if applicable)

Checklist

[ ] I have checked that the changes included in the PR are intended to merge to master or any destination branch.
[ ] I have verified that the new changes do not break any existing functionalities, unless the new changes are intended and have approved by the team.
[ ] I will take care of the merging and delete the side-branch after the PR is merged.

Additional Notes/References

Please refer to new PR for CD set up


Feature request: StaleWhileRevalidate - what is fresh/stale?

Library Affected:
workbox-strategies
Browser & Platform:
all browsers
Feature Request Description:

The stale-while-revalidate Cache-Control Extension
When present in an HTTP response, the stale-while-revalidate Cache-
Control extension indicates that caches MAY serve the response in
which it appears after it becomes stale, up to the indicated number
of seconds.
https://tools.ietf.org/html/rfc5861#section-3

The current implementation of the stale-while-revalidate is very inflexible and just assumes the current cache content is always stale.
Normally I would use this strategy alongside an indication, when the cache content should be consider stale. For example Firefox and Chrome support stale-while-revalidate next to max-age. We use a similar solution with our varnish layer.
Our your goal is to leverage the local cache and reduce the load (requests) on the origin.
This is why I propose an option for the stale-while-revalidate strategy that allows you to set a number of second during which the cache is considered fresh.
This option in combination with the ExpirationPlugin (how long stale content is allowed be serve...) gives us a complete implementation of stale-while-revalidate.

Hello @rubas!
Apologies if I'm misunderstanding your request, but are you asking for the ability to use the StaleWhileRevalidate strategy and completely skip the revalidation (i.e. network) step if some criteria are met?
I'd normally say that one way to handle that would be to ensure that you're using the HTTP cache and associated Cache-Control: headers effectively, since if you are, the revalidation request could be fulfilled from the HTTP cache instead of the network. This means you won't have to change anything in Workbox.
If you can't accomplish this with Cache-Control: headers, then you have some options for extending Workbox to accomplish what you describe. (If you do end up implementing something, feel free to release it on npm so that others can use it!)
Custom strategy
Writing a Strategy subclass that implemented the specific logic you're looking for is probably the easiest approach. Workbox's StaleWhileRevalidate class is only a handful of lines of code (when you omit the comments and logging), and could be adapted to accomplish what you describe. The nice part about writing a custom Strategy subclass is that all the existing plugins will "just work", as long as you interact with the network and cache via the wrapper methods exposed by the handler parameter.
Here's a rough sketch:
import {Strategy} from 'workbox-strategies';

class CustomSWR extends Strategy {
  async _responseIsFresh(response: Response) {
    // Your logic for determining whether response is fresh
    // goes here.
  }

  async _handle(request: Request, handler: StrategyHandler): Promise<Response> {
    // cachedResponseWillBeUsed plugins will automatically be run here, so you
    // could theoretically avoid needing to implement your own _responseIsFresh()
    // if you just require that folks always use a cachedResponseWillBeUsed plugin.
    // But if you want it to be self-contained, you can run logic embedded in the class.
    let response = await handler.cacheMatch(request);
    if (await this._responseIsFresh(response)) {
      return response;
    }

    // fetchAndCachePut() will handle both the network request
    // and updating the cache.
    return await handler.fetchAndCachePut(request);
  }
}

Custom plugin (not feasible)
Another alternative for extending Workbox is to write a custom plugin.
I could imagine a plugin that implemented cachedResponseWillBeUsed and requestWillFetch, making use of the state object that's passed to both to signal from cachedResponseWillBeUsed whether requestWillFetch should return a valid Request or just null. The problem with this approach, though, is that the StaleWhileRevalidate strategy doesn't guarantee that cachedResponseWillBeUsed will execute before requestWillFetch (they're effectively run simultaneously), so you couldn't reliably set state in cachedResponseWillBeUsed before requestWillFetch runs. Additionally, if you did return null in requestWillFetch, then you'd end up with a fetch() failure that you'd have to account for.
I'm going to close this issue for now, but if for some reason that doesn't address your use case, let us know and we can revisit.

Thank you, Jeff. I don't know anybody who answer all issues always this fast and extensive!!

Apologies if I'm misunderstanding your request, but are you asking for the ability to use the StaleWhileRevalidate strategy and completely skip the revalidation (i.e. network) step if some criteria are met?

Correct. As the name implies the idea is that you are allowed to use/send "stale" content while fetching an updated version in the background.
Normally (in the context of http cache, varnish strategies ...) you always have two parameters with this strategy:

when is the cache considered stale? (ie after 10min => max-age=600)
how long are you allowed to send stale content? (ie if the stale content is not older than 1hour, use it => stale-while-revalidate=3600)

I do understand that I could get my desired behaviour with a custom strategy (or just with a http cache afterwards if supported by the browser) but suggest to rethink the name of the strategy (or at least add a note in the docs about the the difference / limitation) - or better add the missing functionality to make it whole 🌻
At the end of the day it is a wording issue.  Treating the cache always as stale, is not in the spirit of the "original" strategy and is imo confusing. This term is always used in a context, where you define first the freshness (lifetime) of the cache. The corresponding RFC has the title  HTTP Cache-Control **Extensions** for Stale Content.
Why do I care?
I treat SW as every other cache layer I work with. If you are only looking for speed and offline functionality, the current implementation works fine. But I also want to reduce unnecessary requests (💰💰💰) to the origin/next cache layer ...

The current implementation is comparable/limited to max-age=0,  stale-while-revalidate=something.
Not my favourite but CacheWhileRevalidate is more in line with this implementation.

Yeah, that's a valid point w.r.t. Workbox's naming—I did think about it when I was writing https://web.dev/stale-while-revalidate/
I don't know that we're going to change anything at this point, as the (technically inaccurate) StaleWhileRevalidate strategy name is used very pervasively in the codebase and supporting build tools. I think it's more likely that we'll add a caveat in the documentation, linking to this issue for folks who want more context and potential workarounds.
I'll reopen this issue to track that documentation change.


Scene understanding crashes Unity 2020.3.2f1

Describe the bug
Unity immediately crashes when trying to open the Scene Understanding example scene in Unity 2020.3.2f1. Produces the error message shown in screenshots. This also happens if you try to add the WindowsSceneUnderstandingObserver in the MixedRealityToolkit object where all various MRTK settings reside.
To reproduce
Create a new project in Unity 2020.3.2f1 and import essential MRTK components. Import the Scene Understanding sample scene via package manager. Navigate to the example scene and try to open it. Application immediately crashes.
Or
Have an existing MRTK project and try to add the WindowsSceneUnderstandingObserver in the MixedRealityToolkit object under Spatial Awareness/
Expected behavior
Expect there to be no errors
Screenshots
If applicable, add screenshots to help explain your problem.
Your setup (please complete the following information)

Unity Version 2020.3.2f1
MRTK Version 2.7.2

Target platform (please complete the following information)

HoloLens 2 / UWP

Thanks for reporting the issue. I was not able to reproduce with Unity 2020.3.2, MRTK 2.7.2, Mixed Reality OpenXR plugin 1.0.1 and Scene Understanding 0.6.0 (I was able to open the sample scene and run it successfully). Could you share with us which XR pipeline you used (Windows XR Plugin or OpenXR) and maybe attach the Unity editor log located at %LOCALAPPDATA%\Unity\Editor\Editor.log if you feel comfortable? Otherwise please reply with the lines in the editor log that seems relevant so that we can better troubleshoot the issue.

I have tried both the Windows XR Plugin and OpenXR with the exact same result. Just tried this again with a totally new project and used the mixed reality feature tool to add MRTK, examples, extensions, foundation, and standard assets. Also adding platform support for Mixed Reality OpenXR plugin and Mixed Reality Scene Understanding. Latest versions selected for all items. After opening the project I import the scene understanding example via package manager and try to open the example scene that results in the error above.
There is nothing in the Editor Log to indicate the error even happened. The last lines in the file are attached.

Now that seems very weird now... So the runtime library popped up, you clicked OK, Unity crashed and there is nothing in their log? Could you send us a copy of the fresh project that on your side exhibited the behavior? We'll try to do a repro with it. At this point I am almost wondering if it's a runtime library not properly installed issue.

Turns out this problem was resolved once I upgraded to a more recent version of windows


CommonLogging instead of log4net

Hi,
Using CommonLogging would allow users to choose their logging framework.
It would be nice to not force TopShelf users to depend on log4net and let them choose their preferred logging framework (and in my case, I tend to use NLog in my apps instead of log4net).
Regards

+1 for this. Using Common.Logging will also probably also solve some issues around log4net changing their strong name key.


Need for ShadyCSS

LitElement is no longer supporting @apply for styles defined using the static styles property, but it's still using shady-render and calling  window.ShadyCSS.styleElement(this); in the connectedCallback.
Why is that still needed? If it's only for supporting @apply in regular <style> tags I think this could be made configurable to get a nice performance boost for most users.
The reason I am asking this is that I am migrating a large codebase from Polymer to LitElement. Our main entry point does not use any polymer, so it would only be loaded once a user lands on some legacy pages. I'd also like to avoid loading ShadyCSS until later on as well, but that might throw off some elements built with LitElement if ShadyCSS suddenly shows up after their first render. I'd prefer it if LitElement did not deal with ShadyCSS at all on modern browsers, or at least have the option to configure it to not do this.

It's still needed to support polyfilled browers without native support for shadow DOM, it's not just for @apply

Of course, but as far as I can tell that is covered within the static styles already.

See also: #612.


react-native-pytorch-core build failed on Android

Version
v0.2.0-rc.1
Problem Area
react-native-pytorch-core (core package)
Steps to Reproduce

make RN clean project
follow tutorial and build
get this error

> Configure project :app
Unable to detect AGP versions for included builds. All projects in the build should use the same AGP version. Class name for the included build object: org.gradle.composite.internal.DefaultIncludedBuild$IncludedBuildImpl_Decorated.

> Task :react-native-pytorch-core:configureCMakeDebug FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':react-native-pytorch-core:configureCMakeDebug'.
> C/C++: /<WorkSpace>/AwesomeTSProject/node_modules/react-native-pytorch-core/android/CMakeLists.txt debug|armeabi-v7a : CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
  Please set them or make sure they are set and tested correctly in the CMake files:
  FBJNI_LIBRARY
      linked by target "torchlive" in directory /<WorkSpace>/AwesomeTSProject/node_modules/react-native-pytorch-core/android
  JSI_LIB
      linked by target "torchlive" in directory /<WorkSpace>/AwesomeTSProject/node_modules/react-native-pytorch-core/android
  PYTORCH_LIBRARY
      linked by target "torchlive" in directory /<WorkSpace>/AwesomeTSProject/node_modules/react-native-pytorch-core/android
  REACT_NATIVE_JNI_LIB
      linked by target "torchlive" in directory /<WorkSpace>/AwesomeTSProject/node_modules/react-native-pytorch-core/android
  REACT_NATIVE_UTILS_LIB
      linked by target "torchlive" in directory /<WorkSpace>/AwesomeTSProject/node_modules/react-native-pytorch-core/android

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

See https://docs.gradle.org/7.3.3/userguide/command_line_interface.html#sec:command_line_warnings

Is there anything that I need to do？
Expected Results
BUILD SUCCESSFUL
Code example, screenshot, or link to repository
No response

Hi @SomaKishimoto Sorry for the late reply. We are working on a fix. This seems to be a issue when the app is using react-native 0.68+ (pls correct me if I am wrong) -- to unblock you at this moment, you may replace the line https://github.com/pytorch/live/blob/main/react-native-pytorch-core/android/build.gradle#L201 with
if (task.name.contains('configureCMake')) {

after install the package
Please let us know if you see other issue, thanks!

@SomaKishimoto, the latest nightly has support for React Native 0.68. A fix has been added in commit fix RN0.68 can't build with react-native-pytorch-core, which is currently only available in the nightly version.
More information is in the docs "Add Package to Existing App".
Can you let us know if this unblocks you?
We are also looking into supporting RN 0.69

@raedle , Sorry for late reply. I confirmed your fix works correctly. Thanks!

No worries, and thanks for the response, @SomaKishimoto.
I'm going to close the issue


Finish Capistrano / get Yale ITS deployment set up

I know that this isn't really a general application issue, but we need to get the ITS deployment procedure aligned with the changes implemented in #683. We can use this to finalize the implementation of Capistrano so that we hopefully have a well-documented example of how one might deploy an instance of Reservations.

2015-02-15
Here are some things that need to be done.

[x] #1104
[ ] have deploy.rb copy over the secrets.yml.example file
[ ] review #275 branch to see what else generally needs to be done

@orenyk what's left to get Capistrano working? Does it work on e.g. laptops, if I were to git clone reservations and run a cap production deploy? Is there anything I can help with on the sysadmin side?

Ummm... good question. It's set up to use localhost as the server but would require a hudson user at the moment. I haven't set up deploy.rb to copy over the secrets.yml file, so that would still be necessary, but other than that you'd have to set some environment variables and it should work. Maybe we should make the user configurable as an environment variable as well so that the whole Capistrano setup is as general as possible.
From ITS' side, we're basically going to need to copy all of the Jenkins parameters into a .env file and pass the deployment path to Capistrano as an environment variable as well. We should set up a meeting over the next month or so to hash this all out, but in the meantime look over #683 and the relevant wiki pages and let me know if anything jumps out at you.

I think the localhost/hudson and secrets.yml is something INF can replace with sed for example, much like we do now---and just dump the parameters into a .env perhaps instead of running it all as bash environment variables.
These are all the BMEC vars (available in /ror_dev/ruby_deploy/reservations01/install-PROD-BMEC_properties):
rails_environment=${deployment_env}
app_path=/path/to/install/directory
database=${bmec_db}
database_host=${which_server_hosts_bmec_db}
db_username=${bmec_db_username}
db_password=${bmec_db_password}
uri=/bmec

The Configuration doc looks pretty thorough. Does it work if one submits dummy values (e.g. localhost with Yale CAS and SMTP) for both the staging and production envs? It would be best to make sure that's working before INF gets involved---once it's confirmed working, we should definitely set up a meeting with Michael and get this going. :grinning:

Ok, things are slowly moving. I've been trying to get this working on a DigitalOcean droplet running CentOS w/ Passenger and Apache (to get close to our setup in ITS) and it's... getting there :confused:. Currently, I've got cap production deploy working until it tries to precompile assets when it fails because I haven't yet run the task that copies over database.yml.
One other thing to note: we've got pg in our production group in the Gemfile; this is so that we can deploy to Heroku. However, it also means that when you run bundle install you have to have postgresql and postgresql-devel (I think) installed on your app server so that it can install the pg gem, even if you're not using it. I'm not sure what the best way to handle this is, and whether or not ITS would be willing to just install those dependencies so that I don't need to figure out a workaround. We'll see...

More to do:

[ ] don't forget to have it working with localhost (I ran into issues with the ssh shell / rbenv not working, see here, rbenv seems to be problematic)
[ ] take all the rbenv stuff out of deploy.rb and go back to rvm

Ok, better but still stuck. I'm having trouble using the test commend from SSHKit, it's returning unknown command '['. Will investigate later.

I've been trying to get this working on a DigitalOcean droplet running CentOS w/ Passenger and Apache (to get close to our setup in ITS) and it's... getting there

Would it help if I cleaned up my Chef proof of concept deploy script which installs apache/passenger + rvm + whatever versions of ruby ya want? What sort of issues are you running into?
you have to have postgresql and postgresql-devel (I think) installed on your app server so that it can install the pg gem, even if you're not using it.

It's mildly clunky, but yum install postgresql-devel shouldn't as far as I know present much of an issue as we should be able to disable it / prevent it from doing anything on the system besides just sitting there. I'd need to check with Michael though for approval, but that's suuuuuper minor and we'll cross that bridge when we need to.

@dgoerger: Actually, DO has pretty good guides on getting set up with CentOS + rvm + Apache / Passenger, so while your Chef work might have been helpful yesterday, at this point I have a VM image where I can locally clone reservations and then run cap production deploy and it starts going. All the default Capistrano / Rails stuff seems to work fine (at least up to bundle install), it's getting stuck in my custom task that turns the local parameter file into .env with all of the configuration params. I'll keep digging...
Glad to hear that installing PostgreSQL should be acceptable; it's definitely clunky though so I'll see if we can work around it (maybe another custom ENV variable :stuck_out_tongue:).

Whew, figured that out - I needed to specify a server to perform the task on, e.g. on roles(:app) do, etc.

(Note that 512 MB of RAM was insufficient for asset precompilation so I had to add a 1 GB swap to supplement)

WOO HOO! Assets are totally broken, but the basics are there:

Note that the deploy directory is the basis, so if you wanted it to be in /var/www/reservations then you'd have to specify /var/www/reservations, not /var/www (as I thought). The Apache conf file would then look in /var/www/reservations/current/public. Tomorrow... assets!

Ok, from memory ITS is using Passenger to deal with assets rather than through Rails, so I'm going to look into that now.

Never mind, I had a relative subdirectory set in the configuration parameters (e.g. example.com/test) so the asset URL's were pointing to non-existent locations. For some reason the restart mechanism isn't working, nor is the whenever crontab generation task. The investigation continues...

:boom:

just testing party foul, but I think this is basically ready :-D

Got it to work by tweaking the initializer to create errors for ActiveRecord::RecordNotFound exceptions and removing the rescue_from block in ApplicationController --> we have a successful deployment :smile:

Note that the current syntax would be GIT_TAG=v1.2.3 DEPLOY_DIR=/path/to/dir PARAM_FILE=/path/to/file cap production deploy

PR opened, I'm just going to run through it's diff later to see if there's anything I'd like to clean up and then it should be ready for review / kicking up the ladder :smile:.

@dgoerger: any chance you could check this out and let me know if you think we're ready to set up a meeting w/ ITS? Thanks!

... still waiting on ITS to start testing...

I will be writing / updating our documentation shortly to include the use of Capistrano for deployment.

Just realized that the whenever crontab update might not be running, might need an immediate patch to v5.3.0 :stuck_out_tongue:. Just testing now, DigitalOcean is awesome!

 Unfortunately that won't help ITS, so they might have to manually delete cron jobs on DEV, but I'm glad I set everything up properly :stuck_out_tongue:.

On second thought, some of our cron tasks are not e-mail related, so we probably want them running on all environments. I'll open an issue for further investigation.


Ledger Live desktop application doesn't recognize the dongle when dongle is connected via bluetooth with mobile app

Describe the bug
The dongle is connected via bluetooth to the mobile app and when opening the desktop app and trying to open the "Manager" section, it doesn't recognize the dongle. Normally the dongle would require you to confirm the opening of the manager section, but right now, it doesn't.
Each of the steps provided in the first level troubleshoot doesn't work, neither the reset of the device. I tried the reboot of the computer, different usb port, disconnect and reconnect the dongle when Live Ledger app is open and closed.
To Reproduce
Steps to reproduce the behavior:

Go to dongle and enable bluetooth
Go to mobile app and connect dongle with live ledger app
Go to desktop app and try to open the manager section
See that the app is trying to wait for the device, but nothing happens
Go to mobile app
Open "My ledger" section
Select device from list
App is asking to keep the device near the dongle
Go to dongle and it request confirmation to open the manager section
Confirm the request at the dongle
Go to app and see the manager section is opened

Above steps shows, that the mobile app is working fine connecting with the dongle, but the desktop app cannot connect.
Expected behavior
The desktop app should recognize the dongle even it is already connected via bluetooth with the mobile device.
Desktop (please complete the following information):

OS: Monterey 12.4

Smartphone (please complete the following information):

Device: iPhone 12 pro
OS: OS15.5
Live Ledger Mobile app: 3.2.0 (383)
Live Ledger version: V2.0.2

Additional context
Add any other context about the problem here.

@cpuell as of today you are correct in your assessment. We can't connect to a device with multiple transports. In this case, BLE and USB transports. Ledger Live desktop will be able to see the device but not communicate with it, since the device will not respond while connected via BLE.
There are some changes incoming that will release the BLE connection after an interaction and this will allow the USB side to talk again with the nano. This will probably feel more natural from a user perspective. I will leave a note to ping back on this thread once we release that version so you're the first to know. In the meantime, I'm closing the issue.


getContent issue!

Hi !
I have an issue with this site : https://www.the-star.co.ke/news/2018/03/13/warning-risks-of-food-security_c1728262
The function "parse()" returns only the title!

JS version is also failing to parse this. I'll add it as a failing test case.

Disregard my last comment, using the latest version I was able to parse everything correctly. Would you mind parsing it again using v1.2.0?

Just realized you changed the link. This one gets parsed correctly. Closing issue.

Thanks! It works with v1.2.0  :)


Add a new rebus

This project needs more fun rebuses to solve! 🎉
The game is live at: https://ollelauribostrom.github.io/rebus/
Instructions:
Open the file src/js/rebuses.js in your favourite editor and add a new rebus object to the end of the rebuses array. Follow the guide in the readme for more detailed instructions on how to get started.

I would like to add more to this rebus game

@andyn95 Sure, go ahead and follow the step-by-step guide in the README to add a new rebus 🙂

Hello !!
I would like to add more to rebus, its my first contribution to open source
:D

#248 Hello !!
I would like to add more to rebus, its my first contribution to open source

https://github.com/ollelauribostrom/rebus/pull/338

hi @ollelauribostrom, i want to add new rebuses and tried running the tests before making any changes but it failed, how do i handle this ?

Does this still need to be worked on? If so I'd like to take it.

@ollelauribostrom i have a confusion, how to add these emojis in array direct?

Hey, I will be so happy to add new rebuses. I am working on it and will try to do it as early as possible.

Would love to contribute to this project but there are 259 PRs pending. @ollelauribostrom Do you need help going through these?

When I run the following command
npm run test: all
it shows the following error
Expected linebreaks to be 'LF' but found 'CRLF'  linebreak-style

i would like to contribute too

I would like to add new rebus

May i add some ??

I would like to add more to this rebus game.

I would Like to add new rebus

Hi,
I'm trying to add a new rebus but I'm getting stuck.. can anybody help?
I think the issue is at Step 5 Install Dependencies. I've run command "npm install" and got the blow response.
Then when trying to run the game locally many more errors appear (whether I used the altered, or unaltered rebuses file)
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/webpack-cli
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@webpack-cli/serve
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Conflicting peer dependency<EMAIL_ADDRESS>npm ERR! node_modules/webpack-cli
npm ERR!   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@webpack-cli/serve
npm ERR!     dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /Users/TiknockTokomak/.npm/eresolve-report.txt for a full report.
npm ERR!      /Users/TiknockTokomak/.npm/_logs/2022-04-10T13_54_18_711Z-debug-0.log
TiknockTokomak@MyMac rebus %

@ollelauribostrom I would like to add new one .

@ollelauribostrom I would like to a new rebus

@ollelauribostrom I would love to add and contribute to Rebus.

After adding two new rebuses, when I tried to merge it. I received an error, that indicated that the Ubuntu image used to host the game on netlify is outdated. Can it be fixed?

please review my request and merge it


MAVLink app: Only start transmitting when boot is complete

@DonLakeFlyer This is to test for you.

Yup, tested and works correctly.


Not able to run app in local workbench after upgrading spfx to 1.6.0

Category

[ ] Question
[ ] Typo
[x] Bug
[ ] Additional article idea

Expected or Desired Behavior
After upgrading to SPFx 1.6.0, app should run in both local and hosted workbenches without any issues.
Observed Behavior
App runs in hosted workbench. However, I see the following error while running the app in local workbench:

Steps to Reproduce
npm i -g @microsoft/generator-sharepoint@latest
Create a new project with 1.6
Copy over the tsconfig.json from new project to existing project.
Make the 2 changes listed in the "Build and tooling changes in 1.6.0" section in the release notes:
https://github.com/SharePoint/sp-dev-docs/wiki/SharePoint-Framework-v1.6-release-notes#build-and-tooling-changes-in-160
Delete node_modules folder
Run npm install
gulp serve --nobrowser
Followed this video to upgrade:
https://www.youtube.com/watch?v=dWmuXjXlZV8
Am I missing any steps which would cause the local workbench to not work? Thanks!

@vman Please let me know if you have suggestions to fix this issue. Thanks!

Based on https://github.com/SharePoint/sp-dev-docs/issues/2062, the issue is that something broke in a recent SPFx update with a dependency. When running gulp serve --nobrowser, none of the necessary packages to run the workbench are copied into the ./temp/workbench-packages. A workaround on this issue is to copy the files from the above folder when running gulp serve to a safe location, then when running gulp serve --nobrowser, copy that folder back in, replacing the empty ./temp/workbench-packages folder. Would there be a better fix for this issue soon? Thanks!

Looking into this.  Thanks for the heads up.

OK, so there was a change in how some of the code is laid down.  To get this to work properly with --nobrowser, navigate to https://localhost:5432/workbench .  It copies all of the packages, and redirects to :4321/temp/workbench.html
Looking into when this change was made, and if we need to do anything specific, or just document what steps need to be followed.

@licypal are you trying to set the breakpoint in the browser or in the code editor?

@waldekmastykarz In the code editor.

@patmill Thank you!

@licypal are you following the steps as described in the docs at https://docs.microsoft.com/en-us/sharepoint/dev/spfx/debug-in-vscode?


Add support for AWS Elasticsearch

Update image with the fluent-plugin-aws-elasticsearch-service gem, https://github.com/atomita/fluent-plugin-aws-elasticsearch-service which allows you to specify an IAM access key/secret key for an IAM account to write to ES.

I'm currently working on that part for my current setup.
@repeatedly would you prefer that to be a brand new image or just add it as an option to the existing debian-elasticsearch one?

Actually, I deployed the aws elasticsearch proxy service inside k8s cluster.
And, use fluent-bit/fluent-d to publish data to proxy service.
I checked the atomita's plugin but feel no one maintain that for a long time.

Interesting. Are you talking about https://github.com/abutaha/aws-es-proxy ?
I've been using teh atomia plugin for a very long time outside of that project and am currently migrating to using this project, just adding the gem from https://github.com/atomita/fluent-plugin-aws-elasticsearch-service . There's been some activity on it lately thanks to @cosmo0920 .

@aerostitch
Yes.
container image: abutaha/aws-es-proxy:0.9

@hixichen @aerostitch  would love to hear more about the aws-es-proxy and any issues you've run into doing so.
Would ideally be best if the stable helm chart https://github.com/kiwigrid/helm-charts/tree/master/charts/fluentd-elasticsearch ? had a way to do this setup or similar.
But still - would rather hear first hand from others who've done it the issues they've faced.. reliability.. scaling.. gotchas.. etc

I tried the https://github.com/abutaha/aws-es-proxy but it does not seem ready for production. It has 13 open issues at the moment, 2 of which are deal killers for me: it fails to pass along 403 or 302 responses. When it encounters those responses from upstream (Elasticsearch or Kibana), it sends an empty 200 response downstream.
So I am using  the mozilla-services proxy  proxy instead, as it seems to be in much better shape than the other one, is very easy to configure, and the whole Docker image is only 11 MB.

Hi Team.
Is there solution for this ?
Thanks in advance.

See https://github.com/fluent/fluentd-kubernetes-daemonset/pull/317

See #317

Thanks bro... I'll test and comment any issue

Can anyone please tell me how can I know if my fluentd is working properly. The daemon-set pods are running with no restarts, but there is still no index to Kibana. Here is my logs for the fluentd pod.
kubectl logs -f fluentd-6c6f9b575c-vgh7k
2020-12-17 14:13:57 +0000 [info]: parsing config file is succeeded path="/etc/fluent/fluent.conf"
2020-12-17 14:13:57 +0000 [info]: [elasticsearch] Detected ES 6.x: ES 7.x will only accept `_doc` in type_name.
2020-12-17 14:13:57 +0000 [info]: using configuration file: <ROOT>
  <match fluent.**>
    @type null
  </match>
  <source>
    @type forward
    port 24224
    bind "<IP_ADDRESS>"
  </source>
  <match fluentd.**>
    @type null
  </match>
  <source>
    @type http
    port 9770
    bind "<IP_ADDRESS>"
  </source>
  <source>
    @type monitor_agent
    bind "<IP_ADDRESS>"
    port 24110
    tag "fluentd.monitor.metrics"
  </source>
  <match **>
    @id elasticsearch
    @type elasticsearch
    @log_level "info"
    include_tag_key true
    host "elasticsearch-client"
    port 9200
    scheme http
    ssl_version TLSv1
    logstash_format true
    <buffer>
      @type "file"
      path "/var/log/fluentd-buffers/kubernetes.system.buffer"
      flush_mode interval
      retry_type exponential_backoff
      flush_thread_count 2
      flush_interval 5s
      retry_forever
      retry_max_interval 30
      chunk_limit_size 2M
      queue_limit_length 8
      overflow_action block
    </buffer>
  </match>
  <system>
    root_dir "/tmp/fluentd-buffers/"
  </system>
</ROOT>
2020-12-17 14:13:57 +0000 [info]: starting fluentd-1.3.3 pid=1 ruby="2.3.3"
2020-12-17 14:13:57 +0000 [info]: spawn command to main:  cmdline=["/usr/bin/ruby2.3", "-Eascii-8bit:ascii-8bit", "/usr/local/bin/fluentd", "--under-supervisor"]
2020-12-17 14:13:58 +0000 [info]: gem 'fluent-plugin-concat' version '2.3.0'
2020-12-17 14:13:58 +0000 [info]: gem 'fluent-plugin-detect-exceptions' version '0.0.11'
2020-12-17 14:13:58 +0000 [info]: gem 'fluent-plugin-elasticsearch' version '3.0.2'
2020-12-17 14:13:58 +0000 [info]: gem 'fluent-plugin-kubernetes_metadata_filter' version '2.1.6'
2020-12-17 14:13:58 +0000 [info]: gem 'fluent-plugin-multi-format-parser' version '1.0.0'
2020-12-17 14:13:58 +0000 [info]: gem 'fluent-plugin-prometheus' version '1.3.0'
2020-12-17 14:13:58 +0000 [info]: gem 'fluent-plugin-systemd' version '1.0.1'
2020-12-17 14:13:58 +0000 [info]: gem 'fluentd' version '1.3.3'
2020-12-17 14:13:58 +0000 [info]: adding match pattern="fluent.**" type="null"
2020-12-17 14:13:58 +0000 [info]: adding match pattern="fluentd.**" type="null"
2020-12-17 14:13:58 +0000 [info]: adding match pattern="**" type="elasticsearch"
2020-12-17 14:13:58 +0000 [info]: #0 [elasticsearch] Detected ES 6.x: ES 7.x will only accept `_doc` in type_name.
2020-12-17 14:13:58 +0000 [info]: adding source type="forward"
2020-12-17 14:13:58 +0000 [info]: adding source type="http"
2020-12-17 14:13:58 +0000 [info]: adding source type="monitor_agent"
2020-12-17 14:13:58 +0000 [info]: #0 starting fluentd worker pid=11 ppid=1 worker=0
2020-12-17 14:13:58 +0000 [info]: #0 listening port port=24224 bind="<IP_ADDRESS>"
2020-12-17 14:13:58 +0000 [info]: #0 fluentd worker is now running worker=0

As of deployment process was improved, there is a room for newer image build pipeline if user helps continuously maintain  the image even though still have  #293 issue. if you still have interest to do it, please create PR.


testcafe hangs with --quarantine-mode on a page that throws an Error

What is your Test Scenario?
I'm testing an application that might throw an error on a page. (Because of wrong jquery.datatables initialization.) Since I have unstable tests, I use --quarantine-mode, but I want to see the errors, so I do not use --skip-js-errors.
What is the Current behavior?
Errors are not reported, instead testcafe hangs with the first test that throws an error.
Removing --quarantine-mode causes errors to be reported.
Running with 'chromium --incognito' also causes errors to be reported.
--skip-js-errors does not hang, but might hide the presence of errors.
Running 'chromium --incognito' behaves as expected, but for some reason 'chromium', 'chromium:headless', 'firefox', and 'firefox:headless' hang as described.
What is the Expected behavior?
Errors in the application code should be reported.
CPE Detail 36
 ✖ editor can set validity (screenshots:
 /home/delgado/projects/Airbus/cve-aggregation/airshield/js/testcafe/screenshots/2019-09-19_14-51-22/test-1/HeadlessChrome_76.0.3809_Linux_0.0.0/
errors/1.png)

   1) - Error in Role initializer -
      A JavaScript error occurred on "http://<IP_ADDRESS>:8003/airshield/cpes/36/".
      Repeat test actions in the browser and check the console for errors.
      If you see this error, it means that the tested website caused it. You can fix it or disable tracking JavaScript errors in TestCafe. To
      do the latter, enable the "--skip-js-errors" option.
      If this error does not occur, please write a new issue at:
      "https://github.com/DevExpress/testcafe/issues/new?template=bug-report.md".

      JavaScript error details:
      TypeError: Cannot read property 'style' of undefined
          at _fnCalculateColumnWidths (http://<IP_ADDRESS>:8003/airshield/static/js/airshield.bundle.js:7006:27)
          at _fnInitialise (http://<IP_ADDRESS>:8003/airshield/static/js/airshield.bundle.js:6125:4)
          at loadedInit (http://<IP_ADDRESS>:8003/airshield/static/js/airshield.bundle.js:2713:6)
          at loaded (http://<IP_ADDRESS>:8003/airshield/static/js/airshield.bundle.js:7742:5)
          at _fnLoadState (http://<IP_ADDRESS>:8003/airshield/static/js/airshield.bundle.js:7826:4)
          at HTMLTableElement.<anonymous> (http://<IP_ADDRESS>:8003/airshield/static/js/airshield.bundle.js:2722:5)
          at Function.each (http://<IP_ADDRESS>:8003/airshield/static/js/airshield.bundle.js:49959:19)
          at jQuery.fn.init.each (http://<IP_ADDRESS>:8003/airshield/static/js/airshield.bundle.js:49794:17)
          at jQuery.fn.init.DataTable [as dataTable] (http://<IP_ADDRESS>:8003/airshield/static/js/airshield.bundle.js:2288:8)
          at jQuery.fn.init.$.fn.DataTable (http://<IP_ADDRESS>:8003/airshield/static/js/airshield.bundle.js:16511:18)

      Browser: HeadlessChrome 76.0.3809 / Linux 0.0.0
      Screenshot:
      /home/delgado/projects/Airbus/cve-aggregation/airshield/js/testcafe/screenshots/2019-09-19_14-51-22/test-1/HeadlessChrome_76.0.3809_Linux_0
.0.0/errors/1.png

What is your web application and your TestCafe test code?
Unfortunately no public code.
Steps to Reproduce:
I think it should be possible to reproduce with --quarantine-mode on
any page that throws an exception.
Your Environment details:

testcafe version:                   1.5.0
node.js version:                    v.10.16.3
command-line arguments:  /usr/bin/node10 ./node_modules/testcafe/lib/cli chromium:headless airshield/js/testcafe/test_*.js --hostname localhost --screenshots airshield/js/testcafe/screenshots --quarantine-mode --concurrency=1 --screenshots-on-fails --app-init-delay 3000 --app 'yarn testcafe-db; yarn testcafe-server --noreload || sleep 2; netcat -z -w 2 localhost 8003' airshield/js/testcafe/test_vulnerabilities.js
browser name and version: Chromium Version 76.0.3809.132 (openSUSE Build) (64-Bit) as well as Firefox Version 60.8.0esr (64-Bit)
platform and version:          Linux openSUSE Leap 15.1

Hi @TauPan
I am afraid this information is not sufficient to find the cause of the issue. Could you please provide a page or a small example so that we can reproduce it on our side?

I see. I've just tried to reproduce it with https://github.com/TauPan/testcafe-4297 but apparently it's not so simple. (The hanging test is as simple as in the example, but the code causing it isn't.)
Not sure which of the many moving parts in my actual project might be causing this (e.g. running django runserver as an app, jquery, datatables, webpack, etc.).
Also there's a workaround (e.g. temporarily remove --quarantine-mode).

@TauPan
I'll close this issue for now, since we are unable to reproduce it. However, if you have an example, feel free to share it here. We'll reopen the issue. If we find the issue ourselves in the future we'll reopen it as well.


GetUserByName

Currently the GetUser method requires the id of the user. What about a GetUserByName method where we can pass in the username instead in case we dont have the id or need to get the id.
GET /users?username=:username

Sure, sounds fine to me.

Actually I realised the response comes back as a list and this is more a list command with a filter.
Using the ListUsers method w/ ListUserOptions works fine.
	git := gitlab.NewClient(nil, *token)
	git.SetBaseURL(*baseUrl)

	options := gitlab.ListUsersOptions{
		Username: username,
	}

	usrs, _, err := git.Users.ListUsers(&options)

	if err != nil {
		panic(err)
	}

	fmt.Println(usrs[0].ID)

Not needed


fix: add php 8.4 compatibility to latest 7.4 release

fixes https://github.com/googleapis/google-api-php-client/issues/2640
Adds PHP 8.4 compatibility to the latest PHP 7.4 release (2.16.0). This will be tagged as v2.16.1

Thanks for fixing this so quickly. I tested it with the following command:
composer require "google/apiclient:dev-2.16.x-php74 as 2.16.1"

And I can confirm that it's no longer showing the deprecation messages. So everything LGTM.

This has been released! You can install it as
composer require google/apiclient:2.16.1


Allow to configure auxclasspath for PMD

The property is called classpath for consistency with FindBugs

Great, thanks.
Have you signed the CLA? http://gradle.org/contributor-license-agreement/

Yes I did, last Friday.

Great, thanks.

Any feedback on this? Is there somehow I can help move this forward?

Hi Juan,
We'll need some kind of test coverage to verify that this actually works.
I'm also wondering if we should match the name of the property, i.e. call it auxclasspath.

@alkemist thanks for the reply.
I did ask on the mailing list for pointers as to how to test this a week ago but got no replies. I looked at similar properties and found no tests either. The best I can come out with is "set the property, run PMD and see it doesn't break", but not if the ant task is actually seeing the property properly defined (I have done manual tests to make sure of this, but nothing that can fit nicely into a unit test, since using the android checks for PMD would require the whole Android SDK just to build Gradle).
If just doing a "set it and make sure it doesn't break" is enough for you, I can have it right away.
I have no issue renaming the property, I was just trying to be consistent with other code quality plugins. FindBugs ALSO has an auxclasspath variable, wich is set through the classpath config var but whatever you guys are comfortable with.
Please let me know and I can have everything changed and ready by tomorrow at most.

I did ask on the mailing list for pointers as to how to test this a week ago but got no replies.

Sorry, I missed that.

If just doing a "set it and make sure it doesn't break" is enough for you, I can have it right away.

Not quite, we have to make sure it actually does what it is supposed to. What's the difference in the result when this property is set correctly and when it isn't? We should be able to write an integration test for this pretty easily.

I have no issue renaming the property, I was just trying to be consistent with other code quality plugins. FindBugs ALSO has an auxclasspath variable

That's a good enough reason (i.e. consistency) to keep it as it is.
I didn't realise that FindBugs has something analogous (which makes sense now I understand what this property actually is). We'll have to wire this in through the source set in the same way.
https://github.com/gradle/gradle/blob/release/subprojects/code-quality/src/main/groovy/org/gradle/api/plugins/quality/FindBugsPlugin.groovy#L115-115

Not quite, we have to make sure it actually does what it is supposed to. What's the difference in the result when this property is set correctly and when it isn't? We should be able to write an integration test for this pretty easily.

None directly visible in the pmd.xml file. The classpath is available for PMD rules that want to determine the hierarchy of a class, allowing for instance to determine if your class extends from android.app.Activity even when this is defined in the Android SDK, and not on your own code.
The best you can get is that some rules start reporting issues they would miss without it. I don't know of any other ruleset other than Android that uses this, but I confess I haven't researched it.

I didn't realise that FindBugs has something analogous (which makes sense now I understand what this property actually is). We'll have to wire this in through the source set in the same way.
https://github.com/gradle/gradle/blob/release/subprojects/code-quality/src/main/groovy/org/gradle/api/plugins/quality/FindBugsPlugin.groovy#L115-115

No problem, I can do that. For Android it will be useless  (since Android plugin doesn't use standard Java sourceset yet), but may be usefull for someone else (or when Android plugin gets fixed).

Confirmed. Only Android rules are currently relying on the auxclasspath. Requiring the Android SDK to build Gradle is certainly not an option.
The alternative would be to find (or write) a custom rule in a plugin to set to PMD through pmdClasspath and make sure the rule reports new issues when the classpath is properly set...
I feel like writing a rule, and having Gradle build it into a jar for another test to pass is a little bit too much... Having the jar directly into the project as a test resource would be easier, but I'm no fan of having a binary blob in the repository...
On another topic, I just added the automatic classpath config just like FindBugs, and added a test for it.

I feel like writing a rule, and having Gradle build it into a jar for another test to pass is a little bit too much... Having the jar directly into the project as a test resource would be easier, but I'm no fan of having a binary blob in the repository...

I've got no idea how hard it is to write a rule. If it's just java, then this wouldn't be too hard to wire together as the rule would just be another project in the build.

Just to make sure I''m understanding correctly. You would like me to add a directory under subprojects called pmd-test-rules or something of the sort, that would contain a gradle module generating a jar, and have the code-quality test suite depend on such project, to include that jar into a PMD run and check the generated results. Right?
If so, I can write a rule that will directly report a specific error if the classpath is defined, and have it run with / without the classpath and check for the report results.

I think what @alkemist is trying to say is your integration test could be a multi-project build where the rule comes from one project and the other project uses PMD + the first project's jar on the auxclasspath.

Here's an example of a multi-project integration test: https://github.com/gradle/gradle/blob/master/subprojects/core/src/integTest/groovy/org/gradle/api/ProfilingIntegrationTest.groovy
You'd write out a settings.gradle that included your 'rule-using' and 'rule' project.  Then you can put everything else in the build.gradle in the root to build them both and add the 'rule' project to 'rule-using' project's auxclasspath.  Then write out the source files, then run the PMD task in the 'rule-using' project looking for success/failure.

@big-guy thanks for your repy, sory I couldn't get to it earlier.
I'm still not sure if my code for both the 'rule-using' and 'rule' projects would have to be actual files I check in in this PR and have those modules as dependencies for my test, or be embeded in the integration test as are those in https://github.com/gradle/gradle/blob/master/subprojects/code-quality/src/integTest/groovy/org/gradle/api/plugins/quality/PmdPluginIntegrationTest.groovy#L188 and have those generate the jar as part of the integration test.
Thanks in advance.

The best way to develop an integration test would probably be to first develop a sample build that demonstrates the use of auxclasspath, without any external dependencies. This sample would:

Have a projectA that defines some additional classes/rules required by PMD, and compiles them into a Jar
Have a second projectB that runs PMD, adding the jar output of projectA to the new PMD classpath variable.
When :projectB:pmd is executed, there should be way to tell if the correct stuff is in the classpath: task failure, rule failure, whatever.

Once you have this sample project, it won't be hard to convert it into an integration test: there are a few ways to provide the source files to the test case, either by embedding the source directly in the test case, or by including them as resources.

Done! Added an integration test that builds a rule and configures it. It checks it works for the newly autoconfigured classpath, and it fails to detect the violation if the classpath is cleared.
Hope that's good enough, but let me know if it isn't.

Thanks. We'll get onto this pretty soon.

Thanks @jsotuyod
This will be in Gradle 2.8.  I simplified your integration tests to just detect if the auxclasspath was set/not set.

@big-guy awesome! Thanks!


⚠ Fortnite has degraded performance

In bce57ea, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1433 ms

Resolved: Fortnite performance has improved in 6f94c8f.


Allow setting of Docker image tag when deploying without building

Hi, thanks for the great tool!
I'm trying to deploy an app without building the Docker image (I already have it), by running:
kamal deploy --skip-push

Unfortunately, I'm unable to set the Docker image tag (a custom one, e.g. 1.2.3) as Kamal always takes the full commit SHA

Is this what I'm looking for?


[Snyk] Security upgrade axios from 1.6.8 to 1.7.8

Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project.
Snyk changed the following file(s):

advanced/dapps/react-dapp-v2-with-ethers/package.json
advanced/dapps/react-dapp-v2-with-ethers/yarn.lock

Note for zero-installs users
If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.
Vulnerabilities that will be fixed with an upgrade:

Issue
Score

Cross-site Scripting (XSS) SNYK-JS-AXIOS-6671926
  100

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Cross-site Scripting (XSS)

:tada: Snyk checks have passed. No issues have been found so far.
:white_check_mark: security/snyk check is complete. No issues have been found. (View Details)
:white_check_mark: license/snyk check is complete. No issues have been found. (View Details)


fp16 training problem

thanks for your projects! when I reimplement this project, I occur the follow problem:   File "/mnt/bn/experience0313/gengwenjia/R2-Tuning/models/adapter.py", line 72, in forward     v_emb = self.video_map(video_emb[i])  # B * T * P * C.  RuntimeError: "LayerNormKernelImpl" not implemented for 'Half'. And I checked all dependencies' version, do you know the possible reasons?

thanks for your projects! Can you provide some code for readers to run a demo? Input the video and query, output the results, so that we can more intuitively see how advanced your method is.

Hi @wenjiajia123! Thanks for reporting this problem. It is weird as it did not happen in our environment. Could you please double-check that the code is running on GPU instead of CPU? If the problem still exists, changing back to FP32 (by setting amp=None at here) should work.

I just check the log file, and I only modify the amp parameter, it's a little weird. 😂

Is it possibly caused by slow I/O? You may compare the data_time (time spent for data loading & pre-processing in seconds) at each step with our log.

this is my log file, it seems both time is much longer.

TBH, I currently have no idea about this. It seems more like an issue from the environment rather than the code (though you have confirmed that the dependencies are correct...). We'll see if there are other users mentioning this problem.

Again, please make sure the code is running on GPU. 😂

thanks for your reply, I wonder what's the total running time with using fp16? could it be the mian reason?🤔

We've tested FP32 training and it costs about three and a half hours.

hi, I have fixed the problem through reinstall torch because my cuda version is 11.4. but the data time costs much longer, do you know how to solve it? 😊

This is only for the first few steps. It would be faster after the warmup.


error

I get an error when trying to use with heroku.
The following error appears and does not work.
2019-05-19T06:10:15.450270+00:00 app[bot.1]:     from dhooks import Webhook, Embed
2019-05-19T06:10:15.450272+00:00 app[bot.1]: ImportError: No module named dhooks
2019-05-19T06:10:15.820141+00:00 heroku[bot.1]: Starting process with command python bot/main.py
2019-05-19T06:10:16.475837+00:00 heroku[bot.1]: State changed from starting to up
2019-05-19T06:10:17.572546+00:00 heroku[bot.1]: State changed from up to crashed
2019-05-19T06:10:17.432657+00:00 app[bot.1]: Traceback (most recent call last):
2019-05-19T06:10:17.432684+00:00 app[bot.1]:   File "bot/main.py", line 1, in
2019-05-19T06:10:17.432692+00:00 app[bot.1]:     from dhooks import Webhook, Embed
2019-05-19T06:10:17.432694+00:00 app[bot.1]: ImportError: No module named dhooks
2019-05-19T06:10:17.557295+00:00 heroku[bot.1]: Process exited with status 1
I want you to use it by all means, is there a solution?
I'm sorry for my poor English.

What version of python are you using?

Closing this issue since no respond from the end user.


Supplying the "project" variable results in an empty tuple error.

What did you expect to happen?
Terraform to create the required infrastructure in GCP.
What actually happened?
Terraform exited with an error: google_project.vault is empty tuple
Output
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.

random_id.kms_random: Refreshing state... [id=m6CgwO-xSrs]
random_id.project_random: Refreshing state... [id=tScE_X6fHyI]
tls_private_key.vault-ca: Refreshing state... [id=f9a5651496d6669594ec30977f50f1de244a7497]
tls_private_key.vault: Refreshing state... [id=9b6dfb19348a69a25f1ef2a31867531916a243fd]
tls_self_signed_cert.vault-ca: Refreshing state... [id=99395545586993871452207941606690158367]
data.google_client_config.current: Refreshing state...

Error: Invalid index

  on gcp.tf line 30, in data "google_project" "vault":
  30:   project_id = google_project.vault[0].project_id
    |----------------
    | google_project.vault is empty tuple

The given key does not identify an element in this collection value.

Additional context
I've created a one-line pull request to fix the issue: https://github.com/sethvargo/vault-on-gke/pull/65

Fixed in #65


Fix multi modal

Fixes #174

Demo:
ChatGPT-Breathtaking_Sunset_Picture.json
ChatGPT-Breathtaking_Sunset_Picture.md

ChatGPT-Breathtaking_Sunset_Picture.txt
ChatGPT-Breathtaking_Sunset_Picture.html.zip
ChatGPT-Dog_Sitting_Serenely.json
ChatGPT-Dog_Sitting_Serenely.md

ChatGPT-Dog_Sitting_Serenely.txt
ChatGPT-Dog_Sitting_Serenely.html.zip

Fixed lint issues. Thanks for correcting them in the other MR.

Thanks. I was quite confused about how to use the file API.


How it works a11y fixes

Replaced Carousel with FlatList component for performance
Fixed images flickering between screens
All content is read through a screen reader properly
Steps now increment when a screen reader is reading through each screen
Body text is separated into different Text components

@smcmurtry Could you verify if this works on iOS? I was able to get it working with TalkBack and had no issues going through the flow.

@nickmly as far as I'm aware we don't really have a problem with the carousel here. But I do want to get in the text splitting fix. Could you open another PR for that and we'll close this one.


When generating a REST API from a SOAP backend it does not generate all the required parameters for the SOAP operations

Description:
When generating a REST API from a SOAP backend it does not generate all the required parameters for the SOAP operations.
If you try to generate a REST API for the WSDL provided then for the "doLogin" SOAP operation which takes in 2 parameters (Login and Password) only one parameter will be generated.
wsdl: https://soap.proofhq.com/soap?wsdl
Steps to reproduce:

Generate a REST API from the WSDL given above from the API Publisher
Check the parameters in the "doLogin" SOAP operation from the swagger definition, you can observe that only one parameter has been generated. (whereas it should have 2)

Affected Product Version:
3.0.0 and 3.1.0 Alpha
Environment details (with versions):

OS: Ubuntu 19.04

tagging: https://github.com/wso2/product-apim/issues/7130


Focusing on first focus-able element by default is a major accessibility issue

I created a pull request for this issue here: https://github.com/davidtheclark/focus-trap/pull/55
The current implementation of focus-trap has a major accessibility issue that can easily be resolved by making the focus-trap container the default element that receives focus when the focus trap is activated.
For example, have a look at demo 1 on the demo site.
This is what the UX is like for a screen reader user using NVDA trying to use demo 1 running the current focus-trap default implementation:

Focus on activate button
"activate trap 1 [button]"
Press enter
"with [link]"

Now this is what it is like if you accept my pull request:

Focus on activate button
"activate trap 1 [button]"
Press enter
"Here is a focus trap with [link] some [link] focusable [link] parts. Deactivate trap 1"

See how much more accessible this default functionality is for screen reader users?

Thanks for the suggestion, @Dan503.
I don't think I'm convinced yet that this is the best default behavior for focus-trap. I believe you already  can accomplish it — focusing a container element — but in many cases it may not be desirable.
For example, in the WAI-ARIA Authoring Practices modal dialog description, they recommend first focusing an interactive element or title when a modal opens, not the modal's container element.
You're right that in your example the verbosity seems helpful; but I'm not sure whether that's reflective of a realistic encounter a screen-reader user would have with a well-designed component.
So, considering that this behavior should be possible now and those ARIA recommendations don't prescribe it in the most common focus-trapping situation (a modal), I'm inclined to think the current defaults are fine. Still open to more information, though.

but in many cases it may not be desirable.

Can you give an example?

the best possible accessibility for modal dialogues

Unless I see more information to the contrary, I feel like I should trust the WAI-ARIA Authoring Practices to tell me what's accessible behavior for a modal dialog. And you haven't addressed your divergence from their recommendations.
I believe there is some authoritative work in support of your suggestion, e.g. https://developer.paciellogroup.com/blog/2018/06/the-current-state-of-modal-dialog-accessibility/. However, I find more suggestions in line with the WAI-ARIA Authoring Practices. If you can find more authoritative info, I'd be very interested. But maybe not for this library so much as for modal components ...

We are talking default behaviour here so we are generally talking about implementation by devs who just want it to work and aren't thinking that much about accessibility.

That is not the concern of this library. It can be used in a universally accessible way (and ideally would be). But it doesn't have to be: for example, it could be used in a way that targets sighted keyboard users. focus-trap is not endorsing anything: it is a low-level utility library that other things can be built on top of. This isn't a modal component — it's mean to be used by modal components.
If you'd like to make a modal library that uses focus-trap in the way that you think is best, you should! Happy to link to it in the readme.

Plus there is also the added benefit of the plugin not throwing an error if the user triggers a focus-trap on an element that has no tabbables inside of it.

I still don't think this is a benefit: that situation is a user error.

So: I think that if you'd like to propose an option to include the container in the focus trap, I'd be open to that. I'm not sure we need a significant, breaking change, though, to address concerns that may be more appropriately addressed in higher-order libraries.

I've had a thought on how this can be implemented without causing a major breaking change to the plugin.
What if by default on activation, focus-trap also takes tabindex="-1" elements and it's container into consideration on where it sends it's initial focus to?
So if the user adds tabindex="-1" to the focus-trap container, then the container will receive focus by default. If a heading inside the container has tabindex="-1" then the heading will receive focus.
It should only take tabindex="-1" elements into consideration on initial focus. They should not be taken into consideration after inital focus.
To make this easier in this plugin, it would be good if there was an includeNegatives option in the Tabbable plugin.
This means that people can get the container focus functionality by default as long as they manually add the negative tabindex property to the focus-trap element themselves.
I don't think it is likely to break current implementations since it requires the user to explicitly add a negative tabindex in the HTML for it to change the functionality.
I'd prefer container focus to be the general default functionality but I don't see that happening. Would you be open to this as a solution?

This is already possible, exemplified in the demo, and now mentioned in the docs, so I don't think changes are necessary. But thanks for the discussion.

I don't see any warnings in the documentation about the potential accessibility issues that come from sending focus to the first focusable element.
There should at least be a warning somewhere to notify users of the potential issue.


Update istio.io/api

This can be updated nor or the automated script in istio/api will run when there is a new checkin. I'll close this out if the automated PR gets merged


MB-13718 convert tests to use transactions

Jira ticket for this change
Summary
Converts the folowing testS to use transactions:

./pkg/payment_request
./pkg/route
./pkg/server
./pkg/parser/transittime
./pkg/services/ghcdieselfuelprice
./pkg/services/fuelprice

this article explains more about the approach used.
Setup to Run Your Code
Run make server_test and make sure everything passes
Verification Steps for Author
These are to be checked by the author.

[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

Verification Steps for Reviewers
These are to be checked by a reviewer.

Frontend

[ ] User facing changes have been reviewed by design.
[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] There are no new console errors in the browser devtools
[ ] There are no new console errors in the test output
[ ] If this PR adds a new component to Storybook, it ensures the component is fully responsive, OR if it is intentionally not, a wrapping div using the officeApp class or custom min-width styling is used to hide any states the would not be visible to the user.

Backend

[ ] Code follows the guidelines for Logging
[ ] The requirements listed in Querying the Database Safely have been satisfied.

Database
Any new migrations/schema changes:

[ ] Follows our guidelines for Zero-Downtime Deploys
[ ] Have been communicated to #g-database
[ ] Secure migrations have been tested following the instructions in our docs

Screenshots

Messages

:book:
:link: MB-13718

  Generated by :no_entry_sign: dangerJS against 0aeff4b1ddb8b5bc2d5f2e802712df2193cf953c

I was actually unable to get the tests to pass. I thought it was my setup at first but I managed to run main and pass everything. Can you check that the tests pass? Errors were largely in TestAllGenerateEdi


Remove/enable tests that make dynamic shapes static

With PR #4900 the codegen path drops support for dynamic shapes for a short period of time. Switching over to the Linalg on tensors path gives back ability to generate code for dynamic shapes. This is realted to some phase ordering issue that exists in the current codegen path, and dropping of some mechanisms that were added to counteract that.
Some tests were modified to handle static shapes only. Either remove these tests or change them back to static shapes when moved to linalg on tensors path.

Most of these tests have been removed/replaced. Closing the issue


useGqlHeaders and useGqlToken aren't reactive

When using useGqlHeaders or useGqlToken, I would assume that the passed values can be refs and that the headers/tokens would update on subsequent requests if the refs change.
A simple use-case is sending along JWT access-tokens that change after each GraphQL call.
Currently it will use just use the initial passed in value.

Currently it will use just use the initial passed in value.

Indeed.
Allowing reactive values to be passed and updated accordingly would certainly be a welcomed improvement, I had initially avoided that very implementation to reduce unintended side effects and ultimately make the debugging process easier on developers' ( having to explicitly call the functions when you wish to affect the underlying request )

Hey @Diizzayy I am having issue with the 'Currently it will use just use the initial passed in value' mentioned above. I have implemented a basic JWT refresh token middleware but when I attempt to clear out the headers via useGqlHeaders or useGqlToken the are sent anyway.
Accepting reactive values would be a great enhancement but could you allow static values to work if updated in a middleware?

I think this is a question related to this - I can't find out how to properly implement it though:
Before every request, I want to call:
useGqlHeaders(useRequestHeaders['cookie']));

or do the equivalent via config.  I'm not able to figure out how, though.  I see this is closed, and it sounds like what I'm trying to do, but I can't find any documentation on how to implement.


breaking down the reverse-eng, for http requests

Hey @tchellomello, this is really great work with the reverse engineering.
I've never developed with Python, or groovy, or Java, so I'm totally out of luck for trying to use your library.
I see that you're using http for the communication to the controller. I'm wondering if there's any way to break it down even further so that the valves could be opened and closed with a simple HTTP request?
I'm thinking that could be a way to use that with homebridge to create a water controller device type or, at the very least, a switch.

Hello @JangoBritt,
Thanks for your kind words. I was only the one that started the work, but lately, @vanstinator  has been helping a lot to the project.
In a nutshell, to open or close a valve is due to an HTTP request, however, due to the implementation on Melnor's side, there are some rules and processes you have to do in order to acquire a token and be authorized to do it.
You could create a script that uses raincloudy on the backend and make it compatible with HomeBridge. I don't have nor used HomeBridge, but if you can plug a custom script there, you can use the library to help you out with this integration.
If you want o to create a connector or extend the library to Homebridge, it would be very appreciated too.
Thanks!

Will have to agree with @tchellomello here. The best course of action would probably be building a wrapper around raincloudy to make this work. Personally I'd rather see this approach than adding Homebridge functionality to this repo. I'd prefer to see raincloudy stay simple and implementation agnostic.


between page exist equal component throw error

Version 4.0.3
Steps to reproduce

custom component，example：popup-phone
page-A import popup-phone in

find bugs，in the popup-phone component used caused by


How to distinguish search from pagination

I want to use cached data for pagination, but i don't know in controller if request is pagination or new search.

Pagination passes query parameters in a form of [Grid.Name-]Page=X&[Grid.Name-]Rows=Y, so you can check if they are set in Request.QueryString and continue from there.

Thanks.
If i were on the page 2 and do ajax search there is still paging info in query string.
When i set any value in query parameter paging invo removed.
 $('.mvc-grid').mvcgrid({
                    query: 'refresh=true', //this removes paging from query string
                    requestType: 'post', // defaults to get
                    name:"partner-pretraga",
                    reload: true,
                    data: $("#pretraga").serialize()
                });

Yes, because you are setting the whole query If that's the problem you can take the current query from $('.mvc-grid').mvcgrid('instance').query and modify it, but I usually reset paging information on every new search to improve user experience and avoid over paging problems.


update to biolink 2.2.x

Per the weekly Translator email, we need to update to Biolink 2.2.x.  There should be no breaking changes so it should be a straightforward update, but needs to be tested.
For reference, #207 tracked update to v2.1.x

Note:

in biolink v2.2.1, new predicates "has real world evidence of association with" and its inverse. For clinical KPs (so multiomics KPs will need x-bte annotation change?)

x-bte changes to use "has real world evidence of association with" seems reasonable to me.  My guess is that predicate will be used in workflow B queries?
On the new predicate mixins, are you saying that we need new code to query those mixins, similar to how we do predicate expansion in the predicate subclass hierarchy?

I'm not sure whether we currently handle predicate mixins...that involves asking Marco?
And the predicate is being used in workflows B and C. I agree that it involves talking to multiomics provider about what operations to change the predicate on...

Updating the file failed a test on account of a predicate being renamed (test has been updated). I diffed the files to check for anything else that might be relevant, just in case:

A number of is_a definitions were updated for various predicates.
relation has been deprecated
A few new predicates were added, such as taxon of
A few new association slots were added, such as original_subject
Some mappings, ID prefixes, aliases changed/added


Use rbconfig to check for host OS

jRuby reports the platform as 'java' rather than the underlying OS. Therefore, to make the check for the host OS compatible w/ the jRuby environment, you need to instead (or additionally) use Config::CONFIG['host_os'] provided by rbconfig.

Could you use the RbConfig constant instead?
(pry):1: Use RbConfig instead of obsolete and deprecated Config.
=> RbConfig

Oops, didn't realize that one was deprecated. Sure thing.
On Tue, Mar 6, 2012 at 05:05, Nando Vieira <
<EMAIL_ADDRESS>
wrote:

Could you use the RbConfig constant instead?
(pry):1: Use RbConfig instead of obsolete and deprecated Config.
=> RbConfig

Reply to this email directly or view it on GitHub:
https://github.com/fnando/notifier/pull/8#issuecomment-4341721

--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://google.com/profiles/dan.j.allen
http://mojavelinux.com
http://mojavelinux.com/seaminaction


Fix off by one error in waitgroup

Fixes issue described in https://github.com/scottjbarr/sqsmv/issues/32

Thanks for catching the error in my PR!


Pass options to generated GeoJson

Thanks for sharing the great omnivore plugin. One thing i really miss is that you do not provide a way to pass options to the generated geojson object.
I know you provide the ready event but for some cases it does not work. For instance I want to generate a CircleMarker for a given point. Usually the GeoJSON layer turns the point into a marker, with the pointToLayer callback I can change this.
So it would be really helpful if you allow to pass the pointToLayer, style, onEachFeature, filter and coordsToLatLng to the geojson layer.
I know by creating a custom layer before and pass it, also works...
Any reasons not to add this feature?

I don't totally follow:

One thing i really miss is that you do not provide a way to pass options to the generated geojson object.

and

I know by creating a custom layer before and pass it, also works...

By creating a custom layer and passing options to it, there is a way to provide options to the generated geojson object. How is this not clear, especially when you state it here and it's thoroughly documented as the first example in the readme?

Sorry, I've read the documentation, but simply missed the way to solve it. During writing this issue I've understood how to do it.
Nevermind, gonna close it.


Cannot install  libhdfs3

Describe the bug
Hi:
I want to use hdfs with cpp,so I install libhdfs3 package use vcpkg, but meet libhdfs3 install failed,the dependency sub package I try many time finally the sub dependency packages all install successfully,but libhdfs3 can not install ,it is install failed.
the log

(base) muller@mullermac ~ % vcpkg install libhdfs3
Computing installation plan...
The following packages will be built and installed:
    libhdfs3[core]:x64-osx -> 2019-11-05
Detecting compiler hash for triplet x64-osx...
Could not locate cached archive: /Users/muller/.cache/vcpkg/archives/e2/e2d541ed69e495e65366ca0bb921aad2b53d18f6.zip
Starting package 1/1: libhdfs3:x64-osx
Building package libhdfs3[core]:x64-osx...
-- Using cached /usr/local/Cellar/vcpkg/2021.05.12/libexec/downloads/erikmuttersbach-libhdfs3-9a60d79812d6dee72455f61bff57a93c3c7d56f5.tar.gz
-- Cleaning sources at /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/src/3c3c7d56f5-99403534e7.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source /usr/local/Cellar/vcpkg/2021.05.12/libexec/downloads/erikmuttersbach-libhdfs3-9a60d79812d6dee72455f61bff57a93c3c7d56f5.tar.gz
-- Using source at /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/src/3c3c7d56f5-99403534e7.clean
-- Configuring x64-osx-dbg
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:105 (message):
    Command failed: /usr/local/Cellar/vcpkg/2021.05.12/libexec/downloads/tools/cmake-3.20.2-osx/cmake-3.20.2-macos-universal/CMake.app/Contents/bin/cmake /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/src/3c3c7d56f5-99403534e7.clean -DCMAKE_MAKE_PROGRAM=/usr/local/Cellar/vcpkg/2021.05.12/libexec/downloads/tools/ninja-1.10.1-osx/ninja -DCMAKE_SYSTEM_NAME=Darwin -DBUILD_SHARED_LIBS=OFF -DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=/usr/local/Cellar/vcpkg/2021.05.12/libexec/scripts/toolchains/osx.cmake -DVCPKG_TARGET_TRIPLET=x64-osx -DVCPKG_SET_CHARSET_FLAG=ON -DVCPKG_PLATFORM_TOOLSET=external -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE -DCMAKE_VERBOSE_MAKEFILE=ON -DVCPKG_APPLOCAL_DEPS=OFF -DCMAKE_TOOLCHAIN_FILE=/usr/local/Cellar/vcpkg/2021.05.12/libexec/scripts/buildsystems/vcpkg.cmake -DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON -DVCPKG_CXX_FLAGS= -DVCPKG_CXX_FLAGS_RELEASE= -DVCPKG_CXX_FLAGS_DEBUG= -DVCPKG_C_FLAGS= -DVCPKG_C_FLAGS_RELEASE= -DVCPKG_C_FLAGS_DEBUG= -DVCPKG_CRT_LINKAGE=dynamic -DVCPKG_LINKER_FLAGS= -DVCPKG_LINKER_FLAGS_RELEASE= -DVCPKG_LINKER_FLAGS_DEBUG= -DVCPKG_TARGET_ARCHITECTURE=x64 -DCMAKE_INSTALL_LIBDIR:STRING=lib -DCMAKE_INSTALL_BINDIR:STRING=bin -D_VCPKG_ROOT_DIR=/usr/local/Cellar/vcpkg/2021.05.12/libexec -D_VCPKG_INSTALLED_DIR=/usr/local/Cellar/vcpkg/2021.05.12/libexec/installed -DVCPKG_MANIFEST_INSTALL=OFF -DCMAKE_OSX_ARCHITECTURES=x86_64 -G Ninja -DCMAKE_BUILD_TYPE=Debug -DCMAKE_INSTALL_PREFIX=/usr/local/Cellar/vcpkg/2021.05.12/libexec/packages/libhdfs3_x64-osx/debug
    Working Directory: /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/x64-osx-dbg
    Error code: 1
    See logs for more information:
      /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/config-x64-osx-dbg-out.log
      /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/config-x64-osx-dbg-err.log

Call Stack (most recent call first):
  scripts/cmake/vcpkg_configure_cmake.cmake:332 (vcpkg_execute_required_process)
  ports/libhdfs3/portfile.cmake:11 (vcpkg_configure_cmake)
  scripts/ports.cmake:142 (include)

Error: Building package libhdfs3:x64-osx failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with `./vcpkg update`, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
  Package: libhdfs3:x64-osx
  Vcpkg version: 2021-05-05-unknownhash

Additionally, attach any relevant sections from the log files above.

Environment

OS: macos
Compiler: vcpkg 2021.5.12
cmake 3.24

To Reproduce
Steps to reproduce the behavior:

./vcpkg install xxxx
See error
Repro code when

Expected behavior
A clear and concise description of what you expected to happen.
Failure logs
-(please attached failure logs)
Additional context
Add any other context about the problem here.

I find  in linux centos 7 ,use vcpkg install apache-arrow, also meet install failed

Please send these two logs to us, thank you!
    /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/config-x64-osx-dbg-out.log
    /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/config-x64-osx-dbg-err.log

(base) muller@mullermac arrow % cat /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/config-x64-osx-dbg-out.log
-- The C compiler identification is AppleClang <IP_ADDRESS>00027
-- The CXX compiler identification is AppleClang <IP_ADDRESS>00027
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /Library/Developer/CommandLineTools/usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /Library/Developer/CommandLineTools/usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- checking compiler: CLANG
-- Looking for dladdr
-- Looking for dladdr - found
-- Looking for nanosleep
-- Looking for nanosleep - found
-- adding c++0x support for clang compiler
-- Checking whether strerror_r returns an int
-- Checking whether strerror_r returns an int -- yes
-- Found LibXml2: /usr/local/Cellar/vcpkg/2021.05.12/libexec/installed/x64-osx/debug/lib/libxml2.a (found version "2.9.10")
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
-- Found Threads: TRUE
-- Found ZLIB: /usr/local/Cellar/vcpkg/2021.05.12/libexec/installed/x64-osx/debug/lib/libz.a (found version "1.2.11")
-- Found Protobuf: optimized;/usr/local/Cellar/vcpkg/2021.05.12/libexec/installed/x64-osx/lib/libprotobuf.a;debug;/usr/local/Cellar/vcpkg/2021.05.12/libexec/installed/x64-osx/debug/lib/libprotobufd.a (found version "3.15.8")
-- Found KERBEROS: /Library/Developer/CommandLineTools/SDKs/MacOSX12.3.sdk/usr/lib/libkrb5.tbd
-- Could NOT find GSASL (missing: GSASL_LIBRARIES GSASL_INCLUDE_DIR)
-- Configuring done
-- Generating done

 cat   /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/config-x64-osx-dbg-err.log
CMake Deprecation Warning at CMakeLists.txt:1 (CMAKE_MINIMUM_REQUIRED):
  Compatibility with CMake < 2.8.12 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

CMake Warning (dev) at /usr/local/Cellar/vcpkg/2021.05.12/libexec/downloads/tools/cmake-3.20.2-osx/cmake-3.20.2-macos-universal/CMake.app/Contents/share/cmake-3.20/Modules/FindPackageHandleStandardArgs.cmake:438 (message):
  The package name passed to `find_package_handle_standard_args` (GSASL) does
  not match the name of the calling package (GSasl).  This can lead to
  problems in calling code that expects `find_package` result variables
  (e.g., `_FOUND`) to follow a certain pattern.
Call Stack (most recent call first):
  CMake/FindGSasl.cmake:24 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
  /usr/local/Cellar/vcpkg/2021.05.12/libexec/scripts/buildsystems/vcpkg.cmake:861 (_find_package)
  CMakeLists.txt:21 (FIND_PACKAGE)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Deprecation Warning at mock/CMakeLists.txt:1 (CMAKE_MINIMUM_REQUIRED):
  Compatibility with CMake < 2.8.12 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

CMake Deprecation Warning at src/CMakeLists.txt:1 (CMAKE_MINIMUM_REQUIRED):
  Compatibility with CMake < 2.8.12 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

CMake Deprecation Warning at gtest/CMakeLists.txt:1 (CMAKE_MINIMUM_REQUIRED):
  Compatibility with CMake < 2.8.12 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

CMake Deprecation Warning at gmock/CMakeLists.txt:1 (CMAKE_MINIMUM_REQUIRED):
  Compatibility with CMake < 2.8.12 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

CMake Deprecation Warning at test/CMakeLists.txt:1 (CMAKE_MINIMUM_REQUIRED):
  Compatibility with CMake < 2.8.12 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

CMake Deprecation Warning at test/function/CMakeLists.txt:1 (CMAKE_MINIMUM_REQUIRED):
  Compatibility with CMake < 2.8.12 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

CMake Deprecation Warning at test/unit/CMakeLists.txt:1 (CMAKE_MINIMUM_REQUIRED):
  Compatibility with CMake < 2.8.12 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

CMake Deprecation Warning at test/unit/CMakeLists.txt:2 (CMAKE_MINIMUM_REQUIRED):
  Compatibility with CMake < 2.8.12 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

CMake Deprecation Warning at test/secure/CMakeLists.txt:1 (CMAKE_MINIMUM_REQUIRED):
  Compatibility with CMake < 2.8.12 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake files:
GSASL_INCLUDE_DIR (ADVANCED)
   used as include directory in directory /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/src/3c3c7d56f5-99403534e7.clean/src
   used as include directory in directory /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/src/3c3c7d56f5-99403534e7.clean/src
   used as include directory in directory /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/src/3c3c7d56f5-99403534e7.clean/src
   used as include directory in directory /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/src/3c3c7d56f5-99403534e7.clean/src
   used as include directory in directory /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/src/3c3c7d56f5-99403534e7.clean/src
   used as include directory in directory /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/src/3c3c7d56f5-99403534e7.clean/src
   used as include directory in directory /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/src/3c3c7d56f5-99403534e7.clean/src
   used as include directory in directory /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/src/3c3c7d56f5-99403534e7.clean/src
   used as include directory in directory /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/src/3c3c7d56f5-99403534e7.clean/test/function
   used as include directory in directory /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/src/3c3c7d56f5-99403534e7.clean/test/function
   used as include directory in directory /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/src/3c3c7d56f5-99403534e7.clean/test/function
   used as include directory in directory /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/src/3c3c7d56f5-99403534e7.clean/test/function
   used as include directory in directory /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/src/3c3c7d56f5-99403534e7.clean/test/function
   used as include directory in directory /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/src/3c3c7d56f5-99403534e7.clean/test/function
   used as include directory in directory /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/src/3c3c7d56f5-99403534e7.clean/test/function
   used as include directory in directory /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/src/3c3c7d56f5-99403534e7.clean/test/unit
   used as include directory in directory /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/src/3c3c7d56f5-99403534e7.clean/test/unit
   used as include directory in directory /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/src/3c3c7d56f5-99403534e7.clean/test/unit
   used as include directory in directory /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/src/3c3c7d56f5-99403534e7.clean/test/unit
   used as include directory in directory /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/src/3c3c7d56f5-99403534e7.clean/test/unit
   used as include directory in directory /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/src/3c3c7d56f5-99403534e7.clean/test/unit
   used as include directory in directory /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/src/3c3c7d56f5-99403534e7.clean/test/unit
   used as include directory in directory /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/src/3c3c7d56f5-99403534e7.clean/test/secure
   used as include directory in directory /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/src/3c3c7d56f5-99403534e7.clean/test/secure
   used as include directory in directory /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/src/3c3c7d56f5-99403534e7.clean/test/secure
   used as include directory in directory /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/src/3c3c7d56f5-99403534e7.clean/test/secure
   used as include directory in directory /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/src/3c3c7d56f5-99403534e7.clean/test/secure
   used as include directory in directory /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/src/3c3c7d56f5-99403534e7.clean/test/secure
   used as include directory in directory /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/src/3c3c7d56f5-99403534e7.clean/test/secure
GSASL_LIBRARIES (ADVANCED)
    linked by target "libhdfs3-shared" in directory /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/src/3c3c7d56f5-99403534e7.clean/src
    linked by target "libhdfs3-static" in directory /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/src/3c3c7d56f5-99403534e7.clean/src
    linked by target "function" in directory /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/src/3c3c7d56f5-99403534e7.clean/test/function
    linked by target "unit" in directory /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/src/3c3c7d56f5-99403534e7.clean/test/unit
    linked by target "secure" in directory /usr/local/Cellar/vcpkg/2021.05.12/libexec/buildtrees/libhdfs3/src/3c3c7d56f5-99403534e7.clean/test/secure

CMake Warning (dev) in src/CMakeLists.txt:
  Policy CMP0021 is not set: Fatal error on relative paths in
  INCLUDE_DIRECTORIES target property.  Run "cmake --help-policy CMP0021" for
  policy details.  Use the cmake_policy command to set the policy and
  suppress this warning.

  Found relative path while evaluating include directories of
  "libhdfs3-shared":

    "GSASL_INCLUDE_DIR-NOTFOUND"

This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) in src/CMakeLists.txt:
  Policy CMP0021 is not set: Fatal error on relative paths in
  INCLUDE_DIRECTORIES target property.  Run "cmake --help-policy CMP0021" for
  policy details.  Use the cmake_policy command to set the policy and
  suppress this warning.

  Found relative path while evaluating include directories of
  "libhdfs3-shared":

    "GSASL_INCLUDE_DIR-NOTFOUND"

This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) in src/CMakeLists.txt:
  Policy CMP0021 is not set: Fatal error on relative paths in
  INCLUDE_DIRECTORIES target property.  Run "cmake --help-policy CMP0021" for
  policy details.  Use the cmake_policy command to set the policy and
  suppress this warning.

  Found relative path while evaluating include directories of
  "libhdfs3-static":

    "GSASL_INCLUDE_DIR-NOTFOUND"

This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) in src/CMakeLists.txt:
  Policy CMP0021 is not set: Fatal error on relative paths in
  INCLUDE_DIRECTORIES target property.  Run "cmake --help-policy CMP0021" for
  policy details.  Use the cmake_policy command to set the policy and
  suppress this warning.

  Found relative path while evaluating include directories of
  "libhdfs3-static":

    "GSASL_INCLUDE_DIR-NOTFOUND"

This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) in test/function/CMakeLists.txt:
  Policy CMP0021 is not set: Fatal error on relative paths in
  INCLUDE_DIRECTORIES target property.  Run "cmake --help-policy CMP0021" for
  policy details.  Use the cmake_policy command to set the policy and
  suppress this warning.

  Found relative path while evaluating include directories of "function":

    "GSASL_INCLUDE_DIR-NOTFOUND"

This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) in test/function/CMakeLists.txt:
  Policy CMP0021 is not set: Fatal error on relative paths in
  INCLUDE_DIRECTORIES target property.  Run "cmake --help-policy CMP0021" for
  policy details.  Use the cmake_policy command to set the policy and
  suppress this warning.

  Found relative path while evaluating include directories of "function":

    "GSASL_INCLUDE_DIR-NOTFOUND"

This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) in test/unit/CMakeLists.txt:
  Policy CMP0021 is not set: Fatal error on relative paths in
  INCLUDE_DIRECTORIES target property.  Run "cmake --help-policy CMP0021" for
  policy details.  Use the cmake_policy command to set the policy and
  suppress this warning.

  Found relative path while evaluating include directories of "unit":

    "GSASL_INCLUDE_DIR-NOTFOUND"

This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) in test/unit/CMakeLists.txt:
  Policy CMP0021 is not set: Fatal error on relative paths in
  INCLUDE_DIRECTORIES target property.  Run "cmake --help-policy CMP0021" for
  policy details.  Use the cmake_policy command to set the policy and
  suppress this warning.

  Found relative path while evaluating include directories of "unit":

    "GSASL_INCLUDE_DIR-NOTFOUND"

This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) in test/secure/CMakeLists.txt:
  Policy CMP0021 is not set: Fatal error on relative paths in
  INCLUDE_DIRECTORIES target property.  Run "cmake --help-policy CMP0021" for
  policy details.  Use the cmake_policy command to set the policy and
  suppress this warning.

  Found relative path while evaluating include directories of "secure":

    "GSASL_INCLUDE_DIR-NOTFOUND"

This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) in test/secure/CMakeLists.txt:
  Policy CMP0021 is not set: Fatal error on relative paths in
  INCLUDE_DIRECTORIES target property.  Run "cmake --help-policy CMP0021" for
  policy details.  Use the cmake_policy command to set the policy and
  suppress this warning.

  Found relative path while evaluating include directories of "secure":

    "GSASL_INCLUDE_DIR-NOTFOUND"

This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Generate step failed.  Build files cannot be regenerated correctly.

Upstream instructions to build libhdfs3, the following libraries are needed. Therefore, these two tripartite libraries need to be installed on your system.
libuuid                         http://sourceforge.net/projects/libuuid/
libgsasl                        http://www.gnu.org/software/gsasl/