Title

What is your username and discriminator?
TheBlueKingLP#0001
Why did you join Discord Linux?
To ask Linux question
Where did you hear about Discord Linux?
Google
What is the passphrase that was assigned to you by the bot?
7z8gedg5uk4my

From Ethan Weegee#9302 :
The passphrase you have entered is not correct.  Please check the message that mentions you in the welcome channel to find your passphrase.

where I can fine my  passphrase

Passphrase: cawojrmy76ihc

From simonizor#0420 :
The passphrase you have entered is not correct.  Please check the message that mentions you in the welcome channel to find your passphrase.

What does the passphrase looks like?

From simonizor#0420 :
Please read the entire contents of the link in the message that mentions you in the welcome channel.

sudo -i acupuncture-contain-travel-weekender

From simonizor#0420 :
Looks good.  I've given you a temporary role so that you can enter the passphrase in the welcome channel.


[HOLD for payment 2023-10-12] [HOLD for payment 2023-10-10] [$500] Chat - New message sent is not showing immediatelly

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Type a message
Press enter to send it

Expected Result:
The message should basically immediately show in the messages list
Actual Result:
There is noticeable delay before the new message shows in chat list
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

Version Number: <IP_ADDRESS>
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/93399543/c8d38513-7119-4954-96fd-d81c742c4637
Expensify/Expensify Issue URL:
Issue reported by: @mountiny
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1696275413656409
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01f9c236f03f59da21
Upwork Job ID:<PHONE_NUMBER>899952128
Last Price Increase: 2023-10-02

:wave: Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

Identify the pull request that introduced this issue and revert it.
Find someone who can quickly fix the issue.
Fix the issue yourself.

Also fixed in staging

Issue is not reproducible on build v1.3.96-10
https://github.com/Expensify/App/assets/93399543/840bfb04-0e22-4dad-a395-218ceb922831

@kbecciv yes, it's expected not reproducible on staging. Did you also not reproduce on this build?

Checking on special build


Docs: fix 50+ errors in documentation

[ ] I added CHANGELOG entry for this change.
[x] Change is not relevant to the end user.

Changes

Fixed 50+ errors in documentation

@squat Updated it

The Circleci test is failing and I am not able to figure out the reason from the error logs.
@squat Could you please guide me if I need to change something from my end?

It's a flaky test it seems. I'm rerunning it


Working LXD API but Google Chrome interprets endpoint as 'Not Secure'

Required information

Distribution: Ubuntu
Distribution version: 16.04.2 LTS
The output of "lxc info" or if that fails:

Kernel version: 4.4.0-64-generic
LXC version: driverversion: 2.0.7
LXD version: serverversion: 2.0.9
Storage backend in use: zfs

The output of "lxc config show"

  config:
  core.https_address: <IP_ADDRESS>:8443
  core.https_allowed_headers: Origin, X-Requested-With, Content-Type, Accept
  core.https_allowed_methods: GET, POST, PUT, DELETE, OPTIONS
  core.https_allowed_origin: '*'
  storage.zfs_pool_name: lxd

Issue description
I use my own CA authority. I have generated a root and intermediate CA cert. I have installed these on my browser keychain. Using a different daemon server (nodejs http-server), i configured it to serve requests to my client browser using https. With http-server pointing to server certs generated by my intermediate cert and intermediate key, i get i nice green padlock in google chrome. Command line - http-server -S -a <IP_ADDRESS> -p 8000 --cert ~/lxd-cert/<IP_ADDRESS>.cert.pem --key ~/lxd-cert/<IP_ADDRESS>.key.pem
However, when i shutdown http-server, add <IP_ADDRESS>.cert.pem to lxd's trust, restart lxd service, and when i try to access lxd api https://<IP_ADDRESS>:8443/1.0 I get a nice json response. LXC-WebGUI is able to read and post to the lxd json api. However, google chrome shows a red 'Not Secure' sign in the address bar when i view lxd api  https://<IP_ADDRESS>:8443/1.0 . What this does is cause the entire client side javascript LXC-WebGUI app to change from green padlock to red unsecured padlock. This is because a website with mixed unsecure and secure times is considered not secure.
Since both http-server cert and lxd trust cert are the same, i am expecting the client browser to show green padlocks for both server daemons. Since the lxd api is working fine and encrypting, and it is only chrome invalidating the cert, is this a bug or just an unsupported feature?
Steps to reproduce

Create you CA server by following - https://jamielinux.com/docs/openssl-certificate-authority/
You should now have a root CA and intermediate CA cert installed in your browser key chain
Install server cert into lxd and make sure Common Name in cert matches the URL of how you access the api eg. <IP_ADDRESS>

sudo lxc config trust add <IP_ADDRESS>.cert.pem
sudo lxc config trust list
sudo service lxd restart

Access https://<IP_ADDRESS>:8443/1.0
You get a red 'Not Secure' sign in google chrome with below response -
'
{"type":"sync","status":"Success","status_code":200,"operation":"","error_code":0,"error":"","metadata":{"config":{"core.https_address":"<IP_ADDRESS>:8443","core.https_allowed_headers":"Origin, X-Requested-With, Content-Type, Accept","core.https_allowed_methods":"GET, POST, PUT, DELETE, OPTIONS","core.https_allowed_origin":"*","storage.zfs_pool_name":"lxd"},"api_extensions":["id_map"],"api_status":"stable","api_version":"1.0","auth":"trusted","public":false,"environment":{"addresses":["<IP_ADDRESS>:8443"],"architectures":["x86_64","i686"],"certificate":"-----BEGIN CERTIFICATE-----\nMIIFXDCCA0SgAwIBAgIRAO5KkgWfgo6A0CiA93nzZT8wDQYJKoZIhvcNAQELBQAw\nNzEcMBoGA1UEChMTbGludXhjb250YWluZXJzLm9yZzEXMBUGA1UEAwwOcm9vdEBi\nYXNlc3RhY2swHhcNMTcwMzA1MDgyODA5WhcNMjcwMzAzMDgyODA5WjA3MRwwGgYD\nVQQKExNsaW51eGNvbnRhaW5lcnMub3JnMRcwFQYDVQQDDA5yb290QGJhc2VzdGFj\nazCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBALf5eyg4fNwRMDq5NyMe\nibfPxQkRb3xk/cJKIpEc9gmFK4sWu6SRB4AJhg6RvUBH5G9cI7UI4OkojFJhHNtp\n0ijtV+yW/qofnPAoMo9IgSharbGlfBGnv6O3ABqBoKGVDesJY7oSetYcK58q9vJF\n/NU011FAcug9V5Pqlj9WGWzgDMYG46eFdns0L/cnCSQRa1urTKBOU3wOamjoV5pY\nJnQz3bAY0afdbOIiqcJ/LECG9v6A39w44Q61ZQMkz6Mc9U+PxZ+cn7UDLnVXykvA\nTIZQBD2S3uXBmbqqG2JYHdC3gfEnoSdGNa3rXQsOkmP5xJrNBCV09yL9WE2UPT2T\nz2sWEqBMeY4csBb1TVmjmKYSxF5mV+zf04v5PYBji10PXnlFaxWdC7bq8aTIlDq3\nOybmf/3nATZMDuT8zsiILa6KP40dJbb8/9Rt6Mgo9wqsHQtNdsSGZ9PBiZ4ueuBn\nsdMvz22Ql9ANxXoNErQlPueHSe1H6+f7gbGIWzBoUjDVclk/ggs0RdATfOsUJIJ3\nn3H5RYY6tfLL5Zd28LWswxOW+abBSak1v+ESfo7bDF8WMmWWVsw3DieI6989x2fM\nAI6kwUduhS796EL3lPInw32B61XUvVtfSrEevZi2NuIeKeQ93GoBjNav857RJWYi\nNlCcT5qfzvvIV9joLDQbhzaRAgMBAAGjYzBhMA4GA1UdDwEB/wQEAwIFoDATBgNV\nHSUEDDAKBggrBgEFBQcDATAMBgNVHRMBAf8EAjAAMCwGA1UdEQQlMCOCCWJhc2Vz\ndGFja4cECgAAP4cQIAGAA2ibNgAKACf//jSjLDANBgkqhkiG9w0BAQsFAAOCAgEA\nQeX9q0OJ8E+wzj1nm0uFWfzI65vhDTOb5mZzeWt1Vi3eBf7lqBre0u6AREV5QqL1\nXw+5e3phnDSvRyd7G3Bzir0gcbNM6htSyWqZvj76ur2YkInEtFs+pp+zRu16Z/ru\n0PRRzaMmsCw/BZJC2qpj5tuOQB3VZAaW183JoPzNQYXzbLjs+oXU8TloVQYOK4eO\ncsMG3Eca+cphUATcI6kobsZ5TEm1+ATi12Z0RL/9wvYK1YzeGUNpbfyD7VdoXkWk\nrITyO8iz3hdGVHmN6lOr+AzINztuHm6GHpljWFMclVTl69/uPgILapxUEOjcJ4+c\neoRjhJqCW9fc/D/k7T24mOzOMkePo82r2rIL6ZpbNFdtvd0a3kbFYqI/ESvJfY7i\nxvTP/4EmibWpZ8ugtgdioZ+cyeM3M/1mFVSvK5OEAnvsM9u23b0AbN5ouwG3GbSb\nRdUPbHw02NiRUTFkwaSNp4A42LSChFJFN8z6+Gy+Zn0YpslNghvgLukOTLVZu26C\niPuFpvJrWkGnxsmOf7cXA+QsEdxv7xeG9ukDj9jqe+Ax849VPSZgYxYfn10WNPNI\nmww5him50AETQqPo9gpjUGTPV4n6/W1YQl40MSuMI4jMVeCR2peg1CG9J42mIN+A\nU43FCOQAVUknCWdrIpAkNFUDxso1tEuxFu8vVIt+R30=\n-----END CERTIFICATE-----\n","certificate_fingerprint":"","driver":"lxc","driver_version":"2.0.7","kernel":"Linux","kernel_architecture":"x86_64","kernel_version":"4.4.0-64-generic","server":"lxd","server_pid":7507,"server_version":"2.0.9","storage":"zfs","storage_version":"5"}}}
'

I have verified the certs and they are valid. the server cert's Common Name matches the accessed url of <IP_ADDRESS>
Information to attach

[ ] main daemon log (/var/log/lxd.log)
ip=<IP_ADDRESS>:52285 lvl=warn msg="rejecting request from untrusted client" t=2017-03-11T16:57:46+1000
ip=<IP_ADDRESS>:52314 lvl=warn msg="rejecting request from untrusted client" t=2017-03-11T16:59:26+1000

What's chrome's reason for marking the connection unsafe? You can usually find out by getting into the developer tools (F12) and look at the security tab.

I just did a quick check using a valid commercial certificate here and my local LXD daemon, validation works fine in my chrome browser, so whatever's happening to you is unlikely to be LXD's fault.


Make datapackage_to_documentation.py more generic

In schema-collaboration there is this file: https://github.com/frictionlessdata/schema-collaboration/blob/master/SchemaCollaboration/datapackage_to_documentation/main.py to convert datapackage to Markdown or PDF.
This file could be generalised with the following features:

