[bug]: WAGMI useWriteContract is unresponsive

Description
I want to call a function on my smart contract for which I'm using wagmi's useWriteContract hook.
The problem is the hook is not erroring out or firing the transaction. Since, there's no error in the console I'm unable to determine the problem. Attaching the code for the component below. Any help is appreciated :)
Issue Environment

[ ] dapps/W3MEthers
[ ] dapps/W3MEthers5
[X] dapps/W3MWagmi
[ ] wallets/rn_cli_wallet
[ ] wallets/rn_cli_wallet_068_5
[X] In my own code

Output of npx react-native info
System:
OS: macOS 15.0
CPU: (8) arm64 Apple M1 Pro
Memory: 257.53 MB / 16.00 GB
Shell:
version: "5.9"
path: /bin/zsh
Binaries:
Node:
version: 16.20.2
path: /opt/homebrew/opt/node@16/bin/node
Yarn:
version: 1.22.22
path: /opt/homebrew/bin/yarn
npm:
version: 8.19.4
path: /opt/homebrew/opt/node@16/bin/npm
Watchman:
version: 2<IP_ADDRESS>
path: /opt/homebrew/bin/watchman
Managers:
CocoaPods:
version: 1.15.2
path: /Users/is-005/.rbenv/shims/pod
SDKs:
iOS SDK:
Platforms:
- DriverKit 23.5
- iOS 17.5
- macOS 14.5
- tvOS 17.5
- visionOS 1.2
- watchOS 10.5
Android SDK: Not Found
IDEs:
Android Studio: 2023.1 AI-231.9392.1.2311.11330709
Xcode:
version: 15.4/15F31d
path: /usr/bin/xcodebuild
Languages:
Java:
version: 21.0.2
path: /usr/bin/javac
Ruby:
version: 2.7.6
path: /Users/is-005/.rbenv/shims/ruby
npmPackages:
"@react-native-community/cli": Not Found
react:
installed: 18.2.0
wanted: 18.2.0
react-native:
installed: 0.74.5
wanted: 0.74.5
react-native-macos: Not Found
npmGlobalPackages:
"react-native": Not Found
Android:
hermesEnabled: Not found
newArchEnabled: Not found
iOS:
hermesEnabled: Not found
newArchEnabled: Not found
info React Native v0.75.3 is now available (your project is running on v0.74.5).
info Changelog: https://github.com/facebook/react-native/releases/tag/v0.75.3
info Diff: https://react-native-community.github.io/upgrade-helper/?from=0.74.5
info For more info, check out "https://reactnative.dev/docs/upgrading?os=macos"
Steps to reproduce
import React, { Suspense, useEffect, useState, useTransition } from 'react'
import { AppRegistry, View, Text, ActivityIndicator, Pressable, Button } from 'react-native'
import '@walletconnect/react-native-compat'
import { WagmiProvider, useReadContracts, useWriteContract, useAccount } from 'wagmi'
import { sepolia, mainnet } from '@wagmi/core/chains'
import { QueryClient, QueryClientProvider } from '@tanstack/react-query'
import { createAppKit, defaultWagmiConfig, AppKit, AppKitButton, NetworkButton } from '@reown/appkit-wagmi-react-native'
import { LPE_TOKEN_ABI, LPE_TOKEN_EXCHANGE_ABI } from './abi'
import { config } from './config'
import { RequestModal } from './RequestModel'
// 1. Get projectId at https://cloud.reown.com
const projectId = '39a38f05adaa9e35db442c0a64abdac2'

const LPE_TOKEN_CONTRACT = {
  address: '0x708638c124204e93Eb7A0EC1FC9e590AAFD305FB',
  abi: LPE_TOKEN_ABI,
} as const

const LPE_TOKEN_EXCHANGE_CONTRACT = {
  address: '0x77287A30363eC91C1719Af966A4E27C9021cF3e9',
  abi: LPE_TOKEN_EXCHANGE_ABI,
} as const

// 2. Create config
const metadata = {
  name: 'AppKit RN',
  description: 'AppKit RN Example',
  url: 'https://reown.com/appkit',
  icons: ['https://avatars.githubusercontent.com/u/179229932'],
  redirect: {
    native: 'YOUR_APP_SCHEME://',
    universal: 'YOUR_APP_UNIVERSAL_LINK.com'
  }
}

const chains = [mainnet, sepolia] as const

const wagmiConfig = defaultWagmiConfig({ chains, projectId, metadata })

// 3. Create modal
createAppKit({
  projectId,
  wagmiConfig,
  defaultChain: sepolia,
  enableAnalytics: true
})

const queryClient = new QueryClient()

function AppContent() {
  const [isTransitionPending, startTransition] = useTransition()
  const [shouldFetch, setShouldFetch] = useState(false)

  const [requestModalVisible, setRequetsModalVisible] = useState(false);
  const { isConnected, address, status } = useAccount();

  const { writeContractAsync } =
    useWriteContract();

  const { data: contractsData } = useReadContracts({
    contracts: [
      {
        ...LPE_TOKEN_EXCHANGE_CONTRACT,
        functionName: 'totalLiquidity',
      },
      {
        ...LPE_TOKEN_EXCHANGE_CONTRACT,
        functionName: 'MAX_BUY',
      },
      {
        ...LPE_TOKEN_EXCHANGE_CONTRACT,
        functionName: 'MIN_BUY',
      },
      {
        ...LPE_TOKEN_CONTRACT,
        functionName: 'balanceOf',
        args: ["0xA1CF1cD5715415825Da4b2E5D5e6dA720B238312"],
      },
      {
        ...LPE_TOKEN_CONTRACT,
        functionName: 'name',
      },
      {
        ...LPE_TOKEN_CONTRACT,
        functionName: 'symbol',
      },
    ],
  })

  const handleFetch = () => {
    startTransition(() => {
      setShouldFetch(true)
    })
  }

  // Function to safely stringify data, handling BigInt values
  const safeStringify = (data: any): string => {
    return JSON.stringify(data, (_, value) =>
      typeof value === 'bigint' ? value.toString() : value
    )
  }

  const buyTokens = async () => {
    console.log("buyTokens");
    try {
      writeContractAsync({
        chainId: sepolia.id,
        address: LPE_TOKEN_EXCHANGE_CONTRACT.address,
        abi: LPE_TOKEN_EXCHANGE_ABI,
        functionName: 'buyTokens',
        args: [10000000000000000],
      });
    } catch (error) {
      console.log(error);
    }
  };

  const addLiquidity = async () => {
    try {
      writeContractAsync({
        chainId: sepolia.id,
        address: LPE_TOKEN_EXCHANGE_CONTRACT.address,
        abi: LPE_TOKEN_EXCHANGE_ABI,
        functionName: 'addLiquidity',
        args: ['0.01'],
      });
    } catch (error) {
      console.log(error);
    }
  };

  useEffect(() => {
    console.log("isConnected", isConnected);
  }, [isConnected]);

  useEffect(() => {
    console.log("address", address);
  }, [address]);

  useEffect(() => {
    console.log("status", status);
  }, [status]);

  return (
    <View style={{ flex: 1, justifyContent: 'center', alignItems: 'center' }}>
      <AppKitButton />
      <NetworkButton />
      <AppKit />

      <Text onPress={handleFetch}>Fetch Data</Text>
      {isTransitionPending && <ActivityIndicator />}
      {contractsData && <Text>{safeStringify(contractsData)}</Text>}
      <Pressable onPress={buyTokens} style={{ padding: 10, backgroundColor: 'lightblue', margin: 10 }}>
        <Text>buy 10 tokens</Text>
      </Pressable>
      <Pressable onPress={addLiquidity} style={{ padding: 10, backgroundColor: 'lightblue', margin: 10 }}>
        <Text>add Liquidity</Text>
      </Pressable>
    </View>
  )
}

function App() {
  return (
    <WagmiProvider config={wagmiConfig}>
      <QueryClientProvider client={queryClient}>
        <Suspense fallback={<ActivityIndicator />}>
          <AppContent />
        </Suspense>
      </QueryClientProvider>
    </WagmiProvider>
  )
}

// Register the app
AppRegistry.registerComponent('main', () => App)

export default App

Snack, code example, screenshot, or link to a repository
https://github.com/thezaidbintariq/react-native-metamask

Hey @thezaidbintariq that's probably an issue with Wagmi. How are you checking that the write contract is not being fired?
const {data, isPending, isSuccess, isError, writeContract} = useWriteContract();
did you check what is returned in data, isPending, isSuccess, isError ?

@thezaidbintariq any news?

closing as apparently it's solved / abandoned


[Not urgent] Include instructions for building from source here on GitHub

Not a high priority thing, but many projects on GitHub include in their readme instructions to build the app from source, or at least they specify the dependencies required by the solution. I tried building from source indeed, but I gave up because I couldn't figure out what's missing and what not

I added instructions to the readme  file.
Thank you @lampenlampen for writing them up!


compare to DiscreteEvents.jl in README

fixes #82

Codecov Report

Merging #88 (0726d80) into master (4920751) will increase coverage by 0.34%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #88      +/-   ##
==========================================
+ Coverage   98.06%   98.40%   +0.34%
==========================================
  Files          10        9       -1
  Lines         258      251       -7
==========================================
- Hits          253      247       -6
+ Misses          5        4       -1

see 6 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Add Opencast 12.13 Changelog and Release Notes

Your pull request should…

[x] have a concise title
close an accompanying issue if one exists
[x] be against the correct branch
include migration scripts and documentation, if appropriate
[x] pass automated tests
[x] have a clean commit history
[x] have proper commit messages (title and body) for all commits

@lkiesow Do you want to add a note in the changelog about the reasons for the invalid zip headers?
The source of all evil was bnd from bndtools. Here's the fix https://github.com/bndtools/bnd/issues/4507 from early 2021 and here's the Apache Felix bug report from four days ago: https://issues.apache.org/jira/browse/FELIX-6622

I'm leaving the technical details for the patch notes.
But I did add the flag to circumvent the new check.


Java VM limits should match (per Atlassian recommendation)

The current blacklabelops docker-compose.yaml Java VM settings are as follows:
    environment:
      - 'CATALINA_OPTS= -Xms256m -Xmx1g'

The Atlassian recommendations on this page state:

In the general case, both Jira & Confluence users will benefit from setting the minimum and maximum values identical

So it seems that this should be changed to:
    environment:
      - 'CATALINA_OPTS= -Xms1g -Xmx1g'

Same applies to the JIRA config... although (for JIRA) I do wonder at the blacklabelops default Xmx value of 1 GB, when the general guidance from Atlassian themselves is:

Granting Jira applications too much memory can impact performance negatively, so it is best to start with 768 MB, and make modest increases as necessary

Bumping to 1 GB seems reasonable to me, but... Java isn't my thing (thankfully) and I'm wary of direct guidance saying not to allocate too much!

