Set forkEvery=1 for stability improvement of embulk-standards tests

To improve embulk-standards tests stability, this PR changes configuration of Gradle test processes with forkEvery=1. It recreates Gradle test processes every test class execution and expect reduction of the heap memory consumption. As the result, it might make the test faster.
https://docs.gradle.org/3.2.1/dsl/org.gradle.api.tasks.testing.Test.html

forkEvery=1
$ ./gradlew :embulk-standards:test
Publication bintrayMavenRelease not found in project :.
Publication bintrayMavenRelease not found in project :embulk-cli.
Publication bintrayMavenRelease not found in project :embulk-docs.
:embulk-jruby-strptime:compileJava UP-TO-DATE
:embulk-jruby-strptime:processResources UP-TO-DATE
:embulk-jruby-strptime:classes UP-TO-DATE
:embulk-jruby-strptime:jar UP-TO-DATE
:embulk-core:compileJava UP-TO-DATE
:embulk-core:unpackGems UP-TO-DATE
:embulk-core:processResources UP-TO-DATE
:embulk-core:classes UP-TO-DATE
:embulk-core:jar UP-TO-DATE
:embulk-core:compileTestJava UP-TO-DATE
:embulk-core:processTestResources UP-TO-DATE
:embulk-core:testClasses UP-TO-DATE
:embulk-standards:compileJava UP-TO-DATE
:embulk-standards:processResources UP-TO-DATE
:embulk-standards:classes UP-TO-DATE
:embulk-test:compileJava UP-TO-DATE
:embulk-test:processResources UP-TO-DATE
:embulk-test:classes UP-TO-DATE
:embulk-test:jar UP-TO-DATE
:embulk-standards:compileTestJava UP-TO-DATE
:embulk-standards:processTestResources UP-TO-DATE
:embulk-standards:testClasses UP-TO-DATE
:embulk-standards:test

BUILD SUCCESSFUL

Total time: 5 mins 43.545 secs

forkEvery=0 (not set)
$ ./gradlew :embulk-standards:test
Publication bintrayMavenRelease not found in project :.
Publication bintrayMavenRelease not found in project :embulk-cli.
Publication bintrayMavenRelease not found in project :embulk-docs.
:embulk-jruby-strptime:compileJava UP-TO-DATE
:embulk-jruby-strptime:processResources UP-TO-DATE
:embulk-jruby-strptime:classes UP-TO-DATE
:embulk-jruby-strptime:jar UP-TO-DATE
:embulk-core:compileJava UP-TO-DATE
:embulk-core:unpackGems UP-TO-DATE
:embulk-core:processResources UP-TO-DATE
:embulk-core:classes UP-TO-DATE
:embulk-core:jar UP-TO-DATE
:embulk-core:compileTestJava UP-TO-DATE
:embulk-core:processTestResources UP-TO-DATE
:embulk-core:testClasses UP-TO-DATE
:embulk-standards:compileJava UP-TO-DATE
:embulk-standards:processResources UP-TO-DATE
:embulk-standards:classes UP-TO-DATE
:embulk-test:compileJava UP-TO-DATE
:embulk-test:processResources UP-TO-DATE
:embulk-test:classes UP-TO-DATE
:embulk-test:jar UP-TO-DATE
:embulk-standards:compileTestJava UP-TO-DATE
:embulk-standards:processTestResources UP-TO-DATE
:embulk-standards:testClasses UP-TO-DATE
:embulk-standards:test

BUILD SUCCESSFUL

Total time: 34 mins 16.844 secs

It seems that it enables reducing wait time for CI passed actually.
10 mins 45 secs: https://ci.appveyor.com/project/embulk/embulk/build/set_forkevery_for_testing 345
11 mins 22 secs: https://ci.appveyor.com/project/embulk/embulk/build/master 350
10 mins 9 secs: https://travis-ci.org/embulk/embulk/builds/251372666
11 mins 18 secs: https://travis-ci.org/embulk/embulk/builds/251370130

@dmikurube Please take a look when you have time.

@dmikurube I think that it's better to include this PR in v0.8.27 release. What do you think about it?
Since AppVeyor build failing, I cannot release v0.8.27.

Thank you for reviewing. Will include this in 0.8.27.

Merged.

Included this in 0.8.27 on https://github.com/embulk/embulk/pull/718.


Productivity Tool validation vs OpenXmlValidator

I'm seeing the OpenXmlValidator v2.6.0 report some errors not being reported by the 2.5 SDK Productivity Tool.  Is this to be expected?

I'm not certain.  Exactly what differences in errors are you seeing?

@kfertitta : Please share specific details so that we can confirm if the behavior is expected or not?

@kfertitta There is nothing we can do with this issue. If you feel like this is still persisting in new builds, please provide a repro and we can take a look.


Update service registration docs to include address and port options

Just a minor update to the README.md to include address and port options to the consul.agent.service.register method.

Awesome, thanks!


HAL supports event reset on the device side which doesn't exist in CUDA