Make it usable from the command line: pass the datapackage.json file and the output file
Output HTML (and odt? It uses Pandoc for PDF so it's easy to add other formats)
Make it independent of schema-collaboration installable via pip? Or part of frictionless-py?
Fix errors (if a resource doesn't have schema it currently fails)

Good idea! This could be used as inspiration:

https://github.com/AntoineAugusti/table-schema-to-markdown/
https://framagit.org/opendataschema/table-schema-to-markdown


Notifications

⚠ Please verify that this bug has NOT been raised before.

[X] I checked and didn't find similar issue

🛡 Security Policy

[X] I agree to have read this project Security Policy

📝 Describe your problem
The Uptime Kuma Notifications send me only "down" and not "Up" to the mail
📝 Error Message(s) or Log
No response
🐻 Uptime-Kuma Version
1.21.2
💻 Operating System and Arch
Ubuntu 20.04.6
🌐 Browser
Google chrome
🐋 Docker Version
No response
🟩 NodeJS Version
No response

Which notification type are you using? (Email, Instagram, etc.)

EMAIL

What is the template for the monitor? is this a duplicate of #3184 ?


Change arXiv to official NeurIPS publication

Description
Closes #204
Motivation and Context

[x] I have raised an issue to propose this change (required for new features and bug fixes)

Types of changes
What types of changes does your code introduce? Put an x in all the boxes that apply:

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds core functionality)
[ ] New environment (non-breaking change which adds 3rd-party environment)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] Documentation (update in the documentation)
[ ] Example (update in the folder of example)

I think it is ok to wait till the url of the neurips version finalized.


Fixed some bugs and added some features

Optimized the software experience

I've incorporated first two commits into master. I can't accept remaining two commits, as they lack meaningful description and introduce license change. For next PRs, please provide more description on what problem you are trying to solve, otherwise I have to guess this.


MM-18901 - Remove unused status flags in requests/preferences.ts #12521

Summary

Removal of unused status flags from requests/preferences.ts

MY_PREFERENCES_REQUEST
MY_PREFERENCES_SUCCESS
MY_PREFERENCES_FAILURE
SAVE_PREFERENCES_REQUEST
SAVE_PREFERENCES_SUCCESS
SAVE_PREFERENCES_FAILURE
DELETE_PREFERENCES_REQUEST
DELETE_PREFERENCES_SUCCESS
DELETE_PREFERENCES_FAILURE

Ticket Link

MM-18901
Fixes #12521
Checklist

[x] Ran make check-style to check for style errors (required for all pull requests)
[x] Ran make test to ensure unit tests passed
[x] Added or updated unit tests (required for all new features)

Thanks @atulya-pandey for the contribution! :tada: Heads up that reviews may be slower with the holidays

This issue has been automatically labelled "stale" because it hasn't had recent activity.
A core team member will check in on the status of the PR to help with questions.
Thank you for your contribution!
/cc @jasonblais @hanzei

@sudheerDev / @saturninoabril / @bradjcoughlin quick reminder to help with reviews when you have a chance, thanks! :)

Thanks @atulya-pandey for the pull request!
Per the CONTRIBUTING.md file displayed when you created this pull request, we need to add you to the list of approved contributors for the Mattermost project.
Please help complete the Mattermost contribution license agreement?
This is a standard procedure for many open source projects. Your form should be processed within 24 hours and reviewers for your pull request will be able to proceed.
Please let us know if you have any questions.
We are very happy to have you join our growing community! If you're not yet a member, please consider joining our Contributors community channel to meet other contributors and discuss new opportunities with the core team.

/check-cla


fix: mistake GetApplicationLogin swagger router  (casdoor#739)

close #739
Signed-off-by: xiexianbin<EMAIL_ADDRESS>

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Large numbers of streamwatcher.go:114] Unexpected EOF during watch stream event decoding: unexpected EOF in kubelet logs

**What kind of request is this (question/bug/enhancement/feature request):**Bug
Steps to reproduce (least amount of steps as possible):
Deploy a new Rancher downstream cluster (have set up on Ubuntu 18.04 in AWS)
Check the logs for kubelet container on a worker only node
Result:
Groups of streamwatcher.go:114] Unexpected EOF during watch stream event decoding: unexpected EOF logs are output every 30s
Other details that may be helpful:
Related to https://github.com/rancher/rancher/issues/14971
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI):2.5.3
Installation option (single install/HA): HA

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): Have seen this on prem, and AWS
Kubernetes version (use kubectl version):  Have seen this on v1.18.12, v1.19.6, and v1.17.14

gz#15237
gz#15657
gz#15799

on master-head (29674d9) and 2.5-head (14c8c62a05f364adf85523d0afd54b24d9dc4cda:
there is no log of streamwatcher.go:114 using amazon nodes in a custom downstream cluster
verified that rancher/rke-tools                            v0.1.75
Was also able to repro on v2.5.8, viewing the logs of kubelet container.
rke tools for 2.5.8 is on version v0.1.74


Infinite loop in sprintf gem

https://hackerone.com/aerodudrizzt reported the following issue:
Brief
As specified in https://github.com/mruby/mruby/issues/4062, there is an undefined behavior in the CHECK macro of the sprintf-gem. An attacker can use this compiler optimization to trigger an infinite loop inside the CHECK macro.
Code Vulnerability
Vulnerable version: master version from github
File: sprintf.c
Macro: CHECK(l)
Since mrb_int is signed, the compiler removes the overflow check inside the while loop.  This means that an attacker can pass l = 2 ** 63 - 1 (in 64 bit) or 2 ** 31 - 1 (in 32 bit) to the macro, causing the condition inside the while loop to be always true. Without an additional escape route, the loop will run forever.
The effective loop code is:
#define CHECK(l) do {\
  /*  int cr = ENC_CODERANGE(result);*/\
  while ((l) >= bsiz - blen) {\
    bsiz*=2;\
  }\
  mrb_str_resize(mrb, result, bsiz);\
  /*  ENC_CODERANGE_SET(result, cr);*/\
  buf = RSTRING_PTR(result);\
} while (0)

PoC Script
This is the 64 bit version, using a width of 2 ** 63 - 1:
sprintf("%<PHONE_NUMBER>854775807s", "")

Possible Fix
Should consider using unsigned variables inside this macro, adding the ability to check that if bsiz after the change is smaller than before the change, than an exception should be raised. This kind of check will be defined only in unsigned integers.
Impact
An attacker with the ability to control the width of a format string template, could trigger an endless loop of the interpreter.

This issue seems to be fixed with #4062 by 180f39b


⚠ ClamAV has degraded performance

In 867d0c0, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 297 ms

Resolved: ClamAV performance has improved in f96ae7c.


Add Markdown syntax highlighting for markdown cells

When using the jupyter notebook data science features, It gets especially hard to read long markdown cells without any sort of syntax highlighting. It would be great leverage the markdown syntax highlighting for any markdown cells.

As this issue was transferred here, the link to my pr of vscode-python disappeared. I'm not obligated to work the way they want me to. And they do not have an internal contributor working on it. So the feature is published as a new extension.


v3.0.2

Improve test coverage
Remove unused parts

Coverage increased (+3.4%) to 95.96% when pulling 9994d254ba5bd79b48026b69eac4a6c544a18814 on v3.0.2 into b682389dee46fb0b309fb4b3e11611450709c1a4 on main.


AnimationPlayer track keys can not be loaded again after first loading with ResourceLoader

Operating system or device - Godot version:
Windows 7, Godot Godot_v2.1.3-stable_win64
Issue description:
AnimationPlayer track keys can not be loaded again after first loading with ResourceLoader.
Situation: We are in an in-game Level Editor, not in Godot Editor!
After modifying a previously loaded scene and loading it again, modified AnimationPlayer track keys are not loaded instead they keep their modified value even if the whole scene (including the AnimationPlayer) is queued_free and completely reloaded from disk.
Expected:
Animation track keys (which are part of the loaded Scene) are are the ones in the loaded Scene not the ones in memory of the queued_free scene.
Details:
I chose GDScript modified scenes (.tscn) as a save format, so I can also use the Godot Editor to tweak the Levels.
Loading:
playable_map = load(path).instance()
I also tried to disabling caching:
playable_map = ResourceLoader.load(path,"",true).instance()
Steps to reproduce:
Following the steps in the attached project to reproduce the bug

Load saved map
change track keys
Load map again

-> changes to track keys are not loaded, but other changes to other nodes are.
Link to minimal example project:
RessourceLoaderAnimPlayerBug.zip

Same Issue with Godot 2.1.4 and Curve2D.
Steps:
1st I save a Level to tscn file on Disk:
var packed_scene = PackedScene.new() packed_scene.pack(tscn) ResourceSaver.save(path, packed_scene)
Then I run it with get_tree().change_scene().
Then I modify the Level (clear_points() on Curve2D and add Points) and save it again overwrite the file.
Then I run it again with get_tree().change_scene().
Result:
The OLD! Curve2D is shown.
Expected:
Changes are loaded
I checked the saved File in an text editor: Its correct!
I exited Godot, restarted and loaded the Level: It's correct!
There is some kind of caching going on that refuses to update some Objects (Curve2D) if the a scene of same name was loaded before. If I save with different file every time (not overwrite) it's also correct.

This is fixed in 2.1.5-rc2. Thank you so much!


Allow out of state addresses for MN

Also, line 32 in address_cleaner.rb will have to change:
lookup.state = 'MN'

right you are on both counts; fixed.


Query metrics with V3 SDK for .net core

Hi! Great article.
Is is possible to populate query metrics in the latest version of the SDK (V3)?
I can find any information on how to do this browsing the api documentation.
I gather that Microsoft recommends going for V3 for new projects and version as will V2 eventually will retire?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 498a360c-9ba7-a124-5fb5-7f4c85c54041
Version Independent ID: 459bc7a4-f3a9-4786-a272-b8d5bb0d73f3
Content: Get SQL query performance & execution metrics
Content Source: articles/cosmos-db/profile-sql-api-query.md
Service: cosmos-db
Sub-service: cosmosdb-sql
GitHub Login: @ginamr
Microsoft Alias: girobins

@magnarw Thank you for your query , our team will further look into it and get back to you at the earliest.

@magnarw Yes, this is the case. Version 2 of the SDK will eventually retire and the capability discussed in the document is dependent on the version of the SDK but, there is a REST option: Tuning query performance with Azure Cosmos DB

Please let me know if I have answered your question or not, or if you require additional information.

We will now proceed to close this thread. If there are further questions regarding this matter, please comment and we will gladly continue the discussion.


[HUDI-6497] Replace FileSystem, Path, and FileStatus usage in hudi-common module

