add where based dimensions to pandas backend

Summary
Dimensions only found in the where clause need to be included
addresses: https://github.com/airbnb/mensor/issues/23
cc: @ailurus1991
Test Plan
Ran the example

Great! Thanks Dan!


Feature simple log implementation

Description
This creates a new logs endpoint that works with the new faas-provider interface the http request to the log provider as described in openfaas/faas#751 and openfaas/faas-provider#15
Motivation and Context

[x] I have raised an issue to propose this change (required)

See openfaas/faas#751
and openfaas/faas#1130
and openfaas/faas-provider#15
How Has This Been Tested?

This has been manually tested so far, i plan to write some tests soon
This can be tested using these instructions

https://gist.github.com/LucasRoesler/a6d0c5e2e669825ec4ab613e3487f1e8 (installs with the updated k8s provider)
https://gist.github.com/LucasRoesler/ec0c365d02296c29e66be683247be8aa

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I've read the CONTRIBUTION guide
[x] I have signed-off my commits with git commit -s
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

@alexellis i have also updated this PR with the changes from https://github.com/openfaas/faas-provider/pull/15

Hi, I think this needs a rebase and maybe re-vendor of faas-provider etc?
Alex

I just pushed another rebase on master

Thank you

do you want me to squash it into a single commit?

I'm fine with this. I thought I merged it, but maybe I missed that

I'm seeing this error, which may be why the rebase was rejected?

I got a DM from Lucas saying that the PR was merged (as I thought), but that GitHub's events appear to be lagging behind. This feature is in master now.


Duplicate organization and repository rows under star history table

Bug report
Been noticing a couple of rows with repeated organization and repository name pairs (not too sure if its from testing, but the data in this table is not that important since its a cache so not to worry). I did verify that the updating of the cache is working without inserting new rows though. Two possible solutions:

Do a check if a row with the organization and repo exists before inserting

Change PK of the table to be organization and repository to enforce this from the DB

Personally feel that option 2 is more optimal - i guess this is one of the instances which the table editor should support creation of more than 1 PK for a table as well haha
For now, we can do it via the second method by good ol' SQL query

odd i was testing this again and it seems like the cacheing wasn't causing any duplication - nonetheless i've created a table with organization and repository forming a composite primary key to enforce this.
if anyone wants do any testing though, i've kept the old stars history table and renamed it as stars_legacy - feel free to use that.


Add dataset: spanish_golden_age_sonnets

A URL for this dataset
https://github.com/bncolorado/CorpusSonetosSigloDeOro
Dataset description
This corpus comprises sonnets written in Spanish between the 16th and 17th centuries.
Each sonnet has been annotated in XML in accordance with the TEI standard. Besides the header and structural information, each sonnet includes the formal representation of each verse’s particular metrical pattern.
The dataset is very interesting both for analyzing patterns / writer's behaviors, but also to train models with historical language data.
Also I am planning to add extra information (translating) on the dataset card related to the descriptions that are in Spanish.
Dataset modality
Text
Dataset licence
Creative Commons Attribution Non Commercial 4.0 International
Other licence
No response
How can you access this data
As a download from a repository/website
Confirm the dataset has an open licence

[X] To the best of my knowledge, this dataset is accessible via an open licence

Contact details for data custodian
https://data.cervantesvirtual.com/

@thebooort  thanks for suggesting this. Looks great. We're likely to have quite a few source datasets with TEI. I didn't look closely at the schema for this but one option that could be interesting to explore would be to support one config that is focused on capturing more of the metadata captured in TEI and one focused on the text. Feel free to shout if you decide to work on this and want any input.

Yes! I will be working in it to add it. I will start reading all the docs on the academic paper they provide, and will move from there. Will ask u any doubt I found along the way ! :)

@thebooort Are you working on this dataset? I would like to add this dataset if you aren't working on it already

Hi @shamikbose  I have a version of this dataset in huggingface (sorrry for the late reply!)
https://huggingface.co/datasets/thebooort/spanish_golden_age_sonnets
I added the datacard info too. so it may be ready for review!
Also @davanstrien  let me know if I should change anything or make anything in a different way (should i transfer it to Biglam ORG already or wait till the corrections/changes?)

#self-assign

#ready-for-review

@thebooort, thanks for working on this!
Happy for you to transfer this over to the BigLAM organization. I will make a pull request with some suggestions for the README, but this looks great otherwise.

ty!  I just transferred the repository, let me know if everything is ok! (I see no preview for de dataset rn)

ty! I just transferred the repository, let me know if everything is ok! (I see no preview for the dataset rn)

Thanks, I just made a small pull request with some suggested changes (https://huggingface.co/datasets/biglam/spanish_golden_age_sonnets/discussions/1). If this looks okay feel free to merge (or I can also do it).

@thebooort thanks again for working on this :)

@davanstrien thanks to you and all the organisers of the hackathon! :smile:


Add e2e test for modifying 02-client params

Summary
Add a test ensuring that only allowed clients are allowed to be created

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged/assigned

Use gov v1 message when #3640 is merged.


Optimize for load time

Please look into using activationCommands in package.jsonto make the package only activate once one of the commands are used.

Nice catch. Thanks. Done in v0.24.3.


homework 5

Approach:

Q1: Message Queue Implementation

Implemented a MessageQueue class with methods for adding messages and synchronized receiving.
Created MessageSender and MessageReceiver classes, both implementing the Runnable interface.
Added a simple run method in both classes for sending and receiving messages using the MessageQueue.

Q2: ExecutorService Integration

Integrated ExecutorService with separate ThreadPools for sender and receiver tasks.
Utilized the submit method to execute tasks asynchronously and printed the messages using dedicated threads.

Q3: Custom Thread Implementations

Implemented the FactorialThread and FactorThread classes, both implementing the Runnable interface.
The FactorialThread class performs the simple task of calculating factorials, while the FactorThread class handles factor calculations.

Added Logging System:
Integrated a logging system, leveraging the Logger architecture from a previous homework assignment, for consistent logging across the project.
Screenshots

Drift Video :
Link : https://video.drift.com/v/abD2dKDVV2yYNKZ1XZCyFw2tWCZRSwiMCRbRn5SNFz3ag/

Metric
Value

alert_status
:white_check_mark: OK

bugs
1

code_smells
1

reliability_rating
C (at least 1 Major Bug)Note: A being best, E being worst

security_rating
A (0 Vulnerabilities)Note: A being best, E being worst

vulnerabilities
0

Metric
Value

alert_status
:white_check_mark: OK

bugs
0

code_smells
0

reliability_rating
A (0 Bugs)Note: A being best, E being worst

security_rating
A (0 Vulnerabilities)Note: A being best, E being worst

vulnerabilities
0


openssl 1.1.1b fails with clang 3.4.1 (FreeBSD10)

After updating our OpenSSL version from 1.1.1a to 1.1.1b, it would no longer compile under FreeBSD 10.4 (clang 3.4.1 default).
CC="cc" /usr/local/bin/perl crypto/modes/asm/ghash-x86_64.pl elf crypto/modes/ghash-x86_64.s
cc -fPIC -pthread -Wa,--noexecstack -Qunused-arguments -Wall -O3 -g -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_CPUID_OBJ -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DKECCAK1600_ASM -DRC4_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DGHASH_ASM -DECP_NISTZ256_ASM -DX25519_ASM -DPADLOCK_ASM -DPOLY1305_ASM -DOPENSSLDIR="\"/opt/symas/ssl\"" -DENGINESDIR="\"/opt/symas/lib64/engines-1.1\"" -D_THREAD_SAFE -D_REENTRANT -DNDEBUG  -c -o crypto/modes/ghash-x86_64.o crypto/modes/ghash-x86_64.s
clang -cc1as: fatal error: error in backend: Starting a frame before finishing the previous one!
gmake[2]: *** [Makefile:4030: crypto/modes/ghash-x86_64.o] Error 1
gmake[2]: Leaving directory '/usr/home/build/sold-<IP_ADDRESS>/FreeBSD10.4-amd64/build/openssl.amd64'
gmake[1]: *** [Makefile:172: all] Error 2
gmake[1]: Leaving directory '/usr/home/build/sold-<IP_ADDRESS>/FreeBSD10.4-amd64/build/openssl.amd64'
gmake: *** [/usr/home/build/sold-<IP_ADDRESS>/openssl.make:104: inter-build-openssl.amd64] Error 2

After building clang 6.0.1 from ports I was able to build OpenSSL 1.1.1b without issue.
So my underlying belief is the issue is related to a bug in clang 3.4.  What's interesting however is that the issue was not triggered with OpenSSL 1.1.1a.  I'm filing this mainly as a reference in case others hit the same problem.

Does dbb1340314fcec37662d79720e6566fdd5a232e8 fix your problem?  It's been committed to the 1.1.1 branch after 1.1.1b...

@levitte Yep, that solved it.  Thanks!


Ubuntu 20.04 Crashes on ~phase2

