Fix bug in confirm prompt to ensure it respects style setting

Fix bug in confirm prompt to ensure it respects style setting in prompt options sent via PromptAsync

Pull Request Test Coverage Report for Build 87368

0 of 0   changed or added relevant lines in 0 files are covered.
38 unchanged lines in 10 files lost coverage.
Overall coverage decreased (-0.06%) to 76.486%

Files with Coverage Reduction
New Missed Lines
%

/libraries/Adapters/Microsoft.Bot.Builder.Adapters.Facebook/FacebookAdapter.cs
1
96.72%

/libraries/Adapters/Microsoft.Bot.Builder.Adapters.Facebook/FacebookClientWrapper.cs
1
92.59%

/libraries/Microsoft.Bot.Builder.Dialogs/Prompts/ConfirmPrompt.cs
1
93.55%

/libraries/Adapters/Microsoft.Bot.Builder.Adapters.Twilio/TwilioAdapter.cs
2
91.84%

/libraries/Adapters/Microsoft.Bot.Builder.Adapters.Webex/WebexAdapter.cs
2
91.67%

/libraries/Adapters/Microsoft.Bot.Builder.Adapters.Slack/SlackAdapter.cs
4
96.15%

/libraries/Adapters/Microsoft.Bot.Builder.Adapters.Twilio/TwilioHelper.cs
4
63.38%

/libraries/Adapters/Microsoft.Bot.Builder.Adapters.Facebook/FacebookHelper.cs
6
67.86%

/libraries/Adapters/Microsoft.Bot.Builder.Adapters.Slack/SlackHelper.cs
7
83.87%

/libraries/Adapters/Microsoft.Bot.Builder.Adapters.Twilio/TwilioClientWrapper.cs
10
29.17%

Totals

Change from base Build 87245:
-0.06%

Covered Lines:
8067

Relevant Lines:
10547

💛  - Coveralls

If I may suggest, we're moving to a model where PR's have to have issue numbers, and be formatted in a "Fixes #XYZ" format. These rules (and a few others) will be enforced by Github actions.
Could you add an issue/bug number to this?
Also - does the same bug exist in the JS side? IF so, can you link them?


fix: removes 3 unnecessary api calls from zrxswapper.

Removes 3 unnecessary API calls in the ZrxSwapper.
Should speed things up

@0xdef1cafe should this pull request have a commit including BREAKING CHANGE: that affects a @shapeshiftoss/types file?


Update node-fetch install in eliminate-js.md

node-fetch was converted to be a ESM only package in version 3.0.0-beta.10. node-fetch is an ESM-only module - you are not able to import it with require. We recommend you stay on v2 which is built with CommonJS unless you use ESM yourself. We will continue to publish critical bug fixes for it.

source

Hi there, just wanted to check in and make sure I understood your feedback correctly. Does this seem like an okay revision for the docs? I haven't cloned the repo and have been doing edits via github which is why there are two separate commits. Happy to squash if necessary.


Doris version 0.11.0 dockerfile ask maven version 3.6.0，but where is it???????

@yangbiao121

we have fixed mvn version to 3.6.3 in master branch.
It is not a good idea to build docker file yourself. we have already provided a docker image, you can use it directly.

I will close this issue.


Add Jason Gu to the board members page

Name: Jason Gu
Desc: Hi! My name is Jason and I am currently a fourth year data science major. As VP Internal I am here to help members around me and make everyone feel welcomed within this org. In my free time I enjoy playing the guitar, singing, going to the gym, going on late night drives, and any outdoor activities. Feel free to reach out to me whenever!
Linkedin: https://www.linkedin.com/in/jingchenggu/
Role: VP Internal
PFP: https://drive.google.com/open?id=1W1qEuIJPuMGwBQzOOCGD1oTARYRhqlOR
Resume: https://drive.google.com/open?id=1AwHHIlAteFZorGDis7DcN91biQqYnS3r
UCSD email<EMAIL_ADDRESS>Relevant Docs: https://www.notion.so/ds3ucsd/Updating-Board-Members-fb4406f46a9e43f0aecf8b155ab06b39

Google Drive img sharing is down for google forms rn


how to remove a particular entry from archivebox scheduling list?

I am a first time user of ArchiveBox, and I have added multiple entries in my ArchiveBox Scheduler.  How can I do it?

