Unable to connect to http://localhost:8000/ in Ubuntu1804x64

Successful installation of npm and dependencies in Ubuntu1804x64
sudo apt update
sudo apt-get install nodejs-dev node-gyp libssl1.0-dev
sudo npm install -g n
sudo n stable
sudo npm install npm@latest
sudo npm install npm -g #https://stackoverflow.com/questions/29956610/error-npm-update
sudo npm install --global cross-env #https://stackoverflow.com/questions/43685777/laravel-mix-sh-1-cross-env-not-found-error

then i got this

$ npm run develop

><EMAIL_ADDRESS>develop /home/air4children/Desktop/github/site
> cross-env GATSBY_GRAPHQL_IDE=playground gatsby develop

success open and validate gatsby-configs - 0.023s
success load plugins - 0.648s
success onPreInit - 0.003s
success initialize cache - 0.010s
success copy gatsby files - 0.042s
success onPreBootstrap - 0.014s
success createSchemaCustomization - 0.005s
success source and transform nodes - 0.189s
success building schema - 0.386s
success createPages - 0.028s
success createPagesStatefully - 0.237s
success onPreExtractQueries - 0.002s
success update schema - 0.044s
success extract queries from components - 0.359s
success write out requires - 0.039s
success write out redirect data - 0.009s
success onPostBootstrap - 0.003s

info bootstrap finished - 4.238 s

success run queries - 0.070s - 9/9 127.84/s

You can now view libre-robotics-gatsby in the browser.

  http://localhost:8000/

View the GraphQL Playground, an in-browser IDE, to explore your site's data and schema

  http://localhost:8000/___graphql

Note that the development build is not optimized.
To create a production build, use gatsby build

success Building development bundle - 3.206s

—————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————
10 pages                                                             Success                                                            libre-robotics-gatsby
^C^C

but when trying this
firefox  http://localhost:8000/

I got this:
Unable to connect
Any ideas?

Installing Gatsby plugins
sudo npm install --global gatsby-cli
sudo npm i gatsby-transformer-sharp gatsby-plugin-sharp gatsby-background-image
sudo npm i gatsby-image
sudo npm i gatsby-remark-images
sudo npm i gatsby-plugin-webpack-bundle-analyzer

:warning:
found 627 vulnerabilities (622 low, 4 moderate, 1 high)
  run `npm audit fix` to fix them, or `npm audit` for details

Perhaps it is not an appropriate approach but using the following lines the site seems to work!
sudo npm run develop

google-chrome http://localhost:8000/

closed as it is outdated


Train Val split and KFold

Hi Daniel
If I understand correctly, the train validation split is done once for the whole training. Only using indices from the first fold. Once the indices are stored, for each epoch, all the batches within the train set is used to train the net and then the net is validated against the validation set. Right ?
Is it possible to train on all the folds and get the average validation loss across all the folds ?
Also, continuing, is it possible to have an access to all the validation losses in an epoch (across all the folds), s.t, I can check the std and mean both rather than checking only the minimum to finalize the best epoch ?
Thanks

To answer your first question: Yes, that's how the two sets are split up.  It's perfectly reasonable to override train_test_split with your own method in a subclass and do whatever you want.  Not sure I understand the reasoning behind training on all folds.  So you don't want to use a validation set?  I guess that's something we could support ourselves.  Maybe you can try and see what changes are required to the code to make this happen (say, when eval_size=None).  (Let's open a more specific issue or pull request for this one.)
Regarding the second question: just take a look at the train_history_ attribute; it's all in there.

Ok - Daniel
When you use KFold, in every iter of the kf, you have a different set of train indices and test indices. I am sure you are with me but just to emphasize, if I am doing 3 fold CV on a 9 element sized array. The train indices from first iter may be 123456 and val indices 789 val. In second iter, the train indices  can be 234567 train and 189 will be val indices and so on. If I take only the indices from the first iter, I will never train on some. So a generic approach is to do train and validation on all the iterations on the KFold for each model (parameters), store the validation results for all the KFold iterations, and use statistical measures across different models to compared the validation errors spread across the KFolds. So say if you are doing only on 1 iter of KFold, you might have the val error on one model as 7% and another model at 6%. You choose the second model. But this is only comparing validation on a particular set of the training instances. So - not quite right to compare. Better is to like 10 fold CV. Have 10 val errors for all the 10 iterations and then compare the distribution of the val errors across different models.
I will check the train_history_ attribute - but I guess it will not have the kind of history I just mentioned.

I see what you mean.  So for a proper cross validation I think you want to use sklearn's utlities for that.  They will give you a test set that the network will never see, and a train and validation set that the network uses for training and maybe early stopping.  So the right thing to do is to evaluate the network on held-out test set that wasn't used to train nor to validate.  Thus you'll be able to train however many networks that you want using cross-validation.
Regarding "validation losses in an epoch (across all the folds)", this isn't something that the network can do currently.  NeuralNet trains one set of parameters; if you want to train multiple networks, say to do cross-vadliation, the right thing to do is to train multiple NeuralNets (again, check scikit-learn utilities for that).  The train_history_ attribute only has validation losses for the single validation set that the single net uses.


C++17

Finally enable C++17 for devel.
The old PR contains some information on Problems that had to be solved:
https://github.com/arangodb/arangodb/pull/7066
Latest PR runs:
http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/6620/
http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/6623/

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/6623/ - OK - except for known cluster error

3rdParty/V8/CMakeLists.txt doesn't switch the MSVS version properly for gyp
no gyp support for MSVS 2019 was added

Almost everything works with MSVS 2017 an upgrade is not urgent.

no patch descriptions in 3rdParty/README_maintainers.md was added.

There is an PR that will remove the mac-hack. And the other change to V8 was taken from
upstream. -> No patching required

3rdParty/V8/CMakeLists.txt doesn't switch the MSVS version properly for gyp
no gyp support for MSVS 2019 was added

Almost everything works with MSVS 2017 an upgrade is not urgent.

MSVS usually doesn't like switching compilers in the midst of a compile of one binary. Hence its all or nothing.

80% of C++17 work with MSVC17. I think we should tackle the switch to 19 in another PR and fix the recommendation for developers. @dothebart @jsteemann what do you think?
https://docs.microsoft.com/en-us/cpp/overview/visual-cpp-language-conformance?view=vs-2019

P0961R1 Relaxing the structured bindings customization point finding rules
P0969R0 Allowing structured bindings to accessible members

?

http://jenkins.arangodb.biz:8080/job/arangodb-ANY-matrix/2/

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/6769/

http://jenkins01.arangodb.biz:8080/job/arangodb-matrix-pr-mac-onlycatch/4733/

Tests blue.


Billing flags moved from Appliance to Deployment

Billing flags (billing_state and prepaid_until) have been moved from Atmosphere::Appliance to Atmosphere::Deployment in order to properly support cases where deployments are dynamically started and shut down during the appliance's lifecycle. The billing service has been refactored to comply with this change.
A set of helper methods has been added to Atmosphere::Appliance in order to mimic the old billing flags on a "best effort" basis - this should prevent breaking backwards compatibility with systems which rely on Atmosphere APIs (CLEW and otherwise).

I've skimmed through the code. There is a lot of changes but I guess the logic is just moved to other place so it's proved to work correctly.
I'm not sure what is our policy for Hound? Should Hound complains prevent from merging code into master?

That depends on a specific case and the complaint. In general - use your own judgment ;).

Not yet ready for review but thanks all the same. :)

Small recommendation - if hound problem is fixed remove hound comment, this allows to clear a little bit PR thread.

Already cleared the duplicates but okay, will do.

All done. Deploying on prod would require us to manually set os_family for each ApplianceType but the deploy action should not break anything (all ATs will be set to "Windows").

billing_service.rb code is illegible using github file browser - take a look here. Can you reformat it and keep more/less 80 chars line long?

I just finished first code review iteration. The biggest problem I see in billing service is the usage of static methods everywhere and violation of Simple Responsibility Principle. In the feature I propose to split this service into smaller classes, which can be instantiated and which can have local context (instead of passing state using method parameters).

I'll need a full day to iterate to 2nd version (Monday). I suggest we do not make this mess of a pull request any bigger by trying to cram in a rework of the billing service along the lines proposed by @mkasztelnik (splitting service into smaller classes). I will be happy to do it in a separate branch once we get this merged & deployed; agreed?

@nowakowski definitely not in the scope of this PR, it should be improved and merged ASAP.

@mkasztelnik @tbartynski I've implemented your suggestions except as concerns refactoring specs - I believe it's wiser to do that in a separate pull request. I've also removed some excessively long lines but I generally disagree with Hound here - in this age of ultra-HD displays the 80 character limit is a classic http://www.retrologic.com/jargon/F/fossil.html :)

Great, I will do second code review round on Monday. Can you also make this PR mergable with latest master?
Also please take a look at #99 it is ready to be merged and it has already one thumb up :)
I cannot agree with your disagree :) No everyone is using whole HD display for only one window. For example take a look at my editor while working with atmosphere:

So more/less 80 to 100 chars per line in every window opened (horizontal ruler is set to 80 chars). This limit also improve readability - you don't have to move your head to read whole line :)

@mkasztelnik I've reviewed #99 as requested; found some minor issues which I hope @bwilk can address without much trouble.
Not sure why this isn't automatically mergeable but I'll perform the merge regardless after you give me those sweet :+1:s. ;)
Your screenshots indicate that your editor supports soft wrapping so where's the problem? ;)

I have it turned on just to be able to read long lines without scrolling editor, but it is much more easy to read good formatted code that long single line - just saying, I'm not forcing you to change it if you don't want to :smile:

I guess I can live with 100 characters per line... Hound still won't like me but that dog barks too much anyway. ;)

@mkasztelnik Done. I've refactored class and attribute names so you'll need to rerun your migrations locally.
Since Travis said "no", I forced an update to rvm 2.1.4. I think it was due anyway.

@tbartynski @Nuanda @mkasztelnik Guys...?

Well, it's a huge push with a lot of changes, discussions, fixes... I don't think I can any longer propose any meaningful comments to this except nitpicking. Sure some things could be written a bit different but perhaps, for the sake of the project, should we move on?

@nowakowski I will do third round (hopefully the last one :smile:) tomorrow after imsop meeting.

