[REGRESSION] Parsing dates of the form 2022-1-1 that used to parse (now needs 2022-01-01)

Describe the bug
In arrow 34.0.0, values such as '2021-1-1T05:11:10.432' were parsed as a timestamp but now they error
To Reproduce
Try to parse this value as a timestamp: '2021-1-1T05:11:10.432'
Expected behavior
The value '2021-1-1T05:11:10.432' parses the same as '2021-01-01T05:11:10.432'
Workaround is to change it to (add leading zeros) '2021-01-01T05:11:10.432'
Additional context
We discovered this as part of the upgrade in DataFusion https://github.com/apache/arrow-datafusion/pull/5685
Per @tustvold it appears that 2021-1-1T05:11:10.432 is supported by chrono even though it is not strictly valid and arrow was not documented to support this format: https://github.com/apache/arrow-datafusion/pull/5685#discussion_r1150732948
It may be that we simply choose not to fix this regression as the previous implementation was working "by accident" but I wanted to file this ticket to track the change in behavior

I'm closing this as 2 months have passed with no complaints


Update scala3-library to 3.4.1

About this PR
📦 Updates org.scala-lang:scala3-library from 3.3.3 to 3.4.1
📜 GitHub Release Notes - Version Diff - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

🔍 Files still referring to the old version number
The following files still refer to the old version number (3.3.3).
You might want to review and update them manually.
.github/workflows/ci.yml
build.sh

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-lang", artifactId = "scala3-library" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scala-lang", artifactId = "scala3-library" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, version-scheme:semver-spec, old-version-remains, commit-count:1

Scala 3.4.1 is not an LTS version


Build for WASM

I'm not a web guy, so I'm not sure what an idiomatic JavaScript/TypeScript interface should look like, but I imagine there's a desire for fast web FFTs and I imagine it should be reasonably easy to build for wasm32-unknown-unknown.

Just so no one else starts working on this or you discard plans for it, I'm working on building a wasm fourier package

Sorry if it's obvious but just so I know for my implementation, what is the complex input for the Bluestein algorithm? I've only ever used the fft for real number values.

I've only implemented complex-to-complex transforms (no real-to-complex or real-to-real, see #5), so both the inputs and outputs are Complex<f32> or Complex<f64>.  In memory, each complex number is just equal to two adjacent real values, something like this:
#[repr(C)]
struct Complex<T> {
    real: T,
    imag: T,
}

That shouldn't be specific to Bluestein's algorithm either.  I'd recommend working with the fourier crate directly rather than the fourier-algorithms crate.

Ahh, thank you. I guess what I am asking is what is this array in real life? Like is it a sine wave that has been processed or what goes into creating this input vector in the real world?

Never mind I figured it out


Accept multiple path arguments

This is https://github.com/Behat/Behat/pull/996 rebased. I've removed the change to CHANGELOG.md.
I've been using this patch for years now, it's great!

@adrienbrault you'll want to rebase this so you get the fix for the issue that failed your build.

@Chekote This PR targets 4.x ( https://github.com/Behat/Behat/pull/996#issuecomment-1171222886 ), which does not have the fix, yet.

Thanks for your patience @adrienbrault


Callable variables and class properties

An interesting use-case came up in the TypeDoc repo (TypeStrong/typedoc#858). Would it be reasonable to define the following as a function rather than a variable? JSDoc users can use @function but from discussions in #8 I don't know if that would be a good thing to carryover.
/**
 * Promisified version of fs.writeFile().
 * @function writeFileAsync
 */
export const writeFileAsync: Function = util.promisify(fs.writeFile);

A similar use case is instance methods. I know that tslint has made changes to view these the same as methods for the purpose of grouping properties and methods.
class Foo {
  constuctor(events: EventService) {
    events.on('someevent', this.bar);
  }

  /**
   * This acts like a method and can be passed as a callback without losing context of `this`.
   * @param param - new value of prop
   */
  bar = (param: String) => {
    console.log('Am I a method?');
    this.prop = param;
  }
}

I recall an office-ui-fabric-react PR #4304 that replaced the @autobind decorator with an incantation similar to what you show above.
I understand why they took that approach, however to me it seemed to have a number of potential downsides as a general practice:

It blurs the distinction between code and data, working against the conventional programming language grammar that people rely upon for understanding someone else's source code

It may work against optimizations that look for stereotypical patterns (i.e. Webpack, Google Closure, etc may have a harder time proving that it's safe to transform a "member function" that doesn't look like a function)

It may not be supported by static analysis tools, e.g. an IDE's features such as "find all callers of this function" or "convert this into a static function" may have trouble determining that this construct should be understood as a function declaration

CC some office-ui-fabric-react people who maybe can provide a counterpoint:  @dzearing @cliffkoh @Markionium


error fixed-HashMap to LinkedHashMap

This PR addresses fixing a total of 11 flaky tests:
com.eatthepath.pushy.apns.ApnsClientTest#testSendNotification
com.eatthepath.pushy.apns.ApnsClientTest#testSendNotificationWithPushTypeHeader
com.eatthepath.pushy.apns.server.TokenAuthenticationValidatingPushNotificationHandlerTest#testHandleNotificationWithEmptyPayload
com.eatthepath.pushy.apns.server.TokenAuthenticationValidatingPushNotificationHandlerTest#testHandleNotificationWithCollapseId
com.eatthepath.pushy.apns.server.TokenAuthenticationValidatingPushNotificationHandlerTest#testHandleNotificationWithExpirationDate
com.eatthepath.pushy.apns.server.TokenAuthenticationValidatingPushNotificationHandlerTest#testHandleNotificationWithSpecifiedPriority
com.eatthepath.pushy.apns.server.TokenAuthenticationValidatingPushNotificationHandlerTest#testHandleNotificationWithMissingPayload
com.eatthepath.pushy.apns.server.TokenAuthenticationValidatingPushNotificationHandlerTest#testHandleNotificationWithOversizedPayload
com.eatthepath.pushy.apns.server.TokenAuthenticationValidatingPushNotificationHandlerTest#testHandleNotificationWithWithExpiredAuthenticationToken
com.eatthepath.pushy.apns.auth.AuthenticationTokenTest#testVerifySignature
com.eatthepath.pushy.apns.server.TokenAuthenticationValidatingPushNotificationHandlerTest#testHandleNotificationWithValidNotification.

Analysis for the test testHandleNotificationWithSpecifiedPriority:
The function AuthenticationTokenTest.testHeadersToMap() examines whether the generated tokens are identical. However, the AuthenticationTokenHeader.toMap() method does not consistently produce the expected output, primarily because it lacks a predefined order and lacks determinism. This issue arises from the fact that the order of token chunks is not preserved due to the utilization of HashedMap. Consequently, the following tests may experience failures: AuthenticationTokenHeader.toMap() and AuthenticationTokenClaims.toMap().
This flakiness was found by using the NonDex tool.
mvn -pl pushy edu.illinois:nondex-maven-plugin:2.1.1:nondex -Dtest=com.eatthepath.pushy.apns.server.TokenAuthenticationValidatingPushNotificationHandlerTest#testHandleNotificationWithOversizedPayload

The fix was done in the line below:
https://github.com/Sujishark/pushy/blob/da5f8b97106cd41278b421ec63e4e76a7313bed9/pushy/src/main/java/com/eatthepath/pushy/apns/auth/AuthenticationToken.java#L132
Environment:

Java: openjdk version "<IP_ADDRESS>"
Maven: Apache Maven 3.6.3

This pull request aims to introduce a dependable sorting mechanism (HashMap to LinkedHashMap) for arranging the returned fields systematically.

Hi,
It's good that you have found the root cause of the test and could fix, but it would be great if you can document it in a more detailed way. I am attaching a sample format that you can follow for the same: https://github.com/uiuc-cs527-fa23/moquette/pull/1

Hello,
My opinion is the same as the previous comment. It would be great to make the description more detailed. For instance, you can include snapshots of code or test results to help support why this fix is import. You should also explain the process of locating the root cause, the process of coming up with the fix. Finally, a result of the fixed NonDax report

Updated the status from Ready to Opened. Thankyou :)


Mixed use of tabs and spaces

Tabs and spaces are mixed throughout the code. Looks like you are using 4 spaces to correspond to a half tab (8 space tabs). For example this while-loop https://github.com/westermo/brist/blob/main/lib.sh#L127.
The loop is indented with 4 spaces. Next line is 1 tab (8 spaces). Next line is 1 tab + 4 spaces. And next line is 2 tabs.
This does not feel like a good way to handle indentation.

My approach to whitespace is pretty simple:

Press Tab key
Trust emacs(1) to do the Right Thing™

I'll admit that mixing spaces and hard tabs is a bit weird, then again it seems to be the default behavior in at least one editor. We could change it I suppose - but to be honest, it is very low on the priority list.


Add back Flashing power button to Video player when video is playing but inactive (aswell as text in url slot)

Need to add back the flashing power button and text telling people to turn on player when a video is playing for others.
Or maybe a big note in middle of display lol

While were at it could we also simply click said onscreen prompt to turn on the player as well?


Fix/absolute imports

Update build to allow absolute imports instead of using relative imports which can get out of control with a lot of ../../ references. All the primary directories in src are defined so we can start import references from those.

:tada: This PR is included in version 1.0.0-beta.17 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


containerd configuration outdated for isolated Kubernetes

https://docs.metal-stack.io/stable/overview/isolated-kubernetes/#OS-Metal-Extension

Changed by https://github.com/metal-stack/os-metal-extension/pull/49


Fix bundleio tests

This fixes these bundleio tests that a were added by Gian. The issues is that he calls two tests with the same executable. One exercises create a lat-lon file, the next exercises creating a cubed-sphere file. The problem is the executable uses a hard coded name for the temporary file created. So after say the lat-lon test runs, when the cube test runs the old lat-lon file from the previous test is still there. Since we do not clobber on creation (might want to revisit this) it tries to use the old existing lat-lon file and goes kaboom since it tries to write to a variable that does not exist.
So I just added the temporary file as an option to the command line for the testing program and use different files for the two tests.

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Types of changes

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Trivial change (affects only documentation or cleanup)

Checklist:

[ ] I have tested this change with a run of GEOSgcm (if non-trivial)
[X] I have added one of the required labels (0 diff, 0 diff trivial, 0 diff structural, non 0-diff)
[X] I have updated the CHANGELOG.md accordingly following the style of Keep a Changelog

Now here's a new question (maybe for @tclune): Should we try enabling these in CI? Or are they not quite tests for CI? Still, I'll pull this in and maybe do an experiment to see if CircleCI is happy when I do.


Using coreLibraryDesugaringEnabled causes crash when my app starts

Hi,
I'm just wondering what is causing the coreLibraryDesugaringEnabled requirement for older devices? Is it because you are using java.util.List.stream?
Thanks

Yes, coreLibraryDesugaringEnabled is needed for java.util.List.stream. If your app crashes because of this maybe you haven't integrated it the right way, take a look at the README, or here.

Thank you, I was definitely integrating properly... But no worries I've recoded the stream parts so it's no longer needed. The extension is working great, thank you for releasing it to the public!


Installing ember-cli-simple-auth breaks Ember in mobile Safari

For some reason, simply installing ember-cli-simple-auth breaks Ember in Safari (testing on iOS 8.4). Here's a bare-bones example which reproduces the problem:
> ember new test-foo
> cd test-foo
> ember generate controller application

// app/templates/application.hbs

Welcome to Ember.js

CLICK ME {{name}}
{{outlet}}

// app/controllers/application.js
import Ember from 'ember';

export default Ember.Controller.extend({
  actions: {
    foo: function() {
      this.set('name', 'foo');
    }
  }
});

If you open this page in Safari on your iPhone, you'll see "foo" when you click "CLICK ME". Now install ember-cli-simple-auth:
> ember install ember-cli-simple-auth

Reload in Safari, and you'll see clicking "CLICK ME" doesnt do anything.

Is this related to emberjs/ember.js#5606? Maybe removing the "use strict" will fix it.

I think the "use strict"s are added by babel to removing them isn't really an option - would be great if someone could track down which exact line is actually causing it.

See the link I included, this is actually a bug with Webkit on iOS that is triggered by Object.create() and "use strict" (if I remember correctly).

@tasn: yes, I saw that but still the bug must be caused by a specific line in ESA. ESA also doesn't use Object.create directly anywhere so if it breaks somewhere in Ember itself it needs to be fixed there.

You could also check whether this fixes your project.

I don't have the time to build things from scratch at the moment, but I have removed every occurrence of "use strict" from my vendor.js file, and now everything works as expected, so the use strict bug is definitely the cause.

This won't be fixed in ESA as it seems to be a bug in Safari actually and rwjblue/broccoli-use-strict-remover already exists to fix it.

For some reason it doesn't work any more. Odd, as it worked perfectly fine a moment ago.

Did you try rwjblue/broccoli-use-strict-remover?

I'm sorry, but please disregard all of my comments. I haven't realised, but I was testing on the iPhone in incognito mode which has issues with local storage (and apparently triggered other things). After trying in "normal" mode, everything works as expected. I'd wait for OP for more information. Can't reproduce, everything works for me.
Sorry for the noise.


Connected to casambi but couldn't log in

Hi,
I'm trying to setup Casambi on Hass.io. HACS is installed and Casambi component is also installed
I configured all parameter in HA but I'm getting these 2 errors at boot
2021-03-26 21:32:22 ERROR (MainThread) [custom_components.casambi.light] Connected to casambi but couldn't log in
2021-03-26 21:32:17 INFO (MainThread) [homeassistant.components.light] Setting up light.casambi
I tried my credentials via https://developer.casambi.com/console
HTTP RequestPOST https://door.casambi.com/v1/networks/session
Path ParametersNone
Request Body
{
"email"<EMAIL_ADDRESS>"password": "password"
}
This is working just fine so I'm wondering why it's not working via the Addon
I tried to capture the trafic via tcpdump on my Router but not seeing the request (TLS)
Also tried to extend the debug via Loger but I'm not getting more details
Is there any option to do the troubleshooting?
Thank you

Hi,
I found that I'm not able to login to POST https://door.casambi.com/v1/users/session
While login to POST https://door.casambi.com/v1/networks/session is ok
Do you think that it could be adapter for Hass.io ?

Hi,
Are you using site user credentials for  https://door.casambi.com/v1/users/session?
The addon is using both (network session & user session), but as you pointed out we could probably go with either or :)
I need to do some testing on my end, I usually use my library for testing https://github.com/hellqvio86/casambi, I don't do MITM attack or MITM proxy.

