bug:  floating window overlays quickfix list

Did you check docs and existing issues?

[X] I have read all the noice.nvim docs
[X] I have searched the existing issues of noice.nvim
[X] I have searched the exsiting issues of plugins related to this issue

Neovim version (nvim -v)
0.9.0-dev-912+gfe1e6b82f
Operating system/version
Windows 10
Describe the bug
If I want to filter the lsp servers in the mason.nvim menu by language, the selection screen appears behind the floating window.

Steps To Reproduce

type in :Mason
press <c-f>

Expected Behavior
Without noice.nvim a full sized window appears.

Repro
-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")
-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  "folke/noice.nvim",
  -- add any other plugins here
  { "williamboman/mason.nvim", config = true }
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here

You can try setting the zindex option to the view that is being used there, but better to use something like dressing.nvim


George Jiang: Assignment 3

Added a file with a reason for my favorite programming language.

You have an empty file as well, please delete that and commit and push again.

@george962 you still have the empty file, please delete that commit and repush.

LGTM, we will go over amending to an existing commit instead of creating a new commit for every new change to the same PR.


gamma: Align data type in computation with the declaration of the helper

Resolve the FP64 issue in the gamma operators on ARC.


Enable cross-namespace ingress in nginx-alpha ingress controller.

This allows you to run one ingress controller rc and fan out to services in multiple namespaces.

Thanks, LGTM


Bump playwright to 1.25.2

