feat: Pyion can now optionally return bundle headers when receiving

A new optional parameter for bp_receive called return_headers has been created. This param takes a boolean value where if set to True, the function call will return a tuple where the first value is the bundle payload and the second is the bundle headers.
The current behavior is to return only the bundle payload. This param is set to False by default so that any existing code will not be broken by this change.

@CWagner23 Please check out this documentation and see if you agree that when a y# is passed to Py_BuildValue the content of the memory buffer is copied. If you do agree, you can close out the TODO before we merge the pull request

@msancheznet I agree that it does copy, so I have removed the TODO comments


AzureSearch error

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain rather than my code.
[X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

Example Code
index_name: str = "langchain-vector-demo"
vector_store: AzureSearch = AzureSearch(
    azure_search_endpoint=vector_store_address,
    azure_search_key=vector_store_password,
    index_name=index_name,
    embedding_function=embeddings.embed_query,
)

Error Message and Stack Trace (if applicable)
Exception ignored in: <function AzureSearch.del at 0x000002B588070FE0>
Traceback (most recent call last):
File "C:\Users\n\AppData\Local\Programs\Python\Python311\Lib\site-packages\langchain_community\vectorstores\azuresearch.py", line 393, in del
File "C:\Users\n\AppData\Local\Programs\Python\Python311\Lib\asyncio\events.py", line 761, in get_event_loop_policy
File "C:\Users\n\AppData\Local\Programs\Python\Python311\Lib\asyncio\events.py", line 754, in _init_event_loop_policy
ImportError: sys.meta_path is None, Python is likely shutting down
Description
Made everything as here:
https://python.langchain.com/docs/integrations/vectorstores/azuresearch/
when calling it i get error like above
System Info
python 3.12
langchain latest

It has nothing to do with Langchain, their is something wrong with your python environment. Or how you are starting the asyncio event loop. Can you share code so I can help you better

related https://github.com/langchain-ai/langchain/issues/27511


Allow components to be displayed within an iframe

Subject
Allow components to be displayed within an iframe
Description
Display in an iframe, like the documentation site, so that modals and drawers can be displayed within the preview.
https://github.com/yamada-ui/yamada-ui/blob/e67ca8473a9b76fc23b6e2e9e03ee464c1c3260c/docs/components/mdx/editable-code-block.tsx#L276
Are you willing to participate in the development of this feature and create a pull request?
None

I have an iframe implementation in this branch, but the theme and config are not reflected properly in the iframe.
https://github.com/yamada-ui/yamada-components/blob/feat/iframe/components/data-display/component-preview.tsx


Claim rewards

Is your feature request related to a problem? Please describe.
Provide a process where users can register their positions to receive rewards, see their available rewards, withdraw and restake.
Background
Some bancor liquidity pools have rewards allocated for users who stake liquidity in them. To qualify for these rewards, you need to have a protected position activite on the relevant pool that receives rewards.
UPDATE - we will calculate the rewards off-chain, which means the LM contract will include all eligible wallets and positions with no need to “register” or take action from the user’s side.
Meaning, if you have a protected position and it is on a pool that qualifies for LM rewards, that pool id will be available on the LM  contract and you can immediately interact (claim/restake) with it.
Describe the solution you'd like
see google docs for details
Attached Issues

[ ] Fetch Rewards information from the Rewards contract instead of hard coding it in the frontend #809
[ ] Implement Claiming of Rewards #810

protection table
https://www.figma.com/file/3yED7o7TgoLwoEjV2EkRLL/Bancor-V2?node-id=1443%3A22
summary table
the new summary table will include data and actions:
Data:

claimable rewards: this value indicates the currently available rewards that were already signed on the onchain contract and are claimable.

this value is pulled from the contract on-chain. it is updated every few days at first, so best if you track events and update when needed (instead of trying to pull it all the time when it doesnt change)
calculate the value in USD based on the BNT price to USD in the system
tool tip: Current rewards that are available to restake in pools and earn fees and rewards when available

future rewards: this value indicates the rewards that are calculated off-chain and represents the rewards that WILL BE CLAIMABLE once the onchain contract is updated. this value keeps growing until it update the on-chain contract and then it starts at 0 again.

pull this data from an off-chain api
refresh often as this is a growing number that increase every second (off-chain calculate it by seconds, not blocks)
calculate the value in USD based on the BNT price to USD in the system
tool tip: Rewards that will be available and added to claimable rewards in the next update

total rewards to date: this value indicates the total rewards given to the user.

pull this data from an off-chain api
refresh often as this is a growing number that increase every second (off-chain calculate it by seconds, not blocks)
calculate the value in USD based on the BNT price to USD in the system
tool tip: Total rewards received

data movement
in order to show movement, we would like to use some type of increasing number effect.

on refresh/load: start all 3 values at 0 and grow them to the number they should be over a span of 3 seconds.
future and total rewards: if refresh of the data is every 15 seconds, break the delta increase to show over a span of 15 seconds.
claimable rewards: 1) when user claims rewards, count down to 0 in a span of 3 seconds. 2) when there is an update to the claimable rewards, increase the number over a span of 30 seconds
code sample to the effect: https://codepen.io/duvander/pen/KXOpXw

Actions:

withdraw: this action is less preferred and we would like the user to "avoid" it as it will reset the multiplier.

https://www.figma.com/file/3yED7o7TgoLwoEjV2EkRLL/Bancor-V2?node-id=1443%3A643

restake: this is the main action we would like users to use with their rewards.

clicking the "restake" will open the pool selection interface: https://www.figma.com/file/3yED7o7TgoLwoEjV2EkRLL/Bancor-V2?node-id=1443%3A967
once you select a pool, you will arrive at this interface: https://www.figma.com/file/3yED7o7TgoLwoEjV2EkRLL/Bancor-V2?node-id=1443%3A813

protection table new column/s
in order to make space in the table which is getting too big to display, we have done few changes to the table columns.

fees & ROI: merging these two columns into 1 will save space and merge two similar items together.

tool tip: Fees your stake has earned since you entered the pool and the Return on Investment given full protection.

rewards: indication of "lifetime rewards"

per row (in case of group, sum of all rows)
position multiplier (coming from off-chain api and changes every 7 days). group row should average this number. example: (row 1 multiplier + row 2 multiplier +...+ row N multiplier) / N rows

actions: changing to icons

mouse over: 1) group icon: "Un-Group" / "Close Group" 2) "Withdraw"

https://www.figma.com/file/3yED7o7TgoLwoEjV2EkRLL/Bancor-V2?node-id=1443%3A22

Comment from @ashachaf
make sure the update goes live together.
check:
IF the user has protected positions in pools that receive rewards, show the new warning.
https://www.figma.com/file/3yED7o7TgoLwoEjV2EkRLL/Bancor-V2?node-id=1443%3A1158

@ashachaf as a followup to our call today:
Currently we need further information for:
UI mockups and contracts not aligned

Withdraw rewards
ReStake rewards

Where to get this data

Future Rewards
Total Reward to date
Multiplier

@pingustar @Velua @H34D
please review the task details and provide feedback.

@pingustar @Velua @H34D
please review the task details and provide feedback.

return the claimable rewards in bnt amount (Wei) for the indicated wallet.

What's an indicated wallet? @ashachaf

return the claimable rewards in bnt amount (Wei) for the indicated wallet.

What's an indicated wallet? @ashachaf

return the claimable rewards in bnt amount (Wei) for the indicated wallet.

What's an indicated wallet? @ashachaf

the connected wallet you are checking the data for.

return the claimable rewards in bnt amount (Wei) for the indicated wallet.

What's an indicated wallet? @ashachaf

the connected wallet you are checking the data for.

Let's put this on pause now, awaiting further information from @ashachaf

Let's put this on pause now, awaiting further information from @ashachaf

@Velua @pingustar @H34D
lets discuss.
https://docs.google.com/document/d/1KOVa-73JEdCvE6LhSWBnIbrF0ezfeaUQBtd2HdRcAe8/edit#

@Velua @pingustar @H34D
lets discuss.
https://docs.google.com/document/d/1KOVa-73JEdCvE6LhSWBnIbrF0ezfeaUQBtd2HdRcAe8/edit#

Permission requested from my<EMAIL_ADDRESS>account

Permission requested from my<EMAIL_ADDRESS>account

Current Status Update:

claimRewards branch is deployed to staging manually. I didnt want to merge it into staging branch yet.
rewards is getting close and I can finish the rest tomorrow
Claim Rewards Features are NOT tested yet
the api has been updated and broke the frontend at multiple fronts. I believe something with decimal/precision got changed.

To Do:

@Velua review stakeRewards and claimRewards in store/rewards/index.ts
@Velua fix errors based on api changes. @ashachaf and Yarif have more information
get claimRewards branch in production ready state
test claim reward features -> currently unclear how

Current Status Update:

claimRewards branch is deployed to staging manually. I didnt want to merge it into staging branch yet.
rewards is getting close and I can finish the rest tomorrow
Claim Rewards Features are NOT tested yet
the api has been updated and broke the frontend at multiple fronts. I believe something with decimal/precision got changed.

To Do:

@Velua review stakeRewards and claimRewards in store/rewards/index.ts
@Velua fix errors based on api changes. @ashachaf and Yarif have more information
get claimRewards branch in production ready state
test claim reward features -> currently unclear how

@pingustar
bug:
"withdraw" text doesnt show up on dark mode

bug:
Rewards amount and "BNT" jump left to right with the numbers. please try to set them in fix positions so they do not move.
https://streamable.com/w7xfel
text change:
please update the main protection page:
current:
You can protect your token pools with our special insurance for impermanent loss by simply adding insurance to each of your transactions.
updated:
Manage your protected positions in Bancor pools and track and analyze your returns.

@pingustar
bug:
"withdraw" text doesnt show up on dark mode

bug:
Rewards amount and "BNT" jump left to right with the numbers. please try to set them in fix positions so they do not move.
https://streamable.com/w7xfel
text change:
please update the main protection page:
current:
You can protect your token pools with our special insurance for impermanent loss by simply adding insurance to each of your transactions.
updated:
Manage your protected positions in Bancor pools and track and analyze your returns.

text and button is fixed.

text and button is fixed.


Tag new release

I'm getting deprecation warnings while updating packages for v0.7-beta from FFTW.jl.

AbstractFFTs also needs a new release.


MGMT-16697: Added ResourceSync monitor thread

This PR adds a ResourceSync monitor thread:

checks if repository resource exists (adds condition)
checks if git repository is accessible (adds condition)
checks if path in repo exists (adds condition)
Parse dir/file path to resources (adds condition)
if resource is a fleet apply (Only fleets are supported at the moment)
adds latest commit hash and path to the resourcesync status (if path changed or commit - sync should happen)
Added a db transaction to apply all fleets or none

