Jupyter notebook failed to launch. TypeError: Cannot read property 'toLocaleLowerCase' of undefined

Environment data

VS Code version: 1.29.1
Extension version (available under the Extensions sidebar): Python extension 2018.11.0
OS and version: Windows 10
Python version (& distribution if applicable, e.g. Anaconda): Python 3.6 (on path)
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A
Relevant/affected Python packages and their versions: jupyter notebook server 5.7.2

Expected behaviour
Run notebook cell:
#%%
import requests

Actual behaviour
N/A
Logs
Output from Console under the Developer Tools panel (toggle Developer Tools on under Help)
workbench.main.js:sourcemap:2429 Jupyter notebook failed to launch.  TypeError: Cannot read property 'toLocaleLowerCase' of undefined

workbench.main.js:sourcemap:294 [Extension Host] Failed to get interpreter information for 'C:\Program Files\nodejs\node.exe' SyntaxError: Unexpected token C in JSON at position 0
	at JSON.parse (<anonymous>)
	at d.<anonymous> (C:\Users\klo\.vscode\extensions\ms-python.python-2018.11.0\out\client\extension.js:83:285742)
	at Generator.next (<anonymous>)
	at s (C:\Users\klo\.vscode\extensions\ms-python.python-2018.11.0\out\client\extension.js:83:284981)
	at <anonymous>

workbench.main.js:sourcemap:294 [Extension Host] Python Extension: Error: Jupyter notebook failed to launch.
TypeError: Cannot read property 'toLocaleLowerCase' of undefined

I'm experiencing this issue as well. Running a notebook cell worked last week, so I'm guessing there was a change that is causing the issue.

Looks to be a kernel spec issue. There's a kernel spec that doesn't specify language or path.

You can enumerate your kernelspecs with 'jupyter kernelspec list'.
One of the kernelspecs listed is missing the language or path in the json.
We recently started forcing a kernel spec so that's the likely cause. Our code is not checking that the language element is missing, and hence the crash.

Thanks! I checked the files and sure enough one of them didn't have language set in the json. I added it, updated the extension back to 2018.11.0 and it's working now! Much appreciated!


WIP initial commit of changes, next step is unit tests

https://issues.redhat.com/projects/DBZ/issues/DBZ-1813
@gunnarmorling I havn't implemented the tests yet, but wanted to run this by you first before embarking on that. If you like this implementation I can work on adding in some unit tests that show the different modes.

Sweet I’ll work that out over the weekend and update the Pr!

@gunnarmorling working on this changes and should have something in the next day or two!

@gunnarmorling I'm sure there is a better way to doing the tablefilter portion, so any guidance is greatly appreciated!

@brbrown25, there's quite a few formatting changes/issues. Can you please run mvn process-sources to apply the auto-formatter? Thanks!

[ ] update connector docs
[ ] Add events filtered from publication

@gunnarmorling I’m gonna start the docs Pr this evening and will work out the additional test to show filtered events as well. I was able to remove the context once I figured out things (thanks for the help!). Also the build is breaking but when I’m getting the same failure in the master branch.

@brbrown25, thanks for all the updates; could you ping me once it's done from your side?

@brbrown25, thanks for all the updates; could you ping me once it's done from your side?

It’s good for you to review just let me know any changes and I can make them! Also was wondering is the documentation supposed to be a Pr in the github.io repo as well? Thanks!

@gunnarmorling It’s good for you to review just let me know any changes and I can make them!

Thanks, going to re-review now.

Also was wondering is the documentation supposed to be a Pr in the github.io repo as well?

Nope, just here in the main repo is all that's needed (i.e. what you already did). The website build pulls in the docs from there for the different branches.

@gunnarmorling I've gone ahead and collapsed this down into a single clean commit. I've addressed all of the feedback (thanks so much!) if there are any other tweaks, I can make them. Really excited for this feature!

darn looks like i broke a test, well fix that shortly!

darn looks like i broke a test, well fix that shortly!

There are a few flaky tests. Do the two failing ones pass for you locally?

There are a few flaky tests. Do the two failing ones pass for you locally?
I'm running it now, to verify, when I did it in intellij shouldProduceEventsWhenAlwaysTakingSnapshots would fail when running the whole suite, but running just that test was successful, so i'm running on commandline now to see what happens.

@gunnarmorling confirmed that locally I now get
[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR]   RecordsSnapshotProducerIT.shouldCloseTransactionsAfterSnapshot:286 Values should be different. Actual: idle in transaction
[ERROR] Errors:
[ERROR]   PostgresConnectorIT.shouldProduceEventsWhenAlwaysTakingSnapshots:640->assertRecordsFromSnapshot:1809 NullPointer

Interesting. So I'd suggest you try and a) see whether those tests pass on current master (might have merged something broken accidentally) and if they do, b) to rebase the PR on current master (a good idea anyways) and see how things then look.

Interesting. So I'd suggest you try and a) see whether those tests pass on current master (might have merged something broken accidentally) and if they do, b) to rebase the PR on current master (a good idea anyways) and see how things then look.

ok indeed my most recent commit broke something, it's in sync with master and master passes for me. will get this worked out this evening and ping!

@gunnarmorling master passes for me, i think i may have been out of sync on my branch, checking one more time

The remaining test failure is unrelated. Pushed one commit which hopefully gets rid of it.

The remaining test failure is unrelated. Pushed one commit which hopefully gets rid of it.

Thanks so much! It's always a joy contributing to Debezium, so thanks for all of the help on this.

looks like the build is green, yay!

yeah, indeed. Waiting for @jpechane to do one last review pass and merge. Thanks for your efforts and contribution, @brbrown25!

Woohoo!


привет мир-privet mir-Hello World

hi, tell me, is there any kind of restriction per person? Let's say 1 person will send me 1000 offers for 1 subject. or on all items at once, and the distribution will not come out all will be taken by 1 person.

For now there are no restrictions. This was already suggested in #4, But I don't have time to implement it. Feel free to send PR if you want.


Quality is blurry for face closeups

It'll be fixed once the face #50 upscaler is merged. Until then you can use my fork.


CHANGELOG.md: Update for diff between 1.0.0 and 1.1.0 releases.

Signed-off-by: Philip Tricca<EMAIL_ADDRESS>

I should note that this is fixing up something that was never done for the 1.1.0 release (my mistake). The patches / commits between 1.0.0 and 1.1.0 can be dumped with: git log 1.0.0..1.1.0 for anyone who wants to check the accuracy of the log.


Analyzing hangs

Binary Ninja takes forever to analyze the attached file. It gets stuck at "Analyzing 198/799" and the graph view is unusable, printing "Loading..." when switching to a different function. I have let it run for about an hour without progress.
Im using version 1.0.14 demo.

I can confirm that this fails on the latest development build as well, thanks for the report

It appears to be trying to disassemble a large block of zeros as a function. There is a symbol for the address, so it is likely mistaking a data symbol for a function symbol. The latest dev build does not hang during analysis but does have some UI responsiveness issues when scrolling though the linear view.

Fixed in dev, there was an error in the PE parser


Support other ORMs (Sequel)

