Windows 11 not working

I found the software deployment ok on Windows 11 but the ADMX template is not applying from Intune due to a version statement in the admx template

Any change we can also make this work on Windows 11?

Hello,
You should be able to change that value.
Also, please check: https://github.com/sciber-io/yubikey-locker
If still a problem, I will investigate (but will take some time).

Ok, but the question is what to change it in?
Should I change 10 to 11 or are there any predefined values that are accepted?

Just to get things clear, I am using: https://github.com/sciber-io/yubikey-locker with the ADMX of the initial version

Ok I found the values in the windows.admx on my system.
So I think we can change it to: SUPPORTED_Windows_11_0_NOSERVER

  <definition name="SUPPORTED_Windows_11_0_SE" displayName="$(string.SUPPORTED_Windows_11_0_SE)">
      <or>
          <range ref="products:MicrosoftWindows" minVersionIndex="16" maxVersionIndex="16"/>
      </or>
  </definition>

  <!--At least Windows 11 22H2 no SERVER -->
  <definition name="SUPPORTED_Windows_11_0_22H2_NOSERVER" displayName="$(string.SUPPORTED_Windows_11_0_22H2_NOSERVER)">
      <or>
          <range ref="products:MicrosoftWindows" minVersionIndex="16" maxVersionIndex="16"/>
      </or>
  </definition>

  <!--At least Windows 11 22H2 -->
  <definition name="SUPPORTED_Windows_11_0_22H2" displayName="$(string.SUPPORTED_Windows_11_0_22H2)">
      <or>
          <range ref="products:MicrosoftWindows" minVersionIndex="16"/>
      </or>
  </definition>

  <!--At least Windows 11 no SERVER -->
  <definition name="SUPPORTED_Windows_11_0_NOSERVER" displayName="$(string.SUPPORTED_Windows_11_0_NOSERVER)">
      <or>
          <range ref="products:MicrosoftWindows" minVersionIndex="16"/>
      </or>
  </definition>

OK, I see. Give it a go and see if it works. If not, report it on the Sciber repo.

The only thing I do not get is that it is referencing to Scriber
And documentation says it need to ref to Windows (windows.admx)
https://download.microsoft.com/download/5/0/8/5081217f-4a2a-470e-a7fa-5976e40b0839/Group Policy ADMX Syntax Reference Guide.doc
Referencing Windows supportedOn elements
Windows product names support information is provided in the Windows base file. You can reference these product names for your .admx file. In order to use the supported on information in the Windows base file, you must do the following:
•	Within your supportedOn element, add the "windows:" prefix to the ref attribute to reference the Windows base file.
•	Reference a defined supportedOn element from the Windows base file. If you use an invalid element name, the Group Policy Object Editor will not display any supported on information and will not display an error message.
This XML fragment demonstrates referencing supported on text for your policy setting, using existing Windows product information.

Continuing here: https://github.com/sciber-io/yubikey-locker/issues/90


supabase storage

https://supabase.com/docs/guides/storage

@pi0 We have over 10 PRs for drivers just waiting for reviews from contributors and yet you want another one ;D


do not use legacy react-dom/server APIs.

I was trying to implement Easy email on the Next Js@14, but I got this error:
Error: Internal Error: do not use legacy react-dom/server APIs. If you encountered this error, please open an issue on the Next.js repo.
Does anyone know about this?

As far as I know, https://react.dev/reference/react-dom/server/renderToPipeableStream should be used. I wonder if anyone has fixed this problem. @m-Ryan
Thank you!

see https://github.com/vercel/next.js/discussions/58305#discussioncomment-7785006


Wrong syllables

Wrong syllables
"Abend" is ["Aben", "d"].
"Und" is ["Un", "d"]
And Missing symbols

Fixed here d82b655412083a29a6473672ab720139402cff5f


fix: Refactor adapter startup to ensure proper log initilization

Signed-off-by: Jorge Turrado<EMAIL_ADDRESS>
Provide a description of what has been changed
Checklist

[x] Commits are signed with Developer Certificate of Origin (DCO - learn more)
[ ] Changelog has been updated and is aligned with our changelog requirements

Fixes https://github.com/kedacore/keda/issues/2316

/run-e2e

/run-e2e rabbit*

Looking good. Feel free to merge this once you are able to confirm this in the next couple days.

I'll keep it there for 2-3 days and if I don't see any trace, I'll merge it, but even do that, I can't guarantee that it's the fix and not just luck


[backport] Refresh instance types from EKS nodegroup template

https://github.com/rancher/rancher/issues/24049

LGTM


init source code

init source code.

Move all added files to src/pwa directory

Move all added files to src/pwa directory

Move all added files to src/pwa directory

I updated the structure to follow your idea. Please help me take a look again. Thanks

Remove .env file from repository and add it to the .gitignore unless this is a method used by NextJS
Use of Sass (node-sass) for styling so we can use variables and mixins
Move font related imports inside App.js to eg. Styles/main.scss and import into app.js

.env where we push app settings for each environment. ex: Dev, Pro ... So We still need it.

Remove .env file from repository and add it to the .gitignore unless this is a method used by NextJS
Use of Sass (node-sass) for styling so we can use variables and mixins
Move font related imports inside App.js to eg. Styles/main.scss and import into app.js

Use of Sass (node-sass) for styling so we can use variables and mixins
Since we are using 'styled component' pattern on top of Emotion, I suggest to follow its principle/pattern until any issue being noticed or the needs to have SASS in place.

Use of Sass (node-sass) for styling so we can use variables and mixins

Since we are using 'styled component' pattern on top of Emotion, I suggest to follow its principle/pattern until any issue being noticed or the needs to have SASS in place.

I agree, since we are using Emotion, no need to utilize SASS for now.


Historical reports uploaded with curl shows last report having zero results

Hi followed your documentation and perfromed the following steps:

Created a report from the Nightwatch tests using nightwatch-allure lib (https://nightwatchjs.org/guide/reporters/use-nightwatch-allure-reporter.html)

Used Junit reports folder from 1. and command bellow to generate allure-report
allure generate junit_reports --clean -o allure-report

Then zipped the report folder
zip -r allure-report.zip allure-report

Started server locally using java
java -jar -Dallure.support-old-format=true -DPORT=9080 allure-server.jar & disown

Upload zip file and grab uuid
curl -X POST 'http://localhost:9080/api/result' -H  "accept: /" -H  "Content-Type: multipart/form-data" -F "allureResults=@./allure-report.zip;type=application/x-zip-compressed" | jq '.uuid'

Create report using UUID (ffebdfc0-bc5a-4ae1-b320-a01b452788de)
curl --location --request POST 'http://localhost:9080/api/report' --header 'Content-Type: application/json' --data-raw '{ "reportSpec": { "path": [ "master", "dash-1" ], "executorInfo": {"buildName": "#dash-1"}},"results": ["ffebdfc0-bc5a-4ae1-b320-a01b452788de"],"deleteResults": true}'
All reports

Manual upload of the allure-report.zip

Upload using curl

cannot reproduce try last release https://github.com/kochetkov-ma/allure-server/releases/tag/v2.13.6


Fix multiset after Value.tag

The Value.tag PR passed CI when it shouldn't have. This PR fixes the compiler error currently on main.

(CodSpeed is just showing the same speedup as on Value.tag.)


Cache all service entity in memory for query

Querying all service entities and storing them in the cache periodically. All service-level queries should be modified to retrieve data from the cache.

[ ] If this pull request closes/resolves/fixes an existing issue, replace the issue number. Closes #.
[x] Update the CHANGES log.

Based on the log prompt, it seems that there is a problem displaying all Kubernetes resource logs. I suspect that this issue might be related to the Kubernetes resources, so I need to debug the container. Let me switch to draft mode for now.

The previous E2E error occurred due to insufficient storage space in GHA, resulting in the inability to write ES data. To resolve this, the data write threshold configuration for ES was updated, leading to the recovery of GHA.
I think now it's ready to review. @wu-sheng @kezhenxu94


Add support for syntax tree input to remark(1)

This update removes the previously supported -a, --ast flag, and
renames it to --tree-out.  In addition, --tree-in is now supported
to depict that the input read from stdin(4) is an already parsed
syntax tree in JSON.  And, this commit introduces a new -t, --tree
flag which turns both --tree-in and --tree-out on, thus specifying
a tree input on stdin(4) and a tree output on stdout(4).
Closes GH-126.
Closes GH-156.

@eush77 Can you review whether this closes your issue?

Just saw that the docs show the same example, that should at least be fixed.

Yeah, this is cool! :smile:
One thing, somewhat unexpectedly:
$ remark --tree-in b.json
Error: remark does not accept both files and `--tree-in`

Why is that?

For some weird reason I initially only allowed stdin(4) as a syntax tree, I changed that, so now it’s possible to transform files from the file-system too: remark --tree fixtures/tree -e json -o should in theory rewrite a directory of syntax tree fixtures.


OSError: Cannot load native module 'Cryptodome.Cipher._raw_ecb'

Constantly failing to load runserver.py because of this error. Can't find a solution anywhere.

Might be an issue with 32bit vs. 64 bit.

Windows 7, 64-bit | Python 2.7.12, 32-bit


Fix missing fields on new car

Proposed Changes
Apparently these fields can be missing from the RDW API.
Related Issues
https://github.com/home-assistant/core/issues/94920

Codecov Report

Merging #416 (c5cf31b) into main (4623c4d) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main      #416   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            5         5
  Lines          153       153
  Branches         9         9
=========================================
  Hits           153       153

Impacted Files
Coverage Δ

src/vehicle/models.py
100.00% <100.00%> (ø)

Boop

Beep


[OpenCASCADE]dependen on eigen3 and miss "OpenGl_khrplatform.h".

Environment
OS: Win11,  VS2022 latest
Describe the bug

I just want use OpenCASCADE, so I specify OpenCASCADE in vcpkg.json. like this:
{ "$schema": "https://raw.githubusercontent.com/microsoft/vcpkg-tool/main/docs/vcpkg.schema.json", "name": "occtest", "version-string": "0.1.0", "dependencies": [  {    "name": "opencascade",    "version>=": "7.6.2#6"  },  {    "name": "eigen3",    "version>=": "3.4.0#2"  } ], "builtin-baseline": "b51f391cd8f1f5a406b3baf9b014acff61702dc3" }
If I do not speficy eigen3 vcpkg notify me can not find eigen3!

When I added eigen3, it's ok. Then I compiled my demo. code like this:
`#include <opencascade/V3d.hxx>
#include <opencascade/V3d_Viewer.hxx>
#include <opencascade/OpenGl_GraphicDriver.hxx>
int main()
{
// create a graphic driver
Handle(OpenGl_GraphicDriver) aGraphicDriver = new OpenGl_GraphicDriver(Handle(Aspect_DisplayConnection)());
// create a viewer
Handle(V3d_Viewer) a3DViewer = new V3d_Viewer(aGraphicDriver);
// set parameters for V3d_Viewer
// defines default lights -
//   positional-light 0.3 0.0 0.0
//   directional-light V3d_XnegYposZpos
//   directional-light V3d_XnegYneg
//   ambient-light
a3DViewer->SetDefaultLights();
// activates all the lights defined in this viewer
a3DViewer->SetLightOn();
// set background color to black
a3DViewer->SetDefaultBackgroundColor(Quantity_NOC_BLACK);
}`

It notify: “OpenGl_khrplatform.h”: No such file or directory. But there is OpenGl_khrplatform.h in "opencascade/include". So I include OpenCASCADE_DIR still not work.
target_include_directories(${PROJECT_NAME} PUBLIC ${OpenCASCADE_DIR}
And there is value in OpenCASCADE_DIR, it points to "opencascade/include".

Could you please provide your reproducible project for me? Also, what is the version of the vcpkg you used?

Thanks for your reply! I could reproduce this issue in my side and I will fix it soon.

@SHIHUAMarryMe Could you please try the change of my PR? This time, there's no need to specifically install eigen3.

find_package(Eigen3 CONFIG REQUIRED) (Please remove)
.....
target_link_libraries(${PROJECT_NAME} PRIVATE TKBO TKBin TKCAF TKCDF
Eigen3::Eigen(please remove))

After modified the contents of CMakelists.txt file, please run below command:

Could you please send the vcpkg_installed/x64-windows/share/opencascade/OpenCASCADEConfig.cmake file to me? Thank you!

Please remove the opencascade:x64-windows and reinstall it again. I saw you still use the old files.

I usually delete it manually.

Have you applied the changes from my PR to your local? That PR hasn't been merged yet, so you'll need to do it manually.

I think below file should be changed. In my change, the port-version of opencascade has increased to 7.
{
  "$schema": "https://raw.githubusercontent.com/microsoft/vcpkg-tool/main/docs/vcpkg.schema.json",
  "name": "occtest",
  "version-string": "0.1.0",
  "dependencies": [
    {
      "name": "opencascade",
      "version>=": "7.6.2#6" (need change)
    }
  ],
  "builtin-baseline": "b51f391cd8f1f5a406b3baf9b014acff61702dc3"
}

Please waiting for the PR is merged.


DIY Tracker on LLCC68 doesn't start

Hi,
I recently built a diy tracker on esp32 and Ebyte E220 400M30S (LLCC68)
The problem is that it doesn't start, I keep getting this error:
Starting LoRa failed! State: -2
Everything is wired right
What is the possible solution?

What are your Lora settings? Sf12?

What are your Lora settings? Sf12?

I am using SF9

What are your Lora settings? Sf12?

SF9

power is on 18 (valid power units are 17, 20, 22... for your board max is 20). change it!

I changed it to 17 and it still doesn't start

the [RADIOLIB_ERR_CHIP_NOT_FOUND]   (-2) you experience is because it can recognize the Lora Module
please check wiring / pins

Wiring is good and it still doesn't start

did you solve this?

No, maybe Lora module is dead?

could you test it with other firmwares?

What other firmwares are there?

is there a meshtastic one for this ESP32 + LLCC68 board?

What other firmwares are there?

is there a meshtastic one for this ESP32 + LLCC68 board?

Yes, meshtastic starts on LLCC68 (RA-02SC) but not on E220 400M30S which is also on LLCC68 chip

I received confirmation of another Ham OP which used ESP32 DIY with LLCC68 board with success
So I would suggest to double check the connections, the esp32 boards and finally see if E220 boards is working

did you try latest update of tracker?


Language issue in Virtual Event Code of Conduct

Please check below link. This all should be in English language rather than a mixture of English and some other language.
https://github.com/microsoft/virtual-events/blob/main/virtual-event-code-of-conduct.md

Yes, this looks like it was intended to be a translation and wasn't saved well

@jennymevents

Thank you for letting me know! Fixed ASAP. Thank you!


Nothing is preventing the user to name scripts "Input" or "Camera" which are built-in Unity scripts

If you name your script "Camera" or "Input" (or ...), some strange behavior will occur. (Your script will look like it is an actual Camera, while it is just a script)
Naming the scripts like that should be prevented.

Ignore above reference... Caused by submit which also merged history of source blockly github project.


Wrong Golang address in setup script

Hi
GoLang installation has a problem in setup/setup_host.sh line 102:
First the link directory doesn't exist and it should be changed to https://go.dev/dl/${GO_BUILD}.tar.gz
Second on variable GO_VERSION you should add revision.
Thank you

Hi, thank you for letting me know!
Does #125 fix the problem?

Yes, thank you.


1-n many relation works implicitly without specifying the foreign key

I'm not sure we would consider this a bug but it certainly seems a bit strange that this is functional so I wanted to raise it here on GitHub. The following schema creates a correct 1-n relation in the DB without the foreign key being specified in the Prisma schema:
generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["nativeTypes"]
}

datasource db {
  provider = "postgresql"
  url      = "postgresql://nikolasburk:nikolasburk@localhost:5432/testdb1"
}

model user {
  id             String        @id @default(uuid()) @db.Uuid()
  email          String        @unique
  password       String
  createdAt      DateTime      @default(now()) @map("created_at")
  organization   organization? @relation(references: [id])
}
model organization {
  id        String   @id @default(uuid()) @db.Uuid()
  name      String
  createdAt DateTime @default(now()) @map("created_at")
  users     user[]
}

Running prisma migrate dev creates the following SQL:
-- CreateTable
CREATE TABLE "user" (
    "id" UUID NOT NULL,
    "email" TEXT NOT NULL,
    "first_name" TEXT NOT NULL,
    "last_name" TEXT,
    "password" TEXT NOT NULL,
    "created_at" TIMESTAMP(3) NOT NULL DEFAULT CURRENT_TIMESTAMP,
    "organizationId" UUID,

    PRIMARY KEY ("id")
);

-- CreateTable
CREATE TABLE "organization" (
    "id" UUID NOT NULL,
    "name" TEXT NOT NULL,
    "created_at" TIMESTAMP(3) NOT NULL DEFAULT CURRENT_TIMESTAMP,

    PRIMARY KEY ("id")
);

-- CreateIndex
CREATE UNIQUE INDEX "user.email_unique" ON "user"("email");

-- AddForeignKey
ALTER TABLE "user" ADD FOREIGN KEY ("organizationId") REFERENCES "organization"("id") ON DELETE SET NULL ON UPDATE CASCADE;

My understanding is that foreign keys should be made explicit in the Prisma schema and specified via references inside the @relation attribute. If the case above should be allowed, we probably should document this approach too.

I would also say this schema should be rejected by that validator. I have candidated this issue so that we can have a look into this in the next planning.

I would also say this schema should be rejected by that validator. I have candidated this issue so that we can have a look into this in the next planning.

Yah, I tend to agree. We should enforce the foreign key, it reduces the number of invalid states a schema can be in.
generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["nativeTypes"]
}

datasource db {
  provider = "postgresql"
  url      = "postgresql://nikolasburk:nikolasburk@localhost:5432/testdb1"
}

model user {
  id             String        @id @default(uuid()) @db.Uuid()
  email          String        @unique
  password       String
  createdAt      DateTime      @default(now()) @map("created_at")
- organization   organization? @relation(references: [id])
+ organization   organization? @relation(fields: [organizationId], references: [id])
+ organizationId String?
}
model organization {
  id        String   @id @default(uuid()) @db.Uuid()
  name      String
  createdAt DateTime @default(now()) @map("created_at")
  users     user[]
}

Agree, I stumbled over the logic for this in the datamodel code (that is making up the scalar field necessary to back the relation).  I also did not know we allowed this and had extra logic handling it. I find it weird that without re-introspecting you would not have the scalar field in your schema.

@pimeys will look into this at the same time as https://github.com/prisma/prisma/issues/5069

We should not run the standardizer on migration or query engine paths, but instead just error out. On prisma-fmt we should still run this, but also fix the problems what the code does in certain cases:
https://github.com/prisma/prisma/issues/5540

This needs planning and I'm re-candidating the ticket after having a meeting with the migrations team. We should change how and where we modify the schema. When it happens during the validation, we get all kinds of errors like this. Something for next sprint maybe?

@do4gr is currently solving this with the standardizer changes.

This should be solved by us splitting the parsing and formatting step here https://github.com/prisma/prisma-engines/pull/1662


Added missing fields in DeploymentEvent

Added StatusChangedAt, DeploymentID, EnvironmentSlug, and EnvironmentExternalURL in DeploymentEvent

@svanharmelen  can you please review this?


Adding a Github Actions workflow to run Jekyll build

This allows us to confirm that changes submitted to the site do not break the Jekyll build. I am not too familiar with Jekyll (looks simple enough) but this helps me feel more confident submitting changes in the future.
Next up will be adding some CI for linting and some small changes. I would like to work my way up to fixing the menu on mobile

Here is an example of a breaking change
https://github.com/ddaws/gutenbergsite/pull/1
And here is an example of a non-breaking change
https://github.com/ddaws/gutenbergsite/pull/2

Looks good to me. @gbnewby

Agreed - would you go ahead to merge into main? I'm not confident I know
how to do that correctly.
On Sun, Dec 1, 2024 at 8:07 AM Eric Hellman @.***>
wrote:

Looks good to me. @gbnewby https://github.com/gbnewby
—
Reply to this email directly, view it on GitHub
https://github.com/gutenbergtools/gutenbergsite/pull/41#issuecomment-2509807707,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFQRDLRTAIE5ORXCXF5HIPT2DMQ2VAVCNFSM6AAAAABSNDZBPGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBZHAYDONZQG4
.
You are receiving this because you were mentioned.Message ID:
@.***>

I pulled to the live website and regenerated with jekyll.
I didn't see any visible changes, and no errors were generated - as
expected. So, this looks like it worked as intended.
Thanks for this submission, Dawson.
Dr. Gregory B. Newby
Chief Executive and Director
Project Gutenberg Literary Archive Foundation www.gutenberg.org
A 501(c)(3) not-for-profit organization with EIN 64-6221541]
On Sun, Dec 1, 2024 at 11:39 AM Eric Hellman @.***>
wrote:

Merged #41 https://github.com/gutenbergtools/gutenbergsite/pull/41 into
master.
—
Reply to this email directly, view it on GitHub
https://github.com/gutenbergtools/gutenbergsite/pull/41#event-15485035363,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFQRDLQ45DBF7BP44RMAO2T2DNJX7AVCNFSM6AAAAABSNDZBPGVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJVGQ4DKMBTGUZTMMY
.
You are receiving this because you were mentioned.Message ID:
@.***>

I'm happy to contribute, and I hope to make more significant changes in the future 🙂


dont work on premise gitlab server

we have out gitlab server . we can get succesfully all files in tree but when click  created url is broken
https://gitlab.domain.com/xx/him/yy/-/blob/develop/Jenkinsfile
must be
https://gitlab.domain.com/xx/him/yy/blob/develop/Jenkinsfile

Hey @erayerdem ! Thank you for reporting the issue and hope you're finding SpanTree useful.
https://github.com/tavyandy97/span-tree/issues/37 This issue has been addressed. However, if switching on Compatibility Mode from the extension settings doesn't work, do let me know.
Do spread the word about SpanTree🌳

Hey @tavyandy97  ! thanks for your answer . its works  . good days


Deal with FP exceptions (x87, SSE) properly in exception handlers

... to avoid double fault

Solved this mostly by not using FP functionality in exception handlers


[RAC] - "Select" cannot disable focus on ListBoxItem hover.

Provide a general summary of the issue here
I am building a shadcn like select with an input inside.

So far so good, I just added a SearchInput inside the Popover of the Select. When the Select popover opens I focus the input by using the onOpenChange
However when i hover on the ListBoxItem the focus of the input disappears because it focuses on the  ListBoxItem instead.
https://github.com/user-attachments/assets/40f078aa-ee3a-4c7f-bf1c-8c5e0b4e7f02
If we look at normal ListBox with ListBoxItem that does not happen
https://react-spectrum.adobe.com/react-aria/ListBox.html
It happens only within a Select
https://react-spectrum.adobe.com/react-aria/Select.html
🤔 Expected Behavior?
Dont focus on the ListBoxItem on hover. Focus only on keyboard interactions or press.
😯 Current Behavior
ListBoxItem focuses on hover, making it impossible to keep the Input focused.
💁 Possible Solution
No response
🔦 Context
No response
🖥 Steps to Reproduce
This is default ListBoxItem behaviour within a select. On hover it will gain focus.
https://react-spectrum.adobe.com/react-aria/Select.html
If we look at normal ListBox with ListBoxItem that does not happen
https://react-spectrum.adobe.com/react-aria/ListBox.html
Version
"react-aria-components": "^1.3.1",
What browsers are you seeing the problem on?
Microsoft Edge
If other, please specify.
No response
What operating system are you using?
Windows 11
🧢 Your Company/Team
No response
🕷 Tracking Issue
No response

