Fix issue where some info tables load in html and others do not

Possible table classes include infobox (see stegosaurus) and wikitable (see Cretaceous)

Temporarily avoided by removing tables from included content


is there a way to add additional animation to a body? Example: polygon fades in as it falls or animates in from the side before gravity takes effect

Not with the built in debug renderer, if you need to do anything fancy I'd suggest creating your own, see Rendering. A place to start is to copy the code of Matter.Render.

so with this:
var render = Render.create({
element: document.body,
engine: engine,
options: {
width: 500,
height: 500,
pixelRatio: 5,
background: (250, 250, 250, 0),
wireframeBackground: '#222',
hasBounds: true,
enabled: true,
wireframes: false,
showSleeping: true,
showDebug: false,
showBroadphase: false,
showBounds: false,
showVelocity: false,
showCollisions: false,
showSeparations: false,
showAxes: false,
showPositions: true,
showAngleIndicator: false,
showIds: true,
showShadows: false,
showVertexNumbers: false,
showConvexHulls: false,
showInternalEdges: false,
showMousePosition: false,
}
});
should be able to? What is the syntax for something like a fade in animation?

There's nothing built in for animations. This library focuses on just the physics, for anything other than basic rendering you'll need to build it or use some rendering library like THREE.js or Pixi.js.


Not able to add to cart

