echo $FOO not working

I'm trying to use cmd-env to help templatize my aws calls from yarn but I'm not able to get the variables...
for example
npx env-cmd -e production echo $FOO returns nothing when I'd expect it to return BAR
but npx env-cmd -e production printenv FOO returns BAR
How can I access to the env vars so I can pipe them into other commands as parameters?

The only solution I have as of now is to do something like so:
echo $(npx env-cmd -e production printenv FOO)

but as you can imagine if there are multiple variables I need, this command gets really long

see response here: https://github.com/toddbluhm/env-cmd/issues/91#issuecomment-548672584

I have published 10.1.0 that now includes support for expanding env vars in arguments using the -x flag and the format $var.

npx env-cmd -x --use-shell 'echo $FOO' still doesn’t seem to be working with version 10.1.0.
Is this expected?


Juniper structured throwing error

Deployment Type
Docker
Version
v2.0.4
Steps to Reproduce
When using structured on Juniper for show bgp route I am getting back
rt, 0, rt_entry, 0, peerAs
When I set structured to false it works fine. (log attached)
Also I noticed that if I set structured as false I see 2 versions of BGP route in the drop down, one does the non xml command, one does the xml command. I assume that is a bug of some sort (image attached of that)
debug.txt

Expected Behavior
router to produce expected results
Observed Behavior
router did not product expected results
Configuration
org_name: redacted
plugins: []
primary_asn: redacted
request_timeout: 15
site_description: redacted Looking Glass
site_title: redacted Looking Glass

web:
    location_display_mode: dropdown
    text:
        title_mode: logo_only
    logo:
         light: /etc/hyperglass/static/custom/light.png
         dark: /etc/hyperglass/static/custom/dark.png
         favicon: /etc/hyperglass/static/custom/fav.png
         width: 50%
         height: null
    theme:
         default_color_mode: dark

structured:
    rpki:
        mode: external

Devices
- name: Router
    group: North Central
    address: x.x.1.100
    credential: *credential1
    platform: juniper_junos
    attrs: *attr1
    directives:
        - builtins: [bgp_route, traceroute, ping]

Logs
attached

looked into this error a bit more. It seems like on my Juniper installs the active route does not display the parameters for peer-as and local-as. It does show them for all the other inactive routes though. not sure what the fix would bee though. I am am not sure if this has to do with the fact we are using reflectors or if the the issue has to do with certain juniper code versions missing those parameters

Worked on this a bit tonight and did a workaround for now and it seems to work properly
edited the juniper parser within the docker container
-vi /opt/hyperglass/hyperglass/parsing/juniper.py
-change the following lines to look like the following
peer_as: int = 0
source_as: int = OUR AS NUMBER
-type in exit
-Get docker container ID
sudo docker ps -a
copy container ID for hyperglass-hyperglass
-commit docker changes
sudo docker commit  hyperglass-hyperglass
-restart service


remove version keyword argument, fix #1

Thank you. Yet it should rather be done with action='version' for both Py2 and 3.

thank you for the iniciative! I made a pull request just removing the, fell free to reject it and fix it properly.
PS: some argumment to generate migrations only for specific versions of django would be nice!

Year passed, fix released %)


Implement Builder::connect_signals_full

This is a safe way to implement builder signal connection, as discussed in #707.
Closes #707.
cc @sdroege

Looks all good to me

@sfanxiang Thanks, please, update generated files

Good to go for me otherwise. I assume you tested that it actually works and can be used? :) Maybe worth adding an example to the examples repo?

@sdroege

I assume you tested that it actually works and can be used? :) Maybe worth adding an example to the examples repo?

This example builds and works. Does it suffice?

On 20 July 2019 10:35:07 EEST, Xiang Fan<EMAIL_ADDRESS>wrote:

@sdroege

I assume you tested that it actually works and can be used? :) Maybe
worth adding an example to the examples repo?

This
example
builds and works. Does it suffice?

I guess so :) can you send a PR for that against the gtk3 examples too? Shouldn't need any code changes
In any case, this PR is good to go for me.
Unrelated, did you merge back any changes that happened in the gtk3 versions of the crates into the gtk4 versions since you started? Should do that before the first release in any case.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

@GuillaumeGomez let's get this in?


:four_leaf_clover: Proposal: Use Validator for Config Validation

What would you like to add? Why is this needed?
Background
Our community member @iyear introduced https://github.com/go-playground/validator into the project in this issue https://github.com/devstream-io/devstream/issues/511 (solved by this PR https://github.com/devstream-io/devstream/pull/533). This has greatly improved our plugin options validation.
However, the configloader module still uses manual validation: https://github.com/devstream-io/devstream/blob/main/internal/pkg/configloader/validation.go
Improvement
We can update the configloader's validation method to use the same validator mechanism.
It's worth noting that the logic here https://github.com/devstream-io/devstream/blob/main/internal/pkg/configloader/validation.go#L93 is a little complicated; we can implement it by something like this https://github.com/iyear/devstream/blob/9ec0591cc9a3b609b0d302d16cd6246c6119c606/internal/pkg/plugin/common/reposcaffolding/options.go#L11.

You may need to use rhese validations: https://github.com/go-playground/validator#other

@iyear Thank you for your helpful information! You must be the next community member this month!

configloader has been refactored, as can be seen in #655. So some of the links above are no longer valid, but don't worry, the configloader is now much more readable and you can easily find where the validation logic is in this package. Please don't worry, feel free to leave a comment and let us know if you encounter any problems.

[WeOpen Star]I would like to help


cannot import sketch_rnn model

I installed magenta with the automated installation script:
curl https://raw.githubusercontent.com/tensorflow/magenta/master/magenta/tools/magenta-install.sh > /tmp/magenta-install.sh
bash /tmp/magenta-install.sh

After source activate magenta here's what I get:
>>> from magenta.models import sketch_rnn
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: cannot import name sketch_rnn

However, I can import other models, e.g., from magenta.models import rl_tuner works just fine.
(Though I have the same problem with importing nsynth.)

Sorry about that. We hadn't yet updated the pip package to include sketch_rnn. It should be available now if you upgrade to the latest version (pip install -U magenta).


Graphite server crash due to memory leak

Hi,
Graphite node continuously crashes after some queries due to memory leak. My configuration include 1 carbon-relay instance and 2 carbon-caches. I have increased the FETCH_TIMEOUT and FIND_TIMEOUT in local_settings.py to 600 and 300 sec respectively.
VM specs are 6vcpus and 8GB RAM.
Some of the sample queries are:
aliasSub(summarize(nPercentile(icinga2.*.services.interface*.*interface*.perfdata.*out_bps.value,90), '1y', 'max', 'false'), '(.*)icinga2.(.*).services.*.perfdata.(.*)(in|out)_bps.*', 'Node  (\2) Interface (\3)')
aliasSub(highestCurrent(summarize(icinga2.*.services.interface*.interface-dual.perfdata.*in_prct.value, '1y', 'average', 'true'), 25) , '(.*)icinga2.(.*).services.*.perfdata.(.*)_in_prct.*', 'Node (\2) Interface (\3)')

Any help would be appreciated.
Thanks,

Are you sure it is a leak, not just using a lot of memory?

That's probably not a leak, Graphite requires RAM to cache data. You can limit cache size in carbon.conf, by default, it's Inf.
On the other hand, that probably will increase disk load even more. Unfortunately, you  need to make some experiments to properly tune it.
Maybe you need just bigger server or you can try to replace carbon-relay and 2 carbon-caches with single go-carbon instance - but usually, it does not help with RAM consumption, but with CPU load.

I have increased the RAM from 8GB to 16GB, now memory issue is resolved but all CPUs are showing 100% utilization when i query the graphite server.

If you want to improve your performance I can suggest you to tune your storage-schemas.conf. You summarize with interval "1y", so you could use a wide grained archive. Storing less metrics can improves retrieval performance a lot. Less data needs to be fetched, less memory needed and less cpu cycles for processing the data. The downside is that storing the metrics will be heavier. Don't forget to resize existing wsp files after you change storage-schames.conf.
Other than that "100% CPU usage" does not have to be a bad thing, at least you are using your hardware ;)


