Point of Sale app

🛠 Issue (Number)
#1960

Closes #
Description
Main dashboard view of POS (Point of Sale) application for restaurant or cafe. The design is not finished yet, and will be continued.
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist:

[x] I have made this from my own
[x] I have taken help from some online resourses
[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] The title of my pull request is a short description of the requested changes.

ATTACH SCREEN-SHOTS / DEPLOYMENT LINK

Make it responsive


Feature request: the maintenance mode.

It would be great to have a feature to turn on the maintenance mode when only admins could enter the server.
Thank you.

Simply enable whitelist and add your admins to this whitelist.

Using the whitelists is inconvenient -- does it not requires a server reboot?

no @swordin
do /whitelist on and /whitelist add  and /whitelist add ...

no need2reboot

I see, you're right, thank you!

np @swordin


[turborepo] can't find turbo.json schema file in this repository

What version of Turborepo are you using?
1.9.1
What package manager are you using / does the bug impact?
pnpm
What operating system are you using?
Mac
Describe the Bug
https://github.com/vercel/turbo/blob/main/turbo.json#L2
Expected Behavior
https://github.com/vercel/turbo/blob/main/turbo.json#L2
To Reproduce
https://github.com/vercel/turbo/blob/main/turbo.json#L2
Reproduction Repo
No response

It needs to be generated first, you can do that with pnpm --filter=docs schema.
If you haven't run a fresh pnpm install in a bit, make sure you do that as well, we renamed a few of the packages and scripts last week and the binary that generates the schema was renamed so a fresh install is required to put that in the right place.

So, why not publish to https://www.schemastore.org/json/


DOCS Rework to have clear user guide and dev docs.

Part of some work towards a more maintainable userhelp documentation website. Making more useful module specific documentation for user guides and keeping it clean from developer documentation. This userguide directory can then be referenced in the userhelp.silverstripe.org site and the documentation nicely integrated, much easier to maintain and ensures up to date versions are displayed for end users.
Will be using a fork including this PR for an initial launch, and this PR can be used for further discussion (or feel free to accept as is).
I've gone ahead and broken a lot of the docs down and provided indexes. Much of this was migrated from the README which had become very long. REAME now includes key information as per the supported module standard and links through to further documentation for both users and devs.

Happy to have this in once you're happy with the level of detail - or should I say, rather than accept now and make you open a new one later, will leave this open til you want it merged :)

thanks mate. Will keep you posted. The PR isn't a block as we'll use forks until we are happy with the result.

@nyeholt think this is ok to merge


dnf_package bug

Description
It seems that the way Chef is using the DNF internal libraries doesn't get the same data as the CLI.
# dnf list avail testpackage1
Installed Packages
testpackage1.x86_64               20181128-133340                @fb-runtime
Available Packages
testpackage1.x86_64               20181128-133340                @fb-runtime
testpackage1.x86_64               20181202-044213                fb-runtime
testpackage1.x86_64               20181202-063154                fb-runtime
testpackage1.x86_64               20181203-063312                fb-runtime
testpackage1.x86_64               20181203-100514                fb-runtime
testpackage1.x86_64               20181204-063215                fb-runtime

