[SUPPORT]

hive (app)> SELECT
> projectid,
> provinceid,
> typeId,
> antistop
> FROM
> app.dwd_recommend_tender_ds
> WHERE
> createTime >=<PHONE_NUMBER>479
> AND antistop != '' limit 2;
OK
projectid       provinceid      typeid  antistop
7876350 150000  9       装修#扩建
7876350 150000  9       装修#扩建
Time taken: 0.133 seconds, Fetched: 2 row(s)
it is work !
but !
hive (app)> select count(1) as total from app.dwd_recommend_tender_ds;
Query ID = root_20210126113448_acb65504-b31b-4309-9d65-39c48743326e
Total jobs = 1
Launching Job 1 out of 1
Tez session was closed. Reopening...
Session re-established.
    VERTICES      MODE        STATUS  TOTAL  COMPLETED  RUNNING  PENDING  FAILED  KILLED

Map 1            container  INITIALIZING     -1          0        0       -1       0       0
Reducer 2        container        INITED      1          0        0        1       0       0
VERTICES: 00/02  [>>--------------------------] 0%    ELAPSED TIME: 0.55 s
Status: Failed
Vertex failed, vertexName=Map 1, vertexId=vertex_1611208773582_0084_1_00, diagnostics=[Vertex vertex_1611208773582_0084_1_00 [Map 1] killed/failed due to:ROOT_INPUT_INIT_FAILURE, Vertex Input: dwd_recommend_tender_ds initializer failed, vertex=vertex_1611208773582_0084_1_00 [Map 1], java.lang.NoSuchMethodError: org.apache.hudi.common.table.timeline.HoodieActiveTimeline.getCommitsTimeline()Lorg/apache/hudi/common/table/HoodieTimeline;
at org.apache.hudi.hadoop.HoodieParquetInputFormat.filterFileStatusForSnapshotMode(HoodieParquetInputFormat.java:238)
at org.apache.hudi.hadoop.HoodieParquetInputFormat.listStatus(HoodieParquetInputFormat.java:110)
at org.apache.hadoop.mapred.FileInputFormat.getSplits(FileInputFormat.java:315)
at org.apache.hadoop.hive.ql.io.HiveInputFormat.addSplitsForGroup(HiveInputFormat.java:442)
at org.apache.hadoop.hive.ql.io.HiveInputFormat.getSplits(HiveInputFormat.java:561)
at org.apache.hadoop.hive.ql.exec.tez.HiveSplitGenerator.initialize(HiveSplitGenerator.java:196)
at org.apache.tez.dag.app.dag.RootInputInitializerManager$InputInitializerCallable$1.run(RootInputInitializerManager.java:278)
at org.apache.tez.dag.app.dag.RootInputInitializerManager$InputInitializerCallable$1.run(RootInputInitializerManager.java:269)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1844)
at org.apache.tez.dag.app.dag.RootInputInitializerManager$InputInitializerCallable.call(RootInputInitializerManager.java:269)
at org.apache.tez.dag.app.dag.RootInputInitializerManager$InputInitializerCallable.call(RootInputInitializerManager.java:253)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
]
Vertex killed, vertexName=Reducer 2, vertexId=vertex_1611208773582_0084_1_01, diagnostics=[Vertex received Kill in INITED state., Vertex vertex_1611208773582_0084_1_01 [Reducer 2] killed/failed due to:OTHER_VERTEX_FAILURE]
DAG did not succeed due to VERTEX_FAILURE. failedVertices:1 killedVertices:1
FAILED: Execution Error, return code 2 from org.apache.hadoop.hive.ql.exec.tez.TezTask. Vertex failed, vertexName=Map 1, vertexId=vertex_1611208773582_0084_1_00, diagnostics=[Vertex vertex_1611208773582_0084_1_00 [Map 1] killed/failed due to:ROOT_INPUT_INIT_FAILURE, Vertex Input: dwd_recommend_tender_ds initializer failed, vertex=vertex_1611208773582_0084_1_00 [Map 1], java.lang.NoSuchMethodError: org.apache.hudi.common.table.timeline.HoodieActiveTimeline.getCommitsTimeline()Lorg/apache/hudi/common/table/HoodieTimeline;
at org.apache.hudi.hadoop.HoodieParquetInputFormat.filterFileStatusForSnapshotMode(HoodieParquetInputFormat.java:238)
at org.apache.hudi.hadoop.HoodieParquetInputFormat.listStatus(HoodieParquetInputFormat.java:110)
at org.apache.hadoop.mapred.FileInputFormat.getSplits(FileInputFormat.java:315)
at org.apache.hadoop.hive.ql.io.HiveInputFormat.addSplitsForGroup(HiveInputFormat.java:442)
at org.apache.hadoop.hive.ql.io.HiveInputFormat.getSplits(HiveInputFormat.java:561)
at org.apache.hadoop.hive.ql.exec.tez.HiveSplitGenerator.initialize(HiveSplitGenerator.java:196)
at org.apache.tez.dag.app.dag.RootInputInitializerManager$InputInitializerCallable$1.run(RootInputInitializerManager.java:278)
at org.apache.tez.dag.app.dag.RootInputInitializerManager$InputInitializerCallable$1.run(RootInputInitializerManager.java:269)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1844)
at org.apache.tez.dag.app.dag.RootInputInitializerManager$InputInitializerCallable.call(RootInputInitializerManager.java:269)
at org.apache.tez.dag.app.dag.RootInputInitializerManager$InputInitializerCallable.call(RootInputInitializerManager.java:253)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
]Vertex killed, vertexName=Reducer 2, vertexId=vertex_1611208773582_0084_1_01, diagnostics=[Vertex received Kill in INITED state., Vertex vertex_1611208773582_0084_1_01 [Reducer 2] killed/failed due to:OTHER_VERTEX_FAILURE]DAG did not succeed due to VERTEX_FAILURE. failedVertices:1 killedVertices:1
hive (app)>

It looks like you may be having multiple hudi bundles (or multiple versions) in the classpath of execution. Can you check if this is the case ?

It looks like you may be having multiple hudi bundles (or multiple versions) in the classpath of execution. Can you check if this is the case ?

think you发自我的华为手机-------- 原始邮件 --------主题：Re: [apache/hudi] [SUPPORT] (#2489)发件人：Balaji Varadarajan 收件人：apache/hudi 抄送：李仕辉 ,Author
It looks like you may be having multiple hudi bundles (or multiple versions) in the classpath of execution. Can you check if this is the case ?
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/apache/hudi/issues/2489#issuecomment-767390678",
"url": "https://github.com/apache/hudi/issues/2489#issuecomment-767390678",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]

think you发自我的华为手机-------- 原始邮件 --------主题：Re: [apache/hudi] [SUPPORT] (#2489)发件人：Balaji Varadarajan 收件人：apache/hudi 抄送：李仕辉 ,Author
It looks like you may be having multiple hudi bundles (or multiple versions) in the classpath of execution. Can you check if this is the case ?
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/apache/hudi/issues/2489#issuecomment-767390678",
"url": "https://github.com/apache/hudi/issues/2489#issuecomment-767390678",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]

@Ishg Do you have any update ?

gentle ping for response.

@ishg Since we haven't heard from you in over a month, closing this ticket. Please re-open if your issue is unresolved.

Just FYI this isn't me. The OP is @lshg (with a L, not I) 😄


Create an initial AWSX/Crosswalk User Guide

I rebased these changes against the latest in master and fixed things up for Hugo in the following branch: https://github.com/pulumi/docs/tree/joeduffy/1071_awsx_user_guide-hugo

Thank you, Justin!

Superseded by https://github.com/pulumi/docs/pull/1136.


LOD meshes attached to wrong bone on export

Broken since 2.0. Steps to reproduce:

Import prop_streetlight_01.yft

Prop_StreetLight_01 bone has 3 LODs, while Bulb_Glass only 1.

Export

Import exported XML.

Now Prop_StreetLight_01 bone has only 1 LOD, while Bulb_Glass has its high LOD + the 2 LODs previously attached to Prop_StreetLight_01.

And the LOD meshes are now incorrectly placed. Which is visible in-game as well.

This seems to actually be an issue with import.
If you export it a first time and try it in-game, the models are placed correctly. Once you import the exported model and export again, the models are placed incorrectly in-game, because Sollumz already placed them incorrectly on import.


Add conda package via conda-forge

The missing dependency is fixed, but this is hung up on a weird dependency situation with testing where we'd originally listed wget as a dependency, but that's an old Python package, not the actual dependency. This is fixed now, but we need a new PyPI release before officially submitting to conda-forge.
Draft PR to conda-forge is here https://github.com/conda-forge/staged-recipes/pull/22409


[Mention The Feature]:  Testimonial Section

Is your feature request related to a problem? Please describe.
A separate testimonial section could be effectively placed above the footer.
Describe the solution you'd like.
No response
Describe alternatives you've considered.
No response
Additional context.
No response
Show us the magic with screenshots
No response
Checklist

[X] I have checked the Existing Issues
[X] I have read the Contributing Guidelines
[X] I want to work on this issue. (optional)

@AasthaSingh28 sure go ahead
Make sure to join the discord server for further communication
Don't forget to star the repository
Complete the task in next 2 days and kindly mention your issue # in your pr like this:
Closes #IssueNumber
Note: the level of the issue may change based on the quality of the PR code


babel-prest-env error when running webpack scripts