Any plans to provide support for other ORMs, namely Sequel (https://github.com/jeremyevans/sequel)?

Hi @gxespino,
This is not on our roadmap since we aren't using this as actively as we used to. That being said I think it could be a great addition to the gem and you're more than welcome to open a PR if you want to!

PRs welcome!  Closing for now.


update overview.md

make some changes as follows:
1.some bold span change to code span.
2. delete some needless new line.

To clean the pr list up a bit, I will close this issue, if you want to update your changes, feel free to submit a new pr


API Endpoint to add a member to an organisation

completing API Endpoints for organization members #645

There is no real need in Gitea for this method as we have already removed from interface as adding user to org members without adding to team does not give anything (including rights to see any private repos etc) as Gitea has a bit different rights model

I see now.
PUT /teams/{id}/members/{username} Add a team member
also adds to the org. I was mislead by the error message "Must be an organization member". It occurred when listing the teams on /orgs/{orgName}/teams.
Closing this.


Add dependabot

https://docs.github.com/en/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically

Nit: Monthly may work better?

sure...


unable to set Typ of Contact Sensor

in Homekit there are different types of contact sensors available, e.g. door or window.
Setting the typ should be possible when creating services.

Hey @andreasgrau thanks for another great suggestion.
I've just taken a look into this and I am afraid the response is very similar to https://github.com/karlentwistle/ruby_home/issues/61. I don't think this is a currently supported feature within the HomeKit Accessory Protocol Specification. As far as I can tell you have to configure the "type" of contact sensor from within the HomeKit API used by HomeKit apps like the Home app on iOS.
HAP specification (page 223)
These are the optional and required characteristics for a contact sensor. I cannot see a type attribute that is available:

Configure type
This is where you can configure the type from within the Home application on iOS:

Test code used:
require 'ruby_home'
RubyHome::ServiceFactory.create(:contact_sensor)
RubyHome.run


clarify how to correctly check that an error is nil

Checking an error or indeed an interface is nil in Golang is confusing and seems to be inconsistent.

spawnStrategy.conclude has to check an TraverseResult.Error is nil and has been implemented in the short term using a simple comparison to nil, wich does work in this instance, but a similar check in different circumstance does not. Where I have opted to use:

!reflect.ValueOf(thisResult.Error).IsNil()

this approach doesn't always work, born out by this proposal I found in golang (I would have liked to comment on this issue but at ths time, it is closed for external comments. They seem to be worried about causing a 'rukus' if they changed the functionality, but isnt the obvious solution just to create a new function, say 'InSafeNil' which returns true instead of panicing and then depricate the old one?).
Here is another example of the simple Error check not working:
func (r *TraverseResult) merge(other *TraverseResult) *TraverseResult {
	// TODO: implement this by combining the results
	//
	if other.Error != nil {
		r.Error = other.Error
	}
	return r
}

When other.Error does not contain an error, the comparison to != nil evaluates to true. So where's the consistency? Why does this somethimes work and sometimes not?
So how to check an error or indeed any interface for nil in a consistent and reliable way?
Also see:

Using IsNil() to check for Interface value
How to check pointer or interface is nil or not in Golang?

See the newly define IsNil function inside utils.


Drag and drop area shows 'dragover-err' class for csv files

Hi,
I am using ng-accept="*.csv" for accepting csv file as input but drop area is using 'dragover-err' class instead of 'dragover'. When i am using ng-accept=".csv" then file is not dropping at all.
Could you please suggest me where i am doing mistake?

ng-accept="'.cvs'"

Thanks @danialfarid, i have already used ng-accept="'.csv'". My problem is 'dragover-err' class added to drop-box instead of 'dragover' when i am dropping csv files.

Can you create a jsfiddle.

@danialfarid , when ever  I use file extensions like "'.csv, .xlsx'" etc 'dragover' class is not worked but instead of file extensions I used mime type of file like "'text/csv, application/vnd.openxmlformats-officedocument.spreadsheetml.sheet'" then 'dragover' class is worked.

Fixed in version 3.1.1.
accept and ng-accept are now acting differently. first one is just for browser filtering, second one is for filtering programmatically.


Remove duplicate paths for core-data/readings by device and value descriptor

Fix #187

Duplicate with https://github.com/edgexfoundry/blackbox-testing/pull/188


This app is on admin panel if yes how to create admin panel?

Describe your issue here.
Steps to reproduce
Tell us how to reproduce this issue.
Expected behaviour
Tell us what should happen
Actual behaviour
Tell us what happens instead
Would you like to work on the issue?
Tell us if you would like to work on this issue

what do you mean by admin panel? What are your expectations for this?

Suppose I want to add more cities or changes description or any other
information from server and after changing the information it should show
on this app so i want admin panel, is this has admin panel?
On Wed 26 Dec, 2018, 10:24 PM Swati Garg<EMAIL_ADDRESS>wrote:

what do you mean by admin panel? What are your expectations for this?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/project-travel-mate/Travel-Mate/issues/562#issuecomment-449993106,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ArR1Mxrn41hgWvVPothP7CfXbmI3vnCeks5u86mngaJpZM4ZhouN
.

you need to set up your own server for this. You can have your database then.
See this repo for setting up the server: https://github.com/project-travel-mate/server

If you need any other info, comment here or join us on slack, or drop a mail


test - Updated index.yml

test - Updated content in index.yml.

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

File
Status
Preview URL
Details

microsoft-edge/index.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Hooks Setup Revision

This is a draft for revising the Hooks Setup Process, after a debate on this subject.
I'm not sure how to handle the Enable/Disable.
The initial idea was to control this by loading (or not) the Hook Service Provider, but I think we need to load it in order to use routines enable/disable.
Maybe any of you wizards have an idea on this?
Ping: @marktopper, @fletch3555, @tnylea
Setup Process

Install Hook
1.1 Download hook
1.2 Load Hook Service Provider
1.3 Run Migrations, Seeders and publish assets

Enable Hook
???

Disable Hook
???

Uninstall Hook
4.1 Prompt User for deleting data
4.2 Un-migrate and delete data

Thank you.

How about this?
Install Hook

Download hook (unless it is already located locally for example when building a hook)
Run migrations
Run seeders
Publish assets
Additional steps can be added by the system itself

Enable Hook

Load service provider

Disable Hook

Unload service provider

Uninstall

Disable Hook
Prompt user for deleting data (for un-migrating, un-seeding and un-publishing assets)
Mark hook as uninstalled
Remove hook (unless locally)

Besides that, I will be adding some more options to the hooks view including buttons like:

Remigrate
Reseed
Republish assets
Un-seed
Un-migrate
Unpublish assets

The power of having the enable/disable option is for the developer to easily disable any hook when debugging some issue.
I personally think it would be a nice idea to still have the the enable/disable option.
I was thinking about handling this by making a separate HookDataProvider which is almost like a service provider, but only with the options supported by the hook system.
This HookDataProvider would include seeders, assets and migrations to run along with a rollback method to un-seed, un-migrate and un-publish assets.

HookDataProvider will do the trick, that's awesome.
Please do it! I'm looking forward to test it!
Then, all hooks will implement that feature, and we have a solid Hook system!
Looks perfect.


improve clean command

in recent PR #56 clean command has been reduced to only clean the output folder.
it could still use some improvements:

[ ] add a dry-run option
[ ] how to cleanup automatically logs?
[ ] support the keep parameter taking values from nimibook config (so that we can avoid cleaning specific files in output folder
[ ] should we reintroduce an option to perform again cleaning of source folder? (we would need keep to support source folder also)

how to cleanup automatically logs?

I don't know what it's worth, but logs are removed at the start of building a document. So if it runs successfully, the old log file will be removed (or rather, it will not be recreated).


[Icon Request] Folder icon for Azure

[ ] I'm sure this issue is not a duplicate.

[ x] I'm submitting an icon request:

Type: folder
Icon Name: Azure
Sample original Icon:
Extensions: ``
Filenames: ``
Language ids: ``

Language Extensions:

More info:
Great to show Microsoft and Azure some love
https://images.duckduckgo.com/iu/?u=https%3A%2F%2Fmspoweruser.com%2Fwp-content%2Fuploads%2F2017%2F09%2Fazure-1.png&f=1

invalid. See #650

Thanks sorry for mistake, tricky to find :)


Docker build error

Server doesn't build.
$ docker-compose up

Sending build context to Docker daemon  7.613MB
Step 1/17 : FROM node:16-alpine as builder
 ---> 51405b97d471
Step 2/17 : WORKDIR /home/node/build
 ---> Using cache
 ---> 88d9a8e1c9ae
Step 3/17 : COPY package.json .
 ---> Using cache
 ---> 303eb67be26d
Step 4/17 : COPY package-lock.json .
 ---> Using cache
 ---> 7ede716cef2c
Step 5/17 : RUN npm install --include=dev
 ---> Running in 9606e6528fce
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
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!   peerOptional<EMAIL_ADDRESS>|| ^17.0.0" from<EMAIL_ADDRESS>npm ERR!   node_modules/@apollo/client
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!   17 more (@reduxjs/toolkit, @testing-library/react, ...)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>|| ^15.0.0 || ^16.0.0" from<EMAIL_ADDRESS>npm ERR! node_modules/react-lottie
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Conflicting peer dependency<EMAIL_ADDRESS>npm ERR! node_modules/react
npm ERR!   peer<EMAIL_ADDRESS>|| ^15.0.0 || ^16.0.0" from<EMAIL_ADDRESS>npm ERR!   node_modules/react-lottie
npm ERR<EMAIL_ADDRESS>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 /root/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2022-11-05T11_22_19_069Z-debug-0.log
1 error occurred:
        * Status: The command '/bin/sh -c npm install --include=dev' returned a non-zero code: 1, Code: 1

I am getting this error, too.  This is being built on the latest release of CentOS 7, and npm v9.1.2 was updated, too.


Add Basic authentication for ClientBuilder

It is currently only possible to add Basic authentication header via basic_auth() method on RequestBuilder.
I would like to add such a feature on ClientBuilder directly, meaning that all requests made with this client would be basic-authenticated.
Currently we can only have this feature by adding a new header and building by ourselves the proper Basic value.
It is something that would be useful to add ? If yes, what should we do when both Basic authentication are set on Client & Request ?

Any chance to see it merge one day ? @seanmonstar


Migrating ParameterHandler to a middleware system

Currently the ParmeterHandlerInterface only allows for a handler to handle or not handle a parameter.
There is no way a ParameterHandler can "wrap" othe parameter handlers. So there is no easy way to write a ParameterHandler that does validation upon the result of other parameter handlers.
This commit moves ParameterMapperInterface to a system of ParameterMiddlewareInterface where parameter middlewares are chained.
We therefore get all the benefits of middlewares when handling parameters.

[x] Migrate to ParameterMiddlewareInterface
[ ] Update doc

Note: this makes https://github.com/thecodingmachine/graphqlite-laravel/pull/12 possible


Hi, can your provide a sample code using python

can you provide a python predication code separately instead of included in training file , so that we can provide any input video. As i am new to ML can not able to retrieve

Hi, sorry for the late response, I read your message today.
Will work on your request tomorrow. Thanks for reaching out.

@raviyellani you can check the repo, I have updated it. Check the readme for instructions.
The Python scripts are in the module directory.

sure will go through it
On Sun, Apr 16, 2023 at 2:13 PM John Pinto @.***> wrote:

@raviyellani https://github.com/raviyellani you can check the repo, I
have updated it. Check the readme for instructions.
The Python scripts are in the module directory.
—
Reply to this email directly, view it on GitHub
https://github.com/JohnPPinto/UCF50_human_activity_recognition_tensorflow/issues/1#issuecomment-1510193143,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABF2G3GPBBKWWB7GNLAFKZ3XBOWJNANCNFSM6AAAAAAWIJVTYQ
.
You are receiving this because you were mentioned.Message ID:
<JohnPPinto/UCF50_human_activity_recognition_tensorflow/issues/1/1510193143
@github.com>

--
Thanking You  & Best Regards

        Ravi Yellani*


Internal error: Cannot read properties of undefined (reading 'tableName')

Seeing quite a few of these errors:
/Users/x/Developer/contra/gaia/apps/contra-api/src/temporal-workflows/routines/invoice/sendInvoiceOverdueFiveDaysReminderEmail.ts
  20:43  error  Internal error: Cannot read properties of undefined (reading 'tableName')  @ts-safeql/check-sql

/Users/x/Developer/contra/gaia/apps/contra-api/src/temporal-workflows/routines/invoice/sendInvoiceOverdueTwoDaysReminderEmail.ts
  23:43  error  Internal error: Cannot read properties of undefined (reading 'tableName')  @ts-safeql/check-sql

Looking at the underlying queries, nothing really stands out as unusual, e.g.
const result = await pool.one(sql.type(InvoiceDetailsShape)`
  SELECT
    pp.client_user_account_id,
    contractor.id contractor_user_account_id,
    contractor.given_name contractor_first_name,
    client.id client_user_account_id,
    client.given_name client_first_name,
    i.total_amount invoice_total_amount
  FROM invoice i
  INNER JOIN paid_project pp ON
    pp.id = i.paid_project_id
  INNER JOIN user_account client ON
    client.id = pp.client_user_account_id
  INNER JOIN user_account contractor ON
    contractor.id = pp.contractor_user_account_id
  LEFT JOIN workspace_team wt ON wt.id = pp.client_workspace_team_id
  WHERE
    i.id = ${invoiceId}
`);

Will debug further and share findings.

The issue here is that you're trying to select two columns with the same name (client_user_account_id).
I'm pushing a fix for the internal error. There was an incorrect lookup when dealing with duplicate columns.

The issue here is that you're trying to select two columns with the same name (client_user_account_id).
I'm pushing a fix for the internal error. There was an incorrect lookup when dealing with duplicate columns and aliases.

oh wow, didn't even notice it!
ts-safeql delivers value yet again.


Malformed slabs get into slab_pool

For some reason malformed slabs (ones without a magic number and garbage data) get into the slab_pool when allocating several.
(gdb) p *list_start

$1 = {slab_magic = 0, size = 802818, alignment = 0, ref_count = -134500188, max_refs = 32767, freelist_start_index = 45228, freelist_end_index = 63483, freelist_buffer = 0x7ffff7fbb0b4,
  allocable_buffer = 0x7ffff7fbb0bc, next = 0x7ffff7fbb0c4, prev = 0x7ffff7fbb0cc}

Fixed on a rewrite.


Feature/judgment tables styles

Changes in this PR:

Made basic style improvements to Judgement content tables that better matched the judgement document PDF.
Added margin above and below the table so it kicked away from the surrounding content.

Trello card / Rollbar error (etc)
trello.com/c/fom57IA8/43-discuss-incremental-improvements-to-the-html-presentation-of-tables
Screenshots of UI changes:
Before

After

[ ] Requires env variable(s) to be updated

Codecov Report

Merging #419 (3fe3591) into main (161a2c4) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #419   +/-   ##
=======================================
  Coverage   77.51%   77.51%
=======================================
  Files          12       12
  Lines         636      636
  Branches       43       43
=======================================
  Hits          493      493
  Misses        131      131
  Partials       12       12

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Hash of file changes after opening with rust-netcdf

Hey everyone,
we've been using this library for a while now at GEOMAR and we've noticed that apparently in some cases the (SHA1-)hash of the file we've opened with the library changes, even though we are just reading from it.
Is this due to some file-locking-flag in the file itself or is it some other problem?
We've also had our application crash for unrelated reasons a few times and ended up with corrupted netCDF-files we were reading from, which refused to be opened for one launch, but worked fine again on the next launch.
Sadly most of the files we've been using are way to big to ever attach them here, but for example this happened with a checkout of the GEBCO-2019-dataset.
Any idea why this could be happening?
Thanks in advance!

Hi @apexys. That sounds like a very bad issue! This library opens files using NC_NOWRITE when using netcdf::open, so such behaviour is definitely unexpected! It looks like we have to find a MRE and report this upstreams to netcdf-c.
What version of hdf5, netcdf-c, and this crate are you using? Any access patterns or behaviours which exacerbates the errors? Are you using the hdf5 or hdf5-sys crates? Are you using multithreading?

I don't think hdf5 got a lock inside the file, it seems to require this from the operating system. I've attempted to replicate using the GEBCO 2020 dataset and using std::process::abort to terminate the program in various places, but no success as of yet.
hdf5 and netCDF does not have any mechanisms to fix corruption, so it is very strange that it should not work for one launch and work for the next. Could there be some hardware errors? Faulty RAM?

Thinking about this further, the file was on an NTFS disk on a Windows 7 machine, so we think it might just be a problem with that system.
For some reason though, the "created" / "last accessed" date is set to the last time the file is "fixed" and the "last changed" date is some time in 2019 which seems plausible.
Weird happnenings.
I'll update this thread when this happens again, we didn't manage to reproduce this issue on Windows 10 or Ubuntu 18.04.


Checkbox click

Hello
I have trouble when clicked to checkbox sometimes node is toggled (open, hide)
How i can disabled it? Need to disable toggle only by checkbox click
Thanks

Read the API docs on the various checkbox plugin settings:
https://www.jstree.com/api/#/?q=checkbox

I trying to change settings
Now it is like
"checkbox" : {
"three_state" : false,
'cascade': 'down',
tie_selection: false,
whole_node: false
},
but it is not helped


Add ContainerRuntimeDisposed Telemetry Event

Use this telemetry event to track container runtime disposes along.
related #3863

/azp where

Closing and reopening to trigger build


Add SameSite support for NancyCookies

Prerequisites

[x] I have written a descriptive pull-request title
[x] I have verified that there are no overlapping pull-requests open
[x] I have verified that I am following the Nancy code style guidelines
[x] I have provided test coverage for my change (where applicable)

Description
Nancy Cookies doesn't support SameSite property. This PR adds SameSite property to cookies. The possible values for SameSite property are defined by an enum SameSite.cs:  Lax, Strict and None.
If the SameSite property is None, the secure value will be set to true automatically. (https://web.dev/samesite-cookies-explained/#changes-to-the-default-behavior-without-samesite)
This change won't break anything, all cookies work as they suppose to work. All the tests are passed and two new tests added to cover the new functionality.
Fix #3002

Nice work on the pr. I think setting the secure value to true automatically isn't the right approach. That should be user set. Not all browsers are doing the none+secure thing. Even if they were it makes the code more obvious if the user is setting it themselves.

Nice work on the pr. I think setting the secure value to true automatically isn't the right approach. That should be user set. Not all browsers are doing the none+secure thing. Even if they were it makes the code more obvious if the user is setting it themselves.

Kinda agree with you. I will change to codes and push them.


Update dependency symfony/web-profiler-bundle to v6.2.2

This PR contains the following updates:

Package
Type
Update
Change

symfony/web-profiler-bundle (source)
require-dev
patch
6.2.1 -> 6.2.2

Release Notes

symfony/web-profiler-bundle
v6.2.2
Compare Source
Changelog (https://github.com/symfony/web-profiler-bundle/compare/v6.2.1...v6.2.2)

bug #48048 Fix dump header not being displayed (HypeMC)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: composer.lock
Command failed: docker run --rm --name=renovate_sidecar --label=renovate_child -v "/tmp/renovate/repos/github/renovate-reproductions/symfony-flex-backend":"/tmp/renovate/repos/github/renovate-reproductions/symfony-flex-backend" -v "/tmp/renovate/cache":"/tmp/renovate/cache" -v "/tmp/containerbase":"/tmp/containerbase" -e COMPOSER_CACHE_DIR -e COMPOSER_AUTH -e BUILDPACK_CACHE_DIR -e CONTAINERBASE_CACHE_DIR -w "/tmp/renovate/repos/github/renovate-reproductions/symfony-flex-backend" docker.io/renovate/sidecar bash -l -c "install-tool php 8.2.0 && install-tool composer 2.5.0 && git stash -- composer.json && composer install --ignore-platform-req='ext-*' --ignore-platform-req='lib-*' --no-ansi --no-interaction --no-scripts --no-autoloader --no-plugins && git stash pop && composer update symfony/web-profiler-bundle --with-dependencies --ignore-platform-req='ext-*' --ignore-platform-req='lib-*' --no-ansi --no-interaction --no-scripts --no-autoloader --no-plugins"
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
fatal: detected dubious ownership in repository at '/tmp/renovate/repos/github/renovate-reproductions/symfony-flex-backend'
To add an exception for this directory, call:

	git config --global --add safe.directory /tmp/renovate/repos/github/renovate-reproductions/symfony-flex-backend


linux-firmware: move ${PN}-cypress-license handling to oe-core recipe

this will make this bbappend a bit more version agnostic
depends on oe-core commits from:
http://lists.openembedded.org/pipermail/openembedded-core/2018-July/153164.html
to prevent including ${PN}-cypress-license package twice in PACKAGES
http://lists.openembedded.org/pipermail/openembedded-core/2018-July/153165.html

Signed-off-by: Martin Jansa<EMAIL_ADDRESS>

I like this PR, definitively looks like the correct approach regarding the license handling :)

@agherzan this PR depends on oe-core commits as the commit message says and those weren't merged yet.
It's ok to keep it if it builds, but I guess it will fail to build.

I can confirm that the builds are failing now:
WARNING: /home/yocto/poky/meta/recipes-kernel/linux-firmware/linux-firmware_git.bb: LICENSE_linux-firmware-bcm43430a1-hcd includes licenses (Firmware-cypress) that are not listed in LICENSE
WARNING: /home/yocto/poky/meta/recipes-kernel/linux-firmware/linux-firmware_git.bb: LICENSE_linux-firmware-bcm4345c0-hcd includes licenses (Firmware-cypress) that are not listed in LICENSE
Parsing recipes: 100% |###########################################################################################################| Time: 0:01:10
Parsing of 2140 .bb files complete (0 cached, 2140 parsed). 3026 targets, 323 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
ERROR: Nothing RPROVIDES 'linux-firmware-cypress-license' (but /home/yocto/poky/meta/recipes-kernel/linux-firmware/linux-firmware_git.bb RDEPENDS on or otherwise requires it)

If the necessary commit in OE-core is coming soon, I think the best approach is simply to wait for it, less hassle. Master is supposed to be unstable anyway and accidents happen =).

@hhromic that is quite strange as the builds did pass. Maybe it got merged afterwards?

@hhromic @agherzan It's not yet merged in oe-core/master (nor in master-next).
If all 3 commits are merged to oe-core as they are now, then I have one more change for meta-raspberrypi as shown in:
https://github.com/shr-project/meta-raspberrypi/commits/jansa/firmware-master

@agherzan, the builds you mention that passes (I assume the yocto-ci ones?) include the package linux-firmware-bcm43430? I suspect they don't and hence they do not trigger the failure. My basic build local.conf for the test is:
MACHINE = "raspberrypi0-wifi"
IMAGE_INSTALL_append = " linux-firmware-bcm43430"

And the BitBake env is:
Build Configuration:
BB_VERSION           = "1.39.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "debian-9"
TARGET_SYS           = "arm-poky-linux-gnueabi"
MACHINE              = "raspberrypi0-wifi"
DISTRO               = "poky"
DISTRO_VERSION       = "2.5+snapshot-20180720"
TUNE_FEATURES        = "arm armv6 vfp arm1176jzfs callconvention-hard"
TARGET_FPU           = "hard"
meta
meta-poky
meta-yocto-bsp       = "master:b0f2f690a3513e4c9fa30fee1b8d7ac2d7140657"
meta-oe
meta-python
meta-multimedia
meta-networking      = "master:6a0efef15cd625d4fb4f60e2235450de0222c357"
meta-raspberrypi     = "master:c7999e8c2f04385f34877aa9c549ed61c8bcf1a1"
meta-wpe             = "master:efc21adcbf38507307ba2d4f3329882028304196"

@shr-project do you have any idea when would that land in oe-core?

@rossburton any estimate on when the 3 linux-firmware from me in last week might land in oe-core?

They're just landing in mut now so this week.

Thanks guys.

Thanks indeed. I will keep an eye and report when the builds are succeeding again.


DeployerSuite.TestServiceEvents timed out waiting for deployment event

FAIL: test_deployer.go:156: DeployerSuite.TestServiceEvents

++ 21:26:15.570 created app nightingales-lead-harburn (4d696b174bf14348a94fdcf59f28889b)
++ 21:26:15.691 waiting for job events: map[echoer:map[up:2]]
++ 21:26:15.732 got job event: echoer 82c487b0-a6c8d32ebc5b490cba20d4790d6f0e49 starting
++ 21:26:15.972 got job event: echoer db7b6395-d9121ae3c3a649eea05c304c93a63115 starting
++ 21:26:17.071 got job event: echoer 82c487b0-a6c8d32ebc5b490cba20d4790d6f0e49 up
++ 21:26:18.542 got job event: echoer db7b6395-d9121ae3c3a649eea05c304c93a63115 up
++ 21:26:18.542 waiting for 2 echo-service services
++ 21:26:18.544 got echo-service service up event
++ 21:26:18.865 got echo-service service up event
++ 21:26:18.939 waiting for 9 deployment events
++ 21:26:31.229 got deployment event: echoer starting
++ 21:26:32.549 got deployment event: echoer starting
test_deployer.go:176:
    waitForDeploymentEvents(t, events, expected)
test_deployer.go:95:
    t.Fatal("timed out waiting for deployment event")
... Error: timed out waiting for deployment event

https://ci.flynn.io/builds/20150311212252-98a24393

This looks like a genuine timeout, the deployer took ~24s to start the two echoer jobs (and the test has a timeout of 15s):
t=2015-03-11T21:26:23+0000 lvl=info msg="starting all-at-once deployment" app=deployer deployment_id=534c3ba70d044a15a79b9beef6992fe1 app_id=4d696b174bf14348a94fdcf59f28889b fn=allAtOnce
t=2015-03-11T21:26:23+0000 lvl=info msg="received deployment event" app=deployer fn=HandleJob deployment_id=534c3ba70d044a15a79b9beef6992fe1 app_id=4d696b174bf14348a94fdcf59f28889b strategy=all-at-once status= type=echoer state=starting
t=2015-03-11T21:26:31+0000 lvl=info msg="received deployment event" app=deployer fn=HandleJob deployment_id=534c3ba70d044a15a79b9beef6992fe1 app_id=4d696b174bf14348a94fdcf59f28889b strategy=all-at-once status= type=echoer state=starting
t=2015-03-11T21:26:31+0000 lvl=info msg="creating new formation" app=deployer deployment_id=534c3ba70d044a15a79b9beef6992fe1 app_id=4d696b174bf14348a94fdcf59f28889b fn=allAtOnce release_id=7c0553670d9842909543e993130e9fa8 processes=map[echoer:2]
t=2015-03-11T21:26:32+0000 lvl=info msg="waiting for job events" app=deployer deployment_id=534c3ba70d044a15a79b9beef6992fe1 app_id=4d696b174bf14348a94fdcf59f28889b fn=allAtOnce release_id=7c0553670d9842909543e993130e9fa8 expected=map[echoer:map[up:2]]
t=2015-03-11T21:26:34+0000 lvl=info msg="got service event" app=deployer deployment_id=534c3ba70d044a15a79b9beef6992fe1 app_id=4d696b174bf14348a94fdcf59f28889b fn=allAtOnce release_id=7c0553670d9842909543e993130e9fa8 job_id=8ac46255d2db4fac908962aa7c039e47 type=echoer state=up
t=2015-03-11T21:26:34+0000 lvl=info msg="received deployment event" app=deployer fn=HandleJob deployment_id=534c3ba70d044a15a79b9beef6992fe1 app_id=4d696b174bf14348a94fdcf59f28889b strategy=all-at-once status= type=echoer state=up
t=2015-03-11T21:26:36+0000 lvl=info msg="got service event" app=deployer deployment_id=534c3ba70d044a15a79b9beef6992fe1 app_id=4d696b174bf14348a94fdcf59f28889b fn=allAtOnce release_id=7c0553670d9842909543e993130e9fa8 job_id=6e49bb332d9c42128d2623d50309d815 type=echoer state=up
t=2015-03-11T21:26:47+0000 lvl=info msg="received deployment event" app=deployer fn=HandleJob deployment_id=534c3ba70d044a15a79b9beef6992fe1 app_id=4d696b174bf14348a94fdcf59f28889b strategy=all-at-once status= type=echoer state=up

I am not sure why the deployer was so slow, maybe just really high load in the CI server, should we maybe up the timeout to 30s?

Closing, this test failure does not appear in the CI logs dating back to May 1st.


thunderbird: huge closure size

It got a huge closure size.  Jump happened here:

91.1.0: 0.5 G
91.1.1: 3+ G

https://hydra.nixos.org/job/nixpkgs/trunk/thunderbirdPackages.thunderbird.x86_64-linux#tabs-charts
On a quick glance, it's mainly due to dragging lots of toolchain packages, rustc in particular:
63992   /nix/store/9wxxikq0iqsq3jig60yzal77z2q2w2xv-llvm-13.0.0
85376   /nix/store/fkzla307l4mlcvfyshsrccwl7szihx2z-python3-3.9.6
180124  /nix/store/a87yinndp3fgpxxfxb9fyr9aln5yzsr7-gcc-10.3.0
197504  /nix/store/n3gwwqwpsimwmzgj5pfqbl6ypf2mqxqp-thunderbird-unwrapped-91.3.1
300648  /nix/store/jicwsjh2r4s2048i1manh4403mzijls9-clang-13.0.0-lib
370932  /nix/store/rn4hqvzb9w4ks83cf6lxpwqr97sqkqf0-llvm-13.0.0-lib
797792  /nix/store/449lmdsx8dv2q5fn4xbkxk51d4cg2zih-rustc-1.56.1

/cc other likely interested people: @lovesegfault, @taku0.

firefox and firefox-esr don't suffer from this, by the way.

This may be relating to no-buildconfig-90.patch (https://github.com/NixOS/nixpkgs/pull/138358).


chore: make test prefix unique per run

We're seeing a bunch of seemingly random 404 errors in our CI system test job. I believe this is because we now have to 2 system-test jobs and our test prefix is not unique. I was going to use uuid but doing so puts us over the character limit.

Ok! I figured out what is going on. We shouldn't change the prefix that we filter on. We use that to delete accidentally-created, stale datasets from previous test runs. Instead, we should only delete ones that are > 24 hours old, for example. That way, we'll avoid parallel CI-run collisions.


Update GitHub Pages

Summary
As we're still relying on the master branch for GitHub Pages, this pull request merges the upstream document changes in the main branch.
Requirements (place an x in each [ ])

[x] I've read and understood the Contributing Guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.

After merging this PR, I noticed that the master/docs GitHub Pages while having another default branch doesn't work at least for this repository. I forgot to take a screenshot but the repository admin page just showed a warning message saying "Your site is having problems building: Unable to build page. Please try again later.".
For now, I've reverted the default branch from main to master and now the pages went back to normal. We'll contact GitHub support and will keep using the master branch for a while.

I've figured out this issue doesn't occur if we use GitHub's built-in Jekyll support.
I like using Sphinx very much, but it may be good timing to switch the current way to it. The document pages are deployed to https://python-slackclient.readthedocs.io/en/latest/ as well. If we move to Jekyll, we need to take care of the compatibility there too.


Add AES encrypt/decrypt support for SE05X on Arduino with two example sketches

Hello,
I used the se05x_APDU_apis.h function for block cipher to implement a demonstration example sketch for AES encryption and decryption. I found AES encryption with secure element nowhere (looked for days/hours) and decieded to do it by myself.
Please add this
kind regards

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

How to sign the license agreement?

OK, the building process failed with
'class SE05XClass' has no member named 'AES_ECB_encrypt'
'class SE05XClass' has no member named 'AES_ECB_decrypt'
'class SE05XClass' has no member named 'writeAESKey'; did you mean 'writeSlot'?

but this are exactly the 3 functions I added to SE05X.c / SE05X.h library.

@jowin202 test failures on the stable version arduino:renesas_portenta:portenta_c33 are expected (since the APIs are not there yet :wink: ). The test that shouldn't fail (and passes indeed) is on arduino-git:renesas:portenta_c33
Waiting for @pennam review but it looks good to me :+1:

Hello,
Just a question: Will this pull request be merged into the original repository (and when)? I would like to do another pull request for HMAC support, but I'm not familiar with github and the branch-things. So I would like to clear my fork and make a completely new pull request.
Kind regards

Oh I see the changes are already here now. Yes, I added HMAC to my personal fork, but I don't know if this is working and ready for being included into the main branch.

Ok, so i will take  your first two commits open a new pr and merge them into main. After that when code is ready you can open a new PR for HMAC support.

Ahh ok. I have 2 commits in this pull request
add AES:       2f96751419e9a012eb0531a6468f3e9d13b64c6c
add HMAC:  336826e0cf2254a6e490608b25541a2ed8cb99c9
Hopefully they can be included into the arduino lib

is also https://github.com/arduino/ArduinoCore-renesas/commit/336826e0cf2254a6e490608b25541a2ed8cb99c9 ready? It was not included in the original PR and i've understood you are not sure it is working.

Yes, I added HMAC to my personal fork, but I don't know if this is working and ready for being included into the main branch.

is also 336826e ready? It was not included in the original PR and i've understood you are not sure it is working.

Yes, I added HMAC to my personal fork, but I don't know if this is working and ready for being included into the main branch.

It’s also ready from my side. I haven’t figured out how to make a new pull request.


Gzip messages before base64 encoding

Summary

Reduces the message payload by gzipping the cloud-info-provider output before encoding it and sending to AMS

Related issue : #144

Not to be merged before AppDB implements the gzip support!


Only get Metadata

Is ist somehow possible to only download the metadata, without the pictures? For example a whole profile and only the metadata for each post?

Hey @boerninator
Sure thats easy use these parameters:
--no-pictures --no-videos --no-profile-pic --no-captions --metadata-json
If you dont want compression than add:
--no-compress-json
Cheers

Hey @flipso
thanks for the answer! Do you also know how I could call the instaloader as an object in my own python script? New into programming and could not figure it out from going through the .py files on GitHub...

Hey @boerninator,

Please close the issue because we solved the problem.
Instaloader have many Commandline options. Read the docs carefully before you start coding:
https://instaloader.github.io/cli-options.html
Of course you can create your own instance aka object of instaloader in your code.

here's code for creating a instaloader instance:
import instaloader
L = instaloader.Instaloader()

you should consolidate the docs first: https://instaloader.github.io/codesnippets.html could be a entry point for your purpose.  But not try to use "likes-of-a-profile-ghost-followers" section because Insta restricted. I have mentioned these in #860
Feel free to ask for help via email if you have problems.
Cheers mate


API: Show/Hide additional y axis

Hi,
I want to dynamically show/hide the additional y2 axis, as it may not be needed anymore after unloading data or before loading any data.
Currently, after I unloaded all data for the y2 axis, the y2 axis is still displayed, which is unnecessary and confusing.
The following jsfiddle illustrates the problem:
http://jsfiddle.net/nullundnix/fLgpu3br/4/
Is it already possible to achieve this or can it be achieved by changing parts of c3.js?
Any help would be greatly appreciated.

Hi,
Your solution looks nice. It's a pluggable approach we intended and I think it seems better to keep this as a plugin at this moment because we are not sure whether this case is usual and it can keeps c3 smaller. Additionally, I'm planning to separate some functionalities, including internal functions and external apis, to make c3 simpler, smaller and more pluggable. Anyway, I'll make some space to add plugins, then add your code there.

+1 , I need this functionality dynamic

yes please +1

Could use this as well +1

+1 Has this been done?

can someone give some update on this please?


🐛 Fix max_length for unicode strings

Change Summary
Update pydantic-core and add tests for max_length behavior with unicode characters
Related issue number
Fix #6542
Checklist

[x] Unit tests for the changes exist
[ ] Tests pass on CI and coverage remains at 100%
[ ] Documentation reflects the changes where applicable
[ ] changes/<pull request or issue id>-<github username>.md file added describing change
(see changes/README.md for details)
[ ] My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

Depends on https://github.com/pydantic/pydantic-core/pull/758

please review


[Bug] When dynamically setting series.markArea in SVG mode, if you set markArea after updating the data, it will not be rendered.

Version
5.4.2
Link to Minimal Reproduction
https://codesandbox.io/s/distribution-of-electricity-forked-209l2z?file=/index.js
Steps to Reproduce
Here's how to reproduce the bug.

Click the "Mark Update" button at the bottom of the chart.
Then click the "Data Update" button to update the data.
Click the "Mark Update" button again to confirm that the Mark Area is not displayed on the screen.

This bug is not reproduced in canvas. If you change the render properties to "canvas" at the top and proceed with the same procedure above, the Mark Area will output normally.
Current Behavior
In SVG mode, you want to set the mark area dynamically regardless of the data update, but in the current version, you cannot set the mark area dynamically after updating the data.
To output mark area, you must clear ECharts, then reset all chart options and set Mark Area. This bug does not appear in Canvas mode; it only works normally in Canvas mode.
Expected Behavior
We request a modification so that the mark area can be dynamically printed regardless of the data update even in svn mode.
Environment
- OS:Window 10
- Browser: Chrome 112.0.5615.138
- Framework: None

Any additional comments?
No response

not-a-bug
Demo Code

not-a-bug Demo Code

What I want is to set up the Mark Area after updating the data. The example you made is different from the problem I found.
Try to set the mark area as shown below after updating the data. It works on canvas, but not on svg.
setTimeout(() => {
  time = doTime(40);
  xa.data = time;
  series.data = [
    3200,
    2280,
    2250,
    2620,
    2730,
    3040,
    5150,
    5040,
    400,
    390,
    380,
    390,
    400,
    500,
    600,
    750,
    800,
    700,
    600,
    400
  ];

  myChart.setOption({
    xAxis: xa,
    series: series
  });
}, 1333);

setTimeout(() => {
  series.markArea = {
    itemStyle: { color: "pink" },
    data: [[{ xAxis: time[2] }, { xAxis: time[3] }]]
  };

  myChart.setOption({
    series: series
  });
}, 5000);

cannot reproduce, works fine with canvas and SVG.
Please reply with fully reproducible code.
NB: please close issue if problem solved.

Thanks for the quick check. Also, the method you gave will be of great help in solving my problem.
Thanks again, hopefully this bug will be fixed in the future.

a better solution with replaceMerge instead of replace - Demo Code


Support marker animations

It would be amazing in my opinion if markers could have animations. For example adding a modifier to a marker to make it pulse. I'm not sure if it is possible, but it would be a great addition to this amazing project.

@MarcoCaloiaro Thank you for opening this issue. 🙏
Please check out these other resources that might help you get to a resolution in the meantime:

Support Console - If you have a support contract.
Discord - chat with other developers
StackOverflow - use the google-maps tag
Google Maps Platform issue trackers

This is an automated message, feel free to ignore.

This would be a feature request for the Maps SDK for Android, which is tracked in its public issue tracker. Please "star" the feature request on this ticket to upvote it and receive updates about the request.


Update metadata for database schema

Update the database schema to support the new fields:

[ ] https://github.com/chanzuckerberg/cryoet-data-portal/issues/66
[ ] #67
[ ] #68
[ ] #69
[ ] #70
[ ] #71
[ ] #74

@manasaV3 it seems like this is treated as an Epic so i added an Epic tag. Jessica added points directly to 67,68,69 which were added to the sprint queue today. would it make sense to remove the points on the epic then?


Improve the readme

Update of the readme with all the progress made in this project.

Great work, the read-me file is very descriptive. You can go ahead and merge.


Update documentation for setting up the backend services

Backend services is not a generic concept. This project was meant to perform project interaction in a generic manner and the ideas are outdated. This will be archived soon.


[Bug] Displayed RGB Value Incorrect

What is the bug?
Beginning with Version 4.6.0, the RGB value displayed in Hex in the small window that follows the pointer (selector) on the screen is actually displaying RRB rather than RGB. The RGB value displayed in hex does not match the adjacent RGB value displayed in Decimal or the the corresponding hex value displayed on the main Picker > Selector window.
This problem appears to be a regression error introduced in Version 4.6.0. It does not affect Version 4.5.0.
How to reproduce the bug?
Start a selection in either version 4.6.0 or 5.1.0 and move the pointer over different colors. Note that in the RGB value displayed in hex adjacent to the pointer, the R and G components  always have the same value and that the G value is actually mirroring the R value. Compare the values in hex to the values in decimal and you will note the values of the Green components do not match. The RGB value in hex also does not match the correct value in hex on the ColorPicker main window.
Screenshots
No response
Operating System
Windows 11
What is the version of the operating system?
Windows 11 Home Version 22H2 (OS Build 22621.1413)
What is the version of the software?
4.6.0 and 5.1.0

Thank you for reporting this issue! It should now be resolved starting with version <IP_ADDRESS>4.


Use task arena instead of embassy-executor's nightly feature

Gets our CI green again, closes #1308.

This really tripped me off, I was getting this (leaving it here so that others can find it easily):
error: concrete type differs from previous defining opaque type use
  --> src/main.rs:43:1
   |
43 | #[embassy_executor::task]
   | ^^^^^^^^^^^^^^^^^^^^^^^^^ expected `writer::Fut`, got `impl Future<Output = ()>`
   |
note: previous use here
  --> src/main.rs:43:1
   |
43 | #[embassy_executor::task]
   | ^^^^^^^^^^^^^^^^^^^^^^^^^
   = note: this error originates in the attribute macro `embassy_executor::task` (in Nightly builds, run with -Z macro-backtrace for more info)

error: could not compile `rust` (bin "rust") due to 1 previous error


fix links on README

In response to issue https://github.com/gql-dart/gql/issues/200

The gql depends on cat using a local path and not version  https://github.com/gql-dart/gql/blob/master/gql/pubspec.yaml#L14
Which is causing multipack to install yaml 3.1.0 insteade of yaml 2 which in return break the tests.
@klavs @micimize should the version of cat be fixed int the specified file?


ArchLinux32, Etcher i686

Etcher version: N/A
Operating system and architecture: Archlinux32.org i686
Image flashed: N/A
Do you see any meaningful error information in the DevTools? N/A

Hey guys, I was wondering if you guys control the AUR entry for Etcher or not? It would seem that it no longer supports 32-bit, about a month or two ago the unofficial archlinux32.org sprouted up & is now running great, at least in my opinion. I was wondering if you guys could make an Etcher AUR entry for i686 arch. Great program btw! I've been using Etcher for quite a while now, I think since it came out, I was one of the ones asking for a Fedora port too long ago :P

I'm pretty sure we had a similar issue on here before, but can't find it anymore...
Either way – we currently do not have control over the AUR packages for Etcher, and I'm not sure who it was who's making them. We were recently discussing this topic though, and thinking about providing more packages directly.

Is there a way to install Etcher-gui with NPM? Or is it etcher-cli only that way?
Thank you for the speedy labels Jhermsmeier, I love this program & I love your speedy support even more!
It would be nice if there were a way to build it from the git repo, like a makefile or something that would work universally on all Linux distros, excuse my ignorance if this is already possible but last I checked I don't think it was. Perhaps it could be added to 'pip' the python-pip thing?
I've never made an AUR entry before but I would gladly give it a shot! Maybe I could just copy the PKGBUILD from the other one?
And yeah I don't know what happened to that first "issue" but I remember seeing it a while ago... Odd how things sometimes just vanish.
As far as nonfree stuff goes, is Etcher 100% free software? I'd like to get Etcher added to Parabola & Archlinux32.

Looking through my emails, it seems the most recent AUR discussion was in #2007 , but it looks like the person who opened that issue ( @kenny-wettlaufer ) actually deleted it (I didn't even know you could do that!) rather than just closing it.

Hmmm, or maybe Kenny deleted his account, which also automatically deleted all the Etcher issues he created? :-/ ( #1964 , #1999 and #2007 )

Oh wow, didn't know that deleting your account makes everything disappear :/

It would be nice if there were a way to build it from the git repo, like a makefile or something that would work universally on all Linux distros

@Jakecheslekov See https://github.com/resin-io/etcher/blob/master/docs/CONTRIBUTING.md (although note that there's currently a step missing #2079 )

As far as nonfree stuff goes, is Etcher 100% free software?

https://github.com/resin-io/etcher/blob/master/LICENSE


Show Storage configuration on admin configuration page

Moves storages to a manager and adds their configuration to the admin page
Signed-off-by: Andrew Thornton<EMAIL_ADDRESS>

This is in progress for a while now, I'm closing it to avoid stale pull requests. Please reopen when it's ready for review.


Case sensitive; editorconfig spec says it should not be?

Atom 1.23.1
Atom EditorConfig 2.2.2
Involved .editorconfig-files
root = true

[*]
charset = utf-8
end_of_line = lf
insert_final_newline = true
trim_trailing_whitespace = false
indent_size = 4
indent_style = tab

[vagrantfile]
indent_size = 2
indent_style = space

Directory structure
.editorconfig
Vagrantfile

Noticing that vagrantfile does not match the file name of Vagrantfile, though, the docs say:

Currently all properties and values are case-insensitive. They are lowercased when parsed.

Thanks!

The cited sentence applies for properties and their values, not sections. You're welcome.

Ahhh, you are right! Sorry that I did not catch that myself.
In fact, there's no reference to the case sensitivity of sections. I'll follow up with EditorConfig repo/folks.
Thanks again!

You're welcome - i wasn't aware this could be an issue. Happy holidays! 🎄


Support for PySD in Python 3.x

Sometime in the near future we should figure out how to support both python 2 and python 3.
There seem to be two major pathways:

Maintain the codebase in python 2 and use tools like 2to3 or modernize or futurize in order to generate python 3 code from the python 2 base.
Maintain the codebase in python 3, and use tools like python-future to allow imports into python 2 environments.

For now I'm leaning towards the first option, as that's where the codebase is currently. If it turns out that a lot of the libraries we want to interface with for model analysis require 3, then we can change strategy.
Dev pathway for this probably looks like creating a fork of the current, non-subscripted master branch to to work in. It'll be simpler than trying with the subscripted version, at least until that is cleaned up. Then we can offer a python 3 version of the current codebase on pypi, and repeat the process when we're ready with the subscripted branch.
I expect we'll need to generate some sort of script to run the conversion tools and place new files in their own (python3) directory. Then we'll need to include the conversion and python 3 execution in the unit tests, so that when we make changes in the python2 codebase, we know they don't break the python3 implementation.

Thinking now that we do use python3 compatible code with import x from __future__.
Would be good to set up a Tox testing framework on Travis to check against.

Resolved this by writing code that was 2/3 compatible. Tests on https://github.com/JamesPHoughton/pysd/commit/158716b5841da981cc6510d29d46a22725d26be8 pass both 2.7 and 3.5.

Is it Py3-compatible? The documentation's still like "PySD is built on python 2.7, and may not work as advertized on 3.x." Also, the whole lot of manuals and examples is based on python2, I believe.

Yes, you should be able to run on python 3. I haven't gotten around to updating docs (classes, research, etc.). If you've got an interest in helping with the docs, though, I'd love to have the help!

Yes, James, I would surely be glad to help with the docs. I have noticed some points that I would expand and/or rectify. How would I do that? And thank you for this unique piece of work, indeed.

I'm going to move the discussion to: https://github.com/JamesPHoughton/pysd/issues/123, as this work deserves it's own issue. =)


High-Scale IPcache: Chapter 3

This is in the context of the high-scale ipcache feature described at https://github.com/cilium/design-cfps/pull/7.
This pull request extends the datapath to be able to encapsulate and decapsulate the special VXLAN tunnel of high-scale ipcache. In this special tunnel, the outer IP addresses are the same as the inner IP addresses; the encapsulation header is just used to carry the source security identity.
This encapsulation therefore allows us to enforce ingress network policies in high-scale ipcache mode. The end-to-end test will however be updated in a separate pull request to reflect that because we still need https://github.com/cilium/cilium/pull/25436 to populate the World CIDR map (see first commit).
Updates: https://github.com/cilium/cilium/issues/25243.
Support ingress network policies in high-scale ipcache mode.

/test

/test

/test-vagrant

/test-vagrant

/test

LGTM for agent-related changes. One question: have you considered adding the new worldcidrsmap to the maps cell in pkg/maps? This could ease the config options management and the testing. Might be something to consider for a follow-up PR.

Yep, I've created  to track this. It doesn't look that trivial of a change so I'd rather have that as a follow up rather than blocking this PR and subsequent ones on this.

/test

/test-vagrant

/test-vagrant

/test

/test


Adminservlet is not done

@Adela-aman please merge your part of the code to the main branch

already done


DataBuffer add test coverage

In order to improve the test coverage of the code base of libGDX, this pull request is created.
In this pull request, the following has been done to the file utils/DataBuffer:

Added the test coverage

The code coverage has been improved as follows

File
Class, %
Method, %
Line, %

utils/DataBuffer (old)
0%
0%
0%

utils/DataBuffer (new)
100%
100%
100%

Tests add to the maintenance burden of the library and should only be added for things that are complex or relatively easy to break when changed. It is not a goal to have test coverage for all lines of code. I would say DataBuffer does not need tests.


[Events. Event preview card] Authorized User is unable to Join the event by clicking Join Event button

Environment: Mac OS High Sierra: Version 10.13.6, Google Chrome: Version 105.0.5195.102
Reproducible: always
Build found: 11.09.2022
Steps to reproduce:

Go to https://www.testgreencity.ga/GreenCityClient/#/  and sign in
Go to "Events" page
View events preview cards and find the "Event" that is not created by current user
Click "Join Event" button on the "Event preview card"

Actual result:
User can not join the event:
"Join Event" button is not replaced with "Cancel Request" button
"Event" is not aded to "My Events" page
Expected result:
User joined the event:
"Join Event" button is replaced with "Cancel Request" button
"Event" is aded to "My Events" page
User story and test case links
[User story] https://github.com/ita-social-projects/GreenCity/issues/3374
[Test case] https://jira.softserve.academy/browse/GC-3568

not reproducible


Removes redunant code and allows override query relation in descendan…

Q
A

Is bugfix?
no

New feature?
yes

Breaks BC?
no

Tests pass?
yes

Fixed issues

Sometimes it's necessary to change default behavior for relation queries.
Example:
I have created a MultiTenantRecord where ActiveRecord::find() must be overrided, like:

public static function find()
{
    $identity = Yii::$app->user->identity;
    if ($identity instanceof TenantInterface) {
        return parent::find()->where([static::tableName().'.tenant_id' => $identity->getTenantId()]);
    } else {
        throw new NotSupportedException("Identity does not implements TenantInteface");
    }
}

but this should be occurs only "master" record not for relation.
Then this allows customize query for relation

Sorry, i removed my fork accidentally, i will redo the changes in another PR


add pseudonormal

This could use a counterexample to https://topology.pi-base.org/theorems/T000401
According to https://dantopology.wordpress.com/2014/02/17/pseudonormal-spaces/ we could add $\omega_1\times(\omega_1+1)$.

I added T404 [pseudonormal + countable ==> normal] as another basic result.
Both T404 and T401 are "immediate from the definitions", so they have no refs.  Is a ref needed in such a case?  If yes, we could add just a ref to the definition.
I have expanded the README for the property itself (https://topology.pi-base.org/properties/P000165).  The reference from Wikipedia did not seem very good in this case, so I added a few.  The book "Pseudocompact topological spaces" seems pretty interesting, but can you fill our the MR field?
See p. 8: https://books.google.com/books?id=fsRlDwAAQBAJ&pg=PA8&dq=pseudonormal+topology&hl=en&newbks=1&newbks_redir=0&sa=X&ved=2ahUKEwj78rLp8rmAAxXEEVkFHVTVD7kQuwV6BAgIEAY#v=onepage&q=pseudonormal topology&f=false
That page mentions a few other things like:

countably compact ==> pseudonormal
pseudonormal + pseudocompact ==> countably compact

We should check that and add it maybe in another PR.

Hmm, pi-base tells me right away that the last two results are not true, even for Hausdorff spaces. Not good.

@prabau in that book every space is considered to be Tychonoff. Author mentions that

in that book every space is considered to be Tychonoff. Author mentions that.

That's good.  It was surprising that the results would fail, as the authors are well known topologists.

Another name: weakly normal

Another name: weakly normal, see e.g. Dugundji

That would have nothing to do with the notion in https://www.sciencedirect.com/science/article/pii/S0166864196001150, right?

it's a different property

I found somewhere that regular countably paracompact space is pseudo-normal.
Thus if we were to find a regular countably paracompact pseudocompact but not countably compact space, then this would be an example of the theorem failing in general.
All the corkscrews included in Steen and Seebach seem like good candidates, but their entries on pi-base seem very incomplete...

Both T404 and T401 are "immediate from the definitions", so they have no refs. Is a ref needed in such a case? If yes, we could add just a ref to the definition.

Adding this to the next community call.

Good comments here but don't want the PR to get too bloated, so maybe other improvements can be made later. Since @prabau made some tweaks, can @lyengulalp or @ccaruvana approve and merge?

Paging Drs. @ccaruvana and @lyengulalp 😆

Sorry for the delay. I will check on this and https://github.com/pi-base/data/pull/407 soon.
One thing I'm noticing here right off the bat is that there is a conflicting file: paraphrased S76/prop/P13

I've merged in main to address the conflict.

Thanks @StevenClontz ! Out of curiosity, why did P65 (cardinality continuum) get removed from S76? It isn't deduced from any other properties, it doesn't seem.

That's a mistake I made while merging. Will add it back in.

Also out of curiosity (but I did agree with it), why was P116 Pseudocomplete deleted (if not just the fact that there are no theorems/spaces referencing it)?


refactor: aliasing for server packages. lib for airtable + slack

Solves aliasing (#11 ) for everything but react app.
Also introduces lib for shared airtable + slack functionality

@alexquick @piratefsh I'm going to merge this and leave the wider airtable refactor for comments

👍


Add version information in some functions

This PR contains some minor fixes in docstrings only:

Use .. versionadded:: RST directive in docstrings to make it more visible when something was added
Minor wording fix in docstrings (versions -> version strings)

As this PR is only about docstrings, it shouldn't create any problems, so merging it.


T000 - Talktorial template

Details

Talktorial ID: T000
Title: Talktorial template
Original authors: @dominiquesydow
Reviewer(s): @AndreaVolkamer
Date of review: 15.12.2020

TODO
Update template w.r.t. @AndreaVolkamer's suggestions (that she send via PM - copied here):

[x] (it is self-explanatory, but one could add a note at the beginning that examples are taken from T001)
[x] Practical: Short summay -> Short summary
[x] In the path description make it even more explicit, that no relative paths should be given
[x] Info for imports (copy info on ordering from issue (?))
[x] maybe for later: generally we could add some general tips from the PR description in here, I will list a few here

[ ] Style guides black, Pep8, …
[x] If functions are used, use docstrings, copy one example over? (one more comment on fcts (local/global variables - do not use globals in function) + link to docstring documentation
[x] Or tips at the end:

Clear output and rerun, does it finish without errors?
Deterministic behavior/output? (help with CI comments)
Check runtime?

[x] In talktorial practical header repeat once that one should make sure the titles are the same as above (as well as the indentation)

Hi @AndreaVolkamer ,
This PR is ready for your review.
https://github.com/volkamerlab/teachopencadd/blob/ds-t000-revamp/teachopencadd/talktorials/T000_template/talktorial.ipynb
I did not add an general comment on

Style guides black, Pep8, …

since I think that Jaime or Jeff wanted to set up a document on best practices anyways, which we will be able to link here in the future.
I did referring though to (a) specific PEP8 guidelines e.g. for imports and (b) our template issue.

Great, thanks, @AndreaVolkamer - all your suggestions are integrated. Will merge now.


:recycle: Refactor the repository interfaces and implementations to d…

…ecrease the interdepencency among classes.

We have exactly the same logic in ConceptMapFolderRepository and CodeSystemFolderRepository. Maybe we can merge these repos and manage them from a single place.

This is a good suggestion. I would prefer implementing such a refactoring in another effort/branch after completing this.


Add documentation for Datadog scaler

This PR adds documentation for a new Datadog scaler.
Related PR for the scaler itself: https://github.com/kedacore/keda/pull/2354
Checklist

[x] Commits are signed with Developer Certificate of Origin (DCO)

I'll be a pain but can you align with this formatting please?
https://github.com/kedacore/keda-docs#writing-documentation-for-a-scaler

I'll be a pain but can you align with this formatting please? https://github.com/kedacore/keda-docs#writing-documentation-for-a-scaler

Not a pain at all! I had missed that! Thanks a lot for the quick reviews, I will fix that now.


Not detecting checks or mates when reading a PGN file

When reading in a file, ChessForge relies on the notation in the file to show check or mate symbols. Consider checking this by the program itself. Need to measure performance impact though.

Fixed


Accept hyphens in jsonpath

This pr adds hyphens ("-") in the map of allowed characters in jsonpath.
According to the provided test, some jsonpath such as $.foo-bar are now possible :)

The reason - was not included is that it is a problem parsing filters like foo[?(@.a-b)] versus<EMAIL_ADDRESS>- b)]. If I can verify that there is a way to assure there is no issue there then I'll merge. You can also use the bracket notation to have a - in a path name.

Here is a concrete example of the issue with allowing "-" or other math operators. Try<EMAIL_ADDRESS>- 1 == @.y)] on [{"x":1,"y":0}]. It should match. Now take the tight way that many people use<EMAIL_ADDRESS>== @.y)]. Is that meant to be a key of "x-1" or x - 1? The results are ambiguous. That's the reason -, +, *, and other common math operators are not parsed as path elements. You can use the bracket notation for  such as $[?(@["x-1"] == @y)] on [{"x-1":1,"y":1}] to get a match though.

