docs: add framework

Codecov Report

Merging #19 (b82aa20) into master (6f24901) will not change coverage.
The diff coverage is n/a.

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


Playready Content with mixed segment (having both encrypted and unencrypted segments) is not playing in Shaka Player Demo App

What version of Shaka Player are you using?
Shaka Player v2.0.0-debug

Can you reproduce the issue with our latest release version?
Yes
Can you reproduce the issue with the latest code from master?
Yes

Are you using the demo app or your own custom app?
Demo

If custom app, can you reproduce the issue using our demo app?

What browser and OS are you using?
Browser - IE11,  Microsoft Edge
OS - Windows10

What did you do?
I created two contents having first few segments encrypted followed by few unencrypted segments followed by encrypted segments.

case 1) Content having two boxes under stsd in init segment: one for encrypted and other for unencrypted playback. In media segment, it has "Sample Description Index" set to 2 for unencrypted segments.
case 2) Same Content as above but having sgpd with 0 iv size and kid info & sbgp boxes for unencrypted content.
I tried to play both contents in Shaka player for both Widevine and Playready DRM. Content is playing fine for Widevine DRM but for Playready it is not playing instead giving MEDIA.VIDEO_ERROR.

What content did you load?
Custom

If standard demo asset, which one?

If custom asset, what manifest and license server URIs?
Manifest:
http://<IP_ADDRESS>/mm/dash/vod/flr/test1/VODSERVICE_1234/TG_TEST_SD.mpd (Case 1)
http://<IP_ADDRESS>/mm/dash/vod/flr/test/VODSERVICE_1234/TG_TEST_SD.mpd (Case 2)

License Server URL:
http://<IP_ADDRESS>/drmclientproxy/playready/get_license

How did you interact with the content, if at all?
This content i created locally and using local server for getting license.

What did you expect to happen?
I expected playback to happen

What actually happened?
Content is playing fine for first few encrypted segments and when unencrypted segment is about to play, giving  MEDIA.VIDEO_ERROR.

This same contents are playing fine for Widevine. Please suggest me if i am missing something for Playready DRM?

Please find the License Server URL for Playready:
http://<IP_ADDRESS>/drmclientproxy/playready/get_license

@rajlaxmi28, @sivarajendranaidu, do you have a license server URL for Widevine as well?  It might be useful to compare working vs non-working playback on the same content.
It seems that some part of this content might be incompatible with either PlayReady or the media stack in Edge.  I'm not sure if they support "clear lead" content or not, and I'm not sure where they would have that documented.  I recommend that you file a ticket with Microsoft about this.  If you do, please link to it here so we can follow along.
Here's a link to the demo with your URLs pre-filled: https://shaka-player-demo.appspot.com/demo/#asset=//<IP_ADDRESS>/mm/dash/vod/flr/test1/VODSERVICE_1234/TG_TEST_SD.mpd;license=//<IP_ADDRESS>/drmclientproxy/playready/get_license
Note, though, that your links are plain HTTP, and will not be accessible to an app running on HTTPS.  You will want to run an SSL-enabled service on port 443 before sending the above link in a Microsoft ticket.

@joeyparrish thanks a lot your support. With reference https://github.com/Dash-Industry-Forum/dash.js/issues/1615 this issue seams to with Edge Browser. Once we update the Windows (Edge Browser > 38) it worked well with our Shaka Player.
Hence its not our player issue

Okay.  Seems to be fixed in EdgeHTML 14, so I'm going to close it now.  Thanks for the report!


Add support for using software rendering and improve CI

This is a moderately large change set.
First thing's first, the biggest feature is the addition of support to CMake to automatically download and install the Mesa 3D library to the build output directory so that it will be used instead of the system provided library on Windows.
This opens up multiple opportunities:

We can use software rendering when running CI since it will provide a much better OpenGL implementation than the lousy one Windows provides by default
We can use OpenGL->DX12 translation if for whatever reason on developer workstations the provided OpenGL implementation is lousy or no longer up-to-date
We can build and test OpenGL ES code even on non-mobile platforms (currently only Windows) where normally only "desktop" OpenGL is provided by the operating system

Just this change alone should lower the barrier to entry of working on OpenGL/OpenGL ES code independent of the concrete system the developer is working on. It isn't unreasonable to assume that DX will always be well supported and widely available on Windows systems.
To make use of Mesa 3D, all the user has to do is enable the SFML_USE_MESA3D CMake option and CMake will take care of the rest when it runs the configuration. The necessary *.dlls will be automatically copied to the right places when examples/tests are built. For a developer working in their IDE this is not noticeable at all and they can keep working as they always have.
Further changes:

Added Visual Studio OpenGL ES jobs to CI so that we can provide testing and coverage for that code as well
Force all CI Mesa 3D implementations to use llvmpipe (software renderer), even when running on Unix-based platforms, this should provide a more consistent environment to work in
Added graphics/display related tests that were impractical when using the default OpenGL implementation on Windows
Fixed bugs that were discovered by the newly added tests

Updated with suggested changes and fixed context management in a couple places.

Rebased to master.

Rebased to master.

Rebased to master.


Refactor WindowService

The problems with the current system are that every time we want to add a model with a new sequence length for an existing model provider, the user has to:

Create a new CONTEXT_WINDOW_TAG
Create a new WindowService that sets the new sequence length
Modify framework code in WindowServiceFactory.get_window_service

The issues here are:

Proliferation of model tags.
It's hard to tell the sequence length of each model, and easy to introduce bugs by introducing the wrong sequence length.
The huge if-else branch tree in WindowServiceFactory is not user-friendly, and is a potential source of bugs.

The proposed refactor:
Currently we have WindowService has a ton of stuff:

Model metadata: tokenizer_name, max_sequence_length, max_request_length
Tokenizer metadata: end_of_text_token, prefix_token
Tokenizer operations: tokenize, encode, decode, get_num_tokens
Windowing logic: fits_within_context_window, truncate_from_right

We should break these out of WindowService as follows:

Move model metadata to the model: tokenizer_name, max_sequence_length, max_request_length
Move tokenizer metadata to the tokenizer: end_of_text_token, prefix_token
Tokenizer operations are tricky because some of these do additional stuff before passing to the underlying tokenizer.

So basically WindowService should only contain the windowing logic. This should also allow us to unify most of the WindowServices that are just thin wrappers around the same logic.

The plan is to introduce a new Tokenizer object that would look like this:
class Tokenizer(ABC):
    @property
    @abstractmethod
    def name(self) -> str:
        """The name of the tokenizer."""
        pass

    @property
    @abstractmethod
    def end_of_text_token(self) -> str:
        """The end of text token."""
        pass

    @property
    @abstractmethod
    def prefix_token(self) -> str:
        """The prefix token"""
        pass

    @abstractmethod
    def encode(self, text: str, truncation: bool = False, max_length: Optional[int] = None) -> EncodeResult:
        """Encodes the input text to tokens given the model"""
        pass

    @abstractmethod
    def decode(self, tokens: List[TokenizationToken], normalized_text: Optional[str] = None) -> str:
        """
        Given the model and a list of tokens, outputs the corresponding text.

        For models using the GPT-2 tokenizer, the tokens are integers; for AI21
        models, the tokens are `TokenizationToken`s.

        Some tokenizers (e.g. AI21) normalize the text before encoding it and
        thus require the `normalized_text` for decoding.
        """
        pass

    @abstractmethod
    def tokenize(self, text: str) -> List[str]:
        """Tokenizes the text."""
        pass

    @abstractmethod
    def get_num_tokens(self, text: str) -> int:
        """Tokenizes the text and counts the number of tokens."""
        pass

This is more or less done by #1903 and #1943.
There is some remaining cleanup (e.g. remove the tokenize method from WindowService) but that is relatively minor.


BUG: stats.tukeylambda: Fix the support() method.

Closes gh-21369.

There is a new unrelated test failure on github actions: Windows tests / fail slow, full, py3.10/npMin, dev.py. It is the sparse linalg test TestExpmActionInterval.test_expm_multiply_interval_matrix


Update kubernetes.md

Updated the installer to align with the new 1.1.0 installer

This is covered in PR 26


include pthread in app -> compilation failed

Hi,
I tried to compile "hello world" with "pthread" include but compilation fail (without pthread compilation pass).
my compilation steps:
rm -rf  build && mdir build && cd build;
cmake -GNinja -DBOARD=qemu_x86 ..
ninja
#include <zephyr.h>
#include <misc/printk.h>
#include <pthread.h>

void main(void)
{
	printk("Hello World! %s\n", CONFIG_ARCH);
}

I got the following errors:
.dir/src/main.c.obj.d -o CMakeFiles/app.dir/src/main.c.obj   -c ../src/main.c
In file included from /home/ehudn/work/zephyr/zephyr/include/posix/time.h:26:0,
                 from /home/ehudn/work/zephyr/zephyr/include/posix/pthread.h:11,
                 from ../src/main.c:9:
/home/ehudn/work/zephyr/zephyr/include/posix/signal.h:37:2: error: unknown type name ‘pthread_attr_t’
  pthread_attr_t *sigev_notify_attributes;
  ^~~~~~~~~~~~~~
In file included from /home/ehudn/work/zephyr/zephyr/include/posix/pthread.h:11:0,
                 from ../src/main.c:9:
/home/ehudn/work/zephyr/zephyr/include/posix/time.h:52:33: error: unknown type name ‘clockid_t’
 static inline int clock_settime(clockid_t clock_id, const struct timespec *ts)
                                 ^~~~~~~~~
/home/ehudn/work/zephyr/zephyr/include/posix/time.h:58:19: error: unknown type name ‘clockid_t’
 int clock_gettime(clockid_t clock_id, struct timespec *ts);
                   ^~~~~~~~~
/home/ehudn/work/zephyr/zephyr/include/posix/time.h:60:18: error: unknown type name ‘clockid_t’
 int timer_create(clockid_t clockId, struct sigevent *evp, timer_t *timerid);
                  ^~~~~~~~~
/home/ehudn/work/zephyr/zephyr/include/posix/time.h:60:59: error: unknown type name ‘timer_t’
 int timer_create(clockid_t clockId, struct sigevent *evp, timer_t *timerid);
                                                           ^~~~~~~
/home/ehudn/work/zephyr/zephyr/include/posix/time.h:61:18: error: unknown type name ‘timer_t’
 int timer_delete(timer_t timerid);
                  ^~~~~~~
/home/ehudn/work/zephyr/zephyr/include/posix/time.h:62:19: error: unknown type name ‘timer_t’
 int timer_gettime(timer_t timerid, struct itimerspec *its);
                   ^~~~~~~