I am getting a 404 for the "add to cart" functionality. I checked everything else works. I am using playa-mesos customized to run on 192.168.xxx.yyy. The nginx app as launched through marathon is running on port 31000.
Here are the HTTP request and response headers for the "Add to cart" function :-
Request headers
GET /%5Bobject%20XMLDocument%5D/GET/f61496e5-b1b5-6a80-6d28-393b30b46e78 HTTP/1.1
Host: <IP_ADDRESS>:31000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:44.0) Gecko/20100101 Firefox/44.0
Accept: */*
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
DNT: 1
X-Requested-With: XMLHttpRequest
Referer: http://<IP_ADDRESS>:31000/
Connection: keep-alive

Response headers
HTTP/1.1 404 Not Found
Server: nginx/1.9.1
Date: Fri, 19 Feb 2016 13:34:23 GMT
Content-Type: text/html
Content-Length: 168
Connection: keep-alive

Can you help me fix this to get it to work ?

Hi @ZeroGraviti — sorry for the delay, I have no idea why I don't get these notifications. Anyways, the request path looks strange. There shouldn't be a /%5Bobject%20XMLDocument%5D/ (see also the respective code). Two quick ideas: have you got CORS enabled? And also: which browser are you using?

This trace was generated from UI interaction on Firefox v44.0.2 web browser. I can share results while testing with other browsers too. I had set env var NODE_DEBUG=request to try to understand whats going on in the server side nodejs app and trace results. This is what I have added to the issue above. I have tested the webdis app and the mesos-dns individually (in isolation) and they are working fine. I dont know how to test the sedi app since it is a non-dockerized app which we are deploying into mesos using marathon.
Please let me know your thoughts.

OK, thanks for this info. Is still don't know if you've got CORS enabled (I used a Chrome plugin to allow access for this app, otherwise the front-end can't talk to webdis). Not sure what you mean how to test sedi, since it's part of my Mesos-DNS setup—or did you not launch system.json via Marathon?
Re the sidenote: because that's the API that Webdis exposes ;)

I launched both the json files to create the respective apps in marathon. I believe CORS is enabled in Firefox for sometime now (by default) but I will double check. I could be wrong but I can test this with popular browsers like Chrome etc.. If you can share the exact Chrome version with me it will help. I will try to use vanilla versions of the browsers ( I usually add plugins like ADB and other stuff to block annoying things :) ) and let you know. Another way to triage this is if you can **_disable _**CORS and share your results with me. We can then compare. Either way, let me know how you want to do this.

Tested with CORS enabled in Chrome. Works perfectly. This bug can be closed.

Perfect, thanks!


"No such module" when importing foreign package even though build succeeds

Steps to reproduce:
mkdir LspTest
cd LspTest
swift package init

Add a package to Package.swift e.g.:
// swift-tools-version: 5.9
// The swift-tools-version declares the minimum version of Swift required to build this package.

import PackageDescription

let package = Package(
        name: "LspTest",
        platforms: [.macOS(.v12)],
        products: [
        // Products define the executables and libraries a package produces, making them visible to other packages.
        .library(
            name: "LspTest",
            targets: ["LspTest"]),
        ],
        dependencies: [
        .package(url: "git@github.com:stevengharris/SplitView.git", from: "3.5.0"),
        ],
        targets: [
        // Targets are the basic building blocks of a package, defining a module or a test suite.
        // Targets can depend on other targets in this package and products from dependencies.
        .target(
            name: "LspTest",
            dependencies: [.product(name: "SplitView", package: "SplitView")]
            ),
        .testTarget(
            name: "LspTestTests",
            dependencies: ["LspTest"]),
        ]
        )

Import the module in a .swift file e.g. in Sources/LspTest/LspTest.swift:
// The Swift Programming Language
// https://docs.swift.org/swift-book

import SplitView

sourcekit-lsp returns "No such module" e.g. in Neovim:

Hint
This seems to be a new bug in the development version of sourcekit-lsp. Using the release version, I do not encounter this problem.

Tracked in Apple’s issue tracker as rdar://121696265

Do you still see the issue after building the package? sourcekit-lsp requires a build to find the modules to import.

Yes, the problem persists after deleting the .build folder and building both the debug and release configurations.

Hmm, that’s very odd. Maybe we aren’t finding the build folder. Could you check if the problem persists when you:

Run swift build and wait for it to finish
Make an edit in the file that contains import SplitView
Restart sourcekit-lsp

I followed the steps. I simply added an "x" on a new lined and saved the file before restarting Neovim (restarts lsp too). The issue persists.

Ah, I think I know what might be going on: Do you use sourcekit-lsp from the same toolchain snapshot that contains your swift build or are they from different toolchain version, eg. because you built sourcekit-lsp from source on main? SwiftPM moved the folder that contains the .swiftmodules, changing the compiler arguments that are required to build the file. Since SourceKit-LSP contains its own copy of SwiftPM, the compiler arguments it gets might not be correct to correctly pick up the Swift modules. https://github.com/apple/sourcekit-lsp/pull/1046/files#diff-d58fae5b483fc1623905094d04af6418aa40c2a77652889be608feb158d15a7dR142-R147
Generally speaking, sourcekit-lsp should be used from the same toolchain that the Swift compiler is from. While mixing and matching sourcekit-lsp with different compiler versions often works, there’s no guarantee that it does.

Spot on! I did use the release version of swift (5.9) to build. Now that I build the module with the dev version that my sourcekit-lsp uses, I no longer get the missing module errors :)


Update Docker image on Dockerhub with latest Snakemake workflow and version

Still running snakemake v5 and using htseq

The singularity run command fails with the old Docker image because the conda environment in the Docker image on DockerHub does not contain the correct dependencies


[Snyk] Upgrade: @babel/core, @babel/plugin-transform-runtime, @babel/preset-env

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade multiple dependencies.
👯♂ The following dependencies are linked and will therefore be updated together.

:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

Name
Versions
Released on

@babel/corefrom 7.23.5 to 7.23.6
1 version ahead of your current version
21 days agoon 2023-12-11

@babel/plugin-transform-runtimefrom 7.23.4 to 7.23.6
1 version ahead of your current version
21 days agoon 2023-12-11

@babel/preset-envfrom 7.23.5 to 7.23.6
1 version ahead of your current version
21 days agoon 2023-12-11

Release notes

Package name: @babel/core

7.23.6 - 2023-12-11v7.23.6 (2023-12-11)
Thanks @ martinez-hugo and @ odinho for your first pull requests!
👓 Spec Compliance

babel-generator, babel-parser, babel-types

#16154 Remove TSPropertySignature.initializer (@ fisker)

babel-helpers, babel-plugin-proposal-decorators, babel-plugin-transform-class-properties, babel-plugin-transform-class-static-block, babel-plugin-transform-runtime, babel-preset-env, babel-runtime-corejs2, babel-runtime-corejs3, babel-runtime, babel-types

#16139 Apply toPropertyKey on decorator context name (@ JLHwung)

🐛 Bug Fix

babel-generator

#16166 fix: Correctly indenting when retainLines is enabled (@ liuxingbaoyu)

babel-helpers, babel-plugin-proposal-explicit-resource-management

#16150 using: Allow looking up Symbol.dispose on a function (@ odinho)

babel-plugin-proposal-decorators, babel-plugin-transform-class-properties

#16161 Ensure the [[@@ toPrimitive]] call of a decorated class member key is invoked once (@ JLHwung)
#16148 Support named evaluation for decorated anonymous class exp (@ JLHwung)

babel-plugin-transform-for-of, babel-preset-env

#16011 fix: for of with iterableIsArray and shadowing variable  (@ liuxingbaoyu)

babel-helpers, babel-plugin-proposal-decorators, babel-runtime-corejs2, babel-runtime-corejs3, babel-runtime

#16144 Set function name for decorated private non-field elements (@ JLHwung)

babel-plugin-transform-typescript

#16137 Fix references to enum values with merging (@ nicolo-ribaudo)

🔬 Output optimization

babel-helper-create-class-features-plugin, babel-plugin-transform-class-properties

#16159 Reuse computed key memoiser (@ JLHwung)

babel-helpers, babel-plugin-proposal-decorators

#16160 Optimize decorator helper size (@ liuxingbaoyu)

Committers: 7

Babel Bot (@ babel-bot)
Hugo Martinez (@ martinez-hugo)
Huáng Jùnliàng (@ JLHwung)
Nicolò Ribaudo (@ nicolo-ribaudo)
Odin Hørthe-Omdal Urdland (@ odinho)
@ liuxingbaoyu
fisker Cheung (@ fisker)

7.23.5 - 2023-11-29v7.23.5 (2023-11-29)
👓 Spec Compliance

babel-plugin-proposal-decorators

#16138 Class binding is in TDZ during decorators initialization (@ nicolo-ribaudo)

babel-helpers, babel-plugin-proposal-decorators

#16132 Allow addInitializer in field decorator context (@ JLHwung)

🐛 Bug Fix

babel-traverse, babel-types

#16131 Do not remove bindings when removing assignment expression path (@ nicolo-ribaudo)

babel-plugin-transform-classes

#16135 Require class properties transform when compiling class with private fields (@ nicolo-ribaudo)

babel-generator

#16122 fix: Missing parentheses after line break (@ liuxingbaoyu)

babel-helpers

#16130 Fix helpers internal fns names conflict resolution  (@ nicolo-ribaudo)

babel-helper-create-class-features-plugin, babel-plugin-transform-class-properties, babel-plugin-transform-typescript

#16123 Simplify class fields injetion after super() (@ nicolo-ribaudo)

babel-generator, babel-plugin-transform-modules-commonjs, babel-plugin-transform-parameters, babel-plugin-transform-typescript, babel-traverse

#16110 fix: Unexpected duplication of comments (@ liuxingbaoyu)

babel-eslint-plugin

#16023 Add @ babel/eslint-plugin/no-undef to fix no-undef with accessor props (@ nicolo-ribaudo)

🔬 Output optimization

babel-helpers

#16129 Optimize decorator helper size (@ liuxingbaoyu)

Committers: 4

Babel Bot (@ babel-bot)
Huáng Jùnliàng (@ JLHwung)
Nicolò Ribaudo (@ nicolo-ribaudo)
@ liuxingbaoyu

    from @babel/core GitHub release notes

Package name: @babel/plugin-transform-runtime

7.23.6 - 2023-12-11v7.23.6 (2023-12-11)
Thanks @ martinez-hugo and @ odinho for your first pull requests!
👓 Spec Compliance

babel-generator, babel-parser, babel-types

#16154 Remove TSPropertySignature.initializer (@ fisker)

babel-helpers, babel-plugin-proposal-decorators, babel-plugin-transform-class-properties, babel-plugin-transform-class-static-block, babel-plugin-transform-runtime, babel-preset-env, babel-runtime-corejs2, babel-runtime-corejs3, babel-runtime, babel-types

#16139 Apply toPropertyKey on decorator context name (@ JLHwung)

🐛 Bug Fix

babel-generator

#16166 fix: Correctly indenting when retainLines is enabled (@ liuxingbaoyu)

babel-helpers, babel-plugin-proposal-explicit-resource-management

#16150 using: Allow looking up Symbol.dispose on a function (@ odinho)

babel-plugin-proposal-decorators, babel-plugin-transform-class-properties

#16161 Ensure the [[@@ toPrimitive]] call of a decorated class member key is invoked once (@ JLHwung)
#16148 Support named evaluation for decorated anonymous class exp (@ JLHwung)

babel-plugin-transform-for-of, babel-preset-env

#16011 fix: for of with iterableIsArray and shadowing variable  (@ liuxingbaoyu)

babel-helpers, babel-plugin-proposal-decorators, babel-runtime-corejs2, babel-runtime-corejs3, babel-runtime

#16144 Set function name for decorated private non-field elements (@ JLHwung)

babel-plugin-transform-typescript

#16137 Fix references to enum values with merging (@ nicolo-ribaudo)

🔬 Output optimization

babel-helper-create-class-features-plugin, babel-plugin-transform-class-properties

#16159 Reuse computed key memoiser (@ JLHwung)

babel-helpers, babel-plugin-proposal-decorators

#16160 Optimize decorator helper size (@ liuxingbaoyu)

Committers: 7

Babel Bot (@ babel-bot)
Hugo Martinez (@ martinez-hugo)
Huáng Jùnliàng (@ JLHwung)
Nicolò Ribaudo (@ nicolo-ribaudo)
Odin Hørthe-Omdal Urdland (@ odinho)
@ liuxingbaoyu
fisker Cheung (@ fisker)

7.23.4 - 2023-11-20v7.23.4 (2023-11-20)
🐛 Bug Fix

babel-generator

#16104 fix: Pure comments missing parentheses (@ liuxingbaoyu)

Committers: 4

Babel Bot (@ babel-bot)
Huáng Jùnliàng (@ JLHwung)
Nicolò Ribaudo (@ nicolo-ribaudo)
@ liuxingbaoyu

    from @babel/plugin-transform-runtime GitHub release notes

Package name: @babel/preset-env

7.23.6 - 2023-12-11v7.23.6 (2023-12-11)
Thanks @ martinez-hugo and @ odinho for your first pull requests!
👓 Spec Compliance

babel-generator, babel-parser, babel-types

#16154 Remove TSPropertySignature.initializer (@ fisker)

babel-helpers, babel-plugin-proposal-decorators, babel-plugin-transform-class-properties, babel-plugin-transform-class-static-block, babel-plugin-transform-runtime, babel-preset-env, babel-runtime-corejs2, babel-runtime-corejs3, babel-runtime, babel-types

#16139 Apply toPropertyKey on decorator context name (@ JLHwung)

🐛 Bug Fix

babel-generator

#16166 fix: Correctly indenting when retainLines is enabled (@ liuxingbaoyu)

babel-helpers, babel-plugin-proposal-explicit-resource-management

#16150 using: Allow looking up Symbol.dispose on a function (@ odinho)

babel-plugin-proposal-decorators, babel-plugin-transform-class-properties

#16161 Ensure the [[@@ toPrimitive]] call of a decorated class member key is invoked once (@ JLHwung)
#16148 Support named evaluation for decorated anonymous class exp (@ JLHwung)

babel-plugin-transform-for-of, babel-preset-env

#16011 fix: for of with iterableIsArray and shadowing variable  (@ liuxingbaoyu)

babel-helpers, babel-plugin-proposal-decorators, babel-runtime-corejs2, babel-runtime-corejs3, babel-runtime

#16144 Set function name for decorated private non-field elements (@ JLHwung)

babel-plugin-transform-typescript

#16137 Fix references to enum values with merging (@ nicolo-ribaudo)

🔬 Output optimization

babel-helper-create-class-features-plugin, babel-plugin-transform-class-properties

#16159 Reuse computed key memoiser (@ JLHwung)

babel-helpers, babel-plugin-proposal-decorators

#16160 Optimize decorator helper size (@ liuxingbaoyu)

Committers: 7

Babel Bot (@ babel-bot)
Hugo Martinez (@ martinez-hugo)
Huáng Jùnliàng (@ JLHwung)
Nicolò Ribaudo (@ nicolo-ribaudo)
Odin Hørthe-Omdal Urdland (@ odinho)
@ liuxingbaoyu
fisker Cheung (@ fisker)

7.23.5 - 2023-11-29 Read more

    from @babel/preset-env GitHub release notes

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Updated in 18c44501a849b8954dfb88e59bc7b5d87e1ab9c4.


Add Support For Per-Profile Config Options

If the user is not playing via the Xbox Store version of Outer Wilds, allow the user to use mod config options that apply either only to their profile or to every profile that uses Global settings.
At the top of a mod’s config settings, there will be a checkbox added by OWML that says “Use Global Settings,” with the tooltip “Use and edit the Global Settings, which will affect all other profiles that use the Global Settings. Turning this off will make your settings apply only to the active profile.”
Use Global Settings will be on by default, and make the configs act as they do now, applying the settings to every profile that has the Use Global Settings option on. Turning it off will allow the user to set their own custom settings, specific to their needs, without affecting other profiles.
Due to the lack of profiles on the Xbox version, the Xbox version will always use the Global settings and the checkbox to turn it off will not appear.
Implementing a per-profile config will require a new config file format, which I will detail in a separate issue.

This is a companion issue to https://github.com/ow-mods/owml/issues/582


storage - storeAll and external

@joyceerhl this builds on top of and is a replacement to https://github.com/microsoft/vscode/pull/185605 and https://github.com/microsoft/vscode/pull/185810
@sandy081 maybe see how the new storeAll method is used in your areas, it should work as before but now storage change events will only be emitted at the end.

Looks good.


[Auth] Email & Name not being retrieved when using Apple Sign-In

Describe the bug
When using Apple Sign-In, the Apple credential has the user name and email, then, registering (or binding) the credential to Firebase using both idToken and authorizationToken, will result in the FirebaseUser not having neither displayName nor email associated.
To Reproduce
Steps to reproduce the behavior:

Use either apple_sign_in or (sign_in_with_apple)[https://pub.dev/packages/sign_in_with_apple] to create a valid Apple sign-in;
Create an AuthCredential using OAuthProvider getCredential() method;

Expected behavior
Expect the user to have name and email — doesn't happen.
Additional context
firebase_auth: 0.15.5+3
Flutter doctor
Run flutter doctor and paste the output below:
[✓] Flutter (Channel stable, v1.12.13+hotfix.9, on Mac OS X 10.15.4 19E287,
    locale pt-PT)
    • Flutter version 1.12.13+hotfix.9 at /Users/miguelruivo/devtools/flutter
    • Framework revision f139b11009 (4 weeks ago), 2020-03-30 13:57:30 -0700
    • Engine revision af51afceb8
    • Dart version 2.7.2

Hey @miguelpruivo
I believe this is working as intended;
Apple only returns the full name and email on the first login on the device for your app, it will return null values for these on any login after that.
For testing purposes, to receive these again; go to your device settings; Settings > Apple ID, iCloud, iTunes & App Store > Password & Security > Apps Using Your Apple ID, tap on your app and tap Stop Using Apple ID. You can now sign-in again and you'll receive the full name and email again.
This is how Apple has designed their API - so it's recommended that you store these elsewhere on your app, e.g. using the shared_preferences plugin - so that you consistently have access to them when required.

@Salakar I'm aware of that, and this happens on a fresh install as soon as the first binding is made. I expect that when a sign in to Auth uses the credential with a name & email, those should be kept on the auth credential itself, which definitely aren't.
Am I missing something?
Thanks.

How are you requesting the credential from Apple, are you adding the email & full name scopes?

@Salakar sure. Like I said, when debugging, I can see the name & email are there. Then, immediately after
final AuthorizationResult appleSignin = await AppleSignIn.performRequests([
      AppleIdRequest(
        requestedScopes: [Scope.email, Scope.fullName],
        requestedOperation: OpenIdOperation.operationLogin,
      )
    ]);

  if (appleSignin.status == AuthorizationStatus.authorized) {
      OAuthProvider oAuthProvider = OAuthProvider(providerId: "apple.com");

  // Until this point, I can access the email & password from `appleSignin` credential.
    credential = oAuthProvider.getCredential(
        idToken: String.fromCharCodes(appleSignin.credential.identityToken),
        accessToken: String.fromCharCodes(appleSignin.credential.authorizationCode),
      );
    }

FirebaseUser user = await _auth.signInWithCredential(credential); // here, the user doesn't have it.

Thanks for the code example;
Is this just iOS that has the issue? Are you using any other OAuth providers and seeing the same behaviour?

Currently I'm only using Sign In with Apple on iOS devices so I can't really tell if this is happening on Android as well — I believe that's less common to have users logging with Apple on Android devices anyway.
As for the second question, this is the only OAuth provider that I'm using. Both Facebook and Google have their own static methods to get an auth credential (ie., FacebookAuthProvider.getCredential() and so on).

@Salakar Any news on this? This seems like an easy fix. The info is there. As of now, the apple sign lacks usability as this is supposed to replace registration. Not having the name or an email we get an incomplete registration and then we need to ask the user a name, manually. @miguelpruivo thanks for opening this issue.

@Salakar Any news on this? This seems like an easy fix. The info is there.

What would you suggest the fix be, could you send a PR over for it if it's still an issue on the latest auth release?

Re-open. The issue still persists.

Can you please open this issue again i am having the same issue too


Exception Handling for Network Offline State in Broadcast API

What this PR does / why we need it?
This PR introduces a broadcast interface with configurable retry mechanisms. In the event of a network failure, the broadcast will automatically retry based on the provided settings.
Any background context you want to provide?
Here is the updated broadcast interface. The BroadcastOptions interface includes optional settings for error callbacks, maxRetries, and retryInterval. Retry options apply only to network errors. (retries will not occur for non-network errors such as broadcasting unserializable payloads.)
  // document.ts

  public broadcast(topic: string, payload: Json, options?: BroadcastOptions) {
      // skipped
  }

export interface BroadcastOptions {
  /**
   * `error` is called when an error occurs.
   */
  error?: ErrorFn;

  /**
   * `maxRetries` is the maximum number of retries.
   */
  maxRetries?: number;  // Default is 0 meaning it won't retry on error.

  /**
   * `retryInterval` is the interval of retries.
   */
  retryInterval?: number;
}

  // usage
  doc.broadcast("YOUR_TOPIC",  "SERIALIZABLE_PAYLOAD", {
      maxRetries: 10,
      retryInterval: 1000,
      error: (error) => {
         console.log(error)
     }
  })