@nervo care to discuss or come up with alternatives?

Unless you can figure out an efficient way to determine the intent of the user to disambiguate the use of hyphens in a path versus a minus sign in and equation I have to close this PR. I suspect there is a way to do so by looking at the operators in the script but it's not something I'm will to tackle yet.


[WIP] New vault page

This creates a new route under /vault/:vaultId for vault details and actions. Each pool summary on the vaults page is now a link.
Closes #58

You can mark it as a draft while you are working on it FloorLamp :)

Would it make more sense to keep the routing, but show this as a modal rather than an actual navigation page?
This way people can click around without having to go back and forth in history, especially with the main page being as heavy as it is.

I tried this as a modal initially:
https://cdn.discordapp.com/attachments/758368074968858645/813002704842391562/Screen_Shot_2021-02-21_at_17.55.21.png
The disadvantage of using a modal is that it's not super mobile friendly. Having a separate page also allows for more vault specific queries to be run.
Another idea is to move the vaults list to a drawer on the left, and show vault details on the right. Not sure if this is great on mobile either though.

@DefiDebauchery yes, i think we can discuss it
https://discord.com/channels/755231190134554696/758368074968858645/813011504009576458

Hi @FloorLamp
Soon we gonna have V2 UI https://vote.beefy.finance/#/beefy/proposal/QmUmnXWJwDQwTDehqdGZAtfwFPHKc2zu6VVs58kfyNpaLZ
And it might be not needed to change vaults behaviour now, as it's gonna be changed soon again.
I'm talking about debates should we open dialog, or keep expanded/collapsed, or add animations.
But separate vault page with deeplink is very cool, as we can share it.
So, what if we drop all changes and only keep routing one "vault/:vaultId".
And have a vault page that is 1:1 current vault card + back to the vaults button.
I think we will close issue then.


