[Device Support Request] Gas detector tuya zigbee TS0601 da _TZE204_chbyv06x

Problem description
Device paired but no entities
Solution description
Please create a custom quirks
Screenshots/Video
Screenshots/Video
[Paste/upload your media here]

Device signature
Device signature
IEEE: a4:c1:38:53:f2:cb:ce:9d
Nwk: 0x069d
Device Type: Router
LQI: 39
RSSI: Sconosciuto
Visto l'ultima volta: 2023-11-13T21:13:00
Sorgente di alimentazione: Mains

Diagnostic information
Diagnostic information
{
  "home_assistant": {
    "installation_type": "Home Assistant OS",
    "version": "2023.11.2",
    "dev": false,
    "hassio": true,
    "virtualenv": false,
    "python_version": "3.11.6",
    "docker": true,
    "arch": "aarch64",
    "timezone": "Europe/Rome",
    "os_name": "Linux",
    "os_version": "6.1.21-v8",
    "supervisor": "2023.11.0",
    "host_os": "Home Assistant OS 11.1",
    "docker_version": "24.0.6",
    "chassis": "embedded",
    "run_as_root": true
  },
  "custom_components": {
    "iphonedetect": {
      "version": "1.4.0",
      "requirements": []
    },
    "tuya_local": {
      "version": "2023.9.2",
      "requirements": [
        "pycryptodome~=3.18",
        "tinytuya==1.12.11"
      ]
    },
    "hacs": {
      "version": "1.33.0",
      "requirements": [
        "aiogithubapi>=22.10.1"
      ]
    },
    "candy": {
      "version": "1.0.0",
      "requirements": [
        "backoff~=2.0",
        "aiolimiter~=1.0"
      ]
    },
    "smartir": {
      "version": "1.17.8",
      "requirements": [
        "aiofiles>=0.6.0"
      ]
    },
    "arpscan_tracker": {
      "version": "1.0.7",
      "requirements": []
    },
    "xiaomi_miot": {
      "version": "0.7.13",
      "requirements": [
        "construct>=2.10.56",
        "python-miio>=0.5.6",
        "micloud>=0.3"
      ]
    },
    "alexa_media": {
      "version": "4.7.9",
      "requirements": [
        "alexapy==1.27.8",
        "packaging>=20.3",
        "wrapt>=1.14.0"
      ]
    },
    "ble_monitor": {
      "version": "12.6.1",
      "requirements": [
        "pycryptodomex>=3.18.0",
        "janus>=1.0.0",
        "aioblescan>=0.2.14",
        "btsocket>=0.2.0",
        "pyric>=<IP_ADDRESS>"
      ]
    },
    "pun_sensor": {
      "version": "0.4.1",
      "requirements": [
        "holidays",
        "bs4"
      ]
    },
    "sonoff": {
      "version": "3.5.2",
      "requirements": [
        "pycryptodome>=3.6.6"
      ]
    }
  },
  "integration_manifest": {
    "domain": "zha",
    "name": "Zigbee Home Automation",
    "after_dependencies": [
      "onboarding",
      "usb"
    ],
    "codeowners": [
      "@dmulcahey",
      "@adminiuga",
      "@puddly"
    ],
    "config_flow": true,
    "dependencies": [
      "file_upload"
    ],
    "documentation": "https://www.home-assistant.io/integrations/zha",
    "iot_class": "local_polling",
    "loggers": [
      "aiosqlite",
      "bellows",
      "crccheck",
      "pure_pcapy3",
      "zhaquirks",
      "zigpy",
      "zigpy_deconz",
      "zigpy_xbee",
      "zigpy_zigate",
      "zigpy_znp",
      "universal_silabs_flasher"
    ],
    "requirements": [
      "bellows==0.36.8",
      "pyserial==3.5",
      "pyserial-asyncio==0.6",
      "zha-quirks==0.0.106",
      "zigpy-deconz==0.21.1",
      "zigpy==0.59.0",
      "zigpy-xbee==0.19.0",
      "zigpy-zigate==0.11.0",
      "zigpy-znp==0.11.6",
      "universal-silabs-flasher==0.0.14",
      "pyserial-asyncio-fast==0.11"
    ],
    "usb": [
      {
        "vid": "10C4",
        "pid": "EA60",
        "description": "*2652*",
        "known_devices": [
          "slae.sh cc2652rb stick"
        ]
      },
      {
        "vid": "1A86",
        "pid": "55D4",
        "description": "*sonoff*plus*",
        "known_devices": [
          "sonoff zigbee dongle plus v2"
        ]
      },
      {
        "vid": "10C4",
        "pid": "EA60",
        "description": "*sonoff*plus*",
        "known_devices": [
          "sonoff zigbee dongle plus"
        ]
      },
      {
        "vid": "10C4",
        "pid": "EA60",
        "description": "*tubeszb*",
        "known_devices": [
          "TubesZB Coordinator"
        ]
      },
      {
        "vid": "1A86",
        "pid": "7523",
        "description": "*tubeszb*",
        "known_devices": [
          "TubesZB Coordinator"
        ]
      },
      {
        "vid": "1A86",
        "pid": "7523",
        "description": "*zigstar*",
        "known_devices": [
          "ZigStar Coordinators"
        ]
      },
      {
        "vid": "1CF1",
        "pid": "0030",
        "description": "*conbee*",
        "known_devices": [
          "Conbee II"
        ]
      },
      {
        "vid": "10C4",
        "pid": "8A2A",
        "description": "*zigbee*",
        "known_devices": [
          "Nortek HUSBZB-1"
        ]
      },
      {
        "vid": "0403",
        "pid": "6015",
        "description": "*zigate*",
        "known_devices": [
          "ZiGate+"
        ]
      },
      {
        "vid": "10C4",
        "pid": "EA60",
        "description": "*zigate*",
        "known_devices": [
          "ZiGate"
        ]
      },
      {
        "vid": "10C4",
        "pid": "8B34",
        "description": "*bv 2010/10*",
        "known_devices": [
          "Bitron Video AV2010/10"
        ]
      }
    ],
    "zeroconf": [
      {
        "type": "_esphomelib._tcp.local.",
        "name": "tube*"
      },
      {
        "type": "_zigate-zigbee-gateway._tcp.local.",
        "name": "*zigate*"
      },
      {
        "type": "_zigstar_gw._tcp.local.",
        "name": "*zigstar*"
      },
      {
        "type": "_uzg-01._tcp.local.",
        "name": "uzg-01*"
      },
      {
        "type": "_slzb-06._tcp.local.",
        "name": "slzb-06*"
      }
    ],
    "is_built_in": true
  },
  "data": {
    "ieee": "**REDACTED**",
    "nwk": 1693,
    "manufacturer": "_TZE204_chbyv06x",
    "model": "TS0601",
    "name": "_TZE204_chbyv06x TS0601",
    "quirk_applied": false,
    "quirk_class": "zigpy.device.Device",
    "quirk_id": null,
    "manufacturer_code": 4417,
    "power_source": "Mains",
    "lqi": 45,
    "rssi": null,
    "last_seen": "2023-11-13T21:15:31",
    "available": true,
    "device_type": "Router",
    "signature": {
      "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.Router: 1>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.FullFunctionDevice|MainsPowered|RxOnWhenIdle|AllocateAddress: 142>, manufacturer_code=4417, maximum_buffer_size=66, maximum_incoming_transfer_size=66, server_mask=10752, maximum_outgoing_transfer_size=66, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=False, *is_full_function_device=True, *is_mains_powered=True, *is_receiver_on_when_idle=True, *is_router=True, *is_security_capable=False)",
      "endpoints": {
        "1": {
          "profile_id": "0x0104",
          "device_type": "0x0051",
          "input_clusters": [
            "0x0000",
            "0x0004",
            "0x0005",
            "0xef00"
          ],
          "output_clusters": [
            "0x000a",
            "0x0019"
          ]
        },
        "242": {
          "profile_id": "0xa1e0",
          "device_type": "0x0061",
          "input_clusters": [],
          "output_clusters": [
            "0x0021"
          ]
        }
      },
      "manufacturer": "_TZE204_chbyv06x",
      "model": "TS0601"
    },
    "active_coordinator": false,
    "entities": [],
    "neighbors": [],
    "routes": [],
    "endpoint_names": [
      {
        "name": "SMART_PLUG"
      },
      {
        "name": "PROXY_BASIC"
      }
    ],
    "user_given_name": null,
    "device_reg_id": "d187025bf125630bf12aae318bfc4d3b",
    "area_id": "cucina",
    "cluster_details": {
      "1": {
        "device_type": {
          "name": "SMART_PLUG",
          "id": 81
        },
        "profile_id": 260,
        "in_clusters": {
          "0x0004": {
            "endpoint_attribute": "groups",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0x0005": {
            "endpoint_attribute": "scenes",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0xef00": {
            "endpoint_attribute": null,
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0x0000": {
            "endpoint_attribute": "basic",
            "attributes": {
              "0x0001": {
                "attribute_name": "app_version",
                "value": 74
              },
              "0x0004": {
                "attribute_name": "manufacturer",
                "value": "_TZE204_chbyv06x"
              },
              "0x0005": {
                "attribute_name": "model",
                "value": "TS0601"
              }
            },
            "unsupported_attributes": {}
          }
        },
        "out_clusters": {
          "0x0019": {
            "endpoint_attribute": "ota",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0x000a": {
            "endpoint_attribute": "time",
            "attributes": {},
            "unsupported_attributes": {}
          }
        }
      },
      "242": {
        "device_type": {
          "name": "PROXY_BASIC",
          "id": 97
        },
        "profile_id": 41440,
        "in_clusters": {},
        "out_clusters": {
          "0x0021": {
            "endpoint_attribute": "green_power",
            "attributes": {},
            "unsupported_attributes": {}
          }
        }
      }
    }
  }
}

Logs
Logs
[Paste the logs here]

Custom quirk
Custom quirk
[Paste your custom quirk here]

Additional information
No response

I also have this device.
I tried using this quirk but it didn't work at first.
I added another Endpoint (242) and after some tweaking I got it to use the quirk when connecting the device.
However, while it shows an entity for gas detection, it doesn't react when I test the device.
I think it may be using a different attribute then the linked quirk.
My device diagnostics are attached, if anyone can help to fix the quirk so it works with this device.
zha-bdd3c06377f38529ecc9fdcb9ca57872-_TZE204_chbyv06x TS0601-b4f66de4a2cdde186916db2ca4189c85.json (2).txt

@tidharmor
Mind sharing your modifications?

My quirk file is attached.
ts0601_gas_leak.txt

@tidharmor  Thank you. I use your quirk with ZHA. But during Alarm I don\t receive Alert in HA. Maybe you have a fix?

I have the same issue, no event nor state change triggered in HA when gas/CO2 is detected, when using the custom quirk provided above by Tidhamor.
Does anyone have a working custom quirk for it?

up

I worked on @tidharmor's shared modification and got a solution to the issue.
Now the device shows the entity and reacts when I test.
ts0601_gas__TZE204_chbyv06x.py.txt
Thanks guys

