Question on CBS Performance

Hi, thanks for the interesting research / technique. I was trying to reproduce it and ran into a potential issue and was wondering if you could help shed some light on whether this is expected behavior. Looking at your training code, it seems that there is no pipeline data augmentation happening (except for a Normalize). When I do the same, I see large accuracy performance gains when using CBS on ciFAIR100 (blue vs orange below). However, looking at the CE graph it seems like the training is severely overfitting. I tried adding a simple 50% horizontal flip data augmentation during training, and the performance gains offered by CBS virtually disappeared (green vs brown). When I added slightly more augmentation (expand&crop + cutout) CBS actually performed worse than normal training (purple vs orange). Any thoughts on whether this is the expected behavior or why this might be happening?

Thank you for your interest. Do you mind following up with me via email since I don't get Github notifications<EMAIL_ADDRESS>I will run the experiments for myself as well and try to replicate your findings and update + close this issue when needed.

What would happen if we use smoothing as a data augmentation technique during training?


feat : Added /events page

fixes #11

Added /events events page.
Used bootstrap card component and props-type npm package for validating props being used.
Added dummy data for events
created custom hook for calling api's
currently using logo for events will update once dummy images are handy.

demo:
https://github.com/user-attachments/assets/eb310303-2e7d-4f59-9280-aae215d5ffe7

@devsdenepal  do we have GSSoC 2024Extd support, if yes could you please add label for same.

Unfortunately, we're not registered there. I'll take care of it next time.


Torn Signpost

text: Sets base strength. If a minion have a base strenght of 3 and plays inferior Torn Signpost, his base damage now is 2.
link: https://www.vekn.net/forum/rules-questions/45620-rock-cat-vs-torn-signpost#45626

Fixed.


dynamic import react components exclude css

In my project, some react components are dynamic imported:
const LazyComponent = React.lazy(() => import(path/to/lazy-component/index.tsx));

But i don't want to load the component css file lazy, because the css file is so small, not worth to send another https request. so in webpack.config.js:
optimization: {
  splitChunks: {
    chunks: 'async',
    name(_1, _2, cacheGroupKey) {
      return cacheGroupKey;
    },
    cacheGroups: {
      'lazy-component': {
        test(module) {
          // I mean to exclude the less/css/scss and image files to this cacheGroup.
          return /lazy-component(.*)?\.(ts|tsx|js|jsx|json)$/.test(module.resource);
        }
      }
    }
  }
}

But, after building, I still get a lazy-component.css file.
So i wonder how to avoid the css splitting, thank you.

@yinjun1991 I think it's good practice to actually show your config, otherwise you're lettting people guess what the hell is going on.
I could be wrong here, but that seems about right, why wouldn't you get a CSS file?
Unless this is a bug, maybe you could into style-loader to inject the styles onto the DOM instead of generating a css file.

@yinjun1991 I think it's good practice to actually show your config related to this, otherwise you're letting people guess what the hell is going on, how does your CSS rules look like for instance?
I could be wrong here, but that seems about right, why wouldn't you get a CSS file?
Unless this is a bug, maybe you could into style-loader to inject the styles onto the DOM instead of generating a css file.

Thanks for your reply, I use plugins to split css chunk to a single file.
Maybe my issue is a little obscure, forgive my unskilled english. I update the issue.

It looks like you just deleted our lovely crafted issue template. It was there for good reasons. Please help us solving your issue by answering the questions asked in this template. I'm closing this. Please either update the issue with the template and reopen, or open a new issue.

Please respect time of other developers, without full confiugration/reproducible test repo we can't help, thanks


UG-646 Handle config within RPCO [Backport: newton-14.0]

Currently the rpc-gating scripts drop some RPCO config overrides,
some are always added, others are scenario dependant. This is
problematic as those overrides may not work for every branch of RPCO
and it creates a tight and inflexible coupling between RPCO and gating.
This commit adds the overrides that gating currently drops into
the boostrap-aio.yml playbook. These overrides are conditionally
applied based on environment variables that indicate the type of
build that is required.
This duplicates gating functionality so must not be merged until it's
counterpart in rpc-gating is merged:
https://github.com/rcbops/rpc-gating/pull/266
(cherry picked from commit 4435dda995de74894017ba48eeced19a3ebe4715)
(cherry picked from commit 72de4174739131c07aea98dedaae320e0b091023)
Issue: UG-646

recheck cit_trusty_deploy_swift failed on test server basic ops

recheck_cit_trusty_deploy_swift failed on test server basic ops


Add focus to a first input with error in UiMultipleAnswer and UiMultipleChoices, add alert attributes to UiAlert if is needed

Description

UiMultipleAnswer and UiMultipleChoices add focus to first answer with error and add stories for this examples
UiAlert add alerts attributes when it is an alert
UiPhoneNumber fix props with error

Related Issue
No ticket in CL
Motivation and Context
We want to improve accessibility
How Has This Been Tested?
In MGP
Screenshots (if appropriate):

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my code
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

This PR is split into the smallest PRs.


textarea value lost when container is rerendered

https://jsfiddle.net/jo32/k93scb5r/

The textarea-Element is a special one, because changing its child affects its value. This is working as expected.


@conda-forge-admin, please add user @pinin4fjords

Solution to issue cannot be found in the documentation.

[X] I checked the documentation.

Issue
N/A
Installed packages
N/A

Environment info
N/A

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added user @pinin4fjords in conda-forge/cheetah3-feedstock#14.


Add blank row to hierarchy.csv from QCAlign

To prevent user errors in Nutil, it would be great if you could add an extra row with "color" in the first cell, positioned between row 2 and 3 in the hierarchy.csv files from QCAlign.
Like this:

Please check if NESYS_Tools\QCAlign-v0.9 is okay.

Follow up @sharoncy


[BUG] double restart app reload

If you click fast 2 times on the script reload button, this system is showing 2 reloads but I think is only doing one.

This is not possible anymore on #486 since the reload button is disabled directly after i pressed one time. So i was not able anymore to start 2 processes even if i try to click multiple times as fast as possible on the reload button.


Use get_random_exp_name from dvc.

Closes #396
Requires DVC release

What do you think of adding back some basic tests, like that it returns a string and that it will return a different name each time?

It is tested in https://github.com/iterative/dvc/blob/main/tests/func/experiments/test_utils.py#L4 , since this is a exact copy-paste, felt like no reason to replicate the same


version bump --> 1.8.5 (auto-sycn graph reference)

Just for consistency, it's a new branch :)

@chriddyp @etpinard @cldougl just pinging you, but i'm going to go ahead and merge this in.


update sidecar for Istio 0.7.1

Upgrade Sidecar and implement Helm based template

Created branch for this 0.7.1


"Player entered/left room" messages should use room ID instead of shortname

The server-driven messages when another player enters/leaves send the shortname to the client. They should send the roomId and let the client do its own local lookup of the shortname.

This is still a good idea — connect/disconnect/move messages should use NameViews instead of plaintext strings — but is tied up in figuring out what we're doing with those messages.

Okay, I was confused about this.
We're already using NameViews for everything. This is purely whether room movement messages include the shortname for the room (which is directly rendered) or a room ID that gets resolved and rendered locally.
The user value of making this change is we could theoretically make the room names clickable (e.g. "[Susan] moved to [the kitchen]"). This is useful but low priority.


chore: add target to update golden-files for individual tests

Signed-off-by: Zain Malik<EMAIL_ADDRESS>What this PR does / why we need it:
Updating the golden files for tests wasn't documented and for first time contributors to those it can be hard to discover how to do it.
This PR adds a Make target to update golden files, and requires the name of individual test to update only one by one. This is to address concerns to avoid doing a massive update in golden files by error
examples:
make update-golden-TestInitCmd_dry
make update-golden-TestParamsList

Nice middle ground, I like it.

Indeed! I like this!


[ICR] Mainnet testing

The whole user flow should be tested on mainnet, in addition to mumbai.
In order to do this, mainnet ICR credits are needed. The ICR dev has suggested they create a mainnet test registry to produce mainnet test projects, so that they are not issuing test credits from the main registry.

[x] In order to use this test registry, the Marketplace facet needs to be updated to query this test registry, in addition to already the main registry, to verify the token.
[x] If the subgraph does not support the test registry (most likely case) then the project contract balance will need to be queried directly.

Currently active


[REG2.067] Issue 14508 - compiling with -unittest instantiates templates in non-root modules

https://issues.dlang.org/show_bug.cgi?id=14508
All template instances outside of version(unittest){} or debug(num){} need to use the normal instantiation strategy.
When -unittest or -debug(=num) switches specified, the instantiation strategy will be tweaked - a conditionally instantiated template code by version(unittest){} or debug(num){} will be generated conservatively, even if it's done in non root module.
It can be formalized as follows:
R = templates instantiated in root module
N = templates instantiated in non root module
S = templates instantiated speculatively

Default instantiation strategy:
codegen = R - (R ∩ N)

The new instantiation strategy for -unittest or -debug=num:
codegen = Rd - (Rd ∩ N)
Rd = R ∪ Nd
Nd = version(unittest) and debug template instances in non-root modules

The old instantiation strategy for -allInst:
codegen = R ∪ N

@WalterBright This is also an answer for the instantiation strategy workaround that you implemented in #2661, to fix issue 11239.
Please review this.

Not sure that this or #2661 are good ideas. You can't generally expect that linking code compiled with different debug/version settings works.
struct Foo
{
    debug size_t cnt;
}
void bar(Foo* foo) { debug ++foo.cnt; }

@MartinNowak Yes, it generally doesn't work. But for the instantiated code we can relax the restriction.
Normally we don't provide unittest version library, as such debug/release version libraries. Therefore the relaxation would be useful.

Auto-tester now shows all green.
The previous Phobos failure in Win64 was another link-failure issue 14541.
Now this PR also fix it.

Shouldn't the codegen be like this instead?
codegen = R - (R ∩ N \ Nd)

Nd = version(unittest) and debug template instances in non-root modules

Pushed additional fix commit. I'll squash it after the review finished.

Shouldn't the codegen be like this instead?

By using Nd, it would be formalized like:
  codegen = Rd - (Rd ∩ N)
  Rd = R ∪ Nd
  Nd = version(unittest) and debug template instances in non-root modules

Sit, Making instantiation strategy more strict will directly hit the root of issue 12661. We need to fix it radically, at first.

OK, I added one more feature "force instantiation mechanism".

More feature for root of issue 12661 - Add forceInst mechanism

If an instantiated function contains debug{} or version(unittest){}, the instance code will be forcibly generated.
If an instantiated function calls other forcibly instantiated function and its attribute is influenced by inference, that code is also generated forcibly.

I'm not in favor of reordering code as in f0080e8 because it makes it very difficult to compare code that crosses such a diff. Can you please back that out?

I'm a bit worried, that doing it transitively will generate an awful amount of code.
Using version (unittest) or debug (PRINTF) in a template is not that uncommon.
Might be worth to think about alternatives, like shipping a debug phobos library.

If an instantiated function contains debug{} or version(unittest){}, the instance code will be forcibly generated.

How can you know that function contains such conditions before instantiating it?
Is this just looking at the AST?

I also have a suggestion to fix part of the instantiation bloat.
https://github.com/D-Programming-Language/dmd/pull/4384/files#r29910422.

Does this resolve the compilation slowdown caused by https://github.com/D-Programming-Language/dmd/pull/4384 ?

I suspect the rule we should be using is that all templates in non-root modules should be instantiated lazily, meaning only if a particular instantiation is actually needed. No eager instantiations.
I did this for enum members a while back, and the results have been very satisfactory. It also resolves order-of-evaluation issues.

I'm a bit worried, that doing it transitively will generate an awful amount of code.
Using version (unittest) or debug (PRINTF) in a template is not that uncommon.

An alternate suggestion would be to change the behavior of -unittest and -debug switches. For example:
"If a template which defined in non-root module is instantiated, unittest {} blocks and version(unittest){} conditions in it are just ignored even if -unittest switch is specified. Same strategy will be applied to -debug."
But, it would prohibit to define a module just for unit-testing/debug utilities. I think it would need a design decision to the D module system.

Might be worth to think about alternatives, like shipping a debug phobos library.

It would be horrible idea. How many combinations would be necessary for the user code conditional compilations?
phobos.lib phobos_unittest.lib phobos_debug1.lib phobos_debug2.lib phobos_debug_PRINTF.lib ...

Does this resolve the compilation slowdown caused by #4384 ?

No. It makes more slow down compilation speed to make linking more stable.

If an instantiated function contains debug{} or version(unittest){}, the instance code will be forcibly generated.

How can you know that function contains such conditions before instantiating it?

There's no general way, so a condition can depend on the semantic result. See the following example code:
// this function template may or may not depend on -unittest
void foo(string code)() {
    mixin(code);
}
foo!"version(unittest) unsafeCheckFunc();"();

I removed commits for code cleanup in order to concentrate on bug fix.

I suspect the rule we should be using is that all templates in non-root modules should be instantiated lazily, meaning only if a particular instantiation is actually needed. No eager instantiations. Thus certainly would resolve the particular case in https://issues.dlang.org/show_bug.cgi?id=14508

See my comment here, https://github.com/D-Programming-Language/dmd/pull/4384#discussion_r29910422.
We should establish a rule which module is responsible for instantiating a template if that's ambiguous (e.g. mutual import). A simple rule would be to use the module with the lexicographically smaller module name.

I suspect the rule we should be using is that all templates in non-root modules should be instantiated lazily

Sounds good, but is that feasible for the next release? It wouldn't solve linkage issues when the template is used though.

An alternate suggestion would be to change the behavior of -unittest and -debug switches. For example:
"If a template which defined in non-root module is instantiated, unittest {} blocks and version(unittest){} conditions in it are just ignored even if -unittest switch is specified. Same strategy will be applied to -debug."

That would actually solve the problem we had with MonoTimeImpl and vibe.d.

But, it would prohibit to define a module just for unit-testing/debug utilities. I think it would need a design decision to the D module system.

How is that? You mean for separate compilation?
That build mode is mostly used to mitigate the CTFE mem consumption.

Does this resolve the compilation slowdown caused by #4384 ?
No. It makes more slow down compilation speed to make linking more stable.

There's got to be a better answer than a 30% slowdown. What about the idea of lazy instantiation?

Alternative: https://github.com/D-Programming-Language/dmd/pull/4780

Superseded by: https://github.com/D-Programming-Language/dmd/pull/4784


Fix run_ogusa_example.py

In a recent PR, run_ogusa_example.py was updated to be more clear.  However, the current configuration will fail for Windows users as the dask processes can't be called from top line code on a Windows machine.
The executing code in this script needs to be put in a main() function.

This was resolved with PR #501


Readme: s/testbed/coav-sim

[x] Update Requirement list
[x] Modify text about "testing the library. Explaing how to try it with coav-control
[ ] Once we have coav-sim up, change to explaing how to try it with coav-sim

Readme and Wiki updated.


Add support for Previous/Next mouse buttons

Godot version:
3.1
OS/device including version:
no matter
Issue description:
The previous and next mouse buttons(Button4 / Button5) aren't recognized by Godot and cannot be added to shortcuts or used in games. I have the mouse with these buttons, and its supported in many games so I maked this request to add support for them in Godot.

At least on macOS mouse buttons 4/5 are detected by Godot as InputEventMouseButton with button indices BUTTON_XBUTTON1 and BUTTON_XBUTTON2

huh.. then it looks like Windows only bug.. and on Linux ?

Ah.. didnt correctly checked.. its work


Fuzzy test domestic migration rates

Fuzzy test domestic migration rates
Description

Category: test
JIRA issue: SSCI-995 (research ticket)
Research reference: none

Changes and notes
Based on #256.
Uses V&V target values calculated on the research side.
Verification and Testing
Ran integration tests with several population sizes.
Intentionally doubled the person migration rate and verified that these tests will fail (even with only 20k population size).

Ran into an issue with the math here; closing for now while I re-think.


Search project directory for test-resources files first

Partially resolves https://github.com/Azure/azure-sdk-tools/issues/4450
Depends on https://github.com/Azure/azure-sdk-tools/pull/4623
Replaces https://github.com/Azure/azure-sdk-for-net/pull/32288 which won't re-open for some reason.
I decided it would be better to add detection at the language repository yaml level for template existence in the project directory, rather than enable the deploy script to fall back to the service directory if the project directory did not have a bicep template. This way we can fail fast locally when people intend to specify a TestResourcesDirectory override but make a mistake with the file path/existence. The downside is we have to add extra yaml handling in the languages.

/azp run net - template - tests

Example run with a sub-project bicep file: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1967774&view=results

/azp run net - Azure.Monitor.Ingestion - tests


Couldn't import custom library file

I am not able to import custom library file. Is there any easy way to do that?

No actually, I dont have jar file. It is a groovy file used in the code I am testing. I have to create instance on that file and pass as a parameter. I have added path of file in NXF_CLASSPATH, but its not working.
To be more clear RNGCreator is class we added in our code which is used to generate random number.
I want to add param in my code something like:
rngCreator = RNGCreator.instance
rngCreator.setBaseSeed(123)
params.rngCreator = rngCreator


[tool_crash] FileSystemException: Failed to decode data using encoding 'utf-8', null

Command
flutter --no-color run --machine --track-widget-creation --device-id=windows --start-paused --dart-define=flutter.inspector.structuredErrors=true lib\main.dart

Steps to Reproduce

...
...
...

Logs
FileSystemException: Failed to decode data using encoding 'utf-8', null
#0      _File._tryDecode (dart:io/file_impl.dart:564:7)
#1      _File.readAsStringSync (dart:io/file_impl.dart:584:7)
#2      ForwardingFile.readAsStringSync (package:file/src/forwarding/forwarding_file.dart:96:16)
#3      ErrorHandlingFile.readAsStringSync.<anonymous closure> (package:flutter_tools/src/base/error_handling_io.dart:209:22)
#4      _runSync (package:flutter_tools/src/base/error_handling_io.dart:545:14)
#5      ErrorHandlingFile.readAsStringSync (package:flutter_tools/src/base/error_handling_io.dart:208:12)
#6      new SettingsFile.parseFromFile (package:flutter_tools/src/base/utils.dart:136:36)
#7      updateLocalProperties (package:flutter_tools/src/android/gradle_utils.dart:222:29)
#8      AndroidProject.ensureReadyForPlatformSpecificTooling (package:flutter_tools/src/project.dart:853:5)
#9      FlutterProject.ensureReadyForPlatformSpecificTooling (package:flutter_tools/src/project.dart:263:21)
<asynchronous suspension>
#10     FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:1117:7)
<asynchronous suspension>
#11     FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:986:27)
<asynchronous suspension>
#12     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#13     AppContext.run (package:flutter_tools/src/base/context.dart:149:12)
<asynchronous suspension>
#14     CommandRunner.runCommand (package:args/command_runner.dart:197:13)
<asynchronous suspension>
#15     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:274:9)
<asynchronous suspension>
#16     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>

[✓] Flutter (Channel dev, 1.25.0-8.0.pre, on Microsoft Windows [Version 10.0.18363.1316], locale en-US)
    • Flutter version 1.25.0-8.0.pre at C:\flutter_windows_1.22.4-stable\flutter
    • Framework revision a12e2a473a (6 weeks ago), 2020-12-08 23:13:04 -0500
    • Engine revision df39e5c515
    • Dart version 2.12.0 (build 2.12.0-133.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at C:\Users\user\AppData\Local\Android\sdk
    • Platform android-30, build-tools 30.0.2
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
    • All Android licenses accepted.

[✓] Visual Studio - develop for Windows (Visual Studio Community 2019 16.8.3)
    • Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2019\Community
    • Visual Studio Community 2019 version 16.8.30804.86
    • Windows 10 SDK version 10.0.18362.0

[✓] Android Studio (version 4.1.0)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)

[✓] VS Code (version 1.52.1)
    • VS Code at C:\Users\user\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.18.1

[✓] Connected device (1 available)
    • Windows (desktop) • windows • windows-x64 • Microsoft Windows [Version 10.0.18363.1316]

• No issues found!

Flutter Application Metadata
Type: app
Version: 1.0.0+1
Material: true
Android X: false
Module: false
Plugin: false
Android package: null
iOS bundle identifier: null
Creation channel: dev
Creation framework version: a12e2a473a3214b4556ca589d2d9bd311ac7c6f1
Plugins
integration_test

Closing this as duplicate of https://github.com/flutter/flutter/issues/65021

Closing this as duplicate of https://github.com/flutter/flutter/issues/65021


Detects Windows 10 if added to the app manifest

Only works if app manifest includes supported OS

Looks good.


Correct usage of "delimiter-separated" in help strings, docs, and comments

When referencing delimiter-separated formats, a hyphen is required. Examples are "tab-delimited" and "space-separated."

This checklist is used to make sure that common guidelines for a pull request are followed.
General Guidelines

[X] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

Command Guidelines

[X] Each command and parameter has a meaningful description.
[X] Each new command has a test.

(see Authoring Command Modules)

View a preview at https://prompt.ws/r/Azure/azure-cli/5472
This is an experimental preview for @microsoft users.

I guess I need to bump the package numbers in each setup.py as well, is how I read the CI failure. I'll try to do that this afternoon.

Docs changes LGTM


openstack: map all the OpenStack VIF models

Add all the missing OpenStack VIF models and map
them to the supported values in OpenShift. Fallback
to virtio if the model is not supported by OpenShift
Fixes #304
Signed-off-by: Miguel Martín<EMAIL_ADDRESS>

we can also add a warning-validation for models that are not supported and going to change during the migration

this requires #289


Implement Access Levels

~(Might need an RFC for this)~ RFC: https://github.com/inveniosoftware/rfcs/pull/13
We want access levels to correspond to permissions. Access levels will be a higher-level abstraction over low-level create/read/update/delete... permissions. By being encoded this way on the record's metadata, we can create generators that hold the business logic and are flexible.

I agree, I think an RFC is a good idea for this. Do you think it could fit in the access control one? or is too much already?

Yeah, I think an extension to RFC 7 like what I wrote for explicit additional permissions would be best.

Closed via #29


Form submission canceled because the form is not connected

The WARNING: "Form submission canceled because the form is not connected"  appears on the console when the user clicks in a cancel button that has the following code:
  handleCancel = (evt) => {
    this.props.reset();
    this.props.router.replace('/');
  }

What is the right way to CANCEL the form submission and navigating away from the page that has a redux-form?
I am using:

redux-form: ^6.5.0
react-router: ^3.0.2
semantic-ui-react: ^0.66.0
apollo-client: ^0.8.7

When the user clicks in the submit button, everything works fine (data is mutate using Apollo Client and navigating away from the page that has the form): no warning is shown

That's pretty strange. My guess is that you have:
<button onClick={this.handleCancel}>Cancel</button>

and it should be
<button type="button" onClick={this.handleCancel}>Cancel</button>
        ^^^^^^^^^^^^^

I think that most browsers default a <button/> to be a submit button, so you are both trying to submit the form and navigate away.
Another option is to call evt.preventDefault() in your handleCancel() function.

Thank you, so much, @erikras!!!
I am using a Button from 'semantic-ui-react', and both solution works, using evt.preventDefault() OR using putting the type'button'
                <Button
                  secondary
                  disabled={submitting}
                  floated='right'
                  icon size='small'
                  labelPosition='left'
                  onClick={this.handleCancel}
                  type='button'
                >
                  <Icon name='cancel' />Cancelar
                </Button>

Are there one preferred solution?

I have the same warning in my UI that is done in Angularjs. But the context is different. I get this warning when I click on the 'a' tag to download a report from a dashboard. There are two tags, 1 for excel sheet, and the second one to download as pdf.
I have copied the code below. export is the function triggered when those icons are clicked.
$scope.export = function (format) {             var form = document.createElement("form");             form.setAttribute("target","_blank");             form.setAttribute("role","form");             form.setAttribute("method","post");             form.setAttribute("action","/reportServer"+format.charAt(0).toUpperCase()+format.substr(1));             var formatInput = document.createElement("input");             formatInput.setAttribute("name","format");             formatInput.value = format;             form.appendChild(formatInput);             var queryInput = document.createElement("input");             queryInput.setAttribute("name","queryData");             var queryData = getReportQuery();             queryInput.value = angular.toJson(queryData);             form.appendChild(queryInput);             var parametersInput = document.createElement("input");             parametersInput.setAttribute("name","parameters");             parametersInput.value = $scope.report.distributions.join();             form.appendChild(parametersInput);             var fieldsInput = document.createElement("input");             fieldsInput.setAttribute("name","fields");             fieldsInput.value = $scope.report.fields.join();             form.submit();         };

the same issue...solved by adding type="button" to .  Thanks for that tip!


GPS doesn't work on 1.4.1 master

When I use latest code on branch master, GPS can't find any satellite.
When I use code on branch beta or stable, GPS works fine.
I tried with two GPS module, an u-blox M8N and an u-blox 7N.And the Hardware is pixhawk 2.4.6.

Can you provide further information? what's the output of gps status? And gps stop, gps start ?


Fix precision setting change not being picked up

PIXI.settings.PRECISION = 'highp';
Wasn't getting picked up in my game.
It turns out, the style of using the PRECISION setting meant it was a static value. This has been changed so that it's looking to the reference of the settings object to pick up the live changed value

Fixes: https://github.com/pixijs/pixi.js/issues/3742

Good find!


implement regrid_like in packages for which the default mechanics do not apply

In GitLab by @luitjansl on May 16, 2023, 12:00

In GitLab by @luitjansl on Jun 2, 2023, 16:58
regrid_like in packages for which the default mechanics do not apply will be implemented in a single issue per package- so this collection issue can be closed. Currently we have task #415 for the Well and task #401 for the structured discretization


[WIP] Add MGSM (Multilingual Grade School Math) benchmark

#3

[x] Add support for CLI parameters to control the size and subset of languages
[ ] WIP: Compare to metrics reported in simple-evals
[x] README.md

gpt-4o-mini-2024-07-18
Exact match accuracy reported in simple-evals: 87.2%
Accuracy on 20% subsample (50 tasks for each language): 86%

Comparing to simple-evals on llama3.1_8b_instant (Groq). Small subset (110 samples out of 2750).
simple-evals: 45.5%
inspect-evals: 41.8%

PR looks good, please address the two comments above and then we can request feedback from AISI. Thanks!


Input does not compile with latest version of std/async