In addition there is a commit that addresses RepoTester monitor. It attaches auth option only if user creds exists.

LGTM as long as  @hexfusion is happy as well


Failed in building : ERROR in ./src/worker.ts

Hi,
Started with Av1 recently and wanted to build the aomanalyzer for the same.
I am getting below error while building aomanalyzer
[478] ./src/worker.ts 7.86 kB {1} [built] [1 error]
+ 466 hidden modules
ERROR in ./src/worker.ts
(2,13): error TS2403: Subsequent variable declarations must have the same type.  Variable 'TextDecoder' must be of type '{ new (label?: string, options?: TextDecoderOptions): TextDecoder; prototype: TextDecoder; }', but here has type 'any'.
npm ERR! code ELIFECYCLE
My build set-up details :-
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>2018-03-30T15_43_24_506Z-debug.log
Please share some pointers
Regards
Pallab Sarkar

#60 fixed the build issue


Suggest to fix typo

'IEE' -> 'IEEE'

@yoichinak : Thanks for your contribution! The author, @erhopf, has been notified to review your proposed change.

#sign-off
@yoichinak - Thanks for submitting the fix!


Add test coverage reporting (via codecov and simplecov)

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@35f397c). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #15   +/-   ##
=========================================
  Coverage          ?   99.20%
=========================================
  Files             ?        4
  Lines             ?      125
  Branches          ?        0
=========================================
  Hits              ?      124
  Misses            ?        1
  Partials          ?        0

Continue to review full report at Codecov.

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


Wire up automated cross browser testing

Feature
Why is this feature being added?

Most likely developers are adding features and testing in one browser. We should have an automated check to make sure the functionality is the same across browsers.
What should your feature do?
In a perfect world I would love to see something that upon a new PR (or update to a PR) looks at the files changed and attaches screenshots (or a link to screenshots) of the pages across the major mobile and desktop browsers. Does browserstack cover this or at least come close?

Sauce Labs and Browserstack provide functionality like this.

We now have a browserstack account.
We still need more detail on how this is implemented. Ideally when a new PR comes in we would have browserstack run some tests/take some screenshots and report its status to said PR.

Do we have a testing framework in mind! Mocha maybe? I know jest is in there by default. I would like to use a good testing library that is easy to write.
Sent from my Samsung SM-S120VL using FastHub

Now we just need someone to write some automated UI tests :)

#327 💃

As for resolving the issue, I think implementing some documentation on using Browser Stack would be good enough to close this.

@kylemh can this be closed due to your testing implementation for the new repo?

No. We need the BrowserStack account information @hollomancer
Once acquired, we can draw up instructions on eyeballing certain browsers on a release basis. We can't exactly share our account out so I think drafting up this methodology is best. It's tough to automate this.


EVA-2722: prepare file for already processed analysis of covid19 project

This looks ok but it makes the assumption that all the already processed files have an analysis in ENA. I'm not sure this is correct. Could you check that it is within the script and count the number of file for which you did not find an analysis

added the check and count for files with no analysis in ENA


Use the right timestamp for notion resources in GC workflow.

Description

Since the Notion garbage collection (GC) logic was modified in #5109, the assumption was made that the workflow would update the resources that still existed in Notion with the appropriate timestamp. This would allow us to execute the same SQL query repeatedly and obtain different results each time.
However, there are logs available (logs) that indicate we are continuously looping over the same page.
This PR aims to resolve the issue by ensuring that we use the same timestamp when updating the resources that still exist and in the SQL query.
This definitely explain the surge of SQL read queries we have been observing lately.
Risk

Deploy Plan

PMRR.


TypeError when choosing nickname

Hello.
I successfully installed everything, when npm start, it works.
I go on a random generated chat like banana, I put my nick, I click "OK" then:
Server disconnected. Attempting to reconnect...
and on the server console:
                    socket._receiver.flush();
                                     ^