Generator turns message options into string

An option definiton can be a message with fields, e.g. a version and an exception_type field:
    def test_parser_generator_transparency_for_options(self):
        from proto_schema_parser.parser import Parser
        from proto_schema_parser.generator import Generator
        SCHEMA_TEXT = '''service TestService {
  option (test.options.v1.service) = {
  version: { major: 1 minor: 0 patch: 0 pre_release: "alpha" }
  exception_type: "test.types.v1.Exception"};
  rpc TestMethod (TestRequest) returns (TestResponse);
}'''
        ast = Parser().parse(SCHEMA_TEXT)
        print(Generator().generate(ast))
        self.assertEqual(Generator().generate(ast), SCHEMA_TEXT)

This test fails, as the generated option has quotes around the braces that enclose the message, as can be seen from the printed output:
test_parser_generator_transparency_for_options (test_schema_parser.TestSchemaParser) ... service TestService {
  option (test.options.v1.service) = "{
  version: { major: 1 minor: 0 patch: 0 pre_release: "alpha" }
  exception_type: "test.types.v1.Exception"}";
  rpc TestMethod (TestRequest) returns (TestResponse);
}

Yes, I haven't implemented the part that handles message literals. The grammar is:
optionValue: scalarValue | messageLiteralWithBraces;

messageLiteralWithBraces: L_BRACE messageTextFormat R_BRACE;

