Spring Integration tests UI changes

Tests type and configuration
Unit tests can be generated in No Configuration and Spring configuration mode.
Integration tests can be generated only with existing Spring configuration.
Tests type and mock strategy
Unit tests are generated with Engine only.

in No configuration mode any mock strategy can be used, default one is Mock everything outside the class.
in Spring configuration mode  is defaulted to Mock using Spring configuration and disabled.

Integration tests are generated with Fuzzing only, so mocking is defaulted to Do not mock and disabled.
Tests type and other settings

[x] When No Configuration is selected, Tests type  is disabled and defaulted to Unit tests.
[x] When existing Spring configuration is selected, Tests type is enabled and two options available: Integration tests and Unit tests.
[x] When Integration tests is selected, Test frameworks must contain JUnit4 and JUnit5
TestNg must disappear from the list of suggestions.
[x] When Integration tests is selected, XML configs must disappear from the list of suggestions in Spring configuration.

Environment
IntelliJ IDEA Ultimate 2023.1

Right now fuzzer can only generate null for most of the interface types (except some collections, for which custom ValueProviders have been written). When we can't generate value other than null we should at least consider using mocks, which will contradict the premise of this issue, stating that: "[if we use] fuzzing only, [then] mocking is not available at all"

@IlyaMuravjov This issue is about settings available on UI only.
Currently Fuzzing is not supporting mocks. So Mocking settings should not be available.

@EgorkaKulikov
Let's consider the following conflict case:

User selects XML-based configuration in Spring configuration field.
User selects Integration tests in Tests type

Shall we hide Integration tests after the first step?

Also I would not exclude XML configuration list from suggestions when Integration tests are selected.
Just if user selects one of XMLs, Unit tests are selected.
Why?
To keep priority and consistency of Spring configuration control.


change ./run_benchmark to ./run_benchmark.py

change ./run_benchmark to ./run_benchmark.py in README.rst
and change benchmarks/full.pdbs to input/full.pdbs

Thanks - fixed now.


Does gpt-fast work on V100 GPUs?

Everything works on my A6000s and A100s, but not on the older V100 (says compute capability is low). Are there plans to add support for the legacy devices? Thanks!

We haven't tested on V100s so I'm not sure. I thought it worked but haven't checked.


documentation: enable swagger to use vendoring

Swagger is a tool used to generate documentation based on
declarative comments in the code, the problem with it was that it
had an issue with vendoring. We have fixed that issue in
https://github.com/yvasiyarov/swagger/pull/120
and now we can use our vendor directory. This fix was need because
we were bringing dependencies with 'go get' which in some PRs were
causing to fail for time outs, an issue aside of the PRs.
In this change we add the required argument to enforce to check for
vendor directory and remove the 'go get'.
Signed-off-by: Leoswaldo Macias<EMAIL_ADDRESS>

Coverage remained the same at 66.944% when pulling 973d79afb428c5fd8a39d86f3a5531729fe002e4 on leoswaldo:leoswaldo/travis-swagger into 9ae419ac21e6282e939861163d4fdc94d64910f1 on 01org:master.

Coverage decreased (-0.02%) to 66.922% when pulling 973d79afb428c5fd8a39d86f3a5531729fe002e4 on leoswaldo:leoswaldo/travis-swagger into 9ae419ac21e6282e939861163d4fdc94d64910f1 on 01org:master.

Coverage decreased (-0.03%) to 66.91% when pulling 973d79afb428c5fd8a39d86f3a5531729fe002e4 on leoswaldo:leoswaldo/travis-swagger into 9ae419ac21e6282e939861163d4fdc94d64910f1 on 01org:master.

Looks good to me.  Bet this speeds up our build a bit as well.


test(ticdc): fix batch_add_table test case

What problem does this PR solve?

Issue Number: ref #11879
What is changed and how it works?
set more times to check if the table exists
Check List
Tests

Integration test

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
`None`.

/retest

close with https://github.com/pingcap/tiflow/pull/11886


Revert "Update docs to remove references to JP team"

Reverts WWCodeTokyo/speak-her-db#169

Omg sorry, completely wrong merge!


Remove duplicate option in cargo-publish man page

The --host option was listed twice; this commit removes one of the duplicates.

@bors: r+
Thanks!

:pushpin: Commit aae3560 has been approved by alexcrichton

:hourglass: Testing commit aae3560 with merge 4d55e55...

:sunny: Test successful - cargo-cross-linux, cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-gnu-32, cargo-win-gnu-64, cargo-win-msvc-32, cargo-win-msvc-64
Approved by: alexcrichton
Pushing 4d55e558a71ad0196d503096b44aec940ff3215b to master...


Add close syscall test

Closes #107

Oops.. it still needs one PR.. hold on

