Difficulty Defining CPU and GPU Machine Types in Kedro-Vertex (vertexai.yml)

Problem:
I'm encountering difficulty in defining the CPU and GPU machine types with respect to nodes and pipelines in vertexai.yml within the Kedro-Vertex framework.
Expected Behavior:
I expect to be able to specify the CPU and GPU machine types for nodes and pipelines in vertex.yml to effectively utilize CPU and GPU resources as needed.
Current Behavior:
I've searched through the documentation and codebase but haven't found clear instructions on how to achieve this. This makes it challenging to optimize the resource utilization for my specific workflow.
Steps to Reproduce:

Create a Kedro-Vertex project.
Attempt to define CPU and GPU types for nodes and pipelines in vertexai.yml.
Encounter difficulties or confusion in the process.

Additional Information:

I've reviewed the official documentation, but the guidance on this specific aspect seems to be lacking.
I've also searched for relevant examples or discussions on forums and GitHub issues but haven't found any direct solutions.

Environment:

Kedro version: 0.18.14
Kedro-Vertex version: 0.9.1
Python version: 3.8.18
Operating System: Mac

Suggested Solution:
It would be helpful to provide more detailed documentation or examples on how to define CPU and GPU machine types for nodes and pipelines in vertex.yml. Alternatively, if this feature is not yet supported, it would be great to know the current status and any workarounds.
Related links
https://github.com/getindata/kedro-vertexai/blob/develop/kedro_vertexai/config.py
https://kedro-vertexai.readthedocs.io/en/0.9.1/source/02_installation/02_configuration.html
Notes:
vertexai.yml is generated by command kedro vertexai init
This issue aims to improve resource management and clarity within Kedro-Vertex, making it easier for users to define CPU and GPU machine types for their nodes and pipelines. Your attention to this matter is greatly appreciated.

Hi @7pandeys, thanks for raising the issue.
The Resources configuration section on the page you've linked has exactly the information about using GPUs. Initial configuration generated by kedro vertexai init also creates the vertexai.yml which contains an example of configuration for nodes with GPUs on Vertex AI.
We're open to improvements on that part - what do you propose?

Config generated by kedro vertexai init
https://github.com/getindata/kedro-vertexai/blob/0bcb35e6dbe4eb2b26c1499065ec68a077e8bb9f/kedro_vertexai/config.py#L57-L78

@marrrcin  thanks for response.
Is there a specific parameter or syntax that allows us to specify the machine type or CPU type in the vertexai.yml configuration? If not, what would be the recommended approach to achieve this?
Related links
https://cloud.google.com/compute/docs/cpu-platforms
https://cloud.google.com/compute/docs/machine-resource

@marrrcin thanks for response.
Is there a specific parameter or syntax that allows us to specify the machine type or CPU type in the vertexai.yml configuration? If not, what would be the recommended approach to achieve this?
Related links
https://cloud.google.com/compute/docs/cpu-platforms
https://cloud.google.com/compute/docs/machine-resource

Follow this guide, our plugin is fully compatible with this approach: https://cloud.google.com/vertex-ai/docs/pipelines/machine-types

Follow this guide, our plugin is fully compatible with this approach: https://cloud.google.com/vertex-ai/docs/pipelines/machine-types

Is it possible to define machine types directly within Kedro-VertexAI without relying on KFP?
If not, are there plans or considerations for enabling this feature in future releases?
Are there recommended workarounds or best practices for specifying machine types when not using KFP?

I don't understand your questions. You can configure machine types as you want in vertexai.yml - the configuration in the plugin exposes the configuration available in native Vertex AI. That means that whatever you define in the vertexai.yml configuration file, it will be used in the plugin to set appropriate CPU/memory/GPU resources + node selectors on the Vertex AI side, you don't have to use KFP directly.
   resources:

     # For nodes that require more RAM you can increase the "memory"
     data_import_step:
       memory: 4Gi

     # Training nodes can utilize more than one CPU if the algoritm
     # supports it
     model_training:
       cpu: 8
       memory: 8Gi
       gpu: 1

     # Default settings for the nodes
     __default__:
       cpu: 1000m
       memory: 2048Mi

   node_selectors:
     model_training:
       cloud.google.com/gke-accelerator: NVIDIA_TESLA_T4

I suggest you try to configure our plugin first, then see whether it works for you and whether it matches your requirements on that part.


change ci configuration

Enable dependabot for github actions and reduce the frequency for pre-commit hook update PRs.

The upstream-dev CI will currently fail because xarray and flox (and possibly others) are incompatible with the most recent numpy version (and since that appears to be pretty unstable at the moment, they might stay like that for a while longer). As such, I will just merge this and keep an eye on the CI status.


generating public and private key

added an entry in the wiki to help explain
let me know if this helped :yum:


Adding pyrad part

Dear all,
Here is the PR with the content of our pyrad short course. It adds config files, presentations and example outputs.
I added a script to download the data from the S3 bucket that we will need to run before the course.
Thank you,
Daniel

One last question, can someone explain why the multitude of png images are necessary to have inside the repo?  As these are in the folder pyrad_output, maybe this slipped in by accident and can be removed before merge?

Hi @kmuehlbauer ,
Sorry for the pyrad_mch that I forgot to remove, I will fix this immediately.
For the pyrad_outputs, I thought I would provide the expected outputs if participants are not able to generate them themselves. But I agree it's a lot of files... :(. Would a tar.gz be ok for you ?

Yes, @wolfidan a tar.gz would be OK.
Please be aware, that I already added some changes to the PR ( docker tag etc)

Thanks all!


Move JUnit/Mockito dependencies to test scope.

Let's not impose JUnit and Mockito dependencies on everyone since they're only used in the test suite.

Thank you Matthias Friedrich for the contribution.


apply_montage

Adds a field to the apply_montage() function to allow imports of montages of different types, which might also need to implement small changes in metadata.
Also add functionality to add localized iEEG electrodes from montage files, in the surface space and using the SEEG coordinate frame. This seems to be the best way to import the types of data that I am working with into .fif format.

you'll need to add a test to avoid reducing the coverage of the package

Coverage decreased (-21.01%) to 65.07% when pulling d685697f43dd80cc3388e419c4386047d0e89605 on aestrivex:apply-ieeg-type-montage into c1c08ff9265b7db7e787e3ccbd6045869996ae9b on mne-tools:master.

Coverage decreased (-3.45%) to 82.63% when pulling d685697f43dd80cc3388e419c4386047d0e89605 on aestrivex:apply-ieeg-type-montage into c1c08ff9265b7db7e787e3ccbd6045869996ae9b on mne-tools:master.

rename_channels isn't a sufficient API for this purpose, because it requires the user to manually specify the names of all the channels to be changed. Instead there needs to be a way to automatically change the type (and preferably also the coord_frame attribute) of all the channels specified in the montage.
Would it be more consistent with the existing API to create a different function to do this similar to rename_channels?

We could extend the rename_channels API to allow for type-wise renaming, or some pattern matching.

On 23 Feb 2015, at 00:30, Roan LaPlante<EMAIL_ADDRESS>wrote:
rename_channels isn't a sufficient API for this purpose, because it requires the user to manually specify the names of all the channels to be changed. Instead there needs to be a way to automatically change the type (and preferably also the coord_frame attribute) of all the channels specified in the montage.
Would it be more consistent with the existing API to create a different function to do this similar to rename_channels?
—
Reply to this email directly or view it on GitHub.

have a look at:
https://github.com/mne-tools/mne-python/pull/1825
it can be done in 1 line with the fix

Thanks, it looks like it will work for my use case.
I'll close this PR.


Be able to get config from a URL

Currently you have to provide a filepath to a config file.
This is fine for local development, but when you're trying to distribute your config to another team to run a CDC it becomes painful from a CI perspective.
It would be easier if the consumer could serve their config over HTTP and then the producer can just point mockingjay at a URL to run their consumer's CDCs.

https://github.com/quii/mockingjay-server/releases/tag/1.11.0


[BUG] Time Period in Dev Tools is showing as time input

Describe the bug
Time Period in Dev Tools > Services is showing as time input instead of a duration. It works OK but is confusing that there is an AM/PM field
To Reproduce
In Dev Tools > Services, select Hive: Boost Heating On
Expected behaviour
Show a time duration instead of a time
Screenshots

Desktop (please complete the following information):

OS: Windows 11
Browser Chrome

Additional context
Home Assistant 2022.7.6
Hive 2022.7.3

I’ll have a look at what home assistant offer but I am limited to what options they give.

OK, it doesn't affect anything just looks weird. If you switch to YAML mode it is ok


buildcache: Add version v0.28.4

Closes #11627

[x] I have read the Contributing Guide.

Issues should be fixed (unless I messed up 😄 ). Thank you!

/verify


Split Pipfile parsing to independent library

Reference: #952.
Parsing à Pipfile using pipenv adds many dependencies (ex: flake8.cli).
Is it possible to split the parsing part from the pipenv CLI into a different package?
I would like to contribute to at least ReadTheDocs and PBR to help them support Pipfile, and that would help a lot if everyone use the same parser.

This seems like a good idea, although technically Pipfile parsing is handled by Toml via the Pipfile spec (see pypa/pipfile)

@Stibbons @techalchemy That repo will eventually contain a parser for Pipfiles once the pipfile spec settles a little.  Probably extract it from pipenv.


Default calendar app

Describe the bug
It always shows me ''Horloge'' (=Clock) in default calendar app, while I set Google Calendar.
NB : When I click on the widget, the correct default calendar app (Google Calendar) opens.
Expected behavior
Display the correct default calendar app.
Screenshots

Smartphone

Device: Xiaomi Redmi Note 7
OS Version: Android 10
App Version: v2.0.14(106)

Fixed, thank you for the feedback.


Duck Highlight for Bird Slayer Task

Ducks (SW of champions guild) dont highlight under the Slayer plugin, they count as a 'birds' task from turael

Added in #14224


[REVIEW]

GitHub Profile Link
https://github.com/VishwaS-22

Some suggestions from my point of view -

add the description of 3-4 lines for your pinned repositories
pin at least 4 repositories


Driver type does not show as Deprecated in API docs

