API management Original versions not working when adding new version

While testing api management (apim) versioning behavior I found out that is not true as per my testing:
https://learn.microsoft.com/en-us/azure/api-management/api-management-versions#original-versions
My scenario:
When I created non versioned API and than added new version into it, I can see the first API indeed created as Original
However this Original API is not choosen by API management as default, when handling requests without version specified (tested on query parameter versioning scheme)
When I inspect settings of the Original API (after adding new version) I can see that that version identifier is missing, which effectively disables Original API (see attached image and traces)
APIM trace of call without version specified:
{
source: "api-inspector",
timestamp: "2024-02-29T18:06:55.5743023Z",
elapsed: "00:00:00.0002754",
data: {
configuration: {
api: {
from: "/path",
to: null,
version: null,
revision: "1"
},
operation: {
method: "GET",
uriTemplate: "/enpoint"
},
user: "-",
product: "-"
}
}
},

APIM trace of call with version 2 specified:
{
source: "api-inspector",
timestamp: "2024-02-29T18:07:15.3641867Z",
elapsed: "00:00:00.0002309",
data: {
configuration: {
api: {
from: "/path",
to: null,
version: "2",
revision: "1"
},
operation: {
method: "GET",
uriTemplate: "/enpoint"
},
user: "-",
product: "-"
}
}
},

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

ID: 48402a72-7516-ebc3-725d-43d6c3450a1d
Version Independent ID: e05ef39a-cf06-9cc6-4abd-65f1a1e3a1b4
Content: Versions in Azure API Management
Content Source: articles/api-management/api-management-versions.md
Service: api-management
GitHub Login: @dlepow
Microsoft Alias: danlep

@DominikKrissVisma
Thanks for your feedback! We will investigate and update as appropriate.

DominikKrissVisma Thanks for the feedback, I see that we need to add the version identifier under settings tab to be specified for the original API.
@dlepow can we update the document there seems to be UI change done recently.

Created work item to confirm change and make appropriate doc updates in an upcoming sprint. According to our usual process, I'll now proceed to close this issue. Thanks for raising it - we appreciate the feedback!
#please-close


feat: add malavi pande as a mentor

Added my-self as a mentor
Describe the changes you have made in this PR -
Screenshots of the changes (If any) -
Note: Please check Allow edits from maintainers. if you would like us to assist in the PR.

@Malavi1 Could you resolve the conflicts ?


Cannot Change to English keyboard

After updating to indic keyboard verson 2.0 i have found an issue. When I change to english keyboard by pressing globe sign in left to the space bar, the keyboard fall back to LG built in keyboard. I have to re-enable it for using it again by going to indic keyboard app. Is there any work around ?
OS Lollipop 5.0
LG G3.

sorry. you have to select languages/layouts again from settings. otherwise, globe button won't switch layouts. This is one time thing.

also, there is an option to disable switching to other keyboard in 'Multilingual settings' under Indic Keyboard settings.

Sorry, it didnt work out. Globe button fails to switch back to English after I finished with Malayalam (Inscrypt). Second, I could not find an option in for Disable switching to other Keyboard under Indic keyboard setting. Even, there is no Multilingual settings'.

which version of android are you using?

Android 5.0
Kernel 3.4.0

For Your Information, I had tried the older version, i mean release just before 2.0. And it works as expected. I think something buggy in 2.0 for Lollipop at least for LG G3.

[Reported by KiranZ on facebook  ]
ഇൻഡിക്കിൽ ടൈപ്പ് ചെയ്തോണ്ടിരിക്കുന്ന ഞാൻ.ദാ കീബോർഡ് മാറ്റാനുള്ള ഗ്ലോബ് ബട്ടണിൽ ക്ലിക്കുന്നു
..now I have English keyboard and it also gives me no option to toggle back to Indic. ..I need to go again to the default keyboard settings and to change the default keyboard as Indic..real pain..phone model Samsung Note 4..Lollipop

@jishnu7  is it possible to disable switching to other keyboards by clicking on the globe icon?

@stultus, The usual behaviour of globe button is to switch between enabled
layouts within the selected keyboard. Long pressing the globe will open a
dialog from where you can select other keyboards. From the description
given in the report, it seems like a but more specific to the model.
On Mon, Jul 20, 2015 at 1:21 PM, Hrishi<EMAIL_ADDRESS>wrote:

@jishnu7 https://github.com/jishnu7 is it possible to disable switching
to other keyboards by clicking on the globe icon?
—
Reply to this email directly or view it on GitHub
https://github.com/smc/Indic-Keyboard/issues/41#issuecomment-122788898.

--
അനൂപ് പനവളപ്പില്

I think this is because of a non-recommended practice from Samsung keyboard.
Android documentation says

Because multiple IMEs may be installed on the device, provide a way for the user to switch to a different IME directly from the input method UI.

Any bug on our part can be ruled out by the following:

Uninstall Indic
Install any other keyboard, say Google keyboard
Switch methods using globe
See if it's possible to return from the Samsung keyboard

Issue is a bit different
As per kiranz says
ഇത് നോക്കൂ അനിവർ..ഇതാണെന്റെ‌കീബോർഡ്..ഇതിലെ ഗ്ലോബിൽ ക്ലിക്കിയാൽ ഇംഗ്ലീഷ് വരണം..

പക്ഷേ സംഭവിക്കുന്നത്..ദാ ഇതാണ്..I just pressed on the globe button and now it turns to this screen..and I don't have the globe anymore to go back to Indic..

In short glob button fails .
device Samsung Galxy Note 4 / android 5.0

Exactly, as I mentioned in my previous comment, this is something to do with how Samsung(Or any other OEM) handles the Globe key in a different IME.

temporary fix is there in latest build


Another try with most continuity proofs.

Most continuity proofs (leading to the existence of tau-minimizer) are done: the main missing sorry requires continuity of products of probability measures (API that should also be developed for Mathlib).

I hope I did this merge conflict resolution an new PR correctly --- I don't have experience on PRs from forks.


make the user disconnect when he type /q after ensuring the message was sent succesfully (Bug)

Currently, the user is not being disconnected from the chat server after typing "/q" following a successful message send. This is a bug that needs to be fixed. The expected behavior is that the user should be disconnected from the server after typing "/q" and the message is sent successfully.

Hi, I jusy want to say, that I'm working on this issue, for now I managed to find a way to make sure if the last message has been successfully sent or not, I hope soon I'll fix the /q bug !

@akai54 perfect!

So I managed to fix the bug, but I have a question, since we can only support 1 client for now, shouldn't it also close the server too when it receives /q from the client ?

well, what i've done so far is basic, now we'll allow multiple users to connect to a server and talk with other users, in the next step the server won't respond to a user, but it will just broadcast the incoming messages from one client to the whole room (the other connected clients), and i'm working on that right now


 However, some user queries include UNION ALLs with several hundred or even thousands of constants, thus generating a massive amount of fragments and pipeline drivers, which significantly impacts performance.
eg:
select 1 union all select 10 + 'a' union all select 3

mysql> explain logical select 1 union all select 10 + 'a' union all select 3;
+-----------------------------------------------------------------------------------------+
| Explain String                                                                          |
+-----------------------------------------------------------------------------------------+
| - Output => [9:cast]                                                                    |
|     - UNION => [9: cast]                                                                |
|             Estimates: {row: 3, cpu: ?, memory: ?, network: ?, cost: 0.0}               |
|         - VALUES => [3:cast]                                                            |
|                 Estimates: {row: 1, cpu: 0.00, memory: 0.00, network: 0.00, cost: 0.00} |
|                 3:cast := 1.0                                                           |
|         - VALUES => [5:expr]                                                            |
|                 Estimates: {row: 1, cpu: ?, memory: ?, network: ?, cost: 0.0}           |
|                 5:expr := 10.0 + cast('a' as double)                                    |
|         - VALUES => [8:cast]                                                            |
|                 Estimates: {row: 1, cpu: 0.00, memory: 0.00, network: 0.00, cost: 0.00} |
|                 8:cast := 3.0                                                           |
+-----------------------------------------------------------------------------------------+
12 rows in set (0.01 sec)

manually changing it to use values greatly reduces the number of fragments:
mysql> explain logical select * from (values (1), (10 + 'a'), (3));
+---------------------------------------------------------------------------+
| Explain String                                                            |
+---------------------------------------------------------------------------+
| - Output => [1:column_0]                                                  |
|     - VALUES => {1.0}, {10.0 + cast('a' as double)}, {3.0}                |
|             Estimates: {row: 3, cpu: ?, memory: ?, network: ?, cost: 0.0} |
+---------------------------------------------------------------------------+
3 rows in set (0.04 sec)

What I'm doing:
For this scenario, add an optimization rule to transform all constant UNION ALLs into a single Values operator to avoid generating a massive number of fragments.
mysql> explain logical select 1 union all select 10 + 'a' union all select 3;
+---------------------------------------------------------------------------+
| Explain String                                                            |
+---------------------------------------------------------------------------+
| - Output => [9:cast]                                                      |
|     - VALUES => {1.0}, {10.0 + cast('a' as double)}, {3.0}                |
|             Estimates: {row: 3, cpu: ?, memory: ?, network: ?, cost: 0.0} |
+---------------------------------------------------------------------------+
3 rows in set (0.02 sec)

What type of PR is this:

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)
[ ] I have added documentation for my new feature or new function
[ ] This is a backport pr

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.2
[ ] 3.1
[ ] 3.0
[ ] 2.5

@Mergify backport branch-3.2


Fix stable branch pattern regular expressions

Changelog: (Fix): Fix regex patterns and move initialization to init() method
The first commit fixes the patterns by adding a . between the last character and the *.
The second commit moves the initialization of the stable_branch_pattern variable to the class' init method to reduce the code size and always assure an initialized value right from the start when the Packager is created. This change would also allow the use of multiple stable branch patterns when using the environment variable CONAN_STABLE_BRANCH_PATTERN.
All changes are backwards compatible.
Issue #557

[X] Refer to the issue that supports this Pull Request.
[X] If the issue has missing info, explain the purpose/use case/pain/need that covers this Pull Request.
[X] I've read the Contributing guide.
[X] I've followed the PEP8 style guides for Python code.