Hi,
I was recently plotting by official chia plotter and everything worked fine.
Wanted to upgrade to MadMax and while plotting after some time (it depends on number of cores I use) whole system crashes (it freezes, nothing moves on screen, video play stops and mouse not moving, can't do anything except reset button).
When I use 1 core it freezes on ~phase 4, while using all 64 cores it passes pahse1 and freezes on phase2.
I use Ubuntu 20.04 AMD Threadripper 32 cores 64 threads, plotter is new bought about 2 months ago.
Could you give me any advice what can I do?

What is your memory voltage?
Try to increase it.

What is your memory voltage?
Try to increase it.

Hi,
So I have kind of similar situation too, I am using ubuntu 21.04 and my whole system freezes after table 5 or 6 in phase one  and then I have to force power it off. For temp dir I am using 3* 1tb gen4 nvme. I even tried plotting with using 50gib of ramdisk as bcache and something odd hapenned, after table 2 or 3, I got a warning saying "system overloaded in last 5 min" and the process just stopped, I could see it in glances but it consumed 0% cpu after table 2 but the system didn't freeze but it didn't pass table 2 it was just stuck there. Both times I used 16 threads and even 10 threads too but no difference. I am using 5900x and 64gb of 3600mhz ram. Should I try to increase the voltage also?

Not sure, but maybe it was running out of memory?

+1  Ubuntu  20.04  system dead

+1 for me too.
I am running Ubuntu 21.04, AMD 5900x, 32GB RAM using 2 x 1TB nvme in RAID0 as temp1 and 2 x 1TB nvme in RAID0 as temp2. Occasionally plotting completes, but more often than not the system completely freezes in table 3 and requires a hard reset.

Not sure, but maybe it was running out of memory?

I don't think it's running out of memory since 9 or 10gib was still free. Also the official plotter works fine will 11 plots in parallel it's only madmax causing problrm

It is not lack of memory problem, because I have 64GB of RAM and I was monitoring it whole time MadMax was running and never went more than 10GB of allocated memory, I don't have experience in boosting and maybe increasing memory would help but I am very curious what is going on with this freeze, is MadMax changing some deep config of operating system, changing memory voltage or something like that? There are no problems on Ubuntu Server probably but I need to test that on my machine

+1 for me too.
I am running Ubuntu 21.04, AMD 5900x, 32GB RAM using 2 x 1TB nvme in RAID0 as temp1 and 2 x 1TB nvme in RAID0 as temp2. Occasionally plotting completes, but more often than not the system completely freezes in table 3 and requires a hard reset.

Fyi, I reinstalled Ubuntu today using 20.04 Server on exactly the same hardware and have made several plots without the same freezing/crash (previously it would freeze every 2nd or 3rd plot). So at least in my case it appears to be something to do with 21.04 or the fact that it was the Desktop version.

+1 for me too.
I am running Ubuntu 21.04, AMD 5900x, 32GB RAM using 2 x 1TB nvme in RAID0 as temp1 and 2 x 1TB nvme in RAID0 as temp2. Occasionally plotting completes, but more often than not the system completely freezes in table 3 and requires a hard reset.

Fyi, I reinstalled Ubuntu today using 20.04 Server on exactly the same hardware and have made several plots without the same freezing/crash (previously it would freeze every 2nd or 3rd plot). So at least in my case it appears to be something to do with 21.04 or the fact that it was the Desktop version.

I'm using Ubuntu 21.04 Server version


Update error handler instrumentation point for Flask v2

Before contributing, please read our contributing guidelines and code of conduct.
Overview
This PR adds an additional instrumentation point for register_error_handler for compatibility with Flask v2.
Related Github Issue
Closes #234

This should also take out the xfails introduced in the previously merged PR.

🚀


Certain dependency situation can make pub get/upgrade run out of memory

This issue was originally filed by @taisph

What steps will reproduce the problem?

Make a new directory and put the following in pubspec.yaml in that directory.

name: dart_pub_test
dependencies:
  angular: any
  core_elements: any

Run pub get.
Wait.

What is the expected output? What do you see instead?
I expected the required packages to be installed or an error saying there was a dependency problem.
After 7 minutes I got an Unhandled exception: Out of memory.
What version of the product are you using?
$ pub version
Pub 1.5.3
On what operating system?
Ubuntu 14.04 64-bit
Please provide any additional information below.
SLVR: BacktrackingSolver took 0:07:33.559082 seconds.
    | - Requested 27 version lists
    | - Looked up 1300836 cached version lists
    | - Requested 121 pubspecs
    | - Looked up 1943197 cached pubspecs
    |
FINE: Clean up system cache temp directory /home/taisph/.pub-cache/_temp.
ERR : Connection closed before full header was received
FINE: Exception type: ClientException
Exhausted heap space, trying to allocate 2560 bytes.
Uncaught Error: Out of Memory
Stack Trace:
#0      Object.toString (dart:core-patch/object_patch.dart:33)
#1      Trace.Trace.from.<anonymous closure> (package:stack_trace/src/trace.dart:104)
#2      LazyTrace._trace (package:stack_trace/src/lazy_trace.dart:1)
#3      Trace.Trace.current.<anonymous closure> (package:stack_trace/src/trace.dart:31)
#4      LazyTrace._trace (package:stack_trace/src/lazy_trace.dart:1)
#5      LazyTrace.terse.<anonymous closure> (package:stack_trace/src/lazy_trace.dart:29)
...
...
#6      _rootRunBinary (dart:async/zone.dart:742)
#7      _RootZone.runBinary (dart:async/zone.dart:867)
#8      _Future._propagateToListeners.handleError (dart:async/future_impl.da#9      _Future._propagateToListeners (dart:async/future_impl.dart:574)
#10     _Future._completeError (dart:async/future_impl.dart:343)
#11     _Future._asyncCompleteError.<anonymous closure> (dart:async/future_impl.dart:406)
#12     _asyncRunCallbackLoop (dart:async/schedule_microtask.dart:23)
#13     _asyncRunCallback (dart:async/schedule_microtask.dart:32)
#14     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:128)
Unhandled exception:
Out of memory
Full verbose output available on request ~128MB log uncompressed.

This issue has been moved to dart-lang/pub#1072.


Fix test running in no_std context

Add extern crate std in appropriate places so that even if the surrounding context has #![no_std] the property tests can continue to run.
TIL: extern crate std in anywhere other than the crate root cannot be used with ::std. It has to be std

LGTM


Returning 404 Status is Incorrect

https://github.com/edgexfoundry/blackbox-testing/blob/master/bin/postman-test/collections/core-data.postman_collection.json#L361
https://github.com/edgexfoundry/blackbox-testing/blob/master/bin/postman-test/collections/core-data.postman_collection.json#L929
When I run these two core-data test script, it's expect return 409 http status ,
cause hummidity is non-existent value descriptor .
I have check java version and go version,
...should return 409 http status at
https://github.com/edgexfoundry/edgex-go/blob/master/core/data/event.go#L262
Just like java version’s core-data
https://github.com/edgexfoundry/core-data/blob/master/src/main/java/org/edgexfoundry/controller/impl/EventControllerImpl.java#L273"
===============
update ...
here are same error at core-metadata
https://github.com/edgexfoundry/edgex-go/blob/master/core/metadata/rest_deviceservice.go#L99
https://github.com/edgexfoundry/edgex-go/blob/master/core/metadata/rest_deviceservice.go#L111
and it's also define in
https://github.com/edgexfoundry/edgex-go/blob/master/core/metadata/raml/core-metadata.raml#L1348

cc @jpwhitemn @tsconn23

It appears the statuses were changed during the initial conversion from Java to Go. Example:
https://github.com/edgexfoundry/core-data-go/blob/master/event.go#L249
To me 404 is more appropriate since we're aware that a value descriptor on the event is not found. By contrast, 409 is as follows:
https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/409
So again, I think the service logic is appropriate but the RAML and tests need to be updated @jpwhitemn @andyf1967

@tsconn23
this is data validation error , I think use 400 as bad request is more sensible,
https://tools.ietf.org/html/rfc7231#section-6.5.1

@andyf1967 @jpwhitemn Please chime in here. Same type of situation as #211

Looks to me as though 404 Not Found is the correct error.  I think if not too much work we should fix RAML and update Java code and tests.

Per sites like this one:  http://www.restapitutorial.com/httpstatuscodes.html, 404 would be the correct response as the resource is not found (The requested resource could not be found but may be available again in the future).  Agree with @tsconn23 .  Update the RAML to meet the current Go code.  We'll update the Java code if not too much lift- otherwise record as an issue against the Java service.


MINOR: fix race condition in KafkaStreamsTest.shouldReturnThreadMetadata

Call for review @bbejeck @guozhangwang @dguy
We should pack port this to 1.0.x, too.

retest this please

I piggy back some JavaDoc fixes (got reported at use list: https://mail-archives.apache.org/mod_mbox/kafka-users/201712.mbox/<CADyNd1QCMi3uEUZZZxz5HFDzd5uYft6GWkjemwBmdLQ3nRptxw%40mail.gmail.com>

Updated this.

LGTM. Merged to trunk.


Setup WordPress Test Suite

Run https://github.com/wp-cli/wp-cli/blob/master/templates/install-wp-tests.sh in provisioning.

https://github.com/vccw-team/vccw/pull/186#issuecomment-260123719


Wrong resources shown in Navigator when switching project with cluster connected

This is weird one and might be hard to reproduce:

Load a local project with many resources/files
Connect to a cluster, select a namespace (or all) with many resources
Go back to load a new project with few files/resources (without first disconnecting from your cluster)
You will be prompted that the cluster connection will be terminated - selected ok
Expected behaviour: Explorer shown with new project Navigator containing resources in new project
Actual behaviour: Explorer shown with new project, Navigator shows resources in previous project (!)

reloading the folder with the "Reload" button on top of the explorer loads the correct resources into the navigator

judging from the console log - what seems to be happening is that when exiting the cluster:

the previous project gets handled by the validation listener
the newly loaded project also gets handled - but is cancelled
the validation result for the previous project comes back - and replaces the resources of the newly loaded project

This is still happening sometimes, will keep an eye on it and try it again after the local/cluster issue https://github.com/kubeshop/monokle/issues/3757


feat: TOC and Sidebar override [v3]

This PR includes improvements to the TOC and Sidebar components that can be overridden through the theme config.
1. TOC component export to allow the following:
toc: {
  title: "Custom TOC title",
  backToTop: false,
  float: true,
  component(props: ComponentProps<typeof TOC>) {
    return (

Custom element

        <TOC {...props} />

    );
  }
}

This will allow us to add a wrapper around the built-in TOC component.
2. A possibility to set a custom component for the Sidebar component + its export:
sidebar: {
  component(props: ComponentProps<typeof Sidebar>) {
    return

Custom element

      <Sidebar {...props}/>

  },
  toggleButton: false
},

The same approach already exists for a number of other components, so I think it would be quite useful and fair to have the same DX for the TOC and Sidebar components.

Hi @dimaMachina, could you please take a look? Would it be possible to include this in the 3.0.0-alpha.25 release? Thanks!

Sorry I am not interested in overriding the sidebar and TOC, you probably should use a custom theme


It is very slow to open recently.

It was very fast, but recently, it takes 3~4 seconds to open the dialog.

Sorry, I mean the Visual Studio, not VSCode. close the issue


Uncorrect matching behavior of fly.target

Found weird issue.
When sourcing files like ./uikit/uikit.sass uikit-react/uikit-react.sass transforming with fly-sass
and then placing compiled files to ./dist/css for example.
It produces ouput like ./dist/css/uikit.css and ./dist/css-react/uikit-react.css instead of all in a single place.

Can you please show your task?

Here is flyfile
const path = require('path')

/**
 * Aliasses
 */
const jn = path.join
const rs = path.resolve

/**
 * Main dirs
 */
const mainPath = jn(__dirname, 'app/ui-kit')
const distPath = rs(__dirname, '../dist')

/**
 * Sass file sources
 */
const sassFiles = [
  jn(mainPath, 'scss/gl-uikit/gl.uikit.scss'),
  jn(mainPath, 'scss/gl-uikit-angularjs/gl.uikit.angularjs.scss')
]
const cssDist = jn(distPath, 'gl-uikit/css')

/**
 * Js sources
 */
const jsFiles = jn(mainPath, 'module/*.js')
const jsDist = jn(distPath, 'js')

const x = module.exports

/**
 * Compile sass sources
 */
x.sass = function * (opts) {
  yield this.source(sasFiles).sass().target(cssDist)
}

/**
 * Compile ESnext sources
 */
x.babel = function * () {
  yield this
    .source(jsFiles)
    .babel({
      preload: true,
      plugins: [
        'add-module-exports',
        'transform-es2015-modules-umd'
      ],
      minified: true
    })
    .target(jsDist)
}

x.default = function * () {
  yield this.serial(['sass', 'babel'])
}

Thanks!
Are there any * in your directory names?
Also, can you please try without using any path methods. Fly does what you're doing under the hood, there's no need to resolve anything ahead of time.
const main = 'app/ui-kit'
const dist = '../dist'

const sassFiles = [
  `${main}/scss/gl-uikit/gl.uikit.scss`,
  `${main}/scss/gl-uikit-angularjs/gl.uikit.angularjs.scss`
]
const cssDist = `${dist}/gl-uikit/css`

const jsFiles = `${main}/module/*.js`
const jsDist = `${dist}/js`

There's also a typo in your sass task -- maybe copy/paste error?
Fix sasFiles to sassFiles

Nope, same thing only gl.uikit.angularjs.scss placed into target directory
It works fine with it
for (var i = 0; i < sassFiles.length; i++) {
  var file = sassFiles[i]
  yield this.source(file).sass().target(cssDist)
}

btw, I am sorry for this, it's not urgent, seems like very early in your timezone.

No problem 😆 I was awake. I just finished traveling & purposefully adopted a new schedule.
Looking into it locally.

Ok, with my setup, I have gl.uikit.angularjs.css writing to dist and I have the other file writing back to the source directory, so that gl.uikit.scss and gl.uikit.css are siblings.
Can you confirm this?

In my case gl.uikit.angularjs.css written to dist, but gl.uikit.scss is not written anywhere.
Also if i change order of files in sassFiles it behave in a different manner.

Ok. I think I see a fix. Once I'm more certain, I'll have you paste in the change & confirm before I commit, if you don't mind.

Sure, thank you.

OK. In fly/lib/api/target.js, add this to the end of trims:
const trims = (...).map(...).sort((a, b) => b.length - a.length);

Then at the bottom, when looping thru trims, change o.dir = obj.dir.replace() to o.dir = o.dir.replace()

Seems working, thanks.
Just wondering, what a purpose of mapping on dirs like it's really rare case when you want to place same files into two or more diferrent directories, isn't it?

Cool.
Not really, I do it fairly often. It also doesn't affect anything negatively & it was a Fly 1.x feature.  Maybe even 0.x, can't remember.


Tests should work on target board

It is very important that the tests work in the target environment (for example, an ARM board). This means adapting the tests so that they can be executed remotely (over adb, for example).
The tests should also be adapted so that the paths to binaries can be configured, instead of relying on the directory structure of the build hierarchy.
Also, the code that compiles and sets up the test should be refactored to make it easier to add containers with different test functionality (for example, testing network functionality).

Implemented with https://github.com/esrlabs/northstar/commit/83570bd97b6361227a7dafb0fb50ffca576328ef


[Bug]: Attempt to read property "value" on null

What happened?
Authenticate with totp to Filamentphp
How to reproduce the bug
Make sure the user has totp enabled.
Authenticate.
You will get Attempt to read property "value" on null
Related code: https://github.com/vormkracht10/filament-2fa/blob/5b37aca3f51f21129d8c5850f0cb42ca4fc3c7d0/src/Http/Livewire/Auth/LoginTwoFactor.php#L47
Suggested fix:
Replace
$this->twoFactorType = $this->challengedUser->two_factor_type->value;

with
$this->twoFactorType = $this->challengedUser->two_factor_type;

Repository
filament-2fa
Package Version
2.0.8
PHP Version
8.3.13
Laravel Version
11
Which operating systems does with happen with?
macOS, Linux
Notes
I'm using Laravel Sail on Mac.

Fixed in #52


Add rendering support for Atlassian Document Format

It would be really great to be able to parse Markdown and output a JSON document as Atlassian Document Format.
Mistletoe already supports rendering Jira syntax, but ADF is supported in both Jira and Confluence so would be incredibly useful for writing Confluence pages as Markdown.
I guess it could work similarly to the ASTRenderer works, since the BaseRenderer methods all expect string outputs, whereas this output is a JSON format so could make more sense to keep the responses as dictionaries and convert to a string at the very end.. but keen to hear thoughts.
I'd like to take a crack at this - my time is limited so may take a while :)

PS: I suggest to place the new renderer to the contrib folder.


(PUP-7675) Add support for convert_to lookup option

This adds support for convert_to in lookup_options.
The convert_to key should be either String (a data type string), or Tuple[String, Any, 1].
The result is only converted at the very end.
There is no conversion of a default value given to the lookup function,
or returned from a block computing the default value - they must return
the expected result type.

There are two TODOs regarding getting errors with the correct reference to where the fault input is - want suggestions how to do that (where can the right info be found).
Is the decision to not convert default values given to the lookup function or computed by a default block the right choice?
There is logic intended to allow a backend to return a data type instead of a string in its lookup options - that is untested. Drop that feature?

CLA signed by all contributors.

I'm questioning the passing of convert_to as an argument. I think that if the caller is aware that a conversion should be made, then that conversion is better performed by the caller than by the lookup framework. I think that letting the caller handle explicit conversion  post-lookup will also resolve the issue regarding default values (this comment has no bearing on lookup_options. That part is fine).

The conversion is "post-op" since it happens as the very last thing in  Lookup.lookup, the callers of that are very simple and do not have the same things in context that the Lookup.lookup does. As I noted earlier it would also need to do the same thing in all locations where a lookup takes place. Can naturally place that as logic that is reachable separately in Lookup, or as a wrapper, that splits off the convert_to, and calls lookup - but I figured that there is really no time you call lookup that you do not want to also support conversion (except for the internal lookup of lookup_options).

Updated - the Lookup.lookup API is unchanged. Added better errors and fixed issues from reiew.

One thing that is missing in this PR is Explain support for the convert_to.


City/District Strike Button Tweaks

Quick Explanation
CQUI makes changes to the City/District strike buttons. The most obvious is the movement of the button locations. However, more changes than that are made, but there are bugs with the implementations. This is purely a bug fix update. No new features are added in this PR. The goals/changes of this PR as as follows:
1. Ensure the strike view is always entered and exited on mouse click
2. Clicking on another strike button when one is currently selected properly opens the new strike view
3. Entering the strike view always shows the strike range and attack arrow
4. Selecting a unit while currently in the strike view exits the strike view and shows the unit panel
5. Encampment strike button is now updated on settings change
6. Updated action panel encampment ranged attack text to be consistent with the city ranged attack text
7. The action panel now ignores city centers when looking for a district that can do a ranged attack
Detailed Explanation

Detailed explanation of changes

1. Ensure the strike view is always entered and exited on mouse click.

Base game behavior: Clicking on a strike button opens the strike view. Clicking on it again does not close it.
Current CQUI behavior: The city strike button opens/closes the strike view on click. The district strike button only opens.
Expected CQUI behavior: Both the city strike button and district strike buttons should open/close the strike view on click.
Files changed: CityBannerManager_CQU.lua, actionpanel.lua, citypanel.lua, NotificationPanel_CQUI.lua

2. Clicking on another strike button when one is currently selected properly opens the new strike view.

Base game behavior: Clicking on another strike button changes the strike view to that city/district.
Current CQUI behavior: When in a city strike view, clicking a district or other city strike button closes the view and does not open a new one. When in a district strike view, clicking a city strike button properly closes and opens a new one.
Expected CQUI behavior: Both the city/district strike buttons should close their views and open a new one when selecting on another strike button.
Files changed: CityBannerManager_CQUI.lua

3. Entering the strike view always shows the strike range and attack arrow.

Base game behavior: Entering the strike view always shows the strike range and attack arrow.
Current CQUI behavior: Entering the strike view when a lens was previously active will not show the strike range and attack arrow.
Expected CQUI behavior: Entering the strike view should always show the strike range and attack arrow.
Files changed: minimappanel.lua

4. Selecting a unit while currently in the strike view exits the strike view and shows the unit panel.

Base game behavior: Selecting a unit from the city strike view hides the unit panel. Selecting a unit from the district strike view does not close the strike view.
Current CQUI behavior: Selecting a unit from any strike view hides the unit panel.
Expected CQUI behavior: Selecting a unit from any strike view should always show the unit panel.
Files changed: UnitPanel.lua, worldinput_CQUI.lua

5. Encampment strike button is now updated on settings change.

Base game behavior: N/A (Doesn't have strike button settings).
Current CQUI behavior: Only the city strike button's location is updated on settings change. The district strike button is not changed.
Expected CQUI behavior: Both strike buttons should update their location when the settings are updated.
Files changed: CityBannerManager_CQU.lua

6. Updated action panel encampment ranged attack text to be consistent with the city ranged attack text.

Base game behavior: N/A (Doesn't have encampment ranged attack notifications).
Current CQUI behavior:

City Strike Notification: CITY RANGED ATTACK - Your city can perform a ranged attack.
District Strike Notification: Encampment Ranged Strike - Your encampment is able to make a ranged strike.

Expected CQUI behavior:

City Strike Notification: CITY RANGED ATTACK - Your city can perform a ranged attack.
District Strike Notification: ENCAMPMENT RANGED ATTACK - Your encampment can perform a ranged attack.

Files changed: cqui_text_general.xml

7. The action panel now ignores city centers when looking for a district that can do a ranged attack.

Base game behavior: N/A (Doesn't have encampment ranged attack notifications).
Current CQUI behavior: When clicking the district ranged attack notification, sometimes a city center will be selected instead of a district.
Expected CQUI behavior: When clicking the district ranged attack notification, districts other than the city center should be selected.
Files changed: actionpanel.lua

Please stop making such massive changes in one PR. It is difficult to process these huge explanations. Like before - please specify first what the actual issue is and how the game behaves normally, with no CQUI.
CQUI is supposed to change only the location of the button. This is it. Why 8 tweaks? Is the vanilla implementation so broken or did someone break CQUI's code?

I put these all in one PR as they are all closely related. Would it be preferred to split it into several PRs? I'd be willing to do it, but that feels a bit excessive for several closely related changes. As for my explanations, I did try to explain what the issue was and what the PR does. I broke it down into several points to try to make it clear what all the code changes do, but if it's not helpful the way it is, I can try to restructure how I write these. My goal is, after all, to make it clear and easy to review and I am open to changing how I submit changes if it would make your review easier.
In the future, instead of doing paragraph explanations of each point, I can try this instead:

One sentence explanation of change
A. Description of original behavior (base game's behavior and CQUI's)
B. Description of problem
C. Description of changes

This would ultimately be the same information, but hopefully presented into a nicer way?
As for why there are 8 tweaks, they're more related than that I'd say. I broke it into 8 points to try to clearly explain the intention of the entire PR. Two of these changes address vanilla bugs, yes. Those would be point 4 and the end of point 1 As for the rest, they are issues with CQUI's and MoreLenses' (in the case of 3) implementations. Most of the issues are with the implementation of the Encampment Strike Button in particular.
I made my changes based off the comments in the code itself and based off of inconsistent behavior while playing. Like with 1, clicking on the city strike button multiple times opens/closes it, but that didn't happen with the encampment. Based off the comments in the code, this was intended, but did not work because of how it was implemented.
Another example would be 7. The code explicitly allows for right clicking away the city strike notification, but did not properly ignore city centers if that was the case. This would lead to you being selected on a city center when you click the encampment strike notification.
In the case of 6, this isn't really an issue, but rather just an inconsistency. I felt the encampment strike notification text should match the same formatting (such as the all caps) as the other notifications.
CQUI clearly intended to do more than just move the button and my goal was just to fix the implementation that was made and make the behavior consistent.

I still think grouping all of these changes in one PR is appropriate given that they are all very closely related and there are no new features added. However, I agree that the formatting of the explanations can be better. I have rewritten the entire original post now to hopefully make it easier to digest. Please let me know what you think.

Thank you for your responses! So it'd be ideal for me to open an issue post before making a PR? I can do that for sure! Sorry for not doing that so far. I often just find these small bugs while playing and I get excited to fix them as soon as possible, which makes me overlook opening issues.
Regarding 6, this is a good point! I originally just went with the text that was already there, which only used the term "Encampment", but I like the idea of using the actual district name! I have updated the code to try to get the actual district name. If that fails, it'll just use the localized word for "District" instead. Only English is updated since I don't know the other languages, but the Lua code should work for all languages if and when the others are updated. While doing this change, I also replaced mentions of "Encampment" with "District" in actionpanel.lua to be more consistent.
Regarding 7, there are two separate notifications in this case. The base game only has the one notification for City Ranged Attack, but CQUI adds in the District Ranged Attack notification. The City Ranged Attack notification takes priority and will show before the District Ranged Attack notification. You have to do your city range attacks or right-click away the City Ranged Attack notification to see the District Ranged Attack notification (Right-clicking this notification is base game behavior that CQUI preserved). Currently in CQUI, if you were to right-click away the City Ranged Attack notification though, clicking the District Ranged Attack notification could select you on a City Center district. Since these are two separate notifications, and the user has to explicitly right-click away the City Ranged Attack one, I think the District Ranged Attack notification should only select districts that aren't the city center, which is what this PR does.

Ad 7. OK. Thank you for the explanation.


Mekanism logistics pipe crash

Put mekanism wrench into item mode, right click on the pipe, crash. 100% of the time. I had it connected to a tinkers controller and a chest, wanted to pull into the controller.

Due to a bad CoFH interaction, a mod is shipping with an invalid API. Not on my end.


One build server to manage multiple PODs

One build server should be able to manage multiple pods.
At the minimum the build server will need to be on the management network for each pod.  Using tagged VLANs can support this in a scalable manner without a lot of extra cabling.

Aricent is trying to run openstack in virtual environments, so this will be supported as a result of this effort.

Randy built a central build server at CableLabs.  We'll use dhcp relay and digital rebar to handle multiple environments with this central build server.


Headers enrichment

Implementing https://github.com/snowplow/snowplow/issues/1373
iglu PR https://github.com/snowplow/iglu-central/pull/290

Exciting! Have you signed the CLA? https://github.com/snowplow/snowplow/wiki/CLA

Fixed your comment, I just signed it :)

Confirmed - thanks so much! Assigning to @chuwy to review...

@khalidjaz just remove please unused import (BasicHeaderValueParser), format config file in according with other enrichments (cookie extractor config has different formatting) and squash commits into one. Everything else looks good. Thank you!

Done thank you so much @chuwy and @alexanderdean!

Closing in favor of: https://github.com/snowplow/snowplow/issues/1373


Single-character CamelCase segments seem not to work

Examples:

Start with aBadTime.  Place cursor on B.  Type civGood<ESC>.  Result should be aGoodTime.  Instead, I get GoodBadTime.  (Rather unexpected: the character under the cursor is not included in the variable segment!)
Start with AgainABadTime.  Place cursor on B and type the same command.  Result should be AgainAGoodTime.  Instead, I get AgainGoodTime.  (Looks like two variable segments, A and Bad, got conflated.)

New user of vim-textobj-variable-segment here! I came to open an issue on this topic, but since it already reported, I will just say that I can confirm this bug. As you might expect, it's especially noticable when working on a C++ codebase, which uses the common convention of prefixing all member variables with 'm', such as 'mMemberVariable'.

Yeah unfortunately I still haven't been able to figure out vim's regexes to figure out how this should be fixed. Patches welcome if you find the issue :/.

Thank you!   I can't find any documentation on that function anywhere. I'm on Neovim, maybe related to the problem:
 nvim --version
NVIM v0.9.4
Build type: Release
LuaJIT 2.1.1692716794

Would be nice to keep this plugin compatible with Neovim -- it's become so engrained in my workflow I don't know if I can live without it :)

(I use neovim and have no such issue -- I don't have time to investigate, but 0.9 is EOL, so perhaps try upgrading to 0.10.)

(I use neovim and have no such issue -- I don't have time to investigate, but 0.9 is EOL, so perhaps try upgrading to 0.10.)

Upgrading fixed it, probably should have tried that first. Thanks


CASMINST-5979: Correct procedures for customizing NCN image timezone post-install

Description

The procedure to update NCN timezones has a few errors in it. In addition, after the CSM install is done, it really should only be used just for timezones, and passwords/SSH keys should be handled using CFS. This PR overhauls that procedure (and makes some small script tweaks) to accomplish the above. While writing and testing these changes, I found other odds and ends in related procedures that I also cleaned up with this PR.
I tested this on fanta except for actually updating the entries in BSS (but I did test the commands to do that -- I just had them echo rather than run the final command to do the update).
This will require backports, but since there are differences that will need to be handled, I'll be rolling them out as I get them ready. I am opening this one for review in the meantime, in case there is feedback I need to address.
Notes/caveats:

I eventually want to replace the manual code being used to update the BSS entries in this procedure. I wrote up a script to do it (just a more careful version of the basic shell commands being done), but I think that may be better off in a separate PR (just because this one is already getting on the large side).
In a recent discussion with @haasken-hpe and @leliasen-hpe , we identified further changes which are going to be needed to procedures in this PR, as well as related procedures. However, more thought and planning is required before we make those.

Given the above two points, some feedback for this PR may get shunted into a future ticket, since we know more work is required. The most important thing that this PR needs to be accomplishing is to fix the broken timezone procedure.
Checklist

[X] If I added any command snippets, the steps they belong to follow the prompt conventions (see example).
[X] If I added a new directory, I also updated .github/CODEOWNERS with the corresponding team in Cray-HPE.
[X] My commits or Pull-Request Title contain my JIRA information, or I do not have a JIRA.

/backport release/1.4

/backport release/1.4


Version check

This includes some clippy stuff and the eglCurrentDisplay patch as well.

@Kethku I'll continue my research with eglGetCurrentDisplay. I may need to make an upstream commit. The snap should be ready to merge too. I would need a review for the new github workflow though. If you would like to have admin access to the snapcraft package, just send me your email.


Does the PP calculation take into account bonuses from the garden?

Yes, it does.

Cool! Thanks for the info. You can close this issue, unless you want to keep it open.

Welcome!  Closing.


Streamline and Parallelize Benchmark Generation

To leverage the computing resources available, mqt.bench should support parallel generation of benchmarks.
From our discussion, there are two ways to parallelize:

Inside python, e.g. with joblib.
Outside python, e.g. with GNU parallel.

The chosen approach should support

a timeout (since the generation of some benchmarks takes very long)
early cancellation of benchmarks (if generation runs into a timeout with $n$ qubits, it should not try $n+1$ qubits next)
selective generation of benchmarks (e.g. just amplitude estimation with 20 to 40 qubits)

Solving this issue also requires at least a brief documentation on the generation and useful features :wink:

I couldn't resist to benchmark the compression times, curiously compression_level=2 is a little bit faster and re-compression from LZMA only slightly slower.
Found 37497 files with<PHONE_NUMBER>2 bytes (26.0GiB)

Starting compression with ZIP_DEFLATED (opt=default)
00:04:36.3 finished compression. target buffer has<PHONE_NUMBER> bytes (1.3GiB)
  Starting chunked re-compression ZIP_DEFLATED (opt=1)
  00:02:29.4 finished re-compression.<PHONE_NUMBER> bytes (2.7GiB).
  Starting chunked re-compression ZIP_DEFLATED (opt=2)
  00:02:26.3 finished re-compression.<PHONE_NUMBER> bytes (2.2GiB).
  Starting chunked re-compression ZIP_DEFLATED (opt=3)
  00:02:41.6 finished re-compression.<PHONE_NUMBER> bytes (1.9GiB).

Starting compression with ZIP_LZMA (opt=default)
00:44:25.0 finished compression. target buffer has 713083055 bytes (680.0MiB)
  Starting chunked re-compression ZIP_DEFLATED (opt=1)
  00:02:46.4 finished re-compression.<PHONE_NUMBER> bytes (2.7GiB).
  Starting chunked re-compression ZIP_DEFLATED (opt=2)
  00:02:43.9 finished re-compression.<PHONE_NUMBER> bytes (2.2GiB).
  Starting chunked re-compression ZIP_DEFLATED (opt=3)
  00:02:59.8 finished re-compression.<PHONE_NUMBER> bytes (1.9GiB).


Support for ESP01

This modification uses https://github.com/kokke/tiny-regex-c library instead of the default ccp #include <regex>. This reduces the size of the resulting binary below 512KB for the eZB dd3 example, making it possible to use an ESP01.
This provides support for https://www.amazon.de/dp/B0CH95T7X4, a IR-Reader with ESP-01 included.
The regex library comes with some limitations, which I tried to document in the README.md.

Hi, thanks for your contribution.
I tried it out with my setup, but found a problem with the textual sensors:

Do you have an idea why this fails?

Hi, thanks for your contribution.
I tried it out with my setup, but found a problem with the textual sensors:
Do you have an idea why this fails?

I think the internal buffer for the charsequence matcher might be too small. I'll push an update with a larger buffer.
I am really dissatisfied, that the count operation is not working, I will try to add support for fixed length matches {N} where N >= 1 to the library.

Hi, I tested both variants and both are working fine. I would prefer the one from branch feature/repetitions, because the syntax is much cleaner.
So, could you please merge this branch into main.
FYI: I plan to add a configuration switch, so that the users can switch between the std::regex variant and the small size variant. This ensures that the config of legacy users will not break.
PS: Please keep the existing code formatting.

Hi,
I merged the changes into my main branch and reset as much of the formatting as I could. It would really help if you could share your formatting settings ;-) The reformat I did was based on the style guide from esphome, which said to use Google C++ formatting.
I also added the configuration switch you mentioned and updated the README.md to include a description on how to switch.

Works like a charm. Thanks!

And it seems to be faster than std::regex. Nice!


Compare version correctly

Description
String comparison of versions breaks because we don't use a padding zero for the
patch segment of our CalVer and SemVer versioning scheme.
Checklist

[x] Update useCheckUpdate.tsx for update dialog
[X] In case I changed code in the orchest-sdk I followed its release
checklist

Should we make use of https://pypi.org/project/packaging/? Comparing versions should be about 2 lines of code

Should we make use of https://pypi.org/project/packaging/?

+1, see https://packaging.pypa.io/en/latest/version.html

Should we make use of https://pypi.org/project/packaging/? Comparing versions should be about 2 lines of code with this

Given that it is just one function, I don't think it makes sense to add an additional dependency.


Chaotic Feat: Dancing words

Describe your chaotic idea
I can add a new feature here user input dances.
Add Screenshots or Sketches
https://github.com/user-attachments/assets/c924a073-1690-46ea-858c-986fbc5aaf15
Confirm

[X] I understand that my idea will add to the chaos and I'm okay with it
[X] I agree to follow this project's Code of Conduct
[X] I want to work on this feature
[X] I'm GSSOC'24 Extd registered Contributor
[X] I'm Hacktoberfest registered Contributor

Would love to have this in React after the website is migrated
Can you do this in React??

yes i will be able to do it.

Sure I will let you know once it is migrated to react so after it you can do this in React

Go ahead @KAmaL-senpai

Whats the update @KAmaL-senpai ??

@vansh-codes i have created a pull request check.


There is no codepage. How should I add it?

dword file and named it as code page. What should I include in the content?

Out of curiosity, why are you setting the code page this way?
CONSOLE_REGISTRY_CODEPAGE looks like CodePage is a DWORD, so you should be able to set it to whatever code page you want. Looks like that value should default to the value of GetOEMCP().
Does chcp {the codepage you want} not work? IIRC you should be able to chcp ..., then open the console settings, hit "Ok", and the settings should be saved for you.


WithdrawAsync not supported in version 1

Bitget is not supporting v1:
await client.SpotApi.Account.WithdrawAsync(...)
calls "/api/spot/v1/wallet/withdrawal-v2"
and I received : [ServerError] 400172: Quantity spot.wallet.amount.empty which was nonsense as the available balance of the spot wallet was 10 x Withdraw Amount. I also double checked my parameters in debug mode.
The code written in #18 proposes a method with a different signature.

V2 API has now been fully released including the withdraw endpoint


feat: update ckb-std and use stable rust

Need to update https://github.com/nervosnetwork/capsule/wiki/Upgrade-an-existing-project-to-capsule-0.10 if this will be included in 0.10

Docs: https://github.com/nervosnetwork/capsule/wiki/Upgrade-Existing-Contracts-to-ckb-std-0.13-and-Stable-Rust
Also mentioned in https://github.com/nervosnetwork/capsule/wiki/Upgrade-an-existing-project-to-capsule-0.10


How to migrate from adminbro to adminjs

Hi all,
I was wondering if there are instructions available on how to migrate to adminjs from adminbro?
Thank you!

Looking forward to it.

admin-bro to adminjs migration is simply rewriting all occurrences of admin-bro to adminjs and AdminBro to AdminJS. There were more changes later, but not directly related to brand name migration. Most breaking changes are in v7:
https://docs.adminjs.co/installation/migration-guide-v7


Added setup configuration for search views and urls

Modified setup.py to add search views and urls in external installations.
Also added search Readme documentation.

Coverage remained the same at 58.151% when pulling 84799bf9eda7a0ef28b28f02a107ae0abadbe1c0 on setup-search into 04b6a3d2b1ac58f5925b6fda861818c2b5994a1f on dev-v2.


halo's official website url error

At the bottom, halo's official website address, you seem to have forgotten to modify

@Dacong-wu  Oh, thanks for pointing that out! That was a mistake

@all-contributors please add @Dacong-wu for bug report


Update Voyager chart to support RBAC

Voyager 3.1.0 supports RBAC. This pr updates the chart.
cc: @sadlil

Here's a suggestion for a great approach to RBAC which we recently discussed among the chart maintainers. Please have a look at it. Would you mind following this path?
https://github.com/coreos/alb-ingress-controller/pull/146
/cc @mgoodness

I will take a look. I was following the pattern used in other charts in this repo.

Marking this as stale. Please update within one week.


Add node-problem-detector

We include busybox in the runtime (AFAIK, npd calls some binaries in the runtime), so binary size increased 134MB -> 145MB
CVE: from 178 packages, 121 vulnerabilities to  122 packages, 17 vulnerabilities
(Benchmark image: registry.k8s.io/node-problem-detector/node-problem-detector:v0.8.13)

Any dependency we bump here breaks the compatibility directly.
NAME                 INSTALLED                           FIXED-IN                           TYPE       VULNERABILITY        SEVERITY
k8s.io/apimachinery  v0.0.0-20190816221834-a9f1d8a9c101  0.0.0-20190927203648-9ce6eca90e73  go-module  GHSA-74fp-r6jw-h4mp  High
k8s.io/kubernetes    v1.14.6                                                                go-module  GHSA-74j8-88mm-7496  Medium
k8s.io/kubernetes    v1.14.6                                                                go-module  GHSA-j9wf-vvm6-4r9w  Medium
k8s.io/kubernetes    v1.14.6                                                                go-module  GHSA-vw47-mr44-3jf9  Low
k8s.io/kubernetes    v1.14.6                             1.16.0-beta.1                      go-module  GHSA-jmrx-5g74-6v2f  Medium
k8s.io/kubernetes    v1.14.6                             1.16.11                            go-module  GHSA-wqv3-8cm6-h6wg  High
k8s.io/kubernetes    v1.14.6                             1.18.18                            go-module  GHSA-g42g-737j-qx6j  Medium
k8s.io/kubernetes    v1.14.6                             1.18.19                            go-module  GHSA-qh36-44jv-c8xj  Low
k8s.io/kubernetes    v1.14.6                             1.19.15                            go-module  GHSA-f5f7-6478-qm6p  High
k8s.io/kubernetes    v1.14.6                             1.20.0-alpha.1                     go-module  GHSA-8mjg-8c8g-6h85  Medium
k8s.io/kubernetes    v1.14.6                             1.20.0-alpha.2                     go-module  GHSA-8cfg-vx93-jvxw  Medium
k8s.io/kubernetes    v1.14.6                             1.24.14                            go-module  GHSA-xc8m-28vv-4pjc  Low

Fixes:
Related:
Pre-review Checklist

[ ] IMPORTANT: 'image-request' tag has been applied if this PR is adding any images, including new versions or variants

Quality Requirements for Images PRs
The items in this checklist should all be checked in the PR with exceptions clearly documented.
The general idea is that to the extent possible, the image should be a drop-in replacement to its public counterpart.

[X] Image is a smaller size than its common public counterpart, or if not, the reason why should be explained:
[X] Image should be scanned for CVEs and should return 0 or near-0 results. Exceptions should be explained.
[X] The software in the image should be able to be installed and work as expected

[X] The image should start in a cluster
[X] The application should be accessible to the user/cluster/etc. as expected

[X] If there is an open source helm chart provided, the image should be able to be used with the chart. If needed, please add a -compat package to close any gaps with the public helm chart.
[X] build for x86_64 and aarch64 if possible, document exceptions

For new image PRs only
If you have an apko.yaml file in this PR you need to follow this checklist, otherwise feel free to remove.

[X] Include tests, sufficient enough that you would trust this image running in production.

[X] Perform manual tests as needed and document your testing results

[ ] For builder images (go, python, etc), build a sample app successfully
[ ] For services images (rabbit, databases, webservers) test basic functionality, upstream install/getting started, port availability, admin access. Document differences from public image.
[ ] Applications intended for use with a specific cloud provider must be tested on that cloud provider.

[X] The version included is the latest GA version of the software

[X] The latest tag points to the newest stable version

[X] There is a dev tag available that includes a shell and apk tools (by depending on 'wolfi-base')

[X] The image runs as nonroot and GID/UID are set to 65532 or upstream default

[ ] Alternatively the username and GID/UID may be a commonly used one from the ecosystem e.g: postgres

[X] The image contains the ca-certs bundle if needed

[X] ENTRYPOINT

[X] For applications/servers/utilities call main program with no arguments e.g. [redis-server]
[ ] For base images leave empty
[ ] For dev variants set to entrypoint script that falls back to system

[ ] CMD:

[ ] For server applications give arguments to start in daemon mode (may be empty)
[ ] For utilities/tooling bring up help e.g. –help
[ ] For base images with a shell, call it e.g. [/bin/sh]

[X] Add annotations e.g:

annotations:
  "org.opencontainers.image.authors": "Chainguard Team https://www.chainguard.dev/"
  "org.opencontainers.image.url": https://edu.chainguard.dev/chainguard/chainguard-images/reference/busybox/ # use the academy site here
  "org.opencontainers.image.source": https://github.com/chainguard-images/images/tree/main/images/bazel # use github here

[X] Check if environment variables are needed e.g. to set data locations
[X] Ensure the image responds to SIGTERM

[ ] docker kill $(docker run -d --rm cgr.dev/chainguard/nginx)

[X] Error logs write to stderr and normal logs to stdout. DO NOT write to file.

Documentation Requirements

[X] Provide a README file, follow the README template to include variants, tags, and usage examples
[X] Document your testing and results in the PR
[X] Document any exceptions to the testing and config requirements outlined in this template
[ ] Document where and how the image deviates from popular alternatives (ports, packages, user, entrypoint, versions, etc). Explain why there's a difference and if the user needs to do anything differently when using the image

This needs a rebase, and might be worth porting to TF if possible.

Rebased and ported to TF. Could you please check? @imjasonh

Rebased.


Added Walkthrough Create Language Editor to Recipes Menu.

@madskristensen Please let me know if this is wrong, but I added the Walkthrough Create Language Editor.md as Walkthrough-Create-Language-Editor.html with Menu Text Walkthrough Create Language Editor

@madskristensen
This is what I did.

@madskristensen I looked at your names for the md files and it has - between words that match the file names in default.html file so I change the markdown for the Walkthough to match.

@madskristensen I looked at your names for the md files and it has - between words that match the file names in default.html file so I change the markdown for the Walkthough to match.

@madskristensen I looked at your names for the md files and it has - between words that match the file names in default.html file so I change the markdown for the Walkthrough to match.

@madskristensen
When you get a chance please merge this pull request.

Sorry, I was out of town for a vacation, and must have lost track of this one. Thank you!


Use XDG_CONFIG_HOME if defined

If defined, XDG_CONFIG_HOME will take precedence over ~/.manifoldrc for reading and writing the config file.
Closes: #227

Addendum to my last point regarding where binaries should be placed: That is only assuming that this is a user-level installation.
If being installed system-wide, it should use the default system-wide location (e.g. /usr/bin/xxx or sometimes /usr/local/bin/xxx)

@luizbranco we should probably have an OS switch in here, the windows situation is very different. They have an app data directory where this would go.
I also like the point about:
~/.config/manifold/config and agree we should default to ~/.config/manifold/ as the path we store config in on Linux / OSX if none is present
But if a config is exists at ~/.manifoldrc we should still read it for backwards compatibility.
We could also consider using it as an override.

Sorry, closing this one for now since the code didn't address the issue.


Update to ungoogled-chromium 118.0.5993.117

No modification aside from the submodule bump is needed.

sorry for the delay


failed to load source for dependency risc0-build

error: failed to get risc0-build as a dependency of package methods v0.1.0 (/root/autodl-tmp/zkFHE/methods)
Caused by:
failed to load source for dependency risc0-build
Caused by:
Unable to update<EMAIL_ADDRESS>Caused by:
failed to fetch into: /root/.cargo/git/db/risc0-8b1b9cfa1fb74959
Caused by:
process didn't exit successfully: git fetch --force --update-head-ok<EMAIL_ADDRESS>'+HEAD:refs/remotes/origin/HEAD' (exit status: 128)

cannot run even with proxy🥲


fix compile bug under clang(backend MSVC)

Compile failed under:

Because clang's backend is MSVC, so all add_definitions apply on MSVC also should apply on clang.
Use
if(MSVC OR (CMAKE_C_COMPILER_ID STREQUAL "Clang" AND CMAKE_C_SIMULATE_ID STREQUAL "MSVC"))

to replace all MSVC detect.

Ping? The CI also tests Clang 17, without failure. How exactly are you compiling it?

No follow-up, closing. Please holler if you want to pick this back up.


Decode once

I didn't really measure. Slime uses 2 hash lookups, but so do the replacement since I want to be able to store nulls. Let me check it tomorrow.

Yes, a FeatureData became about 3-5 times faster for doubles with this.
I made it completely on par with Map here: https://github.com/vespa-engine/vespa/pull/14258


AgentExecutor _call not able to read name of Runnable Binding

In trying to change the name of a tool in the logs using Langsmith, I needed to add runName as a configuration to DynamicStructuredTool https://api.js.langchain.com/classes/langchain_community_tools_dynamic.DynamicStructuredTool.html
It does not directly have a property of runName, but it does have a method call withConfig that takes in the type RunnableBinding<string | {}, string, RunnableConfig)> with RunnableConfig having the property runName.
https://api.js.langchain.com/classes/langchain_community_tools_dynamic.DynamicStructuredTool.html#withConfig
https://api.js.langchain.com/interfaces/langchain_schema_runnable.RunnableConfig.html
Here is how I've got it setup
const tool = new DynamicStructuredTool({
     name: 'ToolName',
     description:
       "Tool Description",
     schema: z.string(),
     func: async (input) => {
       const sanitizedInput = input.split('\n')[0]; // Extract only the question
       const output = await chain.invoke({ query: sanitizedInput });

       console.log('output', output);
       return output.text;
     },
     verbose: true,
   })
   .withConfig({runName: 'ToolRunName'});

When the agent runs and executes _call
It runs this
    const toolsByName = Object.fromEntries(
      this.tools.map((t) => [t.name.toLowerCase(), t])
    );

https://github.com/langchain-ai/langchainjs/blob/bc5dc0014a0167fb920e6f3423dfca83602fb471/langchain/src/agents/executor.ts#L433C1-L435C7
Except the DynamicStructuredTool I created is now  underneath/bound to a property bound of a  RunnableBinding.
https://api.js.langchain.com/classes/langchain_schema_runnable.RunnableBinding.html
name is not top level anymore, it's under bound now, bound.name is valid.  when this code runs it returns correctly a type error TypeError: Cannot read properties of undefined (reading 'toLowerCase')
Here is a screenshot from the debugger on a breakpoint right before toolsByName is run illustrating the shape.

@dosubot could you re-evaluate my original post as I had to edit it extensively

🤖
Of course! Please go ahead and share your revised post, and I'll be happy to assist you with it.
This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.
Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.
If you want to continue the conversation, start your reply with @dosu-bot.
@dosubot here is the link to my first post for this issue
https://github.com/langchain-ai/langchainjs/issues/3996#issue-2077687787

@dosubot here is a link to my first post on this issue
https://github.com/langchain-ai/langchainjs/issues/3996#issue-2077687787

@dosu-bot here is a link to my first post for this issue
https://github.com/langchain-ai/langchainjs/issues/3996#issue-2077687787


Change the HTTP gateway for ChainAPI test calls

Closes #1738
Changes made for HTTP gateway requests:

Return data from successful API calls that fail processing
Make reserved parameters inaccessible in pre/post processing

For 1, a new type, HttpGatewayApiCallPartialResponse, was added for the scenario of a HTTP gateway request that returns data from the API call but fails processing. Within this type there is an errorMessage field and success is set to true, which is necessary to bubble the data field (API response) back up through the call stack.
For 2, only preProcessApiSpecifications was modified. No changes were made to postProcessApiSpecifications because post processing only takes the raw API response data and endpoint array (for extraction of postProcessingSpecifications) as inputs and not reserved parameters:
https://github.com/api3dao/airnode/blob/dbde93c692fef338eb0f6386e74e8f708e4ab97b/packages/airnode-node/src/api/index.ts#L222

post processing only takes the raw API response data and endpoint array (for extraction of postProcessingSpecifications) as inputs and not reserved parameters

Related: https://github.com/api3dao/airnode/issues/1673

The conclusion of this discussion is to proceed with merging this and make reserved parameters inaccessible in post processing later when they get passed to post processing as part of https://github.com/api3dao/airnode/issues/1673 (they are currently not passed to post processing).


dd and rsync equivalent in PowerShell

Is there any cmdlet that work like dd and rsync in linux ,
If no , will the Powershell team add the similar feature to powershell ?
PS:
I know here(this repo) is for powershell core ,not for windows powershell,
The key point is no one will care my request or help me if I post my question to bellow official webpage .
However , here , sometimes ,some one will answer me question. and I get what I want.
Windows PowerShell
Windows PowerShell issues/suggestions need to be reported to UserVoice
https://windowsserver.uservoice.com/forums/301869-powershell

How about the powershell version of robocopy? In 2016, I also saw someone submitting an issue. Is anyone willing to help continue to develop?
@tlsalex you can use dd and rsync in linux version of powershell,any linux command you can use.
can you tell us what do you want?

Is there any cmdlet that work like dd and rsync in linux ,
If no , will the Powershell team add the similar feature to powershell ?

dd and rsync are both available natively for Windows, through Cygwin, or through WSL.

How about the powershell version of robocopy? In 2016, I also saw someone submitting an issue. Is anyone willing to help continue to develop?

robocopy is not a part of cmd but a separate standalone application. It doesn't make sense to make a "powershell" version of it. You could certainly write a version in PowerShell that uses the native File APIs, but that would be reinventing the wheel.

In general, native commands will work within PowerShell.  It would be nice to have a PowerShell equivalent so you can work with objects, but the reality is that if there is a native command that works, it wouldn't make sense to spend time on an equivalent cmdlet vs spending that time on addressing some other issue.

It doesn't make sense to make a "powershell" version of it. ----

How about the powershell version of robocopy? In 2016, I also saw someone submitting an issue. Is anyone willing to help continue to develop?

For reference, that issue is here: #2581 and is "up-for-grabs"

Just to be clear, I'd love to see cmdlets for all heavily used native commands, however, it's a question of priority.  I'd rather spend team resources on enabling new scenarios and use cases vs porting something that works today (perhaps not ideal) just to make it PowerShell-y.  Would love to see the community pick up this type of requests.

I know this has been asked before but if we had the equivalent of ConvertFrom-String in PowerShell core it would be relatively simple to wrap the native commands in PowerShell which would also serve as a transition path for Windows administrators

ConvertFrom-StringData is available, though more limited.
Honestly I always find it easier to work with a decent regex -match expression and generate PSCustomObjects from that. ConvertFrom-String was always a lot more work in my opinion, and despite what it said on the tin I have yet to find anyone who preferred it over the alternatives. You might be the first there, Richard. 🙂

@RichardSiddaway ConvertFrom-String is discussed here https://github.com/PowerShell/PowerShell/issues/726


Fixing and improving environment for testing (docker/nginx)

While working on issue #1886 ad PR #1887 I've noticed some needs to be done with testing environment:

Allowing nginx to return 200 not 405 (Method Not Allowed) if the rule is not triggered using POST method on static uri / (index), it's important if we want to check output header not the rule id in testing framework rule, ie.
output:
header: 200
it's possible to use set of headers like [200,405] or check assert of 405 instead 200 but it's not clear.

Using .env file with environmental variables loaded by Docker in docker-composer.yaml file for TZ variable. It's important to run proper timezone for log parser of FTW testing framework. It was a little bit confusing because my localhost had got 2 hours time ahead (CEST timezone) and the log parser could not find entries of tests in error.log file during using log_contains id rule asserts approach. Setting proper timezone in .env file and passing TZ variable to environment of container has resolved the issue.

.gitignore .env file and logs/ dir added

@airween: You promised to review this PR at the last project meeting. Can you still do this?

I have been trying to contact with @piotrpazola to ask few thing, and reproduce the issue, but I still failed.

Are you referring to the issue "1." above? You can not reproduce that problem or you do not see the point?
As for "2." and "3.", these seems simple enough from my point of view. Please confirm.

I couldn't checked 1st issue, because the Docker .env file builds an image, which unusable (2nd issue). Eg. it contains CRS 3.2 without tests cases... I would like to clarify the circumstances.

I see. Thank you.

I wouldn't modify the test environment to include nginx config.

Good point, since we want to stick with Apache / ModSec2 for the time being.
@fzipi : But you are OK with the other changes? Namely gitignore and docker compose?

I'm totally fine with those changes in docker-compose and .gitignore.

Hey @piotrpazola , we were thinking on splitting this PR in two:

we keep the .gitignore and docker-compose changes in this one
we move the nginx change to the docker repo in https://github.com/coreruleset/modsecurity-docker

What do you think?

Meeting decision monthly chat Jan 2020:
No news from the contributor. We're taking this into our hands and @fzipi will perform the split.

Meeting decision monthly chat Jan 2020:
No news from the contributor. We're taking this into our hands and @fzipi will perform the split.

I'm waiting on #1936 to be merged, to do a couple changes in this PR.

I'm waiting on #1936 to be merged, to do a couple changes in this PR.

I've created PRs #1994 and #1995 to add the functionality to add testing.
The change on configuration for nginx I don't think it belongs here, as the backend is the one that should be able to answer using 200.
In the new change introduced in #1936, you can POST to /post and it will always return 200 (courtesy of https://httpbin.org/).

I've created PRs #1994 and #1995 to add the functionality to add testing.
The change on configuration for nginx I don't think it belongs here, as the backend is the one that should be able to answer using 200.
In the new change introduced in #1936, you can POST to /post and it will always return 200 (courtesy of https://httpbin.org/).


THE "Connecting Down!!!" ERROR

I try to flood a website but the script always notice that "Connecting Down!!!" although the website does not down.


DCOS-50259: Possible exception in the Services Form Constraints reducer

Check if a variable exists before trying to
acccess its property.
Closes https://jira.mesosphere.com/browse/DCOS-50259
Testing
Verify that the added checks make sense for the given sentry error.
Verify that the added test makes sense.
Trade-offs
None.
Dependencies
None.
Screenshots
None.

@pierrebeitz ,  For me in this case it's not worth it to invest time into investigating an edge case that was only in 1.12 and stopped appearing three months ago. But if you have an idea how we can learn more about this, I would be glad to pair.

@GeorgiSTodorov 	ok, i can see your point. why are we fixing something in master, if we have only seen this error for 1.12? i'd personally would go with rather not silently swallowing an error and just closing the issue then.

@nLight suggested that if something can still happen on master, we could take care of it.

it happens when you e.g. add an empty object in constraints via the JSON-editor: constraints: [{}].
we should definitely think of using decoders for those inputs at some point in time. i'm convinced that it's not worth the effort to make for a proper error message.
the bad news is that the form still crashes - even with this fix.

I will take a look.

@pierrebeitz , I tried adding such an object in the jobs JSON form and it didn't crash on master. Can you please give me more detailed reproduction steps?

here's it:

fortunately i retested on your branch as well and it seems to work. sorry for the hassle!

Okay, you were using the services form.

@pierrebeitz , thank you for figuring out the real world scenario where this happens and testing it.

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


System test

Added a script that is able to create configuration by a command-line interface for the nodes, masters and cryptoki for testing purposes.

It may be good, and will probably need it once we automate the installation to have an --output-dir flag to set where to write the generated files. @franchoco ?

I agree with you @fmontoto. @DanielAviv we need an --output-dir flag to choose where to write the config files


[WIP] 2019 09 workshop markups

A bunch of changes to the notebooks and test framework.
I can separate the test framework commits into their own PR if that helps.

@elichai - mind reviewing?

Rebased on master and applied Elichai's review comments.

Changed the manual nonce assignment per elichai's suggestion.
There was also a bug in the ECPubKey.negate() method, which I fixed.

Rebased on master and applied a few minor fixes

This is ready for review

I'm going to go ahead and merge this now


Optimize Write-Log function

Write-Log -Summary 'NAME' -Message|Log [Object[]]

Almost ready.
Need to investigate why env is not indented https://github.com/Ash258/GithubActionsBucketForTesting/runs/171321007


"Report this Resource" Button

Resource landing page needs a button allowing users to report abuse of the system via spam resource creation.

Related: report this comment https://github.com/hydroshare/hydroshare/issues/1213

Closing, stale, covered in other initiatives


[New] Add Objective-See Dylib Hijack Scanner 1.3.1

Dylib Hijack Scanner
Dylib Hijack Scanner or DHS, is a simple utility that will scan your computer for applications that are either susceptible to dylib hijacking or have been hijacked.

https://objective-see.com/products/dhs.html
If there’s a checkbox you can’t complete for any reason, that's okay, just explain in detail why you weren’t able to do so.
After making all changes to the cask:

[X] brew cask audit --download {{cask_file}} is error-free.
[X] brew cask audit --strict {{cask_file}} is error-free.
[X] brew cask style --fix {{cask_file}} reports no offenses.
[X] brew cask style --fix --strict {{cask_file}} reports no offenses.
[X] The commit message includes the cask’s name and version.

Additionally, if adding a new cask:

[X] Named the cask according to the token reference.
[X] brew cask install {{cask_file}} worked successfully.
[X] brew cask uninstall {{cask_file}} worked successfully.
[X] Checked there are no open pull requests for the same cask.
[X] Checked that the cask was not already refused in closed issues.

You did not follow the token reference.
dhs.

noted
the problem is, that it's very hard to find...
tyr:~ benc$ brew cask search dylib
No Cask found for "dylib".

so while the other Objective-See applications are easy to find:
tyr:~ benc$ brew search kextviewr
Caskroom/cask/kextviewr
tyr:~ benc$ brew search knockknock
Caskroom/cask/knockknock

Their silly naming of the .app makes it almost impossible to find.
I see that in issues:open you have a whole thread #28165 about Objective-See from the same day you merged dhs.rb. Without searching the name-space no one will ever find this, as @miccal pointed out.


Add tests for executing wasm-bindgen over invalid inputs

Right now we've got a lot of tests for #[wasm_bindgen] and the CLI tool on valid inputs, but don't have any tests for invalid inputs! We have some tests for errors that the attribute itself emits, but we have no tests for errors that the CLI tool emits, such as with multiple start functions active.
We should add such tests in one way or another!

This is now done in this directory, so closing.


page_token parameter documentation is misleading

The page_token parameter to several api functions such as list_projects and list_jobs is documented as follows:

opaque marker for the next "page" of projects. If not passed, the API will return the first page of projects.

This is very misleading, as these functions return an HTTPIterator which if iterated on will seamlessly return multiple pages of results.
Only though experimentation did I determine that multiple pages of results are returned and that if I did want to make use of page_token I'd need to access it at the next_page_token of the  HTTPIterator.
I think the documentation should be updated to better reflect that multiple pages can be fetched without touching the page_token and possibly include where to access page_token if someone does need to use it.

@mackenzieATA Can I safely assume you're referring to BigQuery?
Regarding documentation, @jonparrott I can't seem to find where the iterators doc is. IIRC when it moved to google.api.core, it became undocumented, to be re-documented at a later date?

Sorry, yes, BigQuery. In particular I'm reading the parameter documentation in google/cloud/bigquery/client.py


Provision from locally stored resources when there is no wifi

One problem I experienced with drupal-lamp while traveling was that I couldn't provision when there was no wifi available.
Would be terrific if vampd would store its component libraries locally to allow a user to provision from those locally stored resources when there is no wifi.

Hey Tim -
I'm just back from Cuba (where I went to participate in a triathlon) and I
see that newmedia has put its drupal-lamp to sleep. Having some trouble
with vampd (can't make directories writable in the vbox, like
sites/default/files, can't use drush in the one Drupal 6 site I still use)

can I ply you with beer or coffee and ask you for help?

On Thursday, November 6, 2014, Tim Whitney<EMAIL_ADDRESS>wrote:

So I agree that this is needed, but I am not sure how feasible this is
since a lot of the dependencies are downloaded onto the machine and that is
quite a bit of resources.
So there are 2 cases:

You have a good wifi connection to start. You do a fresh up, get all
the data the box etc right then and there, and then you go into a location
with no internets or very little.

You have a bad connection and that is all you have to work with.

The first one there is a nice work around. Once you have the information
you are realistically good to go with very little internet (assuming you
are a master at the drupal API and have everything memorized :-) ) The
catch is to never re-provision your machine. Halt and sleep it, but just
run the commands internally for testing. For example: running drush si
will wipe a database and reinstall the site. The trick is making sure your
commands are the same. I could forsee a script that you can run that would
mimic the provisions install command. The other example is an update.This
can be done by running the command . /root/site_name-update.sh. This will
wipe the db, import an existing db and then run drush updb on your site.
The second one is a lot harder to reconcile because of the size of the
boxes we are using. While git commands are small, that initial grab of the
box/recipes/ etc really depends on the internet connection. But I can't see
a way around this.
—
Reply to this email directly or view it on GitHub
https://github.com/vampd/vampd/issues/8#issuecomment-62093455.

--
--
Jordan Graham
HandsomeDog Studio
http://handsomedogstudio.com
720.297.8002
http://www.facebook.com/HandsomeDogStudio
https://twitter.com/jordanlgraham

Hey There,
So yes, nmd has put drupal-lamp to bed and are redirecting here. Huzzah!
This seems like a combination of multiple of issues. Lets break it down.

Having troubles making directories writable in the vbox?

There are a couple things that are going on possibly:  so we'll need to know what the issue is directly and when.

Did you install and run the example recipe?
Can you provision successfully?
Does the drupal 6 site provision?
Have you done a git pull lately to grab the latest?

If all of those are yes, and you have provisioned and the site is running but you can't right, you can hit the script at vagrant ssh, sudo su, and . /root/[site_name]_files.sh

Drush not working. What's going on? Have you sudo su?

Thanks so much for your note. What's your email address these days? I find
myself emailing you through github.

Install and run the example recipe - yup! Works like a charm. Drush
fully functional; here's output from 'drush st'
http://pastebin.com/yLRJmf7s
My Drupal 7 sites are provisioning properly; only issue that I have
with them is the universal permissions issue I'm having in which files /
directories are owned by 'vagrant', and 'sudo chown -R www-data
[directory_name]' returns no errors but also doesn't change the ownership
The Drupal 6 site provisions well until the first drush command; I
don't have a functional Drush environment in the Drupal 6 docroot (here's
output from 'drush st' http://pastebin.com/eHe89Q8G). I get the error
that says that I have to run drush from a more functional environment
I merged the latest master from github last night

Mysql works fine. I can 'vagrant ssh'. I can 'sudo su' and 'bash
/root/[site]-files.sh', but 'ls -l' still shows 'vagrant' as the owner and
group.
--
Jordan Graham
HandsomeDog Studio
http://handsomedogstudio.com
720.297.8002
http://www.facebook.com/HandsomeDogStudio
https://twitter.com/jordanlgraham
On Tue, Feb 3, 2015 at 8:31 AM, Tim Whitney<EMAIL_ADDRESS>wrote:

Hey There,
So yes, nmd has put drupal-lamp to bed and are redirecting here. Huzzah!
This seems like a combination of multiple of issues. Lets break it down.

Having troubles making directories writable in the vbox?

There are a couple things that are going on possibly: so we'll need
to know what the issue is directly and when.

Did you install and run the example recipe?
Can you provision successfully?
Does the drupal 6 site provision?
Have you done a git pull lately to grab the latest?

If all of those are yes, and you have provisioned and the site is
running but you can't right, you can hit the script at vagrant ssh, sudo
su, and . /root/[site_name]_files.sh 1) Drush not working. What's
going on? Have you sudo su?

—
Reply to this email directly or view it on GitHub
https://github.com/vampd/vampd/issues/8#issuecomment-72670449.


Unifi UXG Pro (UniFi Gateway Pro) Cannot Start / Error

On the UniFi Gateway Pro I am running the following command to install which is successful :
sh -c 'sh -c "$(curl -sL https://api.controld.com/dl)"'

System Info

OS Type      : linux

OS Vendor    : ubios

OS Version   : <IP_ADDRESS>35

Router Model : UniFi NeXt-Gen Gateway PRO

Arch         : aarch64

CPU          : Cortex-A57

Free RAM     : 323 MB / 1997 MB

Install Details

Binary URL   : https://assets.controld.com/ctrld/linux/arm64/ctrld

Install Path : /data/controld

Install binary and run it? (y/n): y

Starting download
Making binary executable
Launching /data/controld/ctrld

However, viewing the config file located in /etc/controld/ctrld.toml the default port seems to still be setup (not 5354 as per the discussions) :
[listener]
[listener.0]
ip = '<IP_ADDRESS>'
port = 53
After changing the port to 5354 and attempting to start the service I am seeing the following error :
failed to get default route interface error="defaultRouteFromNetlink: Dial: setsockopt: protocol not available
Are there any ideas on what can be tried next, or is this router type not being setup correctly?

Are you using it with a ctrld upstream? If so, you should run the full installer command from the web panel (after creating a Ubiqiti Device), which includes your resolver ID in the command flags. This will start the service automatically and template the correct things into the config.
If you're editing the config manually, you're responsible for resolving listener conflicts.

At this point I am only using the default configuration (which uses ctrld upstreams by default). I was following as per the details :
Supported Routers
You can run ctrld on any supported router, which will function similarly to the Service Mode mentioned above. The list of supported routers and firmware includes:
......
ctrld will attempt to interface with dnsmasq whenever possible and set itself as the upstream, while running on port 5354. On FreeBSD based OSes, ctrld will terminate dnsmasq and unbound in order to be able to listen on port 53 directly.
It was not clear that in order for this to actually work by default that the next section in the docs "Control D Auto Configuration" needed to also be done. I assumed that when attempting to start the service that it would create a basic configuration that would work, not a broken one (like when running on a machine) - that's not the case now that I have read your comment.

I do agree the default generated config should work "out of the box".  We will make it so in the next update.
That being said, editing the default config to use port 5354 (or any other non-conflicting port) will make it work on a default USG install with no conflicting software running.
root@ubnt:~# host dolohen.com
dolohen.com has address <IP_ADDRESS>
root@ubnt:~# cat /etc/controld/ctrld.toml
[listener]
  [listener.0]
    ip = '<IP_ADDRESS>'
    port = 12345

[network]
  [network.0]
    name = 'Network 0'
    cidrs = ['<IP_ADDRESS>/0']

[upstream]
  [upstream.0]
    name = 'Control D - Anti-Malware'
    type = 'doh'
    endpoint = 'https://freedns.controld.com/p1'
    bootstrap_ip = '<IP_ADDRESS>'
    timeout = 5000

  [upstream.1]
    name = 'Control D - No Ads'
    type = 'doq'
    endpoint = 'p2.freedns.controld.com'
    bootstrap_ip = '<IP_ADDRESS>'
    timeout = 3000
root@ubnt:~# ctrld start -vv
Aug 16 16:41:14.000 INF loading config file from: /etc/controld/ctrld.toml
Aug 16 16:41:14.000 DBG cleaning up router before installing
Aug 16 16:41:14.000 NTC Starting service
Aug 16 16:41:14.000 DBG waiting for ctrld listener to be ready
Aug 16 16:41:22.000 DBG ctrld listener is ready
Aug 16 16:41:22.000 DBG performing self-check
Aug 16 16:41:22.000 DBG self-check against "verify.controld.com" succeeded
Aug 16 16:41:22.000 NTC Service started
Aug 16 16:41:22.000 DBG NetworkManager is not available
Aug 16 16:41:22.000 DBG setting DNS for interface iface=eth0
Aug 16 16:41:22.000 DBG dns: [rc=unknown ret=direct]
Aug 16 16:41:22.000 DBG dns: using "direct" mode
Aug 16 16:41:23.000 DBG setting DNS successfully iface=eth0
root@ubnt:~# host dolohen.com
dolohen.com has address <IP_ADDRESS>
dolohen.com has IPv6 address ::
root@ubnt:~# netstat -tupln
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 <IP_ADDRESS>:80              <IP_ADDRESS>:*               LISTEN      2900/lighttpd
tcp        0      0 <IP_ADDRESS>:39443           <IP_ADDRESS>:*               LISTEN      2931/redirector
tcp        0      0 <IP_ADDRESS>:53              <IP_ADDRESS>:*               LISTEN      30649/dnsmasq
tcp        0      0 <IP_ADDRESS>:22              <IP_ADDRESS>:*               LISTEN      3083/sshd
tcp        0      0 <IP_ADDRESS>:12345         <IP_ADDRESS>:*               LISTEN      29821/ctrld
tcp        0      0 <IP_ADDRESS>:443             <IP_ADDRESS>:*               LISTEN      2900/lighttpd
tcp        0      0 <IP_ADDRESS>:55523       <IP_ADDRESS>:*               LISTEN      2896/telnetd
tcp        0      0 <IP_ADDRESS>:39080           <IP_ADDRESS>:*               LISTEN      2931/redirector
tcp6       0      0 :::80                   :::*                    LISTEN      2900/lighttpd
tcp6       0      0 :::53                   :::*                    LISTEN      30649/dnsmasq
tcp6       0      0 :::22                   :::*                    LISTEN      3083/sshd
tcp6       0      0 :::443                  :::*                    LISTEN      2900/lighttpd
udp        0      0 <IP_ADDRESS>:5353            <IP_ADDRESS>:*                           29821/ctrld
udp        0      0 <IP_ADDRESS>:5353            <IP_ADDRESS>:*                           29821/ctrld
udp        0      0 <IP_ADDRESS>:41489           <IP_ADDRESS>:*                           737/rsyslogd
udp        0      0 <IP_ADDRESS>:10001           <IP_ADDRESS>:*                           2841/mcad
udp        0      0 <IP_ADDRESS>:1812            <IP_ADDRESS>:*                           715/freeradius
udp        0      0 <IP_ADDRESS>:1813            <IP_ADDRESS>:*                           715/freeradius
udp        0      0 <IP_ADDRESS>:1814            <IP_ADDRESS>:*                           715/freeradius
udp        0      0 <IP_ADDRESS>:53              <IP_ADDRESS>:*                           30649/dnsmasq
udp        0      0 <IP_ADDRESS>:12345         <IP_ADDRESS>:*                           29821/ctrld
udp        0      0 <IP_ADDRESS>:67              <IP_ADDRESS>:*                           2613/dhcpd3
udp        0      0 <IP_ADDRESS>:68              <IP_ADDRESS>:*                           2960/dhclient
udp        0      0 <IP_ADDRESS>:39766           <IP_ADDRESS>:*                           2841/mcad
udp        0      0 <IP_ADDRESS>:123         <IP_ADDRESS>:*                           2537/ntpd
udp        0      0 <IP_ADDRESS>:123          <IP_ADDRESS>:*                           2537/ntpd
udp        0      0 <IP_ADDRESS>:123           <IP_ADDRESS>:*                           2537/ntpd
udp        0      0 <IP_ADDRESS>:123             <IP_ADDRESS>:*                           2537/ntpd
udp        0      0 <IP_ADDRESS>:44451           <IP_ADDRESS>:*                           715/freeradius
udp        0      0 <IP_ADDRESS>:18120         <IP_ADDRESS>:*                           715/freeradius
udp6       0      0 :::53                   :::*                                30649/dnsmasq
udp6       0      0 fe80::72a7:41ff:fef:123 :::*                                2537/ntpd
udp6       0      0 ::1:123                 :::*                                2537/ntpd
udp6       0      0 fe80::72a7:41ff:fef:123 :::*                                2537/ntpd
udp6       0      0 :::123                  :::*                                2537/ntpd
root@ubnt:~#

Hi,
Please try the new dev build, it should fix the issue. Default rendered config will now work as is. Use the installer below to download the dev build.
sh -c 'sh -c "$(curl -sSL https://api.controld.dev/dl)"'

This should be fixed in v1.3.1 release.


Can't seem to install galileo-io on latest edison image

I just reflashed a new intel edison image and configure wifi and whatnot. I can install other node packages, like johnny-five. But when it comes to galileo-io (or edison-io), I always get an error. Any ideas how I might be able to resolve this?
When I run:
npm install -g galileo-io
I get the following error:
npm ERR<EMAIL_ADDRESS>postinstall: node scripts/postinstall
npm ERR! Exit status 255
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script.
npm ERR! This is most likely a problem with the galileo-io package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node scripts/postinstall
npm ERR! You can get their info via:
npm ERR!     npm owner ls galileo-io
npm ERR! There is likely additional logging output above.
npm ERR! System Linux 3.10.17-poky-edison+
npm ERR! command "node" "/usr/bin/npm" "install" "-g" "galileo-io"
npm ERR! cwd /home/root
npm ERR! node -v v0.10.38
npm ERR! npm -v 1.4.28
npm ERR! code ELIFECYCLE
npm ERR! not ok code 0
Thanks
Gary

Sorry. I found the workaround (https://github.com/rwaldron/galileo-io/issues/36). Thanks

What version of node/npm did you hit this on? Also what is the version number for "latest edison image"?

node version: v0.10.38
npm version: 1.4.28
edison version: 159
The edison image was obtained from the all-in-one installer for Mac OS X. I got the installer from https://software.intel.com/en-us/iot/hardware/edison/downloads. After re-installing the new image, I used XDK to update the on-board libraries and the xdk-daemon before trying to install galileo-io (or edison-io).


lorri Crash Report

Describe the bug
The lorri daemon crashed, yielding the attached crash report from three threads:

Metadata

reports.zip

$ lorri info --shell-file shell.nix
lorri version: 1.5
GC roots exist, shell_gc_root: /Users/chris/Library/Caches/com.github.nix-community.lorri.lorri.lorri/gc_roots/d44ed7205e17d524d463782543f64e72/gc_root/shell_gc_root

$ uname -a
Darwin ume.local 21.3.0 Darwin Kernel Version 21.3.0: Wed Jan  5 21:37:58 PST 2022; root:xnu-8019.80.24~20/RELEASE_X86_64 x86_64 i386 Darwin

This bug is fixed in 1.7.0, which is in nixpkgs as of NixOS 24.05. Thank you for your patience!


suggestion: make observable shallow by default.

When you make an array observable:
@observable foo: [];

... and assign it a value:
foo = [ { bar: 1, baz: ClassType } ];

...the baz value becomes a setter/getter implicitly, so saying something like:
new foo[0].baz()

Ends up being broken and not what you expect. This is because mobservable is recursing through added things and implicitily observable-ifying them.
Instead what would be more intuitive would be to do shallow observation by default, with optional recursive behavior:
@observable foo: any;

// This only fires change events when the foo is assigned a new instance.

foo = {}; // mutates
foo.a = true; // doesn't mutate a by default

Then, if we want foo to recurse, we explain that explicitly:
@observable({ recurse: true }) foo: []; // Does the recursive thing, so saying foo[0].bar = 2 mutates foo.
foo = { a: false }; // mutates, but also instruments the object
foo.a = true; // mutates foo

Arrays in particular are a bit ambiguous and I could go either way. I think i'm ok mutating a vanilla array into an observable array by default, but I'm not keen on going any farther without an opt in behavior.
@observable foo: any[];

foo = []; // mutates foo
foo.push({}); // mutates foo
foo[0].bar = true; // doesn't mutate foo

... but you could opt in of course, to recurse.
Though, a more pure solution would be to require wrapping an array with an observable to make it observable.
foo = observable([]);

I would rather you not break the current API, and just do @shallowObservable

makes sense to me.

I really like the notion of @shallowObservable.
Besides that I'll add this issue for general reconsideration in a 2.0 api

Closed in favor of the discussion in #211


Light color theme?

I belong to the minority who prefers light terminal background color. Do you have a light theme too? It would be nice if we could choose between a dark and a light color theme easily.

hey @jabbalaci
Yes, we do! Log uses Lipgloss to automatically detect background color. You can customize and adapt the default colors to your liking. Refer to styles.go for more info.
These are the default colors on a light background:

Excellent, thank you! Please mention in the README that you have light theme support too.