I'm concerned that the maxRetries and retryInterval options are not as intuitive as the shouldQueueEventIfNotReady option provided by Liveblocks.
We could also provide the same option by two possible solutions:

The simplest approach would be to set maxRetries to Infinity, though this may lead to performance issues.

Another approach is to implement a loop similar to runSyncLoop for broadcasts, continuously checking if the network is restored. However, adding a separate loop for broadcasting feels redundant at this point. Therefore, I've opted to keep the solution as simple as possible for now.

What are the relevant tickets?

Fixes #891
Checklist

[x] Added relevant tests or not required
[x] Didn't break anything

Summary by CodeRabbit

New Features

Introduced DefaultBroadcastOptions for enhanced broadcasting settings, including retry logic.
Added flexibility in the broadcasting method to handle options for error handling and retries.

Bug Fixes

Improved error handling during network failures with refined retry capabilities.

Tests

Added new test cases to validate broadcasting behavior under network failure scenarios, ensuring correct retry logic.

There are a few important topics that need further discussion:
1. Individual Retries vs. Queue-based Retry Mechanism:
Currently, the retry mechanism is implemented in a way where each request manages its own retry logic, with a set interval between retries. This was designed to respect the interval for each request.
However, @sejongk  proposed an alternative approach: instead of retrying each request individually, why not queue up failed requests and process them once the network is reconnected? Since these events need to be sent anyway once the network is available, a queue-based retry mechanism could potentially be more efficient. Also, we could keep the interface simple as Liveblocks.
{
    shouldQueueEventIfNotReady: bool
}

In this approach, we might need a separate loop similar to current runSyncLoop to monitor the network status and flush the queue as soon as the connection is restored. Here is the pseudo code.
broadcastRetryQueue = []  // Global queue for failed requests

Broadcast() {
  response = rpcClient.Broadcast()

   // Add to queue if retryable
  if ConnectionError(response):
    broadcastRetryQueuequeue.append(request)
}

runBroadcastLoop() {
  while true {
    if NetworkAvailable():
      ProcessQueue()
    delay = ExponentialBackoff(attempts)
    sleep(delay)
  }
}

It might also be a good idea to apply Exponential Backoff for determining delay, as network connectivity issues can persist for varying durations. Gradually increasing the retry interval can prevent overwhelming the network with frequent retries and give the system time to recover before the next attempt.
2. Broadcast Dependency Issue:
Another topic for discussion is whether or not we should guarantee the order of broadcast events. Currently, there are no explicit measures in place to ensure this. If there is any dependency between the events broadcasted (such as in a chat application), even with a queue, the current structure does not ensure that they will be delivered in the correct order. If maintaining the order of broadcast events is critical, additional steps will be required to address this issue.

We've decided to to proceed with the current implementation (Individual Retries) for now. We can test it out and make improvements as we go.
Additionally, I’ve removed the retryInterval option due to performance concerns. Instead, I’ve implemented a exponential backoff mechanism for retries. This simplifies the interface and improves efficiency by dynamically adjusting the retry timing based on the current attempt.

I hope to see many use cases of broadcasting of Yorkie! 😄


Add functionality from QEDbase and QEDprocesses

Adds most of the tests from QEDbase and has them working here. They should next be moved back to QEDbase using package extensions
CI_UNIT_PKG_URL_QEDbase: https://github.com/QEDjl-project/QEDbase.jl/tree/bc811344e751fd4ef1558bc44c9287dd7736abff

The unit test pipelines fail because this PR depends on the movement of types from QEDprocesses.jl to QEDbase.jl. To circumvent these kinds of meta-dependencies, I suggested a plan for the restructuring process here: https://github.com/QEDjl-project/QED.jl/issues/35
For this PR, I suggest removing every functionality from QEDprocesses.jl, i.e. phase_space and such. If you also use import QEDbase instead of using QEDbase (and correct the respective namespace takes), this one should work with the current dev branch of QEDbase.jl. We can now merge this one to dev (dev_refac should be unnecessary).
Then we can proceed with the schedule given here: https://github.com/QEDjl-project/QED.jl/issues/35

CI_UNIT_PKG_URL_QEDbase: https://github.com/QEDjl-project/QEDbase.jl/tree/process_interfaces


Security Vulnerability, openSSL Unit-Testing

Hello! I know I'm new here, but the following change(s) are quite non-invasive and I thought I'd contribute back :D.
Overview
got had a moderate security issue that was thrown. The following PR aims to fix that.
Additionally, I've provided solutions to other larger open source npm packages relating to the minimist issues (a dependency of the very popular mocha package), but as this is my first time around nodegit, I thought it best to first see how willing the maintainers are to accept my PR (while limited, it seems some either copy and replicate my changes, or haven't bothered to look into the proposals).

Reference to minimist-related PR in express dependency

Discussion
It seems that got, a dependency, is getting used only in the util directory.
Further, specific usage of the module where got is initialized is limited to acquireOpenSSL.js.
I thought to also create some unit testing as I saw that was a point of needed contributions.
Further diving down into the rabbit hole, I found that the binding for node-gyp auto-generates with darwin specified
to 10.11 as the minimum version; because I'm unable to verify (10.15) on the lower versions, I set the test to it.skip.
However, I was unable to successfully compile openSSL v1.1.1l. I updated the reference (a magic constant in acquireOpenSSL.js) to v1.1.1p. Thereafter I was able to successfully build wooohoooooo.
I believe usage of these directives is still yet limited to electron applications; but I'm not 100% certain on this one.

Note that while my personal testing included changing the v1.1.1l version to v1.1.1p, I did set it back.

Note that the following PR is also open:

https://github.com/nodegit/nodegit/pull/1920/commits/89bb003237f842479915e610254c275d7b566458

Accepting that PR will break usage. It seems our friend didn't test his changes.

Please update openSSL to 1.1.1p as the current 1.1.1l has compilation problems due to failing tests @ianhattendorf


Unreferenced files are not compiled

I'm using ts-lambda-api as a framework for my application, which allows me to declare controllers using decorators that are discovered at runtime, rather than statically declared.
It seems like the typescript plugin only compiles files that can be resolved at compile time from the function entry points, which means the controllers are not compiled.
My workaround at the moment is to have dummy imports in my main class to import those controller classes so they can be found.  Is there a better way to control this behaviour?

We are using Node Dependency Injection library and experiencing the same issue due to its dynamic imports. Are there any plans to fix this, please?
Our current workaround relies on statically importing the services again in our entry point which is a little hard to maintain.
// ToDo: https://github.com/serverless/serverless-plugin-typescript/issues/188
// eslint-disable-next-line @typescript-eslint/no-unused-vars
import Configurator from './components/Configurator';
...

Does anybody have at least a better workaround?


Add petition action in all the places

This adds the petition action to the admin petition details partial, the
public petition page and the new sponsor email templates.
https://www.pivotaltracker.com/story/show/95039588

:+1:

LGTM :+1:

Rebased, will merge when green.


Add a transition.

Don't know whether this is possible.

Not possible using [NSWorkspace setDesktopImageURL:forScreen:options:error:] ...


Files modified in the past should not trigger a fingerprint change

