cannot import ollama module

pip install -r requirements.txt
Collecting openai
Using cached openai-0.10.5.tar.gz (157 kB)
Preparing metadata (setup.py) ... done
Requirement already satisfied: torch in c:\users\abhinand\easy-local-rag\my_venv\lib\site-packages (from -r requirements.txt (line 2)) (1.10.2)
Requirement already satisfied: PyPDF2 in c:\users\abhinand\easy-local-rag\my_venv\lib\site-packages (from -r requirements.txt (line 3)) (3.0.1)
ERROR: Could not find a version that satisfies the requirement ollama (from versions: none)
ERROR: No matching distribution found for ollama
(my_venv) C:\Users\abhinand\easy-local-rag>python localrag.py
Traceback (most recent call last):
File "localrag.py", line 2, in
import ollama
ModuleNotFoundError: No module named 'ollama'.
I have downloaded ollama windows in my system ,but cannnot import the ollama module.can you please try and figure it out whats wrong.

Will take a look :)

@abhinand888 You can the version here maybe https://pypi.org/project/ollama/

is it solved?

Upgrade the python version to > 3.8


All of these rules fail with the same error when you try to create them

Attempting to Create Rule: Dev-0530 IOC - July 2022
Error Creating Rule: Error in EntityMappings: The given column 'FileHashCustomEntity' does not exist.
Attempting to Create Rule: ACTINIUM AV hits - Feb 2022
Error Creating Rule: Error in EntityMappings: The given column 'FileHashType' does not exist.
Attempting to Create Rule: Tarrask malware IOC - April 2022
Error Creating Rule: Error in EntityMappings: The given column 'FileHashCustomEntity' does not exist.
Attempting to Create Rule: KNOTWEED File Hashes July 2022
Error Creating Rule: Error in EntityMappings: The given column 'FileHashCustomEntity' does not exist.
Attempting to Create Rule: Hive Ransomware IOC - July 2022
Error Creating Rule: Error in EntityMappings: The given column 'FileHashCustomEntity' does not exist.
Attempting to Create Rule: Zinc Actor IOCs files - October 2022
Error Creating Rule: Error in EntityMappings: The given column 'AlgorithmCustomEntity' does not exist.

These too
Attempting to Create Rule: ACTINIUM Actor IOCs - Feb 2022
Error Creating Rule: Error in EntityMappings: The given column 'FileHashType' does not exist.
Attempting to Create Rule: Mercury - Domain, Hash and IP IOCs - August 2022
Error Creating Rule: Error in EntityMappings: The given column 'FileHashCustomEntity' does not exist.
Attempting to Create Rule: Europium - Hash and IP IOCs - September 2022
Error Creating Rule: Error in EntityMappings: The given column 'FileHashCustomEntity' does not exist.

How are you attempting to deploy/create these rules?
Through the UI? API? Or TF provider?

UI
On Oct 12, 2022, at 1:30 PM, A Smith @.***> wrote:

How are you attempting to deploy/create these rules?
Through the UI? API? Or TF provider?
—
Reply to this email directly, view it on GitHubhttps://github.com/Azure/Azure-Sentinel/issues/6363#issuecomment-1276513509, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AIC5OWAEJABTSYDYE26QSG3WC3YUDANCNFSM6AAAAAARCZR7QQ.
You are receiving this because you authored the thread.Message ID: @.***>

+1 on this as well

Any news on this issue?

This is pure speculation but if you read the YAML for these rules the FileHashCustomEntity is a SHA256 algorithm value
| extend timestamp = TimeGenerated, HostCustomEntity = Hostname , AccountCustomEntity = AccountName,  FileHashCustomEntity = SHA256
The correct entry in the YAML for the entity mapping is probably

entityType: FileHash
fieldMappings:

identifier: Algorithm
columnName: SHA256
identifier: Value
columnName: FileHashCustomEntity

Hi @anfisher1967,
Sorry for the delayed response.
We are able to create analytic rules for the above mentioned items. Could you please re-verify again if its working at your end or not?
Thanks!

Same error in two different tenants. Let me know if you want a screen shot.

Hi @anfisher1967, We wanted to check on the status of Issue https://github.com/Azure/Azure-Sentinel/issues/6363. The issue is pending for more than expected days. Please let us know if you need any assistance to review this Issue. As per our standard operating procedures if no response is received in the next 7 business days, we will close this Issue. Thank you for your cooperation.

Since we have not received a response in the last 7 days, we are closing your issue as per our standard operating procedures. If you still need support for this issue, feel free to re-open at any time. Thank you for your co-operation


[docs] Added better example for FormattedInputs

[x] I have followed (at least) the PR section of the contributing guide.

Hi @oliviertassinari ,
I think this code (which is an example of integration with react-text-mask package) is a little complex.
Because it doesn't use a simple TextField component to show the usage of MaskedInput.
So, I've just removed the usage of FormControl, Input, & InputLabel components and used a simple TextField, instead.
Thanks for paying attention

Thanks for the proposal we demonstrate the textfield and composition approach so people can pick what works best for them.


deps: Bump com_github_skyapm_cpp2sky -> 0.5.1

Fix #23032

Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

closing this as unnecessary at the moment


cmd/compile: -m=2 output is missing escape information

What version of Go are you using (go version)?

$ go version
go version go1.13beta1 darwin/amd64

Does this issue reproduce with the latest release?
No, this is only happening on the 1.13beta1 release.
What operating system and processor architecture are you using (go env)?

go env Output

$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/bill/Library/Caches/go-build"
GOENV="/Users/bill/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/bill/code/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/bill/code/go/src/github.com/ardanlabs/gotraining/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/f8/nl6gsnzs1m7530bkx9ct8rzc0000gn/T/go-build144671233=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?
Given this code:
https://github.com/ardanlabs/gotraining/tree/master/topics/go/profiling/memcpu
I ran the following command in 1.13beta1

$ go test -bench . -gcflags -m=2

What did you expect to see?

./stream.go:83:26: &bytes.Buffer literal escapes to heap
./stream.go:83:26: 	from ~R0 (assign-pair) at ./stream.go:83:26
./stream.go:83:26: 	from input (assigned) at ./stream.go:83:8
./stream.go:83:26: 	from input (interface-converted) at ./stream.go:93:26
./stream.go:83:26: 	from io.r (assign-pair) at ./stream.go:93:26
./stream.go:83:26: 	from io.r (passed to call[argument escapes]) at ./stream.go:93:26

What did you see instead?

$ go test -bench . -gcflags -m=2
./stream.go:83:26: &bytes.Buffer literal escapes to heap
./stream.go:89:13: make([]byte, size) escapes to heap
./stream.go:93:26: input escapes to heap
./stream.go:101:27: input escapes to heap
./stream.go:113:28: input escapes to heap

Why is this a problem?
All of the information about why the escape happened is gone. This information is valuable to not guess why. The new output is not saying why and disconnects the information as well.

I'm sorry, I jsut not realized you had an issue 31489 for this. Maybe this can provide more details and a way to test a fix.

CC @mdempsky @dr2chase

Thanks for the report. As you note, this is a duplicate of #31489. I think the details there are adequate, but GitHub has cross-referenced this one anyway should it prove useful.


EGM Control lag

EGMManager.waitForMessage() will sometimes take 15+ ms when trying to run with an update rate of 250 Hz (and EGMActJoint SampleRate of 4 ms).
Using EGMManager.read() without waitForMessage() will sometimes result in reading the same message multiple times - this may cause slightly choppy robot movements.
Diagram of EGM architecture

See related: https://github.com/ros-industrial/abb_libegm/issues/49

Hi,
I actually encountered the same problem. I wasn't yet able to track it down completely, however, I fixed the control lag by switching from EGMManager to EGMControllerInterface. Maybe that also helps you.


add deleting all types of nodes

PR to 1.1.0 branch, the same with https://github.com/RackHD/on-http/pull/80 that has been merged into master.
It is a fix of ODR-314 required for 1.1.0. Implement full function about deleting nodes and update its related ones based on "relations" field in nodes/ document.
Dependent on PR:
https://github.com/RackHD/on-core/pull/62

This PR depend on on-core PR https://github.com/RackHD/on-core/pull/62 for constants definition and unit test.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

:+1:

:+1:

There is no clue about the Jenkins failure, perhaps it is a trial run? Will try to merge and monitor the smoke test report.


Apply filters after applying defaults and conversions

Tmt makes automatic conversions and applies defaults to tests, plans and
stories, however, fmf has no clue about such actions. Previously,
filters and conditions were applied on the raw fmf data (with no
conversions taken into account) which could result in weird errors
(e.g. Test.tag could be set to None when filtering).
Change this behaviour so that filters and conditions are applied after
the Tree has been processed by tmt, in other words once Test/Story/Plan
objects have been created.
Resolves: #469
Resolves: #450
Following the example in the issue produces the following expected result:
$ tmt tests ls --condition '"nonex" not in tag'
/nulltag-test
$ tmt tests ls --condition '"nonex" in tag'
$ tmt tests ls --condition 'tag is None'
$ tmt tests ls --condition 'not tag'
/nulltag-test

Thanks for fixing this, @FrNecas. The essential part looks good. I've slightly improved the code to prevent unnecessary duplication and extended tests a bit. Before merging we should still cover the following:

Handle exceptions raised in fmf.utils.filter() (e.g. missing dimension in data dict)
Handle exceptions raised in fmf.utils.evaluate() (e.g. any invalid python code)
Decide what do we do with custom L1 attributes (anything which is not part of the spec)

Regarding the last one: Users can define and use arbitrary metadata for their tests and then use them for filtering. We should probably support these as well. What do you think?

Rebased to master, added exception handling, boolean values with lowercase are now supported on tmt side and custom attributes are supported as well (I moved _metadata attribute to Node to share the logic for all the node types)

Hmm, seems CentOS8 error is from tmt ...

IMHO it is correct to treat missing attributes as false (as opposed to filter error).
E.g. As a user I want to find all tests which are using specific unofficial attribute (e.g. extra-hardware)

Good, let's merge then. We can adjust/polish this later if needed.


transmute between types of different sizes

Not sure what changed but this just started coming up in one of my CI tests

Compiling stm32h7xx-hal v0.8.0
error[E0512]: cannot transmute between types of different sizes, or dependently-sized types
   --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/stm32h7xx-hal-0.8.0/src/rng.rs:110:67
    |
110 |                         let bytes: [$type; BATCH_SIZE] = unsafe { mem::transmute(random_word) };
    |                                                                   ^^^^^^^^^^^^^^
...
126 | rng_core!(usize);
    | ----------------- in this macro invocation
    |
    = note: source type: `u32` (32 bits)
    = note: target type: `[usize; 0]` (0 bits)
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

I have been messing with my code, but pretty sure my changes didn't cause this.

