Error: Uncaught [SecurityError: localStorage is not available for opaque origins]

Hello! I'm getting this error whenever I try to build my app:
navi-scripts: Using config at /directorytoapp/navi.config.js
Error: Uncaught [SecurityError: localStorage is not available for opaque origins]
    at reportException (/directorytoapp/node_modules/jsdom/lib/jsdom/living/helpers/runtime-script-errors.js:62:24)
    at processJavaScript (/directorytoapp/node_modules/jsdom/lib/jsdom/living/nodes/HTMLScriptElement-impl.js:243:7)
    at HTMLScriptElementImpl._innerEval (/directorytoapp/node_modules/jsdom/lib/jsdom/living/nodes/HTMLScriptElement-impl.js:168:5)
    at onLoadExternalScript (/directorytoapp/node_modules/jsdom/lib/jsdom/living/nodes/HTMLScriptElement-impl.js:90:12)
    at onLoadWrapped (/directorytoapp/node_modules/jsdom/lib/jsdom/browser/resources/per-document-resource-loader.js:53:33)
    at Object.check (/directorytoapp/node_modules/jsdom/lib/jsdom/browser/resources/resource-queue.js:76:23)
    at Promise.resolve.then (/directorytoapp/node_modules/jsdom/lib/jsdom/browser/resources/resource-queue.js:83:27) SecurityError: localStorage is not available for opaque origins
    at Window.get localStorage [as localStorage] (/directorytoapp/node_modules/jsdom/lib/jsdom/browser/Window.js:240:15)
    at b (/static/js/main.ae90c729.chunk.js:1:206435)
    at Object.180 (/static/js/main.ae90c729.chunk.js:1:5543)
    at p (about:blank:1:526)
    at Object.308 (/static/js/main.ae90c729.chunk.js:1:45690)
    at p (about:blank:1:526)
    at Module.858 (/static/js/main.ae90c729.chunk.js:1:184742)
    at p (about:blank:1:526)
    at Object.478 (/static/js/main.ae90c729.chunk.js:1:150792)
    at p (about:blank:1:526)
Error: Uncaught [SecurityError: localStorage is not available for opaque origins]
    at reportException (/directorytoapp/node_modules/jsdom/lib/jsdom/living/helpers/runtime-script-errors.js:62:24)
    at processJavaScript (/directorytoapp/node_modules/jsdom/lib/jsdom/living/nodes/HTMLScriptElement-impl.js:243:7)
    at HTMLScriptElementImpl._innerEval (/directorytoapp/node_modules/jsdom/lib/jsdom/living/nodes/HTMLScriptElement-impl.js:168:5)
    at onLoadExternalScript (/directorytoapp/node_modules/jsdom/lib/jsdom/living/nodes/HTMLScriptElement-impl.js:90:12)
    at onLoadWrapped (/directorytoapp/node_modules/jsdom/lib/jsdom/browser/resources/per-document-resource-loader.js:53:33)
    at Object.check (/directorytoapp/node_modules/jsdom/lib/jsdom/browser/resources/resource-queue.js:76:23)
    at Promise.resolve.then (/directorytoapp/node_modules/jsdom/lib/jsdom/browser/resources/resource-queue.js:83:27) SecurityError: localStorage is not available for opaque origins
    at Window.get localStorage [as localStorage] (/directorytoapp/node_modules/jsdom/lib/jsdom/browser/Window.js:240:15)
    at b (/static/js/main.ae90c729.chunk.js:1:206435)
    at Object.180 (/static/js/main.ae90c729.chunk.js:1:5543)
    at p (about:blank:1:526)
    at Object.308 (/static/js/main.ae90c729.chunk.js:1:45690)
    at p (about:blank:1:526)
    at Module.858 (/static/js/main.ae90c729.chunk.js:1:184742)
    at p (about:blank:1:526)
    at Object.478 (/static/js/main.ae90c729.chunk.js:1:150792)
    at p (about:blank:1:526)
[ohshit] An error occured while building your app
Couldn't find window.NaviScripts - did you call register()?
Error: Couldn't find window.NaviScripts - did you call register()?
    at crawl (/directorytoapp/node_modules/navi-scripts/lib/crawl.js:22:15)

The thing with my setup is that I initialized a blog with the create-react-blog command and copied the files into an existing React app. It worked with react-scripts start, but there seems to be an issue with jsdom and the navi-scripts build command. react-scripts build runs without a hitch, but the entire build grinds to a halt when it gets to navi-scripts build.
Any idea what might be causing this issue? I thought it might be related to issue #87.

This is what my package.json looks like, currently.
{
  "name": "app",
  "version": "0.1.0",
  "private": true,
  "dependencies": {
    "@fortawesome/fontawesome-svg-core": "^1.2.0-14",
    "@fortawesome/free-brands-svg-icons": "^5.7.2",
    "@fortawesome/free-solid-svg-icons": "^5.7.2",
    "@fortawesome/react-fontawesome": "^0.1.4",
    "apollo-boost": "^0.4.1",
    "apollo-link-ws": "^1.0.18",
    "auth0-js": "^9.10.0",
    "blueimp-md5": "^2.3.0",
    "brace": "^0.11.1",
    "feed": "^2.0.2",
    "graphql": "^14.1.1",
    "import-all.macro": "^2.0.3",
    "jwt-decode": "^2.2.0",
    "loadable-components": "^2.2.2",
    "lodash": "^4.17.11",
    "navi": "^0.13.3",
    "navi-scripts": "^0.13.3",
    "netlify-cli": "^2.6.0",
    "prismjs": "^1.15.0",
    "prop-types": "^15.7.2",
    "react": "^16.8.6",
    "react-ace": "^6.4.0",
    "react-adopt": "^0.6.0",
    "react-apollo": "^2.5.2",
    "react-click-outside": "^3.0.1",
    "react-content-loader": "^4.2.1",
    "react-dom": "^16.8.6",
    "react-dropzone": "^10.0.1",
    "react-ga": "^2.5.3",
    "react-grid-system": "^4.4.3",
    "react-gtm-module": "^2.0.8",
    "react-helmet": "^5.2.0",
    "react-motion-drawer": "^3.1.0",
    "react-navi": "^0.13.3",
    "react-navi-helmet-async": "^0.13.3",
    "react-notify-toast": "^0.5.0",
    "react-popover": "^0.5.7",
    "react-quill": "^1.3.1",
    "react-redux": "^6.0.1",
    "react-responsive-modal": "^3.6.0",
    "react-reveal": "^1.2.2",
    "react-router-dom": "^4.3.1",
    "react-router-hash-link": "^1.2.1",
    "react-scripts-mdx": "^3.0.3",
    "react-select": "^2.4.2",
    "react-smooshpack": "^0.0.56",
    "react-sortable-tree": "2.2.0",
    "react-sortable-tree-theme-full-node-drag": "^1.1.0",
    "react-splitter-layout": "^4.0.0",
    "react-tabs": "^3.0.0",
    "react-textarea-autosize": "^7.1.0",
    "react-window-size": "^1.2.0",
    "redux": "^4.0.0",
    "redux-form": "^8.1.0",
    "rimraf": "^2.6.2",
    "runkit-embed-react": "^1.0.0",
    "simple-react-validator": "^1.0.7",
    "slugify": "^1.3.2",
    "styled-components": "^4.1.3",
    "subscriptions-transport-ws": "^0.9.16"
  },
  "scripts": {
    "predeploy": "npm run build",
    "start": "react-scripts start",
    "build": "react-scripts build && navi-scripts build",
    "analyze": "rm -rf bundle && source-map-explorer 'build/static/js/*.js' --html bundle/analyze.html",
    "test": "react-scripts test --transformIgnorePatterns \"node_modules/(?!(react-smooshpack|react-sortable-tree|react-splitter-layout|react-quill|react-day-picker|simple-line-icons|react|react-apollo)/)\"",
    "eject": "react-scripts eject",
    "serve": "navi-scripts serve",
    "deploy": "netlify deploy --dir=build",
    "deploy:prod": "netlify deploy --dir=build --prod"
  },
  "eslintConfig": {
    "extends": "react-app"
  },
  "browserslist": [
    ">0.2%",
    "not dead",
    "not ie <= 11",
    "not op_mini all"
  ],
  "devDependencies": {
    "enzyme": "^3.9.0",
    "enzyme-adapter-react-16": "^1.13.2",
    "enzyme-to-json": "^3.3.5",
    "eslint-config-airbnb": "^17.1.0",
    "eslint-config-prettier": "^4.1.0",
    "eslint-plugin-import": "^2.16.0",
    "eslint-plugin-jest": "^22.3.2",
    "eslint-plugin-jsx-a11y": "^6.2.1",
    "eslint-plugin-prettier": "^3.0.1",
    "eslint-plugin-react": "^7.12.4",
    "gh-pages": "^2.0.1",
    "prettier": "^1.16.4",
    "react-test-renderer": "^16.8.6",
    "redux-mock-store": "^1.5.3",
    "source-map-explorer": "^2.0.0"
  }
}

I previously tried using yarn's resolutions config to use version 11.11.0, as suggested here. I've also tried setting it to use a newer version, 13.2.0 and 14.0.0 and even the latest version. No dice.
I've also tried setting testURL in Jest's config but, because I'm using create-react-app`, that config option isn't available to me. Besides, based on this pull request, create-react-app should've resolved that issue a long time ago.


[winreg] Update to 2.2.0

Update winreg to latest released version 2.2.0.
Related issue #10919
Note: No features need to test.

/azp run


make:image: support arm64 cross compile

This should support cross compile container image.
It does not use docker multiplatfor buildx
It uses the compiled arm64 bpftool with llvm , Todo: fix it so we use it only on cross compile in case bpftool still fails
The make tarball is just make image, when make image works then make tarball should work transparently, but in case with multiplatfor docker buildx, then we just need to select the right image with arch as suffix

This is handled by https://github.com/cilium/tetragon/pull/1805


Radiusberechnung der fmo-Library testen

Zur Berechnung der 3D-Position des Balles

FMO randomly chooses too small radius for the detection, usually around 3-4 detections per strike have a false radius (out of 10-15). So z-position cannot be determined for each detection of one strike, extrapolation is needed.


往新的组织里新建仓库时报错

The issue will be closed without any reasons if it does not satisfy any of following requirements:

Please speak English, we have forum in Chinese.
Please post questions or config/deploy problems on our forum: https://discuss.gogs.io, here are bugs and feature requests only.
Please take a moment to search that an issue doesn't already exist.
Please give all relevant information below for bug reports; incomplete details considered invalid report.

You MUST delete above content including this line before posting; too lazy to take this action considered invalid report.

Gogs version (or commit ref):
Git version:
Operating system:
Database (use [x]):

[ ] PostgreSQL
[x ] MySQL 5.7.16
[ ] SQLite

Can you reproduce the bug at https://try.gogs.io:

[ ] Yes (provide example URL)
[ ] No
[ ] Not relevant
打不开 https://try.gogs.io

Log gist:

Description
往新的组织里新建仓库时报错：
2016/12/11 08:25:00 [...routers/repo/repo.go:101 handleCreateError()] [E] CreatePost: addRepository: getMembers: get team-users: Error 1054: Unknown column 'team_id' in 'where clause'

使用docker部署的

