RocketChat updater buttons don't work

My Setup

Operating System: Windows 10 Pro 1803 x64
App Version: 2.15.0 update to 2.15.1
Installation type: exe

[ ] I have tested with the latest version
[X ] I can simulate the issue easily

Description
Update pop-up appears, but cannot click on any buttons other than the x to close.
Current Behavior
Nothing
Expected Behavior
Update should install

Duplicate of #1141.


Custom directory for "pages"

[x] I have searched the issues of this repository and believe that this is not a duplicate.

I'd like to use a custom sub directory to store my "pages". I looked in the next.config.js but couldn't find any way of customizing it. Also, I found https://github.com/zeit/next.js/blob/07af67bfea3eb366c3b3457db9534d532d2e902b/server/build/webpack/utils.js#L4 which makes me thing it's not possible yet.
Is this something you intend to support?

It's not possible. And it's been discussed in other issues.
We're currently not planning to change it to be configurable.

We really should consider re-opening this.
Adding a variable to allow.
public/pages/
admin/pages/
So that we can have 2 directories of pages.

How is this not a thing?

Posted https://github.com/zeit/next.js/issues/8451


Searching Algorithms and Loop Detection in Single Linked List

Description
It lacked two important searching algorithms and also a method to detect loop in a single linked list
Fixes #370
Added
Please delete options that are not relevant

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] This change requires a documentation update

Checklist:

[x] I have read the contribution guidelines before making this PR.
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented in my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation (Language folder or any other readme instructed to)
[ ] My changes generates no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works

Without being assigned an issue, you can't PR. It is mentioned everywhere and you also received a message from bot regarding this.


botbuilder-adapter-facebook

Hi
The botbuilder-adapter-facebook module doesn't appear to fully work.  It sets up the webhook endpoint fine and validates OK with a Facebook App.  However after that no messages seem to be processed even with this basic code:
const { Botkit } = require('botkit')
const { FacebookAdapter } = require('botbuilder-adapter-facebook')
require('dotenv').config()

const adapter = new FacebookAdapter({
     verify_token: process.env.FACEBOOK_VERIFY_TOKEN,
     app_secret: process.env.FACEBOOK_APP_SECRET,
     access_token: process.env.FACEBOOK_ACCESS_TOKEN
})

const controller = new Botkit({
   webhook_uri: '/api/messages',
   adapter: adapter
})

controller.ready(() => {

    controller.hears('sample','message,direct_message', async(bot, message) => {
        await bot.reply(message, 'I heard a sample message.');
    });

    controller.on('message,direct_message', async(bot, message) => {
        await bot.reply(message, `Echo: ${ message.text }`);
    });

})

controller.webserver.get('/', (req, res) => {
    res.send(`This app is running Botkit ${ controller.version }.`);
});

This is with botkit 4.6.0 and botbuilder-adapter-facebook 1.0.6.  I've got a test project set up here : https://glitch.com/~fragrant-pansy
Is there a way I can output to console the Facebook communication to try and debug?  I can't see anything in the docs.
Microsoft is now recommending to use this module as the old approach is being deprecated so I'm a bit stuck.
Thanks.

Do you see traffic to the webhook at all?
You can turn on simple request tracking by passing in a middleware for the webserver, as seen here:
https://github.com/howdyai/botkit/blob/master/packages/testbot/bot.js#L146
Did you go through all the setup steps to enable the various webhook events?

Thanks for the middleware logging tip and coming back to me.
Yes I went through all the steps, thought I was going mad.  I think the issue was at the Facebook end - I created a new app exactly the same as before and it's now working.  I'll close the issue.  If this happens to anyone else I'd recommend creating a new app first to see if that resolves it.


Menubar: flicker on switch to full screen mode

VSCode Version: 1.26 Insiders
OS Version: Windows 10

During testing https://github.com/Microsoft/vscode/issues/55385
Steps to Reproduce:

Switch to Title Bar Style custom
F11 to go to full screen mode.

Notice a flicker and white line at the top of the menu bar.

Not surprisingly, also when going into Zen Mode.

@gregvanl please try to assign issues to owners when you create them. Since that test plan item was created by Steven I will assign this to him.

@gregvanl does this still repro for you? I was never able to see it on my machine.

@sbatten Yep, I still see it.


Setting up tox on ubuntu-24.04 runners fails

Github recently released their ubuntu-24.04 series runners. Using those results in an error because actions-operator tries to install tox globally with pip, rather than in a virtual environment.
See example failure here: https://github.com/canonical/parca-k8s-operator/actions/runs/10922157328/job/30315898232
Run charmed-kubernetes/actions-operator@main
Install core snap
Install LXD
Initialize LXD
Install tox
  /usr/bin/which tox
  /usr/bin/which pip
  /usr/bin/pip
  pip is available, install tox
  /usr/bin/pip install tox
  error: externally-managed-environment

  × This environment is externally managed
  ╰─> To install Python packages system-wide, try apt install
      python3-xyz, where xyz is the package you are trying to
      install.

      If you wish to install a non-Debian-packaged Python package,
      create a virtual environment using python3 -m venv path/to/venv.
      Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
      sure you have python3-full installed.

      If you wish to install a non-Debian packaged Python application,
      it may be easiest to use pipx install xyz, which will manage a
      virtual environment for you. Make sure you have pipx installed.

      See /usr/share/doc/python3.[12](https://github.com/canonical/parca-k8s-operator/actions/runs/10918199388/job/30304336943#step:3:13)/README.venv for more information.

  note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
  hint: See PEP 668 for the detailed specification.

@addyess are you still a maintainer on this?

For anyone reading, I solved this in zinc-k8s like so:

https://github.com/jnsgruk/zinc-k8s-operator/commit/e6f9a4599eaeb9e3e1cd25e75629d9e818420245
https://github.com/jnsgruk/zinc-k8s-operator/commit/e2efc4f5cc17be3a2af0f52589da74645daaf9ce

@jnsgruk precisely.  That's how it's expected to look

Hmm, seems the action is now stalled on setting up MicroK8s, though: https://github.com/jnsgruk/zinc-k8s-operator/actions/runs/10999695504/job/30540473863

@jnsgruk looking at sg -- maybe it now requires a password?
Mon, 23 Sep 2024 17:55:06 GMT   /usr/bin/bash -c sudo usermod -a -G snap_microk8s $USER
Mon, 23 Sep 2024 17:55:06 GMT   /usr/bin/sg snap_microk8s -c microk8s status --wait-ready --timeout=600
Mon, 23 Sep 2024 23:53:39 GMT   Password:
Mon, 23 Sep 2024 23:53:39 GMT   Error: The operation was canceled.

I recreated your issue in the CI for this project:
https://github.com/charmed-kubernetes/actions-operator/actions/runs/11006467708/job/30560799999?pr=83
the same issue with sg occurs both for microk8s and lxd... in either case the github runner session can't seem to get past an interactive prompt from from sg requesting the password be entered

This seems to be an upstream issue, which is closed but not solved.
Looks like one of our colleagues solved this by replacing instances of sg GROUP with sudo -u GROUP -E

Alright, that's applied but has ripples into pytest-operator
https://github.com/charmed-kubernetes/pytest-operator/issues/139

@jnsgruk thanks for highlighting this need.   #83 closes this issue

I think the way forward should be to swap out pip installation with pipx as #90 suggests. We should not be installing these dependencies on the system but use a separate environment for it. That is the intended purpose since noble and we should probably follow it.
GitHub provided runner images have this issue patched - their version of Noble image still allows pip installation without failure but we should follow our own decisions that the company has taken :)


[Bug]: Don't put comments in generated tsconfig.json

Which Remix packages are impacted?

[ ] remix (Remix core)
[X] create-remix
[ ] @remix-run/architect
[ ] @remix-run/cloudflare-workers
[ ] @remix-run/dev
[ ] @remix-run/express
[ ] @remix-run/netlify
[ ] @remix-run/node
[ ] @remix-run/react
[ ] @remix-run/serve
[ ] @remix-run/server-runtime
[ ] @remix-run/vercel

What version of Remix are you using?
latest
Steps to Reproduce

Generate a new project with: npx create-remix@latest
Choose TypeScript
Inspect the generated tsconfig.json file, it contains the following line:// Remix takes care of building everything in `remix build`.

Expected Behavior
Frustratingly, it is not valid to include comments in JSON files, according to the JSON spec. Some tools do support comments in JSON, but others don't. For me the ALE syntax engine that I use with VIM was not able to parse the comment, and therefore just silently ignored the tsconfig file. Unfortunately to achieve interoperability, comments should not be used in JSON files. The expected behaviour is therefore for the generated remix template to not include comments in the JSON files it generates.
Actual Behavior
The generated remix template DOES include comments in the tsconfig.json file it generates.

I mean... if you run tsc init it will create a tsconfig.json with more comments than actual code. This is expected and works properly.

@charlie632 that's unfortunate, but tsc is wrong in this case too. The JSON spec does not allow comments. Even Node's own JSON.parse does not accept comments, and the files generated by both tsc and remix cannot be parsed using it. If many/most JSON parsers cannot parse the file, then that is simply not correct.

TypeScript has it's own built-in JSON parser it uses for parsing tsconfig.json (require('typescript').parseJsonConfigFileContent().) Using the json5 package will also work. Though it is misleading that tsconfig.json has that extension and is not "valid" JSON, it doesn't look like that's going to change. See also Microsoft/TypeScript#12242.


Don't introduce GetAwaiter extension methods conflicting with Unity's Awaitable in 2023.1+

Overview
As Unity 2023.1 introduces await support for many constructs (including AsyncOperation), the package is running into compilation issues where there are ambiguous method calls when trying to resolve GetAwaiter method.
This PR makes disambiguate them by conditionally compile GetAwaiter extension methods depending on Unity Version
Changes

Fixes: #11171

Verification
I would be feeling much better about this PR if the CI ran tests with 2023.1 (2023.1.0a17 is publicly available and has the Awaitable support). There has been other API deprecations that may impact the package as well in addition to this.

Seems good to me! I ran some local tests on 2023 and was no longer able to repro this with your fix. Appreciate it!


[BUG] module 'fiftyone.utils' has no attribute 'coco'

System information

**windows and ubuntu
**FiftyOne installed from pip ( pip install fiftyone )
**Python version : 3.7

>>> import fiftyone
>>> dataset_dir = 'mydataset'
>>> fiftyone.utils.coco.download_coco_dataset_split(dataset_dir,split='train',max_samples=2000)
Uncaught exception
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
AttributeError: module 'fiftyone.utils' has no attribute 'coco'

