test 5

---
url: 'https://uxarray.readthedocs.io/'
thumbnail: 'https://raw.githubusercontent.com/UXARRAY/uxarray/921dd8f42f661692f0cec170ee5c7dbedb294237/docs/_static/images/logos/uxarray_logo_v_dark.svg'
title: 'UXarray'
description: 'Xarray extension for unstructured climate and global weather data' # A brief description of the resource.
authors:
- name: 'Aaron Zedwick'
  affiliation: 'Liberty University'
  affiliation_url: 'https://www.liberty.edu/'
- name: 'Anissa Zacharias'
  affiliation: 'NSF National Center for Atmospheric Research'
  affiliation_url: 'https://ncar.ucar.edu/'
- name: 'Brian Medeiros'
  affiliation: 'NSF National Center for Atmospheric Research'
  affiliation_url: 'https://ncar.ucar.edu/'
- name: 'Colin Zarzycki'
  affiliation: 'The Pennsylvania State University'
  affiliation_url: 'https://www.psu.edu/'
- name: 'Hongyu Chen'
  affiliation: 'University of California Davis'
  affiliation_url: 'https://www.ucdavis.edu/'
- name: 'Ian Franda'
  affiliation: 'University of Wisconsin-Madison'
  affiliation_url: 'https://www.wisc.edu/'
- name: 'John Clyne'
  affiliation: 'NSF National Center for Atmospheric Research'
  affiliation_url: 'https://ncar.ucar.edu/'
- name: 'Michaela Sizemore'
  affiliation: 'National Renewable Energy Laboratory'
  affiliation_url: 'https://www.nrel.gov/'
- name: 'Orhan Eroglu'
  affiliation: 'NSF National Center for Atmospheric Research'
  affiliation_url: 'https://ncar.ucar.edu/'
  email<EMAIL_ADDRESS>- name: 'Paul Ullrich'
  affiliation: 'University of California Davis'
  affiliation_url: 'https://www.ucdavis.edu/'
- name: 'Philip Chmielowiec'
  affiliation: 'NSF National Center for Atmospheric Research'
  affiliation_url: 'https://ncar.ucar.edu/'
- name: 'Rachel Tam'
  affiliation: 'University of Illinois Urbana-Champaign'
  affiliation_url: 'https://illinois.edu/'
- name: 'Rajeev Jain'
  affiliation: 'Argonne National Laboratory'
  affiliation_url: 'https://www.anl.gov/'
- name: 'Robert Jacob'
  affiliation: 'Argonne National Laboratory'
  affiliation_url: 'https://www.anl.gov/'
tags:
  packages:
    - xarray
    - dask
    - numba
    - numpy
    - spatialpandas
    - datashader
    - holoviews
    - matplotlib
  formats:
    - documentation
    - tutorial
  domains:
    - Unstructured Grids
    - Data Analysis
    - Data Visualization
    - Atmospheric Science
    - Climate Science
  affiliation:
    - Pangeo
    - Raijin
    - SEATS
---

@erogluorhan Good news #477 was opened

Great!

@erogluorhan just wanted to note that the yaml file, while containing the same information, has a lot of restructuring from this different yaml saving method - https://github.com/ProjectPythia/projectpythia.github.io/pull/477/files

Yeah, noticed that! Feels a bit awkward to see them sorted by the authors instead of titles, but that's okay I suppose. Also, this restructuring is only for this time, then the newer ones will only add the new gallery item, right?

@erogluorhan that's my thought as well, but I suppose we could merge a PR for the restructuring (the test PR has a duplicate UXarray entry) and then run a new test.


HDFS-15745. Make DataNodePeerMetrics#LOW_THRESHOLD_MS and MIN_OUTLIER_DETECTION_NODES configurable. Contributed by Haibin Huang.

Description of PR
HDFS-15745. Make DataNodePeerMetrics#LOW_THRESHOLD_MS and MIN_OUTLIER_DETECTION_NODES configurable.
How was this patch tested?
For code changes:

[x] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
9m 48s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-3.3 Compile Tests _

+1 :green_heart:
mvninstall
33m 37s

branch-3.3 passed

+1 :green_heart:
compile
1m 13s

branch-3.3 passed

+1 :green_heart:
checkstyle
0m 49s

branch-3.3 passed

+1 :green_heart:
mvnsite
1m 19s

branch-3.3 passed

+1 :green_heart:
javadoc
1m 25s

branch-3.3 passed

+1 :green_heart:
spotbugs
3m 14s

branch-3.3 passed

+1 :green_heart:
shadedclient
27m  9s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m 11s

the patch passed

+1 :green_heart:
compile
1m  6s

the patch passed

+1 :green_heart:
javac
1m  6s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 41s

the patch passed

+1 :green_heart:
mvnsite
1m 15s

the patch passed

+1 :green_heart:
xml
0m  1s

The patch has no ill-formed XML file.

+1 :green_heart:
javadoc
1m 16s

the patch passed

+1 :green_heart:
spotbugs
3m 16s

the patch passed

+1 :green_heart:
shadedclient
26m 59s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
210m 34s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 37s

The patch does not generate ASF License warnings.

322m 44s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.blockmanagement.TestBlockTokenWithDFSStriped

hadoop.hdfs.server.datanode.TestDirectoryScanner

hadoop.hdfs.tools.offlineImageViewer.TestOfflineImageViewer

hadoop.hdfs.TestRollingUpgrade

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3992/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3992

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell xml

uname
Linux 84d43b1571d0 4.15.0-163-generic #171-Ubuntu SMP Fri Nov 5 11:55:11 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.3 / 81aa7a942b0af7d854b94431e34dd731bdb343c7

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3992/1/testReport/

Max. process+thread count
2163 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3992/1/console

versions
git=2.17.1 maven=3.6.0 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

The failed tests seem not to related. I'm merging it.


Following the license change, modify the boilerplates in crypto/sha/

Merged.
a598ed0dc444e010973c51e024e9b497a9340fee Following the license change, modify the boilerplates in crypto/sha/


REST API: support Application emojis

As of now, discordgo's restapi.go supports control of Guild based emojis, but not Application based ones.
The docs related to Guild and Application emojis are located here: https://discord.com/developers/docs/resources/emoji.
I am interested in supporting all the endpoints that begin with /applications/.
Screenshot below is from the https://discord.com/developers/applications/APPLICATION_ID/emojis page.

Currently I have written this function in my personal project to GET a specific emoji by ID:
// applicationEmoji fetches an emoji from the application
func applicationEmoji(s *discordgo.Session, applicationID string, emojiID string, options ...discordgo.RequestOption) (emoji *discordgo.Emoji, err error) {
	var body []byte
	body, err = s.RequestWithBucketID("GET", discordgo.EndpointApplication(applicationID)+"/emojis/"+emojiID, nil, discordgo.EndpointApplication(applicationID), options...)
	if err != nil {
		return
	}

	err = discordgo.Unmarshal(body, &emoji)
	return
}

// Example usage in my project
emoji, err = applicationEmoji(s, applicationID, emojiID)

I am working on an implementation that is close to the Guild emoji functions.
Progress tracked at this PR, suggestions appreciated.

Closed by https://github.com/bwmarrin/discordgo/pull/1566?

You're right, forgot to add the closes mention in the PR 👍


.btn should allow simple margin overrides

Developing with helper classes has become an excellent use of ply.
Simply pulling and using ply iso or complete, one should be able to simply use something like the following:
<button class="btn margins--margin-bottom">ClickyBoy</button>
To show a button with some margin below it to leave some breathing room before the next bit of content starts.
However, The .btn has a margin: 0 which overrides this simple helper class.
Proposed solutions:

Remove margin: 0 from the .btn selector.
Remove the button.btn selector
Only use button, input[type="button"], etc selectors for bg, border, radius, and not for margin: 0
Some kind of combination of the above.

Thoughts?

Stale, if it needs more discussion reopen it.


Add please  profile sync for plugins, settings and etc...

Add please  profile sync for plugins, settings and etc...
I would like to have synchronization of program settings and installed plug-ins or through an account or via import export, or even better through the cloud :)

There is a good extension for this: https://marketplace.visualstudio.com/items?itemName=Shan.code-settings-sync


#2312 #2398

Fix potential NRE when editor instantiates component

editor can load components via MEF before the package load. I've seen the case in user logs.

#2312 Odd list of directories after installing package in remote

hack really. I am open to better approaches.

#2398 Add yellow state to the connection indicator

will be adding tests

👍


Add photo in edit posts.

Starting the implementation of add photo in edit posts.

Finished implementing add photo in edit posts.


Login Error

Hello!
Maybe will be better to stop trying to login when bot getting login errors like InvalidPassword, AccountLogonDeniedNeedTwoFactorCode, etc.
Bot just trying and trying and steam blocking you for a while.

#855


Standardized Readme

See multiformats/multiformats#13

LGTM, thanks!
The licenses on existing things should probably either stay with their authors for now (particularly those of non-PL people). new things can be PL.


[refactor] remove redundant this

Proposed changes
Removing redundant this, since it is required mostly in constructor.
Issue Number: #9775
Problem Summary:
Before pr:
public AlterHandler getSchemaChangeHandler() {
        return this.schemaChangeHandler;
}

After pr:
public AlterHandler getSchemaChangeHandler() {
        return schemaChangeHandler;
}

Checklist(Required)

Does it affect the original behavior: No
Has unit tests been added: No
Has document been added or modified: No Need
Does it need to update dependencies: No
Are there any changes that cannot be rolled back: No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

BTW, please git rebase and fix the conflict

You can learn knowledge about git.
You can use git rebase and fix conflict.
Now, this PR include some other PR....😂

BTW, thought this problom of this. exist in many files.
You can just fix 10-20 files rather than so many files which is easier to the first-time contribution.

I am trying this.

😂 new conflict

What should I do now ?
I am not able to resolve that conflict issue.
The one thing now I can do is again create fork and starting all over again.

If you have good suggestions than your welcome.

are you talking about
fe/fe-core/src/main/java/org/apache/doris/blockrule/SqlBlockRule.java
this files conflict.

This is what showing

The one thing now I can do is again create fork and starting all over again.

😂It's ok. A PR with a lot of files has conflicts isn't easy for the newer.
You can create a new PR.
What's more, you also can learn something about git rebase and fix conflict, which is useful to your next open-source trip.

usually, my behavior.
# set doris upstream and fetch
git remote add upstream https://github.com/apache/incubator-doris.git
git fetch --all

# rebase to upstream master
git rebase upstream/master

# fix conflict

Some material introduce it. like this
https://www.youtube.com/watch?v=RGtwxYqkkas

Now it's ok or not ?
Or I have to create new PR

Now it's ok or not ?
Or I have to create new PR

