WslRegisterDistribution failed with error: 0x80070424

Windows Version
10.0.22631.2715
WSL Version
<IP_ADDRESS>
Are you using WSL 1 or WSL 2?

[X] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>-1
Distro Version
Ubuntu 22.04.0 LTS
Other Software
No response
Repro Steps

Expected Behavior
ubuntu start success
Actual Behavior
ubuntu system start failed error:0x80070424
Diagnostic Logs
No response

/logs

I have the same error running this version of WSL. Everything worked and suddenly, probably after updating wsl in the background, WSL does not start anymore and it appears the WSL distribution is gone.


Uncaught TypeError: Arguments to path.join must be strings

Uncaught TypeError: Arguments to path.join must be strings
Atom Version: 0.161.0
System: Mac OS X 10.10.1
Thrown From: remote-sync package, v2.3.1
Steps To Reproduce

...
...

Stack Trace
At path.js:384

TypeError: Arguments to path.join must be strings
  at Object.exports.join (path.js:384:15)
  at ScpTransport.module.exports.ScpTransport.upload (/Users/alexcorbi/.atom/packages/remote-sync/lib/transports/ScpTransport.coffee:16:27)
  at UploadListener.module.exports.UploadListener.uploadFile (/Users/alexcorbi/.atom/packages/remote-sync/lib/UploadListener.coffee:18:15)
  at q.process (/Applications/Atom.app/Contents/Resources/app/node_modules/async/lib/async.js:769:21)
  at process._tickCallback (node.js:378:11)
  at Ipc.sendSync (/Applications/Atom.app/Contents/Resources/atom/renderer/api/lib/ipc.js:39:29)
  at Ipc.sendChannelSync (/Applications/Atom.app/Contents/Resources/atom/renderer/api/lib/ipc.js:47:28)
  at BrowserWindow.RemoteMemberFunction [as emit] (/Applications/Atom.app/Contents/Resources/atom/renderer/api/lib/remote.js:110:29)
  at ContextMenuManager.module.exports.ContextMenuManager.showForEvent (/Applications/Atom.app/Contents/Resources/app/src/context-menu-manager.js:169:33)
  at HTMLDocument.<anonymous> (/Applications/Atom.app/Contents/Resources/app/src/window-event-handler.js:138:33)
  at HTMLDocument.handler (/Applications/Atom.app/Contents/Resources/app/src/space-pen-extensions.js:112:34)
  at HTMLDocument.jQuery.event.dispatch (/Applications/Atom.app/Contents/Resources/app/node_modules/space-pen/vendor/jquery.js:4681:9)
  at HTMLDocument.elemData.handle (/Applications/Atom.app/Contents/Resources/app/node_modules/space-pen/vendor/jquery.js:4359:46)

/cc @atom/core

I've been able to reproduce this error by not specifying a "Target directory" in the new configration dialog.
The resulting .remote-sync.json ends up without target as you expected.
Setting a target makes it work.

Might be worthwhile making / the default target to prevent this error happening when one is not specified


Build Output Text Escaping Problems

Describe the bug

When using the online editor, the build output is printing  , ", etc. instead of the corresponding symbols.
Note: We have an exam on Saturday morning and quite a few students seem to prefer using the online editor as their git knowledge is limited. It would hence be wonderful if this could be solved by then :crossed_fingers: otherwise, students will have to fight through a jungle of escaping madness.
To Reproduce
Go to https://artemis.ase.in.tum.de/#/courses/65/programming-exercises/1446/code-editor/383935 and put
module Exercise where

-- Implement the fibonacci numbers function with initial values fib 0 = 0 and fib 1 = 1
fib :: Integer -> Integer
fib = "hi"

in Exercise.hs. Press Save and Submit, wait for the build. The build will fail due to a type error and the text with escaped symbols appears.
Expected behavior

Show the symbols, not the escaped versions.
Screenshots

Environment

 - OS: [e.g. iOS]
 - Browser [e.g. chrome, safari]
 - Version [e.g. 22]

Additional context

Output in Web Console

  [REPLACE THIS WITH YOUR INFORMATION]

Hey @kappelmann ,
I've fixed this in https://github.com/ls1intum/Artemis/pull/1791:


Modified KMeans to use a Seq for model

Hey guys. I modified your code to make the KMeans model a Sequence instead of a Data set. You can merge it to your branch and then it can be further reviewed on your original PR.

@sachingoel0101
if you want to, i can add you as contributor to my repo. so things can be quicker.

Sure. Do that.

done.
so you can directly commit into my branch. and all those changes will go in the PR.


Update deploy_ca.md

Updating line no: 36. The Maximum capacity for the ASG is already 4. We will be changing the minimum capacity to 3 in the below command which follows from line 43.
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Your proposed text doesn't match the command, it's changing to Min :3 Max: 4. The above output doesn't follow the workshop instruction as it should be 3 3 3 at this point.


Icons

Description
Hello everyone. Unfortunately it is not possible to use all icons from Iconify? But what is in the docs. Here's an example:
Use flagpack:ad in Icon Component like <Icon name="flagpack:ad" /> works fine..
And in nuxtui dosnt work with i-flagpack-ad... why?

why should I install the icons individually? The icons all come with the nuxt/icon package?

OK, I was able to recreate the whole thing now. which is really weird. Why do I have to install the icons individually? these all come with nuxt/icon. https://stackblitz.com/edit/nuxt-starter-avneof?file=app.vue

you can enable dynamic icons too in docs talk about it.

@wladiveras i try it. With:
<UButton     icon="i-flagpack-ad"     size="sm"     color="primary"     variant="solid"     label="Button"     :trailing="false"     dynamic   />
and i get Cannot start nuxt:  Icon collection "flagpack" not found. Please install @iconify-json/flagpack or @iconify/json .. check the stackblitz link :)