@RenatoLemons Thank you for sharing your update of the custom quirk! I tested it and it works like a charm for me, much appreciated!
@antoweb @guslma @OleksiiSaviuk @jacadcaps @tidharmor --> if you guys are still interested in a fully working version for the gas/CO2 sensor, you might want to try the custom quick file shared by RenatoLemons.

@GuidoC1 tested, works fine with the new quirk.

I worked on @tidharmor's shared modification and got a solution to the issue. Now the device shows the entity and reacts when I test.
ts0601_gas__TZE204_chbyv06x.py.txt
Thanks guys

Many thanks (I had same issue), i've just loaded it also and it's working perfect :)

Can an update  brick a quirk ? my TZE204_chbyv06x doesn't work with ZHA and quirk.

Can an update brick a quirk ? my TZE204_chbyv06x doesn't work with ZHA and quirk.

Used this quirk today with current HA build and it works fine.

I worked on @tidharmor's shared modification and got a solution to the issue. Now the device shows the entity and reacts when I test.
ts0601_gas__TZE204_chbyv06x.py.txt

Hi there!
@RenatoLemons quirk works. Thanks! But - I have this device in Tuya wifi version also, and there apart of alarm state it shows also LEL (lower explosive level) in %. It is very sensitive and nicely reacts even on burning gas stove. Do you have any idea how to get to this data?


fixes #1818

Coverage increased (+0.05%) to 54.597% when pulling 715d87dc80b3684d7bd5a9cb8cd4fa0b7636c6b0 on reasonerjt:fix-prepare into 411b43bf0c87a6586ea3b48fc056212bc7f376e1 on vmware:dev.


Nested BrowserRouter

Bug
Version
4.0.0
Test Case
https://codepen.io/anon/pen/NgXNxE?
Steps to reproduce

Click "Home" link
Click "Exchange" link
Click "Message link"
Click again to "Exchange" link

Expected Behavior
View "Subroute Home page." header
Address bar also changes
Actual Behavior
View "Subroute message." header
Don't follow to SubrouteIndex
Addressbar not handle route change

You shouldn't nest BrowserRouter ever. If you need an isolated Router, use MemoryRouter.

But how implement nested routing with handling it in address bar?

You can't do that. The top level BrowserRouter is going to create a history instance that will listen to pushState events. There is no way to do what you're looking to do in any version of React Router.

Thx a lot!

I expect wanting to have a nested BrowserRouter may be a common requirement in large applications.
In our case, this is solely so that:

We are able to set a basepath on a descendent of a BrowserRouter, that affects all descendent router components
React Router applications can be distributed as modules and live within parent applications that also use React Router

I looked in to the issues described by @timdorr above and think I have a solution.
I created a NestedBrowserRouter component that uses the parent router's history but adds a basepath:
https://github.com/penx/nested-browser-router
I have put a demo usage here:
https://codesandbox.io/s/q4l9vo1m89
    <BrowserRouter>
      <>

Application

        <Link to="/">Home</Link> | <Link to="/sub">Sub app</Link>
        <Switch>
          <Route exact path="/" render={() =>
Home
} />
          <Route
            path="/sub"
            render={() => (
              <NestedBrowserRouter basename="sub">
                <>

Sub app

                  <Link to="/">Sub Home</Link> | <Link to="/sub">Sub Sub</Link>
                  <Switch>
                    <Route exact path="/" render={() =>
Sub Home
} />
                    <Route exact path="/sub" render={() =>
Sub Sub
} />
                  </Switch>
                </>
              </NestedBrowserRouter>
            )}
          />
        </Switch>
      </>
    </BrowserRouter>
  );

Caveats:

This requires React Router @4.4 which is still in beta
I've only proven a basic use case here, would be interested in feedback and to hear if this works for all use cases. We are planning to use this in production on a large scale, modularised React application that lives across multiple repositories.


Propagate ConsumerGroup status to KafkaSource

We cannot mark the KafkaConditionConsumerGroup as ready until
the underlying ConsumerGroup is ready.
Signed-off-by: Pierangelo Di Pilato<EMAIL_ADDRESS>/assign @aavarghese

/retest


TYPO: Elastic CI for AWS

Old
The stack connects to the Buildkite API to retrieve the autoscaling metrics to spins up and down EC2 instances based on the build activity. You’ll need to create a Buildkite API Access Token for the Elastic CI Stack to use:

New
The stack connects to the Buildkite API to gather autoscaling metrics and build activity to scale up or scale down the number of EC2 instances. You’ll need to create a Buildkite API Access Token for the Elastic CI Stack to use:

Thanks @drusellers! Much appreciated 🎉
I started adding your feedback in and got a little carried away moving things around 😄 That PR should be merged and live shortly.

:100:


Output steps as they happen

Ideally it'd be nice to know what steps are being ran 👍

Yep, i will have a look at that, thanks :)

I have it working, just have to tweak it a little bit :)

Fixed :)


Inheritance mapping on generic types