Hi,
I'm not sure which credentials is needed for Users session
I've a password to access mu network but that's it. I've some users defined in the App but none of these users are able to authenticate
When trying via the WebAPI I'm only able to login via https://door.casambi.com/v1/networks/session
All tests via https://door.casambi.com/v1/users/session are failing.
Can you help me to create a user and run the test again ?
Thank you

Its the same credentials as you are using in your Casambi app, the documentation for creating a site:
https://support.casambi.com/support/solutions/articles/12000041325-how-to-create-a-site
I am doing some testing on using only user or network session.

Thank you I will run the test
Site feature were disabled in my installation. I will try to create a site & a user

Hi
Just to confirm that everything is working after defining a site :)
Do you plan to also allow the change of color on top on the dimmer ? I've these 2 options in the App but not via HA
Thank you for the great work !

Great that it worked (closing the issue)!
No I don't have any plan to add that support my self, I don't have any Casambi hardware currently that supports changing colors, but I am happy to accept PR:s
And the python library and Home assistant integration don't  support colors, that's why you don't have the option in Home Assistant. Its not probably that hard to add the support, probably some format joggling, like the brightness support
Best regards Olof Hellqvist


Add goog.reflect.objectProperty as a first class primitive

This is a rather large PR.

Adds coding convention support for property renaming functions. Eliminates hard coded references throughout the code base to JSCompiler_renameProperty - and the various mis-spelled comments.
Adds support for property renaming functions to the type-based renaming passes. In these cases the renaming function requires a second argument which is an instance of the referenced type. For type-based renaming usage, the property reference must be a single property and not a qualified name.
Updates the Node.getQualifiedName() method to take a boolean argument to support returning the original property names instead of the renamed versions.

Fixes: #179
I'll be adding tests shortly.
CC @concavelenz

This change is

This seems very interesting, but I don't entirely understand the point.  Presumably the compiler can only make the substitution if the property is a string literal, in which case what does this gain us?  Is this just an internal representation, or do you anticipate framework code calling this function, and if so what is an example use case?

Review status: 0 of 15 files reviewed at latest revision, 8 unresolved discussions.

src/com/google/javascript/jscomp/AmbiguateProperties.java, line 461 [r1] (raw file):
compiler.getCodingConvention()?

src/com/google/javascript/jscomp/AmbiguateProperties.java, line 471 [r1] (raw file):
nit: Remove this empty line?

src/com/google/javascript/jscomp/RenameProperties.java, line 354 [r1] (raw file):
compiler.getCodingConvention()?

src/com/google/javascript/rhino/Node.java, line 1756 [r1] (raw file):
This name == null should always be false.

test/com/google/javascript/jscomp/DisambiguatePropertiesTest.java, line 41 [r1] (raw file):
Use LINE_JOINER.join() to save yourself from the concatenations and newlines, same below and in the other test file.

test/com/google/javascript/jscomp/RenamePropertiesTest.java, line 184 [r1] (raw file):
nit: Indent one space more to keep the input and output aligned.

Comments from Reviewable

@shicks There are multiple use cases. The immediate need is with Polymer, but I've personally hit this limitation numerous times.
Polymer({
  is: 'foo-bar',
  created: function() {
    this.foobar = 'some-string'; //This is a renameable reference
  },

  someOtherMethod: function() {
    this.foobar = 'other-string';

    //this must be renamed too
    this.notifyPath(goog.reflect.objectProperty('foobar', this), this.foobar);
  }
})

Review status: 0 of 17 files reviewed at latest revision, 7 unresolved discussions.

src/com/google/javascript/jscomp/AmbiguateProperties.java, line 461 [r1] (raw file):
Done.

src/com/google/javascript/jscomp/AmbiguateProperties.java, line 471 [r1] (raw file):
Done.

src/com/google/javascript/jscomp/DisambiguateProperties.java, line 536 [r1] (raw file):
Done.

src/com/google/javascript/jscomp/DisambiguateProperties.java, line 546 [r1] (raw file):
Done.

src/com/google/javascript/jscomp/RenameProperties.java, line 354 [r1] (raw file):
Done.

src/com/google/javascript/rhino/Node.java, line 1747 [r1] (raw file):
Done.

src/com/google/javascript/rhino/Node.java, line 1756 [r1] (raw file):
Done.

Comments from Reviewable

I had to significantly refactor this. Multiple optimization passes were interfering with the ability to recognize a property rename function late in the optimizations. Instead, I'm no using a peephole replacement to change all of them to JSCompiler_renameProperty. This is much simpler to check for later and already has all the necessary exceptions.

Tests added. I ended up using an integration test because property renaming affects so many optimization passes.

Review status: 0 of 17 files reviewed at latest revision, 9 unresolved discussions.

src/com/google/javascript/jscomp/AmbiguateProperties.java, line 468 [r6] (raw file):
|| should be on the next line.

Comments from Reviewable

Don't worry about formatting things like that. That's why we have a formatter :)
https://github.com/google/closure-compiler/wiki/Contributors#coding-conventions

Getting a crash with some internal tests that use the "dart pass" -- trying to come up with a minimal repro.

@MatrixFrog Did you see the TODO I added in the dart pass? Maybe we should address this at the same time. Trouble is - I don't use dart.

Yes, maybe.
The error is from https://github.com/google/closure-compiler/blob/91cf3603d5b0b0dc289ba73adcd0f2741aa90d89/src/com/google/javascript/jscomp/VarCheck.java#L201 -- we insert a call to a non-existent function, so I guess we need to also create a synthetic externs definition for it.

Say what? That part didn't change.
However adding a synthetic extern is something we should do anyway. I'll see about that. It's a little tricky because there are existing definitions for JSCompiler_renameProperty - some externs, some source.

Yup, including a few in some Google internal projects. This will be "fun"