Instead of putting a search inside the Select, could you use a Combobox? That seems more in line with the pattern you're going for.
Putting a search inside a Select is not the intended interaction model for a Select and may hurt accessibility. For example, how does a keyboard user get to the search? or how do they leave the search field after they've entered their text?

@snowystinger
I did consider it, however there are some issues with the Combobox.
When the user clicks on the Combobox he has to click again to select the text in order to write something. Or he has to click on the text and then click backspace multiple times to clear the text. That is a bit unnecessary when a common solution with a search field exists.
I want a solution that github, gitlab and every other common website has:

Ah, that looks like a Popover with a TextField inside it that filters a ListBox. No need to use Select or Combobox, because it isn't really either of those. Especially with the Tabs, extra Button at the bottom, and a Popover title at the top.
You can swap the Trigger's text based on the item you select in the ListBox, and you can control the state of the ListBox so that it still has that option selected when the Popover is opened again.

ah ok got it! Thank you very much.
Also as you were talking about the combobox i did more digging and found out i can put the cursor at the start of the text each time the user clicks on the combobox which will work for me. Like here
https://react-select.com/home

@snowystinger Sorry to ask, but should I use a MenuTrigger or a DialogTrigger for this component?
I've tried using DialogTrigger however that does not set --trigger-width.
MenuTrigger on the other hand does set it correctly so is it fine if i go with that for this case?
Also since those components have no form intercations, i assume it is a bad idea to use such component within a form and i should fallback to using a combobox there, is that correct?

DialogTrigger would be the way to go.
MenuTrigger's --trigger-width is purely convenience, you can implement it yourself.
See https://github.com/adobe/react-spectrum/issues/4858#issuecomment-1671651194
You can make a hidden input that stores whatever information you need in the form. You shouldn't need us for that.


Nitro doesn't render loading indicator

Environment

Operating System: Darwin
Node Version:     v20.11.0
Nuxt Version:     2.17.3
CLI Version:      3.10.1
Nitro Version:    2.8.1
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      target, ssr, bridge, components, head, serverHandlers, devServerHandlers, devServer, typescript, nitro, buildModules, loadingIndicator
Runtime Modules:  -
Build Modules<EMAIL_ADDRESS>
Reproduction
if you enabled the nitro feature, the loadingIndicator or spaloadingtemplate are not rendered during the first page load in a non-ssr app.
Describe the bug
It's probably because of https://github.com/nuxt/bridge/blob/main/packages/bridge/src/runtime/nitro/renderer.ts#L106
Additional context
It doesn't matter if you have Vite enabled or not. In any case, your HTML file defined for loading is not loaded.
Logs
No response

Is there a solution for this?


Release KTX 1.9.14-b1

[x] GitHub release.
[x] Maven Central upload.

Maintenance release with official support for LibGDX 1.9.14 and a couple of small additions.

@Quillraven A stable release with your changes should now be available.


Accept list of directories / files as arguments

Codecov Report

Merging #209 (3884f60) into master (1633b6c) will decrease coverage by 0.63%.
The diff coverage is 35.00%.

:exclamation: Current head 3884f60 differs from pull request most recent head 7fee602. Consider uploading reports for the commit 7fee602 to get more accurate results

@@            Coverage Diff             @@
##           master     #209      +/-   ##
==========================================
- Coverage   93.96%   93.32%   -0.64%
==========================================
  Files          71       71
  Lines        1871     1887      +16
==========================================
+ Hits         1758     1761       +3
- Misses        113      126      +13

Impacted Files
Coverage Δ

lib/options.js
100.00% <ø> (ø)

lib/codenarc-factory.js
91.28% <35.00%> (-5.75%)
:arrow_down:

Continue to review full report at Codecov.

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


Zoom/pan not working on Windows 10 Touch in Chrome and Edge

The fix #6855 had some side effects on Windows 10 Touch in Chrome and Edge. In Chrome and Edge zoom scales page. Pan works in Edge, but does nothing in Chrome. Firefox is OK.

I think this is related with L.Browser.pointer that is now false where it used to be true on my chrome on windows (with no touch).

On my Windows 10 Surface PC - Chrome, Firefox and Edge are working on the touch screen with this fix, except when I detach the screen it is very hard to zoom in Firefox. I think this is a minor problem. I think most people are using Edge or Chrome on touch screen. I could not find out how to fix this.

Same problem, Chromium 78 on Ubuntu Linux 18.04. Zooming via touch gestures works with Leaflet 1.5.1, but not with 1.6.0. L.Browser.pointer is false on 1.6.
Touch gestures work with Firefox 70 with Leaflet 1.5.1 and 1.6.0.

Touch events on Chrome desktop (79.0.3945.79) not working here (Leaflet 1.6.0). I think it's something to do with how Leaflet internally checks if the browser supports touch. L.Browser.touch=undefined for me on a Windows 10 Surface Pro.

Still affected by this in Chrome using Leaflet 1.6.0, any idea when will it be fixed? Or other workarounds since L.Browser.touch is readonly so cannot be set manually.

Dirty hack: set window.ontouchstart="true" before loading Leaflet.
But better go and up-vote #6977

I had manually patch Leaflet 1.7.1 with my fix. Other fix did not solve this problem.

I had manually patch Leaflet 1.7.1 with my fix. Other fix did not solve this problem.

What is 'your fix'?

I had manually patch Leaflet 1.7.1 with my fix. Other fix did not solve this problem.

What is 'your fix'?

Zoom/pan not working on Windows 10 Touch in Chrome and Edge
"...|| Browser.edge" seems not necessary anymore

@sveine
I suppose this will help too: https://github.com/Leaflet/Leaflet/pull/7029/commits/7187e12bf5c4a4e1ab096bcf41f1850cddf5e6fd

@sveine
I suppose this will help too: 7187e12

Yes it worked!
A side effect of "touch=true" setting is that the touch-panel is slow on pinch/unpinch zoom.

A side effect of "touch=true" setting is that the touch-panel is slow on pinch/unpinch zoom.

Could you provide more details?
And have you applied this single commit, or whole #7029?

A side effect of "touch=true" setting is that the touch-panel is slow on pinch/unpinch zoom.

Could you provide more details?
And have you applied this single commit, or whole #7029?

Only replaced line 1911 in leaflet-src.js 1.7.1 with
var touch = !window.L_NO_TOUCH && (pointer || 'ontouchstart' in window || window.TouchEvent);
(If you has a patched leaflet-src.js I can test)

A side effect of "touch=true" setting is that the touch-panel is slow on pinch/unpinch zoom.

Could you provide more details?
And have you applied this single commit, or whole #7029?

The touchpad zooms on integer levels with touch=false, decimal with touch=true. With touch=true a two finger zoom in/out is OK on fast finger move. Tried Google Maps. It is very smooth on both touchpad, screen zooming and mouse - so it is somehow possible to make it work.

The touchpad zooms on integer levels with touch=false, decimal with touch=true. With touch=true a two finger zoom in/out is OK on fast finger move. Tried Google Maps. It is very smooth on both touchpad, screen zooming and mouse - so it is somehow possible to make it work.

That are valuable details. Could you open separate issue for this problem?

(If you has a patched leaflet-src.js I can test)

Sure I have: https://gist.githack.com/johnd0e/3ad393c73b12b24af7e947711a87b7a4/raw/leaflet-src.js
And here are 2 test pages (for unrelated issues) but with same "patched" leaflet:
https://gist.githack.com/johnd0e/3ad393c73b12b24af7e947711a87b7a4/raw/issue-6632.html
https://gist.githack.com/johnd0e/3ad393c73b12b24af7e947711a87b7a4/raw/issue-5969.html

The leaflet-src.js her works fine.
You do not have zoomSnap: 0 in your example. Setting this to 0 is a must - not to make map jump to next/prev zoom on screen zooming. When zoomSnap is set, I think touchpad zoom should have a factor based on zoomSnap.

You do not have zoomSnap: 0 in your example. Setting this to 0 is a must - not to make map jump to next/prev zoom on screen zooming. When zoomSnap is set, I think touchpad zoom should have a factor based on zoomSnap.

Are we already talking about #7476?

Are we already talking about #7476?

Mostly for #7476. But testing touch in your pages without zoomSnap:0 may not be relevant. https://github.com/Leaflet/Leaflet/issues/7476#issuecomment-783531470

Here is sample with  zoomSnap:0;
https://gist.githack.com/johnd0e/3ad393c73b12b24af7e947711a87b7a4/raw/issue-7476.html

Here is sample with  zoomSnap:0;
https://gist.githack.com/johnd0e/3ad393c73b12b24af7e947711a87b7a4/raw/issue-7476.html

It's working :-)

It's working :-)

Could you describe which of mentioned here issue are fixed there?

It's working :-)

Could you describe which of mentioned here issues are fixed there?

Zoom does not scale the page, but zooms the map

That is weird anyway, because both Chrome and Firefox support pointer events, so neither your, nor your fix should not change anything: when L.Browser.pointer is true - L.Browser.touch gets true as well.
So:

Make sure that you are using latest leaflet (vanilla, without any fixes)
Open dev console and check both values

That is weird anyway, because both Chrome and Firefox support pointer events, so neither your, nor your fix should not change anything: when L.Browser.pointer is true - L.Browser.touch gets true as well.
So:
1. Make sure that you are using latest leaflet (vanilla, without any fixes)

2. Open dev console and check both values

Read the first comment in this issue.

Read the first comment in this issue.

Mentioned there bug was fixed in #7010 (by me).
So if you still can observe same (wrong) behavior with latest leaflet - it is different bug.

Read the first comment in this issue.

Mentioned there bug was fixed in #7010 (by me).
So if you still can observe same (wrong) behavior with latest leaflet - it is different bug.

Long tap on iOS is not working 1.7.1.
By setting var pointer = !webkit && !!(window.PointerEvent || msPointer);, long tap is working.
and then by setting:
var touch = !window.L_NO_TOUCH && (pointer || 'ontouchstart' in window || navigator.maxTouchPoints > 0 || navigator.msMaxTouchPoints > 0 ||
(window.DocumentTouch && document instanceof window.DocumentTouch));
Zoom/pan is working on Windows 10 Touch in Chrome and Edge"

Long tap on iOS is not working 1.7.1.

You can test #7026 and/or #7029.

Can you please create a page for testing?

7026: there is test page in description
7029: see upper post

7026: there is test page in description
7029: see upper post

They are not working. Element on map is selected. Your test page the '+' sign is selected (contextmenu event is triggered)

contextmenu event is triggered == they are working (7026)
And as far as I know, after 7029 + sign should not be selected

contextmenu event is triggered == they are working (7026)
And as far as I know, after 7029 + sign should not be selected

https://user-images.githubusercontent.com/367125/110366946-51e61a80-8047-11eb-84ff-4b3e79c30a75.mp4

Have you followed the link that was mentioned?
I have no gist where both 7026 and 7029 are applied, that's why you still observe + selection.

I have no gist where both 7026 and 7029 are applied, that's why you still observe + selection.
OK! I can test if a gist is created

https://gist.githack.com/johnd0e/eea9cf6cab9070600dae5397fcfe06be/raw/test.html

