How to change musicSrc onPlay?

const onPlay = (audioInfo) => {
    return audioInfo.musicSrc = audioInfo.musicSrc + "&authuser=" +Cookies.get("authuser");
  }

<PlayerWithNoSSR audioLists={data} onAudioPlay={onPlay} />

Why do I need to add it after playing?
i think should map your data ?
const audioLists = data.map(({musicSrc, ...item}) => ({musicSrc: `${musicSrc}&authuser=${Cookies.get("authuser")}`, ...item}))

<PlayerWithNoSSR audioLists={audioLists} />

Why do I need to add it after playing?
i think should map your data ?
const audioLists = data.map(({musicSrc, ...item}) => ({musicSrc: `${musicSrc}&authuser=${Cookies.get("authuser")}`, ...item}))

<PlayerWithNoSSR audioLists={audioLists} />

Yeah, map should be fine in my case, I'm using it in backend to add those parameter. But I think change the URL on audio playing is better than map all of the data to add a simple parameter.

Yeah, map should be fine in my case, I'm using it in backend to add those parameter. But I think change the URL on audio playing is better than map all of the data to add a simple parameter.

i think the player should be a controlled components ,i think uptate music src by hook function, although simple, but unreasonable

i think the player should be a controlled components ,i think uptate music src by hook function, although simple, but unreasonable


BACKLOG-16296 Protect against undefined values

JIRA

https://jira.jahia.org/browse/BACKLOG-16296
Description
Prevent undefined exception

Should we add a default blank value (e.g. r?.displayName || '') or undefined is ok?

Undefined seems to be ok, we get an empty entry in the table.


Improve User Experience when using a Connector

Description
Adding a connector to the Integration Project mainly have 2 issues.

Adding a connector to a project will only add the connector to the existing workspace. Exporting and importing the same project will crash the opened Integration since the connector is not available in the imported workspace.
Most of the new users forget to create a separate Connector Exporter project as they add the connector to the workspace. Having duplicating steps is causing the bad user experience.

Steps to Reproduce
N/A
Affected Component
IntegrationStudio
Version
8.2.0
Environment Details (with versions)
Windows 11
Relevant Log Output
No response
Related Issues
No response
Suggested Labels
No response

related issue: https://github.com/wso2-enterprise/wso2-apim-internal/issues/3001

Hi all,
Please find the ETA for this as follows.
Best Case Estimate: 2023-06-14
Most Likely Estimate: 2023-06-21
Worst Case Estimate: 2023-07-07

Sent PR: https://github.com/wso2/integration-studio/pull/1225

PR merged


Warning in tests on master

PHP 7.4.
PHP Warning:  Use of undefined constant T_NAME_RELATIVE - assumed 'T_NAME_RELATIVE' (this will throw an Error in a future version of PHP) in /data/tests/Tokenizer/Transformer/NameQualifiedTransformerTest.php on line 83

hmm when does that trigger, the test is @requires PHP 8.0


cordova.plugins.zeroconf is undefined

Hello,
I'm testing your plugin to simply display the hostname (for now) of the device on Android 6.0.1 from a computer running on Ubuntu 16.04.
I'm using the getHostname function in the same exact way as shown on the readme for this plugin and the console logs tell me cordova.plugins.zeroconf is Undefined.
Would you have an idea as to why I can't get it to work?

You're remote debugging (Chrome Dev Tools for instance), right?
If you're getting cordova.plugins.zeroconf is Undefined that probably means the plugin is not well installed. Check your install. Remove and re-add the plugin if necessary.

I already tried removing and re-adding the plugin. Several times. Way too many times.
I only try to output console logs on terminal using phonegap serve --console so I don't use chrome dev tools.
I've been stuck on this for way longer than I would admit, I also tried deploying on iPhone to ensure the device wasn't the problem.

I not familiar with phonegap. Can you check install logs?
Also is cordova fully loaded when you call the plugin? i.e. after the deviceready event?

Here is the installation log :
`Fetching plugin "cordova-plugin-zeroconf" via npm
Installing "cordova-plugin-zeroconf" for android
Fetching plugin "cordova-plugin-add-swift-support" via npm
Installing "cordova-plugin-add-swift-support" for android
ANDROID_HOME=/home/me/Android/Sdk
JAVA_HOME=/home/me/Documents/jdk1.8.0_112
Subproject Path: CordovaLib
Incremental java compilation is an incubating feature.
:clean
:CordovaLib:clean
BUILD SUCCESSFUL
Total time: 1.244 secs
ANDROID_HOME=/home/me/Android/Sdk
JAVA_HOME=/home/me/Documents/jdk1.8.0_112
Subproject Path: CordovaLib
Incremental java compilation is an incubating feature.
:clean
:CordovaLib:clean
BUILD SUCCESSFUL
Total time: 1.576 secs
Subproject Path: CordovaLib
Installing "cordova-plugin-zeroconf" for browser
Installing "cordova-plugin-add-swift-support" for browser
Error loading cordova-browser
Installing "cordova-plugin-zeroconf" for ios
Installing "cordova-plugin-add-swift-support" for ios`
Yes, cordova is fully loaded when I call the plugin.
Thanks for your swift answers.

