Add option to star on GitHub

Put in settings after table refactor

What do you have in mind for this? Open repo URL in Safari and ask the user to start it or Use GitHub starring API?
Sent with GitHawk

I'd personally much prefer to use the API

https://developer.github.com/v4/reference/mutation/addstar/
There's also the V4 API we could use -- probably simpler to use V3 though and since we don't have any preference 🤷♂

Need some help on brainstorming for the UI part. Quickly created something in the storyboard.

Cell under "View Source Code" to star on GitHub
Cell has "Star on Github" and total stars
On Click, Call v3 API to add star
If the user already added star ??

Like the idea of having the total stars, maybe the button text just changes to "Unstar" or something to give the user the ability to revert the action?

"Unstar" option would be great! Let me knock this down
Sent with GitHawk

Unrelated, but I feel like we should really explain the options in Settings better. "Read on Open"? "Badge Unread"? I feel these are all but obvious.

@BasThomas suggestions?

@rizwankce @Sherlouk what about making the cell dynamic in that if you've starred the repo then it disappears? That'd obvi make this page much more complicated, but would serve its purpose.
Also, IMO this is pretty low pri vs other stuff (maybe we should have priority labels? or really start using the projects tool).

@rnystrom Agree with the priority. I just filtered issues by Bugs/Feature and started looking into it. Definitely, I can check Projects and take some high pri issues.


test_python_implementation test26 & test27 fail for Python 3 / mpi4py 3.0.0

When running the unit tests, test26 and test27 in amuse/test/suite/codes_tests/test_python_implementation fails.
This is for Python 3.6 (possibly Python 2 as well) and mpi4py 3.0.0 (most recent version).
Running this as
mpiexec /usr/local/bin/python3.6 -m nose /usr/local/lib/python3.6/site-packages/amuse/test/suite/codes_tests/test_python_implementation.py -m 'test2[67]'

The full traceback is listed at the end.
This is on MacOSX 10.13.5, Homebrew Python 3.6, Homebrew mpich (compiled with Homebrew gcc-8), mpi4py 3.0.0.
mpi4py version 1 and 2 do not show an error.

(Separated the two tests, because nose intertwines some of the output. The errors are not identical, but possibly related.)
Traceback for test26:
mpiexec /usr/local/bin/python3.6 -m nose /usr/local/lib/python3.6/site-packages/amuse/test/suite/codes_tests/test_python_implementation.py -m 'test26'
E
======================================================================
ERROR: test26 (amuse.test.suite.codes_tests.test_python_implementation.TestInterface)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/amuse/test/suite/codes_tests/test_python_implementation.py", line 886, in test26
    portname, error = instance1.internal__open_port()
  File "/usr/local/lib/python3.6/site-packages/amuse/rfi/core.py", line 115, in __call__
    raise exceptions.CodeException("Exception when calling function '{0}', of code '{1}', exception was '{2}'".format(self.specification.name, type(self.interface).__name__, ex))
amuse.support.exceptions.CodeException: Exception when calling function 'internal__open_port', of code 'ForTestingInterface', exception was 'Error in code: Argument 'info' has incorrect type (expected mpi4py.MPI.Info, got NoneType)'
-------------------- >> begin captured logging << --------------------
amuse.rfi.channel: DEBUG: got 1 strings of size [75]
amuse.rfi.channel: DEBUG: got 1 strings of size [75], data = ["Argument 'info' has incorrect type (expected mpi4py.MPI.Info, got NoneType)"]
amuse.rfi.channel: INFO: error message!
--------------------- >> end captured logging << ---------------------

----------------------------------------------------------------------
Ran 1 test in 0.585s

FAILED (errors=1)

Traceback for test27:
mpiexec /usr/local/bin/python3.6 -m nose /usr/local/lib/python3.6/site-packages/amuse/test/suite/codes_tests/test_python_implementation.py -m 'test27'
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/amuse/rfi/python_code.py", line 182, in handle_message
    result = method(**keyword_arguments)
TypeError: internal__open_port() got an unexpected keyword argument 'port_identifier'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/amuse/rfi/python_code.py", line 81, in start
    self.handle_message(message, result_message)
  File "/usr/local/lib/python3.6/site-packages/amuse/rfi/python_code.py", line 186, in handle_message
    result = method(*list(keyword_arguments))
  File "/usr/local/lib/python3.6/site-packages/amuse/rfi/python_code.py", line 313, in internal__open_port
    outportname.value = MPI.Open_port(None)
TypeError: Argument 'info' has incorrect type (expected mpi4py.MPI.Info, got NoneType)
Argument 'info' has incorrect type (expected mpi4py.MPI.Info, got NoneType)
E
======================================================================
ERROR: test27 (amuse.test.suite.codes_tests.test_python_implementation.TestInterface)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/amuse/test/suite/codes_tests/test_python_implementation.py", line 912, in test27
    portname, error = instance2.internal__open_port()
  File "/usr/local/lib/python3.6/site-packages/amuse/rfi/core.py", line 115, in __call__
    raise exceptions.CodeException("Exception when calling function '{0}', of code '{1}', exception was '{2}'".format(self.specification.name, type(self.interface).__name__, ex))
amuse.support.exceptions.CodeException: Exception when calling function 'internal__open_port', of code 'ForTestingInterface', exception was 'Error in code: Argument 'info' has incorrect type (expected mpi4py.MPI.Info, got NoneType)'
-------------------- >> begin captured stdout << ---------------------
<class 'amuse.test.suite.codes_tests.test_python_implementation.ForTestingInterface'>

--------------------- >> end captured stdout << ----------------------
-------------------- >> begin captured logging << --------------------
amuse.rfi.channel: DEBUG: got 1 strings of size [75]
amuse.rfi.channel: DEBUG: got 1 strings of size [75], data = ["Argument 'info' has incorrect type (expected mpi4py.MPI.Info, got NoneType)"]
amuse.rfi.channel: INFO: error message!
--------------------- >> end captured logging << ---------------------

----------------------------------------------------------------------
Ran 1 test in 0.523s

FAILED (errors=1)

Below are the errors I get with Python 2 & mpi4py 3.0.0.
This time, test 27 does not show the unexpected keyword argument 'port_identifier' error, but I don't know enough about the code and MPI to know how relevant that is.

test26
$ mpiexec python2.7 -m nose /usr/local/lib/python2.7/site-packages/amuse/test/suite/codes_tests/test_python_implementation.py -m test26
E
======================================================================
ERROR: test26 (amuse.test.suite.codes_tests.test_python_implementation.TestInterface)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/site-packages/amuse/test/suite/codes_tests/test_python_implementation.py", line 886, in test26
    portname, error = instance1.internal__open_port()
  File "/usr/local/lib/python2.7/site-packages/amuse/rfi/core.py", line 115, in __call__
    raise exceptions.CodeException("Exception when calling function '{0}', of code '{1}', exception was '{2}'".format(self.specification.name, type(self.interface).__name__, ex))
CodeException: Exception when calling function 'internal__open_port', of code 'ForTestingInterface', exception was 'Error in code: Argument 'info' has incorrect type (expected mpi4py.MPI.Info, got NoneType)'
-------------------- >> begin captured logging << --------------------
amuse.rfi.channel: DEBUG: got 1 strings of size [75]
amuse.rfi.channel: DEBUG: got 1 strings of size [75], data = [u"Argument 'info' has incorrect type (expected mpi4py.MPI.Info, got NoneType)"]
amuse.rfi.channel: INFO: error message!
--------------------- >> end captured logging << ---------------------

----------------------------------------------------------------------
Ran 1 test in 0.554s

FAILED (errors=1)

test27
$ mpiexec python2.7 -m nose /usr/local/lib/python2.7/site-packages/amuse/test/suite/codes_tests/test_python_implementation.py -m test27
Argument 'info' has incorrect type (expected mpi4py.MPI.Info, got NoneType)
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/site-packages/amuse/rfi/python_code.py", line 81, in start
    self.handle_message(message, result_message)
  File "/usr/local/lib/python2.7/site-packages/amuse/rfi/python_code.py", line 185, in handle_message
    result = method(*list(keyword_arguments))
  File "/usr/local/lib/python2.7/site-packages/amuse/rfi/python_code.py", line 312, in internal__open_port
    outportname.value = MPI.Open_port(None)
TypeError: Argument 'info' has incorrect type (expected mpi4py.MPI.Info, got NoneType)
E
======================================================================
ERROR: test27 (amuse.test.suite.codes_tests.test_python_implementation.TestInterface)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/site-packages/amuse/test/suite/codes_tests/test_python_implementation.py", line 912, in test27
    portname, error = instance2.internal__open_port()
  File "/usr/local/lib/python2.7/site-packages/amuse/rfi/core.py", line 115, in __call__
    raise exceptions.CodeException("Exception when calling function '{0}', of code '{1}', exception was '{2}'".format(self.specification.name, type(self.interface).__name__, ex))
CodeException: Exception when calling function 'internal__open_port', of code 'ForTestingInterface', exception was 'Error in code: Argument 'info' has incorrect type (expected mpi4py.MPI.Info, got NoneType)'
-------------------- >> begin captured stdout << ---------------------
<class 'amuse.test.suite.codes_tests.test_python_implementation.ForTestingInterface'>

--------------------- >> end captured stdout << ----------------------
-------------------- >> begin captured logging << --------------------
amuse.rfi.channel: DEBUG: got 1 strings of size [75]
amuse.rfi.channel: DEBUG: got 1 strings of size [75], data = [u"Argument 'info' has incorrect type (expected mpi4py.MPI.Info, got NoneType)"]
amuse.rfi.channel: INFO: error message!
--------------------- >> end captured logging << ---------------------

----------------------------------------------------------------------
Ran 1 test in 0.497s

FAILED (errors=1)

this is not python 3 specfic...

works here


Set default retry_max_delay to one minute

Related to #369

Unsure why this is done, this changes the default values for folks that have been using kazoo without much reason. I mean I get the change, but it seems bad to change this on folks, its already configurable so just provide the value that you desire when creating a client.


Add README.md

Default readme updated with project specific details.

@mandyreal in the main body/description of the PR please put "Resolves #ISSUENUMBER"

@mandyreal ignore the old readme, that's rails. Pay attention to the NEW ISSUE.

@mandyreal Any progress? I'd like this to be done by our next checkin and if you can't do it, I'm sure somebody else would be willing to snag this issue.

@pachonk yes please feel free to take over or re-assign to other members. thanks.


pane and tab state refactor

partially address Coding/WebIDE#57, 2 big blocker, tab and pane's states have been reimplemented. left is the that of filetree and panel, will come back to them soon.


Crash on -[FPRRemoteConfigFlags cachedValueForConfigFlag:]

[READ] Step 1: Are you in the right place?
Crash
[REQUIRED] Step 2: Describe your environment

Xcode version:  Xcode 11.2.1
Firebase SDK version:  6.13.0
Firebase Component:  Core
Component version: 6.13.0