Note the versions there. Now if I use the API chef does:
# /usr/libexec/platform-python
Python 3.6.6 (default, Oct 16 2018, 01:53:53)
[GCC 8.2.1 20180905 (Red Hat 8.2.1-3)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import dnf
>>> s=dnf.subject.Subject('testpackage1')
>>> base = dnf.Base()
>>> base.read_all_repos()
>>> base.fill_sack()
<dnf.sack.Sack object at 0x7fbac8862728>
>>> q=s.get_best_query(base.sack, with_provides=True)
>>> qq=q.available()
>>> x = qq.run()
>>> for i in x:
...   print(i)
...
testpackage1-20181127-063148.x86_64
testpackage1-20181128-063204.x86_64
testpackage1-20181128-133340.x86_64
testpackage1-20181128-133433.x86_64
testpackage1-20181129-063158.x86_64

That means that Chef will bail out with "version not available" in the event we request a version that is not in the latter but is in the former.
Note the difference in versions there.
Chef Version
Chef 13.10.0 - but we've repro'd on 14 as well.
Platform Version
RHEL8 beta

It's worth noting that this may in fact be a RHEL8 or DNF bug... but my best guess is we're using the API wrong.

To clarify, we reproed on the RHEL 8 Beta, not on CentOS

I suspect this got fixed by #8754
New issue would need to get opened if I'm wrong.


About turbo model or lightning model.

Therefore, it is actually difficult to improve the speed of models with very few noise reduction steps, such as turbo or lightning models.

Thanks for your attention to our work.

As the reported result of LCM, in very few steps of generation, our method can reduce ~10% computation cost for a single image. We believe for a model that may be called for billions of times daily, it is still a non-negligible reduction.

We agree with you that it is more challenging to further improve a distilled diffusion model.

However, TGATE is also applicable to the distilling process. Our method can accelerate the generation process of the teacher model, thereby further accelerating the training of the student model.

Last but not least, Tgate is a free lunch without training costs and performance drops, so please try TGATE to save your time and cost.

Thanks for your attention to our work.  As the reported result of LCM, in very few steps of generation, our method can reduce ~10% computation cost for a single image. We believe for a model that may be called for billions of times daily, it is still a non-negligible reduction.  We agree with you that it is more challenging to further improve a distilled diffusion model.  However, TGATE is also applicable to the distilling process. Our method can accelerate the generation process of the teacher model, thereby further accelerating the training of the student model.  Last but not least, Tgate is a free lunch without training costs and performance drops, so please try TGATE to save your time and cost.

Yes, I agree with it.

And pixart-sigma is released, if you have enough time, I hope you can try it.

Thanks for your suggestions. We plan to have a try soon. Stay tuned!

Hello, we have tested our method on PixArt Sigma. It works well. Please see our implementation on diffusers. We will provide a tutorial for this model once it is officially supported by diffusers.


Expand selection

Issue Type: Bug
Selection > Expand Selection doesn't work right. Please see IntelliJ Phpstorm for an example of expected behavior.
 Feature doesn't work, with or without extensions.

Please explain the problem some more with repro steps.
Or see whether your issue is covered by any of the existing Expand Selection issues like https://github.com/Microsoft/vscode/issues/4795

Here's how it is supposed to work:

I think it's tracked by https://github.com/Microsoft/vscode/issues/4795#issuecomment-346622659


fix(demo): add auto as default placement setting

Updated the documentation for tooltips regarding the "auto" placement option which can be used to place the tooltip where it fits if there is not enough space for the initial placement.

Preview environments are getting posted here, as soon as they are ready!


Lite wallet shutting down

Please help, I want to send some ARRR out of my Lite wallet, and as soon as I hit OK in the final step ( confirmation), wallets shuts down: message Crashed Thread:        4  Thread (pooled)
Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY
Termination Reason:    DYLD, [0x4] Symbol missing
Dyld Error Message:
Symbol not found: ____chkstk_darwin

Having same issues, would like some more info regarding this matter. Thank you

Issue with CPU/OS on Mac- too old and too slow, need to re load on Windows
based PC or Mac OS catalina
On Sat, May 1, 2021 at 9:38 AM brandon954 @.***> wrote:

Having same issues, would like some more info regarding this matter. Thank
you
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/PirateNetwork/PirateWallet-Lite/issues/28#issuecomment-830659066,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AT4RKMNQAFWDVJT2EHSB2CDTLQVADANCNFSM4325VMLQ
.


Clusters, apps/workloads can get stuck in deleting (waiting on foregroundDeletion)

Rancher versions: v2.0.0-alpha17
Steps to Reproduce:

Create a custom cluster
Try to add a couple of nodes that have 16.04 version of ubuntu from DO
When nodes are stuck in adding kubernetes delete cluster

Results: Custom Cluster stuck in removing state.

we didn't fix the root cause of this garbage collector bug. Need to discuss with darren as this needs change from k8s upstream.

Not sure what the current status of this is, but thought it would be worth mentioning that it still occurs for me.

How I got here:

Added node 2 to the cluster
Realized I configured the VM incorrectly, and deleted the VM
AFTER deleting the VM, I deleted it using the rancher console
state stuck in screenshot above for 12+ hours (I assume stuck indefinitely).

Would it have been better for me to remove the node from rancher before deleting the VM? Also, is there any way in the short term, before the root cause is fixed, to fix this without destroying and rebuilding the entire cluster?

How can I remove the node manually?

try below procedures:

 kubectl delete node nodename
in UI ,select the node ,then click edit, choose view in API ,then click delete button and using API to delete the node.
then clean the node .

@yoke88 that didnt help me, cause the nodes weren t initialized in the first place and kubernetes didn t know about them
what I did on a my single node instance with the embedded etcd (not HA rancher !!!!) was:

docker exec into the rancher container
kill the rancher process

Having the same issue with deleting workloads from Rancher 2.0.4 UI on custom offline on-prem cluster:
Deployment does not have minimum availability; waiting on foregroundDeletion
Running kubectl delete deploy/faultyworkload -n mynamespace does remove the workload / deployment.

@StrongMonkey the last time I've seen it happening was on @tfiduccia setup, for cluster object. K8s vendor is v1.10.5. But looks like it happens for both types of objects:

management cluster layer - CRDs created on the rancher side
user cluster layer - k8s "native" objects

Here is the cluster object stuck in finalizer snippet.
{
    "apiVersion": "management.cattle.io/v3",
    "kind": "Cluster",
    "metadata": {
        "annotations": {
            "authz.management.cattle.io/creator-role-bindings": "{\"created\":[\"cluster-owner\"],\"required\":[\"cluster-owner\"]}",
            "field.cattle.io/creatorId": "user-6shtq",
            "lifecycle.cattle.io/create.cluster-agent-controller-cleanup": "true",
            "lifecycle.cattle.io/create.cluster-provisioner-controller": "true",
            "lifecycle.cattle.io/create.cluster-scoped-gc": "true"
        },
        "clusterName": "",
        "creationTimestamp": "2018-07-17T18:26:30Z",
        "deletionGracePeriodSeconds": 0,
        "deletionTimestamp": "2018-07-17T18:46:42Z",
        **"finalizers": [
            "foregroundDeletion"
        ],**
        "generation": 2,
        "name": "c-g2bt6",
        "namespace": "",
        "resourceVersion": "7058",
        "selfLink": "/apis/management.cattle.io/v3/clusters/c-g2bt6",
        "uid": "ed2a7092-89ee-11e8-8cc0-0242ac110002"
    },

The cluster doesn't seem to have any objects referencing it via OwnerReference, but we need to double check on that.
Current workaround is (apply with caution, only when the object is really stuck, and after ensuring that all the objects referencing the removing one, are really removed):

connect to cluster using kubectl (if the object is on the management layer, login to rancher docker container, and run kubectl)
kubectl edit
remove the foregroundDeletion line, and save changes

@StrongMonkey refering to this issue: https://github.com/rancher/rancher/issues/14760
Restarting the Rancher Server deleted the Catalog App but all pods created with the Catalog App stayed stuck.
I then saw that all pods stucked where on the same worker node, so I removed the node and then all the pods were removed.
I'm sure the problem is not with my node because there were other pods on this node that were working perfectly.

I had a a stuck node that even was displayed although it's pool wasn't visible any more. Restarting Rancher server fixed it.

Tested using v2.0.7-rc5:

Deleted a cluster while nodes are being added.
Deleted nodes and deleted the clusters while the node is being deleted.
Deleted a cluster after removing the nodes VMs
I was able to delete resources (clusters, nodes, workloads) successfully.

Have the node removal issue with v2.0.6. Updated to v2.0.7 and issue remains.

I have a similar issue. https://github.com/rancher/rancher/issues/15039

Have the app removal issue with v2.0.6

@timfallmk Can you please provide steps to reproduce the issue after the upgrade ?
@workXMH Can you please try with v2.0.7 ?

I experienced this issue myself and I was able to fix the symptom (cluster not disappearing from the rancher GUI) by ensuring the cluster was completely removed from kubernetes, and then restarting the docker container for rancher. eg. docker restart <rancher container name>
I'm uncertain if this has been mentioned in previous comments, apologies if doubling up.


Run ensure blocks when killing a thread (and various other Threading bug fixes)

This also should produce a proper backtrace inside the killed thread.

OMG it's a miracle. I'm going to run CI again just to be sure. 😄


Apple Pay Is Not Available in App - Flutter

I am getting bellow error in IOS device when trying to pay with Apple Pay:-
Apple Pay is Not available in "App"
Check the settings for this app and make sure it was designed to use Apple Pay.

I am using these versions:-
Flutter SDK verison 3.3.0
pay: ^1.0.11
Please help me to solve this issue.

You probably have not completed the integration requirements for Apple Pay yet. Is that the case?
Make sure to enable Apple Pay in your Xcode project and issue the required certificates and give it another go.
Feel free to re-open the issue if the problem persists.


nrf5 examples stop responding while attempting thread join

As of https://github.com/openthread/openthread/pull/5299 thread joiner initiated at boot results in unresponsive device. It takes several join attempts for this to occur.
Repro (fails):
  git checkout b15c292ee56a0505d3a3904eb295b38bac71cfc9
  git submodule update --init

  cd third_party/openthread/repo
  git checkout addb1936c3e7e14e59f617751e595596980e3ec8 # fails
  cd examples/lock-app/nrf5
  make flash

  # thread CLI
  factoryreset

Boot and just wait. Device hangs after a few join attempts.
Repro: (stable)
  cd third_party/openthread/repo
  git revert HEAD

  cd examples/lock-app/nrf5
  make flash

Boot and just wait. Device stable.
Log:
[00000000] <info> chip: [DL] Setup PIN discriminator not found; using default: f00
[00000000] <info> chip: [DL] Joiner Discerner: 3840
[00000000] <info> chip: [DL] Setup PIN code not found; using default: 12345678
[00000000] <info> chip: [DL] Joiner PSKd: 12345678
[00000000] <info> chip: [DL] Joiner start: No Error
[00000000] <debug> chip: [DL] Thread joiner timer triggered: No Error
<hung>

@lanyuwen @bukepo

Fault stack:
Level,Function,Stack Frame,Source,PC,Return Address,Stack Used
0,,32 @ 0x2001FAE8,,0x00000A60,[0x2001FB00]: 0x0008FFC2,160
0,memcpy, 8 @ 0x2001FB08,,0x0008FFBE,[0x2001FB0C]: 0x0002CC32,128
0,xQueueReceive,48 @ 0x2001FB10,queue.c:1288:5,0x0002CC2E,[0x2001FB3C]: 0x0002DE38,120
0,prvProcessReceivedCommands, 0 @ 0x2001FB40,timers.c:696:7,0x0002DE34,: 0x0002DE98, 72
0,prvTimerTask,72 @ 0x2001FB40,timers.c:644:2,0x0002DE24,[0x2001FB84]: 0x03000000, 72
0,Top of stack - return address out of range: 0x3000000,,,,,

This is a timer task stack overflow. The timer task uses 1k stack by default. Enabling configCHECK_FOR_STACK_OVERFLOW diagnoses this issue.

@bukepo I believe we should move all of the code from GenericThreadStackManagerImpl_FreeRTOS<ImplClass>::OnJoinerTimer off the timer task. Logging uses a 256 byte stack buffer.
In the meantime I will post a patch to increase the stack size.


Disabled IPv6 and DNSTAP enabled triggers a build error

Building nsd without IPv6 but with DNSTAP fails for FreeBSD. See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254874
BTW, just building without IPv6 raises a couple of warnings.

Fixed the warnings and also compilation failure. The compilation failure is caused by debug printout wanting to access the ipv6 socket family descriptor when it does not exist. To test for IPv6. Fixed it to not do that when ipv6 is disabled.


Expired asciinema in readme

At first I thought that this repo was archived/abandoned or something, then I realized that it's just the asciinema in the readme that expired :)
It shows up like that:

the asciinema link says that recordings older than 7 days are archived: https://asciinema.org/a/ydfYbBXFyDDyDOeSPormkjEo6.

I'm not sure what was being showed in the video, if it can fit a screenshot I think it would be better because it shows everything at a glance; if not, a good old gif will be fine 😃


[Suggestion] build sdk only using swagger docs

Feature Request
I wrote swagger document using spring boot.
and I want to build nestia sdk using swagger document.
now, it is impossible to build only sdk using @nestia/migrate (it can generate sdk but also nestjs application)
so, I suggest options like --sdk-only  in @nestia/migrate
example)
npx @nestia/migrate --sdk-only swagger.json output_directory

https://github.com/samchon/nestia/issues/445
Good suggestion.
To accomplish above feature @nestia/editor, I should implement this issue, and it was one of my plan.

@2langk
Completed
https://nestia.io/docs/migrate/


Resolved handler metrics?

In our api, we've chosen to implement an api version as a pydantic validated url variable. Something like @router.get("/{api_version}/status") where the api_version is validated and rejected or accepted.
Prometheus-fastapi-instrumentator works like any other non-versioned route, and is measured fine, but, the api_version is never resolved into the actual version that is passed along. Out metrics end up like this:
http_requests_total{handler="/{api_version}/status",method="GET",status="2xx"} 32.0

While this works for general endpoint analysis, collecting time, or usage based on the api version would be better. So we could tell how frequently /1.0.0/status was hit vs /1.1.0/status, as a contrived example.
Is there any way to get the handler logged to resolved the api_version so our stats would end up like:
http_requests_total{handler="/1.0.0/status",method="GET",status="2xx"} 30.0
http_requests_total{handler="/1.1.0/status",method="GET",status="2xx"} 2.0

If not, and theoretically possible, would there be enough interest in a PR submitted to add this behavior, optionally?

I do concede we would not want this for everything, but an opt-in for certain endpoints might be nice. For instance, the api_version might be something to interpolate, but restful ids not so much. Perhaps a config option like:
interpolated_parameters = ["api_version", "namespace"]  # default = []

..and then adjust _get_handler to render the route.path through a substitution method which iterates over this list?
This way, we default to no change for backwards compatibility, but allow config for the use case described above. Thoughts?

Or perhaps an addition to the labels?
query_parameter_labels = ["api_version"]  # default = []

http_requests_total{handler="/{api_version}/status",method="GET",status="2xx",api_version="1.0.0"} 30.0
http_requests_total{handler="/{api_version}/status",method="GET",status="2xx",api_version="1.1.0"} 2.0

Hey @coneybeare, have you found any workaround for this?

Sadly, I could not allocate time to it so the issue persists on our setup

We have a similar issue. As a (temporary) workaround we just changed the following line in a local fork https://github.com/trallnag/prometheus-fastapi-instrumentator/blob/02e807b76cd2692cf543e207fd07f926a69046d6/prometheus_fastapi_instrumentator/instrumentation.py#L321
to
return request.url.path, True

this returns the fully interpolated path (for all endpoints).


[Network Watcher] Change: Update connection monitor creation and related commands

Related commands
az network watcher connection-monitor create
az network watcher connection-monitor output add
az network watcher connection-monitor endpoint add
az network watcher connection-monitor test-configuration add
az network watcher connection-monitor test-group add
Description

We have two versions of connection monitors- Connection Monitor (Classic) and Connection Monitor. The Connection Monitor (Classic) was in a deprecation phase and it completely stopped working on 29th February after which the customers were not able to use the existing commands for creating a connection monitor. These commands were not able to support the newer connection monitor and the customers were not able to create a connection monitor using these commands.
Changes that we have made
In the network module:

Modified the output/add.py file
Modified the endpoint/add.py file
Modified the test-configuration/add.py file
Modified the test-group/add.py file
Modified the connection_monitor/create.py file
Modified the watcher.py file

We have modified these five commands and followed an approach similar to PowerShell according to which the customer will now be able to use these commands and use the output in the subsequent commands for creating a connection monitor. The test group add command is modified to accept a list of sources, destinations and test configurations and then we can use the output of this command in the connection monitor create command in order to create a connection monitor.
Effect of our changes

We are now able to create a connection monitor with multiple sources, destinations and test configurations using these commands.
The commands support the newer connection monitor and the customers will now be able to use them properly
The customer will not have to pass multiple parameters in the command for creating a connection monitor explicitly. The sources, destinations and test configurations will be stored in the test group command output

Testing Guide

For testing the commands, we use the launch.json file where we specified the commands using the args array.
For output add, the command used is:
"network", "watcher", "connection-monitor", "output", "add", "--type", "Workspace", "--workspace-id", "WorkspaceId"
For test configuration add, the command used is:
"network", "watcher", "connection-monitor", "test-configuration", "add", "--name", "myTC", "--frequency", "60", "--protocol", "Http", "--http-method", "Get", "--http-valid-status-codes", "[200,201]", "--http-port", "84", "--http-request-headers", "[{'name':'name1','value':'value1'},{'name':'name2','value':'value2'}]"
For endpoint add, the command used is:
"network", "watcher", "connection-monitor", "endpoint", "add", "--name", "MyVM", "--type", "AzureVM", "--resource-id", "MyResourceId", "--scope-exclude", "[{'address':'<IP_ADDRESS>'},{'address':'<IP_ADDRESS>'}]", "--coverage-level", "BelowAverage"
For test group add, the command used is:
"network", "watcher", "connection-monitor", "test-group", "add", "--name", "tg1", "--sources", "[{'name':'Google','type':'ExternalAddress','address':'google.com'},{'name':'github','type':'ExternalAddress','address':'github.com','coverageLevel':'BelowAverage','scope':{'exclude':[{'address':'<IP_ADDRESS>'},{'address':'<IP_ADDRESS>'}]}}]", "--destinations", "[{'name':'MyVM','type':'AzureVM','resourceId':'MyResourceId'}]", "--test-configurations", "[{'name':'tc1','protocol':'Http','frequency':'60','httpConfiguration':{'method':'Get','validStatusCodeRanges':['200','201'],'requestHeaders':[{'name':'name1','value':'value1'},{'name':'name2','value':'value2'}]}}]"
For connection monitor create, the command used is:
"network", "watcher", "connection-monitor", "create", "--name", "cm3", "--network-watcher-name", "testnw", "--resource-group", "testrg", "--location", "eastus2", "--test-groups", "[{'testGroupName':'tg1','sources':[{'name':'VNet1','type':'AzureVNet','resourceId':'resourceId','coverageLevel':'BelowAverage',{name:'VNet2','type':'AzureVNet','resourceId':'resourceId2'}],'destinations':[{'name':'Google','type':'ExternalAddress','address':'google.com'},{name:'Github','type':'ExternalAddress','address':'github.com'}],'testConfigurations':[{'name':'tc1','protocol':'Http',frequency:'60','httpConfiguration':{'method':'Get','validStatusCodeRanges':['200','201'],'requestHeaders':[{'name':'name1','value':'value1'},{'name':'name2','value':'value2'}]}},{'name':'tc3','protocol':'Http',frequency:'60'}]},{'testGroupName':'tg2','sources':[{'name':'Vnet','type':'AzureVNet','resourceId':'resourceId'},{'name':'VM','resourceId':'resourceId','type':'AzureVM'}],'destinations':[{'name':'Github','type':'ExternalAddress','address':'github.com'},{name:'Bing','type':'ExternalAddress','address':'bing.com'}],'testConfigurations':[{'name':'tc2','protocol':'Http',frequency:'120','httpConfiguration':{'method':'Get','validStatusCodeRanges':['200','201']}}]}]"
These commands are tested properly, and we also validated them using the get and delete API calls where we were able to get all the details of the connection monitor created using this command and also delete the CM successfully.
This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

Network

unnecessary changes

please provide the pr in aaz repo


Triple ping

When an update gets posted, temporarily unposted, then reposted, the bot will ping three times

Will fix by making last_update an array

Thought this was fixed, but a similar issue - popped up with swords yet again

Finally fixed by b098c1bfa3c9107730ec1fd060de31bbb1fcd555 (hopefully)


Upload releases to pypi

The two latest releases have not been uploaded to pypi, could you do it?
Thanks

We uploaded 0.5.0. I need to patch 0.4.5 to update the version number. I'll do that this morning.


-DisableOnDestination does not appear to work in Copy-SqlJob

During testing for PR #116 I noticed -DisableOnDestination did not seem to be working for me, requires further testing and possibly checking of -DisableOnSource too.

Fixed in #133.


No way to use with storyboards

Need
- (void)awakeFromNib
{
    self.backgroundColor = [UIColor whiteColor];
    [self setDefaultParameters];
}

In FSLineChart.m in order to set up defaults.

Fixed in 0.1.6. Thanks for reporting the issue.


setting to expire time

Description
Hello,i am using spring boot redisson starter in version 3.8.2. I am confusing with the expire() method and remainTimeToLive(). I learned that the remainTimeToLive() method return -1 to indicate the key will never expire,-2 to indicate the key does not exist.However,in the method expire() ,when passing -1 will result in the key not exist,passing -2 will result in the key never expire.
I gets the result by my own test case.I want to know, if that is the design or is a bug?
Thank you!
Steps to reproduce or test case
Redis version
org.redisson:redisson-spring-boot-starter:3.8.2
Redisson version
Redisson configuration

Could you please clarify about expire() method? Since it returns boolean type and doesn't allow to use negative value as parameter.


Exclude websocket connections from Average Response Time

What does this PR do?

Update dependency to fix #3620
Motivation

The average response time on my dashboard was really bad because of it counting websocket connect.
More
not relevant
- [ ] Added/updated tests
- [ ] Added/updated documentation
Additional Notes

@siyu6974 could you don't update your branch.

Ok!


Test - Client aborts downloads if bitrate is too low

Where "download" means reading data from disk, in memory stores, or remote locations, and data means both metadata and target data.

Work tracked in branch timeout.


🐛 [firebase_auth] Email link auth not working with custom dynamic links domain

Bug report
When using a custom dynamic links domain (not a *.page.link) will the sent sign in link not open in app.
Expected behavior
The sign in link should open as expected in app and not in the browser.

Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
[✓] Flutter (Channel stable, 2.0.4, on macOS 11.2.3 20D91 darwin-arm, locale sv-SE)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
[✓] Xcode - develop for iOS and macOS
[✗] Chrome - develop for the web (Cannot find Chrome executable at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome)
    ! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.
[✓] Android Studio (version 4.1)
[✓] VS Code (version 1.55.0)
[✓] Connected device (1 available)

! Doctor found issues in 1 category.

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
Dart SDK 2.12.2
Flutter SDK 2.0.4

dependencies:
- auto_route 1.0.2 [flutter path collection]
- cupertino_icons 1.0.2
- easy_localization 3.0.0 [flutter shared_preferences intl args path easy_logger flutter_localizations]
- firebase_analytics 8.0.0-dev.0 [firebase_analytics_platform_interface firebase_analytics_web firebase_core flutter meta]
- firebase_auth 1.0.1 [firebase_auth_platform_interface firebase_auth_web firebase_core firebase_core_platform_interface flutter meta]
- firebase_core 1.0.2 [firebase_core_platform_interface firebase_core_web flutter meta]
- firebase_dynamic_links 2.0.0-dev.0 [firebase_core flutter]
- flutter 0.0.0 [characters collection meta typed_data vector_math sky_engine]
- flutter_hooks 0.16.0 [flutter]
- flutter_svg 0.21.0-nullsafety.0 [flutter meta path_drawing vector_math xml]
- font_awesome_flutter 9.0.0 [flutter]
- freezed_annotation 0.14.1 [collection json_annotation meta]
- get_it 6.0.0 [async collection]
- hooks_riverpod 0.14.0 [collection flutter flutter_hooks flutter_riverpod riverpod state_notifier]
- http 0.13.1 [http_parser meta path pedantic]
- injectable 1.2.2 [get_it]
- intl 0.17.0 [clock path]
- path 1.8.0
- path_provider 2.0.1 [flutter path_provider_platform_interface path_provider_macos path_provider_linux path_provider_windows]
- sembast 3.0.0+4 [meta path synchronized pedantic]
- shared_preferences 2.0.5 [meta flutter shared_preferences_platform_interface shared_preferences_linux shared_preferences_macos shared_preferences_web shared_preferences_windows]

dev dependencies:
- auto_route_generator 1.0.2 [build source_gen analyzer path build_runner code_builder dart_style auto_route]
- build_runner 1.12.2 [args async build build_config build_daemon build_resolvers build_runner_core code_builder collection crypto dart_style glob graphs http_multi_server io js logging meta mime path pedantic pool pub_semver pubspec_parse shelf shelf_web_socket stack_trace stream_transform timing watcher web_socket_channel yaml]
- flutter_native_splash 1.1.7+1 [image meta path xml yaml]
- flutter_test 0.0.0 [flutter test_api path fake_async clock stack_trace vector_math async boolean_selector characters charcode collection matcher meta source_span stream_channel string_scanner term_glyph typed_data]
- freezed 0.14.1+1 [analyzer build build_config meta source_gen freezed_annotation]
- injectable_generator 1.2.2 [build source_gen path glob analyzer code_builder dart_style injectable collection]
- json_serializable 4.1.0 [analyzer build build_config collection json_annotation meta path source_gen]
- pedantic 1.11.0

transitive dependencies:
- _fe_analyzer_shared 18.0.0 [meta]
- analyzer 1.2.0 [_fe_analyzer_shared cli_util collection convert crypto glob meta package_config path pub_semver source_span watcher yaml]
- archive 3.1.2 [crypto path]
- args 2.0.0
- async 2.5.0 [collection]
- boolean_selector 2.1.0 [source_span string_scanner]
- build 2.0.0 [analyzer async convert crypto glob logging meta path]
- build_config 0.4.7 [checked_yaml json_annotation meta path pubspec_parse yaml]
- build_daemon 2.1.10 [built_collection built_value http_multi_server logging pedantic path pool shelf shelf_web_socket stream_transform watcher web_socket_channel]
- build_resolvers 2.0.0 [analyzer build crypto graphs logging path package_config pool pub_semver stream_transform]
- build_runner_core 6.1.12 [async build build_config build_resolvers collection convert crypto glob graphs logging meta path package_config pedantic pool timing watcher yaml]
- built_collection 5.0.0
- built_value 8.0.4 [built_collection collection fixnum]
- characters 1.1.0
- charcode 1.2.0
- checked_yaml 2.0.1 [json_annotation source_span yaml]
- cli_util 0.3.0 [meta path]
- clock 1.1.0
- code_builder 3.7.0 [built_collection built_value collection matcher meta]
- collection 1.15.0
- convert 3.0.0 [typed_data]
- crypto 3.0.0 [collection typed_data]
- dart_style 2.0.0 [analyzer args path pub_semver source_span]
- easy_logger 0.0.2 [flutter]
- fake_async 1.2.0 [clock collection]
- ffi 1.0.0
- file 6.1.0 [meta path]
- firebase 9.0.1 [http http_parser js]
- firebase_analytics_platform_interface 2.0.0-dev.0 [flutter meta]
- firebase_analytics_web 0.3.0-dev.0 [firebase firebase_analytics_platform_interface flutter flutter_web_plugins meta]
- firebase_auth_platform_interface 4.0.0 [firebase_core flutter meta plugin_platform_interface]
- firebase_auth_web 1.0.3 [firebase_auth_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins http_parser intl js meta]
- firebase_core_platform_interface 4.0.0 [flutter meta plugin_platform_interface]
- firebase_core_web 1.0.2 [firebase_core_platform_interface flutter flutter_web_plugins js meta]
- fixnum 1.0.0
- flutter_localizations 0.0.0 [flutter intl characters clock collection meta path typed_data vector_math]
- flutter_riverpod 0.14.0 [collection flutter meta riverpod state_notifier]
- flutter_web_plugins 0.0.0 [flutter js characters collection meta typed_data vector_math]
- glob 2.0.0 [async collection file path pedantic string_scanner]
- graphs 1.0.0
- http_multi_server 3.0.0 [async]
- http_parser 4.0.0 [charcode collection source_span string_scanner typed_data]
- image 3.0.2 [archive meta xml]
- io 1.0.0 [meta path string_scanner]
- js 0.6.3
- json_annotation 4.0.1
- logging 1.0.0
- matcher 0.12.10 [stack_trace]
- meta 1.3.0
- mime 1.0.0
- package_config 2.0.0 [path]
- path_drawing 0.5.0-nullsafety.0 [vector_math meta path_parsing flutter]
- path_parsing 0.2.0-nullsafety.0 [vector_math meta]
- path_provider_linux 2.0.0 [path xdg_directories path_provider_platform_interface flutter]
- path_provider_macos 2.0.0 [flutter]
- path_provider_platform_interface 2.0.1 [flutter meta platform plugin_platform_interface]
- path_provider_windows 2.0.0 [path_provider_platform_interface meta path flutter ffi win32]
- petitparser 4.0.2 [meta]
- platform 3.0.0
- plugin_platform_interface 2.0.0 [meta]
- pool 1.5.0 [async stack_trace]
- process 4.2.1 [file path platform]
- pub_semver 2.0.0 [collection]
- pubspec_parse 1.0.0 [checked_yaml collection json_annotation pub_semver yaml]
- riverpod 0.14.0 [collection freezed_annotation meta state_notifier]
- shared_preferences_linux 2.0.0 [flutter file meta path path_provider_linux shared_preferences_platform_interface]
- shared_preferences_macos 2.0.0 [shared_preferences_platform_interface flutter]
- shared_preferences_platform_interface 2.0.0 [flutter]
- shared_preferences_web 2.0.0 [shared_preferences_platform_interface flutter flutter_web_plugins meta]
- shared_preferences_windows 2.0.0 [shared_preferences_platform_interface flutter file meta path path_provider_platform_interface path_provider_windows]
- shelf 1.1.0 [async collection http_parser path stack_trace stream_channel]
- shelf_web_socket 1.0.1 [shelf stream_channel web_socket_channel]
- sky_engine 0.0.99
- source_gen 1.0.0 [analyzer async build dart_style glob meta path pedantic source_span]
- source_span 1.8.0 [charcode collection path term_glyph]
- stack_trace 1.10.0 [path]
- state_notifier 0.7.0 [meta]
- stream_channel 2.1.0 [async]
- stream_transform 2.0.0
- string_scanner 1.1.0 [charcode source_span]
- synchronized 3.0.0
- term_glyph 1.2.0
- test_api 0.2.19 [async boolean_selector collection meta path source_span stack_trace stream_channel string_scanner term_glyph matcher]
- timing 1.0.0 [json_annotation]
- typed_data 1.3.0 [collection]
- vector_math 2.1.0
- watcher 1.0.0 [async path pedantic]
- web_socket_channel 2.0.0 [async crypto stream_channel]
- win32 2.0.5 [ffi]
- xdg_directories 0.2.0 [meta path process]
- xml 5.0.2 [collection meta petitparser]
- yaml 3.1.0 [collection source_span string_scanner]

@essarn
Can you provide a complete minimal reproducible code sample ? Also, can you try to use latest firebase_dynamic_link plugin version and see if issue still persists with it or not ?
Thanks.

Also check if this sounds similar to your issue.

Also check if this sounds similar to your issue.

Yes it looks to be the same problem. The only difference is that my custom domain is not using a path prefix as described in that issue.

Thanks. It'll be better to track it separately, so, can you provide steps to replicate along with code sample (with custom link domain) to properly address this issue ?

I don't want to publicly disclose my custom domain here and I have already described what causes the issue. The dynamic link opens in the app when using a .page.link domain but not with a custom one.

Is this on Android or iOS? Have you properly set up the intent filter on Android and added the domain in Xcode?

The problem occurs on Android and I have not added any intent filters. Is there any documentation on how to do that?

https://firebase.google.com/docs/dynamic-links/android/receive#add-an-intent-filter-for-deep-links

https://firebase.google.com/docs/dynamic-links/android/receive#add-an-intent-filter-for-deep-links
Try to see if this fixes the issue (and if the dynamic link data is received on the flutter side as expected).

That solved the problem by adding the intent filter for my custom domain. The email auth link now correctly opens in the app and the correct link is received. But is there a reason for why manually created deep links with the custom domain worked before adding the intent filter and not email auth links?

It probably has to do with the generated link page that is loaded after you open the dynamic link. For manually created deep links they should try to open the app or redirect if opened on desktop but for email verification links they might default to verifying in-browser.
Not really sure since this behavior is controlled by the Firebase side, not us.
Closing this as solved.


envoy: add bazel remote caching

In order to build bazel in CI without getting cache misses, the flag
experimental_strict_action_env was added as a bazel flag.
Signed-off-by: André Martins<EMAIL_ADDRESS>

test-me-please

test-ginkgo-all

test-nightly

test-all-ginkgo

test-ginkgo-all

Looks promising, and better than setting the PATH in the makefile.

waiting on https://github.com/cilium/packer-ci-build/pull/24

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

Is this PR actually adding bazel remote caching? I did not see it.

Is this PR actually adding bazel remote caching? I did not see it.

@jrajahalme
Yes, here https://github.com/cilium/cilium/pull/2826/commits/397f9877fa8f94de5d6dec2763fe75c08a0e7f9b

On Feb 21, 2018, at 1:37 PM, André Martins<EMAIL_ADDRESS>wrote:
Is this PR actually adding bazel remote caching? I did not see it.
@jrajahalme https://github.com/jrajahalme
Yes, here 397f987 https://github.com/cilium/cilium/commit/397f9877fa8f94de5d6dec2763fe75c08a0e7f9b

I see the added command line option that blocks ENV variables being inherited,which allows cache hits even if PATH is different. This works the same with local ore remote caches. However, I don’t see a remote cache being set up or referenced.

I see the added command line option that blocks ENV variables being inherited,which allows cache hits even if PATH is different. This works the same with local ore remote caches. However, I don’t see a remote cache being set up or referenced.

We did that here https://github.com/cilium/packer-ci-build/pull/27 the cache is inside the VM under /home/vagrant/.cache/bazel. Every time a new VM image is created we compile cilium from scratch. By doing this bazel will download everything.

On Feb 21, 2018, at 1:36 PM, André Martins<EMAIL_ADDRESS>wrote:
@aanm commented on this pull request.
In Vagrantfile https://github.com/cilium/cilium/pull/2826#discussion_r169785332:

curl -SsL https://github.com/cilium/bpf-map/releases/download/v1.0/bpf-map -o bpf-map
chmod +x bpf-map
mv bpf-map /usr/bin
-if [[ $(command -v bazel) && "$(bazel version | grep 'label' | cut -d ' ' -f 3)" = #{BAZEL_VERSION} ]]; then

echo "Bazel #{BAZEL_VERSION} already installed, skipping fetch."
-else
wget -nv https://github.com/bazelbuild/bazel/releases/download/#{BAZEL_VERSION}/bazel-#{BAZEL_VERSION}-installer-linux-x86_64.sh
chmod +x bazel-#{BAZEL_VERSION}-installer-linux-x86_64.sh
sudo -E ./bazel-#{BAZEL_VERSION}-installer-linux-x86_64.sh
sudo -E mv /usr/local/bin/bazel /usr/bin
rm bazel-#{BAZEL_VERSION}-installer-linux-x86_64.sh
-fi
@jrajahalme https://github.com/jrajahalme bazel is already installed in the VM, do you still want to download it every time we re-provision?

Yes, but only if the installed Basel version does not match the BAZEL_VERSION the repo needs. This is what the removed lines did.

test-me-please

Yes, but only if the installed Basel version does not match the BAZEL_VERSION the repo needs. This is what the removed lines did.

Removing this forces us to update the base image instead of having to update Bazel dynamically within the CI, which I prefer.

Removing this forces us to update the base image instead of having to update Bazel dynamically within the CI, which I prefer.

It's fine to leave the code as it was before, this allows faster development workflow for @jrajahalme and not have to wait for a new VM box version every time the bazel version changes. I've reverted the changes

On Feb 21, 2018, at 1:43 PM, André Martins<EMAIL_ADDRESS>wrote:
I see the added command line option that blocks ENV variables being inherited,which allows cache hits even if PATH is different. This works the same with local ore remote caches. However, I don’t see a remote cache being set up or referenced.
We did that here cilium/packer-ci-build#27 https://github.com/cilium/packer-ci-build/pull/27 the cache is inside the VM under /home/vagrant/.cache/bazel. Every time a new VM image is created we compile cilium from scratch. By doing this bazel will download everything.

So the cache is local to the VM. As we are not using the Bazel remote cache feature, I suggest removing “remote caching” from the PR title.

It's fine to leave the code as it was before, this allows faster development workflow for @jrajahalme and not have to wait for a new VM box version every time the bazel version changes. I've reverted the changes

Makes sense for development. However, my only concern is that this also allowed the Envoy rebase to be merged without updating the base image as well, which consequently resulted in a huge increase in build time and thus an impact on dev. productivity - if I am wrong in this assumption, please correct me, as I am by no means a Bazel expert. How often will the Bazel version change? If not frequently, I'd prefer we force PRs in the future to use an updated VM with new versions of dependencies as opposed to patching the existing one. This isn't blocking for me, just a discussion on how we want to approach this in the future.

On Feb 21, 2018, at 1:50 PM, Ian Vernon<EMAIL_ADDRESS>wrote:
It's fine to leave the code as it was before, this allows faster development workflow for @jrajahalme https://github.com/jrajahalme and not have to wait for a new VM box version every time the bazel version changes. I've reverted the changes
Makes sense for development. However, my only concern is that this also allowed the Envoy rebase to be merged without updating the base image as well, which consequently resulted in a huge increase in build time and thus an impact on dev. productivity - if I am wrong in this assumption, please correct me, as I am by no means a Bazel expert. How often will the Bazel version change? If not frequently, I'd prefer we force PRs in the future to use an updated VM with new versions of dependencies as opposed to patching the existing one. This isn't blocking for me, just a discussion on how we want to approach this in the future.

Bazel version update is not necessarily what causes the huge cache miss rate, it is the rebase to a newer version of Envoy. To make this better for all of us I’d suggest the following:

Allow Basel version upgrades based on the contents of envoy/BAZEL_VERSION (which is used to define $BAZEL_VERSION) to allow seamless development of PRs rebasing Envoy dependency.
Make it a policy to prepare a new version of the CI box based on a merge-ready Envoy PRs that would invalidate the cache significantly BEFORE such PRs are merged (this can be observed from the CI test runs)

I'm concerned by the failure of 10-proxy.sh as that's directly related to Envoy. There are no logs that were gathered for the test either for some reason :( so I'm not sure what the utility of debugging will be here. Will try running the tests again.

test-me-please

test-me-please

If this is not a blocker for anyone we can wait a couple hours for https://github.com/cilium/packer-ci-build/pull/28 to be merged

Hi,
The version 32 is already made by packer-ci and should work perfect without problems:
https://app.vagrantup.com/cilium/boxes/ubuntu/versions/32

test-me-please

@jrajahalme please check my last commit to see if it makes sense to you

test-me-please

test-nightly

test-nightly

test-nightly

test-me-please

Nightly tests failed, yet Ginkgo tests pass. Thoughts on merging this?

@ianvernon all of them seemed to be related with NODEPORT, worth checking I think

After discussion with @tgraf , merging.


Improve text display

Fixes #27
Preview: https://kimikage.github.io/ProfileSVG.jl/previews/PR28/
I plan to merge this in half a day and release v0.1.2. If there are no serious bugs, the next version will be v0.2.0.

https://kimikage.github.io/ProfileSVG.jl/previews/PR28/#Exporting-to-SVG-file-1
I can't deny the dirtiness, but it is better than nothing. :sweat_smile:

Codecov Report

Merging #28 into master will increase coverage by 1.20%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #28      +/-   ##
==========================================
+ Coverage   87.80%   89.01%   +1.20%
==========================================
  Files           2        2
  Lines          82       91       +9
==========================================
+ Hits           72       81       +9
  Misses         10       10

Impacted Files
Coverage Δ

src/ProfileSVG.jl
82.45% <100.00%> (+3.28%)
:arrow_up:

src/svgwriter.jl
100.00% <100.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 aae2845...489dc9a. Read the comment docs.


Allow a configuration file to designate the credentials for applications that require you to allow the app to make changes to device

Suggested new feature or improvement
Allow a configuration file to designate the elevated credentials to be used for installing applications that require the user to allow the app to make changes to the device. These credentials would be the same credentials specified when you select "Set up as admin" for the configuration file machine setup.
Scenario
If a user is not an administrator on a device, running a configuration file on Dev Home still requires the administrator to re-enter credentials for applications that make changes to the device. This feature would allow the configuration file to run without having to monitor the installations the whole time.
Additional details
No response

There are a few different moving parts related to elevated context for configurations with resources or packages requiring elevation. We're working to improve the flow, so a single elevation is sufficient for the entire configuration.
There will still likely be exceptions in some cases for installers with interesting flows that don't honor an initial elevation and launch user-based processes to trigger an install that still requires a subsequent elevation.
I'm not sure if this is truly a "Dev Home" specific problem, or a WinGet specific problem as WinGet is acting as the LCM (Local Configuration Manager) for Dev Home.
We're looking at ways the configuration file itself can provide the appropriate hints for which resources need elevation and which ones don't. Generally speaking, it's a bad idea to have credentials in a configuration file from a security standpoint.

Thank you, I hope you are successful in improving the flow so only a single elevation is required for the entire configuration, but I understand there may be exceptions in some cases for installers that have unique flows. I was just brainstorming ways there would only have to be one elevation credential provided in the configuration file, but understand that would be a security issue. Thanks again for the response and good luck. Dev Home has the potential to be an incredibly beneficial tool for developers in the future.


Navigation does not work with regexp

I use the current version (1.7) of xyz on a windows host.
I have opened, for example  .pkb PL/SQL File.
The navitagion via CTRL+P and ALT-GR+@ does not show all procs and funcs.
The reason is the regexp_ function, which is inside of another function.
In my case, i use regexp_count..., but also any other regexp_* function caused in a break for showing all funcs/procs in the navigation window.
Any reason why?

Can you give me an example ? In order to reproduce your issue.
(The latest version is 1.8.1)

The newest version seems to be 1.7, look at the picture, there is the german word "Aktuell" means current.

And here is an example. You can see only three procs/funcs. But in reality i have much more in my package.

The reason is the regexp_count function:

all the following funcs/procs will not displayed in the overview listing:

Only the first three proc/func.  With the appearance of the first regexp_* function inside a proc/func all the following won't appear.
Do you have any idea?
As soon as i removed all kind of regexp_* all funcs and procs will be displayed.
Strange behaviour.

Thanks for the example,
The last published version is 1.8.1 => update your vscode version.
You find a bug,
The problem here is not regexp_ but variable pi_case, As soon as I rename it to pi_cse, all funtions will be displayed. I guess there is a confusion in regExParser with keyword case.
I'll fix it...

Fix in version 1.8.2

Thank you for fixing the regexp issue. Right now, after all updates and your fixing it works.


multiple outage modeling updates

@hdunham I know the API never had the option to specify that the outage start time is at the peak load (a current webtool option), but since we are changing the webtool to use default outage start times to make the outage centered on the peak load of each of the four seasons, I was thinking we should at least have an easy option for the REopt.jl/API users to do this. Maybe a new input, boolean or string for different options (like starting on peak versus centered on peak, or seasonal peak versus yearly peak), which would enable that. This would also enable the webtool to use the same function with an endpoint (job.views function, calling a REopt.jl function in http.jl) to get the start time step. Thoughts?

@hdunham I know the API never had the option to specify that the outage start time is at the peak load (a current webtool option), but since we are changing the webtool to use default outage start times to make the outage centered on the peak load of each of the four seasons, I was thinking we should at least have an easy option for the REopt.jl/API users to do this. Maybe a new input, boolean or string for different options (like starting on peak versus centered on peak, or seasonal peak versus yearly peak), which would enable that. This would also enable the webtool to use the same function with an endpoint (job.views function, calling a REopt.jl function in http.jl) to get the start time step. Thoughts?

I added two issues for this and aim to include in the next PR updating outage modeling.
https://github.com/NREL/REopt.jl/issues/164
https://github.com/NREL/REopt_API/issues/395


Fail with error (rather than hanging) when init_op requires starting queues (ManagedSesssion etc)

In 0.12 and in master
MonitoredSession wraps the original SessionCreator in a _CoordinatedSessionCreator in an attempt to ensure queue runners are started before the session is run, however the original session has to be created first (as it is an argument to start_queue_runner). In the case of ChiefSessionCreator, ChiefSessionCreator.create_session calls ChiefSessionCreator._get_session_manager
which instantiates a new SessionManager and returns it. Then ChiefSessionCreator.create_session calls SessionManager.prepare_session which calls sess.run(init_op). Thus resulting in sess.run(init_op) being run before start_queue_runner is called.
This makes it impossible to initialize variables from queues. Even if this is intended behavior, it causes the initialization of MonitoredSession to stall without any logging output, and not respond to SIGTERM.
It seems that prepare_session may need to be split into two calls for this use case.

Unless I'm mistaken, it's quite important for initialization to happen before starting the queue runners, because input_producer() calls limit_epochs(), which sometimes creates a variable... that needs to be initialized before starting the queue runner (for the input producer).
What's the use case for initializing a variable from a queue? It sounds quite exotic, so perhaps it would be possible to achieve with a workaround in the user program.

Ahh shoot. You're right. I was just testing my code with constants upstream from the enqueue_ops (and initializing from a queue worked fine, because I could start the queue before running the init_op) but if I put variables upstream from the enqueue ops it throws a failed precondition.
Going to rescope this bug to failing more noisily when unstarted queues are inputs to ops. FYI my exotic use case was just a regular old rolling window pattern: https://gist.github.com/elibixby/cedd3be67020169ff3efc47dbb603af6
I'll try to find another way to do it.

I had the same issue when I wanted to use data dependent initialization in my neural net. I general, data dependent initialization is not an exotic thing to do, is it? Is there a better workaround than using assign ops after initialization is completed?

@elibixby What's the status of this issue?

Not sure there is any fix in the works. But I believe there may be a workaround, where you can create a separate GraphKey for variables that are downstream of Queues, and run initialization of those variables after queue initialization. Have to test it but believe it should work.

Actually, did https://github.com/tensorflow/tensorflow/commit/b25d1c7d3e9f30925aa132ba62e79d281191a3dc fix this?  It makes Variable.initialized_value not reinitialize already initialized variables, which should make data dependent initialization quite a bit easier.

It's possible, busy today but I can test tomorrow if no-one beats me to it.

@girving Yep! Good catch! This use case is now possible, if you remember to start queue runners, however, it still hangs indefinitely if you do not start queue runners. It should be possible for evaluation of graph nodes to determine if there are upstream queue nodes, and queues have not been started, which would help immensely in debugging this common error (whether it's worth the effort given tf.contrib.data is coming, is another question).
To be clear with the following graph:
import tensorflow as tf

graph = tf.Graph()
with graph.as_default():
   queue = tf.train.string_input_producer(['foo', 'bar', 'baz'])
   var = tf.Variable(queue.dequeue_many(3))

The following code works:
with tf.Session(graph=graph) as sess:
   tf.train.start_queue_runners(sess=sess)
   tf.global_variables_initializer().run()
   print(sess.run(var))

But the easy mistake of reversing two lines:
with tf.Session(graph=graph) as sess:
   tf.global_variables_initializer().run()
   tf.train.start_queue_runners(sess=sess)
   print(sess.run(var))

Results in a program that hangs indefinitely

@mrry Do you think it's feasible to programmatically warn about QueueRunners not being started?  The warning could even point people to tf.contrib.data. :)

@girving I once hacked up something that added to each tf.Tensor the set of queue runners on which it depended, and printed a warning when you tried to evaluate a tensor that depended on a queue runner that hadn't been started. I think it foundered because people ignore warnings and want errors, but there was a concern about false positives (e.g. perhaps you could feed a value to avoid depending on the queue, or it could be control-flow sensitive, and it wasn't clear how much metadata we should track to avoid the problem).

At the very least, I find it concerning that running of the initialization op doesn't respond to SIGTERM and only responds to SIGKILL when it's waiting for a queue dependency. What gives there?

This Stack Overflow answer goes into some of the details. Short answer: invoking native code on the main thread of a Python process can prevent the signal from being delivered.

It has been 14 days with no activity and this issue has an assignee.Please update the label and/or status accordingly.

Given that I think queues are now mostly deprecated, should we mark this wontfix? If no response after a while, we will close this.

I think this is no longer relevant in the world of tf.data, so closing. Please reopen if it's still an issue.


Bug/gotcha with standard String == Integer comparison? Need for stricter RBI's?

Hi! All hope you're all safe out there! We're thinking of adopting Sorbet for making our math and calculations on payments more safe. For this reason I was doing a simple string to int check. And to my surprise it shows no errors.
I can sort of guess that this has to do with the fact that that Integer == can accept everything so  it might be 'technically correct' but totally not what one might expect, coming from languages such as C# as this is a strict no-go.
Is there a path towards more stricter library / RBI for these built in types?
Input
→ View on sorbet.run
# typed: strict
require "sorbet-runtime"

class A
  extend T::Sig
  sig { returns(Integer) }
  def amount
    1
  end
end

a = A.new
if a.amount == "wtf" # why is this possible?
  p "Hi"
end

Observed output
No errors! Great job.

Expected behavior
Would expect that the type system would fail or at least warn me about doing a String to integer comparison.

The == operator accepts an argument of type BasicObject, so you're allowed to compare against anything else. The program you provided is fine, as the comparison will always be false.

Imma close this for now and Integer/Num/float RBI without these overly accepting/kind ==


Updates Mathjax CDN

According to documentations and warning in the cosnole.log Mathjax CDN is changing.
For more information see here:
https://www.mathjax.org/cdn-shutting-down/

:thinking:

Updated MathJax CDN path for v2.7.2 will land in #265 once merged.


Why using id ?

Hi :)
All is in the title, why using id on line 29 :
https://github.com/LukyVj/Colorify.js/blob/master/scripts/colorify.js#L29
And in the examples in doc :

Regards.

Hey, thanks for the issue.
Where ?
For each gradient ?
Just because it makes sense to me. But happy to discuss about it :)

yes i'm just wondering :) each call to colorify should have an id ?

Ok so, I will have to respond to that a bit later. I did this project nearly 1 year ago, and I barely put my hands in the code after that :p
There were a V2 in it's way, but I stopped developing it.
I have to first dig in my code, and then I'll respond.
But so far, what I can say is I target each 'gradient's target' with ID's.

ok :p
it's not a big deal, I was just curious,
Thanks for your lib anyway :+1:


Error when parse hook

Cause: type 'List<dynamic>' is not a subtype of type 'List<String>' in type cast
#0      Object._as (dart:core/runtime/libobject_patch.dart:67:25)
#1      Hook.fromJSON (file:///Users/jimmy/.pub-cache/hosted/pub.dartlang.org/github-4.0.0/lib/src/common/model/repos_hooks.dart:38:34)
#2      RepositoriesService.createHook.<anonymous closure> (file:///Users/jimmy/.pub-cache/hosted/pub.dartlang.org/github-4.0.0/lib/src/common/repos_service.dart:428:51)
#3      GitHub.postJSON (file:///Users/jimmy/.pub-cache/hosted/pub.dartlang.org/github-4.0.0/lib/src/common/github.dart:283:19)
<asynchronous suspension>
#4      RepositoriesService.createHook (file:///Users/jimmy/.pub-cache/hosted/pub.dartlang.org/github-4.0.0/lib/src/common/repos_service.dart:427:20)

Is it shall cast list?
 events = input['events'].cast<String>();

I think this is this fixed w/ #122?


Allow searching from middle of text

Allow searching from middle of text. For example if i have gameobject named ButtonCall, and i search for Call it will not find it.
Also Is there gona be pro version? because its removed from asset store

That's a great idea. I'll track down where that change would need to be made if anyone wants to put together a PR.

Also Is there gona be pro version? because its removed from asset store

This is the full source of the Pro version.

Ensure that the required characters are in the index:

Assets/Haste/Editor/HasteIndex.cs#L26
Assets/Haste/Editor/HasteStringUtils.cs#L278

Ensure that we're filtering the index on more than the first character:

Assets/Haste/Editor/HasteSearch.cs#L29

I believe this was done for performance reasons so I'd definitely check out the test environment:

Assets/Testing/VeryBig.unity

thanks i will check it


Add Sinope switch manufacturer cluster attributes and quirks

Added quirks for many Sinopé switch devices. Supported devices, SP2600ZB, SP2610ZB, RM3250ZB, RM3500ZB,
VA4200WZ, VA4201WZ, VA4200ZB, VA4201ZB, VA4220ZB, VA4221ZB and MC3100ZB.

Codecov Report

Merging #1386 (0d0d78a) into dev (f9e25f4) will increase coverage by 0.06%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##              dev    #1386      +/-   ##
==========================================
+ Coverage   81.06%   81.12%   +0.06%
==========================================
  Files         218      218
  Lines        6093     6114      +21
==========================================
+ Hits         4939     4960      +21
  Misses       1154     1154

Impacted Files
Coverage Δ

zhaquirks/sinope/switch.py
100.00% <100.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 f9e25f4...0d0d78a. Read the comment docs.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

23 of 23 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.07%) to 81.125%

Totals

Change from base Build<PHONE_NUMBER>:
0.07%

Covered Lines:
4960

Relevant Lines:
6114

💛  - Coveralls


handlePlay

Hi, not sure if this is intentional.
handlePlay seems to make a second requestAd after imaPlayer.play(); , which seems to mess up the callbacks.
I'm actually suggesting separation of initialization of both players. Seems to work better.

That issue seems to be resolved with the latest fix.


Keda stuck in error loop calculating lag from kafka

Report
We are using keda with kafka scaler(confluent). At same time in different gke clusters, there was probably a network glitch in keda kafka communication. Then keda-operator pod got stuck in error loop in calculating lag from kafka. Same error log in keda operator logs for 6 hours while other kafka consumers were working fine.
Expected Behavior
Even if there's an error once, keda should calculate correct lag eventually.
Actual Behavior
Keda operator stuck in calculating error loop, causing kafka scaler to stop functioning. Severe SEV1 on production.
Steps to Reproduce the Problem
Keda using kafka autoscaler (confluent). Simulate network glitch.
Logs from KEDA operator
No response
KEDA Version
2.7.1
Kubernetes Version
1.23
Platform
Google Cloud
Scaler Details
Kafka
Anything else?
{
msg:
cluster_name:prod
kubernetes:{
container_name:keda-operator
namespace_name:keda
pod_name:keda-operator-7fdbdfd484-h5fw9
container_image:ghcr.io/kedacore/keda:2.7.1
container_image_id:ghcr.io/kedacore/keda@sha256:
pod_id:
pod_ip:
host:
labels:{
app:keda-operator
name:keda-operator
pod-template-hash:7fdbdfd484
app_kubernetes_io/component:operator
app_kubernetes_io/instance:keda
app_kubernetes_io/managed-by:Helm
app_kubernetes_io/name:keda-operator
app_kubernetes_io/part-of:keda-operator
app_kubernetes_io/version:2.7.1
helm_sh/chart:keda-2.7.2
}
master_url:
namespace_id:
namespace_labels:{
name:keda
kubernetes_io/metadata_name:keda
}
}
stacktrace:github.com/kedacore/keda/v2/pkg/scalers.(*kafkaScaler).getLagForPartition
/workspace/pkg/scalers/kafka_scaler.go:368
github.com/kedacore/keda/v2/pkg/scalers.(*kafkaScaler).IsActive
/workspace/pkg/scalers/kafka_scaler.go:255
github.com/kedacore/keda/v2/pkg/scaling/cache.(*ScalersCache).getScaledJobMetrics
/workspace/pkg/scaling/cache/scalers_cache.go:257
github.com/kedacore/keda/v2/pkg/scaling/cache.(*ScalersCache).IsScaledJobActive
/workspace/pkg/scaling/cache/scalers_cache.go:124
github.com/kedacore/keda/v2/pkg/scaling.(*scaleHandler).checkScalers
/workspace/pkg/scaling/scale_handler.go:286
github.com/kedacore/keda/v2/pkg/scaling.(*scaleHandler).startScaleLoop
/workspace/pkg/scaling/scale_handler.go:149
stream:stderr
level:error
logger:kafka_scaler
time:2022-08-15T18:39:53.42022928Z
error:error finding offset block for topic prod and partition 0
ts:1660588793.420116
docker:{
container_id:
}
}

can anyone check and comment please?

Hey @amit1-100ms ,
I've got the same kind of issue from Azure environment.
We do also suspect issue due to network glitch.
the only workaround we found is to restart the KEDA operator deployment (to start a new pod) then all is fine.
Also really interested in a fix on KEDA side.

Is anybody able to reproduce the issue?

@zroubalik simulating network error on kafka side should reproduce it once in a while
@kevinnesta we had to deploy custom keda code which throws error on this as a stop gap solution. What fix did you guys do?

@amit1-100ms we monitor the KEDA operator service logs to trigger automatic restart ...

When we run on instances in aws with better network performance the problem does not occur. Example: m5.8xlarge, c6i.8xlarge.


Document limitations of Azure Subscription Name

Azure Subscription Name
I am only able to find that there is a limit of 64 characters in an Azure Subscription Name on this page.
I am not able to find any other information documented about characters that are not permitted in the name. Does this documentation exist? If not, can it be added to this page, please?

Closing in favor of #106556


Is it possible to have a step of 1, and show ticks every ten steps?

I am attempting to show slider allowing users to select a percent complete.  Values are in the range 0 - 100.  I'd like them to be able to select any integer value (1,2, 3, ..., 98, 99, 100).  But only show ticks at major intervals for example (10, 20, 30, 40, 50, 60, 70, 80, 90, 100).
I have tried these options, but which allows me to select an integer value, but display all 100 tick marks.  Am I misunderstanding the documentation?  Or is this not possible?
sliderOptions: {
    floor : 0,
    ceil : 100,
    step: 1,
    showTicks: 10
};

There you go: http://jsfiddle.net/uqmpc5k0/ .
Your options are correct but you are probably using an old version, this feature has been added in 2.12: https://github.com/angular-slider/angularjs-slider/blob/master/CHANGELOG.md#2120-2016-04-22


Add reko

Microsoft Reviewers: Open in CodeFlow

What would I put as the detection name?

just put the filename of the installer, Smartscreen identify a file through sha256.

Despite passing the check from the submission to windows defender it is still marked by safescreen. Not sure how reputation is supposed to be established when this app isn't really popular.

Despite passing the check from the submission to windows defender it is still marked by safescreen. Not sure how reputation is supposed to be established when this app isn't really popular.

@KevinLaMS reko no longer fails smartscreen


fixes. additional options

Added isDoubleElimination, disableTeamEdit and disableEditButtons options
fixed proper line endings in source file

@teijo would it be possible to merge this PR?

Thanks for making a PR, I'll try to go through it this weekend.
If the new functionality is something that would be merged, then you should trim the PR a bit to keep the history of changes clear.
I recommend discarding the style changes and squashing the commits so that e.g. the compilation results accidentally included in 7bf178e don't need to be removed right in the next commit ff4022e. The PR should include only the changes required for the new functionality. You should have multiple commits of course if they contain changes not related to each other.

No problem can do.only why do you want to the style changes to be discarded? My editor goes beserk because of all the missing semicolons.

disableEditButtons already exists by not providing save callback in init. From https://github.com/teijo/jquery-bracket/blob/master/src/jquery.bracket.ts#L1114
    if (opts.save)
      embedEditButtons(topCon, data, opts)

Addressed  isDoubleElimination in #36. Use [[[[]]], [], []] as result to init as double elimination instead.
Regarding style changes, I don't see it as a priority as it'll touch nearly every line. If it's done, it has to be enforced by a linting tool as it's impossible to manually adhere to a style perfectly.
What was the functionality of disableTeamNameEdit? To me, it relates to editing to the bracket, but that can be disabled by not defining save in init.

The reasons are:

wanting the save option but not the buttons
wanting the save option but team names need to be static

It makes the library more flexible

I can see how that could make for a better workflow - to prevent user from changing tournament size or participants (from UI) while the tournament is ongoing. I think it should be an OK feature. Just thinking about the API.
Instead of creating a lot of top level booleans that start to conflict with each other, like onMatchClickand onMatchHover that cannot be used while save is defined, howabout a extending save? The options could be configured under save as object as they are both related to the save functionality.
Keep the old API which is:
$('div#selector').bracket({
  save: function() {}
})

But allow extending save by:
$('div#selector').bracket({
  save: {
    callback: function() {},
    disableNameEdit: true,
    disableFormatEdit: true // idk if "format" is descriptive enough...
  }
})

I'd prefer not referring to the buttons as disableEditButtons as it doesn't reflect what functionality the setting changes.
We could close this pull request and make a new one for just enhancing the save functionality. What do you think?

Master branch includes now the support for disabling name editing and resizing (disableTeamEdit and disableResize). Will get included into the next release. Now at top level but as I see my old suggestion here again, might update it for the release :)