Include this in your PR:
diff --git a/internal/syscall/src/lib.rs b/internal/syscall/src/lib.rs
index 41f7f49..7f0cfe4 100644
--- a/internal/syscall/src/lib.rs
+++ b/internal/syscall/src/lib.rs
@@ -167,6 +167,7 @@ pub trait SyscallHandler: AddressValidator + Sized {
             libc::SYS_getgid => self.getgid(),
             libc::SYS_geteuid => self.geteuid(),
             libc::SYS_getegid => self.getegid(),
+            libc::SYS_close => self.close(a.try_into().map_err(|_| libc::EINVAL)?),

             SYS_GETATT => self.get_attestation(),

You forgot Signed-off-by: greyspectrum<EMAIL_ADDRESS>in the commit message

You forgot Signed-off-by: greyspectrum<EMAIL_ADDRESS>in the commit message

Fixed.

It looks like two tests are failing for AMD SEV. I have an Intel machine, so tests pass locally.

It looks like two tests are failing for AMD SEV. I have an Intel machine, so tests pass locally.

Yeah, our expanded integration test coverage has uncovered a bottleneck with our SEV VM launch process. I have patches to ameliorate this for now: https://github.com/enarx/enarx-keepldr/pull/158

Congratulations 👏 🥳


AWS Nitro enclave shutting down automatically

We have created a nitro-based ec2 instance by using instance type c6a.8xlarge and have created a NodeJS-based application.
The following operations are performed inside the ec2 instance.
Enclave was generated by using the following command and the .eif file was successfully created
Command = nitro-cli build-enclave --docker-uri ec2-user/nitro-test-app:latest --output-file nitro-enclave.eif
Enclave was run by using the following command.
Command = nitro-cli run-enclave --cpu-count 2 --memory 3524 --eif-path nitro-test.eif --debug-mode
The results of the run command were as follows
Start allocating memory... Started enclave with enclave-cid: 16, memory: 3524 MiB, cpu-ids: [1, 17]
{
"EnclaveName": "hello",
"EnclaveID": "i-096e001cdd5c912c9-enc182d5585cfe18db",
"ProcessID": 7666,
"EnclaveCID": 16,
"NumberOfCPUs": 2,
"CPUIDs": [ 1, 17 ],
"MemoryMiB": 3524
}
But when we run the command to check the results of the started enclave the results were empty
Command = nitro-cli describe-enclaves
Result = []
Below are the results of the logs
Logs:
[enc-*******0f0dc91:***0][WARN][2022-08-24T22:35:28.916Z][src/enclave_proc/mod.rs:207] Received hang-up event from the enclave. The enclave process will shut down.
[enc-*******0f0dc91:***0][INFO][2022-08-24T22:35:28.916Z][src/enclave_proc/mod.rs:541] Enclave process 5430 exited event loop.
What could be the possible reason that the enclave instance is immediately stopping after instantiating?

Can you try running your image on docker first and see if it exits immediately?

thanks @richardfan1126 for your response, yes I have tried this as well and it was still exiting immediately.

Then you should fix your Dockerfile
Have you set the RUN or ENTRYPOINT?

@richardfan1126 docker image is up and running on the linux ec2 instance below are the results
CONTAINER ID   IMAGE     COMMAND                  CREATED         STATUS         PORTS      NAMES
4b4cf988801b   cisca     "docker-entrypoint.s…"   2 minutes ago   Up 2 minutes   8080/tcp   boring_moser
I ran this command  = nitro-cli run-enclave --enclave-name nitro_enclave --cpu-count 2 --memory 3516 --eif-path hello.eif --enclave-cid 10
Result = Start allocating memory...
Started enclave with enclave-cid: 10, memory: 3516 MiB, cpu-ids: [1, 17]
{
"EnclaveName": "nitro_enclave",
"EnclaveID": "i-0723118e06c5d205c-enc182df10d5942db3",
"ProcessID": 6116,
"EnclaveCID": 10,
"NumberOfCPUs": 2,
"CPUIDs": [
1,
17
],
"MemoryMiB": 3516
}
But when I ran nitro-cli describe-enclaves
Result are empty = []
Log results =
[enc-xxxxxxx:6116][INFO][2022-08-27T11:29:58.666Z][src/enclave_proc/mod.rs:571] Enclave process PID: 6116
[enc-xxxxxxx:6116][INFO][2022-08-27T11:29:58.666Z][src/enclave_proc/mod.rs:479] Received command: Run
[enc-xxxxxxx:6116][INFO][2022-08-27T11:29:58.666Z][src/enclave_proc/mod.rs:272] Run args = RunEnclavesArgs { eif_path: "hello.eif", enclave_cid: Some(10), memory_mib: 3516, cpu_ids: None, debug_mode: None, attach_console: false, cpu_count: Some(2), enclave_name: Some("nitro_enclave") }
[enc-xxxxxxx:6116][INFO][2022-08-27T11:29:58.667Z][src/enclave_proc/resource_manager.rs:371] Allocating memory regions to hold<PHONE_NUMBER> bytes.
[enc-xxxxxxx:6116][INFO][2022-08-27T11:29:58.667Z][src/enclave_proc/resource_manager.rs:453] Allocated 225 region(s): 222 page(s) of 2 MB, 3 page(s) of 1024 MB
[enc-xxxxxxx:6116][INFO][2022-08-27T11:29:59.039Z][src/enclave_proc/resource_manager.rs:693] Finished initializing memory.
[enc-xxxxxxx:6116][INFO][2022-08-27T11:30:08.382Z][src/enclave_proc/mod.rs:281] Enclave ID = i-0723118e06c5d205c-enc182df10d5942db3
[enc-182df10d5942db3:6116][WARN][2022-08-27T11:30:08.555Z][src/enclave_proc/mod.rs:207] Received hang-up event from the enclave. Enclave process will shut down.
[enc-182df10d5942db3:6116][INFO][2022-08-27T11:30:08.555Z][src/enclave_proc/mod.rs:541] Enclave process 6116 exited event loop.
CMD is set in Docker file, following is my docker file
FROM node:16
Create app directory
WORKDIR /usr/src/app
Install app dependencies
A wildcard is used to ensure both package.json AND package-lock.json are copied
where available (npm@5+)
COPY package*.json ./
RUN npm install
If you are building your code for production
RUN npm ci --only=production
Bundle app source
COPY . .
EXPOSE 8080
CMD [ "node", "server.js" ]

Can you run nitro-cli console and see the application log?
I doubt that your image can even start because the Nitro Enclaves doesn't have network connection and you cannot expose a port on it

@richardfan1126 thanks for asking it again, yeah it was fixed. Problem was in my Docker file.


Just Updated and lost all automation

Describe the bug
just updated and after restart i got this

Reproduction steps
reproduces on every restart
Expected behaviour
N/A
Tariff Code
No response
Integration Version
v8.4.3
Home Assistant Version
Home Assistant 2023.10.1
Fresh Install?
After upgrading
Home Assistant Logs
Logger: homeassistant.setup
Source: setup.py:288
First occurred: 16:48:38 (1 occurrences)
Last logged: 16:48:38
Error during setup of component automation
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/setup.py", line 288, in _async_setup_component
result = await task
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/automation/init.py", line 252, in async_setup
await _async_process_config(hass, config, component)
File "/usr/src/homeassistant/homeassistant/components/automation/init.py", line 972, in _async_process_config
entities = await _create_automation_entities(hass, updated_automation_configs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/automation/init.py", line 856, in _create_automation_entities
cond_func = await _async_process_if(hass, name, config_block)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/automation/init.py", line 985, in _async_process_if
checks.append(await condition.async_from_config(hass, if_config))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/condition.py", line 246, in async_from_config
return cast(ConditionCheckerType, await factory(hass, config))
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/device_automation/condition.py", line 55, in async_condition_from_config
return trace_condition_function(platform.async_condition_from_config(hass, config))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/sensor/device_condition.py", line 256, in async_condition_from_config
numeric_state_config = condition.numeric_state_validate_config(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/condition.py", line 1011, in numeric_state_validate_config
config[CONF_ENTITY_ID] = er.async_validate_entity_ids(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/entity_registry.py", line 1380, in async_validate_entity_ids
return [async_validate_entity_id(registry, item) for item in entity_ids_or_uuids]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/entity_registry.py", line 1380, in
return [async_validate_entity_id(registry, item) for item in entity_ids_or_uuids]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/entity_registry.py", line 1349, in async_validate_entity_id
raise vol.Invalid(f"Unknown entity registry entry {entity_id_or_uuid}")
voluptuous.error.Invalid: Unknown entity registry entry 06e8f15ef29ea58ffcc3406078b44c3e
Logger: homeassistant.setup
Source: setup.py:185
First occurred: 16:48:51 (1 occurrences)
Last logged: 16:48:51
Setup failed for default_config: (DependencyError(...), 'Could not setup dependencies: automation')

Sorry that you're receiving this issue. Did you update HA or the integration? I'm assuming as you believe it's this integration you only updated the integration?
As there is no mention of my integration's code in the error logs (seems like a HA bug as this integration doesn't touch automations) and I'm unable to reproduce the issue (I've just updated to the latest version successfully on my test machine), there is very little I can do to fix this issue I'm afraid. The only thing I can suggest is to remove, restart and reinstall the integration.

solved the issue by going back to a previous backup, i will try again over the weekend with the octopus update and see if it happens again


[CA] Moved listers to util package

This is required to make them usable from outside of the project.

lgtm


docs(ionicons): Added tags to icons

I added a few tags to increase searchability since I was having trouble finding the correct icons for both push notifications and privacy policy.
Feel free to reject if the tags are more misleading than helpful 🙂

LGTM, thanks!


Display list of supported documents

A pop-up containing the list of supporting documents should appear on clicking "List of supported documents" link.

Pop-up could be an image or text.

I would like to work on this issue @QAZIMAAZARSHAD

https://user-images.githubusercontent.com/70853906/120662203-90ed0600-c4a6-11eb-873a-9562787be719.mp4

Basics layout is ready just the close button is not working!! @QAZIMAAZARSHAD sir

If you have any other suggestions, pls let me know @QAZIMAAZARSHAD sir

No, You got it all wrong
In list of supported documents you have to display list like:
Adhar card for age proof
passport for address etc.

And also your display design and style were not good. Try to make it attractive/improve the design.

Can i make it same way as is shown in above image @QAZIMAAZARSHAD ?

Yaa sure,
Keep in mind you are making a list of supporting documents for the voter Id card.

okk thanks alot @QAZIMAAZARSHAD sir

https://dot.gov.in/sites/default/files/2016_11_18 POIA-AS-II.pdf?download=1#:~:text=Card with address.-,Kisan Passbook with photograph Kisan Passbook with address.,older than last three months).

Can i just redirect our viewers to this document containing all information regarding list of supporting documents for the voter Id card @QAZIMAAZARSHAD ?

I wanted to have a pop-up display.
But if you are unable to do it just make this document downloadable or redirect it to that document.
I will assign this issue to someone else.

Okk i will make a pop-up display but all the supported documents should be the in same way as shown in the image or do i need to add something else @QAZIMAAZARSHAD sir?

The image you have chosen is very complex, a simple and cool design pop-up will do good.

I am talking this image sent by you
https://user-images.githubusercontent.com/56196640/120663281-82531e80-c4a7-11eb-88e4-9bbbaaad8ef3.png

I showed you this image to explain to you what is meant by supporting documents.

okk @QAZIMAAZARSHAD sir

@QAZIMAAZARSHAD Can the modal pop-up contain an image?

Uploading 1.mp4…

Uploading 1.mp4…

@QAZIMAAZARSHAD sir pls check my work and review it!!

Nice,

Are there any others things that I should improve or include @QAZIMAAZARSHAD sir?

If you think you can improve it then you should definitely give it a try.

Okk @QAZIMAAZARSHAD sir but do we need to add some more examples of documents or these examples are enough?

Close button is working fine already, only thing that i can think of improving is adding one image or maybe changing style of text or add some more examples!!

Okk @QAZIMAAZARSHAD sir but do we need to add some more examples of documents or these examples are enough?

It's fine, but you can if you want to.

Close button is working fine already, the only thing that I can think of improving is adding one image or maybe changing the style of text or add some more examples!!

ok fine.

I will keep you updated sir, Thank you so much @QAZIMAAZARSHAD sir!!

Fine @Sourav61.
Wait till I review your PR.

okk @QAZIMAAZARSHAD  sir

Sir i will be able to display list of supported documents in hindi only when #207 gets resolved!!

There is no such issue.

Make PR its fine, and I was talking about popup in hindi.html not popup in Hindi language as well. Now their is no hindi.html.
Just add your popup in home.html and make PR.

So should the popup be submitted only in English language now @QAZIMAAZARSHAD sir?

Yes

okk @QAZIMAAZARSHAD  sir!!

Update your repo, I think you are not familiar with new changes.

I have forked and cloned just now @QAZIMAAZARSHAD sir, will make a PR very soon!!

Also, fetch upstream(Most important)

okk @QAZIMAAZARSHAD sir!!

@Sourav61 It has been 23 days and this issue is still unresolved, if you need any help you can ask @nlok5923.

@QAZIMAAZARSHAD Sir i am very sorry for delay, but i wasn't able to find any time previous few weeks as i was ill firstly due to side effects of covid vaccine and then renovation at my house i got ill for rest of time as i am allergic to dust, so i was ill for rest of the time as well. But, sir i will try my best to resolve issue as soon as possible.
Again, Sorry for the delay @QAZIMAAZARSHAD  Sir.

No problem

@QAZIMAAZARSHAD sir is this fine for modal popup width??

Ya better

But @QAZIMAAZARSHAD  sir do we need to remove scroll bar because a popup is just for information for an instance and i guess it would be fine without removing the scroll bar?

ok

Sir pls check the below video and review it!!
https://user-images.githubusercontent.com/70853906/123619903-46517600-d827-11eb-997a-bcb598abec8e.mp4

Fine make PR.


swift-driver: repair the build after #980

kill is a non-portable function from the Unix C library.  Replace the
functionality with Windows SDK's TerminateProcess.  Encode SIGINT as
a NT error for the process termination code.

@swift-ci please test


'C:\Program' is not recognized as an internal or external command

Steps to reproduce
Tell us about your environment:

ndb version:  1.0.4
Platform / OS version: Win10ProX64
Node.js version: 10.5

What steps will reproduce the problem?
Please include code that reproduces the issue.

It should not display that error
What happens instead?
While launching it shows this error:
ndb node index.js
'C:\Program' is not recognized as an internal or external command,
operable program or batch file.
Debugger listening on ws://<IP_ADDRESS>:65091/76c88dbd-da7b-4b65-bc3f-f629b3d13206
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.

The issue here that we do not properly process spaces inside path to node binary on Windows. We will fix it soon.

I think I meet the same problem, here is the error:
ndb npm run dev
'C:\Program' is not recognized as an internal or external command, operable program or batch file. 'C:\Program Files\nodejs\\node.exe: Files\nodejs\node_modules\ndb\node_debug_demon\preload.js is not supported in NODE_OPTIONS'

Please try 1.0.7. The issue should be fixed there :)


Upgrade to 2.0.0 broke error-pages

I am trying to upgrade to 2.0.0 of this docker image, great job re-writing it in Go!
I would have thought it would have been a seamless upgrade however on 2.0.0 I am getting the message. Hi there! Error pages are available at the following URLs: /{code}.html. If I rollback to 1.8.0 it works fine.
1.8.0 logs
error-pages-644fdd7c94-g5pzr error-pages <IP_ADDRESS> - - [05/Oct/2021:13:43:13 +0000] "GET / HTTP/1.1" 404 3526 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/94.0.4606.61 Safari/537.36" "x.x.x.x, <IP_ADDRESS>"

2.0.0 logs
error-pages-6b4cc76777-4mt4l error-pages {"level":"info","ts":1633441272.6022592,"msg":"HTTP request processed","useragent":"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/94.0.4606.61 Safari/537.36","method":"GET","url":"/","status_code":404,"connection_close":false,"duration":0.000023755}

You can see my use of error-pages with the middleware and ingressroute here:
https://github.com/onedr0p/home-cluster/tree/main/cluster/apps/networking/error-pages
Is a requirement of the new version supposed to force us to annotate each ingress with using this middleware? If so, can that be changed to be global again?
Thanks!

Hi @onedr0p!
On the first version, the request with an empty URI returned code 200 with the text 404 error. I can bring this behavior back if required. Will this solve your problem?

That's would be excellent, thanks!


Fixed Query.select('field') with no from table.

Fixes #140 Added a check when selecting from a field using a string argument for the field name when there are no tables currently being selected from in the query

Coverage increased (+0.004%) to 97.933% when pulling c27ac7c4f10d0fa8c8b2d9454e14dc3eb819d0b6 on fix_queries_without_from into d47a1e1c44617bb49cf91cc57ac3f7722a4d5c6f on master.

Coverage increased (+0.004%) to 97.933% when pulling c27ac7c4f10d0fa8c8b2d9454e14dc3eb819d0b6 on fix_queries_without_from into d47a1e1c44617bb49cf91cc57ac3f7722a4d5c6f on master.


SP5 RenderManager: EnableRendering flag

~For consistency it would be nice to add the RenderLock() and RenderLock() methods for consistency with previous behavior to compliment the PreRenderLock event handler added in #3095~
Update: I'm going to add a EnableRendering flag to allow this:
void MyDangerousOperation(){

    // disable new renders
    formsPlot1.Plot.RenderManager.EnableRendering = false;

    // wait for the current render to finish
    while (formsPlot1.Plot.RenderManager.IsRendering) {}

    // perform your dangerous operation
    myScatterPlot.DataSource.Clear();

    // permit new renders
    formsPlot1.Plot.RenderManager.EnableRendering = true;

    // force the plot to redraw
    formsPlot1.Refresh();
}

Note that EnableRendering skips renders while PreRenderLock hangs renders

https://scottplot.net/faq/async/

Thank you for the update. However, I am unable to use formsPlot1.Plot.Rendermanager.EnableRenderring = true; as you have implemented the EnableRenderring flag as private in the modified code.


Specifying partial version for pip/setuptools/virtualenv/wheel does NOT pull latest of that major

For the python['version'] property the documentation states,

If a partial version is given, use the latest available version matching that prefix.

I've discovered that even though the documentation only mentions true and false for pip/setuptools/virtualenv/wheel you can also specify a specific or partial version. I am going to submit a PR to update the documentation to indicate that in case people haven't discovered this on their own, but while testing the partial version matching scenario with eg pip['version'] = '9' and running a smoke test with test-kitchen, I discovered it is only pulling the first major version and not the latest of that series. My PR will reflect that you should specify the full version if you are pinning a previous version for some reason. This might just be a pip behavior aka WONTFIX but after a bit of research I think it could be solved with some Ruby creating a constraints file (since pip 7.1) and using that to narrow down the major/minor/patch with a requirement specifier like wheel >0.28,<0.30.
https://pip.pypa.io/en/stable/user_guide/#constraints-files
https://pip.pypa.io/en/stable/reference/pip_install/#requirement-specifiers
My reproduction files aka poise_python_wrapper:
attributes/default.rb
default['poise-python']['options']['pip_version'] = '9.0' # or '9'
default['poise-python']['options']['setuptools_version'] = true
default['poise-python']['options']['version'] = '2.7'
default['poise-python']['options']['virtualenv_version'] = '15'
default['poise-python']['options']['wheel_version'] = '0.29.0'

recipes/default.rb
python_runtime node['poise-python']['options']['version']

test/smoke/default/default_test.rb
describe pip('pip') do
  it { should be_installed }
  its('version') { should cmp == '9.0.3' }
end

# Because we don't pin setuptools we don't test for a specific version
describe pip('setuptools') do
  it { should be_installed }
  #its('version') { should cmp == '39.0.1' }
end

describe pip('wheel') do
  it { should be_installed }
  its('version') { should cmp == '0.29.0' }
end

describe pip('virtualenv') do
  it { should be_installed }
  its('version') { should cmp == '15.1.0' }
end

Test output:
  Pip Package
     ✔  pip should be installed
     ∅  pip version should cmp == "9.0.3"

     expected: "9.0.3"
          got: 9.0.0

     (compared using `cmp` matcher)

  Pip Package
     ✔  setuptools should be installed
  Pip Package
     ✔  wheel should be installed
     ✔  wheel version should cmp == "0.29.0"
  Pip Package
     ✔  virtualenv should be installed
     ∅  virtualenv version should cmp == "15.1.0"

     expected: "15.1.0"
          got: 15.0.0

     (compared using `cmp` matcher)

That logic applies only to the version of Python. pip/wheel/setuptools are installed using pip so the version number for those follows pip semantics.

Going to close this since partial version matching for those packages is not a feature and I have no plans to add it.

Yeah after doing some testing I noticed that because python is installed using package it benefits from apt's fuzzy matching while the pip wrapper is using == which is literal, so you'll get 9.0.0 if you just specify 9. I'm going to do a bit more testing, but I discovered that if you quote the package name and version constraints to pip it will allow that, so it may be another option rather than the constraints file to allow the same fuzzy latest.

No, it's not using apt fuzzy matching. The language version prefix stuff is a feature of poise-languages (which is why it works with all providers).

Ahhh interesting. Well it appears that == is hardcoded somewhere in poise-python for pip so even though I can pip install 'wheel >0.28, <0.30' myself, I can't pass default['poise-python']['options']['wheel_version'] = '>=0.29,<0.30' to the resource. I'll update my PR to remove the partial version verbiage and only mention supplying a full version to override the latest. It would be awesine to be able to use the pip native version constraints, but we can work around it by explicit versions for now.

@espoelstra That is correct, the python_package resource works like most other package resources, not just a simple shell out. It analyzes both the currently installed and candidate versions. Syntax like that could be added (it was recently put in for the yum package provider), but currently is very limited. The more complex behavior like that I add, the more I have to reach into pip's internals because it's surprisingly hard to determine the candidate version for a set of options.


Fix React dependency to enable XCode 12 build

https://github.com/facebook/react-native/issues/29633#issuecomment-694187116

I will recheck and make a release tmr.


Fix ambiguity warnings from Colors

This implements #74, extending Base.parse but in a way that avoids ambiguity warnings. Alternatively, we could use a different name for this.
Also a few other things in separate commits. GtkInteract.jl (an unregistered package) expects values to be implemented, so I thought I'd throw that in here (I can move it to GtkInteract if you prefer). The last commit is the one that makes me most nervous about the absence of tests, esp. since my IJulia is tuned to 0.4.

Thanks for doing this! I should keep in mind to test with GtkInteract. I think a refactor can help with tests. Unfortunately, I haven't been showing a lot of love for this package of late :( it should be straightforward to test parts not tied to IJulia. Will do this one day soon...


cdc changefeed would be blocked when initialize and close the sink

At the moment, when the downstream sink is down, changefeed does not report errors in time, this would cause some problems,

a changefeed with an offline sink will block other changefeeds, which means other's checkpoint won't be progressed. #4241

we can solve the problem by:

[x] #4383
[x] #4384
[x] #4385

closed, since all sub-issues resolved.


Chief Executive Officer can the sign contract

(This issue is a work-in-progress, so I'm locking it until I've finished documenting it fully. If you want to edit it, let me know.)
Additional context
This is a sub-issue of the  [META] Implement the funding compliance and contracting process #2622
User story

As the CEO, I want to sign the contract, so the contractor can start the work they've received funding for.

This issue has been moved to the OTF specific repo https://github.com/OpenTechFund/apply-app/issues/10


TextEdit.SetFontSize() not setting font size

Have tried to use TextEdit.SetFontSize() the same way I have used it with the Label element, but when I have looked at the Mimic example I found that SetFont() and SetSubstrateFontSize() are used instead. It is a bit unexpected that SetFontSize() is available, but has no effect. In fact, using SetFont() and SetSubstrateFontSize() also had no effect. :)
Have tried manipulating font size in the code below:
TextEdit textEdit = new TextEdit();
textEdit.SetFont(DefaultsService.GetDefaultFont(5));
textEdit.SetSubstrateText("Placeholder");
textEdit.SetSubstrateFontStyle(FontStyle.Regular);
textEdit.SetSubstrateFontSize(5);
textEdit.SetHeightPolicy(SizePolicy.Fixed);
textEdit.SetHeight(5);

Could you please let me know if I am missing something in my code?

Strange but your code works fine for me.
public class MyWindow : ActiveWindow
{
    public override void InitWindow()
    {
        // window parameters
        SetParameters("MyWindow", "MyWindow", 300, 300);

        TextEdit textEdit = new TextEdit();
        textEdit.SetFont(DefaultsService.GetDefaultFont(5));
        textEdit.SetSubstrateText("Placeholder");
        textEdit.SetSubstrateFontStyle(FontStyle.Regular);
        textEdit.SetSubstrateFontSize(5);
        textEdit.SetHeightPolicy(SizePolicy.Fixed);
        textEdit.SetHeight(5);

        AddItem(textEdit);
    }
}

Result:

But I do not understand why do you set font size to 5?))
May be I do not understand your question... Do SetFontSize(), SetFont() and SetSubstrateFontSize() have no effect in your demo app?

May be you are confused that I used SetFont(DefaultsService.GetDefaultFont(5)) instead of SetFontSize(5). I did that only to show that there is class-service DefaultService that could be useful.


luci-themes: luci.main.mediaurlbase not set correctly

Currently by default theme Bootstrap is installed but
luci.main.mediaurlbase (it holds the current active theme) still has
openwrt.org set.
I did not find the mechanism how LuCI starts Bootstrap theme but the
installation should set luci.main.mediaurlbase correctly.
Signed-off-by: Christian Schoenebeck<EMAIL_ADDRESS>

Hm, usually the mediaurlbase is set by LuCI when the theme is changed in Admin -> System -> Language & Style.
Not sure if autoswitching to a newly installed theme is the desired behaviour?

Is there a way to detect inside LuCI which one is the current active theme, without reading mediaurlbase ?

When installing a service like privoxy or samba on OpenWrt, it is also auto-enabled and started without asking the user. Why not set the theme to the newly installed one ?
Building the default, bootstrap is installed but mediaurlbase is still set to openwrt.org without this theme is installed.

Yeah I guess we can autochange the theme upon install - I see no harm in that.

This is a really old and already closed PR and the answer is not really needed at the moment, but I will document my findings here anyhow...
The answer to the implicated question in "I did not find the mechanism how LuCI starts Bootstrap theme" in the first post, is probably the fallback mechanism built into dispatcher.lua.
https://github.com/openwrt/luci/blob/master/modules/luci-base/luasrc/dispatcher.lua#L243
As far as I understand, if no mediaurlbase it set or it points to a non-existing theme, dispatcher.lua then goes through all defined themes and tries to find one with a valid header (themes/%s/header). If found, that is used as the fallback theme.
That has probably been the reason why bootstrap worked even without the correct mediaurlbase being set. The commit in this PR has enabled each theme to set the option correctly, reducing the need for the fallback logic. (But that logic is still needed in case the currently active theme is uninstalled and another theme needs to be activated at the next boot).
I corrected today the default mediaurlbase value to bootstrap with 1209ab6ba617.


