Local issuer certificate error with sfcc-ci npm install

sfcc-ci Version
2.11
NodeJS Version
10.23
sfcc-ci Path
No response
Host OS Details
No response
What happened?
We are trying to do npm install where we have sfcc-ci as a dependency in the package.json
"sfcc-ci": "SalesforceCommerceCloud/sfcc-ci#v2.11.0"
npm is throwing an error while installing sfcc-ci dependency. It is failing at prepare: npm run synk-protect. We have tried with the later versions of node, but no luck.
At the end it should NOPACKAGEJSON error even through repo contains the package.json

Anyone faced this issue?
Relevant log output
No response

Hi @rpillamerkle, in the screenshot it says version v2.6.0, whereas in the description you say v2.11.0. Can you clarify please?
In current master (precisely in commit https://github.com/SalesforceCommerceCloud/sfcc-ci/commit/d6e64578f4cceeab7f8c8285ccd5a5307d75e6c6) there is a change related to snyk protect. Just to verify: can you depend from that and see if the npm install is working fine then?

@tobiaslohr Thanks for the reply. I was just trying different versions. So, the same error shows up for both the versions. We have used the commit version that you mentioned, the error shows up for that version as well.

The versions are a bit confused because this is being asked on behalf of multiple people with some differences of versions. I was the first, and I have ci 2.11 and node 12.22.12, while another has ci 2.6 and node 10.23. The errors are identical, however.
I've also tried installing 2.11 globally and using "sfcc-ci client:auth" It gives basically the same error with a slightly different trace:
Error: Authentication failed: Error: unable to get local issuer certificate
at TLSSocket.onConnectSecure (_tls_wrap.js:1502:34)
at TLSSocket.emit (events.js:314:20)
at TLSSocket._finishInit (_tls_wrap.js:937:8)
at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:711:12) {
code: 'UNABLE_TO_GET_ISSUER_CERT_LOCALLY'
}


Allow parentheses in operator method calls for Style/MethodCallWithArgsParentheses

While calls like data&.[] value, value.=== other do compile, I won't
blame people if they want to leave the parentheses so they know what's
going on.
I'm proposing we legitimize the parens when calling operator methods.  I
don't think this deserves extra configuration.

The change is fine, but it should be reflected in the cop documentation via some examples, otherwise I don't think the users will figure out how this works. And you have to move that changelog entry. :-)

Thanks!


Add basic Travis config

Closes #4

My git-fu failed and this did not automatically close. Sorry! But it's merged: https://github.com/DomainGroupOSS/accounts-autocomplete/commit/a9be78dedc140d6c2af6349a149dd871260d531b


edge labels do not appear on the graph

Hi
I have loaded the plugin sigma.renderers.edgeLabels.min.js
Running OSX el-capitan, chrome, safari, firefox
the labels still do not appear on the graph.
Running windows, chrome : same code -> the edge labels DO appear.
Any idea where the difference lies?
Thanks
Best

is there a piece of software missing on unix/osx that would be needed? or is it browser issue?
thks

Hello @gdem123, could you please share the incriminated code with us so we can check if there are compatibility issues?

Thank you.
Here is the code :
difficulty to see the edge labels despite the plugins.  works on some browsers (windows and not all the time…) not on OSX
the graph has edges that cross very far from one another : any way to make them closer to each other and edges not crossing?
I have to state that I am working with flask/ jinja2 templates if it has an impact.
Best,

NODES

 Elements of proposition

 Proposition

 <br>

 EDGES

 Has Need

 Has Solution

 Has Criteria

gdem123

On 06 Sep 2016, at 09:37, Guillaume Plique<EMAIL_ADDRESS>wrote:
Hello @gdem123 https://github.com/gdem123, could you please share the incriminated code with us so we can check if there are compatibility issues?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/jacomyal/sigma.js/issues/762#issuecomment-244872853, or mute the thread https://github.com/notifications/unsubscribe-auth/AIebRJWjUcOYlmajbw4Ph6Iukhq4JrMOks5qnRhRgaJpZM4JvSwB.


Feature: Redstone Power Event

I suggest an event that fires whenever the redstone power level of a block changes.
Information that should be provided:

Old power level
new power level
maybe: source/direction of the change.

Which blocks:

All redstone related blocks
but also "powered" blocks, i.e. opaque blocks with a redstone flow into them (example current: repeater/dust->block->redstone torch)

From what I read so far ther have been some ways to do it (e.g. NotifyNeighborBlockEvent) but this implementation did not seem to work in v7 anymore (or not yet due to the recent major changes)
Related discussions:

https://forums.spongepowered.org/t/redstone-power-data-on-non-redstone-blocks/10932

On source, whilst this would be amazing (this’d make some things sooo much easier), it requires adding event hooks throughout a tonne of places in the code.

Oh man, Please tell me you only want the event fired when it's stabilized to a power level?
Otherwise you could be getting a lot more events then you bargain for.

For my use case awaiting a stabilized power level would be sufficient.
My use case does not involve "flickering" currents / "redstone clock generators".
But maybe there are other use cases that would justify more granular Events, e.g. plugins that want to fiddle with the redstone mechanics itself, chaning currents or whatever.
Meaning: For me it would be sufficient to have "stabilized" redstone events, but if someone might work on this, then it might make sense to also consider more ambituous usecases. Maybe resulting in something like a frequent RedstoneChangeEvent and a less frequent RedstoneChangeStabilizedEvent

My use case does not involve "flickering" currents / "redstone clock generators".

This isn't what I meant, it would still trigger for clocks etc.
By stabilized I mean when depowering a redstone wire, it goes from states 15-0 and notifies all neighbours for each step.

You should already have this in ChangeBockEvent considering the sources are either BlockSnapshots or LocatableBlocks, and the Trasaction<BlockSnapshot>.
Unless I'm mistaken about the proper use of the event itself in the circumstance of red stone exchanges.

I suspect it's more likely to be https://github.com/SpongePowered/SpongeAPI/blob/bleeding/src/main/java/org/spongepowered/api/event/block/NotifyNeighborBlockEvent.java
@gabizou I believe the user story is to create custom redstone reactive things.
e.g. someone builds a multiblock machine out of iron, a block with no native redstone capability, so there is no ChangeBlockEvent.
Neighbour Notify would be applicable, but man the spam of filtering for known locations of these fake  machines would be real.

"but this implementation did not seem to work in v7 anymore" is the real problem, was it removed by design, or as a side effect of the cause refactor?

Regardless, I do wonder if we could have a better user story for this that won't cause such a performance drain.


Add README file listing flake8 violations defined

I really like the idea of this plugin as a short term solution until black https://github.com/psf/black/issues/26 is fixed.
I would encourage you to add a README file including an example showing what the flake8 error code prefix you are using is (recommended three letter, three number format, e.g. ABC001 to reduce the chance of duplicate codes between plugins). In your case, ISC as a prefix make sense to me.

I see you are working on this in #2, and have included pip install flake8-implicit-str-concat which I forgot to suggest 👍

I filed #3 on the wider issue of not using an alphanumeric flake8 violation code

now that #3 has landed, I'd love to see a PR with this added!


Added heartbeat and threading options to check-rabbitmq-amqp-alive

Pull Request Checklist
Is this in reference to an existing issue?
No
General

[x] Update Changelog following the conventions laid out on Keep A Changelog

[x] Update README with any necessary configuration snippets

[X] RuboCop passes

[X] Existing tests pass

Purpose
This adds the ability to set the heartbeat interval on the Bunny client as well as threaded. This becomes desirable when the rabbit server has heartbeats disabled and causes race conditions on connection open and subsequent close.
Known Compatibility Issues
None. Default options on new arguments are the defaults for rubyBunny.

This looks good, I want to merge this after I merge the refactor in #71 which I will get to this weekend as I want to do some testing to make sure it does not break everything.

absolutely, and within 24 hours of merge.

released: https://rubygems.org/gems/sensu-plugins-rabbitmq/versions/3.4.0


Compare NaN values equal

Fixes Olivine-Labs/busted#453.

LuaJIT succeeds and gets SEGV at exit.

is_same is more analogous to == in C/C++. There really is no analog to memcmp in lua, besides you wouldn't really use memcmp to compare two C++ objects for equality (i.e. memcmp does not perform a deep compare). You would have the same problem if you were to attempt the same comparison in C/C++ or any programming language, it would also perform a floating-point compare for NaN values nested inside a container.
In your case it may be better to create a special table that represents NaN instead.  Replacing numeric NaN with table NaN where appropriate or wrapping your function that may return NaN to return table NaN.

@o-lim In C == does not perform deep comparison either like it does here. Not sure about C++, but I guess it will not without overriding ==. Also note that e.g. authors of numpy know that tests that compare NaN equal are needed: http://docs.scipy.org/doc/numpy/reference/generated/numpy.testing.assert_array_equal.html.
As the alternative it makes sense to either have different is_same version or an optional argument to is_same that makes it compare NaN values equal.

In any case first it is needed to report luajit crash. I do not yet have minimal working example, but can say that:

Removing NaN inside table test makes tests no longer crash.
Running only new tests using --filter=NaN does not make luajit crash. Including running only table test that is required to crash the test suite.

Any updates here?


does not work from pleroma

accounts created on rss-parrot are not visibile by pleroma instances

.

maybe piggo.space the creator accepts signups and he's willing to accept you in.

I'm happy to pursue this if the Pleroma creator reaches out to show interest in working together to track down the issues!

I can follow parrot https://miantiao.me/<EMAIL_ADDRESS>on my instance of pleroma but can't see its updates


Breadth First Search Algorithm (AI)

Have you read the Contributing Guidelines on Pull Requests?
(Write your answer here.)
Yes
Description
(Write your answer here.)
Created a .md file containing the explanation of the Breadth-First Search Algo and a file containing the algorithm.
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
#1693
(Write your answer here.)

@HarshCasper Take a look at this.

@HarshCasper Take a look at this. I guess we should assign contributors to work on the wikipages now.

Sir that's not from a wiki page or any such resource. The explanation/concept of the algorithm has been written by me, and I have been learning AI algorithms for a while now. Didn't add the real implementation, because I haven't studied it yet.
Kindly look into it.

@HarshCasper Take a look at this. I guess we should assign contributors to work on the wikipages now.

Sir that's not from a wiki page or any such resource. The explanation/concept of the algorithm has been written by me, and I have been learning AI algorithms for a while now. Didn't add the real implementation, because I haven't studied it yet.
Kindly look into it.
And as for the algorithm, it's the general algorithm.