[REQUIRED] Step 3: Describe the problem
We upgrade to lateast SDK version 6.13.0, Crashed on [FPRRemoteConfigFlags cachedValueForConfigFlag:]
Steps to reproduce:
It's crashed on com.hackemist.SDWebImageDownloader thread, but we do not use SDWebImage with FireBase.
Here is the Crash Info:
#0Crashed: com.hackemist.SDWebImageDownloader (QOS: UNSPECIFIED)EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x0000000d80f10780 Raw Text
--
0 | libobjc.A.dylib | objc_msgSend + 16
1 | ** | -[FPRRemoteConfigFlags cachedValueForConfigFlag:] +<PHONE_NUMBER>
2 | ** | -[FPRRemoteConfigFlags getStringValueForFlag:defaultValue:] +<PHONE_NUMBER>
3 | ** | -[FPRRemoteConfigFlags sdkDisabledVersionsWithDefaultValue:] +<PHONE_NUMBER>
4 | ** | -[FPRConfigurations sdkDisabledVersions] +<PHONE_NUMBER>
5 | ** | -[FPRConfigurations sdkEnabled] +<PHONE_NUMBER>
6 | ** | -[FPRNetworkTrace initWithURLRequest:] +<PHONE_NUMBER>
7 | ** | __InstrumentDataTaskWithRequestCompletionHandler_block_invoke +<PHONE_NUMBER>
8 | SDWebImage | SDWebImageDownloaderOperation.m line 162-[SDWebImageDownloaderOperation start] + 162
9 | Foundation | __NSOQSchedule_f + 276
17 | libsystem_pthread.dylib | start_wqthread + 4

@dongshuju Thanks for the report. The reason why you are seeing SDWebImage as a part of the request is because Firebase Performance tries to measure the performance of all the network requests that happen.
With regards to the crash, we will take a look at it and rollout a fix for this very soon.
Are there any specific pattern you see in the crashes? (Eg. OS Version, Application state)

@dongshuju In order to capture performance information of the network requests Firebase Performance needs to swizzle some object (e.g. NSURLSession). In your case the crash happens while a NSURLRequest created by SDWebImageDownloader is instrumented.
As a workaround you may temporary disable features of Firebase Performance requiring swizzling while investigating and fixing the issue by setting Performance.isInstrumentationEnabled to false before calling FirebaseApp.configure():
Performance. sharedInstance().isInstrumentationEnabled = false
FirebaseApp.configure()

@dongshuju Can you share the complete stack trace for this crash? I'm guessing a possible race condition triggering this issue and I would like to make sure we have other parts of the stack trace available for us to ascertain and look at this issue.

@visumickey  recently we included this SDK in-app and getting the same crash. Here some more information
Crashed: com.google.perf.FPREventsQueue
0  libobjc.A.dylib                0x1e7422f70 objc_msgSend + 16
1  Namshi                         0x101174238 -[FPRRemoteConfigFlags cachedValueForConfigFlag:] +<PHONE_NUMBER>
2  Namshi                         0x10117448c -[FPRRemoteConfigFlags getStringValueForFlag:defaultValue:] +<PHONE_NUMBER>
3  Namshi                         0x101174738 -[FPRRemoteConfigFlags sdkDisabledVersionsWithDefaultValue:] +<PHONE_NUMBER>
4  Namshi                         0x101172a64 -[FPRConfigurations sdkDisabledVersions] +<PHONE_NUMBER>
5  Namshi                         0x101172974 -[FPRConfigurations sdkEnabled] +<PHONE_NUMBER>
6  Namshi                         0x101177130 -[FPRClient processAndLogEvent:] +<PHONE_NUMBER>
7  Namshi                         0x101176a34 __22-[FPRClient logTrace:]_block_invoke +<PHONE_NUMBER>
8  libdispatch.dylib              0x1e7c13b9c _dispatch_call_block_and_release + 32
9  libdispatch.dylib              0x1e7c15134 _dispatch_client_callout + 20
10 libdispatch.dylib              0x1e7c1c78c _dispatch_lane_serial_drain + 872
11 libdispatch.dylib              0x1e7c1d194 _dispatch_lane_invoke + 368
12 libdispatch.dylib              0x1e7c25480 _dispatch_workloop_worker_thread + 588
13 libsystem_pthread.dylib        0x1e7e16b20 _pthread_wqthread + 316
14 libsystem_pthread.dylib        0x1e7e1cdd4 start_wqthread + 4

Xcode version: Xcode 11.2.1
Firebase SDK version: 6.13.0
Firebase Component: Core
Component version: 6.13.0

iOS 11.0.1
iOS 12.x

@visumickey I getting the same crash. Here some more information
Crashed: com.google.perf.FPREventsQueue
0 libobjc.A.dylib objc_object::release() + 16
1 MyApp -[FPRRemoteConfigFlags cachedValueForConfigFlag:] +<PHONE_NUMBER>
2 MyApp -[FPRRemoteConfigFlags getBoolValueForFlag:defaultValue:] +<PHONE_NUMBER>
3 MyApp -[FPRConfigurations sdkEnabled] +<PHONE_NUMBER>
4 MyApp -[FPRClient processAndLogEvent:] +<PHONE_NUMBER>
5 MyApp __22-[FPRClient logTrace:]_block_invoke +<PHONE_NUMBER>
6 libdispatch.dylib _dispatch_call_block_and_release + 24
7 libdispatch.dylib _dispatch_client_callout + 16
8 libdispatch.dylib _dispatch_queue_serial_drain$VARIANT$armv81 + 904
9 libdispatch.dylib _dispatch_queue_invoke$VARIANT$armv81 + 328
10 libdispatch.dylib _dispatch_root_queue_drain_deferred_wlh$VARIANT$armv81 + 332
11 libdispatch.dylib _dispatch_workloop_worker_thread$VARIANT$armv81 + 612
12 libsystem_pthread.dylib _pthread_wqthread + 860
13 libsystem_pthread.dylib start_wqthread + 4

Xcode version: Xcode 11.3
Firebase SDK version: 6.14.0
Firebase Component: Core
Component version: 6.14.0

iOS 11.4.1

@Vitalik13 @BaluNaik Can you share all the threads that were active during the time of crash? We are guessing a probable race condition in fetching a cached value that is leading to this crash.

This is all scheduled for a rollout early next week.


Update raycast-gemini extension

Description

Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Hi 👋
Thanks for your contribution 🔥
Do you want to check this, @EvanZhouDev

@d0zingcat Looks pretty good, just a few minor touchups here and there! Also, not too sure if you can reproduce, but when generating text with Gemini 2.0 Flash (but perhaps also the other models), there appears to be a bit of lag when streaming. The streaming seems to override some existing text occasionally. I realize that there is nothing changed in your code that can directly cause this, but please let me know if you also have this issue.

@d0zingcat Looks pretty good, just a few minor touchups here and there! Also, not too sure if you can reproduce, but when generating text with Gemini 2.0 Flash (but perhaps also the other models), there appears to be a bit of lag when streaming. The streaming seems to override some existing text occasionally. I realize that there is nothing changed in your code that can directly cause this, but please let me know if you also have this issue.

Yes, I can reproduce this issue on both Gemini Flash 1.5 and 2.0, but I have no clue how to resolve it yet, e.g. Prompt: What's the weather like today and both two models show the lag and the text flashing.

@pernielsentikaer This looks good for merge.


add promo img upload support to apps and sites

lot of copy/pasting icon/preview code to add fields and helpers for a different image type.
adds image upload form to lookup tool (no ajax)
adds more tests to check_upload
takes one 1920px image, generates a resized one at 640px

@robhudson r? when you're free. there's one failing test, working on debugging that

Hmm. I asked if we needed this when I created the form and the answer was no since it was only a phase0 project. Did something change?

Ah, sorry. The context is that this is for desktop games.