It took a little longer than expected to add the tests.
All tests were passing locally on Ubuntu 18.04 / Python 3.6.
No idea why AppVeyor is failing, I thought it had been removed?

Is this an issue with how pull requests are configured in this project? I have multiple PRs that are already using GitHub actions in my fork. They are all failing in this repo because of the AppVeyor error.

Weird error from Appveyor. Indeed we could move to Github Actions, or even to our internal Jenkins.


Migrate to clap 4.x (WIP)

This PR migrates to clap 4.3. This in particular requires/benefits from some changes to/on how some errors work, including depending on thiserror; I believe those are good changes overall.
I plan on doing the following in this PR:

[x] migrate to clap 4.x
[x] migrating errors to use thiserror
[x] some glitter (use of Self and of format! only)
[x] removing tests that check some CLI validation errors; ~they currently reflect the state of the PR though, so you can see how CLI error messages differ~ those changes have been isolated in the last commit

Please let me know what you think @noeddl, in particular on the last point.

Thanks a lot for the PR @schneiderfelipe! It looks good to me on first glance but I will take a closer look later when I have some more time, especially on the failing checks. I will probably have to update the minimum supported Rust version to allow for clap 4.
As for testing CLI validation errors: Did clap 4 improve anything in this regard or would you consider these tests superfluous no matter which clap version?

Thanks a lot for the PR @schneiderfelipe! It looks good to me on first glance but I will take a closer look later when I have some more time, especially on the failing checks.

