[Container Apps] Remove AspireResourceServerApi type for DotNetCompon…

…ent - 2023-11-02-preview
ARM (Control Plane) API Specification Update Pull Request

[!TIP]
Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

[!NOTE]
As of January 2024 there is no PR assignee. This is expected. See https://aka.ms/azsdk/pr-arm-review.

PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

 Click here to see the details of Step 1
Breaking changes review (Diagram Step 1)
If the automation determines you have breaking changes, i.e. Step 1 from the diagram applies to you,
you must follow the breaking changes process.
IMPORTANT This applies even if:

The tool fails while it shouldn't, e.g. due to runtime exception, or incorrect detection of breaking changes.
You believe there is no need for you to request breaking change approval, for any reason.
Such claims must be reviewed, and the process is the same.

 Click here to see the details of Step 2
ARM API changes review (Diagram Step 2)

For help with Step 2 / "ARM review", see https://aka.ms/azsdk/pr-arm-review.

 Click here to see the diagram footnotes
Diagram footnotes
[1] See ARM review queue (for PR merge queues, see [2]).
[2] public repo merge queue, private repo merge queue (for ARM review queue, [1])
The ARM reviewer on-call engineer visits the merge queue twice a day, so the approximate ETA for merges is 12 - 24 hours.

Purpose of this PR
What's the purpose of this PR? Check the specific option that applies. This is mandatory!

[ ] New resource provider.
[ ] New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been generated using OpenAPI Hub).
[ ] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix OpenAPI spec quality issues in S360.
[x] Other, please clarify:

Update existing version for an existing feature to remove an enum type we don't need anymore and that was never used.

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[x] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[x] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.

Additional information

 Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.

Getting help

First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
For help with PR workflow diagram Step 2 (ARM review), see https://aka.ms/azsdk/pr-arm-review.
If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

Created this breaking change review request item: https://msazure.visualstudio.com/One/_workitems/edit/27071821

@mushmal, @bexxx, Could you please remove the ARMChangesRequested label? For some reasons I cannot remove it myself from the PR.

@MushMal, @bexxx, Could you please remove the ARMChangesRequested label? For some reasons I cannot remove it myself from the PR.

@MushMal, @bexxx > Sorry for the early ping but I want to make sure I don't forget about this. Could you please remove the ARMChangesRequested label from this PR? I don't seem to have the permissions to do this myself.

@MushMal, @bexxx, Could you please remove the ARMChangesRequested label? For some reasons I cannot remove it myself from the PR.

@MushMal, @bexxx > Sorry for the early ping but I want to make sure I don't forget about this. Could you please remove the ARMChangesRequested label from this PR? I don't seem to have the permissions to do this myself.

@MushMal, @bexxx > Could you please try to remove the ARMChangesRequested label? I'm not able to do it myself and need it to be removed so that this PR can be merged.

@daniv-msft
Your PR should now be pending ARM review:

https://aka.ms/azsdk/pr-arm-review


Node.js 8.xx update deprecation clarification

I believe it's possible to at least update a node.js 8.xx RUNTIME past it's update deprecation date.
So customers won't need to re-create a new lambda, just simply go in and update the runtime.

Yes. You can update a function with a deprecated runtime as long as you change the runtime to one that's supported. You just won't be able to change it back later.


Update index.json

I was checking links and released the link to the  polar coordinates video was broken.

Good catch thank you!


Can't pass arguments to the underlying command when using --filter

What version of Turborepo are you using?
1.2.16
What package manager are you using / does the bug impact?
npm
What operating system are you using?
Mac
Describe the Bug
Can't pass arguments (that start with - or --) to the underlying command that turbo will run, when using --filter.
Expected Behavior
Running:
npm run test -- --filter=ui -- --passWithNoTests

Expected turbo to run:
npm run test -- --passWithNoTests

Only for ui package.
In reality, turbo runs:
npm run test

Only for ui package.
👉 Created a repo to reproduce.
To Reproduce
Run a command with --filter and pass more options. Check Expected behavior and the repo I've created to easily reproduce the issue.

I'm facing the same issue, here the context:
I installed the lib globally:  "dotenv-flow": "3.2.0"
And added a script in the package.json (root):
Script:
"build:app": "dotenv -e .env turbo run build --filter=@crow/app"

Run:
yarn build:app

It's ignore the filter and do a build in entire project (packages. apps)

Why is it marked as ready? The issue cannot be solved without dotenv?

Hey no solution for this yet?

Hey no solution for this yet?

I believe with https://github.com/vercel/turbo/pull/1405 you're able to pass args via npm run test -- -- --someArg --someOtherArg=123

add -- to last of the scripts here https://github.com/ivolimasilva/turborepo-args-bug/blob/main/package.json#L10-L14
like:
 "scripts": {
    "build": "turbo run build --",
    "dev": "turbo run dev --parallel --",
    "lint": "turbo run lint --",
    "test": "turbo run test --",
    "format": "prettier --write \"**/*.{ts,tsx,md}\""
  },

add -- to last of the scripts here<EMAIL_ADDRESS>like:
 "scripts": {
    "build": "turbo run build --",
    "dev": "turbo run dev --parallel --",
    "lint": "turbo run lint --",
    "test": "turbo run test --",
    "format": "prettier --write \"**/*.{ts,tsx,md}\""
  },

Thanks, this solution works perfectly!


Color Updates

base neutrals were updated with a new ZH link
some semantic colors are also updated

Nice - custom zeroheight link for new theme? 🎉

Yup! For the base-neutrals @chudo76 gave me a  new link. However, it looks as if some of the semantic colors were updated in the original link as well?


Bei zwei von drei Zähler keine aktuellen Daten

Hallo,
zuerst ein großes Kompliment für den Adapter!
Ich habe dabei aber ein Problem.  Die Basisdaten werden zu allen drei Zählern angezeigt.
Allerdinge werden in den den Objekten nur die aktuellen Werte eines Zählers geschrieben.
Was viellecht noch hilft.
Wo könnte der Fehler liegen?
First a big compliment for the adapter!
I have a problem with that. There are three power-meter built in, all of which are recognized by the adapter. The basic data is displayed for all three power-meter.
However, in the objects only the current values of a power-meter are written.
What else helps. The counters which have no current display are bidirectional power-meter, the one displayed is a device counter.
Where could the mistake lie?

Hi @gbdeining, thank your for this great feedback and initiating an issue.
(yea some people think issue are bad but issue give me input to improve so i am very happy with that !)
I will keep it in English for track & trace and enable all consumers to read and understand this issue.
Ok lets have a look at your issue, the adapter handles the logic as following :

connect to the API of discovvergy
get a list of all meters and theyr basic information (as you state that happens)
make a call for each meter and get the data of it.

As you mention only the power states are shown, some additional questions :