CUDA events can only be reset from the host using cuEventRecord (https://docs.nvidia.com/cuda/cuda-driver-api/group__CUDA__EVENT.html).
HAL API exposes a way to reset an event on the device analogue to Vulkan vkCmdResetEvent.
The HAL interface has the following signature:
iree_status_t iree_hal_cuda_graph_command_buffer_reset_event(
    iree_hal_command_buffer_t* base_command_buffer, iree_hal_event_t* event,
    iree_hal_execution_stage_t source_stage_mask)

We won't be able to reasonably implement it for CUDA backend.
Are HAL events still being used right? What is the future plan for them? What would it take to remove this part of the API from HAL?

FYI @benvanik

TLDR: ignore reset, or make wait_events fully synchronize and ignore set/reset entirely as that's valid - just suboptimal for when we start using them. Future you (or someone) can figure out how to use them after things are brought up :)
Some background/musings:
HAL events are critical for communicating the dependency information through the HAL (it's how you define the edges on the flattened DAG) - but that doesn't mean it needs to map 1:1 with the underlying HAL implementation
primitives (like CUevent). Think of the iree_hal_event_t as just a virtual handle to your actual CUDA event assigned in your implementation as needed. This means that iree_hal_event_t could just be an integer that maps into some pending CUDA event table and that is evaluated only during submission time (not during command buffer recording). Just a token to carry around so you know what you're referring to.
We need the events to have persistent handles as they can be used across command buffers (within the same queue aka CUDA stream) and those command buffers can be reused - if the events had to be different each time it would require re-recording. The indirection afforded by iree_hal_event_t lets us record command buffers once with a single event handle (essentially just an identifier) and replay them multiple times possibly with different backing event handles.
There is an important implicit guarantee in the event behavior we can exploit: since events are only usable within the same queue, and all submissions to a queue must be able to make forward progress (meaning that you can't issue a wait and then a set to a queue - the sets must always come before waits), you then know that there will never be a reset->wait and instead always a reset->set->wait. The reset is important here because it is observable host behavior but not one we rely on today. We don't have a iree_hal_event_query that enables observation from the host yet - and maybe never as it has implications we don't want to expose to our compiled code (for example when running over RPC/sandbox/non-shared memory systems it is not cheap). So ignoring reset in the CUDA backend is totally valid. We can't remove the reset_event from the HAL though as it's required for vulkan interop - recording a set in vulkan does not reset the event and instead will no-op on an already set event leading to all kinds of badness. So we'll always emit the resets - even if they are ignored by particular backends.
CUDA graphs kind of mash all these concepts together: the events you assign are recorded before/after nodes execute and thus are implicitly reset and reused but it's not something you can do yourself from the API. I feel like that's a big compromise they made as it reduces CPU<->GPU sync opportunities: cuEventQuery and cuEventSynchronize now have some implicit requirements about when they are valid to call where you can't observe the pending state of an event until you have recorded it (submitted the graph) and need an external mechanism to order that host-side behavior. But again since we don't expose cuEventQuery/vkGetEventStatus or cuEventSynchronize (as there is no Vulkan equivalent) we're fine to ignore it :)

Thanks a lot for the detailed explanation! If I understand well this means Events are used only for GPU<->GPU synchronizations within the same stream/queue. Does that mean I can just translate those into CUDA graph edges for the events within a command buffer? Within the same stream different command buffers are serialized so I assume ignoring events spanning across command buffer should be correct (even if at some pointer we might want to avoid the serialization).
One implementation could be to keep track of all the leaf nodes when an event is signaled and use those as dependency nodes when waiting on the event, the reset would then just clear the book keeping. Would that work or am I missing something?
The part I'm still unclear about how we use Event vs Barriers to synchronize within a command buffer?

Spot on, GPU<->GPU on the same device and same queue only. Semaphores are our coarser-grained primitive that allows CPU<->GPU and GPU<->GPU across devices or queues within a single device.
Good idea with the implementation; using a blackboard is what I do on the CPU implementation though I haven't gone too far on that yet and we could maybe share notes/utils whenever we get to doing it. I just accumulate dispatches until there's a barrier of any kind and flush them out - correct, but non-optimal. I know that I won't be writing the code to emit anything more than basic barriers from the compiler for awhile so it was a nice way to get some concurrency without needing to spend a lot of time up front on it :)
Barriers define a relationship between all previously recorded commands from all command buffers submitted to the same queue and all future recorded commands. Events can be thought of as "split barriers" - that's what they are referred to as in the Vulkan spec. They just give you a way to say "everything before this set_event has a happens-before relationship with everything after this wait_events" whereas barriers are like a combined set/wait saying "everything before the barrier happens-before everything after the barrier."
The way you fill bubbles in the pipeline is by packing as much work as you can between set_event/wait_events. That's what we'll be doing in the compiler when we use the SSA DAG to topologically sort dependencies ("move the users of %0 as far down as possible, set the event, move anything not transitively dependent on %0 to after the set_event, and then wait on the event before continuing with users of %0"). There's a tradeoff there with memory consumption: you need to keep the storage of %0 alive until it is fully consumed and something naive may end up going a bit too wide. This is an area where heuristics/profile-guided tuning/search can help.
There's also overhead to tracking the events and there may be actual execution overhead on the target device too so it's a tradeoff as to when to use the simpler barriers vs events. But you can imagine a canonicalizer on hal.command_buffer.wait_events that looks to see if the hal.command_buffer.set_event is right before it and if so turns it into a combined hal.command_buffer.*_barrier - we'll have that eventually but it may be a helpful way to reason about the differences today :)

Just some FYI as this issue will be good to point people at in the future:
The other things barriers/events do is allow us to indicate desired execution and cache behavior. This allows for (but does not require) fine-grained barriers.
For example a barrier (or event set/wait pair) with a source scope of DISPATCH_WRITE and a target scope of INDIRECT_COMMAND_READ says "all previous writes from dispatch operations must be visible to all future indirect dispatches at the time their parameters are read" which just ensures that they happen in the correct order (execution dependency). memory_barriers are that on a global level (all device/host memory) while buffer_barriers let you scope it to particular buffers (only those you are reading back, etc).
Vulkan uses some specific terminology here; "to make available" effectively means "flush caches back to memory" and "to make visible" means "invalidate caches to cause fetches from memory." A barrier that has source scope of DISPATCH_WRITE and target of HOST_READ means that all memory written by dispatches prior to the barrier (or event set) must be made available to the host (flushed from the device) before any more commands can be executed but does not require it to be visible: the host may still have cached values and needs to invalidate its cache. The guarantee is only that if the host does invalidate its cache after the barrier it will see all of the memory written by dispatches on the device.
Another example is the reverse: HOST_WRITE to DISPATCH_READ would say that all host writes before the barrier must be made visible to all future dispatch read operations.
All this is another area, though, that allows for dramatic simplification: it's legal to completely ignore the memory_barriers/buffer_barriers if memory is always coherent, or always flush/invalidate as required all memory instead of scoping it. The only load-bearing part is queue family transfer but that's a whole can of worms I'd like to keep sealed for awhile :P (that's what will help dedicated DMA transfer queues run overlapped with execution queues at a fine granularity)
A good resource for examples, with this one like the above GPU->CPU readback: https://github.com/KhronosGroup/Vulkan-Docs/wiki/Synchronization-Examples#cpu-read-back-of-data-written-by-a-compute-shader
Note that what we are emitting from the compiler now is full pipeline barriers after each dispatch; I like the disclaimer here: https://github.com/KhronosGroup/Vulkan-Docs/wiki/Synchronization-Examples#full-pipeline-barrier :P

I don't think there's anything to do here besides implement events in the CUDA HAL.


Add Film Category

Codecov Report

Merging #21 into main will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main       #21   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           32        34    +2
  Lines          301       305    +4
=========================================
+ Hits           301       305    +4

Impacted Files
Coverage Δ

qual_id/categories/film.py
100.00% <100.00%> (ø)

qual_id/pattern.py
100.00% <100.00%> (ø)

test/categories/test_film.py
100.00% <100.00%> (ø)

test/utils/category_helper.py
100.00% <0.00%> (ø)

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 f5c981f...8ed4339. Read the comment docs.

Thanks @aldinaufal21 !


Refactor of config pkg

TL;DR
There are some duplicates when loading config from env, do validation and set defaults.
https://github.com/abcxyz/jvs/blob/main/pkg/config/public_key_config.go#L43 and https://github.com/abcxyz/jvs/blob/23cdda185a8fc277ba798bfaf3e34543458f1934/pkg/config/crypto_config.go#L102.
We can do refactor to avoid duplicates.
Detailed design
Create a common function which handles loading config from env with any parameter. The caller of the common function need to pass the pointer of specific config like PublicKeyConfig or  CryptoConfig as the value of any parameter.
Alternatives considered
No response
Additional information
No response

Added a lib in pkg: https://github.com/abcxyz/pkg/pull/33

Adopt pkg/cfgloader wherever applicable


Improve handling of Rite Aid API errors

Today we logged an API error from Rite Aid, but the error message was just “200 OK,” which is not very helpful: https://sentry.io/organizations/usdr/issues/2940100159
Luckily, more info was buried in the details object, which still go surfaced on Sentry:
{
  details: {
    body: {
      Data: null,
      Status: 'ERROR',
      ErrCde: '400',
      ErrMsg: 'Captcha validation failed. Please retry or contact system administrator',
      ErrMsgDtl: null
    }
  }
}

The RiteAidXhrError class should have given us a nicer message, but the message did not get set correctly for some reason.
https://github.com/usdigitalresponse/univaf/blob/90b6441c283b36dd05ba83310ce7ad333d782290/loader/src/sources/riteaid/scraper.js#L53-L58

Looks like the call to super.parse(response) probably threw an error getting details.error.message: https://github.com/usdigitalresponse/univaf/blob/90b6441c283b36dd05ba83310ce7ad333d782290/loader/src/exceptions.js#L15-L28
…So maybe RiteAidXhrError should just call JSON.parse() instead of super? Otherwise the superclass’s parse method should be written to be less failure-prone.

We should probably also be re-using this error class in the Rite Aid API.


vim-mode and italian keyboard

It seems to me that vim-mode is not switching accordingly with the system language switch. For example indenting a line with ">" works only with the physical key of the us layout. When I press the ">" with an us layout activated it works as expected, but when I switch layout to the Italian, and the ">" now is elsewhere, the indentation works only with the previous key where is us ">" lays.

This is a duplicate of atom/atom-keymap#35 and atom/atom-keymap#37 - feel free to subscribe there for updates and to check out the keyboard-localization package.


Handle newlines in trigger descriptions

I'm submitting a ...

[ ] Bug report
[X] Feature request
[ ] Question / Support request

I'm not sure, if this or bug or not, but anyway, it would be nice if Grafana-Zabbix plugin was able to handle newlines in trigger description.
Zabbix handles newlines in trigger descriptions:

Grafana skips newlines

I've checked Zabbix API response and determined that newlines are being skipped on Grafana side, response JSON contains newlines.
Maybe it would be nice if Grafana-Zabbix plugin was able to handle other special characters but it's completely up to you.
Thanks in advance.

Yes, I should convert newlines to HTML tags.


how to Get Selected Values instead of indexes

Hey I'm able to get Selected index by calling controller.value. but instead of indexes I want the values which the user selected.. how to do that...
Thanks

reply

DragSelectGridView cannot provide you such information because it doesn't link any data to any index. In fact, the indexes are used by the library users to decide which widget to build in DragSelectGridView.itemBuilder, not by the library itself.
As this issue doesn't concern the library, I'm closing it. However, I believe I should be able to help you with your problem if you give me more details about what are you trying to do. Some code would also help.

Hwy i just want to get the selected values in list...
For eg... User selected 5 items and when he clicks on FAB button then on next screen selected values should come instead of index. Can u help me with this?
Thanks

?


#86 Fix singletone class initialisation

Also take care of start stop Observing issue on metro bundler restart/reload/hot-reload.

@Romick2005
So you do not have init multiple times after this PR?

Actually init called multiple times, but initPrivate only ones. Also on multiple call of init the returning result is same initialised only one time object. But generally this PR implements real singletone pattern.

About startObserving and stopObserving, would you please remove them and treat it as your own workaround in your private branch?
I don't think to ignore stopObserving when debug  is a valid solution here.
Reload process has causes similar issues around different libs ( like mis-created multiple instances for react-native-webrtc, IIRC ), given that the reload only happens on DEBUG mode only, and we can not assure that the behavior is a bug or whether it will change in the future or not, not to say there are different algorithms / fallbacks / Engines there ( ex: full reload / HMS Fast Refresh...etc ), I prefer not to add this for general usages. Personally, I only find Fast Refresh useful when I'm tweaking UI stuff, if the test is related to native library, I always did a clean restart ( swipe out ) to prevent any reload-caused issues.
I think the more appropriate way would be needing an event api like onRefresh or onReload for the native side provided by React Native, and user can config them to reset some states.

@jonastelzio @danjenkins
Hello, would you mind to take a look if this solves your problem described in #85?

Thanks @Romick2005
I just fix the style to match with the current code base, sorry to push to your branch directly, but I think it's more efficient.
If you want to adjust / fix the style, feel free to send another PR, thanks!

Since this an open source, so it would be better to follow the current code base's style, and makes minimal changes in a single PR.
But fire a PR to adjust them is acceptable for sure

Thank you @zxcpoiu, it's just styling, so never mind. No worries I am ok with this, until it works as expected :).


Task #1457217: Create FileFormatFactory for all file formats

@meijin007,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Follow your video and make cmake verison of my code which can run on different platform

https://github.com/rocketman123456/RocketGE
this is my repository, and i'm currently follow your video to study how to make a game engine.
I convert your code to run with cmake and support macos.
Thank you very much for your video series, that helps a lot!

I don’t see how this is an issue. The cherno has already said that he won’t use cmake and that if needed premake can generate cmake files.

actually, i want to leave this comment below the YouTube channel, but because of the GFW, i can't do it, so i write it here

I don’t see how this is an issue. The cherno has already said that he won’t use cmake and that if needed premake can generate cmake files.

The please don’t make a issue for it.

You can always join Cherno's discord and send him a message in the #cherno channel. Alternatively you can find him on twitch.tv/thecherno and send him a live message. I'll close this as this is not a real issue as mentioned before.


Reduce outlines with minimal visual impact

I've found that there are a lot of reaaaally thin outlines that had minimal (practically imperceptible) visual contribution to the scene. particularly at some lower zooms. By slightly cutting down on these (introducing them a bit later), we can get some substantial geometry count / performance benefits. This PR also includes a few syntax clean-ups done while reviewing outlines, such as removing redundant zoom stops (e.g. [9, 0.0px], [11, 0px], [12, 0px], [14, 0px] becomes just [14, 0px]). Examples below. These are fairly conservative, with a more intentional design eye we could probably cut them down further.
z8: 277k -> 209k polys (-68k polys)

z9: 435k -> 399k polys (-36k polys)

z10: 285k -> 267k polys (-18k polys)

z11: 194k -> 182k polys (-12k polys)

z12: 251k -> 247k polys (-4k polys)

Thanks!


I take an issue with this

what is it?

this is a joke issue, github dont ban me pls this guy is my friend


Trigger Azure DevOps Pipeline - Use pipeline access token instead of PAT

Hi Maik!
What was the reason why you built this extension with PAT authentication?
Maybe good to add some words to the documentation:
https://github.com/maikvandergaag/msft-extensions/tree/main/azuredevops/triggerpipeline
With the azure az cli and its azure devops extension something comparable can be done without using a static PAT but with the pipeline access token which is dynamically created per run.
https://docs.microsoft.com/en-us/azure/devops/cli/

We are working on this. The version number counter now has the option. We are also working on the triggerpipeline control


Add initial connector implementation to main branch

Purpose

Provide Microsoft Outlook.Mail REST API Service access through Ballerina. This connector includes the most important operations on Messages, Drafts, Attachments, Mail Folders and Child MailFolders
Fixes: https://github.com/wso2-enterprise/choreo/issues/6414

Goals

Provide Microsoft Outlook webmail service access through Ballerina

Approach

Research on Microsoft Outlook Mail API

Connector Implemetion with Peer Reviews
Add Stream Listings operations
Add Stream Uploadings operations

Automation tests

Unit tests

Done

Integration tests

Done

Security checks

Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes
Ran FindSecurityBugs plugin and verified report? no
Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes

Samples

https://github.com/ballerina-platform/module-ballerinax-microsoft.outlook.mail/tree/main/outlookmail/samples

Test environment

Ballerina Swan Lake Beta 2

Learning

https://docs.microsoft.com/en-us/graph/api/overview?view=graph-rest-1.0
https://docs.microsoft.com/en-us/graph/api/resources/mail-api-overview?view=graph-rest-1.0

var is now deprecated. It is not encouraged to use it.
Since we know the return type of a method, we can directly specify the return type.
It seems var is used in many places. Shall we try to remove the usage of var as much as possible?


webhook error

Results:
{
"error": {
"message": "Insufficient credentials provided in constructor argument. Refer to the documentation for the required parameters. Common examples are username/password and iam_access_token.",
"name": "Error",
"stack": "Error: Insufficient credentials provided in constructor argument. Refer to the documentation for the required parameters. Common examples are username/password and iam_access_token.\n    at DiscoveryV1.BaseService.initCredentials (/node_modules/watson-developer-cloud/lib/base_service.js:249:23)\n

Getting the same error! Bump up!

@Nickblaq @zacaintmyname - It looks like you didn't provide the api_key of your Watson Discovery service instance.  See the screenshot in the tutorial.
If you want to make a call to the Discovery service, you need to set some parameters that lets you call the IAM-enabled service. On the left, click on the Parameters tab. Add the following parameters: api_key, url, collection_id, and env_id. The collection_id and env_id are the values you noted from the Watson Discovery service in the previous steps.

Thanks it worked! but i still can't return data from the covid-19 summary endpoint, i keep getting empty array instead. Any solution?

when you copy the code into your IBM Cloud Functions service, make sure you paste this code from:https://github.com/Call-for-Code/Solution-Starter-Kit-Communication-2020/blob/master/starter-kit/webhook/action/covid-webhook.js
I suggest if you go to Github RAW, and copy paste that would reduce indentation errors.
You should already included your parameters as shared in the tutorial.
Then go to code >> invoke with parameters >> invoke:
{ "":"api", "country":"thailand" }
You should be able to see the results now.
I got mine working!

@Nickblaq @zacaintmyname - It looks like you didn't provide the api_key of your Watson Discovery service instance. See the screenshot in the tutorial.
If you want to make a call to the Discovery service, you need to set some parameters that lets you call the IAM-enabled service. On the left, click on the Parameters tab. Add the following parameters: api_key, url, collection_id, and env_id. The collection_id and env_id are the values you noted from the Watson Discovery service in the previous steps.

I'm

Its no working for me....I'm getting the same error
i have tried inputing the parameters but still not working
{
"error": {
"message": "Insufficient credentials provided in constructor argument. Refer to the documentation for the required parameters. Common examples are username/password and iam_access_token.",
"name": "Error",
"stack": "Error: Insufficient credentials provided in constructor argument. Refer to the documentation for the required parameters. Common examples are username/password and iam_access_token.\n    at DiscoveryV1.BaseService.initCredentials (/node_modules/watson-developer-cloud/lib/base_service.js:249:23)\n    at DiscoveryV1.BaseService (/node_modules/watson-developer-cloud/lib/base_service.js:95:29)\n    at DiscoveryV1 [as constructor] (/node_modules/watson-developer-cloud/discovery/v1-generated.js:58:28)\n    at new DiscoveryV1 (/node_modules/watson-developer-cloud/discovery/v1.js:19:23)\n    at NodeActionRunner.main [as userScriptMain] (eval at initializeActionHandler (/nodejsAction/runner.js:57:23), :55:23)\n    at Promise (/nodejsAction/runner.js:73:35)\n    at new Promise ()\n    at NodeActionRunner.run (/nodejsAction/runner.js:71:16)\n    at doRun (/nodejsAction/src/service.js:196:14)\n    at runCode (/nodejsAction/src/service.js:141:20)\n    at /nodejsAction/platform/platform.js:125:17\n    at Layer.handle [as handle_request] (/node_modules/express/lib/router/layer.js:95:5)\n    at next (/node_modules/express/lib/router/route.js:137:13)\n    at Route.dispatch (/node_modules/express/lib/router/route.js:112:3)\n    at Layer.handle [as handle_request] (/node_modules/express/lib/router/layer.js:95:5)\n    at /node_modules/express/lib/router/index.js:281:22\n    at Function.process_params (/node_modules/express/lib/router/index.js:335:12)\n    at next (/node_modules/express/lib/router/index.js:275:10)\n    at /node_modules/body-parser/lib/read.js:130:5\n    at invokeCallback (/node_modules/raw-body/index.js:224:16)\n    at done (/node_modules/raw-body/index.js:213:7)\n    at IncomingMessage.onEnd (/node_modules/raw-body/index.js:273:7)"
}
}
Logs:
[]

Hey Emirkaz, check this out: https://developer.ibm.com/conferences/c4cdc-take-on-covid19/crisis-communication-starter-kit-extend-your-covid-19-chatbot/
Should be able to troubleshoot your mistake here.

When I set parameters(type:API, country:Nigeria) I get total results? Why? What am I not getting right?
Thanks
Sent from Outlook Mobilehttps://aka.ms/blhgte

From: zacaintmyname<EMAIL_ADDRESS>Sent: Thursday, April 16, 2020 2:15:11 PM
To: Call-for-Code/Solution-Starter-Kit-Communication-2020<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: Re: [Call-for-Code/Solution-Starter-Kit-Communication-2020] webhook error (#31)
Hey Emirkaz, check this out: https://developer.ibm.com/conferences/c4cdc-take-on-covid19/crisis-communication-starter-kit-extend-your-covid-19-chatbot/
Should be able to troubleshoot your mistake here.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/Call-for-Code/Solution-Starter-Kit-Communication-2020/issues/31#issuecomment-614645223, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOTUVMGZWNW7O4EV5SHJP4LRM4AF7ANCNFSM4MGPZ4HA.

the parameters in the Cloud Functions tool is reserved for the API Key, URL, Env and collection ID.
If you key in the right credentials, then this below will work

Then go to code >> invoke with parameters >> invoke:
{ "type":"api", "country":"(of your choice)" }

All right thanks. It later worked.
Sent from Outlook Mobilehttps://aka.ms/blhgte

From: zacaintmyname<EMAIL_ADDRESS>Sent: Friday, April 17, 2020 2:21:10 AM
To: Call-for-Code/Solution-Starter-Kit-Communication-2020<EMAIL_ADDRESS>Cc: InnoOkeke<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [Call-for-Code/Solution-Starter-Kit-Communication-2020] webhook error (#31)
the parameters in the Cloud Functions tool is reserved for the API Key, URL, Env and collection ID.
If you key in the right credentials, then this below will work
Then go to code >> invoke with parameters >> invoke:
{ "type":"api", "country":"(of your choice)" }
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/Call-for-Code/Solution-Starter-Kit-Communication-2020/issues/31#issuecomment-614982405, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOTUVMA4IVROH6RJURQV7NTRM6VINANCNFSM4MGPZ4HA.

Admins i think we can close this issue.

Hey Emirkaz, check this out: https://developer.ibm.com/conferences/c4cdc-take-on-covid19/crisis-communication-starter-kit-extend-your-covid-19-chatbot/
Should be able to troubleshoot your mistake here.

Thanks Sir
its really helpful

@johnwalicki i think we are good to close.


🔹[EPIC] Add BOS to create-near-app

What
create-near-app should include an option for BOS decentralized front-ends.
Why

To provide a quick scaffolding tool that meets existing expectations for front-end devs.
To assist in onboarding developers to BOS by providing a basic project structure and a working demo.

Resources
How
### Related Issues
- [ ] https://github.com/near/create-near-app/issues/2104

@thisisjoshford @gagdiez I would really consider baking it into bos cli: https://github.com/bos-cli-rs/bos-cli-rs/issues/44
I synced with @gagdiez recently on the create-near-app topic, and shared my belief that create-near-app is not doing any good for developers and we’d better focus on the dedicated tools (cargo near new, bos project new, guides on how to integrate NEAR into frontend and backend frameworks)

to give visibility to our talk with @frol I will also include what I said.
When create-near-app was first released it was the only way to scaffold a project. Fast-forward to today and two important things have happen: (1) tooling in the ecosystem has matured, and (2) the focus on "what is a NEAR app" has shifted from a NEAR app is a smart contract with maybe a frontend to a NEAR app is something that uses Web3 Components and maybe a smart contract.
Because of this, I agree that, in the future, we might want to substitute create-near-app for another series of tools (some tools for creating contracts?? and a tool for creating frontends??).
However, right now those tools are not there yet, and the effort on changing the documentation and creating tutorials is higher than the effort to just add a new frontend type to create-near-app.
Therefore, I am going to make one last change to create-neap-app that separates creating contracts from creating frontends. After that, we need to have a call with key members of the ecosystem and make some decisions on scaffolding tools.

From the NEARCON hackathon, a team made a quick create-bos-app. It initializes an app with the bos-workspace structure so devs just need to run create-bos-app, cd into the project, and run bw dev. Now their widgets are being served and can be accessed after setting /flags.
It works, but isn't feature rich. And I do think that ideally, it doesn't need to be a separate package and could be merged into create-near-app or bos-workspace as a bw init command.
The project board for bos-workspace can be found here.
At least 22 developers have used the workspace and it has been used to deliver BOS apps like Create, Genadrop, Magicbuild, Potlock, and more. Every project in the Liberty DAO Hackoween hackathon used it and Near Builders provided support for many projects during the NEARCON hackathon who used it, too.
For context, the bos-workspace replaces bos-loader with a cleaner replacements strategy and a /build folder allowing opportunity to integrate Typescript transpilation, module building, etc..., and wraps around bos-cli-rs to allow managing multiple apps w/ different deploy accounts in one repository, enabling the ability to deploy specific directories for different purposes, and deploying JSON data to the social db (not limited to widget metadata).
I think it would be great for us to collab there, or potentially, evolving it into a fully-featured, all encompassing "near-workspace".

@elliotBraem please notice that the basic gateway created by create-near-app does not include the concept of flags for Component development. This was a conscious choice since addingflags since:

Increases the complexity, i.e. we need to explain more things in our tutorials
Is used for development of components, which we will guide users to do somewhere else (e.g. jutsu, near.org, vscode, etc).

Therefore, create-bos-app and bos-workspaces do not necessarily belong here, but they might have a place in the documentation.


Duplicate posts were made in General

I setup the CC app and had a user post a message.  When the message was sent to the General channel, it was posted 3 times. The first two had the name of our Authors app whereas the last one had the name of the user app.

Hello @monovex,
Is it happening for every message being sent?
There might be some issue at runtime at that time. Can you please confirm?
Thanks


Split UnaryOps.CAST into UnaryOps.CAST and UnaryOps.BITCAST

Here is are a couple of small changes to make the split UnaryOps.CAST into two. In this PR I have not yet created a separate Function for bitcast. I did do this and personally do find it cleaner but just to start small.

I don't understand what needs to happen in the flopcounter so closing this for now


Support detaching/re-attaching scope

This is basically, a reversible $destroy for scopes.
Detaching the scope would mean:

Detaching the scope from the scope's current parent so that watchers no longer fire when the scope's current parent's $digest is called
On re-attaching to a DOM element (as a child), it would be attached as the child scope of the DOM element

I could see this being used for optimizations such as not running watchers on hidden DOM (that could be detached).
I think a factor that affects the adoption of Angular is the fact that having many watchers could slow down the application. Currently, there's no way to "pause" the watchers on DOM that's not currently visible.
It's possible to hack out a directive to do this, but I'm wondering if this feature is of value to the rest of the Angular community as part of the Angular core.
I noticed that jqLite doesn't have .detach. .remove actually destroys the scope of the element so after re-adding it to the DOM, it actually picks up the another scope and has already lost its own scope.

I've decided to fork and modify Angular to add a flag that allows the digest to skip a $scope's children.
I wrote up my motivation and the details of watcher pausing here. Appreciate any feedback on this optimization work.

+1. I've build a routing/navigation system on top of Angular, in witch it is mantained a stack of "opened activity" that the user is working with, but the opened activity that are not in the top of the stack are "paused", i'd like not to looke the user temporary data on "paused" activity (very much like Android systems) but also not to slow down the app when the stack of acrtivity grows.. so this issue is very very Important to me.

Although this is a significant pain point for certain kinds of applications built with Angular 1, it is not a straightforward thing to fix without creating many many opportunities for subtle bugs.
Angular 2 is maturing nicely and has great support for solving this problem. For such applications that require suspending change detection on parts of the application then it would be better to upgrade to Angular 2.
Perhaps one could make use of ngUpgrade to allow those parts of the app that need to be suspended to be controlled by Angular 2?

+1 Surely if this guy can do it, the Angular team could.  I can't really think of an app with multiple "views" that wouldn't benefit from this feature. Please please please put it into 1.x branch.
@petebacondarwin ngUpgrade to a framework that isn't even out of release candidate?  Most of the Angular developers I know are moving/moved to React because of this kind of treatment.

@poshest for sure it is easy to toggle watching for a childscope.
The trouble is that there are subtle issues that can occur if you do not carefully control the boundary between the suspended scope and the rest of the scope hierarchy. In Angular 1 there a many paths that can lead to a value being made available across a scope boundary, such as use of $parent, transclusion, services and so on.
We have spent a lot of time thinking about this over the years and this is in fact one of the driving forces behind the big rewrite that is Angular 2. In Angular 2 there is much more control over the movement of data between components and so it is much safer to select parts of the component tree which do not need to run dirty checking.
If we implemented one of the many suggested solutions to this problem we would then be faced with maintaining it, and more importantly supporting the complicated corner cases that are really hard to control.
But more importantly, application developers might find that there apps are not updating as they expect and it will not necessarily obvious or easy to identify the cause.
There are already a number of production applications running on Angular 2 in the wild. My impression from those projects is that they enjoy the improved ergonomics of the new version of Angular. Of course each project must make a choice about what level of risk it is willing to take on and the timelines of the application that is being developed.

@petebacondarwin thank you.  A very sound response.  I do see the motivations behind pushing people to Angular 2 and iceboxing most requests for 1.x functionality (although why not just close them if you're not going to build them).
I started building in Angular 1.x a couple of years ago precisely because I felt it was suitable for non-trivial apps.  I'm still getting over my disappointment that it simply does not and in that short time has become legacy.  It's like buying a car that you didn't know was limited to 30mph, and being told that the only fix is buy the new faster model.
My major concern with your recommendation to upgrade is that I have no guarantee that Angular 2 will fix this issue.  To that end, perhaps you can help me understand what Angular 2 does that will help in this precise situation?  Will it just create less watches so you can ng-hide more?  Or will it have some smart disabling of watches when they're hidden?
The use case, as explained above, is lots of heavy functionality (ng-repeats, ng-ifs/shows etc, and deeply nested components) for each tab, and wanting not to have to re-render those every time the tab is re-visited.  I am already using 100% 1.5 components and one-way bindings.

Someone will do better than I will. But here's the short of it.
Angular 2 (A2) addresses the digest churn problem in two ways

It only makes a single change detection pass down the component tree whereas Angular 1 has to re-cycle the digest cycle until the model proves to be stable (minimum of 2 cycles) or you exceed the limit (10 cycles).  This one-pass guarantee is already a performance win w/o the developer having to do anything.

In Angular 2, you can set the ChangeDetectionStrategy to OnPush. When you do, Angular stops further change detection for that component and its sub-tree of components.  This is the equivalent on one-time binding BUT ...

We can trigger a new round of change detection for that component whenever we want by calling this.changeDetectorRef.markForCheck() (after injecting ChangeDetectorRef).

I think that's the on-demand refresh option that you want. It's not precisely a disable/enable switch. It's more a switch for taking over when change detection happens for a particular component and its sub-tree.
This facility is baked into A2.  Just one of many reasons to like Angular 2.

@wardbell thanks for your response and the link.
The digest churn isn't the problem I'm trying to address here, although removing the second and later passes will obviously help.  I have two problems.
(a)  It takes a long time to render my complex components.  This is the root cause and this is not addressed by this thread.  To mitigate this somewhat I wish to at least not render those complex components more than once.  But...
(b) If I render a component and then keep it around (hidden by ng-hide), it will continue to be dirty checked in the background. Because of the complexity of my app, I might have 1000s of watches hidden behind the ng-hide.
Halving (or better) the digest cycle time is great, but it doesn't solve the problem.  In addition, in response to your point 1 "w/o the developer having to do anything"... as I understand it, in Angular 2 the developer has to do lots - ie change the entire app to use the "data flows down, functions flow up" pattern.  This is a fundamental change that involves potentially a lot of work for the developer, and is the exact reason why Angular is able to give the one-pass guarantee.  It's like me saying "my framework is really fast, because loops aren't allowed - if you create a loop, the framework will throw an error".  Two-way data binding was what MADE Angular 1.x popular.
Your point 2. is much closer what I am after.  The article you referenced seems complicated and I'll have to read it a few more times.  Once again I'm disappointed that I need to understand so much about the Angular internals to make it work.
But I'm still left yearning for a very simple ng-ifshowwatch, which

before first evaluation to true acted like an ng-if (so that components aren't rendered until the user visits them)
after first evaluation to true acted like ng-show, and
when hidden in subsequent evaluations to false gets the component's (and all its childrens') watches disabled

This is a lovely experience for the developer.  markForCheck is nice for those fine-grained control requirements, but requires too much finessing for this very common use case.
BTW, you can currently do 1 and 2 with this, which is everywhere in my code.

"Oh, ng-ifshowwatch... ng-if="twere_only_for_thee""

@poshest here is another article - https://www.lucidchart.com/techblog/2016/05/04/angular-2-best-practices-change-detector-performance/ - but be aware that the API has changed since this was written.  In it the author writes:

By default, the change detection strategy on any component or directive is CheckAlways. There is another strategy, OnPush, which can be much more efficient if you build your application carefully.

OnPush means that the change detector will only run on a component or directive if one of the following occurs:

An input property has changed to a new value
An event handler fired in the component or directive
You manually tell the change detector to look for changes
The change detector of a child component or directive runs

If you’re able to use OnPush throughout your application, you will ideally only ever run the change detector on components that have actually changed (and their direct ancestors). This reduces the time complexity of the change detector from O(n) to O(log n) in the number of component instances in your application.

As you say this does require the developer to use immutable data structures and one way data-flow if you don't want to do any change detection yourself.
But I think the key for your goal is that in Angular 2 we have full control over the change detection strategy for each component. For example one can use changeDetectory.detach() and changeDetector.reattach() in your component to get the exact behaviour that you are describing that you want in Angular 1. There are some examples of doing this in the docs:
https://angular.io/docs/ts/latest/api/core/index/ChangeDetectorRef-class.html

@vahan-hartooni FYI the broken link on your post.  It's really helpful, so pls update. :)

@petebacondarwin do you have any feedback on @vahan-hartooni 's approach to this?  It's my favourite way to achieve this much needed feature.  It's a couple of lines of code, and Vahoon has already determined that it passed all the AngularJS tests.  Worst case, it doesn't work in some of those "subtle" cases you mention, but if you create the new flag as $skipChildWatchers as Vahoon suggests or even $$skipChildWatchers if you felt it should be an "unsupported, undocumented" feature, no one will be affected unless they use it.  And if they're using this, they're already deep in the belly of the Angular 1.x beast.  What's the downside?  Please consider adding his change to your next 1.5.x release. :)

I've added it to the 1.5.x milestone so that we can consider it further.

Wonderful!  Thank you @petebacondarwin :)

Hi,
It would be really nice to have an implementation of a ChangeDetector similar to Angular 2 with an OnPush mode.
I wrote a module that imitates Angular 2's behaviour but it would be really nice and cleaner to have a similar implementation integrated in Angular 1.5 or Angular 1.6.
http://www.blog.wishtack.com/single-post/2016/10/05/Boost-your-AngularJS-performance-with-ng-steroids-and-get-ready-to-migrate-to-Angular-2
https://github.com/wishtack/ng-steroids
If you agree with the behaviour, I would be glad to get some feedback before making a pull request.
Thank you all!

Is there any chance of something happening on $skipChildWatchers or similar in the 1.6 release candidates?

The feature set for 1.6.0 is more or less fixed, so I don't see it as likely.

I know you guys are better than to be persuaded by begging, but pleeeeeeaaaasse?! :)  At least for 1.6.1?
Adding those two $$skipChildWatchers lines proposed by @vahan-hartooni will not break anything for other users of AngularJS.  Only people on this thread and determined Googlers will know about it.
The app performance upside of these two lines of code for my project is enormous.

@poshest I added it to 1.6.x (post 1.6.0), since it would not be a breaking change. This means that we will try to get it into one of the 1.6.x releases.

That would be absolutely wicked :) Thanks again @petebacondarwin.

Hi @petebacondarwin, have you or any of the core team had a chance to look at this?

@poshest - I have added it to the agenda for our meeting next week. We will decide there to either implement it or close this issue.

@petebacondarwin OK, thanks, that's great. May I make one submission to the team...
If the discussion proceeds along the lines of

"well, if we're gonna do this, we should really do it right, which means creating an API like Angular 2's ChangeDetectionStrategy and all the associated options, and... yeah, it's too hard, so bin it..."

...could I suggest that instead of binning it entirely, the @vahan-hartooni suggestion is implemented.
For very little effort, this simple approach gives the educated developer tremendous control, and won't affect anyone else whatsoever.  Many thanks for your continued great work.

Great!
For the moment, I'm using my library https://github.com/wishtack/ng-steroids/tree/develop/packages/change-detector that implements the same interface as Angular 2+ but it's still too hacky.
It would be really nice to have a ChangeDetector in Angular 1.6.x.
In addition to this, all devs that are discovering Angular 2+ and still using Angular 1.x in some other projects will love to find this feature in Angular 1.x.
Thx

OK, so we have agreed to implement the simple approach using something similar to #10658.

We would like to keep as close to Angular's Change Detection behaviour as possible. If anyone wants to do a write up of how this could be done that would be great.

@petebacondarwin not sure how people should read your final two comments? Are the team planning to implement this ('we have agree to implement...'), or are you looking for outside contribution?
If @shahata's PR was modified to have a more Angular Change Detection feel, would that be merged?

Hi Tim
We have agreed to implement it but we have very few resources right now to implement it.
Also I wanted to have a view on how close we could get it to the semantic vision of Angular.
Both the view and the implementation are up for grabs if someone in the community wants to get involved.

@petebacondarwin we have very few resources to migrate to Angular 2 right now.  My only option is getting max juice out of ol' AngularJS.
Can I suggest that, in the meantime, the @vahan-hartooni suggestion is implemented. Sure, it's not consistent with Angular 2, but it's non-breaking as you said, and would allow us to switch off and on parts of the digest tree for some big big performance gains.

We would like to implement @shahata's PR here https://github.com/angular/angular.js/pull/10658
If you would be interested in helping to get that rebased and tested @poshest

Sorry for ignoring all the refs to the chosen @shahata solution. I see that it's pretty similar to @vahan-hartooni's code, but with nice $suspend and $resume functions.  I'm interested to help, but I've never done something like "rebase and test" before. I will probably mess up stuff more and take more of core members' time than if core members just did it.
For starters, what does testing even involve?  Just running the existing automated tests? Or do I need to write some new tests to properly address @igalfaso in #10658 who says "this needs to be done in a way that does not involve a lot of work for developers to upgrade to these new features, nor break common patterns used today".  I'm not even remotely equipped to do that.

No problem. Perhaps we can put together a new PR and you can try it out for us?

Absolutely happy to do that :)
On 3 October 2017 at 12:08, Pete Bacon Darwin<EMAIL_ADDRESS>wrote:

No problem. Perhaps we can put together a new PR and you can try it out
for us?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/angular/angular.js/issues/5301#issuecomment-333797737,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGp-laFeA8YyjTtEXhuv7Ho2fqlzn4kNks5sogeigaJpZM4BSQM8
.

@petebacondarwin any progress on that PR? :)

No movement yet. Sorry. I'll find some time this week.

Thanks Pete!  I appreciate it. :)

I have created a new rebased PR at #16308. @poshest - please take a look.

Great!  Absolutely, will do. :)


