Latest release 1.6.1 breaks compatibility with 1.6.0 when parsing python/str

Latest release 1.6.1 breaks compatibility with 1.6.0 when parsing python/str.
Example schema (schema_file.yml):
allowempty: True
mapping:
  intents:
    type: !!python/str "seq"
    sequence:
    - type: !!python/str "str"

source file (source.yml):
# all hashtags are comments :)
intents:
 - greet
 - default
 - goodbye

Code:
from pykwalify.core import Core
c = Core(source_file="source.yml", schema_files=["schema_file.yml"])

works just fine in 1.6.0 but is broken in 1.6.1 (python 2.7). Exception:
/Users/tmbo/.virtualenvs/rasa/lib/python2.7/site-packages/pykwalify/core.pyc in __init__(self, source_file, schema_files, source_data, schema_data, extensions, strict_rule_validation, fix_ruby_style_regex, allow_assertions)
     88                         data = json.load(stream)
     89                     elif f.endswith(".yaml") or f.endswith(".yml"):
---> 90                         data = yaml.safe_load(stream)
     91                         if not data:
     92                             raise CoreError(u"No data loaded from file : {0}".format(f))

/usr/local/Cellar/python/2.7.14_3/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/ruamel/yaml/main.pyc in safe_load(stream, version)
    666     Resolve only basic YAML tags.
    667     """
--> 668     return load(stream, SafeLoader, version)
    669
    670

/usr/local/Cellar/python/2.7.14_3/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/ruamel/yaml/main.pyc in load(stream, Loader, version, preserve_quotes)
    637     loader = Loader(stream, version, preserve_quotes=preserve_quotes)
    638     try:
--> 639         return loader._constructor.get_single_data()  # type: ignore
    640     finally:
    641         loader._parser.dispose()  # type: ignore

/usr/local/Cellar/python/2.7.14_3/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/ruamel/yaml/constructor.pyc in get_single_data(self)
    102         node = self.composer.get_single_node()
    103         if node is not None:
--> 104             return self.construct_document(node)
    105         return None
    106

/usr/local/Cellar/python/2.7.14_3/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/ruamel/yaml/constructor.pyc in construct_document(self, node)
    112             self.state_generators = []
    113             for generator in state_generators:
--> 114                 for dummy in generator:
    115                     pass
    116         self.constructed_objects = {}

/usr/local/Cellar/python/2.7.14_3/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/ruamel/yaml/constructor.pyc in construct_yaml_map(self, node)
    609         data = {}  # type: Dict[Any, Any]
    610         yield data
--> 611         value = self.construct_mapping(node)
    612         data.update(value)
    613

/usr/local/Cellar/python/2.7.14_3/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/ruamel/yaml/constructor.pyc in construct_mapping(self, node, deep)
    354         if isinstance(node, MappingNode):
    355             self.flatten_mapping(node)
--> 356         return BaseConstructor.construct_mapping(self, node, deep=deep)
    357
    358     def construct_yaml_null(self, node):

/usr/local/Cellar/python/2.7.14_3/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/ruamel/yaml/constructor.pyc in construct_mapping(self, node, deep)
    234                             "found unhashable key", key_node.start_mark)
    235
--> 236                 value = self.construct_object(value_node, deep=deep)
    237                 if check:
    238                     self.check_mapping_key(node, key_node, mapping, key, value)

/usr/local/Cellar/python/2.7.14_3/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/ruamel/yaml/constructor.pyc in construct_object(self, node, deep)
    157                     constructor = self.__class__.construct_mapping   # type: ignore
    158         if tag_suffix is None:
--> 159             data = constructor(self, node)
    160         else:
    161             data = constructor(self, tag_suffix, node)

/usr/local/Cellar/python/2.7.14_3/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/ruamel/yaml/constructor.pyc in construct_undefined(self, node)
    629             "could not determine a constructor for the tag %r" %
    630             utf8(node.tag),
--> 631             node.start_mark)
    632
    633

ConstructorError: could not determine a constructor for the tag 'tag:yaml.org,2002:python/str'
  in "/Users/tmbo/lastmile/bot-ai/rasa_core/rasa_core/schemas/domain.yml", line 4, column 11

Thanks for the report, will try to reproduce. What version of ruamel.yaml are you using?

The only change i know that i have done realted to this is the following change in my setup.py
-        'ruamel': ["ruamel.yaml>=0.11.0,<0.12.0"],
+        'ruamel': ["ruamel.yaml>=0.11.0,<0.16.0"],

So my guess is that you are getting a newer version of ruamel.yaml lib that possibly has a problem. If you can verify then i would suggest that you search in ruamel.yaml what they have changed between the 2 versions.

Not sure, but also might be related of your change to use load_safe instead of load

I just double checked, everything is the same, including ruamel.yaml==0.15.35. So the only package that I changed in my local test just now is this one.
I've added a source file to the above as well as I noticed you can't create the Core instance without one.

Interesting.. I probably have to do additional refactoring of the yaml client to provide user support for this type of use-case.I guess i also have to consider the case where the end-user either want tot send in their own yaml parser instance, or be able to modify the supported tags. By default the basic python tags could be added, but i think i need this extend ability also.

@tmbo This commit 68405edd89bcf6ec16c76169884e89662db4fc47 that will be in 1.7.1 will fix this issue. Even a test added for it now so it can be detected again in the future if this feature is changed/dropped again.

perfect - will update and unpin the dependency. do you know when you'll tag the 1.7.1 release?

@tmbo I will need to see if i need to get in the include argument or not, if not then it should be within this week.


Study using non-linear proof of stake rewards with pool balance

We want to try to disincentivize accumulation of coins in one pool.

Implemented in #1170


Activate on more specific debug events

Motivation
Activation is currently quite heavyweight due to the download of both the language server and a debug adapter. Making this more lightweight (e.g. by not awaiting the download in the activate function) would be nice too, but something to explore in a future issue.
Proposal
Instead of onDebug, listen to more specific debug activation events.

Fixed as of 0.2.18


QMainWindow UI: Support rounding the edges of the window.

Already included in the main repository - commit ( bf815beb4d83abccfa283d1c58b731c904119ca2


[serverless-next.js component] new service after every update ?

Hi;
I try to deploy using serverless-next.js component via gitlab-ci. everything is perfect, zero config is a magic :)
But there is something i don't understanding.
I push the app to the develop branch and it deployed to aws via Gitlab CI.
when I make a change to the app and push it again to develop branch, i expect to update for existing s3bucket, lambda and cloudfront services. but instead of updating it is creating a new one.
I need your idea on how I need to follow a path to correct this situation.
thanks.
# .gitlab-ci.yml

image: node:latest
stages:
  - deploy
serverless:
  stage: deploy
  only:
    - develop
  script:
    - npm install
    - npm install serverless-next.js --save-dev
    - npm install -g serverless
    - serverless

# serverless.yml
website:
  component: serverless-next.js
package:
  exclude:
    - ./**

Regarding this issue, I'm just deploying with serverless command and it's creating a new service each time. Is there a way to avoid that?

@cristiam86 This is a common problem. In the README, Daniel says to include the .serverless folder in your git repo.
On a technical note, it is because serverless components allow one to save state, however all state is saved locally. Until they make a plan to save that state somewhere in the cloud and bring it into the build process, we are forced to include the state (i.e. the .serverless folder) into our git repo.

thanks @barrysteyn but I have already included the .serverless folder into the repo. In fact I'm the only one making changes a deploying it.

Yes, but the thing is that your state has probably changed (I’m guessing
you have added resources or just removed your current setup and then put it
up again). So do this: delete your state files (.serverless), then deploy
again and then recommit the .serverless folder
On Tue, Nov 19, 2019 at 9:11 PM Cristiam Da Silva<EMAIL_ADDRESS>wrote:

thanks @barrysteyn https://github.com/barrysteyn but I have already
included the .serverless folder into the repo. In fact I'm the only one
making changes a deploying it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/danielcondemarin/serverless-next.js/issues/147?email_source=notifications&email_token=AALXKRGLAW6LXUZA5NBKPIDQUTBH7A5CNFSM4IYLABMKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEQXK4Q#issuecomment-555840882,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AALXKRGA3CHZ6GYKLCWFUETQUTBH7ANCNFSM4IYLABMA
.

--
Barry Steyn
Blog http://doctrina.org LinkedIn http://ca.linkedin.com/in/barrysteyn
GitHub https://github.com/barrysteyn

Thank you @barrysteyn, that worked!

Thank you @barrysteyn, that worked!

Not a problem. This is a problem with the way serverless components are implemented now, however I believe that this issue will be solved kinda soon.


Create /config command

Resolves #15
Adds a new command that allows the user to control configuration files within the game.
Supports reloading + editing.

@gtaEPIC if you could review this when you get the chance it would be really appreciated!
Feel free to lmk if you can't/don't want to review the PR and I can do a self-review


Dock Icon Treatment is Inconsistent

I noticed that the outlines on the icons in the dock are inconsistently treated. It’s minor, but I noticed it right away. It looks like the outlines used for the Dashboard and Turnip icons are consistent (brown), but catalogue and collection are different (Catalogue is dark grey and Collection is dark blue). Then Villagers doesn’t have an outline at all.
That’s it!

We didn’t created the icons. They were provided from other sources. We aren’t able to modify each icon so they will fit together, but we will have an eye on this so we may find a better source for icons that are consistent.


test to check gates report

Please provide a paragraph or two giving a summary of the change, including relevant motivation and context.
Checklist:
Remove the checklist to signal you've completed it. Enable auto-merge if the PR is ready to merge.

[ ] If the pull request requires a cryptography review (e.g. cryptographic algorithm implementations) I have added the 'crypto' tag.
[ ] I have reviewed my diff in github, line by line and removed unexpected formatting changes, testing logs, or commented-out code.
[ ] Every change is related to the PR description.
[ ] I have linked this pull request to relevant issues (if any exist).

Benchmark results
No metrics with a significant change found.

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit a60b71a5 and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
128 txs

l1_rollup_calldata_size_in_bytes
45,444
179,588
716,132

l1_rollup_calldata_gas
222,996
868,172
3,447,884

l1_rollup_execution_gas
842,083
3,595,280
22,203,546

l2_block_processing_time_in_ms
1,327 (-1%)
5,248 (+3%)
21,105

note_successful_decrypting_time_in_ms
338 (-1%)
1,063 (-4%)
3,906 (+2%)

note_trial_decrypting_time_in_ms
48.9 (-8%)
40.8 (+9%)
143 (+4%)

l2_block_building_time_in_ms
14,253 (+5%)
56,192 (+4%)
226,947 (+4%)

l2_block_rollup_simulation_time_in_ms
10,530 (+5%)
41,429 (+4%)
168,440 (+5%)

l2_block_public_tx_process_time_in_ms
3,691 (+5%)
14,691 (+5%)
58,274 (+4%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
15,491 (-4%)
29,829 (+2%)

note_history_successful_decrypting_time_in_ms
2,486 (-2%)
5,075

note_history_trial_decrypting_time_in_ms
91.9 (+8%)
145 (+4%)

node_database_size_in_bytes
3,917,227
4,259,044

pxe_database_size_in_bytes
29,940
59,499

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
204 (+2%)
43,109
20,441

private-kernel-ordering
116 (+1%)
25,833
9,689

base-rollup
2,125 (+3%)
244,144
881

root-rollup
66.1 (-25%)
4,088
889

private-kernel-inner
267 (+3%)
64,516
20,441

public-kernel-private-input
176 (+2%)
25,203
20,441

public-kernel-non-first-iteration
175 (+2%)
25,245
20,441

merge-rollup
11.4
2,608
881

Miscellaneous
Transaction sizes based on how many contracts are deployed in the tx.

Metric
0 deployed contracts
1 deployed contracts

tx_size_in_bytes
10,323
26,359


RI scenario misleading ports

When retrieving the connection, I see the path:
node1/pe113 à node1/pe11 à node4/pe42 à node4/pe41 à node2/pe22 à node2/pe213
I guess that node1/pe113 and node2/pe213 are the client ports that are connected to the UNI ports on the routers.
But when querying about these ports, I see that "layerProtocolName": "OCH" when I would expect to have "layerProtocolName": "ETH", for both.

I don't know if this will bring some multi-layer issues into the scenario.


Securely Store Location Data + Other improvements

Securely store locations in encrypted Realm db

This PR securely stores all captured Geolocation coordinates in an encrypted Realm database.

Secures Locations imported via Google
Migrates old locations to new secure storage -> deletes old on success
Still allows for json export
Fixes bug where locations stopped being captured after device restart

Linked issues:
#527
Fixes https://github.com/safe-paths-contrib/covid-safe-paths/issues/29
How to test
For debug builds, you can download the Realm database inside the apps storage. You can open the database using Realm Studio: https://realm.io/products/realm-studio/. Because the database is encrypted, you will need to log a hex-encoded encryption key.

@tstirrat @kenpugsley Can you assign yourselves as reviewers?

Encryption review is pending. Lets hold off on merging until we get an approval.

Great work!

This is wonderful stuff @troach-sf .

@tstirrat, I've completed testing on both sides. Looks like there is 1 conflicting file that needs to be resolved now. I'll merge that in tomorrow morning.

Thanks! How does one run the native tests?
It would be good to encode that into 2 more jobs in the test.yml workflow.. /cc @efalkner

I just wrote a document on how to manually capture encryption key for develop builds to allow for opening the database. This should help for manual tests. https://gist.github.com/troach-sf/f257bb7b80e6dddd4f3bade81b7b1410
For running the automatic tests.
Android:
cd android
../gradlew clean
../gradlew connectedAndroidTest

iOS:
Haven't tried from the command line but open the project, open the CovidSafePathsTests scheme, and click on the test icon in the sidebar and run all tests in RealmSecureStorageTest

Right now Android requires a device/emulator. I don't think Realm is compatible with Robolectric for unit testing without a device. That may make it tricky to get working on GH Actions.

Note to others ... I'm currently working on doing some functional testing on this, and will try to run new native tests locally.

cd android
../gradlew clean
../gradlew connectedAndroidTest

This doesn't work for me.  It's failing in the geolocation tests ... any ideas?
> Task :@mauron85_react-native-background-geolocation:connectedDebugAndroidTest 12:47:08 V/ddms: execute: running am get-config 12:47:09 V/ddms: execute 'am get-config' on 'emulator-5554' : EOF hit. Read: -1 12:47:09 V/ddms: execute: returning 12:47:09<EMAIL_ADDRESS>Uploading @mauron85_react-native-background-geolocation-debug-androidTest.apk onto device 'emulator-5554' 12:47:09 D/Device: Uploading file onto device 'emulator-5554' 12:47:09 D/ddms: Reading file permision of /Users/ken/code/covid-safe-paths/node_modules/<EMAIL_ADDRESS>as: rw-r--r-- 12:47:09 V/ddms: execute: running pm install -r -t<EMAIL_ADDRESS>12:47:12 V/ddms: execute 'pm install -r -t<EMAIL_ADDRESS>on 'emulator-5554' : EOF hit. Read: -1 12:47:12 V/ddms: execute: returning 12:47:12 V/ddms: execute: running rm<EMAIL_ADDRESS>12:47:13 V/ddms: execute 'rm<EMAIL_ADDRESS>on 'emulator-5554' : EOF hit. Read: -1 12:47:13 V/ddms: execute: returning 12:47:13 I/RemoteAndroidTest: Running am instrument -w -r   com.marianhello.bgloc.react.test/android.support.test.runner.AndroidJUnitRunner on Nexus_4_API_27(AVD) - 8.1.0 12:47:13 V/ddms: execute: running am instrument -w -r   com.marianhello.bgloc.react.test/android.support.test.runner.AndroidJUnitRunner 12:47:13 V/InstrumentationResultParser: INSTRUMENTATION_RESULT: shortMsg=Process crashed. 12:47:13 I/InstrumentationResultParser: test run failed: 'Instrumentation run failed due to 'Process crashed.''

@kenpugsley ah sorry, run :app:androidConnectedTest to limit to just our own tests. Good eye on the backfill. I discussed this with @Ferrumofomega and @tremblerz that we would only store real locations in the db. It would be easy enough to add backfilling in on the js layer when pulling locations. After discussing that a bit, I believe we came to an agreement that if there is a delay we shouldn't make assumptions someone stayed in one spot if the previous location had barely changed. I'll leave that up to you all to decide, but if we add it back in, rather than throwing assumed locations in the db, we should only add during processing.

we should only add during processing.

I see the point on the intersection, but this also have effects on the flow of data to safe paths.  I see the point about not wanting location data that is inferred stored, but this will be a breaking change to the "contract" (not that there is one explicitly) with safe places.  If we don't store the points in the local db, then in both the intersection as well as the data export we have to remember to backfill the gaps.  Seems like a service layer thing to me.

Closing this in favor of #788 where we are automating tests and merging conflicts.

I just wrote a document on how to manually capture encryption key for develop builds to allow for opening the database. This should help for manual tests. https://gist.github.com/troach-sf/f257bb7b80e6dddd4f3bade81b7b1410

I'm getting compilation errors (Android) when I add this immediately after SecureRandom().nextBytes(newKey) in getEncryptionKey()

@AdamLeonSmith, I have updated the gist. There was a missing ")".


Organize apps by folders

Describe the solution you'd like
As developers in a big organization, we would like to be able to organize applications in folders.
Describe alternatives you've considered
We are currently "sorting" by adding prefixes but it doesn't solve our problem.
Additional context
None

Bad bot, good idea


[Vite] Error: You must render this element inside a <Remix> element when running dev server for the first time with default client entry

What version of Remix are you using?
0.0.0-nightly-3874120-20231103
Are all your remix dependencies & dev-dependencies using the same version?

[X] Yes

Steps to Reproduce
(EDIT: It seems this is not limited to pnpm. It's reproducible with npm as well. See 2nd comment for details)
(tldr; adding @remix-run/react to optimizeDeps.include might fix this issue.)
I was trying to reproduce https://github.com/remix-run/remix/issues/7863 on CI, but it turns out this error always happens on clean installation.

Reproduction repo https://github.com/hi-ogawa/test-remix-vite-hmr-runtime
CI failure https://github.com/hi-ogawa/test-remix-vite-hmr-runtime/actions/runs/6761390975/job/18376217210#step:7:22

Locally, I was seeing the same error several times, but after restarting the dev server, the error always went away (note that browser reload alone doesn't fix this).
Investigating further, I found that this is reproducible after rm -rf node_modules && pnpm i && pnpm dev.
And I also found that same could be reproducible by effectively disabling dependency pre-bundling by vite dev --force (cf. https://vitejs.dev/guide/dep-pre-bundling.html).
Here is a screenshot of the error with js code of default client.entry.tsx on the right top:
Reveal screenshot

As partially seen from the screenshot, it seems that when default client entry inside node_modules/@remix-run/dev on pnpm is used, import { RemixBrowser } from "@remix-run/react" is transformed to the following:
// request url
// http://localhost:5173/node_modules/.pnpm/@remix-run+dev@0.0.0-nightly-3874120-20231103_@remix-run+serve<EMAIL_ADDRESS>...
import {RemixBrowser} from "/node_modules/.pnpm/@remix-run+react@0.0.0-nightly-3874120-20231103_react-dom@18.2.0_react@18.2.0_typescript@5.2.2/node_modules/@remix-run/react/dist/esm/index.js?v=1ecd547c";

However, comparing with user routes which also use @rexmi-run/react module, it looks like this:
// http://localhost:5173/app/root.tsx
...
import {Links, LiveReload, Meta, Outlet, Scripts, ScrollRestoration} from "/@id/__x00__virtual:remix-react-proxy";
...

// http://localhost:5173/@id/__x00__virtual:remix-react-proxy
export * from "/node_modules/.vite/deps/@remix-run_react.js?v=864763a5";
...

So, probably having a different import source is leading to some sort of "dual package hazard".
Note that, after the server restart (without --force), the error goes away and the same import looks like this:
// http://localhost:5173/node_modules/.pnpm/@remix-run+dev@0.0.0-nightly-3874120-20231103_@remix-run+serve<EMAIL_ADDRESS>import {RemixBrowser} from "/node_modules/.vite/deps/@remix-run_react.js?v=6e4b22d3";

// http://localhost:5173/@id/__x00__virtual:remix-react-proxy
export * from "/node_modules/.vite/deps/@remix-run_react.js?v=6e4b22d3";
...

After seeing this, it came naturally to try adding @remix-run/react to optimizedDeps.include, and indeed this seems to fix the issue, i.e. no error even with vite dev --force.
import { unstable_vitePlugin as remix } from "@remix-run/dev";
import { defineConfig } from "vite";
import tsconfigPaths from "vite-tsconfig-paths";

export default defineConfig({
  clearScreen: false,
  plugins: [remix(), tsconfigPaths()],
  optimizeDeps: {
    include: ["@remix-run/react"],              ///  <-- add @remix-run/react to optimized deps
  },
});

You can see this error is fixed error on reproduction repo https://github.com/hi-ogawa/test-remix-vite-hmr-runtime/pull/1 but now CI shows error from @vitejs/plugin-react can't detect preamble https://github.com/remix-run/remix/issues/7863.

https://github.com/hi-ogawa/test-remix-vite-hmr-runtime/actions/runs/6761736191/job/18376925487?pr=1#step:7:35

Right now, I don't fully understand the consequence of doing optimizeDeps, so I'm creating this issue first before trying to create a PR. I would appreciate if anyone has insight on this.
Expected Behavior
No error for first vite dev
Actual Behavior
Errro as described in "Steps to Reproduce"

It seems the same error is reproducible with npm as well.
By doing similar debugging as above, I see these imports when running vite dev --force:
// in<EMAIL_ADDRESS>import {RemixBrowser} from "/node_modules/@remix-run/react/dist/esm/index.js?v=17a387ed";
...

// in http://localhost:5173/@id/__x00__virtual:remix-react-proxy
export * from "/node_modules/.vite/deps/@remix-run_react.js?v=d10a7b92";
...

This is fixed by https://github.com/remix-run/remix/pull/7926 which will be available in the next release. If you'd like, you can confirm against the latest nightly release.


Check renderer

Pull request information

Status: ? (ready to merge / in development)

Kind of changes: ? (bug fix / new feature / documentation...)

Change file in the flow.envs.base to create pyglet rendering.

There was a bug I guess which didn't start the pyglet rendering where the should_render was preventing it from rendering.

Related PR or issue: ? (optional)

Description

? (general description)

Sorry, I am new and I couldn't figure out another way to use the rendered
images to train a CNN network. Therefore I was thinking of something like
this. Also in line 436  self.sim_params.render = True,Sets to true which
prevents it from rendering pyglet. Am I doing something wrong here?
Gaurav Bagwe,
PhD Student,
Michigan Tech,
9062759939
On Thu, May 5, 2022 at 12:37 PM Eugene Vinitsky @.***>
wrote:

@.**** commented on this pull request.
In flow/envs/base.py
https://github.com/flow-project/flow/pull/1063#discussion_r866111117:

@@ -133,7 +133,7 @@ def init(self,
self.sim_params = deepcopy(sim_params)
# check whether we should be rendering
self.should_render = self.sim_params.render

   self.sim_params.render = False

   self.sim_params.render = self.sim_params.render

this seems unnecessary?
—
Reply to this email directly, view it on GitHub
https://github.com/flow-project/flow/pull/1063#pullrequestreview-963663894,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKEHHSQQLJV5KRQLD73V6CTVIP2OJANCNFSM5VFSN2QQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Oh no worries and thank you for the PR!


Don't read allure.properties

I try add allure.issues.tracker.pattern and allure.tests.management.pattern to allure.properties, but the property doesn't read. Can you investigate this issue please?

@apanashchenko thanks for suggestion. The problem is the maven plugin has the separate classpath, so it can't read the properties from your project resources. I'll think about it

Thanks a lot. I'll be waiting. Maybe you can give me a hint, how I can set this variable?(mvn site -Dallure.issues.tracker.pattern not good for us, because we use bamboo plugin for report generation)

btw I'll going to add ability to specify the patterns to allure bamboo plugin)

Cool) waiting for improvements)

You can create a related issue here https://github.com/allure-framework/allure-bamboo-plugin

Maybe you can give me a hint, how I can set this variable?(mvn site -Dallure.issues.tracker.pattern not good for us

I guess it is the only way for now, so stay turned we are going to fix this

fixed via https://github.com/allure-framework/allure-maven-plugin/pull/23


Fix typo in PR template

Purpose
This PR fixes a typo in the PR template.
Check List

[x] Read the Contributing Guide
[ ] Required Balo version update
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

It seems this is already fixed with https://github.com/ballerina-platform/ballerina-lang/pull/15978. Seems this PR (which is older) has missed when merging this.


Support whole number float64 type for severity parsing

Severity parsing should support float64 values when they are whole numbers. Golang JSON parsing will consider any number a float64 unless it is unmarshalled to a struct using specific types (int, int64, float64, etc).
Trying to parse the pri field as a Severity will result in an "unsupported type float64" error.
{
  "uid": 62,
  "time":<PHONE_NUMBER>,
  "pri": 6,
  "tag": "pve-ha-lrm",
  "pid": 33690,
  "node": "pve-1",
  "user": "root@pam",
  "msg": "end task UPID:pve-1:0000839B:000C5C3F:6067BB15:qmshutdown:100:root@pam: OK"
}

Additional context:

Stanza PR https://github.com/observIQ/stanza/pull/268
Stanza Issue https://github.com/observIQ/stanza/issues/267

when they are whole numbers

Just to clarify, this works for non-whole numbers as well, right? The number will just lose its decimal precision?


The reset() method does not delete the last response obtained from the form action

Currently, when using the reset() method, it seems to reset the form, the inputs, but the form.response and form.error are not reset. You should reset all form data completely when using this method.

@sawa-ko thanks - that should be a quick fix. Please feel free to submit a PR.

@ivanfilhoz I tried and failed, I need your help! I was unable to detect where the response is handled.


[Chainquery] implement HEALTHCHECK

Eventually, we need boilerplate health checks for all of the containers shipped with the containers themselves.

I'd like to take this.  Although I believe the first healthcheck should be librycrd.
Is there something that can be curl'd in order to determine if chainquery [or librycrd] is ready?

I see this in Dockerfile:
TODO: Implement healthcheck.
HEALTHCHECK ["healthcheck"]
/usr/bin/healthcheck is a script that relies on curl, which isn't installed.  I'd like to take a stab getting it to work with lbrycrd-cli

I have a working patch for lbrycrd healthcheck.  Let's see if I can get chainquery done tonight.

@dangarthwaite open some PR's!

So - the actual healthcheck for chainquery is untested.  A whole lot of other configuration files were tweaked to get lbrycrd running in regtest mode.  In the end this ticket is blocked until https://github.com/lbryio/chainquery/issues/121 is fixed.  chainquery serve gives an error when it starts.
What does work are healthcheckers for lbrycrd and mysql containers that are in this PR.  Also a rewrite of chainquery/start.sh that ought to be wire-compatible and a LOT easier on the eyes.

For the most part the Chainquery "healthcheck" in this case was just to make sure the process hadn't died and had completed it's initial boot process.

I changed chainquery's Dockerfile to download the latest version.  All three containers now have healthchecks.
dan@macbook:~/Projects/forks/lbry-docker
$ cd lbrycrd && docker-compose ps && cd ..
      Name          Command      State                                             Ports
------------------------------------------------------------------------------------------------------------------------------
lbrycrd_lbrycrd_1   start     Up (healthy)   11337/tcp, <IP_ADDRESS>:11337->29245/tcp, <IP_ADDRESS>:11336->29246/tcp, 9245/tcp, 9246/tcp
dan@macbook:~/Projects/forks/lbry-docker
$ cd chainquery && docker-compose ps && cd ..
         Name                       Command                State                     Ports
--------------------------------------------------------------------------------------------------------
chainquery_chainquery_1   start                         Up (healthy)   <IP_ADDRESS>:6300->6300/tcp
chainquery_mysql_1        docker-entrypoint.sh mysqld   Up (healthy)   <IP_ADDRESS>:3306->3306/tcp, 33060/tcp

Fixed by #87


Merge pull request #500 from MicrosoftDocs/main

Deploy February 2022 tools update content

Docs Build status updates of commit 7658a9d:
:warning: Validation status: warnings
For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


#4 #3 #2 #1

Add random quote, so it's now random
Repl.it link: https://repl.it/@IrisDroidology/python-random-quote
https://github.com/irisdroidology/python-learning/issues/3

Task linked: CU-1wu1hx Read from a file


Add a setting to allow private fields to be indexed.

Description
Currently, there is no way to index private fields to be used for search, filter, sort or display.
Basic example
If I had a field that contains metadata or other value that I do not wish to include in the API responses I would make it a private field. However, I still may want to use this value for search, filter or sort. Currently, this is not possible without making the field non-private in which case it requires additional logic on the Strapi side to sanitize the field from the responses.
Potential solutions

Ignore sanitizing private fields if they appear on either searchableAttributes, distinctAttribute, filterableAttributes, searchableAttributes or sortableAttributes.

Pros:

Does not deviate from the Meilisearch settings spec.
Does not introduce an additional setting.

Cons:

By default will be included when using ["*"] which may not be ideal.
Prone to be exposed by mistake.

Add a new setting called indexedPrivateAttributes that takes an array of private attribute names.

Pros:

Easier to distinguish and less likely to expose sensitive fields by mistake.
Can work alongside ["*"] as this is a separate setting.
Can be more flexible depending on the implementation.

Cons:

By default will allow full scope (search, filter, sort, display) unless an additional attribute is added to the same setting to get the scope.
Will deviate from the Meilisearch settings spec.

Other
PR that introduced the current behaviour: https://github.com/meilisearch/strapi-plugin-meilisearch/pull/703
Mentioned in https://github.com/meilisearch/strapi-plugin-meilisearch/issues/695

Hey @haZya, another solution would be to create a boolean in the settings noSanitize that avoid sanitizing any field in any document and then use transformEntry to filter out what you'd like to keep or not. What do you think?

Hi @bidoubiwa Yes, that does sound like a viable solution. I believe this is how it originally worked before the PR that introduced private field sanitization. The difference is the toggle noSanitize boolean to set it on or off.
But the small caveat I see is that this by default will index with full scope search, filter, sort, display . And if I only want to say use it for filter there is no way to allow only that scope. This is not a major problem, but if there are a lot of private fields or they have a lot of content in them, this could increase the document size making it noticeably slower.

Hi @haZya, indeed, it could be an issue, but I believe it will not be a huge concern for 99% of the cases.
If @bidoubiwa's proposed solution can work, I will be glad to review a PR with this :)

Hi @brunoocasali
Yes, I think @bidoubiwa's solution will cover most use cases. I'd like to do a PR on this but my current schedule won't allow me to start working on it immediately. If this is not urgent please go ahead and assign me for this.

Nice @haZya no rush then, we can review it whenever you submits it :)
Thanks a lot for your help!


SwiftCompilerSources: remove references to C's stderr

Fixes a linux build error.
The var standardError was only used in one place for logging, which can be done with log anyway. Instead of using such C library constructs directly we should bridge to higher level APIs. This is more platform independent.
https://github.com/swiftlang/swift/issues/73252
https://github.com/swiftlang/swift/issues/74701

@swift-ci smoke test


[Feature] Notify users of new updates

Description

We should update users of new updates of the CLI, so they know when to update.
Describe the solution you'd like

We can use https://www.npmjs.com/package/update-notifier, it should be straightforward.
Describe alternatives you've considered
"Watch" the GitHub repo or follow social media channels of Leon to be aware of new updates.

 ✨ [CLI 1.1.0] Notify users of new updates


☁  mounting .azure

Mounting .azure so user is logged in to az inside the container

@sozercan,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

My only concern is:

user has never logged into CLI
user enters container
user logs in
user exits container
az tries to refresh an access token or something, and now it can't write to the files in ~/.azure because they're owned by root since they were created in the container.

Not sure if it's enough to block this change, but wanted to mention it.

This can still wind up with users who have ~/.azure/accessTokens.json owned by root, which will be awkward, but this is already true for any files created in container, like _output/* etc... so I'm going to go ahead and give my approval since this is probably a win for acs-engine usability.

I guess maybe adding a sudo -u $(loguser) chown -R $(loguser) . or whatnotafter the docker run might help a tiny bit?

@colemickens chown after docker run seems to be a better solution, let me know if this works


Removed non-ISO usage of FUNCTION.

Fixes #1843

Verde!
(coveralls seems to be stuck across the board).

Which means I can't merge from my phone, so it'll have to be tomorrow :)
On Sun, May 31, 2015, 8:40 PM David G. Quintas<EMAIL_ADDRESS>wrote:

Verde!
(coveralls seems to be stuck across the board).
—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/1844#issuecomment-107298632.


Combine historical with realtime collected bars

data.history() now returns ingested data combined with realtime data collected from broker.

Coverage increased (+0.09%) to 86.173% when pulling 3b5745efe3f7b1de12bfca26a014f156cf4ad38b on tibkiss:feature/combine_historical_with_realtime_bars into 7d1e8b1181b6dd8c1df1c68ee5b13ff224cdc7cc on zipline-live:master.


Browser redirects to link.trustwallet.com/wc (when using WalletConnect) instead of redirecting to TW app

We are having troubles with TrustWallet WalletConnect integration on iOS only (on Android there are no issues).
Steps to repro:

Add Multi-Coin wallet to TrustWallet
Open web dApp in Chrome/Safari on mobile iOS directly (same device as TrustWallet)
dApp connect to mobile WalletConnect and ask for signature

Instead of asking signature in TrustWallet window, it instead redirects page to https://link.trustwallet.com/wc (so our app is closed)

After clicking "Open in Trust Wallet" button there, TW app say: Warning - Deep Link is not supported. (Also not always, sometimes nothing happens)

Expected behavior
Expected would be to redirect into TrustWallet app and ask for confirmation of walletConnect signature. Same as on Android.
Additional context
TrustWallet 5.13
iOS 14.4
Note that I am aware that this might not be bug, but possibly misunderstanding of WalletConnect API on iOS... but I cannot find any reasonable help to resolve this so far. And seems it might be issue with TrustWallet, as it works reliably on Android.

Can you provide video of the issue? I'm not able to understand how to reproduce this issue?

It's happening with active WalletConnect (Multi-Coin Wallet) session (after unlocked wallet = active session):
https://user-images.githubusercontent.com/1630137/108418963-35b64100-7232-11eb-878f-1da5202ed3e2.mp4

On video you can see how I clicked Button to ask for signature of text..
It then redirects instead, and after click on "Open in TrustWallet" no signature is asked too..

If that would be helpful, I can prepare some test environment..

We've seen this now when people are connecting their Trust wallets to our PoolTogether dapp via WalletConnect. Connecting the wallet worked, but when they go to send an "Approve DAI" transaction it redirects to the browser with "https://link.trustwallet.com/wc" in the URL bar.

Exactly the same problem here :/

It looks like web socket reconnecting in latest iOS app is broken, will fix it soon

Any update on this? Thanks in advance

Any update on this? Thanks in advance

We expect to push an iOS update today/tomorrow with fixes for this issue.

Trust iOS 5.15 is released to App Store

Problem solved 👌 thank you 🙏💪

Works great now! Thanks :+1:

This is again happen in latest version 6.3

This is again happen in latest version 6.3

Same issue here


Feature request - Glow animation

Hello me again.
I think a glow animation would be a nice addition, this would be animating the box-shadow property.
You could also use CSS variables --glow-colour (or color).
Even you could also have something like --glow-size and then use: calc(var(--glow-size) * 1px):
See my pen:
box-shadow: 0 0 calc((var(--glow-size) * 2) * 1px) calc(var(--glow-size) * 1px) blue;
Just an idea ;-)

great! I'm gonna give it a try... thanks for your suggestion.

I do understand the request but I think this is out of the animate's scope which has never included or planned to add style to elements.


Upgrade to operator-sdk 1.0.1

All I know is that it is due to the new scaffolding logic. Perhaps they are
using the old beta API to have better backwards compatibility? Not entirely
sure.
On Fri, 2 Oct 2020, 01.57 Jestin Woods<EMAIL_ADDRESS>wrote:

@jswoods approved this pull request.
In charts/humio-operator/templates/crds.yaml
https://github.com/humio/humio-operator/pull/161#discussion_r498562995:

           type: object

       type: object

     status:

       description: HumioRepositoryStatus defines the observed state of HumioRepository

       properties:

         state:

           type: string

       type: object

   type: object

served: true
storage: true
subresources:

 status: {}

-apiVersion: apiextensions.k8s.io/v1
+apiVersion: apiextensions.k8s.io/v1beta1
Do you know why we moved from v1 to v1beta1 here?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/humio/humio-operator/pull/161#pullrequestreview-500786419,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABUEZUZAPME7FE5T35SRQWTSIUJQFANCNFSM4SARNKVA
.


Use integer type for integer fields

Currently all numeric fields are specified having "type": "number", while the GBFS specification defines most of these fileds using Non-negative Integer. This would be reflected better by changing this to "type": "integer", which the json schema specification allows. Also, we could utilize the minimum validation to make sure the values are non-negative.

Thanks for flagging this! Closing this issue, this has been fixed in #58


Error connecting to WebSocket

What kind of request is this (question/bug/enhancement/feature request): bug
Steps to reproduce (least amount of steps as possible):
i create cluster and set etcd , worker , console
and i wait but app is broken
gime me error on after login
Result:
Other details that may be helpful:
Logs-> https://gist.github.com/TheYkk/6b6f1fb67f0848b6a8dbf28888772da4
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI):

Rancher
v2.1.7

User Interface
v2.1.21

Installation option (single install/HA): single

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): custom
Machine type (cloud/VM/metal) and specifications (CPU/memory): vm
Kubernetes version (use kubectl version):

(paste the output here)

Docker version (use docker version):

Client:
 Version:           18.09.3
 API version:       1.39
 Go version:        go1.10.8
 Git commit:        774a1f4
 Built:             Thu Feb 28 06:40:58 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          18.09.3
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.10.8
  Git commit:       774a1f4
  Built:            Thu Feb 28 05:59:55 2019
  OS/Arch:          linux/amd64
  Experimental:     false

There is not really enough information in here to determine what is going on. Are you getting the error websocket popup after logging in to Rancher? Are you directly connecting to port 443 on the host you are running the rancher/rancher container? Does it happen when you start a new container without creating a cluster or does it always happen?

I forgot to close the problem , sorry.


progress for --fsck in setupwizard

If somebody has a lot of archives, the "Verifying archive integrity" stage can take a long time.  It would be nice to display more progress than merely the spinning wheel.

Fixed in #552.


fix: make intToHex produce valid Quantity

Fixes #70

Thanks for the contribution! Completely agree with the "Quantity" data type not having the leading zero, that is wrong, but there were some cases where the leading zero was required. Not within an RPC payload, but when the hex string is used for certain operations that expect the input to have an even length (so that each pair of digits can be used to represent one byte).
I'm unsure if that concern applies in this case. I'll audit the uses of the intToHex funciton to find out.


<EMAIL_ADDRESS>big benchmark regression

In this PR, I upgraded async-std to 1.6-beta.1 because I'm interested in its wasm support, I'm using the PR from fix/file-block.
From the benchmark numbers, I found that there is a big bench regression:
You should be able to see it from here:
https://travis-ci.org/github/casbin/casbin-rs/jobs/685015785#L813

bench code: https://github.com/casbin/casbin-rs/blob/master/benches/benchmark.rs

I also would like to improve bench code by creating only one runtime but since: https://github.com/async-rs/async-std/issues/749 wasn't solved and I don't know how to do it.

See also: https://github.com/async-rs/async-attributes/issues/9

@dignifiedquire Any idea on this? Thanks in advance.

@GopherJ it may also be useful to open an issue on smol since most of the runtime logic now lives there.

@yoshuawuyts From

I believe because async-std's block_on currently starts a smol worker rather than just blocking on a future. This is currently a hack necessary to make spawning thread-local tasks within block_on possible.

then it becomes hard to benchmark async code. block_on will influence the result a lot

I am working on this, the issue will be fixed with smol 0.2 when it gets released. The solution is to create a thread-local executor lazily on demand. If there is no spawn_local() inside block_on(), there is no reason to initialize a thread-local executor.

@stjepang does that mean smol 0.2 block_on will semantically be closer to old async-std and tokio? i.e. in a single threaded runtime, it uses the local thread?
i would like to use smol, but i'm currently struggling cause my simplest case is a block_on that i don't want to spawn any new threads to drive, just use the current.

@algesten In that case, I wonder why not just use smol::run() to run it on the current thread?
Version 0.2 will break smol into 3 subcrates: blocking (already done), async I/O + timers, and executor. There will be more knobs for async I/O and executors, which will allow us to implement block_on() in async-std more efficiently.

@stjepang ah you're right! thanks! I'm just getting acquainted with smol's API. run is indeed what i'm after.

Is this still an issue? I believe it has been resolved but can we check?

HI, @stjepang , I confirm it's nearly fixed:
#![feature(test)]

extern crate test;

use test::Bencher;

fn raw_enforce(r: [&str; 3]) -> bool {
    let policies = [["alice", "data1", "read"], ["bob", "data2", "write"]];
    for policy in &policies {
        if policy == &r {
            return true;
        }
    }
    return false;
}

async fn async_enforce(r: [&str; 3]) -> bool {
    raw_enforce(r)
}

#[bench]
fn b_benchmark_raw(b: &mut Bencher) {
    b.iter(|| {
        raw_enforce(["alice", "data1", "read"]);
    });
}

#[bench]
fn b_benchmark_async(b: &mut Bencher) {
    b.iter(|| {
        async_std::task::block_on(async_enforce(["alice", "data1", "read"]));
    });
}


Add Kubeflow Website links to README

I updated the README with the latest Kubeflow website links that we created.
I removed legacy quick started guide since we have a new one on the website.
If you want me to add more information to the Training Operator README, please let me know.
/assign @johnugeorge @tenzen-y @terrytangyuan @kuizhiqing @deepanker13
/hold for review

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.09%) to 42.816%

Totals

Change from base Build<PHONE_NUMBER>:
-0.09%

Covered Lines:
3749

Relevant Lines:
8756

💛  - Coveralls

Thanks for this @andreyvelich

/approve


APP-475: Fix notification demo flow

/cc @Slash32 @socallmemaybe @GamovCoder

QA Review fixes is not a good description. Please, describe what has been found and what this commit does. (Basically, you're rarely interested in how the issue was found.)

@kaa-leeroy test this please

@socallmemaybe @GamovCoder @rasendubi please review.

@kaa-leeroy test this please


chore: move message decryption into Veritech server

This rather large change move the decryption of function execution requests from the Cyclone server to the Veritech server. Sensitive string redaction still takes place in the Cyclone server.
Prior to this change, portions of the function execution requests would be encrypted before being passed into a Veritech client call using a a public/private keypair called the "Cylone encryption key". The reason for this naming is that the request portions would be decrypted in a Cyclone server before being passed to a language server for final execution.
In order to remove any chance of a user-authored function being able to access such a decryption key, the request decryption activity is now handled back in the Veritech server before it sends the now fully decrypted request over a web socket to a Cyclone server. As a result, there is zero requirement for any message cryptography in the Cyclone server.
The second task that was performed in the Cyclone server was secret substring redaction, using a CycloneSecretStrings Rust type. With this change, the secret substring redaction still takes place in the Cyclone server but now this is realized by adding the set of "sensitive" secrets as part of every Cyclone request. This is how the Cyclone server knows which strings to redact while not participating in the original decryption of the data.
As a result of the change in responsibility, these encryption/decryption keys are now known as "Veritech encryption" and "Veritech decryption" keys. Consequently all variables, CLI arguments, and files in our source tree have been updated to eliminate any possibility of future confusion.

bors try

bors retry

bors try

bors merge


[Volunteer] admin supports permissions based on different applications

Volunteer help
admin dashboard can config the different roles for different application users, the user just can edit the data that he or she owns.

done


Update tests

w/ the support of vector search on service side, now service returns
"document_count", "vector_index_size", "storage_size"
rather than
"document_count", "storage_size"
update the tests plus add retry delay to make tests more stable.

API change check
API changes are not detected in this pull request.

These look like all the tests now take in a backoff_retry with the same value, would it make sense to make it a fixture in conftest so it makes it easier to adjust ?


shouldSend not working

I have setup sentry for electron with a shouldSend that will only send events if user has agreed on it. This is the code:
const { init } = require('@sentry/electron');
const guideSettings = require('./models/guide-setting')();
const log = require("electron-log");
const sentry = require('../assets/data/sentry');

const shouldSendIfAgreed = async () => {
	const result = await guideSettings.findAll();
	log.info("crashReportAgreement", result[0].crashReportAgreement); // prints 0
	// return (result[0].crashReportAgreement === 1)
	return false;
}

module.exports = {
	startCrashReport: async () => {
		log.info("Starting Crash Report")
		init({
			dsn: sentry.dsn,
			shouldSend: (data) => {
				return shouldSendIfAgreed();
			}
		});
		return;
	}
};

So I commented out the actual condicional and changed it to false. Even though, it will not stop sentry to send the error event.
Is there anything I need to do that is not being done on this code or there is actually a bug?
Cheers

shouldSend is a synchronous callback. Since your async implementation effectively returns a truthy value (the Promise), it will always send, regardless of what the Promise resolves to. Return a boolean synchronously and the callback will work as expected.
To do so, you will probably have to externally manage a flag. Also, beware that by marking the startCrashReport function async, its execution might be deferred and enable the crashReporter too late to catch errors happening in the first event loop cycle(s). There's actually no reason this function is async.
const { init } = require('@sentry/electron');
const guideSettings = require('./models/guide-setting')();
const log = require("electron-log");
const sentry = require('../assets/data/sentry');

// assume the user has not agreed until settings have loaded
let agreed = false;

async function loadAgreement() {
	const result = await guideSettings.findAll();
	agreed = result[0].crashReportAgreement === 1;
	log.info("crashReportAgreement", agreed);
}

module.exports = {
	startCrashReport: () => {
		log.info("Starting Crash Report")
		init({
			dsn: sentry.dsn,
			shouldSend: () => agreed,
		});

		// prevent unhandled promise rejections here
                 // alternatively await here and catch the rejection at the call site
		loadAgreement().catch(e => log.error(e));
	}
};


feat|chore|fix: prepare tooling for qa

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)

TODO:

[x] Refactor all of Tom's old nonsense to ESModule Syntax
[ ] Fix bug where copyNonWDirToProject does not work?

@moT01 Sorry, but the workflow is not bug-free when copying to and from root.
So, I am going to go with plan B - Campers must work within the build-a- folders, and I will dynamically hide the ones not selected.

Please note: The project tests are now broken, but that should be an easy fix, I will do in another PR


update version from 0.1.0 to 0.1.1

Signed-off-by: Chris Ahl<EMAIL_ADDRESS>For issue https://github.com/open-cluster-management/backlog/issues/17921

/hold

/unhold


Backport "HBASE-28687 BackupSystemTable#checkSystemTable should ensure system tables are enabled (#6018)" to branch-2

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m  4s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
hbaseanti
0m  0s

Patch does not have any anti-patterns.

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
4m 54s

branch-2 passed

+1 :green_heart:
compile
0m 34s

branch-2 passed

+1 :green_heart:
checkstyle
0m 14s

branch-2 passed

+1 :green_heart:
spotbugs
0m 42s

branch-2 passed

+1 :green_heart:
spotless
0m 59s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 30s

the patch passed

+1 :green_heart:
compile
0m 27s

the patch passed

+1 :green_heart:
javac
0m 27s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 10s

the patch passed

+1 :green_heart:
spotbugs
0m 54s

the patch passed

+1 :green_heart:
hadoopcheck
12m 14s

Patch does not cause any errors with Hadoop 2.10.2 or 3.3.6.

+1 :green_heart:
spotless
1m  9s

patch has no errors when running spotless:check.

_ Other Tests _

+1 :green_heart:
asflicense
0m 14s

The patch does not generate ASF License warnings.

29m  7s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6029/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6029

Optional Tests
dupname asflicense javac spotbugs checkstyle codespell detsecrets compile hadoopcheck hbaseanti spotless

uname
Linux 39b0a352064c 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 9c713fbbdf023e05082dffeb2b9bc19380c7bc8e

Default Java
Eclipse Adoptium-11.0.17+8

Max. process+thread count
77 (vs. ulimit of 30000)

modules
C: hbase-backup U: hbase-backup

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6029/1/console

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m 15s

Docker mode activated.

-0 :warning:
yetus
0m  5s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m 42s

branch-2 passed

+1 :green_heart:
compile
0m 25s

branch-2 passed

+1 :green_heart:
javadoc
0m 17s

branch-2 passed

+1 :green_heart:
shadedjars
6m 23s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m  4s

the patch passed

+1 :green_heart:
compile
0m 18s

the patch passed

+1 :green_heart:
javac
0m 18s

the patch passed

+1 :green_heart:
javadoc
0m 13s

the patch passed

+1 :green_heart:
shadedjars
5m 29s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
12m 18s

hbase-backup in the patch passed.

34m 43s

Subsystem
Report/Notes

Docker
ClientAPI=1.46 ServerAPI=1.46 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6029/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6029

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux e30cfff28cb0 5.4.0-186-generic #206-Ubuntu SMP Fri Apr 26 12:31:10 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 9c713fbbdf023e05082dffeb2b9bc19380c7bc8e

Default Java
Temurin-1.8.0_352-b08

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6029/1/testReport/

Max. process+thread count
3051 (vs. ulimit of 30000)

modules
C: hbase-backup U: hbase-backup

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6029/1/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 48s

Docker mode activated.

-0 :warning:
yetus
0m  5s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
4m  5s

branch-2 passed

+1 :green_heart:
compile
0m 25s

branch-2 passed

+1 :green_heart:
javadoc
0m 18s

branch-2 passed

+1 :green_heart:
shadedjars
6m 44s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 27s

the patch passed

+1 :green_heart:
compile
0m 21s

the patch passed

+1 :green_heart:
javac
0m 21s

the patch passed

+1 :green_heart:
javadoc
0m 17s

the patch passed

+1 :green_heart:
shadedjars
6m 37s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
11m 59s

hbase-backup in the patch passed.

36m 18s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6029/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6029

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux 64609efdab45 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 9c713fbbdf023e05082dffeb2b9bc19380c7bc8e

Default Java
Eclipse Adoptium-11.0.17+8

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6029/1/testReport/

Max. process+thread count
3815 (vs. ulimit of 30000)

modules
C: hbase-backup U: hbase-backup

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6029/1/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 41s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
hbaseanti
0m  0s

Patch does not have any anti-patterns.

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m 58s

branch-2 passed

+1 :green_heart:
compile
0m 37s

branch-2 passed

+1 :green_heart:
checkstyle
0m 17s

branch-2 passed

+1 :green_heart:
spotbugs
0m 43s

branch-2 passed

+1 :green_heart:
spotless
1m  1s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 50s

the patch passed

+1 :green_heart:
compile
0m 31s

the patch passed

+1 :green_heart:
javac
0m 31s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 10s

the patch passed

+1 :green_heart:
spotbugs
0m 43s

the patch passed

+1 :green_heart:
hadoopcheck
11m 47s

Patch does not cause any errors with Hadoop 2.10.2 or 3.3.6.

+1 :green_heart:
spotless
0m 53s

patch has no errors when running spotless:check.

_ Other Tests _

+1 :green_heart:
asflicense
0m 10s

The patch does not generate ASF License warnings.

27m  6s

Subsystem
Report/Notes

Docker
ClientAPI=1.46 ServerAPI=1.46 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6029/2/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6029

Optional Tests
dupname asflicense javac spotbugs checkstyle codespell detsecrets compile hadoopcheck hbaseanti spotless

uname
Linux 2d05e793855b 5.4.0-182-generic #202-Ubuntu SMP Fri Apr 26 12:29:36 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 9c713fbbdf023e05082dffeb2b9bc19380c7bc8e

Default Java
Eclipse Adoptium-11.0.17+8

Max. process+thread count
76 (vs. ulimit of 30000)

modules
C: hbase-backup U: hbase-backup

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6029/2/console

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 42s

Docker mode activated.

-0 :warning:
yetus
0m  4s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
2m 34s

branch-2 passed

+1 :green_heart:
compile
0m 15s

branch-2 passed

+1 :green_heart:
javadoc
0m 12s

branch-2 passed

+1 :green_heart:
shadedjars
5m  5s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 14s

the patch passed

+1 :green_heart:
compile
0m 14s

the patch passed

+1 :green_heart:
javac
0m 14s

the patch passed

+1 :green_heart:
javadoc
0m 11s

the patch passed

+1 :green_heart:
shadedjars
5m  2s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
11m  2s

hbase-backup in the patch passed.

28m 26s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6029/2/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6029

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux f3d2549877e3 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 9c713fbbdf023e05082dffeb2b9bc19380c7bc8e

Default Java
Temurin-1.8.0_352-b08

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6029/2/testReport/

Max. process+thread count
3383 (vs. ulimit of 30000)

modules
C: hbase-backup U: hbase-backup

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6029/2/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 48s

Docker mode activated.

-0 :warning:
yetus
0m  5s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m 54s

branch-2 passed

+1 :green_heart:
compile
0m 28s

branch-2 passed

+1 :green_heart:
javadoc
0m 21s

branch-2 passed

+1 :green_heart:
shadedjars
6m 58s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 52s

the patch passed

+1 :green_heart:
compile
0m 24s

the patch passed

+1 :green_heart:
javac
0m 24s

the patch passed

+1 :green_heart:
javadoc
0m 18s

the patch passed

+1 :green_heart:
shadedjars
6m 45s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
12m  1s

hbase-backup in the patch passed.

36m 50s

Subsystem
Report/Notes

Docker
ClientAPI=1.46 ServerAPI=1.46 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6029/2/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6029

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux 8c6944c119f8 5.4.0-182-generic #202-Ubuntu SMP Fri Apr 26 12:29:36 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 9c713fbbdf023e05082dffeb2b9bc19380c7bc8e

Default Java
Eclipse Adoptium-11.0.17+8

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6029/2/testReport/

Max. process+thread count
3477 (vs. ulimit of 30000)

modules
C: hbase-backup U: hbase-backup

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6029/2/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.


migrate to stdlib 9

we're using this locally and it works fine

Hi there @bastelfreak! Unfortunately we don't actually have anyone maintaining this repo any more as we no longer run Puppet. I'm about to archive this and a bunch of other Puppet-related repos that we haven't touched in a long time.
It's not really feasible for us to accept contributions at this point, as there's quite a bit of process involved on our side and we no longer have enough reviewers on our side who can review Puppet.
My apologies that we haven't signposted that we're no longer set up to receive outside contributions.
You're most welcome to fork, of course — not that that's much consolation. I'm sorry to be the bearer of bad news. I really appreciate that you want to contribute here and I'm sad that I can't help make that happen on this occasion 😞


configs/gradio not found

hi,
I am running gradio_app.py, which needs "configs/gradio" config files, but I cannot find them in your project. Can you provide them for me, thanks!

We will push gradio api demo， ASAP

We will push gradio api demo， ASAP

Thanks!

I want to deploy a web like your "Live Demo" (https://modelscope.cn/studios/Damo_XR_Lab/3D_AIGC) in my ubuntu20.02 machine. Can you provide a tutorial about how to do it, please. Thanks!

I want to deploy a web like your "Live Demo" (https://modelscope.cn/studios/Damo_XR_Lab/3D_AIGC) in my ubuntu20.02 machine. Can you provide a tutorial about how to do it, please. Thanks!

This is our alibaba internal deployment platform, this you should not be able to deploy (●'◡'●)


[3.2] Mark the first shape as inside, not the second shape, when CSG shapes are co-planer.

3.2 version of #41199.

Thanks!


Hello, the AP result I gave after training with the default settings is quite low, only 0.XXXX data, not even 1, I want to know where my reason appears


ops.split() does not split LineString self-intersections as expected

Expected behavior and actual behavior.
When trying to split a LineString that self-intersects, EG:
"""
          (1,2)--<--(2,2)
            |         |
            v         ^
            |         |