Update third_party/fasm

Vendor test failures are due to https://github.com/SymbiFlow/symbiflow-arch-defs/issues/1915, and not due to any changes in the repo (proof: https://github.com/SymbiFlow/symbiflow-arch-defs/pull/1912)


Mongo

PR to capture discussion.
From a Mongo Source perspective I think this is good. Interesting point re 'how do we capture the source?'.
It raised some questions to me about the use of resources.

Initially I was thinking that Mongo(Resource) should be a factory. So should have buildConnection(connection, collection). That would leave each Processor to define it's own connection settings and hence lead to duplication
Then I thought that perhaps the Mongo(Resource) should have its own settings (as it is a component) so in effect you can provide a default (which is processor can override if they wish). This is obviously better than 1.
Then I saw your code about the resourceKey setting -> Mongo resource instance.

I think these are all valid use cases (depends a bit on how the configuration is done, which we aren't defining in core so needs to be flexible).
So I've spilt up into Mongo and MongoFactory (both resources).  With the theory:

If you have a Processor which has wants to manage its own mongo then you can just call MongoFactory
If you want to use a named (or unnamed) Mongo resource instance (ie via context) you can use Mongo

To help manage these different options you
Both Mongo and MongoFactory take an MongoSettings which get merged to form a settings (ie MongoFactory can be used to provide default settings)
Psuedo config code:
resource:
  - name: DefaultMOngoFactory
    type: MongoFactory
    settings:
       connection: mongodb://localhost:27017
       database: annot8
  - name: LocationGaz
     type: Mongo
     settings:
         # Don't override anything just provide the db
        collection: locations
  - name: MongoSource
     type: Mongo
     settings:
        database: docs
        collection: unprocessed

pipeline:
- MongoSource
    settings:
      mongo: MongoSource
 - Gazetteer:
    settings:
       mongo: LocationGaz
-  AnotherMongoProcessor:
    settings:
      connection: mongo://another.host
      database: another
      collection: different

Haven't had a chance to review the code yet (I'll try to look later this week), but I like the approach you've described above.


Achieve and maintain a Core Infrastructure Initiative

achieve and maintain a Core Infrastructure Initiative Best Practices Badge.
refer to

CNCF Graduation Criteria：https://github.com/cncf/toc/blob/main/process/graduation_criteria.md
Best Practices Criteria for Free/Libre and Open Source Software (FLOSS): https://github.com/coreinfrastructure/best-practices-badge/blob/main/doc/criteria.md#best-practices-criteria-for-freelibre-and-open-source-software-floss

done
https://bestpractices.coreinfrastructure.org/zh-CN/projects/6232#quality


desock question

Hello,
first of all thank you for your code! I tried desock with test file provided in the repo and it works well. Then I moved onto a target I'm currently fuzzing (Abyss Web Server) and I'm facing some issues now. When I run desock like this:
PREENY_INFO=1 PREENY_ERROR=1 PREENY_DEBUG=1 LD_PRELOAD=x86_64-linux-gnu/desock.so /opt/abyssws/abyssws-x64
This is an output I receive:
Abyss Web Server X1 (v 2.12.1)
Copyright (C) Aprelium - 2001-2019
Error: to 507)
Error: from 0)
Error: 508
Error: 0
Error: fd 507
Error: 0
Error: 508
Error: to 1)
Error: RequestPowered by Abyss Web Server X1Copyright © Aprelium - 2001-2019+++ wrote 468 bytes to 1 (had read from 507)
+++ shutting down desock...
+++ ... shutdown complete!
Do you have any idea what could go wrong here? I would expect to see "Intercepted socket()!" among first output messages but here I'm getting errors right away.
Thanks a lot!

Hmm.. Those error messages are coming from abyss, so it's hard to say. Web servers can do some crazy things to mess with sockets, some of which might be interfering with preeny. It's hard to guess specifically what.
Some steps forward that come to mind:

Try desock_dup instead of desock. Depending on how the server is implemented, it might work.
Run abyss with ltrace and try to figure out what it does that makes it goes haywire with preeny. It'll be some socket operation that preeny doesn't intercept, probably.
I don't know what abyss does internally, but if it talks to itself over sockets (some things do this, though all that comes readily to mind are CTF challenges), it'll go completely crazy.

Hello Zardus,
thank you very much for fast reply!
I tried with desock_dup as well but unfortunately Abyss won't boot properly:
PREENY_INFO=1 PREENY_ERROR=1 PREENY_DEBUG=1 LD_PRELOAD=x86_64-linux-gnu/desock_dup.so /opt/abyssws/abyssws-x64
--- Disabling dup from 3 to 0
--- Disabling dup from 6 to 1
I guess you are right with point number 2 - probably some woodoo going on with sockets. I did reverse engineering on windows binary and I saw some odd stuff there :) So I might do some RE on linux binary and see if it is the same.
If I manage to come up with working solution I will update this issue to hopefully help others facing simillar issue.
Thanks a lot.


use forked sdk to make dev in windows working

It seems that Kirill has already merged the PR?

But it is not released to npm. We can switch back to npm release after it gets released.


Adding Grouped Single-Node Allocation Paradigm

Adding support for AllocationParadigm.GROUPED_SINGLE_NODE.  This represents associating all requested CPU and memory with a single ResourceAllocation object, which eventually translates to a single Docker container with all the CPU/memory.
This new paradigm is in contrast to the existing values - in particular  SINGLE_NODE - which allocate 1 CPU and identical fractions of memory to n ResourceAllocation objects (i.e., 1 CPU and similar portions of memory to each container), where n is the total number of requested CPUs.

@aaraney, that's the immediate motivation, but this will probably have more general use. There will also likely be "grouped" analogs for the two other existing values, again, for added flexibility (and perhaps greater efficiency) of execution.
I've no doubt we will want to expand and perhaps overhaul the design in the future. We will need to be careful how much control/responsibility we give to users though, and that we don't overwhelm those who are less interested in how the computation is distributed.

@hellkite500, you are correct on the original intent, but that was changed. Reintroducing something to represent that is why this is needed.
The change was largely, if not totally, to adhere to the Docker principle of one process per container (and thus the need for only one CPU).  This was done for all the existing paradigms.
How much we permanently support things that don't adhere to this principle will probably come down to external constraints and performance comparisons, but for now we want both (at least for the single-host case).

To be clear, this will indeed allocate multiple CPUs, and they will be all on the same physical host. But it will do so by creating a collection of ResourceAllocation objects, each requested to have 1 CPU. These will then directly correspond to the ngen worker containers started by the Launcher object within the scheduler service.

To be clear, this will indeed allocate multiple CPUs, and they will be all on the same physical host. But it will do so by creating a collection of ResourceAllocation objects, each requested to have 1 CPU. These will then directly correspond to the ngen worker containers started by the Launcher object within the scheduler service.

This is what I wasn't clear on.  The idea being multiple service containers can be used to serve a single job, and we ensure each of those containers is allocated 1 virtual CPU from our virtual resource pool, as opposed to a single job using a single container but using multiple virutal CPU's.

Sorry if I am kind of making a separate thread. I wasn't the most concise in my initial comment. What I didn't say, but was trying to convey, was that it seems like AllocationParadigm has blended imperative and declarative forms of allocation. For example,  the round robin scheduler specifies how to schedule work, but purposefully doesnt constrain where. In contrast, the grouped single node scheduler is constraining both how and where to schedule work. I think this might lead to a little confusion, like @hellkite500 has mentioned, and potentially lead to single and multinode versions of some paradigms like @robertbartel alluded to with this:

There will also likely be "grouped" analogs for the two other existing values, again, for added flexibility (and perhaps greater efficiency) of execution.

I *think* we can gain some nice characteristics if we are to further separate the declarative aspects of scheduling (what resources are requested; i.e. 1 node, 4 replicas, 1 vCPU per/replica) from the imperative aspects (which resources are allocated). By doing so, I think the majority of existing AllocationParadigms can be handled by a single AllocationParadigm. I still need to work through this more, but am I at least making more sense now?

For example, the round robin scheduler specifies how to schedule work, but purposefully doesn't constrain where. In contrast, the grouped single node scheduler is constraining both how and where to schedule work.

I don't agree.
Round robin does, in general, constrain where work is distributed:  everywhere.   It is the only one that does this, though.   For the others, what matters is the order in which nodes are examined - which does not depend on the paradigm (I think this is effectively random) - and how many compute assets (i.e., CPU and memory ***) remain on the "current" node.
All paradigms address how work is distributed.  Round robin is evenly, single node is all together or not at all, and fill nodes is as much together as possible.
So, I'm not sure if I follow exactly what you have in mind for the design.  But I do agree that there is plenty of room for enhancing this in the future.
*** We may want/need to have other types of compute assets in the future beyond CPU and memory, such as storage space or GPUs.  And when we do, that surely will have implications to how we need to address allocations.

@aaraney, @hellkite500, we seem to have lost track of this one as other things came up at the end of 2022. If my understanding of the functionality of ngen-cal is correct, we will need this change for the calibration job workflow. That workflow, in turn, will need more active development and testing in the near term.
Were there still outstanding questions or discussions on this that needed to be resolved?

Thanks for revitalizing this, @robertbartel. And for your discussion above.
Revisiting my prior comment:

Sorry if I am kind of making a separate thread. I wasn't the most concise in my initial comment. What I didn't say, but was trying to convey, was that it seems like AllocationParadigm has blended imperative and declarative forms of allocation. For example, the round robin scheduler specifies how to schedule work, but purposefully doesnt constrain where. In contrast, the grouped single node scheduler is constraining both how and where to schedule work. I think this might lead to a little confusion, like @hellkite500 has mentioned, and potentially lead to single and multinode versions of some paradigms like @robertbartel alluded to with this:

and @robertbartel's response, what I failed to say more plainly was, are the intent of some AllocationParadigm variants more clearly expressed by introducing compute assets n_tasks and / or n_nodes? I am not advocating for adding n_tasks and n_nodes to all AllocationParadigm variants, just variants' where the paradigm is more clearly captured with the inclusion of compute asset bounds, n_tasks and / or n_nodes. A good use case for this functionality is testing, debugging, and constrained deployment environments. I assume that exclusion of n_tasks and n_nodes thus far has been to purposefully abstract these concepts from the user and by doing so simplify the api. There may be cases in the future where we want the ability to further constrain the scheduler's scheduling bounds.

... are the intent of some AllocationParadigm variants more clearly expressed by introducing compute assets n_tasks and / or n_nodes?

No, I don't think so.  The paradigm selection should just be the general pattern for the scheduler to use to build the resource allocations, not detailed constraints.

I am not advocating for adding n_tasks and n_nodes to all AllocationParadigm variants, just variants' where the paradigm is more clearly captured with the inclusion of compute asset bounds, n_tasks and / or n_nodes

That lack of ubiquity is directly related to why those details belong somewhere else.

A good use case for this functionality is testing, debugging, and constrained deployment environments

I am interested in you elaborating on this, but I expect test cases would be more appropriately handled by just manually initializing resources pools in a test ResourceManager and/or ResourceAllocation objects.

I assume that exclusion of n_tasks and n_nodes thus far has been to purposefully abstract these concepts from the user and by doing so simplify the api.

Essentially, but it's important to be clear that, between making things easier for the user, and users not having fine-grained scheduling control, the latter is actually the higher priority here.

There may be cases in the future where we want the ability to further constrain the scheduler's scheduling bounds.

Again, DMOD itself can, but users should not be able to constrain the scheduler directly except for very limited exceptions that don't offer precise control.
It is useful and/or necessary to give some control levers to users, which we have:  options to communicate either a strict or loose requirement that all job processing be on one physical host, or to indicate all job processing resources are required to be within a single container instead of several.  Those are directly motivated by use cases of the software that gets executed in DMOD jobs.

Just to add to this a little further, I feel like I could be missing part of what @aaraney has been trying to describe here, and I want to make sure everything is clear before we consider this conversation finished.  However, I think we've gotten out of scope for this PR.
If I am also missing a reason why something being discussed should give us pause on adding these changes, let me know.  Otherwise, I suggest we separate the more detailed design discussion to a separate issue.

@robertbartel, thanks for guiding the conversation. I agree, I think my discussion points are a little out of scope and don't directly affect this PR. I may however open an issue to continue discussion of this.

Revisiting this, I think the point I failed to adequately convey is out of scope for this PR.
However, in general I think it would be beneficial to, in the future, add an intermediary GenericResourceAllocation or something similar. It appears that all of the current allocation paradigms could be generally described by the number of nodes, tasks, and amount of memory requested if the compute topology is known.
If this is true, it seems a generic scheduler could be written, such that, given a GenericResourceAllocation it returns one or more ResourceAllocations. So, an allocation paradigm would just return a GenericResourceAllocation that the resource allocation manager would turn into one or more ResourceAllocations. By doing this, we would centralize the resource allocation code into a single unit (this has nice traits if we needed to support non-docker resources in the future) and it would let us:

fail faster because we would know if we could fulfill a request before trying to fulfill it, - enable more informative error messages that dont necessarily need to be obfuscated,
and assist in debugging (i.e. reproducing a request on a system with different topology).


microsoft / WSL2-Linux-Kernel repo needs to be updated.

I updated to Windows 11 build 22538.rs_prerelease.220114-1500. My WSL2 kernel reports now version:
<IP_ADDRESS>-microsoft-standard-WSL2
However, the linux-msft-wsl-5.10.y branch at https://github.com/microsoft/WSL2-Linux-Kernel is still on version <IP_ADDRESS>
I use your source to build a custom kernel with aufs enabled. Your git repo needs to be updated so I can update my kernel to <IP_ADDRESS>

@dslater38 if you build your own kernel, grab the latest stable release from https://kernel.org. I'm running 5.16.0 w/out issues. Microsoft is not adding anything to the Linux kernel.

Microsoft is not adding anything to the Linux kernel.

That's not true.
DirectX for WSL2 and few features has not merged to main tree.
https://www.phoronix.com/scan.php?page=news_item&px=Microsoft-DXGKRNL-2022
https://github.com/torvalds/linux/tree/master/drivers/hv
https://github.com/microsoft/WSL2-Linux-Kernel/tree/linux-msft-wsl-5.10.y/drivers/hv
https://github.com/microsoft/WSL2-Linux-Kernel/blob/linux-msft-wsl-5.10.y/MSFT-Merge/log

https://github.com/microsoft/WSL2-Linux-Kernel/releases/tag/linux-msft-wsl-<IP_ADDRESS>


querydsl is abandoned. It's time to fork.

There are numerous posts about the status of querydsl. I dipped in from time to time as a contributor but full-time job/ life/ etc. meant I couldn't offer much. The project is now stagnant. In its current state, it is dead. We use it extensively in our codebase. querydsl is a great library. Let's move forward. My thoughts are in this SO post: https://stackoverflow.com/questions/55668960/whats-the-latest-status-of-querydsl/56029689#56029689
I propose that we use this issue to focus on a common fork. Who is in? I think querydsl-sql and querydsl-jpa would be a good start. Java version upgrade, dependency reduction, trim the fat.