Some of the checks are failing due to -D warnings. In fact, some of those fail on unmodified code, maybe due to new clippy warnings having been added in the last couple years? I have some changes on my side addressing those (and other) clippy warnings, but I believe that would be outside the scope of this PR (I'm happy to contribute some of those soon 🤗)?

I will probably have to update the minimum supported Rust version to allow for clap 4.

I think the MSRV for clap 4.3 (what this PR is asking for) is 1.64.0. For comparison, clap 4.0 seems to ask for 1.60.0, so that's the interval we could choose from? cargo msrv gave me 1.64.0 if I remember correctly.

As for testing CLI validation errors: Did clap 4 improve anything in this regard or would you consider these tests superfluous no matter which clap version?

That's because some of those validations used to happen here, but since they are being proposed to happen on clap side (e.g. see here), I suggest these tests could be removed.

I suggest that we first update the MSRV to 1.64.0 and make sure all the checks are passing (i.e. by addressing the clippy warnings) in a separate PR. Then we can rebase this PR on the new master after the other one has been merged. What do you think? If you want to you could do that using the changes that you already have in place regarding the clippy warnings.

That's because some of those validations used to happen here, but since they are being proposed to happen on clap side (e.g. see here), I suggest these tests could be removed.

I see, thanks for the clarification.

Good call, I can do that just fine. In the meanwhile, can I ask you to rerun the CI workflow on the master branch, so that we can have a baseline?

Hi @schneiderfelipe, are you still interested in doing the preparations that we discussed above (updating the MSRV and taking care of the clippy warnings)? Otherwise I would like to do them myself so that I can merge this PR and allow for any further development.

Hi Anett, my time got short lately. Feel free to do it if you want. I'll
probably catch pace at a later time! Cheers!
Em ter, 7 de mai de 2024 06:53, Anett Seeker @.***>
escreveu:

Hi @schneiderfelipe https://github.com/schneiderfelipe, are you still
interested in doing the preparations that we discussed above (updating the
MSRV and taking care of the clippy warnings)? Otherwise I would like to do
them myself so that I can merge this PR and allow for any further
development.
—
Reply to this email directly, view it on GitHub
https://github.com/noeddl/ukebox/pull/123#issuecomment-2097906426, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAJCBP33GTEBHIFD4LJ2GLZBCQB5AVCNFSM6AAAAABFPSZTEWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJXHEYDMNBSGY
.
You are receiving this because you were mentioned.Message ID:
@.***>

@schneiderfelipe Thanks again for the PR and thanks for bringing back some life to this project. 🙂


It's helpful to add info / how to do purge for AFD

According to Cache page for Azure Front Door, there is information about purge. However there is no information how to do Purge.
https://docs.microsoft.com/en-us/azure/frontdoor/front-door-caching#cache-purge
As my confirmation, There is no UI to purge of AFD on Azure Portal. But PowerShell Command is acceptable for Purge of AFD.  So that please add below link which can customer follow how to purge for AFD.
https://docs.microsoft.com/ja-jp/powershell/module/az.frontdoor/remove-azfrontdoorcontent?view=azps-2.8.0&viewFallbackFrom=azps-2.6.0

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

ID: 2973ab88-1258-8a80-1344-07a9e0063951
Version Independent ID: c0cff4d9-d7fd-7b25-52da-9cbe5dda3ba8
Content: Azure Front Door Service - caching
Content Source: articles/frontdoor/front-door-caching.md
Service: frontdoor
GitHub Login: @sharad4u
Microsoft Alias: sharadag

@taminta Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

#reassign: amitsriva

Let’s me correct info again then raise issue as needed


[hub] Convert all variables to snakeCase

There are camel_case variables that are leftovers from an older repository.

Example:

Once this is fixed the ESLint rule camelcase should be set to error


docs(hub) fix up optum response-size-limiting plugin

Summary
Set api_id: false to disable documentation around setting response size limiting to API resources as plugin does not support the deprecated resource.
Thx @coopr for the insight in our discussions over here:
https://github.com/Kong/docs.konghq.com/pull/900

Thank you @jeremyjpj0916 !


Class hash of deployed contract different from class hash of compiled one

Describe the bug
I get class hash A from compiled contract Contract using starknet hardhat plugin but when declaring with starknet.js account, the declare transaction returns class hash B for the same contract. Therefore the declare transaction fails because signing payload is not the expected one (because expected class hash B is different from input class hash A).
To Reproduce

Example Contract.cairo contract used:

// Declare this file as a StarkNet contract.
%lang starknet

from starkware.cairo.common.cairo_builtins import HashBuiltin

// Define a storage variable.
@storage_var
func balance() -> (res: felt) {
}

// Increases the balance by the given amount.
@external
func increase_balance{
    syscall_ptr: felt*,
    pedersen_ptr: HashBuiltin*,
    range_check_ptr,
}(amount: felt) {
    let (res) = balance.read();
    balance.write(res + amount);
    return ();
}

// Returns the current balance.
@view
func get_balance{
    syscall_ptr: felt*,
    pedersen_ptr: HashBuiltin*,
    range_check_ptr,
}() -> (res: felt) {
    let (res) = balance.read();
    return (res=res);
}

Compile the contract and read the contract artifact using starknet hardhat plugin:

import { starknet, starknetWrapper } from "hardhat"
import { Account } from "starknet"

const contractFactory = await starknet.getContractFactory("Contract")
const compiledContract = require(contractFactory.metadataPath)
const classHash = await starknetWrapper.getClassHash(contractFactory.metadataPath)
console.log(classHash) // 0x37a54ffa21547ffaef9b75dc2a65d4c0e1f23f3dc2f523fb95df578e12a4293

const account = new Account(provider, ...)
const { transaction_hash, class_hash } = await account.declare({classHash, , contract: compiledContract})
console.log(class_hash) // 0x7c69ad1a294c331b4f99320d992af0f223c93853adce500ea9977668c47075e

await provider.waitForTransaction(transaction_hash) // Error: REJECTED: TRANSACTION_FAILED
// Signature (...) , is invalid, with respect to the public key ..., and the message hash ...

The returned class hash from account.declare(...) is different from the one derived by starknetWrapper.getClassHash(...).
If it is declared by a starknet hardhat plugin account, it will succeed and return the same class hash as starknetWrapper.getClassHash(...):
const defaultAccount = (await starknet.devnet.getPredeployedAccounts())[0]

const class_hash = await defaultAccount.declare(contractFactory)
console.log(class_hash) // 0x37a54ffa21547ffaef9b75dc2a65d4c0e1f23f3dc2f523fb95df578e12a4293

I'm not sure if this is the expected behavior but there should only be one class hash for a given contract?
Expected behavior
The class hash returned from (starknet.js) account.declare() should be the same as (starknet hardhat plugins) account.declare() or starknetWrapper.getClassHash().
Desktop (please complete the following information):

Node version: v16.17.0
StarkNet.js version: 4.17.1
Network: devnet 0.4.3

Since I get the class hash for comparison using starknet hardhat plugin, it could be that the class hash computed by starknet hardhat plugin is wrong. If this could be the case, I will also open an issue there.

Since starknet hardhat plugin also proxy the get_class_hash call to sequencer (devnet), does this mean that the sequencer is computing different class hash for calls from starknet.js and starknet hardhat plugin?

If class hash for starknet.js account declare is fixed and let the declare transaction succeed, meaning declare a different class hash for the same transaction.
import { Account } from "starknet"

// declare using starknet.js account
const account = new Account(provider, ...)

// Fix the class hash so the declare transaction will succeed
const { transaction_hash, class_hash } = await account.declare({classHash: "0x7c69ad1a294c331b4f99320d992af0f223c93853adce500ea9977668c47075e", , contract: compiledContract})

await provider.waitForTransaction(transaction_hash) // transaction succeed

But then deploy the contract using starknet hardhat plugin, will should fail because it is expecting a different class hash to be declared:
const defaultAccount = (await starknet.devnet.getPredeployedAccounts())[0]

const contract = await defaultAccount.deploy(contractFactory)
// This deploy transaction will succeed!

However the deploy transaction succeed, meaning that the actual declared class hash is the one computed by starknet hardhat plugin (0x37a54ffa21547ffaef9b75dc2a65d4c0e1f23f3dc2f523fb95df578e12a4293)?

OK I think I found why... you can not simply use require(PATH_TO_COMPILED_CAIRO_CONTRACT_JSON_FILE), you have to import json from starknet and use it to parse the compiled cairo contract json files...
import { starknet, starknetWrapper } from "hardhat"
import { Account, json } from "starknet"

const contractFactory = await starknet.getContractFactory("Contract")
const compiledContract = require(contractFactory.metadataPath) // ❌ This don't work
const compiledContract = json.parse(fs.readFileSync(contractFactory.metadataPath).toString('ascii')) // ✅ You have to do this
const classHash = await starknetWrapper.getClassHash(contractFactory.metadataPath)
console.log(classHash) // 0x37a54ffa21547ffaef9b75dc2a65d4c0e1f23f3dc2f523fb95df578e12a4293

const account = new Account(provider, ...)
const { transaction_hash, class_hash } = await account.declare({classHash, , contract: compiledContract})
console.log(class_hash) // 0x37a54ffa21547ffaef9b75dc2a65d4c0e1f23f3dc2f523fb95df578e12a4293

await provider.waitForTransaction(transaction_hash) // Transaction succeed

This is not intuitive in my opinion... that I have to parse a (compiled cairo contract) json file in specific way. Is it possible to pass in PATH_TO_COMPILED_CAIRO_CONTRACT_JSON_FILE instead of a parsed json object (just like starknet hardhat plugin)?

@NIC619 thanks, we will clarify in the docs the current situation at least

Added about  json.parse in docs in couple of places


.NET Standard Support

Can you please support .NET Standard and release new packages? Thanks.

Done in 2.1+, via #225


Fix missing period in CanvasItem.draw_primitive() description

Leftover from https://github.com/godotengine/godot/pull/55517.
The change from this PR is already included in https://github.com/godotengine/godot/pull/55518.

Thanks :P


[logicApp] Get error when run az logic workflow list

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
Unknown Extension Name: logic. Version: 0.1.4.
Errors:
The command failed with an unexpected error. Here is the traceback:
Unable to deserialize to object: type, KeyError: 'FlowAccessControlConfiguration'
Traceback (most recent call last):
  File "/usr/local/Cellar/azure-cli/2.25.0/libexec/lib/python3.8/site-packages/msrest/serialization.py", line 1442, in _deserialize
    value = self.deserialize_data(raw_value, attr_desc['type'])
  File "/usr/local/Cellar/azure-cli/2.25.0/libexec/lib/python3.8/site-packages/msrest/serialization.py", line 1620, in deserialize_data
    obj_type = self.dependencies[data_type]
KeyError: 'FlowAccessControlConfiguration'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Users/bill/.azure/cliextensions/interactive/azext_interactive/azclishell/app.py", line 663, in cli_execute
    result = invocation.execute(args)
  File "/usr/local/Cellar/azure-cli/2.25.0/libexec/lib/python3.8/site-packages/azure/cli/core/commands/__init__.py", line 657, in execute
    raise ex
  File "/usr/local/Cellar/azure-cli/2.25.0/libexec/lib/python3.8/site-packages/azure/cli/core/commands/__init__.py", line 720, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
  File "/usr/local/Cellar/azure-cli/2.25.0/libexec/lib/python3.8/site-packages/azure/cli/core/commands/__init__.py", line 704, in _run_job
    result = list(result)
  File "/usr/local/Cellar/azure-cli/2.25.0/libexec/lib/python3.8/site-packages/azure/core/paging.py", line 129, in __next__
    return next(self._page_iterator)
  File "/usr/local/Cellar/azure-cli/2.25.0/libexec/lib/python3.8/site-packages/azure/core/paging.py", line 84, in __next__
    self.continuation_token, self._current_page = self._extract_data(self._response)
  File "/Users/bill/.azure/cliextensions/logic/azext_logic/vendored_sdks/logic/operations/_workflow_operations.py", line 96, in extract_data
    deserialized = self._deserialize('WorkflowListResult', pipeline_response)
  File "/usr/local/Cellar/azure-cli/2.25.0/libexec/lib/python3.8/site-packages/msrest/serialization.py", line 1368, in __call__
    return self._deserialize(target_obj, data)
  File "/usr/local/Cellar/azure-cli/2.25.0/libexec/lib/python3.8/site-packages/msrest/serialization.py", line 1442, in _deserialize
    value = self.deserialize_data(raw_value, attr_desc['type'])
  File "/usr/local/Cellar/azure-cli/2.25.0/libexec/lib/python3.8/site-packages/msrest/serialization.py", line 1618, in deserialize_data
    return self.deserialize_type[iter_type](data, data_type[1:-1])
  File "/usr/local/Cellar/azure-cli/2.25.0/libexec/lib/python3.8/site-packages/msrest/serialization.py", line 1649, in deserialize_iter
    return [self.deserialize_data(a, iter_type) for a in attr]
  File "/usr/local/Cellar/azure-cli/2.25.0/libexec/lib/python3.8/site-packages/msrest/serialization.py", line 1649, in <listcomp>
    return [self.deserialize_data(a, iter_type) for a in attr]
  File "/usr/local/Cellar/azure-cli/2.25.0/libexec/lib/python3.8/site-packages/msrest/serialization.py", line 1631, in deserialize_data
    return self._deserialize(obj_type, data)
  File "/usr/local/Cellar/azure-cli/2.25.0/libexec/lib/python3.8/site-packages/msrest/serialization.py", line 1446, in _deserialize
    raise_with_traceback(DeserializationError, msg, err)
  File "/usr/local/Cellar/azure-cli/2.25.0/libexec/lib/python3.8/site-packages/msrest/exceptions.py", line 51, in raise_with_traceback
    raise error.with_traceback(exc_traceback)
  File "/usr/local/Cellar/azure-cli/2.25.0/libexec/lib/python3.8/site-packages/msrest/serialization.py", line 1442, in _deserialize
    value = self.deserialize_data(raw_value, attr_desc['type'])
  File "/usr/local/Cellar/azure-cli/2.25.0/libexec/lib/python3.8/site-packages/msrest/serialization.py", line 1620, in deserialize_data
    obj_type = self.dependencies[data_type]
msrest.exceptions.DeserializationError: Unable to deserialize to object: type, KeyError: 'FlowAccessControlConfiguration'

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az logic workflow list

Expected Behavior
Environment Summary
macOS-11.4-x86_64-i386-64bit
Python 3.8.10
Installer: HOMEBREW

azure-cli 2.25.0 *

Extensions:
logic 0.1.4
azure-devops 0.18.0
interactive 0.4.5
blueprint 0.3.0

Additional Context

I am the owner of that subscription. Should be not permission issue.

route to service team

thanks @yonzhan
I also run a test with same command on a virtualbox Ubuntu 20.04, got same error.

looks fine to me now. thanks


Custom dataset regression task + inference on cpu

Thanks a lot for your great work!
As stated, I am working on a custom dataset trying to predict angles and translations of planes intersecting input pointclouds, thus it's essentially a regression task of a rotation and a translation matrix.
Currently I am have reconfigured the modelnet40ply2048/pointnext-s.yaml classification head to perform regression instead, which works alright.
However, I am curious if I can perhaps gain more from using feature propagation as well, or if there are better ways of doing regression tasks with PointNeXt?
Also, would like to inference the model on CPU - so wondering if it would be straight forward to substitute the cpp code with perhaps PointNet++ equivalent code (fps/ball query etc.) to be able to run on CPU?
Kindly,
Mikkel

if it is node-level regression, you might need feature propagation, otherwise, it should be standard just replacing classification head to regression head using the classification architecture.
For the CPU application, we do not have a plan for it. You have to do you own research.


Missing Error message when azcopy rm failed

Which version of the AzCopy was used?
Note: The version is visible when running AzCopy without any argument
10.16.2
Which platform are you using? (ex: Windows, Mac, Linux)
Windows
What command did you run?
Note: Please remove the SAS to avoid exposing your credentials. If you cannot remember the exact command, please retrieve it from the beginning of the log file.
azcopy rm
What problem was encountered?
azcopy failed when trying to remove a blob i.e. leased, TransfersFailed: 1. But error message was not populated.

How can we reproduce the problem in the simplest way?
Try deleting a leased blob[Azure storage container] using azcopy rm.
Have you found a mitigation/solution?
No

Hi @veedi ! I am able to successfully delete a leased blob with AzCopy. Could you please rerun with --log-level=DEBUG and share the results with us?

Hi again @siminsavani-msft ,
We do not know the leaseid for the blob and there could be 'n' number of files to remove that may be leased, it's ok if the azcopy fail.
We expect error message to be populated why the azcopy rm command failed. we could see the error message in log file but not in the error message property in the command output logs.
Please see attached log file generated in azcopy logs folder.
RESPONSE Status: 412 There is currently a lease on the blob and no lease ID was specified in the request.
leasejob.log
Command log output when executing azcopy rm command,
ErrorMsg                :
JobID                   : 85fa3c45-9004-cc4c-4124-16f8c3aa7ab2
ActiveConnections       : 0
CompleteJobOrdered      : True
JobStatus               : Failed
TotalTransfers          : 1
FileTransfers           : 1
FolderPropertyTransfers : 0
TransfersCompleted      : 0
TransfersFailed         : 1
TransfersSkipped        : 0
BytesOverWire           : 0
TotalBytesTransferred   : 0
TotalBytesEnumerated    : 20
TotalBytesExpected      : 0
PercentComplete         : 100
AverageIOPS             : 0
AverageE2EMilliseconds  : 0
ServerBusyPercentage    : 0
NetworkErrorPercentage  : 0
FailedTransfers         : {@{Src=https://stousedmdmzdv.blob.core.windows.net/rbac-product-p00000046-pc00000282/sample2.t
xt; Dst=; IsFolderProperties=False; TransferStatus=Failed; TransferSize=0; ErrorCode=0}}
SkippedTransfers        :
PerfConstraint          : 0
PerformanceAdvice       : {}
IsCleanupJob            : False

@veedi Thank you for sharing the logs! The command output is intended to be minimized for perf/UX reasons and errors won't populate in the command output.
When you run AzCopy on many files, the TransfersFailed and TransfersCompleted will be updated to match the number of files that have failed or completed, respectively. The best way to get why AzCopy failed is running --log-level=DEBUG (which I noticed from the log files that you already did).


WIP - adding community_profiles acs calculation notebook

#43 is still pending ....
NYCPlanning/db-community-profiles/issues/43

import reduce from functools

dfs = []
for i in variable_mapping:
    df.append(calculate(i))
dff = reduce(lambda  left,right: pd.merge(left,right, on=['census_geoid'],
                                            how='outer'), dfs)

Full implementation here: https://github.com/NYCPlanning/db-factfinder/tree/comm-prof-pipeline/pipelines/community_profiles
These will live in the community profiles repo, though.


Transfert pokemon only when we don't have free slots

Short Description:
Normally, we don't transfert pokemon after each catch, a more human-like behavior is to transfert pokemon only when we don't have enough slot.
This PR adds this features.

@Segflow please update https://github.com/PokemonGoF/PokemonGo-Bot/blob/dev/docs/configuration_files.md as well

@k4n30 done.


bugfix: set check and report operations on mixer sidecars

Redo of #5283

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: vadimeisenbergibm
Assign the PR to them by writing /assign @vadimeisenbergibm in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kyessenov: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
4a08e3bf95cc6cf1309dad9377a818be1cbcee75
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: douglas-reid
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS [douglas-reid]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kyessenov: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
4a08e3bf95cc6cf1309dad9377a818be1cbcee75
link
/test istio-unit-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
4a08e3bf95cc6cf1309dad9377a818be1cbcee75
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kyessenov: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
4a08e3bf95cc6cf1309dad9377a818be1cbcee75
link
/test istio-unit-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
4a08e3bf95cc6cf1309dad9377a818be1cbcee75
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
4a08e3bf95cc6cf1309dad9377a818be1cbcee75
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kyessenov: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
4a08e3bf95cc6cf1309dad9377a818be1cbcee75
link
/test istio-unit-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
4a08e3bf95cc6cf1309dad9377a818be1cbcee75
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
4a08e3bf95cc6cf1309dad9377a818be1cbcee75
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
4a08e3bf95cc6cf1309dad9377a818be1cbcee75
link
/test e2e-bookInfo

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@kyessenov: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
4a08e3bf95cc6cf1309dad9377a818be1cbcee75
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-bookInfoTests.sh
4a08e3bf95cc6cf1309dad9377a818be1cbcee75
link
/test e2e-bookInfo

prow/istio-pilot-e2e.sh
4a08e3bf95cc6cf1309dad9377a818be1cbcee75
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kyessenov: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests.sh
4a08e3bf95cc6cf1309dad9377a818be1cbcee75
link
/test e2e-bookInfo

prow/istio-pilot-e2e.sh
4a08e3bf95cc6cf1309dad9377a818be1cbcee75
link
/test istio-pilot-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
4a08e3bf95cc6cf1309dad9377a818be1cbcee75
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kyessenov: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
4a08e3bf95cc6cf1309dad9377a818be1cbcee75
link
/test istio-pilot-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
4a08e3bf95cc6cf1309dad9377a818be1cbcee75
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-bookInfoTests-v1alpha3.sh
4a08e3bf95cc6cf1309dad9377a818be1cbcee75
link
/test e2e-bookInfo-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kyessenov: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
4a08e3bf95cc6cf1309dad9377a818be1cbcee75
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-bookInfoTests-v1alpha3.sh
4a08e3bf95cc6cf1309dad9377a818be1cbcee75
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
4a08e3bf95cc6cf1309dad9377a818be1cbcee75
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kyessenov: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
4a08e3bf95cc6cf1309dad9377a818be1cbcee75
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
4a08e3bf95cc6cf1309dad9377a818be1cbcee75
link
/test istio-pilot-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
4a08e3bf95cc6cf1309dad9377a818be1cbcee75
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kyessenov: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
4a08e3bf95cc6cf1309dad9377a818be1cbcee75
link
/test istio-pilot-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
4a08e3bf95cc6cf1309dad9377a818be1cbcee75
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-bookInfoTests-v1alpha3.sh
4a08e3bf95cc6cf1309dad9377a818be1cbcee75
link
/test e2e-bookInfo-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kyessenov: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
4a08e3bf95cc6cf1309dad9377a818be1cbcee75
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-bookInfoTests-v1alpha3.sh
4a08e3bf95cc6cf1309dad9377a818be1cbcee75
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
4a08e3bf95cc6cf1309dad9377a818be1cbcee75
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kyessenov: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
4a08e3bf95cc6cf1309dad9377a818be1cbcee75
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
4a08e3bf95cc6cf1309dad9377a818be1cbcee75
link
/test istio-pilot-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
4a08e3bf95cc6cf1309dad9377a818be1cbcee75
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kyessenov: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
4a08e3bf95cc6cf1309dad9377a818be1cbcee75
link
/test istio-pilot-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
4a08e3bf95cc6cf1309dad9377a818be1cbcee75
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-bookInfoTests-v1alpha3.sh
4a08e3bf95cc6cf1309dad9377a818be1cbcee75
link
/test e2e-bookInfo-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


make[1]: Nothing to be done for 'modules'.

Question
Unable to compile dynamic modules. While make modules, it shows:
root@eriri:/home/sufe/tengine# make modules
make -f objs/Makefile modules
make[1]: Entering directory '/home/sufe/tengine'
make[1]: Nothing to be done for 'modules'.
make[1]: Leaving directory '/home/sufe/tengine'

Tengine version: Tengine/2.3.1
nginx version: nginx/1.16.0
And here's all the logs, the module 'ngx_http_substitutions_filter_module' worked fine in tengine 2.2.2 with dso command.
root@eriri:/home/sufe/tengine# ./configure --prefix=/etc/nginx/ \
>             --with-stream \
>             --with-http_geoip_module \
>             --sbin-path=/usr/sbin/nginx \
>             --conf-path=/etc/nginx/nginx.conf \
>             --http-log-path=/var/log/nginx/access.log \
>             --error-log-path=/var/log/nginx/error.log \
>             --add-dynamic-module=/home/sufe/modules/ngx_http_substitutions_filter_module
checking for OS
 + Linux 4.15.0-55-generic x86_64
checking for C compiler ... found
 + using GNU C compiler
 + gcc version: 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
checking for gcc -pipe switch ... found
checking for -Wl,-E switch ... found
checking for gcc builtin atomic operations ... found
checking for C99 variadic macros ... found
checking for gcc variadic macros ... found
checking for gcc builtin 64 bit byteswap ... found
checking for unistd.h ... found
checking for inttypes.h ... found
checking for limits.h ... found
checking for sys/filio.h ... not found
checking for sys/param.h ... found
checking for sys/mount.h ... found
checking for sys/statvfs.h ... found
checking for crypt.h ... found
checking for Linux specific features
checking for epoll ... found
checking for EPOLLRDHUP ... found
checking for EPOLLEXCLUSIVE ... found
checking for O_PATH ... found
checking for sendfile() ... found
checking for sendfile64() ... found
checking for sys/prctl.h ... found
checking for prctl(PR_SET_DUMPABLE) ... found
checking for prctl(PR_SET_KEEPCAPS) ... found
checking for capabilities ... found
checking for crypt_r() ... found
checking for sys/vfs.h ... found
checking for nobody group ... not found
checking for nogroup group ... found
checking for poll() ... found
checking for /dev/poll ... not found
checking for kqueue ... not found
checking for crypt() ... not found
checking for crypt() in libcrypt ... found
checking for F_READAHEAD ... not found
checking for posix_fadvise() ... found
checking for O_DIRECT ... found
checking for F_NOCACHE ... not found
checking for directio() ... not found
checking for statfs() ... found
checking for statvfs() ... found
checking for dlopen() ... not found
checking for dlopen() in libdl ... found
checking for sched_yield() ... found
checking for sched_setaffinity() ... found
checking for SO_SETFIB ... not found
checking for SO_REUSEPORT ... found
checking for SO_ACCEPTFILTER ... not found
checking for SO_BINDANY ... not found
checking for IP_TRANSPARENT ... found
checking for IP_BINDANY ... not found
checking for IP_BIND_ADDRESS_NO_PORT ... found
checking for IP_RECVDSTADDR ... not found
checking for IP_SENDSRCADDR ... not found
checking for IP_PKTINFO ... found
checking for IPV6_RECVPKTINFO ... found
checking for TCP_DEFER_ACCEPT ... found
checking for TCP_KEEPIDLE ... found
checking for TCP_FASTOPEN ... found
checking for TCP_INFO ... found
checking for accept4() ... found
checking for eventfd() ... found
checking for int size ... 4 bytes
checking for long size ... 8 bytes
checking for long long size ... 8 bytes
checking for void * size ... 8 bytes
checking for uint32_t ... found
checking for uint64_t ... found
checking for sig_atomic_t ... found
checking for sig_atomic_t size ... 4 bytes
checking for socklen_t ... found
checking for in_addr_t ... found
checking for in_port_t ... found
checking for rlim_t ... found
checking for uintptr_t ... uintptr_t found
checking for system byte ordering ... little endian
checking for size_t size ... 8 bytes
checking for off_t size ... 8 bytes
checking for time_t size ... 8 bytes
checking for AF_INET6 ... found
checking for setproctitle() ... not found
checking for pread() ... found
checking for pwrite() ... found
checking for pwritev() ... found
checking for sys_nerr ... found
checking for localtime_r() ... found
checking for clock_gettime(CLOCK_MONOTONIC) ... found
checking for posix_memalign() ... found
checking for memalign() ... found
checking for mmap(MAP_ANON|MAP_SHARED) ... found
checking for mmap("/dev/zero", MAP_SHARED) ... found
checking for System V shared memory ... found
checking for POSIX semaphores ... not found
checking for POSIX semaphores in libpthread ... found
checking for struct msghdr.msg_control ... found
checking for ioctl(FIONBIO) ... found
checking for struct tm.tm_gmtoff ... found
checking for struct dirent.d_namlen ... not found
checking for struct dirent.d_type ... found
checking for sysconf(_SC_NPROCESSORS_ONLN) ... found
checking for sysconf(_SC_LEVEL1_DCACHE_LINESIZE) ... found
checking for openat(), fstatat() ... found
checking for getaddrinfo() ... found
checking for sysinfo() ... found
checking for getloadavg() ... found
checking for /proc/meminfo ... found
checking for /proc/stat ... found
configuring additional dynamic modules
adding module in /home/sufe/modules/ngx_http_substitutions_filter_module
 + ngx_http_subs_filter_module was configured
checking for PCRE library ... found
checking for PCRE JIT support ... found
checking for OpenSSL library ... found
checking for zlib library ... found
checking for GeoIP library ... found
checking for GeoIP IPv6 support ... found
creating objs/Makefile

Configuration summary
  + using system PCRE library
  + using system OpenSSL library
  + using system zlib library
  + jemalloc library is disabled

  nginx path prefix: "/etc/nginx/"
  nginx binary file: "/usr/sbin/nginx"
  nginx modules path: "/etc/nginx//modules"
  nginx configuration prefix: "/etc/nginx"
  nginx configuration file: "/etc/nginx/nginx.conf"
  nginx pid file: "/etc/nginx//logs/nginx.pid"
  nginx error log file: "/var/log/nginx/error.log"
  nginx http access log file: "/var/log/nginx/access.log"
  nginx http client request body temporary files: "client_body_temp"
  nginx http proxy temporary files: "proxy_temp"
  nginx http fastcgi temporary files: "fastcgi_temp"
  nginx http uwsgi temporary files: "uwsgi_temp"
  nginx http scgi temporary files: "scgi_temp"

root@eriri:/home/sufe/tengine# make modules
make -f objs/Makefile modules
make[1]: Entering directory '/home/sufe/tengine'
make[1]: Nothing to be done for 'modules'.
make[1]: Leaving directory '/home/sufe/tengine'

Do you use this module https://github.com/yaoweibin/ngx_http_substitutions_filter_module?
This module does not support dynamic loading, its config file is not modified for dynamic module loading.

I tried to compile the  ngx_http_substitutions_filter_module with --add-module, it was OK. And I tried to compile the other modules with --add-dynamic-module they were OK. Only when I compile the ngx_http_substitutions_filter_module with --add-dynamic-module, there was any ngx_http_substitutions_filter_module.so file in ./objs/.
I guess maybe the module ngx_http_substitutions_filter_module itself cannot being dynamically compiled, but what I interested is why the old dso_tool (Tengine 2.2.2) cloud compile this module but the Nginx cloud not? (Maybe the old Tengine dso tool is stronger?😂)
The module ngx_http_substitutions_filter_module is here: https://github.com/yaoweibin/ngx_http_substitutions_filter_module

@chobits Yes, I'm using this module. But what I am interested is why the old dso_tool (Tengine 2.2.2) could compile this module but the Nginx could not? (Does it mean the old Tengine dso tool is stronger?😂)

原来给 config 加个 . auto/module 就可以了，感谢大大指点😂

@chobits Yes, I'm using this module. But what I am interested is why the old dso_tool (Tengine 2.2.2) could compile this module but the new Nginx could not? (Does it mean the old Tengine dso tool is stronger?😂)

Old dso_tool tries to be compatible with nginx configuration system, current nginx has updated configuration system for new dynamic module loading

原来给 config 加个 . auto/module 就可以了，感谢大大指点😂

How to do this?


Can the bot listen in-game chat?

Hello, I want my bot to interact with the players in the game server, so I've tried to put him in channel.
Dota2.joinChat("Game_" + LobbyID, 11);
At the moment the bot can listen the lobby states, but he can't listen the in-game chat.

Pretty sure that is not a thing. Bots don't join the game, and even if they did... they would only see all-chat.

That's because you are joining the wrong channel, check the readme, it contains several important channels. You are looking for 'Lobby_' +lobby_id
On 6 Jan 2016 1:37 pm, Tom<EMAIL_ADDRESS>wrote:
Hello, I want my bot to interact with the players in the game server, so I've tried to put him in channel
Dota2joinChat("Game_" + LobbyID, 11);
At the moment the bot can listen the lobby states, but he can't listen the in-game chat
—
Reply to this email directly or view it on GitHub.

@Crazy-Duck I put him in the Lobby chat channel, but I can't put him to the in-game chat channel. There is no way to do this with NodeJS?

There probably is, just need to find the right format. I haven't tried joining in game chat myself, I thought lobby chat was the same as in game allchat. Just nethook yourself starting a lobby, you should see a joinchatchannel message being sent to the GC. If you find out, add the format to the Readme ☺
On 6 Jan 2016 1:41 pm, Tom<EMAIL_ADDRESS>wrote:
@Crazy-Duck I put him in the Lobby chat channel, but I can't put him to the in-game chat channel. There is no way to do this with NodeJS?
—
Reply to this email directly or view it on GitHub.

Here is when I last mentioned nethook. Use a dummy account that is not limited.
https://github.com/RJacksonm1/node-dota2/issues/141#issuecomment-153559554

6 Jan 08:26:26 - Chat channel Game_24361177125537785 has 1 person(s) online```

After starting the lobby, but still the bot can't listen the in-game chat. Maybe the prefix or the number are wrong. I can't nethook, because I don't know how :D.

Read the link.

Stale issue. Probably technically possible, but requires a code sponsor or for the proposer to do the leg-work and Nethook to see if it's possible.
Make a new issue or open a new one if you Nethook it.


Raise helpful warnings with Faster R-CNN train script

Error message
$ python train.py
Traceback (most recent call last):
  File "train.py", line 161, in <module>
    main()
  File "train.py", line 76, in main
    'Some hyperparameters are not set.\n'
ValueError: Some hyperparameters are not set.
Please specify the following arguments: 'dataset', 'step_size' and 'iteration'.
ex: python train.py --gpu 0 --dataset voc07 --step_size 50000 --iteration 70000

Why don't you use required option? https://docs.python.org/3/library/argparse.html#required

Thanks. I did not know the option.
The page says the following.
Note Required options are generally considered bad form because users expect options to be optional, and thus they should be avoided when possible.

Maybe, it is better to set default values.
In that case, the default values should be for the simplest experiment, which is VOC07 in this case.

Maybe, it is better to set default values.
In that case, the default values should be for the simplest experiment, which is VOC07 in this case.

I agree. The options with --<name> style should be optional. (at least in argparse). It is a good idea to use VOC07's setting as the default values.

Perhaps, it is better to use VOC0712's setting because we switched the default setting from VOC07 to VOC0712 in #350.

It depends on what you want to set as the default training parameters.
Personally, the most simple setting should be preferred for the default parameters.
"Simple" means that a script finishes quickly and the GPU memory requirement is low.
Although, the difference is not huge, VOC07 ends faster than VOC0712 and downloads less images.
Analogously, if ResNet is added to the train script, VGG feature extractor should be the default extractor.
For evaluation, the choice of pretrained weights do not matter for speed, so it can be anything.
I think it is fine to use weights trained with VOC0712, which is performing the best.

I know why you chose VOC07 as the default of training and VOC0712 as that of testing. However, I thought the difference between training and testing is confusing for users. Perhaps, some user wonder why the score of the trained model is lower than that of the distributed model.

I think it is fine to use weights trained with VOC0712, which is performing the best.

Will you change the default value whenever we add a better model?

I know why you chose VOC07 as the default of training and VOC0712 as that of testing. However, I thought the difference between training and testing is confusing for users. Perhaps, some user wonder why the score of the trained model is lower than that of the distributed model.

How about making all pretrained weight options to the simplest setting? (in this case VOC07)

How about making all pretrained weight options to the simplest setting? (in this case VOC07)

It is OK.

Updated


Allow creating transactions without payee

Overview
actualpy fails to create a transaction without a payee.
When a default (payee='') payee value is used, actualpy searches for a payee with an empty name and expects to find only one such payee. Actual Budget uses special payees to represent transfers between accounts. Such payees always have an empty name. If a budget has more than one transfer payee, create_transaction will fail because get_or_create_payee will find multiple payees with empty names and fail validation.
When a None payee value is passed, create_transaction succeeds, but then Actual errors because of a invalid payee (I haven't captured the exact error, but you can easily reproduce this but calling create_transaction(..., payee=None)) and then editing this transaction in Actual.
Solution
This proposal adds support for the None payee value in create_transaction.
When a None value is passed, the implementation does not attempt to create a payee, and passes None as a payee_id in create_transaction_from_ids.
The proposed implementation should be backward compatible.

Thanks for the PR, actually I don't know why I've set the payee to an empty string initially... I tried on the UI and it's apparently setting it to none, but I guess it was to overcome this issue with the payees linked to the accounts, but your solution is better.
I'll check if all tests run when changing the default and I'll merge it.

Thanks, it's now merged. The default has also been changed to None because that is the frontend default.


Add MATHDX_HOME as band-aid

@conda-forge-admin, please rerender

The actual problem is: There should not be any subdirectory under $CONDA_PREFIX/include.

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender


add 3.0.0-M3 to crossScalaVersions and travis ci

add 3.0.0-M3 to crossScalaVersions and travis ci
I expect there's more to do to support scala 3 but this is a start

Scala 3 support done in #402


Increase Java Driver local pooling to 8 (from default of just 1)

With native CQL driver access we can modify default configuration, and we think that the default setting of a single connection is not optimal. Let's try with 8 instead.

Fixed via https://github.com/stargate/jsonapi/commit/69f16c385ec87afd8df6bbd0063679c18ebb8016


Checking if user is admin in php72

I just tried to deploy using php72, and got
Class 'google\appengine\api\users\UserService' not found
Is there a way to do something like UserService::isCurrentUserAdmin() to show the admin part of the site? thanks

Just saw on docs:
The Users API service is not supported in the App Engine standard environment PHP 7.2 runtime.


Ingress controller - set number of pods to 3(number of masters)

Build FAILURE, see build http://<IP_ADDRESS>:8080/job/dev-tools/385/

Build SUCCESS, see build http://<IP_ADDRESS>:8080/job/dev-tools/488/

lgtm, also tested locally and resolved issues testing with #200 applied


codeql: 2.5.5 -> 2.5.6

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/github/codeql-cli-binaries/releases.
meta.description for codeql is: "Semantic code analysis engine"
meta.homepage for codeql is: "https://semmle.com/codeql"
meta.changelog for codeql is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/zczp4y308dpv48kp60744q1sva9szcld-codeql-2.5.6/bin/codeql passed the binary check.

0 of 1 passed binary check by having a zero exit code.

1 of 1 passed binary check by having the new version present in output.

found 2.5.6 with grep in /nix/store/zczp4y308dpv48kp60744q1sva9szcld-codeql-2.5.6

found 2.5.6 in filename of file in /nix/store/zczp4y308dpv48kp60744q1sva9szcld-codeql-2.5.6

directory tree listing: https://gist.github.com/63d9c9c60718e225df2aefae3945c7d1

du listing: https://gist.github.com/359d65ba49a1cd33c53dc2fd33199dfa

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
0 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
0 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
codeql

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/zczp4y308dpv48kp60744q1sva9szcld-codeql-2.5.6 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A codeql https://github.com/r-ryantm/nixpkgs/archive/19194c50a2da81910a0ddc285736ea476bd67a1c.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/zczp4y308dpv48kp60744q1sva9szcld-codeql-2.5.6
ls -la /nix/store/zczp4y308dpv48kp60744q1sva9szcld-codeql-2.5.6/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

codeql

Maintainer pings
cc @jollheef for testing.

Result of nixpkgs-review pr 127857 at 19194c50 run on x86_64-linux 1

1 package built successfully:

codeql

1 suggestion:

warning: missing-phase-hooks
installPhase should probably contain runHook preInstall and runHook postInstall.
Near pkgs/development/tools/analysis/codeql/default.nix:42:3:
   |
42 |   installPhase = ''
   |   ^


only first invocation of defaultHandler is used

https://github.com/scotty-web/scotty/issues/215#issuecomment-379476979

this behaviour is fine, it just needs to be documented.


Adding owner reference to the external secret name.

Fixes #918
Signed-off-by: Gustavo Carvalho<EMAIL_ADDRESS>

The way I implemented FQDN was to allow this awesome oneliner: kubectl get secrets <my-secret-name> -o jsonpath='{.metadata.managedFields[*].manager}' | tr " " "\n" | grep "externalsecrets.external-secrets.io" | xargs kubectl get

so... anyone knows what's happening with the e2e tests? :sweat_smile:

/merge


Stage 2 updates from Pat

(These are not necessarily in order of commit)

Some text edits in guidelines
Add/update angular size measurement into table when measurements are made/updated
Hide ruler until you get to guideline ang_siz3
Auto-advance to guideline ang_siz4 when ruler is clicked first time
On ang_siz4:
-- Display text "Measure angular size of galaxy" instead of next button until first angular size measurement is made
-- Change text to "next" button after measurement is made
-- Auto-advance to guideline ang_siz5 after measurement is made

all of the changes mentioned in this PR check out on my review. Merging.


added logging of missing image magic.

For easier debugging, provide log ouput when supplied image data lacks the "magic" part. Without this, sharing fails silently when the magic is missing.

Thanks for the PR, it is a good catch. Can you update the log message to mention that the image string has to start with "data:image"? magic is something interval that can produce further confusion :).

Hi. Thanks, I agree. The log message has now been updated according to your feedback!


Can't fix "Timed out fetching a new connection from the connection pool"

Bug description
We are using a small database (2GB of RAM, 48GB of storage, 92 max active connections) and very lightweight queries and Prisma times out frequently. 90% of the queries are findUnique-queries and we have set the connection limit to 86 connections. The remaining 10% are findMany queries that are not executed as often but have a rather restrictive filter that is indexed.
Frequently (i.e. in ~20% of all cases) findUnique queries take more than three seconds to complete or time-out waiting for a connection.
How to reproduce
Create a DB with 4 tables of 500.000 rows.
Expected behavior
Unique queries execute instantaneously in all cases, the DB doesn't timeout waiting for a connection in the pool.
Furthermore,

is it expected that trivial findMany queries in tables with <500.000 rows take more than a second?
what's the expected spec of the DB for Prisma?
is there any info about the overhead that using Prisma / prisma.raw creates?

Prisma information
generator client {
  provider = "prisma-client-js"
}

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

model User {
  id String @id @default(cuid())

  createdAt  DateTime @default(now())
  lastActive DateTime @default(now())

  nickname String?
  country  Country?

  expoPushToken String?

  ChallengeAttempts ChallengeAttempt[]
  Leaderboards      Leaderboard[]
  Scores            WeeklyScore[]

  Streaks UserStreak[] @relation("UserStreak")

  // Each user may create challenges that make up _his_ leaderboard.
  // Other players may play those challenges and climb the leaderboard.
  // We track scores of those players in LeaderboardScores relation.
  Challenges        Challenge[]
  LeaderboardScores LeaderboardScore[] @relation("LeaderboardAuthor")

  // This player's scores on other players leaderboards.
  PlayedLeaderboards LeaderboardScore[] @relation("LeaderboardPlayer")

  @@unique([nickname, country])
}

model UserStreak {
  id String @id @default(cuid())

  user   User   @relation("UserStreak", fields: [userId], references: [id])
  userId String @unique

  country Country

  // We track streaks as a day difference between the first solved
  // challenge and the last one.
  //
  // To extend the streak, we check if last solved challenge was less
  // than 48 hours ago and update the lastChallengeSolvedAt date.
  // If the player solved last challenge more than 48 hours ago, we
  // reset the streak start date to the current date.
  streakStartedAt       DateTime
  lastChallengeSolvedAt DateTime?

  @@unique([userId, country])
}

// A table that we use to track weekly scores of the players in the global leaderboard.
model WeeklyScore {
  id String @id @default(cuid())

  createdAt DateTime @default(now())

  weekSinceEpoch Int
  user           User   @relation(fields: [userId], references: [id])
  userId         String

  value Int

  @@unique([weekSinceEpoch, userId])
  @@index([weekSinceEpoch])
}

// A table that we use to track users progress for challenges made by their friends.
model LeaderboardScore {
  id String @id @default(cuid())

  createdAt DateTime @default(now())

  player   User   @relation("LeaderboardPlayer", fields: [playerId], references: [id])
  playerId String

  author   User   @relation("LeaderboardAuthor", fields: [authorId], references: [id])
  authorId String

  score               Int
  completedChallenges Int

  @@unique([playerId, authorId])
}

model Challenge {
  id        String   @id @default(cuid())
  createdAt DateTime @default(now())
  updatedAt DateTime @default(now()) @updatedAt

  date   DateTime
  number Int
  word   String
  ranked Boolean  @default(true)

  country Country

  author   User?   @relation(fields: [authorId], references: [id])
  authorId String?

  starts      Int @default(0)
  completions Int @default(0)
  successes   Int @default(0)

  ChallengeAttempts ChallengeAttempt[]

  @@index([country, date, ranked])
}

enum Country {
  SI // Slovenia
  DE // Deutchland
  DK // Denmark
  AT // Austria
  CH // Switzerland
  FR // France
  BE // Belgium
  HU // Hungary
  IT // Italy
  NO // Norway
  GB // United Kingdom
}

model ChallengeAttempt {
  id String @id @default(cuid())

  challenge   Challenge @relation(fields: [challengeId], references: [id])
  challengeId String

  user   User   @relation(fields: [userId], references: [id])
  userId String

  Guesses Guess[]

  @@unique([challengeId, userId])
}

model Guess {
  id String @id @default(cuid())

  attempt   ChallengeAttempt @relation(fields: [attemptId], references: [id])
  attemptId String

  guess String
  order Int
}

model Leaderboard {
  id String @id @default(cuid())

  createdAt DateTime @default(now())
  updatedAt DateTime @default(now()) @updatedAt

  name    String
  country Country

  code    String @unique
  Members User[]

  @@unique([name, country])
  @@index([code])
}

Environment & setup

OS: MacOS
Database: Postgres
Node.js version: 16.13.0

Prisma Version
prisma                  : 3.8.0
@prisma/client          : 3.8.0
Current platform        : darwin-arm64
Query Engine (Node-API) : libquery-engine 34df67547cf5598f5a6cd3eb45f14ee70c3fb86f (at<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli 34df67547cf5598f5a6cd3eb45f14ee70c3fb86f (at ../node_modules/@prisma/engines/migration-engine-darwin-arm64)
Introspection Engine    : introspection-core 34df67547cf5598f5a6cd3eb45f14ee70c3fb86f (at ../node_modules/@prisma/engines/introspection-engine-darwin-arm64)
Format Binary           : prisma-fmt 34df67547cf5598f5a6cd3eb45f14ee70c3fb86f (at ../node_modules/@prisma/engines/prisma-fmt-darwin-arm64)
Default Engines Hash    : 34df67547cf5598f5a6cd3eb45f14ee70c3fb86f
Studio                  : 0.452.0

The error message in the title and the description that some queries are sometimes slower, indicate you are hitting the capacity limits of your current configuration.
Fundamentally Prisma opens up to the pool size / connection_limit (86 in your case) connections in the pool, and then uses them to execute queries against the database. When a new query comes in, it gets one of these connections from the connection pool and executes it.
If all connection are busy with queries, it has to wait until a connection becomes available and then executes the query. This is what can lead to some queries being slower than the actual SQL under the hood. A good way to figure that out is to log the SQL query duration and compare it to how long the Prisma Client query took. The difference is overhead - and wait time for a connection.
When that wait time it longer than pool timeout, by default 10 seconds, you get an error message instead of waiting longer for the query to succeed so you can handle that manually (either retry or react in some other way like throwing an error).
So you description with sometimes slower queries and sometimes connection pool timeout errors matches pretty well with your system scrating at the capacity limit it can handle.
So how to go about it? That is a difficult and complex questions. There are multiple approaches:

Update Prisma Client to a newer version. We frequently fix bugs and improve things. Especially 3.12.0 in ~10 days should improve the connection pool behavior, but already 3.11.0 should be better than 3.8.0.
Make sure you do not have additional apps or instances running that connect to this database. Your description above is about 1 app instance running Prisma Client that has a pool size of 86. If there are "other players", this could influence thigns a lot.
Get an overview what queries you are sending and how long they take. Does it make sense hat 86 of them are running at the same time sometimes? Does your database metrics confirm that? Does the math work out for the # of requests you handle? (Caution: Each request probably executes multiple Prisma queries which might run multiple SQL queries under the hood)
Send less queries. Less queries means less load. Can you avoid some? Cache some?
Send faster queries. Are you potentially missing some indexes that could improve the query performance overall?
Measure if you have query queing/waiting time or something else (database side, e.g. overload) that makes your queries slower. Knowing that will inform further decisions.
Look more at your database: Does it have CPU spikes? Other error messages in the log files?
Increase the pool timeout to a higher value and see how that changes the behavior.
Scale up your database so it can reply to queries faster.
Scale up your database so it can can handle more connections.
Put PgBouncer in front of your database so the connection limit can be increased that way.

That way you can usually figure out what is going on and how to fix it.
To your additional concrete questions:

is it expected that trivial findMany queries in tables with <500.000 rows take more than a second?

That depends on the SQL that is executed underneath. Prisma "only" runs SQL and then transforms the data. If one of the two is very resource intensive, that will take time. Start by looking at the SQL.

what's the expected spec of the DB for Prisma?

Prisma does not have special requirement for the database. What kind of database you need depends on your queries and the request patterns you have. At some point the "bandwidth" (# connections, length of queries leads to all connections being busy all the time) of all the connection is just reached, and then you will get error message or timeouts. See the strategies above how to handle that.

is there any info about the overhead that using Prisma / prisma.raw creates?

Overhead of course is there (need to figure out what the query means, what the SQL for that looks like, execute it, get the data, transform the data inot something JS will like, and then return the data to the app.) but usually does not matter that much in most usage scenarios. Raw SQL executed via the native database client will always be faster though (unless you write less optimal queries or more than what Prisma would generate. Which happens more often that we would have expected.)

Hey @maticzav,
Have you perhaps managed to solve your issue? If so, do you have any updates for us that could help us make the experience better for users? (eg: better docs)
Thanks! 🙏

@Weakky I don't think we did. I think we started using something else entirely, because we continualy kept hitting the limit with Prisma.

@maticzav Thank you for your reply and your patience! For now, we're going to be closing this issue but if you run into something similar, please open a new issue.

I have a Postgres DB with a limit of 97 connections. However, Prisma frequently times out when it reaches ~10 connections.
@maticzav what solution did you move over to?

Funnily enough I am trying Drizzle. Impressive experience so far, especially the simplicity.

I have a Postgres DB with a limit of 97 connections. However, Prisma frequently times out when it reaches ~10 connections.

Can you open a new discussion or issue about this @raulsanchez1024? A closed issue is not the right place to start a conversation, which we totally want to do. (For example: What is the size of the connection pool you have configured for Prisma?)

@janpio could you back reference this issue when you create a new one? I am also interested in hearing the wider context of @raulsanchez1024's problems and possible solutions.

My 2cents; I don't wholly agree with the sentiment of the "closed issue is not the right place to start a conversation" especially when you close the issue with "we won't be looking into it".
This is also like the third issue that I spotted with the same pattern of "create a new issue → opens a new issue → we won't be looking into it → create a new issue" and it undermines my trust in Prisma which sucks because I love Prisma.

Of course, maybe @raulsanchez1024 can also just @ mention you when he opens a new issue.

My 2cents; I don't wholly agree with the sentiment of the "closed issue is not the right place to start a conversation" especially when you close the issue with "we won't be looking into it".
This is also like the third issue that I spotted with the same pattern of "create a new issue → opens a new issue → we won't be looking into it → create a new issue" and it undermines my trust in Prisma which sucks because I love Prisma.

Existing issues are bad places to start an investigation because we do not have the information the issue template asks for. I have no idea what Prisma version Raúl is using, that database he is talking to, and so on.
If we later figure out he has an actual problem, it in no way has to mean that it was caused by the same problem you had. "Timed out fetching a new connection from the connection pool" is a generic "There is too much stuff going on" error message that can have a million reasons unfortunately.
And finally, you know we never just close issues with "we won't be looking into it". We closed this one as we did not have enough information to understand what was happening, and you indicated that you could not provide more information anymore. That is fine, but it means we have to close the issue as there is nothing actionable for us.


Up till which Schema.org Release this repo src is updated?

Not an issue, but a question.
There are now release by Schema.org as described here:
https://schema.org/docs/releases.html
Is there any identification in the repo describing uptill which release version the src folder is updated?
Tried to look but could not find.
Thanks in advance

Hey,
we have this on our map - right now we are on v7.04.
https://github.com/spatie/schema-org/blob/b1c88dc9744e70679a466b26432e8b85e4daac64/generator/Console/GenerateCommand.php#L34-L36
Because v8 would be a BC/major release we delay this until #133 is resolved.
One question in it is if we should build and deliver the extensions by default. If so, in a dedicated namespace each and possibly also a dedicated factory class or if we should stick to the basic schema definition.

Thanks @Gummibeer
For the quick update.
I wish i could give you some input on this but my php skills are below the required to comment on this.


⚠ Jenkins Plugins Artifactory has degraded performance

In 1ac7384, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1121 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 9419890 after 12 minutes.


Not working on Windows 10

When using this with any code (including running test/run.sh) I am getting the following in the output file:
javascript:(function()%7BNaN%7D)()

I am getting the same result on macos:
javascript:(function()%7BNaN%7D)()

When I run it on the js file I want to turn into a bookmarklet, I get:
javascript:(function()%7Bundefined%7D)()

I'm also getting the same error.

Should be solved form #8 🥂


Added ServletContext parameter to SparkApplication.init

This is a small change which doesn't break the filter API but allows its users to access to the servletcontext while initializing if they wish. Related to #524

Pushing a little further we could also add a @Deprecated annotation to the original init() call

@perwendel Is there any chance for this to get merged?

@perwendel Is there any chance for this to get merged?


Add attribute clamping and armor limit config

Create a pull request documenting the config additions to PurpurDocs, and you'll be golden


fix: init scroll bug

 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.


AUTOCOMPLETE DISPLAYWITH FUNCTION

Bug, feature request, or proposal:
The function used in displayWith can't access properties of the host component. I'm not sure if this is a mistake or it is a design choice.
I cannot use the arrow function as TSLINT complains and also somehow i see the whole function inside.
What is the expected behavior?
It could access properties in the scope of the host component
What is the current behavior?
Same as the first answer.
What are the steps to reproduce?
Just create a public/private property in the host component class and try to access it.
Here is the plunker (the material.angular.io Autocomplete example modified)
https://plnkr.co/edit/2EgoBdPDohzFa1DYoU2P?p=preview
What is the use-case or motivation for changing an existing behavior?
I was trying to reuse a single autocomplete in two different situations, selected by the user choice in a radio-button-group. Than I used ngModel to get the user's choice and setup the autocomplete according to it. But, depending on the user's choice, the autocomplete works with very different objects and should display very different information when one option is selected from the list.
Which versions of Angular, Material, OS, browsers are affected?
@angular/cli: 1.0.0-rc.0
node: 6.9.5
os: win32 x64
@angular/cli: 1.0.0-rc.0
@angular/common: 2.4.8
@angular/compiler: 2.4.8
@angular/core: 2.4.8
@angular/flex-layout: 2.0.0-rc.1
@angular/forms: 2.4.8
@angular/http: 2.4.8
@angular/material: 2.0.0-beta.2
@angular/platform-browser: 2.4.8
@angular/platform-browser-dynamic: 2.4.8
@angular/router: 3.4.8
@angular/compiler-cli: 2.4.8
Is there anything else we should know?
I can easily replace the one autocomplete by two of them, no problem. Just wanted to report this.

I have the same issue. Followed the recommendation given by #3308 to wrap it in an arrow function however as commented by @arat3091 - "It is showing the function on the input box."
Attached is the plunker
https://plnkr.co/edit/9uwUwd97diGzeDIpAeHg?p=preview

You can do it like this:
<md-autocomplete #auto="mdAutocomplete" [displayWith]="displayFn.bind(this)">

displayFn(val) {
   return this.outsideVariable + val;
}

modified plunker: https://plnkr.co/edit/DU7Yj8QfeCK2UDabbmwl?p=preview
OR if you want to use the arrow syntax:
<md-autocomplete #auto="mdAutocomplete" [displayWith]="getDisplayFn()">

getDisplayFn() {
   return (val) => this.displayFn(val);
}

displayFn(val) {
   return this.outsideVariable + val;
}

modified plunker: https://plnkr.co/edit/R3FtDnCLcFu3I5mJCadj?p=preview

Thank you @mxii displayFn.bind(this) works

@arat3091 I think you can close / resolve your own issues, just so you can save the material guys some time, there are a ton of these to look through


Version Not Updated in CMakeLists File 5.6.2

Hello, 👋 . I was reviewing this  pull request in Conan Center Index (https://github.com/conan-io/conan-center-index/pull/25967) to add the latest version, and I noticed that in the new 5.6.2, the version number has not been updated in the CMakeLists file.
See: https://github.com/simdutf/simdutf/blob/v5.6.2/CMakeLists.txt#L6

Fixed. Thanks for the report.


add translated loadmanagement page

Translated the loadmanagement page to english

changed based on
https://github.com/evcc-io/docs/issues/587

Thanks for the change. I've made some tweaks and also adjusted the german version.
https://github.com/evcc-io/docs/pull/591


Can this be used with Router?

If so would you be willing to show me a quick example and how to require it correctly? Thanks!

I am also curious about this. I'm having trouble using it with router.

i really want to use this with router

any help


Ideas for flexible formatting

How about making doxme formatting customizable?
For example, with a predefined readme structure like
# project name
## installation
## usage
## api
{{ doxme output }}
## license

…one would want function names to be prepended with ###  instead of ## .
How can we do it?
I have two ideas:
1) Accept custom string-based templates
doxme([/* dox output */]
  , { readme: false
    , formatting:
      { functionName: "### %s"
      }
    }
  );

And in the command line:
$ ... | doxme --formatting='{"functionName": "### %s"}'

– or (this I like better):
$ echo '{"readme": false, "formatting": {"functionName": "### %s"}}' > .doxme.json
$ ... | doxme

Pros:

Easy to implement – the templating is already built in :)
JSON-serializable config

Cons:

Not very flexible – e.g. what when we have %s twice, and only want the second one?
If the tool grows, we can quickly end up with dozens of variations of one template (like functionName, functionNameWithParameters, functionNameWithRepetitiveParameters etc.)

2) Accept custom formatting functions (this one I like a lot better)
doxme([/* dox output */]
  , { formatting:
      { functionName: function (name, parameters) {
        return ("### " + name + (parameters
          ? "(" + parameters.join(", ") + ")"
          : ""
          ));
        }
      }
    }
  );

In the command line:
$ echo 'module.exports = {formatting: {functionName: function (...' > .doxme.js
$ ... | doxme

Pros:

A lot more flexible
"do one thing, and do it well" – templating isn't necessarily "the thing"
We could enable the user to parse tags not supported by us – for example through a head(tags) and tail(tags) formatting function:

{ tail: function (tags) {  // Parse the tag @deprecated
  return (
    ( tags.some(function (tag) {return (tag.type == "deprecated");})
    ? "\n_Deprecated_\n"
    : ""
    ));
  }
}

Cons:

One could argue that it's more difficult to setup through the CLI (though I wouldn't agree)

Why would we do it?
Adherence to the Unix "do one thing and do it well" principle is what drew me to doxme in the first place :) Markdox tries to replace dox, so it chokes with non-flexibility.
But Unix programs not only "do one thing" but also "do it well". As I understand it, it means that they are very flexible.
Let's make doxme like that :)

How about making doxme formatting customizable?

I'm not very convinced that there's a concrete use case for this: re-ordering sections? h2s instead of h3s? Seems like reasonable defaults cover 90+% of cases.

I'm not very convinced that there's a concrete use case for this: re-ordering sections? h2s instead of h3s?

Or rather h4s instead (sorry, I've made a mistake in my example)
Support for rarely-used or custom tags
Non-standardized conventions
I'm sure there's way more

My concrete problem at the moment is the third. I'm looking for a good way to document a heavily overloaded function. Standards don't work well in this case, as you can read here: https://groups.google.com/forum/#!searchin/jsdoc-users/overloaded .

Seems like reasonable defaults cover 90+% of cases.

Well, if you look at different readmes in github, you'll hardly ever find two structured in the same way. Every developer has their own conventions and opinions.
Reasonable defaults are great for a start, I agree in that. But "for a start" really means "only up to a point".

@tmcw for reference, here's the case I'm talking about: http://npm.im/parametric-svg – see for yourself.
In the case of doxme's readme, the defaults really work great. But in my project the outcome isn't too readable.

Couldn't you use jsdoc's multiple parameter type syntax for this?

I've tried. But in my case it would be „If you supply an SVGSVGElement, it will be treated as a ... . The second parameter is then optional and will mean ... . If you supply an SVGElement, it will be understood as ... . The second parameter is then required ...” etc.
Think how, say, any jQuery function could be documented with multiple parameter syntax.

The 'just document it multiple times' convention seems to work for me.
Basically customizing doxme's formatting doesn't really make sense to me: it basically just is a template and nothing more. swapping out the formatting means swapping out the whole thing, and at that point... just fork

Yup, and that's what I actually did.
But I see what you mean since I looked closely at the code.
Alright then. As there doesn't seem to be anyone else backing my idea out there, I'm closing.


Bug: Editing the Color Set Name

Describe the Bug
Editing the Color Set name field only updates the UI. Export still uses the system-generated one.
Steps to Reproduce

Add multiple Color Sets
Edit the Color Set name's field from the predefined ones to something random like "GitHub"
Click on "Export all colours to JSON"
Checking the contents of the clipboard it can be seen that the name was not updated.

Expected Behavior
Similar to "Export Colors" we should have the palette be updated for the user. Clicking on "Export all colors to JSON" and "Export all colours to HEX" should be behaving similarly.
If we are only allowed to have predefined palette names then these should be dropdown, not a custom input field.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment

OS macOS
Browser Chrome

Additional Context
We could keep the predefined values for filling in the gaps if there's no custom input.
I can contribute to fix this issue.

Thanks for opening this @lakshmi930
Unfortunately, we have something similar open already - https://github.com/utk09-NCL/color-palette-generator/issues/38 & https://github.com/utk09-NCL/color-palette-generator/issues/51 so I'm going to close this one.
Feel free to open anything else or contribute to new features that I have in pipeline.


Nail down Node version so CI doesn't break

Fixes #395.

Emergency fix so PRs in flight can complete - probably good to clarify if there is a real underlying issue on Node 11 but this gets us building again for now.


If branch not sent, take default branch

This will enable SDK and clients not to send branch information. That way, it will use the default branch if not provided.

closes https://github.com/Visual-Regression-Tracker/Visual-Regression-Tracker/issues/342


Do not show weekdays when returning to time

If you disable the "Show weekdays" feature, weekdays will still be shown when the clock/date switch is active and the display returns from date to clock. The weekdays will be removed with the next update of the clock one second later.
This change keeps the weekdays from appearing.

Thanks!


Switch from winapi to windows crate

This update entirely removes the winapi dependency and replaces it with the windows crate.
This is just a straight port of the API calls to avoid conflating different changes so we can be reasonably confident the port is sound since some of those APIs are a bit complex. Subsequent improvements can then be made since the windows crate supports idiomatic error propagation, among other things, to simplify the code further.
The windows crate has the option to generate bindings as part of a build script, but this can sometimes be a prohibitive cost for library crates. In order to avoid that overhead, I opted to create a "bindings" tool that I also included in the PR that generates the bindings ahead of time and then can simply be compiled as part of the the miow crate. This is how the windows crate itself makes uses of Windows APIs internally. Until we have support for pre-packaged APIs I think this is the best approach for library projects like this one.
A nice bonus is that compiling with the windows crate is almost 2 seconds faster. 😊
Before:
Finished dev [unoptimized + debuginfo] target(s) in 4.92s

After:
Finished dev [unoptimized + debuginfo] target(s) in 3.07s

@kennykerr oh, I didn't expect you to close the PR! - I was hoping we could find a way to resolve the issues I pointed out so we can merge windows-rs as a dependency for miow.
You mentioned a long-term goal is to generate a pre-built library, and publish it to crates.io. That would certainly help resolve the biggest blockers towards landing this. Do you think we could make progress towards that in the short term? For example: is there a way we could prototype an MVP of those bindings specifically to support miow, and use that to build up the larger set of bindings?


What happens when the access token expires

Hi!
Looking through the sources of the backend and frontend I can't figure out what happens when the JWT access token expires. Is there a strategy in place to extend the access token if the user is using it frequently?

When the access token expires, a user would need to login again, sending a request to the backend's /login/access-token route to get a new access token.

@csmcallister: Where in the code it is actually enforced?

Take a look here first:
https://github.com/tiangolo/full-stack-fastapi-postgresql/blob/490c554e23343eec0736b06e59b2108fdd057fdc/{{cookiecutter.project_slug}}/backend/app/app/api/api_v1/endpoints/login.py#L36
Then follow the core.security import to here:
https://github.com/tiangolo/full-stack-fastapi-postgresql/blob/490c554e23343eec0736b06e59b2108fdd057fdc/{{cookiecutter.project_slug}}/backend/app/app/core/security.py#L15
As you can see there, the expiration is either pulled in from the app settings or can be overridden with a custom value. The jwt library is responsible for taking in that expiration value. Their docs explain how expiration is determined and enforced: https://pyjwt.readthedocs.io/en/latest/usage.html

@emsi stumbled upon this today. In addition to @csmcallister's hints, you can use the /login/test-token endpoint (or any other one for that matter) to check if you're current token is still working. It feels a bit hacky though...

Is there something planned to handle the expiration?
Like implement a refresh endpoint in the backend and call the endpoint in the frontend?

Yeah I'm definitely experiencing and endless loop of 403 Forbidden requests to http://localhost/api/v1/users/me when attempting to access the dashboard with an expired access_token.
It seems that, it doesn't actually check if token is expired, only that it is present.
https://github.com/fastapi/full-stack-fastapi-template/blob/5005e5a5c17716c8a51bc3fa162e994c1c6035cd/frontend/src/hooks/useAuth.ts#L16-L18

Same issue here. If the user leaves the browser window open for a while then comes back, the app appears to be broken, i.e. the backend returns 403, but the frontend doesn't report this to the user, only hangs.
Suggestions:

Add a refresh token endpoint on the backend. The frontend should automatically request a new access token when the current one is about to expire or has expired, using the refresh token. This prevents 403 errors caused by expired tokens.

If a 403 error is returned for any other reason, the frontend should gracefully handle it by providing a clear message to the user and/or redirecting them to the login page.

Similar issue found in case of start-stop the backend, so ah the same behaviour take into a place when token will expire. Spinner goes into an endless loop.

After some experiments with expired/Signature verification failed exceptions, faced with issue that the project need refresh token mechanism as @hollowdew and @abrichr says above, I'm also will looking to see this stuff here guys, can anyone share some sketches?


Hotspot b58 Addresses
1127M9wZs4XzK3kEFSPG7T7LvJ7LJusJrpqT4S9jLniFjLEvnAr1
Discord Handle
No response
Reason(s)

Self witnessing (cannot be witnessed by nearby miners which are there a few months ago)
Hotspots only witnessing each other
they poping up on the same day

For the last few days I can see a large list of makers in the witnessed list:

Maker
Number of witnessed

Bobcat
5

Cal-Chip Connected Devices
4

None
4

SenseCAP
2

PantherX
2

Nebra Ltd
1

FreedomFi
1

RAKwireless
1


Helpers script to remove old .kibana indexes

Kibana every time it restarts, creates a new .kibana_ index and update the alias.
For example the index .kibana_4 is the index which alias is .kibana.
Those indexes are used to keep the kibana configuration and are kept in case of a configuration rollback/restore.
It might be the case to keep just the latest index and delete the old ones.

Opensearch/Opendistro maintenance is now outside of the scope of Lagoon


[sui-execution] Re-implement wrapper script in Python

Description
Replace the bash script with an equivalent python script.  This is to prepare for a couple of improvements:

Automating the creation of the new modules in sui-execution, and the executor and verifier dispatch functions.
Adding rebase and merge commands to simplify keeping up with other changes in the execution layer.

Test Plan
sui$ black scripts/execution-layer
sui$ flake8 scripts/execution-layer
sui$ ./scripts/execution-layer --dry-run cut v1
sui$ ./scripts/execution-layer cut v1

If your changes are not user-facing and not a breaking change, you can skip the following section. Otherwise, please indicate what changed, and then add to the Release Notes section as highlighted during the release process.
Type of Change (Check all that apply)

[ ] protocol change
[ ] user-visible impact
[ ] breaking change for a client SDKs
[ ] breaking change for FNs (FN binary must upgrade)
[ ] breaking change for validators or node operators (must upgrade binaries)
[ ] breaking change for on-chain data layout
[ ] necessitate either a data wipe or data migration

Release notes

out of curiosity, why no extension to the python file?

I tend to leave it off for things that look like they could be binaries, I guess to give the illusion of legitimacy (no extension, this must be a polished binary and not some hacky script that @amnn wrote), but I see now that nobody else is doing this in our scripts folder (🥲) so I can add the extension, no problem.