What's your rustc version?

Found it: https://github.com/pdgilbert/rust-radio-sx127x/runs/2099019706 Rust 1.50.0

This is caused by building stm32h7xx-hal for x86_64-unknown-linux-gnu. Be sure to use --target=thumbv7em-none-eabihf.
I've been confused by this before, we should add a compile error for this.

I can verify that adding  --target=thumbv7em-none-eabihf fixes the problem. But I was building with
cargo build --no-default-features --release --features stm32h742

so not specifying any target for this step. That has worked previously and still works with other hals as you can see at https://github.com/pdgilbert/rust-radio-sx127x/actions/runs/647552905.
So it seems to be picking up a default target somewhere. Do I now have to start specifying the target for this first build step?

It looks like the last CI run that worked didn't have this "build" step, just the "build example" steps which use cross and specify the target.
If you don't specify the target the default target is the target of the host, in this case x86_64-unknown-linux-gnu.

Do I now have to start specifying the target for this first build step?

I'd say so, yes. Is there a reason that you're building the HAL for Linux? It wouldn't be hard to fix that build but I hadn't considered that doing so would be intentional and not a mistake.

(I was so blurry eyed from much workflow tweaking that I could not see what was happening.) I think the problem may be an overly agressive build strategy rather than the need for an error message. Here is a summary for anyone interested.
None of the following attempt to build the target directory, eg target/thumbv7em-none-eabihf
  cargo build  --no-default-features

compiles some pieces but not anything requiring features.  (caveat. Above works in rust-radio-sx127x which is using embedded-hal 1.0.0-alpha.4. In another package using embedded-hal 0.2.4 I get the usual problem  no InputPin  in  digital::v2 until I specify some features.) The follow all work in both packages  and compile more pieces:
  cargo build  --no-default-features  --features=stm32f0xx,stm32f030xc
  cargo build  --no-default-features  --features=stm32f4xx,stm32f411
  cargo build  --no-default-features  --features=stm32f1xx,stm32f103
  cargo build  --no-default-features  --features=stm32f3xx,stm32f303xc
  cargo build  --no-default-features  --features=stm32f4xx,stm32f411
  cargo build  --no-default-features  --features=stm32f7xx,stm32f722
  cargo build  --no-default-features  --features=stm32l0xx,stm32l0x2
  cargo build  --no-default-features  --features=stm32l1xx,stm32l100
  cargo build  --no-default-features  --features=stm32l4xx,stm32l4x2

But then
  cargo build  --no-default-features  --features=stm32h7xx,stm32h742

fails with
error: could not compile `stm32h7`

Caused by:
  process didn't exit successfully: `rustc --crate-name stm32h7 --edition=2018 /home/paul/.cargo/registry/src/github.com-1ecc6299db9ec823/stm32h7-0.12.1/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C debuginfo=2 --cfg 'feature="cortex-m-rt"' --cfg 'feature="default"' --cfg 'feature="rt"' --cfg 'feature="stm32h743"' -C metadata=92009c8beecd4dbb -C extra-filename=-92009c8beecd4dbb --out-dir /home/paul/githubClones/rust-radio-sx127x/target/debug/deps -L dependency=/home/paul/githubClones/rust-radio-sx127x/target/debug/deps --extern bare_metal=/home/paul/githubClones/rust-radio-sx127x/target/debug/deps/libbare_metal-efa5ff3a789aa0d1.rmeta --extern cortex_m=/home/paul/githubClones/rust-radio-sx127x/target/debug/deps/libcortex_m-5c544b4361cb95da.rmeta --extern cortex_m_rt=/home/paul/githubClones/rust-radio-sx127x/target/debug/deps/libcortex_m_rt-571e73a6ac779bfe.rmeta --extern vcell=/home/paul/githubClones/rust-radio-sx127x/target/debug/deps/libvcell-00c45049692fe545.rmeta --cap-lints allow -L /home/paul/githubClones/rust-radio-sx127x/target/debug/build/stm32h7-ba81181585b94d3c/out -L /home/paul/githubClones/rust-radio-sx127x/target/debug/build/cortex-m-rt-1ec2c44a7897cd63/out` (signal: 9, SIGKILL: kill)

So is it trying to build the target for the default triple, or doing something else that requires knowing the target?
(I'm new to embedded but the default does not make sense to me. Is there ever any situation one would build an embedded no_std hal like stm32h7xx for the compiler's host? I certainly was not doing it on purpose.)
BTW, specifying the target is good advice if you just want things to work.

So is it trying to build the target for the default triple, or doing something else that requires knowing the target?

Yes, it is building for the host target. Unless you tell cargo to use a different target via command line, environment variable, or .cargo/config it will always build for the host target. There is no automatic detection, there is no way for libraries to tell cargo what target to use. Some libraries will set the target in their .cargo/config file but that only affects cargo invocations in their directory, e.g. examples.
I think the root of the confusion is that the HALs would build for x86 at all, aren't they hardware specific? Yes, they are, and they won't run on x86. However, most of the hardware specific bits in the HALs are just reading and writing to specific memory locations which won't work on other hardware but it will build just fine. Unless the library uses assembly instructions or relies on e.g. pointer size it's easy to accidentally make something which can build on x86. There are also reasons to purposely make it work, like being able to run non-target-specific tests on your host machine.
This specific error is caused by a calculation that assumes the pointer size is 32-bits which is probably not too common among HALs, at least not in a way which causes a compile-time error.

Ok, thank you for the explanations. I think I mostly understand this. But saying "the default target is the target of the host" suggests to me that on my computer
cargo build  --no-default-features

and
cargo build  --no-default-features  --target x86_64-unknown-linux-gnu

should do the same thing. But the second creates a directory target/x86_64-unknown-linux-gnu and puts stuff in it, so you must mean something slightly different by "default target".

That appears to be a bug/simplification in cargo. Judging by the code and comments when cargo is given a --target argument it is considered cross compiling and it simply passes along the target to rustc and builds in a subdirectory that contains the target name.
You may think that this logic would fix that:
    pub fn for_target(self, target: &Target) -> CompileKind {
        // Once we start compiling for the `Host` kind we continue doing so, but
        // if we are a `Target` kind and then we start compiling for a target
        // that needs to be on the host we lift ourselves up to `Host`.
        match self {
            CompileKind::Host => CompileKind::Host,
            CompileKind::Target(_) if target.for_host() => CompileKind::Host,
            CompileKind::Target(n) => CompileKind::Target(n),
        }
    }

but no, for_host is only true for things that need to be built for the host like plugins, proc-macros and build scripts. From my cursory glance it appears that cargo doesn't even know what the host target is, I can't see it stored anywhere obvious.

Thanks, that explains it.


Account level MAXCPUs appears as -1

Need to modify account level section to be consistent with group section. This will simplify and generalize. Also need to adjust spacing to output correctly for long group names.

Resolved in https://github.com/frenchwr/slurm-wrappers/commit/2575d8346d92738511da147eff0714b2be86c099


performance improvement

iterating without recursion, using just dict comprehension instead of ChainMap, and avoiding filtering/mapping looks to be significantly more performant

merging mypy closed this


Get average of time after user input

Bug, feature request, or proposal:
Get average value from 5 input type time
What is the expected behavior?
App should be able to display the value of the average
What is the current behavior?
No value are display
Which versions of Angular, Material, OS, browsers are affected?
Angular2, Material 2, Windows

Hey @addean can you describe differently? I'm not sure I understand the problem.

This looks like more of a question on how to average the values of five form control values. Material isn't likely to build a component that does this for you, so better avenues for troubleshooting / questions are stack overflow, gitter, mailing list, etc.


Stackless coroutines now can refer to themselves (through get_self() and friends)

Fixes #4155

@tianyi93 this should resolve your issues with stackless threads you were seeing in hpxMP. Please verify.

@hkaiser  It seems  error: 'hpx/coroutines/detail/coroutine_stackless_self.hpp' file not found is missing

@hkaiser SIGSEGV is happening when executing create_thread function under hpx/runtime/threads/detail/create_thread.hpp

@tianyi93 I guess your problem has already been fixed by @hkaiser? Not sure if the problem showed up on our builders in the first place but they are happy (enough) now.

@msimberg Yes, the compiler error has been fixed. The issue remains is the implementation in the hpxMP side now. Thanks!


what is GstClockTime timestamp case:447163

Hi TIS team,
What is timestamp provided by the below line in tcam_demo.cpp:
GstClockTime timestamp = GST_BUFFER_PTS(buffer);
Is it timestamp created by the camera?

Hello
Currently the time stamps are generated by software and not by cameras.
Stefan

Hi @TIS-Stefan
Thanks for your reply.
How can i get the camera timestamp ?
There is another open issue about camera that.
you said that we can get it by aravis directly. could you help us to get camera timestamp by a sample code?

Hello
I have to admit never used Aravis on my own.. However, I searched in the internet and found
https://aravisproject.github.io/docs/aravis-0.4/ArvBuffer.html
There is a "arv_buffer_get_timestamp ()" on the "ArvBuffer". That should do the job.
Stefan


Shipping 7z seems wrong

It feels better to check what the current OS is, do a Levenshtein distance match between the os and the links in https://github.com/JuliaBinaryWrappers/p7zip_jll.jl/releases/, then download and try the links from top to bottom.

Removed 7z binaries (an not supporting rar files anymore)


Error in ret[[2]][[2]][, "nodes"] : incorrect number of dimensions

Thanks for your package.  Error occured  when using function statscnQueryData().  Details shown below:
rstatscn::statscnQueryData('A0102',dbcode='hgnd')

Error in ret[[2]][[2]][, "nodes"] : incorrect number of dimensions
I guess it might be the  website updates of NBS China.  Would you kindly check whether it could be fixed easilly?
Thanks in advance !

it seems the function dataJson2df() goes wrong when statscnQueryData() is called.


Please, please please

Can you please set it so the resulting book that got all the enchants from the item has a reset repair cost?
Cause I took of all the enchants off my sword and now can't even add em to a new one due to max expenses.

Thank you for leaving your feedback!
Future versions will support various settings, including the adjustment of repair costs as you mentioned.
I would like to provide these changes immediately, but I am currently addressing an issue with the enchantment base cost calculation in the latest version.
I will strive to resolve this issue and provide a version with these settings before the end of the year if possible.


feat: add birthday command

This pull request adds a new command called "birthday" to the Discord bot. The command allows users to set their birthday, view their current birthday settings, force a specific age, and delete their birthday.

close #281

@jaotan review


Compatibility with coc.nvim

How can i make it work with https://github.com/neoclide/coc.nvim and https://github.com/neoclide/coc-tsserver?

I don't think tsserver is natively supporting html template literals right now. I have managed to get typescript-lit-html-plugin to work in coc.nvim. You might give that a shot.

