Keras network works in some machines, but predicts same class in others

Please make sure that the boxes below are checked before you submit your issue.
If your issue is an implementation question, please ask your question on StackOverflow or on the Keras Slack channel instead of opening a GitHub issue.
Thank you!

[x] Check that you are up-to-date with the master branch of Keras. You can update with:
pip install git+git://github.com/keras-team/keras.git --upgrade --no-deps

[x] Check that your version of TensorFlow is up-to-date. The installation instructions can be found here.

[x] Provide a link to a GitHub Gist of a Python script that can reproduce your issue (or just copy the script here if it is short).

I used a pretrained InceptionV3 network with imagenet weights to transfer learning to an image classification problem with 14 classes. The network reaches a 92 % accuracy while training, and the first time I used it (with CPU) it achieved an 86 % over the test set. I moved to GPU after that, and since that moment the network started predicting most of the test images with the same class. The training process still achieves a 92 %. Predictions don't work even if I move to CPU again. I have tested the code in other machines, and it works only in some of them, independently of the use of GPU or not. Here is my code:
from keras.preprocessing.image import ImageDataGenerator,array_to_img, img_to_array,
load_img
from keras.layers import Dense
from keras.models import Model
from keras.applications.inception_v3 import InceptionV3
import numpy as np
import pandas as pd
from PIL import Image
import os

# Fix seed
seed = 1234

# Load test data
generator = ImageDataGenerator()
iterator = generator.flow_from_directory('Test_Mixed',target_size=(299, 299),batch_size=146,
shuffle=False)
test, y = iterator.next()
names = iterator.filenames
names = [ name[name.index('/')+1:] for name in names]

# Load pre-trained model
base_model = InceptionV3(weights='imagenet', include_top=False, pooling = 'avg',input_shape=(299, 299, 3))

for layer in base_model.layers:
    layer.trainable = False

output_layer = base_model.output

# Hidden and output layers to train
hidden = Dense(100,input_dim=1000,activation='relu')(output_layer)
final = Dense(14,input_dim=32,activation='softmax')(hidden)

# Final model
model = Model(inputs=base_model.input,outputs=final)
model.compile(optimizer='rmsprop',loss='categorical_crossentropy',metrics=['accuracy'])

# Data augmentation
generator = ImageDataGenerator(
                #rescale=0.7,
                rotation_range=20,
                width_shift_range=0.2,
                height_shift_range=0.2,
                horizontal_flip=True
            )

iterator = generator.flow_from_directory('train/',target_size=(299, 299), batch_size=32,
shuffle=True, seed = seed)

# Training
model.fit_generator(iterator,epochs=15,steps_per_epoch=20,verbose=True)

# Predictions
y_preds = model.predict(test)
labels = y_preds.argmax(axis=1)

The model.predict() function is what outputs the unexpected results. As I have said, during the training process in fit_generator the accuracy increases always very nicely, but then predictions are bad. To test overfitting I have also tried to use model.predict() with the training set, obtaining bad results again. What I find more confusing is the dramatic changes from  other computers (and the first attempt in my machine) to the results happening now: from 86 % test accuracy to same class predictions, which is less than 10 % accuracy. The code has been the same all this time.

It appears you're describing the classic overfitting problem, whereby the model learns how to increase its accuracy on the training set "too well". Instead of a colour detector being able to identify pictures of grass are green or a sky is blue, an over-trained model might learn to detect patterns within the grass that might not be reproducible when testing against a picture of a meadow, for example.
This problem can be mitigated by adding a noise layer to randomly reduce some of the input data, so that the model will have to learn how to make sweeping generalisations rather than abnormally specific rules.
https://keras.io/layers/noise/

I think overfitting is not the problem. When I run the code in a friend's computer it always outputs good predictions. The good or bad predictions depend on the used machine.

May be that has to do with a random seed. I mean network parameters initializations. You can set up a constant seed

Do you mean fixing the seed in the kernel_initializer argument? I have also tested it a few days ago. However the results seem still to be machine-dependent. It doesn't mind if I fix a seed or not, the prediction results don't change drastically within the same machine, only from a machine to another.

I mean this
import os
os.environ['PYTHONHASHSEED'] = '0'

import keras
import random as rn
import numpy as np

np.random.seed(1)
rn.seed(1)

Anyways, without setting the seed the differences are not significative in the same machine. I've just tried that and the predictions still are good only in some machines, and same-class in my computer.


Including Release ID as a Field

Can the Release Pipeline Name be used in a field to indicate in which release a change was included?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: dc1abec4-edfe-b170-259b-cd1fa37dead0
Version Independent ID: 66792b32-3ed8-5d33-82be-66a77f8c35fb
Content: Build and test integration queries - Azure DevOps
Content Source: docs/boards/queries/build-test-integration.md
Product: devops
Technology: devops-agile
GitHub Login: @KathrynEE
Microsoft Alias: kaelli

@salipour1105 Thank you for the question.
All work item fields can be found in the field index.
For any items not included, you will need to either use custom fields and update with something like the REST API, or solicit feedback from the product team here to have additional fields added.


JMLR Paper Roadmap

I thought it might be worthwhile to have a list of deliverables that can also serve as a roadmap for the POMDPs.jl paper.
The following is a minimal list of solvers I think we need to support. A finished solver should have extensive documentation, run tests and should be validated.
Have to have solvers:

[ ] ValueIteration (need docs)
[ ] MCTS (need docs)
[ ] QMDP (broken)
[ ] FIB (no repo yet)
[ ] SARSOP (.pomdpx file generator is broken)
[ ] POMCP
[ ] DESPOT

Nice to have solvers (all Julia implementations and not wrappers):

[ ] PBVI and simple variants (no repo)
[ ] Witness  (no repo)
[ ] AMDP (no repo)
[ ] Perseus (no repo)

Most of the solvers do not work with the current version of POMDPs.jl due to recent changes. I am in the process of fixing them, and will update the list as I go.
The following support tools are provided:

[ ] POMDPToolbox (still not clear what this should contain)
[ ] POMDPXFile (SARSOP file generation and .policy file parsing)
[ ] POMDPFile (no repo, would be nice to have but not vital)

Miscellaneous:

[ ] Main Doc (unsure where it should be hosted and in what format)
[ ] POMDPs.jl-Lite (name not finalized :D): This is a wrapper to simplify the API for the user. Hao Yi said he might be interested in working on this.
[ ] [POMDPModels.jl] (https://github.com/sisl/POMDPModels.jl) (example problems for new users)

Benchmarks against the following solvers would be a nice addition to the paper:

[ ] AIToolbox (C++, supports VI, MCTS, QMDP, POMCP, Witness, AMDP, Perseus, and others)
[ ] pomdp-solve (C++, supports PBVI, Witness and others)
[ ] MDP Toolbox (MATLAB, supports VI, policy iteration and LP methods)
[ ] PyMDP Toolbox (python, supports VI and variants)

Please add or edit as you see necessary.

Nice outline. I'd think that a LaTeX repository on GitHub is the way to go for the main document.

Closing this, since the paper is out.


fix max elasticsearch memory

Signed-off-by: Timothy Ehlers<EMAIL_ADDRESS>Description
reconfigure fails on big servers.
Issues Resolved
https://github.com/chef/chef-server/issues/2154
Check List

[x] New functionality includes tests
[ ] All buildkite tests pass
[ ] Full omnibus build and tests in buildkite pass
[ ] All commits have been signed-off for the Developer Certificate of Origin. See https://github.com/chef/chef/blob/master/CONTRIBUTING.md#developer-certification-of-origin-dco
[ ] PR title is a worthy inclusion in the CHANGELOG

Added a unit test for this.

@tehlers320 This looks good.  When you say reconfigure fails, do you mean you were hitting the preflight validator here:
https://github.com/chef/chef-server/blob/master/omnibus/files/private-chef-cookbooks/private-chef/libraries/preflight_indexing_validator.rb#L88
or were you hitting another error?

Just FYI, this is good to merge but we are currently investigating a sqitch+perl issue in the build pipeline so are holding off on merging things until we resolve that.

rebased and merged from #2159. Thank you for your contribution @tehlers320!


Configuration of Tools

Hello,
I see that I am able to configure tools in the config folder, but I would like if I could configure sword and axe damage separately, as well as configuring attack speed of each separately too. Would it be possible to add those options in the configs?
From my understanding with zero knowledge of modding, I am unable to configure each myself by downloading the source code zip file due to private libs.

I'm going to go half way on this.  I'm doing to have config options to adjust the sword and axe attack damage, but not the speed.  Reason being, vanilla uses negative numbers for speed internally and it will lead to confusion by players tweaking the values.  This will be added starting with 1.20.6.


msal-node’s configuration types doesn’t allow elements on the clientCapabilities (type [] does not allow elements)

Core Library
MSAL Node (@azure/msal-node)
Core Library Version
Latest
Wrapper Library
Not Applicable
Wrapper Library Version
Not applicable
Description
The type of clientCapabilities On msal-node is [], but that type does not allow properties to be set. It should be at least string[].
This is what I’m seeing when I try to pass values in that property. Let me know if I’m missing something.
Error Message
[string] is not assignable to type [] or string[] is not assignable to type []
Msal Logs
No response
MSAL Configuration
{ auth: { clientCapabilities: [“CP1”] } }

Relevant Code Snippets
{ auth: { clientCapabilities: [“CP1”] } }

Reproduction Steps
TypeScript would probably give the error out if a TypeScript sample is made in which any string array is passed to this property.
Expected Behavior
String arrays should be allowed.
Identity Provider
Other
Browsers Affected (Select all that apply)
Other
Regression
No response
Source
Internal (Microsoft)

I am not sure if this is supposed to be string. @tnorling to comment once.

@sameerag Yes it should be type string[]. Thanks @sadasant, I'm surprised this didn't get caught earlier...


Windows 11 specifics

I wish there was more information about specifics about Windows 11 - especially with Hyper-V clusters and tpm support.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 12b03f10-0639-a434-6737-b7f69f9d0473
Version Independent ID: d2acf26c-c9aa-04a7-92e8-bd28e46f85f6
Content: Supported configurations for Remote Desktop Services
Content Source: WindowsServerDocs/remote/remote-desktop-services/rds-supported-config.md
Service: windows-server
Sub-service: remote
GitHub Login: @lizap
Microsoft Alias: elizapo

We hugely appreciate your contribution, feedback, and support to our technical documentation.
We’ve phased out GitHub Issues on this repository as the feedback mechanism for content and have replaced it with a new feedback system. For more information see, Content User Feedback. As part of this rollout, we are migrating your issue where our team will use your comments to improve the documentation experience. Unfortunately, this does mean you won't be able to access this issue after the migration is complete.
All issues will be migrated by Thursday 29th August 2024.
Once again, thank you for your valuable feedback, we hope you’ll continue to contribute using our new feedback system.


keda.k8s.io_scaledobjects_crd.yaml create error in k8s1.11

kubectl apply -f https://github.com/kedacore/keda/blob/master/deploy/crds/keda.k8s.io_scaledobjects_crd.yaml
error: error parsing https://github.com/kedacore/keda/blob/master/deploy/crds/keda.k8s.io_scaledobjects_crd.yaml: error converting YAML to JSON: yaml: line 118: mapping values are not allowed in this context
k8s1.11.

hi @zroubalik .
I think you are more familiar with crd, if k8s1.13, no problem. but for k8s1.11 , failure.

@iyacontrol thanks! I will take a look on that, but it seems like issue with old k8s, so there's a question whether we want to support that version of k8s.

I'm tracking this in https://github.com/kedacore/keda-docs/issues/49 already, we should indeed define a minimum bar to comply with imo.

closing this in favor of https://github.com/kedacore/keda-docs/issues/49


docker: split client providers into a local docker client and a cluster docker client

Hello @landism,
Please review the following commits I made in branch nicks/dockerclients:
a3883595b188e34281755575852a386cfd42f702 (2019-06-21 17:48:51 -0400)
docker: split client providers into a local docker client and a cluster docker client

so happy to finally remove the dependency of the synclet on minikube code!
this is part of a bigger cleanup of how we use the docker client


Enable updating collector endpoint while Emitter is running (close #508)

This PR addresses issue #508 which reported that updating the network endpoint doesn't have any effect. I found that there are two possible reasons for this:

the Emitter is currently running, or
it uses a custom network connection.

I don't think that anything should happen in the second case. It sounds reasonable that custom network connections are not updated by setting the endpoint in tracker controller (let me know if you think otherwise).
But the first case is less intuitive and can be a problem for several reasons:

the Tracker calls flush() on Emitter right after initialisation which means that the Emitter starts running and it is not possible to update the endpoint right after the tracker is initialised, and
Emitters can be running for quite a long time. Even when all events are sent, attemptEmit() function goes to sleep a number of times checking for new events.

So I think it's reasonable to enable updating the network configuration while the Emitter is running. This PR enables that and removes the check from setters for network configuration in Emitter. I didn't want to have the network connection change during emitting and so I made the attemptEmit function accept a NetworkConnection to be used while it is running. The network connection is only refreshed in the attemptEmit after the sleep while waiting for new events.
I wrapped the networkConnection instance variable in an atomic reference. I don't think it's extra necessary in this case, probably it's overly cautious.

Thanks for your pull request. Is this your first contribution to a Snowplow open source project? Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
:memo: Please visit https://docs.snowplowanalytics.com/docs/contributing/contributor-license-agreement/ to learn more and sign.
Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.


Update example: Remove bbox property from spatial and remove BOM character

The example dataset currently has bbox property for spatial, which is redundant with coordinates. coordinates basically contains the same info, but is a required geojson property. Removing it indicates to users what is necessary. See also https://github.com/gbif/ipt/issues/2126
The observations.csv also contained a BOM character at the start, which causes the automapping in the IPT to fail. It is a minor annoyance that it made it into the v1.0 dataset, which is attached to the paper and which people can download from https://camtrap-dp.tdwg.org/example/
One option would be to update the download page, so users can also point to the latest (development) version. @kbubnicki?

Update: the version attached to the paper should not contain the BOM character. So it's only on the download page that people will get the 1.0 version with BOM character (which only affects the IPT afaik).


v1.3.1 raises loading errors

v1.3.1 started breaking all our builds this morning. I haven't had a chance to investigate exactly why yet, but below is a stack trace.
Workaround: Rollback to v1.3.0
/Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-reporters-1.3.1/lib/minitest/reporters/base_reporter.rb:114:in `const_get': wrong constant name initialize (NameError)
	from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-reporters-1.3.1/lib/minitest/reporters/base_reporter.rb:114:in `block in load_constant'
	from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-reporters-1.3.1/lib/minitest/reporters/base_reporter.rb:113:in `each'
	from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-reporters-1.3.1/lib/minitest/reporters/base_reporter.rb:113:in `inject'
	from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-reporters-1.3.1/lib/minitest/reporters/base_reporter.rb:113:in `load_constant'
	from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-reporters-1.3.1/lib/minitest/reporters/base_reporter.rb:62:in `test_class'
	from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-reporters-1.3.1/lib/minitest/reporters/base_reporter.rb:18:in `before_test'
	from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-reporters-1.3.1/lib/minitest/reporters/default_reporter.rb:37:in `before_test'
	from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-reporters-1.3.1/lib/minitest/reporters.rb:47:in `block in run_with_hooks'
	from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-reporters-1.3.1/lib/minitest/reporters.rb:47:in `each'
	from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-reporters-1.3.1/lib/minitest/reporters.rb:47:in `run_with_hooks'
	from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-5.11.3/lib/minitest.rb:960:in `run_one_method'
	from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-5.11.3/lib/minitest.rb:334:in `run_one_method'
	from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-5.11.3/lib/minitest.rb:321:in `block (2 levels) in run'
	from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-5.11.3/lib/minitest.rb:320:in `each'
	from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-5.11.3/lib/minitest.rb:320:in `block in run'
	from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-5.11.3/lib/minitest.rb:360:in `on_signal'
	from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-5.11.3/lib/minitest.rb:347:in `with_info_handler'
	from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-5.11.3/lib/minitest.rb:319:in `run'
	from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-5.11.3/lib/minitest.rb:159:in `block in __run'
	from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-5.11.3/lib/minitest.rb:159:in `map'
	from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-5.11.3/lib/minitest.rb:159:in `__run'
	from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-5.11.3/lib/minitest.rb:136:in `run'
	from /Users/dir/vendor/bundle/ruby/2.4.0/gems/minitest-5.11.3/lib/minitest.rb:63:in `block in autorun'

base_reporter tries to load the constant referenced by the test class name, but the name is not a valid constant name for classes defined by describe blocks. should not be trying to load the constant by this class name.

Agree, I implemented some integration specs where the main block is not the name of the existing class but describes tested functionality. I had to rollback to v1.3.0 as well.

same here:
/root/.rbenv/versions/2.4.4/lib/ruby/gems/2.4.0/gems/minitest-reporters-1.3.1/lib/minitest/reporters/base_reporter.rb:114:in 'const_get': uninitialized constant Rails5x (NameError)
rolling back ...

this is a regression from fix for #265 :(

if someone can create a unit test to catch the problem it would be a great help for me (for some reasons current tests don't catch it :(
In any case I will try to work on this over weekend

Are you still looking for a unit test? Sorry, for the late answer.
I can create one for you.
The short answer is that my failing tests start like this:
require "minitest_helper"
describe "Rails5x" do
    ...

Ok, here it is
require 'minitest/spec'
require 'minitest/autorun'
require 'minitest/reporters'

MiniTest::Reporters.use! MiniTest::Reporters::SpecReporter.new

describe 'Rails5x' do
  it 'should expose the reporter bug' do
    true.must_equal true
  end
end

Unit test that can be added to spec_reporter_test.rb
    def test_report_for_describe_not_using_const
      klass = describe("whatever") { it("passes") { assert true } }
      runnable = klass.runnable_methods.first

      # Run the test
      result = klass.new(runnable).run
      @reporter.start
      @reporter.record(result)

      begin
        @reporter.report
      rescue => e
        error_msg = "error executing @reporter.report, #{e}"
      end

      refute error_msg, error_msg
    end

I tried a stab at a fix, but I'm unsure if returning a String, when the klass errors on const_get is the right thing to do. Would need more test coverage. In base_reporter.rb:
      def load_constant(name)
        name.to_s.split('::').inject(Object) do |namespace, const_name|
          return name unless const_name =~ /^[A-Z]/
          namespace.const_defined?(const_name) ? namespace.const_get(const_name) : name
        end
      end

@prettycoder @os97673 Maybe add the suggestion as a pull-request will be easier for maintainers to merge. Please create pull request, and refer this issue.
PS. I also had to roll pack to v 1.3.0, and think it is urgent to get a fix out.

the test is not failing :(  Help needed.

I'm sorry, I should have done the PR myself.
I'm wondering if you need to move one end, so that the test is within the SpecReporterTest class.
I'll be back at work in 12 hours and can help more.

BTW: I checked the methods -- mainly report in minitest-reporter and minitest -- that use the result from load_constant and it looks like returning a String won't break anything.

My bad, mostly android developer nowdays and my current environment is not very friendly :( Windows)

let's move discussion to #268

You don’t close an issue because there’s an open pull request. Instead, you reference the issue in the pull request so the issue auto-closes when the pull request is merged. ¯_(ツ)_/¯

For me both the PR and the issue is the same (PR is just more convenient to work with) and I see no reason to keep both opened.

1.3.2.beta1 has been release, please test

@os97673 It's working fine here!

also works for me:
gem "minitest-reporters", "~>1.3.2.beta1", require: false


Multiarch support

Hi,
We been adding multi-arch support to our cloud-native-postgresql operator in the past few days but we hit a few bugs that were fixed on https://github.com/operator-framework/operator-registry but in community-operators the catalog is created using the old image upstream-registry-builder which is reported as deprecated since it use deprecated apps https://github.com/operator-framework/operator-registry/issues/805
Possible solution, is it possible to switch and use the latest operator-registry/opm image? We can propose a PR but we don't really know if the community-operators wants to update that.
Our understanding is that we just need to update this Dockerfile https://github.com/k8s-operatorhub/community-operators/blob/main/upstream.Dockerfile if that's right we can propose an update.
Best Regards,

@dmesser We know that probably is not the solely change but we need to start at some point and start doing some PRs from there, and basically we need to start by knowing where the image is built and start to do some work on it, otherwise we cannot help, and as you can see there's already people knowing about this and deprecate the use of the old image is important since it can be discarded in the near future.

So for your information the ticket on operator-framework/operator-registry https://github.com/operator-framework/operator-registry/issues/805 has been closed expecting to the community-operator switch images

Any update about it?

@ionutz89 @sxd good news! Priorities have changed and we are going to deliver multiarch k8s index.

@sxd we are producing multiarch index image now. Can you please check if ok with you? If ok please close issue. Thanks


fix: Example in README is incorrect #402

What issue does this PR address?
Example in README is incorrect #402
Does this PR introduce a breaking change?
No.
Please check if the PR fulfills these requirements

[x] The commit follows our guidelines
[x] Unit Tests for the changes have been added (for bug fixes / features)

@mivano This can be merged as well. Trivial typo.


Support for i18n and customization of error messages

Coverage decreased (-0.09%) to 92.519% when pulling a52d6ed4f9025f843c6709fbafd13de8e8a6d210 on edgarmueller:master into d1ded6955213cd8da305903b54186a4c24920263 on eclipsesource:master.


rocAL - SSD training doesn't converge with MIVisionX TOT

@swetha097 Opening an issue to track the SSD issue

@swetha097 we are still seeing issues with --prefetch for NHWC script right?

I think there is no issue with convergence @LakshmiKumar23 , with the lastest rocm 5.2.3 docker, we see it going to a hanged state / leading to HSA_STATUS_ERROR_MEMORY_APERTURE_VIOLATION.
All trainings work on rocm5.2.0 docker


dart2js: Function isn't equivalent to itself

This issue was originally filed by<EMAIL_ADDRESS>
dart2js will often compile functions in such a way that using them results in the same function not being equivalent to itself.
Running
t1.get$_privateFunct() === t1.get$_privateFunct()
Results in false :(
Also t1.get$_privateFunct() doesn't even return a function??? I'm using this in a Chrome extension api and I'm confused how this even works in the first place. Then again it's Javascript so I'm not surprised. Anyways, this is a problem when writing a Chrome Extension and the event listeners need the same function object to properly remove a listener.
Easy repro:
void main() {
  new MyClass();
}

class MyClass {
  MyClass() {
    print("In js \_privateFunct === \_privateFunct is false here");
  }

  void \_privateFunct() {
    print("doing things");
  }
}

The workaround I've found is to do:
void main() {
new MyClass();
}
class MyClass {
MyClass() {
_privateFunctWrapper = () => _privateFunct();
print("In js _privateFunctWrapper === _privateFunctWrapper is true here");
}
Function _privateFunctWrapper;
void _privateFunct() {
print("doing things");
}
}

I think this is working as intended, at least regarding identity() within Dart code.
The behavior of the JS generated by dart2js is more a property of dart2js's ABI/interop layer than it is the language. As far as I know, dart2js doesn't have an officially supported ABI—it doesn't make any claims about what the JS it generates looks like and how you can use it from JS. Instead, you need to explicitly use JS interop.


Track object lifecycle inside tracer?

I.e., record when an object was created and, maybe, when it becomes unreferenced.
We don't have any use cases for this yet, but it might be an interesting feature.

There was a feature request to find out when an object was created. Tracing this in the memory slot 0 should be simple by overriding the new primitives. The construction time of objects could be requested into the history explorer. The trickiest part might be updating the range retracing simulator to deal with shortened memory slices returned by the memory.


Fix PhoneNumber in es-MX

Trying to generate a phone number in the es-MX locale was throwing a translation error:
I18n::MissingTranslationData (translation missing: en.faker.phonenumber.lada_dos)

The issue seems to be that Faker::Base.parse doesn't properly convert the class name to the snake case values used by the yaml file. It seems like a lot of the classes work around this by just defining named methods and avoiding the letting parse try to do a fetch.
I added just the bare minimum to get parse working since I didn't want to pull all of underscore over from ActiveSupport.
Fixes #1184

Yeah happy to. Would be nice if we could get Travis or CodeClimate running it.

Huh wonder why it didn’t report rubocop style issues on the PR then. Needs a rebase then?

Maybe you don't have Rubocop violations?
Just update your branch with master. The steps should be something like item 8.

There was some indenting it didn't like. I fixed that and added the changelog entry like you'd requested.

Gave it another rebase around the recently changelog updates.

@vbrazo could you give this another look? I've had to rebase twice already to keep up with conflicts in the changelog.

For sure. Sorry for the delay. Things have been busy on my side.


Support for GitHub Enterprise

I would like to use this with GitHub Enterprise, but it looks to be hardcoded to use https://api.github.com and https://uploads.github.com. Would it be possible to get an input argument to set the url for github?

Thanks for your request. I will check how I can support enterprise as well.

You can try the latest version v0.8.0 which has a new input value githubAPI to customize the GitHub API BaseURL.


Inheritance in TG.Program

Every TG.Program needs the same two functions getParamsand setParamValue.
getParams: function () {
	return params;
},
setParamValue: function ( id, value ) {
	params[ id ] = value;
},

Could be nice to be implemented just in TG.Program, not on every subclass.

Yeah, the problem is that inheritance works backwards now... TG.Program adds stuff to the program. In order to implement the proper way the code becomes a bit more verbose but I'll see if I can find a way :+1:


1.18.1 No outlines from divination rod

Describe the bug
Blocks aren't outlined by the divination rod. The blocks generate just fine and the item in hand changes sprite from distance correctly, there's just no outline on the block.
To Reproduce
Steps to reproduce the behavior:

Place/Find Iesnium
Attune divination rod
Use divination rod
Divination rod turns purple, but no outline on the ore.

Expected behavior
The block is outlined.
Screenshots
https://user-images.githubusercontent.com/45697042/163493604-eb7d13fb-115b-4c70-9951-96cd3b70ed59.mp4
System (please complete the following information):

Occultism Version: 1.18.1-1.26.9
OS: Linux (openjdk 18 2022-03-22)
Minecraft Version: 1.18.1
Modpack Link and Version, or list of mods:

(Note: OptiFine is being used in the video and is on the list, but I have tried in a separate singleplayer world without OptiFine installed and the issue persists.)

Additional context
The ore block I spawn in the video appears to flash a couple times, but this does not happen when OBS isn't running.

1.18.1 is no longer supported as forge moved on to 1.18.2 (the versions are not compatible, and maintaining both is too much of a strain to keep up)
Does the issue reproduce with just Occultism + Dependencies on the latest 1.18 release?

No, it works fine in the 1.18.2 version.


Adjust font text such that it won't be drawn inside the bow line in image_processing.draw_box

Description:
The image_processing.draw_box function is drawing the label text inside the line. This adjusts the text offset to account for the font size.
Related issue: fixes #27766
Checklist:

[X] The code change is tested and works locally.
[X] Local tests pass with tox. Your PR cannot be merged unless tests pass
[X] There is no commented out code in this PR.
[X] I have followed the [development checklist][dev-checklist]

LGTM


webui: upgrade dependencies

Codecov Report

Merging #170 into master will decrease coverage by 1.14%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #170      +/-   ##
==========================================
- Coverage    67.4%   66.25%   -1.15%
==========================================
  Files          23       23
  Lines        2611     2611
==========================================
- Hits         1760     1730      -30
- Misses        676      712      +36
+ Partials      175      169       -6


AxiIIC usage issue

We are trying to use the AxiIIC library but not able to progress.
Can some please help. There is no example on how to use the AxiIIC.
> from pynq import Overlay
> overlay=Overlay("YaViCamera.bit)
> from pynq.lib.iic import AxiIIC
> i2c = overlay.ip_dict['axi_iic_0']
> i2cNew = AxiIIC(i2c)

ERROR message:
Traceback (most recent call last):
File "", line 1, in
File "/home/xilinx/pynq/lib/iic.py", line 80, in init
AxiIIC._initialise_lib()
File "/home/xilinx/pynq/lib/iic.py", line 68, in _initialise_lib
AxiIIC._lib = AxiIIC._ffi.dlopen(_lib_location)
File "/usr/lib/python3/dist-packages/cffi/api.py", line 141, in dlopen
lib, function_cache = _make_ffi_library(self, name, flags)
File "/usr/lib/python3/dist-packages/cffi/api.py", line 802, in _make_ffi_library
backendlib = _load_backend_lib(backend, libname, flags)
File "/usr/lib/python3/dist-packages/cffi/api.py", line 797, in _load_backend_lib
raise OSError(msg)
OSError: cannot load library '/usr/local/lib/python3.6/dist-packages/pynq/lib/libiic.so': /usr/local/lib/python3.6/dist-packages/pynq/lib/libiic.so: cannot open shared object file: No such file or directory.  Additionally, ctypes.util.find_library() did not manage to locate a library called '/usr/local/lib/python3.6/dist-packages/pynq/lib/libiic.so'

You can use the img PYNQ 2.4，or copy the /usr/local/lib/python3.6/dist-packages/pynq/lib/libiic.so in img PYNQ 2.4 or the attechment to the same path in your rootfs.
libiic.zip

Hi @Swacheta. Looks like your issue was answered elarlier.
However, even if you are not satisfied, I kindly need to ask you to redirect your question to our forum: https://discuss.pynq.io
That's the dedicated place to receive support from the community.
The issue tracker here is to report bugs in the codebase.
Closing this now, thanks in advance for your collaboration.


JS Not working with new rails app

Hi all,
I followed the instructions as per https://primer.style/view-components/#installation in a new rails 7 app, but I get the following error
The asset "primer.js" is not present in the asset pipeline.
when adding javascript_include_tag. I guess for rails apps using sprockets it is needed to include in the documentation to add a primer line into manifest.js file too, however in this gem I only see exposed primer_view_components.js, not primer.js.
Many thanks

Hey @muriloime, thanks for bringing this up, and apologies for missing it! As you discovered, the fix is to use <%= javascript_include_tag("primer_view_components") %> instead. The docs should be fixed once this PR lands.


How to use gofs as a library

Hi.
Looks like gofs is a big project. How do I use this as a library for synchronizing directory in my local machine to ssh server ?

Currently support synchronizing directory in your local machine to the gofs server, you can use the gofs as a library like the following code:
package main

import (
	"os"

	"github.com/no-src/gofs/cmd"
)

func main() {
	cmd.RunWithArgs([]string{
		os.Args[0],
		`-source=rs://<IP_ADDRESS>:8105`,
		`-dest=./dest`,
		`-users=gofs|password`,
	})
}

And more expose functions like Run and RunWithConfig.
More standard protocols like the SFTP will be supported in the future, if you don't want to deploy the gofs server side.

Great, thanks!


Please share the link to official resources where source numbers could be taken

Great charts! Great job!
But I have 1 question about source of data, which was used.
As I could see from code - data is taken  from url
https://www.arcgis.com/sharing/rest/content/items/b5e7488e117749c19881cce45db13f7e/data
But are there any official resources (with similar data) which could be used for verification (citing) ?
For me especially interesting is +/- fine grained death rate statistics.
I've spent a little while by googling, and I could see for example Eurostat Table Deaths (total) by month
But for some unknown reason it contains NO DATA for year 2020 (disregarding that fact that month drop-down shows only passed months of year 2020).
Also I've looked at official site http://www.statistikdatabasen.scb.se/pxweb/en/ssd/
But I could not find there any fine-grained (by time) statistics of deaths total (only yearly, no monthly, no daily ...)
So for example, from what I know, some official daily statistics for Spain could be found at
https://www.isciii.es/QueHacemos/Servicios/VigilanciaSaludPublicaRENAVE/EnfermedadesTransmisibles/MoMo/Paginas/Informes-MoMo-2020.aspx
It is in "poor format"  (batch of pdf-s), and some charts are contradictive (has different values for the same day) - but they are official ...
So if you have some links to official resources from where one could take that timely fine-grained death-rate, it would be really great if you share them.

Just to clarify, (for daily total mortality) are you using data from
https://www.scb.se/om-scb/nyheter-och-pressmeddelanden/scb-publicerar-preliminar-statistik-over-doda-i-sverige/
https://www.scb.se/hitta-statistik/statistik-efter-amne/befolkning/befolkningens-sammansattning/befolkningsstatistik/pong/tabell-och-diagram/preliminar-statistik-over-doda/
or some other sources ?
I guess this (totals) are crucial for understanding "whole picture".
Honestly, I am quite surprised why this statistics is NOT included in table on WIKI, as a reference date (at least to aware how big that "covid" numbers comparing with current and historical totals ...)
https://en.wikipedia.org/wiki/2020_coronavirus_pandemic_in_Sweden

I'm not sure what you are asking? These are the official numbers from FHM hosted on arcgis.com. You can find the link on: https://www.folkhalsomyndigheten.se/smittskydd-beredskap/utbrott/aktuella-utbrott/covid-19/bekraftade-fall-i-sverige/

Yes, your answer is exactly what I've asked - some official link for citing (verification).
I was just thinking that if I'll make a link to that data/charts, I should have valid proof that is is official.
So link that you've gave to me provides that proof.
I guess it would be nice and helpful to mention that in in README file in the root of repository.
And just to explain my "concerns" - I was looking at about section of hosting site
https://www.esri.com/en-us/contact
and could not associate it with Sweden officials easily 😄

And also what was interesting for me to understand, that according to
https://www.scb.se/hitta-statistik/statistik-efter-amne/befolkning/befolkningens-sammansattning/befolkningsstatistik/pong/tabell-och-diagram/preliminar-statistik-over-doda/
Total morality for 15 days of April 2020 is
4713 (2*4713 == 9426)
While according to Eurostat Table Deaths (total) by month
Total morality for entire March 2018 is
9437 (9437 / 2 == 4718.5)
So it looks like in April 2020 Sweden will have less total deaths that in March 2018.
Maybe comparing different months is bit speculative, but still I guess it could be helpful in understanding current situation in Sweden..

Hi! Sorry, I'll add a readme to explain tomorrow. You can find the latest data here: https://www.folkhalsomyndigheten.se/smittskydd-beredskap/utbrott/aktuella-utbrott/covid-19/bekraftade-fall-i-sverige/
FHM do not archive old data, so the place to find that is here in the data folder.


Filemanager is missing

Hi, I have a problem with my P351 and ArkOs Final build.
My Problem:
Under "options" I have only 3 entries.
Network info, Enable Remote Services, Updates
I am sure I had many other entries, especially "File manager"
Do you have an idea?
thx

Sounds like some of the scripts were deleted in the /opt/system folder.  Have you been in this folder changing things?  If not, how do you normally reboot and shutdown the system?


outlineWidth has no visible effect

Reported on the forum. Here's a Sandcastle example.
var viewer = new Cesium.Viewer('cesiumContainer');

viewer.entities.add({
    polygon : {
        hierarchy : {
            positions : Cesium.Cartesian3.fromDegreesArray([-99.0, 30.0,
                                                            -85.0, 30.0,
                                                            -85.0, 40.0,
                                                            -99.0, 40.0]),
        },
        material : Cesium.Color.BLUE.withAlpha(0.5),
        height : 1e5,
        outlineWidth: 20,
        outline : true
    }
});

viewer.entities.add({
    polygon : {
        hierarchy : {
            positions : Cesium.Cartesian3.fromDegreesArray([-99.0, 15.0,
                                                            -85.0, 15.0,
                                                            -85.0, 25.0,
                                                            -99.0, 25.0]),
        },
        material : Cesium.Color.BLUE.withAlpha(0.5),
        height : 1e5,
        outlineWidth: 1,
        outline : true
    }
});

viewer.zoomTo(viewer.entities);

Both polygons have the same outline width.

See https://github.com/AnalyticalGraphicsInc/cesium/issues/4223#issuecomment-241462146

Congratulations on closing the issue! I found these Cesium forum links in the comments above:
https://groups.google.com/d/msg/cesium-dev/o2Lopjekf3Y/P095OR0uBwAJ
If this issue affects any of these threads, please post a comment like the following:

The issue at https://github.com/AnalyticalGraphicsInc/cesium/issues/7022 has just been closed and may resolve your issue. Look for the change in the next stable release of Cesium or get it now in the master branch on GitHub https://github.com/AnalyticalGraphicsInc/cesium.

I am a bot who helps you make Cesium awesome! Contributions to my configuration are welcome.
:earth_africa: :earth_americas: :earth_asia:


Create a way to migrate data into heroku database

To export via command line on local machine:
mongodump  -d dbName -o outPath/
use your own personal zip program for easy emailing - mongo's archive files are kind of buggy
Should create an outPath/dbName hierarchy
outPath is dump/dbname by default (current working directory)
To import via command line on local machine:
mongorestore -d dbName inputPath/inputDbName
To import to Heroku:
mlab offers me the complete command line instructions to run to import and export into heroku. The above methods are for binary files and is recommended for accuracy.


RuntimeError: dictionary changed size during iteration in _handle_cancelled()

This happened when one my service's daemon tasks terminated by raising an exception. The exception from the daemon task is lost and this was the only thing I got in the logs
13:26:13 DEBUG: starting lookup; initial neighbours: [<Node(0x15ac307a470b411745a6f10544ed54c0a14ad640b21f04f523e736e732bf709d4e28c2f06526ecabc03eed226b6d9bee8e433883cd20ab6cbd114bab77a8775d@<IP_ADDRESS>:30303)>, <Node(0x1836710284935d21d3c8ec8735ded61057b3b6700415c9a17643c0fbb79c0cc65acf478374efcba027e21549e845ad2a4bfc9a695579676ac5ffd974f4941fb7@<IP_ADDRESS>:42445)>, <Node(0x865a63255b3bb68023b6bffd5095118fcc13e79dcf014fe4e47e065c350c7cc72af2e53eff895f11ba1bbb6a2b33271c1116ee870f266618eadfc2e78aa7349c@<IP_ADDRESS>:30303)>]
Traceback (most recent call last):
  File "scripts/discovery.py", line 67, in <module>
    trio.run(main)
  File "/home/salgado/virtualenvs/trinity-trio/lib/python3.7/site-packages/trio/_core/_run.py", line 1804, in run
    raise runner.main_task_outcome.error
  File "scripts/discovery.py", line 63, in main
    await service.manager.wait_finished()
  File "/home/salgado/virtualenvs/trinity-trio/lib/python3.7/site-packages/async_generator/_util.py", line 42, in __aexit__
    await self._agen.asend(None)
  File "/home/salgado/src/async-service/async_service/trio.py", line 413, in background_trio_service
    await manager.stop()
  File "/home/salgado/virtualenvs/trinity-trio/lib/python3.7/site-packages/trio/_core/_run.py", line 730, in __aexit__
    raise combined_error_from_nursery
  File "/home/salgado/src/async-service/async_service/trio.py", line 140, in run
    system_nursery.cancel_scope.cancel()
  File "/home/salgado/virtualenvs/trinity-trio/lib/python3.7/site-packages/trio/_core/_run.py", line 730, in __aexit__
    raise combined_error_from_nursery
  File "/home/salgado/src/async-service/async_service/trio.py", line 65, in _handle_cancelled
    for task in iter_dag(self._service_task_dag):
  File "/home/salgado/src/async-service/async_service/_utils.py", line 56, in iter_dag
    for item in dag.keys():
RuntimeError: dictionary changed size during iteration

Sometimes I do get the correct exceptions, so yeah, definitely a race condition somewhere:
13:34:28 DEBUG: bonding completed successfully with <Node(0x15ac30@<IP_ADDRESS>)>
Traceback (most recent call last):
  File "scripts/discovery.py", line 67, in <module>
    trio.run(main)
  File "/home/salgado/virtualenvs/trinity-trio/lib/python3.7/site-packages/trio/_core/_run.py", line 1804, in run
    raise runner.main_task_outcome.error
  File "scripts/discovery.py", line 63, in main
    await service.manager.wait_finished()
  File "/home/salgado/virtualenvs/trinity-trio/lib/python3.7/site-packages/async_generator/_util.py", line 42, in __aexit__
    await self._agen.asend(None)
  File "/home/salgado/src/async-service/async_service/trio.py", line 413, in background_trio_service
    await manager.stop()
  File "/home/salgado/virtualenvs/trinity-trio/lib/python3.7/site-packages/trio/_core/_run.py", line 730, in __aexit__
    raise combined_error_from_nursery
  File "/home/salgado/src/async-service/async_service/trio.py", line 156, in run
    for _, exc_value, exc_tb in self._errors
trio.MultiError: AssertionError(), LifecycleError('Tasks may not be scheduled if the service is not running')

Details of embedded exception 1:

  Traceback (most recent call last):
    File "/home/salgado/src/async-service/async_service/trio.py", line 241, in _run_and_manage_task
      await async_fn(*args)
    File "/home/salgado/src/trinity/p2p/discovery.py", line 223, in fetch_enrs
      raise AssertionError()
  AssertionError

Details of embedded exception 2:

  Traceback (most recent call last):
    File "/home/salgado/src/async-service/async_service/trio.py", line 241, in _run_and_manage_task
      await async_fn(*args)
    File "/home/salgado/src/trinity/p2p/discovery.py", line 238, in _ensure_enr
      await self.get_enr(node)
    File "/home/salgado/src/trinity/p2p/discovery.py", line 356, in get_enr
      enr = await self.request_enr(remote)
    File "/home/salgado/src/trinity/p2p/discovery.py", line 312, in request_enr
      token = self.send_enr_request(remote)
    File "/home/salgado/src/trinity/p2p/discovery.py", line 670, in send_enr_request
      message = self.send(node, CMD_ENR_REQUEST, [_get_msg_expiration()])
    File "/home/salgado/src/trinity/p2p/discovery.py", line 514, in send
      self.socket.sendto, message, (node.address.ip, node.address.udp_port))
    File "/home/salgado/src/async-service/async_service/trio.py", line 274, in run_task
      "Tasks may not be scheduled if the service is not running"
  async_service.exceptions.LifecycleError: Tasks may not be scheduled if the service is not running

I'm thinking that we may need to use a lock to manage access to the task dag.  My reasoning for this is that we want to ensure that once we start cancelling things we don't schedule anything new (modify the dag).  If we protect it with a lock then we should be able to fix this because either the lock will be held by the cleanup code in which case all attempts to schedule new stuff should hang attempting to acquire the lock, or the lock will be held by the code that is starting the task at which point the cleanup code will wait until the task is fully scheduled before doing cleanup.
I think this should fix both scenarios.

Makes sense, that should probably do the trick indeed


Add validation for schedule

For now, there is no validation for schedule.
So I added that and it fails when there is invalid keys.

This works as long as we have only standard schedules ("hourly>", "daily>", "weekly>", "monthly>", "minutes_interval>", "seconds_interval>", "cron>"). However, digdag's scheduler is designed to be pluggable. Can't we have the validation without spoiling it? To make it possible, ProjectResource.putProject needs to validate pushed workflow WITHOUT using static keys (VALID_SCHEDULE_KEYS).
A direction is commented at ProjectControl.updateSchedules:
        // TODO validate workflows and sessions
        //   * compile workflow
        //   * validate SubtaskMatchPattern

ProjectControl.updateSchedules is called by ProjectControl.insertWorkflowDefinitions, and it's called by ProjectResource.putProject. It means that PUT /api/projects returns an error if ProjectControl.updateSchedules throws an exception. Therefore, an alternative direction is adding validation to ProjectControl.updateSchedules so that it throws an exception if schedule definition includes unknown keys.
Now, ProjectControl.updateSchedules is creating a Scheduler instance at https://github.com/treasure-data/digdag/blob/0b1ca9c237b37504d1b34b38b3f6350b81c6f2e7/digdag-core/src/main/java/io/digdag/core/repository/ProjectControl.java#L104. Scheduler is either of CronScheduler, DailyScheduler, etc. implemented in digdag-standards. SchedulerManager is creating a Scheduler instance.
As you can see SchedulerManager.getScheduler there, the code is similar to this code in OperatorManager. It gets "_type" from config, gets SchedulerFactory, and call SchedulerFactory.newScheduler to create a new Scheduler. A big difference is that SchedulerManager.getScheduler doesn't have checking of unused keys. Checking of unused keys is implemented in OperatorManager here.

Thank you for reviewing! I'll fix it. 🙇

So, how about doing this?

Change SchedulerFactory.tryGetScheduler and .getScheduler to get another argument - Consumer<Set<String>> unusedKeysCallback.
SchedulerFactory.getScheduler calls unusedKeysCallback.accept if some config keys are not used.
ProjectControl.updateSchedules calls tryGetScheduler with unusedKeysCallback=(unusedKeys) -> throw new SomeSortOfException.

Item 2 can be implemented by mimicking the same code with OperatorManager here:

Create usedKeys: CheckedConfig.UsedKeysSet usedKeys = new CheckedConfig.UsedKeysSet()
Wrap Config with CheckedConfig (Note: CheckedConfig implements Config).
Give the CheckedConfig to factory.newScheduler.
Thanks to CheckedConfig, usedKeys contains list of used keys now.
Compare usedKeys with shouldBeUsedKeys like here: https://github.com/treasure-data/digdag/blob/v0_10/digdag-core/src/main/java/io/digdag/core/agent/OperatorManager.java#L273-L278
shouldBeUsedKeys is all keys of Config like this: https://github.com/treasure-data/digdag/blob/v0_10/digdag-core/src/main/java/io/digdag/core/agent/OperatorManager.java#L225

@frsyuki Thank you very much for clear explanation.
I fixed like above, so could you review when you have time?

@frsyuki I fixed like the comment and added more tests, so please tell me if there are problem. :man-bowing:

Thanks for reviewing! 🙇


Container fails to start with read-only file system #2

I run this buildpack via helm chart and configured my security context like so:
securityContext:
  readOnlyRootFilesystem: true
  runAsNonRoot: true
volumes:
  - emptyDir: {}
    name: tmpdir
podVolumeMounts:
  - mountPath: /tmp
    name: tmpdir

As the only exception I made /tmp writeable.
Therefore I used an own nginx.conf with some templated values. See:
daemon off;
worker_processes {{env "NGINX_WORKERS"}};
...
http {
  ...
  access_log /dev/stdout;
  error_log stderr;
  client_body_temp_path {{ tempDir }}/client_body_temp;
  proxy_temp_path {{ tempDir }}/proxy_temp;
  fastcgi_temp_path {{ tempDir }}/fastcgi_temp;
  ...
  server {
    listen 8080;
    server_name _;
    client_max_body_size {{env "NGINX_CLIENT_MAX_BODY_SIZE"}}M;
    root ./{{env "NGINX_ROOT"}};
    ...
    location / {
      try_files $uri $uri/ /index.html;
      add_header Last-Modified "{{ env "NGINX_LAST_MODIFIED_HEADER" }}";
      # switch ETag off, since file modification time is always 01-01-1980
      etag off;
    }
  }
}

Expected Behavior

Nginx is up and running serving my content.
Current Behavior

Nginx doesn't start, because configure-0 tries to write on a read-only location.
This was already reported #385
failed to create nginx.conf: open /workspace/nginx.conf: read-only file system
ERROR: failed to launch: exec.d: failed to execute exec.d file at path '/layers/paketo-buildpacks_nginx/nginx/exec.d/0-configure': exit status 1

Possible Solution

In this issue I try to focus on templating issues with nginx.conf. Configure nginx to not write anything should be addressed at nginx team.
Not using templating in nginx.conf was already discussed and is still one workaround. For me this is not an option. E.g. we're using a dynamic URL to proxy our backend depending on our actual environment.
Solutions:

(preferred) Do not perform an replacement of nginx.conf. Instead use the input file as template and write the output file to a user specified location. If BPL_NGINX_CONF_LOCATION is set this configuration is written and used.
A user is responsible to copy nginx.conf to a build/run writeable location e.g. /tmp. Additionally set BP_NGINX_CONF_LOCATION=/tmp/nginx.conf. To make configure-0 working a user must also copy it's nginx.conf at runtime to tmp. Maybe by mounting a ConfigMap to a volume or by other means.

Steps to Reproduce

Deploy an image via helm chart with this values:

securityContext:
  readOnlyRootFilesystem: true
  runAsNonRoot: true

Motivations

As already mentioned we strive to run our images as secure as possible. To do so we try to run a container read-only with some exceptions.
This is described here

Running a read-only file system in your containers forces your containers to be immutable.
Not only does this mitigate some old (and risky) practices such as hot patching, but also helps you prevent the risks of malicious processes storing or manipulating data inside a container.

Is there any update on this?

I hit this issue as well. It seems bad to require that the workspace directory is writable at runtime. Are there any caveats to solution #1 as proposed by @ajdergute ?

I hit this issue as well. It seems bad to require that the workspace directory is writable at runtime. Are there any caveats to solution 1 as proposed by @ajdergute ?


Update realtime functionality

Issue noWork messages when backend sends invalid responses
Avoid printing to console response, if response is invalid

LGTM


PowerShell on Target Machines task: Non-zero exit code is marked as "pass"

Invoking a PowerShell script that exits with a non-zero code does not mark the task as failed.
E.g., simply running a .ps1 with
Exit 1

has the following output reported in the logs
Deployment status for machine '<hostname>:5985' : 'Passed'

The regular PowerShell task with an inline script marks the task as failed as expected.

I'd also like to be able to fail a task by non-zero exit code

@shaykalyan , @NikolayKash , thanks much for reporting the issue. This behavior is by design.
We consider your feedback and will try to address it in future releases.

i have the same problem, I am running some webtest using powershell on target machine. It passes the task even when the tests are failed. Is there a work around for this. Thanks.

@psutharsan: Not a very clean work around, but since the default $ErrorActionPreference is set to "Stop", writing to the Error stream in your script via Write-Error will be terminal and result in the task being marked as failed.
@pavanadepu2: I'm curious why the design is such?

@ericsciple  @pavanadepu2  @mvvsubbu @RoopeshNair - Can you please confirm if the exit code is now returned with merge #5606?

nope that pr is for the powershell task

Thank you for your feedback. This should be fixed now. The latest version supports additional error handling options as well.


Create installer and package

description on this please?
If this refer to released package, I think we can close this

Hi, I forgot what this was actually. I think it was created to create some sort of dmg package.


Update exception message in an indicator unit test

Fixes #352
I still question whether we should be checking exception messages at all.

This is fixing a compatibility problem with the master branch pattern validator.  Recent changes on that branch haven't been officially released, so the unit tests Travis runs are using an older version of the library.  So unit tests without this PR won't break until the next pattern validator release is made, and the tests with this PR won't pass until then either.  I guess you could consider this a proactive PR, fixing a bug which will appear when the next pattern validator release is made.
Btw, it could be made to work in either case by not checking the message at all.  An exception was raised before and it's raised now, so that hasn't changed.


Authentication issue after last release

Hello,
Since the last (big) update, I added the integration from UI successfully, but I only have 4 select entities and this error:
2021-09-05 12:47:51 ERROR (MainThread) [custom_components.babybuddy] Authentication failed while fetching babybuddy data: 403, message='Forbidden', url=URL('https://mybabybuddy/api/children/')

On babybuddy :
Forbidden: /api/children/
I tried to reset my api key multiple times but same issue :(

Check this:
https://gitter.im/babybuddy/Lobby?at=612f62e87cd57813a89fadee

Great thank you,
Is it normal that last_feeding entity state stay at unknown but attributes are all ok :

See https://github.com/jcgoette/baby_buddy_homeassistant/pull/33#discussion_r698911200.


Add support for wildcards in the map file

Hello, in order to reduce the work needed to add a new test in the map I would like to add the support for wildcards in the map file.
Example:
{
  "$.paths./.get.responses.200.schema": [
    "test/basic/*",
    "test/advanced/*",
  ],
  "$.paths./.get.responses.300.schema": "test/*"
}

In this way any new test added in the correct folder will be automatically detected by the script without having to update the map

Sounds good 👍 . PRs are welcome


[Question Bot C#] How to use IActivityLogger for load history of conversations

I'm trying to load old conversations from db into chat when user opens the chat again. I'm looking for some examples to do it by using IActivityLogger but I can't find anything. I've implemented my bot into xamarin app and I want to load the old conversations when user opens the chat. My Bot is in c#, so if anyone have examples about how can I use IActivityLogger please  provide it.

Hello, have you been able to resolve this issue, or are you still looking for an answer?

Still looking for an answer...

@msBot1111
The documentation is here: https://docs.botframework.com/en-us/csharp/builder/sdkreference/d2/d77/interface_microsoft_1_1_bot_1_1_builder_1_1_history_1_1_i_activity_logger.html
here is an issue from the past that looks like it may help:
https://github.com/Microsoft/BotBuilder/issues/2073
Note: if you use the message below, it might be best to first: ask the question on Stack Overflow, answer it, then paste the code below. With a link to the stack overflow question.
The Microsoft Bot Framework team prefers that how to questions be submitted on Stack Overflow. The official Bot Framework Github repo  is the preferred platform for submitting bug fixes and feature requests.
I have closed this issue. Please feel free to resubmit your question over on Stack Overflow and one of our support engineers will help you out as soon as possible.

I am also facing same issue.....hot to use TableLogger class to log the chat...and load it again when user come back to after some time?

How to load old conversations for nodejs bot??


Kubectl v1.26.x annotate overwrites even with --overwrite=false set

What happened:
While trying to add annotation to node or pods, it overwrites existing values, if annotation already exists.
What you expected to happen:
Kubectl should exit with error message, if annotation exists and --overwrite or --overwrite=true aren't provided.
How to reproduce it (as minimally and precisely as possible):
Annotate the same object twice with the same annotation using kubectl version v1.26.x.
If you try to do it using kubectl v1.25.x, it produces the following error:
error: --overwrite is false but found the following declared annotation(s): 'test-annotation' already has a value (true)
Environment:
Testing using kubectl versions ranging from v1.25.3 to v1.26.3 and kubernetes version from v1.21 to v1.26.

➜  ~ kubectl version
WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short.  Use --output=yaml|json to get the full version.
Client Version: version.Info{Major:"1", Minor:"27+", GitVersion:"v1.27.0-alpha.3.905+8f15859afc9cfa-dirty", GitCommit:"8f15859afc9cfaeb05d4915ffa204d84da512094", GitTreeState:"dirty", BuildDate:"2023-03-27T08:43:36Z", GoVersion:"go1.20.2", Compiler:"gc", Platform:"linux/arm64"}
Kustomize Version: v5.0.1
Server Version: version.Info{Major:"1", Minor:"27+", GitVersion:"v1.27.0-alpha.3.905+8f15859afc9cfa-dirty", GitCommit:"8f15859afc9cfaeb05d4915ffa204d84da512094", GitTreeState:"dirty", BuildDate:"2023-03-27T08:43:36Z", GoVersion:"go1.20.2", Compiler:"gc", Platform:"linux/arm64"}

➜  ~ kubectl annotate deploy my-dep deploy=""
error: --overwrite is false but found the following declared annotation(s): 'deploy' already has a value (2)

I cannot reproduce this issue on my Kubernetes cluster version 1.27.0. It seems to have been fixed

Hmm I am not able to reproduce this on v1.26.3.
~ kubectl version
WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short.  Use --output=yaml|json to get the full version.
Client Version: version.Info{Major:"1", Minor:"26", GitVersion:"v1.26.3", GitCommit:"9e644106593f3f4aa98f8a84b23db5fa378900bd", GitTreeState:"archive", BuildDate:"2023-03-19T19:47:22Z", GoVersion:"go1.19.7", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.7
Server Version: version.Info{Major:"1", Minor:"26", GitVersion:"v1.26.3", GitCommit:"9e644106593f3f4aa98f8a84b23db5fa378900bd", GitTreeState:"clean", BuildDate:"2023-03-30T06:34:50Z", GoVersion:"go1.19.7", Compiler:"gc", Platform:"linux/amd64"}

~ kubectl annotate nodes kind-control-plane testing=abc
node/kind-control-plane annotated

 ~ kubectl annotate nodes kind-control-plane testing=123
error: --overwrite is false but found the following declared annotation(s): 'testing' already has a value (abc)

 ~ kubectl annotate nodes kind-control-plane testing=""
error: --overwrite is false but found the following declared annotation(s): 'testing' already has a value (abc)

Anything else you can provide to reproduce?

Just tested again on 1.25 and 1.26 kind clusters.
# 1.26 kubectl and k8s
kubectl version
WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short.  Use --output=yaml|json to get the full version.
Client Version: version.Info{Major:"1", Minor:"26", GitVersion:"v1.26.2", GitCommit:"fc04e732bb3e7198d2fa44efa5457c7c6f8c0f5b", GitTreeState:"clean", BuildDate:"2023-02-22T13:39:03Z", GoVersion:"go1.19.6", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.7
Server Version: version.Info{Major:"1", Minor:"26", GitVersion:"v1.26.2", GitCommit:"fc04e732bb3e7198d2fa44efa5457c7c6f8c0f5b", GitTreeState:"clean", BuildDate:"2023-03-10T21:12:33Z", GoVersion:"go1.19.6", Compiler:"gc", Platform:"linux/amd64"}

kubectl annotate node k8s-1-26-worker test-annotation="1"
node/k8s-1-26-worker annotated

kubectl annotate node k8s-1-26-worker test-annotation="1"
node/k8s-1-26-worker annotated

# 1.25 kubectl, 1.26 k8s
kubectl version
WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short.  Use --output=yaml|json to get the full version.
Client Version: version.Info{Major:"1", Minor:"25", GitVersion:"v1.25.8", GitCommit:"0ce7342c984110dfc93657d64df5dc3b2c0d1fe9", GitTreeState:"clean", BuildDate:"2023-03-15T13:39:54Z", GoVersion:"go1.19.7", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.7
Server Version: version.Info{Major:"1", Minor:"26", GitVersion:"v1.26.2", GitCommit:"fc04e732bb3e7198d2fa44efa5457c7c6f8c0f5b", GitTreeState:"clean", BuildDate:"2023-03-10T21:12:33Z", GoVersion:"go1.19.6", Compiler:"gc", Platform:"linux/amd64"}

kubectl annotate node k8s-1-26-worker test-annotation="1"
node/k8s-1-26-worker annotated

kubectl annotate node k8s-1-26-worker test-annotation="1"
error: --overwrite is false but found the following declared annotation(s): 'test-annotation' already has a value (1)

# 1.26 kubectl, 1.25 k8s
kubectl version
WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short.  Use --output=yaml|json to get the full version.
Client Version: version.Info{Major:"1", Minor:"26", GitVersion:"v1.26.2", GitCommit:"fc04e732bb3e7198d2fa44efa5457c7c6f8c0f5b", GitTreeState:"clean", BuildDate:"2023-02-22T13:39:03Z", GoVersion:"go1.19.6", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.7
Server Version: version.Info{Major:"1", Minor:"25", GitVersion:"v1.25.3", GitCommit:"434bfd82814af038ad94d62ebe59b133fcb50506", GitTreeState:"clean", BuildDate:"2022-11-02T03:22:35Z", GoVersion:"go1.19.2", Compiler:"gc", Platform:"linux/amd64"}

kubectl annotate node k8s-1-25-worker test-annotation="1"
node/k8s-1-25-worker annotated

kubectl annotate node k8s-1-25-worker test-annotation="1"
node/k8s-1-25-worker annotated

# 1.25 kubectl and k8s
kubectl version
WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short.  Use --output=yaml|json to get the full version.
Client Version: version.Info{Major:"1", Minor:"25", GitVersion:"v1.25.8", GitCommit:"0ce7342c984110dfc93657d64df5dc3b2c0d1fe9", GitTreeState:"clean", BuildDate:"2023-03-15T13:39:54Z", GoVersion:"go1.19.7", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.7
Server Version: version.Info{Major:"1", Minor:"25", GitVersion:"v1.25.3", GitCommit:"434bfd82814af038ad94d62ebe59b133fcb50506", GitTreeState:"clean", BuildDate:"2022-11-02T03:22:35Z", GoVersion:"go1.19.2", Compiler:"gc", Platform:"linux/amd64"}

kubectl annotate node k8s-1-25-worker test-annotation="1"
node/k8s-1-25-worker annotated

kubectl annotate node k8s-1-25-worker test-annotation="1"
error: --overwrite is false but found the following declared annotation(s): 'test-annotation' already has a value (1)

Also previously tested on two separate colleagues workstations, one Linux one MacOS, same result.

Ah I see. This only seems to happen when you annotate with the current/same value.
kubectl annotate nodes ip-192-168-2-50.us-west-2.compute.internal test="1"
node/ip-192-168-2-50.us-west-2.compute.internal annotated

kubectl annotate nodes ip-192-168-2-50.us-west-2.compute.internal test="1"
node/ip-192-168-2-50.us-west-2.compute.internal annotated

kubectl annotate nodes ip-192-168-2-50.us-west-2.compute.internal test="2"
error: --overwrite is false but found the following declared annotation(s): 'test' already has a value (1)

This appears to be an intentional change https://github.com/kubernetes/kubernetes/pull/109505.
@bunicb are you running into issues with this change? If so can you please explain more about why?

The use case in which this appeared was that we wanted to annotate nodes with a specific annotation, but only if no-one else previously set it. That way we know which nodes we annotate and can later on remove it only on those nodes.
We've worked around that by getting nodes that are already annotated beforehand, and omitting them during the process. The issue I see with this being intentional is, that if you specifically set --overwrite=false, it still overwrites if it's the same value.


fix(arweave): modify import of Arweave in ArweaveToken

Temporary patch for issues related to using .init() in web environments

:tada: This PR is included in version 1.20.0-alpha.3 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update travis configuration to test on node 0.12 and 0.10, fixes tests

https://travis-ci.org/substack/node-deep-equal is failing because the .travis.yml is configured to only test on very old versions of nodejs, 0.4 and 0.6, which fail to load the newer tape 3.5.0 dev dependency.
This PR updates .travis.yml to test on 0.12 and 0.10, so the tests pass

Out of date

https://github.com/substack/node-deep-equal/pull/33


Regenerate PHP

Updates grpc stub name
Updates docs with backslashes
Adds support for passing in stub creation function

LGTM


Fix crash when attempting to merge an import with a local declaration

Somewhere around #7591, we decided to allow aliases to merge with other symbols. A NamespaceImport is an alias symbol, so is able to merge with another symbol in the file. We no longer crash when you attempt this, as we now handle NamespaceImport in getDeclarationSpaces.
Fixes #17982

Please port this to release-2.5


bar_11

Closes #117

Updated plot after adjusting the figure size, gridspec wspace, and font sizes.


DynamoDB Validation Error in Production

Multiple errors in Production this morning with the following tracelog:
{
    "level": "warn",
    "time":<PHONE_NUMBER>168,
    "err": {
        "type": "DynamoDBServiceException",
        "message": "The provided key element does not match the schema",
        "stack": "ValidationException: The provided key element does not match the schema\n    at throwDefaultError (/src/node_modules/@aws-sdk/smithy-client/dist-cjs/default-error-handler.js:8:22)\n    at deserializeAws_json1_0UpdateItemCommandError (/src/node_modules/@aws-sdk/client-dynamodb/dist-cjs/protocols/Aws_json1_0.js:2719:51)\n    at runMicrotasks (<anonymous>)\n    at processTicksAndRejections (node:internal/process/task_queues:96:5)\n    at async /src/node_modules/@aws-sdk/middleware-serde/dist-cjs/deserializerMiddleware.js:7:24\n    at async /src/node_modules/@aws-sdk/lib-dynamodb/dist-cjs/baseCommand/DynamoDBDocumentClientCommand.js:18:34\n    at async /src/node_modules/@aws-sdk/middleware-signing/dist-cjs/middleware.js:13:20\n    at async StandardRetryStrategy.retry (/src/node_modules/@aws-sdk/middleware-retry/dist-cjs/StandardRetryStrategy.js:51:46)\n    at async /src/node_modules/@aws-sdk/middleware-logger/dist-cjs/loggerMiddleware.js:6:22\n    at async removeProcessedMark (/src/.next/server/pages/api/notify-callback.js:326:12)",
        "name": "ValidationException",
        "$fault": "client",
        "$metadata": {
            "httpStatusCode": 400,
            "requestId": "SI16Q0J1Q89BU6O35T7ST88V4BVV4KQNSO5AEMVJF66Q9ASUAAJG",
            "attempts": 1,
            "totalRetryDelay": 0
        },
        "__type": "com.amazon.coral.validate#ValidationException"
    },
    "msg": "The provided key element does not match the schema"
}

The Notify Callback api is throwing the errors.


Update initDispatch arg order in enhancer

The argument for dispatch in the enhancedInit assignment of initDispatch should be in position 0.

Picking up dev on this project and I'm including this fix in my first update adding an example to make dev easier.


KAFKA-3605: Return error if connector config includes mismatching connector name.

@Ishiihara @hachikuji @gwenshap Should be an easy review, and @gwenshap need you to commit :)

LGTM

@gwenshap If you have a moment, have addressed review comments

LGTM


Fix hasPermission() always returning success on iOS

Use [AVAudioSession sharedInstance] recordPermission to check mic permissions

Closes https://github.com/pbakondy/cordova-plugin-speechrecognition/issues/89

I'm still having this problem, the project looks currently dead and the pull request was not merged.
Does anyone created and maintained a fork with this fix?


Fluentd fails to cleanup buffer metadata

Check CONTRIBUTING guideline first and here is the list to help us investigate the problem.
Describe the bug

I have fluentd tailing kubernetes logs, and sending them to elasticsearch and s3. Both outputs are configured to use file buffers in order to avoid the loss of logs if something happens to the fluentd pod. On one cluster in particular, the s3 file buffer has been filling up with a huge number of empty buffer metadata files (all zero bytes), to the point that it uses up all the inodes on the volume. There is not associated log buffer file, just the metadata. Some of these empty metadata files were months old. I had to go manually clean up all the zero byte metadata files in order to restore cluster functionality. Looking for some insight into why these blank metadata files are created, and why they are never cleaned up by fluentd.
In the past, we were seeing issues with fluentd throughput, and the log buffers would get backed up and fill up all the disk space, so I do have it configured to aggressively create and flush chunks.
${archive_path} is configured from kubernetes metadata like so: ${'container-logs/' + record['kubernetes']['namespace_name'] + '/' + record['kubernetes']['container_name'] + '/' + record['kubernetes']['pod_name'] + '/'}. That along with the 60s chunk interval can make for a lot of chunks when many pods are redeployed, but I still would not expect to see over a million chunks, and it doesn't explain why these empty metadata files are left in place, seemingly forever.
Also asked a question about this here, but it does seem like it's a different issue than what the original question was about so I figured I'd create a new one.
To Reproduce
Still working on reproducing this behavior in a dev cluster. Best I can tell, lots of pod redeploys and nightly cronjob pods.
Expected behavior
Empty metadata files should be cleaned up by fluentd.
Your Environment

Fluentd or td-agent version: fluentd --version or td-agent --version
td-agent 1.3.3
Operating system: cat /etc/os-release
NAME="Container Linux by CoreOS"
ID=coreos
VERSION=1967.6.0
VERSION_ID=1967.6.0
BUILD_ID=2019-02-12-2138
PRETTY_NAME="Container Linux by CoreOS 1967.6.0 (Rhyolite)"
ANSI_COLOR="38;5;75"
HOME_URL="https://coreos.com/"
BUG_REPORT_URL="https://issues.coreos.com"
COREOS_BOARD="amd64-usr"
Kernel version: uname -r
4.14.96-coreos-r1

If you hit the problem with older fluentd version, try latest version first.
Your Configuration
    <match **>
      @type copy_ex
      <store ignore_error>
        @id elasticsearch
        @type elasticsearch
        @log_level debug
        id_key _hash
        remove_keys _hash,_tag # Remove temp key
        include_tag_key true
        host "#{ENV['FLUENT_ELASTICSEARCH_HOST']}"
        port "#{ENV['FLUENT_ELASTICSEARCH_PORT']}"
        scheme "#{ENV['FLUENT_ELASTICSEARCH_SCHEME'] || 'http'}"
        logstash_prefix "#{ENV['FLUENT_ELASTICSEARCH_LOGSTASH_PREFIX'] || 'logstash'}"
        logstash_format true
        reload_connections false
        reconnect_on_error true
        reload_on_failure true
        <buffer>
          @type file
          path /var/log/fluent/elasticsearch
          flush_mode interval
          retry_type exponential_backoff
          flush_interval 5s
          retry_forever
          retry_max_interval 30m
          chunk_limit_size 2M
          overflow_action block
        </buffer>
      </store>
      <store ignore_error>
        @id s3
        @type s3
        @log_level info
        aws_key_id "#{ENV['AWS_ACCESS_KEY_ID']}"
        aws_sec_key "#{ENV['AWS_SECRET_ACCESS_KEY']}"
        s3_region "#{ENV['AWS_DEFAULT_REGION']}"
        s3_bucket "#{ENV['AWS_S3_BUCKET']}"
        store_as json
        path ${archive_path}
        time_slice_format %Y-%m-%d-%H:%M
        <buffer archive_path,time>
          @type file
          path /var/log/fluent/s3
          timekey 60s
          timekey_wait 10s
          timekey_use_utc true # use utc
          chunk_limit_size 64m
          flush_thread_count 4
          flush_mode interval
          flush_interval 60s
          retry_forever
          overflow_action block
        </buffer>
      </store>
    </match>

Your Error Log
Couldn't find any error logs. Even with debug mode on and removing the ignore_error flag.

Hmm... I'm not sure why this happens because fluentd just deletes metadata file after chunk flush:
https://github.com/fluent/fluentd/blob/bd951f3087a2c1f998866b0867d787c06a74db10/lib/fluent/plugin/buffer/file_chunk.rb#L165
fluentd doesn't truncate metadata file so 0 size metadata is curious situation.

Couldn't find any error logs. Even with debug mode on and removing the ignore_error flag.

By no error logs, I assume this problem happens outside of fluentd.
fluentd v1.7 supports file_singlebuffer plugin, https://docs.fluentd.org/buffer/file_single, and this may resolve your problem.

Thanks, that is helpful. Any migration tips for moving to file_single without losing logs? Assuming that it wouldn't know what to do with the existing buffer files if I did a hard cutover.

I guess maybe leave both configurations in place for a while, but have the old one match on nothing?

I did find a number of warnings like these that were from around the time the issue happened.
[s3] failed to write data into buffer by buffer overflow action=:block and error_class=Errno::ENOSPC error="No space left on device @ io_write - /var/log/fluent/elasticsearch/buffer.b590d1984b5c61afe21a9c0095dfbc3d1.log"
Is it possible that fluentd might create meta files, and then leave it there empty if the chunk fails to be written to disk?

Yep :)
Filled up most of the disk, then created a pod that logs a ton of junk data to keep the disk full. After doing so, about 8000 empty meta files were generated within about a minute.

Thank you for your hard work to dig the root cause! Your information was very helpful to us.
https://github.com/fluent/fluentd/pull/2598 should fix this issue.

Great! Thanks for fixing that up so quickly!


Error While Uploading

I followed the instructions and the code compiled without any errors but when uploading I got the following error.
Arduino: 1.8.1 (Mac OS X), Board: "Arduino/Genuino Uno"
Sketch uses 3630 bytes (11%) of program storage space. Maximum is 32256 bytes.
Global variables use 237 bytes (11%) of dynamic memory, leaving 1811 bytes for local variables. Maximum is 2048 bytes.
avrdude: ser_open(): can't open device "/dev/cu.usbmodemfa131": No such file or directory
Problem uploading to board.  See http://www.arduino.cc/en/Guide/Troubleshooting#upload for suggestions.
This report would have more information with
"Show verbose output during compilation"
option enabled in File -> Preferences.

Did you notice that you selected the wrong serial port for the Uno board?


Add dice-roll extension

Description

An extension for rolling any sided dice. You can roll multiple dice, using different combinations of sides.
Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Hi @FrederikBanke 👋
Thanks for your contribution 🔥
Would it make sense to enhance the current one instead made by @TroAlexis

Hi @FrederikBanke 👋
Thanks for your contribution 🔥
Would it make sense to enhance the current one instead made by @TroAlexis

Absolutely, only reason I made this, was because it was marked as stalled at the time.

Hi @FrederikBanke 👋
Thanks for your contribution 🔥
Would it make sense to enhance the current one instead made by @TroAlexis

Absolutely, only reason I made this, was because it was marked as stalled at the time.

It would be really awesome if you could pull up a dice-roller parser like this one to allow for even more versatility in rolls.

What is the status here, can I do something to ease the process?


Incorrect plot command crashes spyder

From<EMAIL_ADDRESS>on 2010-12-06T11:39:27Z
What steps will reproduce the problem?

Open spyder
Type the following code in the temp file:

from pylab import *
x = [1, 2]
y = [3, 4]
plot(x,y, c = '[0.5]')
show()

Run with F5.

What is the expected output?
Stack trace, showing that '[0.5]' is an invalid color...
What do you see instead? Spyder crashes. What version of the product are you using? On what operating system? Spyder 2.0.3 on Fedora 14.
Please provide any additional information below
.
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=491

From<EMAIL_ADDRESS>on 2010-12-15T08:11:10Z
Carlos,
This is what I get starting spyder with the -d flag and then running the script:
Start of MainWindow constructor
Initializing...
End of MainWindow constructor
*** Start of MainWindow setup ***
Loading object inspector...
Loading editor...
Loading file explorer...
Loading history plugin...
Loading online help...
Loading project explorer...
Loading external console...
Loading namespace browser...
Setting up main window...
Setting up window...
*** End of MainWindow setup ***
Segmentation fault (core dumped)
Im using Fedora ( https://fedoraproject.org/ ). It comes with SELinux enabled. Perhaps it is some kind of related issue?

From ccordoba12 on 2010-12-15T08:05:51Z
I'm sorry but I can't reproduce your bug. I'm getting the right stack trace and spyder doesn't crashes.
Please activate the "Internal console" plug-in and try to check what messages appear there before spyder crashes.
Also if you have spyder version 1.0 installed, please uninstall it and reinstall version 2.0 again. That could be the cause of your problem.
Carlos

From<EMAIL_ADDRESS>on 2010-12-15T08:22:09Z
Carlos,
There is not enough time to check the internal console. The application crashes and closes when the segfault occurrs. Is the information logged somewhere else? I'll try later with selinux disabled to see if it crashes.
Thanks.

From ccordoba12 on 2010-12-15T08:19:48Z
I'm using Kubuntu 10.10 so, as you say, probably SELinux is your problem. Can you deactivate it and try again?
Please don't forget to use the internal console and check the (possible) error messages that could appear there.

From<EMAIL_ADDRESS>on 2010-12-22T08:06:56Z
Carlos,
I have tried running it with selinux disabled and it still crashes. Hitting F5 makes the window turn to the ipython console, instead of the internal console. After it runs, the application segfaults and exits. By the way, I tried it now with version 2.0.5 which made its way into the Fedora repos.
Thanks.

From pierre.raybaut on 2011-05-16T01:20:53Z
Labels: Cat-Console

From ccordoba12 on 2010-12-15T12:03:43Z
Cassio, can you see at least something printed on the internal console? You can hit F5 while you are viewing it, and the file still will be run on the ipython console. If not, I would say you have a problem with your PyQt installation.

From ccordoba12 on 2014-08-23T13:09:48Z
Don't know where this could be coming from but it's old now.
Status: WontFix


Added function call inspection with arity checks

This change is

Reviewed 10 of 11 files at r1, 1 of 2 files at r2.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


More binder cache issues

Prerequisites

[X] Put an X between the brackets on this line if you have done all of the following:

Checked that your issue isn't already filed.
Reduced the issue to a self-contained, reproducible test case.

Description
Implicit binders can magically disappear during function coercion.
Steps to Reproduce
universe u

structure Fn (E I : Sort u) := (exp : E) (imp : I)
instance (E I : Sort u) :  CoeFun (Fn E I) (fun _ => I) := {coe := fun K => K.imp}

class Bar.{w} (P : Sort u) :=
  fn : P -> Sort w

variable {P : Sort u} (B : Bar P)
variable (fn : Fn ((p : P) -> B.fn p) ({p : P} -> B.fn p))
#check coeFun fn -- Result is as expected (implicit)
/-
  fn : {p : P} → Bar.fn p
-/

variable (p : P)
variable (Bp : B.fn p)
#check fn Bp -- Errors unexpectedly
/-
application type mismatch
  Fn.imp fn Bp
argument
  Bp
has type
  Bar.fn p : Sort ?u.635
but is expected to have type
  P : Sort u
-/

#check fn p -- Works unexpectedly
/-
  Fn.imp fn p : Bar.fn p)
-/

Also note that the Fn.imp fn p in the last #check  message of the above example is ill-formed:
#check Fn.imp fn p -- Errors
/-
function expected at
  Fn.imp fn ?m.980
term has type
  Bar.fn ?m.980
-/

Versions
Windows 10 20H2
Lean (version 4.0.0-nightly-2021-05-05, commit 7398db5f3fe9, Release)
Additional Information
This is a continuation of the chain of binder/cache issues discussed here: https://leanprover.zulipchat.com/#narrow/stream/270676-lean4/topic/Binder.20bug.3A.20Binder.20not.20being.20properly.20preserved.3F

Yes, this bug is due to another instance of the binder cache issue.
Could you please confirm that the expected behavior is the following one?
#check coeFun fn -- Result is as expected (implicit)
/-
  fn : {p : P} → Bar.fn p
-/
variable (p : P)
variable (Bp : Bar.fn p)
#check fn Bp
/-
 error: function expected at
  Fn.imp fn ?m.710
term has type
  Bar.fn ?m.710
-/
#check fn p
/-
error: function expected at
  Fn.imp fn ?m.811
term has type
  Bar.fn ?m.811
-/
#check fn (p := p)
/-
Fn.imp fn p : Bar.fn p
-/

@leodemoura Given how I wrote the example, yeah that is actually what should be expected. I accidently simplified my original example so much that #check fn Bp is actually invalid. Here is a better example:
variable (fn' : Fn ((p : P) -> B.fn p -> B.fn p) ({p : P} -> B.fn p -> B.fn p))

-- Expect no error
#check fn' Bp

-- Expect error
#check fn' p


Add CI. Enforce code reviews?

We have CI now. Review enforcing is to be decided, we'll see how it goes.


Can we load verifier once, and use same for multiple message token  verification  instead of creating new object each time

Hi,
Thanks for the library, i am fairly new to this.
Able to run it using examples. However, need help as i have multiple messages incoming which need verification using same verifier, which i want to be loaded once at startup.
Since using auto unable to define default verifier class object which could be initialised later at startup.
Tried using the provided constructor:
explicit verifier(Clock )
verifier instance in .h file:
jwt::verifier<jwt::default_clock, jwt::picojson_traits> messageValidator_(jwt::default_clock);
Initialising same by reading config of application on startup once :
messageValidator_ = jwt::verify().allow_algorithm(jwt::algorithm::rs256(pub_key, "", "", "")).with_audience(audience);
Using this object messageValidator_ each time message comes in  :
messageValidator_.verify(decode);
This doesn't Compiles, unable to figure this. Really appreciate some help or some correction in case wrong.
Thanks.

Can you please provide OS, Compiler (and version) along with the error you are getting?
Also since you are using the picojson_traits you can skip the template specialization.

Header

class my_verification {
   jwt::verifier<jwt::default_clock, jwt::picojson_traits> messageValidator_ { default_clock{} };

   my_verification();
}

Source

my_verification::my_verification() {
   messageValidator_.allow_algorithm(jwt::algorithm::rs256(pub_key, "", "", "")).with_audience(audience);
}

Can you please provide OS, Compiler (and version) along with the error you are getting?
Also since you are using the picojson_traits you can skip the template specialization.

Header

class my_verification {
   jwt::verifier<jwt::default_clock, jwt::picojson_traits> messageValidator_ { default_clock{} };

   my_verification();
}

Source

my_verification::my_verification() {
   messageValidator_.allow_algorithm(jwt::algorithm::rs256(pub_key, "", "", "")).with_audience(audience);
}

I just tested it and the following compiles just fine:
class sample {
public:
    jwt::verifier<jwt::default_clock, jwt::picojson_traits> m_verify;
    sample()
        : m_verify{jwt::verify()}
    {
        m_verify.allow_algorithm(jwt::algorithm::rs256(rsa_pub_key, rsa_priv_key, "", "")).with_issuer("auth0");
    }
};

int main(int argc, const char** argv) {
    sample s;
	auto decoded = jwt::decode(token);
	s.m_verify.verify(decoded);
	for (auto& e : decoded.get_header_claims())
		std::cout << e.first << " = " << e.second.to_json() << std::endl;
	for (auto& e : decoded.get_payload_claims())
		std::cout << e.first << " = " << e.second.to_json() << std::endl;
}

Here is the full example, just with .txt cause github does not like .cpp.
example.cpp.txt

I just tested it and the following compiles just fine:
class sample {
public:
    jwt::verifier<jwt::default_clock, jwt::picojson_traits> m_verify;
    sample()
        : m_verify{jwt::verify()}
    {
        m_verify.allow_algorithm(jwt::algorithm::rs256(rsa_pub_key, rsa_priv_key, "", "")).with_issuer("auth0");
    }
};

int main(int argc, const char** argv) {
    sample s;
	auto decoded = jwt::decode(token);
	s.m_verify.verify(decoded);
	for (auto& e : decoded.get_header_claims())
		std::cout << e.first << " = " << e.second.to_json() << std::endl;
	for (auto& e : decoded.get_payload_claims())
		std::cout << e.first << " = " << e.second.to_json() << std::endl;
}

Here is the full example, just with .txt cause github does not like .cpp.
example.cpp.txt

Thanks this compiles fine, however gives a runtime exception:
[json.exception.type_error.302] type must be string, but is null, err2=0
Also can i disable picojson and then try to define a default object to verifier ?
jwt::verifierjwt::default_clock m_verify;

Thanks this compiles fine, however gives a runtime exception:
[json.exception.type_error.302] type must be string, but is null, err2=0
Also can i disable picojson and then try to define a default object to verifier ?
jwt::verifierjwt::default_clock m_verify;

[json.exception.type_error.302] type must be string

That does not come from picojson 😖
Please share your system information along with a small snippet of code such that we can help.

[json.exception.type_error.302] type must be string

That does not come from picojson 😖
Please share your system information along with a small snippet of code such that we can help.

Yes, you are right, i was mistake at my end while passing the key.
Rectified same.
Below are system details:
OS: Linux Centos 7
Compiler :gcc (GCC) 5.4.0
Also verification works now as per code you shared. No issues at my end now.
I have used Nlohmann traits so used :
Validator::Validator()
: messageValidator_{jwt::verify<jwt::default_clock, nlohmann_traits>({})}
Also i see in example nolhmann_traits struct is not present in lib and need to be defined at users end.
Please correct in case i am missing something.

Yes, you are right, i was mistake at my end while passing the key.
Rectified same.
Below are system details:
OS: Linux Centos 7
Compiler :gcc (GCC) 5.4.0
Also verification works now as per code you shared. No issues at my end now.
I have used Nlohmann traits so used :
Validator::Validator()
: messageValidator_{jwt::verify<jwt::default_clock, nlohmann_traits>({})}
Also i see in example nolhmann_traits struct is not present in lib and need to be defined at users end.
Please correct in case i am missing something.

Thanks a lot, verification works now as per code you shared. No issues at my end now.

🎉
You are correct the nlohmann_traits are not public yet, soon 🙏

Thanks a lot, verification works now as per code you shared. No issues at my end now.

🎉
You are correct the nlohmann_traits are not public yet, soon 🙏


Add Vendor Prefixing to -webkit-align-items

Description:
Add the standard style rule for align-items in addition to the vendor prefixed version -webkit-align-items
Screenshots:

Fixed in #49.


Simplify "Contact" block's markup

As seen in https://www.zeiss.de/semiconductor-manufacturing-technology/news-und-events/smt-pressemeldung/europaeischer-erfinderpreis-2018.html#presseinformation

This is handeled by the "Contact" block. This task is logged to simplify the markup generated by this block here
https://github.com/hlxsites/zeiss/blob/b61a426d949efe128cb53fc54522df7a8a1568cc/blocks/contact/contact.js#L5-L74

Example article with multiple contacts https://www.zeiss.de/semiconductor-manufacturing-technology/news-und-events/smt-pressemeldung/deutscher-zukunftspreis-2020-euv.html


Readme is incorrectly formatted on PYPI

Due to use of markdown, and some conversion issues, readme is not formatted correctly once it makes its way to PYPI

Fixed in version 1.4.0


Saving a cell array containing all paths from each node to another

Hi, I was wondering if you could help. thanks for the great work.
I have an adj matrix. I just need a cell array containing all possible paths from each node to another, so that I can use it later in my algorithm.
In fact, I want the cell array to look like this:
1to1  | 1to2      | ...  | 4to3    | 4to4
{}       | {1,2}       | ... | {4,3}     | {}
| {1,4,2}    | ... | {4,1}     |
| {1,4,3,2} | ... | {4,2}     |
|               | ... | {4,3,2} |
|               | ... | {4,1,2} |
|               | ... | ...        |

I mean the real problem is we don't know how many paths each column would have

I’d just suggest setting up a cell array and then looping over the possible source/sink pairs. No need to know how big each cell element will be.
pth = cell(nnode);
for isrc = 1:nnode
    for itar = 1:nnode
        pth{isrc,itar} = pathbetweennodes(adj, isrc, itar);
    end
end

Thank you, man... Your help meant a lot to me.


Add bazel support for easier external integration

Many enterprise companies use Bazel to build their softwawre. Among them Qwello, BMW, Fernride.
Bazel is very good suitable for large repositories, because it ensures correctness of the incremental builds. And therefor even on large code bases CI can handle testing every commit.
To make adoption of Everest easier in such projects we may ship bazel rules for everest-framework.
In this PR bazel rules are added that allow to build everest-framework library, manager and controller.
The proposed usage is described in bazel/README.md.

Following the process that was suggested on the TSC meeting yesterday, we'd like to merge this best-effort support for Bazel which we have been using internally. Having it here makes it easier to keep in sync with future development of the framework and also makes it easy for others to use this in their own build processes.
@corneliusclaussen @caller or any other: any inputs on this?

@corneliusclaussen @caller or any other: any inputs on this?

I'm good with this, but I also think we should put a warning in the Readme or so stating that this build method is wip and your milage may vary.

To get this merged pls look at the comments and especially at the caching key and mark as "Ready for review" when you are done.

I've addressed all comments.


enhancement: ability to view /stats, /integrations, /about pages in the app

would be nice to have those links below show up directly in the app but then we also need a working 'go back' to home button
https://chat.zulip.org/stats
/integrations
/about
pages in the app

@vbNETonIce can you explain why you would prefer these to be in the app (and are the reasons the same for each)?  For several of these pages, we want them to be visible to Google (and thus there's benefit in them not being part of the app).  We could move some (e.g. /stats) into a modal like the settings UI, but it would offer a bit less space on the screen for the actual content.

Oh, I see this is a desktop app issue.  I can see why you'd want it to not open a browser window when those are clicked; is that the motivation?

yes, I mean the desktop app. It doesn't quite make sense since it's Zulip server related and the users would probably expect it to appear right in front of them rather than in an entirely different application (ie. browser).

@vbNETonIce If you click on /integrations it will open in the app, not in the browser and you could always go back using CommandOrCtrl+[ keyboard shortcut.

cool, I tried and it worked. So if /stats will open in a popup soon, we can close this issue already...

To open it in the app, /stats should be hyperlinked somewhere in the webapp just like /integrations.

Yeah, I think we can close this issue.  The plan for #204 should address this as well.


Added support for negative index

https://github.com/sindresorhus/negative-array

Is this possible to implement efficiently?

Without an ES6 Proxy, that is

I do not think so. The reference is for inspiration, but will be difficult bring this feature in the library.
Add others polyfills is not a good idea, because increases considerably the size of the library.
In addition, ES6 Proxy is poor supported, and the current most famous polyfill need special node/browser flags. I would like have this in the library, but too much friction for the final user that is the thing that we try to avoid.

I think the next best thing to negative indexes were if the .last() method could accept (n) and return the [length - n]th element.

@mk-pmb can you provide example of your idea?

function guessScriptTagBeforeCurrent() {
  return Array.from(document.getElementsByTagName('script')).last(2);
}

I think nowadays make sense ship this feature now that Node.js supports Proxy :)
Added https://github.com/sindresorhus/cycled as inspiration, should be done very similar.
Any PR? 🎉


[Typescript] Add actionParams attribute to Message interface

Sometimes adding action attribute is not enough and additional parameters has to be set.
This change allows to set additional parameters in actionParams field.
The alternative solution would be to allow adding any parameters to Message, by setting [index: string]: any at the top level.

If anybody else needs this, it is possible to extends Message declaration by adding this code to your project:
declare module 'botkit' {
    interface Message {
        actionParams ?: {
            [index: string]: any
        };
    }
}


Create README.hi.md for Hindi translation

Correct Hindi translation for the original README.md file

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

Thanks for taking the time to contribute this localization pull request. However, we are not able to accept contributions to this historical reference repository at this time.