Update README.md to support latest Vite/Rollup config

This breaks HMR/hot refresh. I think conditional config is needed to fix that, I have no idea what's happening.

This breaks HMR/hot refresh. I think conditional config is needed to fix that, I have no idea what's happening.

Hi,
Apologies for not noticing this PR sooner. I haven't been using this plugin for a month or so. Today I used it again and I believe I ran across the same issue you did -- the new vendor chunk. It appears you fixed it by assigning manualChunks to null? I did so with () => "everything.js", but I'll go back and try null as well.
I updated the location of inlineDynamicImports as well, so that should resolve everything in this PR. I'll leave it open for now to remember to test manualChunks: null when I have a chance.


Wip subscribe

This branch reflects the update of the codebase to  Meteor <IP_ADDRESS> / Vulcan 1.12.16. Since subscriptions were removed from Vulcan core in this version, I tried to incorporate the older standalone vulcan-subscribe package to the app. I'm encountering issues with the GraphQL User schema and where to modify the schemas across the app to add fields like SubscribedItems.

This branch reflects the updated codebase to Meteor <IP_ADDRESS> / Vulcan 1.12.16 with latest packages. In this version of Vulcan, subscriptions are no longer part of core. I tried to import the older standalone vulcan-subscribe package from a previous version and adapt it. I am encountering issues with the User schema in GraphQL. With different versions and packages I am not clear on where to modify User to included fields such as SubscribedItems which are needed by the vulcan-subscribe package. So my attempt to import the old package is stuck.


Support undiscriminated unions in documentation

Currently we don't handle rendering undiscrminated unions in the fern documentation. See https://github.com/fern-api/fern/blob/73e52c134bc760f973f6a80f8f56faf4824ce02d/packages/ui/app/src/api-page/types/type-definition/InternalTypeDefinition.tsx#L49-L50.
The designs are very similar to discriminated unions:

See the response of this endpoint https://permit.docs.buildwithfern.com/api-reference/resource-roles/get-resource-role-descendants for a reproducible error.
The fern definition for the original API lives here: https://github.com/fern-permit/docs

Tracked in this linear issue now


No way to set animation loop to false or have onAnimationEnd event?

It would be great to have possibility to pass 'loop' parameter to animation.play() method (like anim.play(false) so it plays only once) and even better to be able to get noticed when animation has ended.

Added a property for loop and on complete event. You can use it like this:
animation.loop = true // default will be false
animation.on("complete", () => { console.log("animation complete") })
animation.play()
It's available on develop branch, let me know if it is good enough :-)

I've tried it and I have a few problems now:
animations[x].channels is gone, I have to use private prop (animations[x]._channels)
My animation has 65 frames but it fires "oncomplete" on frame no. 34 or 35:
currentPlayerAnimation.on("complete", (e) => {
	console.log(currentPlayerAnimation._channels[0].frame); 	// shows 34 or 35, but channel has 65 frames...
	player.visible = false;
});

My logic before was something like this:
(on every frame...)
if (currentKeeperAnimation.channels[0].frame === currentKeeperAnimation.channels[0].length - 2) {
    currentKeeperAnimation.stop();
    keeper.visible = false;
}

animation.speed was set to 1.3 on one of my animations, maybe that's why it doesn't calculate correctly the end of animation?

Please clone develop branch and do "npm install" and then "npm run serve -- --env.example=quick-guide"
Change the lines 32-37 to this  and see if it prints "complete"at the correct time in console:
model.animations[0].play()
  model.animations[0].loop = true
  model.animations[0].speed = 1.3
  model.animations[0].on("complete", () => {
    console.log("complete")
  })

I have multiple animations on one mesh. Its in idle animation (and looping) until it needs to switch some other animation.
I had to stop idle animation before playing another, and that solved the problem. Thanks!


Added TLS support.

Design
The TLS support in Document Layer leverages the existing FDBLibTLS from the FoundationDB codebase for the sake of consistency and code reuse. Basically it's a thin wrapper around the network interfaces that, based on whether the listen_address ends with :tls, decides whether to enable TLS or not. The thin layer is totally transparent to the main Document Layer who simply treats it as a normal network interface. And thus the actual code change here in Document Layer is pretty small.
How to use it
I updated the docs to reflect this, but what user needs to do is pretty simple:

Append the :tls to the listen_address
Then supply all necessary parameters whose name starts with tls_.

And that's it!
Note that once the server has TLS enabled, no client would be allowed to connect via non-TLS connections. And similarly if the server has TLS disabled, no client would be able to connect via TLS connections.
Thus if you first run the server without TLS, then later modified the document.conf to enable TLS(or the other way around), which would cause the fdbdoc process restarted by fdbdocmonitor, all outstanding connections will no longer work.
Where are the tests?
Since the FDBLibTLS has been tested pretty throughoutly and been used for a while, I only tested the Document Layer manually, using bunch of self-signed certs and keys. That being said, it's probably a good idea to add some sort of automated tests in the future.

This is for issue #2

@alexmiller-apple you may want to take a look too.

Investigating the macOS build failure...

Test this please.

Other things that are of interest, but I don't know how document layer build is set up:
Are FoundationDB knobs settable on doc layer binary?  If not, then I think you have no way to control TLS cert refresh.
I went looking back over issues that were caused when TLS was enabled in fdb.  The only thing I found that might apply to you is Clusters configured to use TLS could get stuck spending all of their CPU opening new connections., but I assume you're using the same connection receiving code, so you're probably fine.  The other TLS issues were various forms of crashes or bad behavior that were fixed.
There was also something that I recall Evan and Bala discussing, where non-TLS connections to a TLS server would work weirdly, and there was some discussion of trying to convince the TLS server to send back garbage bytes so that we know that it thinks there was a problem.  I can't seem to find any commit for this, so I'll leave Evan a message to ask if anything happened here.
But overall LGTM, and none of my comments are blocking.

Are FoundationDB knobs settable on doc layer binary? If not, then I think you have no way to control TLS cert refresh.

The connections between Document Layer and the backing KVS are not TLS encrypted as of right now, and I think there is no way for the user to configure that.

I went looking back over issues that were caused when TLS was enabled in fdb. The only thing I found that might apply to you is Clusters configured to use TLS could get stuck spending all of their CPU opening new connections., but I assume you're using the same connection receiving code, so you're probably fine. The other TLS issues were various forms of crashes or bad behavior that were fixed.

Yeah Document Layer uses the same connection receiving code.

There was also something that I recall Evan and Bala discussing, where non-TLS connections to a TLS server would work weirdly, and there was some discussion of trying to convince the TLS server to send back garbage bytes so that we know that it thinks there was a problem. I can't seem to find any commit for this, so I'll leave Evan a message to ask if anything happened here.

As of now, Document Layer's TLS feature works as following:

If the Document Layer server was started with TLS enabled, non-TLS connection will NOT be able to connect at all.
Similarly, if the server was started with TLS disabled, TLS connections will NOT be able to connect at all.

So we sort of avoided this problem, at least for now.

Test this please.

test this please

test this please


Using our dedicated stats endpoint for telemetry collection

Description
Using our private stats endpoint instead of Heap: https://stats.whylogs.com
Changes

Remove redundant checks
Enable dev endpoint

Related

[ ] I have reviewed the Guidelines for Contributing and the Code of Conduct.

Task linked: CU-2r7b2hy whylogs: switching to our new endpoint


chore(e2e): fix consistent timeouts

Ready for review.
Being perfectly honest, I'm not 100% sure why this fixes the issue. My theory is that adding the extra log statements just prevents Travis from thinking the task timed out.


Question about trained weights quantization

Hello,
I want to use weight of trained ResNet32 network for experimenting with the kit. I want to see how changing the weight quantization effect the accuracy of the network at the inference stage.
I want to try 3 types of weight precision: FP (no quantization), 8-bit and 4-bit on ideal tiles. From reviewing the source code, I found the function set_weights() which gets as an argument weight matrix and quantizes them. But I couldn't understand how can I specify the number of bins? could you please guide me to where should I look?
moreover, from you documentation I thought the kit could quantize the weights only to 8 or 4 bits (or not quantize at all), but here it looks like I can set any level of quantization, even quantize it into 2-bits. perhaps I've misunderstood something?
Thank you very much for your support.

Hi @ElinorG11,
Normally, we do not really support quantized weights, since the whole purpose of the toolkit is to simulate memristive in-memory compute, where weights are represented by conductances that naturally are analog values and cannot be quantized.  So the proper simulation to see the importance of the exact weight value is the sweep the (instantaneous) weight noise, which is set by the by the rpu_config.forward.w_noise parameter. Or alternatively, for inference only (using RPUInferenceConfig), one can increase the programming weight noise by increasing rpu_config.noise_model.prog_noise_scale which effectively reduces the precision of the weights written to the conductance values.
That being said,  in case of inference only, you can of course just loop through the analog layers, get weights, quantize and set the weights again. If you model is of type AnalogSequential you can use _apply_to_analog (see here) to do something like:
def quantize(mod):
    weight, bias = mod.get_weights()
    weightq = quantize(weight)  # your quantization method
    mod.set_weights()

# this loops through all analog modules and applies the above function :
model._apply_to_analog(quantize)

Hope that helps.

Thank you very much!!


URI not considered

I am trying to config the lib on a brand new project but when i perform a mutation, the request hits localhost (don't consider the uri i pass when configuring the client).
It looks like i am doing like the examples:
ApolloWrapper.tsx
"use client";

import { ApolloLink, HttpLink, concat } from "@apollo/client";
import {
  ApolloNextAppProvider,
  ApolloClient,
  InMemoryCache,
  SSRMultipartLink,
} from "@apollo/experimental-nextjs-app-support";

function makeClient() {
  const httpLink = new HttpLink({
    uri: "http://test.com",
    fetchOptions: { cache: "no-store" },
  });

  return new ApolloClient({
    cache: new InMemoryCache(),
    link: httpLink,
  });
}

export function ApolloWrapper({ children }: React.PropsWithChildren) {
  return (
    <ApolloNextAppProvider makeClient={makeClient}>
      {children}
    </ApolloNextAppProvider>
  );
}

layout.tsx
  return (
    <html suppressHydrationWarning={true} lang="fr">
      <body className={inter.className}>
          <ApolloWrapper>
            <AuthProvider initialUser={user}>
              <ResponsiveAppBar />
              {children}
            </AuthProvider>
          </ApolloWrapper>
      </body>
    </html>
  );
}

folder/page.tsx
import { gql, useMutation } from "@apollo/client";

export default function AddTodoPage() {
  const [addTodo, { data, loading, error }] = useMutation(ADD_TODO);

  try {
    addTodo({}); // localhost instead of test.com
  } catch(e) {
    // ...
  }
}

For debugging i have really hardcoded "http://test.com" be see if it would be reflected in the network when performing the mutation call and i see "localhost" instead.

Phew, that's extremely weird - that code hasn't been touched in years and  together with the Apollo Client core library, probably millions of devs are running this. Really all I can think of would be next not correctly bundling the environment variable.
Does is still log correctly of you put that console.log into the makeClient function?