Within the scope of a release, I want to delete stages or disable triggers

Our release version matches our build version.  If our build version number is a certain format (contains the word 'dev'), that build must only ever be deployed to the dev environment.  If the build version is a parseable semantic version number, the code can be deployed to QA, Staging, and Production.  Currently, I have a powershell script in the later stages that cancels the deployment if the version contains the word 'dev'.  Within the scope of a single release, I want a script in the Dev stage to remove the later stages from the release OR disable their approval conditionals and triggers.

After some consideration, a post deployment gate that calls a simple function app to evaluate my version number may be the right way to handle this.

@itsjusth Thank you for the question.
Perhaps using a combination of pipeline variables, for instance, isDev and task control options?  You can then add your initial script to this solution with the PowerShell task.
There are many possibilities here and the solution you posted might be the easiest depending on your situation.


Add API reference documentation for ci-cd

Part 2 of closing #95.
To do:

[x] Rebase on main after #109 has been merged.

Add API reference documentation for this repository to the documentation at SINTEF.github.io/ci-cd.
Note, this is part 2 of 3 of a new set of PRs that replace #99.
Closes #113

Codecov Report

Merging #110 (56f3f61) into main (2e0929c) will increase coverage by 3.91%.
The diff coverage is 57.74%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main     #110      +/-   ##
==========================================
+ Coverage   53.69%   57.61%   +3.91%
==========================================
  Files           3        8       +5
  Lines         311      361      +50