messageTextFormat: ( ( messageLiteralField ( COMMA | SEMICOLON )? ) | commentDecl ) *;

messageLiteralField: messageLiteralFieldName COLON value |
                       messageLiteralFieldName messageValue;

messageLiteralFieldName: fieldName |
                           L_BRACKET specialFieldName R_BRACKET;

specialFieldName       : extensionFieldName | typeURL;

extensionFieldName     : qualifiedIdentifier;

typeURL                : qualifiedIdentifier SLASH qualifiedIdentifier;

value         : scalarValue | messageLiteral | listLiteral;

messageValue  : messageLiteral | listOfMessagesLiteral;

messageLiteral: messageLiteralWithBraces |
                  L_ANGLE messageTextFormat R_ANGLE;

listLiteral: L_BRACKET ( listElement ( COMMA listElement )* )? R_BRACKET;

listElement: scalarValue | messageLiteral;

listOfMessagesLiteral: L_BRACKET ( messageLiteral ( COMMA messageLiteral )* )? R_BRACKET;

messageDecl: MESSAGE messageName L_BRACE messageElement* R_BRACE;

As you can see, it gets quite complex. Definitely doable, but I haven't spent the time on it. I'll poke at it, but no promises.

I appreciate the complexity or novelty compared to the rest of the grammer - these are a bunch of literals rather than definitions.
Adding this at some point would indeed be very nice - currently I'm using some RE to do specific parsing of the internals of the message.
My ticket was actually only intending to ask for a smaller first step - avoiding the quotes around the re-generated message.