Change Logs
This PR makes the changes to replace most FileSystem, Path, and FileStatus usage with HoodieStorage, HoodieLocation and HoodieFileStatus (introduced in #10567) in hudi-common module, to remove dependency on Hadoop FS abstraction which is not essential to most Hudi core read and write logic.
This PR still keeps using the Hadoop FileSystem-based implementation under the hood.  A follow-up PR will make HoodieStorage and I/O implementation pluggable.
The focus of this PR is to reduce the usage of Hadoop's FileSystem, Path, and FileStatus usage in hudi-common module, mainly to decouple the read path from these classes, so other modules may have leftovers (e.g., on the write path, Spark, etc., which has to rely on these classes) and bridging (e.g., new Path(hoodieLocation.toUri())) and type-casting code (e.g., (FileSystem) storage.getFileSystem()), which are expected.  The clean-up and code improvements of other modules are deferred to HUDI-7363.
Here are details to attend to (especially for reviewers):

HoodieStorage replaces FileSystem wherever the storage abstraction is needed only.  HoodieTableMetaClient provides HoodieStorage with getHoodieStorage(), replacing getFs().
HoodieStorage calls replace FileSystem calls.  Here are a few differences to be reminded of:

storage.createDirectory(path) replaces fs.mkdirs(location)
storage.deleteFile(location) replaces fs.delete(path, false); storage.deleteDirectory(location) replaces fs.delete(path, true).
HoodieStorage list and glob calls return Java List instead of array.

HoodieLocation replaces Path and CachingPath wherever the Path instance is not particularly needed (e.g., serving file system view).  HoodieLocation holds the URI instance inside which is supposed to be Path URI compatible.  The transformation between two are done in: (1) Path -> HoodieLocation: new HoodieLocation(path.toUri()), (2) HoodieLocation to Path: new Path(hoodieLocation.toUri()).
HoodieLocationFilter replaces PathFilter.
HoodieFileStatus POJO replaces the FileStatus, by storing only necessary fields.

This is part of the effort to provide Hudi storage abstraction and decouple hudi-common from hadoop dependencies. For reference, the single big-change PR can be found here: #10360.
Impact
One step further to decouple hudi-common module from Hadoop dependencies.
Risk level
low
Documentation Update
N/A
Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

Note to reviewer: commit [44e3347](https://github.com/apache/hudi/pull/10591/commits/44e334758625cfc2a35d7644cbcbed102e560062) is frozen now and I'll only add new commits for new changes and fixes to easier review.  I'll also defer the rebasing and force-push until CI passes and the PR is approved.

I need to check a few more things before landing this PR.

The PR is rebased on the latest master and ready to land once CI passes.


Use rollupjs

@kamilkisiela Why use rollup instead of webpack? What problem does it solve?

Also, there is an open PR that migrates all code base into TS and over there I've used just the ts compiler to do the bundling. Should we use rollup or webpack over there? (Support umd maybe?)

Moved to TS so this PR is not relevant anymore.. We should maybe open an issue on that subject if @kamilkisiela can tell us the reason to use rollup instead our current setup. (Tree shaking maybe?)


import failures

this is one of the few errors im getting after install. i have gotten
root@kali:/opt/portia# ./portia.py
Traceback (most recent call last):
File "./portia.py", line 16, in
import nmap
ImportError: No module named nmap
i installed python-nmap and i believe i fixed that as it hasnt re-appeared.
as well as
root@kali:/opt/portia# ./portia.py
Traceback (most recent call last):
File "./portia.py", line 9, in
from deps.secretsdump import *
File "/opt/portia/deps/secretsdump.py", line 56, in
from impacket.examples.secretsdump import LocalOperations, RemoteOperations, SAMHashes, LSASecrets, NTDSHashes
ImportError: No module named secretsdump

Regarding the below error.
ImportError: No module named secretsdump
Did you happen to install impacket or run install.sh to install the dependencies ?Thanks
cd /opt
git clone https://github.com/CoreSecurity/impacket
python setup.py install

i had CoreSecurity/impacket installed previously for another programs pre-reqs. but i removed it and installed the impacket from within the install.sh. (i installed everything manully i didnt run the install.sh as i was originally having the above metioned issues.

-quick update... erased impacket folder and reinstalled using
"cd /opt
git clone https://github.com/CoreSecurity/impacket
python setup.py install' ......not sure what changed as i had done this before, but i wont knock it.
-verified it was 'apt-get install python-nmap' that was needed.
i run program....and it loads without error.
root@kali:/opt/portia# ./portia.py
usage: PROG [-h] [-d DOMAIN] [-u USERNAME] [-p PASSWORD] [-s] [-L] [-amsi]
[-bypass] [-obfs] [-M MODULE]
[-o MODULE_OPTION [MODULE_OPTION ...]] [-D]
[target [target ...]]
-closing issue..


Port 3.x

Make sure to copy the .travis dirtectory from https://github.com/Oefenweb/cakephp-vat-number-check/tree/3.x

Make sure to adjust .travis.yml

I rebuild -vat-number-check with the latest CakePHP version: https://travis-ci.org/Oefenweb/cakephp-vat-number-check/jobs/330973077
This seems totally broken

The text_renderer might be a better example, but you might already used that one

Make sure to keep that in mind when reading my comments

Codecov Report

Merging #2 into 3.x will decrease coverage by 11.16%.
The diff coverage is 83.33%.

@@              Coverage Diff              @@
##                3.x       #2       +/-   ##
=============================================
- Coverage     94.49%   83.33%   -11.17%
+ Complexity       34       33        -1
=============================================
  Files             7        4        -3
  Lines           109      102        -7
=============================================
- Hits            103       85       -18
- Misses            6       17       +11

Impacted Files
Coverage Δ
Complexity Δ

src/View/Helper/VatNumberCheckHelper.php
100% <100%> (ø)
4 <4> (?)

src/Model/Datasource/Soap.php
61.76% <61.76%> (ø)
13 <13> (?)

src/Controller/VatNumberChecksController.php
86.95% <86.95%> (ø)
10 <10> (?)

src/Utility/Model/VatNumberCheck.php
95% <95%> (ø)
6 <6> (?)

Continue to review full report at Codecov.

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


Why does it restart the UI whenever you save a new config?

Saving new styles doesn't require restarting the UI, why does saving a new config restart the UI? Can it not add the requisite lines to the JSON file, and refresh its list without needing a full UI restart?

There's some trickery going on with the code that was causing issues, and the only way I could figure out how to resolve it was to restart the UI after creating a new config preset. It should be possible to do it without a restart like before A1111's update a few weeks ago, but I couldn't get it to work after the update.

Maybe you could look at the way styles are being saved, and copy that method?

It's not quite that simple. The styles button reads the values from predefined 2 textboxes (prompt/neg prompt), but config presets needs to accept a variable number of arguments because it works with both txt2img and img2img tabs. To do this we need to make use of a coding trick with *args and anonymous functions. Combined with Gradio being really stupid with how their dropdowns work, desyncs happen between server and client, and I couldn't find a way to fix that desync.

@medledan You need to comment out this function (line ~600) in config_presets (add # before each line):
save_button.click(  # need this to runa after save_config()
                             fn=None,
                             _js="config_preset_settings_restart_gradio()",  # restart Gradio
                             )

All new presets will show up after a reset, and existing preset changes will take effect immediately, which isn't half bad.
@Zyin055 I've been plagued by basically the same thing in regional prompter's presets - the menu item is added to the dropdown, but it isn't recognised the selection event. Are you aware of any fix in recent gradio versions / issue opened in the repo on the matter?

So I think I've located the cause for this in https://github.com/gradio-app/gradio/issues/4210 ; the simple workaround is updating the dropdown with a persistent list object. You can check the PR / commit in regional for details, my testing shows it's working perfectly, no restart needed.

Fixed with PR #41


Exports need to include a BOM

Currently exporting a CSV and opening it in Excel ruins any unicode characters.
For example, Japanese characters display as Ë£ïÂ§™
Exporter needs to do something like this to write the BOM to the beginning of the file;
    contents = StringIO()
    contents.write(codecs.BOM_UTF8.decode('utf-8'))
    writer = csv.writer(contents)

I'd like to work on that if that's ok?

Hi @bdista
It would be great if you're able to. I've not had the time yet so would love a PR to fix this!

Ok great, I'll prepare a PR, thanks!

Hi @marksweb,
While testing this issue locally I noticed that the paths to the requirement files in  test_project/start.sh are not in line with the actual requirements files.
Should I change that in the PR I'll make for the BOM or do you prefer a dedicated issue and PR for this ? (sorry newbie here)
Thanks!

Hi @bdista, happy for you to include that fix.
I think I've broken those paths as I migrated from travis CI to github actions recently!

Hi @marksweb,
I've created a draft PR for this issue.
Not sure how users use this, so I'm wondering if this can be a breaking change for some if these exported csv get then processed by other tools that don't play nice with an UTF8 BOM.
If that's a problem, perhaps a setting in app_settings.py could define whether a BOM is to be included or not.
Happy to try out other approaches if needed!
Thanks

Hi @bdista
At the moment unicode characters don't export properly and nobody else has reported it, so I'm not concerned about this feature having heavy use and prefer to just get bugs fixed.
If this change lead to people raising issues because of the BOM, then we can consider an enhancement with settings I think.

Actually, we also stumbled into this problem in our place.
What we did is the following
We improved the built in exporter a little bit
from explorer.exporters import CSVExporter
from io import BytesIO

class CSVExporterBOM(CSVExporter):
    def _get_output(self, res, **kwargs):
        csv_data = super(CSVExporterBOM, self)._get_output(res, **kwargs)
        csv_data_io = BytesIO()
        csv_data_io.write(b'\xef\xbb\xbf')
        csv_data_io.write(csv_data.getvalue().encode('utf-8'))
        return csv_data_io

than we set this as the CSV exporter in the settings
EXPLORER_DATA_EXPORTERS = [
    ('csv', 'core.exporters.CSVExporterBOM'),
    ('excel', 'explorer.exporters.ExcelExporter'),
    ('json', 'explorer.exporters.JSONExporter')
]

So this is an existing problem I think, it was just easy to fix it like this.

Ok thanks for the feedback! I'll leave the PR as is then.


Update the Getting Started guide in the docs now that environments are created for you

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/3254
Originally created by @kgpayne on 2022-02-17 15:47:55

Once !2526 ships, users will no longer need to create their own environments, as documented in the Getting Started guide. This should be updated to just list functions, to introduce users to the created environments.
Thanks @pnadolny13 for spotting this 👏

View 1 previous comment from the original issue on GitLab


Rename KytheURI#toString() -> #asString() [phab:D1965]

Created by schroederc at 2017-10-03 16:26:08:
Also utilize new method where possible.

jrtom accepted this revision at 2017-10-03 16:33:07

schroederc closed via commit 0a833bf360fec396e4f572a6de593835f7b60e14 at 2017-10-03 16:33:55


MNT: Delete stale / unused / old branches

I have removed all merged branches, but I'll leave removing stale unmerged branches to you, as you can better identify which of them carry important commits or not.


List of DITA Open Toolkit issues which in my opinion would need to be addressed

At some point I told @jelovirt I had a list of DITA Open Toolkit issues which I considered that need to be addressed so I'm opening this issue as a way to split enumerate those issues in categories and enumerate them.

DITA 1.3 support:

Support for MathML:
https://github.com/dita-ot/dita-ot/issues/1774
https://github.com/dita-ot/dita-ot/issues/2391

Support for SVG:
https://github.com/dita-ot/dita-ot/issues/1123

Support for Troubleshooting:
https://github.com/dita-ot/dita-ot/issues/1771

Key scope related bugs:
https://github.com/dita-ot/dita-ot/issues/2410
https://github.com/dita-ot/dita-ot/issues/2393
https://github.com/dita-ot/dita-ot/issues/2525
https://github.com/dita-ot/dita-ot/issues/2523

Branch filtering related bugs:
https://github.com/dita-ot/dita-ot/issues/1998
https://github.com/dita-ot/dita-ot/issues/2147
https://github.com/dita-ot/dita-ot/issues/1999

Now various other issues:

Recent problem related to the changing of the processing stages, conref can no longer be used in keyword metadata:
https://github.com/dita-ot/dita-ot/issues/2420

Issues related to the map reference expansion which possible could be fixed by the mapref processing @jelovirt in working on:
https://github.com/dita-ot/dita-ot/issues/2494
https://github.com/dita-ot/dita-ot/issues/2476

Navigation title without locktitle in topicref overrides topic title:
https://github.com/dita-ot/dita-ot/issues/2187

PDF TOC issue which can probably be fixed now after the upgrade to Apache FOP 2.1:
https://github.com/dita-ot/dita-ot/issues/2403

Flagging no longer works with specialized @props attributes:
https://github.com/dita-ot/dita-ot/issues/2392

Distinct HTML files are created for multiple references to the same topic, even if they are in the same key scope (or there is no key scope defined):
https://github.com/dita-ot/dita-ot/issues/2363

NullPointerException in Eclipse Help output:
https://github.com/dita-ot/dita-ot/issues/1885

Issues related to chunking. Such issues usually result in broken links between topics, broken references to the CSS files...:
https://github.com/dita-ot/dita-ot/issues/2298
https://github.com/dita-ot/dita-ot/issues/2452
https://github.com/dita-ot/dita-ot/issues/2385
https://github.com/dita-ot/dita-ot/issues/2450
https://github.com/dita-ot/dita-ot/issues/2040
https://github.com/dita-ot/dita-ot/issues/2188
https://github.com/dita-ot/dita-ot/issues/2064

Problem with abbreviated-form handling:
https://github.com/dita-ot/dita-ot/issues/2067

Problem with related links and profiling attributes:
https://github.com/dita-ot/dita-ot/issues/2200

Ambiguous error messages:
https://github.com/dita-ot/dita-ot/issues/2079

PDF Bookmark part with no title generates empty entry in TOC:
https://github.com/dita-ot/dita-ot/issues/1930

As a conclusion, I think chunking has the most problems right now in the DITA OT. The DITA 1.3 support is also half baked, support for some major features is missing and there are problems with the implemented features.

I'd submit that #2576 is another must-fix branch filtering bug.
@infotexture If these critical issues can't be fixed — some of them have languished for a while — maybe we should try to identify and document the DITA implementation patterns to avoid (and workarounds where possible) to mitigate their impact.
While I'm not a big fan of having to code your DITA around the limitations of the DITA-OT, it is an open source project with limited resources, and as a matter of practice I suspect many of us do already code around specific problems we've encountered.
As an extension to this effort, maybe some of these patterns can be identified by (Schematron or other) processing early in the build (or by authoring tools) to warn users that while this is a legal DITA construct it's one that might have limited support in the toolkit.

I really like the idea @shaneataylor posted about maintaining a Schematron rule set to warn users about unimplemented or buggy OT features.

Moved into https://github.com/orgs/dita-ot/projects/19


Prevent non-deterministic package resolution in yarn

Description
If you yarn add<EMAIL_ADDRESS><EMAIL_ADDRESS>you will get two different versions of the headline component installed.  The directory structure looks like:

Since you are using the npm-sass package to compile your sass in the bolt build tool, this can lead to unpredictable results depending on how you organize your includes.
This is somewhat of a trivial example since the components-critical-fonts package doesn't actually include the headline scss, but it's the same issue for any component that depends on another component.
@import 'components-headline'; // components-headline sass v2.2.0 is included

@import 'components-critical-font'; // if this had a scss reference to the headline, v2.3.0 is included
@import 'components-headline'; // v2.2.0 is also included. v2.2.0 wins conflicting definitions

// Same, except v2.3.0 wins the conflicting definition race.
@import 'components-critical-font';
@import 'components-headline';

@import 'components-critical-font'; // You get headline v2.3.0 scss

This has other implications, like ballooning our build sizes since we are installing most packages twice.
This is a result of creating dependencies with yarn add <dependency> --scope=<topackage>
Mitigation
The issues with scss are mostly mitigated by the fact that we explicitly list our sass imports in a specific order, but that is a pretty fragile system.
Using the yarn resolutions key can also be used to lock in a single version of a package.
Resolution
I'd like to see bolt switch from using ^<package-version> to <package-version> for inter-package dependencies since that more accurately reflects how the the system is supposed to be used.
We'd have to go back and fix the packages with yarn add <dependency> --scope=<topackage> --exact.

@christophersmith262 I've got some concerns (for and against this) regarding hot fixes in one package requiring re-releasing a whole bunch of components vs allowing hotfix updates to get auto-pulled in (not auto-updating to minor and major versions obv.).
Can we chat a bit more about this one?


RuntimeError: one of the variables needed for gradient computation has been modified by an inplace operation: [torch.FloatTensor [14328, 334]] is at version 1; expected version 0 instead

When I run the model HGSL, the acm4GTN dataset can work normally. When I switch to the dblp4GTN dataset or the imdb4GTN dataset, this error occurs:(the following is dblp4GTN)
RuntimeError: one of the variables needed for gradient computation has been modified by an inplace operation: [torch.FloatTensor [14328, 334]] is at version 1; expected version 0 instead.
And I set the undirected_relations = author-paper,paper-conference for dataset dblp4GTN in config.ini file. I just can find the tensor shape [14328,334] is node type “paper” in variable h_dict, but I don’t know why it doesn’t work? Or could u add the datasets “dblp4GTN” and “imdb4GTN” for HGSL model? And what’s the differences between “acm4GTN” and “[others]4GTN”?

@lazishu2000 Please review and address this issue. Relevant discussions: https://github.com/BUPT-GAMMA/OpenHGNN/issues/137

@lazishu2000 Please review and address this issue. Relevant discussions: #137

Thanks for your reply! In the HGSL model, I even set the variable mp_ emb_ Dim=0 to skip semantic level modules, avoiding the datasets dblp4GTN and imdb4GTN without initial meta-path embeddings from metapth2vec model. But the same error will still occur. So I think there is a greater possibility of problems with the datasets, please fix it as soon as possible.

The difference is that acm4GTN has metapath-embedding which you can find in:
hg.nodes['paper'].data/hg.nodes['subject'].data/hg.nodes['author'].data
and dblp4GTN does not have it. When you simply set variable mp_emb_Dim=0 seems to cause other problems with model operation.
For now this model only support acm4GTN for training. If you have any other questions please feel free to contact us.

The difference is that acm4GTN has metapath-embedding which you can find in:
hg.nodes['paper'].data/hg.nodes['subject'].data/hg.nodes['author'].data
and dblp4GTN does not have it. When you simply set variable mp_emb_Dim=0 seems to cause other problems with model operation.
For now this model only support acm4GTN for training. If you have any other questions please feel free to contact us.

Thanks for your reply! First, I’m not simply set variable mp_emb_Dim=0. What I mean is The relevant code which needs to use metapath embeddings has been annotated. And the purpose is to eliminate the difference between datasets you have told me—Whether it has metapath embedding or not. SO What should I do if I want to use other datasets in this model? There are three datasets which are acm, dblp and yelp in HGSL paper. So I think the model should support other datasets besides acm. Could you give me some solutions about this?

Thanks for your question! According to your requirements, we are going to add dblp and yelp datasets for HGSL training, considering it as an extension of HGSL model.
we will make it work as soon as possible, but the extension won't be our first priority. If you want to get results faster , adding embeddings for metapath as we mentioned in https://github.com/BUPT-GAMMA/OpenHGNN/issues/137 is a possible solution.

We support dblp4GTN and yelp4HGSL  for HGSL model now !
Relevant commits :
https://github.com/BUPT-GAMMA/OpenHGNN/commit/1b31a37ab25c9e10f885f65f8ea001e6af110199
https://github.com/BUPT-GAMMA/OpenHGNN/commit/eec0bdf8957bf6c9d1f0d46c18952ca690fc7171
For your reference ~

We support dblp4GTN and yelp4HGSL for HGSL model now ! Relevant commits : 1b31a37 eec0bdf For your reference ~

Thanks! The results is almost same as my constructed datasets  from the HGSL source code.


showInformationMessage promise never completes if notification is dismissed with ESC

Seems like this has come up and fixed before in #5797, but I'm seeing it today.
Eg. this code:
try {
	const a = await vs.window.showInformationMessage(
		`This is a test....`,
		"DO THING",
	);
	console.log(`User picked ${a}`);
} catch {
	console.log("CATCH");
} finally {
	console.log("FINALLY");
}

Never outputs anything if the user hits <escape> to dismiss it.

ESC does not dismiss the notification, it will still be there in the notifications center. Closing it there will wire up the promise properly.

Oh whoops, didn't realise I could get to them there. That solves my issue then, thanks! 👍


Dropdown Orientation

I have a simple issue possibly already covered here.
My dropdown drops down horizontally rather than the default vertically.
I am having a look at the documents for Drop as suggested.
I have tried setting mode to click and position on vk-dropdown to something vertical for example. I set mode="click" with success for example. Set position has no effect.
I have tried importing the uikit — without the v — stylesheet following your suggestions in the issue cited above. Tried direct reference to the local version in node_modules as well as importing it in main.js of my Vue template as follows.
// The Vue build version to load with the `import` command
// (runtime-only or standalone) has been set in webpack.base.conf with an alias.
import Vue from 'vue'
import App from './App'
import router from './router'

import Vuikit from 'vuikit'
import VuikitIcons from '@vuikit/icons'
import '@vuikit/theme'
import 'uikit/dist/css/uikit.min.css'
import UiKit from 'uikit'

Vue.use(Vuikit)
Vue.use(VuikitIcons)

And so on. My HTML follows the «Nav in Dropdown» snippet in your docs and looks like this.

    <div class="vk-inline">
      <vk-button type="default" size="large"><i class="material-icons">local_bar  </i> Drop Down Tonight</vk-button>
      <vk-dropdown position: top-center mode='click'>
        <vk-nav-dropdown>
          <vk-nav-item title="Monkeys" active></vk-nav-item>
          <vk-nav-item title="Gazelles"></vk-nav-item>
          <vk-nav-item  title="Lions"></vk-nav-item>
          <vk-nav-item title="Jackals"></vk-nav-item>
          <vk-nav-item title="Warthogs"></vk-nav-item>
          <vk-nav-item>Water Buffalo</vk-nav-item>
          <vk-nav-item title="Rhinoceros"></vk-nav-item>
        </vk-nav-dropdown>
      </vk-dropdown>

Having initial difficulty with modal and offcanvas as well but one thing at a time. Thanks hope I am not abusing your kind attention.

What fixed it for me was simply removing the optional ` as a wrapper for the dropdown.
Again thanks for kind assistance.
cb

@bretonio, what do you mean? Do you have any feedback on how could we improve the component or the documentation?

Sorry if I was abrupt! I was a little confused when the VUIKit docs cited
tags with uk prefixes here and there. On the whole the docs are very
helpful however. Perhaps a CDN setup might be welcomed by some users. Keep
up the excellent work I actually find the Vue framework easier to grok than
the original.
cb
On Sun, Apr 15, 2018 at 7:13 AM, Miljan<EMAIL_ADDRESS>wrote:

@bretonio https://github.com/bretonio, what do you mean? Do you have
any feedback on how could we improve the component or the documentation?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/vuikit/vuikit/issues/83#issuecomment-381395055, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ATmAq7xgBiFATWvdPlqZu1YXOIOR3bMYks5tox0zgaJpZM4TG6o3
.

UIkit takes cares of the layout and styling, while Vuikit of rendering it and executing the JS, as such both coexists. I will add some notes about that and avoid confusions with the prefixes.
As for the CDN, you can use the cdnjs one. Will also update the docs about it.
Thanks for you feedback @bretonio.


IDE auto complete friendly documentation of classes and methods

Hello,
I noticed when using pyzmq, that the library does not seem to be very friendly towards the auto completition feature of my IDE, which is pycharm.
It seems that the comments are written in restructured text and sphinx is used to generate the docs. To make the comments IDE friendly http://sphinx-doc.org/domains.html#info-field-lists could be used.
An example what does not work for me is
s = context.socket(zmq.SUB)
s.bind('fooar')  # bind is not available via auto complete, but bind_to_random_port

Also not all constants seem to be available via auto complete. For example zmq.SUB for the subscriber socket. I tried to understand why these are not shown and my guess is, that it has something to do with them being implemented in cython. http://stackoverflow.com/questions/31766219/export-constants-from-header-with-cython seems to have a solution to the problem.

I'm not sure how PyCharm populates its completion. Does it use static code analysis, or does it actually import things?
pyzmq embeds signatures in numpydoc/napoleon format, which I think is a better compromise for humans vs machines than the linked info-fields, which make for much less pleasant docstrings to my eye.
As for the Cython-defined constants, I don't think that SO question addresses the issue of whatever PyCharm's inspection is failing to do, since it seems to be about constants not being available at all to Python, which is not the case in pyzmq. If pycharm imports the library, it will find these values in dir(zmq).

Should be fixed in 15.2

I'm using 15.2.0, and this doesn't seem to be changed.
You can see a screenshot of what PyCharm is autocompleting here: http://cl.ly/3O323a2r3S2B
doing a dir(zmq) doesn't show things like zmq.SUB or zmq.SUBSCRIBE, and these show as unknown references in the IDE.

If dir(zmq) isn't showing those, then it seems like you don't have a working pyzmq. How did you install it? Does anything run? Completion works in IPython, and SUB certainly should be in dir(zmq):
In [1]: 'SUB' in dir(zmq)
Out[1]: True

In [2]: zmq.S<TAB>
zmq.SHARED        zmq.SNDHWM        zmq.SNDTIMEO      zmq.SOCKS_PROXY   zmq.STREAM        zmq.SUB           zmq.Socket
zmq.SNDBUF        zmq.SNDMORE       zmq.SOCKET_LIMIT  zmq.SRCFD         zmq.STREAMER      zmq.SUBSCRIBE     zmq.Stopwatch

In [2]: zmq.__version__
Out[2]: '15.2.0'

I'll chime in to say that I'm experiencing the same issue on PyCharm 5.0.4 under Python 3.4.4 64bit installed using conda.  My pymq version is 15.2.0.  If I load it into IPython the autocompletion works just fine and "DEALER" in dir(zmq) returns True in IPython and the default python REPL.  The constants are certainly in __all__ for zmq, zmq.sugar, and ultimately zmq.backend.cython.constants.  I'll say that zmq.constants.<TAB> does not show the constants but instead just the values like base_names, int_sockopt_names, etc.
PyCharm gives the following warning when it can't find a name, such as zmq.DEALER:

This inspection detects names that should resolve but don't. Due to dynamic dispatch and duck typing, this is possible in a limited but useful number of cases. Top-level and class-level items are supported better than instance items.

So I think what is happening is that PyCharm is not actually importing zmq to provide completions but instead relying on static analysis which is failing in this particular case.  To get it to play well with PyCharm you would probably have to list each export individually.
Hope is not lost, Python has a trick up it's sleeve.  I noticed while poking around in the pyzmq code that you've used the style
from module import submodule1
from module.submodule1 import *
from module import submodule2
from module.submodule2 import *

__all__ = submodule1.__all__ + submodule2.__all__

But Python has a better way through from __future__ import absolute_import
from __future__ import absolute_import

from module.submodule1 import *
from module.submodule2 import *

__all__ = submodule1.__all__ + submodule2.__all__

So if you have them listed out explicitly in __all__ in some lower level module you can use this style all the way up in a less dynamic manner.  This also works in Python 2, I think as early as 2.5 with the __future__ import.  I don't know how well it plays with Cython imports, though.

Apologies, the entries do show up in dir(zmq), but @bheklilr is right that PyCharm does static analysis, so these references aren't found.
The solution I came up with is to make a skeleton for zmq as seen at https://www.jetbrains.com/pycharm/help/using-python-skeletons.html
For the purposes of zmq, something like the output of:
import zmq
for a in dir(zmq):
    if isinstance(getattr(zmq, a), int):
        print "{} = {}".format(a, getattr(zmq, a))

when placed in zmq.py in the appropriate config-directory will do. This isn't perfect, but does address the problem of the constants not being recognized in PyCharm

Adding type annotations for zmq package to https://github.com/python/typeshed would help a lot of people I guess.


[BUG] IRC connection is lost, and wont re-connect without completely restarting TAU.

Describe the bug
Occasionally the websocket connection between TAU and IRC will be lost, and even when telling TAU to reconnect or refreshing tokens, will not reconnect.  This seems to happen after several days.
To Reproduce
Steps to reproduce the behavior:

Run TAU, and have it connect to IRC.
Wait 3-5 days.
Eventually the connection to IRC will be lost.
Attempt to get TAU to reconnect without restarting everything.

Expected behavior
When the IRC websocket is disconnected, TAU should attempt to reconnect, until it is able to re-establish a new connection is set up.

Fixed by #97

Oops, closed the wrong issue.


Update Packet branding to Equinix Metal - index

Please update any Packet.net menu items to match Equinix Metal. Also I was unable to have the Equinix Metal SVG load in, and was wondering if it would be possible to get that on the page as well? Thank you!

Proposed changes

Unreleased product version (optional)

Related issues (optional)

Hi @etrosa
We actually have an equinix metal page already - the packet.net page will auto redirect to that new page and the old one will be removed this week
https://www.pulumi.com/docs/intro/cloud-providers/equinix-metal/
So I'm going to close this PR out if that's ok?
We also added a deprecation message across the top of our old packet.net provider api reference pages to say use the equinix metal provider
Hope this is all ok
Paul

Hi  Paul thank you for updating me. The Equinix Metal page looks good thank you!


refactoring!: fixing all the static analysis warnings

@GZGavinZhao I think we need to bump the minimal SDK version to 2.18.0.

@ykmnkmi I'm okay with it. You also might need to lock build_modules to ^4.0.7

Oh also, if you would like to sign your commits when your PR is ready that would be great. So far I've been manually squashing the commits and signing them using my keys (which is why you sometimes see commits are authored by you but committed by me), and I'm happy to keep doing so, but if it's convenient for you to sign them then that would be great :)

@GZGavinZhao thanks for helping with commits and PR's.


GH-3074: read footer using 1 call readFully(byte[8]) instead of 5 calls

GH-3074: read footer using 1 call readFully(byte[8]) instead of 5 calls
Rationale for this change
performance
What changes are included in this PR?
only method FilePargetReader.readFooter()
Are these changes tested?
Are there any user-facing changes?
no

Could you try to rebase it? I think the CI failure is due to based on a problematic commit.


Interoperability requirements: avoid parenthesis in CURIE

I expect
to avoid parenthesis in curie

@ioggstream could you please provide an example? Parentheses are used in some URIs of some controlled vocabularies and are fine according to URIs rules.

@Clou-dia chiuderei questo issue. Non possiamo cambiare URI consolidati da anni (esempio sulle città, vocabolario critico) soprattutto quando la cosa è anche ammessa (esempio DBPedia le usa).

@giorgialodi since parentheses can break parsers (e.g. during harvesting), the safe choice is to encode them (e.g., %28 / %29 ) when serializing entries.
This does not mean to forbid them.

if you want to escape them internally to the harvester (I image you are referring to schema harvester), it is ok since it is an internal technical stuff, but they won't be escaped in actual URIs (in the RDF files I mean).


This is in order, right?

Challenge Comment out HTML has an issue.
User Agent is: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:47.0) Gecko/20100101 Firefox/47.0.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:

CatPhotoApp

CatPhotoApp

Please refer Help I have found a bug and head on to the chat please.


[volk] Remove the volk port

After discussing with the volk author we decided that building volk separately can currently not be supported due to the implementation file depending on various preprocessor defines that the user project must set. Making those CMake options in volk and features in vcpkg doesn't seem a good fit for this library because it's mostly auto-generated code and that part would have to be maintained manually. The CMake-package-config support in volk was therefore removed.
For the same reason the vcpkg port I added recently should be removed as well -- if actually used, the aforementioned defines likely have the wrong values (...and the vulkan platform-specific extensions will be unavailable in volk).

Curious to see how this will be managed. Currently vcpkg is not ready for the fully removal of a package, but eventually it would have happened such a situation

Well, it makes sense that that would be a tricky situation. But hang on, we may still be able to avoid this mess altogether. It might make a lot of sense to put the lib into vcpkg (and CMake package config) in header-only style, but that's a bit of a change in philosophy upstream, I'm still discussing that with the library author.

typically we don't remove ports from vcpkg because we don't want to break users.  If we can show that no one is using this port then we would probably make an exception.  If someone is using it then we would probably keep the port but deprecate it so it will warn users that it may not be supported in the future and discourage new users.  For now I will wait to hear the result of your discussion with the author.

It took a while, but good news! I gave the library config-file package support and an optional header-only usage mode upstream. This means the volk port now makes total sense, after a small update. I will shortly submit that update as its own PR and close this one.


fix: make light client events spec compliant

Motivation
Make sure returned eventstreams follow the spec
Description
Current implementation of some eventstream values do not follow the spec (missing data indirection and version field).
Closes #6197

From reviewing the spec, I noticed that is states that sync_aggregate fork might be different and is based on signature_slot
specs/altair/light-client/p2p-interface.md?plain=1#L245

A ForkDigest-context based on compute_fork_version(compute_epoch_at_slot(optimistic_update.attested_header.beacon.slot)) is used to select the fork namespace of the Response type. Note that this fork_version may be different from the one used to verify the optimistic_update.sync_aggregate, which is based on optimistic_update.signature_slot.

I don't think we are following the spec here, but based on our current design of spec types it is difficult to use a different fork type for nested properties.
This seems to be mostly relevant during a hard fork and only if the SyncAggregate changes between those forks.
@wemeetagain @g11tech any thoughts?

unrelated e2e test failed due to timeout

:tada: This PR is included in v1.15.0 :tada:


Updating file naming system for S3

Separated out a source date and destination date
Each can be configured separately
Added a timestamp
Removed global transtive=true setting for gobblin-core
Allows you to batch all new logs together or separately

Transitive issue is continuation from #27.

Ready for review @akshayn1107

lgtm


Add dex2jar.vm

Add a shortcut for d2j-dex2jar.

Merging this as it is included in https://github.com/mandiant/flare-vm/pull/490 and I want to create a new VM using the new configuration. 😄 If someone has any feedback on this PR, please open an issue/PR for further discussion.


[SourceKit] Use stack of argument mappings when walking the syntax model

A single map of arguments allows an argument to be added to an incorrect
node, eg. when the parent node isn't handled but the argument is mapped.
Use a stack of (parent, mappings) instead and check that the parent
matches to ensure this cannot happen.

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - b549b52dc34e18c0ca9bd0e85ab52c0d7c2561c4

Build failed
Swift Test OS X Platform
Git Sha - b549b52dc34e18c0ca9bd0e85ab52c0d7c2561c4

@swift-ci please test


Git commit silently ignores commit.gpgsign

Lapce Version
666c4afac532670d7f22353ceab9c6f599ec6abf
System information
Ubuntu 22.04 Gnome
Describe the bug
I have my Git configured to automatically sign commits. When I commit in Lapce, commit succeeds without applying my signature or notifying me that my commits are unsigned. I tested in VS Code and it at least prompts me that GPG signing failed.

Duplicate of https://github.com/lapce/lapce/issues/96


small diff in global aggregate

Regional and global poverty estimates are not identical between the old [povcalnet] and new [pip] command. For example, headcount ratio for the world in 2017 is 9.27% or 9.29%, respectively
@tsamuel321 @tonyfujs @Aeilert @Tefera19

I think the differnece is due to the updates on small updated in microda, right @Aeilert ?

Working on it.
@Tefera19 , Please make sure you address this.
Thanks.

@randrescastaneda : There is a small difference in the total number of poor between PovcalNet sept 2021 (697) and PIP soft launch (698). I would guess that also affects the ratio.
FYI: I think the remaining diff here mainly stems from LAC, possibly due to handling of u/r surveys, but we haven't pinpointed the issue. For soft launch we should be fine anyways.

@randrescastaneda : I have checked the ado file and I've found any problem. Here is how the aggregate data is pulled from the server.
import delimit using "https://apiv2qa.worldbank.org/pip/v1/pip?year=all&country=all&reporting_level=all&povline=1.9&group_by=wb&format=csv", clear varn(1)
Thanks

@randrescastaneda @Tefera19 For group_by=wb, reporting_level should be equal to "national", not "all"
Hopefully this confusion will disappear once the pip-grp endpoint is correctly mapped

@randrescastaneda @Tefera19 For group_by=wb, reporting_level should be equal to "national", not "all" Hopefully this confusion will disappear once the pip-grp endpoint is correctly mapped

But this won't solve the problem. Right?  I mean, the difference in the global poverty rate is not due to this, is it?
Best,
Andres

I have tried reporting_level = national and it hasn't changed the result.
Best,
Tefera

Deprecated.


#104: use TLS certificates in scbe backend

This change is

Coverage decreased (-0.2%) to 51.048% when pulling 71a5d5aca3e6d72e9c4825da1c8df78d9a324a8b on feature/liort_scb_tls into 44e558ef4a81694ebffb3cc765aecd5667764b86 on dev.

Coverage increased (+0.2%) to 51.448% when pulling 16e6feb421ab1e2ef256517ae55e8d8699effb9a on feature/liort_scb_tls into 44e558ef4a81694ebffb3cc765aecd5667764b86 on dev.


investigate setting install name

on macOS, dylibs should have their install_name (set with install_name_tool -id) set to the name that should be used to load the library. At its most specific, this should be the ABI-compatible version (*.4.dylib or *.4.5.dylib). However, the libs from suitesparse appear to set their install_name to their full name (e.g. libsuitesparseconfig.4.5.4.dylib), indicating that every patch-level release can make ABI changes.
This means that all downstream packages have to pin their dependency on suitesparse to the patch-level, because any upgrade to suitesparse, even a compatible one, will result in an image not found error on the old location:
Library not loaded: @rpath/libsuitesparseconfig.4.5.3.dylib
  Referenced from: /Users/minrk/conda/envs/petsc/lib/libslepc.3.7.dylib
  Reason: image not found

(here slepc shows an example of how this can be done: libslepc's install_name is libslepc.3.7.dylib, even though the actual file is libslepc.3.7.1.dylib)
Setting the install_name to the general (version-less) path or the ABI-compatibility version would allow for upgrading suitesparse to a compatible version without needing to rebuild the downstream package.
This should probably be reported upstream to suitesparse itself, but it can be addressed in the conda package by running install_name_tool -id ... in build.sh after make install.

This definitely was an issue with 4.4.*. However 4.5.* and 5.* have not had this issue.
ref: https://abi-laboratory.pro/tracker/timeline/suitesparse/

This is still an issue with 4.5.6.
Note that this issue is not about an ABI breakage. It's the opposite. The ABI is fine. It's theinstall_name, which causes linking to fail to find the file. If it found the file, it would load fine. It is compatible, it's just using the wrong filename, which makes it fail to be found, even though it's compatible.
Here's a quick test with a dummy test.c:
int main(int argc, char const *argv[])
{
    return 0;
}

export PREFIX=/tmp/suite-env
conda create -y -p $PREFIX suitesparse=4.5.4
cc -L$PREFIX/lib -lsuitesparseconfig test.c -o test
./test # ok
conda install -y -p $PREFIX suitesparse=4.5.6
./test # fails

Running a program linked against 4.5.4 with 4.5.6 installed fails with:
dyld: Library not loaded: @rpath/libsuitesparseconfig.4.5.4.dylib
  Referenced from: /Users/minrk/dev/temp/./test
  Reason: image not found
Abort trap: 6

The install_name should not be the full libsuitesparseconfig.4.5.4.dylib, it should be libsuitesparseconfig.dylib (or .4.dylib). That's what #23 fixes.

Ah ok. Misread. Thanks for the clarification.


Directive 'track_errors' is deprecated (PHP v7.2.0)

Laravel Version: 5.5.23
PHP Version: 7.2.0
Database Driver & Version: MariaDB (v10.2.11)
OS: Windows 10 Pro (v10.0 build 16299)

Description:
We are receiving the following errors when we used 'composer update':

Deprecated: Directive 'track_errors' is deprecated in Unknown on line 0
PHP Deprecated:  Directive 'track_errors' is deprecated in Unknown on line 0

Steps To Reproduce:

Update PHP engine from v7.1.11 to v7.2.0.
Update Laravel from v5.5.22 to v5.5.23 using 'composer update'.
Errors will be shown in the command line.

Note: If PHP v7.2.0 is replaced with v7.1.12, then the error disappears.

Laravel does not use track_errors.

Update Laravel from v5.5.22 to v5.5.23 using 'composer update'

That is basically a blind "upgrade every package I have"-command. It upgrades everything, not just laravel/framework. Use composer update laravel/framework to update a specific package, or composer require laravel/framework:5.5.23 to grab a specific version.


Oberstufenzentrum Technik Teltow (OSZ Teltow)

@notbemji First stage of verification passed, official domain is osz-teltow.de as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@notbemji Pull request merged. Thank you!


Send heartbeats every 30s

previously they were sent every 60s, which is dangerous with the default BOSH HM agent timeout of 60s.

Looks good to me.


[Improvement] Replace code coverage tool Jacoco with codecov or something else

What would you like to be improved?
Jacoco is not allowed in the Apache project and has been removed since #4030. However, we require a similar tool to replace it and obtain test coverage data.  codecov is a good option, and we can try it or something similar.
How should we improve?
No response

We could also ask Infra to allow Jacoco

We could also ask ASF Infra to allow Jacoco

So how can we ask ASF infra to allow Jacoco?

You can ask on teh infra channel on teh ASF slack, and they will probably ask you to raise an Infra JIRA to do the work.


socket.emit inside ss(socket).emit(...) callback doesn't arrive

My Node.js application is working fine, and the piece using socket.io-stream was working fine untill I picked up development (since ~4 months inactivity).
First of all, I the browser uploads a file, the server receives it, reads it, and should notify the browser with some information. I can see the server receiving and reading the file(s) without any problem through the console. However, the browser doesn't receive the emits sent by the server. My code is as follows:
ss(socket).on("purchase_image", function(stream, data) {
		console.log("-- image");
		...
		temp.open({
			suffix: suffix
		}, function(error, info) {
			if (!error) {
				stream.on("error", function(error) {
					console.log("error");
					console.log(error);
				});
				stream.on("end", function() {
					console.log("purchase_reading emitted");
					socket.emit("purchase_reading", {
						status: "start",
						tmp_name: info.path
					});
					...

Has something changed in the way I should be emitting data back to the client from within the socket.io-stream callback?

Do you mean you can't receive the purchase_reading event on browser? How your client code looks like?

Exactly, and my code is:
socket.on("purchase_reading", function(data) {
	console.log(data);
	if (data.status == "start") {
		$("#progress_upload").data("status", 1).switchClass("", "progress-bar-success", function() {
			//For some reason the 100% width gets removed, so add it again afterwards
			$(this).css({width: "100%"})
		});

		$("#reading").data("status", 0).switchClass("label-default", "label-primary");
		$("#reading").find(".fa").addClass("fa-spin");
		$("[name=file_tmp_name]").val(data.tmp_name);
	} else {
		console.log("end");
		if ($("#progress_upload").data("status") == 0) {
			//The user has uploaded another document in the meanwhile
			return true;
		}
		$("#reading").data("status", 1).switchClass("label-primary", "label-success");
		$("#reading").find(".fa").removeClass("fa-spin");
	}
});

I've also tried wrapping 'socket' in ss(), but did not help either.
EDIT DURING WRITING: I just realised this event binder is not inside $(document).ready(...). As this piece of code is used on multiple places within the project, I "couldn't" wrap it inside ready(). I tried to confirm this, and the event arrives. I guess this has to do with some performance updates resulting in a "too quick" page load.
In other words, it has been solved, but thanks for your quick reply! If the issue won't help anyone, feel free to delete it ;).


[Impeller] Allow accessing the capabilities of a context and along with default attachment pixel formats.

We should remove kDefaultColor and kDefaultStencil.
Make impeller::Context return a capabilities object.
Make the capabilities object return the color and stencil format recommendations. The recommendations will be supported on the target platform.
Make the capabilities object immutable.
HasThreadingRestrictions and SupportsOffscreenMSAA into the new capabilities object. These are on the context today.

cc @iskakaushik


Pose not working on in Android WebView using Chrome 62+

WebVR polyfill doesn't provide device movement tracking in an Android WebView using

Chrome Stable/Beta/Dev/Canary 62.0.3202.66+
Android System Webview version 62.0.3202.66+

Working as expected using Chrome Stable 61.0.3163.98
Adding an event listener for 'devicemotion' returns an initial event object but no subsequent events as expected.
Issue discovered can be easily replicated by visiting any site using the WebVR polyfill in the aforementioned WebView versions, ex. samples on https://aframe.io

Thanks for filing!
For the record, many of the examples on aframe.io use older versions of aframe and the polyfill.

@jsantell - tested this exhaustively and it appears to be an issue with the DeviceMotion API in Chrome 62+. We ran into this problem on a project, and have tested across a wide range of Chrome/Android System Webview versions. The A-Frame samples are just an easy way to visually reproduce the issue, although a simple window.addEventListener('devicemotion', console.log, true) will expose it too. Not sure if this issue is relevant to the WebVR polyfill necessarily - sorry. Have opened an issue on the Chromium bug tracker.
Thanks

Thanks for digging into this, @meatwallace -- definitely something we'll need to handle for the polyfill. I'll keep an eye on the Chromium issue. Thanks for putting this on the radar!

No worries. Although the issue is with Chromium, if there's anything you think we should testto accelerate resolving the issue, would love to hear.
The release of Chrome 62 happened the day before our scheduled product launch, so we're heavily invested in resolving or finding a workaround for the issue. We've tried:

Passing sensor data into the WebView and generating synthetic DeviceMotion events. As expected, it suffers from performance and latency issues, rendering it unusable.
Using Origin Trials to enable experimental features. It turns out this is unavailable in a WebView, so we can't use the native WebVR API, and we can't write a new pose sensor with the Generic Sensor API.

One of our engineers is working on using a CrossWalk WebView. Seems like the easiest way to bundle a locked version of Chrome. As it's not maintained, this isn't a desirable solution. When complete, I'll share the results, although as it's using Chrome 53, I think we'll run into perf issues.
Beyond that, we're investigating bundling Chrome itself with our app so that we can lock the version, but haven't found any clear strategy for doing so, and our skillset isn't suited for the task.
If anyone has knowledge about bundling Chrome, or any alternative avenues to explore, please shout out! I don't know how widespread this use case is - I imagine it's niche, but if it's affecting anyone else, we would love to collaborate to resolve it.
Sorry if I've gone too far out of scope of the polyfill. As we could be waiting for a patch in Chrome for a while, I figure this is a good place to discuss workarounds in the interim.
Cheers

I just verified the Chrome fix that was merged and released in the Canary build: https://bugs.chromium.org/p/chromium/issues/detail?id=779443
If you have an Android 8 device, you can preview the fixed version by downloading Chrome Canary from the play store, then changing your WebView implementation in developer settings.

Looks like this is fixed in m63+, and with m62 out currently, not sure what a possible workaround is unfortunately :confused: let's leave this issue open if there are any immediate short term fixes we can do on our end

Whilst not an optimal solution at all, we've bundled the last release of the Crosswalk WebView (uses Chrome 53) with our app and are conditionally using it if we detect Chrome / Android System WebView 62.x on the device. Minor performance regressions and it tacks ~40mb onto our bundle, but it works.

Fixed in Chrome 63+, looking into solutions that can prevent this sort of breakage on Chrome's end; closing for now, thank you for reporting and following through on this issue @meatwallace!


Outside users (sometimes?) able to post on AUP jobs board.

Kate Kolendo reported an issue where an outside user was able to post to the AUP jobs board. The board should be publicly visible but only AUP members should be able to create jobs.

I believe this issue was caused by the fix persisting logins across domains. Previously the jobs site was checking whether a user was logged in to determine whether they could post a job. This was fine when logins failed to persist across networks, but now that they do it is necessary to check whether the logged in user has the UP society membership.
A filter was added to humanities-commons to check for this, and an action was added to display a message when a user does not have permission to post.
(The commits are a bit messed up here due to an error in the initial commit.)

commons-235-prevent-outside-users-from-posting-jobs-on-up
commons-235-check-society-membership-for-job-posting

Note: moved this functionality to the aupresses-jobs theme


bug: the code spills to the left hand side

Describe the bug
the code does not complete due to the fact that it creates the code in the left hand side instead of the actual editor itself
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-zxv3av
Steps to reproduce
This is my prompt: Build a fully blown app using react, javascript and tailwindcss with appwrite as the backend that helps people to find new jobs. Use anthropic AI and ChatGPT for analysis of jobs. Sign in with github and google should be present. Let it have a lot of features including resume ai and building, ability to get profile info by updating LinkedIn bio profile pdf, job copilot, interview prep with questions, learning roadmap, dashboard, social connections and explore pages and all
See what it does
Expected behavior
it should write the code in the files and editor
Screen Recording / Screenshot
No response
Platform
Browser name = Chrome
Full version = <IP_ADDRESS>
Major version = 129
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
performance.memory = {
  "totalJSHeapSize": 300111586,
  "usedJSHeapSize": 127525114,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Username = fasakinhenry
Chat ID = 306341a599fb

Additional context
No response

Hey @fasakinhenry! I think you're running into the same issue as #26. I'll close this issue, feel free to reopen if you think your issue is actually different.


Does CFF allow for more than one citation per file?

working on https://github.com/ropensci/handlr/issues/16 and it's not clear to me if you can have more than one citation in a cff file. It doesn't look like that is supported, but wanted to check to make sure

Answered in https://github.com/ropensci/handlr/issues/16.


Add Default trait to Fe32 (derived)

See #187 .
Add derived Default trait to Fe32, and ZERO constant.
Default is trivial and useful in some cases.

API doc updated

Thanks for the contribution. In my personal opinion patch 2 is a NACK (I'm not a maintainer here though). How is this better than using Fe32::Q. Also it begs the question why not have numerics for all 24 characters, and that would be horrible IMO.
(Also, just in general this PR is doing two things. This crate is getting pretty close to being stabalized (in my opinion) so I think we should be extra careful patching it).

Oh there are two PRs (also #185), can you drop the second patch off this PR please.

Oh boy, this is all mixed up, I got confused. You have the changes in #184 and #185 in a single patch described in two PRs.

I created separate PRs for all the different changes (Default trait, ZERO const, Ord trait), to keep changes minimal.
But the ZERO const was in fact in this PR as well. I've removed it now.

Ok, I'd like to see the commit history cleaned up for this one. It can probably be done in a single commit, so squashing might work.

Squashed into one commit

Looks like this slipped through the cracks, can you merge this please @apoelstra


Can I please ask a few beginner questions?

Hi @teticio , I've come across your guide for this repo. Looks amazing! I'm trying to follow instructions but have never done anything with Terraform, AWS CLI, or Lambda before so I'm a little confused about a few things. Your instructions seem clear and straightforward but I'm a little lost through inexperience.
 I don't know where else I could message you so is this the most appropriate place? In the issues section of your repo? Because I wouldn't classify this as an "issue" 😅

Sure. You can email me at @.*** Happy to help
On Sun, 11 Jul 2021 at 07:51, chrisjdixon @.***> wrote:

Hi @teticio https://github.com/teticio , I've come across your guide
https://medium.com/nerd-for-tech/web-scraping-with-a-proxy-pool-the-cheap-way-4c7d6fc9f859
for this repo. Looks amazing! I'm trying to follow instructions but have
never done anything with Terraform, AWS CLI, or Lambda before so I'm a
little confused about a few things. Your instructions seem clear and
straightforward but I'm a little lost through inexperience.
 I don't know where else I could
message you so is this the most appropriate place? In the issues section of
your repo? Because I wouldn't classify this as an "issue" 😅
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/teticio/lambda-scraper/issues/1, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKRPDBZSSWZXIVBK62P3W2LTXE5NVANCNFSM5AE7YFUA
.

Hi man, i'm a beginner in that field, i followed your instructions but when i lunch i got the error in the image
PS C:\Users\elvis\Desktop\Web_scrapper\lambda-scraper> terraform apply -auto-approve ╷ │ Error: Plugin error │ │   with module.lambda_function[3].module.source_zip_file.data.external.archive[0], │   on .terraform\modules\lambda_function.source_zip_file\main.tf line 28, in data "external" "archive": │   28: data "external" "archive" { │ │ The plugin returned an unexpected error from plugin.(*GRPCProvider).ReadDataSource: rpc error: code = Internal desc = │ grpc: error while marshaling: string field contains invalid UTF-8

What OS are you running on? I just tried running it on Windows and had some issues (different from yours). Unfortunately it looks like an issue with the Lambda function module which is developed by someone else. It works on Linux no problem.
I did remove a file from the repo that might solve your problems. Try running everything from scratch in a fresh directory.

OK, I have changed the module for Lambda functions to another provider and it now works on Windows. There was a small wrinkle when I ran it - it had some problem moving a file as it was in use - but running it twice did teh trick (don't worry, terraform will not create double the resources if you run it twice!). Hope this helps. (Again start from scratch in a new folder. To be on the safe side, run "terraform apply -destroy" in your existing folder in case there are some artefacts left over from a partial deployment.)

Thanks a lot it works, i'm using Windows. Really appraciate, thanks to share this template with us. Have a good one! 👍


Error while evaluating tflite model with bazel run_eval

Hi, i managed to train a SSD_mobilenet_v1 using model_main_tf2.py. After that i managed to export with export_tflite_graph_tf2.py changing the max_detections paramenter to 33, and then i successfully exported a tflite model. I tried then to run some inference with the new tflite model and it worked as expected.
I decided then to try to evaluate  the tflite model using this guide,  but when i run this command:
bazel run -c opt -- //tensorflow/lite/tools/evaluation/tasks/coco_object_detection:run_eval --model_file=/home/gab/PycharmProjects/tensorflow_prova2/new_model_quant_F16Q.tflite --ground_truth_images_path=/home/gab/PycharmProjects/tensorflow_prova2/images  --model_output_labels=/home/gab/PycharmProjects/tensorflow_prova2/label_map.txt --output_file_path=/home/gab/PycharmProjects/tensorflow_prova2/coco_output.txt --debug_mode=true
output shows odd results like this:
Object [0]
Score: 33
Class-ID: 1
Bounding Box:
Normalized Top: 0.999825
Normalized Bottom: 0.999262
Normalized Left: 0.999445
Normalized Right: 0.999066
Object [1]
Score: 0
Class-ID: 1
Bounding Box:
Normalized Top: 0.998896
Normalized Bottom: 0.997808
Normalized Left: 0.998822
Normalized Right: 0.996969
Object [2]
Score: 0.780337
Class-ID: 1
Bounding Box:
Normalized Top: 0.996294
Normalized Bottom: 0.988497
Normalized Left: 0.994716
Normalized Right: 0.985629
Object [3]
Score: 0.479028
Class-ID: 1
Bounding Box:
Normalized Top: 0.972919
Normalized Bottom: 0.0584207
Normalized Left: 0.0640493
Normalized Right: 0.0434026
Object [4]
Score: 0
Class-ID: 1
Bounding Box:
Normalized Top: 0.0374295
Normalized Bottom: 0.0290796
Normalized Left: 0.0313877
Normalized Right: 0.0227272
Object [5]
Score: 0
Class-ID: 1
Bounding Box:
Normalized Top: 0.0221782
Normalized Bottom: 0.0208216
Normalized Left: 0.0213712
Normalized Right: 0.0207996
Object [6]
Score: 0
Class-ID: 1
Bounding Box:
Normalized Top: 0.0199532
Normalized Bottom: 0.0192215
Normalized Left: 0.0193954
Normalized Right: 0.0187497
Object [7]
Score: 0
Class-ID: 1
Bounding Box:
Normalized Top: 0.0186509
Normalized Bottom: 0.0180727
Normalized Left: 0.0181409
Normalized Right: 0.0176707
Object [8]
Score: 0
Class-ID: 1
Bounding Box:
Normalized Top: 0.0176005
Normalized Bottom: 2.02493
Normalized Left: 0.0637459
Normalized Right: 0.325256
This is for the first image of the folder i used, one thing i noted is that the first score of the first object is always 33 that is the parameter i changed when i exported the trained model with export_tflite_graph_tf2.py
Is there a way to fix this so i can evaluate my tflite model?
Thanks

@gabrielecorsi97
Could you please provide reproducible code or Colab gist for reproducing the issue reported here?
Thank you!

You can download my model here.
Also my folder images is here and my label_map.txt
These are the inputs for running the command from which i get bad results
Tell me if you need all the code from the training to the conversion of the model.
Thanks again.

@gabrielecorsi97
Kindly provide the complete code from the training to the conversion of the model. Thank you!

Basically i followed this tutorial, i selected the SSD MobileNet V1 FPN 640x640 from the Model Zoo
I  modified the pipeling.config and used this label_map.pbtxt
Then i runned this command:
python model_main_tf2.py   --pipeline_config_path=<path to your config file>   --model_dir=<path to a directory with your model>   --checkpoint_every_n=500   --num_workers=8   --alsologtostderr
And this command:
python object_detection/export_tflite_graph_tf2.py      --pipeline_config_path path/to/ssd_model/pipeline.config      --trained_checkpoint_dir path/to/ssd_model/checkpoint      --output_directory path/to/exported_model_directory
but in the file export_tflite_graph_tf2.py i changed the max_detections from 10 to 33
After that i wrote this script to convert the savedModel to 3 tflite model with 3 different quantization method [model1][model2][model3].
I tried to do some inference with those and all seemed to work as intended (performance seems a bit slow but that is another problem)
At this point i tried to run the run_eval command with bazel but outputs are wrong.

I think i found a way to make the run_eval work for me.
I'm not sure if displaying all the object detected even if their score is very low is the expected behavior but final output with the precision seems correct:
Num evaluation runs: 53
Preprocessing latency: avg=7866.28(us), std_dev=0(us)
Inference latency: avg=183770(us), std_dev=3616(us)
Average Precision [IOU Threshold=0.5]: 0.916775
Average Precision [IOU Threshold=0.55]: 0.915203
Average Precision [IOU Threshold=0.6]: 0.913915
Average Precision [IOU Threshold=0.65]: 0.912595
Average Precision [IOU Threshold=0.7]: 0.906381
Average Precision [IOU Threshold=0.75]: 0.859288
Average Precision [IOU Threshold=0.8]: 0.801814
Average Precision [IOU Threshold=0.85]: 0.648213
Average Precision [IOU Threshold=0.9]: 0.298668
Average Precision [IOU Threshold=0.95]: 0.0243592
Overall mAP: 0.719721
I also tried with a resnet and a centernet but these two don't work as expected. I think the reason is because they expect the input image with different values, right?

Ok @gabrielecorsi97 !
Thanks for the update .
@sachinprasadhs !
Could you look at this issue.
Thank you!

What do you mean by results are not as expected for resnet and centernet.
Basically, all these models use the same preprocessing pipeline for the input image.
If the results are varying from one model to another, it could be due to TFLite conversion, you may have to check your conversion pipeline, please check the documentation here for more details. Thanks!


🐛Button mouse up behavior not working correctly

I have done the items below . . .

[X] I have updated the title by replacing the '<title>' section.

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
When the mouse is in the down position, and then while in the down position the mouse is moved off of the face of the button before letting go of the mouse button, the MouseUp event is not triggered.
Change the behavior of the MouseUp event by having it triggered when the mouse button is released AND the mouse is NOT over the button.
Expected Behavior
When the mouse button is released and NOT over the face of a button/control, the MouseUp event is still triggered.
Steps To Reproduce

Run the Velaptor Testing Application
Goto the Text Rendering Scene which has buttons to control attributes of the text being rendered
Click down on the CW button and hold the mouse button down.
While keep the mouse button in the down position, move the mouse off of the face of the button
Let go of the mouse button

Operating System

[X] Windows
[ ] Linux
[ ] Android
[ ] Mac OS
[ ] iOS

If you now what OS version the bug occurred on, enter the OS version here
Windows 11 - 21H2 (OS Build 22000.376)
Anything else?
No response

Reviewed with @CalvinWilkinson

After investigation into the issue, the behavior of the Button control itself is working as intended.  This is a result of how the MouseUp and MouseDown events are being utilized in the testing application scene.  Basically, this is not a bug.  😃
When the UI controls are changed for a slider control for issue #186 .
This will be implemented using issue #207


Add Documentation Website to Repo

Is there an existing issue for this?

[X] I have searched the existing issues.

Is this issue related to iced?

[X] My hardware is compatible and my graphics drivers are up-to-date.

What happened?
There should be a link to the documentation in the sidebar of the repo.
What is the expected behavior?
There should be a link to the documentation in the sidebar of the repo.
Version
master
Operative System
Windows
Do you have any log output?
No response

Done!


Add sr presets to all execusions

📋 Description
Currently, for mappy presets, we use map-ont and splice for reads longer than 500 bp, and sr, map-ont, and splice for reads shorter than that.
We are considering using sr, map-ont, and splice in all cases.
The reason for including sr is to accurately capture the mapping when reads are fragmented, such as in cases of large deletions or inversions.
Related: #31
🔍 Environment
- DAJIN2 version: 0.5.4

📎 Anything else?
No response

Planned to be supported in v0.5.6

Done. Merge at version 0.5.6 soon.


Switch from CommonJS to ESM for support for TypeDoc 0.27.x

Switch from CommonJS to ESM to support TypeDoc 0.27.x. Up until now, this plugin was distributed as CommonJS. When it tries to require("typedoc"), that fails, since CommonJS can't require ESM modules and TypeDoc is now distributed as ESM.
[error] The plugin typedoc-plugin-mdn-links could not be loaded
[error] Error [ERR_REQUIRE_ESM]: require() of ES Module /home/user/foo/node_modules/typedoc/dist/index.js from /home/user/foo/node_modules/typedoc-plugin-mdn-links/dist/index.js not supported.
Instead change the require of /home/user/foo/node_modules/typedoc/dist/index.js in /home/user/foo/node_modules/typedoc-plugin-mdn-links/dist/index.js to a dynamic import() which is available in all CommonJS modules.

I tested it against Node.JS 18, which is, as far as I can tell, the lowest version that's still supported

Shoot, I thought I'd gotten all of the CJS plugins when migrating... thanks!


[Feature] Publish available_tags event when vlans are allocated or removed

Description of the change
mef_eline manages and consumes tags when circuits are either provisioned or removed, and this resource available_tags needs to be stored and loaded when switches connect again or reboot, so I added a function to publish kytos/mef_eline.link.available_tags  for topology to subscribe, which is being delivered on this PR 46
Release notes
version [2.7.0] - 2022-01-19
Added

Added utils ``notify_link_available_tags``` function
Publish kytos/mef_eline.link.available_tags event
Hooked notify_link_available_tags when choosing or making vlans available

Thanks for reviewing, Antonio


Fix list of non proxy hosts

See https://github.com/jenkinsci/azure-vm-agents-plugin/issues/446 and https://learn.microsoft.com/en-us/java/api/com.azure.core.http.proxyoptions?view=azure-java-stable#com-azure-core-http-proxyoptions-setnonproxyhosts(java-lang-string).
List of Non Proxy hosts passed to ProxyOptions.setNonProxyHosts was not | delimited.
Testing done
I do not have an environment to test this at the moment.
### Submitter checklist
- [ ] Make sure you are opening from a **topic/feature/bugfix branch** (right side) and not your main branch!
- [ ] Ensure that the pull request title represents the desired changelog entry
- [ ] Please describe what you did
- [ ] Link to relevant issues in GitHub or Jira
- [ ] Link to relevant pull requests, esp. upstream and downstream changes
- [ ] Ensure you have provided tests - that demonstrates feature works or fixes the issue

cc @timja

Thanks!


Kafka 3270 Added some Happy Path Tests for the Reassign Partitions Command

with help from @enothereska  :)

@enothereska - updated re your suggestions. I'm afraid the conversation went with the rebase.

Thanks for improving test coverage and refactoring the code to be more testable. I left a few comments.

Thanks for the review @ijuma

LGTM, perhaps @ewencp can have a final look?

@junrao - I've removed the use of Hamcrest & rebased post rack awareness changes. Tests pass locally. Please could you merge.

Thanks for the patch. Just a minor comment above.

@junrao sorry for the delay with this. Fell of my radar. I've made the rename you suggested. Could you please merge. Thanks

I re-ran the test locally and they pass for me. The failed test in Jenkins is unrelated. LGTM.

LGTM


How do I use different certificates for different sites at the same port

example
site1: https://www.aaa.com, have CA pinning
site2: https://www.bbb.com, have CA2 pinning
they have different ca
I want proxy through a same port, and the different site flow through will use different CA, i have their CAs

You can iimplement it into your CertStorage implementation saved in the proxy.
It will receive the host, and you can generate the certificate accordingly.


Parsing plugin's response

Hi,
I'm new to grafana and react,
I would like to create a custom panel (html+js) for out client needs. So I need to parse the response from the plugin :
Suppose I have a response with the following form :

dataframes
[ "QVJST1cxAAD/////eAQAABAAAAAAAAoADgAMAAsABAAKAAAAFAAAAAAAAAEDAAoADAAAAAgABAAKAAAACAAAAIwBAAADAAAATAAAACgAAAAEAAAAFPz//wgAAAAMAAAAAQAAAEEAAAAFAAAAcmVmSWQAAAA0/P//CAAAAAwAAAAAAAAAAAAAAAQAAABuYW1lAAAAAFT8//8IAAAAJAEAABoBAAB7ImN1c3RvbSI6eyJleGVjdXRpb25TdGFydFRpbWUiOjE2MTI5Njg0ODE2NDQsImV4ZWN1dGlvbkZpbmlzaFRpbWUXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX//xYAAABtZWFzdXJlX3ZhbHVlOjp2YXJjaGFyAAAq////FAAAAEwAAABUAAAAAAADAVQAAAABAAAABAAAABj///8IAAAAIAAAABUAAABtZWFzdXJlX3ZhbHVlOjpkb3VibGUAAAAEAAAAbmFtZQAAAAAAAAAAAAAGAAgABgAGAAAAAAACABUAAABtZWFzdXJlX3ZhbHVlOjpkb3VibGUAAACu////FAAAADgAAAA4AAAAAAAFATQAAAABAAAABAAAAJz///8IAAAADAAAAAMAAAB2aW4ABAAAAG5hbWUAAAAAAAAAAJD///8DAAAAdXXXXXXXXXXXXXXXXXXXXXX=" ]

It looks like base64, but when I decode it, only a portion is displayed correctly.
How can I parse the above response?
Thank's.

Hi,
Does anyone knows the answer?
thanks.

Try https://github.com/grafana/grafana/blob/4f61edd28df8c5cfbbb2da4335b189d25a59e7d0/packages/grafana-runtime/src/utils/queryResponse.ts#L33
It is base64 encoded apache arrow files -- use the function above (note that queries is optional) and you won't need to deal with the details.
Or just use a panel plugin and you will get the parsed data directly

I'll close here and you can ask again in the grafana channel if not sufficient


readme: fix typo

Minor typo in README.md :)
Signed-off-by: hasheddan<EMAIL_ADDRESS>

Thanks for the fix @hasheddan! Lmk if you're interested in contributing (this or other samples app contributions are most welcome too), if so please let me know and I can talk to you about some of the interesting additions. Also please add yourself to the committers list: https://github.com/yugabyte/yugabyte-db/blob/master/CONTRIBUTORS.md


cellxgene-schema needs an option to remove or overwrite the labels that are applied to datasets

The data portal runs the following command in the ingestion pipeline:
cellxgene-schema validate --add-labels output.h5ad input.h5ad
This validates the dataset AND adds the human-readable labels for the ontology and gene IDs as defined in the schema. If the validation is successful, a new AnnData file (output.h5ad) is written to disk with the labels appended.
If the resulting dataset is re-processed during a schema migration, then validation will fail. There MUST be an option for cellxgene-schema to either remove or overwrite the labels that were previously applied.

There MUST be an option for cellxgene-schema to either remove or overwrite the labels that were previously applied.

This seems risky as you might overwrite information that the contributor/curator would prefer to retain (cell_type is a common example where you want to move the information to a different column). As such, during a standard (non-migration) submission, you would expect the user to submit the input.h5ad that does not have labels added.
What's the proposed migration workflow? Download existing dataset, make revisions, run validate with strip-labels option so the portal fields are removed, file is validated and written?

That makes sense.


Design and Implement the Lexer V1

Description:
Design and implement the lexer that is capable of parsing a bal file with a small function like below:
public function foo() {
    int x = 0;
}

Initial version is available at https://github.com/SupunS/BallerinaParser/tree/master