NewDriver shows as deprecated, while Driver does not.

Hmmm, that is strange, the deprecated comment is there: https://github.com/neo4j/neo4j-go-driver/blob/0341d94da97a3f3ce2744c26e90c90a095c75ce3/neo4j/driver.go#L30.
Same as NewDriver: https://github.com/neo4j/neo4j-go-driver/blob/0341d94da97a3f3ce2744c26e90c90a095c75ce3/neo4j/driver.go#L64 🤔

Turns out there were a few other occurrences of this problem 😓


Replace references to module load dea/20180515 with new version of dea

Concatenating arrays used to break on module load dea. We temporarily directed people to load dea/20180515, but now we can revert this back to module load dea

This has been fixed for all notebooks on develop


fixShowTablesOrShowDatabasesOnlyReturnInCorrectResult

Fixed issues:

When there are multiple databases under the same account, SHOW DATABASES IN cosmosCatalog only return one database
When there are multiple containers under the same database, SHOW TABLES FROM cosmosCatalog.$databaseName only return one container

Notes: spark 3.1, 3.2 does not support SHOW DATABASES IN cosmosCatalog, so the tests to validate all databases can be returned is only added in spark 3.3, 3.4 and 3.5

/azp run java - cosmos - tests

/azp run java - cosmos - tests

/azp run java - cosmos - spark

/check-enforcer override


Parse Unicode Strings

Codecov Report

Merging #7 into master will increase coverage by 2.67%.
The diff coverage is 88.81%.

@@            Coverage Diff             @@
##           master       #7      +/-   ##
==========================================
+ Coverage   70.16%   72.84%   +2.67%
==========================================
  Files          22       23       +1
  Lines        1790     2073     +283
==========================================
+ Hits         1256     1510     +254
- Misses        534      563      +29

Impacted Files
Coverage Δ

Sources/PureSwiftJSONParsing/JSONValue.swift
91.34% <ø> (ø)
:arrow_up:

...ingTests/Learning/FondationJSONSerialization.swift
72.22% <72.22%> (ø)

Tests/JSONParsingTests/StringParserTests.swift
89.84% <88.59%> (-10.16%)
:arrow_down:

Sources/PureSwiftJSONParsing/DocumentReader.swift
91.04% <90.66%> (+3.32%)
:arrow_up:

Tests/JSONParsingTests/BoolParserTests.swift
96.72% <92.3%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


feat(aws): add web identity provider

Add web identity credential provider to chain (needed for k8s integration)

With HTTPS support this now works with K8S


Add release version for Linux aarch64

Fixes #19

With these changes, I was able to build a release on my fork:
https://github.com/electrum/wasi-vfs/releases/tag/v0.5.3-1
https://github.com/electrum/wasi-vfs/actions/runs/12131640916

Thanks for the quick merge! I can confirm that the latest release works for me when building an ARM64 Docker image.


Looks like promising library, but unfortunatelly does not work for me

I had no success using it on a mobile device:
android - firefox : probably reports some error, but can't see it as its difficult to debug on android
android - chrome: looks like it works but only on https. currently I don't have access to a secure version of our website so have no chance to test it.
what is your recommendation, whats the best way to test this ?

This library uses the WebRTC APIs to interact with the camera. Chrome requires a secure origin (HTTPS or localhost) when using WebRTC APIs.
If you want to avoid HTTPS for testing, you have to either use localhost domain, or close Chrome and relaunch with a special flag, e.g. on macOS open -a "Google Chrome" --args --unsafely-treat-insecure-origin-as-secure="http://mydomain.com:8080" "http://mydomain.com:8080". In production, HTTPS is required.
For Firefox mobile, what are you seeing? Does it request camera access? Does a camera preview appear?

Thanks for quick reply.
I have enabled that flag and chrome://version show its there

I have connected android chrome in remote debugging mode.