@johan-groenenboom I think I've got the parser and generator updated to properly support message literals in option values in https://github.com/criccomini/proto-schema-parser/pull/41. Building a release now.

@johan-groenenboom I just published 1.4.0 here: https://pypi.org/project/proto-schema-parser/1.4.0/
Please let me know how it goes. Closing this for now. We can re-open if you discover issues.

Hi Chris, I think I'm running into a python version compatibility issue again:
File "C:\Python38\lib\site-packages\proto_schema_parser\generator.py", line 241, in Generator
self, elements: list[ast.MessageValue], indent_level: int
TypeError: 'type' object is not subscriptable

I also noticed that for options the field node.element.name has brackets around the string, is this intentional or should this be considered an issue?

Hi Chris, thanks again for your efforts. I think I'm running into a python version compatibility issue again: File "C:\Python38\lib\site-packages\proto_schema_parser\generator.py", line 241, in Generator self, elements: list[ast.MessageValue], indent_level: int TypeError: 'type' object is not subscriptable

Ah, my bad. Sorry about that. Fixed here: https://github.com/criccomini/proto-schema-parser/pull/42

I also noticed that for options the field node.element.name has brackets around the string, is this intentional or should this be considered an issue? For me the brackets were unexpected - should I submit another issue for this?

You're talking about the generator, right? Can you give me an example of what you mean?

