[WIP] Add Composer plugin which scaffolds a Vagrantfile

Proof of concept for #1247 which supports all earlier setups with the addition of reading config_dir from composer.json.
Might want to drop support for some scenarios at some point tbh...

Like basically say "Add Drupal VM as a composer dependency, or use it standalone, and that's it"?

Yeah, that would probably make it easier.
Just realized that making this change would break all existing composer dependency setups as the old Vagrantfile will be overridden and the DRUPALVM_CONFIG_DIR definition will disappear.

break all existing composer dependency setups

😩

Also, with the Vagrantfile ever-expanding in size, I wonder if it might be good to have a 'ruby-src subfolder somewhere (something like that... whatever the Ruby convention would be) and break out business logic in there?
Or if there's some other way of building up a complicated Vagrantfile that's a better pattern. It's just getting unwieldy at this point.

Only one I've seen that breaks out the logic is homestead.
https://github.com/laravel/homestead/blob/master/Vagrantfile
https://github.com/laravel/homestead/blob/master/scripts/homestead.rb

This is what it would look like if we dropped support for a delegating Vagrantfile
diff --git a/Vagrantfile b/Vagrantfile
index ae5021f..3e4b5da 100644
--- a/Vagrantfile
+++ b/Vagrantfile
@@ -6,18 +6,6 @@ require 'yaml'

 VAGRANTFILE_API_VERSION = '2' unless defined? VAGRANTFILE_API_VERSION

-# Absolute paths on the host machine.
-host_drupalvm_dir = File.dirname(File.expand_path(__FILE__))
-host_project_dir = ENV['DRUPALVM_PROJECT_ROOT'] || host_drupalvm_dir
-host_config_dir = ENV['DRUPALVM_CONFIG_DIR'] ? "#{host_project_dir}/#{ENV['DRUPALVM_CONFIG_DIR']}" : host_project_dir
-
-# Absolute paths on the guest machine.
-guest_project_dir = '/vagrant'
-guest_drupalvm_dir = ENV['DRUPALVM_DIR'] ? "/vagrant/#{ENV['DRUPALVM_DIR']}" : guest_project_dir
-guest_config_dir = ENV['DRUPALVM_CONFIG_DIR'] ? "/vagrant/#{ENV['DRUPALVM_CONFIG_DIR']}" : guest_project_dir
-
-drupalvm_env = ENV['DRUPALVM_ENV'] || 'vagrant'
-
 # Cross-platform way of finding an executable in the $PATH.
 def which(cmd)
   exts = ENV['PATHEXT'] ? ENV['PATHEXT'].split(';') : ['']
@@ -44,6 +32,12 @@ def walk(obj, &fn)
   end
 end

+drupalvm_env = ENV['DRUPALVM_ENV'] || 'vagrant'
+
+# Default paths when the project is based on Drupal VM.
+host_project_dir = host_drupalvm_dir = host_config_dir = File.dirname(File.expand_path(__FILE__))
+guest_project_dir = guest_drupalvm_dir = guest_config_dir = '/vagrant'
+
 if File.exist?("#{host_project_dir}/composer.json")
   cconfig = {}
   composer_conf = JSON.parse(File.read("#{host_project_dir}/composer.json"))
@@ -51,18 +45,16 @@ if File.exist?("#{host_project_dir}/composer.json")
     cconfig = composer_conf['extra']['drupalvm']
   end

-  # If Drupal VM is a Composer dependency set the correct paths.
+  # If Drupal VM is a Composer dependency set the correct path.
   if Dir.exist?("#{host_drupalvm_dir}/vendor/geerlingguy/drupal-vm")
-    host_project_dir = File.dirname(File.expand_path(__FILE__))
     host_drupalvm_dir = "#{host_project_dir}/vendor/geerlingguy/drupal-vm"
-    host_config_dir = ENV['DRUPALVM_CONFIG_DIR'] ? "#{host_project_dir}/#{ENV['DRUPALVM_CONFIG_DIR']}" : host_project_dir
-    guest_drupalvm_dir = '/vagrant/vendor/geerlingguy/drupal-vm'
+    guest_drupalvm_dir = "#{guest_project_dir}/vendor/geerlingguy/drupal-vm"
   end

   # Read config_dir from composer.json if set.
-  if !ENV['DRUPALVM_CONFIG_DIR'] && cconfig.include?('config_dir')
+  if cconfig.include?('config_dir')
     host_config_dir = "#{host_project_dir}/#{cconfig['config_dir']}"
-    guest_config_dir = "/vagrant/#{cconfig['config_dir']}"
+    guest_config_dir = "#{guest_project_dir}/#{cconfig['config_dir']}"
   end
 end

break all existing composer dependency setups

This is actually the reason we are dropping all other installation methods so it's easier/safer to make BC breaks - https://github.com/beetboxvm/beetbox/issues/391#issue-209679900
But yeah these changes are only coming in the next minor version bump.

@oxyc there's also a test Class which could be useful -- https://github.com/beetboxvm/beetbox/blob/master/tests/PluginTest.php

[ ] update docs
[ ] should we include tests for the composer plugin?
[x] way more readable logic

Also, with the Vagrantfile ever-expanding in size, I wonder if it might be good to have a 'ruby-src subfolder somewhere (something like that... whatever the Ruby convention would be) and break out business logic in there?

https://github.com/geerlingguy/drupal-vm/pull/1332

@oxyc - Also, note that I think I'd like to include #1332 in a 4.x release, but I'm considering saving this change (along with more of a "this is how you do it the Drupal VM way" philosophy) for a 5.0 release. What do you think?

Yeah I agree this should be saved for 5.0.
Btw, is there a way to detect which version you're updating from in a composer plugin? If it is, we could issue a warning stating that the Vagrantfile has been overridden and a config_dir now needs to be set in composer.json.

Is there a way to detect which version you're updating from in a composer plugin?

That... I'm not sure of. I'm pretty new to Composer plugins myself.

I came pretty far and managed to detect updates from <5.0.0 but then I realized that it won't run when the package is first updated, it will run the previous versions code until the next update.
So I went a different, slightly hackier, way.

Also, note that I think I'd like to include #1332 in a 4.x release, but I'm considering saving this change (along with more of a "this is how you do it the Drupal VM way" philosophy) for a 5.0 release. What do you think?

Or we could just aim to release 5.0.0 at or shortly after DrupalCon? Like we did with 3.0.0 last year. Maybe too early for another major version bump...

Regarding docs for this I guess we could entirely delete Drupal VM as a Composer Dependency, or move it as a short page under_Getting Started_ section somewhere. In the Installation docs we point people to the Quick Start Guide. I guess we should either update the Quick Start Guide, or update these sections with how to set it up a project Drupal VM as a Composer dependency.
Basically the install instructions are

Require Drupal VM as a Composer development dependency.
composer require --dev geerlingguy/drupal-vm

Create and configure a config.yml file, eg. in vm/config.yml.

If you placed the config.yml file in a subdirectory tell Drupal VM about it
 composer config extra.drupalvm.config_dir vm

@oxyc - I think one other thing that would be helpful to document somewhere/somehow is how you could still patch Drupal VM using something like https://github.com/cweagans/composer-patches — sometimes people need to either use a change in master but not a tagged release, or patch one specific task somewhere for their project...

Maybe add as the first page Installation / How to integrate Drupal VM (I'm terrible at naming things)
Where we point out that there are two ways of integrating Drupal VM with your project.

You download Drupal VM and build a quick site within Drupal VM using vagrant up. Point out the downsides.

You require Drupal VM as a development dependency to your existing project. Show a quick start using drupal-composer/drupal-project

Then we also point to this page from the separate Install pages so people consider the options.

@oxyc - I'm good with that. As long as you don't make people who use it standalone feel shameful, since that's probably going to still be the default/majority use case for a while until more of the community adopts Composer.

that's probably going to still be the default/majority use case for a while

Yeah this would probably still be the first option. What about the Quick Start Guide though? Should that be updated to reflect both or should we keep composer dependency as an advanced feature?

patch Drupal VM using something like https://github.com/cweagans/composer-patches

Mind blown! I hadn't even considered that.

Do we want to add support for storing configuration values in the composer.json like beetbox?
We could either a) scaffold the file like they do or b) merge it into extra_vars as we already need to pass config_dir there anyways.

@oxyc we decided to let config in composer.json overwrite the normal config file so it wasn't possible to manage config in both places, mainly to reduce the WTF factor...
Otherwise, debugging could get pretty difficult and confusing as to which takes precedence.
When using composer to manage config it's recommended to ignore the normal config files -- https://github.com/thom8/drupal8-vagrant/blob/master/.gitignore
Also run into a few issues with data type conversion from JSON to YAML, so it's still WIP ;)

we decided to let config in composer.json overwrite the normal config file so it wasn't possible to manage config in both places, mainly to reduce the WTF factor...

Yeah it could easily get very confusing! However I don't see much reason for the feature when the file needs to be created anyways.  Drupal VM won't be providing defaults so the use case would mainly be forks or downstream projects (such as sprintbox) I guess?

Just wanted to note that I grabbed some of the work here and dumped it into https://github.com/geerlingguy/drupal-vm-docker, which is more of a quick proof-of-concept just using the Drupal VM Docker container as a starting point.
I am still planning on eventually converting Drupal VM itself into a Composer Plugin—maybe for 5.0.0 still—but I don't think the timing is right yet; it seems the majority of people using Drupal VM still download or git clone it, and aren't ready to take the full Composer plunge.
But we can use https://github.com/geerlingguy/drupal-vm-docker as a testing ground for this, too.

Dropping to 6.0.0 milestone. The Drupal community's adoption of Composer is just not there yet to default this thing to Composer-first :(


Add BZR segment

Adding support for GNU Bazaar DRCS
This segment requires the bzrlib dependency (but segment is ignored if the lib is not installed)
Works with colo style and shared branches
Overwrite request #128

closing in favor of https://github.com/banga/powerline-shell/pull/162


Standarize timestamp fields

Currently, we have pub_date, date, modified_date, add_date, created_dt and updated_dt.
I suggest to use created_at and updated_at for all the models.
This is useful for #4286

NOTE: for those that do not have these fields I suggest to add them. Example, Version.

Yea, we should just have a subclass that standardizes these fields, and everything inherits from.

I can probably implement it in #4850

Actually, I don't want to hold up that PR on this design decision, and we'll require code migrations anyways, so I'll hold off until we decide on names, etc.

Considering that we are already using django-extensions I suggest to go with

TimeStampedModel - An Abstract Base Class model that provides self-managed created and modified fields.