/home/ehudn/work/zephyr/zephyr/include/posix/time.h:63:19: error: unknown type name ‘timer_t’
 int timer_settime(timer_t timerid, int flags, const struct itimerspec *value,
                   ^~~~~~~
In file included from /home/ehudn/work/zephyr/zephyr/include/posix/pthread.h:12:0,
                 from ../src/main.c:9:
/home/ehudn/work/zephyr/zephyr/include/posix/unistd.h:16:12: error: unknown type name ‘useconds_t’
 int usleep(useconds_t useconds);
            ^~~~~~~~~~
In file included from ../src/main.c:9:0:
/home/ehudn/work/zephyr/zephyr/include/posix/pthread.h:37:2: error: unknown type name ‘pthread_mutex_t’
  pthread_mutex_t cancel_lock;
  ^~~~~~~~~~~~~~~
/home/ehudn/work/zephyr/zephyr/include/posix/pthread.h:41:2: error: unknown type name ‘pthread_mutex_t’
  pthread_mutex_t state_lock;

Should I add some POSIX flag into prj.conf? or into CMakeLists.txt?
Thanks!

@ehudmarvell  can you also dump the prj.conf kconfig options here

please with following changes:
Add  CONFIG_PTHREAD_IPC=y in prj.conf file
Add "target_include_directories(app PRIVATE $ENV{ZEPHYR_BASE}/include/posix)" in CMakeLists.txt
It works for with sample/hello_work app.

tried with hello world and above settings, works fine.


Update Project Portfolio in semjinghan.adoc

Coverage remained the same at 71.675% when pulling ccac7aa15b5c5c71a11b8e68c060487a519e0745 on Kratious:ppp into 74d66506e9942fb5bae01b9700163aeceb35d09d on CS2103-AY1819S1-W16-2:master.


Dynamic height rows seems to cause the issues list to shuffle

I noticed that once we supported dynamic height on the issues list, the table reshuffles strangely when scrolling.
Another (probably related) thing is this occasionally causes our labels to no longer wrap & cause their cell to increase in height, instead reverting to truncating with ellipses ('...').

@bjtitus is looking into this

Likely what I see doing this as well

@mccarron @subdigital See if that PR fixes your issue. The unnecessary reload call is what was triggering this for me. Let me know if you're seeing it in other cases with that call removed.


ninja never completes, build seems to loop on syscalls.

CyberEther@a6e9e08a0a8dce4385b606e585500c09e3603a1e
OSX 13.4.1, meson 1.2.99, ninja 1.11.1
Meson seems to configure build fine but ninja seems to loop indefinitely burning CPU in system calls (See attachments)
command_line:

fs_usage out:

htop:

The Meson build system
Version: 1.2.99
Source dir: /Users/ianb/src/luigifcruz/CyberEther
Build dir: /Users/ianb/src/luigifcruz/CyberEther/build
Build type: native build
Project name: cyberether
Project version: 0.0.0
C++ compiler for the host machine: c++ (clang 14.0.3 "Apple clang version 14.0.3 (clang-14<IP_ADDRESS>.1)")
C++ linker for the host machine: c++ ld64 857.1
Host machine cpu family: aarch64
Host machine cpu: aarch64
Run-time dependency threads found: YES

Executing subproject jetstream

jetstream| Project name: jetstream
jetstream| Project version: 0.1.0
jetstream| C++ compiler for the host machine: c++ (clang 14.0.3 "Apple clang version 14.0.3 (clang-14<IP_ADDRESS>.1)")
jetstream| C++ linker for the host machine: c++ ld64 857.1
jetstream| Dependency threads found: YES unknown (cached)
jetstream| Found pkg-config: YES (/opt/homebrew/bin/pkg-config) 0.29.2
jetstream| Run-time dependency fmt found: YES 10.1.0
jetstream| Run-time dependency CUDA (modules: cudart_static, dl) found: NO (tried system)
jetstream| Run-time dependency fftw3f found: YES 3.3.10
jetstream| Run-time dependency appleframeworks found: YES (MetalKit, Metal, Foundation)
jetstream| Program glslangValidator found: YES (/opt/homebrew/bin/glslangValidator)
jetstream| Program spirv-cross found: YES (/opt/homebrew/bin/spirv-cross)
jetstream| Program python3 found: YES (/opt/homebrew/bin/python3)
jetstream| Run-time dependency glfw3 found: YES 3.3.8
jetstream| Run-time dependency soapysdr found: YES 0.8.1
jetstream| Run-time dependency vulkan found: YES 1.3.263
jetstream| Program glslangValidator found: YES (/opt/homebrew/bin/glslangValidator)
jetstream| Program python3 found: YES (/opt/homebrew/bin/python3)
jetstream| Program glslangValidator found: YES (/opt/homebrew/bin/glslangValidator)
jetstream| Program python3 found: YES (/opt/homebrew/bin/python3)
jetstream| Program glslangValidator found: YES (/opt/homebrew/bin/glslangValidator)
jetstream| Program spirv-cross found: YES (/opt/homebrew/bin/spirv-cross)
jetstream| Program naga found: YES (/opt/homebrew/bin/naga)
jetstream| Program python3 found: YES (/opt/homebrew/bin/python3)
jetstream| Objective-C++ compiler for the host machine: c++ (clang 14.0.3)
jetstream| Objective-C++ linker for the host machine: c++ ld64 857.1
jetstream| Configuring jetstream_config.hh using configuration
jetstream| Build targets in project: 36
jetstream| Subproject jetstream finished.

Build targets in project: 37```

Thanks for reporting this bug!
Looks like this is a multifactorial bug. For it to happen two things need to happen:

Brew incorrectly reports naga is installed.
Python script, for some reason, busy-looping into oblivion trying to execute something non-existent.

Naga is required by CyberEther to convert the GLSL shaders to the WebGPU Shading Language. I'm working on fixing these two failure points, but in the meantime, the absolute minimal fix for this would be installing the naga package with brew.

I'm actually impressed by how random these errors had to be to create this multi-threaded busy loop. 😄

Oh, the plot thickens. This is likely due to the snake game named Naga being installed instead of the shader translator named Naga. The busy loop is caused by the game Naga running on a virtual terminal session.
I initially tried to fix this conflict by checking the version of the Naga binary installed. But the game Naga doesn't respond to the --version command. I'm thinking about another alternative.

Ha! This starts to make sense...I double checked I had a homebrew naga install earlier today, then scratched my head!!

Done! The commit above should fix this problem. It compiles Naga from the source automatically instead of relying on the script installed by Brew. This looks a bit overkill but is fine considering no package manager on Linux has Naga, so this had to be done anyway. Let me know if this works for ya!

The first alpha release is now live. This issue should be resolved by now. Please re-open otherwise. Thanks!


@/codeforafrica/components/Footer

Using @commons-ui/core/ImageButton, @/codeforafrica/components/StayInTouch, @/codeforafrica/components/NavList, and @/codeforafrica/components/NewsletterSubscription, create a site footer component.
Footer in mobile:

Footer in desktop:

Fixed by #60


Added locations field to VLAN.

Closes: #4412
What's Changed

TODO

[ ] Explanation of Change(s)
[ ] Added change log fragment(s) (for more information see the documentation)
[ ] Attached Screenshots, Payload Example
[ ] Unit, Integration Tests
[ ] Documentation Updates (when adding/changing features)
[ ] Example Plugin Updates (when adding/changing features)
[ ] Outline Remaining Work, Constraints from Design

@timizuoebideri1 lets move this PR back to draft until we can have a design discussion


bump: [#4684] Upgrade rimraf dependency to v5

Addresses # 4684
#minor
Description
This PR updates the rimraf package to version 5.0.10, the latest compatible version with Node 18.
Specific Changes

Updated rimraf from 3.0.2 to 5.0.10 in root's package.json.
Fixed import statement in botbuilder-core/tests/transcriptUtilities.js file.

Testing
The following image shows the unit tests in botbuilder-core passing after the upgrade.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>0
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.4%) to 84.997%

Totals

Change from base Build<PHONE_NUMBER>9:
-0.4%

Covered Lines:
20351

Relevant Lines:
22910

💛  - Coveralls

/promoted 4761


BUG: fix multiple columns as primary key in io.sql.get_schema (GH10385)

Closes #10385

Apparantly there was also an bug in the fallback version, it could only handle single character column names ...
@artemyk time we clean this up :-) (I will try to look at your ideas on get_schema and others next week!)

@jreback any remarks?


val_acc KeyError using ModelCheckpoint.

Hi, i am using ModelCheckpoint callback to monitor 'val_acc' and I get this error
File "/usr/local/lib/python2.7/dist-packages/keras/engine/training.py", line 1485, in fit
initial_epoch=initial_epoch)
File "/usr/local/lib/python2.7/dist-packages/keras/engine/training.py", line 1160, in _fit_loop
callbacks.on_epoch_end(epoch, epoch_logs)
File "/usr/local/lib/python2.7/dist-packages/keras/callbacks.py", line 75, in on_epoch_end
callback.on_epoch_end(epoch, logs)
File "/usr/local/lib/python2.7/dist-packages/keras/callbacks.py", line 383, in on_epoch_end
filepath = self.filepath.format(epoch=epoch, **logs)
KeyError: 'val_acc'
Looked at Keras codebase but could not debug it, why is this error coming?

bump

Just found out why this is happening, it seems you have to register for accuracy metrics on the method compile, like this:
model.compile(loss='mse', optimizer='adam', metrics=['accuracy'])
hope this helps

doing the same
bu that did not help
On Sun, Apr 2, 2017 at 2:07 AM, William Queen<EMAIL_ADDRESS>wrote:

Just found out why this is happening, it seems you have to register for
accuracy metrics on the method compile, like this:
model.compile(loss='mse', optimizer='adam', metrics=['accuracy'])
hope this helps
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/fchollet/keras/issues/6104#issuecomment-290945569,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQ2XI02XUI5BpKVDXQlwG59_6O_ZRrXjks5rrrVtgaJpZM4Mwdwy
.

--
Regards,
Mukul Arora
Delhi Technological University
+91-9868430208

@badjano  anything else could you suggest?

Did you run model.fit() with validation_split or validation_data?
I met the same error and it's gone if I set validatoin_split=0.1.

This is my code, it is working, hope it helps:
`self.model = Sequential()
self.model.add(Dense(input_dim=_in, output_dim=_out, init="glorot_uniform"))
self.model.add(Activation("sigmoid"))
self.filepath = "weights.hdf5"
if os.path.isfile(self.filepath):
self.model.load_weights(self.filepath)
self.model.compile(loss='mse', optimizer='adam', metrics=['accuracy'])
checkpoint = ModelCheckpoint(self.filepath, monitor='val_acc', verbose=0, save_best_only=False, mode='max')
self.model.fit(X, Y, nb_epoch=10000, batch_size=10, verbose=1, callbacks=[checkpoint], shuffle=True)`
One other thing, make sure you install h5py module, that is required for checkpoints

ur keras version?
On Tue, Apr 4, 2017 at 7:17 PM, William Queen<EMAIL_ADDRESS>wrote:

This is my code, it is working, hope it helps:
`self.model = Sequential()
self.model.add(Dense(input_dim=_in, output_dim=_out,
init="glorot_uniform"))
self.model.add(Activation("sigmoid"))
self.filepath = "weights.hdf5"
if os.path.isfile(self.filepath):
self.model.load_weights(self.filepath)
self.model.compile(loss='mse', optimizer='adam', metrics=['accuracy'])
checkpoint = ModelCheckpoint(self.filepath, monitor='val_acc', verbose=0,
save_best_only=False, mode='max')
self.model.fit(X, Y, nb_epoch=10000, batch_size=10, verbose=1,
callbacks=[checkpoint], shuffle=True)`
One other thing, make sure you install h5py module, that is required for
checkpoints
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/fchollet/keras/issues/6104#issuecomment-291504519,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQ2XI9HLtuGPtQfY5q9t_Ju8qpQkUa5nks5rsknZgaJpZM4Mwdwy
.

--
Regards,
Mukul Arora
Delhi Technological University
+91-9868430208

keras.version = 1.2.2

updated to 2.0.2, still working ;)

I have the same issue when using ModelCheckpoint and fit_generator. My Keras is 2.0.5.

Fixed this issue ... just remove the 'accuracy' keyword from your checkpoint file point.

I had the same problem, and I solved removing the callback "checkpoint". The code is:
checkpoint = ModelCheckpoint('deep-learning-model-full-v0.03.01.weights-improvement-{epoch:02d}-{val_acc:.2f}.hdf5'                              , monitor='val_loss'                              , verbose=1                              , save_best_only=True                              , period=3)

I solve the problem removing my callback. The code is:
checkpoint = ModelCheckpoint('deep-learning-model-full-v0.03.01.weights-improvement-{epoch:02d}-{val_acc:.2f}.hdf5'                              , monitor='val_loss'                              , verbose=1                              , save_best_only=True                              , period=3)

Just remove the "{val_acc:.2f}" from the checkpoint file name. It will work fine.

Use val_loss in place of val_acc
keras.callbacks.ModelCheckpoint(filepath, monitor='val_loss', verbose=0, save_best_only=False, save_weights_only=False, mode='auto', period=1)

I had the same problem and it was because I set validation_freq > 1 (so the callback did not have all the time access to the "val_acc" value).

change "{val_acc:.2f}"  to "{val_accuracy:.2f}" It will work fine.
as no variable named "val_acc" is defined but what you are trying to get is accuracy value after each epoch,  which is probably defined as "val_accuracy" :) +1:

I had the same problem, but i named the variable correctly (val_accuracy).
After a restart of my PC it worked

please help me to resolve this error....
TypeError: init() got an unexpected keyword argument 'restore_best_weights'

this is my code... while training the model...
from keras.optimizers import RMSprop, SGD, Adam
from keras.callbacks import ModelCheckpoint, EarlyStopping, ReduceLROnPlateau
checkpoint = ModelCheckpoint("emotion_little_vgg_3.h5",
monitor="val_loss",
mode="min",
save_best_only = True,
verbose=1)
earlystop = EarlyStopping(monitor = "val_loss",
min_delta = 0,
patience = 3,
verbose = 1,
restore_best_weights = True)
reduce_lr = ReduceLROnPlateau(monitor = 'val_loss', factor = 0.2, patience = 3, verbose = 1, min_delta = 0.0001)
we put our call backs into a callback list
callbacks = [earlystop, checkpoint, reduce_lr]
We use a very small learning rate
model.compile(loss = 'categorical_crossentropy',
optimizer = Adam(lr=0.001),
metrics = ['accuracy'])
nb_train_samples = 28273
nb_validation_samples = 3534
epochs = 10
history = model.fit_generator(
train_generator,
steps_per_epoch = nb_train_samples // batch_size,
epochs = epochs,
callbacks = callbacks,
validation_data = validation_generator,
validation_steps = nb_validation_samples // batch_size)

Just rename val_acc to val_accuracy and it should work fine

https://github.com/keras-team/keras/issues/6104#issuecomment-449293676
我解决这个问题，通过暂时使用chekpoint的代码

Just rename val_acc to val_accuracy and it should work fine

still it's not working for me

Did you check to make sure your validation_generator is actually finding validation files?  If it doesn't find any files, for whatever reason, this error will also be thrown.

The answer has already been posted above: change val_acc to val_accuracy will fix it in most cases. The reason is a change in Keras2.3.0:

Metrics and losses are now reported under the exact name specified by the user (e.g. if you pass metrics=['acc'], your metric will be reported under the string "acc", not "accuracy", and inversely metrics=['accuracy'] will be reported under the string "accuracy".

https://github.com/keras-team/keras/releases/tag/2.3.0
In my case, I was using BinaryAccuracy, so my callback had to match that:
model.compile(optimizer=keras.optimizers.Adam(learning_rate),
            loss=keras.losses.BinaryCrossentropy(from_logits=True),
            metrics=[keras.metrics.BinaryAccuracy()])
mcp_save_acc = keras.callbacks.ModelCheckpoint('saved_model_' + datetime.datetime.now().strftime('%Y%m%d_%H%M') + '-epoch{epoch:02d}-val_binary_accuracy{val_binary_accuracy:.2f}.hdf5', save_best_only=True, monitor='val_binary_accuracy', mode='max')

I had the same problem. Finally fixed this error (KeyError: 'val_acc) . On my side, this error is occurred due to Keras version. downgrade Keras version to 2.2.4 and error is removed
Helping Source

I also facing same error , could you give a solution
Traceback (most recent call last):
File "main.py", line 34, in
helper.exec()
File "C:\Users\30863\Downloads\Function-level\src\helper.py", line 284, in exec
class_weight = class_weights)
File "C:\Users\30863\Anaconda3\envs\pythonProject1\lib\site-packages\keras\engine\training.py", line 1039, in fit
validation_steps=validation_steps)
File "C:\Users\30863\Anaconda3\envs\pythonProject1\lib\site-packages\keras\engine\training_arrays.py", line 217, in fit_loop
callbacks.on_epoch_end(epoch, epoch_logs)
File "C:\Users\30863\Anaconda3\envs\pythonProject1\lib\site-packages\keras\callbacks.py", line 79, in on_epoch_end
callback.on_epoch_end(epoch, logs)
File "C:\Users\30863\Anaconda3\envs\pythonProject1\lib\site-packages\keras\callbacks.py", line 429, in on_epoch_end
filepath = self.filepath.format(epoch=epoch + 1, **logs)
KeyError: 'val_accuracy'


mobile-relay: Fixed props for PrivateApiRenderer

PrivateApiRendererWithContext as default export should take authHeaderKey as a prop and forward it to PrivateApiRenderer and accessToken is optional since it is taken from context and not provided via props.

@tbergq Done! :)


Underscore instead of dash

In the @postag attribute the last value is saved as underscore instead of dash.

Dupe of #673

It seems the problem comes from an underscore assigned to the postag in morph.js.
I've created a pull request.


toctree not numbered

I am trying to publish a pre-existing documentation in Confluence. When I build the docs in latex or html, the generated toctree is numbered. Unfortunately, if I build and publish it using the confluence extension, the toc is not numbered.
I have seen in the docs this statement:
"Pending work to validate/improve toctree options caption and numbered."
Does it mean that there are cases where this works?

If so, so, any clue about what I could change in terms of configuration to make it work?
If not, is there any plan to work or WIP related to this? Is it doable?

Thanks! BTW, I really like this extension. Good job!
Versions:

sphinxcontrib-confluencebuilder's extension version: 1.1.0
Python version: 2.7.3
sphinx-build: 1.8.5
sphinx_rtd_theme: 0.1.8

@jjcaballero, unfortunately the numbered option for toctree has yet to be supported by this extension (mainly since it just has not been gotten around to yet). The markup most likely identified pending work since the options were not explicitly tried and it was unknown if Sphinx/docutils already handled management of numbered entries before this extension did its thing.
On the bright side, such a feature should be doable. From a quick look at things, I can see the following notables to consider if one attempts to support this feature:

A document's title is extracted/generated from ConfluenceBuilder._parse_doctree_title before being registered into a tracking state (in turn, used to help generate things like link titles). This logic needs to be assessed to ensure a title value can be assigned a respective numbered prefixed based on its position and the configuration value of the toctree directive. Before attempts are made to just assign a prefix entry to the title, it would be good to confirm that if the numbered prefix values only appear in the rendered toctree elements/title pages or if the prefix also extends to things like internal document links as well.
A chunk of work would need to be added (around) the ConfluenceBuilder.process_tree_structure logic. This extension does various doctree processing to help support document squashing (when in "hierarchy mode"). Implementation needs to be added which the toctree element's numbered attribute is checked to see if a numbered prefix should be applied to a document (and child documents). Changes need to consider:

Applying a prefix on a root document containing a toctree which starts a numbering sequence.
Ensure the configured depths value works so that if a fixed number value is provided, children beyond that depth will not be numbered.
Ensure that no issues arise with the confluence_max_doc_depth option set.

Sphinx's documentation on toctree indicates that a user should "give the toplevel toctree a numbered option" (under "Section numbering"). This gives the impression that this feature is only really used when the root/master document has been assigned a numerical value. While the documentation indicates this, it would be good to confirm if this is true for documents built with html.
When testing, this feature should be tested against scenarios where confluence_remove_title is configured on (default) and off.
Should include a new set of unit tests to verify this feature.

One could say there is a plan to provide this capability to this extension. Usually any Sphinx documented feature (at least for the html builder) aims to be supported by this extension as long as it makes sense for when targeting Confluence. Since you have made this issue, there is a higher chance if it being "scheduled" over other unlisted entries -- but there is no official timeline of when it could be done (days, weeks or months -- whenever free time and will collides). You (and other prospect contributors) are more than welcome in trying to work on this yourself; pull requests are welcome. Either way, I can see this feature being done before the next release. I hope this gives a good idea of the state of things.
(note: this is also somewhat related to #164; although both are different features)

With changes introduced into #264, the numbered option for toctree's should be working on master (and available, next stable release; v1.2).
I assume that this issue was primarily focused on the numbered option so I will mark it as pending-next-release for now and close when the stable release has been made. If I have overlooked another issue, please feel free to mention it.


Update for headsetcontrol v3

Removes deprecated silent cli arg and uses json parsing instead.

If we don't want to go this far, then we should at least hide the deprecated argument text which is spamming my logs atm :D
See https://github.com/Sapd/HeadsetControl/releases/tag/3.0.0 for context

Idk if that's a common theme with other headsets but at least with my Corsaid Void showing the bat% instead of just Chg makes no sense and percentage should probably be hidden because the percentage is (likely) measure via voltage at output, which during charging can easily go up to 99% despite the actual battery being something like 3%.
I just checked and the software in windows does the same - it will never show percentage during charging, only once the charger is unplugged will it report the percentage again.
This worked before where when charging it would not show percentage, only Chg, so that would be regression and likely to be perceived as a bug.


rfctr(chunking): generalize PreChunkBuilder

To implement inter-pre-chunk overlap, we need a context that sees every pre-chunk both before and after it is accumulated (from elements).

We need access to the pre-chunk when it is completed so we can extract the "tail" overlap to be applied to the next chunk.
We need access to the as-yet-unpopulated pre-chunk so we can add the prior tail to it as a prefix.

This "visibility" is split between PreChunkBuilder and the pre-chunker itself, which handles TablePreChunks without the builder.
Move Table element and TablePreChunkformation intoPreChunkBuildersuch that _all_ element types (addingTableelements in particular) pass through it. ThenPreChunkBuilder` becomes the context we require.
The actual overlap harvesting and application will come in a subsequent commit.

Thanks @christinestraub! :)