You can create a new PR, it's ok and easier

You can try
git rebase

git push -f

in new PR.
It will be better than git merge, which can avoid following.

I forgot it can't comment after close PR

When I am trying to create new pull request

You can recreate a new branch.
Carry this PR's modification in about 10 files to it.
This branch after git merge is a little mess.


Change Location Form Field to Address to Avoid Confusion in Request

Goes along with #125  Please refer.

similar issue logged


Add New Windows 11 Wallpaper Dracula Edition

I have created a new  wallpaper for Windows 11 (Dracula Edition) . Please, accept the work.

From the documentation mentioned by @freezboltz:

Without a written license or express permission under one of Microsoft's other published guidelines (e.g., Specific Brand and Product Guidelines below), don’t do the following:
Don’t use Microsoft’s logos, icons, or designs, in any manner.

Theres a Windows 11 specific guideline further down the page, which says:

A trademark use license is required to:

Use any Windows logo, symbol or icon.
Indicate sponsorship or endorsement by Windows.

So basically, no one is ever allowed to publish a wallpaper containing the windows logo except Microsoft.
~I don't think that they would go after people if they did anyway, because  Windows themed wallpapers exist all over the internet.~


Add solidity wrappers for CIP-20/30/31 precompiles

Description
CIP-20/30/31 add new precompiles to the celo blockchain. Using these is hard without a set of solidity wrappers. This PR provides these wrappers.
Original implementation from https://github.com/prestwich/b12-sol.
I'm not sure if it was correct to use forge install to install the memview package. If it was, I wonder how I should proceed with the tslint error. Manually editing external dependencies to fix lint errors seems wrong, since it will make it harder to update dependencies.
Tested
Since the wrappers can only be tested against a blockchain implementation with support for the respective precompiles, we can't use ganache to run the tests. Therefore, the wrappers are tested in the celo-blockchain repo against the real implementation.
Related issues

Implementation for https://github.com/celo-org/celo-blockchain-planning/issues/42
Testing happens in https://github.com/celo-org/celo-blockchain/pull/2058

Backwards compatibility
No existing contracts are changed -> backwards compatible
Documentation
See https://github.com/celo-org/docs/pull/872

Oh, one more comment. A more appropriate place for the libraries could be under contracts/common/libraries/.

Oh, one more comment. A more appropriate place for the libraries could be under contracts/common/libraries/.

Make sense. I just took UsingPrecompiles as an example, since it serves a similar purpose.

Oh, one more comment. A more appropriate place for the libraries could be under contracts/common/libraries/.

Make sense. I just took UsingPrecompiles as an example, since it serves a similar purpose.

Ah, makes sense. Actually, looking at the libraries/ directory, it doesn't look like we're really using it nor what it's exact purpose is - there's one library and one contract there, that could instead probably live just in common/ given that's where all the other libraries and helper contracts live right now. Given that, I'd keep your libraries where you put them for now, maybe a future task to reorganize the file structure of contracts/more consistently/usefully.

Not sure how much cryptography expertise

I'm just a developer, not a cryptographer. I can read the code but I don't know the math behind it. So I don't think it makes sense for me to add documentation on the actual crypto part. There's not that much more on that front that I can provide beyond the basic introduction I wrote at https://github.com/celo-org/docs/pull/872.

So I don't think it makes sense for me to add documentation on the actual crypto part. There's not that much more on that front that I can provide beyond the basic introduction I wrote at celo-org/docs#872.

Sounds good, thanks! Crated an issue to track this. Maybe someone could take the low hanging fruit of the more obvious functions (maybe me if I find the time), then would be good to have someone like @kobigurk  fill in the rest.

Is there anything I can do on my side make this ready for merging?

Regarding the failed Google Cloud Build (docker images). I think it is because submodules are not installed with yarn build, so the images can't get built. I already fixed this here: https://github.com/celo-org/celo-monorepo/pull/10124
So when my PR gets it should turn green without any conflicts.


build(docker): support all platforms that publish release supports

closes #235

Inspired by #235 :slightly_smiling_face:

@kkhan01 Thank you for your contribution!
FYI @jtagcat

reverted because typo, see #238


Options for AWS ElasticSearch Service?

Currently, it doesn't seem like this project can work with the AWS hosted ElasticSearch Service. In their limitations section, they specifically mention:
"The service supports HTTP on port 80, but does not support TCP transport."
Because of this, when attempting to use this project with the AWS ES service, one gets a org.elasticsearch.client.transport.NoNodeAvailableException.
Is there a setup or configuration available to use the REST API instead of the TransportClient? If not, are there any plans for making this available?

Thanks for the hint.
Yes, I plan to add HTTP bulk client support in the next version.

Nice!
AWS uses ES 1.5.2. Will the intended solution be available on previous
branches/tags? Or, will the new version work with ES 1.5?
On Nov 17, 2015 5:24 PM, "Jörg Prante"<EMAIL_ADDRESS>wrote:

Thanks for the hint.
Yes, I plan to add HTTP bulk client support in the next version.
—
Reply to this email directly or view it on GitHub
https://github.com/jprante/elasticsearch-jdbc/issues/697#issuecomment-157529724
.

If you want JDBC importer for ES 1.5 I would have to make a backport of the importer style. Of course, I can do that.
I'm confident the bulk HTTP API has not changed between 1.5 and 2.0, but I'm not 100% sure.

I think it would be beneficial. Amazon specifically states they support ES 1.5.2, so anyone trying to use this project with the new AWS ElasticSearch service will probably attempt to use the 1.5 branch first.
Thanks!

@jprante We're facing the same issue. Did you get a chance to make a backport of the importer style? Is there a hack or solution we can try? Thanks in advance.

I pushed out JDBC importer version <IP_ADDRESS> for Elasticsearch 1.5.2
http://xbib.org/repository/org/xbib/elasticsearch/importer/elasticsearch-jdbc/<IP_ADDRESS>/elasticsearch-jdbc-<IP_ADDRESS>-dist.zip
Please try out if it can work with AWS ES, I don't have access to it.

