Latest does not install cleanly on 2.5 of Grafana

# su -s /bin/sh -c "/usr/sbin/grafana-server --pidfile=/var/run/grafana-server.pid --config=/etc/grafana/grafana.ini cfg:default.paths.data=/var/lib/grafana cfg:default.paths.logs=/var/log/grafana" grafana
2016/04/05 03:44:39 [I] Starting Grafana
2016/04/05 03:44:39 [I] Version: 2.5.0-pre1, Commit: v2.1.2+549-g43ca50e, Build date: 2015-10-16 17:03:20 +0000 UTC
2016/04/05 03:44:39 [I] Configuration Info
Config files:
  [0]: /usr/share/grafana/conf/defaults.ini
  [1]: /etc/grafana/grafana.ini
Command lines overrides:
  [0]: default.paths.data=/var/lib/grafana
  [1]: default.paths.logs=/var/log/grafana
Paths:
  home: /usr/share/grafana
  data: /var/lib/grafana
  logs: /var/log/grafana

2016/04/05 03:44:39 [I] Database: sqlite3
2016/04/05 03:44:39 [I] Migrator: Starting DB migration
2016/04/05 03:44:39 [I] Creating json dashboard index for path: /var/lib/grafana/dashboards
2016/04/05 03:44:39 [plugins.go:62 walker()] [E] Failed to load plugin json file: /usr/share/grafana/public/app/plugins/datasource/zabbix/plugin.json,  err: Did not find pluginType property in plugin.json
2016/04/05 03:44:39 [I] Listen: http://<IP_ADDRESS>:3000

All I had to do is add pluginType: datasource as mentioned and the Zabbix plug-in loaded.
I had to copy dist/datasource-zabbix to /usr/share/grafana/public/app/plugins/datasource/zabbix.

Last plugin version not compatible with Grafana 2.5. Use Grafana 3.0 (now in beta).

That is a bummer, as I am not in a position to use the beta, will have to wait for 3.0 of Grafana to release.  Thanks.

No, problem, I think it will be soon.


LANG: update pkg data paths in moshpit

paired with https://github.com/bokulich-lab/q2-moshpit/pull/188

closing because i can't spell...


Not compatible with Puma

We've noticed a strange issue when using the Puma webserver instead of Webrick. Browser-sync will try to run on port 3000 (the same port the rails app is already being served on). I've noticed on your sample app that browser-sync runs on 3001. Gulp recognizes changes to files but the app does not live reload. It also causes serious memory and cpu drain on the computer.
Maybe there is a configuration change we need to make to Puma?

It appears the issue is that when you allow Puma to run multiple threads. When max threads is set to 1, the app behaves as originally intended


Remove net35 assemblies from nuspec templates