Me again : )
Just picked up a new project and trying to run npm run webpack and getting the following.
Have tried installing the package, updating NPM, and a few other things but can't get it to go away.
ERROR in ./src/scripts/index.js
Module build failed: Error: Cannot find module 'babel-preset-env' from '/Users/philipjohnson/projects'
    at Function.module.exports [as sync] (/Users/philipjohnson/projects/vue-shopify/node_modules/resolve/lib/sync.js:40:15)
    at resolveStandardizedName (/Users/philipjohnson/projects/vue-shopify/node_modules/@babel/core/lib/config/files/plugins.js:78:29)
    at resolvePreset (/Users/philipjohnson/projects/vue-shopify/node_modules/@babel/core/lib/config/files/plugins.js:31:10)
    at loadPreset (/Users/philipjohnson/projects/vue-shopify/node_modules/@babel/core/lib/config/files/plugins.js:50:18)
    at createDescriptor (/Users/philipjohnson/projects/vue-shopify/node_modules/@babel/core/lib/config/config-descriptors.js:135:21)
    at /Users/philipjohnson/projects/vue-shopify/node_modules/@babel/core/lib/config/config-descriptors.js:101:12
    at Array.map (<anonymous>)
    at createDescriptors (/Users/philipjohnson/projects/vue-shopify/node_modules/@babel/core/lib/config/config-descriptors.js:100:27)
    at createPresetDescriptors (/Users/philipjohnson/projects/vue-shopify/node_modules/@babel/core/lib/config/config-descriptors.js:92:10)
    at /Users/philipjohnson/projects/vue-shopify/node_modules/@babel/core/lib/config/config-descriptors.js:64:19
    at presets (/Users/philipjohnson/projects/vue-shopify/node_modules/@babel/core/lib/config/config-descriptors.js:54:25)
    at mergeChainOpts (/Users/philipjohnson/projects/vue-shopify/node_modules/@babel/core/lib/config/config-chain.js:294:68)
    at /Users/philipjohnson/projects/vue-shopify/node_modules/@babel/core/lib/config/config-chain.js:247:7
    at buildRootChain (/Users/philipjohnson/projects/vue-shopify/node_modules/@babel/core/lib/config/config-chain.js:83:20)
    at loadConfig (/Users/philipjohnson/projects/vue-shopify/node_modules/@babel/core/lib/config/index.js:50:53)
    at transformSync (/Users/philipjohnson/projects/vue-shopify/node_modules/@babel/core/lib/transform-sync.js:13:36)
    at Object.transform (/Users/philipjohnson/projects/vue-shopify/node_modules/@babel/core/lib/transform.js:20:65)
    at transpile (/Users/philipjohnson/projects/vue-shopify/node_modules/babel-loader/lib/index.js:55:20)
    at /Users/philipjohnson/projects/vue-shopify/node_modules/babel-loader/lib/fs-cache.js:116:18
    at ReadFileContext.callback (/Users/philipjohnson/projects/vue-shopify/node_modules/babel-loader/lib/fs-cache.js:36:21)
    at FSReqWrap.readFileAfterOpen [as oncomplete] (fs.js:420:13)

Will give a look next week thanks for the report

Try adding "babel": {     "presets": ["module:@pixel2html/babel-preset"]   } in package.json

@antekera just looping back to this for another project. Thanks for the suggestion, but unfortunately the same outcome

Will move this issue to our monorepo to deal with it


Replace removed Position property with LinesOnlyPosition

Due to the changes introduced in the pull request the Position property on engine object is no longer present. This caused errors while building docker image.

This ended up being incorporated in #5 because of the related changes around the binary builds, and the fact that our current lack of dependency management makes these difficult to release separately.  Thanks, @jacobi007.


Is it possible to extract types without calling validate?

Thanks for the great library, this is extremely useful :-)
Is it possible to extract the types from a schema without calling attempt or validate similar to https://github.com/TCMiranda/joi-extract-type ?
Since I use Joi to validate requests to my API server, I would like to improve typings for the req.body/req.query by extracting types from the validation schema. Something like what follows.
interface IValidatedRequest<T> extends Request {
  body: Joi.extractTypes<T>
}

Any suggestions?

Of course. See definition of SchemaValue<T>, in which T is SchemaLike. It is similar to extractTypes.
const schema = Joi.object({ a: Joi.number() })
type value = Joi.SchemaType<typeof schema>

BTW I am also doing API validation by using typesafe-joi. It is incredibly useful 😃

Thanks a lot, this works perfectly!


Reduce the direct use of the static logger so tests functional tests work properly

Goal

Testing

Release Notes

WHAT:
WHY:
WHO:

#643  👈
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @bidetofevil and the rest of your teammates on  Graphite

agreed on all fronts! 1-3 are no-brainers - 4 would be nice too but we should assess the impact. If we really reduced how much logging we do, will this make a difference?


dev: update Dockerfile/docker-compose development environment setup

Fix the "development" workflow via Dockerfile/docker-compose and document it.

This is already merged in https://github.com/pytition/Pytition/commit/fd71c89bb6c6a667ae0ac2af34885dcce8db22e2


Updated CHANGELOG

Retroactively update the CHANGELOG to include a link to the official releases page on Github and with Mediation 4 releases (if necessary).

Do not merge until https://github.com/ChartBoost/chartboost-mediation-android-adapter-vungle/pull/68 is merged.


guard against help

Codecov Report

Merging #53 (3d1106b) into main (43b22ad) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #53   +/-   ##
=======================================
  Coverage   80.92%   80.92%
=======================================
  Files          17       17
  Lines        2065     2065
=======================================
  Hits         1671     1671
  Misses        290      290
  Partials      104      104

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 43b22ad...3d1106b. Read the comment docs.


Cannot set network.http.useToken to true

OrientDB Version, operating system, or hardware.

v2.2.5 [x]

Operating System

[x] Linux
[x] MacOSX

Expected behavior and actual behavior
Trying to use oAuth2 Token for HTTP Rest API.
Steps to reproduce the problem
Cannot set network.http.useToken to true over xml config:

        ...

      ...

and -Dnetwork.http.useToken=true
to use OrientTokenHandler.

The handler throws an NullPoint Exception because network.http.useToken has as default false and no tokenHandler is available.
com/orientechnologies/orient/server/network/protocol/http/command/post/OServerCommandPostAuthToken.java
private void init() {

    if (tokenHandler == null && OGlobalConfiguration.NETWORK_HTTP_USE_TOKEN.getValueAsBoolean()) {
      tokenHandler = server.getTokenHandler();
    }
  }

Works only in embedded mode with this:
OGlobalConfiguration.NETWORK_HTTP_USE_TOKEN.setValue("true");

hi @deacix,
I fixed the case, will be out with 2.2.7, closing.

hey! Thanks!

But this is not full fix. It is not possible to set network.http.useToken to true over xml config.

hi @deacix,
I double checked also that case, setting in the properties this
<entry name="network.http.useToken" value="true"/>
the token is enabled
Regards.

ok thanks!


Non-intuitive naming of JSON elements in study response

Looking at the REST API documentation for the Study resource we can see that initialSampleSize and replicationSampleSize are both typed as Strings as they contain textual descriptions about samples of the association study. Yet, their name, by having Size in it suggests that it is numeric, i.e. the size of each respective sample.
So my question is: is this just an unfortunate naming choice or could there be a bug? Was there the intention to have sample sizes reported? If so, would it not be useful to have also numeric variables initialSampleSize and replicationSampleSize, respectively, and change initialSampleSize and replicationSampleSize to initialSampleDescription and replicationSampleDescription, respectively?
Thanks!

Please find more details about the status of your issue here:
https://www.ebi.ac.uk/panda/jira/browse/GOCI-2440


Chain DB: avoid opening an ImmDB iterator when opening a Reader

When opening a new ChainDB Reader, an ImmutableDB iterator starting after Genesis is opened, which requires reading the first index file from disk. However, in most cases (in fact, this is the default behaviour of the Chain Sync Client), the first thing that is done with the Reader is to find a more recent intersection point, which, if it succeeds, discards the initially opened ImmutableDB iterator.
A possible optimisation is to postpone opening this iterator until it is really needed, avoid an unnecessary read.
See https://github.com/input-output-hk/ouroboros-network/blob/master/ouroboros-consensus/src/Ouroboros/Storage/ChainDB/Impl/Reader.hs#L107

#1331 included "ChainDB.Reader: add ReaderInit state as an optimisation", solving this issue.


Update bootstrap fixed thanks

Did this fix your issue with kali-rolling?

Checking right now thanks David

So far I don't know how to run it from the shell I've tried sudo commands for main.sh but get noexec_shell_scripts.md error


Ensure deprecations become a hard error in Bundler 2

What was the end-user problem that led to this PR?
The problem was some deprecations aren't guaranteed to be behind a feature flag, so we want to guarantee that we won't continue to support those behaviors when they're intended to be removed.
What was your diagnosis of the problem?
My diagnosis was we needed to ensure that deprecations don't stay deprecations past the point they're supported.
What is your fix for the problem, implemented in this PR?
My fix adds a major_version argument to the deprecation method, and raises an error if the current version is >= that version
Why did you choose this fix out of the possible options?
I chose this fix because it will ensure that everything deprecated won't continue to work past when it's supposed to, reducing the chance we'll need to accidentally support things we won't want to.

Correct me if i'm wrong but i thought the Gemfile/Gemfile.lock would be deprecated in bundler 2 and then be removed in 3?

@colby-swandale I thought we were just switching the precedence order?

Pushed fixes for the breaking in bundler 2. Did you want to tackle the last breaking spec or if you want, I'll just finish it off?

Looks like there are still a whole bunch of failures on 2.0: https://travis-ci.org/bundler/bundler/jobs/260183748#L1425

I'll tackle these tonight

I'm waiting on #5920 to be merged which fixes a lot fo the bundler 2 errors for free, i'll tackle the rest afterwards.

@colby-swandale it's been merged!

I think I screwed up the rebase because Travis is not pulling the newer code, I'll have to have a look at it tomorrow. Sorry 🙇

@segiddins is there a test that https://github.com/bundler/bundler/pull/5873/commits/95bb71c9b9d71f0cec1c4693b12a75ae9fdaa32c is solving? This is causing the failures for  bundler < 2 but all the tests before that commit pass?

It fixes a bug that caused the deprecation warning to always be printed

Rebased, might finally be green?

🎉

@bundlerbot r+


Update passphrase-existing.html

Change to HTML input field type from text to password in order to prevent shoulder surfing

added fa-eye / fa-eye-slash and the JS to toggle them on click event to html/passphrase-existing.html
also needed some CSS to position the icon, added to css/freewallet-desktop.css

got rid of inline styling for icon


bugfix: when run server Module ServerTest failed, it occur "hostname can't be null" errors. see issue #743

Ⅰ. Describe what this PR did
FixBug #743
When run server Module ServerTest failed, it occur "hostname can't be null" errors. see issue seata#743. According to logics in server.class just add XID set* ops into ServerTest class, then bug is free.
Ⅱ. Does this pull request fix one issue?
fixes #743
Ⅲ. Why don't you add test cases (unit test/integration test)?
Because this bug occur in a test class
Ⅳ. Describe how to verify it
just run ServerTest before and after this bugfix.
Ⅴ. Special notes for reviews

Codecov Report

Merging #907 into develop will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             develop     #907   +/-   ##
==========================================
  Coverage      38.13%   38.13%
  Complexity      1026     1026
==========================================
  Files            222      222
  Lines           8621     8621
  Branches        1044     1044
==========================================
  Hits            3288     3288
  Misses          4941     4941
  Partials         392      392

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 34ef826...7d50dff. Read the comment docs.

LGTM

Thanks all of you. It's my pleasure.


bug(COMPONENT): TITLE

Reproduction
Steps to reproduce:

provide MAT_DIALOG_DEFAULT_OPTIONS in the module
provide useValue. (ex. disableClose: true - see the following code)
{
provide: MAT_DIALOG_DEFAULT_OPTIONS,
useValue: {
disableClose: true,
},
},

Expected Behavior
What behavior were you expecting to see?
Configs should be set along with the default values for the other options. Such behaviour can be seen when provided in the component with dialog.open() method
Actual Behavior
What behavior did you actually see?
Given configs overwrite the Configs value, so that default options are also overwritten.
Environment