I could have it work by manually rebuild my stack
I definitely have an issue with my hot reload which doesn't affect all the changes
Thanks for your time!

Great to hear that everything worked out :)

the same problem is reproduced in the local environment.
Is there currently no way around this other than hard-coding the specification to the uri?


[jdbc]Add a new Kyuubi jdbc connector

What changes were proposed in this pull request?
Create a new Kyuubi JDBC connector so that users may utilize Kyuubi to query Spark SQL and fill up Kyuubi JDBC in the hue.ini configuration file.
such as :
[[[kyuubi_jdbc]]]
name=Kyuubi_JDBC
interface=jdbc
options='{"url": "jdbc:hive2://xxxx:10009", "driver": "org.apache.kyuubi.jdbc.KyuubiHiveDriver", "user": "xxxx", "password": "xxxx"}'
How was this patch tested?
unit tests
Please review Hue Contributing Guide before opening a pull request.

Hey @chengduhaha, thanks for your PR for Kyuubi support using JDBC interface! We'll review it shortly.
Can you also please share the steps to create a test setup (kyuubi + sparksql) and the test scenarios you performed? That'll be very helpful!

Hey @chengduhaha, thanks for your PR for Kyuubi support using JDBC interface! We'll review it shortly.
Can you also please share the steps to create a test setup (kyuubi + sparksql) and the test scenarios you performed? That'll be very helpful!

Sure, here is my  test step:

Use the instructions at https://kyuubi.readthedocs.io/en/master/quick_start/ to install and launch Kyuubi.
Go to https://kyuubi.readthedocs.io/en/master/client/jdbc/kyuubi_jdbc.html to get the Kyuubi JDBC driver.
Update hue.ini with the Kyuubi JDBC interface.
Restart Hue after adding the Kyuubi JDBC driver path to your Java CLASSPATH.
Use the Hue Kyuubi JDBC Editor to run sparksql queries.

Testing Scenarios:
1.Test running various SQL queries from Hue，this includes basic DDL DML queries.
2.Test with multiple users or queries concurrently to ensure stability and proper resource management.

Hey @chengduhaha, thanks for your PR for Kyuubi support using JDBC interface! We'll review it shortly.
Can you also please share the steps to create a test setup (kyuubi + sparksql) and the test scenarios you performed? That'll be very helpful!

Hi @Harshg999 ,
Thank you for reviewing the pull request. I appreciate your interest in the setup and testing details. Here's a brief overview of how to set up a test environment for Kyuubi with Spark SQL and the testing scenarios I performed:
Setting up Kyuubi + Spark SQL Test Environment:
1.Use the instructions at https://kyuubi.readthedocs.io/en/master/quick_start/ to install and launch Kyuubi.
2.Go to https://kyuubi.readthedocs.io/en/master/client/jdbc/kyuubi_jdbc.html to get the Kyuubi JDBC driver.
3.Update hue.ini with the Kyuubi JDBC interface.
4.Restart Hue after adding the Kyuubi JDBC driver path to your Java CLASSPATH.
5.Use the Hue Kyuubi JDBC Editor to run sparksql queries.
Testing Scenarios:
1.Test running various SQL queries from Hue，this includes basic DDL DML queries.
2.Test with multiple users or queries concurrently to ensure stability and proper resource management.

Dear @bjornalm, @agl29, and @Harshg999,
I have submitted a pull request (PR) and require at least two approving reviews for this request to be merged. Please review my code at your earliest convenience and provide feedback or approval. Thank you very much for your time and assistance.
Sincerely,
chengduhaha

@chengduhaha Would you like to take up adding the Hue-Kyuubi JDBC config in the Hue documentation too? :)
You can try checking how JDBC config doc section is added for other connectors in https://docs.gethue.com/administrator/configuration/connectors/ and open a separate PR for a docs change.

Hi @Harshg999,
I wanted to extend my gratitude for your insightful review and valuable suggestions on my previous PR. I have made the recommended modifications and pushed the updated code.
Additionally, following your suggestion, I've created a new PR to add the Kyuubi JDBC config to the Hue documentation. The PR can be found here: Add Kyuubi JDBC Config to Hue Documentation #3593.
I'm looking forward to any feedback you might have on this new contribution.
Thanks again for your guidance and support!

hi, @chengduhaha ,I have already installed the previous steps, may I ask why there is an error when using hue to query kyuubi?
# kyuubi
 echo 'export KYUUBIL_HOME=/usr/share/hue/desktop/kyuubi' >> /etc/profile
 echo 'export CLASSPATH=$KYUUBIL_HOME/kyuubi-hive-jdbc-shaded-1.7.3.jar:$CLASSPATH' >> /etc/profile

restart hue_latest_test

Query error:

Here's a question,Hue not validating user credentials and just caching . Need to restart hue service to again prompt for login prompt if wrong credentials entered.（https://github.com/cloudera/hue/issues/3529）


Move $nds-output-default-print-styles to design system from core

$nds-output-default-print-styles is currently defined in nds-core. However, it's only used in the main NDS package, so it makes sense to live there, and not in core.

Same applies to $nds-output-glyph-classes

done in #273


Enable specifying candle period

!chart TSLA -weekly
Not sure how useful, probably low prio.

Added in https://github.com/e0/stock-chart-discord-bot/commit/3498833399c2a56c6c987f0c6bc497195e04b41e

daily: default
weekly: -w or --weekly
monthly: -m or --monthly


Bump Adaptive Cards to 2.*

Feature Request
https://www.npmjs.com/package/adaptivecards
There are a few breaking changes we will need to modify code on our side to support them.
Adaptive Cards renderer 2.1 is using schema of 1.3, not 2.x.
[Enhancement]

@Jeffders @p-nagpal FYI.

This bump will fix the bug brought up in #3111 (reference: https://github.com/microsoft/AdaptiveCards/issues/3829)


some python3 install instructions

...with pip3 dependency list missing as i don't know what they are 🤷♂
I added a sentence in there about checking if you already have it installed as (i think) it's fairly common for people to already have it, but possibly through some other method (gem?), so ideally this will reduce the issue of having a conflicting install

Thank you , I haven't got my hands on a Mac to try the instructions myself so any improvements/testing is much appreciated!


side-effects with multiple functions to track

It would be nice to distinguish which function is called when side-effects is used with multiple functions.
Assuming this code:
(defn g [_] nil)
(defn h [_] nil)
(defn f []
  (g :a)
  (h :b)
  (g :c))

The expected value doesn't tell which functions is called:
(expect [[:a]
         [:b]
         [:c]]
        (side-effects [g h]
          (f)))

I think this and #49 would make expectations more likely to be preferred over Midje. I would write the same test as such:
(fact "..."
  (f) => anything
  (provided (g :a) => irrelevant
            (h :b) => irrelevant
            (g :c) => irrelevant))

My point is not comparing different test frameworks but to mention that easy mocking is, IMO, an important feature. Expectations is beautiful.

sorry, this completely fell off my radar. I'll try to take a look in the next few days

Four minutes no replies then dis!!!!!11111
I want my money back!
LOL. JK. Take care.

:)
I meant #49 mostly. I'll look at both in parallel. Hopefully in the next few days. Headed to a wedding tomorrow and traveling all weekend. Next week though, I'll see what I can figure out.

putting my thoughts into #49


 The question remains of when we apply it to the whole back catalog of code.
There's a caveat in that pull requests which are open at time of blackification will be a little harder to merge. Perhaps we can say that once #537 is merged, we take the plunge.
To prevent every affected line referencing this commit in git blame, check out the following: https://docs.github.com/en/repositories/working-with-files/using-files/viewing-a-file#ignore-commits-in-the-blame-view

It might also be a good idea to add some docs to our meta repo on how to setup IDE's to run black and other tools automatically. I can do that as well


Issue: AttributeError: module 'livekit.agents.metrics' has no attribute 'PeriodicCollector' in livekit-plugins-deepgram 0.6.10

Issue Report: LiveKit Deepgram Plugin Error in Version 0.6.10
Error Summary:
AttributeError: module 'livekit.agents.metrics' has no attribute 'PeriodicCollector'
Problem Description:
When using livekit-plugins-deepgram version 0.6.10, the system encounters an AttributeError indicating that the PeriodicCollector is missing from the metrics module. This error prevents the STT (Speech-to-Text) functionality from initializing properly.
Key Error Message:
AttributeError: module 'livekit.agents.metrics' has no attribute 'PeriodicCollector'
Environment Details:

livekit: 0.18.1
livekit-agents: 0.11.2
livekit-plugins-deepgram: 0.6.10 (problematic version)
livekit-plugins-openai: 0.10.7
livekit-plugins-silero: 0.7.3
Python: 3.11

