Cannot find module 'strip-ansi' on install

When trying to install a project depending on node-sass I get the following error and node-sass fails to install:
><EMAIL_ADDRESS>install /home/ben/Documents/Code/react-responsive-audio-player/node_modules/node-sass
> node scripts/install.js

module.js:538
    throw err;
    ^

Error: Cannot find module 'strip-ansi'
    at Function.Module._resolveFilename (module.js:536:15)
    at Function.Module._load (module.js:466:25)
    at Module.require (module.js:579:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/home/ben/Documents/Code/react-responsive-audio-player/node_modules/string-width/index.js:2:17)
    at Module._compile (module.js:635:30)
    at Object.Module._extensions..js (module.js:646:10)
    at Module.load (module.js:554:32)
    at tryModuleLoad (module.js:497:12)
    at Function.Module._load (module.js:489:3)

I've tried different versions and nothing works.

NPM version (npm -v): 6.0.0
Node version (node -v): 8.9.0
Node Process (node -p process.versions):

{ http_parser: '2.7.0',
  node: '8.9.0',
  v8: '6.1.534.46',
  uv: '1.15.0',
  zlib: '1.2.11',
  ares: '1.10.1-DEV',
  modules: '57',
  nghttp2: '1.25.0',
  openssl: '1.0.2l',
  icu: '59.1',
  unicode: '9.0',
  cldr: '31.0.1',
  tz: '2017b' }

Node Platform (node -p process.platform): linux
Node architecture (node -p process.arch): x64
node-sass version (node -p "require('node-sass').info"): Can't install so can't give you this
npm node-sass versions (npm ls node-sass): Again I can't install but I tried with 4.5.3, 4.7.1, 4.7.2, 4.9.3.

I was able to solve by upgrading from<EMAIL_ADDRESS>to<EMAIL_ADDRESS>