@nowakowski can you rebase into latest master and check if everything is working as expected? If everything is ok than at the beginning I propose to merge #114 since it solves quite serious bug and #99 (migrations for this PR are already on development), deploy it into production and then merge this one into master.
Are you OK with this plan?

@mkasztelnik Yup, but I cannot do so before Monday (there's a 50% chance I might find some time to review your latest comments on Sunday).

Travis is hiccuping.  Just a hypothesis. Could you comment on why this file was removed?

Ok, fixed - but I had to recommit schema.rb.


When attempting to download from twist.moe, I get "No module named 'Crypto'" error

Describe the bug
When I try to download an anime from twist.moe, I get a module not found error
I've also tried to download Crypto from pip, but even then, I still get the same error
To reproduce

anime dl "Dagashi Kashi" --provider twist.moe

LOG

anime dl "Dagashi Kashi" --provider twist.moe --log-level DEBUG
INFO root: anime-downloader 3.5.0
DEBUG root: Platform: Linux-4.18.10-arch1-1-ARCH-x86_64-with-arch
DEBUG root: Python 3.7.0
Traceback (most recent call last):
File "/usr/bin/anime", line 11, in
sys.exit(cli())
File "/usr/lib/python3.7/site-packages/click/core.py", line 764, in call
return self.main(*args, **kwargs)
File "/usr/lib/python3.7/site-packages/click/core.py", line 717, in main
rv = self.invoke(ctx)
File "/usr/lib/python3.7/site-packages/click/core.py", line 1137, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/usr/lib/python3.7/site-packages/click/core.py", line 956, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/usr/lib/python3.7/site-packages/click/core.py", line 555, in invoke
return callback(*args, **kwargs)
File "/usr/lib/python3.7/site-packages/click/decorators.py", line 17, in new_func
return f(get_current_context(), *args, **kwargs)
File "/usr/lib/python3.7/site-packages/anime_downloader/cli.py", line 94, in dl
anime_url = util.search(anime_url, provider)
File "/usr/lib/python3.7/site-packages/anime_downloader/util.py", line 51, in search
cls = get_anime_class(provider)
File "/usr/lib/python3.7/site-packages/anime_downloader/sites/init.py", line 21, in get_anime_class
'anime_downloader.sites.{}'.format(site[0])
File "/usr/lib/python3.7/importlib/init.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1006, in _gcd_import
File "", line 983, in _find_and_load
File "", line 967, in _find_and_load_unlocked
File "", line 677, in _load_unlocked
File "", line 728, in exec_module
File "", line 219, in _call_with_frames_removed
File "/usr/lib/python3.7/site-packages/anime_downloader/sites/twistmoe.py", line 1, in
from Crypto import Random
ModuleNotFoundError: No module named 'Crypto'

Crypto is not installed and it's last release was in 2013. To put it short, it is not included with the downloader. Even though the twist extractor is built with it in mind for some reason.

pip install pycrypto

should fix it.
Seems like I didn't add it into the requirements.

that worked for the Crypto part
now i'm getting a different error

LOG
anime dl "Dagashi Kashi" --provider twist.moe --log-level DEBUG
INFO root: anime-downloader 3.5.0
DEBUG root: Platform: Linux-4.18.10-arch1-1-ARCH-x86_64-with-arch-Arch-Linux
DEBUG root: Python 3.7.0
Traceback (most recent call last):
File "/usr/bin/anime", line 11, in
sys.exit(cli())
File "/usr/lib/python3.7/site-packages/click/core.py", line 764, in call
return self.main(*args, **kwargs)
File "/usr/lib/python3.7/site-packages/click/core.py", line 717, in main
rv = self.invoke(ctx)
File "/usr/lib/python3.7/site-packages/click/core.py", line 1137, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/usr/lib/python3.7/site-packages/click/core.py", line 956, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/usr/lib/python3.7/site-packages/click/core.py", line 555, in invoke
return callback(*args, **kwargs)
File "/usr/lib/python3.7/site-packages/click/decorators.py", line 17, in new_func
return f(get_current_context(), *args, **kwargs)
File "/usr/lib/python3.7/site-packages/anime_downloader/cli.py", line 94, in dl
anime_url = util.search(anime_url, provider)
File "/usr/lib/python3.7/site-packages/anime_downloader/util.py", line 51, in search
cls = get_anime_class(provider)
File "/usr/lib/python3.7/site-packages/anime_downloader/sites/init.py", line 21, in get_anime_class
'anime_downloader.sites.{}'.format(site[0])
File "/usr/lib/python3.7/importlib/init.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1006, in _gcd_import
File "", line 983, in _find_and_load
File "", line 967, in _find_and_load_unlocked
File "", line 677, in _load_unlocked
File "", line 728, in exec_module
File "", line 219, in _call_with_frames_removed
File "/usr/lib/python3.7/site-packages/anime_downloader/sites/twistmoe.py", line 6, in
from bs4 import BeautifulSoup
File "/usr/lib/python3.7/site-packages/bs4/init.py", line 30, in
from .builder import builder_registry, ParserRejectedMarkup
File "/usr/lib/python3.7/site-packages/bs4/builder/init.py", line 314, in
from . import _html5lib
File "/usr/lib/python3.7/site-packages/bs4/builder/_html5lib.py", line 70, in
class TreeBuilderForHtml5lib(html5lib.treebuilders._base.TreeBuilder):
AttributeError: module 'html5lib.treebuilders' has no attribute '_base'

Try reinstalling or installing inside a virtual env. This is probably caused by a different version of html5lib than needed.

how would i create a virtual env?

i was able to fix it. i needed to downgrade html5lib by doing pip install --upgrade html5lib==1.0b8. thanks for your help!

Also ran into No module named 'Crypto'
Seems like it should be part of the pip description or some such (no idea how python tracks dependencies)


I wanna Implement Smart Search with Dynamic Filtering, Interactive Animal Soundboard, and Animal Info Cards with Pop-up Modals for Wildlife Education #764

1)navbar link styling change
The first navbar link was not so stylish , and made it stylish
https://github.com/user-attachments/assets/53d16468-5668-4bd8-9f53-600a15ae0979
2)item icon hover change
The item icons not stylish so changed there styling
https://github.com/user-attachments/assets/52f3ed6a-1ed2-4297-92e3-08d9d2eedd15
3)fixed some styling issues
There was a lot of work where a proper styling where needed
https://github.com/user-attachments/assets/a7636eba-5502-4f9d-a9eb-b37131d00b95
4)animal soundboard
when the animal logo where clicked , then we have interesting animal soudn effect there
https://github.com/user-attachments/assets/aec708ca-1fb1-46ae-ad05-620bdac1c910

@anuragverma108  sir please check i had raise pull request for https://github.com/anuragverma108/WildGuard/issues/764

@rahul-chakradhari Please see the conflicts . Resolve the conflicts . Ensure you pull all the latest changes before pushing your feature/bug fixes to the main branch. After resolving the conflicts, please open a new PR for review.
Thank you!


syntax error when using lines as variable name in sqlc.slice(lines) or sqlc.arg(lines)

Version
1.27.0
What happened?
Using the word lines throws a syntax error when using mysql engine
Relevant log output
syntax error near "lines));"

Database schema
CREATE TABLE authors (
  line varchar(100)
);

SQL queries
-- name: lines :many
SELECT line FROM authors WHERE line IN (sqlc.slice(lines));

Configuration
{
  "version": "2",
  "sql": [{
    "schema": "schema.sql",
    "queries": "query.sql",
    "engine": "mysql",
    "gen": {
      "go": {
        "out": "db"
      }
    }
  }]
}

Playground URL
https://play.sqlc.dev/p/2899430310b74231cbb1ad09f41593c360f5b121dca1cadeaa17bc4da75bdb0b
What operating system are you using?
Windows
What database engines are you using?
MySQL
What type of code are you generating?
Go

Seems to be some general issue with the word lines. sqlc throws an error when table is named lines https://play.sqlc.dev/p/8da80eacd8d54c87085cfb6e626ba6a05eb9aa7bf39be022ace79bb3ece8e725

lines is a  reserved keyword in mysql
I would suggest use different names

@i-m-afk Thanks for that, this was unknown to me.


Always use all variants available in a component for selecting possible artifacts

May require follow-up work to remove ArtifactView#withVariantReselection()

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build


[BE] Verify email address endpoint returns 500 when email has invalid format

[BE][Bug#9] Verify email address endpoint returns 500 when email has invalid format

Issue moved from Project Board to Project Issues [already resolved].


Configuration file should be in the form "{ bundle: {}, copy: {} }"

How is it possible? 😆
I copied the sample-config file from the documentation and made my adjustments. Now it looks like:
Every time my console says: Configuration file should be in the form "{ bundle: {}, copy: {} }"
// bundle.config.js
module.exports = {
    bundle: {
        main: {
            styles: './content/**/*.css',
        },
        vendor: {
            scripts: [
                './node_modules/jquery/dist/jquery.js',
                './node_modules/instafeed.js/instafeed.js',
                './node_modules/slick-carousel/slick/slick.js',
            ],
        },
    },
    copy: './assets/**/*.{png,svg}',
};

npm v6.4.0
node v10.6.0
gulp v4.0.0
gulp-bundle-assetes v2.29.0

I also ran into this after upgrading to gulp, it's a compatibility issue with gulp v4.
Unfortunately it looks as if this package has no intentions of supporting gulp v4 https://github.com/dowjones/gulp-bundle-assets/issues/103

I'm having the same issue.
@chmontgomery Do you know any package can replace gulp-bundle-assets in gulp 4?

Sorry, as mentioned in #103, this package does not work with gulp 4 and I have no intentions of adding support.
In theory you could fork this repo, add a dependency on gulp 3 and shrinkwrap, then pull it into your project. That way gulp-bundle-assets would still be using gulp 3 under the covers. If anyone tries it, I'd be curious if it works.


What Happened: It wont let me transfer my DOGE to another wallet...

app logs.zip

What happened: It won't let me transfer my DOGE to another wallet.
What you expected to happen: To let me transfer my DOGE
How to reproduce it (as minimally and precisely as possible):
The continue button is grayed out which is hindering the transfer of my DOGE...
What are your environment parameters?

DeFi Wallet Version:
Operating System (OS):

Anything else we need to know?:

Hi @Cisco2794 , how you transferred DOGE to DeFi Wallet, would be the same way to transfer it back out. Tokens transferred to DeFi App are wrapped. You need to transfer DOGE back to how you initially transferred it. You can ask how-to enquiries on DeFiChain Telegram (EN).


[BUG/ISSUE] Missing translation

I've noticed in the "beta" version that differently from https://github.com/marticliment/WingetUI/pull/561/files and https://github.com/marticliment/WingetUI/pull/576/files that haven't been added to Tolgee yet, the strings below are unstranslated despite being added to Tolgee (with semicolon). I believe you could solve this problem by also adding these strings without semicolon to Tolgee:

Yes, i'll fix that


More idiomatic unveil

The use of OR in a conditional to close further unveil calls is not something I've seen in the base system of OpenBSD, this changes the calls to look more conventional. Additionally this may help debugging if one has to determine which unveil call failed.
In src/persist.c calling unveil(NULL, NULL) is unnecessary as a pledge is made immediately after without the unveil promise.
In src/sockpipe.c I have swapped the ordering of calls to pledge and unveil and removed the unveil pledge to achieve the same effect. Though this does represent a change of behavior in that should a call to unveil be made after this point it is now a fatal error as it is a pledge violation.
In src/tinypfctl.c has just been split into two distinct calls to unveil.

Accepted. Thank you.


QR code WalletConnect

Hi everyone,Can I write a custom wallet package to  generate a scanable qr code for all mobile app wallet support walletconnect instead of keplr mobile wallet , leap mobile wallet ... like curently ?
Thanks

@CaptainHoangLe That would be super great! Welcome to make PRs! Thanks :)