`

Subpackages aren't automatically import when you just import fiftyone. Use this instead:
import fiftyone.utils.coco

fiftyone.utils.coco.download_coco_dataset_split(...)


Document differences between que-unique and que-locks

The que-unique gem performs job deduping, so is in a very similar space to another excellent gem que-locks.
In this issue I'll try to collect the differences, and add them to the README.

The que-unique gem performs its deduping in-memory, in one transaction, in a single thread. This means it is fast / has no IO overhead. It does mean, though, that if you have two concurrent transactions, they may both enqueue a job which needn't be run twice. The que-locks gem performs its deduping by asking the DB. This can help mitigate cross-transaction dupe enqueueing at the point of enqueue (though if the race is fast enough, some duplicate rows may make it through).

que-unique supports --worker-count greater than one. que-locks doesn't currently, but they may be looking into it.

que-unique does nothing to stop duplication once the rows are enqueued. que-locks does, by checking for duplicate rows and skipping duplicates where possible.

I believe the above means that the gems can work in tandem. At enqueue time que-unique can prevent "trivial" duplicates quickly in memory, then que-locks which can do a (/slightly/ more expensive) lower level DB check before the final insert. que-locks can then also perform post-enqueue deduping.
@airhorns do please chime in if that sounds right. @fameoflight this may be of interest.

Opened PR: https://github.com/bambooengineering/que-unique/pull/11


Reject case-insensitive name-collisions of public identifiers

Some of our target languages (for example Ruby) put restrictions
on what identifiers are legal in different contexts. For example,
classes and modules in Ruby should start with an upper-case letter.
Other languages (that we don't support yet) may put bigger restrictions,
like total case-insensitivity. That's why we decided that it is a
name collision for two public (currently non-locals only) identifiers
to differ only in case. For example:
    // Collision
    namespace foo {}
    namespace FOO {}

    // No collision, namespace is re-opened
    namespace qux {}
    namespace qux {}

    // Collision
    class bar {}
    class BAR {}

    void test() {
        // No collision
        int bar;
        int BAR;
    }

@rhs this is now merge-ready and passes tests


Sprite2Ds not rendering in specific scenes.

Tested versions
v4.3.stable.official [77dcf97d8]
System information
Godot v4.3.stable - Windows 10.0.19045 - Vulkan (Forward+) - integrated Intel(R) Iris(R) Xe Graphics (Intel Corporation; <IP_ADDRESS>72) - 11th Gen Intel(R) Core(TM) i7-1160G7 @ 1.20GHz (8 Threads)
Issue description
A simple scene with a root node of type Node2D and a single Sprite2D node, with no scripts and everything as the default setting, can sometimes not render the Sprite2D. I experienced multiple scenes in my project no longer render any Sprite2D nodes, and discovered that the problem remains when removing all other potential factors. In an MRP, this is the only scene in the project with everything as default.

The texture on the Sprite2D is assigned to the default icon.svg, and it does appear as if it should be rendered based on the texture preview in the inspector.

Yet in the editor, the Sprite2D is not rendered, and displays as such:

Running the scene will also not render the Sprite2D.
In my experiments, I discovered that changing "top level" to true in the inspector for the Sprite2D makes it render as expected, for some reason. Adding a Node as shown between the Sprite2D and the Node2D will also have this effect.

The only workaround I've found when this occurs is to just make a new, identical scene.
Steps to reproduce
Unfortunately, I don't know how to make this issue occur in a scene, it happened multiple times while I was editing some larger scenes with a variety of nodes and scripts. One thing that may or may not be relevant is that I was changing the type of a few nodes which were parents to multiple Sprite2Ds from Node2Ds to a custom node type I use which extends Node2D. I know very little about how the engine operates under the hood, but my best guess is that this is some sort of corruption of the scene, as making a new identical scene does not have the same issues. At any rate, I've attached my MRP below, perhaps it can be used to find the source of the problem.


Using --log-level info --force-logger duplicates line output

Heya Chefs,
I stumbled on this issue the other day when messing with Test Kitchen log output. It appears that when I ran Chef 11.12.8 (on the ubuntu:12.04 Docker image) in solo mode like this:
sudo -E chef-solo --config /tmp/kitchen/solo.rb --log_level info --force-logger --json-attributes /tmp/kitchen/dna.json

I saw duplicated logger output like the following:
[2014-07-25T14:45:40+00:00] INFO: Forking chef instance to converge...
[2014-07-25T14:45:40+00:00] INFO: Forking chef instance to converge...
[2014-07-25T14:45:40+00:00] WARN:
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
SSL validation of HTTPS requests is disabled. HTTPS connections are still
encrypted, but chef is not able to detect forged replies or man in the middle
attacks.

To fix this issue add an entry like this to your configuration file:

  # Verify all HTTPS connections (recommended)
  ssl_verify_mode :verify_peer

  # OR, Verify only connections to chef-server
  verify_api_cert true

To check your SSL configuration, or troubleshoot errors, you can use the
`knife ssl check` command like so:

  knife ssl check -c /tmp/kitchen/solo.rb

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

[2014-07-25T14:45:40+00:00] WARN:
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
SSL validation of HTTPS requests is disabled. HTTPS connections are still
encrypted, but chef is not able to detect forged replies or man in the middle
attacks.

To fix this issue add an entry like this to your configuration file:

  # Verify all HTTPS connections (recommended)
  ssl_verify_mode :verify_peer

  # OR, Verify only connections to chef-server
  verify_api_cert true

To check your SSL configuration, or troubleshoot errors, you can use the
`knife ssl check` command like so:

  knife ssl check -c /tmp/kitchen/solo.rb

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

[2014-07-25T14:45:40+00:00] INFO: *** Chef 11.12.8 ***
[2014-07-25T14:45:40+00:00] INFO: *** Chef 11.12.8 ***
[2014-07-25T14:45:40+00:00] INFO: Chef-client pid: 386
[2014-07-25T14:45:40+00:00] INFO: Chef-client pid: 386
[2014-07-25T14:45:42+00:00] INFO: Setting the run_list to ["recipe[git]"] from CLI options
[2014-07-25T14:45:42+00:00] INFO: Setting the run_list to ["recipe[git]"] from CLI options
[2014-07-25T14:45:42+00:00] INFO: Run List is [recipe[git]]
[2014-07-25T14:45:42+00:00] INFO: Run List is [recipe[git]]
[2014-07-25T14:45:42+00:00] INFO: Run List expands to [git]
[2014-07-25T14:45:42+00:00] INFO: Run List expands to [git]
[2014-07-25T14:45:42+00:00] INFO: Starting Chef Run for default-ubuntu-1204
[2014-07-25T14:45:42+00:00] INFO: Starting Chef Run for default-ubuntu-1204
[2014-07-25T14:45:42+00:00] INFO: Running start handlers
[2014-07-25T14:45:42+00:00] INFO: Running start handlers
[2014-07-25T14:45:42+00:00] INFO: Start handlers complete.
[2014-07-25T14:45:42+00:00] INFO: Start handlers complete.
[2014-07-25T14:45:42+00:00] INFO: Processing package[git] action install (git::default line 4)
[2014-07-25T14:45:42+00:00] INFO: Processing package[git] action install (git::default line 4)
[2014-07-25T14:45:44+00:00] INFO: Processing log[Well, that was too easy] action write (git::default line 7)
[2014-07-25T14:45:44+00:00] INFO: Processing log[Well, that was too easy] action write (git::default line 7)
[2014-07-25T14:45:44+00:00] INFO: Well, that was too easy
[2014-07-25T14:45:44+00:00] INFO: Well, that was too easy
[2014-07-25T14:45:44+00:00] INFO: Chef Run complete in 1.87953321 seconds
[2014-07-25T14:45:44+00:00] INFO: Chef Run complete in 1.87953321 seconds
[2014-07-25T14:45:44+00:00] INFO: Running report handlers
[2014-07-25T14:45:44+00:00] INFO: Running report handlers
[2014-07-25T14:45:44+00:00] INFO: Report handlers complete
[2014-07-25T14:45:44+00:00] INFO: Report handlers complete

Interestingly, when forcing chef-solo into non-interative mode (i.e. IO.tty? => false):
sudo -E chef-solo --config /tmp/kitchen/solo.rb --log_level info --force-logger --json-attributes /tmp/kitchen/dna.json | cat

then output was as expected:
[2014-07-25T14:49:40+00:00] INFO: Forking chef instance to converge...
[2014-07-25T14:49:40+00:00] WARN:
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
SSL validation of HTTPS requests is disabled. HTTPS connections are still
encrypted, but chef is not able to detect forged replies or man in the middle
attacks.

To fix this issue add an entry like this to your configuration file:

  # Verify all HTTPS connections (recommended)
  ssl_verify_mode :verify_peer

  # OR, Verify only connections to chef-server
  verify_api_cert true

To check your SSL configuration, or troubleshoot errors, you can use the
`knife ssl check` command like so:

  knife ssl check -c /tmp/kitchen/solo.rb

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

[2014-07-25T14:49:40+00:00] INFO: *** Chef 11.12.8 ***
[2014-07-25T14:49:40+00:00] INFO: Chef-client pid: 537
[2014-07-25T14:49:42+00:00] INFO: Setting the run_list to ["recipe[git]"] from CLI options
[2014-07-25T14:49:42+00:00] INFO: Run List is [recipe[git]]
[2014-07-25T14:49:42+00:00] INFO: Run List expands to [git]
[2014-07-25T14:49:42+00:00] INFO: Starting Chef Run for default-ubuntu-1204
[2014-07-25T14:49:42+00:00] INFO: Running start handlers
[2014-07-25T14:49:42+00:00] INFO: Start handlers complete.
[2014-07-25T14:49:42+00:00] INFO: Processing package[git] action install (git::default line 4)
[2014-07-25T14:49:44+00:00] INFO: Processing log[Well, that was too easy] action write (git::default line 7)
[2014-07-25T14:49:44+00:00] INFO: Well, that was too easy
[2014-07-25T14:49:44+00:00] INFO: Chef Run complete in 1.810070921 seconds
[2014-07-25T14:49:44+00:00] INFO: Running report handlers
[2014-07-25T14:49:44+00:00] INFO: Report handlers complete

I suspect this is either a bug or odd edge case combination of flags. Also note that this may very well include chef-client.
Thanks, as always

this seems to be fixed in 15.0.53, also fixed in 14.7.17 probably by #7698


Using wagtail with Jinja

That's not an issue but more like a proposal to extend documentation.
I've tried to integrate wagtail to the project where I'm already using jinja2 (via django_jinja lib).
That's how my Page model looking now:
class StaticPage(Page):
    body = RichTextField()
    template = "cms_pages/static_page.jinja"

    def get_context(self, request, *args, **kwargs):
        return {
            'page': self,
            'request': request,
        }

Key things here is to point to a specific template (with .jinja extension) because by default wagtail is using .html template which is rendered using django, not jinja.
Another thing is to use page instead of self as self is used by jinja to refer to it's own template object.
Hope this will help someone.

Hi @dchaplinsky we'd welcome you create a Pull Request to add help to the documentation on how to integrate with jinja2. Since this Github Issue isn't something we can resolve - rather it's just here for reference, I'll close it - the documentation is the best place for this.

@dchaplinsky did you manage to get wagtailimages_tags and the like to work with django_jinja?
I haven't had any luck so far. And since there is no load statement, I'm not sure how to do it.
Is this part of the context_processors or the extensions options?

@nilssolanki I just made some jinja2 extensions that might help you: https://github.com/minervaproject/wagtail-jinja2
It's my first time building extensions so all feedback is welcome.


[UI] Updated SVG system and compatibility with dark mode

Current Behavior
At present, we are using SVG scaling as defined here - https://github.com/meshery/meshery/blob/master/ui/css/icons.styles.js.
There are more icons that need to be updated with this system.
Desired Behavior
For custom icons (SVGs):

Each icon should have a primaryFill and secondaryFill property to make it darkMode friendly.

example - <DesignsIcon                primaryFill={theme.palette.lightDarkJungleGreen}                secondaryFill={theme.palette.superLightDarkJungleGreen}              />

Each SVG should have a default color that can be overridden according to need.

example - function SvgIcon({ color = "green", ...props }) {   					 return (   				 <svg viewBox="0 0 24 24" fill={color} stroke={color} {...props}>     <path d="M0 0h24v24H0z" fill="none" />   	 <path d="M12 2L2 7v10l10 5 10-5V7L12 2z" />     </svg>   		 )   		}
Usage - <SvgIcon color="blue" />

All the icons should be updated with the existing SVG system.

Acceptance Tests
SVGs should be working fine on all browser types.

Contributor Guides and Handbook

🎨 Wireframes and designs for Meshery UI in Figma
🖥 Contributing to Meshery UI
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

@leecalcote I'd like to work on it. please assign it to me.

Hey @vishalvivekm can i work on this issue ? if issue is in stale state

Hey @vishalvivekm can i work on this issue ? if issue is in stale state

First, Let's ask @MdSahil-oss about his progress on the issue.
@MdSahil-oss any update?

@duckling69 Yes, you can work on it, I haven't made any progress yes because of other on going stuffs.

@duckling69 Yes, you can work on it, I haven't made any progress yes because of other on going stuffs.

In which case, @duckling69 you've the green-light 🚀

@vishalvivekm I'd need a little guidance here

first the issue : can you confirm if the issue is asking me to update system by implementing following function or I just need to update the SVGs according to what issue says and that existing system already have these functions
and if i need to update all SVGs according to this system am i supposed to give it secondary color according to what i think is the best or do I need to follow some rules

@vishalvivekm I'd need a little guidance here

first the issue : can you confirm if the issue is asking me to update system by implementing following function or I just need to update the SVGs according to what issue says and that existing system already have these functions
and if i need to update all SVGs according to this system am i supposed to give it secondary color according to what i think is the best or do I need to follow some rules

Please refer to the discussion on the issue in the Dev Call of May 26th: link
If you still have any doubts, feel free to post them here in discuss forum @duckling69

@duckling69 how's this coming along?

if nobody is currently working on it, can you assign me this issue?

if nobody is currently working on it, can you assign me this issue?

Sure you can go ahead with this 🚀

@ranjanmangla1, progress check...

@thisiskaransgit, almost every png has ben converted to svg, 2-3 files of meshery logo are remaining, resta re complete.
I think i may not be able to convert this imagae to svg:


Add InternalAffairs/NodeFirstOrLastArgument cop

This cop checks for node.arguments.first and node.arguments.last, and corrects them to node.first_argument and node.last_argument, respectively.
Motivation for rubocop/rubocop-ast#270.

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
~Commit message starts with [Fix #issue-number] (if the related issue exists).~
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[x] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

Can you squash your commits into one?

Seems we were quite consistent even before this change, but I don't mind it. Thanks!


False positive vulnerabilities reported

Dear Team,
After detailed investigation for Docker container vulnerabilities reported under https://github.com/microsoft/openjdk-docker/issues/113 - it appears that ones with severity critical and high were actually detected towards krb5 package, and in fact are resolved.
When we look at discovered CVE https://nvd.nist.gov/vuln/detail/cve-2024-37371 - NVD provides solution with higher version as mentioned "In MIT Kerberos 5 (aka krb5) before 1.21.3".
When we check details this specific CVE have been already resolved in patches mentioned by @d3r3kk in https://github.com/microsoft/openjdk-docker/issues/113#issuecomment-2471534617.
The challenge is security scanners compare package version from NVD:
Known Affected Software Configurations
Up to (excluding)
1.21.3
to system level package version hence still this CVE is discovered because Mariner used "patched release", not version, to resolve issue:
Version       : 1.19.4
Release       : 3.cm2
Is this approach of having custom release versions of system package a standard approach for Mariner, or we can expect soon Mariner to have krb5 version bumped to be aligned with official one, which has this CVE resolved.
We are trying to understand how to investigate container security reports without custom rules for Mariner based images, per each CVE that is fixed but cannot be automatically discovered.
Regards
Jan

Any update on this please?

We're working with scanning vendors to get this false positive corrected. You're right in that it's patched already, but it may take some time for the tooling to resolve correctly.


Update mysql since it would terminate on startup

Default mysql image somehow terminates on startup, updating it fixed it.

Worked for me

Closing because this PR is sitting unaddressed in my open PR box for 2 years now.


Confusing error message when providing an invalid combination of causality and variability

The following error message is generated when providing an invalid combination of causality and variability. I interpreted this as a type cast failure from string to the FMU variability enum when it actually means that the variability and causality is invalid according to the FMI standard.
The error message should reflect that it is the invalid combination of causality and variability that is the issue.

Cause by a typo i continous. Correct typing provides a good error message


filament backend not support compute shader feature

filament backend not support compute shader feature. And some function not support, for example, i use opengl bindImageTexture() function,it call 'calling missing GL function!'.

Filament supports the OpenGL ES 3.0 feature set so there is no support for compute shaders indeed. We don’t have plans to address this until ES 3.0 phases out or we can rely only on Vulcan and Metal.

If I want to implement this function in OpenGL, how to solve the problem that the GL function can’t find it，just 'calling missing GL function!'

It depends on the platform. On desktop you’ll have to update the bluegl library. On Android it should just work if you include es 3.1 headers.

Thanks, yeah, I want  implement for macos platform , Can it done?

Can I ask you a question? When I use compute shader, program compile success contains a uniform variable, such as layout (rgba32f, binding = 0) uniform image2d outputimage. When I use glgetuniformlocation() method to access the variable, it prompts invalid gl operation. What is the reason？ it not support？Thanks


ClamAV flags a virus within Bookstack test-data

Describe the bug
I ran a system scan with ClamAV today and the scan result flagged two files in this app as trojans. Can someone explain why this is happening?
/var/www/bookstack/tests/test-data/bad.php: Win.Trojan.Hide-2 FOUND
/var/www/bookstack/tests/test-data/bad.phtml: Win.Trojan.Hide-2 FOUND

----------- SCAN SUMMARY -----------
Known viruses: 6519624
Engine version: 0.101.4
Scanned directories: 77309
Scanned files: 378698
Infected files: 2
Data scanned: 13175.25 MB
Data read: 24070.79 MB (ratio 0.55:1)
Time: 4384.826 sec (73 m 4 s)

Steps To Reproduce
Steps to reproduce the behavior:

Run a virus scan with ClamAV on your web server.

Your Configuration (please complete the following information):

BookStack v0.27.5
PHP Version: 7.2.24
Hosting Method: Apache

My first search of this thread didn't turn up any previous issues opened for this, but I later found this https://github.com/BookStackApp/BookStack/issues/1571 was already open for the topic.
I have also deleted these two files from my server, and will monitor that issue for a solution.


Master -> Live

Docs Build status updates of commit 2efda63:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/community.md
:white_check_mark:Succeeded
View

mixed-reality-docs/hand-menu.md
:white_check_mark:Succeeded
View

mixed-reality-docs/images/BiographyImages/DanielEscudero_270x270.jpg
:white_check_mark:Succeeded
View

mixed-reality-docs/install-the-tools.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mrtk-porting-guide.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Patches in imagery

I have tried to put up most basic level with cesium3dtileset actor with two raster overlay component and cesiumsunsky. I have tried to adjust solar time and time zone suitable. When I play it is showing the patches in the globe imagery. Can anyone from community please guide me with this issue?
I have tried to adjust maximum screen space error default 16 to 2. In that can it is not showing patches. But its is taking too much time to load.

Hi @ankitpentashield,
Could you share more information with us, including:

What version of Unreal Engine are you using?
What dataset is this -- Cesium World Terrain? Google Photorealistic 3D Tiles? Do you see this happen on both tilesets, or only one?
Could you try using the Dynamic Pawn instead? We don't offer a Globe Pawn option in the menu, perhaps you're using a modified version of the plugin?

I am using Unreal 5.3.2 with latest cesium plugin build from screen-space-controller branch I have tried using the dynamic pawn but issue still persist. Regarding the data I am using preprocessed and tiled data downloaded from cesium ion for offline serving and I am using earth emagery from luciad

I am encountering a similar issue. When I zoom out, the terrain appears to be "patchy". I am using the Google Photorealistic 3D tiles in Unreal 5.4.

@ankitpentashield can you please check if you're able to reproduce this problem in an official release of the plugin? It's hard to say what bugs might be lurking in a work-in-progress branch like screen-space-controller.

@Apollo199999999 I can't say for sure, but your screenshot looks like you possible have multiple tilesets displaying on top of each other, for example both Cesium World Terrain and Google Photorealistic 3D Tiles. Is that a possibility?

Please see #1530 for an explanation and fix for this issue.

I see, thanks for the quick response.


Convert ember-cli-babel to dev dependency

ember-cli-babel is only needed as a prod dependency if there are files in the addon folder, which is not the case here. This PR converts it to a dev dependency so that the (empty) dummy app is still built correctly.
/cc @san650

rebased on top of #4

@Turbo87 That was quick 😄
Thanks!

This PR converts it to a dev dependency so that the (empty) dummy app is still built correctly.

I saw this PR after the other, sorry about that. I'll release a major version today EOD.
Thanks for contributing!!


Answer question

Been dropping a Uiua link for some discussions about stack-based array languages on the APL Farm lately, hope that's okay!

Yep, no worries!
I'm surprised you even found this repo.


L920 color change issues

Version of the integration

1.4.0
Configuration

L920-5 HW 1.0, FW 1.0.9
Describe the bug
Unable to change the strip color by using the color wheel of the entity. Brightness instead is working properly.
It’s my first time with this integration, cannot say if with older versions it worked.
Even with a python command like:
service_data = {'entity_id': entity_id, 'rgb_color': rgb_color, 'brightness': 255 }
it doesn’t work.

Same here, color changing of the L920 via the color wheel or via script calls was broken with the upgrade to v1.4.0.
if you downgrade back to v1.3.8 all is working again

Same here but with a different device.
I think this is bug is affecting several lights at the color feature. I have a "Smart WiFi Light Bulb Multicolor" (L530, not sure if B or E) and color setting stopped working with the last version. Can't see any error in the logs.
Going back to 1.3.8 also fixed it for me.

Same here, RGB and colour temperature change is no longer is working with the TP Link L530 bulb on:
Firmware: 1.0.9,
Build 220526 Rel.203202
Hardware: 2.0.
The functionality is working in v1.3.7, and not working in v1.4.0, so for the time being I have rolled back.

Same on L530.
It was fixed but broke again.
Gone back to 1.3.6 to get it working

Can confirm I am also having this issue with L530 colour wheel not setting the light colour.

+1 with the issue of the L530 color issue (v1.4.0)

+1 on L530

v 1.6.1
There is no option to change colors. There are no problems with effects. And the color is only white and you can only change the brightness. It does not change from the interface, I tried to send it manually through the services - it also did not give results. What am I doing wrong? The latest tape firmware is 1.0.9 Build 220422 Rel.150004.

https://user-images.githubusercontent.com/15996927/230762636-eecfa569-e5d3-4f49-b059-3ba21d491644.mp4


Support jsx pragma for custom components

I think I know how this could work, but I have to look into the theme ui code to be sure.
The hurdle is that we need to hook into the component, not just pass a raw className prop.

https://github.com/emotion-js/emotion/blob/master/packages/babel-plugin-jsx-pragmatic/src/index.js

This would be a cool feature. I can definitely try to help with this.
I'm not 100% sure how the theme-ui-native repo did it but it seemed like it just wrapped the components with a ThemeProvider. There's was working last time a played around with that repo not sure if that strategy would work for dripsy but it might be worth a shot looking at it.

All we would really need to do is wrap the function with createThemedComponent. If that's possible, this should be pretty smooth.

That seems like the move.
On another note is it possible to remove styled-components as a dependency now that we have fresnel? Emotion seems like it's doing most of the heavy lifting style wise as a dependency to theme-ui.

https://github.com/emotion-js/emotion/blob/master/packages/core/src/jsx.js (the original emotion file)

On another note is it possible to remove styled-components as a dependency now that we have fresnel? Emotion seems like it's doing most of the heavy lifting style wise as a dependency to theme-ui.

Yeah, I believe I removed that as a dependency in the fresnel branch, but if I forgot, let's get rid of that.

https://github.com/microsoft/TypeScript/pull/38720 relevant for custom pragmas, heard through: https://devblogs.microsoft.com/typescript/announcing-typescript-4-0-rc/#custom-jsx-factories

I'll try to get a PR for this created with in the next day or two. I think it should be relatively simple. I'll also take a look through that typescript article you sent over.

That's great!
I believe the TS article helps with the Fragment. Not sure if you've run into this with theme-ui, but its pragma doesn't let you use <> React fragments which is a pain.

Yeah, I have it's a pain.

Babel plug-in: https://github.com/emotion-js/emotion/blob/master/packages/babel-plugin-jsx-pragmatic/README.md


Keep session

Make IYO to keep session.
Its too much annoying to relogin several times per day.
You can set default 5 days.
And add ability to change in settings.

While it is indeed annoying that you might need to log in multiple times per day, especially with the sms, It should be noted that there having an extended active session is not secure. If we keep the session active for 5 days, then we might as well remove 2FA all at once. Keeping the session open would also mean that users will have multiple sessions open i.e. one on their pc in the browser, on on their mobile (this is one is a huge security hole), ...


Can I estimate only single person?

Can I extract only 1 person's keypoint?

Hi! You can use only pose with the highest confidence.

Thank you! it works very well
But If I want to extract single person's keypoints heatmap, I need to fix network architecture?

You can leave network architecture as is. However for this task you need just annotations for 1 person in dataset. You can assign an empty list in the label['processed_other_annotations'] for this.

Can I just delete below lines in coco.py and run train.py?
for another_annotation in label['processed_other_annotations']:                 keypoint = another_annotation['keypoints'][keypoint_idx]                 if keypoint[2] <= 1:                     self._add_gaussian(keypoint_maps[keypoint_idx], keypoint[0], keypoint[1], self._stride, self._sigma)
 for another_annotation in label['processed_other_annotations']:                 keypoint_a = another_annotation['keypoints'][BODY_PARTS_KPT_IDS[paf_idx][0]]                 keypoint_b = another_annotation['keypoints'][BODY_PARTS_KPT_IDS[paf_idx][1]]                 if keypoint_a[2] <= 1 and keypoint_b[2] <= 1:                     self._set_paf(paf_maps[paf_idx * 2:paf_idx * 2 + 2],                                   keypoint_a[0], keypoint_a[1], keypoint_b[0], keypoint_b[1],                                   self._stride, self._paf_thickness)

Yes, you can.

Ok, I try it. Thank You!

Ok, closing.


[Issue 618]Supported Spark 1.6 in Carbondata

Spark 1.6 changes approach of aggregation and changed the interfaces.  So all old implementations need to be either rewritten or deleted in this PR.
MeasureAggregator object is no longer supported in Spark 1.6 as UDT. As Spark 1.6 is completely based on UnSafeRow and codegen. So it try to read only the sqlType of UDT.
So approach is changed to avoid usage of  MeasureAggregator objects in Spark side aggregation.
Distinct aggregation like count-distinct or sum-distinct is no longer supported to push down to spark layer. Spark changes the plan completely to support distinct count in its way, so carbon cannot get a chance to push down distinct aggregation.
Interface identification and cleanup would be done another PR

I am not sure, to which branch this PR can be merged? Should be merged to master or new branch or westlake? @jackylk Please help me.

@ravipesala I think carbon-spark integration module should provide spark 1.6 integration support as it can be directly used by community users who is running on spark 1.6. So I incline to merge it to master.

This would be possible if u have separate modules /packages for 1.5.2 and
1.6
We should be able to compile using Pom profiles
Else merging to master would fail 1.5.2
On Sun, 12 Jun 2016 at 9:25 AM, Jacky Li<EMAIL_ADDRESS>wrote:

@ravipesala https://github.com/ravipesala I think carbon-spark
integration module should provide spark 1.6 integration support as it can
be directly used by community users who is running on spark 1.6. So I
incline to merge it to master.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/HuaweiBigData/carbondata/pull/624#issuecomment-225408675,
or mute the thread
https://github.com/notifications/unsubscribe/ACxx7zMnej7zyy0ix1oBXBj7M6m7Fccsks5qK4M0gaJpZM4IzQ3v
.

@ravipesala , can we have support for both 1.5 and 1.6 as separate build options similar to how Spark supports different versions of Hadoop.

@Vimal-Das There is a difference in Spark supporting different versions of Hadoop comparing to carbon supporting different versions on Spark.
Hadoop client library is standard and interfaces won't change and they make sure the backward compatability with old client libraries. That's why spark can just change the hadoop jar version while building would be enough.
But when it comes to Carbon, we are not just using the standard spark client interfaces it has very deep integration to the spark sql layer.
I guess we may have following two solutions.

Make the current code to branch as spark 1.5 and push the spark 1.6 to the master. So if user wants to use spark 1.5 then they need to take from branch.
Cons : Defect fixes need to keep sync between both branches
The changed classes/interfaces need to be maintained in separate module or just a package inside integration/spark module. Pick the right version package while building using maven. But extracting the changed classes or interfaces  is not so simpler or cleaner.
Cons : Version to version interfaces changes are maintained different packages are not a good way. And also for spark 2.0 it would be a major change and not possible to do in this way.


Selectively disabled link for citations

As discussed during the meeting, the css selector successfully identified the links specifically for paper citations and disabled them. When the mouse hovers a citation, only the purple highlight is displayed, and when a citation is clicked, the citation tooltip appears.
Screenshot:

@jocelynzsun Can you also add a GIF showing that the links for equations and figures still work?

GIF for links other than citations:

GIF for symbol annotations (a bit slow):


Fix CI broken requirements

Codecov Report

Merging #42 (f33e0ba) into main (6107b0a) will decrease coverage by 14.13%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             main      #42       +/-   ##
===========================================
- Coverage   93.51%   79.37%   -14.14%
===========================================
  Files          11       11
  Lines         771      771
===========================================
- Hits          721      612      -109
- Misses         50      159      +109

Impacted Files
Coverage Δ

aiohttp_pydantic/oas/__init__.py
41.17% <0.00%> (-58.83%)
:arrow_down:

aiohttp_pydantic/oas/view.py
54.20% <0.00%> (-43.00%)
:arrow_down:

aiohttp_pydantic/view.py
68.05% <0.00%> (-26.39%)
:arrow_down:

aiohttp_pydantic/oas/typing.py
80.95% <0.00%> (-19.05%)
:arrow_down:

aiohttp_pydantic/injectors.py
80.66% <0.00%> (-15.34%)
:arrow_down:

aiohttp_pydantic/oas/docstring_parser.py
97.75% <0.00%> (-2.25%)
:arrow_down:

aiohttp_pydantic/oas/struct.py
88.84% <0.00%> (-2.07%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


weird search result

given a customer
Customer.create(address_street_name: "Bjælkevej", address_street_number: "44", rec_id: "kj3")

I get these seacrh results
Customer.search "jælkevej", star: true, ranker: :bm25, with: { deleted_at: 0 }, page: 1, per_page: 15
  Sphinx Query (0.6ms)  SELECT * FROM `customer_core`, `customer_delta` WHERE MATCH('*jælkevej*') AND `deleted_at` = 0 AND `sphinx_deleted` = 0 LIMIT 0, 15 OPTION ranker=bm25
  Sphinx  Found 0 results

Customer.search "ælkevej", star: true, ranker: :bm25, with: { deleted_at: 0 }, page: 1, per_page: 15
  Sphinx Query (0.6ms)  SELECT * FROM `customer_core`, `customer_delta` WHERE MATCH('*ælkevej*') AND `deleted_at` = 0 AND `sphinx_deleted` = 0 LIMIT 0, 15 OPTION ranker=bm25
  Sphinx  Found 1 results
  Customer Load (0.4ms)  SELECT "customers".* FROM "customers" WHERE "customers"."id" = 2
 => [#<Customer id: 2, address_city_name: nil, address_country_name: nil, name: nil, name_alias: nil, phone: nil, rec_id: "kj3", address_street_name: "Bjælkevej", address_street_number: "44", address_zip_code: nil, created_at: "2015-08-08 16:03:58", updated_at: "2015-08-08 16:03:58", address_additional_info: nil, street: nil, delta: true, imported_at: "2015-08-08 16:03:58", deleted_at: nil, email: nil>]

THIS IS MY INDEX
# -*- encoding : utf-8 -*-
ThinkingSphinx::Index.define :customer, :with => :active_record, :delta => ThinkingSphinx::Deltas::DelayedDelta do
  indexes name, as: :customer_name, infixes: true, sortable: true
  indexes name_alias, as: :customer_name_alias, infixes: true, sortable: true
  indexes [address_street_name, address_street_number, address_additional_info, address_zip_code, address_city_name, address_country_name, street], as: :customer_address, infixes: true, sortable: true
  indexes rec_id, as: :customer_rec_id, infixes: true, sortable: true
  has deleted_at
  set_property :enable_star => true
  set_property :min_infix_len => 1
  set_property :html_strip => true
  set_property :charset_type => "utf-8"
end

I'm not really sure why this is happening… which versions of Thinking Sphinx and Sphinx are you using? And what settings do you have for this environment in config/thinking_sphinx.yml?

Yes very strange. It works on circleci , but not in development, so i guess
its my local version of sphinx?
VERSION
sphinx: stable 2.2.9 (bottled), devel 2.3.1-beta, HEAD
YML
development:
mysql41: 9312
enable_star: true
min_infix_len: 3
FAILING TEST
context "GET index", focus: true do
let!(:customer_a) { create(:customer, address_city_name: "København",
address_country_name: "Danmark", name: "Kjeld Fanøgræs", name_alias:
"Kikært", phone: "123456", rec_id: "777777777", address_street_name:
"Bjælkevej", address_street_number: "44", address_zip_code: "1234",
address_additional_info: "4 th v", street: "Bjælkevej 34, 4 th v" )}
let!(:customer_deleted) { create(:customer, address_city_name:
"København", address_country_name: "Danmark", name: "Kjeld Fanøgræs",
name_alias: "Kikært", phone: "123456", rec_id: "77777777743",
address_street_name: "Bjælkevej", address_street_number: "44",
address_zip_code: "1234", address_additional_info: "4 th v", street:
"Bjælkevej 34, 4 th v" )}
let!(:customer_b) { create(:customer, address_city_name: "Odense",
address_country_name: "Danmark", name: "Bingo børge", name_alias: "bimmer",
phone: "987987", rec_id: "76487648", address_street_name: "skistien",
address_street_number: "2", address_zip_code: "5000",
address_additional_info: "", street: "Skistien 2" )}
before :each do
  customer_deleted.destroy
  index_sphinx
end

[
  { attribute: :name, q: "anøg" },
  { attribute: :address_city_name, q: "nha" },
  { attribute: :name_alias, q: "ikær" },
  { attribute: :rec_id, q: "777777777" },
  { attribute: :address_street_name, q: "jælk + 44" }
].each do |h|
  it "should be able to search on customers.#{ h[:attribute] }" do
    authorize_request

    get :index, { q: h[:q], format: :json }

    expect(assigns(:customers)).to include(customer_a)
    expect(assigns(:customers)).to_not include(customer_deleted)
    expect(assigns(:customers)).to_not include(customer_b)
  end
end

end
WORKING TEST
context "GET index", focus: true do
let!(:customer_a) { create(:customer, address_city_name: "København",
address_country_name: "Danmark", name: "Kjeld Fanøgræs", name_alias:
"Kikært", phone: "123456", rec_id: "777777777", address_street_name:
"Bjælkevej", address_street_number: "44", address_zip_code: "1234",
address_additional_info: "4 th v", street: "Bjælkevej 34, 4 th v" )}
let!(:customer_deleted) { create(:customer, address_city_name:
"København", address_country_name: "Danmark", name: "Kjeld Fanøgræs",
name_alias: "Kikært", phone: "123456", rec_id: "77777777743",
address_street_name: "Bjælkevej", address_street_number: "44",
address_zip_code: "1234", address_additional_info: "4 th v", street:
"Bjælkevej 34, 4 th v" )}
let!(:customer_b) { create(:customer, address_city_name: "Odense",
address_country_name: "Danmark", name: "Bingo børge", name_alias: "bimmer",
phone: "987987", rec_id: "76487648", address_street_name: "skistien",
address_street_number: "2", address_zip_code: "5000",
address_additional_info: "", street: "Skistien 2" )}
before :each do
  customer_deleted.destroy
  index_sphinx
end

[
  { attribute: :name, q: "anøg" },
  { attribute: :address_city_name, q: "nha" },
  { attribute: :name_alias, q: "ikær" },
  { attribute: :rec_id, q: "777777777" },
  { attribute: :address_street_name, q: "ælk + 44" }
].each do |h|
  it "should be able to search on customers.#{ h[:attribute] }" do
    authorize_request

    get :index, { q: h[:q], format: :json }

    expect(assigns(:customers)).to include(customer_a)
    expect(assigns(:customers)).to_not include(customer_deleted)
    expect(assigns(:customers)).to_not include(customer_b)
  end
end

end
INDICES
-- encoding : utf-8 --
ThinkingSphinx::Index.define :customer, :with => :active_record, :delta =>
ThinkingSphinx::Deltas::DelayedDelta do
indexes name, as: :customer_name, infixes: true, sortable: true
indexes name_alias, as: :customer_name_alias, infixes: true, sortable:
true
indexes [address_street_name, address_street_number,
address_additional_info, address_zip_code, address_city_name,
address_country_name, street], as: :customer_address, infixes: true,
sortable: true
indexes rec_id, as: :customer_rec_id, infixes: true, sortable: true
has deleted_at
set_property :enable_star => true
set_property :min_infix_len => 1
set_property :html_strip => true
set_property :charset_type => "utf-8"
end
GEM LIST
actionmailer (4.2.0)
actionpack (4.2.0)
actionview (4.2.0)
activejob (4.2.0)
activemodel (4.2.0)
activerecord (4.2.0)
activesupport (4.2.0)
acts_as_list (0.6.0)
addressable (2.3.7)
afm (0.2.2)
akami (1.2.2)
amoeba (3.0.0)
ancestry (2.1.0)
apipie-rails (0.3.1)
arel (6.0.0)
Ascii85 (1.0.2)
ast (2.0.0)
astrolabe (1.3.0)
bcrypt-ruby (3.1.2)
bitmask_attributes (1.0.0)
brakeman (3.0.1)
builder (3.2.2)
bullet (4.14.4)
bundler (1.7.6)
cancancan (1.10.1)
carrierwave (0.10.0)
CFPropertyList (2.3.0)
dalli (2.7.4)
database_cleaner (1.3.0)
delayed_job (4.0.6)
delayed_job_active_record (4.0.3)
delayed_job_web (1.2.10)
diff-lcs (1.2.5)
erubis (2.7.0)
excon (0.44.2)
factory_girl (4.5.0)
factory_girl_rails (4.5.0)
fakeweb (1.3.0)
faraday (0.9.1)
fastercsv (1.5.5)
figaro (1.1.0)
fission (0.5.0)
flying-sphinx (1.2.0)
fog (1.27.0)
fog-atmos (0.1.0)
fog-aws (0.1.0)
fog-brightbox (0.7.1)
fog-core (1.28.0)
fog-ecloud (0.0.2)
fog-json (1.0.0)
fog-profitbricks (0.0.1)
fog-radosgw (0.0.3)
fog-riakcs (0.1.0)
fog-sakuracloud (1.0.0)
fog-serverlove (0.1.1)
fog-softlayer (0.4.1)
fog-storm_on_demand (0.1.0)
fog-terremark (0.0.4)
fog-vmfusion (0.0.1)
fog-voxel (0.0.2)
fog-xml (0.1.1)
formatador (0.2.5)
geocoder (1.2.7)
globalid (0.3.3)
gyoku (1.2.2)
haml (4.0.6)
hashery (2.1.1)
highline (1.6.21)
hike (1.2.3)
httpi (2.3.0)
i18n (0.7.0)
inflecto (0.0.2)
innertube (1.1.0)
ipaddress (0.8.0)
jbuilder (2.2.7)
joiner (0.3.4)
json (1.8.2)
kaminari (0.16.1)
kgio (2.9.3)
launchy (2.4.3)
letter_opener (1.3.0)
loofah (2.0.1)
macaddr (1.7.1)
mail (2.6.3)
middleware (0.1.0)
mime-types (1.25.1)
mini_magick (4.1.0)
mini_portile (0.6.2)
minitest (5.5.1)
monetize (1.1.0)
money (6.5.1)
money-rails (1.4.1)
multi_json (1.10.1)
multipart-post (2.0.0)
mysql2 (0.3.18)
net-scp (1.2.1)
net-ssh (2.9.2)
nokogiri (<IP_ADDRESS>)
nori (2.4.0)
paranoia (2.1.0)
parser (<IP_ADDRESS>)
pdf-core (0.5.1)
pdf-inspector (1.2.0)
pdf-reader (1.3.3)
pg (0.18.1)
powerpack (0.1.0)
prawn (2.0.2)
prawn-table (0.2.1)
pusher-client (0.6.0)
rack (1.6.0)
rack-cors (0.3.1)
rack-protection (1.5.3)
rack-test (0.6.3)
rails (4.2.0)
rails-api (0.4.0)
rails-deprecated_sanitizer (1.0.3)
rails-dom-testing (1.0.5)
rails-html-sanitizer (1.0.1)
rails_12factor (0.0.3)
rails_serve_static_assets (0.0.4)
rails_stdout_logging (0.0.3)
railties (4.2.0)
rainbow (2.0.0)
raindrops (0.13.0)
rake (10.4.2)
riddle (1.5.11)
rspec-core (3.2.0)
rspec-expectations (3.2.0)
rspec-mocks (3.2.0)
rspec-rails (3.2.0)
rspec-support (3.2.1)
rubocop (0.29.1)
ruby-progressbar (1.7.1)
ruby-rc4 (0.1.5)
ruby2ruby (2.1.3)
ruby_parser (3.5.0)
rubyntlm (0.4.0)
sass (3.4.12)
savon (2.8.1)
sexp_processor (4.4.5)
simplecov (0.7.1)
simplecov-html (0.7.1)
sinatra (1.4.5)
sprockets (2.12.3)
sprockets-rails (2.2.4)
systemu (2.6.4)
terminal-table (1.4.5)
thinking-sphinx (3.1.3)
thor (0.19.1)
thread_safe (0.3.4)
tilt (1.4.1)
timecop (0.7.3)
ts-delayed-delta (2.0.2)
ttfunk (1.4.0)
tzinfo (1.2.2)
unicorn (4.8.3)
uniform_notifier (1.7.0)
uuid (2.3.7)
vcr (2.9.3)
wasabi (3.3.0)
websocket (1.2.1)
VH
Nicolai Seerup
Soundtracktor ApS
Lead Developer - Ruby on Rails
Danas Plads 17A
DK - 1905 Frb. C.
+45 3145 8035
ns@s <EMAIL_ADDRESS>Follow Me
Twitter http://www.twitter.com/soundtracktor
Newsletter https://soundtracktor.com/#social
2015-08-09 1:43 GMT+02:00 Pat Allan<EMAIL_ADDRESS>
I'm not really sure why this is happening… which versions of Thinking
Sphinx and Sphinx are you using? And what settings do you have for this
environment in config/thinking_sphinx.yml?
—
Reply to this email directly or view it on GitHub
https://github.com/pat/thinking-sphinx/issues/935#issuecomment-129070977
.

The fact that it passes on CircleCI does suggest it's probably a difference between the two environments. Does it pass in the test environment on your machine, as opposed to development? Do you know what version of Sphinx is being used on CircleCI?

Hi Pat, Im building a strictly JSON API and its not set up to run in
development env locally, only test env. But the test has passed previously,
but after an update of brew, ruby to 2.2.2 and sphinx to 2.2.9_1 it
suddenly failed
Circleci is using 2.0.4 https://circleci.com/docs/test-with-sphinx
Cheers /N
VH
Nicolai Seerup
Soundtracktor ApS
Lead Developer - Ruby on Rails
Danas Plads 17A
DK - 1905 Frb. C.
+45 3145 8035
ns@s <EMAIL_ADDRESS>Follow Me
Twitter http://www.twitter.com/soundtracktor
Newsletter https://soundtracktor.com/#social
2015-08-10 19:16 GMT+02:00 Pat Allan<EMAIL_ADDRESS>
The fact that it passes on CircleCI does suggest it's probably a
difference between the two environments. Does it pass in the test
environment on your machine, as opposed to development? Do you know what
version of Sphinx is being used on CircleCI?
—
Reply to this email directly or view it on GitHub
https://github.com/pat/thinking-sphinx/issues/935#issuecomment-129531342
.

When you upgraded Sphinx versions, do you know what you were on previously when it did work on your machine?

No sorry, i didnt check. Its not a big problem, i can just downgrade to a
previous version, but I´m just thinking its an unexpected behaviour in this
new version that should be investigated...
VH
Nicolai Seerup
Soundtracktor ApS
Lead Developer - Ruby on Rails
Danas Plads 17A
DK - 1905 Frb. C.
+45 3145 8035
ns@s <EMAIL_ADDRESS>Follow Me
Twitter http://www.twitter.com/soundtracktor
Newsletter https://soundtracktor.com/#social
2015-08-10 19:40 GMT+02:00 Pat Allan<EMAIL_ADDRESS>
When you upgraded Sphinx versions, do you know what you were on previously
when it did work on your machine?
—
Reply to this email directly or view it on GitHub
https://github.com/pat/thinking-sphinx/issues/935#issuecomment-129544914
.

Indeed - it'd be good to know which version the issue started appearing. Perhaps it's worth downgrading to the latest 2.1.x Sphinx release first, see how that goes?
Also, there have been some changes to how Thinking Sphinx behaves when interacting with different versions of Sphinx - have you looked at the release notes for this? https://github.com/pat/thinking-sphinx/releases (particularly 3.0.6 and 3.1.0)


Revert "Move C API versioning into Version.xcconfig"

Reverts apple/swift-llbuild#239

@swift-ci smoke test.

@dmbryson @ddunbar Can one of you please merge this revert PR, or checkin the fix ASAP?
rdar://38417076

Sure

Done

On Mar 13, 2018, at 8:35 AM, Andrew Trick<EMAIL_ADDRESS>wrote:
@dmbryson https://github.com/dmbryson @ddunbar https://github.com/ddunbar Can one of you please merge this revert PR, or checkin the fix ASAP?
rdar://38417076
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/apple/swift-llbuild/pull/241#issuecomment-372708648, or mute the thread https://github.com/notifications/unsubscribe-auth/AAGggTMCtTDgVrPNBHudQnPyTEAQkckAks5td-dCgaJpZM4So5_t.

@ddunbar Thanks!


Fixed deactivating non-exist tenant in cli

fixed deactivating non-exist tenant in cli. In the current implementation it doesn't check for the existence of the tenant. Tenant id becomes -1 for non exist tenant.

I have fixed both tenant activate and deactivate cli issues. Please review and merge.

Thanks Pubudu! I have now merged this to master branch, please close the pull request manually.
Thanks


Invalid params: missing field `gasPerPubdata

    <dependency>
        <groupId>io.zksync</groupId>
        <artifactId>zksync2</artifactId>
        <version>0.0.2</version>
    </dependency>