Add option to set languange in admin user view

/admin/users/<UserID>/edit

/admin/users/<UserID>

Sponsored by Kithara Software GmbH

I don't think the title is related with the content.

uh sory i guess i git the wrong title :D

Why users don't change the language themselves but need admin to help? I can't imagine the scenes

Yeah, same as @lunny.
The usecase isn't clear to me either.
Instead, it sounds like something that can be abused when some admin suddenly switches your Gitea language to arabic as a prank

@lunny @delvh if an admin does such a "joke" you should not consider to use that instance at all !!!
and yes if you are not a self-registration instance but you get an account created it's possible that you have to set the language.
for now this is done by log in as the user after it has been created and then change the language.
but you loose the feature to let the user be forced to have to set a new password.

and not all people do speak englisch tbh ...

@6543 please update the branch


React: Pass an Array as Props challenge clarify wording on test

Describe your problem and - if possible - how to reproduce it
The last test in this challenge doesn't explain what is expected in enough detail.  I came across the same issue as in #17758
I suggest fixing this by changing the text of the last test from:
The List component should render the value from the tasks prop in the p tag.
to
The List component should render the value from the tasks prop in the p tag as comma delimited text e.g. walk dog, workout
I'm happy to do the change if the wording looks correct
Add a Link to the page with the problem
https://learn.freecodecamp.org/front-end-libraries/react/pass-an-array-as-props
Tell us about your browser and operating system
n/a