easy handle's lua_State need to initialize.

    local easy = curl.easy()
    easy:setopt_url('http://www.baidu.com')
    easy:setopt_writefunction(function(buf)
        print('recv', #buf)
    end)
    multi:add_handle(easy)

This code would crash, because easy handle's L is NULL, and never be set.

Coverage increased (+0.05%) to 60.997% when pulling a9519f16a16b966468e92c100ab09453f3aad9a4 on yihuang:patch-1 into 14a9246abe3b50309759e1b9f50426ef1f265680 on Lua-cURL:master.

Did you have test code. This code works fine for me.
Not that perform function set Lua State for multi handle and for all childs
This done because you can run this function from different thread from which you create handle.
Can checkout this comment
My test example
local curl = require "lcurl"

local multi = curl.multi()
local easy = curl.easy()

easy:setopt_url('http://www.baidu.com')
easy:setopt_writefunction(function(buf)
	print('recv', #buf)
end)
multi:add_handle(easy)

while multi:perform() > 0 do
  multi:wait()
end

Result
recv	2047
recv	3793
recv	8188
recv	585

I was trying to use multi api with libuv, so I don't call multi:perform().
I've post the full code in this gist: https://gist.github.com/yihuang/7f8d2be038db5636dde35bde6d344865

Multi handle assign lua state before call curl api which can invoke callback.
It done because it ca be called from different coroutines.
So please checkout which function leads to problem
Also I have my own implementation fo libuv io for curl and it works without any problem
You can checkout lluv-curl library


what's black block stand for?

Dear author,
your project is helpful to the research community. just want to ask what are the black blocks in predator-prey? some forbidden areas for both predator and prey?

From the MADDPG paper:

In this variant of the classic predator-prey game, N slower cooperating agents must chase the faster adversary around a randomly generated environment with L large landmarks impeding the way. Each time the cooperative agents collide with an adversary, the agents are rewarded while the adversary is penalized. Agents observe the relative positions and velocities of the agents, and the positions of the landmarks.

 Presumably they are included to make the problem more interesting (e.g. prey can use landmarks to block the path of predators)


fix(booking page): horizontal scroll of hour list

closes #49

@hashrock Can you check if the issue resolved on your end? https://meet-me-vn5wsc9ay2s0.deno.dev/yoshiya/30min

@kt3k
Thank you, It resolved!


⚠ Minecraft has degraded performance

In f40c169, Minecraft (https://www.minecraft.net) experienced degraded performance:

HTTP code: 200
Response time: 1104 ms

Resolved: Minecraft performance has improved in 23fbb9d.


ParamManager.getSecretsProvider() fails with NoSuchMethodException

What were you trying to accomplish?
Create a SecretsProvider without providing a SecretsManagerClient. This may also be true for SSMProvider.
The application using this implementation will not run.
Expected Behavior
A SecretsProvider is created, initialized and handed back to the caller.
Current Behavior
A NoSuchMethodException is thrown:
Caused by: java.lang.NoSuchMethodException: software.amazon.lambda.powertools.parameters.SecretsProvider.<init>(software.amazon.lambda.powertools.parameters.cache.CacheManager)
	at java.base/java.lang.Class.getConstructor0(Unknown Source)
	at java.base/java.lang.Class.getDeclaredConstructor(Unknown Source)
	at software.amazon.lambda.powertools.parameters.ParamManager.createProvider(ParamManager.java:169)

Possible Solution
Create SecretsManagerClient and pass it to the getSecretsProvider() factory method.
Steps to Reproduce (for bugs)

Create a SecretsProvider using its factory method without any parameters:

SecretsProvider secretsProvider = ParamManager.getSecretsProvider().defaultMaxAge(10, MINUTES);

Environment

Powertools for AWS Lambda (Java) version used: 1.16.0
Packaging format (Layers, Maven/Gradle): Gradle
AWS Lambda function runtime: Java 11
Debugging logs

How to enable debug mode**

...
Caused by: java.lang.NoSuchMethodException: software.amazon.lambda.powertools.parameters.SecretsProvider.<init>(software.amazon.lambda.powertools.parameters.cache.CacheManager)
	at java.base/java.lang.Class.getConstructor0(Unknown Source)
	at java.base/java.lang.Class.getDeclaredConstructor(Unknown Source)
	at software.amazon.lambda.powertools.parameters.ParamManager.createProvider(ParamManager.java:169)

Looking at ParamManager.java:169 I can see that the implementation tries to create an instance using a Constructor that accepts only a CacheManager. This Constructor is present in the BaseProvider class but is not present in the SecretsProvider implementation.

Seems that c7aedc4d2a61013450bf472bb7a8285f8cf80e41 fixes this issue

Thanks for reporting this and for the deep analysis. I will have a look at this.

@roamingthings feel free to review https://github.com/aws-powertools/powertools-lambda-java/pull/1282 and let me know what you think


Login Exception

I logged into GitHub then clicked the link to the exercise page and received this error:

Clicking another link : https://www.scala-exercises.org/scala_tutorial/terms_and_types
Then clicking login with github on that page resulted in successful login and no errors.
After successful login I refreshed the exercise main page and still got the exception error.

Hello @thleo, we have been trying to reproduce that behaviour, but we were not able to. We tried on two laptops with different configurations and by being already logged in Github before going into Scala Exercises, the other way around, etc. and the login worked
What browser/OS were you using? Can you reproduce it on a regular basis?

I cannot reproduce the error on a regular basis though I have tried just now. I am on :

windows 8 enterprise
dell machine
Version 61.0.3163.100 (Official Build) (64-bit) chrome

Hello @thleo, I'm gonna close this issue since we haven't found any solid evidence that can lead to this failure. Probably was a punctual GitHub login service downtime, or our server going bananas at the exact moment you logged in.
Please feel free to reopen if you encounter it again on your Scala learning path.


fix(intersection): always set RTC distance to default stop line

Signed-off-by: Mamoru Sobue<EMAIL_ADDRESS>Description
Always set RTC distance to default stop line position
Tests performed
RTC distance value:
before this change:
  module:
    type: 8
  safe: true
  command_status:
    type: 1
  auto_mode: false
  start_distance: -100000.0
  finish_distance: -100000.0

after this change:
  module:
    type: 8
  safe: true
  command_status:
    type: 0
  auto_mode: false
  start_distance: 32.69912338256836
  finish_distance: 32.69912338256836

stop line visibility
pressed R2 button on foa.
before this change (intersection stop line does not appear):

after this change (intersection stop line appears):

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[X] I've confirmed the contribution guidelines.
[X] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[X] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[X] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

@shmpwk @taikitanaka3 please approve this PR


a decorator for http parameters checking

Hi!
I'd like share some piece of code I wrote this morning.   Please let me know if this has been done before or you know how to do it better.
https://gist.github.com/746706
This decorator is very useful when writing an API server with bottle.  With this decorator, I saved  large amount of redundant code on parameter checking.

@defnull Is this something provided elsewhere? I stumbled on more or less the same idea from Giuseppe Tribulato and cleaned his implementation up a smidge:
https://gist.github.com/nugend/f56fa9b7bbddf2c56709
I find this pretty useful, personally.


🐛 use thread-safe maps and fix requeing issue

Summary
use thread-safe maps and fix requeing issue
Related issue(s)
Fixes # https://github.com/kubestellar/kubestellar/issues/1820

@pdettori Not an error,  but in util safemap functions there is a mix of defere unlocks after the lock , and explicit unlocks at the end of the function. Any special reason why not using the defere pattern everywhere?

@nirrozenbaum @ezrasilvera thanks, I have addressed both your comments


[Hive & PostgreSQL] - Validate/Init schema : Error & Lang

Hello,
Thank you for your work which has been much appreciated within our company.
We used the TDP using the "Quick Start" contained in the tdp-getting-started repo. README.md file and found an issue with this task : tdp-collection/roles/hive/common/tasks/init_schema.yml while deploying.
Here is the error message encountered when executing the Validate Hive Metastore Schema task :
TASK [tosit.tdp.common : Validate Hive Metastore schema] ***************************************************************************************************************************************************************
fatal: [master-03]: FAILED! => changed=false
  cmd: |-
    /opt/tdp/hive/bin/hive  --config /etc/hive/conf.ms  --service schemaTool  -dbType postgres  -validate
  delta: '0:00:03.501206'
  end: '2022-05-11 14:54:42.290458'
  failed_when_result: true
  msg: non-zero return code
  rc: 1
  start: '2022-05-11 14:54:38.789252'
  stderr: |-
    SLF4J: Class path contains multiple SLF4J bindings.
    SLF4J: Found binding in [jar:file:/opt/tdp/apache-hive-3.1.3-TDP-0.1.0-SNAPSHOT-bin/lib/log4j-slf4j-impl-2.10.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
    SLF4J: Found binding in [jar:file:/opt/tdp/hadoop-3.1.1-TDP-0.1.0-SNAPSHOT/share/hadoop/common/lib/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
    SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
    SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory]
    org.apache.hadoop.hive.metastore.HiveMetaException: Failed to get schema version, Cause:ERREUR: la relation « VERSION » n'existe pas
      Position : 32
    Use --verbose for detailed stacktrace.
    *** schemaTool failed ***
  stderr_lines: <omitted>
  stdout: |-
    Starting metastore validation

    Validating schema version
  stdout_lines: <omitted>

As a workaround, we add those lines in the all.yml files in order to force the "en_US" LANG parameter for PostgreSQL (i.e. our environments are in French by default and the error management is based, among other things, on an English character string from stderr) :
# PostgreSQL

# Global configuration options that will be set in postgresql.conf.
postgresql_global_config_options:
  - option: unix_socket_directories
    value: '{{ postgresql_unix_socket_directories | join(",") }}'
# Ensure PostgreSQL prints errors message in english for
# ansible_roles/collections/ansible_collections/tosit/tdp/roles/hive/common/tasks/init_schema.yml
# to work.
  - option: lc_messages
    value: 'en_US.UTF-8'

Do you think this is really an issue and if so, does our workaround seem correct to you ?
Thank you for your help,
Cheers

Hello, thanks for issue, could show us the message/error when you manuelly run /opt/tdp/hive/bin/hive  --config /etc/hive/conf.ms  --service schemaTool  -dbType postgres  -validate at your machine  ?

I think we would need to improve the handle of error exceptions in task : tdp-collection/roles/hive/common/tasks/init_schema.yml, because the message "relation "VERSION" does not exist" could depend on database type and on OS language.

A fix for tdp-collection/roles/hive/common/tasks/init_schema.yml could be:
In task "Validate Hive Metastore schema":
failed_when: |
    hive_validate.rc > 1 or
    (hive_validate.rc == 0 and "schemaTool completed" in hive_validate.stdout)

In task "Hive Metastore initSchema":
when: |
    hive_validate.rc == 1 and
    "schemaTool failed" in hive_validate.stderr


Add unocss-themes to community and usage section

Thanks but I think this is too much. Please do one thing per PR


Can this module be used as ECR for lambda image code?

Description
I want to use this module, if possible, to host local AWS account lambda ECR code images. I am having trouble with the policies however. Could the examples be updated if possible to reflect how appropriate policies would be set for lambda to consume the ECR images as code? For that matter could any example show how to set a custom policy, or to ignore changes to policy (made by other AWS services - lambda)?
I can see input: repository_lambda_read_access_arns will result in a policy of:
{
  "Sid": "PrivateLambdaReadOnly",
  "Effect": "Allow",
  "Principal": {
    "Service": "lambda.amazonaws.com"
  },
  "Action": [
    "ecr:BatchGetImage",
    "ecr:GetDownloadUrlForLayer"
  ],
  "Condition": {
    "StringLike": {
      "aws:sourceArn": "arn:aws:iam::<account>:role/<ecr_name>"
    }
  }
}

this is almost a match on what lambda itself seems to want to set on the ECR, this permission appears after lambda is set to grab the ECR image:
{
  "Sid": "LambdaECRImageRetrievalPolicy",
  "Effect": "Allow",
  "Principal": {
    "Service": "lambda.amazonaws.com"
  },
  "Action": [
    "ecr:BatchGetImage",
    "ecr:DeleteRepositoryPolicy",
    "ecr:GetDownloadUrlForLayer",
    "ecr:GetRepositoryPolicy",
    "ecr:SetRepositoryPolicy"
  ],
  "Condition": {
    "StringLike": {
      "aws:sourceArn": "arn:aws:lambda:<region>:<account>:function:*"
    }
  }
}

I am unsure if this is just a user error my end or a feature request sorry.
I should also add that an initial build of the ECR with this module and then a lambda build to reference the ECR as code image does work at first. Where things go awry is any future terraform apply will look to strip the added policy that lambda has added, and this results in permissions errors for Lambda then not being allowed to access the ECR.
If your request is for a new feature, please use the Feature request template.

[ ] ✋ I have searched the open/closed issues and my issue is not listed.

⚠ Note
Before you submit an issue, please perform the following first:

Remove the local .terraform directory (! ONLY if state is stored remotely, which hopefully you are following that best practice!): rm -rf .terraform/
Re-initialize the project root to pull down modules: terraform init
Re-attempt your terraform plan or apply and check if the issue still persists

Versions

Module version [Required]:

Terraform version:

Provider version(s):

Reproduction Code [Required]

Steps to reproduce the behavior:

Expected behavior

Actual behavior

Terminal Output Screenshot(s)

Additional context

Here you can find the code to use Lambda with ECR resources.
I have just updated it (https://github.com/terraform-aws-modules/terraform-aws-lambda/pull/559) and included integration with this ECR repository - https://github.com/terraform-aws-modules/terraform-aws-lambda/blob/master/examples/container-image/main.tf

Thanks. This example: https://github.com/terraform-aws-modules/terraform-aws-ecr/blob/master/examples/complete/main.tf still lacks how to set the lambda policy (LambdaECRImageRetrievalPolicy) though, or any custom policy. Nevermind, have abandoned the use of this module and built as resources instead.


Add Support for Colors of Items

Examples include: ink sacs that are yellow, yellow wool, etc.

Not really necessary anymore, as Spigot now supports it in 1.14+.


MDS-305 | Implemented endpoints

Stub: https://github.com/hmrc/if-stub/tree/MDS-305
In a browser
Visit http://localhost:9949/auth-login-stub/gg-sign-in
Redirect URL: http://localhost:9949/auth-login-stub/session
Enrolment Keys:
read:individuals-matching
read:individuals-benefits-and-credits-lsani-c1 (important so that fields query matches payload in IF)

Submit and copy authToken
Using Postman
Get matchId
POST http://localhost:9653
Authorization: Bearer token (paste in authToken from above)

Headers:
Content-Type: application/json
Accept: application/vnd.hmrc.P1.0+json

Body:
{
"firstName": "John",
"lastName": "Densmore",
"nino": "CS700100A",
"dateOfBirth": "1969-03-05"
}

Copy matchId from:
“/individuals/matching/”
Benefits and credits root
GET http://localhost:9654/
Authorization: Bearer token (paste in authToken from above)

Headers:
Accept: application/vnd.hmrc.P1.0+json

Query Parameters:
matchId: FILL IN FROM ABOVE

Working Tax Credits
GET http://localhost:9654/working-tax-credit
Authorization: Bearer token (paste in authToken from above)

Headers:
Accept: application/vnd.hmrc.P1.0+json

Query Parameters:
matchId: FILL IN FROM ABOVE
fromDate: 2019-01-01
toDate: 2019-12-31

Child Tax Credits
GET http://localhost:9654/child-tax-credit
Authorization: Bearer token (paste in authToken from above)

Headers:
Accept: application/vnd.hmrc.P1.0+json

Query Parameters:
matchId: FILL IN FROM ABOVE
fromDate: 2019-01-01
toDate: 2019-12-31

@owen-opencast  - approved on

@owen-opencast  - approved on

@owen-opencast  - approved once comments are addressed 👍
Moving to test as no show stoppers for me. Just commented out code to remove and a question to answer.

@owen-opencast  - approved once comments are addressed 👍
Moving to test as no show stoppers for me. Just commented out code to remove and a question to answer.


Added remote paging sample

@tishko0 @dkamburov  I don't think this sample is appropriate for a xplat sample. You cannot set a backend or service that can handle paging remote requests via the editor. This should be a custom sample.

Closing since this sample needs to be a custom sample.


Added logscale option

Hey thanks for the PR, I just pushed a new version of the code with histogram equalization, which gives similar results to your logscale option.
Closing this since the histogram equalization is closer to what Strava is doing for its heatmap (link in Readme), feel free to comment or re-open.


There's already a rstudio-server by RStudio; it looks like it can do orchestration

$ /path/to/rstudio-server-2021.09.2-382/bin/rstudio-server --help
Usage: rstudio-server {status|start|stop|restart|test-config|verify-installation|suspend-session|suspend-all|force-suspend-session|force-suspend-all|kill-session|kill-all|offline|online|active-sessions|version}

Maybe this rstudio-server should be used instead of manually calling rserver.  The options can probably be configured in rserver.conf and rsession.conf, cf. https://docs.rstudio.com/ide/server-pro/1.4.1106-5/rstudio-server-configuration.html

Nah, it looks like it's used to control systemd services, which is not what we're after here:
$ rstudio-server start
Failed to start rstudio-server.service: Access denied
See system logs and 'systemctl status rstudio-server.service' for details.

The following command still may be useful, though:
$ rstudio-server version
2022.01.999-dev+999 (Ghost Orchid) for Unknown OS

FWIW, renamed our launcher script to rsc (RStudio Server Controller) to avoid confusion.


requireIdentifier and other required* don't actually validate

requireIdentifier takes in one parameter, but is always called with 2.
The first parameter passed is the identifier string to match against, and the 2nd is the error text. Need to update the method to actually take 2 params, and validate the first against tkn.data

`	this.isDataValid = function(data, str) {
return (null == str || data === str || str.indexOf(data) > -1)
}
/*
Returns the next available token if it is an identifier. If there are no more
tokens, or the next token is not an identifier an exception will be thrown with
the given message.
*/
this.requireIdentifier=function(str, err){
	var t=this.requireToken(err);
	if(t.type==Token.IDENTIFIER && this.isDataValid(t.data, str)){
		return t;
	}
	throw new ParseException(err,t);
}`


Integrate new autograph package into catalyst

To remove our dependency on tensorflow, we will be releasing a standalone autograph package. This PR makes the necessary changes in Catalyst to use the new package.
Changes include:

Substitute tensorflow imports with standalone autograph imports.
Inherit from the existing transformer class to reuse upstream code more effectively. This means we now run all AST passes that standard AutoGraph runs.
Eliminate the ag_utils module.
Make pennylane-autograph a hard dependency of pennylane-catalyst.

[sc-46389]

@josh146 From the technical side I'll consider this ready. As soon as the package is released we can move forward with the PR.

7c6410d seems like an easy change 🤞


When a person adds an audio recording, the main pico needs to refresh its index

or the speaker icon will not show up next to their name in the person list

This is because of a decision to maintain a cache of "child designations" rather than recreate them each time the person list is needed.
As for any cache, this one must have robust and complete cache invalidation. And, it doesn't.

Fixing issue #20 introduced a way to update the cache when a person is deleted.
We already rebuild the cache when a person is added.
Now we need a general purpose way to update the cache when something (like new audio) in a child pico changes, and that something affects the child designation.

When things change in a child pico, it doesn't make sense to have the main pico recreate the entire cache of child designations from scratch each time, because only one child designation might have changed. And the NetID (second entry in the designation) will not have changed (except for the case of renaming (see issue #44) which has been taken care of).
So, I'm imagining an event to the main pico saying in effect, for this NetID here is the new child designation. The rule reacting to that event would simply replace that entry in the cache. For some user-initiated actions, this could result in a quick flurry of such events, but the rule ought to be efficient enough that this is not a concern, so no need to batch these events into a single one (although that could be done with a little trouble).
For reference, the child designation is affected by changes to the following:

the person's full name
the person's NetID (taken care of already)
the person pico's read-only core ECI
the person's last name
the person's work email address
the person's FT/PT status
the person's audio (the thing noticed in this issue)

When any of these change, the main pico needs to be notified by being sent (on the wrangler:parent_eci() family channel) the byu_hr_oit:new_child_designation event, with attributes netid and child_desig.

A helper rule could be established in the byu_hr_core ruleset, such as
rule childDesigChanged {
  select when byu_hr_core child_designation__changed
  event:send({"eci":wrangler:parent_eci(),"eid":"child_desig_changed",
    "domain":"byu_hr_oit", "type":"new_child_designation",
    "attributes":{"netid":wrangler:name(),"child_desig":child_desig()}
  })
}

This could then be raised by rules in both byu_hr_record and byu_hr_core for the cases listed earlier.


Enforce font family on

Fixes #21

Changes proposed in this Pull Request

Enforced "Open Sans" to native HTML element <input>
Enforced primary text color to native HTML element <input>, as we discussed during bug squash

Screenshots
I am 100% happy with the open sans part. But I am a little concerned about using black50 text color under the dark theme, as by default it will render like this:

I am more inclined to take it out at this point. Would like to hear input from you guys.

I am 100% happy with the open sans part. But I am a little concerned about using black50 text color under the dark theme, as by default it will render like this:

I'm fine with leaving off the theme styles for the non-material elements.  They really should be outliers & not directly supported by our themes, color-wise.


Add support for Somaliland

Somaliland is not supported by the library.
For more details please see the following like:
http://somalilandsun.com/index.php/economic/2888-somaliland-as-the-new-063-cell-phone-digits-take-root-telesom-and-state-justify-addition

There seem to be two separate issues here:

whether or not "Somaliland" is identified by the library as a separate country than Somalia
whether +252 63 is supported as a mobile prefix

You can use our demo (http://libphonenumber.appspot.com/) to verify that those numbers are indeed supported, and that the carrier is identified as Telesom. As for identifying Somaliland as a country, we follow the list of countries maintained by the ITU:
http://www.itu.int/oth/T0202.aspx?parent=T0202
Until the ITU lists Somaliland as a separate country, libphonenumber won't do so. The people you need to petition to make this happen are the ITU.


Avoid Latin phrases & format note

according the Documentation Style Guide

This change is

Personally speaking, it is widely existed in docs of k8s.
So I think it is not necessary to update.

OK, then I closed this PR.

wrong click. .

@xuhuilong Please don't create small PRs to fix individual cases of style. If you see a style problem across the docs, open an issue instead. The stream of small PRs for this kind of thing is overwhelming us.
cc @zhangxiaoyu-zidif @markthink

@steveperry-53 ok, I will do it as you said next time.


Changes OnLeavePrompt to FeedbackPrompt

Hmm, I think this wasn't up to date with the latest dev. Hang on a sec.

I am very confused.

I apologize. I obviously thought I'd added changes that I hadn't.

Apology not accepted! That was a great conversation! And I think it was one worth having.


#152: Add option for no view engine

Add '--none' flag to avoid installing any view engine. Serve static HTML files in place of the index and error views.

Hmm... 0.10 and 0.12 support? They're both past their EOL now that we're in 2017 (see Node doc), is this project intending to support those versions for the foreseeable future?

Yea, we support all the versions that Express supports.

Yea, we support all the versions that Express supports.

That blows a little bit... I'll take a look at making this work in 0.10.

We plan on changing it in the next major version. If you're OK with your PR waiting to land until then, then you don't have to worry about 0.10.

I'm still not keen on static (although I might just be misunderstanding things), but I'm happy with html if you'd prefer - no real opinion between the two.

Oh! It just came to me: I wonder if we can make this --no-view which is the typical style to disable something.

Whatever you'd like. --no-view as in a different flag from --view? Like that better than the others?

Yea, something. I'm thinking --no-view as the disablement of --view, which is what you were arguing for with the conversation of none vs static. Just take a look at something like git gc --help for example of what is common in command line programs. For example, it has --prune=<date> or --no-prune. That seems similar to us having a --view=<engine> or --no-view, which makes sense to me, at least.

Sounds reasonable to me, and keeps the options a little more sensible - separates the view engine options from the absence-of-view-engine option. I'll give it a shot this weekend.

This looks like it works for me now with the --no-view options. It looks like commander supports that functionality directly.

I think I've resolved the regression, and I added a test to assert that.

How have I managed to accumulate conflicts? So far as I can tell I'm still working off the head of master and I don't see how I could have introduced a conflict with myself...

I think that may have been my bad. I just got on my main computer and went to this project in order to start merging your PR since we need to get a release out for Express 4.15.0 asap, and syncing the repo I think threw up some commits from last month. You're welcome to rebase (not merge) your changes, otherwise just leave as-is and I can work at rebasing them.

Ah, I hadn't added this as upstream, that's why I wasn't seeing them. I'll give rebasing a shot.

I believe this is ready for a re-review when you have a chance.

Was the --view=none thing ever resolved?

Was the --view=none thing ever resolved?

We talked about it here. I assumed the validation was a separate issue. Perhaps something to address in a follow up?

That's perfectly fine. Pleas let ping me when you've added the follow up commit here to address :)

I replaced all the '\n' with eol in 642ffdb

Newlines and strict string matching assertions look like a bit of a mess. In a09fae2 I tried to use the platform specific newlines, but it looks like it's not consistent (see failing tests in Windows). 1d9b82f is an answer to that - using regexs instead. Hopefully that's workable, @dougwilson?

Hi @tobymurray I just took a look at your updates and I'm a bit confused as to what is going on; my comments on the \n vs eol was only regarding the changes you were making, not the entire project. I think updating the entire project is good, that that would probably be more of something to do in a different PR, rather than postponing this one further. The only thing I've been waiting on is the fix to not accept --view=none. I'm not sure I'm seeing this in the changeset, have you addressed it?

I think we've got our wires crossed here.

my comments on the \n vs eol was only regarding the changes you were making

My bad on that one, I didn't see the value in consistency when the project was inconsistent, so I assumed you meant aligning the project.

The only thing I've been waiting on is the fix to not accept --view=none

That is what I was speaking to in my comment here. The validation to not accept arguments that happen to match the string representation is an existing issue - as you mentioned here.
I thought we were agreeing to punt the validation and you were waiting for newline consistency, so no, I have not addressed it. Clearly that's not the case.

That is what I was speaking to in my comment here. The validation to not accept arguments that happen to match the string representation is an existing issue - as you mentioned here.

So it sounds like you may have misunderstood or because you said a few different things in the paragraph, I wasn't clear enough in what I meant.
The "previous issue" is --view=foo does not error. I'm not expecting that to be fixed here.
But that is not the same as the --view=none issue. This PR needs to treat it exactly the same as view=foo, not the same as --no-view. That is the bug this PR is introducing and I'm expecting to be fixed.
So perhaps to help along, let's set out my expectations for the desired changes to this PR:

Back out all the \n => eol changes into another PR, otherwise you're just going to have to make even more changes here, because I see some issues regarding the changes you made there, but would rather focus on landing the --no-view feature, not endlessly expanding the scope of this PR.
Fix --view=none to behave exactly how --view=foo behaves.

Because this has taken so long, I'm going to release 4.15 of the generator tonight so people can start generating Express 4.15 apps. I was really hoping to land your feature in 4.15, since it's a new feature, but alas it has been almost a month now. Because the version number of this module are locked to the version number of Express, this means that missing the 4.15 release means I have no idea when this feature will land in the generator, since that would depend on when a 4.16 Express gets released.

But that is not the same as the --view=none issue

Makes sense.

I have no idea when this feature will land in the generator

Also makes sense. For the sake of my own sanity, I'm going to close this - a month is just too long. If I get some time to tidy it up, I'll re-issue in a (hopefully) more production-ready state.


Add the ability to build Debian Buster images.

I think this is fixed, right?

It technically requires a small amount of code change, just for us to understand the word Buster as input. The rest should be free.


Make it fail

Test PR for #2328

Nice !

Test completed, see the files changed for the annotations.
It would have been nicer if the place where errors were raised had been annotated, but better than no annotations.


GradCAM results doesn't seem valid with resenet50

`
import cv2
import torch
import numpy as np
from pytorch_grad_cam import GradCAM
from pytorch_grad_cam.utils.image import show_cam_on_image, preprocess_image
from torchvision.models import resnet50
from torchvision import transforms
import matplotlib.pyplot as plt
rgb_img = cv2.imread("/home/zeeshan/Downloads/dog.jpg")
rgb_img = np.float32(rgb_img) / 255
input_tensor = preprocess_image(rgb_img,
mean=[0.485, 0.456, 0.406],
std=[0.229, 0.224, 0.225])
model = resnet50(pretrained=True)
target_layers = [model.layer4]
cam = GradCAM(model=model, target_layers=target_layers)
grayscale_cam = cam(input_tensor=input_tensor, targets=None)
grayscale_cam = grayscale_cam[0, :]
visualization = show_cam_on_image(rgb_img, grayscale_cam, use_rgb=True)
visualization = cv2.cvtColor(visualization, cv2.COLOR_BGR2RGB)
plt.imshow(visualization)
`
I am not getting the desired result? Could somebody please help me out, here is the link to the image.
Output Generated

Desired Output

Can you please:

Paste the original here, so I can take a look.
Retry, but when resizing the image to 224x224, so it's in the scale the model expectes. To rule out it's because the model can't recognize dogs that are so large.

Thank you so much. The problem was resolved when I resized it to 224x224.


JS:recognized in IntentRecognizer not working

Describe the bug
in the JavaScript SDK,when using the startContinuousRecognitionAsync method with a IntentRecognizer,
the recognized is never be called, just recognizing can get the callback
Version of the Cognitive Services Speech SDK
 "microsoft-cognitiveservices-speech-sdk": "^1.23.0"

@Aethey Thank you for using Speech SDK, and writing this issue up. Would you mind sharing the exact code you're reproducing this with (minus any subscription keys)?

@Aethey Thank you for using Speech SDK, and writing this issue up. Would you mind sharing the exact code you're reproducing this with (minus any subscription keys)?

sure,the funcation code like this
async sttFromMicContinuous() {

    // init recognizer
    const audioConfig = speechsdk.AudioConfig.fromDefaultMicrophoneInput();
    // if change the IntentRecognizer to SpeakerRecognizer, the callback has no problem
    const recognizer = new speechsdk.IntentRecognizer(
      speechConfig,
      audioConfig
    );

    // init intentModel
    var intentModel = speechsdk.LanguageUnderstandingModel.fromAppId(APPID);
    recognizer.addAllIntents(intentModel);

    // no problem
    recognizer.recognizing = (s, e) => {
        // can get log
        console.log(`recognizing: ${e.result.text}`);
        console.log(e.result.reason);
      };

      // never be called
      recognizer.recognized = (s, e) => {
        // nothing, never be called,
        console.log(`recognized: ${e.result.text}`);
        console.log(`recognized: ${e.result.json}`);
      };

    // start
    recognizer.startContinuousRecognitionAsync(
        () => {
          console.log("Recognition started");
        },
        (err) => {
          console.trace("err - " + err);
          recognizer.close();
          // recognizer = undefined;
        }
    );

@Aethey Is this code being run in a browser environment? (Node does not have support for direct microphone input).

@Aethey Is this code being run in a browser environment? (Node does not have support for direct microphone input).

run in a browser environment,and the SpeakerRecognizer is work well

@Aethey I've tested the sample here and gotten recognized callbacks using Intent Recognition. Would you mind downloading that sample, running it locally, and seeing if you see (recognized) lines in the bottom text area when you perform intent recognition?

@Aethey I've tested the sample here and gotten recognized callbacks using Intent Recognition. Would you mind downloading that sample, running it locally, and seeing if you see (recognized) lines in the bottom text area when you perform intent recognition?

thanks for your demo,and i have running it locally,but the result like this :

no callback in recognized
about the LUIS part:
    var intentModel = speechsdk.LanguageUnderstandingModel.fromSubscription(       APPKEY,       APPID,       "westus"     );     recognizer.addAllIntents(intentModel);
i can get result in python with the same APPKEY and the same APPID

@Aethey Is the region for your app westus or East Asia? Are you seeing any errors in the JS console?

@Aethey Is the region for your app westus or East Asia? Are you seeing any errors in the JS console?

the speech sdk region is "japaneast". its not in  select bar and i edit it in code.
the LUIS region is "westus",
all the log like this:

there is no response  and no error and no message about LUIS, i have no way to find the reason

@Aethey I've reproduced this, and have an understanding of the root cause. There should be a PR for this within the next few days. Thanks again for letting us know!

@Aethey I've reproduced this, and have an understanding of the root cause. There should be a PR for this within the next few days. Thanks again for letting us know!

thanks for your reply.

@Aethey JS Speech SDK v1.24 has been released, with this fix included. Thanks again for submitting this issue!


Voice Answers Page Context Refresh

The Voice Answers page is a little wacky right now, this is an update that shows questions next to responses.

This is pretty old. There's no clear reason to merge it, so I'm going to close this.


feat: migrate to ape and vyper blueprint

closes #15

another decision:

open_claim by default to enable smart contract recipients like 0xsplits.xyz
recipient can call set_open_claim(bool) which can set open_claim to False to disable this behavior
set_open_claim is a noop if the value doesn't change and emits SetOpenClaim(bool) if the value is changed
the check in claim() is changed to assert msg.sender == recipient or (self.open_claim and recipient == beneficiary)

writing the full spec in #17


Newbie Question: Is it possible t have ALVR and Oculus Rift installed on the same PC?

What happens if I install ALVR and Oculus Rift on the same PC (not using the same time, just installed and occasionally use the one or another)? Are there any conflicts with both installations or with Steam VR itself?
That's for sure a newbie question. I already have a Rift. I just thinking about to have a Go too as it needs less effort to play some VR games shortly (I need to install the sensors and cables for the Rift). Beside of that there are games which are only playable seriously with the Rift.

Yes, no problem.


MINOR: Increase timeout in log4j system test to avoid transient failures

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@ijuma Thanks for the review, merging to trunk, 2.0 and 1.1.


Disable 'Show Line Numbers' option not persistent

Version
2.6.0 (30) F-Droid
Bug
Aftet restarting the app line numbers still appear even rhough the option has been disabled.
Reproduction

Open Settings;
Go to Editor;
Turn off Show Line Numbers;
Exit Karbon;
Restart Karbon;
Line numbers reappear even though the option has been turned off;

In short, even  after Show Line Numbers option has been disabled, on app restart the line numbers appear again. So any time Karbon is started the user needs to enable and disable again this option to remove line numbers from editor.

Version
2.6.0 (30) F-Droid
Bug
Aftet restarting the app line numbers still appear even rhough the option has been disabled.
Reproduction

Open Settings;
Go to Editor;
Turn off Show Line Numbers;
Exit Karbon;
Restart Karbon;
Line numbers reappear even though the option has been turned off;

In short, even  after Show Line Numbers option has been disabled, on app restart the line numbers appear again. So any time Karbon is started the user needs to enable and disable again this option to remove line numbers from editor.

This issue is already fixed in version 2.7.0, it just not released yet

@RohitKushvaha01
Very fast response, thanks.


cmd, lib/game: Parallel universe

This PR adds a ParallelUniverse type to lib/game that uses channels to connect multiple parallel universes. It also adds the ability to run them in the vita command line tool.

Tests fixed and rebased.

Now merging, thanks for the feedback @acifani


Cleanup of bool conversion in Ptr.h for C++11.

[approve ci]

ICC says:
test_Ptr.cc(98): error: no suitable conversion function from "Ptr<PtrObject>" to "bool" exists
    box.check(some, "Non-empty Ptr<T> is true");

[approve ci Fedora]

[approve ci fedora]

@jpeach I am not going to block on this operator thing... But one could make the argument this should not have a bool operator at all.. and only a == and != with nullptr_t. This is a pointer type and it should only be tested against a nullptr_t.

I will change the testing in a separate pull request.
I followed the link to the web page that explains the original code here.  At the bottom on that page, it recommends a different approach explicitly supported by C++11 (as discussed in the working papers).  So I changed the code to use the different approach.
I would prefer something like this: http://coliru.stacked-crooked.com/a/3b082589d62d56ab .
But, if we think we may eventually convert Ptr to std::shared_ptr , then Ptr should use explicit bool like std::shared_ptr does.

The history of this code is that originally Ptr had an implicit conversion to the raw pointer, which created ambiguity about where owning references were being created. The implicit raw pointer conversion also had the side-effect of implementing implicit bool conversions, hence the addition of an implicit bool conversion using the safe-bool idiom.
I'm generally fine with whatever we want to do here, but I do want it to be explicit. If we don't want to support implicit bool conversion, let's state that, comment/document that along with the rationale and add tests to verify this. If this PR is just a cleanup then it should not have any semantic changes.

I refer to this which is the draft standard for adding the explicit qualifier to user defined type conversions. The example in that draft is exactly this case. The feature was added to C++11 primarily to be used precisely the way Walt used it here.
The only difference is there is no longer an implicit conversion to bool function argument. I think that's acceptable for cleaner and far more standard code, as did the C++ Standard Committee. I doubt there is a single use of Ptr<T> in that style. Note all of these compile with these changes:
  box.check(bool(some), "Non-empty Ptr<T> is true");
  if (some) box.check(true, "Non-empty Ptr<T> is true");
  else box.check(false, "Non-empty Ptr<T> is true");

These are the standard usages, not the call to TestBox::check. That is the only line in the entire codebase that is damaged by this change. Do we want less clean code so we do not have to change that one line of test code, which represents no actual use of this feature?
If we want to update the documents, we can simply state the implementation adheres to standard C++ usage of pointer to bool conversion. The rational is precisely that stated in the C++ Standards Committee document.

Do we want less clean code so we do not have to change that one line of test code,
which represents no actual use of this feature?

What are you talking about? My last review comment was that we should make the change in semantics explicit and add tests for all the cases that are expected to work.

Allright, I'll have Walt clean this up as noted.

@jpeach @dragon512 I think this is fine now. Please review. Thanks.

[approve ci ubuntu]

[approve ci centos]

@dragon512 This is ready for re-review.

@gtenev has requested this to be back ported to 7.1.2, so did that.


adding dad jokes

Where are the tests? @ThomasStalley

Where are the tests? @ThomasStalley

¯_(ツ)_/¯
never heard of him

Wait. I just realised your forked the repo! 🤣 Is this a hostile takeover?

Wait. I just realised your forked the repo! 🤣 Is this a hostile takeover?

Git-tatorship ❗

Normally a fork is when you like a project but want to take it in a different direction from the original creators. 🤣

Ah I see, thanks!
p.s. I am the captain now


Separates source from test code in test examples

Addresses https://github.com/pallets/click/issues/1119

Tested with pytest 4.5.0 and Python 3.6.8 on Ubuntu 16.04, all four test examples in the doc passed.


Handle multiple parallel hierarchies per dimension

Forest regions can be grouped following two different taxonomies
Switzerland - Level 0 [root]
    split into [Protection forest regions](https://s.geo.admin.ch/994786067c) - with children at Level 1a:
        Jura + Plateau
        Northwestern Alps
        Northeastern Alps
        Southwestern Alps
        Southeastern Alps
        Southern Alps

    - or alternatively -

Switzerland - Level 0 [root]
    split into [Production regions](https://s.geo.admin.ch/994784e008) - with children at Level 1b:
        Jura
        Plateau
        Pre-Alps
        Alps
        Southern Alps

    - or alternatively -

Switzerland - Level 0 [root]
    split into Cantons - with children at Level 1c:
        ZH
        BE
        ...

By default we should not show regions of different kind (hierarchy trees) as they potentially overlap with each other.
Input from Michael regarding the data side implementation for this issue
1 Additional Description for the Hierarchy (if needed)
The multiple different hierarchies, might have the same root (CH -> Forest Protection Regions / Forest Production Regions), or completely different roots (e.g. Europe -> NUTS Regions / CH -> Cantons). For the same root case, it is necessary, to also show the "type" of the root. (It should be shown together with the Root classification, as shown below.)
The additional description is only shown in case of multiple hierarchies. (To keep the interface clean, and also because most hierarchies do not have such a description.)

The description can be taken from the schema:name inside the hierarchy description which looks something like the below. The same language fallback as in the rest of visualize.admin.ch shall be used:
[
  meta:inHierarchy [
    a meta:Hierarchy ;
    meta:hierarchyRoot <https://ld.admin.ch/country/CHE> ;
    schema:name "CH - Forest Prod" ;
    meta:nextInHierarchy [
      schema:name "Forest Production Regions"@en ;
      schema:name "Wald Produktionsregionen"@de ;
      sh:path <http://schema.org/containsPlace> ;
    ]
  ]
]
[
  meta:inHierarchy [
    a meta:Hierarchy ;
    meta:hierarchyRoot <https://ld.admin.ch/country/CHE> ;
    schema:name "CH - Forest Eco" ;
    meta:nextInHierarchy [
      schema:name "Forest Economic Regions" ;
      sh:path <http://schema.org/containsPlace> ;
    ]
  ]
]

Zazuko will need to document this properly.

Related cube : https://test.visualize.admin.ch/en/browse?previous={"includeDrafts"%3Atrue%2C"order"%3A"SCORE"%2C"search"%3A"nfi"}&dataset=https%3A%2F%2Fenvironment.ld.admin.ch%2Ffoen%2Fnfi%2FC-96-r%2Fcube%2F1&dataSource=Int

example data is provided online in this cube: https://test.visualize.admin.ch/en/browse?dataset=https%3A%2F%2Fenvironment.ld.admin.ch%2Ffoen%2Fnfi%2FC-96-r%2Fcube%2F1&dataSource=Int

UI & spec as documented in michaels comment

LGTM


Some bugs I found

I tried to build with the latest built llvm and mlir, I've found following things which may need to adjust:

[x] deprecated function countPopulation in file BitSequence.h, now it's popcount
[x] zip function used in BitInterpreter.h line 180, which doesn't match the definition in BitSequenceAttr.h line 347
[x] inferReturnTypes impl of both ub dialect's PoisonOp and bit dialect's ConstantOp lack one argument of Type OpaqueProperties
[x] BitSequenceAttr::get on line 28 in BitSequenceAttr.cpp: return Type is BitSequenceAttr but got Attribute
[x] Same function as above line 42, second return has Type IntegerAttr, may need dyn_cast to BitSequenceAttr manually
[x] Same file line 88 error: incompatible operand types ('mlir::bit::BitSequenceType const' and 'IntegerType') for elementTy
[x] Same file line 116 function DenseBitSequencesAttr::get in return statement, should it be elementTy instead of type
[x] Same file line 144,167,192,196,228,229,233 functions of ShapedType but got Type, should use getShapedType instead of getType
[x] 10 more errors

I've changed some of these and left some that I don't know how to fix and there are some I didn't mention here. Would you like to see the fixed I've made?

I've changed some LOC and now it can be successfully built, but there is still something different as expected with base2-opt, i.e. constant folding and bit2llvm lowering. Besides, I think the llvm upstream has a bug and I've already opened a new issue in their GH. I've pushed everything up and been trying to spot the problems.

I've changed some LOC and now it can be successfully built, but there is still something different as expected with base2-opt, i.e. the bit2llvm lowering and integer folding with base2 dialect. Besides, I think the llvm upstream has a bug and I've already opened a new issue in their GH. I've pushed everything up and been trying to spot the problems.

I've fixed the bit2llvm, the problem is that now mlir use Attr instead of Value when creating llvm::ConstantOp. I simply make some casts then it works fine;)


Discord signIn in middleware leads to 400 Bad Request

Environment
No response
Reproduction
Use https://github.com/parafeu/question-astral
Run:
npm run build

npm run preview

and visit localhost:3000 -> the error should appear in the server side console. You do not need to configure the discord provider for this, only setting secret & origin is enough
Describe the bug
Reported by @parafeu on discord here: https://discord.com/channels/1024643779711483944/1045285735575593010
Additional context
No response
Logs
No response

Thanks @parafeu for reporting the issue


Fix WarningBitsConditionChecker

Assume that all masternodes are upgraded to avoid false warnings
(another attempt/part to fix #1756 )

tACK, two nodes tested.


Rendering issue with indium ( i think )

The game crashed whilst unexpected error
latest.log
Error: java.util.concurrent.CompletionException: net.minecraft.class_148: Tessellating block in world - Indium Renderer
Exit Code: -1

I don't think this is an Indium issue; please test without Sodium and Indium. It looks like one of your mods is setting a null BlockState in the world somewhere, or generating blocks that aren't registered properly.

I am also having the same issue. It would be cool if we could figure out how to determine which block(state) from which mod is causing the issues here.

Crash report and latest log: https://gist.github.com/Brittank88/3c0a9061c2357808c1cdfa93d5f66261

Heads up, this might be a result of Fabric Rendering API's SpriteFinderImpl...basically just giving up entirely: https://github.com/PepperCode1/Continuity/issues/120

Fixed in Indigo (https://github.com/FabricMC/fabric/commit/c0ae659db23d759a232f17767d080b0ba3f501fa), needs port to Indium; see https://github.com/PepperCode1/Continuity/issues/120#issuecomment-1280003103

Oh huh, I never realised this was a fix in the rendering API, not Indigo. I've increased the rendering API dependency version for other reasons anyway; this should be fixed with the Fabric API update.


Deprecation warnings with Visual Studio 17.3

Describe the bug
Upon upgrading the Visual Studio to 17.3 I get the following warnings:
warning C4996: '_Header_ciso646': warning STL4036:  is removed in C++20. You can define _SILENCE_CXX20_CISO646_REMOVED_WARNING or _SILENCE_ALL_CXX20_DEPRECATION_WARNINGS to acknowledge that you have received this warning.
abseil-cpp/absl/meta/type_traits.h(125,50): warning C4996: 'std::aligned_storage<_Len,_Align>': warning STL4034: std::aligned_storage and std::aligned_storage_t are deprecated in C++23. Prefer alignas(T) std::byte t_buff[sizeof(T)]. You can define _SILENCE_CXX23_ALIGNED_STORAGE_DEPRECATION_WARNING or _SILENCE_ALL_CXX23_DEPRECATION_WARNINGS to acknowledge that you have received this warning.
60>C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.33.31629\include\type_traits(1070,1): message : see declaration of 'std::aligned_storage'
Steps to reproduce the bug
Build abseil with latest MSVC
What version of Abseil are you using?
0c92330442d6b1be934e0407115c8084250ef347
What operating system and version are you using
Latest Windows 10
What compiler and version are you using?
MSVC 14.33.31629 (Visual Studio 17.3)
What build system are you using?
MSBuild with CMake 3.21.4

Fixed by 3e54e87f020c71440217ce2ad382b800c4658970 yesterday.

Actually the first warning was fixed. The second needs a fix.

The ciso646 include seems to be still present in release 20220623.1

We do releases approximately every 6 months.

Hi,
FYI, the second warning (about deprecated std::aligned_storage is still present in the current release + the current development branches. Is it planned to at least silence it (with a pragma) if you don't immediatly plan on re-writing this part of the code to not use this deprecated class ?
Cheers,
Romain


Updating integration tests to have a single version

The release process doesn't currently work because the integration tests pom.xml allows for multiple versions to be tested.  Reverting back to the old way of having only the current version to be testable.  We switched our jenkins jobs to pull in older versions of the tests using tags in so the pom.xml flexibility is no longer needed anyway.

LGTM


How can monitor the matrics of kafka

Hi have already enabled the jmx exporter and kafka-exporter which deployed the kafka-exporter pod on my one of namespace.
Now i have deployed Prometheus-operator in monitoring name space now how can i get the mertics on my Prometheus and then grafana.

You will need to set up servicemonitors to make prometheus scrape the exporters. Please see the documentation in the coreos/prometheus-operator repo

Or you can add a scrape target for kafka in additionalScrapeConfigs in prometheus operator here.
Scrape configuration -
additionalScrapeConfigs:
  - job_name: 'kafka'
    scrape_interval: 10s
    scrape_timeout: 10s
    static_configs:
      - targets: ['ke-cp-zookeeper.kafka:5556', 'ke-cp-kafka.kafka:5556', 'ke-cp-kafka-connect.kafka:5556', 'ke-cp-kafka-rest.kafka:5556', 'ke-cp-schema-registry.kafka:5556']

The incubator/kafka documentation says that is supports auto-configuration of Promethues explorter and alert manager.
This is an excerpt from my helm value file.

prometheus:
  ## Prometheus JMX Exporter: exposes the majority of Kafkas metrics
  jmx:
    enabled: true

  ## Prometheus Kafka Exporter: exposes complimentary metrics to JMX Exporter
  kafka:
    enabled: true

  operator:
    enabled: true

  operator:
    serviceMonitor:
      selector: { k8s-app: prometheus }

So it should automatically register to the Prometheus operator. This seems to be not working. Anyone has any idea for this?


Use bootstrap-select-2 plugin for per page items selector

Hi,
Before :

After :

Only to have better design.
Regards

I have tried this before, but i can't make the select field and pagination bar the same height, so i give up.


Update PIDSource methods so they can be used

:+1: Jake Backer needs this merged ASAP so I'll merge it for you this time.


[Basic] Use new GetSVN.cmake parameters

This should be merged only after LLVM revision D35133 (or some version of it) is merged into LLVM upstream, and pulled down into apple/swift-llvm. In the meantime, however, I think this patch demonstrates why D35133 is useful, so I'd like to submit it for review.
@jrose-apple, feel free to review either of the patches! 🙇

LLVM's GetSVN.cmake is capable of finding the remote URL and revision of one repository, using the FIRST_SOURCE_DIR/FIRST_NAME parameters, and optionally a second one, using the optional SECOND_SOURCE_DIR/SECOND_NAME parameters. Because Swift requires source control information for three repositories, it calls GetSVN.cmake three times, with three FIRST_SOURCE_DIR/FIRST_NAME parameters.
LLVM https://reviews.llvm.org/D35132 modifies GetSVN.cmake such that it can take any number of SOURCE_DIRS and NAMES, instead of just one (or two). Use these new parameters to simplify the CMake in swift/lib/Basic/CMakeLists.txt.
There's one other change here: instead of creating three files (LLVMRevision.inc, ClangRevision.inc, and SwiftRevision.inc), as of this diff only one is created: Revision.inc. There is no difference in functionality -- swift::printFullRevisionString() behaves the same, even when revision information for only a subset of repositories is found.

@jrose-apple, do you have any suggestions for reviewers for https://reviews.llvm.org/D35132, https://reviews.llvm.org/D35133, and https://reviews.llvm.org/D35138?

ChrisB was my suggestion too.
This is fine to go in if/when the LLVM change goes in.

Seems like this would take significant reworking to get up-to-date with the monorepo work.  I could be very very wrong.  Please reopen this and rebase it if that is the case.


Heroku style commands

Hey,
Using thor at the moment as a CLI tool for an API and one of the things I would like to do is create Heroku style commands. For anyone that is unsure what I a mean, here is an example.
$ myclitool

Commands:
  myclitool servers:list
  myclitool servers:add
  myclitool servers:status

instead of thor's default
$ myclitool

Commands:
  myclitool servers list
  myclitool servers add
  myclitool servers status

I have altered the banner method to output it correctly however it just doesn't accept it the subcommands.
def self.banner(task, task_help = false, subcommand = false)
  subcommand_banner = to_s.split(/::/).map{|s| s.downcase}[2..-1]
  subcommand_banner = if subcommand_banner.size > 0
                        subcommand_banner.join(':')
                      else
                        nil
                      end

  task = (task_help ? task.formatted_usage(self, false, subcommand) : task.name)
  banner_base + " " + [subcommand_banner, task].compact.join(":")
end

Can anyone point me in the right direction with this one?

@jacobbednarz what was the solution?

It's been a little while since I done it however I believe it was contained in these two commits.
Checkout the full project at https://github.com/jacobbednarz/acquia-toolbelt if you want to go through the code.


cargo build always compiles 32-bit binaries on windows

> rustup show
installed toolchains
--------------------

stable-i686-pc-windows-gnu (default)
beta-i686-pc-windows-gnu
nightly-i686-pc-windows-gnu

active toolchain
----------------

stable-i686-pc-windows-gnu (default)
rustc 1.8.0 (db2939409 2016-04-11)

Duplicate of #176 and fixed by #421 which will come into effect with the next release.

Thanks!


[nanodbc] build failure x64-linux openSUSE Leap 15.2 WSL2/Hyper-V

Host Environment

OS: [openSUSE Leap 15.2 running in WSL2 and Hyper-V on Microsoft Windows [Version 10.0.19041.508]]
Compiler: gcc (SUSE Linux) 9.3.1 20200406 [revision 6db837a5288ee3ca5ec504fbd5a765817e556ac2]

To Reproduce
Steps to reproduce the behavior:
The results are the same for separate vcpkg instances running on openSUSE Leap 15.2 within WSL2 and Hyper-V instances.

git pull
commit #13662 https://github.com/microsoft/vcpkg/pull/13662/commits/d056a07cc209173d3573a299823c036d53b9a7a2 is applied and updates master
./bootstrap-vcpkg.sh --disableMetrics as git pull adds/changes some [vcpkg-root]\toolsrc\ source files:
 toolsrc/include/vcpkg/base/files.h          |   4 ++
 toolsrc/src/vcpkg-test/files.cpp            |  56 +++++++++++++++++++++
 toolsrc/src/vcpkg/base/files.cpp            | 180 +++++++
toolsrc/src/vcpkg/vcpkgpaths.cpp            |  24 +++------
./vcpkg remove nanodbc (because vcpkg does not honor --editable from previous install or is it allowed with ./vcpkg upgrade --no-dry-run
rm -rf [vcpkg-root]/buildtrees/nanodbc as a new version is available
/vcpkg install nanodbc --editable
See console output below...

Failure logs

Cut and past the appropriate build messages from the console output.
>$ vcpkg install nanodbc
Computing installation plan...
The following packages will be built and installed:
    nanodbc[core]:x64-linux
Detecting compiler hash for triplet x64-linux...
Starting package 1/1: nanodbc:x64-linux
Building package nanodbc[core]:x64-linux...
-- Downloading https://github.com/nanodbc/nanodbc/archive/7404a4dd7697e188df5724ab95a7553d2fc404eb.tar.gz...
-- Extracting source /home/ac-130h/git/vcpkg/downloads/nanodbc-nanodbc-7404a4dd7697e188df5724ab95a7553d2fc404eb.tar.gz
-- Using source at /home/ac-130h/git/vcpkg/buildtrees/nanodbc/src/3d2fc404eb-bbd91892af.clean
-- Configuring x64-linux-dbg
-- Configuring x64-linux-rel
-- Building x64-linux-dbg
-- Building x64-linux-rel
-- Installing: /home/ac-130h/git/vcpkg/packages/nanodbc_x64-linux/share/nanodbc/copyright
-- Performing post-build validation
The /lib/cmake folder should be merged with /debug/lib/cmake and moved to /share/nanodbc/cmake.
Please use the helper function vcpkg_fixup_cmake_targets()
The following cmake files were found outside /share/nanodbc. Please place cmake files in /share/nanodbc.

    /home/ac-130h/git/vcpkg/packages/nanodbc_x64-linux/lib/cmake/nanodbc/nanodbc-config-release.cmake
    /home/ac-130h/git/vcpkg/packages/nanodbc_x64-linux/lib/cmake/nanodbc/nanodbc-config.cmake
    /home/ac-130h/git/vcpkg/packages/nanodbc_x64-linux/debug/lib/cmake/nanodbc/nanodbc-config.cmake
    /home/ac-130h/git/vcpkg/packages/nanodbc_x64-linux/debug/lib/cmake/nanodbc/nanodbc-config-debug.cmake
The /debug/lib/cmake folder should be merged with /lib/cmake into /share/nanodbc
Found 3 error(s). Please correct the portfile:
    /home/ac-130h/git/vcpkg/ports/nanodbc/portfile.cmake
-- Performing post-build validation done
Error: Building package nanodbc:x64-linux failed with: POST_BUILD_CHECKS_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: nanodbc:x64-linux
  Vcpkg version: 2020.06.15-unknownhash
Additionally, attach any relevant sections from the log files above.

Please attach any additional failure logs mentioned in the console output.
None

Additional context
Add any other context about the problem here, such as what you have already tried to resolve the issue.

Please add vcpkg_fixup_cmake_targets(CONFIG_PATH lib/cmake) to VCPKG_ROOT/ports/nanodbc/portfile.cmake line 28 and try again.
Thanks.

@JackBoosY Thank you. Worked.


Remove divisible keyword

It seems that a divisible, non updatable, non refillable asset with an amount 1 would be equal to a non-divisible asset, so perhaps we can remove the divisible keyword. I think it would be worthwhile as it would remove a bit of complexity from tests and make our product less conceptually complicated.

Have a branch for this: https://github.com/bigchaindb/bigchaindb/tree/remove-divisible-keyword.

Oh interesting. So you're saying that the amount already determines whether an asset is divisible or not?
What about a divisible asset that is refillable and starts out with an amount 1? Initially, it will be effectively indivisible, but later, if it gets more amount added to it, its divisibility would become meaningful. It's true that refillable assets aren't implemented today, but they may be in the future. Were you thinking that the divisible keyword/flag could be added back at that time?
P.S. I took a look at the remove-divisible-keyword branch and see that you spotted some places where the docs became out-of-date when divisible assets became supported. Those docs should be updated, so if this idea gets shelved, let's try to remember to fix those docs at least.

What about a divisible asset that is refillable and starts out with an amount 1? Initially, it will be effectively indivisible, but later, if it gets more amount added to it, its divisibility would become meaningful. It's true that refillable assets aren't implemented today, but they may be in the future. Were you thinking that the divisible keyword/flag could be added back at that time?

If it starts out with amount 1, no-one will be able to divide it, and when it has amount >= 1, it will become divisible automatically. In the case of refillable assets, they don't appear to have any bearing or whether or not we need the divisible keyword. The only case that we would need a divisible keyword is if we want to support non-divisible assets with an amount > 1, but from what I can see this is currently not the intention:
    # If the amount is supplied we can perform extra validations to
    # the asset
    if amount is not None:
        if not isinstance(amount, int):
            raise TypeError('`amount` must be an int')

        if self.divisible is False and amount != 1:
            raise AmountError('non divisible assets always have'
                              ' amount equal to one')

        # Since refillable assets are not yet implemented this shoul
        # raise and exception
        if self.divisible is True and amount < 2:
            raise AmountError('divisible assets must have an amount'
                              ' greater than one')

Relevant:

https://github.com/bigchaindb/bigchaindb/issues/125#issuecomment-240442324
https://github.com/bigchaindb/bigchaindb/issues/125#issuecomment-240656981

Fixed with #962.


Ability to add space between the tab items 💅

Is your feature request related to a problem? Please describe.
Thank you for the plugin! This helped me migrating my visuals from tmux to zellij. I pretty much liked it and worked for me. It isn't something fancy.

However, in order to have separators I had to include an extra spacing with no formatting (nix code):
      tab_normal   "#[fg=${yellow}] {index} #[fg=${brightWhite}] {name} #[] "
      tab_active   "#[bg=${yellow},fg=${black}] {index} #[bg=${brightBlack},fg=${white}] {name} #[] "

Notice how it ends with  $[] ".
Describe the solution you'd like
To make intent more clear, adding a tab_separator perhaps that defaults to empty String and allows, in my case, to set to  .
Additional context
I have other enhancements that I will track separately.

Hey,
thanks a lot for the suggestion. I've implemented the feature and it will be included in the next release.


How to filter for variables containing substring at arbitrary positions?

Lets assume I have many variables and that some contain the key word "Total" at several positions:
foo|Total
foo|baa|Total
foo|baa|Total|qux

=>How can I filter for all variables that contain a specific substring?
I tried to
a) use a regular expression ".(Total)." (can be checked with https://pythex.org/): that.
df.filter(variable=".*(Total).*")
b) use a filter function.
df.filter(variable = lambda variable: 'Total' in variable)
c) use pandas datframe filtering
df.loc[df['variable'].str.contains('Total')]
However, pyam does not seem to support those options.
Edit:
As a workaroun,d I could get the data as pandas dataframe, filter it and wrap it
again in a pyam data frame:
new_data = df.data.loc[df['variable'].str.contains('Oil')]
new_df = pyam.IamDataFrame(new_data)
new_df.timeseries()

If there is a better solution, please let me know.

Following code works, using regular expression:
df.filter(variable=".*(Total).*", regexp= True)\
.timeseries()

I first did not understand what the doc says:
'regexp=True' disables pseudo-regexp syntax in pattern_match()
I would write instead:
'regexp=True' Enables regular expression syntax.

Thanks for raising this issue, glad that you managed to sort it out yourself.
In addition to the option regexp=True, which you found, you can also use simply
df.filter(variable="*(Total)*").timeseries()

i.e., * is a simple wildcard similar to .* in regexp.
PRs to improve the docs are always welcome.
By the way, we also have a Slack workspace with a helpdesk channel for these kinds of questions.

If one wants to ensure that an expression occurs at a distinct level, following regular expression might be helpful:
df.filter(variable="([^(|)](|)){1}Total.", regexp=True)
.timeseries()
=>Ensures that "Total" occurs at level 1


Release Kubernetes 1.7.2 - Linux only

This contains a storage fixes for Azure. I'll work on the PR.

We also need to document how and when the new storage provisioner is used


upgraded to mio v0.4

Just started with Rust and wanted to do something with RabbitMQ, came accross your library. Thanks for the work. Hope this pull request helps for the future.
Since I am really a Rust beginner, there might errors in the modifications I made.

Thanks a lot for putting this together! I'm traveling for work at the moment, but I'll merge your PR in the next day or two.

Would you mind tweaking the Cargo.toml file to specify version 0.4.x so other people don't get bit by my having used "*" everywhere? I'll open an issue to do the same for my other dependencies.

Done.

Since my PR for the updated README.MD, finally I managed to get the connection working. However, there seems to be a problem with this PR. It will only work with mio v3, and not with mio v4 together with this code. So, while Travis believes it is alright, there are still issues left.

Thanks again!

@zslayton There is a problem with the PR. Read my previous message: the example posted in the readme.md does not show similar behaviour as with mio v3. I guess there is more that should be changed in order to have mio v0.4 fully operatable.

Ah, shoot. I missed that. I'll investigate. Are you seeing the error RE: socket not connected?

Nope. There is a connection. But I dont see the messages printed with the v0.4 version. No idea why. But my debugging skills with rust are not up to standards yet.

I'm going to revert this PR until we can figure it out. It looks like v0.4 of mio also included its own version of the TcpStream struct, so there's probably a lot of work for me to do to switch to that as well.

Right, I already referenced that, and that made it compile. But that is not enough.


[KlaudSol-CMS-#222] Temporarily Comment out these areas

Can you please add screenshots of the updated UI after commenting out the areas? Thanks @Norlant1 !


Hey @edulix thank you for reaching out! This is a really cool idea and speaks to a future we'd like to someday get to. I'm going to keep the issue open for others to comment and upvote.

          Hey @edulix thank you for reaching out! This is a really cool idea and speaks to a future we'd like to someday get to. I'm going to keep the issue open for others to comment and upvote.

Originally posted by @KateCatlin in https://github.com/github/advisory-database/issues/474#issuecomment-1224946375

เข้าบัญชี นายอนุรักษ์ ศรีจันทรา เลขบัญชี1238272854กรุงเทพใหานคร


Echarts native support for accessibility

Screenshot

Description

After setting aria.show to true, ECharts will automatically generate a description of the chart according to the title, chart, data, etc. Users can also set description manually through the configuration object.

Increasing accessibility support in Apache/Superset through enhanced a11y features, such as generating aria-label with Echarts, is crucial for ensuring inclusivity and usability for all users, including those with disabilities.
By adhering to WCAG guidelines and making adjustments to colors and patterns as required, we not only enhance the user experience for individuals with disabilities but also align with standards for accessibility, promoting a more inclusive and equitable platform for all users.
Apache/Echarts has built-in capabilities for describing charts.
Let's decide to enable this feature by default, promoting inclusive content for all users. Otherwise, it may be worth considering the implementation of a feature flag to provide flexibility and accommodate varying user preferences.
Design input
If we wish to take additional steps, we can also consider altering the pattern of each series, as illustrated in https://github.com/apache/superset/pull/28171 description

@frassinier great feature request/POC! This is something we're eagerly hoping to support soon, but we need a mechanism for making it possible to enable/disable this type of functionality on a per-user basis. Please take a look at #28047 for more details.

@villebro Excellent! I like the idea of setting up a user preferences service!

Hah, just left a comment to that effect on the PR, but it looks like you beat me to the punch here :)


Solr should warn about low disk space upon startup

I ran into disk issues, hence Solr crashed. Restarted Solr, and it started up just fine and crashed later.
I think Solr should print a warning when the data directory is on a partition with low disk space (say <2% free).
My df -h:
/dev/nvme0n1p1 117G 111G 685M 100% /mnt/nvme0n1p1
I think I've seen this issue somewhere in the past, but can't find it.

torvalds.dev is analyzing the ticket

The issue you're facing is related to Solr, a popular open-source search platform from the Apache Lucene project. Your Solr instance is crashing due to low disk space. You're suggesting that Solr should warn about low disk space upon startup, especially when the data directory is on a partition with less than 2% free space.
To address this issue, you might need to modify Solr's startup scripts or configuration files to check for available disk space before starting. If the available space is less than a certain threshold (like 2%), Solr could print a warning or even refuse to start.
The files you've provided are related to Solr's configuration and system requirements:

SystemCollectionSolrConfig.xml: This is a Solr configuration file. It specifies settings for the Solr instance, such as the directory factory to use, the update handler class, and request handlers. However, it doesn't seem to contain any settings related to disk space checks.

SYSTEM_REQUIREMENTS.md: This is a markdown file that outlines the system requirements for running Solr. It mentions Java version requirements and advises against using experimental JVM options. It also notes that CPU, disk, and memory requirements depend on various factors related to how Solr is implemented. However, it doesn't provide specific guidance on disk space requirements or warnings.

To implement a disk space check, you might need to modify Solr's startup scripts rather than these files. The startup scripts are typically shell scripts that initialize the Solr instance. You could add a command to these scripts to check the available disk space and print a warning if it's below a certain threshold.
As for your question about having seen this issue somewhere in the past, it's possible that others have encountered similar problems. You could search for "Solr low disk space warning" or similar phrases in search engines, the Apache Lucene project's issue tracker, or other online forums where Solr users discuss issues.


[CCXDEV-7330] Fix openapi syntax

Description
Fixed openapi.json syntax.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

Bug fix (non-breaking change which fixes an issue)

Testing steps
N/A
Checklist

[ ] updated documentation wherever necessary
[ ] added or modified tests if necessary

Codecov Report

Merging #139 (16bb181) into main (b608885) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #139   +/-   ##
=======================================
  Coverage   89.37%   89.37%
=======================================
  Files          14       14
  Lines         386      386
=======================================
  Hits          345      345
  Misses         31       31
  Partials       10       10

Continue to review full report at Codecov.

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


Rocket commands system, move and speed control

CHANGELOG :memo:

Updated main.ts file with a new loop which prints movements and pressed keys
Created CLI main class which binds keypress events and prints launch messages
Created a KeyListener class which handles keypress and calls events from the CLI class
Created a location interface with two existing locations (Earth and Moon)
Updated Spacecraft class with speed, movement function and locations
Updated start script in package.json

PRINTS(OPTIONAL) :framed_picture:
LABELS

enhancement

Closes #3, #2, #1

Thank you so much for your contribution!
This changes conflicts with some files, we need to fix it before merge in.
The tests still running? I can't run now because I'm on a cellphone

@pyymenta Thanks.
Yeah, I saw the conflict - the files conflicting are the dist compiled ones. I'll try running the tests and see.

No, tests aren't working because they were based on the createMessage method of the Spacecraft class, which doesn't exist anymore.
I'll create a test which tests if the spacecraft's movement behaves correctly, and remove the previous test.

I understood the conflict.
I don't know why you merged the other movement system though, when I said I was doing it. I'm gonna resolve conflicts, anyways.

Conflicts fixed. The new movement system is inside this pull request, along with the new tests.
I think you can merge now.


Make file:line selectable

When double-clicking file:line the trailing dot also gets selected thus the clipboard cannot be used to paste into the command line: editor file:line.

Thank you.


WIP Renames X and pmf

See #1156 and #1051
To be merged after #1156

[ ] Tests for new functionality/models or Tests to reproduce the bug-fix in code.
[ ] Updated documentation of features that add new functionality.
[ ] Update CHANGELOG.md with major/minor changes.

Given the complexity of the other PR, it might be better to make this change before the xarray work.
I.e., we should settle on interface design choices for the (discrete) distributions, and then later worry about how to implement them.