Same problem here :(


Not aware of updates

I was disappointed to find that juliaup

does not notify me that one of my channels is out of date
is not able to update that channel via juilaup update

Perhaps I'm doing something wrong, but this feels like something juliaup should support.
x@X ~ % julia +beta
               _
   _       _ _(_)_     |  Documentation: https://docs.julialang.org
  (_)     | (_) (_)    |
   _ _   _| |_  __ _   |  Type "?" for help, "]?" for Pkg help.
  | | | | | | |/ _` |  |
  | | |_| | | | (_| |  |  Version 1.8.0-rc1 (2022-05-27)
 _/ |\__'_|_|_|\__'_|  |  Official https://julialang.org/ release
|__/                   |

julia> versioninfo()
Julia Version 1.8.0-rc1
Commit 6368fdc6565 (2022-05-27 18:33 UTC)
Platform Info:
  OS: macOS (x86_64-apple-darwin21.4.0)
  CPU: 4 × Intel(R) Core(TM) i5-8210Y CPU @ 1.60GHz
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-13.0.1 (ORCJIT, skylake)
  Threads: 1 on 2 virtual cores
Environment:
  LD_LIBRARY_PATH = /usr/local/lib

julia>
x@X ~ % juliaup status
 Default  Channel  Version          Update
-------------------------------------------
          beta     1.8.0-rc1+0~x64
          lts      1.6.6+0~x64
       *  release  1.7.3+0~x64
x@X ~ % juliaup update
x@X ~ % juliaup status
 Default  Channel  Version          Update
-------------------------------------------
          beta     1.8.0-rc1+0~x64
          lts      1.6.6+0~x64
       *  release  1.7.3+0~x64
x@X ~ % juliaup update +beta
Error: '+beta' cannot be updated because it is currently not installed.
x@X ~ % juliaup update beta
x@X ~ % juliaup status
 Default  Channel  Version          Update
-------------------------------------------
          beta     1.8.0-rc1+0~x64
          lts      1.6.6+0~x64
       *  release  1.7.3+0~x64
x@X ~ % julia +beta
               _
   _       _ _(_)_     |  Documentation: https://docs.julialang.org
  (_)     | (_) (_)    |
   _ _   _| |_  __ _   |  Type "?" for help, "]?" for Pkg help.
  | | | | | | |/ _` |  |
  | | |_| | | | (_| |  |  Version 1.8.0-rc1 (2022-05-27)
 _/ |\__'_|_|_|\__'_|  |  Official https://julialang.org/ release
|__/                   |

julia>

Me too, now 13 hours after of  julia v1.8.0-rc3 released.
(base) test@DESKTOP-NRERBN7:~$ juliaup st
 Default  Channel  Version          Update
-------------------------------------------
       *  rc       1.8.0-rc1+0~x64
          release  1.7.3+0~x64
(base) test@DESKTOP-NRERBN7:~$ juliaup self update
Checking for self-updates
Juliaup unchanged on channel 'release' - 1.6.4
(base) test@DESKTOP-NRERBN7:~$ date
Sat Jul 16 21:28:49 CST 2022
(base) test@DESKTOP-NRERBN7:~$ juliaup list |grep 1.8
 1.8.0-beta1      1.8.0-beta1+0~x64
 1.8.0-beta1~x64  1.8.0-beta1+0~x64
 1.8.0-beta1~x86  1.8.0-beta1+0~x86
 1.8.0-beta3      1.8.0-beta3+0~x64
 1.8.0-beta3~x64  1.8.0-beta3+0~x64
 1.8.0-beta3~x86  1.8.0-beta3+0~x86
 1.8.0-rc1        1.8.0-rc1+0~x64
 1.8.0-rc1~x64    1.8.0-rc1+0~x64
 1.8.0-rc1~x86    1.8.0-rc1+0~x86
 beta             1.8.0-rc1+0~x64
 beta~x64         1.8.0-rc1+0~x64
 beta~x86         1.8.0-rc1+0~x86
 rc               1.8.0-rc1+0~x64
 rc~x64           1.8.0-rc1+0~x64
 rc~x86           1.8.0-rc1+0~x86

For crying out loud it's been less than 24 hours...

I thought it was auto-syncing of the julia release.

https://github.com/JuliaLang/juliaup/issues/131

I see..

It is coming! We had a hiccup that a publishing key for the Windows Store had expired, that slowed things down further.

I feel like I'm being obtuse here, but AFAICT, this still hasn't been fixed:
shell> juliaup status
 Default  Channel  Version          Update
-------------------------------------------
          beta     1.8.0-rc1+0~x64
          lts      1.6.6+0~x64
       *  release  1.7.3+0~x64

shell> julia +beta
               _
   _       _ _(_)_     |  Documentation: https://docs.julialang.org
  (_)     | (_) (_)    |
   _ _   _| |_  __ _   |  Type "?" for help, "]?" for Pkg help.
  | | | | | | |/ _` |  |
  | | |_| | | | (_| |  |  Version 1.8.0-rc1 (2022-05-27)
 _/ |\__'_|_|_|\__'_|  |  Official https://julialang.org/ release
|__/                   |

julia>

shell> juliaup update beta

shell> julia +beta
               _
   _       _ _(_)_     |  Documentation: https://docs.julialang.org
  (_)     | (_) (_)    |
   _ _   _| |_  __ _   |  Type "?" for help, "]?" for Pkg help.
  | | | | | | |/ _` |  |
  | | |_| | | | (_| |  |  Version 1.8.0-rc1 (2022-05-27)
 _/ |\__'_|_|_|\__'_|  |  Official https://julialang.org/ release
|__/                   |

@LilithHafner Did you update your juliaup? It has a hard-coded list of available Julia versions, so old juliaup versions do not know of recent Julia versions.

@LilithHafner How did you install juliaup? It should auto-update if you use any of the officially supported ways to install it.

I don't recall, but my scrollback history has
brew install juliaup

And then a few lines later (perhaps the first command didn't work as I'd hoped)
brew link --overwrite juliaup

In that case brew is in charge of updating juliaup. I don't know whether it does that automatically, but we are pushing new versions to brew continuously.

One major problem with manual Julia installs is that every user has to figure out how to get update streams on their own device. this problem will exist until https://github.com/JuliaLang/juliaup/issues/131 is implemented.
Juliaup remains unaware of updates on my system. This issue is a duplicate of #131.


explain since format and give examples

relates to #29449
Please provide the following information:
- What I did
change command line info
- How I did it
used the power of vim
- How to verify it
waited for the CI to complete
- Description for the changelog
doc for cli docker logs --since
Write a short (one line) summary that describes the changes in this
pull request for inclusion in the changelog:
doc for cli docker logs --since
- A picture of a cute animal (not mandatory but encouraged)
imagine a santa clause in front if a christmas tree

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "since-flag" git@github.com:tronicum/docker.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

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

Please update this file as well? https://github.com/docker/docker/blob/master/docs/reference/commandline/logs.md

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "since-flag" git@github.com:tronicum/docker.git somewhere
$ cd somewhere
$ git rebase -i HEAD~842353810016
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.

there you go. signed (and squashed ;)

@AkihiroSuda could you have a look please? i guess the windows test ist not failing because of my patch...


Fix repetition issue

A new row would be created every time setProperty was called due to auto increment

Sorry for the delay in seeing this! GitHub never notified me about your Issue or the PR. I’ll try to review this weekend.
Thanks for the help!


BAU Completely remove REST API GW From Core Front

Proposed changes
What changed
BAU Completely remove REST API GW From Core Front
modified:   deploy/template.yaml

Why did it change
BAU Completely remove REST API GW From Core Front
modified:   deploy/template.yaml

Issue tracking

PYIC-XXXX

Checklists
Environment variables or secrets

[ ] No environment variables or secrets were added or changed

[ ] Documented in the README
[ ] Added to deployment repository
[ ] Added to local startup repository

Other considerations

[ ] Update README with any new instructions or tasks

This is no longer needed, closing this PR down.


opsmx-spinnaker-operator for 1.21.2 release

Thanks submitting your Operator. Please check below list before you create your Pull Request.

Flat operator directory structure is obsolete from 23-rd of October 2019, only nested directory structure will be accepted.

New Submissions

[ ] Does your operator have nested directory structure?
[  ] Have you selected the Project Community Operator Submissions in your PR on the right-hand menu bar?
[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?

[ ] Have you tested your Operator in all supported installation modes?
[ ] Have you considered whether you want use semantic versioning order?
[ ] Is your submission signed?

Updates to existing Operators

[ Y ] Did you create a ci.yaml file according to the update instructions?
[ Y ] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[ Y ] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[ Y ] Have you tested an update to your Operator when deployed via OLM?
[ Y ] Is your submission signed?

Your submission should not

[ Y ] Modify more than one operator
[ Y ] Modify an Operator you don't own
[ Y ] Rename an operator - please remove and add with a different name instead
[ Y ] Submit operators to both upstream-community-operators and community-operators at once
[ Y ] Modify any files outside the above mentioned folders
[ Y ] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[ ] Description about the managed Application and where to find more information
[ ] Features and capabilities of your Operator and how to use it
[ ] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[ ] Human readable name and 1-liner description about your Operator
[ ] Valid category name1
[ ] One of the pre-defined capability levels2
[ ] Links to the maintainer, source code and documentation
[ ] Example templates for all Custom Resource Definitions intended to be used
[ ] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

/ok-to-test

/ok-to-test

@dvropsmx since you are previous contributor, can you have a look at changes if ok with you?

@dvropsmx since you are previous contributor, can you have a look at changes if ok with you?

/lgtm

/lgtm

@mvalarh @dvropsmx  is our team member, and he is on vacation period and I have taken up the process, can you please help me in getting this PR Approved

@mvalarh @dvropsmx  is our team member, and he is on vacation period and I have taken up the process, can you please help me in getting this PR Approved

/retest

/retest

@mvalarh can you please help me in getting the error why this check is getting failed,

@mvalarh can you please help me in getting the error why this check is getting failed,

/test deploy-operator-on-openshift

/test deploy-operator-on-openshift

@J0zi  can you please help us what is missing and the test case is getting failed.

@J0zi  can you please help us what is missing and the test case is getting failed.

@vkvamsiopsmx issue was that commits were not squashed. Test was failing at the begining. But I applied a solution to handle such cases. So please wait for the last test, I hope.

@vkvamsiopsmx issue was that commits were not squashed. Test was failing at the begining. But I applied a solution to handle such cases. So please wait for the last test, I hope.

/test deploy-operator-on-openshift

/test deploy-operator-on-openshift

@J0zi seems like the check got failed again, can you please help us in getting fixed as early as possible

@J0zi seems like the check got failed again, can you please help us in getting fixed as early as possible

@vkvamsiopsmx debugging...

@vkvamsiopsmx debugging...

/test deploy-operator-on-openshift

/test deploy-operator-on-openshift

/test deploy-operator-on-openshift

/test deploy-operator-on-openshift

/test deploy-operator-on-openshift

/test deploy-operator-on-openshift

/test deploy-operator-on-openshift

/test deploy-operator-on-openshift

@vkvamsiopsmx found an isue:
sync {"update" "test-operators/install-bwjks"} failed: CustomResourceDefinition.apiextensions.k8s.io "opsmxspinnakeroperators.charts.helm.k8s.io" is invalid: spec.names.singular: Invalid value: "Opsmxspinnakeroperator": a DNS-1035 label must consist of lower case alphanumeric characters or '-', start with an alphabetic character, and end with an alphanumeric character (e.g. 'my-name',  or 'abc-123', regex used for validation is '[a-z]([-a-z0-9]*[a-z0-9])?')

is here https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/operator-framework_community-operators/2931/pull-ci-operator-framework-community-operators-master-deploy-operator-on-openshift/1347629656458661888#1:build-log.txt%3A2676

@vkvamsiopsmx found an isue:
sync {"update" "test-operators/install-bwjks"} failed: CustomResourceDefinition.apiextensions.k8s.io "opsmxspinnakeroperators.charts.helm.k8s.io" is invalid: spec.names.singular: Invalid value: "Opsmxspinnakeroperator": a DNS-1035 label must consist of lower case alphanumeric characters or '-', start with an alphabetic character, and end with an alphanumeric character (e.g. 'my-name',  or 'abc-123', regex used for validation is '[a-z]([-a-z0-9]*[a-z0-9])?')

is here https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/operator-framework_community-operators/2931/pull-ci-operator-framework-community-operators-master-deploy-operator-on-openshift/1347629656458661888#1:build-log.txt%3A2676

@J0zi have corrected and recomitted, but still one check got failed, can you please help here.

@J0zi have corrected and recomitted, but still one check got failed, can you please help here.

@J0zi can you pleas help on my request

@J0zi can you pleas help on my request

deploy-operator-on-openshift is green :tada:

deploy-operator-on-openshift is green :tada:

@J0zi Can you please help me to know when this new operator will be published and will be reflected in the Operatorhub.io.

@J0zi Can you please help me to know when this new operator will be published and will be reflected in the Operatorhub.io.

@J0zi any update on my above request ?

@J0zi any update on my above request ?


Microsoft Azure AD Backend not mentioned in README

Just noticed you support Azure AD but don't mention it in the README.
This gist shows what to do: https://gist.github.com/jayme-github/138316675f29981e1e00a2e1ef78b345

Since the port to python-social-auth, the section in the readme got removed, the backends are listed just in the documentation files.


No way to make a result with an no trailing newline pass the diff

You get something like this
< left / > right
 +-----------------------------------+---------+
 | Lint                              | Status  |
 +=============================================+
 | duplicated-trailers               | enabled |
 |-----------------------------------+---------|
 | subject-not-separated-from-body   | enabled |
 |-----------------------------------+---------|
 | subject-longer-than-72-characters | enabled |
 |-----------------------------------+---------|
 | body-wider-than-72-characters     | enabled |
 +-----------------------------------+---------+
<

Which isn't representable with the code block

What do you think the logic would be for this? Strip all trailing newlines? Strip one trailing newline?

I'm not really sure, this was actually a bug in my app, but if I was testing
echo -n "."

It wouldn't be.


add support to install ecdsa root ca

https://github.com/FiloSottile/mkcert/issues/378

testing locally, works

https://github.com/FiloSottile/mkcert/issues/378#issuecomment-1109232115


Add Aritra Ghosh Dastidar Markdown

Project Request

Proejct Request to Add [your name] markdown file and route

Field
Description

Name
Aritra Ghosh Dastidar

Email
<EMAIL_ADDRESS>

Github
Aritraghoshdastidar

What do you what to contribute to:

[ ] HackFest GDSC Contributor
[ ] Hacktober Fest Contributor

Please add your github link instead of github username.


Decouple message handling from middleware

@remixz Thanks this is really nice!
Issue
I'd like to be able to use this bot within an app that has existing middleware.
Fix
Pull out the logic that handles incoming json from the middleware function. This allows for the server to be instantiated like so:
let app = express()

app.get('/', (req, res) => {
  return bot._verify(req, res)
})

app.post('/', (req, res) => {
  bot._handleMessage(req.body.entry)
  res.end(JSON.stringify({status: 'ok'}))
})

http.createServer(app).listen(3000)

while keeping the current implementation intact.
Thanks!

This looks good! Do you mind fixing the failing standard tests? Looks like you have a few semicolons.

@remixz , fixed semi-colons

Coverage remained the same at 100.0% when pulling f3634d03226c5519e6de98e3be13d09849dc9488 on psealock:master into<PHONE_NUMBER>748079148a4c22c54c95309706a6d3 on remixz:master.

Perfect, thank you! 😄  I've published it as 2.1.0.


Add a community events calendar to community page

Fixes: #59

Hm, I was expecting a dedicated page for the calendar instead of hiding further down on the community page
Can we also modify it to use UTC time instead of Berlin time?

https://deploy-preview-147--conda-dot-org.netlify.app/community#events-calendar - LGTM!
Agreed on the UTC timezone.

@kenodegard,
I think putting this calendar on its own page is a good idea. In order to do this in the best possible way, I had to slight reorganize the website. The "community" page is now under the "learn" section. It still retains its top level navigation link though. The event calendar is underneath the "community" section.
I think this should make it easier for users to browse the content on the site in the future, and it's also more inline with what https://www.nebari.dev/ does, which  I like.
cc: @jaimergp

I'm also using the "redirects" plugin to handle redirecting site visitors to the correct page.

I am afraid ctz=local does not work as expected (I see times as in LA) and we will have to resort to something like this SO answer proposes.

Thanks for reporting that @jaimergp. We also realized that the time zones are not working. Unfortunately, a solution like like the one mentioned in that SO article would be pretty tricky to implement.

Maybe a stop-gap measure would be to just present it in a single timezone (UTC?) and then make sure to mention that above the calendar?

+1 for UTC as default.


Ensure apt-get update is run during Docker builds.

Fixed #590, by preventing caching of layers which can prevent builds
from completing when a step fails, causing the package repository to
become out-of-date and the install step to fail.

bors r+

bors retry


Removing tags from Grape Juice Isometrics post 0.4.0 update

Noticed interesting interaction between Grape Juice Isometrics and Terrain-Height-Tools, when all were updated to their most up to date version.
Module and Foundry Versions:
Grape Juice Isometrics: 0.11.308.0
Grape Juice Isometrics Pro: 0.11.308.0
Terrain Height Tools: 0.4.4 (behavior begins starting with v 0.4.0, downgrading to 0.3.7 fixes interaction)
libWrapper: <IP_ADDRESS>
Foundry V11 Build 315
Issue: After making any changes to a map with terrain-height-tools while the map was set to isometric with the isometrics mod, interacting with tokens or reloading the scene breaks the tokens visually and disables the isometric toggle.
Steps to recreate:

Install all listed mods (pro is not needed, issue is with base version)
set scene to isometric mode
load tokens (for visual evidence)
make change with terrain height tools
reload scene or move tokens

I have raised this issue in the bugs section of the isometric mod discord, but after looking deeper into it, seems to be related more heavily to terrain-height-tools nuking the isometric mods tags
before making any changes to the terrain, I can run
game.scenes.viewed?.getFlag("grape_juice-isometrics","is_isometric)
and it will return true so long as you have the toggle on
after making changes to terrain and running the same command results in "undefined"
simply running
game.scenes.viewed?.flags
before making changes shows both modules flags intact, but after making a change to the terrain, all tags related to isometrics have been removed. I would imagine this is the same for other mods that use tags, however I cannot confirm as I have not found another mod in my setup that relies on those flags.
Screenshots attached

To add on, I manually set a test flag on lib-wrapper and recreated the steps to cause the issue, attached are screenshots of all tags.
Set the flag

Before making terrain changes

After terrain changes

Thanks for testing that. If you're already on 0.4.x then that should be a safe change for you to make.
The problem that it was solving was that old data was being merged with new data when migrating from the v0.3.x data structure to the v0.4.x version. So I tried to make it clear out the existing data in that flag, but it must be clearing out all data from all flags.
I'm going to change it so that it stores whether or not a migration was done, and if so it'll explicitly unsetFlag first, before then using setFlag, which should be safer and not delete other flags.

@mhildom I've pushed v0.4.5 which should resolve the issue. If you can give it a go please, as there doesn't seem to be a public v11 version of Grape Juice Isometrics that I can test on.

@Wibble199 Just updated to v0.4.6, issue seems to be resolved, able to use it properly and tags are being maintained. Thanks for the fast response!


Remove Disable Touch debug project setting

Follow-up to https://github.com/godotengine/godot/pull/70202.
This project setting was only implemented and iOS and likely served no purpose outside of debugging during development of engine features.
It was also located in a confusing location in the project settings editor, as it was located below a root category (which appears in bold and is normally not seen as clickable by users).
See https://github.com/godotengine/godot/issues/70158#issuecomment-1356052626.

Thanks!


feat: add German language support

This is more professional sounding German language support than the pull request that was created 9h earlier and that I was not aware of at the time. 😉

@tedzards509 I have added a new commit in which I integrated almost all your recommendations. Thank you! :)

@Sunsurfer89 Thank you for your recommendations. I added them to the PR. I would hope this PR gets merged soon. I like the project very much, but the time for merging PRs seems to be a bit slow, sadly. :)

@scastiel This PR seems to be complete. I think the German user base would appreciate the added language support. Would you be so kind as to merge it soon? :)

@scastiel I think it could also make sense to add translations for the home page and the page's meta data, like the title for example. Should we, in a follow-up PR, add translation keys for this as well?

@Sunsurfer89 Thank you for your recommendations. I added them to the PR. I would hope this PR gets merged soon. I like the project very much, but the time for merging PRs seems to be a bit slow, sadly. :)

I hope so, too. I have a use case in September and the other contributors to my expense group do not have the best English language skills... so any German translation would be great. And I really love this project, too. So, I hope for a quick release!

Thanks for this PR! As a native German I really appreciate your efforts. I can also confirm that these translations are really good 👍
Not trying to add additional delay, but shouldn't the files be called ger-GER (as in german) instead of de-DE like deutsch in order to follow the existing schema of the other files (like fi.json and also the other open PRs with es.json etc.)?

I would think that the current naming follows the ISO standard for German language in Germany. This is important as there might be different translations for German speakers in Austria or Switzerland :)