Querydsl is awesome. I might be able to contribute (either in this repo or a fork).

Is anybody in contact wiht Timo? Getting him to appoint new maintainers would perhaps be better than forking.

querydsl is wonderful.  I would love to see this project actively developed, and I have been fighting urges to switch over to jOOQ in hopes this project is brought back to life.

Is anybody in contact wiht Timo? Getting him to appoint new maintainers would perhaps be better than forking.

@NiklasMehner I totally agree. I've emailed him with your suggestion. Hopefully, he gets back to us.

I've been in touch with Timo, he's happy to hand the project over. I'm going to close this and create a new issue stating that and see if we can get a team in place.


problem send data from database to user !!!!!!!!

Required Information

PHP version:
PHP Telegram Bot version:
Using MySQL database: yes
Update Method: Webhook
Self-signed certificate no
RAW update (if available):

Expected behaviour

Get all record (38) from databse and send to user.
Actual behaviour

Steps to reproduce

    public static function getansphoto(
        $callback_function,
        $chat_id
    ) {
        $callback_path = __NAMESPACE__ . '\Request';
        if (!method_exists($callback_path, $callback_function)) {
            throw new TelegramException('Method "' . $callback_function . '" not found in class Request.');
        }
         $dats  = array();

        $dats=DBAA::getbillphoto();
        $ccc=count($dats);                =======>>>>>>>>>>>>i have chek this and get true 38 record
        $results = [];
        $data['chat_id']=$chat_id;
        $t=urlencode('\n');
        $num=1;
        if (is_array($dats)) {
            foreach ($dats as $row) {
                $data['caption'] ='.'.PHP_EOL.$ccc.' - '.$rrr.' - '.$num++;
                // $data['caption'] ='.'.PHP_EOL.$row['txt'];
                $file=$row['file'];
                $results[]       = call_user_func_array($callback_path . '::' . $callback_function, [$data,$file]);
                $rrr=count($results);
            }
        }
// $results[]       = call_user_func_array($callback_path . '::' . $callback_function, [$data]);
        return $results;
    }

#####################################################################
in callbackquery .php
        case '051all':
                                $results = Request::getansphoto(
                'sendPhoto',
                $chat_id
            );
                         return $result;
                break;

#####################################################################
Extra details
My problem is get message first 16 record 2 time Continuous
1 - send 16 photo from 1 to 16
2-resend 16 photo from 1 to 16
**********   never send from 17 to 38

Are those getting send in very small intervals? If yes you're exceeding Telegram API limit.

thanks for your quick replay yes send in 16 photo in 20 seconds.
what can i do ?

@jacklul Shouldn't your request limiter be limiting submissions like that?

Yes, the limiter should prevent this from happening.
There might be undocumented limit that we are not aware of.

As I read somewhere some time ago there is not only a message limit of 30 messages per second, there is also a file size limit and a limit of sending images in a row. I actually don't know the correct limits. I think it was 5 images in a short period.

hi again and thanks for your response.
when i change $callback_function from sendPhoto to send message all things is fine .and bot send all(38) record.whats the problem with send photo and anybody have any idea how can i handle that win sendphoto function ???????!!!!!!!!!

@abbe-cipher Mind sharing your solution?

thanks .my problem was in my db.in 17th record to get photo address its was null.


Bazel - IntelliJ Sync issue

Description of the issue. Please be specific.
What's the simplest set of steps to reproduce this issue? Please provide an example project, if possible.
Version information
IdeaCommunity: 2019.2.4
Platform: Mac OS X 10.13.6
Bazel plugin: 2<IP_ADDRESS>.0
Bazel: 1.2.1

I'll close the issue. If you still can reproduce it, please reopen.


Social media meta not pulling through

@saeedmb8 please review
Remove og:url and tested; scraper gets the website URL and website image.
Issue is article meta doesn't get pulled through.

👍


Use lerna independent versioning

Before we release this repo as 1.0, we need to ensure we can hold the metrics packages back as 0.x. We also need processes in place for backporting bug fixes to older minor versions after we reach 1.0.
This should include tooling for automatic release management as well as updating the contributing.md

I think this issue can be closed as this was already done in #2431 which replaced #2393


Does it support multi key polling？

Confirm this is a feature request for the Python library and not the underlying OpenAI API.

[X] This is a feature request for the Python library

Describe the feature or improvement you're requesting
Does it support multi key polling？
Additional context
Does it support multi key polling？

Not currently, no. Can you share more about what you would like to see and why?
Is there any reason that calling .poll(id) in a for-loop would not work well for you?

I think this should be closed right?


wait for profile comp transaction to broadcast before signing and submitting UpdateProfile transaction

Was merged via z/updated-onboarding branch


Replacing all references to VS 17 with VS 19

Docs Build status updates of commit a30f15d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/docfx.json
:white_check_mark:Succeeded

articles/install-guide/index.md
:white_check_mark:Succeeded
View (qsharp-preview)

articles/install-guide/vs-2017.md
:white_check_mark:Succeeded
View (qsharp-preview)

articles/libraries/chemistry/installation.md
:white_check_mark:Succeeded
View (qsharp-preview)

articles/libraries/numerics/installation.md
:white_check_mark:Succeeded
View (qsharp-preview)

articles/quickstart.md
:white_check_mark:Succeeded
View (qsharp-preview)

articles/relnotes/index.md
:white_check_mark:Succeeded
View (qsharp-preview)

articles/techniques/testing-and-debugging.md
:white_check_mark:Succeeded
View (qsharp-preview)

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

Docs Build status updates of commit ba0512f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/install-guide/index.md
:white_check_mark:Succeeded
View (qsharp-preview)

articles/install-guide/vs-2017.md
:white_check_mark:Succeeded
View (qsharp-preview)

articles/libraries/chemistry/installation.md
:white_check_mark:Succeeded
View (qsharp-preview)

articles/libraries/numerics/installation.md
:white_check_mark:Succeeded
View (qsharp-preview)

articles/quickstart.md
:white_check_mark:Succeeded
View (qsharp-preview)

articles/relnotes/index.md
:white_check_mark:Succeeded
View (qsharp-preview)

articles/techniques/testing-and-debugging.md
:white_check_mark:Succeeded
View (qsharp-preview)

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


remove 'CSharp` option from windows installer.

Describe the bug
Gauge windows installer shows 'CSharp' as a plugin to be installed in the wizard. C# plugin is deprecated and can be removed.

Fixed with https://github.com/getgauge/gauge/pull/1763


Please move the deprecation notice, it makes builds fail.

Triggering the error makes development builds fail.  If you must trigger an error, you are triggering this error not because someone is actually using the deprecated extension, but because they are loading in your polyfill.
As stated:  This library attempts to create a drop-in replacement for ext/mysql on PHP 7 using mysqli.
But throwing an error is not what happens if you install the mysql extension from PECL.
Worse, this triggers an error when someone isn't doing anything wrong.  If you must include this error, then move it to the connect section so it doesn't throw the error until after the person has attempted to use the plugin.
    trigger_error(
        "php7-mysql-shim: The mysql extension is deprecated "
        . "and was removed in the PHP 7.0: use mysqli or PDO instead.",
        E_USER_DEPRECATED
    );

Can you elaborate on builds failing? Yours? All of this projects builds pass (although the deprecation notice is shown in the output).
I wasn't entirely happy about adding this, I initially added it to every function but that completely breaks all the tests (converted to exception by PHPUnit and that breaks the test).
Just looking for more insight before I remove it.

I think it should only be added to the mysql_connect function.  There's no point throwing an error every time a user uses a deprecated function, I think once per connection is enough.
I checked my commit against the PHPUnit tests and it worked.  It's going through your automated tests right now.
The error it throws is a custom one because I convert all errors to exceptions in my code.  It reads as follows:
PHP Deprecated:  php7-mysql-shim: The mysql extension is deprecated and was removed in the PHP 7.0: use mysqli or PDO instead. in /Users/michaelsoileau/Sites/cellcontrolDocs/vendor/dshafik/php7-mysql-shim/lib/mysql.php on line 31