https://github.com/django-extensions/django-extensions/blob/master/django_extensions/db/models.py#L14
When implementing this, we will need a migration that migrate the old datetimes values from old fields name to the new names.

Can i work on this?
and does all the needs to inherits from TimeStampedModel ??

When implementing this, we will need a migration that migrate the old datetimes values from old fields name to the new names.

and i didn't get the meaning of this line, does it mean to provide the update migrations file??

okay, I get it.
A custom function needs to be implemented, like in this case
https://github.com/rtfd/readthedocs.org/blob/39303838b17f844f388c0e284afb3761af391a49/readthedocs/projects/migrations/0010_migrate_domain_data.py#L10

You should be able to just do the ./manage.py makemigrations and it will handle the rename of the field, I think.

@ericholscher
aren't we going to make every model inherit from TimeStampedModel ??

I think we shouldn't do every model, but just those that have either an updated or modified time. Maybe it makes sense to do an audit of them.

I believe some parts of the data are also exposed in public API's (eg. the Build object) so I'm not sure the best migration path for some of this stuff.

I believe some parts of the data are also exposed in public API's (eg. the Build object) so I'm not sure the best migration path for some of this stuff.

Since it's a read-only field on just a couple models in the v2 API, worst case we can just use a SerializerMethodField.


Update chart.js

Remove ".js" extensions.

@let-aurn is there a specific issue that this is fixing?


Pass keyword arguments in keras CTC to tensorflow CTC function

Click to expand!
Issue Type
Bug
Source
source
Tensorflow Version
2.8
Custom Code
Yes
OS Platform and Distribution
No response
Mobile device
No response
Python version
3.10
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current Behaviour?
Running a CTC-loss training can cause an error if the label is larger than the model's output. This error can be converted to a warning if you pass the approperiate flag. However, using keras ctc function (which is a wrapper to the tensorflow ctc function) doesn't allow the passing of key-word arguments to the ctc function in tensorflow.

The error text is

Not enough time for target transition sequence (required: 156, available: 13)0You can turn this error into a warning by using the flag ignore_longer_outputs_than_inputs

### Standalone code to reproduce the issue

