text:
Fix prefer web first assertion rule

Fixes the following issue:
#286
I have also added new tests to verify this scenario.

@mskelton I see you have made most of the changes to this rule.
Do you mind taking a looking whenever you have time? Thanks!

Please fix the formatting errors with Prettier before submitting. I'll take a look once the formatting and linting is fixed.

@mskelton I have formatted the files with the command pnpm fmt. Although I did notice that prettier was also formatting two more files unrelated to my changes and I couldn't make prettier run without them. I figured it wouldn't harm anyone having those properly formatted as well in this PR so just kept them in there. Looks like the checks are passing now but please let me know if I missed something and thanks for taking a look.

Thanks!


text:
🛑 eBioDiv Matching Service is down

In 398891b, eBioDiv Matching Service (https://prod.ebiodiv.org/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: eBioDiv Matching Service is back up in 75c2bb2 after 19 minutes.

source: gharchive/issue

repo: plazi/monitoring

license: MIT

license_type: permissive

license_source: github-api


text:
We'd like to implement PCA decomposition plot

Principal component analysis (PCA) to decompose high dimensional data into two or three dimensions so that each instance can be plotted in a scatter plot.
As part of this issue, we'll need to research this plot and implement it as part of the package.
We should test it and add it to the CI, in addition to documenting the code and how to use it via examples.
Below is how it should look like.

repo: ploomber/sklearn-evaluation


text:
Stop building the app when failure

Fixes https://github.com/plotly/streambed/issues/14719
This PR changes the options used for the set bash builtin so that the deployment fails when there is a failure instead of continuing to build the app.
This is how I tested this:

Using the currently shipped conda buildpack, deploy an app with the following .condarc file, which refers to a non-existing conda channel.

channels:
  - https://my.anaconda.repo:8080/conda/

Notice that even when it fails to fetch the packages from the non-existing conda channel, it continues to build the app and fails at the end of the build because the app can't be started with the following error:

File "/app/app.py", line 1, in <module>
           import dash
       ModuleNotFoundError: No module named 'dash'
       [2021-01-14 21:13:51 +0000] [204] [INFO] Worker exiting (pid: 204)
       [2021-01-14 21:13:51 +0000] [13] [INFO] Shutting down: Master
       [2021-01-14 21:13:51 +0000] [13] [INFO] Reason: Worker failed to boot.
=====> end conda-app web container output
To hamza400.plotly.host:conda-app
 ! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'dokku@hamza400.plotly.host:conda-app'

Add a .buildpacks file to the app directory root and point it to this buildpack repo's branch that I pushed my change to and deploy again.

Notice that now it fails and exits the deployment as soon as it doesn't find the conda channel:

remote: An HTTP error occurred when trying to retrieve this URL.
remote: HTTP errors are often intermittent, and a simple retry will get you on your way.
remote: ConnectionError(MaxRetryError("HTTPSConnectionPool(host='my.anaconda.repo', port=8080): Max retries exceeded with url: /conda/linux-64/repodata.json (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f5db4a81898>: Failed to establish a new connection: [Errno -2] Name or service not known'))"))
remote:
remote:
To hamza400.plotly.host:conda-app
 ! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'dokku@hamza400.plotly.host:conda-app'

@tarzzz, could you please review?

Thanks @tarzzz I thought of doing that as well after I submitted my PR and tested it. It works too, I'll add it to my test plan above.

Thanks @tarzzz I thought of doing that as well after I submitted my PR and tested it. It works too, I'll add it to my test plan above.

source: gharchive/pull-request

repo: plotly/conda-buildpack


text:
Try customTraces in Dev

resolves #500

cc @nicolaskruchten

This should work now when configured and when not configured.
This just makes me think of the fact that we don't have anything testing the traces modal on percy as of now, as the tests were green..

OK so can we split this into two commits: one that's intended to be merged, and one that's just demo of how to use it? :)

💃 for the first commit once default values used

authors: VeraZab nicolaskruchten

repo: plotly/react-chart-editor


text:
🛑 Dick Pluim.com is down