[KYUUBI #4197][DOCS] Fix typo in a title of the Flink FTS Connector

Why are the changes needed?

How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[x] Run test locally before make a pull request

thanks, merged to master and branch-1.6.


Update JS dependencies

This is the result of make npm-update js css.

Codecov Report

Merging #8051 into master will decrease coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #8051      +/-   ##
==========================================
- Coverage   41.59%   41.58%   -0.01%
==========================================
  Files         480      480
  Lines       64144    64144
==========================================
- Hits        26678    26675       -3
- Misses      34009    34011       +2
- Partials     3457     3458       +1

Impacted Files
Coverage Δ

modules/avatar/avatar.go
48% <0%> (-6%)
:arrow_down:

models/gpg_key.go
55.83% <0%> (-0.84%)
:arrow_down:

modules/process/manager.go
81.15% <0%> (+4.34%)
:arrow_up:

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 5fc93b4...0c188c2. Read the comment docs.


Customizable loot filters

Allow users to select and customize a number of filters. Only show loot that passes all of the filters.

Item quality: "don't show poor quality items"
Item name: "don't show any items with 'Murloc' in the name"
Lower iLvl than Equipped in slot
Armor/Weapon Class: "don't show soulbound items that I can't equip"

More ideas to come I'm sure.
 Maybe if the addon reaches > 1M downloads 😅

Comparing Weapons (2 handed staff vs main-hand/off-hand) and "Equipability" (Warriors prefer Plate but can wear anything, figuring out class or spec restrictions on gear, primary stats, etc.) make this a bit more challenging than I'm ready to deal with right now. I think item quality filters will be the most commonly used. The name filter is pretty niche. The other two filter ideas could be useful, but I'm going to draw the line at quality filters for now.


Dynamic Batching

Hello, dear developers, I did not find the relevant code about Dynamic Batching_size technology in the source code?If so, please reply, thanks

I focus on this project from their paper,I think some features like batching are not implemented.
These days,I look back this project,I think we can follow their ideas to implement these features by ourselves.

I  found 'batch_size' in build_and_deploy_model function.
If the default value of -1 is used, Clipper will adaptively calculate the batch size
But I couldn't find infomations about model selecction layer.


NOISSUE - Add docker-compose for MQTT cluster

Pull request title should be MF-XXX - description or NOISSUE - description where XXX is ID of issue that this PR relate to.
Please review the CONTRIBUTING.md file for detailed contributing guidelines.
What does this do?
Introduces docker-compose files for MQTT cluster. Also, modifies nginx.conf to improve performance.
Which issue(s) does this PR fix/relate to?
Put here Resolves #XXX to auto-close the issue that your PR fixes (if such)
List any changes that modify/break current functionality
nginx.conf files have been changed, and this demands testing
Have you included tests for your changes?
Did you document any new/modified functionality?
Notes

Codecov Report

Merging #841 into master will decrease coverage by 0.04%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #841      +/-   ##
==========================================
- Coverage   85.58%   85.53%   -0.05%
==========================================
  Files          72       72
  Lines        4702     4702
==========================================
- Hits         4024     4022       -2
- Misses        442      444       +2
  Partials      236      236

Impacted Files
Coverage Δ

things/service.go
86.61% <0%> (-1.41%)
:arrow_down:

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 115d94b...e508333. Read the comment docs.

WIP label removed
:warning: Please pull the branch and test on your machines.
This PR tries to move as much as possible of mutual nginx.conf code into the snippets, also introduce cluster support.
Additionally, in entrypoint.sh environment (read from .env) is substituted in nginx.conf, so proxy URLs are not hadrcoded any more.
docker-compose.yaml is broken in several files, as Aedes is pulled out in aedes.yaml so it can be replaced with verne.yaml. Additionally, verne-cluster.yaml can be used instead (which will pull and setup correct nginx.conf).


Fixed in-page link anchor to Seed Data heading

Omiting details as this is just a PR for a small fix rather than for including a resource.

@tomatic Thanks for the fix.


0.4.5 fixes after testing

update to emit 0.4.10
fix typo for receive address text when doing bitcoin address verification
make last 13 in tx verify screen monospace and fix
make screensaver work on animated qr screens
fix long password run off display. Handles up to 80 characters now.

Thank you Nick!


dataset split error

When trying to use the "split_dataset" function in controller.py, the function seems to pass the wrong information to the template and it will cause the pipeline to generate "nan" lines instead of removing them.
The error happened with the dataset 66(66_chlorineConcentration). The generated result after "Denormalize" primitive and "DatasetToDataframe" primitive would be look like this:

Such error won't happened if not using this function. The normal generated result would look like as:

solved


fix: double pressing CTR+K removes focus

Details

This PR updates the keyboard shortcuts such that they dispatch the navigation action only if the user is currently on a different page than what the shortcut is meant to redirect to. Contrary to the main approach in the proposal, it turns out that preventing the navigation in Navigation.navigate function broke the navigation from home to report screen on mobile. As such, I prevented the navigation in the listeners themselves.
The PR also involves fixing the getActiveRoute function in the lib/Navigation/Navigation.js library. The functioned returned incorrect active route when the keyboard shortcut was pressed for the first time.
Prior to this fix, the getActiveRoute function returned the following when pressing CMD+K twice:
/?initial=true&screen=Search_Root&path=%2Fsearch

After the changes:
/search

Fixed Issues

$ https://github.com/Expensify/App/issues/17482
PROPOSAL: https://github.com/Expensify/App/issues/17482#issuecomment-1517373103
Tests

Open the app on web chrome or web safari
Click CTRL+K to open search page
Again click CTRL+K and verify that focus is not lost from search box
Repeat step 2 and 3 with CTRL+Shift+K

Verify that the auto focused field does remain focused after repeating the keyboard shortcut

[x] Verify that no errors appear in the JS console

Offline tests

N/A
QA Steps

Open the app on web chrome or web safari
Click CTRL+K to open search page
Again click CTRL+K and verify that focus is not lost from search box
Repeat step 2 and 3 with CTRL+Shift+K

Verify that the auto focused field does remain focused after repeating the keyboard shortcut

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

 If you have the K2 extension, you can simply click: [this button]

@mananjadhav let me know when you get a chance to complete the checklist

and observe that focus is lost from search box

@allroundexperts Small correction in the Test Steps pt.3, Verify that the focus is not lost from the search box. Rest it works well, finishing the checklist now.

Thanks for the update @allroundexperts. @luacmartins All done.

🚀 Deployed to staging by https://github.com/luacmartins in version: 1.3.8-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/marcaaron in version: 1.3.8-8 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


TestDoubles (unopionated CppUMock)

see README_TestDoubles.md.
This implementation wraps the current CppUMock behavior using a more expressive grammar (tail recursion by type).
The CppUTestExt/Test_TestDouble.cpp demonstrates that this grammar can be used for call matching, parameter matching, output matching, and return values.
The README_TestDoubles.md identifies where the TestDouble design doesn't match the semantics of CppUMock.  I'd like to coordinate on how to go forward (i.e. make CppUMock less opinionated, or fork into a separate semantic).
FIXMEs:

TestDouble classes expect C++ move semantics.  Instead, explicit move semantics can be used to reduce the copying of SimpleString.
Expectations should be expressed as a set.  The CppUMock semantics enforce sequence of expectations when matching the actual (based on the assumption of matching all actual).

Coverage increased (+0.002%) to 99.88% when pulling 971b181220e97ed88e757e0c66fea41694247805 on redengin:master into 43ad9dca1ff0230e213d78bcf8f5a9bc3568638d on cpputest:master.

Thanks for the pull request. This will need quite a lot of work before I will integrate this within the code. However, I read the tests and I couldn't really understand what you are trying to achieve over the current CppUMock?

@basvodde the current implementation just wraps CppUMock so the only value added is a more expressive grammar.  The TestDouble grammar separates expectations from actual calls to eliminate the common syntax error I've seen where developers mistakenly use mock().expectOneCall() inside the Mock (instead of mock().actualCall()).
My objective of this pull request is to make you aware of the TestDouble design (see README_TestDoubles.md).  This pull request demonstrates that the TestDouble grammar will behave equivalently to CppUMock.
To realize the TestDouble design, I'd like to coordinate with you to determine whether CppUMock should be the underlying implementation for TestDouble or if TestDouble should implement its own expectation framework based on the CppUMock code base.  The primary difference is that the TestDouble framework only opines on the cardinality of expectations if the expectation explicitly describes .times() (otherwise the expectation services all actual calls).  The other change is to allow an expectation to inject a function (.use()) to handle behavior rather than require the mocked method to implement model behavior.

Ok. Not quite sure why it is more expressive than the current Mock interface. Implementation wise, it seems to use templates a lot, which are avoided within CppUTest. That will likely make it hard to integrate and will definitively prevent it from being a standard interface.

@coveralls @basvodde  @jwgrenning
is there a way to run CI checks locally (so I don't have to push commits to test)?

The ci runs mostly make test_all

@basvodde I'm interested in why templates are avoided.  If necessary I'm happy to explicitly define each invocation based on your guidance - (i.e. I'm guessing you don't want a macro function that implements template functionality).

@basvodde
The CI contexts I want to run locally are:

continuous-integration/travis-ci/pr
continuous-integration/appveyor/pr
coverage/coveralls

To get continuous-integration/travis-ci/pr I'm not sure how to initialize a pointer.  Clang doesn't like 0 as a reference to nullptr, but nullptr is only provided by C++11 and therefore can't be used per CppUTest compile options.
using a static_cast<void*>(0) to fake nullptr

re templates. We avoid them as we want to be as safe as possible for old and embedded compilers. Hence, templates (with a few exceptions which are put under #ifdef) are not used.

Don't think you can run the CI local. Sorry about that.

@basvodde  I've finally passed CI, what next? (this is only a prototype, it's not ready to merge to master)
The current implementation of TestDouble is a prototype to demonstrate that the grammar of using TestDouble is largely equivalent to CppUMock grammar.  How can we share ideas about the grammar (i.e. call semantics)?
As there is already a large body of users of CppUMock, I don't expect that TestDouble would replace CppUMock, but rather the two can leverage a common Expectation Framework (e.g. a generalized store of expectations which both implementations can query).
You've identified that their are additional coding standards (e.g. not using C++ templates).

README_TestDoubles.md lays out how CppUTest can support familiar API's (mockito, gtest/gmock).  I'm fine with dropping this pull request.  My next pull request will be replacing the common functionality between CppUMock and TestDoubles with a new base class.

working on new implementation

Ok. I'm still not sure what you are trying to achieve and am not very likely to merge it, but I'm curious and open to be convinced differently.

The design is described in README_TestDoubles.md.  Let me know what you think.


Phishing detected

Hello team,
We just released our platform -https://node-hub.net/
When I activate your plugin and try to reach it I get this message:
Phishing detected
You have been redirected because the Polkadot{.js} extension believes that this website could compromise the security of your accounts and your tokens.
https://node-hub.net/
Note that this website was reported on a community-driven, curated list. It might be incomplete or inaccurate. If you think that this website was flagged incorrectly, please open an issue by clicking here.
Our platform is 100% and I don't believe anyone reported it at all. Anyway, can you please remove it from your list or check what is causing this issue and fix it?
Thanks team!
Greetings,
V

I need to access https://node-hub.net/ and my Polkadot extension is blocking it.

Could you share more information about that "project" with us? Nothing in that site is working, just the "connect wallet" button.

Hello Frank.
The project is about the HyperCycle token (HYPC) and is related to the
Cryptopia VC community. The said site give us the possibility to manage our
nodes. They give the power to AI computing and blockchain synergy.
Best regards,
Curty
Em sáb., 16 de dez. de 2023 às 17:22, Frank @.***>
escreveu:

Could you share more information about that "project" with us? Nothing in
that site is working, just the "connect wallet" button.
—
Reply to this email directly, view it on GitHub
https://github.com/polkadot-js/phishing/issues/4099#issuecomment-1858923042,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMPICIBD3FSKPHVMV43PW5TYJX7HTAVCNFSM6AAAAABAWDFDHCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJYHEZDGMBUGI
.
You are receiving this because you commented.Message ID:
@.***>

Can you share with us any official site from HyperCycle mentioning your project?

Hello @frankywild!
This is an article from HyperCycle medium, announcing Cryptopia as the official node distributor:
https://medium.com/hypercycle/official-node-distributor-announcement-cryptopia-group-3c6908797d9d
This is a post from Hypercycle's official X account stating that Cryptopia is building a monitoring platform:
https://x.com/Hypercycle_AI/status/1735400431357218936?s=20
This is Cryptopia's official Discord server. You can join it to read the discussions about the NodeHub platform:
https://discord.com/invite/cryptopia-group


Is focusedInput requred for DateRangePicker

I can't find any place in documentation that states focusedInput prop is required but when I don't add this prop date picker is not visible after clicking input.
I have to dive into examples to finally see that https://github.com/airbnb/react-dates/blob/master/examples/DateRangePickerWrapper.jsx sets this prop.

Good call. We should probably indicate in the README that this is the case (and the examples folder is a great place to look for how to set up your initial code!). Thanks for highlighting this.

The README should make this information more clear now.


Crashes during parsing of malformed OSMX files

Hi there,
During fuzz testing of the OSMX parsing there were a couple crashes discovered. Although these files only crash the apps, they could potentially be crafted further into security issues where a malformed OSMX file would be able compromise the process's memory through memory corruption, so hardening the code to prevent these kinds of bugs would be great.
You can download the crashing files in a zip from Ufile to debug and understand where the code is crashing.
Here's a snip of one of the crash logs.
Program received signal SIGSEGV, Segmentation fault.
mdb_xcursor_init1 (mc=0x7fffffffdd00, node=0x7efff767ffda) at mdb.c:7507
7507			mx->mx_db.md_pad = 0;

#0  mdb_xcursor_init1 (mc=0x7fffffffdd00, node=0x7efff767ffda) at mdb.c:7507
#1  mdb_cursor_set (mc=0x7fffffffdd00, key=0x7fffffffe0b0,
    data=0x7fffffffe0a0, op=MDB_SET, exactp=0x7fffffffdcfc) at mdb.c:6142
#2  0x00000000005aceb5 in mdb_get (txn=<optimized out>, dbi=<optimized out>,
    key=0x7fffffffe0b0, data=0x7fffffffe0a0) at mdb.c:5762
