Change minSdk version at flutter aar build.

Use case
In usual case with flutter main project, minSdk version can be configurable via editing build.gradle of android/.
But in case of flutter module (aar) it cannot be possible because .android/ directory is auto-generated whenever building module.
Proposal
Please provide option for building flutter with modified minSdk or some configurable way to change minSdk version at flutter build aar.

Hi @wangmir, Thanks for filing the issue.

in case of flutter module (aar) it cannot be possible because .android/ directory is auto-generated whenever building module.

Labeling this issue as a valid feature request to be able to configure the SDK version for a flutter module.

@maheshmnj Thanks, I'll wait for the update.


Creating & Fixing GitHub Actions

Setup actions for

Deployment
Testing
Publishing

In the README.md the badge show failing because i already uploaded the version


Upgarding ElasticSearch for Elassandra

Hi,
The latest release of Elassandra contains Elastic Search version 2.1.1.
I want to upgrade elastic search to the latest release i.e 2.3.4 so that i can use kibana latest release i.e 4.5 for elassandra.
I am unable to find any information on the same.
Please provide steps to upgrade.
Thanks.
regards,
Chinmaya

Hi,
Upgrading elasticsearch require to merge elassandra and the last version of elasticsearch. There is about 100 elasticsearch modified classes from elasticsearch 2.1.1 to merge with elasticsearch 2.1.1+. I plan to do this upgrade for septembre 2016, but you can try it if you want.
Thanks'
Vincent

Hi Vincent,
Thanks for your reply.
If we use elassandra on production, any team or some one would be there to support us for any issues?
Thanks.
Chinmaya

Hi Chinmaya,
Yes, we plan to deliver production support by the end of 2016 with strapdata, a new company supporting elassandra.
Moreover, elassandra will be presented at the cassandra summit 2016 at San Jose.
Thanks,
Vincent.
Le 24 juil. 2016 à 18:11, chinmaya24x7 a écrit :

Hi Vincent,
Thanks for your reply.
If we use elassandra on production, any team or some one would be there to support us for any issues?
Thanks.
Chinmaya
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Any news about the merge with elasticsearch 2.1.1+ ?
I would like to give this project a try but I am scared of the idea of not being able to use the desired version of elasticsearch or cassandra (as they are embedded in elassandra).
Thanks!
Maxime

Next release of Elassandra will be based on Elasticsearch 2.4 + Cassandra 2.2.8, probably by the end of November (and upgrade to cassandra 3.0.last by the end of 2016).

Waiting for ES 2.4 as well. I want to use the  Update By Query plugin that was introduced in 2.3 and replaces the deprecated (since 2.0) plugin.
Shoham

Also waiting for Elastic Search 2.4.
The "end of November" date is still relevant ?

Yes,  it should be available by the end of November, it's currently under testing.

Elassandra release 2.4.2 is available.
It includes units test support and plugins build.


Modify CMakeLists.txt to configure and build googletest in build, rather than source, directory.

This PR modifies the test CMakeLists.txt in order to (correctly) build googletest in the build directory. This solves a longstanding issue whereby repeated builds could be "poisoned" by the googletest source in the test source directory. Additionally, these changes now allow users to use the "Ninja" build tool to configure and build the SYCL-BLAS.

Looks fine to me!


Refresh package-lock.json file with optionals

PR summary
As @bessbd had in one of his previous PRs the package-lock.json file has some "optional": true parameters that are necessary for publishing a new tag.
Note: An existing issue is required before opening a PR.
PR Checklist
Please make sure that your PR fulfills the following requirements:

[x] The commit message follows the
Angular Commit Message Guidelines.
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] New tests
[x] Build/CI related changes
[ ] Documentation content changes
[ ] Other (please describe)

What is the current behavior?

What is the new behavior?

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

Thanks for the quick reviews @vmatyusGitHub and @eiri! I'm about to merge this.

Thanks for the quick reviews @vmatyusGitHub and @eiri! I'm about to merge this.


Character Creation Checking Macro

Skill total = 650?
Know total = 250?

Because of CP options this cannot be checked easily in a useful manner.


Blank page after log in

Problem
After a user recovered his account with passphrase, it showed the blank page like the picture. He tried to clear his chrome browser cache and cookies and recovered his account again, connected a VPN, recovered his account on IE browser, it still did not work.

Expected Behavior
After recovering account with passphrase, the page can be displayed normally
Steps to reproduce

Recover account with passphrase
It shows blank page

@MaximusHaximus Do I recall correctly that someone on the engineering team went ahead and completed this recently? Just wanted to make sure incase it's still waiting for design.


Index order after .Contract and .Contracts

I am trying to use .Contract and .Contracts to check the results after SVD. After the SVD, the labels in S, U, Vdag are such that they can be directly used in .Contract and .Contracts.
# Create a rank-3 tensor with shape [2,2,6]
M = cytnx.UniTensor.arange(2*2*6).reshape(2,2,6)\
.relabels(["a","b","c"]).set_name("M")
# 1. Permute the indices to ("c","a","b") ordering,
M.permute_(["c","a","b"])
# 2. Set rowrank=1, so that "c" is the row index,
# and "a", "b" are the column indices.
M.set_rowrank_(1)
M.print_diagram()
-----------------------
tensor Name : M
tensor Rank : 3
block_form  : False
is_diag     : False
on device   : cytnx device: CPU
          ---------
         /         \
   c ____| 6     2 |____ a
         |         |
         |       2 |____ b
         \         /
          ---------

S, U, Vdag = cytnx.linalg.Svd (M)
U.print_diagram()
S.print_diagram()
Vdag.print_diagram()

-----------------------
tensor Name :
tensor Rank : 2
block_form  : False
is_diag     : False
on device   : cytnx device: CPU
          ---------
         /         \
   c ____| 6     4 |____ _aux_L
         \         /
          ---------
-----------------------
tensor Name :
tensor Rank : 2
block_form  : False
is_diag     : True
on device   : cytnx device: CPU
               ---------
              /         \
   _aux_L ____| 4     4 |____ _aux_R
              \         /
               ---------
-----------------------
tensor Name :
tensor Rank : 3
block_form  : False
is_diag     : False
on device   : cytnx device: CPU
               ---------
              /         \
   _aux_R ____| 4     2 |____ a
              |         |
              |       2 |____ b
              \         /
               ---------

It I use .Contract, it works
US =cytnx.Contract(U,S)
US.print_diagram()
USVdag =cytnx.Contract(M1, Vdag)
USVdag.print_diagram()
Diff = M-USVdag
print(Diff.Norm())
-----------------------
tensor Name :
tensor Rank : 2
block_form  : False
is_diag     : False
on device   : cytnx device: CPU
          ---------
         /         \
   c ____| 6     4 |____ _aux_R
         \         /
          ---------
-----------------------
tensor Name :
tensor Rank : 3
block_form  : False
is_diag     : False
on device   : cytnx device: CPU
          ---------
         /         \
   c ____| 6     2 |____ a
         |         |
         |       2 |____ b
         \         /
          ---------

Total elem: 1
type  : Double (Float64)
cytnx device: CPU
Shape : (1)
[2.70749e-14 ]

But if I use .Contracts, the order of the label is not the same as the original UniTensor M
USVdag =cytnx.Contracts([U,S,Vdag])
USVdag.print_diagram()
-----------------------
tensor Name :
tensor Rank : 3
block_form  : False
is_diag     : False
on device   : cytnx device: CPU
          ---------
         /         \
   a ____| 2     2 |____ b
         |         |
         |       6 |____ c
         \         /
          ---------

So I would have to premute_ if I want to calculate the difference.

Generally, you should always do permute to make sure two tensors you want to compare has the same order ( this is so that you can explicitly know what you are comparing)
permute is O(1), so there is no need to worry about adding an extra line!


vint32mf2_t and some other types seems violate the constraint LMUL ≥ SEW/ELEN when ELEN = 32

Is this intentional or did I get something wrong?
This constraint may come from the requirement in the spec that VLEN >= ELEN.

You are correct. The compiler will need to disable the intrinsics that use those types when ELEN=32. We can't just remove the types from the spec just because ELEN might be 32. They are needed to support some widening/narrowing conversions for ELEN>=64. So it needs to be determined at compile time if the types exist.

So the table below needs some modifications?
https://github.com/riscv-non-isa/rvv-intrinsic-doc/blob/master/rvv-intrinsic-rfc.md#data-types

Yes https://github.com/riscv-non-isa/rvv-intrinsic-doc/pull/114


push Nuki v. 1.4.1 to stable

RE-CHECK!

RE-CHECK!

RE-CHECK!

Automated adapter checker
ioBroker.nuki

[ ] :heavy_exclamation_mark: [E152] common.dataSource type has an invalid type push,pull

Add comment "RE-CHECK!" to start check anew

@smaragdschlange I merge now but please fix the comment!


Remove or document the restriction that index must have at most 1 shard + 1 replica for the plugin to work

There is a hard validation in code (in FairRescoreBuilder.java) that checks that the index has only 1 shard (+1 replica).
This means that the plugin is unusable for bigger indexes, which for performance (and/or reliability) reasons need more than 1 shard (or 1 replica) when deployed (like in a production environment).
If this is an unavoidable limitation of the algorithm or the elasticsearch api used by it, please document it clearly in the readme / userguide (currently there is no mention about this), as for many potential users I think this is a very important consideration, which should be known upfront.
If on the other hand this is an avoidable limitation, and the code can be changed/improved so it works with multiple shards, then please consider improving it in this direction.

Sorry for the late reply. I think the restriction is not needed, but we will look into it.


New explainer and type registry

Co-authored with Sven Sauleau

Merging, though note that all of this is still under discussion.

Note, in particular, the language around registries may be iterated on, and hasn't been reviewed by everyone in the champion group yet.


Fix hyp3 metadata for ingest