@max298 nope: DE-de is correct! Check out: https://en.m.wikipedia.org/wiki/ISO_3166-1_alpha-2
We have this discussion also far too often at work. ISO is the answer 😉

Amazing, thanks @chrisschuller for the translation, and thanks all for the reviews, you rock ❤


Initial integration event listner

Description
This PR will enable the Wholesale domain to subscribe to the MeteringPointCreatedEvent. This PR is still a work in progress but any early feedback will be greatly appreciated <3
References

#784

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@4e2039e). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #40   +/-   ##
=======================================
  Coverage        ?   87.50%
=======================================
  Files           ?        8
  Lines           ?       72
  Branches        ?        3
=======================================
  Hits            ?       63
  Misses          ?        8
  Partials        ?        1

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


chore: fix duplications

Description
Fix duplicated strings.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[ x] Refactor/improvement

How Has This Been Tested?
ui test
Checklist

[ ] My commit message is conventional
[ ] I have run pre-commit on all files before creating the PR
[ ] New and existing unit tests pass locally with my changes
[ ] I have checked my code and corrected any misspellings

:tada: This PR is included in version 1.11.0-beta.7 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


 Let's remove them.
Test plan
n/a

Artifacts tests are a huge mess right now. We don't write tests because of it, and we spend a lot of time updating existing tests when making changes. I'm trying to bring it to a more reasonable state in WB-13808.
First, I plan to consolidate all existing tests into the system_tests directory. Terminology like "functional" vs "integration" vs "unit" tests is arbitrary, see here. We will no longer use the mock server or yea, they are a pain.
Second, I want the tests directory structure to follow the code-under-test directory structure: i.e. tests for /a/b/c.py should be in <tests dir>/a/b/test_c.py. This way when you look at a piece of code it's immediately clear where to find its test and vice versa. Ideally I would like to put the test right next to the code-under-test, i.e. x.py should have test_x.py or tests/test_x.py in the same directory. But this would require changes to our CI config, so I'm not going to do that.
Third, I'll add missing tests. At this point I'll be able to tell what code is missing tests easily.


Document and refactor vm package

This PR is for addressing the 2 feedback I got from #841

the vm.New vm.New and v.ExecInstructions methods would profit from some minimal documentation, especially what all the "paths" actually mean. some of them seemed semi obvious..
same for RegisterExternalClass ExternalClass and vm.Method albeit those are relatively clear

@yannick can you give this a look?


Refresh without reloading the page.

Is there an existing issue for this?

[X] I have searched the existing issues

Package Version
Last
Current Behavior
I have a very simple dapp that I made with hooks.
It is a mint token contract with USDT.
For this I must first approve the tokens and then the mint.
The problem I have is that after approving the tokens, the buy function does not update and shows me the error that I do not have enough allowance. I have to refresh the site to make it work.
Expected Behavior
No response
Steps To Reproduce
`
// Aprove USDT
const { config: ApproveUSDT } = usePrepareContractWrite({
...TokenUSDTAddress,
functionName: "approve",
args: ["0x1c103ad0921c35abe1a5e396479922450D38Ad76", 1000000],
});
const { write: Approve, isLoading, isSuccess } = useContractWrite(ApproveUSDT);
// Buy token
const { config: BuyTokens } = usePrepareContractWrite({
...TokenPresaleAddress,
functionName: "buyTokens",
args: [BNBSend],
});
const { write: Buy} = useContractWrite(BuyTokens);`
Link to Minimal Reproducible Example (StackBlitz, CodeSandbox, GitHub repo etc.)
https://token-presale-usdt.vercel.app/
Anything else?

You'll need to wait for the transaction to be confirmed using useWaitForTransaction.


Chore: Remove node 6 and 7 from travis config

The build was failing presumably due to npm install not being strict with which patch version was being installed.
Installing locally with npm ci using node 7 and npm 6, the correct dependency versions were installed and the rollup build completed successfully.
We could update the travis config to use npm ci and install npm 6 but as 6 and 7 are old now, may as well drop them.
I have updated the travis config to use npm ci so that we don't have this issue in the future.


Filled some of the interfaces

Not all interfaces are done, but this will help speed things up.

Also, documentation still needs to be improved


8.0.0-preview2 issues

I tried out 8.0.0 preview 2 and couldnt get it to work for me. Only changes I made to my code working with version 7.6.104 was to change all SetCollectionValidator calls to use RuleForEach instead. (Edit - going back to version 7.6.104 but leaving these changes in places everything works as expected.)
1)Some of my tests are now failing with errors like:
Message: Test method
MyTestMethod threw exception:
System.MissingMethodException: Method not found: 'FluentValidation.IRuleBuilderInitial`2<!0,!!0> FluentValidation.AbstractValidator`1.RuleForEach(System.Linq.Expressions.Expression`1<System.Func`2<!0,System.Collections.Generic.IEnumerable`1<!!0>>>)'.

2)Trying to use async validation at runtime I get lots of errors, things like:
Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware:Error: An unhandled exception has occurred while executing the request.
System.Reflection.ReflectionTypeLoadException: Unable to load one or more of the requested types.
Could not load type 'FluentValidation.Validators.AsyncValidatorBase' from assembly 'FluentValidation, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7de548da2fbae0f0'.

Hi, all my tests are passing so not sure what's happening there. Please put together a small sample project that reproduces the issue and send it to me. Thanks.

RE: the second error, AsyncValidatorBase doesn't exist anymore. Looks like you have an intermediate assembly that's referencing an older version.

Yes, disregard. I cloned my project and now get lots of compiler errors due to classes I have that inherit from AsyncValidatorBase. Not sure why it was compiling and running (but then failing at runtime) in original location.
Ill have to try to update my code base correctly and try again.
BTW What is the new recommended approach for a Async validator? I have lots of validators that inherit from AsynCValidatorBase and implement IsValidAsync. I don't see anything called out in the upgrade guide.

Inherit from PropertyValidator, override IsValidAsync and ShouldValidateAsync.
ShouldValidateAsync should return context.IsAsync
I may actually reintroduce AsyncValidatorBase for preview 3 which essentially just does those 2 things.

So maybe wait until I’ve done this in preview3 if you make heavy use of AsyncValidatorBase

OK, thanks!

@slubowsky I had some other changes that I needed to do today, so I've gone ahead and pushed out preview3 which reintroduces AsyncValidatorBase

Got it. All seems to work. Thanks!


System.ArgumentOutOfRangeException: 'Index was out of range. (xlsx file)

This exception was originally thrown at this call stack:
System.ThrowHelper.ThrowArgumentOutOfRange_IndexException()
System.Collections.Generic.List.this[int].get(int)
System.Collections.ObjectModel.ReadOnlyCollection.this[int].get(int)
Sylvan.Data.Excel.XlsxWorkbookReader.IsDBNull(int)
Sylvan.Data.Excel.ExcelDataReader.GetValue(int)

I think all the issues you've had should be fixed with 0.1.8-b0003, which I just pushed to nuget.
It looks like have been using GetValue to access values. One thing to be aware of with that: GetValue will return values that are typed to the "schema" of the ExcelDataReader. By default, the schema is that every column will be read as a nullable string. The behavior of the GetValue method cannot be changed, because it is required to comply with the contracts that are expected of the base DbDataReader type. I've added GetExcelValue, which will return the value of the cell as represented in Excel. However, if you know the data type that is expected in a column, it is best to use the strongly-typed accessors GetDouble, GetDateTime, etc, as those are the most efficient; they don't box the values.

I've added some general-purpose tests that demonstrate code that is expected to work for all files, you can see that code here
To use these tests, set the environment variable SylvanExcelTestData to point to a folder containing excel files. Then when you run the tests it will verify that every file in the folder doesn't fail for this standard access patterns.


Improvements while drafting software chapter of my thesis

Improves:

MMS interface and outputs, including formatted tables for LaTeX
Organization of mixed FE solutions

Also base sapphire.Simulation class no longer has to derive from a custom class using an ordered_dict, because dicts are by default ordered in recent versions of Python.

Per a discussion I saw in the Firedrake mailing list, some of the current test failures (which also show up in the CRON job on master) may be related to changes in the default line search method per the changes discussed here: https://github.com/firedrakeproject/firedrake/pull/1471
Since all of the tests pass with my local build from back in March, I'm doing a new firedrake-install locally now.

At this point in my thesis, it makes more sense to freeze the Firedrake version. I already made a Docker image (just a version of the Firedrake Docker image) which I mostly used when running Sapphire while writing this chapter here: https://hub.docker.com/repository/docker/zimmerman/firedrake


Access violation on win10 during "cargo build" when ssh crate url

On Windows 10 with cargo 0.15.0-nightly (298a012 2016-12-20)

Create a new library with cargo new repro.
Set this as the Cargo.toml file:

[package]
name = "repro"
version = "0.1.0"

[dependencies]
some-module = { git = "ssh://github.com/rust-lang/not-a-valid-repo.git" }

Run cargo build. Then I get:

Thanks for the report! This may be a dupe of https://github.com/rust-lang/cargo/issues/3401 (unsure). Could you try out nightly Cargo and see if it's fixed for you?