test

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

noarch: python recipes are required to have a lower bound on the python version. Typically this means putting python >=3.6 in both host and run but you should check upstream for the package's Python compatibility.

For recipe:

Whenever possible python packages should use pip. See https://conda-forge.org/docs/maintainer/adding_pkgs.html#use-pip


[WIP] Replace miqnet calls for network info with LinuxAdmin

Requires https://github.com/ManageIQ/linux_admin/pull/126
https://trello.com/c/rWKh4KQs

https://github.com/ManageIQ/linux_admin/pull/126 merged

Requires gem release and gemfile bump after https://github.com/ManageIQ/linux_admin/pull/126

Marking as WIP while https://github.com/ManageIQ/linux_admin/pull/132 is in progress

Closing in favor of https://github.com/ManageIQ/manageiq/pull/4877


Difference in decoder model from original paper?

I have 2 questions about the decoder model:

Looking at the original TensorFlow implementation and this one, it seems the decoder models are different. The TF version appears to decode to a distribution of observations while this repo uses a standard decoder. Is there a reason you chose to use this decoder, and should that result in any performance differences from the original paper? Or maybe is there something I'm missing that there actually isn't this difference between the versions?
The visual decoder in this repo is a function of both the belief and state and they get concatenated together. In Google's version their decoder is just a function of state though. I know in the paper they formally write the observation model as being a function of both, but the state is already a function of the belief, so maybe the dependence is meant to be implicit? I'm curious if you have insights about which is correct - I find the Google code incomprehensible so it's possible I misinterpret what they're doing.