Same as for https://github.com/Leaflet/Leaflet/issues/6896#issuecomment-792987541.
I cleared cache, tried for Safari, Chrome and Edge (for iOS/iPhone). iOS 1.4, iPhone 12

Could check L.Browser.touchNative value?

Could check L.Browser.touchNative value?

L.Browser.touchNative = true

Ok, try one more time.

Ok, try one more time.


reason-cli '.tar.gz' NPM package errors on NPM update

Problem:
NPM v5.4.2 doesn't handle '.tar.gz' package format properly, on update errors and stops the update, might interfere with other extraneous packages too (but I didn't test it yet) :
On MacOS:

MacBook-Pro:~ intj$ npm -g update
npm ERR! code E404
npm ERR! 404 Registry returned 404 for GET on https://registry.npmjs.org/reason-cli
npm ERR! 404
npm ERR! 404 'reason-cli' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
npm ERR!  /Users/intj/.npm/_logs/2017-10-03T10_14_41_827Z-debug.log
MacBook-Pro:~ intj$

On Ubuntu:

intj@intjDesktop:~ $ npm -g update
npm ERR! code E404
npm ERR! 404 Registry returned 404 for GET on https://registry.npmjs.org/reason-cli
npm ERR! 404
npm ERR! 404 'reason-cli' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/intj/.npm/_logs/2017-10-03T12_35_58_630Z-debug.log
intj@intjDesktop:~ $

Possible fix:
1 - Publish 'reason-cli' NPM package
2 - Deprecate '.tar.gz' package format

I've started to try to solve this one. On discord @andreypopp suggested I create a new package that could be published to npm. Essentially I'd like it to be a script that installs the right tarball for your platform. I don't have a lot of experience on the node platform (Reason is the whole reason I'm getting involved), so any suggestions or PRs would be appreciated.
The code is here: https://github.com/zploskey/reason-cli-bin

That repo is now a working prototype (for me at least). Tested on Linux. Could use a mac tester.

That repo is now a working prototype (for me at least). Tested on Linux. Could use a mac tester.

@zploskey well, doesn't seem so simple anymore for 3.0.0 since the move to esy.

Hopefully the move to esy actually solves this. I think it still needs some work, though.

reason-cli-bin is a good idea. Did you model it after flow-bin? I'm curios about what the best way to do this is. It's generally good for npm packages to not download things on postinstall, but I don't know of any other way. I don't think npm/yarn have any way to dynamically compute a package dependency based on platform. If it did I would express a dependency as something like:
"dependencies": {
  "reason-cli": "platform === 'darwin'<EMAIL_ADDRESS><EMAIL_ADDRESS>: 'null'"
}

Is the original issue still a problem?

Yes, the original issue is still a problem. Npm doesn't handle .tar.gz packages gracefully on upgrades and fails affecting other packages.

Give it a try. Install reason-cli and try to upgrade npm globally and see how it goes.

It looks like since installing the 3.0.0 linux tarball I can do npm update -g with receiving an error as shown in the first post. It just downloaded a few updates and worked just fine. Unless this is somehow still a problem for anyone else, this can probably be closed.

reason-cli-bin is a good idea. Did you model it after flow-bin?

Sort of. I looked up other npm packages that needed to distribute binaries and saw that they used -bin in their names so I followed suit.
Having a way to download pre-compiled packages for your architecture is really useful and clearly something that JS is going to need more of in the future. Python solved this problem a few years ago with what they call wheel binary packages (.whl) because having the packages be compiled on demand was too error-prone, and nearly impossible to get right on Windows. It would be great if we could get something like that to be adopted. It might be good enough for the package managers or repositories to agree on a mechanism for selecting the right binary package by architecture in the request to the repository, and the package manager could provide an override if the user wanted to get binary dependencies for another architecture in order to deploy somewhere else.
The way you suggest with substituting $platform in the name seems reasonable and fits within what's already there in package.json. If the other package managers aren't willing to do it, maybe esy should do it. If it gains traction the others may adopt it too.

" with receiving an error as "
Did you mean without receiving an error?

Problem persists but NPM packages can still be upgraded manually/individually and without errors if done this way. It affects global upgrades only.
Newcomers might be confused on this until they understand this. Leave this open as a reminder of this problem.

@jordwalke Yes, it did not give me an error this last time I tried. Seems to still be a problem for some.

@jordwalke confirming 3.0.0 doesn't make the issue go away.


changing the room icon in #riot caused android's room info to forget it had an icon at all :(

I don't reproduce your issue.
It is very difficult to track this issue without bug report.


Can't run go get

Running go get returns with error
go get -u github.com/go-redis/redis
cannot find package "go.opentelemetry.io/otel/api/trace" in any of:
        /usr/local/opt/go/libexec/src/go.opentelemetry.io/otel/api/trace (from $GOROOT)
        /Users/user/go/src/go.opentelemetry.io/otel/api/trace (from $GOPATH)

Please check readme.


Update postgresql.conf for pg11

If wal_level = minimal, max_wal_senders=0 needs to be set as well

Thanks!


Add Resource Offer Operator

Description
This pr adds an operator over the ResourceOffer CRs. This operator will substitute the advertisement operator in a future pr.
Ref. #573
How Has This Been Tested?

[x] add unit test

/merge


Issue with RKMIMETypeTextXML on mapping ?

Hello,
I already explain my problem here:
http://stackoverflow.com/questions/14876495/restkit-response-in-text-xml
So far I have this:
I have a WS that return a plist.
I am using Restkit and I would like to map the response.
So first I initilialize my ObjectManager like this:
[RKObjectManager managerWithBaseURL:[NSURL URLWithString:ROOT_URL]];

I accept the text/xml:
[[RKObjectManager sharedManager] setRequestSerializationMIMEType:RKMIMETypeTextXML];

And I launch my request:
[[RKObjectManager sharedManager] getObjectsAtPath:@"/foo/foo" parameters:nil success:^(RKObjectRequestOperation *operation, RKMappingResult *mappingResult) {
    NSLog(@"Loading mapping result: %@", mappingResult);
} failure:^(RKObjectRequestOperation *operation, NSError *error) {
    NSLog(@"Fail with error %@", [error userInfo]);
}];

Finally I get this error:
NSLocalizedDescription=Expected content type {( "application/x-www-form-urlencoded", "application/json" )}, got text/xml,

What am I doing wrong? Is-it an issue ?

@blakewatters I am trying to setup xml serialization using the external module.
I was reading the instructions for setting up RKXMLReaderSerialization to parse xml response.
[RKMIMETypeSerialization registerClass:[RKXMLReaderSerialization class] forMIMEType:@"application/xml"];
[objectManager setAcceptHeaderWithMIMEType:RKMIMETypeTextXML];
Even this was not working. Getting a similar error as above. I understand this has been moved to the 1.0 milestone, but shouldn't plugging in the RKXMLReaderSerialization help?
NSLocalizedDescription=Expected content type {(
"application/x-www-form-urlencoded",
"application/json",
"application/xml"
)}, got text/xml}

@deepumukundan as the message says, you'll need to at the proper content type for the XMLSerialization.


Lints should not break compilation of dependencies in cargo

It's very unfortunate if changing lints (e.g., adding a new lint, or making an existing lint stronger and better, or removing a lint that's not very useful) breaks compatibility guarantees. Moreover, lints are only really useful for the current crate you're working on, not for your dependencies. We need to adopt some scheme to avoid this. My rough proposal goes like this:

All stable code can use any lint that it wants to.
We should add an option to rustc that caps all lints at warn.
Cargo should supply this option when building dependencies or installing software

The idea here is that if I am using somebody's package, I don't want to have compilation fail because we added a new lint in the meantime. But if I am editing my own source code, I absolutely do want compilation to fail. I feel like this bridges the gap and avoids the problem of -Wall not being able to refer to "all".

:+1: I've resorted to #[cfg_attr(test, deny(warnings))] to my crates. However, this means it is possible to accidentally let some things slip through, such as dead code which is used by tests.

:+1: Agreed, this is pretty important to have. The example with -Wall is a good reminder of this issue.

triage: I-nominated
recommend P-high/1.1

oops, wrong repo!

:+1: I think this makes a lot of sense. Heck, I'm not really sure if we should even use warnings for dependencies by default. Unless I'm willing to submit a PR to my dependency, I don't care whether it triggers lints internally. This could perhaps be some sort of configuration, e.g. in ~/.cargo/config, that determines whether dependencies should be listed, with the default being allow.

A bit of extra perspective from the C++ world (which I inhabit): it's common to include library headers with the -isystem flag instead of -I to prevent compiler warnings from third-party code breaking builds that also use -Werror. Even for builds without -Werror, nobody wants to see warnings from code that's not theirs. It's just noise.
So cargo being smart about this without extra configuration from the user would be seen as a really nice (albeit small) improvement over the C++ experience.
It would be great to have this sooner rather than later, because it would give a nice first impression for all the C++ devs that will descend upon Rust when it hits 1.0.

Even for builds without -Werror, nobody wants to see warnings from code that's not theirs. It's just noise

Yep. That's precisely what we did in Cargo. Would be nice for Cargo to also be able to pass a flag to rustc that says "ignore denys" for the same reason.


Simplify Closures

Currently, most operators are implemented as such:
public static IEnumerator<TSource> Operator<TSource>(this IEnumerable<TSource> source, ...)
{
   // guard statements
   return _();

   _()
   {
      yield return source.First();
      yield break;
   }
}

A better implementation would be the following:
public static IEnumerator<TSource> Operator<TSource>(this IEnumerable<TSource> source, ...)
{
   // guard statements
   return _(source, ...);

   static _(IEnumerable<TSource> source, ...)
   {
      yield return source.First();
      yield break;
   }
}

With the current implementation, the host method must create a closure class before even doing guard statements, copy parameters, and then call a method on that closure class. This means that there are two closure classes: one for the parameters, and one for the enumerator.
Switching to passing the parameters into the iterator method means that only one closure class has to be created, the one for the enumerator; the parameters will be held by that class. This should simplify and improve the IL, the JIT, and the output JIT-ted code.

Thanks for bringing this up and shame about the closure because it means reverting all of #290. The local functions really made things pleasant (for all the reasons listed in #290), but I agree that inducing a closure is not worth the cost. In fact, if the local function is going to be static, then it might as well be a private method again.

if the local function is going to be static, then it might as well be a private method again.

@atifaziz the function being local has other benefits which are significant, such as being scoped only to that function instead of being callable by the entire class.
I don't think you should make them private methods again for that reason.
@viceroypenguin do you mind if I ask a related question here? Would this also apply to an async method that is split due to validation concerns like this?
public Task DoStuffAsync(string argument, CancellationToken cancellationToken)
{
    ArgumentNullException.ThrowIfNull(argument);
    return DoStuffAsync();

    async Task DoStuffAsync()
    {
        await SomethingElseAsync(cancellationToken);
    }
}

Would it have similar benefits here to make the local function static if possible?

@julealgon Yes, it does make a difference for async methods. See two comparisons here:

closure: https://sharplab.io/#v2:D4AQTAjAsAUCAMACEEB0AVAFgJwKYEMATASwDsBzAblgWQgFZqYaBmZMRAYUQG9ZEByNiABsiACIB7AMoAXAK4AzRQEEAzgE9SAYwAUKJPmzl5AW1ylZAGi74duADYP8s4pNLpJAawuJtd7UdnV3dPH1IASn5BPhhBeMQVYzMLWQA5eScAUQAPQIAHENIMHEkAdwBJRQynXSMTc0sIpgTBEAB2CRkFZXUtPWbYaNaQAA5kEQAeAwA+LrklVU0dXSi41t5hjYEQAE4J1HFHfA1denh4QfXtnc76lMsWjYBfLdfmGGegA=
argument: https://sharplab.io/#v2:D4AQTAjAsAUCAMACEEB0AVAFgJwKYEMATASwDsBzAblgWQgFZqYaBmZMRAYUQG9ZEByNiABsiACIB7AMoAXAK4AzRQEEAzgE9SAYwAUKJPmzl5AW1ylZAGi74duADYP8s4pNLpJAawuJtd7UdnV3dPH1IASn5BPhhBeMQVYzMLWQA5eScAUQAPQIAHENIMHEkAdwBJRQynXSMTc0sIpgTBEAB2CRkFZXUtPXqUpqZo1pAADmQRAB4DAD4uuSVVTR19CENkxtkouNbeUf2BEABOKdRxR3wNXXp4eGbDo47EQe2W/YBfQ+/mGE+gA=

Specifically, the closure version will create a new class and allocate an instance of it for use within the local method. However, the argument version will only create a struct and use it locally.


[Test-Proxy] Need support for Json Path Sanitizers

In order to migrate the .NET Test Framework to use the Test Proxy, we will need a way to add JSON path sanitizers.
The support for this is in RecordedTestSanitizer. These sanitizers allow you to use a JSON path expression to select JSON elements within the request body.
It would be great if there was a way to just serialize the entire RecordedTestSanitizer and recreate it on the other side, but at minimum, we'd need a way to send this data over, and for the RecordedTestSanitizer on the Test-Proxy side to be updated to use it.

/cc @scbedd @pakrym

This is already supported in the BodyKeySanitizer.


Use new HTTPClient class

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

Project coverage is 100.00%. Comparing base (8c95785) to head (bcb2c8c).

Additional details and impacted files
@@            Coverage Diff             @@
##              main        #7    +/-   ##
==========================================
  Coverage   100.00%   100.00%
==========================================
  Files           29        29
  Lines          617       763   +146
==========================================
+ Hits           617       763   +146

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


Toggle calendar

How can I open and close the calendar with one button?
There is a new method "toggleMenu", but it only opens the calendar if it was closed. If you use the "openMenu" and "closeMenu" methods, the situation is the same.
https://stackblitz.com/edit/vuepic-vue-datepicker-tmdwvz?file=src%2Fcomponents%2FPlayground.vue

As answered on #662, you are doing a click away on the menu. You can override a default one like specified here


Update aws-core, http-client-spi, ... to 2.17.285

Updates

software.amazon.awssdk:aws-core
software.amazon.awssdk:http-client-spi
software.amazon.awssdk:netty-nio-client

from 2.17.280 to 2.17.285.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "software.amazon.awssdk" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #290.


Upgrade to Rails 6

Rails 6 is officially out!
Let's do this!

The Rails Guides has a nice upgrading guide that will likely be helpful with this: https://edgeguides.rubyonrails.org/upgrading_ruby_on_rails.html#upgrading-from-rails-5-2-to-rails-6-0

@marclerodrigues Yeah, go for it!

I'm giving this a shot, trying to keep out most of the unnecessary default changes inflicted by rails app:update to keep the scope of reviewing such a large change more manageable.


No such file or directory    #include "ocs2_msgs/msg/detail/mpc_target_trajectories__type_support.hpp"

ros2 humble Ubuntu 22.04 meet the following missing file error ${}_type_support.hpp file doesn't created.
-- stderr: ocs2_ros_interfaces
In file included from /home/nuc/ocs2_ws/src/ocs2_ros2/robotics/ocs2_ros_interfaces/include/ocs2_ros_interfaces/command/TargetTrajectoriesRosPublisher.h:34,
from /home/nuc/ocs2_ws/src/ocs2_ros2/robotics/ocs2_ros_interfaces/include/ocs2_ros_interfaces/command/TargetTrajectoriesKeyboardPublisher.h:36,
from /home/nuc/ocs2_ws/src/ocs2_ros2/robotics/ocs2_ros_interfaces/src/command/TargetTrajectoriesKeyboardPublisher.cpp:30:
/home/nuc/ocs2_ws/install/ocs2_msgs/include/ocs2_msgs/ocs2_msgs/msg/mpc_target_trajectories.hpp:10:10: fatal error: ocs2_msgs/msg/detail/mpc_target_trajectories__type_support.hpp: No such file or directory
10 | #include "ocs2_msgs/msg/detail/mpc_target_trajectories__type_support.hpp"
|          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.

Never met this before, maybe you can try to check the ROS2 and colcon environment.


crystal play when 8080 is already in use reports 'Error: you've found a bug in the Crystal compiler.'

When running from the command line
crystal play

if the port 8080 is already in use Crystal prints the following output:
bind: Address in use (Errno)
  from ???
  from ???
  from ???
  from ???
  from ???
  from ???
Error: you've found a bug in the Crystal compiler. Please open an issue, including source code that will allow us to reproduce the bug: https://github.com/crystal-lang/crystal/issues

Steps to reproduce

Use the port 8080 on localhost with another process
Run crystal play from the command line

Additional informations

Crystal version:

Crystal 0.31.1 [0e2e1d067] (2019-09-30)

LLVM: 8.0.0
Default target: x86_64-unknown-linux-gnu

OS: Fedora 30 Workstation
kernel: 5.2.18-200.fc30.x86_64

What do you think the expected action should be? I think the error message makes it pretty clear and per the docs (crystal play --help) you can specify a different port when starting. The only thing I think could be argued is that the "you have found a bug" message could be removed.

Exactly. It's not a compiler bug and we don't need a stack trace.

It's actually a bit recursive:

it's a bug
the bug is that it says it's a bug

I'd like to take this on, but I have a few discussion points:
Currently, the playground is its own class that is fed arguments from a wrapper that parses the command line (good). However, the only way for the playground to exit is from that wrapper if an exception is thrown from the Playground class or the user interrupts the playground (Ctl+C). I think the most elegant solution would be to exit 1 from the Playground class if the port is already in use, but that would mean that a class is exiting the application and not the wrapper. Is this OK?
If not, I will have to create a new type of exception and then catch that exception in the wrapper class to cleanly exit without giving a stack trace. This is OK, just a little bit more work I think.

I think you just need:
begin
  playground.run
rescue Errno
  # Show some error
  exit 1
end

Yeah, that was the direction I think I was heading next, just need to make sure to put the right output depending on the error. I believe that port or address in use isn't "exceptional" and should print an error message (no stacktrace) but other exceptions should print full stacktrace because they are truly "exceptional." I'll take this one and make a PR.

What other exceptions? I think other exceptions are already caught, and they will show the "Bug found" message shown in this GitHub issue.

@rvictory rescue Errno only rescues Errno and all Errno exceptions raised by playground.run are (most likely) not compiler errors.

Why is this still open? Obviously the compiler should throw a stackdump if it cannot open a regular TCP/IP port?
(Yes, the crystal play script brought me here)

@hholst80 Feel free to send a PR. Thank you!

Na, keep it open it's a great way to measure new user churn. 🤣


Question about checkpoint.Capped behavior

I've been reading through the code for the checkpoint.Capped implementation to understand how the checkpoint_limit configuration worked on the kafka input and I think I found some undesirable behavior.
In kafka, compacted topics can have some pretty wild differences in offsets from one message to the next, but I don't think checkpoint_limit takes this into account, which can break batching.
Here's a test that fails where I would expect checkpoint_limit: 2 to allow two "sequential" offsets 1000 and 2000 through:
func TestBigJumpsMore(t *testing.T) {
	c := NewCapped(2)
	assert.Equal(t, 0, c.Highest())

	ctx, done := context.WithTimeout(context.Background(), time.Second*5)
	defer done()

	require.NoError(t, c.Track(ctx, 1000))
	assert.Equal(t, 0, c.Highest())

	require.NoError(t, c.Track(ctx, 2000))
	assert.Equal(t, 0, c.Highest())

	v, err := c.Resolve(1000)
	require.NoError(t, err)
	assert.Equal(t, 1000, v)
	assert.Equal(t, 1000, c.Highest())

	v, err = c.Resolve(2000)
	require.NoError(t, err)
	assert.Equal(t, 2000, v)
	assert.Equal(t, 2000, c.Highest())
}

I just want to make sure this behavior isn't desired before I attempt a workaround.

Hey @greysond, yeah this ought to be expanded to allow for any range between sequential offsets. It might need a bit of a refactor, it's been a while since I wrote the checkpointer but I probably did it this way for a reason. The only other component that uses this is the aws_kinesis input, but it won't be impacted since it has a (slightly gross) wrapper around this to account for the fact that the shard iterators are arbitrarily long numbers.

Mind if I take a crack at it? And how would you feel about a linked-list implementation?

Go for it, any implementation is fine but keep an eye on the benchmarks. It doesn't need to be super efficient but it'd be nice not too regress too far.

Should it be assumed that Capped.Track(ctx, offset) can be called from more than one goroutine? If not and there will only ever be one goroutine waiting on that call (like a sarama partition consumer), I have a much simpler solution.

Yes, but Resolve can be called from any number of goroutines. Although I wouldn't be opposed to breaking the mutex out when needed.

Solution merged: https://github.com/Jeffail/benthos/commit/7cccc3002b60b71c6efd316810f15af458ff6285


Update Seldon Upstream Operator to 1.5.0

Signed-off-by: Clive Cox<EMAIL_ADDRESS>Thanks submitting your Operator. Please check below list before you create your Pull Request.

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

Updates to existing Operators

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

@cliveseldon We are moving to github actions. Can you please rebase to latest master? Thanks


Ability to show full source code of the original component on the component page

Even better if we'll support multiple files. E.g. Comp.js, Comp.styl, Comp.demo.js.


AttributeError: type object 'IteratorBase' has no attribute 'from_structure'

ｔｅｎｓｏｒｆｌｏｗ　２．５

`
import tensorflow as tf

training_dataset = tf.data.Dataset.range(100).map(
    lambda x: x + tf.random.uniform([], -10, 10, tf.int64))
validation_dataset = tf.data.Dataset.range(50)

# A reinitializable iterator is defined by its structure. We could use the
# `output_types` and `output_shapes` properties of either `training_dataset`
# or `validation_dataset` here, because they are compatible.
iterator = tf.data.Iterator.from_structure(training_dataset.output_types,
                                           training_dataset.output_shapes)
next_element = iterator.get_next()

training_init_op = iterator.make_initializer(training_dataset)
validation_init_op = iterator.make_initializer(validation_dataset)

# Run 20 epochs in which the training dataset is traversed, followed by the
# validation dataset.
for _ in range(20):
    # Initialize an iterator over the training dataset.
    sess.run(training_init_op)
    for _ in range(100):
        sess.run(next_element)

    # Initialize an iterator over the validation dataset.
    sess.run(validation_init_op)
    for _ in range(50):
        sess.run(next_element)`

Please tell me how to revise this piece of code and let it run with tf 2.5? The sooner the better, thanks a million.

@saikumarchalla @ry @jmhodges @eggie5

@saikumarchalla Is there any update?

@Saduf2019 Any progress yet

@Saduf2019 Any progress yet

＠Saduf2019 Don't you think this is an important issue that should be fixed immediately. I've issued this for over three weeks, why there's no reply at all.

Hi! @sjtusmartboy !Was able to resolve the issue with TF v2.5 ,  I changed the code using migration document . find the gist here Thanks!

@mohantym thanks for your reply. If we're using eager mode, then how do we use tf.data.Iterator

@mohantym thanks for your reply. If we're using eager mode, then how do we use tf.data.Iterator

Hi @sjtusmartboy ,
We see that you are using old version of Tensorflow which is officially considered as end of life, We recommend that you upgrade code base to 2.6 version and let us know if the issue still persists in newer versions .Please open a new issue in case you face any errors, we will get you the right help .Thanks!