Description
Update the nuspec template files in the generator not to include net35 assemblies.
This is the start of updating the target frameworks used by the SDK (https://aws.amazon.com/blogs/developer/important-changes-coming-for-net-framework-3-5-and-4-5-targets-of-the-aws-sdk-for-net/), I'll try to create small PRs as much as possible to make reviews easier.

Note: All changes will go into the v4-development branch

Testing
Built the SDK locally, ran the buildtools/create-nuget-packages.ps1 script, and confirmed the generated nupkg files didn't include any net35 assets.
License

[X] I confirm that this pull request can be released under the Apache 2 license

Can we update this nuspec as well? https://github.com/aws/aws-sdk-net/blob/main/extensions/src/AWSSDK.Extensions.CrtIntegration/AWSSDK.Extensions.CrtIntegration.nuspec

Yes, I updated it in https://github.com/aws/aws-sdk-net/pull/3196/commits/60f41ea1a3ca7d4690dc9f0f11ee6b561097dc07 (I was planning to change the extensions project later - I even created a separate dspin/crt-extensions-targets branch - but doesn't hurt to update it now).


release: Update versions to 0.9.0

Signed-off-by: Kalya Subramanian<EMAIL_ADDRESS>
Description:
Update osm version to 0.9.0

Affected area:

Functional Area

New Functionality
[ ]

Documentation
[X]

Install
[ ]

CLI Tool
[ ]

Certificate Management
[ ]

Control Plane
[ ]

Ingress
[ ]

Egress
[ ]

Networking
[ ]

Observability
[ ]

SMI Policy
[ ]

Sidecar Injection
[ ]

Security
[ ]

Upgrade
[ ]

Tests
[ ]

CI System
[ ]

Demo
[ ]

Performance
[ ]

Other
[ ]

Please answer the following questions with yes/no.

Does this change contain code from or inspired by another project?

Did you notify the maintainers and provide attribution?
No

Is this a breaking change?
No

@shashankram The release branch has already been updated (#3589), but yes, it would be good to hold off on merging this until the v0.9.0 docker images this references have been published.

@shashankram The release branch has already been updated (#3589), but yes, it would be good to hold off on merging this until the v0.9.0 docker images this references have been published.

I am suggesting to create a cherry-pick from release-v0.9 to main for this either directly using github or manually through a PR created from a fork.

Oh, I see what you mean now. I'm not sure it's worth recreating this PR from a branch of a fork. If the branch gets deleted right after this PR is merged, does it make a difference?

Closed in favor of #3592


Restructure examples

Now adding a new example with just a few different things will require to create a new folder inside examples and add a whole structure with installing npm. What I would like to suggest is to have more examples that are connected for example for Web Tracer. We can have an extra folder where we could add just index.html and index.js .
For example
examples/web-tracer/examples
example1
example2
example3 ...
testing any examples in web would be possible by going to
http://localhost:8090/example1
http://localhost:8090/example2
...
of course example1 can be plugin-document-load , etc. etc.
The main advantage of this is that it will be easy to add many small examples that covers different issues without necessity of creating the whole new structure and installing all packages

What if we do a tree structure like:
# These examples only show RELEASED functionality
examples/0.2.0
examples/0.2.0/package.json # install packages using specific version (0.2.0)
examples/0.2.0/web-tracer

# these examples show potentially unreleased functionality.
examples/latest
examples/latest/package.json # install packages using relative file path (../../../packages/opentelemetry-node)
examples/latest/mysql

When we do a release, latest would be renamed to 0.x.0 and we would create a new latest with the new unreleased examples

I think keeping version in path will produce more confusion and extra work. Examples should always show the latest anyway and package.json is meant for that. This issue is only about having more small examples in the same folder to reuse the structure. I'm more concern just about naming for subfolder so if examples/web-tracer/examples/myFirstExample would be fine

oh I understand. I think we may be able to tackle both issues at the same time though if we do:
I understand what you mean by having the version in the path being confusing, maybe we just have a subfolder for unreleased examples?
I think it is confusing for new users that some of the examples showcase unreleased examples and some of them don't work if you just do yarn install.
# These examples only show RELEASED functionality
# package.json files in these examples use normal install from npm
examples/
examples/web-tracer
examples/web-tracer/example1
examples/web-tracer/example2

# these examples show potentially unreleased functionality.
# the package.json files in this directory may install some packages using relative paths
examples/unreleased
examples/unreleased/mysql
examples/unreleased/mysql/example1
examples/unreleased/mysql/example2
``

At least web-tracer examples seem to work like @obecny described so can this be closed? @dyladan


Pseudoinverse doesn't work for some arrays

The pseudoinverse doesn't work for some arrays:
xt::xtensor<float, 2> data {{1}};
xt::linalg::pinv(data);

gives
 ** On entry to SGESDD parameter number  5 had an illegal value

and
xt::xtensor<float, 2> data {{1, 2}};
xt::linalg::pinv(data);

gives
 ** On entry to SGESDD parameter number  8 had an illegal value

The expected behavior is
>>> data = array([[1]])
>>> linalg.pinv(data)
array([[1.]])
>>> data = array([[1, 2]])
>>> linalg.pinv(data)
array([[0.2],
       [0.4]])

Indeed there seems to be a limitation in the way our SVD function is currently implemented.
Need to fix this (btw. I think this issue belongs technically to the xtensor-blas repo)

Hi @schra thanks a lot for opening this issues. It led to fixing a couple of significant issues with our current SVD implementation in xtensor-blas.
Should work with this PR: https://github.com/QuantStack/xtensor-blas/pull/53

The fix has been merged into master, and we'll make a release very soon.


Suggestion - show how to add a user to a list towards the top of the README

I believe the following is a rather common use case:

sign up for MailChimp
create a list
subscribe users to this list when they sign up

It takes a few minutes to figure out the solution:
client = Mailchimp(...)
client.member.create('<list_id>', {
    'email_address'<EMAIL_ADDRESS>    'status': 'subscribed',
    'merge_fields': {
        'FNAME': 'John',
        'LNAME': 'Doe',
    },
})

The onboarding experience would be smoother if the README showed that example (or a similar one).
I hope this feedback helps!

Thanks for this one, you are right !


TestWorkloadHealthChecker_PerformApplicationHealthCheck test flake

https://prow.istio.io/view/gs/istio-prow/logs/unit-tests_istio_postsubmit/1473088792515579904
I can reproduce it but don't see any easy fixes. I think what happens is the port we chose is used by something else, so we end up dialing some other server which is 'healthy'. This is because NewPortManagerOrFail doesn't actually truely reserve a port, it just finds a free port.

https://prow.istio.io/view/gs/istio-prow/pr-logs/pull/istio_istio/39625/unit-tests_istio/1541443662322339840


Fix runInsert variants to not throw errors when results are correct

Pretty simple mistake. Running runInsert1 was throwing when it shouldn't have been and I determined it to be this.

(Related thought... doing a length check on lists is a bit costly. Any chance you'd be open to updating the code to take Foldables instead so something more efficient like a Vector could be passed in instead?)

Thanks! Ideally we wouldn't be calculating nAffected at all, changing to vector won't solve that part. We need to be smarter when comparing against nExpected. We use lists because that's what we get from opaleye, and we leave it to the callers to convert to something else if so desired, and it leads to better type inference as well.


Update README with ORACLE_DOWNLOAD_DIR description

After ba6220959305306a9bda9dcf7cd9e4531addc4fe and 0b0608af7661637474ceefc2df5d261ab54c3aa6, ORACLE_DOWNLOAD_DIR variable is ready to be used for caching on Travic CI.
This PR is to add this to the README.

Would be nice to have that feature documented and released

I'm uncertain about releasing caching without #19.

I'm uncertain about releasing caching without #19.

I take it back. Checksums are not necessary to safely cache.


Error with chr_model.pth is not a checkpoint file

Hi, Thank you for reporting this useful software!
When I run autohic.py，I got this error in log.txt:
│ /home/miniconda3/envs/autohic/lib/python3.9/site-packages/mmcv/runner │
│ /checkpoint.py:261 in load_from_local                                        │
│                                                                              │
│   258 │   """                                                                │
│   259 │                                                                      │
│   260 │   if not osp.isfile(filename):                                       │
│ ❱ 261 │   │   raise IOError(f'{filename} is not a checkpoint file')          │
│   262 │   checkpoint = torch.load(filename, map_location=map_location)       │
│   263 │   return checkpoint                                                  │
│   264                                                                        │
│                                                                              │
│ ╭───────────────────────────────── locals ─────────────────────────────────╮ │
│ │     filename = '/home/AutoHic/Schistosoma_haematobium_test/chr_… │ │
│ │ map_location = 'cpu'                                                     │ │
│ ╰──────────────────────────────────────────────────────────────────────────╯ │
╰──────────────────────────────────────────────────────────────────────────────╯
OSError: /home/AutoHic/Schistosoma_haematobium_test/chr_model.pth is not
a checkpoint file
The pre-trained model files were downloaded from Google Drive (error_model.pth and chr_model.pth). The reference genome and hic data are sh.fa and SRR16086854.
To resolve this issue, I attempted to verify the file size, confirm the pytorch version(1.10.1) and re-download the file but the error persisted.
I would be grateful for any assistance with this error!

What machine are you running AutoHiC on, and upload your cft-autohic.txt file.

What machine are you running AutoHiC on, and upload your cft-autohic.txt file.

Here is my log.txt:
log.txt

This is very strange. From your  log.txt, you have run AutoHiC more than once. If you need to run it again, please delete the previous results. Also, the error detection is running normally, only the chromosome number inference is having problems. I suspect that your chr_model.pth file has not been downloaded completely. It is recommended that you download it again, delete the previous results and try again.

This is very strange. From your  log.txt, you have run AutoHiC more than once. If you need to run it again, please delete the previous results. Also, the error detection is running normally, only the chromosome number inference is having problems. I suspect that your chr_model.pth file has not been downloaded completely. It is recommended that you download it again, delete the previous results and try again.

Thank you for your suggestions.  I will try again.

This is very strange. From your  log.txt, you have run AutoHiC more than once. If you need to run it again, please delete the previous results. Also, the error detection is running normally, only the chromosome number inference is having problems. I suspect that your chr_model.pth file has not been downloaded completely. It is recommended that you download it again, delete the previous results and try again.

Hello, sorry to bother you again, I re-downloaded the chr_model.pth file and compared it with the previous download using md5sum and found that they are identical. Then, running it again still has the same issue. Could you please provide me with some new download links? I will try it again.

We have never encountered this situation. We recommend that you reinstall AutoHiC using conda

Closing due to no activity for 2 weeks. Feel free to reopen if any guidance is needed.


Passing component to light param instead of image url

I'm working on a next.js project, where images are automatically sized and optimized on the backend. Being able to pass a Component to the light parameter would be amazing to be able to use those images to help optimize between mobile and desktop.

@andrewscofield What attributes would those components have? Would they be img tags or something else? Can you elaborate more? Thanks

Fixed by https://github.com/cookpete/react-player/pull/1405 I think?

Yes, this looks awesome! Thanks @idiglove for working on this and @cookpete for getting it merged and letting me know about it.


fix: propagate InterruptedException from JLine.readLine

Motivation:
Cannot exit from InteractionService.readLine
Modification:
Remove try/catch of InterreuptedException mapped to None in JLine.readLine

Hi @tpetillot,
Thank you for your contribution! We really value the time you've taken to put this together.
Before we proceed with reviewing this pull request, please sign the Lightbend Contributors License Agreement:
https://www.lightbend.com/contribute/cla

related issue: https://github.com/sbt/sbt/issues/6784


SKPaymentTransactionObserver: Continue App Store purchase

Implements the continue App Store transaction delegate method.
- (BOOL)paymentQueue:(SKPaymentQueue *)queue shouldAddStorePayment:(SKPayment *)payment forProduct:(SKProduct *)product
I followed the same pattern as the other delegate methods.
Let me know if I missed something.

@mattt are you still maintaining this project to merge open pull requests?


Tailscale Serve

Hello,
The tailscale serve command seems to use a control server endpoint that is not implemented in ionscale.
Can this be added?
Thanks a lot,
Mr. Hax

available in release v0.10.0-rc1 and v0.10.0


CRAYSAT-1692: Update logging in sat bootsys

Summary and Scope
This change logs all BOS session statuses together at the end of a sat bootsys run. Sessions with failed components will be logged as warnings, and all other sessions will be logged as info messages. Sessions with error summaries will have the error messages appended to their log messages.
Issues and Related PRs

Resolves CRAYSAT-1692

Testing
Proper end-to-end testing still needed, I will complete this before merging.
Pull Request Checklist

[x] Version number(s) incremented, if applicable
[x] Copyrights updated
[x] License file intact
[x] Target branch correct
[x] CHANGELOG.md updated
[x] Testing is appropriate and complete, if applicable
[x] HPC Product Announcement prepared, if applicable

Regression testing here: https://gist.github.com/jack-stanek-hpe/87e6e15f953991a7ec7880afbc8b4164

See updated logging messages in the error case in the gist: https://gist.github.com/jack-stanek-hpe/87e6e15f953991a7ec7880afbc8b4164#file-gistfile1-txt-L160-L169


Add missing flushFinderCache method to ViewFactory contract

Add missing flushFinderCache() method to Illuminate\Contracts\View\Factory interface causing red squiggle as shown in screenshot below in Markdown.php.

This feels like such an implementation detail on the Factory that I don't think it should be in the interface tbh - sorry. Perhaps Markdown should depend on a concrete instance or we can just ignore this error.


What's to be set as Authorization callback URL for a github authentication?

Description
the docs seem to lack information how the Authorization callback URL has to be configured when setting up a GitHub application as authentication backend (https://github.com/settings/applications/…). i'll amend it to the docs when resolved.

Hi Guys,
I have just successfully added my Gitea installation so that you can login using github credentials.
Its very similar to how Jenkins is done and heres the solution.
First login to github and create a new Github app for your org.
Next use the following:
GitHub App name (mgmt.example.com/git)
Homepage URL (https://mgmt.example.com/git).
User authorization callback URL (https://mgmt.example.com/git/user/oauth2/github/callback)
Webhook URL (https://mgmt.example.com/git)
Save the changes and create the private key.
Note: Webhook URL shouldn't be needed but wasn't accepting without putting something in here.
Next install the github app.
This concludes the github part.
Now login to your gitea install https://mgmt.example.com/git and goto site administration.  Add a new authentication source and use the following details.
Authentication Name (github)
OAuth2 Provider (GitHub)
Client ID (Key) (enter your ID found on your GitHub app you created)
Client Secret (enter your Secret found on your GitHub app you created)
Now active the changes and open a private browser window and try logging into your Gitea install.  It should now have an option to login as GitHub user, select this and enter your github creds, it then should ask you to login with your usual Gitea creds so that it can link.  This only needs to be done once.
Thats all folks, enjoy GitHub based auth :)

@soakes your knowledge is certainly better re-usable if added to the docs. ;-)

Will see what I can do when I get a few minutes or someones welcome to add for us.

http://localhost
https://codelabs.developers.google.com/codelabs/flutter-github-graphql-client/index.html?index=..%2F..index#3


With sanitizeInput update is immediately called even without user interaction

When I specify sanitizeInput, there is immediately a call to update. That is particularly bad in situations with a disabled text input.
E.g.
{{one-way-input layer.startEffect.duration disabled=layer.startEffect update=(action (mut layer.startEffect.duration))}}
Throws an error with sanitizeInput, because layer.startEffect does not yet exist.
There is also a situation where sanitizeInput causes the creation of 40 records just because the user opens a tab, where the inputs are located. By doing this - without typing anything - the update calls are fired immediately.
Without sanitizeInput everything is back to normal

More investigation on this: the problem is undefined !== null. I want to cast empty input fields to null on sanitizeInput. That causes the update. Regardless: what I expected was sanitize only driven by user interaction.
I fixed it this way:
(components/one-way-input.js)
`
import Ember from 'ember';
import OneWayInput from 'ember-one-way-controls/components/one-way-input';
import { invokeAction } from 'ember-invoke-action';
const {
Component,
assert,
computed,
get,
isNone,
run: { schedule }
} = Ember;
export default OneWayInput.extend({
_processNewValue(rawValue, noUpdate) {
    let value = invokeAction(this, 'sanitizeInput', rawValue);
    console.log(get(this, '_value'), value, rawValue);

    if (!noUpdate && get(this, '_value') !== value) {
        invokeAction(this, 'update', value);
    }
    schedule('afterRender', this, '_syncValue');
},

didReceiveAttrs() {
    this.__proto__._super(...arguments);
    this._processNewValue(get(this, '_value'), true);
}

});
`

I removed sanitizeInput and the  processNewValue call in the didReceiveAttrs hook. This should fix your problem.

@martndemus thanks for your fixes! :v:


Fixed #20629 -- Rephrased admonition regarding custom user models

https://code.djangoproject.com/ticket/20629

Considering the experience that most people have made with adding a custom user model at a later stage, what's your opinion on rephrasing the admonition to be more supportive towards custom user models. Even if you don't know you need one right now, having to migrate at a later stage is a hell of a lot more complex than just having a plain custom user model in an accounts app.

This is already a try of being less scary and more supportive of custom user models as per the original ticket – I think this is a good idea. While the Django docs state clearly that starting with a custom user model is recommended … they do so in the custom user model docs. Once you've found those, it's probably too late, though.
Anyways, we might also consider inlining the admonition below the paragraph that follows it. Removing the admonition status in itself makes the comments less scary, I'd say. Opinions?

Incorporating the notes about the model design into the surrounding paragraphs is fine with me. Here's different shot at a rewrite (also removing the "Django expects your custom ..." paragraph):

When you start with a custom user model please consider the database design you are planning to use. On the one hand, keeping all user related information in one model means you don't have to fetch a related model with further information from the database. This removes possible database joins but comes with the cost of large user models. On the other hand, it may be more suitable to store app-specific user information in a model that has a relation with your custom user model. This allows each app to specify its own user data requirements without potentially conflicting with or breaking assumptions by other apps. It also means that you would keep your user model as simple as possible, following the minimum requirements Django expects custom user models to meet.

This paragraph would assume that one has already made the decision to use a custom user model. It removes the whole should or shouldn't. Instead it focuses on how to design the custom user model, which is what the section is about, IMO.

Thank you for your review and suggestions! I drafted a mix of our solutions – I'd be happy to adjust it some more, if anybody has suggestions. I think it's alright the way it is, but it's a bit long/unwieldy, so finding a more concise phrasing might be better. (I'll have another go in a day or two, if nobody else has any ideas.)

I like it as well. Thanks. I'll mark it as ready for commit so Carlton or Mariusz have a final look.

@rixx @MarkusH I pushed some final edits. Can you take a look?

@felixxm Looks good to me, thank you.

@rixx Thanks!


Stopped working in Flutter 3.10 - accentColor deprecated

Describe the bug
As Flutter 3.10 removed accentColor, the package stopped working.
This should be fixed by #102
To Reproduce
Steps to reproduce the behavior:

Depend on this package
Try to run app
See error

Expected behavior
The app runs properly
Desktop (please complete the following information):

OS: Windows 11
Browser: Not Applicable / Run in Android 13 Emulator
Version: Flutter 3.10

Smartphone (please complete the following information):

Device: Pixel 6
OS: Android 13
Browser: Chrome

Any update when it will be fixed?

thanks for the comments and the pull requests. v1.2.1 has just been published, which includes the changes for colorScheme.accentColor


AZ CLI does not install SOCKS support by default

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az *
Errors:
│ Error: Error obtaining Authorization Token from the Azure CLI: Error parsing json result from the Azure CLI: Error waiting for the Azure CLI: exit status 1: ERROR: The command failed with an unexpected error. Here is the traceback:
│ ERROR: Missing dependencies for SOCKS support.
│ Traceback (most recent call last):
│   File "/usr/local/Cellar/azure-cli/2.26.1/libexec/lib/python3.8/site-packages/knack/cli.py", line 231, in invoke
│     cmd_result = self.invocation.execute(args)
│   File "/usr/local/Cellar/azure-cli/2.26.1/libexec/lib/python3.8/site-packages/azure/cli/core/commands/__init__.py", line 657, in execute
│     raise ex
│   File "/usr/local/Cellar/azure-cli/2.26.1/libexec/lib/python3.8/site-packages/azure/cli/core/commands/__init__.py", line 720, in _run_jobs_serially
│     results.append(self._run_job(expanded_arg, cmd_copy))
│   File "/usr/local/Cellar/azure-cli/2.26.1/libexec/lib/python3.8/site-packages/azure/cli/core/commands/__init__.py", line 691, in _run_job
│     result = cmd_copy(params)
│   File "/usr/local/Cellar/azure-cli/2.26.1/libexec/lib/python3.8/site-packages/azure/cli/core/commands/__init__.py", line 328, in __call__
│     return self.handler(*args, **kwargs)
│   File "/usr/local/Cellar/azure-cli/2.26.1/libexec/lib/python3.8/site-packages/azure/cli/core/commands/command_operation.py", line 121, in handler
│     return op(**command_args)
│   File "/usr/local/Cellar/azure-cli/2.26.1/libexec/lib/python3.8/site-packages/azure/cli/command_modules/profile/custom.py", line 77, in get_access_token
│     creds, subscription, tenant = profile.get_raw_token(subscription=subscription, resource=resource, tenant=tenant)
│   File "/usr/local/Cellar/azure-cli/2.26.1/libexec/lib/python3.8/site-packages/azure/cli/core/_profile.py", line 698, in get_raw_token
│     creds = self._creds_cache.retrieve_token_for_user(username_or_sp_id,
│   File "/usr/local/Cellar/azure-cli/2.26.1/libexec/lib/python3.8/site-packages/azure/cli/core/_profile.py", line 1104, in retrieve_token_for_user
│     token_entry = context.acquire_token(resource, username, _CLIENT_ID)
│   File "/usr/local/Cellar/azure-cli/2.26.1/libexec/lib/python3.8/site-packages/adal/authentication_context.py", line 145, in acquire_token
│     return self._acquire_token(token_func)
│   File "/usr/local/Cellar/azure-cli/2.26.1/libexec/lib/python3.8/site-packages/adal/authentication_context.py", line 128, in _acquire_token
│     return token_func(self)
│   File "/usr/local/Cellar/azure-cli/2.26.1/libexec/lib/python3.8/site-packages/adal/authentication_context.py", line 143, in token_func
│     return token_request.get_token_from_cache_with_refresh(user_id)
│   File "/usr/local/Cellar/azure-cli/2.26.1/libexec/lib/python3.8/site-packages/adal/token_request.py", line 349, in get_token_from_cache_with_refresh
│     return self._find_token_from_cache()
│   File "/usr/local/Cellar/azure-cli/2.26.1/libexec/lib/python3.8/site-packages/adal/token_request.py", line 127, in _find_token_from_cache
│     return self._cache_driver.find(cache_query)
│   File "/usr/local/Cellar/azure-cli/2.26.1/libexec/lib/python3.8/site-packages/adal/cache_driver.py", line 198, in find
│     return self._refresh_entry_if_necessary(entry,
│   File "/usr/local/Cellar/azure-cli/2.26.1/libexec/lib/python3.8/site-packages/adal/cache_driver.py", line 177, in _refresh_entry_if_necessary
│     return self._refresh_expired_entry(entry)
│   File "/usr/local/Cellar/azure-cli/2.26.1/libexec/lib/python3.8/site-packages/adal/cache_driver.py", line 153, in _refresh_expired_entry
│     token_response = self._refresh_function(entry, None)
│   File "/usr/local/Cellar/azure-cli/2.26.1/libexec/lib/python3.8/site-packages/adal/token_request.py", line 137, in _get_token_with_token_response
│     return self._get_token_with_refresh_token(refresh_token, resource, None)
│   File "/usr/local/Cellar/azure-cli/2.26.1/libexec/lib/python3.8/site-packages/adal/token_request.py", line 341, in _get_token_with_refresh_token
│     return self._oauth_get_token(oauth_parameters)
│   File "/usr/local/Cellar/azure-cli/2.26.1/libexec/lib/python3.8/site-packages/adal/token_request.py", line 112, in _oauth_get_token
│     return client.get_token(oauth_parameters)
│   File "/usr/local/Cellar/azure-cli/2.26.1/libexec/lib/python3.8/site-packages/adal/oauth2_client.py", line 263, in get_token
│     resp = requests.post(token_url.geturl(),
│   File "/usr/local/Cellar/azure-cli/2.26.1/libexec/lib/python3.8/site-packages/requests/api.py", line 119, in post
│     return request('post', url, data=data, json=json, **kwargs)
│   File "/usr/local/Cellar/azure-cli/2.26.1/libexec/lib/python3.8/site-packages/requests/api.py", line 61, in request
│     return session.request(method=method, url=url, **kwargs)
│   File "/usr/local/Cellar/azure-cli/2.26.1/libexec/lib/python3.8/site-packages/requests/sessions.py", line 542, in request
│     resp = self.send(prep, **send_kwargs)
│   File "/usr/local/Cellar/azure-cli/2.26.1/libexec/lib/python3.8/site-packages/requests/sessions.py", line 655, in send
│     r = adapter.send(request, **kwargs)
│   File "/usr/local/Cellar/azure-cli/2.26.1/libexec/lib/python3.8/site-packages/requests/adapters.py", line 412, in send
│     conn = self.get_connection(request.url, proxies)
│   File "/usr/local/Cellar/azure-cli/2.26.1/libexec/lib/python3.8/site-packages/requests/adapters.py", line 309, in get_connection
│     proxy_manager = self.proxy_manager_for(proxy)
│   File "/usr/local/Cellar/azure-cli/2.26.1/libexec/lib/python3.8/site-packages/requests/adapters.py", line 182, in proxy_manager_for
│     manager = self.proxy_manager[proxy] = SOCKSProxyManager(
│   File "/usr/local/Cellar/azure-cli/2.26.1/libexec/lib/python3.8/site-packages/requests/adapters.py", line 47, in SOCKSProxyManager
│     raise InvalidSchema("Missing dependencies for SOCKS support.")
│ requests.exceptions.InvalidSchema: Missing dependencies for SOCKS support.

To Reproduce:
Run any Azure CLI command with ALL_PROXY set to a SOCKS5 proxy

Put any pre-requisite steps here...
export ALL_PROXY=socks5h://<host>:<port>
az login

Expected Behavior
Command should complete as expected
Environment Summary
macOS-10.15.7-x86_64-i386-64bit
Python 3.8.11
Installer: HOMEBREW

azure-cli 2.26.1

Extensions:
aks-preview 0.5.14
azure-devops 0.18.0
resource-graph 2.0.0
custom-providers 0.2.0
ssh 0.1.5
interactive 0.4.4
costmanagement 0.1.1

Additional Context

@jiasli for awareness

Adding requests[socks] to the requirements should do the trick (tested on Mac via  pip3 install requests[socks] --prefix /usr/local/Cellar/azure-cli/2.26.1/ --ignore-installed )

@grahamhayes, Azure CLI doesn't install requests[socks] by default:
https://github.com/Azure/azure-cli/blob/a46fb8cee0234e7970d75d1bbbeb0b86339e998d/src/azure-cli-core/setup.py#L60
as it will introduce additional dependencies for users who don't use SOCKS5 proxy.
And yes, you may install requests[socks] on-demand to Azure CLI's installation folder:
https://docs.python-requests.org/en/master/user/advanced/#socks
python -m pip install requests[socks]

@jiasli - yeah, that is true, but with the default installation methods used by the CLI avoid using the system python site-packages (brew on OSX, an apt package that ships an entirely new python binary on ubuntu for example), the installation of the extra package is difficult
e.g. - sudo /opt/az/bin/python3 /opt/az/bin/pip3 install requests[socks]==2.25.1 --target=/opt/az/lib/python3.6/site-packages/ on ubuntu  and pip3 install requests[socks] --prefix /usr/local/Cellar/azure-cli/2.26.1/ --ignore-installed OSX.
This also means each time the az cli is updated, you have to re install.
For users behind a SOCKS proxy (e.g. high security environments, managed enterprise environments) - access to pypi is also a problem.
With the advent of private link services, SOCKS proxies via SSH are a very useful tool for interacting with services without having to set up DNS forwarding, VPNs / Express Routes and VNet peerings.
This adds a quite small dependancy (especially as we ship copies of everything including an interpreter in some cases).

Thanks @grahamhayes for the detailed explanation. Let's work on the PR https://github.com/Azure/azure-cli/pull/18931 instead.


[JSS][NextJS] - fix: Prevent passing internalLinkMatcher prop

Prevented passing internalLinkMatcher prop to React Link component as it is an invalid HTML element prop.
Description / Motivation
While attempting to use a custom link matcher (/^\/|^\#/g) to allow internal anchor links, an error occurred for all non-internal link values used in the same component.
When a non-internal link is detected, it attempts to pass all props, including the unused internalLinkMatcher to the JSS React Link component, which then attempts to print it onto the anchor link, resulting in the following error:
Warning: React does not recognize the `internalLinkMatcher` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `internallinkmatcher` instead. If you accidentally passed it from a parent component, remove it from the DOM element.

We can prevent this error by simply not passing the prop to the JSS React Link component.
Testing Details
Tested by utilizing forked version of JSS in existing project.
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation update (non-breaking change; modified files are limited to the /docs directory)

Hello @bhgeorge. This seems good to me. Can you please change the target branch to dev?

@CobyPear Rebased and changed target. Thanks!

@bhgeorge please check the following lint error:
  51:10  error  Replace `<ReactLink·{...htmlLinkProps}·editable={editable}·showLinkTextWithChildrenPresent={showLinkTextWithChildrenPresent}·/>` with `(␍⏎····<ReactLink␍⏎······{...htmlLinkProps}␍⏎······editable={editable}␍⏎······showLinkTextWithChildrenPresent={showLinkTextWithChildrenPresent}␍⏎····/>␍⏎··)`  prettier/prettier

You can run npm run lint --fix in the offending package to fix this.
Thinking about this a bit more, I wonder if another solution to this could be removing the link matcher from the props instead of changing the shape of the returned props, just to keep it easier to maintain in the future. Any thoughts @Sitecore/jss-dev-reviewers ?

@bhgeorge please check the following lint error:
  51:10  error  Replace `<ReactLink·{...htmlLinkProps}·editable={editable}·showLinkTextWithChildrenPresent={showLinkTextWithChildrenPresent}·/>` with `(␍⏎····<ReactLink␍⏎······{...htmlLinkProps}␍⏎······editable={editable}␍⏎······showLinkTextWithChildrenPresent={showLinkTextWithChildrenPresent}␍⏎····/>␍⏎··)`  prettier/prettier

You can run npm run lint --fix in the offending package to fix this.
Thinking about this a bit more, I wonder if another solution to this could be removing the link matcher from the props instead of changing the shape of the returned props, just to keep it easier to maintain in the future. Any thoughts @Sitecore/jss-dev-reviewers ?

Agree, removing the internalLinkMatcher property from props before passing on to <ReactLink /> seems like it would be preferred. Bit more future-proof. Would also be great to cover this issue with a unit test. @bhgeorge if you want to take a stab at it feel free; otherwise we can contribute that.

@bhgeorge please check the following lint error:
  51:10  error  Replace `<ReactLink·{...htmlLinkProps}·editable={editable}·showLinkTextWithChildrenPresent={showLinkTextWithChildrenPresent}·/>` with `(␍⏎····<ReactLink␍⏎······{...htmlLinkProps}␍⏎······editable={editable}␍⏎······showLinkTextWithChildrenPresent={showLinkTextWithChildrenPresent}␍⏎····/>␍⏎··)`  prettier/prettier

You can run npm run lint --fix in the offending package to fix this.
Thinking about this a bit more, I wonder if another solution to this could be removing the link matcher from the props instead of changing the shape of the returned props, just to keep it easier to maintain in the future. Any thoughts @Sitecore/jss-dev-reviewers ?

Agree, removing the internalLinkMatcher property from props before passing on to <ReactLink /> seems like it would be preferred. Bit more future-proof. Would also be great to cover this issue with a unit test. @bhgeorge if you want to take a stab at it feel free; otherwise we can contribute that.

I will go ahead and change the implementation and add a unit test.


Tflite ops: BatchMatMul, TensorListReserve, TensorListSetItem, TensorListStack

System information

Linux Ubuntu 18.04
TensorFlow installed from source
TensorFlow version 2.1.0

Provide the text output from tflite_convert
Some of the operators in the model are not supported by the standard TensorFlow Lite runtime. If those are native TensorFlow operators, you might be able to use the extended runtime by passing --enable_select_tf_ops, or by setting target_ops=TFLITE_BUILTINS,SELECT_TF_OPS when calling tf.lite.TFLiteConverter(). Otherwise, if you have a custom implementation for them you can disable this error with --allow_custom_ops, or by setting allow_custom_ops=True when calling tf.lite.TFLiteConverter(). Here is a list of builtin operators you are using: ADD, CONCATENATION, CONV_2D, COS, DIV, EXPAND_DIMS, FULLY_CONNECTED, MAX_POOL_2D, MEAN, MUL, NEG, PACK, PAD, RESHAPE, SIN, SQRT, SQUEEZE, STRIDED_SLICE, SUB, SUM. Here is a list of operators for which you will need custom implementations: BatchMatMul, TensorListReserve, TensorListSetItem, TensorListStack.

I try to convert generator model from here: https://github.com/russoale/hmr2.0/blob/master/src/main/generator.py
Can you please give me an estimate when such operations as
BatchMatMul, TensorListReserve, TensorListSetItem, TensorListStack will be transferred to tflite?
Looking forward to hearing from you!

TensorListReserve, TensorListSetItem, TensorListStack ops will be disappeared when you have a fixed size in your model, for example, batch size.
BatchMatMul can be supported via Select TF ops and we offer a selective build mechanism for Select TF ops for slim binary size deployment.
https://www.tensorflow.org/lite/guide/ops_select
https://www.tensorflow.org/lite/guide/reduce_binary_size

Thanks a lot for your help Jae!
I have set up the input shape for my model via the attached code, nevertheless, I still get the error that TensorList operations are used. Can you please explain the proper way to set a fixed size in the model.
`
import sys
sys.path.append("hmr2.0/src/")
import tensorflow as tf
from main.model import Model
from notebooks.vis_util import preprocess_image
from main.config import Config
def main():
model = Model()
config = Config()
generator = model.generator
original_img, input_img, params = preprocess_image('hmr2.0/src/notebooks/images/coco4.png', \
                                                    config.ENCODER_INPUT_SHAPE[0])

if len(tf.shape(input_img)) is not 4:
    # [224, 224, 3] -> [1, 224, 224, 3]
    input_img = tf.expand_dims(input_img, 0)
generator._set_inputs(input_img)

converter = tf.lite.TFLiteConverter.from_keras_model(generator)
converter.target_spec.supported_ops = [
    tf.lite.OpsSet.TFLITE_BUILTINS, # enable TensorFlow Lite ops.
    tf.lite.OpsSet.SELECT_TF_OPS # enable TensorFlow ops.
]
tflite_model = converter.convert()

if name == 'main':
main()
`

It happens when I try to transfer the following model:
class Regressor(tf.keras.Model):
    def __init__(self):
        super(Regressor, self).__init__(name='regressor')
        self.config = Config()

        self.mean_theta = tf.Variable(model_util.load_mean_theta(), name='mean_theta', trainable=True)

        self.fc_one = layers.Dense(1024, name='fc_0')
        self.dropout_one = layers.Dropout(0.5)
        self.fc_two = layers.Dense(1024, name='fc_1')
        self.dropout_two = layers.Dropout(0.5)
        variance_scaling = tf.initializers.VarianceScaling(.01, mode='fan_avg', distribution='uniform')
        self.fc_out = layers.Dense(85, kernel_initializer=variance_scaling, name='fc_out')

    def call(self, inputs, **kwargs):
        batch_size = inputs.shape[0] or self.config.BATCH_SIZE
        shape = (batch_size, 2048)
        assert inputs.shape[1:] == shape[1:], 'shape mismatch: should be {} but is {}'.format(shape, inputs.shape)

        batch_theta = tf.tile(self.mean_theta, [batch_size, 1])
        thetas = tf.TensorArray(tf.float32, self.config.ITERATIONS)
        for i in range(self.config.ITERATIONS):
            # [batch x 2133] <- [batch x 2048] + [batch x 85]
            total_inputs = tf.concat([inputs, batch_theta], axis=1)
            batch_theta = batch_theta + self._fc_blocks(total_inputs, **kwargs)
            thetas = thetas.write(i, batch_theta)

        return thetas.stack()

    def _fc_blocks(self, inputs, **kwargs):
        x = self.fc_one(inputs, **kwargs)
        x = tf.nn.relu(x)
        x = self.dropout_one(x, **kwargs)
        x = self.fc_two(x, **kwargs)
        x = tf.nn.relu(x)
        x = self.dropout_two(x, **kwargs)
        x = self.fc_out(x, **kwargs)
        return x

I managed to convert the model using the following code:
def get_tflite_model(model, model_name):
    converter = tf.lite.TFLiteConverter.from_keras_model(model)
    converter.experimental_new_converter = False
    converter.allow_custom_ops=True
    converter.target_spec.supported_ops = [
        tf.lite.OpsSet.TFLITE_BUILTINS, # enable TensorFlow Lite ops.
        tf.lite.OpsSet.SELECT_TF_OPS # enable TensorFlow ops.
    ]
    tflite_model = converter.convert()

Can you please let me know whether it is a proper solution?

Was able to reproduce the issue with TF v2.3 and TF-nightly. Please find the gist of it here. Thanks!

@amahendrakar Thanks for your reply!
Yes, I got the same error when I run my model using tf 2.3, I was rather wondering whether it is possible to fix the current error in tf2.1 the way @abattery mentioned

As I found it here the reason of this error is the same: all shapes have to be fixed, but I have already set up the input shapes.

@amahendrakar looking forward to hear from you! Thanks in advance!

@whiteRa2bit have you set a fixed batch size as well? Usually keras models have non-fixed size if you have not set it explicitly.


[BlockMediator] [Refactor] BM.Set() to be Synchronous

Originally the set() of BlockMediator was designed to be async, so that a global update won't be blocked by one bad consumer running a slow update function. However, it's more complicated and confusing than it is necessary, and the complexities should be shipped to the consuming end. As long as we maintain good control of the repo we don't need this feature. No blocks currently depend on the async nature of set(), so nothing should really be impacted by this PR.
Test URLs:

Before: https://stage--express--adobecom.hlx.page/express/
After: https://block-mediator-sync-set--express--adobecom.hlx.page/express/?lighthouse=on

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 36.66%. Comparing base (e4db728) to head (2ed3a59).

Additional details and impacted files
@@            Coverage Diff             @@
##            stage     #743      +/-   ##
==========================================
- Coverage   36.71%   36.66%   -0.06%
==========================================
  Files         132      132
  Lines       25713    25713
==========================================
- Hits         9440     9427      -13
- Misses      16273    16286      +13

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


missing ) after argument list

Challenge http://www.freecodecamp.com/challenges/waypoint-target-the-parent-of-an-element-using-jquery has an issue. Please describe how to reproduce it, and include links to screenshots if possible.
First checklist item on this page just says "missing ) after argument list" no matter what's in the code window.

https://github.com/FreeCodeCamp/FreeCodeCamp/issues/1912

Closing as duplicate
Please see https://github.com/FreeCodeCamp/FreeCodeCamp/wiki/Searching-for-Your-Issue-on-Github


GroupMerging_old function

Hi, thanks for your code! But when I run generate_result.py, the functionGroupMerging_old() missed. I found a similar function called GroupMerging in test_util.py, I use it instead. But in function BlockMergin(), a bug happens as follow:
File "/SGPN/utils/test_utils.py", line 182, in BlockMerging()
if volume[xx,yy,zz]!=-1 and volume_seg[xx,yy,zz]==groupseg[grouplabel[i]]:
ValueError: The truth value of an array with more than one element is ambiguous. Use a.any() or a.all()
May you help me solve it? thanks a lot!!
By the way, when i run valid.py, the first number of each line is nan. Does it mean no instance detected?

@ZhuangTingT @laughtervv
Hello, I also encountered the same problem, but I did not get an error after using GroupMerging in the test_util.py, I made the prediction correctly, and the output segpred.obj was relatively correct. But when I use the h5 file made by s3dis for valid, the nan in the picture below appears, I don't know if it's the same problem as you said at the end, have you solved it now?

The two file mingroupsize.txt and pergroup_thres.txt obtained after the valid are as follows


AutoCompleteService fails

I "discovered" the link from https://api.nuget.org/v3/index.json

We're on it. An index is being rebuilt. /cc @bhuvak

Thanks for fast response.
/cc @Krzysztof-Cieslak

Do you know how long this takes?

https://api-v3search-0.nuget.org/autocomplete is back

thanks


Major lags during autocompletion

I updated to Emacs 29.4 today and since then, autocompletion has regularly produced ~3s lags during which the entire editor UI freezes. Unfortunately, I also updated a number of packages during the update, so it's hard to tell where the issue lies exactly. I hope you'll be able to reproduce with the following info.
Emacs: 29.4
Doom Emacs: a99c6b9036bde2f60697ce9f2ac259dfa2266dbf
Relevant packages (?):
lsp-mode cec9e56390e90d7ced3b18a922ab954e782b8628
lsp-ui 00f1fecdfb41c30428734cf27e492f26f46627fb
lean4-mode da7b63d854d010d621e2c82a53d6ae2d94dd53b0
company-mode 1a0fc12a9c3d25e28c22f319e7b097f435b1c27d

Repro:

Clone https://github.com/leanprover-community/aesop and check out f465af4466eeb1f195692745fd58bb3f552692f1.
Open Aesop/RuleTac/Forward.lean.
On line 170, remove elabRuleTermForApplyLikeMetaM and type elabRuleTermForApplyLikeMetaM instead. This reliably freezes the UI at some point and autocompletion appears once the UI unfreezes again.

The freeze doesn't always happen at the same point and it only happens when I type somewhat slower than normal, so perhaps the issue is typing when an autocompletion request is already in-flight.
Disabling autocompletion (lsp-completion-enable nil) works around the issue.

This appears to be an issue of lsp-mode, not of lean4-mode. See discussion on Zulip.


Add a Gitter chat badge to README.md

intenthq/icicle now has a Chat Room on Gitter
@janstenpickle has just created a chat room. You can visit it here: https://gitter.im/intenthq/icicle.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

Closing, will add it manually into the right place.


The Handle was removed in v0.9.3

It seems that the Handle was deleted in the latest version. Is that right?
I was hoping to update Vaul to the latest version because it fixes the issue with closing animations when we have a controllable state, but we are also using the Handle and handleOnly
Any reason why it was removed? Is there an alternative? Should we implement our own Handle now?

This will be re-added, I just need to re-think the approach. Feel free to stay on 0.9.1/0.9.2 if you need it.


feature/TCVP-1212 Hand-written ticket validation

Description
This PR includes the following proposed change(s):

JIRA Ticket 1212
update staff API to return deserialized OCR values
add validation processing to staff dashboard instead of hard-coded text
miscellaneous e.g. Given names to Given name(s)

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Refactoring / Documentation
[ ] Version change

if your change is a breaking change, please add breaking change label to this PR
How Has This Been Tested?
Please describe the tests that you ran to verify your changes.
Does the change impact or break the Docker build?

[ ] Yes
[x] No

If Yes: Has Docker been updated accordingly?

[ ] Yes
[ ] No

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have made corresponding changes to the documentation
[x] New and existing unit tests pass locally with my changes

The PR conflicts with another PR already up for TCVP-1339. The StaffService models have moved to Common. We may need to merge that one first into develop, then address this PR.

Yes, Lorraine mentioned it yesterday.
@KDNeufeld Let's get either one merge into develop first.


[W4.2][T09-A4] Marlene Koh

edited input.txt, expected.txt, user guide as well.

@marlenekoh Some comments added. Please close the PR after reading comments.
Overall, good job for doing this LO. Consider if any other method from the Address class can be implemented in the new classes.


code typo error

Hi
It seems there is a code error in ZoomToFeature widget, while setting the renderer for the polygongraphics layer. as shown below the if condition should check for polygonGraphics layer and not polylineGraphics layer.
if (symbols.polygon && this.polylineGraphics) {
polygonSymbol = new SimpleFillSymbol(symbols.polygon);
polygonRenderer = new SimpleRenderer(polygonSymbol);
polygonRenderer.label = 'Search Results (Polygons)';
polygonRenderer.description = 'Search Results (Polygons)';
this.polygonGraphics.setRenderer(polygonRenderer);
}
Please fix the same or let me know, if I can do it.
Warm Regards,
Thejus

Thanks for pointing this out. It has been fixed


Description/ErrorMessageProps from useTextField (useField) returning undefined

🐛 Bug Report

🤔 Expected Behavior
Description and error message props from useField (using useTextField as an example) should return ID's associated with those props.
😯 Current Behavior
There is some re-rendering wierdness occuring with the hooks that provide the error/description props. a simple console log shows values are indeed provided, however immediately, sometimes several more re-renders occur and the values are suddenly undefined.
🔦 Context
Any error or description based fields are no longer associated with my input fields because no id's are generated connecting the two.
💻 Code Sample
codesandbox
open console and see where values are provided then immediately undefined.
🌍 Your Environment

Software
Version(s)

react-aria
3.23.1

Browser
chrome v113.0.5672.93

Operating System
windows 11

useField uses useSlotId to generate the ids for the description/error message, which checks to see if the id is being used in the DOM and will return undefined if not. The thought process here is that if you don't actually have an description/error message then you don't need those ids for your field's aria-labelledby attribute.
If you attach those description/error props to a element, they won't return undefined.

cheers mate, makes sense now.


Modify the flex-items case from ref to manual case.

Impacted tests(approved): new 0, update 1, delete 0
Unit test platform: Crosswalk for Android 21.51.544.0
Unit test result summary: pass 1, fail 0, block 0

@Honry @haoxli

LGTM


Select chat programmatically

Is your feature request related to a problem? Please describe.
no
Describe the solution you'd like
I want to be able to call a function an change the active chat, including on the whatsapp frontend.
Describe alternatives you've considered
None so far
Additional context
I'm implementing an extension that uses a router to refer to chats like: https://web.whatsapp.com/#/chat/123... and I want these routes to open specific chats so that I can pass links of chats to other users that share the same whatsapp number.

You can use WPP.chat.openChatFromUnread or WPP.chat.openChatBottom
https://wppconnect.io/wa-js/functions/chat.openChatFromUnread.html
https://wppconnect.io/wa-js/functions/chat.openChatBottom.html

Perfect, that might be just what I need. I'm currently unable to test because wajs stopped working on this last version: https://github.com/wppconnect-team/wa-js/issues/1322

@edgardmessias I was able to test this copying wa-js code directly into the developer console but noticed an issue: the chat is selected, but the text that indicates whether a message is from today, yesterday or some other day changes to russian:
before:

after calling any of the two functions:

I'd be interested in supporting financially this fix.


Winner Modal without replay or integration

Most feature work for issue #30

update overlay to be over arena for winner modal
hard coded values / integration for testing

Does not include integration with end of game state

@oconn @dehli made changes

What's the reason for having both a special modal and a regular modal?

Would it be possible to pass an additional argument to hide the underlay?


Can't install platform

Hi there!
I'm trying to install the orchid platform on a fresh laravel installation according the installation manual but it gives me the following error.
Can you tell me what went wrong?
Thanks!
composer require orchid/platform
Using version ^2.0 for orchid/platform
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- orchid/platform 2.0 requires laravel/framework 5.5.* -> satisfiable by laravel/framework[5.5.x-dev].
- orchid/platform 2.0.1 requires laravel/framework 5.5.* -> satisfiable by laravel/framework[5.5.x-dev].
- orchid/platform 2.0.10 requires laravel/framework 5.5.* -> satisfiable by laravel/framework[5.5.x-dev].
- orchid/platform 2.0.11 requires laravel/framework 5.5.* -> satisfiable by laravel/framework[5.5.x-dev].
- orchid/platform 2.0.14 requires laravel/framework 5.5.* -> satisfiable by laravel/framework[5.5.x-dev].
- orchid/platform 2.0.2 requires laravel/framework 5.5.* -> satisfiable by laravel/framework[5.5.x-dev].
- orchid/platform 2.0.3 requires laravel/framework 5.5.* -> satisfiable by laravel/framework[5.5.x-dev].
- orchid/platform 2.0.4 requires laravel/framework 5.5.* -> satisfiable by laravel/framework[5.5.x-dev].
- orchid/platform 2.0.5 requires laravel/framework 5.5.* -> satisfiable by laravel/framework[5.5.x-dev].
- orchid/platform 2.0.6 requires laravel/framework 5.5.* -> satisfiable by laravel/framework[5.5.x-dev].
- orchid/platform 2.0.7 requires laravel/framework 5.5.* -> satisfiable by laravel/framework[5.5.x-dev].
- orchid/platform 2.0.8 requires laravel/framework 5.5.* -> satisfiable by laravel/framework[5.5.x-dev].
- orchid/platform 2.0.9 requires laravel/framework 5.5.* -> satisfiable by laravel/framework[5.5.x-dev].
- Conclusion: don't install laravel/framework 5.5.x-dev
- Installation request for orchid/platform ^2.0 -> satisfiable by orchid/platform[2.0, 2.0.1, 2.0.10, 2.0.11, 2.0.14, 2.0.2, 2.0.3, 2.0.4, 2.0.5, 2.0.6, 2.0.7, 2.0.8, 2.0.9].
Installation failed, reverting ./composer.json to its original content.

The new version of Laravel, was released just yesterday.
We have not yet prepared a stable release for him.
Use version 5.5:
composer create-project laravel/laravel orchid  "5.5.*" --prefer-dist

Release for 5.6 is expected in the near future.

Ah, I should have known...
Thanks for your quick response tabuna!


Support classpath: URLs in 'extractorsDir'

Currently LinkMoveFactory.extractorsDir is a String that is treated as a File path by LinkMove. However LM also support ClasspathExtractorModelLoader. So let's change 'extractorsDir' to a FolderResourceFactory, and analyze returned URL, configuring LM for either  "file:" or "classpath:" URLs (and throwing on URLs that are of any other kind).

The 'extracrorsDir' has been replaced with FolderResourceFactory but a new issue has arisen: extracotrs xml files aren't available inside the jar. Proposed solution is to extend API of LmRuntimeBuilder with extractorModelsRoot(URI) to take the right IExtractorModelLoader in relation to protocol 'classpath:' or 'file:' (LmRuntimeBuilder.bindModelLoader(...)).


Update Unreal Engine Plugin

This PR updates the unreal engine plugin with support for QCMP, and continually measuring endpoint latency in the background, enabling client's to get their lowest latency endpoint to them for matchmaking.

CI failure is unrelated.

CI failure is unrelated.

Yeah having a look at the issue now. I think an upgrade of trust-dns-resolver will resolve it.

Yeah having a look at the issue now. I think an upgrade of trust-dns-resolver will resolve it.

And confirmed, but they broke their API, so just resolving it now.

Just bumping that this needs some licences and some readme fixes, and otherwise it's good to merge.

Just checking in to see if there is anything upstream that's blocking this from getting fixed up and merged?

No I just haven't had the time to address the feedback yet.

No worries - just wanted to check 👍🏻


chore(npm): Use CommonJS file as package.json main field

This will allow Browserify users to require('angular') without shimming, and will not affect non-Browserify users.
If this is accepted I will be happy to submit similar PRs for the other modules.

Replaced by https://github.com/angular/angular.js/pull/10731


Limit CSCC calls

Need to limit our CSCC calls, as this error is run into multiple times when trying to utilize CSCC in Stackdriver logs:
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/forseti_security-2.19.0-py3.6.egg/google/cloud/forseti/common/gcp_api/securitycenter.py", line 140, in create_finding
    finding
  File "/usr/local/lib/python3.6/dist-packages/forseti_security-2.19.0-py3.6.egg/google/cloud/forseti/common/gcp_api/repository_mixins.py", line 484, in patch
    return self._modify_resource(resource, data, target, verb, **kwargs)
  File "/usr/local/lib/python3.6/dist-packages/forseti_security-2.19.0-py3.6.egg/google/cloud/forseti/common/gcp_api/repository_mixins.py", line 458, in _modify_resource
    return self.execute_command(verb=verb, verb_arguments=arguments)
  File "/usr/local/lib/python3.6/dist-packages/forseti_security-2.19.0-py3.6.egg/google/cloud/forseti/common/gcp_api/_base_repository.py", line 442, in execute_command
    request_submission_status = self._execute(request)
  File "/usr/local/lib/python3.6/dist-packages/forseti_security-2.19.0-py3.6.egg/google/cloud/forseti/common/util/replay.py", line 169, in replay_wrapper
    return f(self, request, *args, **kwargs)
  File "/usr/local/lib/python3.6/dist-packages/forseti_security-2.19.0-py3.6.egg/google/cloud/forseti/common/util/replay.py", line 82, in record_wrapper
    return f(self, request, *args, **kwargs)
  File "/home/ubuntu/forseti-security/.eggs/retrying-1.3.3-py3.6.egg/retrying.py", line 49, in wrapped_f
    return Retrying(*dargs, **dkw).call(f, *args, **kw)
  File "/home/ubuntu/forseti-security/.eggs/retrying-1.3.3-py3.6.egg/retrying.py", line 206, in call
    return attempt.get(self._wrap_exception)
  File "/home/ubuntu/forseti-security/.eggs/retrying-1.3.3-py3.6.egg/retrying.py", line 247, in get
    six.reraise(self.value[0], self.value[1], self.value[2])
  File "/usr/local/lib/python3.6/dist-packages/six.py", line 693, in reraise
    raise value
  File "/home/ubuntu/forseti-security/.eggs/retrying-1.3.3-py3.6.egg/retrying.py", line 200, in call
    attempt = Attempt(fn(*args, **kwargs), attempt_number, False)
  File "/usr/local/lib/python3.6/dist-packages/forseti_security-2.19.0-py3.6.egg/google/cloud/forseti/common/gcp_api/_base_repository.py", line 543, in _execute
    num_retries=self._num_retries)
  File "/home/ubuntu/forseti-security/.eggs/google_api_python_client-1.7.7-py3.6.egg/googleapiclient/_helpers.py", line 130, in positional_wrapper
    return wrapped(*args, **kwargs)
  File "/home/ubuntu/forseti-security/.eggs/google_api_python_client-1.7.7-py3.6.egg/googleapiclient/http.py", line 851, in execute
    raise HttpError(resp, content, uri=self.uri)
googleapiclient.errors.HttpError: <HttpError 429 when requesting https://securitycenter.googleapis.com/v1/organizations/123123123/sources/1111111111/findings/abc123db?alt=json returned "Resource has been exhausted (e.g. check quota).">"

Recreated this issue by lowering the CSCC write quota to 20 requests per minute.


7 shadows of marshadow

Marshadow @ Marshadium Z
Ability: Technician
EVs: 252 Atk / 4 SpD / 252 Spe
Jolly Nature

Close Combat
Spectral Thief
Bulk Up
Shadow Sneak

Groudon-Primal @ Red Orb
Ability: Desolate Land
EVs: 248 HP / 252 SpD / 8 Spe
Careful Nature

Stealth Rock
Precipice Blades
Roar
Rock Slide

Celesteela @ Leftovers
Ability: Beast Boost
EVs: 248 HP / 8 Def / 252 SpD
Sassy Nature

Heavy Slam
Leech Seed
Flamethrower
Toxic

Arceus-Dark @ Dread Plate
Ability: Multitype
EVs: 248 HP / 72 Def / 188 Spe
Bold Nature
IVs: 0 Atk

Judgment
Will-O-Wisp
Recover
Defog

Salamence-Mega @ Salamencite
Ability: Aerilate
EVs: 16 HP / 252 Atk / 240 Spe
Jolly Nature

Dragon Dance
Roost
Facade
Double-Edge

Tapu Fini @ Leftovers
Ability: Misty Surge
EVs: 248 HP / 172 Def / 88 SpD
Calm Nature
IVs: 0 Atk

Whirlpool
Taunt
Moonblast
Nature's Madness

I assume you're reporting the missing picture of Marshadow? If so, fixed.


[BUG]: After image or link injection, editor lose focus

I'm submitting a

Bug report

Description
A bug: Description of the issue you encountered
In case of usage add a link or image functionality, after the overlay is closed editor loses focus.
steps to reproduce #1

click on the add link or image button
select enter link or any input field
put your image link or a simple link
click add
link was added BUT editor loses its focus
you can't continue typing until set focus onto the editor

steps to reproduce #2

set focus onto the editor
click on the add link or image button
set focus to input inside the overlay
click anywhere in the window outside the editor
editor loses its focus - error thrown by angular

In case of usage component wrapper with ControlValueAccessor, MatFormFieldControl, and FocusMonitor. Due to losing focus angular throwing error
ERROR Error: ExpressionChangedAfterItHasBeenCheckedError: Expression has changed after it was checked. Previous value for 'mat-focused': 'true'. Current value: 'false'.

focusMonitor:
 private focusHandler(): void {
    this.focusMonitor.monitor(this.elementRef, true).subscribe((origin) => {
      if (this.focused && !origin) {
        this.onTouched();
      }

      this.focused = !!origin;
      this.stateChanges.next();
    });
  }

Version Information
ngx-editor: 5.2.0
angular: 9.1.9

Browser

Chrome - Version 87.0.4280.88 (Official Build) (x86_64)

Will fix it.

Will fix it.

Fixed in v6.0.3.

Fixed in v6.0.3.


Crash on turning on Builder

This only happens occasionally, I have no clue what causes it.
Using a Builder with Fortune Quarry (non-clearing) and filter for several blocks. y = 2 (bedrock) to 64 inclusive, x/z exact chunks (2), all in all 16 x 32 x 63=32256 blocks (I think it crashed with larger quarries in the past). When turning on with a lever in the past, now via switching redstone setting to ignore, then clicking the Y-level/restart button to actually start, I immediately crash.
FTBRevelation-1.8.0-1.12.2 with a lot of mods disabled. No OptiFine.
I'm pretty sure this also happened with the (almost) vanilla FTBRevelation-1.8.0, so it is unlikely to be caused by changes made by me.
minecraft 1.12.2
forge-1.12.2-<IP_ADDRESS>27
mcjtylib-1.12-2.6.7
rftools-1.12-7.32
Crash log:
2018-04-25-1.zip

Also, duplicate of #1686 and #1699


Error :Refresh mic list

After giving the permissions to microphone in the website and checking the Voice setting i didn't found any microphone plugged and i try to refresh and nothing work .

If the browser isn't returning any mics, idk if there is anything I can do. It usually has to do with a mic privacy setting.


Invalid Prop type warning when using imported interface with union in defineProps

Version
3.2.26
Reproduction link
sfc.vuejs.org/
Steps to reproduce
Load the reproduction and the warning will appear
What is expected?
I expect the object to be allowed to be passed in.
What is actually happening?
The generated type seems to be of [null, Array]. According to the docs any imported type will just be turned into null to allow any type for it. This also seems to be the case for interfaces defined in the same file also.
The changing to a null type is happening but the null is in the array of types is not allowing for any type? I would assume in that situation the type should just be null since if null matches any type why be more explicit? I suppose might be useful to whoever is using the component and doesn't have volar/typescript.

you have a typo:
-     someObject: someObject | someObject[]
+    someObject: SomeObject | SomeObject[]

@LinusBorg  okay I had a typo and that fixes it if the interface is defined within the component but not if the interface is imported like in here which is my actual real world situation.

Yes, but for that we already have #4294

I see that issue, but my problem is more so with how the prop type is being inferred by the compiler.
According to your docs on the script setup page that I screenshotted

"If the type is referenced to an imported type then the referred result will null (equal to any type)"  That does seem to happen and I get type: [null, Array] but then  I get the warning about passing in my object so it really is not an "any" type then as I expected to be.

Ah, Thanks, that makes it clearer. Agree, this could be fixed.

When can you fix this bug?

same issue here: https://stackblitz.com/edit/vite-vq9eyz when i am using this prop type: IItem | number | null
interesting is when I use: IItem | null | undefined it works, but when I add any other additional primitive type like number, it shows warning
+1 for fix

This issue seems to have been fixed in vue3.3. Can you help confirm this 🧐? @LinusBorg

@baiwusanyu-c
I saw a different code. see

someObject: SomeObject | SomeObject[] 😂

@baiwusanyu-c I saw a different code. see

@baiwusanyu-c I saw a different code. see

There is a typo in his link, you need to fix it

Ah, This is awkward. 😄
Thanks @baiwusanyu-c


SigPloit

Assalamu aleykum bro, really nice work for creating this tool. I hope you can make some new video tutorial because the last one was deleted from youtube. Can you contact me privatly please need some help<EMAIL_ADDRESS>Thank you

Assalamu aleykum bro, really nice work for creating this tool. I hope you can make some new video tutorial because the last one was deleted from youtube. Can you contact me privatly please need some help<EMAIL_ADDRESS>Thank you

bro,i too need a video tutorial o this tool
unable to use it


OpenACI Interface Discrepancy with Linux/MacOS

I'm struggling to get OpenACI & AgentS in their current state to work without heavy modifications (tested across 4 environments now).
I'm getting an error from the OpenACI Ubuntu grounding agent about a missing obs param, see the signature here:
#ubuntu Grounding.py @ OpenACI
class GroundingAgent:
    def __init__(self, obs, top_app=None):
        self.input_tree = obs['accessibility_tree']
        self.screenshot = obs['screenshot']

I noticed, in the MacOS Grounding agent (which appears to be interchangeable, that param doesn't exist:
#macos Grounding.py @ OpenACI
class GroundingAgent:
    def __init__(self, top_app=None, top_app_only=True, ocr=True):
        self.active_apps = set()
        self.top_app = top_app

Is this discrepancy intentional? Trying to figure out how to get it running on Linux but dont want to go making a ton of changes if I just have this setup wrong.

Hi, we just refactored the codebase and fixed some bugs. can you try the new release?


Documentation

Currently we have a good README.md file for the project and helpful notebooks. We can improve this further.

[ ] Add a general description of the goals of state and process tomography.
[ ] Add a clear description of the algorithms used (mathematics can be written in a dedicated notebook).
[ ] Add precise documentation for the user-supplied parameters that can affect the tomography process.

https://github.com/Qiskit/qiskit-ignis/issues/76

I think you should close this and add the documentation to the qiskit mega

https://github.com/Qiskit/qiskit/pull/157


enhance: allow empty hash condition

Proposed changes
Issue Number: close #xxx
Problem summary
allow empty hash condition
Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[ ] Is this PR support rollback (If NO, please explain WHY)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 33.69 seconds
stream load tsv:          452 seconds loaded<PHONE_NUMBER>9 Bytes, about 157 MB/s
stream load json:         40 seconds loaded<PHONE_NUMBER> Bytes, about 56 MB/s
stream load orc:          73 seconds loaded<PHONE_NUMBER> Bytes, about 14 MB/s
stream load parquet:          30 seconds loaded 861443392 Bytes, about 27 MB/s
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230312092356_clickbench_pr_112931.html


fix: should call oauth login with correct route

Fixes #99

:tada: This PR is included in version 6.0.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Dockerize OpenRefine

Code from https://github.com/NINAnor/openrefine.

Great!
The container is built, but not shared, as it is not public. I will start to use the container produced here as soon as they will be made available :)

How do we make it public?

Right column, you should see the package; click on that, then go to package settings, and change package visibility.

Did we make a conscious decision to use the Github Container Registry over Docker Hub? What are the pros/cons?
Also, I know that this has already been merged, but it might be worth considering whether containers is too generic a name.

It is integrated with GitHub, which can make it easier to handle users' permissions, but feel free to use whatever you like the most.
The name of the repository can be changed, and the pipeline executed again, so the name of the container reflects the name. You probably want to use something different from env.IMAGE_NAME, since the image would be named "openrefine/containers", which seems a bit weird :)

The pull limits that DockerHub introduced a couple of years ago are a little annoying, but, in practice, shouldn't affect most people and I think it's a more visible and well known registry. The fine-grained Github permissions could be useful in other contexts, but here it's an artifact that we want public and widely available, so I don't think permissions are an issue.
openrefine/openrefine is probably a better base name. We can than add variants for other containers containing additional components.


All zwave devices disappeart after upgrade to 0.98.1

Home Assistant release with the issue: 0.98.1
Last working Home Assistant release (if known): 0.98.0
Operating environment (Hass.io/Docker/Windows/etc.): Hass.io on debian(stretch)
Component/platform: https://www.home-assistant.io/components/zwave/
Description of problem: After upgrade to 0.98.1 all 68 z-wave devices disappear. Controller appears on the next restart but no other devices. OZW log seems normal.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
zwave:
  usb_path: /dev/ttyACM0
  network_key: !secret zwave_network_key
  autoheal: false

Traceback (if applicable):
2019-08-30 14:56:43 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 1 not ready after 30 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 4 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 6 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 8 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 9 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 10 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 11 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 15 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 16 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 18 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 20 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 21 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 24 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 26 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 28 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 29 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 30 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 31 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 33 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 34 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 35 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 38 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 39 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 40 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 41 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 42 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 43 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 44 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 45 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 49 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 50 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 51 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 54 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 55 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 56 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 57 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 58 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 59 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 61 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 64 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 66 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 67 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 68 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 69 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 70 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 71 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 72 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 74 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 75 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 76 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 77 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 78 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 79 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 83 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 84 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 85 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 86 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 88 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 89 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 90 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 91 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 94 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 95 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 96 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 97 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 99 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 100 not ready after 31 seconds, continuing anyway
2019-08-30 14:56:44 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 101 not ready after 31 seconds, continuing anyway

Additional information:
Tried to restart several times both hardware and software.
OZW-log looks normal 50+ lines pr second.
Works ok after rollback to snapshoot og 0.97.2.

Try updating again maybe? Sounds like the zwcfg file got corrupted and the snapshot restored it.

Mine is also completely rekt

Try updating again maybe? Sounds like the zwcfg file got corrupted and the snapshot restored it.

Great catch. It works after updating again. Thanks for the help.


Halts midway through

SWF: f20c3ac44195c33b12a95ee946bdf7a77d38fba3d0b5c8fec8b0462c182415bc (Direct Link)

That's exactly what we do now, and indeed, the ad now runs through. Some visual differences, but by and large it works.


Escape codes in property annotations not generating correctly

I have hit a issue when generating entities with XML escape codes in a properties annotation value. Any escape codes entered for an annotation don't correctly generate. Previously in beef v3 the escape codes would generate code with the value that the escape code was for. Since upgrading to v4, this no longer seems to work. Is this a configuration issue with the code gen file or new intended behaviour?
As an example if I have this code in the codegen file:
<Property Name="MyObject" Type="int" Annotation1="[XmlElement("MYOBJECT")]"/>
It generates:
[XmlElement("MYOBJECT")]
I expected it to actually generate:
[XmlElement("MYOBJECT")]
Beef Version: V4.1.4

Hi @Nathan-Priebe, this has been fixed. NuGet package Beef.CodeGen.Core version 4.1.8 has been published. Cheers...

Thanks @chullybun


feat: add completion option

Thank you for contributing to jcli!
Please add a summary of your change
feat: add completion option
Does your change fix a particular issue?
Fixes #(issue)
Check list:

[x] Mark if documentation changes are required.
[x] Mark if tests were added or updated to cover the changes.

Codecov Report

Merging #31 (f789524) into main (824d464) will increase coverage by 1.09%.
The diff coverage is 100.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@            Coverage Diff             @@
##             main      #31      +/-   ##
==========================================
+ Coverage   74.35%   75.45%   +1.09%
==========================================
  Files           8        8
  Lines         425      444      +19
==========================================
+ Hits          316      335      +19
  Misses         86       86
  Partials       23       23

Flag
Coverage Δ

unittests
75.45% <100.00%> (+1.09%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Changed
Coverage Δ

application.go
75.53% <100.00%> (+0.72%)
:arrow_up:

command.go
58.87% <100.00%> (+1.72%)
:arrow_up:

options.go
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Support MBR partitions that expand

This is desirable when you don't know the destination media size, but
want to fill it.
Fixes #91

Coverage increased (+0.04%) to 85.962% when pulling 7b261a678bcf997021770e7d9bd93fc2d9fae32d on expand into 79a185eefc40963a85b966facd238e2d04e574de on master.

Couldn't get this to work. I tried modifying the fwup.conf for the nerves_system_rpi3 to use expand = true on partition 3. Also tried adding a partition 4 in case that was the issue. But according to Disk Util on my mac, the final partition size was still set to the default 512 MB in both cases.
fwup was upgraded yesterday from Homebrew to version 1.3.0. System is Mac Sierra 10.6.2.

Just deleted my previous comment by accident. :/ Couldn't get this to work with the latest fwup on homebrew (1.3.0) on Mac Sierra (if that matters). I modified the nerves_system_rpi3 image with the epxand = true option without any affect. Also tried adding a fourth partition without effect.
Other than expand = true is there anything else I could be missing? My linux machine is down or I'd try it their.

I'll take a look at this post-Lonestar. When I was making this, I had memories of the size calculation not work on OSX, but wasn't able to reproduce the issue (i.e., it worked for me). I'd be interested to hear if this works for you on Linux.
Also, if I drop the ball or even if I don't, could you open a new issue?

Sure, I can open an issue and post the details there. Have fun at
LoneStart!
Jaremy Creechley
<EMAIL_ADDRESS>το ευαγγελιον
On Tue, Feb 26, 2019 at 2:15 PM Frank Hunleth<EMAIL_ADDRESS>wrote:

I'll take a look at this post-Lonestar. When I was making this, I had
memories of the size calculation not work on OSX, but wasn't able to
reproduce the issue (i.e., it worked for me). I'd be interested to hear if
this works for you on Linux.
Also, if I drop the ball or even if I don't, could you open a new issue?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/fhunleth/fwup/pull/98#issuecomment-467616626, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AACF5RMd_VJq7mYRHfKjSfG1fPr4G1_rks5vRaPzgaJpZM4a67bz
.


Small problem in demo

I was testing the demo but I think there are some issues with the default tileserver:
https://maydemirx.github.io/leaflet-tag-filter-button/

Maybe in the demo we can adopt the default OpenStreetMap. What do you think about?
Thank you so much for your work :) Very interesting plugin. I've found it from here:
https://leafletjs.com/plugins.html

Fixed, please update the page and check again.
Thank you for your feedback.

Seems good to me! Awesome!


format tool creates syntax error in a specific case

crystal tool format turns this
(1..10).each do |i|
  next unless i.responds_to? :abs
  next unless i > 5
  i.tap() do |i|
    p i
  end
end

into
(1..10).each do |i|
  next unless i.responds_to? :abs  next unless i > 5
  i.tap() do |i|
    p i
  end
end

removing one line feed and turning compilable code into syntactically wrong.
If () after 'tap' is omitted, bug does not happen.

@konovod Thank you for reporting this! :-)


TypeError: love.load() is not a function

I tried to compile a small example, where was printed something on the screen, but the browser accused error: "love.load () is not a function". The error was on line in 1022 ..

That's because it expects you to have at least a love.load function.
love.load = function () {

}

//Initialize love
love.run();

aahh '-'
i'm sorry ><


Merge/602ebf5 from Bitcoin Core: Update libsecp256k1

This merges Bitcoin Core PR #5506.
I made some notes on how to review merging PRs like this one:
https://github.com/bitjson/hivemind-merge-core#reviewing-pull-requests
That repo also provides a simple workspace and scripts for properly merging Bitcoin Core changes into the Bitcoin Hivemind project.

The upstream pull requests are obviously well tested, and I don't see why secp256k1 would have side effects. However, it may be better to hold off on this and go with the rebase as planned.


Update Policy.Type to EntryType in identity cli

Signed-off-by: Ashish Kumar Mishra<EMAIL_ADDRESS>

@vaporos I'm aware of that.
btw, updated commit message.
And here's more context:
This is not a typo. This change was left out during 1.0 release changes in identity.proto.

For the commit message, how about:
'Update Policy.Type to EntryType in identity cli
This change was missed during API stabilization change prior to 1.0.  Fixes
an exception which was being thrown when running XXX.
'
Where XXX is the CLI command that was failing.


Calling setBlock does not fire any ChangeBlockEvents

Simple listener
     @Listener
     public void onBlockChange(ChangeBlockEvent e) {
         System.out.println(e);
     }

Calling World#setBlock from command handler or interact event (and probably anywhere) does not fire a ChangeBlockEvent
Using spongeforge bleeding https://github.com/SpongePowered/SpongeForge/commit/ec945eedf4752f052f104c6c0d006f63865be1f3
This essential feature worked fine on 1.8.9
Also, it looks like ChangeBlockEvent.Post is fired when a player places/breaks a block which contradicts the specification

*
The idea is that  a block, entity, or tile entity "ticks" in which
 * during that "tick", they make different types of block changes. If the
 * block change is purely one type then the corresponding event is thrown
 * instead. For example, If the block change is purely "placing" of
 * blocks, the {@link Place} event would be thrown instead.

@simon816
Need your code for firing setBlock.

@Zidane OK here's a minimal example. It will break the block beneth you when running /testcmd
    @Listener
    public void onBlockChange(ChangeBlockEvent e) {
        System.out.println(e);
    }

    @Listener
    public void onPreInit(GamePreInitializationEvent event) {
        Sponge.getCommandManager().register(this, CommandSpec.builder().executor((src, args) -> {
            if (src instanceof Player) {
                ((Player) src).getLocation().sub(0, 1, 0).setBlock(BlockTypes.AIR.getDefaultState(),
                        Cause.source(Sponge.getPluginManager().fromInstance(this).get()).build());
            }
            return CommandResult.success();
        }).build(), "testcmd");
    }

Pretty sure that this is now fixed since Causes refactor.


[1.19.2] Clouds don't render

Tested with Quilt Loader 0.18.1-beta.68 and SuperFancyClouds: Refabricated 1.4.1

Try to do with https://github.com/Rivmun/SuperFancyCloudsRefabricated/issues/19#issuecomment-1426254805.


[Enhancement]: Updating Screenshot of 2048 game in assets folder

Is your enhancement request related to a problem? Please describe.➕
2048 game was updated but the screenshot of the game in assets folder was not updated.
Describe the solution you'd like
Deleting the old screenshot and adding the new screenshot in the assets folder.
Select program in which you are contributing
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @thevirengarg !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

/assign

Hey @thevirengarg ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


[Fix] setup.py install_requires dependencies housekeeping

Same as storehouse PR #6

LGTM

Thanks for reviewing, Antonio


Using CompletionEntry for strings when name and insertText differ?

TypeScript Version:  4.0.3

Search Terms:
CompletionEntry
Code
We are using the TypeScript plugin model to override getCompletionsAtPosition, for example, as demonstrated in Writing a Language Service.
The scenario we have is a string-based embedded language (with spaces) where the name is different from insertText, but users will want to specify the completion by name. A representative (but abstracted) example:
const completionEntry: ts.CompletionEntry = {
                name: "color blue",
                kind: ts.ScriptElementKind.string,
                sortText: "123456",
                insertText: "123456"
};

Expected behavior:
In the above, we'd like the developer to be able to type "color blue" but have the string "123456" inserted. Currently, we can type 123... and the autocompletion stays but if we type "c" the autocompletion disappears:

Typing insertText:

Typing name:

Actual behavior:
Typing "c" will close the autocompletion. It's unclear if this is a bug, unsupported scenario (feature), or if we don't understand how to use CompletionEntry correctly (do I need replacementSpan?). It appears that there is no FilterText property as in IntelliSense.
@mjbvz might know.
Playground Link:
Related Issues:
https://github.com/microsoft/TypeScript/issues/20730 seems relevant, but it's not clear what the action is when it's a TypeScript plugin.
It may be also be related to:
https://github.com/microsoft/vscode/blob/00fa5d38843ce928d851e687a318cad75a212581/extensions/typescript-language-features/src/languageFeatures/completions.ts

From L83, it looks like filterText is a function of insertText. In the above scenario, it looks like we would need independent control of filterText. Would it be possible to have an optional property of filterText? in CompletionEntry that could be bubbled up?

It does look like getFilterText() has a baked-in set of assumptions that come from TS Server. I think it would be preferable if we could handle this change on the editor side without requiring a TypeScript/protocol change. In other words, this is a feature request for the TS extension in VS Code.

That would be preferable. I still suspect we may need both, since filterText can be disjoint to both name and insertText.  Particularly in a "plugin" model where the editor would not know a priori what to do with the plugin's completions.
Even if we make the change solely on the TS extension side, I wonder what Kind could be re-used on the TypeScript protocol side to signal that name should be part of the filter?

I would like to implement a plugin to convert some kind of complex char to alphabet string, so that i could simply input alpabet string instead of complex char. The scenario also need filterText to filter by converted alphabet string. It's a simple feature, but i have to custom a comprehensive typescript language service client.

eg: input alpha and editor show α suggest


Fixes 5144: nightly job failing

Summary
This fixes the nightly job failure by checking if the context was canceled before closing the pool. Here I added back a separate context for the listener, there might be a better way to do this without that though 🤔
Testing steps

Start the server and run make repos-import-rhel9 && go run cmd/external-repos/main.go nightly-jobs
Should not panic and RH repos should be snapshotted

https://issues.redhat.com/browse/HMS-5144

I took a look at this

9:14AM ERR Error unlistening for tasks in dequeue error="conn closed"

I don't really have a good solution. If closing the pool is causing too much weirdness, then I'm not sure we need to close the pool outside of the tests. Similarly, I don't know how important it really is to unlisten if the connection is already closed?

@rverdile and i chatted about this, and think a waitgroup may help here?

we might also go ahead and merge this so fix the stage jobs and then we can deal with this issue separately ?

we might also go ahead and merge this so fix the stage jobs and then we can deal with this issue separately ?

ok, yea i think merging to fix the nightly-jobs is a good idea. could you open a card for the other issue?

will do!


Allow ItemAlteration for hardness to have a non-integer value

Automate Gorum - Minor Curse using this functionality

As discussed


Don't wait if we don't have to

Counter-proposal to #73 along with some unsafety related cleanup.

I think this is the preferable way


Component getting darker each click

Hey
When i click an "btn" component Content.
It starts to darken and every click it gets darker i don't know how it happen, why it happen and how to solve.
Same happens with class waves-effect waves-light but obviously gets white. I don't demonstrated this but happens.
imgur
:edit on this image i tried add a click more each element first 1 click, second 2 clicks...
Thanks. Have a delicious day!

Can you provide a codepen?

Of course, but works fine, different from my prod/dev environment (imgur link) i tried build as prod and host my project with http-server and same problem appears.
https://codepen.io/luandr/pen/MmdYoM
Thanks @DanielRuf

See: https://github.com/Dogfalo/materialize/issues/2667

Can you please test if https://github.com/Dogfalo/materialize/pull/4474 fixes this?


Update canvas-to-blob.js

The (;) is causing an error to the current webpack build.

Hi @macoybarayan , could you provide a proof of concept and further explanation how this causes an issue?
Cause I'm very reluctant to change code that has been working for years.