My current setup to work on lit-html in vim is using the typescript-lit-html-plugin with coc-tsserver. Would be nice if it could detect string litterals and show coc-html suggestions in those parts. Dunno how impossible it is to get it working though.

My current setup to work on lit-html in vim is using the typescript-lit-html-plugin with coc-tsserver. Would be nice if it could detect string litterals and show coc-html suggestions in those parts. Dunno how impossible it is to get it working though.

How you make it work with vim and coc?

I just have all of them installed and they work. coc.nvim and typescript-lit-html-plugin with VimPlug, coc-tsserver as an extension.

I just have all of them installed and they work. coc.nvim and typescript-lit-html-plugin with VimPlug, coc-tsserver as an extension.

Can you show me config strings for vimPlug?
How do you add
"compilerOptions": {
    "plugins": [
      {
        "name": "typescript-lit-html-plugin"
      }
    ]
  }

to coc-tslint config?

Would be nice if it could detect string litterals and show coc-html suggestions in those parts. Dunno how impossible it is to get it working though.

Yeah, I imagine that would be useful in some scenarios. I think someone would need to fork typescript-lit-html-plugin and first figure out how to enable it on ALL string literals.
(By the way, there is currently an experimental g:htl_all_templates to add html syntax highlighting to ALL template string literals in vim.)

If typescript-lit-html-plugin were to add a section in their readme for using it with vim, I think it might look like this:

With NeoVim
Install coc.nvim and run :CocInstall coc-tsserver.
Install the plugin and a copy of TypeScript in your workspace:
npm install --save-dev typescript-lit-html-plugin typescript

Then add a plugins section to your tsconfig.json or jsconfig.json
{
  "compilerOptions": {
    "plugins": [
      {
        "name": "typescript-lit-html-plugin"
      }
    ]
  }
}


Is the leveldb background compact single threaded?

First of all, this is a great library. But after using it a bit making huge amounts of inserts I have two questions.

Is the leveldb background compact job single threaded?
Is it possible to do inserts while the background compact job is running or is the database locked?

I am using WriteBatch to make 1M inserts at a time. At regular intervals the inserts are just waiting for around 300 seconds before continuing. My guess is that the compact job is running and taking up only one cpu.