Description
(NOTE: removes extra white space from changelog)
Currently, the field weather_model is written to the top level json.
It comes out looking like this:
{
    "label": "S1-GUNW-A-R-064-tops-20220218_20220206-015020-00119W_00032N-PP-c915-v2_0_6",
    "location": {
        "type": "Polygon",
        "coordinates": [
            [
                [
                    -118.39874869085138,
                    32.01295364440911
                ],
                [
                    -118.51960475874401,
                    32.54023395004941
                ],
                [
                    -118.51633125623869,
                    32.54107418154587
                ],
                [
                    -118.74603647034824,
                    33.53782825263393
                ],
                [
                    -117.83011198388779,
                    33.68583931752407
                ],
                [
                    -117.80378783104793,
                    33.567591541588826
                ],
                [
                    -116.86974867684492,
                    33.71080044087251
                ],
                [
                    -116.81256194118323,
                    33.438490049937734
                ],
                [
                    -115.99039499940679,
                    33.55964522347833
                ],
                [
                    -115.85061854534331,
                    32.856958119810386
                ],
                [
                    -115.85261458166339,
                    32.85638896595082
                ],
                [
                    -115.68834841364777,
                    32.02666834493761
                ],
                [
                    -116.52517776141728,
                    31.909401449665673
                ],
                [
                    -116.54815750525835,
                    32.019142204076694
                ],
                [
                    -117.46656347458119,
                    31.883025551704147
                ],
                [
                    -117.52454076946138,
                    32.14807184510674
                ],
                [
                    -118.39874869085138,
                    32.01295364440911
                ]
            ]
        ]
    },
    "creation_timestamp": "2023-05-09T03:44:05.443201Z",
    "version": "2.0.6",
    "metadata": {
        "ogr_bbox": [
            [
                -118.74603647034824,
                31.883025551704147
            ],
            [
                -115.68834841364777,
                31.883025551704147
            ],
            [
                -115.68834841364777,
                33.71080044087251
            ],
            [
                -118.74603647034824,
                33.71080044087251
            ]
        ],
        "reference_scenes": [
            "S1A_IW_SLC__1SDV_20220218T015005_20220218T015035_041961_04FF34_65A4"
        ],
        "secondary_scenes": [
            "S1A_IW_SLC__1SDV_20220206T015006_20220206T015035_041786_04F91C_FABC"
        ],
        "sensing_start": "2022-02-18T01:50:05.000000Z",
        "sensing_stop": "2022-02-18T01:50:35.000000Z",
        "orbit_number": [
            41961,
            41786
        ],
        "platform": [
            "Sentinel-1A",
            "Sentinel-1A"
        ],
        "beam_mode": "IW",
        "orbit_direction": "ascending",
        "dataset_type": "slc",
        "product_type": "interferogram",
        "polarization": "HH",
        "look_direction": "right",
        "track_number": 64,
        "perpendicular_baseline": 34.9459
    },
    "weather_model": [
        "HRRR"
    ]
}

Want weather_model within the metadata subfield. This data will then be searchable and accessible as umm_json through the daac.

@jlmaurer @cmarshak can you look through existing PRs and merge those that are ready?


[ZEPPELIN-1060] validate user before saving

What is this PR for?
Zeppelin notebook permissions change has an issue while reconfiguring permissions by clearing textbox
What type of PR is it?
[Bug Fix]
Todos

[x] - Validate user list before saving
[x] - getPermissions from server again before showing popup

What is the Jira issue?

ZEPPELIN-1060

How should this be tested?

I log in as user 'admin'
I create a notebook 'Untitled Notebbok 1' as user admin
I setup permissions of the notebook as owners = admin, readers= admin, writers= admin and click save button
It works file
Now I again try to give owners permission to 'All users' by clearing owners field. Since in step-3 owners = admin ; it allows me to save these changes successfully
Now I again try to toggle permissions of the notebook. Since in step-4 I cleared owners field, it should allow all users to change permissions. But it is not happening, instead it gives an error box that only User = [] has sufficient permissions

Questions:

Does the licenses files need update? n/a
Is there breaking changes for older versions? n/a
Does this needs documentation? n/a

Ready for review
CI fails for  #5326.1, Which is unrelated.
-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running org.apache.zeppelin.python.PythonInterpreterTest
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/home/travis/build/apache/zeppelin/zeppelin-interpreter/target/zeppelin-interpreter-0.6.0-SNAPSHOT.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/home/travis/build/apache/zeppelin/zeppelin-interpreter/target/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/home/travis/.m2/repository/org/slf4j/slf4j-log4j12/1.7.10/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
log4j:WARN No appenders could be found for logger (org.apache.zeppelin.interpreter.Interpreter).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.399 sec <<< FAILURE! - in org.apache.zeppelin.python.PythonInterpreterTest
testClose(org.apache.zeppelin.python.PythonInterpreterTest)  Time elapsed: 0.29 sec  <<< FAILURE!
java.lang.AssertionError: null
	at org.junit.Assert.fail(Assert.java:86)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at org.junit.Assert.assertFalse(Assert.java:64)
	at org.junit.Assert.assertFalse(Assert.java:74)
	at org.apache.zeppelin.python.PythonInterpreterTest.testClose(PythonInterpreterTest.java:168)

Results :

Failed tests:
  PythonInterpreterTest.testClose:168 null

Merging this if no more discussion.


Prior Art: Reviewers Editions

Noticed the "versioning" bit in CONTRIBUTING. Folks may be interested in the "Reviewers Edition" system I cooked up for functional prose:
https://www.npmjs.com/package/reviewers-edition-parse
The intended use case was legal forms on commonform.org, but I've applied it to tagged releases on GitHub, as well.
For those coming from SemVer:

No x.y.z software-style numbers, but still machine-readable. SemVer-looking version numbers applied to functional prose can't mean what SemVer says they mean. Versions with different meaning ought to look different.
No 0.y.z "hole" in the semantics.
Direct focus on the message intended from maintainers to consumers, rather than vague functional criteria that only get fuzzier when applied to prose, rather than code. New Reviewers Editions tell users what they should review and assess, based on the Reviewers Edition of the copy they're already using.

Thanks for pointing out this prior art. It is very close to the twist on SemVer we came up with:

BEIPA CONTRIBUTING
Reviewers Editions

MAJOR version when objectives of agreement change. A company using BEIPA would have to fully evaluate a new major version to determine fit.
When authors recommend users review a new edition in its entirety to ensure it meets their needs, they increase the edition number.

MINOR version when agreement changes do not change objectives of agreement but are substantial enough to merit legal scrutiny from any user.
When authors recommend users review at least the new or changed parts of a new edition, they increase the update number.

PATCH version for corrections which any user would likely want to accept with minimal additional review.
When authors make only typographic or other, minor corrections that users need not review, they increase the correction number.

I like your take because it's more general, and even more accurate for the potential version 2 of BEIPA (the objectives haven't really changed, but it is a big enough change to fully re-evaluate).
I'm not really thrilled with lack of 0 and .. The result, eg BEIPA 2e or eventually BEIPA 2e1u5c and similar looks really foreign, or rather computer-y and maybe (ironically) not intended for consumption by most humans, though I appreciate the direct focus on the message.
Maybe we should use your definitions but stick with SemVer formatting. 🤔


role.setPermissions or role.edit doesn't work

Please describe the problem you are having in as much detail as possible:
I updated to master, and my working bot that creates a role and updates its permissions doesn't do that anymore.
I can get
message.guild.createRole({
    data: {
        name: 'USER-' + message.author.id,
        color: args[0],
        permissions: []
    },
    reason: 'Hex Bot'
})

To create a role with no permissions, but if I put a .setPermissions or .edit in the .then it will create the role with two permissions it wasn't told to give. (External emojis and add reaction)
And trying to run
role.edit({
    data: {
        color: args[0],
        permissions: ['ADMINISTRATOR']
    },
    reason: 'Hex Bot'
}).catch(error => client.catch(error))

Doesn't edit the permissions. same with setPermissions, it works in stable though.
And it does update the color.
Further details:

discord.js version: Master (12.0.0-dev #317a352)
node.js version: v8.2.1
Operating system: Windows 10 x64 & Generic Linux x86_64
Priority this issue should have – please be realistic and elaborate if possible:
Medium priority, Needs to be fixed before v12 is released but its still not a big problem for in-dev

[x] I found this issue while running code on a user account
[x] I found this issue while running code on a bot account
[x] I have also tested the issue on latest master, commit hash: #317a352

I found this issue last night, and waited until this morning to update Discord.JS and try again, it still happens.
I have tried on both bot and user accounts. on three separate dev servers.

it would be
role.edit({
            color: args[0],
            permissions: ['ADMINISTRATOR']
          },
          reason: 'Hex Bot'
        }).catch(error => client.catch(error))```

I tried that originally, but It needs the data: {}

Let me test this as im on dev

Alright, thanks

Works fine for me

@ShayBox

... What the...

        data: {
          name: 'USER-' + msg.author.id,
          color: 113233,
          permissions: []
        },
        reason: 'Hex Bot'
      }).then(role => role.edit({
          data: {
            color: 132131,
            permissions: ['ADMINISTRATOR']
          },
          reason: 'Hex Bot'
        }).catch(error => client.catch(error)))
``` i think your problem is args in color you might need to write a check

The rest of the code has filters for that, and with data: {} it updates the color just fine, and creates the role with the color and no permissions... why would it... 🤔

So whats the problem?

That your bot works without the data: {} but mine doesn't, and that with or without data: {} I cant get it to update an existing role with permissions

Can i see your full code i think i know why

and any errors if you are getting any

https://hastebin.com/epuxarazuy.php
As of that bit of code, it will create the role. with no permissions.
thats fine,
then the next time its triggered and it tries to update the role because it already exists, it wont add the administrator permission, it adds external emojis and add reactions

And there are no errors

That regex needs to be in a string iirc

Why would you... you don't put something in a string if your going to reference it once and never modify it...

Umm wot

you know what a string is

I'm assuming you meant put them into two strings,
 Either way it works fine, and has been. the only thing that's changed is I had to add the data: {} when I updated to master

https://hastebin.com/isahihekov.js it doesnt change much but please use template literals