Opps , I wanted to know if it was possible or not. I saw wallet info is required walletconnect  option. I don't knows what i should fill in projectID.

If you have a demo for me, it will actually be super great!

mobile is optional, and projectId is required for now but you can set it a random wallet projectId temporarily. On the stage of displaying QR code, none of these two properties is really used so random is acceptable. But you need to hard code projectId and mobile info of all the wallets inside your code so that session can be build successfully

i don't really understand target about "need to hard code projectId and mobile info of all the wallets" . Is Building a WC deep link  required projectID 's mobile wallet app ? if it is true,how can i know what mobile app user will use connecting to choose fit projectID ?

WC deep link doesn't required projectID, but when session is built, which means user has used his/her mobile app to scan, you can receive info from session descriptions. you need to try it out with CosmosKit or WalletConnect Modal to see the details

Do you want to tell about it ?

you can read WalletConnect Docs to learn details about it https://docs.walletconnect.com/

I think my problem is handling the way cosmoskit use received wallet info  not from wc. I will force walletconnect in cosmoskit example and find how to customize it for my app. Thanks for your great support !  Wish you have a effective day. <3

On Thu, Dec 14, 2023 at 11:53 Viet Hoang Le @.***>
wrote:

I think my problem is handling the way cosmoskit use received wallet info
not from wc. I will force walletconnect in cosmoskit example and find how
to customize it for my app. Thanks for your great support ! Wish you have a
effective day. <3
—
Reply to this email directly, view it on GitHub
https://github.com/cosmology-tech/cosmos-kit/issues/367#issuecomment-1855086846,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKRQJSJ7UGU2K7YFFXYXVDLYJJZ3NAVCNFSM6AAAAAA7YWKVUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJVGA4DMOBUGY
.
You are receiving this because you commented.Message ID:
@.***>

Thanks :)

thanks :)


date-field deserialization converts to UTC, picker UI is off

The date picker will behave strangely, i.e. not select the dates correctly by being off by a day. The reason this is an issue and not a pull-request, is because I'm not sure what the solution should be. The below example fixes it for me, but may not b e the right solution for everyone?

I fixed it with the following in components/form-fields/date-field.js:
import Ember from 'ember';
import DateField from 'ember-form-for/components/form-fields/date-field';

const { isEmpty } = Ember;

export default DateField.extend({
  deserializeValue(value) {
    if (isEmpty(value)) {
      return null;
    }

    let date = new Date(value);
    return convertUTCDateToLocalDate(date);
  }
});

function convertUTCDateToLocalDate(date) {
  let newDate = new Date(date.getTime() + date.getTimezoneOffset() * 60 * 1000);
  let offset = date.getTimezoneOffset() / 60;
  let hours = date.getHours();

  newDate.setHours(hours - offset);

  return newDate;
}

Amazing. I did some research and it looks like it might be caused by the same thing as this post.
http://blog.skylight.io/bringing-sanity-to-javascript-utc-dates-with-moment-js-and-ember-data/
It seems like it's a clash between the selector being in UTC and the display being local time?

This is just an issue with the HTML date input. It would be an issue without this addon, I believe. What would you guys think of replacing the date type input in this addon with flatpickr? https://github.com/shipshapecode/ember-flatpickr

@knownasilya I like the idea, I will create a PR for this before next beta.

I have found additional issue with date formats. Postponing this solution after migrating from ember-onw-way-controls.


Missing index on table group_membership for postgres

Hi
we noticed a high SQL execution time for uaa startup on postgress, if there are millions of groups.
The SQL statement causes the high load times is:
select count(*) from group_membership where group_id in (select id from groups where
identity_zone_id='uaa') and LOWER(group_id) = LOWER(?)
was running for several seconds, up to 20 sec.
After we defined an index for it
CREATE INDEX group_membership_group ON group_membership(LOWER(group_id));
the problems get solved and startup times were ok.
Do you noticed similar issues on postgres? Can you please add this index ?
thanks in advance and regards,
-markus

https://www.pivotaltracker.com/story/show/148308021


Added option to pipe report-specific output to file

We could also upgrade arachni to 1.1 and nokogiri to 1.6.5 but that means we have to drop 1.9 support. There's no direct reason for upgrading those two other than they are pretty old. Is there any value to maintaining 1.9 support?

I'm fine with the upgrades and dropping ruby 1.9. What do you think @wickett ?

I don't think so @cgotcu! @wickett ping on this.

This looks great.  This fell off my radar and I am sorry for not merging this until now.  Thanks @cgotcu

hmm, that just broke that travis build

I will have to take a look later tonight at it


All constructs of an application are set as entry points in A2C goal

Is your feature request related to a problem? Please describe.
I noticed that all the constructs of an application are set as entry points in the goal A2C, including private, protected, and package level methods, which significantly increase the time to build the call graph and they are not valid entry points.
Describe the solution you'd like
Add a column to store the access modifier of a construct. For example:
{"lang":"JAVA","type":"METH","qname":"com.example.foo()", "access":"public"}
{"lang":"JAVA","type":"METH","qname":"com.example.bar()", "access":"public"}
Then in the code responsible for setting the entry points of the call graph, we can filter by public access modifiers.
Describe alternatives you've considered
Running external code and try to create Regex to filter only relative entry points.

That's true, we decided some time back to use all application methods as entry points for the CG construction, and I also agree that there's some room for discussions.
The main reasoning back then was the assumption that every method of the application matters - unless it is dead code (but we wanted to stay out of dead code detection).
I think the advantage compared to starting only from the application's main method is to catch more method invocations. Take a Spring application as example: It's main method defers to Spring-specific logic pretty quickly, which calls back into your application at later points in time. The risk of starting with main is that such call backs are missed, hence, the invocations performed by the application's callback methods would not become part of the CG.
Having said that, it could be worthwhile to compare the CGs created by the current implementation and one "simulating" your suggestion, which can for a given application be done by configuring the following:
# Regex to filter entry points (semicolon separated)
vulas.reach.constructFilter =

Of course, the comparison should consider the CG size, generation time and possibly a number of other features.
@serenaponta Anything to add from your PoV?

@henrikplate Thank you very much for the feedback.
If we include only public methods as entry points, would that still keep the advantage of "catching more method invocations"?
Because I don't see the point of adding a private method as an entry point for example (please correct me if there is an advantage).

In terms of static analysis, I very much see the point of only considering a dependency's public methods, because this is what constitutes its API and can be effectively called by clients.
In case of an application, however, we always argued that every application method is relevant for the application developer, no matter its visibility. Otherwise it would not exist...
I theory, all non-public methods of an application should be reachable from its public methods, e.g. from the main method or HTTP handler methods in case of Servlets. However, the Spring example illustrates that this can be difficult in case of framework dependencies that use dependency injection and callbacks.

As @henrikplate wrote, we thought that considering all application methods as entry points was an easy way to get as many invocations as possible. In fact, starting from a "main" or all public methods makes the analysis more prone to all limitations that static analysis is known to have. On top of the Spring example from Henrik, starting from public methods may be subject to false negatives if the application makes use of dynamic features for invoking private methods from public ones.
Assuming that there isn't any dead code in the application, intuitively i would say that both cases (public methods versus all methods) should yield to "comparable" CG as private methods should be used by public ones; the difference could be an indicator of "non-standard" invocations like callbacks, dependency injection, etc.
It would indeed be interesting to quantify the difference and the performance gain in case entry points are restricted to public methods: in my view a considerable performance gain may justify to miss some findings depending on the use case.

I'm interested in the idea of comparing the CGs too. Please share your thoughts on the comparison parameters (e.g., what lib/framework candidate, CG metrics ..etc). Thank you very much for your time.


Cow: Watch 32dental.com

Cow requests the watch of the watch_keyword 32dental\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

32dental\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


Automated component docs ADR

These changes propose an ADR to help us resolve https://github.com/github/primer/issues/3258 using automation tools such as react-docgen-typescript.
Related PR: https://github.com/primer/react/pull/4466

@joshblack and other reviewers - I'd really love to come to a decision with this ADR so we can fix our component prop docs.
If we reject the ADR, I'll use my work on https://github.com/primer/react/pull/4466 to manually update inaccurate .docs.json files.
If we approve the ADR, I'll apply all the feedback to https://github.com/primer/react/pull/4466 so we can get it reviewed and merged.

These two questions are my biggest blockers:

How we should transition from the current components.json output to the new improved components.json output. In this comment we decided we'll slowly remove *.docs.json files, but I still have some questions:

Should we have two components.json files? Or just keep the one at generated/components.json? My preference is to keep the existing one
How might we plan the slow removal of *.docs.json files into our usual work streams?

How we do want to handle generating and snapshot-testing components.json?

Require contributors to run the script locally?
GitHub action like we do for VRT snapshots?

I think the automation-route sounds great! Especially if we can complement with manual documentation for the (hopefully) few components that don't follow the "happy path", also wondering if we have a rough idea of how many those would be 👀.  Some thoughts:

A Github action to snapshot test against components.json sounds good to me.
Agree with @joshblack here on slow phase-out of individual component docs.
Regarding modifying the author experience, wondering just how cumbersome that would be? is it just relating to the way the components are exported as explained in the Gotchas/workarounds and adding the JSDocs updates, or is there more to it?
Also think one components.json file probably makes sense if we followed the proposed rollout plan of using a script action to build, monitor and improve the automation until we're happy with it and ready to switch over.

Regarding https://github.com/primer/react/pull/4727#discussion_r1671099407, wondering just how cumbersome that would be? is it just relating to the way the components are exported as explained in the Gotchas/workarounds and adding the JSDocs updates, or is there more to it?

Nope, there's nothing more to it than that.

Closing this until we revisit


Show entire map title in embeds

I'm not sure if we want to get into this or wait until we develop the public pages, but... given the amount of space available, we should show the entire map title here:

Issue moved to CartoDB/deep-insights.js #578 via ZenHub


Leaked UB in enums

The docs for #[pin_project] attribute state:

This attribute is completely safe. In the absence of other unsafe code that you write, it is impossible to cause undefined behavior with this attribute.

However, somehow we've managed to accidentally hit it in the following code:
#[pin_project(project = SessionProj)]
#[derive(From)]
pub enum Session<M: meta::Input> {
    Init(#[pin] Init<M>),
    Connected(#[pin] Connected<M>),
    Terminated,
}

impl<M: meta::Input> Stream for Session<M> {
    type Item = String;

    fn poll_next(
        mut self: Pin<&mut Self>,
        cx: &mut Context<'_>,
    ) -> Poll<Option<Self::Item>> {
        let action = match self.as_mut().project() {
            SessionProj::Init(s) => s.poll_next(cx),
            SessionProj::Connected(s) => s.poll_next(cx),
            SessionProj::Terminated => return Poll::Ready(None),
        };

        if let Some(into_phase) = action.transition {
            // This line causes the UB.
            let curr_phase = mem::replace(&mut *self, Self::Terminated);
            let new_phase = match (curr_phase, into_phase) {
                (Self::Init(s), Transition::Connected) => {
                    Self::Connected(s.into())
                }
                (_, Transition::Terminated) => Self::Terminated,
                _ => unreachable!(),
            };
            *self = new_phase;
            // And here, at the end of this block we do receive segfault on `Drop`.
        }

        action.result
    }
}

It seems that we've violated structural Pin guarantees by moving the pinned field, because project_replace doesn't allow us to do the same we're doing with mem::replace here. Also, wrapping the field into Option like this Connected(#[pin] Option<Connected<M>>) helped (as we now moving not the whole Option, but its content only).
Another way we're testing at the moment is removing structural pinning from the enum and doing it more precisely
        let action = match self.as_mut().project() {
            SessionProj::Init(s) => Pin::new(s).poll_next(cx),
            SessionProj::Connected(s) => Pin::new(s).poll_next(cx),
            SessionProj::Terminated => return Poll::Ready(None),
        };

so we're not trying to move pinned fields at all.
But the thing that worries us a lot, that it has been introduced without any portion of unsafe from user code, so we were expecting a compile error if something with Pining is not correct.
I'm still not sure I do understand the issue causes correctly, we still do test different code variants to make sure it's raised by #[pin_project] and not our user code. But if it's really a soundness hole, we should figure out some way to close it.

@tyranron Can you share your repository?

@Aaron1011 unfortunately, no. It's a closed source. And we haven't managed to create MRE.

Looking at the code you've provided, I think Session is incorrectly ending up as Unpin. As a result,  Pin<&mut Self> ends up implementing DerefMut, allowing you to overwrite the underlying enum after pinning it.
What crate is providing #[derive(From)]?  Could you post the definitions of Init and Connected? Could you also try to get the generated Unpin impl from cargo expand?

@Aaron1011

What crate is providing #[derive(From)]?

It's derive_more. It generates no unsafe.

Could you also try to get the generated Unpin impl from cargo expand?

    pub(crate) enum SessionProj<'pin, M: meta::Input>
    where
        Session<M>: 'pin,
    {
        Init(::pin_project::__private::Pin<&'pin mut (Init<M>)>),
        Connected(::pin_project::__private::Pin<&'pin mut (Connected<M>)>),
        Terminated,
    }

    const _: () = {
        impl<M: meta::Input> Session<M> {
            pub(crate) fn project<'pin>(
                self: ::pin_project::__private::Pin<&'pin mut Self>,
            ) -> SessionProj<'pin, M> {
                unsafe {
                    match self.get_unchecked_mut() {
                        Self::Init(_0) => {
                            SessionProj::Init(::pin_project::__private::Pin::new_unchecked(_0))
                        }
                        Self::Connected(_0) => {
                            SessionProj::Connected(::pin_project::__private::Pin::new_unchecked(_0))
                        }
                        Self::Terminated => SessionProj::Terminated,
                    }
                }
            }
        }
        #[allow(missing_debug_implementations)]
        pub struct __Session<'pin, M: meta::Input> {
            __pin_project_use_generics: ::pin_project::__private::AlwaysUnpin<
                'pin,
                (::pin_project::__private::PhantomData<M>),
            >,
            __field0: Init<M>,
            __field1: Connected<M>,
        }
        impl<'pin, M: meta::Input> ::pin_project::__private::Unpin for Session<M> where
            __Session<'pin, M>: ::pin_project::__private::Unpin
        {
        }
        #[doc(hidden)]
        unsafe impl<'pin, M: meta::Input> ::pin_project::UnsafeUnpin for Session<M> where
            __Session<'pin, M>: ::pin_project::__private::Unpin
        {
        }
        trait SessionMustNotImplDrop {}
        #[allow(clippy::drop_bounds, drop_bounds)]
        impl<T: ::pin_project::__private::Drop> SessionMustNotImplDrop for T {}
        impl<M: meta::Input> SessionMustNotImplDrop for Session<M> {}
        #[doc(hidden)]
        impl<M: meta::Input> ::pin_project::__private::PinnedDrop for Session<M> {
            unsafe fn drop(self: ::pin_project::__private::Pin<&mut Self>) {}
        }
    };

Could you post the definitions of Init and Connected?

#[pin_project]
pub struct Init<M: meta::Input> {
    pub(super) input: Pin<Box<M::Input>>,
    pub(super) coordinator: M::CoordinatorRef,
    pub(super) context: M::Context,
}

expanded:
```rust
    const _: () = {
        #[allow(dead_code)]
        #[allow(clippy::mut_mut)]
        pub(crate) struct __InitProjection<'pin, M: meta::Input>
        where
            Init: 'pin,
        {
            pub(super) input: &'pin mut (Pin>),
            pub(super) coordinator: &'pin mut (M::CoordinatorRef),
            pub(super) context: &'pin mut (M::Context),
        }
        #[allow(dead_code)]
        #[allow(clippy::ref_option_ref)]
        pub(crate) struct __InitProjectionRef<'pin, M: meta::Input>
        where
            Init: 'pin,
        {
            pub(super) input: &'pin (Pin>),
            pub(super) coordinator: &'pin (M::CoordinatorRef),
            pub(super) context: &'pin (M::Context),
        }
        impl Init {
            pub(crate) fn project<'pin>(
                self: ::pin_project::__private::Pin<&'pin mut Self>,
            ) -> __InitProjection<'pin, M> {
                unsafe {
                    let Self {
                        input,
                        coordinator,
                        context,
                    } = self.get_unchecked_mut();
                    __InitProjection {
                        input,
                        coordinator,
                        context,
                    }
                }
            }
            #[allow(clippy::missing_const_for_fn)]
            pub(crate) fn project_ref<'pin>(
                self: ::pin_project::__private::Pin<&'pin Self>,
            ) -> __InitProjectionRef<'pin, M> {
                unsafe {
                    let Self {
                        input,
                        coordinator,
                        context,
                    } = self.get_ref();
                    __InitProjectionRef {
                        input,
                        coordinator,
                        context,
                    }
                }
            }
        }
        #[forbid(unaligned_references, safe_packed_borrows)]
        fn __assert_not_repr_packed(this: &Init) {
            let _ = &this.input
            let _ = &this.coordinator
            let _ = &this.context
        }
        #[allow(missing_debug_implementations)]
        pub struct __Init<'pin, M: meta::Input> {
            __pin_project_use_generics: ::pin_project::__private::AlwaysUnpin<
                'pin,
                (::pin_project::__private::PhantomData),
            >,
        }
        impl<'pin, M: meta::Input> ::pin_project::__private::Unpin for Init where
            __Init<'pin, M>: ::pin_project::__private::Unpin
        {
        }
        #[doc(hidden)]
        unsafe impl<'pin, M: meta::Input> ::pin_project::UnsafeUnpin for Init where
            __Init<'pin, M>: ::pin_project::__private::Unpin
        {
        }
        trait InitMustNotImplDrop {}
        #[allow(clippy::drop_bounds, drop_bounds)]
        impl InitMustNotImplDrop for T {}
        impl InitMustNotImplDrop for Init {}
        #[doc(hidden)]
        impl ::pin_project::__private::PinnedDrop for Init {
            unsafe fn drop(self: ::pin_project::__private::Pin<&mut Self>) {}
        }
    };
```

#[pin_project(PinnedDrop)]
pub struct Connected<M: meta::Input> {
    input: Pin<Box<M::Input>>,
    coordinator: M::CoordinatorRef,
    context: M::Context,
    #[pin]
    keep_alive: time::Interval,
    data: HashMap<String, Pin<Box<SubscriptionContext<M>>>>,
    starting: StartingOperations<M::Connection, M::Error>,
    ongoing: HashMap<String, Pin<Box<M::Connection>>>,
}

#[pinned_drop]
impl<M: meta::Input> PinnedDrop for Connected<M> {
    fn drop(mut self: Pin<&mut Self>) {
        drop(mem::take(&mut self.as_mut().starting));
    }
}

expanded:
```rust
        const _: () = {
            #[allow(dead_code)]
            #[allow(clippy::mut_mut)]
            pub(crate) struct __ConnectedProjection<'pin, M: meta::Input>
            where
                Connected: 'pin,
            {
                input: &'pin mut (Pin>),
                coordinator: &'pin mut (M::CoordinatorRef),
                context: &'pin mut (M::Context),
                keep_alive: ::pin_project::__private::Pin<&'pin mut (time::Interval)>,
                data: &'pin mut (HashMap>>>),
                starting: &'pin mut (StartingOperations),
                ongoing: &'pin mut (HashMap>>),
            }
            #[allow(dead_code)]
            #[allow(clippy::ref_option_ref)]
            pub(crate) struct __ConnectedProjectionRef<'pin, M: meta::Input>
            where
                Connected: 'pin,
            {
                input: &'pin (Pin>),
                coordinator: &'pin (M::CoordinatorRef),
                context: &'pin (M::Context),
                keep_alive: ::pin_project::__private::Pin<&'pin (time::Interval)>,
                data: &'pin (HashMap>>>),
                starting: &'pin (StartingOperations),
                ongoing: &'pin (HashMap>>),
            }
            impl Connected {
                pub(crate) fn project<'pin>(
                    self: ::pin_project::__private::Pin<&'pin mut Self>,
                ) -> __ConnectedProjection<'pin, M> {
                    unsafe {
                        let Self {
                            input,
                            coordinator,
                            context,
                            keep_alive,
                            data,
                            starting,
                            ongoing,
                        } = self.get_unchecked_mut();
                        __ConnectedProjection {
                            input,
                            coordinator,
                            context,
                            keep_alive: ::pin_project::__private::Pin::new_unchecked(keep_alive),
                            data,
                            starting,
                            ongoing,
                        }
                    }
                }
                #[allow(clippy::missing_const_for_fn)]
                pub(crate) fn project_ref<'pin>(
                    self: ::pin_project::__private::Pin<&'pin Self>,
                ) -> __ConnectedProjectionRef<'pin, M> {
                    unsafe {
                        let Self {
                            input,
                            coordinator,
                            context,
                            keep_alive,
                            data,
                            starting,
                            ongoing,
                        } = self.get_ref();
                        __ConnectedProjectionRef {
                            input,
                            coordinator,
                            context,
                            keep_alive: ::pin_project::__private::Pin::new_unchecked(keep_alive),
                            data,
                            starting,
                            ongoing,
                        }
                    }
                }
            }
            #[forbid(unaligned_references, safe_packed_borrows)]
            fn __assert_not_repr_packed(this: &Connected) {
                let _ = &this.input
                let _ = &this.coordinator
                let _ = &this.context
                let _ = &this.keep_alive;
                let _ = &this.data
                let _ = &this.starting
                let _ = &this.ongoing
            }
            #[allow(missing_debug_implementations)]
            pub struct __Connected<'pin, M: meta::Input> {
                __pin_project_use_generics: ::pin_project::__private::AlwaysUnpin<
                    'pin,
                    (::pin_project::__private::PhantomData),
                >,
                __field0: time::Interval,
            }
            impl<'pin, M: meta::Input> ::pin_project::__private::Unpin for Connected where
                __Connected<'pin, M>: ::pin_project::__private::Unpin
            {
            }
            #[doc(hidden)]
            unsafe impl<'pin, M: meta::Input> ::pin_project::UnsafeUnpin for Connected where
                __Connected<'pin, M>: ::pin_project::__private::Unpin
            {
            }
            impl ::pin_project::__private::Drop for Connected {
                fn drop(&mut self) {
                    unsafe {
                        let __pinned_self = ::pin_project::__private::Pin::new_unchecked(self);
                        ::pin_project::__private::PinnedDrop::drop(__pinned_self);
                    }
                }
            }
        };
        #[doc(hidden)]
        impl ::pin_project::__private::PinnedDrop for Connected {
            unsafe fn drop(self: Pin<&mut Self>) {
                #[allow(clippy::needless_pass_by_value)]
                fn __drop_inner(mut __self: Pin<&mut Connected>) {
                    fn __drop_inner() {}
                    drop(mem::take(&mut __self.as_mut().starting));
                }
                __drop_inner(self);
            }
        }
        /// Helper alias for a [`HashMap`] containing starting GraphQL operations.
        type StartingOperations = HashMap>>;
        impl From> for Connected {
            fn from(init: Init) -> Self {
                Self {
                    input: init.input,
                    coordinator: init.coordinator,
                    context: init.context,
                    keep_alive: time::interval(Duration::from_secs(1)),
                    data: HashMap::new(),
                    starting: HashMap::new(),
                    ongoing: HashMap::new(),
                }
            }
        }
```

@tyranron What crate is time::Interval from?
Also, could you post the source code for the poll_next methods on Init and Connected?

@Aaron1011

What crate is time::Interval from?

It's tokio one.

Also, could you post the source code for the poll_next methods on Init and Connected?

Init::poll_next
impl<M: meta::Input> Init<M> {
    pub fn poll_next(mut self: Pin<&mut Self>, cx: &mut Context<'_>) -> Action {
        let msg = match self.input.as_mut().poll_next(cx) {
            Poll::Ready(Some(m)) => m,
            Poll::Ready(None) => return action::terminated(),
            Poll::Pending => return action::pending(),
        };

        let msg = match serde_json::from_str::<message::Input<M::Scalar>>(&msg) {
            Ok(m) => m,
            Err(e) => return action::invalid_message::<M, _>(&msg, &e),
        };

        if let message::Input::Initialize { payload } = msg {
            if let Some(params) = payload {
                self.context.apply_ws_connect_params(params);
            }
            action::connected::<M>()
        } else {
            Self::unexpected_message()
        }
    }
}

From Init to Connected
impl<M: meta::Input> From<Init<M>> for Connected<M> {
    fn from(init: Init<M>) -> Self {
        Self {
            input: init.input,
            coordinator: init.coordinator,
            context: init.context,
            keep_alive: time::interval(Duration::from_secs(1)),
            data: HashMap::new(),
            starting: HashMap::new(),
            ongoing: HashMap::new(),
        }
    }
}

Connected::poll_next
impl<M: meta::Input> Connected<M> {
    pub fn poll_next(mut self: Pin<&mut Self>, cx: &mut Context<'_>) -> Action {
        self.as_mut()
            .poll_input_messages(cx)
            .or_else(|| self.as_mut().poll_keep_alive(cx))
            .or_else(|| self.as_mut().poll_starting_operations(cx))
            .unwrap_or_else(|| self.poll_ongoing_operations(cx))
    }