Are you aware of the short and long pulling intervall ? (power = short, all others = long ?
the basic setting is short 3seconds and long 1 minute (you can specify this in adapter setting
Did you wait long enough (long intervall) to ensure other states then power are retrieved ?
Do you have any errors in the log mentioning maybe unsupported objects ?

Last but not least, please go to the console and run this command :
cd /opt/iobroker
sudo iobroker update | grep Discovergy
Please post the outcome here, i would like to see which version is running at you system.
Thank you !

I have install IOBROKER on a Windows - PC. I hope it help the install LOG:
2018-12-17 15:19:40.021  - info: iobroker url "https://github.com/DutchmanNL/ioBroker.discovergy.git" --debug
2018-12-17 15:19:40.891  - info: iobroker install https://github.com/DutchmanNL/ioBroker.discovergy/tarball/master
2018-12-17 15:19:42.635  - info: iobroker npm install https://github.com/DutchmanNL/ioBroker.discovergy/tarball/master --production --save --prefix "D:/ioBroker" (System call)
2018-12-17 15:19:49.429  - info: iobroker +<EMAIL_ADDRESS>1 package in 3.782s
2018-12-17 15:19:49.470  - info: iobroker exit 0
2018-12-17 15:19:49.540  - info: host.Server-PC Update repository "default" under "http://download.iobroker.net/sources-dist.json"
2018-12-17 15:20:00.480  - info: host.Server-PC instance system.adapter.tankerkoenig.0 started with pid 13268
2018-12-17 15:20:01.853  - info: tankerkoenig.0 starting. Version 1.0.4 in D:/ioBroker/node_modules/iobroker.tankerkoenig, node: v10.14.2
2018-12-17 15:20:01.982  - info: tankerkoenig.0 objects written
2018-12-17 15:20:02.390  - info: host.Server-PC instance system.adapter.tankerkoenig.0 terminated with code 0 (OK)
2018-12-17 15:20:25.619  - info: host.Server-PC Update repository "default" under "http://download.iobroker.net/sources-dist.json"
2018-12-17 15:20:59.895  - info: iobroker add discovergy  --host Server-PC
2018-12-17 15:21:00.930  - info: iobroker host.Server-PC install adapter discovergy
2018-12-17 15:21:00.941  - info: iobroker got D:/ioBroker/node_modules/iobroker.discovergy/admin
2018-12-17 15:21:00.968  - info: iobroker upload [6] discovergy.admin D:/ioBroker/node_modules/iobroker.discovergy/admin/words.js words.js application/javascript
2018-12-17 15:21:01.039  - info: iobroker upload [5] discovergy.admin D:/ioBroker/node_modules/iobroker.discovergy/admin/tsconfig.json tsconfig.json application/json
2018-12-17 15:21:01.099  - info: iobroker upload [4] discovergy.admin D:/ioBroker/node_modules/iobroker.discovergy/admin/style.css style.css text/css
2018-12-17 15:21:01.163  - info: iobroker upload [3] discovergy.admin D:/ioBroker/node_modules/iobroker.discovergy/admin/index_m.html index_m.html text/html
2018-12-17 15:21:01.233  - info: iobroker upload [2] discovergy.admin D:/ioBroker/node_modules/iobroker.discovergy/admin/Discovergy_logo.png Discovergy_logo.png image/png
2018-12-17 15:21:01.305  - info: iobroker upload [1] discovergy.admin D:/ioBroker/node_modules/iobroker.discovergy/admin/discovergy.png discovergy.png image/png
2018-12-17 15:21:01.361  - info: iobroker upload [0] discovergy.admin D:/ioBroker/node_modules/iobroker.discovergy/admin/admin.d.ts admin.d.ts video/mp2t
2018-12-17 15:21:01.470  - info: iobroker host.Server-PC object system.adapter.discovergy created
2018-12-17 15:21:01.489  - info: iobroker host.Server-PC create instance discovergy
2018-12-17 15:21:01.494  - info: iobroker host.Server-PC object discovergy.0.info.connection created
2018-12-17 15:21:01.524  - info: iobroker host.Server-PC object system.adapter.discovergy.0.outputCount created
2018-12-17 15:21:01.552  - info: iobroker host.Server-PC object system.adapter.discovergy.0.inputCount created
2018-12-17 15:21:01.581  - info: iobroker host.Server-PC object system.adapter.discovergy.0.uptime created
2018-12-17 15:21:01.610  - info: iobroker host.Server-PC object system.adapter.discovergy.0.memRss created
2018-12-17 15:21:01.637  - info: iobroker host.Server-PC object system.adapter.discovergy.0.memHeapTotal created
2018-12-17 15:21:01.668  - info: iobroker host.Server-PC object system.adapter.discovergy.0.memHeapUsed created
2018-12-17 15:21:01.696  - info: iobroker host.Server-PC object system.adapter.discovergy.0.connected created
2018-12-17 15:21:01.726  - info: iobroker host.Server-PC object system.adapter.discovergy.0.alive created
2018-12-17 15:21:01.756  - info: host.Server-PC object change system.adapter.discovergy.0
2018-12-17 15:21:02.048  - info: host.Server-PC instance system.adapter.discovergy.0 started with pid 11104
2018-12-17 15:21:02.049  - info: iobroker host.Server-PC object system.adapter.discovergy.0 created
2018-12-17 15:21:02.084  - info: iobroker exit 0
2018-12-17 15:21:03.507  - warn: host.Server-PC instance "system.adapter.discovergy.0" disabled
2018-12-17 15:21:03.496  - info: discovergy.0 starting. Version 0.3.1 in D:/ioBroker/node_modules/iobroker.discovergy, node: v10.14.2
2018-12-17 15:21:03.508  - info: host.Server-PC object change system.adapter.discovergy.0
2018-12-17 15:21:03.508  - info: host.Server-PC "system.adapter.discovergy.0" disabled
2018-12-17 15:21:03.508  - info: host.Server-PC stopInstance system.adapter.discovergy.0
2018-12-17 15:21:03.508  - info: host.Server-PC stopInstance system.adapter.discovergy.0 killing pid 11104
2018-12-17 15:21:03.544  - warn: host.Server-PC instance system.adapter.discovergy.0 terminated due to SIGTERM
2018-12-17 15:21:03.544  - info: host.Server-PC instance system.adapter.discovergy.0 terminated with code null ()
2018-12-17 15:21:42.387  - info: host.Server-PC object change system.adapter.discovergy.0
2018-12-17 15:21:48.562  - info: host.Server-PC object change system.adapter.discovergy.0
2018-12-17 15:21:48.562  - info: host.Server-PC "system.adapter.discovergy.0" enabled
2018-12-17 15:21:48.794  - info: host.Server-PC instance system.adapter.discovergy.0 started with pid 11520
2018-12-17 15:21:49.610  - info: discovergy.0 starting. Version 0.3.1 in D:/ioBroker/node_modules/iobroker.discovergy, node: v10.14.2
2018-12-17 15:21:49.983  - error: discovergy.0 Connection_Failed

Please send me a short contact mail at guido[at]boehm.computer
I will give you furter Information

.com OR de :-)

Installation log looks good, version 0.3.1
Are there no additional logging messages when you start the adapter?

clear, good to know the issue is solved for you :-)
yeah if discovergy API has no data there is nothing the adapter can retrieve.
So have fun with it and if you have any suggetionns please feel free to submit a new issue we are not on version 1 yet :)


Fix/review readers

Use Enum class to set the different reader options for the review stage.
Default readers of a review are: Program Chairs and signature of the review. 'Reviewers submitted' is not the default option anymore.
Do not show the review content in the email notification because they may no have title or review anymore, like ECCV. This is also good, because we can support Markdown and no need to worry about the email content rendering.
Request form support more options in the Review Stage invitation: https://github.com/openreview/openreview-scripts/pull/1175
Fix tests.

@mohituniyal should be ready to review.


[FLINK-9292] [core] Remove TypeInfoParser (part 2)

What is the purpose of the change
This pull request removed class TypeInfoParser and refactored specific test case
Brief change log

Removed class TypeInfoParser
Refactor code where use TypeInfoParser
Refactor test code where use TypeInfoParser

Verifying this change
This change is already covered by existing tests*.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

hi @StephanEwen this issues part 2, please review it

cc @StephanEwen fixed a incompatibility error

cc @StephanEwen refactored based on your suggestion, the travis build failed because of yarn test,  seems not about this PR's change.

cc @StephanEwen

One minor style comment, otherwise this is good to go!

cc @StephanEwen refactored base on your suggestion.

Looks good, thanks.
+1 to merge

cc @tillrohrmann this can be merged thanks!

cc @tzulitai

@yanghua The PR has been merged, could you close it?

@zentol OK, closing after merged~


Translated new strings to Dutch

Translated the following new keys to Dutch:

Contacts.Bot
Settings.AutosaveScreenshotPath
Settings.Audio.NoiseSupression
Inspector.Audio.DenoiseRNNoise

Updated the following keys to match source strings:

Indicator.OnlineUsers
Importer.Folder.Batch.Description

Thank you for the update!

Thank you for the update!


fix: wc params for argent mobile

Issue / feature description
Quick description of the issue or the feature that is implemented in the pr ie: add new transitions between screens
Changes
quick list regarding the related changes within the pr
ie:

add new connector
fix injected connector
...

Checklist

[ ] Rebased to the last commit of the target branch (or merged)
[ ] Code self-reviewed
[ ] Code self-tested
[ ] Tests updated (if needed)
[ ] All tests are passing locally

Please keep your pull request as small as possible. If you need to make multiple changes, please create separate pull requests for each change. Create a draft pull request if you need early feedback. This will mark the pull request as a work in progress and prevent it from being reviewed or merged until you are ready.
Please move drafts to the ready for review (regular PR) when you are ready to start the review process and other developers will pick it up from there.

@mluisbrown part of the related ticket in jira:
The link under QR could shown follow this schema https://www.argent.xyz/app/wc?uri=${encodedWcUri}&href=${href}&device=mobile

and this encoding was required by android team


Uncomment impl IntoResponse for Result<T: IntoResponse, U: IntoResponse>

Was commented-out in 3aea1d9baba1a13b by @yoshuawuyts.
Not sure shy it was commented out. Maybe a different approach was to be pursued?
My motivation to uncomment was that I want my endpoint handler to have Result<T, E> return type, so that I can use ? operator directly in it. I was not able to implement this in my crate due to Rust orphan rules.
If this is a desired change, I can add tests. If not, I'd be glad for any advice how to achieve the goal differently.

Ah, silly me, this is a duplicate of #382. Closing, should have checked open issues/prs first.


Feat/Hard-deprecation of System seed and metrics custom resource fields