@playwright/test breaks the spa-test  from version 1.26.0 ( same as Vite 4 does #674 ), so this bumps it to the latest version before that.
We bumping to 1.26 and beyond, this happens for both index.html and root.tsx:

Thank you for all your efforts here. Very appreciated.


Refactored Calendar component to remove dependency of primereact.

Hi everyone,
I have implemented a Calendar component as requested in the issue below, with the dependency of primereact removed. I will welcome any feedback or suggestions for improvement.
https://github.com/Magickbase/neuron-public-issues/issues/66
Thanks!

That's cool, but it's better to create a pr for https://github.com/nervosnetwork/neuron, and better to append a video or screenshot about the new calendar in the comment

@mortoys That's cool, but it's better to create a pr for nervosnetwork/neuron, and better to append a video or screenshot about the new calendar in the comment

https://github.com/nervosnetwork/neuron/pull/2513 for instance


✨ Dynamic copyright year

Hi,
I would like to request a feature for a shortcode in the file languages.en.toml, please.
Something like:
copyright = "Copyright © {{ now.Year }}"
Thank you!

@verlanmar this one was already fixed by @AlanTanner
Sorry forgot to close the ticket


Add BetSwirl BETS (Polygon)

https://github.com/beefyfinance/beefy-api/pull/1154

vault: 0x6eAc1214B81acb0F33c5aC4d426587032E53e5eC
strategy: 0x9886724723D5c582B0E164286EE7DF317dFCA867

@shatterproof @frondoto LGTM, can you resolve conflicts? Also are they definitely keeping liquidity on the old Quickswap AMM and not moving to the CL version?

@kexleyBeefy checked with the team and they don’t have plans to move the liquidity, they will let me know if that happens


Update YAML docs

In the config file

@blongden Can you update the css_include entry on this page? Then I think we can close this issue.

https://github.com/holography/holograph/wiki/How-to-configure-Holograph

👍


Image styles for various device widths

http://internal.gbif-dev.org/data-use/page/11343
As the device width changes the banner image may not shown in the best crop. A few more dimensions will offered from the API will improve viewing experiences with proper proportions and resolution.

Merged with #31.


React 19 compatibility

Recently React 19 was released, and I keep getting this warning about element.ref, since it's going to be removed in a future release, are you guys going to adjust this?
Warning: Accessing element.ref was removed in React 19. ref is now a regular prop. It will be removed from the JSX Element type in a future release.

React & ReactDom v19 is in "release candidate phase" and will be released shortly.


File name don't changed color in file list when file modies

Hi
My vscode has stop showing file has been modified by change color of file name in file list to the left side. It's not only mine but my other colleague as well.
My version is:
Version: 1.59.0 (Universal)
Commit: 379476f0e13988d90fab105c5c19e7abc8b1dea8
Date: 2021-08-04T23:14:40.191Z (1 wk ago)
Electron: 13.1.7
Chrome: 91.0.4472.124
Node.js: 14.16.0
V8: 9.1.269.36-electron.0
OS: Darwin x64 20.5.0

You're referring to these markers?

I still see them, have you changed any "decorations" settings?

No I haven't. However the one in the list: Workbench > Editor > Decorations: Colors I don't have in my list. The other options you listed is the same.
As I mention in my description this is not an isolated issue since my other colleague experiencing the same issue.
Need to mention I'm using MacBook Pro laptop if it would be any significant.

I have not been able to reproduce this on the same platform. If you can find a particular repo that causes this behaviour that may help, or try running in insiders. Also, try running via code --user-data-dir {} --extensions-dir {} ({} replaced with a temporary directory) and see if the issue reproduces there.


Object(...) is not a function

Version
v2.6.3
Reproduction link
https://nuxtjs.org
Steps to reproduce
Not sure yet unfortunately
What is expected ?
Nuxt works
What is actually happening?
An Object(...) is not a function error is shown when setContext is called in .nuxt/index.js
Sometimes during development this error happens. I am not exactly sure yet what triggers it, sometimes it happens once a day and sometimes 10+ times.
What I know about it so far:

The error is caused because the .nuxt/utils import returns an empty object
The utils file does exist and when executed with --experimental-modules node has a 0 exit status (so no syntax errors in the file)
Deleting the utils module from require.cache did not solve the issue
Restarting the dev server made the error go away
It doesnt seem to have to do with a long running dev server, this morning I had it within 20mins of starting work

Although restarting the dev server is a good enough solution,  rebuilding the whole project can take quite a bit of time which can be frustrating.
Additional comments?
First reported here: https://stackoverflow.com/questions/55949558/how-to-solve-object-is-not-a-function-error-in-nuxt
Screenshot of error: https://i.imgur.com/CEoHxQq.png

This bug report is available on Nuxt community (#c9157)

One i experienced this issue on code-sandbox (no extra integrations - just nuxt) by very first reload.

Its also not unique for .nuxt/utils, I just received the error with .nuxt/server.js for the .nuxt/index.js import (the not a function error was on createApp this time). But because I tried to add some debug logs to that file, the dev server reloaded and now I get:
ERROR in ./.nuxt/utils.js
Module build failed (from ./node_modules/babel-loader/lib/index.js):
SyntaxError: /var/project/.nuxt/utils.js: Unterminated string constant (454:27)

  452 |       const token = tokens[i]
  453 |
> 454 |       if (typeof token === 'st
      |                            ^
    at Object.raise (/var/project/node_modules/@babel/parser/lib/index.js:6322:17)
   ...

but if I look inside .nuxt/utils it just shows:
    for (let i = 0; i < tokens.length; i++) {
      const token = tokens[i]

      if (typeof token === 'string') {
        path += token

        continue
      }

So apparently there is either some memory corruptions in the dev server somewhere or an IO issue which doesnt or only partially reads the module file?

I'm having the same error. I'm using Nuxt 2.7.1  After a random amount of time the error occurs, after a hot-reload attempt by the dev server. To solve the error I have to restart the dev server. For me it always occurs in nuxt/index.js:113:19 in createApp.
The traceback that is shown:
// ...
  const path = getLocation(router.options.base)
    route = router.resolve(path).route
  }

  // Set context to app.context
  await setContext(app, {
    route,
    next,
    error: app.nuxt.error.bind(app),
    store,
    payload: ssrContext ? ssrContext.payload : undefined,
// ...

This error seems completely random when generating templates. Webpack tries to read the source when it is not completely written to the disk...

I can confirm this with v2.6.3 on Linux.
But seems it's OK with v2.7.1.

I've also been trouble-free since upgrading 2.7.1

I have not seen the error anymore in my current project after upgrading to time-fix-plugin v2.0.6, but as the error shows so erratically its difficult to say whether the issue really has gone.
@pi0 Maybe a bit far-off, but do you think this issue could be related somehow to #5650 ?

In my case on Linux it hasn't happened yet with 2.7.1, but on Windows 10 it does occur frequently,

Just had the error again on Linux with 2.7.1, but this project still used time-fix-plugin v2.0.5. Will upgrade to 2.0.6. and see what happens

Let's hope magically fixed :) (BTW Please report back if still occurs)

+1 here, just had the error with:
<EMAIL_ADDRESS>  version "2.11.0"
  resolved "https://registry.yarnpkg.com/nuxt/-/nuxt-2.11.0.tgz#654664fe1a95af2014fd55c38ba2c732bfa5edc5"
  integrity sha512-Y7lastjYWIOppja0FaWozPfkvlmJ8uZSqWx0VbK7l5djbHls5jgUGag0iu6GsNNwCFTKpoAtptNHiWOsyMxStA==
  dependencies:
    "@nuxt/builder" "2.11.0"
    "@nuxt/cli" "2.11.0"
    "@nuxt/core" "2.11.0"
    "@nuxt/generator" "2.11.0"
    "@nuxt/loading-screen" "^1.2.0"
    "@nuxt/opencollective" "^0.3.0"
    "@nuxt/webpack" "2.11.0"

Bugxt.js.  I'm using the most up to date version in 2022 and this is still and issue.

I had the issue here, fixed by using Node LTS image on my docker container instead of non-LTS (presumably latest).


Export IgnoreUrlsConfig from public-api.ts

It is part of OpenTelemetryConfig and should also be publicly available. Currently IgnoreUrlsConfig needs to be imported as
import { IgnoreUrlsConfig } from "@jufab/opentelemetry-angular-interceptor/lib/configuration/opentelemetry-config";

instead of
import { IgnoreUrlsConfig } from "@jufab/opentelemetry-angular-interceptor/public-api";

Hi @hlovdal
Thanks for your contribution.
LGTM.


feat: missing DenyList feature

Cherry-picking PR #79
Tested the server is able to load the denylist

can you sign the commit ? 🙏

can you sign the commit ? 🙏

done!


Vite throws 'Uncaught ReferenceError: regeneratorRuntime is not defined'

Describe the bug
Uncaught ReferenceError: regeneratorRuntime is not defined when using react-location with Vite.
To Reproduce
Steps to reproduce the behavior:

yarn create vite --template react-ts
yarn
yarn add @tanstack/react-location
Replace App.tsx with code below
yarn dev

import { ReactLocation, Router } from '@tanstack/react-location';

const location = new ReactLocation();

function App() {
  return (
    <Router location={location} routes={[{ path: '/' }]}>

Title

    </Router>
  );
}

export default App;

Screenshots

Desktop (please complete the following information):

OS: Windows 10 64-bits
Browser: Chrome
Version: 98.0.4758.102

See #220. Should be fixed with #223.

This still happens with version 3.6.5 which has #223.
Dependencies

Vite: 2.8.6
@tanstack/react-location: 3.6.5

Only works when using version react-location <= 3.3.5

The problem still exists with version 3.7.0.

Issues are not related. To fix this one you will have to use the regenerator-runtime library and call it from your main file.
See this discussion on a similar issue with amplify-js https://github.com/aws-amplify/amplify-js/issues/8514#issuecomment-871904042
Here, I solved it by installing regenerator-runtime (yarn add regenerator-runtime) and adding import 'regenerator-runtime' to the top-level JavaScript file in my application (main.tsx in my case).

@hugobdev that's for the suggestion. Importing regenerator-runtime fixes the issue.
Maybe this is something that can be added to the docs.

I have tried out react-location a while back with vite and didn't encounter this issue. What changes that made importing regenerator-runtime necessary now?

This issue was fixed with #236
Try the latest version 👍 v3.7.2

Still happening for me in v3.7.4.

Still happening in vite 4.0.2

Still happening in vite 4.3.9

It is still there! vite 4.4.0

Try this way:
pnpm install vite-plugin-babel
Then copy this code to vite.config.ts

When using React Table, if your code uses async/await syntax, you need to introduce the regenerator-runtime library into the project.

You can install the regenerator-runtime library via npm and then include it in your code:
npm install --save regenerator-runtime

Introduce it in your entry file, such as index.js or main.js
import 'regenerator-runtime/runtime'


Buttery-eel using a different guppy config file than requested

The issue presented as Buttery-eel saying it is doing sup basecalling when it was supposed to be doing hac basecalling for me:
timamo@brenner-fpga:PSXPX230069:$ qstat -j 4204295 | grep -e job_args -e script_file -e cwd
cwd:                        /share/ScratchGeneral/NanoporeClientData/tmp/PSXPX230069/PSXPX230069
job_args:                   PSXPX230069_reads.blow5,dna_r9.4.1_450bps_hac_prom.cfg,9,PSXPX230069_fail_hac.fastq.gz,PSXPX230069_pass_hac.fastq.gz
script_file:                /directflow/KCCGGenometechTemp/projects/timamo/scripts/development/buttery_eel_basecall.sge.sh
timamo@brenner-fpga:PSXPX230069:$ pwd
/share/ScratchGeneral/NanoporeClientData/tmp/PSXPX230069
timamo@brenner-fpga:PSXPX230069:$ grep config PSXPX230069/butter_PSXPX230069.out -m2
 Namespace(input='PSXPX230069_reads.blow5', output='./reads.fastq', guppy_bin=PosixPath('/share/ClusterShare/software/contrib/timamo/ont-guppy-6.5.7/bin'), config='dna_r9.4.1_450bps_sup.cfg', guppy_batchsize=4000, call_mods=False, qscore=10, slow5_threads=4, slow5_batchsize=4000, quiet=False, moves_out=False, do_read_splitting=True, min_score_read_splitting=50.0, detect_adapter=False, min_score_adapter=60.0, trim_adapters=False, detect_mid_strand_adapter=False, log='buttery_guppy_logs', seq_sum=True)
PyGuppyClient(address='ipc:///share/ScratchGeneral/NanoporeClientData/tmp/PSXPX230069/PSXPX230069/5887', config='dna_r9.4.1_450bps_sup', align_ref=None, bed_file=None, barcodes=None, status.connected, )

My script was apparently mapping the arguments correctly:
timamo@brenner-fpga:PSXPX230069:$ grep -e MODEL -e MIN_QSCORE -e CALLMODS -e else -e fi$ -e RAW_INPUT -e OUTPUT /directflow/KCCGGenometechTemp/projects/timamo/scripts/development/buttery_eel_basecall.sge.sh | grep -v '^#' | head -n-2
RAW_INPUT=$1               # raw slow5 files for 1D basecalling with
MODEL=$2                   # basecalling model
MIN_QSCORE=$3              # minimum average quality score for reads in pass reads file
OUTPUT=./reads.fastq
if [ -z $MODEL ]; then echo "MODEL required. eg.: dna_r9.4.1_450bps_hac_prom.cfg"; exit 1; fi
if [ -z $RAW_INPUT ]; then echo "Raw input for basecalling not set"; exit 1; fi
if [[ ${MODEL} == *modbases* ]]; then
    CALLMODS="--call_mods"
                OUTPUT="reads.sam"
else
    CALLMODS=""
fi
/usr/bin/time -v buttery-eel -i ${RAW_INPUT} -o ${OUTPUT} --guppy_bin /share/ClusterShare/software/contrib/timamo/ont-guppy-6.5.7/bin/ --port 5887 --config ${MODEL} -x cuda:all --chunk_size 1500 --max_queued_reads 1000 -q $MIN_QSCORE --do_read_splitting --seq_sum $CALLMODS || log "$RUN_ID Could not execute eel command"

James said the issue was because I had

"another buttery-eel running with diff args"

and

"if they are on the same port, and the same machine, using ipc, the buttery-eel client will connect to the existing server with those models loaded"

and

"please use --use_tcp and use different ports each time".

Hasindu said this code (from his bashrc) can automatically find a port (and can be used in a script):
eel(){
#from https://unix.stackexchange.com/questions/55913/whats-the-easiest-way-to-find-an-unused-local-port
PORT=$(netstat -aln | awk '
  $6 == "LISTEN" {
    if ($4 ~ "[.:][0-9]+$") {
      split($4, a, /[:.]/);
      port = a[length(a)];
      p[port] = 1
    }
  }
  END {
    for (i = 5000; i < 65000 && p[i]; i++){};
    if (i == 65000) {exit 1};
    print i
  }
  ') && source ~/hasindu2008.git/buttery-eel/venv3-multi-guppy-6.5.7-python3.8/bin/activate && buttery-eel -g /install/ont-guppy-6.5.7/bin/ "$@" --port ${PORT} --use_tcp && deactivate
}

Hasindu also said:

"We should better put this fact in the readme and HIGHLIGHT it, as this can be a common mistake by users and is not too good, as it is a silent issue"

I fixed this already with --port auto


Why do we need to remove X11 in watchdog.sh

Hello Thyrlian,
First of all thank You very much for all Your efforts related with current project. Could you explain please why do we need to remove X11, i mean instructions in watchdog.sh
 rm -fv /tmp/.X*-lock >> $log_file
 rm -fv /tmp/.X11-unix/* >> $log_file

Thank You!

Hi @StanlyT.
You can find the original commit for that piece of code here.
So the purpose of it was for "Add clean up script for vnc when receiving SIGTERM" according to the commit message.  More details, the concrete problem and the solution are available on stackoverflow.
Is this solution causing any problem for you?  Thanks :)

Hi @StanlyT.
You can find the original commit for that piece of code here.
So the purpose of it was for "Add clean up script for vnc when receiving SIGTERM" according to the commit message.  More details, the concrete problem and the solution are available on stackoverflow.
Is this solution causing any problem for you?  Thanks :)

About causing problem i'm not sure. I have to recheck that. Thanks a lot for Your answer!

About causing problem i'm not sure. I have to recheck that. Thanks a lot for Your answer!


Expose ChangeNotifier.isDisposed

In many situations, it is impossible to safely call removeListener from a StatefulWidget's dispose function. In many cases the stateful widget, or even the developer's app, is not in control of the change notifier and the widget may be disposed before or after the change notifier was disposed. For example, the change notifier may be exposed by a third party package that makes no guarantees about the order in which a change notifier will be disposed. See #71983 for a specific example.
Ideally, calls to removeListener should be safe-it shouldn't throw when the change notifier has already been disposed. However, removing the assert is theoretically a breaking change as some users may have try...on blocks that rely on the assert throwing in this case. To avoid a breaking change, I've instead exposed _debugIsDisposed which is more broadly useful than just for ensuring calls to removeListener are safe.
It appears that ChangeNotifier has been written with a philosophical belief that _debugIsDisposed should not be public. However, you can't have both. Either expose isDisposed, or make removeListener safe to call. Otherwise you're forcing developers in some circumstances to use sloppy and dangerous try...on blocks. Honestly, ideally, we'd want to expose isDisposed AND make calls to removeListener safe.
Fixes: https://github.com/flutter/flutter/issues/71983
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making or feature I am adding, or Hixie said the PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

@goderbauer Hey! I've created this PR to resolve #71983. I noticed you've reviewed some previous PRs against ChangeNotifier-could you look at this one for me?

Looks like the analyzer is unhappy with this change and it is breaking some customers, which makes this a breaking change. Those require special treatment: https://github.com/flutter/flutter/wiki/Tree-hygiene#handling-breaking-changes
Regardless of that, I am not in favor of actually making this change. If you're trying to operate on a disposed ChangeNotifier that usually indicates that there's a lifecycle bug somewhere.

Looks like the analyzer is unhappy with this change and it is breaking some customers, which makes this a breaking change. Those require special treatment: https://github.com/flutter/flutter/wiki/Tree-hygiene#handling-breaking-changes
Regardless of that, I am not in favor of actually making this change. If you're trying to operate on a disposed ChangeNotifier that usually indicates that there's a lifecycle bug somewhere.

Oof yeah I didn't think it through carefully enough-anyone using implements instead of extends will be broken by this-very non-ideal.
This makes making calls to removeListener safe a much more appealing solution.
If you don't think this change is desirable, can you post in the associated bug why? The issue being brought up there is the developer is often not in control of the notifier's lifecycle. eg if they're getting it from a third party package. In those cases, they may not know if they notifier or their widget will be disposed of first and, even worse, there may be race conditions that make the dispose order non-deterministic.

Regardless of that, I am not in favor of actually making this change. If you're trying to operate on a disposed ChangeNotifier that usually indicates that there's a lifecycle bug somewhere.

The keyword here is "somewhere" - you cannot do anything meaningful if third party code involved, the only way is to use try..catch for removeListener

The issue being brought up there is the developer is often not in control of the notifier's lifecycle. eg if they're getting it from a third party package. In those cases, they may not know if the notifier or their widget will be disposed of first and, even worse, there may be race conditions that make the dispose order non-deterministic.

How can you meaningfully use the ChangeNotifier of a third party packages if said package is just willy-nilly disposing the notifier? There must be some kind of a lifecycle contract - and this contract should involve giving the consumer a change to properly release its usage of the notifier before it is disposed.
This change (or the proposed change to removeListener) is just papering over another bug in the system which may then blow up in a different place.

@goderbauer

This change (or the proposed change to removeListener) is just papering over another bug in the system which may then blow up in a different place.

First of all - removeListener must never raise any exceptions - nobody cares if it is already disposed or not. If nothing to do then do nothing without raising useless exceptions.
Second - there is reproducible case, take a look: https://github.com/flutter/flutter/issues/71983#issuecomment-917297746

@goderbauer

This change (or the proposed change to removeListener) is just papering over another bug in the system which may then blow up in a different place.

First of all - removeListener must never raise any exceptions - nobody cares if it is already disposed or not. If nothing to do then do nothing without raising useless exceptions.
Second - there is reproducible case, take a look: #71983 (comment)

FWIW, he just resolved my related issue-I was misunderstanding the intended use of Scrollable.of and how route interacts with it:
https://github.com/flutter/flutter/issues/89924#issuecomment-920424050
I still agree on #1. Cleanup functions should only throw in fairly exceptional circumstances-it's clear this philosophy was already in mind when it was decided that removeListener should not throw if the specified function is not present. The same logic that says it shouldn't throw if the function isn't there is just as compelling for saying it shouldn't throw if the notifier is already disposed.


Main thread optimization

I/Choreographer: Skipped 153 frames!  The application may be doing too much work on its main thread.

need to find where this occurs

occurs on PresetStoreActivity on bringing the presets (local / online)
use AsyncTask


Xiaomi Smart IH Rice Cooker 3L ?

Device model
chunmi.cooker.cmwy3
Device name
Xiaomi Smart IH Rice Cooker 3L
Does the device require a MiCloud connection?
I don't know
Anything special about the device?
I found it doesn't work even though there is a button in homekit

Could it be that the Devise requires a micloud connection? Did you try to specify your micloud credentials and set the device to forceMiCloud?


The MetricsReporterBackgroundService doesn't flush all data

I have an extremely short lived app and it is not pushing any metrics as expected. I'm noticing a potential flaw in this service and just wanted to report it here before attempting a PR.
The MetricsReporterBackgroundService is a BackgroundWorker and it is essentially running in a while loop with a sleep.
My hypothesis is that this worker loops once, awaits on the sleep for 500ms. In that time period my application runs, logs metrics and exits.
Upon exit my application is calling IHostApplicationLifetime.StopApplication() which shuts down the hosted runtime. I'm assuming that at this point the background services cancellation tokens are cancelled, which pops it out of sleep and then causes it to fall out of the while loop. The metrics that were logged during that last sleep iteration are not flushed.
I can imagine two ways to fix this but essentially I believe that there needs to be a final flush that happens before the background service exits.
I believe it could be as simple as changing the order with which sleeping and flushing happen:
From:
while (!cancellationToken.IsCancellationRequested
    && _options.Enabled
    && _options.ReportingEnabled)
{
    await ExecuteOnceAsync(cancellationToken);

    Logger.Trace($"Delaying for {WaitBetweenReportRunChecks}");
    await Task.Delay(WaitBetweenReportRunChecks, cancellationToken);
}

To:
while (!cancellationToken.IsCancellationRequested
    && _options.Enabled
    && _options.ReportingEnabled)
{
    Logger.Trace($"Delaying for {WaitBetweenReportRunChecks}");
    await Task.Delay(WaitBetweenReportRunChecks, cancellationToken);

    await ExecuteOnceAsync(cancellationToken);
}

Or Possibly:
while (!cancellationToken.IsCancellationRequested
    && _options.Enabled
    && _options.ReportingEnabled)
{
    Logger.Trace($"Delaying for {WaitBetweenReportRunChecks}");
    await Task.Delay(WaitBetweenReportRunChecks, cancellationToken);

    await ExecuteOnceAsync(cancellationToken);
}

// Flush remaining metics before exiting
if (_options.Enabled && _options.ReportingEnabled) {
    await ExecuteOnceAsync(cancellationToken);
}

Thoughts on this?

The problem seems slightly worse than I thought, I copied the code into my app and am playing with it and it seems like this background worker does not even startup until after I have already called IHostApplicationLifetime.StopApplication().
It then drops in to call await flushTask.Reporter.FlushAsync() and then something about the host shutting down causes the task to never resolve or ever make an http call.
My local fix, which seems to be working is three-fold:

Import the IHostApplicationLifetime service and register a ShuttingDown event.
Set state on the resolver that the app is shutting down and exit the while loop in that case
I had to remove the entire TaskFactory, I'm not sure why it was even there it appeared to be an unnecessary layer of asynchrony that straight up doesn't work when the host is shutting down.

I'll make a PR but the only thing I'm concerned about is the TaskFactory, which is necessary for the fix but I'm not really sure why it was there at all so I may need someone to explain that.


[Request] Integrate the debugger into Visual Studio as a VS extension for NeoContract project types.

Integrate the debugger into Visual Studio as a VS extension for NeoContract project types.

I don't have the knowledge to implement something like that yet (I'm not familiar with creating extensions for VS).
Here's some documentation I found in case anyone else wants to try:
https://msdn.microsoft.com/en-us/library/bb145934.aspx

After opening this, I think this is the right approach and will be a waste of time relative to other things that can be worked on (e.g. source level profiler).  neo-debugger works fine as a separate desktop app automatically launched from Visual Studio as part of a Debug session.

@mwherman2000 later if you have time please add to the readme instructions how to auto launch the debugger in VS.


Could not resolve all dependencies for configuration ':shared:jsCompileClasspath'. > Could not resolve io.realm.kotlin:library-base:1.11.0.   Required by:       project :shared

I'm using realm in my kmp app, I know that realm isn't  compatible with web yet so I want to run web without realm library but I keep on receiving an error
Could not resolve all dependencies for configuration ':shared:jsCompileClasspath'.
> Could not resolve io.realm.kotlin:library-base:1.11.0.
  Required by:
      project :shared
   > No matching variant of io.realm.kotlin:library-base:1.11.0 was found. The consumer was configured to find a library for use during 'kotlin-api', preferably optimized for non-jvm, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'js', attribute 'org.jetbrains.kotlin.js.compiler' with value 'ir' but:
       - Variant 'iosArm64ApiElements-published' capability io.realm.kotlin:library-base:1.11.0 declares a library for use during 'kotlin-api':
           - Incompatible because this component declares a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'native' and the consumer needed a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'js'
           - Other compatible attributes:
               - Doesn't say anything about its target Java environment (preferred optimized for non-jvm)
               - Doesn't say anything about org.jetbrains.kotlin.js.compiler (required 'ir')
       - Variant 'iosArm64MetadataElements-published' capability io.realm.kotlin:library-base:1.11.0 declares a library:
           - Incompatible because this component declares a component for use during 'kotlin-metadata', as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'native' and the consumer needed a component for use during 'kotlin-api', as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'js'
           - Other compatible attributes:
               - Doesn't say anything about its target Java environment (preferred optimized for non-jvm)
               - Doesn't say anything about org.jetbrains.kotlin.js.compiler (required 'ir')
       - Variant 'iosArm64SourcesElements-published' capability io.realm.kotlin:library-base:1.11.0:
           - Incompatible because this component declares documentation for use during 'kotlin-runtime', as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'native' and the consumer needed a library for use during 'kotlin-api', as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'js'
           - Other compatible attributes:
               - Doesn't say anything about its target Java environment (preferred optimized for non-jvm)
               - Doesn't say anything about org.jetbrains.kotlin.js.compiler (required 'ir')
       - Variant 'iosSimulatorArm64ApiElements-published' capability io.realm.kotlin:library-base:1.11.0 declares a library for use during 'kotlin-api':
           - Incompatible because this component declares a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'native' and the consumer needed a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'js'
           - Other compatible attributes:
               - Doesn't say anything about its target Java environment (preferred optimized for non-jvm)
               - Doesn't say anything about org.jetbrains.kotlin.js.compiler (required 'ir')
       - Variant 'iosSimulatorArm64MetadataElements-published' capability io.realm.kotlin:library-base:1.11.0 declares a library:
           - Incompatible because this component declares a component for use during 'kotlin-metadata', as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'native' and the consumer needed a component for use during 'kotlin-api', as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'js'
           - Other compatible attributes:

I tried this solution but its not working val jsMain by getting {
dependsOn(commonMain)
dependencies {
implementation(compose.html.core)
implementation("io.realm.kotlin:library-base:$realmVersion") {
exclude(group = "io.realm.kotlin", module = "library-base")
}
implementation("io.realm.kotlin:library-sync:$realmVersion") {
exclude(group = "io.realm.kotlin", module = "library-sync")
}
}
}

It seems that Realm.db doesn't support JS target.

You can ask them to provide at least an empty wrapper to pass compilation.
Or you can take that dependency out ofcommonMain and place it in a custom target named mobileOnlyLibs.
Or you can  completely abstract the database layer to interfaces and write code in each platform. This solution you write more but if you have already stuff in each platform you can reuse.

thanks @pablichjenkov , it looks this  js(IR) { browser() } is causing the issue. can I exclude realm inside js(IR) { exclude ("io.realm.kotlin:library-base:1.11.0") } ?

something like this  dependencies {
        implementation("io.realm.kotlin:library-base:$realmVersion") {
            because("Realm is not supported in Kotlin/JS")
            exclude(group = "io.realm.kotlin", module = "library-base")
        }
        implementation("io.realm.kotlin:library-sync:$realmVersion") {
            because("Realm is not supported in Kotlin/JS")
            exclude(group = "io.realm.kotlin", module = "library-sync")
        }

    }. but it won't work

I did this and it working.  js(IR) {
browser()
configurations {
all {
exclude(group = "io.realm.kotlin", module = "library-base")
exclude(group = "io.realm.kotlin", module = "library-sync")
}
}
}. do you think it will cause any issues down the line ?

I don't think an exclusion rule will apply here. It would be a nice feature request but normally gradle tries to resolve all dependencies then apply the exclusion rule. In any case the exclusion rule should be applied in the JS target only, your code above is basically removing it from everywhere.
You should create an intermediate target named onlyMobile, it will have your only mobile dependencies, then make Android and iOS target depend on onlyMobile. Your realmdb dependency will be in onlyMobile not in common.
I could provide some code snippet but I am on my phone atm.

yeah that would be a great feature, also I'm using realm for desktop so can you show a snippet when you're free please. thanks!

Check this project:
https://github.com/pablichjenkov/kmp-amadeus-api/blob/d4b296ccfd6416e79125143e24290a8c216a93c8/amadeus-api/build.gradle.kts#L153

Thank you @pablichjenkov for helping with this question! :)
@ismai117 Feel free to add more questions if needed.
To summarize:
If some libs don't support a particular target (k/js in this case), then that target shouldn't have it as a dependency. As @pablichjenkov has shown, it can be done by adding extra source sets to for supported/unsupported targets.

that's all sorted on my side now, thanks for the help!!

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


boards: arm: gd32f407v_start: Add initial support for gd32f407v_start

Add initial support for the GD32F407V-START board.
This patch is based on GD32E507V-START's one.
Signed-off-by: TOKITA Hiroshi<EMAIL_ADDRESS>

I found using openocd for debugging GD32F407xx in the platform-io package (it seems community base made).
But, I don't include it because I can't verify that it is supported at this time.
https://github.com/CommunityGD32Cores/platform-gd32/blob/52cb1be23bcff41a2b9da6adf3ce9bbdd9b3bf15/boards/gd32407v_start.json#L26

Hi @soburi ,
Update hash.

Hi @nandojve ,

Hi @soburi ,
Update hash.

Rebase done. All CI passed. 👍


Detect crashes with inconsistent/impossible crash addresses

A recent Firefox crash spike (bug 1796282) was caused by a CPU bug. This took a while to figure out as we have only a handful of people within Mozilla that can identify those. However the crashes had an obvious hint that this crash could have been impossible: the disassembled crash address was valid (and not a non-canonical address like it appeared in many crashes) and more importantly it fell within an accessible and readable region of memory, so the crash reason (EXCEPTION_ACCESS_VIOLATION_READ) coupled with that address made no sense.
Given we have the memory info list available in each minidump we could detect these instances and flag these crashes as impossible or inconsistent so that they're easier to analyze.
Note that there's more hints of inconsistency that could be detected: EXCEPTION_ACCESS_VIOLATION_EXEC crashes in areas that are executable, or EXCEPTION_ACCESS_VIOLATION_* crashes when the disassembled instruction doesn't contain any memory accesses (we've seen those in CPU bugs too for example, the crashing instruction was a jump).

More examples of "impossible" crashes that this could help detect:

Crash when executing ucomiss instructions emulating an x86-64 CPU on an AArch64 host
Crash in [@ double_conversion::PowersOfTenCache::GetCachedPowerForBinaryExponentRange] on Gemini Lake-based Atom CPUs
Bug 1796126 - Crashes on AMD Zen 1 (family 23 model 1 stepping 1)
Bug 1863991 - Crash in [@ style::properties::cascade::Cascade::apply_non_prioritary_properties]
Bug 1820832 - Crash in [@ nsIFrame::GetParent]


Search documents with a pagination windows over 10000

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v14.21.3
Amplify CLI Version
12.1.1
What operating system are you using?
Ubuntu
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes have been made.
Describe the bug
When querying a Table with more than 10000 registers the query returns an empty response.
Examples: When I make the following query
query MyQuery {   searchDatas(filter: {dataSetId: {eq: "68ce97d7-61f5-4007-8441-d4465948eca6"}}, from: 9999, limit: 1) {     items {       id     }   } }
I get the following response:
{   "data": {     "searchDatas": {       "items": [         {           "id": "ab4e4bde-939c-4bbe-8774-f502126263cf"         }       ]     }   } }
Which is correct. But once in increment the limit to 2
query MyQuery {   searchDatas(filter: {dataSetId: {eq: "68ce97d7-61f5-4007-8441-d4465948eca6"}}, from: 9999, limit: 2) {     items {       id     }   } }
the response is empty:
{   "data": {     "searchDatas": {       "items": []     }   } }
I have checked the response is empty when the sum of from and limit is bigger than 10000
I guess elasticsearch should be returning null because this param exceeds the index.max_result_window size.
Is there a way to use the scroll API of ElasticSearch using amplify? I need to recover all the registers of this table.
Thanks in advance for the help <3
Expected behavior
I expect to be able to get all the registers of the table.
Reproduction steps

Make  a table and make it searchable
Add more than 10000 registers to the table
Make a "search" query where the from and limit sum is over 10000

Project Identifier
No response
Log output

# Put your logs below this line

Additional information
No response
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

Hey @GuillermoRivero :wave: thanks for raising this! I'm going to transfer this over to our API repo for better assistance and tracking purposes


[CARBONDATA-2750] Updated Documentation for Local Dictionary Support

What has been added?
Described about increase in memory footprint in local dictionary.
Added to reduce block size when local dictionary is enabled,

[x] Any interfaces changed?
NA
[x] Any backward compatibility impacted?
NA
[x] Document update required?
Document updated.
[x] Testing done
Please provide details on
- Whether new unit test cases have been added or why no new tests are required?
- How it is tested? Please attach test report.
- Is it a performance related change? Please attach the performance test report.
- Any additional information to help reviewers in testing this change.
NA
[x] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.
NA

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/6235/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/7871/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/6594/

LGTM


Add experimental option to run unary-stream RPCs on a single Python thread.

Benchmarking revealed that context switching and lock contention led to a considerable amount of overhead in executing RPCs taking the "integrated" code path, which used multiple threads.
Overall, this PR has been shown to consistently decrease end-to-end latency of unary-stream RPCs by around 6.5% on Intel x86-64 workstations. Additional testing involving pinned cores and disabling Intel Turbo revealed that, under non-ideal thermal conditions, this win may degrade to around 2.5%.
An experimental channel option consumed only by the Python layer and not passed to core has been added to activate the single-threaded code path, since it cannot fulfill the grpc.Future interface.
This change was tested both in OSS using bazel and in the Google codebase with Blaze, using various sanitizers, including ASAN and MSAN. I was originally concerned that the change to channel.pyx.pxi would result in a memory leak, but this was not born out by testing.
At the moment, testing this code path is manual, since activating it across the entire test suite would require manual instrumentation and parametrization of every existing unit test. I have filed an issue to track this work.
This PR resolves https://github.com/grpc/grpc/issues/20741.

The TODO was added just a few lines down.

Known failures:

https://github.com/grpc/grpc/issues/20436
https://github.com/grpc/grpc/issues/18111


Migrate To New Build System

Make is really annoying to maintain. It's also somewhat antiquated compared to CMake or Meson.

We're going with CMake as Meson does not support globbing.

Turns out CMake has some assumptions that don't make it ideal for our use. SCons or rethinking our Makefile from the ground up seem to be the best options at this point.

We need to migrate all of the Panix kernel compilation into a Makefile in the kernel directory. From there we need to have a master Makefile that compiles all libraries and then the kernel.

Merged with #150


Views

Features added in this PR:

[x] Implemented the design from the wireframes for creating views

Thank you so much @Ibizugbe  🙏


Gopkg.*,pkg/generator/templates.go: update to kubernetes 1.11.2

this continues https://github.com/operator-framework/operator-sdk/pull/391 @hasbro17 PTAL

    	memcached_test.go:223: Building operator docker image
    	memcached_test.go:226: error: exit status 1
    		Command Output: Error: failed to build: (building memcached-operator...
    		vendor/github.com/operator-framework/operator-sdk/pkg/k8sclient/client.go:31:2: cannot find package "k8s.io/client-go/restmapper" in any of:
    			/home/travis/gopath/src/github.com/example-inc/memcached-operator/vendor/k8s.io/client-go/restmapper (vendor tree)
    			/home/travis/.gimme/versions/go1.10.3.linux.amd64/src/k8s.io/client-go/restmapper (from $GOROOT)
    			/home/travis/gopath/src/k8s.io/client-go/restmapper (from $GOPATH)
    		)

@wongma7 @hasbro17 I think the test is failing because the generated operator is not using this branches SDK code.
What is the best way to either make the generated code point to this branch for the test or do we ignore e2e tests?
IMO we should consider updating the tests, to always pull the branch that is being tested of the sdk. But I don't know if we should block this PR?
/cc @AlexNPavel

This should be using our code, not sure why it is failing: https://github.com/operator-framework/operator-sdk/blob/master/test/e2e/memcached_test.go#L72
I'll look at this more in depth later and see if I can figure out what's going on

@shawn-hurley The e2e test actually does make sure that for the generated operator the current PR branch of the SDK is vendored.
https://github.com/operator-framework/operator-sdk/blob/master/test/e2e/memcached_test.go#L72-L73
The problem we're doing this post dep ensure which ran against the master branch of the SDK which does have a dependency on k8s.io/client-go/restmapper. So that's never added to the vendor.
If the initial dep ensure ran against this PR then k8s.io/client-go/restmapper would be a transitive dependency of pkg/sdk and would be added to the vendor.
It's always always a bit tricky when we update pkg/sdk that introduces new transitive dependencies.

I think we can fix how we run this test and have it run dep ensure against this PR and then get the correct transitive dependencies.
Instead of just replacing the vendored SDK directory directly after running dep ensure, we can have the test get the Git-SHA or revision of the current PR and update the test-operator's Gopkg.toml to use the current PR's revision.
PR_REVISION=git rev-parse HEAD
sed -i 's|branch = "master"|revision = "$PR_REVISION"|g' Gopkg.toml

# Run dep ensure to update the vendored SDK and its transitive deps with the current PR
dep ensure

I think you're going to have to change the dep source as well, depending on travis variables, But I think this approach will be less error-prone IMO

Due to the way that dep works, we cannot fix this with dep (remote references like the ones github/travis use are not supported). We simple have to merge this and then check if travis's master build works.

Travis exposes the following envs:
TRAVIS_PULL_REQUEST_SHA  gives us the HEAD of the current PR. We use this as the revision.
TRAVIS_PULL_REQUEST_SLUG  gives us the owner_name/repo_name of the fork of the PR. We'll use this as the Source in for the sdk constraint.
So we can update the Gopkg.toml accordingly in our test to vendor the PR commit.

New PR open with fix ^

@wongma7 Can you please rebase your PR from master. With #525 we should be able to properly test your changes.

The test is still failing but this time the operator is built and run successfully. Its just not reconciling correctly as we expect it to (i.e create a memcached deployment for a memcached CR).
@wongma7 Can you do a manual test with the example on the README/user-guide to test out if an operator with your changes can still watch and use the client correctly. I'm going to verify that myself.

LGTM Thank you!

LGTM

LGTM


Export parseBoundary

In some cases I need to use parseBoundary to handle grpcgateway-content-type

You don't follow .golangci.yaml rules to have comments on exported functions


Modify VSCode typescript import preferences

Modifies the import preferences (non-relative imports) for VSCode. This forces the IDE to use non-relative paths (i.e. "@/*" path aliases) when automatically importing files.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.03%) to 91.224%

Totals

Change from base Build<PHONE_NUMBER>:
-0.03%

Covered Lines:
4629

Relevant Lines:
4950

💛  - Coveralls


Producer: add listener for bytes written to topic

This is a prerequisite for https://github.com/elastic/apm-ingest-service/issues/478
This change allows us to record the number of bytes written to a topic, as we will be using the information for throttling purposes.
Because apm-queue shouldn't be concerned about throttling matters, this PR adds a generic listener in the form of a kgo.HookProduceBatchWritten. The code that creates the producer may pass an optional listener function to be notified of writes to the topic.

Looks like the tests are already failing in main. Not sure what this is about yet


149 Fix agent's missing registry entries warning on Windows agents

What does this PR do?
The error wording was overall not accurate and in many cases not overly
useful so now we clearly specify that this is something that only
happens on server-provided credentials and the warning has been dialed
down to a notice since this is more common than node-provided
authentication.
What ticket does this PR close?
Connected to #149
Checklists
Change log

[ ] The CHANGELOG has been updated, or
[x] This PR does not include user-facing changes and doesn't require a CHANGELOG update

Test coverage

[ ] This PR includes new unit and integration tests to go with the code changes, or
[ ] The changes in this PR do not require tests
[x] Deferred to #117

Documentation

[ ] Docs (e.g. READMEs) were updated in this PR, and/or there is a follow-on issue to update docs, or
[x] This PR does not require updating any documentation

LGTM!


The .env file not loaded when using Miniflare 2

Hello !
I love this plugin and I think I just found a bug with the new version of Miniflare : I don't have any environment variables.
I checked a little bit and that's part of the breaking change of the v2 :

When using the API, wrangler.toml, package.json and .env are no longer automatically loaded from their default locations.

So I suppose we just need to add the options that they are showing in the "breaking change" in this part of the code, and that would resolve the bug : https://github.com/Aslemammad/vite-plugin-cloudflare/blob/main/packages/vite-plugin-cloudflare/src/cli.ts#L70-L73
Thank you for this great plugin again ! 🔥

Hello, How are you doing? Sorry for not seeing this issue! I don't know what the problem with GitHub notifs is.
What do you think the name should be? you got any suggestions?
And thank you for using this plugin; I'm happy.

Hello !
I'm not sure to understand you're question, you would like me to submit you names but I dont know names of what :/
Because I was just talking about the breaking change with Miniflare v2 so I'm a bit lost here ahah
Thank you and have a good day !

Sure, I'll work on that soon! no need to confuse yourself, I'm going to take it :smile:


CIV-14751 Manage Stay Event Configurations

PR for https://tools.hmcts.net/jira/browse/CIV-14751 & https://tools.hmcts.net/jira/browse/CIV-15168

Closed as merged as part of a separate branch.


How and Why to Un-Reset Tailwind's CSS Reset

source: devto
devToUrl: "https://dev.to/swyx/how-and-why-to-un-reset-tailwind-s-css-reset-46c5"
devToReactions: 19
devToReadingTime: 3
devToPublishedAt: "2020-04-04T13:04:49.296Z"
devToViewsCount: 2126
title: How and Why to Un-Reset Tailwind's CSS Reset
published: true
category: tutorial
tags: Tailwind, CSS, Nextjs, TailwindCSS, Tech
slug: tailwind-unreset
canonical_url: https://www.swyx.io/writing/tailwind-unreset

2021 edit: note that tailwind typography now comes with a not-prose class that unsets typography styles

2023 update: you can also do:
.some-class {
	all: revert; /* locally remove tailwind styles */
}

Tailwind CSS comes with a great CSS Reset, called Preflight. It starts with the awesome Normalize.css project, and then nukes all default margins, styling, and borders for every HTML element. This is so that you have a consistent, predictable starting point with which to apply your visual utility classes separate from the semantic element names.
That's great. So why would you want to unreset a CSS Reset?!

Note from Adam Wathan - they are working on a Tailwind plugin to do this for you properly rather than my janky unofficial solution. See also his talk on Tailwind CSS Best Practices.

The Why
Without unresetting, here's how this post you're reading would look on my own demo site:

This is because this blogpost is authored in Markdown, processed through JDown, and then rendered into our Next.js app with React's dangerouslySetInnerHTML API. Despite the name, this is the main way to inject externally generated HTML into Preact/React pages:

However, this content comes without any Tailwind classes, and because I'm writing this in Markdown, there's really no way to add the Tailwind classes in to each element - nor really would you want to.
The solution, prescribed on the Tailwind docs, is to Add Base Styles for the components you want to render like "normal". Effectively doing a CSS "Un-reset"!
The How
I'm not the first to this idea - and a quick trip to Google yielded this Unreset.scss file. Assuming you're using SASS, you could basically copy it over to your tailwind.scss and namespace it under an unreset class:
.unreset {
  // paste unreset.scss here!
}

And then in your JSX, you can add that unreset class in:

Job done! Right?
The How - Tailwind style!
Nah, I still don't love it. First of all, any customization to colors and margins that you've done won't be respected, because you've "Un-Reset" them to magic numbers. Your blog content will look inconsistent from the rest of your site 💩
The Tailwind Way™ to do it would be to go through all the unreset.css styles and translate them to Tailwind classes as far as possible, so that they will conform as close as possible.
.unreset {
  a {
    @apply text-blue-700 underline;
  }
  p {
    @apply my-4;
  }
  // etc...
}

Since Tailwind's Preflight CSS Reset doesn't reset absolutely everything, you should really diff Preflight against unreset.css in order to figure out what to unreset, so as not ship excess CSS.
Sound like a chore? It is. I've done it for you here!. You can also see it in action on this demo.
Video Demo
I recorded this as a video for my ongoing Dev.to CMS project!

Youtube Link: https://youtu.be/iLEYtgBezhs
Dev.to Embed: {% youtube iLEYtgBezhs %}

Conclusion
Here's my demo site after unresetting:

Of course, like everything Tailwind, feel free to customize to match your exact usecase. I just helped you get started.
That's it for this blogpost, thanks for reading!

How to remove a special base reset rule,like remvoe button?

no idea, just set css properties to initial?

如何删除特殊的基本重置规则，如删除按钮？

  * {
    all: revert;
  }

Like others new to Tailwind I was a little bit gobsmacked by how brutal Tailwind's reset is, and a google search brought me to your article. I added your "unreset" scss and noticed that compiled, it adds over 1500 lines of css! As a web dev it just seems wrong to me that we have to ship extra styles to the browser to just get back to basically default styles. But as you mention in your note, Tailwind now has a prescribed way of doing what you do in your article via the typography plugin. It works the same way by using a parent class to style all the article contents, but only adds around 800 extra lines of css. In light of that, it seems like a better option. Anyway I appreciate this article and your insight!

Man thank you so much, i was researching things like this for my WSIWYG editor, when parsing the result from the editor, tailwind affects it and disable them. So this  blog was superb!

you can disable the preflight in your tailwind.config.js so you can use your own reset or normalize styles
module.exports = {
corePlugins: {
preflight: false,
}
}

Looks like the Gist link is dead, the new location is probably:

https://gist.github.com/swyxio/28c25962485101ca291ec1947b9d0b3e

@systemkrash but sometimes u only want to locally disable it


Update validation code to match order submission spec

The specs for the order types was a little unclear but has been updated to show exactly what order types can be sent and with which TIF flags. The validation code in the protos needs updating to match these clarified specs. Mainly around FOK/IOC with LIMIT/PEGGED orders

Decided this change is not needed until negative offsets are brought back in.
Closing.


Update dependencies + work around govuk_tech_docs.

Update all the Rubygems dependencies as far as possible.
Had to specify a couple of indirect dependencies missing from govuk_tech_docs and avoid html-pipeline >= 3, which appears to be incompatible with govuk_tech_docs for now.
Group the dev/test-only dependencies in the Gemfile so we can skip them in the build later.

No probs! I'll have a look at what's up with tech_docs gem if I have time.
Looks like I need to rebase this.


Ebert Support

Consider adding Ebert badge to identify code smells.
Example:
https://ebertapp.io/github/thomasvincent/mantl
Project should open its own account.

Another choice also is codeclimate. It's free for open source projects.

I also have many CI tools in my cloud infrastructure, I wouldn't mind hosting some tools for Mantl if needed.

For the time being we may have to go that route.

I know of quite a few projects that use codeclimate.

code climate works.

I think this can wait for 2.1, since most of our stuff is Ansible

This will not happen for Mantl 1.x as we are only supporting 1.x as an LTS. There is too much bit-rot to build upon and we have to get away from maintaining a k8s fork. We are currently planning the re-write of Mantl from scratch, you can view the progress and contribute here: https://github.com/cloud-endeavor/endeavor


Fix flag in CONTRIBUTING

Codecov Report

Merging #205 (5309fd7) into main (c6fe935) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main      #205   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            2         2
  Lines          185       185
=========================================
  Hits           185       185

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 c6fe935...5309fd7. Read the comment docs.


Lucene.Net.Store.Azure.AzureDirectory: Enable usage with a sasuri and existing containers

Is there an existing issue for this?

[X] I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.
No response
Describe the solution you'd like
I'd like the Lucene.Net.Store.Azure.AzureDirectory to be enabled for usage with sasuri with existing containers instead of using the storage account connectionstring. Reason: to constrain access to containers for multiple usages on the same storage account.
Additional context
No response

@Shazwazza - Thanks for the info.
It seems this is not pertinent to our project as it is not something we maintain here, so I am closing this.


Support manage the model and policy through CRD

doc: https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/

@ComradeProgrammer


docs(stripUnit): add quotes to strings in example

@bhough Didn't get a chance to run the build yet, need another PR for that?

@AndersDJohnson nope we're good, I merged it and ran the docs build as part of #236. Thanks again for the contribution.


[Emergency] Magica Logia sheet update

Changes / Comments
Disabled legacy sanitization.
The CSS in this sheet is seriously broken right now.
I would appreciate if you could merge this branch quickly.
Thanks.
Roll20 Requests
Comments are very helpful for reviewing the code changes. Please answer the relevant questions below in your comment.

[x] Does the pull request title have the sheet name(s)? Include each sheet name.
[x] Is this a bug fix?
[ ] Does this add functional enhancements (new features or extending existing features) ?
[ ] Does this add or change functional aesthetics (such as layout or color scheme) ?
[ ] If changing or removing attributes, what steps have you taken, if any, to preserve player data ?
[ ] If this is a new sheet, did you follow Building Character Sheets standards ?

If you do not know English. Please leave a comment in your native language.

Character Sheet Info Roll20 Internal Use only.


WIP: Add Device Support

WIP PR for supporting scheduling of node devices.
This PR includes:

The complete API protos.
The complete controlapi implementation, with tests
Partial implementation of the scheduling logic, with tests.

Currently, left to do:

[ ] Support updating nodes.
[ ] Cover some more test cases in the scheduler

Additionally, there is an architectural problem: currently, it is possible for the same device to be added to the node as many DeviceClasses. This may pose a problem, because it is possible that a non-optimal choice of devices could be made, causing a task to not fit when it could.
For example, consider a task that requests two FooDevice, and one BarDevice. Consider a node which has 1 device, /dev/foo, which is of class FooDevice, 1 device /dev/bar, which is of class BarDevice, and 1 device, /dev/foobar, which is of both class FooDevice and BarDevice.
The task should fit with the mapping FooDevice -> /dev/foo, FooDevice -> /dev/foobar, BarDevice -> /dev/bar
However, currently the scheduler may opt to start by mapping BarDevice -> /dev/foobar, which would mean that there aren't 2 free FooDevice remaining, and the filter would fail.
It's unclear to me at this time how to get around that problem cleanly. I have the gut feeling that the issue maps to some NP-space problem.

Please sign your commits following these rules:
https://github.com/moby/moby/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "device-support-scheduler" git@github.com:dperny/swarmkit-1.git somewhere
$ cd somewhere
$ git rebase -i HEAD~842353461120
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.


Rename repo ai-inspector to giskard-client

GC-1
Users should be able to pip install giskard
Project: Giskard Client
Reporter: alex
Created: 2022-03-30

Not valid anymore, closing


cherry pick 5434

Description
Cherry pick of #5435
I re-request review because ISO4 has the processing event state

Processing this pull request

Merged into branches iso4 in 102dc3a2ad911bfa44396b4ac04a97632da8b407


Updated for relevancy with the latest release and added more supporting ...

This page had old content so I took the opportunity to update it and tested it with the v0.10.0 release. It works as advertised.

Thanks for updating.


Checkmarx producer

This component reads checkmarx output and serialises into Dracon format
Keep in mind that it does not orchestrate a remote checkmarx instance, instead it expects to find its input in the scratch directory
TODO:

[ ] add OPTIONAL orchestration of remote Checkmarx

superseeded by #124


Only export images that have export settings

This will prevent a lot of junk/placeholder images being added to the source tree when generating.

covered by #323


Fixed settings file, added addMessage and addSetting

Added addMessage method to shorten the addDefaultMessages method, and make it more easy to add new messages and read
Added addSetting method to shorten the addDefaultSettings method, and make it more easy to add new messages and read
Fixed and tested settings file
Added settings and messages for upcoming inventory block support

Merged. Branch Cleanup-and-Shrik can be deleted now.


It's just broken

at 99% when It's rendering it just give you an error message, note I didn't change any of the setting

well at least give the error message, not much can be done to help without it

it says : IndexError('list index out of range')


fix: do not change custom error texts

Fixes: #239

Coverage increased (+0.3%) to 90.182% when pulling 14ef3d9d952b642941e218185cc72b12ed11d060 on mahovich:patch-12 into 933acdd3888c47994c0b6677205e1d9161cd6a71 on yiminghe:master.

@yiminghe


Add the ability to rotate the x-hasura-admin-secret?

When working with contractors we have to pass this information on to our development env, it would be nice if we had the ability to rotate this to ensure access is terminated to prevent any issues.

I like this suggestion. Another suggestion, somewhat related, is to implement rotation + JWKS: https://github.com/nhost/hasura-auth/issues/123

This has been possible for a while actually.


Restrict creating organisations by user

Allows to restrict, wether an user is allowed to create organisations. See #177.

Current coverage is 3.03% (diff: 0.00%)

Merging #193 into master will decrease coverage by <.01%

@@            master      #193   diff @@
========================================
  Files           33        33
  Lines         8106      8115     +9
  Methods          0         0
  Messages         0         0
  Branches         0         0
========================================
  Hits           246       246
- Misses        7840      7849     +9
  Partials        20        20

Powered by Codecov. Last update cf045b0...d41807e

Please never update vendored libs, it needs to be integrated upstream first and than updated via govendor

Thanks for your reviews. I reverted the changes you suggested to remove. The field AllowCreateOrganization is set to true in migration script.
Please review again.

It already looks pretty fine, but you want to set a default value to true, otherwise registered users are not allowed to create organizations

added default value both in  CreateUser-function and in xorm-annotation

It would be useful if the site administrator was given the option to decide which permissions to give by default to new users.

This PR needs to be delayed until the branch of 1.0 anyway.

LGTM. While I do agree with @strk, that can be implemented at a later point :)

Please resolve the conflicts

conflicts resolved

LGTM


Panel should be dockable in other places in the workspace.

I've got all this unused horizontal space, and the build window insists on taking up the bottom!
It'd be really nice if I could instead have it open on the left or right of the window to reclaim precious vertical space.

Work for this actually begun by in #88 but never reached mergable status.

This is in a branch now, panel-orientation. I'd appreciate if you wanted to test it!

I changed the panel orientation, but no matter where I put it nothing happens (it's stuck at the bottom and the height settings don't do anything).

scratch that - install problem. seems to be working fine, aside from "build finished" being in a weird place (stuck to the bottom of the output, instead of the bottom of the panel)

When you have the panel where? Could you include a screenshot?

Right side.

This was fixed by #180


Unable to install kivy.deps.sdl2 kivy.deps.glew to use with pyinstaller

Versions

Python:2.7.13
OS: DOCKER   resin/rpi-raspbian   stretch
Kivy: Master branch
Kivy installation method: pip install git+https://github.com/kivy/kivy.git@master

Description
I am trying to use pyinstaller to build an executable inside a docker container. I can get pyinstaller to make an executable, but the package is missing the SDL binaries it needs to run.
The docs say to use:
from kivy.deps import sdl2, glew

and
coll = COLLECT(exe, Tree('examples-path\\demo\\touchtracer\\'),
               a.binaries,
               a.zipfiles,
               a.datas,
               *[Tree(p) for p in (sdl2.dep_bins + glew.dep_bins)],
               strip=False,
               upx=True,
               name='touchtracer')

but I get this when trying to install those dependencies
pi@raspberrypi:~/ $ sudo pip install kivy.deps.sdl2
Collecting kivy.deps.sdl2
  Could not find a version that satisfies the requirement kivy.deps.sdl2 (from versions: )
No matching distribution found for kivy.deps.sdl2

These packages are available in pip search though
kivy.deps.angle (0.1.7)           - Repackaged binary dependency of Kivy.
kivy.deps.glew (0.1.10)           - Repackaged binary dependency of Kivy.
kivy.deps.glew_dev (0.1.10)       - Repackaged binary dependency of Kivy.
kivy.deps.gstreamer (0.1.13)      - Repackaged binary dependency of Kivy.
kivy.deps.gstreamer_dev (0.1.13)  - Repackaged binary dependency of Kivy.
kivy.deps.sdl2 (0.1.18)           - Repackaged binary dependency of Kivy.
kivy.deps.sdl2_dev (0.1.18)       - Repackaged binary dependency of Kivy.

When running:
[INFO   ] [Logger      ] Record log in /usr/src/app/logs/kivy_18-09-25_0.txt
[INFO   ] [Kivy        ] v1.11.0.dev0, git-42c0a90, 20180925
[INFO   ] [Python      ] v2.7.13 (default, Nov 24 2017, 17:33:09)
[GCC 6.3.0 20170516]
[INFO   ] [Factory     ] 195 symbols loaded
[INFO   ] [Image       ] Providers:  (img_tex, img_dds, img_ffpyplayer, img_gif, img_pil, img_sdl2 ignored)
[CRITICAL] [App         ] Unable to get any Image provider, abort.
[INFO   ] [Logger      ] Record log in /usr/src/app/logs/kivy_18-09-25_1.txt
[INFO   ] [Kivy        ] v1.11.0.dev0, git-42c0a90, 20180925
[INFO   ] [Python      ] v2.7.13 (default, Nov 24 2017, 17:33:09)
[GCC 6.3.0 20170516]

I will note that if I install all the kivy dependencies and run my app like normal inside the docker container, everything works fine.

Kivy.deps.xxx are only used in windows and those pyinstaller guides you followed were for windows, not linux.

try to install
pip3 install kivy-deps.glew
pip3 install kivy-deps.sdl2
or
pip install kivy-deps.glew
pip install kivy-deps.sdl2

The same here. Coudn't install.
[image: Mailtrack]
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&
Remetente
notificado por
Mailtrack
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&
15/09/20
17:57:22
Em ter., 15 de set. de 2020 às 16:45, cristianmejiaarias <
<EMAIL_ADDRESS>escreveu:

try to install
pip3 install kivy-deps.glew
pip3 install kivy-deps.sdl2
or
pip install kivy-deps.glew
pip install kivy-deps.sdl2
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/kivy/kivy/issues/5944#issuecomment-692939183, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AQT5FCXRJZ2O5MHBWFQ7YK3SF676VANCNFSM4FW7ZFYQ
.


From obsidian to Google Calendard not write

If I write - [ ] prova obsidian ⏫ 🛫 2024-11-09 , when I click in synchronization toogle becomes - [ ] prova obsidian ⏫ 🛫 2024-11-09  ^18XDBC5TADKW0 but not write in calendar


feat: why did my tx fail

What type of PR is this? (check all applicable)

[ ] Refactor
[x] Feature
[ ] Bug Fix
[ ] Optimization
[ ] Documentation Update

Description
Display logs from why-did-my-tx-fail for failed txs
Issue ticket number and link
closes #1929
Checklist:

[ ] I have performed a self-review of my code.
[ ] I have tested the change on desktop and mobile.
[ ] I have added thorough tests where applicable.
[ ] I've added analytics and error logging where applicable.

Screenshots (if appropriate):

:tada: This PR is included in version 1.233.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

@diwakergupta more examples of errors:

Some logs are confusing or user-unfriendly. We'll be looking into improving the logs.


Damage does not calculate in to the modifiers

Describe the bug
Damage does not calculate in to the modifiers on Foundry v12
To Reproduce
If applicable, provide steps to reproduce this issue
Screenshots
If applicable, add screenshots to help explain your problem.
Version Numbers
PLEASE PROVIDE YOUR FOUNDRY, SYSTEM, and MODULE VERSIONS (where applicable)
Foundry: 12 Build 328
wfrp4e: 7.2.4
wfrp4e-core: 5.07
wfrp4e-starter-set:
wfrp4e-rnhd:
wfrp4e-eis:
wfrp4e-ua1:
wfrp4e-dotr:
wfrp4e-archives1:
wfrp4e-middenheim:
wfrp4e-archives1:
wfrp4e-pbtt:
wfrp4e-altdorf:
wfrp4e-ua2:
wfrp4e-owb1:
wfrp4e-horned-rat:
wfrp4e-empire-ruins:

After asking Rupert to do some more testing, Issue does not appear on hex or gridless scenes.
It may be caused by Foundry implementing it's own grid measurement system and its settings:

Switching scene to "Gridless" - fixed the issiue.

Not sure why this was closed as gridded scenes should work

Oh, yeah. Just got overexcited when it started working. What can I say, I'm a simple man with modest expectations towards life ;)


add server-side print docs

Add docs for https://github.com/kubernetes/features/issues/515
@smarterclayton
Is server-side print on by default? (i.e. no feature gate to document here https://kubernetes.io/docs/reference/feature-gates/ ?)
cc @smarterclayton @soltysh

/milestone v1.10

I went ahead and marked this do-not-merge/work-in-progress.  Thanks for your contributions!

@smarterclayton @bradtopol this should be ready for review. Thanks

Is server-side print on by default? (i.e. no feature gate to document here https://kubernetes.io/docs/reference/feature-gates/ ?)

Yes, there's no knob, iirc.

/assign

@soltysh thanks, review comments addressed

/approve
@soltysh if you could check changes and add an /lgtm, we can get this one merged. Thanks!

@soltysh @smarterclayton friendly ping

/lgtm


install_compilers being called twice...

...causing lots of "stale NFS handles" as two installs go on at once!

At least it appears so:

One email:
RESULT CODE: 0

ERROR OUTPUT:
--2019-04-04 03:34:18--  https://dlang.org/install.sh

Another...
received:        Tue, 02 Apr 2019 20:05:59 -0700 (PDT)

Cronic detected failure or error output for the command:
bash -c sudo /home/ubuntu/compiler-explorer-image/update_compilers/install_=
compilers.sh nightly

RESULT CODE: 1

ERROR OUTPUT:
rm: cannot remove '/opt/compiler-explorer/rust-nightly/lib/rustlib/i686-unk=
nown-linux-gnu/lib/librustc_borrowck-c667f875c90f85ab.so': Stale file handl=
e

maybe cronic sends more than one email? I can't see how it could be running twice?
Two separate emails:
Mon, Apr 1, 2019 at 5:05 AM (Delivered after 7 seconds)
Mon, Apr 1, 2019 at 5:05 AM (Delivered after 7 seconds)
Perhaps this isn't actually a problem, it's that one is stderr output and one is "and the whole thing failed" ?

Hnm it can't be cronic: it's cron that sends the email (which is the output of the command it runs!)
SO CONFUSED.

I added instrumentation...and...
email one (10:05pm local time)
Cronic detected failure or error output for the command:
bash -c sudo /home/ubuntu/compiler-explorer-image/update_compilers/install_compilers.sh nightly

RESULT CODE: 1

ERROR OUTPUT:
rm: cannot remove 'ldc-latest-ci/ldc/import/core/stdcpp/string_view.d': Stale file handle
rm: cannot remove 'ldc-latest-ci/ldc/import/core/stdcpp/new_.d': Stale file handle
rm: cannot remove 'ldc-latest-ci/ldc/import/core/stdc/wchar_.d': Stale file handle
rm: cannot remove 'ldc-latest-ci/ldc/import/core/stdc/wctype.d': Stale file handle
rm: cannot remove 'ldc-latest-ci/ldc/import/core/stdc/fenv.d': Stale file handle
rm: cannot remove 'ldc-latest-ci/ldc/import/core/stdc/time.d': Stale file handle
rm: cannot remove 'ldc-latest-ci/ldc/import/core/stdc/string.d': Stale file handle
rm: cannot remove 'ldc-latest-ci/ldc/import/core/stdc/stdio.d': Stale file handle
rm: cannot remove 'ldc-latest-ci/ldc/import/core/stdc/assert_.d': Stale file handle
rm: cannot remove 'ldc-latest-ci/ldc/import/core/stdc/stdarg.d': Stale file handle
rm: cannot remove 'ldc-latest-ci/ldc/import/core/stdc/tgmath.d': Stale file handle
rm: cannot remove 'ldc-latest-ci/ldc/import/core/stdc/float_.d': Stale file handle
rm: cannot remove 'ldc-latest-ci/ldc/import/core/stdc/ctype.d': Stale file handle

STANDARD OUTPUT:
Starting installation at Fri Apr  5 03:05:01 UTC 2019
Installing nightly builds
Skipping install of rust 1.5.0 as already installed
Skipping install of rust 1.6.0 as already installed
...

Email two (same time):
Cronic detected failure or error output for the command:
bash -c sudo /home/ubuntu/compiler-explorer-image/update_compilers/install_compilers.sh nightly

RESULT CODE: 1

ERROR OUTPUT:
rm: cannot remove 'ldc-latest-ci/ldc/import/std/datetime/stopwatch.d': Stale file handle
rm: cannot remove 'ldc-latest-ci/ldc/import/std/internal/math/gammafunction.d': Stale file handle
rm: cannot remove 'ldc-latest-ci/ldc/import/std/internal/windows': Stale file handle
rm: cannot remove 'ldc-latest-ci/ldc/import/std/internal/memory.d': Stale file handle
rm: cannot remove 'ldc-latest-ci/ldc/import/std/internal/unicode_comp.d': Stale file handle
rm: cannot remove 'ldc-latest-ci/ldc/import/std/container/slist.d': Stale file handle
rm: cannot remove 'ldc-latest-ci/ldc/import/std/container/binaryheap.d': Stale file handle
rm: cannot remove 'ldc-latest-ci/ldc/import/std/regex/internal/tests2.d': Stale file handle
rm: cannot remove 'ldc-latest-ci/ldc/import/std/regex/internal/parser.d': Stale file handle
rm: cannot remove 'ldc-latest-ci/ldc/import/std/algorithm/comparison.d': Stale file handle
rm: cannot remove 'ldc-latest-ci/ldc/import/std/algorithm/mutation.d': Stale file handle
rm: cannot remove 'ldc-latest-ci/ldc/import/std/algorithm/internal.d': Stale file handle
rm: cannot remove 'ldc-latest-ci/ldc/import/std/bigint.d': Stale file handle
rm: cannot remove 'ldc-latest-ci/ldc/import/std/demangle.d': Stale file handle
rm: cannot remove 'ldc-latest-ci/ldc/lib/libphobos2-ldc-shared.so.2.0.85': Stale file handle
rm: cannot remove 'ldc-latest-ci/ldc/lib/LLVMgold-ldc.so': Stale file handle
rm: cannot remove 'ldc-latest-ci/ldc/lib/libldc_rt.xray-fdr.a': Stale file handle
rm: cannot remove 'ldc-latest-ci/ldc/lib/libldc-jit.so.85': Stale file handle
rm: cannot remove 'ldc-latest-ci/ldc/lib/libphobos2-ldc-debug-shared.so.2.0.85': Stale file handle
rm: cannot remove 'ldc-latest-ci/ldc/lib/libldc_rt.profile.a': Stale file handle
rm: cannot remove 'ldc-latest-ci/ldc/lib/libphobos2-ldc.a': Stale file handle
rm: cannot remove 'ldc-latest-ci/ldc/lib/libphobos2-ldc-shared.so.85': Stale file handle
rm: cannot remove 'ldc-latest-ci/ldc/lib/libdruntime-ldc-shared.so': Stale file handle
rm: cannot remove 'ldc-latest-ci/ldc/lib/libphobos2-ldc-debug.a': Stale file handle
rm: cannot remove 'ldc-latest-ci/ldc/lib/libphobos2-ldc-debug-shared.so.85': Stale file handle
rm: cannot remove 'ldc-latest-ci/ldc/lib/libldc_rt.xray-profiling.a': Stale file handle
rm: cannot remove 'ldc-latest-ci/ldc/lib/libldc-jit.so.2.0.85': Stale file handle
rm: cannot remove 'ldc-latest-ci/ldc/lib/libdruntime-ldc-debug-shared.so': Stale file handle
rm: cannot remove 'ldc-latest-ci/ldc/lib/libldc_rt.xray-basic.a': Stale file handle
rm: cannot remove 'ldc-latest-ci/ldc/lib/libphobos2-ldc-lto.a': Stale file handle
rm: cannot remove 'ldc-latest-ci/ldc/lib/libldc_rt.asan.a': Stale file handle

STANDARD OUTPUT:
Starting installation at Fri Apr  5 03:05:01 UTC 2019
Installing nightly builds
Skipping install of rust 1.5.0 as already installed
Skipping install of rust 1.6.0 as already installed

ARGH seems two set off at the exact same time. Which then of course explains why they interfere with each other (the Stale NFS handle is a sign of "accessing a file that has just been deleted by something else")

I just can't see how they're set off at the same time:
ubuntu@admin-node ~/compiler-explorer-image> crontab -l
<EMAIL_ADDRESS>PATH=/home/ubuntu/compiler-explorer-image/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

# m h  dom mon dow   command
00 00 * * * cronic bash -c "git -C /home/ubuntu/compiler-explorer-image pull"
05 00 * * * cronic bash -c "crontab < /home/ubuntu/compiler-explorer-image/crontab.admin"
10 00 * * * cronic /home/ubuntu/compiler-explorer-image/admin-daily-builds.sh
00 03 * * * cronic bash -c "sudo /home/ubuntu/compiler-explorer-image/update_compilers/install_binaries.sh"
05 03 * * * cronic bash -c "sudo /home/ubuntu/compiler-explorer-image/update_compilers/install_compilers.sh nightly"
00 04 * * * cronic bash -c "sudo /home/ubuntu/compiler-explorer-image/update_compilers/install_libraries.sh nightly"
15 04 * * * cronic bash -c "sudo /home/ubuntu/compiler-explorer-image/update_compilers/install_nonfree_compilers.sh"
00 09 * * * cronic /home/ubuntu/compiler-explorer-image/remove_old_compilers.sh
05 09 * * * cronic bash -c "ce builds rm_old 7"

Latest experiment, edited crontab to make it trigger then got two emails:
Cronic detected failure or error output for the command:
bash -c sudo /home/ubuntu/compiler-explorer-image/update_compilers/install_=
compilers.sh nightly

RESULT CODE: 1

ERROR OUTPUT:
mkdir: cannot create directory =E2=80=98ldc-latest-ci=E2=80=99: File exists

STANDARD OUTPUT:
Starting installation at Fri Apr  5 12:42:01 UTC 2019, my pid 20850
Installing nightly builds
...

And second email...
Cronic detected failure or error output for the command:
bash -c sudo /home/ubuntu/compiler-explorer-image/update_compilers/install_=
compilers.sh nightly

RESULT CODE: 0

ERROR OUTPUT:
--2019-04-05 13:10:34--  https://dlang.org/install.sh
Resolving dlang.org (dlang.org)... <IP_ADDRESS>, 2607:fc50:1:ff02::5:0
Connecting to dlang.org (dlang.org)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 22382 (22K) [application/x-sh]
Saving to: =E2=80=98install.sh=E2=80=99

     0K .......... .......... .                               100%  175M=3D=
0s

2019-04-05 13:10:35 (175 MB/s) - =E2=80=98install.sh=E2=80=99 saved [22382/=
22382]

######################################################################## 10=
0.0%

######################################################################## 10=
....lots of error output
....
STANDARD OUTPUT:
Starting installation at Fri Apr  5 13:10:01 UTC 2019, my pid 18339
Installing nightly builds
Skipping install of rust 1.5.0 as already installed
Skipping install of rust 1.6.0 as already installed
Skipping install of rust 1.7.0 as already installed
Skipping install of rust 1.8.0 as already installed

DIFFERENT PIDS!!!!!!

Doesn't seem like there's two crons running (looks like someone else on the admin node has checked this too :D )

Apr 05 12:42:01 admin-node sudo[20849]: pam_unix(sudo:session): session opened for user root by (uid=0)
Apr 05 13:08:01 admin-node cron[829]: (ubuntu) RELOAD (crontabs/ubuntu)
Apr 05 13:10:01 admin-node CRON[18334]: pam_unix(cron:session): session opened for user ubuntu by (uid=0)
Apr 05 13:10:01 admin-node CRON[18335]: (ubuntu) CMD (cronic bash -c "sudo /home/ubuntu/compiler-explorer-image/update_compilers/install_compilers.sh nightly")
Apr 05 13:10:01 admin-node sudo[18338]:   ubuntu : TTY=unknown ; PWD=/home/ubuntu ; USER=root ; COMMAND=/home/ubuntu/compiler-explorer-image/update_compilers/install_compilers.sh nightly
Apr 05 13:10:01 admin-node sudo[18338]: pam_unix(sudo:session): session opened for user root by (uid=0)
Apr 05 13:10:34 admin-node sudo[20849]: pam_unix(sudo:session): session closed for user root

seems only one cron (this from journalctl -u cron) and only one instance fired up. CONFUSED

Apr  5 13:10:01 localhost CRON[18335]: (ubuntu) CMD (cronic bash -c "sudo /home/ubuntu/compiler-explorer-image/update_compilers/install_compilers.sh nightly")
Apr  5 13:10:35 localhost sSMTP[18430]: Creating SSL connection to host
Apr  5 13:10:35 localhost sSMTP[18430]: SSL connection using ECDHE_RSA_AES_256_GCM_SHA384
Apr  5 13:10:36 localhost sSMTP[18430]: Sent mail for<EMAIL_ADDRESS>(221 Bye) uid=1000 username=ubuntu outbytes=3127770
Apr  5 13:17:01 localhost CRON[18656]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Apr  5 13:32:26 localhost systemd-timesyncd[629]: Network configuration changed, trying to establish connection.
Apr  5 13:32:26 localhost systemd-timesyncd[629]: Synchronized to time server <IP_ADDRESS>:123 (ntp.ubuntu.com).
Apr  5 13:51:16 localhost systemd[1]: Starting Cleanup of Temporary Directories...
Apr  5 13:51:17 localhost systemd[1]: Started Cleanup of Temporary Directories.
Apr  5 13:54:38 localhost sSMTP[18963]: Creating SSL connection to host
Apr  5 13:54:38 localhost sSMTP[18963]: SSL connection using ECDHE_RSA_AES_256_GCM_SHA384
Apr  5 13:54:39 localhost sSMTP[18963]: Sent mail for<EMAIL_ADDRESS>(221 Bye) uid=1000 username=ubuntu outbytes=170099

more debug info

Just ran a test with "echo $$" and only got one  email... argh.
Then tried a sudo... same deal.
Now trying cronic...

cronic didn't give me two emails either (tested with:
56 16 * * * cronic bash -c "sudo echo Hello XX > /dev/stderr"

)
I AM SO CONFUSED!

I was thinking that maybe root had a crontab with the same line, but that wasn't the case. Nor is there another admin instance alive. It's very odd.

Right! All very weird.
I just made install_compilers exit early and re-tested and it's only doing one... did someone else kill a second cron? Gonna re-run a full install from cron again and see what happens.

@partouf found it!! The builder node was also running the crontab (though an old one that didn't update).
Looking back the evidence was in the emails:
[CEAdmin] Cron <ubuntu@builder-node> cronic bash -c "sudo /home/ubuntu/compiler-explorer-image/update_compilers/install_compilers.sh nightly"

was one of the emails.... the other being from "ubuntu@admin-node"

While we don't fully understand how this came to be; I suspect it was some path-dependent setup in the builder the first time I set it up. Gonna close, and then keep an eye on this one :)


[Task] Scope npm package to @thenewboston/sdk

Task
Contributors are able to complete this task and earn thenewboston coins.  Check out the labels to learn how much you can earn for contributing by completing this task.  Please make sure to be honest if you wish to contribute by saying you can't finish this and we can just un-assign you with no harm done!  There is no point in delaying tasks from being completed for miscommunication!

Overview
since there may be other npm packages by thenewboston org, it may be beneficial to scope this package with “@thenewboston”.
Behavior
Rename name in package.Json from “thenewboston” to “@thenewboston/sdk”
/* code examples are awesome */

Please ask for this task to be assigned to you and earn and its sweet reward 😉
Remember to include your account number in your PR description for us to pay you 💰
** Pull Requests **
All Pull Request should be made to development branch, read contributors guild for more information about contributing

if that's just a renaming issue i could do that...

@angle943 what do you think about the naming convention

I'm just looking at how Sentry names its client side libraries (across different platforms).
https://docs.sentry.io/platforms/javascript/

React Native: @sentry/react-native,
Node: @sentry/node
Client: @sentry/browser

@denistsoi @zinoadidi yeah i agree, we should rename this. tagging @buckyroberts

Perhaps
@thenewboston/client/ @thenewboston/browser - that way you can separate between
npm supports TS/JS - however, i dont suspect us using something like WASM to be deployed via npm (tho a possibility)
@thenewboston/node
@thenewboston/ui

I like @thenewboston/js-sdk

@buckyroberts awaiting input from you :)

@thenewboston/js-sdk seems fine to me

i'm down actually for @thenewboston/js-sdk


Failing tests

Hi,
I am using this for a small personal project, great gem. I wanted to add support for returning queries in languages other than English, but later realised Yahoo didn't support this feature. None the less, forked and pulled the repo and noticed a few tests failing - perhaps the json that is returned changed slightly?
Fixed the tests to be all green. API still works fine either way, but if you are interested I can make a PR with my fixes.
If there is anything else you'd like to see added or changed lmk, I'm happy to contribute.

Hi @lmiller1990 - thanks for letting me know! I've corrected the behaviours causing test failures, and pushed a new release with the fixups (v.1.3.0).


Bug with isFuture flag

Current day tile is incorrectly marked as "future one".
Te replicate:
        $builder = new HeatmapBuilder(
            periodInterval: PeriodInterval::Weekly,
            period: new CarbonPeriod($firstEpisode->watched_at, "1 week", Carbon::now()->endOfYear()),
            arrayAccessIndex: "watched_at",
            decorator: new Decorator("sky"),
            alignedToEndOfPeriod: true,
        );

Screenshot:

Current week's tile receives $futureTileClass in tile's decorator.  It should not.

This is pretty weird behavior, because for me this bug only happens when period is from lets say June 1 and date is set to last week of June, but when i set May or any other month that is before as period start it works fine.

Could this be a Carbon bug? inFuture: $date->isFuture() is responsible for checking if date is in future and then decorator gives  tile opacity to mark it as future tile, so i don`t see any other way that could be broken.

Current week is marked both as current and future


images in yaml file are not updated when releases are tagged

What issue would you like to bring attention to?
Currently the tags that you do to release a new version do not include the charts being updated, this makes it harder for people to install a specific version. If you look at plugins such as multus and flannel you will see that they also update the yaml files when tagging.
What is the impact of this issue?
It makes providing instructions on how to install specific versions harder and increases the risk that people will have mismatches between the version of the yaml file and the version of the software.
Do you have a proposed response or remediation for the issue?
As part of the release process you could add updating the image tags in the yaml file to reflect the new tag.

In this scenario imagePullPolicy should also be removed (or set to pull if not present).


Multiple reviews generated for multiline mypy error

I'm using action with following step configuration:
    - name: Mypy review
      uses: tsuyoshicho/action-mypy@v3
      with:
        reporter: github-pr-review
        level: warning
        fail_on_error: true

As an example, following is a multi-line mypy error when overriding superclass property in an incompatible way:
/home/runner/.../file.pyi:28:6: error: Signature of "error_log" incompatible with supertype "_Validator"
/home/runner/.../file.pyi:28:6: note:      Superclass:
/home/runner/.../file.pyi:28:6: note:          def error_log(self) -> _ErrorLog
/home/runner/.../file.pyi:28:6: note:      Subclass:
/home/runner/.../file.pyi:28:6: note:          @overload
/home/runner/.../file.pyi:28:6: note:          def error_log(self) -> int
/home/runner/.../file.pyi:29:5: error: Return type "int" of "error_log" incompatible with return type "_ErrorLog" in supertype "_Validator"

The error came from a single diff hunk, so I was expecting a single reviewdog action. Instead, it generated 7 independent reviews on the same pull request, each containing one line, and all of them are attached to the same diff.

Work in progress...

Hi @abelcheung san,
https://github.com/tsuyoshicho/test-action-mypy/pull/1
Simply reproduction PR
Basically, mypy report only error and work fine it.
If your project mypy.ini report note:, option mypy_flags use to suppress it.
If you have a problem that you haven't set up that way,
I want you to make a minimum reproduction PR and report it here. (like above PR)

As an example, following image shows the behavior I want to see -- multiple lines which are related to the same error can be grouped together.

FYI
https://github.com/jordemort/action-pyright
use rdjson format (rich error report support),
mypy json report https://github.com/python/mypy/issues/10816
I will think about it.

Ouch, you're right, it is not easy to handle mypy error in its current state. It is fine to put the idea on hold until mypy has done something to improve the situation.

Thanks a lot. (report and PR)

https://github.com/tsuyoshicho/action-test-repo/pull/21
Reproduce PR create in my test repo.
This code is same as abel's test code.
@abelcheung san
Please close PR and remove forked test-action-mypy repository.
This original test-action-mypy repository are other user test repo...Sorry.
I remove my forked repository too.

@tsuyoshicho OK it's done.

Note:
https://github.com/python/mypy/issues/10816#issuecomment-1113861214

FYI:
Relation File Format information.
reviewdog was diagnostics parsing tool, and that support json file.
https://github.com/reviewdog/reviewdog/tree/master/proto/rdf#rdjson
action-pyright using converted rdjson from original json.

When mypy implements Pyright's format json, converting the json using already existing action-pyright's method will be solved this issue.

@abelcheung san
With no progress on JSON support, I've introduced a workaround.
You can ignore the notice of note.
Please try setting according to your needs.
Release 3.10.0 https://github.com/tsuyoshicho/action-mypy/releases/tag/v3.10.0
test result for ignore note: https://github.com/tsuyoshicho/action-test-repo/pull/27
This issue remains open.

@tsuyoshicho I have tried the ignore_note setting and it works fine here. It seems mypy developers don't have interest in implementing JSON support, so your workaround is probably the best approach right now.

JSON output has been merged
Development of JSON output support will begin.

mypy has 2 option

--hide-error-context suppress hint note
output JSON and ignore note


How add  header for Directus client

I need every request add header device_code. Is it possible?

This will set header for shared instance. sdk.custom is simply Dio client that was intended for custom endpoints. In next version I'll make sdk.client public.
sdk.custom.options.headers['Custom-Header'] = 'some-value';

This will set header for shared instance. sdk.custom is simply Dio client that was intended for custom endpoints. In next version I'll make sdk.client public.
sdk.custom.options.headers['Custom-Header'] = 'some-value';

From 0.5.1 you have access to sdk.client where you have full access to Dio client that is used

From 0.5.1 you have access to sdk.client where you have full access to Dio client that is used


Fix TestUploadPackWithContextOnRead test in plumbing/transport/test/upload_pack.go

Signed-off-by: Kuba Podgórski<EMAIL_ADDRESS>

Discard is an io.Writer on which all Write calls succeed without doing anything.

context was canceled (we should wait till context is Done)