Previously, we would bail from the fingerprint computation if the old
and new mtimes had changed in any way. This caused some issues of
rebuilding with filesystems that do not preserve nanosecond
granularity (#2874).

r? @alexcrichton
(rust_highfive has picked a reviewer for you, use r? to override)

Thanks! I think this will take effect, but just to be sure could you add a test for this as well?

@alexcrichton yes, that makes sense. However, I'm having some trouble reproducing in a smaller case.
As far as I can determine, the build.rs file should use mtime-based fingerprints by default. However, the comparison short-circuits when we check the old hash. Investigating further...

I think that the new hash has the mtime internally, which should in theory short-circuit that hash check. You should also be able to just edit tests/paths.rs as path dependencies use mtime checks as well

as path dependencies use mtime checks as well

Yeah, that's the avenue I'm exploring now, but now I'm getting even more confused:
$ cargo build
   Compiling a v0.0.1 (file:///.../backwards_in_time/a)
   Compiling backwards_in_time v0.0.1 (file:///.../backwards_in_time)
$ cargo build
$ touch -t<PHONE_NUMBER>01 a/src/lib.rs
$ cargo build
$ touch a/src/lib.rs
$ cargo build
   Compiling a v0.0.1 (file:///.../backwards_in_time/a)
   Compiling backwards_in_time v0.0.1 (file:///.../backwards_in_time)

So, cargo already ignores when things go backwards in time, except when it doesn't...

Looking back at my original issue, It appears that it's the "output" file (e.g. target/debug/build/tempfile-1b82f6307d61d5f0/output):
$ cargo build
   Compiling a v0.0.1 (file:///.../backwards_in_time/a)
   Compiling backwards_in_time v0.0.1 (file:///.../backwards_in_time)
$ touch -t<PHONE_NUMBER>02 ./target/debug/build/a-e09e69f5aeec0ac1/output
$ cargo build
   Compiling a v0.0.1 (file:///.../backwards_in_time/a)
   Compiling backwards_in_time v0.0.1 (file:///.../backwards_in_time)

This file contains the result of running the build script.

Hm ok, I think if you have path dependencies though you should only need to touch all the files in the crate back in time. (note specifically every file needs to go back in time)

ping @shepmaster, any update on this? (I can certainly help out if needed)

any update on this? (I can certainly help out if needed)

That might be very useful. Basically, I got stuck and then distracted. 😊  I've pushed my latest branch with the tests that I think should fail before and pass after the change. As you can see, that's not the case.
Even just another set of eyes looking at the path that the code is taking and commenting on it would probably prove fruitful.

Awesome, thanks for the update! Of the two tests that are failing:

rebuild_if_build_artifacts_move_forward_in_time - I think this is just due to the updated output on master, should be an easy fix.
no_rebuild_if_build_artifacts_move_backwards_in_time - this I think is actually indicative of a larger problem!

So today the "fingerprint" of a package not only counts the files for that package itself but also the fingerprint of all transitive dependencies. That way if anything changes the updates are pushed upwards through the DAG and we recompile everything. I think the problem here is that the fingerprint of a crate is changing in a way that it decides it shouldn't rebuilt, but the value itself is getting modified. This I believe is because the mtime is considered part of the fingerprint.
So today the mtime considered is actually the mtime of the fingerprint file itself, which I think is fair to say shouldn't be tampered with if you want to not recompile things. Put another way, this patch against your branch should fix the tests in question.
This does raise an interesting question in my mind though! Does this still suffice for the use case you were seeing on Docker? This means that if the mtime of the fingerprint files are changing we're still causing rebuilds, which may not be desirable. Specifically, if a project has two "path crates" (those defined through path dependencies), then you'll have recompiles as the actual fingerprint will change (due to mtimes changing).
An alternative solution, to perhaps fix this entirely, is to just store the mtime in the file rather than relying on the file's mtime itself. That way we can guarantee we never lose precision!
wdyt?

ping @shepmaster curious about your thoughts on my last comment

I've pushed the test fixes to https://github.com/rust-lang/cargo/pull/3246 and I r+'d that, I figure we can handle the "real" problem if comes up, which it's not clear if it does yet!


Update to version 5.0 from version 1.6

Hi,
we have Version 1.6 implememted nearly 3 years ago, its working fine, now we wanted to upgrade to version 5.6, we are seeing issues when trying to resolve references ..we are always seeing no fragments found error
This is how we resolve in version 1.6
       $path = /path/to/schema.json
       $definitionsPath = /path/to/definitions
        $retriever = new UriRetriever();
        $schema = $retriever->retrieve('file://' . $path);
        $refResolver = new RefResolver($retriever);
        RefResolver::$maxDepth = 50;
        $refResolver->resolve($schema, 'file://' . $definitionsPath);

we couldn't find the alternate similar to RefResolver , using SchemaStorage is not resolving the references.
        $resolver = new UriResolver();
        $retriever = new UriRetriever();
        $urlSchema = $resolver->resolve('file://' . $path);
        $refResolver = new JsonSchemaStorage($retriever, $resolver);
        return $schema = $refResolver->resolveRef($urlSchema);

Any help would be much appreciated
Thanks,
Harika

References are resolved as they are needed, rather than a preprocessing step as your example shows. We don't provide a preprocessor that does this.
Can you expand a bit on what you are trying to achieve? You should never need to manually expand references.

Hi,
Many thanks for your reply.
We have a number of schemas, sharing same objects defined in definitions folder.
In the example below, offer object defined in common.json, is shared in foo.json and some other schemas too.
It would be great if you help us to find a solution to our situation, we are desperate to upgrade.
On other note, Is there release supporting draft-07 schema ?
$path => schemas/external/foo.json
$definitions => schemas/definitions/common.json
contents of common.json
{
  "title": "Common Object",
  "description": "My Common Object",
  "definitions": {
    "offer": {
         //elements of offer
           }
      }
}

contents of foo.json
{
  "$id": "http://json-schema.org/draft-04/schema#",
  "type": "object",
  "properties": {
    "offer" : {
      "$ref": "common.json#/definitions/offer"
    }
  },
  "required": [
    "offer"
  ]
}

@harikakatkam Could you please clarify what the problem is? Cross-file references should work out of the box; you don't need to do anything special.
No, we do not yet have a release which supports draft-07.

Thanks @erayd for your help, could you please provide me with a snippet that validates schemas with this structure.
Cheers,
Harika

...could you please provide me with a snippet that validates schemas with this structure.

@hkatkam-eagleeye Your example above is fine. The only thing you need to change is the ref in foo.json; it needs to point to the file in the correct directory:
"$ref": "../definitions/common.json#/definitions/offer"

@hkatkam-eagleeye Here's an example PHP script:
<?php

require "vendor/autoload.php";

use JsonSchema\Constraints\Constraint;
use JsonSchema\Validator;

$schema = (object)['$ref' => 'file://' . realpath('./external/foo.json')];
$data = json_decode(file_get_contents('test.json'));

$validator = new Validator();
$validator->validate($data, $schema, Constraint::CHECK_MODE_EXCEPTIONS);

@harikakatkam / @hkatkam-eagleeye in an attempt to cleanup this repo we are trying to filter the issues and see which ones might be closed. Is it safe to assume this is a rather old issue, which sadly was left unanswered, and can be closed? Feel free to close it yourself with some comments if helpful.


Allow ENV_DIR to be empty if it is not given

Same as https://github.com/mars/create-react-app-buildpack/pull/94 🙏

Closing because the bin/compile arg containing ENV_DIR should allows be provided.


feat(bookmarks): open the browser where the bookmark came from

fix: frecency => frequency
build: major package bump
feat(bookmarks): open the browser where the bookmark came from

Description
Open the browser where the bookmark was sourced from.
In my case, and I imagine most users, different browsers have different login state. For instance, one work, one personal.
If you are trying to open a personal google doc in Chrome when the account is logged in on Safari, the bookmarks plugin is useless.
This fixes that issue.
Screencast
NA
Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

I'm confused what is going on with the typescript errors—any ideas?

Thanks for the comments! Reverted the frecency change, dropped ts version.

The CI errors were partially a Raycast API issue as well. Updating to latest @raycast/api fixes the issues. You can take a look at #8340 for an example

@erics118 fixed!


fix docs for k8snodepool

something seems strange here. I will check again and create a new PR ...

------>   https://github.com/ionos-cloud/module-ansible/pull/59


Expiration Date Calculations Required for MVP

What are the most common scenarios for organizations calculating expiration dates and which of those scenarios should be included in an MVP?
Examples:

Today + 365 days
Today's date next year (e.g. 03/06/2023 to 03/06/2024)*
Today + 365 days rounded to the end of the month (e.g. 03/06/2023 to 03/31/2023)*
Calendar Year
Fiscal Year (e.g. July 1 - June 30)

*Considerations needed for Feb. 29/leap years

We have two schemes, one that uses logic from 2, and another that uses logic May 1- April 30 (our fiscal year is April 1 - March 31)

I have something similar. With annual start date 1st May, paying April to
Feb is this year but March is counted as next year.
On Wed, 29 Mar 2023, 20:19 Kathy-Waterworth, @.***>
wrote:

In one use case I have (and not listed above), the membership is Dec 31 of
the current year. However, if they pay after October 1, the expiration date
becomes Dec 31 of the following year.
This is part of the formula used in a flow for this calculation:
IF(
MONTH ({!$Flow.CurrentDate} ) < 10,
DATE(YEAR({!$Flow.CurrentDate}), 12,31),
DATE((YEAR({!$Flow.CurrentDate})+1),12,31))
—
Reply to this email directly, view it on GitHub
https://github.com/SFDO-Community-Sprints/MembershipSchemaAndBenefits/issues/83#issuecomment-1489170302,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUMH7IG574BF74GC5SDJLX3W6SDNBANCNFSM6AAAAAAVSZIC5Y
.
You are receiving this because you commented.Message ID:
<SFDO-Community-Sprints/MembershipSchemaAndBenefits/issues/83/1489170302@
github.com>

I have a client with a similar business rule. This will help.
On Wed, Mar 29, 2023 at 16:24 DebbieN-SF @.***> wrote:

I have something similar. With annual start date 1st May, paying April to
Feb is this year but March is counted as next year.
On Wed, 29 Mar 2023, 20:19 Kathy-Waterworth, @.***>
wrote:

In one use case I have (and not listed above), the membership is Dec 31
of
the current year. However, if they pay after October 1, the expiration
date
becomes Dec 31 of the following year.
This is part of the formula used in a flow for this calculation:
IF(
MONTH ({!$Flow.CurrentDate} ) < 10,
DATE(YEAR({!$Flow.CurrentDate}), 12,31),
DATE((YEAR({!$Flow.CurrentDate})+1),12,31))
—
Reply to this email directly, view it on GitHub
<
https://github.com/SFDO-Community-Sprints/MembershipSchemaAndBenefits/issues/83#issuecomment-1489170302
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AUMH7IG574BF74GC5SDJLX3W6SDNBANCNFSM6AAAAAAVSZIC5Y
.
You are receiving this because you commented.Message ID:
<SFDO-Community-Sprints/MembershipSchemaAndBenefits/issues/83/1489170302@
github.com>

—
Reply to this email directly, view it on GitHub
https://github.com/SFDO-Community-Sprints/MembershipSchemaAndBenefits/issues/83#issuecomment-1489346030,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXDC7UD26WAZBS4FBG55MDLW6SR7DANCNFSM6AAAAAAVSZIC5Y
.
You are receiving this because you authored the thread.Message ID:
<SFDO-Community-Sprints/MembershipSchemaAndBenefits/issues/83/1489346030@
github.com>

--
T. Ward


Fix issue with titlebar sample setting caption button background to the wrong color

Description

Closes #1355
Motivation and Context

This fixes the issues mentioned in #1355 and also the fact that we showed two titlebars in some cases.
How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[x] Bug fix (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 change)

Thanks for the PR. Could you verify if this issue still exists with newer builds of WInUI gallery  (built from repo). With merger with appwindow titlebar, I think this won't be an issue. But I could be wrong so it is worth checking it out.

@pratikone, I'm afraid this PR is still relevant, the issues were still present when I tested.

/azp run

Thank you @pratikone for the CI rerun and your feedback on this PR!


Should the default build be UMD-wrapped?

Hi there
Thanks for providing a UMD-wrapped build. I'm using this version with RequireJS and it works well.
Looking at the other Tether-based projects Drop and Tooltip I noticed they do not offer such a build, so my first thought was to add to those projects' gulpfile's something similar to what is done in Shepherd's.
Thinking about it though, I'm not convinced this is the best approach. A few issues:

Shepherd's default build cannot be used in combination with that of Drop or Tooltip without Tether and/or Drop being loaded multiple times, as these libraries are bundled in each others' builds.

The point of the UMD pattern is to produce a module which is compatible with all module systems, including "script tags". It shouldn't be necessary to create a UMD build separate from the default build.

The naming of the UMD-wrapped build (shepherd-amd.js) is a bit misleading, since it's not solely an AMD module.

Here's what I propose.

Do not concatenate Tether into the default build. Require it to be loaded separately prior to loading Shepherd, either with the help of a proper module system or with an additional script tag.
UMD-wrap the default build.
Remove the shepherd-amd.js build from the project.
Follow a similar pattern in the other projects (Drop, Tooltip etc.)

If people really want a build with all dependencies bundled, I think this should be a secondary build. Ideally it would contain individually UMD-wrapped components, with the AMD bits producing named modules. Unfortunately I don't know an easy way to achieve this, but see selectize.js' standalone build for an example.
Any thoughts?

By the way, I'm happy to work on a PR to implement this if the owners approve.

Thanks for the analysis @jezstephens.  I think you're correct on all points.  The only change I would make is to continue offering a bundled build of Shepherd, Drop, etc. for users who are installing the file manually and don't want to track down dependencies (less technical users).  That said, we should also offer a build which includes just the appropriate files for more advanced users.  We would very much appreciate you creating the appropriate PRs.

@jezstephens From v1.0.0, the default (and currently only) distribution of shepherd is UMD wrapped. We are working on getting bundled distributions back into the mix since removing them completely is less than ideal as well. :smile_cat:


Don't force redefinition of fixed type members

Motivation
With its current behaviour, Sorbet forces users to redefine every fixed type members used in one of the ancestors.
As shown in the example below, introducing a fixed type member "pollute" the class hierarchy and requires a lot of boilerplate code to be added in all the descendants.
Furthermore, since Sorbet implicitly copies the type member when it's not found locally, error messages point to the wrong place and one has to go up the hierarchy class by class to find the real introduction:
# typed: true

class Base
  extend T::Generic

  MYPARAM = type_member(fixed: String)
end

class C1 < Base # error: Type MYPARAM declared by parent Base must be re-declared in C1
end

class C2 < C1 # error: Type MYPARAM declared by parent C1 must be re-declared in C2
end

class C3 < C2 # error: Type MYPARAM declared by parent C2 must be re-declared in C3
end

class C4 < C3 # error: Type MYPARAM declared by parent C4 must be re-declared in C3
end

This pull-request makes it optional to redefine a type member which is already fixed by an ancestor, then silencing the errors.
Now, the type member is implicitly copied with the fixed bound from the parent and marked as invariant:
# typed: true

class Base
  extend T::Generic

  MYPARAM = type_member(fixed: String)
end

class C1 < Base
  MYPARAM = type_member(fixed: String) # Implicitly copied from Base
end

class C2 < C1
  MYPARAM = type_member(fixed: String) # Implicitly copied from C1
end

# ...

This PR also cleans all the unnecessary type members from the core/stdlib RBIs.
Note that this doesn't change anything to the behaviour of non-fixed type members.
Test plan

See included automated tests.

The reason we have this behavior is the following: when you inherit generic classses you might have different(both larger and smaller, but it's the larger case that matters here) set of type members. Given that use site will need to know their order(e.g. to instantiate the generic), we need definition side to be explicit about order in which type members are.
Implicit copying makes it magic and thus will lead to surprises for users and implementation bugs.
Disclaimer: I'm no longer on the team and the current team opinion takes precedence over mine.

Upd: if this is specific to fixed one, this is actually fine

This is indeed specific to fixed type members and doesn't change how non-fixed ones are handled.
Non-fixed type members still need to be redeclared in each subclass as to specify their order.

Thanks for the suggestion! I agree that it's not great to have to rewrite the type_member declarations for fixed type members, but I don't see a way around it.
The ResolveTypeParamsWalk pass in resolver.cc walks the trees to resolve the bounds of each type member declared on a generic class. If a type member was added through a mechanism that doesn't trace directly back to the tree, then it won't get resolved and will remain a <todo sym>. You can see this in the following example:
# typed: true
class A
  extend T::Sig
  extend T::Generic

  X = type_member(fixed: Integer)

  sig {returns(X)}
  def foo
    10
  end
end

class B < A
  extend T::Sig

  sig {returns(T.attached_class)}
  def self.bar
    new
  end
end

T.reveal_type(B.new.foo) # error: Revealed type: `<todo sym>`
T.reveal_type(B.bar) # error: Revealed type: `<todo sym>`

The X type member never being resolved will block the attached class for B from being resolved, as you can see in the second call to to T.reveal_type.
Separately, I think that there are potentially problems lurking when the SymbolRef stored in the resultType of the type_member doesn't point back to the class that the type_member belongs to, which will be the case when these type members are introduced in the GlobalPass. (The situation I can imagine is an error message that points the programmer back to the wrong file when referencing a usage of the implicitly defined type member on a subclass).
The sorbet team has talked about this PR, and we all generally agree that this is a syntax-motivated change which introduces a lot of edge cases that we don’t want to have to think about, in a part of the codebase that is already requires careful consideration when changes are made. This change makes that code harder to reason about.
We feel like the downsides outweigh the benefit here, especially given Sorbet’s design principles of being explicit rather than implicit.


Handling multiple annotations per image

I'm working with a dataset where each image is associated with a variable number of annotations, and I'm seeking advice on the best way to handle this with webdataset.
For instance, I have images like 1.jpg that are associated with multiple captions, such as 1.txt, 2.txt, ..., 5.txt.
Not all images have the same number of captions; the number of captions per image varies across the dataset.
From my understanding, webdataset primarily handles data where there's a one-to-one correspondence between images and annotations.
As discussed in #91 , one might use a function like this to expand multiple captions for a single image:
def expand_captions(src):
    for image, captions in src:
        for c in captions.strip().split("\n"):
            yield image, c

And then use it as follows:
ds = WebDataset(...).to_tuple("png", "captions").decode(...).then(expand_captions).shuffle(10000)

However, I'm concerned that this approach won't fully shuffle the dataset; annotations for the same image might only appear in close iterations, not fully mixed throughout the dataset.
Moreover, I would like to avoid flattening the dataset in advance to prevent storage capacity issues.
Are there any recommended practices on how to handle datasets with a variable number of annotations per image while still ensuring thorough shuffling of the dataset?

There are many different ways you can handle this.
WebDataset
Here is just one idea: store the image as sample.jpg and the annotations in JSON format as sample.json. Then just map  the sample with:
def transform_sample(sample):
	annotations  = sample["json"]["annotations"]
	sample["annotation"] = annotations[random.randrange(len(annotations))]

If you want to ensure that annotations are encountered regularly, you can also use:
def transform_sample(sample):
	epoch = sample["__epoch__"]
	annotations  = sample["json"]["annotations"]
	sample["annotation"] = annotations[epoch % len(annotations)]

WIDS
You can use the same approaches above also with WIDS.
WIDS also gives you the option of training on an exact full permutation of all (image, annotation) pairs. You can use whatever approach you use with a regular indexed dataset and use WIDS. Presumably, you would start with computing a list of all the (image, annotation) pairs, then permute them.
pairs = []
for i in range(len(dataset)):
	for j in range(len(dataset[i]["annotations"])):
		pairs.append((i, j))

This will not usually give you better results, but it is a lot more complicated to implement. But, again, that's the same whether you use WIDS or any other indexed dataset. I would recommend the very first approach suggested above  instead.


Hash for simulation states

Useful for @select directive which currently only uses the nth state as selection identifier.

Collision management ?


Subset Both functionality

This PR is for the issue #16384

Closing this PR. Didnt notice there was another PR for this issue because it wasnt linked


Julia environment management

Say one has a package CoolPackage which contains a function to be wrapped up and package compiled via Jot. Is the intention to:

Add Jot to the CoolPackage environment and run Jot with CoolPackage activated?
Add Jot to the default Julia environment, activate CoolPackage, and because of environment stacking Jot will still be usable?
Create a new environment that contains both Jot and CoolPackage as dependencies and run Jot from there?

Thanks!
(PS - I really appreciate Jot, I was not super looking forward to simultaneously figuring out Docker, Windows Subsystem for Linux, ECR, Lambda container interfaces, etc. for the first time; Jot really seems to simplify greatly.)

Hello - 3 is the approach that's currently being used - a new environment
is created specifically for the docker image, which includes both Jot and
CoolPackage. This process is (architecturally speaking) a bit clumsy at
the moment and is next on my list of things to refactor, if you have any
strong views on 1 vs 2 vs 3 I'd be happy to hear them.
On Fri, Mar 31, 2023 at 9:23 AM Evan Fields @.***>
wrote:

Say one has a package CoolPackage which contains a function to be wrapped
up and package compiled via Jot. Is the intention to:

Add Jot to the CoolPackage environment and run Jot with CoolPackage
activated?
Add Jot to the default Julia environment, activate CoolPackage, and
because of environment stacking Jot will still be usable?
Create a new environment that contains both Jot and CoolPackage as
dependencies and run Jot from there?

Thanks!
(PS - I really appreciate Jot, I was not super looking forward to
simultaneously figuring out Docker, Windows Subsystem for Linux, ECR,
Lambda container interfaces, etc. for the first time; Jot really seems to
simplify greatly.)
—
Reply to this email directly, view it on GitHub
https://github.com/harris-chris/Jot.jl/issues/43, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALDMVSGH7OG3Z6MPDMS3F4TW6YPWHANCNFSM6AAAAAAWN7FNPI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I guess option 3 isn't so bad in most cases. To confirm, that'd just be like this?
;cd path/to/jot/env
]activate .
]dev path/to/CoolPackage
]add https://github.com/harris-chris/Jot.jl#main
...do stuff with Jot...

If that's all there is to it, pretty smooth, but would be great if the docs clarified this intended workflow. I suppose a problem could arise if Jot's dependencies conflicted with CoolPackage's?


investigating moving out common proto files

(duplicate of https://github.com/blockscout/blockscout-rs/pull/893)


Introduce tests for log_if and log_if_env

Requires: #2

log_if tests completed in 5231f4f6c35581fc2c006b8c9373bdb1876500a0

log_when_env tests completed in 4952de1c50fa6fb728d1513b41c309ffd292a81c


Configuring Timeout [v1.x] [question] [documentation]

Problem
I can't find a way to configure the timeout setting on Slate Tools. I often have to work on a slow broadband connection, where file uploads via Slate often fail with the default timeout setting.
Is there an entry I can add to the .env file to configure this? Similar to config.yml in pre-1.0 where you could add say timeout: 2m.
Replication steps
Upload any file while running slate watch on a slow broadband connection ≈4MEG down (may not be easy to reproduce, I am located in Spain which may play a factor in the slow server response I get).
The timeout response in console is as follow:
[development]: 1 / 1 [====================================================================] 100 %
18:42:53 [development]Asset Perform Update to assets/layout.theme.styleLiquid.scss.liquid at host glasshouse-shop.myshopify.com
	Status: 0
	Errors: Put https://store-name.myshopify.com/admin/themes/33064714283/assets.json: net/http: request canceled (Client.Timeout exceeded while awaiting headers)

My Error 18:42:53 [development]Asset Perform Update to assets/layout.theme.styleLiquid.scss.liquid at host glasshouse-shop.myshopify.com

✔  Files uploaded successfully!

More Information
Version of Slate: 1.0.0-beta.10
Version of Node: 8.9.4
OS: OS X 10.11.6 (15G22010)
Note that the console output then prints  Files uploaded successfully!, even though it failed (a separate issue but thought worth noting).

Hey rossb -- Slate uses node-themekit which wraps Themekit to make requests to Shopify's Asset API. I don't believe the timeout value is configurable, but you could open an issue to expose one, and then I could do the same with Slate so it could be set via the slate.config.js file?

Thanks t-kelly, I will open an issue on node-themekit to request this.

I, too, get timeout errors almost every time I deploy (and like @rossb, ending with a "Files overwritten successfully!" success message). Not sure if this is related to the fact that I live and work on a 2 Mbps Internet connection, although HTTP timeouts are not something I generally experience day to day. Really only when I'm deploying my Slate theme to Shopify, and then it's virtually every time I deploy, at least a good handful of the files display this message. Perhaps the default setting could be made a little more generous?

What seems to be going on here (correct me if I'm wrong) is that on my relatively slow Internet connection where I live, it's timing out on the transfer of individual files due to their size – not because there's an HTTP delay because the server isn't responding. Basically, they're getting uploaded as fast as they can, but if some of these larger files don't manage to make it up there before this time limit (which happens a lot on my connection), it gives up.
Seem to me that the timeout should be triggered only when the remote server stops responding for a period of time.
At it works now, I manage to do a 100% successful deploy maybe 1 out of 10 times. Otherwise there's usually between 4 and a couple dozen of these timeouts.


API: Expose more mirror related option.

Feature Description
Please expose more of the mirror related configuration options via the API. Currently the only mirror related option that seems to be able to be updated via the API is mirror-interval. The following options should also be updatable via API in my opinion:

clone url (for pull mirors)
remote repository url (for push miror)
authorization options.
In addition I especially want an option to convert a mirrored repository into a regular repository via the API.

Screenshots
No response

I second this. The same endpoints that are available for push mirrors (#19796) would be great to have for pull mirrors. At the moment, there seems to be no way to get the remote mirror url of a repository via the API. 😕


[Docs] Add RunLLM chat widget

This PR adds the RunLLM chat widget to the vLLM documentation site. Please see the attached screenshot for how it looks like.

I gave this a try and it's neat!
@simon-mo what do you think of this one?

@WoosukKwon glad it's helpful!


Fix destination name of asm-all-5.0.3.jar

This has caused problems when creating servers if the user didn't have the file cached already.

I'll go ping Nero about this, idk why this wouldnt suddenly be an issue o.o

From what it looks like.

Regardless of the original issue this had been fixed in the new version, I updated to another new version of forge and included new library files for forge to pull from.


Pull from alternate Google Sheet

The original Google Sheet is returning 429s for 50% of the API calls. Changing to a less busy sheet.

FYI @reustle Pushing this change now so the data can still get updated on the site.


Update header parser in Secure Cell master key API

Passphrase API added in #577 has added quite a few new utilities and more robust and readable approach to parsing Secure Cell headers. Fuzzing with AFL in #579 and #583 has uncovered a bunch of sleeper issues in parsing code. This PR incorporates those improvements and updates master key API implementation to resolve all those issues.
First bunch of commits unifies master key implementation with passphrase one, now they are more or less similar, with differences only in KDF processing and header handling. Maybe later we will be able to reduce code duplication even further.
Some next commits resolve miscellaneous issues found in #583 for passphrase API which were also actual for master key API. This should unbreak fuzzing tests performed by #579.
And there are some minor commits with “collateral damage”: extracted common code from passphrase API implementation and some fixups in tests to expect different error codes.
Checklist

[X] Change is covered by automated tests
[ ] Benchmark results are attached (manually compare with master)
[X] The coding guidelines are followed
[X] Public API has proper documentation (no changes)
[X] Changelog is updated (will update in bulk before release)

Since I did not teach our CI to compare benchmark results yet, I'm filling it for this job.
Here are reports for master and this PR, they check only processing of 4 KB of data.

Encryption
Decryption

Before
4.38 µs ± 0.73 µs
3.10 µs ± 0.26 µs

After
4.20 µs ± 0.18 µs
3.01 µs ± 0.28 µs

So it’s even a slight improvement but within the variance so I doubt it is statistically significant.
Performance optimization is not a goal of this PR so I won‘t be doing measurements manually. I’m fine with not having any obvious degradation.


'react/addons' is deprecated

Hi,
The version of react  is 0.14. When I build my project, it shows as follow:
"require('react/addons') is deprecated. Access using require('react-addons-{addon}') instead."
Can you fix it?

see #116 (you need to target 0.14.0 not just 0.14)


Changed ordering of module system usage: first Angular, then AMD

In our application, the previous ordering tried to require('crypto'), while Angular provided it already, so it seemed logical to try the Angular way first.

thanks!

Thanks for the quick response!


filter-out placeholder tickets in triage status

the triage daily status generated a list containing tickets that are only placeholders for logs (generated by the testing for https://github.com/openshift-assisted/assisted-installer-deployment/pull/338). It included tickets for very old clusters that just weren't handled before, because we only filter by ticket creation time and not cluster creation time.
This changes the filter to exclude those kind of tickets (as they can exist for a short period of time also for new failures). In addition, it changes the filtering to be configured from code instead of a pre-defined filter (that currently cannot be managed because the owner left the company).

/hold
testing

/cc @adriengentil @rccrdpccl @nmagnezi

/unhold
works


Add Flow router

Flow router replaces Iron router.

Please wait with merge, I just discovered some bugs.

Nevermind. Fix coming in later PR.


Feature/split launch

What I did

Convert blog into a theme

Require #103

niiiccee work 💪
the only thing I did was to rename the package and the export name... works like a charm 👍
at some point we will need to think about a "best" practice on how to name/structure all those theme files 🤔


after last kml file is removed add files does not open a file dialog

seems when the list is empty we can't add a new file to the list

seems something in my setup blocks the file dialog to start.


Feature List

Database
Description: Scrape/store data
Time Estimation: 20 hours

[ ] Food (Cost, Time, Location) [Due: Milestone 1]
[ ] Activities  (Cost, Time, Location) [Due: Milestone 1]
[ ] Events
[ ] Sightseeing
[ ] Outdoors
[ ] History
[ ] Performances
[ ] Tours
[ ] Visited [Due: Milestone 2]
[ ] Pins (Location, Reviews, User) [Due: Milestone 1]
[ ] User accounts [Due: Milestone 1]

Generate Day Plan
Description: Generate a day plan from pins in database with restrictions of budget, transportation, and type
Requires: Back end logic
Time estimation: 60 hours

[ ] Budget restriction [Due: Milestone 2]
[ ] Transportation restriction [Due: Milestone 2]
[ ] Distance optimization
[ ] Type restriction [Due: Milestone 2]
[ ] Machine learning to predict favourable activities
[ ] Swipe to generate new activity/plan [Due: Milestone 2]

Pins
Description: Logic behind Pins
Requires: Working with Google maps API
Time Estimation: 10 hours

[x] Integrate with maps [Due: Milestone 1]
[x] Create pin [Due: Milestone 1]
[x] Review pin [Due: Milestone 1]

UI
Description: User interface for using and operating features
Requires: Front end app development, authentication, working with google maps API
Time Estimation: 20 hours

[ ] Login [Due: Milestone 1]
[ ] Search [Due: Milestone 3]
[x] Map [Due: Milestone 1]
[ ] Options to plan day [Due: Milestone 2]
[ ] Continue through activities [Due: Milestone 3]
[ ] Change day plan [Due: Milestone 3]
[ ] Save pins [Due: Milestone 3]

Feature List.docx

What out of all these features are necessary for a minimal end-to-end prototype?
Login is not one of those, user accounts probably not either...


refactor: Stage execute and unwind take an immutable provider reference instead

No need for mutable reference anymore

blocked by https://github.com/paradigmxyz/reth/pull/3384


PDCT-682/only_allow_valid_url

Add yup validator for url
Add error message for url validation in Document form
Add the first component render test

The test is not working yet.
But manually tested and working:


feat: add rtl8814au wifi driver

This PR adds two spec files to build akmods packages for the rtl8814au driver. I've been testing it with a 0846:9054 NetGear, Inc. Nighthawk A7000 802.11ac Wireless Adapter AC1900 [Realtek 8814AU] and the driver appears to be working and the kernel modules aliases seem to update correctly when the akmods package builds and installs inside a distrobox container. I'm not totally sure how to get it into rpm-ostree for testing against the host though.
I've got it building in my copr here.
I am new to using akmods for building, so let me know if anything looks wrong. I tried to follow some examples from the existing ublue-os akmods copr builds.

Thanks so much for this one, maybe we can start to collect more of these!


Generate deployable resource yamls as release artifacts

Generate deployable resource yamls for kfserving deployment. This will simplify the kfserving deployments for people wanting to try this out.
Something like here: https://knative.dev/docs/install/knative-custom-install/
https://github.com/knative/serving/releases/download/v0.6.0/serving.yaml

Are you planning on taking this on Kumar?

@ellis-bigelow
I can take this up and probably would need some help from you as I am new to this world.
I was looking into this and the current triggers are setup very differently then using Makefile.
Can we use our Makefile and ko to build push image and then generate the yamls on Google Cloud Build?

I actually don't know the best way to do this.
We could definitely build YAMLs on GCB, but I'm not sure where we'd publish them. We could consider making them public on GCS, which could be kind of cool.
You could then kubectl apply -f URI.
I know the knative and istio use helm for their installations, and they put them in a /install folder. It might be worth reaching out to those teams and finding someone to chat with.
Alternatively, the Kubeflow community does this as well for other modules (though I don't trust it's as mature as Istio, for example), and they might have some ideas.

I can take a stab at doing it through GCB using Makefile through build config. Can I get permissions to edit triggers? Also storing it on publicly readable GCS sounds good for now. I am not sure where to provision the GCS. Can you do that please and let me know?

I think we should probably do a bit of research on existing approaches
before gcb. Is that something you're interested in or are you looking for
more concrete things 😉?
On Fri, May 24, 2019, 1:16 PM Kumar Abhishek<EMAIL_ADDRESS>wrote:

I can take a stab at doing it through GCB using Makefile through build
config. Can I get permissions to edit triggers? Also storing it on publicly
readable GCS sounds good for now. I am not sure where to provision the GCS.
Can you do that please and let me know?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubeflow/kfserving/issues/119?email_source=notifications&email_token=AATXLCED6RNOMSCJAWMEHLLPXBELJA5CNFSM4HPRYQN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWGO7OI#issuecomment-495775673,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AATXLCCYZBZIXJGJ7XFOBZ3PXBELJANCNFSM4HPRYQNQ
.

I was planning to make it work with gcb as that would be a quick path for now to enable release CRDs and image for people to try without enlisting.

Alright, well in that case feel free to make a GCP project and use Cloud Build and GCS to test the solution. Once you've got it all working, I can wire it up with the kfserving project. For now, I don't have Google's permission to open the permissions on this project given that there's a direct billing impact. Sound good?

That sounds good.

Implemented
/close

resolved via https://github.com/kubeflow/kfserving/pull/210


Bug on 118

Help?

Not enough details.

It doesn't have a pic of it on the tech tree and on build

Also Kugelblitz doesn't have a base turret and it couldn't be deconstructed

Also Kugelblitz doesn't have a base turret and it couldn't be deconstructed

Shoulder be fixed, dunno what the other issue is.

This is what the Mindron Collider looks like when built, and it cannot be deconstructed

The OhNo's

@MEEPofFaith

its fine for me

Well not for me

Well then I don't know how to help, though maybe it might be because you aren't playing with the latest version of progressed materials?

I played with your latest version man
In 118 (now version 119) the sprite for Mindron collider is missing, cannot be deconstructed

well then I don't know what the issue is since it works for me :/

Okay I found the problem turns out the master file and v6 file were in the same mod folder so it got conflicted and causing the oh no

oh no


Removed application element from library's manifest

This PR fixes #61 by removing the application element in the library's AndroidManifest.xml as it is not needed and can conflict with consumer's manifest attributes when merging manifests during build process.

Looks good, just waiting on the CI build to complete. Thanks!

Approved


Add Update SDK workflow

I merged Add-update-sdk-workflow in my main branch, so I could execute the workflow Update SDK manually (it seems that cron jobs cannot be executed on fork).
Here is the run: https://github.com/moi15moi/py-win32more/actions/runs/11875453218
As you can see, it updated the Windows App SDK to the version 1.6.241106002 (see this commit), but it is strange because it only has modified the json file and not the actual code, so I'm not sure if there is a problem.
Fix #63

In my main branch, I merged Add-update-sdk-workflow branch.
I also set Microsoft.Windows.SDK.Win32Metadata to 59.0.13 to see how the job Update Win32Metadata would perform.
See the run here: https://github.com/moi15moi/py-win32more/actions/runs/11879979376

Thank you.


Adds import-db and import-files commands

The Problem:
See #33 for full details. Our existing import functionality is heavily reliant on site archives in a very specific structure and naming convention. We want import functionality that does not require rigid archive formats, and we want to be able to separately import the database and files as desired.
The Fix:
This PR introduces 2 new commands, ddev import-db and ddev import-files. The commands have some similar functionality. They both accept a path provided by user prompt or by using a --src flag. They both accept tar.gz archives, and if provided, will be extracted so the assets within can be imported.
The import-db command ultimately expects a single .sql file be provided. This means either a file path should be provided directly, or an archive containing a sql dump at the root of the archive should be provided.
The import-files command ultimately expects a directory path be provided. The provided directory's contents will be copied to the default uploaded files directory for the given application. In Drupal's case, this is sites/default/files. In WordPress' case, this is wp-content/uploads. If an archive is provided, the contents of the archive are copied as-is to the default location.
This also implements a new wp-config.php template that will work with a standard installation. Full details of this can be seen at the closed PR for this task #112
This PR does not remove the previous import command and its related functionality. For the purpose of easier reviews, the removal will be completed in a separate PR.
The Test:
Note: You will need to set the database container tag in the .ddev/config.yaml of the site you are testing to the import-update tag.
You should be able to test this with a pre-existing site, provided the site uses standard location for uploaded files. You can also use the following test sites that I have compiled test assets for:
https://github.com/drud/drupal8/releases/tag/v0.2.2
https://github.com/drud/wordpress/releases/tag/v0.1.0
https://github.com/drud/drupal-kickstart/releases/tag/v0.1.0
Usage examples:
examples are for import-files, but also valid for import-db, provided you are providing a sql dump.
Prompt:
ddev import-files
Provide the path to the directory or archive you wish to import. Please note, if the destination directory exists, it will be replaced with the import assets specified here.
Import path:
~/Desktop/wp-files.tar.gz
Successfully imported files for testsite1

Flag:
ddev import-files --src ~/Desktop/wp-files.tar.gz

or
ddev import-files --src=~/Desktop/wp-files.tar.gz

Automation Overview:
I have added test coverage for ImportDB and ImportFiles at the local plugin level. I have also added test coverage for the new appimport and files packages.
Related Issue Link(s):
#33 OP
#107 / #112  update wp-config template
drud/mysql-docker-local#11 - mysql import updates
Release/Deployment notes:
Does this affect anything else, or are there ramifications for other code? Does anything have to be done on deployment?
This PR does not remove the previous import command and its related functionality. For the purpose of easier reviews, the removal will be completed in a separate PR.
drud/mysql-docker-local#11 - mysql import updates is required for this change. A new tag will need to be pushed for this container.

Looks like there are some remaining clean-up items. FWIW, I would prefer that the imports work with both tar and tar zips, given that users will likely attempt from both (even though I would bet zips are more popular for files and databases are more likely to be unzipped). If we need to split the remaining file extention/zip support to another ticket, I'm cool with that because there is a lot of work here that should get merged sooner than later!

@rickmanelius I assume you're saying .tar and .tar.gz - or are you also saying file imports using .zip ? .zip was spun off into https://github.com/drud/ddev/issues/147
IMO if you think .tar is important (probably is) we should spin that off into another issue, as this one is way overdue for pull.

With the latest updates, sql.gz import should work as expected. Additionally, tar files will work whether or not they are gzipped. Once we have green board on the tests, this should be ready to come in.

I tested .sql, .sql.gz for database and .tar, .tar.gz, .tgz for files. They all seemed to work fine. Approved. There will be followups, we know. Huge accomplishment, thanks for hanging in there.


DZ2: Tracker actions

@keybase/react-hackers
Still finishing this off, not ready to merge, but I'd like to get a review on the approach.  The general idea is that performing an action sets a new "lastAction" field that shows up as new props for the header and action components, allowing them to see what just happened and re-render.
Something to work out: we're still using the "reason" provided over RPC ("To confirm foo is a writer of..") instead of the text in the style guide ("You accessed a private folder with foo."), should that be solved with patches to keybase/kbfs to make it use style guide text?

makes sense to me :+1:

why do we need this last action concept

Added it for two reasons:

Routing actions allows us to wait to see whether the track/retrack/untrack succeeded or failed before updating the popup, so it becomes possible to show an error.
Gabriel made a components sheet for tracker showing the popup in all of its states, and to be able to show a popup in each state I think I need to pass different props for each state.

Does that make sense?  If neither of those reasons are worth it, or there's another way to achieve them, could switch to state.

yeah it's fine, let's do it
On Wed, Feb 24, 2016 at 9:07 AM, Chris Ball<EMAIL_ADDRESS>wrote:

why do we need this last action concept
Added it for two reasons:

Routing actions allows us to wait to see whether the
track/retrack/untrack succeeded or failed before updating the popup, so it
becomes possible to show an error.
Gabriel made a components sheet for tracker showing the popup in all
of its states, and to be able to show a popup in each state I think I need
to pass different props for each state.

Does that make sense? If neither of those reasons are worth it, or there's
another way to achieve them, could switch to state.
—
Reply to this email directly or view it on GitHub
https://github.com/keybase/client/pull/2114#issuecomment-188269605.


Convert JetBrains from a Spelling rule to a CaseSensitiveTerms rule.

Reviewing https://github.com/redhat-documentation/vale-at-red-hat/pull/351, it seems like we should convert "JetBrains" from a Spelling rule to a CaseSensitiveTerms rule. WDYT?

If we apply this change, the output changes from:
 28:1  warning  Use correct American English    RedHat.Spelling
                spelling. Did you really mean
                'jetbrains'?
 29:1  warning  Use correct American English    RedHat.Spelling
                spelling. Did you really mean
                'Jetbrains'?

to
 28:1  error    Use 'JetBrains' rather than     RedHat.CaseSensitiveTerms
                'jetbrains'.
 29:1  error    Use 'JetBrains' rather than     RedHat.CaseSensitiveTerms
                'Jetbrains'.


[Techdocs] Fix sticky sidebars from overlapping other content in Entity Pages

Fixes https://github.com/backstage/backstage/issues/11774
The techdocs reader page repositions the sidebars (navigation and toc) when you scroll the documentation content. This works well in the standalone docs page.
When docs are shown in an entity page under the docs tab the sidebars start overlapping with the header and tabs in the page as shown in https://github.com/backstage/backstage/issues/11774
The fix is to account for the header and tabs shown in entity page and not let the sidebars scroll beyond them.
After fix in entity page

Please suggest if there a better way to fix this or any suggestions welcome.

@camilaibs Your suggestion is better 👍 I have added the same. The PR is ready for review again.

The issue that we had earlier, seemed to be fixed with this merge.
Yet, the same (if not the same, but almost) is when the window is not full size (and smaller screens, like 14" laptop screens). Also, if there is a video, the right side (eg. Table of Contents) will be again over the video.
I'm attaching both screenshots (for video, and not full size window):


Make sure that response list objects get cleared when destroying the service object

See comments:
https://github.com/tanagraspace/ccsdsmo-malc-sepp-apps/blob/2b358ba13f2f6b8947a1af4ea7ae91234429c2d5/apps/nmfapi/src/mc_parameter_service.c#L87-L105

Addressed with issue #83 and enhancement feature request documented with issue #85.

Addressed with issue #83 and enhancement feature request documented with issue #85.


the Repo must be maintained

Hi All,
When I update my projects to Angular 12, I found a really annoying bug that makes my compiled CSS had some syntax error. so I started to dig for this error and found that a lot of issues mentioned the same problem like angular/angular-cli#20975 and an opened one angular/angular-cli#20760 till I found that the problem in @angular-devkit/build-angular and it's dependant on GoogleChromeLabs/critters and I found an Issue opened GoogleChromeLabs/critters#74 but when I tracking the bug in the library it leads me to this project and found an open issue #154
so I found the problem in the Parser in [https://github.com/reworkcss/css/blob/434aa1733f275a67ea700311451b98a14f8cc21a/lib/parse/index.js#L516](this line), the regular expression not suitable for all scenarios especially the strings which had a semicolon inside the value like
@import url('https://fonts.googleapis.com/css2?family=Rubik:wght@300;400;500;600;700');
so I start to get a clone from this repo to fix this problem and I found this repo want really big attention because it follows a 9 years old code for example the test cases file had some bug in reading files so I fix it and add two new test cases for a start.
If this repo will be in a supply chain library for a big framework like Angular, the code must be maintained

Agree, the regexp needs some love. For example it would reject the last-in-file at-rule with omitted ending semicolon. It is correct syntax in css.
Regarding urls I'd suggest adding also a test for data URLs eg.
background: url("data:image/svg+xml;charset=UTF-8,%3Csvg%20width%3D%2236%22%20height%3D%2212%22%20viewBox%3D%220%200%2036%2012%22%20xmlns%3D%22http%3A%2F%2Fwww.w3.org%2F2000%2Fsvg%22%3E%0A%20%20%3Ccircle%20cx%3D%226%22%20cy%3D%226%22%20r%3D%223%22%20fill%3D%22rgba(0%2C%200%2C%200%2C%20.2)%22%3E%0A%20%20%20%20%3Canimate%20attributeName%3D%22r%22%20values%3D%223%3B5%3B3%22%20calcMode%3D%22linear%22%20dur%3D%221s%22%20repeatCount%3D%22indefinite%22%20%2F%3E%0A%20%20%3C%2Fcircle%3E%0A%20%20%3Ccircle%20cx%3D%2218%22%20cy%3D%226%22%20r%3D%223%22%20fill%3D%22rgba(0%2C%200%2C%200%2C%20.2)%22%3E%0A%20%20%20%20%3Canimate%20attributeName%3D%22r%22%20values%3D%223%3B5%3B3%22%20calcMode%3D%22linear%22%20begin%3D%22.33s%22%20dur%3D%221s%22%20repeatCount%3D%22indefinite%22%20%2F%3E%0A%20%20%3C%2Fcircle%3E%0A%20%20%3Ccircle%20cx%3D%2230%22%20cy%3D%226%22%20r%3D%223%22%20fill%3D%22rgba(0%2C%200%2C%200%2C%20.2)%22%3E%0A%20%20%20%20%3Canimate%20attributeName%3D%22r%22%20values%3D%223%3B5%3B3%22%20calcMode%3D%22linear%22%20begin%3D%22.66s%22%20dur%3D%221s%22%20repeatCount%3D%22indefinite%22%20%2F%3E%0A%20%20%3C%2Fcircle%3E%0A%3C%2Fsvg%3E%0A");

Hi, I'm not sure if this repo is still used for the last version of Angular but I created a fork of it and plan to maintain it at: https://github.com/adobe/css-tools
In a few days, the version will be published into npmjs.

https://www.npmjs.com/package/@adobe/css-tools


Chain.Transaction There is no TXID in this class ?

Chain.Transaction There is no TXID in this class ?

No there is not. The same as what's in java-tron, transaction id is in TransactionInfo.

you can calculate txHash with method below. Input is signedTX.
private String getTxHash(Chain.Transaction tx) {
SHA256.Digest digest = new SHA256.Digest();
digest.update(tx.getRawData().toByteArray());
byte[] txid = digest.digest();
return TronClient.toHex(txid);
}

In the next version, we're planning to return directly the transaction hash if the transaction has been successfully broadcasted.
Please note that a successful broadcast is not equivalent to a successful transaction, you can only use getTransactionInfoById to check this.


Do not send migrate task when BE only have 1 storage medium

What type of PR is this：

[x] bug
[ ] feature
[ ] enhancement
[ ] others

Which issues of this PR fixes ：

Fixes #4000
Problem Summary(Required) ：

when be report tablet info to fe.
If we know that this BE must have no other medium, then only write a log as a reminder, not to send a task.

[FE PR Coverage check]
:disappointed: fail : 0 / 14 (00.00%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/catalog/TabletInvertedIndex.java
0
14
00.00%

[FE PR Coverage check]
:disappointed: fail : 10 / 15 (66.67%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/catalog/TabletInvertedIndex.java
10
15
66.67%

[FE PR Coverage check]
:disappointed: fail : 9 / 17 (52.94%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/catalog/TabletInvertedIndex.java
0
8
00.00%

:large_blue_circle:
com/starrocks/system/Backend.java
9
9
100.00%


VIRTUAL_HOST environment var

Hiya, I would love to merge this PR... but unfortunately, it did not works on my Ubuntu 😞
Did you or did I miss something?

Very rare. I made the changes on Github. I have tried to modify the changes.It is better to put the VIRTUAL_HOST variable in .env.dist

I still cannot access to my Symfony app on symfony.dev :confused:


When parsing DBC, make sure there are no unused VAL_ and SIG_VALTYPE_ entries

This makes DBC parsing a little more strict, rejecting DBCs with some common(?) errors.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

14 of 20 (70.0%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.06%) to 93.489%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/cantools/database/can/formats/dbc.py
14
20
70.0%

Files with Coverage Reduction
New Missed Lines
%

src/cantools/database/can/formats/dbc.py
1
96.7%

Totals

Change from base Build<PHONE_NUMBER>:
-0.06%

Covered Lines:
7266

Relevant Lines:
7772

💛  - Coveralls

@andlaus do you want me to rebase this on top of master to pick up the linter fix that you just merged?

I'm not sure about this. I do not see the benefit of raising an exception on unused values. If CANdb++ can open these files, then they are valid and we should accept them.

@andlaus do you want me to rebase this on top of master to pick up the linter fix that you just merged?

that would probably a good idea...

(Oops, didn't mean to close this PR!)

And this latest force-push should fix the ruff linter error i introduced.  :roll_eyes:
Sorry for all the churn...

Here are some small DBC files that demonstrate the issue.  They both define two packets with one signal each.  In bad.dbc the VAL_ and SIG_VALTYPE_ lines have incorrect frame ids (COB IDs?) so they don't get applied to the signals.  In good.dbc the frame ids have been fixed so the lines do get applied to the signals.
good.dbc.txt
bad.dbc.txt
The diff from bad to good is this:
$ diff -u bad.dbc good.dbc
--- bad.dbc     2024-05-03 15:10:47.601981628 -0600
+++ good.dbc    2024-05-03 15:10:53.985999971 -0600
@@ -42,6 +42,6 @@
  SG_ signal2 : 0|32@1- (1,0) [0|0] "" Vector__XXX

-VAL_ 99 signal1 3 "High" 2 "Standard" 1 "Low" 0 "Unknown" ;
+VAL_ 1 signal1 3 "High" 2 "Standard" 1 "Low" 0 "Unknown" ;

-SIG_VALTYPE_ 345 signal2 : 1;
+SIG_VALTYPE_ 2 signal2 : 1;

Here is CANdb++ trying to load bad.dbc:

Here is cantools accepting bad.dbc and just ignoring the invalid VAL_ and SIG_VALTYPE_ lines, so the signals are interpreted as "default" integers:
$ python3 -m cantools list --all bad.dbc
msg1:
  Frame ID: 0x1 (1)
  Size: 1 bytes
  Is extended frame: False
  Is CAN-FD frame: False
  Signal tree:

    -- {root}
       +-- signal1

  Signal details:
    signal1:
      Internal type: Integer
      Start bit: 0
      Length: 8 bits
      Byte order: little_endian
      Is signed: False
msg2:
  Frame ID: 0x2 (2)
  Size: 4 bytes
  Is extended frame: False
  Is CAN-FD frame: False
  Signal tree:

    -- {root}
       +-- signal2

  Signal details:
    signal2:
      Internal type: Integer
      Start bit: 0
      Length: 32 bits
      Byte order: little_endian
      Is signed: True

Here is CANdb++ successfully loading good.dbc:

And for completeness, here is cantools parsing good.dbc:
$ python3 -m cantools list --all good.dbc
msg1:
  Frame ID: 0x1 (1)
  Size: 1 bytes
  Is extended frame: False
  Is CAN-FD frame: False
  Signal tree:

    -- {root}
       +-- signal1

  Signal details:
    signal1:
      Internal type: Integer
      Start bit: 0
      Length: 8 bits
      Byte order: little_endian
      Is signed: False
      Named values:
        3: High
        2: Standard
        1: Low
        0: Unknown
msg2:
  Frame ID: 0x2 (2)
  Size: 4 bytes
  Is extended frame: False
  Is CAN-FD frame: False
  Signal tree:

    -- {root}
       +-- signal2

  Signal details:
    signal2:
      Internal type: Float
      Start bit: 0
      Length: 32 bits
      Byte order: little_endian
      Is signed: True


Replacing logrus with logf.

Replaces logrus with logf.
Modifies the NewServer API to take a logger from the user.
Modifies brokers,results backends to explicitly take a logf logger.

Since 1.16 is not officially supported anymore, we should ideally only support 1.17+

Update logf to the latest version which supports 1.17+


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/97300

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/99003


Changes for AHK 2.0 a108

AHK2 a104 introduces splitting of objects in objects, arrays and maps.
a105 to a108 introduce further breaking changes.
In order to follow this changes log4ahk has to be adapted.

Obsolete - since a108 is also already obsolete, as a122 is the most current AHK V2 version.
From a108 to a122 there have been more breaking changes.
Issue closed


Sorry for annoying, question about Steam "ban"

So im scared as hell. I read pretty much about SAM now and im still not sure if I should use it. The thing is, im convinced that its safe for now, Ive already tried it on my second steam account and did it as obvious as I can, 2 Months later and nothing happened yet. But what makes me really doubtful is the future, maybe the change something in their policy/rules or whatever, and I could get "banned" afterwards.
I dont want to lose my account, Ive spend so much money and time in it, I just want to use it for broken achievements or something like that. And like I said, Im done searching for it, the only thing thats left to seek for kinda answers is here. Would be thankful for answering me.
Greetings

I can't make any guarantees. The only thing I can say is that SAM has existed since 2008 and I have never heard of any ban connected to usage of SAM.

I think it's pretty safe. I used it a LOT during the 2012-13 timeline and kept it very obvious for a long time before removing the achievements and starting legit. Havent heard of anyone getting banned either. But take my advice with a pinch of salt 😄

There is no guarantees as gibbed says. If you're goal is only for some broken achievements, you should contact the support (Steam or game developers) to fix it. Or check online for a better solution.
I recently had an issue with a 2009 game, an achievement as well, but the community worked with ex-developers of the game on a solution to make it work. If you're not lucky about that, just make up your mind to use it or not.
To be closed?

how about running SAM while in VAC secured server??

how about running SAM while in VAC secured server??

That cannot happen because when you run it and pick a game, you cannot be playing the game at the same time.

how about running SAM while in VAC secured server??

That cannot happen because when you run it and pick a game, you cannot be playing the game at the same time.

i mean pick game like dota,tf,etc but not csgo so i play it while SAM was run

how about running SAM while in VAC secured server??

That cannot happen because when you run it and pick a game, you cannot be playing the game at the same time.

i mean pick game like dota,tf,etc but not csgo so i play it while SAM was run

You cannot launch two games at once.


Add new feature to About

From backlog item:339
Scrumwise Status:To do
Update the About window for the new supported feature

While connected, used the Task manager to  end the Petrel process.  Both the petrel process and the arkcls_ods process are removed cleanly.  I would class this as a PASS.


Avoid error message assertions on OS dependent errors (#716)

A proposed fix to Issue #716 where tests are failing on macOS Catalina, which look like:
--- FAIL: TestExtractSecretsToFile_Err (0.00s)
    elasticsearch_secrets_test.go:114:
                Error Trace:    elasticsearch_secrets_test.go:114
                Error:          Error message not equal:
                                expected: "open /root/foo: permission denied"
                                actual  : "mkdir /root: read-only file system"
                Test:           TestExtractSecretsToFile_Err
--- FAIL: TestWriteToWorkingDir (0.00s)
    elasticsearch_secrets_test.go:164:
                Error Trace:    elasticsearch_secrets_test.go:164
                Error:          Error message not equal:
                                expected: "mkdir /foo: permission denied"
                                actual  : "mkdir /foo: read-only file system"
                Test:           TestWriteToWorkingDir
    elasticsearch_secrets_test.go:164:
                Error Trace:    elasticsearch_secrets_test.go:164
                Error:          Error message not equal:
                                expected: "open /root/bla: permission denied"
                                actual  : "mkdir /root: read-only file system"
                Test:           TestWriteToWorkingDir

As alluded to in @volmedo's suggestion, the change here is to assert on the error type os.PathError instead of the OS-specific error message.
Given TestExtractSecretsToFile_FileExists is a table-driven tests with the possibility of more than one error type as an outcome of a particular permutation of inputs, it was decided to use reflection and compare on the error type rather than a err boolean and hard-code a comparison to os.PathError.
For TestExtractSecretsToFile_Err, using reflection would unnecessarily complicate the code as there is only one possible error outcome.
As for TestCreateESSecretsError, the error returned may differ between OSes, but it does not appear to be a known breaking issue AFAIK.

I'm not sure why pkg/apis/jaegertracing/v1/options.go had caused reduced codecov/project coverage when I didn't change that file, nor modify non-test code.  Anyone know what's causing the alert and how I can fix it?

Thank you for your contribution!


Bug Report: mods cant be put be in the kade engine because its not a zip or rar

Elaborate, what are you trying to do exactly? And what have you done to get to this point?

This is not an issue. This is a discussion


Adding InjectResource to the annotation processor

Added Resource Binding module that supports the following data types String, Drawable & Animation.

See #244