==========================================
+ Hits          167      208      +41
- Misses        144      153       +9

Impacted Files
Coverage Δ

ci_cd/tasks/docs_index.py
23.33% <23.33%> (ø)

ci_cd/tasks/setver.py
23.52% <23.52%> (ø)

ci_cd/tasks/api_reference_docs.py
65.41% <65.41%> (ø)

ci_cd/tasks/update_deps.py
68.81% <68.81%> (ø)

ci_cd/utils.py
69.76% <69.76%> (ø)

ci_cd/tasks/__init__.py
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

How do I test that the documentation is properly generated?

You could generate it locally? Or you could check the CI/CD workflow that builds the documentation and that it doesn't fail? So that would be this run.

What are the codecov warnings about newly added lines? They do not seem to be newly added in this PR, but is sounds like that from the codecov issues.

I think this is a timing issue, since these PRs were created simultaneously, but built upon each other. So while the changes codecov reference have now been merged into main from the previous PR, codecov still ran when these changes weren't merged, so it flagged these lines in its run. I'm sure if it runs again, for some reason (if I add more commits) they should go away. We'll see I suppose.


update api link on line 71

Changed the url on line 71 to https://api.cloudflare.com/#zone-purge-files-by-cache-tags,-host-or-prefix because it changed in the doc (sorry if this is repeat, I'm not sure if the first was successful)