@nirajn2311 you are absolutely right the instructions are very concise.  I am probably not clear enough in my communication.  I was referring to the tests for that challenge.  All of the other react challenges have tests that are very specific about what text is expected in the p tag, this seems the odd one out.  If join(',') is used instead of join(', ') then it's hard to figure out what is wrong as the test checks the exact format of the text and there is no feedback on what the issue is.
At least two people have been caught out so I can't see the harm in adding more specific text?
I don't mind doing the change myself

@peterjgrainger if you want to do the changes, you’ll have to do it in the “next” branch as that is where the curriculum contents is currently.

Added PR, let me know if I've done everything right!

Closing, as the issue got resolved in https://github.com/freeCodeCamp/freeCodeCamp/pull/18279


Update PF react to latest

Description
Just updates PF4 to latest, it will solve issue with popover

@Hyperkid123

Codecov Report

Merging #90 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #90   +/-   ##
=======================================
  Coverage   48.53%   48.53%
=======================================
  Files          64       64
  Lines         579      579
  Branches       62       62
=======================================
  Hits          281      281
  Misses        265      265
  Partials       33       33

Impacted Files
Coverage Δ

src/SmartComponents/ProviderPage/providerForm.js
56.66% <ø> (ø)
:arrow_up:

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 2482f8c...0cd9d00. Read the comment docs.

