text:
dragonberry

Description
Note: this PR super-bumps your version of cosmwasm and I don't know if it can affect contracts or not.
Fixes dragons.

Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...

[ ] included the correct type prefix in the PR title
[ ] added ! to the type prefix if API or client breaking change
[ ] targeted the correct branch (see PR Targeting)
[ ] provided a link to the relevant issue or specification
[ ] followed the guidelines for building modules
[ ] included the necessary unit and integration tests
[ ] added a changelog entry to CHANGELOG.md
[ ] included comments for documenting Go code
[ ] updated the relevant documentation or specification
[ ] reviewed "Files changed" and left comments if necessary
[ ] confirmed all CI checks have passed

Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...

[ ] confirmed the correct type prefix in the PR title
[ ] confirmed ! in the type prefix if API or client breaking change
[ ] confirmed all author checklist items have been addressed
[ ] reviewed state machine logic
[ ] reviewed API design and naming
[ ] reviewed documentation is accurate
[ ] reviewed tests and test coverage
[ ] manually tested (if applicable)

Hi @faddat, thanks for the PR!
Considering that:

Desmos mainnet is running on Cosmos SDK v0.45.x
the latest Cosmos SDK version (v0.46.9) contains some breaking changes since v0.45.x
we have in plan to upgraded the Desmos mainnet to Cosmos SDK v0.46.x in the near future

We have decided to proceed as follows:

releasee Desmos [v2.4.0] (https://github.com/desmos-labs/desmos/releases/tag/v2.4.0) which contains the Dragonberry fix provided by the Osmosis team, and ask all mainnet validators to upgrade to it
once #1025 is merged, release Desmos v4.6.0 (which upgrades Cosmos SDK to v0.46.9) and upgrade our testnet to it
if everything goes smooth with the testnet, upgrade the mainnet to Desmos v4.6.0

This should guarantee that both our mainnet and testnet are safe from the bug, while avoiding any mainnet breaking change due to swithing binary to a version that contains incompatible changes.
For the above reasons, I'm going to close this PR.
Thank you anyway for your contribution :pray:

authors: RiccardoM faddat

repo: desmos-labs/desmos


text:
Support segregated witness

Add segregated witness support.

Looks like BitcoinJ hasn't quite finalized their segwit implementation yet but the wallet should continue to operate in a nonsegwit mode of operation and all transactions sent or received will be standard "legacy" transaction format.
I'm still poking around to get my local test environment of floj to sync on testnet to verify how it responds to segwit

source: gharchive/issue

authors: bitspill cchrysostom

repo: desotoinc/floj

license_type: permissive

license_source: github-api


text:
Incorrect typescript compiler option in truffle-v5 example

In /examples/truffle-v5/package.json, there is a script:
"scripts": {
  "migrate": "tsc -p ./tsconfig.migrate.json --out-dir ./migrations && truffle migrate"
}

It produces the following error:
$ yarn migrate
yarn run v1.22.11
$ tsc -p ./tsconfig.migrate.json --out-dir ./migrations && truffle migrate
error TS5025: Unknown compiler option '--out-dir'. Did you mean 'outDir'?
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

The script should be
"scripts": {
  "migrate": "tsc -p ./tsconfig.migrate.json --outDir ./migrations && truffle migrate"
}

lol i think this got messed up while replacing TypeChain's --out-dir CLI option.
This could use some CI test.

authors: SharjeelSafdar krzkaczor

repo: dethcrypto/TypeChain

license: MIT


text:
Following equation not rendering properly

T_2(k) = \binom{k + 1}{2} = \frac{k(k + 1)}{2}

solved by switching to data-urlencode in curl

repo: detrin/latex-in-terminal


text:
주석오류

https://github.com/dev-goose/app-first-gallery/blob/master/src/js/Article.js#L102
인자값이 없는데 주석에 들어있다.
그밖에 주석에 대한 오류가 몇몇군데 보이는데 체크할 필요가 있음.

https://github.com/dev-goose/app-first-gallery/blob/master/src/js/Article.js#L102
이 부분은 문제없었고 다음 부분이 문제가 보임.
https://github.com/dev-goose/app-first-gallery/blob/master/src/js/Article.js#L199
https://github.com/dev-goose/app-first-gallery/blob/master/src/js/Article.js#L350

9deb0fc

repo: dev-goose/app-first-gallery

license: mit

license_source: bigquery


text:
Add a license to the repository

I recently came across your project qiskit-study and I noticed that the repository github.com/dev-onejun/qiskit-study currently does not have a license specified.
Why Adding a License is Important?
As GitHub documents

Public repositories on GitHub are often used to share open source software. For your repository to truly be open source, you'll need to license it so that others are free to use, change, and distribute the software.

Would be possible to add a valid license to this repository? Probably something really OpenSource such as the Apache 2.0 license would fit really well.
Thanks!

I appended Apache 2.0 license  in the repository.
Thank you for noticing me to add a valid license !

Thank you!

authors: cbjuan dev-onejun

repo: dev-onejun/qiskit-study


text:
Will you consider developing based on the bsc chain?

Will you consider developing based on the bsc chain?
The bsc network now has a large number of users, and the gas is much lower than eth

We can, in fact, have the same protocol running on multiple chains. However, all chains should be well-distributed in terms of nodes and governance and have high liquidity. However, such a technical assessment is sometimes ambiguous.
On the other hand, the biggest concern we should consider is the uneven distribution of tokenized projects. We are currently working on L2 for Ethereum. The development of L2 is expected to make significant progress this year, and we may consider expanding to other chains based on network costs only after the implementation of L2.

I believe that the unbalancing of the tokenization will be endevitable in most cases due to the demand of the token as we can all guess some tokens are made for no reason a temporary slogan that shiny thing that is nothing so when it comes to us programming ..... the tokens value has to a allocated/dependant on the actual cost /value of that which the token is spent used; mathematical expression is needed to maintain the balance of the ecosystem with in whole

authors: aggre coder969 iamxyzone

repo: dev-protocol/DIPs


text:
fix: change resourceSummary types in all proto files

I need to change all functions type to i32 to match proto files definition.
This will fix errors when trying to send node resources to the scheduler in node-agent main.rs.

I understand your point of view completely. In fact, at the beginning, I would have wanted to change all the proto files. But after thinking about it, I decided to change only my code to not brake the code of all the teams.
What do you recommend at this stage of the project? Should I change all the proto files or stay with these changes even if it doesn't make much sense?

Should I change all the proto files or stay with these changes even if it doesn't make much sense?

The answer is in your question :-) Do you want to do something that does not make sense? It would not make sense, right?
Bite the bullet and fix the error, across the repo. The sooner, the better and that's no big deal btw.

Okay, I will fix that. Thank you for your return.

I changed all proto files and notified the concerned teams of this change.

source: gharchive/pull-request

repo: dev-sys-do/kudo


text:
Add a Typescript definition file

I'm new to React, Typescript, etc but have managed to use this component with Typescript by creating a custom type definition file.
declare module 'react-hls-player' {

	export class ReactHls extends React.Component<DetailedHTMLProps<VideoHTMLAttributes<HTMLVideoElement>, HTMLVideoElement>> {
		url: string;
		hlsConfig?: Partial<Hlsjs.Config>;
		controls?: boolean;
	}

	export default ReactHls;
}

I'm unsure if it's correct but it got the basics working for me.   Hopefully this helps someone else until someone more experienced than myself could perhaps improve the definition and submit a pull request.

Thanks for the feedback @hastarin. My knowledge in Typescript is fairly limited, but I agree that proper Typescript definitions will definitely make a great addition. I originally forked this project as it looked like it was abandoned and was one I needed. My goal was to fix issues that I was running in to, while also maintaining the package and adding new features. I am currently looking in to the possibility of a full rewrite and releasing as version 1.
I will do more research in to this and as time allows will add Typescript compatibility. I'll leave this issue open for now so others can see a possible solution until then.

@hastarin I've released a V1 of this package. It now includes a typescript definition file by default for all that intellisense goodness! API should be the same, this was just a rewrite a long with some improvements.
7b8979cafb8242b9fd4794fff498b7969dd92b55

Thanks @devcshort I will have to make time to update my little test site I am using this in.
At a glance though something closer to the definitions I used would have worked a lot better?
You're actually extending existing controls and I would have thought it's easier to use their definitions than redefine them.
I'll have to try it to see, but would think that with what you've gone with some of the magic of Typescript, such as Intellisense for various properties, will be unavailable as you've defined them as objects.
Again, I'm no expert, my language of choice is C# which is why I've been using Typescript for a little side project in the first place.

Thanks @devcshort I will have to make time to update my little test site I am using this in.
At a glance though something closer to the definitions I used would have worked a lot better?
You're actually extending existing controls and I would have thought it's easier to use their definitions than redefine them.
I'll have to try it to see, but would think that with what you've gone with some of the magic of Typescript, such as Intellisense for various properties, will be unavailable as you've defined them as objects.
Again, I'm no expert, my language of choice is C# which is why I've been using Typescript for a little side project in the first place.

You’re completely right. I shouldn’t have extended it the way I did. My knowledge of Typescript is minimal and I was fumbling with it earlier. I was too focused on some of the extras that I completely missed the proper typings for some of the things I did as objects. I’ll push out a fix as soon as possible to have better typings. Thanks for the feedback!

@hastarin I tried to update my Typescript definition so that it could extend the HTML Video Element, but I started running in to issues from that. It would tell me that all of the attributes are considered required (width, height, autoplay, etc). Did you run in to this at all? I don't want to force this requirement if I'm to have the hls video player be an extension of that. I also ran in to issues when trying to overwrite the style attribute to use React's style interface.
I'm going to reopen this in case anyone else may be able to help as well. I want to try and get all the Typescript definitions working properly.

@hastarin I tried to update my Typescript definition so that it could extend the HTML Video Element, but I started running in to issues from that. It would tell me that all of the attributes are considered required (width, height, autoplay, etc). Did you run in to this at all? I don't want to force this requirement if I'm to have the hls video player be an extension of that. I also ran in to issues when trying to overwrite the style attribute to use React's style interface.

No I did not.  The only required attribute in the definition I used is url.  Make sure if you're doing something like the following:
hlsConfig?: Partial<Hlsjs.Config>;
You need to use Partial so it doesn't require all attributes from the referenced type.