We don't have a native way to remove an individual entry from the CLI at the moment, it's a tricky problem because the file can be in a few different formats, can be edited directly by users and other programs, and not all the scheduler running methods are stateful (e.g. --foreground doesn't store a crontab at all).
Here are some options to accomplish what you need though:

Option 1. locate the crontab file for you user and remove individual lines from there
We use python-crontab internally to create scheduled jobs (which in-turn uses UNIX's crontab system with a crontab file for your user). https://pypi.org/project/python-crontab/
from crontab import CronTab

>>> c = CronTab(user=True)
>>> c.tabfile
>>> ... figure out where your crontab file is located by exploring more attrs on this object

Then edit/remove individual lines from that file, e.g. /var/spool/cron/crontabs/username

Option 2. Clear the whole list and add back entries manually
# backup the list of schedule jobs to a file somewhere
archivebox schedule --show > ~/Desktop/schedule_backup.txt

# clear the whole list of scheduled jobs registered in the crontab
archivebox schedule --clear

# then add them back in manually from ~/Desktop/schedule_backup.txt
archivebox schedule --add ...

Thank you for the guidance. it was very helpful.


add blog

So in general, I'm asking for some pretty major changes here. We can chat over slack or zoom or w/e to have a more nuanced discussion about my points if you'd like.

👍


Resolve conflict between envvar and cmdline arg for same resource

Description
What happens when envvar and cmdline arg for same resource specify different values?
We need to add a couple tests regarding color:

Given both envvar FORCE_COLOR and --no-color, is color enabled?
Given both envvar FORCE_COLOR=1 and --no-color, is color enabled?
Given both envvar FORCE_COLOR=0 and --color, is color enabled?

Mocha's option parsing with yargs-parser/yargs does not consider environment variables. Closing.


When run in build mode, analyzer examines pubspec.yaml file even if not supplied

With the following directory structure:
pubspec.yaml:
  name: test
  version: 1.0.0
  environment:
    sdk: ^2.0.0

lib/foo.dart:
  Object foo() => {1, 2, 3};

Run the analyzer like so:
$PATH_TO_DART_SDK/bin/dartanalyzer --build-mode 'package:foo/foo.dart|lib/foo.dart'

Observed result:
Analyzing package:foo/foo.dart|lib/foo.dart...
  hint • Set literals were not supported until version 2.2, but this code is required to be able to run on earlier versions at lib/foo.dart:1:17 • sdk_version_set_literal
1 hint found.

Expected result:

No errors.

The reason there should be no errors has to do with the contract of build mode: when run in build mode, the analyzer must not examine any input file unless it was explicitly supplied on the command line.  So even though there is a pubspec.yaml file present, it should be ignored.
Why does build mode have this contractual requirement?  It has to do with how the analyzer is run by the Bazel build tool.  Normally, Bazel runs build rules in a sandbox where the only files present are the ones explicitly specified as inputs in the user's BUILD file.  So if the analyzer goes looking for an input that wasn't expected, it won't find it.  This sandboxing is how Bazel keeps builds reproducible--it ensures that if an input is needed to do a build, the user won't forget to explicitly add it to their BUILD file.
But when Bazel runs the analyzer in "worker" mode, it skips creating the sandbox and relies on the analyzer to only examine input files that it's explicitly granted access to.  (Worker mode is a performance optimization that leaves the analyzer process alive after a build step, and then re-uses it for subsequent build steps; that way VM startup and JIT compilation penalties are amortized.)  If the analyzer accesses other input files, then that causes two problems: (1) it means that the analyzer will get different results between worker and non-worker builds (which is terribly confusing, because performance optimizations aren't expected to change analysis results), and (2) it means that if the user changes one of these other input files, Bazel won't know that it's necessary to re-run the build step (because it didn't know that file was a dependency), so the user will see stale build results.
The way this manifests is that if there's a package in a Bazel build environment with a pubspec.yaml file, and the package uses a feature (such as set literals) that wasn't available in the Dart version in its minimum SDK constraint, then no hint will be reported when Bazel is run normally, but an error will be reported if Bazel is run with the analyzer in "worker" mode.  If the user tries to correct the hint they see in build mode by updating pubspec.yaml, the hint won't go away.
In the long term what we should probably do is:

Add the ability for a pubspec.yaml to be explicitly specified on the command line when running in build mode
Update the Bazel starlark rules for Dart so that when building a package that contains pubspec.yaml, it will be explicitly specified on the command line when running the analyzer.
Change the analyzer behavior so that in build mode, if pubspec.yaml isn't specified on the command line, it acts as if the file isn't present in the filesystem.

However, in the short term I think we should change the analyzer behavior so that in build mode, pubspec.yaml files are ignored.  That will restore parity between worker and non-worker mode and ensure that builds are reproducible.

Consider a filtering resource provider that drops pubspecs when in build mode.

I think there is no longer --build-mode.


Adds Set function to allow jumps longer than 290 years and simplify usage.

With Advance function you can't jump more than 290 years (required for some tests).
Also in many places I have to use something like this:
fc.Advance(newTime.Sub(fc.Now()))

Which could be improved with Set function.

I have some comments. I think they should be visible. My github-fu is a little weak.

They are. For me it's the first PR...


Updated organzation definition for extracting organization names from a body of text

If your PR is related to a contribution to the taxonomy, please, fill
out the following questionnaire. If not, replace this whole text and the
following questionnaire with whatever information is applicable to your PR.
Describe the contribution to the taxonomy

added to qna.yml for "compositional_skills/extraction/information/named_entities/organization" to provide the model a skill for extracting organization information from a body of text
...

Input given at the prompt

   ...

Response from the original model

  ...

Response from the fine-tuned model

  ...

Contribution checklist

[ ] The contribution was tested with lab generate
[ ] No errors or warnings were produced by lab generate
[ ] All commits are signed off (DCO)
[ ] The qna.yaml file contains at least 5 seed_examples
[ ] The qna.yaml file was linted and prettified (yaml-validator can do both)

Thank you for your contribution to InstructLab! Unfortunately, once a Github repo is made public, all open PRs are automatically closed since they link against a private repo. We have detected that your PR might have been one of the ones affected by this change. If you are still interested in contributing your improvement, please fill out the following short form by no later than May 3rd, and we will get back to you with the additional steps necessary once we have had time to assess the PRs of those still interested:
https://forms.gle/V7SrPPMZDo6iGDYu8


Firebase Push Notification

Description:
Push notification.
Why is this needed to be done?
Workers should be notified when hirers create a request and hirers should be notified when a worker accepts or rejects the request.
Implementation:
A push notification can be sent whenever a new document is added to the firebase cloud store.

Please assign this issue to me.


Add did:indy as supported issuer did method

Needs #1

Implemented, but somehow very slow with indicio testnet. Maybe it's the network. It also seems to be resolving the did multiple times just to issue a credential. It should be cached


Demo gh-1405

Demo for reproducing gh-1405: if spring-boot app is decorated with @EnableJpaRepositories,

"regular" images start correctly (mvn clean spring-boot:run)
"native" image won't (mvn clean spring-boot:build-image && docker run --rm -p 8080:8080  -t data-jpa:0.0.1-SNAPSHOT) .

For for the repro, this will be fixed and checked in the sample via #1405.


Fix Build Badge

Hard-wire the build badge to only show the result for the master branch.  The default was to show the result of the latest build.

Great! Thanks, @erikerikson!


Updating the Hybrid AAD join documentation

Through this pull request the following changes are being made

Updating the SMB documentation on how to enroll devices to domain joined devices to Microsoft Intune using the new simplified method
Updating the git ignore file to exclude the .vs directory

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks

@Sirkkuw Please merge this PR. Thanks


Update Sharp version requirement

Hello,
it seems like there is an issue with the version of Sharp required by this module. When I npm install Sharp package separately, it build fine, but when image-resizer tries to install it as a dependency, the build fails.
To install it, I had to modify the version of Sharp required by image-resizer package.json module in ~.npm cache.

Hi @OriginalEXE,
Any chance you can provide more information about this? I am not able to replicate this at all, either with v0.10.1 which is the current version required by image-resizer or the newer version v0.11.3. I am going to bump the version in the next release but from my tests I cant see an issue with this.

Hi,
here are the logs:
12285 verbose about to build /var/www/playground/node_modules/image-resizer
12286 verbose unlock done using /home/originalexe/.npm/_locks/image-resizer-89a535f21d4a8313.lock for /var/www/playground/node_modules/image-resizer
12287 verbose stack Error<EMAIL_ADDRESS>install: `node-gyp rebuild`
12287 verbose stack Exit status 1
12287 verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:214:16)
12287 verbose stack     at emitTwo (events.js:87:13)
12287 verbose stack     at EventEmitter.emit (events.js:172:7)
12287 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:24:14)
12287 verbose stack     at emitTwo (events.js:87:13)
12287 verbose stack     at ChildProcess.emit (events.js:172:7)
12287 verbose stack     at maybeClose (internal/child_process.js:818:16)
12287 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
12288 verbose pkgid<EMAIL_ADDRESS>12289 verbose cwd /var/www/playground
12290 error Linux 3.19.0-26-generic
12291 error argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "image-resizer"
12292 error node v4.1.2
12293 error npm  v2.14.4
12294 error code ELIFECYCLE
12295 error<EMAIL_ADDRESS>install: `node-gyp rebuild`
12295 error Exit status 1
12296 error Failed at the<EMAIL_ADDRESS>install script 'node-gyp rebuild'.
12296 error This is most likely a problem with the sharp package,
12296 error not with npm itself.
12296 error Tell the author that this fails on your system:
12296 error     node-gyp rebuild
12296 error You can get their info via:
12296 error     npm owner ls sharp
12296 error There is likely additional logging output above.
12297 verbose exit [ 1, true ]
12298 verbose unbuild node_modules/image-resizer/node_modules/sharp
12299 info preuninstall<EMAIL_ADDRESS>12300 info uninstall<EMAIL_ADDRESS>12301 verbose unbuild rmStuff<EMAIL_ADDRESS>from /var/www/playground/node_modules
12302 verbose unbuild rmStuff in /var/www/playground/node_modules/image-resizer/node_modules
12303 info postuninstall<EMAIL_ADDRESS>12304 silly gentlyRm /var/www/playground/node_modules/image-resizer/node_modules/sharp is being purged from base /var/www/playground
12305 verbose gentlyRm don't care about contents; nuking /var/www/playground/node_modules/image-resizer/node_modules/sharp
12306 silly vacuum-fs purging /var/www/playground/node_modules/image-resizer/node_modules/sharp
12307 silly vacuum-fs quitting because other entries in /var/www/playground/node_modules/image-resizer/node_modules
12308 verbose unbuild node_modules/image-resizer
12309 info preuninstall<EMAIL_ADDRESS>12310 info uninstall<EMAIL_ADDRESS>12311 verbose unbuild rmStuff<EMAIL_ADDRESS>from /var/www/playground/node_modules
12312 silly gentlyRm /var/www/playground/node_modules/.bin/image-resizer is being gently removed
12313 silly gentlyRm verifying /var/www/playground is an npm working directory
12314 silly gentlyRm containing path /var/www/playground is under npm's control, in /var/www/playground
12315 silly gentlyRm deletion target /var/www/playground/node_modules/.bin/image-resizer is under /var/www/playground
12316 verbose gentlyRm vacuuming from /var/www/playground/node_modules/.bin/image-resizer up to /var/www/playground
12317 info postuninstall<EMAIL_ADDRESS>12318 silly gentlyRm /var/www/playground/node_modules/image-resizer is being purged from base /var/www/playground
12319 verbose gentlyRm don't care about contents; nuking /var/www/playground/node_modules/image-resizer
12320 silly vacuum-fs purging /var/www/playground/node_modules/image-resizer
12321 silly vacuum-fs removing /var/www/playground/node_modules
12322 silly vacuum-fs finished vacuuming up to /var/www/playground

From the terminal:
><EMAIL_ADDRESS>install /var/www/playground/node_modules/image-resizer/node_modules/sharp
> node-gyp rebuild