@noxsii a i dont have any package from iconify but i use like this.
in your app.config.ts
export default defineAppConfig({   ui: {     icons: {       dynamic: true,     }, });
and i use like this <UIcon :name="iconname" size="1.3rem" />
in https://icon-sets.iconify.design/line-md/moon-rising-alt-loop/ u can search a icon.

and thats is my dependencies
  "dependencies": {     "@formkit/auto-animate": "^0.8.1",     "@nuxt/content": "^2.12.1",     "@nuxt/ui-pro": "^1.0.2",     "@nuxtjs/device": "^3.1.1",     "@nuxtjs/fontaine": "^0.4.1",     "@nuxtjs/google-fonts": "^3.2.0",     "@nuxtjs/i18n": "^8.2.0",     "@pinia-plugin-persistedstate/nuxt": "^1.2.0",     "@pinia/nuxt": "^0.5.1",     "@types/uuid": "^9.0.8",     "@unovis/ts": "^1.3.5",     "@unovis/vue": "^1.3.5",     "@vueuse/motion": "^2.1.0",     "@vueuse/nuxt": "^10.9.0",     "animate.css": "^4.1.1",     "date-fns": "^3.6.0",     "maska": "^2.1.11",     "nuxt": "^3.11.1",     "pinia": "^2.1.7",     "uuid": "^9.0.1",     "v-calendar": "^3.1.2",     "yup": "^1.4.0",     "zod": "^3.22.4"   },   "devDependencies": {     "@nuxt/eslint-config": "^0.2.0",     "@nuxt/image": "^1.4.0",     "@nuxtjs/i18n": "^8.1.1",     "@nuxtjs/supabase": "^1.1.7",     "@nuxtjs/turnstile": "^0.6.3",     "@types/node": "^20.11.30",     "@typescript-eslint/eslint-plugin": "^7.3.1",     "@typescript-eslint/parser": "^7.3.1",     "eslint": "^8.57.0",     "eslint-config-prettier": "^9.1.0",     "eslint-plugin-prettier": "^5.1.3",     "nuxt-security": "^1.2.2",     "prettier": "^3.2.5",     "sass": "^1.72.0",     "typescript": "^5.4.3",     "vue-tsc": "^2.0.7"   }


TorsoRat shouldn't use dead mouse sprite

looks kinda weird

downstream issue? animal parts use lizard sprites

downstream issue?

no

animal parts use lizard sprites

but TorsoRat uses dead mouse sprite
https://github.com/space-wizards/space-station-14/blob/808ed846d172f5907113b820d9bc1c57e785f4b9/Resources/Prototypes/Body/Parts/rat.yml#L18-L20

oh thats an ultra placeholder just to make the test work


maxlength metadata not working with pyspark

I made sure the table doesn't exist, then run the following:
df = sqlCtx.createDataFrame(sc.parallelize([Row(value="a"*2048)]))
df.schema.fields[0].metadata['maxlength'] = 4096
df.write.format("com.databricks.spark.redshift") \
        .options(url=pgconn,
                 dbtable="tmptable",
                 tempdir=TMPDIR) \
        .save(mode='append')

The maxlength metadata is ignored and the column is created with character varying(256) type. Any ideas?

Hi @dokipen,
This is a known issue which stems from limitations in PySpark's column metadata APIs.
In order to change a column's metadata you need to create a new DataFrame using the new metadata; modifying it in-place like this won't work. For this reason, the example in the README uses the DataFrame.withColumn() and Column.as() APIs in order to create a new DataFrame with updated column metadata, but those APIs are not currently available in the Python.
It seems like you might be able to set column metadata by using SQLContext.createDataFrame with an explicit schema, but I think that's only a partial solution because it doesn't really address the case where you're trying to save a DataFrame that's been transformed. I suppose you could convert the DataFrame back to an RDD[Row] by calling .rdd() and then call createDataFrame() with that RDD, but this could be slow due to incurring multiple data format conversions.
This limitation is documented at the bottom of the "Configuring the maximum size of string columns" section in the README, although I suppose I could put a :warning: or :information_source: emoji to draw more attention to it.
See also: https://github.com/databricks/spark-redshift/pull/54#issuecomment-135208025
I'm open to the idea of adding new spark-redshift APIs for encoding these column length constraints in case you have any suggestions there.
/cc @marmbrus @rxin, FYI.

Thanks, sorry I didn't read more carefully.

I have gone ahead and updated the README to make this caveat a little clearer: ed75de1c616bd7713a76caa1c024ac36f3ef537a
Therefore, I'm going to close this issue for now. When Spark expands its language support for column metadata operations, I'll be sure to update the README to include examples in other languages.

@dokipen What were the workarounds that worked?

I don't remember at this point.


Error when trying to build example code

I just tried downloading example "Starter Template" from this page. Got the zip file, expanded it in a folder, ran git init && npm install, everything installed correctly. When running  npm start I got the following error:
Error: Error building site: "/Users/username/dev/project-folder/site/content/docs/5.0/getting-started/browsers-devices.md:19:4": failed to render shortcode "rf.inline": failed to process shortcode: template: _inline_shortcode/docs/5.0/getting-started/browsers-devices.md/rf.inline:2:4: executing "_inline_shortcode/docs/5.0/getting-started/browsers-devices.md/rf.inline" at <readFile ".browserslistrc">: error calling readFile: file ".browserslistrc" does not exist

Here's the log.

OS: macOS X Big Sur 11.1
Browser: Firefox
Suggested fix: add .eslintrc.json file and/or adapt the npm script.

You are not supposed to use our scripts if you use the zip file. The zip file offers the built examples for people to use without anything else.
If you want to use our build scripts, you should use your fork.

You are not supposed to use our scripts if you use the zip file. The zip file offers the built examples for people to use without anything else.
If you want to use our build scripts, you should use your fork.

@XhmikosR it is not clear then for the users, cloning/forking the repo is not exposed on the website as a suggestion or tip to use it. Could we make it clear(er) to the user?

@XhmikosR it is not clear then for the users, cloning/forking the repo is not exposed on the website as a suggestion or tip to use it. Could we make it clear(er) to the user?

Feel free to submit any PR to improve things but please make sure it's not covered already.

Feel free to submit any PR to improve things but please make sure it's not covered already.

Same issue here.


[Bug] Going back to the last checkpoint in potion mode removes the potion effect

Good morning,
I found out that when playing on a course in "potion mode" (in my case it's night vision) the plugin removes the potion effect when teleporting back to the last checkpoint. However, when resetting the run, the potion effect is still there.
Steps to replicate:

Join a course in "Potion Mode"
Shift+right click the item used to go back to the last checkpoint
Any potion effects are gone.

I've demonstrated the issue in this video (the course is set to run with NIGHT_VISION): https://youtu.be/m9p7gEjnW-I
I'm using Parkour version 6.2 (newest available on spigotmc.org as of 19.01.2021).
Here is my config: https://pastebin.com/6c52A4HD
Here is my courses.yml: https://pastebin.com/D8Bw7jv2
I'm running my server on Paper 1.16.5 (build #434).
My plugin list:

Hi, thank you for such a well documented issue report.
Fortunately this has already been fixed in a recent commit (https://github.com/A5H73Y/Parkour/commit/3dc389b49889a2c20edc69b6159112634f2a59b8) and is pending a release as Parkour v6.3.

Hi, thank you for such a well documented issue report.
Fortunately this has already been fixed in a recent commit (https://github.com/A5H73Y/Parkour/commit/3dc389b49889a2c20edc69b6159112634f2a59b8) and is pending a release as Parkour v6.3.


Fine tune a model on startup

Might be a bit much, but you could teach a model about the changes between 1.17 and now.
Only needs to be done once per an openai account.
Would make this much more useful.
Could also tell it what version of MC is being played at the start of each session, if you're not already.

I have gone over this before elsewhere and I feel like I'm gonna need to pin this so I don't keep getting asked this as it seems to be a common topic of discussion.
So it can't be done once per account, it has to be done with every conversation via proompting.
Properly fine tuning AI models is incredibly expensive and resource intensive, which is why only big, well funded companies and collectives can do that for models as large as GPT3.
The other way, proompting (providing the model with some initial context that it is missing) is I don’t want to provide the model with too much information at the beginning in order to reduce the amount of tokens the mod uses at a base level as it costs money. Thus, providing the necessary information for 1.18+ is not feasible with both goals in mind. I’d also be limiting how much context the model can process as you’re limited to 4096 tokens per request. It’s the reason I cut it off at 10 Chat messages, otherwise each question will cost the end user more and more money per question. It’s 0.002$/token currently and a token is ~4 characters.
Token usage will creep up from the base the more questions you ask as it needs the prior context, thus, keeping the context as short as possible is desirable.

I don't think you've actually read the docs for OpenAI's tuning:
https://platform.openai.com/docs/guides/fine-tuning
Yes it's more expensive, but it's not impossible.


How would one pass --use-tfstate option?

In order to work with remote state one would need to pass --use-tfstate option to infracost CLI. How can it be done with Github Actions?

@tovbinm thanks for creating this issue, I think #10 should work but I haven't had a chance to test it yet (was going to do tmrw). If you'd like to help test it, I think you can do the following in your GH Action to try the branch:
    - name: Run infracost diff
      uses: infracost/infracost-gh-action@add_tfstate
....
      with:
        use_tfstate: true

I haven't set tfdir since it's marked optional. I am not sure why the script complaints.
Running infracost on master branch using:
  $ infracost --no-color --log-level warn --use-tfstate
Directory "/github/workspace" does not have any .tf files.
Set the Terraform directory path using the --tfdir option.

I tried passing tfdir: . and tfdir: / but I got the following error:
 Running infracost on master branch using:
  $ infracost --no-color --log-level warn --use-tfstate --tfdir /github/workspace/master//

  ⠋ Running terraform show time="2020-11-11T03:24:57Z" level=error
time="2020-11-11T03:24:57Z" level=error msg="Error: Initialization required. Please see the error message above."
time="2020-11-11T03:24:57Z" level=error
time="2020-11-11T03:24:57Z" level=error

  ✖ Running terraform show

  Terraform command failed with:
    Error: Initialization required. Please see the error message above.

Error running terraform show: exit status 1

Do I need to pass Terraform Cloud credentials? How do I pass them into the Infracost container?

@tovbinm the --use-tfstate flag works by reading the statefile, and it looks like the above Terraform project is not init'd. Even if the creds are set, the project needs to be init'd, https://github.com/hashicorp/setup-terraform looks interesting, can you possibly try this:

in your GH repo, create a secret called TF_API_TOKEN and set it to your token.
add the following to your GH action yaml, before the infracost action runs:

steps:
- uses: hashicorp/setup-terraform@v1
  with:
    cli_config_credentials_token: ${{ secrets.TF_API_TOKEN }}
- run: terraform init
uses: infracost/infracost-gh-action@add_tfstate
....

Also, can you possibly share a little about your overall use-case with us?

I will try that. I wonder why you did not have to run any of that in this project - https://github.com/infracost/ci-demo

I was able to initialize Terraformin in both folders, but it did not help:
- name: Setup Terraform
        uses<EMAIL_ADDRESS>        with:
          cli_config_credentials_token: ${{ secrets.TF_API_TOKEN }}

      - name: Terraform init - master
        run: terraform init /home/runner/work/hephaestus/hephaestus/master

      - name: Terraform init - PR
        run: terraform init /home/runner/work/hephaestus/hephaestus/pull_request

      - name: Run Infracost diff
        uses: infracost/infracost-gh-action@add_tfstate
        env:
          INFRACOST_API_KEY: ${{ secrets.INFRACOST_API_KEY }}
          AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
          AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        with:
          use_tfstate: true
          tfdir: /

I still got the same error - https://github.com/infracost/infracost-gh-action/issues/9#issuecomment-725116964

I will try that. I wonder why you did not have to run any of that in this project - https://github.com/infracost/ci-demo

That repo uses plain --tfdir (which means infracost runs terraform init, plan then show), but passing --use-tfstate means that only show is needed as the state (.terraform/terraform.tfstate) can be used (that file is created when init runs).
Can you please try this, my previous suggestion was missing the working dir:
      - name: Terraform init - master
        run: terraform init
        working-directory: /home/runner/work/my-tf/my-tf/master

      - name: Terraform init - PR
        run: terraform init
        working-directory: /home/runner/work/my-tf/my-tf/pull_request

I use --use-tfstate because I selected Remote as my Execution Mode on my Terraform Cloud workspace - https://www.terraform.io/docs/cloud/workspaces/settings.html#execution-mode
I.e. Terraform does not keep any state locally and runs all the commands in the cloud.

@tovbinm makes sense, plz lmk if setting working-directory helped

No, the same issue. Terraform init passed just fine for both branches, but not the Infracost step.

In this repo's README, for the two actions/checkout@v2 steps, the path is set to master and pull_request and GH Actions default to cloning in /github/workspace, but I notice you're using /home/runner/work/my-tf/my-tf/, can those be changed to use the default github action workspace or does this GH Action need to be updated to make that a variable?
      - name: Terraform init - master
        run: terraform init
        working-directory: /github/workspace/master

      - name: Terraform init - PR
        run: terraform init
        working-directory: /github/workspace/pull_request

If I make this change, Terraform init fails with the following error: Error: No such file or directory.

can you possibly share the full yaml? I assume the init step is being run after the checkout?

on:
  pull_request:
    branches:
      - master
#     paths:
#       - '**.tf'
#       - '**.tfvars'
#       - '**.tfvars.json'
jobs:
  infracost:
    runs-on: ubuntu-latest
    name: Show infracost diff
    steps:
      - name: Checkout master branch
        uses<EMAIL_ADDRESS>        with:
          ref: master
          path: master

      - name: Checkout pull request branch
        uses<EMAIL_ADDRESS>        with:
          ref: ${{ github.event.pull_request.head.sha }}
          path: pull_request

      - name: Setup Terraform
        uses<EMAIL_ADDRESS>        with:
          cli_config_credentials_token: ${{ secrets.TERRAFORM_API_TOKEN }}

      - name: Terraform init - master
        run: terraform init
        working-directory: /github/workspace/master
        env:
          TF_WORKSPACE: dev

      - name: Terraform init - PR
        run: terraform init
        working-directory: /github/workspace/pull_request
        env:
          TF_WORKSPACE: dev

      - name: Run Infracost diff
        uses: infracost/infracost-gh-action@add_tfstate
        env:
          INFRACOST_API_KEY: ${{ secrets.INFRACOST_API_KEY }}
          AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
          AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        with:
          use_tfstate: true
          # tfdir: /

@tovbinm can you possibly join our Discord chat, maybe we can pair for a bit to troubleshoot this? (discord has voice+screenshare)

Thank you! Will do.

@tovbinm I found the root cause of this issue in case you'd like to subscribe to that for updates. Once that's resolved we can retest the GH Action without use_tfstate and see if this can be closed.

Thank you for digging into this @alikhajeh1

Fixed by https://github.com/infracost/infracost/issues/221. The following 2 env variables can be set in github, using the latest version of infracost's GH action, so the above yaml is not needed:
TERRAFORM_CLOUD_API_TOKEN: set to a Team API Token or User API Token
TF_WORKSPACE


Parse XML as String [Feature Request]

Sample XML
<rowtag>
   <element>a</element>
   <nested><nest>value</nest></nested>
</rowtag>

I'd like to be able to give a schema element:string, nested:string, such as the value of nested is
"<nest>value</nest>"
. Right now if I provide a schema with nested as StringType, it fails with a Scala MatchError
This is an improvement / feature request and not a bug. Don't know how hard it would be to implement?
Cheers!
Stephane

@maarest Thanks for reporting this and pointing this out precisely. Actually, I found this problem too. This PR, https://github.com/databricks/spark-xml/pull/107, will solve that issue. I will test this again with the PR.

any news on the testing?

@maarest Sorry, I have been busy. I realised I gave a wrong link. This was actually fixed in https://github.com/databricks/spark-xml/pull/106 and included in 0.3.3. So,
with the data below
<people>
  <rowtag>
    <element>a</element>
    <nested><nest>value</nest></nested>
  </rowtag>
</people>

this code below:
val schema = StructType(
  Seq(
    StructField("element", StringType, nullable = true),
    StructField("nested", StringType, nullable = true)))
val df = sqlContext.read
  .format("xml")
  .option("rowTag", "rowtag")
  .schema(schema)
  .load(agesFile)

will produce the results below:
root
 |-- element: string (nullable = true)
 |-- nested: string (nullable = true)

+-------+------------------+
|element|            nested|
+-------+------------------+
|      a|<nest>value</nest>|
+-------+------------------+


duplicate option how to ?

is there a way to allow duplicate,

You can set the allowDuplicates option to true.
new Taggle(containerId, {
    allowDuplicates: true
});

thanks for answering


automatic listing of the @mentions

Sometimes when I click on the Discussion panel, it automagically includes all the @ mentions.
This is rather nice (sometimes) but I would like to know exactly how to trigger this black magic as it does not happen every time.
Anyone know or experience what I am talking about?

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

ID: 34ae521f-6ae4-4d7f-2cce-f844e5811b66
Version Independent ID: 18098490-1f34-e966-3135-cb90197bfa6f
Content: Use @mentions in work items and pull requests - Azure DevOps
Content Source: docs/notifications/at-mentions.md
Product: devops
Technology: devops-collab
GitHub Login: @chcomley
Microsoft Alias: chcomley

@sheirNRC -- thank you for your question.  You may find answers here:

DBA Stack Exchange
Stack Overflow

I am closing this issue now.  You are welcome to @ mention me for any followup.  We hope to hear from you again.


[Bug] Enter button is closing the popup

Is there an existing issue for this?

[X] Yes, I have searched the existing issues and none of them match my problem.

Product Variant
Cloud (http://rxresu.me)
Current Behavior

Expected Behavior
The modal should remained open
Steps To Reproduce

Go to editor
Add and experiencece
In Model click the enter button

What browsers are you seeing the problem on?
No response
What template are you using?
None
Anything else?
No response

This should be solved in the next update, although I wasn't able to reproduce the issue exactly.


Should mouths be more generic, with emotion modifiers?

Interesting idea by a ZenGM Discorder below
Ultimately I really like the set of mouths right now so I wouldn't fully vouch for this change, but it's interesting
Could correlate with how the player feels about re-signing with the team in BBGM or similar
https://discord.com/channels/290013534023057409/331882115119448065/1234550634280386591

This would be an awesome feature, but is not the easiest thing to do. The current implementation of just pasting a bunch of SVGs on top of each other is really simple - easy to maintain, easy to add new features even for a non-developer. Moods would complicate that. Not sure if it's worth it.
Also ideally it'd probably not just be mouths, it'd be other features too.


Unresolved reference: AdapterList

Compose version: 0.3.0-build136
AdapterList was added in Version 0.1.0-dev15 of Compose UI. When we can expect it to be available in Compose for Desktop?

I'm fairly certain that was replaced with LazyColumn.

Yes, we share API (MPP) with the Jetpack Compose, so it's likely there.

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


Hardware specific targets and other minor modifications

This update adds:

a flag to distinguish HW and SW brokers
enables or disables HW only or SW only targets depending on the flag
modifies some targets to supply different metrics for SW and HW brokers or use different SEMP queries
several hardware only targets
minor updates to some targets to add additional metrics e.g. spool + transactions
a new version of the bridge target which adds labels for remote VPNs and Routers
along with readme updates

Thanks for adding those feature. Can you please make the modification i mentioned above?

I think I have made the updates so they feed back in correctly (not a super confident GitHub user!)

Hi Heiko,
I’m not entirely sure this will get through to you, but fingers crossed it will!
It looks like when my changes were merged the updated version wasn’t tagged with a new release number – this may be entirely my fault as I’m not a very competent GitHub user.  This means that the new Docker build is only available as “latest” and “latest” is not the same version as the most recent numbered version (1.7.2.)
Would it be possible to add a new version tag and re-release it?
Thanks,
David
From: Heiko Henning @.>
Date: Friday, 9 August 2024 at 15:59
To: solacecommunity/solace-prometheus-exporter @.>
Cc: David Wray @.>, Author @.>
Subject: Re: [solacecommunity/solace-prometheus-exporter] Hardware specific targets and other minor modifications (PR #74)
Warning - this email originated outside of Solace. Please think before you click or open any links or attachments. If this email is suspicious, report it to @.***
Merged #74https://github.com/solacecommunity/solace-prometheus-exporter/pull/74 into master.
—
Reply to this email directly, view it on GitHubhttps://github.com/solacecommunity/solace-prometheus-exporter/pull/74#event-13822220314, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AA6KNCHO2WDIVF35KGJDMN3ZQTKNLAVCNFSM6AAAAABMEUSHYOVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJTHAZDEMRSGAZTCNA.
You are receiving this because you authored the thread.Message ID: @.***>

Confidentiality notice
This e-mail message and any attachment hereto contain confidential information which may be privileged and which is intended for the exclusive use of its addressee(s). If you receive this message in error, please inform sender immediately and destroy any copy thereof. Furthermore, any disclosure, distribution or copying of this message and/or any attachment hereto without the consent of the sender is strictly prohibited. Thank you.

Was released in:
https://github.com/solacecommunity/solace-prometheus-exporter/releases/tag/v1.8.0

Thanks 😊
From: Heiko Henning @.>
Date: Thursday, 5 September 2024 at 05:01
To: solacecommunity/solace-prometheus-exporter @.>
Cc: David Wray @.>, Author @.>
Subject: Re: [solacecommunity/solace-prometheus-exporter] Hardware specific targets and other minor modifications (PR #74)
Warning - this email originated outside of Solace. Please think before you click or open any links or attachments. If this email is suspicious, report it to @.***
Was released in:
https://github.com/solacecommunity/solace-prometheus-exporter/releases/tag/v1.8.0
—
Reply to this email directly, view it on GitHubhttps://github.com/solacecommunity/solace-prometheus-exporter/pull/74#issuecomment-2330549942, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AA6KNCGLFPIGBFILAAOH2FLZU7JSXAVCNFSM6AAAAABMEUSHYOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZQGU2DSOJUGI.
You are receiving this because you authored the thread.Message ID: @.***>

Confidentiality notice
This e-mail message and any attachment hereto contain confidential information which may be privileged and which is intended for the exclusive use of its addressee(s). If you receive this message in error, please inform sender immediately and destroy any copy thereof. Furthermore, any disclosure, distribution or copying of this message and/or any attachment hereto without the consent of the sender is strictly prohibited. Thank you.


"docker image build & publish" Starter template

We'd love to have a "docker image build and publish" starter template.
Recommended approach and best practices for creating a starter template - (coming soon with https://github.com/dagger/dagger/issues/2642 )

We currently have this in our docs in our QuickStart: https://docs.dagger.io/quickstart. I'm closing this issue


[Feature] Make application into user friendly Jupyter notebook

currently executed in command line with python quiz_reports.py
make into Jupyter notebook
include ONLY user-friendly instructions and minimal code in notebook - treat like a user interface
add printouts for progress and errors

make a priority


Make column filter input type Number

Issue Type (delete the irrelevant ones)

[x] Bug
[x] Enhancement Request
[x] Question

Specs
What version are you using?
2.21.0
What browser?
Chrome
Expected Behavior
Change filter input type from 'text' to 'number' when setting the 'type' column option to 'number'.
Actual Behavior
The input type stays as 'text'

hey @dashtydit, you can use custom column filters to use whatever input type you want to use for filters.
https://xaksis.github.io/vue-good-table/guide/advanced/#custom-column-filters
closing.


Throw proper exception upon missing discriminator field value

I confirm this bug
I've no idea till now , how ODM doesn't add the discrimination filed automatically , the $name , is still not enough , simple logic , If the $name was what all needed , then what's the use of discrimination filed then ?!
There must be away to raise error when discrimination field is missing or add it automatically somehow

how ODM doesn't add the discrimination filed automatically

I believe this was only coming up with projections. I wouldn't have expected users to use "include" mode in a projection (e.g. { x: 1, y: 1 }, where all unlisted fields apart from _id are implicitly excluded) and still expect the data to be hydrated into a class (instead of using hydrate(false) in the query builder and getting raw data back).
In any event, #1164 should help with this. I also think we can still throw an exception here, though, as a fall back, since there's still the possibility that the discriminator doesn't exist in the actual BSON document in MongoDB, and we should have some nicer handling around that.


Add dv response conversion to csv

Hank.ai DocuVision API Sample Code

Convert DocuVision json response files into CSV format.
If --json not passed, will convert ALL .json files in the given --dir to .csv format (or current dir if --dir not passed)
if --json is passed, will convert ONLY that .json file

Example command line command to convert all jsons in directory c:/test/ and create seperate csvs for each unique pid
python convertResultToCSV.py --dir c:/test/ --splitonpid 1 --loglevel DEBUG

Prerequisites:
- Python 3.7.7 or greater installed
- pandas (pip install pandas)
Args: (command line args)
- --dir: (optional) full path to a directory on the current machine you'd like to post to DocuVision API. default=current directory
- --splitonpid: (optional) if 1 will create, in addition to main
- --recursive: (optional) if 1 and --dir passed and not --json passed, will look inside --dir recursively and process .json files
- --json: (optional) full path to a .json file result from DocuVision to convert to csv. If given, --dir will be ignored
- --loglevel: (optional) how verbose you want to logging to be to the csvconversion.log file
Results:
- will save a .csv file alongside each .json with the same filename stem
- will append logging info to csvconversion.log in same dir as this script is run from

must have done something wrong i guess. the file comparison between this pull request and main isn't accurate. most of the changes in the batchsend...py file are already in main. not sure why they're showing up as changes here.


Error "split items cannot be empty" with helm processor and OpenShift GitOps

When trying to deploy a Helm Application, I get the following error message. I think this error comes from helmProcessor.go but I do not know how I could debug this further.
Error
Failed to load target state: failed to generate manifest for source 1 of 1: rpc error: code = Unknown desc = Manifest generation error (cached): plugin sidecar failed. error generating manifests in cmp: rpc error: code = Unknown desc = error generating manifests: `argocd-lovely-plugin` failed exit status 1: 2024/10/31 08:47:44 split items cannot be empty

Environment Information
We are running the plugin inside OpenShift with the OpenShift Gitops Operator, similar to the ArgoCD Operator but supported by RedHat.
Application (redacted)
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: demo
  namespace: demo
spec:
  destination:
    name: in-cluster
  project: default
  source:
    path: demo
    plugin:
      name: argocd-lovely-plugin
      parameters:
      - name: LOVELY_HELM_VALUES
        string: "{}"
    repoURL: https://github.com/xxx/yyy.git
    targetRevision: main
  syncPolicy:
    automated:
      prune: true
      selfHeal: true
    syncOptions:
    - PruneLast=true

Installation (redacted)
apiVersion: argoproj.io/v1beta1
kind: ArgoCD
metadata:
  name: xxxx
  namespace: xxxx
  annotations:
    argocd.argoproj.io/sync-options: Delete=false
spec:
  repo:
    serviceaccount: repo-sa
    mountsatoken: true
    sidecarContainers:
      - name: lovely-plugin
        image: xxxx # Custom Image using ubi9 as base
        envFrom:
          - secretRef:
              name: argocd-lovely-plugin-env
        securityContext:
          runAsNonRoot: true
        volumeMounts:
            # Import the repo-server's plugin binary
          - mountPath: /var/run/argocd
            name: var-files
          - mountPath: /home/argocd/cmp-server/plugins
            name: plugins
            # Starting with v2.4, do NOT mount the same tmp volume as the repo-server container. The filesystem separation helps
            # mitigate path traversal attacks.
          - mountPath: /tmp
            name: lovely-tmp
    volumes:
      - emptyDir: {}
        name: lovely-tmp

Custom Image Containerfile
Because of OpenShift special handling of users, we had to build our own Containerfile supporting it. However it includes all the binary from lovely-vault-plugin:1.1.1
FROM ghcr.io/crumbhole/lovely-vault-plugin:1.1.1 AS source

FROM registry.access.redhat.com/ubi9:9.4

# Switch to root for the ability to perform install
USER root

# Install tools needed for your repo-server to retrieve & decrypt secrets, render manifests
# (e.g. curl, awscli, gpg, sops)
RUN yum update -y
RUN yum install -y curl git --allowerasing
RUN yum clean all
RUN rm -rf /var/cache/yum/* /tmp/* /var/tmp/*

ENV LOVELY_HELM_PATH=/usr/local/bin/helm
ENV LOVELY_HELMFILE_PATH=/usr/local/bin/helmfile
ENV LOVELY_KUSTOMIZE_PATH=/usr/local/bin/kustomize
ENV LOVELY_PLUGINS=
ENV LOVELY_PREPROCESSORS=
ENV HOME=/tmp
ENV HELM_CONFIG_HOME=/tmp/.helm
ENV HELM_CACHE_HOME=/tmp/.helm
ENV HELM_DATA_HOME=/tmp/.helm
COPY --from=source /usr/local/bin/yq /usr/local/bin/yq
COPY --from=source /usr/local/bin/helm /usr/local/bin/helm
COPY --from=source /usr/local/bin/helmfile /usr/local/bin/helmfile
COPY --from=source /usr/local/bin/kustomize /usr/local/bin/kustomize
COPY --from=source /usr/local/bin/argocd-vault-plugin /usr/local/bin/argocd-vault-plugin
COPY --from=source /usr/local/bin/argocd-lovely-plugin /usr/local/bin/argocd-lovely-plugin
ADD *.pem /etc/pki/ca-trust/source/anchors/
RUN update-ca-trust

# Switch back to non-root user
USER 999
ENV LOVELY_PLUGINS="argocd-vault-plugin generate -"
RUN mkdir -p /tmp/.helm
COPY --from=source --chown=999 /home/argocd/cmp-server/config/plugin.yaml /home/argocd/cmp-server/config/plugin.yaml
COPY --from=source /entrypoint.sh /entrypoint.sh
# /var/run/argocd/argocd-cmp-server does NOT exist inside the image, must be mounted from argocd
ENTRYPOINT [ "/entrypoint.sh" ]

Installation Details

OpenShift GitOps Operator
ArgoCD Version: v2.12.6+4dab5bd
Lovely Version: 1.1.1 (Vault Flavor)
OpenShift Version: 4.16.14
Kubernetes Version: v1.29.8+f10c92d

I believe this error is coming from:
      parameters:
      - name: LOVELY_HELM_VALUES
        string: "{}"

I'm not sure why you get that error at the moment, but that definitely looks to be wrong. HELM_VALUES should be a list of one or more file names.

Hi @Joibel
You, of course, are right, I totally missed the variable is to specify files. I was porting the original Helm integration, where you could specify a JSON string.
Thx for helping out. :)


new file python.json

inserted all the necessary definitions of python language
The Pull Request resolves Issue #3108
Description:
A brief description about the addition or edits made.

Duplicate of #3109


README.md Images Broken in maha-service 'test' Directory

2 images broken:
https://github.com/ZhaoqiWang0605/maha/tree/master/service/src/test

Test non-broken badge image:

Test broken badge images:

Generate images with user-images.githubusercontent.com subdomain by uploading the images:
Image 1 (Dims - Relations):

Image 2 (Dims - Alternative Engines):

Image 3 (Facts - Relations with Dims):

Fix the issue in https://github.com/yahoo/maha/pull/764


Connect AQARA TVOC Air Quality Monitor

Discussed in https://github.com/AlexxIT/XiaomiGateway3/discussions/414

Originally posted by Kejszijo July 27, 2021
Hi,
I bought a AQARA TVOC Air Quality Monitor and I want to connect to my gateway 3.
I try this command, but it not connect it.
service: remote.send_command
data:
entity_id: remote.gatewayID_pair
command: pair
device: lumi.airmonitor.acn01
I push the button on the air monitor for 5-10 sec, I see the connect icon, but nothing happened.
Any suggestion?
Thanks!

Maybe gateway should have latest firmware to support this device. Maybe Xiaomi account should be connected to China server

Use Mi Home app, add temperature/humidity zigbee device. Long press the button of TVOC air monitor  8 seconds and release

Use Mi Home app, add temperature/humidity zigbee device. Long press the button of TVOC air monitor 8 seconds and release

Hi,
Which firmware version do you use?
I use 1.4.6_0043. Europe region with EU region gateway3 and unfortunately not working this preocess.
Home app does not offer firmware upgrade.

1.5.

@Kejszijo you can't pair this sensor if you use eu region. switch to cn and pair there. you may need firmware update before.

@Kejszijo you can't pair this sensor if you use eu region. switch to cn and pair there. you may need firmware update before.

Hi,
Can I add EU gateway in China region? Or I must buy a CN Gateway?

yes, you can.

I use 20 connected sensor with this Gateway in EU region. If I think well and I put my gateway to China region, I must reset my gateway (lose my sensors), connect it in china region again, and I must reconnect all sensors again to gateway and configure with HA. Right?

reset gateway by pressing button for 10s and pair to chinese region. then press button 3 times (trippleclick) and reset tvoc sensor. they should pair. reset hub again and move to eu. no sensors should be lost. btw: tvoc sensor is not supported in mi home so you can only access it from HA.

reset gateway by pressing button for 10s and pair to chinese region. then press button 3 times (trippleclick) and reset tvoc sensor. they should pair. reset hub again and move to eu. no sensors should be lost. you can ofc stay on chinese region if you want.
btw: tvoc sensor is not supported in mi home so you can only access it from HA.

Thanks, it's works. It forget the devices name after I go back to EU region, but that is the least. :)
I want to use it with HA, I don't use Mi Home app, so this is perfekt for me.
Information: The sensor works with 1.4.6_0043 firmware.

1.5.

Use Mi Home app, add temperature/humidity zigbee device. Long press the button of TVOC air monitor 8 seconds and release

Hi,
Which firmware version do you use?

1.5.0

I use 1.4.6_0043. Europe region with EU region gateway3 and unfortunately not working this process.
Home app does not offer firmware upgrade.

wait new firmware release, or use custom firmware upgrade (need notice that EU firmware is signed or not)

Hello!!
I just bought the tvoc sensor but doesn't pair with Mi Home, I reseted the device a lot of times but the gateway 3 (lumi.gateway.mgl03) does not detect it.
My GW firmware version is: 1.5.4_0090
Thanks a lot!


City State List and World Tracker

Hi,
City state list shows only first state you encountered and don't let you give any envy. And World tracker at the left top off the screen doesn't show any tech or civics progress.

Are you on Rise and Fall ? Or playing on the base game (without Rise and Fall)

I'm playing with rise and fall ruleset

Used a "reveal all" command after few turns and as you can see at the picture, tech and civics processes aren't shown and city state list doesn't show all the states.

CQUI is not compatible with Rise and Fall yet, see #283


use Placeholders to decide the index name

Hi, I want to modify the fluent.conf and rebuild the fluentd-daemonset-elasticsearch .As long as I know, we can use placeholder to define the index name dynamically ,like https://github.com/uken/fluent-plugin-elasticsearch .
so I modify the fluentd.conf  is:
<match log.*>
 @type elasticsearch
#  hosts XX:9200,XX9200,XX:9200
  hosts "#{ENV['ELASTICSEARCH_HOST']}"
#  port "#{ENV['ELASTICSEARCH_PORT']}"
  ssl_verify "#{ENV['FLUENT_ELASTICSEARCH_SSL_VERIFY']}"
#  target_index_key ESIndex
#  index_name 200000602_200001027
  index_name elastic.${tag}
  <buffer tag>
    @type memory
  </buffer>
  type_name system_log
</match>

But it will regard the index name as "elastic.${tag}" ,not variable.
Is the placeholder supported? Any mistake above?
Any suggestion will be thankful.

have been solved
https://github.com/uken/fluent-plugin-elasticsearch/issues/509

have been solved https://github.com/uken/fluent-plugin-elasticsearch/issues/509

Hi, this link is broken. How did you solve this?


$INCLUDE and relative paths

Hi,
I see that previously this project changed from treating $INCUDE directives relative to the CWD to being relative to the file: https://github.com/miekg/dns/issues/537
As far as I can tell, however, this behavior is not specified by the RFC one way or another, and implementations vary. Here's the relevant standard:
RFC-1035:
Two control entries are defined: $ORIGIN and $INCLUDE.  $ORIGIN is
followed by a domain name, and resets the current origin for relative
domain names to the stated name.  $INCLUDE inserts the named file into
the current file, and may optionally specify a domain name that sets the
relative domain name origin for the included file.  $INCLUDE may also
have a comment.  Note that a $INCLUDE entry never changes the relative
origin of the parent file, regardless of changes to the relative origin
made within the included file.

That RFC obsoleted the earlier RFC-883 which had this to say:
      An include line begins with $INCLUDE, starting at the first line
      position, and is followed by a local file name and an optional
      offset modifier.  The filename follows the appropriate local
      conventions.  The offset is one or more labels that are added to
      the offset in use for the file that contained the $INCLUDE.  If
      the offset is omitted, the included file is loaded using the
      offset of the file that contained the $INCLUDE command.  For
      example, a file being loaded at offset ARPA might contain the
      following lines:

                $INCLUDE <subsys>isi.data ISI
                $INCLUDE <subsys>addresses.data

      The first line would be interpreted to direct loading of the file
      <subsys>isi.data at offset ISI.ARPA.  The second line would be
      interpreted as a request to load data at offset ARPA.

      Note that $INCLUDE commands do not cause data to be loaded into a
      different zone or tree; they are simply ways to allow data for a
      given zone to be organized in separate files.  For example,
      mailbox data might be kept separately from host data using this
      mechanism.

I haven't been able to find another RFC which discusses $INCLUDE directives, though it's entirely possible I missed one.
Given that the most we get from either of these is "The filename follows the appropriate local conventions", could the behavior of relative includes be made a configuration option? I have an existing set of zone files which use "relative to CWD" includes, and I can certainly update the files, but it might be nice if the library could support either mode of operation.

Thinking about it more, the most flexible option would be a way to specify the base for relative includes, generically. Default can be the file. Something like func (zp *ZoneParser) SetIncludeRelativeBase (p string) maybe? Then the caller would have full control.

i don't think we need flexibility here


Document DUPLICATE_USE_INSTANCING #2770

I guess you meant to reference godotengine/godot-docs#2770 instead of #2770?

Oops, clicked merge before seeing that there were two commits instead of one... Next time, please amend the original commit or rebase to squash them instead of making several commits for a single change (see PR workflow for Git usage instructions matching this workflow).
Thanks nevertheless for the docs improvement :)

Sorry didn't know about that.
I'll read it carefully and hope my next commit is without any faults!
Thanks for this incredible open source project.
I'll try to contribute more. :)


feat(firebase_analytics): add appInstanceId property

Add an appInstanceId property on FirebaseAnalytics, exporting the API from the underlying native Firebase library implementations.
Description
This value is needed to send server-side events through the Measurement Protocol as a part of the same session, and also useful for debugging to pair up with the data visible in DebugView and BigQuery.
Related Issues
Replace this paragraph with a list of issues related to this PR from the issue database. Indicate, which of these issues are resolved or fixed by this PR. Note that you'll have to prefix the issue numbers with flutter/flutter#.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (melos run analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change.
[x] No, this is not a breaking change.

Thanks for the code review @russellwheatley!
I'll wait till your PR is merged and rebase, so I don't create a merge conflict.
Just to understand the second point, do we still need to use a TaskCompletionSource when we already have a Task? I think I'd need to Tasks.await to get the value out of that Task to pass to taskCompletionSource.setResult?

@willbryant, yes, for consistency and to use the cachedThreadPool . You can do the following:
taskCompletionSource.setResult(Tasks.await(analytics.getAppInstanceId()));

Cool, that's basically what I did.
I added a try/finally for consistency with the others.

Done, and squashed.

Hey @willbryant, do you mind also adding an e2e test to analytics if possible? 😄

@russellwheatley I can't get e2e tests to run for the life of me, but I've pushed a draft, if you wouldn't mind approving a CI run.

Struggling a bit without CI access, can't get the main e2e test directory to run locally. But, I discovered there's a sort of second copy under example/ in the plugin itself, which showed the same issue, so using that I made a bit more progress.
Hopefully the next run works better.

@willbryant run melos run format and all should be well. Tip for future: comment out all e2e tests here and run melos run test:e2e for testing analytics e2e (provided you've installed melos).
Some of the e2e's need the emulators running to work (e.g. firebase_database) so maybe that was your problem.
I'm also presuming you've ran melos boostrap in the project directory 😄

ahh, you'll have to run flutter format .in tests/ directory. Melos doesn't pick that up at the moment 😞

Hopefully that's it, thanks for you help :).


Feed canvas HTML object to BCGE.Stage()

Done #https://github.com/TheGLander/BadCanvasGameEngine/commit/602008609e53d4446238fe375491eae42d7a3a4d


Laravel Breeze and Inertia

Will breeze with inertia be supported with this package at some point?
https://laravel.com/docs/8.x/starter-kits#breeze-and-inertia

Thanks @PovilasKorop for all of your work!


Fixing tooltip for count and sum_matches in comparison viewer dashboard tooltip

Until now, the tooltip found by hovering over the histogram bars on the comparison viewer dashboard has always shown 'NaN' for the count and sum_matches fields. This patch fixes this.
The cumulative comparisons field has yet to be fixed.
All tests pass on my fork.

Thanks!


Use pcntl_exec() instead of passthru() for artisan's serve command.

artisan's serve command currently uses passthru() for running PHP's built-in web server. However, this kills the ability of have color output on the terminal, and most importantly, it also prevents PsySH from properly working when an eval(\Psy\sh()) is put into the code (and it is rather useful for debugging).
This PR switches the passthru() call to pcntl_exec() to solve the problems described above.

Hi. PCNTL extension is not available on Windows.

Solution is to use symfony's process component properly.


build: introduce a CMake based build for swift-format

This is in preparation to use SwiftFormat from SourceKit-LSP which is distributed as part of the toolchain.
On Windows, we are now able to build swift-format against the shared Swift Syntax package, yielding an overall size reduction:
SPM
swift-format.exe: 75,683,840 b
CMake
swift-format.exe:    830,464 b
SwiftFormat.dll:   7,818,240 b
Net Savings: 67,035,136 b

This does require apple/swift-cmark#69 as well as apple/swift-markdown#141

CC: @ahoppen

Now that the base change is in, yes, it is possible to do the toolchain test - which is not a "good" but really a "must" as we risk breaking the Windows installer build at the very least and we need to ensure that the packaged content is correct.


Seqfault on multiple actor data pass w expect

This is a minimal use case extracted from our code base. Note that this bug does not occur if you aren't using the expect() method on TCPConnection.
use "collections"
use "net"
use "options"
use "time"

actor Main
  new create(env: Env) =>

      var d_arg: (Array[String] | None) = None
      var l_arg: (Array[String] | None) = None
      var n_arg: (String | None) = None

      try
        var options = Options(env)

        options
          .add("listen", "l", StringArgument)

        for option in options do
          match option
          | ("listen", let arg: String) => l_arg = arg.split(":")
          end
        end

          let listener_addr = l_arg as Array[String]

          let store = Store
          let decoder = Decoder(store)

          let tcp_auth = TCPListenAuth(env.root as AmbientAuth)
          let from_buffy_listener = TCPListener(tcp_auth,
            MyListenerNotify(decoder, env.err),
            listener_addr(0),
            listener_addr(1))

      end

class MyListenerNotify is TCPListenNotify
  let _decoder: Decoder
  let _stderr: StdStream

  new iso create(decoder: Decoder, stderr: StdStream) =>
    _decoder = decoder
    _stderr = stderr

  fun ref connected(listen: TCPListener ref): TCPConnectionNotify iso^ =>
    FromBuffyNotify(_decoder, _stderr)

class FromBuffyNotify is TCPConnectionNotify
  let _decoder: Decoder
  let _stderr: StdStream
  var _header: Bool = true

  new iso create(decoder: Decoder, stderr: StdStream)
  =>
    _decoder = decoder
    _stderr = stderr

  fun ref received(conn: TCPConnection ref, data: Array[U8] iso) =>
    if _header then
      try
        let expect = Bytes.to_u32(data(0), data(1), data(2), data(3)).usize()
        conn.expect(expect)
        _header = false
      else
        _stderr.print("Blew up reading header")
      end
    else
      _decoder.received(consume data, Time.wall_to_nanos(Time.now()))

      conn.expect(4)
      _header = true
    end

  fun ref accepted(conn: TCPConnection ref) =>
    conn.expect(4)

actor Decoder
  let _store: Store

  new create(store: Store) =>
    _store = store

  be received(data: Array[U8] iso, at: U64) =>
    _store.received(consume data, at)

actor Store
  be received(msg: ByteSeq, at: U64) =>
    None

primitive Bytes
  fun to_u16(high: U8, low: U8): U16 =>
    (high.u16() << 8) + low.u16()

  fun to_u32(a: U8, b: U8, c: U8, d: U8): U32 =>
    (a.u32() << 24) + (b.u32() << 16) + (c.u32() << 8) + d.u32()

  fun to_u64(a: U8, b: U8, c: U8, d: U8, e: U8, f: U8, g: U8, h: U8): U64 =>
    (a.u64() << 56) + (b.u64() << 48) + (c.u64() << 40) + (d.u64() << 32)
    + (e.u64() << 24) + (f.u64() << 16) + (g.u64() << 8) + h.u64()

  fun from_u16(u16: U16, arr: Array[U8] iso = recover Array[U8] end): Array[U8] iso^ =>
    let l1: U8 = (u16 and 0xFF).u8()
    let l2: U8 = ((u16 >> 8) and 0xFF).u8()
    arr.push(l2)
    arr.push(l1)
    consume arr

  fun from_u32(u32: U32, arr: Array[U8] iso = recover Array[U8] end): Array[U8] iso^ =>
    let l1: U8 = (u32 and 0xFF).u8()
    let l2: U8 = ((u32 >> 8) and 0xFF).u8()
    let l3: U8 = ((u32 >> 16) and 0xFF).u8()
    let l4: U8 = ((u32 >> 24) and 0xFF).u8()
    arr.push(l4)
    arr.push(l3)
    arr.push(l2)
    arr.push(l1)
    consume arr

  fun from_u64(u64: U64, arr: Array[U8] iso = recover Array[U8] end): Array[U8] iso^ =>
    let l1: U8 = (u64 and 0xFF).u8()
    let l2: U8 = ((u64 >> 8) and 0xFF).u8()
    let l3: U8 = ((u64 >> 16) and 0xFF).u8()
    let l4: U8 = ((u64 >> 24) and 0xFF).u8()
    let l5: U8 = ((u64 >> 32) and 0xFF).u8()
    let l6: U8 = ((u64 >> 40) and 0xFF).u8()
    let l7: U8 = ((u64 >> 48) and 0xFF).u8()
    let l8: U8 = ((u64 >> 56) and 0xFF).u8()
    arr.push(l8)
    arr.push(l7)
    arr.push(l6)
    arr.push(l5)
    arr.push(l4)
    arr.push(l3)
    arr.push(l2)
    arr.push(l1)
    consume arr

  fun length_encode(data: Array[U8] val): Array[U8] val =>
    let len: U32 = data.size().u32()
    let arr: Array[U8] iso = Bytes.from_u32(len, recover Array[U8] end)
    arr.append(data)
    consume arr

  fun u16_from_idx(idx: USize, arr: Array[U8]): U16 ? =>
    Bytes.to_u16(arr(idx), arr(idx + 1))

  fun u32_from_idx(idx: USize, arr: Array[U8]): U32 ? =>
    Bytes.to_u32(arr(idx), arr(idx + 1), arr(idx + 2), arr(idx + 3))

  fun u64_from_idx(idx: USize, arr: Array[U8]): U64 ? =>
    Bytes.to_u64(arr(idx), arr(idx + 1), arr(idx + 2), arr(idx + 3),
      arr(idx + 4), arr(idx + 5), arr(idx + 6), arr(idx + 7))

Note that there are 2 ways to fix this bug, both of which are weird. If you change be received(msg: ByteSeq, at: U64)  on Store to be a Array[U8] iso instead of a ByteSeq, there will be no more seqgault.
OR
You can change the be received(data: Array[U8] iso, at: U64) on Decoder to use ByteSeq rather than Array[U8] iso and the seqfault goes away. You need to pass the Array[U8] iso through the first actor to the 2nd in order to trigger the bug.
Note that on Store, the same bug occurs with Array[U8] val as it does with ByteSeq.
@sylvanc is already aware of this bug. We had fun on Saturday WTF'ing over it.

I tried running this code again with all the changes we have made and this no longer occurs. Perhaps a change in Pony, perhaps it was related to the llvm I had installed at the time. Closing.


GetIndexEvent

Refactor existing get index event.

[x] Add type definition.
[x] Add unit test.
[x] Add feature test.
[x] Add documentation.

References upstream API issue HTTP GET / - GetIndexController #67.

Additional documentation will be postponed until the new documentation system is up and running - likely end of 2024.


review of Zellweger spectrum disorders

According to GeneReviews and GHR
https://www.ncbi.nlm.nih.gov/books/NBK1448/#pbd.Nomenclature
The relationships should look something like
Peroxisome biogenesis disorders

Zellweger spectrum disorder
** Zellweger syndrome
***all its gene-specific subclasses
** neonatal adrenoleukodystrophy (NALD)
**infantile Refsum disease
rhizomelic chondrodysplasia punctata spectrum

Do we need another node between peroxisome biogenesis disorder
and Zellweger syndrome  for the Zellweger spectrum?

@ahamosh , @GARDInfoCenter any insights?

And I do see that all the gene-specific subclasses should not be under Zellweger syndrome, given that PEROXISOME BIOGENESIS DISORDER 3B; PBD3B is not a Zellweger
NCIT does have a node for Zellweger spectrum.
http://www.ontobee.org/ontology/NCIT?iri=http://purl.obolibrary.org/obo/NCIT_C146639

Just following up, this remains an unresolved issue. @nicolevasilevsky Can you look into this please?

Ok, Not sure exactly what the question is.  OMIM has Zellweger which is neonatal onset and lethal and then NALD and IRD are listed peroxisomal biogenesis disorders which have prolonged survival, but overlap.  They are not lethal in the first year, hence the separation.  The descriptions in 214100 or 601539 explain this.  We also don't have a Zellweger spectrum.  We use the term Zellweger with more lethal biogenesis disorders (numbered with an A).

I am also unclear what the question is.
@maglott and @kanems Would you like to request a new term? We do have MONDO_0019234 'peroxisome biogenesis disorder' which is equivalent to NCIT:C146639  Zellweger spectrum.
Would you like a rearrangement of the current hierarchy?

The original question was establishing relationships as in GeneReviews.
Peroxisome biogenesis disorders as a parent.
Peroxisome biogenesis disorders

Zellweger spectrum disorder
** Zellweger syndrome

NORD (https://rarediseases.org/rare-diseases/zellweger-spectrum-disorders/) does  equate Peroxisome biogenesis disorders and Zellweger spectrum.  I am not an expert. Just asking whether they should be equated or not given as I read it rhizomelic chondrodysplasia punctata spectrum is a peroxisome biogenesis disorder but not in the zellweger spectrum.

Currently Zellweger syndrome is a child of 'peroxisome biogenesis disorder' which is equivalent to NCIT:C146639 Zellweger spectrum.
I am also not an expert, so I cannot comment if it is appropriate for 'peroxisome biogenesis disorder' to be equivalent to Zellweger spectrum, but that is how we currently have it modeled in Mondo.
MONDO_0015776 'rhizomelic chondrodysplasia punctata' is not a child of peroxisome biogenesis disorder in Mondo (it is a child of MONDO_0016398 'peroxisomal disease with epilepsy').
I may be misunderstanding, but it seems like this current classification is okay?

If I thought it was OK I would not have created the ticket.  Again, I am not an expert either, but Nancy Braverman is and she authored https://www.ncbi.nlm.nih.gov/books/NBK1270/ where it states

Rhizomelic chondrodysplasia punctata type 1 (RCDP1), a peroxisome biogenesis disorder (PBD) has a classic (severe) form and a nonclassic (mild) form.

And https://www.ncbi.nlm.nih.gov/books/NBK1448/, specifically https://www.ncbi.nlm.nih.gov/books/NBK1448/#pbd.Nomenclature, where the distinctions are made that I tried to suggest.
We are trying to be consistent with MONDO, but have reservations about equating peroxisomal biogenesis disorder with Zellweger spectrum.

@cmungall and @pnrobinson could you please weigh in? Thanks!

In OMIM we treat RCDP as a Peroxisome biogenesis disorder, but not as part of the Zellweger spectrum.  Not sure it helpful, but I did get a clarification from Joanna and Anne on the OMIM team.

[ ] Zwelleger should not be an exact syn for 'peroxisome biogenesis disorder'
[ ] add grouping class for 'Heimler syndrome 1' and 'Heimler syndrome 2' (https://en.wikipedia.org/wiki/Heimler_syndrome)

@maglott https://rarediseases.org/rare-diseases/zellweger-spectrum-disorders/
based on the NORD page, it doesn't seem that zellweger spectrum disorders is justified as a separate class (discussing with @cmungall now)

Thanks


adding distributed_by support from annotation in ddlog

adding distributed_by support from annotation in ddlog

Thanks for adding this feature!  Can you do a make checkstyle and also rebase to the latest branch in addition to my inline comments?

@ThomasPalomares Please rebase onto 959282f11c6265c8f85ea9327eba9d0b85f46408 as the latest commit does not fully pass the test yet.  Sorry!

Ahah sure. Also, concerning your previous comments, I added comments near the beginning and checked the trail spaces with a make checkstyle. I am not sure about how to highlight the new part of the code though

ok rebased to 959282f !

LGTM


No files are sent on request to sync config files

MC 1.17.1
BCLib 0.3.0
Fabric API 0.37.2
1. Install BClib 0.3.0 on the server and client
2. Try to connect to the server, it will say "Mismatching config files: Some files on the server doe not match the version on the client. Do you want to replace the local version with the ones from the server?" (and yes, the "doe" has a typo).
3. If you click "Yes", it will say that to apply the changes you need to restart the game and force restart the client, however no files are actually provided as evident in the server log:

[10:24:53] [Server thread/INFO]: John joined the game
[10:24:55] [Server thread/INFO]: [bclib] Received Hello from Client. (server=0.3.0, client=0.3.0)
[10:24:55] [Server thread/INFO]: [bclib] Sending Hello to Client. (server=0.3.0)
[10:24:55] [Server thread/INFO]: [bclib]     - Listing Mod betterend v0.11.0-pre
[10:24:55] [Server thread/INFO]: [bclib]     - Listing Mod bclib v0.3.0
[10:24:55] [Server thread/INFO]: [bclib]     - Offering File bclib.CONFIG_betterend_entities
[10:24:55] [Server thread/INFO]: [bclib]     - Offering File bclib.CONFIG_betterend_blocks
[10:24:55] [Server thread/INFO]: [bclib]     - Offering File bclib.CONFIG_betterend_items
[10:24:55] [Server thread/INFO]: [bclib]     - Offering File bclib.CONFIG_betterend_biomes
[10:24:55] [Server thread/INFO]: [bclib]     - Offering File bclib.CONFIG_betterend_generator
[10:24:55] [Server thread/INFO]: [bclib]     - Offering File bclib.CONFIG_betterend_recipes
[10:24:55] [Server thread/INFO]: [bclib]     - Offering File bclib.CONFIG_betterend_client
[10:24:55] [Server thread/INFO]: [bclib]     - Offering File bclib.CONFIG_bclib_main
[10:24:55] [Netty Epoll Server IO #8/INFO]: Received secret request of John
[10:24:55] [Server thread/INFO]: [bclib]     - Offering File bclib.CONFIG_bclib_recipes
[10:24:55] [Netty Epoll Server IO #8/INFO]: Sent secret to John
[10:24:55] [Netty Epoll Server IO #8/INFO]: Player John joined with a matching carpet client
[10:25:04] [VoiceChatPacketProcessingThread/INFO]: Successfully authenticated player John
[10:25:15] [Netty Epoll Server IO #8/INFO]: [bclib] Client requested 1 Files:
[10:25:15] [Netty Epoll Server IO #8/INFO]: [bclib]     - bclib.CONFIG_betterend_client
[10:25:15] [Server thread/INFO]: [bclib] Sending 0 Files to Client:
[10:25:18] [Server thread/INFO]: John lost connection: Disconnected

Selecting "No" lets the client join just fine, but the prompt will appear again on the next join.

Fixed in 0.3.1


Fix service alias

currently stack dns is off due to service name being overloaded.

so:

be able to attach a specific network to a stack
for each service of the stack create an alias using its short name on the stack network

Correct
On Sep 21, 2016 5:35 PM, Francois<EMAIL_ADDRESS>wrote:
so:

be able to attach a specific network to a stack
for each service of the stack create an alias using its short name on the stack network

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/appcelerator/amp/issues/229#issuecomment-248782039, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAcFqC-EBbPrxpVts7eT1QNStTyO218sks5qsc1ngaJpZM4KDaU5.

related to #239


Automate release using Github Actions

Does not pass pasword token to Action.
From: https://www.theserverside.com/blog/Coffee-Talk-Java-News-Stories-and-Opinions/GitHub-Actions-Secrets-Example-Token-Tutorial
Probably missing the mapping:
  env:
    WHO_TO_TRUST: ${{ secrets.SECRET_TOKEN }}

To test on next release.

Finally: https://github.com/dimitrismistriotis/alt-profanity-check/actions/runs/4075601491/jobs/7022208756


titan remove vertex can not work properly

Titan version: 0.5.4
action: remove vertex
action operation in gremlin:
g = TitanFacotory.open("titan-hbase-es.properties")
1, id = g.V.has("key", "xxx").iterator().next().id
2, g.v(id).remove()
3, g.commit()
4, g.v(id)
5, g.v(id).label
after the remove operation(1-3), exectue operation(4, 5),I still got the vertex and the vertex's label is "_default".
this is confused. how can I remove the vertex thoroughly. help!!!

I think the problem is existing in the titan 1.0 too.

btw, the remove vertex isRemoved() operation return false

unset storage.batch-loading with default value: false

conf = new BaseConfiguration();
conf.setProperty("storage.backend", "inmemory")
g = TitanFactory.open(conf)
mgnt = g.getManagementSystem()
mgnt.makeVertexLabel('person').make()
mgnt.makePropertyKey('key').dataType(String.class).make()
mgnt.commit()
person = g.addVertex('person')
person.setProperty('key', '123456')
g.commit()
g.V.has("key", '123456').iterator().next().id
==>256
g.v(256).remove()
==>null
g.commit()
==>null
g.v(256)
==>null

set storage.batch-loading to true

conf = new BaseConfiguration();
conf.setProperty("storage.backend", "inmemory")
conf.setProperty("storage.batch-loading", true)
g = TitanFactory.open(conf)
mgnt = g.getManagementSystem()
mgnt.makeVertexLabel('person').make()
mgnt.makePropertyKey('key').dataType(String.class).make()
mgnt.commit()
person = g.addVertex('person')
person.setProperty('key', '123456')
g.commit()
g.V.has("key", '123456').iterator().next().id
==>256
g.v(256).remove()
==>null
g.commit()
==>null
g.v(256)
==>v[256]
g.v(256).label
==>_default
g.v(256).isRemoved()
==>false

@spmallette

I'm not sure what this is exactly but definitely looks like a bug of some sort. Using cassandra on the titan11 branch:
gremlin> conf = new BaseConfiguration();
==>org.apache.commons.configuration.BaseConfiguration@4cc65c2
gremlin> conf.setProperty("storage.backend", "cassandra")
==>null
gremlin> conf.setProperty("storage.batch-loading", true)
==>null
gremlin> graph = TitanFactory.open(conf)
==>standardtitangraph[cassandra:[<IP_ADDRESS>]]
gremlin> person = graph.addVertex(label, 'person','k','123456')
==>v[4248]
gremlin> graph.tx().commit()
==>null
gremlin> g = graph.traversal();
==>graphtraversalsource[standardtitangraph[cassandra:[<IP_ADDRESS>]], standard]
gremlin> g.V().has("k", '123456').iterator().next().id()
==>4248
gremlin> g.V().has("k", '123456').drop()
gremlin> g.V().has("k", '123456')
gremlin> graph.vertices(4248)
gremlin> g.tx().commit()
==>null
gremlin> graph.vertices(4248)
==>v[4248]
gremlin> g.V().count()
==>0
gremlin> graph.vertices()

Had a quick discussion with @dkuppitz - this might not really be a "bug" but the behavior is strange. of course, with storage.batch-loading enabled you can expect strange to a certain degree as titan has to turn off a lot of "checks" to ensure loading performance. you really shouldn't use storage.batch-loading when doing graph element removal unless you really know what the consequence are of doing so and have a really good reason. This setting is intended for fast insertion of data and as a final resort for dealing with far-flung situations where you need constraints turned off when doing data manipulations. If you fit the latter then I think you just have to be aware of what the peculiarities are when using Titan this way.

In my situation, I use batch-loading to insert and delete batch data,so if I turn off batch-loading, the performance is too bad to accept. we have billions record...

If I insert a batch data in the wrong way, so I can only swap the titan table when the batch-loading is off. This does not make sense...

BTW, the issue 1334 is a more stranger problem...

Well - again - deleting data is not an expected use case for batch-loading, so i'm not completely surprised that there's some strangeness. If you are using batch-loading in this unintended way, then I could maybe see how #1334 could show itself - again, using batch-loading turns off many internal constraints in Titan, so with those checks unavailable, Titan allows you to "do bad things" to yourself.

the delete is seem to be success when I reopen the titan instance with the batch-loading off, it is strange.BTW, how I should to delete batch data? just turn off the batch-loading? or in some other more ?trikcy way?

#comment, like the comment describe, if I turn the batch-loading off, then deleting data should return nomarl ? or just turn batch-loading off, when I read data from titan.

Deletes will eventually succeed with batch-loading enabled. However, you can't trust the results from read operations. Titan won't send any read requests to Cassandra, instead it will simply return a fake vertex, assuming that you know what you're doing and the vertex actually exists. batch-loading is, as the name implies, made for loading, not for reading.
Why would Titan return a fake vertex? See:
g.v(1).addEdge("link", g.v(2))

Without batch-loading enabled this query would first execute two reads, to verify that vertex 1 and 2 actually exist. An exception would be thrown in case any of the vertices doesn't exist. Next it would send the write requests to create the edge. With batch-loading enabled on the other hand Titan assumes that you know that vertex 1 and 2 already exist and thus it will skip the read request. The fake vertices will then only hold the ids, since theyy are required for the edge write requests.
HTH

@spmallette @dkuppitz Thanks! I get it, I will test the problem in the way you suggest!

I presume that the @dkuppitz explanation has settled this issue - closing.

We got same issue in JanusGraph as well.


Get the tags for a certain asset.

Works on all API versions?

yes sir

:+1:

I've tagged it as 1.2.0 (new feature)


Bump @hpke/hybridkem-x-wing to 0.3.0.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 88.48%. Comparing base (13f1bd6) to head (1fa4c34).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #453      +/-   ##
==========================================
- Coverage   88.71%   88.48%   -0.24%
==========================================
  Files          60       60
  Lines        4716     4716
  Branches      449      448       -1
==========================================
- Hits         4184     4173      -11
- Misses        531      542      +11
  Partials        1        1

Flag
Coverage Δ

unittests
88.48% <ø> (-0.24%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Allow Preprocess and Preprocess (latent) workflows to modify the batch size or batch count.

For the Preprocess workflow, I believe it's just a matter of updating the StableDiffusionProcessingImg2Img's init function arguments in lib_comfyui.webui.patches.py

There's also p.batch_size or p.n_iter we have to update.


Test Flink Simple Transformation

Right now there is no data from output topic from Flink streaming. Because the Kafka FIle Stream Connect Source did not serialize json. It converts it to String which cannot read by Flink Json Table

Use KafkaConsumer read the Json String
Remove additional "" and " from Json String and write to another internal topic
Process using Flink SQL


"checkout scm" on ssh secured private git repo not working on alpine (jenkinsci/jnlp-slave:alpine) due to missing ssh

The ssh package (openssh?) seems to be missing in the alpine edition of the jnlp-slave (jenkinsci/jnlp-slave:alpine).
Thus I am not able to do a "checkout scm" from a private github repo secured by ssh access.
Error Message:  stderr: /tmp/ssh2342644730406476600.sh: line 6: ssh: not found
Current workaround: Use of jenkinsci/jnlp-slave instead of jenkinsci/jnlp-slave:alpine
See also: https://issues.jenkins-ci.org/browse/JENKINS-41137

Probably as designed, alpine is a minimal image for a reason. The main use-case for it is to use it as a base image and to install the stuff you need.
SSH is not required for the agent operation itself. If we want to include it, it needs more votes

I also require SSH when using this alpine-based image in order to clone git repositories. Nevertheless, I agree with @oleg-nenashev, it makes more sense to use this image as a base for all of your needs FROM jenkinsci/jnlp-slave:alpine.
Thinks of the case where someone wants to use https, or some other protocol. Should this image include curl and/or wget as well? I think not.

No response from @TGippert , so I suppose the only thing is to explain limitations/purpose of the Alpine image in the documentation

Hello Oleg, excuse for the late response.
I think, @drywheat wrote a good solution: Create an own image based on jnlp-slave:alpine.
This should work for us :-)


Add Repost Probot App to _apps

Checklist

[x] If you're adding a listing for your app, be sure your app is in the /_apps/ folder before opening this Pull Request.
[x] All comments in frontmatter need to be removed.
[x] Performs a useful action through the GitHub API that solves an existing problem for developers: Teammates can gather feedback on discussion posts via PRs and no longer have to copy/paste markdown or get feedback use Google Docs or something outside of GitHub.
[x] Is original: for example, it does something not already done by an existing Probot app
[x] Has tests - Still somewhat manual right now but I've been doing testing in this demo repo 😞
[x] Has documentation
[x] Is open source
[x] Has a license
[x] Has a code of conduct
[x] Has someone willing to at least minimally maintain them for the near future: @philip-gai

View rendered _apps/repost.md

This looks great!
Two things

Out of curiosity, what is the use case for your app? Why not ask people to just open discussions?
I would recommend you rename the app slug from https://github.com/apps/repo-st to https://github.com/apps/repost before promoting the app. It might not be permitted because there is an org with the same name: https://github.com/repost. But that org seems to be dormant for 10 years, might be worth to ask GitHub to help you get in touch with the owners of the app, maybe they are willing to remove the org

@gr2m thanks for the feedback!

Out of curiosity, what is the use case for your app? Why not ask people to just open discussions?

 At github, we have a ton of team posts that notify hundreds of people. Most author's want that team post to be proofread and reviewed before posting it, so a lot of team repos have a docs/team_posts folder where they stored the post and maybe asked for feedback. Others write the post in Google Docs, get it reviewed, then rewrite it in markdown, add gifs, emojis etc and then post. Once they got the feedback they then copy/pasted the post to actually publish it to the larger team / org.
If you use this app, you can use your small team repo to get the feedback and once you merge the PR it will post it for you to ANY repo or team that you specify and the app is authorized for. You can also use a private, internal team repo to draft things like big product announcements, get them reviewed, and merge once you're ready for it to be posted and it can create the post in your public repo. And you get the added benefit of PR checks, policies etc.

I would recommend you rename the app slug from https://github.com/apps/repo-st to https://github.com/apps/repost before promoting the app.

Yeah that makes sense. It's because I named it (repo)st so the slug became repo-st. It's supposed to be a play on repo + post that you can see visually but it's not super important. I will see if I can get the org removed, if not I might just go for repost-app or something like that

I think that's a great idea, I probably will rename it. Thanks! 😊👍🏼


Official support for python 3.9

First check

[x] I added a very descriptive title to this issue.
[x] I used the GitHub search to find a similar issue and didn't find it.
[x] I searched the FastAPI documentation, with the integrated search.
[x] I already searched in Google "How to X in FastAPI" and didn't find any information.
[x] I already read and followed all the tutorial in the docs and didn't find an answer.
[x] After submitting this, I commit to:

Read open issues with questions until I find 2 issues where I can help someone and add a comment to help there.
Or, I already hit the "watch" button in this repository to receive notifications and I commit to help at least 2 people that ask questions in the future.
Implement a Pull Request for a confirmed bug.

Description
FastAPI officially declares support for python up to version 3.8. This holds true in pyproject.toml and in declaration of tested python versions.
At the same time, FastAPI installs on python 3.9 and works without problem.
The solution you would like

Extend tests to include also python 3.9
Declare support for python 3.9 in pyproject.toml, so that on https://pypi.org/project/fastapi/ it shows support for it.

Additional context
There are also docker images for FastAPI such as tiangolo/uvicorn-gunicorn-fastapi-docker which currently declare support up to python 3.8 and not for python 3.9.
Anyway, these things can go it's own upgrade path.

I use FastAPI with python 3.9, and does so in docker. Been doing since shortly after the 3.9 release back in October.
As for my docker-image I use the tiangolo/uvicorn-gunicorn:python3.8 image in my build stages to copy over all the scripts and unicorn config. Then I set it up in a very similar fashion with some minor tweaks based on our production environment.

I guess the thing is here is to be official.

Yes I agree, should have been more clear.
My posting was meant to reassure that more users are using FastAPI with 3.9 successfully.

Any update on this ?

In package metadata at https://github.com/tiangolo/fastapi/blob/master/pyproject.toml#L31 is python 3.9 compatibility declared.
Test suite https://github.com/tiangolo/fastapi/blob/master/.github/workflows/test.yml#L13 covers python 3.9 too.
PR #2298 is merged and is awaiting next release, changelog already declares 3.9 compatibility in release notes in section "Latest changes".
Closing.


InstantiationException for Presenter

I have the two following classes (simplified):
MyActivity.java:
@RequiresPresenter(MyPresenter.class)
public class MyActivity extends NucleusAppCompatActivity<MyPresenter> {
...
}

MyPresenter.java:
public class MyPresenter extends Presenter<MyActivity> {
...
}

when launching MyActivity, I get the following RunTimeException:
Caused by: java.lang.InstantiationException:
java.lang.Class<MyPresenter> has no zero argument constructor
at java.lang.Class.newInstance(Native Method)
at nucleus.factory.ReflectionPresenterFactory.createPresenter(ReflectionPresenterFactory.java:39)
at nucleus.view.PresenterLifecycleDelegate.getPresenter(PresenterLifecycleDelegate.java:57)
at nucleus.view.PresenterLifecycleDelegate.onResume(PresenterLifecycleDelegate.java:96)
at nucleus.view.NucleusAppCompatActivity.onResume(NucleusAppCompatActivity.java:70)
at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1258)
at android.app.Activity.performResume(Activity.java:6327)
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3092)                                                                 at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3134)                                                                at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2481)                                                                at android.app.ActivityThread.-wrap11(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1344)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:148)
at android.app.ActivityThread.main(ActivityThread.java:5422)

This doesn't change even when I add the required zero argument constructor to MyPresenter (besides, I've never seen this in the examples). Is there anything I missing?
This happens for Nucleus v3.0.1 as well as v4.0.0

Hi, it looks like you do not have a default constructor in you presenter :) (It is something said by the exception)

Ups, sorry. Now I did read it till the end. Did you try to completely clean/rebuild you project?

Hi,
clean/rebuild has no effect, still getting the exception.

@null1099 Do you have proguard, or some APT tool in the build chain?
Try add this to your activity class to see what the runtime sees:
static {
	try {
		Log.d("MyPresenter", "Constructors:");
		for (Constructor<?> constructor : MyPresenter.class.getDeclaredConstructors()) {
			Log.d("MyPresenter", constructor.toString());
		}
	} catch(Throwable t) {
		Log.e("MyPresenter", "Error enumerating constructors", t);
	}
}

(it needs to be in the activity because the presenter class is not initialized until first access, which would be after a successful newInstance')
I noticed that null is using Android 23 or 24 (because newInstance became native on those platforms).
I tried an empty project with just these two classes and the only time I got the same exception is when I added a constructor with argument(s). I tried a lot of other things, like failed static initializer, visibility, abstract, but all of them gave a different error message.


feat(paymaster-mint): update example with new chains

feat(paymaster-mint): update example with new chains
add support for other chains

#198  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @jakim929 and the rest of your teammates on  Graphite


fix(@angular-devkit/schematics-cli): provide resolvePaths to NodeWorkflow

Closes #17067

Also merged to 9.0.x patch branch.


Support Swift Package Manager

Motivation
want to use Swift Package Manager
Changed

Support Swift Package

Add Package.swift

@Nirma
Please review when you have time. 🙇

@nk-5 Good work! LGTM!


Adding support to dynamically discover metrics configs across all namespaces in the cluster

It'd be great if the adapter could dynamically discover metrics configurations across all namespaces in the cluster. This would be helpful in scenarios where application developers can add Prometheus rules for HPA in their Helm chart without needing to touch the adapter configuration.
A similar ask is present in https://github.com/kubernetes-sigs/prometheus-adapter/issues/662, but I've chosen to add support using ConfigMap since the adapter already uses that instead of adding a new CRD.

/assign
/triage accepted


Exporting too many data entries appears to crash Jatos

This issue is somewhat related to #157.
I'm using Jatos 3.3.3 in combination with a MySql database for storage and NginX as a proxy. Everything works fine, but whenever I try to export worker data above a certain amount, then an error message is shown on the Jatos interface:

Exporting smaller amounts of results works perfectly. If you refresh directly after having received the bad gateway message, then you get to see the message in fullscreen (the 'classic' Bad Gateway page), and it appears to take Jatos a few seconds to recover. After recovery, you have to log in again.
My (redacted) Nginx error log shows the following entry:
2019/01/15 09:18:42 [error] 19640#19640: *117497 upstream prematurely closed connection
while reading response header from upstream,
client: ***.37.***.139,
server: jatos.*****.nl,
request: "POST /jatos/studyResult/export/resultData HTTP/1.1",
upstream: "http://<IP_ADDRESS>:9000/jatos/studyResult/export/resultData",
host: "jatos.*****.nl",
referrer: "https://jatos.*****..nl/jatos/57/results"

The jatos logs don't show anything out of the ordinary:
2019-01-15 10:21:05,822 [INFO] - c.p.Publix - .submitResultData: studyId 57, componentId 56, studyResultId 3585
2019-01-15 10:21:05,865 [INFO] - publix_access - POST /publix/57/studySessionData?srid=3585
2019-01-15 10:21:05,865 [INFO] - c.p.Publix - .setStudySessionData: studyId 57, studyResultId 3585

What could be the possible bottleneck here causes this problem?

Added streaming of result data with chunked HTTP response and on the server side only one result is loaded from the DB at the time. This reduces memory consumption and prevents crashing the JVM.
Additionally JATOS UI gives feedback while downloading the results, so users wont get confused if it takes longer.
Will be part in next release (not sure yet if it's called 3.3.7 or 3.4).

Great work! Thanks very much
On Sat, Jul 27, 2019, 19:45 Kristian Lange<EMAIL_ADDRESS>wrote:

Closed #159 https://github.com/JATOS/JATOS/issues/159.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/JATOS/JATOS/issues/159?email_source=notifications&email_token=AAFIHFCGK3QWG33QNSOIBM3QBSCSHA5CNFSM4GQCGUD2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOSXO6CMQ#event-2514346290,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFIHFGAEC5EOVIPYDM22WTQBSCSHANCNFSM4GQCGUDQ
.


API Docs - Disable online swagger validator

Issue type
[X] Feature request
[ ] Bug report
[ ] Documentation

Environment

Python version:  3.6.5
NetBox version:  2.3.3

Description
Hello,
Our instance of netbox is restricted to our internal network only, the problem is that when someone go to the API doc view (/api/docs/), the online swagger validator is triggered, and it delays the whole display of API endpoints to finally display a nice "error badge".
I don't get the point of this online validator on production environnement ...
Thank you

It seems there is no way to customize Swagger settings, since you enforce configuration
https://github.com/digitalocean/netbox/blob/develop/netbox/netbox/settings.py#L250

I have the same issue, it would be nice if we could override the online validator setting from the main config file.

What is the exact change being proposed? How would you modify the configuration?

@jeremystretch well according to https://github.com/swagger-api/swagger-ui/blob/master/docs/usage/configuration.md you can pass the following to Swagger-UI:

validatorUrl
String="https://online.swagger.io/validator" OR null.  By default, Swagger-UI attempts to validate specs against swagger.io's  online validator. You can use this parameter to set a different  validator URL, for example for locally deployed validators (Validator Badge). Setting it to null will disable validation.

Not sure on how to implement that into Netbox. Perhaps if we can set that from configuration.py as an exported variable or something?

So this was an issue for me too, but you can set the validatorUrl via SWAGGER_SETTINGS in settings.py, here's what mine looks like:
SWAGGER_SETTINGS = {
    'DEFAULT_FIELD_INSPECTORS': [
        'utilities.custom_inspectors.NullableBooleanFieldInspector',
        'utilities.custom_inspectors.CustomChoiceFieldInspector',
        'drf_yasg.inspectors.CamelCaseJSONFilter',
        'drf_yasg.inspectors.ReferencingSerializerInspector',
        'drf_yasg.inspectors.RelatedFieldInspector',
        'drf_yasg.inspectors.ChoiceFieldInspector',
        'drf_yasg.inspectors.FileFieldInspector',
        'drf_yasg.inspectors.DictFieldInspector',
        'drf_yasg.inspectors.SimpleFieldInspector',
        'drf_yasg.inspectors.StringDefaultFieldInspector',
    ],
    'DEFAULT_FILTER_INSPECTORS': [
        'utilities.custom_inspectors.IdInFilterInspector',
        'drf_yasg.inspectors.CoreAPICompatInspector',
    ],
    'DEFAULT_PAGINATOR_INSPECTORS': [
        'utilities.custom_inspectors.NullablePaginatorInspector',
        'drf_yasg.inspectors.DjangoRestResponsePagination',
        'drf_yasg.inspectors.CoreAPICompatInspector',
    ],
    'VALIDATOR_URL': None
}

which sets the UI's validatorUrl to Null. Here's what the swagger-settings json object looks like when I view the page source:
<script id="swagger-settings" type="application/json">{"docExpansion": "list", "deepLinking": false, "showExtensions": true, "defaultModelRendering": "model", "defaultModelExpandDepth": 3, "defaultModelsExpandDepth": 3, "showCommonExtensions": true, "supportedSubmitMethods": ["get", "put", "post", "delete", "options", "head", "patch", "trace"], "validatorUrl": null}</script>

Fixed in ef61c70a9dc36969678691afed6b9dbedb33963c


Update sample to use boto3

@kyleknap Can you take a look when you get a chance?

Looks good. Had a small comment. :ship:


Plug.dj no longer scrobbles.

Plug.dj recently got a design update, not sure if this has anything to do with it, but it no longer recognises a song playing.

This issue can be closed (see #985).

thanks!


[ETHOSN] Update compilation defaults to Ethos(TM)-N78

@leandron if you have time

@Mousius @leandron if you have a chance.

Thanks! @Leo-arm @Mousius.


async check_callback function can not prevent operation

async check_callback(...){
     return false;
}

check_callback can not prevent any operation if add "async"

Yes, the places which rely on this function do not work with promises - they need the return value of the function.


Creating "Releases"

In my dreams a "Release" is a light-weight git tag that a data consumer can directly clone and have exactly the files present that they can use for their analysis.
There are a couple reasons for this. First, the whole set of output files makes git/datalad very slow. They still work, but it is unpleasant waiting for their operations to complete. Second, it makes writing papers easier and is a guardrail against p-hacking.
The role of drip this process is to create a branch that corresponds to the nature of the release, delete the outputs that don't meet the thresholds, update the group tabular data and push the branch to github.

We don't need branches!! This can all be done with tsvs and copy/pastable code

Create a superdataset that installs all the modality results subdatasets that they might want. Then based on a projectwise tsv that can be used to to delete incomplete/unusable subjects/sessions/modalities from the subdatasets. THEN save all of the datasets and now you have your own version that you can put on github
Maybe even a template repo for rbc-based projects!!


Make github.com/umputun/reproxy/lib a submodule

Import of github.com/umputun/reproxy/lib adds github.com/umputun/reproxy to go.mod. It results in a significant number of dependencies.
At the same time, github.com/umputun/reproxy/lib requires only 3 dependencies:

github.com/go-pkgz/lgr
github.com/go-pkgz/repeater
github.com/stretchr/testify

Making github.com/umputun/reproxy/lib a submodule can resolve this issue.
However, this change will also require some additional work:

manage 2 versions: vX.Y.Z for github.com/umputun/reproxy and lib/vX.Y.Z for github.com/umputun/reproxy/lib
github.com/umputun/reproxy/lib will have to be vendored (see https://github.com/golang/go/issues/33789 and https://github.com/hashicorp/nomad/pull/10898)
users of github.com/umputun/reproxy/lib will have to update dependency path and version

I don't think these points are very critical: API of github.com/umputun/reproxy/lib is pretty stable, and the current version (v0.10.0) allows to make breaking changes

this is a valid concern. Making submodule in go is smth awkward a little bit with an additional tag we will have to maintain for lib.  However, breaking dependency to the github.com/umputun/reproxy is worth it in my opinion. We
I'm not sure I understand the meaning of  "will have to be vendored" item. Does it mean vendored by reproxy itself because it will be treated as a module and won't be resolvable "directly" anymore? Are you saying this won't work anymore unless vendored?

Does it mean vendored by reproxy itself because it will be treated as a module and won't be resolvable "directly" anymore? Are you saying this won't work anymore unless vendored?

Yes, you are right.
From https://github.com/golang/go/issues/33789:

At the moment, this is working as designed: go mod vendor doesn't know (or particularly care) about the overall repo structure — it just knows where the main module is and vendors in the dependencies of the main module wherever they are found.

Some workarounds:

use a symlink for a local module like github.com/gravitational/teleport - https://github.com/gravitational/teleport/blob/master/Makefile#L923
add a helper script to vendor a local module like github.com/hashicorp/nomad (they don't vendor deps anymore) - https://github.com/hashicorp/nomad/pull/10898

But as I said, github.com/umputun/reproxy/lib should be pretty stable. So, I don't think it will be a big problem


Implement youki spec --rootless

As the title says. The flag should generate an OCI spec used for rootless container. At minimum, the command should generate user namespace and uid/gid mapping. Comparable to runc spec --rootless.

Removed nix from PR : https://github.com/containers/oci-spec-rs/pull/49

Fixed


k2pdfopt: pin tesseract version

This pins the tesseract version of k2pdfopt to  the one expected upstream. Due to the unusual setup of k2pdf it is uncompatible with any updated version. So unless upstream reworks their patches this is the best we can do.
Should then still work when #353902 is merged.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 357698

x86_64-linux

:white_check_mark: 1 package built:

k2pdfopt

aarch64-linux

:white_check_mark: 1 package built:

k2pdfopt