```shell
The code in this keras tutorial https://keras.io/examples/audio/ctc_asr/

Relevant log output
File "/home/username/.local/lib/python3.10/site-packages/keras/engine/training.py", line 1082, in compute_loss
      return self.compiled_loss(
    File "/home/username/.local/lib/python3.10/site-packages/keras/engine/compile_utils.py", line 265, in __call__
      loss_value = loss_obj(y_t, y_p, sample_weight=sw)
    File "/home/username/.local/lib/python3.10/site-packages/keras/losses.py", line 152, in __call__
      losses = call_fn(y_true, y_pred)
    File "/home/username/.local/lib/python3.10/site-packages/keras/losses.py", line 284, in call
      return ag_fn(y_true, y_pred, **self._fn_kwargs)
    File "/tmp/ipykernel_8261/142572972.py", line 10, in CTCLoss
      loss = keras.backend.ctc_batch_cost(y_true, y_pred, input_length, label_length)
    File "/home/username/.local/lib/python3.10/site-packages/keras/backend.py", line 7023, in ctc_batch_cost
      tf.compat.v1.nn.ctc_loss(
Node: 'CTCLoss/CTCLoss'
2 root error(s) found.
  (0) INVALID_ARGUMENT:  Not enough time for target transition sequence (required: 156, available: 13)0You can turn this error into a warning by using the flag ignore_longer_outputs_than_inputs
	 [[{{node CTCLoss/CTCLoss}}]]
	 [[CTCLoss/CTCLoss/_86]]
  (1) INVALID_ARGUMENT:  Not enough time for target transition sequence (required: 156, available: 13)0You can turn this error into a warning by using the flag ignore_longer_outputs_than_inputs
	 [[{{node CTCLoss/CTCLoss}}]]
0 successful operations.
0 derived errors ignored. [Op:__inference_train_function_4574]

suggested edit is to the file python/keras/backend.py , just adding **kwargs passing to the function should in theory allow the passing of the flag to the ctc function in tensorflow

Suggested workaround
in /python/ops/ctc_ops.py update the key-word argument flag ignore_longer_outputs_than_inputs to True

Hey, can I take this issue ?

Hi @brilliant-ember ,
Could you please confirm whether you have done any changes to the code in documentation that causing the error mentioned? Could you please share us a use case of the requirement if any. I tested the same code in documentation without any error and the gist attached here.
Could you please confirm whether you have tested this code with changes you suggested?Was it worked for you?
Thankyou.

The suggested workaround worked for me, but the suggested fix didn't. because the my runtime wouldn't register my code change even if I restart my python runtime. The suggested workaround worked and registered the code change after a runtime restart. So updating the flag in /python/ops/ctc_ops.py worked but updated in python/keras/backend.py didn't even register and the runtime error didn't show my changes, maybe it has to do with the annotations, or my env isn't set up right.
To reproduce the error you need less time frames in the model, so increasing the time window and the frame step should do the trick.  I changed the vars to the ones below  in my local machine and the error occurred, I am running the collab now to confirm the issue happens there too.
frame_length = 1024
# An integer scalar Tensor. The number of samples to step.
frame_step = 512

In general this exception is raised when there's less timeframes than label length. When it is raised that means that the ctc model is not training for that sample. But sometimes you get cases where the label is just too short so it stops the training on an exception while it could have been just a small warning.

Hi, Thanks for opening the issue.
Usually,keras/backend.pyuses legacy code, in most cases it uses compat.v1 mode to ensure the backward compatibility.
It is suggested to use native tensorflow API for any specific use case. Thanks!

Existing keras implementation https://github.com/keras-team/keras/blob/4bc1eadedf19543b1445cb4b95e6f5502ef4ed82/keras/backend.py#L7019-L7022
Tensorflow implementation:
https://github.com/tensorflow/tensorflow/blob/941d9e5c8e9479bd666715ab6a5c2ce311141edf/tensorflow/python/ops/ctc_ops.py#L69-L78


Vite startup is slower than webpack and has a worse UX

Describe the bug
I'm migrating to Vite from Webpack and the default behavior of the Vite dev server seems to have some issues. I'll try to describe what I'm seeing.
When I start the dev server, it's prints a message like this:
  VITE v4.3.8  ready in 1892 ms

  ➜  Local:   http://<IP_ADDRESS>:3001/
  ➜  Network: use --host to expose
  ➜  press h to show help

If I open that link, I get a completely white screen (in the browser) and a spinner in the browser tab for about 2-3 minutes. To me, there are two issues here:

This is slower than webpack, which starts up this app in about 90 seconds
This is not a great UX. By comparison, webpack will print compilation messages on the command-line for 90 seconds, then announce that it's ready, then I'll open the page. Waiting on a blank page with no progress indicator and no ETA is kind of crappy. I have to monitor my Task Manager to make sure that something is actually happening

Next, I get these two messages (which I've opened another issue for):
[BABEL] Note: The code generator has deoptimised the styling of C:\Users\kgetz\Work\event-viewer\lib\geiger-studios\dist\index.js as it exceeds the max of 500KB.
[BABEL] Note: The code generator has deoptimised the styling of C:\Users\kgetz\Work\event-viewer\packages\cv-components\dist\index.js as it exceeds the max of 500KB.

I still don't understand why Babel is involved here at all, since I thought dependencies were built with esbuild? This part doesn't make sense to me.
Next, there's this:
4:22:28 PM [vite] ✨ optimized dependencies changed. reloading
4:22:28 PM [vite] Mixed ESM and CJS detected in react-virtualized, add it to optimizeDeps.needsInterop to speed up cold start

I looked at the docs and I don't see optimizeDeps.needsInterop. If I search the Vite website for needsInterop there are zero results. What is this config setting for?
And then finally, our favorite Babel messages appear again:
[BABEL] Note: The code generator has deoptimised the styling of C:\Users\kgetz\Work\event-viewer\lib\geiger-studios\dist\index.js as it exceeds the max of 500KB.
[BABEL] Note: The code generator has deoptimised the styling of C:\Users\kgetz\Work\event-viewer\packages\cv-components\dist\index.js as it exceeds the max of 500KB.

Reproduction
N/A
Steps to reproduce
No response
System Info
System:
    OS: Windows 10 10.0.22621
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz
    Memory: 5.35 GB / 15.71 GB
  Binaries:
    Node: 16.19.1 - C:\Program Files\Node.js\node.EXE
    npm: 9.6.2 - C:\Program Files\Node.js\npm.CMD
  Browsers:
    Edge: Spartan (44.22621.1702.0), Chromium (113.0.1774.50)
    Internet Explorer: 11.0.22621.1
  npmPackages:
    @vitejs/plugin-react: 4.0.0 => 4.0.0
    vite: 4.3.8 => 4.3.8

Used Package Manager
pnpm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

I'm sorry, that won't be really possible here. I'm working with a very large enterprise application that has private source code.


implement ema warmup from @crowsonkb

@nousr oh my, thank you! and thank you as always Katherine 😃  @crowsonkb


gh access token not required (?)

Maybe I'm missing something, but why would one need to create a gh access token to simply clone a public (!) repository? Your instructions also don't tell them to fork it, so they would not have write permissions there either...
I think we can remove this part of the setup :)

also a bit confusing how to open the notebook from colab after downloading.. seems colab can only read fiels under Colab Notebooks folder. In this tutorial files are downloaded in the Githubs folder and they are invisible.

Hmm, that worked for me though. I was just navigating to the Github folder on my google drive and then double-clicking and they opened in Colab. Does that work for you?

No, nothing appears there.. I can only download them, but cannot run them

Problem solved:
The python notebook files should not be opened in the colab.research.google.com through the "file" menu. Instead, they should be opened in the google drive website. The files will be automatically opended with colab.


Python Chatbot[GSSoC23] #65

Here we create a currency conversion chat bot using Python.
#65

hi @neelshah2409 I have resolved the issue created can you look into it .


Allow to quote text

If we select text and hit single or double quotes, please quote the selected text, instead of replacing the selected text with a quote character.
This would make it work like in other programming languages, then.

This is done by the vscode official Markdown extension.
You can do this by making a PR changing line36
"surroundingPairs": [
	["(", ")"],
	["[", "]"],
	["`", "`"]
]

to
"surroundingPairs": [
	["(", ")"],
	["[", "]"],
	["`", "`"],
	["'", "'"],
	["\"", "\""]
]


Black Screen crash to Home Screen

I've reviewed quite a few of the issues posted here and followed some other information elsewhere and I can't seem to get it to run. It gets stuck on a black screen (which can turn gray if I press a button, using a Retroid Pocket handheld even without controller support). Or just crashes back to the Home Screen.
I'm using the newly release Beta.
I currently have the www folder in storage/emulated/0/OMORI/www as it seemed the app was having trouble getting it on an SD Card or within too many folders. I have also tried just simply using the OMORI directory and the www directory.
www causes the back to Home Screen crash.
OMORI does nothing and stays on a black screen.
www Log
omori.log
OMORI Log
omori.log
The chip is also a Unisoc T618, so it may simply be possible that this won't boot due to that.

Please run adb logcat -c then adb logcat, crash the game (with www folder set as installation directory) and send the output here

Here's the output:
https://pastebin.com/57JGAp01

Looks like your webview is crashing, you can try to download Android System WebView Beta from play store and set it as WebView implementation in Developer settings

That did indeed fix it. Thanks!


Let useNameAsTextLabel set contents of 'text' attribute

Herbert said this is a low priority, but it might be nice for v2:  let the useNameAsTextLabel function actually set the 'text' of the text glyphs so that the IDs are used there instead of the names, so that people who get the model also see the IDs.

Sounds good. Then, we will implement it in v2.


same ip addr value printed for both src and dst in the CSV

unlike the printed values in the stdout, some lines in the CSV output file have the same IP address for source and destination

printed them in separate lines with 2 different calls for frprintf


feat: added voyager in backend

See issue #1824.

Hello @darshi1337 ,
We need for you to sign the DCO agreement by signing off your commits

Thanks for the contribution,
since it seems to be a work in progress (no tests, print statements, etc...) I will put it as a Draft.

Hello @darshi1337 ,
is there any progress to be expected here?


Fix build mode not propagated in android native asset build

Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] I followed the breaking change policy and added Data Driven Fixes where supported.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

@dcharkes

Please add a PR description as well.

Please add a PR description as well.

My bad. Fixed.


Update instagram-channel-setup.md

Added facebook business_management api in documentation.

@scmmishra  Could you check whether we need this permission ?


Dev repository fixes

I had to change these to make Ceph dev deployments work

The CI failures here are unrelated to this PR, as we don't have any PR tests currently that test dev or rhcs installs. I manually ran dev-ansible2.3-journal_collocation test that installs the master branch of ceph with this branch and it passed: https://2.jenkins.ceph.com/job/ceph-ansible-scenario/8/console


Added base SPA program

Added a base SPA to load if no url have been added to the composeui cli.

I'm approving it and going to take a look at the express code during integration


Async Version

can there be a complete async mode?
This will also help prevent blocking.

Duplicate of #732

Duplicate of #732


Add support for recording the diff in the ConfigurationPolicy status

A new recordDiff option of "InStatus" allows the diff to be stored in
the object properties in the ConfigurationPolicy status.
The new default recordDiff value is "InStatus" unless sensitive data may
be in the diff. Then the user must explicitly set recordDiff.
Relates:
https://issues.redhat.com/browse/ACM-11421

/cc @yiraeChristineKim

The Jira mentions "the new options of InStatus and Automatic" but I think this implementation doesn't have Automatic - it just has some behavior when the field isn't set. That's fine with me, just wanted to make sure that detail doesn't get lost.


Layer weight conversion compat matrix for between TensorFlow and PyTorch layers

Right now, the platform independent NPZ layer weights support is rather ad-hoc and not very well documented.  For 2.0, we should at least track which models/primitives are supported (right now pretty much only Transformer models)

For now, Im ok with this being undocumented as its likely to change quite a bit.  Right now all transformer encoder layers and all positional and lookup table embeddings that would typically be used when doing large-scale transformer pre-training work.  Nothing else does.  TensorFlow supports loading only, not saving in NPZ, PyTorch supports both.
Implementations are here:
PyTorch: https://github.com/dpressel/mead-baseline/blob/master/layers/eight_mile/pytorch/serialize.py
TensorFlow: https://github.com/dpressel/mead-baseline/blob/master/layers/eight_mile/tf/serialize.py


Error auth SPFX Webpart calling Azure API authenticated with APP Registration and external user (Redirects 3 times before get token)

Target SharePoint environment
SharePoint Online
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Developer environment
Windows
What browser(s) / client(s) have you tested

[ ] 💥 Internet Explorer
[X] 💥 Microsoft Edge
[X] 💥 Google Chrome
[ ] 💥 FireFox
[ ] 💥 Safari
[ ] mobile (iOS/iPadOS)
[ ] mobile (Android)
[ ] not applicable
[ ] other (enter in the "Additional environment details" area below)

Additional environment details
SPFX v1.12.1
Describe the bug / error
I make a SPFX Webpart that calls API published on Azure with authentication configured by App Registration. I put all API permission configuration on package-solution.config:

And to get token I use aadTokenProvederFactory :

If I open sharepoint page with webpart with an normal licensed user, all goes fine.
But if I open sharepoint page with an external user, then strange behaviors occurs:
Page is opened, webpart is showed but cannot call API because get token fails and page is refreshed 3 times. After 3 refreshes , all goes fine and get token call finished successfully and API is called .
This behavior  only occurs with external users and authenticated API. If I disable authentication on API , all goes fine and no redirects occur.

Someone can help me?
Steps to reproduce

Open page with webpart that calls Azure authenticated API
Page is refreshed
Page is refreshed
Page is refreshed
Page is opened and all goes fine.

Expected behavior
Expected behavior is like a normal licensed user.

hey @marcmoraRAONA, how did you register the Guest account in AAD and SharePoint? mind provide a snipped of the configuration from AAD portal if this is not a production tenant?

Really I only share site with external user, this user now can enter to the site and can use as a normal user except this behavior with authenticated API.
This is the user configuration on Azure AD:

This is App Registration configuration:

This is App Service (API) authentication configuration:

Thanks

Someone can help me? Someone can reproduce same situation?

hey @marcmoraRAONA, sorry for my delay in answering. Here's what I did:

created an SPFx app that access Microsoft Graph
added a guest user in AAD
gave access to the guest user to the Team site
log in to guest user and confirm that everything was working.
I had no issue on that test.. which makes me thinking that the issue you are perceiving is on the custom API registration. Out of curiosity: if you make a call to Microsoft Graph only (I see in your snipped above you do register to graph scope too), do you experience same / similar issue? Or the issue is only when the code tries to get a token to access the custom API?


Add width property to fixed body styles

Corrects the width of the body element when scrolling is disabled.

Landed in<EMAIL_ADDRESS>Thanks!


[SPARK-35624][CORE]Support reading inputbytes and inputrecords of the…

What changes were proposed in this pull request?
add inputBytes and inputRecords interface in SparkStageInfo
Why are the changes needed?
One of our projects needs to count the amount of data scanned and the number of scanned data rows during the execution of sparksql statements, but the current version of spark does not provide an interface to view these data, so I want to obtain this type of data through the spark context interface
Does this PR introduce any user-facing change?
expose new interface in spark context
How was this patch tested?
Manual test

Can one of the admins verify this patch?

@cloud-fan hi, please take a look.

+CC @cloud-fan who took a look at this last.
I am fine with the change in general.

ok to test

Test build #142907 has started for PR 33874 at commit fb66ab3.

Test build #142907 has finished for PR 33874 at commit fb66ab3.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/142907/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47410/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47410/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/47410/

@allendang001  have you checked the python codes?
Especially the status.py:
https://github.com/apache/spark/blob/387a251a682a596ba4156b7d12e6025762ebac85/python/pyspark/status.py#L29-L31

@allendang001 have you checked the python codes?
Especially the status.py:
https://github.com/apache/spark/blob/387a251a682a596ba4156b7d12e6025762ebac85/python/pyspark/status.py#L29-L31

I am not familiar with python codes, can you complete this part?

cc @HyukjinKwon

Just adding these fields into status.py should be enough. e.g.)
diff --git a/python/pyspark/status.py b/python/pyspark/status.py
index a6fa7dd3144..f342ee38a2d 100644
--- a/python/pyspark/status.py
+++ b/python/pyspark/status.py
@@ -28,7 +28,7 @@ class SparkJobInfo(namedtuple("SparkJobInfo", "jobId stageIds status")):

 class SparkStageInfo(namedtuple("SparkStageInfo",
                                 "stageId currentAttemptId name numTasks numActiveTasks "
-                                "numCompletedTasks numFailedTasks")):
+                                "numCompletedTasks numFailedTasks inputBytes inputRecords")):
     """
     Exposes information about Spark Stages.
     """
diff --git a/python/pyspark/status.pyi b/python/pyspark/status.pyi
index 0558e245f49..8ea885693bb 100644
--- a/python/pyspark/status.pyi
+++ b/python/pyspark/status.pyi
@@ -32,6 +32,8 @@ class SparkStageInfo(NamedTuple):
     numActiveTasks: int
     numCompletedTasks: int
     numFailedTasks: int
+    inputBytes: int
+    inputRecords: int

 class StatusTracker:
     def __init__(self, jtracker: JavaObject) -> None: ...
diff --git a/python/pyspark/tests/test_context.py b/python/pyspark/tests/test_context.py
index 4611d038f96..2c28fbabcc8 100644
--- a/python/pyspark/tests/test_context.py
+++ b/python/pyspark/tests/test_context.py
@@ -239,6 +239,8 @@ class ContextTests(unittest.TestCase):
             self.assertEqual(1, len(job.stageIds))
             stage = tracker.getStageInfo(job.stageIds[0])
             self.assertEqual(rdd.getNumPartitions(), stage.numTasks)
+            self.assertGreater(0, stage.inputBytes)
+            self.assertEqual(10, stage.inputRecords)

             sc.cancelAllJobs()
             t.join()

BTW, please keep the Github PR template as is (https://github.com/apache/spark/blob/master/.github/PULL_REQUEST_TEMPLATE), and describe, at "Does this PR introduce any user-facing change?",  which interface it adds with an example preferably.
Also, please add a test at StatusTrackerSuite.

Oh, and we should fix Python example here: https://github.com/apache/spark/blob/0494dc90af48ce7da0625485a4dc6917a244d580/examples/src/main/python/status_api_demo.py#L59-L60 just like you did in Java.
Lastly, Apache Spark leverages the resources of GitHub Actions in your forked repository to test your PR. Please enable it, see also https://github.com/apache/spark/pull/33874/checks?check_run_id=3471668214.

StatusTrackerSuite

thanks a lot

Test build #143111 has started for PR 33874 at commit ebe9447.

Test build #143111 has finished for PR 33874 at commit ebe9447.

This patch fails Python style tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/143111/

Test build #143112 has started for PR 33874 at commit c67a9dd.

Test build #143112 has finished for PR 33874 at commit c67a9dd.

This patch fails Python style tests.
This patch merges cleanly.
This patch adds no public classes.

i have submit this codes, @HyukjinKwon  PTAL

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/143112/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47615/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47615/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/47615/

Kubernetes integration test unable to build dist.
exiting with code: 1
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47617/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/47617/

Test build #143143 has started for PR 33874 at commit 16e6323.

Test build #143143 has finished for PR 33874 at commit 16e6323.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/143143/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47647/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47647/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/47647/

retest this please

@allendang001 mind enabling GitHub Actions in your forked repository? See also https://github.com/apache/spark/pull/33874/checks?check_run_id=3565581644

Test build #143176 has started for PR 33874 at commit 16e6323.

Test build #143176 has finished for PR 33874 at commit 16e6323.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/143176/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47679/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47679/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/47679/


sd: "no paths found" logging is opaque

When sciond can't find any paths:
2019-10-31 14:26:07.868232+0000 [EROR] No convergence in lookup debug_id=42f0a1eb iteration=3
2019-10-31 14:26:07.868241+0000 [EROR] Unable to get paths debug_id=42f0a1eb err="Segment lookup doesn't converge iterations="3""

"convergence" isn't something a user will understand (i certainly don't know what it means from looking at the logs).

probably boils down to https://github.com/scionproto/scion/issues/3094


Matrix build

What
Introduce matrix builds.
How

Modified the Jenkinsfile to split FindBugs from the cloudant tests and run in parallel
Added new nodes for CouchDB 1.6 and CouchDB 2.0.

Testing
No new tests, only ReplicatorTest modified to create the _replicator database during set-up.

Suggest we close this for now, given #348.
Hopefully we can pick it up again sometime when maybe we can do it without DinD. Maybe using peer containers or a multi docker test topology of some kind.


feat: subMacro injection

A

Just a quick question as I see lots of new features coming since a few weeks:
Is the documentation updated accordingly so that at least a minimal sample is included?

Uha, jab the doc is still a work in progress, this week will be the next release ;-) Most of the commits so far are actually fixes or stuff that should actually work but somehow does not :see_no_evil: ...
This specific feature added the evaluation of macros to dynamically created LiaScript content. Here is an example I prepared:
https://github.com/LiaPlayground/ImageDescriber
But anyways, you are right ... we have to focus on documentation

No worries. I'll gladly help documenting and issue tracking when I find the time. As long as new features are being tracked in the changelog I know what is missing in the docs. I just wanted to know if this is on the todo list. 😉

@pwab I should have said within one week :see_no_evil: ... However, the next part about styling is ready.
https://www.youtube.com/watch?v=Zg4YlWmHIP4
The next one about formulas and Footnotes should be rather short ... before moving to quizzes, coding and the rest ... ;-)


Code re-org: data loading

The data loading should be generalized more to deal with different datasets.  Changes can go under /src/deepdisc/data_format/. The way data is loaded in the detectron2 framework is described here [https://detectron2.readthedocs.io/en/latest/tutorials/data_loading.html]

A function is built to read in all the metadata from memory and is passed to the DatasetCatalog.register() method to register it.  This function should return a list[dict] Right now this function is get_data_from_json. It assumes the metadata is saved as a json list of dicts, formatted in the COCO format (see https://detectron2.readthedocs.io/en/latest/tutorials/datasets.html).  Images are not stored in the dictionaries, only filepaths to the images.
The train_mapper_cls class will take as input a single item from the list[dict].  It will use the image filepath to read in the image using some function, apply augmentations, store it in the dictionary and slightly change the format of the dictionary metadata.  This new dictionary that contains the image and reformatted metadata is what is fed into the model.  Right now the function to read in images in the train_mapper_cls is the read_image_hsc function inside astrodet/astrodet.

Both functions in step 1 and 2 should be easily customizable to deal with different dataset formats.  I think having some general base class for step 1 for reading in data and returning a list[dict] would be useful.  Also a base class for reading in image data would also be useful.  This would address much of issue #30.

[ ] Generalize get_data_from_json to class that has a method to read in all metadata and output it in coco dict format
[ ] Generalize the read_image methods to a class that will take a user specified function, apply some scaling, and return an image based on a key found in the dictionary output from step 1.

@grantmerz, what are some of the other dataset formats we want to support beyond the json/COCO format?

For the most part, code should stick with list[dict] COCO format. For example, if you look at demo_decam.ipynb, there is a get_astro_dicts function that outputs a list[dict] after manually reading in files and formatting everything to COCO format.  Below it, there is a get_data_from_json function that reads in a COCO pre-formatted json file and returns a list[dict]. Since these output the same thing, my vision was to have a common class for them. The user would still have to write the code in get_astro_dicts since image files may be formatted differently.  But it would be useful to have the option to customize this portion and output a list[dict] that doesn't adhere to COCO format.

The utility is that if we want to generalize this for other models, we can still use the data loading tools that assume list[dict] but the dict can contain whatever data those other models need

As a small status update. I've been working on this here: https://github.com/lincc-frameworks/deepdisc/blob/data_loader/src/deepdisc/data_format/file_io.py#L12
The main idea being that the DataLoader class has a generate_filedict function which reads in filenames from a given directory. It's generalizable to the extent of being able to handle DECAM and HSC data within the same API. The output is standardized and then can be fed into generate_dataset_dict to pass the image and mask files along to user-defined functions. The result is a list of whatever output is produced by the UDF at the moment. I also plan on potentially adding the canned get_astro_dict() functions from the DECAM and HSC notebooks as available on-hand functions here, modified to work with the format being passed along to the UDFs.
The list[dict] format can also be gotten directly from a file, like get_data_to_json if it's available.
Plan to keep working on this tomorrow, and actually trying this code will almost certainly not work as I've yet to start using it in any capacity. Let me know if this looks totally off-base from what is being requested.

I like the way this is structured.  It would be nice to change the self.dataset_dicts to a self.dataset property.  This is to indicate that the class should be able to output data that might not be in dictionary format, for instance a loaded numpy array of all images+metadata.  This output is reformatted in the DataMapper class which feeds directly into the model, so it's ok if the output data from DataLoader isn't necessarily a dictionary (it just needs to be indexable for pytorch backend). Then, have a general method that users can provide a custom function to for loading the dataset.  This way, the user could insert a loading function (like np.load/get_data_from_json).  Maybe the generate_dataset_dict function could be part of a ScarletDataLoader subclass


Rename the probe rust file to probe.rs

This would help some people with build problems using nix or to be more specific buildRustCrate (but that's probably not meaningful to you).
See https://github.com/kolloch/crate2nix/issues/39 and https://github.com/NixOS/nixpkgs/issues/74071.
It is clearly a bug in buildRustCrate but if you could accept this change in the meanwhile...

I agree. Thank you.


Error while trying to install docker-io

Hi
As per https://docs.docker.com/installation/rhel/ installation procedure for 6.5, I am trying to install docker using yum install docker-io command
However, I get error saying below
Setting up Install Process
No package docker-io available.
Error: Nothing to do
Any help in this regard is greatly appreciated
Thanks in advance
Ramesh

Hi!
If you are reporting a new issue, PLEASE make sure that does not have any duplicates already open.
We would like to take this time to remind you of the information we need to debug the problem you are seeing. This is an automated response so if this ticket is not about a bug, do not fret.
If you fail to provide this information within 7 days, we will close this because we cannot debug your issue. We can reopen whenever the information is provided.
Thank you.
Please see:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues
Description of problem:

`docker version`:

`docker info`:

`uname -a`:

Environment details (AWS, VirtualBox, physical, etc.):

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual Results:

Expected Results:

Additional info:

#ENEEDMOREINFO

Do you have epel setup? Are you on x86-64?

Now I setup epel and running into different issue
Steps to reproduce the issue that I am facing

Installed EPEL on 6.5 RHEL
Installed docker-io
Able to run "docker" command
When running "docker run -i -t fedora /bin/bash" command using without root, getting below error FATA[0000] Post http:///var/run/docker.sock/v1.17/containers/create: dial unix /var/run/docker.sock http:///var/run/docker.sock/v1.17/containers/create:%20dial%20unix%20/var/run/docker.sock : permission denied. Are you trying to connect to a TLS-enabled daemon without TLS?

However, with root getting diff error like below for the same command FATA[0000] Cannot connect to the Docker daemon. Is 'docker -d' running on this host?

2 issues, 1 your user doesn't have access to /var/run, and the docker daemon is not running.
You need to make sure to start the service first.


Investigate HTMX

HTMX could be a great simple addition for some of the more dynamic pages like attendance.

https://www.mattlayman.com/blog/2021/how-to-htmx-django/

I'm also thinking about how to implement a drag and drop interface for mentor <> project <> small group setup. It might be a bit much to have something like Svelte on some pages and HTMX on others. If we're using something like Svelte for more complicated uses cases, might as well also use it on the simpler cases like attendance as we'll have the build pipeline setup for it anyway.


KAMUDEP-37| Change ports in to non privileged

Change ports in to non privileged in kamu-api-server and service in kamu-web-ui

Looks like this PR did not update containerPort of kamu-web-ui chart, causing liveness probes to always fail and pods to enter a crash loop.

@sergiimk fix for containerPort in kamu-web-ui hadn't been released at the time this PR was merged.


Cvd continues even if main signatures is missing

If the main.cvd or dailt.cvd is missing, the update continues, but does not re-pull the daily or main. This has been addresses in the pull request at https://github.com/Cisco-Talos/cvdupdate/pull/35

Merged #35 today. Sorry it took so long!


Update README URLs based on HTTP redirects

Created with https://github.com/dkhamsing/frankenstein
Corrected URLs

Was
Now

http://www.jsoniq.org/
http://jsoniq.org/

https://code.google.com/p/x2js/
https://github.com/abdmob/x2js

https://ilovecoding.org/lessons/5622d1db8795649145fce182
https://ilovecoding.org/lessons/json-what-is-json-and-how-to-use-it

Thanks.

:wink:


Failure to launch: "no attribute password_reset_confirm"

I followed the installation instructions for a Development environment, but when I go to run the first command python manage.py migrate, I receive a traceback that throws AttributeError: module 'django.contrib.auth.views' has no attributes 'password_reset_confirm'
Any help here would be great 👍
Full traceback:
(YaraGuardian) zeroharbor :: /opt/YaraGuardian ‹master*› » python3.5 manage.py migrate
Traceback (most recent call last):
  File "manage.py", line 8, in <module>
    execute_from_command_line(sys.argv)
  File "/home/adam/.local/share/virtualenvs/YaraGuardian-6kWGavhf/lib/python3.5/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line
    utility.execute()
  File "/home/adam/.local/share/virtualenvs/YaraGuardian-6kWGavhf/lib/python3.5/site-packages/django/core/management/__init__.py", line 375, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/home/adam/.local/share/virtualenvs/YaraGuardian-6kWGavhf/lib/python3.5/site-packages/django/core/management/base.py", line 323, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/home/adam/.local/share/virtualenvs/YaraGuardian-6kWGavhf/lib/python3.5/site-packages/django/core/management/base.py", line 361, in execute
    self.check()
  File "/home/adam/.local/share/virtualenvs/YaraGuardian-6kWGavhf/lib/python3.5/site-packages/django/core/management/base.py", line 390, in check
    include_deployment_checks=include_deployment_checks,
  File "/home/adam/.local/share/virtualenvs/YaraGuardian-6kWGavhf/lib/python3.5/site-packages/django/core/management/commands/migrate.py", line 65, in _run_checks
    issues.extend(super()._run_checks(**kwargs))
  File "/home/adam/.local/share/virtualenvs/YaraGuardian-6kWGavhf/lib/python3.5/site-packages/django/core/management/base.py", line 377, in _run_checks
    return checks.run_checks(**kwargs)
  File "/home/adam/.local/share/virtualenvs/YaraGuardian-6kWGavhf/lib/python3.5/site-packages/django/core/checks/registry.py", line 72, in run_checks
    new_errors = check(app_configs=app_configs)
  File "/home/adam/.local/share/virtualenvs/YaraGuardian-6kWGavhf/lib/python3.5/site-packages/django/core/checks/urls.py", line 13, in check_url_config
    return check_resolver(resolver)
  File "/home/adam/.local/share/virtualenvs/YaraGuardian-6kWGavhf/lib/python3.5/site-packages/django/core/checks/urls.py", line 23, in check_resolver
    return check_method()
  File "/home/adam/.local/share/virtualenvs/YaraGuardian-6kWGavhf/lib/python3.5/site-packages/django/urls/resolvers.py", line 398, in check
    for pattern in self.url_patterns:
  File "/home/adam/.local/share/virtualenvs/YaraGuardian-6kWGavhf/lib/python3.5/site-packages/django/utils/functional.py", line 80, in __get__
    res = instance.__dict__[self.name] = self.func(instance)
  File "/home/adam/.local/share/virtualenvs/YaraGuardian-6kWGavhf/lib/python3.5/site-packages/django/urls/resolvers.py", line 579, in url_patterns
    patterns = getattr(self.urlconf_module, "urlpatterns", self.urlconf_module)
  File "/home/adam/.local/share/virtualenvs/YaraGuardian-6kWGavhf/lib/python3.5/site-packages/django/utils/functional.py", line 80, in __get__
    res = instance.__dict__[self.name] = self.func(instance)
  File "/home/adam/.local/share/virtualenvs/YaraGuardian-6kWGavhf/lib/python3.5/site-packages/django/urls/resolvers.py", line 572, in urlconf_module
    return import_module(self.urlconf_name)
  File "/home/adam/.local/share/virtualenvs/YaraGuardian-6kWGavhf/lib/python3.5/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 986, in _gcd_import
  File "<frozen importlib._bootstrap>", line 969, in _find_and_load
  File "<frozen importlib._bootstrap>", line 958, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 673, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 665, in exec_module
  File "<frozen importlib._bootstrap>", line 222, in _call_with_frames_removed
  File "/opt/YaraGuardian/YaraGuardian/urls.py", line 45, in <module>
    auth_views.password_reset_confirm, {'template_name': 'prelogin/ResetPassword.html'},
AttributeError: module 'django.contrib.auth.views' has no attribute 'password_reset_confirm'

I worked around this by using the Docker installation instead of virtual environment. Not exactly a fix but it works for me at the very least.


[Info site] Privacy Policy and Terms and Conditions are missing

Privacy Policy and Terms and Conditions are missing from the Info website, even thought you are marking that you are agreeing with the Terms and Conditions upon singup.

I guess the Legel team is working on those ?

@rkgeorgiev Unfortunately still don't have the content for those pages.
Anyhow at the moment the submission of the form doesn't store any data anywhere, as there's no backend whatsoever :joy_cat:
Thanks for bringing that up

@rkgeorgiev Unfortunately still don't have the content for those pages.
Anyhow at the moment the submission of the form doesn't store any data anywhere, as there's no backend whatsoever 😹
Thanks for bringing that up

I have asked the Legal team in Discord if someone is working on that. Hopefully a discussion will follow about it, since I believe its quite important.

Url to privacy policy document https://docs.google.com/document/u/1/d/1J4koWHP3MX00zffCNhjs1sAwPixFcd9k/edit?usp=drive_web&ouid=101217799053638702478&rtpof=true

Url to privacy policy document https://docs.google.com/document/u/1/d/1J4koWHP3MX00zffCNhjs1sAwPixFcd9k/edit?usp=drive_web&ouid=101217799053638702478&rtpof=true


Properly check if connection can be established for importing interactive visualizations

Fix #895
Summary
As pointed out by @chriseclectic , loading qiskit with no internet connection results in a ConnectionError because the interactive visualizations max out the number of attempts to look for the needed host url.  Here we replace the previous check with on that gracefully exits if no connection can be established.
Details and comments

Please, remember to file an issue and link the PR with it by adding "Fix ".

Can you remember to remove requests as a dependency, as the only place where it was used is now replaced by a standard library call (which I think is a good move)?

Also, perhaps we could take the chance to reevaluate the need for the
from qiskit.tools.visualization import (circuit_drawer, plot_histogram)

line from the main qiskit/__init__.py, in the spirit of @ajavadia's comment at https://github.com/Qiskit/qiskit-terra/pull/890#issuecomment-420779587?
Our top-level qiskit namespace and import qiskit is already more complicated and full of implications than ideal, and importing a member of qiskit.tools there entangles (no pun intended) it even more, which has been the root cause of two user-facing bugs (#895 and #889) already since it was introduced. Any thoughts?

Actually the bug fixed here was caught becuase of the top level visualization imports. They were not the cause. Anytime someone loaded the visualization module, the same issue would pop up.

The function added here could also be useful for having a more graceful error message if the register function cannot connect to the host urls.


Doc

Can you please add some more documentation.

Let me know what part of this project is lacking in explanation and I'll add it!


Jenayah: Watch "Arya Power Yoga Academy"

Jenayah requests the watch of the watch_keyword "Arya Power Yoga Academy". See the MS search here and the Stack Exchange search in text, in URLs, and in code.

"Arya Power Yoga Academy" has been seen in 0 true positives, 0 false positives, and 0 NAAs.

Approved by tripleee in Charcoal HQ


Printing

Coverage decreased (-1.5%) to 57.914% when pulling ad969f837c11cdf02bdfcbdf3c4dfa24beb9ce68 on printing into a72795ba5b0efab4f34cb8ddd538489ca821dc1a on master.


Fix(rhino): Do not skip first item if it is one-to-one conversion

It was on me. While fixing the group highlight performance issue, this scenario skipped..

this was my bad for post multi material, thx for fixing!


remove magic numbers

The code doesn't have too many magic numbers https://en.wikipedia.org/wiki/Magic_number_(programming), but it has some, like this:
https://github.com/MFlowCode/MFC/blob/f347b30f9c0194c0ab3492b7772fa6edbc8d0860/src/simulation/m_qbmm.fpp#L1115C36-L1116
remove them (can set them as constant parameters in the module or subroutine).

I'd be curious to see this strategy continued: https://github.com/MFlowCode/MFC/pull/580/files#diff-3cbade161f91b38a72f4c35e4ab1a5fd66b24ab50d700e4e56eae364e5bd84ed


hidden leaderboard filters in mobile view

Changes

fixes #363
made filters collapsible in mobile view

Screenshots

@rithviknishad Is this fine?

@kshitijv256 The design looks good; Lets ship it out

@bodhish I have already added this change in preivious commit 9fbcd78

@kshitijv256 could you resolve the merge conflicts?

@rithviknishad fixed conflict


Add crawler detecting via ip adress

Hello,
I think it would be great to add detection of the crawlers using a client ip address.
May be some resources like iplists.com or myip.ms/browse/web_bots/ can be used for obtainig a nearly complete list of the ip addresses.

Hi,
Thanks for the suggestion. Detecting via IP address is something we have considered in the past, but ultimately decided against it as we feel it would be difficult to maintain, IP addresses change etc etc.
We are open to being persuaded otherwise, but we can't see it happening in the near future.
Would like to hear other peoples thoughts on this, so will leave this issue open for a while.
Thanks 👍

Closing this as it is unlikely this is a route we will go down


Add a /health endpoint to the Product service for Kubernetes health check

As a Developer/ System Administrator
I need a health check endpoint for Kubernetes
So that I can know the service is running and good for deployment
Details and Assumptions

Add a /health endpoint to the Product service and should return {"status":"OK}, 200

Acceptance Criteria
Given the service is running
When sending a GET request to /health
Then the service should return {"status": "OK"}

Raised PR #51


Broken devise's html template

Hey guys.
Just switched from mailgun to mailtrap and got problem with standard devise's emails.
Particularly with "password restoration" email template.

I'm not 100% sure it's caused by mailtrap. But it seems like I didn't change anything else, except changing from one gem to another.

Hey!
Do you experience any issues with the emails you send via mailtrap?
There is a very similar question on stackoverflow.
But do let us know if you notice any functional defects (e.g. links do not work or content looks weird).

I think you're right about that. We really appreciate you sharing the results of your research. We'll discuss the problem in the team. Having said that, I can't promise any timeline.
Thanks again for the bug report. 🙇

@i7an How is this issue going in your team?
I'm having the same problem.

@jaedung As a quick fix, please try switching to SMTP.
I will get back to you within a week with further updates.
Thank you for understanding.

Hi @i7an
Thanks for your reply.
I've switched to SMTP and it works smoothly but hopefully I can see it fixed for later usage. Thanks!

@jaedung I think we will be able to deliver the fix within two weeks. I'll post an update when its ready Thanks!

The fix is on the way just delayed. I will keep you posted.

Hi,
After experimenting with possible options, we decided to mitigate the issue with a series of small fixes to our email sending service and documentation:

You will no longer see two Content-Transfer-Encoding headers in emails;
API documentation now explicitly states that Content-Transfer-Encoding header is ignored;
A new chapter is added to the README explaining how to deal with Content-Transfer-Encoding headers.

In short, please do not expect Mailtrap API to mirror all the features of the SMTP protocol. If you need your emails to be sent with a specific Content-Transfer-Encoding, consider switching to Mailtrap SMTP.
Thank you for your patience and sorry if your expectation were different 🙏
If you have a different opinion on this matter, please share it as we might consider implementing your suggestions.


fix(drag-drop): remove circular dependencies

Currently we've got the following circular dependencies in master, after the CdkDragDropRegistry got introduced:
drop.ts -> drag.ts -> drag-drop-registry.ts -> drop.ts
drag.ts -> drag-drop-registry.ts -> drag.ts
drop.ts -> drag-drop-registry.ts -> drop.ts

These changes rework the registry to avoid importing CdkDrag and CdkDrop, in order to break the circular references.

I've addressed the feedback @jelbourn.


Security: grafana 未授权访问

In GitLab by @luotian-github on Mar 10, 2020, 02:07
Security: grafana 未授权访问
See attachmentboard容器平台安全测试总结2.0.pdf

In GitLab by @tmon546596046 on May 27, 2020, 24:35
mr http://open.inspur.com/TechnologyCenter/board/merge_requests/2420 fix this issue

In GitLab by @tmon546596046 on May 27, 2020, 24:36
assigned to @luotian-github and unassigned @tmon546596046

In GitLab by @luotian-github on Aug 31, 2020, 06:30
removed milestone


Bump jquery version to 'current' version for 2019

Hi.
I noticed that hammer.js has a transitive dependency to jquery 2.2.1 through jquery.hammer.js.
This should fix it. I am not sure how we can check against regressions. Any idea?
It this PR works and jquery.hammer.js is published to npm and hammer.js updates its version of jquery.hammer.js this issue: https://github.com/hammerjs/hammer.js/issues/1138 can be solved I guess.
Hope I am not badly wrong.

@jtangelder are you still working on this? It has been rather quiet around hammer.js and its suprojects lately.


How to calculate the overall score?

It seems the overall score is not the average of the single task score, how to get it after all?

Found it!


[docs-infra] API generation imports issues

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Steps to reproduce 🕹
Link to live example:
Steps:

Current behavior 😯

Expected behavior 🤔
No response
Context 🔦
No response
Your environment 🌎

npx @mui/envinfo
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.

@mnajdova Do you confirm this issue is solved? I think it got solved by #38297 where I moved the generation of that info into the page data

https://mui.com/base-ui/react-autocomplete/hooks-api/

https://mui.com/base-ui/react-form-control/hooks-api/


Add data loader for CDC

This PR is an approach to loading CDC data, and works with all of the states they support. For the sake of making sure we get good quality matches, it limits its current output to locations where we know the store number. Later on, we may be able to expand the number of locations loaded when we have more Vaccines.gov UUIDs in our system (perhaps from VtS data).
Fixes #300

I'm not sure what we're going to do about trying to match these locations to existing locations in our database

I haven’t read through the code here yet, but my thoughts here were:

Start by only using locations that have the loc_store_no column filled in, and match those (requires parsing the loc_name column to figure out which store system it’s talking about, unfortunately).
Match up other, non store-number locations out of band and add their vaccines.gov GUIDs as external IDs manually. After that’s done, turn this on for all rows, not just those with loc_store_no.

The reverse (locations we’ve got but the CDC data set doesn’t) also shows some disparity we should investigate, but I don’t think is a blocker for this PR:
{
  cvs: 24,
  walgreens: 295,
  kroger: 15,
  publix: 26,
  costco: 2,
  safeway: 5,
  rite_aid: 2
}

Also, just realized I was probably not super clear last night on what I think needs to happen w/r/t the locations that looked problematic to me, so:

Nothing to do for the walgreens and publix ones. The disparity looks correct, so this loader will do the right thing.
The 5 safeway locations:

Need manual remediation in our DB before deploying this.
For the first one, the Vaccinespotter loader should also be amended to automatically set the right external ID and location name and provider, but as a separate PR from this.
Not sure there’s anything we can do in the Vaccinespotter loader for the other 4.

The 18 CVS locations should probably be hard-coded to not be public. I’m not 100% on that, though, and am curious what you think.

@Mr0grog thanks for all the feedback here. I trust your instincts on the CVS situation–seems like we can safely hide them for now.

@Mr0grog I think this is already to after we update the database. Here's the SQL I have planned:
INSERT INTO external_ids (provider_location_id, system, value) VALUES
 ('7bd930d2-2bce-4b47-bcf9-366c35797b13', 'safeway', '3125'),
 ('daeed1fd-ed16-4438-9a6c-b794f343a567', 'safeway', '414'),
 ('b70c960b-c6e5-4043-a1cd-c1a4e9cc5b28', 'safeway', '2248'),
 ('7d196a9e-c781-4fed-9705-22cebb3ec645', 'safeway', '469'),
 ('a4ba3ad1-f746-4945-983e-99b8100c26de', 'safeway', '186');

I'm thinking we just run it manually, but I can add a migration if you prefer.

That looks good to me. I think running it manually makes sense and is a good way to go. 👍

Oh, and I guess we'll need a quick follow-on to schedule this in Terraform. (1/day?)


fix(connectors): update import to work with esm

🔗 Linked issue
Resolves #62
❓ Type of change

[ ] 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
[x] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
Updated import statement for "pg" so that is works well with *.mjs files.
📝 Checklist

[x] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

May I ask when this PR is going to get merged?

can we merge this? need this in a project.

sorry for delay but i need further testing to see either prefer this or import * as syntax (i understand it fixes nitro builds)
in the meantime i suggest to use pnpm patch.

pi0 you have any updates or timeline for when you will look into this?

arg - sorry for accidental click

Hey what are the plans to release this ?

Any updates on this? Currently having issues with using pg in a nuxt3 project on the nitro side of things—same failure to import: "The requested module 'pg' does not provide an export named 'Client'"

Any updates on this? Currently having issues with using pg in a nuxt3 project on the nitro side of things—same failure to import: "The requested module 'pg' does not provide an export named 'Client'"

Based on what I've seen and read.
Yes, pg is unusable until this is fixed. But keep in mind that it is an experimental feature, so it probably has a low priority.
Especially since they are in the middle of releasing nitro 3.0, and nuxt is working on nuxt 4.0
Nitro 3.0 was planned for the middle of june or july, so pi0 is likely working that.

I also wanted to use db0 with postgres, but this is blocking me. @pi0 can you help a fellow Passionate Persion 😉

Thanks for fix PR and sorry it got this delayed. db0 was experimental and took less priority. it will get better attention.


Investigate optimized build setups (e.g. bundling/code-splitting/tree-shaking etc)

We should investigate optimized build setups for Effect CLI apps e.g. using bundling techniques that leverage code-splitting and tree-shaking on a per-command basis. e.g. printing the top-level help command shouldn't yet load all the code for the actual commands etc (see the Oclif docs).

closing as out of scope of Effect/cli that is purely a library and doesn't target specific build setups. This is already possible using dynamic imports if a user wants such behaviour


[enhancement]long press input number's trigger button

ElementUI version
1.0.0-rc.7
OS/Browers version
any
What is Expected?
when long press the input number's trigger button, it's better to repeat the action like every half seconds(or a configurable value).
What is actually happening?
Nothing happened after long press the minus or plus button.

Input number already has such feature. Working example: http://element.eleme.io/#/component/input-number .
If it doesn't work for you, please provide a demo.


Doc: Migration from standalone to integration plugin

Starts with @edmocosta's great work in #14 and expands it.
Design intent

The migration steps are necessary because of the new integration plugin that pulls in input-snmp and input-snmptrap.  The migration content is big news for now and needs to be super-obvious. For that reason, I recommend that we include the migration info in the integration topic and link to it from banners in the the component plugins.  We're no longer forced with a choice between adding heavy, "moment in time" content to the beginning of a topic where it will push down other content, OR add it to the end where it might be missed.

Note that distinguishing between old and new versions of the snmp inputs is tricky. I tried to be as precise as possible, and starting introducing language such as "preview version," "stand-alone," "next generation," and so forth. I'm bound to find more instances where we need to be more clear, but this is start. Comments on the terminology I'm using are always welcome.

Disclaimer: In order to validate structure and formatting, I had to mock up files because the integration plugin isn't generating doc files yet.  This hack makes it easy to obscure problems with formats and links, so hang on!

@edmocosta, thanks for your great work on this.  Let's discuss this approach and decide on next steps.
Fixes: #11

run docs-build

@edmocosta this work adds quite a few links and dependencies.  I'm wondering if it makes sense to generate docs, and then to follow on immediately with the migration guides. Let's discuss!  :-)

@edmocosta, thank you for your comments. I added your suggestion and committed another fix that got my mocked up files building.  🎉
As mentioned earlier,  my test files are mocked up "because the integration plugin isn't generating doc files yet. This hack makes it easy to obscure problems with formats and links, so hang on!"  We should be able to quickly resolve any glitches that come up when we merge and publish.
All that said... This content is ready to go. I believe you'd mentioned absorbing the contents of this PR into your branch? However you want to proceed works for me.  Please continue to keep me in the loop.

@edmocosta, thank you for your comments. I added your suggestion and committed another fix that got my mocked up files building. 🎉
As mentioned earlier, my test files are mocked up "because the integration plugin isn't generating doc files yet. This hack makes it easy to obscure problems with formats and links, so hang on!" We should be able to quickly resolve any glitches that come up when we merge and publish.
All that said... This content is ready to go. I believe you'd mentioned absorbing the contents of this PR into your branch? Or I can merge this one. However you want to proceed works for me. Please continue to keep me in the loop.

Thank you again @karenzone! could you please merge it? I'll update my branch later, no worries! :)


added: new variable to be able to disable the default behavior of wrapping draggable elements

Being able to disable this default behavior might come useful for some people (myself included). I'm using your script in an Angular 2 project, and I need to disable this feature to get everything working correctly.
So would be cool if we could add this feature if possible.

Made the requested changes.

Fixed

@webtrix can you squash the commits into the one named: added: new variable to be able to disable the default behavior of wrapping draggable elements?

Took me some searching but this OK?


[Docs]: Allow single-language blog without creating 404

Current State
Description of the current state/issue:
When submitting a pull request to add a new blog to the website's blog section, usually we need to submit 2 files, one in English and the other in Chinese.
As the community grows, blog in both languages are becoming more diverging than before. Thus, writing and submitting blogs in single-language is the trend.
But the actual behavior is that: when submitting an English blog, and clicking the language conversion button on the top-right corner, it would jump to the default 404 page. I am wondering if there is any chance to enhance the reading experience on this part.
Desired State
Description of the change you are proposing:

Submit a pull request with blog written in English or Chinese.
Visit the blog, and click language switch on the top right corner of the preview (or actual website page after it gets merged).
Stay on the same page.

Would you like to fix this issue?
No

@yzeng25 😀 Can you provide a link to an example?

@yzeng25 😀 Can you provide a link to an example?

Not really. When this issue was found, we did translations to fix it. The best way to reproduce it is to create a pull request and use the preview link to reproduce this issue.

Last year, we translated nearly all Chinese blogs to the English version, here is one PR[1].
@moonming I have one question: which language we will use on the Apache APISIX website? If most coming contents are only in Chinese, We will have the same problem as last year.
[1] https://github.com/apache/apisix-website/pull/659/files

@moonming @yzeng25 @SylviaBABY @nfrankel @Anita-ihuman @avinal @1502shivam-singh @sshniro @iamayushdas  Before reaching an agreement on this issue, I would insist on all Documentation PRs needed to contain the English version at least.

Back to this issue, we're building an i18n website, according to Docusaurus's Documentation[1], it will throw 404 if you switch a language without specific translation. Of course, we could prevent users from switching language, but:

We need to hack codes to Docusaurus, I don't want to do hacks or it's hard to update Docusaurus from upstream.
If I share a Chinese-only blog with Twitter, it will get 404 if people who don't speak Chinese switch a language.

[1] https://docusaurus.io/docs/i18n/introduction

IMO we should only be focusing on English blogs as we all know that the community is going global very fast so for that sake we should switch our content in english only from now. And also we should encourage other blog writers for english content as well.

We keep English contents by default here[1] and other languages contents here[2]. It's totally ok to submit one-language-only content to this repo (e.g Chinese only event/contents), then you need not focus on why it will throw 404. It's the default action from Docusaurus, and it's reasonable to have 404 because we don't have other language contents.
[1] https://github.com/apache/apisix-website/tree/master/website/blog
[2] https://github.com/apache/apisix-website/tree/master/website/i18n/zh/docusaurus-plugin-content-blog

To sum up the above the best solution is to deal with it as it is if we don't want to hack it and have upgrading problems in the future. Is it correct?

the best solution

I don't have the best solution here, and waiting fore more replies.

I think the language switch button can be removed and changed to "Chinese Blog". that's it

After removing the language switcher, what about Documentation in Chinese?

After removing the language switcher, what about Documentation in Chinese?

We can keep them in the archive for now, until we are sure that nothing is missing.

After removing the language switcher, what about Documentation in Chinese?

We can keep them in the archive for now, until we are sure that nothing is missing.

I am sure this will make Chinese readers upset.

After removing the language switcher, what about Documentation in Chinese?

Not removed, it's replaced.
All Chinese blogs will be on a separate page.
Chinese and English are completely independent blogs, so there is no language switch button, no 404 error.

All Chinese blogs will be on a separate page.
Chinese and English are completely independent blogs, so there is no language switch button, no 404 error.

@moonming Why not just mix them in one page? Like https://antfu.me/posts. Use tags to distinguish.
This will make the article look more, Users can also filter through specific language tags. :D

All Chinese blogs will be on a separate page.
Chinese and English are completely independent blogs, so there is no language switch button, no 404 error.

@moonming Why not just mix them in one page? Like https://antfu.me/posts. Use tags to distinguish.
It will make the number of articles look more, users can also filter through specific language tags. :D

We've had that months ago, it is a mess and just don't look right. So I would say no to this option.

it is a mess and just don't look right

Maybe just lack a good UI design :D

Hi @sshniro @iamayushdas @Yiyiyimu @SylviaBABY @Anita-ihuman @leslie-tsang @tokers @totemofwolf what do you think on this?

After reading the above replies, I think maybe we can do this:
Separate Chinese and English into two pages. From today, Chinese articles will no longer be translated, and only Chinese will be sent; English content will also be sent directly to English pages.
But this will cause the content of the output on both sides to be inconsistent, and what English readers see is different from that of Chinese readers; Of course, if readers use translation software to read by themselves, there is no problem, but it will take some extra time.
So I think Ming's opinion can be adopted, that is, all the current articles are directly divided into two pages in Chinese and English, and the subsequent articles can be published in the author's first language type (no translation required). But the folder structure of the website will adjust, don't know if it will affect other things.

I too agree with what @moonming Sir has said.
Separating the chinese and english blogs would be better for now.
@juzhiyuan

Personally, I would prefer to have a native speaker friendly docs rather than a precisely synchronised but poorly understood one.
Agree with @moonming , It will be better separating the chinese and english blogs for now. :)

+1 to @leslie-tsang 's comment. Users and contributors care more about the quality of the content.

We could notice that, what the official documentation of Docusaurus is supporting is that: it uses Crowdin, a volunteering out-sourcing translation platform to support i18n, and use this way to let the community contribute their own translation, so maintainers won't worry about that anymore. Another benefit of it is that it would fall back to the default language if another possible language is unsupported yet, so users could directly use translation tools to do their own work without seeing 404.
Two possible problems of it include that partial translation could be shown on the i18n page, which might make the translation tool confused (as you could see on ref 1), and also migrating our current i18n system to Crowdin could be tiring.
Ref:
[1] https://www.docusaurus.cn/blog/2022/01/24/docusaurus-2021-recap

any update？

@SkyeYoung would you have time to fix this issue?

@SkyeYoung would you have time to fix this issue?

Yes, I can give it a try.

After discussion with @moonming and @SylviaBABY , the following changes are needed for apisix-website:

Remove the Language Switch button from the top right corner of the page. Replace it with the "Blog/博客" button. This button will be displayed in the top right corner of the blog overview page and every blog page. Click this button to jump to the blog overview page in a language other than this one.
The url of each post cannot be changed.
Support separate English and Chinese content.
Submitting a PR with English blog only, the preview should show English blog content
Submitting a PR with Chinese blog only, the preview should show Chinese blog content
Submitting a PR with English and Chinese blogs, preview should show English blog and Chinese blog content

Just to make sure, do you mean remove the Language Switcher from ALL pages or ONLY Blog-related pages?
The navbar has already contained the Blog button, no need to add another one.
The url of each post cannot be changed.: any details?
After removing the language switcher, visitors will only see one specific language content, unless updating the URL manually.

Just to make sure, do you mean remove the Language Switcher from ALL pages or ONLY Blog-related pages?
ONLY Blog-related pages.

The navbar has already contained the Blog button, no need to add another one.
Consider it as a still a  Language Switch button, but only jumps to the blog summary page. This can avoid jumps to 404s when submitting a PR with one language contents.

The url of each post cannot be changed.: any details?
This is just in case when Docusaurus does not work out. If we were to switch to another framewor, say Hugo, I'd like to keep urls the same. Otherwise the SEO work we've done would be wasted.

After removing the language switcher, visitors will only see one specific language content, unless updating the URL manually.
This exactly what we want. cc @moonming

Consider it as a still a Language Switch button, but only jumps to the blog summary page. This can avoid jumps to 404s when submitting a PR with one language contents.

I accept this. But it's hard to remove / replace the locale dropdown without change the code of docusaurus. We can just change the behavior of locale dropdown in blog page.

Submitting a PR with English blog only, the preview should show English blog content
Submitting a PR with Chinese blog only, the preview should show Chinese blog content
Submitting a PR with English and Chinese blogs, preview should show English blog and Chinese blog content

This is a very time-consuming thing. I don't have time to do this until I solve the problem of construction speed.
IMO, I prefer to give a friendly tip 'help us translate' to users who need Chinese on 404 page.

I accept this. But it's hard to remove / replace the locale dropdown without change the code of docusaurus. We can just change the behavior of locale dropdown in blog page.

Sounds good.
We can ask others to help on the second part.

IMO, I prefer to give a friendly tip 'help us translate' to users who need Chinese on 404 page.

Agree. According to https://docusaurus.io/blog/2021/03/09/releasing-docusaurus-i18n, Docusaurus supports 3 ways to achieve i18n. We could support Crowdin.
Another thing is:

First, please clearly expect the problem to be solved.
Second, there are two categories of users for this site: visitors and contributors. So, whose problem is the current issue solving?
Finally, I would not recommend modifying the site until there is a consensus.

3. Finally, I would not recommend modifying the site until there is a consensus.

Agree, we need further discussion.


Not receiving event in Laravel Echo channel listener

Hi there,
I'm trying to setup Laravel + Redis + LaravelEchoServer. So far, I've got Laravel, Redis and the LaravelEchoServer setup. I can see the messages going to Redis and to LaravelEchoServer (printscreens below).
But the last step, logging the event in my browser console is not working.
Laravel Echo Server config:
{
    "appKey": "base64:somethingsecret123",
    "authHost": "http://test.virtual",
    "authEndpoint": "/broadcasting/auth",
    "clients": [
        {
            "appId": "TEST",
            "key": "AAAAABBBBBBCCCCCDDDDD"
        }
    ],
    "database": "redis",
    "databaseConfig": {
        "redis" : {
            "port": "6379",
            "host": "test.virtual"
        },
        "sqlite": {
            "databasePath": "/database/laravel-echo-server.sqlite"
        }
    },
    "devMode": true,
    "host": "<IP_ADDRESS>",
    "port": "6001",
    "protocol": "http",
    "socketio": {},
    "sslCertPath": "",
    "sslKeyPath": ""
}

My JavaScript:
import Echo from "laravel-echo"

window.Echo = new Echo({
    broadcaster: 'socket.io',
    host: 'http://<IP_ADDRESS>:6001/',
    auth: {
        headers: {
            'Authorization': 'Bearer ' + 'AAAAABBBBBBCCCCCDDDDD'
        }
    }
});

window.Echo.channel('examplec')
    .listen('examplee', (e) => {
        console.log('Got event...');
        console.log(e);
    });

My example event:
namespace App\Events;

use Illuminate\Broadcasting\Channel;
use Illuminate\Queue\SerializesModels;
use Illuminate\Broadcasting\PrivateChannel;
use Illuminate\Broadcasting\PresenceChannel;
use Illuminate\Broadcasting\InteractsWithSockets;
use Illuminate\Contracts\Broadcasting\ShouldBroadcast;

class ExampleEvent implements ShouldBroadcast
{
    use InteractsWithSockets, SerializesModels;

    /**
     * The event's data
     */
    public $data = [];

    /**
     * Create a new event instance.
     *
     * @return void
     */
    public function __construct($value)
    {
        $this->data['value'] = $value;
    }

    /**
     * Get the channels the event should broadcast on.
     *
     * @return Channel|array
     */
    public function broadcastOn()
    {
        return new Channel('examplec');
    }

    /**
     * Set the event name
     *
     * @return string
     */
    public function broadcastAs() {
        return 'examplee';
    }

}

And how I trigger the event:
event(new ExampleEvent('this is the value'));

Redis output (redis-cli monitor):

Laravel Echo Server output:

But nothing shows up in my browser console.
Is there something I'm doing wrong? I hope you can help me out here.
Thanks in advance.

Ahh, just found the fix! The event name needs to be prefixed with a dot.
window.Echo.channel('examplec')
    .listen('.examplee', (e) => {
        console.log('Got event...');
        console.log(e);
    });

Source: https://github.com/tlaverdure/laravel-echo-server/issues/73#issuecomment-258433496

Yeah not really sure why that is.
But usually they suggest to use the namespace like App.Example or something.
Also, you shouldnt add the key to your authorisation header, thats only for the HTTP subscriber.

Ok, thanks!

Same issue here, was working before and then suddenly stopped, adding . before event fixes it

This should be fixed

My issue (as many people above have found) is that I should use a custom broadcastWith name. If you state the event name, it is prefixed with 'App\Events\', but the events I was listening for were under 'App\Events\Dialer', which is a different namespace- hence the issue. I don't want to have to state the entire namespace every time I listen for an event, so I resorted to a custom name, prefixed with a period!

Install the Pusher
$ composer require pusher/pusher-php-server "~3.0"

Change in .env file
BROADCAST_DRIVER=pusher

Ahh, just found the fix! The event name needs to be prefixed with a dot.
window.Echo.channel('examplec')
    .listen('.examplee', (e) => {
        console.log('Got event...');
        console.log(e);
    });

Source: #73 (comment)

You saved my day!

Ahh, just found the fix! The event name needs to be prefixed with a dot.
window.Echo.channel('examplec')
    .listen('.examplee', (e) => {
        console.log('Got event...');
        console.log(e);
    });

Source: #73 (comment)

You saved my day!

I am trying from react js
import Echo from 'laravel-echo';
import Socketio from 'socket.io-client';
window.Echo = new Echo({
broadcaster: 'socket.io',
host: 'http://<IP_ADDRESS>:6001',
authEndpoint: '/broadcasting/auth',
client: Socketio,
auth: {
headers: {
'Authorization': Bearer ${localStorage.getItem('logintoken')},
},
},
});
window.Echo.channel('elxorders').listen('.orderhistory', (e) => {
console.log('okkkkkkkkkkkkkkkkkkkkkkkk');
console.log(e);
});
    After run this code from componentDidMount().
    Nothing showing. Anyone help me

I am trying from react js
import Echo from 'laravel-echo';
import Socketio from 'socket.io-client';
window.Echo = new Echo({
broadcaster: 'socket.io',
host: 'http://<IP_ADDRESS>:6001',
authEndpoint: '/broadcasting/auth',
client: Socketio,
auth: {
headers: {
'Authorization': Bearer ${localStorage.getItem('logintoken')},
},
},
});
window.Echo.channel('elxorders').listen('.orderhistory', (e) => {
console.log('okkkkkkkkkkkkkkkkkkkkkkkk');
console.log(e);
});
    After run this code from componentDidMount().
    Nothing showing. Anyone help me

@aleksandrssd same here


US 01.03.01

As an organizer, I want to send notifications to all attendees through the app.
Acceptance criteria

Send notifications to only the relevant attendees
Communicate to the user the nature of the notification (the purpose of the notification)

Unknown

The exact nature of the notifications (what are they for?)

Still need to be done, most likely will be through FirestoreCloudMessaging (FCM)


Add Gzip, make it default, and make Blosc optional

Codecov Report

Merging #12 into master will decrease coverage by 0.26%.
The diff coverage is 91.66%.

@@            Coverage Diff             @@
##           master      #12      +/-   ##
==========================================
- Coverage   95.02%   94.76%   -0.27%
==========================================
  Files           8        9       +1
  Lines         342      363      +21
==========================================
+ Hits          325      344      +19
- Misses         17       19       +2

Impacted Files
Coverage Δ

binpickle/codecs/__init__.py
81.25% <66.66%> (-9.66%)
:arrow_down:

binpickle/codecs/gz.py
100.00% <100.00%> (ø)

binpickle/write.py
96.39% <100.00%> (ø)

Continue to review full report at Codecov.

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


unresponsive server with guestbook example/vagrant

Following the current vagrant path with 19.3. I understand the pods should be reachable inside the vagrant boxes?
PETLAMAR-M-D113:kubernetes petlamar$ ./cluster/kubectl.sh get pods
NAME                 READY     REASON    RESTARTS   AGE
frontend-0pqjg       1/1       Running   0          24m
frontend-an48j       1/1       Running   0          24m
frontend-r4x1f       1/1       Running   0          24m
kube-dns-v3-g1be5    2/3       Running   4          33m
redis-master-hfyql   1/1       Running   0          26m
redis-slave-3rhvb    1/1       Running   0          24m
redis-slave-a34tq    1/1       Running   0          24m
PETLAMAR-M-D113:kubernetes petlamar$ vagrant ssh master
Last login: Tue Jun 23 19:01:51 2015 from <IP_ADDRESS>
[vagrant@kubernetes-master ~]$ kubectl get services
NAME           LABELS                                                                           SELECTOR            IP(S)           PORT(S)
frontend       name=frontend                                                                    name=frontend       <IP_ADDRESS>   80/TCP
kube-dns       k8s-app=kube-dns,kubernetes.io/cluster-service=true,kubernetes.io/name=KubeDNS   k8s-app=kube-dns    <IP_ADDRESS>     53/UDP
53/TCP
kubernetes     component=apiserver,provider=kubernetes                                                        <IP_ADDRESS>      443/TCP
redis-master   name=redis-master                                                                name=redis-master   <IP_ADDRESS>   6379/TCP
redis-slave    name=redis-slave                                                                 name=redis-slave    <IP_ADDRESS>   6379/TCP
[vagrant@kubernetes-master ~]$ curl <IP_ADDRESS>:80

Notification: Gateway Timeout

This Page Cannot Be Displayed

The system cannot communicate with the external server ( <IP_ADDRESS> ).
The Internet server may be busy, may be permanently down, or may be
unreachable because of network problems.

Please check the spelling of the Internet address entered.
If it is correct, try this request later.

If you have questions, or feel this is an error, please contact
your organization's network administrator
and provide the codes shown below.

Notification codes:
(1, GATEWAY_TIMEOUT, <IP_ADDRESS>)

well, according to my experience, they were never available inside vagrant boxes

In earlier versions, I could go 'inside' the cluster and curl the service to verify it was working. How does one do this on vagrant currently? The goal here is to verify the guestbook works with the latest vagrant up.

You can create the service for your frontend.
And you can then SSH into any minion and curl the internal service ip.
I am fixing some SkyDNS issues today on Vagrant setup, but will round back on this issue later today with full set of steps (and probably look to update the documentation).

Indeed, I was SSH into the minion and curling the internal service ip. It would be worth adding that to the docs as a trouble shooting option and I am happy to create the pull request.
In this particular case, that wasn't working and I suspect it was due to a separate issue. You just verified that these steps still should work which is good to know.

You would have needed https://github.com/GoogleCloudPlatform/kubernetes/pull/10562
I am now investigating this issue relative to that PR to see if there are any other issues.

Ok, I ran through the guestbook example, and verified that with #10562, I am able to curl the service ip address for the frontend from any minion in the cluster and get a response.

Hacking the Internet link of the collective computers in Colleges & increase the absolute reach of internet with occupied velocity.
http://www.hackingaccount.com/how-to-hack-internet-server-provider/


fix(celery): tasks now run correctly (if I'm not mistaken)

:tada: This PR is included in version 1.13.8 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Correction for raw affiliation Univ Rennes, CNRS, CREM-UMR 6211 , Condorcet Center for Political Economy , F-35000 Rennes , France

Correction needed for raw affiliation Univ Rennes, CNRS, CREM-UMR 6211 , Condorcet Center for Political Economy , F-35000 Rennes , France
raw_affiliation_name: Univ Rennes, CNRS, CREM-UMR 6211 , Condorcet Center for Political Economy , F-35000 Rennes , France
new_rors: 015m7wh34;02feahw73;0047rmf80
previous_rors: 015m7wh34;02feahw73
works_examples: W4318832666
contact: c580f1d8baf4042e4df352e84fc1eef1:8ba0b9517f3f98260c85195dc56c7ed3 @ univ-rennes.fr

This issue was accepted and ingested by the OpenAlex team on 2024-10-10. The new affiliations should be visible within the next 7 days.


Reduce startup times

For being able to scale more reactively, reduced startup times could help.
One way of achieving that could be to separate init and start phases.

to reduce the startup time even more, we might change the order in ZITADEL itself as well (listen before starting projections)
will have to check if possible

@eliobischof can this one be closed?

@eliobischof can this one be closed?

No. Added the question label and a better title and description.

@fforootd @livio-a
FYI, terraform-provider-google doesn't support cloud run jobs, yet.
https://github.com/hashicorp/terraform-provider-google/issues/11743

Hm, thats a bummer, in that case we need to think of something else 😁

Maybe we can run a cloud run job using the gcloud terraform provider https://github.com/terraform-google-modules/terraform-google-gcloud
@livio-a , when we deploy an init/setup job using a newer image tag, is the old revision still allowed to serve traffic during the job execution?

The old revision must serve traffic until the new is ready
IMO it might even make sense to then gradually swift traffic from the old to the new revision


Section with class combinations on home page disappeared

I just noticed the section with all the possible class combination disappeared. Did this information move elsewhere?
Thanks and loving beercss so far, keep up the good work guys :)

Hi @PotatoesFall ,
I have been received a lot of messages to improve de docs.
Now we are moving the docs to Github https://github.com/beercss/beercss/blob/main/docs/INDEX.md.
For me, that footer section was very helpful, for others not.
How about I rollback that footer?

Hey @leonardorafael ,
I thought the section was great, would love it if it comes back but I only just got started with beercss so don't take me as authority.
Is there a way to get the same information from the github docs?

I always liked the idea of the map with all helpers and elements. I think It's very helpful and easy to learn. I will do that soon.
All best!