Thanks for that fix - it works - will you release a new version for it?

I also noticed that for options the field node.element.name has brackets around the string, is this intentional or should this be considered an issue? For me the brackets were unexpected - should I submit another issue for this?

You're talking about the generator, right? Can you give me an example of what you mean?

proto_text = """
service TestService {
    option (test.major_version) = 1;
}
"""
syntax_tree = Parser().parse(proto_text)
for node in syntax_tree.file_elements:
    if isinstance(node, ast.Service):
        for element in node.elements:
            print(element)

gives the following output:
Option(name='(test.major_version)', value=1)

I suppose the name of the option should be 'test.major_version' without the brackets?

Option names refer to fields on the various concrete options messages, described in more detail in the next section below. Parenthesized names refer to extension fields. An extension on one of the concrete option types is also called a "custom option".

Hmm, yea, TIL. I'm open to whatever you prefer. In the meantime, I'll cut a release.

Ok, I've published 1.4.1:
https://pypi.org/project/proto-schema-parser/1.4.1/
Should have the latest fixes. :)

Thanks for the new release, it helps me to move forward with my project!
For a more limited sub-topic of the hairy topic of option naming : if an option has a parenthesized name with spaces inside the parentheses, e.g. "(  my.options.v1.service  )", then, with the current parser, the name field of the parsed element will come out exactly like that, including the spaces. This makes it more difficult to look for an option with a specific name, as it can be "spelled" with so many white space variations. So having the parser remove that whitespace would be a useful feature / improvement?