    fn poll_input_messages(
        mut self: Pin<&mut Self>,
        cx: &mut Context<'_>,
    ) -> Option<Action> {
        loop {
            let msg = match self.input.as_mut().poll_next(cx) {
                Poll::Ready(Some(m)) => m,
                Poll::Ready(None) => {
                    return Some(action::terminated());
                }
                Poll::Pending => break,
            };

            let msg =
                match serde_json::from_str::<message::Input<M::Scalar>>(&msg) {
                    Ok(m) => m,
                    Err(e) => {
                        return Some(action::invalid_message::<M, _>(&msg, &e));
                    }
                };

            match msg {
                message::Input::Start { id, .. } if self.is_registered(&id) => {
                    return Some(Self::operation_already_exists(&id));
                }
                message::Input::Start { id, payload: req } => {
                    self.start(id, req);
                }
                message::Input::Stop { id } => {
                    self.stop(&id);
                }
                message::Input::Terminate => {
                    return Some(action::terminated());
                }
                message::Input::Initialize { .. } => {
                    return Some(Self::unexpected_message());
                }
            }
        }
        None
    }

    fn poll_keep_alive(
        mut self: Pin<&mut Self>,
        cx: &mut Context<'_>,
    ) -> Option<Action> {
        matches!(self.keep_alive.poll_tick(cx), Poll::Ready(_)).then(|| {
            action::message::<M>(&message::Output::keep_alive())
        })
    }

    fn poll_starting_operations(
        mut self: Pin<&mut Self>,
        cx: &mut Context<'_>,
    ) -> Option<Action> {
        let mut resolved = Vec::new();
        for (id, req) in &mut self.starting {
            if let Poll::Ready(conn) = req.as_mut().poll(cx) {
                let is_err = conn.is_err();
                resolved.push((id.clone(), conn));
                if is_err {
                    break;
                }
            }
        }
        for (id, conn) in resolved {
            match conn {
                Ok(c) => self.started(id, c),
                Err(e) => return Some(self.error(id, e)),
            }
        }
        None
    }