By the way,
If you want to see the code (there isn't much to see) but here's the repository : https://github.com/alambrinidis/cordova-for-spacebro. In case I made a typo or something, I triple-checked it but you know, human error.
Thank you very much.

I quickly looked at your repo. Seems ok.
But in the install logs, Error loading cordova-browser.
This plugin does not support the browser platform.
It's probably not it but just to be sure, could you remove the browser platform, remove/add the plugin and have a try.

I also thought it was nothing but I didn't try it until now.
zeroconf is still undefined. I should have tried that earlier though.
I think I'll just try removing cordova from my computer completely.
Thanks again

is cordova.plugins defined?

Yes, cordova.plugins is correctly defined.

As far as I know you have to test it via device, it won't work via browser.

@alambrinidis
I cloned your repo, built your project with Android Studio and installed the app. It's working!
I don't know what's happening on your side.
A Phonegap problem?
I would check runtime logs too.

PhoneGap serve
@JulianGarciaCastillo you're right.
@alambrinidis, from what I understand, you did not install the app, but a server was started to serve your app files. You're basically displaying a website, the browser platform which this plugin does not support.
So you need to actually phonegap install android instead.

This might actually be it.. Testing right now and reporting back. Thank you very much

This was it.
Thank you both for your time.
(Sorry)

By the way, are you building some kind of (free) app based on this plugin?
If that's the case, please let us know when you release it. Thanks.


Defects found in Accessibility Check - continue for #1353

Detailed description

Describe in detail the issue you're having.
We need do AVT(Accessibility Verification Test) for our project, I found 10 issues(7 of them are below to 1 type problem, 2 of them are belong 1 type problem) cannot be solved from my side. And I opened #1353 ,with your solution to update version to 3.51.0, issues about <ibm-table> are solved. However, a issue about <ibm-checkbox> are still remained.
Please help fixing it.

You can download the IBM Equal Access Accessibility Checker from website
"https://www.ibm.com/able/toolkit/tools#verification-tools"
to install the Accessibility Checker. If you are using Chrome, for example, after the installation, open the developer tool, and select 'Accessibility Checker'.
Element location:
<ibm-checkbox>
<input></input>
</ibm-checkbox>
problem:
Checkbox input is not in the group with another Checkbox with the name "undefined"
Related sets of radio buttons or checkboxes should be programmatically grouped
IBM 1.3.1 Info and relationships
What to do:
Group related controls of the same type by enclosing them within a  element;
OR, group related radio buttons by using role="radiogroup";
OR, group related checkboxes by using role="group";
OR, disassociate unrelated controls or controls of different types by using different "name" attribute values.

Is this a feature request (new component, new icon), a bug, or a general issue?
a bug
Is this issue related to a specific component?
no
What did you expect to happen? What happened instead? What would you like to see changed?
Fixed them so that our project could pass AVT.
What browser are you working in?
Firefox
What version of the Carbon Design System are you using?
^3.51.0
What offering/product do you work on? Any pressing ship or release dates we should be aware of?
4Q of 2020

Steps to reproduce the issue

Step one: Download the IBM Equal Access Accessibility Checker for AVT. (https://www.ibm.com/able/toolkit/tools#verification-tools)
Step two: Scan page with tabs mentioned before.
After scan(very quickly), it's obvious to see the problems.

Additional information

Screenshots or code
Notes

how can I get this fix?

@MiraYuan Hi, should be available in version 3.53.2

I have tried just now, it seems not work. Not only this not can fix the problem, the fix for  in 3.51.0 is not working too...

Who does this affect?
Blind people using screen readers who cannot see the context around the control
People with dexterity impairment using voice control

Why is this important?
Associating a meaningful label with every UI control allows the browser and assistive technology to expose and announce the control to a user. Associating a visible label also provides a larger clickable area.
Violation
Form control element  has no associated label
Each form control must have an associated label
IBM 3.3.2 Labels or Instructions | WCAG 2.1 technique H44 | WCAG 2.1 technique ARIA16
Element location

What to do
Add a for attribute to a visible label with the id of this control (e.g. <label for="controlID">);
OR put the UI element inside a visible <label> element;
OR add an aria-labelledby attribute to the control. It must point to visible text on the page that is meaningful as a label;
OR only if the design cannot have a visible label, use the title attribute to provide a label.

@MiraYuan If you put the checkboxes into a fieldset like in https://github.com/IBM/carbon-components-angular/blob/master/src/checkbox/checkbox.stories.ts#L16-L38 it seems to also work

Hi, I put the checkboxes into a fieldset like you mentioned. There are three problems happen for ibm-checkbox and one problem happen in ibm-checkbox under ibm-table.
1.
Who does this affect?
Blind people using screen readers
People with dexterity impairment using voice control

Why is this important?
Assistive technologies use labels to identify form controls. Providing more than one label for the same form control causes confusion, and may be handled differently by different browsers.
Violation
Form control has more than one label
Form controls should have exactly one label
IBM 1.3.1 Info and Relationships | WCAG 2.1 technique H44
Element location

What to do
If the for attribute references a form control, find all <label> elements with this for attribute value. Decide which is the intended label and remove or change the others;
OR, if the for attribute does not reference a form control, remove the label or the for attribute.

Who does this affect?
Blind people using screen readers
People with dexterity impairment using voice control

Why is this important?
The  of a  element provides a label or instruction for the group of controls within the . This label helps users to recognize that the controls are related. Controls grouping is most important for related radio buttons and checkboxes, but can also be useful for other sets of controls that are not as tightly related.
Violation
 element does not have a
 elements must have a single, non-empty  as a label
IBM 1.3.1 Info and Relationships | WCAG 2.1 technique H71
Element location

What to do
Place a single <legend> as the first element in the <fieldset> group. The legend must contain a brief description of the related fields enclosed by the <fieldset>. For example:

Skill Level

High

Novice

Who does this affect?
Blind people using screen readers
People with dexterity impairment using voice control

Why is this important?
Assistive technologies use labels to identify form controls. Providing more than one label for the same form control causes confusion, and may be handled differently by different browsers.
Violation
Form control has more than one label
Form controls should have exactly one label
IBM 1.3.1 Info and Relationships | WCAG 2.1 technique H44
Element location

What to do
If the for attribute references a form control, find all <label> elements with this for attribute value. Decide which is the intended label and remove or change the others;
OR, if the for attribute does not reference a form control, remove the label or the for attribute.

Problems of checkbox in
1.
Who does this affect?
Blind people using screen readers
People with dexterity impairment using voice control

Why is this important?
Assistive technologies use labels to identify form controls. Providing more than one label for the same form control causes confusion, and may be handled differently by different browsers.
Violation
Form control has more than one label
Form controls should have exactly one label
IBM 1.3.1 Info and Relationships | WCAG 2.1 technique H44
Element location

What to do
If the for attribute references a form control, find all <label> elements with this for attribute value. Decide which is the intended label and remove or change the others;
OR, if the for attribute does not reference a form control, remove the label or the for attribute.

It works well. Thanks for your quickly response!


[Rootfs] Fix name of PlatformSupport artifacts

Also PlatformSupport calls the armv6l artifacts armv7l

Ok, we'll catch this when we make experimental=true the default, soon:tm: Sorry about the mess!


[PINOT-4325] Fix auto-correction logic for consecutive failing segments

Modified createConsumingSegment() to consider whether the previous segment was completed or not, when it
tries to create a new consuming segment. If it was not completed, then the new segment is created with the
same start offset as the prev segment (or earliest available, if that is higher than the start offset
of prev segment).
If the prev segment is completed, then we attempt to create the new segment with a start offset equal to
the end offset (unless of course, that offset is not available in kafka, in which we case we pick the
earliest available offset).
In either case, a warning is printed if data is lost, and a table metric is incremented.
Added the setting of Long.MAX_VALUE as the end offset for auto-created segments. This part was missed before.
Added unit tests.

Current coverage is 64.65% (diff: 90.00%)

Merging #956 into master will increase coverage by 0.07%

@@             master       #956   diff @@
==========================================
  Files           764        764
  Lines         35927      35942    +15
  Methods           0          0
  Messages          0          0
  Branches       5388       5391     +3
==========================================
+ Hits          23200      23238    +38
+ Misses        11228      11196    -32
- Partials       1499       1508     +9

Powered by Codecov. Last update 0cca9a2...2d4c992


Write a Project Plan document

Includes outline of the solution, task allocation, scope, communication plans, mention of the project board and milestones

Initially done - possibly needs updating


Dependence on oj means JRuby needs to have C extensions enabled

In https://github.com/srbartlett/awscosts/commit/82ce80d9e8e0e08a43bb9cd40e241fa544463a24 you switched to using oj, which means when this gem is used in JRuby it requires C extensions to be enabled.
Was there any specific reason for oj? I suspect it is slightly faster than JSON...?

Hi,
The 'oj' gem was introduced by a commit in a pull request so I can't answer your question directly but from looking at the code I see no reason is use it.
Happy to accept a PR should you wish to revert that commit.


add calculator to find radius of circle by its equation

Proposal
add calculator to find radius of circle by its equation
(A clear and concise description of what the proposal is.)

i like to work on this issue


Access to Request Options

Is your feature request related to a problem? Please describe.
Unable to access request information/options. I want to access the request options, to output a cURL request when a test fails. This is useful for reporting API bugs and being able to give the developers a command that they can execute to reproduce any issue.
Describe the solution you'd like
There could possibly be a getRequestOptions method on spec, this way anyone could pull that information and transform it into any request cURL, axios, etc.
Noticed that when a test fails, pactum outputs some request details, ideally, this is the information I would want in that method.

Describe alternatives you've considered
Tried getting that information from the response object, but I was not sure how to parse the request client, as a matter of fact, it didn't seem parsable (maybe I was missing something).
Additional context
I am open to working on this feature, and would only need some guidance as to where to start. Also, get feedback in terms of the best way of doing this. Maybe it's not a new method and can be done from like a handler?

Thanks, I will check that out!

This works great!

Hello @dimitriharding ,
We can use the pactum reporters to perform custom actions. afterSpec would help you to get the required request details to work upon.
Please refer the docs for more information - pactumjs.github.io/guides/reporting.html#adding-a-reporter


1st draft implementation of pinfo/1 and pinfo2 (build on PR#20)

1st draft implementation of pinfo/1 & 2
basically delegate to gen_rpc:call for erlang process_info (notice rpc uses block_callfor pinfo/2 but not implemented yet)
tests:

call a longer running process so that Pid is still alive when initiate gen_rpc:pinfo
call a process tht immediate exit
call a living process for process status
Same on remote node.

I'll implement block_call and let you know so you update the PR! Thanks!

I've also merged #20 so you can rebase off of develop

I had a trial implementation of block_call, which I was not too sure about my approach. I am still getting used to the state machine of the project.
Instead of just scrap it I finish it off and submit as PR 26 for review.
https://github.com/priestjim/gen_rpc/pull/26
If you have time, have a look. Feel free to junk it if need to.

I checked the otp source and I can't find a good enough reason as to why pinfo/2 should block_call, so let's just leave it at simple call!

Also, I think we need some kind of organization with the test_server from the other PR and the dummy module here. Too many auxiliary modules, maybe we should consolidate?

The PRs are kinda independent of each other. To be honest, block_call looks like this is exactly the thing gen_rpc is trying to solve.
Those tests have grown a lot and are now hard to dig through.
That test_server, I was about to junk it. The original intention was to have those eval_everywhere to change the state of the test_sever then use rpc to query the sate of test_server and do the reset. But rpc query always arrives faster than the gen_rpc. Those lines from rpc are left out.
How do you want to reorg?

pinfo and that async_call PR are relatively cleaner

any idea of multicall?  ''''a multicall is an RPC which is sent concurrently from one client to multiple servers"

So for the eval_everywhere, you can timeout-poll until you get a good value. timer:sleep works fairly ok in these situations with a sufficiently large timeout (i.e. 1") - this is tests we're talking about, not production code. If you're gonna ditch the server we need to re-evaluate any auxiliary modules we need for tests.

I ditch the test server which is used in eval everywhere so far.

opt for ping-pong among test script, master and slaves.
Try to avoid overly rely on timeout so tests will run more smoothly on different environment.

Commit (PR23)
https://github.com/linearregression/gen_rpc/commit/a739418c46934bdb37b935129fd3ca68c78748cd

What about the dummy file? Can't it be integrated in the helper somehow?

Forgot about dummy.erl
I need to remove it. Don't think it is used.

dummy is now removed.


added a food api

Thank you for taking the time to work on a Pull Request for this project!
To ensure your PR is dealt with swiftly please check the following:

[x] Your submissions are formatted according to the guidelines in the contributing guide
[x] Your additions are ordered alphabetically
[x] Your submission has a useful description
[x] The description does not end with punctuation
[x] Each table column should be padded with one space on either side
[x] You have searched the repository for any relevant issues or pull requests
[x] Any category you are creating has the minimum requirement of 3 items
[x] All changes have been squashed into a single commit

Thanks for contribution @muhammadh-s, but this API has no data to use. 😅
Also, the Swagger UI documentation does not contain information about the project.


Kokoro job configuration improvements

-- delete unused linux/grpc_master.cfg job
-- switch mac jobs to use RUN_TESTS_FLAGS env var (same as linux jobs)
-- switch windows jobs to use RUN_TESTS_FLAGS env var (same as linux jobs)
-- prepare for renaming grpc_master  suite to a more descriptive grpc_basictests (on windows and mac, similar change was done on linux recently).

FYI @adelez

Known failures:
https://github.com/grpc/grpc/issues/11188


Copy directory structure recursive

Unfortunately I am not sure Dockerfile can access anything outside git repo provided by dokku. This way looks for me very powerful. It copies anything without weird rules. Yes my project have Dockerfile. Yes my project does not have private docker image.
As a result I cannot imagine simple way copy files from host's absolute path.


[ART-3878] apply elliott formatting to slack notification about possible regressions

/lgtm
nice work!

/lgtm


docs: current quickstart is not compatible with fuel-core +0.10

This issue is open as a source of information
The current quickstart uses the fuelup to install the toolchain, which currently installs fuel-core v0.10, which is not compatible with the current TypeScript SDK.
The temporary solution is to install from source code or using fuel-core version v0.9.6.
cargo install fuel-core --version=0.9.6 --force

Or use the docker image.
docker run \
    --platform=linux/amd64 \
    -v <complete path>/chainConfig.json:/chainConfig.json \
    ghcr.io/fuellabs/fuel-core:v0.9.6 \
    ./fuel-core run \
    --ip <IP_ADDRESS> \
    --port 4000 \
    --chain /chainConfig.json

This will be fixed with:

[ ] https://github.com/FuelLabs/fuels-ts/issues/453

To expand on the details surrounding the upcoming fuelup release:
Once fuelup v0.3.0 is released, fuelup will use channels as the source of truth when installing official toolchains such as latest. In this case the channel here would be used as the source of truth - fuel-core v0.10 is not used here since fuelup runs tests of newly released forc and fuel-core and determined them to be incompatible with each other.
Custom toolchains are more expressive in that you can directly specify the version of a component to install and use in a toolchain, and you will be able to switch between the official toolchain and a custom toolchain using fuelup default.


Gitea drone

Update tasks to allow Gitea to get client ID/Secret for Drone to work/implement with Gitea
Fixes: https://github.com/redkubes/otomi-tasks/issues/26

@Morriz and @j-zimnowoda I implemented your suggestions, rewrote part of the script to make it better testable. Hope all is well now?

About readability, there are principles about minimizing lines of code in a function. Rule of thumb is to extract blocks of code into meaningful function names for better readability.

@j-zimnowoda please read up on my comments here, because I feel it is very important to learn how to write good tests.

I am a bit disappointed with the results of you two pair programming and coming up with tests that are ALL not testing any of our functionality. I could not find ONE valid test in there.
So please remove them all, and make sure you use types and interfaces to enforce contracts, and throw errors when invalid data was given.
Please try to avoid inventing wheels and use micro libraries when you can feel in your bones that your problem has been solved by others. Use the force!

@Morriz Apparently you do not understand the difference between unittest and functional tests. Most of the unit test are valid.

I would really like to see my remarks implemented and move on with the release of this. Can you please proceed and just remove the tests I deemed invalid?

The changes are refactoring changes, not functional. None of those unit tests I removed tested any of the code we have. Please check your statements.


TOOLS-129 and TOOLS-112

Changelog:

rework logger
terraform info logging improved

Test:

Let's fix the conflicts and merge


List of administrators group

How to find the list of administrators group?

https://core.telegram.org/bots/api#getchatadministrators


BOOLEAN: Prove Theorem 5.8 (Sheffer stroke axiom)

The bare outline of a proof is sketched at https://teorth.github.io/equational_theories/blueprint/sect0004.html#sheffer , but one should refer to the paper https://www.cs.unm.edu/~mccune/papers/basax/v12.pdf for more details.  That proof is also computer assisted.
One should also locate the equation number for this equation (in principle this just requires running the generate_eqs_list.py script with EQ_SIZE = 6).
When done, mark the statement and proof of Theorem 5.8 with a \leanok, as well as a \lean{} tag.

I'd like to give this a try starting tomorrow, but for now I ran generate_eqs_list.py with EQ_SIZE = 6 and it doesn't seem to have generated the equation in question: https://i.imgur.com/P98JAzp.png
Is figuring out the number of the equation harder than just running the script? Is it a bug? Or did I just mess up?

Ah, there were some parentheses missing, the law should be x = (y ◇ ((x ◇ y) ◇ y)) ◇ (x ◇ (z ◇ y)).  Can you find it now?  I will fix the blueprint.

The equation number is 345169.

Great!  If you are planning to update the blueprint in any event (e.g., to expand upon the sketch of proof currently given), you can certainly add the equation number there, and also add it to Equations.lean as part of your formalization.

I am going to temporarily shelf this until after midterms. My progress so far can be seen here: https://github.com/jjtowery/equational_theories/blob/main/equational_theories/Sheffer.lean and in these Vampire-generated proofs: https://github.com/jjtowery/equational_theories/blob/main/equational_theories/Generated/VampireProven/Sheffer.lean.
First with Sheffer_Equation345169 I show that the Sheffer stroke defined as (a ⊓ b)ᶜ satisfies the 345169. Then I show that 345169 implies the Sheffer axioms with Equation345169_implies_Axiom1, Equation345169_implies_Axiom2, and  Equation345169_implies_Axiom3.
Vampire was easily able to do Equation345169_implies_Axiom1 and Equation345169_implies_Axiom2, but Equation345169_implies_Axiom2, and  Equation345169_implies_Axiom3 it was not very happy with. I tried to goad it into doing Axiom3 by giving it some extra assumptions that I could then prove, but I ended up having to give it so much to do the calculation that it wasn't making it easier at all. I ended up going through the proof given in the paper until I got to something Vampire could do, with lots of Vampire sub-proofs along the way. Probably suboptimal, and I'm not sure how to get Vampire to do something nice like in the paper. Maybe someone more experienced could help.
I believe this is technically sufficient, but I'd like to properly 'close' off by showing a BooleanAlgebra structure from an operation that satisfies the Sheffer axioms with each operation defined in terms of NAND. This is probably unnecessary, but I'd like to try. Going off of how le_trans has been, this will probably need auto-generated proofs too.
This has been super fun to think about, I've learned a ton and have enjoyed it a lot. I will get back to this if no one else does.

disclaim

Thanks for all the work on this statement!    Glad you enjoyed the experience!

This looks fun, though it looks like the hard work is already done by @jjtowery. I'll try to finish it up, should be standard stuff (the McCune &al paper refers to Sheffer's original paper!)
Not sure how to correctly make sure @jjtowery gets the credit, maybe fork and then let them PR?

claim

You could add comments in the Lean code and in the commits indicating that @jjtowery 's code was used as a starting point.

Oh hey! I was thinking of starting this back up either tonight or tomorrow but if you'd like to finish it off, please do! I look forward to seeing what your solution is because this final part of building a BooleanAlgebra instance seemed a bit more involved than what was in Sheffer's paper.

I mean I don't have a solution! I can easily leave it in your hands. It's just that this feels like pretty classic stuff: the Shaffer paper builds the "algebraic" version of what people traditionally call boolean algebra (e.g. here.
Then people separately define a <= b by a = a /\ b and prove that this is an order with the desired properties, in particular transitivity which should follow from a <= b <= c <==> a = a /\ b = a /\ b /\ c etc.
Not trivial stuff, but "textbook", though I can't say I have anything at home that details this. Probably any lattice theory textbook covers this.
I doubt I will have this finished by tomorrow though, so honestly if you wanna take a crack at this with the above hint, no worries.

Ok I did the first half, that just leaves reducing the "equational presentation" of Boolean algebras (that I called "Boolean rings") to the 3 Shaffer laws.
https://github.com/codyroux/equational_theories/blob/codyroux/boolean-ring/equational_theories/BooleanRing.lean
I'll do that tomorrow, I think, unless @jjtowery wants to deliver the killing blow there.
This is actually quite fun! With the calc and conv tactics, you can almost exactly follow the paper proofs. Indeed it's much less tedious than doing this on paper, since there's no worry that you're getting it wrong.

Almost done! The Sheffer laws imply that the magma is a boolean ring (I'm still not happy with the name) and a boolean ring is always a boolean algebra.
Now all that needs to be done is to tie it all together. I'll do that tonight, being careful to note the hard work of @jjtowery (I think over half by volume?).
I didn't use Vampire but I'm regretting it a bit. The paper proofs are quite nice though so no cleverness was required.

Oh btw: the theorem is only true the magma is non-empty, of course (but Lean cares about these things).

Perhaps you can update the blueprint to indicate this.  This is the sort of thing that having the formalization helps with.  One could imagine a very subtle error in some long argument if nobody bothered to mention that non-emptiness had to be verified at some point in order to interpret this law as a Sheffer stroke.

I'll do that later, perhaps, it's really the same thing as specifying that a group should have at least 1 element, I guess. Curiously, people often like boolean algebras to have at least 2 elements, (which Sheffer notes) but Mathlib does not.

propose PR #708


Initial commit of Complex multiplication sample. Modified sample.Json to include citests and guid, updated readme and latest code sample

Initial commit of Complex multiplication sample. Modified sample.Json to include citests and guid, updated readme and latest code sample

@mkitez  Okay to merge this?


Adds second layer HTLC output types to UtxoNursery

This PR marks the first of several to follow aimed at refactoring the persistence and on-chain handling of HTLC outputs in the utxo nursery.
We introduce two new types in this PR:

babyOutput: A struct representing a CLTV delayed output that will mature into a kidOutput after the CLTV output has been spent. HTLCs that need incubation will begin their two stage journey through the utxo nursery in this state.
CsvSpendableOutput: An interface for accessing and generating sweep transactions that spend from CSV delayed outputs. This is an extension of the SpendableOutput interface introduced during the recent breach arbiter refactoring, in efforts to modularize on chain handling.  The existing kidOutput struct now implements this new interface, and direct access to internal state by the utxo nursery is now performed through public interface methods.

Thanks @halseth and @jimpo for the reviews! I've pushed a couple of fixes, PTAL when it's convenient 🚀


Clustering and HA/redundancy on deepstream 3.0

With message connector removed in deepstream 3.0, is it still possible to configure deepstream for clustering and HA?

It isn't no. The message connector prior to 3.0 was very crude, which didn't really matter in smaller deployments. However once we built deepstreamHub we needed to find a different approach that allows deepstream to communicate alot more effectively, since the broadcasting approach becomes a significant bottle neck once you have alot of messages, topics or servers.
Because of this we ended up with a peer to peer network for deepstreams that allows them to directly communicate with each other in a smart manner. Due to the large amount of work required and usage within deepstreamHub this has become part of our enterprise offering.
You can however run hot/cold server deployments for high availability using the opensource server, so that u have no downtime during rolling upgrades and unexpected node failures!

I wish there is still open source clustering solution available for smaller deployments. Can you consider reinstating the crude message connector which as you said is ok for smaller deployments or releasing the peer to peer network but limit the number of nodes in open source deepstream server? This way open source solution available for small deployments and when scale becomes an issue, can migrate to either deepstreamHub or enterprise.

I'm disappointed that clustering has been removed from the open source project.
I understand that a lot of work went into the p2p solution, however it appears you're removing features from the community build to push the enterprise offering. This makes me less inclined to use Deepstream for future projects because I don't know what other features might be removed.
I appreciate all of the work that's gone into Deepstream, and I hope you'll reconsider reintroducing this core functionality.

I agree with John.
IMO this move will hurt Deepstream's Enterprise push, rather than
encourage it.
Deepstream is definitely a great product and I'm currently using this to
power one of my fledgling projects, and settled on it based on its core
features, Clustering being one. Removing it implies that I need to do
custom patchwork (which is daunting at this point) or looking for another
solution, which may mean abandoning Deepstream.
Any users of Deepstream who have scaled up sufficiently to pay for
enterprise accounts, will outsource their server management to you anyway -
not just for technology, but also for your expert team behind it & the fact
that they no longer need to maintain a dedicated team for server
management.
Removing Clustering, prevents users from even scaling up to enterprise
levels, to begin with, and will instead cause them to abandon Deepstream,
in favour of another solution.
Hope you all reconsider.
On 28 July 2017 at 10:00, John Wehr<EMAIL_ADDRESS>wrote:

I'm disappointed that clustering has been removed from the open source
project.
I understand that a lot of work went into the p2p solution, however it
appears you're removing features from the community build to push the
enterprise offering. This makes me less inclined to use Deepstream for
future projects because I don't know what other features might be removed.
I appreciate all of the work that's gone into Deepstream, and I hope
you'll reconsider reintroducing this core functionality.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/deepstreamIO/deepstream.io/issues/765#issuecomment-318556380,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AOK1-LDcQZAoLJtUqJ9AaUdodWznPKVlks5sSWPKgaJpZM4OlHuy
.

Thank you for your opinions, I certainly understand where you are coming from. It took us a while to come to this decision and we went through various different iterations of plans and components before getting here.
We've been dealing lately with larger and larger enterprises as well as ensuring deepstreamhHub scales well, both which requires us to dedicate the majority of our engineering team to their particular requirements. For us, this meant two things:

Catering for these bound most of our engineering capacity and kept our engineers from extending deepstream with more features
Doing this for free keeps us from growing our engineering team to have people working on new features

As a result, as you might have noticed, new features in deepstream have slowed down significantly and our response time to error reports has risen. We love deepstream as much as you do and would love to see it grow!
It is also worth mentioning that we have put in alot of effort prior to this release and going forward in making a single node as performant as possible and will continue to do so. This means we are still onpar/far exceed technologies like MeteorJS which have zero concepts of clustering and yet are still used extensively in production. Deepstream can and will easily ensure your product can accomodate large amounts of users and traffic with a single node, and we will continuously be pushing those boundaries going forwards.
For those with non commercial products or open-source offerings we would be more than happy to provide a free license, please get in contact with us via sending an email to<EMAIL_ADDRESS>And if you are using deepstream as part of a larger commercial company and are happy with it – please consider supporting us in developing it by talking to your managers about getting the clustering plugin.
@wehriam
In regards to us pulling out more features, we can guarantee that we won't be doing this again. We have an exciting roadmap to enhance core features in deepstream such as list deltas, schema/schema validation and other awesome improvements going forward, as well as multiple open source client libraries. We have also just added HTTP support and laid the foundation for other endpoints, meaning things will only get more awesome going forward!
@DhavalW
Finally, in regards to enterprise level scaling, it is also worth mentioning that we already have multiple tiers on our deepstream platform which allows millions of messages and provides a cache/database, autoscaling and other features out of the box, starting totally free and paid for tiers at a rate of $20 a month (less than the price of a small ec2 instance). So we already provide outsourcing of server management with a dedicated team at a rate that is cheaper than running a single node (not to mention the other costs). All using the exact same clients and functionality as deepstream which means moving between the two is as easy as exporting data from one and importing it to another, or vice versa.

For use case where single performant deepstream node is sufficient, any documentation/tutorial on how to implement hot standby for HA?

Also, can third-parties create plugins?

We will be releasing public costs soon, I'll make sure to update this issue as soon as that occurs.
In regards to third-party plugins, that should be fine. We don't have explicit internal APIs for generic plugins yet though, only for cache, storage, permissioning, connection endpoint and authentication. As such we can't guarantee supporting them at this time during releases, and if the plugin modifies behaviour of the server itself would also fall under the AGPL license.
Please let me know if that makes sense!

Would be good if there is plugin API so community can create open source cluster messaging plugin. There are use cases where load or scaling is not the issue but redundancy and on premise are required. Having cluster for on premise use case provide both redundancy and better performance when there is no failure. I assume deepstreamHub Enterprise on premise offering is intended for large deployment.

I would also like to know what the enterprise clustering plugin costs. We just decided to replace our Firebase setup and started migrating to deeplink. We need clustering because we have a very complex server setup in 3 different regions around the world.

@wehriam
Hi John,
could you please send me an email to<EMAIL_ADDRESS>with a few more details about your project and which company we should provide the pricing for?
Thanks,
Juliet

@marcelgoya
Marcel, could you please send me an email to<EMAIL_ADDRESS>to discuss the enterprise clustering plugin costs. Please include there a brief description of your project and the company details (ideally a website) for us to better understand your needs.
Thanks,
Juliet

@julietmatsai Just done that :)

Related note: I see in the product comparison page that there are limits for the  number of connections, messages, throughput, etc for the 'open source' product https://deepstreamhub.com/compare-products/
Are these limits defined during the build step for installers you distribute on your site, or in the actual source code? Are these just practical real world limits, or artificially enforced handicaps on the open source version?

@mattknoxca Don't bother looking into their open source version, unless you only want to use one server in production. Their open source version is basically a trial edition and they want you to use their enterprise products, which are btw very expensive because they're aimed at large companies.

@marcelgoya  Ya, disappointing. Looks like it is time to 'rethink' rethinkdb, which seems to be picking up momentum again under the linux foundation

@mattknoxca the limits are in the actual source code. The opensource version is under AGPL which basically means that even if we did try to add 'limitations' you would be able to remove them anyways.

Hi all, I've released a preview of community supported clustering at deepstream.io-cluster. Please note that it builds upon changes made in 711ba0c8161bb49c5808d38419151822a8acc707 and should be considered an alpha until a 1.0.0 release.
In recognition of deepstreamHub GmbH's contributions and business I have attempted to direct users looking for a commercially supported product to https://deepstreamhub.com/enterprise/ wherever possible.
Deepstream.io-cluster extends the base Deepstream class, and uses two sets of ports. To broadcast messages to the entire cluster, nodes use Nanomsg's pubsub protocol. To direct messages to a specific node, they use the pipeline protocol.
Clusters are easy to set up as nodes bootstrap off of each other. While each node has to connect to every other node, network usage should be reasonably efficient as most messages are routed directly.
I hope the Deepstream community finds this to be a useful intermediate clustering solution, and look forward to building it into a robust component suitable for production deployments.

@wehriam
How is the messaging different from pre 3.x deepstream? Is this more performant?
I currently use deepstream binary and not in nodejs. Will you be releasing binaries too like deepstreamio?
Instead of linking to a specific commit of deepstreamio, I wonder if possible to have deepstreamio-cluster as a plugin and propose plugin API to deepstreamio since deepstreamio currently does not have plugin API.

Hello @wehriam, thanks for putting in the effort in extending DSv3 and building a (free) clustering solution.
Could you elaborate a little bit more on the architecture of your solution? Is it similar in concept to Memcachd clustering where each Memcachd server operates independently while the client does the majority of the work? Or ... ? As a follow up, for those of use less familiar, how does this solution differs from DSv2/v3's "official" cluster solution?
Also, have you run any performance benchmarks on your solution? Do you have any preliminary ideas on how it scales?
Sorry for asking so many questions, and I understand the software is still in its infancy stage. Perhaps adding this information to README would be useful.

@layanto I like your idea of proposing a plugin API to allow extensions to DS. Have you given further thoughts on what this would look like?

Is this more performant?

Will you be releasing binaries too like deepstreamio?

how does this solution differs from DSv2/v3's "official" cluster solution?

Also, have you run any performance benchmarks on your solution?

Do you have any preliminary ideas on how it scales?

@layanto and @charleswhchan - I would appreciate any assistance you can provide to produce tangible information on questions like these. The bulk of the implementation is only about three-hundred lines of code, reviewing it will probably be more helpful than my abstract answers.
I am not familiar with the commercial cluster solution and cannot comment on how it is implemented.
Deepstream.io-cluster implements a peer-to-peer network, and nodes communicate with each other directly. Unlike a structured overlay peer-to-peer network, each node is always connected to all of the other nodes. This will be very performant, and the tests include a 16-node cluster.

Instead of linking to a specific commit of deepstreamio, I wonder if possible to have deepstreamio-cluster as a plugin and propose plugin API to deepstreamio since deepstreamio currently does not have plugin API.

Deepstream.io will become a deepstream.io-cluster peer dependency once the changes in 711ba0c8161bb49c5808d38419151822a8acc707 are part of a versioned release. I am not aware of a way to package it as a plugin.

@wehriam Interesting work! We don't support the clusterNode as an actual API, but I looked through your code and I don't think any changes we make would have any rippling affects. We won't be exposing it as an actual plugin though / have concrete APIs, because we are constantly refactoring things to reduce the amount of messages that the cluster needs to send.
Since you are using nanomsg, it would be quite hard to bundle into an executable since we actually had to add our C++ bindings into the nodeJS build itself.
If you have any questions on why an API exists / is the way it is, feel free to just ping me

Thanks @yasserf! I sincerely appreciate all of your work that made it possible. After you published the ClusterNode class it was largely trivial and took about a day to implement. A few asks, in order of precedence:

A 3.0.2 release incorporating changes from 711ba0c8161bb49c5808d38419151822a8acc707 so I can make deepstream.io a peerDependency rather than using a commit as a dependency

Any cluster-focused tests or benchmarks you could share that might be adapted for use with deepstream.io-cluster

Your thoughts on my approach to featuring deepstreamHub GmbH's enterprise offerings. My goals here are to 1) promote deepstreamHub as a commercial offering to fund your work on deepstream.io and 2) emphasize that deepstream.io-cluster is community supported. I'll let you get paid to handle the issues, I only want pull requests!

Your thoughts on how deepstream.io-cluster could be implemented without extending the Deepstream base class. Am I correct in guessing that the commercial solution takes a similar approach?

Since you are using nanomsg, it would be quite hard to bundle into an executable since we actually had to add our C++ bindings into the nodeJS build itself.

In the past I've used pkg to create installers for Windows, OSX, and Debian that distribute .node packages with the main binary. Naturally it's not as clean of a solution but it could be a viable path if there was demand.

Noticed the config in deepstream 3.1.0 includes configuration for message plugin again (was removed in 3.0). Does this mean deepstream 3.1.0 support clustering like deepstream 2.x?

@layanto I've checked and can see this was done by accident. We will be releasing v4 of deepstream soon in which we'll make sure to remove this option.
I can see that this has been added to the package-conf.yml file, meaning only users who download the binary will see this option in their config.

@yasserf Not only my own thoughts (as I am a immature developer) but just few facts about the  licensing.
If you see the history of CouchDB you will find out Apache CouchDB (merged with CouchBase) is progressing upward now and where is CouchOne only enterprise people know.
Another example is StrongLoop soulution Strong Arc that was only through subscription. They (Strongloop by IBM) have stopped that and converted that to API Microgateway and that is now open source.
I think hosted solution and enterprise solution should be paid and source code should be open.
Few advantage of open source:

Finding a bug is more important, fixing a bug is not difficult. This can be achieved if full source code is open.
Community will create plugins on open source code and that is quit important when deepstreem.io such a generic solution would be used in many application domains like finance, IoT, log, realtime analysis, fraud detection and so on.

Hey, I agree which is why all of our core value proposition is totally open source. We have also spent a couple of months now purely concentrating on revamping deepstream, client and protocol all of which is opensource. A single server can easily provide the same scale of most other opensource software and there are also opensource cluster alternatives if required!
Cheers,
Yasser

@yasserf thanks for update.

there are also opensource cluster alternatives if required!

You mean based on core deepstream.io?
Are there any comparative study done with other realtime application frame works like gun.js
Regards,
Gagan

@gagan-bansal - Deepstream.io-cluster extends Deepstream 3.1.1 and uses Nanomsg for high performance cluster communication.
It's easy to setup, used in production, and released under the same open-source license as the core Deepstream project.
We would sincerely appreciate any contributions you'd like to make, including comparative studies with other frameworks.

Thanks @wehriam I'll check deepstream.io-cluster.

V4 now supports message plugins, we just don't provide any by default. However all clustering state distribution logic is back into OS so message bus should only be a couple hundred lines of boiler plate to work!
Closing this issue as V3 is not really supported anymore other than critical fixes (things changed so much since then).


App Config Fixing Async

Description
This is just to show the async issue.

/azp run java - spring - tests

Work in Progress, keeping open

Work in progress keep open.


add support for regex file paths

we should be able to parse such that given regex, we grab all matching files.

see https://github.com/bengreenier/lconf/blob/master/Parser.js#L20


ATLAS-4321 : Ignore files generated under webapp/overlays

By modifying the .gitignore configuration file, we can ignore the files generated under webapp/overlays and avoid submitting temporary files by mistake.

Thanks @asdf2014 for the fix. Merged the PR.
Thanks @ashutoshm for the code review.

@nixonrodrigues You are welcome, also thanks @ashutoshm for the review


Hooks are not actually executed.

So like described in issue #29 I want to use the remote option to save to a repository which is not my default in the global git config.
I tried multiple approaches, but none of them work. I tried using a local git folder with the git config included and running git push and git pull via hooks, and I tried the remote repository but with setting the config via the hooks. Neither of them does what it should.
Checking the output, it seems like the hooks are not being run at all.
Just to check if I did everything right, this is what I put in my settings.json:
    "syncSettings.hooks.postUpload": [
        "git push origin"
    ]

Is there something I'm doing wrong, or is there an issue with the hooks not actually being run like they are supposed to?

What's the output in the terminal?

I meant what do you see in the terminal (Terminal panel)? (not logs of the extension in the Output panel)

Ok, so this helped. I figured one of the issues out. So it seems like the terminal is not launched in the folder of the git repo. Thus, I have to "cd" to the correct directory first, maybe that should be documented because I assumed that the Terminal session would be in the git directory by default and not the directory of my project. But it could very well be, that this is just me.
Another thing I noticed is, that the terminal is not reliably being launched on every run. I had to run upload a few times before the terminal actually is being created, and I think it might be that after manually closing it with the trash bin it is not being recreated until Codium has been restarted.

I have to "cd" to the correct directory first
I thought that might be the issue when re-reading my doc... I need to improve that. I just wonder what I was thinking without ironing that out.

that the terminal is not reliably being launched on every run
I will have to test that out.

@RayJW The newest should fix your issue. Reopen that issue if you still have the problem!


UseDataFolder intercepts too late

It seems that the UseDataFolder mod intercepts the reading of the package too late for some files.
One specific example is urls.xml. Even with a modified urls.xml in place, the client seems to open the one from the package files.
Is there any way to make UseDataFolder intercept sooner to catch these files, too?

You can remove it from delayed.txt and rename the file to 1UseDataFolder.js. This will make it run first as soon as kanan attaches to Mabi. Even then I think it may miss some files which means the real fix is improving how early kanan attaches, by not relying on waiting for Mabi to create a window. I haven't come up with a good way of doing that yet though.

Even with those steps, it still seems to miss the files. :(
Hope you can think of a solution for this.


Put back Apply for 2019 [Do not merge]

Context
Allow users to apply for 2019/2020 courses
Changes proposed in this pull request

Put back UCAS link
Remove the warning

Guidance to review

Check looks ok

Just merge on Tuesday :)

related to https://github.com/DFE-Digital/bat-infrastructure/pull/32

 Apply 2019 links on course details pages


Ollama does not use custom directory

Describe the bug

Given a home the service does not have the permissions to create files
Steps To Reproduce
Steps to reproduce the behavior:
reloading the following units: firewall.service
warning: the following units failed: ollama.service
× ollama.service - Server for local large language models
     Loaded: loaded (/etc/systemd/system/ollama.service; enabled; preset: ignored)
     Active: failed (Result: exit-code) since Wed 2024-11-20 12:17:40 EST; 1s ago
   Duration: 1min 21.931s
 Invocation: 1cc42576b5d146808b1ec8945474556b
    Process: 28042 ExecStart=/nix/store/g8l9kbff2sk2fr6xkhhvdg953n64mdw8-ollama-0.3.12/bin/ollama serve (code=exited, status=200/CHDIR)
   Main PID: 28042 (code=exited, status=200/CHDIR)
         IP: 0B in, 0B out
         IO: 0B read, 0B written
   Mem peak: 1.9M
        CPU: 39ms

Nov 20 12:17:40 Mythra systemd[1]: Starting Server for local large language models...
Nov 20 12:17:40 Mythra (ollama)[28042]: ollama.service: Changing to the requested working directory failed: Permission denied
Nov 20 12:17:40 Mythra (ollama)[28042]: ollama.service: Failed at step CHDIR spawning /nix/store/g8l9kbff2sk2fr6xkhhvdg953n64mdw8-ollama-0.3.12/bin/ollama: Permission denied
Nov 20 12:17:40 Mythra systemd[1]: ollama.service: Main process exited, code=exited, status=200/CHDIR
Nov 20 12:17:40 Mythra systemd[1]: ollama.service: Failed with result 'exit-code'.
Nov 20 12:17:40 Mythra systemd[1]: Failed to start Server for local large language models.
warning: error(s) occurred while switching to the new configuration

nixos-config on  main [!] took 29s
❯ cat hosts/mythra/ollama.nix
{ config, ... }:
{
  services.ollama = {
    enable = true;
    openFirewall = true;
    user = "ollama";
    group = "ollama";
    home = "/home/ollama";
    models = "${config.services.ollama.home}/models";
    loadModels = [
      "openchat"
      "codellama"
    ];
  };
}

nixos-config on  main [!]
❯ ls -lah /home/
total 36K
drwxr-xr-x  6 root    root   4.0K Nov 20 11:56 .
drwxr-xr-x 20 root    root   4.0K Nov 19 16:54 ..
drwx------  2 root    root    16K May 16  2024 lost+found
drwxrwxrwx  2 ollama  ollama 4.0K Nov 20 11:56 ollama
drwx------ 50 redhawk users  4.0K Nov 20 12:17 redhawk

Expected behavior

I've given 777 permissions and made sure the groups are correct.
Screenshots

Additional context

Metadata

Notify maintainers
@abysssol @dit7ya @elohmeier

Note for maintainers: Please tag this issue in your PR.

Add a :+1: reaction to issues you find important.

.

.

Yeah, creating a user/group/home is not disabling DynamicUser, PrivateUsers, RestrictNamespaces, driving the unit crazy…
Here's a workaround for you, works for me with rocm:
{ config, lib, ... }:
{
  services.ollama = {
    enable = true;
    # ... your stuff goes here ...
    user = "ollama";
    group = "ai";
    home = "/var/lib/ollama";
  };
  systemd.services.ollama.serviceConfig =
    let
      cfg = config.services.ollama;
      ollamaPackage = cfg.package.override { inherit (cfg) acceleration; };
    in
    lib.mkForce {
      Type = "exec";
      ExecStart = "${lib.getExe ollamaPackage} serve";
      WorkingDirectory = cfg.home;
      SupplementaryGroups = [ "render" ];
    };
}

Okay I wasn't crazy, thanks.


Allow parameters to be set with export

Parameters can be set with export key=value and viewed with env.
Closes #33.

Hey, good catch with the 0! That's an easy fix.
Can you show me the full query that threw that error?

Hey @jexp what do you think of handling the eval stuff by having a flag -e for starting cycli in "evaluate exports" mode? With the changes above:
$ cycli -e
> export nums=[x**2 for x in range(5)]
> env
nums=[0, 1, 4, 9, 16]
> UNWIND {nums} AS n RETURN n;
   | n
---+----
 1 |  0
 2 |  1
 3 |  4
 4 |  9
 5 | 16

15 ms

Hmm that would mean depending on which mode you run cycli with your scripts would work or not? I think the eval thing is something on a case-by-case basis rather.

Would it be possible for the eval code to access existing parameters? Like env['nums'] ?

Yeah, that's a good point about scripts. I was trying to avoid having a separate keyword. :) But I like your idea of using a flag for the export command itself.

I think I'm going to stick with the -e flag to start cycli in "evaluate export" mode despite your (@jexp) concern about script compatibility. Because anything you do in the default mode (where it uses json.loads) should be compatible with eval mode. For example, setting constants such as strings or numbers will be the same whether it's passed to json.loads or eval:
>>> json.loads('54')
54
>>> eval('54')
54

>>> json.loads('"Tom Hanks"')
'Tom Hanks'
>>> eval('"Tom Hanks"')
'Tom Hanks'

Same with maps and collections:
>>> json.loads('{"name":"Nicole"}')
{'name': 'Nicole'}
>>> eval('{"name":"Nicole"}')
{'name': 'Nicole'}

>>> json.loads('[1,2,3]')
[1, 2, 3]
>>> eval('[1,2,3]')
[1, 2, 3]

So you can run your scripts in -e mode to ensure compatibility. Can you think of any exceptions to this?

Btw I added the ability to access variables by key.
> export age=54
> env
age=54
> env["age"]
54
> env['age']
54
> env['lol']
>

Alright, new plan is just to use eval all the time since anything that you'd throw at json.loads can be handled by eval as far as Cypher syntax is concerned.

Merged with https://github.com/nicolewhite/cycli/commit/453343643ea0f29b198fe37e5310efd8b974ff57.


⚠ Bofrost.at has degraded performance

In beb6b4d, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1829 ms

Resolved: Bofrost.at performance has improved in ef36fb9.


Find undoc nits

This is a replacement for #4136.

I also wrote manpages for the two commands that were missing.


How to do inference on custom test samples

i have 4 files
image.png
lidar.bin
lid_to_cam: 0.08088629 -0.99590131 -0.04047205 -0.15610122 0.06293044 0.04562682 -0.9969744 -0.3785559 0.99473472 0.07809463 0.06636309 -0.59070911 0. 0. 0. 1.
cam_intrinsic:<PHONE_NUMBER>7 0.<PHONE_NUMBER>3 0.<PHONE_NUMBER>2<PHONE_NUMBER>3 0. 0. 1.
i am testing MVX-Net : https://github.com/open-mmlab/mmdetection3d/blob/master/configs/mvxnet/README.md
while running  python demo/multi_modality_demo.py demo/data/kitti/kitti_000008.bin demo/data/kitti/kitti_000008.png demo/data/kitti/kitti_000008_infos.pkl configs/mvxnet/dv_mvx-fpn_second_secfpn_adamw_2x8_80e_kitti-3d-3class.py checkpoints/dv_mvx-fpn_second_secfpn_adamw_2x8_80e_kitti-3d-3class_20200621_003904-10140f2d.pth --show
i think infos.pkl file is where i can add my custom camera params
while loading *pkl in memory
i got these matrices and their shapes
P0 (4, 4)  P1 (4, 4)  P2 (4, 4)  P3 (4, 4)  R0_rect (4, 4)  Tr_velo_to_cam (4, 4)  Tr_imu_to_velo (4, 4)
how to override these values with my lidar to cam 4*4 matrix and internsic 3*3 camera matrix
# LiDAR to image conversion
if box_mode_3d == Box3DMode.LIDAR:
for item in info['calib']:
print(item, info['calib'][item].shape, "\n")
rect = info['calib']['R0_rect'].astype(np.float32)
#Trv2c = info['calib']['Tr_velo_to_cam'].astype(np.float32)
Trv2c = np.array([0.08088629, -0.99590131, -0.04047205, -0.15610122, 0.06293044,
0.04562682, -0.9969744, -0.3785559, 0.99473472, 0.07809463, 0.06636309, -0.59070911, 0., 0., 0., 1.]).reshape(4, 4)
#P2 = info['calib']['P2'].astype(np.float32)
P2 = np.pad(np.array([649.65825827, 0.,<PHONE_NUMBER>3, 0.,
656.18334152,<PHONE_NUMBER>3, 0., 0., 1.]).reshape(3, 3), (0, 1))
tried to replace trv2c and P2 but still projected boxes to the image are incorrect

Simply replacing lidar2img with your lid_to_cam here? If that doesn't work, try replacing lidar2img with your lid_to_cam @ cam_intrinsic (you may need to pad cam_intrinsic to 4x4)?


injecting ctor of IScopeStore implementation causes circular reference error

Hi,
I have a db repository that is registered in the startup with AddSingleton.  I want to use this db repository for accessing persisted scope configurations and implementing IScopeStore.  When I try to inject it in the ctor of my IScopeStore implementation I get a circular reference error at runtime.  How can I get hold of the registered db repository in the IScopeStore?  Is there a particular pattern that needs to be followed?
Best Regards,
Brent

There is no particular pattern, but the norm is to inject the DbContext or a wrapped DbContext into IScopeStore. Unfortunately the information that you've given us isn't enough to deduce the problem. Perhaps a start would be to show us how you're adding your services to the DI and also the code snippets of each the ctors of each of those services.

Thank you for your response.  While putting together the code bits you requested I found a different injection into the db repository class ctor that was causing the problem.  This is no longer a concern.
Best Regards,
Brent


Added plastitanium walls and windows

About the PR
In addition to already existing square plastitanium wall, this PR adds diagonal plastitanium wall, square and diagonal plastitanium windows both in destructible and indestructible variants.
Why / Balance
More sand in mapping sandbox
Technical details
N/A
Media

https://github.com/user-attachments/assets/05cf056b-541e-4997-9725-2d1ca9416b36
Requirements

[x] I have read and I am following the Pull Request Guidelines. I understand that not doing so may get my pr closed at maintainer’s discretion
[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

Just pointing out that you filled the changelog point of PR wrong, so if it gets merged you won't appear in changelogs

a CL isn't needed for something like this, it's fine

Thank you for your first contribution! If you're on our discord, feel free to check in to get the contributor role.


Local Npm module "grunt-contrib-watch" not found-error

When user has already installed grunt-contrib-watch via npm before installing grunt-express, npm won't install it under grunt-express/node_modules (npm/npm#1341) which leads to the following:
> grunt express
>> Local Npm module "grunt-contrib-watch" not found. Is it installed?

However, other than the error, everything seems to work as normal.
Steps to repro:
Gruntfile:
module.exports = function (grunt) {
	grunt.initConfig({
		express: {
			test: {}
		}
	});
	grunt.loadNpmTasks("grunt-express");
}

> npm install grunt-contrib-watch
> npm install grunt-express
> grunt express
>> Local Npm module "grunt-contrib-watch" not found. Is it installed?

I had solved this problem.
grunt.loadNpmTasks('grunt-contrib-watch');
grunt.loadNpmTasks('grunt-express');
the watch plugin must be ahead.


Plotting with a for loop

I'm trying to produce multiple line plots, one for each column in my data, by looping over the columns. Nothing gets displayed in Jupyter Lab. Is this possible to do?
Python 3.6
Jupyter Lab 1.0.2
plotly==4.0.0
plotly-express==0.4.0
Code sample:
for stat in stats:
    px.line(data, x = 'sequence', y = stat, color = 'category', height= 200, title = stat)```

Short answer: add .show() to the end of the call.
Long answer: px.<whatever>() functions return a Figure object. If this function call happens to be the final call in a Jupyter cell, then the figure will display itself, otherwise it's "just another object". To force the figure to display itself, call .show() on it.
Longer answer: there's a long doc page about this here https://plot.ly/python/renderers/
happy plotting!

PS I strongly recommend upgrading to plotly version 4.1.1 as there's a nasty bug in 4.0.0

Worked like a charm. Thanks for the quick help!


Add MapBox location search

This PR adds location search via MapBox and wires it up to the Leaflet map. I've deliberately refactored the MapBox functionality to live outside of the component; this will both allow us to easily use it across multiple components and will also help with bringing the core functionality upstream to vue-toolkit (which is on my to-do list).

The TEMPO field of regard includes Canada and Mexico (and Cuba, Bermuda, and maybe a touch of Haiti and the Dominican), so we should include those too. Once we have the shape file from the TEMPO team we may want to restrict search to within the field of regard, but let's not worry about that for now. (Even locations inside the field of regard could have no data because clouds, depending on the date range.)

@patudom I've updated to include the other countries inside the field of regard. Agreed that we can revisit what to include once we have s shapefile from the TEMPO team.

I don't know if this is just a css issue, but the dropdown with the location matches doesn't show up for me, so I can't test the "go to" functionality.

Do you have your .env file set up? If you don't, you won't get any results since the API key won't be in the request (you should be able to reuse the one from the solar eclipse story).

Just rebased to remove conflicts.

Yep, .env file was my issue. Thanks!


ci: remove stale config for node 4 and below

We do not need the tooling for node 4 and below. Also, this commits lets us have, named LTS tags. This should speed up the CI even further.

LGTM :+1:


Certain repos fail silently

Works with other repos but the following fails/freezes:
$ fetch --repo="https://github.com/Jannomag/Yaru-Colors" --ref="20.10.1" --source-path="/Themes" /tmp/yaru-themes
Downloading git reference "20.10.1" of https://github.com/Jannomag/Yaru-Colors ...

It fails also with --commit, --tag, --branch etc.
Is there any way to debug what is happening?

Are you able to git clone that repo locally?

Yes of course. Did you try to clone it and to run the command? I suspect you would get to the same conclusion.

Ah, I didn't realize that was an open source repo I had access to! Most people use fetch with private repos.
I can indeed confirm the bug. Not sure of the cause, and am too buried at the moment to dig in. If anyone has time to look into this, PRs are welcome!

Is there any flag or any other way to get a debugging feedback from fetch?

No, not currently. Better logging is something we'd like to add.

I'm unable to reproduce this, and several new tags were created shortly after this ticket was raised related to --ref.  I suspect this isn't an issue anymore

@ddnexus I looked into reproducing this and was unable to. This seems have possibly been fixed by updates to fetch. Closing out this issue, feel free to reopen if you encounter it again.


Pow operator complex32 type UT failure on Windows

🐛 Describe the bug
(Windows only) Pow operator gives incorrect result in UT test_binary_ufuncs_xpu.py::TestBinaryUfuncsXPU::test_pow_xpu_float16.
#798 is to fix this failure. However, additional overhead was introduced in type cast so we need to record this.
The failure is related to the cast of complex half type in kernel. If we convert with opmath_t{}, other ops like log will also gives incorrect results.
Versions
torch-xpu-ops: https://github.com/intel/torch-xpu-ops/commit/47cbc58452e74f70afb5e7f108ff8d7ecc329f21
pytorch: c8626a4e1f0553c8a9af32515555409d151a00c0

This is a bug due to the compiler. For internal user, please track with JIRA CMPLRLLVM-62734 .

tracked in https://github.com/intel/torch-xpu-ops/issues/1195


Error when querying an empty table with unique constraints

Including the following expression in my ClojureScript project:
(-> {}
    (rel/mat [[:from :Thing] [:unique :a :b]])
    (rel/transact [:insert :Thing {:a 1 :b 2}])
    (rel/transact [:delete :Thing [= :a 1] [= :b 2]])
    (rel/q [[:from :Thing] [:where [= :a 1] [= :b 2]]]))

causes this error in the browser console:
Uncaught TypeError: Cannot read properties of null (reading 'cljs$core$IFn$_invoke$arity$1')
    at eval (dataflow.cljc:1368:61)
    at Function.G__123169__2 [as cljs$core$IFn$_invoke$arity$2] (core.cljs:4757:24)
    at eval (core.cljs:10843:15)
    at eval (core.cljs:5686:36)
    at eval (core.cljs:5686:35)
    at Object.eval [as cljs$core$IReduce$_reduce$arity$3] (core.cljs:5690:24)
    at Function.eval [as cljs$core$IFn$_invoke$arity$3] (core.cljs:2570:17)
    at Function.G__124171__2 [as cljs$core$IFn$_invoke$arity$2] (core.cljs:10858:11)
    at Function.G__123169__2 [as cljs$core$IFn$_invoke$arity$2] (core.cljs:4757:13)
at eval (core.cljs:4200:31)

Thanks for the report @happy-river, I believe this is fixed in master but will test the repro and work on a patch release.

Fixed in 0.1.7


[Fern's Documentation] Improve the readme.md based on inspiration from appsmith

Take inspiration from https://www.appsmith.com/blog/write-a-great-readme and
https://github.com/appsmithorg/appsmith

Also worthy inspiration (make it so easy to click and try it): https://github.com/microsoft/typespec

helpful graphics


Decide what needs an RfC

We should decide on a set of changes that should always need an RfC. I haven't come up with an exhaustive list which I'm happy with (so I'm filing an issue to discuss stuff as opposed to writing an RfC).

My opinion:
What definitely needs an RfC:
(I'm only putting objective stuff here, subjectivity will get us back to where we were)

New language additions, or tweaks to existing language features, including unstable language features.
Changes to stable APIs that can be noticed externally. "noticed" does not include benchmarks. "noticed" includes situations where new functionality is added to an API (without breaking how it used to work), since this is similar to the "stabilization of APIs" point below
Stabilization of APIs where the last iteration was not a product of the RfC process. Stabilization PRs must link to the RfC that finalized their design.
Changes to the RfC process itself, the code of conduct, or other community guidelines
Breaking changes to APIs which are widely used, for some definition of "widely used" which I haven't come up with yet
Decisions on guidelines for the naming of functions, the order of parameters, and similar bikeshedding

What probably should use an RfC anyway:
(these are mostly subjective, and hence the points are simply guidelines)

Breaking changes to unstable APIs which have a tendency to pull the rug from underneath users (something like this one, even though that was made to stable APIs). Ideally the change should be made in such a way that people who haven't updated to it will be notified by a compile error (either via a temporary lint, or via renaming of functions or something), however such changes should still be discussed.
Changes which undertake a major refactoring of an unstable API
Changes which may cause significant performance loss in an API or a specific use case of an API
Changes to widely-used lints

Thoughts? Neither of these lists seem to be complete to me.

FWIW:

New language additions, or tweaks to existing language features, including unstable language features.

Sometimes tweaking existing features is just fixing old flaws.
Plus, after you say a RFC is implemented, and you may later find that you need more things to totally support that RFC.

Sometimes tweaking existing features is just fixing old flaws.

Well, we would need some objective guideline to identify these. And generally language changes are breaking, so it's easier to just blanket require an RfC.

The people with commit access don't even follow the existing rules. Adding more rules won't change that.

What existing rules?

The rule they don't get tired reminding everyone but themselves of: Changes to stable APIs require an RFC.

Dupe of #35?

In this case I don't know what happened, but everyone is allowed to make mistakes. Let's not turn this into a slugfest and instead look ahead to see how we can make these rules more concrete.

@P1start New issue since times have changed. What required an RfC last year was a smaller subset than now.

@Manishearth Either this issue or #35 should be closed, then. Traditionally, the earlier issue is kept open, but I'm fine either way.

everyone is allowed to make mistakes

Merging this straight away was no mistake. They wanted to get this change in before beta so they disregarded all established rules because it would have been inconvenient. Don't try to spin this any other way.

This discussion is going nowhere, and is totally tangential to the original topic. If you want to discuss what happened in that issue, do it somewhere else.
While I was spurred by that incident to file this, I've been confused about the RfC process for a while in this regard and either way such a set of rules is necessary IMO. Let's focus on that, here.

So some thoughts:

This does seem like a dup of #35 to me :)
I've definitely been wanting to clarify the rules here too. In particular, I think we've been leaning towards too many RFCs lately. It seems too heavyweight for every API addition to go through the RFC process; RFCs ought to be reserved for deprecations and "major" or cross-cutting additions. For other changes, a lighterweight process should suffice (more thoughts on that to come).
Bug fixes which make silent changes to semantics ought to be advertised but do not necessarily require an RFC.

To be clear, I'm referring here only to backwards compat changes -- after all, there shouldn't be any other kind. (The whole "order of arguments" thing seems to me to be a kind of one-time event, and doesn't fit into the above criteria.)

(OT: DUDE @P1START YOU'RE BACK!!!!)

I would love if every change got huge community feedback and productive discussion.
However, in reality most community members don't follow the RFCs repo, and adding more RFCs certainly isn't going to help with that.  Or even if a change gets lots of responses, it's often just a gut reaction without much reflection. Which is fair, really. We're all busy. We don't have time to think about someone else's ideas all day. Best case scenario you get tons of bikeshedding.
Really I feel like most changes are best handled by the staging process. You try something in nightly. If someone notices a problem, you revert it. No harm no foul. We just have extraordinary pain right now because everyone is on the nightly.

+1 to everything that @Gankro said.

Yes, a hearty :+1: to @Gankro . I've been a little quiet on this issue because I couldn't figure out how to articulate it, and that's exactly how I feel.

I feel very similarly to @Gankro.
I used to be able to read basically everything that happened in this repo, but the massive proliferation of both RFC PRs for increasingly small changes as well as hundreds of issues has made that impossible, and I'm pretty active!

+1 to everything that Niko said
On Apr 7, 2015 11:24 PM, "Niko Matsakis"<EMAIL_ADDRESS>wrote:

So some thoughts:

This does seem like a dup of #35
https://github.com/rust-lang/rfcs/issues/35 to me :)
I've definitely been wanting to clarify the rules here too. In
particular, I think we've been leaning towards too many RFCs lately.
It seems too heavyweight for every API addition to go through the RFC
process; RFCs ought to be reserved for deprecations and "major" or
cross-cutting additions. For other changes, a lighterweight process should
suffice (more thoughts on that to come).
Bug fixes which make silent changes to semantics ought to be
advertised but do not necessarily require an RFC.

To be clear, I'm referring here only to backwards compat changes -- after
all, there shouldn't be any other kind. (The whole "order of arguments"
thing seems to me to be a kind of one-time event, and doesn't fit into the
above criteria.)
—
Reply to this email directly or view it on GitHub
https://github.com/rust-lang/rfcs/issues/1041#issuecomment-90608742.

We've since grown a lot of language about this, and now we've got a whole README section dedicated to this, so closing.


Location.prototype.reload leaks a global "errors"

Hey,
I'm not precisely sure why, but calling window.location.reload leaks errors to the global scope:
> require("jsdom").jsdom().parentWindow.location.reload()
undefined
> global.errors
[ { type: 'error',
    message: 'NOT IMPLEMENTED: location.reload',
    data: null } ]

Adding some sort of an automatic globals checking to your test suite can catch this quickly in the future.

PS. This is with Node v0.11.15 and JSDOM v3.1.1.

Huh, I think our raise call should actually emit on target, instead of this, since raise then sets this.errors, which may be the global scope instead of the given NOT_IMPLEMENTED(target). Not sure if that's the cause of the bug, haven't checked much into it yet.

Blah, in general raise() is annoying. I want to kill it and replace it with something like a new event on our virtual console. Hope to do that "soon" but in the meantime a quickfix patch might work fine.

Added a PR here for the target fix, seems like the tests pass, however we seem to have broken something in frames already in 3.1.1 (or earlier).


How to debug slow downloads?

I have 2 clusters built exactly the same only one with Antrea and another with calico. The Antrea cluster is slow to pull images etc. How do I debug this?

Hello @NiranEC77!
I'm afraid I need more information. I don't think image pull will go either through Antrea or Calico, as that is usually done at the node level.
I guess not only image pulls but generally bandwidth could be slower. Since we seem to have evidence of slowness both in container and host networking, I would:

verify whether bandwidth in a container is radically different from the bandwidth you get on the host
if considerably and consistently slower, then I would proceed to troubleshoot Antrea.
2.1) test bandwidth between two containers on the same node
2.2) test bandwidth between two containers on different nodes
2.3) test N/S bandwidth, on multiple nodes, and compare the,
According to these results, we might infer where the bottlneck is
if there is no significant difference in bandwidth between nodes and containers, then the issue might not lie in container networking, and we should start looking at host setup. Therefore it might be useful to understand a bit more about how host networking is configured.


Incrementing version

Initial 3200 support got versioning out of order.  This should
put latest back where it should be.

@tadpol


Resume a download task has a Throwable.

com.liulishuo.filedownloader.exception.FileDownloadHttpException: response code error: 412,
request headers: If-Match: "853934bff57cc1:624d"
Range: bytes=6350674-
Cache-Control: no-cache
response headers: Date: Tue, 16 Aug 2016 01:21:02 GMT
Content-Length: 1306
Content-Type: text/html
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
It,s has a throwable when i run your demo to resume a download task.

In the demo project, URLs are from the Internet, there occur the response code is non-[200,300) is normal, It just presents what you can meet when you occur such problem.

but i try to remove the " If-Match" from the  http header ,it's running ok.

This problem is more likely to be server-side.

In FileDownloader every ETags(which would be used in the value of "If-Match") must be got from the server( FileDownloader never generate it by local), So if you receive 412 because of can't match ETag in "If-Match", it more likely the problem in the server.
In the official document, we may get the response status code 412, because bellow conditions in request-header match failed:
If-Match
If-Modified-Since
If-None-Match
If-Range
If-Unmodified-Since

Normally, If FileDownloader provides the ETag isn't the latest one in the server, FileDownloader will receive the response status code 200, and FileDownloader will start the task from the length-0, otherwise FileDownloader will receive the response status code 206, and FileDownloader will resume the task from the breakpoint.

In the current version(0.3.4) FileDownloader, you can handle such the reponse status code by following way:
Step 1. clear the ETag stored in the filedownloader database : FileDownloader.getImpl().clear(downloadId, targetPath).
Step 2. start the task normally.

@xiejinglan any problem?


python311Packages.reolink-aio: 0.5.15 -> 0.5.16

Diff: https://github.com/starkillerOG/reolink_aio/compare/refs/tags/0.5.15...0.5.16
Changelog: https://github.com/starkillerOG/reolink_aio/releases/tag/0.5.16
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 234255 run on x86_64-linux 1

5 packages built:

home-assistant-component-tests.reolink
python310Packages.reolink-aio
python310Packages.reolink-aio.dist
python311Packages.reolink-aio
python311Packages.reolink-aio.dist


Questions about the inference code （need  model.eval()）

I use the ‘Airline_demo.py’ to test the images and the original file can get normal results.  But when I add Premodel.eval(), the result is 0（other parameters remain the same）.
without model.eval()

with model.eval()

hmmmm, I had not tested this though, this may affect some normalization but I am not sure. if no .eval() works then I recommend to just leave it so?

When I export onnx using torch.onnx.export,  the bn layer exports in eval mode by default，  If the onnxruntime inference is used, the result is incorrect.  And when converting to tensorrt, it also prompts that the BN layer is in TRAINING mode, which makes it impossible to convert. So I think I still need to check this issue.
Error when converting tensorrt。Official Answers：  https://github.com/NVIDIA/TensorRT/issues/3457#issuecomment-1817477998

yeah sorry, that is indeed something we missed...

Thank you, I look forward to you being able to solve this problem.


WIP: add initial travis yaml

Don't actually merge. Just for review meeting.

Let's add this little fella:


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Logo Proposal / Icon for MediaLoader

a big hello friend, I have noticed that your logo does not have a logo yet, if you allow me I can design a Logo / Icon for your application if it is your total pleasure.

Very nice. You can start your work. My friend. If you need to know some repository information, you can ask questions at any time.

Thank you very much, in advance I went through your blog where it gives the full description of this android application http://jiajunhui.cn/project_mediaload/#more and found enough information to start my proposal I will return when I have designed something, see you later

Good afternoon it's a pleasure to greet you and come back again but this time with the icon designs for your android application. this design each piece has been created for this application and in the same way as this application works that can load images, music, audios and videos. then I will be inspired to represent all these functions in the same logo. Here is the result with 2 different styles.

Sorry, I've been busy working for the last two days. The design is very beautiful. I prefer the first one to the above.

Does he like it? Would he stay with that same one like this? or would it make any change to the text color? to know if I can send you the files PSD, PNG, EPS, SVG, AI

I think the color match is pretty good. Very good, no more change of the design.

ok very well that you have liked this logo of all those that show you ... now you can close the Issue. I will now upload all the editable files for you.

All right, thank you very much.

Hello here are the loaded files ready to use if you do not want more. You can download them now. Thanks to you
FILES MEDIALOADER
Esta obra está bajo una Licencia Creative Commons Atribución 4.0 Internacional.

hello friend and send the files please send me an email when it is added to your repository please that good you have liked I am always at your order.


Triangulation error for polygons with holes

I couldn't find an open issue for this, but it was reported in the forum by a user using GeoJSON files:

https://groups.google.com/forum/?hl=en#!topic/cesium-dev/HfwbCQPi7CI
He says the errors are very common with these types of polygons.

Also reported here:  https://groups.google.com/forum/?hl=en#!topic/cesium-dev/b7nCByVXyKs
example.geojson

Not identical, but related to #2788.

Also reported here: https://groups.google.com/forum/?hl=en#!topic/cesium-dev/SKn6LUR906g

https://groups.google.com/forum/?hl=en#!topic/cesium-dev/wNDxpEPK6QQ
sample-geojson.txt

Improved in #3998.

I'm going to close this and open a new issue. The GeoJson files were fixed, but one still has an issue written up in #4000. The KML triangulation still fails because some of the holes share vertices or edges with the outer ring.


[Linux] App freezes when playing a song

Bug
When I select a song, the app freezes for about one minute.
Steps to reproduce the bug
I am using Arch Linux with i3 Window Manager. When I try to play a song, the song is loaded and then played without any problem. However, the GUI freezes for a while (as well as the mouse pointer shape inside Kaku's window, although the pointer itself still moves).

YouTube
Which track format are you using?
best audio
Is there any error coming from Inspector?
No errors, only warnings.

OBS.: I tried to use the application on xfce4 instead of i3wm and it worked just fine! So it has something to do with the interaction with i3 :/


[WiP] improve load_examples

CATEGORY
Choose one

[ ] Bug Fix
[x] Enhancement (new features, refinement)
[ ] Refactor
[ ] Add tests
[ ] Build / Development Environment
[ ] Documentation

SUMMARY
related to #7472, longer term we will generate the examples by exporting
them into tarball as in #7472. In the meantime, we need this subset of
the features:

allowing specifying an alternate database connection for examples
allowing a --only-metadata flag to load_examples to load only
dashboard and chart definitions, no actual data is loaded

Codecov Report

Merging #7773 into master will decrease coverage by 0.07%.
The diff coverage is 45.31%.

@@            Coverage Diff             @@
##           master    #7773      +/-   ##
==========================================
- Coverage   65.89%   65.81%   -0.08%
==========================================
  Files         459      459
  Lines       22023    22061      +38
  Branches     2418     2418
==========================================
+ Hits        14512    14520       +8
- Misses       7391     7421      +30
  Partials      120      120

Impacted Files
Coverage Δ

superset/data/country_map.py
25.71% <10%> (-1.56%)
:arrow_down:

superset/data/random_time_series.py
21.42% <10%> (-1.65%)
:arrow_down:

superset/data/birth_names.py
100% <100%> (ø)
:arrow_up:

superset/config.py
94.04% <100%> (+0.03%)
:arrow_up:

superset/data/tabbed_dashboard.py
34.37% <100%> (ø)
:arrow_up:

superset/data/energy.py
100% <100%> (ø)
:arrow_up:

superset/connectors/connector_registry.py
87.87% <100%> (-0.7%)
:arrow_down:

superset/data/unicode_test_data.py
100% <100%> (ø)
:arrow_up:

superset/connectors/sqla/models.py
82.46% <100%> (+0.37%)
:arrow_up:

superset/data/world_bank.py
100% <100%> (ø)
:arrow_up:

... and 18 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 d08efd3...1b249b5. Read the comment docs.


Handle prover errors

Description
Resolves #346.

Handles unwrap calls, either by removing them or making sure before that the worse case never happen.
Handles division by zero errors.
Handles out of bounds errors.

Type of change

New feature

Checklist

[x] Linked to Github Issue
[x] Unit tests added
[ ] This change requires new documentation.

[ ] Documentation has been added/updated.

[ ] This change is an Optimization

[ ] Benchmarks added/run

[x] Handle division by zero
[x] Replace map_err with from and simplify

This is heavily outdated, we can re open it later when we need it


Publish to npm?

Hello, this is a friendly reminder to publish 1.4.0 to npm, I'm not sure if it has been forgotten or if there is some bugs that needs fixing. :smiley:
(This is not a bug report)

haha thanks, fixed!


getSegmentData - Orientation around 0 of spectral values

Hi @jdbcode ,
I am using the getSegmentData(lt, index, delta, right) function with NBR index, and having some troubles in understanding the orientation around zero of the output segments values.
I tried running:
var segInfo = ltgee.getSegmentData(lt, index, 'all')
and got this result for pixel A:

Then I tried running:
var segInfo = ltgee.getSegmentData(lt, index, 'all', true)
and got this result for pixel A:

For final comparison I tried running:
var segInfo = ltgee.getSegmentData(lt, index, 'loss')
and got this result for pixel A:

So what I am wondering is whether the ‘right’ parameter set to ‘true’ is not doing its job here (flipping the values to their natural orientation around zero) or am I not using it correctly?
Thank you!
Best,
Agata

Hello! Me again, but I am really using your module and indeed thanks for creating such an interesting implementation and useful APIs.
Still in the getSegmentData function, I noticed that you increment of 1 every start year:
return ee.Image.cat([startYear.add(1), endYear, startVal, endVal, mag, dur, rate, dsnr])
So you basically assign every vertex to the segment at the left of the vertex. May I ask why did you make this choice? Is it in order not to have the endYear of a segment coincide with the startYear of the subsequent segment? Also the duration it is still returned as endYear - startYear so I found it a bit hard to wrap my head around it at first, so I wanted to ask you whether is there a computational reason behind this.
Thank you!

Please separate these questions into different issues. I'll get back to you when I'm off vacation.

Yes, this seems to be a bug.
Only default false is working. The logic to handle an input boolean is not WAI. Here is an idea for how it should be handled:
var getSegmentData = function(options){
  var _options = {right: false};
  if (typeof options == 'boolean') {
    _options.right = options;
  }
  print(_options.right);
};

getSegmentData(true);

Before making the change, will need to determine if this will break anything calling getSegmentData, like getChangeMap.

Script to test the changes: https://code.earthengine.google.com/0ef186eed77e8ff910b82ae1b4a64c41

Closed by #15


feat: Axis sort in the Bar Chart V2

Background
This PR intends to introduce a new control that XAxisSortControl and a new post-processing operator. The goal is to resolve whether the axis could be sorted by the x-axis or any metric.
Before introducing this feature, let's talk about some of the current sorting logic. There are two kinds of sorting logic on the current master branch.

order by on the main query if Sort By is set on the control panel

order by on the main query and the sub-query if Series limit and Dimensions is given.

Both of these sorting methods are sorting on query data results, which means that these sorting occurs at the database stage. The limitation of this approach is that we cannot sort the pivot results. For example, timeseries charts(echart version) are pivoted charts.
Purpose
Imagine that there are request for such analysis, but the data sorting is kept to a fixed metric(in the other words, the database should return static topN):

Bar chart should sort the bar by one of several metrics, for example, there are sum(sales), max(sales) in the metrics, but the max(sales) should be sorted.
Bar chart should sort the bar by the x-axis values.

This PR is designed for this purpose.
Limitation
The current design doesn't support multiple series(dimensions control in the control panel). The reason is that the extra query should be provided for this use case.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

/testenv up

Sorting on the 2v bar graph is not working. Any suggestions for correction.

Mix chart need Axis sort too.


Efficiency in displaying multiple attributes from the same entity

Checklist

[ x] I am running the latest version of the card
[ x] I checked if there isn't another feature request opened with the same request
[ x] I checked that the feature is not already available in the dev branch

Is your feature request related to a problem? Please describe.
Firstly, want to say thanks for the card -fantastic work, it's the only graph card I've found that is able to graph attributes as well as the state of an entity. I have found however that when graphing multiple attributes from the same entity, for example the current and set temperature from a climate entity (I also graph another entity) then this can cause quite a delay in rendering the graph (there are over 5,000 data points for each attribute).
Having profiled the page the delay is spread fairly evenly between the three API calls and three runs through of the updatehistory function.
Describe the solution you'd like
Would it be possible to recode the function to deal with multiple attributes from the same entity more efficiently? In theory only one API call should be necessary but it would also be possible to only loop through the data once also.
Thanks again!

Thanks, I know it's not perfect but I won't do that. I would have to rewrite most of the logic and I won't. I chose maintainability over performance.


Census Individual: Update routing of arrive in UK

What is the context of this PR?
Updated routing of arrive in UK question on the census individual schema for Eng/Wls.

Introduced a new CENSUS_MONTH_YEAR_DATE when building schema to allow the date comparisons of MonthYear dates.
Updated the Census date.

How to review
Ensure:

If census date is 13 October 2019, then routing is as follows:
If the answer to 'When did you most recently arrive in the UK?' is before October 2018 and the age is 3 & over, then route to main language question
If the answer to 'When did you most recently arrive in the UK?' is before October 2018 and the age is under 3, then route to national identity question
If the answer to 'When did you most recently arrive in the UK?' is after October 2018 but before November 2019, then route to intend to stay question.
If the answer to 'When did you most recently arrive in the UK?' is October 2018, then route to 'Did you arrive in the UK on or after 13 October 2018?'

Waiting on Donna to confirm what happens when:

If the answer to 'When did you most recently arrive in the UK?' is after October 2018 and after November 2019, then route to ?

Quick launch for WLS schema

 Update routing of arrive in UK, offset by 1 year (Eng/Wls)

The date is June 2019 not October :)

The date is June 2019 not October :)

Have now been updated to 13 October 2019.

Waiting on confirmation about date validation from Donna.

If the answer to 'When did you most recently arrive in the UK?' is after October 2018 and after November 2019, then route to ?

Is this a typo, or can this be simplified to "after November 2019"?


Simplify Storage Secrets

This simplifies our manifests by using an envFrom block to pull in secret env vars instead of needing to define them manually in the deployment / worker RC. Keys in the secret have been renamed to all caps for env var conformity

Docs: Create/Edit the pachyderm-storage-secret