Angular:
CDK/Material:
Browser(s):
Operating System (e.g. Windows, macOS, Ubuntu):

This seems to be working, here's a stackblitz showing it: https://stackblitz.com/edit/angular-dxw9c8?file=src/main.ts

This seems to be working, here's a stackblitz showing it: https://stackblitz.com/edit/angular-dxw9c8?file=src/main.ts
Please try to click on "Open Dialog" button when your popup is already opened:

There is no backdrop
You can open the same popup over and over again without closing the previous one.
However we both know that by default the backdrop is set to true and in this case there is no backdrop.

There is no automatic merging of your override with the default options. If you want to keep the rest of the default options just merge them when providing the value:
{
    ...new MatDialogConfig(),
    disableClose: true,
}

See: https://stackblitz.com/edit/angular-dxw9c8-2sxvwj?file=src%2Fmain.ts

why then such automatic merging is happening when the configs are provided in the .open() method?

When you call open with a config it merges the given config with the default config. In your case you're overriding the default config, so it merges that with your custom default: {disableClose: true}

I understand that, however in the official documentation there is no info provided for the case when the custom config is provided in the module, you can figure that out only when investigating the source code, I think would be better to somehow include that aspect, it is not intuitive.


TLJH plugin

Fixes #2.
Fixes #7.

Add instructions for running plasmabio as TLJH plugin locally
Update playbooks

At a later stage we can add tags to the Ansible playbooks, to be able to select which tasks to run.
For example we could select the tasks that update the plugin and restart the hub only (marked as upgrade):
ansible-playbook -i hosts all.yml -u ubuntu --tags upgrade


Install location on macOS has redundant folder

Bug Description:
Theia installs in the location:
Applications -> Theia -> Theia.app
I would expect it to be just:
Applications -> Theia.app
One of the side effects is that the app doesn't appear to be indexed for system search until it is opened, although that could be a latency issue related to my system.

Steps to Reproduce:

Install Blueprint

Additional Information

Operating System: macOS Big Sur 11.2.3
Theia Version: 1.11.0

@brianking is this still an issue? I downloaded and installed blueprint today (on macOS) and I got the following:
/Users/vincentfugnitto/Applications/TheiaBlueprint.app

Not an issue. I removed the current folder+application and installed fresh from the package. This time there is no extra folder. Closing.


Small renaming of push_dataset_to_hub arguments

Small flexibility in CLI for dataset conversion

This change is

Updated it to fix the readme and doc. ok to merge @Cadene so I can push a next fix?

Quick updated behavior: default "save-tests-to-disk" to 0

all good to merge


python3Packages.parfive: disable network test

Motivation for this change
Disable network test, and tests which require another aio plugin.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

@jonringer can we close this?
It's been done in #144276 and the package now builds properly on Hydra.


Some situations are slow

I found some situations would make atom slow (er than other editors).

Open atom
Many characters in a single line
Many characters in Markdown file while previewing
Loading a file which has many lines

Thanks for the report! :smile: These have all been reported already, in #979, https://github.com/atom/markdown-preview/issues/197, and https://github.com/atom/atom/issues/8864, respectively.
Also, please take a look at the Contributing guide for a guide on reporting bugs, including searching for duplicates.


[baremetal] Harden x509 cert verify against fault injection in signature verification

Description
Dependencies: This PR is based on #2918
This PR hardens against fault injection the verification of signature of certificates and its propagation up to the caller of mbedtls_x509_crt_verify() (and variants). It builds on #2918 and also makes us of the following techniques:

Large Hamming distance
Double checks - with reporting of detected faults
Default flow assumes failure

It changes some internal interfaces but keeps the user-visible API unchanged.
Restriction of scope:

large hamming distance for internal flags only works when MBEDTLS_X509_REMOVE_VERIFY_CALLBACK is enabled - which it is in baremetal.h
this PR does not address CRL verification (neither signature verification nor propagation of flags) as it is disabled in baremetal.h
this PR only touches the parts that live in libmbedx509 - the parts in libmbedcrypto are done in #2918 and the parts in TLS will be done in a future PR.

Code size impact
Size of the libraries in bytes as measured with scripts/baremetal.sh --rom --armc5.

before
after
diff

libmbedcrypto
18467
18467
0

libmbedx509
4868
4956
+88

libmbedtls
16507
16507
0

total
39842
40930
+88

Status
READY

Rebased on top of recent #2918 as it was itself rebased on top of current baremetal to resolve conflicts.

@jarlamsa Thanks for your feedback! I implemented your suggestions. Please review again.
@artokin This is ready for you to review too.

The pr-head job fully passed, but the pr-merge job has one failure that looks spurious - restarting it.

@artokin @jarlamsa Since your last approval I had to add two commits in order to fix build issues found by the CI. As the CI is now passing again (except for spurious-looking failures), I think this is ready for you to review again.

With two approvals and a passing CI, no conflicts, and the only dependency ready for merge, this is also ready for merge.


Fix some issues and clean up

This fixes the CLI once more since Strings cannot be checked for equality using ==.
Also, this PR fixes some unclosed streams and overall optimizes some code

Looks good to me. Unless Lassebq notices something, I think this is good to merge.

String comparing issues were fixed in my local environment, except I didn't push it yet. Other than that it seems good for a merge.


Lay foundation for developing and distributing with Rust

Describe the feature
As we investigate performance improvements for dbt, we believe Rust will play a factor in this effort. We should POC Rust code in the dbt codebase and sort out what development, CI, and packaging will look like.
Things to cover:

any additional steps to set up dev environment for contributing
updated CI to test Rust code as part of our test suite
update release process to account for packaging Rust code
either port some basic functionality to rust or include noop rust code as an example

Additional context
We currently support distribution with pip and Homebrew. With the introduction of Rust, we should be able to maintain these channels of distribution without any additional steps for the user.
Who will this benefit?
Everyone! Hopefully, this will lay the foundation to continue investing into using Rust as a tool to improve performance for end users.

Will follow up here with concrete steps and exact tools to use to accomplish this.

Example of using rust extensions in python: https://github.com/fishtown-analytics/dbt/compare/experiment/rust-extensions
With this setup, rust code would be packaged with dbt-core. The development workflow essentially stays the same, except the developer will need to compile rust code after changes. As long as the rust compiler is installed (via the rust toolchain aka rustup) everything will "just work".
We did not pursue the changes involved in building dbt for distributing on PyPi with this work.


Multipage PDF

I have not found any way to ma pdf of more than one page ??? can you please guide me in this regard using this package how can i make a multi-page pdf!!!

Thank you , but is there no way to set content on each page !! actually, i have an array of HTML and html content on each index want to display on next page !!!

 I am also facing this issue while using this plugin, what will be the solution for this

Is this your project's gradle file?

no its error in console

it should generate multi-page pdf automatic. you can make a long html page and export it into this lib. try it.

Hello Team. We are able to create pdf but in pdf pages which are generated, page break is sometimes in between text and more than that, margin padding is not being applied on pdf pages at all. Is there any option which we can use from "printPdfConfiguration" apart from printSize and printOrientation? Any help would be greatly appreciated


asyncio recv_pyobj is broken

because it translates into a recv followed by a picke.loads, which ends up trying to unpickle a future :) I looked a bit and there are a variety of ways to fix this, ideally it would be fixed in the future.

This applies to zmq.eventloop.future sockets as well. Same applies when using recv_json.


Added IE 11 support using react-app-polyfill

Fix for issue #211 [Internet Explorer] Site not working

[x] Added npm package - react-app-polyfill which ensure language features are present to support Internet Explorer
[x] CSS variable fallback
[x] X-UA-Compatible meta tag
[x] IE has limited SVG support. Tried my best to fix svg without destroying existing look and feel in modern browsers like chrome

Final result screenshot

Still broken on IE

[ ] Docs page

Special instructions

Delete your entire node_modules folder
Run npm install to re-install the node_modules with polyfill
Run npm start to run again

@itsnikhil hey is this ready for review? Also, could you resolve the merge conflicts and pull in the latest changes?

Hi, @angle943
Before I resolve the conflicts, I saw you removing css variable fallback from on of my previous PR. Fallback is necessary for IE. Most of the conflicts are also because of that only. I wanted your "Go" / "No-Go" on that.

@itsnikhil good point about IE, but currently we use a lot of features that are not supported by IE site-wide, so let's not add the fallbacks.
If later we do realize that we need to add IE support (although I doubt the demand for IE support will ever get that big), we need to do a site-wide update. Let's add in the fallbacks then (or rather, remove css custom properties entirely)


Initial comment - needs better documentation

I'm trying to post a comment here:
https://www.pypy.org/posts/2023/12/pypy-v7314-release.html#utterances-thread
But the thread doesn't seem to exist yet since there are 0 comments, and the documentation is less than crystal-clear:

When Utterances loads, the GitHub issue search API is used to find the issue associated with the page based on url, pathname or title. If we cannot find an issue that matches the page, no problem, utterances-bot will automatically create an issue the first time someone comments.

It looks like there are six different configuration options, and no (documented) way to tell which one the owner of a given repo has chosen:

Blog Post ↔ Issue Mapping
Choose the mapping between blog posts and GitHub issues.

Meaning I'm stuck just blindly trying to create a new issue with the syntax of an existing one, hoping that the configuration hasn't unluckily changed between now and then, and also hoping that Utterances will pick up threads that were not created by it and also not created by the owner of the repo.

Of course, "act on my behalf" is an extremely inappropriate permission. I want to of a particular comment on a particular thread at a particular time while I supervise; I'm not giving a 3rd-party service permission to post unlimited comments in unlimited locations indefinitely and unsupervised.


olLoadFunction.provider: throw correct UnavailableGeoResourceError

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 99.612%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
12437

Relevant Lines:
12439

💛  - Coveralls


USB Midi to Bluetooth LE / Wireless Midi?

Just discovered your library and wondering: can it be used to make a esp32 convert USB midi to wireless midi over Bluetooth LE?

@tilllt
For BLE MIDI, you can use Arduino BLE-MIDI Transport by lathoub.
Combination with it, you can make USB to BLE MIDI converter.
USB-BLE MIDI Bridge for AtomS3 is one example of USB to BLE MIDI converter. Please refer to this.


Ensure dev version works when not in root dir

Previous implementation implicitly assumed that the calling code's current working directory was resqpy root, which is obviously not always the case.

Codecov Report

Merging #370 (a16efc5) into master (ddfbf6c) will increase coverage by 0.01%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master     #370      +/-   ##
==========================================
+ Coverage   74.60%   74.62%   +0.01%
==========================================
  Files         176      176
  Lines       28475    28444      -31
==========================================
- Hits        21245    21227      -18
+ Misses       7230     7217      -13

Impacted Files
Coverage Δ

resqpy/__init__.py
38.46% <0.00%> (ø)

resqpy/olio/simple_lines.py
40.16% <0.00%> (-0.49%)
:arrow_down:

resqpy/olio/wellspec_keywords.py
75.34% <0.00%> (-0.23%)
:arrow_down:

resqpy/olio/factors.py
97.05% <0.00%> (-0.09%)
:arrow_down:

resqpy/fault/_gcs_functions.py
89.05% <0.00%> (-0.08%)
:arrow_down:

resqpy/well/well_utils.py
95.06% <0.00%> (-0.07%)
:arrow_down:

resqpy/olio/triangulation.py
92.62% <0.00%> (-0.04%)
:arrow_down:

resqpy/lines/_polyline.py
90.24% <0.00%> (-0.03%)
:arrow_down:

resqpy/grid_surface.py
80.94% <0.00%> (-0.03%)
:arrow_down:

resqpy/olio/transmission.py
86.28% <0.00%> (-0.02%)
:arrow_down:

... and 8 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 ddfbf6c...a16efc5. Read the comment docs.


Load modules for each task on job-card level (rocoto XML)

Description

Use the date utility of prod_util for PTIME and NTIME.
Remove the module load from the ex-scripts.
Make each task load the modules on the job-card level (rocoto xml file).

Anticipated changes to regression tests:

[ ] Is baseline change expected ?

Subcomponents involved:

[ ] apply_incr.fd (NOAA-PSL/land-apply_jedi_incr)
[ ] ufsLand.fd (NOAA-EPIC/ufs-land-driver-emc-dev)
[ ] ufs_model.fd (ufs-community/ufs-weather-model)
[ ] vector2tile_converter.fd (NOAA-PSL/land-vector2tile)
[x] none

Linked PR's and Issues:

Resolve Issues #103 #104
Testing (for CM's):

RDHPCS

[x] Hera
[x] Orion
[ ] Jet
[ ] Gaea
[ ] Cheyenne

CI

[x] Completed

PW-Clouds

[ ] AWS
[ ] AZURE
[ ] GCP

    Start 1: test_vector2tile
1/7 Test #1: test_vector2tile .................   Passed    3.18 sec
    Start 2: test_create_ens
2/7 Test #2: test_create_ens ..................   Passed    3.68 sec
    Start 3: test_letkfoi_snowda
3/7 Test #3: test_letkfoi_snowda ..............   Passed   35.28 sec
    Start 4: test_apply_jediincr
4/7 Test #4: test_apply_jediincr ..............   Passed    4.36 sec
    Start 5: test_tile2vector
5/7 Test #5: test_tile2vector .................   Passed    4.80 sec
    Start 6: test_land_driver
6/7 Test #6: test_land_driver .................   Passed    9.78 sec
    Start 7: test_ufs_datm_land
7/7 Test #7: test_ufs_datm_land ...............   Passed  520.69 sec

100% tests passed, 0 tests failed out of 7

Total Test time (real) = 581.82 sec


Release v0.12.0

Coverage remained the same at 100.0% when pulling 6476eca59c1b7b2498f7f8ba8fe4ddad41e51431 on release/0.12.0 into 77d3c8521c6ebb80cbbbd64303cb8230b0426212 on master.


[Instrumentation] buffer_reference to array with scalar block layout produces incorrect output, incorrect 'Device address out of bounds' errors

See for details: https://github.com/KhronosGroup/Vulkan-ValidationLayers/issues/4577

@s-perron Can you please assign this to @ncesario-lunarg ?

@ncesario-lunarg Indeed, @jeremyg-lunarg has significantly refactored inst_buff_addr_check_pass.cpp, including the GetTypeLength() function indicated as problematic in the original VVL issues. It now always returns 3 * elementSize for vec3 and does not round up to vec4 as it previously did which was causing the problem for scalar layout.
This is not actually "correct" for std140 and std430, but for the purposes of this module, it works for all block layouts including scalar. This is because the result of GetTypeLength() only comes into play for the last member of block. Previously, it was returning 4 * elementSize for vec3 which was causing a memory exception for scalar layout. Now it always returns 3 * elementSize. This is correct for scalar layouts. It is also "correct" for all other layouts because this code does not depend on correctly padding a trailing vec3 in a block and thus does not cause a problem for these layouts.
This is probably just as well since I don't think there is a way to detect scalar layout was used in the generation of a SPIR-V module. We would need to have VVL somehow tell us to use it.
While I have not extensively verified that inst_buff_addr_check_pass.cpp is doing the right thing for the original shader, I think it can be logically concluded that it will and the original problem has been fixed, and no new errors are caused by this change.
I.E. I think this problem is fixed.

closing based on Greg's comment


npm WARN deprecated<EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained. Upgrade to<EMAIL_ADDRESS>

We can't do much here. The warning comes from old version of glob-watcher which comes as dependency of vinyl-fs.

@redaikidoka create an PR to that repo that is using old version of lo-dash. That should help with this one.


Pull request opened which attempts to downgrade a dependency

Is there an existing issue for this?

[X] I have searched the existing issues

Package ecosystem
Bundler
Package manager version
Bundler 2.3.25
Language version
Ruby 3.0
Manifest location and content before the Dependabot update
/Gemfile
dependabot.yml content
No response
Updated dependency
Redis 4.8.1 -> Redis 5.0.6
What you expected to see, versus what you actually saw
I don't believe the PR should have been opened as the only path forward to upgrade Redis was to downgrade a top-level dependency that specified redis (>= 4.5.0, < 5) back to a version before redis v5 was disallowed.
Native package manager behavior
bundle up redis produces "Bundler attempted to update redis but its version stayed the same."
Images of the diff or a link to the PR, issue, or logs
diff --git a/Gemfile.lock b/Gemfile.lock
index b3fe9f86f..c2e3aa288 100644
--- a/Gemfile.lock
+++ b/Gemfile.lock
@@ -12,8 +12,8 @@ GEM
       einhorn (>= 0.7.4)
       sidekiq (>= 6.5.0, < 7)
       sidekiq-pro (>= 5.5.0, < 6)
-    sidekiq-pro (5.5.8)
-      sidekiq (~> 6.0, >= 6.5.6)
+    sidekiq-pro (5.5.2)
+      sidekiq (>= 6.5.0)

 GEM
   remote: https://rubygems.org/
@@ -359,7 +359,10 @@ GEM
     rake (13.0.6)
     rbtree3 (0.7.0)
     redcarpet (3.6.0)
-    redis (4.8.1)
+    redis (5.0.6)
+      redis-client (>= 0.9.0)
+    redis-client (0.14.1)
+      connection_pool
     regexp_parser (2.7.0)
     representable (3.2.0)
       declarative (< 0.1.0)
@@ -432,10 +435,10 @@ GEM
       rubyzip (>= 1.2.2, < 3.0)
       websocket (~> 1.0)
     semantic (1.6.1)
-    sidekiq (6.5.8)
-      connection_pool (>= 2.2.5, < 3)
+    sidekiq (6.5.5)
+      connection_pool (>= 2.2.2)
       rack (~> 2.0)
-      redis (>= 4.5.0, < 5)
+      redis (>= 4.5.0)
     sidekiq_remappable_errors (1.0.1)
     signet (0.17.0)
       addressable (~> 2.8)

Smallest manifest that reproduces the issue
No response

Do you have a public repo that reproduces the problem? https://github.com/dependabot/dependabot-core#reproducible-example

Hi,
I think I do but this is the first time I've tried to use the dependabot cli tool so forgive me if I've made a misstep somewhere along the line.
https://github.com/jaswilli/dependabot-7127 seems like it's the minimal reproduction.
When I run dependabot update -f job.yml where job.yml is:
job:
  package-manager: bundler
  allowed-updates:
    - update-type: all
  ignore-conditions:
    - dependency-name: sidekiq
      update-types:
      - version-update:semver-major
  source:
      provider: github
      repo: jaswilli/dependabot-7127
      directory: /

The output indicates a PR is going to be created to update redis, even though it shouldn't be allowed:
updater | 2023/04/20 18:33:04 INFO Results:
updater | +-----------------------------------------+
updater | |   Changes to Dependabot Pull Requests   |
updater | +---------+-------------------------------+
updater | | created | redis ( from 4.8.1 to 5.0.6 ) |
updater | +---------+-------------------------------+

Here's a gist containing the entire output if it's useful:
https://gist.github.com/jaswilli/45e877a4435869571fabd55d01a76a99


.

Hey!
It was by mistake that I submitted the issue empty!
I was editing it when you just closed it!
On Mon, Dec 9, 2019 at 11:35 PM Areeb Jamal<EMAIL_ADDRESS>wrote:

Closed #1996
https://github.com/fossasia/open-event-organizer-android/issues/1996.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/fossasia/open-event-organizer-android/issues/1996?email_source=notifications&email_token=AN57MSXDWZENBSDUTHXJPN3QX2CH3A5CNFSM4JYN7C22YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOVLT7WIY#event-2867329827,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AN57MSQWUUJYEK5AW4ATGQLQX2CH3ANCNFSM4JYN7C2Q
.

I closed it because it is not the correct repo for your issue. Read before creating issues


Add .json as an optional file extension

I have some goejson files that are jut .json files. It shouldn't be the default handler for those, but an optional one.
@gnestor

Working on this one now...


Optimize PNG images losslessly

Command used:
parallel oxipng --strip --zopfli ::: **/*.png

@Calinou this is nice, but it never ends... Shouldn't we choose the lazy man way and add this operation to Github actions?

Shouldn't we choose the lazy man way and add this operation to Github actions?

Indeed, you can add ImgBot to the repository to automatize this.

I installed oxipng so I can optimize images when they are created/updated. Thanks!


Update getting-started.md

Added a description on what Appsmith does

Hey @Sayanta66 Thanks for this PR but this is not a good quality contribution. I would suggest you follow our contribution guides and pick up one of the Good First Issues to get started.


Mechanical Pipes and Machines wont in/out liquids

Hello,
So i have a problem with getting chloride from electrolytic separator to the chemical infuser  with mechanical pipes (even tried it with transfer nodes and ender io conduits and doesnt work). As you can see from the pictures, it doesnt even connect to the chemical infuser, so am i doing something wrong here or is it the code fault? Im getting kinda frustraded lol

Aren't they gaseuos? Yes, they are gaseous so try with gas pipeps ans look how it flows :).

Make sure you have the inputs and outputs for the machines correct the Configuator helps a ton with making sure the input and outputs are correct

AS Chaos234 pointed out, the Electrolytic Separator inputs fluids (mechanical pipes) and produces 2 gasses.  Use Pressurized Tubes to extract the Chloride, which I think will come out of the right side of the block (left side on the bottom picture).
As a pre-warning before you find it, The Electrolytic Separator does not receive a power efficiency boost from Energy Upgrades (only the increased internal capacitor).  It produces Hydrogen, which can be burned in a Gas-Burning Generator to produce power (the same amount that you put in).  This upgrade abnormality is there to prevent it from breaking the laws of thermodynamics.
@KingZero I think the Electorlytic Separator is one of the handful of blocks that doesn't have side configuration.  The output and input sides can't be changed.

Oh no's, Im a derp, sorry for the dumb question and thank you for the help.


Add license information to package.json and link it in readme.md

Just to make it visible in https://www.npmjs.com/package/mocha-generators for the next release

Thanks!


Explicitly show the user what "Authorized user:" means (which username)

I saw issue #208 and realized that it might not be obvious to everybody what step2.sh actually means when it's asking for “Authorized user”.
(read #208 for more details, that particular user "had no idea that the username and user were different things", and I think that might be more common than you'd think)
i.e. what the installer specifically wants the user to type in is the macOS UNIX username that launched the installer from macOS (="Login user:")
Collecting system information...
...
  Login user: (username)

Suggestion:
Show the user's actual UNIX username explicitly in step2.sh ("Login user" will first have to be transferred via the Asahi partition or whatever but this would be amazing customer service)
i.e. instead of these rather vague instructions in step2.sh, record and specify the user's actual exact username ("Login user" from macOS step 1):
98  echo "Please enter your macOS credentials (for the macOS that you"
99  echo "used to run the first step of the installation)."

Option 2: ...or if that's not possible for some reason, at least add a hint to the "wall of text" instructions (on macOS, shown just before shutting down) that the username you will have to give in step2.sh is (show the current username / "Login user:" that started the installer)

The real issue here is that we should wrap bputil/kmutil, ask for the password ourselves, and then do some expect like thing to feed it in. That will clear up the confusion in step2 properly. It's also not entirely trivial though :).


Rebuild logic

I was reading the rebuild code, and the logic seemed a little off to me.  Please have a look at my changes and let me know if I'm mistaken!

I think I did something similar in the curly branch:
https://github.com/tadzik/panda/commit/7150a7182daf6322625a7220530aea87690665cd
https://github.com/tadzik/panda/commit/5f74966f1e27510ccb577f085f4011df2f606e16
When working on curly I hit the issue that bootstrapping panda would rebuild a not-yet-installed panda, before all panda deps were installed.

@FROGGS Is the problem just in the bootstrap process?  If so, perhaps we could supply --no-rebuild in the bootstrapping invocation.

Sounds more like rebuild hitting a little bit too early in the general case. I noticed similar problems while initially working on it, but the solution I thought of requires a bit of throwing around panda workflow a little, so I belayed that.
I'm going to accept this nonetheless since it reads better and makes more sense though :)


Update EntityTagFilter to use 'some' instead of 'every'

Signed-off-by: Donner, Lauren [USA]<EMAIL_ADDRESS>Hey, I just made a Pull Request!

This PR changes the behavior of the EntityTagFilter to include all components that match any of the tags chosen.
Because tags can be used to classify catalog entries in various ways, when filtering on multiple tags it stands to reason we would want to find any component that contains any one of those tags, to cast a wide net to discover what we’re looking for.
If, for example, a user is searching for a component related to artificial intelligence, I would expect the user to be able to find my component by checking both “ai” and “artificial-intelligence” in the tag filters even if my component only has the “ai” tag or only has the “artificial-intelligence” tag, but not both.
Or, if a user selects 4 tags and a component has 3/4 of those tags, I would think that component would still be relevant to what they’re searching for.

This would also be more consistent with how filters work when using them in /entities, which uses an “or” relationship for filters.

If a user is searching for something using tags, I think it makes more sense for it to match any of the tags selected, not just components with every single tag in the list.

:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[x] Tests for new functionality and regression tests for bug fixes
[x] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Thank you for taking a look and for adding it to the docket! :)

Thank you for bringing it up for discussion! Yeah something like that was our plan "b" - I'm gonna be pretty swamped for the next sprint or so but I think the plan is to go for something like this if changing the default isn't an option.

Might be a little time before I can get to that, though - should I just close this PR and open another one later or can I leave this one alone for now and come back to it later?

@ltdonner your plan B sounds good and the mockup is in line with what I'm thinking as well 👍
Our stalebot is likely going to poke and close this PR if we leave it open so I'll close it for now but feel free to reopen or just open a new PR referring to this one when you've got some capacity to work on this. Thanks!


Remove outdated information about downloading json for gcp accounts

In pks 1.1.x is not going to be more necessary to add the JSON key when setting up the cloud provider. Only the service account id is going to be necessary.
This part of the documentation can be removed because not more necessary.
[#158457770]

Thanks @carlo-colombo!


Unnest into alias doesn't define the column

Version
1.12.0
What happened?
I guess the parser doesn't understand that the alias after UNNEST defines a column, so when later trying to determine the type of the column, it thinks the column doesn't exist.
Relevant log output
query.sql:2:8: column "x" does not exist

Database schema
No response
SQL queries
-- name: FromUnnest :many
SELECT x FROM UNNEST(array[5,6]) x;

Configuration
No response
Playground URL
https://play.sqlc.dev/p/01ee6a49034c018482526ca75aa29cf93aa447d3d93417543266cd4a6d1577b0
What operating system are you using?
Linux
What database engines are you using?
PostgreSQL
What type of code are you generating?
Go

$ SQLCDEBUG=dumpast=1 sqlc generate
([]interface {}) (len=1 cap=1) {
 (*ast.RawStmt)(0xc00052cb60)({
  Stmt: (*ast.SelectStmt)(0xc0003f1e40)({
   DistinctClause: (*ast.List)(0xc000642570)({
    Items: ([]ast.Node) <nil>
   }),
   IntoClause: (*ast.IntoClause)(<nil>),
   TargetList: (*ast.List)(0xc000642588)({
    Items: ([]ast.Node) (len=1 cap=1) {
     (*ast.ResTarget)(0xc00063f3e0)({
      Name: (*string)(<nil>),
      Indirection: (*ast.List)(0xc0006425a0)({
       Items: ([]ast.Node) <nil>
      }),
      Val: (*ast.ColumnRef)(0xc00052cae0)({
       Name: (string) "",
       Fields: (*ast.List)(0xc0006425b8)({
        Items: ([]ast.Node) (len=1 cap=1) {
         (*ast.String)(0xc0006445a0)({
          Str: (string) (len=1) "x"
         })
        }
       }),
       Location: (int) 33
      }),
      Location: (int) 33
     })
    }
   }),
   FromClause: (*ast.List)(0xc0006425d0)({
    Items: ([]ast.Node) (len=1 cap=1) {
     (*ast.RangeFunction)(0xc00052cb40)({
      Lateral: (bool) false,
      Ordinality: (bool) false,
      IsRowsfrom: (bool) false,
      Functions: (*ast.List)(0xc0006425e8)({
       Items: ([]ast.Node) (len=1 cap=1) {
        (*ast.List)(0xc000642600)({
         Items: ([]ast.Node) (len=2 cap=2) {
          (*ast.FuncCall)(0xc00063b950)({
           Func: (*ast.FuncName)(0xc00063f440)({
            Catalog: (string) "",
            Schema: (string) "",
            Name: (string) (len=6) "unnest"
           }),
           Funcname: (*ast.List)(0xc000642618)({
            Items: ([]ast.Node) (len=1 cap=1) {
             (*ast.String)(0xc0006445e0)({
              Str: (string) (len=6) "unnest"
             })
            }
           }),
           Args: (*ast.List)(0xc000642630)({
            Items: ([]ast.Node) (len=1 cap=1) {
             (*ast.A_ArrayExpr)(0xc000644610)({
              Elements: (*ast.List)(0xc000642648)({
               Items: ([]ast.Node) (len=2 cap=2) {
                (*ast.A_Const)(0xc000642660)({
                 Val: (*ast.Integer)(0xc000648090)({
                  Ival: (int64) 5
                 }),
                 Location: (int) 53
                }),
                (*ast.A_Const)(0xc000642678)({
                 Val: (*ast.Integer)(0xc000648098)({
                  Ival: (int64) 6
                 }),
                 Location: (int) 55
                })
               }
              }),
              Location: (int) 47
             })
            }
           }),
           AggOrder: (*ast.List)(0xc000642690)({
            Items: ([]ast.Node) <nil>
           }),
           AggFilter: (*ast.TODO)(0x2114930)({
           }),
           AggWithinGroup: (bool) false,
           AggStar: (bool) false,
           AggDistinct: (bool) false,
           FuncVariadic: (bool) false,
           Over: (*ast.WindowDef)(<nil>),
           Location: (int) 40
          }),
          (*ast.TODO)(0x2114930)({
          })
         }
        })
       }
      }),
      Alias: (*ast.Alias)(0xc000644660)({
       Aliasname: (*string)(0xc000644650)((len=1) "x"),
       Colnames: (*ast.List)(0xc0006426a8)({
        Items: ([]ast.Node) <nil>
       })
      }),
      Coldeflist: (*ast.List)(0xc0006426c0)({
       Items: ([]ast.Node) <nil>
      })
     })
    }
   }),
   WhereClause: (*ast.TODO)(0x2114930)({
   }),
   GroupClause: (*ast.List)(0xc0006426d8)({
    Items: ([]ast.Node) <nil>
   }),
   HavingClause: (*ast.TODO)(0x2114930)({
   }),
   WindowClause: (*ast.List)(0xc0006426f0)({
    Items: ([]ast.Node) <nil>
   }),
   ValuesLists: (*ast.List)(0xc000642708)({
    Items: ([]ast.Node) <nil>
   }),
   SortClause: (*ast.List)(0xc000642720)({
    Items: ([]ast.Node) <nil>
   }),
   LimitOffset: (*ast.TODO)(0x2114930)({
   }),
   LimitCount: (*ast.TODO)(0x2114930)({
   }),
   LockingClause: (*ast.List)(0xc000642738)({
    Items: ([]ast.Node) <nil>
   }),
   WithClause: (*ast.WithClause)(<nil>),
   Op: (ast.SetOperation) None,
   All: (bool) false,
   Larg: (*ast.SelectStmt)(<nil>),
   Rarg: (*ast.SelectStmt)(<nil>)
  }),
  StmtLocation: (int) 0,
  StmtLen: (int) 60
 })
}

I guess the parser doesn't understand that the alias after UNNEST defines a column

That is indeed the case.

I had another idea right after I hit send.
The other option we have is to use a rewrite pass for these aliases since ast.Alias is a sqlc owned type.
During a rewrite we can pattern match the *pg_ast.List{*pg_ast.FunctionCall, *pg_ast.Alias} and transform it to something along the lines of: *ast.List{*ast.Alias{Node: *ast.FunctionCall}}.
This would require updating the *ast.Alias type to have new fields, but should theoretically be backwards compatible, and I believe that since it is in internal/ it shouldn't be breaking for any outward facing APIs

any workaround for this issue?

Closing as a duplicate of https://github.com/sqlc-dev/sqlc/issues/1322


(SUP-3735) have dashboards autorefresh

Prior to this commit the dashboards where static until refreshed manually in the UI.
The new default behaviour for all dashboards, other than the system data dashboard (because its static data) is to autorefresh, defaulting to the number 1 option, which in this case is 5(s)

on discussion 5 seconds was a but much, considering we don't have poll intervals that low, 5M makes more sense


Fix examples link

Rebase please. Don't use master as a base or commit to it as it causes complications when I merge dev into master.


(PUP-7825) Backport to 4.10.x

@justinstoller we were talking earlier about possible risky interactions with your environment isolation backports, does this look good to you from that perspective?

Yep, looks good!

CLA signed by all contributors.

Since we're at the wire for the next 4.10.x release and Justin says this is fine, I'm hitting the button.


avatar link arguments

This PR adds an option for passing arguments directly to the rendered a tag in the Avatar component.
Situation:
This came up as an issue when I tried to place a margin on the Avatar component, but it distorted the image. When trying to use the "mr-2" class, the linter will not allow it, asking to prefer system arguments instead.
Solution:
Create a link_arguments param that will allow direct placement of link arguments to the rendered LinkComponent

Hey @camertron - not sure if there's something else I need to do to merge these changes, but seems like as a first-time contributor there are some checks that a maintainer has to do first?

I think I'm going to close this PR with changes for now since we have found a workaround on our end, and I am nervous to make these API changes to this component, but not others that render nested components. I can re-open in the future if this is a more widely adopted pattern!


Add support for writing PSK type key from CLI

It should be possible to store PSK from file to the modem credential storage.
The write logic is the same as before, so only need to add PSK to the list of KEY_TYPE allowed values from CLI.

 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.


Tests for @SoftDelete

Fixes #1787
Covers the primary annotation value options.

I will send a new PR


[feat][broker] Support pluggable TopicCompactedService

Fixes #xyz

Master Issue: #xyz

PIP: #xyz

Motivation

Modifications
Verifying this change

[ ] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Does this pull request potentially affect one of the following parts:

If the box was checked, please highlight the changes

[ ] Dependencies (add or upgrade a dependency)
[ ] The public API
[ ] The schema
[ ] The default values of configurations
[ ] The threading model
[ ] The binary protocol
[ ] The REST endpoints
[ ] The admin CLI options
[ ] The metrics
[ ] Anything that affects deployment

Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository:

Codecov Report

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

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

@@            Coverage Diff            @@
##             master      #40   +/-   ##
=========================================
  Coverage          ?   72.96%
  Complexity        ?    31972
=========================================
  Files             ?     1869
  Lines             ?   138710
  Branches          ?    15235
=========================================
  Hits              ?   101208
  Misses            ?    29460
  Partials          ?     8042

Flag
Coverage Δ

inttests
24.16% <0.00%> (?)

systests
24.94% <0.00%> (?)

unittests
72.24% <0.00%> (?)

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


Adding ability to suppress the cell focus piece

So a little checking around found that the issue appears to be that you force the focus back to the page upon refresh. This may be all fine and good for most applications but if creates an issue on IE 11. So in order to allow for a user to manually choose at time of refresh whether to do this or not, I set an optional parameter on all refresh calls that call the "restoreFocusedCell" function. if that parameter is true, the function does not restore focus.

Fixed my pull request, guess I should compile the typescript to ensure no errors :P

added property 'suppressFocusAfterRefresh' - didn't use PR as it has to many files changed - maybe you checked in the dist folder?

That's fine, the PR was modified too many times. It may have been updated with a newer version of the grid as I kept checking the issues. Thanks for the add though!


#include <boost/type_traits/is_convertible.hpp> instead of <boost/type_traits.hpp>

There is a fragment in .../beast/core/buffers_prefix.hpp:
#if BOOST_WORKAROUND(BOOST_MSVC, < 1910)
#include <boost/type_traits.hpp>
#endif

Actually only boost::is_convertible is used, so the include statement can reference only boost/type_traits/is_convertible.hpp:
#if BOOST_WORKAROUND(BOOST_MSVC, < 1910)
#include <boost/type_traits/is_convertible.hpp>
#endif

Such replacement can reduce dependency and is handy if only subset of boost files is available.

@Anton-V-K,
Thanks very much for this. I'll get this into the next release right away.


Resize window immediately after dragging it to another monitor with different density

Most applications will resize their windows immediately. Compose windows don't resized before releasing left mouse button:

How it is happening with native window on Windows:

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


Make defaultOptions into a public function

At the moment the defaultOptions function is private, as such it can't be used by other libraries:

https://github.com/junegunn/fzf/blob/373c6d8d55066251dc7af58598de6af4ff4570cf/src/options.go#L224-L230

A simple patch like:

https://github.com/cipriancraciun/fzf/commit/524c512952bcc8c8a53bde07691d3ea367b77823

, could allow users to prepare options with fzf upstream defaults, override what they need, and pass it to fzf.Run.  (This is especially useful for those wanting to embed fzf in their own tools.)

So I'm assuming this is a "wont' fix" also?

Yes.


Mention full jQuery version in "Getting started" for apps that use Ajax calls

I am starting to migrate an application to Boosted 4.
The documentation uses the jQuery "slim" version. I tried that and got an error because $.ajax is not supported by this version.
The "Getting started" version says that While we use jQuery’s slim build in our docs, the full version is also supported ; could you add a line saying that applications that use Ajax calls should use the full version, and provide the link with the correct integrity attribute ?

Maybe it can help you :wink:
<script src="https://code.jquery.com/jquery-3.2.1.min.js" integrity="sha384-xBuQ/xzmlsLoJpyjoggmTEz8OWUFM0/RC5BsqQBDX2v5cMvDHcMakNTNrHIW2I5f" crossorigin="anonymous"></script>

to generate the integrity value use : https://www.srihash.org/

Thank you. Can this be added to the documentation ? If so, should I submit a PR ?

@Lausselloic any concerns about adding that to your documentation ?

Yes, we will take a look to put a warning into the doc, and more details about Slim version versus full one.
@Johann-S Maybe also an improvement for Bootstrap doc? Will see to PR that when we've done

Yep that's can be an improvement in Bootstraps documentation :+1:
What jQuery said about that slim version :

Sometimes you don’t need ajax, or you prefer to use one of the many standalone libraries that focus on ajax requests. And often it is simpler to use a combination of CSS and class manipulation for all your web animations. Along with the regular version of jQuery that includes the ajax and effects modules, we’ve released a “slim” version that excludes these modules.


RUM-3669 avoid feature flag spamming events

What does this PR do?
This PR attempts to improve the performance linked to setting FeatureFlag evaluations on a RUM View. Namely:

create an addFeatureFlagBatchEvaluation() method allowing to send a batch of feature flags instead of sending them once at a time. This limits the number of event the Rum View Scope has to process, and the number of view updates written on disk.
add a check in the RumViewScope handling the feature flags updates: instead of writing an event update for every call to the addFeatureFlagEvaluation() and addFeatureFlagBatchEvaluation() methods, it only writes an event if at least one feature flag value was changed.

Motivation
For some customer updating many feature flags at once, that would result in a lot of RawRumEvents being processed, and a lot of RUM View updates being written on disk. In some extreme cases it could lead to a lot of backpressure on the executor queues.

Codecov Report

Merging #1932 (23e64db) into release/2.7.0 (9d7e3f9) will decrease coverage by 0.12%.
The diff coverage is 100.00%.

Additional details and impacted files
@@                Coverage Diff                @@
##           release/2.7.0    #1932      +/-   ##
=================================================
- Coverage          83.56%   83.44%   -0.12%
=================================================
  Files                481      481
  Lines              17413    17394      -19
  Branches            2590     2586       -4
=================================================
- Hits               14550    14513      -37
+ Misses              2177     2175       -2
- Partials             686      706      +20

Files
Coverage Δ

.../main/kotlin/com/datadog/android/rum/RumMonitor.kt
28.57% <ø> (ø)

...g/android/rum/internal/domain/scope/RumRawEvent.kt
100.00% <100.00%> (ø)

.../android/rum/internal/domain/scope/RumViewScope.kt
93.47% <100.00%> (-0.48%)
:arrow_down:

.../android/rum/internal/monitor/DatadogRumMonitor.kt
85.99% <100.00%> (+0.73%)
:arrow_up:

... and 25 files with indirect coverage changes


Player can go through obstacles

Add a collision checker.

Update : collision are up on a basic level, sill buggy and not tested.


Feature/support conan package creation from local build

Feature/support conan package creation from local build

The CI cache issue with the up-cpp step is fixed by #36. We will get that merged so you can rebase your PR onto the fix.

Closing stale pull requests. We are tracking conan recipes on the 1.5.8 project board.


Add maxTouchPoints

navigator.maxTouchPoints is important for websites which need to know if user's device have touchscreen

maxTouchPoints is part of Pointer Events, which already has an entry:
http://caniuse.com/#feat=pointer

Also now available at https://caniuse.com/#feat=mdn-api_navigator_maxtouchpoints


pxt serve from forkof fails

When launching pxt serve from forkof, build fails.

If this is still an issue reopen. I don't see this being impacting the end product.


Delete: Optimization when no HSMs exist

During a stack delete operation, detect if zero HSMs exist and skip 30 second wait before checking state of HSMs. For example, if an error occurs during stack create and before any HSMs have been created, a delete operation will currently still wait for 30 seconds before checking the state of HSMs in the cluster and recognizing that none exist.

https://github.com/aws-samples/aws-cloudhsm-cloudformation-template/commit/2f284dfcc984ba253056bfb3a1915cb97717a77a


Add Node::children_elements

@adamreichold I think it would be a great idea to have elements-only alternative for all of our iterators. If you're interested in it.

@adamreichold I think it would be a great idea to have elements-only alternative for all of our iterators. If you're interested in it.

I am somewhat undecided whether I think this is a good idea. In my usage of roxmltree, I repeatedly wondered whether I would create a set of generic iteration/extraction functions on top of the iterator-based API. But in the end, just working with the iterators was simple enough.
If we start adding such convenience API to roxmltree, when do we stop? The most reasonable choice I see ATM is to add only stuff that benefits from having access to the crate's internals. But due to .children().filter(|node| node.is_elment()) being simple enough, I don't think children_elements would pass that test.
One alternative I could get behind is/was #70, i.e. adding an optional dependency here on simplecss to add a feature gated
Node::select(&self, &Selector) -> impl Iterator<Item=&Node>;

because this would be a more fundamental improvement of expressive power. Of course, as you mentioned in #70, the same issue of "Where to stop" would then exist for simplecss as the feature requests start coming in over there...

Yep, I completely forgot about it. You're suppose to use iterators for this. That was the original design goal.
Yes, a bit more verbose, but much more flexible.
We do have some Node::*_element methods, like first_element_child, but having dedicated iterators would probably be an overkill.
I do consider roxmltree to be feature complete and there is no need for CSS query and other stuff. It's already too complicated for my taste, but this is mainly due to inherent complexity of XML.


Search results might be broken.

When putting in the search term "SDL_EVENT_WINDOW_PIXEL_SIZE_CHANGED", some results are gotten. When clicking on the "SDL_EventType" search result, you are redirected to https://wiki.libsdl.org/SDL2/SDL_EventType . However, "SDL_EVENT_WINDOW_PIXEL_SIZE_CHANGED" does not occur on that page, only on the SDL3 version.

Okay, this fix is live on wiki.libsdl.org now!
https://wiki.libsdl.org/wiki/search?q=SDL_EVENT_WINDOW_PIXEL_SIZE_CHANGED


Header issue in safari

Hello,
We are using this library with kevel. When we fire impression or click trackers using the client.pixels.fire method, Safari and Firefox both throw an error:
Failed to load resource: Request header field User-Agent is not allowed by Access-Control-Allow-Headers.
It appears this library is setting a header that is not allowed by the kevel backend?
It looks like the library is forcing a user agent header field here:
https://github.com/adzerk/adzerk-decision-sdk-js/blob/1b5988d61bea60a7b6079607d591fa893e4e0b65/src/client.ts#L338
Could this header be disabled?

Hello,
There is a second problem here. When we use a proxy to avoid CORS issues, the request goes through fine, but because this SDK is overriding the User-Agent header (again doesn't happen in Chrome, just Safari and Firefox) all device and browser information is removed, so our reports in Kevel show no traffic from these browsers (both mobile and desktop).
Safari:

Firefox:

And Chrome is fine, it won't let you override the User-Agent (no idea what version of chrome this started though):

Our reports for these campaigns now show a large number of Chrome users and no Safari or Firefox (i.e. no iPhone users, which is impossible).
Please update your library to allow us to disable this User-Agent header override.


Add webpack config options

This is a bit of an experiment based off our discussion yesterday. Let me know what you think. We may want to do some validation on the CLI side for the string that's passed to entry.

I like this but I want to explore what other options before we commit to this. For instance how will this work when we give them a entry point path?
Also could using individual options help us when we want to do defaults.
For instance
--mode="development" maybe the default is always production or reverse

versus the way we have it it here makes that a bit harder because the position of those values can change if they are left out.

The main issue I've come across is we can't map multiple values to an option like we had sketched out yesterday, the item is ignored entirely.
--name client ./src/client/index.tsx

results in
{
  name: "client"
}

so I think we're going to have to make the file path the last item in the entry string.
The only other option I can see is if all the flags take an array of strings but then we have to make sure everyone maps them in the same order. Ex
--mode production,production --name client,server --target web,node --file-path ./src/client/index.tsx,./src/server/index.tsx

If you were to switch any of them it would all fall apart where it's a bit easier to tell if you have the right ones mapped together as one string

In apps/pixeloven/site I ran
yarn build:development

which does not include the stats option and I still got

Awe! Sorry. I pushed a fix to something I had done wrong in the webpack config. And I meant to cancel a comment I had placed but isntead closed the PR. :)


Allow hosts, instructors, and helpers to be selected on event details page

The event details page should (only) allow instructors and helpers to be added by selection from a list of people who are in the database.  It should be possible to add hosts this way as well.  The wiki page for the event can be used for notes about people who aren't in the database.

Solved in #234.


Add Zot dashboard

This PR adds a private dashboard for Zot related metrics.

Checklist

[x] Update changelog in CHANGELOG.md in an end-user friendly language.

Where is your dashboard coming from ? Maybe add the source so it's easier to update it later on?

@allanger Can you answer this question?
We derived quite a lot by now, but having the upstream reference to pick future additions might be useful.


descriptor 'lower' for 'str' objects doesn't apply to a 'float' object

I tried updating data on existing datasets retrieved from Yahoo Finance using collector.py but received the following error.
The code used is:
python scripts/data_collector/yahoo/collector.py update_data_to_bin --qlib_data_1d_dir ~/desktop/quant_engine/qlib_data/us_data --trading_date 2023-08-16 --end_date 2023-08-17 --region US
"us_data" folder saved those three folders (calendar, features, and instruments) which contain data collected, normalized, and dumped following the instruction.

你把pandas降级到1.5.3，numpy降级到1.23.5试试。安装视频可参考这里，如果严格按这个视频安装，则各个包的版本就是对的。

Is the data you are using self-generated? You can check the following instruments/all.txt for abnormal data.
The data I downloaded using scripts/get_data  and didn’t find the problem you describe.

Is the data you are using self-generated? You can check the following instruments/all.txt for abnormal data. The data I downloaded using scripts/get_data and didn’t find the problem you describe.

The data is downloaded from Yahoo Finance by using the code provided in this link https://github.com/microsoft/qlib/tree/main/scripts/data_collector/yahoo#Automatic-update-of-daily-frequency-data
which is
python collector.py download_data --source_dir ~/.qlib/stock_data/source/us_data --start 2020-01-01 --end 2020-12-31 --delay 1 --interval 1d --region US

Is the data you are using self-generated? You can check the following instruments/all.txt for abnormal data. The data I downloaded using scripts/get_data and didn’t find the problem you describe.

The data is downloaded from Yahoo Finance by using the code provided in this link https://github.com/microsoft/qlib/tree/main/scripts/data_collector/yahoo#Automatic-update-of-daily-frequency-data
which is python collector.py download_data --source_dir ~/.qlib/stock_data/source/us_data --start 2020-01-01 --end 2020-12-31 --delay 1 --interval 1d --region US

Is the data in ~/desktop/quant_engine/qlib_data/us_data your own generated data? You can check if the data in ~/desktop/quant_engine/qlib_data/us_data/instruments/all.txt is in an exception. Because from the error message you provided, it may be due to the existence of abnormal values in ~/desktop/quant_engine/qlib_data/us_data/instruments/all.txt.

Is the data you are using self-generated? You can check the following instruments/all.txt for abnormal data. The data I downloaded using scripts/get_data and didn’t find the problem you describe.

The data is downloaded from Yahoo Finance by using the code provided in this link https://github.com/microsoft/qlib/tree/main/scripts/data_collector/yahoo#Automatic-update-of-daily-frequency-data
which is python collector.py download_data --source_dir ~/.qlib/stock_data/source/us_data --start 2020-01-01 --end 2020-12-31 --delay 1 --interval 1d --region US

Is the data in ~/desktop/quant_engine/qlib_data/us_data your own generated data? You can check if the data in ~/desktop/quant_engine/qlib_data/us_data/instruments/all.txt is in an exception. Because from the error message you provided, it may be due to the existence of abnormal values in ~/desktop/quant_engine/qlib_data/us_data/instruments/all.txt.

Yes the data is newly generated by using the qlib yahoo collector for US data not from get_data. I found that the line that is bugging is line 572 in qlib/utils/init.py, which is
miss_code = set(pd.read_csv(_instrument, sep="\t", header=None).loc[:, 0].apply(str.lower)) - set(code_names)
The thing is somehow this part pd.read_csv(_instrument, sep="\t", header=None).loc[:, 0] is not identified as str but float. Therefore it fails to apply str.lower to this Series. I change it to pd.read_csv(_instrument, sep="\t", header=None).loc[:, 0].astype(str) then it works.

Is the data you are using self-generated? You can check the following instruments/all.txt for abnormal data. The data I downloaded using scripts/get_data and didn’t find the problem you describe.

The data is downloaded from Yahoo Finance by using the code provided in this link https://github.com/microsoft/qlib/tree/main/scripts/data_collector/yahoo#Automatic-update-of-daily-frequency-data
which is python collector.py download_data --source_dir ~/.qlib/stock_data/source/us_data --start 2020-01-01 --end 2020-12-31 --delay 1 --interval 1d --region US

Is the data in ~/desktop/quant_engine/qlib_data/us_data your own generated data? You can check if the data in ~/desktop/quant_engine/qlib_data/us_data/instruments/all.txt is in an exception. Because from the error message you provided, it may be due to the existence of abnormal values in ~/desktop/quant_engine/qlib_data/us_data/instruments/all.txt.

Yes the data is newly generated by using the qlib yahoo collector for US data not from get_data. I found that the line that is bugging is line 572 in qlib/utils/init.py, which is
miss_code = set(pd.read_csv(_instrument, sep="\t", header=None).loc[:, 0].apply(str.lower)) - set(code_names)
The thing is somehow this part pd.read_csv(_instrument, sep="\t", header=None).loc[:, 0] is not identified as str but float. Therefore it fails to apply str.lower to this Series. I change it to pd.read_csv(_instrument, sep="\t", header=None).loc[:, 0].astype(str) then it works.

Ok, very glad you solved the issue.


Allow scaling from an empty model

Possible usecase is setting up test data for a new app. Data structure will exist, but if you use the tool to generate a model from it, it will be empty (or close to empty). It would be interesting if we could say something like: generate --fill 10000 which would force fill the database with data up to 10000 records.
I can imagine some problems with this in the current implementation, however: characteristics could be wrong (does an empty table with a date allow positive or negative dates?) for example. Should do some thinking about this.

I still like this idea.
I don't think a mixture of --factor and --fill would make sense. Should validate for only one or the other.
Characteristics would fail, but we can apply smart defaults in case of a --fill on empty. The goal should always be testability. Worst case people can edit the config manually to get certain characteristics out of it.
For example: Any date is allowed (bigger ranger = more test scenarios)

I've added the --fill option. --fill takes precedence if --fill and --factor are used both. Required to be a positive value.
By doing --fill you can decide to set to a specific amount of rows.
Not yet tested properly on an empty model - as said there might be default characteristics that need to come into play then.


/vote is broken

Ben [9:40 AM]
Apparently /vote is broken
Shane Becker [12:29 PM]
what should /vote go to?
Ben [3:15 PM]
it’s a redirect to http://www.crimethinc.com/tools/vote
Shane Becker [3:17 PM]
what should it go to?
Ben [3:18 PM]
It should go to /tools/vote, which is an article called Democracy is Bankrupt. Where’d it go?
Shane Becker [3:18 PM]
tools/vote is not an article. tools/vote doesn’t exist.
[3:19]
are you saying that you want /vote to redirect to some article called “Democracy is Bankrupt”?
Ben [3:19 PM]
That’s where it went before the redesign broke /tools, so it seems like it should go there. Unless there’s somewhere better it should go…
Shane Becker [3:20 PM]
so. what is the URL of that article that you want it to redirect to?
Ben [3:21 PM]
lol, if i knew that i’d just make it so. but, as far as i know, the redesign broke /tools. i just found Democracy is Bankrupt through the Wayback Machine.
[3:21]
http://web.archive.org/web/20120501102822/www.crimethinc.com/tools/vote
new messages
Shane Becker [3:22 PM]
ok. will you create a github issue with all of this that you know about? and we’ll dig into it. please

Hello,
I try to grep the title or some setences in the seeds and i get nothing about this article. I try to find it with the website search bar and a found nothing too, so maybe the solution would be, after validation with the database content, to republish the article and assign it to the /vote url.

It looks like it didn't make it over in the site migration earlier this year. I'm manually adding it to the site now. Thanks for investigating this.

Fixed.
Added the article.
Redirected to https://crimethinc.com/2012/05/01/democracy-is-bankrupt-vote-here-stickers


[WIP] Impl conversion from v2::Psbt to v0::Psbt

Close #31
I implemented both From<raw::Key> and raw::Key::into_v0 in the first and second commits respectively. Let me know which design you think makes more sense, I tend to lean to the former but I wanted to show both to make a fully informed decision.

Hi @DanGould, either way is fine for me. I'm happy to merge and release this if you are using it but FYI I'm in the middle of re-writing a PSBTv2 crate from scratch that does not import all the bitcoin and miniscript code. I'm away traveling at the moment hacking on it, hopefully will have something ready soon. The API will be similar to whats here so it should be easy to drop in in place of this one.
If you want to look its here: https://github.com/tcharding/rust-psbt-v2
And on top of: https://github.com/rust-bitcoin/rust-bitcoin/pull/3424

is the idea to use primitives instead of the full bitcoin crate? Getting this merged is not urgent as I'm not using it but a downstream user asked for a way to do the conversion.

No, the psbt stuff will never go in primitives. The reason for my multiple attempts at this (I'm on the third crate now rust-psbt, rust-psbt-v0, and rust-psbt-v2) is that I wanted to totally remove all the code from rust-bitcoin (I've had two goes at this idea, this crate and rust-psbt-v0). But it seems this is not going to fly, so I've started of rust-psbt-v2 that doesn't import. And will hopefully just deprecate stuff in rust-bitcoin - time will tell.

I meant the opposite, that the PSBT crate depends only on primitives, and not rust-bitcoin

Woops, we are talking around each other. The psbt logic currently in bitcoin will likely stay in bitcoin but hopefully get dumber and this crate will be downstream of bitcoin. Does that make sense? The bitcoin::psbt::Psbt type will remain in bitcoin and not move into primitives.

yes that does make sense. This crate still needs to depend on primitives since it uses e.g. TxOut, right?


Unexpected behavior while deploying global service with label.

Rancher versions:
rancher/server: latest version
rancher/agent: v1.6.2
Docker version: (docker version,docker info preferred)
1.12.6
Operating system and kernel: (cat /etc/os-release, uname -r preferred)
Ubuntu 16.04.2 LTS (4.4.0)
Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
AWS
Setup details: (single node rancher vs. HA rancher, internal DB vs. external DB)
single node rancher
Environment Template: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
Pre- requisite:

Host A has label - io.rancher.scheduler.require_any="test1=value1, name1=value1"
Host B has label - io.rancher.scheduler.require_any="test1=value2, name2=value2" and hello1=value1
Host C has label - io.rancher.scheduler.require_any="test1=value1, name2=value2"
Host D has no labels.
Host E has label - io.rancher.scheduler.require_any="test1=value3"

Bug detail:

Global service with label="test1=value1" is being deployed on all hosts- Host A, B, C, D, E.
When new host-h1 with io.rancher.sheduler.require_any="test1=value2" is created the instance of global service is deployed there as well.
Once host-h2 without any label created, the instance of global service deployed there as well.

Expected Result:
Global service instances should deployed only in host A, C and D. Service should be in "Active" state. Once host h2 is available, new instance for the global service should not deployed in this host.
Actual Result:
Global service instance deployed on all the hosts- Host A, B, C, D, E, h1 and h2.
Steps to Reproduce

Fulfill prerequisites.
Deploy a Global service with label="test1=value1".
Global service instance gets deployed on all hosts- Host A,B,C,D,E whereas it should get deployed only in host A,C and D.
When new host-h1, h2 created global service instance deployed there as well.

Please let us know in a comment if you can still reproduce the issue, and we'll reopen it


Delete unused Layout.svelte, changed to i++ for readability

Signed-off-by: Marcel Schöckel<EMAIL_ADDRESS>

Two more open comments in the original review :)


Added local openshift cluster files to gitignore

@robshelly this folder is created when you use oc 3.10, right?

@kornys Yeah it's created in the working directory by oc cluster up when using Openshift 3.10.
It appears to store cluster config there so that you can run cluster down and then cluster up again and still have your projects.


Can not find the corresponding model file

Excuse me. I would like to check the effectiveness on the datasets I get by running the code in github. However,  the necessary models, such as DMR and InternLM2-7B, are unknown. Could you please give the model file or the download link. Thank you for your help.

hi, the DMR model can be found at https://huggingface.co/KaiLv/dmr-zh and https://huggingface.co/KaiLv/dmr-en. The InternLM2-7B model is at https://huggingface.co/internlm/internlm2-7b.


Black screen in video call when resume

Getting a black screen when sending the app in background and resuming again.
I've referred the same Camera file that has been provided in the repo

@gitanshubatra239, thanks for letting us know about the issue.
Some key details are left out, however, which makes root cause difficult.  I'm going to close this.  Can you please refile this issue and answer the questions in the template?  That'll help us out a lot, because it'll provide critical information.  Thanks!


track weight of a suit

Maintain a weight value for each suit in a hand. Assign each tile a weight property and add or subtract the weight of the added/removed tiles whenever the suit changes. This way the weight calculation can be done in very few instructions.

Not necessary with the current setup.


Modified project POM so it defines all dependencies and build a single jar for execution.

I made some modifications to the POM for this project to improve the experience for users that want to build it using maven, and also to have the maven build generate a single JAR that contains all dependencies, rather than having to deal with copying multiple JAR dependencies around.

+1 on merging this. Having to manually download dependencies and stick them in ./lib doesn't make any sense. I tried doing this myself but ran into problems because this doesn't build against latest version of the Okta SDK for Java (version 0.7.0). Looks like it needs an ancient version. It would be great to have a project that can be checked out and easily built with Maven. I ended up forking the project and manually applying this patch to be able to use it.

Merging this in as it sounds like this patch is production ready. Thank youl


Fix #1456, Rename CFE_SB_RemovePipeCallback_t to ...backArgs_t

Checklist

[x] I reviewed the Contributing Guide.
[x] I signed and emailed the appropriate Contributor License Agreement to<EMAIL_ADDRESS>and copied<EMAIL_ADDRESS>
Describe the contribution
Fixes #1456
Renames CFE_SB_RemovePipeCallback_t to CFE_SB_RemovePipeCallbackArgs_t, which better matches what the struct represents.
Only used locally in 2 functions.
Testing performed
GitHub CI actions (incl. Build + Run, Unit Tests etc.) all passing successfully.
Expected behavior changes
No impact on behavior.
Contributor Info
Avi Weiss @thnkslprpt

Looks good, but also something we should consider documenting in https://github.com/nasa/cFE/blob/main/docs/cFS_IdentifierNamingConvention.md as well (given that names are almost always subjective, if we are going to be doing PRs to fix names then we should have something to fall back on that says what is "right")

Good point - I forgot to update that doc. Will do so today.


Implement wasi-runtime-config

Feature
The wasi-runtime-config API has entered Phase 2, I think we can start implementing it.
Benefit
For users, the env API from wasi-cli can currently be used to achieve similar functionality. However, from a semantic standpoint, some configuration items that the runtime wants to pass to the user should be implemented through the config API.
Implementation
Because the wasi-runtime-config API is very simple, its implementation will be quick. However, there is one issue: I'm not sure whether this API should be merged into the current wasi crate or if we should create a separate wasi-runtime-config crate like wasi-http. The current wasi crate essentially only implements the wasi-cli API, so I'm uncertain how we should handle new wasi APIs, eg: wasi-runtime-config or wasi-keyvalue, etc.
If this proposal is accepted, I would be happy to implement this API.
cc @alexcrichton

Yeah, thanks for the help, I'll start implementing it soon.


Hi, could you point out which files to use for reproducing you experiment result?

I found that there are many files in Real Toxicity Prompts Dataset and I would like to know which file was used in your experiments, thanks!

Hi @algoflow19, for the self-diagnosis experiments, we used the file \realtoxicityprompts-data\generations\prompted\prompted_gens_gpt2.jsonl to get texts generated by GPT2. For self-debiasing, we used realtoxicityprompts-data\prompts.jsonl, but we filtered out all prompts where challenging == False.

Thanks!


Helm ls is switching working directory

Hey,
first of all, thank you for the lang server, this is really helpful if you start on a new helm Project.
Improvement
Setting the root_dir of the lang server to util.find_git_ancestor as in the yamlls to prevent switching of the working directory.
Reason
As my helm chart is a part of the operator and will be generated by a makefile it's kind of getting annoying that the working directory is changing if I check the output of the templates.
Information
I searched in the code and also some other references and found out the some lang server let's you overwrite this. Is this also doable for helm-ls? Or have I overseen something?

Hi, this is configured in the nvim-lspconfig repo: https://github.com/neovim/nvim-lspconfig/blob/master/lua/lspconfig/server_configurations/helm_ls.lua#L15
But you should be able to easily overwrite it in your nvim config with something like this:
-- setup helm-ls
lspconfig.helm_ls.setup {
  root_dir = util.find_git_ancestor,
  settings = {
    ['helm-ls'] = {
      yamlls = {
        path = "yaml-language-server",
      }
    }
  }
}


example "babi_rnn.py" not work

The dimension mismatch is detected in below.
line183: sentrnn.add(Embedding(vocab_size, EMBED_HIDDEN_SIZE, mask_zero=True))
I think not "vocab_size" but "story_maxlen". And line187 is same.

Definitely does work. Maybe try to sync your version of Keras with the repo (master).


:binding options do not apply when the form has empty body

For example,  for
(let [a :a b :b c "really really long string"])

The options :binding {:force-nl? true :flow? true :indent 0 :nl-separator? true} have no effect at all.
But if the form is
(let [a :a b :b c "really really long string"] a)

instead, the options apply

Yes, that was by design.  I would guess that you would like the binding options to apply even if there is no body, or you wouldn't have filed an issue.  I'll see what I can do about changing it to consider a two-element list a :binding form.

Thanks a lot. It is indeed important for some DSLs that use this kind of two-element binding forms extensively.

I have implemented this, and it will be in the next release, which will probably be early next year.  The rest of this year is looking pretty busy.  I'll close this issue when I release it so you will know.

Great! Thanks. Have a great holidays!


How to deal with great amount data using keras? Is there any simple and efficient way to deal with io problem?

If I want to use keras to deal with thousand hours of speech data or over ten thousands of pictures, is there any way to deal with it efficiently?

The best way is to write a data generator and use the fit_generator training method of models. This means you can stream the data from disk, rather than loading it all into memory.