@rvsia while you are at it i think you should add some spacing between the icon and the text.


graphql-dynamodb-transformer add check of model inputs in request mapping template

Thanks to GraphQl model our object are typed.
It would be great that these types are checked in the request mapping template of mutations before saving anything in database.
The transform of @model should also generate these types checking in the request mapping template.

It looks to be already implemented my bad.
  #set( $condition.expressionValues = {} )
  #set( $conditionFilterExpressions = $util.parseJson($util.transform.toDynamoDBConditionExpression($context.args.condition)) )
  $util.qr($condition.put("expression", "($condition.expression) AND $conditionFilterExpressions.expression"))
  $util.qr($condition.expressionNames.putAll($conditionFilterExpressions.expressionNames))
  $util.qr($condition.expressionValues.putAll($conditionFilterExpressions.expressionValues))

https://docs.aws.amazon.com/appsync/latest/devguide/resolver-mapping-template-reference-dynamodb.html#aws-appsync-resolver-mapping-template-reference-dynamodb-condition-expressions


Refactor parsing to be owned by processors

What changes were proposed in this pull request?

How was this pull request tested?

Developer's Certificate of Origin 1.1
   By making a contribution to this project, I certify that:

   (a) The contribution was created in whole or in part by me and I
       have the right to submit it under the Apache License 2.0; or

   (b) The contribution is based upon previous work that, to the best
       of my knowledge, is covered under an appropriate open source
       license and I have the right under that license to submit that
       work with modifications, whether created in whole or in part
       by me, under the same open source license (unless I am
       permitted to submit under a different license), as indicated
       in the file; or

   (c) The contribution was provided directly to me by some other
       person who certified (a), (b) or (c) and I have not modified
       it.

   (d) I understand and agree that this project and the contribution
       are public and that a record of the contribution (including all
       personal information I submit with it, including my sign-off) is
       maintained indefinitely and may be redistributed consistent with
       this project or the open source license(s) involved.

I think more functionality should be in a component and that's the center of this stuff.  If components were more stateful, then subsequent requests would avoid additional (and expensive) fetch/parse operations.

In order to test the Airflow component split, an extra operator has to be added to airflow_component_catalog.json.
I've been testing with this one:
"slack-operator": {
  "name": "Slack Operator",
  "location": {
    "url": "https://raw.githubusercontent.com/apache/airflow/1.10.15/airflow/operators/slack_operator.py"
  }
}

Just curious, do KFP and Airflow publish component definitions schemas by any chance?  Seems like there has to be something like that.

Surprisingly, I haven't come across any schemas in researching for the runtime-component-support PRs. KFP and Airflow each have a page or two in their documentation that addresses components/operators and what the general structure of each file should be, but no mention of a schema specifically.


Scoping select to current table to prevent "ambiguous" join queries

Reference: #87
Make sure the createQuery function is scoping the select query to the current table, so when making join queries, we don't end up with ambiguous column reference errors.

Totally missed this, sorry! Released as v2.6.3

It seems like this problem came back. I'm having ambiguous issues on version 5.0.5 of feathers-knex

select count(contact.id) as total from contact left join users on contact.assigned_user_id = users.id where id = (1) - Column 'id' in where clause is ambiguous

My code is
`const query = context.service.createQuery({ query: context.params.query })
query.leftJoin('users', 'contact.assigned_user_id', 'users.id');
query.select('users.firstname as user_firstname')
context.params.knex = query;`


Use jest-preset-stylelint

Use stylelint official Jest preset, which removes the need to have and support testRule.

Thanks!


Feature Request: Add the ability to detect modified sectors like KryoFlux's DTC.exe

My current workflow when dumping requires the use of both GW.exe and KryoFlux's DTC.exe.
I still need to use DTC.exe since it will detect and let me know which tracks on a disk have modified sectors.
It would be great if Greaseweazle had this feature so I could remove DTC.exe from my workflow and not have to deal with it anymore.

That's a good idea. What sort of report do you get from DTC?

This is the output I get from DTC.exe.  Notice on track 00.0, it shows a *H +3 and on track 26.0, that it shows a  *H +1 at the end of the log line.  The +3 and +1 signify the number of sectors in the track it has determined were modified.  The KryoFlux documentation describes this exception as follows:
*H Header extra data was found. Data is hidden in unused parts of the block header. Sector images can’t hold such data; warning only
The only warning that normally affects dumping quality is *T. Another one is *H, which is usual for modified data or protection, but sometimes (very rarely) it happens when the data is very hard to read, so the bitcells get delayed. You will always see *H on XROM protected disks and always see *H on modified tracks.
It would be great if GW.exe went one step further and let us know exactly which sectors were detected as modified instead of just providing a count.
KryoFlux DiskTool Console, v3.00_Win64, uiv.1, Apr 15 2018, 23:44:54
(c) 2009-2018 KryoFlux Products & Services Ltd.
Developed by The Software Preservation Society, www.softpres.org
Licensed for private, non-commercial use only.

Stream file: 3-D Helicopter Simulator (1989) (v2.0BH) (360K) [M 0.0,26.0]\track