👋@linzinha Thank you for the correction.


Steps auto-wiring and proc macros (#81)

Closes #81
This PR integrates the machinery described in #81 into cucumber_rust crate. This, however, requires to intoduce a cucumber_rust_codegen sub-crate.
The initial idea was fully designed and implemented by @ilslv in our closed code base, and I'm just baking his work into this upstream crate.
Checklist

[x] Tests are added
[x] Documentation is added
[x] macros feature on https://docs.rs is rendered
[x] README is updated

Filling the CHANGELOG in the correct way was left for maintainers.

Thanks! :)


🔼 Levels & Special Abilities

Feature description:
Level system, players could gain levels by doing several works that fits the theme "survival" like killing zombies, using meds, building, picking airdrops....etc. And each level should be presented with a special reward.
Abilities system, a system thats linked to levels, the more you level up the more "Upgrade Points" you get, you can use those points to buy special abilities such as More damage, shotgun knockback, More resistence, invisiblity against zombies.....etc.
How do you think this feature will benefit the overall experience:
It will be a great experiance ingame to have those.
Additional context
None

Exactly

Adopt an xp system that stretches exponentially f(x) = 2x, where f(x) is the player's score and x is their xp.


process.nextTick(check) in next.group could cause a bug of race condition

I really like the way step works, simplifying my code greatly. However when I read the code of step, I'm really skeptical about this:
function check() {
  if (pending === 0) {
    // When group is done, call the callback
    localCallback(error, result);
  }
}
process.nextTick(check2); // Ensures that check is called at least once