Describe the bug
std/async removed deferred in https://github.com/denoland/deno_std/pull/3852
Since input does not pin the version of std/async, this results in the following error when trying to import the input library:
Warning Implicitly using latest version (0.210.0) for https://deno.land/std/async/mod.tsiB (217/258)
error: Uncaught SyntaxError: The requested module 'https://deno.land/std/async/mod.ts' does not provide an export named 'deferred'
import { deferred } from "https://deno.land/std/async/mod.ts";
         ^
    at <anonymous> (https://deno.land/x/input@2.0.3/index.ts:5:10)

To Reproduce
Attempt to import the input package in deno
Expected behavior
The import succeeds
Program Output
n/a
Versions (please complete the following information):

OS: Mac OSX 14.2.1
Deno Version : 1.32.4

Additional context
Add any other context about the problem here.

Thank you for your report. I'll plan to release version 2.1 shortly to remove the use of deferred. I won't be able to until the evening here, so if you'd like to raise a PR in the meantime to pin the version it would be much appreciated.

Thanks, very much appreciate it! (unfortunately I won't be able to get around to making a PR until later today either)

@joyzheng I've released version 2.0.4 that pins std at 0.205.0 to allow this to compile and run. I still plan to remove the use of the deprecated deferred once I have some more time.


end2end test

url list -> screenshot of the front with checks along the way
can be done easily after #31 is done

done now


test

Codecov Report

Merging #151 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master    #151   +/-   ##
======================================
  Coverage    73.2%   73.2%
======================================
  Files         106     106
  Lines       16627   16627
======================================
  Hits        12171   12171
  Misses       3528    3528
  Partials      928     928

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 91f2127...99568a5. Read the comment docs.


Question: Is the mod server-side, client-side, or both?

Apologies for asking a question here rather than reporting an issue, but saw now other method to ask.

That's fine! A mod should be installed on both side.

Thanks!


fix: decode options in compat mode

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.liuqiang.06 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


[Autocomplete] onkeyup event in renderOption not work

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Steps to reproduce 🕹
Link to live example: https://codesandbox.io/embed/bold-voice-0doitx?fontsize=14&hidenavigation=1&theme=dark
Steps:

click the input
hit the arrow-down button
hit the arrow-right button
see the log

Current behavior 😯
The key-up event set in renderOption is not triggered
Expected behavior 🤔
The key-up event set in renderOption to be triggered
Context 🔦
I want to customize the key-up event and implement some accessibility features in the options
Your environment 🌎
I am using Chrome v105.0.5195.127

The individual menu items don't receive keyboard events because they are not focused. Technically, focus is managed with the aria-activedescendant attribute. The  DOM focus must be placed on the input element, so it's interactive and can receive input.
You have to listen to the keyup event on the autocomplete itself. You can track which item is highlighted using the onHighlightChange prop - this way you'll know which item the virtual focus is on when user presses a key.


Playground support moved to chat completion api and auth

Playground migrated to use chat completion api and auth
Removed chat_playground module - no longer required
EventInfo path is now only "/v1/api/eventinfo"
Old Playground auth code and paths remove from authorize module

Will come as part of #19 to ensure the playground and API are kept in sync.


Update dev-1.22-ko.2 (M46, M48-M50)

Related issue: #30000
Fix tasks: M46, M48-M50
M46. content/en/docs/reference/issues-security/security.md | 4(+XS) 4(-)
M48. content/en/docs/reference/scheduling/config.md | 1(+XS) 1(-)
M49. content/en/docs/reference/setup-tools/kubeadm/_index.md | 1(+XS) 1(-)
M50. content/en/docs/reference/tools/_index.md | 5(+XS) 2(-)

/retitle [ko] Update dev-1.22-ko.2 (M46, M48-M50)
😊

/lgtm
/approve


[BUG] nvcomp (bitcomp) doesn't work on P100 (sm60) GPU

Describe the bug
The nvcomp minimum requirement is Pascal (sm60)+ and only GDeflate requires Volta+. However, I got the below error when I evaluated the bitcomp_test on a CentOS 7 machine (P100, CUDA driver 460.32.03).  The bitcomp_test is shipped with nvcomp_exts_x86_64_ubi7-2.2.tar.gz from NVIDIA website .
I suspect the nvcomp (bitcomp library) is not compiled correctly and which only works for sm62+, and there is no error on V100/A100 machine based on my testing. Hopefully, NVIDIA can make nvcomp (bitcomp library) work with P100 GPU card (I believe it 's not a cheap card)

% ./bitcomp_test ./bitcomp_test
Compression benchmark on file ./bitcomp_test, size = 14970328
Testing with format BITCOMP_UNSIGNED_8BIT and algorithm BITCOMP_DEFAULT_ALGO
Error, cannot get compressed size
Testing with format BITCOMP_SIGNED_8BIT and algorithm BITCOMP_DEFAULT_ALGO
Error, cannot get compressed size
Testing with format BITCOMP_UNSIGNED_16BIT and algorithm BITCOMP_DEFAULT_ALGO
Error, cannot get compressed size
Testing with format BITCOMP_SIGNED_16BIT and algorithm BITCOMP_DEFAULT_ALGO
Error, cannot get compressed size
Testing with format BITCOMP_UNSIGNED_32BIT and algorithm BITCOMP_DEFAULT_ALGO
Error, cannot get compressed size
Testing with format BITCOMP_SIGNED_32BIT and algorithm BITCOMP_DEFAULT_ALGO
Error, cannot get compressed size
Testing with format BITCOMP_UNSIGNED_64BIT and algorithm BITCOMP_DEFAULT_ALGO
Error, cannot get compressed size
Testing with format BITCOMP_SIGNED_64BIT and algorithm BITCOMP_DEFAULT_ALGO
Error, cannot get compressed size
Testing with format BITCOMP_UNSIGNED_8BIT and algorithm BITCOMP_SPARSE_ALGO
Error, cannot get compressed size
Testing with format BITCOMP_SIGNED_8BIT and algorithm BITCOMP_SPARSE_ALGO
Error, cannot get compressed size
Testing with format BITCOMP_UNSIGNED_16BIT and algorithm BITCOMP_SPARSE_ALGO
Error, cannot get compressed size
Testing with format BITCOMP_SIGNED_16BIT and algorithm BITCOMP_SPARSE_ALGO
Error, cannot get compressed size
Testing with format BITCOMP_UNSIGNED_32BIT and algorithm BITCOMP_SPARSE_ALGO
Error, cannot get compressed size
Testing with format BITCOMP_SIGNED_32BIT and algorithm BITCOMP_SPARSE_ALGO
Error, cannot get compressed size
Testing with format BITCOMP_UNSIGNED_64BIT and algorithm BITCOMP_SPARSE_ALGO
Error, cannot get compressed size
Testing with format BITCOMP_SIGNED_64BIT and algorithm BITCOMP_SPARSE_ALGO
Error, cannot get compressed size

Steps/Code to reproduce bug

Download nvcomp_exts_x86_64_ubi7-2.2.tar.gz from https://developer.nvidia.com/nvcomp-download to a CentOS 7 machine (P100, CUDA driver 460.32.03).
Extract the tarball file and switch to ubi7/10.2/bin or ubi7/11.0/bin
Run ./bitcomp_test bitcomp_test

Expected behavior
No error occurs on P100.
Environment details (please complete the following information):

Environment location: Bare-metal
Method of nvCOMP install: nvcomp_exts_x86_64_ubi7-2.2.tar.gz from https://developer.nvidia.com/nvcomp-download

Any feedback from nvcomp maintainer? This issue shouldn't be ignore. Thanks.


Update the docs for building a dynamic ngx_pagespeed module

I am pushing my head with this since last 1 day. I need your help now on this issue. I am going to explain this in detail.
I have an nginx version 1.10.2 installed in /etc/nginx and working perfectly fine. Now I want to integrate page speed module in this nginx. I am following this tutotrial https://modpagespeed.com/doc/build_ngx_pagespeed_from_source
I am running following command to install it
bash <(curl -f -L -sS https://ngxpagespeed.com/install) \
     --nginx-version 1.10.3 \
     --dynamic-module \

it asks me to enter any extra configuration and I found extra configs in nginx -V and I wrote these
--with-cc-opt='-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2' --with-ld-opt='-Wl,-Bsymbolic-functions -Wl,-z,relro' --prefix=/usr/share/nginx --conf-path=/etc/nginx/nginx.conf --http-log-path=/var/log/nginx/access.log --error-log-path=/var/log/nginx/error.log --lock-path=/var/lock/nginx.lock --pid-path=/run/nginx.pid --http-client-body-temp-path=/var/lib/nginx/body --http-fastcgi-temp-path=/var/lib/nginx/fastcgi --http-proxy-temp-path=/var/lib/nginx/proxy --http-scgi-temp-path=/var/lib/nginx/scgi --http-uwsgi-temp-path=/var/lib/nginx/uwsgi --with-debug --with-pcre-jit --with-ipv6 --with-http_ssl_module --with-http_stub_status_module --with-http_realip_module --with-http_auth_request_module --with-http_v2_module --with-http_dav_module --with-http_slice_module --with-threads --with-http_addition_module --with-http_dav_module --with-http_flv_module --with-http_geoip_module --with-http_gunzip_module --with-http_gzip_static_module --with-http_image_filter_module --with-http_mp4_module --with-http_perl_module --with-http_random_index_module --with-http_secure_link_module --with-http_v2_module --with-http_sub_module --with-http_xslt_module --with-mail --with-mail_ssl_module --with-stream --with-stream_ssl_module --with-threads

After that I opened my config file and added
load_module "modules/ngx_pagespeed.so";

and restarted my nginx.
It gives me this error
module "/usr/share/nginx/modules/ngx_pagespeed.so" is not binary compatible in /etc/nginx/nginx.conf:5

Please if anyone can help me in this. I have also tried following this link https://www.digitalocean.com/community/tutorials/how-to-add-ngx_pagespeed-to-nginx-on-ubuntu-14-04 and install with pagespeed module. But I got my nginx messed up completely. Now I am not getting which nginx version is running :(
Kind Regards,
Abubakar Bilal

I did some debugging on where the signature in a module build according to our instructions would diverge from the server signature from, say, the one you can get from the nginx ppa.
1 ubuntu@lw-dev:~/tmp⟫ nginx
nginx: [alert] could not open error log file: open() "/var/log/nginx/error.log" failed (13: Permission denied)
ngx_pagespeed signature: [8,4,8,0000111111010111001111111111101110]
server        signature: [8,4,8,0000111111010111001111111111111110]
NGX_MODULE_SIGNATURE_30 diverges!

At https://github.com/nginx/nginx/blob/a6cb8210905f35977276cb3861184e4dad99cc2a/src/core/ngx_module.h you can see that NGX_MODULE_SIGNATURE_30 corresponds to NGX_HTTP_HEADERS.
That doesn't get set in the nginx core as far as I can tell, and it doesn't show up in the `./configure' line.
To be continued.

Adding --with-cc-opt='-DNGX_HTTP_HEADERS' to nginx's ./configure arguments (or modifying any existing --with-cc-opt='xxx' to include -DNGX_HTTP_HEADERS)  makes ngx_pagespeed.so binary compatible with the ppa version.
Stripping the arguments that are not relevant for binary compatibility, the following should build ngx_pagespeed as a dynamic for use with the latest stable at nginx's ppa (1.12.1):
bash <(curl -f -L -sS https://ngxpagespeed.com/install) \
     --nginx-version "1.12.1" \
     --dynamic \
     -a '--with-http_ssl_module
--with-http_realip_module
--with-http_dav_module
--with-http_gzip_static_module
--with-http_gunzip_module
--with-threads
--with-cc-opt="-DNGX_HTTP_HEADERS"'

When the  above script asks you if it should install nginx, you should probably decline, assuming you just want the dynamic module.
Upon completion, the dynamic module should be ready for use at ~/nginx-1.12.1/objs/ngx_pagespeed.so
If you configure your package managed nginx to load this dynamic module, you may want to block updates for nginx by the package manager: The nginx version is included in the binary compatibility check. Blocking automatic updates implicates that you have to do some regular maintenance to keep up with important updates.

Added an entry to the priority list to update the docs to include the results of the research done in https://github.com/pagespeed/ngx_pagespeed/issues/1440#issuecomment-315565106

Thanks for this great work! I succeeded with @oschaaf 's guide.
I upgrade nginx version to 1.12.1 by add nginx ppa.
sudo add-apt-repository ppa:nginx/stable
sudo apt-get update
apt install nginx

I also made a git repo to share the ngx_pagespeed.so file. Hope this can simplify the procedure adding the dynamic module to existing nginx on the server.
https://github.com/itbdw/nginx_pagespeed_dynamic_module

If anyone is interesting, created gist with detailed information here.   https://gist.github.com/secfigo/f41a5f243610053d03ad410254540802

Adding the -DNGX_HTTP_HEADERS stuff does not solve the issue mentioned here.

Adding the -DNGX_HTTP_HEADERS stuff does not solve the issue mentioned here.


Pagination & performance issues

I'm submitting a...

[ ] bug
[x] feature
[x] chore

What is the current behavior
When using big datasets, the chart is laggy / not-responding.
What is the expected behavior
I actually expected this to happen, however I'd like to discuss what's the best implementation for smooth charts when using big datasets.

Is this hard to implement optimizations in the library to automatically load / unload points when they're out of visible range? This implies not rendering the whole data array but rather it's visible part only. Not sure if it'll fix all the lag tho.
If the above is possible, maybe it would also be possible to implement a data fetch helper. It could be a callback prop that is invoked whenever new data is needed to continue scrolling the chart.
If it's not possible / too hard, I suppose I can manually rotate the input data. However I don't really like this approach, because I don't know when to fetch the data. Do I need to add manual pagination buttons?

Hi, this is always something we want to improve. v1 of the library was mostly around translating from the previous project to typescript and getting props, bugs etc... fixed.
I see v2 as changing the way it works.
how big a dataset are we talking here?

Is this hard to implement optimizations in the library to automatically load / unload points when they're out of visible range? This implies not rendering the whole data array but rather it's visible part only. Not sure if it'll fix all the lag tho.

This is already done, only the visible part is rendered.

If the above is possible, maybe it would also be possible to implement a data fetch helper. It could be a callback prop that is invoked whenever new data is needed to continue scrolling the chart.

This is also already done and how we use the chart, we only pull back what we want to be visible and pan or zoom loads more data.

Your response got me back on the right track. I got fooled by my implementation, the chart was not responsible for the lag.
I am able to display multiple series of 100k points each on the same chart with a decent performance.
I also found out about onLoadBefore and onLoadAfter, which is perfect for data fetch in my use case.
Closing this as there is no problem. Thanks for the great work!


Will postalService contract ever go live?

Question
I am exploring options for sending an array of invitations to a set of whitelisted accounts in a transaction governed by EC. The objective (I believe) is to have the operation complete without any BLDer DAO intervention so I'm discounting options that use a core-eval to send invitations. The postalService contract hit me when I remembered our discussions in the Office Hours. So I'm wondering is there any chance I can count on postalService contract for this task? @dckc

if you don't find this answer suffcient, feel free to re-open the issue.
I'm not aware of any concrete plans to launch postalService on mainnet. I'm not aware of any particular obstacles to launching it (after suitable review / refinement), either. We expect to have regular upgrades to address minor issues as well as major issues, so if there's a good reason to launch it, it seems feasible.
OTOH, it's not particularly novel / powerful. Any feature that could be done by invoking the postalService could be done just by using namesByAddress (or namesByAddressAdmin if the fix for https://github.com/Agoric/agoric-sdk/issues/8113 isn't on mainnet yet.)
Note that postalService is maintained as part of an example dapp now, unlike this un-maintained agoric-labs playground:
https://github.com/Agoric/dapp-agoric-basics/blob/main/contract/src/postal-service.contract.js
cc @mitdralla

Hey @dckc - Thanks for clarifying. I could use some suggestions on where to leverage depositFacet makes the most sense in terms positioning the authority. So looking forward to talking about this in the office hours!


compile fail rayon-core require cc linker

cargo build
Updating registry https://github.com/rust-lang/crates.io-index
Downloading rayon v1.0.1
Downloading rayon-core v1.4.0
Downloading crossbeam-deque v0.2.0
Downloading lazy_static v1.0.1
Downloading crossbeam-utils v0.2.2
Downloading crossbeam-epoch v0.3.1
Downloading cfg-if v0.1.4
Downloading arrayvec v0.4.7
Downloading nodrop v0.1.12
Downloading memoffset v0.2.1
Compiling cfg-if v0.1.4
Compiling nodrop v0.1.12
Compiling memoffset v0.2.1
Compiling lazy_static v1.0.1
Compiling scopeguard v0.3.3
Compiling rayon-core v1.4.0
Compiling either v1.3.0
Compiling num-integer v0.1.35
Compiling memchr v1.0.2
Compiling num_cpus v1.7.0
Compiling rand v0.3.18
Compiling time v0.1.38
Compiling atty v0.2.3
Compiling memmap v0.6.1
Compiling textwrap v0.9.0
Compiling thread_local v0.3.4
Compiling arrayvec v0.4.7
error: linker cc not found
|
= note: No such file or directory (os error 2)
error: aborting due to previous error
error: Could not compile rayon-core.
warning: build failed, waiting for other jobs to finish...
error: build failed

I understand. Thanks a lot. Great libarry.
I will try via compile it via docker.
On Thu, 5 Jul 2018 at 19:28 Josh Stone<EMAIL_ADDRESS>wrote:

This is not a Rayon bug -- you don't appear to have a working Rust
toolchain at all. The only thing that rayon-core needs to link is its
build.rs script, which is very simple. If you can't compile that, then
I'd wager you can't compile any Rust programs at all.
On most unix platforms, rustc uses cc to perform the final linking step.
Please make sure you have a working C compiler installed to provide cc.
If you have further trouble with this, I suggest going to a more generic
Rust support forum for beginners.
https://www.rust-lang.org/en-US/community.html#getting-started
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/rayon-rs/rayon/issues/581#issuecomment-402779468, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ALrs2iqu1ZktxwvUWnJmLi2PbkHqxlDhks5uDj6VgaJpZM4VChya
.

--
Best Regards,
Yoni Shperling


Add gofumpt

Description of change
Add tooling for formatting code. Enable in CI
Type of change

[x]  New feature
[ ]  Bug fix
[ ]  Refactor
[ ]  Documentation

How was this tested?

[ ]  Unit Tests
[ ]  Tested in staging
[ ]  Tested in minikube

Demo

before
after

Additional references

Documentation updated

Going to merge, even though few tests in Acceptance Tests are failing, they seem to not be related to this change.


Compiled docs in frees-rpc repo

Documentation comes from https://github.com/frees-io/freestyle/blob/master/docs/src/main/tut/docs/rpc/README.md, which will be removed very soon in favor of using this one.
The current orgScriptCI sbt task will check the docs in Travis.

Codecov Report

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

@@            Coverage Diff            @@
##             master     #104   +/-   ##
=========================================
  Coverage          ?   84.29%
=========================================
  Files             ?       12
  Lines             ?      121
  Branches          ?        0
=========================================
  Hits              ?      102
  Misses            ?       19
  Partials          ?        0

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 694a518...84a03f4. Read the comment docs.


Move PnP.Core to it's own repository

The repo is really large right now. Let's discuss ways to get it leaner.
I would really prefer a PnP.Core repo with only the core and tests for the core project. Then it would be possible to have a repo for PS, one for samples/solutions etc.
Each repo could have it's own README.md which gives an overview of the actual part.

The entity framework repo is 20mb.

Basically we have outgrown the reasonable size, so we will need to start splitting the repo. This will be one topic for Jan community call with suggestion for comments.

I think we should look at other options by splitting things out

We've split off the guidance part to a separate repository (https://github.com/OfficeDev/PnP-Guidance) which will result in a smaller repo size. Given scenarios and solutions depend on PnP and to not add additional complexity for contributors the core team choose to keep all code together in the PnP repo.


Fix Rotation Issue with NODE_POSITION_VIEW Shader Built-In

Fixes https://github.com/godotengine/godot/issues/75896
Somehow I can't test the compiled editor since the changes do not change anything for me locally... but I used the matrices separately just like in the source code here:
https://user-images.githubusercontent.com/38077837/232257608-f3ffe5bf-1d95-4dd7-bd10-bb3d05ae0904.mov
https://user-images.githubusercontent.com/38077837/232312679-330383d0-cf25-4a89-87ea-29f1bcd20676.mov

So I compiled the editor and these changes solved the issue. Thanks!
https://user-images.githubusercontent.com/130088064/232324552-deccd6cd-aed7-4b3f-9f2f-3804c956bb40.mp4

So I compiled the editor and these changes solved the issue. Thanks!

Great to hear, thanks for testing!

Quick rebase for a merge :D

Cherry-picked for 4.0.3.


Bulk edit repos

Let me explain a little background, recently i was sued by some company and the police didn't tell me more than that it was about some "github repo". In order to be cooperative and increase my chances of the lawsuit being dropped i decided to not delete my account but rather get github premium and make all my repos private until i get information what repo this stuff is about. After purchasing premium i was shocked to see that it doesn't apply to all organisations (i have many repos outsourced) and that i can't bulk edit my stuff. The police was kind enough to tell me that it was one of the repos on my account so i was not worried about the orgs anymore but i had to go through the process of editing the setting of 200+ repos by hand which was kind of a pain in the ass and took me some time but i did it anyway for legal reasons. Now that the case has been dropped i don't need github premium anymore, i had more time and a free head to think about it. I contacted github support about that and asked them why there is no way to bulk edit your stuff because the FAQ states that i will loose all private repos when my gh premium status gets revoked for whatever reason. They said they can't do sh*t and gave me some API endpoints, but i don't feel confident enough to do anything with it so i wanted to ask you if you could help me (and maybe others that want to switch from premium to free and have a bunch of repos on private) by creating something to convert multiple repos at once. I don't really care if it's a "bot" or a website or a userscript.

email-convo

Hi @Bluscream!
I don't have any private repos, so I don't know the process of converting repos from private to public. I wouldn't think it would be difficult. I'm not sure how I can help.

I can give you temporary access to my account if that helps :)

LOL, no don't do that.
I saw this documentation - https://help.github.com/articles/making-a-private-repository-public/
If you need a userscript to fill in the input, just give me the id of that input.

If you need a userscript to fill in the input, just give me the id of that input.

Wouldn't that only make 1 repo public?

Ok, try this:
// ==UserScript==
// @name        GitHub Add Repo Name to Change Visibility
// @version     0.1.2
// @description A userscript that adds your repo name to the visibility dialog
// @license     MIT
// @author      Rob Garrison
// @namespace   https://github.com/Mottie
// @include     https://github.com/*
// @run-at      document-idle
// @require     https://greasyfork.org/scripts/28721-mutations/code/mutations.js?version=597950
// @icon        https://assets-cdn.github.com/pinned-octocat.svg
// ==/UserScript==
(() => {
	"use strict";

	function addName() {
		const name = document.getElementById("rename_field");
		if (name) {
			document.querySelector("form[action$='toggle_permission'] .input-block").value = name.value;
			const btn = document.querySelector("form[action$='toggle_permission'] .btn-danger");
			btn.removeAttribute("disabled");
			btn.removeAttribute("data-disable-invalid");
		}
	}

	document.addEventListener("ghmo:container", addName);
	addName();
})();

And yes, it will only work on one repo at a time... I haven't looked to see how to automate the action using the API as I don't have any way to test the code.

What's your email?


td-agent 4.4.2 for macOS x86_64 lacks libyaml

It's originally reported by @dferreiralopessc at Slack.
Although fluentd 1.15 requires libyaml mandatory but td-agent for macOS x86_64 lacks it:
sudo /opt/td-agent/usr/sbin/td-agent
Traceback (most recent call last):
	24: from /opt/td-agent/usr/sbin/td-agent:15:in `<main>'
	23: from /opt/td-agent/usr/sbin/td-agent:15:in `load'
	22: from /opt/td-agent/bin/fluentd:23:in `<top (required)>'
	21: from /opt/td-agent/bin/fluentd:23:in `load'
	20: from /opt/td-agent/lib/ruby/gems/2.7.0/gems/fluentd-1.15.3/bin/fluentd:15:in `<top (required)>'
	19: from /opt/td-agent/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require'
	18: from /opt/td-agent/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require'
	17: from /opt/td-agent/lib/ruby/gems/2.7.0/gems/fluentd-1.15.3/lib/fluent/command/fluentd.rb:19:in `<top (required)>'
	16: from /opt/td-agent/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require'
	15: from /opt/td-agent/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require'
	14: from /opt/td-agent/lib/ruby/gems/2.7.0/gems/fluentd-1.15.3/lib/fluent/supervisor.rb:21:in `<top (required)>'
	13: from /opt/td-agent/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require'
	12: from /opt/td-agent/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require'
	11: from /opt/td-agent/lib/ruby/gems/2.7.0/gems/fluentd-1.15.3/lib/fluent/config.rb:20:in `<top (required)>'
	10: from /opt/td-agent/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require'
	 9: from /opt/td-agent/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require'
	 8: from /opt/td-agent/lib/ruby/gems/2.7.0/gems/fluentd-1.15.3/lib/fluent/config/yaml_parser.rb:17:in `<top (required)>'
	 7: from /opt/td-agent/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require'
	 6: from /opt/td-agent/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require'
	 5: from /opt/td-agent/lib/ruby/gems/2.7.0/gems/fluentd-1.15.3/lib/fluent/config/yaml_parser/loader.rb:17:in `<top (required)>'
	 4: from /opt/td-agent/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require'
	 3: from /opt/td-agent/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require'
	 2: from /opt/td-agent/lib/ruby/2.7.0/psych.rb:13:in `<top (required)>'
	 1: from /opt/td-agent/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require'
/opt/td-agent/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require': dlopen(/opt/td-agent/lib/ruby/2.7.0/x86_64-darwin20/psych.bundle, 0x0009): Library not loaded: /usr/local/opt/libyaml/lib/libyaml-0.2.dylib (LoadError)
  Referenced from: <35E2A478-8DE6-37F5-B116-40F99453B946> /opt/td-agent/lib/ruby/2.7.0/x86_64-darwin20/psych.bundle
  Reason: tried: '/usr/local/opt/libyaml/lib/libyaml-0.2.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/usr/local/opt/libyaml/lib/libyaml-0.2.dylib' (no such file), '/usr/local/opt/libyaml/lib/libyaml-0.2.dylib' (no such file), '/usr/local/lib/libyaml-0.2.dylib' (no such file), '/usr/lib/libyaml-0.2.dylib' (no such file, not in dyld cache) - /opt/td-agent/lib/ruby/2.7.0/x86_64-darwin20/psych.bundle

On my environment, it uses Homebrew's one:
iMac5k-211:td-agent aho$ otool -L /opt/td-agent/lib/ruby/2.7.0/x86_64-darwin20/psych.bundle
/opt/td-agent/lib/ruby/2.7.0/x86_64-darwin20/psych.bundle:
	/opt/td-agent/lib/libruby.2.7.dylib (compatibility version 2.7.0, current version 2.7.6)
	/usr/local/opt/libyaml/lib/libyaml-0.2.dylib (compatibility version 3.0.0, current version 3.9.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1311.0.0)

td-agent for macOS arm64 doesn't have this issue since it uses built-in libyaml:
aho@M1-Mac-mini td-agent % otool -L /opt/td-agent/lib/ruby/2.7.0/arm64-darwin21/psych.bundle
/opt/td-agent/lib/ruby/2.7.0/arm64-darwin21/psych.bundle:
	/opt/td-agent/lib/libruby.2.7.dylib (compatibility version 2.7.0, current version 2.7.6)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1311.100.3)

We should rebuild ruby with built-in libyaml on x86_64 too.

In addition, Fluentd should require libyaml lazily only when it's really needed.

Bundled libyaml has been removed since Ruby 3.2.
From the next version of td-agent we'll use Ruby 3.2 so we should add libyaml by ourself.

libffi is also required for fiddle on Ruby 3.2.

hi @ashie, do we have an ETA for the new td-agent release? many thanks!

I've fixed it in v4.5.0 for v4 series.
For v5 (work in progress), it's not yet fixed.

thanks @ashie!


x/tools/gopls: VS Code extension showing warning in Terratest

What version of Go are you using (go version)?

$ go version
go version go1.13

Does this issue reproduce with the latest release?
Yes.

I am working on Terratest, and therefore my directory looks more or less like this:
./terraform
./terraform/output.tf
./terraform/main.tf
./terraform/test
./terraform/test/go.mod
./terraform/test/main_unit_test.go
./terraform/test/go.sum
./terraform/Makefile
./terraform/variables.tf
./terraform/provider.tf

I have VS Code open at the terraform directory level, I am working in the main_unit_test.go file.
What did you see?
A warning: You are neither in a module nor in your GOPATH. If you are using modules, please open your editor at the directory containing the go.mod.
What did you expect to see?
Go extension in VS Code working properly. My go.mod file is buried in a subdirectory, but I'm not able to open VS Code in that directory - I need to see the files I'm working on outside of the test directory. I wish there was a way to configure the extension to look for go.mod somewhere else.

Go extension in VS Code working properly. My go.mod file is buried in a subdirectory, but I'm not able to open VS Code in that directory - I need to see the files I'm working on outside of the test directory. I wish there was a way to configure the extension to look for go.mod somewhere else.

You can add the directory to your workspace through File > Add Folder to Workspace. I recognize this is not the ideal workflow, as you will see the directory in two places in the outline on the left-hand side, but it should resolve the issue. We're working on addressing this for gopls/v0.6.0.


Add db revert cmd

This PR adding new subcmd db revert that allows one to revert database to desired block using required flag --to-block.
It's useful in cases you want to debug db starting from specific block (for instance p2p follower node)

I'll update docs, but logic won't be changed

Very nice 🔥


New Feature: Allow passing TypeDeclarations to regular methods at runtime

Right now you can pass TypeDeclarations to macros:
https://play.crystal-lang.org/#/r/41a7
macro what_am_i?(declaration)
  {{ p declaration.type }}
end

what_am_i? thing : String # Prints: String

It would be wonderful to also be able to use a TypeDeclaration class at runtime:
def what_am_i?(declaration)
  p declaration.type
end

what_am_i? thing : String # Prints: String

Example use case:
https://luckyframework.org/guides/database-migrations/#creating-and-altering-tables
# created_at, updated_at, and id are added automatically
create :users do
  add name : String # will set the column to NULL FALSE
  add age : Int32? # will allow NULL values because of the nilable type
end

Right now I have to make add a macro even though it could easily be done as a method if it were possible to pass a type declaration around at runtime. I imagine it would be a simple struct with the exact same methods as the TypeDeclaration(T) available at compile-time (where T is the type, makes it so you can only allow TypeDeclarations of a certain type, used in this case so that only types that are allowed in the database can be passed to the method)
def add(declaration : TypeDeclaration(String))
  # add string column using declaration.type, declaration.var and declaration.default
end

I admit I do not know how this is implemented so maybe this is extremely difficult, but my hope is that it is not. I think this will open up APIs that feel wonderful because you're using familiar syntax instead of something like: add :age, Int32?, default = 1

I didn't know you could do that and I still don't understand it. Could you provide an example?

And one important reason is that macros tend to have awful error messages. I like to avoid them when possible, but maybe what you suggest will not suffer from that same flaw

macro add(typedec)
  add {{ typedec.var.symbolize }}, {{ typedec.type }}, {% if typedec.value %} default: {{ typedec.value }}{% end %}
end

carc.in

macro add(declaration)
  add_impl({{declaration.var.stringify}}, {{declaration.value}}, {{declaration.type}})
end

then define add_impl(var : String, value, type). You can even use forall T to generify on the type!

Oh, I see. So the macro just translates the type declaration into a regular method call. I think that may still result in some harder to trace error messages but aren't nearly as bad as what they look like now with my current implementation!
Thanks for the tips. I'd still prefer having access at runtime, but this gets me pretty close 👍
Also, what do you mean I can use forall T to generify on type? I don't understand forall T well enough to understand how that could be used.

Ohh, I see. That makes sense. Thanks @RX14


fix: autofocus duration field

Fixes #2
Not the cleanest but does the job. 🤷♂

@Fghurayri you saved the input field! :yellow_heart:


Update Processor List

Gathered from https://dev.maxmind.com/minfraud/#Payment_payment

Coverage remained the same at 98.347% when pulling 6a9fda617cddf5ec0f4237f99eb33aa2f708dd35 on kitwalker12:patch-1 into 0d42edc32be3d9032f82505d4fe942001addd68d on kushniryb:master.

Thank you @kitwalker12 👍


Options: Ignore Forbidden {Files, Functions}

Adds options to ignore potentially forbidden files / functions.
Pretty useful when you don't have function restrictions and use a .gitignore file :).

Great additions! I'll review the PL & document these new features as soon as I can 👍

After a few improvements, this pull request is now live on master & on the auto-update system.


spdk receives invalid request

.854376] vfio_user.c:2149:map_io_cmd_req: *ERROR*: /var/run/muser/domain/muser0/8: SQ1 invalid I/O request type 0x9
[2021-02-22 12:12:01.854497] vfio_user.c:2207:handle_cmd_req: *ERROR*: /var/run/muser/domain/muser0/8: map NVMe command opc 0x9 failed
[2021-02-22 12:12:01.854528] vfio_user.c: 619:post_completion: *DEBUG*: /var/run/muser/domain/muser0/8: request complete SQ1 cid=4 status=0x6 SQ head=0xe3 CQ tail=0xe2

This is SPDK_NVME_OPC_DATASET_MANAGEMENT. Need to check whether this should have been disabled in the first place.

We used to have this:
diff --git a/lib/nvmf/vfio_user.c b/lib/nvmf/vfio_user.c
index 2f9325700..16b0d2552 100644
--- a/lib/nvmf/vfio_user.c
+++ b/lib/nvmf/vfio_user.c
@@ -569,6 +569,13 @@ handle_identify_ctrlr_rsp(struct spdk_nvme_ctrlr_data *data)
        assert(data != NULL);

        data->sgls.supported = SPDK_NVME_SGLS_NOT_SUPPORTED;
+
+       /*
+        * Intentionally disabled, otherwise we get a
+        * SPDK_NVME_OPC_DATASET_MANAGEMENT command we don't know how to
+        * properly handle.
+        */
+       data->oncs.dsm = 0;
 }

 /*

With the restored it works! Not sure why it was removed.

This is currently being fixed upstream (DSM will now be supported): https://review.spdk.io/gerrit/c/spdk/spdk/+/6525/5

Removed nutanix-tp: we have SPDK changes to disable dataset management

Removed nutanix-tp: we have SPDK changes to disable dataset management

@jlevon so we can close this?

yup


node-problem-detector: 0.8.3 -> 0.8.4

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/kubernetes/node-problem-detector/releases.
meta.description for node-problem-detector is: "Various problem detectors running on the Kubernetes nodes"
meta.homepage for node-problem-detector is: "https://github.com/kubernetes/node-problem-detector"
meta.changelog for node-problem-detector is: "https://github.com/kubernetes/node-problem-detector/releases/tag/v0.8.4"
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 0.8.4 with grep in /nix/store/d32f20894n72ly64sm9pxwg86g30brpd-node-problem-detector-0.8.4

directory tree listing: https://gist.github.com/36ff0840e6c8c20930a9716c8317aaef

du listing: https://gist.github.com/292afb784fd206def93ede8c6c9943c4

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
node-problem-detector

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/d32f20894n72ly64sm9pxwg86g30brpd-node-problem-detector-0.8.4 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A node-problem-detector https://github.com/r-ryantm/nixpkgs/archive/bc6b53b6df2686a160ba7f1c823ed633455b47e1.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/d32f20894n72ly64sm9pxwg86g30brpd-node-problem-detector-0.8.4
ls -la /nix/store/d32f20894n72ly64sm9pxwg86g30brpd-node-problem-detector-0.8.4/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review 1

1 package built:

node-problem-detector

Maintainer pings
cc @lbpdt @kalbasit for testing.

@ofborg eval


Python 3.11 Unary cancellation and exceptions in pytest-asyncio are resulting in segmentation faults

What version of gRPC and what language are you using?
Using grpcio==1.42.0 and grpcio==1.49.0 with Python 3.11.
What operating system (Linux, Windows,...) and version?
Seeing the error on both MacOS and Linux.
What runtime / compiler are you using (e.g. python version or version of gcc)
Python 3.11. (Specifically Python 3.11.0rc2)
What did you do?
I've attached a gist that should reproduce my error here: https://gist.github.com/Yun-Kim/e4a8f3cef807caa3d42cd9c1714614de
You can reproduce my error through the repro_cmd.sh file steps.
What did you expect to see?
Test cases succeed normally.
What did you see instead?
Running the test cases result in Python segmentation faults randomly. Sometimes one test case leads to the segfault, sometimes both, as if a race condition is happening.
The error log I'm seeing looks like:
test_grpcaio_repro.py::test_unary_cancellation[server_info0] PASSED                                                                                [ 50%]
test_grpcaio_repro.py::test_unary_cancellation[server_info1] Fatal Python error: Segmentation fault

Thread 0x000000016c1ef000 (most recent call first):
  File "/Users/yun.kim/.pyenv/versions/3.11-dev/lib/python3.11/threading.py", line 975 in run
  File "/Users/yun.kim/.pyenv/versions/3.11-dev/lib/python3.11/threading.py", line 1038 in _bootstrap_inner
  File "/Users/yun.kim/.pyenv/versions/3.11-dev/lib/python3.11/threading.py", line 995 in _bootstrap

Current thread 0x00000001056d8580 (most recent call first):
  File "/Users/yun.kim/.pyenv/versions/3.11-dev/lib/python3.11/asyncio/base_tasks.py", line 53 in _task_get_stack
  File "/Users/yun.kim/go/src/github.com/DataDog/tmp/repro_grpcaio/.venv/lib/python3.11/site-packages/grpc/aio/_channel.py", line 315 in _close
  File "/Users/yun.kim/go/src/github.com/DataDog/tmp/repro_grpcaio/.venv/lib/python3.11/site-packages/grpc/aio/_channel.py", line 300 in __aexit__
  File "/Users/yun.kim/go/src/github.com/DataDog/tmp/repro_grpcaio/test_grpcaio_repro.py", line 147 in test_unary_cancellation
  File "/Users/yun.kim/.pyenv/versions/3.11-dev/lib/python3.11/asyncio/events.py", line 80 in _run
  File "/Users/yun.kim/.pyenv/versions/3.11-dev/lib/python3.11/asyncio/base_events.py", line 1909 in _run_once
  File "/Users/yun.kim/.pyenv/versions/3.11-dev/lib/python3.11/asyncio/base_events.py", line 604 in run_forever
  File "/Users/yun.kim/.pyenv/versions/3.11-dev/lib/python3.11/asyncio/base_events.py", line 637 in run_until_complete
  File "/Users/yun.kim/go/src/github.com/DataDog/tmp/repro_grpcaio/.venv/lib/python3.11/site-packages/pytest_asyncio/plugin.py", line 454 in inner
  File "/Users/yun.kim/go/src/github.com/DataDog/tmp/repro_grpcaio/.venv/lib/python3.11/site-packages/_pytest/python.py", line 192 in pytest_pyfunc_call
  File "/Users/yun.kim/go/src/github.com/DataDog/tmp/repro_grpcaio/.venv/lib/python3.11/site-packages/pluggy/_callers.py", line 39 in _multicall
  File "/Users/yun.kim/go/src/github.com/DataDog/tmp/repro_grpcaio/.venv/lib/python3.11/site-packages/pluggy/_manager.py", line 80 in _hookexec
  File "/Users/yun.kim/go/src/github.com/DataDog/tmp/repro_grpcaio/.venv/lib/python3.11/site-packages/pluggy/_hooks.py", line 265 in __call__
  File "/Users/yun.kim/go/src/github.com/DataDog/tmp/repro_grpcaio/.venv/lib/python3.11/site-packages/_pytest/python.py", line 1761 in runtest
  File "/Users/yun.kim/go/src/github.com/DataDog/tmp/repro_grpcaio/.venv/lib/python3.11/site-packages/_pytest/runner.py", line 166 in pytest_runtest_call
  File "/Users/yun.kim/go/src/github.com/DataDog/tmp/repro_grpcaio/.venv/lib/python3.11/site-packages/pluggy/_callers.py", line 39 in _multicall
  File "/Users/yun.kim/go/src/github.com/DataDog/tmp/repro_grpcaio/.venv/lib/python3.11/site-packages/pluggy/_manager.py", line 80 in _hookexec
  File "/Users/yun.kim/go/src/github.com/DataDog/tmp/repro_grpcaio/.venv/lib/python3.11/site-packages/pluggy/_hooks.py", line 265 in __call__
  File "/Users/yun.kim/go/src/github.com/DataDog/tmp/repro_grpcaio/.venv/lib/python3.11/site-packages/_pytest/runner.py", line 259 in <lambda>
  File "/Users/yun.kim/go/src/github.com/DataDog/tmp/repro_grpcaio/.venv/lib/python3.11/site-packages/_pytest/runner.py", line 338 in from_call
  File "/Users/yun.kim/go/src/github.com/DataDog/tmp/repro_grpcaio/.venv/lib/python3.11/site-packages/_pytest/runner.py", line 258 in call_runtest_hook
  File "/Users/yun.kim/go/src/github.com/DataDog/tmp/repro_grpcaio/.venv/lib/python3.11/site-packages/_pytest/runner.py", line 219 in call_and_report
  File "/Users/yun.kim/go/src/github.com/DataDog/tmp/repro_grpcaio/.venv/lib/python3.11/site-packages/_pytest/runner.py", line 130 in runtestprotocol
  File "/Users/yun.kim/go/src/github.com/DataDog/tmp/repro_grpcaio/.venv/lib/python3.11/site-packages/_pytest/runner.py", line 111 in pytest_runtest_protocol
  File "/Users/yun.kim/go/src/github.com/DataDog/tmp/repro_grpcaio/.venv/lib/python3.11/site-packages/pluggy/_callers.py", line 39 in _multicall
  File "/Users/yun.kim/go/src/github.com/DataDog/tmp/repro_grpcaio/.venv/lib/python3.11/site-packages/pluggy/_manager.py", line 80 in _hookexec
  File "/Users/yun.kim/go/src/github.com/DataDog/tmp/repro_grpcaio/.venv/lib/python3.11/site-packages/pluggy/_hooks.py", line 265 in __call__
  File "/Users/yun.kim/go/src/github.com/DataDog/tmp/repro_grpcaio/.venv/lib/python3.11/site-packages/_pytest/main.py", line 347 in pytest_runtestloop
  File "/Users/yun.kim/go/src/github.com/DataDog/tmp/repro_grpcaio/.venv/lib/python3.11/site-packages/pluggy/_callers.py", line 39 in _multicall
  File "/Users/yun.kim/go/src/github.com/DataDog/tmp/repro_grpcaio/.venv/lib/python3.11/site-packages/pluggy/_manager.py", line 80 in _hookexec
  File "/Users/yun.kim/go/src/github.com/DataDog/tmp/repro_grpcaio/.venv/lib/python3.11/site-packages/pluggy/_hooks.py", line 265 in __call__
  File "/Users/yun.kim/go/src/github.com/DataDog/tmp/repro_grpcaio/.venv/lib/python3.11/site-packages/_pytest/main.py", line 322 in _main
  File "/Users/yun.kim/go/src/github.com/DataDog/tmp/repro_grpcaio/.venv/lib/python3.11/site-packages/_pytest/main.py", line 268 in wrap_session
  File "/Users/yun.kim/go/src/github.com/DataDog/tmp/repro_grpcaio/.venv/lib/python3.11/site-packages/_pytest/main.py", line 315 in pytest_cmdline_main
  File "/Users/yun.kim/go/src/github.com/DataDog/tmp/repro_grpcaio/.venv/lib/python3.11/site-packages/pluggy/_callers.py", line 39 in _multicall
  File "/Users/yun.kim/go/src/github.com/DataDog/tmp/repro_grpcaio/.venv/lib/python3.11/site-packages/pluggy/_manager.py", line 80 in _hookexec
  File "/Users/yun.kim/go/src/github.com/DataDog/tmp/repro_grpcaio/.venv/lib/python3.11/site-packages/pluggy/_hooks.py", line 265 in __call__
  File "/Users/yun.kim/go/src/github.com/DataDog/tmp/repro_grpcaio/.venv/lib/python3.11/site-packages/_pytest/config/__init__.py", line 164 in main
  File "/Users/yun.kim/go/src/github.com/DataDog/tmp/repro_grpcaio/.venv/lib/python3.11/site-packages/_pytest/config/__init__.py", line 187 in console_main
  File "/Users/yun.kim/go/src/github.com/DataDog/tmp/repro_grpcaio/.venv/bin/pytest", line 8 in <module>

Anything else we should know about your project / environment?

There is an uninitialized variable in the refactored frame object introduced in Python 3.11.x (when accessed via ctypes/cython). Please see python/cpython#99110

@byllyfish Thanks for the investigation on this and the fix in https://github.com/python/cpython/pull/100182.
@Yun-Kim It looks like the resolution on your end is going to be one of the following:

Downgrading to a 3.10.X interpreter
Waiting until the fix referenced above makes it into a released version of CPython.

Please feel free to reopen if you think what I just said is incorrect.


[UX] Domain verification

[x] Reload domain component after success, to prevent to show the still unverified state of a domain

[x] When clicking verify, show a spinner to better signal the user that something is working. If it is successful then show this and proceed to the domain component.

:tada: This issue has been resolved in version 0.103.0 :tada:
The release is available on:

GitHub release
v0.103.0

Your semantic-release bot :package::rocket:


fix: check for dangling symlinks

CC @jfirebaugh

Is there an issue or something describing the issue this actually causes? Something we can reference or maybe in the commit message?

Repro is https://github.com/aspect-build/rules_ts/compare/main...jfirebaugh:rules_ts:jfirebaugh/worker_bug. We don't have an issue for this.


Add an example for using the sensors service

We provide a sensors service, but there's no example of how to use it.

@abarth do we still have a sensors service? I don't see it in searches, or when looking in /src/services.

I think we should close this issue. We don't have a sensors service, AFAICT.
We might want to open a new issue for a plugin for Accelerometer.

Thanks!

Fixed in https://github.com/flutter/plugins/pull/121


create generic DataReader class

Generic DataReader class

at current stage, there is no need to have a generic class.