Improve FunctionLoader validations

Addresses issue: https://github.com/Azure/azure-functions-cli/issues/254
Reproduce steps
Configure a function for which the entry point doesn't return a function
e.g.: mistype module.exports and you'll end up with a valid entry point referencing an empty object
Proposed Solution
Improve the check and add a different message for when the entryPoint has been resolved but it is not a function

@nelak,
Thanks for your contribution.
To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla2.dotnetfoundation.org.
It will cover your contributions to all .NET Foundation-managed open source projects.
Thanks,
.NET Foundation Pull Request Bot

@nelak, thanks for signing the contribution license agreement. We will now validate the agreement and then the pull request.
Thanks, .NET Foundation Pull Request Bot

I figured getting the environment setup was really painful since I'm not building on windows, but mostly was on the CLI, for debugging I got it working by chance with a mix of VSCode and playing with the chrome debugger.
The worker code was easiest to work with although it had some hardcoded paths and references to powershell, etc. What I still haven't figured out is where the worker gets instantiated on how the grpc communication workflow works but I guess that must be buried in some library referenced by the SDK that I couldn't step into because I lacked the pdbs with the debugging info.

@nelak I had a chat with some team members, we're going to make a push to release the pdbs and get them source linked to github, would make it much easier to contribute / debug issues
Thanks again for the contribution!

@mamaso Pretty cool! That sounds great! Thanks!


migrating doc draft

Description
Replace this with a description of the PR. Explain the problem it solves and the proposed solution.
Fixes #168
Type of change
Please delete options that are not relevant.

[x] This change requires a documentation update

How Has This Been Tested?

[x] Tested manually
[x] Added automated tests

Checklist:

[x] Changelogs have been updated
[x] Unit tests have been added/updated
[x] Documentation has been updated

Codecov Report

Merging #169 (9714e8b) into main (5a567d3) will decrease coverage by 2.88%.
The diff coverage is 35.71%.

@@            Coverage Diff             @@
##             main     #169      +/-   ##
==========================================
- Coverage   87.06%   84.17%   -2.89%
==========================================
  Files          13       14       +1
  Lines         286      297      +11
  Branches       67       69       +2
==========================================
+ Hits          249      250       +1
- Misses         37       47      +10

Impacted Files
Coverage Δ

examples/logs/index.js
0.00% <0.00%> (ø)

src/instrumentations/index.ts
100.00% <ø> (ø)

src/options.ts
98.38% <100.00%> (+0.05%)
:arrow_up:

src/tracing.ts
97.95% <0.00%> (-2.05%)
:arrow_down:

Continue to review full report at Codecov.

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


upped reference to mongodb package to support newer versions of mongo

without this change loading fixture data fails

+1, I've had the same problems since updating mongo.

This would be great to have merged in. Wanting to use Mongo 3.0


Chrome logs from selenoid are not coming up with latest chrome :85 image