Actually, just pushed a fix here:
https://github.com/criccomini/proto-schema-parser/commit/37287dc84ca6ae6a596484bd58890ca1328c3fe2

1.4.2 has been published with name normalization. :)
https://pypi.org/project/proto-schema-parser/1.4.2/

I have integrated version 1.4.2 and everything works fine. If I'm not mistaken I have all I need for my application to work - so  thanks again for the fixes, and being so responsive!


Effect Control

Hey guys,
Thanks for the amazing job upgrading this module!
I've found one more features which would be great to have:
Effects control (on/off)
Maybe even parameter control (+/- XX% ? )
Of course feedback or variables for the values would be a plus :)

Can you tell me shortly, please, where I can find the effects on/off? 😅

oops sorry i wasn't clear enough
The easiest way to toggle the effects on and off for each channel would be in the "FX Sends" tab and via the Mute buttons on each channel and in each FX category (Reverb, Delay, Room)

Thought the parameters are found in each individual channel page

Aah I see 😊 FX channel mute and FX bus mute already works in the current version, so maybe that's already everything you need? 😃

oh my bad! that should be it then! that's great. Sorry due to an injury I haven't really been working with the UI recently.
I will try it hopefully next week, but close this in the meantime. Thanks again!


mpv: prepare for swift on darwin

Description of changes
In anticipation of Swift coming to Darwin (#189977), these changes will allow swiftSupport to simply be changed to stdenv.isDarwin when the time comes, without encountering any compile errors.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

I had a slightly different change prepared: https://github.com/stephank/nixpkgs/commit/4ce183cdd525da0f3cf4cec14356d056dbabed0e

https://github.com/NixOS/nixpkgs/pull/189977 has been merged.

We still have to wait for Swift to land on master, I believe.
Regarding the difference between our changes:

Does AVFoundation enable something extra? It seemed to build without it, but maybe I missed some piece of functionality in testing.
In my testing, xcrun was required for the build system to find Swift. Does the Swift-specific stuff build and work for you without it?
I think it's important we don't pull in the Swift compiler as part of the closure, but just its lib output. Could you verify that's the case in your change?

@stephank the base can simply be changed to staging.
Since you also have an implementation already (which I've used for a bit actually), you can of course always open your own PR.

Superseded by #214944.


Wrong Usage Query

[Enter feedback here]
In following query, either change BillableDataGB  to BillableDataMb or divide by 1000
Usage
| where TimeGenerated > ago(32d)
| where StartTime >= startofday(ago(31d)) and EndTime < startofday(now())
| where IsBillable == true
| summarize BillableDataGB = sum(Quantity) by Solution, DataType

sort by Solution asc, DataType asc

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

ID: fed35a55-0db9-4afa-9a80-fe9adac1e7d7
Version Independent ID: 67af640b-9a6c-bf24-3a99-14ad8dab849f
Content: Manage usage and costs for Azure Monitor Logs - Azure Monitor
Content Source: articles/azure-monitor/logs/manage-cost-storage.md
Service: azure-monitor
Sub-service: logs
GitHub Login: @bwren
Microsoft Alias: bwren

@piyushgupta12 Thanks for your comment! We will review and provide an update as appropriate.

@piyushgupta12 I have verified and updated the document as required. The change should reflect in the document in some time i.e., in less than 24 hours. Thanks again for good catch and providing the feedback!


Allow upload of doc/pptx

File upload currently only allows text of pdf, we could use our tika parser to enable other upload types.
As conversion would be done on the server, this would require adding a simple entrypoint to convert files.

As discussed IRL with @Fraggle and @flvndvd this is on hold until we discuss about the upload/create doc UI and the possible changes - currently uploading a document allows the user to edit and modify the content. As the conversion for pptx/docs is done on the server, this implies sending the file to the server and getting it back on the browser. Although it's perfectly doable we'd rather wait until this UI part is clarified to avoid refactoring.


Added /opt/local/bin as a possible path extension.

Hi!
On my OSX machine, the command-line version of cmake was installed in "/opt/local/bin", which your package couldn't find.
This change fixes that.

Thank you for the PR, but you should modify your PATH setting outside of the package. The reason /usr/local/bin is in there is legacy only and I will remove it as soon as Atom 1.7 hits. Atom will read your shell settings at that point.


[CuBLAS] Support implicit broadcast in batch_matmul

Closing #7730
This PR improves CuBLAS batch_matmul to support implicit broadcasting (i.e., the first dimension of matrix B is 1). Before this PR, the added test cases will throw errors like Check failed: BatchCount3D(B) == batch_size.
cc @masahi @tqchen

Thanks @comaniac, we should do this for rocblas too @csullivan @altanh


feat(build): provide a lite build

Now providing a lite browser build:

search only
vanilla JS only (no angular, jquery lite builds for now)
same export name (algoliasearch)
now 5.93kb gzipped (versus 20kb)
IE11/10/9 not natively supported, use http://cdn.polyfill.io/v2/docs/
or just provide the Promise polyfill in the global object (window)
same init usage
has
client.search/index.search/clearCache/setRequestTimeout/setExtraHeader/..
no write/indexing/waitTask/settings methods => search only
available on jsDelivr using algoliasearchLite[.min].js
also requireable using
var algoliasearch = require('algoliasearch/dist/algoliasearchLite.js');

fixes #215

That's awesome @vvo!

5.93kb
:dancers:
We can have IE9/10/11 compat but it would weight something like 7-8kb, what do you think?

It's 8KB with the Promise polyfill. I will not do it for now, let's wait for some users to ask for it before making plans

Personally I prefer without polyfills. ES6 modules make it easy to add extra polyfills if required.

So this is passing tests, lets wait monday morning for a release :)

By the way, how can we "ES6 import" this lite version? Maybe it should be a separate NPM package.

import 'algoliasearch' from 'algoliasearch/dist/algoliasearchLite.js' should do it.. once released.
In the meantime you should be able to build it yourself if you want:
npm install
NODE_ENV=production npm run build

Great!

We can have IE9/10/11 compat but it would weight something like 7-8kb, what do you think?

Are we able to add the Promise polyfill only for the <script> build? If so I would go that way!


Fix string comparison for ErrorDetectionSimpleRegexp

Changes
Fix string comparison for ErrorDetectionSimpleRegexpKey

Submitter Checklist

[ ] ♽  Run make test lint before submitting a PR (ie: with pre-commit, no need to waste CPU cycle on CI
[ ] 📖 If you are adding a user facing feature or make a change of the behavior, please verify that you have documented it
[ ] 🧪 100% coverage is not a target but most of the time we would rather have a unit test if you make a code change.
[ ] 🎁 If that's something that is possible to do please ensure to check if we can add a e2e test.
[ ] 🔎 If there is a flakiness in the CI tests then don't necessary ignore it, better get the flakyness fixed before merging or if that's not possible there is a good reason to bypass it. (token rate limitation may be a good reason to skip).

does that print less logs in controller?

does that print less logs in controller?

Yes

we probably should do a minor release if that can be integrated in operator

ya v.15.6 right


improved loading indication

Closes #170

Test notes:
Confirm the loading indicator given the following actions:

upon codebook initialization
Group by dropdown changes
filter changes
bar is clicked to effect highlighting
Clear Highlighting button is clicked

Here's a screenshot of the desired behavior mentioned above.


<IP_ADDRESS>启动报错，但是能正常启动

dubbo配置

报错信息

nacos依赖

Environment

Dubbo version: <IP_ADDRESS>
Operating System version: win10
Java version: 8

Steps to reproduce this issue

xxx
xxx
xxx

Pls. provide [GitHub address] to reproduce this issue.
Expected Result
What do you expected from the above steps？
Actual Result
What actually happens?
If there is an exception, please attach the exception trace:
Just put your stack trace here!

更换版本2.7 能正常启动，不会出现这个错误信息

This seems to be that you have introduced multiple nacos versions in your project, dubbo introduced nacos 2.x in 3.x, try to clean up the nacos version to solve the problem.

Dubbo 3.0 及更高版本需要升级 nacos 到 2.0 版本以上（client 和 server 都需要升级）

No feedback for a long time, please close the issue temporarily. If there is still a problem, you can reopen it.


Provide the high-level source code (i.e. TypeScript/ECMA 6).

I am working with your leaflet package and would like to make some changes. My guess is that you are using a higher level language, such as TypeScript, and then building that to JavaScript. I guess that because there is code like this that, to me, seems an odd way of writing things:
import Leaflet from 'leaflet';

export function configure(
  frameworkConfig,
  { LeafletDefaultImagePath =<EMAIL_ADDRESS>} = {}) {

    Leaflet.Icon.Default.imagePath = LeafletDefaultImagePath;
    frameworkConfig.globalResources('./leaflet.js');

}

Are you using a higher-level code and the building to create the above syntax? If you are, can you include that code in your repo.

No worries. I understand now that you're using object destructuring. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Destructuring_assignment#Object_destructuring