I believe the comment "Ensures that check is called at least once" actually means:

If var group = this.group() is executed but no subsequent group() is called, we have to make sure the next step is called back anyway (with result equal to []).

That's right. But what if there are subsequent group() calls? If this next-tick-check is done before any asynchronous callbacks (returned by subsequent group() calls) are called, it's harmless, because pending can't be equal to 0. However, if the next-tick-check is called last, it could be disastrous because localCallback will consume another step function with the same result.
The thing is, you can't assume process.nextTick callback will be called in the very first place. This thread talks about it: https://groups.google.com/forum/?fromgroups=#!topic/nodejs/e8nLG5xrorA . From time to time process.nextTick callback really happens as the last one.
I have managed to construct a counter-example. Firstly, to facilitate watching, I changed step.js a little:
function check() {
  console.trace('check by callback');
  if (pending === 0) {
    console.trace('do by callback');
    // When group is done, call the callback
    localCallback(error, result);
  }
}
function check2() {
  console.trace('check by nextTick');
  if (pending === 0) {
    console.trace('do by nextTick');
    // When group is done, call the callback
    localCallback(error, result);
  }
}
process.nextTick(check2); // Ensures that check is called at least once

Then I run this test code:
var fs = require('fs'),
    path = require('path'),
    step = require('step');

var root = path.join(__dirname, 'test'),
    files;

step(
  function () {
    fs.readdir(root, this);
  },
  function (err, _files) {
    if (err) { throw err; return; }
    files = _files;
    var group = this.group();
    files.forEach(function (file) { fs.stat(path.join(root, file), group()); });
  },
  function (err, stats) {
    if (err) { throw err; return; }
    var group = this.group();
    files.filter(function (file, i) {
      return stats[i].isFile();
    }).forEach(function (file) { fs.readFile(path.join(__dirname, 'test', file), group()); });
  },
  function (err, contents) {
    if (err) { throw err; return; }
    console.log(contents);
  }
);

When there are only one file and one directory under test directory, I get the result, unfortunately, like this:
$ node test.js
Trace: check by callback
    at check (/home/djkings/mdblog/node_modules/step/lib/step.js:98:15)
    at next.group (/home/djkings/mdblog/node_modules/step/lib/step.js:127:22)
    at Object.oncomplete (fs.js:297:15)
Trace: check by callback
    at check (/home/djkings/mdblog/node_modules/step/lib/step.js:98:15)
    at next.group (/home/djkings/mdblog/node_modules/step/lib/step.js:127:22)
    at Object.oncomplete (fs.js:297:15)
Trace: do by callback
    at check (/home/djkings/mdblog/node_modules/step/lib/step.js:100:17)
    at next.group (/home/djkings/mdblog/node_modules/step/lib/step.js:127:22)
    at Object.oncomplete (fs.js:297:15)
Trace: check by nextTick
    at check2 (/home/djkings/mdblog/node_modules/step/lib/step.js:106:15)
    at process.startup.processNextTick.process._tickCallback (node.js:244:9)
Trace: do by nextTick
    at check2 (/home/djkings/mdblog/node_modules/step/lib/step.js:108:17)
    at process.startup.processNextTick.process._tickCallback (node.js:244:9)
[ { dev: 2051,
    ino: 4335031,
    mode: 33188,
    nlink: 1,
    uid: 1000,
    gid: 1000,
    rdev: 0,
    size: 1557,
    blksize: 4096,
    blocks: 8,
    atime: Tue Oct 16 2012 11:09:49 GMT+1300 (NZDT),
    mtime: Tue Oct 16 2012 10:49:08 GMT+1300 (NZDT),
    ctime: Tue Oct 16 2012 10:49:08 GMT+1300 (NZDT) },
  { dev: 2051,
    ino: 4335032,
    mode: 16893,
    nlink: 2,
    uid: 1000,
    gid: 1000,
    rdev: 0,
    size: 4096,
    blksize: 4096,
    blocks: 8,
    atime: Mon Oct 15 2012 17:48:52 GMT+1300 (NZDT),
    mtime: Sun Oct 14 2012 09:46:50 GMT+1300 (NZDT),
    ctime: Tue Oct 16 2012 10:49:16 GMT+1300 (NZDT) } ]
Trace: check by nextTick
    at check2 (/home/djkings/mdblog/node_modules/step/lib/step.js:106:15)
    at process.startup.processNextTick.process._tickCallback (node.js:244:9)
Trace: check by callback
    at check (/home/djkings/mdblog/node_modules/step/lib/step.js:98:15)
    at next.group (/home/djkings/mdblog/node_modules/step/lib/step.js:127:22)
    at fs.readFile (fs.js:176:14)
    at Object.oncomplete (fs.js:297:15)
Trace: do by callback
    at check (/home/djkings/mdblog/node_modules/step/lib/step.js:100:17)
    at next.group (/home/djkings/mdblog/node_modules/step/lib/step.js:127:22)
    at fs.readFile (fs.js:176:14)
    at Object.oncomplete (fs.js:297:15)

However, when I add one more file to the test directory, the timing changes accordingly:
$ node test.js
Trace: check by callback
    at check (/home/djkings/mdblog/node_modules/step/lib/step.js:98:15)
    at next.group (/home/djkings/mdblog/node_modules/step/lib/step.js:127:22)
    at Object.oncomplete (fs.js:297:15)
Trace: check by callback
    at check (/home/djkings/mdblog/node_modules/step/lib/step.js:98:15)
    at next.group (/home/djkings/mdblog/node_modules/step/lib/step.js:127:22)
    at Object.oncomplete (fs.js:297:15)
Trace: check by callback
    at check (/home/djkings/mdblog/node_modules/step/lib/step.js:98:15)
    at next.group (/home/djkings/mdblog/node_modules/step/lib/step.js:127:22)
    at Object.oncomplete (fs.js:297:15)
Trace: do by callback
    at check (/home/djkings/mdblog/node_modules/step/lib/step.js:100:17)
    at next.group (/home/djkings/mdblog/node_modules/step/lib/step.js:127:22)
    at Object.oncomplete (fs.js:297:15)
Trace: check by callback
    at check (/home/djkings/mdblog/node_modules/step/lib/step.js:98:15)
    at next.group (/home/djkings/mdblog/node_modules/step/lib/step.js:127:22)
    at fs.readFile (fs.js:176:14)
    at Object.oncomplete (fs.js:297:15)
Trace: check by callback
    at check (/home/djkings/mdblog/node_modules/step/lib/step.js:98:15)
    at next.group (/home/djkings/mdblog/node_modules/step/lib/step.js:127:22)
    at fs.readFile (fs.js:176:14)
    at Object.oncomplete (fs.js:297:15)
Trace: do by callback
    at check (/home/djkings/mdblog/node_modules/step/lib/step.js:100:17)
    at next.group (/home/djkings/mdblog/node_modules/step/lib/step.js:127:22)
    at fs.readFile (fs.js:176:14)
    at Object.oncomplete (fs.js:297:15)
[ <Buffer 23 20 56 6f 64 6b 61 0a 0a 23 23 20 4e 65 6d 69 72 6f 66 66 20 44 65 6c 69 6b 61 74 0a 0a 21 5b 4e 65 6d 69 72 6f 66 66 20 44 65 6c 69 6b 61 74 5d 28 76 ...>,
  <Buffer 23 20 47 69 6e 0a 0a 2e 2e 2e 74 68 65 20 62 65 73 74 20 64 72 69 6e 6b 20 69 6e 20 65 78 69 73 74 65 6e 63 65 20 69 73 20 74 68 65 20 50 61 6e 20 47 61 ...> ]
Trace: check by nextTick
    at check2 (/home/djkings/mdblog/node_modules/step/lib/step.js:106:15)
    at process.startup.processNextTick.process._tickCallback (node.js:244:9)
Trace: do by nextTick
    at check2 (/home/djkings/mdblog/node_modules/step/lib/step.js:108:17)
    at process.startup.processNextTick.process._tickCallback (node.js:244:9)
Trace: check by nextTick
    at check2 (/home/djkings/mdblog/node_modules/step/lib/step.js:106:15)
    at process.startup.processNextTick.process._tickCallback (node.js:244:9)
Trace: do by nextTick
    at check2 (/home/djkings/mdblog/node_modules/step/lib/step.js:108:17)
    at process.startup.processNextTick.process._tickCallback (node.js:244:9)

I guess now you know what I mean. Ideally we should handle the empty group case just like handling the empty parallel case, checking it synchronously rather than by process.nextTick. As an exercise I'll try to fix this problem but it might involve major revision in step.js.

Yeah... I noticed this bug in the past, as well.  The way I normally do this (and the way I handled it in my async lib ) is by keeping track of the total number of callbacks and the completed number of callbacks.  That way, totalCallbacks is incremented asynchronously and you don't get strange behavior.  Once completedCallbacks >= totalCallbacks, you know that you are done.


Confidence interval robustness fixes.

Exceptions were occurring in some cases when no data was present or no requests of a particular type succeeded. This PR fixes those cases.

@cpennington Please review


feat(remix-dev): allow importing .psd files

Adds support for importing photoshop image files as assets.
Not sure if there's any need to add the MIME type to the binaryTypes.ts files in remix-architect and remix-netlify, but fwiw the MIME is image/vnd.adobe.photoshop
Testing Strategy:
I was able to import a .psd file as an asset as expected:
import sourceArt from "./assets/art.psd"