With chrome 85
Complete logs are not generated , Following are the only log statements that were generated
2020-08-30T18:09:27.999188259Z 2020/08/30 18:09:27 [INIT] [Listening on :7070]
2020-08-30T18:09:29.344704250Z Waiting X server...
2020-08-30T18:09:29.621052094Z Waiting X server...
2020-08-30T18:09:29.650258273Z Logging to: /dev/null
2020-08-30T18:09:29.753304972Z Waiting X server...
2020-08-30T18:09:29.857856203Z Waiting X server...
2020-08-30T18:09:29.988581706Z
2020-08-30T18:09:29.988614494Z  --- x11vnc loop: 1 ---
2020-08-30T18:09:29.988618411Z
2020-08-30T18:09:30.003580531Z Starting ChromeDriver 85.0.4183.87 (cd6713ebf92fa1cacc0f1a598df280093af0c5d7-refs/branch-heads/4183@{#1689}) on port 4444
2020-08-30T18:09:30.003613265Z All remote connections are allowed. Use a whitelist instead!
2020-08-30T18:09:30.003615890Z Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
2020-08-30T18:09:30.038406309Z ChromeDriver was started successfully.
2020-08-30T18:09:30.489087887Z  --- x11vnc loop: waiting for: 157
2020-08-30T18:09:30.489109215Z
2020-08-30T18:09:30.551036695Z PORT=5900

@pranav165 yeah, starting from this version by default logs are not verbose. In order to enable previous behavior you have to add VERBOSE environment variable using capabilities or browsers.json.

@vania-pooh i am not able to get this to work , could you share the exact command . I am using python and configuration manager https://aerokube.com/cm/latest/

@vania-pooh i am not able to get this to work , could you share the exact command . I am using python and configuration manager https://aerokube.com/cm/latest/

./ cm selenoid start is the command i use to start selenoid . How can i add the "VERBOSE" env variable with CM

./ cm selenoid start is the command i use to start selenoid . How can i add the "VERBOSE" env variable with CM

Worked after setting capability as capabilities["env"] = ["VERBOSE=true"]

Worked after setting capability as capabilities["env"] = ["VERBOSE=true"]


Question about deprecation notice

Hey @anthonymartin curious about the deprecation notice, what is the security vulnerability you refer to?

private keys are not segregated in memory. i suggest to use frame as an alternative as it accomplishes much the same as this original package was intended to do.


404 error at https://www.helium.com/link_wallet

Describe the bug
Trying to link my Helium wallet from the FreedomFi app takes me to a web page that returns a 404 error
To Reproduce
Steps to reproduce the behavior:

Open the FreedomFi app on Android or iPhone
Click "Link with Helium"
Browser tries to open https://www.helium.com/link_wallet?appName=FreedomFi&callbackUrl=freedomfi%3A%2F%2F&requestAppId=com.freedomfi.FreedomFiApp
Browser shows a 404 error.

Expected behavior
Expect to be taken to webpage or wallet, or returned to app to continue the linking process.

Device: Pixel 4a or iPhone SE
OS: Android 13 or iOS 15.6
App Version: FreedomFi 0.0.8, Helium 4.3.2, Helium Wallet 2.0.0

Additional context
Add any other context about the problem here.

Turns out the link is supposed to open the old Helium Hotspot app, and that didn't work on my Android, but it does work on the iPhone once I installed the old wallet there.


Improve the block ray filters

In response to: https://github.com/SpongePowered/SpongeAPI/pull/1342
This adds a skipFilter to ignore blocks that match a predicate. The previous filter functionality gets renamed to stopFilter.
Also, based off of feedback from @Deamon5550, I changed the block limit into a distance limit. Since the filter is now built-in it was removed as a stand-alone.
Finally I fixed the GenericArguments #target functionality not returning the target block, but the air block just before it.
I've fixed Cookbook/Smite and I'll merge those changes if the PR is accepted.
@m0pt0pmatt

Looks good, this is what I intended to do -- thanks for fixing it.

As for the command part I'm not sure if it works 100% but the current #target behaviour is useful for setting blocks / teleporting entities.
Wouldn't changing it to the new behaviour cause it to teleport entities into blocks?
e.g. /makelootcrate #target currently would place a block on top of the block being aimed at, vs the new behaviour which would "bury" the block into the ground?


feat: support classic ingest keys

Which problem is this PR solving?
We've released Ingest Keys, but need to update the key detection logic to allow Ingest Keys to be used to send data to Classic environments.
Short description of the changes

updates the Classic API Key detection logic to understand the shape of a Classic Ingest Key
updates tests with a more comprehensive list of cases

How to verify that this has the expected result
It should be possible to use an ingest key pointed to a classic environment after this change. Please note that the ability to create ingest keys in classic environments isn't yet publicly available (since we need to update this library and others to understand classic ingest keys).

To see the specific tasks where the Asana app for GitHub is being used, see below:

https://app.asana.com/0/0/1206670032965819

wait wtf where did my suggestion go 💀


Added 'split' function similar to the clojure split function

Not sure if it would make sense to support regex matches or not, but raw strings were easiest.

Hi Eliot @eliothedeman,
This looks good. If you would, kindly add a short tests/split.zy to demonstrate and test the new split function.
Thanks!
Jason

Thanks for the feedback so fast!

merged, thanks @eliothedeman


Failed to extract volume information from status_output for Google Nest Hub. Using default volume 5

Is that expected:
2023-07-25 13:20:20.179 WARNING (MainThread) [custom_components.continuously_casting_dashboards.dashboard_caster] Failed to extract volume information from status_output for Google Nest Hub. Using default volume 5.
2023-07-25 13:20:20.182 DEBUG (MainThread) [custom_components.continuously_casting_dashboards.dashboard_caster] Setting volume to 0...
2023-07-25 13:20:25.941 INFO (MainThread) [custom_components.continuously_casting_dashboards.dashboard_caster] Executing the dashboard cast command...
2023-07-25 13:20:31.695 INFO (MainThread) [custom_components.continuously_casting_dashboards.dashboard_caster] Setting volume to 5...
Want to add I've configured volume like:
continuously_casting_dashboards:
logging_level: debug
cast_delay: 45
volume: 4
start_time: "06:30"
end_time: "00:00"
devices:
"Google Nest Hub":
dashboard_url: "http://<IP_ADDRESS>:8123/google-nest/main?kiosk"
I'm using HA version 2023.7.2
continuously_casting_dashboards: 1.2.6

Hey @sebastian-bugajny it looks like you have the volume in the wrong section. Could you remove it from the top of you config and place it inside the 'devices' section for each device? For example here is my config:
  logging_level: debug
  cast_delay: 25
  start_time: "06:00"
  end_time: "02:00"
  devices:
    "Kitchen display":
      dashboard_url: "http://<IP_ADDRESS>:8123/kitchen-dashboard/default_view?kiosk"
      volume: 5
      start_time: "06:00"
      end_time: "03:00"

Hey @b0mbays  I've done exactly like you recommend but still the same
logs:
2023-07-26 09:37:52.541 WARNING (MainThread) [custom_components.continuously_casting_dashboards.dashboard_caster] Failed to extract volume information from status_output for Google Nest Hub. Using default volume 5. 2023-07-26 09:37:52.602 DEBUG (MainThread) [custom_components.continuously_casting_dashboards.dashboard_caster] Setting volume to 0... 2023-07-26 09:37:58.340 INFO (MainThread) [custom_components.continuously_casting_dashboards.dashboard_caster] Executing the dashboard cast command... 2023-07-26 09:38:04.083 INFO (MainThread) [custom_components.continuously_casting_dashboards.dashboard_caster] Setting volume to 40... 2023-07-26 09:38:07.604 WARNING (MainThread) [custom_components.localtuya.common] [bfb...9wy] Failed to connect to <IP_ADDRESS>: [Errno 113] Connect call failed ('<IP_ADDRESS>', 6668) 2023-07-26 09:38:54.855 INFO (MainThread) [custom_components.continuously_casting_dashboards.dashboard_caster] Current local time: 09:38:54.855907 2023-07-26 09:38:54.856 INFO (MainThread) [custom_components.continuously_casting_dashboards.dashboard_caster] Local time is inside the allowed casting time for Google Nest Hub. Start time: 06:30:00 - End time: 00:00:00 2023-07-26 09:39:06.358 INFO (MainThread) [custom_components.continuously_casting_dashboards.dashboard_caster] HA Dashboard (or media) is NOT playing on Google Nest Hub! 2023-07-26 09:39:06.358 INFO (MainThread) [custom_components.continuously_casting_dashboards.dashboard_caster] Casting dashboard to Google Nest Hub 2023-07-26 09:39:06.361 DEBUG (MainThread) [custom_components.continuously_casting_dashboards.dashboard_caster] Executing stop command...
config:
continuously_casting_dashboards:   logging_level: debug   cast_delay: 45   start_time: "06:30"    end_time: "00:00"   devices:     "Google Nest Hub":       dashboard_url: "http://<IP_ADDRESS>:8123/google-nest/main?kiosk"       volume: 4       start_time: "06:30"        end_time: "00:00"

It looks like the device is now being set correctly:
2023-07-26 09:38:04.083 INFO (MainThread) [custom_components.continuously_casting_dashboards.dashboard_caster] Setting volume to 40...
Can you check the device after the cast to see if it is?
The warning about not being able to extract is OK, this is a feature where CCD will try and read the current volume and leave it unchanged after the cast. However some devices are unable to be read so this will always fail.

Is your issue that the casting is not working at all? I see in your log it is trying to cast again after

Yeah it doesn't work at all and based on logs I don't have any more clues what might be wrong.

Can you access the dashboard using the URL on the same network as your hub?
http://<IP_ADDRESS>:8123/google-nest/main?kiosk
What behaviour do you see on the hub too? Do you see a "Dash cast" screen and then it goes off? Or nothing at all.

Yes I can. I'm getting login webpage and after providing creds dashboard is loading. I tried to bypass login by applying
 homeassistant:   external_url: "https://my.external.endpoint"   auth_providers:     - type: trusted_networks       trusted_networks:         - <IP_ADDRESS>/24       trusted_users:         <IP_ADDRESS>: kiosk       allow_bypass_login: true     - type: homeassistant
but after restarting I'm loosing access via external endpoint and internally I can only login to mainenetance mode.

What happens on the Google Hub? What do you see when it is trying to cast?

When I run manually casting via catt like:
catt -d <IP_ADDRESS> cast_site http://<IP_ADDRESS>:8123/google-nest/main?kiosk
It starts casting and I'm getting login webpage for HA

When I replaced device_name: "Google Nest Hub": with it's local IP address: <IP_ADDRESS> it started working

The naming of the Hub might be incorrect (capital letters etc). Can you do a 'catt scan' manually and see what you get?
If you are getting a login screen then that means your trusted users section is not setup correctly. Can you post that from your config?

Yeah I did a scan and name was correct, but it doesn't matter as it works with IP so all good. Problem with trusted users have been also removed and it works like a charm from yesterday ( catt + ha-catt-fix +  continuously_casting_dashboards )/ Thank you for all your help.

Nice, great to hear! No problem


WIP: Path matching guide

Its probably the worst + these are the only options from what I can see in the code.
it should be written somewhere.
@mjackson @ryanflorence or anyone who has any suggestions on how to address this better?

See my comments on #1441

thanks for getting started on this, we'll make sure to include stuff you've got in the docs we're writing right now.


🐛 Biome client: couldn't create connection to server

VS Code version
1.89.1
Extension version
2.2.2
Biome version
1.7.3
Operating system

[X] Windows
[ ] macOS
[ ] Linux

Description
Getting an error in VS Code saying "Biome client: couldn't create connection to server."
The exception:
[Error - 11:25:09 AM] Biome client: couldn't create connection to server.
Error: Command "c:\Users\stian.berg\AppData\Roaming\Code\User\workspaceStorage\326c904ecce485a74a3b80bc6d005353\biomejs.biome\biome.exe __print_socket" exited with code<PHONE_NUMBER>
	at getSocket (c:\Users\stian.berg\.vscode\extensions\biomejs.biome-2.2.2\out\main.js:36605:11)
	at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
	at async createMessageTransports (c:\Users\stian.berg\.vscode\extensions\biomejs.biome-2.2.2\out\main.js:36619:16)
	at async LanguageClient2.createConnection (c:\Users\stian.berg\.vscode\extensions\biomejs.biome-2.2.2\out\main.js:15598:28)
	at async LanguageClient2.start (c:\Users\stian.berg\.vscode\extensions\biomejs.biome-2.2.2\out\main.js:15174:30)
	at async activate (c:\Users\stian.berg\.vscode\extensions\biomejs.biome-2.2.2\out\main.js:36368:3)
	at async h.n (c:\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:143:6281)
	at async h.m (c:\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:143:6244)
	at async h.l (c:\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:143:5701)

Restarting the LSP server doesn't work.
If try to run biome.exe I get this error:
biome.exe: error while loading shared libraries: api-ms-win-crt-heap-l1-1-0.dll: cannot open shared object file
Steps to reproduce

yarn install
install VS extension
open a tsx file

Expected behavior
Expect Biome to start
Does this issue occur when using the CLI directly?
Not sure / Not applicable
Logs
Biome trace is empty

Installed VISUAL C++ REDISTRIBUTABLE FOR VISUAL STUDIO 2019 and restarted PC and it's now working.


Adding Graphs and Bars

Using some libraries to add graphs and bars to the project.

Adding and 'info' button showing how to use those graph features ....

Also Please put some documentations for those graphs...

Please add doc string for every function added by you @saanvibehele and @AayushGupta69.

Added doc strings to the functions :- fcd32b7cf7c8e04c6042975e980900c4bf0d7f83


review use of hibernate jar

The existing license (LGPL) in Hibernate is not compatible with Apache License. I know there is a plan to relicense the Hibernate jar but we can't delay doing an analysis of where we use the Hibernate jar.
It's ok to have a pom dependency on Hibernate jar. The issue is if we ship the jar or classes from it in a binary artifact. I mean any of the files in https://dist.apache.org/repos/dist/release/incubator/kie/10.0.0/
If we do ship the jar in a binary artifact, one workaround would be to omit the jar and provide instructions allowing users ro add the jar themselves.
Would it be possible to do a review before the next RC?

drools had removed hibernate dependencies by https://github.com/apache/incubator-kie-drools/pull/5764
Could someone please review other repos?
optaplanner -> @lucamolteni
kogito-runtimes -> @fjtirado ?
kogito-apps -> @pefernan ?
kie-tools (images, operator) -> @tiagobento @ricardozanini ?
Feel free to involve appropriate persons. Thanks!

@tkobayas @pjfanning
Kogito runtimes do not use JPA but Kogito Apps heavily use it, both for data_index and audit components. Therefore removing JPA is not a viable option without basically redeveloping both components.
On top of that, we recently start using Hibernate classes directly to allow querying ProcessInstance.variables property (which is json column in postgress) in postgresql. See here
Therefore we have two options.

Replace Hibernate by OpenJPA, as was made in Drools (where this is not a problem because there is a JPA transaction manager, but not JPA entities) , and study how to achieve the custom function functionality. After a quick study of the OpenJPA documentation, it seems there might be a way, but as you see the doc is sparse.
Do as as @pjfanning (mainly because Hibernate License will be eventually updated and this will be a temporary fix) proposed. Do not distribute the binary (move the dependency as provided in the pom) and include instructions to add it.

I guess we can try OpenJPA as POC and if it works, go ahead, but @krisv, do we really want to get rid of Hibernate strategically?
In any case, before moving forward, we should wait to discuss the alternatives further.

Do as  @pjfanning (mainly because Hibernate License will be eventually updated and this will be a temporary fix) proposed. Do not distribute the binary (set the dependency as provided in the pom) and include instructions to add it.

It's ok for a pom to link to an LGPL jar(not ideal, but ok). The issue is the zips and tar.gz files in https://downloads.apache.org/incubator/kie/10.0.0/ - these cannot include the LGPL jars. They can include scripts to download the LGPL jars if the jar is needed for the build, with instructions detailing the license issue.
I would also like to highlight fat jars (often these are shaded jars) - these are jars that include many classes including 3rd party classes. If you include LGPL classes in these jars, then you have caused a copyleft issue with that fat jar.
The licensing issue is that you can't ship classes or jars that are LGPL but you can link to jars (eg a pom dependency).

@pjfanning Yes, I got that and that what I proposes. If the dependency scope is provided, everything will compile and tests as it does now but the hibernate jar wont be included in the final binary.
Users will need to add it manually later.
(I want to stress Im assuming this will be temporary till Hibernate folks update their license)

What Im trying to say, beyond the technical point of view and the license legal thing is that this a decision that Im not empowered to take and should be further discussed with a broad audience.


How much workload the databases can handle?

In the documentation it's statet that: "Flynn’s databases are currently designed with staging, testing, development, and small-scale production workloads in mind. They are not currently suitable for storing large amounts of data. We are in the process of making them usable for all use cases, including high volume, large dataset workloads."
I just installed flynn in digital ocean, with 3 nodes (1Gb RAM each) and I'm about to deploy a system that will receive some traffic. In this system I will record a lot of clicks in the database related to a experiment in a big site. When should I be concerned regarding the database workload?

The main limiting factor right now in handling higher throughput workloads is #3425 isn't quite yet done.
There some other concerns regarding write throughput due to replication but they are secondary to being able to scale up resource usage of the databases to match the workload.

Ok. For example, if I would have more then 100 thousand write requisitions per day in the database what would you advise-me to do? Do you think that flynn could hold such a load or should I look for something else as a managed database service?

I am working very hard to get #3425 merged this cycle, it should be on master in just a few days so if you have performance requirements that would require you to tweak database settings running master may be an option.
However if this is a business critical application for now I would suggest using a hosted database option until #3425 is in stable and is battletested.


[Clang importer] Minor tweaks for async imports

Implement two tweaks for the import of async functions:

Don't import as async old APIs that were already deprecated by ~2018. We don't need to improve them.  (rdar://73620586)
Make sure we drop "WithBlock" as a completion-handler suffix.  (rdar://73641827)

@swift-ci please smoke test

@swift-ci please smoke test Linux


Register version 2.5.0

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/100163
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v2.5.0 -m "<description of version>" cdcec79817064723c3959aa263162c7554a0ec06
git push origin v2.5.0

Also, note the warning: Version 2.5.0 skips over 2.0.0
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

Version is updated to 2.5.0


Custom OHLC data style

I'm trying to custom the ohlcv info shown on chart but no success. I found the code below on Legend.vue
{{ohlcv[0]}}
However it seems the t-vue-lspan class has been overridden in some other place than Legend.vue because changing CSS props on this file doesn't reflect on chart. So before to create a new class on this file to customize it, I would like to know if there's any explanation about this behavior.

What do you mean by 'doesn't reflect on chart'?

I mean, if I change any CSS prop on this class and rebuild it, I can't see
changes. In my case I was trying to change font-size and color.
On Sat, 14 Nov 2020 at 03:59 C451<EMAIL_ADDRESS>wrote:

[image: image]
https://user-images.githubusercontent.com/48596328/99141807-e4f5e180-265f-11eb-831f-1aca95bff3f1.png
What do you mean by 'doesn't reflect on chart'?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tvjsx/trading-vue-js/issues/156#issuecomment-727157277,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADRAKW56CBU2G3SLZEVAOH3SPYTD5ANCNFSM4TVGIJKA
.

--
Atenciosamente,
Adson Damasceno

I just tried to change the .t-vue-lspan color in the code and it worked.
And also this is not a specific library issue (there are a lot resources about Vue & css).

I see. If you say it worked I will checkout from github again and rebuild
it. I confess it was weird do not see any changes where it seems pretty
simple (and obvious) code edition.
About being an issue, If this CSS prop wouldn't  have changed the display
behavior of something, why I couldn't consider as an issue? I'm asking to
avoid do this again for similar problems in future.
On Sat, 14 Nov 2020 at 09:21 C451<EMAIL_ADDRESS>wrote:

Closed #156 https://github.com/tvjsx/trading-vue-js/issues/156.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tvjsx/trading-vue-js/issues/156#event-3996380268, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ADRAKW3G5VYRNNR3PCMQDKTSPZY4DANCNFSM4TVGIJKA
.

--
Atenciosamente,
Adson Damasceno

Imagine that tvjs is a black box. If you get bad results manipulating its input - that't a legit issue.
If you enter the box (changing the code) that's an unmaintainable territory.

It makes sense. About the "issue" I cloned the repository, rebuild it, checked the problem persists. I also could see that CSS style from Legend.vue was generated twice on vue build files, so when I was changing in the component CSS code it was always overridden by the default code.

So you mean this is a vue-css issue and not the library issue?

Yeah, it can be duplicated bc you have multiple legends. CSS has a solution for overwriting props, so I think this is ok.
I could use scoped style but that way it would be impossible to overwrite colors on multiple instances.

Ah ok, I will use the CSS solution on my app then. Thanks.


build web issue

i am using flutter 2.0.5, everything is going well,
but when i build web, then it gen a folder named "web", then i :

copy all file in the web folder to nginx root path, then visit with : http://localhost:8080, and it is going good.

then i copy the web folder to the root path, want to visit by : http://localhost:8080/web/ , and it is going not good. i debug in the chorme and it shows:

this is the nginx file:

#user  nobody;
worker_processes  1;

#error_log  logs/error.log;
#error_log  logs/error.log  notice;
#error_log  logs/error.log  info;

#pid        logs/nginx.pid;

events {
    worker_connections  1024;
}

http {
    include       mime.types;
    default_type  application/octet-stream;

    #log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
    #                  '$status $body_bytes_sent "$http_referer" '
    #                  '"$http_user_agent" "$http_x_forwarded_for"';

    #access_log  logs/access.log  main;

    sendfile        on;
    #tcp_nopush     on;

    #keepalive_timeout  0;
    keepalive_timeout  65;

    #gzip  on;

    server {
        listen       8080;
        server_name  localhost;

        #charset koi8-r;

        #access_log  logs/host.access.log  main;

        location / {
            root   html;
			try_files $uri $uri/ /index.php?$args;
            index  index.html index.htm index.php;
        }

        #error_page  404              /404.html;

        # redirect server error pages to the static page /50x.html
        #
        error_page   500 502 503 504  /50x.html;
        location = /50x.html {
            root   html;
        }

        # proxy the PHP scripts to Apache listening on <IP_ADDRESS>:80
        #
        #location ~ \.php$ {
        #    proxy_pass   http://<IP_ADDRESS>;
        #}

		#location /jsw/ {
		#		proxy_pass http://<IP_ADDRESS>:8009/;
		#}
		#location /web {
		#		return 302 http://localhost:8009/;
		#}
		#location /web {
		#		return 302 http://localhost:8009/;
		#}

        # pass the PHP scripts to FastCGI server listening on <IP_ADDRESS>:9000
        #
        location ~ \.php$ {
            root           html;
            fastcgi_pass   <IP_ADDRESS>:8080;
            fastcgi_index  index.php;
            fastcgi_param  SCRIPT_FILENAME  /scripts$fastcgi_script_name;
			fastcgi_param  PATH_INFO $request_uri;
            include        fastcgi_params;
        }

        # deny access to .htaccess files, if Apache's document root
        # concurs with nginx's one
        #
        #location ~ /\.ht {
        #    deny  all;
        #}
    }

    # another virtual host using mix of IP-, name-, and port-based configuration
    #
    #server {
    #   listen       8009;

    #   server_name  localhost:8085/web;

    #    location / {
    #        root   html/web;
    #        index  index.html index.htm;
    #    }
    #}

    # HTTPS server
    #
    #server {
    #    listen       443 ssl;
    #    server_name  localhost;

    #    ssl_certificate      cert.pem;
    #    ssl_certificate_key  cert.key;

    #    ssl_session_cache    shared:SSL:1m;
    #    ssl_session_timeout  5m;

    #    ssl_ciphers  HIGH:!aNULL:!MD5;
    #    ssl_prefer_server_ciphers  on;

    #    location / {
    #        root   html;
    #        index  index.html index.htm;
    #    }
    #}

}

please help thank you

Same issue in here #69760

cool! you solved my problem so fast!


QGIS pdf guide missing, do we want to recreate it

This might not really be an issue so feel free to close it if not.
OSM QGIS page links to a Beginning QGIS pdf:
http://www.learnosm.org/files/beginning-qgis/Beginning_QGIS_en_v1.pdf
But that returns a 404.
I edited the osm wiki and pointed it to the github listing of google docs for beginning qgis.
I am not sure if we want to re-generate the pdf from the existing google docs or not.
Should be easy to do if we think we should.

I think this is at least medium if not high priority, the pdfs are useful. But we need to find out how they were created previously if there was an automated tool.
and we should find out if we can automate their generation from markdown as well as I think gdocs versions will slowly go away as they get converted to markdown.

See issue #269

I think this one can get closed for the more general issue 269 which is pdfs of the whole learnosm site. I added a comment to pass on Nick's information about the conversion previously being from google docs not from the learnosm website or the markdown files.


Keysaw read more gutenberg

Tests and tweaks for #2343

Coverage decreased (-2.4%) to 91.567% when pulling 512612be88be89ccdf575ce27e2ec52d046a59aa on Keysaw-read-more-gutenberg into 88f9e52d2f20c70b5dc315965e1f768b3b8a8b2f on master.


Where statement is missing files when searching for properties

What happened?
In my vault, this DQL below shows only 27 records when I have 45 files with the property "type_note" equals to "knowledge_base"
Tried with other properties, it always misses files.
So what I did is add the tag #kbase to those 45 files, and by changing the DQL to "from #kbase" instead of "where type_note="knowledge_base"" I can now see my 45 files listed.
So to me, doing a request on a property is not showing the real informations.
DQL
table
where type_note="knowledge_base"
sort file.name desc

JS
No response
Dataview Version
0.5.67
Obsidian Version
1.7.7
OS
Windows

What do you get if you do the following query:
```dataview
TABLE
WHERE contains(flat(list(type_note)), "knowledge_base")
SORT file.name desc
```

If this query produces all your files, then it's not a bug but a feature that some of your type_note properties are lists, instead of a single value. The syntax is above is useful to force both single values and lists into a coherent list structure. I found it when needing to query old metadata from before the property update in Obsidian where it was common to intermix properties/fields with either a list or a single value.

In fact, my ‘note_type’ is a list and by using this syntax I can see all my notes!
Thanks a lot!

If they're always a list, and never a single value, that is something: singleValue, you could use contains(yourListProperty, "value") to check whether the list has that value.

Thanks, I prefer the second syntax, easier to understand :-)
By the way, do you know if possible to force no more than a single value on the property?


Installation "invalid image" problem

Installing on cuda11, ubuntu20.04, llvm-11, I'm getting this:
python python/tutorials/01-vector-add.py
...
    name, asm, shared_mem = _triton.code_gen.compile_ttir(backend, generator.module, device, num_warps, num_stages, force_nc_cache)
RuntimeError: CUDA: Error- invalid image

After some investigation, I found files begin generated:
cat /tmp/triton_k_C2Lzfo  | head
//
// Generated by LLVM NVPTX Back-End
//

.version 7.3
.target sm_86
.address_size 64

        // .globl       add_kernel
... more asm ...

and the error is:
ptxas /tmp/triton_k_NjSPTP, line 5; fatal   : Unsupported .version 7.3; current version is '7.1'
ptxas fatal   : Ptx assembly aborted due to errors

That leads me to believe LLVM produces assembly "7.3" that is not supported by my psxas that expects "7.1".
ptxas is part of Cuda, therefore my cuda 11.1.1 is too old?
My goal there is to understand this better and maybe update the installation instructions?

Oh I think you are right that there was a regression recently that made Triton incompatible with CUDA 11.1 :o The most recent version should definitely work with CUDA 11.3+, but definitely this bug should be fixed so that people can use Triton on any CUDA 11+ version

This is resolved. It turns out, when they say in conda pytorch py3.8_cuda11.1_cudnn8.0.5_0 they don't mean exactly 11.1 as I thought, cuda 11.2.2 works just as well.

I think this should be fixed. Please create a new issue for triton 2.0 if not.


Refactor: move serializer variable into dbInfo

Such a change would allow us to make custom drivers DRYer.
Simple drivers could greatly reduce their code and file size by overriding only the different methods and reusing the rest ones. The problem currently is that the serializer is referenced by the closures of the  driver methods. Attaching it to dbInfo would be great.
For example, sessionStorage and CordovaSQLitePlugin drivers would just need to override the _initStorage methods and reuse localStorageWrapper and websqldriver respectively.
Making localforage drivers architecture more object oriented (maybe es6 class based) would be an other step forward.
No PR yet, just discussing. Waiting for other major PRs to merge.

This is an awesome idea.
Agreed, we'll merge some other stuff before tackling it but this is a great idea.

tofumatt

On Fri, Jul 3, 2015 at 5:09 PM, Thodoris Greasidis
<EMAIL_ADDRESS>wrote:

Such a change would allow us to make custom drivers DRYer.
Simple drivers could greatly reduce their code and file size by overriding only the different methods and reusing the rest ones. The problem currently is that the serializer is referenced by the closures of the  driver methods. Attaching it to dbInfo would be great.
For example, sessionStorage and CordovaSQLitePlugin drivers would just need to override the _initStorage methods and reuse localStorageWrapper and websqldriver respectively.
Making localforage drivers architecture more object oriented (maybe es6 class based) would be an other step forward.
No PR yet, just discussing. Waiting for other major PRs to merge.
Reply to this email directly or view it on GitHub:
https://github.com/mozilla/localForage/issues/398


OnInitialise doesn't work

<link rel="stylesheet" type="text/css" href="https://cdnjs.cloudflare.com/ajax/libs/cookieconsent2/3.0.3/cookieconsent.min.css" />
    <script src="https://cdnjs.cloudflare.com/ajax/libs/cookieconsent2/3.0.3/cookieconsent.min.js"></script>
    <script>
        window.addEventListener("load", function() {
            var defaultColor =  "#00a0fc";
            window.cookieconsent.initialise({
                "palette": {
                    "popup": {
                        "background": defaultColor,
                        "text": "#ffffff"
                    },
                    "button": {
                        "background": "#ffffff",
                        "text": defaultColor
                    }
                },
                "type": "opt-in",
                "content": {
                    "message": 'This website uses cookies to ensure you get the best experience.',
                },
                "position": "top",
                "static": true,
                "onInitialise": function (status) {
                    console.log('onInitialise ' + status);
                },
            });
        });
    </script>

I've never seen onInitialise on my log, but banner opens

It only gets executed if the cookie has been set.  It's a poor name for the callback.

@nobleclem in the documentation it says it's supposed to always be called:
https://cookieconsent.insites.com/documentation/javascript-api/

This is called on start up, with the current chosen compliance. It can be used to tell you if the user has already consented or not as soon as you initialise the tool.

I agree, the callback is poorly named / documented. These are some great suggestions though. I don't think we should change the name as that would require existing usages to change their code. One  solution is to just call onInitialise all the time (as implied by the name onInitialise).
The function is currently called with the cookie status. I.E. 'allow' | 'deny' | 'dismiss'. Should it just be called with undefined if not selected? I'm not sure how that would affect backwards compatibility.
Maybe it'd just be better to have a new hook altogether that is called if no answer has been given? I think this option is the best for BC, but the naming would probably be confusing, because we'd have an onInitialise thats only called when answered, and a onUnanswered callback.
Maybe we should just define two new hooks, onAnswered and onUnanswered and deprecate the onInitialise function?
Thoughts?

@alexmorleyfinch I agree with your thoughts and like your last suggestion (deprication and using new names).

onInitialise is needed to bind the popup instance to a variable so that later we can use the revokeChoice() method. Please don't deprecate!

There's now a onNoCookieLaw hook.
See thread.


how to clear conversation?

Describe the feature
i used three accounts to use this api and the chatgpt timeout error occurs sometimes. I wonder if this error was caused by too many conversations(threads). Can this be solved in some way or how to clear the conversations?

What do you mean "clear conversation"? If you need send request without conversationId and parentId, you can just run await api.sendMessage('Hello World!'), if you need reset browser, use initSession.
If you get timeout error casually, it maybe openAI server is on the heavy balance.
If you use this api in huge request, you should low your request to 50 in 1 hour.

I don't think that too many conversation threads is an issue from my pretty thorough testing.
As @Glowin mentioned, if you want to create a new thread, just don't pass conversationId and parentMessageId.


Feature_Request in README.md

Describe the feature you are requesting

Hello Sir,
I want to add some cool badges in this repo like

open issues
contributor
open PR
last commites
this type of cool API badges
It will be very helpful to showcase the stats of your Repo as well as will attract more contributors.
Additional context(if any)

Are you contributing under any open-source program ?

APERTRE'24

@rko0211 Please assign me this issue under APERTRE'24

OK go @apu52


Configuration management

wis2box moving from static yaml config files to an elasticsearch database
Retrieve configurations from different systems - e.g. make api call to get data source config to understand how to import
How to interact with external configuration management systems may be used instead (e.g. see <IP_ADDRESS>)

todo

[ ] Backend storage, possible ES (shared with wis2box)
[ ] generic way to configure processes (e.g. scheduling) - does this still exist in OGC API - Processes? A scheduling capability used to exist in WPS 2.0
[ ] define inputs and outputs

Figma software (used in Surface) may be helpful for layout of admin UI layout.


TimberMenu and WPML

Hi I have question about TimberMenu and WPML
I have created following menu in WP
Main Navigation and Main Navigation - English (sinced by WPML), default language german
In twig menu is rendered from variable
$mainMenu = new \TimberMenu('main-navigation');
German menu is correct and coresponds to BE menu (see structure),
BE menu

Home
Page #1
Page #2

FE menu

Home
Page #1
Page #2

but if I switch page to English (I have translated only Home)
BE menu EN

Home EN

FE menu EN

Home EN
Page #1
Page #2
Page #3
Page #4

Very vierd behaviour, Don't you thing?
It is problem only if page translations not exists.
but if I switch menu for EN
$mainMenu = new \TimberMenu('main-navigation-english');
menu on english page is correct and only Home page link shows up in menu
How can I get menu for all languages without need to get each menu separately by menu slug and do not display not translated pages
Installed latest version of WordPress and Timber via composer (using https://wpackagist.org/)

In the past I've loaded the correct menu by ID, depending on the current language selected:
	    // Load Menu depending on current language
	    $context['language'] = ICL_LANGUAGE_CODE;

	    // Menu ID : Default to English
	    $menuID = 2;

	    switch(ICL_LANGUAGE_CODE) {
		    case 'en':
		    	$menuID = 2;
		    	break;
		    case 'fr':
		    	$menuID = 9;
		    	break;
		    case 'ja':
		    	$menuID = 11;
		    	break;
		    case 'de':
		    	$menuID = 10;
		    	break;
		    case 'es':
		    	$menuID = 8;
		    	break;
	    }

    	$context['menu'] = new TimberMenu($menuID);

Funny, I ran into this exact same issue today and was going to report it. Like @addedlovely said using the ID works as a backup, but creating a TimberMenu by supplying the location slug always returns the default language menu instead of the translated one.

Yes solution by @addedlovely works as workarround.
But I thing it should be automatic. imho
When the client adds new language you have to add new menu config

Hi guys,
We are aware of various improvements that could be made with 3rd party plugins and the like, as we are approaching a 1.0 release, those improvements will be on the back burner for a little while. However once we are on 1.0 we can focus on improving our compatibility with popular plugins, such as WPML
Thanks,
Connor

@ogrosko Weird I have similar setup:
$context['menu'] = new TimberMenu('top-bar-r');
And it looks like works nice. I din't sync menu with 'WP Menus Sync'. Make sure you translate all pages that you need in menu.

@orest22 Oh I forgot to mention it
When pages has localizations it works with no problems.
It is problem only if page localization not exists

Any news about this?

Not yet unfortunately, working through a backlog of post 1.0.0 fixes at the moment.

Bump

Hopefully this helps a few of you!
https://github.com/timber/timber/pull/1414/commits/5befe275047ef03a7901cb562a6fb6991cfac927

@ogrosko from what I see this should be fixed. If so, please close the issue.
As this is a bit old issue we'll close in case of no response in two weeks.


Encoding problem with python 2.7

I am not sure why but I am unable to use this module because of the error- "SyntaxError: encoding problem: future_fstrings. I have python 2.7 on my machine.

How did you install future-fstrings? can you provide more information (your file contents, etc.)

I did a pip install.
FstringTest.txt

Can you python -m pip freeze --all?

Alright got it working. Thanks for the help.

what was your solution?


Lazy instantiation in TokenValidationParameters

TokenValidationParameters has this public IDictionary<string, object> InstancePropertyBag { get; } = new Dictionary<string, object>();. Can that be lazily instantiated? I don’t see any other code in the repo (beyond tests) using InstancePropertyBag, yet every TokenValidationParameters being constructed is creating this dictionary instance.

https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/releases/tag/7.0.0-preview2


zef: 0.11.4 -> 0.11.5

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/ugexe/zef/releases.
meta.description for zef is: "Raku / Perl6 Module Management"
meta.homepage for zef is: "https://github.com/ugexe/zef"
meta.changelog for zef is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 0.11.5 with grep in /nix/store/gd555gq6s1h6rpbhmxm946bksz2964h9-zef-0.11.5

directory tree listing: https://gist.github.com/446c4ac43bb339b6245489131b38e092

du listing: https://gist.github.com/592ed5d72e69849572d8c213c1191bfa

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
zef

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/gd555gq6s1h6rpbhmxm946bksz2964h9-zef-0.11.5 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A zef https://github.com/r-ryantm/nixpkgs/archive/1ab22af205f148a309b38eb4df3d482fb923c201.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/gd555gq6s1h6rpbhmxm946bksz2964h9-zef-0.11.5
ls -la /nix/store/gd555gq6s1h6rpbhmxm946bksz2964h9-zef-0.11.5/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

zef

Maintainer pings
cc @stigtsp for testing.

Result of nixpkgs-review pr 116234 at 1ab22af2 run on aarch64-linux 1

1 package built successfully:

zef

1 suggestion:

warning: missing-phase-hooks
installPhase should probably contain runHook preInstall and runHook postInstall.
Near pkgs/development/interpreters/rakudo/zef.nix:17:3:
   |
17 |   installPhase = ''
   |   ^

ping @stigtsp


PDF renderer in @egorpugin (unofficial) VC2015 build

@egorpugin

Try these binaries compiled by me.
https://www.dropbox.com/s/8t54mz39i58qslh/tesseract-3.05.00dev-win32-vc19.zip?dl=1
You have to install VC2015 x86 redist from microsoft.com in order to run them.
Leptonica is built with all libs except for libjp2k.

@nickbe

This build does not create PDFs, but the cygwin from http://3.onj.me/tesseract/ build does.
So currently the VS build is not usable.

@jbreiden

What is this business about certain builds not supporting PDF output? There is nothing special or weird with that section of code. Are they just old builds from before the feature was created, or is there something else going on?

@egorpugin

Is there a simple command to check pdf generation?
I'll try to debug the issue (if any).

@egorpugin
tesseract /path/to/phototest.tif phototest pdf

https://github.com/tesseract-ocr/tesseract/blob/master/testing/phototest.tif

These traineddata files are required: eng, osd

Ok, and how should I understand what is incorrect? Where is tesseract output, error message, anything?
Entered this command, did some preparations and pdf is generated.
Works for me.
Latest binaries are here: https://www.dropbox.com/s/pxu2hp6mg1a64zj/tesseract-3.05.00dev-win32-vc19-2016-jun-03.zip?dl=1

The other binaries simply didn't create a PDF.
But this one in fact does.
So, there's something wrong with the other VC builds.
Am Sa., Jun. 4, 2016 16:07 schrieb Egor Pugin : Ok, and how should I understand what is incorrect? Where is tesseract output, error message, anything?
Entered this command, did some preparations and pdf is generated.
Works for me.
Latest binaries are here: https://www.dropbox.com/s/pxu2hp6mg1a64zj/tesseract-3.05.00dev-win32-vc19-2016-jun-03.zip?dl=1 (https://www.dropbox.com/s/pxu2hp6mg1a64zj/tesseract-3.05.00dev-win32-vc19-2016-jun-03.zip?dl=1)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub (https://github.com/tesseract-ocr/tesseract/issues/338#issuecomment-223757480), or mute the thread (https://github.com/notifications/unsubscribe/AKYuDajKHXrqZUACFMgTwB900UjD9EKmks5qIYZ_gaJpZM4ItVrv).

@egorpugin
How did you build these two (old and new) binaries?

Built liblept with every image library except jpeg2k, built tesseract with that lept. VS2015 Update 2.
I said that in previous thread (issue).
If tesseract.exe creates pdfs and other binaries not, give me simple repro for one of them, so I'll check.

Since the problem does not exist in your newer build, maybe we should close this issue.

It works also on the old build. I checked.

Do you have any guess why it does not work for @nickbe (the old build)?

Nobody wants to provide simple repro of this issue. I cannot guess what's the problem.

I don't have Windows so I can't reproduce it myself...

@amitdo: I didn't build any of these myself. I just followed download links and tried the various latest versions I found. Only thing I can say is that the mingW version worked, that the VC version from your link didn't and that the one from the link above works.

Since both @nickbe and @egorpugin confirm that the PDF renderer feature works in the newer VC build, I'm closing this issue for now.


[Avatar] backgroundColor from string

Closes #12700

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

Should we have a doc for this? or just mention it in the content

Should we have a doc for this? or just mention it in the content

@Vikram710 This is the single most important part. I have pushed a new demo with it. Regarding the actual implementation. I'm not sure what would be best. We have 3 options. 1. demo only 2. a unity function that can be imported 3. a backed-in feature. My concern with 3. is that we force bundle size for developers that have been living find without so far.

@mnajdova Ok, in this case, it's an easy one, merging :)


YARN-11418. Add a new metric that reflects the number of applications whose FinalStatus is FAILED

YARN-11418: Add a new metric that reflects the number of applications whose FinalStatus is FAILED

Description of PR
We are faced with a scenario where the State of the application is FINISHED, but the FinalStatus is FAILED. When the FinalStatus of the application is FAILED, we want to show that through metrics.
How was this patch tested?
create an Application whose FinalStatus is  FAILED, and verify that metrics in JMX are as expected. By the way, the metric is also added to the YARN WebUI.
For code changes:

[ ] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m  2s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
markdownlint
0m  0s

markdownlint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 10 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
14m 40s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
31m 53s

trunk passed

+1 :green_heart:
compile
10m  5s

trunk passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
compile
8m 37s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
checkstyle
1m 47s

trunk passed

+1 :green_heart:
mvnsite
2m 36s

trunk passed

-1 :x:
javadoc
1m  6s
/branch-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt
hadoop-yarn-server-resourcemanager in trunk failed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.

+1 :green_heart:
javadoc
1m 55s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+0 :ok:
spotbugs
0m 29s

branch/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site no spotbugs output file (spotbugsXml.xml)

+1 :green_heart:
shadedclient
23m  6s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 28s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 44s

the patch passed

+1 :green_heart:
compile
9m 26s

the patch passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
javac
9m 26s

the patch passed

+1 :green_heart:
compile
8m 34s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
javac
8m 34s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
1m 36s
/results-checkstyle-hadoop-yarn-project_hadoop-yarn.txt
hadoop-yarn-project/hadoop-yarn: The patch generated 11 new + 688 unchanged - 3 fixed = 699 total (was 691)

+1 :green_heart:
mvnsite
2m 23s

the patch passed

-1 :x:
javadoc
0m 55s
/patch-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt
hadoop-yarn-server-resourcemanager in the patch failed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.

+1 :green_heart:
javadoc
1m 56s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+0 :ok:
spotbugs
0m 31s

hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site has no data from spotbugs

+1 :green_heart:
shadedclient
24m 21s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
103m 45s
/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager.txt
hadoop-yarn-server-resourcemanager in the patch passed.

+1 :green_heart:
unit
0m 48s

hadoop-yarn-server-router in the patch passed.

+1 :green_heart:
unit
0m 34s

hadoop-yarn-site in the patch passed.

+1 :green_heart:
asflicense
0m 57s

The patch does not generate ASF License warnings.

268m 51s

Reason
Tests

Failed junit tests
hadoop.yarn.server.resourcemanager.webapp.TestNodesPage

hadoop.yarn.server.resourcemanager.scheduler.TestQueueMetrics

hadoop.yarn.server.resourcemanager.webapp.TestRMWebServices

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5306/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5306

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets markdownlint

uname
Linux ba30a93ff42d 4.15.0-200-generic #211-Ubuntu SMP Thu Nov 24 18:16:04 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / ff0220ed3cc94e721d5f43a3b33167fb9ce506d2

Default Java
Private Build-1.8.0_352-8u352-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_352-8u352-ga-1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5306/2/testReport/

Max. process+thread count
929 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-router hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site U: hadoop-yarn-project/hadoop-yarn

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5306/2/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 52s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+0 :ok:
markdownlint
0m  1s

markdownlint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 11 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
15m  0s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
30m 47s

trunk passed

+1 :green_heart:
compile
9m 39s

trunk passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
compile
8m 29s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
checkstyle
1m 55s

trunk passed

+1 :green_heart:
mvnsite
2m 45s

trunk passed

-1 :x:
javadoc
1m 11s
/branch-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt
hadoop-yarn-server-resourcemanager in trunk failed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.

+1 :green_heart:
javadoc
2m 18s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+0 :ok:
spotbugs
0m 37s

branch/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site no spotbugs output file (spotbugsXml.xml)

+1 :green_heart:
shadedclient
23m 37s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 28s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 48s

the patch passed

+1 :green_heart:
compile
9m  8s

the patch passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
javac
9m  8s

the patch passed

+1 :green_heart:
compile
8m 33s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
javac
8m 33s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
1m 42s
/results-checkstyle-hadoop-yarn-project_hadoop-yarn.txt
hadoop-yarn-project/hadoop-yarn: The patch generated 3 new + 694 unchanged - 3 fixed = 697 total (was 697)

+1 :green_heart:
mvnsite
2m 29s

the patch passed

-1 :x:
javadoc
0m 56s
/patch-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt
hadoop-yarn-server-resourcemanager in the patch failed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.

+1 :green_heart:
javadoc
2m  1s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+0 :ok:
spotbugs
0m 32s

hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site has no data from spotbugs

+1 :green_heart:
shadedclient
23m 22s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
106m 34s
/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager.txt
hadoop-yarn-server-resourcemanager in the patch passed.

+1 :green_heart:
unit
0m 45s

hadoop-yarn-server-router in the patch passed.

+1 :green_heart:
unit
0m 27s

hadoop-yarn-site in the patch passed.

+1 :green_heart:
asflicense
0m 57s

The patch does not generate ASF License warnings.

270m 33s

Reason
Tests

Failed junit tests
hadoop.yarn.server.resourcemanager.webapp.TestNodesPage

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5306/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5306

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets markdownlint

uname
Linux fe35bdd0ab73 4.15.0-200-generic #211-Ubuntu SMP Thu Nov 24 18:16:04 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 2fc1d60e8bf365513121018a63a2b5778971c012

Default Java
Private Build-1.8.0_352-8u352-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_352-8u352-ga-1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5306/3/testReport/

Max. process+thread count
959 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-router hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site U: hadoop-yarn-project/hadoop-yarn

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5306/3/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

@ashutoshcipher Hello, can you help me to review my commits? Thank you very much.


feat: Add className prop to Toast

Description
The issue is related to https://openedx.atlassian.net/browse/VAN-906 where two toasts are appearing (one for the component that renders when desktop view is on and other for Mobile view)
The classes added to parent components in prospectus that dynamically show and hide the content d-block d-md-none and d-none d-md-block don't work on any children Toast elements. Adding a div with these classes around Toast also doesn't work.
Solution:
Added a span around BaseToast which takes className as props. This doesn't change the appearance of Toast.
Deploy Preview
Include a direct link to your changes in this PR's deploy preview here (e.g., a specific component page).
Merge Checklist

[ ] If your update includes visual changes, have they been reviewed by a designer? Send them a link to the Netlify deploy preview, if applicable.
[ ] Does your change adhere to the documented style conventions?
[ ] Do any prop types have missing descriptions in the Props API tables in the documentation site (check deploy preview)?
[ ] Were your changes tested using all available themes (see theme switcher in the header of the deploy preview, under the "Settings" icon)?
[ ] Is there adequate test coverage for your changes?
[ ] Consider whether this change needs to reviewed/QA'ed for accessibility (a11y). If so, please add wittjeff and adamstankiewicz as reviewers on this PR.

Post-merge Checklist

[ ] Verify your changes were released to NPM at the expected version.
[ ] If you'd like, share your contribution in #show-and-tell.
[ ] 🎉 🙌 Celebrate! Thanks for your contribution.

@adamstankiewicz This is code where both mobile and desktop version of course about pages are rendered in the DOM at the same time. They are dynamically shown/hidden based on the classes d-block d-md-none, d-none d-md-block added to these components. However the Toast in the children of these components doesn't adhere by these classes and appears twice.

@adamstankiewicz This is code where both mobile and desktop version of course about pages are rendered in the DOM at the same time. They are dynamically shown/hidden based on the classes d-block d-md-none, d-none d-md-block added to these components. However the Toast in the children of these components doesn't adhere by these classes and appears twice.

@zainab-amir Great, thanks for this context.
While I think this PR is worthwhile regardless, I think a potentially more optimal solution to your problem might be to not rely on display properties to determine whether CoursePage or CoursePageMobile gets rendered. Each is still rendered in the DOM (and doing all its underlying logic, like showing Toast) even if it's not visible in the UI.
I might recommend exploring conditionally rendered the CoursePage or CoursePageMobile component based on a screen width as it relates to a breakpoint instead. That way, only one of them is truly rendered in the DOM at any given time.
Example:
import { useMediaQuery, breakpoints } from '@edx/paragon';

const CoursePageResponsive = () => {
  const isDesktop = useMediaQuery({
    query: `(min-width: ${breakpoints.medium.minWidth}px)`
  })
  if (isDesktop) {
    return <CoursePage />;
  }
  return <CoursePageMobile />;
};

:tada: This PR is included in version 19.14.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Hotchocolate v14 Persisted Query Id - backwards compatibility option

Product
Hot Chocolate
Is your feature request related to a problem?
Apologies if I am missing something in the docs, the migration guide to v14, or just general graphql understanding.
I am seeing a breaking change with persisted queries in version 14 of HotChocolate and would love a simple way to override the way query Ids are managed to enable backwards compatibility. This would make upgrading easier and would not affect calling clients (which is a blocker to me for upgrading)
In v13 I am able to store persisted queries (in my case using filesystem) in a file say "query1.graphql".
Then issue the request:
{
  "id": "query1",
  "variables": {
    "somevar": 12345
  }
}

Upgrading to v14 this query now gets the response
{
    "errors": [
        {
            "message": "Invalid query id format."
        }
    ]
}

Is this expected? Reading the docs, the Id passed in by clients should be the query hash. But in my use case calling clients use specific named queries as above. So how if 13 is already in use and calling clients cannot be easily changed, how do I migrate?
The solution you'd like
Ideally some way to override this behaviour and implement the behaviour to map the query id passed in to a stored query (in my file storage example it would map to the file name).
If this is possible and I have missed it, then I guess I am asking for a change to the upgrade guide or persisted queries documentation to explain how.

The ID you posted would still be valid. What actual value did you pass?

Ah, could this be because the name has invalid characters? Not sure why I didn't think of that sorry!
The value includes characters "(", ")" and "," i.e. "name(data1,data2,data2)"
Are there any characters that would be rejected through HotChocolate validation, but would be valid characters in a file name?

Yes, we now validate the name for security reasons, as when you map the name 1:1 to a file it provides an attack vector. So, now we in the transport layer already reject names that do not fit the following: a-z A-Z 0-9 - _
Other characters are not allowed as an operation ID. There is also no way around this as we have now a typed operation id struct which ensures that it cannot even passed into the execution engine if it does not fit the pattern.

Thanks for explaining, this makes sense now.
I will have a think how to migrate people over to new names. Thanks for the quick responses.


serving/xrefs: allow a single level of indirection in the documentation serving data [phab:D2002]

Created by schroederc at 2017-10-31 18:23:10:

schroederc wrote at 2017-10-31 18:30:00:
Replace the ticket of the subsuming document

schroederc wrote at 2017-10-31 19:03:11:
Ensure subsuming documentation has the original Document's Node

shahms accepted this revision at 2017-10-31 19:28:22

schroederc closed via commit dd1cbcdfafd54e003bac825ea7745d58aa7947e1 at 2017-10-31 19:30:57


Wrapping results in Hashie::Mash 3.5.1 causes logs to be flooded with warnings

Originally opened on the wrong repo: https://github.com/elastic/elasticsearch-ruby/issues/398
I updated our bundle today which included<EMAIL_ADDRESS>and found our logs are now completely overwhelmed with warnings:
WARN -- : You are setting a key that conflicts with a built-in method Hashie::Mash#sort defined in Enumerable. This can cause unexpected behavior when accessing the key via as a property. You can still access the key via the #[] method.

I believe this is being caused by the "sort" key that comes back in the response body. eg: "sort":[1.121931762,1477653971450]. If I remove any use of sort from the query the warnings go away.
we're doing our searching via elasticsearch/persistence/repository if that has any bearing on things
I suspect it's related to this PR: https://github.com/intridea/hashie/pull/381. I don't have a good suggestion how it might be fixed other than to stop using Hashie, but that seems like a pretty large change.

Moved from https://github.com/elastic/elasticsearch-ruby/issues/398

Yes, this will be tricky to solve, because Hashie::Mash is used as a "freeform" wrapper around deeply structured Hashes coming from Elasticsearch, enabling method access to the structures.
On the original ticket, @gfx suggested using Struct. That would be technically possible, I guess, but crazily obnoxious -- Hashie::Mash is used as a "free-form" wrapper around Hashes coming from Elasticsearch, no matter which internal structure they have, and when using Struct, we would have to define the structure first.
Using OpenStruct would seem as a workable replacement for Hashie::Mash, because you can pass a Hash to it and it will create method accessors. However, this does not apply to an embedded Hash:
o = OpenStruct.new foo: 'bar', moo: { koo: 'loo' }
o.foo
# => "bar"
o.moo
# => {:koo=>"loo"}
o.moo.koo
NoMethodError: undefined method `koo' for {:koo=>"loo"}:Hash

And so this is problematic, because what we do almost always is something like response.aggregations.mytags.buckets.first.etc.etc.etc.
Let's keep the issue open, and let's gather feedback.
What should work is to somehow wrap Hashie::Mash in another class, and define the offending method there -- but I can't go checking the source now.

Workaround for now, setting
Hashie.logger = Logger.new('/dev/null')

in an initializer silences that output.

I released Hashie 3.5.2 today that should allow you to more easily handle this.
As @zealot128 said, if you subclass Mash you can access the new disable_warnings method to disable warnings. I would recommend bumping the Hashie requirement to 3.5.2+ to make it so you don't have to do the torturous method that I used in OmniAuth due to their supporting old versions of Hashie.
Please let me know if I can be of assistance on this.

Hi Michael, many thanks for the info! I think we will go through the subclass route, using the disable_warnings method you've pointed out.
I've also tried some sketches with more acrobatics to remove the sort key from the arguments being passed to initializer, so we bypass the warnings on older versions, but had to abandon it for a while. I'll post the code here if I'm successful later.
(Regarding bumping the requirement, I'm usually very conservative with that, notably for popular libraries like Hashie, because you never know what other gems are people using, and a strict requirement might very easily put them into an un-resolvable gem version specification...)
Thanks again!

@lparry, thanks for the initial report and debug info!
@michaelherold, many thanks for the pointers and the quick release of a fixed version!
I've added a HashWrapper subclass in 5732fa3, and used it as the wrapper across the elasticsearch-model and elasticsearch-persistence gems. As I've said, I've not defined the version requirement because of worries it might get people into dependency hell situations. I guess most people will upgrade Hashie to the fixed version sooner than later anyway.
Please try out the version in master, it should be quiet now.

That looks good, @karmi! The only versions of Hashie where that won't fully fix the problem are 3.5.0 - 3.5.2. The new 3.5.3 will handle that fine. There were a bunch of hurdles to jump because we didn't have good integration tests in place. Hopefully, that won't cause too many issues since most version constraints that get people to 3.5.x will allow them to get to 3.5.3 without trouble.
I'll add it to the to-do list to get integration tests in place for the Elastic gems since I know a lot of people transitively use Hashie through your projects.
Please let us know if you run into any more trouble!

I've tested master against our codebase and this does appear to fix the excessive logging. thanks! any chance you could push a 0.1.10 version of the elasticsearch-persistence gem up to rubygems when  you get a chance please?

Hi, will the fix to be released?


i18n(ko-KR): update endpoints.mdx

Description (required)

update endpoints.mdx
#9240

Related issues & labels (optional)

Closes #
Suggested label:

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File
Note

ko/guides/data-fetching.mdx
Localization changed, will be marked as complete.

ko/guides/dev-toolbar.mdx
Localization changed, will be marked as complete.

ko/guides/endpoints.mdx
Localization changed, will be marked as complete.

ko/guides/testing.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

Once #10226, #10166 are merged, I expect to be able to merge this PR successfully.


Excel File download triggered by a button click in headless mode not working

Steps to reproduce
Tell us about your environment:

Puppeteer version: 1.4.0
Node.js version: 8.10.0

What steps will reproduce the problem?
I'm trying to do a file download(excel file) from my page, triggered by a button click, in 'headless : true' mode, using the below code,
await page._client.send('Page.setDownloadBehavior', {behavior: 'allow', downloadPath: './downloadFolder'});
And its seems it didn't do anything, file is not getting downloaded.
The same worked if i change that to 'headless : false' (downloads to chrome's download directory), also it works even without this code.

There's no good way to download files atm; see #299.


TestMultipleGet is racy

Sometimes fail on CI with output:
=== RUN   TestMultipleGet
{"level":"error","error":"No state for /1623943149477: datastore: key not found","time":"2021-06-17T15:19:10Z","message":"attempting to configure data store"}
2021-06-17T15:19:10.488Z	ERROR	fsm	fsm/fsm.go:92	Executing event planner failed: Invalid transition in queue, state `0`, event `4`:
    github.com/filecoin-project/go-statemachine/fsm.eventProcessor.Apply
        /home/runner/go/pkg/mod/github.com/filecoin-project/go-statemachine@v0.0.0-20200925024713-05bd7c71fbfe/fsm/eventprocessor.go:137
2021-06-17T15:19:10.489Z	ERROR	fsm	fsm/fsm.go:92	Executing event planner failed: Invalid transition in queue, state `0`, event `4`:
    github.com/filecoin-project/go-statemachine/fsm.eventProcessor.Apply
        /home/runner/go/pkg/mod/github.com/filecoin-project/go-statemachine@v0.0.0-20200925024713-05bd7c71fbfe/fsm/eventprocessor.go:137
{"level":"error","error":"No state for /1623943149478: datastore: key not found","time":"2021-06-17T15:19:10Z","message":"attempting to configure data store"}
2021-06-17T15:19:10.499Z	ERROR	fsm	fsm/fsm.go:92	Executing event planner failed: Invalid transition in queue, state `0`, event `4`:
    github.com/filecoin-project/go-statemachine/fsm.eventProcessor.Apply
        /home/runner/go/pkg/mod/github.com/filecoin-project/go-statemachine@v0.0.0-20200925024713-05bd7c71fbfe/fsm/eventprocessor.go:137
2021-06-17T15:19:10.500Z	ERROR	fsm	fsm/fsm.go:92	Executing event planner failed: Invalid transition in queue, state `0`, event `4`:
    github.com/filecoin-project/go-statemachine/fsm.eventProcessor.Apply
        /home/runner/go/pkg/mod/github.com/filecoin-project/go-statemachine@v0.0.0-20200925024713-05bd7c71fbfe/fsm/eventprocessor.go:137
2021-06-17T15:19:10.512Z	ERROR	gs-traversal	runtraversal/runtraversal.go:43	failed to load link=bafy2bzacecddt5b3fodntlgkrtin6nj6ybrflotjzcpqutw4zgxdpk73lfnnk, nBlocksRead=0, err=blockstore: block not found
2021-06-17T15:19:10.512Z	ERROR	gs-traversal	runtraversal/runtraversal.go:32	traversal completion check failed, nBlocksRead=0, err=skip
    node_test.go:623:
        	Error Trace:	node_test.go:623
        	            				popn.go:280
        	            				popn.go:697
        	            				popn.go:752
        	            				node_test.go:626
        	Error:      	Not equal:
        	            	expected: ""
        	            	actual  : "context deadline exceeded"

        	            	Diff:
        	            	--- Expected
        	            	+++ Actual
        	            	@@ -1 +1 @@
        	            	-
        	            	+context deadline exceeded
        	Test:       	TestMultipleGet

Adding additional logs:
=== RUN   TestMultipleGet
{"level":"info","time":"2021-07-09T09:03:39Z","message":"starting query"}
{"level":"info","time":"2021-07-09T09:03:39Z","message":"waiting for triage"}
{"level":"info","time":"2021-07-09T09:03:39Z","message":"selected an offer"}
{"level":"info","time":"2021-07-09T09:03:39Z","message":"started transfer"}
{"level":"error","error":"No state for /1625821418797: datastore: key not found","time":"2021-07-09T09:03:39Z","message":"attempting to configure data store"}
2021-07-09T09:03:39.805Z	ERROR	fsm	fsm/fsm.go:92	Executing event planner failed: Invalid transition in queue, state `0`, event `4`:
    github.com/filecoin-project/go-statemachine/fsm.eventProcessor.Apply
        /home/runner/go/pkg/mod/github.com/filecoin-project/go-statemachine@v0.0.0-20200925024713-05bd7c71fbfe/fsm/eventprocessor.go:137
2021-07-09T09:03:39.805Z	ERROR	fsm	fsm/fsm.go:92	Executing event planner failed: Invalid transition in queue, state `0`, event `4`:
    github.com/filecoin-project/go-statemachine/fsm.eventProcessor.Apply
        /home/runner/go/pkg/mod/github.com/filecoin-project/go-statemachine@v0.0.0-20200925024713-05bd7c71fbfe/fsm/eventprocessor.go:137
{"level":"info","time":"2021-07-09T09:03:39Z","message":"finished transfer"}
{"level":"info","time":"2021-07-09T09:03:39Z","message":"starting query"}
{"level":"info","time":"2021-07-09T09:03:39Z","message":"waiting for triage"}
{"level":"info","time":"2021-07-09T09:03:39Z","message":"selected an offer"}
{"level":"info","time":"2021-07-09T09:03:39Z","message":"started transfer"}
{"level":"error","error":"No state for /1625821418798: datastore: key not found","time":"2021-07-09T09:03:39Z","message":"attempting to configure data store"}
{"level":"info","time":"2021-07-09T09:03:39Z","message":"finished transfer"}
{"level":"info","time":"2021-07-09T09:03:39Z","message":"starting query"}
{"level":"info","time":"2021-07-09T09:03:39Z","message":"waiting for triage"}
{"level":"info","time":"2021-07-09T09:03:39Z","message":"selected an offer"}
{"level":"info","time":"2021-07-09T09:03:39Z","message":"started transfer"}
2021-07-09T09:03:39.819Z	ERROR	gs-traversal	runtraversal/runtraversal.go:43	failed to load link=bafy2bzacedyrtucitacchlrjaikx7gymcuk4iw3q7sldemdbkeaszqhcihuz2, nBlocksRead=0, err=blockstore: block not found
2021-07-09T09:03:39.820Z	ERROR	gs-traversal	runtraversal/runtraversal.go:32	traversal completion check failed, nBlocksRead=0, err=skip
    node_test.go:701:
        	Error Trace:	node_test.go:701
        	            				popn.go:327
        	            				popn.go:815
        	            				popn.go:887
        	            				node_test.go:704
        	Error:      	Not equal:
        	            	expected: ""
        	            	actual  : "context deadline exceeded"

        	            	Diff:
        	            	--- Expected
        	            	+++ Actual
        	            	@@ -1 +1 @@
        	            	-
        	            	+context deadline exceeded
        	Test:       	TestMultipleGet
--- FAIL: TestMultipleGet (10.00s)


Permissions.check(): Always returns 'authorized'

Describe your environment

React-Native version: 0.55.4
Platform: iOS
Device (all iPhones - simulator)
OS version: 11.4
react-native-permissions version: 1.1.1
Devtools: Xcode
(Android only: buildToolsVersion)

How to repeat issue and example

Used yarn add react-native-permissions to add the project.
Manually linked in XCode by following the guide (see my file further down for info about how it looks)
Tried checking for permission
iPhone always returns 'authorized', when I expect 'undetermined'. I have checked that it isn't actually authorized.

And it works on android!

same issue on Android. When i set it to denied before, it returns authorized when I request permission again.

same issue on android
Environment
React Native Environment Info:
System:
OS: macOS High Sierra 10.13.3
CPU: x64 Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz
Memory: 27.68 MB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 8.11.2 - /usr/local/bin/node
Yarn: 1.7.0 - /usr/local/bin/yarn
npm: 6.1.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 11.0, macOS 10.13, tvOS 11.0, watchOS 4.0
Android SDK:
Build Tools: 21.1.2, 23.0.1, 23.0.3, 25.0.0, 25.0.2, 25.0.3, 26.0.1, 26.0.2, 26.0.3, 27.0.0, 27.0.3, 28.0.0
API Levels: 22, 23, 25, 26, 27
IDEs:
Android Studio: 3.0 AI-171.4443003
Xcode: 9.0/9A235 - /usr/bin/xcodebuild
npmPackages:
react: 16.4.1 => 16.4.1
react-native: 0.56.0 => 0.56.0
npmGlobalPackages:
create-react-native-app: 1.0.0
react-native-cli: 2.0.1
Description
When i set it to denied before, it returns authorized when I request permission again.

same issue on Android

I think this problem is from react-native.
Because call PermissionsAndroid  on Android

@elizond0 I think this problem is from react-native.
Because call PermissionsAndroid on Android

Seems somewhat buggy to me.
The only thing I have found out is to make sure the permission you are checking is supported in the "Supported permission types" table. Also, as @xutm suggests, use React Natives own PermissionAndroid on Android devices.

I am closing this since this issue does not exists anymore with the 2.0.0 release.


⚠ Samsung has degraded performance

In f77261b, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2283 ms

Resolved: Samsung performance has improved in dad2b81.


Fixed bibtex references in plot_background_statistics

Reference issue
Example: Fixes #8901.
What does this implement/fix?
Modified references to bibtex references in tutorials/discussions/plot_background_statistics.py

rendering looks good: https://25785-1301584-gh.circle-artifacts.com/0/dev/auto_tutorials/discussions/plot_background_statistics.html#references

Something failed again, any clue what it could be? I am a bit lost

@sfc-neuro the pip pre build has been a bit iffy lately, the failure is unrelated and can safely be ignored. I'll go ahead and merge, thanks @sfc-neuro !


#339 Add 'stop connector' command

Addresses https://github.com/kcctl/kcctl/issues/339
Usage:
Usage: kcctl stop connector [-e] [NAME...]
Stops (but does not delete) the specified connector(s)
      [NAME...]   Name(s) of the connector(s) (e.g. 'my-connector').
  -e, --reg-exp   use NAME(s) as regexp pattern(s) to use on all connectors

Uses the PUT /connectors/{name}/stop endpoint introduced in KIP-875 to stop (but not delete) connectors.
Similar to the 'get offsets' command, this feature requires Kafka Connect 3.5 or later, and the integration test is customized to use a non-stable version of Debezium (2.4.0 alpha). We can and should update the version used in that test once a final release takes place for 2.4.0.

Turns out the test failures in this one weren't flaky! The worker in the 2.4 Debezium image was automatically forming a cluster with the one in the latest stable (i.e., 2.3) image, which also tended to be the leader whenever the full set of tests was run but not when the StopConnectorCommandTest suite was run in isolation. Bit of a headscratcher to debug but I think the latest fix I've pushed should work. The reason this wasn't an issue with https://github.com/kcctl/kcctl/pull/338 is that the GET /connector/{name}/offsets endpoint doesn't require forwarding to the leader, whereas the PUT /connector/{name}/stop endpoint does.

@gunnarmorling thanks again for all the rapid reviews! LMK if you'd like to take another look; otherwise, I can merge and we can see about putting out a new release that includes both this and the get offsets feature.

The worker in the 2.4 Debezium image was automatically forming a cluster with the one in the latest stable (i.e., 2.3) image

Oh, wow, tricky one indeed.

LGTM, merging. Thanks a lot, @C0urante!

Addresses https://github.com/kcctl/kcctl/issues/339

Btw. if you say "Fixes https://github.com/kcctl/kcctl/issues/339", the issue will be automatically closed when merging the PR (just manually did it).


Add fetch in brew

Any change to add fetch as a brew formulae?

We'd love to have fetch installable via brew, and we'd certainly welcome a contribution (to the brew repo) that enables this.

and in apt yum etc... :)

I have created a pull request for the new formula, but It seems the Homebrew CI can't find the fetch dependencies.
I have performed all the steps and it worked perfectly locally.
Can anyone have a look at the broken CI logs and maybe tell me what am I missing?

We haven't updated fetch to use go modules yet, so it needs a dep ensure call before running go build. Have a PR coming shortly that switches over in a moment...

Ok just released the version using go modules: https://github.com/gruntwork-io/fetch/releases/tag/v0.3.10
@andreybleme can you see if that version passes the build on brew?

It passed @yorinasub17 ✅ , just need to wait for it to be merged now.
Thanks.

So, since #71 this can be closed I presume.
Thanks for your work @andreybleme, @yorinasub17 and everyone else involved.


pull request for e2e test at 11/16/2016 02:45:10

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

Details

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.


GDAL 1.11.3 port

This PR adds a port file for GDAL 1.11.3.
This branch depends on the proj port (PR #343).

Hi @mmassing, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;


Injecting lua scripts in istio-proxy container for envoy

[FEATURE REQUEST]
Currently the solution proposed here doesn't have a generic way to inject scripts inside the istio-proxy container.
Here's the problem contextualization:

I create a default.lua script that has envoy's on request and on response method signatures.
The default script requires other files from a given path
I need to download all the scripts (filters and libs) in the pod in order to run the default.lua with success

Current workaround:

The function's bodies call another method that comes from the imported scripts. They're implemented by who will deploy the service (in this case me) and I had to add it to my namespace in a configmap.

This solution is not generic and adds complexity to the deployment. We were wondering what can be a good solution and have this suggestion:

Create a init container that loads all the scripts that are required on the default.lua dynamically.

The init container is also responsible for mounting the scripts on a shared volume so istio-proxy container can get them.

The script's URLs can be defined by env variables. (possibly github or http endpoint)
The default.lua script will run the code from these mounted files.

1 - What you guys think about this?
2 - Is there any other way to get the scripts inside istio-proxy container?
3 - Do you guys see any other alternative or is anyone else working on this?
I'm more than willing to contribute and help you guys.

I like the idea of init container, however any change in the lua scripts would require restarting the pod which is not acceptable in many cases.
Config map mounts work well. They can be made part of the standard deployment. And updated are available to all pods dynamically.

@mandarjog I tried chaging the header value in the configmap but the changes did't take effect

why not compress/generate the scripts into a single file that get injected into the sidecar? are these lua scripts overly large?

@nmnellis, this is a possible solution, but does not solve the problem of getting the changes from the configmap without killing the pod, I was also thinking of creating another container which would check for changes in the configmap and force envoy to restart with changes done to the lua file

why use configmaps at all? the entire lua script can be provided inline within the envoy configuration.

Your scrip May have ‘requires’ that include local scripts.
You use config maps to provide seldom changing libraries. Use the filter to provide changeable scripts.
Even if you just change config maps, you need to force a change thru the script for envoy to reload files. So using config maps is still useful but is not a complete solution.

@mandarjog How do I "force a change thru the script" because I did a change in the file inside the container but they didn't take effect.

@rshriram I thought you were working on the design for Lua filter config specifically?
I'm planning to open source a simple xDS proxy server to allow custom Envoy config injection, as a replacement for the webhook based impl we shipped in 0.7. That at least partially addresses this use case, though I thought we wanted to address Lua specifically with first class support in Istio CRDs?


How to handle _FAIL actions

I am following the same pattern used in the middleware-netcore-example.  I see _FAIL constants in the app.ts actions file.  I am attempting to send  failures into state, but I am getting my wires crossed.
state:
export type App = {     readonly values: { name: string, value: number }[]     _readonly errors: [{ message: string, code: number }]_ };
action:
export type Action =     {         type: 'GET_VALUES_FAIL',          payload: AxiosResponse     } | ...     };
reducer:
case Actions.GET_VALUES_FAIL:             return {                 ...state,                 _errors_: action.payload.data             };
Ideally i would map the fail action to a list of errors in the state..my app i have a error message action that ties into App.errors.  Just not sure now to move forward given the errors live in a different object in state.  How can i add this error data to my state?

@tjhazel what did you do to solve this?


Update index.yml (Typo "Azure notebook"→"Azure Notebook")

https://docs.microsoft.com/en-us/azure/cognitive-services/personalizer/

oyyunttt

Azure Notebooks is the product name, so referring to "an Azure Notebooks file" or instance would be correct.
@nitinme or @erhopf Could you review this text change to the Personalizer landing page? Thanks.

Thanks @diberry


Cannot find module '@vscode/sqlite3'

Environment
Knex version: 1.0.2
Database + version: sqlite3 5.0.2
OS: windows 10 21h2 and mac os big sur 11.6.2, same problem
Node version: 14 lts
Bug

Explain what kind of behaviour you are getting and how you think it should do

npx knex --knexfile knexfile.cjs migrate:make schema_init

Error message

Using environment: development
Knex: run
$ npm install sqlite3 --save
Cannot find module '@vscode/sqlite3'
Require stack:

Reduced test code, for example in https://npm.runkit.com/knex or if it needs real
database connection to MySQL or PostgreSQL, then single file example which initializes
needed data and demonstrates the problem.

see coomand line on bug explain
Feature discussion / request

Explain what is your use case

it's a simple brand new project from scratch. it should simply work.

Explain what kind of feature would support this

Give some API proposal, how the feature should work

Missing / erroneus documentation
Send issue to documentation repo, or fix it and send PR https://github.com/knex/documentation
Questions about how to use knex
GitHub issues are for knex development. Please send questions how to use knex to
Stack Overflow or ask about it in gitter chat.

See https://github.com/knex/knex/blob/master/UPGRADING.md
You need to install @vscode/sqlite3 dependency after migrating to 1.0.0+

@kibertoad : As mentioned in a comment on another issue, they have plans to delete the repo: https://github.com/microsoft/vscode-node-sqlite3/issues/16#issuecomment-1046059712


Fix HF unit test after compatible update

Explain your changes:

One of patches that was applied to compatible was merged to compatible

Explain how you tested your changes:

Ran the HF unit test

Checklist:

[x] Dependency versions are unchanged

Notify Velocity team if dependencies must change in CI

[ ] Modified the current draft of release notes with details on what is completed or incomplete within this project
[x] Document code purpose, how to use it

Mention expected invariants, implicit constraints

[x] Tests were added for the new behavior

Document test purpose, significance of failures
Test names should reflect their purpose

[x] All tests pass (CI will check this if you didn't)
[x] Serialized types are in stable-versioned modules
[x] Does this close issues? None

!ci-build-me

Launched a CI job to run HF unit test: https://buildkite.com/o-1-labs-2/mina-end-to-end-nightlies/builds/1756#018ea376-9eda-42a9-9777-8352d68b969b

Are the patches for caqti-upgrade?

Are the patches for caqti-upgrade?

This PR removes scripts/hardfork/localnet-patches/compatible-2.patch that contained what PR #15433 merged.

!approved-for-mainnet


root directory error on Chromebook

Version 36.0.1985.138
Platform 5841.83.0 (Official Build) stable-channel falco
Steps to reproduce:

Open CDE
Click the Settings button on the bottom
Click the Folder Button near the Root Directory field
Select a directory in the in the Download Tree or in Google Drive
The path is out of boundaries and is not shown after relaunch, even if the path remains set

I am still having this same issue. The root directory is always blank and does not remain set after relaunching. Also if I set the root directory, the subfolder/projects don't load. I must use 'Open Folder...' to get them to load into the sidebar.
I am running on Chrome OS Version 39.0.2171.96 (64-bit) and Chrome Dev Editor Version 0.19.3489


[stable/phpmyadmin] Add apiVersion in Chart.yaml and add test info to README.md

According to https://github.com/helm/helm/blob/master/docs/charts.md#the-chartyaml-file:

The Chart.yaml file is required for a chart. It contains the following fields:
apiVersion: The chart API version, always "v1" (required)
name: The name of the chart (required)
version: A SemVer 2 version (required)
...

We're not using the apiVersion field. In the same way, added some information about how we are testing this chart.

/lgtm