#3  0x000000000040fb30 in osmx::db::Metadata::get(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) ()
#4  0x000000000040da0b in main ()

rax            0x0                 0
rbx            0x7fffffffdd00<PHONE_NUMBER>46368
rcx            0x7efff767ffff<PHONE_NUMBER>48351
rdx            0x1d                29
rsi            0x1000000000000<PHONE_NUMBER>10656
rdi            0x7efff767ffda<PHONE_NUMBER>48314
rbp            0x7fffffffdcfc      0x7fffffffdcfc
rsp            0x7fffffffdc90      0x7fffffffdc90
r8             0x7fffffffdcfc<PHONE_NUMBER>46364
r9             0x6c9a73            7117427
r10            0x6c9828            7116840
r11            0x7ffff7872be0<PHONE_NUMBER>18976
r12            0x7fffffffe0b0<PHONE_NUMBER>47312
r13            0x7efff767f000<PHONE_NUMBER>44256
r14            0xf                 15
r15            0x7fffffffe0a0<PHONE_NUMBER>47296
rip            0x5ad1ba            0x5ad1ba <mdb_cursor_set+762>
eflags         0x10206             [ PF IF RF ]
cs             0x33                51
ss             0x2b                43
ds             0x0                 0
es             0x0                 0
fs             0x0                 0
gs             0x0                 0

=> 0x5ad1ba <mdb_cursor_set+762>:	mov    %rsi,0x188(%rax)
   0x5ad1c1 <mdb_cursor_set+769>:
    movaps 0x9aa78(%rip),%xmm0        # 0x647c40
   0x5ad1c8 <mdb_cursor_set+776>:	movups %xmm0,0x190(%rax)
   0x5ad1cf <mdb_cursor_set+783>:	movq   $0x0,0x1a0(%rax)

'exploitable' version 1.32
Linux ubuntu 5.4.0-48-generic #52-Ubuntu SMP Thu Sep 10 10:58:49 UTC 2020 x86_64
Signal si_signo: 11 Signal si_addr: 392
Nearby code:
   0x00000000005ad19e <+734>:	jne    0x5ad284 <mdb_cursor_set+964>
   0x00000000005ad1a4 <+740>:	movzx  edx,WORD PTR [rdi+0x6]
   0x00000000005ad1a8 <+744>:	lea    rcx,[rdi+rdx*1]
   0x00000000005ad1ac <+748>:	add    rcx,0x8
   0x00000000005ad1b0 <+752>:	movabs rsi,0x1000000000000
=> 0x00000000005ad1ba <+762>:	mov    QWORD PTR [rax+0x188],rsi
   0x00000000005ad1c1 <+769>:	movaps xmm0,XMMWORD PTR [rip+0x9aa78]        # 0x647c40
   0x00000000005ad1c8 <+776>:	movups XMMWORD PTR [rax+0x190],xmm0
   0x00000000005ad1cf <+783>:	mov    QWORD PTR [rax+0x1a0],0x0
   0x00000000005ad1da <+794>:	movzx  esi,WORD PTR [rdi+rdx*1+0x14]

Stack trace:
#  0 mdb_xcursor_init1 at 0x5ad1ba in OSMExpress/osmx
#  1 mdb_cursor_set at 0x5ad1ba in OSMExpress/osmx
#  2 mdb_get at 0x5aceb5 in OSMExpress/osmx
#  3 osmx::db::Metadata::get(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) at 0x40fb30 in OSMExpress/osmx
#  4 main at 0x40da0b in OSMExpress/osmx

Faulting frame: #  0 mdb_xcursor_init1 at 0x5ad1ba in OSMExpress/osmx
Description: Access violation near NULL on destination operand
Short description: DestAvNearNull (15/22)
Hash: 474dceedaab021c3f42b9dc0bd4ed041.474dceedaab021c3f42b9dc0bd4ed041
Exploitability Classification: PROBABLY_EXPLOITABLE
Explanation: The target crashed on an access violation at an address matching the destination operand of the instruction. This likely indicates a write access violation, which means the attacker may control write address and/or value. However, it there is a chance it could be a NULL dereference.
Other tags: AccessViolation (21/22)

Thanks!

@retpoline running osmx on untrusted .osmx file input seems like a nonstandard use case. Can you explain how the fuzz tester works? Considering an .osmx file is just an LMDB database, it seems like this parsing issue is relevant to any LMDB database? https://bugs.openldap.org/buglist.cgi?component=liblmdb&product=LMDB&resolution=---

@bdon thanks for looking into this.
Well, in general file parsers should not crash on malformed filed and ideally should handle error conditions that would otherwise cause them to crash gracefully instead. The fuzz testing performed was to check if the parser would handle invalid files or crash when parsing them.
As far as parsing an untrusted file as a nonstandard use case, I'd say although osmx files are different file types than doc, jpeg or other types of files, we still expect to be able to open a word document and if it contains errors, Word says eg. "Invalid file content" instead of crashing or allowing the file contents to dictate control over process memory. So that's why its a good idea to fix crashes in such scenarios.
Hmm other parses that operate on LMDB databases may crash on malformed input as well and if so, should be hardened to gracefully exit with an error message instead of allowing memory to get corrupted as well.


pyarrow is a dependency but is not in install_requires

Describe the problem

The source comes from this file: https://github.com/modin-project/modin/blob/master/modin/experimental/engines/pyarrow_on_ray/io.py#L4-L5
Source code / logs

This has resurfaced. There is some experimental code which relies on pyarrow


target overrides should check whether the override chain has the same metadata

Based on my understanding when specifying a target in nets.ts, it only swaps out the connection and not the "chain rune".. i.e. westend does not become westendDev. So whatever extrinsics are created will use the original metadata regardless of what the metadata is on the target chain. If there's a runtime upgrade on the prod chain and you don't bump the version in bins, then your extrinsics can seemingly fail, without it being obvious to the end user why its failing.
For example given this nets config:
import { bins, net } from "capi/nets"

const bin = bins({
  polkadot: ["polkadot-fast", "v0.9.43"],
})

export const westendDev = net.dev({
  bin: bin.polkadot,
  chain: "westend-dev",
})

export const westend = net.ws({
  url: "wss://westend-rpc.polkadot.io/",
  targets: { dev: westendDev },
})