Ah, that fixes it. I now get a "failed to authenticate" error instead of a crash, so it seems like it is a duplicate.


Indentation for html, js, stylus, and pug

fixes #7

That's a huge PR, thank you very much for it. I'm checking it tonight 😄

Don't be intimidated, the first commit is html5.vim's indentation which can be assumed to be working.

@bopjesvla It doesn't seem to indent html, jade or stylus when I try it. Do you need any specific extra plugin for this to work?

My guess is that this wasn't installed properly, or that you have a conflicting plugin. Can you verify that indent/vue.vim exists? If that's the case, can you install html5.vim and check if indentation works for you in HTML files?

Works great for me, tested with a clean and my everyday busy config. Indented HTML and JS and did not indent CSS. Hope to see that one added :smile:

I forgot to say, I did experience this: https://i.imgur.com/Byq7QK0.png
First line just says there was an error parsing that file.
As for the other two red lines, "No existe la variable" means "variable doesn't exist".
Nevertheless, it does seem to work as I mentioned.

Why not simply use runtime! indent/html.vim for html indentation?

@adriaanzon ...I can't believe it was this simple all along. That works.

@adriaanzon Where should this be added?

@posva in indent/vue.vim.
You could use $VIMRUNTIME/indent/scss.vim as an example:
if exists("b:did_indent")
  finish
endif

runtime! indent/css.vim

@adriaanzon Do you have a working example of this?
My indent/vue.vim is as follows but I indenting does nothing. Although new lines are created with the appropriate indentation level.
if exists("b:did_indent")
  finish
endif

runtime! indent/stylus.vim
let s:stylindent = &indentexpr

unlet b:did_indent
runtime! indent/pug.vim
let s:pugindent = &indentexpr

unlet b:did_indent
runtime! indent/javascript.vim
let s:jsindent = &indentexpr

unlet b:did_indent
runtime! indent/css.vim
let s:cssindent = &indentexpr

unlet b:did_indent
runtime! indent/html.vim
let s:htmlindent = &indentexpr

let b:did_indent = 1

It'd be great if you could create a pull request if your indent/vue.vim works better 😄

I only tried indenting html/css/js with runtime! indent/html.vim and that worked fine for me. Do you have an example of where js indenting failed for you?
You don't need to use runtime! for javascript and css because indent/html.vim already handles those for you.
For pug/stylus/others you would need to detect the regions where it's contained and then apply the indentexpr for that language. I'm quite familiar with indenting multiple languages in one file (did it for vim-blade) so I will have a look at this.

Closing this in favour of #23
Sorry @bopjesvla 😓


docs(packages): add package development guidelines

The missing guidelines on developing a package.

Alfred retest this please

Merging - Alfred has spent an 1hr 15min trying to test a README.md update.


Fixed problem with driver name.

Covers Driver with unit tests

A new inspection was created.

The inspection completed: 1 updated code elements

A new inspection was created.

The inspection completed: 1 updated code elements


How do you add a node type to an OnPremise Cluster?

How do you add a node type to an OnPremise Cluster?

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

ID: a6803a0f-eda8-acf7-c598-d4679833de08
Version Independent ID: f441710f-8f4e-d46c-5eab-132940f4445f
Content: Add a node type to an Azure Service Fabric cluster
Content Source: articles/service-fabric/virtual-machine-scale-set-scale-node-type-scale-out.md
Service: service-fabric
GitHub Login: @aljo-microsoft
Microsoft Alias: aljo

Thanks for the question! We are investigating and will update you shortly.

I think I may have figured it out but I would like you guys to verify this is the correct answer?  https://stackoverflow.com/questions/51089716/service-fabric-on-premises-add-node-and-node-type-correlation/54724499#54724499
Pretty much you need to update the existing configuration and then add the node.  These does seem to be a "bug" or the lack of flag in the powershell to pass the options for sending windows credentials with the cluster connection.

It looks like the windows credentials bug was marked as fixed in 6.4 as stated by @masnider at the very bottom of this issue: https://github.com/Azure/service-fabric-issues/issues/974
We still need clear direction on the node type though.  I'm also not clear on when adding a node if I should be updating my cluster configuration json or not?  I'll post that into the AddNode article though.

Its already documented, I found it but it wasn't all that easy to find.
https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-cluster-windows-server-add-remove-nodes#add-node-types-to-your-cluster
Any chance we can move that section up to the top of this?  Or at least make it a major category so it shows up on the right nav?  It was listed under the GMA section, I didn't read that far a head because i'm using windows security.

Thanks for the update @gperrego
I will assign to the content author to see if we can make it easier to find

@gperrego
We appreciate your feedback.
You will notice this directly links to the referenced material:
https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-cluster-windows-server-add-remove-nodes#add-nodes-to-your-cluster
and is nested in the table of contents under:
How-To-Guides -> Create and Managed Clusters -> Standalone Clusters -> Scale
Which follows the same format as the Azure SF cluster scale table of contents:
How-To-Guides -> Create and Managed Clusters -> Clusters on Azure -> Scale
Given standalone doesn't use compute providers API, there are only Adding and Removing
Nodes from standalone cluster content:
https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-cluster-windows-server-add-remove-nodes#add-nodes-to-your-cluster
https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-cluster-windows-server-add-remove-nodes#remove-nodes-from-your-cluster
With on Azure using Compute API, we break them out into top level Table Of Content sections, but that isn't applicable to Standalone.
@MicahMcKittrick-MSFT
#please-close


[Bug] [Module Name] Pagination issue. only show 1 page。 分页器只显示1页。

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened

my task instances have more then 10 , but only show 10.
my server is deploy by standalone.
version 3.2.1
我的任务实例数量远超10个，但是只显示10个。没有下一页。
我的部署方式是 standalone。
我的版本是 3.2.1
What you expected to happen
rest api return total : 89 , and I can change pageSize to show more then 10. but pageNum only have 1.
api显示总共有89条，我也可以通过调整分页大小看到超过10条。但是不管怎么调，都只有1页。

How to reproduce
deploy by standalone.
version 3.2.1
3.2.1版本单机部署应该都有这个问题。
Anything else
No response
Version
3.2.x
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Duplicate with https://github.com/apache/dolphinscheduler/issues/15606.


Enhancing  User Interface for a More Intuitive Note-Taking Experience in the note-taking application

This pull request aims to improve the overall user experience by introducing several UI enhancements:
Redesigned note list: A visually appealing and more organized layout for the note list, making it easier to identify and navigate through notes.
Improved formatting options: Enhanced formatting tools, including more font styles, colors, and alignment options, to allow for greater customization and expression.
Enhanced search functionality: A more robust search feature with advanced filtering options to quickly find specific notes based on keywords, tags, or labels.
Improved collaboration features: Enhanced features for sharing and collaborating on notes, including real-time editing and commenting.
Dark mode: A dark mode option for users who prefer a darker background for improved readability and eye strain reduction.
These changes will make PR more user-friendly and efficient, providing a better note-taking experience for our users.

Changed The Ui for More User Interactions and added a better design . Raising a PR


Comments are not accounted for

At least the following make using the types somewhat challenging:

The tag of an element can be etree.Comment, a function.
The text of a comment is always a str.

Given these, I wouldn't be surprised to find other places where the types are misaligned with respect to comments.

@eemeli I presume you mean the tag selector here, please tell me (or even better, provide an example) if I didn't get your real intention.
It is indeed a challenge on how to fit in other types of element factory into the _TagSelector alias, but ultimately there's no good solution. Not just etree.Comment(), there are etree.Entity() and etree.ProcessingInstruction() too, all of them having different call arguments.

The code that I encountered these issues with looks roughly like this:
from lxml import etree
root = etree.fromstring('<foo><!-- comment --></foo>')
comment: list[str | None] = []  # TODO: should be list[str]
for el in root:
    if el.tag == etree.Comment:  # type: ignore[comparison-overlap]
        comment.append(el.text)

To satisfy mypy, I need the type: ignore comment because the current types are presuming that el.tag is always a string, and it isn't for comments.
Also, even if I narrow the typing of el with cast(etree._Comment, el), el.text won't be typed as str, but always as str | None; hence the wider typing for comment.

For the first problem, I don't have any good solution so far. This is the price needed to pay when I decided to follow lxml on how _Comment is inherited from _Element. _Comment has totally different behavior from _Element, yet it is a subclass of _Element. I could have severed the relation between _Comment and _Element, but that leads to another set of problems.
Right now you may want to try narrowing down the type of el itself, for example:
for el in root:
    if isinstance(el, etree._Comment):
        comment.append(el.text)

On second problem, you're right. It is possible to use None as input argument in etree.Comment(), but the .text attribute of comment element is always str. Will fix that soon.

The instanceof check is indeed better, and the text fix looks promising. Thank you!

The fixable part of this issue is addressed, so I'm closing. Please feel free to reopen if something related to this issue still doesn't work.


extra terminal history created after minimizing top sash

open pwsh 7 (shell integration on, terminal experiment suggest disabled)
try scrolling up, and you should already be at the top.
echo 'hello'
still notice you can't scroll up to see anything else.
lower the sash until some of the text is out of the view.
Try scrolling up- there should be history above that just repeats your command a bunch (even though I only ran it max once before this take).

https://github.com/user-attachments/assets/9ab77cbd-453f-47f2-8e3a-0a4825eedc7b

This is likely a problem with the conpty backend we use. You can try to reproduce the problem in Windows Terminal and if it happens there as well, report to microsoft/terminal.
If you cannot reproduce in Windows Terminal, chances are it's fixed in a later version of Windows. You can read more about how we consume conpty here.
/label terminal terminal-conpty windows


AudioServer.get_time_to_next_mix() can return negative values

Godot version:
3.3.2
OS/device including version:
Macbook Pro 2018 13 inch, Big Sur 11.3.1
Issue description:
AudioServer.get_time_to_next_mix() can return negative values. It seems that this happens if a relatively longer stream (eg 2 minutes long) was just set in the audio player.
Expectation: time to the next mix should always be non negative.
Steps to reproduce:
In the same call to _process, set the stream of an AudioStreamPlayer then print AudioServer.get_time_to_next_mix().
Minimal reproduction project:
AudioServerBug.zip

As far as i tested, you dont need to set the stream and call get_time_to_next_mix in the same call to _process. Just doing this also shows negative values sometimes:
func _process(_delta):
	print(AudioServer.get_time_to_next_mix())

Can't reproduce in master build v4.0.dev.20210916.official [104a6191f].
But this still exists in 3.3.3. I will check what is the difference

Update: The code for get_time_to_next_mix method is identical in both versions.
The bug must be somewhere else.

Update 3: I checked pre-alpha versions on 4.0 and