Hard-deprecation of System seed CR fields
Hard-deprecation of System metrics CR fields

Intermediate v0.10.8-alpha1 alpha release has been successfully tested on dev environment. I have just seen the following error, which might be related to https://github.com/3scale-ops/saas-operator/pull/122 , but I think it is normal to see those reconcile errors on services, @roivaz can you confirm?
2021-09-20T17:40:01.172Z	ERROR	util.api	unable to update object	{"object": {"apiVersion":"v1","kind":"Service","metadata":{"creationTimestamp":null,"labels":{"app":"3scale-api-management","threescale_component":"backend","threescale_component_element":"listener"},"name":"backend-listener-internal","namespace":"3scale-saas","ownerReferences":[{"apiVersion":"saas.3scale.net/v1alpha1","blockOwnerDeletion":true,"controller":true,"kind":"Backend","name":"dev-eng-backend","uid":"e4fa6ca1-1933-49f4-b7e7-7dde0524a3eb"}],"resourceVersion":"681585"},"spec":{"ports":[{"name":"http","port":80,"protocol":"TCP","targetPort":"http"}],"selector":{"deployment":"backend-listener"},"sessionAffinity":"None","type":"ClusterIP"},"status":{"loadBalancer":{}}}, "error": "Service \"backend-listener-internal\" is invalid: [spec.clusterIPs[0]: Invalid value: []string(nil): primary clusterIP can not be unset, spec.ipFamilies[0]: Invalid value: []core.IPFamily(nil): primary ipFamily can not be unset]"}