@NoMan2000 I'm inclined to just remove it entirely, as you see in your PR (#25) it causes all tests to fail due to the way PHPUnit handles things.

That's cool too.  I just wasn't sure if you wanted it to remain for a reason.  If not, feel free to remove it.  👍

Done in f5b1bc9. Thanks!


Refactoring code - Iteration 1

No need to send a PR for this one.  You can do your refactors for the next iterations after the PRs have been reviewed.


Various fixes

Fix bug where you cannot log in if your username is over 32 characters (possible when site.username_max_length is changed)
Fix for attributes on the user preferences template so the labels are labelling the correct element
Fix adding admin user instructions in readme (python3 scripts/admins.py --add → ./thoat.py admin add)
Make the Make docker-npm recipe a .PHONY target

Let me know if I should split this into multiple PRs.

good stuff


Add cosign v2.2.3

fixes #535
In addition I think older releases of cosign that depend on the TUF repository should be removed cc: @haydentherapper

So, this can be generated by running this script on cosign_checksums.txt
grep -v -e apk -e deb -e piv -e rpm -e sbom -e exe -e riskv64 $1 | while read line
do
  parts=($line)
  base64="sha25-`echo ${parts[0]} | xxd -p -r | base64`"
  arch=${parts[1]/#cosign-}
  echo "\"$arch\": \"$base64\""
done

Perhaps this script or something like it can be placed in the repo somewhere? (suggestions?)

If you need any old versions still, v1.13.6 also works.

We have automation for version mirroring in most of our repos now. LMK if you get time to add it

We have automation for version mirroring in most of our repos now. LMK if you get time to add it
for cosign?

The test failure in here seems like a fundamental bazel config issue?


[SOFT-435] Setup CI/CD

Opened PR for final debugging of CI

Hmm ideally I would like the dbc file not to be included with the repository. However, since this will cause the test to fail we leave it in for now.


ci add required checks for branch-2.1

Add required checks for branch-2.1.
After this PR, all checks need to be passed before merging PRs to branch-2.1

run buildall


Chapter 4 auction sample

file tsconfig.json:
"target": "ES5" should be "target": "ES6" ??
as find() method not supported in ES5

ES5 is fine - we installed es6-shim  and @types/es6-shim, for supporting find().


Customize Freecam notifications

Feature request: Be able to customize the "Freecam has been enabled" and "Freecam has been disabled" messages. Could be fun.

Do you have a use-case for this? Or a reason why some may dislike the default text?

I don't see a reason to add this. It would clutter the config screen without much benefit to the user.


Add gcc7 to the Travis lineup, fix warnings, etc.

Includes some general cleanup of the .travis.yml file.

LGTM


Automate the selection of sizes, with an option like --auto-size

Automate the selection of sizes, by default:

dpi
b
r

see README table

pick closest known size (distance = dx^2 + dy^2)

model the sizes and settings in a CSV file

on by default

with other options:

disable with -dpi
allow override by -b -r

done


Sites using scss-lint, things people have written about scss-lint

It would be nice to have a list like this compiled for this project. Perhaps this could be added to the readme.
Some inspiration:

http://babeljs.io/users/
http://eslint.org/ (under "Who's using ESLint?")
https://github.com/rackt/react-router/issues/2412
https://github.com/facebook/react/wiki/Sites-Using-React

One potential source: https://libraries.io/rubygems/scss_lint/dependent-repositories


Create updated example app and deprecate Ferret

As somebody that's used Ferret as a reference I'd like to know why it's going to be deprecated. Anything wrong with it?

Patterns need to be updated. Ferret is temporally deprecated while we work on updating the app with the new stuff we are working on.
We will keep the name but upload an updated example that is closer to this: http://hc380.grommet.io

Looking good, I'll look out for the update then.

Ferret has been updated


Documentation issue for urls.py

In the faq section under
http://mezzanine.jupo.org/docs/frequently-asked-questions.html#why-isn-t-the-homepage-a-page-object-i-can-edit-via-the-admin
The documentation points to https://github.com/stephenmcd/mezzanine/tree/master/mezzanine/project_template/urls.py
which gives a 404
I assume this should now be https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/project_template/project_name/urls.py
But it may need rewriting since there's been changes.
Thanks.

It's fixed in master. See #1571.


[release/3.1] Update to August 2020 3.1.107 release (3.1.7)

https://github.com/dotnet/core/blob/master/release-notes/3.1/3.1.7/3.1.7.md

OSX smoke-test failure is https://github.com/dotnet/source-build/issues/1685


Disable IMAP Email Service Code base from Marshal's

Title of ticket:
Description
This ticket is to disable all code flow related with IMAP / or reading emails from inbox, since we were unable to find the IMAP service from ICIO or using summer.gov.bc.ca IMAP is not working. So , team decided to disable the code related with IMAP/reading emails for failure etc.
Dependencies
Are there any dependencies?
DOD

[ ] Make sure all IMAP related code bases are disabled / commented- NOT REMOVED
[ ] confirm the functionality, clarify gaps if any.
[ ]
[ ]
[ ]

For Testing/QA Purposes - Test failure scenarios to confirm they aren't being added to attachments
and Happy path fee payment email scenarios - wait for email (GOV) change to test this to avoid duplication.

All good - failure scenarios aren't being written and new email appears to be working as expected.


Date bug fixed

Description
Fixes #436
Type of change
Just put an x in the [] which are valid.

[x] Bug fix (non-breaking change which fixes an issue)

Hey @Swati4star, check if bug is fixed

Awesome @anirudh8860 ! Good job on finding out & fixing this bug 👍


Extension to single image input

Thanks for the work and code release. I’m wondering if this work could be extended to single image input, similar to Dust3r?

Me too!

Hi, thank you for your insightful question. Our method is not specifically designed for this case. Unlike DUSt3R, which is trained with ground truth depth, enabling easier adaptation to single-image scenarios, NoPoSplat relies solely on photometric loss by rendering intermediate frames between two input frames. Consequently, our method may not perform optimally for single-image cases. However, you are welcome to try it, and we plan to investigate this issue further. There may be some useful ways to improve the quality of a single input, such as using two identical views of the input during training or adding additional depth supervision during training.


[Flowbroker] Correct the text in switch node

Steps to reproduce the problem:

Click "Novo Fluxo"
Edit switch node

Affected Version: 58.2-20190321

Test OK.

Tested on Version: 62.3-20190603


Prototype HarnessU

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the CODEOWNERS.
What Type of PR is This?

[ ] Issue
[x] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[x] Tested Locally
[x] Optional Screenshot.

Missed a period, re-committed

No need to review as this is being closed.


Updating increase limits with new portal information

@mimig1

@AndrewHoh - Can you submit this to azure-content-pr instead so we can see it on staging first? With so many changes, I think that's a safer bet.

@AndrewHoh please close this if it went through azure-content-pr instead. thx.


Update docs to be more like a regular local crates.io setup

@bors: r+

:pushpin: Commit c9a367c3e8ad06a8054aebf08c29b072bfe85dfe has been approved by alexcrichton

:hourglass: Testing commit c9a367c3e8ad06a8054aebf08c29b072bfe85dfe with merge d5842b46a12ca95339a91db19a10a2533daaba1b...

:broken_heart: Test failed - status-travis

@alexcrichton looks like the osx build timed out

@bors: retry
Indeed!

:hourglass: Testing commit c9a367c3e8ad06a8054aebf08c29b072bfe85dfe with merge c0ed157aaccf2bd66b2f7a638079f832bfd4fcbf...

:broken_heart: Test failed - status-travis

@bors: retry

:hourglass: Testing commit c9a367c3e8ad06a8054aebf08c29b072bfe85dfe with merge 1fa30882067703202d13ad0bd53d630bc2c1de66...

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing 1fa30882067703202d13ad0bd53d630bc2c1de66 to master...