Okay, I think I have a fix (in progress, but I'm pretty sure it will work). The Dart pass was using a lot of srcrefTree on calls to JSCompiler_renameProperty, in such a way that the JSCompiler_renameProperty's "original name" would be set incorrectly, so then the CodingConvention wouldn't properly recognize it. We need to set the line numbers of synthetic nodes without accidentally setting the original name property.

Will land the closure-library side of this after the next release (which we hoped would be today but it got delayed a bit)

@MatrixFrog Where are we on this? Do I need to add the synthetic extern or are you still working on this internally?

This was rolled forward on May 18, but it looks like Github isn't seeing that. I think I forgot to get the closure-library side of this done, so I'll do that now. Then I don't think you'll need any synthetic externs.

Ah, sorry I forgot. I'm intentionally not landing the closure-library change until after we build a release (at least a Google-internal release, if not an external one) that contains this change. It may be a week or so.

Closing this PR since it landed as 02c97ef798109c0dfaacf5b565d781d2ff0203c7 (apologies for the misattribution, I must have done something wrong with the MOE stuff) but I'll get the closure-library change in soon, hopefully within a week or so.

No rush from my standpoint on the closure-library changes. It was the compiler changes I was most concerned with.
Thanks!


Warnings output by RSpec

When running RSpec on my project with the warnings flag, following warnings are output:
/home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/dry-schema-1.5.0/lib/dry/schema/dsl.rb:5: warning: /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/dry-schema-1.5.0/lib/dry/schema/dsl.rb:5: warning: loading in progress, circular require considered harmful - /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/dry-schema-1.5.0/lib/dry/schema.rb
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/rspec-core-3.9.1/exe/rspec:4:in  `<main>'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/rspec-core-3.9.1/lib/rspec/core/runner.rb:45:in  `invoke'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/rspec-core-3.9.1/lib/rspec/core/runner.rb:71:in  `run'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/rspec-core-3.9.1/lib/rspec/core/runner.rb:86:in  `run'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/rspec-core-3.9.1/lib/rspec/core/runner.rb:99:in  `setup'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/rspec-core-3.9.1/lib/rspec/core/runner.rb:132:in  `configure'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/rspec-core-3.9.1/lib/rspec/core/configuration_options.rb:22:in  `configure'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/rspec-core-3.9.1/lib/rspec/core/configuration_options.rb:112:in  `process_options_into'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/rspec-core-3.9.1/lib/rspec/core/configuration_options.rb:112:in  `each'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/rspec-core-3.9.1/lib/rspec/core/configuration_options.rb:113:in  `block in process_options_into'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/rspec-core-3.9.1/lib/rspec/core/configuration.rb:1542:in  `requires='
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/rspec-core-3.9.1/lib/rspec/core/configuration.rb:1542:in  `each'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/rspec-core-3.9.1/lib/rspec/core/configuration.rb:1542:in  `block in requires='
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/rspec-core-3.9.1/lib/rspec/core/configuration.rb:2076:in  `load_file_handling_errors'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:72:in  `require'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:72:in  `require'
	from /home/mic/dev/experimental/rack-app/spec/spec_helper.rb:22:in  `<top (required)>'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/2.7.0/bundler.rb:174:in  `require'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/2.7.0/bundler/runtime.rb:58:in  `require'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/2.7.0/bundler/runtime.rb:58:in  `each'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/2.7.0/bundler/runtime.rb:69:in  `block in require'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/2.7.0/bundler/runtime.rb:69:in  `each'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/2.7.0/bundler/runtime.rb:74:in  `block (2 levels) in require'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/2.7.0/bundler/runtime.rb:74:in  `require'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/dry-schema-1.5.0/lib/dry-schema.rb:3:in  `<top (required)>'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/dry-schema-1.5.0/lib/dry-schema.rb:3:in  `require'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/dry-schema-1.5.0/lib/dry/schema.rb:7:in  `<top (required)>'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/dry-schema-1.5.0/lib/dry/schema.rb:7:in  `require'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/dry-schema-1.5.0/lib/dry/schema/dsl.rb:5:in  `<top (required)>'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/dry-schema-1.5.0/lib/dry/schema/dsl.rb:5:in  `require'

/home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/dry-schema-1.5.0/lib/dry/schema/rule_applier.rb:5: warning: /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/dry-schema-1.5.0/lib/dry/schema/rule_applier.rb:5: warning: loading in progress, circular require considered harmful - /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/dry-schema-1.5.0/lib/dry/schema.rb
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/rspec-core-3.9.1/exe/rspec:4:in  `<main>'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/rspec-core-3.9.1/lib/rspec/core/runner.rb:45:in  `invoke'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/rspec-core-3.9.1/lib/rspec/core/runner.rb:71:in  `run'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/rspec-core-3.9.1/lib/rspec/core/runner.rb:86:in  `run'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/rspec-core-3.9.1/lib/rspec/core/runner.rb:99:in  `setup'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/rspec-core-3.9.1/lib/rspec/core/runner.rb:132:in  `configure'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/rspec-core-3.9.1/lib/rspec/core/configuration_options.rb:22:in  `configure'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/rspec-core-3.9.1/lib/rspec/core/configuration_options.rb:112:in  `process_options_into'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/rspec-core-3.9.1/lib/rspec/core/configuration_options.rb:112:in  `each'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/rspec-core-3.9.1/lib/rspec/core/configuration_options.rb:113:in  `block in process_options_into'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/rspec-core-3.9.1/lib/rspec/core/configuration.rb:1542:in  `requires='
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/rspec-core-3.9.1/lib/rspec/core/configuration.rb:1542:in  `each'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/rspec-core-3.9.1/lib/rspec/core/configuration.rb:1542:in  `block in requires='
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/rspec-core-3.9.1/lib/rspec/core/configuration.rb:2076:in  `load_file_handling_errors'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:72:in  `require'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:72:in  `require'
	from /home/mic/dev/experimental/rack-app/spec/spec_helper.rb:22:in  `<top (required)>'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/2.7.0/bundler.rb:174:in  `require'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/2.7.0/bundler/runtime.rb:58:in  `require'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/2.7.0/bundler/runtime.rb:58:in  `each'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/2.7.0/bundler/runtime.rb:69:in  `block in require'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/2.7.0/bundler/runtime.rb:69:in  `each'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/2.7.0/bundler/runtime.rb:74:in  `block (2 levels) in require'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/2.7.0/bundler/runtime.rb:74:in  `require'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/dry-schema-1.5.0/lib/dry-schema.rb:3:in  `<top (required)>'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/dry-schema-1.5.0/lib/dry-schema.rb:3:in  `require'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/dry-schema-1.5.0/lib/dry/schema.rb:7:in  `<top (required)>'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/dry-schema-1.5.0/lib/dry/schema.rb:7:in  `require'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/dry-schema-1.5.0/lib/dry/schema/dsl.rb:11:in  `<top (required)>'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/dry-schema-1.5.0/lib/dry/schema/dsl.rb:11:in  `require'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/dry-schema-1.5.0/lib/dry/schema/macros.rb:9:in  `<top (required)>'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/dry-schema-1.5.0/lib/dry/schema/macros.rb:9:in  `require'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/dry-schema-1.5.0/lib/dry/schema/macros/optional.rb:3:in  `<top (required)>'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/dry-schema-1.5.0/lib/dry/schema/macros/optional.rb:3:in  `require'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/dry-schema-1.5.0/lib/dry/schema/macros/key.rb:3:in  `<top (required)>'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/dry-schema-1.5.0/lib/dry/schema/macros/key.rb:3:in  `require'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/dry-schema-1.5.0/lib/dry/schema/processor.rb:10:in  `<top (required)>'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/dry-schema-1.5.0/lib/dry/schema/processor.rb:10:in  `require'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/dry-schema-1.5.0/lib/dry/schema/rule_applier.rb:5:in  `<top (required)>'
	from /home/mic/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/dry-schema-1.5.0/lib/dry/schema/rule_applier.rb:5:in  `require'

Resources
Ruby 2.7.

Well, it's not a feature request - but not a bug either.

@MicMicMon this is a bug actually, circular requires are nasty and we definitely want to fix this. I actually can't tell from the backtrace which require it is though. Did you track it down?

Yup, looks like it's:
This line in dsl.rb --> main file --> Line 7 requires back dsl.rb
Second warning seems caused by the same cycle: schema/rule_applier.rb --> schema/processor.rb --> schema/macros/key.rb --> schema/macros/optional --> schema/macros --> schema/dsl --> ...and then same cycle as above...

@MicMicMon thank you, this should be easy to fix


Add genomes to v4 validity checks

This adds genomes to the v4 validity check script. There is a hardcoded test path and commented out code that I'll delete and restore once this is ready but leaving this here for easy testing.

Yes -- should have been one for fafmax, just added!

just one thing and removal of TODOs then this is good to go. @KoalaQin can you look into edits for the HGDP_POPS and HGDP_POP_NAMES in gnomad.resources.grch38.gnomad ?

@jkgoodrich, I updated HGDP_POPs in the PR I tagged you, but I can't find HGDP_POP_NAMES.


Porting modified StablizationPlaneModifier from HoloToolkit

Overview
HoloLens 1 and HoloLens 2 support SetFocusPoint which uses a plane to do late stage reprojection. For HoloLens 1 this is the best solution to get hologram stabilization, for HoloLens 2 this is a good solution if you:

Are using Unity UI (which does not write depth)
Do not want to use depth buffer sharing (potentially due to performance concerns)
An interim solution while working to make your application properly write to the depth buffer

There are five modes that are supported in this solution:

Fixed- Sets a fixed plane at a user specified distance along the users gaze vector. 2m is the actual focus of the holograms which is why it is chosen as a default value.
Gaze Hit- Focus plane is set based on the hit position of the gaze ray and is oriented along the users gaze vector.
Plane Override- Focus plane is based on where an override plane specifies it should be. This can be programmatically updated everyone frame. This can be especially useful for planar UI elements, and will make them appear more stable
Target Override- Focus plane position is based on a transform and oriented towards the user. This is useful for if the user is looking at an object, or an object that is moving.
Off- This should be set if you want to use the default system behavior, or you want to switch at runtime to depth LSR

There is one more mode that could be added on HoloLens 2, which is an eye gaze based approach. Fundamentally, Planar LSR is about trying to determine user dwell to stabilize at that location. By implementing a eye gaze hit it will increase the likelihood that the plane is at the correct location.
Changes

From v1 implementation the plane override and target override modes have been added
Instead of a series of Booleans, the logic has been made clearer with an enum
Gizmos logic has been adjusted to render plane correctly
Added better lerp in order to decrease jitter
Removed Singleton

Verification
Reviewers should ensure that I am following the proper coding style for MRTK, verify behavior, and ensure that file is in the correct location

Overall looks good to me. Also lemme know if you want me to just make these changes (i.e. give me write to the fork's branch and I can also patch things up).

/azp run mrtk_docs

One more thing to mention here, which is that we were wanting to move these to an experimental namespace within the MRTK itself, until we have proper test/documentation coverage. It's fine to go in without making this change and I can handle moving it around to the right place afterward

Awesome stuff! Thanks for getting this in

I'll handle getting this in - the queue is a bit backed up (and I'm waiting for a particularly critical one to go before any other ones go in)

/azp run mrtk_pr

/azp run mrtk_pr

Added a commit that fixed some build warnings (a recent change made it so that we treat warnings as errors).

/azp run mrtk_pr

/azp run mrtk_pr

/azp run mrtk_pr

/azp run mrtk_pr

I think at this point all of the warnings should be resolved - just waiting on the latest CI run to validate

/azp run mrtk_docs


Pack Period

There is no schedule for pack period.

This problem has been fully addressed in version 2.1.4


Heading of Main Page

I would like to work on the main page of the site first i.e Get-Set-Go. As of now, I would like to decorate the heading. Can you please tell me a little more about the theme?

Yeah sure @Priiyaa , join us today at 9 PM and we will discuss important things about this project.
Also, feel free to drop a message on the discord channel for better communication.
Closing this issue for now.


Feature/selection without animation

I created another delegate method to notify the listened class exactly when the user tapped the button, not only after finished animation, and created a status switch to allow the button to be touchable or not

@Pelvs thanks, related to #19


Added cross platform dll export

Added cross-platform dll export. When compiling the SDK, GGPO_SDK_EXPORT should be defined otherwise, the ggponet header will import rather than export.

Let's stage all the cross platform work on the dev/crossplatform branch, please.  (see https://github.com/pond3r/ggpo/pull/17 for context).  Thanks!


Use reallyUnsafePtrEquality# for faster Id comparisons

WIP, pushing to see CI output.

No big changes performance-wise unfortunately.
report-dedup-text_master-6.pdf

Our solution in #3217 seems to work and be good enough, so this PR is no longer necessary.


[Extensibility Enhancement] Codeunit 408 "Dimension Management" - GetGLSetup procedure

Could you make GetGLSetup global?
Thanks :)

Can you please explain with code how you are going to use it in extension code?

Hi,
Se image below:


fromJS(false) should really be "{ }" ?

FromJS(true)    // true
FromJS(2.5)     // 2.5
FromJS('hello') // hello
FromJS(null)   // { } *
FromJS(false)   // { } *
FromJS(undefined) // { } *
* ok?
Thanks!!

@TCMiranda which Immutable.js version are you using? Commits https://github.com/facebook/immutable-js/commit/def9a096d25928d809930aa64fa1e4f07424f460 and https://github.com/facebook/immutable-js/commit/2f4882bcee40daa4c52cd67950fb890f62f9ce48 seem to cope with it.
I'm getting the following results when using version 3.7.5 in the browser and Node 4.2.2:
fromJS(null) // null
fromJS(false) // false
fromJS(undefined) // undefined

Anyway, I'm in favor of throwing exceptions.

@eliseumds thank you for the answer. Happens that I was outdated.
Although, I am not in favor of exceptions, since the side effects could be huge. Also, we are semantically correct.
I am closing this. Thoughts about warnings/exception could be brought to a new issue, right?
Regards,


PHPLIB-271: implemented accessors for options on core classes

Closes #375
Unfortunately, I was not able to build documentation using giza due to such an error:
Exception occurred:
  File "<my mongo docs lib>/build/docs-tools/sphinxext/intermanual.py", line 149, in _strip_basic_auth
    url_parts = parse.urlsplit(url)
AttributeError: 'Module_six_moves_urllib_parse' object has no attribute 'urlsplit'

So, documentation pages may be not ok.

The build has failed, but as I see in build log, this is an issue with build environment.

Thanks for submitting this. I will take a look once we sort out PHPC-834 and PHPLIB-261. The latter issue is especially relevant because classes other than MongoDB\Client will no longer track the MongoDB\Driver\Manager options by default, so these accessors may be able to return null (and probably will in most cases).

@jmikola please let me know here in comment when PHPLIB-261 will be done so that I can change this PR respectively.

This PR has been used as a base for https://github.com/mongodb/mongo-php-library/pull/401.


Agent admitted failure to sign using the key.

VSCode Version: Code 1.8.1 (ee428b0eead68bf0fb99ab5fdc4439be227b6281, 2016-12-19T14:41:20.664Z)
OS Version: Linux x64 3.10.0-514.2.2.el7.x86_64
Extensions:

Extension
Author
Version

format-php
Kasik96
1.1.2

material-icon-theme
PKief
1.1.5

python
donjayamanne
0.5.5

php-debug
felixfbecker
1.10.0

Theme-1337
ms-vscode
0.1.2

Steps to Reproduce:
1.define git remote using ssh
jacques@holmes:/sadmin$ git remote -v
gogs	ssh://git@centos7.maison.ca:32/jacques/sadmin.git (fetch)
gogs	ssh://git@centos7.maison.ca:32/jacques/sadmin.git (push)

But pass phrase is blank , password is always ask and refuse blank.
Keep popping up screen asking fore password, and cannot give password because they are none.
Could it be change so a blank pass-phrase is valid ?

Try setting the URL as:
ssh://git:@centos7.maison.ca:32/jacques/sadmin.git

Notice the colon after git.

#10064


[Documentation] No details on package declarations and how packages can be run at different levels

No details on package declarations and how packages can be run at different levels

From where to run the service when a package is given etc.
How to import a package and give is an alias

This is same issue https://github.com/ballerinalang/ballerina/issues/3214

Assign to Anupama.

We now have documentation that covers these aspects


merge from konsum-frontend-svelte,template-arlac77-github,template-svelte-app

package.json

chore(deps): add ^3.1.7 remove ^3.1.6 (devDependencies.vite)
chore(package): add examples (pkgbuild.groups)

.github/workflows/browser_ci.yml

chore: add ubuntu-latest (jobs.test.runs-on)

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

npm package (@latest dist-tag)
v1.34.11
GitHub release

Your semantic-release bot :package::rocket:


Bandit freezes  when start it with key -r against directory with init.py file

Bandit freezes  when start it with key -r against directory with init.py file
Steps to reproduce:

Create dir sec_scan
Create 2 files:

init.py  -  contains one string (comment - see below)
base.py   - see content below

Execute bandit -r sec_scan/

Actual result it is freezes on checking init.py file
The output of executing:
/tests/sec_scan$ ls
base.py init.py
/tests/sec_scan$ cat base.py
try:
from unittest.case import TestCase
except ImportError:
# Runing unit-tests in production environment
from unittest2.case import TestCase
from mock import patch
import logging
import os
import shutil
import subprocess
import sys
import tempfile
logging.basicConfig(stream=sys.stderr)
log = logging.getLogger("CliTest.ExecutionLog")
log.setLevel(logging.DEBUG)
class CliExectutionResult:
def init(self, process_handle, out, err):
self.return_code = process_handle.returncode
self.stdout = out
self.stderr = err
/tests/sec_scan$ cat init.py
Copyright 2013
(fuel-devops-venv)ykotko@ykotko-pc:~/FRESH-FUEL_MAIN/fuel-main/python-fuelclient/fuelclient/tests$ bandit -r sec_scan/
[bandit]        INFO    using config: /home/ykotko/FRESH-FUEL_MAIN/fuel-qa/fuel-devops-venv/etc/bandit/bandit.yaml
[bandit]        INFO    running on Python 2.7.6
----FREEZES---
/tests$ bandit -r sec_scan/
[bandit]        INFO    using config: /home/ykotko/FRESH-FUEL_MAIN/fuel-qa/fuel-devops-venv/etc/bandit/bandit.yaml
[bandit]        INFO    running on Python 2.7.6
Run started:
2016-01-27 15:32:40.661932
Run metrics:
Total lines of code: 19
Total lines skipped (#nosec): 0
Total issues (by severity):
Undefined: 0
Low: 1
Medium: 0
High: 0
Total issues (by confidence):
Undefined: 0
Low: 0
Medium: 0
High: 1
Files skipped (0):
Test results:

Issue: [blacklist_imports] Consider possible security implications associated with subprocess module.

Severity: Low   Confidence: High
Location: sec_scan/base.py:13
12      import shutil
13      import subprocess
14      import sys

Launchpad bug to Github issue import error


[BUG] Shared implementation of CyFunction and FusedFunction has the wrong name

Describe the bug + To Reproduce
# has_function.pyx
def f(x):
    return x+1

Cythonize it with cythonize -if has_function.pyx, then:
>>> import has_function
>>> type(has_function.f)
<class '_cython_3_0_0a9.cython_function_or_method'>
>>> dir(_cython_3_0_0a9)
['__doc__', '__loader__', '__name__', '__package__', '__spec__', '_cython_3_0_0a9.cython_function_or_method']
>>> _cython_3_0_0a9._cython_3_0_0a9.cython_function_or_method(
... )
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
AttributeError: module '_cython_3_0_0a9' has no attribute '_cython_3_0_0a9'

this appears to be general, but it's specifically causing issues with pickling functions in the limited API or with type-slots. I'm not completely sure why it makes a difference to those.
Expected behavior
The function name in the module should be cython_function_or_method (i.e. it shouldn't have the dotted qualname prefix)
Environment (please complete the following information):

OS: Linux
Python version 3.8.10
Cython version: current master branch (3.0.9a ish)

Additional context
It's OK on 0.29.x (you need to change the example to set binding to True)
>>> dir(_cython_0_29_23)
['__doc__', '__loader__', '__name__', '__package__', '__spec__', 'cython_function_or_method']

This looks to be due to 89d2488f7bfd6010b2a5482daede5a26759e1e6d


Errors after add LightOccluder as child of Animation Player ERROR: get: Condition ' !p_rid.is_valid() ' is true. returned: __null

Godot version:
3.1 faa49c1
OS/device including version:
Windows 10 Intel HD 4600, Linux Mint 19 Mate HD 3000
Issue description:
When I create child of anim Node(AnimationPlayer) from 2D Lighting Demo Project, a lot of this errors is shown in Output:
ERROR: get: Condition ' !p_rid.is_valid() ' is true. returned: __null
At: core/rid.h:154
Steps to reproduce:

Download 2D Lightning Demo Project
Add LightOccluder2D as child of AnimationPlayer (e.g /root/base/blue_light/anim)
Look at the Output

https://streamable.com/doj02 (colors are strange)
If you wanna disable this errors, delete LightOccluder2D
Minimal reproduction project:
light.zip

Errors still exists in 3.1 3916a5352250e004504cf97d1eb9df5305c50bbc (master)

Confirmed in the current master branch (ed22a4c45).

That's because the occluder polygon hasn't been defined yet. There's a warning in the scene tree dock, but it doesn't seem to prevent the rendering backend from trying to process the occluders.
Backtrace with GLES2:
(gdb) bt
#0  RID_Owner<RasterizerStorageGLES2::CanvasOccluder>::get (this=0x56a8a98, p_rid=...) at ./core/rid.h:150
#1  0x000000000200719c in RasterizerCanvasGLES2::canvas_light_shadow_buffer_update (this=0x58414d0, p_buffer=..., p_light_xform=..., p_light_mask=1, p_near=1.44815469, p_far=1592.97009, p_occluders=0x68ed260,
    p_xform_cache=0x688e1d4) at drivers/gles2/rasterizer_canvas_gles2.cpp:1897
#2  0x00000000035feab7 in VisualServerViewport::_draw_viewport (this=0x5532aa0, p_viewport=0x6694010, p_eye=ARVRInterface::EYE_MONO) at servers/visual/visual_server_viewport.cpp:205
#3  0x00000000035ff455 in VisualServerViewport::draw_viewports (this=0x5532aa0) at servers/visual/visual_server_viewport.cpp:343
#4  0x00000000035d307f in VisualServerRaster::draw (this=0x551b130, p_swap_buffers=true, frame_step=0.13333334028720856) at servers/visual/visual_server_raster.cpp:108
#5  0x000000000360576e in VisualServerWrapMT::draw (this=0x5888270, p_swap_buffers=true, frame_step=0.13333334028720856) at servers/visual/visual_server_wrap_mt.cpp:102
#6  0x0000000001464f7c in Main::iteration () at main/main.cpp:2022
#7  0x00000000014352cd in OS_X11::run (this=0x7fffffffcf70) at platform/x11/os_x11.cpp:3262
#8  0x000000000142578c in main (argc=3, argv=0x7fffffffd738) at platform/x11/godot_x11.cpp:56

With GLES3:
(gdb) bt
#0  RID_Owner<RasterizerStorageGLES3::CanvasOccluder>::get (this=0x568e748, p_rid=...) at ./core/rid.h:150
#1  0x0000000001ffae94 in RasterizerCanvasGLES3::canvas_light_shadow_buffer_update (this=0x56c74d0, p_buffer=..., p_light_xform=..., p_light_mask=1, p_near=1.44815469, p_far=1592.97009, p_occluders=0x67e6ff0,
    p_xform_cache=0x6782784) at drivers/gles3/rasterizer_canvas_gles3.cpp:1892
#2  0x00000000035feab7 in VisualServerViewport::_draw_viewport (this=0x552f040, p_viewport=0x65853b0, p_eye=ARVRInterface::EYE_MONO) at servers/visual/visual_server_viewport.cpp:205
#3  0x00000000035ff455 in VisualServerViewport::draw_viewports (this=0x552f040) at servers/visual/visual_server_viewport.cpp:343
#4  0x00000000035d307f in VisualServerRaster::draw (this=0x551afd0, p_swap_buffers=true, frame_step=0.12849299609661102) at servers/visual/visual_server_raster.cpp:108
#5  0x000000000360576e in VisualServerWrapMT::draw (this=0x570f6d0, p_swap_buffers=true, frame_step=0.12849299609661102) at servers/visual/visual_server_wrap_mt.cpp:102
#6  0x0000000001464f7c in Main::iteration () at main/main.cpp:2022
#7  0x00000000014352cd in OS_X11::run (this=0x7fffffffcf90) at platform/x11/os_x11.cpp:3262
#8  0x000000000142578c in main (argc=1, argv=0x7fffffffd758) at platform/x11/godot_x11.cpp:56


helper.js: Object.prototype.keyFromValue and Object.prototype.fillDefaults prevent loading mapbox-gl

const Photon   = require("electron-photon");
const mapboxgl = require('mapbox-gl');

creates the following error:
Uncaught TypeError: Cannot read property 'default' of undefined
and mapbox-gl is not loaded.
Removing Object.prototype.keyFromValue and Object.prototype.fillDefaults from helper.js allows loading and usage of mapbox-gl.
tested with:
electron-photon:  1.1.6
mapbox-gl: 1.0.0

Sorry, just saw that this issue was already fixed a year ago. The version you get with nom install still has this problem


Compiler Speed on Mac - Seems slower.

This has been discussed on IRC, so thought I'd put some data here. Hopefully it helps. This seems much more pronounced when using crystal play.
using crystal build src/app.cr -s
Crystal 0.20.4
Parse:                                00:00:00.0033080 (   0.25MB)
Semantic (top level):                 00:00:01.2392970 (  99.43MB)
Semantic (new):                       00:00:00.0034970 (  99.43MB)
Semantic (type declarations):         00:00:00.0367380 ( 107.43MB)
Semantic (abstract def check):        00:00:00.0011570 ( 107.43MB)
Semantic (cvars initializers):        00:00:00.4204640 ( 147.50MB)
Semantic (ivars initializers):        00:00:00.0105320 ( 147.50MB)
Semantic (main):                      00:00:02.1792430 ( 268.37MB)
Semantic (cleanup):                   00:00:00.0089830 ( 268.37MB)
Semantic (recursive struct check):    00:00:00.0019330 ( 268.37MB)
Codegen (crystal):                    00:00:01.2833770 ( 277.37MB)
Codegen (bc+obj):                     00:00:00.3416610 ( 277.37MB)
Codegen (linking):                    00:00:00.3288610 ( 277.37MB)

Crystal 0.20.5
Parse:                                00:00:00.0063990 (   0.25MB)
Semantic (top level):                 00:00:06.7941240 ( 107.57MB)
Semantic (new):                       00:00:00.0027940 ( 107.57MB)
Semantic (type declarations):         00:00:00.0277320 ( 107.57MB)
Semantic (abstract def check):        00:00:00.0010010 ( 107.57MB)
Semantic (cvars initializers):        00:00:00.2018070 ( 115.57MB)
Semantic (ivars initializers):        00:00:00.0082770 ( 115.57MB)
Semantic (main):                      00:00:05.6585260 ( 276.45MB)
Semantic (cleanup):                   00:00:00.0090130 ( 276.45MB)
Semantic (recursive struct check):    00:00:00.0012420 ( 276.45MB)
Codegen (crystal):                    00:00:01.6332900 ( 277.45MB)
Codegen (bc+obj):                     00:00:01.5710510 ( 277.45MB)
Codegen (linking):                    00:00:00.3209750 ( 277.45MB)

What's in app.cr?
In any case, this is a known issue that is already solved in master.  So in summary, Codegen (bc+obj) time should improve (this is the regression) and Semantic (main) will improve if you have {{ run(...) }} in your code. I'll assume app.cr uses kemal or an HTTP::Server which in turn uses ECR which in turn uses macro run :-)

sorry, yes, light on detail... Yes kemal.... Look forward to the update.
For anyone else having slow downs in crystal play, try deleting your cache files in ~/.cache/crystal/. Made my p "hello world" go down from 20sec to 3sec.
Thanks, I'll close.

We'll most likely make a new release next week, because this is quite important (the slowdown is noticeable and kind of annoying :-))

Cool, thanks.


Using icons (e.g. font awesome)

I've tried to use react-fa by setting up the following loaders:
  {
    test: /\.css$/,
    include: /node_modules/,
    loaders: ['style-loader', 'css-loader'],
  },
  {
    test: /\.woff(2)?(\?v=[0-9]\.[0-9]\.[0-9])?$/,
    loader: 'url-loader?limit=10000&mimetype=application/font-woff'
  },
  {
    test: /\.(ttf|eot|svg)(\?v=[0-9]\.[0-9]\.[0-9])?$/,
    loader: 'file-loader'
  }

This works fine on development when injecting into a HTTP page. However, when navigating to a HTTPS page, the url-loader will try to access woff2 files from a unsecured endpoint. The exact error is:
addStyles.js?b980:242Mixed Content: The page at 'https://tweakers.net/?brudy' was loaded over HTTPS, but requested an insecure font 'http://localhost:3000/js/926c93d201fe51c8f351e858468980c3.woff2'. This request has been blocked; the content must be served over HTTPS.

This seems like a tricky issue that would be a good addition to the boilerplate. Do you have an idea on how to resolve this?
Similarly, when building the extension, rather than running with webpack-dev-server, the files cannot be loaded at all.

the content must be served over HTTPS.

The problem is same with https://github.com/jhen0409/react-chrome-extension-boilerplate/pull/37#issuecomment-217719393.

Similarly, when building the extension, rather than running with webpack-dev-server, the files cannot be loaded at all.

You need to add publicPath chrome-extension://{extension-id}/ to production config, then set web_accessible_resources in manifest.json.

@jhen0409 about the second issue: how can I know the extension ID prior to building it? and what to set web_accessible_resources to?

about the second issue: how can I know the extension ID prior to building it?

This is a difficult problem, if not publish will not be determined id. I'm looking for a simple way to transform publicPath, made it can get extension id, maybe a Webpack plugin? I'll take the time to try.

and what to set web_accessible_resources to?

Add you want allow access files to this place, like .ttf file in production.

Closed via #41, just set __webpack_public_path__  dynamically at runtime in the entry point. Also let HMR works via https://github.com/glenjamin/webpack-hot-middleware/pull/109 (webpack-hot-middleware@^2.11.0).


Batch - mode possible?

Would it be possible to add something like a "batch-mode":
--batch "input-directory" "output-directory"
so that all files in that input-directory will be encoded with the same parameters (for something like TV-Shows, when you need to compress everything with like the same vmaf...)
like "alabamaEncoder encode --batch "input-dir" "output-dir" --grain -2 --vmaf_target 95"
I know it would be possible to write a simple loop with "find", but I would love to have batch - option implemented.

Can be closed.
If someone is interested:
find *.mkv -exec alabamaEncoder encode {} {}.av1.mkv --grain -2 --vmaf_target 95 ;
The command is not "clean" and needs to have the source-names without "space" in the file-name


[FEATURE] Readme logo repositioning

Description
please reposition the logo in the 4c readme.md
The file mist be like this one:
# 4C

Repository for the [4c.rocks](https://www.4c.rocks/) website.

**The Cool Community For Content Creators** or **4C**, is a community to connect with other like-minded creators, collaborate on ideas, and motivate each other to create and publish!

<img src='./4c_banner.jpg' alt='4C logo'>

## Running the project

1.  Clone the repo:

    ```console
    $ git clone git@github.com:FrancescoXX/4c-site.git
    ```

2.  Navigate to the cloned directory:

    ```console
    $ cd 4c-site
    ```

3.  Install dependencies:

    ```console
    $ npm install
    ```

4.  Run the project

    ```console
    $ npm run dev
    ```

## Contributing

All contributions are welcome. Learn more about contributing in the [CONTRIBUTING](./CONTRIBUTING.md) file.

Not sure what to contribute? Check out the [GitHub "contribute" page](https://github.com/FrancescoXX/4c-site/contribute)

## License

[MIT](./LICENSE)

ok i will do that

fixed by #193


new package for SLDS 0.9.1

It looks like there was a commit for SLDS 0.9.1 on Sept 30th, but there doesn't appear to be a new package to use this.
Right now the package only exposes SLDS 0.8.0.
Is there a way to get the updates faster?

If you've installed the package already, one option is to just use the setup menu to replace the static resource named "slds" with the most current design system .zip file (that's what I did).

I'll probably end up doing that anyway.
My concern is that there may eventually be incompatibilities. If the Lightning components for SLDSX are expecting one version of SLDS and I provide it with another could it lead to unexpected behavior if they get too far from each other.
I'm also just wondering how maintained this project is in general.

Yeah, understood...
Not sure about the maintenance aspect. The readme states it's not officially supported, so there's that :) But even so, I've found this to be incredibly useful to jump-start a custom lightning project that I built. Also if nothing else there's some great examples of how to build agnostic/reusable components, how to make use of a custom renderer, etc... especially since the current lightning documentation is a little light on stuff like that (I feel).


Switch to container-based Travis CI infrastructure

This gets us off the legacy build system, which means
that the builds will start more quickly and also likely
run more quickly (and with more consistent build times).
See https://docs.travis-ci.com/user/migrating-from-legacy.

Is this still something to be merged in?

Yeah, it should make builds faster.


Adding rsandell and dnusbaum to script-security

Description
https://github.com/jenkinsci/script-security-plugin
Just realized that @dwnusbaum and @rsandell didn't have permissions for script-security, so, hey, adding them. cc @jglick and @svanoort if signoff from other maintainers besides myself is needed.
Submitter checklist for changing permissions
Always

[x] Add link to plugin/component Git repository in description above

For a newly hosted plugin only

[ ] Add link to resolved HOSTING issue in description above

For a new permissions file only

[ ] Make sure the file is created in permissions/ directory
[ ] artifactId (pom.xml) is used for name (permissions YAML file).
[ ] groupId / artifactId (pom.xml) are correctly represented in path (permissions YAML file)
[ ] Check that the file is named plugin-${artifactId}.yml for plugins

When adding new uploaders (this includes newly created permissions files)

[x] Make sure to @mention an existing maintainer to confirm the permissions request, if applicable
[x] Use the Jenkins community (LDAP) account name in the YAML file, not the GitHub account name
[x] All newly added users have logged in to Artifactory at least once

Why should they be able to release, when they cannot commit? Per https://jenkins.io/doc/developer/publishing/source-code-hosting/

they cannot commit

Then fix that.

The bot is dead. I could fix it manually, but I will rather wait till it is back to normal. CC @olblak

@daniel-beck @jglick What @oleg-nenashev says. =) I opened this, went to give commit rights, discovered the bot was down, decided to wait til the bot came back to deal with that.


resolve mdns dat names

This allows you to clone from other people on the same network that are serving a dat by just using the dat name name as the hostname.
On one computer
dat init # set name to example
dat import some-data.csv -d test
dat serve

On another computer you now simply do
dat clone example.dat.local # clones the above dataset

awesome. what happens when it fails? is there a timeout? (on my phone)

You'll get a regular dns timeout (could not resolve host) etc

+1000!

It'd be nice to put something in the readme -- maybe 'can be cloned from the http url or the local hostname'

@karissa updated!

(this branch is failing but it passes when merged into master so yolo)

OK, I resolved the conflicts. But can we think a minute on the API?
Right now, it expects '.dat' in the end name of the package.json.

@mafintosh we tried testing this but it didn't resolve the name. looks like in this PR theres no code to actually resolve the names, just to register them. where does the resolution happen?

@mafintosh ah nevermind, was confused by the title of this pull. we got it working


Add extra HTTP client / retry options

Have a use case where I need to:

Generate a new piece of data on each retry (a header has to be updated each time)
Do some special checking on status codes etc. to determine if retry is suitable
Limit the number of concurrent HTTP socket connections to a host

Codecov Report

Merging #88 (8279627) into main (da6668c) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main       #88   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           63        63
  Lines         4778      4786    +8
=========================================
+ Hits          4778      4786    +8

Impacted Files
Coverage Δ

pkg/i18n/en_base_config_descriptions.go
100.00% <ø> (ø)

pkg/ffresty/config.go
100.00% <100.00%> (ø)

pkg/ffresty/ffresty.go
100.00% <100.00%> (ø)


Responsive Navbar / Redesigned Navbar

Summary
This PR addresses issue #285, where the current navigation bar does not adapt well to different screen sizes, particularly smaller devices like smartphones and tablets. I've redesigned the entire navigation bar to be fully responsive, with enhanced usability on mobile and desktop devices. This new design keeps the core essence of the previous navbar while improving its layout, making it easier to navigate across all screen sizes.
Changes Implemented
1. Dropdown Menu (For Mobile Devices)

Implemented a dropdown menu that appears for smaller screens, making the navigation links easier to access in a compact format.

2. Responsive Navbar
The navigation bar adjusts smoothly to different screen sizes, offering a seamless experience on mobile, tablet, and desktop.
Desktop View:

Increased navbar height for better visibility.
Adjusted font size for clearer text.
Positioned the 'TrendTrove' logo outside the container for a more prominent appearance.
Added a search button, shopping cart button, contact button, and a person icon to the right.
Changed hover effect for the 'Men/Women' dropdown to a rectangular shape (replacing the capsule effect).
Redesigned the rounded container border to be thinner for a more refined look.

Mobile View:

Implemented a hamburger menu that lists navigation links with icons aligned to the left of the hamburger.
Added a 'cancel' or 'close' button for the dropdown/sidebar menu, improving user experience.
The hamburger menu switches between being placed inside the capsule on desktop and aligned to the left on mobile.

3. File Structure

Organized the navigation bar css code into separate navigationbar.css file in a navigation folder, ensuring it can be reused consistently across the entire site. This approach improves maintainability and scalability.

Visual Preview
Here's a brief video showing the new responsive navigation bar in action, highlighting both the desktop and mobile views:
https://github.com/user-attachments/assets/29cd43f8-cee9-40f2-bd4c-ce8161354f9e
Additional Information

I’ve ensured that the new navbar follows best practices for responsive design, optimizing for performance and accessibility.
If there are any additional changes or tweaks you'd like to see, feel free to let me know!

Pending Feedback
@Tejashri-Taral , could you please review the new design and let me know your thoughts on this approach?
Looking forward to your feedback!

@Rahul-AkaVector  Please resolve the merge conflicts

@hars-21 check out and let me know any changes

@Rahul-AkaVector Please resolve the merge conflicts

I'm closing this pr as there are so many conflcts.
Make new PR with required changes


Morning session code review May 18

We have reviewed the code and great work with
✔ Using classes for organization
Issue

[x] It's recommended to sort the data before displaying the scores.

Thank You.

Thank you & noted and solved the issue too.


How should I denoise an already noisy image

First of all, thank you for your contribution. I have a lot of questions about the function of your project. When testing, I pass an image, then Gaussian blurring, and then denoise the image obtained after Gaussian blurring. How should I denoise an already noisy image?

In case of Gaussian blur, the noise2noise approach does not work because an expectation of noisy images is not equal to the original image. Please refer to the original paper for details.

Hi,Did you resolve the problem?I have a question about predicting a noisey image. Can I input a real image with noise to obtain a denoise image?Look forward to your reply.

@zhushuyun I think most of works is based on artificially added noise. It is hard to get a denoise image while you input a real image with noise.


Wrote tests and class for ControllerManager

jsdocs
adds worker manager class and tests
adds travis and coverage

pushkin generate worker apple
pushkin delete worker apple


🐛 [BUG]: Node extent broken on child nodes

Is there an existing issue for this?

[X] I have searched the existing issues and this is a new bug.

Current Behavior
Child nodes do not properly calculate node extent when contained within a parent node.
Expected Behavior
Children should be movable freely inside a parent node.
Steps To Reproduce
No response
Relevant log output
No response
Anything else?
No response

Fixed with 1.5.7


Suggestions for the<EMAIL_ADDRESS>package

Featuring Type
Others
So, what is it about?
Here are some suggestions for the package.
$inviteCodes[(option) userID;(option) splitter]
He sends all his invitation links
example :
$inviteCodes[$authorID; , ]

$inviteCount[(option) userID;codes...]
Indicates the number of people who joined by invitation code
example:
$inviteCount[$authorID;aoi-js;djs]

$splitter
It replaces ";" In the code without escaping
example:
$randomText[$authorID$splitter$clientID]
`
$clientOwnerIDs[$splitter]

$invited[userID;mention or ID]
He sends a mention of the person who invited him
example:
$invited[$authorID;mention]
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Invite info code related and more functions have been added to @akarui/aoi.invite package as aoi.js will move AoiInvite Class into a package.


Prototype for using raw SCALYR_API_KEY environment variable value as-is (e.g. kube-secrets-init use case)

This pull request is a quick prototype for the use case described in #63.
It introduces new a useRawApiKeyEnvValue chart value. When this value is set to true, scalyr.apiKey chart value will be used as-is for the SCALYR_API_KEY pod environment variable (aka secret won't be created and used).
This may come handy in situations where user uses something like kube-cloud-init which doesn't rely on Secret CRD, but it works by replacing references in the environment variable values directly with the actual secrets.
TODO

[x] Tests
[x] Documentation (document this value and use case for it)
[x] Changelog entry

@tomaz-s1
It's quite hard to see the difference between:

deployment_controller_type_raw_api_key_secret_value
deployment_controller_type
They differ on a few lines only.

It applies to other jobs too to some extent.
I am aware that GHA are not very good for writing reusable code, but I suggest creating a Jira ticket to explore how to extract the common parts that can be parametrized so the specific tests of the jobs will stand out more clearly.

@alesnovak-s1 Thanks.

It's quite hard to see the difference between:
deployment_controller_type_raw_api_key_secret_value
deployment_controller_type
They differ on a few lines only.

It applies to other jobs too to some extent.
I am aware that GHA are not very good for writing reusable code, but I suggest creating a Jira ticket to explore how to extract the common parts that can be parametrized so the specific tests of the jobs will stand out more clearly.

Agreed, there is quite some duplication between those jobs. Some of it was already refactored in the past in a reusable workflow and actions (https://github.com/scalyr/helm-scalyr/tree/main/.github/actions), but more can be done to improve it even further.


update_branch: warn doesn’t catch before createDeployment

Describe the Issue
When using the default for update_branch the expected warn and fail scenario is not run.
Action Configuration
##[group]Run<EMAIL_ADDRESS>with:
  production_environment: prod
  environment_targets: sandbox,qa,prod
  environment: sandbox
  skip_completing: true
  github_token: ***
  status: success
  reaction: eyes
  trigger: .deploy
  noop_trigger: noop
  lock_trigger: .lock
  unlock_trigger: .unlock
  help_trigger: .help
  lock_info_alias: .wcid
  stable_branch: main
  prefix_only: true
  update_branch: warn
  required_contexts: false
  allow_forks: true
  admins: false
  admins_pat: false
  merge_deploy_mode: false
##[endgroup]

Relevant Actions Log Output
Skipping commit status check and proceeding...
##[debug]raw graphql result for debugging:
##[debug]{"repository":{"pullRequest":{"reviewDecision":null,"mergeStateStatus":"HAS_HOOKS","commits":{"nodes":[{"commit":{"checkSuites":{"totalCount":1},"statusCheckRollup":null}}]}}}}
##[debug]raw admins value: false
##[debug]***** is not an admin
##[debug]precheck values for debugging:
##[debug]reviewDecision: null
##[debug]mergeStateStatus: HAS_HOOKS
##[debug]commitStatus: null
##[debug]userIsAdmin: false
##[debug]update_branch: warn
##[debug]skipCi: false
##[debug]skipReviews: false
##[debug]allowForks: true
##[debug]forkBypass: false
##[debug]environment: sandbox
##[debug]behind: false
⚠ CI checks have not been defined and required reviewers have not been defined... proceeding - OK

Extra Information
Using GHES 3.6.2 and including the log output that seems the most different from a GitHub Cloud run.

@KevinMSampson if you try the same flow on v4.6.1 do you get the same results?

if you try the same flow on v4.6.1 do you get the same results?

@GrantBirki yes.
Debug Notes
From what I can tell, this is what mainly differs:
Your test run values --- my test run values

# This might be a different issue but I'm not recognized as an admin, maybe because we only assign Teams not Users (best practice)
raw admins value: grantbirki --- false
GrantBirki is an admin via handle reference --- *** is not an admin

# Is HAS_HOOKS considered to be "behind"?
mergeStateStatus: BLOCKED --- HAS_HOOKS

# behind value is wrong
behind: true --- false

Probable cause
Current behind check logic only checks MergeStateStatus for BLOCKED and BEHIND values but we're getting HAS_HOOKS, since we use pre-receive hooks, leaving it set to false by default.
Suggestion
What do you think about updating this logic to account for some of the other values that also refer to mergeable code that may also indicate it's behind?
Misc
As for the update introduced in 4.6.1, I tested with update_branch: disabled and it work as expected!! The createDeployment call doesn't auto-sync the branch with a new, non-ci-triggering commit with a warning message, and continues with a successful message!

@KevinMSampson I'm very excited to see that v4.6.1 solved the issue for you with update_branch: disabled! As for the other issue of HAS_HOOKS I'm not entirely sure what to do about that. Taking a look at the docs, it appears that HAS_HOOKS is considered to be a "mergable" state
HAS_HOOKS

Mergeable with passing commit status and pre-receive hooks.

source

From your output though, I'm assuming by this line
```
⚠ CI checks have not been defined and required reviewers have not been defined... proceeding - OK
```

that the workflow just carried right on and merged the branch because update_branch wasn't set to disabled. I think this warrants an explicit override option to strongly prevent against the updating of branches (particularly for your use case). Thoughts?

@GrantBirki It looks like that BLOCKED conditional check does a comparison that should properly evaluate whether it's behind or not - could it be updated to run the same check for the other statuses as well?
Something like:
if (mergeStateStatus === 'BLOCKED') {

Updated to:

if (mergeStateStatus === 'BLOCKED' || mergeStateStatus === 'HAS_HOOKS') {

That sounds like a fine solution to me! I'll draft up a fix

This is now apart of v5.0.0 which is a pre-release but should be made the latest release by the end of this week. It is now usable though

Thank you!!


Convert Mixer to interface

I think we should convert the Mixer class to an interface with pure virtual methods. We can then have a Null Mixer derived class which implements those methods with simple do nothing stubs. (We can call it MixerNull to be more consistent with Mixer_SDL, which I really wish didn't have an underscore in the name).
Using a virtual base class would provide better error checking for forgotten methods in derived types. It would also eliminate the warnings currently being produced on AppVeyor. (I noticed these just after the .clang-format file was added):
C:\projects\nas2d-core\include\NAS2D\Mixer\Mixer.h(49): warning C4100: 'sound': unreferenced formal parameter (compiling source file ..\..\src\Mixer\Mixer_SDL.cpp) [C:\projects\nas2d-core\proj\vs2019\NAS2D.vcxproj]
C:\projects\nas2d-core\include\NAS2D\Mixer\Mixer.h(98): warning C4100: 'time': unreferenced formal parameter (compiling source file ..\..\src\Mixer\Mixer_SDL.cpp) [C:\projects\nas2d-core\proj\vs2019\NAS2D.vcxproj]
C:\projects\nas2d-core\include\NAS2D\Mixer\Mixer.h(98): warning C4100: 'loops': unreferenced formal parameter (compiling source file ..\..\src\Mixer\Mixer_SDL.cpp) [C:\projects\nas2d-core\proj\vs2019\NAS2D.vcxproj]
C:\projects\nas2d-core\include\NAS2D\Mixer\Mixer.h(98): warning C4100: 'music': unreferenced formal parameter (compiling source file ..\..\src\Mixer\Mixer_SDL.cpp) [C:\projects\nas2d-core\proj\vs2019\NAS2D.vcxproj]
C:\projects\nas2d-core\include\NAS2D\Mixer\Mixer.h(105): warning C4100: 'time': unreferenced formal parameter (compiling source file ..\..\src\Mixer\Mixer_SDL.cpp) [C:\projects\nas2d-core\proj\vs2019\NAS2D.vcxproj]
C:\projects\nas2d-core\include\NAS2D\Mixer\Mixer.h(142): warning C4100: 'level': unreferenced formal parameter (compiling source file ..\..\src\Mixer\Mixer_SDL.cpp) [C:\projects\nas2d-core\proj\vs2019\NAS2D.vcxproj]
C:\projects\nas2d-core\include\NAS2D\Mixer\Mixer.h(149): warning C4100: 'level': unreferenced formal parameter (compiling source file ..\..\src\Mixer\Mixer_SDL.cpp) [C:\projects\nas2d-core\proj\vs2019\NAS2D.vcxproj]
C:\projects\nas2d-core\include\NAS2D\Mixer\Mixer.h(49): warning C4100: 'sound': unreferenced formal parameter (compiling source file ..\..\src\Game.cpp) [C:\projects\nas2d-core\proj\vs2019\NAS2D.vcxproj]
C:\projects\nas2d-core\include\NAS2D\Mixer\Mixer.h(98): warning C4100: 'time': unreferenced formal parameter (compiling source file ..\..\src\Game.cpp) [C:\projects\nas2d-core\proj\vs2019\NAS2D.vcxproj]
C:\projects\nas2d-core\include\NAS2D\Mixer\Mixer.h(98): warning C4100: 'loops': unreferenced formal parameter (compiling source file ..\..\src\Game.cpp) [C:\projects\nas2d-core\proj\vs2019\NAS2D.vcxproj]
C:\projects\nas2d-core\include\NAS2D\Mixer\Mixer.h(98): warning C4100: 'music': unreferenced formal parameter (compiling source file ..\..\src\Game.cpp) [C:\projects\nas2d-core\proj\vs2019\NAS2D.vcxproj]
C:\projects\nas2d-core\include\NAS2D\Mixer\Mixer.h(105): warning C4100: 'time': unreferenced formal parameter (compiling source file ..\..\src\Game.cpp) [C:\projects\nas2d-core\proj\vs2019\NAS2D.vcxproj]
C:\projects\nas2d-core\include\NAS2D\Mixer\Mixer.h(142): warning C4100: 'level': unreferenced formal parameter (compiling source file ..\..\src\Game.cpp) [C:\projects\nas2d-core\proj\vs2019\NAS2D.vcxproj]
C:\projects\nas2d-core\include\NAS2D\Mixer\Mixer.h(149): warning C4100: 'level': unreferenced formal parameter (compiling source file ..\..\src\Game.cpp) [C:\projects\nas2d-core\proj\vs2019\NAS2D.vcxproj]

Additionally, the derived classes should make use of the override to protect against typos and base class / interface changes.

I believe this was address in PR #205.


Missing resource Assets<TextureAtlas> with specific feature combination

Bevy version
0.10.1
[Optional] Relevant system information
If you cannot get Bevy to build or run on your machine, please include:

cargo 1.70.0 (ec8a8a0ca 2023-04-25)
Linux (Pop!_OS)

If your bug is rendering-related, copy the adapter info that appears when you run Bevy.
AdapterInfo { name: "NVIDIA GeForce RTX 2070 SUPER", vendor: 4318, device: 7812, device_type: DiscreteGpu, driver: "NVIDIA", driver_info: "525.116.04", backend: Vulkan }

What you did
Bevy dependency with the following features:
[dependencies.bevy]
version = "0.10"
default-features = false
features = [
  "bevy_asset",
  "bevy_text",
  "bevy_render",
  "bevy_core_pipeline",
  "x11",
  "filesystem_watcher",
  "bevy_ui",
]

main.rs:
use bevy::prelude::*;

fn main() {
    App::new().add_plugins(DefaultPlugins).run();
}

What went wrong
What actually happened:
thread '<unnamed>' panicked at 'Resource requested by bevy_text::text2d::update_text2d_layout does not exist: bevy_asset::assets::Assets<bevy_sprite::texture_atlas::TextureAtlas>', /home/tim/.cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_ecs-0.10.1/src/system/system_param.rs:555:17
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread '<unnamed>' panicked at 'A system has panicked so the executor cannot continue.: RecvError', /home/tim/.cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_ecs-0.10.1/src/schedule/executor/multi_threaded.rs:194:60
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', /home/tim/.cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_tasks-0.10.1/src/task_pool.rs:376:49

What I expected:
The app runs without crashing.
Looks like there is either a missing feature dependency or the texture atlas should be created when another feature is enabled.

Adding the bevy_sprite feature as well fixes the problem.
I assume that bevy_text needs a dependency on that.

On main the given feature configuration doesn't trigger the error anymore, because bevy_ui has bevy_sprite as a dependency.
If you remove the bevy_ui dependency, you can still reproduce the error though.


Web push notifications are broken.

Clients no longer receiving notifications from web push.

The problem was with a recent version of Nymph that no longer woke sleeping references on get calls to guid.


Up to date Crystal changelog

See https://github.com/crystal-lang/crystal/commit/3c3d3e2b830e81de0aa39b7af0cd6f82f759c410#commitcomment-22783920
/cc @matiasgarciaisaia

I meant to do it, but somehow I never got around to it. Thanks @akzhan!

@matiasgarciaisaia @RX14 @mverzilli 🏓


Fix double backslash before escaped unicode character causing lexing error

Fix double backslash before escaped unicode character causing lexing error
What's fixed

Fixes https://github.com/Col-E/Recaf/issues/513

Does this affect disassembler output in such a way that we would need to change how unescapes work?
So for instance, the same char escape as in the linked issue, but in the assembler rather than the decompiler view?

Did some testing, seems to not have any regressions. Merging 👍


Error while trying to use agent in Laravel

Hello,
I'm using...
pinpoint-c-agent master branch
centos 8.2
php 7.3.16
and I'm facing this error when trying to access a Laravel application with the agent extension activated
[18-Mar-2021 17:33:50 UTC] [pinpoint] [420256] [420256]#0 pinpoint_start start [18-Mar-2021 17:33:50 UTC] [pinpoint] [420256] [420256]#128 add clue key:uri value:/ [18-Mar-2021 17:33:50 UTC] [pinpoint] [420256] [420256]#128 add clue key:client value:<IP_ADDRESS> [18-Mar-2021 17:33:50 UTC] [pinpoint] [420256] [420256]#128 add clue key:server value:<IP_ADDRESS> [18-Mar-2021 17:33:50 UTC] [pinpoint] [420256] [420256]#128 add clue key:stp value:1500 [18-Mar-2021 17:33:50 UTC] [pinpoint] [420256] [420256]#128 add clue key:name value:PHP Request [18-Mar-2021 17:33:50 UTC] [pinpoint] [420256] [420256]#128 add clue key:appname value:app-laravel [18-Mar-2021 17:33:50 UTC] [pinpoint] [420256] [420256]#128 add clue key:appid value:app-laravel [18-Mar-2021 17:33:50 UTC] [pinpoint] [420256] [420256]pre_init_shared_object: open address with:Permission denied
I already gave permission everywhere on these directories  and restarted both httpd and php-fpm, what am I missing?

thanks for eeliu...
https://github.com/pinpoint-apm/pinpoint-c-agent/issues/320


Files can't download

Hi Devzhk,
When I download the piececonst_r421_N1024_smooth1.mat file, the web page shows This XML file does not appear to have any style information associated with it. The document tree is shown below.
Is there any other way to download the dataset?
Thanks,
Nevo liu

Hey nevoliu,
I think the link in the README.md is out of date. I just fix it. Thanks for pointing it out.
BTW, the other way to download the dataset is to run download_data.py. For example, if you want to download the training set of the darcy dataset, run
python3 download_data.py --name darcy-train --outdir [the directory to save data]


ItemReorder wont keep original index position

Bug Report
Ionic Info
    @ionic/cli-utils  : 1.19.2
    ionic (Ionic CLI) : 3.20.0

global packages:

    cordova (Cordova CLI) : 8.0.0

local packages:

    @ionic/app-scripts : 3.1.0
    Cordova Platforms  : android 7.0.0 ios 4.5.4
    Ionic Framework    : ionic-angular 3.9.2

System:

    Android SDK Tools : 25.2.5
    ios-deploy        : 1.9.2
    ios-sim           : 5.0.13
    Node              : v8.2.1
    npm               : 5.7.1
    OS                : macOS High Sierra
    Xcode             : Xcode 9.4.1 Build version 9F2000

Environment Variables:

    ANDROID_HOME : /Users/julian/Library/Android/sdk

Describe the Bug
Using ItemReorder, if we drag an element around and, without droping it, move it back to the original position and drop it, the element will move to any other last position it was moved.
Steps to Reproduce
Steps to reproduce the behavior:

Go to the Ionic demo sample ItemReorder
Click on edit, drag an element up and down without droping it, then drop it in the original position.
The element wont be in the right position.

Expected Behavior
The element should  just stay in the original position due we didnt dropped anywhere else.
Additional Context
Somehow while we are dragging the element, an event must be getting index ids, instead of listening  that on drop. Once we have dragged the element to a different position than original, the original position index will be lost.

Thanks for your issue! Could you please check if this is still an issue in beta.17? That would be very nice :)


Fails to run in Go 1.22 RC1

The code located in the example folder does not execute successfully on Go version 1.22 RC1.
go: finding module for package github.com/grafana/pyroscope-go
go: downloading github.com/grafana/pyroscope-go v1.0.4
go: found github.com/grafana/pyroscope-go in github.com/grafana/pyroscope-go v1.0.4
go: downloading github.com/grafana/pyroscope-go/godeltaprof v0.1.4
# github.com/grafana/pyroscope-go/godeltaprof/internal/pprof
../gopath602117689/pkg/mod/github.com/grafana/pyroscope-go/godeltaprof@v0.1.4/internal/pprof/delta_mutex.go:25:20: undefined: runtime_cyclesPerSecond
../gopath602117689/pkg/mod/github.com/grafana/pyroscope-go/godeltaprof@v0.1.4/internal/pprof/proto.go:400:8: undefined: runtime_expandFinalInlineFrame

https://go.dev/play/p/rFVOk4vZiJQ?v=gotip

does it still fail on the latest godeltaprof v0.1.6 ?

Im going to close this issue. godeltaprof should be working since 0.1.5 for go 1.22. Please reopen if you find issues.


ARM64: fix double register handling for prolog/epilog

messed up history to include a different PR as well, closing to create a clean PR


Question about the network architecture

Thank u for your share. I have some questions that I wrote the codes to convert caffemodel to other file with pickle in python, and I wrote the codes to read the parameters using the file I created. At that time, I found your network architecture is not the same as standard C3D network, like conv3 conv4, and fc layer. Is that your personal change to make network performance better ?  How about the result ?

Hi @yzldw333
Can you explain more detail about the difference? I think my network architecture is same as the caffe code's version. And the TF's model is transferred from the caffe's model.


z-index issue

Wen i use Foundation i get this issue:
http://i915.photobucket.com/albums/ac352/chule143/screen1-1.jpg
but when i delete the css foundation i see this:
http://i915.photobucket.com/albums/ac352/chule143/screen2-1.jpg
What can i do to fix this?

I'm seeing a similar problem - but only with IE7. An example can be seen on a test page I've been putting together to trial Foundation at http://camranew.web-brewer.co.uk/pubs/
I'm running the various IE instances in VMs on my Linux desktop, but I don't THINK that would be likely to be anything to do with the problem. It seems OK on IE 8 & 9, Firefox and Chromium. (HTML checked and validated).
Seems to be some sort of z-index problem, though changing the z-index of the flyout class to 999 doesn't help.

I found and try to apply multiple solutions to the problem of z-index but it seems that something in foundation.css created this problem in IE7, but I can not find the class in foundation.css that may be creating this error.

Make sure the elements you're trying to z-index in IE7 are siblings of each other in the markup. Older IE has problems with the z-indexing of subsequent elements' children. Regarding the original note, without seeing the code I can't tell much more, but it in all likelihood the container for your nav and the container for your dropdown are siblings - the nav and image are not, so the image is gonna win (it comes later in the markup).

Fixes it for me, thanks smileyj68.

Thanks again.

This is my menu code:
/* For IE compatibility */
body {
behavior: url('csshover3.htc');
}
div.css_menu ul {
list-style: none;
margin: 0px;
padding: 0px;
}
div.css_menu ul li {
float: left;
margin: 0px;
padding: 4px;
border: 1px solid #ccc;
background-color: #fff;
}
div.css_menu ul li a {
display: block;
font-size: 12px;
text-decoration: none;
white-space: nowrap;
}
div.css_menu ul li div.css_submenu {
position: absolute;
display: none;
}
div.css_menu ul li:hover div.css_submenu {
display: block;
}
div.css_menu ul li div.css_submenu ul {
list-style: none;
position: relative;
top: 5px;
left: -5px;
margin: 0px;
padding: 4px;
border: 1px solid #ccc;
background-color: #fff;
}
div.css_menu ul li div.css_submenu ul li {
float: none;
margin: 4px 0px 0px 0px;
padding: 0px;
border: none;
}
div.css_menu ul li div.css_submenu ul li:first-child {
margin: 0px;
}`
And this is my htc code:
<public:attach event="ondocumentready" onevent="CSSHover()" />

What am I doing wrong?

Without a full page this is almost impossible to diagnose - try setting your LIs to display: block and give the containing row a z-index.

I looked for another module to this menu and this is the link to the website where I have this problem:
boliviarural.org/cipca_2012 /

On the page you sent, try this:
Put position: relative and z-index: 20  on div.limpiar.
Put position: relative and z-index: 21 on the row which holds div.menu_superior
In testing it on the live page with the IE debugger in IE7 that fixes the problem.

@ smileyj68 I put everything that you indicated but I do not see any change: (
http://i915.photobucket.com/albums/ac352/chule143/screen3-1.jpg

Hrmph. If this is live I can try and look at it again, but I don't think this is a Foundation issue at this point...there's a lot of other code going on there.

in your IE debugger, remove the line that links foundation.css and see the result on the menu, so I say that there may be something in the foundation that may affect IE7 in my case: (
Thanks for your help by the way :)

Hey there, I'm a web developer for YouSendIt that's meant you once before and will be using your foundation framework for a new upcoming micro site we're building that's meant to be an example on how we should build our overall website.  Been really loving this framework.
With IE 7 being the 4th most popular browser visiting our site, I have to make sure everything still looks fine on that and this z-index bug was really been causing some issues.  Adding a high z-index value for each parent above the flyout container all the way up to the container that has the columns class, seams to do the trick without adding z-index values to everything the menu floats over.

For Business

Also want to say, your 1.5 version has fixed a couple other issues I was having with the nav, so thank you for releasing that.  I can move past this nav as everything is working great now and take of the last finishing touches.  We'll send you the URL once it launches on March 6th.  Thanks Again.

Wow,works like a charm @peterlp30 thanks xD.
This is the only solution:

thanks @smileyj68  @beermad  @peterlp30  @anthonytadina  for your help :)


resolves #1, import VisUI

tested in zenlib-test
VisTextButton works fine just by importing ZenLib.
Not using uiskin.json, as we can update the skins in code like below without importing it, but we can import uiskin.json once we compose our skin file or feel like default uiskin.json provides more than default VisUI skin.
public class ZenTextButton extends VisTextButton {
    public ZenTextButton(String text) {
        super(text);
        // TODO - add default styling with ZenNinePatches once those are ready
        getStyle().fontColor = Color.RED;
        getStyle().overFontColor = Color.BLUE;
    }
}

Going to work on allowing users to load custom uiskin if they decide to do so.

Added uiSkinPath to config. Not sure if this is the best way to do this.

I think this is good to go, let me know if you have any edits that you want in!


Stepped process: Adding dark variant

@julien-deramond: design specifications for states (hover and pressed) are lacking and will be asked to designers.

Haven't looked at the code but would it be possible for the "arrow separators" to be transparent rather than black (or white by default)? It would allow to use the dark variant (or the light one) on whatever background color.

Haven't looked at the code but would it be possible for the "arrow separators" to be transparent rather than black (or white by default)? It would allow to use the dark variant (or the light one) on whatever background color.
Here is an example of rendering with a .bg-warning:

I don't think so, or at least I can't see any way atm. To sum up the behavior, the arrow shape comes from a ::after with background-clip and the small border comes from a drop-shadow implemented in the next item. If the drop-shadowis removed, set as transparent or inherit, we won't have the small border anymore. However, if you have any idea, feel free to make the changes on the PR directly :)

I don't think so, or at least I can't see any way atm. To sum up the behavior, the arrow shape comes from a ::after with background-clip and background-color: inherit and the small border comes from a drop-shadow implemented in the next item. If the drop-shadowis removed, set as transparent or inherit, we won't have the small border anymore. However, if you have any idea, feel free to make the changes on the PR directly smile

Indeed the way it is developed (and maybe there's no other way to do that) doesn't allow any transparency. So let's let it as it is for now.


About collecting logs on k8s cluster.

Thought to put logs on CephFS so it will be persisted. Then add commands like tail or head to let users to check out the contents of the log files.


Automated cherry pick of #2703: fix: guest get host nil pointer panic

Cherry pick of #2703 on release/2.10.0.
#2703: fix: guest get host nil pointer panic

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.10.0@348eb8b). Click here to learn what that means.
The diff coverage is 0%.

@@               Coverage Diff                @@
##             release/2.10.0   #2704   +/-   ##
================================================
  Coverage                  ?   7.63%
================================================
  Files                     ?     411
  Lines                     ?   64426
  Branches                  ?       0
================================================
  Hits                      ?    4921
  Misses                    ?   59081
  Partials                  ?     424

Flag
Coverage Δ

#aFlag
7.63% <0%> (?)

Impacted Files
Coverage Δ

pkg/compute/models/guests.go
0.67% <0%> (ø)

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 348eb8b...bc7c021. Read the comment docs.

/approve
/lgtm


Remove validation check for reacts

Facebook changed the backend to allow arbitrary emojis to be passed as reactions to messages. These changes can be seen already via listen, but can't be sent from the API because we do a check against what were previously the only valid emojis allowed in the call.
This PR just removes that validation so that any arbitrary reacts can be set on a message via the API.
(Tested it manually and it works)

thanks


Use SSR-compatible slot implementation in PageLayout

Problem
PageLayout.Header and PageLayout.Footer don't render server-side because PageLayout uses an SSR-incompatible approach to implement its slots API (issue).
https://user-images.githubusercontent.com/4608155/225428127-024c35b5-f01a-4a6e-a256-aeabf3dc714f.mov
Notice that the layout shifts because the header appears after the page loads.
Slack discussion for context
Solution
This PR updates PageLayout to use an SSR-compatible slots implementation.
Tradeoff
In this new implementation, PageLayout.Header and PageLayout.Footer must be direct children of PageLayout.

Dotcom uses PageLayout.Header in 3 places. In 2 of 3 usages, PageLayout.Header is a direct child of PageLayout. In the 3rd case, PageLayout.Header can easily be refactored to be direct child of PageLayout.
Dotcom doesn't use PageLayout.Footer.

Merge checklist

[x] Added/updated tests
[ ] Added/updated documentation
[ ] Tested in Chrome
[ ] Tested in Firefox
[ ] Tested in Safari
[ ] Tested in Edge

Take a look at the What we look for in reviews section of the contributing guidelines for more information on how we review PRs.

Hi!
Just leaving it here in case we need it: In case this change isn't backward compatible with instances of PageLayout in gh/gh, we can unblock this team by putting this in drafts/experimental first.

@prashkan verified that this fixes SSR issues with PageLayout in gh/gh ✅ Slack


Release 0.1.6

Fixing Bugs

Identify and resolve errors or issues regarding precision  in unittest

GitHub Actions Pipeline

Refactor workflow, build and release pipelines

Sorry for the delay... this request slip from my attention

👌

👌

👌

👌

👌

👌