The docker-compose.yml needs to be adjusted. You need to specify CATALINA_PARAMETER1, CATALINA_PARAMETER_VALUE1, and so on to set the CATALINA_OPTS.
For Jira it's JVM_MINIMUM_MEMORY and JVM_MAXIMUM_MEMORY.
The default configuration if you don't specify additional environment variables:

Product
Java VM Settings

Confluence
-Xmx1024m -Xms1024m

Jira
-Xms384m -Xmx768m

Jira Image is configured differently. This changed recently: https://github.com/blacklabelops/jira#a-word-about-memory-usage

I'm confused.

Are the JVM_xxx_MEMORY settings a replacement for CATALINA_OPTS or in addition to CATALINA_OPTS?
Does this change only apply for recent JIRA versions, or is it an issue with the container?

Also, per the original reason for this issue, their docs still say to set the min and max the same.
To cover off possible versioning issues, is this how the environment section should look like for these vars in the docker compose file?
    environment:
      JIRA_DATABASE_URL: <snip>
      JIRA_DB_PASSWORD: <snip>
      CATALINA_OPTS: -Xms1024m -Xmx1024m
      JVM_MINIMUM_MEMORY: 1024m
      JVM_MAXIMUM_MEMORY: 1024m

Looks like Jira uses the JAVA_OPTS environment variable. You can check this in /opt/jira/bin/setenv.sh in the Docker container.
You need to specify:
environment:
      JIRA_DATABASE_URL: <snip>
      JIRA_DB_PASSWORD: <snip>
      SETENV_JVM_MINIMUM_MEMORY: 1024m
      SETENV_JVM_MAXIMUM_MEMORY: 1024m

According to Atlassian documentation they changed the memory configuration also for Confluence:
https://confluence.atlassian.com/confkb/how-to-fix-out-of-memory-errors-by-increasing-available-memory-154071.html
Can somebody check if either CATALINA_OPTS or JVM_MINIMUM_MEMORY, JVM_MAXIMUM_MEMORY still works? Maybe we will need an issue here.

The Confluence image is fine. -Xmx1024m, -Xms1024m, and -XX:+UseG1GC are still configured via CATALINA_OPTS in /opt/atlassian/confluence/bin/setenv.sh. -XX:MaxPermSize is not set at all.

Thank you!


Add nralibera/madagascar_is_not_only_a_movie

Repo URL:
https://github.com/nralibera/madagascar_is_not_only_a_movie
Checklist:

[X] The lines end with a .. This is to conform to awesome-list linting and requirements.
[X] The title of the pull request is Add/Update/Remove `username/repo`  (notice the backticks around `username/repo`)
[X] The format of the line is [username/repo](link) - description.
[X] The description doesn't contain emojis.
[X] Acronyms should be fully capitalized.

Thanks for the PR!


Rendering of longish blockquotes

Do you need help or have a question? Please come chat in Slack: https://ghost.org/slack 👫.
If you're filing a bug 🐛, please include the following information:
Screenshot

Steps to Reproduce

In the Ghost 1.x editor, in an article, enter a blockquote (> Quote Text).
See the nice rendering in the left part of the above screenshot.
See the no-so-nice rendering of a longish blockquote by the Casper 2.0.4 theme in the right part of the screenshot.

Technical details

Casper Version: 2.0.4
Ghost Version: 1.6.0
Browser Version: Safari 10.1.2
OS Version: macOS 10.12.6

IMHO the quote looks like an oversized link.


Documentations required

[x] README
[x] Design
[x] Usage
[x] CHANGELOG
[ ] more...

/cc @hhyasdf

We have prepare a basic usage and design doc for v0.1.0. And it must take a long time to write more docs.
This issue will be closed, and maybe a more specific description for what kind of docs do we need is more suitable for related issues next time.


data:Himanshuch8055.json

Fixes Issue

Changes proposed

Check List (Check all the applicable boxes)

[ ] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[ ] All new and existing tests passed.
[ ] This PR does not contain plagiarized content.
[ ] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

Looks Good

Thanks @Tejender1521

Everything looks great.


Fix typo in custom_models.mdx

I have made a correction in line 75 to maintain consistency with the subsequent code. The hidden layer should be labeled as 'seq.2' instead of 'seq.1'.

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


Make an async variant of the reflection server

We should not force hybrid server mode (which will always exhibit poor performance) just for built in services.
We have sample implementation for health checks, part of this work should be expanding that mechanism so other built in services can take advantage of it.

@yang-g can probably give some implementation advice.


pkg/blobserver/replica: staticcheck

Closing this, see my comment here:

https://github.com/perkeep/perkeep/pull/1405#issuecomment-894727096


Include allergy field

Pull Request Test Coverage Report for Build 111

72 of 85 (84.71%) changed or added relevant lines in 11 files are covered.
2 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.8%) to 87.903%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/main/java/seedu/address/model/food/Food.java
7
8
87.5%

src/main/java/seedu/address/model/user/UserProfile.java
9
14
64.29%

src/main/java/seedu/address/storage/XmlAdaptedUserProfile.java
8
15
53.33%

Files with Coverage Reduction
New Missed Lines
%

src/main/java/seedu/address/storage/XmlAdaptedUserProfile.java
1
64.41%

src/main/java/seedu/address/model/user/UserProfile.java
1
46.34%

Totals

Change from base Build 99:
0.8%

Covered Lines:
1744

Relevant Lines:
1984

💛  - Coveralls

Resolves #70


[9.x] Fix decimal cast precision issue

Fixes https://github.com/laravel/framework/issues/45454
Problem
Currently we are handling floats via format_number. Because of number_format, we are losing precision, if the precision is long enough.
Solution
This is a 2 part solution. This PR is part one to address this issue in the least breaking way possible for 9.x and then a follow up PR will fix this using bcmath instead.
To solve this for 9.x we are now manually handling the formatting via the Str helper.
Breaking
number_format rounds numbers when the precision is being reduced. This is no longer the case and I'm not aware of any good way to handle this.
$model = new class extends Model {
    protected $casts = [
        'amount' => 'decimal:1',
    ];
};

$model->amount = '0.99';

// The following test...
// Before ✅
// After ❌

$this->assertSame('1.0', $model->amount);

// The following test...
// Before ❌
// After ✅

$this->assertSame('0.9', $model->amount);

I'm proposing that in 10.x we change this manual string manipulation into a basic bcmath call: https://github.com/laravel/framework/pull/45457
I feel that making bcmath a requirement to use an existing feature could be a breaking change for some applications(?)

It looks like this may break on numbers containing exponents, e.g. 0.1e3. Also, should a zero be added if the int part is empty (.1)?

Follow up that improves this fix: https://github.com/laravel/framework/pull/45492


[Suggestion]: Allow nuggets to form when fluid is exactly 100 mb

General Info

[ ] I would like to propose new content
[X] I would like to propose changes
[ ] I would like to propose another thing

Suggestion Description

According to Integrated Dynamics inside of the vat I have exactly 100 mb and nugget is not formed. Please change that so that automation on a larger scale would be feasible.
Currently, this locks vat to only deal with single type of berry, which also means that if we have 5 types of ores we need to have everything x5.
If this is changed we will be able to split vats into crushing and evaporation, and then use mods like Super Factory Manager to move fluids between them to allow way higher processing speed without pointless duplication.

That was fast, Thanks.


[Youtube] --abort-on-error is triggered for planned streams

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2017.04.28. If it's not read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2017.04.28

Before submitting an issue make sure you have:

[x] At least skimmed through README and most notably FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[x] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[x] Feature request (request for a new functionality)
[ ] Question
[ ] Other

[debug] System config: []
[debug] User config: ['--rate-limit', '4.2M', '-f', 'bestvideo[height<=720]+bestaudio/bestvideo[width<=1920]+bestaudio/bestvideo+bestaudio/best']
[debug] Custom config: []
[debug] Command-line args: ['-v', '--write-pages', 'youtu.be/sCc4edfDAyI']
[debug] Encodings: locale cp1251, fs mbcs, out cp1251, pref cp1251
[debug] youtube-dl version 2017.04.28
[debug] Python version 3.4.4 - Windows-7
[debug] exe versions: none
[debug] Proxy map: {}
WARNING: The url doesn't specify the protocol, trying with http
[youtube] sCc4edfDAyI: Downloading webpage
[youtube] Saving request to sCc4edfDAyI_https_-_www.youtube.com_watchv=sCc4edfDAyI_gl=US_hl=en_has_verified=1_bpctr=9999999999.dump
[youtube] sCc4edfDAyI: Downloading video info webpage
[youtube] Saving request to sCc4edfDAyI_https_-_www.youtube.com_get_video_info_video_id=sCc4edfDAyI_el=info_ps=default_eurl=_gl=US_hl=en.dump
[youtube] sCc4edfDAyI: Extracting video information
ERROR: This video is unavailable.
Traceback (most recent call last):
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpagq0np72\build\youtube_dl\YoutubeDL.py", line 760, in extract_info
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpagq0np72\build\youtube_dl\extractor\common.py", line 429, in extract
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpagq0np72\build\youtube_dl\extractor\youtube.py", line 1715, in _real_extract
youtube_dl.utils.ExtractorError: This video is unavailable.

Example video: https://www.youtube.com/watch?v=sCc4edfDAyI

I'm using --abort-on-error to download my subscriptions, so I don't miss any video by mistake. The current logic makes it impossible to proceed downloading of the subscription list because of a planned stream that is not yet available for playback/download.
Since it can't be downloaded, youtube-dl aborts further operation. In my opinion such planned streams should not trigger this option and be ignored - it's up to a discussion though.
Proposal: If possible, detect if it's a planned stream and if so, do not abort the download even when the option is present.
Dump files:
sCc4edfDAyI_https_-_www.youtube.com_get_video_info_video_id=sCc4edfDAyI_el=info_ps=default_eurl=_gl=US_hl=en.dump.txt
sCc4edfDAyI_https_-_www.youtube.com_watchv=sCc4edfDAyI_gl=US_hl=en_has_verified=1_bpctr=9999999999.dump.txt

Use -i instead.

-i ignores any error, the request is to ignore this specific error for planned streams.


[DOC] Add Nested function SQL documentation

Description
Copy dev authored content to new branch and perform doc review; creates nested function doc
Issues Resolved
See PR https://github.com/opensearch-project/documentation-website/pull/4308
Checklist

[X] By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and subject to the Developers Certificate of Origin.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Per communication with @anirudha, this content should go with how to work with JSON data. See the following notes:

https://github.com/opensearch-project/sql/blob/main/docs/user/index.rst all SQL / PPL detailed docs and references are here. They are auto generated per build
nested docs are here : https://github.com/opensearch-project/sql/blob/main/docs/user/beyond/partiql.rst
PPL is here : https://github.com/opensearch-project/sql/blob/main/docs/user/ppl/index.rst

looks good to me.

looks good to me.

Hi @penghuo: When I tested the query examples, I got the following error. Will you please review and let me know if this error is my user error or if we need to revise the query examples? Thank you, @vagimeli


Implement feedback on CI