I acknowledge that the contributed pseudo codes are your original work, I am just seeking validation from him as we were planning to have dedicated wiki page to document all the algorithms and programs contributed. Personally I don't think that its a nice idea to put the pseudo code and documentation in a folder along with codes.

@HarshCasper Take a look at this. I guess we should assign contributors to work on the wikipages now.

Sir that's not from a wiki page or any such resource. The explanation/concept of the algorithm has been written by me, and I have been learning AI algorithms for a while now. Didn't add the real implementation, because I haven't studied it yet.
Kindly look into it.
And as for the algorithm, it's the general algorithm.

I acknowledge that the contributed pseudo codes are your original work, I am just seeking validation from him as we were planning to have dedicated wiki page to document all the algorithms and programs contributed. Personally I don't think that its a nice idea to put the pseudo code and documentation in a folder along with codes.

Oh. I get it. I am sorry, I misunderstood.😅
I am learning the implementation part and will be soon adding once I am confident with the theory of the algorithms.
Also, consider me in as a contributor for any kind of tech documentations needed.

We don't need to add it now.
I would have considered it, if it was a detailed doc, but here it just a step-wise instruction. We have a resources directory now. Please raise PRs over there if you would like to work on docs and developing resources.
And moreover, ensure that a PR has a corresponding Issue. I am closing it now.

Okay sir, I got it.


Update docs for saved event to be consistent with 'updated' and 'created'

All three event listeners are called with the same arguments, so its just confusing to make the saved parameter have a different name in the docs

So, both the first and the second parameters are "model firing the event"? There must be some difference. Since you're delving into this do you know what the difference is? This could finally fix #1015.

So, both the first and the second parameters are "model firing the event"? There must be some difference. Since you're delving into this do you know what the difference is? This could finally fix #1015.

The first is the bookshelf Model the second is the Model attributes, after having toJSON()ed. All three events have the exact same arguments.
I've been trying to extend Bookshelf with a plugin to fire a 'committed' event after a save in a transaction has committed. I managed to write a version which unfortunately triggers this event when every save in the transaction completes, not the transaction itself. I have since found a better way though
import _ from 'lodash';
import Promise from 'bluebird';

// Committed Plugin
// Emits the 'committed' event on `update` or `insert` when the save transaction completes for all models
module.exports = function(Bookshelf) {
  const proto = Bookshelf.Model.prototype;
  const Model = Bookshelf.Model.extend({
    save: function(key, value, options) {
      let attrs;
      // Handle both `"key", value` and `{key: value}` -style arguments.
      if (key == null || typeof key === 'object') {
        attrs = key || {};
        options = _.clone(value) || {};
      } else {
        (attrs = {})[key] = value;
        options = options ? _.clone(options) : {};
      }
      options.method = this.saveMethod(options);
      const save = proto.save.call(this, attrs, options);

      if (options.transacting) {
        options.transacting.client.on(
          'query-response',
          (response, obj, builder) => {
            console.log(response, obj, builder);
            this.triggerThen('committed', this, attrs, options);
            options.transacting.emit('query-response', response, obj, builder);
          }
        );
      } else {
        save.tap(model => this.triggerThen('committed', this, attrs, options));
      }

      return save;
    },
  });

  Bookshelf.Model = Model;
};

Ok, thanks for the info. Can you update your PR to include that information? I ask because having the first two arguments being "model firing the event" isn't correct.


Add Cursor as easy

Closes #2241

Thanks for all these contributions, including picking up some issues!


Client doesn't need to be mutable, fix table_names

LGTM, but just as a side-note, we probably want to add a similar (if not identical) example into the root rustdoc for the project, so that when the code needs to be updated, the tests will tell us.

Thank you!


Add type overload for Push.Permission.request()

Fixes #243

@Jicmou Thank you for this.
There seems to be a test failing. Can you look into it please.
@Nickersoft LGTM. Can be merged.

@theLufenk  Thanks for approving.
I can reproduce the failing CI on master. Run the following commands:
npm run test
// passing
npm run build
// builds sucessfully
npm run test
// failing

I ran the first two commands before commiting, as stated in the CONTRIBUTING.md, Travis ran the third.
I could submit my PR without the build though, as index.d.tshas no impact on the build.

@Nickersoft Over to you.

nudge @Nickersoft


Interoperability  issue with other l4z libraries

I'm using two github versions of lz4: yours for java and github.com/bkaradzic/go-lz4  for Golang.
I used Golang version in the code below:
package main

import (
	lz4 "github.com/bkaradzic/go-lz4"
	"fmt"
	"os"
	"encoding/base64"
)

func main() {
	var data []byte
	var err error

	to_compress:="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"

	if data,err=lz4.Encode(nil,[]byte(to_compress)); err!=nil {
		fmt.Fprintf(os.Stderr,"Failed to compress: '%s'",err)
		return
	}

	fmt.Fprintf(os.Stderr,"Success! Length=%d\n",len(to_compress))

	fmt.Fprintf(os.Stdout,"%s\n",base64.StdEncoding.EncodeToString(data))
}

and obtain following output:
raffi@iot-micro-raffi ~/tmp > go run ./test_lz4.go
Success! Length=100
ZAAAAB94AQBLUHh4eHh4
raffi@iot-micro-raffi ~/tmp >

Then I inject this output into a Java version below using your library to decode the result:
import java.util.Base64;
import net.jpountz.lz4.LZ4Factory;
import net.jpountz.lz4.LZ4FastDecompressor;

public class test_lz4_decomp {

    public static void main(String[] args) {
        String compressed_base64= "ZAAAAB94AQBLUHh4eHh4";
        int original_size = 100;
        byte [] compressed = Base64.getDecoder().decode(compressed_base64);

        LZ4Factory _factory= LZ4Factory.fastestInstance();
        LZ4FastDecompressor decompressor = _factory.fastDecompressor();
        byte []restored = new byte[original_size];
        decompressor.decompress(compressed, 0, restored, 0,original_size);

        String decompressed_str=new String(restored);

        System.out.println(decompressed_str);
    }

}

but obtain the following output:
raffi@iot-micro-raffi ~/tmp > java -cp ".:lz4-1.3.0.jar" test_lz4_decompException in thread "main" net.jpountz.lz4.LZ4Exception: Error decoding offset 58 of input buffer
	at net.jpountz.lz4.LZ4JNIFastDecompressor.decompress(LZ4JNIFastDecompressor.java:39)
	at test_lz4_decomp.main(test_lz4_decomp.java:16)
raffi@iot-micro-raffi ~/tmp >

The expected result would be that the Java version should be able to decompress the output of the Golang version.

I used another Golang library (https://github.com/pwaller/go-clz4) and succeeded to make it work with your library.
So I believe the issue was in the golang library.
Thanks for your nice work!


Uploaded GoPro image sequence is in incorrect order

Hello!
I have tried to upload a couple of sequences I've taken with my GoPro Hero 8 Black shooting 0.5s timelapse mode, and the resulting tracks' orderings exhibit a three steps forward, one step back pattern as can be seen on this image:
One of the sequences in question
Is it possible that the GPS Time EXIF field is rounded to whole seconds, so the images taken within the same second get swapped? I will try a 1s interval on my next trip and report back with the results.
A sample of the raw images:
G0067200.jpg
G0067201.jpg
G0067202.jpg

I have uploaded a new sequence with a 1s interval, and now the order seems to be good.

thanks for the contribution!


5.6.0 gives error if your not setting the "optional" values

The values in the values.yaml file as well as the comments suggest that these values are optional
https://github.com/lacework/helm-charts/blob/80f998e6d6766a5141aa9c6eab2c946cd868c3b3/lacework-agent/values.yaml#L38-L51
These values are required in the schema file
https://github.com/lacework/helm-charts/blob/80f998e6d6766a5141aa9c6eab2c946cd868c3b3/lacework-agent/values.schema.json#L142-L150
So conflicting information here :) are they required or optional ?

Hi @jbiskur, I apologize for the confusion, as you're not the only one that has run into this (#72).
The original intention was that, although the schema file requires that the fields be present, they default to null values, hence the note about them being optional. However, as you and others have noted, when using a values file that does not include a fim object in the laceworkConfig object, the schema checking fails. We hope to have a fix for this shortly and may need to break the existing API for configuring fim.
In the meantime, we do have a workaround documented in more detail here: https://github.com/lacework/helm-charts/issues/72#issuecomment-1135248696

Relates to #96

The four fim properties in question (coolingPeriod, crawlInterval, noAtime, runAt) should either:

Have null removed from their types and a non-null default value added to values.yaml, or
Should be removed from the list of required properties

I have a PR out for review that will remove these fields from being required. We should have this available in the next release of our charts.


Sortable Field doesn't give default values

Hi @aristath
Issue description:

Sortable field return empty string even we set default values. It returns array only after we have made some change in the sortable field.

Version used:
latest develop branch
Using theme_mods or options?
theme_mods
Code to reproduce the issue (config + field(s))
Kirki::add_field( 'my_config', array(
'type'        => 'sortable',
'settings'    => 'sort_aboutpage',
'label'       => ( 'Sort Sections', 'my_textdomain' ),
'section'     => 'sort_about_section',
'default'     => array( 'intro', 'stat', 'mission', 'core', 'client' ),
'choices'     => array(
'intro'   => esc_attr( 'Intro Section', 'my_textdomain' ),
'stat'    => esc_attr__( 'Stat Counter Section', 'my_textdomain' ),
'mission' => esc_attr__( 'Our Mission Section', 'my_textdomain' ),
'core'    => esc_attr__( 'Our Core Values Section', 'my_textdomain' ),
'client'  => esc_attr__( 'Our Client Section', 'my_textdomain' ),
),
) );
In Front End
$sections = get_theme_mod( 'sort_aboutpage', array( 'intro', 'stat', 'mission', 'core', 'client' ) );
Thanks

I don't think there is anything wrong with it. All the fields of customizer ( nothing to do with Kirki) returns empty by default. This looks odd but that is how it is. That is why you need to specify the second parameter for get_theme_mod which you have rightly done.  You can test with any other field.

@manandharsudin theme mods are by default empty, and only have a value after you change them.
Default values are only there to control what will be shown in the controls if no value is set.
Default values however are not saved in the database and they will never be saved because the WordPress Themes Review Team prohibits that (for good reason).
Adding a default value in the get_theme_mod function is mandatory.


calendarDragAndDrop

Hi sir....
In full calendar.js plugin i want to add number of rows and columns(instead of 6x7)....but i unable to identify where can i write the coding to increase rows and columns...can u help where can i add that.
i will be eagerly waiting for your reply
thanking u...
bs narayana