export default function PsdLink() {
  return (
    Download PSD
  )
}

Yeah, we should probably make it configurable or something

Perhaps we can just add support for a file: prefix and maybe even a content: prefix to  return the content as a string. Not sure how doable this is, although I remember Remix used to have a css: handler at one point.
import psdFile from 'file:~/app/files/example.psd'
import txtFile from 'content:~/app/files/data.txt'

I like @kiliman idea, instead of a config file allow any import to have file: or content:, that could even allow things like content:path/to/file.ts and get the TS file as a string instead of doing an actual import

We would also need to be able to serve the file with the accurate mime-type when it's server from assets. Any ideas on how to implement this as well?

Hiya @machour, thanks for taking a look at this! I'm glad to have started a conversation  - I was surprised after reading through the Remix docs on asset files that I had to apply a patch rather than update a configuration file somewhere to be able to do this. 😅
Let me know if there's any way I can assist.

🤔 I think either Remix lets you configure this in remix.config.js (like an extensions option) or Remix trust the server to send the correct mime types on files from the public folder including public/build

I've created a patch to allow you to specify the server file to use with Remix App Server. It even supports TS files. You just need to export a function named createApp. I want to add an eject command that will generate the server file for you. The cool thing about this is you now get to customize the server all you want but still get the DX benefit of using npm run dev. No need to spawn a separate express server.
BTW: I had to create a new config option. The server option actually bundles the server code with your app, which is not what I wanted. I plan to submit a PR soon.
//server.ts
import { createRequestHandler } from "@remix-run/express";
import compression from "compression";
import express from "express";
import morgan from "morgan";

export function createApp(
  buildPath: string,
  mode = "production",
  publicPath = "/build/",
  assetsBuildDirectory = "public/build/"
) {
  let app = express();

  app.disable("x-powered-by");
  app.use(function (req, res, next) {
    res.setHeader("X-Powered-By", "TS Remix App Server");
    next();
  });
  app.use(compression());

  app.use(
    publicPath,
    express.static(assetsBuildDirectory, { immutable: true, maxAge: "1y" })
  );

  app.use(express.static("public", { maxAge: "1h" }));

  app.use(morgan("tiny"));
  app.all(
    "*",
    mode === "production"
      ? createRequestHandler({ build: require(buildPath), mode })
      : (req, res, next) => {
          // require cache is purged in @remix-run/dev where the file watcher is
          let build = require(buildPath);
          return createRequestHandler({ build, mode })(req, res, next);
        }
  );

  return app;
}

// remix.config.js
/** @type {import('@remix-run/dev').AppConfig} */
module.exports = {
  ignoredRouteFiles: ["**/.*"],
  serverEntryFile: "./server.ts",
  // appDirectory: "app",
  // assetsBuildDirectory: "public/build",
  // serverBuildPath: "build/index.js",
  // publicPath: "/build/",
};

Notice the X-Powered-By header

Sorry, commented on wrong issue.


Deprecate BytesMut::take(), renamed to split()

In 0.5, we wish to implement Buf for BytesMut, and there is a name conflict with Buf::take(). To prepare for it now, rename the current BytesMut::take() to BytesMut::split(). The docs help with the name choice: it's the same as bytes.split_to(bytes.len()).

Why worry about deprecation, etc... at this point? we can make breaking changes on master and move forward.


grpc header

springcloud project  communication via grpc,but the pinpoint has no data.
collector and agent：2.2.2

@yjqg6666 请教一下，我们集群内部的服务间调用，都是用的grpc接口，但是pinpoint页面没有采集到相关的接口信息，请问怎么操作呢？我们的版本是2.2.2

What's your agent config for gRPC ?
https://github.com/pinpoint-apm/pinpoint/blob/master/agent/src/main/resources/profiles/release/pinpoint.config#L1138-L1149

At first, the default configuration I used was not data, but after I adjusted it to true, it still no data.

At first, the default configuration I used was not data, but after I adjusted it to true, it still no data.

@yjqg6666 Can you check it for me again？

Then pls. check your sampling rate config, agent logs in agent directory for any errors. If http request are served, can you see it traced? Any errors on the collector side?

Can you extract a example project and make it available to us for testing if possible?

@yjqg6666  Our HTTP interface data is normal，The GRPC interface has no data

@yjqg6666  Have you seen it for me?

@yjqg6666  Hi，I built one separately, then brought the GRPC project in, and now Collector has this error

@DEWUIW Pls. check for errors on agent  & collector side. And if no further info found, then pls. provide an example project for testing/debug. Also you can capturing networking traffic sent to collector, port 9993 for grpc agent-collector transport and port 9996 for thrift agent-collector transport.

Http 2.0 ?
Pls. provide your agent config, esp. the port 9997 related config.

In agent config,I only change two positions：
profiler.transport.grpc.collector.ip=<IP_ADDRESS>
profiler.collector.ip=<IP_ADDRESS>
the "<IP_ADDRESS>" is the "pinpoint-collector-boot-2.2.2.jar" server's ip
the "9997" is the "pinpoint-web-boot-2.2.2.jar"

Disable the cluster feature on collector & web side by adding jvm property -Dcluster.enable=false. The first few lines of  the log are related to cluster.

collector:
nohup java -jar -Dcluster.enable=false -Dspring.profiles.active=release -Dpinpoint.zookeeper.address=localhost  /data/tools/pinpoint/pinpoint-web-boot-2.2.2.jar >/data/logs/pinpoint-web.log 2>&1 &
web:
nohup java -jar -Dcluster.enable=false -Dspring.profiles.active=release -Dpinpoint.zookeeper.address=localhost  /data/tools/pinpoint/pinpoint-collector-boot-2.2.2.jar >/data/logs/pinpoint-collector.log 2>&1 &
agent:
JAVA_OPTS:-javaagent:/app/pinpoint-agent/pinpoint-bootstrap-2.2.2.jar -Dpinpoint.agentId=${pinpoint_name} -Dpinpoint.applicationName=${pinpoint_name} -Dpinpoint.profiler.profiles.active=release"
The start script like this.But there's still no data.

In skywalking,the grpc interface'data is ok

@yjqg6666

Can you extract a example project and make it available to me/us for testing if possible?

可否提取一个简版的示例项目出来供测试或重现？


Support more non-String Map keys of obvious dart:core types

Partially addresses https://github.com/dart-lang/json_serializable/issues/396

@natebosch – PTAL


Orient DB Pagination along with Filtering specific key issue.

OrientDB Version: 2.1.19
Java Version: 1.8
OS: Windows 10
Expected behavior
I want to query records based on a specific  searchvalue within the document field and also want to implement pagination in the same query. Below is the query
select from <DOCUMENTNAME> let $tmp = (select from (select expand(<FIELDNAME>) from <DOCUMENTNAME>  ) where any() like '%<SEARCHVALUE>%' ) where <FIELDNAME> in $tmp.value SKIP <records-to-skip> LIMIT <max-records>

The above query return no result set. Is it  because that skip and limit does not work on temporary  variable?
Feedback will be appreciated as I am new to orientDB. Thank you
Actual behavior

Steps to reproduce

Hi @thanveeraqtharah
Could you please post a valid query and a script to create a sample schema/db?
It's really hard to help you knowing nothing about the domain and the query you are trying to do...
Thanks
Luigi

Sorry  I had posted the valid query , guess because I had used angle bracket within the query, it skipped the value. and below is the query.
select from DOCUMENTNAME let $tmp = (select from (select expand(FIELDNAME) from DOCUMENTNAME  ) where any() like '%SEARCHVALUE%' ) where FIELDNAME in $tmp.value SKIP 495 LIMIT 5

Ah, got it ;-)
Little hint, you can use Markdown syntax here, it helps a lot for code snippets: https://guides.github.com/features/mastering-markdown/
First of all: why v 2.1.19? It's not supported anymore and last 2.2.21 is much more performant and stable.
The query you posted seems to be correct, the problem could be in the any() expression (maybe an old bug?) or somewhere else. Did you try to execute the single sub-select statements and see what they return?
Thanks
Luigi

Thank you for the  suggesting Markdown syntax  as well for the newer stable version info. Definitely I ll take that into consideration.
When I tried to use 2.2.21 , i.e
artifactId :  orientdb-server
version : 2.2.21
the below exception was thrown
Exception in thread "main" java.lang.NoClassDefFoundError: com/orientechnologies/orient/core/security/OSecuritySystem
Now coming back to query part, if  I use the same query without SKIP and LIMIT i.e
select from DOCUMENTNAME let $tmp = (select from (select expand(FIELDNAME) from DOCUMENTNAME  ) where any() like '%SEARCHVALUE%' ) where FIELDNAME in $tmp.value
Its returns filtered query as expected. But when I try to implement pagination on it. It doesnt return any result set. So  its not them problem is in any() expression. So what might be the problem?

It's a good question, it's really hard to tell without a db to reproduce the problem.
You can try to narrow the scope of the problem adding a simple LIMIT 1, then a simple SKIP 1 and see if it still returns no records.
Any chance to have a screenshot or a dump of the query result without the skip/limit?
Thanks
Luigi

1.First of all, I wana thank you for your support and immediate responses, impressive. :-)
I got to know what was happening . As it was huge data and as SKIP and LIMIT way is slower, because OrientDB repeats the query and just skips the first X records from the result. and it was returning zero records because there was no records containing the searchvalue in the given skip and limit.
There is other way for pagination which is RID-LIMIT , but since im new to OrientDb, I am not sure what this RID represent. I mean earlier for SKIP value i used to give skipvalue =(pageno-1)*pagesize . Where pageno is nothing but on which page filter should be applied and pagesize is nothing but LIMIT value.
Can you please help me with this that my pagination will be faster.

For filtering with searchvalue, I am using "  any() like '%"+searchvalue+"%' ". I want to implement ignorecase of searchvalue. i.e the searchvalue shouldnt  be case sensitive. Can u help with this too ?

Thank you :)

Hi @thanveeraqtharah
The only other alternative for pagination (apart the two you mentioned above) is using another filter by a property (eg. an ID or a sequence number), index it and then do a range query on it.
About the case insensitive search, IMHO the best thing you can do is using a Lucene index: http://orientdb.com/docs/2.2.x/Full-Text-Index.html
Thanks
Luigi

Ok I will give you the clear picture of db.
1.There is Document By Name "ds_records".
2. This Document has 3 fields namely 'appid','sourceid' and 'records'
and I am saving the data to the above Document as shown below
private void saveRecords(String documentName,List<Map<String, String>`>' records, String appId, String sourceId) {
	for(Map`<String, String>` record : records){
		// create a document and save in db
		ODocument doc = new ODocument(documentName);
		doc.field("appid", appId);
		doc.field("sourceid", sourceId);
		doc.field("records", record);
		// SAVE THE DOCUMENT
		doc.save();
	}

}

where records field will save Map'<String,String>`.

So I want to filter all the records based on the searchvalue , which is inside records field i.e searchvalue in other words will be map value. How to create a index for the above db structure. And what about clusters?. Will that improve the search performance too? . Sorry as I am new to OrientDb, Im  not able get what you have said i.e "another filter by a property (eg. an ID or a sequence number), index it and then do a range query on it."

Feedback will be appriciated.

Thanks