    fn poll_ongoing_operations(
        mut self: Pin<&mut Self>,
        cx: &mut Context<'_>,
    ) -> Action {
        let mut resp = None;
        for (id, conn) in &mut self.ongoing {
            if let Poll::Ready(r) = conn.as_mut().poll_next(cx) {
                resp = Some((id.clone(), r));
                break;
            }
        }
        match resp {
            Some((id, Some(resp))) => {
                action::message::<M>(&message::Output::data(id, resp))
            }
            Some((id, None)) => {
                self.complete(id)
            }
            None => {
                action::pending()
            }
        }
    }
}

Interval is Unpin,  so your Session enum is legitimately Unpin. Can you share the stacktrace you're getting from the default? I suspect that the bug is in some other code (maybe the concrete type being used for M). Is the type implementing meta::Input from a closed source crate as well?
Would it be possible for you to share the repository with me privately? It would really speed up the process of narrowing down the cause of the bug?

Would it be possible for you to share the repository with me privately?

Unfortunately, no. This is not permited for me by the job contract.
The bug is not persitent. It doesn't reproduce neither on our CI or production workloads (amd64 arch), but does reproduce very oftenly (but still sporadically) on Apple M1 machine (arm I guess?) for one of our developers (for another one with M1 this somehow is fine).
After applying the fixes, and running E2E tests for the whole night, the bug didn't reproduce, but there have appeared new similar segfaults in other parts of code. Now I have strong feeling this is really not pin-project related one, so I'm closing this issue for now, to not make false positive claims. After we finish investigation completely, I'll mention here the causes and will re-open (if it will make sense).

It would really speed up the process of narrowing down the cause of the bug?

@Aaron1011 thank you for your effort, patience and help with this.
One last question: as we cannot share the codebase, could you advice us some techniques for better narrowing the bug? At the moment we do trace this with LLDB, but the cause is quite opaque doing so.

One last question: as we cannot share the codebase, could you advice us some techniques for better narrowing the bug? At the moment we do trace this with LLDB, but the cause is quite opaque doing so.

Can you elaborate on the problems you're running into with LLDB?

@Aaron1011

Can you elaborate on the problems you're running into with LLDB?

There were no problems with LLDB, but rather with us being a little bit unused to such deep debug trips 😅
In the end, it turned out to be a system allocator problem on cfg(all(target_os = "macos", target_arch = "aarch64")). Somehow it returned bad memory on allocation under some circumstances. It's still not quite clear why. But switching to mimalloc or jemalloc on that arch removed all the problems completely.
We are now trying to construct MRE (which is hard) and report it to upstream, but with lower effort.
Thanks again.


Improved performance of loading embedding matrix

Use Queue's from the multiprocessing library to speed up the loading times of the embedding layer. Also, use the knowledge of the sampling to not having to load the whole matrix into memory.
On a MacBook Pro Retina 2012 there is a 10x speed up, now loading in approximately 30s.

Nice PR and nice speed up.
Is there a reason to choose queus over a pool?

I'm no expert on either, but Queue's seem more convenient with a simultaneous IO/worker process configuration? Pool's seem more useful when all the data is already present.

Shall we add a unittest before merging?

And a function to download the embedding?

I added unit tests, including testing for the URL you gave me. (Obviously it all passes.)
I think all the things you mentioned are resolved.
One possible issue: if one of the processes gets an exception, the others will deadlock. Obviously, the error will still be raised. Solution would be a try/except block that only raises an error after everything will be joined. But of course the whole thing would be one more indented to the right...

Please rebase.

Can you add the following line to the init.py of the module?
from asr.models.embedding import load_embedding, sample_embedding

Should be able to merge now?

What time should I think of? It takes ages (or hangs) on my machine.
In [1]: import asr

In [2]: %timeit asr.load_embedding("/Users/jonathan/asr_data/fasttext.cc.en.300.vec")
Reading 2000000 vectors with 300 dimensions.

Hmmm, with 1 core and no sampling it should be similar to what it was before, so 5 min perhaps (depending on hardware obviously)?
On 12 Mar 2019, at 16:30, Jonathan de Bruin <notifications<EMAIL_ADDRESS>wrote:
What time should I think of? It takes ages (or hangs) on my machine.
In [1]: import asr
In [2]: %timeit asr.load_embedding("/Users/jonathan/asr_data/fasttext.cc.en.300.vec")
Reading 2000000 vectors with 300 dimensions.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/msdslab/automated-systematic-review/pull/9#issuecomment-472046772, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Aqb8sLCGklHO0Vps18XXM1N2wkPTv6aZks5vV8gtgaJpZM4bJvqd.


[refactor proposal] Separate existing and draft media

The useMediaFiles hook and other media management code is a mess, especially because the behaviour is very different between the media library tab and the draft entry editor.
To make it easier to maintain, I propose to separate 'media files' which already exist in a folder and are being retrieved from the backend, and 'media operations', which contain file replacement, creation and deletion.
This would consist of the following changes:

add mediaOperations to Entry interface
simplify useMediaFiles to a unified method
implement a method to put mediaFiles and mediaOperations together
refactor creation, deletion and replacement behaviour -> possibility: implement "draft deleting" inside entries, batch media operations

I would try to implement this refactor, but first I want to know what you think about it @KaneFreeman

That sounds like a good approach to me.


Default vagrant version is 18.04 not 20.04

I am trying to build the sd image and follow the instruction started with vagrant.
The instruction https://pynq.readthedocs.io/en/v2.7.0/pynq_sd_card.html says

But what I got is 18.04.
And check the source in the Vagrantfile also says disk image is 18.04

Should I use the 18.04 or 20.04? Or even better, will 22.04 work?

We will move to docker flows in the future. If this is still an issue re-open it as a [discuss.pynq.io](https://discuss.pynq.io/) post.


Documentation highlights not consistent (and impossible to fix by highlighting all of the cmp highlight groups)

FAQ

[X] I have checked the FAQ and it didn't resolve my problem.

Announcement

[X] I have checked Breaking change announcement.

Minimal reproducible full config

Description

Inconsistent cmp highlighting when opening documentation, and not of the hi groups fix it, i tried changing all of them.
As you can see, i have some parts that are with a darker background, and i want to find it and fix it.
I tried changing all of the highlight groups that start with Cmp:

And yet wasn't able to find the one that highlights it.
Steps to reproduce
Just open a cmp completion window.
Expected behavior
To find the highlight group.
Actual behavior
Changed all of the cmp highlight groups and none of them highlights it. Its coming from somewhere else.
Additional context
No response

i tryed to mess with the hi groups, found out only these want to work:
select menu:
:lua vim.api.nvim_set_hl(0,'PMenu',{ bg='#ffffff' })
docs float window (this one is weird, like the inner inhert hi group from floatborder and after change inner stays same as it was, when i use transparency plugin to clean the hi group before it loads  the whole window of docs lose color):
:lua vim.api.nvim_set_hl(0,'FloatBorder',{ bg='#ffffff' })


⚠ ClamAV has degraded performance

In 29134a4, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 596 ms

Resolved: ClamAV performance has improved in 268f05d.


[Event Request] Table 9053 "Sales Cue" - OnCalculateAverageDaysDelayedOnBeforeSumDelayDays

We are migrating our code from NAV 2018 to BC16.4. In the Table 9053 "Sales Cue", in the procedure CalculateAverageDaysDelayed, we need to add a condition inside the repeat. To do so, we need a IsHandled flag and an event publisher, like this :

With this integration event :

Do you think it could be possible ?
Thank you for your work.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


No way to connect label & input via htmlFor and name

I would like to see (or contribute) a way to connect DatePicker labels with their input elements by setting htmlFor prop on the label and name prop on the input tag.
The reason I would like to see this is because react-testing-library uses this convention to select elements from the DOM.
Let me know what you think.

It’s already possible because of possibility to pass down all the props to material ui TextField component. So you can use

It’s already possible because of possibility to pass down all the props to material ui TextField component. So you can use inputProps and InputProps for this purpose

Thank you sir


modify src\bin\initdb\polar-initdb.sh for delete local_data/base/*

rm_dir ${local_data}base/${pFile}/* can't delete files completely，need to delete cyclically

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


Update examples requirements for sdk3.3

What does this PR do?
Updates the torchaudio and torchvision versions in the requirements files.

Fixes # (issue)
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


//tensorflow/compiler/xla/service/gpu:fusion_merger_test fails on AARCH64

Issue type
Bug
Have you reproduced the bug with TensorFlow Nightly?
Yes
Source
source
TensorFlow version
git HEAD
Custom code
No
OS platform and distribution
Ubuntu 20.04
Mobile device
n/a
Python version
3.9.17
Bazel version
6.1.0
GCC/compiler version
10.2.1
CUDA/cuDNN version
n/a
GPU model and memory
n/a
Current behavior?
//tensorflow/compiler/xla/service/gpu:fusion_merger_test unit test fails when run on AARCH64 machine.
Standalone code to reproduce the issue
bazel test --cache_test_results=no --config=mkl_aarch64_threadpool --jobs=75 --copt=-flax-vector-conversions --test_env=TF_ENABLE_ONEDNN_OPTS=1 --test_env=TF2_BEHAVIOR=1 --define=tf_api_version=2 --test_output=errors --verbose_failures=true --test_keep_going --notest_verbose_timeout_warnings --build_tests_only -- //tensorflow/compiler/xla/service/gpu:fusion_merger_test

Relevant log output
FAIL: //tensorflow/compiler/xla/service/gpu:fusion_merger_test (see /home/andrew/src/tf_test/tensorflow-git/bazel-ci_build-cache/.cache/bazel/_bazel_andrew/eab0d61a99b6696edb3d2aff87b585e8/execroot/org_tensorflow/bazel-out/aarch64-opt/testlogs/tensorflow/compiler/xla/service/gpu/fusion_merger_test/test.log)
INFO: From Testing //tensorflow/compiler/xla/service/gpu:fusion_merger_test:
==================== Test output for //tensorflow/compiler/xla/service/gpu:fusion_merger_test:
[==========] Running 21 tests from 1 test suite.
[----------] Global test environment set-up.
[----------] 21 tests from FusionMergerTest
[ RUN      ] FusionMergerTest.MergeSharedFusionInstruction
[       OK ] FusionMergerTest.MergeSharedFusionInstruction (9 ms)
[ RUN      ] FusionMergerTest.MoreMemoryAccessIfFused
[       OK ] FusionMergerTest.MoreMemoryAccessIfFused (1 ms)
[ RUN      ] FusionMergerTest.LessMemoryAccessIfFused
[       OK ] FusionMergerTest.LessMemoryAccessIfFused (1 ms)
[ RUN      ] FusionMergerTest.WillMergeIntoInputFusion
[       OK ] FusionMergerTest.WillMergeIntoInputFusion (1 ms)
[ RUN      ] FusionMergerTest.WillMergeIntoUnfusedConsumer
[       OK ] FusionMergerTest.WillMergeIntoUnfusedConsumer (1 ms)
[ RUN      ] FusionMergerTest.WillNotMergeReduceUnfriendlyLayouts
[       OK ] FusionMergerTest.WillNotMergeReduceUnfriendlyLayouts (0 ms)
[ RUN      ] FusionMergerTest.WillMergeReduceNotTooUnfriendlyLayouts
[       OK ] FusionMergerTest.WillMergeReduceNotTooUnfriendlyLayouts (1 ms)
[ RUN      ] FusionMergerTest.AvoidsLargeFusion
[       OK ] FusionMergerTest.AvoidsLargeFusion (1 ms)
[ RUN      ] FusionMergerTest.WillNotMergeIfFusionEmitterIsInefficient
[       OK ] FusionMergerTest.WillNotMergeIfFusionEmitterIsInefficient (1 ms)
[ RUN      ] FusionMergerTest.WillMergeSliceIntoReusingConsumer
[       OK ] FusionMergerTest.WillMergeSliceIntoReusingConsumer (0 ms)
[ RUN      ] FusionMergerTest.WillMergeExpensiveFusionsIfSavesMemory
[       OK ] FusionMergerTest.WillMergeExpensiveFusionsIfSavesMemory (1 ms)
[ RUN      ] FusionMergerTest.WillMergeExpensiveFusionsWithSingleConsumer
[       OK ] FusionMergerTest.WillMergeExpensiveFusionsWithSingleConsumer (0 ms)
[ RUN      ] FusionMergerTest.WillNotMergeExpensiveFusionsWithReusingConsumer
[       OK ] FusionMergerTest.WillNotMergeExpensiveFusionsWithReusingConsumer (0 ms)
[ RUN      ] FusionMergerTest.NoMergeWithBitcast
[       OK ] FusionMergerTest.NoMergeWithBitcast (1 ms)
[ RUN      ] FusionMergerTest.CostBasedMerge
[       OK ] FusionMergerTest.CostBasedMerge (1 ms)
[ RUN      ] FusionMergerTest.CostBasedNoMerge
[       OK ] FusionMergerTest.CostBasedNoMerge (4 ms)
[ RUN      ] FusionMergerTest.NoMergeBecauseTooManyBasicBlockSplits
[       OK ] FusionMergerTest.NoMergeBecauseTooManyBasicBlockSplits (4 ms)
[ RUN      ] FusionMergerTest.CommonElementwiseUsedParameter
[       OK ] FusionMergerTest.CommonElementwiseUsedParameter (1 ms)
[ RUN      ] FusionMergerTest.IncompatibleNonTrivialHeroes
[       OK ] FusionMergerTest.IncompatibleNonTrivialHeroes (0 ms)
[ RUN      ] FusionMergerTest.DoNotMergeDUSFusions
[       OK ] FusionMergerTest.DoNotMergeDUSFusions (1 ms)
[ RUN      ] FusionMergerTest.MergeDUSFusionWithElementwiseFusion
tensorflow/compiler/xla/service/gpu/fusion_merger_test.cc:1127: Failure
Value of: fusion_merger_.Run(module.get()).value()
  Actual: false
Expected: true
[  FAILED  ] FusionMergerTest.MergeDUSFusionWithElementwiseFusion (0 ms)
[----------] 21 tests from FusionMergerTest (41 ms total)

[----------] Global test environment tear-down
[==========] 21 tests from 1 test suite ran. (42 ms total)
[  PASSED  ] 20 tests.
[  FAILED  ] 1 test, listed below:
[  FAILED  ] FusionMergerTest.MergeDUSFusionWithElementwiseFusion

 1 FAILED TEST
================================================================================
Target //tensorflow/compiler/xla/service/gpu:fusion_merger_test up-to-date:
  bazel-bin/tensorflow/compiler/xla/service/gpu/fusion_merger_test
INFO: Elapsed time: 392.381s, Critical Path: 276.82s
INFO: 1497 processes: 613 internal, 884 local.
INFO: Build completed, 1 test FAILED, 1497 total actions
//tensorflow/compiler/xla/service/gpu:fusion_merger_test                 FAILED in 1.2s
  /home/andrew/src/tf_test/tensorflow-git/bazel-ci_build-cache/.cache/bazel/_bazel_andrew/eab0d61a99b6696edb3d2aff87b585e8/execroot/org_tensorflow/bazel-out/aarch64-opt/testlogs/tensorflow/compiler/xla/service/gpu/fusion_merger_test/test.log

Executed 1 out of 1 test: 1 fails locally.

@nSircombe @cfRod FYI

Digging into this a bit.
It fails on AARCH64 because  of "Fused would run slower than unfused!" which seems to be because the exec time gets calculated as 'inf'. Tracing back this comes as a result of the utilization by the consumer being 0.
The difference with x86 is that although it also has 0 utilization by the consumer, the exec time comes out as '-inf'.
So I think that both x86 and AARCH64 should fail and x86 only works by accident.
But the question I have yet to answer is why the utilization by the consumer is 0.


Run "Prefer Lowest" tests

Rer #1641

Coverage remained the same at 94.376% when pulling 5e86503bec55119a8c2574fc9394c47cfb1b343d on 1641/prefer_lowest into b9300aacca1afbd306d748cc6619d9af1233ee74 on master.


restructure how the dash app is created

What
Restructures the global dash app creation so that we can support more configuration (added in #116) without having to change the import structure (i.e. so we don't need to separate config call and dashboard creation)
from rubicon_ml.ui import Dashboard

dash_options = {
    "requests_pathname_prefix": "/proxy/8050"
}

Dashboard(persistence="memory", dash_options=dash_options).run_server(proxy="http://<IP_ADDRESS>:8050::https://my-jupyterhub-server.com/")

or with CLI
rubicon_ml ui --root-dir /rubicon-root --page-size 20

@ryanSoley thanks - updated!


fix bug of TablesNamesFinder when SubSelect has withItemsList

In original code, TablesNamesFinder just parse the selectBody in a SubSelect object. However it would lead to a mistake when a SubSelect object has withItemsList. This pull request fix it and add the corresponding unit test.
By the way, for the universal of unit test module, this pull request use Statement object replacing Select object.
Thanks for your reading.

Coverage decreased (-0.1%) to 83.668% when pulling 276ddc8a4dd8bf73cc2710761c345ba4bf7f71d3 on iceflying:tables_names_finder_oracle_bugs into 37f061014e21f01af82db66dc0d0bb0f817fb499 on JSQLParser:master.


Parse error for the official swift socketIO client

The ErizoClient build process shows errors on building project, but works for the original objc socketIO lib, any build steps for this latest official swift socketIO client replacement? Thanks

the same question

@jasonchuang @juicechu Ensure you have Compile active architecture? only to YES for Debug in the case you want to go with an specific commit before that 5.4.1 for that release vendored SocketIO has been replaced with a Pod.

i found the reason you must complie in xcode 9.0


remotebox: 2.7 -> 3.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/remotebox/versions.
meta.description for remotebox is: "VirtualBox client with remote management"
meta.homepage for remotebox is: "http://remotebox.knobgoblin.org.uk/"
meta.changelog for remotebox is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
Warning: no invocation of /nix/store/6v4408wbwx6kq0dkjs7njx67i6nygi10-remotebox-3.1/bin/.remotebox-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/6v4408wbwx6kq0dkjs7njx67i6nygi10-remotebox-3.1/bin/remotebox had a zero exit code or showed the expected version
0 of 2 passed binary check by having a zero exit code.
0 of 2 passed binary check by having the new version present in output.
found 3.1 with grep in /nix/store/6v4408wbwx6kq0dkjs7njx67i6nygi10-remotebox-3.1
found 3.1 in filename of file in /nix/store/6v4408wbwx6kq0dkjs7njx67i6nygi10-remotebox-3.1

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

2 total rebuild path(s)

1 package rebuild(s)

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

First fifty rebuilds by attrpath
remotebox

Instructions to test this update (click to expand)

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

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

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

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

1 package built:

remotebox

Maintainer pings

From upstream:

2021-11-14 : RemoteBox 3.0 released
RemoteBox has been ported to Gtk3. Review the requirements before updating to ensure your operating system is compatible.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/remotebox/versions.
meta.description for remotebox is: VirtualBox client with remote management
meta.homepage for remotebox is: http://remotebox.knobgoblin.org.uk/
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.2 with grep in /nix/store/09ms63yq3b3jjfb8s7hfl2j4zmfc5pq8-remotebox-3.2
found 3.2 in filename of file in /nix/store/09ms63yq3b3jjfb8s7hfl2j4zmfc5pq8-remotebox-3.2

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
remotebox

Instructions to test this update (click to expand)

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

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

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

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

1 package built:

remotebox

Maintainer pings

Closing as abandoned. Maybe the next time ryanbot will awake someone.


bug: MetaMask Connect Button Intermittently Missing or Non-Responsive in Chrome

Is there an existing issue for this?

[X] I have searched the existing issues

Package Version
1.3.3
Current Behavior
I'm facing an intermittent issue with MetaMask when using Wagmi's web3 interface in Chrome:

Sometimes, the button to connect MetaMask is not visible, as though MetaMask is not installed.
At other times, the button is visible but unresponsive. Nothing happens upon clicking (except changing the loading state), and the MetaMask extension does not open.

This issue is not specific to Wagmi, as I can reproduce it across different web3 apps and while using the basic MetaMask API call window.ethereum.request({ method: 'eth_requestAccounts' }).
The issues do not always occur and it's unpredictable which of the two scenarios will occur. I have not encountered these issues in Firefox or Brave.
Expected Behavior
The button to connect MetaMask should always be visible and responsive. Clicking it should always open the MetaMask browser extension.
Steps To Reproduce

Open a new tab in Chrome (Version 114.0.5735.133 (Official Build) (arm64)).
Navigate to https://wagmi.sh/examples/connect-wallet.
Check if the button to connect MetaMask is present and note what happens upon clicking it.

Refreshing the page usually fixes the issue. However, the issue frequently occurs when a web3 app is initially loaded in a new tab.
Link to Minimal Reproducible Example (StackBlitz, CodeSandbox, GitHub repo etc.)
https://wagmi.sh/examples/connect-wallet
Anything else?
I have reported the same issue to the MetaMask team on their GitHub repository here. This report is for awareness, and to see if there are any known workarounds or fixes from the Wagmi side.

I have faced the same issue with "wagmi": "^1.3.3". The metamask connector is not ready for the first page load and becomes ready for the second page load. Workaround is to reload the page every time on the first load. This behaviour is also reproduced on earlier versions of wagmi for examle ^0.12.8


Optimized Files

Optimized PNG data chunks, having an overall effect of smaller file sizes and potentially faster load/render times. Also, optimized JSON/MCMETA/PROPERTIES files by uniformly using LF as the EOL and spaces for all indentation instead of mixing tabs and spaces.
Note: No textures have visually changed.

Thank you for your optimizations !


fixscan node should project all required expr from parent node

pick from master https://github.com/apache/doris/pull/26886
Issue Number: close #xxx

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

run buildall


Add pg_mooncake to compute-node.Dockerfile

The v15 failure is weird. Why would there not be issue in 14 or 16 given they use the same Debian version?

Hm, yeah
 #80 1171.4 /usr/local/pgsql/include/server/port/atomics/arch-x86.h: In function 'bool pg_atomic_test_set_flag_impl(volatile pg_atomic_flag*)':
#80 1171.4 /usr/local/pgsql/include/server/port/atomics/arch-x86.h:143:16: error: ISO C++17 does not allow 'register' storage class specifier [-Werror=register]
#80 1171.4   143 |  register char _res = 1;
#80 1171.4       |                ^~~~
#80 1171.4 In file included from /usr/local/pgsql/include/server/port/atomics.h:70,
#80 1171.4                  from /usr/local/pgsql/include/server/storage/lwlock.h:21,
#80 1171.4                  from /usr/local/pgsql/include/server/storage/lock.h:23,
#80 1171.4                  from /usr/local/pgsql/include/server/catalog/namespace.h:18,
#80 1171.4                  from ../../src/pgduckdb/catalog/pgduckdb_table.hpp:10,
#80 1171.4                  from ../../src/pgduckdb/catalog/pgduckdb_schema.hpp:4,
#80 1171.4                  from ../../src/pgduckdb/catalog/pgduckdb_catalog.hpp:5,
#80 1171.4                  from ../../src/pgduckdb/catalog/pgduckdb_catalog.cpp:1:
#80 1171.4 /usr/local/pgsql/include/server/port/atomics/arch-x86.h: In function 'bool pg_atomic_test_set_flag_impl(volatile pg_atomic_flag*)':
#80 1171.4 /usr/local/pgsql/include/server/port/atomics/arch-x86.h:143:16: error: ISO C++17 does not allow 'register' storage class specifier [-Werror=register]
#80 1171.4   143 |  register char _res = 1;
#80 1171.4       |                ^~~~
#80 1171.4 cc1plus: all warnings being treated as errors

Maybe Postgres version matters? Slightly different build system?

Looks like e2e job is not gonna run. cc @bayandin

@sharnoff will you take a look at the vm-builder changes? What are the implications of using something like 2G vs 1.5G

I added --recursive to the git-submodule(1) command. More futureproof. @ololobus maybe you can merge in European morning (assuming CI doesn't flake out)?

@ololobus maybe you can merge in European morning (assuming CI doesn't flake out)?

Rebased with button


new post about lazy encoding

reference https://github.com/BuckleScript/bucklescript.github.io/pull/211

rebased

feel free to merge this when ready. Date is set to May 15, which is Friday, so I guess this is the release date?

@ryyppy that feedback is already addresed

I don't have permissison to merge it


undefined symbol: _hex_value, unable to preload libheapusage

on an openSUSE LEAP 15.3:
$ cmake -DCMAKE_INSTALL_PREFIX:PATH=/tmp/heapusage ../heapusage
-- The C compiler identification is GNU 7.5.0
-- The CXX compiler identification is GNU 7.5.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc - works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ - works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found BFD: /usr/lib64/libbfd.a
-- Configuring done
-- Generating done
-- Build files have been written to: /data/heapusage-build
tiziano@tcopt15 /data/heapusage-build $ make
Scanning dependencies of target ex005
[  7%] Building CXX object CMakeFiles/ex005.dir/tests/ex005.cpp.o
[ 14%] Linking CXX executable ex005
[ 14%] Built target ex005
Scanning dependencies of target ex004
[ 21%] Building CXX object CMakeFiles/ex004.dir/tests/ex004.cpp.o
[ 28%] Linking CXX executable ex004
[ 28%] Built target ex004
Scanning dependencies of target ex003
[ 35%] Building CXX object CMakeFiles/ex003.dir/tests/ex003.cpp.o
[ 42%] Linking CXX executable ex003
[ 42%] Built target ex003
Scanning dependencies of target ex002
[ 50%] Building C object CMakeFiles/ex002.dir/tests/ex002.c.o
[ 57%] Linking C executable ex002
[ 57%] Built target ex002
Scanning dependencies of target ex001
[ 64%] Building C object CMakeFiles/ex001.dir/tests/ex001.c.o
[ 71%] Linking C executable ex001
[ 71%] Built target ex001
Scanning dependencies of target heapusage
[ 78%] Building CXX object CMakeFiles/heapusage.dir/src/humain.cpp.o
[ 85%] Building CXX object CMakeFiles/heapusage.dir/src/hulog.cpp.o
[ 92%] Building CXX object CMakeFiles/heapusage.dir/src/humalloc.cpp.o
[100%] Linking CXX shared library libheapusage.so
[100%] Built target heapusage
tiziano@tcopt15 /data/heapusage-build $ make install
[ 14%] Built target ex005
[ 28%] Built target ex004
[ 42%] Built target ex003
[ 57%] Built target ex002
[ 71%] Built target ex001
[100%] Built target heapusage
Install the project...
-- Install configuration: ""
-- Installing: /tmp/heapusage/lib/libheapusage.so
-- Installing: /tmp/heapusage/bin/heapusage
-- Installing: /tmp/heapusage/share/man/man1/heapusage.1
tiziano@tcopt15 /data/heapusage-build $ /tmp/heapusage/bin/heapusage ./ex001
./ex001: symbol lookup error: /tmp/heapusage/bin/../lib/libheapusage.so: undefined symbol: _hex_value
error: unable to preload libheapusage

Thanks @dev-zero for reporting the issue. It should be fixed now in above commit.
I tested on openSUSE LEAP 15.3 using:
sudo zypper install git-core ca-certificates{,-cacert,-mozilla} cmake gcc
gcc-c++
sudo zypper install binutils-devel  # optional for src filenames in callstack
git clone https://github.com/d99kris/heapusage && cd heapusage
mkdir -p build && cd build && cmake .. && make -s
./heapusage ./ex001


[QUESTION] Complex Index using calculated values of field

Is it possible to create a complex index such that it has concatenated values calculated from fields.
(Example):   Fields Description, DateTime
I want to make an index that contains
"Description + DateTime + "#year=" + DateTime.ToString("yyyy") + "#dow=" + DateTime.DayOfWeek.ToString() ... etc ... so that I can do a query EQ or Contains or the like and hit it.
From the Documentation I have found.. I can figure this much:
col.EnsureIndex("textsearch", "$.Description + ';' + $DateTime", false);
How would one manage to apply DateTime.ToString() on the values such as
col.EnsureIndex("textsearch", "$.Description + ';' + $DateTime + ';#year=' + $DateTime.ToString('yyyy')", false);
Or is this even possible?

The public getter/setter logic here is what I was aiming for. Thanks.


No provider for DraggableHelper!

Hi!
I try to use your work but when I copy your code I get this error in my browser's console.
Any ideas why I get it?

As documented in the change log, you need to import the module like DragAndDropModule.forRoot() instead of DragAndDropModule. Hope that helps!


Add documentation for converting old ARM operation patterns

There are still older ARM specs that use interface templates, which can result in confusing deprecation messages, and inexact usage of suppressions to get rid of the warnings (because suppressions cna only happen at the interface definition).

Add a section to troubleshooting describing the deprecation messages and options for how to deal with them
Talk to breaking change folks about promoting breaking changes that do not represent API changes, such as removing 200 responses for asynchronous APIs.

est: 2


Update k325 branch of kintex-chatter prjxray-db repository to upstream

For ease of development at this time, we change the submodule path to kintex-chatter's fork of prjxray-db, cf.
https://github.com/kintex-chatter/xc7k325t-blinky-nextpnr/issues/18
and #1.
Once k325t becomes part of the upstream prxjray-db, we should revert the changes of #1 and https://github.com/kintex-chatter/nextpnr-xilinx/commit/3165a86527e997416de0f6569d8b35e244e34c5d

This ticket is now obsolete, since we have toolchain-installer
and demo-projects, which supersedes the blinky project.


Missing removeEventListener from useNetInfo hook

We need remove event listeners before unmount components :)

@jdnichollsc 👋 The hook currently does this by returning a function when creating the hook which handles the "unsubscribe".
The return from addEventListener is a function which stops the listener:
https://github.com/react-native-community/react-native-netinfo/blob/8a8defe887b235cb04944f2af012208dcf81fd66/src/index.ts#L93-L95
And this is returned when creating the effect hook:
https://github.com/react-native-community/react-native-netinfo/blob/8a8defe887b235cb04944f2af012208dcf81fd66/src/index.ts#L113
These two lines are enough to handle the unsubscription according to the React documentation:
https://reactjs.org/docs/hooks-reference.html#cleaning-up-an-effect
Let me know if this is not working as expected and I can look into it.

Oh ok, but it looks very weird by removing the listener from the addEventListener instead from the hook,
What about having this instead?
export function useNetInfo (): NetInfoState {
  const [netInfo, setNetInfo] = useState(inititalState)

  function onChange (newState) {
    setNetInfo(newState)
  }

  useEffect(() => {
    NetInfo.fetch().then(setNetInfo)
    NetInfo.addEventListener('connectionChange', onChange)

    return () => {
      NetInfo.removeEventListener('connectionChange', onChange)
    }
  }, [])

  return netInfo
}

The alternative way to write the hook would be:
useEffect((): (() => void) => {
  const unsubscribe = addEventListener(setNetInfo);
  return unsubscribe;
}, []);

The way to think about it is that the addEventListener returns the function which unsubscribes that listener. The way it's written in the library just avoids the additional variable, but I agree that it's a bit clearer to split it out as above.

Can we add the NetInfo.fetch().then(setNetInfo) before register the event? or is that listener executed immediately?

No need to do a fetch. Your callback is called on subscribe. This is in the README:
https://github.com/react-native-community/react-native-netinfo/tree/ed4a2cf7c7a1bf8fae9f9a543f59658b4f55031f#addeventlistener

I have found a case where the new paradigm doesn't work.
Using the handleFirstConnectivityChange pattern (as defined in the deprecated API https://facebook.github.io/react-native/docs/netinfo.html) is now impossible without a setTimeout hack.
This is because this.netinfoUnsubscribe() gets executed before it is set.

@kiwidood Why would you not just use a fetch in that instance?

@kiwidood Why would you not just use a fetch in that instance?

The actual isConnected state was getting passed down as props to the child components. I was using the first connectivity change handler separately on the individual components to start a setInterval based fetch when isConnected was true the first time.
Otherwise I would have to have a componentDidUpdate on every component and a state to hold whether it was the first isConnected true or not. The unsubscribe pattern just seemed like a nicer way of doing this.


Release v1.12.4

Which issue(s) this PR fixes:
none
What this PR does / why we need it:
Deliver #3391 to v1.12 users since it's a critical regression.
master branch is already for v1.13 so it has too much changes for v1.12.
So we decide to create a new branch for v1.12.
Docs Changes:
none
Release Note:
none

v1.12.4 has been released: https://rubygems.org/gems/fluentd/versions/1.12.4


USHIFT-758: Include arm release in rebase branch name

Currently only an amd64 release tag is used for branch name. This means that if new amd64 nightly is not produced, but there's a new ARM64 nightly we won't update images for arm until next amd64 nightly.

added rationale to the PR's description
/cc @ggiguash

/lgtm