试了下二进制的部署，没有这个问题，那还是用二进制的吧，等后面有精力看看问题出在哪里

I don`t know what author wrote, but i have the same problem.

@Lourens-Rich Well, the author said, it would happen only in docker env.
Although it occurred in my docker env, I don't think so. This should be an upgrading issue, if you back to 0.9.97, this issue would disappear.
感觉好多人报这个issue哎，我感觉是做某功能时数所库新填了字段。因为我这边是从老版本直接变新版发现这个错的，退回0.9.97就不会有这错了。印象中看数据库，不管组织和用户都在user表里，估计在做这方面的区别 更新。
论坛Gogs discussion 里这个问题也炸成了锅，不过我到是希望先把discussion修复一下，我登录不上去，github授权不了，提示错，注册帐号发邮件成激活显示成功，但就是登录不上。

我这里也是docker环境，创建组织无法新建仓库。。。

+1

Duplicated to https://github.com/gogits/gogs/issues/3905.


[MI-2071]: Auto select drop down values on clicking subscription button

Auto select drop down values on clicking subscription button

these changes have been picked


Master to Live

Docs Build status updates of commit 0d103b4:
:clock10: Full build: the average full build time is 18 min(s) 1 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 0d103b4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/app-only-auth-powershell-v2.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Get-BlockedSenderAddress.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Herbarium - Use metadata to customize REST endpoints

Dependency: https://github.com/herbsjs/herbs2rest/issues/22
Being able to customize REST endpoints is extremely important since the current convention is just one of many possible configurations.
But instead of informing the library (herbs2rest) explicitly how to behave, we should use generic metadata to achieve that.
For instance:
Verbs:
herbarium.usecases.get('UpdateUser').metadata({ REST: { verb: 'GET' } })

URL path:
herbarium.usecases.get('UpdateUser').metadata({ REST: { path: '/user/:id/update' } })

Resource:
herbarium.usecases.get('UpdateUser').metadata({ REST: { resourceName: 'users' } })

What exactly does the resourceName field refer to?

What exactly does the resourceName field refer to?

The resource to be used: GET /{resourceName}/ -> GET /user/

Would that make group replacement? Or addition?
For example, I have usecases and routes:
Test endpoints
    GET /Test/ -> ReadAll Usecase
    GET /Test/:id -> Read Usecase
    POST /Test -> Create Usecase
    PUT /Test/:id -> Update Usecase
    DELETE /Test/:id -> Delete Usecase
    OTHER /customgetallroute -> Other Usecase

If I pass the resourcename 'companies' it should look like this:
PUT /Test/companies/:id -> Update Usecase
Or
PUT /companies/:id -> Update Usecase
?

Would that make group replacement? Or addition?

If you want to follow the convention {httpVerb} /{resourceName}/:id you can just inform resourceName and a path will be generated for you.
If you want to override the convention, you can inform the path directly. Ex: /user/:id/update/foo/bla.


Podcast Progress Syncing

When I start a podcast that I've already partially listened to on my phone, when resuming the podcast from Sonos it starts from the begining again.
The same is true for podcasts that I start listening to on Sonsos, it doesn't sync the progress

Hey @grunt121, I appreciate you opening this issue. This feature should generally work—but there are some known issues with some particular podcasts not reporting back a correct episode duration which prevents progress from being saved. It appears to be a limitation on the Sonos side. So I'm not sure there's anything I can do about it. Thanks for trying my side project!


oidc/forms: turn empty environments into None

This fixes the immediate bug (which was caused by a comparison that began failing due to dual state between '' and None columns), but should be further improved: the unique constraint between GitHubProviders needs to be expanded to include the environment name as well.
Edit: Done.

I haven't added any unit tests (since this shouldn't produce any branch changes, but I can also add some tests to ensure that the normalized_environment behavior is now as we expect.


Music bot not working.

I request a song, It finds the song, buffers the song, says it plays the song when it really isn't and then finishes instantly I look at the CMD and it says that it tried it 4 times, It didn't work - check your API key or a new song.. I have tried a new song and I checked the API key everything looks fine.. Any tips on how to fix this?

You didn't set her up correctly. Check out the #85

Oh duh.. I moved the folder without changing the path. Thanks!


XP Build?

Any chance this could be built to run on Windows XP? We're stuck in legacy land with XP build machines at present which have Visual Studio 2010 installed on them, however running vswhere.exe gives the following error:

I would have to build an XP machine (given it's out of support, I don't have an image handy) so please download the artifact from the PR build from https://ci.appveyor.com/project/heaths/vswhere/build/1.0.57%2Bgc757b8a2cf/job/b3l2uccqouj1tk6a/artifacts and see if vswhere.exe works for you on XP before I can merge the PR.

That did the trick. I’ve tested it on Windows XP 32bit, Windows 7 32bit, and Windows 10 64bit and it worked fine on all.
Thanks
Derek
From: Heath Stewart<EMAIL_ADDRESS>Sent: Wed 15 March 2017 6:01 PM
To: Microsoft/vswhere<EMAIL_ADDRESS>Cc: vbtrek<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Microsoft/vswhere] XP Build? (#44)
I would have to build an XP machine (given it's out of support, I don't have an image handy) so please download the artifact from the PR build from https://ci.appveyor.com/project/heaths/vswhere/build/1.0.57%2Bgc757b8a2cf/job/b3l2uccqouj1tk6a/artifacts and see if vswhere.exe works for you on XP before I can merge the PR.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/Microsoft/vswhere/issues/44#issuecomment-286828289 , or mute the thread https://github.com/notifications/unsubscribe-auth/AZLimCVUWGYvbKE8ohURL18Q5Ip1WKrDks5rmCdAgaJpZM4MeK4c .  https://github.com/notifications/beacon/AZLimC2uGY3xwofQsvfPbbqJg0Uqpt7Fks5rmCdAgaJpZM4MeK4c.gif

Thank you for your help!


TS String Enum for Stytch Token Type

I'd like to have a TS constant and a union type. Something like:
import {StytchToken, StytchTokenType} from "stytch";

const MAGIC_LINKS_TOKEN: StytchTokenType = StytchToken.Magic_Links; // "magic_links";

Docs:
https://stytch.com/docs/guides/dashboard/redirect-urls#structure
I don't want to use the "magic_links" string.

Heya @grant! Thanks for the feedback.
You can see how we handled this in one of our Next.js example apps here: https://github.com/stytchauth/stytch-nextjs-integration/blob/main/pages/authenticate.tsx#L5-L24
Our app using consts there does align with the theme of your feedback here as well. I'll chat with our SDK team about this!

Sweet, sounds good @chris-stytch . Will hardcode these for now.


Help,I need build run or debug mattermost-webapp in Release 5.18

1.build on windows environment.
run :  make build command,the error result:
'cross-env' is not recognized as an internal or external command,
operable program or batch file.

I don't know how to run or debug in vs code

I need your help. thanks.

Thanks @focusme for the pull request!
Per the CONTRIBUTING.md file displayed when you created this pull request, we need to add you to the list of approved contributors for the Mattermost project.
Please help complete the Mattermost contribution license agreement?
This is a standard procedure for many open source projects. Your form should be processed within 24 hours and reviewers for your pull request will be able to proceed.
Please let us know if you have any questions.
We are very happy to have you join our growing community! If you're not yet a member, please consider joining our Contributors community channel to meet other contributors and discuss new opportunities with the core team.

i have not fou

Hello @focusme, I realize that you wanted to raise an issue, but instead raised a PR to get our attention.
This is likely because npm install wasn't run and therefore npm build is unable to find the tool.
Would you be open to joining our community server so that we can help you resolve your issue ?


call-cpg_pileup

[2024-08-02 00:10:37,03] [info] WorkflowManagerActor: Workflow 1d59a918-9c14-48eb-ab41-4954f086c5cb failed (during ExecutingWorkflowState): java.lang.RuntimeException: Unable to start job.
Inside call-cpg_pileup/stderr.submit:
WARNING: Couldn't use cached digest for registry: Get "https://quay.io/v2/": dial tcp [2600:1f18:483:cf01:8e6a:c950:848:e19b]:443: connect: cannot assign requested address
WARNING: Falling back to direct digest.
FATAL:   While making image from oci registry: error fetching image to cache: failed to get checksum for docker://quay.io/pacbio/pb-cpg-tools@sha256:b95ff1c53bb16e53b8c24f0feaf625a4663973d80862518578437f44385f509b: Get "https://quay.io/v2/": dial tcp [2600:1f18:483:cf02:556a:c33d:2296:61e9]:443: connect: cannot assign requested address
Same for call-paraphase:
FATAL:   While making image from oci registry: error fetching image to cache: failed to get checksum for docker://quay.io/pacbio/paraphase@sha256:186dec5f6dabedf8c90fe381cd8f934d31fe74310175efee9ca4f603deac954d: Get "https://quay.io/v2/": dial tcp [2600:1f18:483:cf02:5c1c:7ce4:bb33:d2b5]:443: connect: cannot assign requested address
Same for call-coverage_dropouts
WARNING: Couldn't use cached digest for registry: Get "https://quay.io/v2/": dial tcp [2600:1f18:483:cf01:d775:5fe7:4c84:600d]:443: connect: cannot assign requested address
WARNING: Falling back to direct digest.
FATAL:   While making image from oci registry: error fetching image to cache: failed to get checksum for docker://quay.io/pacbio/trgt@sha256:8c9f236eb3422e79d7843ffd59e1cbd9b76774525f20d88cd68ca64eb63054eb: Get "https://quay.io/v2/": dial tcp [2600:1f18:483:cf02:5c1c:7ce4:bb33:d2b5]:443: connect: cannot assign requested address
Same for call-trgt:
WARNING: Couldn't use cached digest for registry: Get "https://quay.io/v2/": dial tcp [2600:1f18:483:cf00:d132:ff60:66a5:45f1]:443: connect: cannot assign requested address
WARNING: Falling back to direct digest.
FATAL:   While making image from oci registry: error fetching image to cache: failed to get checksum for docker://quay.io/pacbio/trgt@sha256:8c9f236eb3422e79d7843ffd59e1cbd9b76774525f20d88cd68ca64eb63054eb: Get "https://quay.io/v2/": dial tcp [2600:1f18:483:cf01:8e6a:c950:848:e19b]:443: connect: cannot assign requested address

These are network errors as Cromwell tries to connect to quay.io to fetch container images. It's possible that these are transient errors with quay.io.  Can you try again to see if the error goes away?

I have to run from the beginning?
May I know why it didn't try multiple time to connect?

If call caching has been enabled and configured, starting again will reuse the output from previous executions.

May I know why it didn't try multiple time to connect?

Like you, I'm a Cromwell user and not a Cromwell developer. This question is better-suited for the https://github.com/broadinstitute/cromwell repo or the Cromwell community forums.


tests/lib/mem_alloc fails to build on Arduino Due after SoC move

Bunch of build errors like:
drivers/serial/libdrivers__serial.a(uart_sam.c.obj): In function `uart_sam_init':
drivers/serial/uart_sam.c:106: undefined reference to `soc_pmc_peripheral_enable'
drivers/serial/uart_sam.c:109: undefined reference to `soc_gpio_configure'
drivers/serial/uart_sam.c:110: undefined reference to `soc_gpio_configure'
collect2: error: ld returned 1 exit status

this happens in many other test cases too.

fixed by #9959


merge package from arlac77/npm-package-template

package.json

chore(package<EMAIL_ADDRESS>

Codecov Report

Merging #327 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #327   +/-   ##
=====================================
  Coverage      75%    75%
=====================================
  Files           1      1
  Lines           8      8
=====================================
  Hits            6      6
  Misses          2      2

Continue to review full report at Codecov.

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

Coverage remained the same at 70.0% when pulling 840b20bad0f6291dca18c3f0a864fe527862bcab on template-sync-1 into 1bab92bbb4f3770c628395582fad39adefc5a194 on master.


Unable to Reproduce the Final Result

Hi, We ran the code for 295 epochs. Below is the log after the run of the code. Please help us if we are missing something
epoch [294/295]  train_loss 0.2000 supervised_loss 0.1954 consistency_loss 0.0012 train_iou: 0.9596 - val_loss 0.5416 - val_iou 0.6689 - val_SE 0.5690 - val_PC 0.6468 - val_F1 0.5644 - val_ACC 0.7565
We have done this modification for learning rate, as we were encountering the "RuntimeError: For non-complex input tensors, argument alpha must not be a complex number.". BAsed on the link provided by you in other issue
def adjust_learning_rate(optimizer, i_iter, len_loader, max_epoch, power, args):
lr = lr_poly(args.base_lr, i_iter, max_epoch*len_loader, power)
optimizer.param_groups[0]['lr'] = lr
if len(optimizer.param_groups) > 1:
optimizer.param_groups[1]['lr'] = lr * 10
return lr
lr_ = adjust_learning_rate(optimizer, iter_num, len(trainloader), max_epoch, 0.9, args)

You can follow [https://github.com/FengheTan9/Multi-Level-Global-Context-Cross-Consistency/issues/2](this issue).

Could you please provide the code or can you refer us to some link. Thanks for replying

scheduler = torch.optim.lr_scheduler.CosineAnnealingLR(optimizer=optimizer, T_max=max_epoch)

hello，Is there a formula for calculating this max_iterations?


There are 89 broken links in the documentation site

You all put so much effort into writing very helpful documentation but when the links are 404'ing, it makes it harder to find them :(
Rather than report them one-off, I ran a script to crawl doc.babylonjs.com for broken links:
blc https://doc.babylonjs.com/ -ro -e github -e .jpg -e .png -c 10 > broken-links-babylon.txt
grep -E '├─BROKEN─' broken-links-babylon.txt | sort | uniq

Here's the output after I cleaned it up a little:
https://doc.babylonjs.com/How_To/Animations#animation-blending
https://doc.babylonjs.com/How_To/Environment
https://doc.babylonjs.com/How_To/Normals
https://doc.babylonjs.com/How_To/Reflec#refractiont
https://doc.babylonjs.com/How_To/ShaderIntro
https://doc.babylonjs.com/How_To/Solid_Particle_System
https://doc.babylonjs.com/How_To/Using_the_Canvas2D
https://doc.babylonjs.com/How_To/environment#automatic-creation
https://doc.babylonjs.com/How_To/setup_visualStudio
https://doc.babylonjs.com/How_To/shadows
https://doc.babylonjs.com/advanced/Shader_Material.html
https://doc.babylonjs.com/api/classes/babylon.sceneloaderprogressevent
https://doc.babylonjs.com/api/classes/babylon.webxrcontroller
https://doc.babylonjs.com/babylon101/Environmentt#changing-the-background-color-sceneclearcolor
https://doc.babylonjs.com/babylon101/cascadedShadows
https://doc.babylonjs.com/extensions/Using_The_Canvas2D
https://doc.babylonjs.com/extensions/oceanpostprocess
https://doc.babylonjs.com/features/(/How_To/CreateBox_Per_Face_Textures_And_Colors
https://doc.babylonjs.com/features/Observables
https://doc.babylonjs.com/features/Using_The_Physics_Engine
https://doc.babylonjs.com/features/customize_debug_layer
https://doc.babylonjs.com/features/observables#multiobserver
https://doc.babylonjs.com/features/physically_based_rendering
https://doc.babylonjs.com/features/webvr_camera
https://doc.babylonjs.com/generals/File_Format_Map_(.babylon
https://doc.babylonjs.com/generals/Framework_versions
https://doc.babylonjs.com/how_To/Particles/Animate.md
https://doc.babylonjs.com/how_to/%22http:/localhost:1338/Playground/index-local.html%22
https://doc.babylonjs.com/how_to/%22http:/localhost:1338/inspector/index.html%22
https://doc.babylonjs.com/how_to/%22http:/localhost:1338/localDev/index.html%22
https://doc.babylonjs.com/how_to/%22http:/localhost:1338/materialsLibrary/index.html%22
https://doc.babylonjs.com/how_to/%22http:/localhost:1338/postProcessLibrary/index.html%22
https://doc.babylonjs.com/how_to/%22http:/localhost:1338/proceduralTexturesLibrary/index.html%22
https://doc.babylonjs.com/how_to/%22http:/localhost:1338/sandbox/index-local.html%22
https://doc.babylonjs.com/how_to/%22http:/localhost:1338/tests/validation/index.html%22
https://doc.babylonjs.com/how_to/WebXR_Controller_Support
https://doc.babylonjs.com/how_to/debug_layerEnable
https://doc.babylonjs.com/how_to/how%20to%20start%20contributing
https://doc.babylonjs.com/how_to/scene/Optimizing_your_scene#turning-adapttodeviceratio-offon
https://doc.babylonjs.com/how_to/several%20includes%20in%20Babylon
https://doc.babylonjs.com/how_to/solid_particle_system
https://doc.babylonjs.com/how_to/webxr
https://doc.babylonjs.com/img/extensions/dynamicTexture.jpg
https://doc.babylonjs.com/page.php?p=22081
https://doc.babylonjs.com/page.php?p=22531
https://doc.babylonjs.com/page.php?p=22581
https://doc.babylonjs.com/page.php?p=22591
https://doc.babylonjs.com/page.php?p=22601
https://doc.babylonjs.com/page.php?p=22611
https://doc.babylonjs.com/page.php?p=24822
https://doc.babylonjs.com/page.php?p=24824
https://doc.babylonjs.com/page.php?p=24825
https://doc.babylonjs.com/page.php?p=24827
https://doc.babylonjs.com/page.php?p=24828
https://doc.babylonjs.com/page.php?p=24829
https://doc.babylonjs.com/page.php?p=24830
https://doc.babylonjs.com/page.php?p=24831
https://doc.babylonjs.com/page.php?p=24832
https://doc.babylonjs.com/page.php?p=24833
https://doc.babylonjs.com/page.php?p=24834
https://doc.babylonjs.com/page.php?p=24837
https://doc.babylonjs.com/page.php?p=24840
https://doc.babylonjs.com/page.php?p=24841
https://doc.babylonjs.com/page.php?p=24847
https://doc.babylonjs.com/page.php?p=25088
https://doc.babylonjs.com/page.php?p=25090
https://doc.babylonjs.com/page.php?p=25091
https://doc.babylonjs.com/page.php?p=25094
https://doc.babylonjs.com/page.php?p=25096
https://doc.babylonjs.com/page.php?p=25109
https://doc.babylonjs.com/resources/Creating_Cinematic
https://doc.babylonjs.com/resources/Creating_Materials
https://doc.babylonjs.com/resources/Creating_Particle_Systems
https://doc.babylonjs.com/resources/File_Format_Map_(.babylon
https://doc.babylonjs.com/resources/Installing__the_Babylon_Exporter
https://doc.babylonjs.com/resources/Managin_Lens_Flare_Systems
https://doc.babylonjs.com/resources/Managing_Animations
https://doc.babylonjs.com/resources/Managing_Materials
https://doc.babylonjs.com/resources/PBT_Writing
https://doc.babylonjs.com/resources/PBT_previous_and_next
https://doc.babylonjs.com/resources/PBT_slider
https://doc.babylonjs.com/resources/Unity
https://doc.babylonjs.com/resources/Using_Actions_Builder
https://doc.babylonjs.com/resources/Using_Materials_Builder
https://doc.babylonjs.com/resources/Using_Post_Processes_Builder
https://doc.babylonjs.com/resources/[![image](https:/user-images.githubusercontent.com/954596/59141279-63c8f400-896f-11e9-9f2a-177b451f069f.png
https://doc.babylonjs.com/resources/hiding_editor_lines
https://doc.babylonjs.com/resources/how_to/how_to_use_gamepads
https://doc.babylonjs.com/resources/samples/OpenUrl

Hey this is fantastic
@PirateJC should be able to replace them! Feel free to send PR as well if you want to
Pinging @BabylonJSGuide  as well

This is awesome! I'm going to dig into this now! Thank you @Jarred-Sumner

Np
Also worth flagging that many of the links pointing to demos don't work:
For example, in https://doc.babylonjs.com/how_to/optimizing_your_scene_with_octrees#Demos:

Ok did a pass through and fixed links as well as removed a few old outdated ones.
https://github.com/BabylonJS/Documentation/pull/2011
Thanks again for pointing this out! We'll have to do another pass through to find broken demo links.


'arguments' resolution is incorrect

From the ES6 Specification Draft

Else if "arguments" is an element of parameterNames, then
  a. Let argumentsObjectNeeded be false.

However, if you have
function f() {
    var arguments: number;
    return arguments;
}

we concede the type of arguments to number. This should at least only be the case if arguments appears in the parameter list. One might assume that arguments has the value undefined, and use it inappropriately before it is actually declared.

@DanielRosenwasser, What is the proposed change?

I spoke with @ahejlsberg about this and the outcome was that the complexity that this introduces does not justify the gains.


Use Shellingham for shell detection on Windows

Close #182.
Detection logic based on Shellingham’s documentation.

As a side note, Shellingham also contains detection logic for POSIX platforms. But the current logic in Pew works well there already, so I’m not changing that.

Looks like the test is failing on Windows (there's only one test for the _detect_shell function...). I'm not entirely sure that what the test is checking for is actually reasonable - why would we want python.exe to be returned as the shell? It may have simply been checking a detail of the previous implementation. So if you feel it's more reasonable to update the test suite to add some more thorough tests, I'd be OK with that (ideally, any new tests should clarify why they expect the results they are testing for a bit more clearly ;-)).
I'll try to get some time in the next few days to install this PR and do some manual testing, in addition.

Checking for python.exe was probably indeed a bit of an implementation detail, but it was matching the code's logic since the shell is actually the parent process, but when running that code under py.test, the parent process is simply a Python interpreter.

OK, I've just run some manual tests, and can confirm that in all but one of my tests, this PR behaves the same as master. The one test that does not behave the same, works better with this PR - if you run pew mktmpenv from the Windows "run" dialog (so that there is no parent shell other than Windows Explorer), master starts an Explorer window, whereas this PR starts cmd.exe.
So based on my testing, this looks like a definite improvement. If you could fix the tests, I'm happy with this.

@berdario That's what I suspected - the existing code goes a fixed number of steps up the process stack, whereas I assume (but haven't checked) shellingham searches the tree for a shell (although I need to check it's code to see what it thinks of as a "shell").
It might be worth testing for "odd" shells like git bash, but I don't have time to do that right now. I'll find some time this evening.
Also, I'd like to see somewhere a description of the logic being used - I dislike "do what I mean" magic that isn't documented anywhere. I don't think it necessarily needs to be in pew's documentation, I'd be fine if it got added to the shellingham docs (as it stands, I'll go hunting round in the code to see what it's doing so that I can do more tests).

Yes, I just checked how does shellingham check if a process is a shell: it just checks in a set:
https://github.com/sarugaku/shellingham/blob/master/src/shellingham/_core.py
I'm not aware of git bash being an odd shell: I think it's just a different terminal emulator, and then being invoked with a few environment variables (PATH primarly, I presume) preset

IIRC Git Bash (more specifically Msys2’s bash.exe) actually does have some problems with the shell command, but I cannot recall exactly what. There’s something about its process management.

I just checked how does shellingham check if a process is a shell: it just checks in a set

Thanks, I found that yesterday evening when I did some further checking. I think this is OK - the list seems comprehensive enough, and if any user comes up with a case where it doesn't work, directing the report upstream to shellingham should hopefully be an easy fix (just add the new shell to the set).

IIRC Git Bash (more specifically Msys2’s bash.exe) actually does have some problems with the shell command

Again, I think this is a rare enough case that we can legitimately wait to see if users report an issue (which has the additional advantage of providing a test case) and fix it then.

Again, I think this is a rare enough case that we can legitimately wait to see if users report an issue (which has the additional advantage of providing a test case) and fix it then.

Agreed.

Nice! I think this looks good to go. @berdario any further comments?

The issues around msys2 were around the emulation layer. IIRC MSYS2 / git bash uses a virtual console emulation layer on top of the actual console and it’s not part of the process hierarchy. When we did the implementation I remember this being raised and not finding a good solution

@techalchemy Thanks for the information. If anyone raises the problem for pew, we can take a further look, and if it is a technical limitation that we can't work around, falling back to cmd seems like a fair compromise to me. So I don't think it's a showstopper.

[e2a7aea2e2b2a277cbf8092e2c8fde8eeeb69536](Https://steamfox.com)


Extension Request: Postgresql Anonymizer

https://www.postgresql.org/about/news/postgresql-anonymizer-10-privacy-by-design-for-postgres-2452/

@lubennikovaav to enable it this week

Duplicate: #4970

PR in pg_anonymizer https://github.com/neondatabase/postgresql_anonymizer/pull/3
To test in on preview today/tomorrow

in testing

in review

This extension is now available on staging and prod behind feature flag Anon Extension (can be enabled per-user in Admin console).
Also for most use-cases, this extension should be added to shared_preload_libraries in compute spec:
pg_settings{"shared_preload_libraries": "neon,anon"}.
@raoufchebri is testing it now,
as soon as it will pass internal check, I will start gradually enabling it for clients.

@seymourisdead, I guess it can be a good candidate for feature preview that users can enable on their behalf

It's on production under feature flag

Figure out workflow for users. No issues found during testing.
Discuss with Ann
@raoufchebri Do you have an update on the rollout?

According to Raouf the extension is tested, and works well. There are some inherent challenges, these are listed and explained in an upcoming blog posting.

Rollout plan:

Unblock newer Compute images (unrelated to this ticket)
Include this extension in new copute image
Release it
Another test, ideally by a customer
Announce it
Publish blog posting (already written)

There is a feature flag, which is not enabled for all users. Enable it for everyone. Then remove the feature flag.

See if the error message can be improved, and point the user to what needs to be done (loading the library).
The library is not there because the feature flag is not enabled, but the error message can happen anywhere, not just in Neon.


Fix the wrong pre-commit hyperlink in Prerequisites section

changed wrong hyperlink in Prerequisites section

Description
third and second hyperlink in Prerequisites section is same. updated third one to right link.
Fix #3335

@ichbinmeraj Thankyou 🍪 🚢


Transmitter can transmit stale fragment which is already timed out at the receiver

Is your feature request related to a problem? Please describe.
Reassembly timeout is currently handled via OPENTHREAD_CONFIG_6LOWPAN_REASSEMBLY_TIMEOUT (2s) which would mean a new fragment received every 2s. If transmitter cannot send the reassembly fragment within that time (due to MLE or CoAP packet coming in middle or due to channel conditions, this would cause receiver to drop.
Describe the solution you'd like A clear and concise description of what you want to happen.
The above behavior can be avoided if transmitter checks for the same timeout on the transmit side and drop the packet rather than transmitting a fragment after OPENTHREAD_CONFIG_6LOWPAN_REASSEMBLY_TIMEOUT
Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.
NA
Additional context Add any other context or screenshots about the feature request here.
NA

This seems to be a useful optimization/enhancement to avoid sending frames when we know the receiver will drop or ignore them.
I see one potential downside that we may want to consider:

If I am not mistaken, the "6lowpan reassembly timeout" value of 2 is not explicitly specified or fixed in the Thread specification, and I think it is a configurable parameter in OpenThread (OT).

I tried searching in Thread spec and could not find it.
In rfc4944 I see "The reassembly timeout MUST be set to a maximum of 60 seconds" (which seems to set a max value for timeout).

So the sender cannot be certain that the receiver is using the same timeout value of 2.
By implementing this optimization on the sender side, we are indirectly limiting the receiver's timeout value as well.

Despite this, I still believe that implementing this optimization is useful. We can consider defining and fixing the timeout in the Thread specification to be 2 seconds.

Praticially, I think it is unlikely that any deployment of OT has modified the default value of OPENTHREAD_CONFIG_6LOWPAN_REASSEMBLY_TIMEOUT to use a different value.

Thoughts? @jwhui @sarveshkumarv3 @EskoDijk

thanks @abtink!
I agree defining OPENTHREAD_CONFIG_6LOWPAN_REASSEMBLY_TIMEOUT as spec parameter would help here.
By implementing this optimization on the sender side, we are indirectly limiting the receiver's timeout value as well.
How was 2s chosen? Do you see any downside to limiting the timeout to 2s?

Agree that it needs to be defined in the spec if we want to optimize anything here. From the transmitter's perspective: it only knows that the receiver implements the reassembly rules per RFC 4944 (which refers to 2460, now replaced by 8200) and it doesn't take into acount whether the receiver is OpenThread or other software stack.  I created SPEC-1239 for possible spec updates.

Thanks guys.
I am not sure how the 2 seconds was picked as default but seems to me as a reasonable interval. I think it should be fine to require the same value in spec. Probably very unlikely that any deployment of OT has changed this number from original default of 2 seconds.

The current implementation of reassembly timeout in OT utilizes the TimeTicker class which is a one-second periodic timer that emits a signal at each tick (every second) to modules that have registered to receive ticks using the HandleTimeTick() callback.
Consequently, the 2 seconds reassembly timeout is not exact in the sense that the actual time at which a partially reassembled message is discarded can range from 2 up to to 3 seconds.

I am not sure how the 2 seconds was picked as default but seems to me as a reasonable interval. I think it should be fine to require the same value in spec.

To provide some historical context:

We used to have a timeout config for reassembling the entire datagram.
In #3317, this was changed to a timeout config for receiving the next fragment. At the time, 2 seconds seemed sufficient for receiving the next fragment.

Submitted PR for this.

https://github.com/openthread/openthread/pull/9684

@EskoDijk @sarveshkumarv3 can you please take a look when you can chance? Thanks.

Submitted PR for this.

[mesh-forwarder] drop msg if frag tx delay exceeds reassembly timeout #9684

@EskoDijk @sarveshkumarv3 can you please take a look when you get a chance? Thanks.

Looks good, thanks for handling this.

The PR was closed - difficult because fragments may go via different routes, or be delayed > 2 sec en-route while still meeting the final reassembly deadline.
One thing I realized when doing fragmentation experiments with OT: if a mesh-router on the route decides to drop one fragment, the packet reassembly is very likely to fail in the final mesh destination. In that case this mesh-router can save bandwidth by not forwarding any further fragments with that same tag/sender.  The decision to drop a single fragment can come from failure to transmit the frame after 16 attempts (e.g. NoAck); or because (ECN) queue management drops it.

In that case this mesh-router can save bandwidth by not forwarding any further fragments with that same tag/sender.

I believe such a behavior may be already supported in certains situations.

We have OPENTHREAD_CONFIG_DROP_MESSAGE_ON_FRAGMENT_TX_FAILURE impacting the original sender which does the fragmentation.
https://github.com/openthread/openthread/blob/49c59ec519cc8b49dd58978d1bc80b7ae7ba88d0/src/core/config/mesh_forwarder.h#L49-L63
For intermediate routers we have mechasnim to track if an earlier fragment was dropped by queue managment logic and ensure to drop all subsequent related fragements.  But I dont think this behavior is supported in the case where frag is dropped at MAC layer (no ack after retx).

@abtink Thanks,

But I dont think this behavior is supported in the case where frag is dropped at MAC layer (no ack after retx).

There's also the possibility that only the Ack frame was disrupted, but not the original data frame. So after a fragment drop due to NoAck it may be still the case that the fragment was actually delivered okay to the next-hop router so there's no reason to drop any further/future frames.
If the drop is due to ECN / queue management logic, it's a different story: there's no chance that the fragment was delivered to the next hop because it wasn't sent yet.
Possibly related to this concept of "Ack-disruption": I've seen in the ot-rfsim simulation platform that transmitting radios will not send for some time period after a frame transmission (SIFS/LIFS time) which gives time for the Ack to be sent back undisturbed. However, neighboring radios that did receive the same frame and that know an Ack is likely to follow, don't apply any pause per the 802.15.4 spec.  So they could be disturbing the Ack if they want to transmit something for themselves at that time. To be further investigated!

@sarveshkumarv3 Ok to close this issue? It looks like the only feasible case of fragment dropping is when a router decides to drop a fragmented frame from its buffer (due to time) and no single Tx attempt has been made yet for that frame. Then, any follow-up fragments can also be dropped safely. And OT was already doing this.

sure thanks @EskoDijk, agree this issue can be closed


UI + Workflow - Validate Schedules

Validate that Schedules works.

Testing schedules with the following scenarios

Every 15 minutes echo a shell
Every 1 hr echo a shell
Every 1 hr echo a parameter

@timrbula it looks like the ScheduleEntity has changed. Moving from parameters: { key: value} to params [{name: "", value: ""}]
I attempted to fix it to params from parameters (see latest push to the web app)... but its got the wrong type... its meant to be a RunParam (like on the Run modal).
I imagine the read of the params has changed as well from key: value to a run param if you are editing the schedule as well.
Is that something you can help fix? i think it might be in the SchedulerEditor.tsx but not 100% certain.

Additionally, another part of the app that we removed but might be helpful bringing back is the Schedules page for a team.


Sankey transport loss falls out of chart margins

In a blank EU-27 scenario, the transport loss of the Sankey for future energy flows is out of chart margins:

I can't recreate this issue because I don't have the password for this dataset. Would you mind sharing it @mabijkerk? That's the contents of the .password file in Etsource.
It doesn't seem to be an issue in other scenarios at least, although the Sankey's do sometimes struggle to fit everything in which might be something we want to also look at in this issue.

I think you need to use the EU27_european_union_27_countries dataset, instead of eu. Let me know if this works!

It's this one right?

I just get this error as soon as I open it.

Although I can replicate the issue on the server, locally it doesn't occur. @noracato is there any way this could be related to the server configuration / do you have advice on how to troubleshoot?

Fixed already on Beta!


NTR: mortality

Hey @kaiiam I noticed we don't have anything about mortality, I have some fish datasets where it's binary alive/dead counts of various expressed as TRUE or FALSE or similar. Can we have terms for alive and dead or something to that effect. I don't need it super urgently but when you get to this it'd be great to have.
Thanks!

Thanks @adyork I'll have a look at this, would you mind linking to the example dataset that you found this in?

@whshannon I think brought up a recent case.
But this one has mortality true false and other mortality related things.
https://www.bco-dmo.org/dataset/804502

Low priority since it isn't holding up anything.

This is the example I was looking at this morning: https://www.bco-dmo.org/dataset/856464


Directory with the same name

Type: Feature Request
If I open two directories with the same name, it's difficult for me to distinguish them. Right clicking to see two identical names makes it difficult to distinguish them
VS Code version: Code 1.85.1 (0ee08df0cf4527e40edc9aa28f4b5bd38bbff2b2, 2023-12-13T09:48:06.308Z)
OS version: Darwin x64 23.2.0
Modes:

/needsMoreInfo
Please provide screenshots of the problem to point exact places with problems

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.
Happy Coding!

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Unfilled copyright tag in license

Not very important but I figured it was worth opening an issue for.
https://github.com/Feel-ix-343/markdown-oxide/blob/4af110c1c654a21d034c70ca648c3806924804d1/LICENSE#L189
Thanks for maintaining markdown-oxide!

thank you for reporting!


mark the end of block also with STOP

I think this change would make sense given the surrounding code and comments, but not completely sure. This fixes the bug with the empty contract:
pragma solidity ^0.4.24;

contract C{
}

Blocked by #57.

Definitely makes sense. Good catch.
Don't you think we should also add Return, Revert and Selfdestruct here? Probably we should define this in a more central place like doesOpcodeEndBlock() and doesOpcodeEndExecution() or so, so that these checks are consistent everywhere.
I guess we should also add it here: https://github.com/eth-sri/securify/blob/f5e7e4ada1dd53a2fdfb80f6b773ce64c49dea0e/src/main/java/ch/securify/decompiler/Decompiler.java#L183 This sparks a more general question, whether we want to keep both of them. (Background: Decompiler is more precise if it works, but function detection rarely does. I don't know why it doesn't work though.) I realized that a couple of recent PRs were only against the fallback variant. (mea culpa)
@ptsankov was in favour of keeping the Decompiler in, maybe he can elaborate on its advantages.

I agree with everything you mention, and I have the same questions regarding Decompiler vs DecompilerFallback.
I think I'll first focus on having more tests before we do these changes, so that we can keep track of whether we introduce bugs or not.

For STOP it is clear that it fixes some things using the examples I have added on another branch (basically Securify does not fail on SafeMath anymore), I'm looking for examples for the other opcodes now so that we can compare.

Yes, and it works also for the other opcodes, so perfect.

I've added the other opcodes and tests, if the changes are good for you I'll reorganize the commits and merge.

Can you briefly explain the changes that are going on in the 238 changed files? How does the end-to-end testing work? From where is it triggered?

Can you briefly explain the changes that are going on in the 238 changed files? How does the end-to-end testing work? From where is it triggered?

Sorry that should be clearer now, basically I want to wait until the end_to_end_testing branch is merged before we merge this. It just compares the current output with saved output so that we manually acknowledge the changes. See #57  for more details.

See #68.


How to make weekly view start from Monday

Hi,
The calendar weekly view is starting from sunday. How to make it start from Monday? Urgent help appreciated. thanks.

@aurigamc this library is no more updated and you can try out my library i.e. react-big-schedule.
Do you need just week days or need sunday at last?


Will code be released?

Hello,
Will code be released?
Thanks!

Sorry for the very long delay,
yes we will upload the code hopefully soon.

Awesome, looking forward to it, no rush

@AlessioTonioni Hello, when the code will be released? I want to refer to your code to continue some plans. Thank you very much for your sharing!

Hello,  when the code will be released?Thank you very much for your sharing!

Will the code be released?

Will the code be released?

2023, this code didn't release yet. huh...


Audit dependencies

These are the required dependencies in the requirements.txt.
cycler
event-model
historydict
jsonschema
matplotlib
numpy
super_state_machine
toolz
tqdm

We have discussed removing our dependency super_state_machine in favor of a hand-rolled solution since we aren't using much of its capability. It's a clever library but not a commonly-used one, and it could become a fragile dependency.
We might also make matplotlib optional. I recall that our original reasoning for making it a hard dependency was that experimental science almost always requires some visualization. But on the other hand, bluesky might be run on systems without display. Matplotlib brings in heavy dependencies and significant import time.
All the rest of the requirements are light and pure Python -- with the exception of numpy which is obviously needed. They are either from the NSLS-II org (historydict, event-model) or commonly used and likely to be well-supported in the future.

If matplotlib is going to be optional what is the plan for callbacks? Will there by a try/except import?

Something like that. I dislike it when packages force me to discover optional dependencies in that way, but I'm starting to think its the lesser evil in this case.

I like the separation of MPL. One could imagine separating the visualization from the data acquisition completely via ZMQ and friends. One could even imagine having a server blade run your experiment while visualizing it from the comfort of your very own office, which would make the MPL dep superfluous.

I agree. Try/except is a good thing to add, and requires little effort. Looks like all the imports are mostly in callbacks/ which is good. This might help contain them for machines that don't need plotting.
About potentially replacing matplotlib in bluesky (in case it was considered), I would disagree. Matplotlib is a great library in that it supports multiple backends and works out of the box most of the time. I'm not sure if it is worth the extra effort of extending the built in callbacks to support other plotting libs (but of course external use is encouraged). I'd say definitely remove the dependency, but let the usage of other plotting libs be up to the user? If one has a good solution in the long run, it can then be considered to add?

since we're discussing dependencies, LiveImage also has an xray_vision dependency:
        from xray_vision.backend.mpl.cross_section_2d import CrossSection
might be a good idea to see if there is an alternative to this as well.

Yeah, it might be worth vendoring that (which is what we do in databroker-browser).

...Or maybe working on a separate library of image viewing utilities. Image viewing (beyond simple imshow might be across the threshold of what we want to ship in bluesky itself, given complexity and heavy dependencies.

Xray vision may need a bit of a refactor at the least.

I created two actionable issues from this discussion. Closing.


Route Guide

Hi, this is Kushagra and I want to add the feature of telling the way to user where he/she wants to go according to google maps.
Please assign this task to me @Umesh-01 .

@TheCreaToR-01 go for it 👍


Collect failures from included builds in a composite build

See https://github.com/gradle/gradle/issues/4064 for more context.

LGTM


Groovy lexer doesn't handle quoted function names

Noticed when opening a PR on GitHub with Spock framework tests. Spock uses Groovy's support for quoted function names to describe the test in readable language. Unfortunately this is misinterpreted and we lose syntax highlighting for part of the test.
Here is a shorter example which exhibits the problem. The following two snippets should be highlighted the same way:
def thisFunctionLooksLikeJava() {
    println "hello"
}

thisFunctionLooksLikeJava()

def "this is a (long) function"() {
    println "hello"
}

"this is a (long) function"()

Interesting. You can see here that GitHub is also not happy with the syntax :) Do you want to work on a PR?

@birkenfeld I didn't manage to get a Python environment set up to test locally, but with the help of the CI and adding a new test I was able to confirm that the change works as expected without breaking the existing tests. I also made another small fix for Groovy while I was there. See #1765


insync-v3: <IP_ADDRESS>925 -> <IP_ADDRESS>499

Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

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

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 230932 run on x86_64-linux 1

1 package built:

insync-v3

Hi, can you please add the .desktop files and icons to the insync package? Thanks!


fix bug in translate physical project

Proposed changes
regression case: query_p0/aggregate/aggregate_count1
NPE
a simplified version
"SELECT t1.a
FROM t1,
(SELECT b FROM t2 ORDER BY c ) t3;
"
Issue Number: close #xxx
Problem summary
Describe your changes.
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[ ] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[ ] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[ ] No
[ ] No Need

Does it need to update dependencies:

[ ] Yes
[ ] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[ ] No

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

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 35.09 seconds
load time: 638 seconds
storage size:<PHONE_NUMBER>7 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20221222135834_clickbench_pr_67412.html

remove useless project in translator has many corner case need to handle. And maybe the better way to do this is in Nereids itself. So close this PR and will refactor it later


GH-40152: [C++] Remove redundant invocation of BatchesFromTable

What changes are included in this PR?
This PR fixes a minor performances bug in TableSorter::SortInternal, which invokes BatchesFromTable to get record batches that have been built already.

Are these changes tested?
Yes, by existing tests.
Are there any user-facing changes?
No.

GitHub Issue: #40152

I rebased and will wait for CI.

Ok, the Python test suite failures are because we are Feb 29. They will disappear tomorrow and reappear in 2028 :-)

I rebased and will wait for CI.
Thanks


require('node-localstorage') breaks webpack

We can't use this module in webpack apps as is because it requires node-localstorage (for testing).
Webpack tries to import all requires even ones that conditionally won't be executed because we're in the browser.
My attempt at fixing this by moving the module to runtime dependencies didn't work.
https://github.com/blockstack/blockstack-storage-js/commit/cde11db7ff88fc0a8e7466624b31687f76a6fcbe

 ERROR  Failed to compile with 1 errors                                                                     7:23:18 PM

This dependency was not found:

* node-localstorage in ./~/blockstack-storage/lib/datastore.js

Is there some other mechanism we can use?  I need localStorage to work in node.js.

We can probably mock localstorage if it doesn't exist. That's what I'd assume node-localstorage would do, but apparently it doesn't.

I've mocked local storage in this commit https://github.com/blockstack/blockstack-storage-js/commit/be2088c95ea0182b4e05ad47beb9bf84a87259bb and the errors about missing localStorage in node seem to have gone away.


Ground Markers in POH

Ground markers are not working like they used to inside of POH. When I enter my POH, the ground markers are not visible. If i "mark" a random tile, the other ground markers then appear where i marked them in the past.
Notice how there are no ground markers..
https://puu.sh/CTcHO/4a632957e8.png
Now if i mark a random tile (the tile beside the entrance portal) the other 3 appear on the ground automatically.
https://puu.sh/CTcJ4/053edfd679.png

This only seems to apply to certain room types. I noticed tiles in the starting portal and normal portal rooms appeared fine on first load. Tiles in portal nexus rooms or studies would not appear until another marker was placed. I'm looking into why that is now.


Create dependabot.yml

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 97.059%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
132

Relevant Lines:
136

💛  - Coveralls


feat: unique sorries

Motivation: sorry should have an indeterminate value so that it's harder to make "fake" theorems about stubbed-out definitions. This PR makes each instance of sorry be non-defeq to any other. For example, this now fails:
example : (sorry : Nat) = sorry := rfl -- fails

However, this still succeeds:
def f (n : Nat) : Nat := sorry
example : f 0 = f 1 := rfl -- succeeds

One can be more careful by putting parameters to the right of the colon:
def f : (n : Nat) → Nat := sorry
example : f 0 = f 1 := rfl -- fails

Details:

Adds Lean.Meta.mkUniqueSorry, which creates a sorry that is not defeq to any other sorry. It also encodes the source position into the term. For example, (sorry : Nat) might elaborate to
sorryAx (Lean.Name → Nat) false<EMAIL_ADDRESS>

Makes the sorry term and sorry tactic create unique sorries.

Adds support to the LSP so that "go to definition" on sorry in the Infoview goes to the origin of that particular sorry.

Fixes sorry pretty printing: no more sorryAx in the Infoview.

Removes Lean.Meta.mkSyntheticSorry in favor of Lean.Meta.mkSorry.

Changes sorryAx so that the synthetic argument is no longer optional.

Nice! I'm curious how this interacts with #print axioms. Will each unique sorry show up independently?

Interesting idea @alexkeizer! That wasn't the plan, but I'll look into it. Maybe it would be better to have a #print sorries command?
In the current implementation, the sorryAx still appears like usual, but what's unique is that it's given a unique Lean.Name argument. So, #print axioms still prints sorryAx.

I should clarify, I think I'd prefer the unique names don't show up in #print axioms, as it'd might make it harder to check for axioms with a #guard_msgs in #print axioms line. At least, I'm assuming that the name is derived from the line-number of the sorry, and thus that the output of #print axioms would become more brittle.
Granted, 99% of the time we use the #guard_msgs in #print axioms pattern to assert that there's no sorries, so in reality it's not a big deal either way. Still, having a separate #print sorries would be better.

@alexkeizer These unique sorries just pretty print as sorry, unless you set set_option pp.sorrySource. It could work by having some number of sorrys in the output rather than just a single sorryAx. I won't touch #print axioms in this PR though.


UIKitView Scroll error

The error happens When I put any UIKitView in ListView or PageView and Scroll
Everything is fine when using AndroidView on android.
[VERBOSE-2:shell.cc(186)] Dart Error: Unhandled exception:
'package:flutter/src/gestures/converter.dart': Failed assertion: line 143 pos 18: '!state.down': is not true.
#0      _AssertionError._doThrowNew (dart:core/runtime/liberrors_patch.dart:40:39)
#1      _AssertionError._throwNew (dart:core/runtime/liberrors_patch.dart:36:5)
#2      PointerEventConverter.expand (package:flutter/src/gestures/converter.dart:143:18)
#3      _SyncIterator.moveNext (dart:core/runtime/libcore_patch.dart:151:12)
#4      ListQueue.addAll (dart:collection/queue.dart:715:25)
#5      _WidgetsFlutterBinding&BindingBase&GestureBinding._handlePointerDataPacket (package:flutter/src/gestures/binding.dart:83:27)
#6      _invoke1 (dart:ui/hooks.dart:173:13)
#7      _dispatchPointerDataPacket (dart:ui/hooks.dart:127:5)

Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel master, v1.1.5-pre.38, on Mac OS X 10.14.2 18C54, locale zh-Hans-CN)
[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[✓] iOS toolchain - develop for iOS devices (Xcode 10.1)
[✓] Android Studio (version 3.2)
[!] IntelliJ IDEA Ultimate Edition (version 2018.1.5)
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
[✓] Connected device (2 available)

Can you please provide a minimal reproduction?

Might be related to #24207

Can you please provide a minimal reproduction?

Widget ios = UiKitView(
viewType: "hugo.com/videoplayer",
onPlatformViewCreated: onPlatformViewCreated,
//        hitTestBehavior: PlatformViewHitTestBehavior.transparent,
gestureRecognizers: <Factory>[
Factory(
() => EagerGestureRecognizer()),
].toSet(),
creationParams: <String, Object>{
"url": widget.url,
"options": widget.options,
"auto": widget.auto
},
creationParamsCodec: const StandardMessageCodec(),
)
Widget body = ListView.builder(
itemCount: videoList.length,
controller: _scrollController,
itemBuilder: (context, index) {
return theNativeView;
},
);
in ios
@implementation VideoController{
UIView* _playerContainer;
int64_t _viewId;
FlutterMethodChannel* _channel;
//NSObject* _registrar;
bool _isLive;
bool _isLoop;
UIView * _testView;
}

(instancetype)initWithFrame:(CGRect)frame viewIdentifier:(int64_t)viewId arguments:(id _Nullable)args binaryMessenger:(NSObject*)messenger{
if ([super init]) {
_viewId = viewId;
  _testView = [[UIView alloc] initWithFrame:frame];

}
return self;
}
-(UIView *)view{
return _testView;
}

then when i scroll the listview
the error happen

We would need a minimal runnable reproduction
as a single file (or 2 files in this case) so that we can just copy your code into lib/main.dart of a new project and run to reproduce,
or a minimal GitHub repo.

I have the same problem. Pls solve this error.

[✓] Flutter (Channel stable, 1.22.4, on macOS 11.1 20C69 darwin-x64, locale en-GB)
    • Flutter version 1.22.4 at /Users/fokin/tools/flutter
    • Framework revision 1aafb3a8b9 (6 weeks ago), 2020-11-13 09:59:28 -0800
    • Engine revision 2c956a31c0
    • Dart version 2.10.4

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /Users/fokin/Library/Android/sdk
    • Platform android-30, build-tools 30.0.2
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    • CocoaPods version 1.10.0

[!] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[!] IntelliJ IDEA Ultimate Edition (version 2020.2.3)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • For information about installing plugins, see
      https://flutter.dev/intellij-setup/#installing-the-plugins

[✓] Connected device (3 available)
    • sdk gphone x86 arm (mobile) • emulator-5554                        • android-x86 • Android 11 (API 30) (emulator)
    • iPhone Александр) (mobile)  • 00008030-001D095C3ED2402E            • ios         • iOS 14.2
    • iPhone 11 (mobile)          • 80773A4C-7A78-4B3F-A174-827ED1227B7C • ios         • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)

I have an Ads on ios making by UiKitView and when I scrolling from UiKitView the all of app elements is unfocus and I cant do anything. Pls help.


VPC to VNet

Currently the page describes:
You can use IP access lists to enforce the network location of Azure Databricks users. Using a customer-managed VPC, you can lock down outbound network access.
VPC is an AWS term and should be replaced with the Azure term VNet.
You can use IP access lists to enforce the network location of Azure Databricks users. Using a customer-managed VNet, you can lock down outbound network access.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: e86476af-e94d-51ef-4914-17f7dd399177
Version Independent ID: 9cfe7a64-317d-1aa6-1d85-33ab7359ab69
Content: Security guide - Azure Databricks
Content Source: databricks/security/index.md
Service: azure-databricks
GitHub Login: @mssaperla
Microsoft Alias: saperla

@Techneaux
Thanks for your feedback! We will investigate and update as appropriate.

@mamccrea
Could you please review add comments on this, update as appropriate.

@Techneaux
Thank you for bringing this to our attention.
I've delegated this to content author @mamccrea, who will review it and offer their insightful opinions.

Thanks for providing feedback that helps improve our documentation. We've created an internal work item (DOC-8891) to address your feedback. The timeline for resolution varies based on resourcing.
#please-close


Don't rely on ClassAd updates for image pull failures

For HPC/HTC systems we can't update the job's ClassAd (I think), so we should rely on the promlet JSON

imagePullStatus now in promlet.json: added in https://github.com/prominence-eosc/prominence/commit/445fb2ec6943bb1473978aaee6b7cba191ac6786

Status is returned as "failed" with reason "Contaier image pull failed" using information from promlet.json: added in https://github.com/prominence-eosc/prominence/commit/76fdc9e90538f7ffc2af87bfbaeb49373d915caf


Automatically download snapshots

Summary of changes
Changes introduced in this pull request:

Ask the user when applicable if they would like forest to download a snapshot from a trusted source using RPC methods when running without --detach
Add --download-snapshot flag to download a snapshot prior to syncing for use when stdin is not available (such as running fresh node with --detach)

Reference issue to close (if applicable)

Closes #1847
Other information and links

Known bug that doesn't hinder functionality: The prompt is drowned out in logs so its a couple lines up when it blocks and will look like Forest is stuck. I can't figure out a way around this
Works in --detach when stdin is not a tty (only when --yes/-y is on), and when running normally through the prompt (must enter yes/no)

Another thing, as user, I'd expect --download-snapshot to download one regardless of my current DB status, e.g. if I'd like a fresh one.

Another thing, as user, I'd expect --download-snapshot to download one regardless of my current DB status, e.g. if I'd like a fresh one.

What would you recommend as a new name for a flag? I'm currently looking into the snapshot crash. Don't have anything off the top of my head for a name for the flag

Can't reproduce the crash on my machine.

Can't reproduce the crash on my machine.

@connormullett Have you tried cleaning the db, i.e. rm -rf ~/.local/share/forest/calibnet/?

@connormullett Have you tried cleaning the db, i.e. rm -rf ~/.local/share/forest/calibnet/?

I have. I run before every run testing this feature. I'll try running it longer. But it got past the validation step. I've also just merged main. Maybe I missed a fix. Continuing to check

@connormullett what does this config of yours contain? Have you tried without it, with defaults?

what does this config of yours contain? Have you tried without it, with defaults?

It just contains the encrypt-keystore flag

@connormullett do you mind running it longer? In my case it's still failing, just after those first two computing state messages.
forest on  connor/automatic-snapshot-download [$?] via 🦀 v1.66.0-nightly took 4m53s
❯ target/release/forest --chain calibnet --encrypt-keystore false
 2022-09-29T19:51:08.863Z INFO  forest::daemon > Starting Forest daemon, version 0.2.2+git.27da2815
 2022-09-29T19:51:08.863Z INFO  forest_libp2p::service > Recovered libp2p keypair from "/home/rumcajs-work/.local/share/forest/libp2p/keypair"
 2022-09-29T19:51:08.864Z INFO  forest::daemon         > PeerId: 12D3KooWN9wV8DVwHXAFocGFJTpf7BwpTGkEE4nrtdJkBsf1f34X
 2022-09-29T19:51:08.864Z WARN  forest::daemon         > Warning: Keystore encryption disabled!
 2022-09-29T19:51:08.864Z INFO  forest::daemon         > Prometheus server started at <IP_ADDRESS>:6116
 2022-09-29T19:51:08.864Z INFO  forest::daemon         > Admin token: eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJBbGxvdyI6WyJyZWFkIiwid3JpdGUiLCJzaWduIiwiYWRtaW4iXX0.8IqfOBc_l9awxLRg7K6fzePe6jhkpalfrpxKDUqvljw
 2022-09-29T19:51:08.882Z WARN  forest_chain::store::chain_store > No previous chain state found
 2022-09-29T19:51:08.887Z INFO  forest_genesis                   > Initialized genesis: BlockHeader: Cid(bafy2bzacecz3trtejxtzix4f4eebs7dekm6snfsmvffiqz2rfx7iwgsgtieq4)
 2022-09-29T19:51:08.887Z INFO  forest::daemon                   > Using network :: calibrationnet
✔ Forest needs a snapshot to sync with the network. Would you like to download one now? · yes
 2022-09-29T19:51:11.203Z INFO  forest::cli::snapshot_fetch      > Snapshot will be downloaded to /home/rumcajs-work/.local/share/forest/snapshots/calibnet/forest_snapshot_calibnet_2022-09-29_height_1345031.car (4.76 GiB)
Downloading snapshot 4.76 GB / 4.76 GB [==================================================================================================================================================================================================================================================================] 100.00 % 38.45 MB/s
Finished downloading the snapshot. 2022-09-29T19:53:18.051Z INFO  forest::cli::snapshot_fetch      > Snapshot checksum is 4c34c15817acbad45a6b9450202209fc57fe671a0232fd39951b2cc984425dcd. Validation is not yet available.
 2022-09-29T19:53:18.053Z INFO  forest_genesis                   > Importing chain from snapshot at: /home/rumcajs-work/.local/share/forest/snapshots/calibnet/forest_snapshot_calibnet_2022-09-29_height_1345031.car
 2022-09-29T19:53:18.054Z INFO  forest_chain_sync::chain_muxer   > Evaluating network head...
 2022-09-29T19:53:18.054Z INFO  forest::daemon                   > JSON-RPC endpoint started at <IP_ADDRESS>:1234
 2022-09-29T19:53:18.054Z INFO  forest_rpc                       > Ready for RPC connections
 2022-09-29T19:53:18.056Z INFO  forest_genesis                   > Reading file...
Scanning blockchain 1054871 / 1345031 [========================================================================================================================================================================================================>-------------------------------------------------------] 78.43 % 14129.39/s 21s Scanning blockchain 1341271 / 1345031 [=================================================================================================================================================================================================================================================================] 99.72 % 15387.05/s 0s  2022-09-29T19:55:07.935Z INFO  forest_genesis                   > Validating imported chain from height: 0
 2022-09-29T19:56:08.518Z INFO  forest_state_manager             > Computing state (height: 0, ts=[Cid(bafy2bzacecz3trtejxtzix4f4eebs7dekm6snfsmvffiqz2rfx7iwgsgtieq4)])
 2022-09-29T19:56:08.519Z INFO  forest_state_manager             > Computing state (height: 1, ts=[Cid(bafy2bzacebbzkct2j2kssnnunxxblza3jbiot3sokyslltgk7ovdh2osz52sy)])
thread 'main' panicked at 'Failed miserably while importing chain from snapshot: Invalid tipset: no msg root with cid bafy2bzacebqdl36mjrld2vkvbu56gksjyanpcteskuah6ehom6fnxvfwrbm5y', forest/src/daemon.rs:440:10
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Yup, that's the case. I'm getting it now

What about implementing --assume-yes/--assume-no for case when stdin is not a tty, like proposed by David?

What about implementing --assume-yes/--assume-no for case when stdin is not a tty, like proposed by David?

Hubert suggested we rename the flag to --download-snapshot which makes sense from a user perspective. They may not want to assume-yes for everything

I'm also have this which seem weird:
✔ Forest needs a snapshot to sync with the network. Would you like to download one now? · yes
 2022-09-30T14:50:55.469Z INFO  forest::cli::snapshot_fetch > Snapshot will be downloaded to /Users/guillaume/Library/Application Support/com.ChainSafe.Forest/snapshots/calibnet/forest_snapshot_calibnet_2022-09-30_height_1347965.car (4.78 GiB)
Downloading snapshot 4.78 GB / 4.78 GB [==============================================================================================================================================================================================] 100.00 % 42.73 MB/s
Finished downloading the snapshot. 2022-09-30T14:52:49.927Z INFO  forest::cli::snapshot_fetch > Snapshot checksum is ae8cd7949833c1029e90db2e1326a7ca005ee8a6582e5aba135788d76f394dab. Validation is not yet available.
 2022-09-30T14:52:49.932Z INFO  forest_chain_sync::chain_muxer > Evaluating network head...
 2022-09-30T14:52:49.932Z INFO  forest_genesis                 > Importing chain from snapshot at: /Users/guillaume/Library/Application Support/com.ChainSafe.Forest/snapshots/calibnet/forest_snapshot_calibnet_2022-09-30_height_1347965.car
 2022-09-30T14:52:49.932Z INFO  forest::daemon                 > JSON-RPC endpoint started at <IP_ADDRESS>:1234
 2022-09-30T14:52:49.932Z INFO  forest_genesis                 > Reading file...
 2022-09-30T14:52:49.932Z INFO  forest_rpc                     > Ready for RPC connections
Scanning blockchain 1345585 / 1347965 [==============================================================================================================================================================================================] 99.82 % 3376.96/s 1s  2022-09-30T15:00:06.128Z
INFO  forest_genesis                 > Validating imported chain from height: 0

What about implementing --assume-yes/--assume-no for case when stdin is not a tty, like proposed by David?

Hubert suggested we rename the flag to --download-snapshot which makes sense from a user perspective. They may not want to assume-yes for everything

Hmm. I find this a bit cumbersome to understand, maybe consider renaming it to --force-download-snapshot.

What about implementing --assume-yes/--assume-no for case when stdin is not a tty, like proposed by David?

Hubert suggested we rename the flag to --download-snapshot which makes sense from a user perspective. They may not want to assume-yes for everything

Hmm. I find this a bit cumbersome to understand, maybe consider renaming it to --force-download-snapshot.

We want this flag in particular to download a snapshot when one isn't given to Forest and the DB is out of date. I don't think that portrays the intended use of the flag and to @LesnyRumcajs's point, the current one doesn't either

One thing that came to my mind - it'd be great to automatically dispose of the snapshot after it is loaded in the db, so it doesn't pollute the disk space. Probably a flag --preserve-snapshot would be helpful then. We can do it as a separate task though.

Please update the PR description to match what has been implemented.

Ask the user when applicable if they would like forest to download a snapshot from a trusted source using RPC methods when running without --detach

This is not really accurate. The code still asks even in --detach mode.

Add --download-snapshot flag to download a snapshot prior to syncing for use when stdin is not available (such as running fresh node with --detach)

You haven't added a --download-snapshot flag. You've only added it to the configuration file.

Known bug that doesn't hinder functionality: The prompt is drowned out in logs so its a couple lines up when it blocks and will look like Forest is stuck. I can't figure out a way around this

This is a big problem. What parts of Forest are logging while we're asking the user for input? Maybe those background processes could be started after the snapshot has been downloaded.

Works in --detach when stdin is not a tty (only when --yes/-y is on), and when running normally through the prompt (must enter yes/no)

I don't see any code that deals with ttys nor do I see any code related to --yes/-y.

It would be nice to import the snapshot /while/ they're being downloaded. But that can wait for another PR.

Please update the PR description to match what has been implemented.

Updated. The bug was fixed when we added dialoguer. Rest of the PR comments are good now. Looking into why --detach isn't working with it

The bug where the --detach flag being present broke the logic to skip the prompt has been fixed. However the log shows an error in forest.err and you can see the progress bar in forest.out. Not sure what's going on

In the PR description, you talk about these flags: --yes/-y. Could you point to me where you've implemented these flags?
You also state The prompt is drowned out in logs so its a couple lines up when it blocks and will look like Forest is stuck.. Could you elaborate on this? How can I replicate this problem? Do you have any ideas how it can be fixed?

In the PR description, you talk about these flags: --yes/-y. Could you point to me where you've implemented these flags?
You also state The prompt is drowned out in logs so its a couple lines up when it blocks and will look like Forest is stuck.. Could you elaborate on this? How can I replicate this problem? Do you have any ideas how it can be fixed?

Coulda swore I deleted that because the bug is fixed and --yes is no longer there, been changed to --download-snapshot

Running with --detach still fails badly for me. We should never ask for user input if stdin is not a tty.

Running with --detach still fails badly for me. We should never ask for user input if stdin is not a tty.

how is it failing. Is the daemon saying there is an error? have you checked forest.out? does it fail after downloading?

It waits for user input which never comes and then it times out after about 4 seconds. Does something different happen for you?

It waits for user input which never comes and then it times out after about 4 seconds. Does something different happen for you?

yes, it succeeds however it displays an error in the output (when it tries to detach). The error appears but Forest.out logs show that its downloading. Does your config have disable encryption set? that will also ask for user input

It waits for user input which never comes and then it times out after about 4 seconds. Does something different happen for you?

yes, it succeeds however it displays an error in the output (when it tries to detach). The error appears but Forest.out logs show that its downloading. Does your config have disable encryption set? that will also ask for user input

I'm running this command ./target/release/forest --encrypt-keystore false --chain=calibnet --detach.
It downloads the snapshot for you when run it in detach mode? For me it just blocks waiting for user input.

I'm running this command ./target/release/forest --encrypt-keystore false --chain=calibnet --detach.
It downloads the snapshot for you when run it in detach mode? For me it just blocks waiting for user input.

Ok this is a different issue. Try adding the --download-snapshot flag to that command and you'll see what I'm getting. It should fail because you haven't opted into the flag/config option. It shouldn't ask though, not sure why it is. Looking into it

I'm running this command ./target/release/forest --encrypt-keystore false --chain=calibnet --detach.
It downloads the snapshot for you when run it in detach mode? For me it just blocks waiting for user input.

Ok this is a different issue. Try adding the --download-snapshot flag to that command and you'll see what I'm getting. It should fail because you haven't opted into the flag/config option. It shouldn't ask though, not sure why it is. Looking into it

Ah, interesting. Didn't expect it to fail with the --download-snapshot set. We need to update the code such that it doesn't time-out in either case.
When --download-snapshot is set, it should detach properly and download the snapshot.
When --download-snapshot is not set, it should fail immediately.

I haven't found the reason when download snapshot is set with detach it gives a false error, and you're right I'll be looking into why it's not failing when detach is set without download snapshot set as well

Is this PR ready for review?

Is this PR ready for review?

yes, fixing conflicts now

Todo:
[ ] the prompt is stuck somewhere in logs, should be the last log.
[ ] investigate --detach compatibility


Bug

we can /msg and /tell when we are mute

I really forgot that as I made BetterMute. I'll implement it in a future version.


edge-cases per folder using foldername

This adds the ability to define edge cases per folder-name for a list of files, so the edge-case only has to be defined once.
For example items held by a hand, where the skin color of the hand is compatible with the body, based on the body skin color a different edge-cases for those items can be created, without having to rename a large list of files multiple times.

Hi @Artimunor, thanks for your contribution, I really appreciate it! 🙏
We'll review this PR as soon as possible, I already apologize if this will take some time due to our current heavy workload.


Unify push events for master and pull requests

Coverage remained the same at 100.0% when pulling dac2ea024c6f43194992161a544823474751f70e on unify_pull_for_master_and_pr into be6a097f321422983af4ce607256e4a8a495412e on master.


Popup on attribute suggested enhancement, take more than one type of event trigger

It would be nice if for the Popup's on attribute, I could supply both hover and click, eg.
  <Popup
   inverted
   on='hover, click'
  ...

Hm, I believe this would lead to conflicting interactions.  Example, on='click' does not close on blur while on='hover' does close on blur.  There are more complications when you consider on='focus'.
Note that these are just "presets", if you will, for the underlying Portal props.  You can set them explicitly yourself if you wish to be more precise about the behavior:
https://github.com/Semantic-Org/Semantic-UI-React/blob/master/src/modules/Popup/Popup.js#L253


x/tools/cmd/gopls, maybe gopls should not lint error when same method occurs in different files which adapt different platform

Like this

Duplicate of #29202.


staging-next 2023-05-10

According to 23.05 schedule, breaking changes aren't allowed anymore (except desktop environments).
Helpful links

workflow docs: https://nixos.org/manual/nixpkgs/unstable/#submitting-changes-commit-policy
important jobs:
https://hydra.nixos.org/job/nixpkgs/staging-next/unstable#tabs-constituents
https://hydra.nixos.org/job/nixos/staging-next-small/tested
jobsets:
https://hydra.nixos.org/jobset/nixpkgs/staging-next
https://hydra.nixos.org/jobset/nixos/staging-next-small
nix-review reports: https://malob.github.io/nix-review-tools-reports/
previous staging-next: https://github.com/NixOS/nixpkgs/pull/229429

Mass breakages
(will be edited based on progress)

"channel blocker": the gnupg update in previous staging-next iteration caused is currently blocking the nixos-unstable channel, and this iteration contains a revert.

breaking changes aren't allowed anymore (except desktop environments)

... then why the hell am I repeatedly encountering python packages with newly breaking version constraints?  😠


🐛 Bug Report: Users Are not listed on Chrome fór phone

👟 Reproduction steps
Go to Users tab on Google Chrome on phone and there is no text.

👍 Expected behavior
It should list all users.
👎 Actual Behavior
No text.
🎲 Appwrite version
Appwrite Cloud
💻 Operating system
Linux
🧱 Your Environment
No response
👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

@step135, you're seeing this because these users have an email/phone, but don't have a name set. What would you rather see in this scenario?


Https hijacking  with HttpClient .

When I use  HttpClient to request  "https://www.google.com" in china ， I  was surprised to find that the response  is not the  google home page and without any error tip !  some of response content is :
  <script src="https://ss1.bdstatic.com/5eN1bjq8AAUYm2zgoY3K/r/www/nocache/imgdata/seErrorRec.js"></script>
    <title>页面不存在_百度搜索</title>
    <style data-for="result">
....

It seems to be Http hijacking!
Because the certificate of baidu.com is  trusted root certificate, so  the badCertificateCallback of HttpClient is not invoked。
I guess that the HttpClient may not verify the hostname listed in  server certificate (should assure  the request hostname is in the server certificate ) .  If this is really the fact , means all  trusted root certificate  can be used to hijacking the https request.  It will lead serious security  issue.
My environment
Dart VM version: 1.24.3 (Wed Dec 13 23:26:59 2017) on "macos_x64"

This is a version of the VM (1.24.3) that is no longer being actively worked on.
I'd try the latest Dart 2.0-dev SDK, and refile if you are still having an issue.

Yes, I  have set the proxy as fellows:
   httpClient.findProxy = (uri) {
    //proxy all request to localhost:8888
    return "PROXY localhost:8888";
  };

Is this a problem with the proxy?


Execution failed for task ':app:generateDebugBuildConfig'.

Execution failed for task ':app:generateDebugBuildConfig'.

Failed to calculate the value of task ':app:generateDebugBuildConfig' property 'appPackageName'.
Failed to calculate the value of property 'applicationId'.
String index out of range: 0

Empty string not allowed in build.gradle, i.e for  applicationIdSuffix ''


Send prevnode down the line into the resource's match function

We already run both the current node and the previous node through the match function when a watch event fires (to classify the event: https://github.com/GoogleCloudPlatform/kubernetes/blob/master/pkg/tools/etcd_helper_watch.go#L320). Why not send both of them into the filter so resources can implement custom comparison? There's at least one case that @thockin brought up with endpoints (where he didn't want to fire a watch if the order of a list changed), and it might be useful in general?
@lavalamp

I can live without it.  I am worried about making more couplings to etcd
specifics..
On Mon, Mar 23, 2015 at 6:53 PM, Prashanth B<EMAIL_ADDRESS>wrote:

We already run both the current node and the previous node through the
match function when a watch event fires (to classify the event:
https://github.com/GoogleCloudPlatform/kubernetes/blob/master/pkg/tools/etcd_helper_watch.go#L320).
Why not send both of them into the filter so resources can implement custom
comparison? There's at least one case that @thockin
https://github.com/thockin brought up with endpoints (where he didn't
want to fire a watch if the order of a list changed), and it might be
useful in general?
@lavalamp https://github.com/lavalamp
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/5828.

Obsolete


daemonization causes na+sm initialization failure

Describe the bug
UnifyFS has an option to daemonize its server, which makes the server call its daemonize() function before initializing margo/mercury. When this option is enabled, margo_init("na+sm", ...) fails.
To Reproduce
I created a simple reproducer (see below) based on the example mercury server in the documentation (https://mochi.readthedocs.io/en/latest/mercury/01_init.html). The failure can be reproduced when this code is compiled with -DDAEMONIZE=1 and run passing "na+sm" as the first parameter. Without that flag defined, the example works.
Platform (please complete the following information):

Ubuntu 18.04 docker container (based on spack/ubuntu-bionic) with kernel.yama.ptrace_scope=0
Compiler version: gcc (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0
Spack spec<EMAIL_ADDRESS>^libfabric fabrics=rxm,sockets,tcp
Plugin and protocol used: na+sm

Reproducer Code
#include <assert.h>
#include <errno.h>
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <sys/stat.h>
#include <unistd.h>
#include <mercury.h>

static hg_class_t*     hg_class   = NULL; /* the mercury class */
static hg_context_t*   hg_context = NULL; /* the mercury context */

/*
 * Perform steps to create a daemon process:
 *
 *  1. Fork and exit from parent so child runs in the background
 *  2. Set the daemon umask to 0 so file modes passed to open() and
 *     mkdir() fully control access modes
 *  3. Call setsid() to create a new session and detach from controlling tty
 *  4. Change current working directory to / so daemon doesn't block
 *     filesystem unmounts
 *  5. close STDIN, STDOUT, and STDERR
 *  6. Fork again to abdicate session leader position to guarantee
 *     daemon cannot reacquire a controlling TTY
 *
 */
static void daemonize(void)
{
    pid_t pid;
    pid_t sid;
    int rc;

    pid = fork();
    if (pid < 0) {
        fprintf(stderr, "first fork failed: %s", strerror(errno));
        exit(1);
    }

    if (pid > 0) {
        exit(0);
    }

    umask(0);

    sid = setsid();
    if (sid < 0) {
        fprintf(stderr, "setsid failed: %s", strerror(errno));
        exit(1);
    }

    rc = chdir("/");
    if (rc < 0) {
        fprintf(stderr, "chdir failed: %s", strerror(errno));
        exit(1);
    }

    close(STDIN_FILENO);
    close(STDOUT_FILENO);
    close(STDERR_FILENO);

    pid = fork();
    if (pid < 0) {
        assert(!"second fork failed");
        exit(1);
    } else if (pid > 0) {
        exit(0);
    }
}

int main(int argc, char** argv)
{
    hg_return_t ret;
	char* proto = argv[1];

#ifdef DAEMONIZE
    daemonize();
#endif

    FILE* log = fopen("/tmp/test_mercury_server.log", "w");

    /* Initialize Mercury and get an hg_class handle.
     * bmi+tcp is the protocol to use.
     * localhost is the address of the server (not useful at the server itself).
     * HG_TRUE is here to specify that mercury will listen for incoming requests.
     * (HG_TRUE on servers, HG_FALSE on clients).
     */
    hg_class = HG_Init(proto, HG_TRUE);
    if (hg_class == NULL) {
        if (NULL != log) {
            fprintf(log, "HG_Init(%s, HG_TRUE) failed\n", proto);
            fflush(log);
            fclose(log);
        }
        exit(1);
    }

    /* Get the address of the server */
    char hostname[128];
    memset(hostname, 0, sizeof(hostname));
    hg_size_t hostname_size = sizeof(hostname);
    hg_addr_t self_addr;
    HG_Addr_self(hg_class, &self_addr);
    HG_Addr_to_string(hg_class, hostname, &hostname_size, self_addr);
    if (NULL != log) {
        fprintf(log, "Server running at address: %s\n", hostname);
    }
    HG_Addr_free(hg_class, self_addr);

    /* Creates a Mercury context from the Mercury class. */
    hg_context = HG_Context_create(hg_class);
    if (hg_context == NULL) {
        if (NULL != log) {
            fprintf(log, "HG_Context_create() failed\n");
        }
    } else {
        /* Destroys the Mercury context. */
        ret = HG_Context_destroy(hg_context);
        if (ret != HG_SUCCESS) {
            if (NULL != log) {
                fprintf(log, "HG_Context_destroy() failed\n");
            }
        }
    }

    /* Finalize Mercury. */
    ret = HG_Finalize(hg_class);
    if (ret != HG_SUCCESS) {
        if (NULL != log) {
            fprintf(log, "HG_Finalize() failed\n");
        }
    }

    if (NULL != log) {
        fclose(log);
    }

    return 0;
}

Hmm I think it's related to the fact that you close the std streams, if you comment out those lines it seems to pass fine. Looking at it...

Alright once PR #430 is merged, everything should be fine. Also as I was playing with your reproducer and in case you don't know you can redirect mercury logs by adding:
    HG_Set_log_level("debug");
    NA_Set_log_level("debug");
    hg_log_set_stream_debug(log);
    hg_log_set_stream_error(log);
    hg_log_set_stream_warning(log);

Adding those will redirect all streams to your log file and enable a debug level of output.

@soumagne Thanks for the info on redirecting the mercury logs. I am planning to make use of that.


Azure - PCR Support

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Support for Azure Private Container Registry (PCR) is available in v0.10.0-beta.7 and later.


[Enhancement] Space Debris

Space Debris that can hit your ship and Damage you. Would be a cool option for the next update!

I don't really like the idea of having to constantly upkeep my ship because the Random Generator said so.

It would be interesting, and a reason to upgrade your ship components over time.
Should definitely be toggleable, I'd turn it on, but I play on hard anyway.

Maybe a sort of defensive turret to shoot them would be a valid way to lower the need of constant upkeep,
Essentially You'd need to automate ammo of some sort, or make a higher tier that can run off of electricity

Constant upkeep is only acceptable if it requires little thought and is easy to fix, such as Minecraft's hunger system. Getting hit with meteors and losing parts of the ship that you may not remember how to fix is not something I would find "fun" in any non-sarcastic definition of the word.
It's the reason why people on the Minecraft Forum don't like suggestions for Natural Disasters, or creepers with larger explosions. It's annoying, and takes time that the player could be spending on progressing or building.

Duplicate of #386


vendor: move to go dep tool

Gah, oops. I will try and get some time to fix this this weekend.
On Wed, May 17, 2017 at 12:49 PM Nick Miyake<EMAIL_ADDRESS>wrote:

@nmiyake requested changes on this pull request.
I tried running go build . locally on this branch and it failed.
I've updated the project to include basic CI verification that ensures
that go build . succeeds in Go 1.8 and Go 1.7. Would like to make sure
that this builds properly before accepting the PR.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/palantir/tfjson/pull/4#pullrequestreview-38770364,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACDCLBMGVUI5MrTThPdZUy_GWtC2A6qks5r608_gaJpZM4NeVO5
.