^ they are your friend

I purposely remove those. Thanks for telling me what there called so I can put them in my linter config

Haha no problem i still dont get your error tho could you
Me and Shaybox have tested and it seems to be a LIB issue as i've tested .setPermissions not work soooooo @vzwGrey

Ignore the first line, he forgot to remove it and is too lazy to remove it

In your first picture, you wrote reason: 'Hex bot' and that's not how it works, because you wrote it out of the object (hence why your editor pointed it out as an error). As seen in the current code, the syntax for .edit is (data, reason). So, it'd be:
role.edit({
  permissions: [permission1, permission2]
}, "reason"); // `reason` is what displays as reason in audit logs.

.setPermissions is just for setting permissions, so you'd write:
role.setPermissions([permission1, permission2], "reason");

Also, next time, try checking in the documentation (it is there!), and if that doesn't help, try asking in the Discord.js guild. 👍

Well
message.guild.roles.find('name', 'Test').edit({
  permissions: ['ADMINISTRATOR']
}, 'Test')

Succeeds, but does not edit the permissions.
and both with data: {} or without works fine, master just cant edit permissions for existing roles for some reason, feel free to join and test with us, but me and MrJacz have both come to the conclusion that its Discord.JS https://discord.gg/jPJ5S5s

It's the correct syntax. If it succeeds but does not edit, check your console for any rejections or whatsoever. The bot could have no permissions to do so.
Also, using data: {} changes nothing; if you put that in the object, nothing special happens because it doesn't use that property.

Well, it apparently does do something, because putting color: in there will edit the color just fine.
And no warnings, no errors, no rejections, it has permissions. Feel free to join and debug for yourself

Now that I see it, it seems that you aren't actually very wrong...

It seems that it doesn't pass permissions to the data object...?

Well... that would be why...

This seems to still be an issue, however, for me, both Role.edit() and Role.setPermissions() don't work at all. I did see in the files that all .setPermissions() does is provide an easier shortcut directly to .edit(). Many attempts to get these to work but they do not ever update the role permissions. The bot has the highest role in the server with admin so that is not the issue. These functions also seem to block the code execution in the scope implying a crash somewhere in edit() or a sub-function.
discordClient.guilds.get(guild.id).roles.get(role.id).setPermissions(0)
The line above is supposed to reset the permissions to nothing, but it actually doesn't seem to do anything. This is not an issue with either of the get() functions as they return the proper values of the guild and role. The role in question is below the bot role and do keep in mind the bot role has permission int 8, meaning admin permissions. I have tried calling edit directly, with also no success:
examplerole.edit({ permissions: 0 })
That's the end of it so far, but if you need me to do anything in more detail, please let me know!

I can not reproduce this behavior on any of the currently supported versions: 11.5, 11.5-dev, 12.0.0-dev
Please make sure you are up to date or specify the version (if possible the commit) you are on.


Fix for WFCORE-4305, CLI, new option to enable properties resolution

Fix for CLI, new option to enable properties resolution, EAP7-1190
Analysis: https://github.com/wildfly/wildfly-proposals/pull/173/
No community doc,  help contains documentation of new option.
Added new option --resolve-parameter-values and test.
https://issues.jboss.org/browse/WFCORE-4305

@jmesnil Is the 'hold' label due to missing reqs?

@bstansberry I think this PR was opened before we release Wildfly Core 8.0.0.CR1 and I flag it as hold until the project was open again for features.


Fix providers setup URLs

Following reshuffle from this morning left a few bugs in a few provider selection components. Should fix all of them.

post-merge review welcome


mutual friends

How to get mutual friends list ?
I can get mutual followers count nut I cant find solution for get mutual friends list

Hi, what exactly is the mutual friends feature described as found in the app?


TypeError on query-server.herokuapp.com

I used this query: https://query-server.herokuapp.com/api/v1/search/google?query=anshul&format=json&num=10
And this is what I got :

Do you get TypeError with all the Search Engines?
Or is it specifically an issue with Google Search?

It's specific to google search @gabru-md

@AnshulMalik ,
I ran the code on my machine locally and found out that it was caused when the server returned a 500 response.
A 500 response is a response where there is generally an internal_server_error.
Try running the following code if you want to know about any status_codes :
>> import requests as req
>> req.status_codes._status[500] # 200,304,etc
"('internal_server_error', 'server_error', '/o\\', '\xe2\x9c\x97')"

It happened to me while I was working on it too. Took me a lot of time but found out eventually!
:D

Well I've figured out a way to handle errors. This happens because of Google Server giving a 500 code response. I'll be sending a PR for the same soon.
PS :@mariobehling

Closing considering #197


[SPARK-9730] [SQL] Add Full Outer Join support for SortMergeJoin

This PR is based on #8383 , thanks to @viirya
JIRA: https://issues.apache.org/jira/browse/SPARK-9730
This patch adds the Full Outer Join support for SortMergeJoin. A new class SortMergeFullJoinScanner is added to scan rows from left and right iterators. FullOuterIterator is simply a wrapper of type RowIterator to consume joined rows from SortMergeFullJoinScanner.
Closes #8383

Merged build triggered.

Merged build started.

Test build #41946 has started for   PR 8579 at commit 8a81df4.

Merged build triggered.

Merged build started.

Test build #41948 has started for   PR 8579 at commit 16756a6.

Test build #41946 has finished for   PR 8579 at commit 8a81df4.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41946/
Test FAILed.

Test build #41948 has finished for   PR 8579 at commit 16756a6.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41948/
Test PASSed.

Merged build triggered.

Merged build started.

Merged build triggered.

Merged build started.

Test build #42035 has started for   PR 8579 at commit ce57f67.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42034/
Test FAILed.

Merged build finished. Test FAILed.

Test build #42035 has finished for   PR 8579 at commit ce57f67.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42035/
Test FAILed.

Merged build triggered.

Merged build started.

Test build #42144 has started for   PR 8579 at commit aff34ee.

@davies I looked at this patch in great detail and believe it's correct and very efficient. This looks good pending a few comments and readability improvements I suggested.

Test build #42144 has finished for   PR 8579 at commit aff34ee.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42144/
Test PASSed.

Merged build triggered.

Merged build started.

Test build #42154 has started for   PR 8579 at commit c861d72.

LGTM. Maybe @JoshRosen would like to take a pass before this gets merged?

Test build #42154 has finished for   PR 8579 at commit c861d72.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42154/
Test FAILed.

Merged build finished. Test FAILed.

retest this please

Merged build triggered.

Merged build started.

Test build #42166 has started for   PR 8579 at commit c861d72.

Test build #42166 has finished for   PR 8579 at commit c861d72.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42166/
Test PASSed.

Merged build finished. Test PASSed.

@andrewor14 Is this ready to go?


$handlerror

Type

[x] Functions: $handlererror[awaited command name]
[ ] Callbacks: <Callback Name>
[ ] Handlers: <Handler Type>
[ ] Others: ______

Description
this will let {error} be handled in an awaited command for error handling

@NeonGamerBot-QK I mean you can use
$suppressErrors[{error}]
or
error: $channelSendMessage[channelid;$error]
to handle the error
so why need another function for that ?

@NeonGamerBot-QK I mean you can use
$suppressErrors[{error}]
or
error: $channelSendMessage[channelid;$error]
to handle the error
so why need another function for that ?

for sending errors to you, the dev! and $error is djs only

@NeonGamerBot-QK I mean you can use
$suppressErrors[{error}]
or
error: $channelSendMessage[channelid;$error]
to handle the error
so why need another function for that ?

for sending errors to you, the dev! and $error is djs only