But STILL get this error :(
For Firefox for android , it looks it works

Closing due to inactivity. Let me know if I can help further.


its not actually updating to latest stable?

i've had this problem occassionally where, after trying to update to the latest stable, and apparently being successful, its actually not updating at all after the reboot.
this is on an eu o3ds.
sometimes it works after a few tries, but now it hasn't worked in 10 attempts

It is a server side issue., the latest release build on the server is not the most recent one.


⚠ Bofrost.fr has degraded performance

In b777bf8, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 979 ms

Resolved: Bofrost.fr performance has improved in 9dcb696 after 10 minutes.


Add badges to README.md

I used badges a lot in PostCSS. But didn't find good use cases.
Why you want it?

Why not? If all green then all right 👌  UX best practices 😄
The use of badges is probably already a de facto standard. When I first read README, I immediately noticed their absence.
IMHO, they allow you to visually evaluate the repository (code is being built, dependencies are up to date, Code Climate gives some kind of integral rating of code quality and coverage info and sometimes helps with code refactoring, etc.). In general, there is some benefit. 😄

I agree that it is de facto standard, but I think it is a bad standard.
People just don’t use it. Or use it very rare.
So in my opinion it is just trend for trend.


Sound jitter, distortion, and delay

This fixes the above for me.
This should work fine because

it's called in its own thread so it won't block.
the sound files should be small and won't bloat memory

It could also be further improved upon by creating a map of file paths to audio data to save time on re reading and opening an audio file.
In addition, if the symphony theme uses a consistent format for all it's audio files then only one stream needs to be created. That comes with the adding of locks with little gain, though.

closes #1


Improve workshop by reusing Jason's workshop content

Brainstorming (pending to have a workshop with Jason)

[ ] K8s Runtime

[ ] Security Playground attack scenario

[x] Deploy Security Playground workload
[ ] Bootstrap scripts.sh  to trigger attack scenarios

[ ] Read files /etc/shadow/ ...
[ ] Write /bin and chmod +x ...
[ ] Install nmap ... etc ... Run cryptominer
[ ] Explain sysdig rules/events

[ ] Explain drift detection
[ ] Explain outbound crypto miner
[ ] Malicious binary detected
[ ] Analyze process tree

[ ] K8s network

[ ] Enforce policies

[x] Vuln Mgt

[ ] CLI Scan demo
[x] Runtime Insights / Risk Spotlight permanent infra + scenario

[ ] Zones-Teams (Still in progress - Jason)

[ ] Configure sysdig zone-team sample and show how it works

[ ] KSPM

[ ] K8s posture & firewall

Notes

Security playground app is the same from sysdiglabs and demoenv
https://github.com/sysdiglabs/security-playground

...

1st iteration: Vuln mgt runtime insights


place .chips in $(document).ready in order for it to work?

Description
I'm using trying to use chips feature in my Angular 1.X app, and the .chip class works as expected but not the .chips, well not until I place it in a $( document ).ready(function({} inside my controller, where I'm instantiating the chips. There should be a better way to handle this; and if there is please let me know.
I'm using the version 0.98.0 materialize.

Well you can probably also use the angular.element(document).ready() but yes this is required

Correct. I normally use angular.element rather than $ in my angular apps. Just though I this i was a bit cumbersome to get it working. Thanks for the prompt response though. @Dogfalo


Build UI for claiming unbonding tokens

Initial UI for claiming unbonding tokens.
https://github.com/penumbra-zone/web/assets/1121544/ef217b93-f8d4-4606-9f01-311835898671
🚨 This will automatically attempt to claim all unbonding tokens that the current address holds, even if some of them are not yet eligible for claiming. In that case, an error will show up, saying that we're not yet in the right epoch for claiming unbonding tokens. At the moment, there's no RPC method to detect which unbonding tokens are eligible for claiming and which aren't . When there is, we can automatically select just the eligible tokens and claim those. Until then, we'll just cross our fingers :D
In this PR

Create an undelegateClaim action in the Staking slice, as well as in the WASM planner.
Create a client for the SCT service (to get the current epoch).
Implement the ValidatorPenalty method of StakingService, which is required for an undelegation claim.
Fix a bug with how proving keys were being loaded.
Move staking slice into its own directory.

Closes #655

@grod:

At the moment, there's no RPC method to detect which unbonding tokens are eligible for claiming and which aren't

Can you create an issue for this and add it to the staking tracking issue?

I believe @erwanor was already working on this... @erwanor , is there a ticket for this RPC method?

@grod220 Nevermind — just created the ticket after discussing with @erwanor . https://github.com/penumbra-zone/penumbra/issues/4006


Update dynamodb to 2.15.29

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

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

labels: library-update, semver-patch

Wow, that worked like a charm!
Now we just need to get the Scala Steward action right.


Add parameter for setting port to custom acl type

@solarkennedy,
I need to set the port for consul, but it's hard coded into the type provider. Added a parameter to the type and set the default to 8500.
Thanks

Thanks!


x/pkgsite: present the package paths in the vulnerability info shown in the versions tab

https://pkg.go.dev/golang.org/x/text?tab=versions
A module may contain multiple packages. When browsing the module's version history,
the versions tab provides vulnerability info. However, it's hard to figure out whether
a vulnerability affects the entire module, or only a certain package.
For example, GO-2022-1059 affects golang.org/x/text/language, but visible from
pkg.go.dev/golang.org/x/text?tab=versions and it's not obvious that this vulnerability
affects only golang.org/x/text/language.

OTOH, if other packages in the module "transitively" depend on golang.org/x/text/language,
I wonder if they are included in the osv entry.

Hmm, I'm not sure that this matches the scope of the versions tab. Listing packages may be distracting and/or misleading.
Aside: it would be nice if the vulnerability pages defined what it means for a package or symbol to be affected.

https://pkg.go.dev/golang.org/x/text?tab=versions
A module may contain multiple packages. When browsing the module's version history, the versions tab provides vulnerability info. However, it's hard to figure out whether a vulnerability affects the entire module, or only a certain package.
For example, GO-2022-1059 affects golang.org/x/text/language, but visible from pkg.go.dev/golang.org/x/text?tab=versions and it's not obvious that this vulnerability affects only golang.org/x/text/language.
OTOH, if other packages in the module "transitively" depend on golang.org/x/text/language, I wonder if they are included in the osv entry.
https://github.com/golang/go/issues/60579#issue-1738511488


Raven throws ReferenceError: window is not defined

I'm using raven-js in parse cloud code:
import Raven from 'raven-js';

// Initialize Sentry
Raven.
  config(ENV.SENTRY.DSN)
  .install();

Got following error on raven-js 3.3.0
ReferenceError: window is not defined
/**
 * Enforces a single instance of the Raven client, and the
 * main entry point for Raven. If you are a consumer of the
 * Raven library, you SHOULD load this file (vs raven.js).
 **/

'use strict';

var RavenConstructor = require('./raven');

var _Raven = window.Raven;

var Raven = new RavenConstructor();

Is parse cloud an actual browser runtime or is it node?

@dcramer Ah It's node. Thanks for pointing that out.

@yingliangzhang np -- raven-node should work, but if it doesnt feel free to open a ticket there

It's not quite exactly node according to this:

Most but not all Cloud Code can be directly ported to node.js. Parse Cloud Code is based on the V8 JavaScript engine, but it does not run node.js. In particular, Cloud Code environments are loaded and unloaded individually for each request, while node.js services typically serve multiple requests at a time.

but nonetheless window definitely won't be a thing, so raven-js won't work. You could try raven-node, but I doubt that will work; Parse cloud code has its own methods for sending requests according to their docs and this blog post. They do note that "You can use your favorite npm module to make HTTP requests, such as request", but I'm not sure what that means regarding the node-native http/https modules.
I haven't used Parse cloud code before, so for all I know it'll work with raven-node out of the box, but I'm guessing that this will at least require some trickery to make the node http/https modules available to raven-node, and may need a custom client using Parse's http API.

Thanks @LewisJEllis for explaining. I'm quite new to Parse Cloud as well and I've never used raven. I'll try raven-node and see how it goes.


Getting error during initial load of vscode for JS files

Getting below error notification when opening the vscode after installing Intellicode.
This issue happens when js files is opened by default.
Couldn't download IntelliCode model. Please check your network connectivity or firewall settings.
Visual Studio IntelliCode Version: 1.1.0
Version: 1.29.1 (user setup)
Commit: bc24f98b5f70467bc689abf41cc5550ca637088e
Date: 2018-11-15T19:13:36.375Z
Electron: 2.0.12
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
Architecture: x64
OS Version: Windows 10

@markw-t Thank you!. After performing the steps mentioned in #4 works for me.

Great; out of interest which specific set of steps worked for you? (there are a few in #4 )

I had tried by switching the proxy and it worked. It does not work in office network. I had tried in home  network which doesn't have any firewall settings.


Enable/disable SBOM generation for specific language types

Fixes #840
Example command to exclude a language cataloger
syft packages alpine:latest --exclude-cataloger go-module-binary-cataloger --exclude-cataloger go-mod-file-cataloger

@kzantow Motivation behind this is performance and time.

by default all catalogers are enabled, unless someone explicitly enables one or more, like --enable-cataloger npm --enable-cataloger dpkg

Sure, that works too. I'll make the change.

@kzantow Opened a new pull request here


HV-1536

https://hibernate.atlassian.net/browse/HV-1536

@gsmet Reworded the comment as per your request.

Amended and merged! Thanks.


Blank page in popup

From my web app, I do a contract call and see only a blank page in the popup. In the console log of the popup I see
Unable to get signed transaction - no pending transaction found.
switching to index 1
Uncaught (in promise) TypeError: h is undefined
    d clarityValue.esm.js:162
    d clarityValue.esm.js:193
    d clarityValue.esm.js:180
    x contract-call-details.tsx:26
    Preact 83
clarityValue.esm.js:162:10

Stacks Wallet for Web version: 2.10.0

Is this for any contract you attempt to call or a particular one?

This may be fixed once https://github.com/blockstack/stacks.js/pull/1034 is deployed via npm. @friedger is that your understanding as well?

maybe related to #1111


Misalignment of programming document in cups web interface Fix

This fixes issue #344 , Basically, cups web interface has its own header and footer, therefore we shouldn't include them in these html files since they might overlap and cause misalignment. In this modification, I merely changed their class from header to body so that they don't clash with cups web interface header.

@michaelrsweet i think that's little complicated as the header is clashing with cups web interface's header  so we need to change that, could you please tell what i can do now as according to me the only option left is to change template code for header.
the problem only occur for programming manual not in complete help

@michaelrsweet  could you please tell me what should i do to solve this issue ,like what to change instead of these files


Introduce error message for GitHub rate limit

The current error message when hitting the GitHub API rate limit gives very little information for what has happened.

Duplicate


The ability to switch off real-time code editor linting in the settings

CodeMirror has linting errors that pop up when you type invalid code:

A camper suggested we allow for them to toggle these off. Is this a feature we can easily support, and if so, should we support it?

@QuincyLarson we have debated over this in the past. And I believe we should not.
Reasons in short:

Support requests:
"My code is correct, but its not working"! - Usual suspects, "You missed a comma there, or that brace there, etc."

Habit building as debated in https://github.com/freeCodeCamp/freeCodeCamp/issues/16509
Its easy to fall into a practice of OKAY practices for example as popularized by https://standardjs.com/#standardjs--the-rules
That's a good thing, but the tradeoff for our audience is not justified IMHO, who are more often than just getting started to coding.

I would rather propose to have a lesson, following which you fall into a practice of typing code where you never see a warning.
Ex:
Step 1:
function ()

Step 2:
function () {}

Step 3:
function (paramA, ParamB) {
}

Step 4:
function (paramA, ParamB) {
 ...
}

And so on. I just typed that snippet out of muscle memory. I don't think I would be getting errors, in any steps.
Where this one would give me nightmares;
Ex:
Step 1:
function (

Step 2:
function (paramA, ParamB

Step 3:
function (paramA, ParamB)

Step 4:
function (paramA, ParamB) {
 ...

So, its worth reinforcing this paradigm.
Adding a setting will make things only more complex, and we will keep getting issues that aren't worth the time for the sake convenience these offer.
BUT, that said all I am taking about is our own editor. Users should of course do whatever they wish in their own setups, for projects, local editors etc.

@raisedadead Thanks for your detailed feedback. I hadn't thought about the spike in support issues and help questions on the forum that removing linting would cause, but you're right. This is not worth it.


Find out a way to better guide users if maven is not in path

We got feedback that a lot of users get errors because that Maven is not in their environment path. Need to find a way for the users to better troubleshooting.

Addressed in #530


How can I get a weights file of all integers?

Any weights outcome is a float-point .pth file. How can I get a .pth file made of integers int4 or int8?

hello! did you find the solution? #

Any weights outcome is a float-point .pth file. How can I get a .pth file made of integers int4 or int8?

i have same problem.did you finds the solution?


CASSANDRA-15321 replace SNAPSHOT dependencies with STABLE

Hi peeps,
I just noticed that for cassandra 4.0-alpha1, the cassandra-all has a dependency to chronicle-core version 1.16.3-SNAPSHOT.
http://repo1.maven.org/maven2/org/apache/cassandra/cassandra-all/4.0-alpha1/cassandra-all-4.0-alpha1.pom
Snapshots versions are not available on maven central, meaning cassandra-all can't be used as dependency for maven projects as is

I also noticed cassandra-driver being SNAPSHOT and moved to use the release. And, that carrotsearch was missing from the dependency list. Added.

build failure with the driver version change. looking into it…

@mck where is the build being executed? Can I see the error?

where is the build being executed? Can I see the error?

@velo if you do ant antifacts

build failure with the driver version change. looking into it…

if you undo the java-driver change, will maven builds using cassandra-all work again @velo ?
(i don't believe the name of the jar files themselves impact the maven declared dependencies. the java-driver used is a problem, it contains a version and code that is not found anywhere on the java-driver github repository, but i believe this can be fixed separately and is not part of your breakage here.)

if you undo the java-driver change, will maven builds using cassandra-all work again @velo ?

Yeah, I think that would be good enough for me.
BTW, replacing /lib folder with https://ant.apache.org/ivy/ would prevent this problem (and the cassandra driver one) from ever happening again.


fix: Backend's get_block_template must give an address for the block

It doesn't make sense to mine blocks without an output, and to generate an output we need an address. Even though it is very unlikely that the tx-mining-service will find a block in Hathor's mainnet, it is also used to mine blocks in the testnet where it indeed find many blocks.

The motivation for this change is unclear, address is in fact an optional parameter, the miner may manually add a script after the fact. I agree we should be mining blocks we can claim the reward for, but the hashrate we use is so small it doesn't make any difference.

The motivation for this change is unclear, address is in fact an optional parameter, the miner may manually add a script after the fact. I agree we should be mining blocks we can claim the reward for, but the hashrate we use is so small it doesn't make any difference.

The motivation for this change is unclear to me, address is in fact an optional parameter, the miner may manually add a script after the fact. I agree we should be mining blocks we can claim the reward for, but the hashrate we use is so small it doesn't make any difference.

I agree that it is optional. There was a hot fix in the production server with the comment # XXX: API error without address. Anyway, it makes sense to run only one miner for both blocks and transactions in a testnet. In this case, it is relevant to be able to choose the address.

The motivation for this change is unclear to me, address is in fact an optional parameter, the miner may manually add a script after the fact. I agree we should be mining blocks we can claim the reward for, but the hashrate we use is so small it doesn't make any difference.

I agree that it is optional. There was a hot fix in the production server with the comment # XXX: API error without address. Anyway, it makes sense to run only one miner for both blocks and transactions in a testnet. In this case, it is relevant to be able to choose the address.

I agree that it is optional. There was a hot fix in the production server with the comment # XXX: API error without address. Anyway, it makes sense to run only one miner for both blocks and transactions in a testnet. In this case, it is relevant to be able to choose the address. @jansegre

I think that hotfix was because of a regression on the node API that broke that endpoint when no address was given. That regression is fixed and tested. But that makes sense if the testnet relies on this.

I agree that it is optional. There was a hot fix in the production server with the comment # XXX: API error without address. Anyway, it makes sense to run only one miner for both blocks and transactions in a testnet. In this case, it is relevant to be able to choose the address. @jansegre

I think that hotfix was because of a regression on the node API that broke that endpoint when no address was given. That regression is fixed and tested. But that makes sense if the testnet relies on this.


Fix detection of test/lint cancellation.

Fixes #45

Codecov Report

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

@@           Coverage Diff           @@
##           master      #50   +/-   ##
=======================================
  Coverage   26.52%   26.52%
=======================================
  Files           8        8
  Lines         460      460
=======================================
  Hits          122      122
  Misses        338      338

Continue to review full report at Codecov.

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


Unsupported driver [mongodb]

Hey,
I just tried installing mongo support in laravel, but when I try to seed the database I get the error message:
[InvalidArgumentException]
Unsupported driver [mongodb]

when I check my php for Mongo support with:
php -i | grep 'Mongo'

I get:
MongoDB Support => enabled

In my database.php I have default set to mongodb and in the connections array I have an entry for mongodb with driver => 'mongodb'
what have I overlooked?

This issue should be closed, since it was caused by a problem that can no longer be reproduced or a simple typographical error (see https://github.com/jenssegers/laravel-mongodb/issues/334#issuecomment-57601748).

Hi,
i am also getting error while migration
[InvalidArgumentException]
Unsupported driver [mongodb]
i don't why any one plz help ...?

make sure you are adding the service provider.
if you are using lumen, make sure you are adding the service provider before $app->withEloquent();

HI Tralves
That great

thank you tralves. LOVE YOUU<3

Hi @tralves ,
That perfect solution.Thanks Dude.


Update README.md

Made the naming convention for new packages less strict

@mehalter I was asked to make the language around new template names to be less strict.


Fix audio crashes and leaks; add stress tests

Closes #174.
Resurrection of #285.

LGTM! Thanks.

Perhaps adding comments or adding to PR description what was wrong, and what the code does to fix it?

Definitely, this is a WIP; marked it as such.
I have a bunch more code floating for this that's very close to a fix but it needs to be unstashed, pushed, and documented. I'll see if I can pull it out.

Pulling out the hacks to https://github.com/webmixedreality/exokit/tree/audio-leak-2. Still needs a writeup.


Data-ize various page content-generation calls

New first-class options under page specs replace repeated hard-coded calls to specific HTML templates:

page.cover: {src, alt, artTags} replaces calls to generateCoverLink
page.main.headingMode: 'sticky', 'static', 'none' replaces calls to generateStickyHeadingContainer (or just html.tag('h1'))
page.main.classes: ['long-content'] replaces an additional level of nesting under html.tag('div', {class: 'long-content'})

Consequently, certain values no longer need to be stored in a variable or written twice:

source path & options (alt, tags) for cover art - used by both generateCoverLink and generateStickyHeadingContainer, now passed just once through page.cover
title of the page - used by both the main page template (for <title> element) and generateStickyHeadingContainer / html.tag('h1'), now passed just once through page.title (same place as before)
marking the page as long-content - in the nested container div and generateStickyHeadingContainer, now passed just once through page.main.classes

Also tweaks to function names to do with reveal strings (cccebf04544d9d80e84a32a905c5c133a46badd4) for legibility.
These changes will make it easier to fidangle code surrounding cover art and page layout into an expanded form for multiple artworks, serving as an in-between so code changes for the new feature aren't so groundbreaking.
These changes are also foundational to large image overlay, which benefits from the page template having direct access to cover art info.
Added to preview milestone since this brings relatively major changes to page-template.js, as well as tweaks to misc-templates.js and bind-utilities.js that are just kinda inconvenient to port to staging. This provides the proper fix to #148 but a separate (one-line) staging commit will fix it for the staging/release site.

This PR has breaking changes to site2.css so rename it to site3.css (obviously) before pushing preview, since static files are shared between release and preview!


Can't pass array from the table to component

Hello @gurghet!
I have a component (show-menu) which I put in <smart-table>. And menu component inside of show-menu component.
show-menu component html:
<menu :options="menuOptions"></menu>

show-menu component js:
    props: {
        menuOptions: {
            type: Array,
            required: true,
            default() {
                return [];
            }
        }
    },

use smart-table on the page:
<smart-table
    :body="body"
    :order-by="['first', 'second', 'third']"
    >
    <show-menu :menu-options="menuOptions" col="third"></show-menu>
</smart-table>

inside of script tag:
var menuOptions = [
    {
        id: 'test',
        text: 'test'
    }, {
        id: 'test1',
        text: 'test1'
    }
];

and in js file of the page:
data: {
    menuOptions: menuOptions
}

It doesnt works. No error, just empty menu list. But it works perfect outside of smart-table, for example if I move this line of code outside of smart-table:
<show-menu :menu-options="menuOptions" col="third"></show-menu>

What I do wrong?

Component props are handled specially so there may be some bugs there. Is
the component yours? If so, please try to rename 'menu-options' to a simple
word, like 'options', maybe it's a naming issue. If it's still broken I
will try to reproduce the problem.
Сб, 17 сент. 2016 г. в 9:12, lavezzi1<EMAIL_ADDRESS>
Hello @gurghet https://github.com/gurghet!
I have component (show-menu) which I put in . And menu component inside of
show-menu component.
show-menu component html:

show-menu component js:
props: {
    menuOptions: {
        type: Array,
        required: true,
        default() {
            return [];
        }
    }
},

use smart-table on the page:

inside of script tag:
var menuOptions = [
{
id: 'test',
text: 'test'
}, {
id: 'test1',
text: 'test1'
}
];
and in js file of the page:
data: {
menuOptions: menuOptions
}
It doesnt works. No error, just empty menu list. But it works perfect
outside of smart-table, for example if I move this line of code outside of
smart-table:

What I do wrong?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gurghet/vue-smart-table/issues/22, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAZrf9BNfqjd2JTLraiVk-49tkjVBjigks5qq5LUgaJpZM4J_h_Q
.

I tried it doesn't help.

I tried to reproduce my problem and that's what I got: http://codepen.io/anon/pen/rrLKAy?editors=1010#0
That's not exactly what I want to accomplish but very very close. Still doesn't works.

I hope you take a look at it.

Thanks for reproducing the problem. Apparently this is not documented well enough.
All the components you put in the smart-table are children of the smart-table. If you want to access properties of the parent smart-table you have to prefix them with $parent.
Furthermore, you are trying to access the parent property 'listItems' which doesn't exist. You should try to access options instead (depending on what you want to do).
<showmenu :options="$parent.options" col="more"></showmenu>

http://codepen.io/gurghet/pen/dppRvL?editors=1010#0
Please tell me if this works for you. I'll close the issue for now.

@gurghet It works perfect on codepen, I played with it to create more complex components. But unfortunately it doesn't works in my real case, in my project...
In my
show-menu component js:
I deleted the:
            default() {
                return [];
            }

Because it doesn't need if I set required value to true right? And now I got the error  Invalid prop: type check failed for prop "menuOptions". Expected Array, got Undefined. (found in component: <show-menu>)

I'm not able to reproduce this problem. I'm afraid you have to make sure that menuOptions actually contains an array at time of initialization.
Would you mind posting the code that contains the data that should initialize menuOptions?

---

and in js file of the page:
data: {
    options: menuOptions
}

---

<show-menu :menu-options="$parent.options" col="third"></show-menu>

Try to put some example data in options to see if it works
data: {
  options: [{ name: 'some data' }]
}

No, it doesn't.
Only works like if I do:
<show-menu :menu-options="[{ id: 'somedata', text: 'some data' }]"></show-menu>

This clearly means the link between the <show-menu> component and the root instance is not as simple as it was in the codepen. Try to understand the hierarchy between the smart-table and the instance holding data: { options: ... }. Maybe you need another $parent.$parent.

Actually when I wrote $parent.$parent it works with
data: {
  options: [{ id: 'somedata', text: 'somedata' }]
}

but didn't works:
data: {
  options: menuOptions
}

What that means?

I'll try to explain more detailed. And real data.
I have index.html page with:
<smart-table
    :body="body"
    >
    <smart-table-view-more :list="$list" col="more"></smart-table-view-more>
</smart-table>

index.js


Toolbox feature dataZoom: Cannot read property 'group' of undefined.

Version
5.0.2
Steps to reproduce
Try zoom by toolbox zoom feature.
What is expected?
Zoom is worked.
What is actually happening?
Toolbox zoom is broked after migration to 5.0.2. Error:

// fix cannot read property ‘group’ of undefined
 animationDuration: 5000,
 animationDurationUpdate: 5000,

设置 silent: true看下是否有效避免


fix: bundle naming collisions when using device filesystem cache

Summary
Closes #660
To prevent naming collisions on the device filesystem we're now using uniqueId as a filename.
Script.locator.uniqueId is generated by prepending caller to the scriptId.
If the caller is unknown, then uniqueId is equal to the scriptId.
Notes
This PR changes the cache key from v3 to v4 so all previous cache won't be accessible with the next release that includes this PR
Test plan

[x] - local test on federation tester
[x] - added unit tests to ScriptManager suite
[ ] - verify the change works in super app showcase scenario
[ ] - (optionally) verify canary release fixes the issue

Canary release for testing<EMAIL_ADDRESS>


A fresh zebrad instance tries to verify the highest block

As far as I understand, the sync service and block downloader should download blocks roughly in chain order. But I'm seeing zebrad download the tip of the current chain within a minute or two of starting.
Either our assumptions about zcashd are wrong, or zebrad has a bug:

[ ] the sync service queries blocks from genesis onwards
[ ] peers respond with hashes based on our queries
[ ] the downloader rejects blocks that we haven't asked for

I'll try to make a branch and add diagnostic logs.

I'm using the branch in PR #699.
The diagnostic warning is "unexpected high block".

I haven't looked in detail, but I think the mistaken assumption may be "peers respond with hashes based on our queries". Peers can send unsolicited messages at any time. (I know, it sucks.)

@daira Something like that is probably the cause, but zebra-network doesn't make that assumption. Instead it's designed with the assumption that peers may send totally unrelated messages and goes to some effort to interpret whether any of the messages it sees are potential responses, so that the caller gets high quality responses (for instance, when you request a block, it checks that the block received is actually the block requested).
So this sounds like a bug where that interpretation and filtering logic is breaking down, not a bug where we're making a bad assumption about the network behavior.

@hdevalence I don't think the sync service rejects high block hashes, and I'm not sure if it can.
So I think:

zebrad::sync is getting a high hash from a peer, and then downloading it, or
zebra-network is getting an unsolicited high block from a peer, and returning it to the syncer.

From https://en.bitcoin.it/wiki/Protocol_documentation#getblocks , the response to a getblocks message is an inv message with the hashes of the following blocks.  However, inv messages are also sent unsolicited to gossip new blocks across the network.  Normally, this wouldn't be a problem, because for every other request we filter only for the messages that are relevant to us.  But because the response to a getblocks message is an inv, the network layer doesn't (and can't) distinguish between the response inv and the unsolicited inv.
But there is a mitigation we can do.  In our sync algorithm we have two phases: (1) "ObtainTips" to get a set of tips to chase down, (2) repeatedly call "ExtendTips" to extend those as far as possible.  The unsolicited inv messages have length 1, but when extending tips we expect to get more than one hash.  So we could reject responses in ExtendTips that have length 1 in order to ignore these messages.  This way we automatically ignore gossip messages during initial block sync (while we're extending a tip) but we don't ignore length-1 responses while trying to obtain tips (while querying the network for new tips).
[Note: this is separate from the process of handling gossiped blocks when they do not collide with our queries]
(This also wouldn't be a problem if the chain-finding algorithm was sane and included the common root as the first entry of the response).

(This also wouldn't be a problem if the chain-finding algorithm was sane and included the common root as the first entry of the response).

During initial sync, we could trick peers into providing the common root by making the locator send hashes for (tip-1), ... rather than (tip). At least in the typical case.

Turns out that leads to a lot of special cases: we need to track the chain, and we need to handle the genesis block specially.

But there is a mitigation we can do. In our sync algorithm we have two phases: (1) "ObtainTips" to get a set of tips to chase down, (2) repeatedly call "ExtendTips" to extend those as far as possible. The unsolicited inv messages have length 1, but when extending tips we expect to get more than one hash.

I don't understand; absolutely nothing stops there from being unsolicited invs with length > 1. I would think that if you don't want to be trying to verifying blocks beyond the range you've asked for, you have to ignore them based on their height, not on the length of the inv.

Yes, nothing stops there from being unsolicited inv messages of larger length, in the same way that nothing stops a peer from replying to a getblocks message maliciously with garbage data. That has to be (and is, albeit as-yet-incompletely) handled elsewhere.
But it's still worthwhile to try to avoid misinterpreting an honest peer's messages, which is what ignoring responses of length 1 does.


Updated to work with Rclone v1.44

Thanks! Let me check few things, and I'll merge it.
I'm not sure about change in utils.h for prepending space to --config. If this is fix for macOS then I think proper fix would be to add space after " config" string here:
RcloneBrowser/src/main_window.cpp
Line 274 in 7106638
QTextStream(tmp) << "#!/bin/sh\n" << GetRclone() << " config" << GetRcloneConf().join(" ") << "\n";
Also not sure about move -> moveto change. This probably will not work in some cases.

That is for macOS, yes, but I'm not as well known in this, so if you think the proper fix would be to add space, then that's probably better.
The move -> moveto is because when I tried to move a file, let's say in Movie (2009) there was a file named Movie (2009).mkv, here's an example of the structure:
Movie (2009)
------Movie 20009.mkv
, if I tried moving it to New Location Movie (2009), it just created a new folder in the same folder as the file, so that it was now like this:
Movie (2009)
------Movie 20009.mkv (now a folder)
------------Movie 20009.mkv (the real file)
It might be something I did wrong, but it worked when move was changed to moveto.

@mmozeiko
I enjoy a lot RcloneBrowser. Unfortunaletlly I am not able to propose PR not to compile it.
Could we have an official update release?
TIA
CTone

@jonaknop
@MostHated
I can confirm what MostHated reported. Same issue here (use W10 x64). Tried all proposed workarounds.
Simply, it seems unable to use a custom location of config and furthermore is unable to configure the standard location either.
CTone

@jonaknop @mmozeiko
As I noticed something strange, as I used this version while I kept the official one (1.2) (each on different directories), the second one, when opening settings, there were some values there ... of the official one.
Searching in the registry i found out two things
a) rclonebrowser is not truly portable as it stores its parameters in the registry
b) seems that there some issue with the storage in the registry, see image.

Hello!. I am a complete zero in programming, and do not know English), could you compile your branch under windows 32 and 64 bit. I would be very grateful!

does this work for rclone 1.41 from ubuntu 18.10 ?

@mmozeiko would it be possible to get this merged?

If you want to contact the developer, leave him a message on reddit.  He is active on that site.  Here is his profile.  https://www.reddit.com/user/martins_m
He doesn't really hang out here anymore.


[analyzer] Expression.staticParameterElement should not be null for method with generics

Follow up on dart-lang/linter#2530
On the following example functionExpression.staticParameterElement.library is null for the generic case ff but not for f. Both should be set with a non-null variable.
class MyMap<K, V> {
  void f(void Function(int a) p) {}
  void ff(void Function(K a) p) {}
}
m() {
  MyMap().f((int? a) {}); // staticParameterElement.library is correctly set
  MyMap().ff((Object? a) {}); // staticParameterElement.library is null
}

(with analyzer-1.5.0)
/cc @scheglov

This issue still exist in analyzer-4.3.1. I just faced it again in https://github.com/dart-lang/linter/pull/3568#discussion_r935636271


feat: add remaining modifiers to NoteLookup

This PR:

Adds horizontal split modifier (#1045)
Adds copy note link modifier (#1046)
Adds tests for various modifier interactions

Submitting a draft for timely communication.
pending tasks:

[ ] fix note type modifier so that failing tests pass
[ ] make multi select + copyNoteLink test work

think of our tests as guardrails vs blueprints - they're here to make sure big features work, not to execute all code paths
right now, speed of delivery is much more important then getting full coverage

noted 👍🏼

changing this into a draft. Found an issue with a weird onHide() behavior.

onHide behavior is fixed and hopefully this is ready to be merged 😅


OTIOVIEW: Zoom in/out with mouse scroll wheel stopped working in PySide6

In PySide2, you could use mouse scroll wheel to zoom in/out of a timeline.
This interaction stopped working when using pyside6==6.2.3.

Fixed by #1262


Which PHP version do you use?

:-1: 5.3
:confused: 5.4
:+1: 5.5
:laughing: 5.6
:heart: 7.1
:tada: 7.2

currently using php 7.2 and it is working like a charm


Scoping or filtering to specific namespace/pods

Currently is there any way to scope to a specific namespace and/or annotations such that only logs from these are forwarded. I don't see anything of the sort in the helm values.yaml.

Hi @GoldenMouse,
You should use LOGDNA_EXCLUSION_RULES env variable to set the exclusion rule to anything that does NOT match your namespace:
- name: LOGDNA_EXCLUSION_RULES
  value: "!(*my-namespace*)"

The agent uses k8s logs symlinked to /var/log/containers/. K8S logging drivers will create symlink files to using the following pattern: {pod-name}_{namespace}_{containerid}.log. So you could use "!(*my-namespace*)" or "!(*_my-namespace_*)"
TLDR: We have an internal ticket to document this sort of allowlisting/denylisting.

Documentation would be good; this took me hours to figure out.  And still it doesn't work the way I want.  For instance, I only want a few namespace logged. Inclusion rules doesn't seem to work - it includes /var/log/ no matter what.

I agree we should support it: I've filed an internal ticket to support excluding or including only pods matching labels and annotations (LOG-9906).
About including /var/log no matter what, I also found it unexpected initially. We have an internal ticket (LOG-9352) to allow overriding that behaviour. In the meantime, we will tackle that issue with documentation.
To workaround this issue, the best solution is to use negative exclusion rules (exclude everything that doesn't match).

It is not working tested for 3.7 and 3.6.
          - name: LOGDNA_EXCLUSION_RULES
            value: '!(*default*)'

With this ^ rule I still see all logs.

Thank you for the feedback @Mmmariusz. We were able to reproduce this behavior and have filed an internal ticket to investigate further.
In the meantime, as a workaround, you could just use the LOGDNA_EXCLUSION_RULES to explicitly exclude log file you don't want to see.
Additionally, the above mentioned feature (LOG-9906) is complete and will be included in our next release. This will allow you to explicitly target Kubernetes objects such as namespaces, rather than using glob patterns.

TLDR: We have an internal ticket to document this sort of allowlisting/denylisting.

@jorgebay - Was this ever released? If yes, could you please point to the documentation?

Hi Sagar,
I'm currently not dedicated to this project, I think the feature is documented under the K8s docs: https://github.com/logdna/logdna-agent-v2/blob/3.8.6/docs/KUBERNETES.md#configuration-for-kubernetes-metadata-filtering
The settings are LOGDNA_K8S_METADATA_LINE_INCLUSION and LOGDNA_K8S_METADATA_LINE_EXCLUSION.
@stsantilena Can you confirm that this is included in the latest 3.8 release? can this ticket be closed?

Hey @jorgebay - Yes, this work was included in the 3.8 release. I'll defer to @gjanco on whether or not he wants to close this issue as I'm no longer dedicated to this project either.

Closing the loop on this.  This fix is currently available in all distros.
cc: @AdamHattrell


[IPFS get] Do not cache exceptions

The back-end processing queue had a few failures caused by IPFS timeouts. All the retries failed with logs that look like this:
2020-08-02T04:49:47.198016519Z [INFO]  dshop.utils.handleLog: Event OfferCreated for listing Id 1-001-233
2020-08-02T04:49:47.201167573Z [DEBUG] dshop.utils.events: Upsert event...
2020-08-02T04:49:47.207408834Z [DEBUG] dshop.utils.events: Event exists
2020-08-02T04:49:47.210113302Z [INFO]  dshop.utils.handleLog: OfferCreated - 592 by 0xDF73aF150b8E446a6D39FDdc2CFA7Bf067B88936
2020-08-02T04:49:47.210283391Z [INFO]  dshop.utils.handleLog: IPFS Hash: QmYNkDPPDtX1QbDBrjLSBJwr66GabdDh6DHG6vXwmeYNoG
2020-08-02T04:49:47.215113744Z [INFO]  dshop.utils.handleLog: Using IPFS gateway https://ipfs.ogn.app for fetching offer data
2020-08-02T04:49:47.21534627Z [INFO]  dshop.utils.handleLog: Fetching offer data with hash QmYNkDPPDtX1QbDBrjLSBJwr66GabdDh6DHG6vXwmeYNoG
2020-08-02T04:49:47.21873529Z [ERROR] dshop.queues.eventsProcessor: Log handler failed: IPFS gateway timeout

Notice that based on log timestamps, fetching the offer data from IPFS returned with a timeout immediately, despite the timeout being set to 60sec... I checked the content for that hash is available by logging into a server container and fetching the content.
It turns out there is a subtlety in the way memoize works for async functions. It caches the Promise. Therefore, if the Promise gets rejected (due to an IPFS timeout), all subsequent calls to the function for the same IPFS hash would return the same exception as opposed to trying to fetch the content again. Which explains why the queue retries all failed.
Fixed by adding a wrapper method that clears the memoize cache in case of an exception.
Also cleaned up Jsdoc for this file.

Looks good. Did you just test it manually, or wondering if it's worth adding a simple test in here...

Yes I did test manually but let me add a quick unit test. Good to have!

Reworked the memoize wrapper and moved it under @origin/utils/memoize
Refactored the code a bit so that we now have a single place @origin/ipfs/index where this code leaves as opposed to duplicating it under backend/src/util/_ipfs and @origin/ipfs


sts vBump <IP_ADDRESS> from <IP_ADDRESS>

@ssreerama can you please link the issue that's been approved in the PR description?


GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v5.8 to before v5.15.25",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=04f9bf2bac72480ca1d289b751b956dd1707a5d5",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=bf4161eb7e3bc63986eab516b147196d2240d743"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "04f9bf2bac72480ca1d289b751b956dd1707a5d5",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "bf4161eb7e3bc63986eab516b147196d2240d743",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "perf bpf: Defer freeing string after possible strlen() on it\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.15.25 by commit bf4161eb7e3bc63986eab516b147196d2240d743, it was introduced in version v5.8 by commit 04f9bf2bac72480ca1d289b751b956dd1707a5d5. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2022-1000470


Error

2022-01-27T19:48:47.367411+00:00 heroku[worker.1]: Stopping all processes with SIGTERM2022-01-27T19:48:48.018196+00:00 heroku[worker.1]: Process exited with status 02022-01-27T19:48:50.127895+00:00 heroku[worker.1]: Starting process with command python3 bot.py2022-01-27T19:48:50.768873+00:00 heroku[worker.1]: State changed from starting to up2022-01-27T19:48:54.000000+00:00 app[api]: Build succeeded2022-01-27T19:49:39.598695+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/" host= and so on..
Please solve it.. your codes are showing this error on heroku

Restart dynos

This Not Over Issue


When I create a project to scan with the devel and deploy I would like to avoid renaming inputs

When I create a project to scan with the devel and deploy I would like to avoid renaming inputs.
Instead I would like to either:
Upload inputs or add URLs and state which is To and which is From.
In particular URLs cannot be easily prefixed by hand and need today to be downloaded, renamed and uploaded.

For input URLs, we could add support for tagging the inputs using a sort of "prefix":
from:https://url1
to:https://url2

Now for the uploaded inputs, there's no easy way to flag things using a form input type (drag and drop).
We could have multiple input fields but I do not like this solution as it only makes sense in the context of this specific pipeline for now.
We could instead have a way to "tag" inputs post upload from the "Inputs" box section in the project details view.

re: https://github.com/nexB/scancode.io/issues/708#issuecomment-1530913139
This could work OK for a start, and we may evolve this with something similar for uploaded files later.

And we would need to be able to tag URLs we upload also in the API and command line. Until the alternative would be:

fetch the files by hand (say with wget)
rename accordingly with a to- or from- prefix
create a project and upload the renamed files

Implemented in https://github.com/nexB/scancode.io/pull/1069/
See https://scancodeio.readthedocs.io/en/latest/faq.html#how-to-tag-input-files for the various uses of the tag features.


Add init command

It should be possible to run npx relative-deps --init that does the following things

install relative-deps as dev dependency
initialize an empty relativeDependencies section in package.json
set up postinstall script (and others?)

Released as part of 1.0.0


Feature/Users can log in (1/2)

Context
Users need to be able to log into the app. We have decided to use magic links for this.
This is part 1 of this feature: it sets up the flow and the forms but doesn't send any emails. The magic link is printed directly on the page(!). Therefore the whole flow is feature flagged. PR 2 will add and configure Notify for emails.
Changes proposed in this pull request
Support managing users via the admin
This is a bit ick because the admin is chaotic, but it works for now.

Use the django-magic-link library to support signing in using a magic link
I chose this library because

it creates a new table for magic links, which is cleaner than abusing the password reset flow
it has the useful feature that there's an additional POST to make on sign in, which prevents overzealous email clients (outlook) from invalidating magic links by prefetching the URL
it has auditing built in
it makes no assumptions about how to send the email, so we can control that how we like

Sign in page

Insecure confirmation page
(Note that for security, this page is the same whether the email exists or not)

Add crispy-forms and crispy-forms-gds
GDS forms and especially the error handling are tricky and time consuming to code. These well-maintained libraries make it a lot easier.
There is a small hack to support crispy-forms-gds because it only works with django templates, not jinja2 — see commit for details.
Error handling:

Set up and integrate django.contrib.messages
Show a message when the user signs out (django-magic-link is in the way for signing in, but we can live with that for the good it does us elsewhere).

Context processors
This PR builds on #104 to manage menus using a context_processor — have a look in that file to see how menus are now configured.
Guidance to review
Pls run locally as well as reviewing code
Link to JIRA ticket
https://technologyprogramme.atlassian.net/jira/software/projects/CON/boards/418?selectedIssue=CON-139
Things to check

[X] I have added any new ENV vars in all deployed environments and updated the .env.example and .env.test files in the repo

Thanks for review @252afh !

If trying to continue without an email address at all, it provides the error message "This field is required". Wondering if we can make this more specific, e.g. "Your email address is required"? Not a huge issue as there's only one input on the page! And I think we'd want to lose the full-stop on all validation error messages.

Good points, will adopt


v1.0.0

DSL2 version of nf-core/circrna.
A few minor comments on the linting warnings:

I need some assistance configuring the full AWS test dataset. The data can be accessed via SRA, this should be straightforward using fetchngs.

Links to manuscripts / DOI links - I have a paper for the workflow currently under review, I'm hoping this will be accepted soon having addressed reviewer comments.

I feel like comments from https://github.com/nf-core/circrna/pull/69 haven't been integrated in this PR yet.


[Bug] AllPaths incorrect on const objects

The paths for the object { a: 1, b: 2, c: [{ d: 3 }, { e: 4 }] } as const are incorrect.
But it works correctly for { a: 1, b: 2, c: [{ d: 3 }, { e: 4 }] }.
Reproduction:
https://stackblitz.com/edit/typescript-wrimqa?file=index.ts
Thanks for looking into this 👍

Thanks for opening this issue, this is fixed on the main branch

Publish as v1.0.11

Thank you very much for the quick fix 👍


Content sent via sendBuf/sendBufTo is not correct

Take sendBuf as example, the parameter buffer is not put to fi_context2. After sendBuf method return, the pointer may be get released even the buffer pointer was passed to fi_send which is asynchronous. Thus, the content referenced by the buffer pointer may be not the same content when we call sendBuf. It causes incorrect content being sent.
int RdmConnection::sendBuf(const char* buffer, int buffer_size)

@tanghaodong25 , please check.

yes, I'm thinking if we can use fi_sendmsg with FI_INJECT_COMLETION, which guarantees that the buffers will not be read from again and the application may reclaim them. Do you have any suggestion?

@tanghaodong25 , I fixed the issue by referencing it from the chunk which is in-turn referenced by fi_context2.  It makes sure buffer not being released after sendBuffer return. Before that, I removed the "const" modifier of buffer. otherwise, I cannot set it to chunk's buffer.


Feature request: two-step exponential model for Mars

The exponential atmosphere model currently implemented for Mars is accurate only roughly up to 25km.
As suggested in Gallais, P. Models of Atmosphere, pages 21–29. Springer Berlin Heidelberg, 2007.
doi:10.1007/978-3-540-73647-9_3, two distinct exponential atmosphere model can be fitted: one for 0-25km, and one for 25+km, see Table 3.2 of the above reference:

To motivate this implementation, here is a plot I just made comparing the simple exponential atmosphere model (currently implemented), the one I call "two-step" exponential model, as well as Mars GRAM 2010 (truncated after 250km), and the MCD 5.3:

This shows the two-step exponential model stays closer to both Mars GRAM and the MCD. I do not suggest replacing the existing exponential model, but giving the option between the one-step or two-steps models.

I think this would be a worthwhile model to implement, and can think of a couple of options:

Implement this as above, with/without a check for continuity at the switch point of models
Implement this, with only the scale height for the second model (>25 km) provided, and the reference density calculated from enforcing continuity at he switch point
I think both models could be implemented (which would be implemented as the same atmosphere model, but with different factory functions)
Alternatively, we could implement the above (both options) as a succession of not just 2, but N, exponential atmosphere models

My preference would be for the latter, implementing both the interface options. What are your thoughts on this?

A little late, but I finally caught up to my emails...

Implement this, with only the scale height for the second model (>25 km) provided, and the reference density calculated from enforcing continuity at the switch point

I would not be entirely in favor of this. If I understand correctly, this would mean that we then have an incorrect density as a function of altitude between 0-25km. This means that, between the current implementation, and this suggestion, a user would have to choose between having an accurate density before or after 25km, but never both.

Alternatively, we could implement the above (both options) as a succession of not just 2, but N, exponential atmosphere models

This would definitely have my preference. Especially since this model could then be made configurable, by passing for instance a list of altitudes, reference density, and scale heights, having by default the current or (linked) two-step models. This would actually allow having just one function defined for exponential atmosphere, with some default options (including the current one) being available (and exposed) to users, to avoid breaking backward-compatibility

No worries, there is no rush with this issue :)

Implement this, with only the scale height for the second model (>25 km) provided, and the reference density calculated from enforcing continuity at the switch point

I would not be entirely in favor of this. If I understand correctly, this would mean that we then have an incorrect density as a function of altitude between 0-25km. This means that, between the current implementation, and this suggestion, a user would have to choose between having an accurate density before or after 25km, but never both.

Well, kind of. It would allow different scale heights at different altitudes, but would enforce that the curve of density as a function of altitude is continuous, which imposes a constraint on the combination of reference density and scale height for each atmosphere range

Alternatively, we could implement the above (both options) as a succession of not just 2, but N, exponential atmosphere models

This would definitely have my preference. Especially since this model could then be made configurable, by passing for instance a list of altitudes, reference density, and scale heights, having by default the current or (linked) two-step models. This would actually allow having just one function defined for exponential atmosphere, with some default options (including the current one) being available (and exposed) to users, to avoid breaking backward-compatibility

Indeed, this would allow full control to the user to impose scale heights/reference densities. But, but allowing this control, the user can also provide values that lead to discontinuities in the density with altitude.
I think that having both could be advantageous as interfaces (depending on whether you want to be sage, or in control)

I think that having both could be advantageous as interfaces (depending on whether you want to be sage, or in control)

I totally agree, this should be the way to go then I think. I also gives user a choice to go more in depth or not in their implementation (and so if they don't want to, we avoid making this too complex as a default)


fix: remove legacy alert

Description
Title

Testing required outside of automated testing?

[x] Not Applicable

Screenshots (if appropriate):

[x] Not Applicable

Rollback / Rollforward Procedure

[x] Roll Forward
[ ] Roll Back

Reviewer Checklist

[ ] Description of Change
[ ] Description of outside testing if applicable.
[ ] Description of Roll Forward / Backward Procedure
[ ] Documentation updated for Change

:tada: This PR is included in version 1.184.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Analyzer: implementing null-aware operators

Tracking issue for null-aware operators.
Proposal: https://github.com/gbracha/nullAwareOperators/blob/master/proposal.md

What work remains here? Looks like dart2js and VM have completed their work on this.

The only issue that remains is #23464, which I've been delaying waiting for an email discussion with Gilad to conclude.  I will ping him.
Issue #23464 is just an issue with the presentation of the warning message; the analyzer is generating static warnings in all the correct circumstances.  So I think we can consider the analyzer implementation of null-aware operators to be feature complete.  I will close this bug and leave #23464 open.


unique constraint violated over '_key' after restore (traditional key generator)

Originally reported by @choppedpork in https://github.com/arangodb/arangodb/issues/12378#issuecomment-770949107
My Environment

ArangoDB Version:        3.7.6
Storage Engine:             RocksDB
Deployment Mode:       Cluster
Deployment Strategy:   Docker
Configuration:               ArangoDB is deployed in custom Docker containers build using the official Debian packages, the topology is 3x agency, 3x server, 3x coordinator.
Infrastructure:
Operating System:
Total RAM in your machine:
Disks in use:
Used Package:              Debian packages

Component, Query & Data
Affected feature:

Dataset:

Size of your Dataset on disk:
the affected DB is 27MB when arangodumped
Replication Factor & Number of Shards (Cluster only):
repl. factor - 2, number of shards - 3
Steps to reproduce

Problem:
I'm getting a unique constraint violation on _key (to be specific: Response: 409, Error: 1210 - unique constraint violated - in index primary of type primary over '_key'; conflicting key: 10070041). The collection is using the default (traditional) key generator. This happens only following an arangorestore.
Expected result:

Thanks, @Simran-B! Here's some of the missing information as I can't edit the first post:
ArangoDB is deployed in custom Docker containers build using the official Debian packages, the topology is 3x agency, 3x server, 3x coordinator.
Size of your Dataset on disk: the affected DB is 27MB when arangodumped
Replication Factor & Number of Shards (Cluster only): repl. factor - 2, number of shards - 3

@choppedpork Thanks, edited. In hindsight, it would had been easier to let you create the issue so that you can edit it.

Engineering shared the following information:
We recently identified that with all the traditional and the padded key generators there can be the following problem, at least in the cluster:

You have a collection on installation A. This installation has seen quite a few documents already, so the internal id sequence generators have larger values.
a dump is taken from that installation A and restored into a different installation B
on B, the collection is restored fine and all documents get the key values as in the dump. However, creating new keys in that collection may fail with unique constraint violation, because for new documents the key generator is used, but the sequence value may not have been bumped forward by the restore

Thanks @Simran-B - that is indeed exactly our use case, ArangoDB is part of an application deployment we're currently load testing. We're taking backups, terminating all of the infrastructure and then starting back from backups the following day.

Hi. Is there any update on this?
I believe this may be the root cause for #19460. We are in the process of upgrading ArangoDB to 3.10.8 but not sure if that will fix the issue.

@Nahuel92 : this was an issue with arangorestore in versions before 3.8.9 (ArangoDB 3.8 branch) 3.9.10 (ArangoDB 3.9 branch), or before 3.10.5 (ArangoDB 3.10 branch).
It should be fixed from the mentioned versions onwards.


[SVE][TC-LVL-3.1] Test Step 16 shoule have same PICS with Step 14

Problem
Step 14 ("sends a Move to level command") send MoveToLevel command only if LVL.S.A0010 (OnOffTransactionTime) is supported.
If the DUT does not support LVL.S.A0010, MoveToLevel will not be invoked on DUT. So the current level are remains unchagned.
The Step 16 read current level in this condition is invalid, and should also be skipped as same as Step 14.
https://github.com/project-chip/connectedhomeip/blob/78dc599df930c05aacb49502975a214539dacee2/src/app/tests/suites/certification/Test_TC_LVL_3_1.yaml#L177

@bzbarsky-apple TC-LVL-3.1 is fixed in PR please verify it and close the ticket

Thanks.
will retest on Monday.

Verified. Step skipped as expected.


Changing the defaulted CDN for Pure to something more up to date in the new theme generated file

Currently the defaulted cdn for pure in a new theme page ::
http://yui.yahooapis.com/pure/0.6.0/pure-min.css
However we could use this instead since they recommend it::
<EMAIL_ADDRESS>

Where are you changing this? Are you talking about the devtools plugin? If so, this issue should be raised there, or better yet, edit the file and submit a PR.

Understood. I'll submit a pull request there! Thank you.


error indexOF undefined

dear henrie, big props to this amazing plugin. i almost got it to work, even sniffed out the codes, but after adding them to my config.json, and reloading homebrige, i got this error.
do you know how to fix it? im a rookie in the pi business!
cheers and thank you!
fynn
[11/1/2016, 10:59:36 PM] [Switch A] Initializing RCSwitch accessory...
[11/1/2016, 10:59:36 PM] [Switch B] Initializing RCSwitch accessory...
[11/1/2016, 10:59:36 PM] [Switch C] Initializing RCSwitch accessory...
[11/1/2016, 10:59:36 PM] [Switch D] Initializing RCSwitch accessory...
/usr/local/lib/node_modules/homebridge/lib/api.js:46
if (name.indexOf('.') == -1) {
^
TypeError: Cannot read property 'indexOf' of undefined

and the config.json part:
},  {
"accessory": "RCSwitch",
"name": "Switch A",
"onCode": 5359777,
"offCode": 5353887,
"pulseLength": 329,
"bitLength": 24,
"repeats": 10
},{
"accessory": "RCSwitch",
"name": "Switch B",
"onCode": 5352849,
"offCode": 5352852,
"pulseLength": 329,
"bitLength": 24,
"repeats": 10
},{
"accessory": "RCSwitch",
"name": "Switch C",
"onCode": 5353617,
"offCode": 5353620,
"pulseLength": 329,
"bitLength": 24,
"repeats": 10
},{
"accessory": "RCSwitch",
"name": "Switch D",
"onCode": 5353809,
"offCode": 5353812,
"pulseLength": 329,
"bitLength": 24,
"repeats": 10
},{

Huh. Sorry for the slow reply. What version of homebridge and
homebridge-rcswitch-gpiomem are you running? I'll see if I can replicate.
Also are you sure about the pulse length of 329?
Nate
On Tue, Nov 1, 2016 at 4:09 PM, fynn<EMAIL_ADDRESS>wrote:

and the config.json part:
}, {
"accessory": "RCSwitch",
"name": "Switch A",
"onCode": 5359777,
"offCode": 5353887,
"pulseLength": 329,
"bitLength": 24,
"repeats": 10
},{
"accessory": "RCSwitch",
"name": "Switch B",
"onCode": 5352849,
"offCode": 5352852,
"pulseLength": 329,
"bitLength": 24,
"repeats": 10
},{
"accessory": "RCSwitch",
"name": "Switch C",
"onCode": 5353617,
"offCode": 5353620,
"pulseLength": 329,
"bitLength": 24,
"repeats": 10
},{
"accessory": "RCSwitch",
"name": "Switch D",
"onCode": 5353809,
"offCode": 5353812,
"pulseLength": 329,
"bitLength": 24,
"repeats": 10
},{
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/n8henrie/homebridge-rcswitch-gpiomem/issues/7#issuecomment-257714233,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABLYDLGB8iutgcNorR3FSTq0iDvd7_G9ks5q57iygaJpZM4Kmo_0
.

hey nate! thanks for the reply.
i managed to fix this bug. it was caused by a misconfiguration of another accessory.
but i still cant use ur plugin. ive been trying to send signals with your rf_pi, but nothing goes through.
ive connected the send module to 2 (vcc) 6 (grd) and 11 (out - atad)
the receive module is hooked up to 4 (vcc) 9(grd) and 13 (in - data)
is it possible to connect both modules or is this where my error origins?
fynn

thanks nate for your reply. the original error was due to a misconfig.
i take it has to be the exact puls length? what if i have a different length on the out frequence?
fynn

ur right. the puls length was incorrect. extraordinary work nate! you made my year!

Sweet! Glad you got it working. If there's nothing else, would you mind closing the issue?


helm-deploy github action

This is an initial exploratory version for deploying helm charts to openShift. This is mostly copied from here, I would like some feedback on what I have so far. I'm unsure if the GHRC image registry is required in this instance, as well as the secrets. Also, where is it intended that secrets or env is pulled from?

Ah i see that you're supposed to specify the env at the top of the file, so nvm on that question. 👍🏻

PR is in draft mode and there's still some work to do before it's ready for another set of eyes. Removing myself as a reviewer for now.


alasql behaviour different when run vs step through

When the code below is run without interruption, the final setOption() call results in the table being EMPTIED as if a TRUNCATE TABLE had been executed. If you step through it using the debugger the behaviour is as intended. Suggestions for a workaround also appreciated.
Tested in Brave browser using alasql<EMAIL_ADDRESS>and strict mode.
 function setOption(prop, value){
            let sql = "SELECT count(id) as numrecs FROM dbOptions WHERE app = 'list_' AND property = '" + prop + "'";
            let info = alasql(sql);
            if(info[0].numrecs === 0) {
                sql = "INSERT INTO `dbOptions` (`app`, `property`, `propertyValue`) VALUES('list_', '" + prop + "', '" + value+"')";
                alasql(sql);
            } else {
                sql = "UPDATE `dbOptions` SET `propertyValue` = '" + value + "' WHERE `app` = 'list_' and `property` = '" + prop + "'";
                alasql(sql); //The problem appears to happen when this is executed.
            }
            alasql("COMMIT TRANSACTION");
        }

        function getOptions() { //get all options
            return alasql("SELECT `property`, `propertyValue` FROM `dbOptions`");
        }

        alasql("CREATE localStorage DATABASE IF NOT EXISTS listdb");
        alasql("ATTACH localStorage DATABASE listdb");
        alasql("USE listdb");
        alasql("CREATE TABLE IF NOT EXISTS `dbOptions` (`id` int PRIMARY KEY, `app` char(255), `property` char(255), `propertyValue` char(255))");
        alasql("TRUNCATE TABLE `dbOptions`");

        console.log("INSERT: A = FIRST VALUE");
        setOption("A","FIRST VALUE");
        console.log(JSON.stringify(getOptions(), null, 4))
        console.log("INSERT: B = SECOND VALUE");
        setOption("B","SECOND VALUE");
        console.log(JSON.stringify(getOptions(), null, 4))
        console.log("REPLACE: 'A = REPLACEMENT VALUE");
        setOption("A","REPLACEMENT VALUE");
        console.log(JSON.stringify(getOptions(), null, 4))

Local storage operations are asynchronous.
https://github.com/agershun/alasql/wiki/Async
This means that if you let it run like this you dont know if the first command is done before the next is initiated. I am not sure about how it works when stepping.
All in all, use promise notation. I recommend something like
alasql(["CREATE localStorage DATABASE IF NOT EXISTS listdb",
"ATTACH localStorage DATABASE listdb",
"USE listdb",
"CREATE TABLE IF NOT EXISTS `dbOptions` (`id` int PRIMARY KEY, `app` char(255), `property` char(255), `propertyValue` char(255))"
,"TRUNCATE TABLE `dbOptions`");

or if you need to step for debugging
await alasql(["CREATE localStorage DATABASE IF NOT EXISTS listdb"])
await alasql(["ATTACH localStorage DATABASE listdb"])
await alasql(["USE listdb"])
await alasql(["..."])

or
await alasql.promise("CREATE localStorage DATABASE IF NOT EXISTS listdb")
await alasql.promise("ATTACH localStorage DATABASE listdb")
await alasql.promise("USE listdb")
await alasql.promise("...")

or
await alasql(["CREATE localStorage DATABASE IF NOT EXISTS listdb"])
      .then(()=>alasql(["ATTACH localStorage DATABASE listdb"]))
      .then(()=>alasql(["USE listdb"]))
      .then(()=>alasql(["..."]))


RN revert changes to 1.3

-Remove the changes to 1.3 because of it breaking ckan and my mod/the
game from loading.
@linuxgurugamer This needs to go hand in hand with removing those
metadata files I mentionned in the forum PM. Once all that is deleted I will quickly remove the releases for 1.3.

@linuxgurugamer changing my mods to use kspavc to version check from now on. This will hopefully prevent this from ever happening again in the future.

#rebuild


Update intro slides

[x] Links
[ ] People

[x] Daniel
[ ] Liming - @clarkliming please add to the branch
[ ] Joe - @shajoezhu please add to the branch
[ ] Shuang @shuangli22 please add to the branch

[ ] chat channel - waiting for @shajoezhu information
[ ] Slido - does not work in China, at least in the office I cannot even create an account on the website. What would be an alternative @shajoezhu @clarkliming @stevemun ?

[x] would https://www.mentimeter.com/ work?

Yes, menti works well. We have a shared menti account. I will give it to you tomorrow.

Super thanks @Stevemun !


[DC-2134] Verify if RemoveParticipantDataPastDeactivationDate does or does not require an update

@lledezma - This looks good to me, but could you resolve the conflict?  Once that's taken care of, I will approve.  Thanks!


operator apicurio-registry (1.1.3-v2.6.4.final)

Thanks for submitting your Operator. Please check the below list before you create your Pull Request.
New Submissions

[ ] Are you familiar with our contribution guidelines?
[ ] Are you familiar with our operator pipeline?

[ ] Have you tested your Operator in all supported installation modes?
[ ] Have you considered whether you want to use semantic versioning order?
[ ] Is your submission signed?
[ ] Is operator icon set?

Your submission should not

[x] Add more than one operator bundle per PR
[x] Modify any operator
[x] Rename an operator
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description of the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[x] Valid category name1
[x] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[x] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

hi reviewers, the tests failure check_operator_name_unique is a known issue that has happened during the previous release as well https://github.com/redhat-openshift-ecosystem/community-operators-prod/pull/4437 . Please allow an exception, the issue is caused by a past mistake and we are unable to rename the operator at the moment. We are planning to fix it in the future by creating a new package.

/label tests/skip/check_operator_name_unique

hi @jfrancin Can you please add the tests/skip/check_operator_name_unique label? Apologies for pinging you directly, but I've seen you mentioned in another PR. Is it possible to add a more permanent exception?

Thank you!

I tried adding it for another partner earlier; I think the automation rejected it.
Please note that I am not one of the normal people who support the Community pipeline; the people who do have the ability to add permanent exceptions.


Create p003-Dot-product.cpp

You may wan't to use a library instead of hard plain c++, but installing c++ lib isn't as simple as pip install . So for the moment I propose to stick to plain c++.

If more C++ people have strong opinions on how to move forward, we can consider it.
I fear that as we progress, you will probably want something better than pure raw C++, but I will try to leave that up to whoever is contributing consistently. For now, I'll just merge this!


Adjust IRC rate limits

Cinch's standard limits of 10 queue size and 0.5 per second are a bit odd. 1 per second is generally acceptable on most networks, but at least on hackint, a slightly lower queue size seems to be necessary to avoid messages getting swallowed by something.

Travis CI integration appears to be broken, but the build passed: https://travis-ci.org/github/ArchiveTeam/ArchiveBot/builds/742188431


Implement do-notation as a macro

One possible approach:
(do
  <- x getLine
  (putStrLn x))

Another, with <- used infix:
(do
  x <- getLine
  (putStrLn x))

This has the advantage that it is similar to Haskell, albeit at the expense of being less Lisp-like. However, given that Axel aims to stay true to Haskell where possible, this solution is currently preferred.

The example with <- infix is what the current implementation looks like (and accurately depicts the extent of its capabilities, i.e. there is not yet support for let etc.)


Improve PearAI UX for choosing models

Context
Improve the login and choosing model flow for PearAI now that we have a PearAI server as an option.
Current behaviour
Right now users choosing a model looks like this:

On first time app open

Clicking "Cloud models" goes to the chat panel, but it uses "Free trial" models (see bottom left). Users have to click the '+' on the bottom left to open up the models panel and choose a different model. (Bad cause we don't have free trial yet)

At the models panel (panel where you choose models), users can select "PearAI Server", to go to the PearAI Server model panel

The PearAI server model panel then looks like:

Changes needed
A couple things need to change here:

at (4) the PearAI Server panel, make buttons look nicer: text and button size consistent.
at (4), change last button text to "Start coding 😎"
at (2), we don't have free trials. It should ask the user to choose a model directly (redirect to the models panel (this is the panel that appears when you click the bottom left "+")).

Secondary tasks:

at (1), PearAI server should be an option directly (can also be another PR)
at (4) we shouldn't even need the 'click to complete' button , after the user clicks login, it should wait the code-oss://pearai.pearai/auth/ callback (frontend landing page opens up the app with that link) and automatically continue. This might take some elbow grease so we can do this in another PR as well

The line to look at is here:
https://github.com/trypear/pearai-submodule/blob/be276437eefcb20517d9837234c34b149ce84c38/gui/src/pages/modelconfig.tsx#L197

at (2), we don't have free trials. It should ask the user to choose a model directly (redirect to the models panel (this is the panel that appears when you click the bottom left "+")).

@Fryingpannn @nang-dev
we have default config.json content defined at https://github.com/trypear/pearai-submodule/blob/be276437eefcb20517d9837234c34b149ce84c38/core/config/default.ts#L7-L27
should we remove them and replace with pearai-server's ?

we also have https://github.com/trypear/pearai-submodule/blob/be276437eefcb20517d9837234c34b149ce84c38/core/config/onboarding.ts#L1
anyway, an appropriate config should be created after onboarding

ill take the secondary tasks a part now.

@MaySoMusician we actually should* have a free trial so it actually works out of the box. But for this beta launch lets just set it to pearai server as well as OpenAI (with no api key, theyre gonna have to input this). UX will not be perfect

S/o @Himanshu-Singh-Chauhan for doing the UI/UX flow!!!
only thing left is the default models (free trial) that need to be changed

done