Feedback is here: https://github.com/bcgov/digital_marketplace/pull/177

fix is here: https://github.com/button-inc/digital_marketplace/pull/11


Should not flushall redis DB when service API starts

This PR is to disable "flushall" Redis store when service api starts.

suggest to close this PR, PR#171 already cover this change and this change already out of date.


[Oracle Linux] 8.8 version released, please update accordingly.

Link to product page on endoflife.date
Let us know the to url of the product page on endoflife.date you found the incorrect details.
https://endoflife.date/oraclelinux
8.8 version released, please update accordingly.
Details of incorrect and correct details you have found

Thanks @cashfit for the finding. Our upstream source DistroWatch is also not tracking this release. The only mention of 8.8 is in the 9.2 entry:

Oracle Linux 8, the distribution's legacy branch, has also been updated, to version 8.8.

I have filed the PR #3153 for the update.
@captn3m0 You have added the DistroWatch automation. Do you have an idea how to handle this case in the automation?

Our upgrade automation (latest.py in this repo) never downgrades a version for exactly such cases. So we can go ahead and merge #3153.
Distrowatch has an option to submit new release information, but I've found their rules to be a bit strict around what they accept. Worth trying.


storage, raftstore: move RegionInfoProvider into raftstore

What have you changed?
RegionInfoProvider should be defined in raftstore instead of storage.
What is the type of the changes?

Engineering (engineering change which doesn't change any feature or fix any issue)

How is the PR tested?

Unit test

Does this PR affect documentation (docs) or should it be mentioned in the release notes?
No.
Does this PR affect tidb-ansible?
No

/merge

/run-unit-test


test

Task/Issue URL:
Description
Steps to test this PR
Feature 1

[ ]
[ ]

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

Current dependencies on/for this PR:

develop

PR #2444   👈

This comment was auto-generated by Graphite.


Fix MacOS example C build

Running the example cc command didn't work for me without the -ObjC option.

Thanks

This is no longer relevant. See 06957b65e97ccdccdef0a41952c7e4e68af4d781 for more information


Large volumes of liquid in puddle form seemingly never decay.

How to replicate:

Fill a bucket with water, or welder fuel if you're feeling particularly sadistic.
Spill the bucket in a high-traffic area.
Watch as the entire 40+ minute round goes by without the puddles decaying.
Steal one of the janitor's signs, put it down, then sit back and laugh.

Screenshots

FWIW evaporation has a minimum threshold (where anything below won't evaporate) and a maximum threshold (where anything above won't evaporate).

Upper threshold was a mistake.

In the case of water I thought that in the puddle overflow volume would prevent the puddle from ever going over the evaporation threshold. But seemingly some of the puddles just end up with more than OverflowVolume reagent.
Is that a bug or intentional? If not, should puddles just cap their volume at OverflowVolume or periodically attempt to re-overflow in case neighbours have evaporated?

Not sure. What happens if room is 1x1 and water canisters is destroyed? Logically that tile would become a water field without oxygen and prohibiting movements.

I'll have a look at this one, but I need to know intended behaviour first. I like the re-overflow attempt idea - this alone might solve it. If OverflowVolume and EvaporationUpperLimit are similar enough, then puddles should always either evaporate or overflow unless they are confined.

@Willhelm53 Check with Vera. From my understanding/recall it's like this:

If volume > 20u, then overflow
evaporation has upper and lower limit.
By default the evaporation lower limit is 0u i.e. always evaporate, unless some puddle that sticks around like tomato.
Upper evaporation limit was set to Puddle limit to give janitors something to work on i.e. balance reasons.
Nothing prevents systems from setting this value to a random value.

@Zumorica do you have any changes based on the comment @Ygg01 just made? No rush. Thanks Ygg for these details!

I do still want to fix this issue, but I'm waiting for the overflow algorithm change in #6280 to be merged.

this was changed i believe


Apply form group size variations to static control. Fixes #15536

Fixes #15536.
This PR adds form-control-static to blocks that apply form input group size variations to input controls. After this PR the size of form-control-static will be displayed the same way as form controls with form-control classes. The comment is also updated to match changed code.
This PR does not change code covered by automated or visual tests.
Thanks!

Competing PR: #15539.

Fix added in dbffb0b47f573097ec2a0500720accb6aeeab72e. Went with a slightly different approach to avoid unnecessary styles.

Thanks guys!


Updated nethackcocoa (0.3.4)

Tick #17075

Thank you for the contribution. It was merged directly as 68d3ea461e559eae8aca7214d59262513cbb7b0e to keep commit history cleaner. Your contribution is still credited to you.


doc: getting_started: Remove redundant and erronous doc's

The 'getting started' documentation is stating that one should set
some environment variables, but this is not necessary because the user
has already been instructed to set the variables in the
platform-specific guides.
The duplicated documentation should be removed because it is inferiour
to the original documentation. E.g. this documentation does not
describe how to permanently set environment variables. Also, it is
confusingly demonstrating how to use the SDK on Windows, but this is
not supported.
I believe that the purpose of the section is to verify that the user
has not misconfigured or misinstalled the toolchain, but this
responsibility is handled better by CMake itself.
Signed-off-by: Sebastian Bøe<EMAIL_ADDRESS>

Codecov Report

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

@@           Coverage Diff           @@
##           master    #7542   +/-   ##
=======================================
  Coverage   55.25%   55.25%
=======================================
  Files         467      467
  Lines       51673    51673
  Branches     9893     9893
=======================================
  Hits        28554    28554
  Misses      19206    19206
  Partials     3913     3913

Continue to review full report at Codecov.

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


URLLoader not working at all (except when using -Dv2)

Here is the forum topic:
http://community.openfl.org/t/urlloader-not-triggering-any-events-or-errors/1399
Basically, the URLLoader does absolutely nothing. No events, no errors, no crash, no success.
The problem can be resolved by going into legacy mode using -Dv2, which is why I am sure there is a bug somewhere in the newer URLLoader implementation.

This is resolved on the repository :smile:


SetupFakeDriver sometimes causes failure in the unit test.

          Yes, because sometimes it causes failure in the `With_Subview_Using_PosFunc` unit test. See https://github.com/gui-cs/Terminal.Gui/actions/runs/11903293490/job/33169963032. The reason is a racing condition where the `SetupFakeDriver` was resizing the terminal to (5,5) and when the above unit test is running the terminal size isn't what it's expected and corrupt the expected value.

  Failed Terminal.Gui.LayoutTests.DimAutoTests.With_Subview_Using_PosFunc [3 ms]
  Error Message:
   Assert.Equal() Failure: Values differ
Expected: 25
Actual:   20
  Stack Trace:
     at Terminal.Gui.LayoutTests.DimAutoTests.With_Subview_Using_PosFunc() in /home/runner/work/Terminal.Gui/Terminal.Gui/UnitTests/View/Layout/Dim.AutoTests.PosTypes.cs:line 647
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
   at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr)

Originally posted by @BDisp in https://github.com/gui-cs/Terminal.Gui/pull/3828#discussion_r1848887686

Another failure. Don't know if it's related.
  Failed Terminal.Gui.ViewTests.NeedsDrawTests.NeedsDraw_False_After_SetRelativeLayout_10x10 [< 1 ms]
  Error Message:
   Assert.True() Failure
Expected: True
Actual:   False
  Stack Trace:
     at Terminal.Gui.ViewTests.NeedsDrawTests.NeedsDraw_False_After_SetRelativeLayout_10x10() in /home/runner/work/Terminal.Gui/Terminal.Gui/UnitTests/View/Draw/NeedsDisplayTests.cs:line 188
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
   at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr)

Thanks for the labels. I forgot 😃

Reopening this because there is still a bug in the SetupFakeDriver.


Improve database

Make foreign keys NOT NULL
and other

Also

make primary keys NOT NULL
convert breed to an ENUM


Provides Empty Message

As Protobuf provides Emtpy, this PR provides an empty type: freestyle.rpc.protocol.Empty as generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method.
For instance:
@free
@service
trait Foo {
  @rpc def Bar(empty: Empty): FS[Empty]
}

Fixes #63

Codecov Report

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

@@           Coverage Diff           @@
##           master      #75   +/-   ##
=======================================
  Coverage   88.52%   88.52%
=======================================
  Files          12       12
  Lines         122      122
=======================================
  Hits          108      108
  Misses         14       14

Continue to review full report at Codecov.

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


Proof of concept ES6 / acorn / espree / esprima / babylon support complete

Greets @jared-stilwell et al,
I just finished a significant refactor of escomplex that fully supports ES6 along with acorn, espree, esprima generated AST.  (edit: and ES7 / all babylon features!)
Here are the two repos:
https://github.com/typhonjs-node-escomplex/escomplex
https://github.com/typhonjs-node-escomplex/escomplex-core
I split off all AST processing to escomplex-core and removed all external dependencies including node so escomplex-core can be used anywhere including the browser.
escomplex has the same API, but I switched things to espree as it's a way better parser than esprima and conformant to the ESTree spec which esprima is not.
Don't fret though as I resolved all of the issues in supporting acorn / espree / esprima and escomplex-core runs all test suites against these 3 parsers. I also added a thorough test suite for ES6 which is almost twice as large as the core module test suite.
For now you can use the following in package.json to test things out:
  "dependencies": {
    "escomplex"<EMAIL_ADDRESS>  },

or just for the core AST processing:
  "dependencies": {
    "escomplex-core"<EMAIL_ADDRESS>  },

@jared-stilwell I'd be glad to do a PR once you get to check things out.

@typhonrt After doing a casual walk-through both projects and gathering some anecdotal test runs against a couple test cases, this is definitely an improvement on a number of fronts. While initially, I was a skeptical of the split between the escomplex and escomplex-core, the code organization is surprising pleasant and its clear from recent activity on this project that this fills a need.
I did run into a bit of a snag with the spread operator when trying to run against some of the react source code, but this is such small potatoes compared to the huge boost in functionality your changes provide, that I hesitated to even mention it.
Nice work. I'm more than happy to get these changes merged in.
One possible way forward I can see is to simply absorb your escomplex-core project into the escomplex org, then PR escomplex to leverage it and remove the unnecessary code. Let me know what you have in mind.
Cheers 👍

Right on.. I did put a bit of time into getting it all working and dare I might say I have a thorough knowledge of ES6 at this point and the vagaries of esprima vs acorn / espree. ;)
I'll take a look at the React source code example as supporting the spread / rest forwarding of the name was tricky as I used the assignableName function / field for that as can be seen here and here. I modified a bit how assignableName works with Identifier. The React case pointed out looks like a trickier test case / example.
Re: >"One possible way forward I can see is to simply absorb your escomplex-core project into the escomplex org, then PR escomplex to leverage it and remove the unnecessary code. Let me know what you have in mind."
Again stepping on eggshells per se I'm certainly fine with integrating this effort into any separate escomplex org as I just want to see things move forward as a range of depending projects from Plato to XXX will now be able to support ES6, but also would like to extend the offer to join the larger TyphonJS community. The main impetus behind what I'm putting together with TyphonJS is to support a federated many org / repo offering with thorough tooling and production ready efforts. IE escomplex could live on in the typhonjs-node-escomplex org. This org would host escomplex, escomplex-core and complexity-report and only this. I have no problem making you an owner of this org with future maintenance guided by your efforts. IE you'd still be in control of the NPM module publishing and everything pertinent to releases. I'm drawing inspiration for TyphonJS from the zeroMQ process. I certainly would be honored to have escomplex join TyphonJS and be the first independently driven org.
A potential benefit of hosting things with TyphonJS is that I'd take the time to further work on escomplex to convert it to ES6 and also add copious amounts of inline documentation via ESDoc. One of the major difficulties / barriers for anyone to work on escomplex is that you really have to dig into the source code and understand it as there isn't adequate documentation. I can imagine this has been one of the stalling points of getting others to work on the code base. In the process of converting to ES6 and full integration with the TyphonJS process is that I'd take the time to impart all of the internal knowledge that I have from working with escomplex into thorough inline documentation. I've been doing a lot of work with ESDoc to provide exceptional documentation for any project, but all TyphonJS efforts benefit from integrated tooling and instant publishing of documentation when a repo is committed to is soon going to be available.
All that said I'm fine with getting a separate escomplex org setup and fully functioning with the existing efforts or fully integrate escomlex with your direct and continuing involvement into TyphonJS if that makes sense.

@jared-stilwell so I have an answer regarding the React test case that you pointed out.
It turns out that this is not ES6 and is an ES7 stage 2 proposal. Acorn which also backs espree only supports stage-4 (finalized) functionality for ES7. Even setting the ecmaVersion to 7 for acorn it doesn't parse this particular use case properly.
Given that the React codebase is run through Babel this is why it eventually resolves to valid JS. In particular it uses babel-plugin-transform-object-rest-spread in .babelrc.
If you can find any other ES6 specific test cases where things fail do let me know. Another general concern is to check all the new ES6 syntax to make sure I got the Halstead operator / operand and logical line of code values correct for all nodes.

Well escomplex-core now also supports babylon and the differences between ESTree AST and Babylon AST at least for the current test suites. I'd say things are rather comprehensive at this point.

Allright.. So after some basic testing I switched the default parser in escomplex to babylon with all plugins available (jsx, flow, etc. etc.). In escomplex-core I created an initial Babylon test suite, but it is far from complete. However I did test object spread / rest and an example based on the React example @jared-stilwell originally mentioned above and a basic flow typing test.
It is suggested that you delete your node_modules directory for escomplex and reinstall via npm install to make sure you pull in the latest escomplex-core version from Github.
Well... After a thorough testsuite for ES7 / Babylon is created I think we have a winner here and ready for v2.0! ;)

@typhonrt very cool. I'm open to rolling this under the umbrella of typhonjs. My first priority is getting this project to a state where it is easier to use and easier to contribute to. Your invitation seems to accomplish both of these. I'm not sensitive about holding on to maintainership of this project, especially since my own contributions to the project since taking the mantle from Phil Booth have been relatively minor. Having said that, I'm glad to continue to contribute to the project and direct things to the extent that my involvement is helping to move things forward.
Currently these projects are published under the MIT license. Do you see this changing with the migration of the project?

@jared-stilwell I appreciate the inclination to move things forward for sure. Your message above has freed me to further modify the codebase towards what I consider the optimum solution and hopefully creating an environment for future evolution.
Since your post I have modified the walker functionality to traverse all keys and inverted the children trait resolution to ignoreKeys removing the connection between trait data collection and node traversal along with a reshuffling of trait resolution switching assignableName before ignoreKeys has allowed the syntax definitions to be further simplified. My goal at this point is to actually remove the walker code in favor of estraverse and further rewrite the syntax definitions such that assignableName can be removed entirely as estraverse supports processing w/ (node, parent) such that the syntax definitions can remove the necessity of  assignableName in the old walker code. At this point the aim is to support a plugin system where AST to node resolution is flexible instead of hardcoded.
Yep... A bit architecture astronaut territory, but where I'm headed is making escomplex support a plugin architecture for defining syntax definitions and generic AST node processing along with pluggable report generation. I think by Monday things will be more apparent.
In regard to license migration all TyphonJS modules are published under the MPLv2. I'll certainly make sure the license recognizes the MIT origin of this effort. IE I see no problem in adding all existing contributors to the AUTHORS.md. My goal is to make escomplex concise and extendable for 3rd parties however they see fit, but maintain a solid core bit of functionality.

+1
I've actually just commented on an old issue saying that there should be a way to provide the ast instead of the path directly and the escomplex-core accomplishes just that.

For those that want to track the new escomplex / escomplex-core progress check out this issue:
https://github.com/typhonjs-node-escomplex/escomplex-core/issues/2
Up next... plugins...

@typhonrt it would be cool to have something like the citgm tool for testing the impact to downstream consumers of escomplex. This could be a nice way to measure impact to consuming projects, especially during the current rewrite process.

@jared-stilwell yeah.. That seems like an interesting tool in general that I'll take a look at for escomplex and the rest of the typhonjs node modules. For v2 I assume there can be a few small API changes. I saw  a couple of leftover TODO notes about supporting asynchronous / Promise based functionality which is easily possible when switching the code to ES6 for instance. After the next full session tomorrow things will be modularized w/ plugin infrastructure and converted to ES6 and documentation started.

@jared-stilwell well... I've made some major progress.  Mostly things have been converted to ES6 except for escomplex which will be addressed soon. One more coding session and I should have it all done.
One thing I'm considering since ES6 classes can be supported is to create a class scope to gather metrics for classes and their methods and run aggregate stats on classes instead of just independent functions. Any thoughts on this?

@typhonrt I'm having trouble getting started with any of the projects in the typhonjs-node-escomplex org due to the prepublish hooks which involve transpilation. I've filed an issue on the escomplex-core-commons project which provides the details of the error. However, I'd like to pull back even further for a second.
I question the prudence of using transpiling code that is only intended for node. Even when everything works, it introduces unnecessary heft and complication to the workflow. If we move forward with this as it is, I'm concerned it will be unnecessarily cumbersome to work with, especially for beginners.

Yeah.. I posted a note. The development TyphonJS modules are designed for Node 5+ / NPM 3+ and the flat package hierarchy. In the case of the prepublish script it doesn't need babel-node, but the other scripts won't work from testing to building either as Babel will be tucked away under various sub-modules instead of at the top root path if not using Node 5+. As mentioned in the note this is only a development concern as the published modules will work on any version of Node.

That makes sense. Thank you for clarifying. I'm still having a hard time understanding the need for Babel here. I get why it feels good to use the latest language features, but the end result is that the project becomes much more complex to work with.
On an unrelated note, I wanted to get your take on the use of the MPLv2. I'm curious which outcomes this takes into account that the existing MIT license doesn't provide for? On balance, the MIT is drastically more straight-forward than the MPLv2. This seems to be of particular value when deciding which open source projects to count as dependencies.

Ultimately I think you need to reserve final thoughts as I'm mid-stream in the refactor. A week from now (or less) things will be very stable.
Regarding Babel it allows the module to be released and work on any Node version. Using ES6 is not so much about the feel good experience as it indeed does provide additional code clarity and detailed inline documentation via ESDoc. TyphonJS is all about providing a standardized set of tools applied across all repos / modules. This is what typhonjs-npm-build-test accomplishes. I'll be doing an update soon to it soon as well streamlining things further. The process is standardized and is the same across all repos. I've already released 12+ ES6 based NPM modules. One of the nice things with the NPM scripts is for say the prepublish one which stops publishing if eslint fails, tests fail and auto-builds the transpiled code before publish is completed.
For an example of where ES6 has simplified things in escomplex is to look at the trait / syntax definition code. Here is PluginSyntaxESTree. You can see that it only contains member methods that clearly provide the syntax definitions. Extending AbstractSyntaxLoader which provides the plugin hook for automatically loading the definitions. More so it supports extended child inheritance such that PluginSyntaxBabylon which is a superset of ESTree syntax simply can inherit from PluginSyntaxESTree and everything is automatically loaded.  Sure you could do this in CJS, but it would be messier in general.
It would be one thing if I was just adhoc adding Babel or haven't had experience publishing ES6 NPM modules. Admittedly things are a little wonky right now when it comes to referencing multiple Github linked modules in the current status of the rewrite since these modules are not published on NPM. For instance the /dist or transpiled code needs to be checked in. Once these modules are published on NPM that is all handled automatically by the build scripts and is not checked in.
What IDE do you use? I use WebStorm and highly recommend it. All of the linking between NPM modules source code is handled transparently in WebStorm.
Now as far as ESDoc is concerned I've been writing a lot of plugins for it including a forthcoming escomplex plugin. Currently I have plugins that integrate JSPM managed packages across repo / modules. Once I finish escomplex refactor I'll be finishing the NPM version of the plugins. For a taste though here is a plugin that completely replaces the left hand navigation for an enhanced JSPM aware version (click JSPM Managed source to reveal / also context click to jump to linked code on Github) and even D3 interactive dependency graphs (JSPM packages for now / context click on nodes to jump to NPM or Github repo!). Again I'll have NPM versions soon after the escomplex refactor. The documentation generated will span all of the escomplex modules included as dependencies including setting up all the inheritance across modules.
Another thing that I'll be finishing soon is automatic documentation generation on commit via Travis CI for all TyphonJS modules (and anyone else who wants to do the same) which can then be simply pulled down on a docs web site to update online documentation.
Basically give things a week or two...

Regarding MPLv2 my opinion is that it works really well for efforts that are well defined and reach production quality release status. Changes by the license should be upstreamed to the authoritative version. However, consider the plugin mechanism being added to the escomplex refactor. Anyone can create 3rd party plugins that are licensed however they want and completely replace the default plugins. MPLv2 doesn't limit situations in that regard. In fact all the functionality of escomplex refactor is driven by plugins. Another general aspect as far as TyphonJS is concerned is that I'm putting in a considerable amount of time to polish everything from documentation to functionality of all modules involved (still forthcoming on some of this). I haven't been keeping a detailed hourly report for the time I am putting into escomplex, but it's a bit at this point. I'm going to see it through and finish the job quickly and efficiently at production quality levels before I work on anything else. In many ways MPLv2 respects the effort to get "finishers" involved in the process. IMHO MIT fits well for efforts that are openly exploratory and have adhoc contributors over time. Again these are just opinions. MPLv2 gives me the peace of mind to spend the time to open source quality code at production levels as I'm self-funding all TyphonJS efforts. With the MIT license all of that effort could be immediately subverted by any 3rd party for any reason. And after all it's not like I'm forking escomplex adding a single line of code and changing the license. I'd love to see escomplex usage explode when v2 hits and remain the authoritative tool for JS complexity reports. If anyone wants to modify it then create a plugin and do what thou wilt!

It is obvious you have invested substantial time, and my intention is absolutely not to disrespect the level of effort and skill involved.
My priority remains ensuring ease of use and contribution for the escomplex project. The decisions to require a transpilation step and to exclude the current LTS version of Node for development purposes represent barriers to this end. What tooling gives you in enhanced capabilities, it tends to take away in the cost to setup and contribute to a project. Folks should be free to use any version of node that escomplex supports for development purposes as well.
This seems to betray some fundamental philosophical differences between us and what style of project we are trying to cultivate. It would seem that this will still be the case once the code has settled a bit more. Perhaps I was too apologetic initially and gave the wrong impression. I'd love nothing more than to accept changes that extend the current project to support the full language standard and provide more flexibility to consumers of the project. But, I think we can do this while preserving the relative code style and without introducing unwarranted complexity.
You seem to have a very clear vision for the project and for the rest of typhonjs. My recommendation, given our differences in style and project ergonomics, is for you to release your work under a scoped module in npm. This will give folks a drop-in replacement for escomplex, which is still sorely needed. However, it provides for the possibility that the invaluable work you've done here can be ported into the existing escomplex codebase without fundamentally changing the requirements or license of the current project. Is it a great thing to fork the project? Perhaps not, but I think it leads to a place where folks have a choice in which style of project they want to use and contribute to without one necessarily needing to squelch the efforts of the other.
I realize this is a bit of a regression from my early enthusiasm. I am absolutely interested in where your version of escomplex is headed. After giving it some thought, I'm convinced the move to the typhonjs umbrella is not going to work out.

Well that is a bummer and a bit arbitrary on your part especially considering development to be possible on all versions of Node. You are aware that v6 is going to be LTS in 4 months right?
You've made a snap decision before I've even finished and I indeed asked you to wait a week before expressing doubts. There are easy answers to all of your newly expressed concerns and I'd be glad to take the time to assuage the issues at hand.
I will finish my effort and hope that you might come around once you see the finished work. You do understand that anyone creating a plugin for my version of escomplex can do so with any version of Node right?
I'll withhold my own judgement of this situation for a week or two though I can't guarantee what my perspective will be at that time if no further consideration is granted. I can tell you that I'm not pleased with the arbitrary switch in opinion without due consideration regarding the finished effort first.

@jared-stilwell So given all those "copy / duplicate issues" you just posted that are already handled in my efforts I assume you have no intention of providing additional consideration? I'm all for trying to make something work together and it just takes a minor compromise on your part that I'm sure would be accepted by a majority if actually polled. At the very least you should consider what this conveys to anyone potentially contributing to escomplex or any repo you maintain. Feel free to @ mention any contributor to escomplex to involve them in the discussion. I'm still open to discussing the matter, but if you're not just drop a note here; I suppose a day or two of silence will also be counted as an appropriate negative response.

@typhonrt As to the matter of the escomplex project joining the typhonjs community, I ultimately decided to decline. If the further consideration you are looking for is whether to wholesale merge your rewrite of the project, then I must decline that as well.
Having said that, your rewrite of the project is deeply instructive to escomplex in its current state and demonstrates some patterns that are worth adopting. As I see it, there are only two paths forward: 1.) Accept your fork of the project as the new canonical base of development. 2.) Identify an iterative development path forward based on the best parts of your fork.
Early on in our discussion, I was optimistic about the prospects of the first option. With a little time and reflection, I became convinced that this was not necessarily in the best interest of the project, but there would be no harm in having the project be forked. If there is as much interest in the features your fork provides as it seems, I have no doubts it will do well. Meanwhile, this will free up this escomplex project to glean some of the best patterns as it iterates into features like modern syntax support. The second option simply seems better for everyone.
And so I'm now working on documenting what a possible path forward looks like, based directly on reviewing your work. This is why they seem like "copy /duplicate issues". They absolutely are. :)
My goal is not to ignore or undermine your efforts, but simply to try to get a backlog of issues that are reasonably scoped and lead to place where people can use and contribute to escomplex more easily.
I've tried to be as forthcoming as possible and I hope you'll consider releasing your work as a fork of escomplex. I think the javascript community will benefit from your experience and hard work.

Ultimately the reason why escomplex is not picking up significant momentum / developer community is that no one really wants to work on it versus simply consuming a working version of it. What I'm getting at is that escomplex doesn't need an extended developer community itself; it's a fundamental tool that just needs to work. The vibrant developer communities that form around escomplex are downstream from the core tool itself. To that end a significant possibility once I publish my version is that any / all downstream consumers simply switch over as few if anyone actually cares how escomplex is internally structured or if it's written in idiomatic ES6 or CJS or has a development dependency on Node 5 & Babel as that doesn't matter to consumers.
Besides a counterargument can easily be made insofar that adopting modern tooling with thorough inline documentation / online docs and a plugin architecture is more likely to attract developers. The lack of code documentation in your version is a severely high barrier of entry for anyone to join in development.
I was clear in stating what I was going to do as part of a refactor and you agreed and even stated "I'm not sensitive about holding on to maintainership of this project". Having done the work and then being rebuffed for IMHO what amounts to empty reasoning; you can call it philosophical if you want is what it is; seems pretty "sensitive" to me... What rubbed me the wrong way is that you didn't try to discuss pros / cons or be inclusive or wait to evaluate the finished result. You made a huge flip flop. I would have been amenable to working within the constraints you now are enforcing if things were transparent through the whole process. To build a successful community it's all about the people involved and very few if any folks like myself will likely be showing up to contribute here once a next generation escomplex version is out. Few if any will flock to a version that is far behind and exists only because it restrictively enforces old coding styles for reasons.
Besides the idiomatic approach I've developed for ES6 NPM modules is actually fairly conservative in regard to adopting modern tooling (compared to say including TypeScript or adding JSPM / SystemJS / Browserify / Webpack). To that end if you want to enforce your rules and be sensitive in that regard I recommend that you extend the contribution guidelines to be very explicit about what is allowed and what isn't (ala Node versions for development / no Babel / ES6) and be as transparent as possible in sticking to them in all communication in regard to what you consider appropriate for outside contributors. Also leading by example by actually authoring several of the core enhancements / features that you are posting shows your commitment to your version. IE don't sit back and simply wait to micro-manage other contributors as that is not going to go over well in general. No one comes here excited to join a "pseudo-inclusive"  yet in reality restrictive project with a lacking developer community.
I'll be publishing my fork later this week. Do mull over the conjecture that you are fighting the wrong battle insofar as to what type of project escomplex is at it's core.  1) is still an option for a few days.. :) I guess you can tell I really do not like unnecessary forking despite ruffled feathers.
To that end though things remained cordial for the most part... I did pick up a few things here and there like learning how cool snyk is (which I integrated into typhonjs-npm-build-test) and your suggestion to take a look at citgm is pertinent and welcome. Best of luck...


**my-notes

[X I have read freeCodeCamp's contribution guidelines.
[X] My pull request has a descriptive title (not a vague title like Update index.md)
[X] My pull request targets the master branch of freeCodeCamp.
[X] None of my changes are plagiarized from another source without proper attribution.
[X] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Please edit this to be in the tone of a guide article rather than an informal "my notes" section, which is likely to only confuse people.

Thank you for opening this pull request.
This is a standard message notifying you that we’ve reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you.
Thank you and happy coding.


Installation Error

Hii @acadTags
For using Rare-disease-identification I tried to install Dockerised SemEHR .
At docker build step I am stuck
docker build -t semehr/core - < Dockerfile
The build start well but it fails for the following command (line 43 in the Dockerfile):
RUN cd /opt/gcp/gcp-2.5-18658 && ant
Please help me out !!

Hi Siddhijain16,
Thanks for your question. I see that you have a post in https://github.com/CogStack/CogStack-SemEHR/issues/2#issuecomment-1217528616 too. Hope there will be some reply on the issue.
We actually installed the Minimised SemEHR version to process the MIMIC-III radiology reports, maybe it is worth having a try if that helps.
Best regards,
Hang


chore: run jest-circus tests on GH Actions

Summary
Faster

Test plan
Green CI

Interesting that the leak test fails... It passes locally and on circle. Might be a timing issue? It failed twice in a row, tho


M3U8_Queue Unknown Channel - When Connecting to DaddyLive

Hello! Ultra noob here, having some trouble with connecting to the DaddyLive plugin.
The goal is to run these channels through Jellyfin, which I was successful with XUMO, and the Plex Channels, but I'm getting an error whenever I attempt to open a stream. I've attempted from both VLC and Jellyfin.
In Terminal, I see:

While in the Cabernet UI, I see this on the Tuner (The channel is different from the one above, as the pictures were taken at different times, same this happens though.)  :

Would definitely appreciate the help! The application has been working well so far with other providers.
Let me know if there's anything else I need to provide.
Cheers.

Posted in wrong repo did you check dlhd website because there were a number of channels that failed to load due to a manifest error. They have now been fixed
Issues for dlhd are
https://github.com/cabernetwork/provider_video_daddylive
Also make sure you are using the channel list from
https://github.com/cabernetwork/provider_video_daddylive/issues/22

Duplicate https://github.com/cabernetwork/provider_video_daddylive/issues/22


Support for Slash Commands and Interactions

Discord will be adding slash commands soon. Documentation PR is here already.
Discordeno should implement that when its out.
To-Do:

[x] Events
[x] Controllers
[x] Handlers
[x] Structures
[x] Types

#248 is merged into next; slash commands are usable using next branch.


Adding Deathbringer by Dungeoncraft, made with permission

Submission Checklist
Required

[x] The pull request title clearly contains the name of the sheet I am editing.
[x] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[x] The pull request makes changes to files in only one sub-folder.
[x] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

New Sheet Details

The name of this game is: Deathbringer

The publisher of this game is: DungeonCraft

The name of this game system/family is: Dungeons & Dragons

[x] I have followed the Character Sheets Standards when building this sheet.

[x] This sheet has been made on behalf of, or by, the game's publisher.
[x] This game is not a traditionally published game, but a copy of the game rules can be purchased/downloaded/found at: https://www.drivethrurpg.com/product/396879/Deathbringer-RPG
[x] This sheet is for an unofficial fan game, modification to an existing game, or a homebrew system.

Changes / Description

Character Sheet Info Roll20 Internal Use only.

Hi @jscranton2004
Could you please fill out this section of the PR body:

The name of this game is: (i.e. Dungeons & Dragons 5th Edition, The Dresden Files RPG)
The publisher of this game is: (i.e. Wizards of the Coast, Evil Hat)
The name of this game system/family is: (i.e. Dungeons & Dragons, FATE)

Done! Sorry I missed that!


Handling of response of email id creation.

Describe the bug
Email not created but assigned to telegram user.
To Reproduce

Expected behavior
Either end to end flow should work or it should roll back.

@dcRUSTy thanks for pointing this out. I have already added this issue in #5
The flow is different but the underlying logic is same.  I will work on this fix quickly and will update on the issue as well.
I will keep this issue and mark the other one as duplicate. :+1:

Fixed in 6819a7648f917c8b428208560772929d9f6a2d95. Yet to deploy this.

@dcRUSTy  Deployed as well, I request you to please perform a single delete operation  with /delete<EMAIL_ADDRESS>once, and then you wont face this issue again. :)
Thanks again for pointing this out.


Connection string doesn't support username and password nats://user:password@host:port

node-nats should support the same connection string as NATS.  Please ignore.
Code looks good! :+1:


[bug] screenpipe self signed certs issue - tls connection init failed

describe the bug
brief description of the bug.
to reproduce

Install screenpipe via homebrew
Start screenpipe via command line

expected behavior
Seeing the following error:
2024-11-21T19:08:28.461123Z ERROR screenpipe: continuous recording error: request error: https://huggingface.co/openai/whisper-large-v3-turbo/resolve/main/config.json: Connection Failed: tls connection init failed: invalid peer certificate: UnknownIssuer

system info

os: 15.1 (24B83)
screenpipe version: 0.1.98

additional context
It's related to a self signed certificate. The certificate is trusted in the MacOs KeyChain. However, it is not recognized by screenpipe. Is there a way to let screenpipe trust this self signed cert?

are you in china or behind firewall?

Located in North Americas. I am on a corporate laptop so behind VPN/firewall stuff.

Update: If I stop the corporate VPN (GlobalConnect), the problem is gone.

@louis030195 Any updates on this, it would be great if we had system keychain/certificates imported by default. I believe currently I'm seeing this same issue due to ZScaler on our corporate machines.

some ideas from AI:
use reqwest::Client;
use std::time::Duration;

pub fn create_client() -> Result<Client> {
    let client = Client::builder()
        .timeout(Duration::from_secs(30))
        .use_system_proxy() // Use system proxy settings
        .tls_built_in_root_certs(true) // Use system root certificates
        .build()
        .context("failed to create http client")?;

    Ok(client)
}

@joshuaauger
i'm not sure where is the problem, should i send a PR to huggingface or is it something in our CLI code?
not familiar at all with this
https://github.com/huggingface/candle/issues/2668
trying to figure out

@louis030195
I'm no rust developer, but I think rustls doesn't use the system certificates but native-tls does.
something similar to this:
#38

https://github.com/huggingface/hf-hub/blob/ac22200ea0b5af4d8c362f699be0340647b19060/Cargo.toml#L44

https://github.com/huggingface/hf-hub/issues/56

/bounty 150

@neo773
I'm on MacOS, trying to follow the build guide but I don't see any changes in behaviour. What do I need to do to build with your changes?

I see this message from screenpipe-audio, maybe I'm not building correctly:
[2024-12-16T01:53:04Z DEBUG rustls::client::hs] ALPN protocol is None
Error: request error: https://huggingface.co/distil-whisper/distil-large-v3/resolve/main/model.safetensors: Connection Failed: tls connection init failed: invalid peer certificate: UnknownIssuer

Caused by:
    0: https://huggingface.co/distil-whisper/distil-large-v3/resolve/main/model.safetensors: Connection Failed: tls connection init failed: invalid peer certificate: UnknownIssuer
    1: invalid peer certificate: UnknownIssuer

https://github.com/mediar-ai/screenpipe/pull/986
Added a PR, this was required for me to get past the certificate issue, not sure why the patch alone wasn't working, but I needed the features in the workspace dependencies, added the workspace = true to server, and added the feature to core, didn't work without all of the changes
Not sure if anything else broke, need someone to verify PR and do a full test.

@louis030195 let me know if we can run a test build with the changes!
Thanks!

Yes, the issue was other workspace packages had conflicts with feature flags.
I couldn't really test it within screenpipe as I did not have the same setup as you so I tested the changes within my fork and it worked fine .
Seems to be working now.

Awesome!
Thanks for confirming @neo773.

@joshuaauger @zy31415 is it working now?

It should be once the new build has these. My test build had some other issue unrelated but the certificate warnings were gone. Sent from my iPhoneOn Dec 19, 2024, at 7:33 AM, Louis Beaumont @.***> wrote:
@joshuaauger @zy31415 is it working now?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>


Userchrome not loading

Followed the instructions exactly and restarted Firefox - but the stylesheet doesn't load. Any thoughts as to why?

Firefox is a bit weird with their version stuff, pls check if you created the chrome folder in the right place 🙏

Oh, I see now. The chrome folder you created need to be inside of the version folder. Just move your chrome to that folder on top of it and restart your Firefox.

Place the chrome folder in the Profile Folder located at about:support


[MC736429] the global Microsoft Intune PowerShell application (client) ID based authentication method is being removed.

Today I was informed from our company EntraID Admin, that the Intune PowerShell application ID (d1ddf0e4-d672-4dae-b554-9d5bdfd93547) will be removed by Microsoft?
Here the Message:

As mentioned in MC721851, last year we announced a new Microsoft Intune GitHub repository (https://aka.ms/Intune/Scripts-blog) based on the Microsoft Graph SDK-based PowerShell module. The legacy Microsoft Intune PowerShell sample scripts GitHub repository is now read-only. Additionally, starting on or after April 1, 2024, due to updated authentication methods in the Graph SDK-based PowerShell module, the global Microsoft Intune PowerShell application (client) ID based authentication method is being removed.
[How this will affect your organization:]
If you are using the Intune PowerShell application ID (d1ddf0e4-d672-4dae-b554-9d5bdfd93547), you will need to update your scripts with a Microsoft Entra ID registered application ID to prevent your scripts from breaking.
[What you need to do to prepare:]
Before April 1, 2024, update your PowerShell scripts by:
Creating a new app registration in the Microsoft Entra admin center. For detailed instructions, read: Quickstart: Register an application with the Microsoft identity platform (https://learn.microsoft.com/entra/identity-platform/quickstart-register-app). Update scripts containing the Intune application ID (d1ddf0e4-d672-4dae-b554-9d5bdfd93547) with the new application ID created in step 1.

Are you aware of theese changes?

We got the following announcement in our intune tenant:
We've detected a Microsoft Intune PowerShell script issue in your environment User impact: If action isn't taken, PowerShell scripts may break. Current Status: If you are using the Intune PowerShell application ID (d1ddf0e4-d672-4dae-b554-9d5bdfd93547), you will need to update your scripts before May 6 with a different Microsoft Entra ID registered application ID to prevent your PowerShell scripts from breaking. Microsoft has replaced the GitHub repository using the old application ID d1ddf0e4-d672-4dae-b554-9d5bdfd93547 with a new repository...

It is possible to use your own application by doing:
Connect-MSIntuneGraph -TenantID $TenantID -ClientID $ClientID -ClientSecret $ClientSecret
I am not sure on the least access permission but the one I tested this with had:

DeviceManagementApps.Read.All
DeviceManagementApps.ReadWrite.All
DeviceManagementManagedDevices.Read.All
DeviceManagementManagedDevices.ReadWrite.All

It appears that Connect-MSIntuneGraph is failing on most tenants now.
I've tried creating an application as per here but it fails with Forbidden errors despite seemingly having the same permissions.
This is significantly impacting us as it has broken all our Intune application deployments.
VERBOSE: POST https://graph.microsoft.com/Beta/deviceAppManagement/mobileApps
WARNING: An error occurred while creating the Win32 application. Error message: UnknownError: {"ErrorCode":"Forbidden","Message":"{\r\n  \"_version\": 3,\r\n  \"Message\": \"An error has occurred - Operation ID (for customer support): 00000000-0000-0000-0000-000000000000 - Activity ID: 9ac8ae62-7e74-4777-9d37-17aeaf202201 - Url: https://fef.msuc03.manage.microsoft.com/AppLifecycle_2404/StatelessAppMetadataFEService/deviceAppManagement/mobileApps?api-version=5024-03-08\",\r\n  \"CustomApiErrorPhrase\": \"\",\r\n  \"RetryAfter\": null,\r\n  \"ErrorSourceService\": \"\",\r\n  \"HttpHeaders\": \"{\\\"WWW-Authenticate\\\":\\\"Bearer realm=\\\\\\\"urn:intune:service,9225b241-44e1-44a8-8bfe-c10e39177505,3e9c57b9-808d-4aa0-9500-4b2d369279e7\\\\\\\"\\\"}\"\r\n}","Target":null,"Details":null,"InnerError":null,"InstanceAnnotations":[]}

WE have the same issue, that Microsoft Intune Powershell app registration has been revoked my Microsoft

Create new app registration or use the "new default" app registration. Lookup the client id from appregistration. With the same settings as the revoked one.
Connect to Microsoft Intune Graph
Connect-MSIntuneGraph -TenantID "yourtenant.onmicrosoft.com" -ClientID "yourappregistrationid"
Then you can connect again.

It is possible to use your own application by doing: Connect-MSIntuneGraph -TenantID $TenantID -ClientID $ClientID -ClientSecret $ClientSecret
I am not sure on the least access permission but the one I tested this with had:

DeviceManagementApps.Read.All
DeviceManagementApps.ReadWrite.All
DeviceManagementManagedDevices.Read.All
DeviceManagementManagedDevices.ReadWrite.All

Thanks for this! We are back up and running again.
I can confirm that using an application with only:

DeviceManagementApps.ReadWrite.All

I was able to create an app, get list of all apps, supersede a previous version, and assign the app to group's whose IDs I had passed.
I would assume that if you want to look up groups and members you would need to add Directory.Read.All
Other functions may need DeviceManagementManagedDevices.Read(/Write).All if your script performs other actions - but I think for this module at least, DeviceManagementApps is enough.

Confirming that a new application with permissions assigned as Application gives me the same access as previously.
NOTE that many commenters have specified to duplicate the existing Microsoft Intune PowerShell application, but this has permissions assigned as type Delegated which gives a token but does not work.
I'm still finding that Add-IntuneWin32App fails with
WARNING: Failed to finalize Azure Storage blob upload. Error message: The given key 'Content-Type' was not present in the dictionary.

but switching to PowerShell 5.1 it works.

Working for me fine with 5.1

Same. Connect-MSIntuneGraph fails with Application with identifier 'd1ddf0e4-d672-4dae-b554-9d5bdfd93547' was not found.  This has broken our deployments, so we are unable to deploy until it gets resolved. From what we gather, Connect-MSIntuneGraph has a reliance on the above ID which was published years ago by Microsoft as a kind of Powershell sample code.  And now Microsoft has blocked this identifier.
The workaround seems to be for administrators to create an application.  I tried a few things but couldn't get it working.  If someone can document the steps that would be very helpful.  Ideally, the codebase should include a method for creating the application with the 'correct' permission, if not in-line, then at least as a utility function.

Run my script here which will create an Azure application called "IntuneWin32App" and add the permissions...
DeviceManagementApps.ReadWrite.All and DeviceManagementConfiguration.ReadWrite.All
You'll need the PowerShell module Microsoft.Graph installed to run it successfully

It works for most parts, but when checking or changing the Category I still get an error, so we probably need more API Permissions
WARNING: Graph request failed with status code '401 (Unauthorized)'. Error details: UnknownError - {"ErrorCode":"Forbidden","Message":"{\r\n  \"_version\":  3,\r\n  \"Message\": \"An error has occurred - Operation ID (for customer support): 00000000-0000-0000-0000-000000000000 - Activity ID:  d6e7b4ab-0199-45a0-98ee-22248f2117e3 - Url:  https://fef.msub07.manage.microsoft.com/AppLifecycle_2404/StatelessAppMetadataFEService/deviceAppManagement/mobileAppCategories?api-version=5024-03-08&$filt er=displayName+eq+%27Web+Browsers%27\",\r\n  \"CustomApiErrorPhrase\": \"\",\r\n  \"RetryAfter\": null,\r\n  \"ErrorSourceService\": \"\",\r\n   \"HttpHeaders\": \"{\\\"WWW-Authenticate\\\":\\\"Bearer

I also ran into this as described at Plan for Change: Update your PowerShell scripts with a Microsoft Entra ID registered app ID. I found that the only MS Graph permission required for my use case was
DeviceManagementApps.ReadWrite.All, but that application permissions were required. Delegated permissions did not work.

I have also just encountered the problem, how do I have to set the app so that it works again?
I have created an app and given it the DeviceManagementApps.ReadWrite.All Application api permission, but I still get error messages when executing the commands:
Get-IntuneWin32App -DisplayName "7-zip"
WARNING: Graph request failed with status code '401 (Unauthorized)'. Error details: UnknownError - {"ErrorCode":"Forbidden","Message":"{\r\n  \"_version\": 3,\r\n  \"Message\": \"An error has occurred - Operation ID (for customer support): 00000000-0000-0000-0000-000000000000 - Activity ID: f48ecac5-fe6b-4b5f-a40e-a64e60503fe0 - Url: https://fef.amsub0502.manage.microsoft.com/AppLifecycle_2405/StatelessAppMetadataFEService/deviceAppManagement/mobileApps?api-version=5024-03-08&$filter=isof(%27microsoft.management.services.api.win32LobApp%27)\",\r\n  \"CustomApiErrorPhrase\": \"\",\r\n  \"RetryAfter\": null,\r\n  \"ErrorSourceService\": \"\",\r\n  \"HttpHeaders\": \"{\\\"WWW-Authenticate\\\":\\\"Bearer realm=\\\\\\\"urn:intune:service,9225b241-44e1-44a8-8bfe-c10e39177505,3e9c57b9-808d-4aa0-9500-4b2d369279e7\\\\\\\"\\\"}\"\r\n}","Target":null,"Details":null,"InnerError":null,"InstanceAnnotations":[]}
WARNING: Query for Win32 apps returned an empty result, no apps matching type 'win32LobApp' was found in tenant

To use the IntuneWin32AppAssignment features, you also need the Group.Read.All permission

Run my script here which will create an Azure application called "IntuneWin32App" and add the permissions... DeviceManagementApps.ReadWrite.All and DeviceManagementConfiguration.ReadWrite.All
You'll need the PowerShell module Microsoft.Graph installed to run it successfully

There is no script ;)

@twelch-ricohnz May you able to share your script again, please? It is not available anymore.

@aCID-sLAM , @alexhass
Here is a basic version of it. It will create an application called IntuneWin32App with the correct permissions assigned.
Connect-MgGraph -Scopes "Application.ReadWrite.All, Directory.Read.All" -TenantId (Read-Host -Prompt "Enter Tenant ID or FQDN")
$NewApp = New-MgApplication -DisplayName "IntuneWin32App"
$BodyParams = '{
    "requiredResourceAccess": [
      {
        "resourceAppId": "00000003-0000-0000-c000-000000000000",
        "resourceAccess": [
          {
            "id": "78145de6-330d-4800-a6ce-494ff2d33d07",
            "type": "Role"
          },
          {
            "id": "9241abd9-d0e6-425a-bd4f-47ba86e767a4",
            "type": "Role"
          },
          {
            "id": "5b567255-7703-4780-807c-7be8301ae99b",
            "type": "Role"
          }
        ]
      }
    ]
}'

Update-MgApplication -ApplicationId $NewApp.Id -BodyParameter $BodyParams

Once you have this in place you'll have to work out how you are authenticating against it. We're using a self-signed certificate and storing the tenant id and application id within a JSON file. The below gets added to every application upload script...
$Cert = Get-ChildItem "Cert:\CurrentUser\My" | Where-Object FriendlyName -eq "IntuneWin32App"
Try {
    $Tenant = (Get-ChildItem -Path ".\tenant" -File *.json).Name |
        ForEach-Object {
        [PSCustomObject]@{
            Tenant = $_  # Set the property name to "Tenant"
        }
        } | Out-GridView -Title "Select a Tenant" -OutputMode Single
    $Params = Get-Content -Path ".\tenant\$($Tenant.Tenant)"
    If (-not($Params)) { Write-Warning "Tenant not selected"; Exit 1}
    Connect-MSIntuneGraph -TenantID $Params.TenantId -ClientID $Params.AppId -ClientCert $Cert
} Catch {
    Write-Warning "Error connecting to Tenant"
    Exit 1
}

It would be good to have this issue marked as a bug and the module updated so that users can at least register an azure app and then connect the module with something like:
Connect-MSIntuneGraph -TenantID "yourtenant.onmicrosoft.com" -ClientID "yourappregistrationid"
(The above doesn't currently work for me).
Below are the steps that I have compiled for the current user based auth workaround:
In azure, go to azure app registrations and register an app.
set the  RedirectUri (public client/native)  = "https://login.microsoftonline.com/common/oauth2/nativeclient"
Go to api permissions, add a permission, Microsoft graph, delegated permissions,
add:
DeviceManagementManagedDevices.ReadWrite.All
DeviceManagementApps.ReadWrite.All
Group.Read.All
(note that application permissions for these 3 roles may also be needed)
Get the appid for the app you just registered.
Edit the powershell module
Edit the Connect-MSIntuneGraph.ps1
You must update lines #106 and #107 in the Connect-MSIntuneGraph.ps1 file located in the C:\Program Files\WindowsPowerShell\Modules\IntuneWin32App\1.4.4\Public folder
If installed in a user area… C:\Users\username\OneDrive\Documents\PowerShell\Modules\IntuneWin32App\1.4.4\Public
in Connect-MSIntuneGraph.ps1, set the following old values > new values.
Old values:
$ClientID = "d1ddf0e4-d672-4dae-b554-9d5bdfd93547"
$RedirectUri = "urn:ietf:wg:oauth:2.0:oob"
New Values:
Define static variables
        $ClientID = "Your client ID/App ID (not object ID) of the custom App reg with proper DeviceManagement related permissions (Application permissions)"
        $RedirectUri = "https://login.microsoftonline.com/common/oauth2/nativeclient"

Now you should be able to connect with
Connect-MSIntuneGraph -TenantID "yourtenant.onmicrosoft.com”

I created an App registration with the following API permissions:

I altered Connect-MSIntuneGraph.ps1 with mit App-ID and the Redirect-Uri.
But when I execute Add-IntuneWin32App I still get an error:
WARNING: An error occurred while creating the Win32 application. Error message: UnknownError: {"ErrorCode":"Forbidden","Message":"{\r\n  \"_version\": 3,\r\n  \"Message\": \"An error has occurred - Operation ID (for customer support): 00000000-0000-0000-0000-000000000000 - Activity ID: 962e5aff-dax3-485e-94xa-a0941f993535 - Url: https://fef.msub03.manage.microsoft.com/AppLifecycle_2406/StatelessAppMetadataFEService/deviceAppManagement/mobileApps?api-version=5024-03-08\",\r\n  \"CustomApiErrorPhrase\": \"\",\r\n  \"RetryAfter\": null,\r\n  \"ErrorSourceService\": \"\",\r\n  \"HttpHeaders\": \"{\\\"WWW-Authenticate\\\":\\\"Bearer realm=\\\\\\\"urn:intune:service,9225x241-44e1-44a8-8bfe-c10e3917x505,3e9c57b9-808d-4aa0-9500-4b2x369279e7\\\\\\\"\\\"}\"\r\n}","Target":null,"Details":null,"InnerError":null,"InstanceAnnotations":[]}
And idea what I might have done wrong? I need to upload additional apps :-/


Support readOnly, writeOnly (>= Draft 7)

The readOnly and writeOnly keywords (see specification (Draft 7)) make validation behave differently in the context of a write or read operation.
Unfortunately this does not seem to be covered by JSON-Schema-Test-Suite.
I found one (Java) library that supports this.

The specification doesn't seem to get into how these keywords relate to validating data, though I can see how specifying a validation context could be useful. I don't plan on working on this myself, but PRs are always welcome.

There is an example how one could handle readOnly: true via the before_property_validation option that was added in https://github.com/davishmcclurg/json_schemer/pull/77 in one of the tests.

If someone is interested in this as well: Actually using the added hooks to hack in readOnly behaviour did not work in my case, because is not called on sub-schemas used inside allOf etc. :|
Another, probably better, approach could be a custom keyword. There already is some support for custom keywords, but I cannot use that to hack readOnly.

Released in 2.0.0. Use access_mode option (read/write):
JSONSchemer.schema(schema).validate(data, :access_mode => 'read')


E117: Unknown function: unite#filters#matcher_default#use

Hello Vitaly.
I get this error message everytime I open file for editing in vim, after installation dotvim2.
Do you have a sugesstion how to fix it?
//------- error message
Error detected while processing <any_file>:
line   10:
E117: Unknown function: unite#filters#matcher_default#use

I have the same problem.


Dependency list values in JSON and Text reports not 100% accurate

Describe the bug
Dependencies reported in the json and text formats often have incorrect values.  The related rules need to be reviewed for accuracy.  See bolded examples below.
To Reproduce
Steps to reproduce the behavior:
Really just depends on the source code that is scanned
Expected behavior
Only actual includes, required etc. dependency files should be output
Screenshots
Example content:
"NJsonSchema.Validation.FormatValidators",
"StreamReader sr = new StreamReader(serializedStream.Content)",
"System",
"System.Collections.Concurrent",
"System.Net",
"System.Threading",
"System.Threading.Tasks",
"var aggregate = await CreateAggregateAsync(scope.ServiceProvider.GetRequiredService<IAggregateRepository>(), descriptor, command).ConfigureAwait(false)",
"var cts = new CancellationTokenSource()",
"var file = File.CreateText(filePath)",
"var file = File.OpenText(path)",

Improved it quite a bit.  Hard to get 100% but we're within our accuracy range.


Geodata point appearing behind surface

Hi again,
I made a global map of volcanoes using a freelayer, however that are located behind the planet appear through the layer. I tried playing with the visibility styling, but didn't have any success.
Any thoughts?
https://www.holoceneadventures.com/ivft2/world.html

Apologies, realised that the freelayer was not set on the page above. It should work now

Hi, again trying to sort this out but having no luck. I noticed that the OSM freelayers displays properly (i.e. it is hidden when on the other side of the globe see https://jsfiddle.net/7vuvgdme/) However can't see the styling so not sure how to troubleshoot the solution. Thanks.

Allright- I figured out where I went wrong - however I still think there is a bug.
When using the 'culling" style parameter, it works well to hide features such as labels and icons- however it does not work well on  'points'. However- if I set point as false, the icon is not 'clickable' ( i.e. i does not fire a click event if clicked on).
One solution I thought of is to set the point as true, but then set the point-color alpha value at 0. This cause the icon to flicker when moving, but at least the points are clickable. Finally, the solution I'm happy with is just to set the point value as true in a different style property, with the alpha value at 0. This seems to work.
`              "volcanoes" : {
"filter" : ["==", "#group", "Volcanoes"],
"culling": 90,
'icon': true,
'icon-source': '@icon-marker',
'icon-color': [125,255,0,255],
'icon-scale': 2,
'icon-origin': 'center-center',
"point-radius" : 30 ,
"point" : false,
"point-color":[255,0,0,255],
              "label": true,
              "label-size": 19,
              "label-source": "$NAME_",
              "label-offset": [0,-20],

              "zbuffer-offset" : [-8,0,0]

          },
          "clickable point" : {
              "filter" : ["==", "#group", "Volcanoes"],
              'icon': false,
              'icon-source': '@icon-marker',
              'icon-color': [125,255,0,0],
              'icon-scale': 2,
              'icon-origin': 'center-center',
              'click-event' : true ,
              "point-radius" : 30 ,
              "point" : true,
              "point-color":[255,0,0,0],

              "label": true,
              "label-size": 19,
              "label-source": "$NAME_",
              "label-offset": [0,-20],

              "zbuffer-offset" : [-8,0,0]

          },`

sorry- that does not solve the label problem. Also you can accidentally click on a point on the other side of the planet..

sorry again - culling does work for labels, just not for points


Revert "Revert "PostCSS support""

Reverts OpenNTF/JavascriptAggregator#280

OpenNTF » JavascriptAggregator #653 SUCCESS
This pull request looks good
(what's this?)


Replacer for the meta object?

Is it possible to apply the replacer function to the meta object? I sometimes log whole objects using the meta object and it would be nice if I could mask mySecretValue with something else using the replacer function.
log.debug('Test debug log',{'mySecretKey':'mySecretValue'});

From the docs, I understand that the replacer is only applied if I would call it like this:
log.debug({'mySecretKey':'mySecretValue'}).toJSON(true);

Thanks for this neat little module,
Marco

The replacer function is utilized when logging to the console as well, so implementing the replacer function will work without you manually having to call .toJSON();. Given that, you would be able to utilize the replacer function to mask values within any passed in metadata. For example:
log.options.replacer = function(key, value) {
	if(key === 'mySecretKey') {
		return 'XXXXXX';
    }
	return value;
};

log.error('My message', { mySecretKey: 'mySecretValue' });
//=> { "_logLevel": "error", "msg": "My message", "mySecretKey": "XXXXXX", "_tags": ["log", "error"] }

I hope this helps!

This definitely helps, thanks a lot for the quick response! I did set contradicting log.options in two different files during my tests, but it seems like only the first options got applied (which didn't have the replacer function set).


For modern Chef

This cookbook is depended on by daemontools cookbook, and both of them are using very old custom resource DSL.
This PR rewrites all the custom resources with the latest one and added tests for them, without changing resource interfaces, except removing exists from group resource.
Test passes as here: https://app.circleci.com/pipelines/github/limitusus/pacman?branch=feature%2Fchef16

@jesseadams Could you check this please? Or I release it as a new fork cookbook.

@limitusus - Would you like for me to pass over ownership of this repo to you? I no longer use chef.

@jesseadams
Sure. I will carry it over if you transfer GH repo and Supermarket cookbook to me :)

@jesseadams
I noticed transferring Supermarket cookbook to me is enough.
I'll update relevant links after that.

Transfer email sent

Thank you. I received its ownership.
I close this PR and handle this in my repo.


[New game]: Add Drop Dash Game

🎮 Game Request
Game logic and basic description

Point down the features
Game points
Select program in which you are contributing
No response
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

/assign

Hey @Ishitamukherjee2004 !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

Hey @Ishitamukherjee2004 ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


Add Kick Preview

Along with the Chat (Closed/Open), Lore, Hologram, & Server List previews, a kick preview would be nice to have!

fwiw, #179 and #217 will add an in-game kick preview


ZTEST_ZCL_PDF

Hi,
The test report ZTEST_ZCL_PDF requires screen 0100 to work properly.
Can I submit a PR for the repository in abapGit format?

Hi,
Yes of course - please do :)
I looked briefly on the abapGit client and it looked great! I will test it
as soon as I get the opertunity.
--BE
On Tue, Oct 24, 2017 at 6:51 PM, Lars Hvam<EMAIL_ADDRESS>wrote:

Hi,
The test report ZTEST_ZCL_PDF requires screen 0100 to work properly.
Can I submit a PR for the repository in abapGit format?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/beraadim/zcl_pdf/issues/2, or mute the thread
https://github.com/notifications/unsubscribe-auth/AMdhXCYeSmXVUZ72QeyEXwUofX_TG3ROks5svhWWgaJpZM4QEwGL
.

Isssue should now have been resolved.


Prevent formatting links as markdown links

Currently, users can create open redirects to potentially malicious links.
For example I can write https://stacker.news/items/194732 which actually redirects to https://stacker.news/items/194731
(interestingly, this also works in Github).
At first, I thought a open redirect warning would be enough but since we use a lot of links to external sites on SN, I think this would be detrimental to UX.
So I think the better solution is to check if the thing inside [] is already a link and then prevent using the markdown link syntax ([]())
edit: Or only use open redirects for this case if possible. For example, by replacing the URL to a page like https://stacker.news/redirect?url=<external_url>

Reference: https://stacker.news/items/194732

Hey i'm about to for the repo and start working on this @huumn or another dev, could you point me in the right direction of the flow and the files I'll need to touch? I can stumble through it, but with a bit of guidance I could probably get it wrapped up pretty quickly. Just getting my sea legs in your software :D

For this ticket, I would guess that the important files are components/text.js since that's where our Markdown input is defined (it uses react-markdown) and lib/md.js for other markdown stuff


file_browser still throwing attempt to index a nil value

Description
I think the file_browser was somehow missed when implementing
https://github.com/nvim-telescope/telescope.nvim/pull/1289
The file_browser picker still throws the error when hitting return on an empty list :smiley_cat:
Neovim version
NVIM v0.6.0-dev+627-gb5b025f6a
Build type: RelWithDebInfo
LuaJIT 2.0.5
Compilation: /usr/bin/cc -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions     -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security     -fstack-clash-protection -fcf-protection -Wp,-U_FORTIFY_SOURCE -Wp,-D_FORTIFY_SOURCE=1 -DNVIM_TS_HAS_SET_MATCH_LIMIT -O2 -g -Og -g -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wmissing-prototypes -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fno-common -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DMIN_LOG_LEVEL=3 -I[..]/neovim-git/src/build/config -I[..]/neovim-git/src/neovim-git/src -I/usr/include -I[..]/neovim-git/src/build/src/nvim/auto -I[..]/neovim-git/src/build/include
Compiled by aron

Operating system and version
Arch Linux x86_64 @ 5.15.5-arch1-1
checkhealth telescope
telescope: require("telescope.health").check()
========================================================================
## Checking for required plugins
  - OK: plenary installed.
  - OK: nvim-treesitter installed.

## Checking external dependencies
  - OK: rg: found ripgrep 13.0.0
  - OK: fd: found fd 8.3.0

## ===== Installed extensions =====

Steps to reproduce

Open the file_browser
Enter something that leads to an empty selection
Hit enter

Expected behavior
Print [telescope] Nothing currently selected like find_files or other pickers
Actual behavior
E5108: Error executing lua ...ker/start/telescope.nvim/lua/telescope/builtin/files.lua:374: attempt to index a nil value
stack traceback:
        ...ker/start/telescope.nvim/lua/telescope/builtin/files.lua:374: in function 'condition'
        ...packer/start/telescope.nvim/lua/telescope/actions/mt.lua:8: in function 'run_replace_or_original'
        ...packer/start/telescope.nvim/lua/telescope/actions/mt.lua:30: in function 'run_replace_or_original'
        ...packer/start/telescope.nvim/lua/telescope/actions/mt.lua:30: in function 'key_func'
        ...k/packer/start/telescope.nvim/lua/telescope/mappings.lua:235: in function 'execute_keymap'
        [string ":lua"]:1: in main chunk

See https://github.com/nvim-telescope/telescope-file-browser.nvim/issues/9

@thraizz could you please confirm that this issue does not persist on latest master as it should be fixed by https://github.com/nvim-telescope/telescope-file-browser.nvim/commit/f7f8f2a9717d65d2aeeadd23af127b8a879789f1

Can confirm it was resolved with f7f8f2a:

Cool thanks :)

Thanks for the quick fix!


Create Scatter Plot

Create a Scatter Plot chart

Curious if this has gained any traction.

me too; would be great. Also if it would include bubble sizes and colors!

Will have some time to work on it in upcoming days!

+1 for this, especially if it includes generating trendlines!

Hey guys, I implemented initial work for Scatter Plot. More features will be added soon. Feel free to leave comments/feedback: https://github.com/eventbrite/britecharts/pull/560

Scatter plot was created. All the new functionalities and fixes will be added with new issues.


Panel shows automatically on startup

I noticed that the output panel was opening right on startup opening a JS project I had checked out showing me this:

I suggest to use a notification instead that is easier for the user to deal with. A panel is not easy to dismiss, takes a lot of vertical space and destroys my current workbench layout.

Filed https://github.com/Microsoft/vscode-tslint/issues/415 for the related issue in TSLint.
/cc @egamma

Thanks!


Added option to preselect an item

By filling the $scope.resolvedOptions in both methods we can "preselect" some items.
example:
// You can add this in your app.js
$scope.options = [ {id: 1, foo: "bar"}, {id: 2, bar: "foo"} ];
$scope.selection = [ {id: 1, foo: "bar"} ];

When you load your webpage the item with id 1 is already selected

Worked fine. Thanks!

Was this merged on master?
I need this so all options come pre-selected and the user filters then out, instead of selecting then.
May be an odd behavior, I know, but it's what was requested.

As far as I know this is not merged, but feel free to my fork.

Simply set it in your JS code :)
$scope.filtro.clientes = [objectA, objectB, objectC, ...];

Oh yup, it's simple, Thanks! You're awesome!

No probs! Have fun with it!

I'd love to use this feature, any updates on merging this in the master @bentorfs?