Having a read through a large portion of the code base, I feel confident to say (correct me if I'm wrong):

The background compaction job is single threaded
It is possible to do inserts while the background compaction job is running, however certain situations will cause the writing thread to wait. Namely, when a memtable is full and a previous memtable is already undergoing compaction. This will pause writing threads until a new memtable can be created i.e. when the compaction is done. The default memtable size is 4 MiB. Maybe your write pattern is filling memtables up too fast?

Aside, these types of questions are probably best suited to be asked on stack overflow. From what I've seen, unless its an actual problem with the lib, these types of questions dont really get much love in the leveldb issues.

Thanks for the hint.
I also started reading the source and the background worker seems to be very single threaded. Even if I create multiple instances (pointing to separate db folders) the background worker is shared between them. It runs as a singleton.
https://github.com/google/leveldb/blob/4fb146810cd265ffefa7f9905c016ae965ad36c8/util/env_posix.cc#L922
I ended up increasing the write_buffer_size to 1GB.
options.write_buffer_size = 1024ull * 1024ull * 1024ull

This made the problem less frequent anyway.
Ok, will post on stack overflow next time. Closing this thread.


Show tooltip, as controlled by AM, only when it has text

The action-menu code interacts with showing the tooltip,
and if an item doesn't have tooltip text, but the tooltip
is configured to have a background, an empty background
would show up without this.
It's annoying and fortunately fixed now.

Looks good to me. Is it possible to open the action menu while a tooltip is set, resulting in the tooltip not being hidden when it's supposed to as a result of this and the trigger in https://github.com/godotengine/escoria/blob/master/device/globals/action_menu.gd#L42 ?

I have not seen an issue with tooltips not being hidden when the action menu is opened.

Ok. I'm wondering if it might be better to change
if $"tooltip" and $"tooltip".text:
    $"tooltip".visible = p_visible

to
if $"tooltip":
    $"tooltip".visible = p_visible and $"tooltip".text

to safe-guard against such scenarios though? Otherwise there's a chance calling set_tooltip_visible(false) to hide the tooltip might not be future-proof.

@fleskesvor agreed with your reasoning, force-pushed.
Of course I haven't had the opportunity to actually test it, but there's no reason it would fail.
Maybe later today or just hit merge on the sucker.

Hit it, flesk! I noticed no difference.

Great, thanks! :+1:


Improve F-beta metrics

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (2282839) to head (ccf84c8).
Report is 7 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #296   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           98        98
  Lines         2359      2358    -1
  Branches       214       214
=========================================
- Hits          2359      2358    -1

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


v5 AmplitudeTap.amplitude always equal to 0.0

When using AmplitudeTap I want to get the amplitude value. I put a microphone at the entrance. For some reason, the amplitude is always 0.0.

You're doing something wrong but you haven't shown anything. Issues are for posting specific problems proven to be with AudioKit not your own code. This is just too vague.

You're doing something wrong but you haven't shown anything. Issues are for posting specific problems proven to be with AudioKit not your own code. This is just too vague.

Thanks, I figured it out. The problem was that I did it like this:
let stereoMic = StereoFieldLimiter (mic, amount: 1)
let amplitude = AmplitudeTap (stereoMic)
And you need to feed the microphone directly:
let amplitude = AmplitudeTap (mic)

Thanks, I figured it out. The problem was that I did it like this:
let stereoMic = StereoFieldLimiter (mic, amount: 1)
let amplitude = AmplitudeTap (stereoMic)
And you need to feed the microphone directly:
let amplitude = AmplitudeTap (mic)


phonegap-plugin-push ionic 1 can't receive notification

Reproduce Scenario (including but not limited to)
Hi everybody,
I'm new to use phonegap-plugin-push with ionic v1, I am finding this problem: when I send a notification my device does not receive it. The registration part works and I get the device tocken, but after that I don't receive notifications or errors when I send a notification by server. I'm sure the server sends a correct notification.
Platform and Version (Android 6.0 )
Cordova CLI version and cordova platform version
cordova --version                                    7.0.1
cordova platform version android                     6.2.3

Plugin version
cordova plugin version | grep phonegap-plugin-push   2.0.0

Sample Code that illustrates the problem
my code:
app.js
         `.run(function ($ionicPlatform, $window, $rootScope,ToastService,LocalStorageHelper) {
            $ionicPlatform.ready(function () {

    if (window.cordova && window.cordova.plugins && window.cordova.plugins.Keyboard) {
        cordova.plugins.Keyboard.hideKeyboardAccessoryBar(true);
        cordova.plugins.Keyboard.disableScroll(true);

    }
    if (window.StatusBar) {

        StatusBar.styleDefault();
    }

    const push = PushNotification.init({
        android: {
            senderID: "MY FIREBASE PROJECT ID",
            sound: "true",
            vibrate: "true",
            icon: "phonegap",
            iconColor: "blue"
        },
        browser: {
            pushServiceURL: 'http://push.api.phonegap.com/v1/push'
        },
        ios: {
            alert: "true",
            badge: "true",
            sound: "true"
        },
        windows: {}
    });

    push.hasPermission((data) => {
        console.log('hasPermission data=')
        if (data.isEnabled) {
            console.log('isEnabled');
        }
    });

    push.on('registration', (data) => {
        // data.registrationId
        console.log('*****************')
        console.log('push success data=',data);
        console.log('*****************')
        LocalStorageHelper.setDeviceToken(data.registrationId)
    });

    push.on('notification', (data) => {
        // data.message,
        // data.title,
        // data.count,
        // data.sound,
        // data.image,
        // data.additionalData
        console.log('*****************')
        console.log('push notification data=',data);
        console.log('*****************')
    });

    push.on('error', (e) => {
        // e.message
        console.log('*****************')
        console.log('push Error data=',data);
        console.log('*****************')
    });

});}`

config.xml
    ` <plugin name="phonegap-plugin-push" spec="^2.0.0"/>
       <platform name="android">
       <resource-file src="google-services.json" target="google-services.json" />
        </platform>
       <platform name="ios">
       <resource-file src="GoogleService-Info.plist" />
        </platform>`

pakage-json
 `"plugins": {
    "cordova-plugin-inappbrowser": {},
    "cordova-plugin-whitelist": {},
    "cordova-plugin-x-toast": {},
    "phonegap-plugin-barcodescanner": {
        "CAMERA_USAGE_DESCRIPTION": ""
    },
    "cordova-plugin-camera": {
        "CAMERA_USAGE_DESCRIPTION": " ",
        "PHOTOLIBRARY_USAGE_DESCRIPTION": " "
    },
    "cordova-plugin-file": {},
    "cordova-plugin-file-transfer": {},
    "cordova-plugin-email-composer": {},
    "phonegap-plugin-push": {}
}

Thanks in advance!

@S3r3n4 what does your payload look like? What do you see when running adb logcat | grep Push?

hi, thanks for your reply!
After running adb logcat | grep Push I get:
11-22 17:33:09.873  8389  8407 D SPPClientService: PushLog.txt file is not deleted.
11-22 17:33:09.873  8389  8407 D SPPClientService: PushLog.txt file is not deleted.
11-22 17:33:09.873  8389  8407 D SPPClientService: ============PushLog. stop!
11-22 17:35:03.233  9610  9665 D Push_InsIdService: Refreshed token: elYnb3z9Jjo:APA91bFkXpsrAHeIfGsMeHmJcc0hS2pAdGUfg5IB6SMW7j6b0lE6Ev3DDG9B6oNCDrvoUUUrkMfbtw9GoAhE1msWeU9fTVzU6-o5Nt7rWLepaUGwsK3-6PP5MZ7v11433eRoi5Dnb9xk
11-22 17:35:05.403  9610  9734 V Push_Plugin: execute: action=hasPermission
11-22 17:35:05.473  9610  9734 V Push_Plugin: execute: action=init
11-22 17:35:05.473  9610  9735 V Push_Plugin: execute: data=[{"android":{"senderID":"pjoon.com:platform-storeden"},"browser":{"pushServiceURL":"http://push.api.phonegap.com/v1/push"},"ios":{"alert":"true","badge":"true","sound":"true"},"windows":{}}]
11-22 17:35:05.473  9610  9735 V Push_Plugin: execute: jo={"senderID":"pjoon.com:platform-storeden"}
11-22 17:35:05.473  9610  9735 V Push_Plugin: execute: senderID=1005267570499
11-22 17:35:05.473  9610  9735 V Push_Plugin: onRegistered: {"registrationId":"elYnb3z9Jjo:APA91bFkXpsrAHeIfGsMeHmJcc0hS2pAdGUfg5IB6SMW7j6b0lE6Ev3DDG9B6oNCDrvoUUUrkMfbtw9GoAhE1msWeU9fTVzU6-o5Nt7rWLepaUGwsK3-6PP5MZ7v11433eRoi5Dnb9xk","registrationType":"FCM"}
11-22 17:35:05.473  9610  9735 D Push_Plugin: no icon option
11-22 17:35:05.473  9610  9735 D Push_Plugin: no iconColor option

@S3r3n4 Yeah, so you are getting the registration ID fine. What logs, if any do you see when you send the push to the device? Also, I need to see your payload.

I had try to catch the log when notification arrives on device but adb logcat |grep Push not write log.
I don't have the payload sent because i haven't access to the sender server

@S3r3n4 how are you sending the push.

I use the website connected to old app, I send a message from website.
After that on the old app i get a notification.
I would see the notification on new app.

@S3r3n4 I'm not getting the necessary info I need in order to help you. Without more information they only think I can guess at is that your app is registering with a different project than the website is setting pushes to.

Hi,
I had found the correct project, but now when I send the notification the app crashes without any error.
The adb logcat | greap push give me this when this app starts:
11-27 10:13:10.661  1108  1108 I GservicesProvider: Gservices pushing to system: true; secure/global: true
11-27 10:13:11.001   820  4785 I ActivityManager: Killing 28238:com.sec.spp.push/u0a58 (adj 15): DHA:empty #37
11-27 10:13:11.011   820  1745 D ActivityManager: isAutoRunBlockedApp:: com.sec.spp.push, Auto Run ON
11-27 10:24:12.671  4235  4362 V Push_Plugin: execute: data=[{"android":{"senderID":"289396574454"},"browser":{"pushServiceURL":"http://push.api.phonegap.com/v1/push"},"ios":{"alert":"true","badge":"true","sound":"true"},"windows":{}}]
11-27 10:24:12.681  4235  4235 D SystemWebChromeClient: file:///android_asset/www/js/app.js: Line 85 : push success data=
11-27 10:24:12.681  4235  4235 I chromium: [INFO:CONSOLE(85)] "push success data=", source: file:///android_asset/www/js/app.js (85)
What can I do to resolve the problem?

To use phonegap-plugin-push I need install also cordova-plugin-fcm?

@S3r3n4 no, in fact that would be really bad as the two plugins would conflict with each other.

Ok, thanks so much, what can I do to find the reason of crash of my app?

Hi,
now the plugin works! :) I had change some configuration of cordova plugin facebook4, maybe the  two plugins was conflict but I'm not sure of that.
Thanks so much for your help!!! :)

@S3r3n4 https://github.com/phonegap/phonegap-plugin-push/blob/9afac3882d93f445f800be681b1ac491ececd7ff/docs/INSTALLATION.md#co-existing-with-facebook-plugin


AgentView support

What's this PR do?

Namespaces Mobile Commons specific config variables with a MOBILECOMMONS_ prefix:

MOBILECOMMONS_OIP_CAMPAIGNBOT, MOBILECOMMONS_OIP_DONORSCHOOSEBOT, MOBILECOMMONS_OIP_DONORSCHOOSEBOT_ENDED, MOBILECOMMONS_OIP_DONORSCHOOSEBOT_ERROR

Adds a new GAMBIT_CMD_MEMBER_SUPPORT config variable. If the member texts in the value during a CampaignBot conversation, they are opted into a Mobile Commons OIP defined by new config variable MOBILECOMMONS_OIP_AGENTVIEW.

The AgentView OIP conversation should be set to NOT trigger any mData's, which means all subsequent messages the member sends will be added to the Mobile Commons Agent View queue for member support to respond to, until they text in another Mobile Commons keyword.

Sends new CampaignBot member_support message to the member when they are opted into the Agent View OIP. This message should contain the {{keyword_continue}} variable to inform the member how to continue in CampaignBot after they have submitted their support questions.  {{keyword_continue}} renders our new MOBILECOMMONS_KEYWORD_CAMPAIGNBOTconfig variable.

The MOBILECOMMONS_KEYWORD_CAMPAIGNBOT should be set to the keyword defined on our CampaignBot mData, which posts to chatbot without a campaign (the same mData that our MOBILECOMMONS_OIP_CAMPAIGNBOT posts to). This allows the member to text in a keyword to continue where they left (loading their saved current_campaign).

The end result of all this makes our member_support copy look something like this:

Text back your question and I'll do my best to answer back within 24 hours. If you'd like to continue on {{title}}, text back {{keyword_continue}}.

Adds additional Gambit Jr. support for {{cmd_reportback}} and {{cmd_member_support}} for Gambit commands to use in CampaignBot messages.  Here's what an example menu_completed could read like:

Got you down for {{quantity}} {{rb_noun}} {{rb_verb}}. If you have {{rb_verb}} more, text {{cmd_reportback}}. If you have a question, text {{cmd_member_support}}

Refactors isCommandCacheClear(req) and isCommandReportback(req) to single isCommand(req, type) function with expected type values of cache_clear, reportback, and member_support

How should this be reviewed?
👀
Relevant tickets
#606
Checklist

[ ] Added required config vars on staging and production.
[ ] Documentation added for new features/changed endpoints.
[ ] Tested on staging.

Latest commits have been working well on staging, until Mobile Commons requests back to my phone display as failed. Don't see any errors in our Gambit app logs though 😕
Note I had to alter our chatbot Mobile Commons OIP to force sending MMS today in order to avoid rendered message content truncating at 160 chars -- wonder if that could be the issue?

Following up on the last comment, failed messages seem related to my profile specifically and due to a Mobile Commons "aggregator problem" with my phone and MMS messages (not SMS messages).
I did change our CampaignBot Staging OIP to "Force MMS" for the time being while we're in development -- this change was made to avoid our Gambit chatbot copy getting truncated (and put off on engineering for non-MMS members until we have our prototype finished).

@sergii-tkachenko 👍  ?


WebRTC.Native.Win32 change output from a .dll file to .exe

Hi,
Is it possible to change the output from an .dll to .exe. when compiling?
I tried changing in the settings "configuration type" from .dll to .exe, but does not work.
https://imgur.com/Zu80uMF

Sorry @polhaghverdian this is never possible. A library and an executable are 2 different things. You cannot convert a shared library to an executable.

Sorry @polhaghverdian this is never possible. A library and an executable are 2 different things. You cannot convert a shared library to an executable.

I dont want to convert, but to run it as an executable instead. The project seems to produce .dll file instead.

@polhaghverdian to convert from dll into an exe, you'll need to supply an entry point such as main() yourself. Usually though, you would link the webrtc dll against your application instead. Is there some reason you don't want to take that approach?

@stephenatwork I dont see it necessary to have an dynamic library, which complicates development, and debugging in my case. I could give a try but am convinced this wont be optimal. I need to have a project for the actual application and one for the library.

@polhaghverdian are you saying you want static linking? It is not clear to us what you are trying to achieve here, can you describe your use case please?

@djee-ms  Exactly am trying to achieve Static Linking ( Statically Linked Executable )

Ok then this is not currently supported. In v2.0 we plan to change the C++ interop layer, which currently has issues due to crossing DLL boundaries, and still have a DLL but make the C++ library statically linked by default (and using the DLL internally only), see the discussion on #123. Until then I'm afraid there's no simple solution.

@djee-ms
@stephenatwork
Thank you!


Update how-to-retrieve-iot-edge-logs.md

Been trying this out with UploadSupportBundle method but kept getting running then Cancelled after about 30 seconds as the status, could see you didn't have that listed in the docs so thought id add it !

@jonnychipz : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off

@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change.


For discussion.. signalling Indexer tests in lieu of Thread.sleep(...)

@ederign and I think @psiroky spoke about the obvious "elephant" in the room... indexing tests that like to wait. Thanks to @porcelli original code and the virtues of copy and paste we now have a lot of indexer tests across lots of repositories that happily wait. This PR includes a potential fix - or basis for a fix - for the wait state.
The code that runs the indexers consists of two nested threads; one runs constantly (or at least until a VFS is disposed) and it's nested child in reaction to a set of WatchEvents raised from VFS. It's the inner child that calls the indexers.
My change reports completion of the inner worker thread to an observer that can then perform tasks at different steps in a tests sequence. The test (or author) needs to know how many times the inner thread is invoked as you need to know the stage when the indexes should contain the correct information; for example ioService.delete(..) leads to the inner thread being started twice - one for the "real file" and again for "dot file" whereas ioService.write(..) leads to the inner thread being started once - for both the "real file" and "dot file```. So the tests currently set up "checks" to perform per completion of the inner thread.
Anyway, not for merge, but to start discussion about how to improve our indexing tests..

@csadilek @psiroky @ederign @porcelli ... for opinions please.

Jenkins please retest this.

@manstis what about, instead change our execution model (adding the observer), why not use Byteman to block/release/check? We already have some Byteman tests in our codebase: https://github.com/uberfire/uberfire/blob/master/uberfire-nio2-backport/uberfire-nio2-impls/uberfire-nio2-jgit/src/test/java/org/uberfire/java/nio/fs/jgit/JGitFileSystemProviderBytemanTest.java

I like this solution as it's low on complexity and makes the tests easy to read (not that I dislike the Byteman approach, but it is significantly more complex).
One minor suggestion I have is to improve the API used in tests...to add a call similar to this:
observer.onEventCount(3, () -> assertEvents());

instead of
observer.addInformationCallback(IndexObserverCallback.NOP);
observer.addInformationCallback(IndexObserverCallback.NOP);
observer.addInformationCallback(() -> assertEvents(3));

I guess my PR reflects the difference between me and Alexandre... I am simple (in mind) whereas he is complex. Let's wait for more comments (in any) before making any decision. Thanks for the feedback (so far).

I am also in favor of this approach when compared to Byteman.

That solution could be also be applied to fix this intermittent failing test https://kie-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/uberfire-pullrequests/794/testReport/junit/org.uberfire.ext.metadata.io/BatchIndexConcurrenyTest/testSingleConcurrentBatchIndexExecution/

Jenkins please retest this.

Jenkins please retest this

Jenkins please retest this

@porcelli are you working on a POC for byteman approach?

PR #628 as byteman alternative


[material-ui][Drawer] Type error on Android with the swipeable variant

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Steps to reproduce 🕹
I have this error for many users in my Sentry.
TypeError Cannot read properties of null (reading 'contains')
@mui/material/SwipeableDrawer/SwipeableDrawer.js handleBodyTouchStart 393:55
if (open && (hideBackdrop || !backdropRef.current.contains(nativeEvent.target)) && !paperRef.current.contains(nativeEvent.target))
Current behavior 😯
In my application side menu is impelemented with SwipeableDrawer. Users random get full screen errors becuase of this issue.
Expected behavior 🤔
MUI does not throw this error
Context 🔦
.
Your environment 🌎

npx @mui/envinfo
OS and browser copied from Sentry
  System:
    OS: Android 10
  Binaries:
    Node: 18.11.0 - ~/.nvm/versions/node/v18.11.0/bin/node
    Yarn: 3.2.4 - ~/.nvm/versions/node/v18.11.0/bin/yarn
    npm: 6.14.18 - ~/clouderp/node_modules/.bin/npm
  Browsers:
    Edge Mobile 117.0.2045
  npmPackages:
    @emotion/react: ^11.9.0 => 11.10.5
    @emotion/styled: ^11.8.1 => 11.10.5
    @mui/base:  5.0.0-alpha.116
    @mui/core-downloads-tracker:  5.11.7
    @mui/icons-material: ^5.6.2 => 5.11.0
    @mui/lab: ^5.0.0-alpha.81 => 5.0.0-alpha.118
    @mui/material: ^5.7.0 => 5.11.7
    @mui/private-theming:  5.11.7
    @mui/styled-engine:  5.11.0
    @mui/styled-engine-sc: ^5.7.0 => 5.11.0
    @mui/styles: ^5.7.0 => 5.11.7
    @mui/system:  5.11.7
    @mui/types:  7.2.3
    @mui/utils:  5.11.7
    @mui/x-data-grid:  6.3.0
    @mui/x-data-grid-pro: ^6.3.0 => 6.3.0
    @mui/x-date-pickers:  6.3.0
    @mui/x-date-pickers-pro: ^6.3.0 => 6.3.0
    @mui/x-license-pro:  6.0.4
    @types/react:  18.0.27
    react: 18.1.0 => 18.1.0
    react-dom: 18.1.0 => 18.1.0
    styled-components: ^5.3.5 => 5.3.6

Debugging without a reproduction is challenging. Could you please attempt to provide a CodeSandbox or create a minimal GitHub repository that demonstrates the issue? You can use the issue template as a helpful starting point.


Content_shell test of package:http/browser_client test fails by timeout

From @YuriKulaghin on June 22, 2016 7:55
Simple test of client.get(url) (see attached zip) gives timeout fail when started by command pub run test -p content-shell test/test.html, i.e. without browser window. If to select platform as dartium or chrome then test passes OK. If to start pub serve and content_shell manually and to select in content_shell window url http://localhost:8080/test.html then test passes OK. When test fails by timeout no data exchange tries are detected by tcpdump. Problem tested on Linux Ubuntu 12.04LTS amd64, CentOS 7.2 amd64 and dart-sdk/dartium/content_shell 1.17.1.
content_shell_test.zip
Copied from original issue: dart-lang/test#440

If this is only happening in content_shell and not Dartium, it's unlikely to be an issue with the test runner. I suspect that content_shell is somehow treating CORS headers differently—if I change your test to make a request to window.location.href rather than 'https://hacker-news.firebaseio.com', it works fine. I'm going to move this to the SDK repo.


Unset http.Client.Timeout to obey CommonOpts.Timeout

This PR leaves http.Client.Timeout unset so that CommonOpts.Timeout is obeyed when it's higher than the default timeout given to the go-eth2-client.
The timeout is set on every request to CommonOpts.Timeout or go-eth2-client's default timeout using context.WithTimeout, so not setting http.Client.Timeout should be safe.
Here's a scenario to reproduce the timeout issue:
client, err := auto.New(
	ctx,
	auto.WithTimeout(5*time.Second),
)
if err != nil {
	panic(err)
}

validators, err := client.(eth2client.ValidatorsProvider).Validators(ctx, &api.ValidatorsOpts{
	State:   "head",
	Common:  api.CommonOpts{Timeout: 30 * time.Second},
})
if err != nil {
	panic(err) // times out after 5 seconds
}

Looks good, thanks.


Rewrite hashcode computation for Uri.Path

Closes #6538
The actual fix would be along the lines of what was discussed here, but we'll have to wait for cats-uri for a definitive solution

I'm very sorry this PR missed the release, it's a good fix and I think it could have landed but unfortunately nobody had reviewed and I was focused on https://github.com/typelevel/fs2/security/advisories/GHSA-2cpx-6pqp-wf35.
@danicheg would you be able to look again when you have a chance? Thanks!

To be honest, I'm not sure that we're free to do that change in 0.23 and not in 1.0.

I mean, it's a bug fix, if the equality and hashcode are not consistent with each other then one of them has to change :)

I mean, it's a bug fix

Sure, but we change the whole mechanism of hashCode calculating. So this might affect users somehow (in a pretty strange way though). But maybe I'm overthinking, so feel free to decide on your own about this one.


[Spanner]: Instance Database limit (100) reached easily.

Alternatives:

Keep decrementing the time to consider a DB stale.

Currently at 48hrs which already doesn't give us time to check on weekend failures.
If there's a lot of activity on the repo, and since all tests are executed on presubmit, we can always reach limit even if we delete tha databases inmediately after running the tests, we only need a set number of presubmit checks executing at the same time.
@laljikanjareeya You mentioned something about there being leftover DBs from before. I just tried deleting them on the UI but they have backups, I will try and submit a PR just for the sake of deleting them later, tweaking the fixture code to include this once DBs whose name is my-db-, and then close the PR. Maybe that fixes it and we don't have to consider anything else.

Consider creating an instance per test run, and deleting the stale instances after 72hours.

It would address #1173
What's the max amount of intances that we can have? We would created one per tests run, as opposed to many databases per test run?
How long does it take to create an instance?

@skuruppu and @laljikanjareeya thoughst welcomed.

@laljikanjareeya do you now why we might be creating so many databases? Is it that we're creating a database per test?
Either that, or the tests are run too many times a day since they're run for all PRs.
I think in Node.js, we create instances each run (it doesn't take very long, maybe a couple of seconds). Then instances are deleted at the end of the test. If the test crashes before the resources can be cleaned up, at the beginning of the test run, we delete all stale backups/instances that are older than 4 hours.
So we might have to do that here, especially given that the tests are run much more frequently in this repo than in the Node.js repo (which is spanner-specific).
Assigning to @laljikanjareeya to prepare a fix.

Thanks for #1190 @laljikanjareeya, all the old DBs are now gone and we have less than 10 now.
Maybe let's keep things as are for a week and see if we see the resource exhasuted failures again. If we don't see them, it was just because of the old DBs. If wee see it, then we'll have to create new instances.
I'll leave this issue open so that I remember to check for failures in presubmits and CI by this time next week.

We are creating only two database in test and one is for backup that we never delete.
CI Project there were more than 50 old databases and they never deleted based on current logic that we implemented, I have submitted a PR to delete old databases.
In Node.js we also use SPANNERTEST_INSTANCE environment variable for instance I don't know it been set on CI or not.
We can do same thing that @amanda-tarafa  mention create new instance on each test cycle and delete stale instances after 72 hours but it might be create problem of timeout in backup test.
I just created PR#1191 to check if databases are more than 94 than delete 5 database from the list that has been created first.

This should have been addressed by #1190 and #1191. Thanks @laljikanjareeya .


browserify always bundles the minified file

I'm trying to understand what is happening with my local build and I'm trying to figure out what this transform (#326) is supposed to do.
The issue I'm having is that regl is the only dependency in my build which is minified in development, which makes it hard/impossible to debug.
Steps to reproduce in a clean directory
npm i regl
echo "require('regl')" > index.js
npx browserify index.js > bundle.js

The bundle.js now contains the minified regl.
What is the purpose of the browserify transform that was added in #326? If I remove it, browserify correctly uses the main file specified in package.json and I get a non-minified bundle.js

@Prinzhorn I believe you need to add the --debug flag to your browserify args. Then it will swap out regl with the unminified version. TBH I often just explicitly require('regl/regl') when I want to dig into node_modules and debug the internals.
You can test this by running:
echo "require('regl')" | browserify - --debug

which has the unminified source as opposed to
echo "require('regl')" | browserify

which uses the minified source.

Since this is noted in the documentation:

By default if you compile regl with browserify then all error messages and checks are removed. This is done in order to reduce the size of the final bundle and to improve run time performance.
If you want error messages and are using browserify make sure that you compile using --debug. Not only will this insert debug messages but it will also give you source maps which make finding errors easier.
Alternatively, consider using budo for your live development server. budo automatically compiles your code in debug mode and also provides facilities for live reloading.

I'll close this issue, but would gladly accept a PR if there's an inconsistency I'm not catching or if there's something you think would make this more straightforward.

Thanks, I understand.

I'll close this issue, but would gladly accept a PR if there's an inconsistency I'm not catching or if there's something you think would make this more straightforward.

As far as I understand, other projects (react and my projects included) use NODE_ENV for this purpose. When combined with uglify dead code elimination it behaves as you described.
Examples:
https://github.com/facebook/react/search?q=node_env&type=Code
https://github.com/reduxjs/redux/search?q=node_env&type=Code
I, as a user regl somewhere in my project, will then set NODE_ENV globally and get either a debug build (with ALL modules being unminified) or a production bundle (with ALL modules being compressed).
In dev if(process.env.NODE_ENV === 'development') is compiled to if('development' === 'development'). In production it turns into if('production' === 'development') and is removed by uglify.
envify does that, which is uncluded in https://www.npmjs.com/package/tinyify

envify - Replace environment variables—by default, replaces NODE_ENV with "production"

I think the particular reason for the extra step is that there's some rollup setup to remove checks at the AST level so that you don't need to write the conditional if (process.env.NODE_ENV === 'development') check.command(...); throughout the codebase in order for it to get removed in the production version. Alternatively you could put the conditional inside check.command, but then if you're reallly trying to squeeze out performance, you still have a large number of no-op function calls that don't get removed.
In other words, I believe it leans on rollup to perform the removal since it's more targeted and concise than uglify—so that the transform swaps the rollup'd version as needed.
I'm not sure it's a perfect solution (or that a perfect solution exists), but glad to help if it can be made clearer, whether through docs or tweaks that preserve the fundamental goals!

Now that I know about --debug i can use it instead of manually patching regl inside node_modules. However, I believe it is a misuse of the flag since it has side effects not intended by browserify

When opts.debug is true, add a source map inline to the end of the bundle. This makes debugging easier because you can see all the original files if you are in a modern enough browser.

Or does it? As far as I understand you're shipping the unminified regl when --debug is set, instead of a source map?

so that you don't need to write the conditional if (process.env.NODE_ENV === 'development') check.command(...); throughout the codebase

I see. I does make sense what you're saying, but it looks like a homebrown solution specific to this repository if I understand https://github.com/regl-project/regl/blob/8f26f111a913cd9f7f239ebcdf691189e82c7a5f/rollup/plugins/remove-check.js correctly.


Don't start

I will not start, tears fall down. why? npm run dev cont`t

Hi @zhoupeihuang , I need more information

Try live demo

T h s !


Checkstyle Standards for Powershell Modules

Proposal: Checkstyle Standards for Powershell Modules
Author: Jordan Borean @jborean93
Date: 2017/05/21

Status: New
Proposal type: core design
Targeted Release: 2.4
Associated PR: TBC
Estimated time to implement: 4 weeks

Motivation
Trying to keep the Powershell modules consistent with each other and define
a standard that is enforcable without human intervention.
Problems
Some of the current problems we have today are;

There is a mixture of ways Powershell modules are written which causes confusion and fragmentation
The Python modules use PEP for standards but no automated checked are in place for Powershell
There is also no official standard for how we write these modules, this proposal will both create that standard and enforce it

Solution proposal
The proposed solution is to use 2 Powershell modules called PSScriptAnalyzer
and Pester to run a check style analysis
as well as generate reports on this analysis in a CI like fashion. These tools
should run on the module affected on every pull request.
PSScriptAnalyzer is a tool that can run checkstyle analysis on powershell
scripts based on a custom ruleset. It has the ability to specify rules that you
wish to scan for as well as writting custom rules if the in built ones don't
match your requirements.
Pester is a framework for running tests that can easily integrate in a CI
system. While it has a lot of features we can use in the future like unit
testing for powershell modules and code coverage reporting this proposal is
limited to using Pester to run PSScriptAnalyzer and generate an NUnit XML
report at the end of the process. There are numerous tools out there to convert
an NUnit xml to HTML for reporting purposes.
While these modules need to run in Powershell with the ability to install
Powershell 5 on both Windows and Unix we have various options available to us
when running these tests.
The following rule settings for PSScriptAnalyzer is as follows
@{
    IncludeRules = @(
        'PSAvoidUsingCmdletAliases',
        'PSAvoidUsingEmptyCatchBlock',
        'PSAvoidUsingPositionalParameters',
        'PSAvoidUsingWMICmdlet',
        'PSAvoidUsingWriteHost',
        'PSMisleadingBacktick',
        'PSPlaceCloseBrace',
        'PSPlaceOpenBrace',
        'PSReservedCmdletChar',
        'PSReservedParams',
        'PSUseConsistentIndentation',
        'PSUseConsistentWhitespace'
    )

    Rules = @{
        PSAvoidUsingCmdletAliases = @{
            Whitelist = @('')
        }
        PSPlaceCloseBrace = @{
            Enable = $true
            NoEmptyLineBefore = $true
            IgnoreOneLineBlock = $false
            NewLineAfter = $false
        }
        PSPlaceOpenBrace = @{
            Enable = $true
            OnSameLine = $true
            IgnoreOneLineBlock = $false
            NewLineAfter = $true
        }
        PSUseConsistentIndentation = @{
            Enable = $true
            IndentationSize = 4
        }
        PSUseConsistentWhitespace = @{
            Enable = $true
            CheckOpenBrace = $true
            CheckOpenParen = $true
            CheckOperator = $true
            CheckSeparator = $true
        }
    }
}

The documentation for these rules can be found here. These rules are
open to debug they are just what I believe we should be aiming for but happy to
add/remove/modify rules based on a consensus with the community.
The second part of this proposal is to go through our existing modules and
ensure they conform to this new standard. Because of the different coding
styles in place it is hard to.
As well as implementing these checks into the existing testing process we will
also need to modify the existing modules to ensure they pass the new checks
added.
An example of the output of running this check on an existing module like
win_acl
PS C:\Users\jbore> powershell.exe -File C:\dev\ansible\test\runner\powershell-pester.ps1

Describing Testing against PSSA rules
   Context PSSA Ansible Rules

RuleName                            Severity     ScriptName Line  Message
--------                            --------     ---------- ----  -------
PSAvoidUsingCmdletAliases           Warning      win_acl.ps 67    'where' is an alias of 'Where-Object'. Alias can
                                                 1                introduce possible problems and make scripts hard to
                                                                  maintain. Please consider changing alias to its full
                                                                  content.

    [-] Should pass PSAvoidUsingCmdletAliases 1.03s
      Expected: {0}
      But was:  {1}
      13:                     $failures.Count | Should Be 0
      at <ScriptBlock>, C:\dev\ansible\test\runner\pester-tests.ps1: line 13
    [+] Should pass PSAvoidUsingEmptyCatchBlock 127ms
    [+] Should pass PSAvoidUsingPositionalParameters 19ms

RuleName                            Severity     ScriptName Line  Message
--------                            --------     ---------- ----  -------
PSAvoidUsingWMICmdlet               Warning      win_acl.ps 67    File 'win_acl.ps1' uses WMI cmdlet. For PowerShell 3.0 and
                                                 1                above, use CIM cmdlet which perform the same tasks as the
                                                                  WMI cmdlets. The CIM cmdlets comply with WS-Management
                                                                  (WSMan) standards and with the Common Information Model
                                                                  (CIM) standard, which enables the cmdlets to use the same
                                                                  techniques to manage Windows computers and those running
                                                                  other operating systems.

    [-] Should pass PSAvoidUsingWMICmdlet 30ms
      Expected: {0}
      But was:  {1}
      13:                     $failures.Count | Should Be 0
      at <ScriptBlock>, C:\dev\ansible\test\runner\pester-tests.ps1: line 13
    [+] Should pass PSAvoidUsingWriteHost 25ms
    [+] Should pass PSMisleadingBacktick 20ms

RuleName                            Severity     ScriptName Line  Message
--------                            --------     ---------- ----  -------
PSPlaceCloseBrace                   Warning      win_acl.ps 41    Close brace does not follow a non-empty line.
                                                 1

    [-] Should pass PSPlaceCloseBrace 28ms
      Expected: {0}
      But was:  {1}
      13:                     $failures.Count | Should Be 0
      at <ScriptBlock>, C:\dev\ansible\test\runner\pester-tests.ps1: line 13

RuleName                            Severity     ScriptName Line  Message
--------                            --------     ---------- ----  -------
PSPlaceOpenBrace                    Warning      win_acl.ps 29    Open brace not on same line as preceding keyword. It should
                                                 1                be on the same line.
PSPlaceOpenBrace                    Warning      win_acl.ps 37    Open brace not on same line as preceding keyword. It should
                                                 1                be on the same line.
PSPlaceOpenBrace                    Warning      win_acl.ps 39    Open brace not on same line as preceding keyword. It should
                                                 1                be on the same line.
PSPlaceOpenBrace                    Warning      win_acl.ps 43    Open brace not on same line as preceding keyword. It should
                                                 1                be on the same line.
PSPlaceOpenBrace                    Warning      win_acl.ps 48    Open brace not on same line as preceding keyword. It should
                                                 1                be on the same line.
PSPlaceOpenBrace                    Warning      win_acl.ps 54    Open brace not on same line as preceding keyword. It should
                                                 1                be on the same line.
PSPlaceOpenBrace                    Warning      win_acl.ps 59    Open brace not on same line as preceding keyword. It should
                                                 1                be on the same line.
PSPlaceOpenBrace                    Warning      win_acl.ps 65    Open brace not on same line as preceding keyword. It should
                                                 1                be on the same line.
PSPlaceOpenBrace                    Warning      win_acl.ps 69    Open brace not on same line as preceding keyword. It should
                                                 1                be on the same line.
PSPlaceOpenBrace                    Warning      win_acl.ps 74    Open brace not on same line as preceding keyword. It should
                                                 1                be on the same line.
PSPlaceOpenBrace                    Warning      win_acl.ps 78    Open brace not on same line as preceding keyword. It should
                                                 1                be on the same line.
PSPlaceOpenBrace                    Warning      win_acl.ps 82    Open brace not on same line as preceding keyword. It should
                                                 1                be on the same line.
PSPlaceOpenBrace                    Warning      win_acl.ps 100   Open brace not on same line as preceding keyword. It should
                                                 1                be on the same line.
PSPlaceOpenBrace                    Warning      win_acl.ps 238   Open brace not on same line as preceding keyword. It should
                                                 1                be on the same line.

     You can see
them here.
Dependencies

Powershell 5.0
PSScriptAnalyzer
Pester

Testing
These tests only need to run on the module that is affected in the PR, there is
no reason that we need to run it on all modules but that is possible if we wish
to go down that path.
Documentation
New docs page created that will show the rules and examples that we are
enforcing as well as some guidelines on how to run these tests locally
before raising a PR.
Anything else?
While this is not part of the scope for this proposal I believe using a library
like Pester brings us a step forward to implementing unit tests on our
powershell modules and bringing more in line with our processes around Python
modules.
This is my first proposal so let me know if I have missed anything or whether I
have done something wrong.

Looking good. My only concern is that I do all my development on Linux, so I won't be able to test conformity locally, so it will require a few more (amend) commits before getting it right. Which sometimes is a big time-consumer.

You should be able to run these modules on a linux box if you install powershell. I haven't tested it myself but the docs indicate it is supported.

@mattclay It would be nice to have this integrated as soon as possible (say, by AnsibleFest Londen ? :-P).
@nitzmahone @jborean93 @jhawkesworth Up to us to play with it already so we can have balanced discussion and understand the possible trade-offs.
The way I see it, after the discussion, we only have to check off on the proposed rules, but that shouldn't be a concern for already looking to integrate this mechanism in Shippable.

Matt is on holiday and will only get back the Monday before London.
I'd like to discuss this with him before it gets implemented.
So to set expectation:

This sounds good
Check back in a month

Is this still being considered?

@aaronk1 This is already implemented, but we are not enforcing all rules we considered originally AFAIK. I think we had a set of style-related requirements that are not being enforced. Maybe we should have that discussion next Windows WG meeting ?

@jborean93 While fixing my Windows modules to validate with pslint, I came across this (ansible/ansible#37718):
PSPossibleIncorrectComparisonWithNull $null should be on the left side of equality comparisons.

And I don't agree based on readability. But maybe there's a good reason to do this in Powershell ?

@dagwieers I agree it's definitely not as readable. However, it's intended to avoid incorrect comparisons against $null. The example in the issue you linked demonstrates the problem:
https://github.com/nightroman/PowerShellTraps/blob/c1b35f876a0ce737ed31cf6c1e2747b073521733/Basic/Comparison-operators-with-collections/looks-like-object-is-null.ps1#L2-L8

@mattclay My problem here is that we know that $value is a string, we already enforce it when assigning parameter values. Pylint is simply not smart enough, still we are going to make things less readable where there's really no issue. So to me these are false positives.

@dagwieers That rule shouldn't have false positives unless the type is unspecified:
https://github.com/PowerShell/PSScriptAnalyzer/issues/200#issuecomment-114946701

The rule is now raised only if the object on the LHS has an unspecified type or is an array.

Is this a bug in PSScriptAnalzyer, or is the LHS an unspecified type?

@mattclay I don't know if we can force the type from within a function and if it gets inherited on assignment, if not we may have to force the type on each assignment. Let's see what @jborean93 @nitzmahone think about this.

@jborean93 Do we also want to enforce some of the coding style-related tests, as we originally contemplated ?

Closing as this has been implemented ages ago, just run ansible-test sanity --test pslint --docker default to run the checks locally.


dual check should performed if entitlement is registered

See detailed description in the commit message.

unit test still needed

I have added a small smoke test to check legacy authz for user without poweruser role.

http://ci-cloudbreak.eng.hortonworks.com/job/cloudbreak-real-ums-test-legacy-nonpower/13


on rule add its selecting first value

When we add a new rule first element in list is already selected.
You can see the behaviour on official doc example: https://sapientglobalmarkets.github.io/react-querybuilder/
Is there any way to disable that?
I want to disable that behaviour since I am showing a nested list with labels and I don't want label to be selected.

Update: While trying to figure out why left hand operand's value is selected, stumbled upon following code in QueryBuilder.tsx.
const createRule = (): RuleType => {
    const field = fields[0].name;

    return {
      id: `r-${nanoid()}`,
      field,
      value: '',
      operator: getOperatorsMain(field)[0].name
    };
  };

The field is always fields[0].name while creating new rule, which is causing the issue of first value being selected on left hand side operand.
@jakeboone02 I think this should be configurable. What do you think?

That code is actually why it chooses the first field, not why it chooses the first value.  The value code is a little farther down, see https://github.com/sapientglobalmarkets/react-querybuilder/blob/master/src/QueryBuilder.tsx#L201-L234.
How would you model the configuration?  What should the options be and what would the behavior of each option be?

Oh, I think I misunderstood.  I thought you were talking about the value being selected, not the field.  Same question though:  what should the configuration look like and how should each option behave?

I think it make sense to provide configuration param functions to provide field's default and value's default data.
From code I can see in case of value we are only handling if array has length then set [0].value else if type is checkbox then false. But that's a limited set. Someone may want to specify their own set of defaults for different types based on values selected for field.
for e.g.
for number it can be 0
for floatingnumber it can be 0.0
for date it can be an epoch / today's date in user defined format
for email it can be empty or default support email address value of end user's choice

I am thinking we should add defaultField and defaultValue function which will return string values. This will give user an opportunity to either not set field and value on new rule or specify program specific defaults.
controlElements={
  ...
  defaultField?: (fields: any) => string
  defaultValue?: (fieldData: any, values: any) => string
  ...
}

We can take out the logic of existing function's default selection part in new functions and use them as fallback functions if user does not wish to override them.
The behaviour:
If user passes defaultField then user function's returned value will be used. It needs to be string, if its empty then we can run existing logic to set it to [0].name and empty string if it's not an array.
If user passes defaultValue then user function's returned value will be used. It also need to be string, if its empty then we can run existing logic to set it to [0].value and empty string if it's not an array and false if it is eligible for that based of type which is currently happening.
I believe this will not impact any existing users since they are not passing these controlElement options.

@saurabhnemade thanks for the detailed explanation.  I implemented the defaultField and defaultValue props mostly as you suggested, with a few changes, in PR #157.  The props are at the top level rather than within the controlElements object, and the function parameters are a little different (they match the internal default functions).  Let me know if that satisfies your needs.

Yup. It totally does the job 💯
Thanks @jakeboone02 !!

This feature is in v3.7.0.


Only Two Password Formats

Many sites (iCloud for one) have complicated password requirements-- ie. passwords must contain caps and lowercase, passwords must contain >=1 number, passwords must contain >1 symbol. Extend the configurability to add more possible formats for each password, at least one with symbols and uppercase letters included.

I'll need some kinda deterministic algorithm to generate these. I'm thinking maybe just get the first letter of every word in the readable password with a period at the end. Not sure about numbers.

I'm open to ideas on how to solve this.

I devised the following algorithm, to generate a password with numbers, symbols and uppercase letters from both the conventional and the readable password.

From the conventional password, we may transform it by using a permutation of the characters we want to add:

import math
import string
import random

# A random shuffle of string.punctuation + string.ascii_uppercase
to_add = '*>OI+D~}E{AF"`KXR\[J:-&#BQWN;$%TGPZ.=U,_HS()@L\'|<M]YCV/?!^'
required = (string.ascii_lowercase,
            string.ascii_uppercase,
            string.digits,
            string.punctuation)

def nth_perm(S, n):
    '''Compute the n-th lexicographic permutation of the alphabet S.'''
    p = []
    for l in range(len(S) - 1, -1, -1):
        i, n = divmod(n, math.factorial(l))
        p.append(S[i])
        S = S[:i] + S[i + 1:]
    return p

def transform(keyword, password):
    res = []
    perm_number = len(keyword) * sum(map(ord, keyword))
    chosen_perm = nth_perm(to_add, perm_number % math.factorial(len(to_add)))
    for i, c in enumerate(password):
        # 2/3 of the original is preserved
        if i % 3:
            res.append(c)
            continue
        # We index from the bottom of the string, because that's where the
        # permutation changes most
        res.append(chosen_perm[-((i + len(keyword)) % len(to_add) + 1)])
    # There's a little possibility that the required chars aren't there
    for i, req in enumerate(required):
        if not set(req).intersection(res):
            res[i] = req[0]
    return ''.join(res)

The string to_add was shuffled just to mix the characters, in order to avoid many repetitions when we do chosen_perm[...]. Also, we index chosen_perm from the bottom and we use negative indices because otherwise the results would be too similar of even identical for different keywords.

For the readable password, we might add a symbol or an uppercase letter in between the words. The additional characters could be chosen depending on the length / characters of the preceding word. The end result would be something like:
Diffidence_6_hollers_*fluorocarbon_U_varnished-_traffic

@rubik Thanks for the comment. I've been busy recently so haven't had time to properly check it out. Is that algorithm deterministic? I see you used the random module.

@libeclipse Yes, it's deterministic. Actually the random module is a leftover from a previous version and I've only used it to generate the to_add string. This is just to get better looking passwords.

@rubik could you look over that PR?


240804_amb - IF command Refactor

Refactor of IF command to be more consistent
Also added a couple functions that will be used for additional Label conversion support (coming soon)

Looks like this also has changes made to prior PR. Will resubmit after previous PR is merged


Check Webhooks

Thank you for your contribution ! We will try and get back to you as soon as possible. xD.


Provide 3.8 and 3.9 python versions of TrustyAI image

In ODH/RHODS it might be reasonable to have (same as for other images) a TrustyAI image for python 3.9 (n) as well as python 3.8 (n-1) versions, this probably can be beneficial for easier adoption, depending on user needs.

related PR: https://github.com/opendatahub-io/notebooks/pull/164


PWA for Mobile doesn’t work: “Error Not Found”

Preflight Checklist

[x] I agree to follow the Code of Conduct that this project adheres to.
[x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

You must agree to search and the code of conduct. You must fill in this entire template. If you delete part/all or miss parts out your issue will be closed.
If you are technical, you should reporting bugs along the lines of https://marker.io/blog/how-to-write-bug-report. If you are not technical, we will make allowances, please try to make an effort to understand the process.
Describe the bug
PWA does not work on iOS. Shortcut added to Home Screen and opens page with “Error Not Found”
To Reproduce
Steps to reproduce the behavior:

Go to apps.diagrams.net
Click on Share Button
Add to Home Screen
Click icon
See error

Expected behavior
Apps.diagrams.net opens in PWA
Screenshots
If applicable, add screenshots to help explain your problem.

draw.io version 24.2.7

Smartphone (please complete the following information):

Device: [e.g. iPhone6] IPad Pro M2
OS: [e.g. iOS8.1] iOS 17.4
Browser [e.g. stock browser, safari] Safari
Version [e.g. 22]

I tested the problem in incognito/private mode with all browser extensions switched off, write "yes" below:

Yes

Additional context
Add any other context about the problem here.

Try using 24.2.9.

I'm seeing version 24.2.18 as latest on mobile and it's showing same error.

Visit https://clear.diagrams.net and try again please.

Works perfectly now. Thank you both!

Works perfectly now. Thank you both!


[Bug]

How you out here building a custom remote framework but having obvious errors in ur code.

(quick-install script)

The issue occurred because the code was executed within a script instead of a command line. As a result, the script did not have sufficient permissions to utilize game:GetService("HttpService").HttpEnabled = true

Command Bar instead of Script


How to "stop" closing modal if form invalid

Hey guys,
I have a form in a Semantic UI Modal, and I use the jQuery Form Plugin (http://malsup.com/jquery/form/#validation) to submit the form via ajax. The "submit" process of the form is triggered by the modal "ok" button. But if the form is invalid, the modal is still closed.
How can I "stop" the modal close procecedure?
Thanks a lot!

Adjust the selector object for close in settings.
http://beta.semantic-ui.com/modules/modal.html#settings


Crontab - Allow L with # syntax for the week field  (enhanement)

Allow for the ability to use the L for the week field for a crontab entry
You can then specify implied dates like:
MON#L means the last Monday in the last week of the month
FRI#L means the last Friday of the Month
Since there are either 4 or 5 weeks in a month, you can specify tasks to run for last week and not be concerned if there is 4 or 5 weeks for any month.

Hi Norman, I believe this is already implemented, per the documentation for the cron expression evaluator:

L stands for "last". When used in the day-of-week field, it allows you to specify constructs such as "the last Friday" (5L) of a given month. In the day-of-month field, it specifies the last day of the month.

https://github.com/aptible/supercronic/tree/master/cronexpr#l
https://github.com/aptible/supercronic/tree/master/cronexpr#implementation
Are you reporting that this doesn't work, or have you not tried it?

Does not work as well as a L by itself does not work

Can you give an example of the entry, and when you want it to run? I'm not understanding from your examples how it's not meeting your needs:

MON#L means the last Monday in the last week of the month

In supercronic, this  would be 1L in the day-of-week field

FRI#L means the last Friday of the Month

In supercronic, this  would be 5L in the day-of-week field


Upload is stuck

First of all the video is uploaded as a draft, and it get stuck while processing it for some reason. And I think it's because youtube asks me to check the COPPA (if it's made for kids or not). I changed a bit of the default script and also added the option to choose if it's gonna keep it draw or not, but it didn't seem to work. Please tell me if I'm doing something wrong/dumb or if I am dumb by myself.
Here is the script:
const { upload } = require('youtube-videos-uploader');

const credentials = { email: '*', pass: '*', recoveryemail: '*' }

const onVideoUploadSuccess = (videoUrl : any) => {
    // ..do something..
}

const video1 = { path: 'C:\\Users\\BlykS\\Desktop\\test\\video.mp4', title: 'video', language: 'english', channelName: 'my secondary channels name', keepDraw: 'false', onSuccess:onVideoUploadSuccess, skipProcessingWait: true, onProgress: (progress : any) => { console.log('progress', progress) } }

upload (credentials, [video1]).then(console.log)

And here is what happens in my terminal:
C:\Users\BlykS\Desktop\test>npx ts-node uploader.ts
progress { progress: 0, stage: 0 }
progress { progress: 3, stage: 0 }
progress { progress: 7, stage: 0 }
progress { progress: 10, stage: 0 }
progress { progress: 14, stage: 0 }
progress { progress: 17, stage: 0 }
progress { progress: 20, stage: 0 }
progress { progress: 24, stage: 0 }
progress { progress: 27, stage: 0 }
progress { progress: 30, stage: 0 }
progress { progress: 34, stage: 0 }
progress { progress: 37, stage: 0 }
progress { progress: 41, stage: 0 }
progress { progress: 44, stage: 0 }
progress { progress: 47, stage: 0 }
progress { progress: 51, stage: 0 }
progress { progress: 54, stage: 0 }
progress { progress: 57, stage: 0 }
progress { progress: 61, stage: 0 }
progress { progress: 64, stage: 0 }
progress { progress: 71, stage: 0 }
progress { progress: 78, stage: 0 }
progress { progress: 81, stage: 0 }
progress { progress: 84, stage: 0 }
progress { progress: 88, stage: 0 }
progress { progress: 95, stage: 0 }
progress { progress: 100, stage: 0 }
progress { progress: 51, stage: 0 }
progress { progress: 78, stage: 0 }
progress { progress: 87, stage: 0 }
progress { progress: 95, stage: 0 }
progress { progress: 0, stage: 0 }
progress { progress: 1, stage: 0 }
progress { progress: 2, stage: 0 }
progress { progress: 3, stage: 0 }
progress { progress: 4, stage: 0 }
progress { progress: 5, stage: 0 }

Yeah, the skipProcessingWait doesn't seem to do anything atm. It waits until the processing is done.
It may be best to set your whole channel for kids or not so it doesn't cause a issue here.
What do you mean by keepDraw?

Yeah, the skipProcessingWait doesn't seem to do anything atm. It waits until the processing is done.

It may be best to set your whole channel for kids or not so it doesn't cause a issue here.

Ok I'll try that.

What do you mean by keepDraw?

I was searching through the issues to fix my problem with youtube always processing the video as draft and I thought readme was outdated but It's not.

It may be best to set your whole channel for kids or not so it doesn't cause a issue here.

Ok after trying that and waiting the process, I got another error:
progress { progress: 100, stage: 2 }
C:\Users\BlykS\node_modules\youtube-videos-uploader\dist\upload.js:5
        function fulfilled(value) { try { step(generator.next(value)); } catch (e) { reject(e); } }
                                                         ^
TypeError: Cannot read properties of undefined (reading 'substring')
    at C:\Users\BlykS\node_modules\youtube-videos-uploader\src\upload.ts:218:41
    at Generator.next (<anonymous>)
    at fulfilled (C:\Users\BlykS\node_modules\youtube-videos-uploader\dist\upload.js:5:58)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

But after checking what was causing the problem one more time, I realized that youtube stuck on the upload due to the copyright claim check and idk how to pass this without clicking then Next button myself and posting it.

found any fix?
seems like project is ded

seems like project is ded
Stop saying BS, last commit on this project is 5 days ago, you know ?

@Icaro1447 You could update your issue's title to speecify that it's for copyrighted claimed videos.

@Icaro1447 You could update your issue's title to speecify that it's for copyrighted claimed videos.

Well, I discovered that it doesn't matter if the video has copyright or not. The tool simply won't upload anything. It saves everything as draft and I dont know what to do anymore.

This sometimes happens to me, when the videos is left as a draft.
It used to happen if I had another video uploading (separately)
But it happens somewhat randomly still.
I don't have any copyright issues with my videos.

@Icaro1447 You could update your issue's title to speecify that it's for copyrighted claimed videos.

Well, I discovered that it doesn't matter if the video has copyright or not. The tool simply won't upload anything. It saves everything as draft and I dont know what to do anymore.
Did you make sure to do all the steps described in the readme file ? Usually when a video is stuck as a draft, it's likely because it's missing a default upload value for a field.

@Icaro1447 You could update your issue's title to speecify that it's for copyrighted claimed videos.

Well, I discovered that it doesn't matter if the video has copyright or not. The tool simply won't upload anything. It saves everything as draft and I dont know what to do anymore.

Have tried with another tool using a random video and happened again, and tried on a different channel as well, no idea whats causing it

Well, I discovered that it doesn't matter if the video has copyright or not. The tool simply won't upload anything. It saves everything as draft and I dont know what to do anymore.

Did you make sure to do all the steps described in the readme file ?
Usually when a video is stuck as a draft, it's likely because it's missing a default upload value for a field.

Feel free to post the MR then so we can all benefit from this :P


I don't see the default admin/admin account.

Is their a seed script somewhere I didn't find it as part of the EF migration, maybe I am missing something or my setup is wrong.
I am using MYSQL.
I checked the AspNetUsers table it is empty.

I thought the migrations didn't execute but they did but the admin/admin user is missing. AspNetRoles is also empty I am able to create a user that has IsAdmin=true in the Authors table but the admin View is not providing much interaction with the blog itself.

The seed data with default admin account is for demo purposes only. When you start new blog from scratch, you just register new account using actual blogger name and start building your own content.

I did that but is there an interface to add roles because the interface I see only let's me modify the current user
May 16, 2020 13:10:07 rxtur<EMAIL_ADDRESS>
The seed data with default admin account is for demo purposes only. When you start new blog from scratch, you just register new account using actual blogger name and start building your own content. —
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub[https://github.com/blogifierdotnet/Blogifier/issues/199#issuecomment-629685714], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AAEXZ3BZ62EW6UQ4YQMQZEDRR3JH3ANCNFSM4NC573HQ]. [https://github.com/notifications/beacon/AAEXZ3GFVGPC7PNQEL4TB6DRR3JH3A5CNFSM4NC573H2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEWED3UQ.gif]

Blogifier is a single-user personal blog...
If you are looking for a multi-user Angular version of Blogifier, please find it under Blogifier.SPA repository.

Ah ok thank you.
May 16, 2020 13:16:28 rxtur<EMAIL_ADDRESS>

Blogifier is a single-user personal blog... If you are looking for a multi-user Angular version of Blogifier, please find it under Blogifier.SPA repository.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub[https://github.com/blogifierdotnet/Blogifier/issues/199#issuecomment-629686561], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AAEXZ3FJHK4FXGO2D3F4KA3RR3J7RANCNFSM4NC573HQ]. [https://github.com/notifications/beacon/AAEXZ3CVQT7ZRTTQUIV46ATRR3J7RA5CNFSM4NC573H2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEWEECII.gif]

No problem, glad to help.


Issue 44

Thanks for opening these PRs! Just to clarify, does this PR supercede #45?

Thanks for opening these PRs! Just to clarify, does this PR supercede #45?

I think commit 83b1d6a actually merges #45 into this one. I've been using that commit successfully while waiting for the PR to be merged.

Got it. This looks good, so I'll go ahead and merge this and close #45. Thanks to both of you for looking into this issue!


Add dynamic public prefixes through constitution

Previously the maps for kv would be either all private or all public. This makes it more dynamic, moving the option into a constitution-managed map.
Every key is kept in the private map, keys that match the public prefix will also be kept in a public map which is viewable in the ledger. By default there are no public prefixes and so everything is private.
Fixes #179
Code caveats:

Currently no way to have the CCF sandbox start with a custom constitution https://github.com/microsoft/CCF/issues/4572

I think it would be much preferable to have this as constitution-first rather than going with this intermediate step but at least this shows a potential way forward.

I think we should add a comment somewhere that this is a bit of a hack, and that the nicer solution to avoid duplicate storage would be to add an iterator API to the CCF kv::Map so that we can foreach across two maps (private and public).

Needs to wait for a new CCF release so that we have the cose tooling


Use new rich text element

Motivation
Use new @simply007org/kontent-react-components richtect element component for resolution.
Checklist

[ ] Code follows coding conventions held in this repo
[ ] Automated tests have been added
[ ] Tests are passing
[ ] Docs have been updated (if applicable)
[ ] Temporary settings (e.g. variables used during development and testing) have been reverted to defaults

How to test
If manual testing is required, what are the steps?

Blocked by https://github.com/Simply007/kontent-react-components/issues/3


KYLIN-1505 Combine guava filters with Predicates.and

https://issues.apache.org/jira/browse/KYLIN-1505

Combine guava filters with Predicates.and(filters)
Combine hbase RowKeyOnlyFilter and PrefixFilter with FilterLists

Combine changes into #31, so that only need to merge single patch into master, so treat this one as resolved.


[FT][ERROR] CUDA runtime error: operation not supported

Description

I try to run fauxpilot, so I believe the branch is v5.0.
docker-ce  Version: 20.10.18
image: moyix/triton_with_ft:22.06
in container: CUDA Version: 11.7.
on hostmachine: Driver Version: 515.65.01 CUDA Version: 11.7.
GPU and machine: tesla M60 on aws g3s

Reproduced Steps
1. git clone https://github.com/moyix/fauxpilot.git
2. cd fauxpilot
3. ./setup.sh
4. choose the minimal model with only 2G
5. sudo ./launch.sh

in launch.sh, docker-compose will run this script:
    image: moyix/triton_with_ft:22.06
    command: bash -c "CUDA_VISIBLE_DEVICES=${GPUS} mpirun -n 1 --allow-run-as-root /opt/tritonserver/bin/tritonserver --model-repository=/model"

I found out that M60 doesn't support FasterTransformer, but same issue occurs on T4.


Upgrade to coola 0.0.12

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (631e04b) 100.00% compared to head (6468638) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #302   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           14        14
  Lines         1292      1300    +8
  Branches       147       147
=========================================
+ Hits          1292      1300    +8

Impacted Files
Coverage Δ

src/redcat/comparators.py
100.00% <100.00%> (ø)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Proof of concept to IsPick util

Not sure of nested examples because it is not possible to achieve with Pick util.
Do you have idea how to implement it?

I think I have basic functionality of IsPick. More complex examples are something more than is Pick. And for my purpose I still need sth more than IsPick, because I need to check also nested props and arrays.
But IsPick is a good start.

Thank you for your PR!
Everything looks good to me!
I just added some simple test case that helps grasp what this is about, whould you merge: https://github.com/garronej/tsafe/pull/16
Would you go the extra mile of adding a documentation page for it? Here is the invite link.
It's realy easy to eddit. GitBook provide a "what you see is what you get" editor.
Thanks again.