error with enqueue?

Original issue by nixshal on 2022-01-27 17:24:53+00:00
I packaged your 'minimal' example into a app() function (so I can run it as a page in a multi-page streamlit app). Similar to what's being done here.
import streamlit as st
import datetime

try:
    import streamlit_analytics
except ImportError:
    import subprocess, sys # Install streamlit-analytics on first run (not included in requirements.txt).
    subprocess.check_call([sys.executable, "-m", "pip", "install", "streamlit_analytics"])
    import streamlit_analytics

def app():
  with streamlit_analytics.track(verbose=True):
    st.text_input("Write your name")
    st.selectbox("Select your favorite", ["cat", "dog", "flower"])
    st.button("Click me")

However, I got the following error using streamlit 1.4
File "/home/appuser/venv/lib/python3.7/site-packages/streamlit/script_runner.py", line 379, in _run_script
    """
File "/app/k_internal_tools/app.py", line 23, in <module>
    apps.run()
File "/app/k_internal_tools/multiapp.py", line 64, in run
    functions[titles.index(title)]()
File "/app/k_internal_tools/apps/tracking.py", line 12, in app
    with streamlit_analytics.track(verbose=True):
File "/usr/local/lib/python3.7/contextlib.py", line 112, in __enter__
    return next(self.gen)
File "/home/appuser/venv/lib/python3.7/site-packages/streamlit_analytics/main.py", line 443, in track
    load_from_json=load_from_json,
File "/home/appuser/venv/lib/python3.7/site-packages/streamlit_analytics/main.py", line 282, in start_tracking
    last_time=datetime.datetime.now(),
File "/home/appuser/venv/lib/python3.7/site-packages/streamlit_analytics/session_state.py", line 92, in get
    (not hasattr(s, "_main_dg") and s.enqueue == ctx.enqueue)

Any ideas?

Comment by nixshal on 2022-02-03 06:29:55+00:00
Downgraded to streamlit v1.3.1 and it worked. Changes need to be made to accommodate v1.4


maint: convert hardcoded operators to constants

Which problem is this PR solving?

This was intended to be purely a refactoring to pull out constant values
But it uncovered a bug -- we had a switch where we weren't checking the ">=" case!

Short description of the changes

Constantize all the things
Add the missing switch case
Write some tests (not exhaustive but try to prove all the major spots work)
Fix the boolean bug that was also uncovered by the tests

Oh, duh. I just now saw the reference to that issue in your branch name now.


Make :sudo in installer/uninstall :script 'false' by default

Currently installer :script uses sudo by default. This seems wrong, as contributors will likely set as few options as possible to have the cask work (as they should) and hence scripts that could otherwise be run without extended privileges will be anyway. The reverse should be true: if a contributor notices the installations breaks and sees extended privileges are needed, those should be set then.
sudo should be set when needed, not unset when not needed.

Lists of casks (from the next post, with fixes) with an (un)install :script, but no sudo line explicitly defined. Should be ticked as they are verified.

[x] amazon-cloud-drive
[x] amazon-music
[x] ax88179
[x] ax88772
[x] blast2go
[x] cacoo-ninja
[x] drobo-dashboard
[x] fitbit-connect
[x] gobbler
[x] jenkins
[x] lastpass
[x] logitech-control-center
[x] logitech-options
[x] logmein-hamachi
[x] paye-tools
[x] private-internet-access
[x] scratch
[x] sencha
[x] sophos-anti-virus-home-edition
[x] totalspaces
[x] vuze
[x] xampp

To verify:
To check their need for it now, you’d need to change each cask to explicitly use :sudo => false, and install/uninstall that. If everything goes right, :sudo => false should stay; if something goes wrong, it should be changed to :sudo => true and installed/uninstalled again (to make sure the error was really due to sudo, and not some change in the package, since the last time).

Roadmap:

[x] Make every cask with this use case use :sudo explicitly (no matter if true or false).
[x] Change the rule in the core to make false the default.
[x] Delete :sudo => false from the casks that have it.

Lists of casks that would need to be modified (casks with no sudo line)
acquia-dev-desktop
amazon-cloud-drive
amazon-music
ax88179
ax88772
blast2go
cacoo-ninja
drobo-dashboard
fitbit-connect
gobbler
google-cloud-sdk
jdownloader
jenkins
lastpass
logitech-control-enter
logitech-options
logmein-hamachi
paye-tools
private-internet-access
scratch
sencha
sophos-anti-virus-home-edition
splice
totalspaces
vuze
xampp

I want to highlight this problem further. Especially jdownloader previously bundled malware/adware on windows. Elevated privileges seems like a really bad idea for that program.

@adityadalal924 Changed “would” to “could”, and copied your list to the top post (thank you for making it).

@vitorgalvao How would I go about verifying that sudo is (or isn't) required?

@adityadalal924 We should implement this in three phases:

Make every cask with this use case use :sudo explicitly (no matter if true or false).
Change the rule in the core to make false the default.
Delete :sudo => false from the casks that have it.

To check their need for it now, you’d need to change each cask to explicitly use :sudo => false, and install/uninstall that. If everything goes right, :sudo => false should stay; if something goes wrong, it should be changed to :sudo => true and installed/uninstalled again (to make sure the error was really due to sudo, and not some change in the package, since the last time).

@vitorgalvao I've done a few - care to take a quick look and make sure everything looks okay?

Everything looks fine.
It’s clear why true is the default, since most need it. Making sure we don’t use sudo needlessly still trumps that, I’d say.

I've used the
  uninstall :script => { :executable => 'Uninstall.app/Contents/Resources/Scripts/__name__.sh',
                         :sudo => true },

construct a bit - would https://github.com/caskroom/homebrew-cask/issues/13607 fix that? (if and when it's fixed?)

In what manner? They aren’t related.

As in, it shouldn't be necessary for me to always use the :executable block for a script, they should automatically be executable.
(I saw it in one Cask, so I've been using that style - but I'm not sure if it's actually required.)

Ah, I see where the confusion is. executable does not make scripts executable. It just says “this is the script to run”, and needs to be used when the script needs extra commands. It has nothing to do with permissions.

All casks on the list are now checked and done.

@vitorgalvao: Does this behaviour also apply to brew cask zap? It seems that this command always requires sudo, regardless whether the files to be zapped can be deleted with just user permissions (e.g. files in ~/Library).

This has nothing to do with zap. This is only for things where sudo is given through a flag.

All PRs to finish this already open.

I believe this is breaking google-cloud-sdk.
I'm getting dozens and dozens of:
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/gsutil/th...
==> chmod: Unable to change file mode on /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/VERSION: Operation
==> Using sudo to gain ownership of path '/usr/local/Caskroom/google-cloud-sdk/latest'
Error: Command failed to execute!

==> Failed command:
/usr/bin/xattr -w com.apple.metadata:kMDItemAlternateNames (\"git-credential-gcloud\") /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/bin/git-credential-gcloud.sh

==> Standard Output of failed command:

==> Standard Error of failed command:
xattr: [Errno 13] Permission denied: '/usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/bin/git-credential-gcloud.sh'

==> Exit status of failed command:
#<Process::Status: pid 69886 exit 1>
Error: nothing to install


[depth_from_video_in_the_wild] about the checkpoint in table.4

Thank you very much for your code. But I had a problem loading the weight: tf.train. latest_checkpoint (checkpoint_dir) return None Type. It seems to lack the "checkpoint" file in the compressed package.

create a checkpoint file manually as workaround:
CKPT_DIR=depth_from_video_in_the_wild/checkpoints/cityscapes_kitti_learned_intrinsics
touch $CKPT_DIR/checkpoint
CKPT_STEP=1000977 # replace with you own latest checkpoint
echo "model_checkpoint_path: \"model-$CKPT_STEP\"
all_model_checkpoint_paths: \"model-$CKPT_STEP\"" > $CKPT_DIR/checkpoint


Why does Containers::get() not return Option?

Hi,
I don't understand why Containers::get() does not return an Option<Container>. From what I understand, get()ing a container by name (which seems to be the argument here) would either return an instance of Container or None if the named container does not exist.
But the interface does not return an Option but simply an instance of Container.
I don't understand why.
Maybe the docs are missing something here, maybe I just don't understand.
Can someone please elaborate or, if applicable, fix the documentation/interface?

Currently Containers::get() directly passes the name you provide to Container::new() as the ID, so it doesn't do any validation on the name to ensure the container exists, just returns a potentially invalid handles. The docs are definitely lack-luster in this regard and should be improved.
I think it would be a good idea to make it so Containers::get() would actually convert the name you provide to an ID and return Some(Container) if it is successful or None if it cannot find the container.

I consider this solved with the two PRs merged.


python310Packages.textnets: 0.8.8 -> 0.9.3

Changelog: https://github.com/jboynyc/textnets/blob/v0.9.3/HISTORY.rst
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 254197 run on x86_64-linux 1

4 packages built:

python310Packages.textnets
python310Packages.textnets.dist
python311Packages.textnets
python311Packages.textnets.dist

There's already a PR open for this (#240359) that has been awaiting review.

@jboynyc I apologize. I was not aware of the duplicate, although I commented on that PR...
Thanks for checking.


ipcache: Simplify implementation with guaranteed LPM support

Cilium v1.13 and above has a minium kernel version requirement of v4.19.57 or above (or with equal feature support). This means that we can assume that we always have full LPM map support including iterating over the map and deleting elements from the map.
This allows us to considerably simplify our IPCache logic. This commit drops all fallback code for non-LPM maps or LPM maps without delete functionality.
Removed legacy fallbacks for LPM maps

/test

/test

Thanks everyone for the reviews so far. The timing of this PR was a bit unfortunate since there is quite some changes to be made seeing the feedback so far, however I have been re-tasked to do some client work. I will still move forward, but it might take me a bit.
I will take all of this feedback, revise the commits, then split them up into 2 PRs as suggested. Should have done that to begin with. The second commit is what the work was initially about, but while doing so I discovered all of the now-legacy code. Removing the legacy code made the modularization step easier. It was only during the "rebase to make neat commits" stage that it separated into two loose steps that can be their own thing. Hope that explains the rational at least.

My changes to bpf.Map have landed, so this PR can be rebased now. Re-opening.


[hotfix] Remove local timeout for Hybrid and Tiered result partition test.

What is the purpose of the change
HsResultPartitionTest#testRelease and TieredResultPartitionTest#testRelease  depend on local timeout, which will make the test unstable.
Brief change log

Remove local timeout for Hybrid and Tiered result partition test.

Verifying this change
This change is already covered by existing tests.
Does this pull request potentially affect one of the following parts:

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

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

Thanks @TanYuxin-tyx for the quick review, I have updated and force pushed this as it is only minor fix.


news api error : origin 'http://localhost:4200' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource

🐞 Bug report
Command (mark with an x)

- [ ] new
- [ ] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Description
 I am able see the data in network but not in browser console. this is literally weired for me.  prints the api result in server side logs. please help me out.
code:
getlatestnews(st,ed): Observable {
return this.http.get('XXXXXXX&FromTime='+st+'&EndTime='+ed)
}
🔥 Exception or Error

Access to XMLHttpRequest at 'xxxNews apixxxx' from origin 'http://localhost:4200' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

🌍 Your Environment

"@angular-redux/store": "^9.0.0",
    "@angular/animations": "^6.1.0",
    "@angular/common": "^6.1.0",
    "@angular/compiler": "^6.1.0",
    "@angular/core": "^6.1.0",
    "@angular/forms": "^6.1.0",
    "@angular/http": "^6.1.0",
    "@angular/platform-browser": "^6.1.0",
    "@angular/platform-browser-dynamic": "^6.1.0",
    "@angular/platform-server": "^6.1.0",
    "@angular/router": "^6.1.0",
    "@ng-toolkit/universal": "^1.1.50",
    "@nguniversal/express-engine": "0.0.0",
    "@nguniversal/module-map-ngfactory-loader": "0.0.0",
    "@ngx-meta/core": "^7.0.0",

Hello, we reviewed this issue and determined that it doesn't fall into the bug report or feature request category. This issue tracker is not suitable for support requests, please repost your issue on StackOverflow using tag angular-cli.
If you are wondering why we don't resolve support issues via the issue tracker, please check out this explanation.


gcc_stage2: -G0 flag removed

Ref #24

This does mean that we require changes in psp-packages to make sure we're not shipping everything without -G0 now.


Error on .jsx file

What version of Hono are you using?
4.2.1
What runtime/platform is your app running on?
nodejs
What steps can reproduce the bug?
In starter template I choose nodejs and rename file index.js to index.jsx and update package.json. When I go to route I get error on line with c from line with return c.html() that render JSX.

What do you see instead?
ReferenceError: React is not defined
    at Array.<anonymous> (my-app/src/index.jsx:29:16)
    at Hono.dispatch (my-app/node_modules/.pnpm/hono@4.2.1/node_modules/hono/dist/cjs/hono-base.js:198:38)
    at fetch (my-app/node_modules/.pnpm/hono@4.2.1/node_modules/hono/dist/cjs/hono-base.js:224:17)
    at Server.<anonymous> (my-app/node_modules/.pnpm/@hono+node-server@1.9.1/node_modules/@hono/node-server/dist/index.js:404:13)

Additional information
This is tsconfig.json
{
  "compilerOptions": {
    "target": "ESNext",
    "module": "ESNext",
    "moduleResolution": "Bundler",
    "strict": true,
    "types": [
      "node"
    ],
    "jsx": "react-jsx",
    "jsxImportSource": "hono/jsx",
  }
}

Can you post the code too to verify this error is not do to something there

Run pnpm create hono my-app then select nodejs and pnpm. Replace line in index.ts to return c.html(
test
). Change index.ts to index.jsx and update package.json then pnpm run dev and access localhost:3000 and you'll get the error.

Since you not using typescript with a .jsx file its not added to the compiler. You need to add in the pragma directives
/** @jsx jsx */
/** @jsxImportSource hono/jsx */

Then you will need to import jsx as well
import { jsx } from 'hono/jsx';

For first change this is already in tsconfig.json, which file do I need to add pragma?
"jsx": "react-jsx",
"jsxImportSource": "hono/jsx",

Where to import jsx and how to use it? I didn't import tsx so nowhere to replace it.

Yes, but the tsconfig.json only works when you are using typescript. If you have a .jsx file you are no longer using typescript.
You need to import jsx in any .jsx file, just like in React you used to have to import it even thought it was not used.

Ultimately, you should use.tsx. Typescript is working as the compiler, and using pragma directives will work but there may be bugs. In order to use vanilla javascript you would want to have a compiler like babel

Javascript is valid typescript so typescript should still work as compiler instead of babel. Files that are .jsx should work as easy as .tsx.

Yes JavaScript is valid typescript but JavaScript files are usually ignored by TypeScript.
However, a good point I didn't consider is allowing plain js to run with typescript. If you add allowJs: true, checkJs: true to your tsconfig.json that should allow it to work as well

@cdtut Did this work for you? Can we close this issue?


Looking for Developer to Create Simple Software for Hikvision DS-TCG406-E ANPR Camera

Hello, Dear Partners!
We are very interested in your project involving Hikvision equipment. My name is Denis, and I am with Skyvision Co. Ltd., based in Azerbaijan. We are about to launch a project focused on developing our own software for a management parking system, and we plan to use the Hikvision DS-TCG406-E ANPR camera. As you know, this is one of the latest Hikvision models suitable for creating a fully integrated parking solution.
We are currently looking for an expert who can assist us in developing this program. If you have source code for the DS-TCG406-E camera that could be integrated into our solution, we would be interested in purchasing it. Our preferred programming language is C++. As a startup in the early stages, we are hoping to keep costs reasonable. We look forward to your support and the opportunity to work with you.
Please feel free to reach me at<EMAIL_ADDRESS>With best regards,
Denis Vlasov
Director for Infrastructure Solutions
Skyvision Co. Ltd.

Hi, Denis
There are to ways to integrate

Using de SDK which is free and available from official channels. Not sure, but I guess the SDK is for windows only.
Using ISAPI also free similar to a web server recieving post requests.

Not sure which one applies to yor architecture but the second is the recommended by Hikvision,
In my experience code should not vary based on the cammera model.
Which O.S. are yo tergeting?
Do you want to proceed with SDK or ISAPI?


gateway facing should take carpet into account

You should be able to place carpet around and anchor to control facing direction, in addition to solid blocks and slabs.

fixed in https://github.com/globau/ClodMC/commit/37dac5268245b6c4579e291628d24150c64236a9


Add more resources

https://www.codecademy.com/learn/learn-the-command-line

https://guides.github.com/introduction/git-handbook/


Davinci Resolve Script Install Mac

How do i install for mac?

1, install python3.10.11
2, run setup_python.command
3, run りぞりぷと.command
The rest of the operation is the same as in windows.

I'll try it again. I had an error when I ran the command. aggraw wasn't
able to be updated. Should I try reinstalling python again?
On Fri., Feb. 2, 2024, 9:59 p.m. nakano000, @.***>
wrote:

1, install python3.10.11
2, run setup_python.command
3, run りぞりぷと.command
The rest of the operation is the same as in windows.
—
Reply to this email directly, view it on GitHub
https://github.com/nakano000/Resolve_Script/issues/13#issuecomment-1925049659,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVZWSMJTMYRC2IAIQE5JTCDYRWYYNAVCNFSM6AAAAABCWCIVWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRVGA2DSNRVHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Different versions of Python may produce errors.

ill install 3.10.11 again.
Thanks
On Fri, Feb 2, 2024 at 10:28 PM nakano000 @.***> wrote:

Different versions of Python may produce errors.
—
Reply to this email directly, view it on GitHub
https://github.com/nakano000/Resolve_Script/issues/13#issuecomment-1925081300,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVZWSMNRDGV5WGNPWT4A6R3YRW4HNAVCNFSM6AAAAABCWCIVWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRVGA4DCMZQGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Still doesnt work
A new release of pip is available: 23.2.1 -> 23.3.2
Im using DR 18.6
On Fri, Feb 2, 2024 at 11:15 PM GLDN @.***> wrote:

ill install 3.10.11 again.
Thanks
On Fri, Feb 2, 2024 at 10:28 PM nakano000 @.***>
wrote:

Different versions of Python may produce errors.
—
Reply to this email directly, view it on GitHub
https://github.com/nakano000/Resolve_Script/issues/13#issuecomment-1925081300,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVZWSMNRDGV5WGNPWT4A6R3YRW4HNAVCNFSM6AAAAABCWCIVWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRVGA4DCMZQGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Please let me know the error message displayed.

~ %
/Users/wadat/Desktop/Tutorials/Scripting/Resolve_Script2.5.10_mac/setup_python.command
; exit;
Collecting aggdraw==1.3.16 (from -r requirements.txt (line 1))
Using cached aggdraw-1.3.16.tar.gz (260 kB)
Installing build dependencies ... done
Getting requirements to build wheel ... done
Installing backend dependencies ... done
Preparing metadata (pyproject.toml) ... done
Collecting attrs==23.1.0 (from -r requirements.txt (line 2))
Using cached attrs-23.1.0-py3-none-any.whl (61 kB)
Collecting audioread==3.0.0 (from -r requirements.txt (line 3))
Using cached audioread-3.0.0.tar.gz (377 kB)
Installing build dependencies ... done
Getting requirements to build wheel ... error
error: subprocess-exited-with-error
× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> [20 lines of output]
  Traceback (most recent call last):

    File

"/Users/wadat/Desktop/Tutorials/Scripting/Resolve_Script2.5.10_mac/bin/python-3/lib/python3.12/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py",
line 353, in
      main()

    File

"/Users/wadat/Desktop/Tutorials/Scripting/Resolve_Script2.5.10_mac/bin/python-3/lib/python3.12/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py",
line 335, in main
      json_out['return_val'] = hook(**hook_input['kwargs'])

                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^

    File

"/Users/wadat/Desktop/Tutorials/Scripting/Resolve_Script2.5.10_mac/bin/python-3/lib/python3.12/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py",
line 118, in get_requires_for_build_wheel
      return hook(config_settings)

             ^^^^^^^^^^^^^^^^^^^^^

    File

"/private/var/folders/dy/5gctb17102l3gdy2jb8l50rw0000gn/T/pip-build-env-1doujy9e/overlay/lib/python3.12/site-packages/setuptools/build_meta.py",
line 325, in get_requires_for_build_wheel
      return self._get_build_requires(config_settings,

requirements=['wheel'])
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File

"/private/var/folders/dy/5gctb17102l3gdy2jb8l50rw0000gn/T/pip-build-env-1doujy9e/overlay/lib/python3.12/site-packages/setuptools/build_meta.py",
line 295, in _get_build_requires
      self.run_setup()

    File

"/private/var/folders/dy/5gctb17102l3gdy2jb8l50rw0000gn/T/pip-build-env-1doujy9e/overlay/lib/python3.12/site-packages/setuptools/build_meta.py",
line 480, in run_setup
      super(_BuildMetaLegacyBackend,

self).run_setup(setup_script=setup_script)
    File

"/private/var/folders/dy/5gctb17102l3gdy2jb8l50rw0000gn/T/pip-build-env-1doujy9e/overlay/lib/python3.12/site-packages/setuptools/build_meta.py",
line 311, in run_setup
      exec(code, locals())

    File "<string>", line 17, in <module>

  ModuleNotFoundError: No module named 'imp'

  [end of output]

note: This error originates from a subprocess, and is likely not a
problem with pip.
error: subprocess-exited-with-error
× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a
problem with pip.
[notice] A new release of pip is available: 23.2.1 -> 23.3.2
[notice] To update, run: pip install --upgrade pip
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.
[Process completed]
On Sat, Feb 3, 2024 at 12:05 AM nakano000 @.***> wrote:

Please let me know the error message displayed.
—
Reply to this email directly, view it on GitHub
https://github.com/nakano000/Resolve_Script/issues/13#issuecomment-1925153190,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVZWSMKYORDCTEPCSJZYKW3YRXHSFAVCNFSM6AAAAABCWCIVWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRVGE2TGMJZGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

It was reported before that putting it on Desktop does not work.
Please try it under HOME.

changed the directory and that error has gone but the app still doesn't
work. See a link to the video below.
https://youtu.be/g9SGPtQ8G44
On Sat, Feb 3, 2024 at 12:22 AM nakano000 @.***> wrote:

It was reported before that putting it on Desktop does not work.
Please try it under HOME.
—
Reply to this email directly, view it on GitHub
https://github.com/nakano000/Resolve_Script/issues/13#issuecomment-1925158966,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVZWSMPS43GEBPPP6SKBOTTYRXJQZAVCNFSM6AAAAABCWCIVWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRVGE2TQOJWGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

It seems that the previous file remains
Please start over from UnZip.


Instructions incomplete (Android Studio 1.0.2, novice AS user)

On Android Studio 1.0.2, following the instructions leaves me with these problems:

Running the tests via gradle works, but running them via Android Studio's Run>Run... gives me this failure:
```
!!! JUnit version 3.8 or later expected:

java.lang.RuntimeException: Stub!
```

Note: I am running Java 1.8 ("1.8.0_25")

When the project view is showing "Android", the DeckardActivityTest (and its whole tree) doesn't show up, as shown here.

You can see the class's whole tree when that button thingee at the top left is changed to "Project". However, that source tree has none of the Jetbrains magic applied to it. (imports aren't automatically generated, syntax errors aren't flagged, New doesn't give you the option of creating a new class, etc.)

I was planning to update the documentation and write a pull request, but I don't know enough to fix these.
Note: Android Studio install forced the installation of Android SDK 24.0.2, Android SDK Platform Tools 21, and Android SDK Build Tools 21.1.2. Also Android 5.0.1 (API 21). I installed API 19 myself.
Suspecting the problem might be API 21, I tried removing it, which caused Android Studio to (1) still not be able to run the tests, and (2) caused "internal error, please report" messages. I reinstalled Android Studio from scratch, and reproduced the problem up until the point of removing 21. I'll try that again, if instructed.

I recently ran into the same problem with a different project.  This is happening because of your classpath  - Android comes first, which contains the old jUnit.  But these tests probably require jUnit 4.0.  To fix it, go to the Project Structure dialog in Android Studio and change the order of dependencies.
This is explained here in Stack Overflow for IntelliJ, but same principles apply.
http://stackoverflow.com/questions/2422378/intellij-idea-with-junit-4-7-junit-version-3-8-or-later-expected

That works to solve the first problem, thanks. As for the second problem, it seems it might be solved by AS 1.1beta. Will try.

AS 1.1-beta4 has unit test support baked in. Looks like it's heading in the direction of eliminating the need for Robolectric.
Interestingly, when you follow their instructions, AS knows that /test/java/... contains Java code, but it no longer knows that AndroidTest/java does.

Here's the link to 1.1-beta4 testing: http://tools.android.com/tech-docs/unit-testing-support

Very interesting! Thanks for passing that along. Do you think Android Studio / grade will be able to keep unit tests separate from instrumentation tests? Like keep them in separate folders or would it have a different gradle command to invoke unit tests separately from instrumentation?  I would hate to see a command that runs all tests regardless, that wouldn't be helpful in my environment.

@RichardGuion No idea.

@RichardGuion @marick Just looking at switching deckard to work with Studio 1.1 here. It seems like there is some weirdness with having to switch build variants to run either Espresso or Robolectric tests but there is finally no need for a gradle plugin to make everything work.


in 应该有最低优先级

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS, ArchLinux, Debian]
Runtime  Version [e.g. Graalvm, Oracle JRE, Android]
Version [e.g. 1.0]

Smartphone (please complete the following information):

Device: [e.g. Nexus6]
OS: [e.g. AndroidO, MIUI]
Browser/Dalvik Version [e.g. SystemWebView, Legacy]
Version [e.g. 1.0]

Additional context
Add any other context about the problem here.

Fixed in https://github.com/duangsuse/Lite/commit/3998dbd76b6f3e2b13e14e3d0b6d3ef57ee23b8e


Research Using Button Board for More Input

For some games, it may be beneficial to have more than the limited number of buttons on the gamepad. Some teams overcome this by using a button board.  A button board simply maps a bunch of physical buttons as another custom joystick.
Here's some documentation on how to use the controller that we have:
MSP430 LaunchPad Operator Interface for FIRST Robotics Competition
In the 2018 preseason, we will try to learn more about button boards and possibly create a general button board for future use.

@TechplexEngineer @jaredbotte is this something we're still considering as an option?

There is nothing on the to buy list.

Just wanted to check in if that was something we should add.
I'll close this for the time being, as it seems unlikely with our current schedule.
I'd say these are the ones to use, if we decide to come back to this later:
http://www.leobodnar.com/products/BU0836X/
http://www.leobodnar.com/shop/index.php?main_page=product_info&cPath=94&products_id=205


Adding changes for having JSON instead of XML

@jesuspg @jframos

What is the difference between this PR and #260?


Incorrect positions / interactive path on mutiple variable declaration

Compiler version
3.5.0
Minimized code
val xx, yy, zz = 1

Output
[[syntax trees at end of                     typer]] // demo.scala
package<EMAIL_ADDRESS>{
  final lazy module val demo$package<EMAIL_ADDRESS>=
    new demo$package@demo.scala<0..0>@demo.scala<0..0>@demo.scala<0..0>()@
      demo.scala<0..0>
  @demo.scala<0..0>
  final module class demo$package() extends<EMAIL_ADDRESS><EMAIL_ADDRESS>{
    this: demo$package<EMAIL_ADDRESS>=>
    val xx: Int = 1<EMAIL_ADDRESS>    val yy: Int = 1<EMAIL_ADDRESS>    val zz: Int = 1<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
Problem
Start and end position for all definitions are the same. This leads to incorrect Interactive.pathTo for position on xx or yy definition -- head being zz definition.
Expectation
I would either expect positions on multiple declaration to be solved as in Scala 2 (though this is also buggy there):
xx -- `4..18`
yy --`8..18`
zz -- `12..18`

or for Interactive.pathTo to account for that situation.

Isn't there namePos in dotty?

Isn't there namePos in dotty?

Yes there is. But Interactive.pathTo won't use that in any way... Or am I missing your point?


update example notebooks

In the docs branch I'm taking a different approach. The problem with having an examples folder is that they become outdated every time we make even minor API changes. Instead I am going to include the examples in the docs folder, which are executed every time we build the docs. Read-the-docs will build them every time we update the repo, so we can ensure that they are always executing correctly, and also includes them in the documentation.

Great!

The examples are now available in the docs at http://scarlet.readthedocs.io/en/latest/.


Garage controller accessory shows up as generic switch

Hi-
Thanks for your efforts.
Using yolink plugin v 1.3, setup as child bridge on Docker/Synology.
Under Accessories (Homebridge UI) tab - do not see garage controller accessory. Garage controller, sensor, and battery level displayed separately for ungrouped devices. For 1 grouped set (garage controller and sensor) only see a switch listing.
Also, same findings on HomeKit. Controllers are displayed/behaving as simple switches.
I think the expected behavior is to show open-closed-state, opening-closing transition state, and display as garage door.
Tried removing and reinstalling child-bridge accessory / resetting the hub on HomeKit.
Any ideas?

Have you setup the garage door sensor and controller in the config file (or with the config UI)?  You should have something that looks like this..
"garageDoors": [
                {
                    "controller": "0123456789abcdef",
                    "sensor": "abcdef0123456789",
                    "timeout": 45
                }
            ]

If you have not assigned a controller and sensor to a garage door as above then yes, each device will show separately.
If you have that, then l need to see whether there are any errors or warnings in the log file.
Thanks

I have one controller/sensor set grouped and another without. The grouped item displays as one unit (without sensor) but acts/displays as a switch, and doesn't provide state info.
Log file attached.
homebridge.log.txt
Thanks for helping.

The clue is in this log file message...
[10/5/2022, 11:37:08 AM] [YoLink] Garage Door must have two known devices. Ignoring this door:
{"controller":"d8864c010003f92e","sensor":"d88b4c020006740a"}

You mistyped the UID for the controller... value in position 4 is wrong.  This line should have appeared in the homebridge log viewer highlighted in orange to draw your attention.

Hi-
Reentered UID and all work as expected. Issue resolved.
Thanks again for doing this project and helping me troubleshoot.
Cheers


[Merged by Bors] - chore: bump std

Since this bump does not include https://github.com/leanprover/std4/pull/427 (in order to avoid having to handle the intermediate commits all at once), we temporarily remove the single use of a ∀ i ∉ s, binder, and the two tests of it.
We can revert these changes in a later Std bump, once we've address the other awkward bumps inbetween.
This unblocks #8711.

That seems ready to go. :smile:

bors merge

Note this broke two new uses of ∃ a ∉ s, in #8892 that should therefore be fixed too when we gain back the nice binders. The uses are Set.ssubset_iff and Finset.ssubset_iff.

Note this broke several new uses of ∃ a ∉ s, in #8892 that should therefore be fixed too when we gain back the nice binders. Look for ∃ a, a ∉ s ∧ to find them.

I've fixed these again in #8888.


Revert "At -Onone preserve debug info after splitting loads"

This reverts commit 02f7450759c992682ed3f149914bd2ecf4dec071.
Fixes rdar://104667596 (incorrectly reports an error when resolving initialization out of a switch)

The only failure is: linux-x86_64 SIL/verify_all_overlays.py: error: cannot load underlying module for 'CxxStdlib'
A known issue: https://github.com/apple/swift/pull/63243

@swift-ci smoke test linux


NServiceBus message correlation

This pull request includes the following:

added envelop mapping for CorrelationId into NServiceBus interop
added correlationId checks into InteropTests

Great timing Michael, I was in the midst of making the next release! This will be in 1.8.1 by tomorrow.
@misha-p ^^^


Windows High Contrast Mode / forced color adaptations

Proposal
Adding a few surgical, very specific general styles to Bootstrap using the (forced-colors) media query, to make sure that some of our components that aren't properly discernible in Windows High Contrast Mode stand a slightly better chance at having at least minimal styles applied even in WHCM.
Motivation and context
Splitting the idea out of https://github.com/twbs/bootstrap/pull/29490
A lot of the standard Bootstrap styles rely on background colours, borders and shadows (e.g. to make buttons/pills/etc look "button-like"). These styles usually get completely overridden by Windows High Contrast Mode (WHCM), which explicitly ignores things like background and forces specific user-defined colours for things.
Until recently, there was no clean standardised way of approaching this issue (even with proprietary things like -ms-high-contrast - see https://www.tpgi.com/windows-high-contrast-mode-the-limited-utility-of-ms-high-contrast/)
However, the relatively new (forced-colors) media query offers a relatively stable way of approaching this issue now, adding very targeted adaptations/tweaks for cases where WHCM is enabled.
I have recently been playing with it on a project (not directly using Bootstrap, but the concept is obviously the same) to force an outline (rather than a border, so it doesn't affect element dimensions), a la
@media (forced-colors) {
  button {
    outline: 1px solid LinkText !important;
  }
}

Trying to do further/more intense styling is probably counterproductive (i.e. not doing a whole exercise like dark mode or anything), but just some basics like this would immediately make BS more WHCM-friendly for very little extra effort.

Hi  @patrickhlauke, are you aware of a shared gist or other source that gathers together the forced-color adaptions that aren't yet accepted into upstream Bootstrap? I'm looking at adding them to a Bootstrap 4(.6) project and if one doesn't exist I might create it as it seems generally useful and shareable, rather than project specific.

i don't think there's a single collated list at the moment. would suggest, if you can find the time, going through the docs pages and trying to identify all the different places where currently forced colors/WHCM is not ideal (in terms of borders, outlines, etc not showing up)

I've started a gist here, I'll try to remember to update it as I test and find issues:
https://gist.github.com/davidscotson/446f5a637715af9d1db832f60640e705

Taking https://getbootstrap.com/docs/5.2/examples/cheatsheet/ for a quick spin in high contrast (Windows 10 WHCM, Chrome):
Forms
Overview

checked checkbox, selected radio button, shows no focus indication

switch checkbox input: when not checked, only shows outline border; when focused, shows faint off switch; when checked, has no focus indicator

example range totally invisible

Floating labels

floating label doesn't hide placeholder text; when focused, shows awkward focus outline

Validation

"Agree..." checkbox shows no focus indication

Components

Accordion shows no focus indication

Alerts

No visible X close control, no focus indication for it

Badge

Shows no outline/border

Carousel

Dots look awkward/wrong

Dropdowns

Down arrow looks wrong
Focus indication on active dropdown item not shown

Modal

No visible X close control, no focus indication for it

Navs

doesn't show active one

Navbar

First example, logo doesn't show

Pagination

Current active one not shown

Popovers

Arrow looks awkward/wrong

Progress

Bar is totally invisible

Spinners

Completely static circles

Toasts

No visible X close control, no focus indication for it

Tooltips

Arrow looks awkward/wrong

A few other examples not covered in the cheatsheet:

toggle buttons https://getbootstrap.com/docs/5.2/components/buttons/#toggle-states don't visually differentiate active one

checkbox/radio button group https://getbootstrap.com/docs/5.2/components/button-group/#checkbox-and-radio-button-groups don't differentiate checked/unchecked

as already seen in the alert and modal above, close button https://getbootstrap.com/docs/5.2/components/close-button/ doesn't show at all (except for its white variant)

Another thing I didn't see in previous comments is the fact that you can't see the checked state of the checkboxes when viewed in certain themes, such as High Contrast White in Windows 10 and  Desert High Contrast in Windows 11.  You can find an explanation of the issues I found with this control and my proposed solutions in this CodePen:
Fixing Accessibility of Bootstrap's Checkbox Styling
This is easy to miss, because it doesn't show up when checking with darker themes, which is all most people test with.
I'm not sure, but I think I remember there being similar issues with the radio buttons.

I spent a lot of time going through the components and have created a forced-colors: active stylesheet which fixes just about all issues I could find in both dark and light high contrast themes. Tested with Edge on Windows 11.

GitHub repo: https://github.com/coliff/bootstrap-forced-colors-css
npm: https://www.npmjs.com/package/bootstrap-forced-colors-css
Demo: https://coliff.github.io/bootstrap-forced-colors-css/tests/

Some fixes made are a bit opinionated, e.g. increasing border width from 1px to 2px on form inputs to counter the fact that there is no box-shadow. It'd be great to see some/most of these fixes be made to Bootstrap in the future. For now though, users can use this stylesheet to improve things for Windows users with High Contrast themes.
<link
  rel="stylesheet"
<EMAIL_ADDRESS>  media="screen and (forced-colors: active)">

Testing with Forced Colors Mode Emulation in Chrome / Edge


[analyzer] redundant nullable variable

For a code like:
void f(int x) {
  int? i = x;
}

i is always not nullable.
Would it be helpful to have a hint about this redundancy?

It is already being handled in the following sense: When a variable has a nullable declared type and it has an initializing expression whose type is the corresponding non-nullable type, then the variable is immediately promoted. Spec language here.
This means that subsequent code will be able to use i with the non-nullable type (such that i.isEven is not a compile-time error), as long as it isn't demoted (as it would be, e.g., after i = null). So it could be argued that the situation isn't much of a problem: The variable has the "nice" type anyway, and we're assuming that the developer has the intention that null could be assigned to i at some point.
It could be argued that there should be a diagnostic message to suggest that a local variable x with declared type T should should be changed to have declared type S, where S is the least subtype of T which will not cause any expression in the entire scope of x to become a compile-time error, if any such type exists.
However, that could be a bad idea: It is often recommended that local variables are declared with a somewhat abstract type (for instance, in Java code, it's commonly considered better to use List<...> than ArrayList<...> as the type of a local variable—and in Dart we've hidden the concrete list implementation types so well that there is no debate about that question at all).
In summary, it would be possible to flag situations like this, but there are multiple reasons why it might not be needed so urgently.

I mostly agree with that, though I have to wonder whether nullability might be slightly different than the more general case from the user's perspective.
If we were to add something we would probably want to make it a lint so that interested users could opt in to this kind of information, but users that don't care won't be bothered.


fixed rate irm

Fixed rate IRM for Morpho Blue. Anybody can set the rate for a market but it can be set only once. Typical use case is that the market creator batches the creation of the market with the fixed rate IRM with the setting of the rate they want for it on the IRM.
Note that this IRM probably doesn't make sense alone, as a lending pool with fixed IRM faces illiquidity risks. It will be used to experiment with different stuff  like terms on blue.
This IRM makes market creators vulnerable to a griefing attack: for an oracle, you can set the rate for all the markets that make sense with this oracle, making these markets that could have been created in the future ususable. Meaning that now to create a market with the same pair of assets (with a different LLTV for example) you might have to re-deploy the oracle because a malicious actor could have set the rate already.

Tests are failing :/

not anymore :-) (weird rounding in adaptive curve irm when fuzzing that i can't reproduce locally, but not impact). Will open an issue to investigate


Azure AppStack remains 'Waiting for Registration'

The appstack instance was still waiting for registration twenty minutes after the other sites were online.
command
terragrunt run-all apply
git
c165dff (HEAD -> main, origin/main) Merge pull request #20 from mjmenger/azure-appstack

deleted the terragrunt cache, tried apply again, and had a successful result


github workflows

Add github workflows to have CI for format/lint/unittest.
Also add the vu.lock because thats required for the github actions. (use it to determine if vu cache can be used)

Moved to the correct project: https://github.com/carlovoSBP/crave_all_the_money/pull/1


Replace Cherow by Babel or Acorn in Node Loader Bootstrap.js

🚀 Feature
The idea of this is to get rid from cherow and implement a fully standard compliant parser with latest ES standards. The cherow library is already deprecated.
Is your feature request related to a problem?
Not yet, but as this library is deprecated, we will have problems supporting new standards.
Describe the solution you'd like
Any of the aforementioned will be enough. Speed is important but to be standard compliant is has a higher priority in the list.
Describe alternatives you've considered
Babel: https://github.com/babel/babel
Acorn: https://github.com/acornjs/acorn
There's an important requirement which is, whenever selection we do, it should be able to be packaged in a self contained manner, without any dependencies. This is very important because for packaging npm packages in Guix it's a nightmare.
We should end up with something like this: https://github.com/metacall/distributable/blob/e3c07dcd22292283645450e7beb35292a0d38545/source/metacall.scm#L90
Additional context
For more information, check the current cherow implementation:

Include: https://github.com/metacall/core/blob/4baa35658e316ba8848a2bf966ec09197a7bfef6/source/loaders/node_loader/bootstrap/lib/bootstrap.js#L10
Parsing: https://github.com/metacall/core/blob/4baa35658e316ba8848a2bf966ec09197a7bfef6/source/loaders/node_loader/bootstrap/lib/bootstrap.js#L238

The implementation is a little bit tricky because it loads first the functions and then converts them to string in order to get the type info. Maybe we can improve this.

@trgwii suggested https://github.com/eslint/espree
I think it may be a better alternative, but it must be investigated.


Cannot access static members of model with .schema() call

Versions

sequelize: 5.21.5
sequelize-typescript: 1.1.0
typescript 3.8.3

I'm submitting a ...
[ x ] bug report
[ ] feature request
Actual behavior:
When you call .schema() method of model then call static member typescript says that member doesn't exist.
Expected behavior:
Ability to use static members of model without warnings.
Steps to reproduce:
You need model with static member defined, call schema method of it and then try to use any static member.
Related code:
const model = ModelWithStaticMethodDefinied.schema('blah');

model.staticMethod();

FYI:
It might be easy fixed by adding schema method to model definition:
static schema<T>(this: NonAbstract<T>, schema: string, options?: SchemaOptions): NonAbstract<T>;

Hey @kacepe, thanks for reporting. For me in is working very well. sequelize-typescript uses the official typings and schema is already defined there. See this https://github.com/sequelize/sequelize/blob/master/types/lib/model.d.ts#L1626

@RobinBuschmann Idk how it can works for you.
Here is a code example:
https://repl.it/repls/FrequentLostGraphicslibrary

Ah sry, I didn't understand it in the first place. Now I see. Anyways, this need to be fixed in the official sequelize typings: https://github.com/sequelize/sequelize/blob/master/types/lib/model.d.ts#L1626

Closing this since it isn't an issue with sequelize-typescript but an issue with sequelize.


Pull request template is not working

Pull request template is not being applied. I guess we are not following the naming convention correctly.
https://docs.github.com/en/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository

Fixed on master.
As an extra note - I want to simplify/make less verbose the PR template. Will make a PR to that soonish.

Fixed on master.
As an extra note - I want to simplify/make less verbose the PR template. Will make a PR to that soonish.


Add release notes for version <IP_ADDRESS>-beta1

Signed-off-by: Tyler Ohlsen<EMAIL_ADDRESS>Description
Adds release notes for <IP_ADDRESS>-beta1
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

I propose we remove anything that's not actually meaningful to the release?

Guidance before has been to include all commits, regardless of how meaningful they are, to the release notes. We may bring this discussion up again if we want to filter out certain commits.

I propose we remove anything that's not actually meaningful to the release?

Guidance before has been to include all commits, regardless of how meaningful they are, to the release notes. We may bring this discussion up again if we want to filter out certain commits.

I'll approve for now, but to me that makes little sense for a 1.0 release.


MWPW-143405: table-of-contents block

Describe your specific features or fixes
Resolves: MWPW-143405
Test URLs:

Pre Migration Link: https://adobe.com/express/learn/blog/what-is-shopify
Before: https://main--express-milo--adobecom.hlx.page/express/learn/blog/what-is-shopify
After: hhttps://rl-adobe-table-of-contents--express-milo--adobecom.hlx.live/express/learn/blog/what-is-shopify?martech=off

Codecov Report
Attention: Patch coverage is 0% with 16 lines in your changes are missing coverage. Please review.

Project coverage is 23.01%. Comparing base (b35d73c) to head (e4cc6a9).
Report is 1 commits behind head on main.

Files
Patch %
Lines

express/scripts/utils.js
0.00%
16 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #20      +/-   ##
==========================================
- Coverage   24.44%   23.01%   -1.44%
==========================================
  Files           1        1
  Lines         225      239      +14
==========================================
  Hits           55       55
- Misses        170      184      +14

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Update zio-interop-cats to 3.3.0-RC3-2

Updates dev.zio:zio-interop-cats from 3.3.0-RC1 to 3.3.0-RC3-2.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "dev.zio", artifactId = "zio-interop-cats" } ]

labels: library-update, early-semver-pre-release, semver-spec-pre-release, commit-count:1

Superseded by #52.


Gammagard-liquid hero tag-line should be orange

This is for the first line below the logo. Hex should be #f89a38 = var --gammagard-liq:

Screenshot from live site


Bump nginx-php-fpm-local version to v0.8.2

The Problem/Issue/Bug:
We had a nightly build failure caused by docker.nginx-php-fpm-local due to our pinning of php7.1. This bumps docker.nginx-php-fpm-local to v0.8.2
This should pass after @cweagans docker-pushes v0.8.2 but will fail right now, but that's OK. We'll just rebuild after that. I just wanted to get the PR up.
How this PR Solves The Problem:
Manual Testing Instructions:
Automated Testing Overview:

Related Issue Link(s):
Release/Deployment notes:

The new image has been pushed. Any way to force a rebuild?

👍

Randy said to merge this.


[BUG]: Better way to handle if conditions

Report hasn't been filed before.

[X] I have verified that the bug I'm about to report hasn't been filed before.

What version of drizzle-orm are you using?
0.27.0
What version of drizzle-kit are you using?
0.36.0
Other packages
No response
Describe the Bug
Suppose my route has an optional parameter minDate and I want to have a query like:
gte(orders.createdAt, minDate).if(minDate)

This code does not work since minDate is sometimes undefined. This forces me to add ! in the gte function. This seems like a bad pattern.

You can refer to the examples given in the official documentation。 Compose a WHERE statement and then use it in a query
async function getProductsBy({
  name,
  category,
  maxPrice,
}: {
  name?: string;
  category?: string;
  maxPrice?: string;
}) {
  const filters: SQL[] = [];
  if (name) filters.push(ilike(products.name, name));
  if (category) filters.push(eq(products.category, category));
  if (maxPrice) filters.push(lte(products.price, maxPrice));
  return db
    .select()
    .from(products)
    .where(and(...filters));
}

This completely disregards the original post. My issue in relation to the .if API.


[8.x] Adds If method for Collections

Overview

This is a successor to PR #35570, which would have been a breaking change.

This adds an if method to Collection. This is essentially the same as when and unless, just that the parameter to be passed is always a callable. The check is passed the current Collection to evaluate:
collect(['taylor', 'adam'])->if(fn($names) => $names->contains('taylor'))->concat('poppy')

// ['taylor', 'adam', 'poppy']

Benefits/Usage
Often when working with a Collection, it would be useful to inspect the current state of the data and then act accordingly. Otherwise, a temporary variable is required, the pipe method is required, or some other solution. This is especially so when the inspection is desired before the interaction with the Collection is finished.
Say we want to report a low quote count for an Api response before mapping over them. Currently, it might look like this:
$quotes = Api::getQuotes()->reject(fn($quote) => $quote->isExpired())

if ($quotes->count() < 3) {
    $this->reportLowCount($quotes)
}

$quotes = $quotes->map('...')

With a callable that can inspect the current state of the Collection, it can become:
$quotes = Api::getQuotes()
               ->reject(fn($quote) => $quote->isExpired())
               ->if(fn($quotes) => $quotes->count() < 3, fn($quotes) => $this->reportLowCount($quotes))
               ->map('...')

Granted, this is a simplistic example, but I hope it illustrates the usages possible.
Testing/Compatibility
Tests have been added to SupportCollectionTest. These imitate the existing when and unless tests for functionality.
Unlike the previous PR, this should not be a breaking change.
Pros/Cons of a new method
As seen in the previous PR, updating when and/or unless for this functionality is a breaking change. As the use case of this functionality is perhaps limited, it seems the break might not justify the update?
Which is why this PR targets 8.x with a new method that utilises when:
public function if(callable $check, callable $callback = null, callable $default = null)
{
    return $this->when($check(clone $this), $callback, $default);
}

Which means it can even be used as a higher order function.
But, it is just a wrapper around when, which could just be macroed in projects that desire this functionality. Therefore, it might be deemed that adding a new method is not justified. Plus, I appreciate the name if might be somewhat ambiguous.
Summary
I think it would be a really useful addition to have this option to inspect the Collection. When combined with the higher order function available for the underlying implementation of when, it should make for clean and expressive code.
p.s. This will be the last PR on this topic unless requested otherwise!

I think we already have when Method in collection.

For now why don't you use the pipe method to accomplish what you want. It's not quite as obvious but I don't really want to introduce another when style method:
$collection->pipe(function ($collection) {
    if ($collection->count() < 3) {
        ...
    }
})

Thank you for the feedback and assistance 👍


How to generate report with zero impressions along with segments.Date  ?

The query listed below , returns rows containing non-zero values for "metrics.impressions" column. However if I remove "segments.date" from the select statement , all the records , including ones that contain zero "metrics.impressions" value are returned.
string query =                 $@"SELECT 	                 ad_group_ad.ad.id, 	                 campaign.id, 	                 segments.date, 	                 metrics.impressions, 	                 metrics.clicks, 	                 metrics.cost_micros,                          metrics.average_position,                 FROM 	                ad_group_ad                 WHERE segments.date BETWEEN '2019-04-17' AND '2019-04-28'
I want to retrieve all the "metrics.impressions" rows by "segments.date". What should I do to modify the query listed above to return zero "metrics.impressions" rows along with "segments.date" value?

I don’t think it can be done, IIRC zero impression rows are incompatible with date segments even in the old API.
Could you post this question on https://groups.google.com/forum/m/#!forum/adwords-api also, sonce this question is not specific to .NET library?


#3898 add pod disruption budgets

Signed-off-by: Raymond Phua<EMAIL_ADDRESS>
Pull Request Motivation
This PR should fix the request in the following issue: https://github.com/cert-manager/cert-manager/issues/3898

Kind
Feature

Release Note

Support added for PodDisruptionBudgets

/retest

/assign @wallrj

Hello, it's been 3 weeks. Could someone look at the changes made to support PDBs for certmanager? @wallrj @yongk802

Thank you for the contribution.
I think we already have an open PR that makes this same change (and is currently blocked on some discussion). Please feel free to upvote that PR #3931


Request to be removed from Deny List

Hotspot Name
Rapid Powder Iguana
Hotspot b58 Address
11hWNEHCsGwex8FgQ4FqfuYdxa68fDCuqAjU9VYjUpnesSg758v
Discord Handle
#1776
Hotspot Manufacturer
PantherX 2
Removal Reason
I bought 6 blacklisted PantherXs in the second-hand market of salted fish in China. I didn't want to buy 6 units at a time. The seller said that the price is cheap to buy them all together. In the end, each set was sold for 2000 CNY. I bought a lot of accessories and DIY. , Install 3 units first, then find a suitable place to install others or sell them. These 3 units were installed on the roof of a friend's apartment and a company, using POE power supply and transmission network, and waterproof treatment. 3 The platform has all been installed and requested to be removed from the rejection list. Thanks to the team for their efforts to maintain the healthy development of the helium network, thank you!
Modifications
No
Extra forwarders
No
Extra antennas
No
Additional Information

We have taken into account this removal request in the next iteration of the denylist. It may take some time before it's processed. This is an automated comment due to the volume of addition and removal requests. A future tool is in the works to provide more insight into the analysis approach made by the Helium team and community members that maintain this list.

Thank you team for your hard work, I will try my best to maintain helium


⚠ Secret Website 3 has degraded performance

In bf1029a, Secret Website 3 ($SECRET_WEBSITE_3) experienced degraded performance:

HTTP code: 200
Response time: 2136 ms

Resolved: Secret Website 3 performance has improved in 53c6197.


Provide demo

Is there a demo on the web for this? The documentation says I can look in the demo folder in the repo- but I'd rather not download the repo and all its dependencies to see it.

Found it here: http://shoppinpal.github.io/ng-mobile-menu/demo/#/skinny. Perhaps adding this to the Readme.md would be good.

@SyntaxRules - the original author of this code is now using https://github.com/dpiccone/ng-pageslide and this is no longer under development, please consider switching.


fix: file-validation-display

Types

[x] 🐛 Bug Fixes

Background or solution
closes https://github.com/opensumi/core/issues/628
before：

there is css classname which should be removed if the validation has been triggered before.
Changelog
fix file validation display

Codecov Report

Merging #642 (a55a5b7) into main (6e57e9d) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #642      +/-   ##
==========================================
+ Coverage   58.98%   58.99%   +0.01%
==========================================
  Files        1209     1209
  Lines       74645    74649       +4
  Branches    15464    15468       +4
==========================================
+ Hits        44028    44041      +13
+ Misses      27915    27907       -8
+ Partials     2702     2701       -1

Impacted Files
Coverage Δ

...components/src/recycle-tree/prompt/PromptHandle.ts
90.84% <100.00%> (+0.26%)
:arrow_up:

...erences/src/browser/preference-settings.service.ts
79.86% <0.00%> (+0.69%)
:arrow_up:

...kages/theme/src/browser/workbench.theme.service.ts
72.10% <0.00%> (+0.89%)
:arrow_up:

packages/core-common/src/node/port.ts
45.45% <0.00%> (+1.51%)
:arrow_up:

...ages/file-service/src/node/file-service-watcher.ts
72.88% <0.00%> (+1.69%)
:arrow_up:

packages/monaco/src/browser/schema-registry.ts
71.11% <0.00%> (+2.22%)
:arrow_up:

Continue to review full report at Codecov.

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


additional tests for get_template_setting

Coverage decreased (-0.03%) to 71.037% when pulling<PHONE_NUMBER>59b1b1deff92d5a1a0980e01401ada on kuter:additional_tests_for_compat into cb66b31d287bbd14a08b03b2a311bb96d28ce473 on django-extensions:master.

Coverage decreased (-0.03%) to 71.037% when pulling<PHONE_NUMBER>59b1b1deff92d5a1a0980e01401ada on kuter:additional_tests_for_compat into cb66b31d287bbd14a08b03b2a311bb96d28ce473 on django-extensions:master.

Coverage decreased (-0.03%) to 71.037% when pulling<PHONE_NUMBER>59b1b1deff92d5a1a0980e01401ada on kuter:additional_tests_for_compat into cb66b31d287bbd14a08b03b2a311bb96d28ce473 on django-extensions:master.

Thanks !


New reloader mode

The reloader is awesome however depending on the IDE configuration you could end up having a project that reload automatically because the IDE will changes the files mtime.
I suggest adding a reloader type, that use the file size instead of the mtime, I've tried and it works like a charm.
class SizeReloaderLoop(ReloaderLoop):
    name = "size"

    def __enter__(self) -> ReloaderLoop:
        self.sizes: t.Dict[str, float] = {}
        return super().__enter__()

   def run_step(self) -> None:
        for name in chain(_find_stat_paths(self.extra_files, self.exclude_patterns)):
            try:
                size = os.stat(name).st_size
            except OSError:
                continue

            old_size = self.sizes.get(name)

            if old_size is None:
                self.sizes[name] = size
                continue

            if size > old_size:
                self.trigger_reload(name)

I don't plan to maintain more reloaders at this point, it's hard enough with the current behaviors. You can add this to the reloader loops in your project if you'd like to use it:
from werkzeug._reloader import reloader_loops

reloader_loops["size"] = SizeReloaderLoop

Then you can do run_simple(..., reloader_type="size").
Note that this is all internal, so it's the user's responsibility to pin versions and adapt to changes.

If you IDE touches files that haven't been modified, I'd report that as a bug in the IDE.

BTW, your size reloader has a bug - it should be != and not > since removing something from a file is certainly a reason to trigger a reload.

BTW, your size reloader has a bug - it should be != and not > since removing something from a file is certainly a reason to trigger a reload.

Indeed, many thanks to both of you, perfect and quick answers !


ui: the box on the bottle should not hide log contents

The box on the bottle should not hide log contents
version:  0.3.0 (go1.9.1)

The box on the bottom of the UI


Eliminate HasPureRunner typeclass

Replace the HasPureRunner (Apropos.Pure) with a datatype:
data PureRunner p m = PureRunner
  { expect :: Formula p
  , script   :: m -> Bool
  }

Update the examples:

Replace the HasPureRunner instances with (named) PureRunner objects
Update calls to runPureTestsWhere

Update documentation

You may find draft PR #32 useful to get you started.

Just to make it clear for the issue: this would allow multiple runners to be defined per module. Any other benefits, @AriFordsham ?

That's the biggie. I feel it is cleaner, more idiomatic design, and easier to implement and use, but others may differ.

Bonus points for coming up with a more descriptive name than PureRunner. maybe Model or similar?

I always liked PureRunner. Sounded very cyberpunk IMO :joy: any suggestions @delicious-lemon @Geometer1729 ?


Cannot set properties

Cannot call set_text:
Can't set text: No named arguments. (0x80020007)

fixed by #5


Investigate performance to establish if DOM rendering is going to be possible for large runs

We should investigate the perf of the app on the client to see where the hold ups are

This was over a period of about a minute. If I'm reading this right, a lot of the time is PubSub publishing messages but many of the other methods seem to be the react-dom-debugging stuff>
I've attempted to produce a production build to take the debug stuff out of the equation but have hit an error:
c:\github\gareththegeek\corewar-ui>npm run build

><EMAIL_ADDRESS>build c:\github\gareththegeek\corewar-ui
> react-scripts build

Creating an optimized production build...
Failed to compile.

Failed to minify the code from this file:

        ./node_modules/corewar/dist/index.js:1662

Read more here: http://bit.ly/2tRViJ9

Hmm, setTimeout perhaps?

Further investigation seems to point to the rendering of dom elements and possibly even the early exit from shouldComponentUpdate method when many state changes are performed.

Discussion with @gareththegeek leads us to believe avoiding redux state for the canvas rendering would be most sensible to avoid all the react hooks.
I've also discussed some of the more redux'y considerations on this the back end of this issue with some really useful information.
https://github.com/reactjs/redux/issues/758#issuecomment-349470124

Closed as now using canvas


Dependency issue with bare installation

When installing on react native app , I got dependency issue. Please refer below image

Reset the expo shell

Issue in react native cli mode app not expo app, I am getting expo-file-system not found error in react-native cli app

It happens to me too.
I'm not gonna use expo and it has supported for bare project until 1.2.0, but after 1.3.0 the expo-file-system dependency was added, it forces me to change or rebuild my bare project into expo-based project.
It seems that the code was added on #107 to fix #57 to serve jszip & epubjs locally.
I think the code for serving jszip & epubjs should use FileSystem on @epubjs-react-native/file-system or @epubjs-react-native/expo-file-system, not expo-file-system directly.

Hi guys, I'm already working on a solution for this and it should be out in the next few days! Sorry for the delay


Compiling on MacOS M1

Do you have any idea how to or instructions for compiling on an M1 Mac?
I've been trying to build with cmake but I keep running into lots of errors. Do you have any hints?
Thanks!

Did you use vcpkg?
Also try use GitHub Actions, iirc there's an Apple M1 option.

vcpkg worked. I haven't used that before but for others who might want to do the same, I did:
git clone https://github.com/LagPixelLOL/ChatGPTCLIBot.git
cd ChatGPTCLIBot
cd main/interface/
rm -r clip
git clone https://github.com/dacap/clip.git
cd ../..
git clone https://github.com/Microsoft/vcpkg.git
cd vcpkg
./bootstrap-vcpkg.sh --disableMetrics
cd ..
cmake -B build -S . -DCMAKE_TOOLCHAIN_FILE=./vcpkg/scripts/buildsystems/vcpkg.cmake

That should do it. Thanks!

Also you can delete the vcpkg.json so you can install the libraries at a global level not at the project level, if vcpkg detects theres a vcpkg.json, the installed libraries can only be used in this project but not in others.


Update spring maven repository to use HTTPS

repo.spring.io recently started enforcing the use of https to connect and download artifacts. This change updates the root POM to reflect this requirement. Builds off of a fresh maven cache should now succeed.

alluxio-bot, cherry-pick this to branch-2.0 please

alluxio-bot, cherry-pick this to branch-1.8 please


Fix deadline on update issue or PR via API

Fix #8179.

Should this be backported to both v1.10 and v1.9? There was some changes after v1.9 so I can't just cherry-pick, but no problem to do similar fix.

@davidsvantesson I think yes. But so that you can't remove the deadline any more?

I have submitted all PRs for this issue now, slight difference:
master & 1.10: The deadline can be removed (if set but is zero)
1.9: The deadline can't be removed, to not change behavior.
Make comment in respective PR if you think it should be different.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@70fa80d). Click here to learn what that means.
The diff coverage is 0%.

@@           Coverage Diff            @@
##             master   #8696   +/-   ##
========================================
  Coverage          ?   41.7%
========================================
  Files             ?     531
  Lines             ?   68721
  Branches          ?       0
========================================
  Hits              ?   28662
  Misses            ?   36384
  Partials          ?    3675

Impacted Files
Coverage Δ

routers/api/v1/repo/pull.go
35.88% <0%> (ø)

routers/api/v1/repo/issue.go
22.98% <0%> (ø)

Continue to review full report at Codecov.

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

1.11.0+dev-104-ge3875ace9
Confirmed working:

Setting due date via PATCH /repos/{owner}/{repo}/issues/{index} now works.
Editing title or body without due date via PATCH /repos/{owner}/{repo}/issues/{index} now works without triggering erroneous "due date removed" timeline comment.

Having trouble with:

I can't remove the due date by setting it to "", "0", 0, null, "null", nill, "nill", false, "false" or "0000-00-00".  I just get various "cannot parse time" errors. Interestingly setting to value null (without the quotes) does not produce an error, but it does not remove the due date.

@bobemoe I though I tested that but apparently not after my fix. I will look at it tonight.


chore: deprecate icons

This is a big PR, but i've split it into different commits so use the commit selector in Files Changed:

We may need to remove this from the schema in our repository.


Memory usage increases while interacting with plot

Bug Report Template
ScottPlot Version: 4.1.16
Operating System: W10
Application Type: WinForms & WPF
Bug Description:

While interacting with the plot e.g., continuously doing a pan action, the RAM memory increases, especially for WPF application. In case of WinForms memory increases as well but not as significant
Once the interraction is released:
- WPF: memory is released
- WinForm: memory usage remains but I noticed that after a while of interraction sometimes it is also released.

I marked it as bug but I am not sure if it is a bug or normal functioning. So, please feel free to change if you consider so.
Reproducing: Create complete new apps in WPF and WinForms. Drag one single ScottPlot object from the Toolbox. Run the application.
WPF:
https://user-images.githubusercontent.com/24780745/120432507-4ff7d300-c37a-11eb-982d-1b9cac130d21.mp4
WinForms
https://user-images.githubusercontent.com/24780745/120432519-5423f080-c37a-11eb-89c5-caaf55d28dd7.mp4

I don't see a big problem here, it's quite normal behavior.
Yes, ScottPlot is not very careful about memory allocations, but in the end the garbage collector will clean it all up, which is why it was made. The different behavior for different platforms can also be explained by different settings of the garbage collector.
In the example that you brought allocations of hundreds of megabytes, in 2021 I think you shouldn't even think about that.

I did play once until I reached +2 Gb for WPF. But if you say it is normal behavior then we can close the issue.


Images missing max-width property

Hello!
I found the problem exactly the same as one by link https://github.com/dim0627/hugo_theme_beg/issues/19:

Blank theme contains blank style.css (it means zero lines of css code). So, it's not a bug.


bundle: Remove distribution references

These distribution requirements belong in image-spec or similar.  They
don't apply to runtimes or filesystem bundles (the latter are covered
by the earlier "This MUST include the following artifacts"), which are
the two entities tested for compliance with this spec.

These sentences are out of scope to me, and hard to be tested, so
LGTM

LGTM


Feature/configuration

@afaur looks like nodegit is failing to install on windows/linux. I switched to using git-clone which has an external dependency of GIT. I assume we don't want users to need GIT, so we need to talk up a better solution.


Added the option of obtaining the GPOs

Hello, good afternoon,
I have added the option to download GPOs. Basically, it downloads all the information related to GPOs and generates a json with this information. There are some data that I have not been able to download in comparison with the bloodhound collection scripts. But I think it still provides interesting information for the user.
Thank you very much for this amazing project.
Best Regards,

Making some changes


deprecation in odu

The way we're using the interpolation object will be deprecated in a future version of Interpolations.jl; should replace if possible.

@ajozefiak This is the exact deprecation and the fix for it: https://discourse.julialang.org/t/interpolate-deprecate-getindex/15207 The two interpolates are called vf and pf, if I'm not mistaken. On the road today but let me know if this doesn't work out.

Nevermind, fixed this. And I think performances goes up significantly too.


[No QA] Remove unused methods and exports

This is just some cleanup that I came across
Tests / QA Steps
No QA - Normal regression steps will catch anything
Tested On

[x] Web
[x] Mobile Web
[x] Desktop
[x] iOS
[x] Android

Screenshots

Web

Mobile Web

Desktop

iOS

Android

Ooops, updated to remove the import.
On Wed, May 19, 2021 at 3:07 PM Rocio Perez @.***>
wrote:

@.**** approved this pull request.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/Expensify/Expensify.cash/pull/3016#pullrequestreview-663662662,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJMAB5ZJEH6ZQA6TIJN3F3TOQSCJANCNFSM45FKVYXQ
.

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.


MODELIX-1015 model-api-gen-gradle unusable in latest releases

To be verified by reviewers

[ ] Relevant public API members have been documented
[ ] Documentation related to this PR is complete

[ ] Boundary conditions are documented
[ ] Exceptions are documented
[ ] Nullability is documented if used

[ ] Touched existing code has been extended with documentation if missing
[ ] Code is readable
[ ] New features and fixed bugs are covered by tests

Why wasn't this noticed by tests? Can we update the tests to somehow make this visible?

Our tests don't cover publication at all. In the past we published these locally and then used them in the test-projects, but we moved away from that since it was too easy to forget the core build or the publishToMavenLocal step and accidentally test the wrong version.
I'm not aware of plugins which can automatically validate the POM.

For verifying the overall functionality, we should have, at the highest level of the test pyramid, a real e2e test verifying that the integrated product is usable. This would have been caught that way. It would probably be enough to test this on main only and only in CI to cover these issues and to prevent automatic tagging on releases.

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


dependency_order_cop: make strict.

This can be strict now that it's been verified for a while on new formulae.

I haven't seen this show up in messaging except once so far, in which case it was ignored for other reasons. So I don't think this is quite premature.

Ok, cool.

in which case it was ignored for other reasons.

What reasons?

llvm@5 new formula so that it wouldn't be out of the sync with the preexisting llvm formula and other llvm@*


Problems disabling/configuring a cop

I have a problem, disabling RSpec/MultipleExpectations. I some some funny behavior, when trying to configure/disable the cop via .rubocop.yml.
This:
RSpec/MultipleExpectations:
  Max: 5

works. I see fewer violations and the proper counters at the end of the lines in the report (e.g. RSpec/MultipleExpectations: Example has too many expectations [8/5].)
This:
RSpec/MultipleExpectations:
  Enabled: false

doesn't work, the cop is not disabled, violations are still reported.
However, this:
RSpec:
  MultipleExpectations:
    Enabled: false

works... with a twist:

$ rubocop -D --only RSpec/MultipleExpectations
Inspecting 100 files

0 files inspected, no offenses detected
key not found: "Enabled"
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/config.rb:436:in `fetch'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/config.rb:436:in `enable_cop?'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/config.rb:118:in `block in initialize'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/config.rb:208:in `for_cop'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/cop/registry.rb:119:in `block in enabled'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/cop/registry.rb:138:in `select'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/cop/registry.rb:138:in `select'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/cop/registry.rb:118:in `enabled'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/cop/team.rb:47:in `cops'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/cop/team.rb:137:in `validate_config'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/cop/team.rb:25:in `initialize'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/runner.rb:257:in `new'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/runner.rb:257:in `inspect_file'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/runner.rb:205:in `block in do_inspection_loop'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/runner.rb:237:in `block in iterate_until_no_changes'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/runner.rb:230:in `loop'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/runner.rb:230:in `iterate_until_no_changes'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/runner.rb:201:in `do_inspection_loop'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/runner.rb:111:in `block in file_offenses'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/runner.rb:121:in `file_offense_cache'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/runner.rb:109:in `file_offenses'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/runner.rb:100:in `process_file'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/runner.rb:78:in `block in each_inspected_file'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/runner.rb:75:in `each'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/runner.rb:75:in `reduce'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/runner.rb:75:in `each_inspected_file'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/runner.rb:67:in `inspect_files'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/runner.rb:39:in `run'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/cli.rb:82:in `execute_runner'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/cli.rb:28:in `run'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/bin/rubocop:13:in `block in <top (required)>'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/2.4.0/benchmark.rb:308:in `realtime'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/bin/rubocop:12:in `<top (required)>'
/Users/apopov/.rbenv/versions/2.4.1/bin/rubocop:22:in `load'
/Users/apopov/.rbenv/versions/2.4.1/bin/rubocop:22:in `<main>'

Sorry, the last configuration doesn't work, it just breaks rubocop, as the result is the same regardless of the options.

O.K., it seems there was an error in my setup, as I tried yet again and it worked, sorry for the confusion.

@AlexVPopov do you remember what the error in your setup was?
I started getting the behavior you're describing after upgrading to rubocop 0.49.0 from 0.47.1
TIA

@bobmazanec unfortunately I have totally forgotten what the error was, sorry 🤷♂

I had to try
Thanks & HNY 😃


fix outline

This pull request removes the outline on the timeslot buttons in the focused state. Before this fix, after a timeslot was selected the button would filled black with a blue outline, which contrasted and seemed unintentional. After this fix, there's no outline in the selected state, so the selected timeslot button just shows as filled color.

Thank you!


Drilldown does not maintain state of input DOM elements

In my drilldown menu, I have elements which are input elements. I have noticed that the drilldown menu does not keep the values of these input elements when the menu is updated.
I suspect this is because the actual elements are not injected into the drilldown-root element, but instead a clone.
Would be nice to have support for this use case.
I suggest, using some sort of class attribute to identify the trigger which was clicked, then instead of injecting a $.clone version of the DOM, to use the actual DOM element ($next), and finally when the drilldown goes back up, restore the original .drilldown-sub class and finally use $.insertAfter  to place the actual DOM elements back to the original position.
Any thoughts?

I have encountered the same "issue", would be very nice to have a support for this.

@marlongichie  I think I have the same problem using this drilldown and angular-gettext. I come with a PR to fix this.

This has been implemented by @oterral in #7 and landed into the codebase.


Add drawerLockMode to DrawerView

This allows us to disable the gesture to open the drawer. Related to #390.

This PR will simplify a LOT our navigation. Thanks! :D

Did you test that locked-open ? Because I tried doing this PR and I couldn't make the option to work. I understand that if I choose locked-open, drawer should be opened by default and that is controlled by navigation state so probably we need to add some logic ?

cc @DanielMSchmidt

@ferrannp AFAIK lock-open is implemented both in Android as well as in the react-native-drawer-layout-polyfill as "When the drawer is open, don't let it close". This does not include opening it as the property gets set. If you experience a different behaviour on Android, please let me know.
@martnu PR looks nice, can you make sure the behaviour is documented somewhere? Maybe @satya164 can hint you in the right direction 👍

@DanielMSchmidt right mmm, it would be nice thought to provide a prop as initial state of the drawer (closed or open) and then I can use it together with locked-open to be able for example to develop for tablets.

Probably better t just use a plain view on tablets. You don't need any of drawer's behaviour.

@satya164 @martnu How can I help getting this merged ASAP?

@DanielMSchmidt I just updated the branch, but after CI runs I'm just waiting for a merge.

I think it makes more sense in navigationOptions. You cannot change this option dynamically, so it doesn't really do anything. A drawer navigator with always locked drawer? not very useful.

@satya164 It is useful since it allows us to only open/close the drawer programmatically and not via touch gestures since that currently conflicts with the default swipe-back behavior in a stack. I do agree that it would be nice to have it configured for each screen but I'd have to look into the code a bit more.

How can you change this programmatically?

@satya164 We can't change the behavior for the drawer, but I can open the Drawer programmatically via navigate('DrawerOpen').

I see.
Anyway, we should add it to navigationOptions since we will need that, and it will not be very nice to have the same config in 2 places.

CI is failing. You probably need to fix the flow types.

Doesnt work for me.

How do you use lockMode to disable the swipe for iOS. I am specifying lockMode in navigationOptions ={lockMode:'locked-closed} does nothing for me.

How to update the lock-mode dynamically? Currently setting these options only work when you do it in the DrawerNavigator options and cannot be updated. When I try to use static navigationOptions for the drawer nothing happens. I declare it on the contentComponent.

hey guys newbie here.. so I was wondering how do I implement this??or how do I use this??

Yes this is much needed feature. Will solve a lot of problems.

Will this PR be merged for the next release (hopefully in 2-4 weeks)?

Would this allow you to disable the drawer in nested navigators? If so +💯

@martnu  I made a pr with the updates to adjust when the screen is locked per scene here https://github.com/react-community/react-navigation/pull/1378/files

Could some one (who can) please review an update this?

The option to programmatically lock the drawer will be much needed here too.

Would be good to have this PR merged. Seems like this feature will be useful to a lot of people. Or has someone found a way around this?

need this soooo much. have already tested it and it works finefor me. hope you guys will merge this pr soon

Or maybe let us know what's blocking this PR? What needs to be done? I'm willing to help get this in.

Not sure if something is blocking. There is a weird flow type-dance that I can't get around, but awaiting some further information from @satya164. I won't solve any conflicts before we iron that out.

Alright. Thanks for the clarification @martnu

Is there anything we can do to help get this PR merged faster? This PR Is much needed.

Same, really need this merge

The changes in code are minimal. Could the conflicts be fixed and the PR merged? There seems to be many lots of support for this PR. @satya164 what's blocking?

Is there any option to Lock Drawer after open it, it needs so much here also.

+1
I waiting for this functional.

+1
The same, hope to get it soon.

+1
Waiting for this function!!

+1
Waiting for this

@DanielMSchmidt what is blocking this feature? Besides the conflicts!

This has gone on for a super long time. I'm about to finish my second
project and it's still not fixed. I've moved along.
On Sat, 8 Jul 2017 at 6:33 AM, Guilherme Decampo<EMAIL_ADDRESS>wrote:

@DanielMSchmidt https://github.com/danielmschmidt what is blocking this
feature? Besides the conflicts!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/react-community/react-navigation/pull/793#issuecomment-313808363,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAvnfVn2T3KN6NFqA5Pni1sbMwJRkTu7ks5sLrIugaJpZM4Mmx0G
.

--
Sent from my mobile device. Skype: jason.nathan, Mobile: 90220964

+1 I sooo need this

Would greatly greatly appreciate it if this function were implemented! Please merge this ASAP!
(After resolving the conflicts first of course, but make haste!) 👍

This is a feature that would be very very helpful in developing an application. Right now I'm having trouble in making a drawer navigation feature not appear in one page.
Having the drawer navigation close feature would be very very helpful

This feature is much needed for the app I'm working on, any idea when we can get this merged?  I would love to be able to use this functionality, navigation isn't complete without it.

I have copied this feature into my own project, and am using a fork now. It works for me. If the team (or if I read correctly @satya164) could comment what's needed to get this through, I'm sure there are plenty of people willing to help.

plenty @satya164

I will be working on this this weekend

+1

Thank's alot @DanielMSchmidt! The community desperately need this!

+1 on this
It looks like the drawer will only open with the gesture if you have already visited it before, so this would definitely be needed upon logging out.

+1

+1

5 months in, no progress.
@DanielMSchmidt must have been one hell of a weekend :p

I hope I can use this function quickly

Hi guys any update on this? For one of my project, we had to switch to react-native-router-flux in order to move quick. But my ongoing project requires me to strictly implement this feature! Any ETA?

+!

I ended up removing the drawer from react navigation and configured it manually, unfortunately.

Yes. That works best. I have a top level component that initializes a give
stack based on a value in the reduced store.
That way I have dedicated stacks transitioning over a loading screen.
LayoutAnimation really shines here
On Aug 8, 2017 12:19 AM, "Christian Hess"<EMAIL_ADDRESS>wrote:

I ended up removing the drawer from react navigation and configured it
manually, unfortunately.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/react-community/react-navigation/pull/793#issuecomment-320710130,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAvnfbbcIzRXmuPv-Vo0dd2P1US_Too9ks5sVzktgaJpZM4Mmx0G
.

Did the same. The performance was actually better and the you have overall more control of the drawer.

Why is this PR not getting implemented? I forked the project now and implemented it on my own. These are only minor code changes? I dont get it.

+1

Why hasn't it turned out yet? This function is important

It is very strange that such useful PR is not merged for so long time. And it is not only case - the same happens for TabBar and other related bug fixes.
Community, I'm thinking about merging all these very useful PRs into own fork of react-navigation and use it by RNRF (or you could use it as just react-navigation replacement) until they will not be merged, what do you think?

great idea @aksonov

I tried to use this patch after fixing the merge conflict but unfortunately it doesn't properly forward the drawerLockMode setting from the DrawerNavigator.navigationOptions. I think it only works via the screen props. Also the locked-close documented setting is incorrect and needs to be locked-closed on android. I also tried #1377 and had similar issues with the setting not being respected from the top-level navigator options so neither one of these PRs should be merged as-is.

@mmerickel Are you able to fix it?

If you fork the library and patched it with the PR code, it works but
Why you no merge!

Hello!! Is anyone there?  This PR is critically important, I will clone this repo and work with you for this.

Exactly, do it :)

seems like #1377 is a better PR than this one since it allows to specify this within navigationOptions

Hmmm 🤔  So, what's happening? Why a highly-requested 6 months-ago PR is not merged? Is there any reason?

can we get this or #1377 merge in?
This should some real app use cases

@sibelius there is some issues someone need to fix

There are conflicts in src/TypeDefinition.js - can you fix them?

any update?

@spencercarli I read on a blog post that you'll work here on react-navigation to take a look on documentation and issues can you give a heads up about this one here?
We are building an app that this is primordial. There is any timeline or another PR, issue etc that people are working for this feature? Definitely we can help in any means.
Best,

@guilhermedecampo going to try to get this merged asap. I'm not super familiar with drawers so I'm going to have someone else look it over. Looks good to me though

besides this, it looks great.

@spencercarli please note this PR does not allow to specify drawer lock mode in navigation options and several people already expressed they need that. There is another pr that I linked a couple of posts higher which should be able to do that, it might be good to take a look at it.

@spencercarli - I agree with @vonovak
After reviewing both PRs, I find #1377 better.
We might need to make drawer lock mode optional in the type and implementation but that would be a small patch, I'm sure everyone is up for.

Agree with @vonovak. +1

Just merged #1337 in! Thanks for everyone's work and input on this. Will be in the next release 😄

Hold coming soon !!! @spencercarli

Wait it's being fixed!? I actually lost hope, only checking on this status once per month! Thanks guys!

const navigationOptions = ({navigation}) => ({
  //Other configuration items are omitted
    drawerLockMode:'locked-closed' //here
});

const MainStackNavigator = StackNavigator({
    Chat:{
        screen: Chat,
        navigationOptions:{
             drawerLockMode:'unlocked',  //here
        }
    }
  //Other configuration items are omitted
},{
    navigationOptions: navigationOptions,
    initialRouteName: 'Chat', //home page
});


product_id is required in OpportunityProperties

See https://github.com/stapi-spec/stapi-spec/blob/main/opportunity/README.md#properties-object.

This is also needed in OrderProperties.


Make visualisation frames movable

Make the frames movable so that the location can be changed within the grids. See this
https://github.com/atlassian/react-beautiful-dnd
First try if it is possible with MUI

MUI does not support rearrangeable grid layouts out of the box. Its better to go with external libraries that support it. I will try it out with the one you have mentioned.

Added resizable chart feature with the PR