Detailed Error Log:
2024-11-16 08:52:36,008 - livekit.agents - DEBUG - http_session(): creating a new httpclient ctx
2024-11-16 08:52:36,009 - livekit.agents.pipeline - ERROR - Error in _recognize_task
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/livekit/agents/utils/log.py", line 16, in async_fn_logs
return await fn(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/livekit/agents/pipeline/human_input.py", line 100, in _recognize_task
stt_stream = self._stt.stream()
^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/livekit/plugins/deepgram/stt.py", line 249, in stream
return SpeechStream(self, config, self._api_key, self._ensure_session())
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/livekit/plugins/deepgram/stt.py", line 284, in init
self._audio_duration_collector = metrics.PeriodicCollector(
^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: module 'livekit.agents.metrics' has no attribute 'PeriodicCollector'
Resolution:
Downgrading livekit-plugins-deepgram to version 0.6.9 resolves the issue. The system functions correctly with this earlier version.
Steps to Reproduce:

Install livekit-plugins-deepgram version 0.6.10
Initialize STT with Deepgram
Attempt to create a speech stream
Observe AttributeError for missing PeriodicCollector

Steps to Resolve:

Downgrade livekit-plugins-deepgram:

pip install livekit-plugins-deepgram==0.6.9

Restart the application

Additional Notes:

The error appears to be introduced in version 0.6.10
No other package versions needed to be modified
The issue specifically relates to the metrics collection functionality in the Deepgram plugin
Version 0.6.9 remains stable and functional
The error occurs when attempting to initialize the speech recognition stream
The missing PeriodicCollector class in the metrics module suggests a possible dependency issue or incomplete implementation in version 0.6.10

Impact:
The error prevents the speech-to-text functionality from initializing, making the voice assistant feature completely non-functional when using version 0.6.10.
Copy CopyRetryClaude does not have the ability to run the code it generates yet.Ehata  başlığınıda  yazarmısınEditIssue: AttributeError: module 'livekit.agents.metrics' has no attribute 'PeriodicCollector' in livekit-plugins-deepgram 0.6.10
CopyIssue Report: LiveKit Deepgram Plugin Error in Version 0.6.10

Error Summary:
AttributeError: module 'livekit.agents.metrics' has no attribute 'PeriodicCollector'

Problem Description:
When using livekit-plugins-deepgram version 0.6.10, the system encounters an AttributeError indicating that the PeriodicCollector is missing from the metrics module. This error prevents the STT (Speech-to-Text) functionality from initializing properly.

Key Error Message:
AttributeError: module 'livekit.agents.metrics' has no attribute 'PeriodicCollector'

Environment Details:
- livekit: 0.18.1
- livekit-agents: 0.11.2
- livekit-plugins-deepgram: 0.6.10 (problematic version)
- livekit-plugins-openai: 0.10.7
- livekit-plugins-silero: 0.7.3
- Python: 3.11

Detailed Error Log:
2024-11-16 08:52:36,008 - livekit.agents - DEBUG - http_session(): creating a new httpclient ctx
2024-11-16 08:52:36,009 - livekit.agents.pipeline - ERROR - Error in _recognize_task
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/livekit/agents/utils/log.py", line 16, in async_fn_logs
return await fn(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/livekit/agents/pipeline/human_input.py", line 100, in _recognize_task
stt_stream = self._stt.stream()
^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/livekit/plugins/deepgram/stt.py", line 249, in stream
return SpeechStream(self, config, self._api_key, self._ensure_session())
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/livekit/plugins/deepgram/stt.py", line 284, in init
self._audio_duration_collector = metrics.PeriodicCollector(
^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: module 'livekit.agents.metrics' has no attribute 'PeriodicCollector'

**Resolution:**
Downgrading livekit-plugins-deepgram to version 0.6.9 resolves the issue. The system functions correctly with this earlier version.

Steps to Reproduce:
1. Install livekit-plugins-deepgram version 0.6.10
2. Initialize STT with Deepgram
3. Attempt to create a speech stream
4. Observe AttributeError for missing PeriodicCollector

Steps to Resolve:
1. Downgrade livekit-plugins-deepgram:
```bash
pip install livekit-plugins-deepgram==0.6.9

Restart the application

**Additional Notes:**

The error appears to be introduced in version 0.6.10
No other package versions needed to be modified
The issue specifically relates to the metrics collection functionality in the Deepgram plugin
Version 0.6.9 remains stable and functional
The error occurs when attempting to initialize the speech recognition stream
The missing PeriodicCollector class in the metrics module suggests a possible dependency issue or incomplete implementation in version 0.6.10

**Impact:**
The error prevents the speech-to-text functionality from initializing, making the voice assistant feature completely non-functional when using version 0.6.10.

Thank you for this was having the same issue.

sorry, we pushed an update to Deepgram without bumping a dependency's version. will fix this right now

Thank you to the LiveKit team for quickly resolving the issue we encountered and providing excellent support. Their swift solution and professional approach are truly commendable. Wishing you continued success!


materia-kde-theme: init at 20210612

Motivation for this change
I plan to switch from archlinux with nix to nixos, so I'm trying to add this pkg to nixpkgs, with some reference to the arc-kde implementation for some work. Please let me know if there are any shortcomings.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes

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

[x] Fits CONTRIBUTING.md.

The problematic part has been revised.


Library\PackageCache\com.unitynative.toasts@ac09d7fc59\UnityNativeToasts.cs(39,46): error CS0246: The type or namespace name 'NullUnityNativeToastsAdapter' could not be found (are you missing a using directive or an assembly reference?)

Copied from

Fixed in v1.0.3 and closed #4


[crash] SubscriptionCallback::OnReportEnd()

Problem
Crash seen during stability testing with SHA 5d8599d195a93dfe5473f64e4f888c322e5df1d2
Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000010
Exception Codes: 0x0000000000000001, 0x0000000000000010
VM Region Info: 0x10 is not in any region.  Bytes before following region:<PHONE_NUMBER>0
      REGION TYPE                 START - END      [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
      UNUSED SPACE AT START
--->
      commpage (reserved)<PHONE_NUMBER>-7000000000 [384.0G] ---/--- SM=NUL  ...(unallocated)
Termination Reason: SIGNAL 11 Segmentation fault: 11
Terminating Process: exc handler [16211]

0   CHIP                          	       0x188393dac invocation function for block in (anonymous namespace)::SubscriptionCallback::OnReportEnd() + 20 (connectedhomeip/src/darwin/Framework/CHIP/CHIPDevice.mm:1409)
1   libdispatch.dylib             	       0x1d12cb7ac _dispatch_call_block_and_release + 32 (Sources/libdispatch/src/init.c:1518)
2   libdispatch.dylib             	       0x1d12cd2d0 _dispatch_client_callout + 20 (Sources/libdispatch/src/object.m:560)
3   libdispatch.dylib             	       0x1d12d49d4 _dispatch_lane_serial_drain + 672 (Sources/libdispatch/src/inline_internal.h:2631)
4   libdispatch.dylib             	       0x1d12d5554 _dispatch_lane_invoke + 436 (Sources/libdispatch/src/queue.c:3939)
5   libdispatch.dylib             	       0x1d12e00a8 _dispatch_workloop_worker_thread + 652 (Sources/libdispatch/src/queue.c:6766)
6   libsystem_pthread.dylib       	       0x1d1532fe4 _pthread_wqthread + 288 (Sources/libpthread/src/pthread.c:2618)
7   libsystem_pthread.dylib       	       0x1d153a5c8 start_wqthread + 8

2022-07-22 14:03:21.7033 -0700 default 0x17dbf1 0x0 homed[16211] (CHIP): 🟢 [1658523801634] [16211:1563633] CHIP: [EM] Removed CHIP MessageCounter:174118038 from RetransTable on exchange 15319i
2022-07-22 14:03:21.7227 -0700 default 0x17dbf1 0x0 homed[16211] (CHIP): 🔵 [1658523801653] [16211:1563633] CHIP: [DMG] Refresh LivenessCheckTime for 25000 milliseconds with SubscriptionId = 0x4e4b0c04 Peer = 01:00000000FB384A57
2022-07-22 14:03:21.7228 -0700 default 0x17dbf1 0x0 homed[16211] (CHIP): 🟢 [1658523801654] [16211:1563633] CHIP: [EM] Piggybacking Ack for MessageCounter:87523897 on exchange: 15319i
2022-07-22 14:03:21.7229 -0700 default 0x17dbf1 0x0 homed[16211] (CHIP): 🔵 [1658523801654] [16211:1563633] CHIP: [IN] Prepared secure message 0x103029e68 to 0x00000000FB384A57 (1)  of type 0x1 and protocolId (0, 1) on exchange 15319i with MessageCounter:174118039.
2022-07-22 14:03:21.7230 -0700 default 0x17dbf1 0x0 homed[16211] (CHIP): 🔵 [1658523801654] [16211:1563633] CHIP: [IN] Sending encrypted msg 0x103029e68 with MessageCounter:174118039 to 0x00000000FB384A57 (1) at monotonic time:<PHONE_NUMBER>2A2900 msec
2022-07-22 14:03:21.9020 -0700 default 0x17dd00 0x0 homed[16211] (CHIP): 🔵 [1658523801833] [16211:1563904] CHIP: [EM] Received message of type 0x5 with protocolId (0, 1) and MessageCounter:87523898 on exchange 15319i
2022-07-22 14:03:21.9020 -0700 default 0x17dd00 0x0 homed[16211] (CHIP): 🟢 [1658523801833] [16211:1563904] CHIP: [EM] Found matching exchange: 15319i, Delegate: 0x105b57ac0
2022-07-22 14:03:21.9020 -0700 default 0x17dd00 0x0 homed[16211] (CHIP): 🟢 [1658523801833] [16211:1563904] CHIP: [EM] Rxd Ack; Removing MessageCounter:174118039 from Retrans Table on exchange 15319i
2022-07-22 14:03:21.9020 -0700 default 0x17dd00 0x0 homed[16211] (CHIP): 🟢 [1658523801833] [16211:1563904] CHIP: [EM] Removed CHIP MessageCounter:174118039 from RetransTable on exchange 15319i
2022-07-22 14:03:21.9091 -0700 default 0x17dd00 0x0 homed[16211] (CHIP): 🔵 [1658523801840] [16211:1563904] CHIP: [DMG] Refresh LivenessCheckTime for 25000 milliseconds with SubscriptionId = 0x4e4b0c04 Peer = 01:00000000FB384A57
2022-07-22 14:03:21.9092 -0700 default 0x17dd00 0x0 homed[16211] (CHIP): 🟢 [1658523801840] [16211:1563904] CHIP: [EM] Piggybacking Ack for MessageCounter:87523898 on exchange: 15319i
2022-07-22 14:03:21.9092 -0700 default 0x17dd00 0x0 homed[16211] (CHIP): 🔵 [1658523801840] [16211:1563904] CHIP: [IN] Prepared secure message 0x103029e68 to 0x00000000FB384A57 (1)  of type 0x1 and protocolId (0, 1) on exchange 15319i with MessageCounter:174118040.
2022-07-22 14:03:21.9093 -0700 default 0x17dd00 0x0 homed[16211] (CHIP): 🔵 [1658523801840] [16211:1563904] CHIP: [IN] Sending encrypted msg 0x103029e68 with MessageCounter:174118040 to 0x00000000FB384A57 (1) at monotonic time:<PHONE_NUMBER>2A29BA msec
2022-07-22 14:03:22.1309 -0700 default 0x17dd00 0x0 homed[16211] (CHIP): 🔵 [1658523802062] [16211:1563904] CHIP: [EM] Received message of type 0x5 with protocolId (0, 1) and MessageCounter:87523899 on exchange 15319i
2022-07-22 14:03:22.1309 -0700 default 0x17dd00 0x0 homed[16211] (CHIP): 🟢 [1658523802062] [16211:1563904] CHIP: [EM] Found matching exchange: 15319i, Delegate: 0x105b57ac0
2022-07-22 14:03:22.1311 -0700 default 0x17dd00 0x0 homed[16211] (CHIP): 🟢 [1658523802062] [16211:1563904] CHIP: [EM] Rxd Ack; Removing MessageCounter:174118040 from Retrans Table on exchange 15319i
2022-07-22 14:03:22.1311 -0700 default 0x17dd00 0x0 homed[16211] (CHIP): 🟢 [1658523802062] [16211:1563904] CHIP: [EM] Removed CHIP MessageCounter:174118040 from RetransTable on exchange 15319i
2022-07-22 14:03:22.1447 -0700 default 0x17dd00 0x0 homed[16211] (CHIP): 🔵 [1658523802076] [16211:1563904] CHIP: [DMG] Refresh LivenessCheckTime for 25000 milliseconds with SubscriptionId = 0x4e4b0c04 Peer = 01:00000000FB384A57
2022-07-22 14:03:22.1448 -0700 default 0x17dd00 0x0 homed[16211] (CHIP): 🟢 [1658523802076] [16211:1563904] CHIP: [EM] Piggybacking Ack for MessageCounter:87523899 on exchange: 15319i
2022-07-22 14:03:22.1449 -0700 default 0x17dd00 0x0 homed[16211] (CHIP): 🔵 [1658523802076] [16211:1563904] CHIP: [IN] Prepared secure message 0x103029e68 to 0x00000000FB384A57 (1)  of type 0x1 and protocolId (0, 1) on exchange 15319i with MessageCounter:174118041.
2022-07-22 14:03:22.1449 -0700 default 0x17dd00 0x0 homed[16211] (CHIP): 🔵 [1658523802076] [16211:1563904] CHIP: [IN] Sending encrypted msg 0x103029e68 with MessageCounter:174118041 to 0x00000000FB384A57 (1) at monotonic time:<PHONE_NUMBER>2A2AA6 msec
2022-07-22 14:03:22.2826 -0700 default 0x17dd00 0x0 homed[16211] (CHIP): 🔵 [1658523802213] [16211:1563904] CHIP: [EM] Received message of type 0x5 with protocolId (0, 1) and MessageCounter:87523900 on exchange 15319i
2022-07-22 14:03:22.2826 -0700 default 0x17dd00 0x0 homed[16211] (CHIP): 🟢 [1658523802213] [16211:1563904] CHIP: [EM] Found matching exchange: 15319i, Delegate: 0x105b57ac0
2022-07-22 14:03:22.2827 -0700 default 0x17dd00 0x0 homed[16211] (CHIP): 🟢 [1658523802213] [16211:1563904] CHIP: [EM] Rxd Ack; Removing MessageCounter:174118041 from Retrans Table on exchange 15319i
2022-07-22 14:03:22.2827 -0700 default 0x17dd00 0x0 homed[16211] (CHIP): 🟢 [1658523802213] [16211:1563904] CHIP: [EM] Removed CHIP MessageCounter:174118041 from RetransTable on exchange 15319i
2022-07-22 14:03:22.2992 -0700 default 0x17dd00 0x0 homed[16211] (CHIP): 🔵 [1658523802230] [16211:1563904] CHIP: [DMG] Refresh LivenessCheckTime for 25000 milliseconds with SubscriptionId = 0x4e4b0c04 Peer = 01:00000000FB384A57
2022-07-22 14:03:22.2993 -0700 default 0x17dd00 0x0 homed[16211] (CHIP): 🟢 [1658523802230] [16211:1563904] CHIP: [EM] Piggybacking Ack for MessageCounter:87523900 on exchange: 15319i
2022-07-22 14:03:22.2994 -0700 default 0x17dd00 0x0 homed[16211] (CHIP): 🔵 [1658523802230] [16211:1563904] CHIP: [IN] Prepared secure message 0x103029e68 to 0x00000000FB384A57 (1)  of type 0x1 and protocolId (0, 1) on exchange 15319i with MessageCounter:174118042.
2022-07-22 14:03:22.2994 -0700 default 0x17dd00 0x0 homed[16211] (CHIP): 🔵 [1658523802230] [16211:1563904] CHIP: [IN] Sending encrypted msg 0x103029e68 with MessageCounter:174118042 to 0x00000000FB384A57 (1) at monotonic time:<PHONE_NUMBER>2A2B41 msec
022-07-22 14:03:22.5343 -0700 default 0x17dd01 0x0 homed[16211] (CHIP): 🔵 [1658523802465] [16211:1563905] CHIP: [EM] Received message of type 0x4 with protocolId (0, 1) and MessageCounter:87523901 on exchange 15319i
2022-07-22 14:03:22.5343 -0700 default 0x17dd01 0x0 homed[16211] (CHIP): 🟢 [1658523802465] [16211:1563905] CHIP: [EM] Found matching exchange: 15319i, Delegate: 0x105b57ac0
2022-07-22 14:03:22.5344 -0700 default 0x17dd01 0x0 homed[16211] (CHIP): 🟢 [1658523802465] [16211:1563905] CHIP: [EM] Rxd Ack; Removing MessageCounter:174118042 from Retrans Table on exchange 15319i
2022-07-22 14:03:22.5344 -0700 default 0x17dd01 0x0 homed[16211] (CHIP): 🟢 [1658523802465] [16211:1563905] CHIP: [EM] Removed CHIP MessageCounter:174118042 from RetransTable on exchange 15319i
2022-07-22 14:03:22.5345 -0700 default 0x17dd01 0x0 homed[16211] (CHIP): 🟢 [1658523802465] [16211:1563905] CHIP: [DMG] mResubscribePolicy is null
2022-07-22 14:03:22.5345 -0700 default 0x17dd01 0x0 homed[16211] (CHIP): 🟢 [1658523802465] [16211:1563905] CHIP: [DMG] MoveToState ReadClient[0x105b57ac0]: Moving to [      Idle]
2022-07-22 14:03:22.5345 -0700 default 0x17dd01 0x0 homed[16211] (CHIP): 🟢 [1658523802465] [16211:1563905] CHIP: [EM] Sending Standalone Ack for MessageCounter:87523901 on exchange 15319i
2022-07-22 14:03:22.5346 -0700 default 0x17dd01 0x0 homed[16211] (CHIP): 🔵 [1658523802465] [16211:1563905] CHIP: [IN] Prepared secure message 0x16f6fd288 to 0x00000000FB384A57 (1)  of type 0x10 and protocolId (0, 0) on exchange 15319i with MessageCounter:174118043.
2022-07-22 14:03:22.5346 -0700 default 0x17dd01 0x0 homed[16211] (CHIP): 🔵 [1658523802465] [16211:1563905] CHIP: [IN] Sending encrypted msg 0x16f6fd288 with MessageCounter:174118043 to 0x00000000FB384A57 (1) at monotonic time:<PHONE_NUMBER>2A2C2C msec
2022-07-22 14:03:22.5347 -0700 default 0x17dd01 0x0 homed[16211] (CHIP): 🟢 [1658523802465] [16211:1563905] CHIP: [EM] Flushed pending ack for MessageCounter:87523901 on exchange 15319i

Apple reference: rdar://97467750

0   CHIP                          	       0x188393dac invocation function for block in (anonymous namespace)::SubscriptionCallback::OnReportEnd() + 20 (connectedhomeip/src/darwin/Framework/CHIP/CHIPDevice.mm:1409)

That line on 5d8599d195a93dfe5473f64e4f888c322e5df1d2 looks like this:
    if (mEventReportCallback && eventReports.count) {
        dispatch_async(mQueue, ^{
1409 --> mEventReportCallback(eventReports);
        });
    }

the crash is a null-deref.  This looks a lot like https://github.com/project-chip/connectedhomeip/issues/21453 and should have been fixed by https://github.com/project-chip/connectedhomeip/pull/21456


Move the About Us text to Settings Activity

Move the About Us text to SettingsActivity and delete the AboutUs Activity.

Interested in taking up this issue? Leave a comment expressing your interest.
Each issue expects a 24hr turnaround time by default. In case where a student doesn't come back with an update after 24 hours have elapsed, the issue is up for grabs by anyone.

I have changed but unable to push it error code 403

If instead of moving about us text to settings activity if we put a option of terms of use at the bottom of settings activity alongwith adding a copyright symbol definitely with small font so what are your views regarding that @numerative

yeah @chanmol1999 we can do that


remove fragment sign ("#") from URLs without fragment

the "#" sign existed on URLs before the query sign "?" which made rails believe there are no params in the url (e.g. ventory.com#?param1=value1&param2=value2 was recognized as the request for ventory.com without params.).
removing the "#" sign was necessary in case there is no fragment in the url.
Thanks

Hi @tomdov - thank you for taking the time to send this PR!
This was originally a workaround for a bug in angular itself.  Hopefully I'll have time for this tomorrow or this weekend.

Hi,
have you checked this? can it be merged?
Thanks in advance and thanks for this gem!

Hit this in the wild the other day. LGTM!


Consider how to handle study resuming from the same browser, different browsers, and different devices

Copying the current url from one browser to another might not necessarily work, but copying a link from the email/prolific again and reopening elsewhere should

Same browser is handled. We still need something for different browsers. Probably using the prolific ID to inform the participantId


Namemangling revamp

The name mangling needs revamp, for both correctness and overall efficiency (do not allocate as much to construct the mangled names; and make the mangled names shorter). See #2175.

Do we need to include the namespaces in the typenames? What if we instead just use the type simple name; and disambiguate it if there is conflict - similar to what we do for methods.
Use shortcut for the system module or frequently used system types. E.g. The reference to System.String type today is something like: System_Private_CoreLib__System__String. What if it is just something like #String?
CppCodeGen and native codegen name mangling can be quite different
Store the mangled strings as UTF8
Robustness against collisions with built-in C++ identifiers or our internal identifiers

Do we want to make this also track #32 and close that one?

We should make the mangled names more global ready, too. Currently if you are a Japanese developer, your generated C++ will most likely crash, and if not identifiers will all look like _____::_____ etc


Support getting all testers instead of specifying an app_id

Would like to go through all our testers and/or go through an array of app ids. To do a proper house cleaning of testers.
I'd be happy to try and submit a PR.
https://github.com/KrauseFx/fastlane-plugin-clean_testflight_testers/blob/5ac11aafa4426ec3666c241b649c5fcce4fcede7/lib/fastlane/plugin/clean_testflight_testers/actions/clean_testflight_testers_action.rb#L19
We are only removing for a specific app_identifier.

Should the and/or be a separate issue? :)

Yeah, a PR sounds great 👍

I'll try and spent sometime on it during the weekend 👍

I guess iTunesConnect was updated since I last looked at User roles (Last week) I remember there being a External Tester page...
They removed that since. So back providing an array of app_ids :)


Fix errors in cli parameter description in README

To be clear; The current documentation is incorrect; typer doesn't work with lower-case.
Try it out! :)


pinning pytest in install dependencies is incorrect

this file: requirements.txt
this file: setup.cfg

Pin pytest as an install dep, which is incorrect.
At most could it be a build dependency.

Hello @drake-mer and thanks for the issue, will check this and come back to you as soon as the problem will be solved.
Have a nice day,
David, Product Manager for Flagship

Hi @drake-mer, thx for your feedback. i have merged @remihuguet PR #18 . Have a nice day.


Enabled gzip compression

Added gzip compression interceptor

Confirmed! @antonkazakov  has signed the Individual Contributor License Agreement. Thanks so much

Any news on these PRs?

ping @mhadam

@mhadam Great news. Thank you!

@antonkazakov Just wanted to point out that there's no collector support for gzip encoding right now, so we should make sure that's at least PR'd on a collector before this gets released.

the relevant issue is https://github.com/snowplow/snowplow/issues/4006 if you want to have a look :+1:

This PR has been on hold for a long time because blocked by https://github.com/snowplow/stream-collector/issues/9.
Considering it seems a task with low priority, I'm closing this PR for now. We will rework on this when the relative ticket on Stream Collector is in-progress.
cc @paulboocock


Contributing to jexcel docs

This isn't so much an issue as a question about contributing --
I'm an avid user of the library, and have submitted a few issues in the past as well.  I'd love to contribute to the library and I thought a good way to start would be by improving the docs, starting with React.
Since React has added hooks and is moving away from class components, I thought it might be helpful to add an implementation for that in the docs.  But -- I couldn't find the repository that backs https://bossanova.uk/jexcel/v3/docs.  Is it open-source? Would contributing to this repo be helpful?

Hi @leahein, I'm interested to use this library in my next project. Do you have a working example of the library using hooks? I'll be very grateful if you can share it.
Thanks!

Sure :)
You can see the working code here.
The code sandbox translates the example provided by the jexcel docs here, but it uses a functional React component with hooks, rather than a class-based one.
It leverages the useRef hook as a way to access the DOM div element, and the useEffect hook to create the jexcel table as a side-effect after the component renders.
Let me know if you have any questions.
@paulhodel Feel free to include this example using hooks in the docs here.
Happy to provide additional documentation as well.

Thanks, I have included your example in the website. ;)

For documentation, examples contributions
https://github.com/paulhodel/jexcel-documentation

Hi, here is a small fix regarding the use of the library in react + typescript:
import { useRef, useEffect } from 'react'
import jspreadsheet from 'jspreadsheet-ce';

import '../node_modules/jspreadsheet-ce/dist/jspreadsheet.css';

function App() {
  const jRef = useRef<HTMLDivElement>(null);

  useEffect(() => {
    if (jRef?.current && typeof jRef?.current === 'object' && !('jspreadsheet' in jRef.current)) {
      jspreadsheet(jRef.current, {data: [[]], minDimensions: [10, 10]});
    }
  }, []);

  const addRow = () => {
    if (jRef?.current && typeof jRef?.current === 'object' && 'jexcel' in jRef.current) {
      (jRef.current as jspreadsheet.JspreadsheetInstanceElement).jexcel.insertRow();
    }
  };

  return (

      <input type='button' onClick={addRow} value='Add new row' />

  );
}

export default App


Add Japanese translation to subdivisions data

Added Japanese translation to some subdivisions data files.

Thanks for the PR! ❤


Several Win Trojan Detections:  dss-windows-amd64.exe.zip

Hello - for your awareness regarding executable binaries, the zip-extracted EXE (20.8 MB) for dss-windows-amd64.exe.zip released two days ago at https://github.com/GlobalCyberAlliance/DomainSecurityScanner/releases is triggering the following online malware file checking services:
VirtusTotal -
Detected  - Trojan.Malware.300983.susgen
https://www.virustotal.com/gui/file/19300db7ce81db811d0bd9af125a406dab57b3dc6391398cbe3c64d88447a1bd
Microsoft Security Intelligence Submission
Detected - Trojan:Win32/Sabsik.FL.A!ml
Detected by Microsoft Defender Antivirus
https://www.microsoft.com/en-us/wdsi/submission/dc12bd13-5ee1-440b-bfd8-f56c6f11511e
Could you please review and advise?
Respectfully,
Orlando Stevenson
dss-windows-amd64_(infected).zip

Hey @OrlandoNE, thanks for bringing this to our attention. I'm not too sure why this would be detected as a trojan, but rest assured that we're looking into it.

@OrlandoNE this seems like nothing more than a false positive. I've checked both the most recent build, and the build before that, and only one provider (MaxSecure) seems to flag the binaries as containing trojans. Our source code is completely open, and you can review the build process here: https://github.com/GlobalCyberAlliance/DomainSecurityScanner/blob/main/.github/workflows/release.yml
Unless you have any other queries or suggestions as to what may be triggering this false positive, I'll close this out. Thanks again!

Hello - thank you for promptly responding and checking into this issue!
My Microsoft submission also came back as a false positive following further review with the following analyst comments:
"t this time, the submitted files do not meet our criteria for malware or potentially unwanted applications. The detection has been removed. Please follow the steps below to clear cached detections and obtain the latest malware definitions.... "
More:  https://www.microsoft.com/en-us/wdsi/submission/dc12bd13-5ee1-440b-bfd8-f56c6f11511e
:)

@wolveix Hello - thank you for promptly responding and checking into this issue!
My Microsoft submission also came back as a false positive following further review with the following analyst comments:
"t this time, the submitted files do not meet our criteria for malware or potentially unwanted applications. The detection has been removed. Please follow the steps below to clear cached detections and obtain the latest malware definitions.... "
More:  https://www.microsoft.com/en-us/wdsi/submission/dc12bd13-5ee1-440b-bfd8-f56c6f11511e
:)


feat: add python bindings

We face this problem of coordinating repos, where the python side of
things needs to know many constants and message data structures that
need to match c++. It's really annoying to keep these synchronized, and
really annoying to do cross-repo work. The solution is to move the
bindings to the same place as the firmware, and (eventually) make a
single source of truth for the messages by having the python generate
the c++ (since that code is written already).
This adds a new directory python/ containing a new python package
opentrons_ot3_firmware, which contains the section of opentrons_hardware
that just contains static object definitions for messages and also some
constants, along with its tests.
The python constants.py and associated scripts is used to generate the canbus
ids header.

So I understand this properly, the new way of adding CAN messages would be:
1. Add the message ids/definitions in `python` of this repo

Yup

2. Have that code generate the C++ code

Yeah, but you don't have to do anything special for this - cmake should notice that the python was edited and regenerate everything the next time you build.

3. Also synchronize it with the monorepo, or are we eventually adding all CAN Bus handling stuff into this repo?

The next step is to have the monorepo use this package, yeah, so in theory we'll be able to update this and the monorepo will pick it up. Exactly how that works I haven't decided yet.


🐛 [Crashlytics] Build error links to internal Google login page for Google employees rather than Firebase console

Bug report
When building an app for iOS that uses Crashlytics, build output says to visit https://firebase.corp.google.com/, a website that requires<EMAIL_ADDRESS>credentials.
Steps to reproduce
Prerequisites: A Flutter project with Firebase imported and Crashlytics added.
Steps to reproduce the behavior:

flutter build ipa --obfuscate --split-debug-info ./debug-info

Expected behavior
A message appears telling me to upload dSYMs and provides a link to do so.
Actual behaviour
Such a message appears, but the link is broken.
    Running upload-symbols in Build Phase mode
    error: Flutter build with --obfuscate enabled. Crashlytics does not support
    uploading obfuscated dSYMs via the command line. Please upload dSYMs through
    the Firebase console web uploader at
    https://firebase.corp.google.com/project/_/crashlytics
    Command PhaseScriptExecution failed with a nonzero exit code

The link https://firebase.corp.google.com/project/_/crashlytics redirects to https://login.corp.google.com/request?..., which asks me for an email address ending in<EMAIL_ADDRESS>Sample project
https://github.com/wesleym/corptest - basically an empty project with Firebase, Crashlytics

Additional context

A closely related issue was previously reported as https://github.com/firebase/flutterfire/issues/3795, but the response didn't specifically address that links to firebase.corp.google.com do not work for public users.
https://github.com/firebase/flutterfire/issues/10994 has the same repro steps, and that bug also quotes the same build output with the same broken link.
This document also refers to https://firebase.corp.google.com/: https://github.com/firebase/flutterfire/blob/81f1b80c445cfaab3e7752b8c58f35c92d234d8d/packages/firebase_performance/firebase_performance/example/README.md

Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
➜  src flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.10.2, on macOS 13.2.1 22D68 darwin-arm64, locale
    en-CA)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.2)
[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.1)
[✓] VS Code (version 1.78.2)
[✓] Connected device (3 available)
    ! Error: (null) needs to connect to determine its availability. Check the
      connection between the device and its companion iPhone, and the connection
      between the iPhone and Xcode. Both devices may also need to be restarted
      and unlocked. (code 1)
[✓] Network resources

• No issues found!

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
➜  corptest git:(main) flutter pub deps -- --style=compact
Dart SDK 3.0.2
Flutter SDK 3.10.2
corptest 1.0.0+1

dependencies:
- cupertino_icons 1.0.5
- firebase_crashlytics 3.3.2 [firebase_core firebase_core_platform_interface firebase_crashlytics_platform_interface flutter stack_trace]
- flutter 0.0.0 [characters collection js material_color_utilities meta vector_math sky_engine]

dev dependencies:
- flutter_lints 2.0.1 [lints]
- flutter_test 0.0.0 [flutter test_api path fake_async clock stack_trace vector_math async boolean_selector characters collection js matcher material_color_utilities meta source_span stream_channel string_scanner term_glyph]

transitive dependencies:
- _flutterfire_internals 1.3.2 [collection firebase_core firebase_core_platform_interface flutter meta]
- async 2.11.0 [collection meta]
- boolean_selector 2.1.1 [source_span string_scanner]
- characters 1.3.0
- clock 1.1.1
- collection 1.17.1
- fake_async 1.3.1 [clock collection]
- firebase_core 2.13.1 [firebase_core_platform_interface firebase_core_web flutter meta]
- firebase_core_platform_interface 4.8.0 [collection flutter flutter_test meta plugin_platform_interface]
- firebase_core_web 2.5.0 [firebase_core_platform_interface flutter flutter_web_plugins js meta]
- firebase_crashlytics_platform_interface 3.6.2 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
- flutter_web_plugins 0.0.0 [flutter js characters collection material_color_utilities meta vector_math]
- js 0.6.7 [meta]
- lints 2.1.0
- matcher 0.12.15 [async meta stack_trace term_glyph test_api]
- material_color_utilities 0.2.0
- meta 1.9.1
- path 1.8.3
- plugin_platform_interface 2.1.4 [meta]
- sky_engine 0.0.99
- source_span 1.9.1 [collection path term_glyph]
- stack_trace 1.11.0 [path]
- stream_channel 2.1.1 [async]
- string_scanner 1.2.0 [source_span]
- term_glyph 1.2.1
- test_api 0.5.1 [async boolean_selector collection meta source_span stack_trace stream_channel string_scanner term_glyph matcher]
- vector_math 2.1.4

That log is not produced by FlutterFire, but by the firebase iOS SDK. More specifically, it is created by the FirebaseCrashlytics/upload-symbols script. Please file an issue on that repository here if you wish to get it fixed: https://github.com/firebase/firebase-ios-sdk
If you want to manually upload symbols, you just have to open Crashlytics in the Firebase console and upload them here:


Build Failed

Please don't do fixes in this way.
If you want to fix anything - add a new tag.
At this moment our builds are broken cuz Xcode 13.2 can't find package product 'MedalliaPackage'. And
And the previous version was good.
'Reset packages cache' and other commands don't help. As result, we will try to use manual integration and this is not the first time.

Hi @Chevit
What you're suggesting won't work in Xcode 13.3 and above.
First, you need to remove the package from your project
Clear the Swift Package Manager cache on your machine by going to ~/Library/Caches/org.swift.swiftpm/ and delete:
Digital-iOS-SDK folder
Digital-iOS-SDK lock file
Then please reintegrate with version 4.0.2
If for some reason it doesn't work for you please contact your Medallia's CSM and we'll schedule a meeting.

We ran into the same issue.  Our build broke and I can't re-add it using SPM for a specific version or range of versions (like we were doing).
I'm working around this issue by pointing to the main branch rather than specifying a version.

Hi @noelstieglitz
You can point to exact version 4.0.2 or if you don't want to use exact version it should be between 4.0.0 to 5.0.0
You can see that the 4.0.2 tag exist here https://github.com/medallia/Digital-iOS-SDK/tags
If you're still experiencing this issue, please contact your Medallia's CSM and we'll schedule a meeting

@OriMedallia thanks for following up.  We were successfully referencing this project pointing to 3.9.1 prior to the update to this repo ~8 days ago. After the latest changes, I receive an error on my dev machine (as well as in the CI pipeline, pointing to it not being a cache issue) trying to reference this library using SPM.  As I mentioned in my previous comment, I also am not able to add a reference using a specific version or a range of versions.  Steps to reproduce:

Clear the cache per your recommendation above.
Following the steps described in the readme (https://github.com/medallia/Digital-iOS-SDK/blob/main/README.md), reference a specific version or range of versions.  Try 4.0.2 or 4.00 - 5.0.0.
See an error in the Xcode SPM UI that the "package resolution failed"

I can temporarily work around this issue by following the steps in the readme, except instead of choosing a specific version or a range of versions, choosing "branch" -> main.  This is obviously a bad long term solution because anytime you push to this repo, we'll get latest, which could cause unexpected changes in our CI pipeline vs. our local environment. @Chevit's solution is the better long term solution if you guys aren't able to fix the repo.
Interestingly I'm not seeing any reference to the previously existing (at least looking at our references, looks like it used to exist) 3.9.1 tag and I'm seeing multiple commits against the same 4.0.2 tag.

@noelstieglitz  Can please try to create a new project with v4.0.2 and let me know if the issue is reproduceable on an empty project? Thanks


Some questions about the project

Hey !
I'm looking into this project because i want to render html in "headless" mode but chrome feels too slow. I've tried to compile the project without success (i'm under linux though).
I was mainly wondering whats the status of this ? Do you plan to actually use it one day ?
I also saw some of your other projects (phaneron or beamcoder which are awesome !) so i also wanted to thank you for all the work !
Regards

This project is on a list of projects "to be finished" as it will be a key component of Phaneron - creating software-generated graphical overlays. I expect to complete it during the autumn. The aim is to build a CasparCG-like application from a set of reusable Node building blocks. That will be a cross-platform project so ceforama will be checked to work under Linux at that point ... but for now my main development platform is Windows.
You might be interested in elecular which performs a similar function to ceforama but from within an Electron context. That project is experimental but I know of one company that uses that approach to render HTML at 50fps.
Thanks for your interest in our work and happy media coding!
Regards,
Richard

@sparkpunkd thanks for your quick response. To be a little more precise, our use case is to render content (which can be a image, gif or video) dynamically depending on the user as fast as possible. Definitely looking forward this implementation and i will check elecular too, thanks again !


Transfer from child

There are a few FIXMES pending but I'd like to merge this already mainly to avoid future conflicts.

All tests pass for me in both branches. I'll have to check when it's merged why they don't pass.


unable to see text because of its colour

Before Creating an issue

Are you running the latest version?
Are you reporting to the correct repository?
Did you search existing issues?

Unable to see button's text because of its colour
When saving an SR, unable to see text on button because of its colour
See attached.
Please use code blocks to show formatted errors or code snippets

:warning: Reports we cannot reproduce are at risk of being marked stale and
closed. The more information you can provide, the more likely we are to look
into and address your issue.

Forgot to mention, this is from OHIF's v3-stable branch.

I can see this on the current demo url. Likely related to this change: #3031?

thanks.


Azure Security Benchmark v1

I believe v3 is out for the ASB, can you update the link and info please?
Thanks

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 8925ae80-af82-f464-b700-511ddc0cbdf1
Version Independent ID: 5c29f4a8-7ecd-74b5-abb2-33ad118caed2
Content: Azure Policy Regulatory Compliance controls for Azure Logic Apps - Azure Logic Apps
Content Source: articles/logic-apps/security-controls-policy.md
Service: logic-apps
GitHub Login: @ecfan
Microsoft Alias: estfan

Hi @henrypi73,
Thanks for reaching out! The doc will be updated to be version agnostic. The changes will publish later today.
@mike-urnun-msft: #please-close


adding creation of service account to the deployments

/cc @cooktheryan
/cc @sallyom
This is the service account per component feature.

Moving to #76


fix: cargo-generate.toml not picked up on interactive template selection

Fixes #468

/rebase

Rebased and ready :-)


Null reference if command classes have same name

Reported by gyd via email.
in my project, i created my own PlayAudio command, but i forget to rename the class to MGPlayAudio. ( and the priority is 1 )
it compile success, i think it's because PlaySound is in the scope of namespace fungus.
when we add the command, it's okay, but later it will become null component ( make sence ).
the issue is, after that, the command is broken, and the error code is here:
NullReferenceException: Object reference not set to an instance of an object
Fungus.BlockInspectorEditor+c__AnonStorey1.<>m__1 (Fungus.CommandEditor e) (at Assets/Fungus/Flowchart/Editor/BlockInspector.cs:137)
System.Linq.Enumerable+c__Iterator1D1[Fungus.CommandEditor].MoveNext () System.Linq.Enumerable.Count[CommandEditor] (IEnumerable1 source)
Fungus.BlockInspectorEditor.DrawCommandUI (Fungus.Flowchart flowchart, Fungus.Command inspectCommand) (at Assets/Fungus/Flowchart/Editor/BlockInspector.cs:139)
Fungus.BlockInspectorEditor.OnInspectorGUI () (at Assets/Fungus/Flowchart/Editor/BlockInspector.cs:118)
UnityEditor.InspectorWindow.DrawEditor (UnityEditor.Editor editor, Int32 editorIndex, Boolean forceDirty, System.Boolean& showImportedObjectBarNext, UnityEngine.Rect& importedObjectBarRect, Boolean eyeDropperDirty) (at C:/buildslave/unity/build/Editor/Mono/Inspector/InspectorWindow.cs:1162)
UnityEditor.DockArea:OnGUI()

I wasn't able to reproduce this error, but I think I see where the null reference is happening so I added a check to avoid that.
It's generally a bad idea to have classes with the same name in a project anyway!


perf: factor out replacement/termination waits from deprovisioning

Fixes #N/A
Description
This adds in an orchestration queue that commands will be added to. This doesn't change any of the core logic but will let Karpenter compute commands while it waits for a command's replacements to be initialized, speeding up Karpenter.
How was this change tested?

make presubmit
applying to my local cluster.

Scale Tests

Testing briefly with KwoK, I was able to do a 200 node, 3000 pod test. I tested how long it took for all the nodes to be expired, and fully refreshed (using two provisioners to ensure each node was only expired once).

With the change: 17:44:13 -> 17:48:57 (~4m44s)
Without the change: 18:30:44 -> 18:50:24 (~19m40s)

This shows the time taking 76% amount of time, or being 415% quicker.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Wanted to follow up on this - it looks like this PR has been marked stale. I was linked to this PR from another issue I posted https://github.com/aws/karpenter/issues/4809 . Is this still an active line of work? Happy to help explain our use case (please see the linked ticket I shared).

Hey @thjwhite, sorry for the delay in response, this was blocked due to some other concerns on our NoSchedule Taint, and the v1beta1 migration. I'm working on this at the moment since it's no longer blocked.

Hey @thjwhite, sorry for the delay in response, this was blocked due to some other concerns on our NoSchedule Taint, and the v1beta1 migration. I'm working on this at the moment since it's no longer blocked.

Thanks for keeping the thread updated!

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
We've detected an issue with your CI configuration that might affect the accuracy of this pull request's coverage report.
To ensure accuracy in future PRs, please see these guidelines.
A quick fix for this PR: rebase it; your next report should be accurate.

238 of 296 (80.41%)  changed or added relevant lines in 15 files are covered.
23 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.001%) to 79.558%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/controllers/disruption/singlenodeconsolidation.go
3
4
75.0%

pkg/controllers/disruption/types.go
3
5
60.0%

pkg/controllers/state/statenode.go
26
33
78.79%

pkg/controllers/disruption/controller.go
23
31
74.19%

pkg/test/expectations/expectations.go
20
28
71.43%

pkg/controllers/disruption/orchestration/queue.go
140
172
81.4%

Files with Coverage Reduction
New Missed Lines
%

pkg/controllers/provisioning/scheduling/nodeclaim.go
2
88.17%

pkg/controllers/disruption/controller.go
7
74.29%

pkg/apis/v1beta1/nodeclaim_validation.go
14
91.41%

Totals

Change from base Build<PHONE_NUMBER>:
-0.001%

Covered Lines:
8356

Relevant Lines:
10503

💛  - Coveralls


Remove unused function from neo4j.py

I couldn't find get_model being used anywhere.

we do need to maintain more things at the same time

And this results in unmaintained code like the one this PR removes.
If I understand what get_model does, it creates an instance model from a neo4j instance. I think this is clearly out of scope for the mal-toolbox, don't you think?

we do need to maintain more things at the same time

And this results in unmaintained code like the one this PR removes.
If I understand what get_model does, it creates an instance model from a neo4j instance. I think this is clearly out of scope for the mal-toolbox, don't you think?

This was not something that was left over from some early iteration, it was something that Giuseppe specifically requested at the time. It was out of scope when it was introduced, the question if it's needed.

It's your call. My input is that the potential of seeing specication.py removed is great news. If you don't feel comfortable removing the securicad module, perhaps the relevant code from specification.py that is used only in securicad.py could go in there and specification.py is removed?


Add Windows CPU/GPU CMake support

environment:

w64devkit-1.21.0: provide make tools, see details in https://github.com/ggerganov/llama.cpp/tree/master-ff966e7?tab=readme-ov-file#build
use:
Run w64devkit.exe
Use the cd command to reach the PowerInfer folder
make

Thanks @bobozi-cmd for your contribution! Would you mind delete useless code instead of commenting them out? That would give us a cleaner codebase.
Despite that, LGTM! Will be tested and merged soon.

Windows GPU Make Method
Use:

make LLAMA_CUBLAS=1 to build GPU version PowerInfer with w64devkit.exe
Note:
If encounter error like this, check your CUDA_PATH whether has space, ensure this then make clean and remake

cuda12.1 windows won't compile
cc  -I. -Icommon -D_XOPEN_SOURCE=600 -DNDEBUG  -std=c11   -fPIC -O3 -Wall -Wextra -Wpedantic -Wcast-qual -Wno-unused-function -Wshadow -Wstrict-prototypes -Wpointer-arith -Wmissing-prototypes -Werror=implicit-int -Werror=implicit-function-declaration -Wdouble-promotion -march=native -mtune=native -Xassembler -muse-unaligned-vector-move    -c ggml.c -o ggml.o ggml.c:48:23: error: conflicting type qualifiers for 'atomic_int'    48 | typedef volatile LONG atomic_int;       |                       ^~~~~~~~~~ In file included from ggml.h:216,                  from ggml-impl.h:3,                  from ggml.c:4: E:/Langchain-Chatchat/w64devkit/lib/gcc/x86_64-w64-mingw32/13.2.0/include/stdatomic.h:46:21: note: previous declaration of 'atomic_int' with type 'atomic_int' {aka '_Atomic int'}    46 | typedef _Atomic int atomic_int;       |                     ^~~~~~~~~~ ggml.c:49:20: error: conflicting type qualifiers for 'atomic_bool'    49 | typedef atomic_int atomic_bool;       |                    ^~~~~~~~~~~ E:/Langchain-Chatchat/w64devkit/lib/gcc/x86_64-w64-mingw32/13.2.0/include/stdatomic.h:40:23: note: previous declaration of 'atomic_bool' with type 'atomic_bool' {aka '_Atomic _Bool'}    40 | typedef _Atomic _Bool atomic_bool;       |                       ^~~~~~~~~~~ ggml.c:51:13: error: expected identifier or '(' before '__extension__'    51 | static void atomic_store(atomic_int * ptr, LONG val) {       |             ^~~~~~~~~~~~ ggml.c:51:13: error: expected identifier or '(' before ')' token    51 | static void atomic_store(atomic_int * ptr, LONG val) {       |             ^~~~~~~~~~~~ ggml.c:54:13: error: expected identifier or '(' before '__extension__'    54 | static LONG atomic_load(atomic_int * ptr) {       |             ^~~~~~~~~~~ ggml.c:54:13: error: expected identifier or '(' before ')' token    54 | static LONG atomic_load(atomic_int * ptr) {       |             ^~~~~~~~~~~ ggml.c:57:13: error: expected declaration specifiers or '...' before '(' token    57 | static LONG atomic_fetch_add(atomic_int * ptr, LONG inc) {       |             ^~~~~~~~~~~~~~~~ ggml.c:57:13: error: expected declaration specifiers or '...' before '(' token    57 | static LONG atomic_fetch_add(atomic_int * ptr, LONG inc) {       |             ^~~~~~~~~~~~~~~~ ggml.c:57:13: error: expected declaration specifiers or '...' before numeric constant    57 | static LONG atomic_fetch_add(atomic_int * ptr, LONG inc) {       |             ^~~~~~~~~~~~~~~~ ggml.c:60:13: error: expected declaration specifiers or '...' before '(' token    60 | static LONG atomic_fetch_sub(atomic_int * ptr, LONG dec) {       |             ^~~~~~~~~~~~~~~~ ggml.c:60:13: error: expected declaration specifiers or '...' before '(' token    60 | static LONG atomic_fetch_sub(atomic_int * ptr, LONG dec) {       |             ^~~~~~~~~~~~~~~~ ggml.c:60:13: error: expected declaration specifiers or '...' before numeric constant    60 | static LONG atomic_fetch_sub(atomic_int * ptr, LONG dec) {       |             ^~~~~~~~~~~~~~~~ ggml.c: In function 'ggml_graph_compute_thread': ggml.c:16993:30: warning: initialization of '_Atomic atomic_int *' {aka '_Atomic int *'} from incompatible pointer type 'volatile atomic_int *' {aka 'volatile long int *'} [-Wincompatible-pointer-types] 16993 |                 /*.aic   =*/ &state->shared->aic,       |                              ^ ggml.c:16993:30: note: (near initialization for 'params.aic') ggml.c:17077:26: warning: initialization of '_Atomic atomic_int *' {aka '_Atomic int *'} from incompatible pointer type 'volatile atomic_int *' {aka 'volatile long int *'} [-Wincompatible-pointer-types] 17077 |             /*.aic   =*/ &state->shared->aic,       |                          ^ ggml.c:17077:26: note: (near initialization for 'params.aic') ggml.c: In function 'ggml_graph_compute_thread_hybrid': ggml.c:17183:30: warning: initialization of '_Atomic atomic_int *' {aka '_Atomic int *'} from incompatible pointer type 'volatile atomic_int *' {aka 'volatile long int *'} [-Wincompatible-pointer-types] 17183 |                 /*.aic   =*/ &state->shared->aic,       |                              ^ ggml.c:17183:30: note: (near initialization for 'params.aic') ggml.c:17284:26: warning: initialization of '_Atomic atomic_int *' {aka '_Atomic int *'} from incompatible pointer type 'volatile atomic_int *' {aka 'volatile long int *'} [-Wincompatible-pointer-types] 17284 |             /*.aic   =*/ &state->shared->aic,       |                          ^ ggml.c:17284:26: note: (near initialization for 'params.aic') make: *** [Makefile:533: ggml.o] Error 1

Core i3 12100F, 16 GB , Nvidia RTX 3060 12GB
Windows 11, Python 3.11, Visual Studio 2022, CUDA 12.1
git clone https://github.com/bobozi-cmd/PowerInfer
cd PowerInfer
pip install -r requirements.txt
mkdir build
cd build
cmake .. -DLLAMA_CUBLAS=ON
cmake --build . --config Release

C:\Users\Windows\AI\powerinfer.exe --vram-budget 12 -t 7 -m C:\Users\Windows\AI\llama-7b-relu.powerinfer.gguf --repeat_penalty 1 --no-penalize-nl --color --temp 0 --top-k 50 --top-p 1 -c 2048 -n 256 --seed 1 -p "Once upon the time"

llama_print_timings:        load time =    8458.75 ms
llama_print_timings:      sample time =      14.00 ms /   179 runs   (    0.08 ms per token, 12789.37 tokens per second)
llama_print_timings: prompt eval time =   13564.37 ms /     5 tokens ( 2712.87 ms per token,     0.37 tokens per second)
llama_print_timings:        eval time =   36187.15 ms /   178 runs   (  203.30 ms per token,     4.92 tokens per second)
llama_print_timings:       total time =   49795.77 ms

It works but it's very slow. I'll convert and quantize ReluLLaMA-13B to gguf fp16 to compare offloading on powerfinfer and if it is faster than llama.cpp.

There are many questions on windows and current test data may not reliable , we are trying to fix them, please wait for us, thank you.

After discussion with @bobozi-cmd, we will continue the work on #114 and close this PR.

Hello,
Thanks for your efforts.
I have been trying to run on windows, through w64devkit, and while it worked and offloaded it GPU, it's very slow.
I used the llama-7b model. It takes more than a few seconds to generate one token.
My device: RTX 2060.


Coding of Dictionary<enum,codable> is broken

Describe the bug
Encoding and decoding of Dictionaries that use an enum for the key and have a codable object as the value is broken. Container coding is not reset when encoding the value.

fixed now we use property wrappers


Allow ignoring nameSuffix for PVC

Details
Helm chart name:
common
Describe the solution you'd like:
allow having no suffix by giving a negate option
Anything else you would like to add:
N/A
Additional Information:
Relevant code:
https://github.com/k8s-at-home/library-charts/blob/a06271207b537e8a5dd4e93f5549905cabaefad3/charts/stable/common/templates/_pvc.tpl#L17-L19
changing L17 to:
{{- if or (not $persistenceValues.nameSuffix) (eq $persistenceValues.nameSuffix "-") }}

should resolve the issue

Added this in the upcoming version 👍🏻


color schemes

Adds support for named color schemes as defined by Vega and d3-scale-chromatic.

Schemes with 20 color swatches are not yet supported because they aren't supplied by d3-scale-chromatic, so color.scheme: "category10" will work but color.scheme: "category20" will throw an error.

In the case of a misconfigured specification which simultaneously calls for both a named color scheme and a color blindness palette, the more accessible colors will be preferred.


feat: mergeable indexes

Summary of changes

Changes introduced in this pull request:

Reference issue to close (if applicable)

Closes
Other information and links

Change checklist

[ ] I have performed a self-review of my own code,
[ ] I have made corresponding changes to the documentation,
[ ] I have added tests that prove my fix is effective or that my feature works (if possible),
[ ] I have made sure the CHANGELOG is up-to-date. All user-facing changes should be reflected in this document.

I'd hate to lose the code but it just isn't a priority to get it working.

David in Slack

No bandwidth for this.


Possible bug in update

In my test harness update_lbaas_healthmonitor returns a request-format-error, and permanently shifts the loadbalancer into a UPDATE-PENDING state.

Fixed!  Thanks @richbrowne !


[Feature Request]: As a Playground user, I can open and run an example that uses emulated data source

What would you like to happen?
As a Playground user, I can open and run an example that uses emulated data source
Issue Priority
Priority: 3
Issue Component
Component: beam-playground

Tracked in https://github.com/apache/beam/issues/23850


Scaffold a subcrate for ion-hash

Not sure we want this to live here forever, but this should let us
iterate in lock step with the in-development ion-rs crate.
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Do you want to call this ion-hash-rust or ion-hash-rs or just ion-hash? I chose the latter.

Do you want to call this ion-hash-rust or ion-hash-rs or just ion-hash? I chose the latter.

I prefer ion-hash, the only reason why we have ion-rs is because of crates.io name clash.


fix(ant): update write handler types removes evolve handler name

:tada: This PR is included in version 2.5.3-alpha.2 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.5.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add CBMC harness for QueueCreateMutexStatic

Description

This PR adds a CBMC harness for QueueCreateMutexStatic, QueueGenericCreateStatic and QueueCreateCountingSemaphoreStatic.
See the added README.mds for made assumptions.
Depends on #774 and #697
Checklist:

[x] I have tested my changes. No regression in existing tests.
[ ] My code is Linted.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

The last force push adds configuration checking for configSUPPORT_DYNAMIC_ALLOCATION set to 0 and 1 for the QueueGenericCreateStatic harness.

Closed in favor of https://github.com/aws/amazon-freertos/pull/1324.


Stop requiring charset in Content-Type

Since spray always renders JSON to UTF-8 they made their constant require UTF-8. But we should not be so restrictive. When the charset is not specified, UTF-8 is assumed. See RFC 4627, section 3.

:+1:

:shipit:


life altering for testing

Description
A description of the PR, should include a decent explanation as to why this change was needed and a decent explanation as to what this change does
Issue
https://ucsc-cgl.atlassian.net/browse/DOCK-2007
Please make sure that you've checked the following before submitting your pull request. Thanks!

[ ] Check that your code compiles by running npm run build
[ ] If this is the first time you're submitting a PR or even if you just need a refresher, consider reviewing our style guide
[ ] Do not bypass Angular sanitization (bypassSecurityTrustHtml, etc.), or justify why you need to do so
[ ] If displaying markdown, use the markdown-wrapper component, which does extra sanitization
[ ] Do not use cookies, although this may change in the future
[ ] Run npm audit and ensure you are not introducing new vulnerabilities
[ ] Do due diligence on new 3rd party libraries, checking for CVEs
[ ] Don't allow user-uploaded images to be served from the Dockstore domain

for Monday: husky doing some extra formatting

Found more trailing spaces in the "Source Repositories" box on both the tool and container pages.

Found more trailing spaces in the links in the "Source Repositories" box on the tool and container pages.

That's what I thought too at first, then I noticed that the "pop-out" icon is part of the same hyperlink. So instead of having "link space same-link", I just left it alone.


Added StateOverrideSet parameter

Summary
Added StateOverrideSet parameter in SDK.
Todo's:

add test cases

More about StateOverrideSet:

https://www.libevm.com/2022/01/12/advance-geth-pt-2-stateoverrides/

Change Type

[ ] Bug Fix
[ ] Refactor
[x] New Feature
[ ] Breaking Change
[ ] Documentation Update
[ ] Performance Improvement
[ ] Other

Checklist

[x] My code follows this project's style guidelines
[x] I've reviewed my own code
[x] I've added comments for any hard-to-understand areas
[ ] I've updated the documentation if necessary
[x] My changes generate no new warnings
[ ] I've added tests that prove my fix is effective or my feature works
[ ] All unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published

Additional Information

resolve conflicts


Use something fancier rather than textarea

https://github.com/superRaytin/react-monaco-editor

actually not worth it.


How can I get a UIImage from GPUImage camera?

I know I can use the still camera's capturePhotoAsImageProcessedUpToFilter method, but it gives a shutter click sound and I still have some processing to do so I don't want it to sound yet.
I tried using a filter's imageFromCurrentFramebuffer method, but that is always turning nil.
_camera = [[GPUImageStillCamera alloc] initWithSessionPreset:AVCaptureSessionPresetHigh cameraPosition:AVCaptureDevicePositionBack];
_camera.outputImageOrientation = UIInterfaceOrientationLandscapeRight;
filter = [[GPUImageBrightnessFilter alloc] init];
filter.brightness = 0;

[_camera addTarget: filter];

[filter addTarget:_backgroundImageView];
[_camera startCameraCapture];
// processTimer is to periodically do processing on what's being shown on screen.
processTimer =[NSTimer timerWithTimeInterval:.25 target:self selector:@selector(processImage) userInfo:nil repeats:NO];
[[NSRunLoop mainRunLoop] addTimer:processTimer forMode:NSRunLoopCommonModes];

-(void) processImage {
    [processTimer invalidate];
    UIImage *testImage = [filter imageFromCurrentFramebuffer]; // always nil

    [_camera capturePhotoAsImageProcessedUpToFilter:filter withCompletionHandler:^(UIImage *processedImage, NSError *error) {

         // additional processing here ... don't want shutter sound yet.

    }];
}

The same problem also plagued me for a long time, I also want to ask how to do? When the camera when I need high pixel, but I want to get 10 low-resolution images(240x320) per second, then you need to mute. What should I do?


Disable / Change F11 when conflicting

How can I disable or change the full screen shortcut (F11)? It conflicts with firefox on my system.

@BatmansGehilfe Did you mean to say that F11 of Todoist is registered as a global shortcut and is conflicting with Firefox? If yes, did you happen to notice that with other apps too? For instance, with Todoist open (but NOT focused), try F11'ing chrome maybe?

hey @BatmansGehilfe, thanks for letting us know about it.
I was just able to reproduce it. It happens because our F11 is set globally. So even if you are in Firefox or any other app, F11 will full screen the todoist instance anyway.
As a workaround you can edit your $XDG_CONFIG_HOME/.todoist-linux.json and line "toggle-fullscreen": "F11" in particular. Just change F11 to something else.
If you have no such line in your config file then you need to add it. But make sure JSON is correct (every line except last one should end with comma).
@cyfrost thanks for jump in!

thanks @cyfrost and @KryDos ! That was both extremely helpful and quick. @KryDos hint actually worked - there was no such line present in my file.

🎉 I'm glad this issue is resolved for you.
I'll keep this one opened for awhile just to make sure Globally bound F11 is changed to locally bound.

I actually had the same issue. Would it be possible to just opt out of certain shortcuts? Removing the line from the config just results in falling back to the default. I have mapped fullscreen to some obscure key combination because I don't use it that much, but it'd be nice to not pollute global shortcuts if possible.

@karthikiyengar yeah, unfortunately removing the line from config file just falls back to defaults. Solution you came up with is the only possible currently. We'll make the change and new version of the app should not contain this issue.
Maybe we should just remove shortcut for full screen... I don't think it is a functionality that needs a shortcut.
I'll post here when new version is ready.

Maybe we should just remove shortcut for full screen... I don't think it is a functionality that needs a shortcut.

Just putting my feeling about this: I think so too, I've trouble remembering the last time I F11'ed Todoist, for all practical purposes, the Maximized view is quite sufficient for me.
Maybe you can get rid of F11 shortcut and add it if someone raises a feature request for it :)

hey guys,
Please take a look at Release 1.16 where this issue is fixed.
F11 isn't globally bound anymore. At the same time it does work inside the app.
I'm closing the issue. Let me know if you still see the bug.


Handle application errors more gracefully

In dev (FLASK_DEBUG=true), showing a traceback is good. If we are not in dev, we currently show a 500 internal server error page.
To do better than that, we should show something to the user that is useful for reporting the error ("who do I call?"), describes how to recover, and enables them to continue using the app.
We should set this up so all exceptions generated by requests are caught. Does Flask have a built-in method to intercept request exceptions?
Probably a medium-term thing?

https://flask.palletsprojects.com/en/2.3.x/errorhandling/

TODO: We need to figure out how to handle errors with HTMX. E.g. when you delete a node from the node library, it will fail if that node is used in an assessment. It won't tell you why, the button just does nothing. How can we get the server-side error message (e.g. "Can't delete because this node is associated with surveys X, Y, Z") back into the app for the user to see?


Chat adminlogs

Currently these are only on grafana and I imagine painful for admins to piece together events without it.
My first alogs pr be gentle.
:cl:

add: Admins can now also get chat logs in-game.

conflicts somehow


Evaluate usage of libnpx

Kudos to @zkat for suggesting we take a look at npx - a module for executing npm package binaries and installing any dependencies needed for them to work. Here's a demo of npx in action with yo:
https://twitter.com/maybekatz/status/883846850171641856
libnpx is a lib-ified version of npx that we could embed in yo, opening the door to $ yo <generator-name> installing and running <generator-name> automatically in a private scope the same way npx does without polluting globals.
Why is this potentially useful?
This effectively reduces the two steps of npm install -g yo generator-name followed by yo generator-name into yo generator-name - lowering the friction for how easy it would be to start off a new project.
The differences between merely stringing these steps into npm install -g yo generator-name && yo generator-name and npx support is:

No global conflicts
Easily pick different versions
Private scopes
Don't pollute global installs with things you'll only ever run once

npx is slated to land in npm sometime in the next few weeks.

I think this is a great idea (and I believe we've had such a discussion before). So it's great to see a library that would make building this functionality easy.
Integrating this with yo though would still require the user to first install yo; so we just skip the npm install generator-node step once yeoman is installed right?
Does anyone knows more about the private scope? I'm not clear what's the impact of this.

the gist of the "private scope" is that npx installs things using ~/.npm/_npx as a "global prefix", and then adds ~/.npm/_npx/bin to $PATH. That means installations work exactly like globals, except npx happens to be doing some $PATH magic to arrange it into place. npx also does a bit of juggling to make that (mostly) safe to do, make it relatively efficient, etc.
Note that integrating this with yo wouldn't require users to install yo, if they already have npx installed (which any users using<EMAIL_ADDRESS>will have, starting next week).
So, putting it all together, if yeoman integrates libnpx and a user has npx available in their system, as most npm users will, you can do:
$ npx yo node --opt1 --opt2
# npx installs yo, then yo installs generator-node
...scaffolding time!...

Or, if they're using the npx fallback:
$ yo@3 node

Which is I think about as short as you can get for any scaffolding ever tbh. ;) Note that this is something users would be able to do just by installing Node.js.

@zkat is there API/integration documentation for npx?

@SBoudrias the "API" is really just a fairly hacky/quick refactor of what was once a CLI-only app, so I could use it with npm itself. There's nothing specifically documented yet at the JS API level, but also what's currently there is all I need from it, so I'm hoping having other use-cases for it will help develop it a bit. Literally the only consumers of libnpx right now are npm and npx.

So, what's the progress on this. It would be a very nice to have. Are you still discussing it internally or do you wait for a PR?

@Telokis PR is welcomed :)

PR anyone?:)


Stop using java default executor pool for AsyncRunner

We should create our own executor pool for AsyncRunner rather than using  CompletableFuture.delayedExecutor so that we control how many threads are available etc.
Add metrics to track how many threads are in use and how long the queue of tasks is.

Done.


Constraint create from YAML stuck saving

Go to the Dashboard in the local cluster
Apps -> Charts -> rancher-gatekeeper Install.
Under OPA Gatekeeper -> Constraints -> Create from YAML
Enter name and YAML.
Ex:
apiVersion: constraints.gatekeeper.sh/v1beta1
kind: K8sRequiredLabels
metadata:
  name: ns-must-have-gk
spec:
  match:
    kinds:
      - apiGroups: [""]
        kinds: ["Namespace"]
  parameters:
    labels: ["gatekeeper"]

Result:
Creation is stuck saving

Rancher server rancher\rancher:master-head version 9b6984d5f master-9b6984d5fa33c65ebcc3dee04bb918300451cf37-head

On inspect:


Refactor API modules

This pull request builds on my two earlier PRs: #2002 which moves contrib.wagtailapi to wagtail.api.v1 and #1974 which adds the new wagtail.api.v2 module. There's a lot of shared code between these two modules so this PR has been created to move some common parts to a new wagtail.api.shared module.

Moved some of this into a new PR #2002.


Lighthouse test of the website

Summary:
Conduct Lighthouse testing to assess the performance scores of both the index page and an additional page, focusing on various aspects such as Performance, Accessibility, Best Practices, and SEO.
Acceptance Criteria:

Performance Score:

Score should be above 90
Evaluate the Performance score using Lighthouse in Chrome Developer Tools.
Ensure comprehensive assessment, covering aspects such as loading speed and resource optimization.

Accessibility Score:

Score should be above 90
Assess the Accessibility score using Lighthouse in Chrome Developer Tools.
Verify that the website adheres to accessibility best practices, ensuring a positive user experience for all.

Best Practice Score:

Score should be above 90
Check the Best Practice score using Lighthouse in Chrome Developer Tools.
Examine adherence to best practices in web development, focusing on security, performance, and overall robustness.

SEO Score:

Score should be above 90
Review the SEO score using Lighthouse in Chrome Developer Tools.
Confirm that the website is optimized for search engine visibility, addressing key SEO metrics.

Developers are tasked with conducting a comprehensive Lighthouse test on both the index page and an additional page, addressing and improving scores in Performance, Accessibility, Best Practices, and SEO as necessary.

Light house test results: