aggregate grain and filter grain are different so get incorrent results in explore page

Currently, Superset uses the time section to generate the time-partition filter, but doesn't apply time grain on the filter. The time grain only apply to the groupby column(or other aggregate columm). This will get incorrect query results.
How to reproduce the bug

find a whole year dataset on the Internet
use generic chart
select Week in time grain
select time range and pick Jan 1st to Dec 31

Expected results
aggregate grain and filter grain should be consistance.
Actual results
time grain only apply to groupby
Environment
latest master branch
Checklist
Make sure to follow these steps before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[x] I have reproduced the issue with at least the latest released version of superset.
[x] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
Add any other context about the problem here.

I don't consider this a bug, since 2013-01-01 (Tuesday) gets truncated to 2012-12-31 (Monday) by DATE_TRUNC('week', ...) on Postgres. However, I do wonder if we should make it possible to also apply the time grain to the time filter. With the given time filter you will get an incomplete first week (6 days) unless you apply the DATE_TRUNC to the left hand side of the temporal filters.

This query may cause some potential problems. If January 1st is a Friday, then there will be an extra Monday to Tuesday records.
SQL Engine executed where clause is before the group-by clause, so some database engines will filter out the appropriate where data first, then it calculate group by clause. different databases may get different results for such statements.

I don't consider this a bug, since 2013-01-01 (Tuesday) gets truncated to 2012-12-31 (Monday) by DATE_TRUNC('week', ...) on Postgres. However, I do wonder if we should make it possible to also apply the time grain to the time filter. With the given time filter you will get an incomplete first week (6 days) unless you apply the DATE_TRUNC to the left hand side of the temporal filters.

The first Mondy is 2013-01-07. If the user wants to get more extra data, he should adjust where clause scope.

This query may cause some potential problems. If January 1st is a Friday, then there will be an extra Monday to Tuesday records.

Let's assume we'd have one observation in our main metric for each day, meaning that a full week would have a metric value of 7. In this example, currently we'd have the following result:

__timestamp: Monday December 28th
metric: 3

So it will show a date for the Monday, but only record metrics for Friday to Sunday. I believe users will expect to see the following result:

__timestamp: Monday December 28th
metric: 7

This gives the false impression of the first week of the time series to have a very low value for our metric (value: 3), despite the week being completely normal (value: 7)

@villebro @zhaoyongjie This one got pretty stale... is this still an issue after all the recent changes that were made in 2022, or is it time to close this one out?


Where are the Data from

Specify per dataset how the data are collected. For this see the [config/donwload.yaml] file. It may be enough to argue it for each table (code before the dash "-").

Shouldn't we wait until we know which tables we include in the paper?

Done


Add crash reporting to Flutter app

We can add Firebase Crashlytics to the Flutter app.

Firebase Crashlytics is a lightweight, realtime crash reporter that helps you track, prioritize, and fix stability issues that erode your app quality. Crashlytics saves you troubleshooting time by intelligently grouping crashes and highlighting the circumstances that lead up to them.

Make this crash reporting optional (a toggle in the settings screen).

@anhappdev  will you work on that, or me?

I will do that because I have some other Firebase related issues open.

Firebase Crashlytics needs to upload symbol files in the build step:
https://firebase.google.com/docs/crashlytics/get-deobfuscated-reports?platform=flutter
I could not find a way to make this optional, which means that Firebase is always required to build the app.


32 bit android and web builds fail with CBLast or OpenCL not supporting 32 bit

Reenable them somehow.

I don't think we're crashing anymore.

We aren't supporting webgl builds still. Not sure about 32 bit android also.

This isn't about crash, it's about web support for whisper.

Seems like builds fail simply because of conversion issue(from long to uint or smht like that). For now building with:
env.Append(CCFLAGS=["-Wno-c++11-narrowing"])
To see if it fixes.
I am not 100% sure if it will run correctly with optimization on web, but at least for now to see if it builds.


Fix missing z-index on calendar popup with pickDate=false or pickTime=false options.

Hi,
I saw that the z-index style is missing from the dropdown-menu if either pickDate or pickTime option is set to false. I tried without success to built a jsFiddle to reproduce the problem.
For the record, I'm seeing this problem in a AngularJS app when opening a modal (from ui-bootstrap) that contains a datetimepicker.
Thank you for your work, it is much appreciated !

Thanks a lot !


cross-platform build?

I realize this is a huge pain and likely requires us to finish setting up some example action scripts to better support cross-platform building, but it would be great if the plugin supported other platforms besides windows.
Mostly just putting this here to track it since I know someone will want it. 😉

Customized code base to be compilable on linux (using input prompt instead of reading directly from clipboard) and uploaded linux binaries - related commit. Also added better support for dev builds to the loader since dev builds seem to roll out almost on daily basis - related commit.


Collated code

Added md files for collated code
Updated links to portfolio will be done in another PR

Coverage remained the same at 92.056% when pulling e09fb8213659334770365d409e33f5bc57cf02cb on jo-lyn:collate-pr into d4017e08a3baf681673001fc2db51292f1b4d9ea on CS2103AUG2017-W11-B2:master.


Cannot edit ~/.gnupg/gpg.conf, get Permission denied

Description
Cannot edit ~/.gnupg/gpg.conf, get Permission denied
The code is: cat ${{github.action_path}}/gpg.conf >> ~/.gnupg/gpg.conf;
Area for Triage:

Question, Bug, or Feature?:
Virtual environments affected

[ ] Ubuntu 16.04
[ ] Ubuntu 18.04
[x] Ubuntu 20.04
[ ] macOS 10.15
[ ] macOS 11.0
[ ] Windows Server 2016 R2
[ ] Windows Server 2019

Expected behavior
The file should be edited;
Actual behavior
Permission denied
Repro steps
mkdir -p ~/.gnupg;
touch ~/.gnupg/gpg.conf;
chmod -R 600 ~/.gnupg;
cat ${{github.action_path}}/gpg.conf >> ~/.gnupg/gpg.conf;

Hello, @KOLANICH
This behavior is by design - https://askubuntu.com/questions/83788/accessing-files-in-a-directory-without-x-permission
- name: chmod gnupg
  run: |
         mkdir -p ~/.gnupg
         touch ~/.gnupg/gpg.conf
         chmod -R 600 ~/.gnupg/*
         cat ${{github.action_path}}/gpg.conf >> ~/.gnupg/gpg.conf

My bad, shame on me. 🤦


Enable viper for configuration management

What type of PR is this?
Feature
What this PR does / Why we need it?

This PR leverages viper to enable effective configuration management for Backplane CLI.
Users no longer need to switch between different config files based on the OCM environment, the Backplane URL will be dynamically populated based on the OCM environment the user is logged into. UX win!
The configuration filepath, proxy, Backplane URL set by the users via the BACKPLANE_CONFIG, HTTPS_PROXY and BACKPLANE_URL environment variables are respected and given preference over the values defined in the configuration file.

Which Jira/Github issue(s) does this PR fix?
Resolves: OSD-15922
Special notes for your reviewer
In order to test this PR, please create the config.env file in $HOME/.config/backplane folder. The contents of the file should be as follows:
➜ cat .config/backplane/config.env
HTTPS_PROXY="${PROXY}"

# OCM URLs based on environment
OCM_PROD="${OCM_URL}"
OCM_STG="${OCM_URL}"
OCM_INT="${OCM_URL}"

# Backplane URLs
BACKPLANE_URL_PROD="${BP_URL}"
BACKPLANE_URL_STG="${BP_URL}"
BACKPLANE_URL_INT="${BP_URL}"

Pre-checks (if applicable)

[x] Ran unit tests locally
[x] Validated the changes in a cluster
[x] Included documentation changes with PR

Codecov Report

Merging #67 (0f4b5d2) into main (82570cd) will decrease coverage by 0.51%.
The diff coverage is 30.76%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #67      +/-   ##
==========================================
- Coverage   43.90%   43.39%   -0.51%
==========================================
  Files          37       37
  Lines        2182     2196      +14
==========================================
- Hits          958      953       -5
- Misses       1082     1100      +18
- Partials      142      143       +1

Impacted Files
Coverage Δ

cmd/ocm-backplane/cloud/credentials.go
78.18% <ø> (ø)

cmd/ocm-backplane/console/console.go
10.88% <0.00%> (ø)

cmd/ocm-backplane/managedJob/logsManagedJob.go
14.58% <0.00%> (ø)

cmd/ocm-backplane/testJob/getTestJobLogs.go
19.60% <0.00%> (ø)

pkg/utils/clientUtils.go
0.00% <0.00%> (ø)

pkg/cli/config/config.go
33.33% <22.50%> (-24.17%)
:arrow_down:

cmd/ocm-backplane/cloud/console.go
53.70% <100.00%> (ø)

cmd/ocm-backplane/login/login.go
70.22% <100.00%> (ø)

cmd/ocm-backplane/managedJob/deleteManagedJob.go
48.14% <100.00%> (ø)

cmd/ocm-backplane/managedJob/getManagedJob.go
66.15% <100.00%> (ø)

... and 3 more

/lgtm

/hold

Will have to change a few things as we cannot have .env files, they can be easily sourced, and sensitive data can be revealed to the terminal. Additionally, an erroneous rebase, I'll be closing this PR and opening a new one.


Issue 282 use pint to check and convert units

This PR mostly contains behind the screens work as a base for future user functionality (i.e. auto-converting data to desired units when POSTing and GETting data). I did already hook up unit conversion to our dev endpoint for posting sensor data.
I also left a todo to possibly move a list of preferred units to a config setting, but we can also leave that in the code for now. @nhoening what would you prefer?

I'd leave preferred units in the code for now, as I don't see how users need to care. Both determine_stock_unit and determine_flow_unit (only places this gets touched) don't seem to be used yet in code?

Both determine_stock_unit and determine_flow_unit [...] don't seem to be used yet in code?

Correct, not in FlexMeasures, but I had moved it here from one of our plugins. With the introduction of pint, I intend to factor these functions out of that plugin first, and then remove them here.


Ignore cache if policy is empty

just a small PR, avoid utilizing a cache, if the cache policy is empty..

saw that ops are filtered by max tracked items.


Parsing the Complete Document

I was able to get the library working on iOS, however, I am using it only for parsing. I took an existing JSON document and converted to BSON using the bsontools. When I load that document into the parser, I only get a single record out even though the JSON had an array of 408 records. I may just be using it wrong, but here's my code:
import UIKit

class ViewController: UIViewController {

    @IBOutlet weak var textView: UITextView!

    override func viewDidLoad() {
        super.viewDidLoad()

        if let resource = Bundle.main.url(forResource: "categories", withExtension: "bson") {
            if let data = try? Data(contentsOf: resource) {
                let doc = Document(data: data)
                textView.text = "\(doc)"
            }
        }
    }
}

Here's what the output looks like in a text view:

and I've attached the BSON and corresponding JSON file for reference:
categories.zip

Document's initializer is for a single document.
We've added an initializer as extension on array for this.
[Document](bsonBytes: myArrayOfBytes)as seen here.
It doesn't yet support Foundation.Data in this initializer but that can be added.

Ah great. Many thanks!


No direct connection even if peers are in the same network

Describe the problem
I have deployed netbird on server in the public internet. Two peers are at home behind NAT (from the view of the server), but in the same LAN.
Is this expected to result in a relayed connection? I was hoping this would give a direct connection between the two peers.
Are you using NetBird Cloud?
Self-hosted
NetBird version
0.26.3
NetBird status -d output:
Peer two from the view of peer one.
caladan.net.cerberus-systems.de:
  NetBird IP: <IP_ADDRESS>
  Public key: OyaccKy8y/+itamr2Y9EGJ/iU4PCBuQtgDxdSVGHXHE=
  Status: Connected
  -- detail --
  Connection type: Relayed
  Direct: false
  ICE candidate (Local/Remote): relay/srflx
  ICE candidate endpoints (Local/Remote): <IP>:51882/<IP_ADDRESS>:51882
  Last connection update: 2024-03-27 13:30:42
  Last WireGuard handshake: 2024-03-27 14:49:05
  Transfer status (received/sent) 3.8 KiB/12.7 KiB
  Quantum resistance: false
  Routes: -

Hi @jvanbruegge, can you share some debug logs from one (or both) of the peers? to see why ICE is choosing a relayed connection over the P2P one.

I found these lines in the debug logs of peer one (<IP_ADDRESS> is the LAN IP of peer two):
2024-03-27T18:11:36Z DEBG client/internal/peer/conn.go:255: trying to connect to peer OyaccKy8y/+itamr2Y9EGJ/iU4PCBuQtgDxdSVGHXHE=
2024-03-27T18:11:36Z DEBG client/internal/peer/conn.go:286: connection offer sent to peer OyaccKy8y/+itamr2Y9EGJ/iU4PCBuQtgDxdSVGHXHE=, waiting for the confirmation
2024-03-27T18:11:36Z DEBG client/internal/peer/conn.go:705: OnRemoteAnswer from peer OyaccKy8y/+itamr2Y9EGJ/iU4PCBuQtgDxdSVGHXHE= on status Disconnected
2024-03-27T18:11:36Z DEBG client/internal/peer/conn.go:307: received connection confirmation from peer OyaccKy8y/+itamr2Y9EGJ/iU4PCBuQtgDxdSVGHXHE= running version 0.26.2 and with remote WireGuard listen port 51820
2024-03-27T18:11:36Z DEBG client/internal/peer/conn.go:603: peer OyaccKy8y/+itamr2Y9EGJ/iU4PCBuQtgDxdSVGHXHE= ICE ConnectionState has changed to Checking
2024-03-27T18:11:36Z DEBG client/internal/peer/conn.go:562: discovered local candidate udp4 host <IP_ADDRESS>:51820
2024-03-27T18:11:36Z DEBG client/internal/peer/conn.go:562: discovered local candidate udp4 host <IP_ADDRESS>:51820
2024-03-27T18:11:36Z DEBG client/internal/peer/conn.go:562: discovered local candidate udp4 host <IP_ADDRESS>:51820
2024-03-27T18:11:36Z DEBG client/internal/peer/conn.go:719: OnRemoteCandidate from peer OyaccKy8y/+itamr2Y9EGJ/iU4PCBuQtgDxdSVGHXHE= -> udp4 host <IP_ADDRESS>:51820
2024-03-27T18:11:36Z DEBG iface/bind/udp_mux.go:346: ICE: registered <IP_ADDRESS>:51820 for QBbcWttbcskPPDOS
2024-03-27T18:11:36Z DEBG client/internal/peer/conn.go:255: trying to connect to peer aqlPE89LUf4SF+bsXRiX7RaT4ef5teboEoJsWZYk0mQ=
2024-03-27T18:11:36Z DEBG client/internal/peer/conn.go:719: OnRemoteCandidate from peer OyaccKy8y/+itamr2Y9EGJ/iU4PCBuQtgDxdSVGHXHE= -> udp4 srflx <IP_ADDRESS>:51820 related <IP_ADDRESS>:51820
2024-03-27T18:11:36Z DEBG iface/bind/udp_mux.go:346: ICE: registered <IP_ADDRESS>:51820 for QBbcWttbcskPPDOS

Here is the full log of peer one: netbird.log

So it discovers the proper candidate. I am unable to see the full logs, I only see a login request from up command could you check again please?

Oops sorry, here is the correct file:
netbird.log

I actually have a hard time reproducing this. I've had to restart netbird and now the connection is indeed P2P. I will try to put some load on the system to see if this triggers the relay again.

Yeah, even with 100% CPU and 90% memory load I now get direct P2P connections even for stuff that I actually would not expect (another server that sits behind another NAT).
So it being a race conditions sounds reasonable? But apparently I have no way to test this.


GUI redesign

this is kind of a learning experience for me regarding how to style xaml. so far so good though

using this color palette btw https://flatuicolors.com/palette/gb

Absolutely love this opening page. You could add a link for .xml. I don't think many people understand the xml and its utility. I think it would help if we had and easy explainer on the concept.
also some bullet points to key MM features here would be great:

calibration

ptm discovery

top-down

crosslink

glycopeptide

non-specific (antigen)

The add buttons looked like tabs to me. I couldn't find "the button". Maybe these could look more like buttons some how? At the bottom of the page?

by accident, i dragged a raw file onto the databases page and it still went where I wanted it to go. that's cool. but a little scary. cuz you might drag something by accident and not know it.

I really like the bold text. Since you have lots of room on the right, you could have a separate button for each kind of task. that way people could see the whole menu without digging deeper. I don't know if new people understand the task system enough to know to look for search there.

Maybe "Quantification" should be its own task? It seems too buried in search to me. I'd like to showcase it more.

kinda feel like notifications box should be open by default?

Absolutely love this opening page. You could add a link for .xml. I don't think many people understand the xml and its utility. I think it would help if we had and easy explainer on the concept.
also some bullet points to key MM features here would be great:

calibration
ptm discovery
top-down
crosslink
glycopeptide
non-specific (antigen)

we should probably add links to vignettes too

kinda feel like notifications box should be open by default?

the notifications pops up if/when a notification appears. it's just minimized by default because there are no notifications to display

I think each of these could be a separate line item and maybe boost the font size a point or two?

Wow, this new GUI is beautiful and nicely organized.
Could you add a link to Spritz (https://smith-chem-wisc.github.io/Spritz/) in the Help page with something like "Generate Sample-Specific Database for MetaMorpheus with Spritz" as the button?

On the about page, we should remove HPLC from "HPLC-MS/MS proteomics data" since MetaMorpheus can also analyze CZE data

I really like the bold text. Since you have lots of room on the right, you could have a separate button for each kind of task. that way people could see the whole menu without digging deeper. I don't know if new people understand the task system enough to know to look for search there.

I agree that having separate buttons for each task would be nice

Should we update the task windows as well to go more with the new GUI. Nothing drastic, maybe just altering colors to have them look like they belong more with the new GUI than the old

I think that the order of the tasks in the drop down menu should go calibrate, GPTMD, search, crosslink and glyco instead of calibrate, search, GPTMD, Crosslink and glyco

I added links to our papers along with a description of each task to the home page and boosted font size; I could not find good link to .xml but added a short description of the advantages of .xml in the database page; added link to spritz; removed HPLC; reordered tasks in menu.
I'd prefer to keep the design fairly minimal so I think one button for "add task" is preferable to me. It seems like the interface would be crowded to have a button for each task. Or I'd have to change the button size. I like the uniform size of the buttons currently, it's just a design thing. But I could change this somehow if people feel strongly about it.
Button styling - I'm using a "flat UI" style for the interface so I'd prefer to keep the button styling as-is but again I could change this if people feel very strongly about it.
Task windows - I do agree that these should be updated and I've laid some foundation for that in the app.xaml file (this controls app-wide styling). However it's more work than I want to do with this current PR.

Can you just have "+ADD TASK," and keep the dropdown open until the user clicks off somewhere else or hits escape? Then, it'll keep the GUI clean, but the user won't have to click it three times to add calibration/gptmd/search, for example.

Could change "+ADD TASK" to "+ADD TASKS" in that case.

And maybe add tooltip information for each of the tasks if it's not there already.

separating the tasks into separate buttons seems to be very popular, let me see if I can make that look nice

-added separate button for each "add task" operation
-added option for right click -> delete
-added bullet points for task descriptions in the about page
-added a column for the file name in addition to the file path for spectra + protein DB pages


feat: AdaptiveExpressions: Allow 0 to convert as false bool

Fixes #5615
Description
The docs state that at least 1 and 0 should convert to true/false, respectively.

However, currently all integers are evaluated as "True" (see tests, prior to this change).
Specific Changes
Allowed converting 0 to false. All other integers will be considered "truthy" and convert to True. Some alternatives might be to:

Throw an error if int and not 1 or 0,
Only 1 is True and all others are False

This just seemed to make the most sense to me.
Willing to Change

I'm okay nixing this PR; I just saw the docs didn't match
I'm okay re-working the code such that only 1 is True and all other values are False

Note
I originally tried making changes to FunctionUtils.IsLogicTrue(), which is called by Bool(), but that affected a much larger surface area than anticipated.

@boydc2014, could you please review this PR? Thank you.

@chrimc62 has changed the logic to : Make booleans be false if expression is null or error and otherwise be true for non-boolean values or the actual boolean value.
But the document has not been updated.
So, do we need to modify the doc or need to modify the code logic here?
Reference:
https://github.com/microsoft/botbuilder-dotnet/commit/effd01fb736a9ea8f794d3453286bfbe4ee72253
cc: @boydc2014 @chrimc62


Use RBAC and bicep provisioning for Azure OpenAI

Fixes #2490
Microsoft Reviewers: Open in CodeFlow

Couldn't test E2E right now as it blocks on quotas. Won't merge before this is resolved.

Looks good.


Error when trying to install on react 17.0.2

Command:
npm install tawkto-react --save
Response:
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/react
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/tawkto-react
npm ERR!   tawkto-react@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See C:\Users\xxxxxx\AppData\Local\npm-cache\eresolve-report.txt for a full report.

npm ERR!      C:\Users\xxxxxx\AppData\Local\npm-cache\_logs\2021-11-12T13_17_00_073Z-debug.log

I am getting same error with
npm install tawkto-react --save
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/react
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/tawkto-react
npm ERR!   tawkto-react@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See C:\Users\xxx\AppData\Local\npm-cache\eresolve-report.txt for a full report.

npm ERR!      C:\Users\xxx\AppData\Local\npm-cache\_logs\2021-11-17T13_12_47_983Z-debug.log

Hello @andrem0
the package is updated to fully support React 17.0.x and comes with more functionalities. Hope it helps!

Hello @andrem0
the package is updated to fully support React 17.0.x and comes with more functionalities. Hope it helps!


updated travisci readme document and fixes issue #2248

Description

Reference has been created for Travis CI readme in docs/index.md document also changed the travis settings images reference path. This PR also fixes issue #2248.
Motivation and Context

Fixes #
#2248
How Has This Been Tested?

Only documentations changes has been updated.
Checklist:

[x] I have added a Signed-off-by.
[x] I have either added documentation to cover my changes or this change requires no new documentation.
[x] I have either added unit tests to cover my changes or this change requires no new tests.
[] I have run golint and have fixed valid warnings in code I have added or modified. This tool generates false positives so you may choose to ignore some warnings. The goal is clean, consistent, and readable code.

<EMAIL_ADDRESS>

@christo4ferris : Could you please review this?

@rameshthoomu I had a look at the text and the new pic. Seems OK to me and I think it could be merged. @christo4ferris

LGTM


Mydumper + nxs-backup = <3

https://github.com/maxbube/mydumper/tree/v0.9.5
please )

If parallelism is needed, why not implement the support of the mysqlpump?

Hello.
Parallelism will be introduced in the new version. Stay tuned for project updates!


Remove LGTM badge from README

LGTM.com will be shut down in December 2022, so the badge will no longer work.
As an alternative, GitHub code scanning is recommended.

Thanks!

Cherry-picked for 3.6.


Problem in codefolding: can not fold completely.

When i use code folding in Jupyter, some cells can not be folded, and i did not find any grammar errors in these cells.

I've just tried installing the codefolding extension and I don't see any codefolding (recent Jupyter install, on a Mac, using chrome)? Notes suggest I maybe need to update Codemirror? Is this still the case or do I have another issue? Is there a simple instruction list for updating Codemirror for use by Jupyter server?

Works for me with current Jupyter on Mac with Chrome. Do you get any error messages on the Javascript console output ?

I reinstalled the Jupyter and the problem disappeared, thank you all.
And another small problem is the Css still dose not work, the option menu only has default option.


Minor stuff

When reading darknet weights from file, allocate the vector capacity once, up front. Why not, may as well.
After watching some C++ Weekly videos and reading cppreference, it turns out type punning is bad and can cause undefined behaviour, sometimes, maybe, theoretically, possibly never. But, ..., probs a good idea to obey the C++ standard and do what is suggested, i.e. use memcpy()

Thank you :)


"Searching for peers"

I am in an infinite loop of "Searching for peers". If i try to rescan blockchain nothing happens

This means an app has no network access. Please check if networking works on your phone (in a browser for example). If it does then check if network access is restricted for a wallet app in phone settings.

Network access is ok. I solved the problem by unchecking "Connect to trusted nodes"

Seems like your app version is rather outdated. Trusted nodes was an emergency measure during UASF times and was removed later.

Turns out my phone isn't supported now and F-Droid didn't update the app


Rest client seems to edit the HTTP header field names

When I send a request using the client, it seems to change the names of the HTTP header fields to lower case automatically.
Expected outcome
The client should not be editing the header fields. For example, if I set a header field as "Content-Type", the request should be received at the server as "Content-Type"
Actual outcome
After the new update, the client seems to be sending headers which were set as "Content-Type" to "content-type"
Versions
App: <IP_ADDRESS>-stable
Chrome: 47.0.2526.111
Platform: Linux (-)
Steps to reproduce

Create a message with a payload and use POST as the method
Set the header "Content-Type: application/json"
Send the message and observe the request received at the server

Facing the same issue. Please fix this +1

Hi,
Thank you for an issue report. Please refer to the duplicate issue #517 for the discussion.
I'm closing it as WAI.


Implement body.formData

The spec implements a formData method to turn a request/response body back into a FormData

Node.js doesn't have FormData, I just don't think we can do that without explicit dependency on form-data, and form-data isn't explicitly isomorphic either.

When the user is already using node-fetch, then he/she is probably already past the isomorphic layer – as node-fetch itself is not isomorphic. Regarding the dependency on form-data, I don't consider it to be that great of an issue; but we could let the user specify the constructor as an option if we were to care about the size of this installation.

Something that just pop-out of my mind is handing over just a instance to wish we can append the data into...  May not be the right thing to do...
var FormData = require('form-data')
new Response(...).formData(new FormData)

One think i don't like so much about form-data today is that's not fully implemented. Lacks many feature of reading and manipulate the form. Without this it would be no point in even implementing body.formData since you would not have any way of changing/reading it... But hopefully they will resolve this issue: https://github.com/form-data/form-data/issues/124 someday - kind of lost hope since it have taken them a long time now...
I did implement a better fully spec'ed FormData polyfill here. But it was targeted for browser (not for node - since it depends on Blob & File)

@jimmywarting Hi! If you still need a FormData implementation, may be you check out this one? I've implemented more than just an .append method.

Never seen it before, have only used https://www.npmjs.com/package/form-data so far.
Just another implementation of FormData. It's nice that the rest of the methods are implemented like the iterator and all that. But maybe not certain node-fetch can work together with that.
The sad part is that there is no standard spec of how it should be read/handeld.
But the feature might look brighter: https://github.com/w3c/FileAPI/issues/40
We will maybe get Symbol.stream or something like that. There have been numerus of talk about  making FormData streamable and having a unknown content-length

btw, i did this for the fetch polyfill: https://github.com/github/fetch/issues/571
The reason i would like to see this implemented on the server is so that i can have one less dependency :P
Express.js app:
app.post('/user', async (req, res) => {
  const fd = new FormData()
  await new Response(req).formData(fd)

  fd.get('username')
})


Remove criteria code modifiers that are not allowed (e.g. BA1_Supporting, BS1_Standalone, etc)

Specified changes signed off by SVI on 3/4/2022:

https://docs.google.com/spreadsheets/d/1heS9fPizdZt0_r6kgPqKKd1Gizm98b6cUUjRLqmD3MQ/edit#gid=0
https://docs.google.com/presentation/d/1UYvB21CUh_YltWdXskzbHHJKJFDlydHfHTpG4pIKnoY/edit#slide=id.g11809e98eef_0_6

The VCI team will generate a list of current records already using the to-be-deprecated modifiers in the VCI, the proxy team will be responsible for following up with owners to address these and republish to the Erepo

https://broadinstitute.atlassian.net/browse/CGSP-159
Replaced https://github.com/ClinGen/clincoded/issues/2284

May require more discussion.

Requires more discussion

Final list of modifiers to be supported was signed off by the SVI as of March 4, 2022. Discussed was the need to widely publicise the changes when this is launched, specifically:

Email the user base with an explanation.
Briefly present at a biocurator meeting
Use other platforms (twitter) to spread the word


Add support for custom filetypes.

Right now, the extension relies on the languages identified by VS Code. I think there's potential to allow custom filetypes.

In dire need of support for .go files. But this sounds even better


Extend PgQueryProtobuf.len to machine word size

The len field is expected to be size_t from the protobuf side (see the definition of pg_query__parse_result__unpack()). Also, clients are expecting to be able to use size_t-like types when filling the PgQueryProtobuf structure.
This is how this problem was discovered in pglast: deparse_protobuf(parse_sql_protobuf('select 1')) would always return '' on big-endian machines.
deparse_protobuf() populated a 64-bit machine-word-sized len field, but libpg-query would only read an "int" from it, which is 32-bit only even on 64-bit machines. On big-endian machines, the "wrong" half of the integer is read, so the len is effectively always zeros.
Close lelit/pglast#114.

Thanks!
Fwiw the issue was on 64-bit big endian (because int is still 32-bit only even on 64-bits).


DocsArchive-<IP_ADDRESS>Auto archive content

Auto archive content from https://github.com/OPS-E2E-PPE/docs-archive-test-source

Docs Build status updates of commit 3934179:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Archive_master_2019-10-09-08-40-39 has been deleted or has been force pushed: fatal: Couldn't find remote ref Archive_master_2019-10-09-08-40-39

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.


No result when put object again

What do you think, is it expected for default put resolver, that when you:

put object
delete it
and put again the same object (with not null internal id)

As a result, there is no any changes in storage after second put.
May be we can check result of update in second case, and try use insert?

Damn, great use case. I'll think about it and comment
пт, 13 марта 2015, 8:10, Dmitrii Nikitin<EMAIL_ADDRESS>
What do you think, is it expected for default put resolver, that when you:

put object
delete it
and put again the same object (with not null internal id)

As a result, no any changes in storage after second put.
May be we can check result of update in second case, and try try use
insert?
—
Reply to this email directly or view it on GitHub
https://github.com/pushtorefresh/bamboo-storage/issues/97.

I see two things:

Put object can set inserted id, and we can add delete resolver which will just remove id from object.
We can add check to default put resolver and make insert if update returned 0

Also, we can add resolvers for all operations, put, get, delete with default implementations to allow users customize behavior of the operation, what do you think about it?

I just think only about second variant.
But resolver for all operations, that by default will resolve this issue and will be hide from user in common case, it sounds flexibly.

So, I'll create an issue for resolvers! Better API for everybody


concurrent package builds in same directory fails

the TempPath option isn't being used
no temporary directory is used at all

I haven't looked at the details of the deb file creation so I might have missed
something but it seems like the whole process just use io.writer's writing
directly to the .deb-archive instead of writing it out to multiple files first?
new suggestion: create intermediate files concurrently in goroutines

Thanks for the PRs! I am not getting emails from GitHub for some reason so I just saw all three of them; I'll look them over this weekend.

new suggestion: create intermediate files concurrently in goroutines

Sounds like a good change to me! I think when I first wrote this I was taking apart .ar files and it was helpful to have them on disk but it's not necessary at this point.

I implemented concurrent archive writing (which was at least about 13% faster for small package builds) but it introduced some bug and it got more and more drawn into fixing related bugs so I'll defer writing improvements like that until some bugs and usage issues are resolved.
Please review and merge/comment on my pull requests if possible


Jumping to top of screen with nested repeater

Hi
I've set up a two-level repeater (top level are 'questions', inner level are 'choices'). All is working well except for one thing: when you click an Add Choice or Delete Choice button on any question apart from the first one, it correctly adds or deletes the choice, but then jumps to the top of the screen. So you then have to scroll back down to the correct place every time (which in my case is below lots of other stuff, so it's a lot of jumping about and scrolling).
The same thing happens with Delete Question, again it's for any question except the first one.
The Add Question button is fine.

Very sorry to hassle you, I wondered if there's any update on this? Happy to help out if there's anything I can do to help clarify/debug/test/etc (I'm a developer but I'm not a JavaScript expert).

Check your delete button, it must have href = "#", change it for href = "javascript:;"

Ah, something so simple!
Thanks very much, it's working perfectly now.


HDDS-8697 Recon - Expose API for total count for blocks pending for deletion.

What changes were proposed in this pull request?
Improvements have been made to the existing BlocksEndpoint API response. Now, the total count of blocks pending deletion is displayed in the API response. The updated response will appear as follows:
{
  "totalCount": 1000,
  "containerStateBlockInfoListMap": {
    "OPEN": [
      {
        "containerId": 100,
        "localIDList": [
          1,
          2,
          3,
          4
        ],
        "localIDCount": 4,
        "txID": 1
      }
    ]
  }
}

This new response includes the total count of pending deletions blocks and a list of containers, each with their state, container ID, list of local IDs, count of local IDs, and transaction ID.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-8697
How was this patch tested?
Added new and made modifications to the existing UT's

@devmadhuu @adoroszlai @krishnaasawa1 @symious Can you please take a look !!


Create build scripts

This is the first step towards a more user friendly build process.
With a build script you now have the ability to add or remove steps without changing the workflow of the user.
With this pr the build scripts will be created and later I will update the readme by providing a new building.md file

Hi @FairyTail2000 . Sorry for taking so long to review this and thanks for creating a PR to help folks build the project. For the time being we'll be looking to simplify the build down to just two commands:
go generate ./..
go build .

Ideally, it's even just one (go build .). We're trying to cut down on scripts as much as possible as they can be hard to maintain over time. In that light, I'm going to close this PR but feel free to suggest other improvements – all ears!


nav alignment and styling contact us form in index

Description
@swaraj-das  I done that please see https://durgaprasad-developer.github.io/Collect-your-GamingTools/
Screenshots
No response
Any additional information?
No response
What browser are you seeing the problem on?
No response
Checklist

[X] I have checked the existing issues.
[X] I have read the Code Of Conduct
[X] The changes don't break the code
[X] Please attach the screenshots and video of the development work once it is done

@swaraj-das I done it please see https://durgaprasad-developer.github.io/Collect-your-GamingTools/


Option to not write coordinates to output files?

@mathomp4 and I were talking and wondering if it would make sense to add an option to History and the IO layer to not write the coordinates to files in cases where they are 2D arrays like for the Cubed-Sphere or Tripolar grid now that we are starting to have more non Lat-Lon output. At high resolution replicating these over and over again in every file seems like something the astute user might not want to do to save disk space. We already have the coordinates for both the Cubed-Sphere grid resolutions we run as well as the MOM5 and MOM6 tripolar grids just sitting in separate files already if someone needs them.
For regular Lat-Lon grids where the coordinates are 1D probably not even worth worry about.

@tclune @mathomp4
Suppose I were to do this. There are two options, any thoughts on which to do, obviously one is more work than the other.

Option 1 is to just add a flag so that the files do not have the 2D coordinates but that the coordinates do get written once to a file during a run
Option 2 to is to add the flag so that files do not have the 2D coordinates and not bother even writing them at all to a different file. The rational for this would be that I already have the coordinates in multiple formats for every possible resolution we can or will run on Discover so if people want them I have them and they can get them. No real reason to write them out at all if they can handle doing a cp on the command line

Thoughts?

Not stale. Marking long-term


Add a icon for the project

Hello,
As always we need an icon for the project. To kickoff the idea here are some drafts:

Feel free to share your ideas and your drawings.

Vote done during a internal meeting. The first answer won.


Regression test request for #27913

Precondition:

None

Test:

Go into any chat report.
Type the suggested message below, it's been prepared for testing purposes:

`thissadasdasdsadsadasdadsadasdasdasdasdasdasdasdasdasdasdsadsadggggggggggggggggg` multilingual
`https://www.google.com/search?q=google&oq=goog&gs_lcrp=EgZjaHJvbWUqEAgAEAAYgwEY4wIYsQMYgAQyEAgAEAAYgwEY4wIYsQMYgAQyEwgBEC4YgwEYxwEYsQMY0QMYgAQyDQgCEAAYgwEYsQMYgAQyBggDEEUYOzIGCAQQRRg8MgYIBRBFGDwyBggGEEUYPDIGCAcQBRhA0gEHNzM1ajBqN6gCALACAA&sourceid=chrome&ie=UTF-8`

Confirm that the message displays and wraps around properly for both IOS and Android native.

cc @isagoico

Created the following TC to cover this scenario in the regression run:

Markdown - Code Block in mobile

Closing the issue, please reopen if needed.


Can't build with --prod flag on Angular 4

Works well without the --prod flag. If --prod flag is added I get the following error:
Error: Metadata version mismatch for module /node_modules/ng2-swipe-cards/ng2-swipe-cards.d.ts, found version 4, expected 3

remove the node_modules/ng2-swipe-cards/node_modules folder from your project.
and please update here if it fixed your issue .
thanks


Fix building without reqwest

This fixes a compilation error when building with no-default-features, and adds a build step to compile without default-features to make sure it keeps working.

Thanks!


Update Globals “nav”

Automatically generated by Netlify CMS

👷 Deploy Preview for benevolent-muffin-215770 processing.

Name
Link

🔨 Latest commit
c68f71bcd774f57292a1b7f70102af82690b0314

🔍 Latest deploy log
https://app.netlify.com/sites/benevolent-muffin-215770/deploys/62841b484e5f9a000877d82e


Fix --envs filter

sampletester --envs was blowing up for me
$ sampletester --envs node talent/v4beta1/*.yaml
SKIPPED: Test environment: "php"
Traceback (most recent call last):
  File "/Users/rebeccataylor/code/beccasaurus/sample-tester/sampletester", line 250, in <module>
    main()
  File "/Users/rebeccataylor/code/beccasaurus/sample-tester/sampletester", line 95, in main
    success = manager.accept(visitor)
  File "/Users/rebeccataylor/code/beccasaurus/sample-tester/testplan.py", line 242, in accept
    visit_testcase = visit_suite(suite_num, suite, do_suite)
  File "/Users/rebeccataylor/code/beccasaurus/sample-tester/testplan.py", line 179, in <lambda>
    do_suite, start),
  File "/Users/rebeccataylor/code/beccasaurus/sample-tester/testplan.py", line 184, in visit_suite
    start = [visit(idx, suite, doit) for visit in visit_fns]
  File "/Users/rebeccataylor/code/beccasaurus/sample-tester/testplan.py", line 184, in <listcomp>
    start = [visit(idx, suite, doit) for visit in visit_fns]
TypeError: 'NoneType' object is not callable

The case suites for the skipped environment were (and still are) being visited.
But visiting the test cases of a skipped suite was breaking. This is my fix.
Works for me now, after continue'ing when do_suite = False
I didn't spot any tests to update to reproduce this, but feel free to point me in the right direction and I'll repro with a test.

I created #19 to track the issue. This fix isn't quite right: we always want all the visitors to visit all the nodes in the hierarchy, even if they are to be skipped. Each visitor at a node should decide what to do if the node is skipped. (Rationale: we want to be able to report on the skipped nodes to, even if no tests executed there.) Fixed in #20.


@bn3t/svelte-apexcharts not found in NPM

npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@bn3t%2fsvelte-apexcharts - Not found
npm ERR! 404
npm ERR! 404  '@bn3t/svelte-apexcharts@*' is not in this registry.
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

Indeed, it was not published to npm. I am not going to work on it since I don't do svelte work anymore. Feel free to clone it and publish it under your own name.


Update styles.css

in dark mode the text in the learn more pop up can't be seen because the text color is same as the background color. it was fixed

Thank you for contributing! Merging it🚀


Add helper for triggering test builds of github PRs

LGTM besides the flake8 errors
not sure but does it make sense to put the constants into a yml file to make it reusable for other machines or scenarios?

@MaximilianMeister yes, eventually this makes sense. I've been thinking about this but weren't able to come up with an extensible format that could be used for more than just one purpose. If you have other code in mind that could benefit from sharing that config data, we can take a look at refactoring those two tools then.

@dirkmueller to be honest I haven't even thought about the other tool when I wrote my comment. it was really just for this tool here. but yes it would be good to bring the tools together somehow at a later point.

LGTM

:+1: looks as if it cannot break much


fix menu-list bullets in content section

Fix menu-list bullets rendering in content section

I'm going to close this for now since our ship is sailing in a different direction....


Add support for comments other than comment.line

This should fix #5
Add support for other types of comment, eg block comments in languages other than Python.

Hi @a-stewart, thanks for your contribution! I integrated the fix among other fixes in last version, therefore closing this PR.


Add RFC 3339 as a date/time format

The [RFC 3339] format is similar to ISO8601 except that it also supports time zone information.

See branch feature/rfc3339

According to this, ISO 8061 support time zone information.  This is also currently supported.


Enable default value flow for milestoning parameters

Summary

Enable default value flow for milestoning parameters
How did you test this change?

[ ] Test(s) added
[x] Manual testing (please provide screenshots/recordings)
[ ] No testing (please provide an explanation)

https://github.com/finos/legend-studio/assets/73408381/51f8433a-1be9-44a9-915e-f5a154b28684

lets also remove milestoning icon next to the entity name

The icon has been removed as well

convert to draft to fix an issue with milestoning derived prop


Update LZ4 compression utility to version 1.9.3

Benchmark results of compress + write RGB 1280x720 frame (frame only no additional data)
Tested on Windows 10
Laptop HP Elitebook 850 G6
Version 1.8.0 benchmark results:
AVG time: 53 [ms]
Min time: 40 [ms]
Max time: 67 [ms]
Version 1.9.3 benchmark results:
AVG time: 23 [ms]
Min time: 19 [ms]
Max time: 39 [ms]
Performance enhancement of :~ 50%
Tracked on [LRS-34]

Post the comparison table for video compression with previous and current LZ4 versions in the PR's description

Done


Update aes and cfb8 dependencies

aes and cfb8 crates are at 0.8 currently but they are 0.7 in Valence. I tried updating a while back but couldn't figure out how to use the new API (It's very different).
Not much urgency on this one.

It turns out there are some breaking changes here. I'll throw up a draft PR of what I have so far.

I think the best way to upgrade this is to create a couple of new types that implement AsyncRead and AsyncWrite that can encrypt and decrypt blocks on demand. That way, we can use decrypt_block_mut() which doesn't consume the cipher. I'm not familiar enough with async rust to be able to do this myself.

Neither am I.


Update PR size labeler line counts

The new line numbers for the labels are:
XS: 0-9
S: 10-99
M: 100-999
L: 1000-4999
XL: >5000
I think these fit nicely to the PR sizes we usually get.

As the person who set the initial values; agreed. We used the defaults from goonstation, and I think the proposed values are much better.


Prevent users from manipulating return stack past user's frame

As it currently stands a trivial r>  can bypass any it block, which is probably too trivial to do. Doing it more sometimes terminates the tests immediately depending on the number of r>s.

This is a core feature of Forth, its flexible control structures that can be redefined by the user entirely depend on being able to manipulate the return stack. Yes, it is possible to crash a test by doing this. It is not possible to accidently pass a test however. In case a specific Kata author or translator wants to disable stack manipulations, he can always disable it in 'preloaded.4th'. In general, it might actually be required to have a Kata manipulate the return strack. It's therefore not a good idea to block it all together by the framework.
For an example how to disable Forth words, look at the test cases in Sum of Two Integers
: + 2drop rnd ; : - 2drop rnd ;

Theoretically, it might be possible to redefine ALL stack manipulating words to include stack over- and underflow checking. That would be however far out of scope of this simple test framework.


Fix: vorpal.exec never fires callback with piped commands when using promises #33

See: https://github.com/dthree/vorpal/issues/33

:+1:


Type info not collected for :add-ed modules

Repro:

Run stack ghci --with-ghc intero in the stack repo (perhaps with --no-build if it's already been built)
Try :all-types and get no results
Do a :load Main
Now :all-types yields all types

The difference is that the ghci-script generated by stack uses :add.

Opened a PR which seems to address this.

Think we can close this now.


Accessing Child Items in dragula callbacks

Hi there,
I'm struggling to understand the best way to map the dom elements passed back in dragula callbacks to react child items. My code is as follows:
    componentDidMount: function () {
      var container = React.findDOMNode(this),
      drake = ReactDragula([container], {
        moves: function (el, source, handle, sibling) {
          // there are some items in the list of children associated with this container
          // which should not be draggable. Identifying these by their class name feels
          // somewhat wrong (shouldnt be reaching into the DOM to understand a child's state?).
          return el.className !== 'draggable';
        },
        direction: 'horizontal'
      });
      drake.on('drop', (el, target, source, sibling) => {
        // how to I convert the DOM `el` here into the corresponding child item
        this.props.moveFrameCallback(item.id);
      });
    }

The el parameter passed into the drop method is a dom child element of the dnd container. Was wondering what's the best way to map this dom element to the react child item so I can invoke a callback?
I'd like to be able to make an API call based on the drop action and need the id of the child element. The id of the child item is somewhat parsable in the data-reactid attribute of the dom node - is that where I should be taking it from, or is there a more advisable way?
Thanks again for dragula,
Sean

It appears that dragula tracks DOM elements instead of React components, but that doesn't make sense in a React app as you never really care about the DOM. :(

Yep - after reading some react documentation and reading this SO post , it appears that a mapping between dom nodes and react components isn't exact the react way of doing things.
In order for this to work, some the corresponding react component would need to be sent back in line 266 of dragula.js:
 else {
      drake.emit('drop', item, target, _source, _currentSibling);
    }

Based on this article, I think there'd (very understandably) be some resistance to leaking any react specific code into dragula.js to provide this react component in the callback.
@evandavis @bevacqua - Would there be any any way for react-dragula to accommodate this additional context?

Can't we just map the drake instance to the react component?

@bevacqua how do you propose doing that?

I haven't used React that much, but we could change react-dragula to fit React -- as long as dragula itself doesn't need to change to accomodate React we're fine. So, maybe we could do
In react-dragula:
drake.on('react-component', component => _component = component);

In user code:
drake.emit('react-component', component);

Where did we land with this? I am running into this problem now.

+1
I'm currently getting around this by assigning data-* attributes to the DOM elements, but would much prefer if there was another way :)

In the next version of React the data-reactid's will be removed, so you shouldn't try to map them to React components.

Am I missing something? What's the point of react-dragula if it breaks how React works with the DOM?

I'm also unclear on how this project actually lets you use dragging and dropping to accomplish anything.  Dragula is a very nice and lightweight project, it would be great to use this, but I'll check out http://gaearon.github.io/react-dnd/ for now.

Hey @bevacqua , is there any solution to this issue? It seems like we need some sort of callback like "onDrop" that includes info about the element being dragged.

... Does anyone have a solution or workaround to this issue?

Given that my question was never addressed and this still seems to be antithetical to how React works by changing the DOM directly, I've abandoned this for http://gaearon.github.io/react-dnd/ as well.

I'm not seeing why using data attributes is so bad? I'm not seeing anything break. Take this example:
var listsNode = ReactDOM.findDOMNode(this.refs.lists);

drake.on('drop', function (el, target, source, sibling) {
    var listsNum = source.children.length;
    var i, j;

    for (i = 0; i < listsNum; i++) {
        console.log(source.children[i].dataset.oid);
    }

    for (j = 0; j < listsNum; j ++) {
        console.log(listsNode.children[j].dataset.oid);
    }
});

In both instances the correct oid is logged. Data attributes aren't somehow "not React", they are valid HTML5 attributes and work fine with React (https://facebook.github.io/react/docs/jsx-gotchas.html#custom-html-attributes).
So what's wrong with using this method to update the order? @levrik We are not talking about the react- attributes, we are talking about custom html5 data attributes.
Seems like an easy and valid way to fix the problem to me.

Why is it not ok to read the DOM? Seems to me that accessing elements through data-something attributes does the same thing.


python310Packages.deal: 4.23.7 -> 4.24.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.deal is: Library for design by contract (DbC) and checking values, exceptions, and side-effects
meta.homepage for python310Packages.deal is: https://github.com/life4/deal
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 4.24.0 with grep in /nix/store/ca19nkgfxf42nvqsd0yh23rsivyzw6ni-python3.10-deal-4.24.0
found 4.24.0 in filename of file in /nix/store/ca19nkgfxf42nvqsd0yh23rsivyzw6ni-python3.10-deal-4.24.0

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

6 total rebuild path(s)

6 package rebuild(s)

First fifty rebuilds by attrpath
python310Packages.deal
python310Packages.icontract
python310Packages.pylddwrap
python311Packages.deal
python311Packages.icontract
python311Packages.pylddwrap

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/ca19nkgfxf42nvqsd0yh23rsivyzw6ni-python3.10-deal-4.24.0 \
  --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 python310Packages.deal https://github.com/r-ryantm/nixpkgs/archive/8d8c53c68923e235b53ff9e1995a490dded43798.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/ca19nkgfxf42nvqsd0yh23rsivyzw6ni-python3.10-deal-4.24.0
ls -la /nix/store/ca19nkgfxf42nvqsd0yh23rsivyzw6ni-python3.10-deal-4.24.0/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

6 packages built:

python310Packages.deal
python310Packages.icontract
python310Packages.pylddwrap
python311Packages.deal
python311Packages.icontract
python311Packages.pylddwrap

Maintainer pings
cc @gador for testing.

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
Result of nixpkgs-review pr 218513 run on x86_64-linux 1

6 packages built:

python310Packages.deal
python310Packages.icontract
python310Packages.pylddwrap
python311Packages.deal
python311Packages.icontract
python311Packages.pylddwrap


Is “Spatial simulcast” and “Dynamic changes of resolution" the same thing

I wonder wether openh264 support Dynamic changes of resolution by  using Spatial scalability. And if so, the MAX_SPATIAL_LAYER_NUM is 4, then the max number of resolution is 4 ,am I right? Thank you so much.

Could you explain "Dynamic changes of resolution" you mentioned more clearly?
And if so, the MAX_SPATIAL_LAYER_NUM is 4, then the max number of resolution is 4. => Yes

Thank you for your answer.
I mean there are two  features of openh264. One is "Spatial simulcast up to 4 resolutions from a single input". The other one is "Dynamic changes to resolution". Are they the same?

@LiuxjYolanda the answer is no.

Spatial simulcast up to 4 resolutions from a single input" : means that you can give the encoder a simulcasting parameters, and the encoder will try to output simulcasting bit streams, that means bitstreams that encoding the same video content but different in resolution. Say you can give a 720 video raw source to the encoder, and set the encoder to be simulcasting up to 4 spatial layers, then the encoder will output encoded packets that can be decoded into 90p, 180p, 360p, 720p respectively.

"Dynamic changes to resolution": means that when you use the openh264 lib in your application, you can change the resolution to be encoded, in the middle of encoding, by correctly calling the encoder's parameter setting interface (API).

Can you show me a coding efficiency comparison of spatial scalable coding and h264?

@ruil2 does openh264 have an example of cfg file supporting spatial scalable coding

@echoxk it sure have several cfg files in testbin/ folder.


Red Alert 2 & Yuri's Revenge minimize on fullscreen

I can't seem to get RA2/Yuri's Revenge to fullscreen.
When I launch in fullscreen it minimzies instantly. If I alt+tab quick enough at the right moment I can get it into windowed mode.
Here is my log.
cnc-ddraw.log

Could you generate me a new debug log please? Just updated the debug build, link: https://github.com/CnCNet/cnc-ddraw/issues/44


"binding 3rd signature will be deprecated" is not very clear

Since updating today I have seen this message popup in the cmdline window below a few times. Firstly, it took a while to find that this was the plugin printing it. Now I gather its to do with the breaking changes neovim is considering for lsp handlers in 0.6. However im still not sure if there is a config/fix that I should be applying to get rid of this message for now. What is check_client_handlers?
What is the feature that is being deprecated here?

I get this issue too :

The plugin will disable hook signature handler from other sources. E.g. from lspsaga signature.

I dont use lspsaga

another error message

Is your plugin updated? I pushed a few commits today.

thanks! it works now :)


ifc exchange websit crex24.com China user use vpn

ifc exchange websit crex24.com  China user use vpn

https://crex24.com/zh/exchange/IFC-BTC


[Baggage] Add organizer/volunteer that checks the baggage

Save who did what!

Added on model and saved on views.


Improved unsubscribe design

I was discussing this issue with @viniciussbs on Slack the other day. Opening an issue to solicit ideas.
With Apollo Client, after performing a watchQuery, you get back an “observable” object. The ember-apollo-client Apollo service then "subscribes" to this observable, and the resulting subscription later needs to be unsubscribed from when you no longer want it to get updated w/ new data from the store. Typically this is done when you exit a route, or when the component is being destroyed. My initial version of this addon used an ugly hack to enable this, by exposing an _apolloUnsubscribe function on the returned data and making the user responsible for calling it.
@viniciussbs and I are both unhappy with the current way that ember-apollo-client puts the onus on the user to unsubscribe from watched data whenever they're done w/ it. I’m trying to come up with a more user-friendly design that still meshes well w/ Ember.
One idea I had is that instead of injecting the apollo service directly into routes/components, you’d use some sort of mixin that would function as a proxy. It would still be available via this.get('apollo'), and would proxy all calls to the actual apollo service, except that it would also track queries and route/component lifecycles. Then it could automatically unsubscribe from anything that was queried within the route/component when teardown is happening.
This might also enable some better designs for pagination (see #18). If the tracked observables are easily available to the developer (say with this.get('apolloQueries.myActiveQueryName')), then it would be trivial to call fetchMore() on the observable when you want to get another page of results.
One of the key design goals I'd like to achieve with this project is to avoid layering too much on top of Apollo Client. I hope that means it's easier to keep up with the project and we can avoid situations where functionality is available in the upstream but not easy to use in this addon.
Thoughts on whether this is a good idea or on how to implement it? Are there other projects out there with a similar model, where a service is wrapped to make it route-aware or component-aware?

I have a use case for this.
Let's say a route could have actions to open modals with a query per modal. That leads to many query subscriptions into the same route asking to be unsubscribed when you exit the route.
I have a similar use case into my application, but all actions that open modals are into the route Application - because the modals can be opened from any route. In this case, the route's query manager won't help. Calling something like this.queryManagerFor('application') inside the route could help. This is a corner case, though. I can solve this doing the query inside the modals components - I was avoiding it to follow the DDAU style.

Fixed by #20.


Revert "Update dobby action to use reusable workflows"

Reverts simplybusiness/twiglet-ruby#70

What is the reason?

What is the reason?

I've sent you a message on Slack for the reason.


Problems getting started

I use the lib as you described in README. Unfortunately I'm not able to use your lib. Could you pleas point me in the right direction?
let socket = window.RxSocketSubject.create('ws://echo.websocket.org');
socket.onNext('one');
socket.forEach(
(a)=>{ console.log('sub a', a); },
(b)=>{ console.log('sub b', b); },
(c)=>{ console.log('sub c', c); }
);
//sub b, TypeError: Cannot read property 'map' of undefined(…)

Probelms solved. After having a look at the sourcecode and the awesome tests i was able to handle this easily.
Ther is a small error in the README.
rxSockets are created like this:

connections = Rx.Observable.just('ws://echo.websocket.org');

var socket = this.rxSocket =RxSocketSubject.create(connections);

Will send pull request with updated docs


AddCardLink: refine onclick

Is your feature request related to a problem? Please describe.
-When AddCardLink is supplied as a custom component there is no way to supply onclick callback function, lets say if I want to show modals when it is pressed.
-If i just add onclick method on the custom component and dispatch some action using redux. the dispatch function of does'nt pick up my app store instead reac-trello's store.. so things get a little complex
Describe the solution you'd like
A way to supply onclick callback function for AddCardLink.

Hi,
Do you know how to add link on title or somewhere else?
Best,
Marko

Hey @MarkoKurtovic .
Can you elaborate the question? Where do you wanna add the link.. is it on card titles?

Thanks for answering @jordanos
Yes, i just need simple redirect link on title.
Best,
Marko Kurtovic

okay @MarkoKurtovic
You can get that by creating a custom card component where you'll add a redirect link by wrapping the <CardTitle/>, Then supplying it as a prop like this:
const components = {
Card: CustomCard,
};
<Board components={components} />
You can create a custom card component using this format.
I've done the same stuff when I needed to customize the card for my use here check it out it might help you.


CI: Fix CUDA 11.6 driver update steps

nvidia-smi -pm 0 had to be done before driver update.

/test mini


md-tab is not working correctly with (textarea mdInput md-autosize)

Bug, feature request, or proposal:
Bug
What is the expected behavior?
TextArea with md-autosize inside a md-tab should show the initial ngModel value in the 2nd Tab and above.
What is the current behavior?
Currently the initial value is only visible for the 1st Tab. For the 2nd Tab and above it is not visible until user type something into the textbox
What are the steps to reproduce?
Step 1) Verify that the mdInput md-autosize work as expected in Tab 1 & Outside of the Tab
Step 2) Click on Tab 2, the ngmodel value is not visible however the word count is correct
Step 3) Click on the Textarea in Tab 2 and type, value is now visible.
Plunker template: https://plnkr.co/edit/d7ypZ7afCMgAmV425Ohz?p=preview
What is the use-case or motivation for changing an existing behavior?
TextArea should be able to display initial value.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Material beta 8
Angular 4.3.1
Typescript 2.4.2
Chrome OS
Is there anything else we should know?
NA

Maybe related to #5269.


Single change version: Updates crayfish repo and commit hash

There are some changes in the Houdini micro service to help cleanup imagemagic tmp files if left behind - this PR pulls in those changes.
This also:
Switches us to referencing our own fork of crayfish in the crayfish docker file
This is a simpler version of #90

It's good to know that the hash that was changed (in the houdini dockerfile) is located here on a branch in the jhu-idc/crayfish repository: https://github.com/jhu-idc/Crayfish/tree/tmpfiles_fix_branch.


InvalidTemplate: Deployment template validation failed:

Please provide us with the following information:

This issue is for a: (mark with an x)
- [X ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Used already deployed search Azure AI services, Azure Open AI

Any log messages given by the failure

"status": "Failed",

"error": {
    "code": "InvalidTemplate",
    "message": "Deployment template validation failed: 'The resource 'Microsoft.CognitiveServices/accounts/ACCOUNTNAME/deployments/DEPLOYMENTNAME'
	at line '1' and column '2306' is defined multiple times in a template. Please see https://aka.ms/arm-syntax-resources for usage details.'.",
    "additionalInfo": [
        {
            "type": "TemplateViolation",
            "info": {
                "lineNumber": 1,
                "linePosition": 2306,
                "path": "properties.template.resources[1]"
            }
        }
    ]
}

}
Expected/desired behavior

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

azd version?

run azd version and copy paste here.

Versions

azd version 1.6.1

Mention any other details that might be useful

Thanks! We'll be in touch soon.

{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.","details":[{"code":"InvalidTemplate","message":"Deployment template validation failed: 'The resource 'Microsoft.CognitiveServices/accounts/AZUREOPENAIACCOUNTNAME/deployments/gpt4chatwithyourdata' at line '1' and column '2306' is defined multiple times in a template. Please see https://aka.ms/arm-syntax-resources for usage details.'."}]}


Community alert incorrect position

It should always be just above the footer, regardless of scroll level. Make sure the width is also handled fine.

Fixed by #41


IS-04 Sender "interface_bindings" for IS-07 Senders

This may be more of a question for IS-04.
The example in Core models - IS-04 highlights - Senders shows "interface_bindings": [ "eth0" ].
Does it make sense for Senders with transports like WebSocket or MQTT to be bound to a particular interface?
If so, in an out-of-band configuration (separate media and control networks) which network would WebSocket/MQTT flows be likely to use?

This is now an issue in IS-05 - https://github.com/AMWA-TV/nmos-device-connection-management/issues/70 - since binding to multiple interfaces in IS-04 probably then requires that we represent the multiple redundant interfaces with multiple 'legs' in IS-05.


Added singularity file for pytorch-geometric

Following #923. I've reworked the example file a bit (for example removing that tmp-directory issue), and removed a few extraneous things.

Thank you very much :)


Add test output to the TAPI progress events

This PR contains an attempt to expose the output from test execution via the Toolin API. This is a requirement for JetBrains to use the TAPI to launch and debug tests.

I don't think it's sufficient to get access to the output when a test is finished. In an IDE, users expect to see output while a test is running.

Fair enough. I guess I need to introduce a brand new child event for the test progress events containing the test output.

The PR now builds successfully. @marcphilipp @big-guy could you please take another look. It would be nice to ship this feature with Gradel 6.0.

@marcphilipp Thanks for the review. I'll respond to your items individually.
I was thinking about adding TestLauncher.addOutputListener(). It should not be hard to add as internally it would use the same event system I've patched in this PR. On the other hand, I don't think it would add much value. Test output is only meaningful if clients know the parent tests/suites/etc.. To identify them, clients need to listen to the test progress events anyway, so it seems actually simpler use progress events only.


Overwriting sob

https://github.com/thejevans/mla/blob/53c503daec0aaefa634a23e1c4f0f982d82fc86e/mla/analysis.py#L126
I think it will go wrong when doing the minimization step but I am not sure why.
I did something like
    splines, sob = preprocessing
    sob_new = sob*np.exp([spline(gamma) for spline in splines])

    return np.log((ns/n_events*(sob_new - 1)) + 1)

you saw this not working?

This has confirmed to be an issue. Your fix is good.


feature: Support paths with .s in them.

Before, lockedFields[fieldName] would blow up if fieldName had a ..

Closing because all instances of this module must share the same uuid.  I might follow up with a fixed PR


Corrected typos

OPS Build status updates of commit 2dea933:
:clock10: Preparing: average preparing time is 1 min(s) 13 sec(s)

OPS Build status updates of commit 2dea933:
:clock10: Incremental building: average incremental building time is 12 min(s) 23 sec(s)

OPS Build status updates of commit 2dea933:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Set-CsOnlineVoiceUser.md
:white_check_mark:Succeeded
View (skype-ps)

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.


An initial Python attempt at splitting images

In order to hopefully allow for faster image loading, 2i2c is letting us set up separate images for Python and R (and possible Python + ML libraries or other massive stuff).
I've started by creating a new directory for a Python image with a few updates to match the current 2i2c environment, and slimmed down further using micromamba.
I've also created a re-usable workflow for building and pushing Docker images, that we can then reference from image/directory specific workflows.
I'm fully expecting needing to tinker on the workflows to get it building and pushing as expected.

I'm gonna merge without review so that I can debug and get 2i2c testing the images.

Thanks. I was going to keep dependency changes minimal at this stage, just so that we can get to the point of testing with 2i2c sooner. I've also had enough weirdness around Python 3.10 to leave that for a later PR.
Of course I also moved to Micromamba as a base at the same time, so my judgement may be lacking.

Good strategy! For the GHA actions bumps we should probably adopt dependabot, not sure if we can enable it only for GHA. The Python 3.10 is not important. I'm mostly curious about what is broken.

I nearly wrote 'thanks, dependabot' You can enable it just for actions, but I would probably set it up for the Docker FROM images too.
Largely some weirdness about types.


IE11 support?

More of a question: Is react-big-calendar supposed to support IE11? I see "IE10+" in the README but a "no"-answer would be fine.
We are hoping to drop support due to all problems, but currently one of our customers is using it. We notice a problem in IE11 with the new 0.19 version and investigating the issue I found that I cannot access the page http://intljusticemission.github.io/react-big-calendar/examples/index.html with IE11 either.

The core library, (add-ons less so) should support ie11 but there is no active testing on it. We're happy to fix stuff as it comes up, the docs page may not work for unrelated reasons

Ok, great.

Managed to find some more info now. It was NaN
In Chrome: totalMin = 720 step = 60 timeslots = 2 numGroups = 6
In IE11: totalMin = NaN step = 60 timeslots = 2 numGroups = NaN

Ok so the problem seems like it's earlier in the totalMin calculation. Thanks for helping track this down, i don't have a lot of access to IE11 at the moment

Yes, the start and end date seems to be invalid. TBC...

Ah, sorry, it seems to be my Date() constructions... String arguments doesn't work in IE. My bad.


Fix compatibility with older Python versions

add a fallback to typing_extensions when importing Self
use pre-3.10 Union types

Hopefully this should fix #17 (at least for 3.9+)

Codecov Report
Attention: Patch coverage is 81.81818% with 2 lines in your changes missing coverage. Please review.

Project coverage is 99.70%. Comparing base (7cbf31a) to head (2c814ed).

Files with missing lines
Patch %
Lines

circuitpython_mocks/_mixins.py
60.00%
2 Missing :warning:

Additional details and impacted files
@@             Coverage Diff             @@
##              main      #18      +/-   ##
===========================================
- Coverage   100.00%   99.70%   -0.30%
===========================================
  Files           15       15
  Lines          677      682       +5
  Branches        56       56
===========================================
+ Hits           677      680       +3
- Misses           0        2       +2

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

I should also add older python versions to the CI workflow for verification.

I have a branch ready for this, but need this merged first.


Fix multipart/form-data requests support

Besides avoiding event.data to read the whole req.body when the content type is multipart/form-data, we need to configure the body parser (raw) to not generate a buffer with the payload.

Hi @diugalde,
I have built the NodeJS images with your changes, do you mind updating your branch so we can run the tests with the new image? The images are in stable/nodejs/nodejs.jsonnet. The new sha256 are:

NodeJS 6: sha256:e72370621155aafe904e38e2c382dd3cd5e4058c7ad8baf9bda0d163c001399e
NodeJS 8: sha256:f4b210a7c45730fec888a8ff9ab853405536a361c2526306659c68487528892b

Also, to ensure that the feature is working, do you mind adding a example as simple as possible in stable/nodejs/examples/? Then, to run that example as part of the tests, you need to add it to the NodeJS Makefile (stable/nodejs/Makefile). You can create two tasks nodejs-multipart and nodejs-multipart-verify and add it to the tasks deploy and test which are the ones executed in the CI. Something like:
diff --git a/stable/nodejs/Makefile b/stable/nodejs/Makefile
index 138c21d..5c659b4 100644
--- a/stable/nodejs/Makefile
+++ b/stable/nodejs/Makefile
@@ -16,8 +16,8 @@ build-all: build6 build8
 push-all: push6 push8

 # Testing jobs
-deploy: get-nodejs get-node-url-zip get-nodejs-custom-port get-nodejs-stream timeout-nodejs get-nodejs-deps get-nodejs-multi post-nodejs get-nodejs-extra-conf
-test: get-nodejs-verify get-node-url-zip-verify get-nodejs-custom-port-verify get-nodejs-stream-verify timeout-nodejs-verify get-nodejs-deps-verify get-nodejs-multi-verify post-nodejs-verify get-nodejs-extra-conf-verify
+deploy: get-nodejs get-node-url-zip get-nodejs-custom-port get-nodejs-stream timeout-nodejs get-nodejs-deps get-nodejs-multi post-nodejs get-nodejs-extra-conf nodejs-multipart
+test: get-nodejs-verify get-node-url-zip-verify get-nodejs-custom-port-verify get-nodejs-stream-verify timeout-nodejs-verify get-nodejs-deps-verify get-nodejs-multi-verify post-nodejs-verify get-nodejs-extra-conf-verify nodejs-multipart-verify

 get-node-url-zip:
        kubeless function deploy get-node-url-zip --runtime nodejs6 --handler index.helloGet --from-file https://github.com/kubeless/kubeless/blob/master/examples/nodejs/helloFunctions.zip?raw=true
@@ -96,3 +96,10 @@ get-nodejs-extra-conf-verify:
        kubectl rollout status deployment/nodejs-extra-conf && sleep 2
        $(eval POD := $(shell kubectl get po -l function=nodejs-extra-conf -o jsonpath="{.items[0].metadata.name}" 2>&1 || true))
        kubectl exec $(POD) -- npm config list | grep foo:bar
+
+nodejs-multipart:
+       kubeless function deploy nodejs-multipart --runtime nodejs6 --handler hello.handler --from-file examples/hello-multipart.js
+
+nodejs-multipart-verify:
+       kubeless function call nodejs-multipart | grep success

That way we can ensure the feature is working as expected and we make sure we don't break it in the future.

Hello @andresmgot ,
I added a simple example and tried to modify the Makefile but I'm getting this error during the ci:
kubectl proxy -p 8085 &
curl \
  		--header "Content-Type:multipart/form-data" \
 		-F "prop=This is a normal prop" \
 		-F<EMAIL_ADDRESS>\
  		localhost:8085/api/v1/namespaces/default/services/hello-multipart:http-function-port/proxy/ |egrep hello.world
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (7) Failed to connect to localhost port 8085: Connection refused
make: *** [nodejs-multipart-verify] Error 1
make: Leaving directory `/home/circleci/project/stable/nodejs'
Exited with code 2

Locally, that's how I did it and it was working. I need to expose the function via http and use curl to perform a multipart request. Do you happen to know a workaround for this?

@diugalde you can try something like:
nodejs-multipart-verify:
	$(eval IP := $(shell minikube ip))
	$(eval TOKEN := $(shell kubectl get secrets -n kube-system  -o jsonpath={.items[0].data.token}))
	curl \
  		--header "Content-Type:multipart/form-data" \
  		--header "Authorization: Bearer $(TOKEN)" \
 		-F "prop=This is a normal prop" \
 		-F<EMAIL_ADDRESS>\
  		$(IP):8443/api/v1/namespaces/default/services/hello-multipart:http-function-port/proxy/ |egrep hello.world

That will be using the minikube IP and the default user to access the service. If the Makefile syntax gives you trouble you can always create a bash script and execute it in the make task.

@andresmgot That seems correct. The ci build is now failing in a previous step (not sure why):
See also: go build, go get, go clean.
make[1]: *** [binary] Error 2
make[1]: Leaving directory `/home/circleci/.go_workspace/src/github.com/kubeless/kubeless'
mv: cannot stat ‘/home/circleci/.go_workspace/bin/kubeless’: No such file or directory
make: *** [kubeless] Error 1
Exited with code 2

The fix is already in master, please rebase to fix your issue

hi @diugalde any chance you can take a look to the required changes? I am preparing a new version of Kubeless and it would be good to include this feature in the NodeJS runtime.

@andresmgot yeah! I'll work on that now so you can included it! Thanks!

@diugalde it's weird, I tried the make tasks in the CI and it says Unauthorized even after using an admin account. Changing the approach I made it work with the following task:
start-proxy:
        kubectl proxy& sleep 2

nodejs-multipart-verify: start-proxy
        curl -v \
  		--header "Content-Type:multipart/form-data" \
 		-F "prop=This is a normal prop" \
 		-F<EMAIL_ADDRESS>\
                <IP_ADDRESS>:8001/api/v1/namespaces/default/services/hello-multipart:http-function-port/proxy/

But the function is returning an error:
*   Trying <IP_ADDRESS>...
* Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 8001 (#0)
> POST /api/v1/namespaces/default/services/hello-multipart:http-function-port/proxy/ HTTP/1.1
> Host: <IP_ADDRESS>:8001
> User-Agent: curl/7.47.0
> Accept: */*
> Content-Length: 312
> Expect: 100-continue
> Content-Type:multipart/form-data; boundary=------------------------e708c902fc29838e
>
< HTTP/1.1 100 Continue
< HTTP/1.1 200 OK
< Content-Length: 26
< Content-Type: text/plain; charset=utf-8
< Date: Fri, 28 Jun 2019 08:30:05 GMT
< X-Powered-By: Express
<
* Connection #0 to host <IP_ADDRESS> left intact
You did not upload a file.

Do you know what could be happening? Are you able to make it work locally with the same image than in the PR?

I found the issue, the CI is not substituting the new images so it's not taking your changes. Let me fix that.

I have landed the fix, with the changes in master and my suggestion with the Makefile this should be ready to be landed.

@andresmgot It's working now! Thank you!

great, thanks!


✨  (next) NICE-57 draft [b]

Change from preview to draft

[x] draftMode
[x] draft get from datasource, do not setCache

This pull request has been deployed to Vercel.

Latest commit:
b81de35

✅ Preview:
https://jeromefitzgerald-lt56tfz9e-jerome5.vercel.app

🔍 Inspect:
https://vercel.com/jerome/jeromefitzgerald/EG6wtnKu9YJgRpNSxbxHm3147NcW

View Workflow Logs

This pull request has been deployed to Vercel.

Latest commit:
bc2cf58

✅ Preview:
https://jeromefitzgerald-a323ngxsz-jerome5.vercel.app

🔍 Inspect:
https://vercel.com/jerome/jeromefitzgerald/En89FtM5w6WKYE7YLJBi7NufZdgE

View Workflow Logs


os/sdk-modifying-coreos: removed repo and cros_sdk instructions

The "option 2" section of the sdk instructions is apparently obsolete. cc @euank

The option 1 text has two instances of can be that can be strengthened now that cork is the only option.  There's also one remaining reference to cros_sdk further down the page.
Also also, there are cros_sdk references in sdk-building-production-images and sdk-tips-and-tricks that we should clean up at some point.

I can modify the cros_sdk references in sdk-building-production-images and sdk-tips-and-tricks in this pr as well, if it is entirely deprecated.

Yeah, let's get rid of it everywhere we can.

ping @sdemos

Sorry, forgot about this pr.
Question for the changes in sdk-building-productions-images - is COREOS_SDK_VERSION used anywhere else? The line with cros_sdk in there seems to imply that cros_sdk is the only thing it's needed by.
Question for the changes in sdk-tips-and-tricks - is there another way to "recreate the chroot prior to a clean rebuild" other than ./chromite/bin/cros_sdk -r?
@bgilbert / @euank for answers. That should entirely remove any references to that tool.

In that context, COREOS_SDK_VERSION is still valid/relevant. cork create will still bootstrap from an existing sdk version, which is still derived from that.
For the second one, I think cork create --replace does the same thing?

This pr should be all set now.

@bgilbert are the new changes satisfactory?

We now have a published cork binary.  Could you update the instructions to cover downloading and GPG-verifying the binary, rather than building from source?

updated to download the cork binary and verify. /cc @bgilbert


UTF-8 URIs are broken by parse_url when locale is set

The parse_url function is not multibyte safe, and was never designed to be, which seems to be why this bug from 2010 has still not been addressed. As mentioned in the comments on that bug, a nicer behaviour would be for parse_url to "treat all extended characters ... as opaque characters and copy them as-is without modification", but I don't see that happening any time soon.
There are a couple of options I can think of to try and support UTF8 URIs in this library;