Hi
Tried out this version and I get
[05:30:40,824][WARN ][org.elasticsearch.transport.netty][elasticsearch[importer][transport_client_worker][T#1]{New I/O worker #1}] [importer] exception caught on transport layer [[id: 0x83bc06f5, /<IP_ADDRESS>:33909 :> xxxxxxx.us-west-2.es.amazonaws.com/<IP_ADDRESS>:80]], closing connection
java.io.StreamCorruptedException: invalid internal transport message format, got (48,54,54,50)
	at org.elasticsearch.transport.netty.SizeHeaderFrameDecoder.decode(SizeHeaderFrameDecoder.java:47) ~[elasticsearch-jdbc-<IP_ADDRESS>-uberjar.jar:?]
	at org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:425) ~[elasticsearch-jdbc-<IP_ADDRESS>-uberjar.jar:?]
	at org.elasticsearch.common.netty.handler.codec.frame.FrameDe...

Elastic Search Version
{
  "status" : 200,
  "name" : "Living Monolith",
  "cluster_name" : "lorem",
  "version" : {
    "number" : "1.5.2",
    "build_hash" : "62ff9868b4c8a0c45860bebb259e21980778ab1c",
    "build_timestamp" : "2015-04-27T09:21:06Z",
    "build_snapshot" : false,
    "lucene_version" : "4.10.4"
  },
  "tagline" : "You Know, for Search"
}

I will drop you an email with an aws node address so that you can try it also.

It looks like AWS is only supporting HTTP.
HTTP support for JDBC importer is work in progress. Please be patient.

Any news on the HTTP support for JDBC?

Im trying to do this now myself!! I want to bulk index with jdbc importer to es service on aws which is 1.5.2.
Any suggestions what I can do!?

You can always write your own JDBC importer by forking the code.
At the moment, HTTP is not that important for JDBC importer. Also, supporting ES 1.5.2 is awkward to me, it's an unsupported, unstable und outdated version. Maybe AWS can offer supported toolkits to customers who are paying them to get data imported from DB, or can switch to up-to-date ES 2+. I'm just writing code in my limited spare time and have no relationship and no interest in AWS.

I appreciate the response mate.
I understand that 1.5.2 is extremely old. Current version is 2.3.2 and is what i would prefer to use!
But currently I am doing a technical spike of aws managed service. From what i gather they are planning to update but not sure when that will happen.
I will fork your repo and see  can i introduce jest.


Help Needed: sheriff.config Rules Not Enforcing as Expected

I thought this was the best place to post my issue after stackoverflow.
I'm having trouble understanding why I don't get an error when the rules defined in sheriff.config are violated. For example, when placing a component from one domain into another, or placing a feature component in the ui or util folders.
Here is my sheriff.config:
export const config: SheriffConfig = {
  version: 1,
  entryFile: 'src/main.ts',
  tagging: {
    src: {
      app: {
        'domains/<domain>': {
          '<type>/*': ['domain:<domain>', 'type:<type>'],
        },
        'shared/<type>/*': ['domain:shared', 'type:<type>'],
        'openapi/<domain>/*': ['domain:<domain>', 'type:util'],
      },
      environments: ['domain:shared', 'type:util'],
    },
  },
  depRules: {
    root: ['*'],
    'domain:*': [sameTag, 'domain:shared'],
    'type:feature': [
      ({ to }) => to.startsWith('type:ui'),
      'type:data',
      'type:util',
    ],
    'type:ui': ['type:data', 'type:util'],
    'type:data': ['type:util'],
    'type:util': noDependencies,
  },
};

And here is the a partial output of npx sheriff list command:
. (root)
└── src
  ├── app
    ├── domains
      ├── device
        ├── data (domain:device, type:data)
        ├── feature (domain:device, type:feature)
          ├── default-parameters (domain:device, type:feature/default-parameters)
          └── tracker-details (domain:device, type:feature/tracker-details)
        ├── ui (domain:device, type:ui)
        └── util (domain:device, type:util)
      └── gateway
        ├── data (domain:gateway, type:data)
        ├── feature (domain:gateway, type:feature)
          └── gateway-details (domain:gateway, type:feature/gateway-details)
        ├── ui (domain:gateway, type:ui)
        └── util (domain:gateway, type:util)
    ├── openapi
      ├── gateway (domain:gateway, type:util)
        ├── api (domain:gateway/api, type:util)
        └── model (domain:gateway/model, type:util)
    └── shared
      ├── data (domain:shared, type:data)
      ├── feature (domain:shared, type:feature)
      ├── ui (domain:shared, type:ui)
        ├── card (domain:shared, type:ui/card)
      └── util (domain:shared, type:util)
  └── environments (domain:shared, type:util)

Here's the output of npx sheriff verify:
Verification Report :
No issues found. Well done!
Even if i dont respect the config...
I'm not sure how to resolve this issue. Does anyone have any ideas?

It would be great to have a working example, but since you've already posted the config, it is enough if you take the file in question and post its path and its import statements.

Just noticed that you have all your features in one parent folder feature which seems to be a module on its own?
Shouldn't it be more like?
. (root)
└── src
  ├── app
    ├── domains
      ├── device
        ├── data (domain:device, type:data)
        ├── feature
          ├── default-parameters (domain:device, type:feature)
          └── tracker-details (domain:device, type:feature)

In that case, your config should look like this:
export const config: SheriffConfig = {
  version: 1,
  entryFile: 'src/main.ts',
  tagging: {
    src: {
      app: {
        'domains/<domain>': {
          'feature/<feature>: ['domain:<domain>', 'type:<type>'],
          '<type>': ['domain:<domain>', 'type:<type>'],
        },
        'shared/<type>/*': ['domain:shared', 'type:<type>'],
        'openapi/<domain>/*': ['domain:<domain>', 'type:util'],
      },
      environments: ['domain:shared', 'type:util'],
    },
  },
  depRules: {
    // ...
  },
};

Just noticed that you have all your features in one parent folder feature which seems to be a module on its own?
Shouldn't it be more like?
. (root)
└── src
  ├── app
    ├── domains
      ├── device
        ├── data (domain:device, type:data)
        ├── feature
          ├── default-parameters (domain:device, type:feature)
          └── tracker-details (domain:device, type:feature)

In that case, your config should look like this:
export const config: SheriffConfig = {
  version: 1,
  entryFile: 'src/main.ts',
  tagging: {
    src: {
      app: {
        'domains/<domain>': {
          'feature/<feature>: ['domain:<domain>', 'type:<type>'],
          '<type>': ['domain:<domain>', 'type:<type>'],
        },
        'shared/<type>/*': ['domain:shared', 'type:<type>'],
        'openapi/<domain>/*': ['domain:<domain>', 'type:util'],
      },
      environments: ['domain:shared', 'type:util'],
    },
  },
  depRules: {
    // ...
  },
};

Yes here a screenshot

It would be great to have a working example, but since you've already posted the config, it is enough if you take the file in question and post its path and its import statements.

For instance here i import a component from an other domain (DDSComponent)

@alcaidio  Okay, in which folder is this file located?

@alcaidio I encountered a similar issue last week but wasn't sure if it was a bug or misconfiguration. I'll investigate and mark this issue as "potential bug" until further notice.

@alcaidio, I encountered a bug which might be related to your reported issue. Fix will come coon.

@alcaidio, can you please try it out with v0.17.0? I can confirm that the new dependency rules algorithm works on a really project and I hope that it was the cause of your issue.

@rainerhahnekamp i try with
@softarc/eslint-plugin-sheriff": "^0.17.0",
@softarc/sheriff-core": "^0.17.0",

But nothing change, i always can import component from a domain to another :/

Hello @rainerhahnekamp, @alcaidio.
I think I actually encountered this issue before, where Sheriff was unable to flag a forbidden module import as a Lint error.
I notice that in @alcaidio screenshot, the full path src/app/... is being used to import modules.
As weird as this may sounds:

This error happens when I was importing modules using the full import path, e.g. src/app/path/to/forbidden/module, like @alcaidio is doing. In this case, Sheriff is unable to flag the import as forbidden.

The error is gone, when I switch to using relative path to import modules, e.g. ../../../path/to/forbidden/module. In this case, Sheriff is able to flag the import as forbidden due to insufficient dependency rules.

The error is also gone, when I use path substitution in tsconfig.json to import modules. Basically in tsconfig.json:

{
  "compilerOptions": {
    // other configs
    "paths": {
      "@subs/*":  ["src/app/*"]
    }
}

Then in your code, use @subs/path/to/forbidden/module. Sheriff would be able to flag that this is a forbidden import.
I am unable to share screenshots due to company policy, but I hope the above info is enough for @rainerhahnekamp to do a bug re-production.
@alcaidio may be you can try switching your import paths to option (2) or (3) above and see if your problem is fixed.
I am using Sheriff version 0.16 by the way.

@hoangvutruong513 thanks for that tip.
It could be that these absolute imports couldn't be properly resolved. In case that happens, Sheriff silently skips them because they should throw a TypeScript compilation error either way.
Thanks, maybe there is connection to #122
I will investigate further

@hoangvutruong513 @alcaidio v0.17.2 can now also deal with static imports. Please give it a try and let me know if it works. Thank you

@hoangvutruong513 @alcaidio v0.17.2 can now also deal with static imports. Please give it a try and let me know if it works. Thank you

Hello @rainerhahnekamp, I just tested v0.17.3, glad to report that the issue I reported has been resolved. Now Sheriff correctly raised lint errors, regardless of the format of the import path (absolute/substituted/relative paths).
Although the update to the core dependency logic introduced in v0.17.2 has led to new dependency errors in my codebase.
After reading the doc, am I correct to say that ALL from tags need to satisfy ANY to tags in order for the lint rule to pass?
Thank you again for this amazing library. Kudos to the new documentation too.

I am so glad to hear that. We had integration tests set up, but the final test is still done by someone else.
You are right about the new rules. The algorithm loops over the from tags and every from tag requires a clearance.
0.17.0 introduced these changes, which could lead to new dependency errors. The reason was to streamline it to the way how Nx is doing it.
Thanks a lot, @hoangvutruong513. If you encounter other issues, let us know. Of course, the same goes for you, @alcaidio.
Going to close this issue now.


:tada: Add performance kit to leaderboard

Adding a contender to the leaderboard. 😄 🤣
Tested on incognito chrome and got 0.8s 🥇

Hey @code-mattclaffey, I was browsing around and noticed the build failed on your PR. I think there's a linter in the CI that doesn't like the indentation in your JSON. Try converting to 2tabs/4spaces and see if the CI passes properly 😄

Hey @code-mattclaffey, I was browsing around and noticed the build failed on your PR. I think there's a linter in the CI that doesn't like the indentation in your JSON. Try converting to 2tabs/4spaces and see if the CI passes properly 😄

Thank you!

Thank you!


How to display(add) text right at the center of MDSpinner in kivymd

I am using MDSpinner in my kivy program and want to show(display) text right in the middle of MDSpinner.I tried adding MDLabel but it is always slightly off from center for different screen sizes.Is there any way to add text in the middle of MDSpinner circle?

@atheistrepublic This is against the rules of material design. You can make your custom spinner using MDSpinner as a basis.


⚠ Bofrost.de has degraded performance

In e1aff98, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1108 ms

Resolved: Bofrost.de performance has improved in 7017650.


Foundation for bidirectional

Hey Geoff.
This pull request adds many things, but not least of all the foundation for bidirectional C-Bus/ZigBee via zigbee2mqtt.
It adds:

Create/update/delete for ZIGBEE keyword settings, probably in an overkill way, but in a way that is highly extensible for adding new keywords. Think things like sensor value scale (scale=), or number of decimal places (dec=) for user parameter values.
Synchronous Mosquitto broker comms, avoiding loop_start to allow re-entry to script on error conditions that force an exit, handling socket:close before reopen on reentry as well.
Message queueing for inbound and outbound.
Mosquitto broker re-connection, with queueing of C-Bus level/status changes while the broker is out of action. Once re-connected all C-Bus messages will be sent to the broker in order.
Shifting the responsibility of keyword monitoring from event-based to resident (on check changes, which can be disabled). Plus adding validation of the hexidecimal ZigBee unique ID.

Using a ZigBee 'friendly' name if set is not yet considered.
I'm still waiting for a ZigBee interface to arrive, which has been stuck on Long Island NY for a while. Given a looming Easter I will probably give up all hope before it gets here. This is why I have not evolved sending to C-Bus from the broker subscriptions, as I'm running blind. But I thought I'd share where my head is going with all this.

I also removed the LWT and status=online because zigbee2mqtt will be managing this. We're just an intersted party to its topics, so I misled you there.

Some bug fixes and an untested MQTT light status update to C-Bus. I've ordered a Zigbee temp/humid sensor so that I can see how sensors work once the Zigbee coordinator arrives.

Hi Steve - this is awesome, I'll just merge.
I've just received some 3 relay zigbee modules that I suspect will require a bit of a refactor, and supporting friendly names is getting essential with the number of devices I have in zigbee2mqtt now.
So I'll get into that next few days (my cadence for spending time on this is lower than yours!)


[ErrorUtil] errorutil now updates component_info.json in directory sepcified by -i flag

fixing bug where errorutil was not updating component_info.json in th…e directory specified by -i flag
minor refactoring

Signed-off-by: Michael Gfeller<EMAIL_ADDRESS>Description
This PR fixes #84
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

Hey @mgfeller I tested this in my local machine and observed that the component_info.json file only remains in the helpers directory and is not generating outside the helpers directory anymore. @DelusionalOptimist what's your view on this?

thanks @DelusionalOptimist  and @sayantan1413 for you help and patience!


Cloud Code query not returning an instance of my subclass

All my models are defined like so:
var School = Parse.Object.extend("School",
{ // Instance methods
    doSomething: function() {}
},
{ // Class methods
});

I construct my queries like so:
var query = new Parse.Query(School);
query.equalTo(...);
query.first().then(function(s) {
    console.dir(s);
    s.doSomething();
});

In my cloud code running on the Parse backend, this query returns an instance of my School subclass, and I can invoke doSomething() on it.
In the same code running on parse-server, the query returns what looks like an abstract object, and invoking doSomething() fails with School.doSomething is not a function.
The output of console.dir(s) is:
ParseObject {
  _objCount: 0,
  className: 'School',
  id: 'kC9xAgytAM' }

Is there something I need to do to make parse-server use my subclasses when returning objects from queries, or is this a bug?

Some additional info: if do the same query in a separate client node process (using the latest JS Parse SDK and connecting to my localhost parse server), I do get back a ParseObjectSubclass, and I am able to call doSomething() on the returned object.
So this only happens when performing a query from Cloud Code hosted in parse-backend.

If I import the "real" (?) Parse SDK in my Cloud Code module, and use that import's Query class, then I get back the intended result (a ParseObjectSubclass).
However, for some reason, I cannot simply do:
var Parse = require('parse/node').Parse;

Because this gives this runtime error: Parse.Cloud.define is not a function.
So I have to do this:
var ParseSDK = require('parse/node').Parse;
ParseSDK.initialize('redacted', 'redacted');
ParseSDK.serverURL = 'http://localhost:5000/parse'

var query = new ParseSDK.Query(School);

But this doesn't feel right at all...

I have moved all my business logic functions into a separate module, which exports functions that are called by my Cloud Functions.
This allows me to require('parse/node') without errors.
However, whenever I try to use the Parse module (e.g. perform a query), I get this error:

You need to call Parse.initialize before using Parse.

Which leads me to believing that if I do have to call Parse.initialize, it means that whenever I run a query from within cloud code it performs an HTTP request to my parse-server to actually run the query... Is that the case?
I'm a little confused about how the Parse SDK behaves when used within Cloud Code...

Yes, Cloud Code is essentially just functions that are being called without any special context. If you're using the parse/node library from Cloud Code it's going to behave as it would in any other context. What you're probably wanting to do is access the ParseServer context from the req parameter passed in.

access the ParseServer context from the req parameter passed in

Care to elaborate on this? The only context that I see is:
{
    params: req.body || {},
    master: req.auth && req.auth.isMaster,
    user: req.auth && req.auth.user,
}

I have just updated to the latest HEAD (by doing npm install --save git+git@github.com:ParsePlatform/parse-server.git), and all of these issues went away:

Doing a Query from within a Cloud Function properly returns a parse object subclass
I no longer need to call Parse.initialize when using the Parse SDK

Looks like commit a65f2d13abdc9d4663d61308f426dd517491c9ee might be involved in resolving these issues.

@bourquep Currently the ParseServer context isn't be passed in to the req. I have done it in a few forks of mine, but haven't merged in with this branch. I'm not sure what exactly changed for your code to start working. If the Parse global was being initialized in index.js before your cloud code gets included via require() it should've already been working.

Well, not sure why it was not working and why it is now, but one thing's for sure is all I did was update parse-server to the latest HEAD (I was initially using v2.0.6).

Hi, I also can't get my custom subclass when fetching, finding or even createWithoutDataing outside Parse Cloud Code.
 When calling it from simple express route handler it doesn't.
Any ideas of why it doesn't work? And what should I do to make it work (besides moving to Cloud Code).


Add dtl and l2geth patches

Add dtl and l2geth patches

Codecov Report

Merging #24 (c4612fd) into develop (e77e2f4) will increase coverage by 17.29%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           develop      #24       +/-   ##
============================================
+ Coverage    73.98%   91.28%   +17.29%
============================================
  Files           64       31       -33
  Lines         2164     1078     -1086
  Branches       304      149      -155
============================================
- Hits          1601      984      -617
+ Misses         563       94      -469

Flag
Coverage Δ

batch-submitter
?

contracts
91.28% <ø> (ø)

core-utils
?

data-transport-layer
?

message-relayer
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

packages/core-utils/src/watcher.ts

.../batch-submitter/src/transaction-chain-contract.ts

packages/data-transport-layer/src/utils/eth-tx.ts

packages/batch-submitter/hardhat.config.ts

...kages/data-transport-layer/src/utils/validation.ts

packages/core-utils/src/common/index.ts

packages/core-utils/src/coders/sequencer-batch.ts

packages/message-relayer/src/relay-tx.ts

packages/data-transport-layer/src/utils/index.ts

packages/core-utils/src/batches.ts

... and 22 more

Continue to review full report at Codecov.

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


Migrate all relevant repos from travis-ci.org to travis-ci.com

Description
As a developer, I want to ensure Travis CI works properly after it's migration announced to happen "no later than 31 December 2020".
https://docs.travis-ci.com/user/migrate/open-source-repository-migration
Acceptance criteria

[x] all relevant repos migrated to travis-ci.com

Migrated the following repos:

pdx-admin-ui
pdx-data-core
pdxfinder
pdx-ontology

@zperova done

@zperova done


Allowing to opt-out of E2E timeout for non-point operations via system property or environment variable

This PR adds an option to opt-out of applying End-to-end timeouts for non-point operations like queries when the end-to-end timeout is defined on the CosmosClientBuilder. When the end-to-end timeout is specified on the CosmosQueryRequestOptions it is always applied independent of this override.
The opt-out can happen either via System property COSMOS.E2E_FOR_NON_POINT_DISABLED == true or environment variable COSMOS_E2E_FOR_NON_POINT_DISABLED == true

API change check
API changes are not detected in this pull request.

/azp run java - cosmos - tests

/azp run java - cosmos - spark

This PR would need a changelog entry.

/azp run java - cosmos - tests

/azp run java - cosmos - spark


refactor(auth, functions, firestore, storage): use ActivityResultLauncher

This PR should update firebase-ui-auth to 7.2.0 in order to use the new ActivityResultLauncher API instead of the deprecated startActivityForResult().

Thanks for this! I love this launcher stuff (although I am still annoyed that they deprecated startActivityForResult)


Add method to create a graph from jumps

This PR makes an attempt to calculate the activation energy graph from the jumps object. I implemented it as a directed graph, but it can easily be collapsed into a undirected graph.
>>> from gemdat import Trajectory, load_known_material
>>> from gemdat.utils import VASPRUN
>>>
>>> trajectory = Trajectory.from_vasprun(VASPRUN)
>>> diff_trajectory = trajectory.filter('Li')
>>>
>>> sites = load_known_material('argyrodite', supercell=(2, 1, 1))
>>>
>>> transitions = trajectory.transitions_between_sites(
>>>     sites=sites,
>>>     floating_specie='Li',
>>> )
>>>
>>> jumps = transitions.jumps()
>>> G = jumps.to_graph()
>>> list(G.adjacency())
[(94, {0: {'e_act': 0.08184877863639753}, 86: {'e_act': 0.17199768720154068}}),
 (0, {94: {'e_act': 0.07200775957630277}, 64: {'e_act': 0.20098168979635483}}),
 (86,
  {94: {'e_act': 0.1676656025734321},
   34: {'e_act': 0.09749500858643947},
   78: {'e_act': 0.20649062422834097}}),
 (2,
  {92: {'e_act': 0.19221497535660828},
   66: {'e_act': 0.13067877194389088},
   58: {'e_act': 0.15338995370169942},
   34: {'e_act': 0.19221497535660828}}),

You can also get the activation energy by site:
>>> jumps.activation_energy_between_sites(2, 92)
0.19221497535660828

to_graph() takes the min and max energy:
>>> G = jumps.to_graph(min_e_act=0.1, max_e_act=5.0)
...

Closes #322

Hi @SCiarella @v9lgraf could you have a look at this PR and let me know if the implementation looks sensible to you? Also happy to take any other feedback you may have 😁


Quick Start Guide: Cordova build bit-tabs content disappearing

So I was going through the quick start guide and discovered a few issues.
In the Desktop and mobile apps > Cordova section, when I build the app, and go to the homepage, when I switch back and forth on the tabs the content disappears.
This does not happen on the web or NW version, just the Cordova iPhone build (I did not check any other mobile build).
It happens on the simulator:

and the actual device:

Also tracked here: https://github.com/donejs/chat/issues/4
I'm wondering if it is this CSS:
bit-panel {
  display: block;
  padding: 10px;

  &:empty {
    display: none;
  }
}

This could be fixed with the change with https://github.com/donejs/chat/commit/7ac1c21344901363dad93b345d3a301489a22d7d and updated in the documentation via https://github.com/donejs/donejs/commit/81b67568e2c3f469695b3f52e38bd83b2f73b686.


What about Testing ???

I cried All the night...
The tests folder was all empty. :((

Sorry ^^

your app was full of lessons... thanks.
but the moment I just clicked on the tests folder to see a bunch of nice tests...
became a drama for me.
Sadly, the tests folder was all empty. :(

Do you what me to create some integration tests on this app ?

Sure, it's an open project.


[SPARK-29961][SQL] Implement builtin function - typeof

What changes were proposed in this pull request?
Add typeof function for Spark to get the underlying type of value.
-- !query 0
select typeof(1)
-- !query 0 schema
struct<typeof(1):string>
-- !query 0 output
int

-- !query 1
select typeof(1.2)
-- !query 1 schema
struct<typeof(1.2):string>
-- !query 1 output
decimal(2,1)

-- !query 2
select typeof(array(1, 2))
-- !query 2 schema
struct<typeof(array(1, 2)):string>
-- !query 2 output
array<int>

-- !query 3
select typeof(a) from (values (1), (2), (3.1)) t(a)
-- !query 3 schema
struct<typeof(a):string>
-- !query 3 output
decimal(11,1)
decimal(11,1)
decimal(11,1)

presto
presto> select typeof(array[1]);
     _col0
----------------
 array(integer)
(1 row)

PostgreSQL
postgres=# select pg_typeof(a) from (values (1), (2), (3.0)) t(a);
 pg_typeof
-----------
 numeric
 numeric
 numeric
(3 rows)

impala
https://issues.apache.org/jira/browse/IMPALA-1597
Why are the changes needed?
a function which is better we have to help us debug, test, develop ...
Does this PR introduce any user-facing change?

add a new function
How was this patch tested?

add ut and example

cc @cloud-fan @dongjoon-hyun @maropu @HyukjinKwon, thanks for reviewing in advance

Test build #114095 has started for PR 26599 at commit fab1c37.

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-K8s/18953/
Test PASSed.

this is a useful feature, thanks for adding!

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-K8s/18961/
Test PASSed.

Test build #114103 has started for PR 26599 at commit 876e122.

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-K8s/18964/
Test PASSed.

Test build #114107 has started for PR 26599 at commit 07a2d35.

Test build #114095 has finished for PR 26599 at commit fab1c37.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class TypeOf(child: Expression) extends UnaryExpression with CodegenFallback

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/114095/
Test PASSed.

Test build #114111 has started for PR 26599 at commit eb2d7e6.

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-K8s/18970/
Test PASSed.

Test build #114103 has finished for PR 26599 at commit 876e122.

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/114103/
Test PASSed.

Test build #114107 has finished for PR 26599 at commit 07a2d35.

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/114107/
Test PASSed.

Test build #114111 has finished for PR 26599 at commit eb2d7e6.

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/114111/
Test PASSed.

How about the case about UserDefinedType? Can you add tests?

How about the case about UserDefinedType? Can you add tests?

Could you suggest a place to put it?  Although I think what I am doing here is just to test the DataType.catalogString

How about UserDefinedTypeSuite?

@yaooqinn . Looks useful! Thanks.

We've marked UDT as interval API, I don't think we need to support it in the end-user function.

Test build #114136 has started for PR 26599 at commit 7acdf39.

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-K8s/18995/
Test PASSed.

Test build #114136 has finished for PR 26599 at commit 7acdf39.

This patch fails due to an unknown error code, -9.
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/114136/
Test FAILed.

We've marked UDT as interval API, I don't think we need to support it in the end-user function.

Yea, I also think we don't need to support it. But, if we don't support it, I think we need to define checkInputDataTypes for typeof. Actually, it seems this pr hits weird exceptions for the type;
scala> sql("select * from t").show()
+---+-------------+
| id|       vector|
+---+-------------+
|  a|[1.0,2.0,3.0]|
|  b|[4.0,5.0,6.0]|
+---+-------------+

scala> sql("select * from t").printSchema
root
 |-- id: string (nullable = true)
 |-- vector: vector (nullable = true)

scala> sql("select typeof(vector) from t").show()
java.lang.ClassCastException: java.lang.String cannot be cast to org.apache.spark.unsafe.types.UTF8String
  at org.apache.spark.sql.catalyst.InternalRow$.$anonfun$getWriter$10(InternalRow.scala:176)
  at org.apache.spark.sql.catalyst.InternalRow$.$anonfun$getWriter$10$adapted(InternalRow.scala:176)
  at org.apache.spark.sql.catalyst.expressions.InterpretedMutableProjection.$anonfun$fieldWriters$2(InterpretedMutableProjection.scala:66)
  at org.apache.spark.sql.catalyst.expressions.InterpretedMutableProjection.$anonfun$fieldWriters$2$adapted(InterpretedMutableProjection.scala:66)
  at org.apache.spark.sql.catalyst.expressions.InterpretedMutableProjection.apply(InterpretedMutableProjection.scala:89)
  at org.apache.spark.sql.catalyst.optimizer.ConvertToLocalRelation$$anonfun$apply$17.$anonfun$applyOrElse$71(Optimizer.scala:1502)
  at scala.collection.TraversableLike.$anonfun$map$1(TraversableLike.scala:238)
  at scala.collection.immutable.List.foreach(List.scala:392)
  at scala.collection.TraversableLike.map(TraversableLike.scal

We've marked UDT as interval API, I don't think we need to support it in the end-user function.

Yea, I also think we don't need to support it. But, if we don't support it, I think we need to define checkInputDataTypes for typeof. Actually, it seems this pr hits weird exceptions for the type;
scala> sql("select * from t").show()
+---+-------------+
| id|       vector|
+---+-------------+
|  a|[1.0,2.0,3.0]|
|  b|[4.0,5.0,6.0]|
+---+-------------+

scala> sql("select * from t").printSchema
root
 |-- id: string (nullable = true)
 |-- vector: vector (nullable = true)

scala> sql("select typeof(vector) from t").show()
java.lang.ClassCastException: java.lang.String cannot be cast to org.apache.spark.unsafe.types.UTF8String
  at org.apache.spark.sql.catalyst.InternalRow$.$anonfun$getWriter$10(InternalRow.scala:176)
  at org.apache.spark.sql.catalyst.InternalRow$.$anonfun$getWriter$10$adapted(InternalRow.scala:176)
  at org.apache.spark.sql.catalyst.expressions.InterpretedMutableProjection.$anonfun$fieldWriters$2(InterpretedMutableProjection.scala:66)
  at org.apache.spark.sql.catalyst.expressions.InterpretedMutableProjection.$anonfun$fieldWriters$2$adapted(InterpretedMutableProjection.scala:66)
  at org.apache.spark.sql.catalyst.expressions.InterpretedMutableProjection.apply(InterpretedMutableProjection.scala:89)
  at org.apache.spark.sql.catalyst.optimizer.ConvertToLocalRelation$$anonfun$apply$17.$anonfun$applyOrElse$71(Optimizer.scala:1502)
  at scala.collection.TraversableLike.$anonfun$map$1(TraversableLike.scala:238)
  at scala.collection.immutable.List.foreach(List.scala:392)
  at scala.collection.TraversableLike.map(TraversableLike.scal

InterpretedMutableProjection

@maropu can you try this with the latest commit? thanks for verifying.

Test build #114156 has started for PR 26599 at commit 54c6cfa.

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-K8s/19012/
Test PASSed.

Can you add some tests for that?

I'm surprised that the tests passed before. returning string should always fail as we need UTF8String

Can you add some tests for that?

done

Test build #114162 has started for PR 26599 at commit 8b96f2c.

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-K8s/19017/
Test PASSed.

Test build #114163 has started for PR 26599 at commit 5759be3.

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-K8s/19018/
Test PASSed.

Test build #114156 has finished for PR 26599 at commit 54c6cfa.

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/114156/
Test PASSed.

Test build #114162 has finished for PR 26599 at commit 8b96f2c.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class VectorUDTSuite extends QueryTest with SharedSparkSession

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/114162/
Test PASSed.

Test build #114163 has finished for PR 26599 at commit 5759be3.

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/114163/
Test PASSed.

Merged to master.


grok() panics on "a|b" pattern when both a and b contain named grok patterns

A community user recently shared a Zed program using grok() that causes zq to panic.
At b9e99c2cdccf74a349aad0326397c05db53a4a00, grok() panics when called with a pattern argument containing a|b where both a and b contain named grok patterns (i.e., %{PATTERN:field_name}).
$ zq 'grok("(%{INT:a}|%{INT:b})", "1")'
panic: runtime error: slice bounds out of range [:-1]
goroutine 1 [running]:
runtime/debug.Stack()
	/opt/homebrew/Cellar/go/1.21.5/libexec/src/runtime/debug/stack.go:24 +0x64
github.com/brimdata/zed/runtime/sam/op.(*Catcher).Pull.func1()
	/Users/noah/brimdata/zed/runtime/sam/op/catcher.go:25 +0x3c
panic({0x103d68880?, 0x140001a80c0?})
	/opt/homebrew/Cellar/go/1.21.5/libexec/src/runtime/panic.go:914 +0x218
github.com/brimdata/zed/pkg/grok.(*Pattern).ParseValues(0x140000dd200, {0x104a01de8, 0x1})
	/Users/noah/brimdata/zed/pkg/grok/grok.go:192 +0x20c
github.com/brimdata/zed/runtime/sam/expr/function.(*Grok).Call(0x140005c1b40, {0x10284d5c4?, 0x10554f2d0?}, {0x140005c1d80?, 0x10554b258?, 0x1051ac5b8?})
	/Users/noah/brimdata/zed/runtime/sam/expr/function/grok.go:45 +0x330
github.com/brimdata/zed/runtime/sam/expr.(*Call).Eval(0x140005c7b30, {0x10554f2d0?, 0x140005c1e00}, {{0x103e2b290?, 0x104b31ac0?}, 0x0?, 0x1400049f8c8?})
	/Users/noah/brimdata/zed/runtime/sam/expr/eval.go:799 +0x130
github.com/brimdata/zed/runtime/sam/op/yield.(*Op).Pull(0x1400065aff0, 0x0?)
	/Users/noah/brimdata/zed/runtime/sam/op/yield/yield.go:31 +0x34c
github.com/brimdata/zed/runtime/sam/op.(*Single).Pull(0x1400061fb90, 0xf8)
	/Users/noah/brimdata/zed/runtime/sam/op/mux.go:134 +0x3c
github.com/brimdata/zed/runtime/sam/op.(*Catcher).Pull(0x8?, 0x10?)
	/Users/noah/brimdata/zed/runtime/sam/op/catcher.go:28 +0x60
github.com/brimdata/zed/runtime/exec.(*Query).Pull(0x1400049fab8?, 0x10?)
	/Users/noah/brimdata/zed/runtime/exec/query.go:59 +0x48
github.com/brimdata/zed/zbuf.CopyPuller({0x10554f198, 0x1400061fa10}, {0x103e251b8, 0x1400065b020})
	/Users/noah/brimdata/zed/zbuf/batch.go:162 +0x54
github.com/brimdata/zed/cli/zq.(*Command).Run(0x14000022a80, {0x140001b8010, 0x1, 0x1})
	/Users/noah/brimdata/zed/cli/zq/command.go:162 +0x5b4
github.com/brimdata/zed/pkg/charm.path.run({0x1400019c338?, 0x1, 0x1}, {0x140001b8010?, 0x1, 0x0?})
	/Users/noah/brimdata/zed/pkg/charm/path.go:11 +0x68
github.com/brimdata/zed/pkg/charm.(*Spec).ExecRoot(0x140000726e8?, {0x140001b8010, 0x1, 0x1})
	/Users/noah/brimdata/zed/pkg/charm/charm.go:63 +0x40
main.main()
	/Users/noah/brimdata/zed/cmd/zq/main.go:11 +0x5c

It looks like this is not unique to a|b patterns (or, at least, the patterns the user can see). I was working on some docs improvements to explain how the "custom pattern" approach should be used instead of the "named capture" syntax that are both shown in Logstash's docs. However, when I tried to run their simple custom pattern example in Zed, I triggered what looks like the same panic shown above.
$ zq -version
Version: v1.12.0-45-gb9e99c2c

$ echo '"Jan  1 06:25:43 mailserver14 postfix/cleanup[21403]: BEF25A72965<EMAIL_ADDRESS>|
zq -z 'yield grok("%{SYSLOGBASE} %{POSTFIX_QUEUEID:queue_id}: %{GREEDYDATA:syslog_message}", this, "POSTFIX_QUEUEID [0-9A-F]{10,11}")' -

panic: runtime error: slice bounds out of range [:-1]
goroutine 1 [running]:
runtime/debug.Stack()
	/usr/local/opt/go/libexec/src/runtime/debug/stack.go:24 +0x5e
github.com/brimdata/zed/runtime/sam/op.(*Catcher).Pull.func1()
	/Users/phil/work/zed/runtime/sam/op/catcher.go:25 +0x3d
panic({0x25466e0?, 0xc0005bc048?})
	/usr/local/opt/go/libexec/src/runtime/panic.go:914 +0x21f
github.com/brimdata/zed/pkg/grok.(*Pattern).ParseValues(0xc000bee690, {0xc0006e6000, 0x82})
	/Users/phil/work/zed/pkg/grok/grok.go:192 +0x238
github.com/brimdata/zed/runtime/sam/expr/function.(*Grok).Call(0xc0003c1380, {0xc00041f870?, 0x100dc5d?}, {0xc00061d560, 0x36d2960?, 0xc000800000?})
	/Users/phil/work/zed/runtime/sam/expr/function/grok.go:45 +0x486
github.com/brimdata/zed/runtime/sam/expr.(*Call).Eval(0xc00061f0e0, {0x4aa39338?, 0xc0003c1640}, {{0x28bd150?, 0x36d2960?}, 0xc000800000?, 0x1011045?})
	/Users/phil/work/zed/runtime/sam/expr/eval.go:799 +0x155
github.com/brimdata/zed/runtime/sam/op/yield.(*Op).Pull(0xc00077e7b0, 0x5?)
	/Users/phil/work/zed/runtime/sam/op/yield/yield.go:31 +0x432
github.com/brimdata/zed/runtime/sam/op.(*Single).Pull(0xc0006928a0, 0x20)
	/Users/phil/work/zed/runtime/sam/op/mux.go:134 +0x2b
github.com/brimdata/zed/runtime/sam/op.(*Catcher).Pull(0x3cb6a68?, 0x50?)
	/Users/phil/work/zed/runtime/sam/op/catcher.go:28 +0x62
github.com/brimdata/zed/runtime/exec.(*Query).Pull(0x4aa39318?, 0xd8?)
	/Users/phil/work/zed/runtime/exec/query.go:59 +0x3e
github.com/brimdata/zed/zbuf.CopyPuller({0x4aa39318, 0xc0006926c0}, {0x28b70a0, 0xc00077e7e0})
	/Users/phil/work/zed/zbuf/batch.go:162 +0x4d
github.com/brimdata/zed/cli/zq.(*Command).Run(0xc0004e2a80, {0xc0000400a0, 0x2, 0x2})
	/Users/phil/work/zed/cli/zq/command.go:162 +0x79e
github.com/brimdata/zed/pkg/charm.path.run({0xc0005a62a8?, 0x1, 0x1}, {0xc0000400a0?, 0x2, 0x0?})
	/Users/phil/work/zed/pkg/charm/path.go:11 +0x79
github.com/brimdata/zed/pkg/charm.(*Spec).ExecRoot(0x100874b?, {0xc000040090, 0x3, 0x3})
	/Users/phil/work/zed/pkg/charm/charm.go:63 +0x3f
main.main()
	/Users/phil/work/zed/cmd/zq/main.go:11 +0x5b

@philrz definitely shouldn't have a panic but in your example %{SYSLOGBASE} doesn't have an associated field tag and this shouldn't be supported.

@mattnibs: I know these kinds of subtleties are always open to debate since Grok lacks a formal specification (sigh!) but I see lack-of-field-name often used for "I want to match against this pattern but I don't need to store it". It does look like our implementation can handle that, such as if I drop the reference to the timestamp field in the example from our docs.
$ zq -version
Version: v1.12.0-46-g828a2dd8

$ echo '"2020-09-16T04:20:42.45+01:00 DEBUG This is a sample debug log message"' |
  zq -Z 'yield grok("%{TIMESTAMP_ISO8601} %{LOGLEVEL:level} %{GREEDYDATA:message}", this)' -

{
    level: "DEBUG",
    message: "This is a sample debug log message"
}

I deleted my prior comment after further investigation.

Verified in Zed commit f50db2d.
The two examples shown above that reproduced the original panic now both work as expected.
$ zq -version
Version: v1.12.0-47-gf50db2df

$ zq 'grok("(%{INT:a}|%{INT:b})", "1")'
{a:"1"}

$ echo '"Jan  1 06:25:43 mailserver14 postfix/cleanup[21403]: BEF25A72965<EMAIL_ADDRESS>|
  zq -Z 'yield grok("%{SYSLOGBASE} %{POSTFIX_QUEUEID:queue_id}: %{GREEDYDATA:syslog_message}", this, "POSTFIX_QUEUEID [0-9A-F]{10,11}")' -
{
    timestamp: "Jan  1 06:25:43",
    logsource: "mailserver14",
    program: "postfix/cleanup",
    pid: "21403",
    queue_id: "BEF25A72965",
    syslog_message<EMAIL_ADDRESS>}

Thanks @mattnibs!


Hi here I attached holiday-calendar from 2012 to 2025 for China, but the question is that it may be a little different with the real holiday cause we don't know the accual date untill The Government announce it.......

Hi here I attached holiday-calendar from 2012 to 2025 for China, but the question is that it may be a little different with the real holiday cause we don't know the accual date untill The Government announce it.......
so  do you think you can use it?
Thank you ~~
Originally posted by @DaisyLL in https://github.com/dr-prodigy/python-holidays/issues/201#issuecomment-501516847

file


PR for the issue #150

This is the pull request for the issue #150.

Oh, sorry.
I removed print.
Thanks,

@ahartoto
I found flake8 warning and modified the code (I removed a blank line.).
If there were no problem, please merge.


run doesn't pass empty arguments

Source
rustup run stable cargo build --verbose --no-default-features --features ""

Expected argument for flag '--features' but reached end of arguments.

This is probably a bug in clap or me not understanding clap. The code is pretty straightforward. values_of("command") is supposed to return multiple arguments but doesn't return the trailing empty argument. cc @kbknapp does this look familiar to you?

"command" is defined as Arg::with_name("command").required(true).multiple(true))

@brson I think that's a docopt error message, or at least it's not one from clap. The error clap would have given in the same scenario (expecting an argument value but not getting one) would be:
$ rustup run stable cargo build --verbose --no-default-features --features
error: The argument '--features <feature>...' requires a value but none was supplied

USAGE:
    fake-rs [FLAGS] --features <feature>...

For more information try --help

I also just tested it with the empty string: --features "" which doesn't give an error. Empty values are allowed by default.
Side note, you can force it to be an error with the Arg::empty_values(false) if that's desired.

@brson Thinking about it, I think it's because those arguments are being passed to cargo, which explains the error message.

Yes it's because the error came from cargo. I'll keep looking into it. Thanks

@brson Ah ok, I misunderstood how it was running, I wasn't thinking the entire stable cargo build --verbose --no-default-features --features "" was being passed. This may in fact be a bug, let me look into it a little deeper I'll get back.

@kbknapp here's a test case https://gist.github.com/brson/2e4a020b220500d9b2d24e4c2faef29c

Thanks! Checking it out now.

Just put in a PR to fix this!

v2.2.4 is on crates.io

\o/ @kbknapp Thanks for the quick update! I'm pulling it in now.


"Wallet loaded, but with errors..."

Creating and loading 2/3 and 3/5 wallets gives me "Wallet loaded, but with errors..." warning, and funds sent to the receive address are not showing as available, despite being confirmed on the blockchain.

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Feature request
[ ] Documentation issue or request
[x] Support request

Expected Behavior
I expected that scanning the QR code for receive address and seeing the transaction with 6+ confirmation on the blockchain should show available funds in the UTXO.
Current Behavior
I created a 3/5 wallet with 5 Trezor One's. Upon creating the wallet, I got a message that read in red text, ""Wallet loaded, but with errors...". I then used 3 of those same Trezors to create a new 2/3 wallet. Same message. To test these wallets out, I sent some bitcoin to each of the wallets by scanning the QR code in the "Receive" tab. Both transactions to the 2/3 and 3/5 wallet confirmed from the sender side, but I don't see any funds in either wallet.
I checked the blockchain and see that the funds were sent to the correct address, which is still listed as the first address in the wallet. However, the address shows zero funds available. The transaction was sent from a Blue Wallet wallet which is connected to my own node. This was several days ago.
The configuration I used was P2SH/Mainnet/Public/Default. I also downloaded the wallet configuration for each wallet, reloaded the wallets, and the error persisted, plus no funds available.
Steps to Reproduce (for bugs)
Screenshot: https://www.screencast.com/t/u7AIErRyMlOq

Where are you running caravan:   unchained-capital.github.io
Operating system:  Mac
Browser and version:  Chrome

Hmm ... that's odd. So just to confirm - the address shown has a balance on a block explorer but it's not showing up in caravan using the "Public" node option, correct?
Are you using standard/default BIP32 paths?
The error message seems to suggest that the public node is not behaving properly. E.g. there are errors when trying to fetch UTXOs for a particular address from the node.

Your brainstorming helped fix it, so thank you!
Even though Caravan was not connected to my private node during the wallet creation process, I was running the Caravan Multisig Tool on MyNode. Once I disabled that and reloaded the wallet configuration, the funds now appear normally, and the wallets load without the error message.
I guess the error was that I created the wallet with a public node, but it was attempting to connect to my private node.
I hope documenting this helps someone in the future solve a similar problem.

Awesome.
If you get the connection to your private node working, you may need to "Import Addresses" before it loads correctly in Caravan, but good to hear you're all set.
I'm going to close this issue.
Cheers


Disable splaying

I'm migrating from version 2.3.0 to the latest version, 5.0.0-dev1 and I'm facing issues from changes made in version 3.
I've previously implemented my own UI for lots of markers placed exactly onto each other. I'd like to keep that, but the ClusterSplayDelegate seems required by SuperclusterLayer and I couldn't find a way to disable it or force it to display just the underlying markers without interfering with the marker tap function.
Am I missing something?

Hey @JFtechOfficial, I don't have a good answer for you as I'm not working on this actively at the moment due to work commitments. I'm open to PRs but apart from that I don't have much time available to maintain this currently.


[CHANGE] on web documents

<IP_ADDRESS> Departments must provide an accessible version of any non-web documents when requested.
https://a11y.canada.ca/en/standards/standard/#<IP_ADDRESS>
This needs to clearly be listed as an exception. You just can't allow non-web documents to be delivered that aren't accessible, unless it is exceptional. Lots of non-web documents can be made more accessible.
Specifically with PDFs, the government needs to stop the bleeding. Every new PDF is future technical debt. Yes, you can technically make them accessible, but this is hard and limited in many ways. It is just too easy to produce inaccessible PDFs and too hard to determine if they are reasonably accessible.
PDFs are encapsulated paper documents and are not digital native. https://gds.blog.gov.uk/2018/07/16/why-gov-uk-content-should-be-published-in-html-and-not-pdf/

That article is new-to-me, thanks Mike!
Strong +1 (from painful experience) that phrasing similar to "accessible versions provided upon request" is a red flag, especially for anything recent and/or public facing.  As a checkbox option while registering for an in-person event, fine.  As a proactive attempt at indemnification?  It may have the opposite effect!
Accessibility of born digital content in U.S. .gov space is also a work in progress.

@mgifford should the subject line read non-web?


Terminology for "All" and "Subset" need to be consistent

Update label in birds eye view to All and Subset
More details...
On the browse & subset tab, legend for histograms is All entity vs Subset of entity

Update birds eye verbiage to match. It should be All vs Subset in the plot itself as well as in the headers mouseover text (note mouseover verbiage is fine as is)

Checked language over a few different studies and different types of visualizations and I can confirm the changes have been made. Mouseover text is also correct

thank you for your review and tests @sweverschulman 👍


Update unofficial-ring-connect.groovy

add support for Spotlight Cam Plus (cocoa_spotlight)

I had to add this to my local copy of the app code for the app to recognize my Spotlight Cam Plus device in discovery.

Fixed in a1a705605b5


Minor fixes.

This was intended to be related to tappedout stuff, but I ended up fixing core things in the process.


Changed CS-PUI link in cer.js

Changed the link to point to the homepage with all job listings (https://cs-pui.github.io/). Previously, it was pointed to guidance for posting a listing (https://cs-pui.github.io/guide). Thanks for including the link!

Thanks for the update! This is live.


AssertionError when i try to move model to direct ml

I cant move model to direct ml but it works with cpu
since this works fine with cpu i assume this is a direct ml issue but i could be wrong
maybe im just doing something wrong here and if thats the case any help would be appreciated
im using torch-directml 0.2.4.dev240815
code that doesnt work :(
import torch
import torch_directml
dml = torch_directml.device()

device = dml

model = torch.hub.load(repo_or_dir="miccunifi/ARNIQA", source="github", model="ARNIQA",
                       regressor_dataset="kadid10k")    # You can choose any of the available datasets
model.eval().to(device)

outputs:
File "C:\Users\AppData\Local\Programs\Python\Python311\Lib\site-packages\torch\nn\modules\module.py", line 830, in _apply
assert isinstance(param, Parameter)
AssertionError

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

I'm having the same issue, is there any new progress?


Fix: url hash not preserved after page reload

Fixes #104

Thanks! Should browser.getHash() only be added when starting (transitioning to the first step)? If you load a new page /route1#part-1, and then navigate to /route2, the browser's URL would change to /router2#part-1 rather than /route2?

Is it enough to check if fromState is null? Or I missed your point?

@troch, could you merge, please?

Yep, sorry for the delay. Like #143, can you put this behaviour behind an option? Name it preserveHash, default to false for now, so current usage is not impacted. Reason for this is I'm not ready to bump a major version now (I'm in the process of refactoring the repo to host all packages, so major version bumps are made easier).

Thanks!


Prepare for an external start page

This updates the first page of the claim to be a new action, rather than a create action, which then starts the claim process. This means that the start of the journey will be able to be linked to from a GOV.UK start page.
The bulk of the lines of code in this PR are test changes, I've endeavoured to tidy up the tests a bit by adding a Request helper that means we're not always repeating ourselves when we're POSTing to create a Claim. This will also make things easier to change if / when we change the journey in any way.

 Prepare for an external start page


Gave up support for Python 3.6

I could not install Python 3.6 on CI environment (Ubuntu 22.04)
py_nullable depends on typing_extensions since v0.3

If you want to use it in 3.6, please fork and modify it.


NewRelic agent: Failed to extract source code context from callable

Description
I added newrelic apm to a tornado based application. The agent is outputting a lot of error messages: newrelic.api.time_trace ERROR - Failed to extract source code context from callable <address.to.request.handler.here>. Report this issue to newrelic support.
Is this something in our code?
Expected Behavior
No error messages and expected to see transactions in the APM.
Steps to Reproduce

install newrelic==<IP_ADDRESS>
wrap python main.py execution in newrelic-admin run-python path/to/code

Your Environment
Python 3.9.2
NewRelic <IP_ADDRESS>
Tornado 6.1.0

Hello! This is an issue in a new feature we've just added in this version. If you're seeing that log message, your application should be safely recovering from the issue and there shouldn't be any crashes related to it. (If there are, definitely let us know.)
Could you tell us a bit about the callable this error message is referencing? We'd like to figure out what's not functioning as expected and get that data reporting. Specifically in the logs where you've redacted it to say: <address.to.request.handler.here>
Is that piece of code a function, a functools.partial, a callable object, a classmethod, etc?
If the log messages are bothering you and you'd like to temporarily disable the new feature you can use this setting to temporarily disable it.

What we have is a class, a request handler, that is decorated with a function that returns a configured handler, with changed type.
From the error message, it looks like the part that causes the failure in the agent is the decorator.
Basically this part, see example code, specifically this:
app = Application([
    (r'/user/(.*)', ProfileHandler, dict(database=database)),
    ])

Let's say you have:
@configure_handler(configs=some_configs_obj)
class SomeHandler(RequestHandler):
    ...

and configure_handler is something like this:
def configure_handler(config: GenericHandlerConfig) \
        -> Callable[[GenericHandlerClassType], GenericHandlerClassType]:
    def inner_configure(cls: GenericHandlerClassType) -> GenericHandlerClassType:
        return type("GenericHandler_configured", (cls,), dict(_is_debug=config.is_debug))
    return inner_configure

And the error in the agent is for "GenericHandler_configured".
Hope this helps.

We have a fix coming for this!


chore: release main

:robot: I have created a release beep boop
interop: 3.0.1
3.0.1 (2024-01-16)
Bug Fixes

update type import path (#379) (ece384a)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/ipfs/helia/releases/tag/interop-v3.0.1 :sunflower:


feat: Some feedback dataset improvements

Description
The main improvements that this PR brings are:

Feedback dataset class method unification: All expected methods are defined in the base class, so they must be available for each dataset implementation. For those cases where the method has less sense or is not implemented yet, the user will be notified with a warning (@davidberenstein1957 review and improve, please)
More general workflow with response unification: The unification workflow support dataset connected to Argilla. This means that the prepare_for_training can be applied with remote datasets. The unify_responses returns a dataset where responses are unified. As a common practice, returning data is preferable to modifying values internally. We can avoid weird side effects. So, the unification workflow should be as:

from argilla import MultiLabelQuestionStrategy, FeedbackDataset

dataset = FeedbackDataset.from_argilla(name="my-dataset")
strategy = MultiLabelQuestionStrategy("majority") # "disagreement", "majority_weighted (WIP)"

unified_dataset = dataset.unify_responses(
    question=dataset.question_by_name("tags"),
    strategy=strategy,
)

unified_dataset...

Type of change
(Please delete options that are not relevant. Remember to title the PR according to the type of change)

[X] Refactor (change restructuring the codebase without changing functionality)
[X] Improvement (change adding some improvement to an existing functionality)

How Has This Been Tested
(Please describe the tests that you ran to verify your changes. And ideally, reference tests)
Some of those flows have been tests locally
Checklist

[ ] I added relevant documentation
[x] I followed the style guidelines of this project
[x] I did a self-review of my code
[ ] I made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[ ] I filled out the contributor form (see text above)
[x] I have added relevant notes to the CHANGELOG.md file (See https://keepachangelog.com/)

@frascuchon can you give this a final lookover?


The follow button displays on my own page (in 2 spots)

Same with the message button

Nevermind


MWPW-137347 Analytics test for resources pages

Analytics impression is controlled by the server side. Currently DC resources pages behave randomly in tracking impressions. Therefore, this test is not stable.
Merge the test first, and then will work with the analytics team to find a solution

To run the test case:
npx run test/e2e/frictionless -t @MWPW-137347 --enableAnalytics

Codecov Report

Merging #396 (28c36f2) into stage (d5f016f) will decrease coverage by 0.04%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##            stage     #396      +/-   ##
==========================================
- Coverage   93.53%   93.49%   -0.04%
==========================================
  Files          26       26
  Lines        2969     2969
==========================================
- Hits         2777     2776       -1
- Misses        192      193       +1

see 1 file with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Add AF_UNSPEC from Apple socket.h

socket.h of Apple contains this definition so i'm not sure why it is missing from libc.
The same goes for other BSD-like OSes...
Is there some particular reasons why it is so?

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @alexcrichton (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

@bors: r+

:pushpin: Commit 45ba8c1 has been approved by alexcrichton

:hourglass: Testing commit 45ba8c1 with merge 6813109...

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing 6813109faeb0d0b548b05598d207ddfff237098f to master...


Controller does not validate updated subnet size

This is based on an inspection of the code so I could be mistaken.  However, as far as I can tell controller does not validate the tenant subnet size when processing a tenant update command.  Ciao-cli does perform some validation so it's hard to actually exploit this.  Nonetheless, it should be possible to construct a json package with invalid data which would potentially destabilize controller.  Note the subnet size is verified by controller when creating a new tenant.

So we check here when creating a tenant
https://github.com/ciao-project/ciao/blob/master/ciao-controller/tenants.go#L82
but not here when updating one
https://github.com/ciao-project/ciao/blob/master/ciao-controller/tenants.go#L69


expand doc page width

remove docs right side bar and expand main content area

@antoninbas ready for review, commit signed and fixed the oddness for antctl page


URGENT!!! I am able to edit the wiki pages on bluek8s. Please remove access

We managed to save changes on any wiki page in bluek8s/kubedirector. Please remove access.

Done. Thanks for the alert


why does sess.run()so slow on android?

I used retrain.py to retrain inception_v3 with my own images.It works will on pc with label_image.cc.It costs about 2-4s on android demo(just change the graph.pb) once sess.run().In original demo,it costs only 400ms?whats wase,the result always get wrong.I have no idea,why it works so slow?why the accuracy so low on android device?

Sorry you're hitting problems! There are various changes you need to make to successfully run the Inception v3 model in the Android demo, including altering the mean and std values that the input images are scaled by. We don't have an example of this yet, but we'll track it in this bug.

trying to build label_image:main.cc on Android...


YETUS-785. Download page must not link to dist.apache.org.

JIRA: https://issues.apache.org/jira/browse/YETUS-785

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
112
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

_ master Compile Tests _

_ Patch Compile Tests _

+1
whitespace
0
The patch has no whitespace issues.

_ Other Tests _

+1
asflicense
11
The patch does not generate ASF License warnings.

140

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/yetus-github-multibranch/job/PR-45/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/yetus/pull/45

Optional Tests
dupname asflicense

uname
Linux 24dbe7ed3306 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
precommit/src/main/shell/personality/yetus.sh

git revision
master / 99a6c86

maven
version: Apache Maven 3.3.9

Max. process+thread count
47 (vs. ulimit of 2000)

modules
C: asf-site-src U: asf-site-src

Console output
https://builds.apache.org/job/yetus-github-multibranch/job/PR-45/1/console

Powered by
Apache Yetus 0.10.0-SNAPSHOT http://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
128
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

_ master Compile Tests _

_ Patch Compile Tests _

+1
whitespace
0
The patch has no whitespace issues.

_ Other Tests _

+1
asflicense
9
The patch does not generate ASF License warnings.

154

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/yetus-github-multibranch/job/PR-45/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/yetus/pull/45

Optional Tests
dupname asflicense

uname
Linux 34472852ecd6 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
precommit/src/main/shell/personality/yetus.sh

git revision
master / ee8cebc

maven
version: Apache Maven 3.3.9

Max. process+thread count
51 (vs. ulimit of 2000)

modules
C: asf-site-src U: asf-site-src

Console output
https://builds.apache.org/job/yetus-github-multibranch/job/PR-45/2/console

Powered by
Apache Yetus 0.10.0-SNAPSHOT http://yetus.apache.org

This message was automatically generated.

Committed. Thanks @busbey !


Update event management

Today, the events are stored in a map (with the id of the key and the state) into the encapsulation of the graphic lib.
Many changes are needed:

Store the map in the game instead of the graphic lib (the code of the key needs to be unknown for the game, as only the graphic lib needs to understand this code)

Add a new type of key (ONE_TIME or PRESSED), this type will determine if the event handler needs to check for a one time pressed key or a pressing key. This type is useful for the shot for example (in order to avoid long pressed key and so multiple shots)

Rename the event component from Keyboard to Event

good part, this is a important task,
the graphic need to be abstract
i advise you to create one or 2 interface to unified the graphic game interaction

No needs to add the input type of the key we can handle it with systems


Rewarding/ allocating a defined % of unruggable memecoin to addresses that meet specific criteria

Bootstrap your meme community by rewarding ecosystem participants with a defined % of the overall unruggable memecoin allocation.
This idea lets you onboard addresses and bring attention to your unruggable memecoin. At their core, memecoins are about attention. Without attention, no one will trade, or be interested in your unruggable memecoin, as there's no intrinsic value.
What criteria do we use to define allocation?
When creating an unruggable memecoin, a % of the unruggable memecoin can be allocated on historical behaviours, such as: made a specific number of transactions, account value, interacting with specific dapps, account age, transaction volume, or owning a specific NFT.
These seem the most obvious and can be adjusted based on who to target. Not all these criteria have to be set for the unruggable memecoin. It can be as simple as allocating 50% of the supply to addresses that have more than $100 in their address at the time of the unruggable memecoins creation, and every address that meets the criteria receives the same amount of unruggable memecoin.
Other examples include:

Rewarding a % of the unruggable memecoin to addresses that hold a specific NFT. In this example, the maximum number of eligible addresses is known, so the amount that can be airdropped/ claimed by eligible addresses is known
Rewarding DeFi power users through account age, transaction volume, dapps used and min wallet balance. In this example, the rewarding/allocation is more targeted to appeal to specific addresses. The amount being rewarding/ allocating can be variable.

What about the claiming process?
The method behind distribution can either be via a direct airdrop which will require gas for the unruggable memecoin creator(s) to distribute tokens, or via a claiming process, akin to typical airdrops, where addresses that meet the criteria can claim their allocation by a specific date. TBD.
Unclaimed tokens can then either be burnt or added to bolster liquidity.
The benefits of rewarding/ allocating a defined % of unruggable memecoin to addresses that meet specific criteria
As memecoins are all about attention, this achieves that from the onset.

Interested addresses will claim the airdrop
Addresses will either: hold, sell, trade or LP airdrop
More activity results in higher volume
The more volume means more fees for LPs
Attractive fees bring deeper liquidity
Deeper liquidity results in a better trading experience and price action
The flywheel repeats

This is not a new idea. BONK airdropped 50% of the total supply to members of the Solana ecosystem based on defined criteria and has since become the defacto memecoin of the Solana community.

Hey @abdelhamidbakhta @EdwardCWilson, I would love to work on that!

Hey @abdelhamidbakhta @EdwardCWilson, I would love to work on that!

Great, assigned to you

Hey Abdel, thank you very much! On which criteria should I work? What do you think could be the best claiming process?


update swift-format to 0.45.6

motivation: swift-format is broken on 5.3
changes: update to 0.45.6 that is compatible with 5.3

@tomerd Why has this been closed?

@fabianfett its not really helping with the 5.3 issue. I am waiting for 5.3 nighties to be available to see if this is an issue on master - which is what we are using on 5.2 CI rn
cc @mishalsha


syscall: incorrect value for TCGETS and TCSETS in std syscall pkg on ppc64x

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
go 1.8, master
What operating system and processor architecture are you using (go env)?
Ubuntu and RH ppc64le and ppc64
What did you do?
Tried to use ioctl syscall with TCGETS on ppc64le.
What did you expect to see?
Valid result.
What did you see instead?
Error message: inappropriate ioctl for device
This error occurs when using the syscall package but works when using golang.org/x/sys/unix due to the fact that these two packages define different values for TCGETS and TCSETS:
In golang syscall package, ztypes_linux_ppc64le.go and ztypes_linux_ppc64.go:
    TCGETS = 0x403c7413
    TCSETS = 0x803c7414

In golang.org/sys/unix/zerrors_linux_ppc64le.go and zerrors_linux_ppc64.go
TCGETS                           = 0x402c7413
TCSETS                           = 0x802c7414
I see there is a comment in the golang.org documentation about the use of the syscall package being "locked down".  My assumption is that the syscall package should be fixed since it is now incorrect.
Testcase:
ioctlbug.go.txt
Failing execution:
Error on get: inappropriate ioctl for device
importing from golang.org/x/sys/unix allows the test to work.

This was found as a result of investigating https://github.com/opencontainers/runc/issues/1364

@bradfitz Who can answer questions about this issue?
Is the answer supposed to be that users should be using golang.org/x/sys/unix instead of syscall from golang std?
Personally I think that the syscall package in golang should be correct.  But it is not clear to me how to get the correct value generated from the sh and pl files that are used to create them, and why the one in golang.org/x is correct but the other is not.

Why is std incorrect? Have these values changed over time? If so, that suggests even more that the answer is using x/sys/unix and not trying to keep syscall up to date.
But yes, the real answer is that everybody should use x/sys and pretend that the std package "syscall" doesn't exist.

I'll slightly disagree with @bradfitz and say that if the values in the syscall package were always wrong, then I think it would be OK to correct them.  It looks like they were introduced by @minux in https://golang.org/cl/127170043, where he says they were autogenerated.  Minux, do you know anything about these values?

Yeah, if they were always wrong and they by definition never change and it's just a result of a bug in our generator program, I'm fine changing it. But that does mean that users will need to wait for a new version of Go for the fix, whereas if runc used golang.org/x/sys/unix, they'd have the fix already.

It looks like this problem was identified here https://groups.google.com/forum/#!msg/golang-nuts/K5NoG8slez0/mixUse17iaMJ and fixed some time after that in golang.org/x/sys/unix.
This explains why syscall and golang.org/x/sys/unix are different.  And just fixing one value in syscall might not be enough -- when other ioctl functions are used they could be wrong also.

So it looks like they were always wrong, and it would be good to fix this since so many projects do still syscall. I see that the rec is definitely to move (https://groups.google.com/forum/#!topic/golang-dev/cEASnHIXmLI), but at least the container-focused projects haven't yet.
@bradfitz, I did a quick substitution of syscall for sys in parts of the runc code, and it looks like there are some things missing from sys like Signal. Actually, it looks like syscall.Signal is used by sys, so, there's no clean break from syscall. Is this something I should take up on the mailing list if I want to get advice on moving over? It seems strange to mix the two.

I can't think of a reason for golang.org/x/sys/unix to use syscall.Signal.  Perhaps we should just replace it.  Anyhow, yes, raise this on golang-dev.  Thanks.

I've been trying to understand how sys/unix could be fixed, but I can't get the generator scripts to work.  Here are the errors I get when I run this:
GOOS=linux GOARCH=ppc64le ./mkall.sh
could not determine kind of name for C.TIOCGETC
could not determine kind of name for C.TIOCGETP
could not determine kind of name for C.TIOCGLTC
could not determine kind of name for C.TIOCSETC
could not determine kind of name for C.TIOCSETN
could not determine kind of name for C.TIOCSETP
could not determine kind of name for C.TIOCSLTC

What do the definitions for those symbols look like in the header files on your system?

@ianlancetaylor  Sorry somehow I missed your previous question.
The errors above occur because these values are defined in terms of the _IOR macro and the set of header files as they are now don't provide the definition of that before it is used AFAICT.
What we have discovered is that on some platforms these are defined in asm/termios.h but on others it is in asm/termbits.h.  So when files are changed to use the right header files for ppc64x, that results in many other changes in the zppc64.go files as well as other platforms I'm sure.
Something like this seems to make it work by changing mkerrors.sh, as well as a change with the same effect in linux_types.go:
+if [[ "$GOARCH" == "ppc64" || "$GOARCH" == "ppc64le" ]]; then

includes_Linux+='
+#include <asm/termios.h>
+'
+else
includes_Linux+='
+#include <sys/ioctl.h>
+#include <sys/mount.h>
+#include <asm/termbits.h>
+'
+fi


For applicability, IIDs must be recognizable as an IID, simply by examining its syntax -- Is this true?

The text refers to an IID as having equivalent sytnax to a DID. So how can one distinguish between them from the IID?

Good question. This is also something that still confuses me a bit. What is the key difference between an IID and DID:EARTH. From my discussions with Shaun and Joe it seems that IID is merely a type of implementation for the DID:EARTH method.
Maybe @jandrieu or @ig-shaun can provide more clarity on this.


#270 - Import package.json as default module

Import package.json as default module rather than named exports
Resolves #270

 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.


Google Cloud Bucket: Sorry, the server was not able to fulfil your request.

I'm trying to access the data via the Google Cloud Bucket links provided on the website. I have registered with my Google account at least 4-5 days ago and am logged in with the same account while accessing the link, however I cannot access the files, and the following error message is shown.

This happens with all of the 6 links of the 3 versions.

Thanks for your question. We will look into this. What is the email address that you used to register?

Thanks for your question. We will look into this. What is the email address that you used to register?

I've tried a different address now as well without success. I can PM the addresses to someone if necessary.

I've tried a different address now as well without success. I can PM the addresses to someone if necessary.

Hi, feel free to email the address to<EMAIL_ADDRESS>

Hi, feel free to email the address to<EMAIL_ADDRESS>

same issue for me. sent an email as well.

In my case this was caused because I registered without filling the optional fields, which seemed to work because I got access to the links, but only when I filled the optional fields as well I got a confirmation mail and (after a processing delay of a day or so) access to the bucket. Maybe this helps you as well @dschoerk, otherwise you can reopen this.

In my case this was caused because I registered without filling the optional fields, which seemed to work because I got access to the links, but only when I filled the optional fields as well I got a confirmation mail and (after a processing delay of a day or so) access to the bucket. Maybe this helps you as well @dschoerk, otherwise you can reopen this.

thanks! somehow the fields didn't show up at first for me. after switching to a different browser where i wasnt logged in before they showed up.

Which optional fields? I also cannot get access and see only 4 fields (all required), no e-mail sent. Tested on multiple browsers. I only tried an hour ago though, so maybe just delay.

Yes, it seems like they changed it. Should be 4 fields as you said

Hi all, this is just to confirm that all 4 fields in the licensing terms are required, and you should not be running into the issue that ptoews experienced.
If your registration is successful, you should receive a confirmation email from Waymo shortly and have access to the bucket. If you received the registration confirmation email, but do not have access to the bucket, please reach out to<EMAIL_ADDRESS>