No I did not. The only required attribute in the definition I used is url. Make sure if you're doing something like the following:
hlsConfig?: Partial<Hlsjs.Config>;
You need to use Partial so it doesn't require all attributes from the referenced type.

I had tried the Partial based on your example, which worked for the Hlsjs Config, but I was also trying to have the base extend from the html video component which is where I was running in to issues. Essentially I want all html video component props to be accessible as root props rather than being a separate object. As soon as I extended HTMLVideoElement I received errors that all video element props are required. Maybe I should replicate your example completely rather than just making an interface. 🤔

Just released version 1.1.0. I updated the Typescript declaration to use your example. I made one small change to how the types extend as I was getting class based component methods showing up in intellisense for props. It seems to be working as it should now. Let me know if you think there are any other changes I should make to it.
Thanks again!

authors: devcshort hastarin

repo: devcshort/react-hls


text:
add push framework

增加大体架构

麻烦你解决一下冲突。

repo: developer-learning/night-reading-go


text:
🛑 wa is down

In ef181d1, wa (http://ws.clusterciar.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: wa is back up in 9bb2f7d.


text:
🛑 Ceres is down

In 1f7ef21, Ceres (http://erp.clusterciar.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Ceres is back up in 059c8be.


text:
Fix dev server clientLogLevel

What kind of change does this PR introduce?
:bug: fix
Did you add tests for your changes?
N/A
Summary
In webpack-dev-server v3.4.0, the clientLogLevel value of none was removed and replaced with silent. As v3.4.0 falls in preact-cli's range of ^3.3.1, and webpack-dev-server strictly validates its options before starting, this should be causing preact watch to fail if the project was created after said dev server version was published.
See https://github.com/webpack/webpack-dev-server/pull/1825
Does this PR introduce a breaking change?
No (other than bumping webpack-dev-server, which could be considered a breaking change, and probably should have on their part).
Other information
specs -m
Host: XPS 13 9370
OS: Manjaro Linux x86_64
Kernel: Linux 5.0.9-2-MANJARO
CPU: Intel i7-8550U (8) @ 4.0GHz
GPU: Intel UHD Graphics 620

node -v
v11.15.0

npm -v
6.9.0

yarn -v
1.16.0

This was already fixed in v3.4.1. I'll close this for now, it's probably better to just leave this at the now deprecated none for now.

repo: developit/preact-cli


text:
{ Silly question} VirtualDOM compability with Elmish

Sorry for putting this probably obvious topic here in the issues:
Is it possible to see preact as a drop in replacement for react?
Since its API is the same?
Can I simply use Preact in Elmish, since its ported to React already?
Thanks :D

In most projects preact can be used as a drop in replacement for react. In case some 3rd party library needs react-specific things we have a compat layer called preact-compat that can be used in conjunction. Note that the latest react has made some API changes in 16.3. though, but most libraries haven't switched yet.
I'm not sure how Elmish works under the hood. It looks really interesting! I don't have any experience with F#, perhaps someone else can chime in here?

You can indeed use preact, inferno or any library compatible with react using Elmish and modifying only your webpack config.
See their migration guide: https://preactjs.com/guide/switching-to-preact
{
  "resolve": {
    "alias": {
      "react": "preact-compat",
      "react-dom": "preact-compat"
    }
  }
}

repo: developit/preact


text:
add Microsoft Azure function deployment

@robintw would you be able to review this? 🙏

@robintw I may have 👀  https://github.com/robintw/starlette-test-azure/blob/master/HttpTrigger1/function.json for inspiration 😉
🙏

repo: developmentseed/titiler


text:
Fix location of fake DWO CSV

What does this PR do?
Fix location of fake DWO CSV
What issues does this PR fix or reference?
Is it tested? How?

PR Checklist

[ ] E2E tests pass (when PR is ready, comment /test v8-devworkspaces-operator-e2e, v8-devworkspace-happy-path to trigger)

[ ] v8-devworkspaces-operator-e2e: DevWorkspace e2e test
[ ] v8-devworkspace-happy-path: DevWorkspace e2e test

/test v8-che-happy-path

/test v8-devworkspace-operator-e2e

/test v8-che-happy-path

DevWorkspace is not deployed correctly

/test v8-che-happy-path

now happy path test fails to deploy DWO

message: 'MountVolume.SetUp failed for volume "webhook-tls-certs" : secret "devworkspace-webhooks-tls" not found'

/test v8-che-happy-path

/test v8-che-happy-path

/test v8-che-happy-path

Finally:
INFO[2021-09-07T12:52:31Z] Step che-happy-path-che-happy-path succeeded after 17m20s.

/test v8-devworkspace-operator-e2e

I'm merging it just to get working happy path test in main branch. And will create a separate PR for fixes.

repo: devfile/devworkspace-operator


text:
[test] Redirect noisy output #98

Should give error

Error summary here https://github.com/openwisp/openwisp-utils/pull/156#issuecomment-725574906

Closing as the issue is resolved now

repo: devkapilbansal/openwisp-utils


text:
TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/26302

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/35829


text:
Unify home / Downloads directory

The locations of HOME (~) and Downlods (~/Downloads) sometimes differ leading to duplicated downloads, devon script installation and licenses agreement. Locations are:

C:\Users\«user»\ for windows and git-bash on win
C:\cygwin[64]\home\«user»\ for cygwin
/Users/«user»/ on mac
/home/«user»/ on linux
Further if you are using virtualization e.g. VM Ware Fusion can "embed" your native Downloads directory from your host into the VM. So I am running windows 10 as VM inside MacOS. Then in Win10 I see my MacOS "Downloads" inside Windows Explorer. But it is redirecting to \\vmware-host\Shared Folders\Downloads and still there is a regular folder C:\Users\«user»\Downloads where devon-ide will put Downloads from git-bash.

This is surely nice to have. Maybe we should not bother too much about cygwin but if we want to support both git-bash and cygwin, then IMHO it would be good to only define a single location .devon and Downloads on the same machine.

Within cygwin the value of  $(cygpath $USERPROFILE\Downloads) could be used as download directory. I have never seen a cygwin that had  /home//Downloads pre installed.
Also I'd vote to only use any fixed prefixes like "C:\Users" if there isn't any other option. This could be for example D:\Users.  (might even be true on Capgemini Group windows image - not sure)
It is better to rely on HOME variable. On Windows no predefined %HOME% exists, so either "%USERPROFILE% or %HOMEDRIVE%%HOMEPATH% needs to be used.

For linux/mac there is no issue as there is only one concept of a home directory (~ = $HOME)
For windows CMD world everything is already solved via %USERPROFILE%
For windows git-bash everything is also solved as it uses %USERPROFILE% as $HOME
The only issue is with cygwin that is using a different $HOME directory to isolate from the windows world (e.g. if you are using tools both natively in windows and in cygwin this can lead to conflicts if that tool writes its settings to something like ~/.tool but these settings are not portable). As we can not change the way cygwin is working, we still will end up with duplicate .bashrc, .zshrc, etc. We could avoid duplicating .devon folder in the 2 different home directory as well as Downloads. For Downloads I would strongly vote for doing so. For .devon I do not care much as the disc space is not an issue so it is more about simplicity/complexity here vs. there (cygwin workarounds for installation vs. uninstallation).

fixed with PR #114

authors: hohwille markusschuh

repo: devonfw/devon-ide


text:
Blob Implementation for H2 DB

This PR also covered Issue - https://github.com/devonfw/my-thai-star/issues/278

Created separate issue for SAP HANA -https://github.com/devonfw/my-thai-star/issues/294

Merging the PR as the issue related to SAP Hana is created

repo: devonfw/my-thai-star


text:
Add some common file extensions for frontend code

Fixes #308
It makes sense to add frontend file extensions to the default. This might onboard new users more easily ('works out-of-the-box')

If there's a way to know in which IDEA instance the plugin is running (like PyCharm, PHPStorm, etc.) we could adjust the default file extensions automatically at first start.

Actually there is, created an issue for that: https://github.com/devoxx/DevoxxGenieIDEAPlugin/issues/310

Maybe also add tsx and jsx for React?

Made a start with a list in issue #310

authors: mydeveloperplanet stephanj wimdeblauwe

repo: devoxx/DevoxxGenieIDEAPlugin


text:
wisdeom 깃헙액션 완료

각 챌린지 미션을 완료 할때 마다 각자 자신의 항목을 수정하는 PR을 생성해 주세요.

챌린저 정보
챌린저의 정보를 아래에 남겨주세요.

팀 이름: Chamomile

Microsoft Learn 프로필 URL은 https://docs.microsoft.com/ko-kr/users/******와 같이 생겼습니다.

Microsoft Learn 프로필 URL: https://docs.microsoft.com/ko-kr/users/jihyeeom-6719
GitHub ID: @wisdeom

아래는 SNS 챌린지의 경우에만 입력해 주세요.

다양한 SNS가 있지만, 여기서는 트위터, 페이스북, 인스타그램만 인정합니다.

SNS 이름: 인스타그램
SNS ID: @wisdeom

완료된 챌린지

이번에 완료된 챌린지의 내용을 마킹해주세요.

[] 애저 정적 웹 앱 챌린지 완료
[x] 깃헙 액션 챌린지 완료
[] 소셜미디어 인증샷 챌린지 완료
[] 애저 정적 웹 앱 URL 제출 챌린지 완료
[] 애저 정적 웹 앱 리포지토리 제출 챌린지 완료
[] 블로그 후기 URL 제출 챌린지 완료

@wisdeom 챌린지하나당 하나의 PR만 올려주세요:)

/ghasignoff

repo: devrel-kr/HackaLearn


text:
Difficulty Levels Issue #13

Followed the style of the theme selector to stay consistent.

With different level score should also change differently. Can you fix that?

@Jflyer45 as @Neeraj319 has already worked on this feature I'll have to reject one. Are you fine if I reject yours which gives him opportunity to contribute more?

I did dibs it first but that's fine. They should condense their code tho

@Jflyer45  okay, need to setup prettier as to not conflict code structure.

@Jflyer45 your implementation is much better and follows the current conventions of this project so I'm accepting this

repo: devsargam/SnakeGame


text:
⚠ Mobitopup has degraded performance

In ff3e51d, Mobitopup (https://napcard.voz.tech) experienced degraded performance:

HTTP code: 200
Response time: 19060 ms

Resolved: Mobitopup performance has improved in 1fde1b1.


text:
일부 국가들에서 자동 업데이트가 제대로 되지 않음

대다수의 유럽 국가를 포함한 일부 국가들에서 자동 업데이트가 오작동하는 문제를 발견하였습니다.
원인은, DFAssist는 20170901.1 처럼 되어있는 버전을 decimal로 파싱해서 최신 버전과 비교를 하는데,
한국과 미국 등은 소수점을 . 을 이용해 마킹하기 때문에 20170901.1 은 올바른 실수였고 파싱에 문제가 없었지만
유럽 등은 소수점을 , 혹은 띄어쓰기를 이용해 마킹하는 경우도 많기 때문에
OS의 표기 설정이 유럽으로 되어 있다면 20170901.1 의 파싱을 실패해
바로 catch로 빠져나가 더 이상 업데이트를 진행하지 못 하던 문제였습니다.
다행히 c#의 decimal.Parse 함수에는 IFormatProvider 를 받는 오버라이드가 있어서,
기존 decimal.Parse(version) 코드를 decimal.Parse(version, new CultureInfo("en-us")) 로 변경하는 식으로 문제를 해결했습니다.
일단은 원인을 파악하고 문제를 해결했지만, 혹시라도 비슷한 상황에 처하실 분이 계실 때를 대비해 정보 공유차 남겨놓습니다.

자동 업데이트가 안 되는 버전을 배포하면 배포 할 수록 버전 파편화가 심해지기 때문에 이번에는 빠르게 다음 버전을 릴리즈하겠습니다.

repo: devunt/DFAssist

license: unlicense


text:
大神，有几个问题问一下

运行了three的例子，发现滨崎步那个视频太卡了，zoom变换和拖拽都会卡住，并且非常消耗CPU，几乎没办法正常播放。
还有一个问题想问，就是苏州那个例子three拉伸的三维模型，那个多边形建筑数据是怎么取的，自己画的吗（但是感觉数据量很大呢）？
如果是自己画的有什么方便画多边形的工具吗？

@deyihu 大神求解答

@binfenshijie
你好，卡的原因为 程序一直在渐进加载房屋数据

等数据加载完了就不卡了；
视频播放不了，因为github的cdn在国内太慢了，视频流速度跟不上导致的，我这边看了一下，网速还可以的，正常加载视频；
如果等数据加载完了还是卡，那你的电脑配置估计有点差，我这边是不卡的；
至于房屋数据的制作，这个网站可以帮你  osmbuildings ，可以自己下载一些数据
另外这个demo是我练手用到，如果在项目中使用注意风险

authors: binfenshijie deyihu

repo: deyihu/maptalks-three-test


text:
Failed to execute 'index' on 'IDBObjectStore': The specified index was not found.

Hi,
i have a problem with a query for which an index is used.
The DB document is the following:
choiceAnswersChoices: '++id, deleted, questionId -> questions.id, creationDate, modificationDate, [id+deleted]',
The query is this:
db.choiceAnswersChoices.where({ id: intId, deleted: 0 }).first()
The error message is this:
name: "NotFoundError"
message: "Failed to execute 'index' on 'IDBObjectStore': The specified index was not found."
When i remove the index [id+deleted] the problem disappears an all work fine.
How can i solve it?
Best regards

Sounds familiar that both Chromium and Firefox have issue with including an autoincremented primary key in another compound index. This however does not have to be that issue. Could also be an issue in Dexie. If you had the time to create a failing test that reproducers this in a PR, that would help out nailing down the issue.


text:
Issue if you resize the browser screen (Chrome)

I noticed that when you resize the browser screen the content of the tab shrinks and won't expand when you expand the browser window back to its original size. You would have to "refresh" the page for the content of the active tab to also size back. It is a great extension and it would be nice if this is fixed. Qlik June 2017 SR1, Chrome build: 60.0.3112.90

Same issue in IE 11.0.10240.17443 and Qlik june 2017 SR1.

Same issue in Chrome.  It would be great if this gets fixed.  Thanks.

Hello to all,
I've created a pull request that I think, solves the issue (see #32).
Could someone verify that this solves the problem on your end before I merge it to master?

I tested it.  The new fix solved the problem.  Thanks a lot!!

I am glad to hear that. I've just merged the fix to master.
Closing the issue now. Feel free to reopen it if you still see this happening

authors: dfarache enaoki geck123 marcoyukon

repo: dfarache/Tabbed-Container-Extension


text:
feat: block header validation

Adds validation to the block headers. This code has been running on a testnet with the full mainnet state
to ensure that we don't have false negatives.

Did you intend to have this be based on #128? Some changes seem to be coming from that one actually. Or is this one supposed to supersede the previous one?

Yes, correct. I merged #128 so this should now be resolved.

repo: dfinity/bitcoin-canister


text:
Apply the detected changes

Fixes #6
Apply the proposed changes.
If you specify --apply, it will ask for confirmation after printing the results for every target.
If you also specify --no-verify, it will apply the changes without confirmation. Haven't actually tested this part yet, but that's the way it should work.
One caveat here is that the pretty printing of the package description is different than the input file in a lot of cases, so it will mess up the .cabal file in question. Also I made it ignore package.yaml files. Maybe both of those things should be warnings.
Checklist:

[x] Test --apply
[x] Test --no-verify
[x] Add warnings for changing .cabal file and ignoring package.yaml
[x] If possible, instead of pretty printing the output, maybe do something like parsing the file halfway and modifying it in-place to cause as little churn as possible. Could do something like parsing test-suite <name> *> indentation *> build-depends <* end-indentation, overwriting the build-depends, and overwriting.

As of the last commit, I tested it like this:

add transformers as a dependency to prune-juice.cabal
run stack run -- prune-juice --apply apply-no-verify --apply-strategy smart
it correctly removed the dependency from the file, however it slightly changed the format

@mirko-plowtech do you think this fixes your issue? You can test it out by running the following:
stack run -- prune-juice --apply

If you don't want it to prompt before applying, run
stack run -- prune-juice --no-verify

If it messes up your .cabal file, you can try running in "safe" mode with
stack run -- prune-juice --apply-strategy safe

I attempted this on my company's cabal files, which use common stanzas, and it didn't apply any of the changes. So I'll try to parse the common stanzas.

@mirko-plowtech do you think this fixes your issue? You can test it out by running the following:
stack run -- prune-juice --apply

If you don't want it to prompt before applying, run
stack run -- prune-juice --no-verify

If it messes up your .cabal file, you can try running in "safe" mode with
stack run -- prune-juice --apply-strategy safe

Sorry the delay, I will try to test it this weekend =)

I'm going to merge this so that some other contributions can be merged on top of it.

authors: dfithian mirko-plowtech

repo: dfithian/prune-juice


text:
#include : Failed to compile the shader

I'm trying to add a simple include to my shader:
#version 330
#extension GL_GOOGLE_include_directive : require
#include "common.glsl"

in vec4 color;
out vec4 outColor;

void main() {
   outColor = vec4(color);
}

ShaderEd finds the included file and compiles it.
I know this because it displays syntax errors correctly if I add some.
But then, the Shader pass fails compilation with the error "Failed to compile the shader(s)"
I tried enabling the logs, but they gave no additional information about what's wrong.
I'm on Windows 10 x64
Any idea?

Thank you for reporting this issue. I've pushed a commit that fixes this. The fix will be available in SHADERed v1.4.2

For what it's worth, I'm on SHADEREd v1.5.6 and still seeing this exact same issue

authors: dfranx gregschlom zeroinformatique

repo: dfranx/SHADERed


text:
possibility of animation?

is there anyway at all to animate the tree nodes as they are rendered to and from the dom? this libraries almost perfect as far as dev experience and accessibility is concerned. id even settle for a toggle on the root config or a node callback that wraps each underlying ul in a parent component so we could wrap each ul in something like framer-motion....without any animation it immediately stands out in applications that have a modicum of micro interactions....

This is outside of the scope of this library. But if you want to add it yourself, you can do it via the provided noderenderer function and with CSS. Please don’t ask us how. That’s why we made an issue template (which you ignored) that clarifies that we can’t answer Stack Overflow style questions. Please take this question there after you’ve messed around with noderenderer.


text:
Activate JMH for testing on JDK8

The puzzle DEV-5f4df571 from #DEV has to be resolved:
https://github.com/dgroup/arch4u-pmd/blob/870567e72a9f230c6fe3ab05fd85e589deaf5acb/pom.xml#L205-L205
The puzzle was created by @dgroup on 07-Jan-22.
role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

For some reason I wasn't able to add GitHub labels `` to this issue (required=pdd; existing=bug, dependencies, documentation, duplicate, enhancement, good first issue, help wanted, invalid, pdd, question, wontfix). Please, submit a ticket to us with the text you see below:
POST https://api.github.com/repos/dgroup/arch4u-pmd/issues/10/labels: 403 - Must have admin rights to Repository. // See: https://docs.github.com/rest/reference/issues#add-labels-to-an-issue
/app/vendor/bundle/ruby/2.6.0/gems/octokit-4.20.0/lib/octokit/response/raise_error.rb:14:in `on_complete'
/app/vendor/bundle/ruby/2.6.0/gems/faraday-1.8.0/lib/faraday/middleware.rb:19:in `block in call'
/app/vendor/bundle/ruby/2.6.0/gems/faraday-1.8.0/lib/faraday/response.rb:59:in `on_complete'
/app/vendor/bundle/ruby/2.6.0/gems/faraday-1.8.0/lib/faraday/middleware.rb:18:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/octokit-4.20.0/lib/octokit/middleware/follow_redirects.rb:73:in `perform_with_redirection'
/app/vendor/bundle/ruby/2.6.0/gems/octokit-4.20.0/lib/octokit/middleware/follow_redirects.rb:61:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/faraday-1.8.0/lib/faraday/request/retry.rb:148:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/faraday-1.8.0/lib/faraday/rack_builder.rb:154:in `build_response'
/app/vendor/bundle/ruby/2.6.0/gems/faraday-1.8.0/lib/faraday/connection.rb:516:in `run_request'
/app/vendor/bundle/ruby/2.6.0/gems/faraday-1.8.0/lib/faraday/connection.rb:281:in `post'
/app/vendor/bundle/ruby/2.6.0/gems/sawyer-0.8.2/lib/sawyer/agent.rb:94:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/octokit-4.20.0/lib/octokit/connection.rb:156:in `request'
/app/vendor/bundle/ruby/2.6.0/gems/octokit-4.20.0/lib/octokit/connection.rb:28:in `post'
/app/vendor/bundle/ruby/2.6.0/gems/octokit-4.20.0/lib/octokit/client/labels.rb:127:in `add_labels_to_an_issue'
/app/objects/github_tagged_tickets.rb:51:in `submit'
/app/objects/commit_tickets.rb:38:in `submit'
/app/objects/emailed_tickets.rb:35:in `submit'
/app/objects/sentry_tickets.rb:46:in `submit'
/app/objects/puzzles.rb:89:in `block in expose'
/app/objects/puzzles.rb:80:in `loop'
/app/objects/puzzles.rb:80:in `expose'
/app/objects/puzzles.rb:33:in `deploy'
/app/objects/job.rb:38:in `proceed'
/app/objects/job_starred.rb:33:in `proceed'
/app/objects/job_recorded.rb:32:in `proceed'
/app/objects/job_emailed.rb:35:in `proceed'
/app/objects/job_commiterrors.rb:36:in `proceed'
/app/objects/job_detached.rb:48:in `exclusive'
/app/objects/job_detached.rb:36:in `block in proceed'
/app/objects/job_detached.rb:36:in `fork'
/app/objects/job_detached.rb:36:in `proceed'
/app/0pdd.rb:357:in `block in <top (required)>'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.1.0/lib/sinatra/base.rb:1675:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.1.0/lib/sinatra/base.rb:1675:in `block in compile!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.1.0/lib/sinatra/base.rb:1013:in `block (3 levels) in route!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.1.0/lib/sinatra/base.rb:1032:in `route_eval'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.1.0/lib/sinatra/base.rb:1013:in `block (2 levels) in route!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.1.0/lib/sinatra/base.rb:1061:in `block in process_route'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.1.0/lib/sinatra/base.rb:1059:in `catch'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.1.0/lib/sinatra/base.rb:1059:in `process_route'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.1.0/lib/sinatra/base.rb:1011:in `block in route!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.1.0/lib/sinatra/base.rb:1008:in `each'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.1.0/lib/sinatra/base.rb:1008:in `route!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.1.0/lib/sinatra/base.rb:1129:in `block in dispatch!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.1.0/lib/sinatra/base.rb:1101:in `block in invoke'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.1.0/lib/sinatra/base.rb:1101:in `catch'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.1.0/lib/sinatra/base.rb:1101:in `invoke'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.1.0/lib/sinatra/base.rb:1124:in `dispatch!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.1.0/lib/sinatra/base.rb:939:in `block in call!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.1.0/lib/sinatra/base.rb:1101:in `block in invoke'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.1.0/lib/sinatra/base.rb:1101:in `catch'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.1.0/lib/sinatra/base.rb:1101:in `invoke'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.1.0/lib/sinatra/base.rb:939:in `call!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.1.0/lib/sinatra/base.rb:929:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-protection-2.1.0/lib/rack/protection/xss_header.rb:18:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-protection-2.1.0/lib/rack/protection/path_traversal.rb:16:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-protection-2.1.0/lib/rack/protection/json_csrf.rb:26:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-protection-2.1.0/lib/rack/protection/base.rb:50:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-protection-2.1.0/lib/rack/protection/base.rb:50:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-protection-2.1.0/lib/rack/protection/frame_options.rb:31:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-2.2.3/lib/rack/logger.rb:17:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-2.2.3/lib/rack/common_logger.rb:38:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.1.0/lib/sinatra/base.rb:253:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.1.0/lib/sinatra/base.rb:246:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-2.2.3/lib/rack/head.rb:12:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-2.2.3/lib/rack/method_override.rb:24:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.1.0/lib/sinatra/base.rb:216:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.1.0/lib/sinatra/base.rb:1991:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.1.0/lib/sinatra/base.rb:1542:in `block in call'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.1.0/lib/sinatra/base.rb:1769:in `synchronize'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.1.0/lib/sinatra/base.rb:1542:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-2.2.3/lib/rack/handler/webrick.rb:95:in `service'
/app/vendor/ruby-2.6.0/lib/ruby/2.6.0/webrick/httpserver.rb:140:in `service'
/app/vendor/ruby-2.6.0/lib/ruby/2.6.0/webrick/httpserver.rb:96:in `run'
/app/vendor/ruby-2.6.0/lib/ruby/2.6.0/webrick/server.rb:307:in `block in start_thread'


text:
jq requirement breaks windows suppport

I tried installing MinGW and python and no dice. I don't think jq is available on windows via pip.
C:\Users\user\src\changedetection.io(master -> origin)
λ pip install jq
Collecting jq
  Using cached jq-1.3.0.tar.gz (2.7 MB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Building wheels for collected packages: jq
  Building wheel for jq (pyproject.toml) ... error
  error: subprocess-exited-with-error

  × Building wheel for jq (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [5 lines of output]
      running bdist_wheel
      running build
      running build_ext
      Executing: ./configure CFLAGS=-fPIC --prefix=C:\Users\user\AppData\Local\Temp\pip-install-bv3bfmag\jq_bfc06f477e2f4481a8c3efa8d867bad1\_deps\build\onig-install-6.9.4
      error: [WinError 2] The system cannot find the file specified
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for jq
Failed to build jq
ERROR: Could not build wheels for jq, which is required to install pyproject.toml-based projects

@orcutt989 hello, does this resolve your issue?

I havent tried that- but the error happens running from master.

@orcutt989 hmm that's not possible, because master doesnt have jq in the requirements.txt anymore.. are you sure you're up to date?
closing issue marked as done, please reopen if you know more

You literally made a commit yesterday that fixed this ssue. https://github.com/dgtlmoon/changedetection.io/commit/32ea1a8721e4ddbd69967a7e4753448f1e2ea6ad#diff-4d7c51b1efe9043e44439a949dfd92e5827321b34082903477fd04876edb7552L22

@orcutt989 not sure 'literally' is the word you're after there, but "I havent tried that- but the error happens running from master." you mean it happens after I made that commit?

https://www.quora.com/Why-do-people-say-literally-so-much aah ok

The date of this issue was before your commit to master that removed JQ as a requirement. I did not try it after the commit. I was not aware of the commit as you did not say "I pushed a commit that fixed it, try it now". You told me to retry the pip package, so I wanted to clarify that it was on master where I was experiencing the issue.

https://www.quora.com/Why-am-I-not-able-to-communicate-with-people-and-actually-fear-of-talking


text:
added keras2json converter for Keras version 1.0.0

I adapted the keras2json converter with respect to the output conventions used in Keras version 1.0.0.
In addition, the version number gets saved in the input HDF5 file and a warning is printed in case the Keras output files were generated using another Keras version.

Awesome! If I can confirm that everyone is using Keras 1.0 or later I can just replace the current converter with this one.

I merged the commit where you added this into my master branch.

repo: dguest/lwtnn


text:
jBrowserDriver is licensed under Apache 2

See: https://github.com/MachinePublishers/jBrowserDriver/tree/v1.0.0-RC1#jbrowserdriver

This just got merged in another PR. Thanks for the contribution anyway!

authors: dhamaniasad xiongtx

repo: dhamaniasad/HeadlessBrowsers


text:
feat: Splitting the route by org units

Summary
The previous implementation splits the route only by the program indicators. This PR splits the route by both program indicators and the organisation units. This is done by,

Initially fetching OUs and assigning to a route property
Implementing a new MultidimensionSplitter which generates all possible pairs of OUs and PIs.
Analytics call is done for every possible split generated in the above step
Continues the old route

Additionally,
Log4j2 was added to the project.

I agree bob. This change can be easily incorporated. I'll wait till we merge @claudemamo 's PR. Then I'll rebase on main branch and remove redundant stuff and implement grouping if it's not available.
One question though. Should we worry about character limit for GET requests when sending multiple ous? I guess it ranges from min of 2048 to few thousands and depends on how it's configured. Usually it's safer to aim at 2048 right?

Closing the PR since this is obsolete.


text:
feat: persist sorting information in AO (DHIS2-14955)

Implements DHIS2-14955
Fixes DHIS2-15248
Requires https://dhis2.atlassian.net/browse/DHIS2-14956

Key features

persist sorting details in LL AOs
apply sorting also to downloads

Description
Moved the sorting field and direction state from the Visualization component to the App.
The sorting details are fetched directly in the visualization/current object, in this way the sorting is correctly applied to dashboard items too when first loaded.
~One regression tho, is that changing sorting does not work in dashboard.~
~The reason is that the onDataSorted callback is only passed to the plugin by the LL app.~
The above has been fixed by adding the onDataSorted callback to the PluginWrapper component used by dashboard.

TODO

[x] figure out a solution for "temporarily" changing sorting in dashboard
[x] enable the new Cypress test when the backend support is in place

Screenshots
Sorting applied and returned in the AO:

LGTM

authors: edoardo jenniferarnesen


text:
Eliminar "Obtener posiciones y obtener Sexo"

En el menú de personajes para obras de teatro se mostraban las opciones obtener posiciones y obtener sexo, las cuales siempre estaban marcadas ya que era el primer paso a la hora de generar la red y por mantener el modelo que había en los otros 2 módulos.
Es redundante y hay que eliminarlo.
Quitar también el obtener posiciones en las películas, ya que es algo exclusivo de novelas.

Realmente no era obtener posiciones, sino obtener apariciones.
Esta opción creo que estaba incluida porque en caso de no marcar todos los checkbox de primeras y querer por ejemplo calcular el sexo o la etnia una vez calculadas las apariciones, habría que indicar de alguna forma que no se deben volver a calcular todas las apariciones de nuevo.
Lo dejo de momento parecido a como estaba, con la salvedad de que para obras de teatro, he fusionado las opciones de apariciones y sexo ya que siempre se calculan a la vez y no tiene sentido dar 2 opciones.
También he corregido el método para obtener etnia que estaba mal definido para obras de teatro.

Finalmente lo he quitado para que no quede redundante y simplificar el tratamiento que se hace


text:
docs: fixed text typo in README.md file

cloud computer has been fixed to cloud computing.

GJ First Pull Req

authors: Aclaputra dhupee


text:
listResp, err := client.Warehouses().GetListOfWarehouses(context.Background()) error:

error when getting warehouse list	{"error": "json: cannot unmarshal number into Go struct field GetListOfWarehousesResult.result.working_days of type ozon.WorkingDay"}

Hi. Thank you once again for reporting problems in this library. I'm on my way to fix it.
Want to add that this may happen due to incorrectness in official Ozon API Seller documentation. It says this field is an array of strings, but it's array of integers actually.
Will fix soon.

Fixed in #83

waiting for new release

发件人: Kirill @.>
发送时间: 2024年4月21日 15:42
收件人: diPhantxm/ozon-api-client @.>
抄送: elder frog @.>; Author @.>
主题: Re: [diPhantxm/ozon-api-client] listResp, err := client.Warehouses().GetListOfWarehouses(context.Background()) error: (Issue #82)
Fixed in #83https://github.com/diPhantxm/ozon-api-client/pull/83
―
Reply to this email directly, view it on GitHubhttps://github.com/diPhantxm/ozon-api-client/issues/82#issuecomment-2068089484, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGM46IF5UROAXDA5QMAO373Y6PM5JAVCNFSM6AAAAABGRLMUQ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRYGA4DSNBYGQ.
You are receiving this because you authored the thread.Message ID: @.***>

authors: JoeyFrancisTribbiani diPhantxm

repo: diPhantxm/ozon-api-client


text:
Autoload order keeps changing when using Dialogic with another plugin (Maaack's Menus Template)

The problem
Describe the bug
This is a crossed bug, so I cannot say who's responsible: Godot, Dialogic or the other plugin Maaack's Menus Template.
Every day I launch the project and observe Autoload order has been changing, with either Dialogic's own Dialogic going to the bottom, or Maaack's Menus Template 4 singletons (AppConfig, SceneLoader, ProjectMusicController, ProjectUISoundController) going to the bottom.

This may be a limitation of Godot who cannot decide which plugin to initialize first, but still I don't see why it would reorder autoloads already added.
Sometimes, Maaack's Menus Template 4 singletons are completely removed from the project after issues like compile errors, I notice this after closing project sometimes, whereas Dialogic is never removed, so maybe Dialogic is not the culprit after all.
When working with a team I must tell my collaborators not to commit those autoload order change, it can create unwanted conflicts.
To Reproduce
Steps to reproduce the behavior:

Make a project and install both Maaack's Menus Template and Dialogic addons
Make sure that both plugins are enabled
Do some stuff (the less precise step, cannot find exact trigger conditions; you can try to trigger parse errors for instance)
Check VCS
Close project
Check VCS
Open project
Check VCS
Revert your stuff (e.g. fix parse errors)
Check VCS

Expected behavior
Autoload order should be stable
System (please complete the following information):

OS: Linux Ubuntu 22.04
Godot Version: v4.2.1.stable.official [b09f793f5]
Dialogic Version: main commit https://github.com/dialogic-godot/dialogic/commit/a9c56aa674c30cf242b2b87e5749235bd2d2fe53 (2024-05-05)

Solutions
Workaround
I just revert the change after closing the project, and make sure to never commit them.
Possible fixes
Godot / Maaack's Menus Template could avoid removing autoload singletons when there are project issues.

This has been fixed on the main branch already.
The branch is currently experimental, you can try and use it or backport the fix to your current version.

authors: CakeVR hsandt

repo: dialogic-godot/dialogic


text:
revert: "build: dialtone vue styles (#936)"

Description
We're no longer embedding dialtone-vue styles on dialtone as we had issues related with Vue versions and scoped styles.
This reverts commit #936
Pull Request Checklist

[x] Ask the contributors if a similar effort is already in process or has been solved.
[x] Review the contribution guidelines.
[x] Use staging as your pull request's base branch. (All PRs using production as its base branch will be declined).
[x] Ensure all gulp scripts successfully compile.
[x] Update, remove, or extend all affected documentation.
[x] Ensure no private Dialpad links or info are in the code or pull request description (Dialtone is a public repo!).

Obligatory GIF (super important!)

Let's do a release after this goes in so we can update in ubervoice

authors: braddialpad juliodialpad

repo: dialpad/dialtone


text:
Efficiency of comparison to the feasible set

The distribution of hill nbs for draws from a feasible set of given s,n is a knowable thing. In moving towards making comparisons to the feasible set using sim models, it's a reasonable expectation that there will be be repeated s,n combinations and that we will want to make a lot of comparisons.
Thinking to start populating a centralized database, essentially a massive table of s, n, hill1, hill2 and then 1000-5000 records for each combination (or the number possible). I could store this as a targets thing but I'd prefer not to...seems like an opportunity to practice databases, overkill for this but good practice.

use sqlite x RSqlite
(this is what drake used also)
https://solutions.posit.co/connections/db/databases/sqlite/
https://sqlitebrowser.org/dl/
https://swcarpentry.github.io/sql-novice-survey/setup.html
If you ultimately want to plug this into an R package that might be tricky depending on the ultimate size of the db.

repo: diazrenata/upgraded-pancake


text:
Possibility of integrating OWL2 Reasoner and GeoSPARQL?

Hello,
I'm evaluating whether Tentris would be a good pick for a project my company is working on as we're looking for a Knowledge-Graph solution with semantic reasoning/inference capabilities and GeoSPARQL support.
As far as I could see, Tentris does not integrate reasoning/GeoSPARQL so far. Thus, I'm wondering if there would be any chance if this could be implemented by you or, if possible, could give us some guideline on how to do it ourselves and eventually contribute to your project.
Lastly, are there any benchmarks for Tentris?
Thank you

Hi sorry for the long delay.
We do not plan to integrate reasoning or GeoSPARQL here at the moment. But contributions are always welcome.
For both, a good starting point would be looking at how the query library in hypertrie works. reasoning and GeoSPARQL should be implemented as an extended version of that library.
Benchmarks can be found in the following papers:

ESWC, 2024, #inproceedings, Efficient Evaluation of Conjunctive Regular Path Queries Using Multi-way Joins, By Nikolaos Karalis, Alexander Bigerl, Liss Heidrich, Mohamed Ahmed Sherif, Axel-Cyrille Ngonga Ngomo
ECML PKDD, 2024, #inproceedings, Evaluating Negation with Multi-way Joins Accelerates Class Expression Learning, By Nikolaos Karalis, Alexander Bigerl, Caglar Demir, Liss Heidrich, Axel-Cyrille Ngonga Ngomo
SEMANTiCS, 2023, #inproceedings, Native Execution of GraphQL Queries over RDF Graphs Using Multi-way Joins, By Nikolaos Karalis, Alexander Bigerl, Axel-Cyrille Ngonga Ngomo
The Semantic Web -- ISWC 2022, 2022, #article, Hashing the Hypertrie: Space- and Time-Efficient Indexing for SPARQL in Tensors, By Alexander Bigerl, Lixi Conrads, Charlotte Behning, Muhammad Saleem, Axel-Cyrille Ngonga Ngomo,
The Semantic Web -- ISWC 2020, 2020, #article, Tentris -- A Tensor-Based Triple Store, By Alexander Bigerl, Felix Conrads, Charlotte Behning, Mohamed Ahmed Sherif, Muhammad Saleem, Axel-Cyrille Ngonga Ngomo

authors: bigerl gpicciuca

repo: dice-group/tentris


text:
api不支持28

api不支持28

确实不支持28及以上 Androidx

可以看看我开发的 xPlugin，兼容性更好，已经测试支持Android11，不依赖support库，想用啥用啥，插件用的库和宿主隔离，不会冲突。插件可完全原生api开发。

authors: Roy1994419 showkiwi wyouflf

repo: didi/VirtualAPK


text:
Loss of so Library：x_ops.so

ERROR:
tensorflow.python.framework.errors_impl.NotFoundError: /home/delta/delta/layers/ops/x_ops.so: cannot open shared object file: No such file or directory

I got the same issue. How to fix the problem??

@Susan19900316  You probably didn't compile the ops successfully. Could you run this line again
and give more information if it fails: https://github.com/didi/delta/blob/master/tools/Makefile#L85

@hankun11  I install Delta in steps like this:

cd tools
./install/install-delta.sh nlp gpu
source activate delta-py3.6-tf1.14
cd ..
source env.sh
pushd egs/mock_text_cls_data/text_cls/v1
7../run.sh

In the seventh step, i had two problems. The first one is that some python libraries, such like matplotlib,hurry, hurry.filesize and pyyaml,  haven't been installed. The second one is the loss of x_ops.so. The details follow:
./run.sh
/bin/bash: /home/Software/miniconda/envs/robot_pytorch/lib/libtinfo.so.6: no version information available (required by /bin/bash)
/home/Software/miniconda/envs/delta-py3.6-tf1.14/lib/python3.6/site-packages/tensorflow/python/framework/dtypes.py:516: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_qint8 = np.dtype([("qint8", np.int8, 1)])
/home/Software/miniconda/envs/delta-py3.6-tf1.14/lib/python3.6/site-packages/tensorflow/python/framework/dtypes.py:517: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_quint8 = np.dtype([("quint8", np.uint8, 1)])
/home/Software/miniconda/envs/delta-py3.6-tf1.14/lib/python3.6/site-packages/tensorflow/python/framework/dtypes.py:518: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_qint16 = np.dtype([("qint16", np.int16, 1)])
/home/Software/miniconda/envs/delta-py3.6-tf1.14/lib/python3.6/site-packages/tensorflow/python/framework/dtypes.py:519: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_quint16 = np.dtype([("quint16", np.uint16, 1)])
/home/Software/miniconda/envs/delta-py3.6-tf1.14/lib/python3.6/site-packages/tensorflow/python/framework/dtypes.py:520: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_qint32 = np.dtype([("qint32", np.int32, 1)])
/home/Software/miniconda/envs/delta-py3.6-tf1.14/lib/python3.6/site-packages/tensorflow/python/framework/dtypes.py:525: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
np_resource = np.dtype([("resource", np.ubyte, 1)])
/home/Software/miniconda/envs/delta-py3.6-tf1.14/lib/python3.6/site-packages/tensorboard/compat/tensorflow_stub/dtypes.py:541: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_qint8 = np.dtype([("qint8", np.int8, 1)])
/home/Software/miniconda/envs/delta-py3.6-tf1.14/lib/python3.6/site-packages/tensorboard/compat/tensorflow_stub/dtypes.py:542: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_quint8 = np.dtype([("quint8", np.uint8, 1)])
/home/Software/miniconda/envs/delta-py3.6-tf1.14/lib/python3.6/site-packages/tensorboard/compat/tensorflow_stub/dtypes.py:543: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_qint16 = np.dtype([("qint16", np.int16, 1)])
/home/Software/miniconda/envs/delta-py3.6-tf1.14/lib/python3.6/site-packages/tensorboard/compat/tensorflow_stub/dtypes.py:544: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_quint16 = np.dtype([("quint16", np.uint16, 1)])
/home/Software/miniconda/envs/delta-py3.6-tf1.14/lib/python3.6/site-packages/tensorboard/compat/tensorflow_stub/dtypes.py:545: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_qint32 = np.dtype([("qint32", np.int32, 1)])
/home/Software/miniconda/envs/delta-py3.6-tf1.14/lib/python3.6/site-packages/tensorboard/compat/tensorflow_stub/dtypes.py:550: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
np_resource = np.dtype([("resource", np.ubyte, 1)])
Traceback (most recent call last):
File "local/generate_mock_data.py", line 19, in
from delta.data.utils.test_utils import mock_a_text_file
File "/home/Projects/delta/delta/data/utils/init.py", line 17, in
from delta.data.utils.common_utils import *
File "/home/Projects/delta/delta/data/utils/common_utils.py", line 26, in
from delta.data.preprocess.text_ops import tokenize_label
File "/home/Projects/delta/delta/data/preprocess/text_ops.py", line 22, in
from delta.layers.ops import py_x_ops
File "/home/Projects/delta/delta/layers/init.py", line 27, in
from delta.layers.common_layers import *
File "/home/Projects/delta/delta/layers/common_layers.py", line 22, in
from delta.data.feat import speech_ops
File "/home/Projects/delta/delta/data/feat/init.py", line 17, in
from delta.data.feat import speech_ops
File "/home/Projects/delta/delta/data/feat/speech_ops.py", line 25, in
from delta.layers.ops import py_x_ops
File "/home/Projects/delta/delta/layers/ops/py_x_ops.py", line 27, in
tf.compat.v1.resource_loader.get_path_to_datafile('x_ops.so'))
File "/home/Software/miniconda/envs/delta-py3.6-tf1.14/lib/python3.6/site-packages/tensorflow/python/framework/load_library.py", line 61, in load_op_library
lib_handle = py_tf.TF_LoadLibrary(library_filename)
tensorflow.python.framework.errors_impl.NotFoundError: /home/Projects/delta/delta/layers/ops/x_ops.so: cannot open shared object file: No such file or directory

@hankun11  Sorry. I have fixed the issue. Something wrong appeared in the step 'make', but i did not found.

repo: didi/delta


text:
Make record to model logic shared

closes #200
Presentation Record logic shared fully
Signed-off-by: morrieinmaas moritz@animo.id

@TimoGlastra Any feedback welcome!
Maybe you can spot some more things that can be shared?
Think this should largely cover the shared logic and conversion to models as discussed.

repo: didx-xyz/aries-cloudapi-python


text:
Option to disable "New Note" button

Hey @diegoeis ,
could it be possible to add an option to disable the "New Note" button located at the bottom of the file explorer? If there's enough notes and/or folders, or the Obsidian window is small enough, that button overlaps the last notes and it's impossible to select them without collapsing opened folders.
And, could it be also possible to have the option to disable the translucency and the margin below the "new folder, sort order, and collapse" buttons? This is just an aesthetic consideration, but those effects can be a bit distracting and off-putting when everything else is so clean and simple; and without that effect, that empty space could feel a bit purposeless.
Thanks for reading my humble feedback. Love your theme, it's amazing.

Hey!
Thank you so much for the message.
I just to update the theme with your considerations at this moment.
Can you try and give the feedback?

Hi Diego,
thanks a lot for reading my comment and replying so quickly. I've updated the theme and now it's working great :)
Regarding further feedback I'd be really hard-pressed to provide any useful takes, but I've tried listing here the only nitpicks which I managed to spot:

It'd be nice to have the option to hide the 'New note' button and switch it for the default icon and location just beside the new folder icon at the top of the file explorer. Honestly, it doesn't bother me much where it is now because it's so well integrated and I get it's not only a design choice, but also a helpful indication for beginners; but in terms of hierarchy and association, having the 'create new note' button/functionality besides the 'create new folder' might feel a bit better for usability. Moreover, once you learn the 'create new note' shortcut, it can feel like that button is taking some screen real estate which could be saved by using the default icon instead (if there's space there, of course. I have lots, but I'm on a laptop and also maybe that's not everyone's case).

The callouts now seem to only take the space of their content instead of the full-width of the page so, in case there's a few of them one after another, the overall design can feel like it's losing a certain degree of visual cohesiveness. Also, in my end the paddings are slightly off, and it seems the emojis might be as well (not vertically aligned with the text).

There's a border which appears when hovering over callouts and tables, but not over other elements like code blocks or fenced text. I guess it's an expected behaviour but I thought I'd better mention it just in case it isn't.

That's all I got. Sorry for the long read, I hope it can be helpful somehow. Thanks again for designing such an awesome theme!

Hey @thisisgonnatakeawhile the answers:

Sorry, I didn't mention last comment that you can now enable/disable this using Style Settings (plugin) in Config. Like image attached.
Fixed.
Yeah, don't know why obsidian are showing these borders. usually these borders just show up in components created by plugins, embeds and code blocks. Didn't saw that before in callouts... Anyway, I think are better now, without spaces/padding.

Thanks for the fixes and the didactic and kind replies @diegoeis. Somehow I missed the option toggle in Style Settings before replying. My bad! And sorry for unnecessarily reiterating that point.
I'll close the issue thread here with a heartfelt thank you for developing Obsidianotion and making my writing much more comfy, pleasant, and productive.
All the best :)

Thanks a lot for the suggestions and feedbacks!!
On Fri, 12 May 2023 at 18:16 thisisgonnatakeawhile @.***>
wrote:

Closed #1 https://github.com/diegoeis/obsidianotion/issues/1 as
completed.
—
Reply to this email directly, view it on GitHub
https://github.com/diegoeis/obsidianotion/issues/1#event-9236695550, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAOUKAUIIJMCPBWXTCSZA7DXF2SBVANCNFSM6AAAAAAX6EGYX4
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Valeu! Diego Eis http://twitter.com/diegoeis @.***/
http://tableless.com.br/

authors: diegoeis thisisgonnatakeawhile

repo: diegoeis/obsidianotion

license: Unlicense


text:
[prover] separate functions for is_native and is_intrinsic

Previously, is_native conflated these two concepts, which frustrates analysis clients that want to treat these differently.
The motivation for this change is to support the read/write set analysis, which needs to analyze the body of functions marked as intrinsic.
The PR changes all uses of is_native in bytecode_translator.rs and spec_instrumentation.rs to is_native && is_intrinsic. There are more uses of is_native in some of the other bytecode analyses/transformations (e.g., borrow_analysis), but I left them as is because it seems like they also want to ignore the intrinsic pragma. Let me know if this wrong and I can fix them.

How is is_intrinsic different from is_native?

How is is_intrinsic different from is_native?

How is is_intrinsic different from is_native?

Native is a Move VM feature that allows Move functions to be implemented in the host language (e.g., Rust), whereas intrinsic is a Move prover feature that (to my understanding) allows the prover to use a handwritten model of a Move function instead of its Move bytecode implementation.
A function foo is marked native via public native fun foo() { ... } and intrinsic via spec module { pragma intrinsic = true }

How is is_intrinsic different from is_native?

Native is a Move VM feature that allows Move functions to be implemented in the host language (e.g., Rust), whereas intrinsic is a Move prover feature that (to my understanding) allows the prover to use a handwritten model of a Move function instead of its Move bytecode implementation.
A function foo is marked native via public native fun foo() { ... } and intrinsic via spec module { pragma intrinsic = true }

/land

/land

/land

/land

authors: bmwill sblackshear shazqadeer

repo: diem/diem


text:
[RUSTSEC-2021-0093][rel-1.3] crossbeam-deque 0.8.0 -> 0.8.1

Motivation
https://github.com/diem/diem/issues/9009
https://rustsec.org/advisories/RUSTSEC-2021-0093
Have you read the Contributing Guidelines on pull requests?
y
Test Plan
existing coverage
Related PRs
(If this PR adds or changes functionality, please take some time to update or suggest changes to the docs at https://developers.diem.com, and link to your PR here.)
If targeting a release branch, please fill the below out as well

Justification and breaking nature (who does it affect? validators, full nodes, tooling, operators, AOS, etc.)
dependency update

Comprehensive test results that demonstrate the fix working and not breaking existing workflows.
existing tests

Why we must have it for V1 launch.
Vulnerability seems real.

What workarounds and alternative we have if we do not push the PR.
Wait for 1.5 roll.

release binaries dependency change summary:
target packages:
  M crossbeam-deque 0.8.1 (transitive third-party, crates.io)
    * version upgraded from 0.8.0
    * (unchanged features: crossbeam-epoch, crossbeam-utils, default, std)

LEC dependency change summary:
target packages:
  M crossbeam-deque 0.8.1 (transitive third-party, crates.io)
    * version upgraded from 0.8.0
    * (unchanged features: crossbeam-epoch, crossbeam-utils, default, std)

LSR dependency change summary:
target packages:
  M crossbeam-deque 0.8.1 (transitive third-party, crates.io)
    * version upgraded from 0.8.0
    * (unchanged features: crossbeam-epoch, crossbeam-utils, default, std)

/land

authors: libra-action msmouse sausagee


text:
Consider throwing away infer_schema

There is no way rustc ever expected code to make database connections at compile-time. Why not just make an auxiliary tool that outputs Rust code that can then be included in the project? Why put such a heavy thing (database connections) at compile-time?
This means that we will never be able to enforce using miri or stuff like that to run proc macros.

It's already included in diesel print-schema.

We recommend using diesel print-schema in the long run, but infer_schema! is still a very useful tool for prototyping when the schema file churns a lot.

I see your reasoning and I too want faster compile times, but I don't think this is something that's easy to fix. I'd really like to know what you have in mind :)

How is it more useful than using the print command?

More useful? Hard to say. More convenient? Yes: It literally is one less thing you need to do. You will never forget to run diesel print-schema > src/schema.rs after changing your DB.

There is no way rustc ever expected code to make database connections at compile-time.

That's a very weird argument. Proc macros and build scripts can do whatever they want. They are not required to be run in a sandbox and are written in a Turing complete language.

The more projects do fancy things at compile-time, the less freedom the Rust team will have to improve compile times, AFAICT.

What optimizations are we talking about?

Memoization and caching for incremental compilation? Is there a way for you to detect proc macros to be pure by try running it through miri or something like that? If so, what stops from falling back to the way things are currently done when that fails? Or requiring proc-macros to set a "pure" flag?
Skip potentially costly LLVM-based compilation by interpreting the code in miri? Not sure how fast miri is. That may be an interesting tradeoff.

My point was that we can't experiment with using MIRI for procedural macros if procedural macros do I/O and connect to databases and whatnot.
I've personally never expected people to do things like that, even though Rust is a Turing-complete language and used to implement them proc macros.

The more projects do fancy things at compile-time, the less freedom the Rust team will have to improve compile times, AFAICT.

Given that proc macros are capable of running any arbitrary code, the Rust team will always need to assume that proc macros do anything, including network or Disk IO. Whether our project takes advantage of those capabilities is irrelevant.

I've personally never expected people to do things like that

Perhaps seeing these use cases in the wild will change your expectations. You may also be interested in embed_migrations!, which would also prevent things like using MIRI for proc macros.

Given that proc macros are capable of running any arbitrary code, the Rust team will always need to assume that proc macros do anything, including network or Disk IO. Whether our project takes advantage of those capabilities is irrelevant.

That's because MIRI wasn't a thing when proc macros landed. If no one uses them in such dubious ways, the Rust team will be able to easily switch their evaluation to MIRI. If popular projects start relying on this behaviour, they won't be able to.
To me your justification of your usage of proc macros sound like people wanting Rust to enforce a specific order in HashMap to be able to rely on it.

Perhaps seeing these use cases in the wild will change your expectations. You may also be interested in embed_migrations!, which would also prevent things like using MIRI for proc macros.

No, I'll keep try to make those disappear, because that's not where that code should run in the first place. I'll stop pursuing that objective here, though.

If no one uses them in such dubious ways

Again, claiming that our project has any impact on that is ridiculous. It is impossible to know if anyone is using Rust in a certain way. You can say for sure that someone is using something, but unless you have access to everybody's closed source repositories, it is impossible to say that someone isn't using something.

that's not where that code should run in the first place

Frankly, I'm not sure what gives you the right to say where other people's code should or shouldn't be run

Again, claiming that our project has any impact on that is ridiculous. It is impossible to know if anyone is using Rust in a certain way. You can say for sure that someone is using something, but unless you have access to everybody's closed source repositories, it is impossible to say that someone isn't using something.

In general, Rust has never been quite afraid of changing behaviour after the fact if a Crater run ends up green.

Frankly, I'm not sure what gives you the right to say where other people's code should or shouldn't be run

Oops, I'm sorry I meant to add "in my book" after that and removed it after I rephrased the sentence. :(

Enforcing proc macros to not have side effects and not use external resources reduces their usefulness quite a bit. I'd personally be very disappointed if this limitation was introduced. Not that I think there is any way to introduce it—crater or no crater, this is a huge change of a stable feature!
But wait: What is actually stopping us from experimenting with miri here? I've not dived deep into how miri does its thing, but I imagine that there is a way for it to give up, at which point you could fall back to the current way of executing them. Is this not possible? Is this in combination with a "this macro is pure" opt-in flag not sufficient?

Am 23.12.2017 um 16:00 schrieb Anthony Ramine notifications@github.com:
My point was that we can't experiment with using MIRI for procedural macros if procedural macros do I/O and connect to databases and whatnot.
I've personally never expected people to do things like that, even though Rust is a Turing-complete language and used to implement them proc macros.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

authors: Eijebong killercup nox sgrif

repo: diesel-rs/diesel


text:
PgConnection::establish isn't thread-safe on Windows with libpq v9.6.3

Setup
Versions

Rust: rustc 1.37.0 (eae3437df 2019-08-13)
Diesel: 1.4.2
Database: 11+197.pgdg14.04+1
Operating System Windows 10.0.17763 Build 17763
libpq: 9.6.3

Feature Flags

diesel: postgres

Problem Description
Sometimes the process crashes when establishing connections.
error: process didn't exit successfully: `target\release\pqconectiontest.exe` (exit code: 0xc0000374, STATUS_HEAP_CORRUPTION)

What are you trying to accomplish?
two independent threads connecting to the same database.
Steps to reproduce
use diesel::Connection;
use std::thread;

fn main() {
    let mut handles = Vec::new();
    for _ in 0..20 {
        let handle = thread::spawn(move || {
            let _con =
                diesel::PgConnection::establish("postgres://user:password@hostname/database"); //?sslmode=disable");
        });
        handles.push(handle);
    }
    for handle in handles {
        let _ = handle.join();
    }
}

run this program in release mode a few times.  sometimes it crashes with the reported error code.
if you add sslmode=disable then it never crashes.  It seems like something in libpq isn't thread-safe when creating SSL connections.

Could you grab a stacktrace of this crash using a debugger?

Can you also confirm that libpq was in fact linked with thread safety enabled? You can check this by calling pq_sys:: PQisthreadsafe().

original request for help with more details on Reddit
stack trace under lldb:
Process 23092 stopped
* thread #5, stop reason = Exception 0x80000003 encountered at address 0x7ffec0bf8906
    frame #0: 0x00007ffec0bf8907 ntdll.dll`RtlpNtMakeTemporaryKey + 21767
ntdll.dll`RtlpNtMakeTemporaryKey:
->  0x7ffec0bf8907 <+21767>: movb   $0x0, 0x5af42(%rip)       ; _fltused + 15759
    0x7ffec0bf890e <+21774>: retq
    0x7ffec0bf890f <+21775>: int3
    0x7ffec0bf8910 <+21776>: int3

modified example to include:
    unsafe {
        println!("PQisthreadsafe: {}", pq_sys::PQisthreadsafe());
    }

and output was
PQisthreadsafe: 1
error: process didn't exit successfully: `target\release\pqconectiontest.exe` (exit code: 0xc0000374, STATUS_HEAP_CORRUPTION)

I've spent the last 30 minutes or so trying to reproduce this locally and wasn't able to. Is there any other information you can give us that we might be able to use to reproduce? Perhaps you can provide a repo with a windows CI config that can reproduce the issue?

I'll see if I can get a repo together that builds the same as my desktop.  other things to note in my project are:

vcpkg 2019.08.27-nohash
RUSTFLAGS=-C target-feature=+crt-static

[patch.crates-io]
pq-sys = { git = 'https://github.com/sgrif/pq-sys.git' }

The patch was to pick up https://github.com/sgrif/pq-sys/pull/26

Just to clarify, you're using the msvc target then, not gnu?

Also just so you have some kind of workaround while we determine if this is a bug anywhere in our stack that we can do something about, you might want to try calling openssl::init() and then pq_sys::PQinitSSL(0) before you open any database connections (the first function manually initializes openssl, the second function will tell libpq not to try to initialize it)

yes, I'm using toolchain stable-x86_64-pc-windows-msvc.  I created a repo at https://github.com/ian-p-cooke/pqconnectiontest but there's no CI yet.  However, I was able to duplicate this on my laptop at home which has a similar setup to my work computer.  I realized that Windows doesn't always pop up a dialog with a memory exception, sometimes it just fails and you have to check the exit code.  So the repo includes a 'runme.bat' that can be used to easily see when it fails.
PS C:\Users\ipc\CLionProjects\pqconnectiontest> .\runme
PQisthreadsafe: 1
failure: -1073741819

In my project at work I added a lock around establish which I think is legit so I'm not blocked:
lazy_static! {
    static ref CONNECTION_LOCK : Arc<Mutex<usize>> = Arc::new(Mutex::new(0));
}

pub fn establish_connection(database_url: &str) -> Result<PgConnection, Box<dyn Error>> {
    let _guard = CONNECTION_LOCK.lock();
    PgConnection::establish(&database_url).map_err(Into::into)
}

So, I could replicate the problem when connecting to the same database (home laptop VPN'd in to work) but I couldn't get it to fail when I connected to my local docker instance of postgres 11.  Maybe the local connection is too fast?  It'd be really weird if it was the version of my database.
I'm also going to try using the latest libpq and see if that makes any difference.  Even though I have a workaround this is exactly the kind of problem that I don't expect from Rust so I really want to know the cause.

I think I figured it out.  When building libpq, vcpkg does define ENABLE_THREAD_SAFETY but does not define HAVE_CRYPTO_LOCK even though it's using openssl<1.1.0.  When I define HAVE_CRYPTO_LOCK and rebuild vcpkg's libpq then I can't get my example to fail.  I'll open an issue with vcpkg and see what they say.
So, not really a diesel issue.

I'm glad you were able to figure it out!
On Fri, Sep 6, 2019 at 5:27 AM Ian P. Cooke notifications@github.com
wrote:

I think I figured it out. When building libpq, vcpkg does define
ENABLE_THREAD_SAFETY but does not define HAVE_CRYPTO_LOCK even though it's
using openssl<1.1.0. When I define HAVE_CRYPTO_LOCK and rebuild vcpkg's
libpq then I can't get my example to fail. I'll open an issue with vcpkg
and see what they say.
So, not really a diesel issue.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/diesel-rs/diesel/issues/2162?email_source=notifications&email_token=AALVMK6OZJD3M64EQ2OFUWDQII5C5A5CNFSM4IT4EPNKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6CR5UI#issuecomment-528817873,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AALVMK6IWOP3AAYB4FZPLDDQII5C5ANCNFSM4IT4EPNA
.

--
Thanks,
Sean Griffin

authors: ian-p-cooke sgrif weiznich


text:
Create customers view

finish layout for views related to customers (without image support)

Merged in  #2

repo: digiaonline/resourceplanningtool-ui


text:
Upgrade afj

This PR is equivalent to https://github.com/hyperledger/aries-framework-javascript-ext/pull/222 from the upstream. Most of the comments from there apply equally here. Note I would try to avoid changing too much as the upstream PR is not yet approved and we will likely want to fix this up in line with that.

btw these tests are really flakey and that issue has been raised i nthe upstream

repo: digicatapult/veritable-cloudagent


text:
Improve documentation of date utility packages

Fixes https://github.com/digital-asset/daml-finance/issues/1017

Do you think that a tutorial on this package would be a valuable addition to the docs? I feel that it would benefit the users who do not have a strong financial background, as these concepts are not rocket science but need to be explained one by one

Possibly, I think it depends on who the target user would be for such a tutorial, for example

A user of Daml Finance instruments is probably mostly interested in what these concepts mean on a higher level and what they need to specify for a given trade. There is an overview of this functionality in the [bond instrument documentation] (https://docs.daml.com/daml-finance/instruments/bond.html#:~:text=The day count,initial stub period.)
A developer of Daml Finance instruments probably needs a more in-depth understanding, but such a quant developer cam maybe also be expected to know the concepts beforehand?

In any case, I could link to the relevant part of the bond instrument docs from the Interface.Types.Date doc page for an example on how this is used in practice.
What do you think?

Do you think that a tutorial on this package would be a valuable addition to the docs? I feel that it would benefit the users who do not have a strong financial background, as these concepts are not rocket science but need to be explained one by one

Possibly, I think it depends on who the target user would be for such a tutorial, for example

A user of Daml Finance instruments is probably mostly interested in what these concepts mean on a higher level and what they need to specify for a given trade. There is an overview of this functionality in the [bond instrument documentation] (https://docs.daml.com/daml-finance/instruments/bond.html#:~:text=The day count,initial stub period.)
A developer of Daml Finance instruments probably needs a more in-depth understanding, but such a quant developer can maybe also be expected to know the concepts beforehand?

In any case, I could link to the relevant part of the bond instrument docs from the Interface.Types.Date doc page for an example on how this is used in practice.
What do you think?

Linking to some parts of the bond documentation sounds good.
On your point number 2, I feel that most of our users have a developer background rather than a quant dev background (such as ours). That's why I'm thinking that a tutorial / primer on dates, schedules, calendars, ... would be quite empowering for them. @frankPreiwussDA any thought?

Do you think that a tutorial on this package would be a valuable addition to the docs? I feel that it would benefit the users who do not have a strong financial background, as these concepts are not rocket science but need to be explained one by one

Possibly, I think it depends on who the target user would be for such a tutorial, for example

A user of Daml Finance instruments is probably mostly interested in what these concepts mean on a higher level and what they need to specify for a given trade. There is an overview of this functionality in the [bond instrument documentation] (https://docs.daml.com/daml-finance/instruments/bond.html#:~:text=The day count,initial stub period.)
A developer of Daml Finance instruments probably needs a more in-depth understanding, but such a quant developer can maybe also be expected to know the concepts beforehand?

In any case, I could link to the relevant part of the bond instrument docs from the Interface.Types.Date doc page for an example on how this is used in practice.
What do you think?

Linking to some parts of the bond documentation sounds good.
On your point number 2, I feel that most of our users have a developer background rather than a quant dev background (such as ours). That's why I'm thinking that a tutorial / primer on dates, schedules, calendars, ... would be quite empowering for them. @frankPreiwussDA any thought?

I opened an issue for it and added it to the UX roadmap, so we can discuss it in the next UX session.
https://github.com/digital-asset/daml-finance/issues/1044

Thanks!

authors: markus-da matteolimberto-da


text:
4 mutable and immutable learned

closes #4

✅ Looks good

Thank you for the feedback.


text:
Paginator adds an extra '/' to the URL which messes up AWS S3.

I fixed my problem and created a pull request which you may want to take a look at. I couldn't find a way to strip off the extra '/' from the pre/next link so I removed the trailing slash from the baseURL and updated the source to take account. I don't know if this is the best way of doing this, but it does fix my problem. Would welcome any feedback or a better way.
Thanks for a very nice theme.
Patrick

Hello @patrickn,
thank your for reporting this issue and for this fix. However, removing the / from the end of the of the base url doesn't really solve the problem because it should still work. I rather have to change the way how I link assets and pages. This can be done by using Hugo's templates functions constructs hopefully working urls under all circumstances.
Therefore, I'll close this issue and approach this problem as described.

authors: digitalcraftsman patrickn

repo: digitalcraftsman/hugo-icarus-theme


text:
i have a error when i use ethereum-php-eventlistener

PHP Fatal error: Uncaught Exception: Graze\GuzzleHttp\JsonRpc\Exception\ClientException: Client RPC error response [uri] / [method] eth_getBlockByNumber [error code] -32602 [error message] invalid argument 0: hex number with leading zero digits
this is my temporary solution that change the DataType/EthBlockParam.php. Can you fix this problem？
public function hexVal()
{
if ($this->isTag()) {
return $this->value;
} else {
$val = intval($this->value->toString());
$val = ($val === 0) ? $val : $this->value->toHex(false);
$pattern = "/([0]*)([0-9a-f]+)/i";
$replacement = "$2";
$val = preg_replace($pattern,$replacement,$val);
// Unpaded positive Hex value.
return $this->ensureHexPrefix($val);
}
}

+++ digitaldonkey/ethereum-php/src/DataType/EthBlockParam.php 2022-03-07 21:34:03.341242711 +0800
@@ -105,6 +105,7 @@
} else {
$val = intval($this->value->toString());
$val = ($val === 0) ? $val : $this->value->toHex(false);

      $val = ltrim($val, '0');

       // Unpaded positive Hex value.
       return $this->ensureHexPrefix($val);

same error here

repo: digitaldonkey/ethereum-php


text:
Radar water detection and extent for Lake chad

Proposed changes
Add radar water detection and extent use case for the Lake Chad area. The 4 notebooks show the comparison between the Sentinel 1 Water Index (SWI) and the Sentinel 2 MNDWI, WOfs Feature Layer and WOfS Annual Summaries.
Closes issues (optional)

Closes Issue #000
Closes Issue #000

Checklist (replace [ ] with [x] to check off)

[ ] Remove any unused Python packages from Load packages
[ ] Remove any unused/empty code cells
[ ] Remove any guidance cells (e.g. General advice)
[ ] Ensure that all code cells follow the PEP8 standard for code. The jupyterlab_code_formatter tool can be used to format code cells to a consistent style: select each code cell, then click Edit and then one of the Apply X Formatter options (YAPF or Black are recommended).
[ ] Include relevant tags in the final notebook cell and re-use tags if possible
[ ] Clear all outputs, run notebook from start to finish, and save the notebook in the state where all cells have been sequentially evaluated

I've left the default area of the notebooks to be Lake Sulunga in Tanzania. I tried running the notebook using the Lake Chad shapefile with the 4XL sandbox and got the error:


text:
TypeError

Trying to run the colab given in the readme file. Getting this

any idea to resolve?

I meet the same question bro

authors: Shujiaer anubhavsinghgtm


text:
Erro de Ortografia

Na parte final da carreira de Front End, a palavra disponível está escrito errado.

Vlw demais @alinerx e @jeffersonsimaogoncalves 🥰

authors: alinerx falvojr

repo: digitalinnovationone/roadmaps


text:
Adding custom fields to device roles

Environment

Python version:  3.4
NetBox version:  2.4.4

Proposed Functionality
Allowing the addition of custom fields to device role objects.
Use Case
We'd like to provision different devices automatically (OS, configuration) according to their role in NetBox, through external automated systems that can hook into the API and web hooks. In order to to do that we need to store the ID mapping from roles to those external systems' databases, so they can be looked up from the single source of truth by the tooling we use. :)
This seems very synonymous with the example named in the documentation, which is also an external system ID associated with the entity. As such it seems like a natural fit for NetBox integration.
Database Changes
N/A
External Dependencies
N/A

Ah, apologies! The issue text has been updated.

Per the FAQ we are not adding custom fields to any additional models at this time.

authors: jeremystretch mxxxc

repo: digitalocean/netbox


text:
Do not enable HSTS by default

Feature request
Currently, HSTS is enabled by default with a very long period, subdomains included, and preload enabled. This has some problems:

A user may not know what HSTS means, and accidentally ruined all his non-HTTPS subdomains by using the generated config.
The max-age is too long. For anyone who want to try HSTS, he should start by using short periods to test.
If a user added two sites: "example.com" and "foo.example.com", and explicitly disabled HSTS for "foo.example.com", it still gets HSTS by default because "example.com" enabled HSTS for all subdomains by default. This behavior is just wrong.
Preloading should be opt-in. If you maintain a project that provides HTTPS configuration advice or provides an option to enable HSTS, do not include the preload directive by default.

So, my suggestion is to disable HSTS by default (or at least warn people about includeSubDomains). User should only enable HSTS if they know what they are doing.

HSTS is a huge step in the right direction for a more secure web -- most sites now use HTTPS by default, some TLDs even have HSTS forced (.dev for example), so I think it is right for a tool designed to provide the best practices to default to having HSTS enabled.
The max-age on HSTS is recommended to generally be long, somewhere in the range of 120 days to a year. nginxconfig is designed to apply the best practices to the generated nginx config files, so we use 1 year for the max-age on the HSTS header.
However, I do agree about the dangers of not correctly explaining the use of includeSubDomains as well enabling preload by default (these decisions predate me working on the project) -- I think we can address the includeSubDomains issue by adding some explainer text next to that setting for those that may need HTTP subdomains, and we can make preload disabled by default.

How does this look to you?

I still worry about someone may accidentally enabled HSTS for non-HTTPS subdomains :( But I agree that enabling includeSubDomains is a best practice, thus should be default for nginxconfig. I think this solution (more text & disable preload) is acceptable.

A small problem with "Split column mode":

Oops, will get some text wrapping added

Should be fixed as soon as the latest push deploys:


text:
Feature/pt br translation

Type of Change

Add Portuguese Brazilian translation

What issue does this relate to?

N/A

👋 Tyvm for the PR, @fcpimenta!
Could you rebase this against lastest master when you have a second -- we just merged a few new i18n strings and a tool to help check i18n packs :)

👋 Tyvm for the PR, @fcpimenta!
Could you rebase this against lastest master when you have a second? -- we just merged a few new i18n strings and a tool to help check i18n packs :)

Hi Matt! I've already rebased my fork. Could you please check if all things are ok?

It looks like this branch specifically still needs to be rebased against your fork's master branch

Branch rebased.

I think the issues were corrected.

Hey, @fcpimenta - Thanks a ton for this sweet PR! 😄
Would you please shoot me an email when you get a chance?
mcowley at digitalocean dot com 🎉