The issue
If you have different types that are related in some way, when you try to map all the "Many-to-Many" relationships via a single table using a discriminator column, adding a new migration fails.
Exception message:
Stack trace:
System.InvalidOperationException: The entity type 'NewsPageDocument' cannot inherit from 'Relationship<Page, LibraryItem>' because 'NewsPageDocument' is not a descendent of 'Relationship<Page, LibraryItem>'.
   at Microsoft.EntityFrameworkCore.Metadata.Internal.EntityType.HasBaseType(EntityType entityType, ConfigurationSource configurationSource, Boolean runConventions)
   at Microsoft.EntityFrameworkCore.Metadata.Internal.InternalEntityTypeBuilder.HasBaseType(EntityType baseEntityType, ConfigurationSource configurationSource)
   at Microsoft.EntityFrameworkCore.Metadata.Builders.DiscriminatorBuilder.HasValue(InternalEntityTypeBuilder entityTypeBuilder, Object value)
   at Microsoft.EntityFrameworkCore.Metadata.Builders.DiscriminatorBuilder`1.HasValue(Type entityType, TDiscriminator value)
   at Website.Dal.DatabaseContext.<>c.<OnModelCreating>b__3_4(EntityTypeBuilder`1 e) in C:\Source\EF-Demo\EntityFrameworkCore\src\Website\Dal\DatabaseContext.cs:line 56
   at Microsoft.EntityFrameworkCore.ModelBuilder.Entity[TEntity](Action`1 buildAction)
   at Website.Dal.DatabaseContext.OnModelCreating(ModelBuilder modelBuilder) in C:\Source\EF-Demo\EntityFrameworkCore\src\Website\Dal\DatabaseContext.cs:line 50
   at Microsoft.EntityFrameworkCore.Infrastructure.ModelSource.CreateModel(DbContext context, IConventionSetBuilder conventionSetBuilder, IModelValidator validator)
   at System.Collections.Concurrent.ConcurrentDictionary`2.GetOrAdd(TKey key, Func`2 valueFactory)
   at Microsoft.EntityFrameworkCore.Internal.DbContextServices.CreateModel()
   at Microsoft.EntityFrameworkCore.Internal.LazyRef`1.get_Value()
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScoped(ScopedCallSite scopedCallSite, ServiceProvider provider)
   at Microsoft.Extensions.DependencyInjection.ServiceProvider.<>c__DisplayClass16_0.<RealizeService>b__0(ServiceProvider provider)
   at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetService[T](IServiceProvider provider)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitTransient(TransientCallSite transientCallSite, ServiceProvider provider)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, ServiceProvider provider)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitTransient(TransientCallSite transientCallSite, ServiceProvider provider)
   at Microsoft.Extensions.DependencyInjection.ServiceProvider.<>c__DisplayClass16_0.<RealizeService>b__0(ServiceProvider provider)
   at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService(IServiceProvider provider, Type serviceType)
   at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService[T](IServiceProvider provider)
   at Microsoft.EntityFrameworkCore.Design.Internal.MigrationsOperations.AddMigration(String name, String outputDir, String contextType)
   at Microsoft.EntityFrameworkCore.Design.OperationExecutor.AddMigrationImpl(String name, String outputDir, String contextType)
   at Microsoft.EntityFrameworkCore.Design.OperationExecutor.OperationBase.<>c__DisplayClass3_0`1.<Execute>b__0()
   at Microsoft.EntityFrameworkCore.Design.OperationExecutor.OperationBase.Execute(Action action)
The entity type 'NewsPageDocument' cannot inherit from 'Relationship<Page, LibraryItem>' because 'NewsPageDocument' is not a descendent of 'Relationship<Page, LibraryItem>'.

Steps to reproduce
EntityFrameworkCore.zip
Load the project in the attached zip file.
Build solution (No Errors)
Go to "Package Manager Console"
Type: "Add-Migration "test"
See error.
Expected result
In my example project, as NewsPage is a Page and Document is a LibraryItem, I expect this to detect the inheritance chain correctly and apply the relevant mapping.
Further technical details
EF Core version: found in project.json (v1.1.0)
Operating system: Windows 10 Pro
Visual Studio version: VS2015 Community

The problem is that you are trying to map NewsPageDocument and ProductPageImage as if they have the both inherit from Relationship<Page, LibraryItem>, but they do not.
modelBuilder.Entity<Relationship<Page, LibraryItem>>(e =>
{
    e.ToTable("PageLibraryItems");
    e.HasKey(r => new {r.ParentId, r.ChildId});
    e.HasOne(r => r.Parent).WithMany().IsRequired().OnDelete(DeleteBehavior.Restrict);
    e.HasOne(r => r.Child).WithMany().IsRequired().OnDelete(DeleteBehavior.Restrict);
    e.HasDiscriminator<string>("Type")
        .HasValue<NewsPageDocument>(nameof(NewsPageDocument))
        .HasValue<ProductPageImage>(nameof(ProductPageImage));
});

NewsPageDocument inherits Relationship<NewsPage, Document> and ProductPageImage inherits Relationship<ProductPage, Image>. I realize that both NewsPage and ProductPage inherit Page and that Document and Image inherit LibraryItem... but that's not how inheritance works with generic in .NET (not specific to EF at all).
To demonstrate this, if you run the following code, you'll see that x is true, and y is false.
var x = typeof(Relationship<ProductPage, Image>).IsAssignableFrom(typeof(ProductPageImage));
            var y = typeof(Relationship<Page, LibraryItem>).IsAssignableFrom(typeof(Relationship<ProductPage, Image>));


docs: python-runtime and container-runtime runners

Fixes #1605
This updated README includes information about the python-runtime and container-runtime runners along with the existing deno-runtime runner. It provides usage instructions and examples for each runtime.

Need to fix the markdown lint issues. I think running make markdownlint-fix on your local branch then pushing those changes will fix at least most of the errors.

@StackScribe  I  will correct it and rise PR today

@Nitishupkr please also check my comment above. the issue has new updates. also, please use this PR and don't create a new one

@Nitishupkr the python-runtime and deno-runtime are now properly named and all moved in this new path https://github.com/keptn/lifecycle-toolkit/tree/main/runtimes I would suggest we either close this pr since the issue is stale, or we do move the file with your changes as a read me in the runtimes folder

Due to inactivity, we are closing this PR, if you want to work on it further, feel free to reopen it or open a new one


Monitoring

I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.

we require python3. and better without log4j, but can fix in later PR. we can merge once the license comments are added


iOS - floating cursor

@MagTuxGit  Please try this and let me know. Thanks!

@MagTuxGit I think you care most about https://github.com/singerdmx/flutter-quill/pull/518/files#diff-60c7745a42cf72ae5b3efa03ea85e3464e770f04295ba56a6a09e1cff764a728


colab install issue

@mediummandoo it looks like you didn’t do the pip install and there it cannot find the package.
You might need to restart the notebook kernel for the changes to take effect.

@mediummandoo it looks like you didn’t do the pip install and there it cannot find the package. You might need to restart the notebook kernel for the changes to take effect.

I feel like I asked a foolish question as a complete beginner, so I'm sorry. Thank you for answering.


ci: merge staging to master

This is an automatic PR generated by the pipeline CI/CD. This will be automatically fast-forward merged if successful.

Pipeline Attempt on<PHONE_NUMBER> for fe32230e55e2831b12739975fda81faad9b81c3c
https://gitlab.com/MatrixAI/open-source/js-ws/-/pipelines/1015454347

Pipeline Succeeded on<PHONE_NUMBER> for fe32230e55e2831b12739975fda81faad9b81c3c
https://gitlab.com/MatrixAI/open-source/js-ws/-/pipelines/1015454347


doc says I must define radosgw_interface or radosgw_address.  What if I have no rgw?

What happened:
doc says I must define radosgw_interface or radosgw_address.  What if I have no rgw?

@dmick it's a wrong indication in the doc, you don't have to define those variables if you don't have rgw. Will push a PR to clarify in the doc, thanks.


Terminal error while running npx commands (from meow dependency)

After updating to the lastest version I can no longer run npx prismic-ts-codegen.
If I try to build the types the following error appears:
➜ npx prismic-ts-codegen init
file:///Users/andrelergier/Developer/test/node_modules/meow/source/options.js:52
		throw new Error(errorMessages.join('\n'));
		      ^

Error: The option `alias` has been renamed to `shortFlag`. The following flags need to be updated: `--config`
    at validateOptions (file:///Users/andrelergier/Developer/test/node_modules/meow/source/options.js:52:9)
    at buildOptions (file:///Users/andrelergier/Developer/test/node_modules/meow/source/options.js:87:2)
    at meow (file:///Users/andrelergier/Developer/test/node_modules/meow/source/index.js:91:24)
    at file:///Users/andrelergier/Developer/test/node_modules/prismic-ts-codegen/dist/cli.js:12:13
    at ModuleJob.run (node:internal/modules/esm/module_job:194:25)

Node.js v18.16.0

Versions

@prismicio/client: 7.0.0
prismic-ts-codegen: 0.1.7
node: v18.16.0

Reproduction
I reproduced the issue with creating a new repository and following the steps described in the readme.
As soon as I run the following command the error already appears as well:
npx prismic-ts-codegen init

Additional Details

package.json-File:
{
  "name": "slice-library",
  "version": "0.1.0",
  "main": "index.ts",
  "types": "index.ts",
  "scripts": {
    "lint": "eslint \"**/*.ts*\"",
    "build": "npx prismic-ts-codegen && npm run lint"
  },
  "dependencies": {
    "@prismicio/client": "^7.0.0",
    "@prismicio/react": "^2.5.2",
    "next": "^13.4.0",
    "ui": "*"
  },
  "devDependencies": {
    "@types/node": "18.16.0",
    "@types/react": "18.2.0",
    "@types/react-dom": "18.2.0",
    "eslint": "8.39.0",
    "eslint-config-custom": "*",
    "prismic-ts-codegen": "^0.1.7",
    "react": "^18.2.0",
    "react-dom": "^18.2.0",
    "tsconfig": "*",
    "typescript": "5.0.4"
  }
}

Has this anything to do with the newest version or the update to @prismicio/client v7?
Thank you for your support.

I just saw your new 0.1.8 release. 🙂
The error still appears in my repository...
"prismic-ts-codegen": "^0.1.8"

Hey @andre-lergier, sorry for the trouble!
Could you try the latest release, v0.1.9?
We don't have proper tests for the CLI yet, which unfortunately resulted in some faulty releases.

Hi @angeloashmore
Thank you for the quick release - you saved my day!
Now it works again...


I want to change the cidr，according the doc, but it does not affect

What happened:
I want to change the default cidr <IP_ADDRESS>/10 to <IP_ADDRESS>/10. Then exec the sealer apply -f Clusterfile command,but it does not affect.
What you expected to happen:
the cidr change，and ip change
How to reproduce it (as minimally and precisely as possible):
First metod:

sealer run kubernetes:v1.19.8  ...
change the Clusterfile

metadata:
  annotations:
    ClusterfileName: /root/.sealer/Clusterfile
  creationTimestamp: null
  name: my-cluster
spec:
  hosts:
...
status: {}
---
apiVersion: sealer.aliyun.com/v1alpha1
kind: Config
metadata:
  name: calico
spec:
  path: etc/custom-resources.yaml
  strategy: merge
  data: |
    apiVersion: operator.tigera.io/v1
    kind: Installation
    metadata:
      name: default
    spec:
      calicoNetwork:
        ipPools:
        - blockSize: 26
          cidr: <IP_ADDRESS>/10 #需与kubeadm配置中cidr一致
          encapsulation: VXLANCrossSubnet
          natOutgoing: Enabled
          nodeSelector: all()

sealer apply -f Clusterfile

Second metod:

make kubeadm.yml:

---
apiVersion: kubeadm.k8s.io/v1beta2
kind: ClusterConfiguration
kubernetesVersion: v1.19.8
networking:
  # dnsDomain: cluster.local
  podSubnet: <IP_ADDRESS>/10
  serviceSubnet: <IP_ADDRESS>/22

make custom-resources.yaml:

# This section includes base Calico installation configuration.
# For more information, see: https://projectcalico.docs.tigera.io/v3.22/reference/installation/api#operator.tigera.io/v1.Installation
apiVersion: operator.tigera.io/v1
kind: Installation
metadata:
  name: default
spec:
  # Configures Calico networking.
  registry: sea.hub:5000
  calicoNetwork:
    # Note: The ipPools section cannot be modified post-install.
    ipPools:
    - blockSize: 26
      cidr: <IP_ADDRESS>/10
      encapsulation: VXLANCrossSubnet
      natOutgoing: Enabled
      nodeSelector: all()

---

# This section configures the Calico API server.
# For more information, see: https://projectcalico.docs.tigera.io/v3.22/reference/installation/api#operator.tigera.io/v1.APIServer
apiVersion: operator.tigera.io/v1
kind: APIServer
metadata:
  name: default
spec: {}

make Kubefile:

#Kubefile
FROM kubernetes:v1.19.8
COPY kubeadm.yml etc
COPY custom-resources.yaml etc

sealer build -t xwc1125-kubeadm-kubernetes:v1.19.8 .
sealer run xwc1125-kubeadm-kubernetes:v1.19.8  ...
err:

{"gitVersion":"v0.8.5","gitCommit":"f9c3d99","buildDate":"2022-04-28 14:16:58","goVersion":"go1.16.15","compiler":"gc","platform":"linux/amd64"}

The default configuration image repository is incorrect, you can add in kubeadm.yml:
---
apiVersion: kubeadm.k8s.io/v1beta2
kind: ClusterConfiguration
kubernetesVersion: v1.19.8
imageRepository: sea.hub:5000
networking:
  # dnsDomain: cluster.local
  podSubnet: <IP_ADDRESS>/10
  serviceSubnet: <IP_ADDRESS>/22

First method or Second?

second @xwc1125

The second method is successful. Thanks very much!
By the way, why did the first method go wrong?

The second method is successful. Thanks very much!
By the way, why did the first method go wrong?

maybe the same issue as #1482


in 2.2 alpha there is no implementation of "if" statement in batch mode

Hi,
I was really relying on your "if" in batch mode but I've found out that it was introduced in 2.1.7(which was really hard to find unless you compiled it from sources).
Unfortunately in 2.2 alpha there is no "if" either.
Please add it.
Best regards

HI @fr3ak666
2.2 alpha was released before "if" was implemented.
I suggest you to build it from sources, just checkout "develop" branch and run
mvn clean install

As an alternative, you can wait for next RC1, it should be available in a few days
Thanks
Luigi


Uses react dom portals for portal version when portalId is provided

Changes

providing portalId when used in conjunction with withPortal will render the portal version calendar in a ReactDOM portal (using the Portal component).
Removes confusing logic of inline portals. Inline always renders the calendar. Providing the withPortal prop only wrapped the calendar in the portal class.
Adds documentation for portal versions rendered with ReactDOM portals.
Removes documentation for InlinePortal which was not used.
Adds documentation for toggling an Inline calendar.
Tests inline prop will ignore withPortal prop
Tests withPortal and portalId will render a portal version with the portalId

Can you confirm this doesn't break any of the existing behaviors or does this require a major release?

I don't think this requires a major release. Really what this does is give consistency to the 'portalId' attribute. As for the inline prop change, as I mentioned providing the withPortal prop ended up just wrapping it in the portal class (so render the calendar full page but you'd have no way to dismiss the calendar because it's also inline). To me that made no sense in terms of when it would be used and the documentation never actually demonstrated that behavior nor did any tests. That's why I opted to just simplify the code and write the docs and tests to clarify the expected behavior. If you disagree I can add back that behavior and I'll write the tests/docs to support it as well.


Generic Aspects OpenAPI v2 API(GET /v2/entity/{entityName}/{entityUrn}/{aspectName}) not working as expected

Describe the bug
Generic Aspects OpenAPI v2 API(GET /v2/entity/{entityName}/{entityUrn}/{aspectName}) not returning the requested aspect data for the provided aspectName
Version: v0.13.1
To Reproduce
Steps to reproduce the behavior:

Try to fetch any aspect data with the OpenAPI V2 API GET /v2/entity/{entityName}/{entityUrn}/{aspectName}
example: http://localhost:9002/openapi/v2/entity/datasets/urn%3Ali%3Adataset%3A%28urn%3Ali%3AdataPlatform%3Ahive%2CSampleHiveDataset%2CPROD%29/structuredProperties
here on the above example we tried to fetch the structuredProperties(aspectName) assigned to a dataset(entityName) urn
urn%3Ali%3Adataset%3A%28urn%3Ali%3AdataPlatform%3Ahive%2CSampleHiveDataset%2CPROD%29
Response:

{
  "systemMetadata": {
    "properties": null,
    "registryName": null,
    "registryVersion": null,
    "lastObserved":<PHONE_NUMBER>791,
    "lastRunId": "no-run-id-provided",
    "runId": "no-run-id-provided",
    "pipelineName": null
  },
  "value": {
    "name": "SampleHiveDataset",
    "platform": "urn:li:dataPlatform:hive",
    "origin": "PROD"
  }

Though the structured properties are assigned to the dataset, the API is not returning the data.
Expected behavior
structuredProperties data should be returned by the API
Screenshots
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.

This is already fixed on latest master branch now


write EPIPE error

Bug summary
When I run npm run dev, it compiles successfully but shows this error:
Error: write EPIPE
      at _errnoException (util.js:1022:11)
      at WriteWrap.afterWrite [as oncomplete] (net.js:880:14)

Expected behavior
No error message
Actual behavior
EPIPE error

Error: write EPIPE
      at _errnoException (util.js:1022:11)
      at WriteWrap.afterWrite [as oncomplete] (net.js:880:14)

Steps to reproduce the problem

git clone git@github.com:Shopify/shopify-demo-app-node-react
create .env file
npm install
npm run dev

Reduced test case
This lib reproduces.
Specifications

Browser: Chrome 74
Device: Desktop
Operating System: macOS 10.13.6

Hi @tim-phillips I've recently made some changes to the repo. Let me know if you're still experiencing this.


Installation via pip failing

The version uploaded to the PyPI repo seems to be missing a CMakelists.txt:
Failed to build pyscf
Installing collected packages: pyscf
    Running setup.py install for pyscf ... error
    ERROR: Command errored out with exit status 1:
     command: /usr/bin/python -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-m4au67r2/pyscf_660d58bc048641c6a59afff7a8102f1f/setup.py'"'"'; __file__='"'"'/tmp/pip-install-m4au67r2/pyscf_660d58bc048641c6a59afff7a8102f1f/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-2dqydpw5/install-record.txt --single-version-externally-managed --compile --install-headers /usr/include/python3.10/pyscf
         cwd: /tmp/pip-install-m4au67r2/pyscf_660d58bc048641c6a59afff7a8102f1f/
    Complete output (10 lines):
    running install
    /usr/lib/python3.10/site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
      warnings.warn(
    running build
    running build_ext
    Configuring extensions
    cmake -S/tmp/pip-install-m4au67r2/pyscf_660d58bc048641c6a59afff7a8102f1f/pyscf/lib -Bbuild/temp.linux-x86_64-3.10
    CMake Error: The source directory "/tmp/pip-install-m4au67r2/pyscf_660d58bc048641c6a59afff7a8102f1f/pyscf/lib" does not appear to contain CMakeLists.txt.
    Specify --help for usage, or press the help button on the CMake GUI.
    error: command '/usr/bin/cmake' failed with exit code 1
    ----------------------------------------
ERROR: Command errored out with exit status 1: /usr/bin/python -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-m4au67r2/pyscf_660d58bc048641c6a59afff7a8102f1f/setup.py'"'"'; __file__='"'"'/tmp/pip-install-m4au67r2/pyscf_660d58bc048641c6a59afff7a8102f1f/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-2dqydpw5/install-record.txt --single-version-externally-managed --compile --install-headers /usr/include/python3.10/pyscf Check the logs for full command output.

Everything works fine with the version 2.0.1 downloaded from GitHub and installed locally

@quosta, thanks for letting us know you're having problems. I think this is a duplicate of #1112 so I'm going to close it, but if you disagree feel free to reopen.


missing isBrowser function in util package triggers an exception

Since "ibm-cos-sdk": "1.10.0", the isBrowser function seems to be missing in master/lib/util.js. Thus the following exception will be thrown if using the SDK.

Thank you for your report. Could you provide more details about your code and environment? I can use 1.10.0 and a simple script to create, list, get, put, and delete objects and buckets without seeing this exception.

@IBMeric basically we instantiate the SDK like this:
import IBMS3 from "ibm-cos-sdk/clients/s3"

new IBMS3({
			endpoint: endpoint,
			serviceInstanceId: storageInstanceId,
			sslEnabled: true,
			s3ForcePathStyle: true,
			// @ts-ignore
			tokenManager: {
				getToken: function () {
					return { accessToken: token };
				}
			}
		});

On the instance we then call upload with the following upload options:
uploadOptions = {
  Bucket: auth.bucket,
  Key: key,
  Body: body,
  progressEventListener: /* some function */
};

Not sure whether this helps answering your question. I am also available on IBM Slack, feel free to reach out.

@IBMeric - any updates? I've hit the same issue while upgrading from "ibm-cos-sdk": "1.9.0" -> "ibm-cos-sdk": "1.10.0"
Some changes in this diff must cause the problem

https://github.com/IBM/ibm-cos-sdk-js/compare/1.9.0...1.10.0

Our code fails in this line (running in a browser environment) because AWS.util.isBrowser is not a function
https://github.com/IBM/ibm-cos-sdk-js/blob/b86487e106df1d4d4d545384c2c20ed6c4e02001/lib/http.js#L115
The stack trace that lead to the invocation of this line is below
# the exact line numbers I have access to wouldn't help because they refer to bundled code on our side
 at HttpRequest.getUserAgentHeaderName
 at HttpRequest.setUserAgent
 at new HttpRequest
 at new Request
 at features.constructor.makeRequest
 at features.constructor.svc.<computed> [as putObject]
 at ManagedUpload.nextChunk
 at ManagedUpload.fillBuffer
 at ManagedUpload.send

Below lines were removed in the referenced diff and at least look suspicious:
https://github.com/IBM/ibm-cos-sdk-js/blob/9bec9207a1df0404d3cfeef42234cdea501a5253/lib/util.js#L38-L39
Is there anything else you need to drive this forward?

This seems to be an interaction issue with the way the SDK is being used. When using require('ibm-cos-sdk'), everything works as expected. When only importing from a directory in the SDK, the above exception can happen. The workaround is to add those two lines above back in. This issue has been reproduced and is being tracked internally.
For reference: https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-node#node-examples-init

I created a new project from scratch for test purposes and am unable to reproduce the exception (the previous reproduction turned out to be an unrelated problem). Could you provide additional details on differences between this sample code and your project? Since I cannot reproduce the problem in pure Javascript, are you using a dialect? Which one?
npm install ibm-cos-sdk
main.js
import S3 from 'ibm-cos-sdk/clients/s3.js'
import myCreds from './creds.js'

const s3Config = {
		endpoint: 'https://' + myCreds.api_endpoint + ':8443',
		apiKeyId: myCreds.ibm_api_key,
		serviceInstanceId: myCreds.ibm_service_instance_id,
		ibmAuthEndpoint: myCreds.ibm_auth_endpoint,
		signatureVersion: 'iam',
		// accessKeyId: myCreds.aws_access_key_id,
		// secretAccessKey: myCreds.aws_secret_access_key,
		// signatureVersion: 'v4',
		s3ForcePathStyle: true,
};

var s3Client = new S3(s3Config);

async function main() {
  var bucketName = `cos-${Date.now()}`;
  console.log('createBucket');
  var createBucketParams = {Bucket: bucketName, CreateBucketConfiguration: {LocationConstraint: ''}};
  var response = await s3Client.createBucket(createBucketParams).promise();
  console.log('deleteBucket');
  response = await s3Client.deleteBucket({Bucket: bucketName}).promise();
  console.log('Complete!');
}

main();

package.json
{
  "type": "module"
}

Thank you for the project. I have been able to reproduce the issue in Firefox 88. The problem appears to be an interaction with React that could also apply to other frameworks. I need to discuss this internally and have opened a tracking ticket.

With some researches I have found a temporary solution.
Just adding this line in the ibm-cos-sdk/lib/utils.js into the var util :
isBrowser: function isBrowser() { return process && process.browser; },
/!\ this fix is not viable for production (it's a local only fix) but it's a good start for further long term fix by IBM.
Please fix it quickly!

@rrodriguez06 isn't this exactly the line that was removed and thus did cause the breakage?

Yes exactly. All the call to the isBrowser function still reffered it in util even if it was moved to another file/var

@IBMeric  @modean
For those who are still experiencing this issue, here is an hotfix of the problem.
const AWS = require('ibm-cos-sdk')
AWS.util.isBrowser = function isBrowser() { return process && process.browser; };
AWS.util.isNode = function isNode() { return !AWS.util.isBrowser(); };

it's a bit tricky !

Sorry for a delayed response. I've tested a resolution against @daka1510's project. I no longer see output in the browser console. The plan is to publish this fix in the next point release. Currently there are some other fixes we are working on. If those appear to require too much time, we'll do a separate update for this fix.

@IBMeric - can you share a rough release timeline for this fix?

The release will either be this week or early next week.

@modean We have published 1.10.1, and I have verified that @daka1510's example project prints no errors to the console. Could you verify your issue is resolved and then close this ticket?

Closing this issue as resolved.

@IBMeric I verified the published version 1.10.1 locally and it seems to be working.


mediaarea.net website down invalid certificate & PPA error

Hi. For the past two or so days the website has been down.
Checking https://downforeveryoneorjustme.com/mediaarea.net?proto=https results in:

Is Mediaarea.net down?
Checking if mediaarea.net is down or it is just you...
It's not just you! mediaarea.net is down.

I was alerted to this when attempting a repo update:
Fatal error: E: The repository 'https://mediaarea.net/repo/deb/ubuntu focal Release' no longer has a Release file.
W: Updating from such a repository can't be done securely, and is therefore disabled by default.
W: See apt-secure(8) manpage for repository creation and user configuration details.
E: https://mediaarea.net/repo/deb/ubuntu focal Release is not (yet) available (Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate.  Could not handshake: Error in the certificate verification. [IP: <IP_ADDRESS> 443])

Thank you for the report.
It seems that the certificate was not updated in one place, it is fixed.

Thanks!


Moving the suite is not smooth

Ex: I created different suites and trying to move the suite to another suite is not smooth, sometimes its creating under the different suite. Is there any smooth way of doing this or only Drag and Drop ?
FYI - I am using new(UX) test plans page
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 3c520dee-1218-777e-7405-551623817c03
Version Independent ID: 82b5d172-ae1a-2b4c-82ac-595cd7609d3c
Content: New test plans page - Azure Test Plans
Content Source: docs/test/new-test-plans-page.md
Product: devops
Technology: devops-test
GitHub Login: @ravishan-msft
Microsoft Alias: ravishan-msft

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

Azure DevOps Support Bot
Azure DevOps on Stack Overflow

@ravishan-msft -- please look into this issue.


Include pages in the search index

fixes #18

Lovely @emohamed, will have a look at it this afternoon :-)

Hey @emohamed!
Thanks a bunch for making #18 real 👍
I amended a few stuff, most notably splitting the Promise to isolate the Post fetching and the Pages fetching. Also, for now, I restricted the Pages fetching to { layout: 'page' } items.
Released in v1.2.0. With a CHANGELOG now!
Thanks again :-)

Glad to help, thanks for the great package!


DLL load failed after migrating to 4.0.28

Environment

Python: 3.7.0 (64-Bit)
pyodbc: 4.0.28
OS: Windows (64-bit)
DB: MS SQL Server 2008 R2
driver: ODBC Driver 17 for SQL Server

Issue
On "import pyodbc" I'am getting the following message: "ImportError: DLL load failed: Não foi possível encontrar o módulo especificado.". Works fine with version 4.0.27.
Test code:
import pyodbc
DRIVER='{ODBC Driver 17 for SQL Server}'
SERVER=r'localhost\SQLEXPRESS'
DATABASE=''
UID=''
PASSWORD=''
def get_connection_string():
return 'DRIVER=%s;SERVER=%s;DATABASE=%s;UID=%s;PWD=%s' % (DRIVER, SERVER, DATABASE, UID, PASSWORD)
def exec_query_raw(sql):
with pyodbc.connect(config.get_connection_string(), autocommit=True) as cnxn:
results = list(cnxn.cursor().execute(sql))
return results
print(exec_query_raw(sql='SELECT * FROM '))

Duplicate of #663

Thanks gordthompson.  Let's close this and work on the other.


Use yt-dlp's progress_template for simplifying progress data

yt-dlp has an argument, --progress-template, that permits customising the output template of the progress bar.  This should be used for stability (as per the yt-dlp README), and for simplicity when parsing progress output.

This will require changing:

checking which lines show progress
checking speed
checking percentage

This has been completed in the subprocess runner, but needs to be done for the playlist handler.  However, both may become moot if the yt_dlp package is used directly (which would be the better way).  So I will merge in the change for the subprocess runner, but the branch and ticket will remain open for now.

Closing: Subprocesses are no longer used for downloads


chore: add better regression test

Contributor checklist

[ ] Bug fixes include regression tests
[ ] Features include unit/acceptance tests

🚀 Thank you for your contribution! 🚀


Add a flag to only allow move to next word if the current word is correct

Please, add a flag that only allow move to next word if the current word is correct.
That flag will force the user to correct the current word if it's wrong.

I don't know if it fits in the current project, but I'm already working on this feature for myself.
What I'm in trouble is to find a good name for that flag.
If anyone knows one, please tell me.


Update fi.coffee

@toivomattila could you sign our CLA so we can accept your PR?

I signed the CLA, should be good now :+1:

Thanks!


ncluster ls doesn't account for spot instance price

Needs something like this, with a join on instance name
# print instance_id, price
from ncluster import aws_util as u

client = u.get_ec2_client()
spot_requests = []
for request in client.describe_spot_instance_requests()['SpotInstanceRequests']:
    if not: request['State'] == 'active: continue
    print(request['InstanceId'], request['SpotPrice'])

# print instance_id, instance name
for i in u.lookup_instances():
    print(i.instance_id, u.get_name(i))

it's also under Lifecycle field


fix the suppressiong handling for the same bug

Suppressing the same bug twice should not fail.
For the second suppression nothing should change.
The suppress comment from the first suppression is kept.
Resolves  #334
Added test for double suppression

LGTM!


Activating Alt key shortcuts prints the character in the terminal

When I press Alt+W (to access the Window menu - to Dock/Float/etc), it prints a 'w' character in the terminal. When I press Alt+F, it prints an 'f'.
Can we have VS handle all Alt key shortcuts and not pass any to the terminal?
(Not sure if that's a good idea. I couldn't think of any reason to use an Alt shortcut in the terminal.)

I'll look into adding it as a preference that you can change but the current behavior will probably remain the default. I can't think of a reason that you might want Alt shortcuts in the terminal but there may be a reason that I am unaware of.

Given we can't find a good reason to use Alt keys in the terminal, and given that Alt keys are really useful for everything else - particularly accessing the Menu with accelerator keys, can we say this IS a desired feature that should be implemented (if time and energy permit)?

I do agree that this feature should be implemented. I just think that it shouldn't be the default (especially since VSCode behaves that way).

Well then, VS Code should change their behavior. At least for VS users, the default should be to let VS handle the Alt keys, otherwise a user's ability to use VS is hampered.
If there are users who want the Alt key handled by the terminal, they should opt-in to that behavior. (IMO)

Fixed, alt key combos no longer print in the terminal in 1.0

Thanks Daniel! :-D


Update ember-cli-babel

The ember-cli-babel dependency should be updated to the latest version to allow consuming apps to drop ember-cli-shims as a dependency of ember 2.16+ apps.
https://www.emberjs.com/blog/2017/11/20/ember-2-17-released.html#toc_changes-in-ember-cli-2-17

I think this is resolved, just needs a release.

When will this be released?

Since it's unclear if/when master will be cut into a new release, I published a fork at @alexlafroscia/ember-pikaday from the current master branch (commit e367b56a242fd1cafb1940788bcac2308b31fa53)

note that deprecation warnings will appear when on a newer version of ember (3.3)
DEPRECATION: ember-cli-babel 5.x has been deprecated. Please upgrade to at least ember-cli-babel 6.6. Version5.2.8 located: my-app -> ember-pikaday -> ember-cli-babel
DEPRECATION: ember-cli-babel 5.x has been deprecated. Please upgrade to at least ember-cli-babel 6.6. Version5.2.8 located: /my-app/node_modules/ember-pikaday/node_modules/ember-cli-babel

This is going to become critical as ember-cli 3.4 seems to drop support for addons which have not updated in https://github.com/ember-cli/ember-cli/pull/7774#issuecomment-384677373

@alexlafroscia thank you for publishing a new release, it's taking the pressure off.

@alexlafroscia If you're up for maintaining this package take a look at https://www.npmjs.com/policies/disputes
NPM has a clear process for adopting an abandoned package and making your fork official.

Maybe we can do this more formally, if people are interested in that. I don't mind taking over maintenance duties, but maybe we can transfer ownership to https://github.com/adopted-ember-addons and do something on the NPM side to allow a group of people to publish updates from that repo.
@edgycircle would that be OK with you?

@alexlafroscia can you volunteer over in #195

I'll join that conversation, thanks @jrjohnson!

Okay, seeing as I just released a real version of 2.2.5 on the official ember-pikaday package, I'm going to close this.
If you've using my fork at @alexlafroscia/ember-pikaday, please move back to the original ember-pikaday. The 2.2.5 package is identical to my fork's 2.2.5.


Table not applied well in mobile environment

What version of Hugo are you using (hugo version)?

$ hugo version

Hugo Static Site Generator v0.68.3/extended linux/amd64 BuildDate: 2020-03-25T06:15:45Z
Does this issue reproduce with the latest release?
yes
PC version

Mobile

In mobile environment, is there any ways to apply table format on the page? I took the way like below.

| High | Close | MDD  |
| ---- | ----- | ---  |
| 9.53%| 5.87% | 3.05%|

only for Samsung Internet
it shows well like PC version in Safari, Chrome mobile env.


Kokkos adding CUDA Toolkit dep unnecessarily?

Comment:
The PennyLane feedstock recipe includes Kokkos and Kokkos-kernels. The Lightning subpackage expects the SERIAL backend, although OPENMP might be there without impacting the build. After adding the CUDA backend however, the build fails because libcuda.so is not found. This happens either during build, when the new package with the CUDA backend is pulled, or during tests, when the new package is pulled even though the old package was used to build. I'm thus wondering, does it mean that all packages with Kokkos as a dependency now have to have CUDA-variants builds, even though they are not using CUDA whatsoever?

No, they can depend on the non-CUDA build variant.

Thanks, makes sense. I wonder why the test section pulled the CUDA variant.

It shouldn't be possible to install the CUDA variant in an environment without the __cuda virtual package.

@jakirkham, how do we prevent conda from installing the CUDA variant in non-__cuda environments?

For example, I have this issue here. I have CUDA_VERSION=None, etc. and I build with Kokkos-3.7.01 (a workaround for now since it's trying to use the CUDA variant), but in the tests, it is still installing Kokkos-3.7.02 with cudatoolkit==11.8.0-h37601d7_11.

Lemme know if #24 fixed issues with kokkos 3.x. If not, we may need to mark some packages as broken. If so, then I'll port the changes to kokkos 4.

#24 fixes the issue with Kokkos 3.x. Thanks a bunch @carterbox


Initiate NodeHelper before running build

There a chance something downstream is preventing test runs on
Docker platforms because the NodeHelper isn't initiated prior to
the build (which was the case prior to an earlier commit).
Signed-off-by: Adam Farley<EMAIL_ADDRESS>

If someone else wants to take the risk on this approach based on "There a chance something downstream" then they are welcome to, but I'm not personally willing to sign this one off for inclusion during a GA cycle. I'd prefer a more conrete understanding that this will resolve things.
"Needed for the Oct 2020 release" isn't quite true as an alternative would be initiating the test jobs manually for the two platforms (Linux/x64 and Linux/aarch64) affected by this.

Just pointing out that "initiating the test jobs manually for the two platforms (Linux/x64 and Linux/aarch64) affected by this" = manually submitting 216 jobs.

add to whitelist

run tests

Hmm, PR builder error is:
org.jenkinsci.plugins.workflow.cps.CpsCompilationErrorsException: startup failed:
Script2.groovy: 753: unable to resolve class NodeHelper
 @ line 753, column 47.
   NodeToBecomeActive(def label, NodeHelper
                                 ^
Script2.groovy: 804: unable to resolve class NodeHelper
 @ line 804, column 36.
                           NodeHelper nodeHelper = context.library(identifier: 'openjdk-jenkins-helper@master').NodeHelper

Maybe it'd work if we:

call "context.library(identifier: 'openjdk-jenkins-helper@master').NodeHelper" in the build method, while ignoring the return object.
remove NodeHelper from the wait method's params
and call "context.library(identifier: 'openjdk-jenkins-helper@master').NodeHelper" in the wait method while not ignoring the return object.

Done, with a helpful comment.
Proved to fix the build-test flow on docker, as evidenced here: https://ci.adoptopenjdk.net/job/build-scripts-pr-tester/job/build-test/job/jobs/job/jdk8u/job/jdk8u-linux-x64-openj9/444/console
The only change needed, in the end, was a simple library load. Added a helpful comment so the user knows what's going on.


Broken tests due to new numpy version

Some tests depend upon autograd-backed grcwa, which have started failing due to changes in numpy. It seems autograd will not be updated to address the issue. https://github.com/HIPS/autograd/pull/618
We should perhaps set up CI so that autograd-dependent tests run using a pinned version of numpy.

Hi there, we released a new version of Autograd: https://github.com/HIPS/autograd/releases/tag/v1.7.0, which includes NumPy v2 support. It will be available via PyPI later in the day.


"for"-template not initially selected

VSCode Version: 1.5.0-insider
OS Version: Windows 10, Build 14901

Steps to Reproduce:

Open a c# file
Write "for"
You have to press (Down) and (Tab) to use the "for"-template, it's not possible to write "for" and press (Tab) to use that template on the go.
Selecting the template initially would speed up coding.

This issue was moved to OmniSharp/omnisharp-vscode#659

@johanneskopf This is not a bug - as of VSCode 1.4 "editor.snippetSuggestions": "top" can be used to change the default VSCode behavior.

Thanks for the hint!
It's working great using that setting.


DOCS: Moving skills and knowledge guides to taxonomy

Description: Moving the skills_guide and knowledge_guide files to the taxonomy repo. Removing the files in community and fixing the links.
Additional info:
Updates in taxonomy in this PR - https://github.com/instructlab/taxonomy/pull/777

YAY! 👍

We probably should not merge this until after https://github.com/instructlab/taxonomy/pull/777 is merged.


Folder structure for Gherkin files

With a reference to step 5 of the Readiness Checklist (https://github.com/camaraproject/Commonalities/blob/main/documentation/API-Readiness-Checklist.md), I would like to agree with you on the folder structure for the Gherking files placement. My idea is to create a folder named “Test” under the already existing folder “code”.
In the Test folder all the APIs can place their Gherkin file (api_name.feature) or they can create a new  subfolder folder named Cucumber if they also provide some code.

@FabrizioMoggio I like the idea, would the structure be one Test directory per API folder, e.g.
/EdgeCloud/code/API_Definitions/Discovery/Test/
/EdgeCloud/code/API_Definitions/Traffic_Influence/Test/
or one Test folder under code? i.e. structure is then
/EdgeCloud/code/API_Definitions/Discovery/foo.yaml
/EdgeCloud/code/API_Definitions/Traffic_Influence/bar.yaml
/EdgeCloud/code/API_Definitions/Test/foo.feature, bar.feature....
WDYT?

@Kevsy actually my proposal was based on the old folder structure without the subfolders for each API. Let's consider how it is done in QoD, they decided to go not just with the ".feature" file but with the complete Cucumber solution, that is optional. We should support both the possibilities. For this reason I would suggest to have anyway a "Test" folder with inside or just the ".feature" file or the Cucumber folder structure.
For this reason I suggest to use your option 1:
/EdgeCloud/code/API_Definitions/Discovery/Test/
/EdgeCloud/code/API_Definitions/Traffic_Influence/Test/
QoD/code/cocumber

@Kevsy this issue is related, isn't it?
https://github.com/camaraproject/WorkingGroups/issues/302

Yes - thanks  for adding the reference!

Discussion at Commonalities level:
https://github.com/camaraproject/Commonalities/issues/59

Closing according to the results of https://github.com/camaraproject/Commonalities/issues/59:
The structure is:
https://github.com/camaraproject/Template_Lead_Repository


Docs?

Hi. I'd like to self host this. Are there any docs? If not, how can I get started with creating them?

Hi there's only this https://blog.npub.pro/post/how-to-self-host-on-github/

Thank you so much!.
On Friday, November 1st, 2024 at 6:20 PM, Nostr.Band @.***> wrote:

Hi there's only this https://blog.npub.pro/post/how-to-self-host-on-github/

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.


[BZ-1221830] radosgw pkg is ceph-radosgw on RPM systems

I incorrectly thought in https://github.com/ceph/ceph-deploy/pull/282 that these changes were no longer needed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins.ceph.com//job/ceph-deploy-pull-requests/1589/
Tests passed for this pull request.


[Bug]: Failure: could not clone https://github.com/zitadel/zitadel.git: signal: killed

Preflight Checklist

[X] I could not find a solution in the documentation, the existing issues or discussions
[X] I have joined the ZITADEL chat

Version
2.56.0
Describe the problem caused by this bug
When i try to pnpm generate it is giving me this error . i try to clean up the node modules and all but failed.
To reproduce
just you have to pnpm generate
Screenshots

Expected behavior
it should have generate
Relevant Configuration
No response
Additional Context
No response

hm @peintnermax have you experienced this as well?
I tested it on my mac and did not see this problem 😓

No the error suggests that it is a local connection issue. Our builds work too, so it is not an issue for us.

@khatiwada-Saurav does this error persist?
The git clone happens during the buf generate which loads the latest proto files from zitadel/zitadel

As we didn't get any response anymore, I will close the issue for now.
Feel free to reopen, if you can provide us with more informaiton


Update cub submodule

This was updated in 707aed36e89ab9e2041de25166a4930fc4e24ee7 but a
force push into https://github.com/NVlabs/cub made the commit Caffe2
was pointing to unreachable.
cc @slayton58 @lukeyeager

Also reported at https://github.com/caffe2/caffe2/pull/1085. Apparently there was a forced update to every CUB release branch in order to remove some big files from the history. Clones should be smaller and faster now.


[YUNIKORN-1106] Reduce idle CPU usage (v2)

What is this PR for?
Updated PR for YUNIKORN-1106 which removes the unconditional sleep in favor of a non-blocking channel.
What type of PR is it?

[ ] - Bug Fix
[x] - Improvement
[ ] - Feature
[ ] - Documentation
[ ] - Hot Fix
[ ] - Refactoring

Todos

[ ] - Task

What is the Jira issue?
https://issues.apache.org/jira/browse/YUNIKORN-1106
How should this be tested?
No behavioral changes, so no test updates.
Experimental testing locally results in CPU usage at idle around 0.1%.
Screenshots (if appropriate)
Questions:

[ ] - The licenses files need update.
[ ] - There is breaking changes for older versions.
[ ] - It needs documentation.

FYI: code coverage decrease is due to less lines of code in the patch overall.


Examples on distributed server environment(i.e. scaling-out)

Please, give me comments or example codes to use this torch-distlearn in distributed servers.(i.e. scaling-out)

Hi,
There are example scripts in the examples directory. Folks have used these on their own clusters as well as AWS. No cluster is the same, so you'll need to do some work depending on what type of cluster you want to use.
Thanks,
Zak


Do not trigger panic when there is nothing in the session on lock.Middleware

When GET /auth/login. the request goes into middleware first. so it is always panic since PostAuth is not yet get called. thus nothing is in the session.
I have read this https://github.com/volatiletech/authboss/issues/192. To handle this I have to wrap the lock.Middleware like this
func maybeCheckLockStatus(ab *authboss.Authboss) func(h http.Handler) http.Handler {
	return func(h http.Handler) http.Handler {
		return http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
			if user := (*r).Context().Value(authboss.CTXKeyUser); user != nil {
				lock.Middleware(ab)(h)
			}

			h.ServeHTTP(w, r)
		})
	}
}

I don't see the reason why we need this rather than skip the locking feature

There's no reason that a route that is not a protected resource should ever run many middlewares

Do you conditionally load middlewares in your projects?
And the last, the error notice of this is quite vague. it just a stack of error message with GET /auth/login -> 500 Internal Server Error (panic: user not found). It took me hours to figure out what was wrong.

Any route that wants to deal with users and locking users out (ie. authenticated routes only) should be the ones that have this middleware applied. In my projects using authboss I have middleware sets that routes get added to, if it's an unauthenticated route, lock/loadclientstate/remember all of these middlewares are excluded.
I'd be happy if someone were to add some additional context to the panic, since it's one you should never technically see in production unless things have been configured incorrectly we can add a bit of debugging text around it asking why this middleware is being called before state is loaded or what have you.


fix: bump dotenv dep

Proposed changes

Bumps dotenv package

Fixes
n/a
Types of changes
What types of changes does your code introduce to agents-aea?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist
Put an x in the boxes that apply.

[x] I have read the CONTRIBUTING doc
[x] I am making a pull request against the develop branch (left side). Also you should start your branch off our develop.
[x] Lint and unit tests pass locally with my changes and CI passes too
[ ] I have added tests that prove my fix is effective or that my feature works
[x] I have checked that code coverage does not decrease.
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules

Further comments
n/a

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

Project coverage is 90.26%. Comparing base (af1336f) to head (75d6d8b).
Report is 5 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #721      +/-   ##
==========================================
+ Coverage   90.25%   90.26%   +0.01%
==========================================
  Files         373      373
  Lines       29854    29854
==========================================
+ Hits        26945    26948       +3
+ Misses       2909     2906       -3

Flag
Coverage Δ

unittests
90.26% <ø> (+0.01%)
:arrow_up:

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

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


[1.20.1] Setting respawnHealth inoperate

Setting 'respawnHealth' is inoperate.
Trying to set respawnHealth = 1 doesn't change the player Health to 1 when he dead, but he has full life instead.

There seems to be no issue with this using the latest version. Please make sure that you are using the correct config file. With Forge, you have to use the file in saves/world/serverconfig of each world. Every other modloader (fabric and quilt) use the file in config folder.

You can disable this in config:
in l2configs/l2library-common.toml, set
restoreFullHealthOnRespawn = false
I add that because my mods have curios that adds max health, and MaxHealthFix cannot fix that because curios load attributes after first player tick.

Thanks, it works, but now, it's the mod Aether that breaks this mod.


What's your email?

I haven't been able to find your email on your site or elsewhere. Would you care to share it?
In any case, I really liked your XOR trick post, as well as your book posts.

Thanks! Glad to hear that. :)
Yeah, my email isn't really explicitly listed anywhere.
I think you can only find it if you look at the Git commit metadata.
I just sent you an email though, so you don't have to do that.

Thanks! Glad to hear that. :)
Yeah, my email isn't really explicitly listed anywhere.
I think you can only find it if you look at the Git commit metadata.
I just sent you an email though, so you don't have to do that.


[gardening] Adjust line wrapping and code comments for newly added diagnostic

Minor gardening for the great new diagnostic added by @mininny in #35230.

@swift-ci smoke test and merge


AttitudeControl: let the user set yaw weight directly via parameter

instead of infering the yaw weight from the gains which can lead to
unexpected results depending on the particular vehicle tuning.

This is setting a default of 0.4, what would the defaults have roughly been before? I don't have a feeling for what yaw P gain would be compared to pitch/roll.

@jkflying Good point. I should mention:

The default gain parameters of PX4 made almost exactly a ratio of 0.4.
The paper https://www.research-collection.ethz.ch/bitstream/handle/20.500.11850/154099/eth-7387-01.pdf under chapter 4.2 states that their experimental results were best with 0.4.
During my test flying for my master thesis I also experimented with this weight and around 0.4 gave me the most desirable results.
I made a prototyping script in python with visualization here https://github.com/Auterion/Flight_Control_Prototyping_Scripts/tree/master/quaternion_attitude_control#details in which you can try yourself what value results in which attitude run.

@MaEtUgR this is worth keeping open, right?

I revived this and finished the work:

rebased on master (first commit was existing)
fixed the yaw output scaling which was like expected broken with the original first draft
Added unit tests to verify that the yaw output scaling is correct and doesn't result in division by zero

I found a better implementation for the exact same thing and squashed my commits.

@PX4/testflights Could you please do a quick test on this with focus on multicopter yawing? Stabilized, Altitude, Position, Mission just check if yaw tracking looks like expected.

Tested NXP FMUK66 V3
Modes Tested

Position Mode: Good.
Altitude Mode: Good.
Stabilized Mode: Good.
Mission Plan Mode (Automated): Good.
RTL (Return To Land): Good.

Procedure
Arm and Take off in position mode, after flying for approximately one minute, switched to altitude then stabilized mode proceed to switch to mission plan mode then make sure that vehicle follows all waypoints as shown in QGC, once completed all waypoint then trigger RTL.
Notes
No issues noted, good flight in general.
Logs

https://review.px4.io/plot_app?log=2b83350f-df29-4956-8fd8-7b226b6c9923
https://review.px4.io/plot_app?log=1dd134b3-b12a-448d-a2bf-3e6d6e7524f5

Tested Pixhawk 3 V4Pro
Modes Tested

Position Mode: Good.
Altitude Mode: Good.
Stabilized Mode: Good.
Mission Plan Mode (Automated): Good.
RTL (Return To Land): Good.

Procedure
Arm and Take off in position mode, after flying for approximately one minute, switched to altitude then stabilized mode proceed to switch to mission plan mode then make sure that vehicle follows all waypoints as shown in QGC, once completed all waypoint then trigger RTL.
Notes
Vehicle does not detect all Flight Modes Switches, Top = Stabilized ; Mid = Altitude (Undetected No Flight Mode Change) ; Bot = Position (Switched to altitud) RC Work with no issue on other vehicles.
Logs

https://review.px4.io/plot_app?log=b28b4721-682c-47ce-a8f9-1d47740b2756

Tested on pixhawk4 v5 f-450
Modes Tested
Position Mode: Good.
Altitude Mode: Good.
Stabilized Mode: Good.
Mission Plan Mode (Automated): Good.
RTL (Return To Land): Good.
Procedure
Arm and Take off in position mode, after flying for approximately one minute, switched to altitude then stabilized mode proceed to switch to mission plan mode then make sure that vehicle follows all waypoints as shown in QGC, once completed all waypoint then trigger RTL.
Notes
No issues noted, good flight in general.
Logs
https://review.px4.io/plot_app?log=aa76011d-28d7-413b-81b5-3fb3047e9b65
https://review.px4.io/plot_app?log=f85caf4c-973d-43d9-9904-640ddcfb237a

Tested on PixRacer V4
Modes Tested
Position Mode: Good.
Altitude Mode: Good.
Stabilized Mode: Good.
Mission Plan Mode (Automated): Good.
RTL (Return To Land): Good.
Procedure
Arm and Take off in position mode, after flying for approximately one minute, switched to altitude then stabilized mode proceed to switch to mission plan mode then make sure that vehicle follows all waypoints as shown in QGC, once completed all waypoint then trigger RTL.
Notes
The following issue was not seen in this PR "In altitude mode, the vehicle did not respect the height that continued to increase in pitch forward"
We are unsure if this was due to the lack of strong winds on the field today.
Logs
https://review.px4.io/plot_app?log=54f0c926-14eb-47de-a996-6a0ee3f33710
https://review.px4.io/plot_app?log=f667ae28-5495-4694-ae36-b85ddff54698
Tested on CUAV nano V5
Modes Tested
Position Mode: Good.
Altitude Mode: Good.
Stabilized Mode: Good.
Mission Plan Mode (Automated): Good.
RTL (Return To Land): Good.
Procedure
Arm and Take off in position mode, after flying for approximately one minute, switched to altitude then stabilized mode proceed to switch to mission plan mode then make sure that vehicle follows all waypoints as shown in QGC, once completed all waypoint then trigger RTL.
Notes
No issues noted, good flight in general.
Logs
https://review.px4.io/plot_app?log=4f4c2181-b7ea-4707-b46b-345b58c3c0ca
https://review.px4.io/plot_app?log=cd036b34-a4c4-4764-af43-1277d34552b4

Thanks so much for testing!


DO NOT MERGE, work in progress

added functionality for default values and config changes
the correct command is already given, but it is not executed correctly

was implemented in another way


ci: update bee version

Closes #677

That is already part of the workflow: https://github.com/ethersphere/bee-js/blob/master/.github/workflows/update_bee.yaml#L48

Release v5.0.0 addresses this.


Added C Cheat Sheet

Hacktoberfest notes:

due to volume of submissions, we may not be able to review PRs that do not pass tests and do not have informative titles.
please read our contributing guidelines
be sure to check the output of Travis-CI for linter errors
if this is your first open source contribution, make sure it's not your last!

What does this PR do?
Add Resource(s) | Remove Resource(s) | Add info | Improve Repo
For resources
Description
Why is this valuable (or not)?
How do we know it's really free?
For book lists, is it a book? For course lists, is it a course? etc.
Checklist:

[ ] Not a duplicate
[ ] Included author(s) if appropriate
[ ] Lists are in alphabetical order
[ ] Needed indications added (PDF, access notes, under construction)

the trick to getting c++ working in the index is * [C++](#c-1)

Sir please check my current PRs and take a action immediately because today
is the last day of that program Hacktoberfest.
On Fri, 30 Oct 2020, 9:23 pm Eric Hellman<EMAIL_ADDRESS>wrote:

Closed #4913
https://github.com/EbookFoundation/free-programming-books/pull/4913.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/EbookFoundation/free-programming-books/pull/4913#event-3941916931,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMVM2IVX6FFDC22H2LGKBJDSNLOP7ANCNFSM4TE3MUJQ
.


Source packer

btw, I have written a roslyn based source packer... that you might be interested in.  It can take all source files in a CSPROJ and pack them into one file.
It consolidates all usings outside the namespace declarations into one or more targetfiles.
You add comment directives to your files to control the packer...
//!packer:targetFile=LogProviders.cs

Its located here... [post link here]

Theoretically you transform the ..pp files to .cs files, then pack all the bits into a single file... bam... you're back to simple "copy this one file" instructions

Hi @ericnewton76,
In v4 and prior, it was packaged and available as a single file for the following reasons:

In the early days of the project there was no mechanism to install the source code via nuget or other means. Single file here was useful.
Then nuget supported .pp file transform. It was still included in your actual project source code and committed to version control. One file was preferable over littering many files into other peoples source. 3. Not eveyone could use nuget or could use it's transforms (xamarin / mono), so single file helped.
Then the whole vNext -> ASP5 -> DNX -> .NET Core thing happened over a few yers where source code nuget packages and/or transforms not supported. Single file to the rescue...
Then, around .NET core 2.0, the source code transforms became supported again in the SDK as a build task. This time cross platform and works in most platforms. It also went directly to the obj folder and not inside your repo. The single file is no longer necessary.

So as of version 5, the files are split out for my own maintainability reasons and should be totally hidden from the consumer (though fxcop and others still seem to see it...).
 However, for those stuck on old platforms / mechanisms, which you appear to be, they can still use the v4.x line (which I'm willing to patch for a while).
In the end, as @snakefoot mentioned in another thread, LibLog changes very slowly (it's been surprisingly reliable tbh), so for your unique case, fork and copy is totally a reasonable away to go (it's MIT after all).
Cheers.


Test against py35

@@            master      #4   diff @@
======================================
  Files            5       5
  Stmts          213     213
  Branches         0       0
  Methods          0       0
======================================
  Hit            199     199
  Partial          0       0
  Missed          14      14

Review entire Coverage Diff as of a825528

Powered by Codecov. Updated on successful CI builds.

Yes! Now we can async and await!


[RoleManagement] Feature Request: Roles should be removed if required roles are removed.

Is your feature request related to a problem? If so, Please describe.
Role A depends on Role B. If the user loses Role B, Role A stays.
Describe the solution you'd like
Role A should be removed when Role B is removed since the latter is a requirement.
Describe alternatives you've considered if any
N/A
Additional context
Testing was done using requireany.

This has been on my radar for a small bit of time already, but I need to come up with consistent handling of this which properly interacts with all of the other settings without causing a performance drain, which might require slightly more work. (large public instances of red use this cog, so if this becomes too intensive on role removal, this will be an issue)
I'm placing this as a medium-high priority, but compliance with the new discord terms (both with the stuff I'm contributing to core red, and the adjustments to #236 that will be needed) is above this in the list of larger things to handle.

How hard would it be to re-use the extension component from the automod tools? I know you weren't ready to publish that, but it's working and faster than anything else we've tried.

Without testing it, I'm assuming it won't be worth it. The main performance concern is config access, and caching would be irresponsible here. Maybe if I can express this as a single efficient SQL statement, but even that has issues since i would need to have array types and red cant guarantee anything more than sqlite


v3.0.0, sass: several newlines between rules -> bad indent

no config is used
input
div
    top: 0

span
    bottom: 0

output
div
    top: 0

    span
    bottom: 0

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

This is fixed in the latest csscomb release 😄


Add support for llm-chain

Trying to use mistralrs with llamaindex, but it's still quite slow. For my use case, I'm trying to get performance in millisecs. With llamaindex, performance is not ideal.
I'm wondering if I can use mistralrs with llm-chain (it's a Rust-based alternative to llamaindex). I'd be willing to do the work to get the two to work together, but I'm not sure where to start. Can you let me know how I can integrate the two?

That sounds like a great idea.
To implement, the integration, I would recommend looking at how to connect their Executor trait with our Pipeline trait. Mistral.rs is designed around the Engine, which does the overseeing work of processing, scheduling, and running the Pipeline.
Currently, we don't have an embedding API, which we should probably add to implement this. I'm not very familiar with llm-chain so I'm not sure if that is a necessity. If it is, I'll try to add that API, as it has already been on my to-do list for some time.

Thanks for the info.
I'm going to close this for now as I've got another project I'll be working on for the next few weeks. If I have the time afterward, I'll reopen the issue and work on the solution.


Ebuild depends on x11-libs/libva[X,opengl] but opengl use flag isn't supported upstream

The ebuid declares a runtime dependency for x11-libs/libva[X,opengl]. But x11-libs/libva does not support the opengl use flag, see https://packages.gentoo.org/packages/media-libs/libva.

The issue you are describing doesn't seems to be fixable here.
I recommend to send this bugreport to the Gentoo bugtracker, as there are much higher chances it will be at least seen there. I doubt Gentoo maintainers closely monitor this place.


expose all settings in optimizers to constructor

What is the expected enhancement?
As we update all pluggable class with concrete constructors, will it better we also promote all setting in parameters to the init method.
Thus, we do not need to call the set_options method.
I know that the reason we had this set_options is that in scipy, those setting are needed to be set in a dict.

resolved by #282


more efficient sample op

@eytan
Another thing that I found was rather inefficient was the sample op since if we're only sampling 5 elements from a 1000 element population it doesn't make sense from an efficiency standpoint to have to iterate through all 1000 of them.
Due to the way that the Fisher-Yates algorithm works, we know that for if we are on iteration i, then the elements for n - i + 1 are fixed.  We can still have the same desirable properties from a statistical perspective (i.e. every element has an equal probability of being in the sample + in any arbitrary position in the sample - I did some quick calculations to verify this + the sample op tests still pass but I would appreciate some double checking of this) with our sample op if we early return once we have k elements (where k is the number of draws) that are fixed. As the segment size increases this can make a real impact performance-wise.
Running the namespace initialization benchmarks gets the following results now (which are a slightly skewed test for this since they only allocate 5 segments for each added experiment, but the differences are still meaningful):
Result w/ compatibility turned on:<PHONE_NUMBER>003899 ms over 500 runs
Result w/ compatibility turned off (without this sampling change): 19.26401599845849 ms over 500 runs
Result w/ compatibility turned off + this change: 0.4321100015658885 ms over 500 runs
In the worst case this is just as bad as without the changes, but for the average case it's much better.
This of course breaks compatibility with other implementations + previous versions of the JS implementation, but we should consider changing this in the ref implementation.

This sounds awesome!  I'll try to take a closer look soon, and also verify that the unit test is doing the right thing... In the meantime, do you have a proof that this works correctly?

@eytan yea I'll try to write it out tomorrow to verify (or disprove :)) its correctness tmw- I'm currently on a train with 5% battery left on my laptop.

Really nice work. Since Fisher-Yates only ever swaps elements at a smaller or equal index, as you said, there should be no difference in the distribution of samples. This is a great optimization! :)
I'm starting to wonder though if it might be worth thinking about a better abstraction for the compatibility vs non-compatibility mode. Right now it's still quite readable, and the hashing implementation doesn't really leak outside of the random ops module, but maybe it will make the verification of the statistics involved, and producing optimized bundles simpler.

Quick proof of correctness for this:
Effectively a sample is a random permutation of size k which means that there are n! / (n-k)! samples for a sample size of k. All we have to show is that with early return from the fisher-yates shuffle each permutation has probability (n-k)! / n! to occur.
We'll pick an arbitrary permutation of k elements and show that it has (n-k)! / n! probability of being the selected permutation by the algorithm. The first position in the permutation has probability 1 / n of being selected. After this step, the element is fixed in that position and we select from the remaining n - 1 options. The second position in the permutation has probability 1 / n -1 of being selected, etc. up until the kth element in the permutation which has probability 1 / n - k + 1 probability of being selected. This means that the probability of this arbitrary permutation being selected after k iterations of the algorithm is  (1 / n) * (1 / n - 1) * (1 / n - 2) * ... * (1 / (n - k + 1)) = (n-k)! / n!. Since the selection of the original permutation was arbitrary this allows to all k permutations which is precisely what we want.

@TimBeyer would be happy if you came up with a proposal. One thing that's important (at least from my perspective) is having a way to slowly transition existing namespaces / experiments onto using the non-compatible version as it would become possible to transition them (i.e. their segment size would hit 0). I'm not sure entirely certain that the current compatibility toggle supports that well, but I think that including multiple bundles may make such efforts unnecessarily difficult and costly. Let me know if you can think of a good solution to the issue.

I'm leaning towards just turning compatibility off by default and having it be opt-in. If other people complain that they need a more clear upgrade path for namespace by namespace then I think it's worth investing time in, but I think it's unneeded unless explicitly requested. @TimBeyer would you be fine with that?

I believe this would be fine for us since assignments are persisted in cookies and reassignments happen automatically once experiments are added or concluded. So current membership would stay the same, new membership would be assigned according to the new hashing, following the same distribution, and once experiments change everyone would be assigned using the new hashing.

Hi @rawls238 -- this all looks good: the modification seems straightforward and solid, and this is such a huge performance improvement that compatibility mode should definitely be off by default.  One thing to note though is that the original sample() unit test is not particularly rigorous: it only tests to make sure that, for example, given 1, 2, 3 draws from a list of elements yields their expected probabilities; it does not actually check whether the expected subsequences occur with equal probability.

:+1: going to merge this and then add some docs and release a new version.


updated readme of cartoonify Image folder

Related Issuse or bug

Info about Issue or bug

Fixes: #182
Proposed Changes

Added images that describes the issue in a subfolder of the cartoonify image folder

Additional Info

Anything related Issues

Screenshots
Before:

After:

@akshitagupta15june please check the pr


feat(#201): Check bytecode for RuleAllTestsHaveProductionClass

Check bytecode for RuleAllTestsHaveProductionClass rule.
Closes: #201

PR-Codex overview
Clearly explain the focus of this PR in less than 300 characters. Then write "
Detailed summary
" followed by all notable changes formatted as a bullet list. Be specific and concise.

The following files were skipped due to too many changes: src/test/java/com/github/lombrozo/testnames/rules/RuleAllTestsHaveProductionClassTest.java, src/main/java/com/github/lombrozo/testnames/rules/RuleAllTestsHaveProductionClass.java, src/main/java/com/github/lombrozo/testnames/bytecode/BytecodeProject.java

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@rultor merge

@rultor merge

@volodya-lombrozo OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@volodya-lombrozo Done! FYI, the full log is here (took me 3min)


Add filter: All / Filters / Actions

GET Param + on page links

Done in develop branch
Done in next version -> 1.1


cmtk: 3.3.1 -> 3.3.2; fix darwin build

Description of changes
changelog: https://www.nitrc.org/frs/shownotes.php?release_id=4738

update to 3.3.2
fix darwin build
add some buildInputs

Things done

Built on platform(s)

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

[x] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 236810 run on x86_64-linux 1

1 package built:

cmtk


It seems 1.0.5-beta broken in browser

I reverted webpack library target to umd. bcoz "var" library target was not working in nodejs.
I am investigating umd load problem with scriptjs

It will be perfect! Now I use static linked scripts for TS and AS

I guess, this might be the problem

are you using rawgit.com?

I use rawgit.com of course.
Check tests my script.js repo. This test pass in vanilla js but fail inside react.js environment=(

Modern browsers ignore MIME type. But recommend use application/javascript. Never mind, script always load successfully.Main problem with assignment to global scope

I am closing this issue as this cannot be fixed from this repo.

sure


Fix for #3190

Short Description:
Recent refactor can return an empty list
Fixes:
when we would normally return the empty list, return the original list

I think we have the problem in a few other files. I'll keep an eye on my logs.
Good, and quick, work!


Content QA

Hello, I just noticed a couple small editorial inconsistencies and wanted to list them here for addressing:

[x] There are two periods in a sentence in the About text on this page: http://gcappbesp307/dev-test/beta/data-explorer/walking-driving-and-cycling/?id=2112#display=summary

[x] The last heading in this one isn't formatted like the other headings (it's in regular body text).  https://a816-dohbesp.nyc.gov/IndicatorPublic/beta/data-stories/aq-cooking/

[x] There is a repeated sentence in this story: https://a816-dohbesp.nyc.gov/IndicatorPublic/beta/data-stories/localtemp/

"As the climate changes, NYC faces rising average temperatures and heat waves that place New Yorkers at risk. Already more than 100 New Yorkers die each year due to extreme heat. Even modest cooling can save lives, and cooling neighborhoods with trees and other vegetation is a critical step we can take to protect people from hot weather. Even modest cooling can save lives

[x] Fix typo in Read Me

Thank you!

Comment filed in EHDP-data re: a typo in "Recent driving" indicator description, so I'll close this issue.

There is a typo in Block by Block in the 1969 text block. "the" is misspelled.


fix for #998 Reseting scrollUp/scrollLeft to scrollToRow/scrollToColumn incorrectly

The original fix #1001 for the issue #998 is reverted because of failing tests due to upgrading to React 16. I create two tests to verify that scrollUp/scrollLeft are not reset to scrollToRow/scrollToColumn when recompute grid size with index less than scrollToIndex.
closes #998
Before submitting a pull request, please complete the following checklist:

[x] The existing test suites (npm test) all pass
[x] For any new features or bug fixes, both positive and negative test cases have been added
[ ] For any new features, documentation has been added
[ ] For any documentation changes, the text has been proofread and is clear to both experienced users and beginners.
[x] Format your code with prettier (npm run prettier).
[x] Run the Flow typechecks (npm run typecheck).

Here is a short checklist of additional things to keep in mind before submitting:

Please make sure your pull request description makes it very clear what you're trying to accomplish. If it's a bug fix, please also provide a failing test case (if possible). In either case, please add additional unit test coverage for your changes. :)
Be sure you have notifications setup so that you'll see my code review responses. (I may ask you to make some adjustments before merging.)

The original fix https://github.com/bvaughn/react-virtualized/pull/1001 for the issue https://github.com/bvaughn/react-virtualized/issues/998 is reverted because of failing tests due to upgrading to React 16.

My problem is exactly the same as https://github.com/bvaughn/react-virtualized/issues/1148. This PR should solve it.

#998 specifically discusses scrollToIndex, can we get a test case verifying that specific behavior being fixed?

@aem That's what the tests in this PR do. If you revert the changes, these two test should fail.

sorry. didn't scroll down far enough. that's my fault

@aem , we got the same issue and we need this PR is merged soon to resolve our issue. I think the change is good enough. If you think we have another way to fix, let us know when possibly we can fix the issue. Thanks

cc: @dcolens. I didnt get a chance to fix the broken tests after the rewrite. But this MR will have it in!

Hi there, can you brief when will you patch this?

@sytranvn I would say within a week!

Thanks @wuweiweiwu

Hey @wuweiweiwu,
I haven't seen this patch released. Can you tell me when will this patch be released?
Thank you :)

@sytranvn there are some more bugs that I want to fix before the next patch release. Thanks for your patience

@wuweiweiwu I'd also love to see a patch release for this. Unless you're addressing new bugs that have only been present on master since 9.20.0, it'd be great if you could release now, and release again with those additional bug fixes later.
🍻

I see. That makes sense. I'll try to release tomorrow!

Released in version 9.20.1!


The error is unclear when the preview of parquet files fails

Storage Explorer Version: 1.33.0 (97)
Build Number: 20240404.6
Branch: dev/cralvord/hotfix-build
Platform/OS: Windows 10/Linux Ubuntu 22.04/MacOS Sonoma 14.4(Apple M1 Pro)
Architecture: x64/x64/arm64
How Found: From running test cases
Regression From: Previous release (1.32.1)
Steps to Reproduce

Expand one storage account -> Blob Containers.
Create a blob container -> Upload the parquet file 'brotli.parquet'.
Preview the parquet file -> There is a failed activity log.
Check whether the error is clear.

Expected Experience
The error is clear.

Actual Experience
The error is unclear.

Additional Context
Below are two files that can reproduce this issue.
brotli.zip

A fix has been merged. Messages are now less vague. Please keep in mind that the specific BROTLI error message is different, but a specific message is still displayed.

Verified this issue on the hotfix build 20240409.2. Reproduce. So, we are going to reopen it.

The build I sent you did not contain the fix. Please verify on a new build.

Verified this issue on the hotfix build 20240410.2. The error is clear.


Make CircuitParameters#init public

Hi, it seems that CircuitParameters#init should be public as it is not possible to instantiate it.

Fixed in https://github.com/IBM-Swift/SwiftyRequest/commit/5b64cccbc1dd986632c4ae22be409fb095c15c75


Additional filters in karyon2-admin container

config param to introduce additional filters to admin resources.
While it defaults to no different behavior than current state, it provides an extension point to provide extra tomcat filter behavior that is pluggable in karyon2-admin container

@elandau thanks for the review, good catch on redirect filter issue.