ｔｅｎｓｏｒｆｌｏｗ　２．５
`
import tensorflow as tf
training_dataset = tf.data.Dataset.range(100).map(
lambda x: x + tf.random.uniform([], -10, 10, tf.int64))
validation_dataset = tf.data.Dataset.range(50)
A reinitializable iterator is defined by its structure. We could use the
output_types and output_shapes properties of either training_dataset
or validation_dataset here, because they are compatible.
iterator = tf.data.Iterator.from_structure(training_dataset.output_types,
training_dataset.output_shapes)
next_element = iterator.get_next()
training_init_op = iterator.make_initializer(training_dataset)
validation_init_op = iterator.make_initializer(validation_dataset)
Run 20 epochs in which the training dataset is traversed, followed by the
validation dataset.
for _ in range(20):
# Initialize an iterator over the training dataset.
sess.run(training_init_op)
for _ in range(100):
sess.run(next_element)
# Initialize an iterator over the validation dataset.
sess.run(validation_init_op)
for _ in range(50):
    sess.run(next_element)`

问题已经解决。出现这个问题是因为TensorFlow2.X版本中，IteratorBase这个对象对应的类，没有封装from_structure这个属性。安装TensorFlow1.x版本即可解决这个问题。
The problem has been solved. This problem occurs because in TensorFlow2.X, the class corresponding to the IteratorBase object does not encapsulate the from_structure attribute. Install the TensorFlow1.x version to resolve this issue.

ｔｅｎｓｏｒｆｌｏｗ　２．５

`
import tensorflow as tf

training_dataset = tf.data.Dataset.range(100).map(
    lambda x: x + tf.random.uniform([], -10, 10, tf.int64))
validation_dataset = tf.data.Dataset.range(50)

# A reinitializable iterator is defined by its structure. We could use the
# `output_types` and `output_shapes` properties of either `training_dataset`
# or `validation_dataset` here, because they are compatible.
iterator = tf.data.Iterator.from_structure(training_dataset.output_types,
                                           training_dataset.output_shapes)
next_element = iterator.get_next()

training_init_op = iterator.make_initializer(training_dataset)
validation_init_op = iterator.make_initializer(validation_dataset)

# Run 20 epochs in which the training dataset is traversed, followed by the
# validation dataset.
for _ in range(20):
    # Initialize an iterator over the training dataset.
    sess.run(training_init_op)
    for _ in range(100):
        sess.run(next_element)

    # Initialize an iterator over the validation dataset.
    sess.run(validation_init_op)
    for _ in range(50):
        sess.run(next_element)`

问题已经解决。出现这个问题是因为TensorFlow2.X版本中，IteratorBase这个对象对应的类，没有封装from_structure这个属性。安装TensorFlow1.x版本即可解决这个问题。
The problem has been solved. This problem occurs because in TensorFlow2.X, the class corresponding to the IteratorBase object does not encapsulate the from_structure attribute. Install the TensorFlow1.x version to resolve this issue.


processors for training meta model