00.0    : MFM: OK*, trk: 000, sec: 9, *H +3
00.1    : MFM: OK, trk: 000, sec: 9
01.0    : MFM: OK, trk: 001, sec: 9
01.1    : MFM: OK, trk: 001, sec: 9
02.0    : MFM: OK, trk: 002, sec: 9
02.1    : MFM: OK, trk: 002, sec: 9
03.0    : MFM: OK, trk: 003, sec: 9
03.1    : MFM: OK, trk: 003, sec: 9
04.0    : MFM: OK, trk: 004, sec: 9
04.1    : MFM: OK, trk: 004, sec: 9
05.0    : MFM: OK, trk: 005, sec: 9
05.1    : MFM: OK, trk: 005, sec: 9
06.0    : MFM: OK, trk: 006, sec: 9
06.1    : MFM: OK, trk: 006, sec: 9
07.0    : MFM: OK, trk: 007, sec: 9
07.1    : MFM: OK, trk: 007, sec: 9
08.0    : MFM: OK, trk: 008, sec: 9
08.1    : MFM: OK, trk: 008, sec: 9
09.0    : MFM: OK, trk: 009, sec: 9
09.1    : MFM: OK, trk: 009, sec: 9
10.0    : MFM: OK, trk: 010, sec: 9
10.1    : MFM: OK, trk: 010, sec: 9
11.0    : MFM: OK, trk: 011, sec: 9
11.1    : MFM: OK, trk: 011, sec: 9
12.0    : MFM: OK, trk: 012, sec: 9
12.1    : MFM: OK, trk: 012, sec: 9
13.0    : MFM: OK, trk: 013, sec: 9
13.1    : MFM: OK, trk: 013, sec: 9
14.0    : MFM: OK, trk: 014, sec: 9
14.1    : MFM: OK, trk: 014, sec: 9
15.0    : MFM: OK, trk: 015, sec: 9
15.1    : MFM: OK, trk: 015, sec: 9
16.0    : MFM: OK, trk: 016, sec: 9
16.1    : MFM: OK, trk: 016, sec: 9
17.0    : MFM: OK, trk: 017, sec: 9
17.1    : MFM: OK, trk: 017, sec: 9
18.0    : MFM: OK, trk: 018, sec: 9
18.1    : MFM: OK, trk: 018, sec: 9
19.0    : MFM: OK, trk: 019, sec: 9
19.1    : MFM: OK, trk: 019, sec: 9
20.0    : MFM: OK, trk: 020, sec: 9
20.1    : MFM: OK, trk: 020, sec: 9
21.0    : MFM: OK, trk: 021, sec: 9
21.1    : MFM: OK, trk: 021, sec: 9
22.0    : MFM: OK, trk: 022, sec: 9
22.1    : MFM: OK, trk: 022, sec: 9
23.0    : MFM: OK, trk: 023, sec: 9
23.1    : MFM: OK, trk: 023, sec: 9
24.0    : MFM: OK, trk: 024, sec: 9
24.1    : MFM: OK, trk: 024, sec: 9
25.0    : MFM: OK, trk: 025, sec: 9
25.1    : MFM: OK, trk: 025, sec: 9
26.0    : MFM: OK*, trk: 026, sec: 9, *H +1
26.1    : MFM: OK, trk: 026, sec: 9
27.0    : MFM: OK, trk: 027, sec: 9
27.1    : MFM: OK, trk: 027, sec: 9
28.0    : MFM: OK, trk: 028, sec: 9
28.1    : MFM: OK, trk: 028, sec: 9
29.0    : MFM: OK, trk: 029, sec: 9
29.1    : MFM: OK, trk: 029, sec: 9
30.0    : MFM: OK, trk: 030, sec: 9
30.1    : MFM: OK, trk: 030, sec: 9
31.0    : MFM: OK, trk: 031, sec: 9
31.1    : MFM: OK, trk: 031, sec: 9
32.0    : MFM: OK, trk: 032, sec: 9
32.1    : MFM: OK, trk: 032, sec: 9
33.0    : MFM: OK, trk: 033, sec: 9
33.1    : MFM: OK, trk: 033, sec: 9
34.0    : MFM: OK, trk: 034, sec: 9
34.1    : MFM: OK, trk: 034, sec: 9
35.0    : MFM: OK, trk: 035, sec: 9
35.1    : MFM: OK, trk: 035, sec: 9
36.0    : MFM: OK, trk: 036, sec: 9
36.1    : MFM: OK, trk: 036, sec: 9
37.0    : MFM: OK, trk: 037, sec: 9
37.1    : MFM: OK, trk: 037, sec: 9
38.0    : MFM: OK, trk: 038, sec: 9
38.1    : MFM: OK, trk: 038, sec: 9
39.0    : MFM: OK, trk: 039, sec: 9
39.1    : MFM: OK, trk: 039, sec: 9
40.0    : MFM: <unformatted>
40.1    : MFM: <unformatted>
41.0    : MFM: <unformatted>
41.1    : MFM: <unformatted>

Enjoy your shiny new disk image!
Please consider helping us to preserve media and continue development:
www.softpres.org/donate

Since gw.exe already outputs a nice full map of all of the sectors, maybe put something like an M on the grid when a modified sector is detected.

Okay this is mostly an exercise in plumbing I think. Definitely doable!

hi no news for this enhancement ?

I feel like chipping in with a "watch out" here - if you don't care for the gory details then skip to the end for the issue :)
Back when I was actively working on DiscFerret and the Merlin disc analyser/decoder, I was looking at how this could be done (I wondered how SPS did it but never looked at their code, only the public descriptions - it would have been silly to encumber the DiscFerret code).
I came up with two ways to identify modification - but they only work on commercially-duplicated (using a Copypro, Trace or similar single-pass copier):

Different gap width between the sector header and sector data.
Timing change in the sector data

The gap width (number of bits of gap) should be a reasonable indicator. It works because a single-pass disc duplicator doesn't do separate format and write steps. Instead, it builds an image of the track, writes it, then reads the data back and verifies it. This all happens in two rotations of the disc.
The issue is that this would only work with discs which were made on a single-pass duplicator. If someone had created the discs on their Acorn, Amiga or whatever - it'll give a false "modified" indication. At the time, I was dealing with Acorn discs and most of them were duplicated on physical machines.
The (partial) solution I came up with was to look for differences in motor speed between the drives. The way I did it was to figure out the nominal bit cell width, normalise each measurement to that (divide by 1.0, 1.5 or 2.0), then calculate the timing error vs. ideal in PPM. In theory all sectors written with the same drive (i.e. machine) should be written at the same speed.
The error terms (drive figures are from http://www.techtravels.org/wp-content/uploads/pefiles/SAMSUNG-SFD321B-070103.pdf) boil down to:

+/- 50ppm - disc controller clock crystal
+/- 1.5% LSV speed variation (= +/- 15,000 ppm)
+/- 1.5% ISV speed variation (= +/- 15,000 ppm)

ISV is instantaneous speed variation. LSV is long-term speed variation. Note that the Sony MPF-920 quotes +/- 3% ISV.
The ISV should (in theory) average out over the sector, leaving the LSV - which is the error in calibration for that particular drive. In actuality what's measured is the ISV+LSV of the reading drive, and the ISV+LSV of the writing drive.
If desired, the LSV of the reading drive can be measured (index pulse timing) and subtracted from the measurement.
What's left over is the LSV(write) + ClockError(write) + LSV(read) + ClockError(greaseweazle).
The clock error is only 100ppm and fades into the noise of the potentially 30,000 PPM motor speed error.
Once you've got the sector and sector header timing (and gap timings if you want to do that), you can analyse the timings to find out:

Written with a single pass duplicator and not modified later: All sectors, headers, and gaps are the same speed. Gaps are also consistent. Only one write splice, near the index pulse.
Formatted in the factory then written on a computer: Formatted elements (gaps and headers) have one timing value. Some or all sectors have different timing values.
Formatted and written on the same computer: Formatted elements (gaps and headers) and sectors have the same or similar timing. Evidence of write splices or gap lengths which don't match the format.
Data modified on a different computer: At least one sector with different timing to others on the disc.

Identifying a factory formatted (or duplicated) disc might be tricky, but I'd expect the motor speed to be pretty much dead on. They would have been checked and calibrated - if the distribution house cared about quality. There's also a chance there might be duplication metadata (TRACEBACK or similar) on track 80.


issue fix #349 and #375

Issue #349 Random ball throwing functionality added. Velocity and position are randomized.

https://user-images.githubusercontent.com/126502226/227988098-94fb8017-37ba-41d0-b7e2-227ac498609c.mov

Fixed issue #375 . Added the command to the extension context.

https://user-images.githubusercontent.com/126502226/227988170-967484f3-74c9-4ebf-a51d-2c920fb409e8.mov

will resubmit


Self discovery of annoted workers finds and runs workers from Examples folder

If I use WorkflowTaskHost.CreateWorkerHost() in my own worker project the self discovery of annoted workers (those using attribute [WorkerTask]) finds and runs workers from Examples folder placed directly in sdk project. It would be best to move the whole Examples folder to existing csharp-examples project, it doesn't make sense to be placed in core sdk library. Thank you.

I also encountered this problem. My job worker broke after updating to 1.0.15.


Gpo function add

Added the function to extract all the information related to GPO:
Final result:

Best regards!

This looks like a duplicate implementation of #103?


List the Settings page in the navbar dropdown menu

Changes
This PR makes accessing the settings page accessible to the students by displaying a link in the navbar dropdown menu.
Screenshot

Testing

Click on the Settings link
Make sure it's working

Related issues
#1629

What do you guys think? Is it the right location? Should be named differently?


[Forwardport 2.8] integration test suite: unbreak f-string

Forwardport of https://github.com/rancher/rancher/pull/43580

ping @bmdepesa


Codon table generation awkward

It is kind of awkward generating codon tables. For example, an external user would input something like this -
seq := poly.ReadGbk("data/pichia_chr2.gb")
ct := seq.GetOptimizationTable(poly.GetCodonTable(11))

It might be a lot easier to give the sequence as a parameter for generating the table, for example
seq := poly.ReadGbk("data/pichia_chr2.gb")
ct := poly.GetCodonTable(seq, 11)

This change would be mildly more ergonomic, and clearer to the end users.

The confusion comes in because there aren't any "optimization tables", there are only codon tables, they just each have a slightly different structure.

You're right and I like this better syntactically. Any reason you can think of why we shouldn't do this @Koeng101?

Or rather. Things we should be aware?

Yea so the biggest one is something around this - https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3115271/
You can express two different codon tables from a single genbank file. Though probably for historical reasons, the translation table is actually defined on the gene level, NOT the file level - https://www.ncbi.nlm.nih.gov/nuccore/CP060121.1
In addition, our code doesn't properly pick up start codon biases, which code for M, but can easily be codons like GTG or TTG in many E coli. It might be time to rethink this code?

@TimothyStiles Is this issue close ? I see that the method GetCodonTable is already there in the codebase


Assign image artifacts properly in Tinkerbell bundle

Possible fix for tinkerbell Helm chart issues.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/close


Best Arabic Trained Data feedback

Hi everybody
Big improvement in recognizing Arabic text with heavy vowel diacritics but hope to give option to strip out the vowel diacritics in the output.
but unfortunately there is a bug in output letters map. Some non standard Arabic characters used in the output which will be okay for printing but not for storing document digitally, it will be considered as mistake because we use standard Arabic keyboard to write and search.
Some of these letters are
used         ی               ک
right one     ي            ك
I believe if we run find and replace we could bypass this issue

the same problem ?

Please check with traineddata from tessdata_fast and post whether you face same issue with both ara and Arabic traineddata.

No, the traineddata from tessdata_fast does not have this issue.


Question about the rescue game.

Hi, from reading the paper《Coach-Player Multi-Agent Reinforcement Learning for Dynamic Team Composition》, I became very emotional about the rescue mission. But I can't find the location of this environment. If this repository does not contain the codes of the rescue game,  could you open-source this environment?

Hello author, I am also very interested in rescue environment, could you please open source this environment?


Provide a system configuration with a default port setting

As mentioned in https://github.com/nornforge/norn/blob/main/doc/serialport.md the only robust way to distinguish the ports when multiple Picos are used is the link in /dev/serial/by-path folder. The idea is to have a config file which provides support for multiple devices. Maybe an environment Variable is also feasible for testing

fixed in: #6


Retain the pull secret information

Can we retain the pull secret information after a crc delete? The idea is to persist the pull secret after a successful start of cluster automatically so that we do not need to send the user to pull secret download as often.

Use crc config set pull-secret-file:
https://github.com/code-ready/crc/blob/master/cmd/crc/cmd/config/config.go#L18
... When implementing the config dialogs for Windows and macOS we weill consider using trhe native keystores: #1104

Marking as duplicate of #1104


0.11.x TF not supported by resource manager, and Error code: InvalidParameter(400)

Hello Jeevan,

I was trying your example deployment from this blog: https://blogs.oracle.com/cloud-infrastructure/post/create-your-own-web-presence-with-oracle-cloud-infrastructure-using-wordpress
From the readme.md, https://github.com/oracle-quickstart/oci-arch-wordpress-mds/tree/master/micro-deployment, I chose 'Deploy to Oracle Cloud'
It takes you to the console, https://cloud.oracle.com/resourcemanager/stacks/create?region=us-phoenix-1&zipUrl=https%3A%2F%2Fgithub.com%2Foracle-quickstart%2Foci-arch-wordpress-mds%2Freleases%2Flatest%2Fdownload%2Foci-wordpress-micro-stack-latest.zip
Check the box to accept oracle terms
You will see a yellow warning label: '0.11.x is no longer supported.'
Followed by a red error bar at the lower part of the page, with the following message: (400, InvalidParameter, false) https://github.com/oracle-quickstart/oci-arch-wordpress-mds/releases/download/v1.4/oci-wordpress-micro-stack-latest.zip (opc-request-id: csidc744bfac4a8ea4881af1729c04f8/e6064b84d0e1457b8644a2d2bf515da5/B7097997E9BD123D977D8762EBEC41A5) Request ID: csidc744bfac4a8ea4881af1729c04f8/e6064b84d0e1457b8644a2d2bf515da5/F8AB00FEC2B439EA4C91AC48E12B9E8E. Timestamp: Wed, Sep 29, 2021, 04:40:53 UTC. Endpoint: https://cloud.oracle.com/resourcemanager/stacks/create. Error code: InvalidParameter(400).
For steps 4, 5, 6 please see the image below:

I have added ORM stack zip files to the latest release. Now deploy button for micro-deployment should work fine.


Prepare for the P3 conversion

Fixes #46

This change is

Reviewed 15 of 16 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Review status: :shipit: all files reviewed at latest revision, all discussions resolved, all commit checks successful.

Comments from Reviewable


Use ruby-version instead of version

While merging an automated bundle update, I seen an annoated beta message below the files section that pointed out we should be using ruby-version not version when using the actions/setup-ruby@v1 container.

See https://github.com/Homebrew/homebrew-bundle/pull/568/files for the message.

Thanks @jacobbednarz, good catch!


Container list page is not working

Rancher versions: Wagyu (master 7/25)
Steps to Reproduce:

Create a new environment
Add host
Create a service and add a new stack
Click on Container list button to get out of Stack view

Results:  Can't see a container list, I can never leave the stack view

Version - master 2.0 8/2
Verified fixed


Fix: Fixed crash that would occur when clicking browse on properties customize page

Resolved / Related Issues
Items resolved / related issues by this PR.

Closes #10193

Validation
How did you test these changes?

[x] Built and ran the app

I'll try to find a faster way to retrieve the window handle

What was the issue?

What was the issue?

It was an issue with WinUI3 and windows APIs more details here

I'll try to find a faster way to retrieve the window handle

I changed the code, now it's slightly faster but much more readable

LGTM code-wise.

Did you also test the behavior?

Did you also test the behavior?

I did, it solves the crash for me.


[WIP] Prefer standard where over AREL

It doesn't look like this is going to work with the tag filtering I need to do

So just as a recap, did this fix the issue with the acts_as_tenant gem?
Also curious what about the filtering would make a difference between these implementations.


fixes typos and corrects links in the minikube guide

This change is

@sameersbn do you know which issues it fixes ? Can you list here.

@sebgoa the pr fixes issues I noticed while referring to the minikube document. It does not target any open issue from the issue board.

oops.. accidentally hit the close button.
re-submitted in #4051


meta data addition

New view

Added a new api endpoint:
url: http://localhost:3000/api/providers
method: Post
Request.payload:
{
    "action": "meta_data",
    "resource": {
       "name": "Molecule",
       "exp_date":  {"value":"1.12.2016", "field_type": "DateTime"},
       "expected_num_of_nodes": {"value":2, "field_type": "Integer"},
       "sales_force_acount": {"value":"ADF231VRWQ1"}
    }
}

depends on: https://github.com/ManageIQ/manageiq/pull/10896

So, I think we already have methods for adding and removing custom attributes (perhaps not via the REST API).  I'm not sure why we need to re-add that under a new name of "meta data"

an action name of  "meta_data" by itself is very strange.  Since it does a full replacement (but no deletes?) I would expect an action word in the front like "update_metadata"
Also,

metadata is a single word, so shouldn't be broken up
even so (as mentioned above) I think it should say custom_attributes to be consistent with usages in the UI.

Sorry, one more thing...we also have the concept of different types of custom_attributes as handled by the "source" column.  So ManageIQ can have it's own custom_attributes which I think uses the MIQ source, and the EMS can have theirs which I think is the EMS source, with possibilities of other sources.  I think you might want to limit which source you want to show in the UI.  Again, I believe this is handled on the VMs screen, but possibly others...I'd have to check to be sure

You can see this on the VM screen by editing any VM in the UI and setting the Custom Identifier field to value.

It will show up in the Custom Attributes section of the VM Summary screen as custom_1

@Fryguy Made a round of repairs please have a second look :)