v4.0.dev.20210727 - Issue exists
v4.0.dev.20210811.official [7188cb601] - Issue exists
v4.0.dev.20210820.official [75697c0df] - Issue exists
v4.0.dev.20210916.official [104a6191f] - Issue exists

CC @godotengine/audio

Does this cause problems in practice? get_time_to_next_mix seems to me like a convenient way to say latency - time_since_last_mix which can obviously be negative if a mix takes more time than expected or is delayed for any reason.
That said, I can't figure out what the default implementation of this method is doing:
https://github.com/godotengine/godot/blob/d187bb4e11182ee3edbc0008dba5762148bc530d/servers/audio_server.cpp#L87-L95

Took a look at this, and _last_mix_frames is a bit of a misnomer.  It's the number of frames to mix, set by void AudioDriver::update_mix_time (and only used in this function).  Dividing that by the mix rate will give the time, in seconds, for each mix buffer.
So it's calculating how much time has passed since the last mix, converting that to seconds, and finding how long the mix buffer, in seconds is, and returning the difference between the two.
The thing that's tricky here is that, since the mixing happens in a different thread, you could query the time to the next mix and get a negative value since enough time has passed to start a mix, but it hasn't started doing the mix on the audio thread yet.
So if you play your sound, it might mix that frame, or it might be delayed 1 full mix.  In fact, that has potential to happen even with values that are greater than 0.
UNLESS, the audio mixing does not start until the end of the frame, in which case, the fix for this is to simply return 0 if the value is less than 0.
All that being said, I'm trying to figure out how to actually use get_time_to_next_mix() in practice.  For example, if I have some sounds I want to play exactly on a beat, knowing the time to the next mix could mean I could play them sooner, but they'd still be off.  It's like I'd need a way to play a sound with a delay that happens within the mixing thread.  This is probably not the place for this  discussion, but I found this github issue when searching for a practical use for get_time_to_next_mix(), so if somebody knows how to apply it, maybe throw a link in here for wild internet wanderers like myself who might stumble upon this.

Is this still reproducible in 4.0 RC 3 or later?

Confirmed happening with latest mainline (synced within 24 hours).
Could trigger it thires in 16 attempts of running the scene of the MRP (after using the auto-upgrade).  All negative values were always before Load music into player.

Godot Engine v4.0.2.stable.official.7a0977ce2 - https://godotengine.org
Vulkan API 1.3.194 - Forward+ - Using Vulkan Device #0: NVIDIA - NVIDIA GeForce GTX 970

iter
time to next mix
time since last mix

0
-0.00099402267574
0.012604

1
-0.00152202267574
0.013132

2
0.00925997732426
0.00235

3
0.00904397732426
0.002567

4
0.00889597732426
0.002714

Load music into player

5
0.00228797732426
0.009322

6
0.00791997732426
0.003691

7
0.00773397732426
0.003876

8
0.01125197732426
0.000358

9
0.01097397732426
0.000636

10
0.01082897732426
0.000782

reduz said about the return value of AudioServer.get_time_to_next_mix():

I think its the estimated time until you get an audio mix callback. I think it needs to be used together with the audio latency value to get the time it will take for a sound played to be actually heard.


WIP disable istio for debug

Signed-off-by: Or Shoval<EMAIL_ADDRESS>

/uncc @mhenriks @yuhaohaoyu

/test pull-kubevirt-e2e-k8s-1.21-sig-network

didnt help


512x512 Model

Hello,
Thanks for releasing the excellent code. Do you have plans to release a model capable of generating 512x512 images and maybe larger?

I released two 512x512 models yesterday (not CLIP conditioned yet). :)


Feature hide until

Hey Javi Filella,
I think the hide button can be improved.
A variable in $ .fn.postitall.globals named 'hideUntil' can save time (eg one day) to hide the note.
When the user clicks the 'hide button', then the note is hidden for this time. (not for ever)
On backside of the note is a input field (e.g. with datepicker) for set the show date (e.g. named: hidden until).
What do you think about this little feature??
Thanks for Postitall...
Best regards Ronny

Hi Ronny,
it's a good idea :+1:
I don't know when the next release will be published, but sure, I will add it!
Regards
Javi Filella

That's very good.
It's just a couple of lines of code. If you need assistance, I'd be glad to help.
Best regards Ronny

Hey Rony,
Sure!! You can create a new branch and do the chnges here, later if all is right I will merge it with the master branch.
Thanks in advance! :smile:
Javi Filella

Hi again Rony,
I've just released a new version with your suggestions. I hope you like it :)
https://github.com/txusko/PostItAll/pull/23
Best regards
Javi Filella


can.stache helpers that rely on array replacement don't work, but work in can.mustache

Found this issue earlier today. In a component, if you have a mustache helper that relies on running on a list's length changing, and you replace the list outside of the component - everything works just fine.
If you do this using Stache...the helper stops running.
Example (can.mustache): http://jsfiddle.net/imjoshdean/ojrhg955/
Example (can.stache): http://jsfiddle.net/imjoshdean/ojrhg955/1/

Essentially, a Stache helper's binding on a list will break if the list is overwritten.
// Helper
isListEmpty: function (options) {
  return ! this.attr('items.length') ? options.fn() : options.inverse();
}