(0,1)--->---+--->---(2,1)
            |
            v
            |
          (1,0)
"""

If the "splitter" is a point placed at the line self-intersection (1,1), I would expect the line to be split twice at that location, EG from the example above:
from shapely import ops
from shapely.geometry import LineString, Point
line = LineString([(0, 1), (2, 1), (2, 2), (1, 2), (1, 0)])
point = Point(1, 1)
split_line_collection = ops.split(line, point)

I would expect the returned geometry collection to contain the following lines:
LineString([(0, 1), (1, 1)])
LineString([(1, 1), (2, 1), (2, 2), (1, 2), (1, 1)])
LineString([(1, 1), (1, 0)])

However, it appears in this case to only be splitting the line once by the point, at the "first" instance along the line:
from shapely import ops
from shapely.geometry import LineString, Point
line = LineString([(0, 1), (2, 1), (2, 2), (1, 2), (1, 0)])
point = Point(1, 1)
split_line_collection = ops.split(line, point)
for geom in split_line_collection.geoms:
    print(list(geom.coords))

[(0.0, 1.0), (1.0, 1.0)]
[(1.0, 1.0), (2.0, 1.0), (2.0, 2.0), (1.0, 2.0), (1.0, 0.0)]

Operating system
Windows 10
Shapely version and provenance
Shapely version 1.6.4, installed using pip

Sorry, but this is nearly a duplicate of other closed issues: lines cannot be reliably split using a point due to floating point precision issues.

Yeah ok, that makes sense.
Sorry for duplicating a closed issue, and thanks for the reply!


Object ID is different on every Azure tenant

Following line needs to be fixed. The AppID of the KV principal remains the same in every AAD, but the Object is different on every AAD and you can get it with: az ad sp show --id cfa8b339-82a2-471a-a3c9-0fc0be7a4093
<<<93c27d83-f79b-4cb2-8dd4-4aa716542e74 is the Object ID for Key Vault in the Azure public cloud. To get the Object ID for Key Vault in the Azure Government cloud, see Service principal application ID.>>>

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: cebec73e-e7f4-75c5-2068-ae89f12d8d95
Version Independent ID: e2497a7b-3b5f-554a-1a31-da540740fcc9
Content: Manage storage account keys with Azure Key Vault and the Azure CLI
Content Source: articles/key-vault/key-vault-ovw-storage-keys.md
Service: key-vault
GitHub Login: @msmbaldwin
Microsoft Alias: mbaldwin

@FabianGCZ Thanks for your feedback! We will investigate and update as appropriate.

@FabianGCZ Thanks for your feedback.  There is already a GitHub issue-36229 and this issue will be address covered with the same.


KYLIN-3586

Use parseInt() to parse a primitive instead of to use boxing/unboxing

Can one of the admins verify this patch?

Can one of the admins verify this patch?

LGTM. Merged.


MethodDeclarationMacro needs to be specialized for top level functions

Today the api is void visitMethodDeclaration(MethodDeclaration declaration, ClassDeclarationBuilder builder) but really we need a LibraryDeclarationBuilder for this case, as the addToClass method on ClassDeclarationBuilder doesn't make sense in this context :).

We now have Function* introspection types and macros


Button made using HTML and CSS

I added some transition effects to the button and styled it with different hover effects to enhance its look.

@geeky-hypertext629 The button isn't centered aligned.
Please resolve this and make a PR.
Star and Follow. 🌟


Please document supported platform flags

Also related - I noticed --platform Windows/x86 called out as an example above, which is wrong. The typical Windows example should be Windows/amd64.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: c608162e-cf40-9d53-da4a-51f51a0311ea
Version Independent ID: eccbb543-be68-7de2-d41d-abee55c81452
Content: az acr
Content Source: src/command_modules/azure-cli-acr/azure/cli/command_modules/acr/_help.py
Service: container-registry
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

If you are trying to build using the example here with --platform Windows/x86 and get this error:
hcsshim::PrepareLayer failed in Win32: The parameter is incorrect. (0x57) path=C:\ProgramData\docker\windowsfilter\.. then you probably need to use --platform Windows/amd64 instead.

https://github.com/Azure/azure-cli/pull/10406 should have addressed this
CC: @northtyphoon


Block collision bug

So in vanilla if i stand sneaking at the edge of the corner block and place one block below its working

in minestom its not working

I think thats a bug :)

Should be fixed by bcfb4c6ea4d82228aca4336066efe7ab66460ad3


Add reduction for arrays.

This PR adds some reduction kernels for arrays. For CUDA and HIP the existing reduction kernels are reduced, with only one kernel added.
TODO

[ ] Add a return overload.

I want to ask whether we make Array class related to the device (not header only) or not? (before release 1.4)
for now, we have fill and this pr reduce.

have fill and reduce in class:
good for usage,
but need to link all ginkgo always and still use free function to use fill/reduce in the device side
only have fill and reduce free function
Array is header-only class
but always use free function to call fill/reduce.

Generally, I like to think of gko::Array as a the only vocabulary type that Ginkgo exposes. Something that can be used universally for interoperability with other libraries and user data. Now we have a few additions, namely value-converting Array::operator= and Array::fill that rely on actual device kernel and only work for specific ValueTypes. The more I think about it, the more I think it might be better to keep these out (replacing them by explicit conversion kernels for arrays only used internally, and maybe a datatype-agnostic Array::fill that acts like repeated memcpy)
All of this becomes especially important in the context of #715, where Array is the fundamental type that gets passed around between all shared libraries.
My point here is: If people want to compute a reduction over an array, I believe they should use more high-level functionality, like Dense or (maybe later) the simple kernel interface. Otherwise we risk overloading the Array type.

I agree with making not overloading Array, but I think that can severely restrict functionality. For example, the only way to store integer types right now is with arrays. And there are many situations where you need reductions for these integer arrays.

In that case, wouldn't a free function ValueType reduce(const Array<ValueType>&) be more suitable? What use case do you have in mind for index calculations from the user side?

Yes, I guess we could add a free function instead of member functions. I am not sure where to add them though. I think there are multiple use cases for reduction over integer arrays. To calculate the total number of non-zeros in a matrix, if you have the number of nonzeros per row to give a very specific example :)
But in general, I believe this is something useful not only from a user's perspective but also for us to write our algorithms more easily in our core.

In core algorithms, we usually need prefix sums, not plain reductions. And these computations are mostly necessary in the context of a matrix conversion, which we represent with a high-level interface already. If we want to use this operation inside core, we can use existing kernels.
I think we need to find a balance of how much we want to enable to write their own complex algorithms, and how generic we want to make that. Sum reductions are for example not the only important operation, think of (arg)min/max for building ELL.


i cant install wifiphisher

apt-get install dnsmasq                                             1 ⨯
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package dnsmasq is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'dnsmasq' has no installation candidate

What version of linux are you running? if you can run neofetch and post the output here. Also did you run apt update? If you can aswell post a dump of your /etc/apt/sources.list


[Bug]: Broken files for Select component when installing over CLI

Describe the bug
When installing the Select component as described on the website like so:
npx shadcn-vue@latest add select

I was getting the following errors:
[plugin:vite:vue] Error parsing JavaScript expression: Unexpected token, expected "," (5:1)

/TestProject/resources/js/Components/ui/select/SelectItem.vue:33:13
32 |      v-bind="forwardedProps"
33 |      :class="
34 |  cn(
   |  ^
35 |    'relative flex w-full cursor-default select-none items-center rounded-sm py-1.5 pl-8 pr-2 text-sm outline-none focus:bg-accent focus:text-accent-foreground data-[disabled]:pointer-events-none data-[disabled]:opacity-50',
36 |    props.class

[plugin:vite:vue] Error parsing JavaScript expression: Unexpected token, expected "," (6:1)

/TestProject/resources/js/Components/ui/select/SelectContent.vue:55:15
53 |      <SelectContent
54 |        v-bind="{ ...forwarded, ...$attrs }"
55 |        :class="cn(
   |                 ^
56 |    'relative z-50 max-h-96 min-w-32 overflow-hidden rounded-md border bg-popover text-popover-foreground shadow-md data-[state=open]:animate-in data-[state=closed]:animate-out data-[state=closed]:fade-out-0 data-[state=open]:fade-in-0 data-[state=closed]:zoom-out-95 data-[state=open]:zoom-in-95 data-[side=bottom]:slide-in-from-top-2 data-[side=left]:slide-in-from-right-2 data-[side=right]:slide-in-from-left-2 data-[side=top]:slide-in-from-bottom-2',
57 |    position === 'popper' &&

I checked out the installed files SelectItem.vue and SelectContent.vue and noticed that there is an extra square bracket ] placed after the cn(...) function call in each file respectively for the :class attribute.

Code for SelectItem.vue when installing the Select component over the CLI
<script setup>
import { computed } from "vue";
import {
  SelectItem,
  SelectItemIndicator,
  SelectItemText,
  useForwardProps,
} from "radix-vue";
import { Check } from "lucide-vue-next";
import { cn } from "@/lib/utils";

const props = defineProps({
  value: { type: String, required: true },
  disabled: { type: Boolean, required: false },
  textValue: { type: String, required: false },
  asChild: { type: Boolean, required: false },
  as: { type: null, required: false },
  class: { type: null, required: false },
});

const delegatedProps = computed(() => {
  const { class: _, ...delegated } = props;

  return delegated;
});

const forwardedProps = useForwardProps(delegatedProps);
</script>

<template>
  <SelectItem
    v-bind="forwardedProps"
    :class="
cn(
  'relative flex w-full cursor-default select-none items-center rounded-sm py-1.5 pl-8 pr-2 text-sm outline-none focus:bg-accent focus:text-accent-foreground data-[disabled]:pointer-events-none data-[disabled]:opacity-50',
  props.class
)]"
  >
    <span class="absolute left-2 flex h-3.5 w-3.5 items-center justify-center">
      <SelectItemIndicator>
        <Check class="h-4 w-4" />
      </SelectItemIndicator>
    </span>

    <SelectItemText>
      <slot />
    </SelectItemText>
  </SelectItem>
</template>

Code for SelectContent.vue when installing the Select component over the CLI
<script setup>
import { computed } from "vue";
import {
  SelectContent,
  SelectPortal,
  SelectViewport,
  useForwardPropsEmits,
} from "radix-vue";
import { SelectScrollDownButton, SelectScrollUpButton } from ".";
import { cn } from "@/lib/utils";

defineOptions({
  inheritAttrs: false,
});

const props = defineProps({
  forceMount: { type: Boolean, required: false },
  position: { type: String, required: false, default: "popper" },
  bodyLock: { type: Boolean, required: false },
  side: { type: null, required: false },
  sideOffset: { type: Number, required: false },
  align: { type: null, required: false },
  alignOffset: { type: Number, required: false },
  avoidCollisions: { type: Boolean, required: false },
  collisionBoundary: { type: null, required: false },
  collisionPadding: { type: [Number, Object], required: false },
  arrowPadding: { type: Number, required: false },
  sticky: { type: String, required: false },
  hideWhenDetached: { type: Boolean, required: false },
  updatePositionStrategy: { type: String, required: false },
  prioritizePosition: { type: Boolean, required: false },
  asChild: { type: Boolean, required: false },
  as: { type: null, required: false },
  class: { type: null, required: false },
});
const emits = defineEmits([
  "closeAutoFocus",
  "escapeKeyDown",
  "pointerDownOutside",
]);

const delegatedProps = computed(() => {
  const { class: _, ...delegated } = props;

  return delegated;
});

const forwarded = useForwardPropsEmits(delegatedProps, emits);
</script>

<template>
  <SelectPortal>
    <SelectContent
      v-bind="{ ...forwarded, ...$attrs }"
      :class="cn(
  'relative z-50 max-h-96 min-w-32 overflow-hidden rounded-md border bg-popover text-popover-foreground shadow-md data-[state=open]:animate-in data-[state=closed]:animate-out data-[state=closed]:fade-out-0 data-[state=open]:fade-in-0 data-[state=closed]:zoom-out-95 data-[state=open]:zoom-in-95 data-[side=bottom]:slide-in-from-top-2 data-[side=left]:slide-in-from-right-2 data-[side=right]:slide-in-from-left-2 data-[side=top]:slide-in-from-bottom-2',
  position === 'popper' &&
  'data-[side=bottom]:translate-y-1 data-[side=left]:-translate-x-1 data-[side=right]:translate-x-1 data-[side=top]:-translate-y-1',
  props.class
)]"
    >
      <SelectScrollUpButton />
      <SelectViewport
        :class="
          cn(
            'p-1',
            position === 'popper' &&
              'h-[--radix-select-trigger-height] w-full min-w-[--radix-select-trigger-width]',
          )
        "
      >
        <slot />
      </SelectViewport>
      <SelectScrollDownButton />
    </SelectContent>
  </SelectPortal>
</template>

Weirdly enough the code in the repository / registry seems to be correct, hence there isn't any ] after the cn(...) function call for the :class attribute:
https://github.com/radix-vue/shadcn-vue/blob/d50ea38f4abccdad5db190ad2b1da26815e4c6aa/apps/www/src/lib/registry/default/ui/select/SelectItem.vue#L31
and
https://github.com/radix-vue/shadcn-vue/blob/d50ea38f4abccdad5db190ad2b1da26815e4c6aa/apps/www/src/lib/registry/default/ui/select/SelectContent.vue#L43
System Info
* macOS
* node 20.15.0
* npm 10.7.0
* Safari 17.5
* npmPackages:
  * @vueuse/core: ^10.11.0 => 10.11.0
  * radix-vue: ^1.8.5 => 1.8.5
  * vue: ^3.4.31 => 3.4.31

Contributes

[ ] I am willing to submit a PR to fix this issue
[ ] I am willing to submit a PR with failing tests

JavaScript support for shadcn-vue components is not yet completed
Process of transforming Vue/TS to Vue/JS is handled by detypes inside CLI which has some edge cases

Fixed on v0.11.0


Fix README example install CLI

When executing the below command that is wrriten the README , we got an error.
$helm install my-release --namespace kube-system descheduler/descheduler

Error: failed to download "descheduler/descheduler"

I found that the chart name is different from README.
I think this PR may help people who want to install this chart.
$ helm repo list | grep descheduler
descheduler             https://kubernetes-sigs.github.io/descheduler/

$ helm search repo descheduler
NAME                                    CHART VERSION   APP VERSION     DESCRIPTION
descheduler/descheduler-helm-chart      0.19.0          0.19.0          Descheduler for Kubernetes is used to rebalance...

verified CLA

/assign @k82cn

cc @seanmalloy @damemi

/ok-to-test

thank you @taisyo7333 for noticing this though :)

/close


Fix Style/AlignArray

@homu r+

:pushpin: Commit f637a00 has been approved by indirect

@homu r+

:pushpin: Commit 536a496 has been approved by segiddins

:hourglass: Testing commit 536a496 with merge f676130...

:broken_heart: Test failed - status

Maybe a connection problem?

:sunny: Test successful - status

:eyes: Test was successful, but fast-forwarding failed: 422 Reference already exists


FEAT: support scheduling-policy for vllm

since version 0.6.3, the AsyncLLMEngine in vllm supports priority scheduling (https://github.com/vllm-project/vllm/pull/8850)，so add a new parameter "scheduling-policy" for the vllm model config to support priority scheduling.
Fixes #2669 .

Oh, I wrongly thought this solved #2669 , besides the scheduling policy, we can support priority as well right?

yes, but need to set the scheduling policy to priority, the default value is fcfs

yes, but need to set the scheduling policy to priority, the default value is fcfs

OK, can you add the priority option in this PR?

user can set the scheduling policy to priority by passing custom parameters when launching models with the vllm inference engine, whether through the interface or the command line. I didn't quite understand the specific meaning for add the priority option. Could you please elaborate further?

user can set the scheduling policy to priority by passing custom parameters when launching models with the vllm inference engine, whether through the interface or the command line. I didn't quite understand the specific meaning for add the priority option. Could you please elaborate further?

Indeed, the priority is an generation option, never mind, let’s check it later.