If such feature does exists, you need to search on their repo/forum/site (http://fullcalendar.io/).

Hi!
As @rafael-renan-pacheco suggested, you should ask about this feature on the fullcallendar site. We apologize for the inconvenience!


New opportunity notifications

Hello guys!
I am subscribed for notifications of new opportunities under my Public Sector Employee account. Pretty sure I did not receive a notification about this latest one.

We needed to batch the notification emails that are being dispatched by the government email server. This fix has been implemented and deployed to production. Thanks @mark-a-wilson


Add test coverage with coveralls

We should track and report test coverage.

Submitted and merged PR#44. Closing.


[TechDocs] Docs return 404 on first render with local builder

Expected Behavior
When a doc is built for the first time, it should render successfully after the backend finishes building.
Current Behavior
After the building, request for the newly built docs results in a 404. Refreshing the page afterward loads the docs correctly.
Possible Solution
Not sure, see context below.
Steps to Reproduce

Configure Techdocs with builder: 'local'
Register a new entity with associated Techdocs
Open docs for new entity
Techdocs builds new docs in backend, frontend shows loading indicator
Backend successfully builds docs with logs such as "Step 3 of 3: Publishing docs for entity ..."
Frontend loading completes and shows 404 error
Refresh the page and the docs now loads successfully

Context
I've experienced this both with publisher set to 'local' and 'awsS3' and the docs loads successfully after the first time so I don't think it has anything to do with the artifacts being published in the right location. My suspicion is that there might be some race condition where the frontend makes a request for the docs before they are completely ready.
This also used to work for me so some recent change seems to have introduced this bug. I tried digging into the code and my theory is that it might be due to this change where this request used to redirect to the storageUrl after the docs finished building whereas now (if I understand correctly) the frontend re-attempts to load from the storageUrl after syncing but I couldn't find any concrete explanation/evidence whether this is related to the cause.
Your Environment

builder: 'local'
publisher.type: 'local' or 'awsS3'
NodeJS Version (v12): v14
Operating System and Version (e.g. Ubuntu 14.04): Ubuntu 18.04 LTS
Browser Information: Chrome

This could be due to Async build behavior. The default experience is first load the docs from the storage and then figure out whether it needs update or re-build. This for sure affects the user when they are loading a site for the very first time, which should be addressed. :)

If this is due to the async build behavior would a better message in the UI (than a 404) work? Like showing "docs are currently being built. please check back in a few mins"?
or do we want to fix the behavior where we make the FE wait for the docs build and publish to finish?
cc @ottosichert

I would argue having an async loader is an even better UX than displaying a message. I'll look into the change mentioned above and see if it's a straightforward fix!

https://github.com/backstage/backstage/pull/5975 implements a state machine that correctly handles reloading after the initial build.  Suggesting to go with that approach 👍


Fix #8 - Fixing cuda issues in basic usage text detection

Fixing issue #8
In this quick-fix I referenced craft_net as a global variable. If this is not an acceptable workaround, then consider reorganizing the structure of the code.
Have a nice day :)

Thanks a lot :) Accepting this as a temporary fix, will look into it in more detail.


Support combination of group field and span in stats command

Description

Support combination of group field and span. doc.
Refactor AggregatorOperator implementation.

Remove Group and SpanBucket.
Add Collector.

Breaking Change

Missing Span is ignored. Aligned with OpenSearch Histogram/DateHistogram missing value handling.

Issues Resolved
#395
Check List

[x] New functionality includes testing.

[x] All tests pass, including unit test, integration test and doctest

[x] New functionality has been documented.

[x] New functionality has javadoc added
[x] New functionality has user manual doc added

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #417 (d3142ea) into main (fe20fb1) will decrease coverage by 33.61%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##               main     #417       +/-   ##
=============================================
- Coverage     96.52%   62.91%   -33.62%
=============================================
  Files           265       10      -255
  Lines          7204      658     -6546
  Branches        538      118      -420
=============================================
- Hits           6954      414     -6540
+ Misses          196      191        -5
+ Partials         54       53        -1

Flag
Coverage Δ

query-workbench
62.91% <ø> (ø)

sql-engine
?

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

Impacted Files
Coverage Δ

...ain/java/org/opensearch/sql/analysis/Analyzer.java

...arch/sql/planner/physical/AggregationOperator.java

...earch/sql/planner/physical/collector/Rounding.java

...java/org/opensearch/sql/ppl/parser/AstBuilder.java

...ensearch/storage/system/OpenSearchSystemIndex.java

...arch/storage/script/filter/FilterQueryBuilder.java

...ssion/operator/arthmetic/MathematicalFunction.java

...pensearch/sql/planner/physical/ValuesOperator.java

...search/sql/expression/datetime/CalendarLookup.java

...rch/planner/logical/rule/MergeSortAndIndexAgg.java

... and 243 more

Continue to review full report at Codecov.

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


feat: add bogoSort algorithm in typeScript language

Add type-safe algorithm for bogo-sort (aka. monkey-sort) - typeScript

Hey, Thanks for your contribution. Request, Please share this repository more.


chore(wallet-connect): new release

Added

#671

Tested and verified that:

EIP-1271 support works with the web PRs that have the implementation enabled.
Nothing breaks on prod where the implementation is not yet live.
WC V1 works as usual in prod.
WC V2 works as usual in prod.

Maybe we can add #675 to the release as well and do a 2x1?
Cheers!


Remove obsolete contribution doc

It appears that recent contributions are no longer following the gitflow branching model.

@homu r+

:pushpin: Commit 5d0d239 has been approved by poteto

:hourglass: Testing commit 5d0d239 with merge b206bfe...

:sunny: Test successful - status


E2E - PLP facets

Make sure facets are correctly applied.
When sorting, the products must be correctly sorted. The same for price range and other filters

Is there a E2E pipeline in place with an example I can reproduce? Which data is used?


"Not defined" error when using apollo properties in 3.0 beta

After upgrading from 3.0.0-alpha to 3.0.0-beta.4 the behavior of reactive properties changed in a breaking way:
Code:
export {
  apollo: {
    users: {query: usersQuery}
  }
}
// template:
{{users}}

( users query returns array, pseudo code for demonstration)
This used to work in 3.0 alpha.
In 3.0.0-beta.4 I get the following error in dev console:

Property or method "users" is not defined on the instance but referenced during render. Make sure that this property is reactive, either in the data option, or for class-based components, by initializing the property. See: https://vuejs.org/v2/guide/reactivity.html#Declaring-Reactive-Properties.

Workaround:
export {
  apollo: {
    users: {query: usersQuery}
  },
  data() {
    return {users: null}
  }
}
// template:
{{users}}

Is this new behavior intended or a bug?
Thanks

This is a little diversion but I think it might be related. In the project I'm working on the this.$apollo.queries was empty and on 3.0.0-beta.4 and no requests were being sent to the graphql server. A downgrade to3.0.0-alpha.1 and no changes in code did the trick.
Regarding the upgrade to 3.0, I can't find any docs on what has changed and I spent the entire day trying to figure out how to do queries in 3.0 😢