// Template
{{#each items}}
  ...
{{/each}}
{{#isListEmpty}}
  There are no items!
{{/isListEmpty}}

scope.attr('items', new can.List([ ... ])); // Breaks helper binding


make sure BEC never kills a plan due to raising an exception

Should we advocate for putting non-breaking callbacks on a proxy?

@CJ-Wright that is also a solution, but going from 0 to running proxy is not trivial on the floor.

Should we add an ignore_exceptions kwarg to RunEngine.subscribe? We have an instance-global switch RunEngine.ignore_callback_exceptions which is too broad (it would ignore db.insert failure too). Maybe the right place for that switch is on a per-subscription basis.
One reason not to do this is that ignoring exceptions isn't always enough. In the case of pyolog, we have to also process the callbacks on a Thread because the pyolog sometimes fails by being slow.

Closed by #1249


'.Site.IsServer' was deprecated in Hugo v0.120.0. Use 'hugo.IsServer' instead.

https://github.com/bowman2001/perplex/pull/174


Making kubernetes package unit testable using fake and add tests

Changes to make kubernetes package unit testable using fake
Add unit tests to test all the APIS of kubernetes package

This change will enable to test the Dapr APIs to use kubernetes fake.
Issue reference
#665
This PR will close: #665
Checklist
Please make sure you've  completed the relevant tasks for this PR, out of the following list:

[x] Code compiles correctly
[x] Created/updated tests
[x] Unit tests passing
[ ] End-to-end tests passing
[ ] Extended the documentation
[ ] Specification has been updated
[ ] Provided sample for the feature

Thanks for this work :) I left some nitpicks.

thanks @youngbupark . sure thanks for review !

Don't merge yet please, I'll post a review tomorrow.

Don't merge yet please, I'll post a review tomorrow.

Sure, I will wait for your review.


Added SimpleG processor

Closing this PR as discussed so that new PR can be submitted with updated README and files.


Evaluation on if MiniCPM-2B-sft-bf16 need model based optimization on ipex-llm

Below are the benchmark results on both THUDM/chatglm3-6b and openbmb/MiniCPM-2B-sft-bf16, from which we can see that chatglm3-6b has better throughput than miniCPM-2b. Considering MiniCPM-2b is a 2B model while chatglm3-6b is a 6B model, I'm not sure if the results are considered normal or further optimization should be done on miniCPM-2b.
Platform: Core ultra 7 165H,  32GB*2=64GB DDR5 5600 MT/s, ubuntu 22.04, Ipex-llm 2.1.0b20240526

Model
Data type
Batch
Input
Output
First token latency （ms/token）
Rest token latency（ms/token）

THUDM/chatglm3-6b
INT4-SYM
1
32
32
468.38
46.98

INT4-SYM
1
1024
128
3997.21
48.87

INT4-SYM
1
1024
1024
3987.13
49.31

INT4-SYM
1
2048
1024
8607.79
50.25

openbmb/MiniCPM-2B-sft-bf16
INT4-SYM
1
32
32
258.62
44.72

INT4-SYM
1
1024
128
2602
65.81

INT4-SYM
1
1024
1024
2720.03
80.4

INT4-SYM
1
2048
1024
6910.26
112.05

Can you try the latest ipex-llm 2.1.0b20240603?

Platform: Core ultra 7 165H, 32GB*2=64GB DDR5 5600 MT/s, ubuntu 22.04, Ipex-llm 2.1.0b20240606
Compared to previous version, the performance improvement is obvious.

model
1st token avg latency (ms)
2+ avg latency (ms/token)
input/output tokens
batch_size
low_bit

intel/MiniCPM-2B-sft-bf16
246.71
24.11
32-32
1
sym_int4

intel/MiniCPM-2B-sft-bf16
2493.34
27.85
1024-128
1
sym_int4

intel/MiniCPM-2B-sft-bf16
2626.22
29.96
1024-1024
1
sym_int4

intel/MiniCPM-2B-sft-bf16
6618.25
34.09
2048-1024
1
sym_int4


How do you use vssetup.powershell

It would be great if there was an example of how to use vssetup.powershell to find MSBuild

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

ID: eb723883-dd62-0c53-8617-7bc867b9aaf3
Version Independent ID: de1ff8ce-885c-9df0-077c-48c82f163c83
Content: What's New in MSBuild 15 - Visual Studio
Content Source: docs/msbuild/what-s-new-in-msbuild-15-0.md
Product: visual-studio-dev15
GitHub Login: @Mikejo5000
Microsoft Alias: mikejo

This is a great idea for a topic, but the work is currently out of scope for MSBuild docs


Bump Ruby from 3.3.4 to 3.3.5 [DEV-109]

This didn't update BUNDLED WITH. I am going to close and retry.


fix dot style

In my opinion it's looks better, when the dot size equal to system dot size 💅
Before:

After:

lgtm, thanks!


Feature/zclconfig

externalise config addnodes, fix ant build for new resources. #6

Looks good, let's also review the dnsseeds in z-classic/zclassic chainparams.cpp. See https://github.com/z-classic/zclassic/pull/153


404 Error

🐛 Bug Report
The  index.html is missing to show the home page, please fix

Looks like you beat me to it :)
When navigating to https://facebook.github.io/jest/, I get a 404 error. Other sites (e.g. the react-native site) load fine.
To reproduce, go to the Jest website. Direct URL, via the facebook.github.io website, via google, etc.


Git - Deprecate Repository.refs property to improve performance

[x] Add new git extension API to query for refs
[x] Update git extension not to rely on the refs property
[x] Update 1st party extensions to adopt the new git extension API
[x] Post announcement of the deprecation to vscode-discussions
[x] Update code so that the refs property always returns an empty array
[x] Remove the code to keep the refs property from updateModelState

Verification steps:

Open a folder/workspace that contains a git repository
Open the Output window, and switch to the git output channel
Open the Source Control view, and click on the "Refresh" action

Confirm that the "Refresh" action produced the following output in the git output channel2023-03-13 11:44:14.808 [info] > git config --get commit.template [17ms]
2023-03-13 11:44:14.812 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) refs/heads/main refs/remotes/main [20ms]
2023-03-13 11:44:14.977 [info] > git status -z -uall [164ms]

Open the command palette and invoke the "Git: Checkout to..." command

Confirm that the quick pick widget contains all branches, remote branches, tags
Confirm that when opening the quick widget the following output is added to the git output channel2023-03-13 11:46:02.340 [info] > git for-each-ref --sort -committerdate --format %(refname) %(objectname) %(*objectname) [61ms]


Update Delete to handle long-running deletions

Updated to handle cache refreshing and also made some docs updates.

Ok, updated again to address the feedback.


Pin grunt to version 0.4 in Travis build

npm install grunt now installs version 1, which breaks a peer-dependency with grunt-saucelabs

Changes Unknown when pulling ba7273d8022171904f10af4249d743699afa0650 on travis-grunt-pin into ** on master**.


feat: granule links via event subscription

What I am changing
This PR adds an API endpoint to handle ESA's "push" subscription notification for new data. This endpoint is intended to handle new granule "created" event notifications for Sentinel-2. This PR also adds a CLI script to list, create, and terminate subscriptions. This script defines the filters that we wish to apply for new granules, which at the present is limited to filtering to only Sentinel-2 imagery.
For more background on ESA's subscription system, the design of this handler, and preliminary results, see this ticket, https://github.com/NASA-IMPACT/hls_development/issues/300
This subscription handling endpoint is intended to be run alongside the existing scheduled "link fetcher" that runs once a day. Once we have more evidence that this is working as expected we can remove the old "link fetcher" and associated machinery (date generator Lambda, StepFunction, and the GranuleCount tracking table).
How I did it
At a high level one of the implementation choices was "where should this live?" especially given that both the event and polling based link fetching was to live side-by-side for a time. In other words they will share some code related to the message payload, state tracking, and sending messages to the queue. I had thought of two possible alternatives,

Create a new module under lambdas/ and either,

Copy/paste "common" code
OR, migrate "common" code into some shared location (i.e., a new Lambda layer)

Reuse the same module lambdas/link_fetcher,

Refactor "common" code into a common.py

Either way we still have 2x sets of Lambda functions, log groups, and alerts! I picked option 2 because sharing the same directory didn't cause any blockers (i.e., Lambda zip getting too large), was relatively less complex than migrating to another directory, avoided setting up yet another workspace in CI and Makefiles, and eventually we'll be deleting the old link fetcher so this shared living arrangement will only be temporary.
With that high level decision made, there are a few other steps I want to call out for review,

I created the hls-s2-downloader-serverless/{stage}/esa-subscription-credentials secret
in AWS SecretsManager and populated it with the user/password that I used when creating the 'push' subscription on ESA's side.
Once the endpoint was deployed I used the manage_subscription.py script to create the "push" subscription to our endpoint.
I added a "date observed" filter to the event handler to mimic the 30 day look back in the schedule based "link fetcher". I did this after noticing that ESA has been in the middle of a reprocessing campaign to process data from 2022 with the newer baseline 05.10 software (see announcement, https://dataspace.copernicus.eu/news/2024-9-2-sentinel-2-collection-1-products-availability).

Right now the filter is simply ignoring results that were acquired > 30 days since today. In the future we could handle these differently, perhaps adding them into some reprocessing download queue that is processed with lower priority than new granules.

How you can test it
There's a few ways to test this,

Unit tests can be run as usual make unit-tests from root, or make test from the lambdas/link_fetcher module
Integration tests are run from CI/CD in this PR
I've deployed this to our AWS environment using the IDENTIIFIER=event-subs for the past ~2 weeks. I've purged the queue a few times as I've made changes, for example to ignore reprocessed granules that were acquired in ~2022. Still though this has been useful to check in bulk how many granule messages we're getting. Below is a screenshot of the queue depth for the last 2 days that shows we're getting approximately the ~5-7k messages per day that we usually get from the schedule based link fetcher.

Thanks @chuckwondo! I'll get to your feedback later today or first thing tomorrow but it looks like great input, really appreciate your close review!

Hey @chuckwondo, thanks for your reviews! I think I addressed your feedback and this PR is now up to date with main after fixing some merge conflicts with the work related to updating for ESA's change in search query offset/limit. Would you mind re-reviewing?
I won't turn on the pushes to this endpoint until after some more acceptance testing in another stage deployment that writes to a non-production bucket, but it'd be nice to get it in the main Git branch in case there are other changes that come up.


refactored XenonProperties .clear(), .exclude() and .include()

Codecov Report

Merging #549 into master will increase coverage by 0.37%.
The diff coverage is 77.14%.

@@             Coverage Diff              @@
##             master     #549      +/-   ##
============================================
+ Coverage     84.89%   85.27%   +0.37%
- Complexity     1541     1548       +7
============================================
  Files           103      103
  Lines          4634     4617      -17
  Branches        693      684       -9
============================================
+ Hits           3934     3937       +3
+ Misses          482      468      -14
+ Partials        218      212       -6

Flag
Coverage Δ
Complexity Δ

#fixedclientenvironment
27.68% <17.14%> (+0.25%)
465 <1> (+3)
:arrow_up:

#integration
58.15% <57.14%> (+0.51%)
900 <9> (+8)
:arrow_up:

#livelocal
23.34% <14.28%> (+0.23%)
372 <1> (+1)
:arrow_up:

#unit
55.51% <77.14%> (+0.16%)
1140 <22> (+2)
:arrow_up:

Impacted Files
Coverage Δ
Complexity Δ

...esciencecenter/xenon/adaptors/XenonProperties.java
76.68% <77.14%> (+3.9%)
53 <22> (ø)
:arrow_down:

...enon/adaptors/schedulers/slurm/SlurmScheduler.java
66.89% <0%> (+1.37%)
32% <0%> (+2%)
:arrow_up:

...nl/esciencecenter/xenon/utils/StreamForwarder.java
76.92% <0%> (+1.92%)
12% <0%> (+1%)
:arrow_up:

...on/adaptors/schedulers/torque/TorqueScheduler.java
81.21% <0%> (+3.63%)
50% <0%> (+3%)
:arrow_up:

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 adaa0d0...764d2a2. Read the comment docs.


feat: auto expand tag + command

Currently doesn't work with React and latest Volar

Omg, this is so cool


Please update latest version to npm

Hello,
This navigation package makes the most sense for me as compared to the zillions out there in react native land.
Could you publish the most latest version to NPM please? I guess the one currently live on npm is almost 6 months old. I'm unable to run the one from github directly. Thanks.

Done ! 😎


job types should have a project relationship

Issue by opalmer from Wednesday Dec 18, 2013 at 05:18 GMT
Originally opened as https://github.com/pyfarm/pyfarm-models/issues/27

Projects may need to override a job type definition however the current job type model does not support this.  Add a project relationship so that a job type can be associated with 0+ specific projects.

We do not have a projects table any more.


Getting this error { error: 'json: cannot unmarshal number into Go value of type map[string]json.RawMessage',   code: 3 }

Background
I am using bitcoind regetest network. When I am setting up lightning network. I created two nodes in the network. when I am connecting two nodes(peers) using following code-
var fs = require('fs');
var request = require('request');
var macaroon = fs.readFileSync('/home/annant/lnd_A/data/chain/bitcoin/regtest/admin.macaroon').toString('hex');
var requestBody = {
addr: "03abd76b87c7638352c8b6d84ee765ffab6a9f275409624c365e36e92fe8d059e8@localhost:9734",
perm: true,
};
var options = {
url: 'https://localhost:8080/v1/peers',
// Work-around for self-signed certificates.
rejectUnauthorized: false,
json: true,
headers: {
'Grpc-Metadata-macaroon': macaroon,
},
form: JSON.stringify(requestBody),
};
request.post(options, function(error, response, body) {
console.log(body);
});
I am getting error=>
{ error: 'json: cannot unmarshal number into Go value of type map[string]json.RawMessage',
code: 3 }

The address cannot be provided as a string, but rather as an object that contains a pubkey and a host. This is indicated in our documentation. Give this a try:
var requestBody = {
    addr: {
        pubkey: "03abd76b87c7638352c8b6d84ee765ffab6a9f275409624c365e36e92fe8d059e8",
        host: "localhost:9734"
    },
    perm: true,
};

Thanks..Its working..I will join slack group.


Revert #12888 for potential task scheduling problems

Motivation:
The code I commited in #12888 may cause unexpected task scheduling problems.
Modification:
Revert this commit.
Result:
Fixes #13018 .

Please also merge this to the trunk. Thank you! @normanmaurer


[JENKINS-31437] attach properties to resources, inject properties at build time

This PR allows to define properties, a list of key/value pairs, attached to each resource.
On the project then you can decide to receive (as build parameters) the properties of the elected resources.
I use this feature to define named pools of resources that I can then use at build time. Especially, by product family (named pool) I am able to define resources and for each I define for example the host name, host ip, communication ports, ...

I created JENKINS-31437 to track and ask for inclusion of this PR.

This would be great!

Should this be updated to comply with Pipeline step?

@izzekil do you have pointers/link to plugins code/repos to comply to that?

Very excited about this.   Lockable resources with relevant properties is exactly what I'm looking for.

this would be super awesome, waiting for this to be released :smile:

Any news on when or if this will be released?

OP any thoughts about merging?

Would like this too

Looks neat, but has to be rebased/re-merged against current master branch.
On a side note: would it be a big further leap to also publish the resource instance's assigned labels, the labels which matched for the current selection, and the description (all as string variables, perhaps named with the base-name user requested for storing the name of the resource instance plus some suffix?) I guess not, after all the work done here? It would nicely address several open issues/feature requests...

FWIW, I posted https://github.com/McFoggy/lockable-resources-plugin/pull/2 against @McFoggy 's branch to bring this codebase up to date against master. The best test of the update I could do is for it to be compilable with mvn; conflicts resolved in a way which made sense to me by logic - but not sure how correct the resulting Java is (ain't my native tongue).

Hi there, as it was long requested I reworked this PR to rebase it, add pipeline support and introduce some integration tests.
You can now, additionally to standard usage, use properties inside a pipeline job:
echo 'Starting'
lock(label: 'RES', quantity: 1, injectProperties: true) {
  echo 'injected id: ' + env.id
}
echo 'Finish'

added parameters:

injectProperties: true/false, controls if resource properties are merged inside the step environment variables
prefixProperties: true/false, if true and if variable parameter exist then injected properties will be prefixed with the value of the variable followed by an underscore.

given the resource r1 {label: 'RES', properties: {'id':'prod'}
defining step lock(label: 'RES', quantity: 1, variable: 'kind', injectProperties: true, prefixProperties: true)
will make the injected id property accessible under: env.kind_id

uppercaseProperties: true/false, controls if resource properties keys are put upper case

Even for standard builds I added the possibility to prefix & uppercase the injected properties.

I need some more time to review what makes the tests fail.

tests are fixed.

@amuniz any chance to get a review?

@amuniz @abayer may I please request some feedback (positive or negative) on this 2.5 years old PR?

:+1:  Would love to see this get merged...anything I can do to help?

anything I can do to help?

provide some help to keep it up to date?
I am a bit out of time to keep the PR aligned with master until it got merged.

I tried to give the resync a shot in updating my PR https://github.com/McFoggy/lockable-resources-plugin/pull/2 but there are quite a few conflicts I'm not qualified to make heads or tails of and resolve logically properly :)
Although it seems you've rebased your commits with newer pipeline-compatible code, so my earlier PR actually grows from a different revision of your work that's no longer in the current branch's git tree, right?

there are quite a few conflicts I'm not qualified to make heads or tails of and resolve logically properly :)

That's why I also can't maintain unmerged by myself my PR in synch with upstream that is constantly evolving (which is normal).

that's no longer in the current branch's git tree, right?

you're right.
Thanks for the trial anyway.

when is it going to be merged? thank you

I will be taking a look at this merge request. It's quite old and cannot easily be rebased so I'll submit it as a new branch based on this one.

close as it is trimmed to a lot of other PRs and this one will be no more possible to merge (due many of conflicts)


Peek - Show more information when peeking into folders.

Microsoft PowerToys version
0.7
Installation method
PowerToys auto-update
Running as admin
No
Area(s) with issue?
Peek
Steps to reproduce
Click on a folder in File Explorer
Press Ctrl+Space
✔ Expected Behavior
a quick preview of files selected in File Explorer
❌ Actual Behavior
Only a brief summary of properties is provided.

Other Software
No response

This is more like an enhancement request, not an actual bug.

dup #16124

/dup #26171


ClickHouse compatibility (S3 and ReplicatedMergeTree)

Question
We're currently using ClickHouse's ReplicatedMergeTree and we're doing ingestion via
INSERT INTO foo SELECT * FROM s3('....')

My first question is do we have a corresponding external table function? I did a quick search into the codebase and it seems there is a CnchS3(...) table function but not quite sure if it is the same thing as ClickHouse's S3 table function.
My second question is do we still need any sort of replication if we are using cnch_default_s3 as the default storage policy? Is it true that we can on-demand spin up more byconity-server statefulset to query the same table because the storage is decoupled from the compute? Will the new byconity-server instance replicate metadata from peers automatically?
Thanks

Hi @lazywei , thank you for the question. The CnchS3 is the same as s3 table function in clickhouse. And we don't need any sort of replication for that case because the data is stored in remote disk and not local. It is true that we can on-demand spin up more byconity-worker not server to query the same table because storage is decoupled from the compute. Currently we store meta data in FoundationDB, a dedicated component to store metadata that can scale independently so no need to replicated the metadata as well.

Hi @lazywei , I didn't know that issue in ClickHouse. For insert query I think you can control the part size of both ClickHouse or ByConity by using Settings min_insert_block_size_rows and min_insert_block_size_bytes. Unless you have fine grain partition key, those settings is the settings control Squash operator that squash smaller blocks into big blocks before insert to disks

Hi @lazywei, I think the point is better to have the part size big enough to avoid unnecessary merge, improve insert performance and improve select query performance. In ByConity for CnchMergeTree engine, we use system.cnch_parts. You can take a look into a list of our system table in here. And the squash operator is like you said is to keep data in memory a little while until the size is big enough before push to disk. And these settings is there quite a while ago in ClickHouse. You can look at this document. https://clickhouse.com/docs/knowledgebase/Insert_select_settings_tuning


travis macOS beta timeout

As seen in gtk-rs/gtk#948.

We don't use travis anymore, see #13 for an issue that tracks re-adding a github action job for macos builds.


Restructure project to src style

Put package under src
Put example app under example
Put tests under tests
Add README and requirements to example
Fix docs build, needed django
Remove gis and django.contrib.gis requirement from example
Add tests

Coverage increased (+0.3%) to 87.581% when pulling 2071328afd6267b671bd853d1513f0953388ab89 on restructure into 49e1fbd75e6944d35d2c612bcf127e9ea9ea460a on master.


docker can not push images

i just suddenly can not push images by docker push command.
1963422757ad: Pushing [==================================================>] 45.06 kB
5f70bf18a086: Layer already exists
510e363c12a3: Layer already exists
f09fdb5ddd25: Layer already exists
a2ab78debd3e: Layer already exists
66754d2993e3: Layer already exists
b435f567e45e: Layer already exists
df09ce9c9073: Layer already exists
6eb35183d3b8: Layer already exists
digest invalid: provided digest did not match uploaded content
docker -v
Docker version 1.12.3, build 6b644ec
docker info
Containers: 4
Running: 3
Paused: 0
Stopped: 1
Images: 72
Server Version: 1.12.3
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 133
Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: overlay host null bridge
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: seccomp
Kernel Version: 4.4.27-moby
Operating System: Alpine Linux v3.4
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 1.951 GiB
Name: moby
ID: GDTW:Q2BH:OB3P:3YFX:KLAG:FVWB:6E3H:LDNS:GO57:UX3M:N3OU:EAGY
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
File Descriptors: 37
Goroutines: 62
System Time: 2016-11-29T11:54:50.258301314Z
EventsListeners: 1
Http Proxy: <IP_ADDRESS>:8080
No Proxy: *.local、169.254/16
Registry: https://index.docker.io/v1/
WARNING: No kernel memory limit support
Insecure Registries:
<IP_ADDRESS>:5000
<IP_ADDRESS>/8
it will retry a few times, then show digest invalid.
anyone knows why?

Can you provide all the Docker info/version stuff, hard to say anything otherwise...

@runcom  ok

could it be your "moby" VM is out of disk space?
/cc @justincormack is there an easy way to view this?

@linpf870208 could you tell us which image are you trying to push?

Can you open an issue on https://github.com/docker/for-mac/issues
You can check for free space with docker run alpine df -h

@justincormack
docker run alpine df -h
Unable to find image 'alpine:latest' locally
latest: Pulling from library/alpine
3690ec4760f9: Pull complete
Digest: sha256:1354db23ff5478120c980eca1611a51c9f2b88b61f24283ee8200bf9a54f2e5c
Status: Downloaded newer image for alpine:latest
Filesystem                Size      Used Available Use% Mounted on
none                     59.0G      2.9G     53.1G   5% /
tmpfs                   998.9M         0    998.9M   0% /dev
tmpfs                   998.9M         0    998.9M   0% /sys/fs/cgroup
/dev/vda2                59.0G      2.9G     53.1G   5% /etc/resolv.conf
/dev/vda2                59.0G      2.9G     53.1G   5% /etc/hostname
/dev/vda2                59.0G      2.9G     53.1G   5% /etc/hosts
shm                      64.0M         0     64.0M   0% /dev/shm
tmpfs                   998.9M         0    998.9M   0% /proc/kcore
tmpfs                   998.9M         0    998.9M   0% /proc/timer_list
tmpfs                   998.9M         0    998.9M   0% /proc/sched_debug
OK

@runcom i build an local image by dockerfile
FROM <IP_ADDRESS>:5000/node:6.9
RUN mkdir -p /parse-server
COPY ./ /parse-server/
RUN mkdir -p /parse-server/config
ADD ./local/config/config.json /parse-server/config/
VOLUME /parse-server/config
RUN mkdir -p /parse-server/cloud
ADD ./local/cloud/*.js /parse-server/cloud
VOLUME /parse-server/cloud
WORKDIR /parse-server
RUN npm config set registry https://registry.npm.taobao.org --global
RUN npm config set disturl https://npm.taobao.org/dist --global
RUN npm install && \
npm run build
ENV PORT=1337
EXPOSE $PORT
ENTRYPOINT ["npm", "run", "start_trace", "--"]

Let me close this ticket for now, as it looks like it went stale.


UiBroker support for wasm/Kotlin Particles

Note: my editor converted 4-space tabs to 2-space tabs in some of these files, it makes it look like more changes than were actually made.
IIUC, 2-space tabs is our project standard.

In re: tests, looks like since I added a method to wasm.ts that I have to modify the CPP files too. I'll start looking into it.

Closed this in favor of #3652


Added define command

Adds a command that returns the dictionary definition of the argument.

isn't adding it as an attachment pretty much equivalent to using >>>? Also, would be great if you could include some tests (as per gricey's new test framework)

Using an attachment adds the grey bar which I thought was a nicer format for the response. Can change if you disagree.
Will do, forgot that was a thing now. But I will wait for another script to implement them first so I can get some idea of what is wanted.

>>> does that too though-- and would just make for more obvious code intention imo
as for tests, sgtm-- i'm busy for a while with uni but if you want to give it a crack i'm pretty sure gricey submitted a few examples of testing base, maybe go off that?

Oh, my bad. I see what you mean. Didn't know that piece of slack formatting.

I tried to make some tests but apparently they aren't compatible with async?

yeah I wrote async fixes but haven't been bothered cleaning the code yet for a PR, I'll try take a look after wednesday-- if you wanna take a look though it should be in my forked repo


How to add terms and conditions?

Hello, I followed the guide in the documentation and checked the keycloak action as required. I used keycloak-starter project. But in the registration form there is no button with the terms and conditions. What am I doing wrong?

It's notmal.
The terms are not shown on the register-user-profile.ftl page but later on in the flow.
It's when the user first try to connect that terms are shown to him and get to accept or refuse.

yes, thanks


Cutout Improvements and Transformation Affected Nodes API

Multistate Cutouts
Allow cutouts from SDFG where the cutout consists of one or more entire states that form a coherent, self-contained SDFG. In practice, that means that there is a single distinct entry state to the cutout's state machine. This mode of constructing cutouts will always create a copy of states and does not contain a reference-cutout mode like in-state cutouts, since states hold a back reference to the SDFG they're contained in and that reference must point to the new cutout SDFG for the cutout to validate.
Transformation Affected Nodes API
This gives transformations a get_affected_nodes API method where the set of nodes touched by the transformation is returned. For most pattern transformations, this set of nodes is equivalent to the matched pattern nodes. However, some transformations (like MapToLoop) may modify additional nodes (or states) that are NOT matched by the pattern nodes, like loop bodies. This makes it impossible for anything other than the transformation itself to report what nodes are affected. With this API call, a transformation author can (and must) provide this information transparently iff the set of affected nodes diverges from the patched pattern nodes. If not overridden, the standard pattern node matches are used.
"Alibi Nodes" in Cutouts
If a cutout inside of a scope region borders one of the scope nodes (exit or entry), the cutout attempts to cross the scope via each memlet path to connect the corresponding data containers. In the example image below, a cutout of the tasklet prog_39 would result in the cutout procedure attempting to add the map exit and the access node to C to the cutout. Having only the map exit in the cutout, but not the entry trivially leads to a fault. Including the entry node would require including the entire content of the scope. Both these solutions are not what the cutout should intuitively contain.

To address this, this PR adds "Alibi Nodes" to cutouts that cross scope borders. What this means, is that in the example above, the access across the map exit border is detected and instead of inserting both the exit node and the outside access node to the cutout, the outgoing memlet from prog_39 is analyzed, and a new data container with a shape corresponding to the accessed subset is inserted into the cutout SDFG. The memlet is then attached to that new alibi data container instead. This further solves the problem that the memlet crossing the scope border may have symbols in the index term, which can only be defined by the map itself.
Miscellaneous Other Points

Changes the assignments property on InterstateEdges to a DictProperty (from a regular property with dtype=dict). This is necessary to get proper metadata which can be used to infer what type of information this property contains.

Haven‘t looked into it yet, but we should add at least simple two positive tests for cutout. But no over-engineering, can do this after deadlines thoroughly.

Agreed. Particularly multistate cutouts and alibi nodes themselves currently have no coverage. This has to be added, I'll take thosw two specific ones up asap after deadlines.

Some points from earlier discussions:

Alibi cutouts: I think it makes total sense to include to stay within the scope defined by the given nodes. Including temporary data containers makes total sense.
Affected nodes: I don't have a very strong opinion on it, but I think we should not introduce this concept in the same PR. Maybe we can separate this into a draft PR? Even if it is not harmful right now because it is not used within dace and defaults to something reasonable, we should have a broad agreement on it with more developers. It changes how we write transformations. Also how does this compare to "annotate_memlets"? Is the enclosing scope affected? Maybe the state/nested SDFG? I am thinking about a more general API. I see more applications for this: When I fuse two nodes, I don't know what happened to the nodes. Is it gone? Are both nodes gone? Did we create a new one that replaces another? This is quite crucial to know when you want to pin a sequence of transformations to a subgraph, you want to know how it is transformed like a trace

Some points from earlier discussions:

Alibi cutouts: I think it makes total sense to include to stay within the scope defined by the given nodes. Including temporary data containers makes total sense.
Affected nodes: I don't have a very strong opinion on it, but I think we should not introduce this concept in the same PR. Maybe we can separate this into a draft PR? Even if it is not harmful right now because it is not used within dace and defaults to something reasonable, we should have a broad agreement on it with more developers. It changes how we write transformations. Also how does this compare to "annotate_memlets"? Is the enclosing scope affected? Maybe the state/nested SDFG? I am thinking about a more general API. I see more applications for this: When I fuse two nodes, I don't know what happened to the nodes. Is it gone? Are both nodes gone? Did we create a new one that replaces another? This is quite crucial to know when you want to pin a sequence of transformations to a subgraph, you want to know how it is transformed like a trace

So maybe separate the PRs?

Some points from earlier discussions:

Alibi cutouts: I think it makes total sense to include to stay within the scope defined by the given nodes. Including temporary data containers makes total sense.
Affected nodes: I don't have a very strong opinion on it, but I think we should not introduce this concept in the same PR. Maybe we can separate this into a draft PR? Even if it is not harmful right now because it is not used within dace and defaults to something reasonable, we should have a broad agreement on it with more developers. It changes how we write transformations. Also how does this compare to "annotate_memlets"? Is the enclosing scope affected? Maybe the state/nested SDFG? I am thinking about a more general API. I see more applications for this: When I fuse two nodes, I don't know what happened to the nodes. Is it gone? Are both nodes gone? Did we create a new one that replaces another? This is quite crucial to know when you want to pin a sequence of transformations to a subgraph, you want to know how it is transformed like a trace

Sorry, but it would be nice to know what the graph translation of a transformation was in general, maybe we can actually solve this by some form of "graph changes instrumentation" instead of manual specification.


Provide some code coverage

Provide some code coverage using https://codecov.io

Good job!

You'll have to enable this repo in codecov.io at https://codecov.io/github/yzalis/Identicon ;) @blaugueux

Already done.


Building does not verify gonixutils version

I ran into an issue building libStorage for testing today because of a stale version of gonixutils that was present.
dicey1:libstorage clintonkitson$ make deps
go build -o /Users/clintonkitson/go/bin/printf-gnix github.com/akutz/gnixutils/cli/printf
can't load package: package github.com/akutz/gnixutils/cli/printf: cannot find package "github.com/akutz/gnixutils/cli/printf" in any of:
	/usr/local/go/src/github.com/akutz/gnixutils/cli/printf (from $GOROOT)
	/Users/clintonkitson/go/src/github.com/akutz/gnixutils/cli/printf (from $GOPATH)

This was fixed by removing the old version with rm -Rf $GOPATH/src/github.com/akutz/gonixutils and re-running make deps.

Hi @clintonskitson,
Thanks for filing this. OOC, why invoke make deps directly? Is there an issue using make install or one of its cross variants? I think I fixed the issue of deps not working for cross builds.

In troubleshooting it, I was just replicating what I saw in the Travis-CI log to make sure I aligned against a known working method.

Hi @clintonskitson,
Understood. Makes sense. I should set Travis up to dogfood the fix.


Added cccp.yml for for building on container pipeline.

This is for the purpose of building these containers through the CentOS Community Container Pipeline.

Can you point me to some docs for cccp?

Sure.
Wiki Page:
https://wiki.centos.org/ContainerPipeline?action=show
Container Pipeline Service Readme:
https://github.com/CentOS/container-pipeline-service/blob/master/README.md
Container Index Readme
https://github.com/CentOS/container-index/blob/master/README.rst


Occurrence Notes option is unchecked by default for the second file in Translation mode.

translationCore Create - v1.0.0-rc.1
Related to #208.
For tN, when the file is opened first time it overwrites the file with English as reported in #208.
For the Second file(That has an alternative language translation file) that is opened, the Occurrence Notes option is unchecked by default so the content is the Target language is not seen.

The FIX cannot be demonstrated in the preview.
But at least we can verify the change does not crash/break anything else.
True testing of this bug fix will need to be in the tc-create-app.
https://deploy-preview-14--datatable-translatable.netlify.app/

Looks good in translationCore Create - v1.0.0-rc.3


[pt-br] Install Kubeadm page in Brazilian Portuguese is outdated

The session about get certificate is dedepracate on ubuntu 22.04

Page reported in issue: https://kubernetes.io/pt-br/docs/setup/production-environment/tools/kubeadm/install-kubeadm
/language pt

Check out this note in English version -

The legacy package repositories (apt.kubernetes.io and yum.kubernetes.io) have been deprecated and frozen starting from September 13, 2023. Using the new package repositories hosted at pkgs.k8s.io is strongly recommended and required in order to install Kubernetes versions released after September 13, 2023. The deprecated legacy repositories, and their contents, might be removed at any time in the future and without a further notice period. The new package repositories provide downloads for Kubernetes versions starting with v1.24.0.

/triage accepted
The Portuguese page needs to be updated in sync with the English manual.

/retitle [pt-br] Install Kubeadm page in Brazilian Portuguese is outdated

@stormqueen1990 if you want i can rewrite the pt-br for that.

@stormqueen1990 if you want i can rewrite the pt-br for that.

@seilorjunior feel free to take this up and work on it if you're interested.

/help

@stormqueen1990 I can try to help on this

Hi folks, Is anyone working on this issue?

@ricardoamaro, Can you confirm are you working on this ?

@stormqueen1990 I can try to help on this

@edsoncelio we learned that the pt-pt team formalization will still take some time, so this remains as pt-br if no one disagrees and we can help each others meanwhile 🤗

Okays, thanks @ricardoamaro!
Let me know If you need some help :D

Created a PR in https://github.com/kubernetes/website/pull/46001
Feel free to give your suggestions, improvements, reviews, etc

https://github.com/kubernetes/website/pull/46001 has been merged! This issue can be closed

/close
Solved via #46001


Update defconfig for 5.10 kernel and configure new drivers as modules

Also, add the RTW88_8821CE driver specifically as per customer request.

@balena-ci I self-certify!


Question: GitLens for Atom

Is there any chance that gitlens could be ported to Atom? Atom's git integration is far superior to VS Code in my experience.
This would be a great plugin to have on Atom.
Pretty please!

This would not only be a large undertaking, it also isn't something I'm really interested in right now as I am not an Atom user (and I would want to use the product regularly to ensure its high quality).

Try
atom-inline-blame in atom packages, install it.
It won't be able to compete with GitLense but it works fine; it shows inline authors. At least for me that is the only thing I look for.


Make core project "cats friendly" and get rid of Futures

Hi Alfonso,
Thank you for your project, I was able to quickly add telegram bot in my application.
I would like to propose some changes in this pull request. Project 'core' is based on scala.concurrent.Future but it actually doesn't use any specific Future's properties. Core needs only instance of cats.MonadError. So we can abstract over Effect container, declare BotBase as
trait BotBase[F] {
  implicit val monad: MonadError[F, Throwable]
  ...
}

and use generic F instead Future.
This project is based on sttp which provides backends for Future from standard lib, IO from cats-effect, Task from Monix and IO from ZIO. This gives us compatibility with any of these libraries without necessary to convert IO to Future and Future to IO for any operation.
I also tried to get rid of mutable state inside Polling.scala and BotBase.scala:

Polling had variable

@volatile private var polling: Future[Unit]

which allowed to interrupt polling. But this is not needed for IO/Task which has built-in cancellation functionality. So I decided to declare common trait telegram.api.Polling and two "implementations" telegram.future.Polling for Future's and telegram.cats.api.Polling for cats-effect. New trait telegram.cats.api.Polling doesn't have mutable state.

BotBase had mutable variable

protected var getMe: User = _

to handle "respectful" commands. I removed this variable and pass User as argument of method BotBase.receiveUpdate. It required some changes in telegram.api.declarative.Commands.
Even though this pull request has a lot of changes and they are relatively straight-forward. I tried to minimize changes for users of this library to migrate code to this version. Basically they need just to add [Future] for traits from telegram.api.declarative, for example,
trait Declarative extends Updates[Future]
  with Messages[Future]
  with ChannelPosts[Future]
  with Callbacks[Future]
  with InlineQueries[Future]
  with Payments[Future]

I've been sidelined by my thesis deadline; please bear with me, I'll put some work to merge this once I'm done. This is major change that needs some polished docs, working examples in the README...

Sure, no problem.