In 0fb85aa, Dick Pluim.com (https://dickpluim.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Dick Pluim.com is back up in 427371c after 1 hour, 4 minutes.


text:
🛑 KCG is down

In 169340d, KCG (https://kunstrijclubgroningen.nl) was down:

HTTP code: 0
Response time: 0 ms

Resolved: KCG is back up in 65cb01e after 48 minutes.


text:
checkbox: add partial selection state

Enhancement Request
Desired behavior
Via content tools team... request for partial checkbox support
Today's behavior
only selected / deselected
The Value Add
Common UI for table actions

Status: closing as revisit

authors: dborodyansky jaketrent

repo: pluralsight/design-system


text:
Not an issue, instead a suggestion

Culinaire Integration/Collaboration pack would be an interesting addon or maybe a main mod update 👀
I'd love to see Pluto's kettle model there or maybe a proper Coffee Maker thingy which name I always forget
Not demanding it, no way I'm swooping this low, but they seem to be quite a good mod team and their tea is a lovely addition.
Besides, you collaborating will also solve the Coffee-Tea conflict in the peacefull-est way

I am actually currently working on an actual Coffee Machine, and a better, more customizable way to make coffee with NBT Instead of Seperate Items. As of Tea, I have a tea mod that I am working on Integrating into this one, I just have to update it first. Thanks for the suggestion, and I am also working on a mod that adds a bunch of new foods, which of course will interact with this mod if you are using both.


text:
Missing ENV Error

Hi there, getting an error when instantiating a new MQTT Client. To reproduce, I build k6 with...
FROM grafana/xk6

RUN xk6 build --with github.com/pmalhaire/xk6-mqtt@latest

Then with that k6 executable I can run the following testing code
import { Client } from 'k6/x/mqtt';

export default function () {
  try {
    const mqttPublisher = new Client(
      ['whatever:80'],
      '',
      '',
      false,
      'k6_publisher',
      2000,
    );

    mqttPublisher.connect();
    console.log(`Connected successfully`);
  }
  catch (error: any) {
    console.error(`Error: ${error.message}`);
  }
}

I get the following error GoError: missing env. I've tracked down the error to https://github.com/pmalhaire/xk6-mqtt/blob/343795c84676942243d493b304420204cfc5a6d9/stats.go#L31 which invokes vu.InitEnv which I admit, I don't really understand. All of this is happening either in setup or in a normal vu execution path. Anyway, any help would be very appreciated.

I had the same issue. If i remember it correctly, you can call "new Client" only in the init phase. See https://grafana.com/docs/k6/latest/using-k6/test-lifecycle/

Yes the client are only created in the init phase see here
https://github.com/pmalhaire/xk6-mqtt/blob/main/examples/test.js#L45

authors: Spittal ezeeb pmalhaire


text:
Update spring-boot-starter-camunda to 8.5.10

About this PR
📦 Updates io.camunda.spring:spring-boot-starter-camunda from 8.5.9 to 8.5.10
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.camunda.spring", artifactId = "spring-boot-starter-camunda" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "io.camunda.spring", artifactId = "spring-boot-starter-camunda" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #112.


text:
⚠ Slack has degraded performance

In a878826, Slack (https://status.slack.com/api/v2.0.0/current) experienced degraded performance:

HTTP code: 200
Response time: 208 ms

Resolved: Slack performance has improved in ca7fde6.

repo: pmmmwh/upptime


text:
Character can't jump

My character can't jump. This is my Ground code. Please help!
import { Plane } from "@react-three/drei";
import { RapierRigidBody, RigidBody } from "@react-three/rapier";
import { useRef } from "react";
const Ground = () => {
const ref = useRef(null);
return (

<Plane
position={[0, 0, 0]}
args={[1000, 1000]}
rotation={[-Math.PI / 2, 0, 0]}
>

);
};

There is not enough information provided here. Perhaps you may want to refer to the codesandbox for detailed setups:
https://codesandbox.io/p/sandbox/ecctrl-w-o-animations-3k3zxt?file=%2Fsrc%2FApp.js

Thank you for your response. I think the problem because the capsule stick on the floor. But I don't know how to fix it

Seems like Ecctrl is not been used. I'll need more information about the context and setup to better understand the issue.

I found the problem is that actualSlopeAngle always more than slopeMaxAngle therefore the capsule can't jump. But all options are default, but I don't change anything

Again, I need more information to be able to help 😅

My problem because I put the Floor component before the Ecctr component. When I reverse it, it works fine. Thank you

My problem because I put the Floor component before the Ecctr component. When I reverse it, it works fine. Thank you

Thank you, this solved it for me.

repo: pmndrs/ecctrl


text:
disabled demos (don't build)

Some apps/* has been temporarily disabled "bbuild2" before of build errors
https://github.com/search?q=repo%3Apmndrs%2Fexamples bbuild2&type=code

superseded by https://github.com/pmndrs/examples/issues/38

repo: pmndrs/examples


text:
Upgrade to latest sloc

Also upgrade devDependecies to current versions
Keep gulp on 3.x for now
Also upgrade dependencies to latest gulp-util, lodash, mkdirp
Also add jshint to devDependencies, for compatibility with modern npm
Also add package-lock.json from npm 6.4.1 to prevent accidental transitive dependency changes

@rjatkins is this still needed? Would you want to be a collaborator on this repo?

authors: pnarielwala rjatkins

license: mit

license_source: bigquery


text:
Hightlight rows current weekday

Q
A

Bug fix?
no

New sample?
yes

Related issues?
no

What's in this Pull Request?
This is a new sample that demonstrates how to apply formatting to list columns based on the current day of the week.
So the same view is formatted differently on a Sunday than on a Wednesday.

Hi @365knoten . Thanks for the great sample!!
I tested the sample at my place and the day of the week was different depending on the current time, even on the same day.

This is probably an effect of my computer being set to Japan time(UTC+09:00).
I am sorry, but could you please confirm this phenomenon?

Thank you for the update @365knoten 🙏✨
I'll test it again on my end!

Thank you for testing @tecchan1107 .
I did not take different timezones into account, but tested the new formula with many different timezones yesterday.
Kind Regards,
Sven

Hi @365knoten ! I tested it and it successfully highlighted the today's day of the week row!
Thanks for the fix, and for the great, great sample😍😍😍✨
I have done the merge, please check the following link. (I made some minor adjustments when merging.)
https://github.com/pnp/List-Formatting/tree/master/view-samples/highlight-rows-current-weekday
Please let us know if you have any questions.
Once again, thanks for the awesome sample! I learned a lot about the math of the days of the week🤩!

If you are interested, please register for the recognition program at the following link. You will receive a digital badge when you register!
http://aka.ms/m365pnp-recognition

repo: pnp/List-Formatting


text:
Updates dependencies

Updates dependencies

Thank you. Manually merged

authors: plamber waldekmastykarz


text:
Bug-fix onenote notebook list: missing telemetry / validator checks

Closes #4315
Also made some minor enhancements to the code to make it match more with our async/await approach.

Great job, we'll try to review it ASAP!

Sorry for the wait @MathijsVerbeeck.
Looks like the PR has some conflicts, could you take a look at them.


text:
Updates planner roster docs response. Closes #5910

Updates planner roster docs response by updating the roster ID as GUID. Closes #5910

Thank you @nanddeepn! We'll try to have a look at it ASAP!

Merged manually, thank you for this fix!

authors: milanholemans nanddeepn


text:
Add PreviousNode parameter to Add-PnPNavigationNode

Type

[x] Bug Fix
[x] New Feature
[ ] Sample

What is in this Pull Request ?
Added parameter PreviousNode to specify the navigation node after which the new navigation node will appear in the navigation node collection, which allows to add it to the correct position in the navigation instead of adding and then reordering afterwards.
Changed the type of the Parent parameter to NavigationPipeBind to allow a object of type NavigationNode as input in addition to just the ID.
Fixed the issue that target audiences weren't set when creating a node as a child of a parent node.

Thanks @reusto!

authors: KoenZomers reusto

repo: pnp/powershell


text:
sessionStorage exceeds max-size when browsing large termsets

Category
[ ] Enhancement
[x] Bug
[ ] Question
Version
Please specify what version of the library you are using: [1.13.2]
We tried the latest version also, but gives the same error.
Expected / Desired Behavior / Question
Browsable termsets with more than 1500 terms
Observed Behavior
When opening multiple large termsets the spinner is stuck and won't load the termset tree
Steps to Reproduce
Open a couple of taxonomy pickers with more than 1000 terms. After a few the spinner gets stuck and in the console this error occurs:
Uncaught (in promise) DOMException: Failed to execute 'setItem' on 'Storage': Setting the value of '[guid]' exceeded the quota.
Workaround/Question
After selecting a term we're removing the termset-item from sessionStorage in order to not exceed the quota on the next load of a different termset, but it feels like a unnecessary workaround. Any ideas how this could be fixed without this workaround?
Thanks and regards,
Johan

Hi @JohanFiske!
Thank you for reporting the issue!
@gautamdsheth has fixed it in #745 and it'll be available in the next release.
In a meantime you can test it in beta version.

authors: AJIXuMuK JohanFiske

repo: pnp/sp-dev-fx-controls-react


text:
FilePicker Issue - Site Tab - Many Document Libraries No Scrolling

Q
A

Bug fix?
[ X]

New feature?
[ ]

New sample?
[ ]

Related issues?
fixes #X, partially #Y, mentioned in #Z

What's in this Pull Request?
'FilePicker' control, 'Sites' tab - when many document libraries exists in the site, the control would not scroll if they didn't fit in the layout - <ScrollablePane /> added
Same issue as in the property controls (https://github.com/pnp/sp-dev-fx-property-controls/issues/525)
@joelfmrodrigues  -> As agreed

@krainer Many thanks!!! Merged

authors: joelfmrodrigues krainer


text:
Error! Unable to verify source code on Kovan Etherscan

If you are reporting a problem with Token Wizard, please include the following information:
Which network did you use? (Mainnet, Kovan, Rinkeby, etc.)
Your answer
Kovan
If you were able to create it, what is the URL of your crowdsale?
Your answer
https://kovan.etherscan.io/address/0x7A62bE1157b2aCcc2Eb62598c78EB41642b21219
Do you have screenshots showing the problem?
Your answer

Do you see errors in the dev console? If yes, please include a screenshot
To open the dev console in Google Chrome, press F12, or go to View -> Developer -> Developer Tools, and open the Console tab
If you see errors, please right click on them and "Save as..". Zip saved file and attach it to the Issue.
Your answer

Hi,
I deployed a token with three Tiers to the kovan network, i was able to verify the  'SafeMathLibExt; contract on Kovan Etherscan, but every other contracts verification flagged an error
Error! Unable to verify source code
Exception #1 Occured: ERROR|The Contract solidity compilation has exceeded the maximum timeout/memory limit that we can safely process. Automated source code verification is unavailable for this source code.
And i also noticed that the ' CrowdsaleTokenExt.txt' does not have an Abi-encoded constructor arguments.
see the code below.
Token name: GEMSTRA

Token ticker: ASTRA

Token decimals: 18

Multisig wallet address: 0x9781fce5d8DB90409B1Ff4D955aCeD0e30ab0629

*****************************

Crowdsale rate: 1500

Crowdsale start time: 2018-03-20T03:00 (GMT + 1)

Crowdsale end time: 2018-03-23T00:00 (GMT + 1)

Compiler Version: 0.4.11

Is optimization enabled?: true

*****************************

Token contract name: CrowdsaleTokenExt

Token contract address: 0x6F19693600778A7256eaAB9a668B37C182365F09

*****************************

****Token contract ABI:****

[{"constant":false,"inputs":[{"name":"addr","type":"address"},{"name":"state","type":"bool"}],"name":"setTransferAgent","outputs":[],"payable":false,"type":"function"},{"constant":true,"inputs":[],"name":"mintingFinished","outputs":[{"name":"","type":"bool"}],"payable":false,"type":"function"},{"constant":true,"inputs":[],"name":"name","outputs":[{"name":"","type":"string"}],"payable":false,"type":"function"},{"constant":false,"inputs":[{"name":"_spender","type":"address"},{"name":"_value","type":"uint256"}],"name":"approve","outputs":[{"name":"success","type":"bool"}],"payable":false,"type":"function"},{"constant":true,"inputs":[],"name":"totalSupply","outputs":[{"name":"","type":"uint256"}],"payable":false,"type":"function"},{"constant":false,"inputs":[{"name":"_from","type":"address"},{"name":"_to","type":"address"},{"name":"_value","type":"uint256"}],"name":"transferFrom","outputs":[{"name":"success","type":"bool"}],"payable":false,"type":"function"},{"constant":false,"inputs":[{"name":"addr","type":"address"}],"name":"setReleaseAgent","outputs":[],"payable":false,"type":"function"},{"constant":true,"inputs":[],"name":"decimals","outputs":[{"name":"","type":"uint256"}],"payable":false,"type":"function"},{"constant":true,"inputs":[{"name":"addr","type":"address"}],"name":"getReservedPercentageUnit","outputs":[{"name":"inPercentageUnit","type":"uint256"}],"payable":false,"type":"function"},{"constant":true,"inputs":[],"name":"minCap","outputs":[{"name":"","type":"uint256"}],"payable":false,"type":"function"},{"constant":false,"inputs":[{"name":"receiver","type":"address"},{"name":"amount","type":"uint256"}],"name":"mint","outputs":[],"payable":false,"type":"function"},{"constant":true,"inputs":[{"name":"","type":"address"}],"name":"mintAgents","outputs":[{"name":"","type":"bool"}],"payable":false,"type":"function"},{"constant":false,"inputs":[{"name":"addr","type":"address"},{"name":"state","type":"bool"}],"name":"setMintAgent","outputs":[],"payable":false,"type":"function"},{"constant":false,"inputs":[{"name":"value","type":"uint256"}],"name":"upgrade","outputs":[],"payable":false,"type":"function"},{"constant":true,"inputs":[{"name":"addr","type":"address"}],"name":"getReservedPercentageDecimals","outputs":[{"name":"inPercentageDecimals","type":"uint256"}],"payable":false,"type":"function"},{"constant":false,"inputs":[{"name":"_name","type":"string"},{"name":"_symbol","type":"string"}],"name":"setTokenInformation","outputs":[],"payable":false,"type":"function"},{"constant":true,"inputs":[{"name":"","type":"address"}],"name":"reservedTokensList","outputs":[{"name":"inTokens","type":"uint256"},{"name":"inPercentageUnit","type":"uint256"},{"name":"inPercentageDecimals","type":"uint256"},{"name":"isReserved","type":"bool"},{"name":"isDistributed","type":"bool"}],"payable":false,"type":"function"},{"constant":true,"inputs":[],"name":"upgradeAgent","outputs":[{"name":"","type":"address"}],"payable":false,"type":"function"},{"constant":false,"inputs":[],"name":"releaseTokenTransfer","outputs":[],"payable":false,"type":"function"},{"constant":true,"inputs":[],"name":"upgradeMaster","outputs":[{"name":"","type":"address"}],"payable":false,"type":"function"},{"constant":true,"inputs":[{"name":"addr","type":"address"}],"name":"getReservedTokens","outputs":[{"name":"inTokens","type":"uint256"}],"payable":false,"type":"function"},{"constant":false,"inputs":[{"name":"addr","type":"address"}],"name":"finalizeReservedAddress","outputs":[],"payable":false,"type":"function"},{"constant":true,"inputs":[{"name":"_owner","type":"address"}],"name":"balanceOf","outputs":[{"name":"balance","type":"uint256"}],"payable":false,"type":"function"},{"constant":true,"inputs":[{"name":"","type":"uint256"}],"name":"reservedTokensDestinations","outputs":[{"name":"","type":"address"}],"payable":false,"type":"function"},{"constant":true,"inputs":[],"name":"getUpgradeState","outputs":[{"name":"","type":"uint8"}],"payable":false,"type":"function"},{"constant":true,"inputs":[{"name":"","type":"address"}],"name":"transferAgents","outputs":[{"name":"","type":"bool"}],"payable":false,"type":"function"},{"constant":true,"inputs":[],"name":"owner","outputs":[{"name":"","type":"address"}],"payable":false,"type":"function"},{"constant":true,"inputs":[],"name":"symbol","outputs":[{"name":"","type":"string"}],"payable":false,"type":"function"},{"constant":true,"inputs":[{"name":"addr","type":"address"}],"name":"isAddressReserved","outputs":[{"name":"isReserved","type":"bool"}],"payable":false,"type":"function"},{"constant":true,"inputs":[],"name":"released","outputs":[{"name":"","type":"bool"}],"payable":false,"type":"function"},{"constant":true,"inputs":[],"name":"canUpgrade","outputs":[{"name":"","type":"bool"}],"payable":false,"type":"function"},{"constant":false,"inputs":[{"name":"_to","type":"address"},{"name":"_value","type":"uint256"}],"name":"transfer","outputs":[{"name":"success","type":"bool"}],"payable":false,"type":"function"},{"constant":true,"inputs":[{"name":"addr","type":"address"}],"name":"areTokensDistributedForAddress","outputs":[{"name":"isDistributed","type":"bool"}],"payable":false,"type":"function"},{"constant":true,"inputs":[],"name":"reservedTokensDestinationsLen","outputs":[{"name":"","type":"uint256"}],"payable":false,"type":"function"},{"constant":true,"inputs":[],"name":"totalUpgraded","outputs":[{"name":"","type":"uint256"}],"payable":false,"type":"function"},{"constant":true,"inputs":[],"name":"releaseAgent","outputs":[{"name":"","type":"address"}],"payable":false,"type":"function"},{"constant":false,"inputs":[{"name":"agent","type":"address"}],"name":"setUpgradeAgent","outputs":[],"payable":false,"type":"function"},{"constant":true,"inputs":[{"name":"_owner","type":"address"},{"name":"_spender","type":"address"}],"name":"allowance","outputs":[{"name":"remaining","type":"uint256"}],"payable":false,"type":"function"},{"constant":false,"inputs":[{"name":"_token","type":"address"}],"name":"claimTokens","outputs":[],"payable":false,"type":"function"},{"constant":true,"inputs":[],"name":"isToken","outputs":[{"name":"weAre","type":"bool"}],"payable":false,"type":"function"},{"constant":false,"inputs":[{"name":"addrs","type":"address[]"},{"name":"inTokens","type":"uint256[]"},{"name":"inPercentageUnit","type":"uint256[]"},{"name":"inPercentageDecimals","type":"uint256[]"}],"name":"setReservedTokensListMultiple","outputs":[],"payable":false,"type":"function"},{"constant":false,"inputs":[{"name":"newOwner","type":"address"}],"name":"transferOwnership","outputs":[],"payable":false,"type":"function"},{"constant":false,"inputs":[{"name":"master","type":"address"}],"name":"setUpgradeMaster","outputs":[],"payable":false,"type":"function"},{"inputs":[{"name":"_name","type":"string"},{"name":"_symbol","type":"string"},{"name":"_initialSupply","type":"uint256"},{"name":"_decimals","type":"uint256"},{"name":"_mintable","type":"bool"},{"name":"_globalMinCap","type":"uint256"}],"payable":false,"type":"constructor"},{"anonymous":false,"inputs":[{"indexed":false,"name":"newName","type":"string"},{"indexed":false,"name":"newSymbol","type":"string"}],"name":"UpdatedTokenInformation","type":"event"},{"anonymous":false,"inputs":[{"indexed":true,"name":"_token","type":"address"},{"indexed":true,"name":"_controller","type":"address"},{"indexed":false,"name":"_amount","type":"uint256"}],"name":"ClaimedTokens","type":"event"},{"anonymous":false,"inputs":[{"indexed":true,"name":"_from","type":"address"},{"indexed":true,"name":"_to","type":"address"},{"indexed":false,"name":"_value","type":"uint256"}],"name":"Upgrade","type":"event"},{"anonymous":false,"inputs":[{"indexed":false,"name":"agent","type":"address"}],"name":"UpgradeAgentSet","type":"event"},{"anonymous":false,"inputs":[{"indexed":false,"name":"addr","type":"address"},{"indexed":false,"name":"state","type":"bool"}],"name":"MintingAgentChanged","type":"event"},{"anonymous":false,"inputs":[{"indexed":true,"name":"previousOwner","type":"address"},{"indexed":true,"name":"newOwner","type":"address"}],"name":"OwnershipTransferred","type":"event"},{"anonymous":false,"inputs":[{"indexed":false,"name":"receiver","type":"address"},{"indexed":false,"name":"amount","type":"uint256"}],"name":"Minted","type":"event"},{"anonymous":false,"inputs":[{"indexed":true,"name":"owner","type":"address"},{"indexed":true,"name":"spender","type":"address"},{"indexed":false,"name":"value","type":"uint256"}],"name":"Approval","type":"event"},{"anonymous":false,"inputs":[{"indexed":true,"name":"from","type":"address"},{"indexed":true,"name":"to","type":"address"},{"indexed":false,"name":"value","type":"uint256"}],"name":"Transfer","type":"event"}]

Duplicate of https://github.com/poanetwork/token-wizard/issues/679

Hello vbaranov ,
Any answer to this issue? Today I'm facing exactly the same problem. Kindly help.

The problem is solved: you don't need to put a colon before the library name.

authors: drdonjuan jacobabiola vbaranov

repo: poanetwork/token-wizard


text:
As a User, I want an indication as to whether a previous stream was a default

Along with any other signalling around this issue (can it be deleted? etc)
Fill in more detail to this issue as we learn more.

@ggeisler we're going to start keeping track of streams that were formerly set as the default. We'd like to indicate this in the UI in the list of streams and on the stream's show page as well. We will also know the date range that the stream was the default and it might be helpful to display that information. It is possible that a stream could be set to the default for more than one period of time.

Closing this in favor of more actionable tickets #769 and #771.

authors: Hurlyburly2 corylown ggeisler


text:
union and minus are sets operations

That means
(1; 1; 1) UNION (1 ; 1) = (1; 1)
We must change that

You must change that

authors: gliboc poechsel

repo: poechsel/MiniSQL


text:
lampe-gtk: light names are not shown

not enough information

duplicate of #32

#32 was closed

repo: poinck/lampe


text:
ViewController's observe is triggered when state is set to nil

Description
When the parent Reducer declares the ViewController's State with @Presents, the observe in the ViewController is incorrectly triggered once when the parent Reducer sets the ViewController's State to nil.
Checklist

[ ] I have determined whether this bug is also reproducible in a vanilla SwiftUI project.
[X] If possible, I've reproduced the issue using the main branch of this package.
[X] This issue hasn't been addressed in an existing GitHub issue or discussion.

Expected behavior
I expected that when the parent Reducer sets the child's ViewController's State to nil, the observe in the ViewController would not be triggered at all.
The observe should not execute any logic when the state is set to nil.
Actual behavior
When the parent Reducer declares the ViewController's State with @Presents, the observe in the ViewController is incorrectly triggered once when the parent Reducer sets the ViewController's State to nil.
Steps to reproduce

Present the UIViewController modally (tap the "Present ChildView" button)
Parent sets the ViewController's state to nil (tap the "Cancel" button)

Minimal code to reproduce the issue:
import SwiftUI
import ComposableArchitecture

@ViewAction(for: SampleFeature.self)
struct SampleFeatureView: View {
    @Environment(\.locale) var locale

    @Bindable var store: StoreOf<SampleFeature>

    var body: some View {
        VStack {
            Button("Present ChildView") {
                send(.onClickPresentModal)
            }
        }
        .sheet(
            item: $store.scope(
                state: \.child,
                action: \.child
            )
        ) { store in
            NavigationStack {
                ChildFeatureView(store: store)
                    .toolbar {
                        ToolbarItem(placement: .cancellationAction) {
                            Button("Cancel") {
                                send(.onClickCancel)
                            }
                        }
                    }
            }
        }
    }
}

@Reducer
struct SampleFeature {

    @ObservableState
    struct State {
        @Presents var child: ChildFeature.State?

        init(child: ChildFeature.State? = nil) {
            self.child = child
        }
    }

    enum Action: ViewAction {
        enum ViewAction {
            case onClickPresentModal
            case onClickCancel
        }

        case view(ViewAction)

        case child(PresentationAction<ChildFeature.Action>)
    }

    var body: some Reducer<State, Action> {
        Reduce<State, Action> { state, action in
            switch action {
            case .view(let action):
                switch action {
                case .onClickPresentModal:
                    state.child = .init()
                    return .none

                case .onClickCancel:
                    // If it is set to nil from parent,
                    // observe in ViewController is working after being set to nil.
                    state.child = nil
                    return .none
                }

            default:
                return .none
            }
        }
        .ifLet(\.$child, action: \.child) {
            ChildFeature()
        }
    }
}

struct ChildFeatureView: UIViewControllerRepresentable {
    typealias UIViewControllerType = UIViewController

    private let store: StoreOf<ChildFeature>

    init(store: StoreOf<ChildFeature>) {
        self.store = store
    }

    func makeUIViewController(context: Context) -> UIViewControllerType {
        ViewController(store: store)
    }

    func updateUIViewController(_ uiViewController: UIViewControllerType, context: Context) {
    }

    @ViewAction(for: ChildFeature.self)
    public class ViewController: UIViewController {
        @UIBindable public var store: StoreOf<ChildFeature>

        public init(store: StoreOf<ChildFeature>) {
            self.store = store
            super.init(nibName: nil, bundle: nil)
        }

        required init?(coder: NSCoder) {
            fatalError("init(coder:) has not been implemented")
        }

        public override func viewDidLoad() {
            super.viewDidLoad()

            observe { [weak self] in
                guard let self else {
                    return
                }
                // This line is also executed when the parent is set to nil
                print("observe", self.store.count, #line)
            }
        }
    }
}

@Reducer
public struct ChildFeature {

    @ObservableState
    public struct State: Sendable {
        var count: Int

        init(count: Int = 0) {
            self.count = count
        }
    }

    public enum Action: ViewAction {
        public enum ViewAction {
        }

        case view(ViewAction)
    }

    public var body: some Reducer<State, Action> {
        Reduce<State, Action> { state, action in
            switch action {
            case .view:
                return .none
            }
        }
    }
}

The Composable Architecture version information
1.14.0
Destination operating system
iOS 17.5
Xcode version information
Xcode 15.4
Swift Compiler version information
swift-driver version: 1.90.11.1 Apple Swift version 5.10 (swiftlang-5.10.0.13 clang-1500.3.9.4)
Target: arm64-apple-macosx15.0

Hi @yimajo, are you sure this is TCA-specific behavior? Have you tried reproducing in vanilla SwiftUI with @Observable to see if the same thing happens?

Hi @mbrandonw.  Thank you for your response.
Since you responded, I tried it with vanilla SwiftUI.
The same thing did not happen. When @Observable is set to nil, the change in its state appears to be the result of it being monitored correctly by SwiftUI.
import SwiftUI

@MainActor
struct SampleFeature2View: View {
    @State var counter: Counter?

    var body: some View {
        VStack {
            Button("Present ChildView") {
                counter = Counter(count: 1)
            }
        }
        .sheet(
            isPresented: Binding<Bool>(
                get: { counter != nil },
                set: {
                    if !$0 {
                        counter = nil
                    }
                }
            )
        ) {
            NavigationStack {
                ChildFeature2View(counter: $counter)
                    .toolbar {
                        ToolbarItem(placement: .cancellationAction) {
                            Button("Cancel") {
                                counter = nil
                            }
                        }
                    }
            }
        }
    }
}

struct ChildFeature2View: View {
    @Binding var counter: Counter?

    init(counter: Binding<Counter?>) {
        self._counter = counter
    }

    var body: some View {
        VStack {
            Text("Counter: \(String(describing: counter?.count))")

            if counter == nil {
                Text("counter is nil")
                    .onAppear {
                        // When printed, it is working properly.
                        print("observe", self.counter?.count, #line)
                    }
            }
        }
    }
}

@Observable class Counter {
    var count: Int
    init(count: Int) {
        self.count = count
    }
}

Hi @yimajo, thanks for that, but unfortunately I'm not sure if that is a faithful recreation in vanilla. You should have a parent @Observable model that holds onto a child @Observable model, and does presentation from that. And further I wouldn't use @State because it tends to behavior much differently from regular let properties holding onto observable models. Also, the child feature should probably be UIKit too, and you can use withObservationTracking to see if it gets pinged when dismissing the child feature.
Also, aside from the repro, have you been able to determine if there are any negative effects of this additional observation? We need to prioritize investigating this issue amongst all of our other work, and if there are no negative side effects we may just consider it "expected behavior" for the time being and close out this issue.

Hi @mbrandonw. Thank you for your response.
I’ll proceed under the assumption that you’d like me to provide an example.
The following is an example of a camera app where state is set to nil, and observe is triggered, but observe itself cannot handle the situation correctly. It monitors the switching of captureSession when switching between multiple camera lenses or video cameras, initializes the preview view when the captureSession changes, and calls the Reducer’s Action based on that change.
// Here's my example.
override func viewDidLoad() {
    super.viewDidLoad()
    store.send(.view(.onAppear))

    observe { [weak self] in
      guard let self else { return }
      guard let session = store.captureSession else { return }

      // Clear PreviewLayer
      ....

      // Create PreviewLayer
      previewView = createPreviewLayer(size: view.bounds.size, session: session)
      view.addSubview(previewView)
      store.send(.view(.didCreatePreviewLayer))
    }
  }

when setting the Presents state to nil causes the camera screen to close, observe is triggered, causing the view to reinitialize and the Action to be re-issued.

Hi @yimajo, thanks for the real world use case. That definitely helps us understand better how you are using these tools.
It looks like we need to improve the documentation here a bit because currently your code snippet is doing some dangerous things inside the observe closure. That closure should be thought of as being analogous to the body property of a SwiftUI view. You should only perform the most basic of UI updates in that closure. You should not perform side effects, just as it is not valid to mutate state or perform side effects in a body:
struct MyView: View {
  @State var count = 0
  var body: some View {
    let _ = count += 1         // ❌ Not correct to do!
    URLSession.shared.data(…)  // ❌ Also not correct to do!
  }
}

In your case, sending an action to the store during observe is not a good idea. And really, it seems like it shouldn't be necessary to send the action. After all, your feature knows when captureSession flipped from nil to non-nil, or vice-versa, and so can't it perform the logic of didCreatePreviewLayer at that moment instead of having the view tell it to do that logic?
And further, even the addSubview logic is a little tricky. You should probably only addSubview if the view isn't already created, and further you should probably remove the previewView when the state becomes nil:
observe { [weak self] in
  guard let self else { return }

  if let session = store.captureSession, previewView == nil {
    previewView = createPreviewLayer(size: view.bounds.size, session: session)
    view.addSubview(previewView)
  } else if let previewView, store.captureSession == nil {
    previewView.removeFromSuperView()
    previewView = nil
  }
}

And this kind of tricky logic is what our fully general destination is supposed to accommodate, though sadly right now it is tailored only for UIViewController, not UIViews. I could imagine us generalizing it anymore to allow for this kind of pattern:
destination(item: $store.captureSession) { session in
  createPreviewLayer(size: view.bounds.size, session: session)
} present: { previewView in
  view.addSubview(previewView)
} dismiss: { previewView in
  previewView.removeFromSuperview()**
}

And then you wouldn't have to deal with observe and all the if/else-checking at all.
With all that said, I do believe that this isn't really an issue with the library and so I am inclined to convert it to a discussion. I feel that if you removed the side-effects from your observe you would not notice the extra observation, and I'm not entirely sure it's possible to avoid that observation. Though that would take more investigation to determine.

Hi @mbrandonw. Thank you for your response.

I feel that if you removed the side-effects from your observe you would not notice the extra observation,

You mentioned removing side effects from observe, but please take another look at the example I initially provided: https://github.com/pointfreeco/swift-composable-architecture/issues/3367#issue-2513397561
In this case, when the state is set to nil, self is still not nil and the observation is triggered. Is there really a side effect happening here? Also, I don’t mind if this issue is moved to a discussion.
I hope my point is clear.

authors: mbrandonw yimajo


text:
[ENH] More advanced heuristics for finding out echo train length

Changes proposed in this pull request
This pull request slightly changes the heuristics for finding the echo train length, taking into account that the length of the phase-encoding dimension in a nifti-file (or DICOM) is not necessarily the same as that of the acquired data. There can be a difference between the acquired and reconstructed matrix.
See also issue https://github.com/poldracklab/fmriprep/issues/1029

Documentation that should be reviewed

None

Hi @Gilles86, sorry for pestering you with this PR, but I'm doubtful to hit merge before having some explicit answer to the questions above. With that, we'll be able to update the documentation accordingly and resolve related issues more promptly. Thanks a lot for your contribution!

Hey @oesteban,
After discussing this a bit more with some colleagues and reading up, I would like to revoke the pull request for now. I think I misunderstood. The effective echo spacing is the 'virtual' amount of time it takes between k-space lines in the reconstructed image (and not the acquired one). So we should take into account the number of reconstructed voxels rather than the number of acquired k-space lines.
See also the BIDS specification ("RECOMMENDED. The "effective" sampling interval, ..., defined based on the size of the reconstructed image in the phase direction.") and this thread on the FSL mailing list.
This suggests that the current code works well, even though in a way it 'overestimates' the number of phase-encoding lines, because this is what FUGUE expects you to do.
I think that the current fmriprep code probably behaves like it should and my pull request would break things. I find it very hard to understand what exactly goes on though and whether FUGUE indeed behaves correctly when you upsample the image by factor x in the phase-encodign direction, but then also reduce the effective echo spacing by the same factor x.
What is especially strange to me is that the TotalReadOutTime is defined 'effectively' as follows: "... specified in seconds, that would have generated data with the given level of distortion. It is NOT the actual, physical duration of the readout train".
In that case, I think this line is off, since it does not take into account the acceleration.
https://github.com/poldracklab/fmriprep/blob/a255683b2f2a0d643accfb13b341cbd9311cda55/fmriprep/interfaces/fmap.py#L431
Is there anyone else in the fmriprpe/BIDS community who is a true expert on this?

Thanks for all these details. I've opened a new issue to note your request for information and double check that line you believe is off. Please reopen if you feel we'd need to take further actions.

repo: poldracklab/fmriprep


text:
distorted screen on quest 2. is there any paln to support quest 2?

same as title. I've just recieved my quest 2 today, and ALVR connects fine, but screen is distorted.
is there any plan to support Oculus Quest 2?

I also have this as a bug. Is there any updates on this?

Same issue here. Quest 2 with most games gives at least some kind of weird distortion effects. Blade and Sorcery looks like it's set to negative IPD lmao

Are you all using IPD 3? I'm using ALVR from this repo, and with this issue report, it seem IPD 3 is broken in ALVR.

Are you all using IPD 3? I'm using ALVR from this repo, and with this issue report, it seem IPD 3 is broken in ALVR.

Nope, I use the 1 setting for IPD. I’m a cyclops. 😂

Visual distortion when using ALVR with Steam VR and Quest 2
Same Issue for me, to add a little more detail.  I'm Oculus Quest 2 on ALVR 12.4.1 downloaded from https://github.com/JackD83/ALVR/releases.  I'm running a Radeon RX 5700 XT with Ryzen 7 2700X and Radeon Software 20.4.2.
The problem seems to be with the interface between Steam VR and ALVR and it's understanding of headset orientation.  When ALVR server first connects to the client on the Quest 2 (white background, black grid, ALVR text) all is fine, I can look around and change headset orientation and everything is perfect.  Once Steam VR home loads however, the visual distortion starts.   There are various things wrong with the view, including incorrect "depth" but the most obvious noticeable distortion is when you tip your head to the side.  If you tip your head to the right (clock wise viewed from the rear) , the geometry skews so as to render vertical lines still vertical when they should now be rotated to the left (anti clockwise).  What was a square is now a rhombus! I've tried adjusting a variety of settings and haven't been able to cure this.    There are clearly people using Quest 2 and ALVR as I've read plenty of reviews, there are also clearly at least a few others with this issue though.  Any help would be greatly appreciated.  I love my Quest 2, but desperately want to use it now to access my Steam VR library.

Are you all using IPD 3? I'm using ALVR from this repo, and with this issue report, it seem IPD 3 is broken in ALVR.

This was the issue for me.  The problem occurs when I've moved the eye-pieced in the headset as far apart as they can go.  If I move them to the central position, everything works perfectly :-)  I think I must be IPD 2.5 as I'm quite comfortable in either of those lens positions.  Thank you for the fix! :-)

i got the same problem, when i look arround its looks like warped distortion, i use ipd 3 with quest 2.
its there any setting that can help with this? or we have to waiting to an update?

The other thread about this issue has a post from the developer saying it
will be patched 'next week'.  For now, if you can still see ok, move the
lenses to central IPD 2 position. ALVR then works fine.
On Thu, 22 Oct 2020, 19:00 nuevakenia, notifications@github.com wrote:

i got the same problem, when i look arround its looks like warped
distortion, i use ipd 3 with quest 2.
its there any setting that can help with this? or we have to waiting to an
update?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/polygraphene/ALVR/issues/683#issuecomment-714662434,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOIJIMRRLOMCQSG65UMXFZDSMBXMXANCNFSM4SQDRN4A
.

repo: polygraphene/ALVR


text:
do cnrs natively in deno

it seems like deno will soon get the crypto libraries we need to drop our cnrs dependency on nodejs, this is a draft until those features land in deno

Closed in favour of terraform and cloud-init's user-data

repo: polyseam/cndi-next


text:
Pass comparisons tests

comparison-3.yaml
comparison-5.yaml
comparison-6.yaml
comparison-7.yaml

comparison-3 is also enabled for some time now.

no disabled comparison tests left


text:
In dockerMonitoring.writeToFile(), replace list of metrics with JSON file.

In order to make the method more generic and independent of predefined lists of metrics, I recommend to replace the long parameter list with a JSON file (the same that is saved in the database). Writing to a file, like writing to a database should be independent of the monitor (Docker or otherwise).

[ Replace parameter list with JSON file]
[ Add checks for missing metrics or empty file]
[ Add warnings in a log for missing metrics or empty file. Do not interrupt the execution of the monitor. Do not use log4j for the logging part ]

the JSON file should be an input from the user, or it's the a JSON variable similar to write_db function ?

authors: fokaefs wejdeneHaouari

repo: polytechnique-ease/blockcompass


text:
new terms for nuclear localization  / proteasome

NTR: normal proteasome localization to nuclear periphery
descendent of
FYPO:0000644	normal protein localization during vegetative growth
NTR: abolished proteasome localization to nuclear periphery
NTR increased protein localization to nuclear periphery (cut8)
NTR normal protein localization to nuclear periphery

normal proteasome localization to nuclear periphery FYPO:0005146
abolished proteasome localization to nuclear periphery FYPO:0005147
increased protein localization to nuclear periphery FYPO:0005148
also TG'd proteasome localization to nuclear periphery, so reasoner yada yada
normal protein localization to nuclear periphery is FYPO:0002563

edit file: a411f52957726ae8601bcdc51ab138446e7a0399
release: a0f809c8ef7bf13df45f7e875d5dd36751ca02f9

repo: pombase/fypo


text:
normal protein localization to Mmi1 focus

PMID:21317872

normal protein localization to Mmi1 focus FYPO:0006080
edit file: 47c54a43dd2e6328e1193a687e68e266fecd2af3
release: b10d953504e1c1eb6c93d767b60ee14903ca10d3


text:
Describe usages of fypo in the OBO metadata record

See OBOFoundry/OBOFoundry.github.io#451
I can provide an example

you can close if this is an ok example

That example is fine. I'll leave this ticket open for myself, to remind me to update the example URL when we release shiny new PomBase (aiming for September).

created pull request to update URL


text:
increased transcriptional readthrough

can
increased transcriptional readthrough
be related in some way to
abnormal transcription termination?

I can put in an "output" link.


text:
terms for PMID:18184749 Vjestica

check session

abnormal ER polarization (ectopic)
normal ER recruitment to divisions site, abnormal maintenance


text:
Update website SSL certificates

Needs to be done the week of 23rd Sept.

actually, needs to be done this week to be ready for NCBI to run checks on the 23rd ...

No problem, I'll do it later in the week.

repo: pombase/website


text:
Submodules for pony-semver, ponylang/appdirs; using appdirs for repo cache

Migrated use of pony-semver to a submodule referencing btab/pony-semver @ v0.1

Fixes #77

Added submodule for ponylang/appdirs.

Fixes #78

Using appdirs now to compute default repo cache directory.

Fixes #28

Added a --repo_cache_dir option to allow custom repo cache locations.

This needs manual CHANGELOG entries.

And one of:

The Makefile needs to be updated to check out git submodules if they don't already exist.
The checkout needs to be done in a recursive fashion to get the submodules

I'm leaning towards the Makefile should use dependency tracking to determine if the submodules are checked out and if not, should check them out. However, to move along the PR and verify that tests pass etc, Then the various github workflows that use the checkout action should be updated like this:
uses: actions/checkout@v1
  with:
    submodules: recursive

I'm not particularly comfortable with the change to using an external dependency that we don't control.
And important issue. It's referencing a tagged commit. I think this is a bad idea. Security-wise, that tag can be moved. It should use a SHA because, its a repo that is out of our control. A tag can be moved and introduce an attack vector. A SHA will still point to the same commit. That said, I'm not really comfortable using a library that is external. I'd prefer to develop a ponylang alternative or if @btab is willing, to make pony-semver a Ponylang project.

I have updated the Makefile to pull the submodules as a dep. This works locally, but I am not sure if it addresses all the paths that the github workflows need. I've updated the pony-semver reference to use the SHA. I will check with @btab to see if he is interested in moving pony-semver into ponylang.

I updated the github workflows that were building Docker images to ensure that the submodules are pulled at checkout time. And I updated the Dockerfile to get the submodule trees copied into the build container. But I now see an error from make:  make: *** No rule to make target 'install'.  Stop. locally and on github that is mysterious.

So, you don't need both the submodule recursive in github workflows and also in the Makefile. You should pick one. 2 is redundant.
You didn't update all the .github workflow files that need updating so if you want to go that route, that needs to be completed.
The submodules support is incorrect how it is done. I could start to fix it, but it also won't work particularly well for anything other than pulling in the dependencies. Really it should also be scanning for .pony files in the directories and using as part of a build target. Other than the existing syntax problem, the current setup would allow for a change to a dependency in the subdirectory and wouldn't trigger a rebuild.  But if you changed the README for either, it would trigger a rebuild.

I see that both the git workflows and Makefile approach are redundant in the CI use cases. But they are not necessarily in developer use cases. I guess we could add a note to the readme to remind people to git clone  --recursive and/or git submodule update --init. I took the approach of relying on the Makefile for make-based targets but added the --recursive to the workflows that ran Docker build directly which then requires the submodules to be pulled prior to the Docker build.
The Makefile implementation for pulling the submodules is strictly for pulling them the first time to make it more developer-friendly. Maybe that limited solution is more confusing than helpful and we should just rely on instructions in the readme.

I think we should be doing the Makefile approach, but neither was complete when I left that comment. The recursive ci pull wasn't done for all cases that needed it and Makefile left a lot of edge-cases around and wasn't working.
I think you should finish off the recursive CI stuff (it needs to be done everywhere in a .github workflow that uses checkout@v1) and remove the Makefile stuff for now and we can add an issue to add full and correct handling in the Makefile.

I'm going to take over finishing off this PR unless someone else wants to.
I definitely want to see Carl's last work completed and merged.

I did implement most of these changes.

authors: SeanTAllen cquinn

repo: ponylang/corral


text:
Compiler crash in type_append

Found on OS X using tagged Pony release 0.23.0 and also at https://playground.ponylang.org/?gist=f80edac96516b514918d1a83c6fb7cef
use "files"

actor Main
  new create(env: Env) =>
    try
      let fp = FilePath(env.root as AmbientAuth, "/tmp/foobar")?
      let f = File(fp)

      f.writev(recover [] end)
    end

The playground's execution says:
0.23.0 [release]
compiled with: llvm 3.9.1 -- cc (Ubuntu 5.4.0-6ubuntu1~16.04.9) 5.4.0 20160609
Defaults: pic=false ssl=openssl_0.9.0
src/libponyc/codegen/genname.c:63: type_append: Assertion `0` failed.

Backtrace:
This is an optimised version of ponyc: the backtrace may be imprecise or incorrect.
Use a debug version to get more meaningful information.
  ponyc(ponyint_assert_fail+0x8f) [0x73a3cf]
  ponyc() [0x6f1441]
  ponyc() [0x6f149c]
  ponyc() [0x6f130c]
[... blah blah ...]

A debug flavor of the compiler says this:
Generating
 Reachability
src/libponyc/codegen/genname.c:63: type_append: Assertion `0` failed.

Backtrace:
  0   ponyc                               0x000000010f2e29b2 ponyint_assert_fail + 162
  1   ponyc                               0x000000010f22de8a type_append + 682
  2   ponyc                               0x000000010f22e279 types_append + 89
  3   ponyc                               0x000000010f22dcbd type_append + 221
  4   ponyc                               0x000000010f22e279 types_append + 89
  5   ponyc                               0x000000010f22de26 type_append + 582
  6   ponyc                               0x000000010f22dbc9 genname_type + 41
  7   ponyc                               0x000000010f2b3f6c reach_type + 28
  8   ponyc                               0x000000010f2b4c62 add_nominal + 50
  9   ponyc                               0x000000010f2b44da add_type + 186
  10  ponyc                               0x000000010f2b72e5 reachable_expr + 1717
  11  ponyc                               0x000000010f2b74d7 reachable_expr + 2215
  12  ponyc                               0x000000010f2b74d7 reachable_expr + 2215
  13  ponyc                               0x000000010f2b74d7 reachable_expr + 2215
  14  ponyc                               0x000000010f2b74d7 reachable_expr + 2215
  15  ponyc                               0x000000010f2b74d7 reachable_expr + 2215
  16  ponyc                               0x000000010f2b74d7 reachable_expr + 2215
  17  ponyc                               0x000000010f2b74d7 reachable_expr + 2215
  18  ponyc                               0x000000010f2b74d7 reachable_expr + 2215
  19  ponyc                               0x000000010f2b74d7 reachable_expr + 2215
  20  ponyc                               0x000000010f2b74d7 reachable_expr + 2215
  21  ponyc                               0x000000010f2b3f3c handle_method_stack + 108
  22  ponyc                               0x000000010f2b3c42 reach + 82
  23  ponyc                               0x000000010f222413 genexe + 435
  24  ponyc                               0x000000010f21027e codegen + 302
  25  ponyc                               0x000000010f2899a3 generate_passes + 51
  26  ponyc                               0x000000010f1d41d1 compile_package + 177
  27  ponyc                               0x000000010f1d4070 main + 432
  28  libdyld.dylib                       0x00007fff9340d235 start + 1
  29  ???                                 0x0000000000000004 0x0 + 4
Abort

A tiny bit of LLDB inspection.
(lldb) p *type
(ast_t) $4 = {
  t = 0x000000011a339880
  symtab = 0x0000000000000000
  data = 0x0000000000000000
  parent = 0x000000011a33a9c0
  child = 0x000000011a3367c0
  sibling = 0x000000011a33a200
  annotation_type = 0x0000000000000000
  flags = 0
  frozen = false
}
(lldb) call ast_id(type)
(token_id) $5 = TK_ARROW

This works so its related to the array being assigned in the writev call.
use "files"

actor Main
  new create(env: Env) =>
    try
      let fp = FilePath(env.root as AmbientAuth, "/tmp/foobar")?
      let f = File(fp)
      let g: Array[String] = []

      f.writev(g)
    end

Maybe a dup of https://github.com/ponylang/ponyc/issues/2701?

@jemc Yes, I think so.  The array need not be empty (as 2701's subject says): f.writev(recover ["foo"; "bar"] end) will crash for the same reason.  But avoiding some refcap inference by let goo1 = recover val ["foo"] end ; f.writev(goo1) will avoid the crash.  Not using the intermediate let will crash, though.
Closing: duplicate of #2701.

authors: SeanTAllen jemc slfritchie

repo: ponylang/ponyc


text:
Use RLIMIT_STACK's current limit for Pthreads stack size if it is sane

While investigating some strange memory-clobbering looking behavior in #2850, I discovered that macOS uses a different default Pthreads stack size than Linux does.  This PR uses the RLIMIT_STACK's current limit if it is sane, i.e., if it meets the minimum size and isn't infinity.
Note that the libuv developers discovered this and have a patch that I borrowed from: https://github.com/libuv/libuv/issues/669
I'm not Pthreads-savvy enough to know if it is safe to set both actual stack memory & stack size in the same attr, in the case of the Pony runtime's checking for NUMA use on Linux.  I am being conservative and assuming that they should not be combined. This patch could save a few lines if it were OK to do combine them.

@slfritchie can you craft release notes for this change?

authors: SeanTAllen slfritchie


text:
Add Makefile-ponyc to the Appveyor ignore list

Changes to that Makefile have no impact on the Windows build and
shouldn't trigger a build.
[skip  ci]

Well this shouldnt have kicked off CI, but it did. Sigh. Any failures can be ignored as its appveyor specific.


text:
[Feature]  Create a Loader for your website according to theme

Description
Create a Loader for your website according to theme
Screenshots
No response
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I am willing to work on this issue (optional)

Congratulations, @RamakrushnaBiswal! 🎉 Thank you for creating your issue. Your contribution is greatly appreciated and we look forward to working with you to resolve the issue. Keep up the great work!We will promptly review your changes and offer feedback. Keep up the excellent work! Kindly remember to check our contributing guidelines

We already have a <Loader />
Closing as duplicate.

authors: RamakrushnaBiswal pooranjoyb

repo: pooranjoyb/popShop


text:
Allow humans WRITE access to main resources

Per: https://centrepopgen.slack.com/archives/C020PDNH3N0/p1639356527032300?thread_ts=1639355990.032000&cid=C020PDNH3N0

Thanks, I've commented on the Slack thread.

I think we've had some back and forth and agreed that only machines should really have write access to metadata - It does add some complication when manual intervention is required to modify metadata, but happy to close this.

authors: illusional lgruen

repo: populationgenomics/analysis-runner


text:
feat(packages): upgrade packages [EE-5147]

Closes EE-5147

/azp run

/scan

repo: portainer/portainer

license: Zlib


text:
Update class reference

Was referencing the wrong path to the class.

Merged, thanks!

authors: Baachi tegansnyder

repo: portphp/portphp


text:
Remove asset_dir variable and optional asset writes

Originally, generated TLS certificates, manifests, and cluster "assets" written to local disk (asset_dir) during
terraform apply cluster bootstrap
Typhoon v1.17.0 introduced bootstrapping using only Terraform state to store cluster assets, to avoid ever writing sensitive
materials to disk and improve automated use-cases. asset_dir was changed to optional and defaulted to "" (no writes)
Typhoon v1.18.0 deprecated the asset_dir variable, removed docs, and announced it would be deleted in future.
Remove the asset_dir variable

Cluster assets are now stored in Terraform state only. For those who wish to write those assets to local files, this is possible doing so explicitly.
resource local_file "assets" {
  for_each = module.bootstrap.assets_dist
  filename = "some-assets/${each.key}"
  content = each.value
}

Related:

https://github.com/poseidon/typhoon/pull/595
https://github.com/poseidon/typhoon/pull/678

Have to say I always appreciate your detailed descriptions. ❤

authors: dghubble maikelvl

repo: poseidon/terraform-render-bootstrap


text:
using thunderbird

hello,
my solution is OK , work fine,
i want to know how using Thunderbird and the solution.
Thanks

Postal does not have email accounts so you cannot connect to it using POP or IMAP.
You can configure Thunderbird to use Postal SMTP credentials if you like but that would only seem to be half of a traditional email setup as you wouldn't be able to read email Postal had received in Thunderbird.

repo: postalhq/postal


text:
Broken postal.lodash.js

Since the lodash@4 version bump in the postal@1.0.9 update, the postal.lodash.js build is broken. As shown in the npm run test-lodash :
❯ npm run test-lodash

> postal@2.0.0 test-lodash /Users/thibaut/Code/postal.js
> ./node_modules/mocha/bin/mocha -r spec/helpers/node-lodash-build-setup.js spec

module.js:440
    throw err;
    ^

Error: Cannot find module 'lodash/internal/createPartialWrapper'

After some investigation, it seems that the src/mindash.js is out of date, as lodash@4.0.0 changed most of its modules paths (the full list of changes is here : https://github.com/lodash/lodash/wiki/Changelog#v400)
For example
var createPartialWrapper = require( "lodash/internal/createPartialWrapper" );

seems to be now
var createPartialWrapper = require( "lodash/_createPartialWrapper" );

For people using Webpack or other bundlers with the postal.lodash.js build, I recommend to keep the postal version to 1.0.8 until this is fixed.

I wanted to submit a PR until the simple require( "lodash/internal/createForEach" ) transformation into  require( "lodash/_createForEach" ) failed, as this module don't seem to exist anymore.

Something is definitely up, a bunch of my builds are failing right now from this.

Looks like the only way to "fix" it as of right now is to lock the version of lodash to 3.x.


text:
Allow inline json instead of file

I would like to use configure head as inline json, form same config instead of using external file

@justgook Hi, yes you can for example
require('posthtml-head-elements')({headElements: {/* you inline json */}})

or are you talking about something else?

im about using it over CLI / config json..
https://github.com/posthtml/posthtml-head-elements/blob/master/index.js#L127  - based on that line - it will try to load file..

if i run via posthtml-cli - that config will fail..
module.exports = {
    posthtml: {
        plugins: {
            'posthtml-head-elements': {
                headElements:
                    {
                        "meta": [
                            {
                                "charset": "utf-8"
                            },
                        ]
                    }
            }
        }
    }
}```

@justgook can you create a repository with an example of playing back an error?

in progress.. now ill create that PR - and later evening will push updates to repo.

now ill create that PR - and later evening will push updates to repo.
Thank you very cool 👍

authors: Scrum justgook

repo: posthtml/posthtml-head-elements


text:
DNS issue(s) with new hassio_supervisor version (image 208 and above) - [supervisor.dbus.nmi_dns] No DnsManager support on the host. Local DNS functions have been disabled.

Hey, i'm using this docker-compose for the past few months (thanks!) and all of a sudden things become more problematic.
i'm using:
NAME="Ubuntu
VERSION="18.04.4 LTS (Bionic Beaver)

regular computer to run this docker-compose and i noticed that the DNS container is not longer work with the warning below and after this i'm getting:
hassio_supervisor | 20-03-09 19:58:52 ERROR (SyncWorker_11) [supervisor.docker] Can't create container from addon_core_duckdns: 404 Client Error: Not Found ("No such image: homeassistant/amd64-addon-duckdns:1.10")
hassio_supervisor | 20-03-09 19:58:52 ERROR (SyncWorker_17) [supervisor.docker] Can't create container from addon_a0d7b954_portainer: 404 Client Error: Not Found ("No such image: hassioaddons/portainer-amd64:1.0.0")
hassio_supervisor | 20-03-09 19:58:52 ERROR (MainThread) [asyncio] Task exception was never retrieved
hassio_supervisor | future: <Task finished coro=<Addon.start() done, defined at /usr/src/supervisor/supervisor/addons/addon.py:472> exception=AddonsError()>
hassio_supervisor | Traceback (most recent call last):
hassio_supervisor |   File "/usr/src/supervisor/supervisor/addons/addon.py", line 493, in start
hassio_supervisor |     raise AddonsError() from None
hassio_supervisor | supervisor.exceptions.AddonsError
hassio_supervisor | 20-03-09 19:58:52 ERROR (MainThread) [asyncio] Task exception was never retrieved
hassio_supervisor | future: <Task finished coro=<Addon.start() done, defined at /usr/src/supervisor/supervisor/addons/addon.py:472> exception=AddonsError()>
hassio_supervisor | Traceback (most recent call last):
hassio_supervisor |   File "/usr/src/supervisor/supervisor/addons/addon.py", line 493, in start
hassio_supervisor |     raise AddonsError() from None
hassio_supervisor | supervisor.exceptions.AddonsError
hassio_supervisor | 20-03-09 19:58:57 INFO (SyncWorker_12) [supervisor.docker.interface] Start homeassistant/qemux86-64-homeassistant
hassio_supervisor | 20-03-09 19:59:02 ERROR (MainThread) [supervisor.homeassistant] Home Assistant has crashed!
hassio_supervisor | 20-03-09 19:59:02 INFO (MainThread) [supervisor.addons] Phase 'application' start 2 add-ons
hassio_supervisor | 20-03-09 19:59:02 ERROR (SyncWorker_16) [supervisor.docker] Can't create container from addon_core_configurator: 404 Client Error: Not Found ("No such image: homeassistant/amd64-addon-configurator:4.7")
hassio_supervisor | 20-03-09 19:59:03 ERROR (SyncWorker_0) [supervisor.docker] Can't create container from addon_a0d7b954_nodered: 404 Client Error: Not Found ("No such image: hassioaddons/node-red-amd64:6.1.3")
hassio_supervisor | 20-03-09 19:59:03 ERROR (MainThread) [asyncio] Task exception was never retrieved
hassio_supervisor | future: <Task finished coro=<Addon.start() done, defined at /usr/src/supervisor/supervisor/addons/addon.py:472> exception=AddonsError()>
hassio_supervisor | Traceback (most recent call last):
hassio_supervisor |   File "/usr/src/supervisor/supervisor/addons/addon.py", line 493, in start
hassio_supervisor |     raise AddonsError() from None
hassio_supervisor | supervisor.exceptions.AddonsError
hassio_supervisor | 20-03-09 19:59:03 ERROR (MainThread) [asyncio] Task exception was never retrieved
hassio_supervisor | future: <Task finished coro=<Addon.start() done, defined at /usr/src/supervisor/supervisor/addons/addon.py:472> exception=AddonsError()>
hassio_supervisor | Traceback (most recent call last):
hassio_supervisor |   File "/usr/src/supervisor/supervisor/addons/addon.py", line 493, in start
hassio_supervisor |     raise AddonsError() from None
hassio_supervisor | supervisor.exceptions.AddonsError

I've tried to use older version but it's keep update the image
also i've tried to set the DNS address manually and also i was able to reproduce this issue on other machines.

Sorry, I have no idea what happens here 😟 I don't have this problem myself. Have you tried searching the forums, in case someone else has similar issues?

authors: Johaik postlund

repo: postlund/hassio-compose


text:
Open Banking Element

Add an element explaining what open banking is about.

Added - https://apis.how/elements/open-banking/

repo: postman-open-technologies/lifecycle


text:
Make indentation consistent

I got tired of switching between 2- and 4-space indenting when I switched files. I've gone through and reindented all the files (without changing any code of course).
NB There may be some Emacs indenting artefacts still in there. But we can fix those when we spot them.

Hmm, pull requests don't really work for global cosmetic changes. Retracting. I would like to see the whitespace sorted out though.

repo: postwait/node-amqp


text:
Man page install

It would be good to add a man page install to the CMakeLists.txt file.

That's true, It'd be better than doing manually as I tried to do in the brew formula.
It have been a long time since I last used CMake, so if you can help, I'd really appreciate that 😄

authors: fszymanski posva

repo: posva/catimg


text:
docs: fixed dead link to docs

Fixes this issue https://github.com/posva/pinia/issues/637

@posva Thanks, I originally created the issue because I wasn't sure where the URL should have pointed to in the docs until I read all the way to the bottom. At that point I decided I might as well fix my own issue.

repo: posva/pinia


text:
setattr in handle.py does not always work with my version of Python

I am running anaconda 1.9.1 with Python 2.7.6.
I was running "test_cases/issue_120" with Questa through the FLI interface, after fixing #364, and still came across an issue that prevented the test from passing.
I found that setattr in handle.py works the first time it is invoked, but the next time it is invoked it fails and raises an Attribute exception.
I loaded up handle.py with a lot of debug and the attribute was being found, but the test
"if hasattr():" was failing.
The issue went away if I changed the test to check for "not None".

Issue is fixed in the latest master.

repo: potentialventures/cocotb


text:
Intercom adapter

We use Intercom in our app and we're currently adding it to a custom ember-metrics adapter. Would be happy to create a PR if you'd consider adding Intercom support to ember-metrics core?

Yes definitely!

authors: poteto wecc

repo: poteto/ember-metrics


text:
Add isna.ir

Crawl https://www.isna.ir/

I added this one but there is a problem. Archive page for each day contains information from other days as well. I should create a filter for that and crawl the data again.


text:
add examples section to docs

[x] link revme there (will be done in https://github.com/powdr-labs/powdr/pull/1359)
[x] some more examples
[ ] example with public inputs

Done

oops missed the last item

repo: powdr-labs/powdr


text:
Pr tests

Pull Request
WHAT
Attempt to add trigger for tests on pull requests.
WHY
To reduce likelihood of tests breaking.
Type of change

[ x] DevOps, CI/CD

@HaraldGSvendsen

repo: powergama/powergama


text:
Tgbot转发错误

设置好token，chatid，测试显示SenderTelegramMsg-发送状态：{"ok":false,"error_code":400,"DESCRIPTION":"Bad Request:chat not found"}

chatid弄错了，
wiki有写明

获取自己（或群组）的ChatID，粘贴到「设置被通知人的ChatId」一栏
跟自己的机器人聊天，随便说点什么；或者创建一个群组，把机器人拉入群组，在群组里随便说点什么。
然后打开这个链接 https://api.telegram.org/bot/getUpdates 获取（PS.注意换成你自己的）
ChatID 取值 result->message->chat->id (个人是纯数字；群组是负数，type：group；)

repo: pppscn/SmsForwarder


text:
是否有人曾提过类似的问题？
否（No）
你觉得APP有什么不足之处？
目前仅有POST和GET，是否可以新增PATCH请求方式，这样可以利用gihub的OpenAPI不断地将新消息推送到某个地方（如Issuse地某条评论）。
当然也可以用POST请求方式新建，但这样地结果就是导致消息越来越多，还需要当时清理。
你觉得该怎么去完善会比较好？【非必答】
No response

测试一下

请下载每周构建版本帮忙测试一下 PUT/PATCH 请求方式
https://github.com/pppscn/SmsForwarder/actions/workflows/Weekly_Build.yml
PS. 上一楼是通过smsf修改的，参考文档：https://docs.github.com/cn/rest/issues/comments#update-an-issue-comment

测试PATCH方式正常，

authors: BetaXOi pppscn


text:
Vídeo de propaganda do Maker

Todas as informações gerais estão na issue central.
Para mais informações do APP basta procurar no repositório "Programa" ou no repositório de cada aplicativo.
Dúvidas que não forem sanadas com as buscas nos repositórios devem ser tiradas com a pessoa que é gerente do projeto.

Criei as pastas dessa issue no Google Drive:

 Pasta da issue
🔽 Entrada
🔼 Saída

"o nós fizemos a diagramação pra vc" n está certo, mas achei o vídeo interessante

Vídeo atualizado na pasta de entrada.

Fiz as alterações no vídeo. Como ainda não temos identidade visual, o vídeo continua sem finalização. Está na pasta de entrada.

Achei que o vídeo ficou bem melhor! Parabéns!
Essa tela ainda me incomodou um pouco....
não sei se deixar as capas meio viradinhas não melhoraria ou fazer elas serem menores e aparecerem mais juntas?

O vídeo está ficando maravilhoso, parabéns Amanda, você arrasa demais!!
No finalzinho do vídeo, eu vou deixar uma sugestão....

Na transição dessas duas palavras, eu sugiro que a palavra "maker" apareça como um "boom" logo após que desaparece o "acesse", porque ela parece meio escondida e sem destaque quando fica embaixo da outra e com os pontinhos no final, seguindo extamanete o mesmo padrão da palava anterior, já que o vídeo é sobre o MAKER, poderia colocar essa palavra maior, mais destacada, talves com outra cor e em uma tela separada do acesse.

Concordo com a Luiza em deixar as capas mais pertinho umas das outras e um pouco menores. Também acho que daria para colocar mais uns dois exemplos na parte após o "Nós fazemos a diagramação para você".
Em relação ao seu comentário @MariaLuizaReviliau. Creio que esse finalizinho esteja assim só por otimização do tempo mesmo. Como não tem a logo, esse final vai ser alterado depois e vai seguir o mesmo padrão dos vídeos anteriores.

@practice-uffs/ger-auxilio @practice-uffs/ger-comunicacao @morgana-mo @Claudineia-VR @lcaimi @Dovyski
Aguardamos o feedback até amanhã a noite, depois disso a issue será concluida.

Gostei bastante da batida da música  que foi utilizada.
Nessa tela concordo com o colocado anteriormente que daria para deixar as capas mais pertinho umas das outras e um pouco menores, acredito que daria uma sensação de uniformidade maior.

Nessa tela em específico a transição para chegar a frase completa me pareceu "lenta" em relação as demais.

O trabalho feito até aqui é excelente @amandasegattob, parabéns!

Boa noite! Fiz as alterações. O vídeo está na pasta de entrada.

@practice-uffs/con-design @minieradka
quando a logo do maker estiver pronta, nos avise para que possamos finalizar o vídeo.

Quando existir uma logo, voltamos nessa tarefa. Por enquanto nossa parte está finalizada.

@amandasegattob como já existe a logo, esse vídeo pode ser finalizado.

Só pra avisar que eu ainda não consegui finalizar o vídeo pq preciso gerar o qr code e o site do PRACTICE tá fora do ar, mas assim que conseguir, coloco aqui.

Bom dia! Finalizei o vídeo e acrescentei a versão vertical dele. Estão na pasta de saída.

@morgana-mo @JuliaGaboardiB vídeos finalizados e prontos para serem postados.

authors: MariaLuizaReviliau PracticeUFFSBot amandasegattob luizatonial morgana-mo robisonjose

repo: practice-uffs/programa


text:
Documentation updates

We need to add the latest features to the release notes, as well as update the link to the demo video

Ready for review

:+1:

authors: justinvdm rudigiesler

repo: praekelt/junebug


text:
Is it possible to not trim the inputted text onChange?

I am passing inputValue and an onChange function into react tags.
The problem is i am unable to add any spaces to the end of the inputted text i think this is because it is trimmed before it gets to the passed onChange method.
Not sure what the best option would be for this improvement/change. Either remove the trimming altogether and let users implement there own or pass trim as a prop which you can pass true or false.

@con322 leading and trailing spaces will be trimmed, i didn't get your use case here. why do you need it not to be trimmed, can you explain?

@ad1992 thanks for the quick reply. I am setting the input value therefore need to change the state using the onChange function, within the onChange function i set the state of inputValue which is passed to react-tag-input also within that function I have custom validation (validation doesnt do anything fancy other than display a message somewhere outside of the react-tag-input component), because the text is trimmed before it reaches my code it means that I cannot put spaces at the end of the thing i am typing i'd have to type the phrase and then go back and put the spaces in. Does that make sense?

@con322 I am not sure If I got you right. I understood that spaces are trimmed before your callback is hit. But can you give an example of why the spaces are needed?

@ad1992 because validation is done onChange therefore after every key press so if a users puts a space it's then trimmed before i can change the state.

@con322 we trim the data only when the keys which are delimiters are pressed. So you can pass only enter key as a delimiter and use handleAddition callback. does that make sense ?

@ad1992 I am also having the same issue and I believe it to be a bug.

@ad1992 Any news on this?

@add1992 I've recreated this issue. It's here https://stackblitz.com/edit/react-tag-input-953xaw
It seems to me that this is a really simple fix, simply don't trim the text and send it as is. It's not like it's any of your code that is dependent on the text being trimmed, it's only consumers of the component who would subscribe to the event. Why not leave it up to them to trim the input if needed?

@richsell86 @con322 got it. We shouldn't trim the for a controlled component. I will push the fix for this.

this has been fixed @richsell86 @con322 . Thanks for reporting.


text:
Bullseye Game

Describe the project you want to add with tech stack
It is a simple game based on html, css and javascript where player have to draw back an arrow and launch it to hit the target.
Expected behavior
As the arrow hit the target the points will increase and if it doesn't the score will remain as it is.
Screenshots (optional)

Additional context (optional )

Please assign me this issue under Gssoc'23.

@MohitGupta121 please add the labels.

@uzmaansari23 make pr

repo: pranjay-poddar/Dev-Geeks


text:
Lost function

Hi! I was operating great, with the cloud project and everything, then I had to restart the HB service a couple of timer due to other plug-in and now the log says this plug-in has access denied tried uninstalling and reinstalling but no luck.
Here is a copy of the log with the errors.
Any idea or solution? Pliss
Been lovin the IoT

I have added good amount of error handling now. Can you please update and let me know if error persists? Please feel free to reopen if error persists.

repo: prasad-edlabadka/homebridge-tuya-ir


text:
Windows 7 & Server 2K8 Speed Limitation

#1) Appreciate the project.
#2) It appears that on Windows 7 and Windows Server 2008 R2 the uploads are limited to 600KB/s.  On Windows 10 and Server 2012 R2 it uploads at full speed (10MB/s+).
Any idea what the problem could be?
v. 2.0.1

Did you use gdrive 1 on the same system without limitations? It might be related to the chunksize,  you could try experimenting with the --chunksize flag, the default in gdrive 1 was 4194304.

I get the same results with gdrive 1.9.
I have tried playing with the chunk size going all the way up to 16MB. It actually goes slower the more I mess with it.
It only happens on my Windows 7 (32 and 64) and Server 2008 R2.  It basically caps out at 600KB/s.  I have Windows 10 Pro and Server 2012 R2 boxes using the same binary (386 and 64) and the same config file and it uploads at 10MB/s.

It also works fine on Ubuntu.   I mounted an admin share and uploaded my file from the share at full 10MB/s speed.  So I know its not an i/o problem with the disk I'm trying to work from.
It has to be something to do with Windows 7 and 2008.  I tried with two different antivirus as well wondering if that might be the issue. Doesn't seem to matter.

I just installed an original Windows 7 Pro (no SP1) and I have the same results.  So it's not a Windows Update that broke this.
Will attempt at another site later and see if its my network with Windows 7/2008 only. Ubuntu/2012 works fine on this network but I really want to provide as much feedback as possible.

Offsite Update: Can confirm that on a fresh install of Windows 7 Home Premium 64bit that the upload is still slow. I got around 400KB/s upload. Windows 10 Pro at same location upload is at 4.5MB/s.
Not sure what the total upload bandwidth is but results speak for themselves.

Providing as much feedback as possible:
A Windows 10 VM on a Windows 7 Host works fine as well.

As a continued follow up.
Windows 8.1 Pro fresh install works fine as well.
Anything else I can do to help narrow down the issue?

Went back through the old binaries to 1.6.0 and all of them do the same thing.

I am seeing the same issue as well on my Windows 7 system.  Tried latest version.
gdrive: 2.1.0
Golang: go1.6
OS/Arch: windows/amd64

I have seen performance improvement if I use:
--chunksize 104857600
Setting a 100MiB size when uploading a 10.7GB file seems to help.  I went from ~300KB/sec to ~1.5MB/sec.

I have the same issue on server 2008 R2. Only mine was 300KB/sec tops.

authors: carbm1 dingerkingh prasmussen rbeede

repo: prasmussen/gdrive


text:
gdrive-linux-rpi caps speed at 2MBps (16Mbps)

While I am able to download at 50Mbps through my browser and close to 65Mbps through desktop (ubuntu - gdrive-linux-x64), the download rate stays at 16Mbps in gdrive-linux-rpi. I have tried with multiple connections.  Is this an intentional limitation?

I don't see the purpose and benefits of intentionally limiting the speed for a particular platform? If you're using the vanilla version of the pi (i.e. you did not do any mods to the networking on the pi), it's more likely that you've hit some sort of hardware speed cap on the pi itself.

True. I assumed it might've been done in consideration to the hardware
capabilities of Pi. All other downloads happen in full speed through wget &
curl.
I'm running the latest Raspbian Jessie Lite on RPi2. Ethernet connection.
Is there a way I can find out some debug info on this? A verbose mode or a
log file that I could post here?
On Jan 19, 2017 7:51 AM, "chuanzgh" notifications@github.com wrote:

I don't see the purpose and benefits of intentionally limiting the speed
for a particular platform? If you're using the vanilla version of the pi
(i.e. you did not do any mods to the networking on the pi), it's more
likely that you've hit some sort of hardware speed cap on the pi itself.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/prasmussen/gdrive/issues/250#issuecomment-273663623,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABXaukUpfoteqv3FOD_B9uCfb6ZACGx-ks5rTsiTgaJpZM4LnNj-
.

Sadly no.
On Sun, Jul 1, 2018 at 1:55 PM, pvlvsk notifications@github.com wrote:

I'm having the same problem.. @mccbala https://github.com/mccbala do
you have a solution by now?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/prasmussen/gdrive/issues/250#issuecomment-401592221,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABXaujpCa8K7m9WZbsIO1dbCAb-h1tI6ks5uCIdggaJpZM4LnNj-
.

authors: chuanzgh mccbala


text:
🛑 QRCode Generator is down

In 8e0a1e3, QRCode Generator (https://qrcode-generator.onrender.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: QRCode Generator is back up in 222ec1d after 42 minutes.

repo: prateekralhan/status


text:
provide historical usage data if available in r.auth.limits

Describe the solution you'd like
Since the values in r.auth.limits are updated every time an API call is made, it'd be really sweet to include some historical information:

A way to check the peak usage value reached since creating the Reddit object (e.g., peak_usage).
A way to check the previous final usage value for the previous period reached right before the API usage counter reset (e.g., previous_usage). This could even be a list of values that caps at an hour or something like that. (This might get a little complex for code not making a call for over 10 minutes at a time, but storing tuples of timestamp, final_usage might be easier than adding logic to add a 0 value for quiescent periods.)

Describe alternatives you've considered
I'm just going to check this periodically right now, but unless you check after every single request, you wouldn't get the true peak usage value or previous usage value, just values that are close to the real numbers.
Additional context
If the instance is new and the previous usage isn't yet known, it should either be left out or left undefined.

There really is no need for such a feature in the main package, because it's not necessary for the API, and there aren't too many people that would benefit from this. The best way to deal with your problem would be to wrap the function so that every time it is called, it appends the value to a dict with the timestamp, and then perform analysis on the data.
from time import time
rate_data = {}
reddit =Reddit(...)
rate_limit_update_function = reddit._core._rate_limiter.update
def update(self, *args, **kwargs):
    value = rate_limit_update_function()
    rate_data[time.time()] = {
            "remaining": self.remaining,
            "reset_timestamp": self.reset_timestamp,
            "used": self.used,
        }
    return value
reddit._core._rate_limiter.update = update
...

At the end of your program, you could just do this:
from json import dump
with open("data.json", "w") as fp:
    dump(rate_data, fp)

There really is no need for such a feature in the main package, because it's not necessary for the API, and there aren't too many people that would benefit from this.

I think it is potentially useful generally. It's more about improving the performance of code than it is about avoiding the maximum rate limit. It's sometimes hard to tell which things are going to generate an API call and which things are not (e.g., submission and comment objects returned by listing generators sometimes contain the data you want and sometimes they do not) and by making small changes you can often reduce your API usage and improve performance by a significant amount.

The best way to deal with your problem would be to wrap the function so that every time it is called, it appends the value to a dict with the timestamp, and then perform analysis on the data.

Thanks for the code. I might be able to use that in some testing/development code, but I'm pretty reticent to touch private functions or data so I wouldn't consider this approach practical for long-term logging and usage.
If there was a public hook, that could work.

It's sometimes hard to tell which things are going to generate an API call and which things are not (e.g., submission and comment objects returned by listing generators sometimes contain the data you want and sometimes they do not)

I have plans for a logging system that will log any attributes that result in a network request, maybe this will allow better insight as to what is causing attributes to be fetched.

If there was a public hook, that could work.

There really is no need to hook into the update function to log every update. Furthermore, any such hook should go in prawcore.

repo: praw-dev/praw


text:
Paths with arrays don't seem to work as documented.

Describe the bug
The example in the docs clarifies how to use arrays in paths:
import { defineStore } from 'pinia'

export const useStore = defineStore('store', {
  state: () => ({
    save: [
      { me: 'saved', ignored: 'ignored' },
      { me: 'saved-too', value: 'ignored-too' },
      { me: 'saved-as-well', test: 'ignored-as-well' },
    ],
  }),
  persist: {
    paths: ['save.[].me'],
  },
})

But this doesn't work, and I can't find a test that would indicate this could work.
Is the documentation correct? I sort of expected to find a test in https://github.com/prazdevs/pinia-plugin-persistedstate/blob/main/packages/plugin/tests/pick.spec.ts, or in the specs that cover configuring paths in https://github.com/prazdevs/pinia-plugin-persistedstate/blob/main/packages/plugin/tests/plugin.spec.ts#L191
So when peeking at the source, there wasn't anything obvious either, but maybe it's supposed to be handled by StateTree in pinia? I didn't dig further, so maybe someone knows off hand if the docs are incorrect, or if the feature didn't make it into release.
Thanks for the useful library, and I'll help update docs if there's something that needs to be updated there.
Reproduction
https://prazdevs.github.io/pinia-plugin-persistedstate/guide/config.html#paths
System Info
Versions:
  pinia: "^2.0.28",
  pinia-plugin-persistedstate: "^3.0.1",
System:
  OS: macOS 13.0.1
  CPU: (10) arm64 Apple M1 Max
  Memory: 212.31 MB / 32.00 GB
  Shell: 5.8.1 - /bin/zsh
Binaries:
  Node: 19.2.0 - ~/.asdf/installs/nodejs/19.2.0/bin/node
  npm: 9.2.0 - ~/.asdf/plugins/nodejs/shims/npm
  Browsers:
    Chrome: 108.0

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] The provided reproduction is a minimal reproducible of the bug.

This feature has been removed for several reasons in 3.x
It is documented here : https://prazdevs.github.io/pinia-plugin-persistedstate/guide/migrating.html#breaking-changes
If you really need to use this feature, you may want to use 2.x version.

Nope, that's the answer I was looking for. I don't need it, but having it would allow me to reduce the size of the overall data in the package. Thank you!

repo: prazdevs/pinia-plugin-persistedstate


text:
Image with fixed width and height

From what i can see this library is meant for images with a width of 100% of the container. Using an image with a fixed width and height doesn't fully pan since its calculating for an image that is meant to be 100% of the container. I can fix this by setting limitToBounds to false so that i can pan it but then by doing this you can pan the content off the screen. Is there a way to use an image with a fixed width and height while sticking to the limit bounds?
Thanks.

Yes, you can try to put your image into div and style it inside as you want 👍

https://im3.ezgif.com/tmp/ezgif-3-bc00ea4c1fbd.gif
I think the question might of been confusing. The gif above illustrates my question. The image is larger than the viewport so when i zoom in a little i can pan but its not panning all of the image. If i resize the browser you can see that there is more of the image to the right that you're not able to pan.

You have to use some css styling for that - object-fit / width / height styling, image must be contained inside of the wrapper

That answers my question, It wont work as intended with an image larger than the wrapper. Thanks for the reply, i appreciate it!


text:
improve ES6 linting

all of the es6 linting comments were coming from JSHint. ESLint is working fine and configured for ES6. there was also a problem with the JSHint+JSX and JSCS+JSX linters when having react-tools transform es6 code which resulted in some parse errors. ESLint's does have built-in support for JSX so I don't think it's too much of a concern with the workaround in place.

updates the jshint package
updates the config to lint es6 code properly
use workaround to ignore Error: Parse Error: Line #: Illegal import/export declaration for JSHint and JSCS linters

I re-updated and turned off the old js linters (jshint and jscs) so this is covered now.

authors: oohnoitz prehnRA

repo: prehnRA/lintron


text:
UI router sref links don't work

Hi,
I'm using prerender with hashbang and ui router. The links that are using ui router's sref attribute are getting autogenerated href values. The problem is that the hrefs are something like href="#!/route1" and are not working (this will get concatenated to server/?escaped_fragment=route2/#!/route1) because of the missing / at the start of the link. And I cannot force the value for href. Is this is an prerendering issue or phantomjs?
Thanks a lot

You can close this, actually the href was generated by ui-router's ui-sref directive. This can be fixed by using absolute urls through ui-sref-opts directive.
Sorry :)

Great, let me know if there's anything I can do to help!

authors: thoop unDemian

repo: prerender/prerender


text:
🛑 Beta is down

In 72c7804, Beta (https://beta.presquelabs.com) was down:

HTTP code: 400
Response time: 632 ms

Resolved: Beta is back up in 906b18c.

repo: presquelabs/upptime


text:
Change ROW representation on the client to avoid fake row field names

Fixes https://github.com/prestosql/presto/issues/4587

This changes CLI, but also impacts ResultSet#getObject. It's no longer a Map.
cc @electrum

The one of remianing failures is
java.lang.AssertionError:
Expecting:
  <{tag=0, field0=180, field1=null, field2=null}>
to be an instance of:
  <io.prestosql.client.Row>
but was instance of:
  <io.prestosql.jdbc.$internal.client.Row>

before i go into fixing this, let's agree on the direction.
@electrum @martint @kokosing please take a look.

Discussed offline with @electrum -- seems fine as a general direction

PTAL

(no longer "WIP")

@losipiuk thanks for the review. I split this into 3 commits now. Accidentally rebased on current master, sorry.

repo: prestosql/presto


text:
Add root configuration option for relative routing

Most APIs have a common prefix in all of their routes, e.g. /api/v1/
Repeating this prefix in all Pretender routes is less than ideal. It's not DRY, and an API prefix can sometimes change, requiring redundant edits across all routes.
It would be great if we could configure a shared root and specify the routes relative to this root, as shown below:
const server = new Pretender();
server.root = '/api/v1/';
server.get('users', ... );
server.get('users/:id', ... );
server.get('products', ... );
server.get('products/:id', ... );

Even better, this root property could be used to limit which requests will be handled by Pretender, so that requests to other URLs that don't match would automatically pass through.

repo: pretenderjs/pretender


text:
Removed my pr tab and fixed the linter

Removed the MY PULL REQUESTS tab.
Fixed around 70 linter erros.
(made with our tool, so we have groups)

LGTM

authors: TimvdLippe eanker

repo: preview-code/rite-evaluation


text:
🛑 TOR Node is down

In b3ac9b7, TOR Node ($TOR_IP) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TOR Node is back up in 612ff6d.

repo: prevplan/prevhelp-status


text:
Decouple HTML semantics from styles in Heading

Currently the Heading component sets styles for different heading elements (<h1> – <h6>). Instead font-size, weight and other styles should be handled through props and not tied to the semantic heading level

Closing this since it’s now in the v2 PR

repo: pricelinelabs/design-system


text:
Test

Authors: Please fill out this form carefully and completely.
Reviewers: By approving this Pull Request you are approving the code change, as well as its deployment and mitigation plans.
Please read this description carefully. If you feel there is anything unclear or missing, please ask for updates.
What are you trying to accomplish?

Screenshots

Integration

List the issues that this change affects.

Closes # (type the GitHub issue number after #)
Risk Assessment

[ ] Low risk the change is small, highly observable, and easily rolled back.
[ ] Medium risk changes that are isolated, reduced in scope or could impact few users. The change will not impact library availability.
[ ] High risk changes are those that could impact customers and SLOs, low or no test coverage, low observability, or slow to rollback.

What approach did you choose and why?

Anything you want to highlight for special attention from reviewers?

Accessibility

Fixes axe scan violation - This change fixes an existing axe scan violation.
No new axe scan violation - This change does not introduce any new axe scan violations.
New axe violation - This change introduces a new axe scan violation. Please describe why the violation cannot be resolved below.

Merge checklist

[ ] Added/updated tests
[ ] Added/updated documentation
[ ] Added/updated previews (Lookbook)
[ ] Tested in Chrome
[ ] Tested in Firefox
[ ] Tested in Safari
[ ] Tested in Edge

Take a look at the What we look for in reviews section of the contributing guidelines for more information on how we review PRs.

It works 🎉