make: Entering directory `/var/www/playground/node_modules/image-resizer/node_modules/sharp/build'
  CXX(target) Release/obj.target/sharp/src/common.o
  CXX(target) Release/obj.target/sharp/src/utilities.o
In file included from ../src/utilities.cc:4:0:
../node_modules/nan/nan.h:324:27: error: redefinition of ‘template<class T> v8::Local<T> Nan::imp::NanEnsureHandleOrPersistent(const v8::Local<T>&)’
   NAN_INLINE v8::Local<T> NanEnsureHandleOrPersistent(const v8::Local<T> &val) {
                           ^
../node_modules/nan/nan.h:319:17: error: ‘template<class T> v8::Handle<T> Nan::imp::NanEnsureHandleOrPersistent(v8::Handle<T>&)’ previously declared here
   v8::Handle<T> NanEnsureHandleOrPersistent(const v8::Handle<T> &val) {
                 ^
../node_modules/nan/nan.h:344:27: error: redefinition of ‘template<class T> v8::Local<T> Nan::imp::NanEnsureLocal(v8::Handle<T>&)’
   NAN_INLINE v8::Local<T> NanEnsureLocal(const v8::Handle<T> &val) {
                           ^
../node_modules/nan/nan.h:334:27: error: ‘template<class T> v8::Local<T> Nan::imp::NanEnsureLocal(const v8::Local<T>&)’ previously declared here
   NAN_INLINE v8::Local<T> NanEnsureLocal(const v8::Local<T> &val) {
                           ^
../node_modules/nan/nan.h:757:13: error: ‘node::smalloc’ has not been declared
     , node::smalloc::FreeCallback callback
             ^
../node_modules/nan/nan.h:757:35: error: expected ‘,’ or ‘...’ before ‘callback’
     , node::smalloc::FreeCallback callback
                                   ^
../node_modules/nan/nan.h: In function ‘v8::Local<v8::Object> NanNewBufferHandle(char*, size_t, int)’:
../node_modules/nan/nan.h:761:50: error: ‘callback’ was not declared in this scope
         v8::Isolate::GetCurrent(), data, length, callback, hint);
                                                  ^
../node_modules/nan/nan.h:761:60: error: ‘hint’ was not declared in this scope
         v8::Isolate::GetCurrent(), data, length, callback, hint);
                                                            ^
../node_modules/nan/nan.h: In function ‘v8::Local<v8::Object> NanNewBufferHandle(const char*, uint32_t)’:
../node_modules/nan/nan.h:768:67: error: call of overloaded ‘New(v8::Isolate*, const char*&, uint32_t&)’ is ambiguous
     return node::Buffer::New(v8::Isolate::GetCurrent(), data, size);
                                                                   ^
../node_modules/nan/nan.h:768:67: note: candidates are:
In file included from ../node_modules/nan/nan.h:25:0,
                 from ../src/utilities.cc:4:
/home/originalexe/.node-gyp/4.1.2/include/node/node_buffer.h:31:40: note: v8::MaybeLocal<v8::Object> node::Buffer::New(v8::Isolate*, v8::Local<v8::String>, node::encoding) <near match>
 NODE_EXTERN v8::MaybeLocal<v8::Object> New(v8::Isolate* isolate,
                                        ^
/home/originalexe/.node-gyp/4.1.2/include/node/node_buffer.h:31:40: note:   no known conversion for argument 3 from ‘uint32_t {aka unsigned int}’ to ‘node::encoding’
/home/originalexe/.node-gyp/4.1.2/include/node/node_buffer.h:43:40: note: v8::MaybeLocal<v8::Object> node::Buffer::New(v8::Isolate*, char*, size_t) <near match>
 NODE_EXTERN v8::MaybeLocal<v8::Object> New(v8::Isolate* isolate,
                                        ^
/home/originalexe/.node-gyp/4.1.2/include/node/node_buffer.h:43:40: note:   no known conversion for argument 2 from ‘const char*’ to ‘char*’
In file included from ../src/utilities.cc:4:0:
../node_modules/nan/nan.h: In function ‘v8::Local<v8::Object> NanNewBufferHandle(uint32_t)’:
../node_modules/nan/nan.h:772:61: error: could not convert ‘node::Buffer::New(v8::Isolate::GetCurrent(), ((size_t)size))’ from ‘v8::MaybeLocal<v8::Object>’ to ‘v8::Local<v8::Object>’
     return node::Buffer::New(v8::Isolate::GetCurrent(), size);
                                                             ^
../node_modules/nan/nan.h: In function ‘v8::Local<v8::Object> NanBufferUse(char*, uint32_t)’:
../node_modules/nan/nan.h:779:12: error: ‘Use’ is not a member of ‘node::Buffer’
     return node::Buffer::Use(v8::Isolate::GetCurrent(), data, size);
            ^
make: *** [Release/obj.target/sharp/src/utilities.o] Error 1
make: Leaving directory `/var/www/playground/node_modules/image-resizer/node_modules/sharp/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:270:23)
gyp ERR! stack     at emitTwo (events.js:87:13)
gyp ERR! stack     at ChildProcess.emit (events.js:172:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
gyp ERR! System Linux 3.19.0-26-generic
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /var/www/playground/node_modules/image-resizer/node_modules/sharp
gyp ERR! node -v v4.1.2
gyp ERR! node-gyp -v v3.0.3
gyp ERR! not ok
npm ERR! Linux 3.19.0-26-generic
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "image-resizer"
npm ERR! node v4.1.2
npm ERR! npm  v2.14.4
npm ERR! code ELIFECYCLE

npm ERR<EMAIL_ADDRESS>install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the sharp package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls sharp
npm ERR! There is likely additional logging output above.

that looks like a sharp issue with node v4.1.2. As a temporary workaround I would suggest setting the node engine in your package.json to v.0.12.7.
I will check into issues with v4.1.2.

Actually, I had the same issue with the latest 0.12.x version of node. I opened this ticket 29 days ago and I was not running a node 4.x back then, it was only released.
I don't think you need to lose time on figuring this out though, if you will bump the sharp version in the new version, it will work fine as that's what I did to get sharp to build.

OK good to know. New version coming up soon, just working on your other issue #72


Liquid Syntax Error in _layouts/post.liquid line 59

Have you checked that your issue isn't already filed?

[X] I read through FAQ and searched through the past issues, none of which addressed my issue.
[X] Yes, I have checked that this issue isn't already filed.

Bug description
Liquid Syntax Error in _layouts/post.liquid line 59 with the original project
How to reproduce the bug

go to https://github.com/alshedivat/al-folio
click "Use This Template"
In the drop down manu, click "Create a new repository"
Now you are in your own repo with this template
Do not change anything.
Install missing gems with `bundle install`.
Warning: The github-pages gem can't satisfy your Gemfile's dependencies. If you want to use a different Jekyll version or need additional dependencies, consider building Jekyll site with GitHub Actions: https://jekyllrb.com/docs/continuous-integration/github-actions/
To use retry middleware with Faraday v2.0+, install `faraday-retry` gem
  Liquid Exception: Liquid syntax error (line 5[9](https://github.com/david-wei-01001/temp/actions/runs/8577271982/job/23509620788#step:4:10)): Unknown tag 'toc' in /_layouts/post.liquid
/usr/local/bundle/gems/liquid-4.0.4/lib/liquid/block.rb:38:in `unknown_tag': Liquid syntax error (line 59): Unknown tag 'toc' (Liquid::SyntaxError)
	from /usr/local/bundle/gems/liquid-4.0.4/lib/liquid/tags/if.rb:38:in `unknown_tag'
	from /usr/local/bundle/gems/liquid-4.0.4/lib/liquid/block.rb:68:in `block in parse_body'
	from /usr/local/bundle/gems/liquid-4.0.4/lib/liquid/block_body.rb:32:in `parse'
	from /usr/local/bundle/gems/liquid-4.0.4/lib/liquid/block.rb:58:in `parse_body'
	from /usr/local/bundle/gems/liquid-4.0.4/lib/liquid/tags/if.rb:30:in `parse'
	from /usr/local/bundle/gems/liquid-4.0.4/lib/liquid/tag.rb:10:in `parse'
	from /usr/local/bundle/gems/liquid-4.0.4/lib/liquid/block_body.rb:34:in `parse'
	from /usr/local/bundle/gems/liquid-4.0.4/lib/liquid/document.rb:10:in `parse'
	from /usr/local/bundle/gems/liquid-4.0.4/lib/liquid/document.rb:5:in `parse'
	from /usr/local/bundle/gems/liquid-4.0.4/lib/liquid/template.rb:130:in `parse'
	from /usr/local/bundle/gems/liquid-4.0.4/lib/liquid/template.rb:114:in `parse'
	from /usr/local/bundle/gems/jekyll-3.9.5/lib/jekyll/liquid_renderer/file.rb:13:in `block in parse'
	from /usr/local/bundle/gems/jekyll-3.9.5/lib/jekyll/liquid_renderer/file.rb:49:in `measure_time'
	from /usr/local/bundle/gems/jekyll-3.9.5/lib/jekyll/liquid_renderer/file.rb:12:in `parse'
	from /usr/local/bundle/gems/jekyll-3.9.5/lib/jekyll/renderer.rb:121:in `render_liquid'
	from /usr/local/bundle/gems/jekyll-3.9.5/lib/jekyll/renderer.rb:195:in `render_layout'
	from /usr/local/bundle/gems/jekyll-3.9.5/lib/jekyll/renderer.rb:158:in `place_in_layouts'
	from /usr/local/bundle/gems/jekyll-3.9.5/lib/jekyll/renderer.rb:88:in `render_document'
	from /usr/local/bundle/gems/jekyll-3.9.5/lib/jekyll/renderer.rb:62:in `run'
	from /usr/local/bundle/gems/jekyll-3.9.5/lib/jekyll/site.rb:479:in `render_regenerated'
	from /usr/local/bundle/gems/jekyll-3.9.5/lib/jekyll/site.rb:464:in `block (2 levels) in render_docs'
	from /usr/local/bundle/gems/jekyll-3.9.5/lib/jekyll/site.rb:463:in `each'
	from /usr/local/bundle/gems/jekyll-3.9.5/lib/jekyll/site.rb:463:in `block in render_docs'
	from /usr/local/bundle/gems/jekyll-3.9.5/lib/jekyll/site.rb:462:in `each_value'
	from /usr/local/bundle/gems/jekyll-3.9.5/lib/jekyll/site.rb:462:in `render_docs'
	from /usr/local/bundle/gems/jekyll-3.9.5/lib/jekyll/site.rb:191:in `render'
	from /usr/local/bundle/gems/jekyll-3.9.5/lib/jekyll/site.rb:71:in `process'
	from /usr/local/bundle/gems/jekyll-3.9.5/lib/jekyll/command.rb:28:in `process_site'
	from /usr/local/bundle/gems/jekyll-3.9.5/lib/jekyll/commands/build.rb:65:in `build'
	from /usr/local/bundle/gems/jekyll-3.9.5/lib/jekyll/commands/build.rb:36:in `process'
	from /usr/local/bundle/gems/github-pages-231/bin/github-pages:70:in `block (3 levels) in <top (required)>'
	from /usr/local/bundle/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `block in execute'
	from /usr/local/bundle/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `each'
	from /usr/local/bundle/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `execute'
	from /usr/local/bundle/gems/mercenary-0.3.6/lib/mercenary/program.rb:42:in `go'
	from /usr/local/bundle/gems/mercenary-0.3.6/lib/mercenary.rb:19:in `program'
	from /usr/local/bundle/gems/github-pages-231/bin/github-pages:6:in `<top (required)>'
	from /usr/local/bundle/bin/github-pages:23:in `load'
	from /usr/local/bundle/bin/github-pages:23:in `<main>'
Error:  Logging at level: debug Configuration file: /github/workspace/./_config.yml GitHub Pages: github-pages v231 GitHub Pages: jekyll v3.9.5 Theme: jekyll-theme-primer Theme source: /usr/local/bundle/gems/jekyll-theme-primer-0.6.0 Requiring: jekyll-github-metadata Requiring: jekyll-seo-tag Requiring: jekyll-feed Requiring: jekyll-sitemap Requiring: jemoji Requiring: jekyll-coffeescript Requiring: jekyll-commonmark-ghpages Requiring: jekyll-gist Requiring: jekyll-github-metadata Requiring: jekyll-paginate Requiring: jekyll-relative-links Requiring: jekyll-optional-front-matter Requiring: jekyll-readme-index Requiring: jekyll-default-layout Requiring: jekyll-titles-from-headings GitHub Metadata: Initializing... Source: /github/workspace/. Destination: /github/workspace/./_site Incremental build: disabled. Enable with --incremental Generating...  Generating: JekyllReadmeIndex::Generator finished in 7.5351e-05 seconds. Jekyll Feed: Generating feed for posts Generating: JekyllFeed::Generator finished in 0.000776573 seconds. Generating: Jekyll::JekyllSitemap finished in 0.00[20](https://github.com/david-wei-01001/temp/actions/runs/8577271982/job/23509620788#step:4:21)00048 seconds. Generating: Jekyll::Paginate::Pagination finished in 5.239e-06 seconds. Generating: JekyllRe

Pictures also supplied:

What operating system are you using?
Not applicable (e.g. you're using GitHub Pages or other hosting)
Where are you seeing the problem on?
Deployed site
More info
This was found when I finish editing my customized webpage and trying to deploy it. The same error appears. I saw that it was in a file that I need not look or change, so I hypothesize that this is an error with the initial repository, so I restart the forking process and deploy immediately to get the default webpage, and yes on this new repo where I did not touch at all, deployment also failed with the same error.

You did it wrong. As stated in the recommended approach, you should set to deploy from gh-pages branch, NOT master branch.

Yeah yeah of course. I resolved the problem by closely following the INSTALL.md.
I was trying to close this issue but I don't know how to.
Sorry about this!

I propose to change the name INSTALL.md to INSTALL And DEPLOY.md
The reason why I missed it is because I thought I was not installing anything, I am simply deploying it, so I ignored this file...

Will change the name of it in the README, but no need to change the name of the file.


Type 'CAEmitterLayerEmitterShape' (aka 'NSString') has no member 'line'

Issue occur for Xcode 10.2

I believe this is if your Swift version is less than 4.2.
You can use emitter.emitterShape = kCAEmitterLayerLine instead.


[bug] slider cannot swipe back to previous slide when it has only two children

If there are only two children in one slider and user swipe to the second one, then he cannot swipe back to the first one. Please checkout this demo: demo url. The demo code was copied from examples in the docs.
If there are more children, there will be no problem.
You can use Weex Playground iOS App(1.3) to reproduce this issue.

OS version: iOS 10.2
weex version: 0.9.4

This PR/issue doesn't receive response since Weex migrated to Apache two years ago and this repository is no longer active yet.
Feel free to ask question in new repository and thanks for your contribution.

This issue is outdated for a long time and will be closed now. You can create a new one if you still have questions.


UTXO ThorChain Savers TX's Don't Update to Confirmed on Mobile

Overview
After testing UTXO thorchain savers deposits, going to the asset page and clicking on the TXID from that send shows pending forever. Vault balance also won't update until you close out of the app and reopen it.
Recreation Steps:

Deposit into a UTXO ThorChain Savers Vault on mobile
Once that TXID confirms, go to the asset page on mobile and click on the TXID of that send.
Notice that pending TX is still there and that DeFi modal hasn't updated native or fiat amounts.

References and additional details

Acceptance Criteria
Confirmed ThorChain TXID's should update to confirmed on transaction history on mobile and DeFi overview page should update native and fiat amounts on confirmed as well on mobile.
Need By Date
No response
Screenshots/Mockups
No response
Estimated effort
No response

@tshifty can you confirm that this is happening exclusively within the mobile app and not when using the app from a regular browser on mobile / desktop ?

@gomesalexandre It only does this on the mobile app. Not through the browser on the phone. It's a very weird bug

FYI, a user is reporting this issue with BTC yields 3/17/23

closing as sporadic websocket issues rather than specifically related to savers - any fixable bug would occur consistently on all devices


Add an example for PullRequestsService.Create

This PR is about providing an example on how to create a pull request (it's always nice to have examples in the godoc).

I signed it! :smile_cat:

Thanks, but I don't think you should make that change. The other examples do not need authentication because they perform read operations on public data. They'll work okay without auth.
Only the new PullRequest.Create example you're adding needs authentication.
Additionally, I think all that auth code detracts from the point of the example. I think adding a comment saying that authentication is needed and linking to the documentation at https://godoc.org/github.com/google/go-github/github#hdr-Authentication for more information is a better way to go.
We want to keep the quality of the examples high.
If you'd like to add the example code for doing auth via oauth2 package, we can make that a separate dedicated example covering authentication only. But that should be a separate PR. For this one, please revert these changes and add a comment instead.

@shurcooL I reverted the auth changes and added a comment about authentication.
Not sure if you saw my comment on the outdated change so here it is:

But you can't see the code of newGitHubClientWithAuth in the final godoc if you do that right?
So that would be a bit misleading for the user that thinks the newGitHubClientWithAuth is an unexported helper from the package right?

Thanks for the review!
Yes, I think that adding newGitHubClientWithAuth (while useful in real-life programs) would be more confusing than it would provide help for new users reading the documentation on godoc.

Thank you for improving the package documentation @aerostitch!
The example is visible at https://godoc.org/github.com/google/go-github/github#example-PullRequestsService-Create now.


No such file or directory: './npy/ffhq/W.npy' when execute python GetCode.py

I try the code in StyleCLIP_global.ipynb, the first job is to prepare the input data. When I execute the following commends, I get the FileNotFoundError:
Traceback (most recent call last):
File "GetCode.py", line 214, in
save_tmp=GetS(dataset_name,num_img=2_000)
File "GetCode.py", line 132, in GetS
dlatents=np.load(tmp)[:num_img]
File "/Users/liukai/opt/anaconda3/lib/python3.8/site-packages/numpy/lib/npyio.py", line 416, in load
fid = stack.enter_context(open(os_fspath(file), "rb"))
FileNotFoundError: [Errno 2] No such file or directory: './npy/ffhq/W.npy'
dataset_name='ffhq' #@param ['ffhq'] {allow-input: true}
input dataset name
#%cd /content/StyleCLIP/global/
input prepare data
!python GetCode.py --dataset_name $dataset_name --code_type 'w'
!python GetCode.py --dataset_name $dataset_name --code_type 's'
!python GetCode.py --dataset_name $dataset_name --code_type 's_mean_std'
Anyone can help, thanks.

Dear kennethliukai,
Thank you for your interest in our work.
I just rerun the global notbook, but failed to reproduce the error. I believe the error you show is due to another error in the following line
!python GetCode.py --dataset_name $dataset_name --code_type 'w'

Would you mind rerun the notebook to see if you still meet the same error? If so, would you mind just running the line in above, to see if there is a error? If so, please inform us the log of error.
Best Wishes,
Alex


Update geofencing.yaml for release candidate 0.1.0-rc

What type of PR is this?

enhancement/feature

What this PR does / why we need it:
According to #112
Prepared release-candidate 0.1.0-rc, including some corrections
Which issue(s) this PR fixes:
Special notes for reviewers:
Changelog input
- Changed version to v0.1.0-rc

Additional documentation

Hi @akoshunyadi, please take a look into the conflicts, due to the other PR https://github.com/camaraproject/DeviceLocation/pull/115 being recently merged

We can also adjust some misalignments regarding Errors:

Generic400: Change description and message in example to: "Invalid argument"
Generic401: Change description and message in example to: "Unauthenticated"
Generic403: Change description to "Permission denied"

as in https://github.com/camaraproject/DeviceLocation/pull/104/files#diff-4d5f8ffcf7c3ed5fd9dcf63999a1413cba4fee213f2ae8dbf67efc460427a1ccR370-R395

Since multiple examples are not possible in Schema Object prior OAS 3.1.0 I propose to modify Source component definition as follows:
Source:
      type: string
      format: uri-reference
      minLength: 1
      description: |
        Identifies the context in which an event happened - be a non-empty `URI-reference` like:
        - URI with a DNS authority:
          * https://github.com/cloudevents
          *<EMAIL_ADDRESS>        - Universally-unique URN with a UUID:
          * urn:uuid:6e8bc430-9c3a-11d9-9669-0800200c9a66
        - Application-specific identifier:
          * /cloudevents/spec/pull/123
          * 1-555-123-4567
      example: "https://notificationSendServer12.supertelco.com"

@akoshunyadi ,  @rartych , please tale a look to the new Device model approved by QoD: https://github.com/camaraproject/DeviceLocation/issues/117
I have already adjusted location-verification.yaml

Thanks @akoshunyadi
2 smalls comments:

I understood you used same description for datetime but are we sure it's not better to have explicit description for startsAt & expiresAt attribute ? Not a blocker for me but @JoachimDahlgren  point was to have explicit description.
This description must have following sentence also: It must follow [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339#section-5.6) and must have time zone. Recommended format is yyyy-MM-dd'T'HH:mm:ss.SSSZ (i.e. which allows 2023-07-03T14:27:08.312+02:00 or 2023-07-03T12:27:08.312Z) in order to be aligned with the guideline (https://github.com/camaraproject/Commonalities/blob/main/documentation/API-design-guidelines.md#115-data-definitions)

@bigludo7 sure, I can change that, I think also other date-time fields are affected.


exceptions: Add new error class to be used for invalid parameter values.

This would help us in avoiding adding translation everytime we use this error for a new pair of parameters.

Self-review checklist

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

Communicate decisions, questions, and potential concerns.

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

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

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

Completed manual review and testing of the following:

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

Merged, thanks @sahil839! I'd intended to click the merge button yesterday.


Update flappy_main.py

thanks for fixing my username bruh

thanks for fixing my username bruh

:wesh:


Add z and ^w related keys

These are the keys that I use really often:
zz, zt, zb, <c-w>c
So I add them here.

Come check this @chakrit .

@off99555 thanks!


[DOCS] Analytics and Scripts

How can the documentation be improved?
I want to add analytics without using Partytown. It's unclear to me how to do this.
For Vue and React, I'd usually edit the index.html file and install my own scripts in the  tag like this: https://stackoverflow.com/a/56185465/12713117
But I can't find an index.html in Qwik. The examples seem to assume I'm going to use Partytown and that 3rd party analytics will be shoved into a service worker. Although I do approve of this as a general idea, there should be an obvious way to get analytics working without Partytown.
My specific use-case is evaluating Qwik with an apples-to-apples comparison to our Vue website. To do that, I need to ensure things like Analytics are loaded similarly, and since our analytics are loaded in the  tag with defer, that means I need to put our analytics into the  tag in Qwik.

To add html tags to the <head>, <body> or <html>, you can add any html tag in src/root.tsx in <head>, <body> or <QwikCity>.
(Adding to  <QwikCity> is not recommended, as it leads to technically not valid html)
E. g. :
export default component$(() => {
  return (
    <QwikCity>
      <head>
        <meta charSet="utf-8" />
        <RouterHead />
+       <script type="application/javascript" src="some-script.js" defer />
      </head>
      <body lang="en">
        <RouterOutlet />
        <ServiceWorkerRegister />
      </body>
    </QwikCity>
  );
});

Maybe I'm not understanding something simple, but adding a

I googled for how to deal with this in React without using index.html and found: https://vancelucas.com/blog/using-google-analytics-with-react/
But that uses dangerouslySetHTML, which I believe is not available in Qwik: https://github.com/BuilderIO/qwik/issues/1033

I've seen dangerouslySetInnerHTML in qwik:
https://github.com/BuilderIO/qwik/blob/c1e759eef1364984270e0eb1fbc6d0b443ef11ac/starters/apps/basic/src/components/router-head/router-head.tsx#L39

This works for me:
export default component$(() => {
  const analyticsScript = `
    window.dataLayer = window.dataLayer || [];
    function gtag() { window.dataLayer.push(arguments); }
    gtag('js', new Date());

    gtag('config', '');
    gtag('config', '');
  `;
  return (
    <QwikCity>
      <head>
        <meta charSet="utf-8" />
        <RouterHead />
        <script defer async dangerouslySetInnerHTML={analyticsScript}></script>
      </head>
      <body lang="en">
        <RouterOutlet />
        <ServiceWorkerRegister />
      </body>
    </QwikCity>
  );
});

I can see the scripts now, thanks @wtho - I'll do some testing to make sure the analytics scripts are working properly with Qwik, and if they seem to be working, then I'll try to do a docs PR too.

Hi @Gregory-Ledray 👋
Hope everything is up and running on your end 💪 just wanted to dbl check what the current state is and if you still would like to give a hand on creating a PR 👼

return (     <QwikCityProvider>       <head>         <meta charSet="utf-8" />         <link rel="manifest" href="/manifest.json" />         <QwikPartytown forward={['gtag','dataLayer.push']} />         <script           type="text/partytown"           dangerouslySetInnerHTML={
window.dataLayer = window.dataLayer || [];
window.gtag = function() {
dataLayer.push(arguments);
}
gtag('js', new Date());
gtag('config', 'G-XXXXXX'); // <-- CHANGE THIS
}         />         <script           async           type="text/partytown"           src="https://www.googletagmanager.com/gtag/js?id=G-XXXXXX"         />                 <RouterHead />       </head>       <body lang="en">         <RouterOutlet />         <ServiceWorkerRegister />       </body>     </QwikCityProvider>   );
Courtesy of @kerbelp on Builder.io discord. Worked for me after many hours of struggle <3


As an engineer on Cartographer, I want to easily be able to debug an issue in the field.

"I want to easily be able to debug an issue in the field."
Given Cartographer is deployed at a customer site
When Something really bad happens
Then I should be easily able to debug from the logs

Examples:
<Code snippets that illustrate the when/then blocks>
Notes:
Minimal info logging
More debug logging
We need a debug level and a way for customers to turn debug on (covered by #251)

@jwntrs can you add additional details to this issue?

There's probably more that needs to be done around this theme, so I broke out a separate issue to make sure we revisit our existing logging: https://github.com/vmware-tanzu/cartographer/issues/347


Unused Services Panorama.

Hi, I had been working on Panorama migrating rules from Juniper to palo alto, but now I´m having an issue with the number of services I can create, I reached the limit and now I don't know how to check how many services are unused, is there any option or script to check which services are unused to delete?
I have 2000 services and 5000 rules.
Thanks in advance..
A.J.

Quick questions :
1/ are you limited on the local firewall or is it Panorama that is not allowing you to create more than 2000 service objects ?
2/ Did you disable the option "Push unused objects to firewalls" in Panorama? (ignore if not relevant)

I'm limited by Panorama, and yes "Push unused objects to firewalls" is disable, I'm trying to find a way to check which services are unused to delete, something similar to panorama-unused-objects.php.

Ok, last question : can objects be used in local firewalls rules? ( firewall local rules using objects from Panorama). If yes then I have no script ready to run/stable. I didn't have time to make a proper and standard one.
If not then you guessed right : panorama-unused-objects.php can be adapted ( 5 lines to be changed at first look ) to spot unused services instead of unused Address objects.

Sorry, I was wrong, I'm limited by the local firewall, in Panorama I have more than 2000 services but in palo alto I can use only 2000, I'm checking again and I'm trying to find the number of unused services in the local firewall.

Ok, so in first instance you said that you disabled option ""Push unused objects to firewalls"" , can you double confirm ?
If it's already disabled then unfortunately it means that your firewall is using all these groups and you can do nothing (simple) about it but to delete/explode some. You could use my library to check for groups with little use (referenced in less than 2/3 rules) and 'explode' them : use their members instead of the group itself in the rules.
If it's not disabled then please disable it and retry to push config , it's made for that purpose.

It is disable, I'll try to check groups with litlle use as you said...
Thanks.

You should modify the example where-used script to just print the number of references or print a special message when they are < 3 and then see where it leads you.
object->countReferences() is the way to know how many times this object is used.

I made a script called 'service-edit.php' that you could eventually use to spot groups you are looking for.
just get latest version.
cheers

I'll try it now !
Thank you !


How to configure proxy for SQS in Spring Cloud AWS 3

Discussed in https://github.com/awspring/spring-cloud-aws/discussions/1027

Originally posted by ghughal January 22, 2024
With 2.4.x version, we were using ClientConfiguration to configure proxy (and other properties like max retry, max connection etc.) here is a sample below:
import com.amazonaws.ClientConfiguration;
import com.amazonaws.auth.profile.ProfileCredentialsProvider;
import com.amazonaws.services.sqs.AmazonSQSAsync;
import org.springframework.beans.factory.annotation.Value;
import com.amazonaws.services.sqs.AmazonSQSAsyncClientBuilder;

public class SqsConfig {

    @Value("${cloud.aws.client.proxy-host}")
    public String proxyHost;

    @Value("${cloud.aws.client.proxy-port}")
    public String proxyPort;

    @Value("${cloud.aws.client.non-proxy-hosts}")
    public String nonProxyHost;

    // Value is populated by the region code in the cloud environment.
    @Value("${cloud.aws.region.static}")
    public String region;

    public ClientConfiguration clientConfiguration() {
      final ClientConfiguration config = new ClientConfiguration();
      config.setProxyHost(proxyHost);
      config.setProxyPort(Integer.parseInt(proxyPort));
      config.setNonProxyHosts(nonProxyHost);
      return config;
    }

    public AmazonSQSAsync localamazonSqsAsync() {
          String awsProfileName = "adfs";
          return AmazonSQSAsyncClientBuilder
            .standard()
            .withRegion(region)
            .withCredentials(new ProfileCredentialsProvider(awsProfileName))
            .withClientConfiguration(clientConfiguration())
            .build();
      }

}

but it's not clear how to do that programmatically with 3.1.x version and it was not clear from documentation. Thank you.
Here is what I have for the migration to 3.1.x.
import com.amazonaws.ClientConfiguration;
import software.amazon.awssdk.auth.credentials.ProfileCredentialsProvider;
import software.amazon.awssdk.regions.Region;
import software.amazon.awssdk.services.sqs.SqsAsyncClient;

public class SqsConfig {

    @Value("${cloud.aws.client.proxy-host}")
    public String proxyHost;

    @Value("${cloud.aws.client.proxy-port}")
    public String proxyPort;

    @Value("${cloud.aws.client.non-proxy-hosts}")
    public String nonProxyHost;

    // Value is populated by the region code in the cloud environment.
    @Value("${cloud.aws.region.static}")
    public String region;

    public ClientConfiguration clientConfiguration() {
      final ClientConfiguration config = new ClientConfiguration();
      config.setProxyHost(proxyHost);
      config.setProxyPort(Integer.parseInt(proxyPort));
      config.setNonProxyHosts(nonProxyHost);
      return config;
    }

    public SqsAsyncClient localamazonSqsAsync() {
      String awsProfileName = "adfs";
      return SqsAsyncClient.builder()
          .region(Region.of(region))
          .credentialsProvider(ProfileCredentialsProvider.create(awsProfileName))
          // .asyncConfiguration(clientConfiguration())  -- tried using asyncConfiguration but this does not take the client configuration
          .build();
    }

Any information on how to incorporate the clientConfiguration?

Hmm, not sure about this one, @maciejwalkowiak @MatejNedic do you have any ideas?

@tomazfernandes will take a look

Having battled this issue for a while, this is what worked for me:
`
@Bean
AwsClientCustomizer sqsAsyncClientBuilderAwsClientConfigurer() {
LOG.info("Creating sqs async client config with proxy: " + proxyHost);
return new SqsAsyncAwsClientClientConfigurer(proxyHost, proxyPort);
}
static class SqsAsyncAwsClientClientConfigurer implements AwsClientCustomizer<SqsAsyncClientBuilder> {
    private String proxyHost;
    private int proxyPort;

    public SqsAsyncAwsClientClientConfigurer(final String proxyHost, final int proxyPort) {
        this.proxyHost = proxyHost;
        this.proxyPort = proxyPort;
    }

    @Override
    public SdkAsyncHttpClient asyncHttpClient() {
        return NettyNioAsyncHttpClient.builder().proxyConfiguration(ProxyConfiguration.builder()
                        .host(proxyHost).port(proxyPort).build())
                .build();
    }
}

`

This is workable for our needs. So closing this out on my end


[fix] bump current version of adapter-node on npm

Before submitting the PR, please make sure you do the following

[x] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[x] This message body should clearly illustrate what problems it solves.
[ ] Ideally, include a test that fails without this PR but passes with it.

Tests

[x] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[x] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpx changeset and following the prompts. All changesets should be patch until SvelteKit 1.0

Fixes #2239 by bumping the current version of adapter-node on npm.

thanks. closing in favor of https://github.com/sveltejs/kit/pull/2244


New update of ion does not work for ion-app-web

Your environment.

Version: d1ca70f5839b0397fa4af790491e982d410013ad
Browser: Chrome Version 87.0.4280.88
Other Information - stacktraces, related issues, suggestions how to fix, links for us to have context

I could confirm from new commit in ion caused the issue. Seems ion-app-web is not adapted to new update in ion project.
What did you do?
1-  In ion start with  docker-compose -f docker-compose.stable.yml up -d
2- In ion-app-web I used npm start
What did you expect?
Websocket should be established.
What happened?
The websocket got error ion-conference.3f7ba6d81ab829d1566a.js:113134 WebSocket connection to 'wss://localhost:8080/ws?peer=9c5febc2-6df8-4a5b-817c-aa6aa11cbc75' failed: Error during WebSocket handshake: Sent non-empty 'Sec-WebSocket-Protocol' header but no response was received W3CWebSocket @ ion-conference.3f7ba6d81ab829d1566a.js:113134

@cgojin any ideas?

FYI: I did try with new release of ion-sdk-js and it works well with new stable version of ion docker-compose. This project is using old version of  ion-sdk-js, so it should be the cause of this issue.

got it. would you mind proposing a pr to update it?

Sure! I will prepare a pull request as soon as possible.

Sorry, I'm busy refactoring the ion ISLB recently, and I haven't extended ion-siganl yet. If someone does it, that's good.


When i debagging on window platform getting this issue, the problem navigating to firbase_cpp_sdk

Launching lib\main.dart on Windows in debug mode...
Building Windows application...
CMake Error at flutter/ephemeral/.plugin_symlinks/firebase_core/windows/CMakeLists.txt:12 (message):
Firebase C++ SDK not found in C:/firebase_cpp_sdk
Error: Unable to generate build files
How can solve this issue?

Seems like a problem with the flutterfire scripts and not firebase-cpp-sdk itself.


XBee connection issues

I am using this library to connect and transfer data between two xbees. Writes to the serialport works such that another xbee receives the correct data. As soon the other xbee sends data, then all the future send fails from the serialport library.Your help will be much appreciated.
In terms of a timeline:
XBee-A -> "hi" > XBee-B : Good
XBee-A -> "how" > XBee-B : Good
XBee-A -> "are" > XBee-B : Good
XBee-A -> "you" > XBee-B : Good
XBee-B -> "good" -> XBee-A: Good
XBee-A -> "nice!" -> XBee-B: Failed

XBee-A using serialport library

I have two xbees: one is set to coordinator API 2 and the other is router API 2. The nodejs application is connected to the coordinator. The router is connected to a pic and controlled with xctu next gen application.
var util = require('util');
var SerialPort = require('serialport').SerialPort;
var xbee_api = require('xbee-api');

var C = xbee_api.constants;

var xbeeAPI = new xbee_api.XBeeAPI({
    api_mode: 1
});

var serialport = new SerialPort("/dev/ttyAMA0", {
    baudrate: 9600,
    parser: xbeeAPI.rawParser()
});

serialport.on("open", function () {
    var frame_obj = {
        type: 0x10,
        id: 0x01,
        destination64: "0013A200407A25A7",
        broadcastRadius: 0x00,
        options: 0x00,
        data: "Hello world"
    };

    serialport.write(xbeeAPI.buildFrame(frame_obj));
    console.log('Sent to serial port.');

   setTimeout(function() {
         // this doesn't work if the receiving xbee sends back something
          serialport.write(xbeeAPI.buildFrame(frame_obj));
  },  5000):
});

serialport.on('data', function (data) {
    console.log('data received: ' + data);
});

// All frames parsed by the XBee will be emitted here
xbeeAPI.on("frame_object", function (frame) {
    console.log(">>", frame);
});

// note: there are no errors coming from ' error' event

I just wanted to add that the xbee does receive the  message the router xbee sends back. To help debug the error,  I placed numerous print statements in 'serialport.js` and I noticed that when I send the data the first time, the following function is called however the subsequent times, it fails to reach this line: https://github.com/voodootikigod/node-serialport/blob/master/serialport.js#L231


All rows are active after selecting row programmatically  (table with groupping)

I'm submitting a ... (check one with "x")
[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, post on Stackoverflow or Gitter

Current behavior
All rows are active instead of one specific (when specific row is selected programmatically).
Expected behavior
Only selected row is active.
Reproduction of the problem
I chose row programmatically in AfterViewInit lifehook (that's just my test solution). Instead of activating one row, all rows are active (there is class active for every datatable-body-row DOM element).
Example:
https://stackblitz.com/edit/angular-ngx-datatable-row-grouping-and-row-detail-7q3fwc?file=src/app/app.component.ts
What is the motivation / use case for changing the behavior?
I want to add styling class for selected row. When I select row datatable-body-row is set with class active . So I can use this class to stylish selected row. But now it's not possible because all datatable-body-row are set with class active.

macOS Big Sur (11.0.1), WebStorm, npm.

Table version:
19.0.0 (bug reproduced for this table version)
14.0.0 (there is no such a bug on this table version)

Angular version:
Tested on version 6.1.7 (bug is reproduced).
Tested on version 12.1.3 (bug is reproduced as well).

Browser: all

Language:
TypeScript 2.7.2
TypeScript 4.3.5 (tested as well)

I'm facing this issue as well with the latest version of ngx-datatable and angular.
is there any plans to fix it?

I'm facing this issue.
ngx-datatable: 20.0.0
angular: 13.3.0


HamburgerMenu Background property gets overwritten on Accent Color change

Hi,
If I set <HamburgerMenu HamburgerBackground="{x:Null}" the property is overwritten with "CustomColor" when the accent color in Windows changes.
This, in my setup happens every 15 minutes due to rotating wallpapers and accent color generated from said wallpaper.
I am using the latest GIT code (Not NuGet package)

Yes. This is true.

You can set it directly in the HamMenu tag. Just not using a style.

I will eventually fix this. Just not sure how yet. Suggestions?

I'll look into it and explore some ideas. If I come up with anything I'll post them here.

Thanks


Small cleanup

- What I did
I've cleaned up a bunch of packages found under pkg.
- How I did it
I've made the following changes:

removed comparisons to bool in if conditions
switched to bytes.Equal where that made sense
removed for loops where arrays could be appended
made the code return directly where the returned value was the error return by the called function
- How to verify it

- Description for the changelog
pkg: clean up a few small issues

tests are failing, @unclejack (also see @AkihiroSuda's comment)

Interesting;
13:41:38 ok  	github.com/docker/docker/pkg/idtools	0.015s	coverage: 17.5% of statements
13:41:40 --- FAIL: TestAtomicWriteToFile (0.00s)
13:41:40 	fswriters_test.go:41: Data mismatch, expected "barbaz", got "barbaz"
13:41:40 --- FAIL: TestAtomicWriteSetCommit (0.00s)
13:41:40 	fswriters_test.go:89: Data mismatch, expected "barbaz", got "barbaz"
13:41:40 FAIL
13:41:40 coverage: 69.5% of statements

Everything should be OK now. PTAL

LGTM


Deleting bot chat conversation

Hi,
Is it possible to delete bot 1-1 / personal conversation with user using bot state API
If yes then the URL endpoint  DELETE /v3/botstate/{channelId}/users/{userId}
returns a 404 for channel id = msteams and userid = OUR_USER_ID
And yes i have seen this, just wanted to confirm.
Thanks

@register9091 - The Bot State APIs are used to store and retrieve state data and not the chat thread/conversation. Currently, there is only Create Chat Thread api available in beta version.

@Wajeed-msft is there any alternate way to delete the conversations? Or say keep it in memory only for the current session? Maybe a url flag?
We need this for testing purposes.

The conversation itself cannot be deleted: once a conversation is established between a user and a bot the same "thread" will be used each time. However, if you're referring to the bot state you're storing against the conversation, you can use an in-memory store. See examples Node and C#.
BTW the BotState API you're using above is deprecated, and may be turned off at some point, so I recommend explicitly setting your bot storage.

@aosolis yeah the bot state API does not seem to work. We want that the conversation the user is having with the bot is say stored only for the current session and when the user comes to chat with the bot the next time, he/she should have a clean slate to start with. We need it for our testers as its quite difficult for them to keep track of new elements with the previous messages and cards being already shown on the screen. So can we get some URL flag which can help in this scenario ?

Unfortunately what you're asking for is not supported. Right now there is no way to delete a conversation. The thread will always be there: there's no way to delete it or clear the messages inside it. Attempting to start a new conversation between the bot and a user will return the same conversation.
The closest you can probably get is to clear your bot's memory of the conversation by deleting all state associated with that conversation id in your bot's state store. In your testing environment you could implement a command like reset, that would delete all your state and send a banner message to the thread that says something like ----conversation reset here----, to hopefully make it clearer to your testers where the "new" conversation began.

Ok. Thanks 👍


Where to change the export CSV SQL ?

Make sure these boxes are checked before submitting your issue - thank you!

[x] I have checked the issue tracker for the same issue and I haven't found one similar

Superset version
0.20.4
Expected results
Any idea where I can override the SQL used to generate the CSV to add additional fields or change the fields from the SELECT section ?
Ideally I would just want to change the
SELECT x,y,z FROM mytable
Into
SELECT * FROM mytable
just for the CSV export
I already have a python code :
sql = "SELECT x, y, z FROM asd WHERE etc etc etc"
sql_arr = sql.split( 'FROM')
newsql = "SELECT * FROM "+sql_arr[1]
I just need to find where to change the SQL ( new to python and having difficulties with the superset architecture )

https://github.com/apache/incubator-superset/blob/eb0f3970cfdef64ca932ddd72f817a82075b35a2/superset/views/core.py#L2192

Hi vnmw,
Nopes it does not seem to be this location.
There is already a logging.info("Exporting CSV file [{}]... etc )
but its not being logged when I generated the CSV from a slice.
I tried the code anyway but no changes occured :
def csv(self, client_id):
"""Download the query results as csv."""
logging.info(blablablabla)
query_arr = Query.split('FROM')
Query = "SELECT * FROM "+query_arr[1]
query = (
db.session.query(Query)
blablablabla
( The indentation is not appearing in the wysiwyg but its present in the file )

Arf... Dunnot what I clicked but it closed by error.
incubator-superset/superset/views/core.py
def csv(self, client_id):
does not seem to be called when I click on export CSV
Its this button :

@XavierDeLapeyre
What are you trying to achieve?
The code you included:
sql = "SELECT x, y, z FROM asd WHERE etc etc etc"
sql_arr = sql.split( 'FROM')
newsql = "SELECT * FROM "+sql_arr[1]

...would be unstable for queries will multiple sub-selects, and so wouldn't be suitable for the standard export button.
If you just want a one-off export then I'd recommend using the SQL Lab functionality

@alanmcruickshank
My need is to change the content of the CSV file generated for the slices when the user clicks on the "Export CSV" button.
I need to find this location, I will do the necessary adjustments ( regarding sub-selects, group by, order by etc )
And the code provided is just an example. The sql queries generated in my case are pretty straight forward.
Ideally, I would want to create a new field within the edit slice view.
Add a text zone to enter my own sql CSV generate query
and when I click on generate CSV, it just overrides whatever SQL is has and uses the CSV query inputed.
But the quickest action for me right now is just to override the sql for the demo graphs I have in hand.

That specific button you're looking at calls this endpoint:
https://github.com/apache/incubator-superset/blob/eb0f3970cfdef64ca932ddd72f817a82075b35a2/superset/views/core.py#L997-L1000
it calls it with the csv parameter set to True so that it eventually calls:
https://github.com/apache/incubator-superset/blob/eb0f3970cfdef64ca932ddd72f817a82075b35a2/superset/views/core.py#L1015-L1020
If you ever need to find out things like this you can use the "Inspect" feature of most modern browsers by right clicking on something. That will then show you the HTML which represents that object and you'll see the link within it.

@alanmcruickshank thanks!


[Docs]: Add Geolocation

Is there an existing issue for this?

[X] I have searched the existing issues

Release Number or Date
NA
Documentation Link
https://docs.appsmith.com/reference/appsmith-framework/widget-actions
Discord/slack/intercom Link
No response
Describe the problem and improvement.
Add docs for all the actions related to Geolocation.

closed via https://github.com/appsmithorg/appsmith-docs/pull/1450

closed via https://github.com/appsmithorg/appsmith-docs/pull/1450

canBeRequested Boolean
This property indicates the feasibility of accessing the user's current location. Use this to check if the user has granted location permissions and gracefully handle failures. eg:
if(appsmith.geolocation.canBeRequested) {
    // access the user's location
    appsmith.geolocation.getCurrentPosition()
}
else {
  // ask user to grant location access
  showAlert("Please allow location access on the browser and refresh this page")
}

currentPosition object
This object contains additional properties that can help determine the user's current position.
refer: https://developer.mozilla.org/en-US/docs/Web/API/GeolocationCoordinates
https://developer.mozilla.org/en-US/docs/Web/API/GeolocationPosition

Docs are already available for the functions here:

geolocation.getCurrentPosition() - Get Geolocation
geolocation.watchPosition() - Watch Geolocation
geolocation.clearWatch() - Stop watching Geolocation

Closing this ticket.


Feature: Custom noResultsText / noChoicesText per element

It would be a nice touch in something I'm creating to be able to customise the verb based on some attribute of each item - for example 'No ingredients to choose from', 'No courses to choose from'.
I could loop through all selects and instantiate Choices manually, but I imagine this probably isn't super efficient.
I'm thinking perhaps allowing these two options to be functions which take the element as a parameter so we can build whatever string we require would be awesome.

This has been implemented as of version 2.7.1 👍


Incompatible (u)intptr_t type and PRIxPTR definitions

Describe the bug
For some platforms, the intptr_t and uintptr_t types do not match the PRIxPTR types.
To Reproduce
On an x86-64 host, build the following code for native_posix board using LLVM (ZEPHYR_TOOLCHAIN_VARIANT=llvm).
uintptr_t val = 1234;
printk("%" PRIuPTR "\n", val);

See the following error:
error: format specifies type 'unsigned int' but the argument has type 'uintptr_t' (aka 'unsigned long') [-Werror,-Wformat]

Expected behavior
The types of intptr_t and uintptr_t and the PRIxPTR match.
For instance:

If intptr_t is int, PRIdPTR should be %d.
If intptr_t is long, PRIdPTR should be %ld.

Impact
Makes PRIxPTR useless on the affected platforms (in particular, native_posix on x86-64 with Clang/LLVM).
Environment (please complete the following information):

OS: Ubuntu 20.04
Toolchain: Clang 10.0 (also tested on Clang 12 and the problem persists)
Commit SHA: feb0e9f766b1328b45666e5e71134c34ae17b742

Additional context
This happens because zephyr_stdint.h re-defines __INTPTR_TYPE__ and __UINTPTR_TYPE__  as long int and long unsigned int, respectively, while the PRIxPTR definitions stay %x with no size prefix.
https://github.com/zephyrproject-rtos/zephyr/blob/feb0e9f766b1328b45666e5e71134c34ae17b742/include/toolchain/zephyr_stdint.h#L47-L50
See https://github.com/zephyrproject-rtos/zephyr/pull/37712#discussion_r689578180.

TODO: Further investigate all the affected platforms and make a list of them.

cc @npitre @andyross @pfalcon @galak @nashif @carlescufi @mnkp @pabigot

LLVM is wrong. On a 64-bits platform, a pointer is wider than an unsigned int.
In lib/libc/minimal/include/inttypes.h we have:
#define PRIuPTR                 "lu"

What lib are you using?

LLVM is wrong. On a 64-bits platform, a pointer is wider than an unsigned int.

@npitre Building native_posix is with -m32, so pointer should be/is by default int.
For native_posix_64 (which builds with -m64), it will be long.

This might give better overview of the issue seen on native_posix with LLVM:
https://gist.github.com/stephanosio/01d70f08046dc979ff7c1de5aab9ea4e

Building native_posix is with -m32, so pointer should be/is by default int.
For native_posix_64 (which builds with -m64), it will be long.

A while ago, we had many problems like that. Commit f32330b22c33 fixed
most of them. Zephyr is a young hosting environment so it is in a position
to dictate its types and avoids such legacy shortcomings.
So int32_t is always an int, intptr_t is always a long, and PRIuPTR is
always "lu", for all supported architectures.
Now the native_posix target is a special cases as it runs inside another
environment. Still, the native_posix environment should be isolated as
much as possible so to preserve the Zephyr conventions for Zephyr specific
code.

The scope of this issue might be limited to the POSIX arch boards, but I somehow doubt that because we have other third-party toolchains like Arm Compiler and ARC MWDT with their own headers (by the way, cc @tejlmand).
I don't have time to do an in-depth analysis on this at the moment. I will revisit this later and do full analysis.

There is also problem of definitions like __UINTPTR_MAX__ that do not get override.

Now the native_posix target is a special cases as it runs inside another
environment. Still, the native_posix environment should be isolated as
much as possible so to preserve the Zephyr conventions for Zephyr specific
code.

I definitely second the sentiment that native_posix breaks a lot the fun. I had a lot of issues with it while working on POSIX subsys: https://github.com/zephyrproject-rtos/zephyr/issues/13054 . And I also eyeballed "radical" solutions like saying that POSIX subsys simply isn't supported on native_posix. Of course, I never went forward with that and exactly tried to "isolate" native_posix stuff from Zephyr's POSIX, but that was quite a swamp (and never finished). Of course, here it's much more focused matter, and maybe it will be possible to make it reach the sweet spot. But given concerns of supporting additional toolchain types raised above, maybe it would just make sense to (re)embrace the fact that these definitions belong to a toolchain, not Zephyr...
(Just thinking aloud really, my 2 cents.)

I think it really depends on how important the native_posix target is,
and how much it is worth affecting all other targets to accommodate it.
Having a coherent set of definitions for all (real) target is a big
plus.
And this particular issue is valid only for native_posix (the 32-bit
one). There are no such conflicts with native_posix_64.

TODO: Check how sane the type system is in armclang with both STDLIB and MICROLIB (cc @tejlmand).

For 2.7, we will leave the Arm Compiler and ARC MWDT out of question since they are very much experimental right now.
The scope of fix for 2.7 will be limited to the native_posix with Clang as identified in this issue.
In the future, we could look into reverting #16645:

#16645 should not have been necessary if we actually made use of the PRIx and SCNx definitions from inttypes.h in the code -- we have no reason not to since we are effectively on C99 and there is no point in supporting both ancient and highly obsolete C standards that predate C99.
Strange targets such as baremetal x86-32 that define INT32_TYPE as long int can be reworked to use int for INT32_TYPE, once we have the infrastructure to do that -- https://github.com/zephyrproject-rtos/sdk-ng/issues/350 will add Zephyr OS native targets for the GNU toolchains (i.e. aarch64-*-zephyr instead of aarch64-*-elf).


fix: _theme_variables file was not included in deploy

Proposed changes
file renamed to scss.

[x] Bug fix (non-breaking change which fixes an issue).
[ ] New feature (non-breaking change which adds functionality).
[ ] Breaking change (fix or feature that would cause existing functionality to change).

Checklist:

[x] I have read the CONTRIBUTING document.
[x] My commit messages follows the conventional commit format
[ ] My change requires a change to the documentation, and updated it accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

LGTM! Thanks for the fix :)
Sorry I am currently moving and have less time atm :) But it should be better soon ;)

Good luck with the moving... and congratulations with the new web, it looks great!