Had i used anything lower than v0.9.43, extrinsics would fail with:
Unhandled promise rejection Unhandled {
  value: ServerError: Invalid Transaction
    at RunMap.fn (http://localhost:1234/index.b7a05eb9.js:24333:36)
    at RunMap._evaluate (http://localhost:1234/index.b7a05eb9.js:23114:44)
    from execution of the ValueRune instantiated
        at new Rune (http://localhost:1234/index.b7a05eb9.js:22321:23)
        at new ValueRune (http://localhost:1234/index.b7a05eb9.js:22997:1)
        at Function.new (http://localhost:1234/index.b7a05eb9.js:22999:16)
        at ValueRune.map (http://localhost:1234/index.b7a05eb9.js:23002:29)
        at ConnectionRune.subscribe (http://localhost:1234/index.b7a05eb9.js:24332:177)
        at RunMap.fn (http://localhost:1234/index.b7a05eb9.js:24725:60)
        at RunMap._evaluate (http://localhost:1234/index.b7a05eb9.js:23114:44)
        from execution of the ValueRune instantiated
            at new Rune (http://localhost:1234/index.b7a05eb9.js:22321:23)
            at new ValueRune (http://localhost:1234/index.b7a05eb9.js:22997:1)
            at Function.new (http://localhost:1234/index.b7a05eb9.js:22999:16)
            at ValueRune.map (http://localhost:1234/index.b7a05eb9.js:23002:29)
            at SignedExtrinsicRune.sent (http://localhost:1234/index.b7a05eb9.js:24725:27)
            at transferDev (http://localhost:1234/index.b7a05eb9.js:653:13)

Similar to #961, #1052.
Ideally Capi should have a check in place to make sure the target chain is compatible with the prod chain.

#925 also mentioned

This would also open the door for us to validate prod-dev chain feature parity. We could produce console warnings about inconsistencies between the default and target-listed metadata.

so this issue should be seen as a follow up

Currently, specifying --target does not actually touch the codegen; it passes an env var, which is picked up by the detectConnect util. Although we could swap out the served chain rune, this could be treacherous for a few reasons:

cached code would frequently change / become invalid
extra codegen (for every target)
in Node projects, we'd need to write to chains' respective node modules (which could be stored in different places depending on the package manager)

Would warnings about incompatibilities suffice? Not sure we should try to do anything too fancy with --target.

Warnings seem like the best option 👍


Version 2.0.0

Landed in https://github.com/metarhia/Example/commit/7bf558966af31a4e31afcc3f674aeb217baac91d


Error: Unable to resolve action raulanatol/jest-coverage-comment-action@v1

Hi @ethanneff, could you test with the last version 1.1.1?
uses<EMAIL_ADDRESS>


use shrink_to_fit while shrink_to can trigger UB

we should at least check if it's worth to shrink before doing so, now that we have to use shrink_to_fit

Just so you know, shrink_to_fit suffers from the same potential UB as shrink_to (e.g. running MIRI on this reports an uninitialized read: https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=fed140485b86747eef2f61cfec434c63 ). I think that currently to safely shrink a VecDeque you have to call make_contiguous first. Alternatively, the fix (rust-lang/rust#108475 ) will probably be part of the next nightly, and also get backported into stable somewhat soon I believe.

hm, okay. Thanks for the information!


/api/auth/logout doesn't clear cookies when handleAuth's cookieOptions are set

Bug report
Describe the bug
In order to have auth work across my root and subdomains, I'm setting a custom domain in cookieOptions for the handleAuth handler in /api/auth/[...supabase].js.
Setting works like a charm for having the user session detected across the domains, but when I try to log out using handleAuth's helper route, the cookies are not cleared. The helper route works only when I do not set any custom cookieOptions.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:

When initializing handleAuth in /api/auth/[...supabase].js, set custom cookieOptions e.g.

export default handleAuth({
    // For setting top-level cookies to work across subdomains
    cookieOptions: {
        domain: 'some-domain.com', (without the www)
    },
});

Sign in, e.g. await supabaseClient.auth.signIn(...) - user is signed in successfully, auth works across the domains. The sb- cookies have domain set to .some-domain.com. I've noticed that they get the "." pre-pended to the domain I specify.
Attempt to log out by calling router.push('/api/auth/logout')
sb- cookies aren't cleared, browser behaves as if user never logged out

Expected behavior
Based on https://github.com/supabase/auth-helpers/issues/178, the logout route should take care of clearing the cookies.
System information

OS: macOS
Browser (if applies) [e.g. chrome, safari]: Chrome
Version of supabase-js: 1.35.6
Version of @supabase/auth-helpers-nextjs: ^0.2.7,
Version of @supabase/auth-helpers-react": ^0.2.3,

Figured this out... the auth-helper-'s handleLogout isn't explicitly specifying the domain: when calling setCookies:, so I wrote my own API route to include this and the cookies were cleared!


Add xarray support to hyperslicer

Problem
Hyperslicer should support xarray natively and read names and such for the sliders via the xarray info.

Proposed Solution
@jrussell25 has  most of implementation of this. We should bulid on that. I'm opening this just so there is a coherent place to keep track of it and to note things like this:
Currently hyperslicer forces all arrays to be loaded into memory due to this line: https://github.com/ianhi/mpl-interactions/blob/050c989557aecbcb1077306a7b325159ea3c8ecd/mpl_interactions/generic.py#L574 we will need to avoid that otherwise v bad news when big data.

Additional context

I dont know how to handle the out of memory case. Is that really something we need to support?
My only idea is to call .load() on the xarray slice when you call imshow. but maybe theres a better way. I also dont know how you did caching for ode stuff but something like that would probably be helpful if were going to go down this road.

This will be closed by #138

fixed by #138


[SPARK-35242][SQL] Support changing session catalog's default database

What changes were proposed in this pull request?
This PR is a follow-up PR for #32364. It has been closed by github-actions because it hasn't been updated in a while. The previous PR has added a new custom parameter (spark.sql.catalog.$SESSION_CATALOG_NAME.defaultDatabase) to configure the session catalog's default database which is required by some use cases where the user does not have access to the default database.
Therefore I have created a new PR based on this and added these changes in addition:

Rebased / updated the previous PR to the latest master branch version
Deleted the DEFAULT_DATABASE  static member from sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/catalog/SessionCatalog.scala and refactored the code regarding this

Why are the changes needed?
If our user does not have any permissions for the Hive default database in Ranger, it will fail with the following error:
22/08/26 18:36:21 INFO  metastore.RetryingMetaStoreClient: [main]: RetryingMetaStoreClient proxy=class org.apache.hadoop.hive.ql.metadata.SessionHiveMetaStoreClient<EMAIL_ADDRESS>(auth:KERBEROS) retries=1 delay=1 lifetime=0
org.apache.spark.sql.AnalysisException: org.apache.hadoop.hive.ql.metadata.HiveException: MetaException(message:Permission denied: user [hrt_10] does not have [USE] privilege on [default])
  at org.apache.spark.sql.hive.HiveExternalCatalog.withClient(HiveExternalCatalog.scala:110)
  at org.apache.spark.sql.hive.HiveExternalCatalog.databaseExists(HiveExternalCatalog.scala:223)
  at org.apache.spark.sql.internal.SharedState.externalCatalog$lzycompute(SharedState.scala:150)
  at org.apache.spark.sql.internal.SharedState.externalCatalog(SharedState.scala:144)

The idea is that we introduce a new configuration parameter where we can set a different database name for the default database. Our user has enough permissions for this  in Ranger.
For example:
spark-shell --conf spark.sql.catalog.spark_catalog.defaultDatabase=other_db
Does this PR introduce any user-facing change?
There will be a new configuration parameter as I mentioned above but the default value is "default" as it was previously.
How was this patch tested?

With github action (all tests passed)

https://github.com/roczei/spark/actions/runs/2934863118

Manually tested with Ranger + Hive

Scenario a) hrt_10 does not have access to the default database in Hive:
[hrt_10@quasar-thbnqr-2 ~]$ spark-shell
Setting default log level to "WARN".
To adjust logging level use sc.setLogLevel(newLevel). For SparkR, use setLogLevel(newLevel).
22/08/26 18:14:18 WARN  conf.HiveConf: [main]: HiveConf of name hive.masking.algo does not exist
22/08/26 18:14:30 WARN  cluster.YarnSchedulerBackend$YarnSchedulerEndpoint: [dispatcher-event-loop-17]: Attempted to request executors before the AM has registered!

...

scala> spark.sql("use other")
22/08/26 18:18:47 INFO  conf.HiveConf: [main]: Found configuration file file:/etc/hive/conf/hive-site.xml
22/08/26 18:18:48 WARN  conf.HiveConf: [main]: HiveConf of name hive.masking.algo does not exist
22/08/26 18:18:48 WARN  client.HiveClientImpl: [main]: Detected HiveConf hive.execution.engine is 'tez' and will be reset to 'mr' to disable useless hive logic
Hive Session ID = 2188764e-d0dc-41b3-b714-f89b03cb3d6d
22/08/26 18:18:48 INFO  SessionState: [main]: Hive Session ID = 2188764e-d0dc-41b3-b714-f89b03cb3d6d
22/08/26 18:18:50 INFO  metastore.HiveMetaStoreClient: [main]: HMS client filtering is enabled.
22/08/26 18:18:50 INFO  metastore.HiveMetaStoreClient: [main]: Trying to connect to metastore with URI thrift://quasar-thbnqr-4.quasar-thbnqr.root.hwx.site:9083
22/08/26 18:18:50 INFO  metastore.HiveMetaStoreClient: [main]: HMSC::open(): Could not find delegation token. Creating KERBEROS-based thrift connection.
22/08/26 18:18:50 INFO  metastore.HiveMetaStoreClient: [main]: Opened a connection to metastore, current connections: 1
22/08/26 18:18:50 INFO  metastore.HiveMetaStoreClient: [main]: Connected to metastore.
22/08/26 18:18:50 INFO  metastore.RetryingMetaStoreClient: [main]: RetryingMetaStoreClient proxy=class org.apache.hadoop.hive.ql.metadata.SessionHiveMetaStoreClient<EMAIL_ADDRESS>(auth:KERBEROS) retries=1 delay=1 lifetime=0
org.apache.spark.sql.AnalysisException: org.apache.hadoop.hive.ql.metadata.HiveException: MetaException(message:Permission denied: user [hrt_10] does not have [USE] privilege on [default])
  at org.apache.spark.sql.hive.HiveExternalCatalog.withClient(HiveExternalCatalog.scala:110)
  at org.apache.spark.sql.hive.HiveExternalCatalog.databaseExists(HiveExternalCatalog.scala:223)
  at org.apache.spark.sql.internal.SharedState.externalCatalog$lzycompute(SharedState.scala:150)
  at org.apache.spark.sql.internal.SharedState.externalCatalog(SharedState.scala:144)
  at org.apache.spark.sql.internal.SharedState.globalTempViewManager$lzycompute(SharedState.scala:179)

This is the expected behavior because it will use the "default" db name.
Scenario b) Use the "other" database where the hrt_10 user has proper permissions
[hrt_10@quasar-thbnqr-2 ~]$ spark-shell --conf spark.sql.catalog.spark_catalog.defaultDatabase=other
Setting default log level to "WARN".
To adjust logging level use sc.setLogLevel(newLevel). For SparkR, use setLogLevel(newLevel).
22/08/26 18:27:03 WARN  conf.HiveConf: [main]: HiveConf of name hive.masking.algo does not exist
22/08/26 18:27:14 WARN  cluster.YarnSchedulerBackend$YarnSchedulerEndpoint: [dispatcher-event-loop-15]: Attempted to request executors before the AM has registered!

...

scala> spark.sql("use other")
22/08/26 18:29:22 INFO  conf.HiveConf: [main]: Found configuration file file:/etc/hive/conf/hive-site.xml
22/08/26 18:29:22 WARN  conf.HiveConf: [main]: HiveConf of name hive.masking.algo does not exist
22/08/26 18:29:22 WARN  client.HiveClientImpl: [main]: Detected HiveConf hive.execution.engine is 'tez' and will be reset to 'mr' to disable useless hive logic
Hive Session ID = 47721693-dbfe-4760-80f6-d4a76a3b37d2
22/08/26 18:29:22 INFO  SessionState: [main]: Hive Session ID = 47721693-dbfe-4760-80f6-d4a76a3b37d2
22/08/26 18:29:24 INFO  metastore.HiveMetaStoreClient: [main]: HMS client filtering is enabled.
22/08/26 18:29:24 INFO  metastore.HiveMetaStoreClient: [main]: Trying to connect to metastore with URI thrift://quasar-thbnqr-4.quasar-thbnqr.root.hwx.site:9083
22/08/26 18:29:24 INFO  metastore.HiveMetaStoreClient: [main]: HMSC::open(): Could not find delegation token. Creating KERBEROS-based thrift connection.
22/08/26 18:29:24 INFO  metastore.HiveMetaStoreClient: [main]: Opened a connection to metastore, current connections: 1
22/08/26 18:29:24 INFO  metastore.HiveMetaStoreClient: [main]: Connected to metastore.
22/08/26 18:29:24 INFO  metastore.RetryingMetaStoreClient: [main]: RetryingMetaStoreClient proxy=class org.apache.hadoop.hive.ql.metadata.SessionHiveMetaStoreClient<EMAIL_ADDRESS>(auth:KERBEROS) retries=1 delay=1 lifetime=0
res0: org.apache.spark.sql.DataFrame = []

scala> spark.sql("select * from employee").show()
+---+----+------+-----------+
|eid|name|salary|destination|
+---+----+------+-----------+
| 12| Ram|    10|     Szeged|
| 13| Joe|    20|   Debrecen|
+---+----+------+-----------+

scala>

@cloud-fan, @hddong, @dongjoon-hyun could you please review my changes? Thanks!

Can one of the admins verify this patch?

@cloud-fan
Could you please take a look when you have some time?  This PR is a follow-up PR for https://github.com/apache/spark/pull/32364. Thanks!

we should also update V2SessionCatalog.defaultNamespace

Thanks @cloud-fan, I will check these!

we should also update V2SessionCatalog.defaultNamespace

@cloud-fan, for example this change will be good?
diff --git a/sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/v2/V2SessionCatalog.scala b/sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/v2/V2SessionCatalog.scala
index efbc9dd755..23775c3ae0 100644
--- a/sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/v2/V2SessionCatalog.scala
+++ b/sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/v2/V2SessionCatalog.scala
@@ -33,6 +33,7 @@ import org.apache.spark.sql.connector.expressions.Transform
 import org.apache.spark.sql.errors.{QueryCompilationErrors, QueryExecutionErrors}
 import org.apache.spark.sql.execution.datasources.DataSource
 import org.apache.spark.sql.internal.connector.V1Function
+import org.apache.spark.sql.internal.SQLConf
 import org.apache.spark.sql.types.StructType
 import org.apache.spark.sql.util.CaseInsensitiveStringMap

@@ -43,7 +44,7 @@ class V2SessionCatalog(catalog: SessionCatalog)
   extends TableCatalog with FunctionCatalog with SupportsNamespaces with SQLConfHelper {
   import V2SessionCatalog._

-  override val defaultNamespace: Array[String] = Array("default")
+  override val defaultNamespace: Array[String] = Array(SQLConf.get.defaultDatabase)

override val defaultNamespace: Array[String] = Array(SQLConf.get.defaultDatabase)

Yes

override val defaultNamespace: Array[String] = Array(SQLConf.get.defaultDatabase)

Yes

@cloud-fan Ok, I have fixed this.

Is this a common behavior in other databases?

@cloud-fan Good question. The reason that we cannot delete the user specified default database because we have the following if statement in the actual code:
if (dbName == defaultDatabase)

and this is the latest state of master:
https://github.com/apache/spark/blob/master/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/catalog/SessionCatalog.scala#L286
  def dropDatabase(db: String, ignoreIfNotExists: Boolean, cascade: Boolean): Unit = {
    val dbName = format(db)
    if (dbName == DEFAULT_DATABASE) {
      throw QueryCompilationErrors.cannotDropDefaultDatabaseError
    }

As you can see that I am just using the same logic.
If you think that we should only deny the database drop for "default" and allow for the value of spark.sql.catalog.spark_catalog.defaultDatabase, it is ok for me. The change is very simple:
+++ b/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/catalog/SessionCatalog.scala
@@ -284,7 +284,7 @@ class SessionCatalog(

   def dropDatabase(db: String, ignoreIfNotExists: Boolean, cascade: Boolean): Unit = {
     val dbName = format(db)
-    if (dbName == defaultDatabase) {
+    if (dbName == "default") {
       throw QueryCompilationErrors.cannotDropDefaultDatabaseError
     }
     if (!ignoreIfNotExists) {

and here is the validation:
 $ ./spark-shell --conf spark.sql.catalogImplementation=hive --conf spark.sql.catalog.spark_catalog.defaultDatabase=xyz
Setting default log level to "WARN".
To adjust logging level use sc.setLogLevel(newLevel). For SparkR, use setLogLevel(newLevel).
22/09/19 14:21:07 WARN NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
Spark context Web UI available at http://localhost:4040
Spark context available as 'sc' (master = local[*], app id = local-1663590068068).
Spark session available as 'spark'.
Welcome to
      ____              __
     / __/__  ___ _____/ /__
    _\ \/ _ \/ _ `/ __/  '_/
   /___/ .__/\_,_/_/ /_/\_\   version 3.4.0-SNAPSHOT
      /_/

Using Scala version 2.12.17 (OpenJDK 64-Bit Server VM, Java 1.8.0_345)
Type in expressions to have them evaluated.
Type :help for more information.

scala> spark.sql("show databases").show()
+---------+
|namespace|
+---------+
|      abc|
|  default|
|      xyz|
+---------+

scala> spark.sql("use database abc")
res1: org.apache.spark.sql.DataFrame = []

scala> spark.sql("SELECT current_database() AS db").show()
+---+
| db|
+---+
|abc|
+---+

scala>

scala> spark.sql("drop database xyz")
res3: org.apache.spark.sql.DataFrame = []

scala> spark.sql("show databases").show()
+---------+
|namespace|
+---------+
|      abc|
|  default|
+---------+

scala>

Is this solution acceptable for you?

Thanks @cloud-fan, I have implemented this and all tests passed. As I see we have resolved all of your feedbacks.

Hi @cloud-fan,
Thanks for the feedbacks, I have resolved all of them. Unfortunatelly I did a mistake during the version magament but I have already resolved with git rebase / git push as you can see.  This is the reason that a lot of new labels have been added which are not necessary by this pull request. Only the SQL label is the good one.

Hi @cloud-fan,
All build issues have been fixed and all of your feedbacks have been implemented. Latest state:
$ bin/spark-shell --conf spark.sql.catalog.spark_catalog.defaultDatabase=other_db
Setting default log level to "WARN".
To adjust logging level use sc.setLogLevel(newLevel). For SparkR, use setLogLevel(newLevel).
22/09/25 14:34:16 WARN NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
Spark context Web UI available at http://localhost:4040
Spark context available as 'sc' (master = local[*], app id = local-1664109256655).
Spark session available as 'spark'.
Welcome to
      ____              __
     / __/__  ___ _____/ /__
    _\ \/ _ \/ _ `/ __/  '_/
   /___/ .__/\_,_/_/ /_/\_\   version 3.4.0-SNAPSHOT
      /_/

Using Scala version 2.12.17 (OpenJDK 64-Bit Server VM, Java 1.8.0_345)
Type in expressions to have them evaluated.
Type :help for more information.

scala> spark.sql("show databases").show()
org.apache.spark.SparkDefaultDatabaseNotExistsException: [DEFAULT_DATABASE_NOT_EXISTS] Default database other_db not exist, please create it first or change default database to 'default'.
  at org.apache.spark.sql.errors.QueryExecutionErrors$.defaultDatabaseNotExistsError(QueryExecutionErrors.scala:1936)
  at org.apache.spark.sql.internal.SharedState.externalCatalog$lzycompute(SharedState.scala:156)
  at org.apache.spark.sql.internal.SharedState.externalCatalog(SharedState.scala:147)
  at org.apache.spark.sql.internal.BaseSessionStateBuilder.$anonfun$catalog$1(BaseSessionStateBuilder.scala:154)
  at org.apache.spark.sql.catalyst.catalog.SessionCatalog.externalCatalog$lzycompute(SessionCatalog.scala:122)
  at org.apache.spark.sql.catalyst.catalog.SessionCatalog.externalCatalog(SessionCatalog.scala:122)
  at org.apache.spark.sql.catalyst.catalog.SessionCatalog.listDatabases(SessionCatalog.scala:323)
  at org.apache.spark.sql.execution.datasources.v2.V2SessionCatalog.listNamespaces(V2SessionCatalog.scala:232)
  at org.apache.spark.sql.execution.datasources.v2.ShowNamespacesExec.run(ShowNamespacesExec.scala:42)
  at org.apache.spark.sql.execution.datasources.v2.V2CommandExec.result$lzycompute(V2CommandExec.scala:43)
  at org.apache.spark.sql.execution.datasources.v2.V2CommandExec.result(V2CommandExec.scala:43)
  at org.apache.spark.sql.execution.datasources.v2.V2CommandExec.executeCollect(V2CommandExec.scala:49)
  at org.apache.spark.sql.execution.QueryExecution$$anonfun$eagerlyExecuteCommands$1.$anonfun$applyOrElse$1(QueryExecution.scala:98)
  at org.apache.spark.sql.execution.SQLExecution$.$anonfun$withNewExecutionId$6(SQLExecution.scala:111)
  at org.apache.spark.sql.execution.SQLExecution$.withSQLConfPropagated(SQLExecution.scala:171)
  at org.apache.spark.sql.execution.SQLExecution$.$anonfun$withNewExecutionId$1(SQLExecution.scala:95)
  at org.apache.spark.sql.SparkSession.withActive(SparkSession.scala:779)
  at org.apache.spark.sql.execution.SQLExecution$.withNewExecutionId(SQLExecution.scala:64)
  at org.apache.spark.sql.execution.QueryExecution$$anonfun$eagerlyExecuteCommands$1.applyOrElse(QueryExecution.scala:98)

LGTM except for 2 minor comments

Thanks @cloud-fan! I have implemented these two comments.

thanks, meriging to master!

@cloud-fan,
Thank you very much for your help!


Q. rootSaga: yield watchSaga() VS fork(watchSaga) [VS takeEvery(action, saga)]?

In the documentation (more precisely, in the beginner tutorial), the rootSaga is implemented as:
export default function* rootSaga() {
  yield [
    watchSagaOne(),
    watchSagaTwo(),
  ];
}

This Saga yields an array with the results of calling our two sagas[...]. This means the two resulting Generators will be started in parallel.

Great, I got it. Everything's work.
Now, let's take a look to the real-world example:
export default function* rootSaga() {
  yield [
    fork(watchSagaOne),
    fork(watchSagaTwo),
  ];
}

Hmm. Not the same.
The API documentation says that fork:

Creates an Effect description that instructs the middleware to perform a non-blocking call on fn

But, having the sagas run in parallel directly, I'm wasn't really expecting any blocking call.
I tried switching between having the watchSaga functions invoked directly or using fork (and even mixing the two), but I don't see any difference in the behaviour.
My question: what's the difference? Is there a best way  or a suggested use case scenario?
Is it related to tests, maybe?
Or maybe fork is the redux-saga way, and the other is the js generator way?
Also, (but this is more of a confirmation), using something like:
export default function* rootSaga() {
  yield [
    takeEvery(actionOne, sagaOne),
    takeEvery(actionTwo, sagaTwo),
  ];
}

looks like it's working great and we can get rid of the "watch" sagas (that is, if you don't need any additional "in-between" logic, of course).
Are there any (other) disadvantages in using takeEvery directly?
Thank you so much! :)

great question! I'd suggest searching the issues section. there's an extension discussion here
https://github.com/redux-saga/redux-saga/issues/760
docs also say that the "watch/fork" method allows for more powerful code patterns while takeEvery will guarantee that you fork a new task in response to a particular action

Thank you @anthonychung14, I did search a little in the issues, but I completely missed #760: looks like I'm not the only one with doubts (I'm relieved)! :)
I'll surely dig into it, thanks! <3

Actually, I'm going to close this issue: the discussion in #760 is exactly what I was looking for. Thanks again.


BUG: DCA Bot has so many problems. They are documented in this ticket with two Looms.

What is happening?

Section description
Provide as much context as you can. Give as much context as you can to make it easier for the developers to figure what is happening.

Loom Number 1 of DCA Bott:
https://www.loom.com/share/f00a579374c54139b695c9a2a74d4e3e?sid=f7e556ee-076d-48e6-a01c-c0bdb23eb1b7

Loom Number 2 of DCA Bot:
https://www.loom.com/share/d2e09a7ed88542399760ee3e86265588?sid=8a3a2ecc-c70f-414e-b11d-aed4663f4762

Transactions:

DCA Bot Transactions Happened with 1 minute of each other:
https://etherscan.io/address/0x83334ef0C6f6396413C508A7762741e9FD8B20E9#internaltx
Which was incorrect when they were scheduled for 1 hour apart.

Front-end:

The DCA Bot was scheduled to start at 1AM, but on the website it said it would start in 1, but they started at the time I scheduled so the front-end was incorrect. Check Loom.
No TVL shows on the bot page
Bot is not visible on CurveBot My bots if started on Palomabot.

Telegram Alerts

Wrong information, but also showin gthat the bots did not respect the schedule. See the attached picture

What is the expected behaviour?

Section description
If you know, please write down what is the expected behaviour. If you don't know, that's ok. We can have a discussion in comments.

DCA Bot:

schedules 1 tx each period
Correct front-end time to start
Correct TVl number

@wdev733 more issues:
I started a DCA bot with the following input:

I started the bot at 3:12pm my local time. It is 4:21pm so all three trades should have done. But so far only the deposit tx at the beginning is there https://etherscan.io/tx/0x4627ef292fae6dda478dad7eb5867fe778ee62e4b174ff6563b3dda51899d312
Also, there's no DCA bot under mybots page:


Is there version to support ControlzEx 6.0

When i use the 3rd library like Fluent.Ribbon,i found that the lastest version of Fluent.Ribbon supports ControlzEx 6.0 and the lastest version of MahApps can not support ControlzEx 6.0 .
But i want to use the new feature of the lastest theme in MahApps. So is there new version of MahApps to support ControlzEx 6.0 later.

You can try the pre-release of v3.0.

[!NOTE]
Please close this issue and ask such things on Discussions instead in order to keep issue list clean. Thx.


gulp dist fails at 'test' task

PROJECTS/grommet (master)
$ gulp dist
[00:24:04] Using gulpfile c:\PROJECTS\grommet\gulpfile.js
[00:24:04] Starting 'dist-preprocess'...
[00:24:04] Starting 'preprocess'...
[00:24:04] Starting 'clean'...
[00:24:04] Finished 'clean' after 307 ms
[00:24:04] Starting 'copy'...
[00:24:04] Finished 'copy' after 9.08 ms
[00:24:04] Starting 'jslint'...
[00:24:09] Finished 'jslint' after 5.05 s
[00:24:09] Starting 'scsslint'...
[00:24:09] Finished 'scsslint' after 4.76 μs
[00:24:09] Finished 'preprocess' after 5.37 s
[00:24:09] Starting 'dist-css'...
[00:24:10] Finished 'dist-css' after 546 ms
[00:24:10] Starting 'copy'...
[00:24:10] Finished 'copy' after 5.05 ms
[00:24:10] Starting 'test'...
c:\PROJECTS\grommet\node_modules\jsdom\lib\jsdom\utils.js:269
const children = el._childNodes;
^^^^^
[00:24:10] 'test' errored after 604 ms
[00:24:10] SyntaxError: Use of const in strict mode.
at Module._compile (module.js:439:25)
at Object.require.extensions..js (c:\PROJECTS\grommet\src\utils\test\test-compiler.js:44:17)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object. (c:\PROJECTS\grommet\node_modules\jsdom\lib\jsdom.js:12:17)
at Module._compile (module.js:456:26)
at Object.require.extensions..js (c:\PROJECTS\grommet\src\utils\test\test-compiler.js:44:17)
at Module.load (module.js:356:32)
[00:24:10] 'dist-preprocess' errored after 6.53 s
[00:24:10] Error: [object Object]
at formatError (c:\Users\belovy\AppData\Roaming\npm\node_modules\gulp\bin\gulp.js:169:10)
at Gulp. (c:\Users\belovy\AppData\Roaming\npm\node_modules\gulp\bin\gulp.js:195:15)
at Gulp.emit (events.js:117:20)
at Gulp.Orchestrator._emitTaskDone (c:\PROJECTS\grommet\node_modules\gulp\node_modules\orchestrator\index.js:264:8)
at c:\PROJECTS\grommet\node_modules\gulp\node_modules\orchestrator\index.js:275:23
at finish (c:\PROJECTS\grommet\node_modules\gulp\node_modules\orchestrator\lib\runTask.js:21:8)
at cb (c:\PROJECTS\grommet\node_modules\gulp\node_modules\orchestrator\lib\runTask.js:29:3)
at finish (c:\PROJECTS\grommet\node_modules\run-sequence\index.js:53:5)
at Gulp.onError (c:\PROJECTS\grommet\node_modules\run-sequence\index.js:60:4)
at Gulp.emit (events.js:117:20)

Hi @cssberries, can you describe more about your environment? Are you using es6 syntax at all?
I'm wondering if const children = el._childNodes; is coming from your app or from a dependency we use.

I'm running on Windows 7 64bit.
I'm going though the steps shown in the video.

Ok thanks. So probably is a dependency of ours using ES6 format.
I will investigate that on windows. I was not expecting this issue. Let me get back to you soon.

Hi @cssberries , I've just tried in the same environment and using Windows 7 as well and I'm not able to reproduce this issue.

Can you confirm the Node and NPM version you are using?
I'm using Node v0.12.4 and npm 2.10.1.

Updating Node to v0.12.4 solves the issue.
Now I have Warning when running "coverage" task.
Should I open a new issue for that?
[09:47:10] Finished 'test' after 7.37 s
[09:47:10] Starting 'coverage'...
Done! You can checkout the report at test/coverage.html.
[09:47:13] Finished 'coverage' after 2.93 s
Warning: owner-based and parent-based contexts differ (values: undefined vs pt-BR) for key (locales) while mounting LoginForm (see: http://fb.me/react-context-by-parent)
Test failed: Error: connect ECONNREFUSED
at exports._errnoException (util.js:746:11)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1010:19)

Well this warning is expected as part of React version 0.13. We are waiting for the release of React 0.14 to get this warning gone. You should not worry about it. But I would not expect your test to fail.
Based on the logs it seems to be related to a network issue. Error: connect ECONNREFUSED.
Are you under a proxied network?

I am behind a proxy server but NPM is configured as expected.

It's a bit hidden, but this line is the key thing
[webpack-dev-server] started: Browse to http://localhost:undefined/webpack-dev-server/

If you point your browser at **http://localhost:undefined/webpack-dev-server/**you should see the app you're running.

Well, it takes me to the google's search result page.

I should have looked closer, the "port" part of the URL is "undefined".  I'll need Alan to look at that.

The default port is 9000, I'm not sure why yours is showing as undefined. In your gulpfile.js could you please make sure you have the following entry in your opts:
var opts = {
   ...
   devServerPort: 9000,
   ...
};

If you have it there, your dev server should be available at http://localhost:9000/webpack-dev-server/

If you see the Grommet logo loading forever you might be experience the webpack problem. I'm going to create a separate issue for this and post it here so that you understand.

#44

Nope, I don't have the "devServerPort: 9000" entry.
I added it and got this:

Hum, interesting. I guess I know what's going on. Where are you trying to run gulp dev? At grommet root folder?
I believe you need to run gulp dev inside the docs folder. I remember you trying to watch the video on How to Contribute to Grommet, and I believe I mention that in the video. There is no UI to be server for the grommet root folder, that's why I think you are getting the not found stuff.

Alan, would it make sense to change the gulp dev task in the root folder to instruct them where the right place to run 'gulp dev'.

Good point. Will work on that.

Done!
https://github.com/HewlettPackard/grommet/commit/f44c6b8bc04c302c3e9db6f0d62a21ef1f3a572a
@cssberries, if you sync your Fork you should be able to see the message now.

Finally I can see the right screen!
And some errors from Chrom's console:
GET http://localhost:8002/favicon.ico 404 (Not Found)
dev-server.js?b7b7:57 [HMR] Waiting for update signal from WDS...
warning.js?8bc8:48 Warning: Failed propType: Invalid prop handler of type object supplied to Route, expected function.
warning.js?8bc8:48 Warning: Invalid undefined handler of type object supplied to UnknownComponent, expected function.

Cool, I can see possible Pull Requests here. :+1:


test(htlc-eth-besu-erc20): migrate refund-endpoint test cases from Tape to Jest

Need to migrate all existing test cases for the refund-endpoint to Jest
https://github.com/hyperledger-cacti/cacti/blob/main/packages/cactus-test-plugin-htlc-eth-besu-erc20/src/test/typescript/integration/plugin-htlc-eth-besu-erc20/refund-endpoint.test.ts

Hi @petermetz, Please assign this issue to me!

@Udhayakumari Done! Thank you for the contribution!


Support for Jade?

Hey there, I was wondering if Timber supports Jade? I'm asking because after trying it, I simply can't go back to writing normal HTML ever again :D.

Not something that it supports right now -- but something that would make for an interesting extension. Let me know if you have a start or have progress to share. I can imagine a future where Timber is agonistic about allowing different template languages.

Okay, thanks anyways. Yeah, I've been building static sites for a while (I'm a front end guy), and, like many of us front-enders out there, we simply can't go back to writing pure HTML again.
PHP is on the same line of "ugliness" as well, so making Timber work with these preprocessors would be great.

:+1: For Jade support!

I'm totally for Jade support. In the meantime, I have set up my gulp install to bridge the gap somewhat:
changed = require 'gulp-changed'
jade = require 'gulp-jade'
plumber = require 'gulp-plumber'
rename = require 'gulp-rename'

gulp.task 'jade', ->
  gulp.src paths.jade.input
    .pipe changed paths.jade.output, extension: '.twig'
    .pipe plumber(
      derrorHandler: (error) ->
        gutil.log('(ERROR)', error.message)
        gutil.beep()
      errorHandler: notify.onError("Error: <%= error.message %>")
    )
    .pipe jade(
      pretty: true
    )
    .pipe rename
      extname: '.twig'
    .pipe gulp.dest paths.jade.output

In the Jade templates, you simply write the Twig tags/expressions as plain text, like so:
body
  .site-container
    | {% include 'header.twig' %}
    | {% block content %}{% endblock %}
    | {% include 'footer.twig' %}

Works like a charm. And I was positively shocked when I realized how much cleaner my templates have become by using Jade.
Direct support would be much preferred at any rate. Imagine how fantastically clean it would be to do something like this
each post in posts
  article
    h3= post.title
    p= post.content

instead of this
{% for post in posts %}

{{post.title}}

{{post.content}}

{% endfor %}

Any news on this?

I'm looking forward to Jade support too. But for now @herrbischoff 's solution should work.

@dinolatoga @herrbischoff: I'd love to see continued development on this front, but I'm afraid I'm working on an intense backlog of stuff and don't see getting to this myself for quite some time. That said, PRs are always welcome if you want to pursue a "more native" (ie: gulp-less) solution towards implementation

@jarednova I'd love to work on it but have to admit that I'm a little puzzled by how the actual template compile workflow runs. If you could give me some pointers where I should replace code, hook in and what to expect to happen, I'd give it a shot. Especially important would be the proper implementation of the included functions, variables and placeholders.
A serious roadblock may also be that there appears to be no up-to-date implementation of Jade for PHP, which is a shame.

Just wanted to bring this back into consideration. There is now a very active and maintained implementation of Jade for PHP: https://github.com/kylekatarnls/jade-php
I'd really like to take a stab at bringing it to Timber. Having looked through the source, so far it promises to be rather painful as Twig appears to be woven in pretty deep. On the other hand, as Jade has no concept of filters in the way Twig does, it should be possible to leave a lot of those complexities out. All in all Jade is a very much different approach to templating than Twig is and way less in the general PHP style, which I consider to be a good thing.

Hi @herrbischoff, I think this would be great to implement at some stage.
I can't speak for @jarednova however I do feel this would be better suited for v2, rather than trying to crowbar it into the existing codebase. As obviously that might take a little while and you want to take a crack at this (I saw you posted a workaround), it may be worth forking Timber or doing a PR on https://github.com/timber/sugar (whichever is more suitable) so when it comes to making Timber a bit more agnostic about it's templating language we have something to work from

I'm going to go ahead and close this as it's not an issue as such and trying to get the issues list a bit clearer. If you want to discuss this further jump into Gitter :+1:

Agreed, although this issue carries the "enhancement" tag. I'm going to go ahead and fork Timber to try and get the Jade implementation going. I presume there is no rough timetable for the template engine agnostic change, is there? I wouldn't want to write code that cannot be used afterwards.

It's more for my sanity, going through 100+ issues everyday is taxing :)
We are a way off V2 (re-write, not on V1 yet!) so I think you are good for a while, I'm sure there will be some notification on when V2 is being started and (if we haven't spoke before that time) we can take a look at a Jade implementation.

And make sure to keep us up to date via Gitter!


Issue 154

Fix #154
Test URLs:

Before: https://main--ororafresh--hlxsites.hlx.live/
After: https://issue-154--ororafresh--hlxsites.hlx.live/about-us

Checked LHS with .live, still all 100's
https://pagespeed.web.dev/analysis/https-issue-154--ororafresh--hlxsites-hlx-live-about-us/0lap8szbkm?form_factor=mobile


Push git tags for 0.6 and 0.7

There aren't any git tags for the releases on PyPI and it's kind of hard to see what has changed since there isn't a prose changelog either

Tagged v0.6 and v0.7
Thanks for reporting @jezdez

💐

and 0.7.1


Line 115 (em support branch): 'null' is null or not an object (only appears with concatenated CSS)

The script doesn't throw any errors when I load in my three separate CSS files separately:
http://dev.paulrobertlloyd.com/about/
However, when using concatenated CSS files (compressed using PHP Minify), I get the following error:
'null' is null or not an object, line 115, character 5
Here's a link to the CSS file I'm loading, and the page where this CSS is being called from:
http://dev.paulrobertlloyd.com/_php/min/?g=css&1313442539
http://dev.paulrobertlloyd.com/about/styleguide/

Hey Paul, can you test this on the em-support branch and see if it's better now? I dropped your CSS into my demo files and things look good to me, so I'll close this now.
If not, let me know and I'll reopen. Thanks so much.


Add optional crash dumping on ConnectionError

Crash dump on ConnectionError if a global variable is provided.
The goal is to see inside of a request without logging sensitive fields

No longer necessary due to multi-part endpoint


Fix typo in code example

dotenvy should be dotenv

Thanks for opening this PR. dotenvy is the correct crate name there as the dotenv crate is no longer maintained.

@weiznich thanks for clearing that up.


white screen not working

white screen not working

SOLUTION:
set flex:1 for both
1): <View style={{flex: 1}}>
and

issue solved in #81


refactor(upload): refactoring of upload methods

Improved the way that new upload methods can be implemented:

Threading logic was moved from each upload method to the upload command. This avoids code duplication and simplifies the implementation.
Moved upload method implementation under a new methods sub-module. New methods only (or ideally) need to add/modify files from this module.

Can’t look too in depth at current moment but from what I see it looks like this will conflict with the refactoring I did for animation if you could review there first plz

@stranzhay Yes, definitely, I will take a look as soon as I am done with this one.

This has been replaced by PR #236


fix: Conditionally import async_hooks to avoid leaking into browser chunks with conditional imports

!snapshot

!snapshot

!snapshot

!snapshot

!snapshot

!snapshot


Build with MinGW-w64

I'm trying to build with mingw w64 and got following error:
olp-cpp-sdk-core\src\http\winhttp\NetworkWinHttp.cpp:473:11: error: 'WINHTTP_DECOMPRESSION_FLAG_ALL' was not declared in this scope flags = WINHTTP_DECOMPRESSION_FLAG_ALL;
Would someone please add mingw-w64 support?

@lezipg Thank you for opening the first-ever issue for this SDK. Sadly there is no award attached to this honor.
As for your mingw-w64 issue, I must say it is a pretty uncommon supported environment, especially with NetworkWinHttp which requires Windows native libs.
Also, I would not assume to use NetworkWinHttp under Mingw-w64 but rather the curl based overload for UNIX systems. I wonder why the WIN32 CMake variable is set at all, it should be MINGW which should put you into the NetworkCurl which should build properly, assuming you provide a valid libcurl.so in your library path.
Is it a long-term solution on your side using Mingw-w64 or only for development purposes?

@andescu Thanks for the quick respond. I have tried to force cmake to use curl and it didn't work. Apparently these codes are focused on gcc, like the signal.h is different as from mingw-w64.
Yes, we're using mingw-w64 for long term. Actually we're changing from DataStore API to OLP and
wondering if we need to use this sdk.

Even if we add Mingw-w64 support it will definitely not be for WinHttp. I don't think that this is even possible as it highly depends on Windows libraries and includes.
Can you tell me how do you want to include our library? Is it with add_subdirectory from a root CMakeLists.txt file or are you trying to build and install upfront?
This SDK offers you an easy framework to communicate with the new OLP Data API so it is recommended to use it. You will benefit from many optimizations like cache, indexed queries, and prefetching that you normally would have to figure out and implement yourself.

Right, my wish would be mingw-w64 support with curl for Windows, if possible. For the DataStore API i'm using the libcurl for Windows.
I'm trying to build the sdk then link the library from install. It's more easier or perhaps the only possible way as i need to link these libraries in our project using Makefile.

@lezipg We are currently trying internally to see what is the effort to force cmake triggering the curl based network layer to build. But for the long run, I am not sure if we can provide a stable mingw support as we have clear dependencies (leveldb, boost, RapidJson) which do not come with mingw support themselves. So I am not sure if this will eventually work.
Anyway, we will provide feedback asap with the internal analysis.

@andescu Great! Thanks for the effort!

@lezipg Sorry for the delay, we needed to move this ticket to v1.5 due to some internal issues that were more burning. We anyway took it to the current sprint and will have an answer in the next two weeks if we are going to support this or a workaround on how to achieve. Does this sound ok to you?

@lezipg Can you please check PR #735 on your side to see if this would solve your problem. Once you give us positive feedback, we will decide if we support mingw in the long term or just on a hotfix basis.

@andescu Thanks for this information! Due to COVID-19 i may postpone my work. However, i'll check it as soon as possible.

@andescu It works with mingw-w64 on my side. Thank you!

Good to hear.


Docker using .env?

I am converting to the docker image hosting on AWS.   I put the .env file in the same directory with docker-compose.yml etc.  it contains LDAP settings but I do not see any packets going to my LDAP server.  It appears that it may not be reading .env, do I have this in the wrong location?
thanks!

@jacksonp2008
When using docker-compose, variables in a .env will not be passed through to the container, They are only usable within the docker-compose itself.
You should be able to use the env_file option to pass them through to the container like so:
version: '2'
services:

  mysql:
    image: mysql:5.7.12
    environment:
    - MYSQL_ROOT_PASSWORD=secret
    - MYSQL_DATABASE=bookstack
    - MYSQL_USER=bookstack
    - MYSQL_PASSWORD=secret
    volumes:
    - mysql-data:/var/lib/mysql

  bookstack:
    image: solidnerd/bookstack:0.17.1
    depends_on:
    - mysql
    env_file: .env
    volumes:
    - uploads:/var/www/BookStack/public/uploads
    - storage-uploads:/var/www/BookStack/storage/uploads
    ports:
    - "8080:80"

very good.  This works.


Remove old static function pages

Part of https://github.com/apache/datafusion/issues/12740
Is your feature request related to a problem or challenge?
@Omega359  added the infrastructure to automatically create documentation from code in https://github.com/apache/datafusion/pull/12668
For a while this will result in a transition period where we have two copies of most function documentation:

A "static" one (e.g. https://datafusion.apache.org/user-guide/sql/scalar_functions.html)
A "auto generated" one (e.g. TODO WHEN MERGED)

Describe the solution you'd like
Once all the documentation for functions has been migrated to the new auto generated pages, we should remove the static pages
Describe alternatives you've considered
Basically this means for the scalar, window and aggregate functions:

Delete the static file docs/source/user-guide/sql/scalar_functions.md
Rename the _new files like docs/source/user-guide/sql/scalar_functions_new.md to  docs/source/user-guide/sql/scalar_functions.md
Update the index page docs/source/user-guide/sql/index.rst to remove the _new entries
Update the script dev/update_function_docs.sh so it writes to the scalar_functions.md file

Additional context
We need to complete porting all documentation first

I think we are in the position that someone could pretty easily remove the Aggregate and Scalar functions page. We need to wait for https://github.com/apache/datafusion/issues/8709 before we can remove the window function one (but @jcsherin  and @jatin510  are pretty close)
https://datafusion.apache.org/user-guide/sql/index.html

My only concern is what to do with the functions that have postgresql-style syntax options (2 of which are still on the scalar doc page):

extract - it's data_part, but with different syntax
position - it's strpos, but with different syntax
substring, it's substr, but with different syntax
trim, it's one of the trim functions, but with different syntax

Should we put those into the special functions page?

@Omega359 I'm thinking we can probably put them as aliases?

That may work though it doesn't help in documenting the difference in syntax. I was also wondering about add an alternative_syntax(...) section to the Documentation struct for functions like these.

Yeah that could work, I can add an issue for that.

take


[FEAT] Update wash to use max_concurrent control interface

Feature or Problem
This PR is updating wash to use the latest control interface that supports max scale instead of counts. I verified that this version of the control interface works great with wasmCloud 0.78.0 as the breaking changes there are either backwards compatible over-the-wire or no longer involve the host (e.g. querying links and claims from the bucket directly always).
I got a little carried away and made a few more changes in this PR regarding the ctl command in this PR. This sets us up to be able to deprecate ctl entirely instead of keeping it stable for a subset of commands:

Added top level wash scale actor command to eventually replace wash ctl scale actor
Added top level wash update actor command to eventually replace wash ctl update actor
Removed wash ctl apply manifest entirely, as it's functionality that is replaced by wadm and uses a manifest format that's bespoke for this individual command.
The above changes were mostly moving code to wash-lib and then exposing another top level command, e.g. mostly refactoring.

Related Issues
Depends on https://github.com/wasmCloud/control-interface-client/pull/58 (this PR's checks can be re-run after that merges)
RFC https://github.com/wasmCloud/wasmCloud/issues/696
Release Information
wash-lib v0.12.0
wash-cli v0.21.0
Consumer Impact
As designed, this version of wash will remain completely compatible with older versions of the host and work for newer released versions.
Testing

Built on platform(s)

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

Tested on platform(s)

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

Unit Test(s)

Acceptance or Integration

Manual Verification

Are you able to add integration tests for the new commands?

Good call, they aren't new commands but we should definitely have an integration test for it at least basic. I've tested with a few manual cases so I'll just turn that into an integration test :)

Failing tests because of a DNS error... will try again tomorrow

Failing tests because of a DNS error... will try again tomorrow

Failing tests because I didn't exclude them from the nix suite :)

@mattwilkinsonn added integration tests and ready for re-review


Failing recognition of last list item

I'm using taggle together with type-ahead for autocompletion.
Type-ahead inserts a list of suggestions right after the .taggle_input element, wrapped in ul and li elements. When a suggestion gets selected and the tag is to be added, the Taggle.add function breaks because self.list.querySelectorAll('li') doest not target only the direct descendants of .taggle_list. Therefore insertBefore throws an exception because the selected lastLi is not a child of the taggle list but rather an item in the suggestion list.
This is quite easy to fix, but there are different possibilities and I'm not sure which one is the best.
I just expanded the selector to self.list.querySelectorAll('li.taggle') and used lastLi.nextSibling to get the right target for insertBefore. It would also be able to set a specific class on the last li which holds the input. Or maybe just use self.list.children? The li containing the input should always be the last item...
Having this fixed, the integration with type-ahead works pretty well.

Ah I see the problem. I'm thinking .children should be fine. Does that work for you?
Not sure about type-ahead's other options or how you're using taggle to work with it but it kinda works here http://jsfiddle.net/m6n0z8ww/

My solution with querySelectorAll('li.taggle') won't work when there are no tags since this function would return an empty array. I didn't recognize this before because I always had some tags prefilled.
.children works for me and I can't think of any reason why it shouldn't. Since the input is always spans the remaining space, there cannot really be anything else behind it.
Unfortunately I encountered some trouble with key events. When selecting an item from the autocomplete list and hitting enter or tab, the key event on the input attached by taggle fires first and adds the current partially typed key word as tag. Only after that, type-ahead adds the suggested tag. Only using the mouse to select a suggestion works fine.
So I guess I'll either have to fiddle with the event handlers or look for a different solution... But I'd like not to use any heavy frameworks.

That makes sense. Let me mess around with type-ahead and ill figure out a solution.

So @straight-shoota basically, it looks like you want to ignore Taggle's events and only add tags based on typeahead stuff. With the soon-to-be-added change of .children you should be able to do this:
(The more important stuff is at the bottom of the JS pane)
http://jsfiddle.net/m6n0z8ww/2/


Fix(45)-fix_ci_yaml

Welcome to Codecov :tada:
Once merged to your default branch, Codecov will compare your coverage reports and display the results in this comment.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


Tooltip not working

Describe the bug
Don't know if this is a bug or if I am just not using it correctly, but I can't seem to get the tooltip working. It only shows NaN-values.
To Reproduce
import bqplot as bqp
import bqplot.pyplot as plt

fig = plt.figure()
plt.plot(np.random.rand(10))
fig.marks[0].tooltip = bqp.Tooltip(fields=['x', 'y'], formats=['.2f', '.2f'])
fig

Expected behavior
See x, y values of the plot on hover.
Screenshots

Also, omitting a format instead shows blank:
fig.marks[0].tooltip = bqp.Tooltip(fields=['x', 'y'], formats=['', '.2f'])

And x, y does seem like the correct fields to use:

Looks to be duplicate of https://github.com/bqplot/bqplot/issues/1238


Memory Leak In Xamarin Forms CachedImage When Using Grid

Here is the scenario I followed:
Get an image from Android photo gallery as a byte array (possibly a downsampled size of 3MP). Create a CachedImage with DownsampleWidth = 100 and DownsampleUseDipUnits = true. Set the source of the CachedImage as photo.Source = ImageSource.FromStream(() => new MemoryStream(photoByteArray)). Then add this to a List<CachedImage> photoViews list.
After each addition or removal, update the Grid with the following code:
        public void ArrangePhotoViews()
        {
            photosGrid.Children.Clear();
            int row = 0;
            int column = 0;
            for (int i = 0; i < photoViews.Count; i++)
            {
                photosGrid.Children.Add(photoViews[i], column, row);
                if(column == 0)
                {
                    column = 1;
                }
                else if(column == 1)
                {
                    column = 0;
                    row++;
                }
            }
        }

I used Android Studio to track memory usage. Every time ArrangePhotoViews is called, regradless whether it is an addition or a removal operation, memory increases as if every photo in the list is newly being created and added to the grid.

What version of FFImageLoading?

I tested it with the latest version: 2.2.22. Application starts with 27.26 MB. After adding 10 photos, it becomes 35.22 MB. And after removing all 10 photos, it is 51.90 MB.

What is you cached image code?
Please mind that by default, FFImageLoading caches bitmaps in memory for future usage and it's completely normal to use some ram for that.
BTW: removing a view from grid doesn't guarantee to dispose it immediately.

 After using GC.Collect() from code, I saw that there was no leak.

Nice to hear that you sort it out 👍 Cheers

@john-larson  in which part of your code do you use GC.Collect() ? I mean how do you generally clean cache images. For example, I have listview on my page, when I pop from that page, i want to clean memory for all cached images. what is the suggested way to do this?

@EmilAlipiev I manually forced garbage collection just to test the memory usage, that was not meant for managing caching. As far as I understand, what you are trying to do is to clear the cache. @daniel-luberda  has recommended me to use the ImageService.Instance.InvalidateMemoryCache() method of the library for that purpose in another thread(see https://github.com/luberda-molinet/FFImageLoading/issues/782). But I would not want to misguide you as I am not an expert on the library. You can find the documentation here: https://github.com/luberda-molinet/FFImageLoading/wiki


Trying to use manual integration fails

I was trying to integrate the framework manually by using the guide but build fails with "No such Module CleanroomASL"
I am using cocoapods for other frameworks

Hi Tomas,
Sorry to hear you're having trouble. Would you mind posting the full text of the error message you're seeing?
That would definitely help me narrow down the problem.
Thanks a lot,
E.

Hi thanks for quick response. I am sorry but i cannot reproduce right now. In general, as I remember it seemed that the CleanroomASL was being imported before it was compiled, but i cannot be sure any longer.

No worries. Glad to hear it's working for you now.


Change ownership of Org request

Hi,
I created https://github.com/bitnami/kubeless which is a serverless framework on top of kubernetes.
I demonstrated this project back in december 2016 at the Kubernetes community meeting.
There is community wide interest to move this project further and I would like to move the source under its own organization kubeless. But it appears that you created it and created two empty repositories.
Since there are no activities in this organization, would you mind transferring the ownership to me ?
thanks,
-Sebastien

friendly ping

@paalth
https://github.com/bitnami/kubeless is an active project already known within the community by this name. It would be confusing for another project to adopt the same name, and this repo doesn't appear to be active. The Kubernetes project would appreciate the transfer of this org to @sebgoa.
You would, of course, be welcome to collaborate on Kubeless. Kubernetes does need a solid FaaS project.


Re-introduce StackOverflowError as non-fatal exception in Try

See #1961 and Scala

No, it was also removed in Scala. I've confused it with an out-dated version of NonFatal. This is the most recent one.


[BUG] Android 13 Issues: System share sheet and initial test startup

Two issues I've noticed when testing against an Android 13 emulator that don't affect previous versions of Android:

Tapping on a system share sheet brings it up and immediately dismisses it on Android 13. On previous versions, tapping it leaves it up as expected until dismissed.

Tests seem to fail when starting quite a bit due to Maestro acting and tapping on elements before they are visible to the user as the app is still opening up. This is probably due to the speed of Android 13 but it should be waiting for animation to settle a bit better I think. I don't have any of these issues on Android 12 or previous, so I have had to add in a - waitForAnimationToEnd: timeout: 1500 command just to handle this

Thanks for reporting this Simon, we'll make sure to take a look at this.

Also experienced by Thomas here:
"Thomas Vackier
4 hours ago
Seeing the same, restarting adb solves this for me somehow. ¯_(ツ)_/¯"

Hi there Simon! Could you try upgrading to the latest version of maestro and let us know if this issue still persists? Thanks!


Elasticsearch SQL Connector with ssl

when i use Elasticsearch SQL Connector
i found that my es secret by ssl  and use Self-Sign Certificate, i can not connect elasticsearch as sink,because there is no option   to set cert
CREATE TABLE enriched_orders (
  order_id INT,
  order_date TIMESTAMP_LTZ(3),
  customer_id INT,
  price DECIMAL(10, 5),
  product ROW<name STRING, description STRING>,
  order_status BOOLEAN,
  customer_name STRING,
  customer_address STRING,
  PRIMARY KEY (order_id) NOT ENFORCED
) WITH (
 'connector' = 'elasticsearch-7',
 'hosts' = 'http://localhost:9200',
 'index' = 'enriched_orders',
 'username' = 'root',
 'password' = 'password'
);

when i use kibana to connect to es i had to set elasticsearch.ssl.verificationMode: none to let ssl connect to es successful
when i use filebeat to connect to es i had to set ssl.verification_mode: none to let ssl connect to es successful
any other client want to connect to es also nedd to set  ssl config to connect es with ssl.
but i found no idea how to connect to es as a sink with ssl
this is my es config
cluster.name: "docker-cluster"
network.host: <IP_ADDRESS>

http.cors.enabled: true
http.cors.allow-origin: "*"
http.cors.allow-headers: Authorization,X-Requested-With,Content-Length,Content-Type

xpack.license.self_generated.type: basic

xpack.security.enabled: true

xpack.security.transport.ssl.enabled: true
xpack.security.transport.ssl.verification_mode: certificate
xpack.security.transport.ssl.keystore.path: certs/elastic-certificates.p12
xpack.security.transport.ssl.truststore.path: certs/elastic-certificates.p12

xpack.security.http.ssl.enabled: true
xpack.security.authc.api_key.enabled: true
xpack.security.http.ssl.keystore.path: certs/elastic-certificates.p12
xpack.security.http.ssl.truststore.path: certs/elastic-certificates.p12
xpack.security.http.ssl.verification_mode: none
xpack.security.http.ssl.client_authentication: none

xpack.monitoring.collection.enabled: false

This is the Flink CDC community. The CDC connector runs as a source. Please feed back to the Flink community about the sink connector

Closing this issue because it was created before version 2.3.0 (2022-11-10). Please try the latest version of Flink CDC to see if the issue has been resolved. If the issue is still valid, kindly report it on Apache Jira under project Flink with component tag Flink CDC. Thank you!