Thanks for your help.

Optimising the log likelihood of an observation with respect to a Normal distribution with a given mean and a standard deviation of 1 is equivalent to optimising the MSE between the observation and the mean, so they're the same apart from how you interpret them.
I based my code on the paper, referring to the code if I had any issues. I would argue that this is the better way to do it, as otherwise the state would have to retain all the relevant information from the belief, when the belief is the best way to retain all deterministic information.

Thanks for your response, both points make sense.
I'm having some trouble trying to use this on my own dataset where I have a 7-DOF robot arm picking and placing blocks. I trained on a static dataset of "expert" demonstrations and then take the model offline and use ground-truth action sequences to feed through the model and see what the decoded observations look like. I'm finding the motion of the robot arm look quite accurate, but it has a very hard time localizing the objects on the table. The objects just kind of ghostly pop up all over the table until the robot arm is closer to the object, at which point the object becomes clearer. I guess this is because at that point it starts to have a clearer association with the robot's actions, while when the arm is further away from the object it's a part of the scene that was randomized so much in training it doesn't know where to localize them. I thought maybe the encoder/decoder model could be an issue but maybe it's how I'm training the model? I'm not quite sure now.
Did you ever try running on an environment where there is more than just an agent in the scene? That is, there are additionally objects in the scene with positions that are randomized during training and testing?

Pixel-level losses have always been a bit iffy for scenes with small objects. There's a couple of options, from using a higher res input, to a more powerful encoder/decoder, to a different observation model, and possibly even adding the overshooting loss back in.
I have run it on a robot reaching task, which is visually more simple, and didn't have any issues with the target object appearing. Didn't get it to succeed, but I believe the credit assignment for the problem was hard to learn from scratch.

I appreciate your suggestions, seems we were thinking along the same lines as I'm currently training with a beefed up encoder/decoder, and was planning to double the image resolution if that still wasn't effective. I also am ultimately going to be using a more complicated sensory space with at least depth images, and possibly other things like joint/object state and segmentations. I was thinking that may also help if the representation has to be used to jointly predict these various observations that need to be consistent, albeit a more complicated learning problem.


Release @google-cloud/logging v4.5.2

This pull request was generated using releasetool.

What I am not clear on is why https://github.com/googleapis/nodejs-logging/pull/439 is marked as a fix. Isn't it a feature?

Not sure how to look at that one.  @alexander-fenster any thoughts?

@JustinBeckwith @alexander-fenster re: #439, these added headers are required by the spec for all calls which have variable assignment in google.api.http annotation (e.g. post: "v1/{parent=projects/*}/foo") but in most cases, it actually works without those headers. In this sense, we are fixing a bug by making the implementation follow the spec it did not follow before, and it does not change any behavior, so for me callling it a fix: (and not a feat:) is fine.

Thanks @alexander-fenster . That context was not apparent from the PR itself. For future PRs, can we get a better description so that it is easier to determine semverity?

That one is on me.  Right now our tools in this space aren't very great.  There's no way to preserve context from a change in the generator to the changes in the underlying library.  As a result, we often have to guess based on the changed output what happened.  We are trying to find ways to make this better, but it's unlikely to happen until we transition to the micro-generator.

Release is at https://github.com/googleapis/nodejs-logging/releases/tag/v4.5.2

The release build has started, the log can be viewed here. :sunflower:

:egg: You hatched a release! The release build finished successfully! :purple_heart:


CRYPTO_THREAD_write_lock hang on 3.0.1