Tests are failing due to dependency on #10896

@alongoldboim can you fix tests?
@miq-bot assign alongoldboim

Tests are failing due to dependency on #10896
@simon3z

@alongoldboim I don't think that the section should be left to the user to decide (he could push malicious values). The section must be enforced.

@simon3z OK, removed user input, its now auto-set to metadata.

@imtayadeway Have another look please :)

@imtayadeway @lpichler  Have another look please.

👍 LGTM (I added some comments to #10896) which this depends on.

@gtanzillo  #10896 was merged, can we get this in?

@miq-bot assign gtanzillo

@imtayadeway Can you review based on your requested changes?  thanks!

@alongoldboim this is looking good. I have just a few comments above but it's mostly there. @abellotti anything to add?

Other than edits here does this PR support custom attributes on providers ?   We support the capabilities on vms as per https://github.com/ManageIQ/manageiq_docs/blob/master/api/reference/custom_attributes.adoc  should also work on /api/providers/:id/custom_attributes for consistency.  Thanks.

@abellotti If I understood correctly I think this action is supported in current implementation?

@alongoldboim This is looking real good.  Nice enhancement to the API !!
Minor changes noted above.  Thanks!!

@abellotti If I understood correctly I think this action is supported in current implementation?

Are there tests to support that?

@abellotti fixed minor comments, @imtayadeway Yes the current tests are supporting add/edit/delete.
@gtanzillo Think this one can get merged if there are no more comments.

@miq-bot add_label euwe/yes

Hi @alongoldboim thanks for the updates. could you take of the rubocop warnings ?  Thanks.

👍 LGTM. Will merge once the rubocops are addressed.

@gtanzillo Rubocop is happy now.

Euwe Backport details:
$ git log
commit a16aedc889a2bec9e37a2530b530f46483b31d33
Author: Gregg Tanzillo<EMAIL_ADDRESS>Date:   Thu Oct 6 11:08:03 2016 -0400

    Merge pull request #10897 from alongoldboim/provider_meta_data

    Adding custom attributes to provider (UI + API)
    (cherry picked from commit 46277eefa4ea925a2607628c7815fbc5a8f214c0)


Chapter3/homework/5

Here's the solution for the exercises. I tried reusing knowledge we've learned throughout this chapter (generics, etc.).

Looks good


V2 status support summary table

As API V2 is under development by Twitter, some new API will appear, and developers would like to know which of them are already supported by this library.
I think there should be some summary table

Hi,
Currently my only solution is a little bit raw but you can just check the ITwitterClientV2 interface containing all the V2 implemented methods. By the way I think that all the available V2 endpoints are implemented on the library.
But yes a table can be more user friendly, I'll check that.


Set Up SAP HANA Cloud for Kyma

Tutorials: https://developers.sap.com/tutorials/btp-app-kyma-hana-cloud-setup.html
Hi,
At the second section this tutorial says:
Copy the folder scripts from templates/kyma-add-helm-chart to your project root folder.
Where can you find templates/kyma-add-helm-chart ? Is this supposed to be a link?

Hi @HamzaM1 ,
Before you work on this tutorial you would have followed the prerequisite tutorials mentioned. In the prerequisites there is a tutorial called Create a Directory for Development. In this tutorial you would have downloaded the tutorial into a folder called tutorial and the templates folder is present there.
Best regards,
Manju

I see. My fault for not checking. Thanks!


Add mamba

Mamba currently does not support XDG, added information to point to the issue

Thank you!


Understanding React's New Context API

Proposed title of article
Understanding React's New Context API
Proposed article introduction
Given the various front-end frameworks, it tends to be challenging to know which is best to choose. But with the new  React JS framework developed by Facebook, which applies virtual DOM and JSX makes it one of the most reliable and powerful frameworks.
Key takeaways

What is Props and States
What the Context API is solving

Article quality
It shows how simple prop drilling solution that can scale decently
References
N/A

Good afternoon and thank you for submitting your topic suggestion.
Your topic form has been entered into our queue and should be reviewed (for approval) as soon as a content moderator is finished reviewing the ones in the queue before it.

Good afternoon and thank you for submitting your topic to the EngEd program.
After some careful consideration, it struck us that this topic may be a bit over-saturated throughout other blog sites and official documentations.
We typically refrain from publishing content that is covered widely on the net or other blogs. We're more interested in original, practitioner-focused content that takes a deeper dive into programming-centric concepts.
But in order to approve the topic, it has to serve value to the larger developer community at large.
An option and a great way to write this as an in-depth article and make it more add value to the greater developer community at large would be to walk the reader through the USE of methods and functions by building a unique, different, useful project.

We would love to learn your thought process behind the solution you arrived at using these concepts and topics.

That way a developer could see them in action.
As mentioned above - we believe this topic is widely covered on other blog sites.
The best way for students to build a great portfolio is by building what does not exist and what can provide the most value.


Authorization-Model-Id is required when using default-model

Hello together,
I want to have a check if all the types are available in the schema, before starting the service (Liveness/readiness check).
When I Inject the AuthorizationModelClient, it does not work. Every time, it throws the error message below.
If I use the Inject in request-scope later on, the logic works fine.
If I create tests and use the dev-service, it works fine! It's just not working, whether build and deployed or using the official openfga docker container!
Given:
%dev.quarkus.openfga.url=http://localhost:8081
%dev.quarkus.openfga.store=test
Caused by: io.quarkiverse.openfga.client.model.FGAValidationException: invalid ReadAuthorizationModelRequest.Id: value does not match regex pattern "^[ABCDEFGHJKMNPQRSTVWXYZ0-9]{26}$"
JavaClasses:
fga.zip

Same problem


Cannot retrieve balance changes: Error checking transaction input objects

sui_getTransactionBlock: Cannot retrieve balance changes
RPC request exception, Request transaction cannot obtain balance change, Actually, This transaction has a change in balance.
request:
curl -X POST 'https://fullnode.testnet.sui.io:443' \ -H 'Content-Type: application/json' \ -d '{"jsonrpc":"2.0","id":1,"method":"sui_getTransactionBlock","params": ["6DNWZoxKc8Dbbsm6eqRhowk8YUV155SqJ3bLDkGVa9XW",{"showBalanceChanges": true}]}'
response:
{"jsonrpc":"2.0","result":{"digest":"6DNWZoxKc8Dbbsm6eqRhowk8YUV155SqJ3bLDkGVa9XW","timestampMs":"1688745043522","checkpoint":"7066825","errors":["Cannot retrieve balance changes: Error checking transaction input objects: ObjectNotFound { object_id: 0x2f86921bf880424bf63830f1bea58a0e8b3be9255d0c495f08fbd68bfa1bf8f1, version: Some(SequenceNumber(6971160)) }"]},"id":1}

The digest in your curl query does not exist on testnet: 6DNWZoxKc8Dbbsm6eqRhowk8YUV155SqJ3bLDkGVa9XW
Can you provide the right digest?

transactionDigest:"3V1JNdLQfv5ynY4UqL1K8VwpnPUDzwqriQbdKEofww7K"


geoip:private setting block google.com

Please read the instruction and answer the following questions before submitting your issue. Thank you.
Please answer all the questions with enough information. All issues not following this template will be closed immediately.
If you are not sure if your question is truely a bug in V2Ray, please discuss it here first.

What version of V2Ray are you using (If you deploy different version on server and client, please explicitly point out)?
V2Ray 4.22.1 (V2Fly, a community-driven edition of V2Ray.) Custom (go1.13.5 linux/amd64)

What's your scenario of using V2Ray? E.g., Watching YouTube videos in Chrome via Socks/VMess proxy.
Google Chrome visit www.google.com

What did you see? (Please describe in detail, such as timeout, fake TLS certificate etc)
Cannot open google,
there are block www.google.com message in server log

if remove these default setting from server config file:
    "rules": [
       {
        "type": "field",
        "ip": [
          "geoip:private"
        ],
        "outboundTag": "blocked"
      }
    ]

this will fix this issue.

What's your expectation?

Please attach your configuration file (Mask IP addresses before submit this issue).

Server configuration:
Client configuration:
    // Please attach your client configuration here.

Please attach error logs, especially the bottom lines if the file is large. Error log file is usually at /var/log/v2ray/error.log on Linux.

Server error log:
    // Please attach your server error log here.

Client error log:
    // Please attach your client error log here.

Please attach access log. Access log is usually at '/var/log/v2ray/access.log' on Linux.

    // Please attach your server access log here.

Other configurations (such as Nginx) and logs.

If V2Ray doesn't run, please attach output from --test.

The command is usually /usr/bin/v2ray/v2ray --test --config /etc/v2ray/config.json, but may vary according to your scenario.

If V2Ray service doesn't run, please attach journal log.

Usual command is journalctl -u v2ray.
Please review your issue before submitting.

看看error log啊

if add a allow rule before the "geoip:private" rule
{
        "domain": [
          "google.com",
          "apple.com",
          "oppomobile.com"
        ],
        "type": "field",
        "outboundTag": "allowed"
      },

Can also fix this problem.
Server logs show that "apple.com", "oppomobile.com" are sometimes blocked, and an allow rule needs to be added for them.

日志稍等...

https://github.com/v2ray/geoip/blob/286f746b3a187c2b9ed2b3a7c1991ed43d3cb915/main.go
localIPs = []string{
"<IP_ADDRESS>/8",
"<IP_ADDRESS>/8",
"<IP_ADDRESS>/10",
"<IP_ADDRESS>/8",
"<IP_ADDRESS>/16",
"<IP_ADDRESS>/12",
"<IP_ADDRESS>/24",
"<IP_ADDRESS>/24",
"<IP_ADDRESS>/24",
"<IP_ADDRESS>/16",
"<IP_ADDRESS>/15",
"<IP_ADDRESS>/24",
"<IP_ADDRESS>/24",
"<IP_ADDRESS>/4",
"<IP_ADDRESS>/4",
"<IP_ADDRESS>/32",
"::1/128",
"fc00::/7",
"fe80::/10",
}
geoip:private 只有这些啊

抱歉，我前几天遇到这个问题，今天再试又好了。我再观察观察。

顶楼更新了一下，增加了服务器配置文件和访问日志
是跟我增加block 色情站点有关系，增加上就回block google 等网站
必须再在前面加
···
{
"domain": [
"google.com",
"apple.com",
"oppomobile.com"
],
"type": "field",
"outboundTag": "allowed"
},
···
才行，否则就会block google apple.com 等

顶楼更新了一下，增加了服务器配置文件和访问日志
是跟我增加block 色情站点有关系，增加上就回block google 等网站
必须再在前面加
···
{
"domain": [
"google.com",
"apple.com",
"oppomobile.com"
],
"type": "field",
"outboundTag": "allowed"
},
···
才行，否则就会block google apple.com 等

le.com
这条规则会匹配google.com
所以block了
用domain:le.com 替代
纯字符串: 当此字符串匹配目标域名中任意部分，该规则生效。比如"sina.com"可以匹配"sina.com"、"sina.com.cn"和"www.sina.com"，但不匹配"sina.cn"。
子域名 (推荐): 由"domain:"开始，余下部分是一个域名。当此域名是目标域名或其子域名时，该规则生效。例如"domain:v2ray.com"匹配"www.v2ray.com"、"v2ray.com"，但不匹配"xv2ray.com"。

哦，明白了，原来是这样的，多谢大侠！


Refactor CI script

I think should do all tests in order to expose all existing problems except when configure/build fail.

Let me think about this a little bit. I'm a little hesitant because I find Travis CI to have too long of a turnaround time these days (30+ minutes) and a small issue can drag on forever and slow down iteration. While exposing more errors is good, I find that halting immediately tend to give a fast feedback to the user and when you scroll down to the end of the log that's where the error is instead of needing to scroll up the massive amount of log spam from successful tests and search around.

Hi @ichizok is this still work in progress? I noticed you renamed the title to "[WIP]" a while ago but wondering if there are still changes that need to go in.

There are the below major factors causing tests take long time:
brew update
In all envs. This can resolve to use directory cache.
Upgrading brew packages
Especially in xcode7.3: packages are built from their sources, not using bottles.
Thus I think should enable the language interfaces (if_xxx) only in xcode10.2, or at least disable in xcode7.3.
Test_writedelay (test_options.vim) on GUI
Except in xcode7.3.
https://travis-ci.org/macvim-dev/macvim/builds/555492863
xcode7.3:
Executed Test_writedelay() in   1.871324 seconds

xcode 8.3:
Executed Test_writedelay() in 205.001438 seconds

xcode9.4:
Executed Test_writedelay() in 272.267539 seconds

xcode10.2
Executed Test_writedelay() in 455.950352 seconds

These are caused by the behavior (bug?) of set fullscreen.
In test_options.vim Test_set_values does set fullscreen, set nofullscreen, and set fullscreen& but actual screen remains full-screen after first set fullscreen therefore redrawing screen spends long time when with set writedelay.

Thank you, please merge.


Sbt release

First step in the SBT release process. With a local pgp installation it is now possible to deploy to maven central from sbt command line.

👍  @NRBPerdijk After you've reviewed it, feel free to merge this pull request


Windows problems with cookies on chrome

When using selenium grid extras on windows 7 with chrome my test blows up because it cannot access the cookies of the browser. If using the same version of chrome (latest) and the chromedriver (latest), and running the vanilla selenium-standalone-server jar my test works. Is Selenium Grid Extras doing something strange when it starts the jar like passing in a flag or something?

@eelessam There is nothing special when starting the nodes. It uses the JVM arguments (mine for OSX):
-Dwebdriver.chrome.driver=/tmp/webdriver/chromedriver/chromedriver_2.16_32bit
Are you still having this issue? What version of SeleniumGridExtras (1.10.0 is the latest). What version of Chromedriver? What version of Chrome?

Closing since no response after > 6 months. Please post back or open a new issue if this is still a problem.
Thank you.


Password requirements aren't known

Fix issue where the password/passphrase requirements aren't known until after the dialog window has closed.

Password/passphrase requirements are now shown when creating your account, profile, or changing your profile passphrase.


Photos not centering when info panel is opened

Horizontal photos are not centering when info panel is opened:

It is working ok with vertical photos:

Also, after opening info panel and switching to next photo, there is a fragment of next photo visible at the left and sometimes right, this does not occur when I don't touch info panel.

Which browser are you using?

Chrome  87.0.4280.88, without any adblockers

Similar problem on phone, this time photo is very small (white box) after closing info panel

I pushed a new docker image. It should work now. Does it resolve your issue?

Yes 😀


Reorganize .graphql files

No functionality/API changes, just cleaning up.
I'm about to add new functionality to the annotation graphql schema and decided it was time to clean up the remaining declarations from the left-over schema.graphql file.

@LachlanStuart probably .circleci/config.yml needs to be updated to fix test-webapp job

@intsco Thanks, I hadn't noticed CircleCI failed. I had a suspicion that there was a 2nd place I had to update, but couldn't find anything with Find in Files.
I've fixed the issue and added comments linking the two places that should be updated at the same time.


RxJS missing from blueprint

temporary work around is to add RxJS with bower and import it directly in your Brocfile.js

Fixed in https://github.com/Netflix/ember-nf-graph/pull/56


Set runAsUser to 0 for bundle push step

This resolves the "Unsuccessful cred copy" warning.
warning: unsuccessful cred copy: ".docker" from "/tekton/creds" to "/tekton/home": unable to open destination: open /tekton/home/.docker/config.json: permission denied

/test build-definitions-pull-request


[Event Request] codeunit 5760 "Whse.-Post Receipt" PurchaseLineSkipModify

                                if "Source Document" = "Source Document"::"Purchase Order" then begin
                                    ModifyLine := PurchLine."Qty. to Receive" <> 0;
                                    // DINNL <<
                                    DINIsHandled := false;
                                    DINPurchaseLineSkipModify(PurchLine, DINIsHandled);
                                    if not DINIsHandled then
                                        // DINNL >>
                                    if ModifyLine then
                                            PurchLine.Validate("Qty. to Receive", 0);
                                end else begin
                                    ModifyLine := PurchLine."Return Qty. to Ship" <> 0;
                                    // DINNL <<
                                    DINIsHandled := false;
                                    DINPurchaseLineSkipModify(PurchLine, DINIsHandled);
                                    if not DINIsHandled then
                                        // DINNL >>
                                    if ModifyLine then
                                            PurchLine.Validate("Return Qty. to Ship", 0);
                                end;

[IntegrationEvent(false, false)]
local procedure DINPurchaseLineSkipModify(PurchaseLine: Record "Purchase Line"; var IsHandled: Boolean)
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.