Use a wrapper for parse_url which URL encodes/decodes extended characters (e.g. in this comment from the manual page)
Manually parse the URL in PHP without parse_url

Or alternatively this library could simply reject URI's with extended characters which aren't properly encoded, as they are technically invalid according to RFC 3986.
Whichever way, it might be worth adding something to the Travis config to run the tests under different locale environments to show how this is reproduced in the unit tests (though this might be a pain, since the available values for the locale are platform dependent).
Originally posted by @Pudge601 in https://github.com/zendframework/zend-diactoros/issues/155#issuecomment-455520479

This repository has been closed and moved to laminas/laminas-diactoros; a new issue has been opened at https://github.com/laminas/laminas-diactoros/issues/9.


Unable to launch provided Devcontainer. Directory ../partners/openai does not exist

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain rather than my code.
[X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

Example Code
Not applicable
Error Message and Stack Trace (if applicable)
=> ERROR [langchain langchain-dev-dependencies 6/6] RUN poetry install -  1.6s

[langchain langchain-dev-dependencies 6/6] RUN poetry install --no-interaction --no-ansi --with dev,test,docs:
1.464
1.465 Directory ../partners/openai does not exist

[2024-05-19T18:27:00.124Z] failed to solve: process "/bin/sh -c poetry install --no-interaction --no-ansi --with dev,test,docs" did not complete successfully: exit code: 1
[2024-05-19T18:27:00.128Z] Stop (30914 ms): Run: docker compose --project-name devcontainer -f /mnt/c/IT/Projects/langchain/langchain/.devcontainer/docker-compose.yaml -f /tmp/devcontainercli-devcontainers/docker-compose/docker-compose.devcontainer.build-1716143189213.yml build
[2024-05-19T18:27:00.129Z] Error: Command failed: docker compose --project-name devcontainer -f /mnt/c/IT/Projects/langchain/langchain/.devcontainer/docker-compose.yaml -f /tmp/devcontainercli-devcontainers/docker-compose/docker-compose.devcontainer.build-1716143189213.yml build
[2024-05-19T18:27:00.129Z]     at Km (/home/devcontainers/.vscode-remote-containers/dist/dev-containers-cli-0.366.0/dist/spec-node/devContainersSpecCLI.js:429:525)
[2024-05-19T18:27:00.129Z]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[2024-05-19T18:27:00.129Z]     at async QtA (/home/devcontainers/.vscode-remote-containers/dist/dev-containers-cli-0.366.0/dist/spec-node/devContainersSpecCLI.js:429:2476)
[2024-05-19T18:27:00.130Z]     at async utA (/home/devcontainers/.vscode-remote-containers/dist/dev-containers-cli-0.366.0/dist/spec-node/devContainersSpecCLI.js:409:3506)
[2024-05-19T18:27:00.130Z]     at async KtA (/home/devcontainers/.vscode-remote-containers/dist/dev-containers-cli-0.366.0/dist/spec-node/devContainersSpecCLI.js:481:3865)
[2024-05-19T18:27:00.130Z]     at async AB (/home/devcontainers/.vscode-remote-containers/dist/dev-containers-cli-0.366.0/dist/spec-node/devContainersSpecCLI.js:481:4807)
[2024-05-19T18:27:00.130Z]     at async hrA (/home/devcontainers/.vscode-remote-containers/dist/dev-containers-cli-0.366.0/dist/spec-node/devContainersSpecCLI.js:661:13255)
[2024-05-19T18:27:00.130Z]     at async lrA (/home/devcontainers/.vscode-remote-containers/dist/dev-containers-cli-0.366.0/dist/spec-node/devContainersSpecCLI.js:661:12996)
[2024-05-19T18:27:00.134Z] Stop (32915 ms): Run in Host: /home/devcontainers/.vscode-remote-containers/bin/f209ce35ef894bd32c12057724e8d1f1139c433f/node /home/devcontainers/.vscode-remote-containers/dist/dev-containers-cli-0.366.0/dist/spec-node/devContainersSpecCLI.js up --container-session-data-folder /tmp/devcontainers-747ad587-40d5-4457-ba1a-99c12d4be9721716143184888 --workspace-folder /mnt/c/IT/Projects/langchain/langchain --workspace-mount-consistency cached --id-label devcontainer.local_folder=c:\IT\Projects\langchain\langchain --id-label devcontainer.config_file=/mnt/c/IT/Projects/langchain/langchain/.devcontainer/devcontainer.json --log-level debug --log-format json --config /mnt/c/IT/Projects/langchain/langchain/.devcontainer/devcontainer.json --default-user-env-probe loginInteractiveShell --mount type=volume,source=vscode,target=/vscode,external=true --mount type=bind,source=/run/user/1000/wayland-0,target=/tmp/vscode-wayland-104b6397-6aed-4445-8184-e94bff82c011.sock --skip-post-create --update-remote-user-uid-default on --mount-workspace-git-root
[2024-05-19T18:27:00.134Z] Exit code 1
[2024-05-19T18:27:00.138Z] Command failed: /home/devcontainers/.vscode-remote-containers/bin/f209ce35ef894bd32c12057724e8d1f1139c433f/node /home/devcontainers/.vscode-remote-containers/dist/dev-containers-cli-0.366.0/dist/spec-node/devContainersSpecCLI.js up --container-session-data-folder /tmp/devcontainers-747ad587-40d5-4457-ba1a-99c12d4be9721716143184888 --workspace-folder /mnt/c/IT/Projects/langchain/langchain --workspace-mount-consistency cached --id-label devcontainer.local_folder=c:\IT\Projects\langchain\langchain --id-label devcontainer.config_file=/mnt/c/IT/Projects/langchain/langchain/.devcontainer/devcontainer.json --log-level debug --log-format json --config /mnt/c/IT/Projects/langchain/langchain/.devcontainer/devcontainer.json --default-user-env-probe loginInteractiveShell --mount type=volume,source=vscode,target=/vscode,external=true --mount type=bind,source=/run/user/1000/wayland-0,target=/tmp/vscode-wayland-104b6397-6aed-4445-8184-e94bff82c011.sock --skip-post-create --update-remote-user-uid-default on --mount-workspace-git-root
[2024-05-19T18:27:00.139Z] Exit code 1
[2024-05-19T18:27:04.194Z] Start: Run in Host: wslpath -w c:/IT/Projects/langchain/langchain/.devcontainer/devcontainer.json
[2024-05-19T18:27:04.204Z] Stop (10 ms): Run in Host: wslpath -w c:/IT/Projects/langchain/langchain/.devcontainer/devcontainer.json
Description
I'm trying to launch Devcontainer with .devcontainer provided in repository using VSCode. Launch failes during poetry install with message Directory ../partners/openai does not exist. This was a fresh clone from repository. No changes were introduced.
System Info
VSCode Version: 1.90.0-insider
OS: Windows_NT x64 10.0.22631

Hi, can you assign this issue to me?


Update Horreum raw client on main

There is a change in the Horreum openapi spec for branch master. Verify that there are no breaking changes.

Nothing changed in the api itself, can close this one


Doesn't work with milkdown v7

Throws an error
index.es.js:14 Uncaught (in promise) TypeError: t.create is not a function
    at P.eval [as inject] (index.es.js:14:1781)
    at placeholder (index.js:12:456)

index.es.js:25 Uncaught (in promise) MilkdownError: Context "s" not found, do you forget to inject it?
    at f (index.es.js:25:1333)
    at b.eval [as get] (index.es.js:14:810)
    at P.eval [as use] (index.es.js:14:2100)
    at P.eval [as set] (index.es.js:14:2168)

The playground is not working after upgrade to milkdown v7 and I have pushed my code in main branch.
PR is welcome!

I think nord goes on editor.config(nord) now? Instead of use

The style of <code>, <img> etc. is still broken though I setting up tailwindcss and some plugins and  according to https://milkdown.dev/docs/api/theme-nord. But the placeholder seems to work correctly.
I have released v0.2.0 for milkdown v7

Seeing this with with 0.2.0
index.es.js:24 TypeError: Cannot read properties of undefined (reading 'waitTimers')
    at eval (index.js:23:19)
    at Generator.next (<anonymous>)
    at eval (tslib.es6.js:93:71)
    at new Promise (<anonymous>)
    at __awaiter (tslib.es6.js:89:12)
    at eval (index.js:22:69)
    at eval (index.es.js:350:23)
    at Array.map (<anonymous>)
    at Ce.eval (index.es.js:346:44)
    at Ce.create (index.es.js:368:20)

Seeing this with 0.2.0
index.es.js:24 TypeError: Cannot read properties of undefined (reading 'waitTimers')
    at eval (index.js:23:19)
    at Generator.next (<anonymous>)
    at eval (tslib.es6.js:93:71)
    at new Promise (<anonymous>)
    at __awaiter (tslib.es6.js:89:12)
    at eval (index.js:22:69)
    at eval (index.es.js:350:23)
    at Array.map (<anonymous>)
    at Ce.eval (index.es.js:346:44)
    at Ce.create (index.es.js:368:20)

fyi i've got the same issue above, using with milkdown v7

Seeing this with 0.2.0
index.es.js:24 TypeError: Cannot read properties of undefined (reading 'waitTimers')
    at eval (index.js:23:19)
    at Generator.next (<anonymous>)
    at eval (tslib.es6.js:93:71)
    at new Promise (<anonymous>)
    at __awaiter (tslib.es6.js:89:12)
    at eval (index.js:22:69)
    at eval (index.es.js:350:23)
    at Array.map (<anonymous>)
    at Ce.eval (index.es.js:346:44)
    at Ce.create (index.es.js:368:20)

Incorrect build of 0.2.0. I have released 0.2.1 and tested in https://stackblitz.com/edit/github-7xktcp?file=src%2Fmain.ts

Nice, it works


Write as mdbook

#02

@kaaatsu32329
Could you try spell checker??
https://www.npmjs.com/package/cspell