We keep running into a hang situation in OpenSSL 3.0.1 which manifests like the following:
(gdb) bt
#0  futex_abstimed_wait (private=<optimized out>, abstime=0x0, clockid=0, expected=3, futex_word=0x55ba31fd573c)     at ../sysdeps/nptl/futex-internal.h:284
#1  __pthread_rwlock_wrlock_full (abstime=0x0, clockid=0, rwlock=0x55ba31fd5730) at pthread_rwlock_common.c:731
#2  __GI___pthread_rwlock_wrlock (rwlock=0x55ba31fd5730) at pthread_rwlock_wrlock.c:27
#3  0x000055ba306fb179 in CRYPTO_THREAD_write_lock ()
#4  0x000055ba3070f2dc in ossl_method_store_cache_set ()
#5  0x000055ba306d1216 in inner_evp_generic_fetch.constprop ()
#6  0x000055ba306d14a2 in evp_generic_fetch ()
#7  0x000055ba306c729a in EVP_MD_fetch ()
#8  0x000055ba306c7b18 in evp_md_init_internal ()
#9  0x000055ba306ea36d in HMAC_Init_ex ()
We're seeing the lock itself in this state which is unclear on exactly how to interpret:
(gdb) p *rwlock
$2 = {__data = {__readers = 19, __writers = 0, __wrphase_futex = 3, __writers_futex = 3, __pad3 = 0, __pad4 = 0,     __cur_writer = 557540, __shared = 0, __rwelision = 0 '\000', __pad1 = "\000\000\000\000\000\000", __pad2 = 0,     __flags = 0},
But following that __cur_writer thread we find this stack in OPENSSL_LH_doall_arg:
(gdb) bt
#0  0x000055ba306eb1b4 in OPENSSL_LH_doall_arg ()
#1  0x000055ba3084cee9 in ossl_sa_doall_arg ()
#2  0x000055ba3070f451 in ossl_method_store_cache_set ()
#3  0x000055ba306d1216 in inner_evp_generic_fetch.constprop ()
#4  0x000055ba306d14a2 in evp_generic_fetch ()
#5  0x000055ba306cf6ea in EVP_CIPHER_fetch ()
#6  0x000055ba306d01b0 in evp_cipher_init_internal ()
#7  0x000055ba306d05cb in EVP_CipherInit_ex ()
As expected, there are other threads awaiting the read lock:
(gdb) bt
#0  futex_abstimed_wait (private=<optimized out>, abstime=0x0, clockid=0, expected=3, futex_word=<optimized out>)     at ../sysdeps/nptl/futex-internal.h:284
#1  __pthread_rwlock_rdlock_full (abstime=0x0, clockid=0, rwlock=0x55ba31fd5730) at pthread_rwlock_common.c:460
#2  __GI___pthread_rwlock_rdlock (rwlock=0x55ba31fd5730) at pthread_rwlock_rdlock.c:27
#3  0x000055ba306fb159 in CRYPTO_THREAD_read_lock ()
#4  0x000055ba3070f1b4 in ossl_method_store_cache_get ()
#5  0x000055ba306d10fc in inner_evp_generic_fetch.constprop ()
#6  0x000055ba306d14a2 in evp_generic_fetch ()
#7  0x000055ba306c729a in EVP_MD_fetch ()
#8  0x000055ba306c7b18 in evp_md_init_internal ()
#9  0x000055ba306d235c in EVP_BytesToKey ()
And in this thread also in EVP_BytesToKey is awaiting the write lock:
(gdb) bt
#0  futex_abstimed_wait (private=<optimized out>, abstime=0x0, clockid=0, expected=3, futex_word=0x55ba31fd573c) at ../sysdeps/nptl/futex-internal.h:284
#1  __pthread_rwlock_wrlock_full (abstime=0x0, clockid=0, rwlock=0x55ba31fd5730) at pthread_rwlock_common.c:731
#2  __GI___pthread_rwlock_wrlock (rwlock=0x55ba31fd5730) at pthread_rwlock_wrlock.c:27
#3  0x000055ba306fb179 in CRYPTO_THREAD_write_lock ()
#4  0x000055ba3070f2dc in ossl_method_store_cache_set ()
#5  0x000055ba306d1216 in inner_evp_generic_fetch.constprop ()
#6  0x000055ba306d14a2 in evp_generic_fetch ()
#7  0x000055ba306c729a in EVP_MD_fetch ()
#8  0x000055ba306c7b18 in evp_md_init_internal ()
#9  0x000055ba306d235c in EVP_BytesToKey ()
Other threads awaiting the lock:
(gdb) bt
#0  futex_abstimed_wait (private=<optimized out>, abstime=0x0, clockid=0, expected=3, futex_word=0x55ba31fd573c)     at ../sysdeps/nptl/futex-internal.h:284
#1  __pthread_rwlock_wrlock_full (abstime=0x0, clockid=0, rwlock=0x55ba31fd5730) at pthread_rwlock_common.c:731
#2  __GI___pthread_rwlock_wrlock (rwlock=0x55ba31fd5730) at pthread_rwlock_wrlock.c:27
#3  0x000055ba306fb179 in CRYPTO_THREAD_write_lock ()
#4  0x000055ba3070e9fb in ossl_method_store_add ()
#5  0x000055ba306d0ca9 in put_evp_method_in_store ()
#6  0x000055ba306ec4c5 in ossl_method_construct_this ()
#7  0x000055ba306ec2ee in algorithm_do_this ()
#8  0x000055ba306fa497 in ossl_provider_doall_activated ()
#9  0x000055ba306ec3d9 in ossl_algorithm_do_all ()
#10 0x000055ba306ec6c4 in ossl_method_construct ()
#11 0x000055ba306d11b4 in inner_evp_generic_fetch.constprop ()
#12 0x000055ba306d14a2 in evp_generic_fetch ()
#13 0x000055ba306cf6ea in EVP_CIPHER_fetch ()
#14 0x000055ba3062e6ca in ssl_evp_cipher_fetch ()
#15 0x000055ba30623c92 in ssl_load_ciphers ()
#16 0x000055ba3062fa83 in SSL_CTX_new_ex ()
(gdb) bt
#0  futex_abstimed_wait (private=<optimized out>, abstime=0x0, clockid=0, expected=3, futex_word=<optimized out>) at ../sysdeps/nptl/futex-internal.h:284
#1  __pthread_rwlock_rdlock_full (abstime=0x0, clockid=0, rwlock=0x55ba31fd5730) at pthread_rwlock_common.c:460
#2  __GI___pthread_rwlock_rdlock (rwlock=0x55ba31fd5730) at pthread_rwlock_rdlock.c:27
#3  0x000055ba306fb159 in CRYPTO_THREAD_read_lock ()
#4  0x000055ba3070f1b4 in ossl_method_store_cache_get ()
#5  0x000055ba306d10fc in inner_evp_generic_fetch.constprop ()
#6  0x000055ba306d14a2 in evp_generic_fetch ()
#7  0x000055ba306d8e78 in EVP_KEYMGMT_fetch ()
#8  0x000055ba306e36c0 in int_ctx_new ()
#9  0x000055ba30636b44 in ssl_setup_sig_algs ()
#10 0x000055ba3062fa93 in SSL_CTX_new_ex ()
We're unclear on what to do to keep this internal locking mechanism from entering this state... any help/guidance is appreciated.

Could you please test with the latest code from the openssl-3.0 branch? There were some locking fixes since 3.0.1 and other related changes.

Thanks for the comment - were these locking fixes specific to the 3.0 branch or did they also apply to the 1.1.1 branch?  We switched to the 3.0 branch around the same time we started seeing these issues but cannot definitively pinpoint it.

@mpietras Does the issue still exist in the latest openssl-3.0 branch? I tried to simulate the issue with a code that calls functions from backtraces in several threads and I was not able to achieve the lock hang.

We're currently running with 3.0.3 and have not hit this issue since updating so things are looking positive.

Let's close this issue then. Please open a new issue if you still encounter something with current release.


support paysafecard type definition  in web component & typescript

Is your feature request related to a problem? Please describe.
I'm always frustrated when use @adyen/adyen-web and typescript with web-component

Describe the solution you'd like

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Hi  @Fog3211 ,
PaySafe is not defined on its own folder/file because it is a Redirect component. Its type definition is based on the Redirect.
Regarding the Typescript types, we are working on the next major release which will improve the types. It should be released early next year.  Cheers


DEP: Clean up spent deprecations in spatial.distance

What does this implement/fix?

Removes old_cosine metric, deprecated in #7043 (SciPy 0.17)
Removes _filter_deprecated_kwargs, also deprecated in #7043 (SciPy 0.17)
Removes *args from pdist/cdist which was deprecated in #7629 (SciPy 1.0)

These have all been deprecated for >= 6 releases.

Thanks @peterbell10


Quit printing exception backtrace twice

This makes it so that exception backtrace is printed to stdout only once.  More info inline.
@os97673 @grosser

Actually, this fix is not completely right, changing soon

It would be very helpful if you'd provide output you have before and after the changes, so it would be obvious what problem you are trying to address.

@os97673
For sure.
Before:
 test_both_block_settings_and_block_content_tags_must_be_present#ThemeBlockAssetTest (6.95s)
AssetCloud::InvalidBucketError:         AssetCloud::InvalidBucketError: No such namespace: blocks_new/foo.liquid
            /home/vagrant/src/ruby/shopify/vendor/bundle/gems/asset_cloud-2.2.0/lib/asset_cloud/buckets/invalid_bucket.rb:17:in `write'
            /home/vagrant/src/ruby/shopify/vendor/bundle/gems/asset_cloud-2.2.0/lib/asset_cloud/base.rb:147:in `write'
            /home/vagrant/src/ruby/shopify/vendor/bundle/gems/asset_cloud-2.2.0/lib/asset_cloud/callbacks.rb:44:in `write_with_callbacks'
            /home/vagrant/src/ruby/shopify/vendor/bundle/gems/asset_cloud-2.2.0/lib/asset_cloud/asset.rb:116:in `store'
            /home/vagrant/src/ruby/shopify/vendor/bundle/gems/asset_cloud-2.2.0/lib/asset_cloud/callbacks.rb:44:in `store_with_callbacks'
            /home/vagrant/src/ruby/shopify/vendor/bundle/gems/asset_cloud-2.2.0/lib/asset_cloud/validations.rb:21:in `store_with_validation'
            test/unit/asset_cloud/theme_block_asset_test.rb:39:in `block in <class:ThemeBlockAssetTest>'
        /home/vagrant/src/ruby/shopify/vendor/bundle/gems/asset_cloud-2.2.0/lib/asset_cloud/buckets/invalid_bucket.rb:17:in `write'
        /home/vagrant/src/ruby/shopify/vendor/bundle/gems/asset_cloud-2.2.0/lib/asset_cloud/base.rb:147:in `write'
        /home/vagrant/src/ruby/shopify/vendor/bundle/gems/asset_cloud-2.2.0/lib/asset_cloud/callbacks.rb:44:in `write_with_callbacks'
        /home/vagrant/src/ruby/shopify/vendor/bundle/gems/asset_cloud-2.2.0/lib/asset_cloud/asset.rb:116:in `store'
        /home/vagrant/src/ruby/shopify/vendor/bundle/gems/asset_cloud-2.2.0/lib/asset_cloud/callbacks.rb:44:in `store_with_callbacks'
        /home/vagrant/src/ruby/shopify/vendor/bundle/gems/asset_cloud-2.2.0/lib/asset_cloud/validations.rb:21:in `store_with_validation'
        test/unit/asset_cloud/theme_block_asset_test.rb:39:in `block in <class:ThemeBlockAssetTest>'

After:
 test_both_block_settings_and_block_content_tags_must_be_present#ThemeBlockAssetTest (5.73s)
        AssetCloud::InvalidBucketError: No such namespace: blocks_new/foo.liquid
            /home/vagrant/src/ruby/shopify/vendor/bundle/gems/asset_cloud-2.2.0/lib/asset_cloud/buckets/invalid_bucket.rb:17:in `write'
            /home/vagrant/src/ruby/shopify/vendor/bundle/gems/asset_cloud-2.2.0/lib/asset_cloud/base.rb:147:in `write'
            /home/vagrant/src/ruby/shopify/vendor/bundle/gems/asset_cloud-2.2.0/lib/asset_cloud/callbacks.rb:44:in `write_with_callbacks'
            /home/vagrant/src/ruby/shopify/vendor/bundle/gems/asset_cloud-2.2.0/lib/asset_cloud/asset.rb:116:in `store'
            /home/vagrant/src/ruby/shopify/vendor/bundle/gems/asset_cloud-2.2.0/lib/asset_cloud/callbacks.rb:44:in `store_with_callbacks'
            /home/vagrant/src/ruby/shopify/vendor/bundle/gems/asset_cloud-2.2.0/lib/asset_cloud/validations.rb:21:in `store_with_validation'
            test/unit/asset_cloud/theme_block_asset_test.rb:39:in `block in <class:ThemeBlockAssetTest>'

@os97673 let me know if you need more info

Well, the current version doesn't use name parameter :(

@gauravmc I agree with you, there's way too much stuff being reported right now when MiniTest::UnexpectedError is raised.
@os97673 you are also right, name is not being used in @gauravmc last implementation.
Here's a better implementation which satisfies the API requirements and the need to remove the clutter.
        print "#{e.exception.class.to_s}: " if name
        e.message.each_line { |line| print_with_info_padding(line) }

        # When e is a Minitest::UnexpectedError, the filtered backtrace is already part of the message printed out
        # by the previous line. In that case, and that case only, skip the backtrace output.
        unless e.is_a?(MiniTest::UnexpectedError)
          trace = filter_backtrace(e.backtrace)
          trace.each { |line| print_with_info_padding(line) }
        end

I tried to understand how the reporter got into such a state. By looking at the original version, which we can see in https://github.com/kern/minitest-reporters/commit/3125026c96efe55590bee02cfb14fb35e0550a80. I think perhaps it was made for MiniTest (pre-5), which had a different message?

Here's a better implementation which satisfies the API requirements and the need to remove the clutter.

@francoisjacques your implementation looks ok for me, do you want to create a PR? ;)

I tried to understand how the reporter got into such a state. By looking at the original version, which we can see in 3125026. I think perhaps it was made for MiniTest (pre-5), which had a different message?

agree, most likely it is pre-5 code which is not optimal now.

New pull request opened at https://github.com/kern/minitest-reporters/pull/165

@francoisjacques just got around to looking at the comments, thanks for taking over


doc: update README badges

Add a badge for crates.io and switch to shields when possible (still waiting for docs.rs).

As always thank you!
P.S. Sorry it may take a while to review the rest of your PRs.


Fix land sound bug

Issue:
Does not have land sound
https://user-images.githubusercontent.com/60634884/181633118-29a3e10d-1d4d-4ccc-bdf6-5ec1e4be5676.mp4
Would play the land sound when doing double jump
https://user-images.githubusercontent.com/60634884/181633218-1050a734-bc65-4b97-aba6-a0a61df48166.mp4
Result:
https://user-images.githubusercontent.com/60634884/181633374-56c7f41a-886b-4bab-b52a-2a623cd15d2a.mp4

Works fine.

https://github.com/webaverse/app/pull/3542


Consider adding support for multiple for different web beacons

Lots of companies have some kind of simple web beacon that lets us know if we're online or not. Make a single Macro that checks google, apple, mozilla, etc. beacons.

v15 has it


Discrepancies on what is being sold

https://gyazo.com/103d2fe3ec55bd8ae5d8e641363e5b2a
I believe this in itself can be a huge issue, perhaps 1 line should be kept to make sure the correct item is being sold as this is a potential source to scam players and can leave this plugin unviable for servers with larger player counts.

This is a matter of opinion; The names of items, especially modded items, are usually wrong - the data usually used in these kind of plugins are not the names you see on the item names. Plus, there is the added problem of specialised items and amounts, and the fact that you can have more than one type of item in a chest when selling things.
If you are worried about players being scammed, just make sure your players are aware to left click the sign before using right click to buy - it shows what is in it (although using the crappy names I mentioned before).

My complaint stems from the fact anyone can write anything to say something else will be sold.
It generally is also a good idea to assume ignorance from the perspective of players
Also in terms of modded items it would be assumed they take the name such as pixelmon:masterball or it can remove the source and place the name after
Shop plugins in spigot generally handle stuff in such a manner and if need be add a #nbt type of thing
In which case a second sign may be added for specification. It also is much less likely to be a scam if an item being sold holds NBT data or is enchanted

If you put your mouse over the item in chat you should be able to see the exact type.
As yepi said, it can be hard to get what will eventually be displayed. Using this method happen to be the most accurate.
If you want, you can alter the language file to add an extra 'mouse over item for details'

Closing this issue as for now as I think hovering over the item name in chat for more details is enough.
Feel free to re-open if you want to discuss it


SPIKE - Quick assumption check that GitHub actions better than AWS pipeline

Describe the issue
We want to make sure we are choosing the pipeline with the least amount of vendor lock-in and the best capabilities for our future dev team's needs.
Which Sprint Priority is this issue related to?
Milestone #2
Additional context

We have working GitHub Action code over in our bcdevops/managed-ocp repo.
Ryan J has offered us workshop on AWS pipelines

Definition of done

A short minimally technical powerpoint slide on which pipeline is best for our future clients (using the current Demo App as a test case)

For reference: https://www.terraform.io/docs/github-actions/setup-terraform.html


What happened to com.gargoylesoftware.htmlunit.html.InputElementFactory?

This class seems to have disappeared in 2.37.0, but I don't see any information in the change history as to why.  I haven't even found the commit that removed it.  Was this an intentional change?

Nevermind... my poor log searching ability... I found commit that references use of DefaultElementFactory for input items too.

Sorry for not mention this in the changes, but from my point of view these factories are part of the internal API.
There is still the plan to (optionally) replace the neko parser with a different one - that is more or less the reason for doing the refactoring in that area.

So I tripped over this change when I was trying to upgrade Webtest to use latest HtmlUnit.  An old application I know, but I still like it because of it’s Ant/XML driven test cases… which seems easier to write for QA teams composed of non-developers.  I’ll dig around and see if I can figure out how to avoid this internal API call.
Thanks for the response!
On Jul 9, 2020, at 5:23 AM, RBRi <notifications<EMAIL_ADDRESS>wrote:
Sorry for not mention this in the changes, but from my point of view these factories are part of the internal API.
There is still the plan to (optionally) replace the neko parser with a different one - that is more or less the reason for doing the refactoring in that area.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://github.com/HtmlUnit/htmlunit/issues/190#issuecomment-656016858, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AESFRLLSLSGVFC3WCRPHQMDR2WEC3ANCNFSM4OU3ESFA.


Auto-publish to NuGet

Is there a reason we're currently leaving changes in "unreleased" state at all? (For example, https://github.com/G-Research/fsharp-analyzers/actions/runs/7726152791/job/21061944118 on commit 10808cb33f001365cc6c189a8099f164810cc3e9 didn't release a new version because it wanted to publish to the same 0.8.0 version that had already been published earlier.) The "underscore in named placeholders" bugfix isn't strictly a prerequisite for me testing the analysers on my team's monorepo, but it's currently quite a noisy false positive.

There is no good reason in this particular case.
We will ship a new version once @dawedawe has updated to the latest analyzer SDK.
Sorry, for not shipping this earlier.

Yes, sorry. I didn't realize that this was anoying to you and a new release would have made sense.


Unable to change HVAC mode (dry mode only)

Since the last update of OS and supervisor (I think, not sure if there has been some other updates) I am unable to set de dry mode on the HVAC. It used to work perfectly. The rest of the modes, temperature and fan work correctly.
If I set the dry mode through the smart life/tuya app, it updates to the dry mode on HA.
The log detail:
Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/commands.py:283
integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 9:10:23 AM (5 occurrences)
Last logged: 9:12:54 AM
[547490217648] Unable to change hvac mode

Hi, I haven't encountered this problem.
Are you using the latest released version (2024.8.3)?
Does the problem always occur?
Are there more details in the Home Assistant logs to understand the problem?
Thanks

Hello in my Home Assistant server this integration not working  - Core 2024.8.3 my config is:
tuya_smart_ir_ac:
access_id: "nxxxxxxxxxxxxxxxxxxxxxxxxxx"
access_secret: "6xxxxxxxxxxxxxxxxxxxxxxxxxxxx"
country: "EU"
Help me!!! Grazie Enzo

Enzo, I wasn't in the latest version. I just updated and it is still happening. I don't have any log info. It happens to the 3 IR devides that I have. Is there any way I can help you understanding the problem?Thanks --Javier EstebanEl 27 ago 2024, a las 11:11, PakyITA @.***> escribió:
Hello in my Home Assistant server this integration not working  - Core 2024.8.3 my config is:
tuya_smart_ir_ac:
access_id: "nxxxxxxxxxxxxxxxxxxxxxxxxxx"
access_secret: "6xxxxxxxxxxxxxxxxxxxxxxxxxxxx"
country: "EU"
Help me!!! Grazie Enzo
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

My telegram is @PakyITA create a telegram group please

@geced It's very strange because I fixed this bug in an old version of the integration.
You can try to enable debug logs by adding these lines in your configuration.yaml file
logger:
  logs:
    custom_components.tuya_smart_ir_ac: debug

You need to restart HA and see if this way there are more details in the logs.
Thanks

@EnzoD86 why you delete my messages?

@paky888 It is important to open a different issue for your request to avoid confusion.
In any case I created the telegram group and added you.
Thanks

This is what I get now:
Logger: custom_components.tuya_smart_ir_ac
Source: custom_components/tuya_smart_ir_ac/api.py:62
integration: Tuya Smart IR AC (documentation
https://github.com/EnzoD86/tuya-smart-ir-ac, issues
https://github.com/EnzoD86/tuya-smart-ir-ac/issues)
First occurred: 4:09:59 PM (1 occurrences)
Last logged: 4:09:59 PM
Error sending multiple command to climate bf5f45a094f1096905ilp7: {'url':
'/v2.0/infrareds/bfb90d9ab7cb0fa414ysza/air-conditioners/bf5f45a094f1096905ilp7/scenes/command',
'request': {'power': '1', 'mode': '4', 'temp': '25.0', 'wind': '0'},
'response': {'code': 30100, 'msg': '没有查询到码库', 'success': False, 't':
1724767799369, 'tid': '0b6eab94647e11ef9a8c4604aebef837'}}
El mar, 27 ago 2024 a las 11:46, EnzoD86 @.***>)
escribió:

@paky888 https://github.com/paky888 It is important to open a different
issue for your request to avoid confusion.
In any case I created the telegram group and added you.
Thanks
—
Reply to this email directly, view it on GitHub
https://github.com/EnzoD86/tuya-smart-ir-ac/issues/14#issuecomment-2312057933,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQTLL7672T2DYMKTSPO5JETZTRDJBAVCNFSM6AAAAABNFPL6L2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJSGA2TOOJTGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Javier Esteban Zarza

Sorry about the grey color.
Some more info:
2024-08-27 16:12:59.887 DEBUG (MainThread)
[custom_components.tuya_smart_ir_ac] API fetch_all_data url:
/v1.0/cloud/rc/infrared/ac/status/batch?device_ids=bf9e30bb9b7el,bf5f45a096905*,bf9a12a115cdcz
2024-08-27 16:13:00.039 DEBUG (MainThread)
[custom_components.tuya_smart_ir_ac] API fetch_all_data response:
{'result': [{'devId': 'bf9e30bb9b7el', 'fan': '0', 'mode': '0',
'powerOpen': True, 'swing': 'false', 'temp': '26'}, {'devId':
'bf5f45a096905', 'fan': '0', 'mode': '0', 'powerOpen': True,
'swing': 'false', 'temp': '25'}, {'devId': 'bf9a12a1*15cdcz', 'fan':
'2', 'mode': '4', 'powerOpen': True, 'swing': 'false', 'temp': '26'}],
'success': True, 't':<PHONE_NUMBER>011, 'tid':
'**************883136d89ae34f8e'}
2024-08-27 16:13:00.039 DEBUG (MainThread)
[custom_components.tuya_smart_ir_ac] Finished fetching tuya_smart_ir_ac
data in 0.152 seconds (success: True)
El mar, 27 ago 2024 a las 16:11, Javier Esteban @.***>)
escribió:

This is what I get now:
Logger: custom_components.tuya_smart_ir_ac
Source: custom_components/tuya_smart_ir_ac/api.py:62
integration: Tuya Smart IR AC (documentation
https://github.com/EnzoD86/tuya-smart-ir-ac, issues
https://github.com/EnzoD86/tuya-smart-ir-ac/issues)
First occurred: 4:09:59 PM (1 occurrences)
Last logged: 4:09:59 PM
Error sending multiple command to climate bf5f45a094f1096905ilp7: {'url':
'/v2.0/infrareds/bfb90d9ab7cb0fa414ysza/air-conditioners/bf5f45a094f1096905ilp7/scenes/command',
'request': {'power': '1', 'mode': '4', 'temp': '25.0', 'wind': '0'},
'response': {'code': 30100, 'msg': '没有查询到码库', 'success': False, 't':
1724767799369, 'tid': '0b6eab94647e11ef9a8c4604aebef837'}}
El mar, 27 ago 2024 a las 11:46, EnzoD86 @.***>)
escribió:

@paky888 https://github.com/paky888 It is important to open a
different issue for your request to avoid confusion.
In any case I created the telegram group and added you.
Thanks
—
Reply to this email directly, view it on GitHub
https://github.com/EnzoD86/tuya-smart-ir-ac/issues/14#issuecomment-2312057933,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQTLL7672T2DYMKTSPO5JETZTRDJBAVCNFSM6AAAAABNFPL6L2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJSGA2TOOJTGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Javier Esteban Zarza

--
Javier Esteban Zarza

For the first time is set to 16ºC. --Javier EstebanEl 27 ago 2024, a las 16:24, EnzoD86 @.***> escribió:
Thanks for the logs, I got an idea of the reason for this error.
When you set the dry mode from smart life, what temperature is set?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

ok, as I thought.
Currently when the HVAC mode is changed, the integration keeps the same set temperature (even if it is not normally used for the dry or fan mode).
Most likely your air conditioner doesn't like this.
It needs the minimum temperature to be set to change to dry mode.
In my case this problem does not occur for the temperature, but only for the fan.
I had in fact corrected this problem by resetting the fan speed when the HVAC mode is changed.
Give me a few days to try to release a fix on this.
We'll update as soon as I have something ready.
Thanks for reporting the bug!

I understand. Great news that can be fixed!Thanks for the support!PS: it would be great to have a solution like this one for the covers that are not supported by HA--Javier EstebanEl 27 ago 2024, a las 16:40, EnzoD86 @.***> escribió:
ok, as I thought.
Currently when the HVAC mode is changed, the integration keeps the same set temperature (even if it is not normally used for the dry or fan mode).
Most likely your air conditioner doesn't like this.
It needs the minimum temperature to be set to change to dry mode.
In my case this problem does not occur for the temperature, but only for the fan.
I had in fact corrected this problem by resetting the fan speed when the HVAC mode is changed.
Give me a few days to try to release a fix on this.
We'll update as soon as I have something ready.
Thanks for reporting the bug!
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

At least we try to fix it!
Just out of curiosity, what brand is the air conditioner?

It is kosner, but the real hardware brand is Gree, at least for the remote control. --Javier EstebanEl 27 ago 2024, a las 16:56, EnzoD86 @.***> escribió:
At least we try to fix it!
Just out of curiosity, what brand is the air conditioner?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

One more thing that may help. If I change to dry in the ac wall panel, it keeps the temp I had in this mode. It does not go to 16°C. --Javier EstebanEl 27 ago 2024, a las 18:24, Javier Esteban @.> escribió:It is kosner, but the real hardware brand is Gree, at least for the remote control. --Javier EstebanEl 27 ago 2024, a las 16:56, EnzoD86 @.> escribió:
At least we try to fix it!
Just out of curiosity, what brand is the air conditioner?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

Could you tell me if the problem occurs even if you change to fan only mode?
Thank you

It only occurs with dry mode. Fan only is ok. Fan mode does not take into account the temperature, while dry mode does. It does not only extract humidity, it tries to achirve the  temperature that has been set. --Javier EstebanEl 28 ago 2024, a las 1:15, EnzoD86 @.***> escribió:
Could you tell me if the problem occurs even if you change to fan only mode?
Thank you
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

If I set 16°C before I change to dry mode, it works fine. --Javier EstebanEl 28 ago 2024, a las 10:04, Javier Esteban @.> escribió:It only occurs with dry mode. Fan only is ok. Fan mode does not take into account the temperature, while dry mode does. It does not only extract humidity, it tries to achirve the  temperature that has been set. <Vídeo.mov>--Javier EstebanEl 28 ago 2024, a las 1:15, EnzoD86 @.> escribió:
Could you tell me if the problem occurs even if you change to fan only mode?
Thank you
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

Hi, I'm trying to fix the problem, I need you to try the beta version I released to see if the problem is solved in your case.
You can find it here:
https://github.com/EnzoD86/tuya-smart-ir-ac/releases/tag/2024.8.4-beta
After installing it, you need to update your air conditioning configuration; you will find a new flag called "Set minimum temperature in dry mode", try to activate it and let me know if anything changes.
Thanks

I've the same issue with "official" and "beta" release

hi @SabatoArdolino,
it seems that there are 2 different problems depending on the air conditioner models; I released a "beta2" version where you can also set the fan to minimum when switching to dry mode. Let me know if this change fixes the problem.
You can find it here:
https://github.com/EnzoD86/tuya-smart-ir-ac/releases/tag/2024.8.4-beta2
Experiment a bit by activating both flags or just the second.
Thank you

@EnzoD86 I've the same issue with beta2. I want to share that with the "old / cloned" repository all work fine. Unfortunately the old repository is not available / compatible with new version of Home Assistant

@SabatoArdolino do you have any logs to share to better identify the problem?

Sorry... this method works well but, for me, since I use the dry mode more than the cold one, it is more inconvenient. Is there a way to "set" different temperatures instead of the minimum one?

@SabatoArdolino the flag sets the minimum temperature when you switch to dry mode, but you should be able to increase the temperature manually.
Unfortunately this is how tuya works, in fact even from the SmartLife application when you change to dry mode, it should have the same behavior.
Then you could create some automations in home assistant that allow you to automatically set a temperature.

In both betas this id happening.--Javier EstebanEl 30 ago 2024, a las 8:43, EnzoD86 @.***> escribió:
@SabatoArdolino the flag sets the minimum temperature when you switch to dry mode, but you should be able to increase the temperature manually.
Unfortunately this is how tuya works, in fact even from the SmartLife application when you change to dry mode, it should have the same behavior.
Then you could create some automations in home assistant that allow you to automatically set a temperature.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

@geced I don't understand what you wrote

Sorry Enzo. I had a problem setting the minimum and maximum temp but now
it's working fine with beta2. I also need the low fan activated.
El vie, 30 ago 2024 a las 10:43, EnzoD86 @.***>)
escribió:

@geced https://github.com/geced I don't understand what you wrote
—
Reply to this email directly, view it on GitHub
https://github.com/EnzoD86/tuya-smart-ir-ac/issues/14#issuecomment-2320514719,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQTLL77LCK3X5ULIBW6FC43ZUAWDRAVCNFSM6AAAAABNFPL6L2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRQGUYTINZRHE
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Javier Esteban Zarza

@geced ok so the problem for you has been solved!
I can make the beta2 release official

Thank you!!--Javier EstebanEl 30 ago 2024, a las 12:03, EnzoD86 @.***> escribió:
@geced ok so the problem for you has been solved!
I can make the beta2 release official
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>


Feat:Enhanced Product Filtering Options

Describe the feature
I would like to request the addition of enhanced product filtering options on the Flipkart Clone project. Currently, users can filter products by category, but additional filters such as price range, brand, customer ratings, and discount offers would significantly improve the user experience.
Describe the solution you'd like
The product filtering system should be enhanced to include:

Price Range Slider: Allow users to select a minimum and maximum price range.
Brand Filter: Users can select one or multiple brands to filter products.
Customer Ratings: Filter products based on customer ratings (e.g., 4 stars and above).
Discount Offers: Option to filter products that are on discount.

Describe alternatives you've considered
As an alternative, consider implementing a search filter sidebar where users can dynamically add or remove filters. Another option is to provide preset filters for common search criteria, such as "Best Deals" or "Top Rated Products".
Add ScreenShots
Brand filter checkboxes
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

can you add labeles such as gssoc'24 , level 2


Fixed Pandas .loc notation and added gene_names parameter to violin

With this PR, I tried to fix issue https://github.com/theislab/scanpy/issues/140. Needs to be tested still.
Additionally, I found it useful to provide to scanpy directly the gene names when plotting violins. Use case: you have a different algorithm that is not implemented in scanpy for differential gene expression, and you want to plot its results with scanpy.
Feel free to reject if there's a better way to do it currently in scanpy. I didn't find it though.

Makes sense! Thank you!


custom_payload is "persisted' (or per se kept) between 2 requests

if I start to have conditional things I want to sho on my payload based on the controller "type", or how it's shaped, there is a concerning issue: the data that isn't "overwritten" is kept between 2 requests
Example:
code:
# initializers/lograge.rb
Rails.application.configure do
  config.lograge.custom_payload do |controller|
  custom_payload = {}

  custom_payload[:test] = 123
  custom_payload[:respond_to_current_user] = controller.respond_to?(:current_user)

  if controller.respond_to?(:current_user)
    custom_payload[:user_id] = controller.current_user&.id
  end

  custom_payload
end

let's now have 2 consecutive calls, one to a controller that define a current user, and another that has no current user
the first one will have
test: 123
respond_to_current_user: true
user_id: 456

And the second one
test: 123
respond_to_current_user: false
user_id: 456 # oppsie

might be because of that here
https://github.com/roidrage/lograge/blob/c737a13779fef5c2b6050ce9356fd7acb86a8905/lib/lograge/log_subscribers/base.rb#L73
        options.merge event.payload[:custom_payload] || {}
what we might want may be
        options.deep_dup.merge event.payload[:custom_payload] || {}
Otherwise we effectively "definitely" (until further re-write) merge the custom payload to the @@custom_options, which is not what we want

So. Definitly not the issue. .merge doesn't commit anything (.merge! does)
Not sure if it (and so how) it's specific to our own config or not, but when I try to fork and build failing example (in order to send the part that is supposed to fix it), can't reproduce

more context: Looks like this happens when we pop threads into a request. Somehow - the child threads, or main thread hanging while child threads resolve - that pick up next query have polluted logs

So the issue was threading + usage of OGAI with_fields method wrapped in an "around_action"
Issue was it affects the shared Logger
https://github.com/tilfin/ougai/issues/107


Containers fallback to Google DNS <IP_ADDRESS> after host reboots, breaks DNS for local domains

Description
Using docker on hosts with a dedicated DNS server specified in hosts /etc/resolv.conf (e.g. <IP_ADDRESS>) and containers with restart=always policy results in containers falling back to Google Public DNS (<IP_ADDRESS>) instead of hosts DNS (<IP_ADDRESS>) after host reboots.
Might be a problem regarding DNS server not yet available/reachable when docker starts the container due to hosts network (DHCP, ...) not being up yet.
Steps to reproduce the issue:
% cat /etc/resolv.conf
nameserver <IP_ADDRESS>
search lan

% dig +noall +answer fileserver.lan @<IP_ADDRESS>
fileserver.lan.		0	IN	A	<IP_ADDRESS>

% docker run --restart always --name dnstest --detach php:7-fpm
63e092c423cb4153c96029b449f0645fa61775308c5427378f87cd1518c1653a

% docker exec -it dnstest ping -c 1 fileserver.lan
PING fileserver.lan (<IP_ADDRESS>): 56 data bytes
64 bytes from <IP_ADDRESS>: icmp_seq=0 ttl=62 time=0.816 ms

% reboot

% docker exec -it dnstest ping -c 1 fileserver.lan
ping: unknown host

% tcpdump -i eth0 -p -n -t -s 0 'udp and port 53'
IP <IP_ADDRESS>.41292 > <IP_ADDRESS>.53: 22988+ A? fileserver.lan. (32)
IP <IP_ADDRESS>.53 > <IP_ADDRESS>.41292: 22988 NXDomain 0/1/0 (107)

% sudo service docker restart

% docker exec -it dnstest ping -c 1 fileserver.lan
PING fileserver.lan (<IP_ADDRESS>): 56 data bytes
64 bytes from <IP_ADDRESS>: icmp_seq=0 ttl=62 time=0.913 ms

% tcpdump -i eth0 -p -n -t -s 0 'udp and port 53'
IP <IP_ADDRESS>.53812 > <IP_ADDRESS>.53: 29159+ A? fileserver.lan. (32)
IP <IP_ADDRESS>.53 > <IP_ADDRESS>.53812: 29159* 1/0/0 A <IP_ADDRESS> (48)

Describe the results you received:
Container is using <IP_ADDRESS> as DNS resolver instead of the one specified in hosts /etc/resolv.conf (<IP_ADDRESS>) after reboot of the host.
Describe the results you expected:
Container is using DNS resolver specified in hosts /etc/resolv.conf - even when that DNS server might not be reachable at first due to hosts network not being up yet.


Member variables moved to initialization list

Code style changes like this one should be discussed in a proposal beforehand, so we can coordinate in making those all in one go.

And in this case this would have been rejected. Initializations should be moved to the header declarations instead of the constructor.


Suggestion: license in, license out

I got this catchphrase from a collegue at Aalto.  It originally applied to copyright, but the overall idea applies, too.  I think we can structure somewhat around the concept of "you want to use what others have done, and you want others to be able to use from you".  They are symmetric and we perhaps go by topic, talk about what you are allowed to use, and then how you can make your stuff usable by others.  Quick mock-up attached.
I will have more suggestions shortly (I hope), which we can discuss in person.

This suggestion is already in master. Closing.


Putting a colon on the title leads to friendly URL of /posts/empty

Whenever you put a colon in the title, the friendly URL becomes /posts/empty rather than having the title of the post. It makes me wonder: if you create two pages with that tile, will the second override the first?

I can't reproduce this bug with the latest master. Please see the attached screenshot.

Can't reproduce.

Why would you have a post title with a single character?

@anaggh Has shown that it will not overwrite the previous ones. So I guess the issue is resolved.
However, you're probably wondering why symbols are not generated in the friendly URL.

There are some character you can't have in the URI. And the colon are to define the port number.


Custom repository integration not possible anymore

hey
I'm using the Home Assistant 2023.9.3 version and its currently not possible to hadd your repository to the addons:

Is there maybe a config issue with the current new release?
Thanks for any help.
best regards

This is not an add-on. It's an integration. You need to install via hacs.


The icons are not shown well when hovering

Bug
When creating a channel, the icons are not being displayed correctly in the description section.
To Reproduce
Steps to reproduce the behavior:

Go to 'create channel'.
On the description section, when hovering over icons these are not displayed correctly.

Expected behavior
These icons should be visible when the mouse is over
Screenshots

System Configuration

LBRY App version: 0.53.4
LBRY Installation ID:  9aVm9nSeE2u1n3NFjoLMKvocjZsERnjEuAqdFkuAp92RotoiVJFdg4knE4Qu3uepVv
Operating system: Windows (Windows-10-10.0.19041-SP0)

Additional context
Add any other context about the problem here.

Ok, i'll be working on this ticket

@jessopb  I was watching it, what do you think?

Hi @jessopb , sorry to bother you, can you confirm this change?

Something like that, with 3 states? 3 different background colors


[FLINK-16359][table-runtime] Introduce WritableVectors for abstract writing

What is the purpose of the change
In FLINK-11899 , we need write vectors from parquet input streams.
We need abstract vector writing, in future, we can provide OffHeapVectors.
Brief change log

Introduce WritableVector interfaces.
Implement WritableVectors in Heap vectors.

Verifying this change
ColumnVectorTest
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)

Thanks @JingsongLi for the PR. I left some minor comments. Also noted we're doing some mem copy in methods like HeapDoubleVector::setDoublesFromBinary , and wonder whether we should add some safety check to make sure the source/dest have sufficient space, so as to avoid potential segment faults?

Thanks @JingsongLi for the PR. I left some minor comments. Also noted we're doing some mem copy in methods like HeapDoubleVector::setDoublesFromBinary , and wonder whether we should add some safety check to make sure the source/dest have sufficient space, so as to avoid potential segment faults?

Good suggestion! Updated.

Thanks @lirui-apache for your review. Merging....


Release 1.0.1

No review needed.

Coverage remained the same at 35.903% when pulling 585261ee1926467c4ac65ffc25f2273a0a93d879 on release_1.0.1 into 27e0084966fe075ba802ef76e6ced4d9eebee9ec on stable_1.0.


Shortcut to compare the last two tabs

Hi, I'm using this and will be good to have a shortcut (something like ctrl+shift+c) to compare the last two tabs, or the two tabs that are open side by side.
I was trying to figure it out how to do it in the sublime-keymap user, but I didn't find it.
Could you please maybe guide me how to do it ? or will be a good enhancement.
Thanks
Muadiv.

OK, I did a shortcut to open the compare menu ({ "keys": ["ctrl+alt+c"], "command": "sbs_compare" }, ) but will be good to have the option more easy .


redfish: fix nil check on gofish client

What does this PR implement/change/remove?
fixes a panic on Close() in the Redfish provider if the Redfish client was never setup.
goroutine 37 [running]:
github.com/bmc-toolbox/bmclib/v2/internal/redfishwrapper.(*Client).Close(...)
        /Users/jrebello/go/pkg/mod/github.com/bmc-toolbox/bmclib/v2@v2.0.1-0.20230324092939-d39fb75b6aa9/internal/redfishwrapper/client.go:126
github.com/bmc-toolbox/bmclib/v2/providers/redfish.(*Conn).Close(0x0?, {0x100c00005a804?, 0x477d9e?})
        /Users/jrebello/go/pkg/mod/github.com/bmc-toolbox/bmclib/v2@v2.0.1-0.20230324092939-d39fb75b6aa9/providers/redfish/redfish.go:63 +0x20
github.com/bmc-toolbox/bmclib/v2/bmc.closeConnection({0x107cd78, 0xc000182660}, {0xc0002de280?, 0x2, 0x0?})

Checklist

[ ] Tests added
[ ] Similar commits squashed

The HW vendor this change applies to (if applicable)
The HW model number, product name this change applies to (if applicable)
The BMC firmware and/or BIOS versions that this change applies to (if applicable)
What version of tooling - vendor specific or opensource does this change depend on (if applicable)
Description for changelog/release notes

rebased on main


Woodknots parallel featurization

Added parallel blob dl to workers.
Added knots dataset hooks.

just going for it, to delete branches


{project,workflow,dataset} delete endpoints are not complete

Current versions only remove single objects from the db, and not all the "children" objects.

Expected behavior (in progress):

Removing a Project removes all its Dataset's and Workflow's
Removing a Workflow removes all its WorkflowTask's
Removing a Dataset removes all its Resource's
Removing a Task is forbidden if it is associated to a WorkflowTask

Task removal is deferred to #403

Note: access control is not yet tested


Add Python 3.12 to the test matrix / wheels build

Changes proposed in this pull request:

Add Python 3.12 to the mix

The Python team encourages libraries to test against 3.12 now that beta is out

thanks for the pull request, I really doubt that everything will be assembled without errors - but it's normal, I'll correct it if anything.
how soon do you need those wheels? What to know - restart the action for this version or can it wait 2-2.5 weeks before the release of the next pillow-heif?

Thank you for the prompt response @bigcat88
Thought I'd add 3.12 to the Willow test matrix (https://github.com/wagtail/Willow/pull/124) and got the error, hence this PR. I can most certainly wait 2-2.5 weeks.

python 3.12 wheels published


Handling the notification for payment receive

Thank you very much for the great work!
I have a question regarding how to handle the notification when the payment is received?

Hey @xvilaysouk yw.
There is an example for streaming for payments: https://github.com/Soneso/stellar_flutter_sdk/blob/master/documentation/sdk_examples/stream_payments.md
However, this only works if your app is running. If you want to implement notifications even if the app is currently not open (or running in the background) on the device, than you will need to implement that on server side and send push notifications to your app.
Hope this helps.
Kind regards
Christian

Hey @xvilaysouk yw.
There is an example for streaming for payments: https://github.com/Soneso/stellar_flutter_sdk/blob/master/documentation/sdk_examples/stream_payments.md
However, this only works if your app is running. If you want to implement notifications even if the app is currently not open (or running in the background) on the device, than you will need to implement that on server side and send push notifications to your app.
Hope this helps.
Kind regards
Christian

Thanks Christian for your reply.
Sincerely yours,
X. Vilaysouk

Thanks Christian for your reply.
Sincerely yours,
X. Vilaysouk


scriptFailed and undefined behaviour.args

What is the purpose of scriptFailed ? Appears to not do anything.
Also if behavior is null, then the check on line 4 will log and continue executing, when we then reach  line 19 behaviour.args will throw exception (we can't get args on undefined behaviour).
https://github.com/jpotts/alfresco-developer-series/blob/75fd25869e42370a1d2a28fcaa74521a135c0005/behaviors/behavior-tutorial/behavior-tutorial-platform-jar/src/main/resources/alfresco/module/behavior-tutorial-platform-jar/scripts/onDeleteRating.js#L2-L19

Sweet! here is the PR: https://github.com/jpotts/alfresco-developer-series/pull/29


The nightly build sometimes fails with segmentation fault in LoadTest::testIntMapDummyClientServerRestart

The test failure at https://hazelcast-l337.ci.cloudbees.com/job/cpp-linux-nightly-64-SHARED-Release/93/console is examined. It is found out that theLoadTest finishes successfully but the test causes "Segmentation fault" on HazelcastClient destructor. The core was being caused due to the usage of thread cancel for PartitionService::shutdown. This somehow messes up with the mutex held by the cancelled thread and it causes segmentation fault. The case can easily be generated by repetitively running the LoadTest (I set up a test build for this where the LoadTest dummy client test running the test in a loop 10 times).
The fix is to not use thread cancel but just set a flag and wakeup the thread.
The commit also contains flushing the logger output when the logs are printed. This way we do not lose any logs if the process crashes.
Also added a control on the invocation service to not retry if the service is shutting down already.

Test PASSed.


Relay generates "open //./pipe/docker_engine: All pipe instances are busy." errors

When running docker-compose commands, which opens several simultaneous sockets at once, the relay generates error messages:
2019/06/14 08:51:50 open //./pipe/docker_engine: All pipe instances are busy.

On the docker-compose side, this shows itself in several ways, but mostly seen as:
ERROR: for my-service  ('Connection aborted.', BadStatusLine('No status line received - the server has closed the connection',))
ERROR: Couldn't connect to Docker daemon at http+docker://localunixsocket - is it running?

Did you find any workaround?

My work-around was to switch to the WSL2 engine with docker for windows support.  That alleviated the need for this tool.

Yeah that works, except if you're on a corporate machine with an older build.

The same error happens when you start multiple ssh sessions within a loop.

Same error here All pipe instances are busy
Any new about?
BTW: anyone tested it with Windows 11?


Remove unused _make_labels() in orchestrate_build

_make_labels() collects the 'koji-build-id' labels
from the worker builds, but that label is never
set on worker builds, so the method always
returns an empty dict.

CLOUDBLD-91

Signed-off-by: Ben Alkov<EMAIL_ADDRESS>Maintainers will complete the following section

[ ] Commit messages are descriptive enough
[ ] Code coverage from testing does not decrease and new code is covered
[ ] JSON/YAML configuration changes are updated in the relevant schema
[ ] Changes to metadata also update the documentation for the metadata
[ ] Pull request has a link to an osbs-docs PR for user documentation updates
[ ] New feature can be disabled from a configuration file

LGTM
Do we need to remove the labels to any calls to make_build_result in the test suite? I understand it is all mocked in there, but is it still relevant?

Travis?!

LGTM
Do we need to remove the labels to any calls to make_build_result in the test suite? I understand it is all mocked in there, but is it still relevant?

@athos-ribeiro; Ooohh, good point; I'll check


[ANTLR] gphase needs to take expression

Example of gphase in the spec  is gphase(-tau/2); and this -tau/2 looks expression in the grammar. However, current grammar takes Identifier.
quantumPhase
    : 'gphase' LPAREN Identifier RPAREN
    ;

fixed in https://github.com/Qiskit/openqasm/pull/195.


Implement a TLS based networks stack

More work towards #15, leaving out Tor for now but implementing secure communications for public network usage.
TODO:

[x] Justify crypto choices
[x] Tests

Crypto choices
PKCS_ECDSA_P256_SHA256 is what cln-grpc uses and seems closest to our existing crypto suite. If someone has stronger opinions on TLS I'd be happy to hear them.

LGTM.  AFAIK RSA will be larger signatures but faster verifying, but shouldn't make much difference for our purposes.
Are we going to use the same TLS for client-server communication?

Are we going to use the same TLS for client-server communication?

I don't think so. That has to happen via  Tor anyway eventually and Tor has built-in authentication and encryption if we use a hidden service.