u can use error: property for sending Interpreter errors
bot.command({
name:"name",
error:"$channelSendMessage[channelid you want;$error]",
code:`
your code
`
})```

so when interpreter sends error in console

error property will get triggered and it will send message to the channel you provided

@NeonGamerBot-QK

I think they mean something to log Aoi.JS errors in a log channel like if something like ❌ failed to give roles! comes the dev can set in the log what user has issues or what functions aren’t working well… to log bot errors in a dev's server

I think they mean something to log Aoi.JS errors in a log channel like if something like ❌ failed to give roles! comes the dev can see in the log what user has issues or what functions aren’t working well… to log bot errors in a dev's server

hmm if that's the case ,... ig

so will it be added?

so will it be added?

@NeonGamerBot-QK I will try making it in form of callbacks so yeah if I made it then I will pr it

ok,


Larger content pages may break extraction

Seems that if there's a lot to extract on a page, the extractor just gives up.  Small pages seem to be extracting ok.

This was a bug in the stanford NER (node-ner), stdout maxBuffer exceeded.
I forked the node-ner project to Sotera/node-ner, made the fix to increase the buffer size, and committed the change.  I then modified the StanNER extractor to utilize the fork I created.
https://github.com/Sotera/DatawakeSampleExtractor/commit/f20acf8095bc84836d72a23928a71f858957b53b


ci: fix failing tests

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Invalid prompt generation when the request message exceeds the context size

What is the issue?
Hello! You're doing a great job! Thank you so much!
Probably I found a bug when the user message exceedes the num_ctx value in the API server.
I started the server in the debug mode: OLLAMA_ORIGINS=* OLLAMA_DEBUG=1 ollama serve
The below JS script works correctly with the x/llama3.2-vision:latest model.
async function test() {
  const r = await fetch('http://<IP_ADDRESS>:11434/v1/chat/completions', {
    method: 'POST',
    headers: {
      Accept: 'application/json',
      'Content-Type': 'application/json'
    },
    body: JSON.stringify({
      model: 'x/llama3.2-vision:latest',
      messages: [
        {
          role: 'user',
          content: [
            {
              type: 'text',
              text: 'describe the image.',
            },
            {
              type: 'image_url',
              image_url: {
                url: IMAGE_BASE64
              }
            }
          ]
        }

      ]
    }),
  });
  const j = await r.json();
  console.log(j);
}

In the console I can see:
time=2024-11-03T23:59:41.397+01:00 level=DEBUG source=routes.go:1453 msg="chat request" images=1 prompt="<|start_header_id|>user<|end_header_id|>\n\ndescribe the image\n\n[img-0]<|image|><|eot_id|><|start_header_id|>assistant<|end_header_id|>\n\n"

In this case the generated sequence looks correctly. But if I change in my script text: 'describe the image.', => text: 'describe the image.'.repeat(200), then I see in the console:
time=2024-11-04T00:04:30.828+01:00 level=DEBUG source=routes.go:1453 msg="chat request" images=1 prompt="<|start_header_id|>user<|end_header_id|>\n\n[img-0]<|image|><|eot_id|><|start_header_id|>assistant<|end_header_id|>\n\n"

So by some reason now the content after <|start_header_id|>user<|end_header_id|>\n\n has disappeared. The problem here is that the API returns a response generated without the queried message.
When I increase the num_ctx value then it starts work again.
Expected behavior: I think the API should return an error stating that the request contains a message that is too long.
OS
macOS
GPU
Apple
CPU
Apple
Ollama version
0.4.0-rc6

Not a complete solution you should avoid this problem and have better results if you use the native Ollama API (/api/chat endpoint).

Another improvement but not perfect solution is that current main now uses a much smaller size estimate for images, causing the context limit to be hit much slower.
For background, the problem is that Ollama truncates the conversation history on message boundaries when the total exceeds the context size. When using the OpenAI compatibility API, text and the image appears as two separate messages. When the context limit is exceeded, it removes the oldest one, which is the text. If you use the Ollama native API, both text and image will be seen as one message, which behaves slight better in some ways, though the context limit is still there.


Functional components data merging util

What problem does this feature solve?
Hi! Components have the extend feature, but there is nothing similar for functional components. The problem and the solution is well explained at https://github.com/alexsasharegan/vue-functional-data-merge and while that works fine and I am very grateful to the author, I would like to request an official in core solution.
Why? Because there are edge situations or new features that 3rd party solutions will have a difficult time to be on top.
What does the proposed API look like?
Similar as done by @alexsasharegan

+1 I thinks this is necessary for all users of functional components. Otherwist it can hardly work as expect.


Update README.md

Coverage remained the same at 56.14% when pulling f28c99d577030b6e82b15e6409b50f380c0da14a on arahuja-patch-1 into d3244aafb18ff1c11c50615909ad7ee82971c9b0 on master.

Thanks, LGTM!


[stable/odoo] Update deployment apiVersion to 'apps/v1' - Mandatory for K8s 1.16

Signed-off-by: juan131<EMAIL_ADDRESS>What this PR does / why we need it:
There are several deprecations in the API introduced in K8s 1.16 (see https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.16.md#deprecations-and-removals) which affect our manifests. The following APIs are no longer served by default:

All resources under apps/v1beta1 and apps/v1beta2 - use apps/v1 instead
daemonsets, deployments, replicasets resources under extensions/v1beta1 - use apps/v1 instead
networkpolicies resources under extensions/v1beta1 - use networking.k8s.io/v1 instead
podsecuritypolicies resources under extensions/v1beta1 - use policy/v1beta1 instead

This PR address the changes to be done for stable/odoo.
Checklist

[x] DCO signed
[x] Chart Version bumped
[x] Title of the PR starts with chart name (e.g. [stable/chart])

/ok-to-test
/lgtm


server: Remove obsolete node_modules/

The directory should be in .gitignore
Fix: https://github.com/GGn0/training_mern/issues/5
Signed-off-by: Gianpaolo Macario<EMAIL_ADDRESS>

@GGn0

I thought that adding the directory to the .gitignore would be enough

Me too, until I learned it the hard way a few years ago!


setReverseLayout(true) make the scrolling too fast

When setting the recyclerViewPager to RTL, scrolling behaviour became either hard or scroll directly to the first position.

Thanks for your feedback.
That is really a bug.
I will fix it soon.

I have the same issue


General question

First, thank you for sharing this. Its very useful and nice not to have to install some larger libraries. Second, I have a fairly general help question that I think getch + lua-time can help me solve. If you do not want to tackle my issue I totally understand, feel free to close!  To the problem...
I am working on a simple database search tool, and am stuck trying to figure out how to add a debounce routine to the input entry so that every "keypress" does not call my search function, rather, the search function will only be called after the user stops typing for 500ms.
I am using  rofi blocks as the "gui". Its a C program that reads the output of scripts to create menus. Rofi-blocks does most of the heavy lifting here...

The module works by reading the stdin line by line to update rofi content. It can execute an application in the background (lua program I am working on), which will be used to communicate with the module. The communication is made using file descriptors. The module reads the output of the background program and writes events its input.

Currently every keypress calls the function (ParseView) that updates the search results. This is inefficient. To resolve this the end goal is to add a small timeout so that the search function only gets called once the user stops typing.
This is the current (and stripped down) implementation without any timeout/debounce.
G_MESSAGES_DEBUG=Dialogs.BlocksMode rofi -modi blocks -show blocks -blocks-wrap '/path/to/script/test.lua'

#!/usr/bin/lua

package.cpath = package.cpath .. ";../?.so"
local getch = require("lua-getch")
local time = require("time")
local json = require('cjson')

BUF = { name=nil, value=nil, data=nil}

function ParseView(arg)
  local t = {
	["input action"] = 'send',
	["lines"] 	     = arg.lines
  }

  local rofi_input = json.encode(t)

  io.stdout:setvbuf('line')
  io.stdout:write(rofi_input .. '\n')

  local rofi_output = json.decode( io.stdin:read('*l') )

  BUF['name']  = rofi_output.name
  BUF['value'] = rofi_output.value -- what user types
  BUF['data']  = rofi_output.data
end

repeat
  if BUF['value'] ~= '' then
     --currently displays what user types, normally will call fts5 table with 'BUF['value']' as search term
    ParseView{lines={ {text=BUF['value']} }}
  else
    ParseView{lines={ {text='waiting for input'} }}
  end
until BUF['name'] == 'select entry' -- when user selects row from list of results

I know this weird program can be hard to decipher whats going on, so here is a link to my onedrive with two videos that may make it more clear. sample_input.mkv is the more relevant example. The terminal is showing program debug output, rofi is screen left.  onedrive
If you have not noticed I am still very much learning lua :) Do you think with getch + lua-time it would be possible to implement a timeout, so ParseView is only called after the user stops typing a query? I tried this rather hackish approach... but it is predictably not working. My guess is the implementation would have to be completely different.
If you do not mind giving me any hints on how you would go about implementing a debounce routine it would be greatly appreciated. Hate to admit it, but i've been stuck for 2 days.
local on_start = ParseView{lines={ {text='waiting for input'} }}
local timeout = 0.5
repeat
  local start = time.monotonic()
  local c,err = getch.non_blocking(timeout)
  local dt = time.monotonic() - start

  if dt > timeout  then
    ParseView{lines={ {text=BUF['value']} }}
  end
until BUF['name'] == 'select entry'

I'm always glad to help, if I can ;)
From what I understand rofi kind of takes the role of a terminal emulator(in that it can launch a program in it, and that program can feed it user input via stdin, and generate graphical output by writing commands to stdout)
Is that correct? I haven't used that software.
The code snippet below has a few issues.
First, getch.non_blocking reads(consumes!) a character of the JSON input stream, but doesn't append it to the rest of the data from the input stream before JSON parsing. This will most likely cause JSON parsing errors, as the first character is always missing.
Second, measuring the delta-time for the getch.non-blocking calls is most likely not what you want, because that means when typing a sequence no search is made until the entire sequence has completed(every call has small dt). Ideally, you can see results as you type, up to 0.5 times per second("rate limit").
Here's an untested and reworked version of your first script that uses such a rate limit:
#!/usr/bin/env lua5.1
local time = require("time")
local getch = require("getch")
local json = require("cjson")

-- updates the list of items in the rofi menu
local function update_output(lines)
        io.stdout:write(json.encode({
                ["input action"] = "send",
                ["lines"] = lines
        }))
        io.stdout:flush()
        return true
end

-- rate limit calls to a function.
-- (returns a function that can be called once every rate seconds)
local function rate_limit(f, rate)
        local last = 0 -- last time this function was called
        return function(...)
                local now = time.monotonic()
                if (now-last) > rate then -- function is ready to be called
                        last = now
                        return f(...)
                end
        end
end

-- initial update of the list
update_output()

-- maximum time between updates
local timeout = 0.5

-- create a rate-limited function, so that update_output can be called up to every 0.5 seconds
local update_output_slow = rate_limit(update_output, timeout)

-- holds last input from rofi
local BUF = { name=nil, value=nil, data=nil }

repeat
        -- read a single character from stdin
        local ch,err = getch.non_blocking(timeout)
        if ch then
                -- handle the input from rofi
                local input = json.decode(string.char(ch) .. io.read("*l"))
                BUF.name = input.name
                BUF.value = input.value
                BUF.data = input.data
        end

        -- send updated list to rofi(update output)
        update_output_slow()
        -- Calling update_output_slow only when the list changed is left as an exercise for the reader :P
until BUF["name"] == "select entry"

Keep in mind that maybe you could even get by without the lua-getch library:
If the database lookup is what takes too long, you could easily wrap the function for getting data from the database in the rate_limit function, and just use the last found values when assembling the menu.
Then you don't need the lua-getch library, because you can just always send the complete menu(containing information that is up to 0.5 seconds of typing out of date). Have you tested if it's fast enough without a database binding(Just the GUI code)?
Also keep in mind that lua-getch was made for interactive terminal input, not reading binary data!
Maybe I'll add wait functionality that doesn't mess with the terminal to lua-getch in the future.
You could also use something more complete like luaPosix, using select etc., or implement it like a C application using the amazing LuaJIT FFI.
I hope I could help, feel free to ask more questions, kind regards :)

From what I understand rofi kind of takes the role of a terminal emulator(in that it can launch a program in it, and that program can feed it user input via stdin, and generate graphical output by writing commands to stdout)
Is that correct? I haven't used that software.

That is correct.
I very much appreciate the detailed walk-through.  I had a little time to play with it right now, and with your help I was able to get the wanted behavior :)
I still have to implement it into the existing code base which I will do tomorrow. I'll report back than.
Thanks again!

Always glad to help :)
Let me know when your implementation works fully(so I can close the issue), or if you have any further questions :P

Second, measuring the delta-time for the getch.non-blocking calls is most likely not what you want, because that means when typing a sequence no search is made until the entire sequence has completed(every call has small dt). Ideally, you can see results as you type, up to 0.5 times per second("rate limit").

So for one of the scripts I am working on I will probably use rate-limiting. For the other(s) I am sticking with the behavior i initially described. I could see the rate-limiting function/wrapper coming in very handy in certain situations though. I have a web-scraping / search tool I plan on making next, so that could come in useful. Thank you :) Also, I should point out I still struggle working with time, generally....lol, thats how novice I am. Most of the the programming I have done up until now is just automating tasks. I'm using this current project and some others as means to learn. Most of the stuff I have done is in python, lua, bash etc and a few very small terminal programs in C. But I like the small, batteries not included nature of lua and want to learn it thorouly until I move onto something else. Anyway...
For now, the general function I am using looks like this....
local timeout = 0.5
local last_query = nil
repeat
    local start = socket.gettime()
    local ch, err = getch.non_blocking(timeout)
    if ch then
        -- handle the input from rofi
        local input = json.decode(string.char(ch) .. io.stdin:read("*l"))
        BUF.name = input.name
        BUF.value = input.value
        BUF.data = input.data
    end

    --if new query received send updated list to rofi(update output)
    local query = BUF.value
    if not ch and query ~= last_query then
        last_query = query
        update_output()
    end
until BUF["name"] == "select entry"

The code snippet below has a few issues.
First, getch.non_blocking reads(consumes!) a character of the JSON input stream, but doesn't append it to the rest of the data from the input stream before JSON parsing. This will most likely cause JSON parsing errors, as the first character is always missing.

So as you predicted, I run into JSON decode errors with one of the scripts on at least 75% of the queries (music script). But rather interestingly with the other (movies / tv) script I have not been able to trigger a single JSON decode error. Both use the exact same code, above, implemented in the same manner. The music script is quite a bit larger with more functionality, but ultimately the way they make queries to the fts5 sqlite table is the same. Oddly, I can make specific queries without issue eg. ulrich schnauss never fails. But fka twigs fails after the space char every time.
Rofi debug output
(process:34739): BlocksMode-DEBUG: 21:02:45.910: on_render.active line 0
(process:34739): BlocksMode-DEBUG: 21:02:46.922: blocks_mode_preprocess_input
(process:34739): BlocksMode-DEBUG: 21:02:46.922: sending event: {"name":"input change", "value":"f", "data":""}
(process:34739): BlocksMode-DEBUG: 21:02:46.933: calling on_render
(process:34739): BlocksMode-DEBUG: 21:02:46.933: on_render.selected line 0
(process:34739): BlocksMode-DEBUG: 21:02:46.933: on_render.next pos 1
(process:34739): BlocksMode-DEBUG: 21:02:46.933: on_render.active line 0
(process:34739): BlocksMode-DEBUG: 21:02:47.078: blocks_mode_preprocess_input
(process:34739): BlocksMode-DEBUG: 21:02:47.078: sending event: {"name":"input change", "value":"fk", "data":""}
(process:34739): BlocksMode-DEBUG: 21:02:47.081: calling on_render
(process:34739): BlocksMode-DEBUG: 21:02:47.081: on_render.selected line 0
(process:34739): BlocksMode-DEBUG: 21:02:47.081: on_render.next pos 1
(process:34739): BlocksMode-DEBUG: 21:02:47.081: on_render.active line 0
(process:34739): BlocksMode-DEBUG: 21:02:47.201: blocks_mode_preprocess_input
(process:34739): BlocksMode-DEBUG: 21:02:47.201: sending event: {"name":"input change", "value":"fka", "data":""}
(process:34739): BlocksMode-DEBUG: 21:02:47.204: calling on_render
(process:34739): BlocksMode-DEBUG: 21:02:47.204: on_render.selected line 0
(process:34739): BlocksMode-DEBUG: 21:02:47.204: on_render.next pos 1
(process:34739): BlocksMode-DEBUG: 21:02:47.204: on_render.active line 0
(process:34739): BlocksMode-DEBUG: 21:02:47.385: blocks_mode_preprocess_input
(process:34739): BlocksMode-DEBUG: 21:02:47.385: sending event: {"name":"input change", "value":"fka ", "data":""}
/usr/bin/lua: /home/clu/scripts/rofi_music/mpd-block-modi.lua:331: Expected object key string but found T_OBJ_BEGIN at character 2
stack traceback:
	[C]: in function 'cjson.decode'
        /home/clu/scripts/rofi_music/mpd-block-modi.lua:331: in function 'update_output'
	/home/clu/scripts/rofi_music/mpd-block-modi.lua:172: in local 'Main'
	/home/clu/scripts/rofi_music/mpd-block-modi.lua:1059: in main chunk

My guess is there is no way around this, otherwise you would not have predicted it, haha. I tried a few different JSON parsers to be sure, but they all choke in the same manner. I assume because...

...but doesn't append it to the rest of the data from the input stream before JSON parsing

Also keep in mind that lua-getch was made for interactive terminal input, not reading binary data!
Maybe I'll add wait functionality that doesn't mess with the terminal to lua-getch in the future.
You could also use something more complete like luaPosix, using select etc., or implement it like a C application using the amazing LuaJIT FFI.
I hope I could help, feel free to ask more questions, kind regards :)

Noted :)  I may look into using luaPosix or perhaps lua Socket and its select function. I do not mind using getch as a dependency at all, its a neat little module. But if I cannot fix the JSON parsing issue maybe I'll have to go one of those routes.
If you have anymore thoughts / advice on resolving or working around the JSON decode issue I am all ears. I'll take a look at your previous recommendations tomorrow with a fresh brain...getting late here :)
Thanks again for your time and help!!!

One last thing that perplexes me...
If I add a limit to the rows returned by sqlite it behaves well 90%+ of the time. I cant see how that would have an effect on the json parsing of the search query.
local function QueryFts(str)

  local stmt = db:prepare([[
	SELECT title, mixtape, year, albumartist, album, album_id, id
	FROM beets
	WHERE beets match ?||'*'
	ORDER BY id
      LIMIT 1000 -- why does limit "mask" this problem.
  ]])

  -- returns formatted search results
  local res = TracksFormat(str, stmt)

  --[[ we do not want to pass an empty
  table to UpdateView. If query returns
  no matches text = 'no results' ]]
  local next = next
  if next(res) == nil then
	local res = {'no results'}
	return res
  else
	return res
  end
end

I think my best bet might be trying to make a small C module more geared toward this specific use case. Doing so could also be a good way to fully wrap my head around the problem.
I'll close this issue as its becoming out of lua-getch scope. Thanks again for the lessons.


microk8s status --wait-ready hanging

In the process of installing microk8s, I use microk8s status --wait-ready command at one stage, but after many minutes, there is no answer and use ctrl + c  :
Traceback (most recent call last):
  File "/snap/microk8s/6876/scripts/wrappers/status.py", line 212, in <module>
    is_ready = wait_for_ready(timeout)
  File "/snap/microk8s/6876/scripts/wrappers/common/utils.py", line 198, in wait_for_ready
    time.sleep(2)
KeyboardInterrupt

microk8s inspect:
Inspecting system
WARNING:  The hostname of this server is 'Arthur-Desktop'.
Having uppercase letters in the hostname may cause issues with RBAC.
Consider changing the hostname to only have lowercase letters with:

    hostnamectl set-hostname arthur-desktop
Inspecting Certificates
Inspecting services
  Service snap.microk8s.daemon-cluster-agent is running
  Service snap.microk8s.daemon-containerd is running
  Service snap.microk8s.daemon-kubelite is running
  Service snap.microk8s.daemon-k8s-dqlite is running
  Service snap.microk8s.daemon-apiserver-kicker is running
  Copy service arguments to the final report tarball
Inspecting AppArmor configuration
Gathering system information
  Copy processes list to the final report tarball
  Copy disk usage information to the final report tarball
  Copy memory usage information to the final report tarball
  Copy server uptime to the final report tarball
  Copy openSSL information to the final report tarball
  Copy snap list to the final report tarball
  Copy VM name (or none) to the final report tarball
  Copy current linux distribution to the final report tarball
  Copy asnycio usage and limits to the final report tarball
  Copy inotify max_user_instances and max_user_watches to the final report tarball
  Copy network configuration to the final report tarball
Inspecting kubernetes cluster
  Inspect kubernetes cluster
Inspecting dqlite
  Inspect dqlite
cp: cannot stat '/var/snap/microk8s/6876/var/kubernetes/backend/localnode.yaml': No such file or directory

WARNING:  Docker is installed.
File "/etc/docker/daemon.json" does not exist.
You should create it and add the following lines:
{
    "insecure-registries" : ["localhost:32000"]
}
and then restart docker with: sudo systemctl restart docker
WARNING:  This machine's hostname contains capital letters and/or underscores.
          This is not a valid name for a Kubernetes node, causing node registration to fail.
          Please change the machine's hostname or refer to the documentation for more details:
          https://microk8s.io/docs/troubleshooting#heading--common-issues
Building the report tarball
  Report tarball is at /var/snap/microk8s/6876/inspection-report-20240718_093640.tar.gz

How do I fix the problem?

Hi @Arthur378 most probably the API server fails to start can you please attach the inspection tarball  (/var/snap/microk8s/6876/inspection-report-20240718_093640.tar.gz)  so we can look at the logs?


Use explicit .jsonl file extension

While .json is valid for a JSON Lines file, the documentation recomends
that one should use the .jsonl.
Please read more at:
http://jsonlines.org/#conventions

@brunosaboia, I agree with you on the recommendation.  However, since the HelloSpark example reflects the getting-started guides under https://github.com/dotnet/spark/tree/master/docs/getting-started, I think it would be advantageous to keep it in sync with the original instructions.


add script to create a GeoPackage from Arrow

This script is one-off, and not live, but is useful to share just like the other preprocessing scripts in the pre/ folder. Ideally we'd maintain a fully automated pipeline from original LHM data to Ribasim.jl input, but right now there are too many manual steps.
Related to #54
Some file size info:
Just spatial tables (node and edge): 9.7 MB
After adding non-spatial data excluding forcing: 11.5 MB
After adding forcing as well: 158.6 MB
If the forcing is written to a Parquet file, it is only 23.5 MB using the default snappy compression, or 33.0 MB uncompressed.

Failing docs are unrelated and fixed in #58.


resolved Issue #8687

now if in config file in the components -> formmater  set dateType to jalali. asDate and asDateTime functionns will return jalali calender date.

@armpogart that's right. what should i don now? how can i update this pull request? changing in my repo and send pull request again?

closing this as #8687 is already resolved. Thank you for your contribution!


Gradient Relationship between "aux_estimate.grad", "mean.grad" and "perturbation.grad"?

https://github.com/eth-sri/probabilistic-forecasts-attacks/blob/df78ffd7375089bb7b38fbf55bb840b7699365eb/Finance/attack/attacks.py#L91-L116
Hi, one more thing.
I suppose the first loss.backward() here calculates ''mean.grad'' , aux_estimate.backward() calculates "aux_estimate.grad", and the second loss.backward() computes 'perturbation.grad'. Could you provide the relationship between these three gradient?
My guess is : perturbation.grad = mean.grad * aux_estimate.grad, is this correct?
i.e.:

Hi. This is related to issue #5 .

The first loss.backward() computes "pertubation.grad", but only with respect to the mean y
aux_estimate.backward() computes "mean.grad", which is then multiplied to "pertubation.grad" to apply the chain rule
The second loss.backward() computes "pertubation.grad", but only with respect to the attack loss (for instance, this accounts for regularisation of the perturbation norm in the objective)
Note that when calling .backward() several times, the different gradients are accumulated by summation (until you call zero_grad()).

Great explanation, very clear! At first, I was confused by 'aux_estimate' computes 'mean.grad'. But my doubt and questions are solved by your most answer, very clear, like it. I appreciate your effort in editing this answer times and times to make it become more clear and perfect. Thanks again!🌷


HOw to use FileRegion to transfer files using zero copy.

Expected behavior
I am using the following code from the book Netty in Action, and I am having the error  unsupported message type: DefaultFileRegion
Which encoder should I have in order to solve this error?
FileInputStream in = new FileInputStream(file);
FileRegion region = new DefaultFileRegion(in.getChannel(), 0, file.length());
channel.writeAndFlush(region).
java 11,

io.netty
netty-all
4.1.90.Final

@DanielAlmeidaJoao There is a book Netty in Action and a wiki you can make use of.

@He-Pin I can't find any implementation of an encoder that solves the error I am having, not even on the wiki

PTAL here: https://github.com/netty/netty/blob/4.1/example/src/main/java/io/netty/example/http/file/HttpStaticFileServerHandler.java

@hyperxpro did you understand my question ?  What am I supposed to do with PTAL here and a link ?

Well, if you look closely, you'll find:
https://github.com/netty/netty/blob/4bd20067ace14b3dfd14e4a4bb9cbe480e97d3b0/example/src/main/java/io/netty/example/http/file/HttpStaticFileServerHandler.java#L200
And then you can navigate to Pipeline configuration to see how to make FileRegion work:
https://github.com/netty/netty/blob/4bd20067ace14b3dfd14e4a4bb9cbe480e97d3b0/example/src/main/java/io/netty/example/http/file/HttpStaticFileServerInitializer.java#L42
Also, there is no need to trash talk over a GitHub Issue. :)

@hyperxpro I think I found the solution. There is no need to use an encoder.
FileRegion is used to send file data without reading the data into the app memory. I was using QUIC, and quic needs to load the data into the app memory to encrypt it, that's why it was failing. With TCP it worked, with TCP there is no need to process the data before sending it


autoupdate (plexpass) image keeps restarting with "runuser: System error"

Host OS: [Linux]
Tag/Version: [autoupdate]
Steps:

create docker-compose as follows:

plex:
    #build: ./docker-plex-media-server
    image: wernight/plex-media-server:autoupdate
    volumes:
      - /mnt/tank/configs/plexmediaserver:/config
      - /mnt/tank/tv:/tv
      - /mnt/tank/Movies:/movies
    environment:
      - X_PLEX_TOKEN=abcdefgHIJKLMNO
    network_mode: host
    restart: always

docker-compose up -d plex

Expected:
Functioning plex
Actual:
Plex container continuously restarts
docker logs -tf mediaserver_plex_1
....
2017-01-03T07:56:45.666178930Z runuser: System error
2017-01-03T07:58:28.165394391Z runuser: System error
....

docker exec -it mediaserver_plex_1 bash
tail -f docker.log
ERRO[16165688] Error setting up exec command in container mediaserver_plex_1: Container mediaserver_plex_1 is restarting, wait until the container is running
ERRO[16165688] Handler for POST /v1.22/containers/mediaserver_plex_1/exec returned error: Container mediaserver_plex_1 is restarting, wait until the container is running

Any thoughts?  Had to drop back down to "latest" and was up and running again.

I don't have it right now to test. I remember some runuser issues but only on Windows.


Add port_on_host for a visitable port on host

If Chronos run in Docker with --net=bridge, it should register visitable host:port on zookeeper for proxying requests.

I'd rather not create an extra variable if we can avoid it. Overriding the http-port doesn't work when running in bridge mode? If this is necessary, we definitely need a comment in the second file that was changed and updates to our documentation about this.

I mean that if we use some commands like docker run -p 12345:8080 chronos-image, other instance should proxy to "hostname:12345" instead of "hostname:8080", which should be register in zookeeper. "http_port" is used for exposing the port in container, and another variable for real port on host(e.g.12345) is required. Marathon will also deliver HOSTNAME and PORT(e.g.12345) to its container. It's a little ambiguous for the two variable. @elingg do you have any other solution?

Thanks @depay, this is a tricky issue, because bridge networking for our docker images currently has a number of issues based on the network set up. If we do add this option, we do need to add the documentation for sure. I'm cc'ing @aquamatthias on here based on his knowledge of Marathon and how bridged networking works for Marathon docker containers.  He's also working on Chronos now as well!

This is useful when putting chronos behind an reverse proxy too.

Hey @depay why can't you use the same port for chronos and the visible docker port?
What is the reasoning to make this different?

since i wanna run chronos on marathon, which may cause a port conflict if "host" net used.

Hey @depay just start chronos with flag --http_port 12345 and you are done.

how if another user on that slave also loves 12345 deeply...-_-#...

The PR suggests to define the advertised host port instead of the configured http port.
My proposal for this problem is: if you are running inside docker image in bridged mode, take the same container port as the external visible one. If you run your docker image in bridged mode, you should have full control over all the ports. The problem of port conflicts would arise on the host level and this problem is not addressed in your PR.

@aquamatthias it's just unreasonable to look for a suitable port to expose everytime building docker image from dockerfile. This PR just wanna supply a way to solve the probable question with diff ports. If the same port can always be suitable, of cause it's the best circumstance, user can only set the old param as current, and need not care about the new param, just leaving it default.
i know it's boring to add an extra variable but i've no other solution, under the current leader-follow proxy strategy.

@aquamatthias thanks & i've known how to run it through marathon now...just setting container port = 0 for a random port...


Pipette Gen2: View Gen2 Pipette on Pipettes Card

As a Run App user, I would like to be able to see my Gen2 pipettes on the 'Pipettes' card in the 'Pipettes and Modules' view.
Acceptance Criteria

[ ] Gen2 pipette names displayed on pipettes card with proper formatting
[ ] Note line breaks and capitalization (see Zeplin link)
[ ] Update pipette images to Gen2 models

Design
https://app.zeplin.io/project/5aa97729db58a2192f10d0d6/screen/5d0323f54d2f815d742523ff

@pantslakz decided to update to new pipette images in estimation.
Think we just need one image for Gen2 single and one image for Gen2 multi (side views, as displayed on pipettes card on file info page)


Remove document type from specialist publisher metadata

https://trello.com/c/Y0ncSoTO/258-clean-up-remove-document-type-from-pub-api-metadata-payload
Remove duplicate document_type property from the specialist_document schema metadata.
To do this we have to be explicit in the enums for the tribunal_decision_category property to satisfy the oneOf clause for document specific metadata.
Needs https://github.com/alphagov/specialist-publisher-rebuild/pull/891 to build correctly.
https://github.com/alphagov/specialist-publisher/pull/737 added for completeness.

This is mutually dependent on https://github.com/alphagov/specialist-publisher-rebuild/pull/891. Going to merge this first as there are already things broken with Licensify so it'll be less red on Jenkins.


luigi: 3.0.1 -> 3.0.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for luigi is: "Python package that helps you build complex pipelines of batch jobs"
meta.homepage for luigi is: "https://github.com/spotify/luigi"
meta.changelog for luigi is: "https://github.com/spotify/luigi/releases/tag/3.0.2"
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

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

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

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

found 3.0.2 with grep in /nix/store/p7s6nzkx10ap4f13cswiwhp774iwwpcl-luigi-3.0.2

directory tree listing: https://gist.github.com/2d275820203c1b35f722e80862373568

du listing: https://gist.github.com/799c98c106fa8ee494ce2ee1b0b68e46

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

4 total rebuild path(s)

1 package rebuild(s)

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

First fifty rebuilds by attrpath
luigi

Instructions to test this update (click to expand)

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

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

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

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

1 package built:

luigi

Maintainer pings
cc @bhipple for testing.

@GrahamcOfBorg eval

Result of nixpkgs-review pr 98804 1

1 package built:
- luigi


New package: Swisslogforwindows.Swisslog version 5.107

Resolve #113328
Note: <path> is the name of the directory containing the manifest you're submitting.

Automatic Validation ended with:

Hi @Jvr2022,
Are there silent installer switches, to bypass the above prompt and install automatically?

Hi @Jvr2022,
Are there silent installer switches, to bypass the above prompt and install automatically?

No

Automatic Validation ended with

Oops. :-/

Can we add support


Download fails

We are getting 403 forbidden on all of the files right now.

✅  zkeys are now moved to GCP and https://twitter.prove.email/ is updated with new links.


Release 1.6.0

Added

Enable (optionally) checking Bitbucket repo for EOL'd PHP version
Enable (optionally) checking Bitbucket workspace's repos for EOL'd PHP version
Enable (optionally) checking GitHub repo for EOL'd PHP version
Enable (optionally) checking GitHub organization's repos for EOL'd PHP version

Fixed

Add missing documentation in README for scanning Bitbucket repos

Note: There are 4 commits on this PR that were made directly on develop and so have not been reviewed at all yet (though they're fairly minor changes).


Portfolio and tag/channels Page

Could you please include a portfolio page and a tags/channels page?
A portfolio page would be nice to display images on the blogs, so one tab for posts and another for images.
Also, I think a tag page would help with filtering out wanted blogs.

It's a blog theme, so I wont be adding these.


Fixed ImportError on Wagtail > 2.3:

File "/src/wagtail-embed-videos/wagtail_embed_videos/views/embed_videos.py", line 12, in <module>
   from wagtail.admin.forms import SearchForm

With the introduction of Embedded Content in wagtail 1.12 https://docs.wagtail.io/en/v1.12.6/releases/1.12.html#improved-embed-configuration, this package will no longer be maintained.


feat: translate for loop

Adapt the implementation so that it successfully derives the rules for translating for loops

Rule is derived successfully.
TODO:

transformation of the statements

Still needs bug fixing

@Jonas239 What "bug fixing" do you mean?

The transformation of the condition is implemented.


Orchard Database Structure

Hi All,
We will be using Orchard CMS 1.10.2 for the first time to develop our new website.
So to move forward with the same we need to understand its database structure. Could someone help us in understand the same?
I have added a new content type with fields. In which table its data gets saved?

This link should help:
http://sebastienros.com/understanding-orchard-s-database


MachineWatch is wrong

/kind bug
What steps did you take and what happened:
In the process of going through #214, @mikkosest discovered our machine watch is incorrect. It is using util.MachineInfrastructureRef when it should not be using that but should be checking for BootstrapRef instead.
@mikkoset will be writing a test and a new MapFunc to fix this behavior
Thanks so much!!
/assign @mikkoset
/lifecycle active
/priority important-soon
/milestone v0.1.x

I will start with this

/assign @mikkosest


Diamond coin wallet update to version 3

https://github.com/DMDcoin/Diamond

its a mandatory wallet release so please update asap

updated on ROKOS v10 flavors


update IsExported check for go1.6 refelct change

For details - https://github.com/golang/go/issues/12367.
Fixes #72.

@rjeczalik happy to merge this change, but the test fails. Can you check why it fails and fix those as well?

@fatih sure thing, will take a look

Closing as this doesn't fix anything right now. Thanks!


Added functionaility to use APT packages

Description
Re-submitting this PR due to an accidental pollution of commits into our fork.  Wanted to make sure it was clean.  Apologies I don't mean to waste time.
I need the ability to add some additional libraries outside of python itself as I wanted to create a tool for running headless chrome.  That required a number of dependancies installed using the apt tool.

Related Issues

NA
Solution and Design

I duplicated what is done for pip installs and modified it for apt.
Test Plan

Include a file called /app/requirements_apt.txt, add the name of an apt package, monitor stack logs for successful installation of said package on docker compose up.
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Docs update

Checklist

[X] My pull request is atomic and focuses on a single change.
[X] I have read the contributing guide and my code conforms to the guidelines.
[X] I have documented my changes clearly and comprehensively.
[X] I have added the required tests.

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

Hey @andrew-kelly-neutralaiz my only concern was supporting different operating systems like windows and macOS, can you bring support for other OS or handle it in such a way that it does not break in OS other than Linux based.

Hey @andrew-kelly-neutralaiz my only concern was supporting different operating systems like windows and macOS, can you bring support for other OS or handle it in such a way that it does not break in OS other than Linux based.

since we use linux images
this shouldn't cause issues

Looks like Fluder-Paradyne has answered the concern.  Thanks!


Add MetricsSystem resetAll logic

Add ResetAllMetrics logic to the existing MetricsSystem.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/7299/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/7301/
Test FAILed.

alluxio.master.table.transform.TransformManagerTest.jobHistory(alluxio.master.table.transform.TransformManagerTest)
Run 1: TransformManagerTest.jobHistory:223->heartbeat:328 » Runtime Timer for thread ...
Run 2: TransformManagerTest.jobHistory:223->heartbeat:328 » Runtime Timer for thread ...

jenkins, test this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/7302/
Test PASSed.

@calvinjia PTAL, I mainly add the resetAllMetrics logic in the MetricsSystem. Thanks

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/7308/
Test PASSed.

alluxio-bot, merge this please.


1.16.x support?

Are you going to make 1.16.x version?

Rewrite is in progress

Rewrite is in progress

I have done a good chunk of the conversion in my Fork, I have it loading with 1.16.5 and SOME functions working but I am now a bit out of my depth and would LOVE for your input/assistance as the creator!

Mod is now rewritten for 1.18.x!

I just want to confirm by the close that there is no intent to backport for 1.16.5? I only ask as a LOT of old/legacy 1.12 mod authors came out of the woodwork and updated their mods for 1.16 and have since dropped off the planet again not updating for 1.17 or 1.18

Yea, I don't think I'll be backporting for 1.16.x.


refactor(cdk/table): change deprecated APIs for v12

Changes the APIs that were marked as deprecated for v12.
BREAKING CHANGES:

_viewRepeater, _coalescedStyleScheduler, _stickyPositioningListener and _viewportRuler
parameters of the CdkTable constructor are now required.
_coalescedStyleScheduler parameter of the StickyStyler constructor is now required.

I just realized that I forgot to remove the @Optional from the parameters that aren't optional anymore. Pushing another change now...


ptcolors v0.1.x

📜 Software Release Plan 📜
Purpose

Requirements

Quality Criteria

Approach

Cost/Benefits/DisBenefits/Risks

Personnel and Resources

Lead:
Composition of the Solution

Inputs

Delivery Approach & Schedule

CC

@cmbengue-ec-intl
@ECImingee
@Azendae-Popo

Key Results and Deliverables

### v0.1.0-3
- [ ] https://github.com/ec-intl/tcolors/issues/2
- [ ] https://github.com/ec-intl/ptcolors/issues/8

### v0.1.4-6
- [ ] https://github.com/ec-intl/ptcolors/issues/11

### v0.1.7-8
- [ ] https://github.com/ec-intl/ptcolors/issues/14
- [ ] https://github.com/ec-intl/ptcolors/issues/19
- [ ] https://github.com/ec-intl/ptcolors/issues/20

Complete 🌵


rp2040 multicore code style?

the first para of spawn_core1 function is _core1: CORE1, but this function does't need it, as there is a _ before core1.
When I only have compute and no peripherals operation on core1, how to put
   let p = embassy_rp::init(Default::default());

into core0 task without
103 |     spawn_core1(p.CORE1, unsafe { &mut CORE1_STACK }, move || {
    |                 ------- value partially moved here

compiler error?

I believe the point of that unused parameter is to prove ownership of the CORE1 peripheral. It prevents you from accidentally running spawn_core1 twice.
To use other peripherals in other tasks, you can use the same partial move pattern - but you'll need to pass in each part you want to use as a separate param, rather than the whole p


Add proof of concept

https://deep-foundation.github.io/questions-and-answers/questions/1.html is added.
It is done using the most popular Stack Overflow question, answers were merged from multiple most voted answers using GPT-4.


Bucket.location cannot be changed once assigned

Addresses #5194 by restricting location to only be settable once as we cannot alter the location of a bucket afterwards

A quibble:  the location of a bucket (our local proxy instance) could logically be changed right up to the point that the server-side bucket is created.   There isn't a good way to detect this, since the server-side bucket could be created or deleted from another process / instance at any point.  Do we win by trying to validate it on the client side at all?

@tseaver , I had pretty much the exact same internal debate while making this. I could both see leaving it as is or taking the change. On one hand, it is correct that we don't really know until we try on the server. On the other hand this allows the user to sort of go down a bad path.
I could also see it being reasonable to instead validate on patch, since the problem really seems to be that after patch the user was expecting an update to the object. I didn't go down that path but it seems reasonable that, since we can't patch the server side with the change requested, that operation could fail instead.

Do we win by trying to validate it on the client side at all?

In general, no, we do not. We should always err on the side of being too lax on the client side and letting the server deal with validation.

@jonparrott , does it make sense to bail on this entirely and leave things be? Or would you be fore hardening our patch code to report the failure. Right now I think we just silently fail and continue even though we can't patch the location.

we should definitely report errors back for any API call that fails.

The lowest level issue (not trying to handle location edits client side) is that the method patch doesn't report any issue when a property fails to patch. Today, if a user modifies Bucket.location and patches, it will just get reset to the original location.
>>> bucket = client.get_bucket('bucket-test-5194')
>>> bucket.location
'US'
>>> bucket.location = "EU"
>>> bucket.location
'EU'
>>> p = bucket.patch()
>>> bucket.location # Bucket is now back to US
'US'

So the core issue is that we allow this edit but don't let the user understand why location wasn't respected.

Hmm, I see. And that's likely the case because we don't send location at all in the patch request?
Idk. I feel like this is maybe something that can be solved with a docstring.

We already have such a docstring on client.create_bucket =>
        """Create a new bucket.
...
        To set additional properties when creating a bucket such as
        :attr:`~.Bucket.location`, use :meth:`~.Bucket.create`.
...

Even with this there was some confusion, so that is making me wonder if that is really enough.

well then.
@frankyn wdyt?


Inclusive Language Fix

Do you mind running all of gulp to update the binaries, as mentioned on CONTRIBUTING.md?


init

Status
Ready/In Progress/In Hold (Reason for hold)
Related Content Pull Request
Related PR: link to the PR at demisto/content
Related Issues
Related: link to the issue
Description
A few sentences describing the overall goals of the pull request's commits.

This PR needs a force-merge as the build is failing on errors that are not relevant for a deprecated image.
There is a ticket open for this issue here: CIAC-11362


Fix typos

Thanks! Can you please split the vax and docs change in a separate commit? Would ease for us to upstream this work to antidote. :)

Thanks for the contribution, I think it's ok to merge it as is and cherry-pick necessary changes later.

:partying_face: :partying_face: :partying_face: :partying_face: :partying_face:


Convert Events into extension functions AND Modify the way Novu class is constructed

The 2 constructors for the Novu class are now Novu(apiKey) and Novu(novuConfig) (instead of Novu(apiKey, novuConfig)). That means the NovuConfig class now has apiKey as one of the fields. With this approach, we can easily introduce more parameters into the NovuConfig class in the future

Also, for separation of concerns, the Event functions were extracted into a dedicated class

@nulllvoid @Cliftonz Please review


docker-node-version-fix

Apply the node version pinning fix proposed in issue https://github.com/julianfbeck/localpdfmerger/issues/18

@FabriceBoyer Thanks!


Add tooltip over copy icon in reimburse expenses page

Details

Added tooltip over copy icon in "Reimburse expenses" page. Issue is occurring in Web and Desktop App.
Fixed Issues

$ https://github.com/Expensify/App/issues/7466
Tests

Settings > Workspace > Reimburse expenses
Hover over copy icon in Capture receipts section

QA Steps

Settings > Workspace > Reimburse expenses
Hover over copy icon in Capture receipts section

Tested On

[x] Web
[ ] Mobile Web
[ ] Desktop
[ ] iOS
[ ] Android

Screenshots

Web

Mobile Web

Desktop

iOS

Android

There is  'MODULE_NOT_FOUND' error in E2E iOS Tests. I don't know how my change in code can produce that error.

Could you try pulling main into your branch and seeing if that fixes the tests?

Could you try pulling main into your branch and seeing if that fixes the tests?

Thank you.

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by @thienlnam in version: 1.1.38-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by @Julesssss in version: 1.1.38-3 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Correct link for "Re-evaluating how we work: bringing the whole team along"

Link text "soft launch" in paragraph "Final deliverable"

@daniel-coleman-1 I think we should just remove this link, since the site's no longer out there.

This is fixed.


Reference to ControllerContext

How to get a reference to (or create) a ControllerContext when method is executing from a scheduled task or web service so there is no request? Many thanks in advance for any clues.

there is premium template with some background running task example...

In background service there is no controller context, so you should have none. There is some background service samples in StartSharp.


Linting, dependency management and code formatting

Rn, the extension doesn't have any dependency management, linting or code formatting. I propose that we:

Initialize the extension as an npm package
Add eslint with the airbnb config, to maintain code consistency
Set up a githook using husky to automatically lint and format code as soon as it's staged.

Add prettier too. Not sure how well prettier plays with husky though. You might have to the git index stuff we did previously.

Yep we should add prettier too. I just configured husky to work with prettier and eslint. It was pretty straightforward.

@AdaephonBen, remember the git index issue we previously had? Can you make sure that isn't the case?

@TarunNoone, please let me know before you setup ESLint and more importantly, first run. There are a couple of minor Git issues that popup and I don't want you guys to be affected by them down the line.

Pre-commit errors?
On Mon, Oct 5, 2020, 19:37 Tarun Noone<EMAIL_ADDRESS>wrote:

Added Husky, ESLint Airbnb Config and Prettier. Pushed to linting_v1
branch. Pre-Commit errors have not been fixed.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/iith-dashboard/AIMS-Helper-Chrome/issues/18#issuecomment-703656061,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AINGXXMS44VY5LTGKXVNBPLSJHHLZANCNFSM4RZN2FMQ
.

--
Disclaimer:- The information contained in this electronic message and any
attachments to this message are intended for the exclusive use of the
addressee(s) and may contain proprietary, confidential or privileged
information. If you are not the intended recipient, you should not
disseminate, distribute or copy this email. Please notify the sender
immediately and destroy all copies of this message and any attachments. The
views expressed in this E-mail message (including the enclosure/(s) or
attachment/(s) if any) are those of the individual sender, except where the
sender expressly, and with authority, states them to be the views of IIT
Hyderabad. Before opening any mail and attachments please check them for
viruses, malware, and the sender email address is indeed from IITH domain.
IITH does not accept any liability for malware infected mails.

ESLint and Prettier errors. There are quite a few of those.

I've fixed a few pre-commit errors. #19 took care of the rest. I've added firebase and html2pdf as NPM modules and removed the static imports. There are only 2 errors left.

All ESLint errors have been resolved.

@TarunNoone Cool. Apparently, no one has a copy of the AIMS registration page, so we'll have to wait a few days for the Add/Drop period to start. We can close this issue and merge back to master then.

Initialized as npm package; Code fixed to conform to ESLint Airbnb Config; Lint-staged and Husky set up.

Good work on this, @TarunNoone


Unable to load plugin with version 2024.3 of IntelliJ

Hi,
There was a new version of IntelliJ released not long ago and some of my coworkers are already using it. We'd prefer not having to downgrade those installs.
Do you think it would be possible to update the plugin to support version 2024.3?

Hi @Willbill360!
Nice to learn this plugin is seeing some real use, it helps with motivation :)
For some reason, my JetBrains Toolbox wasn't showing the 2024.3 release, but I can update now. I will test the plugin with the new version and make a new release of the plugin. It usually takes a few days to pass validation, so you can expect it for the beginning of next week!

The new version is already available, it skipped validation this time.

Thanks a lot @qligier for the quick turn around!


Not working... Any tips?

Url directory works fine, used provided gif URL as to ensure proper link format, preview shows black screen and did not seem to work.
Any help is appreciated. Thanks.

Update - in using a different gif URL, got it to show up in the preview
Alas, shows as a black screen in screensaver and background mode flips back to stop every time I set it to start.

Update - screensaver works, background doesn't.
Keeps switching to stop every time I set it to start.

@iwantmac-hacks
Oh right, I actually haven't tested that feature at all. What is it supposed to do?

Alright, I looked into it. So in the original repo this is stated:
Note: AnimatedGif is not working with Catalina(10.15) since screensavers are now sandboxed (this means no GIF files can be selected or read from local disk and also background mode is broken), see issue #57.
I've only resolved the gif file issue, not the background mode one.


Show doc tooltips when hovering properties in the theme editor

Just a small QOL thing I wanted to do in a while. I took some inspiration from dalexeev's work in the signal dock on how to implement it.

Let's draft it until https://github.com/godotengine/godot/pull/82051 is ready.

This PR now makes use of the new EditorHelpTooltip and it's ready for review.

Thanks!


Cache downloaded data / use simulated data for faster testing

The issue
Testing with TravisCI is currently slow. This is painful for quick development, since a single run of all the builds on Travis currently takes ~40 minutes (due to the limit in # of concurrent jobs). Merging a PR then triggers a build on master, holding up subsequent PRs until that merge build is complete.
The primary holdup for these tests is, by a wide margin, fetching the raw microarray data from the Allen Institute. Unfortunately, investigating the caching abilities of Travis suggests that trying to store all the downloaded data would not be particularly fruitful...
Something needs to be done to make these builds quicker, though, because development is getting painful with the current process.
Proposed solution
One option to consider is making the jump to CircleCI. CircleCI specifies that caches should be no larger than 500MB; while the data downloaded by abagen tests is approximately 700 MB zipped we could split the tarballs for each donor (300 + 400MB, respectively) into two caches. This would certainly be faster than the current method, but may not actually net huge improvements...
Another alternative is to modify the TravisCI builds to only use real data for a few of the builds and just test on simulated data for the remainder. I'm not sure whether the simulated data would be as effective as the real data in catching bugs, but as long as we have a few "real" tests then hopefully things won't go too awry.
It might be worth playing around with CircleCI to see the extent to which it could improve build times. If CircleCi works then we could modify all the TravisCI tests to use simulated data; otherwise, we can investigate moving some of the Travis tests to simulated data.

Closed with #123 via #122!


Properly handle JSON String values for object type

When doing type conversion for strings when the expected type is object and the string contains a JSON encoded object, it is not converted to object.
This breaks response validation in swagger-restify, which sets up connect middleware, which passes the body of the response to the validator as a string: https://github.com/theganyo/swagger-node-runner/blob/master/lib/connect_middleware.js#L162. I can't see what else it can do, and it would have worked before 473c6db.

Ironically, the reason this feature was removed was because of swagger-node-runner.  What version of swagger-node-runner are you running?  If it's not the latest, do you mind upgrading and trying with sway as-is?  Let me know what you find out.

It is the latest. Just spent the day fixing npm update issues :-)
─┬<EMAIL_ADDRESS>└─┬<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>

Okay.  I don't see why we can't just add this back and resurrect its tests but I'd love to let @theganyo chime in first.

Also, if you don't mind could you create an issue in swagger-node-runner for this as well, for posterity?

I don't recall any specific reason from prior discussions why this feature was removed. The only discussions I'm remembering were around not parsing when the type was indeterminate. But maybe I'm forgetting something?

Could be.  Maybe too much was removed.  I'll add it back so that when we know the type is object and the value is a string, we try to parse it.  We should do the same for arrays.


Bump Ruby v on Travis, remove Date Parse

Just some quick tweaks to pass on Travis (hopefully) and not parse those dates on the garden_crop_create mutation.

Cool. While I'm here, let's see if the Mongoid team saw the issue I raised.