Refactor settings

Implements settings as an application specific entity that is hydrated from the Django settings. Similar patterns can be seen in packages such as all_auth.
Also moves settings to an EB_SQS dictionary and issues deprecation warning if found in the global namespace. (see #8 for reasoning).
Last but not least, implements a TODO: puts queues on the settings and caches them.

@DataGreed any chance of getting this merged?


Create a space

Description
As a project owner, I'd like to create a new space, so that I can collaborate with other team members on a specific project.
When creating a space, I should specify a name unique to the namespace where the space exists. Currently, this is the user account, and may eventually be an organization account.
Functional Acceptance Criteria:

Spaces can be created with an alphanumeric set of characters.
Space names should be unique to the entity where it is created - user or organization.
Spaces must have names. Blank space names are not permissible.
Spaces must have an associated process template at the time of creation - agile, scrum, etc.

Tasks:

Extend SpacesService to create spaces in the REST API backend. (#67)
Update SpacesDialogComponent to use SpacesService instead of DummyService to create spaces. (#68)

@VineetReynolds the UI now has all of this.

@VineetReynolds can you make sure you add validation to the rest endpoint for allowed chars. ^[a-zA-Z0-9_-]*$


add support for writing custom IFDs to lazy files

fixes #105

Codecov Report
Patch coverage: 100.00% and project coverage change: -0.33% :warning:

Comparison is base (fee7559) 90.21% compared to head (4bf3c15) 89.88%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #109      +/-   ##
==========================================
- Coverage   90.21%   89.88%   -0.33%
==========================================
  Files          13       13
  Lines         756      761       +5
==========================================
+ Hits          682      684       +2
- Misses         74       77       +3

Files Changed
Coverage Δ

src/types/lazy.jl
89.85% <100.00%> (+0.79%)
:arrow_up:

... and 1 file with indirect coverage changes

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


Multiple scopes for namespace foo.bar

If I understand correctly, this:
namespace foo.bar {
  export const qux = 123;
}

is just shorthand for:
namespace foo {
  export namespace bar {
    export const qux = 123;
  }
}

Therefore, namespace foo.bar essentially represents 2 scopes - 1 for foo, and a 2nd for bar.
I propose to encode this in the AST by either:

Add scope_id field to the TSModuleDeclarationBody::TSModuleDeclaration variant
or
Remove scope_id field from TSModuleBlock and add it to TSModuleDeclaration instead.

Creating multiple scopes seems semantically correct to me, and would make transforming it to JS much simpler.
Just opening this issue because I'm pretty rubbish with TS, and want to check my reasoning before going ahead with it. Am I misunderstanding anything?
cc @Boshen @Dunqing

Sounds reasonable. I'm fine with that.

Thanks. I'll do that, and then hopefully can get all the scopes in namespace transform correct.

Implemented in #3488.


Final layout is not invoked in the transpiler unless the swap mapper is called.

Environment

Qiskit Terra version:
Python version:
Operating system:

What is happening?
In the following code
theta = Parameter('theta')
qc_example = QuantumCircuit(3)
qc_example.h(0) # generate superposition
qc_example.p(theta, 0) # add quantum phase
qc_example.cx(0, 1) # condition 1st qubit on 0th qubit
qc_example.cx(0, 2) # condition 2nd qubit on 0th qubit

qc_ibm = transpile(qc_example, basis_gates = ['cz', 'sx', 'rz'],  coupling_map =[[0, 1], [1, 2]], optimization_level=3)
print(qc_ibm)

The transpiler performs a mapping but only initial_layout is updated not the final_laytout is set to none
qc_ibm.layout

gives
TranspileLayout(initial_layout=Layout({
1: Qubit(QuantumRegister(3, 'q'), 0),
2: Qubit(QuantumRegister(3, 'q'), 1),
0: Qubit(QuantumRegister(3, 'q'), 2)
}), input_qubit_mapping={Qubit(QuantumRegister(3, 'q'), 0): 0, Qubit(QuantumRegister(3, 'q'), 1): 1, Qubit(QuantumRegister(3, 'q'), 2): 2}, final_layout=None)

This should give
final_layout=Layout({
1: Qubit(QuantumRegister(3, 'q'), 0),
2: Qubit(QuantumRegister(3, 'q'), 1),
0: Qubit(QuantumRegister(3, 'q'), 2)

How can we reproduce the issue?
see code above
What should happen?
This should give
final_layout=Layout({
1: Qubit(QuantumRegister(3, 'q'), 0),
2: Qubit(QuantumRegister(3, 'q'), 1),
0: Qubit(QuantumRegister(3, 'q'), 2)

Any suggestions?

Personally I find the notation very confusing. It took me a while (actually I never did @nonhermitian explained it to me) to realize initial_layout is not the initial_layout but the initial_layout to the swap mapper and the final_layout is the layout  after the swap mapper (also no idea what 'input_qubit_mapping' is). Personally I think layout should just be the final one but if the user wants the history of how the layout changed then the should have meta data that correlates passes used with layout changes. But I think this would be a longer issue. My suggestion is to perform a quick update to set final_layout for this example and then in the future create an issue for what should be in the layout after the transpiler and how a user can get meta data that includes how the layout changes.

Actually None is equivalent to a trivial final layout. So it would be:
Layout({
0: Qubit(QuantumRegister(3, 'q'), 0),
1: Qubit(QuantumRegister(3, 'q'), 1),
2: Qubit(QuantumRegister(3, 'q'), 2)

The final layout is mapping the qubit object in it's position in qc_ibm.qubits at the start of the circuit (after the initial layout) to the output position after routing; not the original circuit's position to the final position like the name implies. So if qc_ibm.layout.final_layout is None that means routing wasn't need and there is no output permutation caused by swap mapping. That being said we can update the default in the transpiler output to always populate final_layout even if routing doesn't run, that probably would make it easier for people as you don't need to explicitly handle the None case.
The input_qubit_mapping object attribute is the positions for the virtual qubit objects in the input circuit, that information is lost from the transpiler's output circuit and if we want to reverse the permutations caused by the transpiler we need to know where the qubits started in the input circuit. The best example to see how all these attributes are used is in Operator.from_circuit (https://github.com/Qiskit/qiskit/blob/cd507adc68a96a333bc62de7ce9799a245506f25/qiskit/quantum_info/operators/operator.py#L410-L426) which reverses the permutation tracked in qc_ibm.layout so that it's operator is the same as the input circuit qc's.
The TranspileLayout object is basically already what you're describing where each stage tracks the permutation it causes to the circuit (per pass is too fine grained as earlier permutations may be changed later in the pipeline). That being said the names are confusing (I also don't like the structures we use for this as I would just like arrays of integers), but it's an interface that people are relying on and while not super ergonomic it is workable. For me the path forward here is to improve the documentation, right now we have some description in: https://qiskit.org/documentation/stubs/qiskit.transpiler.TranspileLayout.html#qiskit.transpiler.TranspileLayout and I feel like we can improve that and also include better examples of how to work with it.

no as this circuit is in the input_layout it was changed from the original. Why I said a bug


Authentication Method

I'm trying to connect to a subsonic server that uses password authentication. Since I can't change the server config to use token authentication, I can't use the application at all. I would like to request the option of choosing between authentication methods when adding a new server.

https://github.com/NattyNarwhal/Submariner/blob/master/Submariner/SBServer.m#L349-L363
I should un-hardcode this :sweat_smile:

I've added this for the next version. You can try compiling it yourself (should be a normal Xcode project), or using the output from CI (be warned that those builds aren't signed). Note that this fix does involve a schema upgrade, so it'll be incompatible with 2.0.


docs: added LF Edge required Adopters, Governance and Owners MD pages

Signed-off-by: jpwhitemn<EMAIL_ADDRESS>PR Checklist
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

If your build fails due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-go/blob/master/.github/Contributing.md.
What is the current behavior?

LF Edge required documentation pages added to the repository (Adopters, Governance and Owners)
Issue Number:
What is the new behavior?
Does this PR introduce a breaking change?

[ ] Yes
[x] No

New Imports

[ ] Yes
[x] No

Specific Instructions
Are there any specific instructions or things that should be known prior to reviewing?
Other information

Codecov Report

Merging #3660 (5ce3423) into main (a7bcd55) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #3660   +/-   ##
=======================================
  Coverage   47.29%   47.29%
=======================================
  Files         112      112
  Lines        9177     9177
=======================================
  Hits         4340     4340
  Misses       4463     4463
  Partials      374      374

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 a7bcd55...5ce3423. Read the comment docs.


Re-factor: Code re-factor to separate out realtime specific references from fixed-byte readers/writers.

Created an interface PinotDataBufferMemoryManager, that is now passed
to fixed-byte readers/writers.

Eliminated segmentName being stored in memory manager. Instead, now
callers allocating memory pass an allocationContext
(segmentName:columnName), that is used for logging within memory
manager. RealtimeOffHeapMemoryManager still has dependency on segment
name, that is harder to remove, and will explode this PR, therefore not
addressed.

Fixed code-style for all touched files.

Codecov Report

Merging #2476 into master will increase coverage by 0.1%.
The diff coverage is 86.98%.

@@            Coverage Diff            @@
##           master    #2476     +/-   ##
=========================================
+ Coverage   69.32%   69.43%   +0.1%
=========================================
  Files         840      840
  Lines       39376    39350     -26
  Branches     5299     5289     -10
=========================================
+ Hits        27299    27321     +22
+ Misses      10302    10257     -45
+ Partials     1775     1772      -3

Impacted Files
Coverage Δ

...a/manager/realtime/RealtimeSegmentDataManager.java
100% <ø> (ø)
:arrow_up:

...inot/core/realtime/impl/RealtimeSegmentConfig.java
96.22% <ø> (ø)
:arrow_up:

...manager/realtime/LLRealtimeSegmentDataManager.java
68.28% <ø> (ø)
:arrow_up:

...impl/dictionary/FloatOffHeapMutableDictionary.java
87.27% <100%> (ø)
:arrow_up:

...time/impl/dictionary/MutableDictionaryFactory.java
66.66% <100%> (ø)
:arrow_up:

...e/impl/dictionary/IntOffHeapMutableDictionary.java
94.54% <100%> (ø)
:arrow_up:

...mpl/dictionary/StringOffHeapMutableDictionary.java
98.21% <100%> (ø)
:arrow_up:

.../impl/dictionary/LongOffHeapMutableDictionary.java
87.27% <100%> (+3.63%)
:arrow_up:

.../FixedByteSingleColumnSingleValueReaderWriter.java
100% <100%> (ø)
:arrow_up:

...pinot/core/io/writer/impl/DirectMemoryManager.java
100% <100%> (ø)
:arrow_up:

... and 23 more

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 8bbb5fe...8ed294d. Read the comment docs.


Build with Xcode 10 throw error - 'Redefinition of module Pods_

Migrated project to Xcode 10. When build the app it gives below build error.
SMXcrashlytics.m - Redefinition of module ‘Pods_myapp’
I have used below version in Podfile:
pod 'Fabric', '1.9.0'
pod 'Crashlytics', '3.12.0'

In my case it complaints about  Sift redefinition


RaidGuild Request: indexed.wtf doc edits and additions

Hello blessed devs,
@ChihChengLiang @vaibhavchellani @kilic @thrilok209 @zemse @0xAshish @sz-piotr
We here at Raid Guild have brought you indexed.wtf and are taking care to make sure the docs we display for each Layer 2 and side-chain project are accurate and filled with information the dev teams would like to highlight specifically. Having easily accessible information about all these solutions will bring more attention to your project.
Please find the markdown for the docs for your project below.
Kindly review, edit and provide any missing details and information at your taste and discretion as project leaders.
Moving forward we aim to keep indexed.wtf as current and beneficial to developers researching the ecosystem as possible. Please feel free at any time to submit an issue or PR to update the displayed information.
Thank you for your attention to this matter.
Best,
The Indexed Army
We stand for accurate data.
www.RaidGuild.org
@chair28980 @kittyslasher
# indexed.wtf Template

## Name

Hubble Optimistic Rollup

## Description

An optimistic rollup powered by BLS signature.

## Consensus Type

The liveness and safety are provided via a centralized coordinator, whose role is auctioned to the public and whose behavior is held accountable via fraud proofs.

## Tx Cost

- Gas price not applicable yet. We have to know when it is in production
- Gas cost is 345 gas.

## Average TPS

2786

##Finality Time

1 Week

## Governance/validator Token

No

## Transactional Token

ERC20s

## Resources

[Github](https://github.com/thehubbleproject/hubble-contracts)
[Developer Docs](https://thehubbleproject.github.io/docs/)

## Social Media & Community

https://github.com/thehubbleproject/hubble-contracts/discussions

Hello @kittyslasher,
Thanks for reaching out. I've given it a round of editing.

Hello @kittyslasher,
Thanks for reaching out. I've given it a round of editing.

Thank you so much! I will edit it a little further before publishing such as linking people to BLS. We would like to keep these documents updated on a regular basis as it will change with development. We will have the ability for you to submit PR to the docs any time changes are made. for social media do you guys have any discord, twitter, Reddit ect ect?

Hi @kittyslasher,

I will edit it a little further before publishing such as linking people to BLS. We would like to keep these documents updated on a regular basis as it will change with development.

That is awesome, thank you so much for the effort.
For social media, we have only one Telegram channel to communicate with the people who interested. But we haven't shared the joining link with the public for the fear of bots joining. Let me add some bot protection before sharing.

Hi @kittyslasher,

I will edit it a little further before publishing such as linking people to BLS. We would like to keep these documents updated on a regular basis as it will change with development.

That is awesome, thank you so much for the effort.
For social media, we have only one Telegram channel to communicate with the people who interested. But we haven't shared the joining link with the public for the fear of bots joining. Let me add some bot protection before sharing.

No worries I completely understand! We will work on getting the information posted as soon as possible. I did request one extra piece of information I forgot in the template which is finality time. The template has been edited and there is a section for the requested information.

I did request one extra piece of information I forgot in the template which is finality time.

Sorry for the delay, I've updated the requested information.

I did request one extra piece of information I forgot in the template which is finality time.

Sorry for the delay, I've updated the requested information.

I apologize for the delay myself! I much appreciate your efforts on this!  We will be going live within the next week with the new site. I will keep you updated on everything and set up communication for future updates!


Add test cases for uvx in binary build workflow

I don't think this would have caught the problem in 0.2.19 but I hope it saves us from trouble in the future.

Related to https://github.com/astral-sh/uv/pull/4743


Change axios back as dependency.

Hi,
The last PR (https://github.com/vpulim/node-soap/pull/1179) where axios moved as peer-dependency was a way to fix type issues with axios instance if project depending from node-soap would also use axios as their dependency and axios versions would be different.
The idea is correct, but I'm currently not sure what would be the correct fix. Correct fix is not to move axios as peer-dependency, because broke node-soap usage with npm versions lower than 7, because npm versions 3-6 will not install peer-dependencies by default. PR checks run by node-soap CI pipeline https://github.com/vpulim/node-soap/pull/1179/checks were green, because build pipeline is using node 16.13.2 which has npm 8.x and that will install peer-dependencies automatically.

Not PR related.
GitHub issues have been disabled to focus on pull requests., I wish you would enable issues again because that would allow normal way of communication. If you do not like "please help me" issues, then close those automatically or guide users to use gitter for that purpose.
Axios released new 0.25.0 version that fixes security issue in 'follow-redirects' package, I did not update axios in this PR, because I'm not sure how axios-ntlm works with different axios versions.
From some PR comments my co-worker picked up phrase something like "Because node-soap is under version 1, we can make breaking changes.". This is at-least 7 year old project and it has no good alternatives so this package IS in production use in many places and I suggest that working habits in this project get more mature. Change from request to axios caused breaking change although it was not mentioned as such. My customers project issue was caused proxy handling differencies between request and axios and fix caused over 10 000 eur cost (consultant fixing code) after this node-soap patch version upgrade.

package-lock.json changed a lot because I used node 12.18.3 that has npm 6.14.6. It is ok to develop with the latest node+npm versions, but because package.json states that node-soap is compatible with node 12.0.0+ CI pipeline should also ensure that things work with other node versions as well.

One possible workaround to type issue could be
import { IOptions } from 'soap' // with axios 0.21.1
import axios from 'axios' // our axios 0.25.0

// code

const clientOptions = {
  request: axios.create({
    timeout,
  }) as IOptions['request'],
}

Or, (axios.create() as unknown) as IOptions['request']

The fix suggested here might cause some unexpected behavior.
The type error fix suggested here works and the user is able to "force" higher version axios to be used by this library. However, this would effectively make this library use two different versions of Axios, unless each instance is provided explicitly with the new Axios version. This is because when this library uses the default Axios, its version is still the old ^0.21.1.
So basically the fix suggested here works as intended IF all the instances of this library is provided manually with the higher version of Axios. Otherwise two different versions are used.
Axios as a peer dependency fixes this problem, but as you have pointed out, it also creates other issues.

@jsdevel ping

@RopoMen can you look at the failing build issue?

@jsdevel It seems to fail also with master.

@vpulim ping?

@orgads .  sorry for the late reply.  can you take a look at the failing test?

It's not related to this change.

What's the update on this? I can't install the new version normally because of a dependency mismatch:
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/axios
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/soap
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

What's the update on this? I can't install the new version normally:
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/axios
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/soap
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

Same here, node-soap can't be installed with<EMAIL_ADDRESS>

If you depend on axios directly, a workaround is to add this to package.json to make soap use the same version:
"overrides": {
  "soap": {
    "axios": "$axios"
  }
}

Overrides is available only in npm 8, not in npm 6 or 7.

we'll move forward with #1188 for the time being and see how it goes in the community.  thank you all!

alright, looks like users are having issues with peerDependencies.  @RopoMen can you fix the build and resolve conflicts?

@jsdevel I started my summer vacation yesterday and I'm back at work 27.7. I dont have my work laptop with me.

Any update on this?

Axios latest version also has a breaking change. It does no longer export with "default" attribute so code in lib/http.js is broken.
More info here: https://github.com/axios/axios/issues/5011

I am not able to upgrade soap, because the peerDependency doesn't allow<EMAIL_ADDRESS>Is it possible for node-soap to use axios >=0.27.2?
This way 1.2.0 would be useable in combination with the latest node-soap Version

Axios latest version also has a breaking change. It does no longer export with "default" attribute so code in lib/http.js is broken.
More info here: axios/axios#5011

This problem was fixed in Version 1.2.0.

Does anybody know of a suitable replacement module for this one? Unless axios is a dependency, this module is not usable. Our security team won't let us install axios 0.27 as a direct dependency when 1.6 is available. But this peer dependency means we can't npm install If it's a real dependency then npm will install a second version and all will work.
And since it's been so long since this module changed, I presume it's "dead" - so is there something else with an almost equivalent API?

I'm considering using strong-soap https://github.com/loopbackio/strong-soap

New version has been released. I guess this PR is not relevant anymore? Please let me know if this is still an issue.

Still not sure peer dependency is the way to go but at least it now points to a recent version and I can actually install soap.

Do you still use old npm versions? My team is on the latest node and npm so I can't really say how important this is.

We use the latest we can of everything. That was the problem. We had axios 1.6 but soap required 0.27 and we couldn't build our software. This release solves that immediate problem but the generic issue of one module having different versioning requirements to the main project yet still using peer dependencies remains. It'll happen again one day. If axios releases v2 tomorrow, our software will break because we'll upgrade and soap may not. The truth of the OSS world is I can't force maintainers to issue updates. I rely on many modules that have not been updated in years (one of them is a reference OAUTH client I've had to rewrite from scratch because they have security holes in their submodule versions but nobody is publishing it any more ). I was pleasantly surprised when this repo was published after a year. I honestly expected to have to rewrite my code to use a new soap library. And it's all caused by the peer dependency.

Thanks for detailed response @KrayzeeKev. I don't see any problems to make it normal dependency. At least it does not look like it should introduce any problems. Do you mind raising a merge request?
I don't have much time for this project, but planning to review MRs every 1-2 weeks and publish releases.
Feel free to suggest other changes you think can be useful.

I raised another PR as it was easier https://github.com/vpulim/node-soap/pull/1237
Please comment there if you have any objections, otherwise I will include it into next release.

Change is accepted and merged in https://github.com/vpulim/node-soap/pull/1237


Added Central Bank of the Republic of Turkey provider.

Hello,
Created new provider for Central Bank of the Republic of Turkey.
It's similar to the National Bank of Romania provider but not based on base currency.
CBRT is publishing currencies as quote currency in TRY.
Eg: EUR/TRY, USD/TRY etc.
Currencies provided from and tcmb.gov.tr/kurlar/today.xml  updated daily based on 15:30.

Hello @ugurerkan, thanks for your contribution.
I will merge it once the small code style issues are fixed

Thank you for your review @florianv, issues are fixed now.


CDF Sampling causes halo on mobile

Started on 55310f06fbc7dba87eae7059b315536a925e4c2e
Still working on at least bc638674e62d87da9a3ede9fd4986c9454b9455a
Perhaps related to the tent filter?

This seems to no longer be an issue -- perhaps it was caused by mip maps.


Browser's selection highlight dimensions don't match the emulated highlights

Issue
When users select the text, both the default browser's selection highlight and the customly drawn highlight appear. Unfortunately, their dimensions don't match and that leads to the following views across browsers:

Chrome
Safari
Firefox

That hanging bluish default selection background looks a bit out of place. Ideally, the emulated highlight should match its dimensions. Fortunately, that can be achieved by applying various sizes of compensations based on the browser:

Chrome
Safari
Firefox

The padding can be applied in the concrete renderers, as I did for the canvasRenderer:
// // Chrome
// const selectionHighlightTopCompensation = 3;
// const selectionHighlightBottomCompensation = 7;

// // Safari
// const selectionHighlightTopCompensation = 7;
// const selectionHighlightBottomCompensation = 7;

// Firefox
const selectionHighlightTopCompensation = 0;
const selectionHighlightBottomCompensation = 0;
offsetRects.forEach(({ x, y, width, height }) =>
  ctx.fillRect(
    x,
    y - selectionHighlightTopCompensation ,
    width,
    height + selectionHighlightBottomCompensation
  )
);

I'm surprised that Firefox is the only browser that doesn't apply some magical padding to its selection highlight

Thanks for testing this out. I was thinking about whether I should just CSS-disable the native selection. But then left it because a) it's probably something that the host application would want to control; b) the native selection is, simply, rendered faster. Not a massive issue, and only for really large (XML - in our case) documents. But still.
About matching the sizes: I wonder how reliable those numbers are though, across different OSes and version increments...

I already tried disabling the native selection in my app and it didn't go that well 😅
Especially when you have not-annotatable content in between the annotatable parts:

The selection could stop abruptly when it's started on the not-annotatable element:

https://github.com/recogito/text-annotator-js/assets/68850090/21080513-89da-4d52-942b-1fedd9050027

There could be 2 highlights at the same time 😆. One is made on a not-annotatable element, and the other one is emulated:

screen-capture (11).webm

And the Ctrl+A acts weirdly then as well if you're focused on the not-annotatable element:

https://github.com/recogito/text-annotator-js/assets/68850090/655593f8-2311-44f1-ab16-3ce1ce7731e1

About matching the sizes: I wonder how reliable those numbers are though, across different OSes and version increments...

That's a great question! I was about to experiment with that using the Browserstack. I'll get back with the results 🙌🏻

Aha, it's even more complex than I anticipated... The browser's selection highlight height can differ based on the selection element (h vs p) and the text row number 🤯
Here are the demos of the selection behavior across browsers with the:
const selectionHighlightTopCompensation = 0;
const selectionHighlightBottomCompensation = 0;

TL;DV;
Firefox is the most stable one and it always paints the selection hight using the same height.
Chrome:
https://github.com/recogito/text-annotator-js/assets/68850090/a295843d-a219-483b-b9cb-8ff546b235ce
Safari:
https://github.com/recogito/text-annotator-js/assets/68850090/4f029b1c-d4d4-4981-a617-60cddb135a6d
Firefox:
https://github.com/recogito/text-annotator-js/assets/68850090/a161771b-61e5-48fd-b9bb-e3925df4b665

After many trials and tests in different environments, I would say that the _selection selectionHighlightCompensation should be removed and we should draw highlights using just the raw dimensions". Such a conclusion comes from multiple factors:

Default browser's selection highlight height has inconsistent behavior across browsers / target elements / position of the text. This makes the creation of some generic compensation quite a moving target.
Even when using the CSS highlights API - there is a difference between the text selection highlight and the one drawn by CSS, especially in Chrome.

https://github.com/recogito/text-annotator-js/assets/68850090/2667de32-640b-4d56-9215-7f6077fc357c
In the video, you can see that only in Chrome the default selection highlight is higher than the CSS one. Which begs the question whether that was intended behavior added by the Chromium devs 🤔

After many trials and tests in different environments, I would say that the _selection selectionHighlightCompensation should be removed and we should draw highlights using just the raw dimensions". Such a conclusion comes from multiple factors:

Default browser's selection highlight height has inconsistent behavior across browsers / target elements / position of the text. This makes the creation of some generic compensation quite a moving target.
Even when using the CSS highlights API - there is a difference between the text selection highlight and the one drawn by CSS, especially in Chrome.

https://github.com/recogito/text-annotator-js/assets/68850090/2667de32-640b-4d56-9215-7f6077fc357c
In the video, you can see that only in Chrome the default selection highlight is higher than the CSS one. Which begs the question whether that was intended behavior added by the Chromium devs 🤔


switch to dune, make it compile

Hey @zapashcanon thanks for the PR. I haven't touched this in years so I haven't been really following Ocaml too closely. Let me know if you want me to add you as a maintainer to the project so you can manage and freely commit.

You're welcome.
I did it because of someone mentioning the library in IRC:
hendursaga:

Anyone aware of OCaml library for web browser automation? The closest I could find is https://github.com/mayanez/ocaml-webdriver but I doubt it'd compile these days.

I'm actually not interested in this myself so don't think I'd want to become a maintainer but thanks anyway ! :)


Piranha.EF: Db needs virtual properties

Problem
The Piranha.EF.Db class's DbSet properties are not marked as virtual. Because of this, Moq won't be able to mock the properties for testing of repository implementations
Possible Solutions

Mark DbSet properties as virtual

Just noticed that Piranha.EF.Db is a sealed class, and therefore cannot have virtual properties. This should like be refactored to inherit from an internal Piranha.EF.IDb so that unit tests can be written to verify the repository implementations. This would also mean updating all constructor/properties within the /src/data folder to use the new Piranha.EF.IDb.
Thoughts on this, @tidyui?

Since Unit Testing is not my field of expertise I'll just write the thoughts behind the current architecture and you can evaluate from a Unit Testing perspective.
Sealed DbContext
The Db context should never be extended by the users, it is an internal object of the Entity Framework implementation of the repositories. The reason for the class being public is that users should be able to add repository extensions which can then access use the DbContext for custom queries.
Mocking the DbContext
The IApi is injected an IDataService. Piranha.EF implements the IDataService interface for Entity Framework. Instead of overriding properties in the DbContext a mock Data Service should be created (or at least that was my idea behind it).
Let me know if the clarifies and solves the issue!
Regards

I should start off by saying that unit tests are also not my area of expertise, but I have been trying to improve my understanding of TDD, and writing good unit tests to help improve projects.
I'm realizing I wrote this issue, but didn't actually clarify why I wrote it. I want to make unit tests for each of the I*Repository implementations. In order to accomplish this, I need to be able instantiate the repository object and give it some in memory data to test on, which means I need to use their default constructors. This in turn means I need to be able to inject an instance of Piranha.EF.Db into the object to perform testing and provide the repo with the data.
Sealed DbContext
This totally makes sense, and I 100% agree with making it sealed; it shouldn't be manipulated publicly. With that being said, I'm thinking an internal Piranha.EF.IDb would be the best option that Piranha.EF.Db then implements. I believe it would require the least amount of refactoring, and realistically wouldn't make any functional changes.
Why IDb?
Apologies if this is redundant information or you're already aware of this!
The reason we need either an interface or virtual properties/methods is so that mocking frameworks, such as Moq, can create proxy implementations of those properties/methods. If the method can't be overridden then Moq can't intercept it and inject an artificial result. With an IDb, however,  we can do the following for a PageRepository unit test
var mockDb = new Mock<IDb>();
mockDb.Setup(d => d.Pages).Returns(new List<Page> {
    // in memory Page objects
}.AsQueryable());
var pageRepo = new PageRepository(mockDb.Object);
var page = pageRepo.Query();
// runs the Pagerepository.Query method, but operates on the data we
// povided during the .Setup().Returns() call

Mocking the DbContext
If I'm understanding correctly, you were thinking an IApi instance would have an IDataService injected, which can then have unit tests done on it, or be used for injection into other tests, such as PageController. This is actually already achievable, since there is already an IApi that can be Moqed, and is in fact what's going on in the Manager controller unit tests. But when it comes to testing the implementations in Piranha.EF, the repos are tightly bound to Db and DataService, preventing them from being Moqed properly and tested.
Conclusion
I think a Piranha.EF.IDb should be created, which can then be used for injecting Mock<IDb> objects into repo implementations for unit testing. Furthermore, in order to create these repo tests Piranha.EF will need to use the InternalsVisibleToAttribute.

Sidebar
Why do only some of the Piranha.EF.Repositories derive from RepositoryBase<T, TModel>? My first assumption was that it had to do with a TModel not having a matching Extend.T to pair with, but I see that BlockTypeRepository doesn't derive from RepositoryBase even though there is a Extend.BlockType. Is there a particular design logic behind this, or was this an accident? If it was an accident, would you like me to take the time to fix it while handling the IDb refactor?

I see, I never intended for the repositories to be created outside of the DataService which is why all constructors are internal as well:
https://github.com/PiranhaCMS/piranha.core/blob/master/src/data/Piranha.EF/Repositories/BlockTypeRepository.cs#L31
Now if you have a solution on how to maintain a good secure code structure and still being able to mock the DbContext for testing the repositories by all means go ahead.
Regarding the PageType/BlockType repositories not deriving from RepositoryBase it's probably just a miss but we don't need to invest to much time into these right now, I thinking about removing/disabling them for the first version as types will be import only.

Handled in 7aa6c98 using an interface


Aspect ratio of captured image is incorrect

The captured image appears to be stretched in the app, like it's being forced into a particular aspect ratio that does not correspond with the image's actual aspect ratio.

@dolph has fixed it!


Adds Validation Rules

This adds 19 new validation rules from graphql-js as well as all associated tests. As bugs were exposed through this testing, relevant fixes were made. This should improve usability of GraphQL APIs built on this package, since APIs will now automatically return better error messages to clients.
Since this is such a large merge request, I've organized the commits so that each new rule is specified in a feature commit. Any required fixes or adjustments were made in fix commits before the feature commit in which the rule was added. The MR may be easier to review commit-by-commit.

@paulofaria @d-exclaimation Hey guys, let me know if there's something I can do to make this easier to review. I realize that it's very big and I'd be willing to split it up into smaller PRs if that helps.

@paulofaria Thanks! In applying it to my big complex GraphQL schema, I found and fixed one small bug. Please re-approve if that one looks okay! https://github.com/GraphQLSwift/GraphQL/compare/33fa691e106911893265995f1be99efd965d6e1b..a4063a10941592c45c3dd92f3f0c5f9d70043aca


[Bug]: Container.Name always starts with forward slash

Testcontainers version
3.7.0
Using the latest Testcontainers version?
Yes
Host OS
Windows 10
Host arch
x64
.NET version
8.0.101
Docker version
Client:
 Cloud integration: v1.0.35+desktop.10
 Version:           25.0.2
 API version:       1.44
 Go version:        go1.21.6
 Git commit:        29cf629
 Built:             Thu Feb  1 00:24:09 2024
 OS/Arch:           windows/amd64
 Context:           default

Server: Docker Desktop 4.27.1 (136059)
 Engine:
  Version:          25.0.2
  API version:      1.44 (minimum version 1.24)
  Go version:       go1.21.6
  Git commit:       fce6e0c
  Built:            Thu Feb  1 00:23:17 2024
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.6.28
  GitCommit:        ae07eda36dd25f8a1b98dfbf587313b99c0190bb
 runc:
  Version:          1.1.12
  GitCommit:        v1.1.12-0-g51d5e94
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

Docker info
Client:
 Version:    25.0.2
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.12.1-desktop.4
    Path:     C:\Program Files\Docker\cli-plugins\docker-buildx.exe
  compose: Docker Compose (Docker Inc.)
    Version:  v2.24.3-desktop.1
    Path:     C:\Program Files\Docker\cli-plugins\docker-compose.exe
  debug: Get a shell into any image or container. (Docker Inc.)
    Version:  0.0.22
    Path:     C:\Program Files\Docker\cli-plugins\docker-debug.exe
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-dev.exe
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.21
    Path:     C:\Program Files\Docker\cli-plugins\docker-extension.exe
  feedback: Provide feedback, right in your terminal! (Docker Inc.)
    Version:  v1.0.4
    Path:     C:\Program Files\Docker\cli-plugins\docker-feedback.exe
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.0.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-init.exe
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
    Version:  0.6.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-sbom.exe
  scout: Docker Scout (Docker Inc.)
    Version:  v1.3.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-scout.exe

Server:
 Containers: 0
  Running: 0
  Paused: 0
  Stopped: 0
 Images: 18
 Server Version: 25.0.2
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: ae07eda36dd25f8a1b98dfbf587313b99c0190bb
 runc version: v1.1.12-0-g51d5e94
 init version: de40ad0
 Security Options:
  seccomp
   Profile: unconfined
  cgroupns
 Kernel Version: <IP_ADDRESS>-microsoft-standard-WSL2
 Operating System: Docker Desktop
 OSType: linux
 Architecture: x86_64
 CPUs: 24
 Total Memory: 4.802GiB
 Name: docker-desktop
 ID: 7ecf11cf-d186-4888-b03d-4934292531d1
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 HTTP Proxy: http.docker.internal:3128
 HTTPS Proxy: http.docker.internal:3128
 No Proxy: hubproxy.docker.internal
 Experimental: false
 Insecure Registries:
  hubproxy.docker.internal:5555
  <IP_ADDRESS>/8
 Registry Mirrors:
  https://docker.company.ch/
 Live Restore Enabled: false

What happened?
When starting a container, the Name property always starts with a / which is not present when running docker ps:

Relevant log output
No response
Additional information
At the moment, the following test fails:
using FluentAssertions;
using Testcontainers.PostgreSql;

namespace TestProject1;

public class UnitTest
{
    [Fact]
    public async Task ContainerName_ShouldNotStartWithForwardSlash()
    {
        var postgreSqlContainer = new PostgreSqlBuilder().Build();

        await postgreSqlContainer.StartAsync();

        postgreSqlContainer.Name.Should().NotStartWith("/"); // <= fails, the current value is `/musing_khayyam`
    }
}

I'm happy to provide a fix if it's a smaller issue and you can help me walk in the right direction.

This is not an issue. This is how Docker stores the container name internally. See the following commands:
docker run --name foo httpd
docker inspect --format '{{.Name}}' foo

We do not modify any data here; we simply forward it. I do not want to change it TBH.

Oh wow, I didn't know that! 😲 Learning never stops...
Could you image introducing a dedicated property that corresponds to the value one sees via docker -ps? If not it's also fine, just close the issue :)

As mentioned, I have no intention to change it. We do not recommend using the container name (setting it through the builder's API) anyway. In case you need to set up a container-to-container communication, you can use WithNetworkAliases(string). Or is there any other use case I am missing?

I will try whether WithNetworkAliases helps in my use case 💪🏻


Make Ping Driver To Test Uplink

Should just listen for ping commands, and on receipt, transmit an ACK

Should also emit radio pings at regular intervals


Remove dependabot config

We have both renovate and dependabot in this repo
This removes dependabot since we have better central orchestration of renovate currently
Checklist

[ ] Update changelog in CHANGELOG.md.
[ ] Make sure values.yaml and values.schema.json are valid.
[ ] (Giant Swarm) If creating a release, bump the version and appVersion in Chart.yaml.

Shouldn't you do replace.dependabotRemove: true on /github too?


ati-drivers: Restore opengl & direct rendering

Removed a collision in the nix store
Removed dependency on qt
Fixed opengl and direct rendering by correcting some link paths
Some code refactored in builder.sh
Comments added/modified

This pull request fixes #11740,#11817 and I recommend that it be considered
as a hotfix for the stable channel due to the fact that opengl
and direct rendering are broken there too.

Given that reportedly it doesn't work at all now and the patch looks good to me, I'll merge this in a few days if nobody won't object.

@abbradar I just applied this patch locally and it seems to be working well, thank you!

I probably forgot to mention that the patch also fixes a bug with sddm (related to qt 5 opengl) where you get a white screen due to opengl not functioning. And the up shot of it is that with this patch; users of ati-drivers should now be able to pull Plasma Workspaces 5 into their environment, set sddm as the default dm and migrate to Plasma Workspaces 5 if they so choose.

Yay! Thanks!
Ping me if it breaks or anyone finds something else not working.

No problem, thank you for your work ^_^

Do I understand correctly that release-15.09 has broken drivers, too?

@abbradar Yes. That is correct.

Cherry-picked to 15.09 at https://github.com/NixOS/nixpkgs/commit/a7369685453f0b8996563e51056681bb49626988

Looking forward to giving this a try, sorry I haven't been able to test anything for a few days! Fingers crossed it still works :)


fix: Adds generated code

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

v1.5.1
GitHub release

Your semantic-release bot :package::rocket:


Enhance OS Detection to Verify Arch Linux More Reliably

This pull request updates the project to enhance the detection of Arch Linux. The new version introduces a more robust detection mechanism and includes improvements in code structure and documentation.
Changes Made

Improved Detection Logic:

Added functions to read and parse the /etc/os-release file and to check for the presence of the pacman package manager. This combined approach increases detection accuracy.

Modular Code Design:

Introduced helper functions (is_arch_linux, check_os_release, check_pacman) for better code organization and readability.

Updated README:

Enhanced the README to provide clear instructions, detailed information about the tool's functionality, and usage examples.

The new README provides comprehensive information about the project, its functionality, and usage. It also includes installation instructions, code overview, and notes about potential limitations.
Need to be fixed:
With this new patch and the present you could still trick the program that you are using Arch Linux by changing the os-release file shown in the video
https://github.com/user-attachments/assets/bef89e5f-3c20-45a7-a0e1-795e0676f935

Thanks for the update and I like the improvements you have made.
Jonathan Steadman. :)


validator: add validation for scheduler cache

Add helper packages to check the state of the scheduler cache. The first and most obvious troubleshooting step is to check if the scheduler cache is clean (vs dirty, thus not sending pods to a node because the overallocation).
To do so, we rely on the tracing functionality introduced in podfingerprint package >= 0.1.0. Components computing the pod fingerprint can now expose the debug data in JSON format, which this code reads, consumes and crosschecks.
The output can tell the client (human or machine) if the scheduler cache is clean for each node, and if not, why the computation drifted.
Drifted is caused by different perspective on which pods are present on which node. There's only one key scenario on which this happen and it is not eventually self-healed: lingering terminated pods, which stay around and are terminated before the scheduler plugin starts.
Arguably, the scheduler plugin (aka the go k8s client) can make steps to make sure it gets these pods, but until (if) this happens, better to detect this scenario.
Signed-off-by: Francesco Romani<EMAIL_ADDRESS>

/hold
depends on https://github.com/openshift-kni/numaresources-operator/pull/443

Feel free to unhold when https://github.com/openshift-kni/numaresources-operator/pull/443 is ready.


GPG error: The following signatures were invalid

Hi, I am trying to install Dart from the page https://dart.dev/get-dart but 'sudo apt update' give me the following:
W: GPG error: https://storage.googleapis.com/download.dartlang.org/linux/debian stable Release: The following signatures were invalid: BADSIG 4EB27DB2A3B88B8B Google Inc. (Linux Packages Signing Authority<EMAIL_ADDRESS>E: The repository 'https://storage.googleapis.com/download.dartlang.org/linux/debian stable Release' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

Same on Ubuntu 22.04.02 as of today. Yesterday apt-get update was fine. I tried reinstalling the key:
wget -qO- https://dl-ssl.google.com/linux/linux_signing_key.pub | sudo gpg --dearmor -o /usr/share/keyrings/dart.gpg
However, apt-get update still fails:
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://storage.googleapis.com/download.dartlang.org/linux/debian stable Release: The following signatures were invalid: BADSIG 4EB27DB2A3B88B8B Google Inc. (Linux Packages Signing Authority<EMAIL_ADDRESS>W: Failed to fetch https://storage.googleapis.com/download.dartlang.org/linux/debian/dists/stable/Release.gpg  The following signatures were invalid: BADSIG 4EB27DB2A3B88B8B Google Inc. (Linux Packages Signing Authority<EMAIL_ADDRESS>W: Some index files failed to download. They have been ignored, or old ones used instead.

Fixed, details on #53045. It was a race condition while signing the stable and testing channels at the same time.


When you save a model the name is not updated

After saving a model the name in the JSON and in the upper right of the editor should reflect the saved name.

The saved/downloaded file name is not retrievable, so renaming would not work in this manner.  However, there should be a way to rename projects; I'm about to create a PR to handle that.


Run checks in cross-repo PRs

See e. g. https://github.com/krzema12/github-actions-kotlin-dsl/pull/28, the checks weren't ran.

Added pull_request: to all relevant workflows. Let's wait till we know it helps.


[$500] Sign out - Page gets unresponsive after sign out when login with Abracadabra

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

Version Number: 1.4.25-1
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:

Navigate to staging.new.expensify.com
Enter email address and click Continue
Navigate to the email and copy the login link
Paste it to new tab and change to staging
Navigate to the original tab and hit Sign out

Expected Result:
User should successfully sign out from New expensify page
Actual Result:
Page gets unresponsive after sign out when login with Abracadabra
Workaround:
Unknown
Platforms:

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

[ ] Android: Native
[x] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/93399543/8921a16f-c96b-4e36-9221-58eeae14ae2b
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01ff3aff1986d09d05
Upwork Job ID:<PHONE_NUMBER>652462080
Last Price Increase: 2024-01-16

Can this be retested on the latest staging version please

Still able to reproduce this issue in Web, build v1.4.25-6

Issue still reproducible in 25-6.

@AnshuAgarwal24 can you share console error?

I cannot reproduce the issue, but there's some weird behaviour on my side like:

upon login, only 1-2 reports are showing in the LHN + report open avatars are not showing
upon signing out and being redirected to login page, focus mode gets activated and the modal appears
post-login loading times and overall fetching is very slow and also the Abracadabra page when link is opened

Weird behaviour video
https://github.com/Expensify/App/assets/56457735/09843204-89bf-4923-bf69-a03ffb3d2d34

Could we maybe try reverting the onyx bump and see if this behaviour gets better?

I am trying a test build here and we can see if this is any better there https://github.com/Expensify/App/pull/34596

I suspect many similar deploy blockers came from Onyx. So worth trying revert

QA confirmed the fix


RangeError when creating colliders

I'm using 2D rapier.js.  When creating a collider, I sometimes see this error:
RangeError: Invalid array length
      at Array.push (<anonymous>)
      at Coarena.set (party/index.ts:12939:17)
      at ColliderSet.createCollider (party/index.ts:17125:14)
      at _World.createCollider (party/index.ts:15592:27)

It looks like the issue is coming from Coarena, where Coarena.index(handle) is returning an unexpectedly large number that exceeds the possible array length.
Relevant snippet of Coarena:
export class Coarena {
    constructor() {
        this.fconv = new Float64Array(1);
        this.uconv = new Uint32Array(this.fconv.buffer);
        this.data = new Array();
        this.size = 0;
    }
    index(handle) {
        /// Extracts the index part of a handle (the lower 32 bits).
        /// This is done by first injecting the handle into an Float64Array
        /// which is itself injected into an Uint32Array (at construction time).
        /// The 0-th value of the Uint32Array will become the `number` integer
        /// representation of the lower 32 bits.
        /// Also `this.uconv[1]` then contains the generation number as a `number`,
        /// which we don’t really need.
        this.fconv[0] = handle;
        return this.uconv[0];
    }
    set(handle, data) {
        let i = this.index(handle);
        while (this.data.length <= i) {
            // ERROR COMES FROM THIS data.push() pushing past array length limit
            this.data.push(null);
        }
        if (this.data[i] == null)
            this.size += 1;
        this.data[i] = data;
    }
}

In my case, the handle passed to set() was 2.7161131672e-312, which is translated to index<PHONE_NUMBER>.  Interestingly, the failure case is always with the handle 2.7161131672e-312.  This doesn't happen every time I call createCollider(); it only happens "after a few times".  And once it fails, it always fails with the same handle, until I restart the server, in which case it will work for a little while until it produces that same handle again.
The handle is directly coming from RawColliderSet.createCollider(), which calls into the wasm code.  Not sure whether this is an invalid handle? (so the issue is with the wasm rust code), or if the conversion to index is incorrect? (so the issue is with the js wrapper).
Thanks!

Specifically, I'm seeing these as the high and low bits of the handle:
High bits:<PHONE_NUMBER>0000000000000001111111
Low bits:<PHONE_NUMBER>1111111111111111111111
Combined:<PHONE_NUMBER>000000000000000111111111111111011111111111111111111111

This definitely looks pretty unusual :thinking:

I think this is my user error, caused by a hot-reloading server that is loading the wasm module multiple times. Closing.


nb-select dont set value

[x ] bug report
[ ] feature request
[ ] question about the decisions made in the repository

I dont konw if its is an error exactly. Sorry about that, but I decided call help here because I am search for solution for 4 days and didnt found anything.
The fact is that nb-select set value in my project dont work.
Iam using Angular 9 and Node 10.20.1
When a try set a value after it was been populatedt, nb-select dont update
My code:
html component:
                            <nb-select   formControlName="sis_id" [(selected)]="prfForm.controls.sis_id" fullWidth (selectedChange)="onSisChange($event)">
                                <nb-option *ngFor="let item of ddlSis" [value]="item.value">{{item.text}}</nb-option>
                            </nb-select>

ts component:
this.prfForm.patchValue({
  sis_id: data['sis_id'],
  sisfun_id: data['sisfun_id'],
  sisfun_idsuperior: data['sisfun_idsuperior'],
  sisfun_descricao: data['sisfun_descricao'],
  sisfun_tag: data['sisfun_tag']
});

Abpout error reprodution information requered,  do not exist,  Iam just trying  set value when I need edit a record.

For me this is working:
Component
list = [1, 2, 3]
form: FormGroup;
ngOnInit(): void {
this.form = this.fb.group({
dropDown: 2,
});
}
setValue() {
this.form.controls['dropDown'].setValue(3);
}
Html
   <form [formGroup]="form">
            <div class="form-group">
                <nb-select placeholder="Form control" formControlName="dropDown">
                    <nb-option *ngFor="let item of list" [value]="item">{{item}}</nb-option>
                </nb-select>
            </div>
        </form>

489/5000
Thanks for the answer,
Perhaps my problem is in the following definition, when I initial load the component:
   for (let i = 0; i <result.sis.length; i ++) {
     this.ddlSis.push ({id: result.sis [i] ['sis_id'], text: result.sis [i] ['sis_sistema']});
   }

I'm using id for the option value, and option text to show in the combo.
in this case, how would I use it to set a new value?
this.form.controls ['dropDown']. setValue (id);
or
this.form.controls ['dropDown']. setValue (text');

@lapereirabr
You should use:
this.form.controls ['dropDown']. setValue (id);


Library console logs "dude" when using a DatBoolean

Offending code is here: https://github.com/claus/react-dat-gui/blob/master/dist/index.es.js#L457

LOL okay, PRs welcome ;) will get to this in the next round of changes otherwise

Fixed, and deployed 4.0.2, thanks!

Hah no problem :)


98 voting pallet

Updated launch period vote for democracy to 1 day and voting period to 3 minutes for integration test

Codecov Report

Merging #111 (70f683e) into main (afb0246) will decrease coverage by 0.06%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #111      +/-   ##
==========================================
- Coverage   69.96%   69.90%   -0.07%
==========================================
  Files          27       27
  Lines        1931     1927       -4
==========================================
- Hits         1351     1347       -4
  Misses        580      580

Impacted Files
Coverage Δ

node/src/chain_spec.rs
0.00% <ø> (ø)

pallets/voting/src/lib.rs
82.97% <ø> (-0.10%)
:arrow_down:

pallets/voting/src/tests.rs
100.00% <ø> (ø)

runtime/src/lib.rs
2.77% <ø> (ø)

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


Troublesome Raspberry Pi OS experience

I'm trying to create a cluster from scratch using Raspbery Pi 3/4.
I've configured the master node (local IP <IP_ADDRESS>) by adding
cgroup_memory=1 cgroup_enable=memory

to /boot/cmdline.txt
Now, the server is up and running.
The problem comes when I try to add a worker node.
I executed this in the worker:
curl -sfL https://get.k3s.io | K3S_URL=https://<IP_ADDRESS>:6443 K3S_TOKEN=********** sh -H

This command ran undefinitely. I opened another terminal in the agent and exectued
systemctl status k3s-agent.service

This is what I got.
● k3s-agent.service - Lightweight Kubernetes
     Loaded: loaded (/etc/systemd/system/k3s-agent.service; enabled; vendor preset: enabled)
     Active: activating (start) since Tue 2023-08-08 12:08:58 CEST; 1h 44min ago
       Docs: https://k3s.io
    Process: 2462 ExecStartPre=/bin/sh -xc ! /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service (code=exited, status=0/SUCCESS)
    Process: 2464 ExecStartPre=/sbin/modprobe br_netfilter (code=exited, status=0/SUCCESS)
    Process: 2465 ExecStartPre=/sbin/modprobe overlay (code=exited, status=0/SUCCESS)
   Main PID: 2466 (k3s-agent)
      Tasks: 10
     Memory: 188.5M
        CPU: 28.837s
     CGroup: /system.slice/k3s-agent.service
             └─2466 /usr/local/bin/k3s agent

Aug 08 13:53:28 rpi3-1 k3s[2466]: time="2023-08-08T13:53:28+02:00" level=error msg="failed to get CA certs: Get \"https://<IP_ADDRESS>:6444/cacerts\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"
Aug 08 13:53:50 rpi3-1 k3s[2466]: time="2023-08-08T13:53:50+02:00" level=error msg="failed to get CA certs: Get \"https://<IP_ADDRESS>:6444/cacerts\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"
Aug 08 13:54:12 rpi3-1 k3s[2466]: time="2023-08-08T13:54:12+02:00" level=error msg="failed to get CA certs: Get \"https://<IP_ADDRESS>:6444/cacerts\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"
Aug 08 13:54:34 rpi3-1 k3s[2466]: time="2023-08-08T13:54:34+02:00" level=error msg="failed to get CA certs: Get \"https://<IP_ADDRESS>:6444/cacerts\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"
Aug 08 13:54:56 rpi3-1 k3s[2466]: time="2023-08-08T13:54:56+02:00" level=error msg="failed to get CA certs: Get \"https://<IP_ADDRESS>:6444/cacerts\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"
Aug 08 13:55:18 rpi3-1 k3s[2466]: time="2023-08-08T13:55:18+02:00" level=error msg="failed to get CA certs: Get \"https://<IP_ADDRESS>:6444/cacerts\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"
Aug 08 13:55:40 rpi3-1 k3s[2466]: time="2023-08-08T13:55:40+02:00" level=error msg="failed to get CA certs: Get \"https://<IP_ADDRESS>:6444/cacerts\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"
Aug 08 13:56:02 rpi3-1 k3s[2466]: time="2023-08-08T13:56:02+02:00" level=error msg="failed to get CA certs: Get \"https://<IP_ADDRESS>:6444/cacerts\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"
Aug 08 13:56:24 rpi3-1 k3s[2466]: time="2023-08-08T13:56:24+02:00" level=error msg="failed to get CA certs: Get \"https://<IP_ADDRESS>:6444/cacerts\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"
Aug 08 13:56:46 rpi3-1 k3s[2466]: time="2023-08-08T13:56:46+02:00" level=error msg="failed to get CA certs: Get \"https://<IP_ADDRESS>:6444/cacerts\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"

I've checked if this runs:
curl -vk https://<IP_ADDRESS>:6443/cacerts

And it connects correctly and shows a lot of info.
BTW, I've tried to run this line in https://docs.k3s.io/advanced?_highlight=raspb#raspberry-pi
sudo apt install linux-modules-extra-raspi

But it seems that package doesn't exist.
What am I doing wrong?
Extra info

This is the server
Static hostname: rpi4
Icon name: computer
Machine ID: 0f67f650c33742f3b3775200e4ee1921
Boot ID: 642c705ebc594ce8a3a34e05e309dfa7
Operating System: Debian GNU/Linux 11 (bullseye)
Kernel: Linux 6.1.21-v8+
Architecture: arm64

This is the agent:
Static hostname: rpi3-1
Icon name: computer
Machine ID: 62e0a214daa74e48b84e8b824f6945f5
Boot ID: 3bcd800aa9bc4856bde4263d0018585b
Operating System: Debian GNU/Linux 11 (bullseye)
Kernel: Linux 6.1.21-v8+
Architecture: arm64

The sudo apt install linux-modules-extra-raspi is only relevant on Ubuntu, not Raspberry Pi OS. Additionally, you need to make sure all nodes, not just servers, have the cgroup_memory=1 cgroup_enable=memory.

I've configured the master node (local IP <IP_ADDRESS>) by adding
I executed this in the worker:
curl -sfL https://get.k3s.io | K3S_URL=https://<IP_ADDRESS>:6443 K3S_TOKEN=********** sh -H

There are two different IPs here, did you typo one of them when running the command on the agent?


Update from upstream SwiftPhoenixClient

What kind of change does this PR introduce?
Bug fix, feature, docs update, ...
What is the current behavior?
Please link any relevant issues here.
What is the new behavior?
Feel free to include screenshots if it includes visual changes.
Additional context
Add any other context or screenshots.

Looks great, could use this now! Any idea on when this will be merged / released?

I tried using this version in my project, but the latest version of supabase-swift has different initializers. I was able to enable usage by editing the initializers in #22.

Currently using latest from update-upstream with realtime Presence in my project. However could only get it working when adding custom channel configuration that matches RealtimeChannelOptions type from supabase-js (See RealtimeChannelOptions in supabase-js master). Wondering if there should be some additional config type, automatic config injection in Presence, or I should just add docs @grsouza?
let client = supabase.realtime
let params = [
    "config": [
        "presence": [
            "key": profile.id
        ],
        "broadcast": [
//          "ack": true
            "self": true
        ]
    ]
]
// let channel = client.channel(.table(id, schema: "someChannel") - presence.onSync will never call
let channel = client.channel(.table(id, schema: "someChannel"), params: params) // This works fine
let presence = Presence(channel: channel)
presence.onSync {
    // Only calls if params are passed into channel
}
client.connect()
channel.join()

@foodisbeast realtime-js automatically inject params as you can see on https://github.com/supabase/realtime-js/blob/master/src/RealtimeChannel.ts#L136-L142
I think we should use the same approach.

What do you think about adding a string initializer to ChannelEvent @grsouza? Seems having a finite set of events will prevent adding Presence track and untrack (Presence docs), and Broadcast send functions (Broadcast docs).


Implement endpoint to list available users in UserApiClient.

fix #258
Implement remaining endpoint:

List available Users GET /_api/user/

https://www.arangodb.com/docs/stable/http/user-management.html#list-available-users

@modios @rossmills99 Thank you for reviewing. I will merge this and v1 should be good to go.


How can I apply customized template?

I wanna customize format of selected field and list field.
Can I use some options to apply template customized format with data value?
For example that I think(below),
selected field...
selectedFieldTemplate: function(dataItem){
    return dataItem.value + '(count: ' + dataItem.count + ')';
}

list item field...
In case of multi-select, I want to add checkbox in each item field.
listItemTemplate: function(dataItem){
    return '<input type="checkbox"/>' + dataItem.lable + '~' + dataItem.value;
}

Hi,
For the first point you want this function only apply when element is selected ?
for the second point you prefer to see a checkbox instead of ✓ ?

Hi,
Not only when element is selected, I mean some functions to customize template of each items in title and popup of Combobox. Is there any API to do this?

for the first point yeah it should be possibble, i will make this feeature before the end of the week.
For the second point, not it's not possible, because i didn't split the component in two component and i don't use

Thanks,
if the first point should be possible, It's enough to use your component in my case.
Thanks for your help!!

Take care, if you want to alter the option from outside of the multi-select for the you will need to manual reload multi-select. Options are deep copied for isolation.


Improve error on empty Config.toml file

Description:
The current error is

error: an empty configuration file is found in path '/path/to/config/file/Config.toml'. Please provide values for configurable variables

Since we have two sentences, we should have a period at the end of the second sentence too.
Also since we include the file name in the error shouldn't we say

error: empty configuration file found at '/path/to/config/file/Config.toml'. Please provide values for configurable variables.

Affected Version:
slalpha3

This error message is no longer valid after fixing https://github.com/ballerina-platform/ballerina-lang/issues/30160.
Hence, closing this.


Output to remote rsyslog problem

Hi, I have configured td-agent with remote_syslog plugin. I made data input to td-agent, in parallel I store output data to file in td-agent instance. In file I see changes, but nothing in output to remote rsyslog. Hosts file contain ip/hostname, iptables is down on both instances. Please, help me solve problem, Thanks

i have save problems

Sorry for not responding for so long.
If you still have such problems in the current version,  please reopen this issue and please provide details of the actual settings to reproduce the problems.


Provide Geocoded data

Compliments with this project!
For many applications that produce maps and/or apply spatial analysis, geocoded COVID-19 data (data with coordinate attributes/columns) would be very helpful. This sounds more complex than it actually is:

many of the produced data CSVs here, have columns like Municipality (Gemeente)/Province code and or name
the Dutch government via Kadaster-PDOK provides Open datasets for Administrative Borders (Bestuurlijke Grenzen) with those same names/codes.
GeoJSON is an ideal format for supplying geospatial data
there is ample Open Source software to convert/simplify these (GML) datasets. With little search found e.g. this script
"geocoding" is mainly a matter of JOIN-ing on Municipality/Province names/codes (i.s.o. using Geocoding backends like Nominatim ), possibly GeoPandas can be of help. e.g. https://geopandas.org/mergingdata.html

I hope this triggers interest. Eventually I could foresee some extra/derived GeoJSON files generated from the CSVs under /data/ like under /data/geocoded. Is all data here generated via GitHub Workflows/Actions?  Then contributors could also add the required geocoding steps there.
Next step are OpenAPI endpoints from this GeoJSON data. This could  be served directly from GitHub. We have a project based on OGC OpenAPI REST standards: pygeoapi where we are working on providing an Open Endpoint for COVID-19 data: https://demo.pygeoapi.io/covid-19/collections?f=html. Some Collections there already serve directly from GitHub repos, like Italy. For NL we use/proxy ESRI Endpoints, but would rather serve directly from a/this GH repo.
In theory I could do the work on this issue, but already quite occupied with the pygeoapi part...

RIVM is now providing a part of its data as geocoded data https://data.rivm.nl/geonetwork/srv/dut/catalog.search#/metadata/1c0fcd57-1102-4620-9cfa-441e93ea5604

Yes, very much aware of this activity. Some from our Open Source geo-community are involved and the services are evolving.
Still some work (for RIVM) to do:

it is indeed part of the data (aantallen_gemeente_cumulatief).
the JSON files are not GeoJSON, i.e. spatially enabled.
the geospatial data is a single layer (aantallen_gemeente_cumulatief) via WFS

But ok, that same table CSV-data, can now be downloaded via the WFS as GeoJSON (or GML KML, and even Shapefile, outputFormat=shape-zip). 355 records each with municipality border, about 26MB, think because municipality borders ("gemeentegrenzen") have not been simplified (so too many border-points):
curl 'https://geodata.rivm.nl/geoserver/wfs?request=GetFeature&service=WFS&version=2.0.0&typeName=vw_nl_covid_19_aantallen_gemeente_cumulatief&outputFormat=json' > wfs.json

Still a good start, don't know how this affects the current work/dataflows here. Can all (RIVM) CSVs here be derived from that CSV file? NICE data off course still has different source.
(Now I see a new map data-geo and related workflow scripts. Though also the data is not yet spatially enabled. That would require either using the WFS download, but then we only have municipality-level (plus very large datafiles because of the non-simplified borderpoints) that needs to be aggregated to province and country-levels.
I need to study the (Python) scripts and see how to make the files geospatial as GeoJSON as I described in the issue text above. But the ultimate solution would be if RIVM would provide the data at the detail/expanded level as here...

To be honest, I'm disappointed about the geocoding stuff RIVM worked on this week. Time is tight for RIVM at the moment. We all know and accept I think/hope. The geocoding work doesn't add anything new. We can convert the data into GeoJSON ourselves, isn't it? Shapefiles are there, cumulative numbers are there... simply join the two files and we do have these geocoded files. Like many of us did for their websites, models, and scientific publications.
Thinking aloud, what does this add to handle the pandemic in The Netherlands? The latest cumulative numbers aren't very informative. Daily changes are. However, they still provide the latest values only (and overwrite the previous counts). We still don't have access to large parts of the time series (#44). Tables with very important information are discontinued or significantly changed (like test data, and underlying medical problems). Other tables do have clear mistakes, like the province data in the PDF files. Hopefully, RIVM will prioritize on the completeness and FAIRness of the data instead of working on things we can derive ourselves. Secondly, work on easy-to-use features.
Sidenote for those who want to make the join themselves: We do have simplified geoJSON files with the municipalities in this folder: https://github.com/J535D165/CoronaWatchNL/tree/master/ext. This is the same file as they use on their news page.

@J535D165 I share your sentiment. The current offering from RIVM is half-baked, hidden among many other datasets. They have put something out quickly. Hopefully work-in-progress. Also on other aspects of the current crisis there is a need to bring together experts that build transparent/Open Source solutions. Simplest would be if RIVM/government put together teams with people like you/your team and other data/geospatial experts to unlock detailed data via downloads and APIs/web services to help other experts in their analysis. The data itself is IMHO not complicated, but indeed needs to be supplied fully temporal (time-series) and, where applicable, geospatial...Me and other geospatial folks are in contact with them, but still on the outside, basic advise, not detailed/implementation level. There are also procedures/bureaucracy that hampers technical folks "inside" to move quickly with using external expertise.

Hi @J535D165 and @justb4, can we help with Geocoded data somehow?
We have more than 1k people in our community and public Cloud infrastructure for heavy computations. I'm pretty sure we can find some people interested in this task.


Let since decorator max version apply to upgrade tests as well

@pcmanus or @smccarthy788 to review

This appears to be the behavior that every upgrade test expected anyway.

lgtm +1


Don't check configuration until user input is applied

Signed-off-by: Daniel J Walsh<EMAIL_ADDRESS>

@edsantiago @mheon PTAL

LGTM

@edsantiago PTAL
Could you check if this PR fixes your issue with the warnings?

What timeframe do you need? Will Monday be OK? I don't have a rhel8 box right now, and just wasted an hour trying to build one with the right repos to build podman. I can't get gpgme, btrfs, devmapper, and a few others; and I can't afford any more time today. I can try to find time over the weekend if it's necessary.

@edsantiago No problem.  Monday is fine.

Confirmed: the error message is gone. I managed to build v1.9.0 in rhel8, confirmed that my built image has the multi-line warning; built with your patch, the warning is gone. All system tests pass, root and rootless. LGTM, adding /hold in case there are any other pending reviews. Remove when desired.
/lgtm
/hold

/hold cancel
If this fixes our spurious warnings, LGTM on my end


Tests for ElasticSearchResults and fix for #1271

This should be merged into 0.8.8 as well. I've put it on the 1.0 milestone so someone looks at it


Needs Hard Refresh

Great job on this browser, extremely helpful for prototyping phonegap/cordova builds. I that I was unable to refresh. Selecting the URL bar and pressing go did not refresh the window, as if it new it was the same address. I'd like to suggest a small refresh icon to the right of the URL bar to do a full page reload. Thanks!

Hiya there @Aslan11 - did you ever get a chance to test this branch and see if it solved your issue? Let me know if so!

I'm going to close this out unless anyone else reports issues with this. Thanks!

Hi Stakes,
I'm having a cache issue currently.  I'm refreshing the page but it still has old JS and CSS.
Is it easy for me to build the cache branch and add it to my iPad for testing?  This isn't something I've done before :)

Hey @stakes,Frameless is not refreshing my js. Please help!

Same problem here!

Thanks guys for reporting. I don't have a ton of time to work on this right now, but @ashleyhindle if you're still interested you can absolutely build and test, and if you need help or pointers in the right direction let me know!

Still having this problem, how can you refresh now. Do I close the app or something ?

Hey @JeffreyBouva I haven't been maintaining Frameless for some time now :( if you are using it for Framer prototyping I would recommend getting into Framer's official iOS app. Thanks!


Billed Invoices - Buttons disappear from the invoice

Expected behavior:
Buttons to add payment, edit, delete  are always there.
Actual behavior:
If you click on add payment, the buttons disappear.
Steps to reproduce:
on beta site
Billing > Invoices > click on the add payment button for an invoice.   The buttons disappear when the dialog comes up.   If you dismiss the dialog with cancel, the buttons are gone.
Screenshots (if applicable):

OS and Browser:
OSX   Chrome

I'll take a look at this issue if nobody else has taken it already.

Marking in progress @BrianHC

@BrianHC any update on this?

I have found fixed the problem and am putting together a pull request.

See https://github.com/HospitalRun/hospitalrun-frontend/pull/538 for the fix
@tangollama

This problem should only happen when an invoice's total cost is zero.
When clicking "Add Payment", a new payment object would be created and then recalculating of the balance would be triggered. Since the initial value of the amount field for the newly created object is zero, we've already paid up for the zero-cost invoice at the moment of clicking the button. The buttons disappear because they are only showing for the unpaid invoices.
Considering zero-cost invoices should be rare in real cases, so this bug should be relatively harmless. Anyway, I've tried to fix it in the following pull request. The idea is simple, I just count for the saved (not new) payment objects when calculating the balance.
I'm totally new to Ember, so please correct me if I'm outright wrong.


Step 4 of @value elimination

@kyouko-taiga PTAL at the failure; we now have no hard distinction between generic value parameters and generic type parameters: id-1: id-2 could be either one.  Can you suggest an approach?

#121 has so much in it that it’s hard for me to tell for sure, but it seems likely.

On Nov 27, 2022, at 2:52 PM, Dimitri Racordon @.***> wrote:
@kyouko-taiga commented on this pull request.
I think this set of changes has been made obsolete by #121 https://github.com/val-lang/val/pull/121. Is that correct?
—
Reply to this email directly, view it on GitHub https://github.com/val-lang/val/pull/110#pullrequestreview-1195068409, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAKYINMHRX7ZPWDVPAGTQLWKPQ4DANCNFSM6AAAAAASKZRZUE.
You are receiving this because you authored the thread.


Fix logging race condition in bb-test-zfstests.sh

test-runner.py now creates a simlink to the directory
where output is stored. Have buildbot track the
log via the symlink instead of relying on
bb-test-zfstests.sh to find the output directory.
Signed-off-by: Giuseppe Di Natale<EMAIL_ADDRESS>

This can be accepted once zfs#5293 is accepted.

Updated to use the new symlink that test-runner will create in zfsonlinux/zfs#5314

Merged as:
2f0f996 Enable ShellCommand lazy logging
9efcf8d Hide test steps if they are skipped
5f5add4 Fix logging race condition in bb-test-zfstests.sh


Use of abbreviation without a definition or context

This is relatively minor, but it's also trivial to fix. You describe was is ASE near the top of this article, but when describing features used to solve specific use cases you reference "ILB ASE" without a previous reference or definition for the term "ILB". I was able to confirm the definition by reading through the related content references at the bottom of the page, but that should not be necessary. The first use of an abbreviation should always include the expanded term, and ideally a definition or link to a definition.

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

ID: ae743313-9367-b465-e31a-5beae33018d1
Version Independent ID: c0cd348d-764a-572b-d900-ff0cffe12a31
Content: Networking features - Azure App Service
Content Source: articles/app-service/networking-features.md
Service: app-service
GitHub Login: @ccompy
Microsoft Alias: ccompy

Hi @ChrisSeitzinger , thanks for your feedback! We will review and update this doc accordingly.

I see what you mean @ChrisSeitzinger and we appreciate the feedback. I've assigned the issue to the doc author for further evaluation and update as appropriate.

@ChrisSeitzinger we've updated the doc to address this feedback. Thanks!


Bug with extended level search page (Plus button on the level search pages)

Entering the filtered search options page on the level search results page containing only one level, results in generating a page with 21 of the same level.
How to reproduce:
1). Search a particular level so only it show in the search results.
2). Click the + button(filtered search options)

can confirm
related to the way the gd server handles pagination of these - affects search types 0 (only during id search) and type 10 (map pack levels)
possible solution: hide the button during these conditions


Use asciicast image link

You may be interested in embedding asciicast as image link.

Nice! Thanks.


fix(balancer): query args not forwarded bug

Summary
This PR fixes the issue described in #11325
Checklist

[ ] The Pull Request has tests

Full changelog
Replace query args handling code introduced in this commit to what it was prior to it, with one minor change. Instead of using var.request_uri, use ctx.request_uri (since the motive of the change was to not refer var)
Issue reference

Fix #11325

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.11 out of 12 committers have signed the CLA.:white_check_mark: vm-001:white_check_mark: flrgh:white_check_mark: oowl:white_check_mark: chronolaw:white_check_mark: curiositycasualty:white_check_mark: windmgc:white_check_mark: ADD-SP:white_check_mark: hanshuebner:white_check_mark: samugi:white_check_mark: outsinre:white_check_mark: zhongweiy:x: chirag-manwaniYou have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.11 out of 12 committers have signed the CLA.:white_check_mark: vm-001:white_check_mark: flrgh:white_check_mark: oowl:white_check_mark: chronolaw:white_check_mark: windmgc:white_check_mark: ADD-SP:white_check_mark: samugi:white_check_mark: curiositycasualty:white_check_mark: outsinre:white_check_mark: zhongweiy:white_check_mark: hanshuebner:x: chirag-manwaniYou have signed the CLA already but the status is still pending? Let us recheck it.

@fffonion @javierguerragiraldez Adding you since the original change was done and reviewed by you guys.
Any thoughts on this issue?

Yes. Will do @samugi

@samugi
I've been trying to run tests on my local system for a while and I am stuck at an issue.
spec/fixtures/proxy_wasm_filters/build/debug -> ~/kong/bazel-bin/build/kong-dev/wasm-cargo-target/wasm32-wasi/debug
~/kong/bazel-bin/build/kong-dev/venv/bin/resty: line 2: ~/kong/bazel-bin/build/kong-dev/openresty/bin/resty: No such file or directory
make: *** [test-integration] Error 127

Is there something I am doing wrong? I am running make test-integration. I am assuming it would also install all the required dependencies.
Could you help out here and point me in the correct direction?

@chirag-manwani I am not hitting that issue in my environment, it might be due to some problem with the build process, I would recommend, however, running the individual test you are developing, e.g. bin/busted spec/02-integration/05-proxy/32-query-params_spec.lua from the dev virtual environment.
Let me know if you encounter any issue and whether you prefer me to add a test for this instead.

@samugi I think what you suggested is run if I execute make test-integration or any test goal. I ran make clean and tried again and it started working. Will update here once I have the test working.

Added a test case for testing the fix.

@samugi Can this change be released in the next patch version of Kong 3.3.x?

@samugi Can this change be ported to the next patch version of Kong 3.3.x?

@samugi Can this change be released in the next patch version of Kong 3.3.x?

In general, we do not do this backport to the old kong community old version.

@samugi @oowl Could you approve the workflow runs once more?

The DB less integration test is failing. Should this test be skipped for db less? I am unsure of how to set the required config for dbless mode. (one route with request-transformer)

@oowl @samugi Should this test be placed in spec/02-integration/05-proxy as these tests are run when TEST_SUITE is set to dbless
spec/02-integration/02-cmd \
spec/02-integration/05-proxy \
spec/02-integration/04-admin_api/02-kong_routes_spec.lua \
spec/02-integration/04-admin_api/15-off_spec.lua \
spec/02-integration/08-status_api/01-core_routes_spec.lua \
spec/02-integration/08-status_api/03-readiness_endpoint_spec.lua \
spec/02-integration/11-dbless

I noticed that the tests I was running on local were only running for postgres. Once I made them run for dbless, the tests failed. On further search I found that the route I am creating is being created, but the plugin I am applying on that route is not.
Is there something wrong in the way I've setup the test?

@samugi @oowl Please allow the workflow once more. I've updated the tests to work for dbless mode also. All tests should pass now.

@oowl @samugi
An unrelated test case failed. Is this a flaky test case? The tests should just be re-run in this case right?
FAILED  spec/02-integration/05-proxy/10-balancer/01-healthchecks_spec.lua:1893: Ring-balancer #postgres #healthchecks (#cluster #db) #hostname #healthchecks perform active health checks on targets that resolve to the same IP -- automatic recovery #http
...ntegration/05-proxy/10-balancer/01-healthchecks_spec.lua:1995: Expected values to be near.
Passed in:
(number) 5
Expected:
(number) 10 +/- 3

Please re-run the failed workflow when you have the time.
@oowl @samugi

@samugi Added the test case in a separate file.

@samugi
All tests have passed, please merge the PR. I have one additional request though. If possible please make this change available in any patch version of Kong 3.3.x

thanks again for your contribution @chirag-manwani! As @oowl also mentioned before I believe there is no plan to backport this right now, but we will update you here if that changes.


Packaging and collateral

Keeping this open for follow ups

Plan is Outside bag is heat-sealed tear-top paper bag.


Support to pass Client CERT/Key and CA CERT

Please feel free to correct me where I might be wrong in this feature request. I am naive to how certificates work. Seems to be close but not exact to #26
Would like to see support to pass along CA Cert as well as Client Cert/Key. I am able to run a basic curl with the three files specified but getting TLS handshake failure with reg usage. Possibly need to create a PR if want it done but want to make sure I am not misusing before hand. Thanks!
$ ls -l
total 32
-rw-------  1 joseestrada  staff  2026 May  2 09:26 ca.crt
-rw-------  1 joseestrada  staff  4449 May  2 09:26 client.cert
-rw-------  1 joseestrada  staff  3446 May  2 09:26 client.key

$ curl -I "https://<registry>/v2/org/tags/list" -X GET --cacert ca.crt --cert client.cert --key client.key
HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8
Docker-Distribution-Api-Version: registry/2.0
X-Content-Type-Options: nosniff
Date: Wed, 12 Jun 2019 19:20:50 GMT
Transfer-Encoding: chunked
Strict-Transport-Security: max-age=7884000; preload

$ reg ls <registry>/org
INFO[0000] domain: <registry>/org
INFO[0000] server address: <registry>/orgs
Get https://<registry>/org/v2/: remote error: tls: handshake failure

I agree with this suggestion -- we cannot use reg because our registry requires client side PKI certificate.
If I get a chance I may try to put together a PR, but want to be sure someone will consider including it before I do.


Update to JupyterLab 4

Fixes #31
Fixes #54
Fixes #57
Closes https://github.com/jupyterlab-contrib/jupyterlab-filesystem-access/pull/32

[x] Bootstrap the update with the update script: https://jupyterlab.readthedocs.io/en/latest/extension/extension_migration.html#upgrading-extension-using-the-upgrade-script
[x] Enable toolbar items

Looking good at first:

Some dev tools errors that might be related to the update:

While the current JupyterLite version seems to be working fine accessing files from the kernel:

Using this branch with the latest jupyterlite-*packages gives the following error:

Checking with jupyterlite-pyodide-kernel==0.2.0a2, jupyterlite-core==0.2.0rc1 and the current version of jupyterlab-filesystem-access (0.5.3, the extension is built against JupyterLab 3 but activates fine in JupyterLab 4):

So this might be more of an issue with the latest jupyterlite-* packages when accessing drive content from the kernel, than an issue with this PR updating to JupyterLab 4.

Hopefully this will be fixed in https://github.com/jupyterlite/jupyterlite/pull/1227.

Getting this one in to follow-up with https://github.com/jupyterlab-contrib/jupyterlab-filesystem-access/issues/58.

Great thanks!


Add public user to web config

In exploration of adding of public user to outreach server via omero web config.
Does not work very well atm. When a new public user is created, and a new public group, the Dataset inside that group is not publicly visible, e.g. https://ome-training-4.openmicroscopy.org/webclient/?show=dataset-5405
Not sure where the mistake is.
cc @jburel @sbesson

Looking at a specific image in this dataset, https://ome-training-4.openmicroscopy.org/webgateway/render_image/53009/ works for me. Is the problem that /webclient is not in the url_filter list?

The playbook works now as expected, the url https://ome-training-4.openmicroscopy.org/webclient/?show=dataset-5405 is opening without creds in private window, thanks for the hint @sbesson . The situation is complicated by the fact that the full config is not present in our doc, see https://docs.openmicroscopy.org/omero/5.6.4/sysadmins/public.html#configuring-public-user contains only
omero config set omero.web.public.url_filter '^/(webadmin/myphoto/|webclient/(?!(script_ui|ome_tiff|figure_script))|webgateway/(?!(archived_files|download_as))|iviewer|api)'
This is not matching the real situation on ns server, which has
omero.web.public.url_filter: ^\/(api|iviewer|figure|webadmin\/myphoto\/|webclient\/(?!(script_ui|ome_tiff|figure_script|render_image_download|download_|ome_tiff_script|archived_files\/download|download_orig_metadata))|webgateway\/(?!(archived_files|download_as)))
And also, the latter (the ns situation) is not in this repo, but in the mngmt one.

Thank you @sbesson
Successfully deployed and tested on all 4 outreach servers.
E.g. https://outreach.openmicroscopy.org/webclient/
Merging


Added new people to OWNERS

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm


Change namespace to nextcloud and collection name to admin

requires:

[x] #206 merged
[x] #185 and #171 done
[x] #216  merged
[ ] #186 done

changes :

changed all references of:

aalaesar.nextcloud => nextcloud.admin
aalaesar/install_nextcloud  => nextcloud/ansible-collection-nextcloud-admin  (expected repository new name)

updated some titles

Hi @aalaesar!
As the collection PR is already merged, could you rebase this Draft? This will resolve conflicts and fast-forward to current main states, so this PR would be much smaller after all.

@aalaesar basically the conflict files have:
  collections:
    - nextcloud.admin

But ansible-lint errors saying to remove it and use full-qualified name on roles instead such as:
  roles:
    - nextcloud.admin.install_nextcloud

@aalaesar basically the conflict files have:
  collections:
    - nextcloud.admin

But ansible-lint errors saying to remove it and use full-qualified name on roles instead such as:
  roles:
    - nextcloud.admin.install_nextcloud

:+1:
Didn't got time to rebase yet 😃

LGTM
It's ready for reviewing :smiley:

LGTM =)


QA-13751 : add placeholder support for iFrameRenderer

https://jira.jahia.org/browse/QA-13751

I just realized this IframeRenderer is deprecated. You should do the changes in https://github.com/Jahia/jahia-ui-root/tree/master/src/javascript/shared/components/IframeRenderer (and use this IframeRenderer if it's not already the case)

(otherwise, changes look good :-) )

We won't use that functionality, as we have no real use case, no need to port and merge.


Stop downscaling steps if bias-correction validation fails

close #378

Looks good to me and very useful @brews 👍

Thank you! Merging.


Logged_events needs to be queried based on path id, activity id, course id & cohort id

Provide options to save  path id , activity id ,course id and cohort id directly under the logged_events node.

https://github.com/NUS-ALSET/achievements/pull/950
https://github.com/NUS-ALSET/achievements/pull/954


Circleci integration

face_recognition version: face-recognition==1.2.2
Python version: Dockerfile
Operating System: Dockerfile

Description
Hey, I'm trying to get my app working on circleCI. I am building it inside docker. I'm using the Dockerfile from this repository.
I am able to build/run app locally, but pip install fails on circle CI when building dlib?
Stack trace can be seen here: https://circleci.com/api/v1.1/project/github/Meemaw/Idify/21/output/103/0?file=true
Everything else can be found at:
https://github.com/Meemaw/Idify

Hi @Meemaw did you manage to get through the circleCI build, i'm having the same issue.
Thanks

No, I switched to travis.

Leaving this behind as none of the hits when I Googled for this problem had this as an answer: You probably need more memory. Even the xlarge size currently isn't enough in our case.
https://github.com/davisking/dlib/issues/2261#issuecomment-744115606


added update button, idk if it works

no tested

This contributor looks dangerous, @Sachaa-Thanasius - I think we perma ban him


Create LibraryManagement.py

A program that does the work of a library manager made using oops in python.

Do give Star to this repo.. happy hacking.

Thanks for merging my PR. 😊


Allow running with prepend and output

Is your feature request related to a problem? Please describe.
In short I need 2 files, one with version 0.X.X.md and one with CHANGELOG.md
Describe the solution you'd like
It should be possible to run with --prepend and --output.
Describe alternatives you've considered
Run the same command twice, once with --prepend one with --output.

Hello, thanks for submitting this issue! 🐻 This feature is implemented in 7325be84045ad376e0989a111ed3c44a3e1400ea and will be available with the next release.

Thank you for implementing!


Use a single queue in UniformStreamByteDistributor

Motivation:
The UniformStreamByteDistributor currently processes all zero-length frames, regardless of add order. This means that we would always send HEADERS for all streams, possibly taking away bandwidth for streams that actually have data.
Modifications:
Empty frames are now treated the same as any other frame except that the algorithm will pop off the any empty frames at the head of the queue.
Result:
Empty frames require no extra processing.

@Scottmitch @ejona86 PTAL

@nmittler can you rebase?

@Scottmitch PTAL

@nmittler - LGTM

Cherry-picked into master (9df16a6) and 4.1 (79ab756)


#Offtopic: Do this more often

I find very interesting to do things such as this because it's a great training on how to use github and working in teams. We shoul do this more often...

Agreed. That's why I've setup a CI, coverage measurement. @tgermain has suggested we integrate a sonar also. All that does not really make sense for a joke project like this one.. However, you're right, it's good training :)


inconsistency in planning - finding an valid plan

valid plan could not be found right after the same plan was generated.

Issue happened when I tried to make play the notes slower.
(motion was generated for Tempo=120, not for 100 )

It could be related to the interpolation. We should have a look at the generated trajectories in rqt and plotjuggler (?)

Can we close this @Flova

It is way more consistent now, so I would think so.