❓ Questions and Help
I am experiencing the following errors when trying out the DDG meta model:
[31550:MainThread](2022-01-17 22:14:54,658) ERROR - qlib.workflow - [utils.py:38] - An exception has been raised[ValueError: Input contains NaN, infinity or a value too large for dtype('float32').].
  File "workflow.py", line 261, in <module>
    fire.Fire(DDGDA)
  File "/home/xxxxxxxxxx/.venv/lib/python3.8/site-packages/fire-0.4.0-py3.8.egg/fire/core.py", line 141, in Fire
    component_trace = _Fire(component, args, parsed_flag_args, context, name)
  File "/home/xxxxxxxxxx/.venv/lib/python3.8/site-packages/fire-0.4.0-py3.8.egg/fire/core.py", line 466, in _Fire
    component, remaining_args = _CallAndUpdateTrace(
  File "/home/xxxxxxxxxx/.venv/lib/python3.8/site-packages/fire-0.4.0-py3.8.egg/fire/core.py", line 681, in _CallAndUpdateTrace
    component = fn(*varargs, **kwargs)
  File "workflow.py", line 250, in run_all
    self.dump_meta_ipt()
  File "workflow.py", line 123, in dump_meta_ipt
    internal_data.setup(trainer=TrainerR)
  File "/home/xxxxxxxxxx/.venv/lib/python3.8/site-packages/pyqlib-<IP_ADDRESS>-py3.8-linux-x86_64.egg/qlib/contrib/meta/data_selection/dataset.py", line 82, in setup
    trainer.train(gen_task)
  File "/home/xxxxxxxxxx/.venv/lib/python3.8/site-packages/pyqlib-<IP_ADDRESS>-py3.8-linux-x86_64.egg/qlib/model/trainer.py", line 252, in train
    rec = train_func(task, experiment_name, **kwargs)
  File "/home/xxxxxxxxxx/.venv/lib/python3.8/site-packages/pyqlib-<IP_ADDRESS>-py3.8-linux-x86_64.egg/qlib/model/trainer.py", line 122, in task_train
    _exe_task(task_config)
  File "/home/xxxxxxxxxx/.venv/lib/python3.8/site-packages/pyqlib-<IP_ADDRESS>-py3.8-linux-x86_64.egg/qlib/model/trainer.py", line 44, in _exe_task
    auto_filter_kwargs(model.fit)(dataset, reweighter=reweighter)
  File "/home/xxxxxxxxxx/.venv/lib/python3.8/site-packages/pyqlib-<IP_ADDRESS>-py3.8-linux-x86_64.egg/qlib/utils/__init__.py", line 847, in _func
    return func(*args, **new_kwargs)
  File "/home/xxxxxxxxxx/.venv/lib/python3.8/site-packages/pyqlib-<IP_ADDRESS>-py3.8-linux-x86_64.egg/qlib/contrib/model/linear.py", line 65, in fit
    self._fit(X, y, w)
  File "/home/xxxxxxxxxx/.venv/lib/python3.8/site-packages/pyqlib-<IP_ADDRESS>-py3.8-linux-x86_64.egg/qlib/contrib/model/linear.py", line 80, in _fit
    model.fit(X, y, sample_weight=w)
  File "/home/xxxxxxxxxx/.venv/lib/python3.8/site-packages/sklearn/linear_model/_base.py", line 662, in fit
    X, y = self._validate_data(
  File "/home/xxxxxxxxxx/.venv/lib/python3.8/site-packages/sklearn/base.py", line 581, in _validate_data
    X, y = check_X_y(X, y, **check_params)
  File "/home/xxxxxxxxxx/.venv/lib/python3.8/site-packages/sklearn/utils/validation.py", line 964, in check_X_y
    X = check_array(
  File "/home/xxxxxxxxxx/.venv/lib/python3.8/site-packages/sklearn/utils/validation.py", line 800, in check_array
    _assert_all_finite(array, allow_nan=force_all_finite == "allow-nan")
  File "/home/xxxxxxxxxx/.venv/lib/python3.8/site-packages/sklearn/utils/validation.py", line 114, in _assert_all_finite
    raise ValueError(

Is there any way I can add processors for training meta model to solve this error?

Here is the result by running python workflow.py --forecast_model="gbdt" --sim_task_model="gbdt" run_all
test.txt

@wendili-cs will help to answer this question.

Could you please provide more details, such as the sim_task_model that you use? If you use linear, it should have defined Fillna and DropnaLabel processors in its yaml, so it is supposed to avoid such a problem...


Add load/reloader logs

Continuation of #1501
Also add prefix option for the logs, not by a stack, but rather by a variable set by the owning file
TODO:

[ ] Add logs to plugins
[ ] Unset prefix on closure of each file
[ ] Add logs to completions?
[ ] Add logs to themes?

Nice work knocking out a version of this already !
I suppose a simple string prefix is usable as my initial stack idea.
However, I don't think I would expect each individual alias/plugin/completion/theme/etc file set the prefix directly.   I think the bash-it.sh can set the prefix right before sourcing the individual files:
# libraries, but skip appearance (themes) for now
_log_debug "Loading libraries(except appearance)..."
LIB="${BASH_IT}/lib/*.bash"
APPEARANCE_LIB="${BASH_IT}/lib/appearance.bash"
for _bash_it_config_file in $LIB
do
  if [ "$_bash_it_config_file" != "$APPEARANCE_LIB" ]; then

    BASH_IT_LOG_PREFIX="library: ${$_bash_it_config_file}"  # TODO - strip path prefix and .bash suffix

    # shellcheck disable=SC1090
    source "$_bash_it_config_file"
  fi
done

Here, each library gets the context (prefix) for free and only has to worry about logging messages.
Just a few of these sprinkled throughout the bash-it core code would go a long way.

The bash-it.completion.bash file uses this: basename $f | sed -e 's/\(.*\)\..*\.bash/\1/g' | sed -e "s/^[0-9]*---//g"

What are we, animals !?
# full component filename with path, priority and extension
$ filename="/home/user/.bashit/enabled/123---awesome-component.type.bash"

# filename without path
$ filename=${filename##*/}

123---awesome-component.type.bash

# filename without path or priority
$ filename=${filename##*---}

awesome-component.type.bash

# filename without path, priority or extension
$ filename=${filename%.*.bash}

awesome-component

After the loop reset the prefix variable to its previous value

This is kinda what my stack idea as meant to address.
I wouldn't want the code at the loop location to hard-code the previous value.  We might be able to use a backup variable to store/restore the value, but you'll want the backup variable name to be unique to the loop so that if the call path enters a second loop somewhere that also needs to store/restore the context, it doesn't trash your first backup value.
You could also use this backup variable to abstract global context from the local loops:
# Store global context so we can restore it later
BASH_IT_LOG_PREFIX_BAK_LIB=${BASH_IT_LOG_PREFIX}

for do
    # Add our local context, maintaining global context
    BASH_IT_LOG_PREFIX="${BASH_IT_LOG_PREFIX_BAK_LIB}:library: ${_bash_it_config_file}"
done

# Restore global context before moving on
BASH_IT_LOG_PREFIX=${BASH_IT_LOG_PREFIX_BAK_LIB}

Again, my stack idea was mean to enable these concepts using simpler push/pop semantics.
Overall I think we're heading in a good direction !
-DF

I did not yet implemented stack or even prev backup, but now there are many log messages and the prefix are set up correctly
I might add some tests to see that it works as expected

Thanks for working through this - looks great now! Is this ready-to-merge from your perspective?
@davidpfarrell Comments, thoughts?

Thanks so much for reviewing!
I think this is a nice start, and we should start to recommend adding logs to anyone who opens a PR. I think we can merge this, but let's wait for more people to chime in :smile:
In any case, we can add more logs to various components whenever we want to

Merging this now - we can keep adding more logs as needed.

Thanks again for the implementation, @NoahGorny - this is great!

Thanks for merging @nwinkler
Happy to help 😊


migrate scripts to ESM

refactor(scripts): migrated 'build.js' to ESM
refactor(scripts): migrate 'test' to ESM
refactor(scripts): migrate download.js to ESM

Resolves #366

Behavior
Before the change?
scripts/<test|build|download> are using require(...).
After the change?

scripts/<test|build|download> use import ... from ....
we update execa, map-obj and sort-keys to the latest versions:

https://github.com/octokit/openapi/pull/332
https://github.com/octokit/openapi/pull/318
https://github.com/octokit/openapi/pull/317)

Additional info
Pull request checklist

[ ] ~Tests for the changes have been added (for bug fixes / features)~
[ ] ~Docs have been reviewed and added / updated if needed (for bug fixes / features)~
[x] Added the appropriate label for the given change

Does this introduce a breaking change?

Please see our docs on breaking changes to help!

[ ] Yes (Please add the Type: Breaking change label)
[x] No

If Yes, what's the impact:

N/A

Pull request type

Type: Maintenance

Why is the old build.js still present?

Just fyi, once folks start reviewing your pull request, it's good to avoid push force requests, otherwise the reviewers will loose the state of changes they already checked. PR commits can be messy, we will squash them at the end anyway

I just push-forced after reading this, sorry. I will do that from now on. (I'm working in other projects where we don't squash so I mix approaches sometimes, sorry for that).


Azure Vault integration

Hi,
that will great have Azure Vault integration too.
Thanks,
L.

Sorry I didn't see in page but I found it in code https://github.com/tellerops/teller/blob/master/pkg/providers/azure_keyvault.go


How to build and test locally

I was hoping to add some functionality via a pull request but really struggling getting this working locally. I've cloned and linked the repo and followed various online tutorials on how to do this but to no avail. Do you have a list of easily reproducible steps on how to get a local lib working in a local project for test purposes?

Potentially add something like the demo page to the source package so that a simple npm install+ng serve would render a testing page. It would allow for rapid prototyping without a large setup step.
I've seen quite a few components having a demo directory specifically for this purpose.

Added with #352


Version 5.0

Move to datasource plugin code
Support alert
Support public dashboard

we are still working on it. my goal was to finish this month, but I don't think that is going to be possible.

Any development in the work on Version 5.0?

Is there any release date yet?

If you want to try it out check the backend branch.

There are a few bugs yet. Should have a new version by the end of next week.

@elwills https://github.com/GridProtectionAlliance/osisoftpi-grafana/pull/155 ready to merge.

The latest release is pending review at Grafana.


isort: bug in sorting sub-package modules

.isort.cfg
[settings]
known_first_party=foo.bar,baz
known_third_party=foo,blub,blah

valid isort-compatible code:
import sys

import blah
import blub
import foo
from foo import bar, baz

import baz
import foo.bar
from foo.bar import blah, blub

pyproject.toml:
[tool.ruff]
select = ["I"]
[tool.ruff.isort]
known-first-party = ["foo.bar", "baz"]
known-third-party = ["foo", "blub", "blah"]

$ ruff --fix --diff foo.py
--- foo.py
+++ foo.py
@@ -3,8 +3,8 @@
 import blah
 import blub
 import foo
+import foo.bar
 from foo import bar, baz
+from foo.bar import blah, blub

 import baz
-import foo.bar
-from foo.bar import blah, blub

Would fix 1 error.

I'm tempted to call this unsupported. Isn't the issue here that you're marking a module and one of its submodules as third- and first-party respectively?

ruff should be isort compatible, right?
we have a main package foo with many different sub-packages as foo.bar or foo.blub.
In the code of foo.bar we want that foo.bar is a first-party module and everything else (foo and foo.blub) is just a third-party module.

The intent is to be isort-compatible, but we do deviate in a small number of cases, and this to me seems like a situation where there isn't a clear definition of correct behavior. I'd be open to doing what isort does rather than our current behavior, but I won't personally prioritize it.

I provided a fix in #3064. Isort has a test case for it: https://github.com/PyCQA/isort/blob/main/tests/unit/test_isort.py#L2213-L2304 → test_placement_control() and test_custom_sections()

One usecase where we encounter the same issue are namespace packages. We have different packages (in different repositories) share the same namespace package.
With the following config, isort lists namespace.packageA imports in the last section while all other namespace imports are listed in the third party section above.
known_first_party = namespace.packageA
default_section = THIRDPARTY

I played around with known_first_party and known_third_party options but I cannot get packages with the same namespace prefix to end up in different sections.


Example in the readme not working

Hi, the example within the readme are not working.
However, I would like to add that for activity diagrams (vertical line things), we can also use those icons. For example:
@startuml My Sample
  title Some kind of title
  !include <font-awesome/common>

  ' https://github.com/Roemer/plantuml-office (basically the ICONURL in VS code need a local URI)
  !define ICONURL ../plantuml-office/office2014
  !include ICONURL/Devices/workstation_pc.puml
  !include ICONURL/Servers/mainframe_host.puml

  participant "<$workstation_pc>" as pc
  participant "<$device_printer>" as printer

  pc -> printer: Print a document
  printer -> pc: Ok!

@enduml

Hi
I fixed the examples. The problem was that !include <font-awesome/common> must be changed to !include <tupadr3/common>.
Your example works like this:
@startuml
title Some kind of title
  !include <tupadr3/common>

  ' https://github.com/Roemer/plantuml-office (basically the ICONURL in VS code need a local URI)
  !define ICONURL https://raw.githubusercontent.com/Roemer/plantuml-office/master/office2014
  !include ICONURL/Devices/workstation_pc.puml
  !include ICONURL/Servers/mainframe_host.puml

  participant "<$workstation_pc>" as pc
  participant "<$device_printer>" as printer

  pc -> printer: Print a document
  printer -> pc: Ok!
@enduml

Can you please try again?
Also using remote urls works great in VSCode when using
https://marketplace.visualstudio.com/items?itemName=jebbs.plantuml

Easy only example (using http://www.plantuml.com/plantuml/)
| :---: |
| |
| 🆚 |
|  |


Add the limit when dumping data

Possible config syntax:
tables:
  - users:
    # per table
    limit: 10000
    # ........................
default:
  # global
  limit: 1000

We can also think about more flexible customization - specifying an SQL query for the table.

@akirill0v, what do you think?

Perhaps it would be better to add a custom SQL conditional query? For example:
tables:
  - users:
    # per table
    query: age > 18 or age < 50 and state = 'enabled'
    # ........................
default:
  # global
  query: limit 1000

How the parts of the query affect each other (global condition and table condition) may be discussed below. My guess is they are concatenated via the AND operator.

I like this idea.


Groupby.idxmax and Groupby.idxmin

Now only support one-level index

Codecov Report

Merging #649 into master will decrease coverage by 0.36%.
The diff coverage is 94.87%.

@@            Coverage Diff             @@
##           master     #649      +/-   ##
==========================================
- Coverage    93.3%   92.93%   -0.37%
==========================================
  Files          32       32
  Lines        5106     5141      +35
==========================================
+ Hits         4764     4778      +14
- Misses        342      363      +21

Impacted Files
Coverage Δ

databricks/koalas/missing/groupby.py
100% <ø> (ø)
:arrow_up:

databricks/koalas/groupby.py
86.12% <94.87%> (+0.36%)
:arrow_up:

databricks/koalas/missing/__init__.py
92.3% <0%> (-7.7%)
:arrow_down:

databricks/koalas/indexes.py
88.78% <0%> (-2.81%)
:arrow_down:

databricks/koalas/__init__.py
82.05% <0%> (-2.57%)
:arrow_down:

databricks/koalas/exceptions.py
80.95% <0%> (-2.39%)
:arrow_down:

databricks/conftest.py
95.34% <0%> (-2.33%)
:arrow_down:

databricks/koalas/plot.py
92.51% <0%> (-1.58%)
:arrow_down:

databricks/koalas/datetimes.py
95.68% <0%> (-0.87%)
:arrow_down:

... and 1 more

Continue to review full report at Codecov.

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

wait to be code reviewed.

I do nothing with  groupby.rank why i failed in groupby.rank. Can you help me check it?


New Book Suggestions

I want to add two books about OS and databases.

Operating System Concepts - Abraham Silberschatz & Greg Gagne & Peter B. Galvin
Database System Concepts -  Abraham Silberschatz  & Henry Korth & S. Sudarshan

You can add these books to related category. Thank you for your suggestions.


Allow importing files from JSON schemas

🔍 Search Terms
JSON schemas are the standard for describing the structure of JSON and YAML data. They are essentially a stripped down version of TS types. It would greatly increase DX if one could just import a JSON schema and use it as a type in TS. Currently, one has to manually convert the schema into TS using something like npx json-schema-to-typescript -i schema.json -o schema.ts.
✅ Viability Checklist

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[x] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
[x] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

⭐ Suggestion
There are several ways this could be realized. The most straightforward seems to be to build on import attributes.
import type Schema from "./schema.json" with { type: "json-schema" };

We could also allow specifying a schema for imported JSON files:
import config from "./config.json" with { type: "json", $schema: "./schema.json" };

// ... would be the same as:
import config_ from "./config.json" with { type: "json" };
import type Schema from "./schema.json" with { type: "json-schema" };
const config = config_ as Schema;

Feel free to bikeshed the syntax.
📃 Motivating Example
import type Person from "https://example.com/person-schema.json" with { type: "json-schema" };

const res = await fetch("https://example.com/get-person");
if (res.ok) {
  const p: Person = await res.json();
  p.name // correctly typed!
}

import type Config from "https://example.com/config-schema.json" with { type: "json-schema" };
const config: Config = YAML.parse(
  await Deno.readTextFile("./config.yml")
);
config.version // correctly typed!

💻 Use Cases
Simplifying working with JSONs and YAML files, not having to run json-schema-to-typescript.

I'd call this almost a duplicate of #49314.
Relevant comment: https://github.com/microsoft/TypeScript/issues/49314#issuecomment-1142727347

The Venn diagram of things supported by JSON Schema and by TypeScript has substantial area in both non-overlapping regions, including things we're likely to not ever implement (maxProperties, minLength, etc). Without a 1:1 translation between JSON Schema and TS we'd be left making a ton of policy decisions that people might need to be configurable, and it'd just be a huge mess.

Yeah, you're right. Closing this in favor of the linked issue.


Get toneout info from safalert

Right now safalert sends emails with the following:

Delivered-To<EMAIL_ADDRESS>Received: by <IP_ADDRESS> with SMTP id w88csp8842571qtd;
Thu, 5 Jan 2017 17:24:33 -0800 (PST)
X-Received: by <IP_ADDRESS> with SMTP id k125mr709177wmb.89.1483665873731;
Thu, 05 Jan 2017 17:24:33 -0800 (PST)
Return-Path<EMAIL_ADDRESS>Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com. [2a00:1450:400c:c09::22c])
by mx.google.com with ESMTPS id n5si61963700wje.171.2<IP_ADDRESS>.24.33
for<EMAIL_ADDRESS>(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Thu, 05 Jan 2017 17:24:33 -0800 (PST)
Received-SPF: pass (google.com: domain of<EMAIL_ADDRESS>designates 2a00:1450:400c:c09::22c as permitted sender) client-ip=2a00:1450:400c:c09::22c;
Authentication-Results: mx.google.com;
dkim=pass<EMAIL_ADDRESS>dkim=pass<EMAIL_ADDRESS>spf=pass (google.com: domain of<EMAIL_ADDRESS>designates 2a00:1450:400c:c09::22c as permitted sender<EMAIL_ADDRESS>Received: by mail-wm0-x22c.google.com with SMTP id a197so70wmd.0
for<EMAIL_ADDRESS>Thu, 05 Jan 2017 17:24:33 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:delivered-to:dkim-signature:dkim-signature
:mime-version:from:to:reply-to:subject:message-id:date;
bh=fPdf6rzggxPy4b/dJ/SoB9NTynAMUaxwYoSWcXsr754=;
b=o6QeAJvqg/dgUXtIC8E1leUQcyJS3xvUBk1kWxKn6BcbtlzELwq83m5hspUkYzpKBu
JJDlUbaiuwsESLwE+1cplSfMO5SFxKTo6ds+BUN8zUIp4pwsgWycY+tyMvy01u1CBvPi
OFUW6tWQzccGBoayKyW4yrL3z2IoSelELdEGegAaCiz89VhdenAULB4TbPAFxBZ5C50n
zwg2doJryn0AqD/LmOP16O0QcCvN0YBpPpaNN4rQbxbLBHITvuiOdnPu0vFdmYmjdWXR
o9SY+o+GGwn+ULXAw9+YOu8P0i+YQXD5v9ZY2Ilu3/rHNMdHxLdmJvCmaHsW2okfi11w
sloQ==
X-Gm-Message-State: AIkVDXJj1yI8PIvpm/mfO7XaM7yGcpSnbhaXOdufXCW8yqVB0TR8Cev08ODVQ9VxjBzziduRz/mVi9IisR9FnMB1pa+h+A0=
X-Received: by <IP_ADDRESS> with SMTP id 71mr748115wmy.74.1483665873420;
Thu, 05 Jan 2017 17:24:33 -0800 (PST)
X-Forwarded-To<EMAIL_ADDRESS>X-Forwarded-For<EMAIL_ADDRESS><EMAIL_ADDRESS>Delivered-To<EMAIL_ADDRESS>Received: by <IP_ADDRESS> with SMTP id k17csp8512396edb;
Thu, 5 Jan 2017 17:24:31 -0800 (PST)
X-Received: by <IP_ADDRESS> with SMTP id i5mr139266629pgp.10.1483665871710;
Thu, 05 Jan 2017 17:24:31 -0800 (PST)
Return-Path<EMAIL_ADDRESS>Received: from o2.ems.safalert.net (o2.ems.safalert.net. [<IP_ADDRESS>])
by mx.google.com with ESMTPS id g1si77695782plb.278.2<IP_ADDRESS>.24.31
for<EMAIL_ADDRESS>(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Thu, 05 Jan 2017 17:24:31 -0800 (PST)
Received-SPF: pass (google.com: domain of<EMAIL_ADDRESS>designates <IP_ADDRESS> as permitted sender) client-ip=<IP_ADDRESS>;
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=safalert.net; h=mime-version:content-type:from:to:reply-to:subject; s=smtpapi; bh=KEvi5sCnrGly+XelPFYrroMikpc=; b=LB6YpzcggsLZ1oDYvkbbQMTRfL/Tx N5LseVaMKbrieLwXzsHqZl+EsAkk1fOEgrRkC4O8H9NaW475z5dScZRnQ2mbYx7G ViZ8YgubBI52h0/oEGbY6UAh8CJgeU2ieugPHC0j8L5fgU6MMSKLxEYwbLVUBl50 9svjLyFtzh++PY=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sendgrid.info; h=mime-version:content-type:from:to:reply-to:subject:x-feedback-id; s=smtpapi; bh=KEvi5sCnrGly+XelPFYrroMikpc=; b=M4unjqad9xzuiVHCqC tYtTevgwIo/HP5S3ggSfc5nK5wUo0fbsRGJHBCUTLJGM6dYSiCI+aDdURv40/0+0 PRyC93+nJqPZZqVPuwB7durqMaICMJRQ1RsysTRAo3OScY0ooqqDRd9hQagi8UKp tJbZo9EW9NbgVO4ZgExa1seoU=
Received: by filter0030p1las1.sendgrid.net with SMTP id filter0030p1las1-30120-586EF1CE-16
2017-01-06 01:24:30.659143998 +0000 UTC
Received: from localhost (ec2-52-37-19-41.us-west-2.compute.amazonaws.com [<IP_ADDRESS>]) by ismtpd0004p1sjc2.sendgrid.net (SG) with ESMTP id xE0I_Q_zSuGE3Apw3Ocf-w for<EMAIL_ADDRESS>Fri, 06 Jan 2017 01:24:30.473 +0000 (UTC)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="=_be78f63b17a33b6d0a8babb7f026cc22"
From<EMAIL_ADDRESS>To<EMAIL_ADDRESS>Reply-To<EMAIL_ADDRESS>Subject: 200 ALERT
Message-ID<EMAIL_ADDRESS>Date: Fri, 06 Jan 2017 01:24:30 +0000 (UTC)
X-SG-EID: 8tNxmV0jzzPzE6W5j+Ajsmp1hGpqL4seICdxkQ6Z9n7h8dGMKaopovKSTQJ3YHhWO8usgsnALVhTiA Ggz+APsUH2j6P9Ri4CLfqFWM3n0Fs+3ZJ+PHHaw5nx7NDdjJHSuG4r4sE8OWDtLoXvi3caJNlqZAVH I4MXZsDrP1ML27DBvGKDLXsGzakSY+0KXiizVgb9ZbaIzLksLtsmMVdikw==
X-Feedback-ID: 1815244:XFQPzWYtzfHIfKdZ5CxHvIOd4eBDvE5K6hG6v4EgLAY=:XFQPzWYtzfHIfKdZ5CxHvIOd4eBDvE5K6hG6v4EgLAY=:SG

--=_be78f63b17a33b6d0a8babb7f026cc22
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=ISO-8859-1

Dispatch Time: 2017-01-05 07:24:08 PM CDT
Sent By SafAlert
--=_be78f63b17a33b6d0a8babb7f026cc22
Content-Transfer-Encoding: base64
Content-Type: audio/mpeg; name=Dispatch_01-06-2017_1923-37.mp3
Content-Disposition: attachment; filename=Dispatch_01-06-2017_1923-37.mp3; size=90720

--=_be78f63b17a33b6d0a8babb7f026cc22--

Ideally we'd be able to directly integrate with them so that we can get the alerts directly (no e-mail required), but maybe the integration will require e-mail. Either way, through this we should get the time of the event, the type of event, and the recording.

I e-mailed safalert asking for API docs; they don't have any information on an API published online.


refactor(client): togglebutton's layout from float to flex

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #49459

Are these changes sufficient? Please let me know if more changes are needed and I will gladly do so.

Did as told! Please review these changes and let me know if anything else needs to be done :)


Websockets are stuck in CONNECTING state.

I'm trying to connect to a local websocket server.
socket = new WebSocket("ws://localhost:30003");
The socket never connects properly. When I try to do socket.send(), it throws a DOMException:
Uncaught DOMException: Failed to execute 'send' on 'WebSocket': Still in CONNECTING state.
It works fine in Chrome 43. I've also tried running this code inside the Atom editor, it doesn't work.

I've tried it with Socket.io, and it works.

https://github.com/websockets/ws works as well, but native WebSockets don't work.

@RonnChyran what If I told you that https://github.com/websockets/ws doesn't use any fallbacks and relies solely on Native WebSockets :smiley:

It reimplements WebSockets in node. To clarify what I mean by "Native WebSockets", I mean the browser-based window.WebSocket in the Renderer process; the same WebSocket provided by Google Chrome. Those don't work in electron, the node module is required to have working WebSockets.

@RonnChyran I think you are doing it incorrectly, it has reimplemented websockets using nodejs but only for servers and clients that don't have them natively and from what I understand is that you want to connect to a websocket server not be one, So you don't need any library for that.

My point is that the built-in WebSockets are stuck in CONNECTING. Thus, my only solution is to use the nodejs WebSockets. It doesn't really bother me, its just that it's a bug that the built-in WebSockets never connect.

Due to #1450 user agent is not set in WebSockets, can you check if your server correctly handles this situation?

Closing since it is very likely a duplicate of #1450.


Update Table component in @iot-app-kit/components

Overview
Replace old table component with new component from @iot-app-kit/table.

add a wrapper of @iot-app-kit/table to @iot-app-kit/components
update iot-table component
update test for iot-table
add some example of the new table component to testing-ground.

Tests
[Include a link to the passing GitHub action running the test suite here.]
Legal
This project is available under the Apache 2.0 License.

needs to also be marked as a breaking change with the change log detailing it

needs to also be marked as a breaking change with the change log detailing it

Agree. Change log and documentations will be added in next PR.

Adding a new change to apply formatting property filtering options. Now property filtering has the same formatting behaviour like the table component.
Default rounding for numbers:

User provided formatter:
formatter: (data) => `${Math.round((data as number) * 100) / 100} kN/M`


Moron implementation of createOncoMatrix

dplyr >>>>>> data.table
The output is identical to the version generated by maftools:::createOncoMatrix but implemented in a way that is not sensitive to the number of rows in the incoming data.

Is this PR ready for review Kostia?

Yes 😄

Thanks Adam!


Do you want me to improve GitHub Actions?

Is your feature request related to a problem? Please describe.
The only CI in here is Hassfest.
Describe the solution you'd like
I can contribute some advanced CI to your repository in a PR. Let me know if you want that.
Describe alternatives you've considered
Closing this issue.
Additional context
Add any other context or screenshots about the feature request here.

Hi @KTibow
We are looking to merge this custom_component into HA core (see https://github.com/home-assistant/core/pull/39605)
Once we manage this, this repository will become obsolete so it's probably not worth spending too much time on CI

Okay. Thanks.

@KTibow I'm interested in your ideas for CI. I'm working in a cookiecutter template for HA custom component based on blueprint repository. If you want we can continue the discussion here: https://github.com/oncleben31/cookiecutter-homeassistant-custom-component

See https://github.com/KTibow/ha-blueprint


Added timestamp offset

Hey!
I really wanted this feature (and at least one more person - #59), so I wrote it myself. This is my first time programming in TS (or JS), so I hope I did everything right (it compiles and works as intended).
It basically just offsets the timestamp (and t= link) by some amount of seconds chosen in the settings.

Default offset is 0 (no offset).
Offset resulting in a negative time will stamp 00:00 instead.
Setting the offset amount to a negative number will flip the sign (since offsetting forward makes no sense, and is assumed to be a mistake).
Entering anything that is not a number will change the offset to default (0).

I've left some code comments in File changes section of PR, you can create another commit to address those.

I can't any comments, what am I missing?

Sorry, forgot to submit review, first time I've ever used this feature😂 It should be visible now


Add metrics for writing or reading size of cursor

Motivation
Currently, there is no visibility about the following activities:

How many bytes are written from a cursor update?
How many bytes are read from loading a cursor?
So when the bookkeeper cluster is having heavy traffic, it is hard to tell which topic or namespace contributes most of the traffic.

Add metrics at the broker about how many bytes are written and read per cursor/namespace.
Modifications
Add metrics writeLedgerSize, writeLedgerLogicalSize, readLedgerSize.

@codelipenghui :
brk_ml_cursor_writeLedgerSize contains cursor-prefix, do I need to change the metric name to brk_ml_cursor_writeCursorLedgerSize?

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

I think we might need to remove the single dimension metrics for namespace. See comments for details.
Otherwise, the new metrics look good to me.

Thanks and I have updated the patch.

@michaeljmarshall Please help review again.


Cobra CLI

merged from codegangsta/cli to spf13/cobra.

@xenolf Maybe this PR should be synced up and merged in before more refactoring happens...

@mholt branch synced up locally with the current state. will restart the work tomorrow.


Search through ALL searchers

Hey, loving Kaku so far. Great job getting this up and running.
I'm hoping there could be an option for searching on all the different music platforms (youtube, soundcloud, vimeo), rather than just picking one at a time.
I'll be looking through the code to see if I can send in a PR with something hacked together.
Not sure if there will be conflicts with each of the "Searcher" elements though. We will seee!
Thanks

hi @patrickbolle, Hmm, this sounds interesting.
If you read the source code, you'll notice that Searcher will try to retrieve each sub-searcher and use their own search() function to do the search. And because there is an select/option list for users to decide which searcher they gonna use, it would be a preference kept in LocalStorage and will be used next time when booting up.
The better solution here from my mind is that, you can try to make a new sub-searcher with the same API interface like the others. In its search() function, you'll iterate all sub-searchers' search() function and collect those data into one there. By doing so, you can also create a new preference called All Searcher or something in Settings page for users to use with.
Hope this information helps :) any patch is welcome !

I'll work on this one because I am working on refactoring seachers !