This new behavior is intended. I had the old one working but wanted to ditch it and now I got a good reason to do so (it doesn't work with the usage of provide/inject - related to lifecycle hooks).
Explicitly declaring the properties initial values in the data hook is a much better practice.


Cannot open Geometry Dash after installation.

After i install this, i launch the game through Steam, and it does not open.

Wait, i did not have microsoft C++ 2015 package


feat: Add multiple bills at a time

Current dependencies on/for this PR:

main

PR #30   👈

This stack of pull requests is managed by Graphite.


Fix missing bracket in the code listing

@doshyt Sorry for the delay, I've been out of the office.  This looks correct, thanks for noticing and contributing the fix, it is much appreciated!
#sign-off


[BugFix] crash when apply in table with AUTO_INCREMENT column (#27176)

problem:
suppose we have a table created by:
and then insert into a new record:
and we have a CSV file with: 1,2,3 and 2,3,4
we want to partial update the v2 and v3, and we will get a crash when we apply.
The reason is that, in the apply phase, we need to get the column id in auto increment to do some work, but the id is incorrect in this case.
Fixes #27176
What type of PR is this:

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.1
[ ] 3.0
[ ] 2.5
[ ] 2.4

[FE PR Coverage Check]
:heart_eyes: pass : 0 / 0 (0%)

[FE PR Coverage Check]
:heart_eyes: pass : 0 / 0 (0%)


Invalid tool calls when using streamEvents and a node calls model.withStructuredOutput()

Hello! When using structured outputs within a node, I am getting back AIMessageChunks containing invalid_tool_calls with an error stating Malformed args. and error type being invalid_tool_call. Following the LangChain docs on .withStructuredOutput() from here and using that in LangGraph, results in AIMessageChunks containing for example:
AIMessageChunk {
  "id": "chatcmpl-AT7lKLldnGMv0PmRhp0xdQwN5934F",
  "content": "",
  "additional_kwargs": {
    "tool_calls": [
      {
        "index": 0,
        "function": "[Object]"
      }
    ]
  },
  "response_metadata": {
    "usage": {}
  },
  "tool_calls": [],
  "tool_call_chunks": [
    {
      "args": "rating",
      "index": 0,
      "type": "tool_call_chunk"
    }
  ],
  "invalid_tool_calls": [
    {
      "args": "rating",
      "error": "Malformed args.",
      "type": "invalid_tool_call"
    }
  ]
}
AIMessageChunk {
  "id": "chatcmpl-AT7pv0xRkHB6QFhe2z5KKTS1AjfuF",
  "content": "",
  "additional_kwargs": {
    "tool_calls": [
      {
        "index": 0,
        "function": "[Object]"
      }
    ]
  },
  "response_metadata": {
    "usage": {}
  },
  "tool_calls": [],
  "tool_call_chunks": [
    {
      "args": "}",
      "index": 0,
      "type": "tool_call_chunk"
    }
  ],
  "invalid_tool_calls": [
    {
      "args": "}",
      "error": "Malformed args.",
      "type": "invalid_tool_call"
    }
  ]
}

The response/output of the chain run is complete and useful, but I noticed these invalid_tool_calls when using .streamEvents(). It does not seem to happen when using .stream(). When not using withStructuredOutput(), everything works as expected. Not sure if this is potentially related to https://github.com/langchain-ai/langgraphjs/issues/470.
Here's an example:
import { Annotation, START, StateGraph, END } from '@langchain/langgraph';
import { BaseMessage, isAIMessageChunk } from '@langchain/core/messages';
import { ChatOpenAI } from '@langchain/openai';
import { z } from 'zod';

const GraphState = Annotation.Root({
  messages: Annotation<BaseMessage[]>({
    reducer: (x, y) => x.concat(y),
  }),
});

const joke = z.object({
  setup: z.string().describe('The setup of the joke'),
  punchline: z.string().describe('The punchline to the joke'),
  rating: z.number().optional().describe('How funny the joke is, from 1 to 10'),
});

const model = new ChatOpenAI({
  model: 'gpt-4o-mini',
  temperature: 0,
  streaming: true,
});

const nodeFn = async (state: typeof GraphState.State) => {
  const responseMessages = await model.withStructuredOutput(joke).invoke(state.messages);

  return { messages: [responseMessages] };
};

const workflow = new StateGraph(GraphState).addNode('node', nodeFn).addEdge(START, 'node').addEdge('node', END);

const app = workflow.compile();

const stream = app.streamEvents(
  { messages: [{ role: 'user', content: 'Tell me a joke about cats.' }] },
  { version: 'v2' },
);

for await (const { event, data } of stream) {
  if (event === 'on_chat_model_stream' && isAIMessageChunk(data.chunk)) {
    console.log(data.chunk);
  }
}

Using @langchain/core ^0.3.18, @langchain/langgraph ^0.2.20, and @langchain/openai ^0.3.13.
LangSmith trace: https://smith.langchain.com/public/e2ee1092-6315-4bd4-a11d-9950d540a015/r

up!


Make GitHubChecksContext public outside of package

We want to start using this plugin to send GitHub status check, but our pipelines do not always use GIT or GitHub SCM. For instance, in some cases we use a generic pipeline and use environment variables/parameters to checkout the correct sources. By default, the GitSCM will not be configured to the repository we want to send checks to.
Would it make sense to have GitHubChecksContext public, so we can create a new context and a new ChecksPublisherFactory ?

of course, that makes sense

of course, that makes sense


DotNetCoreTestSettings Can Have Multiple Logger's

With .NET Core 3.0 and with the latest Microsoft.NET.Test.Sdk 16.3.0 NuGet package installed in your test project, you can now create HTML reports as well as TRX XML files like so:
dotnet test --logger trx;LogFileName=foo.trx --logger html;LogFileName=foo.html

The DotnetCoreTestSettings.Logger property is currently a string and needs to be an IEnumerable<string>.

Fixed by #2867


WIP: improve how we construct volumes and volume mounts

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes #
Checklist

[ ] Subject and description added to both, commit and PR.
[ ] Relevant issues have been referenced.
[ ] This change includes docs.
[ ] This change includes unit tests.

/close
superseded by https://github.com/openshift/hypershift/pull/4450


Support alignment algorithm for vision MLLM

PR type

[x] Bug Fix
[x] New Feature
[x] Document Updates
[x] More Models or Datasets Support

PR information

support DPO, ORPO, SimPO, CPO for MLLM
support RLAIF-V dataset
fix florence models infer bugs

Experiment results
Paste your experiment result here(if needed).
TODO:

[x] LLM rlhf test
[x] MLLM test

[x] internvl
[x] llava1.6-mistral
[x] florence

[x] ORPO
[x] SimPO/CPO

LGTM


add a simple MatLab example with Output Windows

set all Events to true
run MtApiClient on Tester or Live (otherwise OrderSend will not work)
Testet with MatLab 2020a and MT5 2650

@KptKuck thank you.


Duplicate OpenDistro security roles for Lagoon groups

Describe the bug
Duplicate OpenDistro security roles for Lagoon groups with differing index permissions created in OpenDistro Security.
To Reproduce
Steps to reproduce the behavior (as a user):

Impersonate as an affected user.
Log in to Kibana and view a problematic index pattern.
See error

Steps to reproduce the behaviour (as an admin):

In Kibana, search for a security role associated with a given Lagoon group.
See that there are multiple roles returned.
See that the roles may also have different index permissions.

Expected behavior
I would expect that there is a single tenant role for a Lagoon group with all the required index permissions.
Screenshots
n/a
Additional context
From the naming of the duplicate roles, they appear to be associated with Lagoon billing groups. Should billing groups have any OpenDistro Security roles associated with them? I would guess they shouldn't?

This has been tightened up


Breaks PLY compatibility

Exported PLYs with Super-Splat has broken compatibility. What exactly breaks is way above my knowledge level.
Impossible to open with https://www.unrealengine.com/marketplace/en-US/product/3d-gaussians-plugin for instance.

Might be worth logging this on the develop's website since I can't test this myself. I suspect the plugin assumes all spherical harmonic data is present. We'll add this option soon!

Would be great, since I can't afford to pay another small fortune for the only plugin that currently supports you in Unreal Engine xD

it's also broken when trying to import ply with Luma AI plugin for UE5 https://lumaai.notion.site/Luma-Unreal-Engine-Plugin-0-4-8005919d93444c008982346185e933a1#0dea5ebba2e24566b7f622a113b38373

I'll add an option so user can choose how many bands of SH to load and save(0..4) - though initially the SH will not be used for rendering in the viewport.

We've released https://github.com/playcanvas/super-splat/releases/tag/v0.10.1 which includes an option to load/save the extra SH data.
Please can you try modifying a scene with option enabled and confirm the resulting files load correctly in the respective plugins?
Thanks!

Unfortunately, that's a no. Does not work.
I don't know if it helps to figure it out, but there is a converter that supports converting to CloudCompare and back to standard 3DGS PLYs again. Might want to look at what it does when going back to 3DGS. https://github.com/francescofugazzi/3dgsconverter

Reposting for notification purposes:
Unfortunately, that's a no. Does not work.
I don't know if it helps to figure it out, but I'm currently using CloudCompare to edit, and there is a converter that supports converting to CloudCompare and back to standard 3DGS PLYs again which seems to work with every single plugin (since it, again, can convert it back into standard 3DGS PLYs).
Might want to look at what they're doing to re-convert it. https://github.com/francescofugazzi/3dgsconverter
EDIT: I can also confirm that that 3dgsconverter now works on PLYs exported with SH setting on! So there is a step missing, but the information needed for conversion is there.
EDIT 2: Apparently, it works to convert it without SH as well. I could have sworn I did a test on this before and the conversion failed...

Edited previous comment due to misinformation, converter does NOT work with SuperSplat, I must have messed up my workflow and gotten my files mixed up.

What a mess of edits and comment deletes I'm doing, sorry. The converter DOES work on SuperSplat (originally made for working with CloudCompare).
So all that needs to be done to open it is:

Import and export with Super-Splat, with or without SH on.
Run the generated PLY through 3dgsconverter.
Open with software or plugin of your choosing. Should work with anything, since 3dgsconverter converts back into completely standard 3DGS PLYs.

No idea what they do that makes it compatible, since all of this is severely out of my league, I just know that it works by testing.
So up to you if you want to check what they are doing to make it 3DGS original compatible and implement a similar feature or suggest using a converter if there are compatibility issues.

Thanks for the realtime updates @AtlasRedux!
I've just noticed that we're exporting some internal editor data to PLY. Presumably it's the extra data that's confusing the plugins. I'll remove that from the output stream.

Ok we've updated the editor. Please try again!

Going to need a live version, for some reason I can't get it to work. Even tried making a test web server in case some weirdness doesn't allow for it to work on local file systems...

Going to need a live version or a build guide. Installed NodeJS and did an NPM INSTALL, but I have absolutely no idea what the output remotely even is. I have zero experience with this, and I just see a bunch of folders I have no idea what is for after an NPM INSTALL.

Going to need a live version or a build/use guide. Installed NodeJS and tried figuring out how to build this, but no go. I am very dependant on build- and usage-instructions on github projects, if it's not VS, I don't know it :P

Sorry I'd published the wrong version. I tested this time and don't see the internal bits exported. Should be all good now 🤞🏼

(Though you might need to reload the page without cache - ctrl + f5)

Regarding building of the project, it was made a mess literally today. We're moving the splat rendering code from one project to another and we've not have time to fix the build steps. Sorry!!!

(welcome to "bleeding" "edge" :D)

There ya go, works like a charm with SH setting on! Guess you can close it now (maybe make a tooltip explaining that it improves compatibility or something to avoid possible future created Issues)

(welcome to "bleeding" "edge" :D)

Hehe, indeed.

Awesome thanks for the help!


Update master branch to guidebot v13

Not sure what to put here other than updating the master branch to the latest code.

guild.owner was removed in v13, use guild.ownerId or guild.fetchOwner to get the ID.

discordjs/discord.js#5480

I only just noticed this comment, but regarding what you said about guildCreate, if you actually look at the code it clearly uses guild.ownerId
https://github.com/AnIdiotsGuide/guidebot/blob/7836eef100fe38fe4197eda88b822ced2a9244a6/events/guildCreate.js (from this very commit)


Use OpenStreetMap instead of google maps

Use this maps instead of evil google maps: https://www.openstreetmap.org

Actually there is another argument for OSM - Google will start charging you if site becomes popular. I used to work in car fleet management company, we paid something above 10K USD per year to Google for Maps, they want to charge you "per asset".

Thanks for the suggestion!


Error: Qiime 2 plugin 'demux' has no action 'emp'

Hi,
I am doing the tutorial with for qiime 2 (2017.4 installed) and I'm getting the following issues:
Error: QIIME 2 plugin 'demux' has no action 'emp'

Thanks for the advice

Hi @rimanasra, can you please post this to the QIIME 2 Forum --- this is where we provide user support. Thanks!


pythonPackages.sqlalchemy: 1.3.19 -> 1.3.20

Motivation for this change
https://docs.sqlalchemy.org/en/13/changelog/changelog_13.html#change-1.3.20
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

if it was under 500, I would be fine with master as well. But yea, better just target staging
git rebase --onto=origin/staging HEAD^
git push ... ... --force

then you need to edit the target branch on this PR

Included in https://github.com/NixOS/nixpkgs/pull/101636.


Additional code cleanup

Codecov Report

Merging #27 (49bba25) into master (a7a69d1) will decrease coverage by 0.26%.
The diff coverage is 77.77%.

@@            Coverage Diff             @@
##           master      #27      +/-   ##
==========================================
- Coverage   53.48%   53.22%   -0.27%
==========================================
  Files          43       42       -1
  Lines        6254     6219      -35
==========================================
- Hits         3345     3310      -35
  Misses       2909     2909

Impacted Files
Coverage Δ

src/evotorch/tools/misc.py
81.74% <63.63%> (-0.60%)
:arrow_down:

src/evotorch/neuroevolution/gymne.py
25.09% <100.00%> (-1.60%)
:arrow_down:

src/evotorch/neuroevolution/neproblem.py
35.16% <100.00%> (ø)

src/evotorch/neuroevolution/vecgymne.py
20.89% <100.00%> (ø)

src/evotorch/tools/__init__.py
100.00% <100.00%> (ø)

src/evotorch/tools/readonlytensor.py
72.52% <100.00%> (-0.95%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Customize colors in settings

This is a placeholder to address #1380 creating a UI and storing settings for the css color variables for page, page draft, chapter, book, and shelf.

@ssddanbrown Do you see this having its own settings card or live within the existing card for customizing the app?

This didn't take as long as I'd initially expected, largely due to the fact that the future was kept in mind when writing the settings controller.
I decided to, for now, leave the colors where they are in the "customization" section because I think that makes the most sense.
I did have to add a number of new labels/descriptions, so one downstream effect of this PR will be that a number of languages will be missing translations for those added keys.

Awesome, Nice work @james-geiger. I'll review this soon. I would have said to live within the existing card anyway :+1:

Thank you for this @james-geiger, All worked great.
Before merging I tweaked up the UI a little just to take up less space in the settings view:

Will be in the next release.


Intro to state in Compose: Android Basics with Compose

URL of codelab
https://developer.android.com/codelabs/basic-android-kotlin-compose-using-state?continue=https%3A%2F%2Fdeveloper.android.com%2Fcourses%2Fpathways%2Fandroid-basics-compose-unit-2-pathway-3%3Fhl%3Dko%23codelab-https%3A%2F%2Fdeveloper.android.com%2Fcodelabs%2Fbasic-android-kotlin-compose-using-state#7
In which task and step of the codelab can this issue be found?
task : adding TextField
Describe the problem
I already did import "androidx.compose.material3.TextField" , sync project with gridle and rebuild, but
errors aren't resolved.
the error is "This material API is experimental and is likely to change or to be removed in the future"
Steps to reproduce?

Go to...
Click on...
See error...

Versions
Android Studio version: Flamingo 2022.2.1 Patch 1 runtime version 17.0.6
API version of the emulator: 33
material3:1.0.1
Additional information
Include screenshots if they would be useful in clarifying the problem.

I have the same issue.
Adding @ExperimentalMaterial3Api before the function remove the issues, but it dosen't seem like the true solution ...

@Jacqueries
@jsmecha
Thank you for reaching out to us.
For now adding @ExperimentalMaterial3Api before the function is one of the temporary solution till the API is stable.


Refactored ui automation framework

Refactored the framework using three layer architecture (page layer, action layer, test class) and added multiple browser support as per requirement.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: patelsurajk sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

@patelsurajk looks pretty good. I think the stuff related to the signin page should be all in the signin page.
Also for some reason the build system didn't trigger. Let's see what happens when you push a new commit to the branch.


Save the current app state (minimized/maximized)

Let's just use my commit, it does nearly the same.

There is one problem with your code and that is multi monitor support.
Imagine I open the app at my third monitor, let it be position 3500|1300, then I close the app and the position will be saved. When I turn off that monitor and open the app again, the app will recover its position, but you won't see it, becasue the monitor is not there anymore.


Errors trying to run examples

I'm getting errors trying to run some of the examples. Here are the ones that run correctly and the ones that don't:

canvas: no
cube: no
cursor: yes
custom-cursor: no
custom-icon: yes
events: yes
multi-window: yes
opengl: no (i'm on a mac, but i put the error below anyway for the sake of completeness)
styles: yes (with message "themes not implemented for this system")
transparent: yes
window: yes

System: MacOS 11.6.8
Deno: 1.31.2
I'm running examples from the links like this:
$ deno run -Ar --unstable https://raw.githubusercontent.com/deno-windowing/dwm/main/examples/canvas.ts
Most examples give this error:
error: Uncaught (in promise) Error: Could not open library: Could not open library: dlopen(/blah/blah/Library/Caches/deno/plug/https/github.com/dde09b5bbcf801e9d3dbb0bf6276f9d048d6643f6b34855bc184ebffa990fd30.dylib, 5): Symbol not found: __ZNKSt3__115basic_stringbufIcNS_11char_traitsIcEENS_9allocatorIcEEE3strEv
  Referenced from: /blah/blah/Library/Caches/deno/plug/https/github.com/dde09b5bbcf801e9d3dbb0bf6276f9d048d6643f6b34855bc184ebffa990fd30.dylib (which was built for Mac OS X 12.6)
  Expected in: /usr/lib/libc++.1.dylib

  return Deno.dlopen(await download(options), symbols);
              ^
    at new DynamicLibrary (ext:deno_ffi/00_ffi.js:415:46)
    at Object.dlopen (ext:deno_ffi/00_ffi.js:545:10)
    at dlopen (https://deno.land/x/plug@1.0.0-rc.3/mod.ts:145:15)
    at async https://deno.land/x/skia_canvas@0.5.2/src/ffi.ts:961:10

imgui error:
error: Uncaught SyntaxError: The requested module '../ext/imgui.ts' does not provide an export named 'CBool'
import { CBool, createContext, destroyContext, imgui } from "../ext/imgui.ts";
         ^
    at <anonymous> (https://raw.githubusercontent.com/deno-windowing/dwm/main/examples/imgui.ts:3:10)

imgui2:
error: Uncaught (in promise) Error: need more work!
      throw Error("need more work!");
            ^
    at getOutFileName (https://raw.githubusercontent.com/djfos/dimgui/main/script/convention.ts:26:13)
    at prepareLibraryFile (https://raw.githubusercontent.com/djfos/dimgui/main/src/ffi.ts:32:38)
    at loadLibrary (https://raw.githubusercontent.com/djfos/dimgui/main/src/ffi.ts:40:30)
    at https://raw.githubusercontent.com/djfos/dimgui/main/src/ffi.ts:56:23

opengl:
GlfwError: 65542 NSGL: OpenGL ES is not available on macOS
error: Uncaught (in promise) Error: Failed to create window
      throw new Error("Failed to create window");
            ^
    at new WindowGlfw (https://raw.githubusercontent.com/deno-windowing/dwm/main/src/platform/glfw/window.ts:674:13)
    at createWindow (https://raw.githubusercontent.com/deno-windowing/dwm/main/src/platform/mod.ts:43:10)
    at https://raw.githubusercontent.com/deno-windowing/dwm/main/examples/opengl.ts:4:16

the first one is because the dl was built for macos X 12.6 and you have 11.6.8. so you need to upgrade to 12.6. not sure how macos works, but here found a similar one: https://stackoverflow.com/questions/71174306/expected-in-usr-lib-libc-1-dylib-installing-tensorflow-on-m1-macbook-pro
Idk why you would run them from a link, but you should probably clone the git repo and then run or copy the code locally and then fix imports (.. becomes https://deno.land/x/dwm@0.3.3). so the imgui error may be because of that
the second imgui error is because deno imgui isnt implemented for macos (hopefully yet ;p)
in dwm/src/script/convention.ts:

export function getOutFileName(): string {
  switch (Deno.build.os) {
    case "windows": {
      return "imgui_windows.js";
    }
    case "linux": {
      return "imgui_linux.js";
    }
    default:
      throw Error("need more work!");
  }
}

as you can see, windows and linux have their implementation but other os dont.


brew reinstall neovim is broken

brew config output
❯ brew config
HOMEBREW_VERSION: 3.0.5
ORIGIN: https://github.com/Homebrew/brew
HEAD: 8b677c0ddd5f96b5521c1b353a9ca07dfe57b80e
Last commit: 15 hours ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: 0d5ae88abf46a18896a1fd0b481a6cfe2e28e0ff
Core tap last commit: 25 minutes ago
Core tap branch: master
HOMEBREW_PREFIX: /usr/local
HOMEBREW_CASK_OPTS: []
HOMEBREW_MAKE_JOBS: 4
Homebrew Ruby: 2.6.3 => /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby
CPU: quad-core 64-bit haswell
Clang: 12.0 build 1200
Git: 2.24.3 => /Library/Developer/CommandLineTools/usr/bin/git
Curl: 7.64.1 => /usr/bin/curl
macOS: 11.2.1-x86_64
CLT: <IP_ADDRESS>.1.1610135815
Xcode: 12.4
brew doctor output
❯ brew doctor
Your system is ready to brew.

[X] The brew doctor above contains no "Warning" lines.

What were you trying to do (and why)?
I am trying to run brew reinstall neovim in order to reinstall neovim to the latest commit on --HEAD (my first install was brew install --HEAD neovim). I do this every day in order to stay on the latest commit of the neovim nightly version.
What happened (include all command output)?
The following error is written to stdout:
❯ brew reinstall neovim
Error: neovim: no bottle available!
You can try to install from source with:
  brew install --build-from-source neovim
Please note building from source is unsupported. You will encounter build
failures with some formulae. If you experience any issues please create pull
requests instead of asking for help on Homebrew's GitHub, Twitter or any other
official channels.

I have never seen this before in the year I've been doing this.
What did you expect to happen?
Because my install was brew install --HEAD neovim I expected brew reinstall neovim to reinstall neovim to the latest --HEAD on the neovim nightly.
Step-by-step reproduction instructions (by running brew commands)
❯ brew install --HEAD neovim
❯ brew reinstall neovim

@glitchy
brew uninstall neovim
brew install --build-from-source --HEAD neovim

If you don't uninstall first, you'll get a weird message saying

Warning: neovim HEAD-c29494b_1 is already installed and up-to-date.
To reinstall HEAD_1, run:
brew reinstall neovim


New version

@JuliaRegistrator register

@JuliaRegistrator register

Registration pull request updated: JuliaRegistries/General/115554
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.2.0 -m "<description of version>" e18701e8567958b84a68ef14dcc01dc8f94ab928
git push origin v0.2.0


Resetting digital miner with redstone signal

I would like to see a way to resetting the digital miner with a redstone signal, so you can use it to harvest trees for example :)

Thanks for maintaining this feature, although its a bit unclear that it exists might have to add a note somewhere that this is possible.


Ubuntu 22.04 setup - unable to add keyring: apt-key failed with message "keyserver receive failed: end of file"

Hello, I'm trying to install Krakend on Ubuntu 22.04
I'm following the official guide for Debian based distro on https://www.krakend.io/docs/overview/installing/
Issued commands:
sudo apt install -y ca-certificates gnupg
ca-certificates is already the newest version (20230311ubuntu<IP_ADDRESS>).
ca-certificates set to manually installed.
gnupg is already the newest version (2.2.19-3ubuntu2.2).
gnupg set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 10 not upgraded.
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv 5DE6FD698AD6FDD2
Executing: /tmp/apt-key-gpghome.AZShtIgpeb/gpg.1.sh --keyserver keyserver.ubuntu.com --recv 5DE6FD698AD6FDD2
gpg: keyserver receive failed: End of file

I received same error on Ubuntu 20.04 also; since apt-key is officially deprecated, what is the recommended way to install Krakend on such os ?
Thanks.

Hi @birbygit
I have no problem installing on Ubuntu 22.04:
root@bc0cc8b90fe8:/# apt-key adv --keyserver keyserver.ubuntu.com --recv 5DE6FD698AD6FDD2
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
Executing: /tmp/apt-key-gpghome.aj97ve5IUI/gpg.1.sh --keyserver keyserver.ubuntu.com --recv 5DE6FD698AD6FDD2
gpg: key 5DE6FD698AD6FDD2: public key "Devops Faith Package Manager<EMAIL_ADDRESS>imported
gpg: Total number processed: 1
gpg:               imported: 1

Hi @birbygit
I have no problem installing on Ubuntu 22.04:
root@bc0cc8b90fe8:/# apt-key adv --keyserver keyserver.ubuntu.com --recv 5DE6FD698AD6FDD2
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
Executing: /tmp/apt-key-gpghome.aj97ve5IUI/gpg.1.sh --keyserver keyserver.ubuntu.com --recv 5DE6FD698AD6FDD2
gpg: key 5DE6FD698AD6FDD2: public key "Devops Faith Package Manager<EMAIL_ADDRESS>imported
gpg: Total number processed: 1
gpg:               imported: 1

Hi taik0, thanks for your feedback.
I noted that you issued the commands as root: why? sudo is not enough?
Anyway, is possible to install krakend by downloading the tar.gz file?
The server where I've to setup Krakend is managed by my client and is under strict security policy so I cannot login as root user.
Thanks.

Hi @birbygit ,
It shows root because it is the official Ubuntu Docker container. Yes, you can use the tar.gz file. The difference with package managers is that you only get the binary, so you must create the service that auto-starts the gateway on server restart.


"NotImplementedYet" Error (SteamVR)

using version v2.1.1 and the UE4Project / OffAxisTest. Unreal 4.2.2
When i select SteamVR as my Tracking Device and play the scene, my window fills up with the error NotImplementedYet. Any idea what's going on here?

Sorry! Currently, there is no support SteamVR tracking (simply because I did not need it yet). It's in the blueprint because someone asked me where he should apply the tracking data from SteamVR/Lighthouse. So, it's just there so it's known where to update the eye position with tracking from the lighthouse system.
Sorry for the confusion.

Ok, coming back to this. So what you're saying is if I input the Vive Tracker xyz positional data in the Do_Steam_VR blueprint's Relative Eye Position, and on the OffAxisActor set the Tracking Device parameter to SteamVR, then that's all i need to get the system working?

In theory, yes :)
There might by some wrangling of the coordinates necessary. The OffAxisPlugin uses the following coordinate system:.
Here is how I've done it in for Optitrack (it's in the [OffAxisActor_CustomOptitrack.uasset](https://github.com/fweidner/UE4-Plugin-OffAxis/blob/master/Content/OffAxisActor_CustomOptitrack.uasset!
1

I have my Vive attached to another computer that sends values over OSC to the computer running the unreal project. Glad to say it's working without issue using this workflow:

Glad to hear that!


Pylance server.bundle.js is detected as trojan

I am noting that the latest version of pylance (11/4/2021, 02:39:25) is being detected as trojan by Windows Defender. See below. Is this a known issue?

The same behaviour occurs with me. The operating system is Windows 11 Pro version 10.0.22000.

Thanks for the report. We will investigate the issue.

Defender for Endpoint is alerting to Pylance 2022.1.1 being infected with Oneeva.
[.vscode\extensions\ms-python.vscode-pylance-2022.1.1\dist\server.bundle.js]

Is this still happening on the latest 2022.2.4 release?

@bschnurr I will remove the whitelisting of the file and see if it is being detected again. I will get back to you.

Have reported to the Defender team and they will update sigs. Thank you for the report.

Defender for Endpoint is alerting to Pylance 2022.1.1 being infected with Oneeva. [.vscode\extensions\ms-python.vscode-pylance-2022.1.1\dist\server.bundle.js]

Lol I feel like I'm in a flying circus episode with @microsoft @python!
Hi guys! I was thinking to myself, and I reached the conclusion that public shaming bad projects with bad maintainers is a reasonable way to entice action.
So I'll tag some organizations in particularly egregious examples of bad behavior with the hopes that given enough eyeball, all bugs are shallow!
I sure hope that one day the guys at @google, @aws, or even @facebook, maybe @apple, that someone, will provide a great open source competitor so that we don't get locked into using the bad @microsoft @python extension as the python experience! 😢
Of I course I must mention the @eclipse @apache and @mozilla guys lest they get jealous! ❤

@JonKast, please open a new issue.


Fix email confirmation: ReviseAuth::Model#confirm_email_change now clears the unconfirmed email.

I was trying out the gem and found out that when changing the email and confirming the view kept saying "Waiting for confirmation of...". The problem was that the unconfirmed email was never cleared when confirming it.

Good catch, and thanks for the PRs!


Universal debug #2140

https://github.com/request/request/issues/2140

[Current coverage][cc-pull] is 91.17%

Merging [#2238][cc-pull] into [master][cc-base-branch] will not change coverage

@@             master      #2238   diff @@
==========================================
  Files            12         12
  Lines          1417       1417
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           1292       1292
  Misses          125        125
  Partials          0          0

Powered by Codecov. Last updated by [1b19c88...4c84e7c][cc-compare]
[cc-base-branch]: https://codecov.io/gh/request/request/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/request/request/compare/1b19c88134b54fec75a270aeb8847d465a4ba8b1...4c84e7ca6c0635e6987692a403dbcc16c6166bf5
[cc-pull]: https://codecov.io/gh/request/request/pull/2238?src=pr

This PR has been closed as "abandoned" as a part of an automated cleanup. If this is a mistake and you are still interested in merging this PR, please do the following:

[ ] Rebase your changes onto the master branch (even if there are no merge conflicts, we want to make sure your change is under the most recent tests).
[ ] Push your updated branch to Github to update this PR.
[ ] Make sure this PR's Travis tests are still passing. (Run npm test locally if tests are still failing).
[ ] Comment here to let us know that you've updated the PR and are still interested in getting it merged. Somebody from the project will respond and work with you to review.

Thank you for your understanding. If you have any questions, please check out https://github.com/request/request/issues/2556 and feel free to comment / ask anything there.


Issue with button click with experimentalProxyless=true

What is your Scenario?
When experimentalProxyless=true, testcafe is not clicking _search button mentioned in below script ( or after clicking browser is not responding) and it fails
This is related to https://github.com/DevExpress/testcafe/issues/6861 (without experimentalproxyless mode we are hitting issue #6891)
Script Used to reproduce with Public Website
import {t, Selector} from 'testcafe'
fixture UnHandledException
test(UnhandledExceptionTC, async tn=>{
const _addressField = Selector('#Address_SingleStreetAddress,input[name="localizationAddressField"]');
const _search = Selector(".localization-container button[type='submit']");
await t.navigateTo("https://www.xfinity.com/learn/offers");
await t.wait(10000);
await t.typeText(_addressField,"200 MAIN ST, NORTHAMPTON, MA 01060",{paste:true})
await t.wait(2000)
await t.click(_search)
await t.expect(_search.visible).notOk();
})
What is the Current behavior?
button not clicked or not responding
What is the Expected behavior?
Should proceed to next step
What is your public website URL? (or attach your complete example)
https://www.xfinity.com/learn/offers
What is your TestCafe test code?
import {t, Selector} from 'testcafe'
fixture UnHandledException
test(UnhandledExceptionTC, async tn=>{
const _addressField = Selector('#Address_SingleStreetAddress,input[name="localizationAddressField"]');
const _search = Selector(".localization-container button[type='submit']");
await t.navigateTo("https://www.xfinity.com/learn/offers");
await t.wait(10000);
await t.typeText(_addressField,"200 MAIN ST, NORTHAMPTON, MA 01060",{paste:true})
await t.wait(2000)
await t.click(_search)
await t.expect(_search.visible).notOk();
})
Your complete configuration file
experimentalProxyless=true
Your complete test report
No response
Screenshots
No response
Steps to Reproduce
import {t, Selector} from 'testcafe'
fixture UnHandledException
test(UnhandledExceptionTC, async tn=>{
const _addressField = Selector('#Address_SingleStreetAddress,input[name="localizationAddressField"]');
const _search = Selector(".localization-container button[type='submit']");
await t.navigateTo("https://www.xfinity.com/learn/offers");
await t.wait(10000);
await t.typeText(_addressField,"200 MAIN ST, NORTHAMPTON, MA 01060",{paste:true})
await t.wait(2000)
await t.click(_search)
await t.expect(_search.visible).notOk();
})
TestCafe version
2.3.0
Node.js version
19.3.0
Command-line arguments
testcafe chrome -F UnHandledException
Browser name(s) and version(s)
No response
Platform(s) and version(s)
No response
Other
No response

Thank you for the example. I managed to reproduce the problem. The actual issue is not with the click action, but with some XHR request that is related to the click action. We'll research it.

I am also experiencing this issue. After enabling proxyless mode in 2.4.0, a button click is no longer functioning. Proxyless mode is needed because the page cannot be tested with hammerhead-js due to its bugs.

@patrickathompson the original issue is very specific. It's unlikely that you have a similar one. Please create a separate issue and share an example using this template.

I appreciate the advice. I was able to find a way to hack around my issue. His example seems to be a very general usecase (not a specific one) of utilizing .click() in a test. It appears that testcafe behavior is different between proxy vs proxyless mode. Once proxyless mode is enabled code that worked to click a button no longer works in the same manner. It's likely that if I created a ticket on this issue it would get the same attention and support as the current one. It is unlikely that there has been any progress on resolving the issue. You have to ask yourself, how good is a test framework that cannot click a button reliably? How critical is this type of bug for a test framework?

@aprabh001c
I cannot reproduce the issue anymore. Please try updating your TestCafe version to 2.5.0 and try the test again.

Hi
Thank you for your response
I am able to see this issue in 2.5 as well.
Node version - 18.16.0
Browser  - Chrome  112.0.5615.138
configuration:
"nativeAutomation": "true"
Please let me know if i need to provide more details
with   "nativeAutomation": "false", we are seeing Error: Session closed with error code 11 for no reason

I've recorded a video to demonstrate that TestCafe handles a button click correctly. Please take a look at the attached video file.
Please also try using the following TestCafe version: https://www.npmjs.com/package/testcafe/v/2.5.1-rc.1
If the issue persists, record a video that demonstrates the issue. Use the following command to record such a video:
npx testcafe chrome test.js -e --native-automation --video artifacts
https://user-images.githubusercontent.com/1678902/235848409-ccbeefc7-42e5-43d9-b4d2-ea4df8bc0875.mp4

I am not seeing this issue with 2.5.1-rc.1 version, but hitting another issue, which is not related to this. I will raise a new issue for that. Thank you for your support.


Files: make it easier to create a new folder

A lot of "file management" starts with creating a new folder and moving things to it.
Right now "New folder" action is hidden under "Add to IPFS" button and hard to discover and requires 2 clicks instead of one.
What if we make it a top-level button (in faded out, much less  prominent colors than "Add to IPFS")?

Thoughts?

Yep, it's confusing to have "new folder" in the same list. I'd like to do some design exploration on what we can do to make the "add to IPFS" process much better. "Add by path" is confusing for new users and it sound like "file system path", so I think we need to re-think this menu entirely.


Add iconfont capabilities

don't mind the svg's they are not complete yet
this does not yet migrate all available icons

LGTM


Disabling built-in functions

Luau currently does not have a way to modify built-in libraries like vanilla Lua does. Even though it is possible to remove, rename or overwrite global functions and functions in module tables using the C API (before loading any scripts), the built-ins hardcoded in the compiler always exists and have priority.
This means that any new built-in introduced to Luau can effectively force embedders to rename their existing functions with the same name.
This issue came up when adopting the vector library but it is a more generic issue only somewhat related to the vector library.
One way to resolve this would be to a new field disabledBuiltIns to Luau::CompileOptions.

Similar to other options, it seems like it can be a list of libraries and not specific functions.
Or will it be better for you to select functions individually?

I think it would be better to allow functions to be selected individually, if possible. That would allow removing colliding functions (or monkey patching) without losing fastcalls for every other function in the same module. This would be future-proof with any new functions added to the language.
Would it be possible to specify the functions as "<optional-module>.<function>". Imaginary example: "setmetatable", "vector.dot", "table.clear"?

thx for the update

Should be implemented in the sync this week.

Thank you!


JS Interop: "setter is not defined" if annotation in other file

I've got annotation like
class hash1{
  external String get _id;
  external void set _id(String _id);
  external factory hash1();
}

You cannot pass _id to factory due to issue https://github.com/dart-lang/sdk/issues/26425
So you should use workaround and set it later, like:
var x = new hash1();
x._id = "someValue";

If annotation is used in the same file it is defined - everything works ok.
If annotation is imported and used in other file - analyzer shows warninng:

"The setter '_id' is not defined for the class ..."

Everything compiles and works correctly, but this warning may  mislead.
Example
https://github.com/denis-aes/dartbug-setter-is-not-defined/blob/master/example/main.dart
Actual for dart 1.16.0

The JS$ encoding scheme is the workaround for JS property names that are not public Dart names such as _foo, 43bar, or catch.
For this case, use
JS$_id everywhere in the dart code and the JS property _id will be referenced.


#us23 flow between epics and projects

User Story
https://tree.taiga.io/project/aanthir1-ser516-spring23-trinity/us/23?milestone=343218
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[Y ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Change Description
Created Flow Between Projects , Epics and New Epics based on the project-slug
Checklist:

[Y ] My code follows the style guidelines of this project
[Y ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ Y] My changes generate no new warnings
[ Y] I have added tests that prove my fix is effective or that my feature works
[ Y] New and existing unit tests pass locally with my changes

Merging pull request after approval into main.


slackUserIdsFromCommitters(botUser: true) is crashing

Your checklist for this issue

[X] Jenkins version 2.249.2

[X] Plugin version 2.43

[X] OS Cloudbees Jenkins docker hub container

Description
Please see https://gist.github.com/mariadb-JeffBachtel/5d934194bc21c0290d4964271132339e for a gist of the FINE logs around the problem
java.lang.UnsupportedOperationException: Refusing to marshal org.apache.http.impl.client.InternalHttpClient for security reasons; see https://jenkins.io/redirect/class-filter/

My pipeline is running on a Kubernetes cloud executor, and not on the master node, if that makes a difference. I'll whitelist the method in question and test as well, but it seemed unlikely others were hitting this.

don't whitelist it

hmm from what I can tell the client should be constructed on the agent already.
this seems to somehow be an interaction with the configuration-as-code plugin.

can you reliably reproduce this?
cc @jetersen

Yes, with "reliably" doing some lifting (I only have 1 pipeline I'm testing the Slack plugin on. The Slack plugin is configured via JCasC. This crash happens every time there is a changeset, but not when a pipeline is rerun with no changes)
The config as code snippet (from Jenkins console)
unclassified:
    slackNotifier:
    botUser: true
    room: "ci-cd"
    sendAsText: false
    slackUserIdResolver: "email"
    teamDomain: "myslackdomain"
    tokenCredentialId: "slack-token"

JCasC plugin is version 1.45, if that's useful

don't whitelist it

I missed this and whitelisted the method, and got the following error when there's a change (and thus emails to lookup): https://gist.github.com/mariadb-JeffBachtel/581ba7b11dcaf6c2bc9653692e28c31d
java.lang.NullPointerException
	at hudson.plugins.jira.JiraMailAddressResolver.findMailAddressFor(JiraMailAddressResolver.java:35)
	at jenkins.plugins.slack.user.EmailSlackUserIdResolver.lambda$resolveUserId$0(EmailSlackUserIdResolver.java:97)

I have the Jira plugin installed and unconfigured via a BlueOcean aggregator. I'm going to try disabling it.

Removing the Jira plugin resolved the NPE (although slackUserIdsFromCommitters(botUser: true) is returning an empty list [], even if the build has a changeset)

the jira issue is fixed in
https://github.com/jenkinsci/slack-plugin/pull/742

Removing the Jira plugin resolved the NPE (although slackUserIdsFromCommitters(botUser: true) is returning an empty list [], even if the build has a changeset)

I (think) am seeing the same issue. slackSend with notifyCommitters: true is not sending anything to the committers. I have added a logger looking at everything under jenkins.plugins.slack.* but the only messages I have got are the JiraMailAddressResolver null pointer exception and the
Posting: ....
Posting succeeded

messages.

@RedDwarf69 have you tried the latest version? https://github.com/jenkinsci/slack-plugin/releases/tag/slack-2.44

Yes.
To be clear, the fix from 2.44 does work for me. I see the JiraMailAddressResolver null pointer exception message only in the Jenkins logger, it's not stopping the Slack plugin from working.
The remaining problem with 2.44 is that that it seems to thinks there are no "changes", or it can't find the emails in the changes, or it can find the Slack users from the emails... and it simply doesn't try to send the direct messages to the committers. There is no error message anywhere, so I don't know exactly where the problem is. The end result it simply that, in Slack, I see the message sent to the channel but not to me (me being the committer of the only commit in the changeset).

bit hard to debug that, possibly some extra logging could be added though...
you might be able to find out by looking at the changes for the build, and via the Jenkins API inspect what objects are associated to it and see if the expected email is there

Since @mariadb-JeffBachtel said (although slackUserIdsFromCommitters(botUser: true) is returning an empty list [], even if the build has a changeset) I simply supposed a general bug in the slack plugin.
Looking into it now,

http://<jenkins_url>/job/<job>/changes shows the user name as an hyperlink
Clicking on the user name I can reach http://<jenkins_url>/user/<user>/configure and in there I can see both

"E-mail address"
"Slack User Settings"->"User Id"

I have two emails configured in GitHub. My understanding is that the company Jenkins instance gets the users from GitHub and apparently it was using the "wrong" email address (not the one used in Slack). But it still doesn't work after correcting the email address.
FWIW in http://<jenkins_url>/configure I have the Slack plugin configured to use "Slack email User ID Resolver" as "User ID Resolver".
If "Slack User Settings"->"User Id" is empty it simply doesn't work (after correcting the email address).
If I manually set my current Slack name (the thing you can do @slack_user in Slack to notify me) in "Slack User Settings"->"User Id" it complains with "channel_not_found". But if in "Slack User Settings"->"User Id" I put the original Slack name I used when creating the Slack account... IT WORKS. I have looked around Slack and nowhere I can find any reference to my original Slack name, luckily I did remember.
My understanding from Jeff comment and the behaviour I observe is that the email->username mapping in slack-plugin is currently not working. But obviously in my case there is something else going on.

use your member id not your username: https://github.com/hmcts/github-slack-user-mappings#github---slack-usernames


Add a GCP notebook image that includes a Hail installation

Linting changes. Would we want to include anything else, like SM or cpg-common?

Good idea, done!


Removing Redundancy from Track Page

The dates are REDUNDANT written two times, once in the pills and then in the track filter bar.
Remove the pills bar and filter content on the basis of track bar only.

Process

Input: User clicks on 17 Jan on tracks bar.
Output: Tracks appear for the given dates and the page content is filtered according to date.

@aayusharora We should toggle between the specific tracks container for the date when the user click the date button. By default all the dates are shown. if user clicks a specific date, only tracks of that date is shown. What is your opinion?

Yes, in that way we can get rid of the above date-pills bar which is confusing to users. @geekyd

@aayusharora There is already an issue regarding this #1176. Please check. Thanks!!

I am unclear if this is a real issue.
Both navigation bars serve a different purpose and provide different actions.

The upper bar provides a direct link and it works in the same way on schedule, tracks and rooms page.
The bar below only exists on tracks and rooms page.

Now as I can see the proposed solution is to change the way the upper bar works on tracks and rooms page. We will have the same buttons on schedule and tracks/rooms page, but they work in different ways: On the schedule page link to the date section, on the tracks/rooms page expand to show more information.
We need to think this through more and maybe change the whole design of this on all pages. As a design principle, please follow this: The same button needs to perform the same action on all pages.

@mariobehling @aayusharora If we are to abide by the proposed design principle, then we can

Remove the date pills from rooms and tracks page and use the navbar for the dates and direct links to tracks and pages. We will be using the date pills on the schedule page though.
OR
We can stick to the current UX for simplicity.

Would love to hear your opinions. Thanks. :)

@geekyd I am unclear what is the right direction. I propose to take a general look at other sites and check out options. Some users asked to separate the session sections to become separate pages. We could also add options to the overview page. So the user can choose. Until we are clear what options there are it is hard to take a decision on details. As a goal for this summer I also see to develop this app into a progressive web app with offline capabilities. What is necessary to achieve this?
Please follow up on this here https://github.com/fossasia/open-event-webapp/issues/1228

Closing this. It was solved with #1262


Attempt to clean up TestHandleTasks

Attempt to clean up TestHandleTasks

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

77 of 980 (7.86%)  changed or added relevant lines in 23 files are covered.
2 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.9%) to 25.426%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

assignments/tasks.go
0
1
0.0%

assignments/assignments.go
0
2
0.0%

database/gormdb_group.go
4
7
57.14%

ag/task.go
0
4
0.0%

database/gormdb_course.go
10
16
62.5%

ag/course.go
0
7
0.0%

scm/env_helper.go
0
7
0.0%

scm/helper.go
0
8
0.0%

web/hooks/github.go
0
10
0.0%

ag/pull_request.go
8
23
34.78%

Files with Coverage Reduction
New Missed Lines
%

database/gormdb_group.go
1
56.25%

scm/helper.go
1
0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.9%

Covered Lines:
2699

Relevant Lines:
10615

💛  - Coveralls


[Master] Update to Unity 2017.4

Update the MRTK with support for the LTS version of Unity 2017 (2017.4.1f1)

https://unity3d.com/unity/whats-new/unity-2017.4.1

I don't think Master should move to 2017.4.
It'll break backwards compatibility with 5.6

If devs want to use 2017.4 they can and unity's auto updater will do everything they need.

@StephenHodgson, How would it break 5.6 compat? It didn't break when we went to 2017.1 and .2?
Thx!

Because unity made some Breaking changes to the Editor from 2017.2 -> 2017.3

The Unity API updater takes care of it for you.

Potential issue with shader changes needs investigation.... Can we #if UNITY_2017_... in the shader and allow support for pre/post 2017.3 changes?

Potential issue with shader changes needs investigation.... Can we #if UNITY_2017_... in the shader and allow support for pre/post 2017.3 changes?

No. That's why I've been apprehensive about updating the editor and just letting Unity's auto updater do the work for us.

This was released in the 2<IP_ADDRESS> release candidate


Fix Dependabot

Well it gives an error about "cannot read version file" or something like that, ill see if i can fix it

are you sure that's the reason? from what i've seen it fails because it uses an older cargo version that does not support rust edition 2024
not really sure how to fix that besides temporarily disabling it

maybe we should disable it.


Update corner.jl

Test cases added for Moravec detection Algorithm

Intended for #15. Please close.


Multi-line comments, adding missed keywords + adding a snippet

Multi-line comment capability (fixing #7)
Added certain keywords e.g. Type, Enum, Implements, Optional, Friend,
Also changed behaviour of some keywords, e.g. "End","Function","Sub"
instead of "End Function", "End Sub" etc..
Removal of non-vba behaviour (remnants from VBScript)
Added basic If snippet, and changed all snippets to use tabs (for user customisation capability).

Thanks @sancarn, that's published now :+1:


Include TypeChecker in TransformationContext so that custom transformers can use type information

Search Terms
customTransformers, custom transformers
Suggestion
Though there are several module bundler plugins that support custom transformers, such as ts-loader, awesome-typescript-loader, parcel-plugin-typescript, rollup-plugin-typescript2, currently some of them cannot accept custom transformers that require TypeChecker.
Including TypeChecker in TransformationContext resolves this issue.
Use Cases
ts-loader, for example, currently supports custom transformers by providing getCustomTransformers option whose type is () => { before?: TransformerFactory[]; after?: TransformerFactory[]; }.
It is not possible to use custom transformers that require TypeChecker such as ts-transformer-keys (it actually requires Program but can be rewritten so that it only requires TypeChecker) with ts-loader.
Though awesome-typescript-loader and rollup-plugin-typescript2 supports such custom transformers
by passing Program or LanguageService, respectively, to the callback corresponding to  getCustomTransformers in ts-loader, I found that it is difficult to modify ts-loader's code so that it can also pass Program or LanguageService (or TypeChecker) to the callback.
Examples
Using ts-transformer-keys with ts-loader as described above.
Checklist
My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript / JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions

Depends on the behavior of custom transformers to use, but at least TypeScript itself does not need to emit different JS based on the types of the expressions

[x] This isn't a runtime feature (e.g. new expression-level syntax)

The type checker is intentionally separated from the transformation process. the rational is that two processed do not need to be serialized. e.g. to get the errors in your editor, you do not need to transform the code, and to transform a single file (ts.transformModule) you do not need to type check the whole project.
That said, you can capture the checker from the compiler API. i do not recommend making any type-directed emit transforms though.

As TypeScript does not provide a functionality to emit JS based on the types of the expressions, implementing custom transformers that depend on TypeChecker is the only way for developers to achieve that functionality.
Therefore, I believe this is one of the most common use cases of custom transformers. Angular also implements and uses such custom transformers.
Providing TypeChecker as a property of TransformationContext is helpful to use such custom transformers.

I'd like this issue to be re-opened.
Custom transformers with TypeChecker give us the power to extend the TypeScript language itself.

How would this be implemented properly? Isn't it possible for the type checker to be out of date due to other transformations?
For example, doing this in a transform outputs number both times:
console.log(typeChecker.typeToString(typeChecker.getTypeAtLocation(declaration))); // number
ts.updateVariableDeclaration(declaration, declaration.name, ts.createTypeReferenceNode("Date", undefined), undefined);
console.log(typeChecker.typeToString(typeChecker.getTypeAtLocation(declaration))); // number

@dsherret Absolutely right. The current design passes one sourcefile at a time into a transformer function chain, which means it would require a redesign to process each sourcefile in the project into one transformer with a new Program instance per each transformer.
This wouldn't be a difficult change to make, however I'm wondering about the expense of creating a Program instance. It seems to me that ts.transform() isn't creating a Program instance at all. (Can anyone confirm?) I assume this design choice is largely performance related, as not all transformers will use a TypeChecker, so recreating one each time would be unnecessarily expensive.
What could work would be to change the transform process from the one file at a time in a transformer chain to each file in the bundle passing to one transformer before moving to the next. This coupled with passing the current state of transformed SourceFiles to the context should allow the transformer to selectively create a CompilerHost which feeds the updated files to a new Program instance which would have an up to date TypeChecker.
Considering that there are many cases where people do use typechecking during transform, I do think it could be a valid change without breaking anything or slowing down the process. It would also be a very simple change. I will likely be adding something like this to ts-patch.
That said, would a PR with the proposed changes be considered? I'd be happy to submit one for review!


Added Malendar

Do you think that there should be a calendar section? I think it would be cool to have different style calendar projects.  If so, I can edit the README

Hm not right now, thanks :smile:


Include pysqlite by default

Graphite-web uses SQLite by default (including the DATABASES setting in local_settings.py) so it makes no sense imho not to install this driver by default.
Cherry-picked into master from 0.9.x, refs #1115.

It's not needed :) Python has native sqlite support since version 2.5.
https://docs.python.org/2/library/sqlite3.html

Ha, nice.


Need store state aware effects testing

I have effects that vary their behavior based upon the state of the store (using withLatestFrom).  Something akin to if I am the first thing added, open a display, if I am the last removed, close it.  However, the EffectsRunner does not actually run the reducers.  This leaves the store state unchanged so my tests do not get the proper effects.  What is the best way to exercise these state aware effects?

Ok, after a bit of tinkering I decided to use the store and its dispatcher rather thane the EffectsRunner.  I created a jasmine custom matcher:
import { Actions } from "@ngrx/effects";
import { Action, Store } from "@ngrx/store";

// This approach was outlined here:
// https://blog.thoughtram.io/angular/2016/12/27/angular-2-advance-testing-with-custom-matchers.html
declare const global: any;
const jasmineExpect = (typeof window === "undefined" ? global : window).expect;

export const expectDispatch:
    <T>(actual: {actions: Actions, store: Store<T>, dispatch: Action}) =>
        DispatchMatcher<T> = jasmineExpect;

export interface DispatchMatcher<T> extends jasmine.Matchers<T> {
    toEmit(...expected: Array<Action|[Action, T]>): boolean;
}

export const customJasmineMatchers: jasmine.CustomMatcherFactories = {
    toEmit: (util, customEqualityTesters) => {
        return {
            compare: <T>(
                actual: {actions: Actions, store: Store<T>, dispatch: Action},
                ...expected: Array<Action|[Action, T]>) => {

                const verify = [...expected];
                const result = {
                    message: "success",
                    pass: true,
                };
                const subscription = actual.actions
                    .withLatestFrom(actual.store)
                    .subscribe(([action, state]) => {
                        const value = verify.shift();
                        if (value === undefined) {
                            result.pass = false;
                            result.message = "extra values were emitted";
                        }
                        if (result.pass) {
                            const actualValue = Array.isArray(value)
                                ? [action, state] : action;
                            result.pass = util.equals(actualValue, value);
                            if (!result.pass) {
                                result.message =
                                    util.buildFailureMessage(
                                        "to equal", false, actualValue, value);
                            }
                        }
                    });
                actual.store.dispatch(actual.dispatch);
                subscription.unsubscribe();
                if (result.pass && verify.length !== 0) {
                    result.pass = false;
                    result.message = "not all values were emitted, " +
                        `expected ${expected.length}, ` +
                        `got ${expected.length - verify.length}`;
                }

                return result;
            },
        };
    },
};

Then I initialize my TestBed thusly:
        function setup(initialState: AppState) {
            TestBed.configureTestingModule({
                imports: [
                    StoreModule.provideStore(appReducer, initialState),
                    EffectsModule.run(AppEffects),
                ],
                providers: [
                    Actions,
                ],
            });

            return {
                actions: TestBed.get(Actions) as Actions,
                store: TestBed.get(Store) as Store<AppState>,
            };
        }

And use it in my tests like so:
            it(`should dispatch one, and trigger effect two and three`, () => {
                const {actions, store} = setup();
                const dispatch = new OneAction();
                const initialState = {};
                const finalState = {one: 1, two: 1, three: 1};
                expectDispatch({actions, store, dispatch}).toEmit(
                    [
                        { type: Dispatcher.INIT } as Action,
                        initialState,
                    ],
                    new TwoAction(),
                    new ThreeAction(),
                    [
                        dispatch,
                        finalState,
                    ]);
            });

This approach allows me to verify all the emitted actions including effects and, if i desire, verify the state after each effect.  Two things to note is that be the very first emitted action will be the Dispatcher.INIT, and the dispatched action itself will show up last (not exactly sure of the details on this, but it may be related to: Actions are received in wrong order #126 ).


Copy "mark-as-read" native method call to the send-message functions

Wait I'm so confused what you want from me here. You want me to move what to where?


Tech Debt: Use testify for pkg/imageset tests

Note: Currently stacked on #1619. Review only the second commit.