TypeError: socket._receiver.flush is not a function
at WebSocket. (/root/hack.chat/server.js:64:21)
at emitOne (events.js:77:13)
at WebSocket.emit (events.js:169:7)
at Receiver._ultron.on._receiver.onmessage (/root/hack.chat/node_modules/ws/lib/WebSocket.js:146:47)
at Receiver.dataMessage (/root/hack.chat/node_modules/ws/lib/Receiver.js:389:14)
at Receiver.getData (/root/hack.chat/node_modules/ws/lib/Receiver.js:330:12)
at Receiver.startLoop (/root/hack.chat/node_modules/ws/lib/Receiver.js:165:16)
at Receiver.add (/root/hack.chat/node_modules/ws/lib/Receiver.js:139:10)
at Socket. (/root/hack.chat/node_modules/ws/lib/WebSocket.js:142:22)
at emitOne (events.js:77:13)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>start: node server.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2017-10-31T13_59_06_273Z-debug.log
data contained in /root/.npm/_logs/2017-10-31T13_59_06_273Z-debug.log:
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/nodejs', '/usr/bin/npm', 'start' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>6 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>7 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
8 verbose lifecycle<EMAIL_ADDRESS>PATH: /usr/lib/node_modules/npm/bin/node-gyp-bin:/root/hack.chat/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/lib/jvm/java-8-oracle/bin:/usr/lib/jvm/java-8-oracle/db/bin:/usr/lib/jvm/java-8-oracle/jre/bin
9 verbose lifecycle<EMAIL_ADDRESS>CWD: /root/hack.chat
10 silly lifecycle<EMAIL_ADDRESS>Args: [ '-c', 'node server.js' ]
11 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1  signal: null
12 info lifecycle<EMAIL_ADDRESS>Failed to exec start script
13 verbose stack Error<EMAIL_ADDRESS>start: node server.js
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter. (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:280:16)
13 verbose stack     at emitTwo (events.js:87:13)
13 verbose stack     at EventEmitter.emit (events.js:172:7)
13 verbose stack     at ChildProcess. (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack     at emitTwo (events.js:87:13)
13 verbose stack     at ChildProcess.emit (events.js:172:7)
13 verbose stack     at maybeClose (internal/child_process.js:862:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:222:5)
14 verbose pkgid<EMAIL_ADDRESS>15 verbose cwd /root/hack.chat
16 verbose Linux 2.6.32-042stab123.9
17 verbose argv "/usr/bin/nodejs" "/usr/bin/npm" "start"
18 verbose node v4.8.2
19 verbose npm  v5.5.1
20 error code ELIFECYCLE
21 error errno 1
22 error<EMAIL_ADDRESS>start: node server.js
22 error Exit status 1
23 error Failed at the<EMAIL_ADDRESS>start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
Plz help

I'd be nice if people went to browse the issues a bit before posting new ones : https://github.com/AndrewBelt/hack.chat/issues/136

Thanks @raf924, duplicate of #136


Ruins Shuffler

We have a black market shuffler already. Ruins behave in much the same way - maybe a Ruins shuffler would be useful.

It's way different scenario from the end-user perspective though:

Black Market, no app scenario:
Have to run through ALL expansions, grab one of a card, play a game with it, then sort them and put them ALL back

Black Market, app scenario:
Grab the app, whenever you choose a card - grab that expansion box and pull out the card - they are easy to find because boxes are well organized. In practice, rarely anyone buys a whole lot from Black Market, so you take these couple of cards back to their boxes with much less effort.

Ruins, no app scenario
You have to grab this big deck of cards, but it's already assembled together. There's no bustle around every box and cleanup is much easier, it's just putting all ruins back into one deck.

Ruins, app scenarion
You have to keep your ruins organized into 5 separate piles, either all the time or sort them before the game. The only thing we get in return is no shuffling of a massive deck.


Enhance support for default values

Fixes #169.
Makes the following changes:

Properties with default values have their default values assigned in initializers and decoders, if their type is a specifically-supported builtin (previously this only worked for booleans).
Properties with default values that match an enum case will use the enum case as default rather than nil.
Required properties with enum types that contain only one case now automatically use the only case as a default value.

I can see the default value useful as a hit in the generated initialisers, but manipulating the decoded response to fill gaps with it feels like it might be a step too far since nothing suggests that nullable and default are related to each other (thinking outside of Swift).
That being said, I don't know everything so I could be wrong.. Have you compared how some of the other generators in existence use default? I might be swayed if there are other good examples but at the moment I'm leaning towards suggesting that we only apply the default to the initialisers.

I can compare output to some of the other big generators. I generally agree that defaults should not be influencing the decision to generate decoder-inits. I'm also leaning towards minimizing the generation of decoder-inits as much as possible, but that would require us to have a little more insight into whether or not synthesis is possible.

I've put up a couple new solutions to the feedback you've given me. Let me know what you think of this once you've reviewed, given your time and energy.

@aaronsky sorry it took me so long to get back to this! Just to confirm from your last message, my understanding was that we aren't going to provide a default value when decoding via init(from:) and instead would only use the default values in the generated memberwise initialiser?

I believe that's what we agreed on.

@aaronsky sorry it took me so long to get back to this! Just to confirm from your last message, my understanding was that we aren't going to provide a default value when decoding via init(from:) and instead would only use the default values in the generated memberwise initialiser?

I believe that's what we agreed on.

Ah ok then, I ask because I still see the nil coalescing to the default value in the snapshots, like this:
https://github.com/CreateAPI/CreateAPI/pull/170/files#diff-e17d0dd37de44a675de95aef390c1a217a05ce891f7bc9902e7b284b75ec5ed0R92
We shouldn't be doing that, right?

Actually that one is deliberate, because that is the default defined in the github.yml spec

I think that still goes against how we want to interpret default? We want to keep it to be provided as a hint for the memberwise initialiser but we don't really want to start making customisations to the decoder behaviour.
The property is still optional, so if the decoding container doesn't decode the value (either because it was omitted or because it was null?) then we should pass that on still rather than falling back to the default.
With the exception of the separate bug fix, it's important that the only change in generator output is the addition of a default value on the memberwise initialiser rather than behavioural changes to how decoding works. Maybe we could look into seeing if the decoder defaults becomes an opt-in change that we might want to support later on, but I don't think that it should happen by default or in this PR.
Does that sound ok? Thanks for sticking with me on this one as I also try to figure out how we want this to work 😅

@liamnichols I see what you mean now. I've pushed up a revision to (hopefully) address this.


Add doc around authentication related configurations

Add doc around authentication related configurations.
@RackHD/corecommitters @WangWinson @iceiilin @heckj

:+1:

Looks great! I've added a bunch of very minor grammar modifications, other than that, thanks!

Thanks @benbp for the nice line-by-line review. I appreciate that. Perhaps consider a carrier of English teacher in China, that's a huge need for that LOL

Thanks @benbp .
Did I learn English at school ? Well , I don't remember ~ facepalm ~

Added a section regarding how to change default auth password, per suggestion by @zyoung51 in PR https://github.com/RackHD/specs/pull/39/files#r51731769

Hahaha @cgx027 I will consider that!

@WangWinson no shame needed there, he does the same service for me all the time. @VulpesArtificem is equally proficient. Alas, I am not.
BTW: :+1:

Yep, my hammer of grammar applies equal justice to all.


Add a "Group by" dropdown selector in the folder collection view

Is your feature request related to a problem? Please describe.
Given an example "scholars" folder collection with taxonomies "cohort" and "country" (grouped by Markdown frontmatter values), if I want to browse scholars by cohort, I can't easily do that in the folder view.
Describe the solution you'd like
Ideally there would be a dropdown "Group by" right next to "Sort by" in the collections list view. The selected dropdown value would then be used to group items in the list, like so:

Describe alternatives you've considered

I could search for "2019" in the global search box, but that would return any post from any collection containing that term.
I could also sort by cohort and then view scholars sequentially (and potentially change the "summary" collection config variable to show their cohort in the listing), but that creates cognitive overload.
I could split the collection up into different collections with the "filter" collection config variable, but my understanding is that this creates separate collections, which is undesired for a use case like the above.

Additional context

Excellent feature request!

@erezrokah is it possible to work on it?

Thanks @MohamedBechir, I've already assigned you to https://github.com/netlify/netlify-cms/issues/3640. Let's keep this one open for grabs 😄

As suggested, posting this potential feature for validation Multiple Filters with different categories
The idea is almost the same since the filter will be "grouped by".
Thank you @erezrokah 😄

Hi,
I would like to work on that issue.
If you have a good place to start, any advice or direction is welcome 😄
@erezrokah

Hi @KancerEzeroglu, I think we could start by configuration only groups and as a second iteration infer groups automatically.
You can mode this after https://www.netlifycms.org/docs/configuration-options/#view_filters if you think that makes sense.

Hi,
I will start to add a new configuration for groups.
In the config file, it will look like that:
view_groups:
      - label: "Date"
        field: date
      - label: 'Country'
        field: country

If you add this attribute in your config file, then we'll show a 'group by' filter.
And the user can group items as she/he wanted.
Assume you added these posts:
postA:
 date: 01.01.2020
 country: USA
postB
 date: 01.01.2020
 country: USA
postC:
 date: 01.01.2021
 country: USA
postD
 date: 01.03.2020
 country: Netherlands

When you group by Country you will see these posts as below:
--- Country: USA ---
postA
postB
postC
--- Country: Netherlands ---
postD
Whereas when you group by the date, you will see this:
--- Date: 01.01.2020 ---
postA
postB
--- Date: 01.03.2020 ---
postD
--- Date: 01.01.2021 ---
postC
As you see, this is a date group and it groups by day, not year. I don't know how can we provide a configuration for a year group. WDYT @erezrokah ?

As you see, this is a date group and it groups by day, not year. I don't know how can we provide a configuration for a year group. WDYT @erezrokah ?

Maybe we can add an optional pattern to extract the value e.g.
view_groups:
      - label: "Year"
        field: date
        pattern: "\\d{4}$"

WDYT?

@erezrokah it makes sense theoretically. I'm working on that.


Okta SAML Integration Not Working

Firezone V0.7.35
Okta
I have configured the Okta tenant and Firezone as per the documentation. When users login they get:
invalid_request unknown IdP
This looks similar to issue 1341 that is fixed in 0.74?

Thanks for the report @prsf1233 -- usually this happens due to a misconfiguration of some sort. Nothing has changed with our SAML integration in quite some time. Perhaps double-check the config ID, ACS URL, and entity ID?

Thanks for the hint, I had misspelt the config id.


.NET Framework Initialization Error

Describe the bug
FilesFullTrust.exe - .NET Framework Initialization Error
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscoreei.dll could not be loaded
Desktop (please complete the following information):

OS Version: Windows 10 21277.1000
App version: 0.23.1

Additional context
Error when open Files

Thanks for this report. It looks more like a Windows issue that a Files issue.
Are you getting the same error in any other program?
Last answer here suggests a way to fix the issue

Thanks for this report. It looks more like a Windows issue that a Files issue.
Are you getting the same error in any other program?
Last answer here suggests a way to fix the issue

Thanks again for your feedback.
Since we didn't hear from you on this topic for 4+ days, we'll assume everything is worked out and close this feedback item. If you had more feedback to provide, please re-open this and help the owners by describing the current status and any steps taken to troubleshoot this.

Thanks again for your feedback.
Since we didn't hear from you on this topic for 4+ days, we'll assume everything is worked out and close this feedback item. If you had more feedback to provide, please re-open this and help the owners by describing the current status and any steps taken to troubleshoot this.

I have the same issue. Would greatly appreciate help on this.
See error message:

The message pops up three times in a row in overlapping dialogs.
I am not receiving this message in any other programs.
Files Version <IP_ADDRESS> did not resolve the issue.
Resetting the app did not help.
I am on Windows Insider Build<PHONE_NUMBER>, but the Problem existed for a while already.
I am on Windows on Arm on a Surface Pro X.
debug.txt content from last launch:
2021-01-25 12:14:52.0375|INFO|GetClassFullName|App launched|
2021-01-25 12:14:52.5244|INFO|GetClassFullName|Drive added: C:\, Fixed|
2021-01-25 12:16:43.3654|INFO|GetClassFullName|Running on ARM: True|
mscoreei.dll exists in folder C:\Windows\Microsoft.NET\Framework64\v4.0.30319 with file version 4.8.4161.0
All users or group have at least "Read & execute" permission

I have the same issue. Would greatly appreciate help on this.
See error message:

The message pops up three times in a row in overlapping dialogs.
I am not receiving this message in any other programs.
Files Version <IP_ADDRESS> did not resolve the issue.
Resetting the app did not help.
I am on Windows Insider Build<PHONE_NUMBER>, but the Problem existed for a while already.
I am on Windows on Arm on a Surface Pro X.
debug.txt content from last launch:
2021-01-25 12:14:52.0375|INFO|GetClassFullName|App launched|
2021-01-25 12:14:52.5244|INFO|GetClassFullName|Drive added: C:\, Fixed|
2021-01-25 12:16:43.3654|INFO|GetClassFullName|Running on ARM: True|
mscoreei.dll exists in folder C:\Windows\Microsoft.NET\Framework64\v4.0.30319 with file version 4.8.4161.0
All users or group have at least "Read & execute" permission

Same issue here.

Still getting this error, on latest 2022

Try the preview version https://files.community/download/preview
You can also try running these in an admin CMD terminal then restart when there finished.
sfc /scannow
dism /online /cleanup-image /restorehealth`


elegantrl DRLAgent: cannot import name 'Arguments' from 'elegantrl.train.config'

Describe the bug
It appears that [elegantrl.train.config](https://github.com/AI4Finance-Foundation/ElegantRL/blob/master/elegantrl/train/config.py) doesn`t contain class 'Arguments'.
To Reproduce
Steps to reproduce the behavior:

Run simple script with: from finrl.agents.elegantrl.models import DRLAgent as DRLAgent_erl

Error I get
ImportError: cannot import name 'Arguments' from 'elegantrl.train.config'

Consider freezing version in requirements

Is this problem solved?

as I saw there is no specific version given for elegantRl in requirments
I'm getting the same error that Arguments class not found in config.


SPOI-12594 - Engine changes - STRAM analysis

Backend changes to engine to facilitate STRAM analysis.

Please follow http://apex.apache.org/contributing.html to open a new PR or re-open this one.


Null/empty searches?

Wanted to reach out to see if there were any options for null/empty searches? Doesn't seem possible with text searches, nor with the select searches.
Thank you in advance,
Juan

Hello @jpuerto-psc, thank you for interesting and inspirational question.
In the current implementation, hem .. the short answer is "no".
Column filters are based on input and select widgets, and not much can be easily done apart from simple matching of column values.
Mhhh ... mumble mumble ....
I do believe your request is just an example of the many occasions where, due to the specific context, a complex or custom filtering is needed.
A possible solution is suggested here:
https://github.com/morlandi/django-ajax-datatable#provide-extra-data-to-narrow-down-the-initial-queryset
I tested that technique with the use case you suggested, and added a detailed solution (and explanation) to the example project:
https://github.com/morlandi/django-ajax-datatable#18add-a-sidebar-with-custom-filters
You might want to check if, with a few adaptations, that can be applied to your code too.

Thanks for the advice @morlandi. I can definitely understand the complication with implementing this at the column header level.
I realize that as of now, the searching is entirely text based; however, it may be helpful to include some level of "symbolic" searching in the columns. For example, this particular situation could be resolved if I could do a != '' search in a column. This would also make searching more intuitive for numeric fields. Perhaps something to consider.
If there was a way to make the searching functionality overridable - I could implement this myself; however, I would really prefer not to have to fork this library and modify core functionality to do so.
Best,
Juan

I recently added the capability to search multiple values on a single columns; that is, you can type "a + b" to search "a" OR "b", as explained here:
https://github.com/morlandi/django-ajax-datatable#112filtering-multiple-values
This might be a good starting point; the relevant code can be found here:

AjaxDatatableView._filter_queryset()
filters.build_column_filter()

You can adapt it to your specific needs, or if you think of a way to express this in a generale and reusable manner, we can discuss about the feasibility to include as a new feature


The custom error addition should handle edge cases

Please add a test about a custom error handler that could be used to invalidate an error by returning nil
adding a custom error handler allow to mess up things, because people may do that in their custom handler if you dont want to support it, the mechanism of error handling should be rewritten to forbid this behavior
Originally posted by @ccoVeille in https://github.com/go-fuego/fuego/pull/320#discussion_r1899168562

Good ideas


POS tagger for tamil language

@abuvanth Thanks for raising an issue. Just like to clarify and ask what is the issue about =)

Is this a feature request?
Are you going to contribute a Tamil POS tagger model to NLTK?

If it's the latter, please take a look at https://github.com/nltk/nltk/blob/develop/CONTRIBUTING.md
Please do a pull request once it's ready and someone will review and take a look at it =)


Peek References tree not expanding/collapsing nodes on mouse click anymore

Version: 1.47.0-insider
Commit: 6c235c723cb2d8defb840f732eac620f54aa8b9d
Date: 2020-06-26T05:33:20.679Z
Electron: 8.3.3
Chrome: 80.0.3987.165
Node.js: 12.13.0
V8: 8.0.426.27-electron.0
OS: Darwin x64 19.4.0
The tree used to expand/collapse nodes on mouse click:

Same in debug hover. Moving to @joaomoreno.

Fixed in master already.


[OSS] Replace buttons with the Button component from the theme

To get more familiar with the code base, and to ensure we have the gatsby-theme-newrelic package installed correctly, lets convert the buttons to use the <Button /> component.

Moved to https://github.com/newrelic/opensource-website/issues/544


Use rollup or some other tool to flatten the dependency tree of shipped code

linkedom has quite many files in cjs and esm folders.
Requiring the library from client side especially commonjs take quite some time to resolve all the files, this could be improved by using rollup or some other bundling tool to flatten the files into single shipped file

the worker.js is the file that bundles this for you ... have you tried that? it's linkedom/worker


Create interface for electron app

Need to create more user-friendly interface template
Add visual plotter for data got from BLE

https://www.npmjs.com/package/@electron/remote
https://www.electronjs.org/docs/latest/breaking-changes


Perception object iterables and estimation should be possible from a static object

The Conflict class supplies a perception iterable for downstream or upstream GTUs. An arbitrary perceiving GTU is cached with this information, as the perception iterable needs one. This iterable itself does not use the arbitrary GTU, but supplies unaltered information and is wrapped in another iterable.
Implementation of Estimate should explicitly know whether it is anticipating from a static object or a GTU, as speed vs. speed difference becomes the relevant perceived speed.

AbstractPerceptionIterable, AbstractPerceptionReiterable, MultiLanePerceptionIterable and LaneBasedObjectIterable now have a perceiving object data type P.
DownstreamNeighborsIterable and UpstreamNeighborsIterable are now tied to Conflict as being the perceiving object.
MultiLanePerceptionIterable, LaneBasedObjectIterable, DownstreamNeighborsIterable and UpstreamNeighborsIterable might be replaced with logic more similar to what LaneStructure uses.
Estimation receives a reference object in its methods, and accounts for an appropriate speed difference, e.g. relative to perceiving GTU if its the reference, otherwise relative to zero speed for a static object such as a Conflict. This could use a unit test!
Anticipation.egoAnticipation() removed as it was not used.
Anticipation does the same, but gets different input. Parameter traveledDistance, which used to point to the distance the perceiving GTU travelled during the anticipation, has been renamed with traveledDistanceReference, which will be zero in case of a static reference.
Input parameter perceivingGtu was removed from AbstractPerceptionReiterable.perceive() as this is available in implementation classes.
Perception iterables created within Conflict now provide the correct object, being either the conflict itself, or a perceiving GTU.
ConflictGtu removed, it extended HeadwayGtuReal but only added access to the underlying GTU, which HeadwayGtuReal now provides.
HeadwayGtuType.createHeadwayGtu() has a default implementation which now accounts for perceiving GTU length, or Conflict length. In other cases zero length is assumed. Note that GTU's and static objects do not share any super class that can provide length. Perhaps there should be one. Currently OtsLocatable is used as class to allow either reference object type.

As part of issue #100 and its resulting inheritance structure, relevant static objects and relevant GTU's now are both subclasses of LaneBasedObject. This is used in HeadwayGtuType.createHeadwayGtu() and Estimation as the bounding type for reference objects.

Isolated NavigatingIterable from LaneStructure so it can be used stand-alone with SimpleLaneRecord outside of the LaneStructure.
Removed AbstractPerceptionIterable and its sub-classes DownstreamNeighborsIterable, UpstreamNeighborsIterable and LaneBasedObjectIterable. The class Conflict now uses NavigatingIterable to find relevant GTUs and objects upstream and downstream.

EstimationTest tests None and Factor estimation in the case of both a static and dynamic (ego GTU) reference.


Confusing validate schema behavior

🐛 Bug report
Current Behavior
validateYupSchema casts empty strings to undefined. Moreover, it does so inconsistently (#1125, #1520)
Expected behavior
I have a yup schema which treats empty strings and undefined values differently. I had to debug and found this out. So technically validationSchema prop is not strictly yup schema. Why is that so? Current workaround is to use your own validateYupSchema but without this casting.

Reproducible example

Suggested solution(s)
I think validateYupSchema should pass values to yup without alterations. Yup is totally capable of dealing with empty strings, undefined values and nulls on its own. Or at least this unexpected behavior should be mentioned in docs.

Additional context

Your environment

Software
Version(s)

Formik
^2.0.1-rc.12

React

TypeScript

Browser

npm/Yarn

Operating System

Hey @doomsower can you try with the latest stable release, and if problem still persists, revert back so that we can help.
Closing for now

@maddhruv it does and is driving me crazy. Just spent 2 hrs trying to figure out why is yup's schema saying a field that should be .defined() is invalid when in the same time I get that field as empty string in validate={console.log}.
It's because of prepareDataForValidation call in 1073:
https://github.com/formium/formik/blob/c45baba225d0e15b345021878b9af541c31d5a3b/packages/formik/src/Formik.tsx#L1067-L1078
which indeed casts empty strings to undefined:
https://github.com/formium/formik/blob/c45baba225d0e15b345021878b9af541c31d5a3b/packages/formik/src/Formik.tsx#L1083-L1106
This prepareDataForValidation function AFAIK is used only for yup validation, which is  SOOOOO wrong since yup can actually
distinguish between '' and undefined using .required() or .defined() - especially for TypeScript users.

I've raised a PR fixing the same - https://github.com/formium/formik/pull/2902


Add a header with manifest tag to pull and push

Signed-off-by: Yinon Avraham<EMAIL_ADDRESS>Add an optional request header Docker-Manifest-Tag to all requests in the push and pull operations.
This request header, when added, shall include the tag value of the image being pushed / pulled.
For example, when pushing or pulling image foo:1.2, the following header will be added to all requests:
Docker-Manifest-Tag: 1.2

Registries can then use this header, if it exists, for various use cases. For example:

In the /v2/ (ping) request - to identify the specific requested tag and by that limit the authorization request (auth challenge), making the authorization grant specific to that tag
In the .../blobs/... requests - optimize locating blobs while they are being pushed or pulled. This is useful in registry implementations which keep a link between tags and their blobs

Because the distribution spec leaves authentication and authorization out of scope (which IMHO is a good decision), and because this information is helpful in several use cases, the suggestion here is to add it as a new request header.
For tag based authorization, having the header with the relevant tag when pushing or pulling a manifest or blob by digest can be very helpful. It gives the registry a hint on the context which points it on which tag to check, which leads the registry to the actual manifest to see if the requested blob is referenced. The auth token only serves as a mean for carrying the granted permissions. The header is used to easily locate the tag's manifest. Without it, the registry needs to get all tagged manifests of the named image, filter only those referencing the blob, and check each one to find the first that the auth token grants permissions on.

Some stream of consciousness feedback:

the docker headers were kept for legacy reasons, any new headers we add should be OCI headers
auth specifications in OCI is being planned, I'll be submitting a new working group proposal for that, hopefully this week
on the /v2 API, you don't know which repository is being accessed if you only have a tag
registries don't require the ping of the /v2 API, docker does this since it builds the auth headers manually, but you can skip that and get the auth header on your request directly to the repo, possibly skipping a round trip if anonymous access is permitted
some images are pushed/pulled by digest
multi platform images require recursion to search all child manifests
multiple tags can be pushed for the same digest in the same build command
on push, the blobs are pushed before the manifest, so there's nothing to verify
the user can lie about which tag is being pushed for a blob, then use it in a differently tagged manifest

@sudo-bmitch thanks for the feedback.

the docker headers were kept for legacy reasons, any new headers we add should be OCI headers

Understood. The goal with the suggested header name was to be aligned with similar existing headers like Docker-Content-Digest. But any better suggestion is of course welcome.

on the /v2 API, you don't know which repository is being accessed if you only have a tag

Right, mentioning the /v2/ endpoint was slightly wrong and biased by the actual implementation. I will rephrase -
The added section in the spec doesn't mention a specific endpoint, but refers to all requests in the push / pull. In the existing implementation this includes the GET /token request issued by the client following the auth challenge in the /v2/ response. This followup request does include the repository in the scope. So the goal was to make it accompany that request as well. But nevertheless, this is only one part of the goal of adding this header.
Since there is going to be a work group on adding auth to the spec, I think it is good to consider including the tag in addition to the repository and actions.

registries don't require the ping of the /v2 API ...

This is one of the reasons the header is added to each request, not relying on the auth. Anonymous access can be viewed at the same as any other principal. A repository owner might want to open specific tags for anonymous access, but require auth on other tags. Having the header on each request, regardless of the auth, supports it.

some images are pushed/pulled by digest

True for pull, not sure about push. But anyway - pulling (or pushing) images by digest is a different story, not covered by the suggestion in this PR. I did start to think about it, but decided to not mix the two for now and keep this PR focused on tags.

multi platform images require recursion to search all child manifests

True, but knowing which manifest list to start with by its tag is a very big hint which can greatly reduce the search area. The common recursion level is 2 (manifest list -> manifests) and the number of leaf manifests is usually small (e.g. number of supported platforms).

multiple tags can be pushed for the same digest in the same build command

Good point. As much as I saw, the reference implementation (moby) takes the tags one-by-one and relies on the HEAD request for checking whether the blob already exists. But if there are other implementations that do it otherwise, I think it is OK to define that the header can have multiple values. But I'm not sure it is really required for now. If needed - it can probably be added later on.

on push, the blobs are pushed before the manifest, so there's nothing to verify

You can verify that the authenticated principal is authorized to push the specific tag and fail the upload of the blobs earlier in the process, instead of only when the manifest is uploaded.

the user can lie about which tag is being pushed for a blob, then use it in a differently tagged manifest

Registries must take such "lies" under consideration. The suggestion says this is not a hard requirement - clients SHOULD send it, registries MAY use it. This header acts as a hint, enabling the registry to improve some actions based on it.

@sudo-bmitch thanks for the feedback.

the docker headers were kept for legacy reasons, any new headers we add should be OCI headers

Understood. The goal with the suggested header name was to be aligned with similar existing headers like Docker-Content-Digest. But any better suggestion is of course welcome.

Here's some context from when the spec was being written: https://github.com/opencontainers/distribution-spec/issues/26
Looking back at the suggested use cases:

In the /v2/ (ping) request - to identify the specific requested tag and by that limit the authorization request (auth challenge), making the authorization grant specific to that tag

Scoping access to tags instead of repos is certainly something that I've seen interest in. But I don't think depending on user hints is a good way to securely implement it. Maybe I'm missing something.

In the .../blobs/... requests - optimize locating blobs while they are being pushed or pulled. This is useful in registry implementations which keep a link between tags and their blobs

Because of how blobs are reused between manifests, and manifests can have multiple tags, this feels like the wrong place to create that relationship, especially since images sharing layers may be pushed long after the blobs they are sharing were first pushed. But I spend most of my time on the client side, so I want leave space for registry operators to weigh in.
For myself, I don't see a clear issue being solved by this that wouldn't be better solved another way. So it may help to work through what problems this solves, and why this is the best way to solve those problems.

@sudo-bmitch thanks for the link regarding the header naming. As I understand, the suggestion is to name this field: OCI-Manifest-Tag, right? Please correct me if I misunderstood. I saw PR #206 was merged, but the spec in main branch does not include it, so it is not very clear...
Let's put the discussion on /v2/ aside, since it is not the main topic here. It is not mentioned explicitly in the suggested paragraph.
The suggestion is not to rely on the manifest tag in the header for scoping the request, as the header by itself cannot be trusted. The goal of the header is a hint for the registry on the context of the request, i.e. which manifest to check and verify this blob belongs to it.
Today, when a registry receives a request for blob, and the request has authorization which is scoped to specific image repositories and tags (because it is explicit in the token, or implied by other means - specific to the auth provider), in order for the registry to check the request can access the requested blob, it needs to:

Optionally try to extract the permitted tags from the request's authorization, either by parsing the token (which is not something I would expect the registry to do), or by querying the authorization service - which probably requires a dedicated API. Anyway, the result of this extraction can be a list of tags.
Must iterate over all (or just the list from step 1) the repository image tags, read their manifests' config and find the first one that both - (a) the request is authorized on, and (b) references the requested blob.

Having the tag added to the context of the request using a header gives a hint to the registry where to look. If the header is missing - nothing changed, this is the same as before (backward compatible). But if the header exists, the registry can check only that specific tag, avoiding the need to scan all other tags.
If the client lies and hints with a wrong tag there are several options:

the request is not authorized on the hinted tag - the registry rejects the request
the request is authorized on the hinted tag, but the tag doesn't reference this blob - the registry rejects the request
the request is authorized on the hinted tag, and the tag references this blob - the registry serves the request. And this is ok.

Except for tag based authorization, there are other viable use cases for adding this header. Another example is registries which collect statistics on downloads and uploads can use this quite simply in order to give more fine-grained reports such as how many bytes downloaded/uploaded per tag.

X-ref: https://github.com/opencontainers/distribution-spec/issues/328

@sajayantony , @sudo-bmitch ,
I saw this PR is listed in the agenda items of the OCI weekly discussion on Oct. 27th 2022, but I didn't find any notes.
How can we proceed and push this proposal forward?

@sudo-bmitch I started to fix the PR based on the comments, but I have the following dilemma -
The suggestion is to use a header named OCI-Ref.
BUT- In the spec, the term reference usually refers to the tag or digest, while in #328 the suggestion is to put the full named image reference in the header value, i.e. : <registry>/<name><reference> (where <reference> is either :<tag> or @<digest>).
To resolve that and make the header name more explicit, I suggest to use: OCI-Named-Ref.
Although it still leaves it unclear whether the registry is part of the name or not, I think it is good enough and OCI-Full-Named-Ref seems an overkill...

@yinonavraham That hits on https://github.com/opencontainers/distribution-spec/issues/216. We've been rather inconsistent and need to clean that up. I would lean towards reference being the full name (e.g. registry/repo:tag) and coming up with a new name for a tag or descriptor.

@sudo-bmitch how can we push this forward?

We need to get some reviews from other mods, but I think most of the focus is on getting a 1.1 release out right now.


Add a Regression Test For Scenario Improved By Private Dependencies

The basic setup is this - Suppose that three files define four types:
// File 1
struct A {}

// File 2
struct B { let x: A }
struct C { }

// File 3
struct D { let x: C }

If type 'A' is perturbed, we could expect that File 2 would rebuild
because B has a member of type A. What we don't expect is for File 3 to
rebuild, but thanks to cascading edges that is precisely that happens!
This is because the member x in File 3 creates a cascading edge to File
2, and that edge is traversed while evaluating the cascading edge from
File 2 to File 1. With private dependencies, the expected rebuild
behavior is restored. Commit a regression test to this effect.

@swift-ci smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci smoke test

⛵


BSX Asset page

Is your feature request related to a problem?
Since BSX on Rococo / Kusama will support Kusama as the currency we will need new /bsx/assets page
Describe the solution you would like
The solution is pretty straightforward:

[ ] make a table - asset, balance, actions
[ ] list tokens that are available to the user
[ ] make it settable to the chain.

Where to get the data?
Best to start with the BalanceList.tsx ;D
Describe alternatives you have considered
~
Screeenshots
I really like the implementation of @maht0rz

Link
Are there opened related issues?
No response

We already have one, but deserves better than current bulky design
https://beta.kodadot.xyz/bsx/assets

We already have one, but deserves better than current bulky design
https://beta.kodadot.xyz/bsx/assets

we already have one, but it is only design :D

Continue to

#4119


feature #136 : Log scale switch for cumulative charts

Added Logarithmic switch on right pane. This is available only for Cumulative charts and not for daily charts.
Added SI format for numbers on scale (Although I hope it never reaches there, numbers fall out beyond 9999 on Y-axis without this)
Fixes #136

@imjaypatel12 Looks great, but the UI breaks on phone.

@imjaypatel12 Looks great, but the UI breaks on phone. Maybe, shorten it to just Log.

PS: @jeremyphilemon I think we might have to remove the toggle and instead make the text clickable.

Thanks for reporting it. It's fixed now.

This is weird now... im on it. I do not know whether I should create a new ticket for it or not. I am going to push this change in the same PR. Let me know if this doesn't align with your defined procedures.

Hey @imjaypatel12, not sure why but the commit history and diff of this PR seems screwed up. Any way you can rebase --> force-push, or open a new PR?

@shuklaayush I noticed that too, but I just don't seem to understand why is it showing all these intermediate commits as part of the PR. All I did was pull-rebase to resolve conflicts. Even the current diff of 2 branches from new PR page shows only 6 commits -- all of which are mine.
https://github.com/covid19india/covid19india-react/compare/master...imjaypatel12:issues/136?expand=1

Anyway, I am going to rebase again to resolve conflicts and will see if that resolves this.

@jeremyphilemon Any idea why this might be the case?

@shuklaayush alright, I did the merge instead of rebase and the issue is magically disappeared, shows only 3 files changed now :). But, the deployment failed :/ What the heck, i just accepted your changes in merge, and its working fine on local too.

@imjaypatel12 That might be because of the compilation warning. Try to fix it and push an update.

@imjaypatel12 Found a bug. I think you forgot to accommodate for the lack of log scale in the daily trend charts. I guess you'll need to add a check for the yScale based on the index as well.

@shuklaayush oh no, that’s totally intentional (in fact, had to write some special cases to turn that damn switch off and not apply log scale logic for daily charts). I can't wrap my head around using log scale for daily counts, I think log scales are used only for exponential growth charts.
P.S. I should have thought about better word instead of cumulative in the PR title lol.

@imjaypatel12 That's exactly what I'm saying. You've disabled the switch, but the daily trend graphs are still plotted on a log scale (which doesn't make sense).

Woah! Damn you’ve got some good eyes :D Let me fix that


Update requirements.txt to fix dependency issues

Replaced bs4 with beautifulsoup4 and lxml to resolve build errors.
Unified pymongo version to 3.12.1 for consistency between api and parser.
Ensured compatibility of dependencies across the project.

Update requirements.txt to fix dependency issues

Replaced bs4 with beautifulsoup4 and lxml to resolve build errors.
Unified pymongo version to 3.12.1 for consistency between api and parser.
Ensured compatibility of dependencies across the project.


Disable rack-attack throttle to run performance test

I'm creating some specs to validate whether my throttle rules are doing well, however, I want to create another spec right below these ones to evaluate performance. The latter one is written below:
    it "performs at least 100 votes per second" do
      expect {
        post "/submit"
      }.to perform_at_least(100).ips
    end

Is there some way to temporarily disable rack-attack, only for this specific test?
PS: I've already tried to add the line Rack::Attack.cache.store.clear before posting the request, but it returns an error.

Is there some way to temporarily disable rack-attack, only for this specific test?

You can use Rack::Attack.enabled = false for >= 6.2.0.


Community users who hit the usage limit should see a dismissable upsell to drive the user to Cody Pro

We are not moving the Cody Manage and onboarding from dotcom to SSC. This is already solved in the current version.


Receiving error on mac: /usr/local/bin/t: Read-only application cannot POST.

Have the application set up for full access and ability to DM.

Changes to the application permission model will only reflect in access tokens obtained after the permission model change is saved. You will need to re-negotiate existing access tokens to alter the permission level associated with each of your application's users.

Run t authorize again


Change of Schedule/Timeslot Behaviour

Expected behaviour:
The opening schedule is set to the opening time for the delivery and pick up options. The website displays the timeslots accounting for the opening time + the lead time .
Example: The time is 4pm, delivery starts at 4pm but there is a 60 minute lead time for delivery. The website should show the first available timeslot to be 5pm, and should display that delivery starts at 4pm.
Actual behaviour:
The timeslots do not take into account the lead time, allowing people to order at 3.55pm and expect their delivery at 4pm, for example.
Reproduce steps:
I think this only started to occur on the new update, after the time schedule feature was updated.
Version:
v3.0.4-beta.28
Additional Information:
(Additional information, if any)

Images requested: https://imgur.com/a/rTnDiXV

@tastyigniter/core-team any one else able to replicate this? I’m not seeing it.

@sampoyigi just bumping this to see if you can recreate?


Infinity Docs Are Offline

System Info
Irrelevant *
Information

[ ] Docker
[ ] The CLI directly via pip

Tasks

[X] An officially supported command
[ ] My own modifications

Reproduction

Open https://michaelfeil.eu/infinity/

Expected behavior
Docs Should open.
Currently it shows
404
There isn't a GitHub Pages site here.
If you're trying to publish one, read the full documentation to learn how to set up GitHub Pages for your repository, organization, or user account.

https://michaelfeil.gothub.io/infinity

Thank You!


[Question] Can I only use cert to do checking: raising exception when valid cert not found without creating one.

New Issue Checklist

[X] Updated fastlane to the latest version
[X] I have read the Contribution Guidelines

Issue Description
What I want to do is only using cert to check if I have valid cert in the machine.
If the machine does't have any, raise an exception and exit. Without creating a new one.
I did some search but didn't find a command to do so.
Environment
✅ fastlane environment ✅
Stack

Key
Value

OS
10.12.4

Ruby
2.2.4

Bundler?
false

Git
git version 2.11.0 (Apple Git-81)

Installation Source
~/.fastlane/bin/bundle/bin/fastlane

Host
Mac OS X 10.12.4 (16E195)

Ruby Lib Dir
~/.fastlane/bin/bundle/lib

OpenSSL Version
OpenSSL 1.0.2g  1 Mar 2016

Is contained
true

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
8.3

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL
en_US.UTF-8
✅

LANGUAGE
en_US.UTF-8
✅

fastlane files:
`./fastlane/Fastfile`
# More documentation about how to customize your build
# can be found here:
# https://docs.fastlane.tools

default_platform :ios

lane :beta do |options|

  increment_build_number(build_number: options[:build_number])

#  cert(
#    output_path: "./fastlane/beta"
#  )
#  sigh(
#    output_path: "./fastlane/beta",
#    adhoc: true
#  )

  gym(
    output_directory: "./fastlane/beta",
    output_name: "Wedding-adhoc.ipa",
    scheme: "Wedding-Release",
    export_method: "ad-hoc"
  )

  crashlytics(
    api_token: "edabc3b306e76721cd71a893109d059a20c86ed5",
    build_secret: "67319de84acb9b10e25a14ae0839750076d823bb72f43878fbeab06807d32cae",
    emails<EMAIL_ADDRESS>  )

end

No Appfile found
fastlane gems

Gem
Version
Update-Status

fastlane
2.26.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

CFPropertyList
2.3.5

activesupport
<IP_ADDRESS>

addressable
2.5.0

babosa
1.0.2

bigdecimal
1.2.6

bundler
1.14.3

claide
1.0.1

cocoapods
1.2.0

cocoapods-core
1.2.0

cocoapods-deintegrate
1.0.1

cocoapods-downloader
1.1.3

cocoapods-plugins
1.0.0

cocoapods-search
1.0.0

cocoapods-stats
1.0.0

cocoapods-trunk
1.1.2

cocoapods-try
1.1.0

colored
1.2

commander
4.4.3

commander-fastlane
4.4.4

domain_name
0.5.20161129

dotenv
2.2.0

escape
0.0.4

excon
0.54.0

faraday
0.11.0

faraday-cookie_jar
0.0.6

faraday_middleware
<IP_ADDRESS>

fastimage
2.0.1

fourflusher
2.0.1

fuzzy_match
2.0.4

gh_inspector
1.0.3

google-api-client
0.9.26

googleauth
0.5.1

highline
1.7.8

http-cookie
1.0.3

httpclient
2.8.3

hurley
0.2

i18n
0.7.0

io-console
0.4.3

json
1.8.1

jwt
1.5.6

libxml-ruby
2.9.0

little-plugger
1.1.4

logging
2.1.0

memoist
0.15.0

mime-types
3.1

mime-types-data
3.2016.0521

mini_magick
4.5.1

minitest
5.4.3

molinillo
0.5.6

multi_json
1.12.1

multi_xml
0.6.0

multipart-post
2.0.0

nanaimo
0.2.3

nap
1.1.0

netrc
0.7.8

nokogiri
1.5.6

os
0.9.6

plist
3.2.0

power_assert
0.2.2

psych
2.0.8

public_suffix
2.0.5

rake
10.4.2

rdoc
4.2.0

representable
2.3.0

retriable
2.1.0

rouge
1.11.1

ruby-macho
0.2.6

rubygems-update
2.5.2

rubyzip
1.2.0

security
0.1.3

signet
0.7.3

slack-notifier
1.5.1

sqlite3
1.3.13

terminal-notifier
1.7.1

terminal-table
1.7.3

test-unit
3.0.8

thread_safe
0.3.5

tty-screen
0.5.0

tzinfo
1.2.2

uber
0.0.15

unf
0.1.4

unf_ext
<IP_ADDRESS>

unicode-display_width
1.1.3

word_wrap
1.0.0

xcodeproj
1.4.2

xcpretty
0.2.4

xcpretty-travis-formatter
0.0.4

generated on: 2017-04-06

@ShaneQi Hi 👋
Thanks for your question.
cert can not do that right now, it creates new one if no certificates found in your local machine.

@nafu Thanks for the response.


PP-6688 Change vat_number & company number tasks path

WHAT

Moves vat-number & company-number paths out of /vat-number-company-number/*** path as these are now independent tasks

Nice work 👍


Some doc fixes for Flask-Restful

Please reformat some of your changes to wrap at the 80 character column so the formatting of the document source stays consistent with what's there already. You can typically configure your editor to show this. For example if you use Sublime Text, select "View" -> "Ruler" -> "80" from the menu.

OK I think that's everything I can think of.  Thanks so much for taking time to help fix this up!

my please...can you help me with one thing: how can i add reference to Nested to the class docs? should i do: :py:class:Nested?
also how can i view the changes for .rst files in the format as the flask-restful doc....i can open them in the browser?

Use:
:class:`~fields.Nested`

You can build the docs with the command:
make doc

or alternatively:
make read

which will build the docs, then open them in your browser. virtualenv is required for this. I haven't tested it recently on windows, but it should work.

it worked like a charm :+1:

Changes Unknown when pulling a218e1e5d5a76673dedac07a7293b06258133463 on ueg1990:doc-fixes into ** on flask-restful:master**.

Thanks again! :+1:

hey josh, i had a quick question. if i want to test changes in the code for flask-restful....how can i test them? do i have to do something like: "python setup.py develop" or "make develop" and then import it in a test file?

Check out the testing page in the docs


Open CX not simulated correctly

Informations

Qiskit Aer version: 0.6.0
Python version: 3.7.5
Operating system: macOS Catalina , 10.15.4

What is the current behavior?
The CX gate with an open-control does not get simulated correctly. This is a follow-up on Qiskit/qiskit-terra#4180 where this has first been discovered.
The output state of
q_0: ──o──
     ┌─┴─┐
q_1: ┤ X ├
     └───┘

should be |10> (in Qiskit endianess) but the QASM and statevector simulator both produce |00>. The quantum_info.Statevector object however computes the correct result.
This might be a gate-naming issue, since the CX gate is called 'cx' both for open and closed controls. The same problem occurs for the CCX gate.
Steps to reproduce the problem
Aer's simulators:
>>> from qiskit import Aer, QuantumCircuit, execute
>>> open_cx = QuantumCircuit(2)
>>> open_cx.cx(0, 1, ctrl_state='0')
>>> open_cx.draw()
q_0: ──o──
     ┌─┴─┐
q_1: ┤ X ├
     └───┘
>>> sv = execute(open_cx, Aer.get_backend('statevector_simulator')).result().get_statevector()
>>> sv
array([1.+0.j, 0.+0.j, 0.+0.j, 0.+0.j])   # expect [0 0 1 0]
>>> open_cx.measure_all()
>>> counts = execute(open_cx, Aer.get_backend('qasm_simulator')).result().get_counts()
>>> counts
{'00': 1024}    # expect '10'

Statevector object from quantum info:
>>> from qiskit.quantum_info import Statevector
>>> sv = Statevector.from_label('00').evolve(open_cx)
>>> sv
Statevector([0.+0.j, 0.+0.j, 1.+0.j, 0.+0.j],    # as expected
            dims=(2, 2))

What is the expected behavior?
Produce |10>.
Suggested solutions
Check the ctrl_state upon simulation for the gate names 'cx' and 'ccx'. But I haven't worked with Aer before so maybe this is also completely wrong!

This is changing the qobj spec for "cx" which is not a parameterized gate. If you transpile and assemble for a backend that only supposed "cx" this is the resulting qobj from your example:
qobj = assemble(transpile(open_cx, Aer.get_backend("qasm_simulator")))
qobj.experiments[0].instructions
[QasmQobjInstruction(name='cx', qubits=[0, 1])]

An open-controlled-X gate should be compiled to x q0; cx q0, q1; x q0 for correct execution on a backend.


(ci) Initial implementation of GitLab CI

The tests largely use lab with this configuration https://github.com/zaquestion/lab/blob/master/testdata/lab.hcl

The tests failing on gitlab may have to do with these steps missing from CI https://github.com/zaquestion/lab/blob/master/.travis.yml#L23-L29
I should have some time to look closer later this week. Unfortunately until Thurs, I'm "enjoying" my first week oncall at the day job.

I take it back 401 {message: 401 Unauthorized} isn't related to the ssh config, it's the test binary picking up the CI credentials with it's "automatic CI config" mode. Hmmm, need to figure out a way to tell lab to use the correct creds when running in it's own pipeline. 😆


Question: Title bar command area customization

Hi,
I have been using WinAppSdk in 1.0.0 version so far. To workaround titlebar issues I have created custom control with command buttons (minimize, maximize, close) that was set as title bar and it worked like a charm as it covered native command bar
It looked like that:

After upgrading WinAppSdk to 1.0.3 version where bugfixes for titlebar were implemeted, that custom title bar control no longer cover native command bar and it looks like this:

You can see that it's darker as grey background of native command bar overlaps.
Command buttons that were part of custom control are no longer clickable (hover also doesn't work) when SetTitleBar is used on that control.
On top of that this is not reversable. I went back to WinAppSdk 1.0.0 with all nuget cache clearing etc. and I can still see all those changes from 1.0.3 version. My colleague didn't even upgrade to 1.0.3, but run other app that was using that version and all those changes were imposed on our app.
So I have 3 questions based on that:

Is it possible to customize native command bar and if yes, how to do that? I would like to change color and size of command buttons to match it with my custom bar, as currently it look like this;

Is it possible to have some property for MainWindow class that would allow for titlebar to work like in 1.0.0 version?

Most important question: Why this change is not reversible? And why running another application with newer version can change behaviour of mine? (I guess that some common OS .xaml files were changed)

Best regards
Bartek

1 . Is it possible to customize native command bar and if yes, how to do that?

You can copy and update the style (in App.xaml)

1 . Is it possible to customize native command bar and if yes, how to do that?

You can copy and update the style (in App.xaml)

I just uploaded a basic test sample : WinUI3_CustomCaption
where I updated a few values (with a Manifest on Windows 10 21 H1, for the layered window)
which seems to work fine on my OS


Flask based API

follow up on https://github.com/cmu-delphi/delphi-epidata/pull/350 with the branch in this repo for CI purposes.
based on #337
closes #178 and closes #177
proof of concept that we could also use Python for the API and thus get rid of PHP for hosting the API. The public interface remains the same but allows way more flexibility if we want to. Moreover, it is python thus we can unit test/lint/format it properly.
There is also a Dockerfile that will create a docker image to run it.
for the 414 failing unit test, see also https://github.com/benoitc/gunicorn/issues/2487

I created https://github.com/cmu-delphi/delphi-epidata-regression which is a repo for:

querying the access logs in ElasticSearch to find api requests
creating a Postman collection out of the results
running the collection against the new api and does some basic checks on them to see if they work

I created https://github.com/cmu-delphi/delphi-epidata-regression which is a repo for:

querying the access logs in ElasticSearch to find api requests
creating a Postman collection out of the results
running the collection against the new api and does some basic checks on them to see if they work

I added a bunch of unit tests, a simple endpoint one and more for other modules (such as extract_strings)
Moreover, the CI is now using pytest for running the tests

I added a bunch of unit tests, a simple endpoint one and more for other modules (such as extract_strings)
Moreover, the CI is now using pytest for running the tests

start setting up a repo for the scalability testing based https://locust.io
-> https://github.com/cmu-delphi/delphi-epidata-testing


docs: adds OR filter sample

@kolea2  I think we should discuss a nested OR query in a follow-up PR. WDYT?


Fervo Project Cape updates

https://github.com/NREL/GEOPHIRES-X/issues/288

Meant to create this as a PR into my own fork, closing in favor of https://github.com/softwareengineerprogrammer/GEOPHIRES-X/pull/36


Shared memory for H(curl) PA

This PR uses shared memory to mitigate CUDA "out of memory" failures for several H(curl) PA kernels. Shared memory (smem) is used rather than stack frame memory, for limited orders (for very high order the compiler would fail due to excessive shared memory), so there are switches between the new smem kernels and the old ones depending on the order. This allows successful builds, although the old kernels run out of memory at run time more easily than the smem kernels. Also, the smem kernels do not run correctly on CPU, so there is logic to ensure they are called only when running on device.
A new way of using unit tests on device is introduced. The unit tests now include a serial test (executable cunit_tests) with "cuda" device, which runs all test cases with tag CUDA and without tag PARALLEL. The CUDA tag is now applied to some H(curl) unit tests, so that the new smem kernels are tested on device, whereas the old kernels are still tested by the standard serial unit tests on CPU.

PR
Author
Editor
Reviewers
Assignment
Approval
Merge

#1584
@dylan-copeland
@tzanio
@stefanhenneking + @camierjs + @jandrej
07/25/20
⌛due 08/08/20
⌛due 08/15/20

Note that commit c71428a62324124559e0bb832295a3da0e566936 increased the number of registers for SmemPACurlCurlApply3D from 64 to 72, did not change smem or cmem, and had a small effect (about 1 or 2% increase) on the shared_efficiency reported by nvprof. Thus the changes had negligible effect on GPU performance, and it seems there are some complicated issues involved in optimizing (possibly bank conflicts), which have not been addressed. At least this commit makes the code a bit simpler and eliminates one loop over the components.

The makefile cunit_tests executable should be disabled if mfem was not compiled with cuda instead of handling the logic in the executable.

Note that I added the CUDA flag only to some H(curl) tests, as a minimal change in this PR to introduce the new unit testing. Please feel free to suggest other tests to tag with CUDA.

I've got errors with the Unit tests [ cunit_tests ... ]: FAILED  (33.07s 204516kB).
Not sure it's related to this: test_linear_fes.cpp, test_operatorjacobismoother.cpp & test_datacollection.cpp.

AppVeyor is failing in a Visual Studio build. Can someone interpret the error message?

1675  C:\projects\mfem\fem\bilininteg_hcurl.cpp(393): note: failure was caused by a read of a variable outside its lifetime
1676  C:\projects\mfem\fem\bilininteg_hcurl.cpp(393): note: see usage of 'this'
1677  C:\projects\mfem\fem\bilininteg_hcurl.cpp(4628): note: see reference to function template instantiation 'void mfem::SmemPAHcurlMassAssembleDiagonal3D<0,0>(const int,const int,const int,const mfem::Array<double> &,const mfem::Array<double> &,const mfem::Vector &,mfem::Vector &)' being compiled
1678C:\projects\mfem\fem\bilininteg_hcurl.cpp(393): error C2148: total size of array must not exceed 0x7fffffff bytes [C:\projects\mfem\build_parallel\mfem.vcxproj]
1679  bilininteg_hdiv.cpp

@jandrej Visual Studio's warning that an "array" size is too large is not very specific. This function has more than 1 array. Do you think this means a shared memory array is too large? I think the sizes are comparable to other shared memory kernels.

0x7fffffff is the 32bit limit, there must be something wrong in the declaration of SmemPAHcurlMassAssembleDiagonal3D or in the passed variables to the MFEM_FORALL_3D(e, NE, Q1D, Q1D, Q1D, on line 393.

Compilers can give more information when the MFEM_FORALL_3D is replaced with a regular for (int e=0; e<NE; ++e), but I don't have VS setup to try the build. I could commit that change temporarily to see the error message from AppVeyor, then undo it.

@dylan-copeland, the issue with VS maybe related to the fact that the arrays use dimensions defined outside the lambda -- you can try moving those constexpr definitions inside the lambdas.

@stefanhenneking Since you asked about the performance impact of MFEM_SYNC_THREAD, I tested ex3p with this branch and master to compare timings of the overall assembly and solution (steps 11, 12, 13 in ex3p). For the 3D test
srun -n4 -p pdebug ./ex3p -m ../data/beam-hex.mesh -pa -d cuda
on ray, pacurlsmem took 0.14 s, and master took 0.21 s. There are algorithmic differences in the old kernels and shared memory kernels which must account for the faster times with shared memory. This does not show how much time the MFEM_SYNC_THREAD takes, but at least we can conclude that it is not a problem.

This PR is past the approval date. Do any reviewers see any issues to resolve before approving? It seems to be ready, except that PR #1620 should be merged first.

This PR is past the approval date. Do any reviewers see any issues to resolve before approving? It seems to be ready, except that PR #1620 should be merged first.

@camierjs Were the failed unit tests that you mentioned addressed somehow? I couldn't reproduce them (everything was looking okay on Ray).

Note that the last merge from master includes new code added to support matrix coefficients in the shared memory H(curl) kernels.

This implies we have to review again correct?

This implies we have to review again, right?

@jandrej Yes, there were a few related PRs being reviewed simultaneously, and this is not the first to be merged. The changes for coefficient support are relatively small.

Can you please resolve the merge conflicts?

The last commit merges master into this branch and extends the new features to include general coefficient support in the shared memory kernels.

Merged in next for testing...


Modularise

Part of the modularisation refactor.
Now builds on types defined in GeodesicBase.jl.

Still needs linking with GeodesicBase.jl


Minimize OpenGL allocations

Partially solves #31

So far the changes minimized the number of allocations by 2 per each MainThreadLoop#Execute, but:

they look ugly
is it not enough - still a lot of allocation takes place because of extensive use of func literals passed to MainThreadLoop#Execute

The golang 1.14 will be released soon with better escape analysis. Maybe wait with merging till new release and verify it those changes are really needed.

Go 1.14 does not improve anything. For now we have 2 allocations per each GL call.

Number of allocations downed to zero. Unfortunately was added

Right the biggest problem is huge synchronization impact. It takes few microseconds to execute empty job in a MainThreadloop.

Better optimization was done by PR: https://github.com/jacekolszak/pixiq/pull/87/
Closing this one.


Feature/aprimo integration

Current PR provides an integration with Aprimo, a Digital Asset Management platform, for Umbraco CMS versions 10.3+, providing a custom media picker used as a property editor, a value converter with a strongly typed model to render the selected asset.
A video demonstration can be viewed here. As Aprimo does not support Firefox and Internet Explorer, my demo toggles between Firefox and Edge to provide a behavioral insight into working with Aprimo Cloud.
An editor can manage DAM assets in two ways:

Using the Aprimo API and picking a media item from property editor list.
Using the Content Selector and selecting the asset directly from Aprimo Cloud.

For handling authorization, I am using the Authorization Code Flow with Proof Key for Code Exchange (PKCE), by generating a code verifier and a code challenge and store them into the Umbraco database.
The code challenge will be sent with the first request for authorization and the Aprimo Authorization Server saves it. With the received code the code verifier will be sent in the second request to retrieve the access token and the refresh token.
The scopes used are api and offline_access, meaning that we are receiving a refresh token with the access token, and use it to renew the access token in case a 401 Unauthorized code is received. This is why in several places I check the value of the IsAuthorized flag, and request the server to renew the access token.

Additional changes included in the PR based on feedback and demos:

allow users to choose the desired workflow for picking content: using the Aprimo Content Selector or the Content API. To do so, the Use Content Selector option from the data type configuration is to be used. If Use content selector option if true, then the property editor overlay will not be shown, the Add will open the Content selector directly. If false, then you will be able to retrieve the media assets through the API, and filter them by a search term or go to different pages.
authorization process is detached from the OAuthProxy and it is self hosted, exposing a controller endpoint (_https://localhost:44324/umbraco/api/authorization/oauth_) for handling the response from the Aprimo Authorization Server.
If the authorization code is received, I will request the access tokens and then inject through ContentResult JavaScript code that sends a message to the parent window.
regarding the content preview, I have raised an issue with the frontend team as the image does not fit the card.

The recorded demo: https://youtu.be/ShqDRvtA_JI

Additional updates:

retrieve cropped items
retrieve additional fields and their values based on language
updates to rendering component
updates to models based on the additional data retrieved from the API.

Additional updates added to the PR:

async/sync methods for services
update client headers to retrieve the public CDN URLs used for rendering the media asset: original and cropped items
updated the rendering component using the Aprimo item details as reference, and display the crop name, extension, size and render the image from the Public CDN of Aprimo resized

code refactoring


[Feature Request] Add Title / Name for the Episodes

Name for the Episodes for better sorting and analysis in Jellyfin
this is One Piece example: (scheme: One Piece - S01E01 - Hier kommt Ruffy, der künftige König der Piraten!)

Will work on this when I have time on the weekend.

Closed as of discord discussions. JellyFin doesn't index via file name but indexer service.


Fix test fail

We have CI test failures with message:
Error: async hook stack has become corrupted (actual: 1610, expected: 0)
...
[main 2020-03-12T13:44:02.534Z] [VS Code]: render process crashed!

This pr try to fix that error

Codecov Report

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

@@           Coverage Diff           @@
##           master     #199   +/-   ##
=======================================
  Coverage   73.44%   73.44%
=======================================
  Files          33       33
  Lines        1894     1894
  Branches      293      293
=======================================
  Hits         1391     1391
  Misses        503      503

Continue to review full report at Codecov.

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


Fix various Type Errors/warnings on php 8 and above and fix c5:phpcs command

This PR fixes various warnings in php 8 and above, it also fixes the c5:phpcs command
Since php8 changed a lot of the internal warnings to Type/Value errors and considers any warning an error by default its best to fix these when found.
This is the current ones I've found and fixed, I also updated concrete/src/block/block.php to use the latest database commands and removed if statements that aren't need.
Also all core_area_layout,youtube block and page title block files now pass PHPStan level 6
https://phpstan.org/user-guide/rule-levels
Fixes #10141
Also fixes an issue with updating child blocks from page defaults with forked blocks

@aembler I've removed all the code related to the changing of the display order when adding blocks


emoji_picker: Fix keys not working if search yields no results.

As a consequence of commit 1113589b9d the backspace key and some other keys did not respond if the search yielded no results. This change fixes that bug.
Relevant discussion.
Original bug:

Merged, thanks @vinitS101 and @Gittenburg!


Fix yaml acc tests in cg

Describe your changes
Comment Triggers

PR Check triggers

Build: trigger build
Sub Category Field Check: trigger subcategoryfieldcheck

trigger build

trigger build


Text size updated

Issue resolved: #834
Related Issue
[Cite any related issue(s) this pull request addresses. If none, simply state “None”]
Fixes:  #(issue no.) #834
Description
[Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.]
changed the text size accordingly

Type of PR

[ ] Bug fix
[ ] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)
[Attach any relevant screenshots or videos demonstrating the changes. Make sure to attach before & after screenshots in your PR.]
Checklist:

[ x] I have made this change from my own.
[ ] I have taken help from some online resources.
[x ] My code follows the style guidelines of this project.
[ x] I have performed a self-review of my own code.
[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] I have made corresponding changes to the documentation.
[ x] My changes generate no new warnings.
[ ] I have tested the changes thoroughly before submitting this pull request.
[ ] I have provided relevant issue numbers and screenshots after making the changes.

@Kajalmehta29 Text is getting out of place. Fix it or Find another issue or feature to contribute to. Thank you!


Help needed - sending integer in request

Hello,
I may be blind or stupid :) , but i cant find how to send integer in request body.
example:
"body": {           "caption": "${RANDOM.UUID}",           "external_id": "${RANDOM.NUMBER}"         }       }
Is there any way to send body.external_id as integer when we are using randomizers?
Thanks in advance
BR
AB

As far as I could see, this is not possible out-of-the-box. If it is however really desirable, there would be quit a change (the ${} is substituted only, not the surrounded double quotes)...

I mean, its not big problem cuz apps are trying to convert str to integer so it works, but would be nice to have control.

Thanks, Happy to know @automatedbegginer.
However we will raise a TECH-DEBT for this to address this.
Something like
"caption": "(int)${RANDOM.UUID}" should help.

I am going to look at implementing this as a first feature.
I know AC1 lists the syntax as: "caption": "(int)${RANDOM.UUID}" which follows the java casting style.
From a limiting code change perspective and trying to prevent unintended functionality to users (who may be trying to pass in a static value of (int)) I think something like: "caption": "${(int)RANDOM.UUID}" is better as it ties the data type directly into the ZeroCodeValueToken expression


Add host to the connection error message

When running docker client against a swarm cluster and connection to a
node failed, it's not obvious to figure out the targeting host from the
error message.
This is related to issue: https://github.com/docker/swarm/issues/2393
Signed-off-by: Jin Xu<EMAIL_ADDRESS>

Superseded by PR #302. Close it.


Implement EIP-712 Typed Data

Summary

Clean Apache 2.0 implementation of https://eips.ethereum.org/EIPS/eip-712

Initial implementation believed to contain all core features

Re-uses the ABI encoding libraries in this repo wherever possible, for consistent encoding/parsing behavior

Had to expose a couple of new side-doors to the ABI package to do this - other consumers could use these too

Operation compared with ISC License reference implementation in TypeScript:

See https://github.com/MetaMask/eth-sig-util/blob/main/src/sign-typed-data.ts
See PR https://github.com/ethereum/EIPs/pull/2190 against standard (never merged)

Implements V4 derivation of the behavior, as adopted by Metamask and OpenZeppelin communities

Most questions in the spec resolved through behavior of above reference implementation

Extends the ethsigner.Wallet interface with ethsigner.WalletTypedData

Avoids existing wallet implementations being forced to change

Extends the fswallet.Wallet implementation to include SignTypedDataV4
Contains some general maintenance on the repo

Updates firefly-common
Updates to Go 1.20
Updates dependencies

Provides mapping of ABI types to EIP-712 type arrays

Feels like the tooling around EIP-712 requires quite a bit of hand-spinning for the Solidity developer, and I was thinking this could take away at least one potential source of mistakes, and remove a 3rd artifact to maintain (Solidity struct/ABI, Solidity EIP-712 signing construct on-chain, JSON EIP-712 type array off-chain). Maybe even allow alternative APIs to be built that take ABI type definitions to sign directly.

Outstanding conversations

EIP-712 original standard includes this comment:

Note that the v parameter includes the chain id as specified in EIP-155.

I did not find evidence that this is adopted. Instead, there is strong guidance to use chainId in the EIP712Domain structure, where it can be verified on-chain using the current block.chainId.
As a result, the ethsigner.SignTypedDataV4 code does not call sig.UpdateEIP155(chainID)

@awrichar - looks like there's a DCO issue on the initial commit. Will work with you to get that resolved.

Codecov Report

Merging #51 (cf81fff) into main (e4d4a70) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##              main       #51    +/-   ##
==========================================
  Coverage   100.00%   100.00%
==========================================
  Files           35        38     +3
  Lines         3015      3307   +292
==========================================
+ Hits          3015      3307   +292

Files
Coverage Δ

pkg/abi/inputparsing.go
100.00% <100.00%> (ø)

pkg/abi/typecomponents.go
100.00% <100.00%> (ø)

pkg/eip712/abi_to_typed_data.go
100.00% <100.00%> (ø)

pkg/eip712/typed_data_v4.go
100.00% <100.00%> (ø)

pkg/ethsigner/typed_data.go
100.00% <100.00%> (ø)

pkg/fswallet/fswallet.go
100.00% <100.00%> (ø)

pkg/rpcbackend/backend.go
100.00% <100.00%> (ø)

FYI: I went back to add signoff on my commit, then replayed all of @peterbroadhurst 's commits on top. Should be unchanged in terms of the actual code changes.


kie-issues#42: DMN Editor: Repetitive opening of properties panel for List expression

Closes https://github.com/kiegroup/kie-issues/issues/42
An easier way to reproduce the issue, as analyzed by @yesamer in https://github.com/kiegroup/kie-issues/issues/42:

Add a Decision
Open de Decision node
Add a List
Add a new list item
Select the first item

Analysing the issue
As @yesamer mentioned in his first analysis, the error was caused because of a recursive reference in 'DMNModelInstrumentedBase:getDefaultNamespace()'
Every row in a 'List' is a 'HasExpression' encapsulated in 'WrappedHasExpression'.
The parent of 'WrappedHasExpression' is the list itself and the expression is the real expression (a 'LiteralExpression' in this case).
The issue was happening because in the 'AddListRowCommand' the parent of the 'WrappedHasExpression' (which is the 'List') was being set to the 'List' but it should be the expression inside 'WrappedHasExpression' that needs to have its parent set to 'List'.
Maybe the method 'asDMNModelinstrumentedBase()' is incorrect because its returning the parent instead of the expression wrapped in WrappedHasExpression, but change this method will require to check it in all other places where it is called....

@yesamer In my opinion it is not feasible to track all places where WrappedHasExpression.asDMNModelInstrumentedBase() is used, because asDMNModelInstrumentedBase() is an implementation from HasExpression. So we gonna need to track all places where the instance of HasExpression is WrappedHasExpression and analyze if the logic is correct.

@danielzhe This is the PR that introduced it: https://github.com/kiegroup/kie-wb-common/pull/3220.
Looking in the test It seems that returning the parent was intended https://github.com/kiegroup/kogito-editors-java/commit/24a424c0eb4a6c1e64c18cb1f638bcc978048c11#diff-0ee778ee563e991f475a6fdaa1079e9533357bb53f877521ec120344accab7c7R55.


[BEAM-5791] Improve Python SDK progress counters.

The returned metrics are supposed to count the elements consumed, which should
be incremented after an element is produced, not before.  Updated counters
to correctly reflect this, which is important for tracking the rate of buffer
consumption by runners
Also, some runners (e.g. the Dataflow harness) don't set unique names on
PTransforms, which was causing counters to be conflated.  Now the counters
use the ptransform_id if the unique name is not provided.

Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.


Handling lots of warnings.

Is your feature request related to a problem? Please describe.
I have a little bit awkward LTN network which doesn't empty items on the request station. This network generate lots of warnings, so I'd like to cleanup them easily.
If I have lots of warnings(say, 100+) then the GUI of LTN Managers is extremely slow, so it is not feasible to remove them one by one.
Describe the solution you'd like

Add a button to clear all alerts.
Use Lua`s pattern matching to ignore specific patterns of warnings.

Additional context

This is important because if there are a lot of alerts (more than 100, I guess), the load on the server and the clients increases considerably. And, if you then try to delete a message, the game 'hangs' for a couple of seconds (1-3). It is not possible to delete a significant number of error messages under these circumstances.
Current solution: Stop the server, remove LTN Manager mod, start server, stop server, re-add mod, start server and the messages are gone.
After that the load on the server is back to about 0.3 (from above 1) and the in-game fps are at stable 60 (before drops to 15 where "normal"). Also, deleting new messages does not have an impact on game performance, as long as the message queue is relatively empty.
The server is a virtual machine running linux with 4 cores (Xeon Gold 6136 based), 16 GB RAM and SSD disk, so the problems should not be due to weak hardware.

Hey, sorry for the delay, I'm horrible at juggling projects and have been otherwise occupied.
The main issue causing all of the slowdown is that I neglected to put a limit on the number of alerts it stores at a time. I didn't realize that some maps might have tons and tons of alerts. So I will also fix that for the next version.
I will merge your PRs later today. However, I won't be able to release a new version today, because the current state of master is not suitable for public consumption, and there is a lot of work to be done to re-add some missing features, specifically the search GUI.

This was implemented in v0.4, with a "clear all alerts" button and advanced search on all tabs.