2021-09-20T17:40:01.172Z	ERROR	resource-reconciler.3scale-saas/dev-eng-backend.v1/Service/3scale-saas/backend-listener-internal	unable to create or update	{"resource": {"Object":{"apiVersion":"v1","kind":"Service","metadata":{"creationTimestamp":null,"labels":{"app":"3scale-api-management","threescale_component":"backend","threescale_component_element":"listener"},"name":"backend-listener-internal","namespace":"3scale-saas","ownerReferences":[{"apiVersion":"saas.3scale.net/v1alpha1","blockOwnerDeletion":true,"controller":true,"kind":"Backend","name":"dev-eng-backend","uid":"e4fa6ca1-1933-49f4-b7e7-7dde0524a3eb"}]},"spec":{"ports":[{"name":"http","port":80,"protocol":"TCP","targetPort":"http"}],"selector":{"deployment":"backend-listener"},"sessionAffinity":"None","type":"ClusterIP"},"status":{"loadBalancer":{}}}}, "error": "Service \"backend-listener-internal\" is invalid: [spec.clusterIPs[0]: Invalid value: []string(nil): primary clusterIP can not be unset, spec.ipFamilies[0]: Invalid value: []core.IPFamil...

/kind feature
/priority important-soon
/assign

Confirmed by @roivaz that the error shown in PR description is expected:

The service reconciler controller on the first execution tries to create something that it is already created (service), failing
On next reconcile loop the operator will do a patch instead, and success
I have done an small test to prove it works: to add manually a port into a service managed by the operator, and the operator reconciles the service immediately removing successfully the new manual added port

/approve


resource/cloudflare_tunnel_config: fix duration handling

Due to marshal/unmarshal support lacking for time.Duration in Go 1, we were previously sending nanosecond values to the API instead of the required seconds. This would have resulted in higher than usual timeout durations (10 seconds would have been sent as<PHONE_NUMBER> seconds since it duration unmarshals to nanoseconds).
Updates all the instances of time duration handling in cloudflare_tunnel_config resource to use the newly introduced TunnelDuration to ensure we correctly setting the units.
Depends on cloudflare/cloudflare-go#1303
Closes #2495

acceptance tests all passing
TF_ACC=1 go test ./internal/sdkv2provider -v -run "^TestAccCloudflareTunnelConfig_" -count 1 -timeout 120m -parallel 1
=== RUN   TestAccCloudflareTunnelConfig_Full
--- PASS: TestAccCloudflareTunnelConfig_Full (25.28s)
=== RUN   TestAccCloudflareTunnelConfig_Short
--- PASS: TestAccCloudflareTunnelConfig_Short (23.35s)
PASS
ok  	github.com/cloudflare/terraform-provider-cloudflare/internal/sdkv2provider	49.789s

HTTP payloads have also been manually verified as sending the seconds value.

cc @obezuk

Any update on this?

functional changes merged into #2541 to get CI green for version bumping


remove a non-haiku

Since the first line wasn't a haiku, (wrong amount of syllables).

Caaaaaaan we make it into a haiku? 🙀

Maybe "This is cat, hello./Where is everybody/I'm getting hungry"?

Yep, converting it to a haiku is a better option.

Sorry, terrible at mobile code

Heh no worries. Thanks!


Protontricks for Re:ZERO -Starting Life in Another World- The Prophecy of the Throne [ID: 1277510]

This is mostly just a scuffed pull request because I don't know how to do that, sorry. the tl;dr is that Re Zero: The Prophecy of the Throne crashes on startup, and adding d3dcompiler_47 in protontricks seems to fix this.
Describe the bug
Re Zero: The Prophecy of the Throne crashes on startup.
To Reproduce
Click and run the game on steam without adding d3dcompiler_47 using protontricks.
Expected behavior
Game starts up, and plays.
Logs
My apologies, but I don't have access to my linux laptop right now to really give you this.
Operating System:

Distro and Version: Tested on SteamOS 3.4
Proton Version: 8.0-2

Game (if applicable):

Game Name: Re:ZERO -Starting Life in Another World- The Prophecy of the Throne
Game ID: 1277510

Additional Information
I have mostly only played the beginning parts of the game, but nothing seems to be broken based on what I have played, I just want to submit that d3dcompiler_47 makes the game run.

Made one for you, dunno if it works as I don't own the game, but it's there. #5

Thank you!


ImportError: No module named 'gym_remote'

Hi,
Could somebody help me with the error:
import gym_remote.client as grc
ImportError: No module named 'gym_remote'
Where can I get 'gym_remote'?
Thank you.

pip install gym-remote


rename to couchdb-calculate-session-id?

I feel like the name might be a bit confusing. "generate" might imply that we randomly generate a session id, but in fact the result is always the same based on the input.
I think calling it couchdb-calculate-session-id would make that more clear.

This is how a couchdb-validate-session-id method could look like :v:
module.exports = validateSessionId

var calculateSessionId = require('couchdb-calculate-session-id')
var base64url = require("base64url")

function validateSessionId(sessionId, serverSecret, findUserDoc) {
  parts = base64url.decode(sessionId).split(':')
  var username = parts[0]
  var timestamp = parseInt(parts[1], 16)
  if (timestamp * 1000 < Date.now()) {
    return Promise.reject(new Error('expired'))
  }

  return findUserDoc(username)
  .then(function(doc) {
    if (sessionId === calculateSessionId(username, doc.salt, secret, timestamp)) {
      // session is valid
    } else {
      throw new Error('invalid')
    }
  })
}

How about just couchdb-session-id with methods: validate || verify, generate || new ? Short, clear and simple.

small npm modules are the best, I'd make two separate ones :) sorry for putting the distraction with putting couchdb-validate-session-id in this thread, I had to put this somewhere so I don’t forget :) Was late yesterday
Shall we rename couchdb-generate-session-id to couchdb-calculate-session-id or not?

from Hoodie Chat

renamed it: https://www.npmjs.com/package/couchdb-calculate-session-id


Should sjb/hack/determine_install_upgrade_version.py ever return an upgrade version that is not the search version?

@jhadvig one of the side-effects of the issues today was that I noticed that sjb/hack/determine_install_upgrade_version.py is returning something other than the input package version for the upgrade target. When does this make sense? I thought we always want to upgrade to the code we just built, right? Maybe I am forgetting something in the history of this script :\

@stevekuznetsov so the only case that this could occure is that we are building a pre-release upgrade version of the built pkg, cause in that case we are using the latest release version that is available, check https://github.com/openshift/aos-cd-jobs/blob/master/sjb/hack/determine_install_upgrade_version.py#L31-L34
True that we want to upgrade to the version that we just built, but I have a strange feeling that we are missing some other edge case.

So I think its because of the *_TARGE_BRANCH variables,. If the origin PR is eg. against release-1.5, are we chcking our the matching branch of o-a repo ?

I don't think we are.


Parse music and sound should show update

Parsing music and sound files in the load service should count as a step in the percentage. Right now the parsers are immediately executed like the system parser.

Not going to fix.


PYIC-5820: add language toggle

Proposed changes

Add language toggle

What changed

Added language toggle for welsh and english translation

Why did it change

To allow user to switch language options.

Issue tracking

PYIC-5820

Also, does this fix date string not updating with language, or has that already been fixed?


[Event Request] Report 99000754 Rolled-up Cost Shares - trigger OnPreReport  - OnBeforeOnPreReport

Describe the request
Please add the following Event/-s OnBeforeOnPreReport to trigger OnPreReport in Report 99000754 Rolled-up Cost Shares.
[Event Request] Report 99000754 Rolled-up Cost Shares - trigger OnPreReport
trigger OnPreReport() // <-- NEW TRIGGER
begin

    OnBeforeOnPreReport(Item); // <-- NEW EVENT

    CalculateDate := WorkDate();
end;

[IntegrationEvent(false, false)]
local procedure OnBeforeOnPreReport(Item: Record Item)
begin
end;

Additional context
We need a possibility to stop executing the report before processing
Internal work item: AB#542267

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 22007.


Often, the title of a page is the URL

Often, document.body.title is not available, so the url is taken instead of a title field in the search result elements.

However for the same pages, if i use document.title everything works fine and it gives me the correct title.
I assume that changing the request to document.title (or asking for both and take the longer one) could solve the issue.

Its actually weird, I just tested it with a page that worked for @urbancvek, and it does not for me:
Urbans version:

my version:

Every page that I visit now/yesterday/this week shows url where the title should be. If I filter the page to only show those before 05-06-2017 it shows the title. So maybe is something in how the data is stored.

Maybe it has something to do with a recent update you made @poltak?
Seems like if that the data is not stored correctly anymore:

Title is first attempted to be taken from extractedMetadata.title (extractedMetadata extracted from the tab in the analysis stage), but will fallback to  url in the case where nothing else is available (in that screenshot from @oliversauter's last comment, the page doc does not contain extractedMetadata, hence it makes sense that title is set to the URL).
This code in src/page-analysis/index.js does the current setting of title field, being called right at the end of the analysis stage once all extra data has been attempted to be fetched for a given page. This hasn't changed for quite a while though.
Another thing is that the title should be available on the title field of a page doc, not body.title (there is no body field in the current model that I can see). It should be rendered in the view in on this line in VisitAsListItem component (note that doc is a visit doc and doc.page has been filled out with the corresponding page doc in this context, hence it is accessing a page doc's title field). But I assume this is just a minor mistake/misunderstanding in the OP.
The screenshots given in this thread are from a development branch, but looking at the code on @urbancvek's PR, the VisitAsListItem code has not changed; still accessing title field on the page doc, so in this case shouldn't be too important, but for safety sake in the future just use master for testing these things.
Looking into my data of ~2700 page docs on my web browsing browser, everything looks fine for the last 3-4 days, however a lot of the earlier data is missing extractedMetadata, hence title is set to URL. So rather than the bug being incorrect title, the bug seems to be that a few days back extractedMetadata stopped being extracted properly. However, looking at @oliversauter's screenshot in the last post, that visitStart time is from today. From this, it makes sense to me that this troublesome visit + page data has been gotten from the imports process (as you said you ran it yesterday, and I haven't run it on my main web browsing browser for maybe 3 days), hence not really an issue, but @urbancvek did say specifically in the above comment that it's doing this for him on page visits (and that wired.com comment), which I cannot reproduce.
Can you guys try this on master, visit some pages, wait a bit, see if they show up in overview with title as page title or URL and whether or not they have extra data like screenshot, and send me a list of any of the problem URLs so I can see if I can reproduce this at all? Another thing is to open up the background script's console (https://stackoverflow.com/a/10258029) and see if any errors are showing up there.
tl;dr bug seems to be in getting the extractedMetadata on page visit, and I can definitely see it missing in some of my older page docs, but cannot reproduce in any page visits I do now

I am specifically looking at visits, not imports.
I tested it with master, and everything works fine. In your fork @urbancvek it does not. Maybe something got mixed up on your side then.

I pretty sure the problem was that there was something wrong with the branch I was working with. Because it works from the time that I rebased from master.

Mhh weird, now it seems to be fine for me as well. Just redownloaded your branch and built it again. Gonna close the issue then.


Exclude ARM from macOS builds architectures

Description
Before this change flutter build macos --release failed even on an x86 mac because release builds include all "valid" architectures, which includes arm64 on Xcode 12.
Exclude arm64 from macOS builds until that architecture can be added to the FlutterMacOS.framework.
This "fixes" commands from flutter tooling, but not Xcode.  Archiving from Xcode would still fail.
Related Issues
https://github.com/flutter/flutter/issues/70566
Tests
build_macos_test

Thanks!


The RFC2822 functionality requires a dedicated to-string function

Add a toRFC2822String() method to output a string in a fixed RFC2822 format.
See comments in issue #3920

PR #3939 added to resolve.

Issue withdrawn.


Supported features

Mainly wanted to start with thanking you for making MaxText available. I have been using it for a few days, and the first impression is fantastic. Getting started was really easy, it seemed very stable, and the performance was fantastic. It seems to scale very nicely.
A few things that I have not been able to figure out yet, it might be because of lack of documentation, or simply because it is not implemented.

Are there any support for Flash attention, or any plans for implementing this? This has been a major area where GPUs have been ahead of TPUs. I have noticed that there now is at least an experimental implementation from the Jax-team: https://github.com/google/jax/blob/main/jax/experimental/pallas/ops/tpu/flash_attention.py.

Training directly from  tfds seemed straight forward. However, I was a bit confused about how to implement more advanced data loader features, for instance probability sampling like explained here. This can be somewhat tricky to do efficiently on multiple tpus. What is the sensible approach here? Manually sampling into a tfds dataset does not seem very efficient. Are there external libraries here that are compatible with maxtext?

Are there plans for implementing DPO/RLHF?

I also shamelessly wanted to point you to my own repo: https://github.com/peregilk/ttconnect. It is a very simple bash script that ideally should be run on a VM in the same zone. It automatically opens up synchronised tmux windows to all the VMs in the pod, and allows you to type the same command into all the VMs. This makes it even easier to go from one tpu to pods.

Thank you for the comments!
(1) Fused attention is on by default for training! We use "splash attention" which is a custom and faster version! (And we're working on accelerated inference attentions.)
(2) We don't implement more advanced data loaders though I think they can be implemented in TFDS. It is also easy to plug in your own data loader. Is there a specific data loading solution you'd like us to use?
(3) Yes, DPO is underway!
ttconnect is super cool, thanks for sending!

Thanks for the answer. Looking forward to the DPO support.
It would of course be fantastic if the HuggingFace datasets could natively be supported. I have never really been able to run large non-streaming datasets from HF on the TPUs (disk-size issues on the VMs), but we have been able to wrap the HF datasets in torch.split_dataset_by_node, to stream on multiple TPUs. Im not sure if I am able to implement something like this into MaxText though. Not really sure on what level it should be implemented.
Any chance you support HF datasets in the future?
But any way of preprocessing the data before it is split to the TPUs would be extremely useful for running experiments on dataset building. Thats both for sampling or filtering based on a field in the dataset.

Yes support for HF datasets in MaxText is on the way
@aireenmei

Thank you for tagging me on this. Yes, supporting HuggingFace dataset is in our plan. We have some implementations and are undergoing some perf evaluations to understand it better. I will update here when we have it out.

Hi @peregilk , HuugingFace dataset is supported now. Please check out https://github.com/google/maxtext/blob/main/getting_started/Data_Input_Pipeline.md.

Yes, jsonl.gz is supported, as well as other formats supported by datasets.load_dataset (https://huggingface.co/docs/datasets/en/loading)

@aireenmei Is there a more detailed documentation here. I was for instance unable to figure out how to specify the validation set.

Hi @peregilk, a specific validation set is not supported yet. But this is in our list of items to be worked on.

Hi @peregilk , eval is supported now https://github.com/google/maxtext/pull/738

@aireenmei Thanks a lot. Really looking forward to testing this.
Since this seems to be very related, I am reporting here. Can open an issue if you like:
I am training with:
hf_data_files='gs://mybucket/mydir/train*.jsonl'

There are 256 files in the directory. Close to the end of the first epoch one of the workers throws this error in maxtext/MaxText/input_pipeline/_input_pipeline_utils.py", line 95, in __getitem__:
The above exception was the direct cause of the following exception:

ValueError: Run out of shards, shard 259 is not available

Hi @peregilk , this should be the expected behavior. With the current implementation, you may not be able to use all the data in your train files. Say that you have 256 files and you are using v4-64 that has 8 hosts. Each host will read 256/8=32 shards. The i-th host will read the (8*x + i)-th shard (0<=x<32). For exp, host 0 reads shard 0, 8, 16, ..., 248; host 7 reads shard 7, 15, ..., 255 etc. When a host finish their current shard, they move to the next shard assigned to them. But since each shard has slightly different number of examples, the training will stop when the one of the hosts run out of data. For the above exp, if host 0 is the first one to finish it's last shard, 248, it will look for shard 248+8=256, which is not available, and it will results in the error you see.

Thank @aireenmei. Not sure I understand though. Why would not the logical behaviour here be simply to restart on the first shard that was given to the host when there are no more shards available? Alternatively you would have to duplicate your dataset for training more than one epoch, right?

I did not implement the auto restart because some users may not want their model to see repetitive data. I can add the multi-epoch support to our backlog. Meanwhile it should be straightfoward to change the shard update logic here: https://github.com/google/maxtext/blob/main/MaxText/input_pipeline/_input_pipeline_utils.py#L105

OK. Makes sense. Thanks.

@aireenmei I have tried using your validation support for hf-datasets. I am seeing the same issue here, setting hf_eval_files. Even if the number of shard are dividable by the number of the number of workers, it still crashes asking for the next shard. I cant see any way to limit the number of eval steps, so that it does not run out of shards. What am I missing?

Hi @peregilk indeed this is a bug. I will fix it. Meanwhile this flag (https://github.com/google/maxtext/blob/main/MaxText/configs/base.yml#L336) controls eval step that you can use for now, I'll rename it to eval_steps in my next pr for clarity.

any update on dpo?

DPO is still underway! Very close now

That is fantastic news @gobbleturk. Any chance this also would support SimPO. I understand the implementation would be very similar. It would just align perfectly with an ongoing project of mine..;)


Update LFF converter to latest FontoBene specifications

See commit messages for details.

Oh, I forgot to implement https://github.com/fontobene/fontobene/pull/28 :scream:

Did you test a few files with this converter?

So far I tested only the unicode.lff file.


Check content of Topic#message

It looks like the serializer for topic messages is broken on BE side.

// response from http://localhost:8080/api/clusters/secondLocal/topics/__confluent.support.metrics/messages
[
  {
    "partition": 0,
    "offset": 0,
    "timestamp": "2021-02-17T12:36:37.028Z",
    "timestampType": "CREATE_TIME",
    "key": null,
    "headers": {},
    "content": "Obj\u0001\u0002\u0016avro.schema�\u0010{\"type\":\"record\",\"name\":\"SupportKafkaMetricsBasic\",\"namespace\":\"io.confluent.support.metrics\",\"doc\":\"Represents basic metrics captured on a single Kafka broker\",\"fields\":[{\"name\":\"timestamp\",\"type\":\"long\",\"doc\":\"Time when this data record was created on the broker (Unix time).\"},{\"name\":\"kafkaVersion\",\"type\":{\"type\":\"string\",\"avro.java.string\":\"String\"},\"doc\":\"The version of Kafka this broker is running.\"},{\"name\":\"confluentPlatformVersion\",\"type\":[\"null\",{\"type\":\"string\",\"avro.java.string\":\"String\"}],\"doc\":\"The version of the Confluent Platform this broker is running.\"},{\"name\":\"collectorState\",\"type\":\"int\",\"doc\":\"The state of the collector (e.g., Running or Shutting down).\"},{\"name\":\"brokerProcessUUID\",\"type\":{\"type\":\"string\",\"avro.java.string\":\"String\"},\"doc\":\"A unique identifier that is valid for the runtime of a broker.  The identifier is generated at broker startup and lost at shutdown/crash.\"},{\"name\":\"clusterId\",\"type\":{\"type\":\"string\",\"avro.java.string\":\"String\"},\"doc\":\"A unique identifier for the Kafka cluster.\",\"default\":\"NA\"}]}\u0000\u0016�,���>�]������\u0001\u0002�\u0001���\f\u00122.1.0-cp1\u0002\n5.1.0\u0004Hc2ed1ede-1ee7-4d9e-8165-e123b87f62ac,v9x-xSFPTE6hrwU2BN-dDA\u0016�,���>�]������\u0001"
  }
]

Please describe how kafka-ui was launched, looks like schema registry config was missed

hi there
for me i have the same problem
i am supposed to sue avro SERDE
but i was unable to find on the documentation the exact config that should be used in order to tell the UI
that he supposed to use the AVRO dec


fix: fix scope error with duplicate schema name

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[ ] N
[x] Y  fix #1552

2. What is the scope of this PR (e.g. component or file name):

3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[x] Other

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

[x] N
[ ] Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

[ ] Unit test
[ ] Integration test
[ ] Benchmark (add benchmark stats below)
[x] Manual test (add detailed scripts or steps below)
[ ] Other

Pull Request Test Coverage Report for Build<PHONE_NUMBER>0
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 70.587%

Totals

Change from base Build<PHONE_NUMBER>1:
0.0%

Covered Lines:
50595

Relevant Lines:
71678

💛  - Coveralls


Warning with _xenomai_init_fetchargv in bootstrap-template.h

Hi, I compiled a simple HelloWorld using the patchset (Xenomai 3.1) with the following config :

COBALT
_XENOMAI_BOOTSTRAP_GLIBC_CONSTRUCTORS_REAL = 1
_XENOMAI_INIT_HASFETCHARGV not defined

In this case, the static inline function _xenomai_init_fetchargv() is declared but not defined. I think the declaration should be moved just before the definition of xenomai_bootstrap() only in the case _XENOMAI_BOOTSTRAP_GLIBC_CONSTRUCTORS_REAL != 1.
Do you want a PR ? If yes, which headers do I have to change (there are three bootstrap-template.h in the repository)

I horribly neglected this repository, I still want to do a big cleanup, potentially after 3.1 is released. So a PR is not worth it for now.
I also have a local version, that I have not pushed yet, see if this fixes your problem:
@@ -109,7 +109,8 @@ int _XENOMAI_BOOTSTRAP_DEFINE_MAINWRAPPER(int argc, char *const argv[]);

 #if defined(_XENOMAI_INIT_HASFETCHARGV)
 #define _xenomai_init_fetchargv(a, v) xenomai_init_fetchargv((a), (v))
-#else
+#elif  (!defined(_XENOMAI_BOOTSTRAP_GLIBC_CONSTRUCTORS_REAL) || \
+        _XENOMAI_BOOTSTRAP_GLIBC_CONSTRUCTORS_REAL != 1)
 __attribute__((unused,always_inline))
 static __inline__ int _xenomai_init_fetchargv(int *argcp, char *const **argvp);
 #endif

Ok, seems good thanks !


Create 'getting started'

Create a getting started guide on how to create your own plugin

Issue migrated to our-city-app/gae-plugin-framework#7


Change page_type parameter to model_type or content_type

Since it can be something other than a page. There are also a few other places where we refer to page that we should probably refer instead to obj

Resolved by #38


Mobile toc fix

These changes make it so that the table of contents is not sticky on mobile/touch screens.

thanks

Thanks for the awesome theme!


Organization pages return empty array

Calling GET on organization pages returns an empty array when there should be one page. With the panoptes-javascript-client GET on https://panoptes-staging.zooniverse.org/api/organizations/6/pages?http_cache=true returns a 200 response and the following:
{
  "organization_pages": [],
  "links": {
    "organization_pages.organization": {
      "href": "/organizations/{organization_pages.organization}",
      "type": "organizations"
    }
  },
  "meta": {
    "organization_pages": {
      "page": 1,
      "page_size": 20,
      "count": 0,
      "include": [],
      "page_count": 0,
      "previous_page": null,
      "next_page": null,
      "first_href": "/organizations/6/pages?language=en",
      "previous_href": null,
      "next_href": null,
      "last_href": "/organizations//pages?page=0&language=en"
    }
  }
}

This would be fine, except I had previously created a page and would expect that one to be in the array of the response of the GET request. If I make a POST for the page I had thought I had created, I get a 400 with the response errors: [{message: "Validation failed: Url key has already been taken"}].

@srallen i assume the page was linked to org 6? Thoughts @zwolf ?

Yep, id 6 is the org I'm working with on staging.

This is because the /pages#index endpoint (of both projects and orgs) is open and doesn't check authentication. As such, it's filtering out all the private orgs and projects. For project, it's checking the private boolean, and for orgs it's checking where(listed_at: nil).
I haven't looked, but I'm guessing the way PFE is actually getting the project pages is with a call to /projects/:id?include=pages.  PR incoming.

We found this is actually happening because of a mismatch of the language codes between the organization resource's primary_language and the contents' language property (en-US vs the hardcoded en language on pages right now). The API probably shouldn't 500 for this.

I'm not sure about the best place to note this, but a request for a dialect should really fall back to the root language if the dialect isn't available. So a request for en-US should return resources flagged en instead of nothing.
We can possibly handle this in the front end by making a second request for the general language, if the request for a specific dialect fails.
In the past, though, we've never differentiated between US and UK English. English resources have just been flagged en. Similarly with Spanish translations. I think the only times that we've used language dialects is in Chinese translations.

@eatyourgreens what lang codes does the front end use when creating translatable resources?

@camallen it gets the locale from counterpart. That defaults to en but would be set be the end user once other languages are available.

This issue came up recently because the lab app isn't using Counterpart and is getting the locale directly from the browser, which was 'en-US'. For pages, paniptes is hardcoded to alter the language param. But that isn't the case for projects/orgs themselves.
Options include trimming on the front end, using Counterpart instead, or matching differently in the controllers.

I think loading with the supplied language codes (with a defaut) API side is the optimal solution here. Something similar to this i guess.

Counterpart will be added to the PFE lab app soon.

Noting here that translators will request resources in more than one language, so the translation app or API client should be able to easily switch languages when making queries to the Panoptes API.


Split NED into topology and topobathy parts

This should help to alleviate the overlapping nature of the files doesn't cause too many problems.
Connects to #3.
@rmarianski could you review, please?

Looks good! :+1:
I personally try to avoid inheritance and base classes everywhere I can. If there's anything that needs to vary behavior-wise, I usually just pass references to functions around to handle that. I do recognize that this is somewhat a stylistic preference though :)

Good point! I refactored in ac522da to use composition rather than inheritance. The code is a little bit longer, but might be easier to maintain / test. Could you take another look, please, and let me know what you think?

:+1:


Notes not being saved

I noticed either on the Groups page where you can add a note for each grouping or add a note anywhere else, it just says "Working..." and continues to load but doesn't add the note. In the rails server log, it says it has completed rendering the page or something like that and does nothing else. So not sure if it's a database issue or something wrong with notes code.

This is a chrome issue. It works fine on Firefox.


docs(hubble): improve docs in www

What is the issue?
A few suggestions for improving documentation for Hubble:

[x] Connect public domain to deployment
[x] Explain how versioning works
[x] CLI - re-arrange, re-name and correctly document command options
[x] Explain how authentication works
[x] Double check that all available APIs are correctly documented
[ ] Explain how to set up Hubble from source without docker.
[ ] @CassOnMars to do a review of the storage APIs and ensure they are correctly documented
[ ] @sanjayprabhu to do a review of the ens names and make sure they are correctly documented
[ ] @sds explain how envoy works and how to configure it.

fixed cli in #1154


revanc docker containers and meshdir are restarting every 1 minutes

What do the logs say?

Nothing actually...

If the logs say nothing then the container is not starting. Try ./scripts/clean.sh and restart everything.

Can you add a screenshot of the command you use to show the container logs?

That looks like the output of ./scripts/nrrn-testing.sh
Can you show the output of docker logs -f maria1.docker?

You said something about /bin/sh: 1: /reva/cmd/revad/revad: not found on Slack. That can probably be fixed by running ./scripts/build-revad-on-host.sh

That looks like the output of ./scripts/nrrn-testing.sh Can you show the output of docker logs -f maria1.docker?

2023-01-30 11:14:58+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.10.2+maria~ubu2204 started.
2023-01-30 11:14:58+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2023-01-30 11:14:58+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.10.2+maria~ubu2204 started.
2023-01-30 11:14:58+00:00 [Note] [Entrypoint]: Initializing database files
2023-01-30 11:14:58 0 [ERROR] mariadbd: Error writing file './ddl_recovery.log' (Errcode: 28 "No space left on device")
2023-01-30 11:14:58 0 [ERROR] Aborting
2023-01-30 11:14:58 0 [ERROR] mariadbd: Error on close of '(null)' (Errcode: 9 "Bad file descriptor")
Installation of system tables failed!  Examine the logs in
/var/lib/mysql/ for more information.

Like I thought, "No space left on device" :)


DDCE-5501:Initial commit for upgrading sbt-accessibility linter

heya maybe just unlucky with timing on review but there are some more dependency bumps which can also be done with this ticket.
And the bot has picked up on some plugins aswell.

also as part of the acceptance criteria can you please add the a11y tests to the run_all test script please.


Fbx animation parser bug

In some case, animation is not parsered correctly( no error, just wrong animcurve time? ).

A sample fbx file has sended to auther's mail.

It seems that the animation was not baked: some anim curves only have 3 values of the 30 frames. Check Bake Animation when exporting from 3DS Max.

Thanks! I'll check it asap.


Python is broken in the current Nuget version

Description
Python is broken in the current Nuget version : v1.0.1
It seems the last version (v2.0.13) of ColorCode had some build issue that somehow broke support for Python, it was fixed in the latest version (v2.0.14). This has been updated and merged already but the Nuget package has not been updated.
Expected Behaviour
Python language blocks should be properly color coded

    this = that
    DoSomething()
    # this is a comment

Actual Behaviour
Python language blocks are not properly color coded

    this = that
    DoSomething()
    # this is a comment

Affected Version
v1.0.1
Steps to Reproduce
dotnet add package Markdown.ColorCode --version 1.0.1
string code = @"```python
    this = that
    DoSomething()
    # this is a comment
```";
                var pipeline = new MarkdownPipelineBuilder()
                    .UseAdvancedExtensions()
                    .UseColorCode()
                    .Build();
                Console.WriteLine(Markdig.Markdown.ToHtml(code, pipeline));

Checklist

[x] I have read the contributing guidelines
[x] I have verified this does not duplicate an existing issue

Hey, thanks for the report @netclectic!
I just cut a new v1.0.2 release that includes the updated ColorCode packages. Let me know if this addresses the issues with Python that you were seeing and close out this issue if it is resolved. 👍🏻

Yep, sorted now.
Thanks.


NATIVE-164: Persist city selection

@Schedulaar how would injecting an initial route config solve the problem that we don't need a Loading screen? The loading route is for the time it takes to decide whether there is a selected city or not. If we set an initial route config, be have the problem with jumpy screens again. Am I understanding something wrong here?


Source Command Drops Last Line of Code

Small bug I noticed when asking the source command to print specific lines of code. The last line seems to get dropped.
Example <bot_prefix>source example_cog.py 1 3 would only print lines 1 and 2:
1:    #what the bot does
2:    import logging

when i originally wrote it it, i wrote it to be range inclusive exclusive but that really doesnt make a ton sense and should probably be changed

Should this be closed since the source command no longer outputs the source in Discord?


Tooltip display cut off

The current tooltip direction does not respond accordingly to it's current position. In the event the tooltip is overly right and tooltip direction is set to right, the tooltip is hidden by the screen.
We should check the current position of the tooltip on hover and check if the tooltip message has sufficient space to display in it's set direction. If not, then the tooltip should move itself.

Need more discussion on this issue:

If the tooltip is set far right/left, the tooltip wraps the text to make it's best effort to make the dialog intact within the screen. Therefore, the question is is it nessesary to overwrite the user direction setting in this case? How much text wrapping should be the threshold to overwrite the direction?

The case when tooltip is hidden is when the user had set the direction to top/bottom and the users screen is scrolled past the tooltip direction. When the vertical direction is set but not the top/bottom, horizontal direction is set automatically.

Closing this issue by deciding not to override developers decision automatically


Handling attributes documented using sphinx comment-based docstrings

The attributes in plotnine.options look as follows:
#: Development flag, e.g. set to ``True`` to prevent
#: the queuing up of figures when errors happen.
close_all_figures = False

#: Theme used when none is added to the ggplot object
current_theme = None

#: The base font family for all text that is part of the theme.
#: Default is sans-serif and one is choosen automatically from
#: rcParams["font.san-serif"]
base_family = "sans-serif"

Note that lines starting with #: are a special comment-based docstring syntax in sphinx. This isn't currently supported in griffe.
I can open a feature request on griffe, but if us changing these to use the """ docstring syntax is an option, it might get us over the finish line a bit faster 😅
With the other syntax it looks like...
close_all_figures = False
"""
Development flag, e.g. set to ``True`` to prevent
the queuing up of figures when errors happen.
"""

current_theme = None
"""Theme used when none is added to the ggplot object"""

@has2k1 WDYT?

The 2nd option is okay.


Style/AlignHash: Align the elements of a hash literal if they span more than one line.

Hello!
Getting that offense on 0.29.1 where I didn't get them before.
Been able to figure out most of them, but this one has me stumped. :-)
                  'Content-Length'                   =>
                    'length',
                  'Content-Type'                     =>
                    'application/json; charset=utf-8',
                  'Access-Control-Max-Age'           =>
                    '1728000',
                  'Access-Control-Allow-Methods'     =>
                    'POST, PUT, GET, PATCH, HEAD, OPTIONS',
                  'Access-Control-Allow-Origin'      =>
                    Constants::BASE_URL,
                  'Access-Control-Allow-Credentials' =>
                    'true'

I'm not able to do anything simpler due to line length limits...

Hmm, I'll have to think about this. I've never had to write a hash in this manner and I feel that breaking it up like this seriously impairs the readability.

There is a good reason why cops can be disabled.
Sometimes there may be rare situations where a general style rule just doesn't apply. But we can't cater for every such rare situation. A better solution is to simply disable the cop.

@alexdowad I agree 100%, just wanted to show a situation I came across.

@tmornini Thanks for showing us, and sorry that there doesn't seem to be a better solution right now.
Maintainers, please close.

I encountered this today.
I originally had

def foo
@bar = { en: "Lorem",
es: "Ipsum",
fr: "Dolor"
}
end

It has to be

def foo
@bar = {
en: "Lorem",
es: "Ipsum",
fr: "Dolor"
}
end

@martinverdejo me, uhh?

Elements of a hash can be just aligned literal, like this:
def foo
  @bar ||= { end: 'Lorem',
             es: 'Ipsum',
             fr: 'Dolor' }
end

We have the same problem, that we'd like to align a hash as @akimd did, but rubocop complains. Aligning a hash in such a way is especially useful if the lengths of the keys differ greatly from one another, because it increases readability imo:
Currently required by rubocop:
my_hash = {
  abc: 10,
  def: 20,
  ghijklmno: 30,
  p: 40,
  qrstuvwyxzw: 50
}

What I'd wish would also be accepted:
my_hash = {
  abc:         10,
  def:         20,
  ghijklmno:   30,
  p:           40,
  qrstuvwyxzw: 50
}

why is this being ignored?

why is this being ignored?

because it was closed 5 years ago :)

Just stumbled on this issue in some of our code. Solved it this way to troll a coworker.  rubocop approved. Coworker did not.
my_hash = {
  'foo' => '   perfectly_aligned_value_1'.strip,
  'z' => '     perfectly_aligned_value_2'.strip,
  'bar' => '   perfectly_aligned_value_3'.strip,
  'baz' => '   perfectly_aligned_value_4'.strip,
  'bletch' => 'perfectly_aligned_value_5'.strip,
  'dr' => '    perfectly_aligned_value_6'.strip,
}

But more seriously, it looks those of us who showed up since 2019 are concerned about a different issue than the one this ticket was opened for.
It looks like a more relevant bug about value, rather than key alignment would be here, and perhaps recently resolved?
https://github.com/rubocop-hq/rubocop/issues/7291

@bjtucker Looking at https://github.com/rubocop/rubocop/blob/master/spec/rubocop/cop/layout/hash_alignment_spec.rb
I notice there are not specs dealing with values of varying characters.  All of these alignments should be valid:
my_hash = {
  abc:         10,
  def:         20,
  ghijklmno:   30,
  p:           40,
  qrstuvwyxzw: 50
}

my_hash = {
  abc:         1,
  def:         20,
  ghijklmno:   30,
  p:           40,
  qrstuvwyxzw: 50
}

my_hash = {
  abc:          1,
  def:         20,
  ghijklmno:   30,
  p:           40,
  qrstuvwyxzw: 50
}

I haven't  confirmed, but I suspect the one of the latter two examples makes Rubocop unhappy.

@KelseyDH this is the only one that got accepted on my side (default rubocop, format similar to @bsolomud 's one )
        { 'a1' => 1.0 / (24 * 60),
          'a2' => 5.0 / (24 * 60),
          'a23' => 15.0 / (24 * 60),
          'a4' => 1.0 / 24,
          'a433' => 4.0 / 24,
          'a432' => 12 / 24,
          'a12' => 1,
          'ab' => 7 }


web script loading fix

Is your feature request related to a problem? Please describe.
fixing the pdf.js not loading for some people due to The https://cdn.jsdelivr.net/ domain is blocked in a number of countries including Egypt and China. It has been blocked in China since about May 2022 and in Egypt since about June 2023. You have to either use your files locally or search other alternatives like UNPKG or cdnjs
Describe the solution you'd like
i am using the script to try to load pdf.js from two places if one fails
Describe alternatives you've considered
  <!-- pdf -->
  <script>
    function loadScript(url, fallbackUrl, onSuccess, onError) {
      var script = document.createElement('script');
      script.src = url;
      script.onload = onSuccess;
      script.onerror = function () {
        console.error('Failed to load script: ' + url);
        if (fallbackUrl) {
          console.log('Trying fallback URL: ' + fallbackUrl);
          loadScript(fallbackUrl, null, onSuccess, onError);
        } else {
          onError();
        }
      };
      document.head.appendChild(script);
    }

    function loadPDFJS() {
      pdfjsLib.GlobalWorkerOptions.workerSrc =<EMAIL_ADDRESS>      pdfRenderOptions = {
        cMapUrl<EMAIL_ADDRESS>        cMapPacked: true,
      };
      // console.log('Loaded PDF.js from ');

    }

    // Try the primary URL first
<EMAIL_ADDRESS><EMAIL_ADDRESS>loadPDFJS, function () {
      console.error('Failed to load PDF.js');
      // Handle error condition, e.g., show an error message to the user
    });
  </script>

Additional context
hope it helps, and if any thing that needs to be updated let me know (the script was created by chatgpt since i dont understand much in javascript)
but it worked in my case

Sorry for piggy backing off your question, does anyone know how to bundle this pdfjs library into my flutter web app directly so I don't need to download it from the cdn?

Sorry for piggy backing off your question, does anyone know how to bundle this pdfjs library into my flutter web app directly so I don't need to download it from the cdn?

I didn't try, but I think you can download it and add it to web folder, and then make the script read it from that


Finish application translation

This fixes #8 thanks to the work made by @b-durand in #78.

The reorganization of the English translation is now complete. Please review it before I make the needed changes in the rest of translations. Thanks.

@javiereguiluz if this is merged i will do the german translation if you like and if useful

@OskarStark great! That would be awesome.

ok :smile:

I have a question about the names of the translation strings related to the entity validation.
I've defined them as follows, but I don't like it:
<trans-unit id="entity.comment_blank">
    <source>entity.comment_blank</source>
    <target>Please don't leave your comment blank!</target>
</trans-unit>
<trans-unit id="entity.comment_short">
    <source>entity.comment_short</source>
    <target>Comment is too short ({{ limit }} characters minimum)</target>
</trans-unit>
<trans-unit id="entity.comment_long">
    <source>entity.comment_long</source>
    <target>Comment is too long ({{ limit }} characters maximum)</target>
</trans-unit>
<trans-unit id="entity.comment_invalid">
    <source>entity.comment_invalid</source>
    <target>The content of this comment is considered spam.</target>
</trans-unit>
<trans-unit id="entity.summary_blank">
    <source>entity.summary_blank</source>
    <target>Give your post a summary!</target>
</trans-unit>
<trans-unit id="entity.post_short">
    <source>entity.post_short</source>
    <target>Post content is too short ({{ limit }} characters minimum)</target>
</trans-unit>

What do you think of replacing it by the following?
<trans-unit id="comment.blank">
    <source>comment.blank</source>
    <target>Please don't leave your comment blank!</target>
</trans-unit>
<trans-unit id="comment.too_short">
    <source>comment.too_short</source>
    <target>Comment is too short ({{ limit }} characters minimum)</target>
</trans-unit>
<trans-unit id="comment.too_long">
    <source>comment.too_long</source>
    <target>Comment is too long ({{ limit }} characters maximum)</target>
</trans-unit>
<trans-unit id="comment.is_spam">
    <source>comment.is_spam</source>
    <target>The content of this comment is considered spam.</target>
</trans-unit>
<trans-unit id="comment.blank_summary">
    <source>comment.blank_summary</source>
    <target>Give your post a summary!</target>
</trans-unit>
<trans-unit id="post.too_short">
    <source>post.too_short</source>
    <target>Post content is too short ({{ limit }} characters minimum)</target>
</trans-unit>

:+1:  for shorter version!

@javiereguiluz the domain is validators and not message for constraints.

@b-durand I can't believe I made this mistake :'(  This morning I saw that translation wasn't working for validation ... but I didn't realize this issue. Thanks for telling me! It's fixed now.

We should also localize the date format for "commented on". I regret to have choice with only 4 formats instead of format pattern for skeleton :disappointed:

@b-durand I'm not sure I understand your last comment about date internationalization.

i think @b-durand would say, that in englisch we use 01-01-2015 and in german ```01.01.2015````

OK, I understand now. Thanks. Let's do that change in a separate PR because it needs to install the Twig extensions and all that.

@b-durand this feature is finally merged. Thanks a lot for working on this!

@OskarStark this feature is finally merged, so you can update the German translation if you have some free time. Thanks!

i can do for Hebrew
still needed?


Use https for wpackagist in docs

As in 19c79b812 this pull request simply updates all the URLs to wpackagist.org in the documentation. That avoids »insecure connection« errors in composer for a user, when following the documentation strictly (c&p).

@dnaber-de Thanks!


For rke2 installs to vmware, note that open-vm-tools must be installed to prevent cni issues

Note that when rke2, though not exclusively k3s should be affected similarly like any other userland application in linux, is installed into a system on vsphere. To prevent intermittent errors relating to CNI traffic as well as local inter process IPC, open-vm-tools must be installed to have a CNI setup that doesn't have intermittent tcp errors.
Not sure where we would want to document this guidance appreciated.

PRs are welcome, a good place would be in the requirements page, like as an addendum to the Linux/Windows section
https://github.com/rancher/rke2-docs/blob/main/docs/install/requirements.md#operating-systems
Yes vsphere is not an OS, but it fit with "foundational software/hypervisor" idea for requirements.


fix for 11-usart

@paulkernfeld should fix #264
11-usart was panicking on the older version of cortex-m, updating to 0.6.3 fixes that, but introduces incompatibilities with the f3 crate. I replaced the f3 crate with the newer stm32f3xx-hal. Also had to add memory.x to project root in order to get things to compile, maybe there's a better solution for that?

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @andre-richter (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

FYI, we are looking at a major rewrite of this book since the STM32F3Discovery boards have become difficult to buy. We may choose the micro:bit board as a replacement. See #263

I am not familiar with the cortex-m stuff. Temporarily switching my assignment mit @adamgreig. Adam, please see if you can review or delegate this. Thanks :)

@andre-richter Is someone else available to review this?  I assume that @adamgreig is busy.

Ugh, sorry, this totally fell off my radar. I think there's two issues merging this as-is:

It requires an additional change to 11-usart/src/main.rs to put the call to tdr().bits() into an unsafe block (and also removing the #[deny(unsafe_code)] attribute at the top), but sticking that unsafe code in seems quite confusing to newcomers and would need explaining (why do we need it here but not elsewhere, etc)
I guess memory.x was being provided by the HAL, but we shouldn't then stick a new one in the repository root. We could probably place it inside the 11-usart/ directory along with a build.rs script to copy it to the linker directory.

For the second point I think we can just swap the dependency to the new stm32f3-discovery crate and update the exports to stm32f3_discovery::stm32f3xx_hal::..., so we don't need a memory.x at all.
However I think we still need the unsafe block which isn't great... looking into it it seems like an error in the stm32f3 crate where the TDR register is said to be safe for any value 0-255 but as it's a nine-bit register it should actually go to 0x1ff. Dunno why that's not been caught before to be honest... but it won't be a quick update, so for now I guess we're stuck with the unsafe block.

This has now been fixed by #354, thank you for starting the work in this PR!


Yen Trader/Cross Trader

Original idea: https://www.forexfactory.com/showthread.php?t=595898
Possible improvement: Instead of using related pairs to identify trend we should use the related currency indexes for indication which removes skew and noise caused by the unrelated currency (USD in case of Yen crosses).
The existing rules to identify trend are counter-productive and cause a near random entry on lower timeframes.
The advised trailing stop concept destroys the risk-reward ratio and thus the potential.
The general system idea can be extended to any FX pair and may serve as a cheap replacement for trading synthetic currency indexes. However because of its nature an index will always trend better than any pair.
There are some interesting scalping forward tests. By using indexes and/or runtime optimization there could be short term potential. Some stuff to play with. :-)

All the good performance examples have been a direct result of the strong GBP trend in the first 6 months of 2016 related to Brexit. Since volatility came back to normal levels the system immediately started losing.


CPP: Better handling of %s/%c/%S/%C in Printf/FormattingFunction.qll

A customer pointed out a few weeks ago that the meanings of the %s / %S format characters are not 'reversed' in wide printf functions on Linux as they are on Microsoft platforms - i.e. %s is always char and %S is always wide on Linux, whereas %s always matches the format string's character type and %S is always the opposite in Microsoft-land.  %c / %C are similarly affected.
I've run some tests using VS on my Windows laptop and g++ on a remote Linux box and this appears to be an accurate summary - but I wouldn't be surprised if at some point we find edge cases (compiler arguments? C++ versions? MinGW?) to account for as well.
This PR fixes the above, improves the Microsoft-detection logic, and cleans up a bit more duplicated logic (see prior work in https://github.com/Semmle/ql/pull/1008).
Results and performance are unaffected for most real-world projects (wide character printfs are relatively rare).  Sadly I do not have access to the example which motivated this work, so we have to rely on tests.

Merge conflict fixed.

There's a failing test and a merge conflict.

Yep, it's yet another conflict on the change notes file - fixed.
The test result changes are addressed in https://git.semmle.com/Semmle/code/pull/31148/files


Add naqline

Adds Naqline processing stuff up to what you can do in late IV (including Naquadria, excluding Extremely Unstable Naq Ingot and other ZPM stuff). I pruned down most cycles by hand but there are some byproducts that could be recycled in awkward ratios (including sodium hydroxide, sulfuric acid, maybe some more) that seemed too nasty.

Looks good to me. Thanks for manually solving the parts the solver could not and leaving comments about how you did so


multiPart file Post call failing with updated version past 2.6.0 and up

I updated my pom.xml to the latest version 2.9.0 and started getting the following error.
java.lang.NoSuchMethodError: org.apache.http.entity.ContentType.withParameters([Lorg/apache/http/NameValuePair;)Lorg/apache/http/entity/ContentType;
	at org.apache.http.entity.mime.MultipartEntityBuilder.buildEntity(MultipartEntityBuilder.java:219)
	at org.apache.http.entity.mime.MultipartEntityBuilder.build(MultipartEntityBuilder.java:240)
	at org.apache.http.entity.mime.MultipartEntityBuilder$build$16.call(Unknown Source)
	at com.jayway.restassured.internal.multipart.RestAssuredMultiPartEntity.getEntity(RestAssuredMultiPartEntity.groovy:58)

I get the same error if I switch to 2.8, 2.7, and 2.6.
I don't have any special set up for rest-assured or the TestNG framework. The below is how it's set up in the pom.xml file.
	<dependency>
		<groupId>org.codehaus.groovy</groupId>
		<artifactId>groovy-all</artifactId>
		<!-- Needs to be the same version that REST Assured depends on -->
		<version>2.4.4</version>
		<scope>test</scope>
	</dependency>

        <dependency>
            <groupId>com.jayway.restassured</groupId>
            <artifactId>rest-assured</artifactId>
            <version>2.6.0</version>
            <scope>test</scope>
        </dependency>
        <dependency>
            <groupId>com.jayway.restassured</groupId>
            <artifactId>json-schema-validator</artifactId>
            <version>2.6.0</version>
            <scope>test</scope>
        </dependency>
	<dependency>
		<groupId>commons-codec</groupId>
		<artifactId>commons-codec</artifactId>
		<version>1.4</version>
	</dependency>
	<dependency>
		<groupId>org.testng</groupId>
		<artifactId>testng</artifactId>
		<version>6.9.10</version>
		<scope>test</scope>
	</dependency>

I did find the following issue you responded to and I don't have any other dependencies to Apache HTTP client as you've mentioned. Everything goes strictly through Rest-assured.
Is there anything additional I should be requiring or looking into? Let me know if there's additional information I should provide.
Also, please let me know if this is the proper forum for help with these kind of issues.

Thanks for reporting. Could you provide some code that shows what you're doing?

Here is the call where the error is coming from:
        Response response = given()
                .header("Accept", "application/json")
                .queryParam("token", accessToken)
                .multiPart("body", new File(getClass().getResource("/csv/"+locationFileName).getFile()))
                .when()//.log().all()
                .post(URI.UPLOAD_DATA_FILE.getUri())
                .then()//.log().all()
                .contentType(ContentType.JSON)
                .statusCode(200)
                .assertThat()
                .body( matchesJsonSchemaInClasspath("json-schema/v2-upload-post.json"))
                .extract()
                .response();

I noticed under the change notes for v2.6 there were updates to the multipart call. Do I need to change the configuration for the file now?

Hmm I find it quite strange that you run into a java.lang.NoSuchMethodError. I suspect that you are not using Apache HTTP Client 4.5.1 (that RA depends on). I can confirm that the method you're missing is indeed there. I've debugged your example and I can step into the ContentType.withParameters without any problems.

It looks like there's another dependency that uses Apache HTTP Client 4.3.5 or something. Since that dependency was sitting before RA, the Maven would use the first HTTP Client it hit. I wasn't aware java did that. Very interesting.