{
"jsonrpc": "2.0",
"error": {
"code": -32602,
"message": "Invalid params: missing field gasPerPubdata."
},
"id": 1
}

This should be resolved with latest release. You can refer to examples here: https://github.com/zksync-sdk/zksync2-examples/tree/main/java


Update service-premium-gen2-what-is.md

Misleading. Gen2 does not provide separation between refreshes and queries. When we add support for query scale-out, that will become available.

Learn Build status updates of commit f2cc9b1:
:bulb: Validation status: suggestions

File
Status
Preview URL
Details

powerbi-docs/enterprise/service-premium-gen2-what-is.md
:bulb:Suggestion

Details

powerbi-docs/enterprise/service-premium-gen2-what-is.md

Line 40, Column 2: [Suggestion: column-header-missing - See documentation] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Fixed in the private repo.


Bump storybook deps to 6.3.2: MB-8274

Description
Updating @storybook deps to the same version all at once rather than one by one.

Reviewer Notes
This accounts for:

https://github.com/transcom/mymove/pull/6910
https://github.com/transcom/mymove/pull/6912
https://github.com/transcom/mymove/pull/6913
https://github.com/transcom/mymove/pull/6915
https://github.com/transcom/mymove/pull/6916

The tests should run and pass w/o issues...
References

Jira story for this change

Messages

:book:
:link: MB-8274

  Generated by :no_entry_sign: dangerJS against 469f2f4ddbcd520bb514dddc7373c6f0744da408

looks good


GitHub is reporting the Hound check as passed when violations are found

I would expect it to be marked as failed, with a red x since violations were found, no?
Thanks for this great service, by the way!

Oops. Got posted twice. Closing this one.


add 5s and 15s byoyomi time choices to proposal form (for blitz)

A small tweak to the proposal form to allow not just 10s, 20s, 30s etc. byo-yomi times, but 5s, 10s, 15s, 20s, then 30s, 40s, etc. times. This is meant for more refined control for blitz, where 5s makes a big difference.
(In CGoban, the button increments are 10s below 60s, but you can manually enter any time in the time input box, which isn't possible with Shin KGS. Adding the 5s increments below 20s seemed like an elegant solution in keeping with your UI style.)

Thanks! I was tempted to keep 10s increments for simplicity, but I'll allow people their weird time controls 🙃


parse failure on Twilio

Describe the bug
When calling in voice command and dtmf I get an error on all options from Twilio

What version are you running
2.4.0
Expected behavior
Connect to helpline volunteer, meeting finder or JFT
Screenshots

Another screenshot

Not a good idea to have phone numbers in the description.  Repro steps should work in an isolated system, not on a test system.

These repro steps seem incomplete.  Several people are running 2.4.0 and have not reported this issue.

I'm running different instances on the same server and not having any issues with those 2.4.0 installations, just this one. I just reuploaded all of the files again to make sure none were corrupted.

It’s your PHP settings most likely.
On Sun, Oct 21, 2018 at 4:45 PM Steve Scranton<EMAIL_ADDRESS>wrote:

Same error,
[image: image]
https://user-images.githubusercontent.com/31661648/47272227-46622980-d548-11e8-9219-51acac9acc65.png
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/radius314/yap/issues/165#issuecomment-431702491, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABw9u7OKp7jkz2SJpKhtv703Aw3PWkumks5unNzVgaJpZM4XypIw
.

Downgrade to the last known working version.
On Sun, Oct 21, 2018 at 4:46 PM Danny Gershman<EMAIL_ADDRESS>wrote:

It’s your PHP settings most likely.
On Sun, Oct 21, 2018 at 4:45 PM Steve Scranton<EMAIL_ADDRESS>wrote:

Same error,
[image: image]
<
https://user-images.githubusercontent.com/31661648/47272227-46622980-d548-11e8-9219-51acac9acc65.png
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/radius314/yap/issues/165#issuecomment-431702491,
or mute
the thread
<
https://github.com/notifications/unsubscribe-auth/ABw9u7OKp7jkz2SJpKhtv703Aw3PWkumks5unNzVgaJpZM4XypIw
.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/radius314/yap/issues/165#issuecomment-431702573, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABw9u0aaRN3VWWJ46heHEme24cAbe_g9ks5unN0XgaJpZM4XypIw
.

back to 2.3.3 and php ver 7.0, still have issues

I believe I know what might be going on.  I can't repro it, but I've narrow it down to two files that have been causing this.  Can you see if master fixes your issue?

Works as expected now, thanks for getting it fixed.

Good to hear.  Will close this when 2.5.0 is officially released this week.
On Mon, Oct 22, 2018 at 9:57 AM Steve Scranton<EMAIL_ADDRESS>wrote:

Works as expected now, thanks for getting it fixed.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/radius314/yap/issues/165#issuecomment-431843266, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABw9u_LN8p-1eBGbst-xSrYdrpPgLLHAks5unc7VgaJpZM4XypIw
.

released with 2.5.0


In-client designer crashes when designing on custom database

Hello everybody,
We encounter the following error when trying to design a page in our localized version of NAV 2018 CU2 installed on a local VM:

We are using AL Language 0.12.16641.
We didn't publish any extension from VS Code. We just tried to design a page (e.g. Sales Order List - to add/remove a field).
On the W1 version the in-client designer works fine.
On our localized version, after the adding/removing the field, the designer crashes:

We downloaded the symbols in VS Code.
We published succesfully the symbols with cmdlet -SymbolsOnly.
We changed NetFx40_LegacySecurityPolicy setting in Microsoft.Dynamics.Nav.Server.exe.config file to "false" and restarted NAV Server Instance.
We searched for similar issues, and we found #296.
Does anyone else still has the same problem? How can we solve it?
Thanks a lot,
Raluca

The event viewer entry claims that you do not have the application symbols in your database.
How did you add the application symbols ? I think you have juts added the system symbols?
https://blogs.msdn.microsoft.com/nav/2018/01/16/generate-symbols-in-a-modern-development-environment-with-microsoft-dynamics-nav-2018/
https://blogs.msdn.microsoft.com/nav/2018/02/02/import-symbols-in-new-or-upgrade-databases-with-microsoft-dynamics-nav-2018/
https://docs.microsoft.com/en-us/dynamics-nav/developer/devenv-running-cside-and-al-side-by-side

Thank you very much.
We thought about that, but also in the links that you mentioned (last one) it says: "If you are upgrading to Microsoft Dynamics NAV 2018 CU1, or higher, please use the symbols that you find in the ModernDev folder on the cumulative update DVD."
We are using NAV 2018 CU2 and on the DVD we have:

We generated the symbols as it is stated in the other link:

And we have the following result:

All this didn't solve the problem.
What are we doing wrong?

That means that you have the test and system symbols in place. The designer on the other hand still does not "see" your app symbols.
Does the "Hello World" VsCode sample work for you. Can you publish it from within VsCode?

Yes, we can publish the Hello World sample.

What happens if you publish the symbol file named Microsoft_Application* (as symbols) that you have downloaded in VSCode. This is the symbol reference file generated from C/SIDE?

We manage to download the Microsoft_Application* symbols and published them.

So now we have:

And the in-client designer works. Yey!
Maybe it would be helpful to update the info in the link:
https://docs.microsoft.com/en-us/dynamics-nav/upgrading-the-data#AddExtensions
because it says:

We were using NAV 2018 CU2, so we published only the symbols we found on the DVD:

Thank you very much.
Raluca

https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-running-cside-and-al-side-by-side


[Event Hubs] Update RetryOptions interface to pass exponential retry params

For more context refer to #4266

In the getMaxMessageSize() is a function that uses retry. It should also use the exponential parameters as well

Updated

I like what we have done in the receiver.ts file i.e have all the defaults handled in core-amqp and avoid the retryOptions && retryOptions.maxRetries model in favor of retryOptions.amxRetries. Let's ensure we do the same in the eventHubSender.ts file

Updated

I believe #4322 is almost done. Let's get that merged, and then update this PR to pass in the exponential things to the management operations

Updated, yes depending on which PR gets merged first, I can take care of the conflicts and ensure this is in place. (The other one's waiting on another approval)
cc: @ramya-rao-a

Looks good. Just 2 comments regarding inlining maxRetries and delayInSeconds to be consistent

Updated


Redo contestation

closed by commit: https://github.com/alescrocaro/forum-invasores/commit/6b31c599473832069e19fbc2bcb83e7f9e287cdf


I'm not even a developer >> just a student trying to get his project done at last minute
but I tried running the exact code but I got this error :
FileNotFoundError: [WinError 3] The system cannot find the path specified: '/dev/random'
environment: VSCode , Win10 , Py3.8.2
for full Error message :
Traceback (most recent call last):
File "xx", line 4, in
shamir.to_base64(shamir.split_secret("this is my secret".encode('ascii'), required_shares, distributed_shares))
File "xx\Python\Python38-32\lib\site-packages\sslib\shamir\shamir.py", line 73, in split_secret
with kwargs.get('randomness_source', randomness.RandomReader() if secret_length <= 65 else randomness.UrandomReader()) as randomness_source:
File "xx\Python\Python38-32\lib\site-packages\sslib\randomness.py", line 15, in enter
if os.stat("/dev/random"):
FileNotFoundError: [WinError 3] The system cannot find the path specified: '/dev/random'
sorry again just trying to help

same issue for me, i've tried to work with this algorithm and most of the libraries online have problems, none of them work

The current implementation does not work with windows, only with Linux.
Why not use https://docs.python.org/3/library/secrets.html#module-secrets ? secrets.token_bytes should provide the best available solution on each context

The PR #4 offers a solution for this issue


Release a stable Microsoft.Web.Xdt.Extensions

Microsoft.Web.Xdt.Extensions is shared with Application insights and bundled into both ours and their site extensions. They have asked us to release release a stable version, preferably to nuget.org as we don't have other hosts for stable packages.
It still needs some tests (https://github.com/aspnet/AzureIntegration/issues/21)  and has one possible bug with hiding environment variables (https://github.com/aspnet/AzureIntegration/issues/84)

@glennc Thoughts here? Do we want to make this a "stable, supported" package, or work with AppInsights to get them either internalize or use a submodule to get this code?

Based on the discussion with @glennc, we are not planning to publish this to nuget. We'll continue to hand out source/dlls.


Zoom and pan programatically

I'm trying to add some buttons to let users control the zoom level using just a button, but I can't seem to get the zoomTo, panTo and viewportTo functions working.
Like this:

My current attempt is accessing the vflow component using a viewChild, and then running the zoomTo function there, but nothing seems to happen. The viewportChange observable also does not register any changes.
Are these not meant to be run like this?

Thanks for your issue! See the problem, will be fixed during this week

Just released 0.6.0, manual zoom/pan should work fine here
#64

Awesome, thank you! It works almost perfectly now, only thing is that I would have assumed that the zoom would be centered on the center of the viewport, but it doesn't seem to do that. See attached video.
I can try to work around it, but just thought I'd point it out!
https://github.com/artem-mangilev/ngx-vflow/assets/9968658/e6ad9aaf-1450-4822-b72a-f396940db906

Seems like zoomTo must behave like this by default, will fix it during the weekends

Could you please share the code snippet of how to manage the manual zoom?
My implementation is:
<button (click)="zoom()">Zoom</button>
<vflow />

  ...

  zoom() {
    const current = this.vflow.viewport().zoom

    this.vflow.zoomTo(current + .3)
  }

...

When user clicks the zoom button, I just get the current level of zoom (from the viewport() signal), add some value to it and pass to zoomTo method of VflowComponent.
https://github.com/artem-mangilev/ngx-vflow/assets/53087914/11d3d9b9-dd59-4478-8649-7a60ae682c06

Huh, my code is exactly like that 😅 And I just tested in a Stackblitz and it does behave like in your video. There must be something else that's off with my solution. I think you can close this issue then. Thanks!

Figured it out now. I forgot to put view="auto" on the vflow component, and had used css instead to increase the size.

Thanks! Yeah, for now you basically have 2 options: fixed view size with passing [width, height] tuple and auto size when the flow adjusts to its container: https://www.ngx-vflow.org/examples/view-size


Failed! missing_scope ERROR

Hi Folks, neat App,
I installed fine through downloading and executing the docker container.
Then I accessed with a browser and received the error:
Failed! missing_scope in the browser.
I cannot access more than this as logs from the container:
POST /invite 200 1110.118 ms - 624 GET /css/style.css 304 3.993 ms - - GET /images/bg.jpg 304 1.094 ms - -
In the Oauth & Permissions Page at /oauth? -- which has changed since the manual was written --
I added under User Token Scopes

admin.teams:write

But when I follow up by pressing Please reinstall your app for these changes to take effect ..
The page reports:
This app can not be installed on this workspace. Apps with this feature are only available to Enterprise customers.
We are on the Slack Standard Plan.
Do I have the wrong Oauth permissions option or id an Enterprise Grid a requirement for programatic inviting of Users
Thanks for your help and any advice.

Hello ! Any update on this issue ? ;)

@allomorphy @ThomasLachaux did any of you solve this? I have the same issue.

@kindofone @ThomasLachaux @allomorphy, did any of you find an alternative solution?

@elimcjah I didn’t invest time in trying to solve this. So, nothing on my end 🤷♂

Hi guys, I'm having the same issue here, an I tried adding a new Scope under User Token Scopes

I added the scope "Invite members to a workspace and approve or deny invitation requests" and tried to "Reinstall to Workspace", bu I get the nex request by Slack

I don't know if this is the real problem, but if so, Slack is asking for an Enterprise plan to do this. Any suggestions to solve this by the maintainers/owners. Is this the way to solve it? Basically same error as @allomorphy

Looks like that this project is not working anymore for new installs.

Looks like that this project is not working anymore for new installs.

Same here, can't use it for the fresh community

Same here, can't use it for the fresh community

+1
same issue

+1
curl -X POST 'https://YOUR-SLACK-TEAM.slack.com/api/users.admin.invite'
--data 'email=EMAIL&token=TOKEN&set_active=true'
--compressed
is giving : {"ok":false,"error":"missing_scope","needed":"client","provided":"admin,identify"}%
To give the client scope : tried this https call
https://slack.com/oauth/authorize?&client_id=CLIENT_ID&team=TEAM_ID&install_redirect=install-on-team&scope=admin+client
But this really is not helping as the client scope is not being granted. (Even though the page redirects asking for allow/cancel option). The application scope is not being reflected here: https://api.slack.com/tokens.
Only the changes done via UI seems to work and admin.invites.read/write too are not for standard edition slack.
Have tried this quickfix for granting client scope: https://medium.com/@andrewarrow/how-to-get-slack-api-tokens-with-client-scope-e311856ebe9 .
Dint work either

same

I think this issue does not go away. If you do not have legacy token, then the OATH token is broken for free slack users. Enterprise slack users may enjoy the benefit of this project only.

Same issue - "This app can not be installed on this workspace. Apps with this feature are only available to Enterprise customers."

Just tried, doesnt work indeed.

Did not work for me either. I lost the legacy token too.

Did not work for me either. I can't make the legacy token too.

Any updates?

No. This bug is not this application.
Slack's bugs.

I'm using this as a workaround:
https://github.com/outsideris/slack-invite-automation/pull/149

Having this same issue but getting;
Invalid permissions requested
invalid_scope
when trying to add "admin.apps:read" as a User OAuth scope. Incredibly frustrating? I am the workspace and App admin, so can't understand why I still have the error?

I'm having the same issue.  No previous suggestions seem to help.  Anyone know how to fix this?


Question

Ok first of all, I love the work you do!
I just wanted to ask if you could make it like the real deal with their snapshots that you give us test versions every now and then along with of course the normal "stable" releases. I'd really like to help find issues and bugs.
Another thing I noticed is that sometimes saving the game makes the game give out a very eery sound and crash the game, I don't know why it happened, sadly. Also I feel like there should be a deadzone of 0.25 as a standard setting instead of 0.00
Also, in case survival was ever planned, I feel like the player should still get to decide at what mining speed creative mode goes, maybe with a bedrock pickaxe or smth to get that insta mine like the real deal and without to get a little more of a survival feeling, idk.
Also: is survival planned? If yes, what needs to be done before that?

Hey @Niplob, thx for messaging me!
A bug hunter is welcome!
Some bugs has been fixed in these most recent builds;
Survival is a possibility, but might take time. There's only on DEV nowadays, that's me XD....

wow thx wellinator im subscribed but i was removed due to inactivity but xD i just wanted to support a bit cause idk but i think imma try working on my own projects see what i can do i got a pc that finaly can open blender mabe ill port fallout 3 if i get this in my hands

wow thx wellinator im subscribed but i was removed due to inactivity but xD i just wanted to support a bit cause idk but i think imma try working on my own projects see what i can do i got a pc that finaly can open blender mabe ill port fallout 3 if i get this in my hands

Man you are going be banned if you continue like this...


Changes

Renamed body_parser to BodyParser for PEP8 compliance
Added JSON handler in BodyParser
Change tasks.TODO to todo.md
Added a list of possible tasks in todo.md
Added query string support
Fixed an edge case in splitting by \r\n where body could contain a \r\n\r\n
Renamed body_parser to BodyParser, changed request_parser to function parse_request and response_builder to class Response
Added error handlers and ability to add more handlers
Added a couple extra status codes

Hey Aarav! 👋
first of all thank you so much for contributing and taking the time to read the code, you brought some really good ideads that i didn't think of.
However, when i tested your code it was not working, i found several bugs and i really tried to debug them to get your contribution working, because i wanted to add the features that you brang to the framework, but it did not lead to anything.
here are the bugs that i found:

TypeError: parse_request() missing 1 required positional argument: 'request' : this happened when launching the server and visiting the webpage, and it occured because when you converted the request_parser class to a function you leaved the self parameter. i corrected that quickly.
NameError: name 'req' is not defined: this happened because you renamed some variables but not in all the code, there were another couple of these NameError erros that i will not talk about.
IndexError: list index out of range: finally i got stuck on this error that i could not debug, that happened during the parsing of the headers, i couldn't figure out why it happened because i am a student and i had some classes today that didn't let me the time 😅 .

but other than that, i really like what you brang, especially the PEP8 compliance that i totally forgot about, and the tasks in the todo.md file are very good.
i hope that you will debug the code that you wrote so i can push it to the repository
also, do you think refactoring the request_parser class to a function is a good idea ? because parsing the request will necessite quite a lot of functions, and it would be great to include them under on class


feat(rust): node config improvements

Add validation for node create positional argument (name or conf): we'll now return an error if the node name is not valid (e.g. node create config.yaml and the config file doesn't exist.
Refactor ArgKey as a struct instead of a type. This simplifies some data conversions and makes the code more readable
The command args now have precedence over config values. This means that we now have a lot of combinations to run a node with a config file. For example: node create n1 --identity i1 --configuration "{name: api-service-inlet}" will use the name from the command arg, instead of the one defined in the config
If an identity is passed to node create, the identity will be created if it doesn't exist, so that running the command in foreground/background/config modes, the behaviour will be the same

I hadn't noticed that we could pass a configuration file directly with ockam node create config.yaml.

Yeah, this was the intended UX when we first added the config file so the user can use the same positional argument for either a config or a node name. We should revisit it, but it will probably break some examples.

My concern is that this is redundant with the existing --configuration argument. This also leads to more complicated code because now we have to guess if we're being passed a name or a configuration.

The --configuration argument was later added to accept an inline config, for use cases where we can't or don't want to store the config in a file. But same thing, we should revisit this UX.


feat(compiler): support rc4 encrypt model and format CMakeLists

@chenqy4933 @haolongzhangm  @chen-2569 麻烦review下

LGTM

gently ping @haolongzhangm

国产化加密，好耶！


Fix ext::auth::ClientTokenIdentity cardinality

Since conf.key is a set, we end up with a multi cardinality

Just to confirm @msullivan: this would be hard to patch into 4.1?


:bug:Fix logical clusters issues.

Summary

Do not return from provider watch loop.
Enqueue for all object changes on update event.
Do not use controller context and logger outside the controller.
Change some log messages.

Related issue(s)
Fixes #

/lgtm
/approve


Prototype: Generate JWTs for human agents

This PR reuses and tweaks the delegation token logic for agents in paused runs, to also use it to generate JWTs for agents in human baselines. These JWTs allow human baseliners to call some but not all hooks.
This code just covers the authentication side of things. On the JWT generation side, we'd need a code path that generates these JWTs using createNonAuth0Token and puts them in the database as part of run setup. For that, I think we could have an isHumanBaseline field on the setupAndRunAgent procedure's request body, like I added in https://github.com/METR/vivaria/pull/205. (However we probably don't need the viv human-baseline command.
Benefits of this:

We don't need to make most hooks routes public.
We could easily add some authentication to prevent baseliners from calling hooks routes on runs other than the one they have a token for.

Disadvantages:

I'm not sure we should have Vivaria generate JWTs in more situations. It would be nice if Auth0 were the only place in our system that generated JWTs.
This is slightly more complicated than making most hooks routes public, but not that much more complicated.

seems like a good idea to me

Closing this since we're going to go with a different approach, using Auth0 to generate JWTs for human agents.


The video sound gets very soft

I have compared the sounds with YouTube Application.  Sound is working fine in youtube application but in your library it is getting very slow.
Please help me.

It is low.
I have used youTubePlayer.setVolume(100) as well. But no effect. :(

There's not much I can say, have you tried on different devices?

related to #79

Yeah I have tried it but same result. :(

I've never faced this issue, let me know if you manage to find a solution!

can it set volume more than 100% ?

@ghozien no.

i compare this library volume is 50% low than with youtube app

Where does the 50% measurements comes from? On my devices they have the same volume.


jQuery conflict

Hi, congrats on this very nice looking library :)
So, first issue: it's not working if you run jQuery on the same page. Using latest jQuery as of now, version 2.1.3
Adding is.js before jQuery produces this error in jQuery (copied from Firebug):
TypeError: d[q] is not a function

...d[k],h&&(d[k]=null),n.event.triggered=q,d[q](),n.event.triggered=void 0,h&&(d[k]...
If you call is.js after jQuery, then you get this error:
TypeError: X[g].exec is not a function

....slice(c.length));for(g in d.filter)!(e=X[g].exec(h))||j[g]&&!(e=j[g](e))||(c=e....
This library looks like a must-have, but then again, jQuery is a must have. :)

Hello @hellocosmin , I'm going to check into this when I get back home, not sure what could be but remember that jQuery 2+ only works on modern browsers and is.js works on ie 6+ so maybe it has something to do with that.

Are there any plans on moving forward and dropping such old browser support, in order to enable compatibility with future versions of jQuery?
The way I see it, the web is quickly moving towards adapting new versions of jQuery and dropping support for dinosaur browsers. It would mean less headaches for you too - perhaps a separate branch?

I though it was finally working fine, here is a simple working demo: http://jsfiddle.net/1z0vh5wp/
Can you show me your code or where are you getting this error?


ASA calculation

It is an extra orca calculation which enables simulating emission spectra.
In order to to implement this calculation, I need to first fix #3
From there, either I need to write a new calculation class which subclass the OrcaCalculation or implement it there.

closed in #23


broken blogpost link in the readme

readme links https://crfm.stanford.edu/2023/06/14/anticipatory-music-transformer.html , actual link is https://crfm.stanford.edu/2023/06/16/anticipatory-music-transformer.html

Thanks! Fixed.


support shutdown hooks

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.莫彦豪 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Create ISSUE_TEMPLATE.md

Add an issue template [1] in order to have better issue description.
[1] : https://github.com/blog/2111-issue-and-pull-request-templates

You can see it in action at https://github.com/farnulfo/Flickr4Java/issues/new

Thanks, this is now merged and released.


suggestions of files and folders in workspace  when i wrote src/href in tags

Does this issue occur when all extensions are disabled?: Yes/No

Duplicate of #2037


bug(slider): JAWS incorrectly announces MatSlider value changes

Reproduction
Default slider with no modifications: https://angular-cxwukz.stackblitz.io
Steps to reproduce:

Enable JAWS
Focus on the slider, and hold down left or right arrow to move slider.

Does not repro with NVDA or ChromeVox.
Expected Behavior
Slider will move while button is pressed and stop when it is  not. JAWS will announce the slider values as the slider is moved.
Actual Behavior
The slider keeps moving, and JAWS says nothing.  When the slider stops moving, JAWS repeats the value multiple times.  "79 79 79 79 79 79".
Environment

Angular: Google
CDK/Material: Google
Browser(s): Chrome 85
Operating System (e.g. Windows, macOS, Ubuntu): Windows 10 Pro

I believe that our slider is based on this example from the W3C https://www.w3.org/TR/wai-aria-practices-1.1/examples/slider/slider-1.html. There are a couple of other approaches we could take, but they have their own drawbacks:

We could have an internal input[type="range"] that we proxy all events and focus to. This is problematic, because we can't do a multi-handle slider in the future.
We could have the value inside an aria-live element, but that may generate more noise to the user.

I don't have JAWS available, but I wonder if debouncing the aria-valuenow assignments would help with it.

Unfortunately we don't have access to JAWS while Google is working remotely, so we might not be able to look at this for a while.

The upcoming MDC-based slider will use an internal <input type="range"> that will likely fix this problem.

For the new MDC based slider coming soon in v15, JAWS correctly says the updated value. I also tested the current slider component (v14), this is working correctly now too.


SQS Golang example is outdated

The example: https://cloud.yandex.ru/ru/docs/message-queue/instruments/golang doesn't work with recent versions of AWS SQS SDK.
Recently SQS migrated their service's protocol from the Query protocol which was XML based, to a JSONRPC protocol, and updated the default SDK behavior accordingly.
See https://github.com/aws/aws-sdk-go-v2/issues/2451 for exact error and explanation.

The workaround is to downgrade corresponding deps:
github.com/aws/aws-sdk-go-v2 v1.22.2
github.com/aws/aws-sdk-go-v2/service/sqs v1.26.0

It seems fixed in #725